Windows Server 2019 — DHCP Server service refuses to start after scope conflict — Fix & Prevention

📖 ~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

DHCP Server on Windows Server 2019 refuses to start, so clients on managed subnets stop receiving leases. New devices fall back to APIPA addresses, VPN pools dry up, and helpdesk volume spikes within minutes of the outage.

Environment & Reproduction

Reproduce after restoring or importing a scope that overlaps an existing one. Inspect DhcpSrvLog files and the System log.

Get-Service -Name dhcp
Get-WinEvent -LogName System -MaxEvents 40
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 10

Root Cause Analysis

Causes include overlapping scope ranges, missing authorization in Active Directory, broken JET database, or a failed failover partner relationship.

Quick Triage

Capture service state, scope list, and the most recent DHCP error event before remediation.

sc.exe query dhcp
Get-Service -Name dhcp | Select-Object Status,StartType
Get-EventLog -LogName System -Newest 30 | Where-Object {$_.Source -match 'dhcp'}

Step-by-Step Diagnosis

Enumerate scopes, validate AD authorization, and read the DhcpSrvLog tail for binding errors.

Get-WinEvent -LogName System -MaxEvents 50 | Where-Object {$_.ProviderName -match 'dhcp'} | Select TimeCreated,Id,LevelDisplayName,Message
sc.exe qfailure dhcp
sfc /verifyonly

Solution — Primary Fix

Remove or correct the overlapping scope, verify authorization, and restart DHCP Server.

Restart-Service -Name dhcp -Force
Get-Service -Name dhcp | Select-Object Status,StartType
Get-WinEvent -LogName System -MaxEvents 20 | Where-Object {$_.ProviderName -match 'dhcp'}

Solution — Alternative Approaches

If the JET database is damaged, run jetpack to repair and compact dhcp.mdb, then restart the service.

sc.exe config dhcp start= auto
sc.exe failure dhcp reset= 86400 actions= restart/60000/restart/60000/run/1000
Restart-Service -Name dhcp -Force

Verification & Acceptance Criteria

DHCP Server runs, clients receive leases, and the DhcpSrvLog confirms healthy DISCOVER/OFFER exchanges.

Get-Service -Name dhcp
Get-WinEvent -LogName System -MaxEvents 25 | Where-Object {$_.ProviderName -match 'dhcp' -and $_.LevelDisplayName -eq 'Error'}
Test-NetConnection -ComputerName localhost -Port 

Rollback Plan

Restore the prior dhcp.mdb backup and the previous scope list snapshot from configured backups.

Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5
wbadmin get versions
# Restore previous configuration export if available

Prevention & Hardening

Document scope ranges in a central IPAM, enable scheduled DHCP backups, and review failover state weekly.

Get-Service -Name dhcp | Export-Clixml C:/Temp/dhcp-baseline.xml
Get-WinEvent -LogName System -MaxEvents 50 > C:/Temp/dhcp-events.txt
Get-ScheduledTask | Where-Object {$_.TaskName -match 'dhcp'}

Related Errors & Cross-Refs

Related to events 1041, 1059, and JET error 17.

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

View all Windows Server 2019 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Microsoft Learn references for DHCP database maintenance and failover on Windows Server 2019.