slow screen-motion using Terminal Server

[Guest MacGyver]

Hello,

 

Can someone explain me the problem that happens us when using Terminal server.

There is about 700 thin clients connected to 35 terminal servers, and almost

all of them have the same problem, and it is slow screen motion.

 

For example when they are writing in the MS Word or another program the text

update is slow, they wrote whole word, but only first cahacters appears and

so....

 

The same happens when they are srcolling the web pages (slow)

 

The network is containing D-Link switches, HP Switches and SonicWall Switches.

 

Any idea what to check first ? The networks seems to be ok after we checked

the performance.

 

Thank You

Best regards

[Guest Yuri GMT+1]

RE: slow screen-motion using Terminal Server

 

This is diffucult to troubleshoot.

 

Is the performance of the TS in general good?

 

Do you have multiple networkcards (NIC) in the server?

Is RDP traffic fixed to go over one NIC and all other traffic over the other

NIC?

This could help.

[Guest MacGyver]

RE: slow screen-motion using Terminal Server

 

 

 

"Yuri GMT+1" wrote:

> This is diffucult to troubleshoot.

>

> Is the performance of the TS in general good?

>

> Do you have multiple networkcards (NIC) in the server?

> Is RDP traffic fixed to go over one NIC and all other traffic over the other

> NIC?

> This could help.

 

Hello. thank you for reply !!!

Well the Terminal servers have 2 NIC, one primary and another is backup.

And all traffic for terminal server is passing trough one NIC, in to network.

 

What i think the problem could be something I have not checked yet, and it

is NIC driver. Often using IBM server if windows AUTO UPDATE is enabled on

the server, than the server downloads all updates from Microsoft and installs

it on the server, so if we use another driver on IBM server than its orginal

NIC driver it could cause problems on packet loss-drop...

 

This should maybe be checked ??

 

Best regards

[Guest Yuri GMT+1]

RE: slow screen-motion using Terminal Server

 

I would perform an update on the NIC without users working on the TS. You

never know.

What does it show on the networking tab in the Task Manager?

 

As I said in the first response. It is difficult to troubleshoot. But I also

know that it helps to have somebody to brainstorm with. I will try to respond

on your questions asap.

 

To come back to the driver. I would use the vendors driver and not the MS one.

 

About the NIC. You say one pri and one secondary. Are they working together

with teaming? Or do you manually change the network cable in case of a

failure?

[Guest MacGyver]

RE: slow screen-motion using Terminal Server

 

 

 

"Yuri GMT+1" wrote:

> I would perform an update on the NIC without users working on the TS. You

> never know.

> What does it show on the networking tab in the Task Manager?

>

> As I said in the first response. It is difficult to troubleshoot. But I also

> know that it helps to have somebody to brainstorm with. I will try to respond

> on your questions asap.

>

> To come back to the driver. I would use the vendors driver and not the MS one.

>

> About the NIC. You say one pri and one secondary. Are they working together

> with teaming? Or do you manually change the network cable in case of a

> failure?

 

Nothing is changed manually, both NIC`s are connected whole time against 2

switches. But I`ll check the NIC driver first, than I will connect only my

laptop directly to the terminal server with crosower cable and test it than,

if it works than the problems are not located in the terminal server.

 

But as you say it helps a lot to brainstorm there is no talk about it.

 

Thank you for helping again!!

 

Best regards

[Guest Vera Noest [MVP]]

RE: slow screen-motion using Terminal Server

 

=?Utf-8?B?TWFjR3l2ZXI=?= <MacGyver@discussions.microsoft.com>

wrote on 20 maj 2008 in

microsoft.public.windows.terminal_services:

>

>

> "Yuri GMT+1" wrote:

>

>> I would perform an update on the NIC without users working on

>> the TS. You never know.

>> What does it show on the networking tab in the Task Manager?

>>

>> As I said in the first response. It is difficult to

>> troubleshoot. But I also know that it helps to have somebody to

>> brainstorm with. I will try to respond on your questions asap.

>>

>> To come back to the driver. I would use the vendors driver and

>> not the MS one.

>>

>> About the NIC. You say one pri and one secondary. Are they

>> working together with teaming? Or do you manually change the

>> network cable in case of a failure?

>

> Nothing is changed manually, both NIC`s are connected whole time

> against 2 switches. But I`ll check the NIC driver first, than I

> will connect only my laptop directly to the terminal server with

> crosower cable and test it than, if it works than the problems

> are not located in the terminal server.

>

> But as you say it helps a lot to brainstorm there is no talk

> about it.

>

> Thank you for helping again!!

>

> Best regards

 

What you describe sounds to me a typical problem with the latency

of the connection.

Latency is very important for terminal server sessions, as it's the

amount of time it takes packets to go from the client to the server

(typing), and from the server to the client (screen changes /

refresh, printing, audio...).

 

You can test latency with the "ping" cmd line utility.

Anything over a few hundred mS will induce perceived lag/slowness

 

Most connections have a latency < 100mS, however some have latency

> 400mS, which induce sluggish response. The most common

connections with high latency are satellite and wireless Internet

Providers.

Nothing you can do about latency, other than finding a backbone

with a better response time.

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

TS troubleshooting: http://ts.veranoest.net

___ please respond in newsgroup, NOT by private email ___

[Guest Mark Stoker]

RE: slow screen-motion using Terminal Server

 

We had something similar - we use Wyse S30/V30 Thin clients. When we

configured the RDP connection with BITMAP CACHING enabled we somtimes had

black 'blocks' on the screen together with the 'slowing' down of the screen.

We turned off the BITMAP CACHING whiched fixed the problem.

 

Mark

 

"MacGyver" wrote:

> Hello,

>

> Can someone explain me the problem that happens us when using Terminal server.

> There is about 700 thin clients connected to 35 terminal servers, and almost

> all of them have the same problem, and it is slow screen motion.

>

> For example when they are writing in the MS Word or another program the text

> update is slow, they wrote whole word, but only first cahacters appears and

> so....

>

> The same happens when they are srcolling the web pages (slow)

>

> The network is containing D-Link switches, HP Switches and SonicWall Switches.

>

> Any idea what to check first ? The networks seems to be ok after we checked

> the performance.

>

> Thank You

> Best regards

>

>