Moving DHCP from a Windows 2000 Server to a Windows Server 2003 machine
I was wondering if I could get some advice on what would be the best way to move a DHCP server to a new box. I currently have a DHCP server still running on 2000 and I wanted to migrate it off to a 2003 box. I have tried using the DHCPEXIM tool to extra the database and move it to the new server and I exported the file using the netsh command and everything worked fine. However, after I authorized the DHCP server I was get address that was not in my scopes.
Example:
We have four scopes (10.30.26.0; 10.30.36.0; 10.30.40.0; 170.190.240.0), but I was being assigned a 192.168.1.x address.
Any help would be greatly appreciated.
Example:
We have four scopes (10.30.26.0; 10.30.36.0; 10.30.40.0; 170.190.240.0), but I was being assigned a 192.168.1.x address.
Any help would be greatly appreciated.
Hmm sorry, I see you must have used that one already.
For the invalid address assignment, check the DHCP Server IP address listed in "ipconfig /all" on the client. Could be barking up the wrong tree by looking at the import.
Chris
ASKER
Everything looks correct. Here is the steps I did.
1.) Installed DHCP on 2003 box
2.) Ran "net stop dhcpserver" on 2000 box
3.) Ran "jetpack dhcp.mdb temp.mdb" on 2000 box
4.) Ran DHCPEXIM app and saved the scopes as text file
5.) Disabled DHCP on 2000 box
5.) Moved text file to 2003 box
6.) Ran "netsh dhcp server import c:\2000.txt all" on 2003 box
7.) Authorized DHCP server
Everything looks to be correct with my scopes and reservations, but I still get that assigned address of 192.168.1.x
1.) Installed DHCP on 2003 box
2.) Ran "net stop dhcpserver" on 2000 box
3.) Ran "jetpack dhcp.mdb temp.mdb" on 2000 box
4.) Ran DHCPEXIM app and saved the scopes as text file
5.) Disabled DHCP on 2000 box
5.) Moved text file to 2003 box
6.) Ran "netsh dhcp server import c:\2000.txt all" on 2003 box
7.) Authorized DHCP server
Everything looks to be correct with my scopes and reservations, but I still get that assigned address of 192.168.1.x
That all sounds fine. The 192.168.x.x lease is definitely coming from that DHCP server?
Chris
ASKER
The thing is I don't know where. Where do I need to look on my DHCP server?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for the info. I had to roll back, but I will give it another shot and let you know.
ASKER
I am waiting for change control to go through to try it out. I will accept the answer and open a new question if I have issues. Thanks for your help.
ASKER
I found the rogue DHCP server and shut it down. After I did the migration everything looked good, but the new DHCP server was not issuing addresses. It seemed like the clients were still trying to contact the old DHCP server. Is there anything I need to do to have the clients now to contact the new DHCP server to assign IPs? Thanks.
Shouldn't be, DHCP is broadcast based.
That is, the client sends a Broadcast asking for an address, then it uses the IP address from the first DHCP server to respond.
I take it the new server is authorised in AD? Perhaps check the DHCP log file in %SystemRoot%\System32\DHCP
Chris
Hey,
There's a KB Article for this one, it covers a move from 2000 to 2003, maintaining all configuration and leases.
http://support.microsoft.com/kb/325473
HTH
Chris