Re: EXCHANGE: Outlook 2007 Cannot collect Exchange Mail

Hi 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.

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.


Malcolm Cheyne wrote:

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@xxxxxxxxxxx
(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



--
Regards,
Steve.
.

Relevant Pages

  • Re: Exchange 2003 SP2 - able to send but not receive email
    ... product and not part of Exchange Server itself. ... OWA already setup and running - My whole goal is to setup this server to ... settings it successfully saved my settings - ...
    (microsoft.public.exchange.admin)
  • RPC over HTTP, Microsoft solution
    ... Exchange Server 2003 RPC over HTTP Deployment Scenarios ... Place a check in the box next to 'Certificate Services' and click 'Yes' ...
    (microsoft.public.exchange.setup)
  • Re: how to configure rpc over http connection for a client
    ... This is a server for my client. ... When i work at my office, outlook can connect to the exchange server. ... Yep - this is where you accept & then install the certificate after you get ...
    (microsoft.public.windows.server.sbs)
  • Re: Dead Exchange Server
    ... Microsoft Certified Partner ... Server, and matched up every setting on my default, then deleted the new one, ... I would suggest downloading Exchange Best Practice and SBS Best Practice ... > certificate that was generated with the install, but i made a new one> to ...
    (microsoft.public.exchange.connectivity)
  • SMTP Issues
    ... I have had numerous problems with trying to send e-mail since installing SBS ... 2003 with Exchange. ... I have SBS 2003 also set up as the DHCP server. ... settings as well as the "Small Business SMTP Connector" settings. ...
    (microsoft.public.exchange.setup)
Loading