Re: iSeries netserver wont start V5r4 -- MIDRANGE-L

Our dns & dhcp are handled by the isp (they manage the router/firewall).There are nowin servers in the network. Not sure what happened, but IBM Support had usaddthe netserver name ("Q" and the system name) to the Host Table - andstrtcpsvr *netsrvand it worked. It seems like that should have been in there all along. Thiswas set upyears ago and has always worked. Don't know if the entry suddenlydisappeared or

if our isp changed something in dns.
jim franz

----- Original Message -----From: <rob@xxxxxxxxx>

To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Monday, November 13, 2006 10:23 AM
Subject: Re: iSeries netserver wont start V5r4

You have one or more DNS servers in your network.  When you take the
system name that you have configured in your NetServer iNav stuff and
bounce it up against one of these DNS servers it is coming up with that
bogus IP address.  We added a new lpar called GDIHQ2.  We had an old lpar
that never got configured registered in the DNS as a different name.
Forgot about that until Mimix consultant tried to ping GDIHQ2 and came up
with a funky IP address.  He rebooted his PC and came up with the right
one.  Instead of simply relying on the "short term corrective action" I
did alert the network people and they found that, yes, we did have GDIHQ2
registered twice, with different addresses.

Happy hunting.

Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





"Jim Franz" <franz400@xxxxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
11/13/2006 10:15 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
<MIDRANGE-L@xxxxxxxxxxxx>
cc

Subject
iSeries netserver wont start V5r4






Has worked fine for months since v5r4 upgrade.
IPL over weekend & netserver not started
Message ID . . . . . . :   CPIB683       Severity . . . . . . . :   40
Message type . . . . . :   Information
Date sent  . . . . . . :   11/13/06      Time sent  . . . . . . : 10:00: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 209.215.39.23 is invalid.

This address not in our network, & not on our iSeries.When I look at
Netserver config in Ops Nav - no mention of ip address.
The 209 # is a number at our isp - Bellsouth, but not their dns server.

Where does Netserver retreive this from?

jim franz

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
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) mailinglist

To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.