Well, I've accomplished something today, anyway. Got both you and Scott confused, a daily double.

Option 12 had:

Change TCP/IP Domain (CHGTCPDMN)

Host name . . . . . . . . . . . HOSTNAME 'BNW400'
Domain name . . . . . . . . . . DMNNAME 'bnw.com'

I think bnw.com used to belong to us, but was, I guess, given up after we moved from the Model 720 to the 520's. I copied the set-up on the 720 to the 520's. If you bring up bnw.com in a browser, it's apparently up for sale. Pinging either CROW or S10EC28C returned the 216 address.

I changed the DMNNAME to bwwholesale.com, which is out on some ISP somewhere. Now pinging CROW or S10EC28C returns "Unknown host." BUT Netserver started.

Changing the lookup priority from *Remote to *Local, by the way, did not have any effect.

I'm pretty sure that the Production box is flummoxed, too. If I ping CROW or S10EC28C from it I still get the 216 address. Oddly Netserver, as I said, comes up pretty quickly when it returns from a restricted state. But I would like to change Production, too, to bwwholesale.com. Bearing in mind that we are pretty much a closed environment here (i.e., the network in solely within these four walls, no remote sites, no remote access to the System i's from outside the building), and that things have been working for years on Production with bnw.com,
1) Would it be a could idea to "fix" the production box, and
2) Can I do this during the day (i.e., while orders are coming in)?

The issue may never have arisen with Production because I always use the Test box for outside access (PTF's and such) and later FTP them to production using an explicit address (10.0.0.2). Same when I ftp the nightly save files from Production to Test: I use Test's explicit address, not its name.

I think Scott is right: We need to pay someone to fix this. The operative word is "pay". Not likely to happen any time soon.

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 rob@xxxxxxxxx
Sent: Wednesday, August 26, 2009 11:43 AM
To: Midrange Systems Technical Discussion
Subject: RE: NetServer Not Starting

Change your netserver name. If you PING S10EC22C (or the other one - now
you have me confused) you're ending up with 216.8.179.24.

1 - Change your netserver name to match your i name. Verify that a ping
of the new netserver server name and a ping of the new netserver server
name concantenated with the netserver domain name both work - and return
the IP address of your i.

2 - Make sure you don't have an errant dns or host table entry that
returns 216.8.179.24 for whichever one you are pinging (S10EC22C or the
other one).

Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.