I manage a 2003 Terminal Server. Normally, we have 30 active sessions at a time. We run several apps including Office, Pervassive SQL client, Attachemante, and several other small apps.
Users access this server from XP and 2000 clients.
The server ran perfectly for many months. About 2 months ago we started having a problem. Users can not logoff the server. They can close the session by clicking on the 'X', but when they do a start > logoff, the server appears to hang forever.
I have setup group policy to force a disconnected session to logoff after 1 minute of inactivity. This works. Through Terminal Manager, I can force a logoff or disconnect.
For many reasons, closing a session by logging off is a much preferred method of exiting a session.
My thinking is that this problem was possibly caused by an update, but I can't confirm this.
Any thoughts on this?
Software/Hardware used:
ASKED:
October 3, 2004 5:15 PM
UPDATED:
November 14, 2010 2:21 AM
We have a similiar situation on Win 2003 Term Svr.
Here are some of the things I’ve found:
Just tried to run an Ad-Aware remover – and now i can log off within seconds rather than minutes. Didn’t think that this was a problem – looking at the problem in the wrong way…..
Article ID : 828326
Last Review : November 3, 2004
Revision : 1.0
SYMPTOMS
It may take 30 to 60 seconds to log off from a Terminal Services session. This length of time is longer than expected.
CAUSE
This problem may occur after you install Microsoft Windows 2000 Service Pack 4 or Windows Server 2003, and if your Remote Desktop Protocol (RDP) Client has two or more redirected printers through the client.
To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix.
Terminal Server hangs with Novell Client 4.83 SP2
Document ID: CTX103265
Created: Feb 9, 2004
Updated: Mar 2, 2004
Products: Citrix MetaFrame XP 1.0 for Microsoft Windows 2000, Citrix MetaFrame XP 1.0 for Microsoft Windows 2003
Symptoms
A Metaframe XP server with the Novell 4.83 Service Pack 2 client may experience a fatal system error after an amount of time.
The problem occurs only after the machine has been running for a day or more.
Cause
This is a problem with the Novell client.
Resolution
Novell fixed the issue in client 4.9 Service Pack 1. See TID10086900 for further information.
I am still searching for answers to this.
If the log off don;t work try using the Terminal Services policy to automatically logoff the user. But you will be required to set some time limit before the users gets log off