If one PC won’t get an IP address from an ISP-supplied router while other devices still work, the break is usually on that PC, its cable or Wi‑Fi link, or a router rule tied to that one device. Start by checking whether the PC actually sent a DHCP request and whether the router answered. Then work through the safe fixes in order. A manual static IP is useful only as a short test. If it works, it can prove the link is alive, but it can also hide the real DHCP fault.
What the symptom usually means
When only one PC misses its lease, the router is usually still serving addresses normally to everyone else. That narrows the fault to the PC’s DHCP client, the network link, or a router setting that applies to that device alone.
The usual clues are 169.254.x.x, no default gateway, or a duplicate address warning. 169.254.x.x means the PC asked for DHCP but did not get a reply. It self-assigned an address in the APIPA range. A missing default gateway usually means the PC has no usable route off the local network, even if it shows some kind of address. A duplicate address warning means something else on the network is already using the same IP, or the router and PC disagree about which device should own it.
Here is the fastest way to separate the failure points:
| What you see | What it usually means | Next check |
|---|---|---|
169.254.x.x | The PC did not get a DHCP reply | Check the link, the adapter settings, and router filters |
| IP address but no default gateway | The PC has partial or stale network settings | Renew the lease, then check for static IP or reservation mismatch |
| Duplicate address warning | Another device already has that IP, or the router has a stale reservation | Compare the current MAC address with the router’s record |
| PC never appears in the router client list | The router may never have answered, or the link is not reaching the router | Test cable, port, Wi‑Fi link, and adapter health |
In practice, I treat 169.254.x.x as “no lease,” not “bad internet.” That matters because the fix changes depending on whether the PC never asked, asked and got no answer, or got an address that conflicts with something already on the network.
Before you start
Use the same connection type the problem PC normally uses. If it is wired, have a known-good Ethernet cable and a known-good router port ready. If it is on Wi‑Fi, stay close enough to rule out a weak signal, and know which SSID and band the PC is supposed to use.
Before changing anything, check for a few things that can block DHCP on just one machine:
- The adapter is enabled and not stuck in airplane mode.
- The PC is set to obtain an IP address automatically, not to use a manual static IP.
- Any VPN client, security suite, or connection manager is not forcing a custom network profile.
- The router does not have a reservation, MAC filter, parental control, access rule, or lease limit aimed at this PC.
If you are unsure about a setting, stop before you change a working device into a broken one. It is safer to compare the bad PC against a device that already works on the same router than to guess at values from memory.
First check: is the problem on the PC or the router?
Start by proving where the break is. If another phone, laptop, or console gets an address from the same router on the same cable, port, or Wi‑Fi network, the router’s DHCP server is probably fine and the problem sits on the one PC.
Use the same connection type the bad PC is using. If it is wired, move the cable to a known-good port and test a different cable. If it is on Wi‑Fi, try the same SSID on another device, then test the problem PC on a different band or SSID if your router offers one. That tells you whether the link itself is the issue.
A useful clue is whether the PC shows a link but never gets a lease. Link means the adapter sees the cable or Wi‑Fi signal. Lease means the router actually answered the DHCP request. If the link looks up but the PC still sits at 169.254.x.x or shows no default gateway, the next place to look is the adapter settings or a router rule that targets only that device.
On Windows, ipconfig /all shows whether the adapter has an address, a gateway, and DHCP enabled.
ipconfig /allOn macOS, ifconfig and networksetup -getinfo can show the same kind of mismatch.
ifconfig
networksetup -getinfo Wi-FiOn Linux, ip address and nmcli dev show usually tell you whether the interface got a lease.
ip address
nmcli dev showIf the PC never appears in the router’s device list, the router likely never accepted the request. If it appears with the wrong name, wrong MAC address, or no lease, that points toward a reservation or identity mismatch.
The PC-side settings that can block DHCP
The PC can block its own lease in a few ordinary ways. The common ones are a disabled adapter, a stale static IP, a bad saved profile, or a MAC-address change that makes the router think it is a different device.
Start with the adapter state. Make sure the Ethernet or Wi‑Fi adapter is enabled, not disabled in settings, and not stuck in airplane mode. Then check that the PC is set to obtain an address automatically, not to use a manual static IP from an old network.
On Windows, open the adapter’s IPv4 settings and confirm both IP and DNS are set to automatic. If you recently copied an old config, remove the static address before testing DHCP again. A saved static address can keep the PC from asking properly, or it can leave it on the wrong subnet even if the router answers.
On macOS, check the TCP/IP settings for the interface and switch the method back to DHCP if it was set manually. Then renew the DHCP lease from the network settings panel. On Linux, NetworkManager users can flip the connection back to automatic addressing in the connection editor, or reapply the connection profile if it was altered by hand.
MAC randomization is another common snag on Wi‑Fi. Some systems randomize the Wi‑Fi MAC per network. Some USB Wi‑Fi adapters or dock NICs expose a different MAC after a driver update or a move to another port. If your router has a reservation tied to the old MAC, the PC may stop matching it. A cloned MAC can also create a duplicate identity if two adapters end up looking the same to the router.
Security software or a firewall can interfere with DHCP on a single machine, but that is less common than a bad adapter profile. Reset the network profile first, then test again before changing security software.
Router rules that can stop only one device
A router can block one device while leaving the rest of the house online. The usual causes are a DHCP reservation mismatch, MAC filtering, an access-control rule, a full address pool, or a lease conflict left behind by a changed adapter.
A reservation mismatch is very common. Some routers call it a static IP, but the router is really reserving an address for a specific MAC address through DHCP. If the PC’s MAC changed because of a new Wi‑Fi adapter, dock, or privacy setting, the reservation no longer matches. In that case the router may hand out a different address, or refuse the expected one if the pool is tight.
Check the router’s client list first. Look for the problem PC’s MAC address and see whether it has a lease, a reservation, or both. If the router shows a reservation for an old adapter ID, delete the stale entry and create a fresh one only after the PC is working again. That keeps you from pinning the wrong identity in place.
MAC filters and access controls can fail quietly. A router may allow the device to join the Wi‑Fi network but still block its traffic, or it may block the DHCP exchange before the lease is assigned. If the router has parental controls, access schedules, guest-network limits, or a deny list, check whether the PC’s MAC or hostname was added there by mistake.
Lease limits and pool exhaustion are easier to miss. If the router’s DHCP pool is too small, or a lease table is stuck, one device may be left out while others keep their old leases. Rebooting the router can clear a stuck table, but only after you confirm the PC is not blocked by a reservation or filter. Otherwise the reboot just hides the real cause for a while.
If the router supports logs, look for DHCP deny messages, MAC filter hits, or no-free-lease notices. If it does not, use the device list and the reservation screen to compare the PC’s current MAC address with what the router expects.
When to renew, forget, reset, or escalate
Use the reversible steps first, in this order. Stop if a step makes the device worse, or if it starts taking the PC from no lease to a stable address and you can browse normally.
- Renew the lease on the problem PC. On Windows, run:
ipconfig /release
ipconfig /renewOn macOS, renew the DHCP lease from the network settings for that interface. On Linux, disconnect and reconnect the connection, or renew through your network manager. If the PC gets a valid address and default gateway, the problem was a stale lease.
- Forget and rejoin the network. This is especially useful for Wi‑Fi. Removing the saved network profile clears a bad remembered setting, including a stale MAC-related profile on some systems. If the PC reconnects and gets a lease, the old profile was the fault.
- Reset only the network stack if the PC still will not ask cleanly. A Windows network reset can clear broken adapter bindings and stale TCP/IP settings. Use it only after you have checked for a manual static IP, because a reset can erase custom networking choices you may want to keep.
- Test with a static IP only as a diagnostic. A manual static IP can prove the cable, port, or Wi‑Fi link works if the PC can reach the router at all. But it can also hide the real fault, because the PC may look online even though DHCP is still broken. Use it for a short test, then put the adapter back to automatic addressing. If the static test works but DHCP does not, the issue is almost certainly in the DHCP path, reservation, or client config.
- Try a different adapter or port. If the PC works with another Ethernet port, another cable, or another USB Wi‑Fi adapter, the original network adapter is likely the problem. A flaky NIC can still show link lights and still fail DHCP.
If none of that helps, check the router’s reservation and filter screens one more time. Then call the ISP if the router is theirs and you cannot access or interpret those settings. Escalate sooner if the router’s logs show DHCP errors you cannot clear, or if every other device gets a lease while this one PC never does. If the adapter works on another network but not on this router, that also supports a router-side or reservation-side fault rather than a dead NIC.
Verify the fix
A good fix ends with the PC getting a normal lease, not just showing some kind of address. Confirm that the adapter now has a real IP from the router’s subnet, a default gateway, and working DNS if you can reach a site or the router admin page.
The PC should no longer show 169.254.x.x, a missing gateway, or repeated duplicate address warnings. It should also appear in the router’s client list with the current MAC address and a live lease. If you made a reservation, verify that the reservation matches the adapter you are actually using.
If the PC only works with a static IP and falls apart again when you switch back to DHCP, the local diagnosis is not finished. That usually means the problem is still in the DHCP path, not in general connectivity.
Conclusion
If the same PC still cannot get a lease after a clean renew, a cable or port swap, and a check for reservations or filters, stop guessing and call the ISP if it owns the router or replace the adapter if the hardware looks suspect.
Frequently Asked Questions
Should I use a static IP to fix this permanently?
Usually no. A static IP can help you test whether the link is alive, but it can also hide the real problem if DHCP, a reservation, or a MAC mismatch is what actually failed. For a normal home or small-office setup, it is better to restore DHCP and use a router reservation if you need a fixed address.
How do I know if the network adapter itself is bad?
If the same PC still fails DHCP after a different cable, a different port, a network reset, and a clean DHCP renew, but another adapter works on the same router, the original NIC is the likely fault. USB Wi‑Fi adapters and dock-based Ethernet ports are common suspects because their identity can change with drivers or hardware changes.
Sources
- How to Set Up a Static IP Address (pcmag.com)
- ISP given static IP address resets to dhcp ip address - Networking - Spiceworks Community (community.spiceworks.com)