P
penleydr
I have several users who are complaining about their rdp sessions
locking up on them after varying but relatively short periods of time.
I've experienced the problem myself and am beyond the point of
frustrated with the matter. The terminal server in question is a 2003
Server box. Clients connect using RDP 5.1.
There's no fault in the session timeout settings on the server, I have
it set to an hour. Basically what happens is this - after some period
of inactivity, which I've personally seen range from a few seconds to
15 minutes or so, the session locks up, or disconnects, however you
want to put it.
A couple times I had an extended ping to the firewall or server going
while the rdp session was minimized, and I would get timeouts
SOMETIMES, not all the time, when the rdp connection was actually lost.
It was almost always just a single timeout, then back to a pretty
consistent response, from 55-65ms with a 32 byte ping. If I upped the
size, the results were the same, except for a slightly longer response
time. The highest I got was I think 1372 bytes at around 110-120ms
response.
The only thing that can be done on the client side after the connection
is lost is to close RDP. Sometimes, if the connection is just starting
to be "lost" and the flashing "connection lost" icon starts flashing,
the session can be saved, but you have to be prety quick with the
mouse.
This wouldn't be such a problem except for this little fact - these
users all use a third party application that doesn't free up the
session inside the application when the rdp session gets hosed. I have
to go into Terminal Services Manager and reset the old session. I've
set the "end session after disconnect" down to a minute, but to the
users, it's not good enough. I've thought about all kinds of
possibilities and ways to make the connection more stable, like
dropping the MTU, but nothing is working.
Local users (on the LAN) do not have this issue, only users over the
WAN
The local connection is a full T1, and all users connect over the
internet through ADSL at no less than 3MB up 256 down.
I've tried using a VPN (Sonicwall Global Client) to no avail.
If anyone knows of ways to help keep an rdp session up and stable due
to connections being lost, please share your thoughts...at this point
I'll try almost anything, short of using two cans and a long string.
locking up on them after varying but relatively short periods of time.
I've experienced the problem myself and am beyond the point of
frustrated with the matter. The terminal server in question is a 2003
Server box. Clients connect using RDP 5.1.
There's no fault in the session timeout settings on the server, I have
it set to an hour. Basically what happens is this - after some period
of inactivity, which I've personally seen range from a few seconds to
15 minutes or so, the session locks up, or disconnects, however you
want to put it.
A couple times I had an extended ping to the firewall or server going
while the rdp session was minimized, and I would get timeouts
SOMETIMES, not all the time, when the rdp connection was actually lost.
It was almost always just a single timeout, then back to a pretty
consistent response, from 55-65ms with a 32 byte ping. If I upped the
size, the results were the same, except for a slightly longer response
time. The highest I got was I think 1372 bytes at around 110-120ms
response.
The only thing that can be done on the client side after the connection
is lost is to close RDP. Sometimes, if the connection is just starting
to be "lost" and the flashing "connection lost" icon starts flashing,
the session can be saved, but you have to be prety quick with the
mouse.
This wouldn't be such a problem except for this little fact - these
users all use a third party application that doesn't free up the
session inside the application when the rdp session gets hosed. I have
to go into Terminal Services Manager and reset the old session. I've
set the "end session after disconnect" down to a minute, but to the
users, it's not good enough. I've thought about all kinds of
possibilities and ways to make the connection more stable, like
dropping the MTU, but nothing is working.
Local users (on the LAN) do not have this issue, only users over the
WAN
The local connection is a full T1, and all users connect over the
internet through ADSL at no less than 3MB up 256 down.
I've tried using a VPN (Sonicwall Global Client) to no avail.
If anyone knows of ways to help keep an rdp session up and stable due
to connections being lost, please share your thoughts...at this point
I'll try almost anything, short of using two cans and a long string.