Windows Server / DNS, DHCP & Server Networking
Investigate a DHCP reservation assigned to the wrong client identity
A reserved address can fail to apply when the reservation identifier does not match the client's request or adapter.
Environment and inputs: Windows Server 2022 / 2025 baseline · Windows PowerShell with the specified role or RSAT modules; native utilities are identified in the text. Use delegated administration and elevation only where required.
Start with this check
Confirm the host, shell and access role. Replace sample names, paths, domains and interfaces with approved targets. These are diagnostic commands; assess policy and workload impact before making changes.
Get-DhcpServerv4Reservation -ComputerName DHCP01 -ScopeId 192.0.2.0Read the result
The result shows configured reservations for the example scope. Compare the stored client identifier with the actual request, not just a handwritten asset label.
Resolve and verify
Check the intended adapter, device replacement history and scope. Correct the reservation through the network owner's process and validate the resulting lease.
Before changing production
Do not assign the same reserved address to several clients or assume every DHCP client identifier is simply a MAC address.