× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Jerry,

That's right, DNS will associate the IP addresses with the host names.
Keep in mind that on some machines for various reasons people (users and 
admins) add entries to the host file (on Win NT/2K/XP is here: 
C:\WINDOWS\system32\drivers\etc\hosts (if you installed your win to the 
default drive/path)). 

This can be confusing as Windows will check for the host file for the IP 
address if you want to connect to a host (by name).
So on a PC if it is something different than your DNS entries you may have 
a problem on that workstation.

Peter
 



Jerry Adams <jerry@xxxxxxxxxxxxxxx> 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
16/10/2006 15:03
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
Midrange-L <midrange-l@xxxxxxxxxxxx>
cc

Subject
Switching ID's






We have two [2] 520's.  One is production; the other is our backup 
system.  Both are single partition.  There are 20 - 30 workstations and 
about the same number of printers.  The workstations are primarily PC's 
using iSeries Access for Windows; we have a few twinax workstations 
(including the system console).


So far we (knock on wood) haven't had to use the backup system for 
production.  Someone had the radical idea, however, that we actually 
needed a disaster recovery plan.  I need a little (?) help with an 
aspect of the plan.


For this phase we are assuming that the damage is isolated to the 
production box (SystemA); that there is no structural damage to the 
environs; that everything else is copasetic.  I port the configuration 
from SystemA to SystemB (the backup) in a save file (SAVCFG) 
automatically every night.  (Forget to mention: Both boxes are supposed 
to be identical in all regards.)  Security data (SAVSECDTA) is, also, 
pushed to the backup in a save file.


My question relates to user access via iSeries Access for Windows.  Each 
PC user's IAW is configured to identify SystemA as the system to which 
they will access programs and data.  Even though there are "only" about 
20 PC's attached this way, I would rather not set up a connection to 
SystemB and, then, change each PC to access the backup system.  Instead, 
I would rather change the identifier on the system (520) itself.


It looks like CHGNETA can be used to rename the systems.  Is this all 
that I need to do?  Or do I, also, need to change the IP address for the 
box?  I seem to remember that there is a server somewhere that says, "IP 
address 10.0.0.4 = SystemB" etc.  Is that the Domain Name Server (DNS)? 
And would I need to change that, too?


Thanks.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.