DHCP scope exhaustion is a capacity failure inside an otherwise functioning DHCP system
A DHCP server can be online, reachable, and correctly processing requests yet still fail new clients because the relevant scope has no eligible address left to lease. That is the central distinction: scope exhaustion is not automatically a server outage. The strongest diagnosis ties a selective symptom pattern to actual capacity evidence.
Practice defensible pool counts in AP Networking DHCP Leases and Relays Practice Test. Inclusive ranges, exclusions, current leases and additional unavailable entries must be counted without double subtraction. The diagnostic also distinguishes real endpoint growth from a test tool repeatedly consuming leases under new identities.
Subnet size, DHCP pool size, and truly available addresses are three different numbers
A /24 contains 256 total addresses, with the network and broadcast addresses traditionally unavailable to ordinary hosts. But a DHCP scope may lease only a portion of the remaining addresses. Infrastructure addresses, exclusions, reservations, active leases, declined/conflict entries, and intentionally unused space all reduce the number the server can actually offer.
If the scope leases only 192.168.10.100 through 192.168.10.199, the dynamic pool contains 100 addresses even though the subnet is much larger.
A 100-address pool can exhaust long before a /24 subnet appears “full”
In this hypothetical scope, 94 addresses are unavailable to ordinary new clients, leaving only six. The subnet may still contain many IP addresses outside the DHCP pool, but those addresses do not help unless the administrator safely expands the pool or redesigns the address plan.
This is why “the subnet has room” is weaker evidence than the actual DHCP scope statistics.
Model whether a scope can serve the next group of clients
Use the calculator to distinguish raw pool size from practical availability. This is a planning model, not a substitute for live server data.
Existing clients can hide exhaustion because they already possess valid leases
A client that already has a valid lease does not necessarily need a brand-new address each time it sends traffic. That allows established users to keep working while new devices fail. This selective pattern is one of the strongest clues because it separates address acquisition capacity from general network availability.
Lease duration changes how quickly departed clients release practical capacity
Long leases are not inherently bad, but they can be a poor fit for networks with high turnover. A guest or event network may see hundreds of short-lived devices over a day. If those addresses remain leased long after clients leave, the scope can run out even though only a fraction of historical clients are physically present.
Shorter leases improve reuse but create more renewal activity. A strong design matches lease duration to client behavior rather than choosing “short” or “long” as a universal best practice.
Protected addresses reduce dynamic capacity even when they are operationally necessary
Exclusions prevent DHCP from offering addresses that belong to gateways, servers, printers, or statically managed infrastructure. Reservations give known clients predictable DHCP addresses. Both are legitimate tools, but they consume address-plan capacity. A scope with many obsolete reservations can look roomy on paper while offering very little space to ordinary clients.
Capacity review should therefore count not only active leases, but also every address intentionally or accidentally unavailable to new dynamic clients.
A static address inside the DHCP pool is a collision problem, not classic exhaustion
If a printer is manually configured as 192.168.10.150 but DHCP still considers .150 part of its free pool, the server can attempt to lease that address to another client. The resulting conflict can create intermittent or duplicate-address symptoms even though the scope still has free entries.
Exhaustion can appear as a Discover that reaches the server but produces no usable Offer
Hypothetical DHCP log 12:02:14 DISCOVER from client AA:BB:CC:11:22:33 12:02:14 Scope 10.40.20.0/24 selected 12:02:14 Available addresses: 0 12:02:14 No lease offered
This is much stronger evidence for exhaustion than a client simply showing APIPA. It shows that the request reached DHCP, the correct scope was considered, and the capacity condition blocked assignment.
A 169.254/16 address tells you assignment failed—not why
A Windows-style client may self-assign an IPv4 link-local address when normal configuration does not complete. Scope exhaustion is one plausible cause, but so are VLAN mismatch, relay failure, filtering, server outage, or client-side problems.
Use DHCP Explained for DORA reasoning and Wrong Default Gateway Symptoms when the client did receive a lease but cannot route normally.
Separate exhaustion from server outage, relay failure, and VLAN mismatch
| Pattern | More consistent with | Next discriminating evidence |
|---|---|---|
| Existing clients work; new clients fail | Scope capacity / new-lease problem | Available-address count, DORA/server log |
| Every scope fails suddenly | Shared server/service/path problem | Server status, common route/policy, logs |
| Only one VLAN fails, scope has free space | Relay/VLAN/path-specific problem | Relay config, packet path, VLAN evidence |
| One client fails, peers lease normally | Client or access-port/VLAN issue | Client state, port VLAN, packet trace |
| Lease succeeds but gateway is wrong | Bad DHCP option, not exhaustion | Compare lease options with known-good peer |
Swipe horizontally to see the full diagnostic table.
A classroom adds 25 devices and only the first six receive leases
The scope has 100 configured addresses, 84 active leases, eight reservations, and two conflict/declined entries. Only six addresses remain. The first six new devices receive leases; the remaining nineteen fail.
Mechanism: the pool runs out during the arrival burst. Evidence: free-address count reaches zero as new leases are issued. Repair: expand valid capacity or redesign the subnet based on projected demand. Verification: fresh clients lease successfully and useful headroom remains.
Guest Wi-Fi exhausts every afternoon even though only half the devices are still present
The guest scope uses a very long lease while client turnover is high. Many departed phones still occupy leases. Shortening the lease to a value that better fits guest behavior may improve reuse, provided the design accounts for increased renewal traffic and operational requirements.
The information gain here is the relationship between turnover rate and lease retention, not simply the total number of people currently in the building.
One VLAN fails DHCP, but its scope still has 120 addresses free
Students in VLAN 30 receive APIPA addresses. Staff in VLAN 20 lease normally from the same server. The VLAN 30 scope has plenty of capacity. This contradicts an exhaustion diagnosis.
The next evidence should move to VLAN 30's relay/path, not scope expansion. This is an important counterexample: a similar client symptom does not justify the same root cause.
A printer's manual static address collides with the DHCP pool
A printer is manually set to 192.168.10.150, but .150 remains inside the dynamic pool. A laptop receives .150 and both devices behave inconsistently. The DHCP server still shows free capacity, so this is not exhaustion.
The correct change is address-plan hygiene: move the static address outside the dynamic range or protect it with the appropriate exclusion/reservation strategy, then verify the duplicate condition is gone.
The scope was expanded, but the network will exhaust again tomorrow
An administrator adds ten addresses to a scope that receives roughly thirty new clients each morning. One test laptop leases successfully, but only two free addresses remain afterward. The repair technically worked for one client but failed the capacity requirement.
Verification must include headroom. A single successful DORA exchange proves assignment works now; it does not prove the design can sustain expected demand.
Use peak concurrent demand and turnover—not average occupancy—to size the pool
A safer capacity estimate considers the maximum number of simultaneously valid leases, not just the average number of devices observed at one moment. Guest networks, labs, rotating classrooms, and device refresh events can create bursty demand. Growth margin matters because a scope designed to run at 99% utilization has no resilience for unusual days.
For AP Networking reasoning, the exact target headroom is a design decision, but the principle is universal: size for the requirement and verify with evidence.
Choose the fix that addresses the capacity mechanism without creating a new network problem
| Repair | When it fits | What to verify |
|---|---|---|
| Remove stale reservations safely | Capacity is consumed by no-longer-needed reserved entries | No required device depended on them |
| Adjust lease duration | High-turnover clients retain addresses too long | Reuse improves without excessive churn |
| Expand pool | Unused valid addresses exist in subnet | No overlap with static/infrastructure space |
| Resize subnet | Subnet itself is too small for requirement | Addressing, masks, routes, DHCP, security all align |
| Add another VLAN/subnet | Growth justifies another logical network | Routing, policy, DHCP relay/scope, capacity |
Swipe horizontally to see the full repair table.
Each scope-exhaustion clue has limits
| Evidence | Supports | Does not alone prove |
|---|---|---|
| Existing clients work | Some network paths and leases remain usable | DHCP can issue fresh leases |
| APIPA on new client | Normal assignment did not complete | Scope is exhausted |
| Server responds to ping | Some IP reachability to server | Scope has free addresses or DHCP is permitted |
| Available count = 0 | No free entries in reported scope | That client is using the intended scope unless scope selection is confirmed |
| Fresh lease succeeds | At least one new assignment worked | Capacity is sufficient for expected demand |
Swipe horizontally to see the complete evidence table.
Seven DHCP exhaustion claims that are too broad
- “The server is down because new clients fail.” Exhaustion can occur on a healthy server.
- “A /24 means 254 DHCP addresses.” The configured pool may be much smaller.
- “Existing clients work, so DHCP is fine.” Existing leases can mask new-lease failure.
- “APIPA proves exhaustion.” It proves only that normal assignment did not complete.
- “Short leases are always better.” Lease duration must fit turnover and operational requirements.
- “A static address inside the pool is exhaustion.” It is primarily an address-collision/design problem.
- “One successful lease proves the fix.” Capacity verification also needs sustainable free-address headroom.
Build the answer from selective symptoms and capacity evidence
Observation: identify who fails—new clients, one VLAN, or every scope.
Evidence: cite available-address count, leases, scope, DORA/log output, or relay behavior.
Mechanism: explain why the scope cannot issue another eligible lease.
Boundary: state what the evidence does not prove.
Repair: choose capacity reclamation, pool expansion, lease adjustment, or network redesign based on the cause.
Verification: use fresh clients and confirm both correct lease options and post-repair headroom.
Prove both immediate recovery and sustainable capacity
After repair, test with a client that did not already hold a valid lease. Confirm that it receives an address from the intended scope with the correct prefix/mask, default gateway, DNS, and other required options. Then inspect the scope again. If the pool has only one or two addresses left and the network regularly adds dozens of clients, the immediate symptom is fixed but the design requirement is not.
24 DHCP scope exhaustion digital flashcards
Practice capacity math, lease behavior, exclusions, reservations, turnover, APIPA, differential diagnosis, repair selection, evidence boundaries, and verification. Before revealing each answer, identify the exact artifact you would inspect.