I have a possible issue, when connecting to the autodiscover URL through IE, I get an error 600 invalid request <? xml version="1.0" encoding="utf-8" ?> - < Autodiscover xmlns =" http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006 " > - < Response > - < Error Time =" 10:24:50.3269845 " Id =" 656902405 " > < ErrorCode > 600 </ ErrorCode > < Message > Invalid Request </ Message > < DebugData /> </ Error > </ Response > </ Autodiscover > However, running test-outlookwebservices works fine, and "test email autoconfiguration" works fine inside of Outlook. Is this normal? Environment is Exchange 2007 SP1, UR9 running on Server 2003 SP2, Outlook 2007 SP2. This is the output from Outlook test email autoconfiguration: <?xml version="1.0" encoding="utf-8"?> <Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006"> <Response xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a"> <User> <DisplayName>lastname, firstname</DisplayName> <LegacyDN>/o=mydomain/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=myname</LegacyDN> <DeploymentId>3899692f-23d1-4b06-9380-03545f1b42a7</DeploymentId> </User> <Account> <AccountType>email</AccountType> <Action>settings</Action> <Protocol> <Type>EXCH</Type> <Server>CMBS2CC.mydomain.int</Server> <ServerDN>/o=mydomain/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=CMBS2CC</ServerDN> <ServerVersion>720180F0</ServerVersion> <MdbDN>/o=mydomain/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=CMBS2CC/cn=Microsoft Private MDB</MdbDN> <PublicFolderServer>CMBS1CC.mydomain.int</PublicFolderServer> <AD>datacenter-DC2.mydomain.int</AD> <ASUrl>https://autodiscover.mydomain.com/ews/exchange.asmx</ASUrl> <EwsUrl>https://autodiscover.mydomain.com/ews/exchange.asmx</EwsUrl> <OOFUrl>https://autodiscover.mydomain.com/ews/exchange.asmx</OOFUrl> <UMUrl>https://datacenter-cas1.mydomain.int/UnifiedMessaging/Service.asmx</UMUrl> <OABUrl>http://cas.mydomain.int/OAB/01334fe7-b431-4901-a937-df466f9f3389/</OABUrl> </Protocol> <Protocol> <Type>EXPR</Type> <Server>autodiscover.mydomain.com</Server> <SSL>On</SSL> <AuthPackage>Basic</AuthPackage> <ASUrl>https://autodiscover.mydomain.com/ews/exchange.asmx</ASUrl> <EwsUrl>https://autodiscover.mydomain.com/ews/exchange.asmx</EwsUrl> <OOFUrl>https://autodiscover.mydomain.com/ews/exchange.asmx</OOFUrl> </Protocol> <Protocol> <Type>WEB</Type> <Internal> <OWAUrl AuthenticationMethod="Basic, Fba">https://datacenter-cas1.mydomain.int/owa</OWAUrl> <OWAUrl AuthenticationMethod="Basic, Fba">https://datacenter-cas2.mydomain.int/owa</OWAUrl> <Protocol> <Type>EXCH</Type> <ASUrl>https://autodiscover.mydomain.com/ews/exchange.asmx</ASUrl> </Protocol> </Internal> </Protocol> </Account> </Response> </Autodiscover>

Autodiscover isn't expecting Internet Explorer to connect, it is expecting Outlook. Therefore things shouldn't be expected to work as you might expect. If autodiscover is working correctly through the tools available in Exchange and Outlook, then I wouldn't worry about it. Simon.Simon Butler, Exchange MVP. http://blog.sembee.co.uk , http://exbpa.com/

You can test your autodiscover function from external by using <cite>https://www.testexchangeconnectivity .com</cite> Jonas Andersson MCTS: Microsoft Exchange Server 2007/2010 | MCITP: EMA 2007/2010 | MCSE/MCSA Blog: http://www.testlabs.se/blog

You can test your autodiscover function from external by using <cite>https://www.testexchangeconnectivity .com</cite> Jonas Andersson MCTS: Microsoft Exchange Server 2007/2010 | MCITP: EMA 2007/2010 | MCSE/MCSA Blog: http://www.testlabs.se/blog Yes, I am aware of that site, it was down or not working yesterday before I posted this. I have checked autodiscover through IE before, I just did not remember it giving back this response, I knew it was some xml page, but the 600 kind of gave me pause. Everything is working ok on our side except a cross-forest free/busy lookup on a partner's side, which is when I ran across this troubleshooting it.

Hi, That's the normal behaviour. This indicates the Autodiscover service is running well when receiving the 600 error code after accessing the autodiscover url. Thanks Allen