I have an iPhone 3G (running OS 4.1). I have it connecting to Exchange 2003 (SP 2). Over the past several weeks I and my users have had difficulty getting the iPhone to sync with our exchange accounts. The oddities are as follows: *) When an Outlook client is open to the same account as the iPhone, the iPhone will sync. *) When I reboot my exchange server the iPhone will sync (at least for a little while). *) When I set up the exchange account on the iPhone, the account will "verify" just fine. But when I tried to connect to the account I get a message that says "cannot get mail. The connection to the server failed." If I press "ok" in response to this message, the message does not appear again but mail also does not flow (unless the Outlook client is open as described above). *) The log files in the "C:\WINNT\system32\LogFiles\W3SVC1" directory have jumped from under 10 megs to over 300 per day. Any help or experience anyone can offer would be greatly appreciated. *) I have tried restarting the Exchange and IIS services on the server. No effect.

Hi Just test the basics Does it work from any other mobile device? Windows mobile? If it does, contact the vendor for the phone (apple), they also have a forumJonas Andersson MCTS: Microsoft Exchange Server 2007/2010 | MCITP: EMA 2007/2010 | MCSE/MCSA Blog: http://www.testlabs.se/blog

This does not just affect one phone. I have five users who all have 3G or 3GS phones. I have two users with 4G phones and one iPad. This is affecting all of them. I have not seen anything on the Apple forums that is any different than what I have found here. Based on the high volume of logging going on for OMA I am theorizing that this has something to do with the number of connections and possibly the HTTP(S) timeout set on my firewall. I adjusted the timeout on the firewall so that it exceeds the heartbeat interval and then I disabled the Direct Push over HTTP(S) in the Mobile Services Properties of the Exchange System Manager. The logging activity for my OMA decreased from 51 kB per minute down to 5 kB per minute. This means that my users will have to use "Fetch" instead of "Push" to get their mail, but I'm hoping that they will at least stay connected.Dave

Turing off the Direct Push shrunk the size of my oma log, but iphones stopped connecting again this morning. I am thinking that maybe updating the massync.dll to the latest version might help. Or uninstalling and re-installing the ActiveSync directories from IIS. Anyone got any ideas? Any response would be appreciated.Dave

Is it a single exchange box environment? Is SSL or forms-based authentication enabled on the /Exchange virtual directory? Please follow the KB below to troubleshoot the issue Exchange ActiveSync and Outlook Mobile Access errors occur when SSL or forms-based authentication is required for Exchange Server 2003 Please browse the “Microsoft-Server-ActiveSync” virtual directory, the expect error feedback is “501/505” on the webpage Please check if the third-party File Access Manager service is running on the server, which can cause the same symptom The File Access Manager driver (FAMv4.sys) is installed Please enable the Background Scanning & Pro-Active Scanning on the Anti-Virus software Server ActiveSync does not download all items during a synchronization session Please use the Remote Connectivity Analyzer that can help for troubleshooting Please verify the ActiveSync functionality with windows mobile emulator Windows Mobile 6 Localized Emulator ImagesJames Luo TechNet Subscriber Support (http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx) If you have any feedback on our support, please contact tngfb@microsoft.com

These are all great suggestions. Thank you for your very thorough response. It is a single exchange box environment. While SSL and forms-based authentication are enabled, they are not enabled on the Exchange-OMA virtual directory. I created a separate directory for Exchange-OMA. Currently the ActiveSync is working. I followed the instructions in KB 883380, to re-create the ActiveSync directories. I think it may have been a permissions issue. I will follow your other suggestions just to test. Thanks again.Dave