iSeries NetServer will not start and returns error code 3420

15 pts.
Tags:
AS/400 networking
Error 3420
i5/OS NetServer
iSeries error messages
NetBIOS
NetServer
TCP/IP
V5R2
V5R2 5 - Start of the NetBIOS over TCP/IP failed with return code 3420. Our AS400 can see our network devices (ping them with ip or PC name) and also ping www.google.com Telnet is working fine.
ASKED: December 12, 2008  9:58 AM
UPDATED: December 15, 2008  8:59 AM

Answer Wiki

Thanks. We'll let you know when a new response is added.

Did you try the solution the error message recommends?
____________________________________________________________

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
_____________________________________________________________

Searching the internet I found someone with a similar issue and this was the suggestion they were given:

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.

Discuss This Question: 1  Reply

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • Steved15
    Hi If I use the command nbtstat -a 192.nnn.nnn.nnn I get a host not found answer. Steve
    15 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following