How To • Networking • IP and DHCP issues

How to Troubleshoot DHCP Issues on Mesh Networks

This guide will help you fix common problems where devices on your mesh network fail to get a valid IP address, resulting in "No Internet" or "Limited Connectivity" errors. You'll learn how to diagnose the DHCP server, refresh IP assignments, and resolve conflicts to restore stable connections across all your mesh nodes and connected devices.

Note: Steps may vary by device and router model. This guide focuses on safe, general methods.

Quick Answer

Restart your entire mesh system and the problematic device.
On the troubled device, run the network troubleshooter (Windows) or renew the DHCP lease (macOS/Linux).
Log into your main router's admin page and ensure the DHCP server is enabled.
Check that the DHCP address pool is large enough and not conflicting with static IPs.
Reduce wireless interference by spacing mesh nodes appropriately.
Consider updating your main router's and mesh nodes' firmware.

If this doesn’t work, follow the detailed diagnostic flow and steps below.

What you need

Before you start

A device with a working web browser to access router settings.
Your mesh system's main router admin password.
A second device (like a phone) for checking connectivity.
Physical access to your main router and mesh nodes.
An Ethernet cable for testing wired connections.

Good to know

How to find your device's IP address (ipconfig, ifconfig).
The default gateway address of your network (often 192.168.1.1).
That only ONE device on your network should act as the DHCP server (usually the main mesh router).
Mesh systems often have a dedicated app for management.
Basic understanding of terms: IP address, DHCP, gateway, DNS.

Diagnose the issue in 2 minutes

Is it one device or all devices?
- One device: Problem is likely with that device's settings or wireless adapter.
- All devices: Problem is likely with the main mesh router, its DHCP server, or the ISP connection.
For the affected device, can you get an IP address?
- Check for a 169.254.x.x (APIPA) or 0.0.0.0 address. This means DHCP failed.
- Check for a valid IP in your router's range (e.g., 192.168.1.x).
Test connectivity type:
- Wi-Fi: Try moving closer to the main node.
- Ethernet: Connect directly to the main router if possible.
Quick checks:
- Ping your router's internal IP (e.g., ping 192.168.1.1). No reply indicates a local network break.
- Ping a public DNS server (e.g., ping 8.8.8.8). No reply but router pings means an internet issue.
- Power cycle the main mesh router and one satellite node. Wait 2 minutes.

Step-by-step guide

Step 1 — Restart the network in order

A sequential restart clears state and allows the mesh to re-establish proper hierarchy.

Unplug the power from all mesh satellite nodes.
Unplug the power from your main mesh router and modem (if separate).
Wait 60 seconds, then plug in the modem. Wait for all lights to stabilize.
Plug in the main mesh router. Wait 2 full minutes for it to boot.
Now plug in the satellite nodes, one by one, waiting for each to connect.

Step 2 — Renew the DHCP lease on the troubled device

Forcing the device to request a new IP address from the mesh router's DHCP server.

Windows: Open Command Prompt as admin. Run ipconfig /release then ipconfig /renew.

macOS: Open System Settings > Network. Select your connection, click Details... > TCP/IP. Click "Renew DHCP Lease".

Linux: Open terminal. For systems using NetworkManager: sudo nmcli con up "YourConnection". For others: sudo dhclient -r then sudo dhclient.

What you should see: The device obtains a new IP address (not 169.254.x.x) and connects.

Step 3 — Verify the main router's DHCP server is on

Log into the web admin interface of your primary mesh router (not a satellite).

Find the DHCP or LAN settings section.
Ensure the DHCP server is "Enabled".
Note the "Starting IP Address" and "Ending IP Address" range (e.g., 192.168.1.100 to 192.168.1.200).

What you should see: DHCP is enabled with a pool of at least 20 addresses.

Step 4 — Check for IP address conflicts

Conflicts occur if two devices have the same IP, often due to manual assignments.

In your router's admin, look for a "Connected Devices" or "DHCP Client List".
Check for duplicate IPs in the list.
Review any static IP reservations you've set up. Ensure they are outside the main DHCP pool.

What you should see: All listed devices have unique IP addresses.

Step 5 — Inspect wireless backhaul connections

A weak connection between mesh nodes can disrupt DHCP request forwarding.

Open your mesh system's app or admin page.
Check the connection status/strength between nodes.
Reposition satellites to be closer to the main node, avoiding thick walls and large metal objects.
If possible, use Ethernet backhaul (wiring nodes together) for the most stable backbone.

Step 6 — Update firmware

Manufacturers release updates that fix bugs, including DHCP issues.

