TP-Link troubleshooting technician providing live chat help

Joe B.

Reviewed for technical accuracy

Specialities: TP-Link Archer/Deco, DHCP & IP conflicts, wrong gateway issues, modem & router setup, Windows/macOS TCP/IP repair

Fix “TP-Link router assigning wrong IP address” — wrong gateway, APIPA 169.254, devices in the wrong subnet

Technician avatar Technician
Welcome! We’ll sort out why your TP-Link router is assigning wrong IP addresses and get all devices on the right network again.

To get a clear picture:
• What exact TP-Link model are you using — Archer router, Deco mesh, or a TP-Link modem router combo?
• When a device has the problem, what IP address, subnet mask, default gateway, and DNS do you see in its network details?
• Do any devices show a 169.254.x.x APIPA address or an IP from some other router (like your ISP modem) instead of from the TP-Link?
• Are there other routers or Wi-Fi extenders on the network that might also be running a DHCP server?

Once we know whether the wrong IP address is coming from TP-Link’s DHCP or from a second DHCP server, we can fix the TP-Link LAN and gateway settings step by step.
Customer
It’s a TP-Link Archer AX20 behind my ISP’s modem/router combo. The TP-Link is supposed to be the main router for Wi-Fi. Some devices get a normal IP like 192.168.0.105 with gateway 192.168.0.1, but other devices randomly get an IP like 192.168.1.50 with gateway 192.168.1.1, or sometimes 169.254.x.x. When that happens, they can’t reach the internet. So it really looks like the TP-Link is assigning wrong IP addresses or something else on the network is doing it.
Technician avatar Technician
Great detail, thanks. What you’re seeing is a classic DHCP conflict / wrong gateway scenario:

• Your ISP modem/router is handing out 192.168.1.x addresses.
• The TP-Link LAN is probably using 192.168.0.x and also running a DHCP server.
• Devices are sometimes talking to the ISP box and sometimes to the TP-Link, so they land in the wrong IP range with the wrong default gateway.
• When a device falls back to a 169.254.x.x APIPA address, it means it couldn’t get an IP from any DHCP server at all.

We’ll fix this by: choosing one device to be the DHCP server, putting the other box in bridge/AP mode, and then cleaning up any static IPs so the TP-Link stops “assigning” confusing or wrong IP information.
Customer
That makes sense. I think the ISP router still has its Wi-Fi on, and some devices might be connecting to it. The TP-Link Archer is plugged into a LAN port on the ISP router. I didn’t change much from default other than Wi-Fi name and password on the TP-Link. I didn’t touch any DHCP settings manually.
Technician avatar Technician
Got it — that layout explains why the TP-Link router appears to assign wrong IP addresses even though it’s really a battle between two DHCP servers.

Step A — Decide who is the boss (main router + DHCP)
Since you want the TP-Link Archer to be the main router:
1) Log into your ISP modem/router and look for settings like “Bridge mode”, “Modem only”, or “Turn off router/DHCP/Wi-Fi”. Enable bridge mode if available, or at least:
  • Turn off the ISP router’s Wi-Fi so devices stop connecting there by mistake.
  • Disable its DHCP server so it stops handing out 192.168.1.x addresses.
2) Move the cable so the ISP box’s LAN (or bridge) port goes into the TP-Link’s WAN/Internet port, not LAN-to-LAN, so the TP-Link clearly sits “behind” the modem.
3) Log into the TP-Link and confirm that its LAN IP is something like 192.168.0.1 and that the DHCP server is enabled there with a range like 192.168.0.100–192.168.0.249.

Once only the TP-Link is allowed to give out IP addresses, we’ll clean up any devices that still have a wrong IP address or gateway stuck from before.
Customer
I turned off Wi-Fi and DHCP on the ISP router and moved the cable to the TP-Link’s WAN port. The Archer’s LAN is 192.168.0.1 with DHCP 192.168.0.100–249 like you said. New devices that reconnect now get a 192.168.0.x address and work fine. But a few PCs still keep getting a 192.168.1.x or 169.254.x.x address until I reboot them.
Technician avatar Technician
Perfect — that means the network design is now correct and the TP-Link is the only DHCP server. The stragglers just need their IP settings refreshed.

Step B — Fix PCs that still get the wrong IP address
On a Windows PC that’s misbehaving:
1) Open Network & Internet > Adapter settings, right-click Wi-Fi/Ethernet > Properties > IPv4.
2) Make sure it’s set to “Obtain an IP address automatically” and “Obtain DNS server address automatically”. If any static IP, subnet, gateway, or DNS is filled in, clear it — static values can make it look like the TP-Link router is assigning the wrong IP when it’s actually the PC forcing an old one.
3) Open Command Prompt as admin and run:
  • ipconfig /release
  • ipconfig /renew
  • ipconfig /flushdns
4) After that, check that the PC now shows an IP like 192.168.0.xxx with gateway 192.168.0.1 (your TP-Link).

