Problems Syncing Sprint Mogul Windows Mobile Smart Phone to Exchange Server
Using "Sprint Mogul" Smart Phones with Windows Mobile and Active Sync to Sync with MS Exchange 2003 Server. 1 phone is giving a problem. It just sits there and never completes the sync. The error is that the server could not be contacted. I have 3 other identical phones with the same windows mobile OS and the exact same settings in active sync and they work fine. I hard reset the phone yesterday but it has the same issue. I check for sessions in Exchange system manager on the IMAP server but I never see a session when the phone is trying to sync. This phone did work fine for a long time and the issue started when the end user decided to try adding another account to the messaging section and that's when the issue started supposedly. I also updated the Windows 2003 SBS to SP2 right around the time this problem started but like I said the other smart phones are still working fine so I don't think the SP2 update did anything to it.
ASKER
No certificate errors. The phone does get to the internet. How do I get the URL for my OWA page? I thought it was just http://servername but I get a not authorized message when I do that. I checked IIS and its set to grant all access.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
OK, good stuff so far. I was able to hit the OWA at all of the above addresses. I even set up the sync on my palm treo with that user account and it worked fine.
Now see if you can access /oma instead of /exchange. Try it for a user that's working and for the user that's not working.
ASKER
It works for the user that's not working on the phone. I could not test anyone else because that first user is staying logged in.
Sounds like everything is working as it should, especially if you did NOT receive any cert errors. Try accessing the /oma page on the phone that's a problem now.
ASKER
Turns out its a bad phone. Sprint is sending a new one. Thanks for you help ! Very informative.
If it can, try hitting your OWA page and make sure that works as well. Also take note if you receive any certificate errors.