Forum Discussion

BrentStobbs's avatar
BrentStobbs
Brass Contributor
Sep 12, 2021

is the Microsoft Remote Connectivity Analyzer broken?

I am having issues configuring my autodiscover configuration after an exchange server rebuild (Single exchange server which failed and had to be rebuilt using the setup.exe /m:recover option) and it'...
Exchange Server
hybrid
BasL86's avatar
BasL86
Copper Contributor

bradhugh Hi Brad, the update seems to have solved our issues. Thank you! Great tool!

gabrielsix's avatar
gabrielsix
Copper Contributor
Oct 29, 2021

bradhugh I can't agree with BasL86 the Remote Connectivity Analyzer shows with Sectico Certificate still the Same result and issue that 

The certificate couldn't be validated because SSL negotiation wasn't successful. This could have occurred as a result of a network error or because of a problem with the certificate installation.
 
  • bradhugh's avatar
    bradhugh
    Icon for Microsoft rankMicrosoft
    Oct 29, 2021
    gabrielsix - Our telemetry has shown a drastic drop of this error after our latest deployment. Can you send me a private message with your URL (assuming it's accessible from the internet)? I can try to see if I can figure out what's going wrong.
    • rrecinos13's avatar
      rrecinos13
      Copper Contributor
      Dec 09, 2021
      Hello, I am having the same issue with a Digicert certificate
    • bradleysp's avatar
      bradleysp
      Copper Contributor
      Sep 24, 2022
      I'm currently seeing this with a Network Solutions cert. Qualys gives the server an A rating, Can I PM you the URL?
      • bradhugh's avatar
        bradhugh
        Icon for Microsoft rankMicrosoft
        Oct 06, 2022
        bradleysp - sure, PM me the URL I can try to see what's up. We know one scenario is that certain firewalls block TLS scanners and these catch ours where they may not catch the Qualys scanner. Otherwise, this is fixed for the vast majority of folks.
    • thehagman's avatar
      thehagman
      Copper Contributor
      Sep 27, 2022
      This is still an issue for me. Since the error message suggests that the cert could not be obtained (as opposed to: could not be validated), the issuing CA should be irrelevant, but as others mentioned theirs: We are using LetsEncrypt certs. The server is also behind a reverse proxy, but that should not play a role either until a specific URL is requested (hence *after* TLS negotiation)

Resources