I've had this problem on multiple terminal server deployments--and am having it on one server specifically now. This particular server is Windows Server 2003 R2 running terminal services.
The problem we're having is that if a user leaves their terminal server window idle or minimized for even a couple of minutes, when they try to restore their session or click back into their TS window, one of two things happen:
1. Their TS window is completely black, and clicking on it does nothing, OR
2. They get the 'Re-connecting attempt 1 of 20..." dialoge
In both cases it takes upwards of 60 seconds to re-connect. This may not sound like a big deal, but having to wait a minute each time the user steps away or switches to another program for a few minutes THEN having to wait is a major productivity problem.
I've read up on articles (including here) on setting the keep-alive, and have set it as such. Quick config info:
Terminal Server Keep-Alive (in registry): Enabled
TCP Keep Alive (in registry): Not set (shoudl this be set too?)
End Idle Sessions In: 3 hours
End Disconnected Sessions In: 3 hours
Desktop Resolution set on Console of TS: 1024x768
I've also read that resolution can be a problem. Whats the ideal setting? Should this be set on the console of the terminal server? On the desktop of the local client PC itself? Somewhere else?
Any other feedback as to what causes TS sessions to go idle/dead so quickly?