If only one PC won’t get an IP address on Google Nest Wifi while other devices connect normally, the problem is usually on that PC, its adapter, or a bad reservation or IP conflict—not the whole Nest Wifi network. Start on the PC, then check any dock, USB Ethernet adapter, cable, or MAC-address change before you touch Nest Wifi settings. A factory reset is rarely the first fix.
Symptom: one PC fails while everything else works
The pattern that matters is simple: phones, tablets, TVs, and other PCs get online, but one machine stalls at connecting, shows no valid IP configuration, or falls back to a self-assigned address like 169.254.x.x. That usually means the PC is reaching the network differently from the others, or it is asking for an address in a way Nest Wifi can’t satisfy.
The fastest way to separate causes is to look at the link first. If there is no Wi‑Fi signal, no Ethernet link light, or the adapter keeps disconnecting, think cable, port, dock, or USB Ethernet adapter. If the link is up but the PC has no valid IP, think DHCP, static IP, reservation, MAC mismatch, or software on the PC that is blocking the lease request.
A single-device failure is a strong clue that Nest Wifi itself is still working. The goal is to find out whether the PC is failing before DHCP starts, during DHCP, or after it gets an address that conflicts with something else.
Before you start
Work from the PC outward. That keeps you from changing router settings when the fault is actually local.
- If the PC is wired, have a known-good Ethernet cable handy.
- If it uses a dock or USB Ethernet adapter, be ready to test a different USB port or bypass the dock.
- If the PC can join the Nest Wifi over Wi‑Fi, note whether the problem happens on Wi‑Fi, Ethernet, or both.
- If you have set a static IP or a reservation before, be ready to check whether the PC’s current address, gateway, and MAC still match.
- If you use a VPN client or security software with network filtering, disconnect or pause it long enough to test.
If the PC is the only device affected, start with reversible checks. Save a factory reset for the end, not the beginning.
Check the PC first
- Confirm that the PC is set to get an address automatically.
On Windows, both the IP address and DNS settings should normally be automatic unless you intentionally use a manual setup. If a leftover static IP is still in place, switch it back to automatic and try again.
- Renew the lease on the PC.
A stale lease can get stuck even when the rest of the network is fine. If you know how to do it, release and renew the address from the PC before you reboot the router.
- Forget the network, then reconnect.
For Wi‑Fi, this clears a bad saved profile. For Ethernet, it can still help if the adapter has a stale configuration tied to that network path. After reconnecting, check whether the PC gets a normal address instead of 169.254.x.x.
- Temporarily disable anything that can filter network traffic.
VPN clients, endpoint protection, and some network tools install filters or virtual adapters that can interfere with DHCP. If the PC works after turning one of these off, the router was not the real problem.
If the PC gets a valid IP after these checks, you’re done on the PC side. If it still shows no valid IP configuration or keeps self-assigning an address, move to the adapter and hardware path.
Check for adapter, dock, cable, and port problems
A bad physical path can look exactly like a DHCP problem because the request never makes it through cleanly.
- If the PC is wired, swap the Ethernet cable.
Use a known-good cable and try a different port on the router or dock. If one cable or port works and another doesn’t, the issue is hardware, not Nest Wifi settings.
- If the PC uses a dock or USB Ethernet adapter, bypass it.
Unplug the dock or adapter, reconnect it, and if possible test a different USB port or a different adapter. A flaky dock or dongle often causes one machine to fail while every other device stays fine.
- If the PC has both Wi‑Fi and Ethernet, test one at a time.
A machine can look broken when it is really trying to use the wrong adapter. Disable the path you are not testing so you know which interface is actually failing.
If the PC works directly on another cable, port, or adapter, the fault is in the hardware path. If it still fails on a clean path, the next likely cause is an IP conflict, reservation mismatch, or MAC-address change.
Check for a bad static IP, reservation, or IP conflict
A static IP can block only one PC if the address is outside the Nest Wifi DHCP range, already in use, or paired with the wrong gateway and DNS. A reservation can do the same thing if it points to the wrong hardware address.
A reservation is supposed to give one device the same IP each time. If the PC’s network identity changed, Nest Wifi may now be reserving the address for a different MAC address than the one the PC is presenting.
This is where MAC randomization can trip you up. On Wi‑Fi, some systems can use a randomized MAC address for a network. If that setting changed after you created the reservation, Nest Wifi may treat the PC as a different device and the old reservation no longer matches. The same thing can happen if you moved the PC from built-in Ethernet to a USB Ethernet adapter or dock, because that adapter has its own hardware address.
Check the PC’s current MAC address, then compare it with the reservation. If they do not match, update the reservation or turn off randomization for that network and reconnect. If you intentionally use a static IP, make sure it does not overlap with another device’s address and does not sit inside a range that the router is already handing out.
Check Nest Wifi settings before you reset anything
Before you factory-reset Nest Wifi, confirm the current network settings in the Google Home or Nest management view. The exact layout can change, so check the live interface rather than an old screenshot.
Look for three things:
- The network is online and other devices still get leases normally.
- DHCP is still enabled and there is no unusual manual address setup that would clash with the PC.
- Any reservation for this PC matches the PC’s current MAC address.
If the router is online, DHCP is on, and the reservation matches but the PC still cannot get an address, the remaining suspects are usually the PC adapter, a dock or USB Ethernet adapter, or a conflict created by a stale local profile.
Only after those checks should you think about deeper router changes. A factory reset is a last resort because it can wipe working settings and make a simple one-device problem harder to sort out.
Verify the fix
You know the fix worked when the PC stops showing a self-assigned 169.254.x.x address and receives a normal local IP from Nest Wifi again. The gateway and DNS values should also populate, and the PC should be able to reach the rest of the network without reconnecting repeatedly.
If you changed a reservation or MAC setting, reconnect once more and confirm the PC keeps the same lease or renews it cleanly. If you changed a cable, dock, or adapter, test the same setup twice so you know the result is stable, not just a one-time success.
If the PC only works after you bypass a dock or adapter, replace that hardware. If it only works after you change the reservation or MAC setting, the fix was the address mismatch, not Nest Wifi itself.
Conclusion
If the PC still won’t lease an IP after the PC-side checks, the adapter, dock, or reservation is still the best place to look next.
Frequently Asked Questions
How do I know if Nest Wifi is the problem or just this one PC?
If other devices get leases normally and only one PC fails, the PC, its adapter, or its reservation is more likely at fault. Start with the PC, then the cable or dock, before changing Nest Wifi settings.
What does a self-assigned IP mean?
A self-assigned address usually means the PC did not get a DHCP reply in time, so it assigned itself a fallback address. That points to a lease problem, adapter problem, or bad physical link more often than a general internet outage.
Should I factory-reset Nest Wifi if one PC still will not connect?
Not first. Factory reset is a last step after you have checked the PC’s IP settings, any reservation, the MAC address, and the cable, dock, or adapter.