Forum Discussion
Rodney_80133
Feb 11, 2014Nimbostratus
Experienced the same issue: mailbox traffic (the 60001 port in this case) used a TCP keep-alive. The global catalog traffic (the 60002 port in this case) does not. This cause an intermediate Juniper firewall to drop sessions based on its default Maximum Timeout setting of 1800s. Increasing this timeout to 125 min (to make sure it's longer than the default server tcp-keep alive). This alleviated the problem but of course did not solve it completely. A better solution would be to activate a TCP keep-alive on the client, but Outlook does not offer this option (or registry key). Right now I'm looking at activating a TCP keep-alive on the load-balancer VIP between client and server.