> On Tue, 30 Nov 1999 04:45:44 -0500, "Ogunsanya A.T."
> <[log in to unmask]> wrote:
>
> >** NETXPORT TCP; Bad status
> >- Loc: 11912; Class: 1; Parm= $00000003; PortID: $869DD400
> >
> >and after some more lines of user logon processes,
> >
> >** NETXPORT TCP : INBOUND; Packet error
> >- Loc: 11911; Class: 1; Parm= $00000000; PortID: $869DEE40
> >
> >Does anyone understand what exactly this means and how I can correct
it?
>
 This morning, we started monitoring the console messages again and we
noticed the message below:

8:14/#J683/373/Could not initialize data in path with TCP

and after a while the system started hanging. Any ideas pls?

Regards.


On Tue, 30 Nov 1999 04:45:44 -0500, "Ogunsanya A.T."
<[log in to unmask]> wrote:

>** NETXPORT TCP; Bad status
>- Loc: 11912; Class: 1; Parm= $00000003; PortID: $869DD400
>
>and after some more lines of user logon processes,
>
>** NETXPORT TCP : INBOUND; Packet error
>- Loc: 11911; Class: 1; Parm= $00000000; PortID: $869DEE40
>
>Does anyone understand what exactly this means and how I can correct it?

No, but often times one can decode the PortIDs as 4 hex numbers to get
the IP address, and that often helps.  I calculate them as follows:

$869DD400 = 134.157.212.0
$869DEE40 = 134.157.238.64

These look like strange numbers.  Do  you have checksum on for TCP?  (It
is OFF by default...that is never a good idea.)

Hope this helps,

Steve Cooper