We went through an upgrade from Exchange 2003 to Exchange 2007 and we are now having problems with Autodiscover as it pertains to RPC over HTTP. The previous server name was mail.domain.com and the new server is mail2.domain.com. Autodiscover works perfectly fine internally, but always fails externally. Autodiscover posts mail.domain.com as the HTTP server, so each time a machine is connected to the network it receives the faulty info from Autodiscover and once the machine is taken outside the network Outlook will fail to connect since HTTP is no longer on mail.domain.com it is on mail2.domain.com. Outlook Anywhere works fine if manually configured until it's plugged back into the network. It's a simple fix on the client side (add a '2' on the Exchange HTTPS server in Outlook settings), and some of my users are savvy enough now to fix this on their own but anyone know how I can fix Autodiscover? Happy to post logs if necessary Thanks,

Do you have an srv record for autodiscover and have you changed it mail2.domain.com? What does the test-exchanegconnectivity tool shows when you do an autodiscover test

I meant the Exchange remote connectivity analyzer tool https://www.testexchangeconnectivity.com/

<form id="form1" action="https://www.testexchangeconnectivity.com/Default.aspx#&&/wEXAQUBcwUBM6hsZ7Mm/gYiLf3f68Q6JkwLY9BI" method="post"> <script type="text/javascript">// <![CDATA[ //<![CDATA[ var theForm = document.forms['form1']; if (!theForm) { theForm = document.form1; } function __doPostBack(eventTarget, eventArgument) { if (!theForm.onsubmit || (theForm.onsubmit() != false)) { theForm.__EVENTTARGET.value = eventTarget; theForm.__EVENTARGUMENT.value = eventArgument; theForm.submit(); } } // ]]></script> <script type="text/javascript">// <![CDATA[ //<![CDATA[ Sys.WebForms.PageRequestManager._initialize('scriptManager', document.getElementById('form1')); Sys.WebForms.PageRequestManager.getInstance()._updateControls(['tupdPanel'], ['scriptManager'], [], 90); // ]]></script> <input id="scriptManager" name="scriptManager" type="hidden" value="/wEXAQUBcwUBM6hsZ7Mm/gYiLf3f68Q6JkwLY9BI" /> <input id="exrcalogo" style="border-width: 0px;" name="exrcalogo" src="https://www.testexchangeconnectivity.com/Images/ExRCA.png" type="image" /> Connectivity Test Failed Test Details <input class="btn" onclick="return false;WebForm_DoPostBackWithOptions(new WebForm_PostBackOptions("testSelectWizard$ctl12$btnExpandAll$ctl01", "", true, "", "", false, true))" name="testSelectWizard$ctl12$btnExpandAll$ctl01" type="button" value="Expand All" /><input class="btn btnWithLeftBorder" onclick="return false;WebForm_DoPostBackWithOptions(new WebForm_PostBackOptions("testSelectWizard$ctl12$btnCopyClipboard$ctl01", "", true, "", "", false, true))" name="testSelectWizard$ctl12$btnCopyClipboard$ctl01" type="button" value="Copy" /> ExRCA is attempting to test Autodiscover for xxxxx.xxxxx@domain.com. Testing Autodiscover failed. Test Steps Attempting each method of contacting the Autodiscover service. The Autodiscover service couldn't be contacted successfully by any method. Test Steps Attempting to test potential Autodiscover URL https://domain.com/AutoDiscover/AutoDiscover.xml Testing of this potential Autodiscover URL failed. Test Steps Attempting to resolve the host name domain.com in DNS. The host name resolved successfully. Additional Details IP addresses returned: 64.29.151.221 Testing TCP port 443 on host domain.com to ensure it's listening and open. The specified port is either blocked, not listening, or not producing the expected response. <label for="testSelectWizard_ctl12_ctl06_ctl00_ctl00_ctl01_tmmArrow">Tell me more about this issue and how to resolve it</label> Additional Details A network error occurred while communicating with the remote host. Exception details: Message: No connection could be made because the target machine actively refused it 64.29.151.221:443 Type: System.Net.Sockets.SocketException Stack trace: at System.Net.Sockets.TcpClient.Connect(String hostname, Int32 port) at Microsoft.Exchange.Tools.ExRca.Tests.TcpPortTest.PerformTestReally() Attempting to test potential Autodiscover URL https://autodiscover.domain.com/AutoDiscover/AutoDiscover.xml Testing of this potential Autodiscover URL failed. Test Steps Attempting to resolve the host name autodiscover.domain.com in DNS. The host name resolved successfully. Additional Details IP addresses returned: 64.29.151.221 Testing TCP port 443 on host autodiscover.domain.com to ensure it's listening and open. The specified port is either blocked, not listening, or not producing the expected response. <label for="testSelectWizard_ctl12_ctl06_ctl00_ctl01_ctl01_tmmArrow">Tell me more about this issue and how to resolve it</label> Additional Details A network error occurred while communicating with the remote host. Exception details: Message: No connection could be made because the target machine actively refused it 64.29.151.221:443 Type: System.Net.Sockets.SocketException Stack trace: at System.Net.Sockets.TcpClient.Connect(String hostname, Int32 port) at Microsoft.Exchange.Tools.ExRca.Tests.TcpPortTest.PerformTestReally() Attempting to contact the Autodiscover service using the HTTP redirect method. The attempt to contact Autodiscover using the HTTP Redirect method failed. Test Steps Attempting to resolve the host name autodiscover.domain.com in DNS. The host name resolved successfully. Additional Details IP addresses returned: 64.29.151.221 Testing TCP port 80 on host autodiscover.domain.com to ensure it's listening and open. The port was opened successfully. ExRCA is checking the host autodiscover.domain.com for an HTTP redirect to the Autodiscover service. ExRCA failed to get an HTTP redirect response for Autodiscover. Additional Details A Web exception occurred because an HTTP 404 - NotFound response was received from Unknown. Attempting to contact the Autodiscover service using the DNS SRV redirect method. ExRCA failed to contact the Autodiscover service using the DNS SRV redirect method. Test Steps Attempting to locate SRV record _autodiscover._tcp.domain.com in DNS. The Autodiscover SRV record wasn't found in DNS. <label for="testSelectWizard_ctl12_ctl06_ctl00_ctl03_ctl00_tmmArrow">Tell me more about this issue and how to resolve it</label> <input class="btn" onclick="javascript:WebForm_DoPostBackWithOptions(new WebForm_PostBackOptions("testSelectWizard$__CustomNav3$buttonStartOver$ctl01", "", true, "", "", false, false))" name="testSelectWizard$__CustomNav3$buttonStartOver$ctl01" type="submit" value="Start Over" /> <input class="btn btnWithLeftBorder" onclick="javascript:WebForm_DoPostBackWithOptions(new WebForm_PostBackOptions("testSelectWizard$__CustomNav3$buttonRunAgain$ctl01", "", true, "", "", false, false))" name="testSelectWizard$__CustomNav3$buttonRunAgain$ctl01" type="submit" value="Run Test Again" />

