At 10:45 30/11/1999 +0100, Ogunsanya A.T. wrote:

>We've been having some problems with our JINETD job for sometime
>reporting communication problems with tcp. We then decided (on advise)
>to increase the Jinetd job to the CS queue. I further started keeping a
>log of console messages and this morning while looking through, I found
>the error below:
>
>** 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

I'm speaking off the top of my head here.

Have you looked at the maximum TCP connections parameter
in NMMGR (NETEXPORT, whatever, path).

I recently had a problem with network printers dropping out
and had an awful time getting them to spool again.  The error
message in this case indicated that transport wasn't started
(yet it most definitely WAS!).

I increased the parameter from 256 to 512 and have had no problems
since.

FWIW.

Ron Burnett
[log in to unmask]