Client Sessions Slow To Log Off

Hello all,

I'm having a problem with our site's Terminal Server in that when a client
logs out, it takes upwards of 10 minutes before the session is actually
ended on the server. The client is stuck at the "Logging off..." screen.
If they close the client session and they try to re-login, the client is
redirected back to the "Logging off..." screen. Log-ins on the other hand
are quick (for most users) - generally it only takes a few seconds to log
in.

I'm watching the TS performance counters on log-off for a session and
there's nothing that jumps out at me as being off - the processors are less
than 5% utilities and the system has 2GB of RAM and less than 300 MB (for
all users), is in use. Any ideas?

Thanks.


.

Relevant Pages

  • Re: Sessions "Time Out" but server still thinks active
    ... also would not fix the Client disconnecting (as you said you suspect router) ... After a terminal server client loses the connection to a terminal ... logs on to the same terminal server again, a new session might be ...
    (microsoft.public.windows.terminal_services)
  • Re: Challenge: Local App to Run in TS Session??
    ... Microsoft MVP - Terminal Server ... Launch Navision RDP Client (preconfigured parameters auto-connects ... given time from within the TS session. ... to run in a non-full-screen window, because as soon as the user clicks ...
    (microsoft.public.windows.terminal_services)
  • Re: Sessions "Time Out" but server still thinks active
    ... in the disconnected state, the user will be able to connect to the ... same session again and continue where she was before. ... MCSE, CCEA, Microsoft MVP - Terminal Server ... something on the client machine itself). ...
    (microsoft.public.windows.terminal_services)
  • Re: Sessions "Time Out" but server still thinks active
    ... KeepAlive has no effect on the client. ... After a terminal server client loses the connection to a terminal ... logs on to the same terminal server again, a new session might be ... can use this setting to enable keep-alive connections and ensure ...
    (microsoft.public.windows.terminal_services)
  • Re: Restrict Terminal Service Access
    ... > terminal server administrator has access to the client machines. ... > on the session change state WTS_REMOTE_CONNECT if the remote machine name ... > You can't monitor SessionChange events with the current .NET 1.1 ...
    (microsoft.public.windows.terminal_services)