Issue:
User is setting up Outlook to connect to Exchange 2007 server. The user can access the server via POP3 and OWA (Outlook Web Access). The user can ping the server successfully.
When user tries to setup, he/she cannot verify his/her name - error is that "connection to Microsoft Exchange is unavailable."
Possible Solutions:
1. Outlook may be having some connectivity error with your profile. Can you Ping? Is port 135 open? If using a VPN to remotely access the server, is it down? Are you really using "Exchange mode" or are your POP3 or IMAP?
2. Registry settings could be corrupt, but not very likely.
3. Can Outlook on another workstation connect okay? If so, this is a workstation issue, not a server one.
Once you receive this error, you may still be able to connect in some cases: support.microsoft.com/kb/927481
It seems to depend on the registry values for the key DWORD ZeroConfigExchange. By simply clicking OK to the errors and setting up a new profile, it might work anyway!
Note: Setting up a new profile if you already have one is often not desirable. You lose local configuration options you previously had.
If port 135 was blocked, turned off the Firewall and test again. Set an exception for port 135 in Windows Firewall. While off confirm you can get into the Exchange server. You may find out that you still have to delete the current profile (Exchange Mail Account) and set it up again. Once you have done your first send-and-receive, try turning on the Windows Firewall and see if you next one succeeds.
Un-installing Office 2k3 and re-installing may fix this for you. Un-installing Office 2k3 and installing office 2k7 may fix this for you.
Check connectivity ...
Use a command window for the following tests...
(e.g. Start --> Run --> cmd and click OK
Can you ping the server?
e.g. ping exchange.mindwatering.com and click enter.
If successful, you will receive messages about ping the server with 32 bytes of data with how long each one took. If not successful, you will receive an unknown host error if DNS is not functioning, or you will get timed-out messages on the pinging if DNS works but your connection is bad. (Note: You can also get timed-out messages via ping if a firewall is blocking the pings from being sent or received back.)
Can you get to port 135?
Besides using the Outlook client, you can use telnet to check if a port is open.
e.g. telnet exchange.mindwatering.com 135 and click enter.
If successful, you will get a blinking cursor meaning that the connection was made. If not successful, telnet will give you an error that it could not connect. Close the window to kill your telnet connection.
Repair the Registry for Windows XP IP Network...
1. In a command window (cmd), type netsh int ip reset c:\ipresetlog.txt
(A log is written to c:\ipresetlog.txt file.)
2. Close the window by clicking the X or by typing exit and clicking enter.
3. Restart XP.
After the restart, try your connection again.
previous page
|