Advertisement

Netgear Orbi Not Assigning IP to One PC

When only one PC on a Netgear Orbi loses its IP address, the cause is usually local: a stale lease, bad static setting, adapter issue, or a weak link. Start with the PC, then check the cable or Wi‑Fi path, and only then look at Orbi DHCP settings.

Networking 10 min read
mesh Wi‑Fi router

If only one PC on your Netgear Orbi is not getting an IP address while everything else still works, the fault is usually on that PC, its link to the network, or a bad DHCP reservation or static setting, not the whole Orbi system. Start by checking for a stale lease or a wrong or duplicate address. Then move through the adapter, cable or Wi‑Fi link, and Orbi DHCP settings in that order. A manual static IP can get the PC online temporarily. But it is not the right fix if the link is unstable or the PC fails on every network.

What it means when only one PC fails to get an IP on Orbi

When one PC fails and other devices keep connecting normally, treat it as a single-device problem first. In practice, that usually means one of three things: the PC is not asking for DHCP correctly, Orbi is handing out the wrong address for that device, or the network link is too shaky for the lease process to complete.

A true no-lease problem usually shows up as no valid IPv4 address or an 169.254.x.x address on Windows. That APIPA range means the PC tried to get an address from DHCP but did not complete the lease.

A wrong or duplicate IP looks different. The PC may have an address, but it conflicts with another device, falls outside the normal subnet, or connects briefly and then drops. If the rest of the network is fine, do not start by blaming Orbi hardware. First, decide whether the PC is failing to ask for an address, Orbi is refusing or misassigning it, or the link itself is unstable.

Before you start

Before changing Orbi settings, check the affected PC and the connection path. That saves time and avoids chasing a router problem that is really a local setting or a bad physical link.

  • Know whether the PC is on Ethernet or Wi‑Fi.
  • If it uses a dock, USB adapter, switch, or powerline bridge, be ready to bypass it for a direct test.
  • If you can reach the Orbi admin page, keep your current settings visible so you can undo a reservation or address change if needed.
  • If the PC is already on a manual static IP, note the current address, gateway, and DNS before changing anything.

If the PC is the only device failing, and it works on another network or another connection path, that strongly points to a local PC setting or a bad link path rather than a whole-network outage.

Check the PC first

Start on the affected PC. A saved static IP, a stuck adapter setting, a VPN client, or security software can block DHCP or distort the connection so it looks like Orbi is the problem.

  1. Check whether IPv4 is set to automatic. Open the network adapter settings and make sure the PC is set to obtain an IP address automatically unless you intentionally use a static address. If an old manual address was left behind from a previous setup, remove it and switch back to automatic.
  1. Turn off any VPN client for the test. Some VPNs install network filters that interfere with DHCP or change how traffic is routed. If the PC gets an IP after the VPN is disabled, the VPN client or one of its network filters is the culprit.
  1. Pause third-party security software briefly. Some antivirus and endpoint tools install network drivers that can interfere with the handshake. Disable them only long enough to see whether the PC can obtain a lease, then turn them back on.
  1. Test the PC on another network if you can. A phone hotspot, another router, or a different wired path can show whether the PC can get a lease at all. If it does, the problem is more likely tied to Orbi settings or the current link path. If it fails everywhere, the adapter, driver, or network stack on the PC is the stronger suspect.

If the PC works elsewhere but not on Orbi, keep going. That usually points to a reservation conflict, adapter state issue, or bad link rather than a dead network card.

Rule out cable, port, dock, or weak Wi‑Fi

A bad cable, bad port, dock, or weak Wi‑Fi link can look like a DHCP problem because the adapter never completes the handshake cleanly. Rule out the physical path before changing router settings.

  1. If the PC is wired, swap the Ethernet cable first. Use a known-good cable and reseat both ends. A flaky cable can still show link lights but fail under real traffic.
  1. Try a different LAN port on the Orbi router or node. If the PC goes through a switch or dock, bypass it for one test if you can. A bad port on the dock or switch can be the real cause, even when the Orbi itself is fine.
  1. If the PC is on Wi‑Fi, move it closer to the Orbi router or node for the test. Weak signal, interference, or a poor uplink can interrupt the early part of the connection and make it look like DHCP failed. If the PC gets an address when it is nearby but not in its usual spot, the wireless link is part of the problem.
  1. Test without the dock or adapter layer. USB and Thunderbolt docks add another adapter layer and are common trouble spots. If the PC works when connected directly but not through the dock, the dock or its driver is the issue.

If the link is unstable, fix that first. Changing DHCP settings will not help if the PC cannot stay connected long enough to ask for a lease.

Check Orbi DHCP, reservations, access control, and firmware

