Windows Server / DNS, DHCP & Server Networking
Diagnose clients receiving the wrong gateway or DNS options
A correct leased address can still leave a server unreachable when DHCP options are wrong at the applicable scope or policy.
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-DhcpServerv4OptionValue -ComputerName DHCP01 -ScopeId 192.0.2.0Read the result
Replace the documentation scope with the real subnet. The query reads scope-level option values; server, reservation and policy overrides may affect the actual lease.
Resolve and verify
Compare the client's received options with all applicable configuration layers. Correct the winning managed option and renew only in a safe maintenance context.
Before changing production
Do not release a remotely administered server's lease before arranging another access path.