Fix IPv4 Pool Exhaustion: DHCP Out of IPs

Quick answer for advanced users

Check your DHCP server logs for Event ID 1007 or 20290. If the pool is full, either reduce the lease time to 8 hours, expand the scope range, or add a second scope on a different subnet with a helper address.

Why this happens

I had a client last month—a small law firm with 20 people—who suddenly couldn't print or get online. Their receptionist's laptop showed "Limited connectivity" and the rest of the office started complaining. Turns out, their DHCP server (a Windows Server 2016 box in the closet) had a scope of 192.168.1.100 to 192.168.1.150—only 50 IPs. That worked fine for years because most people used wired workstations. But then they added 10 iPads for document review, plus a few guest phones, and suddenly the pool was dry. The DHCP server just couldn't hand out any more addresses.

This usually happens in small businesses where the network grows faster than the admin thinks about IPs. You add Wi-Fi devices, VoIP phones, maybe a new camera system, and boom—no more leases. The DHCP server keeps trying but every request gets a NAK. Devices either show an APIPA address (169.254.x.x) or just sit there with a yellow triangle.

The core issue is simple: the scope range is too small for the number of devices. But the fix isn't always obvious if you're not the one who set it up.

Step-by-step fix

Confirm the exhaustion – On the DHCP server, open DHCP Manager. Right-click your scope and pick Display Statistics. You'll see "Addresses in use" equals "Total addresses." Also check event logs for DHCP warnings. On a client machine, run ipconfig /all at the command prompt. If the IP starts with 169.254, you've got no lease.
Shorten lease times first – This is the quickest win. Open the scope properties, go to Lease Duration, and drop it from 7 days to 8 hours (or even 1 hour if it's temporary). This frees up IPs as devices disconnect. On a small network, most devices only connect for a few hours at a time. With a 7-day lease, those IPs sit locked up for a week. After shortening, wait 5 minutes for renewals to happen.
Expand the scope range – If shortening doesn't cut it, you need more IPs. In the scope properties, click Address Pool. Increase the end IP. For a typical /24 subnet (like 192.168.1.0/24), you can go from 192.168.1.100-150 to 192.168.1.100-254. That gives you 155 usable IPs instead of 51. Check for conflicts—don't include your router's IP (usually x.x.x.1) or any static devices. Add exclusions for those.
Release and renew on affected clients – On each stuck machine, open Command Prompt as admin and run:
```
ipconfig /release
ipconfig /renew
```
Wait 10-20 seconds, then check with ipconfig. If it grabs a new IP, you're good. If not, the pool might still be full—give it a minute or reboot.
Check for rogue DHCP servers – Sometimes a second DHCP server (like a home router plugged in by mistake) hands out IPs and exhausts your official pool. Use ipconfig /all on a client and see if the DHCP server IP matches your real server. If it's different, unplug that device. I once found an old Netgear router in a break room that someone plugged in as a switch—it was handing out IPs from its own pool.

Alternative fixes if the main one fails

If you can't change the scope (e.g., static devices on that range)

Create a second scope on a different subnet. For example, if your main network is 192.168.1.0/24, add a second scope like 192.168.2.100-200. Then configure DHCP relay on your router to forward requests to the server for both subnets. This is more complex—you need to understand VLANs and routing—but it works. I've done this for a warehouse that added 30 IoT sensors and couldn't touch the main office LAN.

If the problem is temporary (e.g., a guest event with 50 phones)

Just shorten the lease to 30 minutes for a day. After the event, set it back to 8 hours. Don't forget to revert—I've seen people leave leases at 1 hour and cause network chatter.

If you don't have DHCP server access

Use static IPs for a few critical devices. Pick an IP outside the DHCP range (like 192.168.1.200 if the range is 100-150), set the subnet mask, gateway, and DNS manually. This is a band-aid, not a fix, but it'll keep printers and servers online while you get admin rights.

Prevention tip

Once you've fixed it, plan ahead. For any small business network, leave at least 50% headroom in your DHCP scope. If you have 50 devices today, use a range of at least 100 IPs. Better yet, switch to a /23 subnet (512 IPs) if your router and servers support it. Most modern gear does. Also, set lease times based on device types: workstations get 8 hours, guest devices get 1 hour, printers get 7 days (since they're always on). Monitor your DHCP usage monthly—just glance at the stats in DHCP Manager. It takes 10 seconds and saves you a headache later.

And for heaven's sake, label that rogue router in the break room. Or better, disable its DHCP server. You'll thank me when you're not getting calls at 3 PM on a Friday.