Terminal service gets disconnected

[Jasjeet Singh]

I have about five clients that make connection to a
terminal server at a remote location. They seem to work
fine for a while and then it looks like they get
disconnected. I have to make the connection again. It has
happened when I am in the system working and when not
working. Both.

Thanks,
JS

[Matthew Harris [MVP]]

Try either of these:

1) Enable keep alives

support.microsoft.com/default.aspx?scid=kb;en-us;216783

2) change the Value of TCPMaxDataRetransmissions from 5 to
10

support.microsoft.com/default.aspx?scid=kb;en-us;120642

-M

>.
>

[Scott Owens]

Could just be the modem disconnecting
if it is dialup noise on the line or something liek that

"Jasjeet Singh" <jsi...@hotmail.com> wrote in message
news:09f901c2b5e2$cefeda00$cef82ecf@TK2MSFTNGXA08...

[wall...@kmsi.net]

"Matthew Harris [MVP]" <har...@crocker.ucdavis.edu> wrote:

>Try either of these:
>
>1) Enable keep alives
>
>support.microsoft.com/default.aspx?scid=kb;en-us;216783
>
>2) change the Value of TCPMaxDataRetransmissions from 5 to
>10
>
>support.microsoft.com/default.aspx?scid=kb;en-us;120642
>
>-M

I've been trying to enable keepalives for RDP sessions, and I've been using
a sniffer to watch for actual keepalive packets between client and server
when a session is minimized, to be sure it's not just screen updates.

It was a time-wasting exercise in frustration, and I was beginning to think
all those KB articles were little more than placebos. But my sniffer is
now counting packets that must be keeplives.

The key:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server]
"KeepAliveInterval"=dword:00000001

And damn, was that one hard to find. BTW, it took a server reboot to make
it kick in; disabling/enabling the TCP stack wasn't enough.

So, to summarise, here are the (.reg-able) registry entries that I'm now
using (not sure they're all necessary, but they're otherwise apparently
benign):

-----------------------------------------------------------------------
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters]
"KeepAliveTime"=dword:0000ea60
"KeepAliveInterval"=dword:000003e8
"TcpMaxDataRetransmissions"=dword:0000000a

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server]
"KeepAliveEnable"=dword:00000001
"KeepAliveInterval"=dword:00000001
-----------------------------------------------------------------------

giving us (presumably) a one-minute RDP keepalive timer, 10 TCP data
retries, a 60-second TCP keepalive and a one-second TCP keepalive retry
timer. FWIW, I think I believe the MS KB note that says that by default
TCP keepalives are not used and must be enabled by the application. From
what I've seen, TS doesn't, and frobbing and diddling those are a
fustrating waste of time. My guess is that the TS keepalives are the only
ones that do anything.

Oh, and the business of using the TS Configuration -> Sessions ->
Disconnect from Session... I don't know if it makes any difference or not.
Don't see why it should affect whether keepalives are sent, but who knows.

/kenw
Ken Wallewein CDP,CNE,MCSE,CCA,CCNA
K&M Systems Integration
Phone (403)274-7848
Fax (403)275-4535
ke...@kmsi.net
www.kmsi.net