Exchange 2010 Autodiscover 600 Error
Contents |
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeOnline20132010Other VersionsLibraryForumsGalleryEHLO Blog Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My autodiscover certificate error exchange 2010 Forums Answered by: Error code 600 and 500 on autodiscover exchange 2010 autodiscover dns in Exchange 2010 Previous Versions of Exchange > Exchange Server 2010 Question 1 Sign exchange 2010 autodiscover not working in to vote Hi, I have a problem on Exchange 2010 Autodiscover, the error code 600 and 500, Please see below message and
Exchange 2010 Autodiscover External Url
please help to fix this error. -
using a browser. But when navigating to the autodiscover URL https://autodiscover.contoso.com/autodiscover/autodiscover.xml you’ll see a 600 Invalid Request error message. When you click exchange 2010 autodiscover certificate name invalid the Show All content button the entire XML package is
Exchange 2010 Autodiscover Test
shown: When you see this message your autodiscover configuration is absolutely fine! The reason you see
Exchange 2010 Autodiscover Internal Url
this message is that the autodiscover service expects an HTTP POST command from Outlook, and not an HTTP GET command from Internet Explorer. So, the service https://social.technet.microsoft.com/Forums/exchange/en-US/da75b301-a9ef-43fa-8990-a4317b446340/error-code-600-and-500-on-autodiscover-in-exchange-2010?forum=exchange2010 is good but the actual request that’s send to the autodiscover service is not good and therefore autodiscover returns the Error 600 Invalid Request message. So this error is good🙂 Share this:TwitterFacebookGoogleLike this:Like Loading... Related AutodiscoverbrowserError 600IEInternet ExplorerInvalid Request Post navigation Previous PostFile Share Witness (FSW) on non-Exchange ServerNext PostExchange /hosting discontinued Leave https://jaapwesselius.com/2011/10/10/error-600-invalid-request/ a Reply Cancel reply Enter your comment here... Please log in using one of these methods to post your comment: Email (required) (Address never made public) Name (required) Website You are commenting using your WordPress.com account. (LogOut/Change) You are commenting using your Twitter account. (LogOut/Change) You are commenting using your Facebook account. (LogOut/Change) You are commenting using your Google+ account. (LogOut/Change) Cancel Connecting to %s Notify me of new comments via email. Notify me of new posts via email. Microsoft UC Specialist Follow @jaapwess Follow me on TwitterMy TweetsArchives August 2016(5) June 2016(7) March 2016(5) February 2016(1) January 2016(1) December 2015(1) November 2015(7) October 2015(4) September 2015(3) August 2015(1) July 2015(5) June 2015(3) May 2015(11) April 2015(4) March 2015(2) February 2015(1) January 2015(2) December 2014(6) November 2014(10) October 2014(2) September 2014(7) August 2014(3) July 2014(5) June 2014(8) May 2014(1) April 2014(7) March 2014(8) February 2014(7) January 2014(1) December 2013(2) November 2013(2) October 2013(2) September 2013(1) August 2013
but it just won't work? You're checking your autodiscover URL http://exchange.contoso.com/autodiscover/autodiscover.xml but all you're seeing it this stupid error message that tells you nothing, except: http://dirty-motherfucker.org/blog/2012/05/09/error-code-600-when-viewing-autodiscover-xml-wtf/ version="1.0" encoding="utf-8" ?>
Followers - Follow 43 Mentions12 Products Neal (Exclaimer) Sales & Marketing Manager GROUP SPONSORED BY EXCLAIMER See more RELATED PROJECTS Exchange Online Migration Migrated Exchange 2007 on premise server to Exchange online Office 365 Deployment Transition all users to office 365 Hosted Email Mass Email Deployment System We needed to build a system from scratch that would be able to send around 1,000,000 opt-in emails per week to very specific groups of people within our customer base. TECHNOLOGY IN THIS DISCUSSION Microsoft 492094 Followers Follow Microsoft Windows Server 2012 Microsoft Exch...osted Services GoDaddy Domain Registrar Join the Community! Creating your account only takes a few minutes. Join Now Here's my setup: Mixed environment transitioning: Exchange 2010 running on Server 2008 in a VMExchange 2013 running on Server 2012 in a VM I have split dns so that autodiscover.domain.com points to my 2013 server internally and my 2010 server externally. When setting up new profiles in outlook internally, autodiscover seems to work fine. However, when I try moving the public autodiscover.domain.com DNS record over to the 2013, pretty much nothing works. I know that the 2013 server is reachable from the outside because mail.domain.com will to go owa and ecp without a problem. I can log in to both without an issue. If I point public DNS back to my 2010 server, then all is well again with outlook anywhere and mobile connectivity. I'm not really sure what needs to be tweaked for the 2013 server to be ready to take over the day to day communications so that I can decommission my 2010 server. Here are the results of the connectivity analyzer: TextThe Microsoft Connectivity Analyzer is attempting to test Autodiscover for me. Testing Autodiscover failed. Additional Details Elapsed Time: 1774 ms. Test Steps