The "DHCP out of range" error occurs when a client device requests an IP address outside the subnet defined by your router's DHCP pool, typically due to incorrect static IP configurations or mismatched subnet masks. To resolve this, verify that your computer’s network adapter is set to obtain an IP automatically, ensure your router’s DHCP server is active and covers the desired range, and check for any conflicting static assignments on other devices within the same local network segment.
Understanding the Network Configuration
Before diving into fixes, it is crucial to understand why this error happens. Your home network relies on a specific subnet, usually
192.168.0.x or
192.168.1.x. The router acts as the gateway and the DHCP server, handing out addresses from a defined pool (e.g.,
192.168.1.100 to
192.168.1.200). If a device is manually configured with an IP like
192.168.2.50, it falls outside this pool. When the device tries to communicate, it cannot reach the gateway because it believes it is on a different logical network. This mismatch creates the "out of range" symptom, preventing internet access and local resource sharing.
Step 1: Reset Client Device to Automatic IP
The most common cause is a stale or manually entered static IP address on your computer or mobile device. You need to force the operating system to request a fresh lease from the router.
For Windows users, open the Command Prompt as an administrator. Type
ipconfig /release followed by
ipconfig /renew. This forces the network interface to drop its current configuration and ask the router for a new one. If you are on macOS, go to System Preferences > Network, select your active connection, and click Advanced. Under the TCP/IP tab, ensure "Configure IPv4" is set to Using DHCP. On mobile devices, forget the Wi-Fi network in settings and reconnect to trigger a fresh handshake.
If you have previously set a static IP for a printer or server, ensure those devices are correctly configured to stay within the router’s DHCP scope or use a reserved IP address via MAC binding. For stable addresses without manual entry issues, consider configuring your router as the primary DHCP server while keeping the modem in bridge mode, as detailed in our guide on
Router as DHCP Server for Computers and Modem to Keep 192.168.0.x Addresses.
Step 2: Verify Router DHCP Settings
Access your router’s administration panel to check the DHCP server status. Most routers use default gateways like
192.168.1.1 or
192.168.0.1. If you are unsure of your login IP, refer to the sticker on the back of your device or consult resources like
192.168.10.1 Router Login IP - How to Access Your Router's Settings.
Once logged in, navigate to the LAN or DHCP settings section. Ensure the DHCP Server is enabled. Check the Start IP Address and End IP Address fields. These must fall within the same subnet as your router’s LAN IP. For example, if your router is at
192.168.1.1, the DHCP pool should start at something like
192.168.1.100 and end at
192.168.1.200. The Subnet Mask should typically be
255.255.255.0. If these values are misaligned, clients will receive invalid leases or fail to connect entirely. Save changes and reboot the router if you modified these settings.
Step 3: Check Physical Connections and Switches
Sometimes the issue lies in the hardware chain between the modem and the router, or between the router and the switch. A faulty Ethernet cable or a misconfigured managed switch can sometimes interfere with DHCP broadcasts, though this is less common than IP misconfiguration.
Ensure all cables are securely seated. If you are using a network switch, verify that it is functioning correctly. In some complex setups involving multiple routers or extenders, improper cabling can create loop conditions or isolate segments. For instance, if you are integrating advanced mesh systems like the Eero Pro 6e, proper connection to the upstream network is critical. See
How to Connect an Eero Pro 6e Router to Network Switch for best practices on wiring topology.
Disconnect non-essential devices from the switch and router. Test connectivity with a single device plugged directly into the router’s LAN port. This eliminates potential interference from downstream switches or hubs that might be dropping packets.
Step 4: Clear DNS Cache and Renew Lease
Even after correcting the IP address, residual DNS cache entries on your computer can cause confusion, making it seem like the IP issue persists. Flush your local DNS cache to ensure your computer resolves names based on the new correct IP configuration.
On Windows, run
ipconfig /flushdns in the command prompt. On macOS, use
dscacheutil -flushcache in the terminal. After flushing, restart your web browser and attempt to load a website. If the problem persists, try pinging your router’s IP address (e.g.,
ping 192.168.1.1). If you get replies, your IP configuration is likely correct, and the issue may be with your ISP or DSL modem synchronization rather than the local DHCP range.
Conclusion
Resolving "DHCP out of range" errors primarily involves ensuring that client devices are set to automatic IP acquisition and that the router’s DHCP pool aligns with the local subnet. By systematically checking your computer’s network settings, verifying router configurations, and inspecting physical connections, you can restore full network functionality. Always document any static IP reservations to prevent future conflicts.
Frequently Asked Questions
What does "DHCP out of range" mean exactly?
It means your device has an IP address that does not belong to the same network segment as your router. Consequently, the device cannot communicate with the gateway to access the internet or local resources.
Can a faulty modem cause this error?
No, a faulty modem typically causes no internet access or sync issues, but it does not generate DHCP out of range errors. That error is strictly related to local IP configuration mismatches between the client and the router.
How do I find my router’s default gateway IP?
On Windows, type
ipconfig in the command prompt and look for "Default Gateway." On macOS, go to System Preferences > Network and view the details of your active connection. It is usually
192.168.1.1 or
192.168.0.1.
Should I use a static IP instead of DHCP?
You can use static IPs for servers or printers, but they must be within the router’s subnet and outside the DHCP pool to avoid conflicts. For general devices, DHCP is safer and easier to manage.
Why does my phone show this error but my laptop doesn’t?
Your phone may have retained a cached static IP from a previous network setup or a different router. Resetting the network settings on the phone or forgetting the Wi-Fi network usually clears this stale configuration.
Is resetting the router necessary after changing DHCP settings?
While not always required, rebooting the router ensures that all connected devices receive fresh leases according to the new settings. It also clears any temporary glitches in the DHCP service.