DHCP Authorize/Unauthorize in AD using Netsh
Posted on 2010-11-15
Having a strange issue. I'm trying to add a new dhcp server at a site, but cannot properly authorize/unauthorize DHCP. I believe this is due to leftover baggage in AD from a previous DC with the same name/IP. When I run a netsh dhcp show server, it shows me two authorized DHCP servers at that site, but both contain incorrect information, yet one is currently authorized and performing DHCP without issue. Does AD key off the DNS name, IP address or both when authorizing a dhcp server? For example, here's what I see in AD >
Server [ChicagoDC.sub.domain.com] Address [10.28.32.47] Ds location: cn=ChicagoDC.sub.domain.com
Server [ChicagoDC1.sub.domain.com] Address [10.28.32.48] Ds location: cn=ChicagoDC.sub.domain.com
The server that's currently up and running and serving DHCP properly is ChicagoDC.sub.domain.com, but it's IP address is really 10.28.32.48 so both AD entries are technically incorrect. I could delete them both, but I'd like to avoid breaking the current DHCP server if possible.
Ultimately, I'm trying to move DHCP from ChicagoDC [10.28.32.48] to Chicago DC1 [10.28.32.49]. I know how to move it, but cannot get it to work on ChicagoDC1 due to the mixup in AD.
Any thoughts on how to clean up the incorrect DHCP info in AD?