Router Not Assigning IP Addresses? Fix DHCP Issues Fast

Symptoms vs. Root Causes Diagnostic Table

When Layer 2 connectivity is established but Layer 3 IP configuration fails, client systems present specific system alerts. Use the diagnostic matrix below to map errors to their corresponding fixes:

What Is Happening Internally? The DHCP Handshake (DORA) and APIPA Fallback

To understand why a router stops assigning IP addresses, it is necessary to examine the underlying Layer 7 protocol transaction: the **DHCP DORA** handshake. This transaction operates over **UDP Ports 67** (server listening port) and **UDP Port 68** (client listening port):

1. Discover: The client broadcasts a DHCP Discover packet to the MAC address FF:FF:FF:FF:FF:FF and IP address 255.255.255.255. This packet alerts any active DHCP server on the physical LAN segment that a client needs an IP address.
2. Offer: The router's DHCP daemon (such as dnsmasq or dhcpd) receives the broadcast, checks its lease database, reserves an available IP, and unicasts or broadcasts a DHCP Offer containing the proposed IP, subnet mask, default gateway, and DNS servers.
3. Request: The client receives the offer and responds with a DHCP Request broadcast, confirming it accepts the offered IP. Broadcasting this packet notifies other potential DHCP servers on the subnet that their offers have been rejected.
4. ACK (Acknowledgment):The router receives the request, writes the client's hardware MAC address and lease timestamps to its active lease table, and sends a DHCP ACK packet to finalize the lease.

APIPA Fallback Mechanics

If the client system broadcasts a DHCP Discover packet but receives no valid DHCP Offer within a specific timeout window (typically 10 to 15 seconds), the operating system triggers its fallback routine: **APIPA (Automatic Private IP Addressing)**.

The OS automatically selects an address from the Link-Local block **169.254.1.0 to 169.254.254.255** (defined by RFC 3927). It then broadcasts local **ARP (Address Resolution Protocol)** queries to ensure no other device on the link is using that self-assigned IP. While this allows basic peer-to-peer communication on the local layer 2 segment, APIPA addresses do not have a default gateway. As a result, the device cannot route packets outside its local LAN segment, resulting in a loss of internet access.

Lease Pool Exhaustion and NAT Constraints

Every DHCP lease has a set **lease time**. If the router's configured address range (for example, 192.168.1.100 to 192.168.1.150) contains 50 IP addresses, and 50 unique MAC addresses have connected within the lease period, the pool is fully exhausted.

When device number 51 requests an IP, the router's DHCP daemon has no available addresses to assign, and ignores the DHCP Discover packet. Because Network Address Translation (NAT) maps internal private IP addresses to a single public WAN IP, any device without a valid local IP address lease cannot be added to the NAT translation tables, blocking internet access.

Advanced Root Causes of DHCP Failures

Aside from simple pool exhaustion, several advanced network configurations can disrupt DHCP operations:

• Disabled DHCP Server Daemon: When a router is converted to an Access Point (AP) or configured behind a primary gateway, its internal DHCP server must be disabled to avoid conflict. If this is done accidentally on a primary router, clients will fail to obtain IPs.
• Rogue DHCP Servers: If a secondary access point, network bridge, or virtualization server (running hypervisors like Proxmox or Hyper-V) is misconfigured to run its own DHCP server on the same VLAN, it will reply to DHCP Discover broadcasts. Devices receiving these rogue offers may be assigned invalid subnets or gateway routes.
• Firmware RAM Memory Leaks: Budget routers with limited RAM (e.g., 128MB or 256MB) can experience memory leaks in their DHCP daemons over time. This causes the daemon to crash, preventing it from responding to queries even though the physical Wi-Fi and Ethernet ports remain active.
• Mesh Topology STP Loops:In mesh Wi-Fi setups, connecting multiple mesh nodes via physical Ethernet cables without configuring Spanning Tree Protocol (STP) on the backhaul switch can trigger a **network loop**. This floods the network with broadcast packets, causing the router's CPU to spike to 100% and drop DHCP traffic.
• VLAN Isolation Blocks: If your network uses Virtual Local Area Networks (VLANs) to segment traffic, and your DHCP server is on a different VLAN than the client, the DHCP broadcast packets cannot cross the VLAN boundary. You must configure a **DHCP Helper Address** (IP Helper / DHCP Relay) on the Layer 3 switch or router interface to forward the broadcast packets to the DHCP server.
• MAC Filtering Policies: If MAC address filtering is active on the router, the DHCP daemon will ignore requests from unauthorized hardware, forcing client systems into APIPA configurations.
• ISP Bridge Mode Subnet Mismatches: If your primary router is connected to an ISP gateway that has not been placed in Bridge Mode, both devices may attempt to host the same subnet (e.g., 192.168.1.0/24), creating routing conflicts and blocking IP assignment.

