TS Client Disconnects - new thread

[Ken Doerbecker]

OK, we were getting off track so here's a frsh start.
Please check out my logic on this.

Issue: remote clients to a TS disconnect randomly.
Sometimes they complain about the network not being
available.

I have seen this caused by soho routers that reboot
occasionally or VPN routers that do not have the "keep
alive" feature set and timeout after a while. This is NOT
the case in my situation. My router has been up solid for
5 days and I am not using VPN.

My situation seems to be caused by packet loss or delays
which are within the normal performance range of the
Internet as it exists today. The default setting for data
transmission retries established by MS in Win 2k or XP is
5 retries with each retry waiting double the time of the
prior one. The starting wait time is the latency that was
experienced during the connect process.

So, if we initally connected with say a 10 ms latency. TS
is going to retry in 10, 20, 40, 80, and 160 ms and then
disconnect. Add that up and you get 310 ms.

I find that it is not unusual for latency to vary from
under 10 ms to nearly 1 second. Also, from time to time,
it is aso not unusual for the Internet to go braindead
for 5-10 seconds.

So, it would seem more appropriate to set this default to
10. This would retry at 10, 20, 40, 80, 160, 320, 640,
1280, 2560, and 5120 ms. Total time before disconnect
would be 10230 ms. 10.2 seconds would seem more
appropriate.

Am I nuts, misinformed, dazed, confused or, God forbid,
correct? Is waiting 10 seconds harmful?

Ken

 

[Matthew Harris [MVP]]

Many terminal server admins set that to 10. It is a good
idea, although setting it too high can be a problem.

-M

 

[S Verne]

What registry setting did you change on the XP pc?

 

[Matthew Harris [MVP]]

Cool. Glad this helped. Most TS admins adjust that
registry entry to 10 as well as turning on keep alives.

Well, from Microsoft's point of view (and I have talked to
a few MS guys about this) doing the fix you just performed
sometimes can affect and/or cause other problems. In most
cases, it won't do anything except fix your problem, but
it is in Microsoft's best interest to not give out fixes
like this that can cause side-effects. I mentioned it to
another person in a MS chat and was quickly told that
while this registry fix may indeed fix the problem, it
isn't recommended. Other than that, I can't give you a
more definite answer.

This is Microsoft's policy on several things. For
instance, they only distribute certain hotfixes through
their support phones. These fixes (much like the one you
are using) can possibly upset your server, and in some
cases, those sideeffects may not be so temporary os
insignificant.

So...the moral of the story is that if you don't want to
pay for support from Microsoft, you should come to the
newsgroups! We are here to help you! Microsoft is really
putting the push for 'community', so if you have a
problem, then please post it!

Anyways...so all the people who have replied to this
thread, the registry entry and information and be found
here: (the link will most likely wrap)

http://www.microsoft.com/windows2000/techinfo/reskit/en-
us/default.asp?url=/windows2000/techinfo/reskit/en-
us/regentry/58805.asp

As I said before, sometimes a registry change can be good
and bad, so beware when adding things like this to your
registry. Be sure to backup the registry beforehand and
then reboot your system after you put the change in.

-M

 

[arno schoblocher]

Hello Mathew,

I am also interested where you set the value of "10". Would you pls. let us
know?

I set KeepAlive to the following values, does this make sense?

HKLM\System\CurrentControlSet\Services\TCPIP\Parameters (all values in
decimal):
- KeepAliveInterval 1000 milliseconds
- KeepAliveTime 120,000 milliseconds (2 minutes)
- TCPMaxDataRetransmissions 10 (repeat 10 times)

Thank you

arno