EXCHANGE: Outlook 2007 Cannot collect Exchange Mail

I have setup a new SBS2k3 server with Exchange.

The domain is registered and Host and MX records are pointing to domain.

Wizards were used to setup users and computers and (almost) everything is
working as expected. I can connect remotely to both workstations and
server.

Outlook 2007 is installed on one of the Vista workstations. I can send
emails (in fact I just tested it by logging in with RWW starting Outlook2007
and sent myself a message, which I received OK).

The problem is I am not receiving messages at the workstation. Using
Exchange I can see 44 messages in the mailbox still waiting to be delivered.
Exchange does not seem to be getting the message to deliver the mail.

What have I not done.? Or what do I need to do ?

TIA

Malcolm
Townsville, Australia

Malcolm Cheyne wrote:

> Outlook 2007 is installed on one of the Vista workstations. I can
> send emails (in fact I just tested it by logging in with RWW starting
> Outlook2007 and sent myself a message, which I received OK).
>
> The problem is I am not receiving messages at the workstation. Using
> Exchange I can see 44 messages in the mailbox still waiting to be
> delivered. Exchange does not seem to be getting the message to
> deliver the mail.
>
> What have I not done.? Or what do I need to do ?

How is Outlook 2007 configured to access the mailbox - using cached
Exchange mode? If yes, try deleting the user's local cache file
(usually called outlook.ost) - while OL2K7 is closed - and try OL2K7
again.

--
Regards,
Steve.

Thanks for reply spm

That made no difference. From Outlook with Exchange selected I did a
"Repair" which showed an error saying ...

"Problem connecting to server" with red X alongside UserName@FQDN

FQDN is the same as MX record and UserName is same as in user setup.

Malcolm



"spm" <nospam@coco.dot.co.dot.uk> wrote in message
news:xn0f932rg29x5o000@news.microsoft.com...
> Malcolm Cheyne wrote:
>
>> Outlook 2007 is installed on one of the Vista workstations. I can
>> send emails (in fact I just tested it by logging in with RWW starting
>> Outlook2007 and sent myself a message, which I received OK).
>>
>> The problem is I am not receiving messages at the workstation. Using
>> Exchange I can see 44 messages in the mailbox still waiting to be
>> delivered. Exchange does not seem to be getting the message to
>> deliver the mail.
>>
>> What have I not done.? Or what do I need to do ?
>
> How is Outlook 2007 configured to access the mailbox - using cached
> Exchange mode? If yes, try deleting the user's local cache file
> (usually called outlook.ost) - while OL2K7 is closed - and try OL2K7
> again.
>
> --
> Regards,
> Steve.

Malcolm Cheyne wrote:

> That made no difference. From Outlook with Exchange selected I did a
> "Repair" which showed an error saying ...
>
> "Problem connecting to server" with red X alongside UserName@FQDN
>
> FQDN is the same as MX record and UserName is same as in user setup.

