Diagnose DHCP pool exhaustion
The office with no vacancies. New laptops cannot get an address. Existing laptops continue working. The DHCP service dashboard is green. The dashboard would like that entered into the record.
What you’ll practise
Inspect the supplied evidence, distinguish competing explanations and choose a proportionate next action. Use the clickable topology and private notebook to keep track of your findings.
Lab scope: Single authorised server; VLAN 40. Client requests reach the server. No failover partner or alternative pool in this lab.
Validation: Fictional training scenario; not vendor-build verified. No live network access is required. Basic DNS, DHCP and IP addressing knowledge is helpful. Progress is stored in this browser.
DHCP says yes.
DNS says yesterday.
A laptop moved networks. Its name didn’t. Find out who’s telling the truth — and what you should check next.
Realistic DNS, DHCP and IPAM mysteries.
No lab setup. No production access. Just your judgement.
New lease.
Old address.
Same confused user.
10.62.4.27 ✓↓ six minutes and three cache flushes later09:36 / DNS ANSWER10.61.4.27 ?“Have you tried flushing it again?”
The fourth time is not a strategy.
Troubleshooting guide
Recognise the symptoms
New laptops cannot get an address. Existing laptops continue working. The DHCP service dashboard is green. The dashboard would like that entered into the record.
Checks to compare
- Trace a new client request. Compare what this check establishes with the other devices in the path.
- Audit the pool. Compare what this check establishes with the other devices in the path.
- Review safe capacity options. Compare what this check establishes with the other devices in the path.
Scope matters. Single authorised server; VLAN 40. Client requests reach the server. No failover partner or alternative pool in this lab.
Reveal the diagnosis, common mistakes and next action
What the evidence supports
The 50-address pool is entirely unavailable: 48 active leases plus two conflict-marked addresses. The server receives requests but cannot allocate an address.
Common mistakes to avoid in this scenario
- Broken relay: Change helper address.
- Leases are disposable: Delete every active lease.
A proportionate next action
Investigate conflicts and validate capacity before changing the pool. Do not erase active leases or blindly extend into unverified addresses.
Limits of the conclusion
A /24 does not mean 254 dynamic leases are configured. Scope range, exclusions and lease state matter.