Questions

Re "IP'ing" my entire infrastructure

Tags:
+
0 Votes
Locked

Re "IP'ing" my entire infrastructure

kdyck
Hello. I am going to be leading a project to completely re-IP our entire infrastructure. We are moving from a 192.168.x.x/22 to a 172.21.x.x/16 subnet. The infrastructure is 98% Windows (2003 SP1 and SP2). Forest functional level is W2K3 as well.
We are a pretty small shop so I am not going to have to worry about different sites (we are located in one central location) I am just nervous that when I change the IP addresses of the DC's my Active Directory is going to fail. Am I safe in assuming that if I change the IP's of the DC's first and then log in locally to the other servers in the AD forest I can manually change the IP and then reboot?
Has anybody gone through this before and can offer any advise?

thanks in advance
  • +
    0 Votes
    CG IT

    and do you currently use DHCP?

    The real problem is changing IP addresses of DCs but DNS isn't updated with the new addresses. Clients won't find the DCs as DNS is giving the wrong address.

    If your a real small shop and DCs also host the DNS server and you don't run DHCP, it's just a matter of changing DC and DNS addresses and then update DNS with the changes. Then change clients addressing. Should go smoothly [but do when users aren't around].

  • +
    0 Votes
    CG IT

    and do you currently use DHCP?

    The real problem is changing IP addresses of DCs but DNS isn't updated with the new addresses. Clients won't find the DCs as DNS is giving the wrong address.

    If your a real small shop and DCs also host the DNS server and you don't run DHCP, it's just a matter of changing DC and DNS addresses and then update DNS with the changes. Then change clients addressing. Should go smoothly [but do when users aren't around].