Exchange Server 2007 and Windows Server 2008 Outlook Anywhere not working
Posted by Chad McGreanor on June 21, 2009
I have recently began working with Exchange 2007 and Windows Server 2008. After I disabled UAC and all the firewalls (yes there is more then 1) it was actually usable. I installed Exchange Server 2007 which I have done many times before and configured all the autodiscover settings and went to fire up Outlook anywhere and it did not work. So I read around and saw there were some issues with IPv6 with Exchange Server 2007 SP1 if you did not have Update Rollup 4 or greater. I had Update Rollup 8 installed so I did not think that would pertan to me. So here is the errors I got:
When attempting to connect using Outlook 2007:
- The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action.
When I tested connectivity using http://testexchangeconnectivity.com I got the following:
“Failed to ping RPC Endpoint 6004 (NSPI Proxy Interface)”
So I went back to the server and tried to telnet to each rpc port on the CAS server. The ports RPC over HTTP uses are 6001, 6002, and 6004. I could connnect to all of them except 6004. The solution to the problem was to disable IPv6. Solution below:
I went to the network card properties and de-selected IPv6 and then went to the HOSTS file and commented out :::1 localhost then added the hostname and fqdn of the cas server. This could be the same server you installed all of your roles on, or a seperate CAS server. Then I added the ip address of the server as well:
ssfex1 10.1.2.2
ssfex1.ssf.voxns.com 10.1.2.2
Attempted to telnet to ssfex1 6004 and everything worked. i tested connectivity at http://testexchangeconnectivity.com and all tests passed. Then I tried Outlook 3007 again and was able to connect this time.
So apparently IPv6 is still an issue even if you have all of your patches on.
Jakub said
Thank you !
This is what I needed to solve connectivity problems. I am not sure why do you put hostname and fqdn to hosts file. In my case disabling IPv6 and commenting :::1 solved issue.
Thanks again
Chad McGreanor said
Im glad my trouble helped you out.