If one PC on a TP-Link Deco mesh won’t get an IP address while other devices still work, the fault is usually on that PC, on the cable or Wi‑Fi path to one Deco node, or in a Deco setting that’s blocking that device. Start with the PC’s DHCP state and connection path. Then check Deco reservations, access control, and the node or port it uses. If several devices fail at once, look at the Deco main unit, upstream router, or modem instead.
What it usually means when one PC gets no IP address
When one PC cannot get an IP address, the PC is not finishing the DHCP handshake. That is how the network hands out an address.
In practice, the problem can be on the PC itself. It can also be on the exact wired or Wi‑Fi path it uses, or farther upstream in the router or modem feeding the mesh.
If phones, tablets, and other PCs are fine, the Deco mesh is probably still handing out leases. That points to a device-specific issue. Common causes are a stale lease, a hidden static IP, a MAC address mismatch, a reservation that no longer matches the device, or a bad cable or node path.
If the PC gets an address but still cannot reach anything, that is a different problem. Look harder at an address conflict, a subnet mismatch, or a reservation that points to the wrong device.
Before you start
Use the least disruptive checks first. A reboot or a lease renew is safe. Changing subnet settings, deleting reservations, or resetting hardware is not the first move.
Before you change anything, note whether the PC is wired or on Wi‑Fi, and which Deco node or port it uses. If you can, test one other device on the same path. That tells you whether the path itself can hand out an address.
If the PC has a custom static IP set on purpose, write it down before you touch it. If you change it by mistake, you may lose access to the device until you restore the old settings.
First figure out where the break is
Start by separating a PC-only fault from a node-specific or whole-network fault. The quickest proof is to test the same PC on a different path and see whether the failure follows the machine or stays with the location.
- Check whether another device gets an IP address on the same Deco node, Ethernet port, or Wi‑Fi spot.
- Check whether the same PC fails on both wired and wireless, or only one of them.
- If you can, move the PC to a different Deco node or a different cable and retest.
| What happens | Likely cause |
|---|---|
| Only one PC fails everywhere | PC-side setting or adapter problem |
| The PC fails only on one node or port | That node, port, cable, or local path |
| Several devices fail at once | Deco-wide, upstream router, or modem issue |
If another device works on the same path, the mesh is probably healthy there. If the same PC fails everywhere, focus on the PC first before changing Deco settings.
Fast PC checks
The most common PC-side causes are a static IP left behind, DHCP turned off, a stale network profile, or an adapter that needs a reset.
- Confirm the PC is set to obtain an IP address automatically. - In Windows network settings, both the IP address and DNS settings should usually be automatic unless you set them on purpose. - If a static IP is set, remove it and switch back to automatic addressing.
- Renew the lease. - Disconnect and reconnect the cable or Wi‑Fi, or use the network renew action in Windows. - If the PC was stuck on APIPA, which is the automatic fallback address range Windows uses when it cannot reach DHCP, this often clears it.
- Restart the network adapter. - Disable and re-enable the Ethernet adapter or Wi‑Fi adapter. - If the adapter is stuck after sleep or a bad reconnect, this can be enough.
- Forget the Wi‑Fi network and join again if the PC uses wireless. - A stale profile can keep the PC trying old credentials, an old band, or a bad connection path. - If the problem started after a password change, node swap, or sleep cycle, this is a strong suspect.
- Check whether the PC is really using the path you think it is. - For Ethernet, confirm the cable is plugged into the Deco port you meant to use, not the upstream router or another switch. - For Wi‑Fi, confirm the PC is connected to the Deco SSID you expect, not a nearby guest network, extender, or old saved network name. - If the PC can see multiple similar networks, it may be joining the wrong one and never reaching the Deco node you’re testing.
If the PC still cannot get a lease after those steps, stop changing random Deco settings and confirm the connection path first.
Check the Deco side for one-device blocks
A Deco mesh can block or misdirect one computer without breaking the whole network. Usual causes are access control, an IP reservation that no longer matches the device, a MAC address change, or an address conflict on the subnet.
Look for these cases in the Deco app:
- Access control or blocking rules that may be applied to the PC.
- IP reservation entries that point to the wrong MAC address.
- A MAC address change from the PC, especially if the adapter uses MAC randomization on Wi‑Fi.
- A duplicate address on the same subnet, which can make the PC appear online but broken.
The Deco app may only let you assign a static IP to devices it has recognized. One Home Assistant user reported seeing devices in the app that could be reserved while the device they expected to manage did not appear the way they expected. If a reservation does not match the actual MAC address the PC is using, the Deco may hand out the wrong lease or no useful lease at all.
If the PC works after you remove a bad reservation or unblock the device, you have found the cause. If the same PC still fails after those checks, the problem is more likely the local connection path or a single Deco node.
Safe test order and when to stop
Use this order so you do not lose a working setup while troubleshooting. Make one small change at a time, then stop when you find the point where the IP lease returns.
- Reboot the PC first.
- Reboot the Deco node the PC uses, or power-cycle the main Deco if that is the only control you have.
- Renew the lease on the PC.
- Swap the cable or move to a different LAN port if the PC is wired.
- Forget and rejoin the Wi‑Fi network if the PC is wireless.
- Move the PC to another Deco node and test again.
- Isolate the cable by testing it with another device, or by using a different known-good cable.
If the problem follows the PC to another node, the fault is probably on the PC. If it stays with one node or one port, that Deco node, that port, or that cable is the likely cause.
That is the point where a firmware update check makes sense. Check the current TP-Link support page for the exact Deco model before updating, because firmware behavior can change. If the PC fails on every path even after you remove static settings and renew the lease, the next stop is the operating system network stack or hardware replacement for the adapter. If multiple devices lose leases at once, contact your ISP or check the upstream router and modem before replacing the PC or the Deco.
Verify the fix
After the change, confirm that the PC gets a normal IP address again and stays connected after a reboot or sleep cycle. If it is wired, unplug and reconnect the cable once to make sure the lease returns on its own. If it is on Wi‑Fi, reconnect to the same Deco network and confirm the PC comes back with the same working path.
If the PC now gets an address but breaks again only on one node, you still have a node, port, or cable problem. If the PC works on one path but not another, the difference between those paths is the clue you need.
Conclusion
If the PC still won’t get an IP address after the PC-side checks, the path tests, and the Deco reservation review, stop and narrow it to one node, one cable, or the upstream router before replacing anything.
Frequently Asked Questions
How do I know if the PC is getting no lease or the wrong one?
If the PC shows no valid IPv4 address, or it falls back to APIPA, it is usually failing DHCP outright. If it gets an address but still cannot reach the network, that points more toward a bad reservation, subnet mismatch, or IP conflict than a total lease failure.
Should I reboot the PC, Deco, or modem first?
Start with the PC, then the Deco node it uses, and only then the modem or upstream router if other devices are also affected. That order is safest because it preserves the wider network while you check the device most likely to be at fault.
Why would only one PC fail when everything else works?
A hidden static IP, a stale network profile, a changed MAC address, or a bad reservation can affect one PC without touching the rest of the mesh. A bad cable or a single Deco node can do the same thing, which is why path testing matters so much.
Sources
- Static ip on deco mesh - Configuration - Home Assistant Community (community.home-assistant.io)