For devices that showed 169.254.x.x APIPA addresses, this same process forces them to talk to the TP-Link DHCP server instead of making up their own IP.
Customer
I changed my main PC back to “Obtain IP address automatically” and did the release/renew commands. It now gets 192.168.0.120 with gateway 192.168.0.1 and works. But I have a smart TV and a printer that still show 192.168.1.x until I power cycle them. Is that just cached info too? Also, the TP-Link DHCP page shows a couple of devices with strange IPs at the bottom.
Technician avatar Technician
Yep, TVs, printers, and IoT devices often hold onto old IP information until you hard-reset their network connection.

Step C — Clean up “stubborn” devices and the TP-Link DHCP list
• For the TV and printer, open their network settings and make sure they are also set to DHCP/automatic IP, not hard-coded to 192.168.1.x. Then disconnect/reconnect Wi-Fi or unplug power for 30 seconds.
• In the TP-Link web interface, look at DHCP Clients List / Address Reservation. If you see any reserved addresses outside the 192.168.0.100–249 pool, delete or adjust them so every reservation fits inside the correct TP-Link LAN subnet.
• Avoid manually assigning addresses ending in .1, .2, or .254 unless you’re sure, so there are no IP conflicts between the router and clients.

Once each device is set to DHCP and has been reconnected, they should all pull a correct IP address, subnet mask, and default gateway from the TP-Link instead of random or wrong IP information.
Customer
After setting the TV and printer to DHCP and rebooting them, they now both get 192.168.0.x addresses and work. The DHCP list looks cleaner too. But I still worry I’ve misconfigured something on the TP-Link and it might start giving out wrong IPs again, especially since I also have a range extender plugged in upstairs.
Technician avatar Technician
Good catch mentioning the range extender — that’s the other common way a network ends up with the wrong DHCP server assigning wrong IP addresses.

Step D — Make sure extenders and access points don’t hand out IPs
• Log into your TP-Link extender or access point (or any third-party repeater) and confirm it is in “Access Point” or “Range Extender” mode, not “Router” mode.
• In its LAN/DHCP settings, make sure DHCP is disabled, and that its own management IP (for example 192.168.0.2) is in the same subnet as the main TP-Link but outside the DHCP pool so there is no IP address conflict.
• All extenders should pass DHCP requests through to your main TP-Link router, not assign their own IP range like 192.168.1.x or 10.0.0.x.

With only a single active DHCP server (the Archer) and all other boxes in bridge/AP/extender mode, your network will stop randomly giving devices a wrong IP address or gateway.
Customer
I checked the extender and it was actually in “router” mode with its own DHCP pool. I changed it to access point mode and disabled DHCP there. Now every device I test is getting a clean 192.168.0.x address with gateway 192.168.0.1 from the TP-Link. No more 192.168.1.x or 169.254.x.x so far. Anything else I should tweak so this stays stable long term?
Technician avatar Technician
Nice work — you’ve just eliminated the main reasons a TP-Link router seems to assign wrong IP addresses.

Step E — Make the fix stick
• In the TP-Link DHCP page, create address reservations for critical devices (NAS, printer, smart TV) so they always get the same correct IP in the 192.168.0.x range.
• Write down your chosen LAN IP (192.168.0.1), DHCP range, and Wi-Fi name/password so if you ever factory-reset the router you can rebuild the same layout quickly.
• Avoid plugging anything into the network that acts as a router unless you deliberately set it to bridge/AP mode with DHCP off — that includes ISP replacements, powerline kits, and extra Wi-Fi routers.
• Once in a while, spot-check a few devices to confirm they still pull the right IP address, subnet mask, default gateway and DNS from TP-Link; if you ever see a different gateway or a 169.254.x.x address again, you’ll know exactly to look for a rogue DHCP server.

With all that in place, the TP-Link router assigning wrong IP address issue shouldn’t come back, even as you add more devices or upgrade equipment.
Customer
After changing the extender and reserving IPs for a few devices, everything looks consistent. Every phone, laptop, and TV I check has the same subnet and gateway now. No more random wrong IP ranges or APIPA addresses. This was way more organized than just rebooting stuff blindly.
Technician avatar Technician
Glad to hear it — nice job cleaning up the network.

Summary: To fix a TP-Link router assigning wrong IP address problem, make the TP-Link your only DHCP server, put ISP routers and extenders into bridge/AP mode, ensure the TP-Link LAN and DHCP pool are in one subnet, and switch every device back to automatic IP/DNS. Then refresh their leases so they pick up the correct IP, subnet mask, default gateway, and DNS from the TP-Link.

If you ever see weird IPs again — 169.254 APIPA addresses, devices on the wrong subnet, or “connected, no internet” with a strange gateway — you can start a chat with an expert and we’ll trace it live with you.
Customer
Perfect. The TP-Link network finally looks clean and everything just works. Thanks again for helping me fix the wrong IP address problem the right way.

Quick answer: the accepted fix

Accepted fix when a TP-Link router is assigning wrong IP addresses: choose the TP-Link as the only DHCP server, put any ISP routers/extenders into bridge or AP mode with DHCP off, set the TP-Link LAN to a single subnet (for example 192.168.0.x) with a matching DHCP pool, then set all devices to obtain IP and DNS automatically and renew their leases so they get the correct IP, subnet mask, default gateway, and DNS.


