asked on
Exchange 2007 SP1 AutoDiscover issues
Hi,
I have posted previously about this but had no replies, so I'll be a precise as possible and try not to waffle.
Basically, I have set up Exchange 2007 SP1 to use the same Autodiscovery FQDN internally as externally as set out in exchange_ginie's blog, in order to get around the certification issues. Internally the Autodicover seems to work well and OWA works internally & externally. However Outlook Anywhere will not work at all internally or externally, it will repeatedly ask for the login credentials and will continue to do so until you are blue in the face.
When I run Test_OutlookWebServices |fl in the Exchange Power Shell, It finds the url and then gives a 401 error for unauterised. I have tried to Disable the Loop Back Check in the registry as discribed by exchange_ginie's blog, however this does not fix the 401 issue, so I am unable to get any further with my trouble shooting.
Please, please, please.... ANY help would be gratly appriciated on this issue
I have posted previously about this but had no replies, so I'll be a precise as possible and try not to waffle.
Basically, I have set up Exchange 2007 SP1 to use the same Autodiscovery FQDN internally as externally as set out in exchange_ginie's blog, in order to get around the certification issues. Internally the Autodicover seems to work well and OWA works internally & externally. However Outlook Anywhere will not work at all internally or externally, it will repeatedly ask for the login credentials and will continue to do so until you are blue in the face.
When I run Test_OutlookWebServices |fl in the Exchange Power Shell, It finds the url and then gives a 401 error for unauterised. I have tried to Disable the Loop Back Check in the registry as discribed by exchange_ginie's blog, however this does not fix the 401 issue, so I am unable to get any further with my trouble shooting.
Please, please, please.... ANY help would be gratly appriciated on this issue
ExchangeWindows Server 2003Microsoft IIS Web Server
Last Comment
gabiosz
ASKER
Wierdly when i execute get-oulookanywhere one of the values returned is OriginatingServer: which states the name of my now decomissioned Exchange 2003 server, is this perhpas relevant?
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Interesting, this is all very odd.... it simply seems to have started working!?!
I have tried so many things that I can't identify what actually fixed it, however I can say for sure that it had something to do with the get-oulookanywhere returning the OriginatingServer: <old server>. It now has the name of the new server and seems to work.
I have tried so many things that I can't identify what actually fixed it, however I can say for sure that it had something to do with the get-oulookanywhere returning the OriginatingServer: <old server>. It now has the name of the new server and seems to work.