RDP Sessions Disconnect

[Guest]

I am having a problem at one of my accounts that I hope someone can offer
some direction on.

Remote users get disconnected, seemingly at random. They might have been on
for 5 minutes, they might have been on for 2 hours. They may show no
inactivity time, or they may show some time (it is set to 30 minutes
currently). They might be printing, or they might just be entering data.
There is no consistency to it.

They log on from different sites. Those on cable seem to have more trouble
than those on DSL or dialup.

Nothing is logged in the event log on the Terminal Server.

The can get disconnected with 5 users logged on or with just 1 or 2.

The RDP is the most current version. Connections are made from Windows XP
Pro workstations, via Symantec Enterprise VPN Client, through D-Link (cable)
or Actiontec (DSL) routers, to DSL connection through Cisco moden/router, to
Symantec VPN/Firewall 200R to a dedicated W2K Terminal Server running 2
processors with 1.3 GBytes of memory. It seems to me that all of the tools
should be in place.

Then only thing I have been able to notice is that when watching on the TS
task manager, I will oftentimes (can't say always) see a BIG spike in CPU
activity when someone gets disconnected.

HELP!!!!!!!!!

Bob Showalter, Packer International
(e-mail address removed)

 

[Guest]

If RDP connections from the local network do not experience problems, the
it's a bandwidth issue.

If all remote users get disconnected, then it's a problem with your WAN
connection getting saturated.

If only one user gets disconnected, then it's a problem with their connection.

If ALL users, local and WAN get disconnected, then you need to start
monitoring processes & resources on the server to see what the culprit is.


Patrick Rouse
Microsoft MVP - Terminal Server
http://www.workthin.com

 

[Guest]

Patrick,

Thanks so much for the reply. Bandwidth is something I had never considered
as the number of remotes sites has grown. They do not use any RDP
connections on the local network, just from remote sites to the Terminal
Server.

When you say "If all remote users get disconnected" I assume you do not mean
all at one time? That does not happen. It is a one at a time thing. And it
is not particular to any one user or location.

And I have had users tell me that at times when no one else is working
(holidays, etc.) they do not have the problem. I guess that could support
the idea of a faster connection needed at the Server. The main office is
running DSL that was purchased as 256K, but in reality is 640K. The remote
sites are cable and I think all but one of them is running 1.5 M.

So I will look into this and see about upping the speed at the main office.

Again, thanks, and if you have any other ideas based on what I just said, it
would be appreciated also.

BobS

 

[Guest]

If you have the option, go for a SDSL or T1 connection, as ADSL connections
ususlly max-out at 384Kbps upstream, which is used when people print toi a
remote location or when they transfer files to their remote computer.

Satellite connections are BAD.

Patrick Rouse
Microsoft MVP - Terminal Server
http://www.workthin.com