Re: RDP Freeze - troubleshooting steps

Tech-Archive recommends: Fix windows errors by optimizing your registry

OK, so the server itself doesn't become totally unresponsive, since
some sessions and the console session continue to work OK.
Regarding the sessions that do freeze, does it happen during
logging on and starting the session, or does it happen while they
have been connected and working for a longer period?
If you don't reset a frozen session, does it eventually become
responsive again, or not?

I'm not sure at all if this helps, but I would check these
articles:

931656 - FIX: You cannot use the Remote Desktop Connection feature
or the Remote Desktop MMC to connect to a remote Windows Server
2003-based server
http://support.microsoft.com/?kbid=931656

947773 - A Windows Server 2003-based computer responds slowly to
RDP connections or to SMB connections that are made from a Windows
Vista-based computer
http://support.microsoft.com/?kbid=947773

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

"benxxv via WinServerKB.com" <u30064@uwe> wrote on 01 feb 2008 in
microsoft.public.windows.terminal_services:

Dear Vera,

Further to my earlier post, few more inputs.

Do all clients freeze simultaneously? Or only some of them ?

only some of them. 3 or 4 at a time.

When this happens, is the console session still behaving
normally ?
We cannot even minimize the RDP. The user gets stuck on the
screen and cannot use the computer and when he closes and
reopens RDP session, it opens the same session that was hung up.

How often does this happen ?

at least every other day.

At what time of the day ?

During working hours 8AM to 5PM when the users are working with
the Application.

Is there any pattern ?

No

Any correlation with print jobs ?

No

Regards.

benxxv wrote:
Dear Vera,

Following are my findings.

Only some of the clients freeze.
Console session is working normal, all we do is reset the TS
Account for that RDP client.
Everyday atleast 3 to 4 clients freezes at different timings
during the day. Print jobs - I am not very sure.

I am aware, with the above vague description we may not be able
to troubleshoot further, but still I seek your help.

Regards,

Do all clients freeze simultaneously? Or only some of them?
When this happens, is the console session still behaving
normally?
[quoted text clipped - 15 lines]

Regards.
.

Relevant Pages

  • Re: Terminal server: restricted each user to one session, but not in local
    ... connect to the console session. ... MCSE, CCEA, Microsoft MVP - Terminal Server ... Allow only a real admin to connect to the console session (this ...
    (microsoft.public.windows.terminal_services)
  • Re: RWW Timing
    ... I understand that you want to monitor when and how ... > to an internal Windows XP or Terminal Server computer. ... SBS creates a connection to the internal client on port 3389 which is ... But it can not tell which one session from the RWW, ...
    (microsoft.public.windows.server.sbs)
  • Re: Restricting TS USers
    ... MCSE, CCEA, Microsoft MVP - Terminal Server ... Terminal Services and Microsoft Windows Server 2003 Service Pack ... the remote session does not end immediately. ...
    (microsoft.public.windows.terminal_services)
  • Re: Terminal Services
    ... The console session is the user session on the physical console of ... On a Windows 2003 server, ... If different user accounts wished to logon i.e. those without ...
    (microsoft.public.windows.terminal_services)
  • Re: ASP sessionstate
    ... :>: so it is a clientside issue. ... ASP doesn't know or care what browser it ... but then it is not a new session. ... :> How can a Response.Write write to the server screen? ...
    (microsoft.public.inetserver.asp.general)