Well, I find OL2K7's account 'repair' function very flakey, and never
rely on it. Go to OL's Account Settings for the Exchange account and
check all settings manually (press the Change button, rather than the
Repair button to access all the account's settings). You still don't
say whether you use cached mode, and you don't say whether you use RPC
over HTTPS, for instance. For cached mode with RPC over HTTPS, the
following settings should be in force:

MS Exchange server: servername.yourlocaldomain.local
Use cached Exchanged mode: Yes
User name: username (will be underlined when present - press the Check
Name button if not.

Other settimgs (press 'More settings...' button to access):

Advanced
Use Cached Exchange Mode
Download shared folders and Download Public Folder Favorites, as
desired
Offline Folder File settings (points to your OST file)
Security
Encrypt data between MS Office outlook and MS Exchange (needs
server's SSL certificate installed)
Logon network security: Negotiate authentication
Connection
Connect using my Local Area Network
Connect to MS Exchange using HTTP
Exchange proxy settings:
Use this URL to connect to my proxy server for Exchange: (https://)
FQDN-of-server (i.e., NOT the internal server name!)
Connect using SSL only
Only connect to proxy servers that have this principal name in
their certificate: msstd:FQDN-of-server
On fast networks: As desired
On slow networks: Connect using HTTP first, then TCP/IP
Proxy authentication: Basic authentication
(or NTLM authentication if you also enable it in your IIS
Default Web Site's RPC directory)

--
Regards,
Steve.

Malcolm Cheyne wrote:

Sounds like it might be a certificate issue. Please see inline...

> How do I check if this is installed? If just create through Internet
> wizard I did create a certificate using FQDN. e.g domain.com.au

OK. I assume you have created a self-signed certificate. So, on the
problem Vista machine, what happens if you connect to the user's
mailbox using OWA (https://localservername/exchange)? What is the
(exact) error message you encounter?

> Was set to NTLM. Changed to Basic
>
> > Default Web Site's RPC directory)
>
> What/where is this ?

NTLM auth is OK if your RPC directory allows it. To check...

On your server, open Server Management go to the "Advanced Management"
branch and expand down to the following:
Internet Information Services -> your-server-name -> Web Sites ->
Default Web Site (and click on the latter).
In the right-hand pane right-click Rpc in the Name column and choose
Properties.
On the Directory Security tab click the Edit button under
"Authentication and access control".
If only Basic Authentication is selected, you will need to use Basic
Authentication in your OLK2K7 account settings for the proxy. If you
also select "Integrated Windows authentication" here for the RPC
directory, then you can use NTLM auth in OLK2K7.

--
Regards,
Steve.

Malcolm Cheyne wrote:

> This is the same message I get when logging in with \remote
>
> "There is a problem with this website's security certificate."
>
> Continue to this website (not recommended)
>
> Which I read somewhere to just ignore and continue.

Yes, continuing is fine, but you also need to install the self-signed
certificate (generated by the CEICW on your server). This process is
described in detail here:

http://blogs.technet.com/sbs/archive...-a-self-signed
-certificate-as-a-trusted-root-ca-in-windows-vista.aspx

Having done this, can OLK2K7 now access the user's mailbox OK?

--
Regards,
Steve.

Sorry to take so long to get back. For some reason the little peepers
wanted to close at 4.30 am. ;-)

> Having done this, can OLK2K7 now access the user's mailbox OK?
>

No.

I can view the Certicate in IE7. It shows the correct FQDN with the
following status:

This CA Root certificate is not trusted because it is not in the Trusted
Root Certification Authorities store.

I found the Certifcate in the "Intermediate Certification Authorities",
exported it and imported it into "Trusted Root Certification Authorities".

Now I see the padlock with OWA from my (remote) computer.

Logged in with RWW and looked at IE7 Certificates on (client) computer.
Certificate *IS* in Trusted Root .... Certification says "This Certificate
is OK".

Using Exchange System Manager I looked in Server | Queues and can see four
emails Q'd for the one user. In this users mailbox, using Ex Task Wizard I
can see Mobile Services and Protocols enabled (3 each). I disabled POP3 for
a test (we are only using IMAP4) .

Rerun CEICW (Allowed it to configure Netgear DG834 Router) I'm only using
one NIC (not my normal policy and I'll certainly be using two NICs in future
installs).

"Additional Services"- Selected all.

"Web Services" - Selected all - except Business Web Site (wwwroot)

Do not change Web server certificate (Web server name (greyed out) is
correct FQDN)

Enable Internet email

Use DNS to route email

Use Exchange with mail delivered direct to server.

Email Domain name - correct FQDN
====================================
(dynDNS.org shows following for CustomDNS settings .....)
Hosts (A) Records - correct FQDN
Mail eXchanger (MX) Records - correct FQDN - Pref 5 - Data = same FQDN
Alias (CNAME) Records - www.FQDN - Deleted this (not using).
No other info set up at dynDNS.org
====================================

Enable Exchange Server to remove ...... accepted all defaults

Finish ...

(Internal Error in IE7 on Firewall configuration - totally expected - log
back in with RWW)

The Wizard has completed successfully.

Checking Event Viewer | Application I see a warning ....

"Verify that the Microsoft Exchange MTA service has started. Consecutive
ma-open calls are failing with error 3051. " EventID 2000

I can see this is related to X400 - which we do not use.

I have deleted all events information and will monitor these over the next
few hours/days.

All Automatic Services are started (except Performance logs - not necessary)
Started then stopped - No work to do.

From my normal computer I sent an email to malcolm@FQDN (an admin on the
server) as well as a drop copy to myself malcolm@xxxx.com.au (which arrived)

I then setup a new installation of Outlook2007 on my Vista system (No RWW
stuff here) The Account Configuration wizard started and I was creating an
account for malcolm@FQDN During the online search for server settings OL
successfully established Network Connections but then failed on the "Search
for malcolm@FQDN". The message is "An encrypted connection to your mail
server is not available. Click next to attempt an unencrypted connection".
This also failed and I am now asked to verify the email address (which *IS*
correct) and click Retry. We now move to "Manually configure server
settings" where I select MS Exchange. Asked to enter MX server FQDN and
select "Use Cached Ex Mode" and the User Name "malcolm". Click to "Check
Name" and get an error "The connection to MS Exchange is unavailable.
Outlook must be online or connected to complete this action". (Dughh!! We
are online!) Next test .... "The name cannot be resolved".

I am lost and going around in circles.

I can ping the server with a response time of 65ms.
I can nslookup the FQDN and resolve to the server IP
server=FQDN
set type=mx

DNS request timed out (2 seconds). Now we are getting somewhere ....

I have posted a request for help to support at dynDNS.org and am awaiting
their reply.

malcolm

> I am now a little confused. You say "I disabled POP3 for a test (we are
> only using IMAP4)". If you are setting up a "Microsoft Exchange"
> account in Outlook, then you are not using IMAP - you are using MAPI,
> or RPC over HTTPS (which is what I have assumed until now). RPC over
> HTTPS is the preferred approach, but you will need to set this up while
> your computer is connected locally to the LAN at the office. Once set
> up, you can then use if offsite. Again, if Outlook 2007's auto setup
> doesn't work then configure the Exchange account manually.
>

I'm sorry for the confusion. I last touched Exchange about 2-3 years ago.
Maybe I just used the wrong term.

Why can't I setup everything logged in remotely with RWW ? If I can setup a
system locally I should be able to also do it remotely (unless of course I
have to physically do something on the PC).


> If you are to use RPC over HTTPS remotely, you will need to have your
> Netgear router forward HTTPS (TCP port 443) to your server's internal
> IP address. Even though you have run the CEICW, I would advise checking
> this manually via the router's admin interface. Even though the CEICW
> can use UPnP to configure your router (provided the router also
> supports and enables it), many people prefer to do configure their
> router/firewalls manually.
>

Yes I configured the router for port 443 and 4125 as well.

FYI this is the reply that I just received from dynDNS .....

====================================
I checked all of the name servers and I was able to get a reply from all
of them. Your mx records look fine. You may be having a local dns issue.

I'm also able to connect to your email server.
====================================
He then went on with a list of all the tests performed ..... All OK

I'm just wondering about that "local DNS issue". I'll login and check the
IP addressing.

Malcolm

> I'm just wondering about that "local DNS issue". I'll login and check the
> IP addressing.
>

On the server (Single NIC) ....

Windows IP Configuration:

Host Name ..................... SERVER
Primary DNS Suffix ........ xxxxxx.local
Node Type ..................... Unknown
IP Routing Enabled ......... Yes
WINS Proxy Enabled ..... Yes
DNS Suffix search List .... xxxxxx.local

Ethernet Adapter Server Local Area Connection:

Connection-specific DNS Suffix ... : <blank>
DHCP Enabled ............................ : No
IP Address .................................. : 192.168.0.2
Subnet Mask ............................... : 255.255.255.0
Default Gateway .......................... : 192.168.0.1
DNS Servers ............................... : 192.168.0.2
Primary WINS Server ................. : 192.168.0.2

Can somebody please verify if these are OK ?

Malcolm

I changed the DNS Server address to that of my ISP and Exchange is now
delivering mail.

HTH somebody else.

Malcolm


"Malcolm Cheyne" <malcolm@XXXXsbca.com.au> wrote in message
news:%23$zGPXszHHA.3536@TK2MSFTNGP06.phx.gbl...
>> I'm just wondering about that "local DNS issue". I'll login and check
>> the IP addressing.
>>
>
> On the server (Single NIC) ....
>
> Windows IP Configuration:
>
> Host Name ..................... SERVER
> Primary DNS Suffix ........ xxxxxx.local
> Node Type ..................... Unknown
> IP Routing Enabled ......... Yes
> WINS Proxy Enabled ..... Yes
> DNS Suffix search List .... xxxxxx.local
>
> Ethernet Adapter Server Local Area Connection:
>
> Connection-specific DNS Suffix ... : <blank>
> DHCP Enabled ............................ : No
> IP Address .................................. : 192.168.0.2
> Subnet Mask ............................... : 255.255.255.0
> Default Gateway .......................... : 192.168.0.1
> DNS Servers ............................... : 192.168.0.2
> Primary WINS Server ................. : 192.168.0.2
>
> Can somebody please verify if these are OK ?
>
> Malcolm
>

I have had exactly the same problem and have re-checked everything in this
thread.
I also have both external and internal DNS addresses in the server config.

Mine still does not work - Outlook 2007 just cannot connect to the Exchange
server.
I've also followed everything in the "Microsoft Exchange Server 2003 RPC
over HTTP Deployment Scenarios" document. All the tests in there for SBS
setup of HTTP over RPC give exactly the results they suggest and all the
configuration has been done according to the document. But I still can't get
Outlook to connect to the Exchange server.
OWA connects to the same URL perfectly of course.

Nick
=====================
=====================
"Malcolm Cheyne" wrote:

> I changed the DNS Server address to that of my ISP and Exchange is now
> delivering mail.
>
> HTH somebody else.
>
> Malcolm
>
>
> "Malcolm Cheyne" <malcolm@XXXXsbca.com.au> wrote in message
> news:%23$zGPXszHHA.3536@TK2MSFTNGP06.phx.gbl...
> >> I'm just wondering about that "local DNS issue". I'll login and check
> >> the IP addressing.
> >>
> >
> > On the server (Single NIC) ....
> >
> > Windows IP Configuration:
> >
> > Host Name ..................... SERVER
> > Primary DNS Suffix ........ xxxxxx.local
> > Node Type ..................... Unknown
> > IP Routing Enabled ......... Yes
> > WINS Proxy Enabled ..... Yes
> > DNS Suffix search List .... xxxxxx.local
> >
> > Ethernet Adapter Server Local Area Connection:
> >
> > Connection-specific DNS Suffix ... : <blank>
> > DHCP Enabled ............................ : No
> > IP Address .................................. : 192.168.0.2
> > Subnet Mask ............................... : 255.255.255.0
> > Default Gateway .......................... : 192.168.0.1
> > DNS Servers ............................... : 192.168.0.2
> > Primary WINS Server ................. : 192.168.0.2
> >
> > Can somebody please verify if these are OK ?
> >
> > Malcolm
> >
>
>