Remote Desktop Slow..

[snootalope]

Are delays in typing or clicking (screen refresh) just the way it is?

We've been using remote desktop at our business to provide remote users access while they're on the road. This has always been a problem. It'd be fine if the text could keep up with what someone is typing. Or, keep up with the mouse clicks they make.

We've got two bonded T1's for bandwidth and we're hardly putting a dent in it. I do a cnet.com bandwidth test and the result comes back at over 2MB. The remote connections are all at least 2MB connections as well.

I've tried VNC and Citrix clients as alternatives, but it's pretty much the same results.

I've tried different servers, ones that only have 5 or so users on them.. servers that are dual processors, 4GB of RAM, and tons of disk space.

I've knocked down the colors and resolution for all sessions..

Nothing seems to help.

I've spent hours upon hours searching the internet for answers or recommendations.

Is this just the way it is? Anyone else out there have remote clients that DON'T complain about the speed of their remote sessions? If so, what are you using or what did you put in place to keep em' happy?

 

[lhuegele]

I'm confused here too. Do you have multiple users using remote desktop to gain access to the same single server or are they using remote desktop to access their own PC remotely?

Good luck,

 

[snootalope]

Nope, they all go to a single server. A workhorse machine that isn't even near it's capacity.

 

[itsp1965]

Snootalope a couple of questions for you;

- Although you have bonded T-1s what exactly is the round trip latency in ms when you perform a ping between your users and this server
- With the above on latent links you will experience the issues you have indicated. Since you are using TS primarily ensure that the users connections are configured for the appropriate speed under the experience tab in RDC. Same thing applies to Citrix (you have more granular control of the user experience). I won't comment on VNC because it's NOT designed for WAN use (don't care what version is being used)

Hope this helps

 

[snootalope]

wow.. just ran ping for about two minutes and the average is 286ms. that's horrible!

 

[snootalope]

hmm.. just pinged the external interface of our firewall from a client machine and the average round trip time there was 263ms. that's gotta be the issue huh?

 

[normntwrk]

I would say that's a good place to start



Norm

 

[snootalope]

hmm.. but if I ping google and yahoo from the same client machine, it's still over 220ms. I would expect it to be quicker than that. What do you get if you ping

http://www.goolge.com?

 

[schtek]

yes i have just remoted in from home and hit a work station and server i found that average of 92 ms for google.com ans 32 ms for google.co.uk..

i dont use VPN server i use RDC port 3389


"Practice makes Perfect"
("la pratique rend parfait")
CPO rt'd RN

 

[snootalope]

wow.. 32ms to google? compared to my 260ms.. somethin be wrong with them numbers!

I'm gonna go find someone to yell at.

 

[snootalope]

well.. I didn't find anyone to yell at. I got home and tested my own connection. Ping times to google were 35ms, and to our Firewall at our business was 32ms - averages.

Round trip times from our firewall to our terminal server are less than 10ms. Sure it'll bounce about that occasionally, but it won't stay there for but a ms or two.

I've even knocked down our QoS on our network for testing..

Anyone know different clients, or somekind of different method to test? Maybe something with the profile the user logs on with? Colors for the sessions is limited to 256 already so not much I can do there.

gotta be something..

 

[lhuegele]

There is a lot you don't have control over in this situation. If they are using home PC's - you don't have control over that - they could have tons of spyware choking their own systems. You don't have control over their internet connections, etc.

Good luck,