To disconnect a Windows 2000 Terminal Services session without signing out or stopping its programs, run tsdiscon from a command prompt. Use it alone for your current session, or identify another session with query session and pass its ID or name. The session stays on the server so its user can reconnect and resume.
Disconnect your current session
- From the Terminal Services session, open Start, choose Run, type
cmd, and open Command Prompt. - Type
tsdisconand press Enter. This disconnects the session in which you ran the command.
Microsoft KB 321705 documents this procedure for Windows 2000 Server, Windows 2000 Advanced Server, and Windows 2000 Professional. The article was last reviewed on November 20, 2003: Microsoft KB 321705.
As an Amazon Associate I earn from qualifying purchases.
Disconnect a session by ID or name
To target a particular session, first inspect the sessions on the server:
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →- At the command prompt, run
query session. - Find the target session’s ID or name in the results.
- Run
tsdisconfollowed by that ID or name. For example,tsdiscon 2 /vdisconnects the session with ID 2 and requests verbose feedback. The Windows 2000 article also givestsdiscon rdp-tcp#5as a session-name example.
The documented syntax is tsdiscon SessionID | SessionName [/server:ServerName] /v. Use /server:ServerName to select the Terminal Services server hosting the session; if you omit it, the current Terminal Services server is used. The optional /v requests verbose information. See the Windows 2000 command examples and syntax.
#1 Best Overall
Choose the right target
| Command approach | When to use it | What it targets |
|---|---|---|
tsdiscon |
You are running the command inside the session you want to disconnect. | The current session; no session lookup is needed. |
query session, then tsdiscon ID-or-name |
You need to disconnect a specific session, such as one belonging to another user. | The session whose ID or name you provide. Inspect the results first to avoid selecting the wrong session. |
What happens after disconnection
Disconnecting is not the same as logging off or ending the session. The session remains on the Terminal Services server in a disconnected state, and its programs continue running. When the user reconnects, they can resume that session and continue using those programs. Microsoft describes this behavior in KB 321705.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Permissions and the console-session restriction
- You can disconnect your own session.
- To disconnect another user’s session under the Windows 2000 instructions, you need Full Control access permissions.
- The console session cannot be disconnected with this command.
Microsoft Learn’s current tsdiscon reference lists Full Control or Disconnect special access for disconnecting another user’s session. That reference was updated November 1, 2024, and applies to newer Remote Desktop Session Host environments; it does not list Windows 2000. Do not treat its additional permission option as a Windows 2000 rule.
Quick Recap
Best Value
Rank #3
- Used Book in Good Condition
Rank #2
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
