Bug ID 462985: Remote Desktop session terminates after TCP idle timeout without any activities from the client

Last Modified: Oct 17, 2023

Affected Product(s):
BIG-IP APM(all modules)

Known Affected Versions:
11.6.0, 11.6.1, 11.6.2, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3, 12.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2

Opened: May 19, 2014

Severity: 4-Minor

Symptoms

Remote Desktop session terminates after TCP idle timeout without any activity from the client.

Impact

When there is no activity from the RDP client, the session is terminated and the client tries to reconnect to the server.

Conditions

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.

Workaround

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.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips