Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!
Exchange 2013
am seeing following error when I use test-casserverconnectivity
Failure
[System.Net.WebException]:
trust relationship for the SSL/TLS secure channel. Inner error
[System.Security.Authentic
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
Failure
[System.Net.WebException]:
trust relationship for the SSL/TLS secure channel. Inner error
[System.Security.Authentic
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
Do more with
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
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
https://www.digicert.com/util/
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.
You can check your store if everything is installed properly using Digicert tool
https://www.digicert.com/util/
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.
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.
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
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 www.testconnectivity.microsoft.com 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
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 -
http://www.howto-outlook.com/howto/autodiscoverconfiguration.htm
he thinks, there's a missing autodiscover tag in our xml:
this: <Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006"> is missing from our xml: https://mail.company.com/autodiscover/autodiscover.xml.
Is the above article only useful for old versions of exchange?
http://www.howto-outlook.com/howto/autodiscoverconfiguration.htm
he thinks, there's a missing autodiscover tag in our xml:
this: <Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006"> is missing from our xml: https://mail.company.com/autodiscover/autodiscover.xml.
Is the above article only useful for old versions of exchange?
Premium Content
You need an Expert Office subscription to comment.Start Free Trial