Changing IP addresses, domain wide, on Windows 2000 AD network
We have been mandated to change our entire networking IP addressing scheme, to fit into a new IP address structure of a company which has recently acquired us. We will need changes for DNS, DHCP scopes, all static IP servers and print servers, firewall routes and rule based host changes, managed switches (Avaya C460 VOIP), and a Network Appliance FAS270 filer. What would one recommend, in terms of the order in which IPs should changed? I feel doing domain controllers last would be good, so that one can do as many IP changes as possible via web browsers (switches and Netapp), while still on the domain, before losing connection, without going to console sessions. Maybe this is not the case, and another approach should be used. Also, what things should we look out for, so that the IP migration goes as smoothly as possible?
Software/Hardware used:
Software/Hardware used:
ASKED:
April 22, 2005 9:08 AM
UPDATED:
April 25, 2005 1:57 PM
Answer Wiki:
Hi there
When you say managed switches are you using any VLANs?
One advice change the lease period on your DHCP server from whatever is set to to a very short time at least one week before you start the task other wise you will have to wait until the lease time expires or yourself manually releasing and renewing on every single workstations.
always decide what IP addressing you will be giving to your servers so start at the top (servers first) by doing that your clients will be able to login and get on with thier jobs (may be no internet and mail for a short while), second update your firewall (internal interface then anyrule you set
The DCs need to be approched another way as you need to get on the dns console and update some properties on the SRVs
It is hard to do I've done it many times there is no best approach depends on the structure of your network.
To see all answers submitted to the Answer Wiki: View Answer History.
First step is to apply the new IP addressing structure as secondary/additional (depending on the vendor definition) so that the two networks overlay one another, and you don’t lose connectivity to anything during the migration.
Then proceed as suggested above by ramheka
Once you have most of the work accomplished, then set sniffers at various points in the network to check for non-compliant addresses so that you can go back and catch the systems that fell through the cracks – and there are ALWAYS some.
Bob