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

New (additional) DHCP scope won't hand out leases

I have added a 2nd DHCP scope to our existing Windows 2000 DHCP server so that the current production scope can be disabled (we are moving to a different IP range with more host addresses).  When I disable the currently running scope and enable the new one, none of the DHCP clients are able to get a new lease.  
0
vilasnair
Asked:
vilasnair
3 Solutions
 
adnanmigCommented:
Hi,

did you configure the ip-helper address in your router?
please put your config here.

regards,
0
 
MikeKaneCommented:
Is the dhcp on the same subnet as the clients?  Did the clients have a lease that runs out or was it set to permanent?   If you are at a client and run an IPCONFIG /release and then IPCONFIG /renew does the client get a good address or an error message?

0
 
vilasnairAuthor Commented:
Thanks for the quick responses.  I will try to answer all the questions in this posting.

I made no changes to the router although my office network is completely flat (no vlans or other segmentation) and the DHCP server already hosts a scope that is handing out leases properly.

The DHCP server is on the same subnets as the clients (again, the network here in the office is flat). The lease length for the current scope is 7 days but I did try to release and renew DHCP on a test client and the request times out.

Thanks!
0
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

 
netnounoursCommented:
The server must receive DHCP requests on a NIC that is in the same IP subnet than the scope.
So, you will need to either set an ip helper in your router or set a second nic on your server with the matching ip address (I am not sure that assigning a secondary ip address to the existing nic will work).

Let us know
0
 
adnanmigCommented:

Hi,

why dont you just delete the old scope and create the new one. all devices that have the old ip will keep working and the new one will get the new leases. ofcourse, your router interface should have secondary ip from the new scope.

regards,
0
 
vilasnairAuthor Commented:
I was finally able to get it working.  I changed the IP to an address in the new subnet and after a reboot it began to hand out leases properly.  

Netnounours, I did try adding a second IP address to the existing NIC and it did not help.  Just so you know.

Thanks everyone for their help!
0

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

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