I stood up this new Debian box on my network and ran into an issue when I went to reserve the MAC address and found that it was being ignored — well it was actually just using a new type of GUID to keep the same IP no matter what network adapter a machine uses and Server 2012 R2 which is what I’m currently using to handle DHCP on my home lab. You can revert Debian-based distros to continue to use the hardware address (MAC) but in this case I figured I’d just adapt and overcome. Here is an outline of what I did to get this working without upgrading to a newer Windows Server:
- Open the DHCP RSAT Tool
- Find the lease in my dynamic pool and reserve it
- Right click and do properties on it
- Copy out the hardware address noting its a lot longer
-
Fire up PowerShell and use this command on the 2012 R2 DHCP server after deleting the reservations since its not in the block I want:
- Add-DhcpServerv4Reservation -ScopeId 10.100.0.0 -IPAddress 10.199.1.30 -ClientId “dda6603200020000ab1149cdd31c16532944” -Description “Debian VM”
- In other words: Add-DhcpServerv4Reservation -ScopeId [Scope’s IP] -IPAddress [IP You want to assign this machine] -ClientId “[The Devices DHCP ID]” -Description “Debian VM”