Microsoft KB Archive/216783

= You cannot completely disconnect a Terminal Server connection =

Article ID: 216783

Article Last Modified on 2/27/2007

-

APPLIES TO


 * Microsoft Windows NT Server 4.0, Terminal Server Edition
 * Microsoft Windows 2000 Server
 * Microsoft Windows XP Professional
 * Microsoft Windows XP Home Edition
 * Microsoft Windows Server 2003, Standard Edition (32-bit x86)
 * Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)

-



This article was previously published under Q216783



Important This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry



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 If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

Windows NT 4.0 Terminal Server Edition
To work around this issue, follow these steps:  Apply the latest service pack for Windows NT 4.0, Terminal Server Edition. Use Registry Editor to add a DWORD value, KeepAliveEnable, with a Positive numeric value of 1 (which represents 1 minute) to the following registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server

 In the Terminal Server Connection Configuration tool, double-click rdp-tcp, and then click Advanced. On the On a broken or timed-out connection,  the session line, click to clear the inherit user config option. Click Disconnect on On a broken or timed-out connection,  the session, and then click OK.</ol>

Windows 2000 Server
To work around this issue, follow these steps: <ol> Use Registry Editor to add a DWORD value, KeepAliveEnable, with a positive numeric value of 1 (which represents Enable) to the following registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server

</li> Open Terminal Services Configuration in Administrative Tools, double-click RDP-Tcp in the Connections folder, and then click the Sessions tab.</li> Click to select Override user settings and make sure that Disconnect from session is selected and then click OK.</li></ol>

Windows XP and Windows Server 2003
To work around this issue, follow these steps:
 * 1) Click Start, click Run, type gpedit.msc, and then click OK.
 * 2) Expand Computer Configuration, expand Administrative Templates, expand Windows Components, and then click Terminal Services.
 * 3) In the right pane, double-click Keep-Alive Connections.
 * 4) Click Enabled, and then click OK.
 * 5) Close Group Policy Object Editor, click OK, and then quit Active Directory Users and Computers.

Additional query words: terminalsvr terminal KeepAliveEnable KeepAliveInterval session disconnect session alive

Keywords: kbnetwork kbprb kbui KB216783

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.