Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

2003 DC replacing 2000 DC and taking over 2000 DC IP address

Status
Not open for further replies.

bdoub1eu

IS-IT--Management
Dec 10, 2003
440
US
Sorry about the subject above...

I am almost finished with a migration from 2000 to 2003 and I have one more 2000 AD server that I'm about to decomission.

AD has already been upgraded to 2003 using adprep and domainprep and I currently have 4 2003 DC's in the domain.

The 2000 DC has an ip of 10.3.100.16 which we have been using for years as our primary DNS and WINS server for DHCP clients. Obviously I can change this quickly on our new 2003 DHCP server but we have about 50 plant machines that have static IP's and static DNS/WINS settigs...

Bottom line, I'd like to bring the 2003 DC into production using the IP from the 2000 DC (10.3.100.16) since most everything is already pointing to .16 for DNS/WINS.

I also wanted to keep the 2000 DC online as a DC/DNS/WINS in case we need to bring it back into production, otherwise, I would just demote it, change the IP to free up 10.3.100.16 to use for the new server.

Is it as simple changing the IP on the 2000 DC to something else and applying the 10.3.100.16 IP to the 2003 DC? Will the 2003 DC register the new IP correctly and will AD like the IP change? I just didn't want there to be some records of the IP pointing to the old server that would confuse AD...

Maybe I'm overdoing this and thinking too much about it because it really is a simple thing but I just wanted to make sure before I do it.

Thanks!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top