Active Sync not Working - Exchange 2013 with Exchange 2007

Question

Hi
Recently we introduced Exchange 2013 servers to our existing Exchange 2007 organization. The servers are just configured with default self-signed certificate and URLs are pointing to server FQDNs.
Everything is at default as far as configuration is concerned in Exchange 2013.
After just introducing the Exchange 2013 CAS servers was checking the ActiveSync functionality using a new mailbox created on Exchange 2013. We have not yet published our Exchange 2013 servers to
Internet (before even doing that, want to ensure ActiveSync is working). We're connecting using our Private network and trying to make a connection to CAS FQDN. Checked a iOS7 (iPad) and a Windows Phone device, both of them configure successfully (with the
certificate warning, which is obvious) but when it comes to synchronizing the contents they fail saying "Cannot Get Mail. Connection to Server Failed"
Checked the IIS Logs on CAS server and found that the device makes a successful connection - as is indicated by successful configuration but thereafter nothing happnes on the device and no error
logged in Event Viewer as well. Could it be that the mailbox server is denying the connection....how to check. How to go ahead with the troubleshooting.
Everything else expect ActiveSync is working perfectly. Tries accessing the ActiveSync VD using the link
HTTPS://Server_FQDN/Microsoft-Server-ActiveSync, this pops-up a window asking for credentials – which is normal behavior indicating ActiveSync virtual directory is good.
Thanks
Taranjeet Singh
zamn

Answer 1

Hey Guys
Just to update here my initial testing revieled that if I run Test-ActiveSyncConnectivity by not specifying the -URL parameter like this:
Test-ActiveSyncConnectivity -MailboxCredential (get-credential User1) |FL
 the command fails for an obvious reason as shown in the result. The command is getting the mailbox server name in the ActiveSync URL returned automatically:
ClientAccessServer         
: SITE-MBX-02.ABC.COM
Scenario                   
: Options
ScenarioDescription        
: Issue an HTTP OPTIONS command to retrieve the Exchange ActiveSync protocol version.
PerformanceCounterName     
: DirectPush Latency
Result                     
: Failure
Error                      
: The OPTIONS command returned HTTP 200, but the Exchange ActiveSync header
                           (MS-Server-ActiveSync) wasn't returned. The request likely did not reach a
Client Access
server, either because
- A proxy server intervened (check the headers below for any that may have been
returned by a proxy)
-The virtual directory could not be reached:
https://SITE-MBX-02.ABC.COM/Microsoft-Server-ActiveSync
                     - The virtual directory does not point to a Client Access server:
https://SITE-MBX-02.ABC.COM/Microsoft-Server-ActiveSync
If however, I manually provide the -URL parameter value with FQDN of CAS server:
Test-ActiveSyncConnectivity -URL
https://SITE-CAS-02.ABC.COM/Microsoft-Server-ActiveSync
-MailboxCredential (get-credential User1) |FL
it succeeds.
We have our CAS and Mailbox servers installed on separate systems - no colocation.
This is strange and makes me curious to find out, where does the command without -URL parameter is getting the ActiveSync URL that has mailbox server in it. I checked that the new Exchange 2013 CAS servers have InternalURL parameteres populated with their
own FQDNs and the ExternalURL is empty for now.
Need help in drilling down this further.
Thanks
Taranjeet Singh 
zamn