asked on

IP Address Change on Network

I am Changing the IP Addresses on our network this weekend to a Private IP Scheme. We are going from 1.x.x.x to 10.x.x.x. We are on a Server 2003 Domain and AD. We only have one location and one domain. I was planning on starting with the Domain Controllers by changing the IP's and then doing a 'ipconfig /flushdns' and 'ipconfig /registerdns'. Then maybe going to the file-server; exchange server; print server; etc, then also doing a 'ipconfig /flushdns' and 'ipconfig /registerdns'. I have to change the IP on the printers as well. All desktops and laptops will get their IP's from DHCP from the routers DHCP server, which will be updated as well. We have about 8 servers and 35 desktops/laptops. Does anyone have any advice on how to minimize any problems or suggest a better order of operations? I am starting Saturday afternoon and hope to be finished in half a day. Nobody will be back in the building until Monday morning.

SOLUTION

Don S.

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Michael McGuire

ASKER

Forgot to mention that I am putting in a new Firewall/Router that I have already configured with the new DHCP Server containing the new IP Scheme and DNS as well. On my domain Controller would I have to create a new Reverse Lookup Zone or would it be created automatically once I ran the Ipconfig /registerdns from the domain controllers?

ASKER CERTIFIED SOLUTION