|
damber -> Outlook 2003 fails to connect to Exchange 2003 (2.Mar.2005 6:08:00 PM)
|
After reading quite a few posts on this forum with regards to the issue of connecting Outlook 2003 client to the Exchange 2003 server, I thought it worth providing you with as much detail as I have on the issue I have experienced. It appears remarkably similar to the others - though none of them have been answered, so maybe one of the Exchange Guru's on this site can help us mere mortals figure out this issue.
- 1) I have installed a fresh copy of Windows 2000 advanced server and updated with all the latest patches / SP's etc. And installed a fresh copy of Exchange 2003 as the first Exchage 2003 server in the domain (I previously had 2000 and then moved to 2003, though after a bit of a disaster with some security software with Exch2003 and SP1, I had to remove all traces (all - including Active Directory and Registry) )
- 2) After adding SP1 to the install I configured a basic setup for the single server and enabled SMTP for a single domain. Then started all the services (and ensured the event log did not report any issues), including POP3, HTTP(OWA), SMTP, IMAP.
- 3) I have tested POP3, HTTP(OWA),SMTP, IMAP all succesfully - using Outlook as the client and IE6 browser for OWA
- 4) I can connect to the server for remote admin, and ping etc as you would expect. The DNS resolution is fine for FQDN, Hostname and IP Address via rDNS.
- 5) What I cannot do is access Exchange directly via the Outlook client using (I believe) MAPI. Which does not have a specific setting in the Exchange Manager to configure (that I'm aware of)
- 6) I tried to set up a new profile in Outlook by selecting Exchange Server as the type and then entering the server name (also tried the IP address here, and FQDN) and the username of a mailbox that works via OWA.
- 7) I get the following error message: "The Action could not be completed. The operation failed". Then when it automatically opens the popup window to confirm the details, it gives me this error: "The Name could not be resolved. The operation Failed".
- 8) Out of curiosity I deselected the "Use Cached Exchange Mode" to see if this was used during Setup or not. It is (in exactly what capacity I'm not sure). I then got a new message before the one above is shown, this stated: "Outlook could not logon. Check to make sure you are connected to the network and are using the proper server and mailbox name. The operation could not be performed because the connection to the server is offline"
- 9) I have checked the Event Log for any related errors on both the server and the client machine - I couldn't find any. I also temporarily disabled any firewalls, just in case.
It seems very much that the Outlook client just cannot access the Exchange Service (MAPI I assume). Which would indicate (as many other access methods work ok) that the server is not listening correctly for these requests. Or if the client is trying to get information from Active Directory then maybe it hasn't found what it needs ? Either way, I have ensured that all the services with Exchange are running without errors, still without joy.
Please can someone either:
1) let us know what this problem is, and how to resolve it, or if this is not possible..
2) tell us how the process works - i.e. what ports/protocols are used in this initial connection/query to the server and what services should be running to facilitate it.
I hope that one of the experts here can shed some light on this fairly common issue, which to date doesn't seem to have been given an answer.
Thanks in advance.
Damian
|
|
|
|