In the router admin or dedicated app, find the Firmware Update section.
Check for updates for both the main router and all satellite nodes.
Apply updates one at a time, allowing the system to stabilize between updates.

What you should see: A confirmation that you are running the latest firmware version.

Common fixes by symptom

Connected but no internet (Self-assigned IP 169.254.x.x)

Likely causes: DHCP server off, device too far from node, router overloaded, wireless interference.

Safe fixes: Renew DHCP lease, restart the specific mesh node the device is connected to, ensure DHCP pool is not exhausted.

When to stop: If toggling DHCP server on/off doesn't help, consider a factory reset of the mesh system.

Intermittent drops for wireless devices only

Likely causes: Weak backhaul signal, channel congestion, device roaming poorly between nodes.

Safe fixes: Reposition nodes for better line-of-sight, change Wi-Fi channel in router settings, enable "Fast Roaming" (802.11r/k/v) if supported.

When to stop: If professional-grade channel analysis and repositioning yield no improvement.

IP conflict error message

Likely causes: Manual static IP set on a device within the DHCP range, a device with a reserved lease came back online after a long time.

Safe fixes: Restart the device to get a new lease, change the DHCP pool range to exclude the conflicted IP, clear all DHCP leases in router admin and restart.

When to stop: If conflicts keep reappearing with different IPs, suspect a rogue DHCP server on the network.

New devices cannot join the Wi-Fi

Likely causes: DHCP address pool is full, weak signal at the join location, incompatible security (WPA3 vs older device).

Safe fixes: Increase the size of the DHCP address pool, bring the device close to the main node to join, temporarily use WPA2/WPA3 mixed mode.

When to stop: If the pool is already large (e.g., 150 addresses) and the issue persists.

Slow speed after connecting via mesh node

Likely causes: Node is connected via a weak wireless backhaul, using a congested band, or the node itself is malfunctioning.

Safe fixes: Test speed when connected to the main router. Move the satellite closer. Ensure it's using a dedicated 5GHz backhaul if supported.

When to stop: If wiring the node (Ethernet backhaul) doesn't solve the speed issue, the node may be faulty.

Quick reference

Table A: What the metric means

Metric	Ideal Range	Impact on DHCP/Connectivity
Signal Strength	-50 dBm to -65 dBm (Good)	Weak signal (< -75 dBm) can cause DHCP requests to time out.
Latency (Ping)	< 30ms to local router	High latency within your local network suggests interference or node overload.
Packet Loss	0% to local router	Any loss between device and router can disrupt the DHCP handshake.
DHCP Lease Time	6 to 24 hours	Very short leases (<1h) increase network chatter; very long leases (>1 week) can exhaust the pool.

Table B: Safe baseline router settings

Setting	Recommended Value	Reason
DHCP Server	Enabled	Must be on to assign IPs automatically. Ensure it's only on the main router.
DHCP Address Pool	.100 to .200 (Example)	Leaves room for static IPs (.2 to .99) and reduces chance of pool exhaustion.
Wi-Fi Security	WPA2/WPA3 Mixed	Balances modern security with compatibility for all devices.
Router Admin Password	Unique and strong	Prevents unauthorized changes to DHCP and network settings.
Firmware Updates	Auto-update if stable	Fixes bugs, including DHCP and mesh coordination issues.

Mind map summary

DHCP Issue on Mesh Network
|
├── Scope: One Device vs. All Devices
│   ├── One Device → Focus on device/client.
│   │   ├── Renew DHCP lease (ipconfig /renew, etc.).
│   │   ├── Forget and rejoin Wi-Fi network.
│   │   └── Check for driver/OS updates.
│   │
│   └── All Devices → Focus on main router & mesh system.
│       ├── Restart main router & nodes in sequence.
│       ├── Verify DHCP server is ON in router settings.
│       └── Check DHCP address pool range and size.
|
├── Check Physical & Wireless Factors
│   ├── Weak backhaul signal between nodes → Reposition nodes.
│   ├── Interference from other electronics → Change Wi-Fi channel.
│   └── Ethernet backhaul preferred for stability.
|
├── Configuration Checks
│   ├── Only ONE DHCP server active (disable on old routers/extenders).
│   ├── No IP conflicts (check client list in admin).
│   ├── Static IPs must be outside the DHCP pool.
│   └── Lease time: 6-24 hours is typical.
|
└── Last Resorts
    ├── Update firmware on all mesh units.
    ├── Factory reset mesh system and reconfigure.
    └── Contact ISP to check modem/router combo unit DHCP passthrough.

Troubleshooting checklist

Device

