DHCP migration from 2k to 2k3 – No new IP leases

[JBL312]

Hello,

I’m in the process of migrating services from a computer running Windows 2000 Server to one that is running Windows Server 2003. After following the steps in Microsoft Knowledge Base article 325473 (

http://support.microsoft.com/?kbid=325473),

the 2003 server is not handing out IP addresses. The Knowledge Base article had me disable the DHCP service on the 2000 server, so none of my clients are able to get a new IP when they need one.

Note: The Windows 2000 server that I migrated DHCP from is a domain controller. The Windows 2003 server that I migrated DHCP TO is a domain controller.

Any ideas about how I can get this going would be greatly appreciated.

 

[58sniper]

Is the DHCP scope active? Anything in the event logs to indicate a problem?

Pat Richard, MCSE(2) MCSA:Messaging, CNA(2)

 

[pagy]

Check the dhcp audit logs, c:\windows\system32\dhcp.
Check the obvious , is the dhcpserver service running on the 2003 box?

 

[jrbarnett]

Has the DHCP service been authorised in Active Directory?

John

 

[JBL312]

All,

I appreciate the replies. To answer your questions…

The DHCP service is running.
The DHCP service have been authorized.
The scope is active.

I will check the log’s when I get into work and go from there.

Is there something that I need to do on the client side to tell it “Alright, I know you got an IP lease from DHCP server 1, but that server no longer exists. What you need to do when you try and renew your lease is look for a different server.” Or perhaps on the server it’s self some way of telling it “Alright, here’s the deal. You have inherited a scope from another server, and when the clients need to renew there IP’s there going to try and do that with another server. You need to get out there and let them know that you have taken over, and they are going to have to get there IP’s from you.”

 

[58sniper]

Well, there could be an issue with the scope itself. If you do an ipconfig /release and ipconfig /renew on a workstation, it does a broadcast to find a DHCP server, so it should see your new server. If it's not getting an address, try adding another scope and disabling the first. See if that works. If it does, then there is likely some sort of issue (like database corruption) for the first scope.

Pat Richard, MCSE(2) MCSA:Messaging, CNA(2)

 

[JBL312]

Alright, I figured out the problem…me!

There is a difference between activating the scope and authorizing the server in active directory. You know this, you asked me about it, I said it was taken care of and it turns out that it was not. That was the problem.

The DHCP help file has a checklist for setting up the DHCP server, I should have used it in the first place.

I appreciate the help,

Ryan