RE: AS/400 Support for Windows Network Neighborhood problem

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
--
[ Picked text/plain from multipart/alternative ]
IPL the system and then restart TCP, this happed to us just the other week
when someone did a port scan on our system and it left the port open.

-----Original Message-----
From: Jim Langston [mailto:jlangston@celsinc.com]
Sent: Monday, April 08, 2002 12:35 PM
To: 'MIDRANGE-L@MIDRANGE.COM'
Subject: AS/400 Support for Windows Network Neighborhood problem


We have some problems with AS/400 support for Windows Network Neighborhood,
and looking in QSYSOPR messages I see:


 AS/400 Support for Windows Network Neighborhood started, but an error was
   encountered.
                         Additional Message Information



 Message ID . . . . . . :   CPIB687

 Date sent  . . . . . . :   04/06/02      Time sent  . . . . . . :
05:04:27


 Message . . . . :   AS/400 Support for Windows Network Neighborhood
started,
   but an error was encountered.



 Cause . . . . . :   The required AS/400 Support for Windows Network

   Neighborhood (AS/400 NetServer) job QZLSSERVER started, but may not be
fully
   functional because of reason code 1. See the following reason codes and

   their meanings:

     1 - NETBIOS over TCP/IP started with errors - return code 3021.


Although a few entries later I see:

 AS/400 Support for Windows Network Neighborhood (AS/400 NetServer)
   QCELS400 initialization complete.

I am not familiar at all with AS/400 Windows Network Neighborhood support,
nor how to debug it.

Anyone have any suggestions as to where I go from here?

Thanks,

Jim Langston

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