Restart the device
Renew DHCP lease
Toggle Airplane/Wi-Fi mode
Forget and re-add network
Check for OS updates

Router & Mesh

Sequential power cycle (Modem → Main Router → Nodes)
Confirm DHCP server enabled
Verify adequate DHCP pool size
Check for firmware updates
Inspect node connection strength in app
Disable any extra DHCP servers

ISP & Environment

Test with a direct Ethernet connection to modem
Check for ISP outage reports
Reduce wireless interference (microwave, baby monitors)
Ensure nodes are not too far apart

When to escalate

Escalate the issue if you've methodically tried all steps above without success.

Contacting your ISP: If no devices get an IP even when wired directly to the modem, or if the modem's gateway IP is inaccessible. This could indicate a modem or upstream provisioning issue.
Replacing router/mesh hardware: If the main router repeatedly crashes, fails to enable DHCP after a factory reset, or shows consistent hardware failure lights. Also if certain satellite nodes consistently fail to connect.
Asking IT support or a professional: For complex network setups involving VLANs, multiple subnets, or business-critical environments where you cannot risk downtime.

What to collect before you call:

Speed test results (to a common site like speedtest.net).
IP address and default gateway of a working and non-working device.
Timestamps of when the issue occurs.
Exact error messages (e.g., "DHCP server not found").
Your mesh system and router model numbers and current firmware versions.

FAQ

Should I enable DHCP on my mesh satellite nodes?

No. In a standard mesh network, only the main router (the one connected to your modem) should have its DHCP server enabled. The satellite nodes act as access points and should relay DHCP requests back to the main router. Enabling DHCP on satellites will create multiple servers and cause conflicts.

Why does my device keep getting a 169.254.x.x IP address?

This is an Automatic Private IP Address (APIPA). Your device assigns this to itself when it cannot contact a DHCP server. The cause is usually a broken connection to the main router, a disabled DHCP server, or the device being too far from a mesh node to complete the DHCP handshake.

Can too many devices break DHCP on a mesh network?

Yes, in two ways. First, if the DHCP address pool is too small, it can run out of assignable IPs. Second, if there are hundreds of very active devices, the main router's CPU might struggle to handle all the requests, leading to timeouts. Ensure your DHCP pool is large enough (e.g., 100 addresses) and consider segmenting IoT devices onto a guest network.

How do I find my router's admin IP address if I can't connect?

On a Windows device with a valid connection, open Command Prompt and type ipconfig. Look for the "Default Gateway" address. On macOS or Linux, open Terminal and type netstat -nr | grep default (macOS) or ip route | grep default (Linux). The IP listed is your router's address.

What is DHCP lease time, and what should I set it to?

Lease time is how long a device keeps its assigned IP address before it must request renewal. Typical values are 6 to 24 hours. Shorter leases (1 hour) can help in dynamic environments but create more network chatter. Longer leases (1 week) are stable but can slow the reclamation of unused IPs. For most homes, 12-24 hours is a safe setting.

Will a factory reset on my mesh system fix DHCP issues?

Often, yes. A factory reset erases all custom settings (including any accidental misconfigurations) and restores the default, working DHCP setup. This is a last-resort step because you will have to set up your Wi-Fi name and password again, and any port forwards or reservations will be lost.

My old router is still connected. Could that cause problems?

Absolutely. If an old router is still plugged into the network (even just via Ethernet) and has its DHCP server enabled, it will create a "rogue DHCP server" scenario. Devices may get IP addresses from the wrong router, leading to no internet. Ensure only your main mesh router is providing DHCP.

Does using a VPN affect DHCP?

Usually not. DHCP assigns your local network IP before the VPN connects. However, some VPNs have settings like "kill switches" or "LAN blocking" that can interfere with local network communication after connection. If DHCP works until you turn on the VPN, check the VPN's settings for options that allow local network access.

Sources and references

Microsoft Windows documentation on TCP/IP networking and the ipconfig command.
Apple Support documentation for network settings and renewing DHCP lease on macOS.
Linux man pages for dhclient, NetworkManager, and net-tools utilities.
General networking concepts from Cisco's "How DHCP Works" technology overview.
IEEE 802.11 standards documentation for Wi-Fi operation and mesh networking principles.
Router and mesh system vendor administration guides (e.g., TP-Link, Netgear, Google, eero).
Online networking forums and communities for common mesh DHCP troubleshooting scenarios.
CompTIA Network+ certification study materials on IP addressing and DHCP.

Menu

How to troubleshoot DHCP issues on mesh networks

AI Assistant

Was this tool helpful?