Forum Discussion
BrentStobbs
Sep 12, 2021Copper Contributor
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'...
mohsan466
Oct 14, 2021Copper Contributor
Hello, any update on this issue? I am doing some autodiscover testing for my exchange 2013 server on-prem, and seem to be getting the same issue.
- bradhughOct 14, 2021
Microsoft
mohsan466 - yes, sorry for the delay. We released a new deployment which seems to have resolved the issue. If you are still having problems, send mail using the feedback link in the footer of the site with your specific issue and someone can take a look.
- Andres_PaezApr 19, 2023Copper Contributor
Hola, tengo el mismo error, y estamos utilizando Exchange server 2016 CU21, y sobre los servidores para el balanceo de peticiones tenemos un f5, y nos genera el error mencionado.
- BasL86Oct 14, 2021Copper Contributor
bradhugh Hi Brad, the update seems to have solved our issues. Thank you! Great tool!
- gabrielsixOct 29, 2021Copper Contributor
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.