Home > Return Code > Return Code 3420

Return Code 3420

Thanks. This error indicates there is another computer on the network already using the name configured for the IBM i NetServer. The changes were intentional andthis is working as designed, in accordance with the specification. Unexplained Return Codes can be displayed with DSPMSGD CPEnnnn (for example, for RC3021 use DSPMSGD CPE3021). this contact form

Amendments 2001—Subsec. (a)(2). We'll email youwhen relevant content isadded and updated. The message we get is CPIB683 with reason code 6. Following Follow NetBIOS Thanks! http://publib.boulder.ibm.com/html/as400/v4r5/ic2989/info/RZAHLTIP2.HTM

If the return code is 3420, see the recovery forreason code13. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Please try again later.

Help text for the error reads: If the return code specified is 3435, check that your network's Primary WINS server is functioning properly. When you configured Netserver using the wizard, did you specify a WINS server? We'll email youwhen relevant content isadded and updated. See the following reason > codes and their meanings: > > 1 - Unable to retrieve user credentials. > > 2 - Unable to retrieve credentials. > > 3 - Exchange

A port scanner can cause orphaned TCP/IP connections that need to be cleaned up by ending and restarting TCP/IP. Complete the following steps to solve the problem. Don’t miss out on this exclusive content! CPIB683 RC5 RC3406 This RC indicates a timing problem in which the QSERVER subsystem isn't active (or isn't finished starting) when the NetServer attempts to start.

A timing problem can be confirmed by reviewing the QHST History log. Error 3420 indicates there is a name conflict on the network.The NetServer name was configured to be the same as the iSeries systemname which should work. Recycling QZLSFILE jobs followed by starting NetServer with a reset might correct the problem. RC3435 Cannot reach the destination network.

Use of the archive is restricted to research of a business or technical nature. Additionally, if there are no QZLSSERVER messages in the history log but the NetServer is set to start with TCP, then the QSERVER subsystem was not started before TCP attempted to Following Follow i5 Thanks! If changes have recently been made on the DNS, check to be sure that a valid IP address is listed there for the NetServer name.

In testing, the name was changed to another name and NetServer started successfully. weblink In this case, the IP address should be corrected and the NetServer restarted to resolve the problem. I'm puzzled as to why this causes an error, but in my case my PC's can still see the AS/400 in network neighborhood, so it's not critical that I have this o Check for QZLSSERVER joblogs for errors (WRKSPLF QPGMR).

  1. For information on taking the trace and/or dump, refer to the links in the section below called Check the Following Additional Items.
  2. Does anyone know the greenscreen equivalent of the reset and restart for Netserver?The error message is below:Message ID . . . . . . : CPIB683 Severity . . . .
  3. A smaller value might cause NetServer to fail to start with a RC6 RC3423.
  4. Isn't that like, May of 2002?

See the following reason codesand theirmeanings:1 - Unable to retrieve usercredentials.2 - Unable to retrievecredentials.3 - Exchange user profilefailed.4 - Unable to obtain lock for service program QZLSSRV1 in libraryQSYS.5 - o Current IBM i NetServer PTFs are applied. Ibm says that this problem is repaired with PTF SI15797. navigate here Send me notifications when members answer or reply to this question.

WRKACTJOB SBS(QSERVER) can be used to determine the status of the job. IBM i NetServer ends normally after being started. Etymolus 2003-10-16 20:46:04 UTC PermalinkRaw Message Post by Tom HFor the past few weeks whenever we IPL Netserver has been unable tostart.

RC3448 The protocol required to support the specified address family is not available at this time.

CALL QZLSENDS PARM(x'00000000') CALL QZLSSTRS PARM('1' x'00000000') If still no success, contact Support for assistance in collecting a TASKINFO dump. In V5R1M0, thisportion of the code was rewritten to follow the NetBIOS over TCP/IPspecification more closely, and this is the reason the problem wasexposed with the upgrade to V5R1. If the problem continues, contact your serviceprovider.    7 - Use the Display Message (DSPMSG) command to see messages inthe  QSYSOPR message queue related to resource sharingfailures.    8 - Contact Search IBM i Support for message IDs (CPIB68x RCx) because new Technotes are added as new errors and causes are discovered.

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 TCP/IP is not active, the TCP/IP interface is not defined, or the interface is not active. If the problem continues, contact your serviceprovider. his comment is here Bengt Persson 2003-10-16 18:33:26 UTC PermalinkRaw Message Green Screen stuff for Netserver can be found here:http://www-1.ibm.com/servers/eserver/iseries/netserver/Look for "API mini Guide" or "Go Nets".--BengtPost by Tom HFor the past few weeks whenever

Following Follow AS/400 networking Thanks! It can be caused by a TCP/IP address conflict in the Domain Name Server (DNS) or WINS Server entries for the IBM i system name or the NetServer name. If you have questions about this, please contact Re: NetServer starting problem From: CRPence Date: Fri, 01 Feb 2008 11:48:52 -0600 Was the recovery procedure for RC13 followed as suggested? Thanks.

RC16 generally indicates a name conflict between the NetServer name and something else on the network. Afterthe QSERVER subsystem is started, start the iSeries NetServer usingeitherthe Start Server (QZLSSTRS) API or the Start TCP/IP Server(STRTCPSVR*NETSVR) command. If NetServer is not active, there should not be any NetBIOS nor CIFS jobs under the Local Port column. Note: This may affect otherusers.

Verify the name and TCP/IP are correct on the DNS server and/or WINS server. yes no add cancel HOME | ABOUT US | CATALOG | CONTACT US | ©2017http://www.rssing.com Jump to navigation Cornell University Law SchoolSearch Cornell Toggle navigation Support Us! Cross reference information Segment Product Component Platform Version Edition Operating System IBM i 6.1 Operating System IBM i 7.1 Historical Number 371183307 Document information More support for: IBM i Host Servers Ask Question Free Guide: Managing storage for virtual environments Complete a brief survey to get a complimentary 70-page whitepaper featuring the best methods and solutions for your virtual environment, as well

For OS V5R4 V5R4M5 V6R1 V6R1M1 V7R1, see APAR MA42411. Please try again later. If the problem continues, restart TCP/IP with theEndTCP/IP (ENDTCP) and Start TCP/IP (STRTCP) commands. In the NetServer Properties, change the Logon Server Roll from Server to None.

The default is 0. Five other plastic bags with no disks > A. 5722QU1 Query > B. 5722ST1 DB2 and SQL Dev Kit > C. 5722PT1 Performance Tools > D. 5722SS1 Base Pubs Kit > Search form Search About LII Who We Are What We Do Who Pays For This Contact Us Get the law Constitution Supreme Court U.S. RC3500 Object is a read only object.

A resource is temporarily unavailable. The NetServer name was configured to be the same as the iSeries system name which should work. However it can be the same as the System i name (for the system on which it exists). o From an operating system command line, run NETSTAT *CNN.