TCP Connections "Age Out"...

  • Thread starter Thread starter frodo
  • Start date Start date
F

frodo

TCP Connections "Age Out".

I have an "issue" w/ TCP connections simply "timing out" at the XP end of
things.

If I have, say, a telnet session open, and I go into my browser and view
several (20 or 30) pages, when I come back to telnet its connection is
dead. This happens even if I've only been away for 1 minute. When I
reconnect, my session is still there at the remote end, I have to kill it;
so, it dies at my end, not the unix host end. [FWIW, there is no
interveining terminal server - this is a broadband connection].

If I do nothing else, say for 20 minutes, the telnet session is still
alive. It only dies if I open many subsequent connections. So, it's not
strictly a time issue.

What I believe it is is that the connection "number" has gotten "too old"
and XP has killed it. This smacks of the security fix from several months
ago that only permitted so many "in-progress" (ie, sync) tcp connections.
But this is different, it's an "aged out" connection, not a "timed out"
one.

Setting reg entries for keepalive seems to have had no effect.

I have never heard of a tcp stack implementation doing this. Does
anyone else have this same issue, or heard of it, and is there a cure?
It's very annoying!!!

TIA...
 
Kelly said:
Dunno. Start here and good luck!
http://www.google.com/search?hl=en&q=Telnet+times+out
Click to expand...

well, of course I did do that prior to asking you fine people for help,
but I did look again, and tho there was nothing explicitly addressing my
issue, there was a thread that mentioned that a NAT may do something like
this, which, unfortunately, makes a lot of sense. I now suspect it is the
NAT and not XP; I'll have to go back and use a dialup connection to verify
that the "problem" does not occur under dialup; if so then XP is
vindicated. turning off pipelining in the browser might help too.

thanks...
 
Back
Top