The network I just inherited has a 192.168.1.0 scheme that causes no end of headaches for VPN users. I've been tasked with getting this changed sooner than later - but I've never touched true "networking" on this scale and have only ever
administered a network - not configured one. It's generated a lot of questions for me and I was hoping someone could direct me to resources that can help.
I've found a number of posts here with a lot of helpful information, but still have some (quite a few) blanks that I need to fill in. My biggest concerns are that I'll make a change somewhere and find myself unable to access that system to correct
it, or that I'll run into an issue where everything should be working but it just isn't.
We have a primary network (192.168.1.x, Small Business 2003 (planning to move to 2008/2012 before April)) and multiple sites external to that, connected via VPN through their firewalls. Each site has it's own backup domain controller. I'm planning
to undertake an IP conversion at the smaller sites first to see how well I handle it and build on what I do there if it's feasible.
The sub-sites have very simple networks - just the backup domain controller, a firewall, and a switch for the most part. The primary site has a larger server room and multiple buildings connected to it directly.
For the sub-site TestA I think my order of operations is (please let me know if I've got this wrong):
Pre-Project:
- Plan my change - I've got my scope picked out and will assign each device a new IP on paper before I ever launch.
- Check DNS and DHCP scopes for devices that have been manually configured and document them.
- Add firewall rules to all sites to route traffic to my new IP range across the VPN, duplicating the existing rules so I can reconnect as I work.
- Set my domain DHCP rules to refresh every 2 hours a couple days before.
Project Start:
- Change static IP of the site Backup Domain Controller on the NIC. I imagine this will reset my connection to the server and I'll need those firewall rules to let me get back in.
- Restart DNS and NetLogon services.
- Open cmd and run ipconfig /flushdns as well as ipconfig /registerdns
- Open DNS and check domain zone properties > Nameservers and make sure the new IP is listed; remove old one as needed and manually recreate if required.
- In DNS, clean out any old IP references to the SiteA devices.
- In DNS, create a new Reverse Lookup zone for the SiteA IP.
- In DNS, delete old Reverse Lookup Zone.
- Open DHCP, create a secondary DHCP scope that covers my new 10.74.21.x IP range and after ensuring it's a good duplicate, delete the old one.
- Update Firewall IP Address
- Check ports and routing on firewall and update as required (should be pre-planned and documented)
- Ensure other locations are using the new IP Address for SiteA in their DNS > Zone (r-click) Properties > NameServers tabs
- Clean out old Firewall rules from Pre-Project Step 3 that should now be obsolete.
- Test internet and server connectivity from SiteA Server.
- Check Active Directory Sites and Services on primary Domain Controller and Add the new site as needed.
- Update static IP addresses devices for servers.
- Run ipconfig /registerdns on servers as needed
- Update static IP addresses for computers, printers, devices
- Update static IP addresses and rules on routers and switches
- Log in as a user, test AD, test printing
Questions:
- My How well will I be able to work on devices with dissimilar IP addresses? If I've changed the Domain Controller IP to 10.73.21.x will I have trouble connecting to other devices on the network using their old 192.168.1.x IP's? Logically this
seems like it has to work, since - you know - the internet works - but some part of me is afraid that when I switch the IP on the Domain Controller, I'll be locked out of every other device on the network.
- I'm not sure how to maintain the link between sites. I was in the Active Directory Sites and Services list on the Primary Domain Controller, but couldn't make adjustments to SiteA's displayed IP of 192.168.2.0/24. Will this simply auto-update
itself - I have a step to recreate this, but I haven't researched how that works or exactly what it does.
I appreciate any feedback or help provided. This is new territory for me and I really want to nail it as best as I can.
Once I get through the first remote site, I plan to duplicate the process on the others and then return to the main site and handle it like the remote sites but on a larger scale with more switches/routers/PC's.
Thank you!
Edit: I also found this today: http://blog.geek4god.net/2011/01/windows-domain-ip-scheme-change.html and am looking through it.