IP address pool exhausted

DHCP Server Out of IP Addresses – Real Fix for a Dead Network

Network & Connectivity Intermediate 👁 6 views 📅 Jul 4, 2026

Your DHCP server ran out of IPs. Devices can't get online. The fix: find the leak, extend the pool, or clean up old leases.

1. The Most Common Cause: Too Many Devices, Not Enough IPs

I walk into a small office. The owner says: "Nobody can print, and half the computers say 'No Internet.'" First thing I check: the DHCP server. Almost always, the pool is empty. Simple math: if your router gives out 192.168.1.100 to 192.168.1.200, that's only 100 addresses. But you have 50 computers, 30 phones, 20 printers, 5 smart TVs, and a bunch of IoT stuff. That's way more than 100 devices.

The fix: Log into your router or DHCP server and look at the scope. See how many IPs are leased. If it's full or close to full, you need more addresses. The easiest fix? Expand the pool.
On a typical home or small business router (like a TP-Link, Netgear, or Asus):

  1. Go to LAN settings.
  2. Find the DHCP server section.
  3. Change the starting and ending IP range. For example, from 192.168.1.100 - 192.168.1.200 to 192.168.1.50 - 192.168.1.254. That gives you 200 addresses instead of 100.
  4. Save and reboot the router.

That's it. Took me 2 minutes. But if your network is bigger, you might need a bigger subnet. For example, change from 255.255.255.0 (254 addresses) to 255.255.254.0 (510 addresses). But that's a different topic. For most small businesses, just extending the pool range works.

2. Second Most Common: IP Leases That Never Expire

Here's another scenario: last month I had a client with 30 employees. Their network kept dropping. Checked DHCP: pool had 50 addresses, but 48 were "active." Yet only 25 people were in the office. The problem? Lease time was set to one week. People brought laptops from home. Each laptop grabbed an IP and held it for 7 days. Even after they left, the lease stayed.

The fix: Reduce the lease time. In most routers, it's in the DHCP settings. Change it from 7 days (10080 minutes) to 8 hours (480 minutes) or even 1 hour. That way, when a device leaves, the IP is freed up fast.
On Windows Server DHCP:

Open DHCP snap-in > Scope > Scope Options > Lease Duration > Set to 8 hours (0 days, 8 hours, 0 minutes)

Also, run a manual cleanup. On Windows Server, right-click the scope and choose Remove Leases for all inactive ones. On a router, reboot it. That forces all devices to get new IPs.

One more thing: If you have static IPs that aren't in the DHCP exclusion range, they count against the pool. I've seen printers with static IPs that the router thinks are available. Then it gives that IP to a laptop. Conflict. So make sure all static IPs are excluded from the DHCP range.

3. Third Common: Rogue DHCP Servers or IP Conflicts

Had a client last month whose entire print queue died because someone plugged a home router into the office network. That router's DHCP served IPs to half the devices. The main server ran out of IPs because it was still trying to give them out. Chaos. Devices got IPs from two different servers and couldn't talk to each other.

The fix: Find and disable the rogue DHCP server. On a managed switch, enable DHCP Snooping (if it's a Cisco or HP switch). That blocks any DHCP response from unauthorized servers. On smaller networks, check for extra routers. Look for devices with DHCP turned on that shouldn't have it. Usually it's a travel router or a Wi-Fi extender someone plugged in.

Also check for IP conflicts. Two devices with the same IP can't both work. On Windows, run ipconfig /all on a computer that can't connect. If it shows an IP that's also used by a printer or server, you found the problem. Release and renew the IP: ipconfig /release then ipconfig /renew. If that fixes it, find the other device and change its IP.

Another quick trick: ping the IP of a device that's stuck. If you get a reply, another device is using it. Use arp -a to see the MAC address. Then trace it in your switch logs.

Quick-Reference Summary Table

CauseSymptomFix
Too many devicesDHCP pool full, no free IPsExtend pool range or increase subnet
Leases never expirePool shows many old leasesReduce lease time to 8 hours, remove old leases
Rogue DHCP server or IP conflictDevices get IPs from two sources, IP conflictsDisable extra DHCP servers, enable DHCP snooping, release/renew IPs

Bottom line: A full DHCP pool is easy to fix. First, check how many devices you actually have. Then fix the lease time. And watch out for people plugging in random routers. I've seen this kill networks a dozen times. Don't let it happen to you.

Was this solution helpful?