Hi @BP-7667
Great to know that the issue has already been resolved and thanks for sharing the solution so that others experiencing the same thing can easily reference this! Since the Microsoft Q&A community has a policy that "[The question author cannot accept their own answer. They can only accept answers by others]", I'll repost your solution in case you'd like to "[Accept]" the answer : )
--------------
Issue Symptom:
- Attempting to configure an outlook 2016 client could not connect to the exchange 2016 server.
- DNS is correct for both internal and external access. Pings from internal and external return the proper ip addresses.
- When attempting to browse to the autodiscovery.xml via a browser, it comes up with a http 500 error.
- When running the Microsoft Remote Connectivity Analyzer It fails at the autodiscover POST with an http 404 and 500 "The Microsoft Connectivity Analyzer failed to obtain an Autodiscover XML response".
- Internally running the Test E-Mail AutoConfiguration from Outlook, getting that the Autodiscover is found through SCP then continuously fails with 500 and 404 errors. The failed erros are 0x800C820f, 0x80070057, and 0x8004010f (SRV Record Check).
- Adding the exchange server to the Hosts file on the internal client computer did not resolve the issue.
- DNS on the internal network is correct.
- Everyone that is currently connected to exchange is not having an issue. Anyone attempting to connect to exchange cannot connect due to the autodiscover issue.
Resolution:
Enable Failed Requet Tracing Rules and configured a rule for error 500 on the autodiscover vdir.(This can give more detailed information )
In this case:
This pointed directly to a URL Rewrite rule.Removing the rule on the Default Website allowed EEMS to apply the rule to the autodiscover vdir, and autrodiscover started accepting requests.