Re: Bad NIC Card ?

Is there a firewall between the PC and your i? Especially if you use things from Management Central but some iNav stuff as well the i attempts to reach out (establish a connection) to the PC. If the PC is behind a firewall this will almost certainly fail. There are other reasons why management central can cause this message as well.

- Larry

DrFranken

Chief Mad Scientist
Frankeni Technology Consulting, LLC
Middleville, MI 49333

www.frankeni.com/frankeni.html

DrFranken@xxxxxxxxxxxx



Chuck Lewis wrote:

*This message was transferred with a trial version of CommuniGate(r) Pro*
Hi Folks,

We keep getting this message on qsysopr every couple of minutes:

TCP/IP connection to remote system 172.16.10.79 closed, reason code 2.

Additional Message Information


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

Message type . . . . . : Diagnostic

Date sent . . . . . . : 07/09/09 Time sent . . . . . . :
10:43:31
Message . . . . : TCP/IP connection to remote system 172.16.10.79
closed, reason code 2.

Cause . . . . . : The TCP/IP connection to remote system 172.16.10.79
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 20663

- remote IP address is 172.16.10.79

- remote port is 3766

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.

More...

This IP address is a specific PC.

I've Googled the message and got info from IBM (first hit !) about using
CHGTCPA to change the Keep Alive setting and it's at 120 so I changed it
to 360 and still get it.

I'm beginning to wonder if there is a NIC card going bad in this PC ? It
doesn't drop the 5250 emulation sessions or anything thing.

Any idea/comments ?

Thanks !

Chuck