Avatar of Uptime Legal Systems
Uptime Legal Systems
Flag for United States of America asked on

Terminal server keep-alive

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?  

Microsoft Server OSWindows Server 2003

Avatar of undefined
Last Comment
Uptime Legal Systems

8/22/2022 - Mon

What is the bandwidth like?
Uptime Legal Systems

Server side: Ample.  10+ MB (the terminal server is in a colo facility
Client side:  Cable Internet, tested at 4+ MB.

When the RDP session is active its very snappy.  the problem is it goes "asleep" and has trouble coming back from an idle state.
Uptime Legal Systems

Any other feedback from anyone else?
Experts Exchange is like having an extremely knowledgeable team sitting and waiting for your call. Couldn't do my job half as well as I do without it!
James Murphy

Is there a VPN between the client and server or some other firewall?  It could be that the timeout isn't from the client but its caused by the firewall/VPN timing out the connection.
Uptime Legal Systems

The terminal server itself is behind a Cisco ASA 5505 firewall, and is accessible via a one-to-one NAT.  Have you heard any problems with this particular firewall,
Uptime Legal Systems

View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.