• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 504
  • Last Modified:

Changing DHCP Servers

We have 11 clinics serviced by one data center but only 5 of them get their DHCP from us. The others have local servers. We are putting into place a DHCP server to replace the current one that is having hardware issues. I have created all the scopes and I have authorized it and unauthorized the old one. However. when I am trying to release - renew on a test machine it does not find the new DHCP server. I have even put in the Gateway router a line  (ip dhcp-server x.x.x.x) to point to the new dhcp server.

Am I missing something else? Yes I have activated the scopes and I can ping the new server, in fact I remote into the new server. I have checked any other routers and firewalls to see if they point dchp somewhere else and they do not.

Does this normally take awhile to get replicated and I need patience?
3 Solutions
djsharmaTechnical ConsultantCommented:
Run netsh dhcp show server command and see whether it is showing older DHCP server name if yes .then refer http://support.microsoft.com/kb/306925 to remove older one.
tnholtAuthor Commented:
OK - same issue but more information. The scope I need them to get is a x.x.100.x but the new DHCP Server is on the x.x.101.x subnet.

I did run the netsh dhcp show server and it had the new dhcp server showing and the old one gone. So then i did the following.

 I created a subnet for the x.x.101.x, activated and immediately got a lease. But I want them to get the x.x.100.x subnet lease for those in the local clinic.
Stelian StanNetwork AdministratorCommented:
I think you need to move the database from old DHCP server to new one (http://support.microsoft.com/kb/962355)
Make sure the DHCP Helper is configured for the interface that represents their next gateway. That can get tricky if you have VLANS in place AND it depends on what platform their gateway is, as to how it's implemented. The DHCP Helper should point to the new DHCP server's IP address. Make sure you list out the configuration of the gateway at each location to confirm that the new DHCP helper address you added isn't in addition to the original one. On some implementations (HP, CISCO) you have to remove the old entry as well as add the new one.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now