NetServer starting problem

[comp.sys.ibm.as400.misc]

I tried to configure a Windows system to AS400 for sharing directory ,
after configuring recycled the NetServer, but encountered the
following error
Message ID . . . . . . : CPIB683 Severity . . . . . . . :
40
Message type . . . . . :
Information
Date sent . . . . . . : 02/01/08 Time sent . . . . . . :
04:47:16

Message . . . . : iSeries Support for Windows Network Neighborhood
(iSeries
NetServer) was unable to
start.
Cause . . . . . : The required iSeries NetServer job QZLSSERVER was
unable
to start because of reason code 5. See the following reason codes
and their

meanings:
1 - Unable to retrieve user
credentials.
2 - Unable to retrieve
credentials.
3 - Exchange user profile
failed.
4 - Unable to obtain lock for service program QZLSSRV1 in library
QSYS.
5 - Start of the NetBIOS over TCP/IP failed with return code
3420.
6 - Start of the internal server failed with return code 3420.
Note:
Return code 16 indicates that there is another computer on the
network
already using the same name as the iSeries NetServer server
name.
7 - Error occurred when sharing resources with the
network.
8 - Unable to retrieve maximum incorrect sign-on attempts system
value.
9 - Unable to retrieve code page
information.
10 - Unable to retrieve host IP address because of return code
3420.
11 - iSeries NetServer requires the services of TCP/IP, which is
not

started.
12 - The iSeries NetServer is configured with an EBCDIC CCSID when
it
should be an ASCII CCSID, or the translation functions are not
working
correctly on the
server.
13 - The retrieved host IP address of is
invalid.
Recovery . . . : Complete recovery for the specified reason
code.
1 - Contact your service
provider.
2 - Contact your service
provider.
3 - Contact your service
provider.
4 - Use the Work with Object Locks (WRKOBJLCK) command to find the
owner
of the lock and take steps to remove the
lock.
5 - Start iSeries NetServer with the reset option using the Start
Server
(QZLSSTRS) API. If the problem continues, restart TCP/IP with the
End
TCP/IP (ENDTCP) and Start TCP/IP (STRTCP) commands. Note: This may
affect
other users. If the return code is 3420, see the recovery for
reason code
13. If the problem continues, contact your service
provider.
6 - Restart the QSERVER subsystem with the End Subsystem (ENDSBS)
and
Start Subsystem (STRSBS) commands. Note: This may affect other
users. After
the QSERVER subsystem is started, start the iSeries NetServer using
either
the Start Server (QZLSSTRS) API or the Start TCP/IP Server
(STRTCPSVR
*NETSVR) command. If the problem continues, contact your service
provider.
7 - Use the Display Message (DSPMSG) command to see messages in
the
QSYSOPR message queue related to resource sharing
failures.
8 - Contact your service
provider.
9 - Contact your service
provider.
10 - Contact your service
provider.
11 - Use the Start TCP/IP (STRTCP) command to start TCP/IP
services.
12 - Make sure the iSeries NetServer is configured with the
correct CCSID.
If the CCSID is correct, contact your service
provider.
13 - Correct the name configured for iSeries NetServer which
conflicts
with an existing name on the network, and try the request
again.

[jacko]

On Feb 1, 5:13 am, "comp.sys.ibm.as400.misc"

Hope this helps you out:
Problem Summary:
After upgrading from V4R5 to V5R1, NetServer failed to start with
error CPIB683 reason code 5 return code 3420 in the QSYSOPR message
queue. Error 3420 indicates there is a name conflict on the network.
The NetServer name was configured to be the same as the iSeries system
name which should work. In testing, the name was changed to another
name and NetServer started successfully.

Resolution:
A Server Message Block (SMB) licensed internal code trace was taken.
The trace showed TCP/IP addresses of several PCs on the network that
had a group name conflicting with the NetServer name. To test this the
following command was run from a DOS prompt using the IP address of
one of the PCs identified in the trace:

nbtstat -a nnn.nnn.nnn.nnn *** substituting the PC IP address

The NetBIOS Remote Machine Name Table displayed showed a group name
matching the NetServer name. Checking the PC configuration verified
the Windows Workgroup name was the same as the NetServer. This is not
allowed by the NetBIOS over TCP/IP specification. In V5R1M0, this
portion of the code was rewritten to follow the NetBIOS over TCP/IP
specification more closely, and this is the reason the problem was
exposed with the upgrade to V5R1. The changes were intentional and
this is working as designed, in accordance with the specification. To
resolve the problem, the Windows Workgroup name on the PCs was
changed.

[CRPence]

Was the recovery procedure for RC13 followed as suggested?

Regards, Chuck
--
All comments provided "as is" with no warranties of any kind
whatsoever and may not represent positions, strategies, nor views of my
employer

comp.sys.ibm.as400.misc wrote:
> I tried to configure a Windows system to AS400 for sharing directory ,
> after configuring recycled the NetServer, but encountered the

> following error:
>
> msgCPIB683 rc5 rc3420 "The required iSeries NetServer job QZLSSERVER

> was unable to start because of reason code 5."

> 5 - Start of the NetBIOS over TCP/IP failed with return code 3420.

> Recovery: Complete recovery for the specified reason code.

> 5 - Start iSeries NetServer with the reset option using the Start
> Server (QZLSSTRS) API. If the problem continues, restart TCP/IP with
> the End TCP/IP (ENDTCP) and Start TCP/IP (STRTCP) commands.
> Note: This may affect other users. If the return code is 3420,
> see the recovery for reason code 13. If the problem continues,
> contact your service provider.