Unable to Completely Disconnect a Terminal Server Connection

ID: Q216783

This article discusses a Beta release of a Microsoft product. The information in this article is provided as-is and is subject to change without notice.

No formal product support is available from Microsoft for this Beta product. For information about obtaining support for a Beta release, please see the documentation included with the Beta product files, or check the Web location from which you downloaded the release.
The information in this article applies to:
  • Microsoft Windows NT Server version 4.0, Terminal Server Edition
  • Microsoft Windows 2000 Server
IMPORTANT: This article contains information about editing the registry. Before you edit the registry, make sure you understand how to restore it if a problem occurs. For information about how to do this, view the "Restoring the Registry" Help topic in Regedit.exe or the "Restoring a Registry Key" Help topic in Regedt32.exe.

SYMPTOMS

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.


CAUSE

This issue can occur because Terminal Server implements a "keep alive" mechanism.


RESOLUTION

WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

For information about how to edit the registry, view the "Changing Keys and Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Note that you should back up the registry before you edit it. If you are running Windows NT, you should also update your Emergency Repair Disk (ERD).
To work around this issue:

  1. Apply the latest service pack for Windows NT 4.0, Terminal Server Edition.


  2. Use Registry Editor to add a DWORD value, KeepAliveEnable, with a value of 1 to the following registry key:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server


  3. In the Terminal Server Connection Configuration tool, double-click rdp-tcp, and then click Advanced.


  4. On the On a broken or timed-out connection, connect action the session line, click to clear the inherit user config check box. Click disconnect on the On a broken or timed-out connection, connect action the session, and then click OK.


Additional query words: terminalsvr

Keywords : kbnetwork kbtool kbui
Version : WINDOWS:2000; winnt:4.0
Platform : WINDOWS winnt
Issue type : kbprb


Last Reviewed: June 2, 1999
© 2000 Microsoft Corporation. All rights reserved. Terms of Use.