Possible explaination.... I had similar behavior when I upgraded a client with a single server to a newer/faster machine. I initially cloned the original disk to the new server and let 'plug and play' do its thing with the differences in hardware. This included a new network card (among other things). All went well except the authorization of the DHCP server at its previous settings. I did many of the things you did, deleting the old scope, even uninstalling DHCP altogether and re-installing.
It didn't work again until I modified the original IP from 192.168.100.254 to x.x.x.253. My thoughts at the time were that the original DHCP installation 'registered' more than just the host's IP info into the AD but also info relating to the NIC (possibly the unique MAC address). I also guessed that I couldn't properly remove the previous settings once that card was not part of the system. I suspect that in the process of your Re-Creation of your server to a DC that something in the AD still thought of your DHCP server's IP with a different NIC was still registered within its guts somewhere. So I agree with others, in hindsight we might guess, but no one can tell us what the problem is. Just go with what works and get on with the next issue. Be Pragmatic! Good luck. drew sweeney ------ You are subscribed as [email protected] Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe send a blank email to [EMAIL PROTECTED]