If the PC-side checks and link checks do not solve it, move to Orbi. The settings most likely to affect one device only are the DHCP pool, a reservation, access control, and firmware.

  1. Open the Orbi admin page and check the DHCP settings. Confirm DHCP is on and that the address pool still has free addresses. If the pool is too small or has been exhausted, one device may fail while others continue to work.
  1. Look for an IP reservation for that PC. A bad reservation can pin the PC to an address another device already uses, or to an address outside the usable range. If you find one, remove it temporarily and let the PC request a fresh lease.
  1. Check access control or device blocking. If the PC was blocked by name, MAC address, or a security rule, it may fail in ways that look like a DHCP issue. Remove the block and test again.
  1. Check firmware on the Orbi router and nodes. Firmware bugs can cause odd lease behavior, especially after long uptime or after a network change. If Netgear has a current firmware update for your Orbi model, install it through the normal update path in the admin page and then retest. Check the current official source for your exact model before updating, because firmware availability and release timing can change.
  1. Clear the PC’s stale lease and renew it. On Windows 10 or Windows 11, a clean release and renew often fixes a stale lease faster than a full reboot because it forces the adapter to ask again.
Command Prompt
ipconfig /release
ipconfig /renew

If that does not help, disable and re-enable the network adapter in the PC’s network settings. That resets the adapter state without changing anything permanent. If the adapter comes back with a valid address after that, the stale lease or adapter state was the issue.

If the PC still cannot get an address after release, renew, adapter reset, and a quick check of Orbi reservations and blocks, the balance shifts back toward a PC-side filter or a bad physical link rather than Orbi hardware.

When a manual static IP helps, and when it is the wrong move

A manual static IP can be a useful temporary workaround if you need the PC online right now and you know the correct subnet, gateway, and DNS values. Use it as a bridge while you sort out a bad lease, a bad reservation, or a flaky adapter.

It is the wrong move if the PC is still dropping link, still showing APIPA, or failing on every network. In that case, a static IP can hide the problem for a while without fixing the cause.

It is also the wrong move if you are unsure of the Orbi subnet or if you suspect a duplicate address. Picking the wrong static IP can create a second conflict and make the problem harder to unwind later.

Use a static IP only as a temporary fix when the physical link is stable and you need a stopgap. If the PC only works with a manual address, something is still wrong in DHCP, the reservation table, or the adapter state. Keep troubleshooting instead of leaving it that way.

When the problem points to the PC instead of Orbi

At this point, the pattern usually tells you where the fault lives.

  • If the PC works on other networks but not on Orbi, focus on Orbi settings, a reservation, or the link path to that PC.
  • If the PC fails everywhere, suspect the adapter, its driver, the VPN client, or security software.
  • If the PC only fails through one cable, dock, port, or node, that piece of hardware is the likely culprit.

A PC-side fault is especially likely when the adapter never shows a proper lease, works after VPN or security software is disabled, or starts behaving normally on another network immediately. A network-side fault is more likely when only one reservation or one port path reproduces the issue.

Stop treating it as an Orbi problem if the same PC fails on multiple networks and with multiple adapters. That usually means the computer itself needs attention, not the mesh system.

When to stop and suspect hardware failure or contact Netgear support

Stop troubleshooting and suspect hardware failure if the problem follows a specific Orbi port, node, or adapter even after you have checked the cable, reservation, and firmware. If multiple devices start failing in the same pattern, that is also a sign the problem is no longer limited to one PC.

If the PC’s adapter fails across networks and even after you have ruled out VPN, security software, stale leases, and a bad dock, the PC hardware or its driver is the more likely problem. If the issue stays tied to one Orbi node or router port after firmware updates and DHCP checks, contact Netgear support or replace the suspect hardware.

Get support if you cannot confirm the current Orbi firmware for your exact model from the official source, or if the admin page shows settings you do not recognize and you are not sure whether changing them is safe. At that point, continuing blind is more likely to create a second problem than fix the first.

Conclusion

Once the PC gets a fresh lease again, leave it on automatic addressing unless you have a real reason to use a static IP. If it still fails, the fastest next move is to test the same PC on another network or bypass the dock, switch, or node that sits in the middle.

Frequently Asked Questions

How do I know if my PC has an APIPA address instead of a real lease?

On Windows, an APIPA address usually shows up in the `169.254.x.x` range. That means the PC did not complete a DHCP lease, so the next checks should be the adapter, link path, and Orbi reservation or DHCP settings.

Should I use a static IP to fix this permanently?

Usually not. A static IP is best as a temporary workaround when you need the PC online and you know the correct network details. If the real issue is a bad cable, VPN filter, duplicate reservation, or unstable link, a static address only hides the fault.