Haven't made any DNS changes related to Exchange. We are using a split-DNS and no changes at all on the particular domain used by Exchange.
No changes to DFL/FFL in about a year. No changes to GC or sites. All Exchange servers are in the same site and all DC's are GCs. The only thing that has been done recently that seems like it could possibly be related is adjusting the proxy exceptions list. Basically, we have a proxy server and have to add an exception to tell the browsers not to use the proxy when connecting to the CAS array. Thought maybe I had a typo or something causing a problem, but I have checked and see no traffic destined for Exchange hitting the proxy servers. Additionally, connecting the XML URL in IE does seem to work as expected, which suggests that is not an issue. From: [email protected] [mailto:[email protected]] On Behalf Of Michael B. Smith Sent: Tuesday, April 04, 2017 1:30 PM To: [email protected] Subject: [Exchange] RE: Shared Calendar/Autodiscover problem Have you made any recent internal vs. external DNS changes? DFL/FFL changes? GC changes in the AD-site where your Exchange servers are placed? From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Mayo, Bill Sent: Tuesday, April 4, 2017 1:01 PM To: [email protected]<mailto:[email protected]> Subject: [Exchange] RE: Shared Calendar/Autodiscover problem For both a failing user and successful user, exrca.com indicates a successful test. FWIW, here is some additional information from troubleshooting since I initially sent the message. 1) I downloaded and ran "autodiscovertest.exe"; I don't see any error messages there on the same computer/user for which I get a failure for Outlook. 2) I turned on Outlook logging and in addition to the "0x80072ef3" error, I note the additional message preceding that error is "GetLastError=12175; httpStatus=0." 3) Logging on with different accounts and onto different computers, it does not appear to be specifically following a user or computer. An account without the problem logged onto a different computer and had the problem there. An affected account logged onto the computer where the unaffected user did not have a problem, and still had the problem there. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Michael B. Smith Sent: Tuesday, April 04, 2017 12:06 PM To: [email protected]<mailto:[email protected]> Subject: [Exchange] RE: Shared Calendar/Autodiscover problem I've not (yet, anyway) heard of a growing problem with the recent updates. What does exrca.com say for both a failing user and a successful user? From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Mayo, Bill Sent: Tuesday, April 4, 2017 11:00 AM To: [email protected]<mailto:[email protected]> Subject: [Exchange] Shared Calendar/Autodiscover problem This morning we started getting calls about people unable to view information on shared calendars with a message of "no connection". Tested via OWA and the information is accessible. Did a lot of googling and found suggestions that it was tied to autodiscover. Tested autodiscover on a computer with the problem and it fails with an error 0x80072ef3. However, we have at least one computer where there is no problem with the calendars and autodiscover is working. I did a "Test-OutlookWebServices" on both CAS servers and that seems to be reporting OK. The only thing that I know of that is different with the computer that doesn't have a problem is that it hasn't had the same updates applied as a computer with the problem (it hasn't applied the last cycle). We also just received a report about a problem setting out of office, which I think also ties into autodiscover. We are on Exchange 2010 and Outlook 2010. Two CAS servers in an NLB, and they have both been rebooted. Any help or pointers would be appreciated. Bill Mayo
