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: //technet.microsoft.com/library/cc731606.aspx. 2. Set the idle session limit to Never for Remote Desktop Services sessions: //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