RE: NetServer Not Starting -- MIDRANGE-L

The QZLSSERVER job is *not* running. From the History (DSPLOG):

Job 265084/QPGMR/QZLSSERVER started on 08/26/09 at 10:57:03 in subsystem QSER
iSeries Support for Windows Network Neighborhood (iSeries NetServer) was unab
iSeries Support for Windows Network Neighborhood (iSeries NetServer) CROW end
Job 265084/QPGMR/QZLSSERVER ended on 08/26/09 at 10:57:04; 1 seconds used; en

F1 on the last entry:

Message ID . . . . . . : CPF1164 Severity . . . . . . . : 00
Message type . . . . . : Completion
Date sent . . . . . . : 08/26/09 Time sent . . . . . . : 10:57:04

Message . . . . : Job 265084/QPGMR/QZLSSERVER ended on 08/26/09 at 10:57:04;
1 seconds used; end code 0

X.
Cause . . . . . : Job 265084/QPGMR/QZLSSERVER completed on 08/26/09 at
10:57:04 after it used 1 seconds processing unit time. The job had ending
code 0. The job ended after 1 routing steps with a secondary ending code of
0. The job ending codes and their meanings are as follows:
0 - The job completed normally.

After STRTCPSVR *NETSVR, the QSYSOPR message queue has:

iSeries Support for Windows Network Neighborhood (iSeries NetServer) was
unable to start.
iSeries Support for Windows Network Neighborhood (iSeries NetServer) CROW
ended.

Detail on the first message shows:

Message ID . . . . . . : CPIB683 Severity . . . . . . . : 40
Message type . . . . . : Information
Date sent . . . . . . : 08/26/09 Time sent . . . . . . : 09:22:33

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 13. See the following reason codes and
their meanings:

13 - The retrieved host IP address of 216.8.179.24 is invalid.

I have no idea what 216.8.179.24 is.

I compared the configuration of NetServer on the Test box (which, once again, is the one with the problem) and the Production box, which starts pretty soon after coming out of a restricted state. The differences were in the Description (3rd panel of System i Navigator's Configuration option) and the Domain (4th) panel.
Description: Test = 520 #2
Production = New 520
Domain: Test = S10EC22C
Production = S10EC28C

I do not think the Test box is overburdened. WRKACTJOB shows .7% CPU used.

This morning, before I applied the PTF's delayed and did the automatic IPL, I did get NetServer started (System i Navigator). Of course, after the IPL it was stopped. I have tried the iNav Start as well as the Reset and Start options; I have done the green screen command STRTCPSVR *NETSVR. The History and QSYSOPR messages (above) are the same for both methods. The job log for the green screen command doesn't show squat except "NETSVR server starting".

To answer, I hope, Lukas' question: On the Configuration panel #13 (Do you want to allow PC clients to locate and connect to i5/OS NetServer using WINS?) the NO button is checked on both boxes.

Thanks.

Jerry C. Adams
IBM System i Programmer/Analyst
--
B&W Wholesale
office: 615-995-7024
email: jerry@xxxxxxxxxxxxxxx

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Simon Coulter
Sent: Tuesday, August 25, 2009 6:26 PM
To: Midrange Systems Technical Discussion
Subject: Re: NetServer Not Starting

On 26/08/2009, at 5:45 AM, Jerry Adams wrote:

Any ideas what I should look for?

Find the NetServer host job (QZLSSERVER) and see if it shows anything
helpful.

Regards,
Simon Coulter.
--------------------------------------------------------------------
FlyByNight Software OS/400, i5/OS Technical Specialists

http://www.flybynight.com.au/
Phone: +61 2 6657 8251 Mobile: +61 0411 091 400 /"\
Fax: +61 2 6657 8251 \ /
X
ASCII Ribbon campaign against HTML E-Mail / \
--------------------------------------------------------------------