Affected versions: Windows Server 2022

📖 ~1 min read

Table of contents
  1. Symptom & Impact
  2. Environment & Reproduction
  3. Root Cause Analysis
  4. Quick Triage
  5. Step-by-Step Diagnosis
  6. Solution — Primary Fix
  7. Solution — Alternative Approaches
  8. Verification & Acceptance Criteria
  9. Rollback Plan
  10. Prevention & Hardening
  11. Related Errors & Cross-Refs
  12. References & Further Reading

Symptom & Impact

New clients fail to receive IPv4 leases and fall back to APIPA addresses.

Environment & Reproduction

Windows Server 2022 DHCP on build 20348 with high churn VLANs.

Get-DhcpServerv4ScopeStatistics -ComputerName localhost
Get-DhcpServerv4Lease -ScopeId 10.10.20.0 | Measure-Object
ipconfig /all

Root Cause Analysis

Scope range too small, lease duration too long, or stale reservations consuming addresses.

Quick Triage

Identify top lease consumers and active exclusions.

Get-DhcpServerv4Lease -ScopeId 10.10.20.0 | Group-Object ClientId | Sort Count -Descending | Select -First 10
Get-DhcpServerv4ExclusionRange -ScopeId 10.10.20.0

Step-by-Step Diagnosis

Review lease age, rogue MAC churn, and conflict detection settings.

Get-DhcpServerv4Scope -ScopeId 10.10.20.0 | Select Name,LeaseDuration,State
Get-DhcpServerSetting
Get-WinEvent -LogName 'Microsoft-Windows-DHCP Server Events/Operational' -MaxEvents 80
Illustrative mockup for windows-server-2022 — terminal_or_powershell
DHCP lease and scope utilization output — Illustrative mockup — Progressive Robot

Solution — Primary Fix

Expand scope capacity and shorten lease for high-turnover segments.

Still having issues? Our IT Solutions & Services team can diagnose and resolve this for you. Get in touch for a free consultation.

Set-DhcpServerv4Scope -ScopeId 10.10.20.0 -LeaseDuration 1.00:00:00
Add-DhcpServerv4ExclusionRange -ScopeId 10.10.20.0 -StartRange 10.10.20.1 -EndRange 10.10.20.20
Set-DhcpServerv4Scope -ScopeId 10.10.20.0 -StartRange 10.10.20.21 -EndRange 10.10.20.240
Illustrative mockup for windows-server-2022 — event_or_log_viewer
DHCP exhaustion events — Illustrative mockup — Progressive Robot

Solution — Alternative Approaches

Create superscope or split VLAN into additional subnet.

Add-DhcpServerv4Scope -Name 'VLAN20-B' -StartRange 10.10.21.21 -EndRange 10.10.21.240 -SubnetMask 255.255.255.0 -State Active
Add-DhcpServerv4Superscope -SuperscopeName VLAN20-SS -ScopeId 10.10.20.0,10.10.21.0

Verification & Acceptance Criteria

Free address percentage should recover and clients obtain leases normally.

Get-DhcpServerv4ScopeStatistics -ScopeId 10.10.20.0
Get-DhcpServerv4Lease -ScopeId 10.10.20.0 | Select -First 5

Rollback Plan

Revert lease duration and range if downstream network policy conflicts appear.

Set-DhcpServerv4Scope -ScopeId 10.10.20.0 -LeaseDuration 8.00:00:00

Prevention & Hardening

Track utilization thresholds and alert before exhaustion.

Get-DhcpServerv4ScopeStatistics | Where-Object { $_.PercentageInUse -gt 80 }
Export-DhcpServer -File C:Tempdhcp-backup.xml -Leases

Often paired with rogue DHCP offers and relay (IP helper) misconfiguration.

Related tutorial: View the step-by-step tutorial for Windows Server 2022.

View all Windows Server 2022 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Microsoft Learn DHCP scope capacity planning and lease optimization.

Need Expert Help?

If you cannot resolve this yourself, our team offers hands-on Server Management, Managed IT Services, and flexible Support Plans. Contact us today — we respond within one business day.