tadlocks
asked on
I'm having trouble transferring DHCP settings from one server to another
In preparation for rebuilding a failed drive array on a server, we need to shift DHCP from that server to another. Both are Windows 2003 servers at the same service pack level.
I tried this, in this order:
1. Configure the destination server with the DHCP role. Disable the DHCP service on the destination server and reboot it.
2.. On origin server, entering "netsh dhcp server export C:\dhcp.txt all" on the command line. Copy dhcp.txt from the origin server root to the destination server root.
3. Immediately stopping the DHCP server service on the origin computer.
4. On the destination server, entering "netsh dhcp server import C:\dhcp.txt all".
5. Enabled the DHCP service on the destination server and rebooted. Verified the service was running and set for automatic startup.
6. Accessed the DHCP console on the destination server and authorized the server.
All of the scopes and reservations and existing leases transferred just fine but the durn thing won't hand out new leases!
Anyone know what I'm missing, here?
I tried this, in this order:
1. Configure the destination server with the DHCP role. Disable the DHCP service on the destination server and reboot it.
2.. On origin server, entering "netsh dhcp server export C:\dhcp.txt all" on the command line. Copy dhcp.txt from the origin server root to the destination server root.
3. Immediately stopping the DHCP server service on the origin computer.
4. On the destination server, entering "netsh dhcp server import C:\dhcp.txt all".
5. Enabled the DHCP service on the destination server and rebooted. Verified the service was running and set for automatic startup.
6. Accessed the DHCP console on the destination server and authorized the server.
All of the scopes and reservations and existing leases transferred just fine but the durn thing won't hand out new leases!
Anyone know what I'm missing, here?
DId you activate the scope?
ASKER
I'm pretty certain I did activate it, though I don't specifically recall doing so. I'll keep that in mind!
In addition to making sure the scope is active, you need to authorize the server as a DHCP server for the domain. Did you do that?
ASKER
Yes, I used the DHCP mmc plugin, added the server to the console and then authorized it.
I almost asked you in my first post if you had authorized it, but then re-read and saw you had. And it's showing a green up arrow, right? I'm sure it is, because you knew to authorize it :)
Any errors in the system log on the server?
ASKER
Yep, green arrow and no errors. Nothing.
Have you looked in the DHCP folder in your %systemroot%\system32 folder for the DHCP logs? I would check them for errors first. You won't necessarily see event log errors, but the DHCP logs should show you exactly what's going on.
You need to disable the other DHCP server with the same scope and address pool. The DHCP service will stop if it sees a rogue DHCP server. The old server will be viewed as a rogue server until it is removed or stopped from sending out DHCP.
One other thing, do you have windows firewall or ISA active. Those firewalls block DHCP discoveries from reaching the server.
ASKER
Thanks for the suggestions, all, but no luck. Here's my last attempt:
Destination server: removed DHCP role, rebooted, re-installed DHCP role, rebooted, skipped scope setup wizard, verified DHCP service running.
Origin server: exported DHCP settings using command noted in OP. Immediately un-authorized DHCP service, then stopped it.
Destination server: imported DHCP settings, verified scopes were activated, authorized server, re-started server, verified all systems go (by appearance).
Fired up a client computer, no IP address. Ran IPCONFIG /release and then IPCONFIG /renew on a client that had been running. still no IP address.
Nothing in logs, other than "service stopped", "service started", etc. No errors.
Everything done while logged on as domain administrator. No firewalls to impede requests.
I'm at a loss.......
Destination server: removed DHCP role, rebooted, re-installed DHCP role, rebooted, skipped scope setup wizard, verified DHCP service running.
Origin server: exported DHCP settings using command noted in OP. Immediately un-authorized DHCP service, then stopped it.
Destination server: imported DHCP settings, verified scopes were activated, authorized server, re-started server, verified all systems go (by appearance).
Fired up a client computer, no IP address. Ran IPCONFIG /release and then IPCONFIG /renew on a client that had been running. still no IP address.
Nothing in logs, other than "service stopped", "service started", etc. No errors.
Everything done while logged on as domain administrator. No firewalls to impede requests.
I'm at a loss.......
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
hypercat beat me too it. Good advice to check the DHCP logs.
ASKER
You pointed me in two directions. I hadn't set up this box and took for granted it had a fixed IP; it did not. A DHCP server cannot,naturally receive an IP address assignment via DHCP! The log told me that and after I had that fixed, the server was advertising for clients.
However, we also are running VLAN's and multiple IP segments in our building. I contacted my network guru and he "reminded" me that DHCP traffic won't cross boundaries without routing in place specifically for it. So, after he added those routes, everything worked smoothly.
Thank you.
However, we also are running VLAN's and multiple IP segments in our building. I contacted my network guru and he "reminded" me that DHCP traffic won't cross boundaries without routing in place specifically for it. So, after he added those routes, everything worked smoothly.
Thank you.