Activesync SBS 2011 - Can't connect Android

This is a new server setup. I have run internet and email wizards.

I believe the certificate name is CN=remote.legaltnt.com
however the URL that you are connecting is mail.legaltnt.com for the mail server, correct me if wrong. Also does the certificate have a Subject alternative name of Mail.legaltnt.com ?
what happens if you run the test on testexchangeconnectivity and check the ignore trust SSL check box ?

the prior server was set to mail.legaltnt.com this sbssetup wizzard created the remote.legaltnt.com.

the go daddy had an a record for mail.legaltnt.com

when the certificate was provisioned, sbs used the remote.legaltnt.com
 and I figured it was better to let the wizzrd stand.  I added an  A record for remote tot he DNS

Go daddy has a cname set to autodiscover points to mail.legaltnt.com, I was afraid to change that becuse i dont want to mess up mail flow...

It looks like go daddy has aN SRV setup.

So tell me if I am on:

1 Delete autodiscover entry
2 Add SRV entry

Do I keep the A record for Mail. or rmeote. or both???
Do I need to rerun any wizards?

Do as the article I linked above tells you... delete the autodiscover record and create the SRV one instead.

You will not need the A record for mail.legaltnt.com unless you have some other thing which is configured to use that host name.  There is no harm in keeping it.

You definitely want to keep the A record for remote.legaltnt.com

Once this is complete you should not need to rerun any wizards, however if things still aren't working correctly you can always run the FixMyNetwork wizard.

Jeff
TechSoEasy

I run it through tonite and go from there!!  Thank you!

I made the changes and ran the test again, it said it was successfull, but When I expanded the test results, there were failded sections. I have attached a print screen for the DNS info and the test results.

But the over all autodiscover test said it was successfull...

But there are two different IP addresses in defferent sections of the test...

Would you please take a look?
DNS-info.docx

BTW, I was able to connect another android this morning and the iPhones that were connected previously (before server change) were able to connect once I changed the domian and turned off SSL...

I could no add a new account to an iPhone that had not been previously connected to old server.

Androis seems functional, iPhones are intermittanly getting send errors... some emails go thru and some get stuck.

I made the changes last night.

Trying to add an iphone, cannot connect to server using remote.legaltnt.com

But can connect using mail.legaltnt.com, but cannot send out email.

Something is still amiss....

Any ideas?  I posted some printout from last night's changes.

Androids can send and receive...  setup using remote.legaltnt.com

I reran the analizer and now its failing:

ExRCA is testing Exchange ActiveSync.
 The Exchange ActiveSync test failed.
 Test Steps
 Attempting the Autodiscover and Exchange ActiveSync test (if requested).
 Testing of Autodiscover for Exchange ActiveSync failed.
 Test Steps
 Attempting each method of contacting the Autodiscover service.
 The Autodiscover service couldn't be contacted successfully by any method.
 Test Steps
 Attempting to test potential Autodiscover URL https://legaltnt.com/AutoDiscover/AutoDiscover.xml
 Testing of this potential Autodiscover URL failed.
 Test Steps
 Attempting to resolve the host name legaltnt.com in DNS.
 The host name resolved successfully.
 Additional Details
 IP addresses returned: 64.202.189.170

Testing TCP port 443 on host legaltnt.com to ensure it's listening and open.
 The specified port is either blocked, not listening, or not producing the expected response.
  Tell me more about this issue and how to resolve it
 Additional Details
 A network error occurred while communicating with the remote host.




Attempting to test potential Autodiscover URL https://autodiscover.legaltnt.com/AutoDiscover/AutoDiscover.xml
 Testing of this potential Autodiscover URL failed.
 Test Steps
 Attempting to resolve the host name autodiscover.legaltnt.com in DNS.
 The host name couldn't be resolved.
  Tell me more about this issue and how to resolve it
 Additional Details
 Host autodiscover.legaltnt.com couldn't be resolved in DNS InfoDomainNonexistent.



Attempting to contact the Autodiscover service using the HTTP redirect method.
 The attempt to contact Autodiscover using the HTTP Redirect method failed.
 Test Steps
 Attempting to resolve the host name autodiscover.legaltnt.com in DNS.
 The host name couldn't be resolved.
  Tell me more about this issue and how to resolve it
 Additional Details
 Host autodiscover.legaltnt.com couldn't be resolved in DNS InfoDomainNonexistent.



