RE: Meanings of TCP/IP connection error messages ?

Hi Jan,

Great link, thanks but still not sure what is going on/why.

I've dug into this a little deeper and here is where is gets interesting,
for lack of a better word :-)

The remote user has been using a Windows 98 PC for months and said he could
leave that one connected but doing nothing for HOURS. And I can confirm that
I can do this on my Windows 2000 Pro PC at home. So this is coming down to
something in Windows XP it looks like. This should be fun... But that was
good information you pointed me to and I appreciate it.

Thanks,

Chuck

-----Original Message-----
From: midrange-l-bounces+clewis=iquest.net@xxxxxxxxxxxx
[mailto:midrange-l-bounces+clewis=iquest.net@xxxxxxxxxxxx] On Behalf Of
Jan.Rockstedt@xxxxxxxxxxxx
Sent: Wednesday, January 21, 2004 8:34 AM
To: Midrange Systems Technical Discussion
Subject: Re: Meanings of TCP/IP connection error messages ?

Hi !

http://www-912.ibm.com/s_dir/slkbase.nsf/1ac66549a21402188625680b0002037e/dc
e52e8dee822d1d86256d040064def4?OpenDocument&Highlight=0,TCP2617

Mvh / Regards Jan Rockstedt
HSB Syd IT
Spangatan 37B, 2:a van.
211 53 Malmo Sweden
Phone: +46-40 - 668 07 45
Fax: +46-40-668 07 55
www.sydit.hsb.se




"Chuck Lewis" <clewis@xxxxxxxxxx>
Sänt av: midrange-l-bounces@xxxxxxxxxxxx
2004-01-21 14:30
Sänd svar till Midrange Systems Technical Discussion
 
        Till:   "midrange-l" <midrange-l@xxxxxxxxxxxx>
        Kopia: 
        Ärende: Meanings of TCP/IP connection error messages ?
Hi Folks,

We have a VPN user that is getting knocked off. He says it is like it is
timing out (when he is in the process of entering a long order or bid). He
is running XP on a new PC, cable access over the internet to a dedicated 
T1
here. He is running the Synapse IP Client product for 5250 emulation. We 
are
V5R2.

What I see on the iSeries side around the time of his job logs is the
following:

Message ID . . . . . . :   TCP2617       Severity . . . . . . . :   20


 Message type . . . . . :   Diagnostic


 Date sent  . . . . . . :   01/20/04      Time sent  . . . . . . :
20:41:32 

 


 Message . . . . :   TCP/IP connection to remote system 192.168.2.4 
closed,


   reason code 2.


 Cause . . . . . :   The TCP/IP connection to remote system 192.168.2.4 
has


   been closed. The connection was closed for reason code 2.  Full
connection 

   details for the closed connection include:


     - local IP address is 172.16.10.11


     - local port is 23


     - remote IP address is 192.168.2.4


     - remote port is 4718


 Reason codes and their meanings follow:


     1 = TCP connection closed due to expiration of 10 minute Close Wait
timer. 

     2 = TCP connection closed due to R2 retry threshold being run.


     3 = TCP connection closed due to keepalive timeout.


 If TCPCNNMSG(*THRESHOLD) is defined for the Change TCP/IP Attributes
(CHGTCPA) 

   command then there could be additional connections that have closed
within 

   the threshold window. The number of additional TCP connections that 
have


   closed is 1.


 Recovery  . . . :   Informational message.


and I also get the same message but for #3 above.

 

Anyone have any idea what this is or if there is some setting on the 
iSeries
that can be set to handle this ?

 

Thanks !

 

Chuck

_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.