We're having problems getting iPhones to sync properly with SBS 2003 Exchange.
When you add a new Exchange ActiveSync account on an iPhone and enter all the pertinent information, it shows a "Verifying Exchange account info" message for a minute or so, then says everything's verified and asks what you want to sync, Mail, Contacts, Calendars... so it looks like it's working.
However, when you go to the Mail app and select the Exchange email account, it just shows an "Inbox" folder with nothing in it. When you try refreshing, it attempts for a second, then says "Last Updated" with a timestamp, as if it worked, but there's no mail and no error message/feedback at all.
I think I've narrowed it down to some sort of certificate issue, but I'm having trouble finding out where to go from here... I ran MS's Exchange connectivity testing tool with these results:
Our cert was purchased from Network Solutions, and I'd already added it to the IIS Default Website for OWA purposes. But this report makes it look like the cert is somehow problematic. I don't know what to do now...
Here's a shot of the cert details, just in case:
Does the iPhone have the CA for that certificate on it by default (I'd expect it to being a Verisign cert but you never know)?
If you can browse on the iPhone to https://yourdomain.com/exchange with no warnings then it shouldn't be a certificate issue.
If you've not already had activesync working I'd be thinking authentication settings in IIS or something along those lines.
You're getting that error in the Exchange connectivity testing tool because the Network Solutions SSL certificate isn't trusted by default in Windows Mobile phones. The only ones that are trusted by default are:
I usually go with GoDaddy certs for this reason (they purchased Valicert and their CA root awhile ago).
That being said, iPhones do trust Network Solutions certs. Are you running Exchange 2003 SP2? iPhones need Exchange 2003 SP2 to sync.
So... it turns out the issue is a Small Business Server Exchange 2003 problem. I got it solved by following this Microsoft KB article.
Though different diagnostic tools were hinting at unrelated issues, like certificates and authentication, the problem was that ActiveSync on SBS is expecting a specific Virtual Directory in IIS called
exchange-oma
that was not there for some reason, so I had to create the directory myself:I'm not sure how that VDir wasn't there, but recreating it did the trick.
Thanks everyone...