Hi - I'm working with a client who has two Exchange 2010 servers (Servers A and B), both running MB, CAS, HT. Their Server B was having issues with AutoDiscover. Running the command "test-outlookwebservices" on Server A was fine. Running the same command on ServerB generated many errors including: When contacting https://cas.mydomain.com/autodiscover/Autodiscover.xml received the error A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 10.125.39.25:443. This IP is their WebMux, which load balances between Server A and B. A look at their DNS records shows entries for CAS.mydomain.com and Autodiscover.mydomain.com pointing to the WebMux at 10.125.39.25. If I edit the Hosts file on Server B to point CAS and Autodiscover to its own IP address, "test-outlookwebservices" runs fine. If I clear the hosts file, add another DNS A record for cas pointing to the IP of Server B, and register DNS then the "test-outlookwebservices" also runs fine without error. What am I missing here? What the right way for DNS to be configured for AutoDiscover to work on Server B, like it does for Server A?

Here's another discovery, I am unable to browse to the EWS directory on Server B using the common URL https://cas.mydomain.com/EWS/Exchange.asmx and receive a "page cannot be displayed" message. On Server A I can browse to this URL successfully. On Server B I can also browse to the URL https://ServerB.mydomain.com/EWS/Exchange.asmx successfully.

Hello, Since everything works well when you didn't test through webMux, I suggest you go to check the configuration on webMux, make sure it can proxy your request to serverB well. Thanks, Evan Liu TechNet Subscriber Support in forum If you have any feedback on our support, please contact tnmff@microsoft.com Evan Liu TechNet Community Support

Everything isn't well. Server B cannot resolve the URL https://cas.mydomain.com/EWS/Exchange.asmx. Server A can. Server B is able to bring up the URL if I call it using its own name https://ServerB.mydomain.com/EWS/Exchange.asmx Thanks

Seems you always do testing from server but not client. It may not be necessarily a problem. Suggest to test it from a client and if you hit a problem, start troubleshooting from there.