Re: NetServer Configuration

Thanks -- this seemed to do the trick.  I re-configured it with the
wizard and removed all references to WINS.

The performance seems very slow, so I am going to install the PTF's
passed along by Mr. Dietz over the weekend.

Take care!


>>> steve_landess@hotmail.com 01/21/03 06:03PM >>>
Tom -

I have a 170 running V5R1M0 with 5722999 (Licensed Internal Code) cum
TL02134 and 5722SS1(OS/400) cum TC02134.

When you configured Netserver using the wizard, did you specify a WINS
server?  A couple of weeks ago, I tried to configure mine to use WINS
and
got the same error that you are getting.

I just tried it again, by using Ops Nav to change the properties of
Netserver to use WINS, specifying my WINS server (10.0.0.30) as the
primary
WINS server.  When I stop & try to restart Netserver, I get the
CPIB683
message with the same reason code (5) and return code (3420).

When I change it back to _not_ use WINS, Netserver started.  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 setup
in
Netserver.

I hope that someone else can shed some light on why this fails.  In
the
meantime, I just left the WINS option blank in Operations Navigator
setup...

Steve Landess
Austin, Texas
(512) 423-0935


----- Original Message -----
From: "Tom Jedrzejewicz @ San Pedro" <TJedrzejewicz@contessa.com>
To: <midrange-l@midrange.com>
Sent: Tuesday, January 21, 2003 6:13 PM
Subject: NetServer Configuration


> Greetings!
>
> I have to get the NetServer running, and am having some issues.  Any
> help would be appreciated.  820-249C, V5R1, current Cum
>
> I followed the configuration wizard from OpsNav, and it all took
fine.
> However the server will not start and the following message is sent
to
> QSYSOPR.  Any ideas?
>
>                          Additional Message Information
>
>
>
>  Message ID . . . . . . :   CPIB683       Severity . . . . . . . :  
40
>
>  Message type . . . . . :   Information
>
>  Date sent  . . . . . . :   01/21/03      Time sent  . . . . . . :
> 15:01:55
>
>
>  Message . . . . :   AS/400 Support for Windows Network Neighborhood
> (AS/400
>    NetServer) was unable to start.
>
>  Cause . . . . . :   The required AS/400 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
>
> More...
>
>
>
> >>> joepluta@PlutaBrothers.com 01/21/03 03:03PM >>>
> Alrightie.  I'm ready to start.  I think.
>
> Here's what I found in the upgrade package:
>
> 1. OS disks: I_BASE_01, L_2924_01/02, B_2924_01-05
> 2. PTF disks: C2134510_01-03
> 3. Four separate plastic bags with single disks:
>    A. 5722AC3 Crypto Acc Prov 128-bit
>    B. 5722CE3 Client Encryption 128-bit
>    C. 5722CR1 Cryptographic Support
>    D. 5722XW1 Client Access Family
> 4. 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
>    E. 5722SS1 Operating System 400
> 5. Separate loose disks:
>    A. iSeries Installation Estimation
>       PTFs for V4R4 and V4R5 (?)
>    B. iSeries Operations Console Update
>    C. iSeries 400 Setup and Operations
> 6. Finally, WDS/400
>    It's an empty packing bag, but there's a set of
>    disks for Development Studio Client
>
> I also got one big black and reddish striped envelope with a bunch
of
> software keys, and a smaller black and red striped envelope with a
> bunch of
> license agreements.  There's also a getting started guide.
>
> I think I'm ready, but a couple of things bother me.
>
> 1. C2134510?  Isn't that like, May of 2002?  I guess I should
> immediately
> order more PTFs, eh?  And group PTFs, too, right?  And maybe have
them
> on
> hand BEFORE I begin the upgrade?
>
> 2. I don't use Operations Console.  My machine thinks it does.  It
> always
> gives me an A900 error while its running, because it's just not
happy
> with
> my dumb terminal console.  Could this cause a problem during
upgrade?
>
> The empty bags scare me a little, and I don't like the age of the
> PTFs.
> Other than that, I look ready to roll.  Comments?
>
> Joe
>
> _______________________________________________
> 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/mailman/listinfo.cgi/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.
>
> THIS MESSAGE IS INTENDED ONLY FOR THE USE OF THE INDIVIDUAL OR ENTITY
TO
WHICH IT IS ADDRESSED AND MAY CONTAIN INFORMATION THAT IS PRIVILEGED,
CONFIDENTIAL AND EXEMPT FROM DISCLOSURE UNDER APPLICABLE LAW.  If the
reader
of this message is not the intended recipient, or the employee or
agent
responsible for delivering the message to the intended recipient, you
are
hereby notified that any dissemination, distribution, copying,
downloading,
storing or forwarding of this communication is prohibited.  If you
have
received this communication in error, please notify us immediately via
email
and delete the message from your computer files and/or data base. 
Thank
you.
> _______________________________________________
> 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/mailman/listinfo.cgi/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.
>
_______________________________________________
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/mailman/listinfo.cgi/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.

THIS MESSAGE IS INTENDED ONLY FOR THE USE OF THE INDIVIDUAL OR ENTITY TO WHICH 
IT IS ADDRESSED AND MAY CONTAIN INFORMATION THAT IS PRIVILEGED, CONFIDENTIAL 
AND EXEMPT FROM DISCLOSURE UNDER APPLICABLE LAW.  If the reader of this message 
is not the intended recipient, or the employee or agent responsible for 
delivering the message to the intended recipient, you are hereby notified that 
any dissemination, distribution, copying, downloading, storing or forwarding of 
this communication is prohibited.  If you have received this communication in 
error, please notify us immediately via email and delete the message from your 
computer files and/or data base.  Thank you.