Re: Inactive Telnet Session Timeout -- MIDRANGE-L

Dave

Searching on "telnet AND connection" at the improved search site got many resluts. Here is an article from the Knowledge Base, "Telnet Session Drop Checklist", that may be helpful. <http://www-1.ibm.com/support/docview.wss?uid=nas1a53b17cf8d5ed7c386256cf3006ba9d2&rs=110>

Another on, called, "TCP/IP Problem Analysis - Telnet", at <http://www-1.ibm.com/support/docview.wss?uid=nas14756a9ed93cc7125862565c2007cdbe3&rs=110>, seems more about how to collect information for IBM to look at. Another, "Message TCP2617", (great title, eh?) is about the message in QSYSOPR message queue and QTCPIP job log when connections abnormally closed <http://www-1.ibm.com/support/docview.wss?uid=nas1dce52e8dee822d1d86256d040064def4&rs=110>.

BTW, we have the TCP keep alive set to the maximum value, but we may not be a good reference - I usually use Remote Desktop to connect to my work machine, where I have the sessions running locally - the local ones never drop, a remote one might from time to time.

If you have a secure connection to your work intranet, and you have a work PC with Win XP, you can use Remote Desktop. Even when it fails, the session on the work PC is still there when you reconnect. It's a little slower, but you can optimize that. It's worked really well for me for some time now. You could also use PCAnywhere.

HTH

Vern

At 12:07 AM 9/22/2003 -0400, you wrote:

A longstanding problem I have is that when I telnet from home to work, any
session inactive for about 15 minutes is disconnected.  My home PC's are
behind a router/firewall.  The problem disappears if I set the PC I telnet
from to a fixed IP address, and designate it as the DMZ.  Of course that is
not so good because it leaves the machine exposed.  I believe the AS/400 TCP
and Telnet timeout parameters are adequately defined.  I have tried the
Mochasoft 5250 telnet client as well as Win2K telnet from the command
prompt, with identical results.  Since the problem dissapears when running
in DMZ mode, it seems likely that more than the telnet connection on port 23
is at work here.  The AS/400 must be trying to communicate to my PC using
some port(s) in addition to port 23, and my router is blocking it.  I could
buy a telnet client with a keep-alive feature, but I'd rather not.  So, if
anyone sees a problem with my AS/400 settings, knows the ports used to
maange the session timeout conversation, knows of a cheap telnet client with
a keep-alive feature, or some other solution, please advise.  -Dave K.
                      Change TCP/IP Attributes (CHGTCPA)
TCP keep alive . . . . . . . . .   120           1-40320, *SAME, *DFT
(that's 120 minutes)
                       Change TELNET Attributes (CHGTELNA)
 Session keep alive timeout . . .   0             0-2147483647, *SAME,
*CALC...
(that's "never check for a timeout condition", which I will set to a
reasonable value after all this is resolved")