Article ID: 216783 - View products that this article applies to.
This article was previously published under Q216783
After a Terminal Server client loses the connection to a Terminal Server, the session on the Terminal Server may not transition to a disconnected state, instead, it may remain active even though the client is physically disconnected from the Terminal Server. If the client logs back in to the same Terminal Server, a totally new session may be established, and the original session may still remain active.
This issue can occur because Terminal Server implements a Keep Alive mechanism.
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/322756/ )How to back up and restore the registry in Windows
Windows NT 4.0 Terminal Server EditionTo work around this issue, follow these steps:
Windows 2000 ServerTo work around this issue, follow these steps:
Windows XP and Windows Server 2003To work around this issue, follow these steps:
Article ID: 216783 - Last Review: February 27, 2007 - Revision: 6.4
Contact us for more help