ActiveSync testing for Exchange 2010 not working
I downloaded Windows Mobile 6 SDK to try to test ActiveSynch for my new Exchange Server 2010 that was recently installed.
I have tried to set up the emulator to connect through the Settings, Network Cards, NE2000 Compatible Ethernet Driver and configured it with an IP address.
I then went to ActiveSync and tried to set it up to point to a mailbox on my Exchange Server 2010 box. It keeps failing. ActiveSync was setup on the Client Access for this server and I even turned off the SSL cert in the IIS but that didn't help. I have allowed non-provisioned devices to work with this, am not requiring a password, Allowing all devices, allowing all device applications.
The user is enabled for the Active Sync profile.
I have also created 2 profiles, one is the default and another is one I setup when the default wasn't working.
I have tried to set up the emulator to connect through the Settings, Network Cards, NE2000 Compatible Ethernet Driver and configured it with an IP address.
I then went to ActiveSync and tried to set it up to point to a mailbox on my Exchange Server 2010 box. It keeps failing. ActiveSync was setup on the Client Access for this server and I even turned off the SSL cert in the IIS but that didn't help. I have allowed non-provisioned devices to work with this, am not requiring a password, Allowing all devices, allowing all device applications.
The user is enabled for the Active Sync profile.
I have also created 2 profiles, one is the default and another is one I setup when the default wasn't working.
Do you have active sync published to the outside world? try first using the testexchangeconnectivity site to connect to a mailbox by activesync in your envoirement. Post the result of the attempt for us to debug the problem.
ASKER
Right now I have it only enabled internally while I am testing the new server. Give me a little time to get it setup on the internet and I will post when done.
You can test internally if you like with the following tool:
https://store.accessmylan.com/main/diagnostic-tools
https://store.accessmylan.com/main/diagnostic-tools
ASKER
alanhardisty:
Ran the tool and got an error:
Failed to detect ActiveSync [HTTP Status: 505]
Ran the tool and got an error:
Failed to detect ActiveSync [HTTP Status: 505]
Usually a 500 error not 505 - are you sure it was 505?
My article in my initial post might help you on that error.
Is the account you are testing one with Administrator privileges?
My article in my initial post might help you on that error.
Is the account you are testing one with Administrator privileges?
you need to check the activesync url and the type of authentication. Should be this data that you should use in the test tool.
ASKER
Definitely a 505 error. It is not an administrator account.
505 is version not supported error. maybe one incompatibility between the internal test software and the cas 2010.
The tool works with ALL version of Exchange happily.
ASKER
I went to the site...www.testexchangeconnectivity.com
Got the following output:
ExRCA is testing Exchange ActiveSync.
The Exchange ActiveSync test failed.
Test Steps
Attempting to resolve the host name outowa.xxx.com in DNS.
The host name resolved successfully.
Additional Details
IP addresses returned: 2x.x.x.x, 6x.x.x.x
Testing TCP port 443 on host outowa.xxx.com to ensure it's listening and open.
The port was opened successfully.
Testing the SSL certificate to make sure it's valid.
The SSL certificate failed one or more certificate validation checks.
Test Steps
Validating the certificate name.
Certificate name validation failed.
Tell me more about this issue and how to resolve it
Additional Details
Host name outowa.xxx.com doesn't match any name found on the server certificate CN=OUTOWA.
Got the following output:
ExRCA is testing Exchange ActiveSync.
The Exchange ActiveSync test failed.
Test Steps
Attempting to resolve the host name outowa.xxx.com in DNS.
The host name resolved successfully.
Additional Details
IP addresses returned: 2x.x.x.x, 6x.x.x.x
Testing TCP port 443 on host outowa.xxx.com to ensure it's listening and open.
The port was opened successfully.
Testing the SSL certificate to make sure it's valid.
The SSL certificate failed one or more certificate validation checks.
Test Steps
Validating the certificate name.
Certificate name validation failed.
Tell me more about this issue and how to resolve it
Additional Details
Host name outowa.xxx.com doesn't match any name found on the server certificate CN=OUTOWA.
>> Host name outowa.xxx.com doesn't match any name found on the server certificate <<
What names are included in your certificate?
Is it a 3rd party SSL certificate>
Does it include the following names:
mail.domain.com
autodiscover.domain.com
internalservername.interna
internalservername
What names are included in your certificate?
Is it a 3rd party SSL certificate>
Does it include the following names:
mail.domain.com
autodiscover.domain.com
internalservername.interna
internalservername
ASKER
Ok, I got past the previous problem, but have the issue below...
Few questions:
1. What's the issue with mobile?
2. Why is it failing?
I'm using DNS round robin with 2 public ips assigned to the domain name.
-----
ExRCA is testing Exchange ActiveSync.
The Exchange ActiveSync test failed.
Test Steps
Attempting to resolve the host name outowa.xxx.com in DNS.
The host name resolved successfully.
Additional Details
IP addresses returned: 2.x.x.x, 1.x.x.x
Testing TCP port 443 on host outowa.xxx.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
Validating the certificate name.
The certificate name was validated successfully.
Additional Details
Host name outowa.xxx.com was found in the Certificate Subject Common name.
Validating certificate trust for Windows Mobile devices.
The test passed with some warnings encountered. Please expand the additional details.
Additional Details
The certificate is only trusted on Windows Mobile 5.0 with the Messaging and Security Feature Pack and later versions. Windows Mobile 5.0 devices won't be able to sync. Root = E=info@valicert.com, CN=http://www.valicert.com/, OU=ValiCert Class 2 Policy Validation Authority, O="ValiCert, Inc.", L=ValiCert Validation Network
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 = 2/15/2011 8:34:02 PM, NotAfter = 2/15/2016 8:34:02 PM
Checking the IIS configuration for client certificate authentication.
Client certificate authentication wasn't detected.
Additional Details
Accept/Require Client Certificates isn't configured.
Testing HTTP Authentication Methods for URL https://outowa.xxx.com/Microsoft-Server-Activesync/.
The HTTP authentication methods are correct.
Additional Details
ExRCA found all expected authentication methods and no disallowed methods. Methods found: Basic
An ActiveSync session is being attempted with the server.
Errors were encountered while testing the Exchange ActiveSync session.
Test Steps
Attempting to send the OPTIONS command to the server.
Testing of the OPTIONS command failed. For more information, see Additional Details.
Additional Details
A Web exception occurred because an HTTP 401 - Unauthorized response was received from IIS7.
Few questions:
1. What's the issue with mobile?
2. Why is it failing?
I'm using DNS round robin with 2 public ips assigned to the domain name.
-----
ExRCA is testing Exchange ActiveSync.
The Exchange ActiveSync test failed.
Test Steps
Attempting to resolve the host name outowa.xxx.com in DNS.
The host name resolved successfully.
Additional Details
IP addresses returned: 2.x.x.x, 1.x.x.x
Testing TCP port 443 on host outowa.xxx.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
Validating the certificate name.
The certificate name was validated successfully.
Additional Details
Host name outowa.xxx.com was found in the Certificate Subject Common name.
Validating certificate trust for Windows Mobile devices.
The test passed with some warnings encountered. Please expand the additional details.
Additional Details
The certificate is only trusted on Windows Mobile 5.0 with the Messaging and Security Feature Pack and later versions. Windows Mobile 5.0 devices won't be able to sync. Root = E=info@valicert.com, CN=http://www.valicert.com/, OU=ValiCert Class 2 Policy Validation Authority, O="ValiCert, Inc.", L=ValiCert Validation Network
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 = 2/15/2011 8:34:02 PM, NotAfter = 2/15/2016 8:34:02 PM
Checking the IIS configuration for client certificate authentication.
Client certificate authentication wasn't detected.
Additional Details
Accept/Require Client Certificates isn't configured.
Testing HTTP Authentication Methods for URL https://outowa.xxx.com/Microsoft-Server-Activesync/.
The HTTP authentication methods are correct.
Additional Details
ExRCA found all expected authentication methods and no disallowed methods. Methods found: Basic
An ActiveSync session is being attempted with the server.
Errors were encountered while testing the Exchange ActiveSync session.
Test Steps
Attempting to send the OPTIONS command to the server.
Testing of the OPTIONS command failed. For more information, see Additional Details.
Additional Details
A Web exception occurred because an HTTP 401 - Unauthorized response was received from IIS7.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Solved issue on my own.
Can you tell me what you did exactly? I'm having the same exact problem it seems.
Also - please have a read of my article which might be of use to you:
https://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/A_2861-Activesync-Working-But-Only-For-Some-Users-On-Exchange-2007-2010.html