Remote Desktop Loses Connection

[Guest]

First, I hope I'm posting to the correct forum, since my TS server is W2K3.
We recently implemented remote desktops to our W2k3 server via RDP, but I
have many users complaining that their sessions are getting reset, sometimes
after just a few minutes of idle time.

I've tried a number of things, like prioritizing the RDP traffic, setting
the registry on the server to enable keepalives and maxtcpretransmissions,
and I've checked the RDP connection settings on the server to make sure it's
not some administrative logoff. The eventviewer doesn't seem to log these
incidents either.

Also, a ping -t to the server shows that ping times are healthy when
sessions are reset.

Can anyone point me in the right direction here? This is really causing me
problems because my users are losing data when these session resets happen.

Thanks in advance,
Kerry Davis
(e-mail address removed)

 

[Guest]

Hi, Kerry
A number of questions:
1. What (if anything) does the server event viewer says regarding
disconnections?
2. Is there a specific error your users receive at disconnection? For
example "Socket closed"...

 

[Guest]

Unfortunately, I haven't been able to find much in the event viewer that
looks related. There don't seem to be any logon event IDs of 538 with type
10 or anything else.

Is there any way to turn on something like verbose diagnostics logging for
Terminal Services to get some descriptive events?

As for the client experience, they are getting absolutely nothing. I've
seen this myself. The RDP client simply closes and disappears and then the
user has to launch a new session. Only seems to happen when idle for at
least a few minutes.

 

[Guest]

1. What is the setting for "idle time" in TS Config?
2. What is supposed to happen if Network connection breaks down? Disconnect
or log off?
3. Also, what do you see in TS Admin for these connections? Do they just
disappear, or do they become "disconnected"?

Jetro CockpIT
Fulfilling the promise of server-based computing
http://www.jp-inc.com

 

[Janaina Rodrigues]

Did you try this:

Terminal Server stops responding when idle sessions are being ended
http://support.microsoft.com/default.aspx?scid=kb;en-us;828662

Windows Server 2003 Terminal Server Stops Responding
http://support.microsoft.com/default.aspx?scid=kb;en-us;821467

Windows Server 2003-Based Computer Becomes Unresponsive to RDP Sessions
http://support.microsoft.com/default.aspx?scid=kb;en-us;826139

 

[Guest]

Thanks for the article references. Unfortunately, the behavior we are seeing
is not the same as what these describe (no blue screens or unresponsive
server). The RDP session simply disappears with no notification to the user.
They can then immediately log back in, but their old session is not
preserved.

I'm trying something by setting the TSConfig properties to explicitly define
"Never" as the session limits for all three settings and to specify
"Disconnect" rather than log off for the behavior of a lost connection.
We'll see if this makes any difference.