C
Calvin Cannon
We're using Win2K Terminal Services. Occasionally, a
user's session will become non-responsive. This does not
affect all sessions, but only the one session. And it
doesn't matter if the session is running on the console or
from an RDP client.
I can clear up the problem one of two ways:
1. Log the user out and have her log back in.
2. Kill & restart the user's explorer.exe process.
I've looked at the article at...
support.microsoft.com/default.aspx?scid=kb;en-us;324446
....but this seems to be an SP3 issue. That article also
seems to describe a problem where the entire server
becomes non-responsive rather than just one session.
We're running Win2k Server w/ Terminal Services in App
Mode, SP4 & patched to the latest. Anyone have any ideas?
- CLC
user's session will become non-responsive. This does not
affect all sessions, but only the one session. And it
doesn't matter if the session is running on the console or
from an RDP client.
I can clear up the problem one of two ways:
1. Log the user out and have her log back in.
2. Kill & restart the user's explorer.exe process.
I've looked at the article at...
support.microsoft.com/default.aspx?scid=kb;en-us;324446
....but this seems to be an SP3 issue. That article also
seems to describe a problem where the entire server
becomes non-responsive rather than just one session.
We're running Win2k Server w/ Terminal Services in App
Mode, SP4 & patched to the latest. Anyone have any ideas?
- CLC