RDP sessions unresponsive and Task manager "hangs"

[AndiK]

We have 5 Windows Server 2003 Enterprise Edition Terminal Servers in a wlbs
cluster with clustered session directory serving about 250 users, most of
them with thin clients.

Starting about 3 weeks ago, our users experience sporadicly unresponsive
sessions. These states can last up to 5 or 6 minutes. If users disconnect and
then reconnect to their session, the problem doesn't remain.

In addition, we can see that on the servers (in console and TS sessions)
taskmanager misbehaves like that:

It takes up to 10 or 15 seconds to show up and lot of more seconds to show
anything more than a grey screen.

Servers are not "overloaded", processor and ram usage is reasonable. The
above configuration did work well for about 2,5 years.

Is there anyone outside who experiences similar problems or does
anyone have an idea how to fix this issue?

Best regards

Andi

 

[AndiK]

RE: RDP sessions unresponsive and Task manager "hangs"

AddOn:

If i add a counter of one of the two terminal services objects (perfts.dll)
in system monitor, the program immediately stops responding. All other
counters/objects are delivering performance data as expected. This behaviour
occurs locally on the terminal servers (console session) and also with remote
system monitor consoles.

"AndiK" wrote:

> We have 5 Windows Server 2003 Enterprise Edition Terminal Servers in a wlbs
> cluster with clustered session directory serving about 250 users, most of
> them with thin clients.
>
> Starting about 3 weeks ago, our users experience sporadicly unresponsive
> sessions. These states can last up to 5 or 6 minutes. If users disconnect and
> then reconnect to their session, the problem doesn't remain.
>
> In addition, we can see that on the servers (in console and TS sessions)
> taskmanager misbehaves like that:
>
> It takes up to 10 or 15 seconds to show up and lot of more seconds to show
> anything more than a grey screen.
>
> Servers are not "overloaded", processor and ram usage is reasonable. The
> above configuration did work well for about 2,5 years.
>
> Is there anyone outside who experiences similar problems or does
> anyone have an idea how to fix this issue?
>
> Best regards
>
> Andi
>