Why TP-Link routers assign wrong IP addresses (DHCP conflicts, wrong gateway, APIPA)

Most TP-Link router assigning wrong IP address problems boil down to multiple devices trying to be the DHCP server at the same time. An ISP modem/router, a second Wi-Fi router, or a misconfigured extender can all hand out their own IP ranges and default gateways, so some clients end up on 192.168.1.x, others on 192.168.0.x, and some even fall back to 169.254.x.x APIPA addresses when they can’t reach any DHCP server at all.

Incorrect static IP settings, bad address reservations, or overlapping DHCP pools can make it look like the TP-Link is giving wrong IP information when the issue is really the configuration. Checking that you have just one active DHCP server, verifying the TP-Link LAN subnet and mask, and making every client use automatic IP/DNS are the key steps to keeping addresses consistent.

How to confirm if the wrong IP address is from TP-Link, another router, or the client

To narrow down a wrong IP address or wrong gateway problem, look at three things:

First, check the network details on an affected device. If the gateway or IP range doesn’t match your TP-Link LAN (for example, gateway 192.168.1.1 when the TP-Link is 192.168.0.1), that address is coming from another DHCP server. Second, check the TP-Link’s DHCP Clients List and Address Reservation page — if the router only shows 192.168.0.x clients but your device has a 192.168.1.x or 169.254.x.x address, the device is not actually talking to the TP-Link DHCP server.

Third, temporarily disconnect or power off any extra routers, extenders, or ISP Wi-Fi boxes and renew the client’s IP. If the device immediately gets a correct address from the TP-Link, you’ve confirmed the issue was an extra DHCP server assigning wrong IP addresses. If even with everything removed the client still keeps a wrong or static address, the problem is on the client side and you should reset its network settings.

TP-Link router assigning wrong IP address — quick troubleshooting tips

Pick one DHCP server, fix the LAN subnet, then refresh every client’s IP settings.

Fast path: confirm which device should be the main router → disable DHCP and Wi-Fi on any other routers/extenders or put them into bridge/AP mode → set the TP-Link LAN and DHCP pool to one subnet → make sure PCs, phones, TVs, and printers are all using automatic IP/DNS → release/renew IP on problem devices. These steps solve most cases where a TP-Link router assigns wrong IP addresses, wrong gateway, or 169.254 APIPA to clients.

Disclaimer: This information is AI-generated and intended for general guidance only. For advice specific to your TP-Link model, firmware, and ISP equipment, please consult a verified expert on Whizz-Tech before making decisions.


Getting Started Is Easy

Ask for help, 24/7

Members enjoy round-the-clock access to 12,000+ verified Experts for TP-Link router assigning wrong IP address, wrong default gateway, DHCP conflicts, and more.

Expert will respond in minutes

We match you with a TP-Link networking specialist who understands DHCP server settings, AP/bridge mode, LAN IP planning, and IP conflict resolution so you don’t have to debug it alone.

Save time & money

Stop guessing why devices get 169.254 APIPA or the wrong IP range. Get a clear, step-by-step TP-Link DHCP fix in chat and get back to work or streaming quickly.

FAQ

Why is my TP-Link router assigning wrong IP addresses or gateway?

A TP-Link router assigning wrong IP addresses is usually a sign of a DHCP conflict or misconfiguration. Another router, ISP modem, or extender may also be running a DHCP server and handing out a different subnet or gateway, or the TP-Link LAN and DHCP pool may not match. Disable extra DHCP servers, keep only the TP-Link issuing IPs, and make sure its LAN IP, subnet mask, and DHCP range are consistent.

Why do some devices get 169.254.x.x addresses on my TP-Link network?

An address starting with 169.254 is an Automatic Private IP Addressing (APIPA) address that devices assign to themselves when they cannot reach a DHCP server. On a TP-Link network, this usually means there is a cabling issue, the DHCP server is disabled, or a firewall/guest network is blocking DHCP traffic. Fix the DHCP server and then renew the device’s IP so it obtains a proper address from the router.

Can a range extender or second router cause wrong IP addresses?

Yes. If a range extender or second router is left in router mode with its own DHCP server, it can hand out a different IP range or default gateway than your main TP-Link. That leads to some clients landing in the wrong subnet and losing internet. Put extenders into AP/bridge mode with DHCP disabled so the main TP-Link is the only device assigning IPs.

Should I use static IPs instead of DHCP on TP-Link?

Most home networks are more reliable when devices use DHCP (automatic IP) and only the router runs a DHCP server. Static IPs are fine for a few advanced devices, but they must be in the correct subnet, outside the DHCP pool, and use the TP-Link LAN IP as the gateway. Incorrect static settings often look like the router is assigning wrong IP information when the problem is really the manual configuration.

Sources

Matt Verified Icon
Matt ● replies in < 1 min
Technician Expert
⭐⭐⭐⭐⭐ Trusted by 27,000+ customers
Avatar
Alex · Expert's Assistant