Two Routers on Same Network: Stop IP Conflicts

You've got two routers — maybe one from your ISP and an old one you're repurposing. You plug the second router into the first, everything seems connected, then devices start dropping off the network. Phones can't get IPs, printers disappear, and one laptop gets an IP that another device already grabbed. That's an IP conflict, and it's almost always because both routers are running DHCP servers on the same subnet.

What's actually happening here is that Router A (your main router, probably 192.168.1.1) hands out a lease to your phone: 192.168.1.100. Router B (the second router, also defaulting to 192.168.1.1 or similar) doesn't know that and hands out the same IP to your laptop. Now both devices fight for that address. The network gets confused, packets go to the wrong device, and you get random disconnects. This isn't a hardware defect — it's a configuration collision.

The Root Cause

Consumer routers ship with DHCP enabled by default and use the same private IP range (192.168.x.x or 10.x.x.x). When you connect two on the same broadcast domain without disabling one's DHCP server, you get duplicate IPs. The second router also often tries to act as a gateway and NAT device, which just adds more chaos — traffic routing gets weird, and some devices might see the second router as their default gateway instead of the first.

The Fix

The only clean fix is to disable DHCP on the second router and turn it into a simple access point (or switch). Here's how to do it step by step. I'm assuming both routers are consumer-grade (TP-Link, Netgear, Asus, Linksys). The exact menu names vary, but the logic is the same.

1. Identify the main router's LAN IP address. Usually it's 192.168.1.1 or 192.168.0.1. Log into it and check the LAN settings. Write this down — you'll need it later.
2. Log into the second router. Disconnect it from the main router first. Connect a computer directly to one of its LAN ports (not the WAN/internet port). Open its admin panel — default IP is often 192.168.1.1 or 192.168.0.1. If it conflicts with the main router, you'll need to change it. That's fine, do that next.
3. Change the second router's LAN IP. In its LAN settings, set a static IP on the same subnet as the main router, but outside its DHCP pool. For example, if the main router is 192.168.1.1 and its DHCP pool is 192.168.1.100–199, set the second router to 192.168.1.2 or 192.168.1.254. Do not use 192.168.1.1 — that's the main router. Save and reboot the second router.
4. Disable DHCP on the second router. Find the DHCP settings (often under "LAN" or "Setup") and turn it OFF. This is the critical step. Without this, the second router will keep handing out IPs that conflict with the main one. Save the changes.
5. Disable NAT on the second router. If your second router supports it, go to WAN settings and set it to "Access Point" or "Bridge" mode. If not, just disable NAT manually — on some routers it's under "Advanced" > "NAT". This stops the second router from trying to create its own network boundary. Not all routers let you disable NAT entirely; if yours doesn't, just skip this and rely on DHCP being off.
6. Connect the second router. Use an Ethernet cable from a LAN port on the main router to a LAN port on the second router. Do not use the WAN/internet port on the second router. That port is for connecting to a modem, not another LAN. Using it would bypass the second router's switch and re-enable its routing logic, undoing your fix.
7. Verify everything works. Reboot both routers. On a client device, release and renew the DHCP lease (on Windows: ipconfig /release && ipconfig /renew). Check that you get an IP from the main router's DHCP range — you should see something like 192.168.1.x with a gateway of 192.168.1.1.

If It Still Fails

Three things to check. First, make sure the second router's Wi-Fi channel doesn't overlap with the main router if both are broadcasting. Use different channels (e.g., 1 and 6 for 2.4 GHz) or better, set one to auto. Second, verify you didn't plug into the second router's WAN port — that's the most common mistake. Third, log back into the second router and confirm DHCP is still off. Some routers reset to default after a hard power cycle — if yours does, tape over its reset button or set a static lease for it on the main router as a backup.

If you still get conflicts after all that, you might have a rogue DHCP server on your network — a device like a printer or a Pi-hole that's also handing out IPs. Check the main router's DHCP lease table. If you see IPs from a different range (like 10.x.x.x when your main is 192.168.x.x), something else is handing them out. Track it down by disconnecting devices one by one until the leases stop appearing. That device needs its DHCP server disabled too.