Link to home
Start Free TrialLog in
Avatar of pchettri

asked on

Exchange 2013

am seeing following error when I use test-casserverconnectivity. Some of my iphone 6 pus user keep losing connection.

[System.Net.WebException]: The underlying connection was closed: Could not establish
trust relationship for the SSL/TLS secure channel. Inner error
[System.Security.Authentication.AuthenticationException]: The remote certificate is
invalid according to the validation procedure.

I was able to reconnect them by removing user based device from ADsiedit but now it is not working either.

Also, I have connection error when I tried connecting from Outlook 2016. Email is working on Outlook 2013 and 2011 (mac).

Android users and old Iphone users are able to connect to email
Avatar of Mohammed Hamada
Mohammed Hamada
Flag of Portugal image

Link to home
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Is the certificate issuer in the Trusted Root CA of the server? As issuers, such as Verisign, update their own certificates the server (and clients) need to update the trusted root CA. If the entire certificate chain is not available, validation errors can occur.
Avatar of pchettri


I have digicer sha2 applied in active DAG server and I have checked the report on ECP and ran test and get powershell command to get details on owavD, webvd, activesync etc. Health report for database and replication is correct. Somehow outlook setup with autodiscovery seemed to pointing to passive DAG server under proxy settings of Outlook 2013 configuration.
I need to find out why is goes the passive though database health, cluster and replication all seem to be correct
One digicert I did get Do not trust fiddler room on root certificate. Intermediate and personal seem to be fine
Could you please run autodiscover check on and check the certificate errors there? please post a screenshot here.
I dont have certificate error on autodiscovery. Since my passive DAG server does have full role, looks the outlook eventually resolves the certified name to DAG passive server instead of active, but it is only using it as proxy and it would continue to work when passive server is shut down for update.
when I ran auto discovery instead of manual setup the auto discovery is resolving correctly
My auto discovery test passes on analyzer and outlook connection test. One of my web admin has found this article and he thinks there is still something wrong as -

he thinks, there's a missing autodiscover tag in our xml:

this: <Autodiscover xmlns=""> is missing from our xml:

Is the above article only useful for old versions of exchange?