Windows 11 Console Diagnostics

To troubleshoot DHCP failures on Windows 11, open PowerShell or Command Prompt as an Administrator and execute the following commands. These commands interact directly with the Windows TCP/IP stack:

1. Release Current Address Bindings

ipconfig /release

Internal Action: Instructs the DHCP client service to send a unicast DHCP Release packet (via UDP port 67) to the active DHCP gateway. This relinquishes the current IP address lease and updates the system registry.

2. Request New IP Allocation

ipconfig /renew

Internal Action: Forces the network adapter to broadcast a DHCP Discover packet. It resets the lease negotiation sequence to secure new IP address bindings and subnet routing information from the active gateway.

3. Flush DNS Resolver Database

ipconfig /flushdns

Internal Action: Purges the local DNS resolver cache, forcing the operating system to perform new DNS queries instead of relying on outdated cache data.

4. Reset TCP/IP Stack Configuration

netsh int ip reset

Internal Action: Rewrites critical TCP/IP system registry keys to their default states. This clears custom configurations, incorrect static routes, and registry corruption affecting the network stack.

5. Reset Winsock API Catalog

netsh winsock reset

Internal Action: Resets the Windows Sockets API catalog. This removes third-party LSP (Layered Service Provider) drivers and network filters installed by VPNs or security software that can intercept and block socket queries.

macOS / Linux Terminal Diagnostics

On Unix-based operating systems, network configuration is managed via configuration daemons or directly via commands. Execute these commands in Terminal:

Renew DHCP Leases via networksetup (macOS)

Identify your active network interface (typically Wi-Fi or USB 10/100/1000 LAN) and trigger a lease renewal:

sudo ipconfig set en0 DHCP

Internal Action: Resets the DHCP state machine for interface en0. This releases the current IP address and broadcasts a new DHCP Discover query.

Release and Renew on Linux (dhclient)

Linux distributions utilize the ISC DHCP client daemon to manage leases. Release the current address and request a new one:

sudo dhclient -r eth0
sudo dhclient eth0

The -r flag instructs the daemon to release the current lease on interface eth0. The second command starts a new DHCP transaction to obtain a fresh IP configuration.

Mobile OS Configurations: Android and iOS

Modern mobile operating systems include security features that can complicate DHCP addressing:

MAC Address Randomization (Private Wi-Fi Address)

By default, iOS and Android randomize their MAC addresses for each SSID to prevent tracking. While beneficial for privacy, this can cause issues on local networks:

• Lease Pool Depletion: If a device frequently changes its MAC address, the router will treat it as a new device each time, assigning it a new IP address. This can quickly exhaust the DHCP lease pool.
• Static IP Binding Failures: MAC-to-IP binding configurations will fail if the client device uses a randomized MAC instead of its hardware MAC.
• Resolution: Go to the Wi-Fi settings on your mobile device, select the network name, and toggle **Private Wi-Fi Address** (iOS) or **Use Device MAC** (Android) to disable randomization for that network.

Forget and Reconnect Network Profile

Forgetting the network profile clears cached IP configurations, lease details, and custom DNS settings stored on the device. Reconnecting forces the device to request a new IP address lease.

Console Settings: PS5 and Xbox

Gaming consoles require stable, uninterrupted network paths to support multiplayer matching:

