• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Avoid Windows Server 2012 R2 DHCP servers from giving IPs that are static assigned?

riahc3

Senior member
There are PC on my network that have a IP static assigned. Is there any way the DHCP server can detect a IP that has already been assigned by a client on the network and not reassign it to avoid IP conflicts?
 
There are PC on my network that have a IP static assigned. Is there any way the DHCP server can detect a IP that has already been assigned by a client on the network and not reassign it to avoid IP conflicts?

well you should have a couple of things configured

the DHCP scope should not overlap, or should have exclusions for, ranges of assigned static addresses.

that is, if your subnet is 192.168.150.0 /24, and you have static IPs assigned as 192.168.150.1-49, then you create a DHCP scope of
1 - 192.168.150.50 - 200
or
2 - 192.168.150.1 - 200 with exclusion 192.168.150.1-49 [i think this is best practice, since you can arrange exclusions to cover address range changes without having to delete/recreate the entire scope]

second, you can enable address conflict detection for the dhcp server. this will ping an IP before handing it out when a request comes in.
https://technet.microsoft.com/en-us/library/cc737924(v=ws.10).aspx

you could, if you wanted, also just let the PCs get a DHCP address, then right-click the lease in the dhcp scope and assign that pc to a DHCP reservation, so that it will only get that particular IP address assigned from the DHCP server every time it asks for an address/renewal [based on the mac address of the network adapter in the pc]
 
Put in a reservation on the DHCP server so it wont give out that IP?

I agree with both respondents. With my limited experience, I know that a server OS such as yours can be a DHCP server. So can a gigabit router, though.

Either way, you should be able to create reservations for the individual static addresses within the DHCP assignment range, or simply exclude a sub-range of addresses used for static assignment from DHCP range. I actually do it both ways with a total of 256 addresses in my subnet range, with the DHCP range beginning at 100, ending at 200. I have printers and workstations with static addresses below 100. If it had been more convenient to let DHCP assign an address to a workstation or device, I then reserve that specific address for that particular device and MAC at the router. I couldn't imagine how it would be any different if the server itself is also acting as DHCP server (in which case you'd turn off that feature in your router hardware).
 
Back
Top