If one PC on an eero mesh won’t get a working IP address while other devices connect fine, the issue is usually on that PC, its Wi‑Fi adapter, or the path between that client and DHCP rather than the whole mesh. Start by checking whether the PC has no IP, a self-assigned IP, or a duplicate IP. Then renew the lease and test a different eero node or adapter before changing eero settings. A DHCP reservation can help later, but it won’t fix a PC that never reaches DHCP in the first place.
What the symptom means
A PC can show a Wi‑Fi connection and still fail to get a usable network address. That usually means the break is before normal internet use, often where the device asks DHCP for an IP address.
If the PC has no IP address at all, the request is not completing. In practice, that points first to the PC itself: a driver issue, VPN or security software that filters traffic, a bad adapter setting, or Wi‑Fi association trouble.
A self-assigned address means the client fell back to a local-only address because it still did not get a lease from the network. In that case, the client never completed DHCP, so DNS is not the first thing to chase.
If the PC gets a duplicate IP address, you are dealing with a conflict. That can happen when the machine uses a manual static address, an old lease is still hanging around, or a DHCP reservation overlaps with something else on the network.
Before you start
Start with the PC before you touch eero settings. When only one device is affected and everything else works, that is a strong clue that the fault is local until proven otherwise.
- Confirm the PC is actually connected to the right Wi‑Fi network.
- Make sure the PC’s IPv4 settings are set to automatic unless you intentionally use a manual address.
- Turn off any VPN client for the test.
- If you use security software that installs network filters, pause it temporarily if you can do that safely.
- If the PC recently moved from another router, remove any old static IP settings that might have been left behind.
- If the PC uses Wi‑Fi privacy features such as MAC randomization, note whether that feature is enabled for this network.
If you know the PC has a working Ethernet port, that can be a useful comparison later. If Ethernet works and Wi‑Fi does not, the wireless path is the likely problem, not eero’s general DHCP service.
Separate Wi‑Fi, DHCP, DNS, and static IP problems
The fastest way to avoid guessing is to split the failure into layers.
If the PC cannot get a valid local-network address, the problem is before DNS. That means the machine is failing at Wi‑Fi association, DHCP, or a local client setting.
If the PC gets a normal local address but websites still do not load, DNS becomes more likely. At that point, fixing DHCP alone will not help if the PC is pointed at a bad DNS server or a VPN tunnel is hijacking traffic.
If the PC gets a duplicate IP, stop treating it like a Wi‑Fi problem until you check for a manual static address, an overlapping reservation, or stale network state on the client.
A good practical check is this: if the PC cannot reliably reach the router or show a valid lease, focus on the client and DHCP path first. If it can reach local devices but fails on names like websites, focus on DNS after the address issue is fixed.
Renew the lease and clear stale network state
Use the least disruptive fix first. A fresh lease request often clears a stale state without changing anything on the mesh.
- Disconnect the PC from Wi‑Fi.
- Renew the DHCP lease on the PC.
- Disable and re-enable the Wi‑Fi adapter.
- Reboot the PC if the address still does not come back.
- Reconnect the PC to the same network and check whether it now receives a normal local IP address.
On Windows, use the network status or the command-line tools you already trust for your version of Windows. The exact command set can vary, so follow the current Microsoft documentation for your build if you need it. On macOS, renew the DHCP lease from the network settings for that Wi‑Fi interface, then reconnect and check whether the address changes.
If the PC still fails, test it in a different location near another eero node. If the failure only appears near one node, that points to coverage, local interference, or a roaming issue with that client. If the failure follows the PC everywhere, the adapter or software stack is the stronger suspect.
If you have a second Wi‑Fi band available on that network, try it too. Some clients behave differently on different bands, and eero’s client steering only helps favor a band or the nearest node; it does not guarantee the device will choose the 5 GHz or 6 GHz band or the closest eero.
If you can safely test Ethernet, do it. A lease on Ethernet but not Wi‑Fi usually means the wireless adapter, driver, privacy setting, or Wi‑Fi security software is involved, not the whole network.
Check eero settings that can interfere
Before you reset anything on the mesh, check the settings that can block one device while leaving everything else working.
- Make sure the PC is not paused in the eero app.
- Check that the PC is not being blocked by any filters or access controls you have set.
- Confirm the PC is not being excluded from the guest network if you are testing there; guest access is a separate network path.
- If you use bridge mode, remember that some advanced eero features change in bridge mode.
If the PC works on one network path but not another, compare those settings directly. A pause, a filter, or the wrong network segment can make the client look like it has a Wi‑Fi connection when it still cannot get a usable address.
A DHCP reservation can help once the client is already healthy enough to receive a lease. eero says IP reservations act like static IP addresses for devices on the eero network. That makes the device’s address predictable, but it is not a cure for a PC that cannot complete DHCP at all.
eero also notes that its networks support static IP setup at the WAN level during setup or later edits through the app, and that you should get the static IP details from your ISP before making those changes. That is useful for the internet connection itself, not for fixing one broken PC on the LAN. Do not confuse the two.
PC causes that commonly block one device
When only one PC is affected, the local software stack deserves a close look.
Driver problems can stop a wireless adapter from completing a normal lease even though the radio still shows as connected. If the issue started after an update, rollback or reinstall of the adapter driver may be the cleaner test.
VPN clients can also interfere. Some add network filters that sit between the PC and the rest of the network, so turning the VPN off for the test is a simple way to see whether it is part of the problem.
Security software can have the same effect if it inspects or filters local network traffic. If you can pause it briefly and retest, that is often more informative than changing router settings.
MAC randomization is another common trap. If the PC presents a different MAC address to the network each time, a reservation or allowlist may not match the device consistently. For troubleshooting, turn that feature off for the test network if your operating system allows it.
If the PC is still the only device failing after those checks, the adapter itself may be the issue. A USB Wi‑Fi adapter or a wired Ethernet test can help you separate a bad internal card from a broader PC software problem.
When to stop adjusting settings and escalate
Stop treating it as a simple network-setting problem if the same PC still fails after lease renewal, adapter reset, a reboot, a different node, and the PC checks above. At that point, the odds shift toward a driver, privacy setting, VPN, security stack, or failing adapter rather than eero configuration.
If the problem follows the PC everywhere but every other device still works normally, contact eero support with the exact symptom and the tests you already ran. Be ready to say whether the PC gets no IP, a self-assigned IP, or a duplicate IP, because that changes the diagnosis.
If only one eero node reliably triggers the problem after you have tested other clients, that node is the hardware to escalate. If multiple devices fail on the same node but work elsewhere, the node is the better suspect than the PC.
If the adapter is removable and another adapter works immediately, replace the original adapter instead of spending more time on router settings.
Frequently Asked Questions
Does a DHCP reservation fix a PC that has no IP address at all?
No. A reservation only helps after the PC can already ask for and receive a lease. If the machine cannot get any address, focus first on the adapter, driver, VPN, MAC randomization, or a stale local network setting. Then test again once that path is clear.
Should I change eero settings first if only one PC is broken?
Usually not. When every other device works, the fastest path is to check the PC, renew its lease, and test another node or adapter before changing eero settings. That shows whether the fault follows the device or the mesh point.
Sources
- What advanced features does eero support? | eero Support (eero.com)
- static IP assignment for each eero? - Discussion Topics - eero Community (community.eero.com)
- What is a static IP address? | eero Support (eero.com)