Windows 2000 Terminal Server Disconnects

[bjyuke]

Are there any settings regarding the time-out/disconnect time for Windows
2000 Terminal Server?

Is hardware/RAM a factor? We are not currently using any group policies.

My client has a Terminal Server that supports 10 remote users. During the
day time outs occur after about 2-3 minutes of inactivity. At night, this is
much longer - 45 minutes to an hour (or more).

The timeouts seem inconsistant - two connections made at the same time may
experience two different disconnects times.

Can somebody point me in the right direction?

Thank you...

[Vera Noest [MVP]]

Could be a router between your clients and your server, which sees
no traffic and decides that the session must have ended and throws
it out.

The solution in that case is to enable KeepAlives. For the correct
registry key, check:

216783 - Unable to Completely Disconnect a Terminal Server
Connection
http://support.microsoft.com/?kbid=216783

Also check this link:
http://terminal.servebeer.com/php/flaky_connections.php
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

Post by bjyuke
Are there any settings regarding the time-out/disconnect time
for Windows 2000 Terminal Server?
Is hardware/RAM a factor? We are not currently using any group policies.
My client has a Terminal Server that supports 10 remote users.
During the day time outs occur after about 2-3 minutes of
inactivity. At night, this is much longer - 45 minutes to an
hour (or more).
The timeouts seem inconsistant - two connections made at the
same time may experience two different disconnects times.
Can somebody point me in the right direction?
Thank you...