Hello,
I recently upgraded my environment from Exchange 2010 SP2 to Exchange 2013 SP1 CU5.
My end users are a mix of Office 2010 SP1 and Office 2013 and we have various remote sites that have a local AD/DNS/DHCP server against which the remote clients authenticate, etc.
My issue is that one particular site that has AD/DNS, some clients are unable to connect to Exchange using Outlook. The message they get is "Exchange server unavailable".
When I try to re-create their profile, I am unable to "autodiscover" it. We use Split DNS configuration for Exchange as recommended by MS. I can resolve the server internally to the internal IP (traceroute and ping) from the affected client.
The only way I can get the client Outlook to work is if I manually add "DS Server" in the registry (http://www.msoutlook.info/question/531) and point to the DC that is local to the Exchange server (and not their remote site DC).
My question here is, why can't this client computer detect the GC? I want to fix the issue at the core and not use registry hacks to get Outlook to work.
What should I test for or check? I verified the remote site DC is set as a "GC" in AD Sites and Services so what is the issue?? The remote site is a Windows 2003 R2 server and our domain functionality is 2013.
The site that Exchange is in we have 2 DCs and both are GCs as well.
Thank you.