Believe it or not this issue came down to a diskeeper issue. After calling MS and doing a bunch of troubleshooting, we uninstalled diskeeper and the synching immediately started working.
Just wanted to follow up and let everyone know. Thanks Scott From: Alexander Rose [mailto:arose...@gmail.com] Sent: Friday, April 12, 2013 2:34 AM To: MS-Exchange Admin Issues Subject: Re: Activesync/cert issue The error you are getting is confusing but normal as Exrca will always try to hit autodiscover on your default domain name (ex if you administer acme.com) the test will run against acme.com (will fail) and then try autodiscover.acme.com You should see later in your test an attempt on autodiscover.thanksal.com <http://www.thanksal.com> As for the cert have you re-enrolled and copied the certificate to the device? On Fri, Apr 12, 2013 at 5:15 AM, Scott Weber <swe...@thanksal.com> wrote: I'm just going to throw this out there since its late and some maybe reading this. I have an exchange 2003 server running our own cert server on it for self signing certs for owa. After a reboot today we started having all sorts of weird active sync issues. Mainly geared toward iPhones and iPad. But they will not sync at all. I noticed the cert expired some time so in an attempt to re-do quickly since some higher ups were lost without their email, I attempted to re-self sign a cert to correct this issue. Now If I try to add a new account to an ipad , it just fails and will not sync at all. Is there anyway to completely remove the CA and all the certs to this point and basically just start over? And now when I run the exchange connectivity.com test I get the following: Testing the SSL certificate to make sure it's valid. The SSL certificate failed one or more certificate validation checks. Test Steps ExRCA is attempting to obtain the SSL certificate from remote server thanksal.com on port 443. ExRCA successfully obtained the remote SSL certificate. Additional Details Remote Certificate Subject: CN=www.thanksal.com, OU="Al Boenker Insurance Agency, Inc.", O="Al Boenker Insurance Agency, Inc.", L=Fort Worth, S=Texas, C=US, Issuer: CN=VeriSign Class 3 Secure Server CA - G3, OU=Terms of use at https://www.verisign.com/rpa (c)10, OU=VeriSign Trust Network, O="VeriSign, Inc.", C=US. Validating the certificate name. Certificate name validation failed. Tell me more about this issue and how to resolve it Additional Details Host name thanksal.com doesn't match any name found on the server certificate CN=www.thanksal.com, OU="Al Boenker Insurance Agency, Inc.", O="Al Boenker Insurance Agency, Inc.", L=Fort Worth, S=Texas, C=US. But now its trying to autodiscover against our real certificate on our webserver which has nothing to do with our exchange server. Almost as if the local cert server root cert is bad or something. I don't know.. I have been searching Google high and low but, just not sure what to check out next.. Thanks for your time reading this, if you have any ideas, I would love to hear them. Thanks Scott Scott Weber || IT Systems Administrator Boenker Group of Companies swe...@thanksal.com p.817.306.2565 c.817.584.2245 --- To manage subscriptions click here: or send an email to with the body: unsubscribe exchangelist --- To manage subscriptions click here: or send an email to with the body: unsubscribe exchangelist --- To manage subscriptions click here: or send an email to with the body: unsubscribe exchangelist
