Did you also accept the certificate on the iPhone as you would need to to make it work.
Without server access, about all you can do is run the https://testexchangeconnec
Hello, a client of ours is having an issue with getting an iPhone to work with their server. The site is running SBS 2003 and Exchange 2003 (unknown SP level), and has no other mobile devices. I don't have the client's iPhone but I have access to one of my own, and I have a Windows Mobile 6 device as well.
When I set up the WM6 phone and make it use SSL I get no problems connecting with the clients account. Mail, calendar, and contacts all pull down.
When I set up the iPhone with the same settings and credentials I first get an "unable to verify certificate" message, and then when the sync is tried I get a "The connection to the server failed".
Any thoughts? Unfortunately I don't have administrative access to their server so I can't really play around in it, but does anyone have suggestions as to what it might be, and what might cause the iPhone not to work when a WM6 device works fine with the same account/server?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Did you also accept the certificate on the iPhone as you would need to to make it work.
Without server access, about all you can do is run the https://testexchangeconnec
Try disabling SSL and sync with the Exchange Server. See if that works. Also in iPhone's, they can automatically install a certificate incase the root CA is missing from the device. You just need to click 'accept' on prompt.
Here are a few articles to double check the configuration on the iPhone.
http://www.theiphoneblog.c
http://blog.fosketts.net/2
Let us know how it goes.
As you said you can sync windows mobile not the iPhone ,please check Sp on Exchange it should be Sp2 ,iPhone wont sync without it.
And let us know if you use SSL or not,if you have internal certificate you will need to install it on the iPhone
By default iPhone configures with SSL you need to manually turn it off.
Follow http://support.apple.com/k
Wow, quite a few responses.
I know that SSL is required for this, as when I used the WM6 phone it would only work with SSL enabled.
However, I do not think Exchange 2003 SP2 was applied, or any SP for that matter. When I contacted the technician he read off a build 6XXX number to me when he went into the server properties in ESM, and said that no SP text existed. He installed SP2, but now neither the WM6 phone nor the iPhone connect. The iPhone is acting the same as it has been, and the WM6 device is giving off a 0x85010014 error. OWA still works fine, however. Additionally, the testexchangeconnectivity.c
Thanks all, I'll let you know how it goes from here. Just wanted to update you all with the new info.
If you send your IT department my checklist - now also sitting at http://www.it-eye.co.uk/fa
Security / permissions / authentication methods need to be setup correctly for Activesync to work.
Once the WM6 phones are working, the iPhone should also work.
Alanhardisty, that link appears broken on my end, and I cannot access just www.it-eye.co.uk. Is that site having issues?
Business Accounts
Answer for Membership
by: alanhardistyPosted on 2009-09-10 at 07:14:23ID: 25300419
Here is my activesync troubleshooting guide - please check all settings, run the tests and all should be well:
You need to make sure that you have Exchange Server 2003 Service Pack 2 Installed - http://www.microsoft.com/d ownloads/d etails.asp x?FamilyID =535BEF85- 3096-45F8- AA43-60F1F 58B3C40&di splaylang= en
Open Up Exchange System Manager - Start, Programs, Microsoft Exchange, System Manager. Expand Servers, Right-Click your server and choose properties. This will display whether you have SP2 installed or not.
If you have installed SP2, check on https://testexchangeconnec tivity.com running the Exchange Activesync check. You may need to tick the Ignore Trust for SSL check box if you have a self-signed certificate as these always fail.
Ensure that port 443 is open and forwarded on your firewall to your Exchange server.
Please check and mirror the settings below - Open up IIS and expand the default website then Click on the Directory Security Tab:
c Virtual Directory
om/kb/9376 35
Exchange Virtual Directory
· Authentication = Integrated & Basic
· Default Domain = NETBIOS domain name - e.g., yourcompany
· Realm = yourcompany.com
· IP Address Restrictions = Granted Access
· Secure Communications = Require SSL NOT ticked
Microsoft-Server-Activesyn
· Authentication = Basic
· Default Domain = NETBIOS domain name - e.g., yourcompany
· Realm = NETBIOS name
· IP Address Restrictions = Granted Access
· Secure Communications = Require SSL NOT ticked
For SBS 2003 - please check this MS article - http://support.microsoft.c
Then issue IISRESET from Start, Run
Make sure that the name on the certificate that you are using matches the FQDN that you are connecting to e.g., mail.microsoft.com. If it does not match, either re-issue the certificate if you created it yourself, or re-key the certificate from your SSL certificate provider.
Ensure that the IP for the Default Website is set to All Unassigned
Ensure that Forms Based Authentication is NOT turned on under HTTP Virtual Server under Exchange Protocols. If it is read http://support.microsoft.c om/kb/8173 79
ASP.NET should be set to version 1.1 for all virtual directories listed above.