Last Modified: Mar 17, 2021
See more info
Known Affected Versions:
11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 11.6.1, 11.6.1 HF1, 11.6.1 HF2, 11.6.2, 11.6.2 HF1, 11.6.3, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 11.6.4, 11.6.5, 18.104.22.168, 22.214.171.124, 126.96.36.199, 12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4
Opened: May 19, 2014
Remote Desktop session terminates after TCP idle timeout without any activity from the client.
When there is no activity from the RDP client, the session is terminated and the client tries to reconnect to the server.
Remote Desktop Services by default do not send keep-alive packets to the RDP clients. When there is no activity from the client or terminal server, the TCP session is terminated.
To work around the problem, configure AD policy: 1. Set a keep-alive connection interval of 1 minute for the terminal servers: http://technet.microsoft.com/library/cc731606.aspx. 2. Set the idle session limit to Never for Remote Desktop Services sessions: http://technet.microsoft.com/library/cc754272.aspx. 3. Increase TCP idle timeout to 900 seconds on the BIG-IP system if the RDP clients that you support do not send keep-alive packets.