Attempting to contact the Autodiscover service using the DNS SRV redirect method.
 ExRCA failed to contact the Autodiscover service using the DNS SRV redirect method.
 Test Steps
 Attempting to locate SRV record _autodiscover._tcp.legaltnt.com in DNS.
 The Autodiscover SRV record was successfully retrieved from DNS.
 Additional Details
 The Service Location (SRV) record lookup returned host remote.legaltnt.com.

Attempting to test potential Autodiscover URL https://remote.legaltnt.com/Autodiscover/Autodiscover.xml
 Testing of this potential Autodiscover URL failed.
 Test Steps
 Attempting to resolve the host name remote.legaltnt.com in DNS.
 The host name resolved successfully.
 Additional Details
 IP addresses returned: 67.138.0.75

Testing TCP port 443 on host remote.legaltnt.com to ensure it's listening and open.
 The port was opened successfully.
Testing the SSL certificate to make sure it's valid.
 The certificate passed all validation requirements.
 Test Steps
 ExRCA is attempting to obtain the SSL certificate from remote server remote.legaltnt.com on port 443.
 ExRCA successfully obtained the remote SSL certificate.
 Additional Details
 Remote Certificate Subject: CN=remote.legaltnt.com, OU=Domain Control Validated, O=remote.legaltnt.com, Issuer: SERIALNUMBER=07969287, CN=Go Daddy Secure Certification Authority, OU=http://certificates.godaddy.com/repository, O="GoDaddy.com, Inc.", L=Scottsdale, S=Arizona, C=US.

Validating the certificate name.
 The certificate name was validated successfully.
 Additional Details
 Host name remote.legaltnt.com was found in the Certificate Subject Common name.

Certificate trust is being validated.
 The certificate is trusted and all certificates are present in the chain.
 Test Steps
 ExRCA is attempting to build certificate chains for certificate CN=remote.legaltnt.com, OU=Domain Control Validated, O=remote.legaltnt.com.
 One or more certificate chains were constructed successfully.
 Additional Details
 A total of 1 chains were built. The highest quality chain ends in root certificate OU=Go Daddy Class 2 Certification Authority, O="The Go Daddy Group, Inc.", C=US.

Analyzing the certificate chains for compatibility problems with versions of Windows.
 Potential compatibility problems were identified with some versions of Windows.
 Additional Details
 ExRCA can only validate the certificate chain using the Root Certificate Update functionality from Windows Update. Your certificate may not be trusted on Windows if the "Update Root Certificates" feature isn't enabled.



Testing the certificate date to confirm the certificate is valid.
 Date validation passed. The certificate hasn't expired.
 Additional Details
 The certificate is valid. NotBefore = 8/13/2012 5:01:31 AM, NotAfter = 8/13/2013 5:01:31 AM



Checking the IIS configuration for client certificate authentication.
 Client certificate authentication wasn't detected.
 Additional Details
 Accept/Require Client Certificates isn't configured.

Attempting to send an Autodiscover POST request to potential Autodiscover URLs.
 Autodiscover settings weren't obtained when the Autodiscover POST request was sent.
 Test Steps
 ExRCA is attempting to retrieve an XML Autodiscover response from URL https://remote.legaltnt.com/Autodiscover/Autodiscover.xml for user pault@legaltnt.com.
 ExRCA failed to obtain an Autodiscover XML response.
 Additional Details
 None of the expected XML elements were found in the XML response.

If I set server (remote.) manuall it passes with warnings:

 Validating certificate trust for Windows Mobile devices.
  The certificate is trusted and all certificates are present in the chain.
   Test Steps
   ExRCA is attempting to build certificate chains for certificate CN=remote.legaltnt.com, OU=Domain Control Validated, O=remote.legaltnt.com.
  One or more certificate chains were constructed successfully.
   Additional Details
  A total of 1 chains were built. The highest quality chain ends in root certificate OU=Go Daddy Class 2 Certification Authority, O="The Go Daddy Group, Inc.", C=US.
 
 Analyzing the certificate chains for compatibility problems with Windows Phone devices.
  Potential compatibility problems were identified with some versions of Windows Phone.
   Tell me more about this issue and how to resolve it
   Additional Details
  The certificate is only trusted on Windows Mobile 6.0 and later versions. Devices running Windows Mobile 5.0 and 5.0 with the Messaging and Security Feature Pack won't be able to sync. Root = OU=Go Daddy Class 2 Certification Authority, O="The Go Daddy Group, Inc.", C=US.

So it all seems fine.

Everything working as expected?

Jeff
TechSoEasy

Finnally...   they are hooked up and sending...

Awesome help! Thank you.