I dont believe we have an SRV record for autodiscover...at least I have never found one in DNS. The upgrade was performed several months before I started and the guy who performed it is nowhere to be found....

Internal cients find autodiscover via Active directory SCP object. Clients that are not connecting via LAN or VPN would connect via autodiscover srv record.

Also, in the EMC under CAS in Server Config it still had mail.domain.com and I changed it to mail2.domain.com manually. I also updated the ActiveSync external URL since it was blank. The internal URL had the correct setting.

Do you have an srv record for autodiscover and have you changed it mail2.domain.com? What does the test-exchanegconnectivity tool shows when you do an autodiscover test

I meant the Exchange remote connectivity analyzer tool https://www.testexchangeconnectivity.com/

Internal cients find autodiscover via Active directory SCP object. Clients that are not connecting via LAN or VPN would connect via autodiscover srv record.

The Outlook anywhere client outside of your company uses the DNS to resolve the autodiscover services. It uses a pre-defined autodiscover url which is depended on your smtp email suffix. For example, if a user’s email address is user@microsoft.com, Outlook will try to resolve the autodiscover url like: https://microsoft.com/autodiscover/autodiscover.xml https://autodiscover.microsoft.com/autodiscover/autodiscover.xml You must have created a public record for the autodiscover.domian.com and point it to the Exchange 2003 FE which is now not available so that the autodiscover fail to be resolved. Contact the ISP to change the autodiscover.domian.com to your current Internet facing server. Thanks, Simon