Discussion Locked

Need to change IP address on PDC

0 helpful
8 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I currently have a domain with 2 different subnets. The primary subnet (10.4.x.x) has 2 domain servers, 1 PDC and one BDC. The secondary subnet (10.5.x.x) has another BDC. I am joining both subnets. I've already moved all client PCs over to the target subnet (second: 10.5.x.x). Now I need to move my PDC and BDC for the 10.4.x.x subnet over to the 10.5.x.x subnet.

It would be so much easy to just change the IP of the PDC and reboot it but I know it's not that easy.

I've read about demoting PDCs and promoting it back to PDC status after the IP change is in place but I need a confirmation on this:

In my current scenario, will there be any problems if I promote my BDC (on the 10.5.x.x subnet) to PDC status (thus demoting the PDC), change the IP address of the old PDC, bring it back up into the new subnet then promote it back to a PDC?

Changing IP on the other BDC should be easy.

BTW: all three servers run identical copies of DNS and WINS services.

8 replies

by snapp1337

Actually your idea of demoting the current PDC and promoting your BDC on the 10.5 network is the best idea. Then reset the IP of the current PDC to the 10.5 network and then promote it back to the PDC level. This has worked for us with no problem. Good Luck!

by nettek

The IP address of a machine on your network is irrelevant to its status (PDC, BDC, member server, or NT workstation). You do not need to demote a PDC to a BDC to change its IP address. In fact, you could set your PDC to take its address from a DHCPserver (if you were not using DNS), in which case its address would constantly be changing.

All you need to do is delete the WINs entries for your servers, re-enter the appropriate entries in your DNS servers, change the IP address on the server (don't forget to change the WINS server settings to point to the new IP address) and reboot.

by psx

Hrmm...this sounds interesting. I always thought that changing IP on a domain server is not a big deal but what about trust relationships? NT4 is very picky about this. In fact, I did go through with the above scenario and I had a bunch of weird problems (I demoted the PDC, change its ip address, then promoted it back to PDC status).

First of all, I have 2 other BDCs. One of the BDC (somehow) lost its trust relationship (probably because I also changed its IP during the move). Lots of problems with WINS resolution because I ran WINS service on all 3 servers (and all PCs in the domain use one of the 3 as their primary WINS server). I had to clear out all WINS entries, wait for the scavenging process to complete, then replicate the databases amongst the three servers. On top of that, the NAV for Exchange service failed to start on my Exchange server (the 2nd BDC). This service should not be dependent on the server's IP but somehow it failed and couldn't be restarted. I fixed this problem by unintalling and reinstalling the software.

Needless to say, the whole process was a huge headache. It sounds very easy but many things could go wrong (and in my case, they did) so if you are trying to attempt this, plan it out. Look at all the things that could go wrong and try to solve them ahead of time. With Microsoft products, you never know what could happen...

BTW: I am keeping this thread open for one more week then I will award points.

This discussion is closed to new replies.