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
pchettriIT DirectorAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Mohammed HamadaSenior IT ConsultantCommented:
You probably have mistakenly added personal certificates into the root certificate store...

You can check your store if everything is installed properly using Digicert tool

There's another microsoft script that would also list all the none root certificates installed on your Root store but I couldn't find it. I'll bring it up to you  when I get it. meanwhile could you please take a screenshot of your certificate's "Certification Path" tab .. you can get that by simply opening MMC -> Certificates >  Computer Account > Local

In personal store double click on the faulty certificate and navigate to Certification Path.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Delphineous SilverwingGood Ol' GeekCommented:
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.
pchettriIT DirectorAuthor Commented:
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
Your Guide to Achieving IT Business Success

The IT Service Excellence Tool Kit has best practices to keep your clients happy and business booming. Inside, you’ll find everything you need to increase client satisfaction and retention, become more competitive, and increase your overall success.

Mohammed HamadaSenior IT ConsultantCommented:
Could you please run autodiscover check on and check the certificate errors there? please post a screenshot here.
pchettriIT DirectorAuthor Commented:
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
pchettriIT DirectorAuthor Commented:
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?
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.