Question Locked

Big lag problem through terminal services

0 helpful
6 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

We have an MIS running from a server at our head office. We have staff that need to access this from a different site. We are running Terminal Services through a VPN and have recently started seein a major lag. When i say major lag i mean that it can take upto 3 minutes to load a screen that a few weeks ago would have loaded within seconds.

I have been over to the other site trying to solve this problem, When i connect through a standard RDP as an administrator there is no lag what so ever. The lag only occurs when going through terminal services.

Any ideas?

6 replies

by oh smeg

Before tearing into the Server look for communication problems in between the 2 offices. Things like new construction or any other ground works could have cut the connection that is being rerouted elsewhere or through a slower connection till repairs or the work is finished. It may even be routine maintenance where some external Hardware is pulled out of service and the connection is slowed down.

So start off by looking at th actual traffic between the 2 sites and then if that is fine and not slow you can start to look at the server & it's accosted hardware. But you first need to check with the Link Provider for possible problems.

Col

by steven.cottom

The connection between both offices seems to be fine. When i do a remote desktop as an administrator to the server running terminal services the software runs without lag. As soon as i connect through Terminal Services the lag starts.

Cheers

by 1bn0

between RDP for admin and Terminal Services except the number of clients you are licensed for.

??
Default installation allows 2 connections for remote administrtion. License required to allow more connections?

Does anyone else have differnt information?

by robo_dev

The first thing I would do is plug in a hub with a laptop running WireShark or Ethereral open source protocol analyzers and look at some packets to see what's going on.

My first guess is that something changed in the router/firewall, such as MTU size, or some sort of routing error was introduced.

Do a tracert to the server from the workstation and make sure the packets are traversing the route they are supposed to be.

You need to validate what MTU is supported by the VPN that you are using and make sure that the MTU is set correctly in the workstation.

http://www.msterminalservices.org/articles/Poor-Bandwidth-Latency.html

See this troubleshooting guide:
http://support.microsoft.com/kb/274805

Any personal firewall being used in the workstations??

This discussion is closed to new replies.