activesync not working - been through everything!!
I'm trying to get my iphone to sync up with my exchange server without much success..I have a single server which serves as an internal file server, AD, DHCP server and also now has exchange 2003 SP2 installed on it.I had installed exchange server before I realised the domain the server was registered under was incorrect. I then used the Microsfot tech notes to change the domain name of the server from a no-descript internal one, to the correct one I actually needed. Everything went ok with no errors.Everything works well on the exchange server, people can connect using the web access, can access their mailbox using outlook and if I navigate to http://mail.mydomain.com/oma it comes up (albeit with that warning about not being a compatible device etc)However whenever I try to get it work to my iphone I get nowhere.. the furtherest I've ever had it was:a) - when it had the incorrect domain on it, I could see the mails, but it would not use activesyncb) - when it had the correct domain, it doesn't error, but the mailbox is blank and activesync still not working.I've used the MS testexchange website and it does show a http 500 error on the activesync.the three steps it recommends I've been through with no success (make sure windows auth is on, make sure not just allowing SSL connections, and also even setup a whole new alias for exchange for it to connect to)I'm totally stumped with what to try next...I can't even see any error in the event viewer that seem to be related...Anyone give me some more pointers as to where things are going wrong?cheerrsMTM81
July 6th, 2009 4:53pm
So when you state you've been thru the steps from Microsoft, you followed article http://support.microsoft.com/?kbid=817379I've seen this before and have solved the issue several times using Method 2 from the article above where you create a separate Exchange vDir that doesn't require SSL for OMA
Free Windows Admin Tool Kit Click here and download it now
July 6th, 2009 9:46pm
Yes, please try the steps in KB817379 first. At the same time, I suggest you download ExBPA to have a health check for the Exchange Server. Thanks,Elvis
July 9th, 2009 11:14am