Comments on: Outlook Anywhere is ‘broken’ on IPv6 in Windows Server 2008

By: Kevin Reeuwijk

Kevin Reeuwijk — Tue, 11 Aug 2009 06:07:34 +0000

Jacob,

your best bet is to first determine the root cause of your problem using https://www.testexchangeconnectivity.com/

Regards, Kevin

By: Jacob

Jacob — Tue, 11 Aug 2009 05:36:57 +0000

Dear Kelvin,

Thanks for these solutions, I have one small problem to ask, I have ISP who is my mail exchange “mail.mca-t.go.tz” and I have internal exchange 2007 server on win 2008 sp1 with different hostname from “mail”, Internally OWA is working, and I have done all the fixes you provided but still doesn’t work, I have also done all the HTTP redirection, Enable Outlook Anywhere, RCP over HTTP, local DNS MailExchanger records, all those things, I still can’t have it anywhere only internally what could be the problem ? Please

By: Chip

Chip — Wed, 29 Jul 2009 19:48:00 +0000

Thank you thank you! Even with Rollup 9, they still haven\’t fixed this. Implemented your hosts work around and Outlook Anywhere is working!

By: Dwayne

Dwayne — Tue, 09 Jun 2009 05:11:25 +0000

AWESOME !!! took me a lot of searching, yur site needs to come up 1st when you google this error !
Kudos for the detailed information.

By: Lisa

Lisa — Mon, 25 May 2009 23:09:58 +0000

Thank you! I was laughing at the comment about someone getting tears in their eyes when it worked but now I know the feeling!

By: Qwerty

Qwerty — Tue, 27 Jan 2009 22:47:37 +0000

First…THANK YOU!!

When on a machine configured behind the firewall and on the network, OWA worked fine when the machine was moved outside the firewall and off the network. However, if first configured outside the firewall and off the network, OWA, as you described, did not work. I struggled with this for a few days tweaking my DNS, router/firewall, Exchange settings, autodiscover, etc..

Then, through another blog, I found your post. SUPURB!!!

By: Al

Al — Wed, 17 Dec 2008 17:00:47 +0000

I was trying for 5 weeks now for outlook anywhere to work. The level of frustration was unbelievable. Thanks for sharing your expertise

By: Matt

Matt — Thu, 27 Nov 2008 06:18:04 +0000

I\’ve been trying this and spending many, many hours on it. When I run netstat -an it shows :::1:6004 LISTENING and 127.0.0.1 6004 LISTENING along with 6001 and 6002 so I\’m not sure this is my problem. I\’m running windows 2008, Exchange 2007 SP1, have 3rd party single cert (haven\’t got a SAN Cert). It prompts me for a password and then fails after 30 seconds saying exchange server not available.

My internal FQDN of the exchange server is different from the external FQDN. Have a separate windows 2003 DC/GC.

PLEASE HELP………………. I\’M DYING TRYING TO FIGURE THIS OUT………… TOO MANY HOURS….

By: Gerrit

Gerrit — Wed, 12 Nov 2008 14:27:44 +0000

THANK U THANK U THANK U THANK U THANK U THANK U THANK U THANK U THANK U THANK U THANK U THANK U THANK U THANK U THANK U THANK U THANK U THANK U THANK U THANK U THANK U THANK U THANK U THANK U
so happy with the solution, I\’ve spend over 30 hours of testing, reinstalling configuring etc etc.

hero!

By: Sebastian

Sebastian — Mon, 03 Nov 2008 07:48:00 +0000

RPC over HTTPS is broken also in W2003 R2 (tested with 64 bits version and Exchange 2007) when hosting virtual machines at the same time, even when IPv6 is disabled. Solved uninstalling IPv6.