The primary effect that this will have is poorer battery life for users with relatively low mail volumes, for high volume users the mail downloads dominate the power consumption so power users tend not to notice these problems as much as those who only get infrequent mail. Given that you are certain your own firewalls are not enforcing the session timeouts it is pretty clear that the most likely culprit is the Cellular provider. There is some specific information on the components involved and what is being reported by this error in this technet article. There are a lot of iPhones and Palm devices in the organization, including mine, and I have yet to get a complaint that seems to relate to this. My firewall is an OpenBSD box using the default tcp.established timeout of 86400 seconds (24 hours), so I don't think this is a problem. Most of the documentation I've found on this refers to firewall timeouts. There are no accompanying explanatory log messages. For more information about how to configure firewall settings when you use Exchange ActiveSync, see Microsoft Knowledge Base article 905013, "Enterprise Firewall Configuration for Exchange ActiveSync Direct Push Technology" ( ). Specifically, make sure that your firewall is configured so that requests to Exchange ActiveSync do not expire before they have the opportunity to be processed. Make sure that your firewall configuration is set to work correctly with Exchange ActiveSync and Direct Push technology. Owa1 is logging the following errors several times a day:Īug 5 21:01:07 owa1 ActiveSync: 1040: The average of the most recent heartbeat intervals used by clients is less than or equal to. owa1 is exposed to the world on port 443 for external access. I have two Exchange 2007 servers, one (exch1) in Transport Hub, Mailbox, and Client Access roles and the other (owa1) in the Client Access role.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |