Disconnect from RDP clients

[Matthew Reed]

Hi, I have a Windows 2000 terminal server that has roughly 25 users. The
terminal server is acessed over the internet via VPN and one to one NAT over
a DSL connection. When my remote users stop working on their desktop for a
short period (1 - 2 mins). the client is disconnected. When the user logs in
again, he gets a new session. His existing session is still marked as active
in the Terminal services manager. Does anyone have any tips that might help?

Regards,

Matthew Reed

[Vera Noest [MVP]]

Could well be that there is 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
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---

=?Utf-8?B?TWF0dGhldyBSZWVk?= <Matthew

Post by Matthew Reed
Hi, I have a Windows 2000 terminal server that has roughly 25
users. The terminal server is acessed over the internet via VPN
and one to one NAT over a DSL connection. When my remote users
stop working on their desktop for a short period (1 - 2 mins).
the client is disconnected. When the user logs in again, he gets
a new session. His existing session is still marked as active
in the Terminal services manager. Does anyone have any tips that might help?
Regards,
Matthew Reed

[Adrian]

Post by Vera Noest [MVP]
216783 - Unable to Completely Disconnect a Terminal Server
Connection
http://support.microsoft.com/?kbid=216783

Anyone know if the registry settings for Windows 2000 server also apply to
Windows 2003 server?

Thanks,

Adrian

Post by Vera Noest [MVP]
Could well be that there is 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
216783 - Unable to Completely Disconnect a Terminal Server
Connection
http://support.microsoft.com/?kbid=216783
http://terminal.servebeer.com/php/flaky_connections.php
--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---
=?Utf-8?B?TWF0dGhldyBSZWVk?= <Matthew

Post by Matthew Reed
Hi, I have a Windows 2000 terminal server that has roughly 25
users. The terminal server is acessed over the internet via VPN
and one to one NAT over a DSL connection. When my remote users
stop working on their desktop for a short period (1 - 2 mins).
the client is disconnected. When the user logs in again, he gets
a new session. His existing session is still marked as active
in the Terminal services manager. Does anyone have any tips that might help?
Regards,
Matthew Reed

[Matthew Reed]

Thanks for your help Vera - have applied the registry changes and wait to see
if the problem has been solved.

Regards,

Matthew Reed.

Post by Vera Noest [MVP]
Could well be that there is 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
216783 - Unable to Completely Disconnect a Terminal Server
Connection
http://support.microsoft.com/?kbid=216783
http://terminal.servebeer.com/php/flaky_connections.php
--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---
=?Utf-8?B?TWF0dGhldyBSZWVk?= <Matthew

Post by Matthew Reed
Hi, I have a Windows 2000 terminal server that has roughly 25
users. The terminal server is acessed over the internet via VPN
and one to one NAT over a DSL connection. When my remote users
stop working on their desktop for a short period (1 - 2 mins).
the client is disconnected. When the user logs in again, he gets
a new session. His existing session is still marked as active
in the Terminal services manager. Does anyone have any tips that might help?
Regards,
Matthew Reed