Telnet Timeout

  • Thread starter Thread starter scorpion53061
  • Start date Start date
S

scorpion53061

I have users using a telnet connection on various configurations of Windows.

I have set up my AIX Server to have an astronomically high number before
their connection times out if they are idle. Customer didnt like being
turned off. However it appears Windows is the one disconnecting them. Is
there a setting or such I can advise them to adjust to allow their
connection to remain?

--
Do you have people in your band or group that only play by ear?
When transposing songs do those that play by ear struggle and
does it leave vocals and band members without a recording in the
correct key to practice with?
Visit http://www.jerichoband.net/jericho/keychange.htm
where you can have the song's key changed to what you need
without negatively affecting the tempo or instruments in the recording...
 
Locate and use a "better" telnet client. Powerterm, Tinyterm and Procomm Plus
all have enhanced setting which control to the telnet sessions better than the
"default" telnet client in most Windows versions.
 
I am not really using the Windows "client". In another control of a Windows
program that is invisible I write, it initiates a connection to my server on
port 23. I give it a stayalive command but Windows disconnects it after a
certain amount of time if there is no activity regardless. I am preparing to
put in a statement that does a random action every few minutes if no
activity is noticed but I would much rather not do that if possible.

Where does Windows set options that handle idle disconnects and such for any
application? I would assume it is in the registry somewhere but would not
know where to look.
 
scorpion53061 said:
I have users using a telnet connection on various configurations of Windows.
Click to expand...
I have set up my AIX Server to have an astronomically high number before
their connection times out if they are idle. Customer didnt like being
turned off. However it appears Windows is the one disconnecting them. Is
there a setting or such I can advise them to adjust to allow their
connection to remain?
Click to expand...

http://www.microsoft.com/technet/pr...nol/windows2000serv/reskit/regentry/58768.asp

Describes how there is a default Telent Keep Alive timeout value.
If there is no entry in the Registry then the default is used.
But the web page describes how you can adjust this.

However, from my reading, it must be the Telnet application that
then makes use of the timeout.

I've been fighting this for a while, made the registry change,
thus far no luck.

It MAY be the Linksys BEFSR41 router that is throwing away the
connection after an idle period. But I haven't been able to
confirm this or to find a way to change that. (At least not in
version 1 of that router)

It MAY be the ActionTec GT701-WG modem, but the support folks
for that deny that this can be the problem and claim that the
default timeout on that cannot be causing this.

And it MAY be something further up the chain.

I've tried this with both ProComm's telnet and Windows telnet.
 
Yves Leclerc said:
Locate and use a "better" telnet client. Powerterm, Tinyterm and Procomm Plus
all have enhanced setting which control to the telnet sessions better than the
"default" telnet client in most Windows versions.
Click to expand...

Can you tell me where in Procomm Plus I can set the timeout
or the Keep Alive Time? I've searched and I can't find it.

I've been fighting what appears to be a 5 minute idle timeout.
Thanks
 
FWIW, I like HyperTerminal's telnet, it's one of the most robust and
compliant terminal emulators out there. Get the free version from the
hilgraeve site, not the one included w/ XP.

Second, I had/have the same problem w/ telnet "dieing", and I tracked it
down to the NAT router, not telnet, nor XP. Are your clients behind a NAT
router? NAT routers have to reuse connection identifiers, and it will
"age-out" older connections if there is no activity on them, well before
the connection itself times-out.
 
Back
Top