• PS5 NAT Type Failures:A Strict NAT Type on PlayStation consoles often stems from local IP address lease changes. If the router assigns a new IP address to the console via DHCP, any port forwarding rules configured for the console's previous IP will no longer apply. To prevent this, configure an **Address Reservation** on the router to lock the console to a specific IP address.
• Xbox Teredo Network Conflicts: Xbox consoles use the Teredo tunneling protocol to establish peer-to-peer connections. If the router's DHCP server assigns incorrect default DNS settings, or if UPnP is disabled, Teredo cannot resolve routing targets. Configure a static IP on the Xbox and set the primary DNS to Cloudflare (1.1.1.1) or Google (8.8.8.8) to resolve this.

Brand-Specific DHCP Settings Navigation

If you need to adjust DHCP parameters, lease durations, or configure static IP reservations, use the paths below to locate the settings in your router's admin panel:

1. TP-Link (Archer series)

Go to **Advanced** → **Network** → **DHCP Server**. Here, you can modify the Start and End IP address pool ranges, adjust the lease time (we recommend 1440 minutes / 24 hours), and configure DNS addresses.

2. ASUS (ASUSWRT console)

Go to **Advanced Settings** → **LAN** → **DHCP Server** tab. Enable the DHCP Server toggle. You can set the IP pool range and configure **Manual Assignment** (MAC binding) at the bottom of the page.

3. Netgear (Nighthawk / Orbi)

Go to **Advanced** → **Setup** → **LAN Setup**. Ensure the **Use Router as DHCP Server** checkbox is selected. You can set the start and end IP addresses and configure static address reservations here.

4. Linksys

Go to **Connectivity** → **Local Network** → **DHCP Server**. Toggle the DHCP Server to Enabled, adjust the client lease time, and save your changes.

Hardware Failures Causing DHCP Drops

If a router continues to drop DHCP allocations even after a factory reset and with minimal devices connected, the hardware itself may be failing:

• RAM Degradation:The DHCP lease table is maintained in the router's system RAM. If the RAM chips degrade due to voltage fluctuations or age, data writes to the lease tables can fail, causing the DHCP service to crash.
• Thermal Throttling of the Switch SoC: Many home routers are fanless and rely on small passive heatsinks. If the router is placed in an unventilated area, the switch chip can overheat. This causes the router to drop packets and fail to process DHCP broadcasts, even while maintaining active LED link lights.
• Physical Port and PHY Chip Faults: Power surges can damage the physical Ethernet PHY transceiver chips behind the LAN ports. This damage can prevent client handshake frames from reaching the CPU, preventing the DHCP server from receiving the Discover request.
• Capacitor Aging:Swollen or failing electrolytic capacitors on the router's mainboard can cause voltage instability, leading to random CPU resets and crashes of network daemons like the DHCP service.

How ISPs Detect DHCP Issues Remotely

Internet Service Providers monitor network equipment performance up to your home gateway using several telemetry tools:

• CMTS Loop Diagnostic Logging: On cable networks, the **Cable Modem Termination System (CMTS)** monitors downstream DOCSIS channels. If a client router generates broadcast storms (e.g., from an STP network loop), the CMTS logs an alert and may throttle the connection to protect the node.
• DHCP IP Lease Expiry Telemetry: ISP routers check RADIUS and DHCP server logs for lease request patterns. If your router stops sending DHCP Request packets before its WAN lease expires, the ISP systems will log a provisioning timeout and mark the connection as offline.
• Modem SNMP Poll Errors: ISPs use Simple Network Management Protocol (SNMP) to poll modems and ONT units. If the ONT reports high packet drop rates on its Ethernet port, it indicates a link negotiation issue between the modem and your primary router.

When to Replace Your Router

Troubleshooting can only resolve configuration errors. If your router displays the following symptoms, it is time to replace the hardware:

• Recurring DHCP Crashes: The router stops assigning IP addresses every 24 to 48 hours, requiring a physical power cycle to restore network connectivity.
• NVRAM Write Errors: Settings changes, static IP reservations, or custom DNS configurations revert to default values after the router is rebooted.
• High Thermal Output: The router chassis feels hot to the touch, and throughput speeds drop under heavy network load.