If your Netgear Orbi works on DHCP but loses internet after you switch the WAN to a static IP, the fix is usually to match the ISP details exactly. Also confirm the modem or ONT is healthy before you change anything. Check the static IP, subnet mask, default gateway, DNS, and any required PPPoE or VLAN settings. Then reboot the modem or ONT first and the Orbi second. If DHCP works again right away, the problem is in the static-IP configuration or an ISP handoff requirement, not the Wi-Fi side of the Orbi.
What the failure usually looks like
A static-IP failure on an Orbi usually appears in one of three ways. You may lose internet completely, keep local access but lose websites, or see a WAN link that looks connected but passes no traffic.
This often starts right after you save the WAN settings. The Orbi drops the working DHCP lease, tries the new static values, and then either loses the route to the internet or never gets a valid handoff from the modem or ONT.
A healthy WAN light does not prove the settings are right. If the gateway, subnet, or ISP requirements are wrong, the Orbi can still show a link while the connection is effectively dead.
Before you start
Before you change anything again, make sure the upstream device is up and stable on its own. If it is offline, in the wrong mode, or still booting, the Orbi can look like the problem when it is only reacting to a bad handoff.
Use the ISP’s current handoff details, not memory or an old note. For a static setup, the values that must match are the IP address, subnet mask, default gateway, and DNS servers. Some providers also need PPPoE credentials, tagged VLAN settings, or MAC registration.
If you are not sure whether the upstream device is healthy, stop and verify that first. A stable handoff with no internet narrows the fault to the Orbi WAN settings, the ISP’s provisioning, or an upstream requirement that was missed.
Check the modem or ONT first
Check the light status on the modem or ONT the way your ISP expects, and confirm it is online before you touch the Orbi. If you have a separate modem, make sure it is in the mode the ISP expects for an external router setup, which is often bridge mode.
If that device cannot stay online by itself, do not keep changing Orbi settings. That points to a line, provisioning, or handoff problem upstream, and the router can’t fix that.
If the handoff device is healthy but the Orbi still fails, move on to the WAN settings. At that point, the problem is most likely a wrong static-IP value or an extra ISP requirement such as PPPoE or VLAN tagging.
Match the ISP’s WAN settings exactly
Open the Orbi admin page and recheck the WAN settings field by field. Start with the WAN type and confirm it is set for static IP, not left on automatic or DHCP.
Then verify these values against the ISP handoff sheet:
- IP address
- Subnet mask
- Default gateway
- DNS servers
- PPPoE username and password, if your ISP uses them
- VLAN ID or tagging, if your ISP requires it
- WAN MAC behavior, if the ISP binds service to a registered device
The most common mistakes are a wrong subnet mask, a wrong gateway, a duplicate IP, or leaving a DHCP-style setting in place after switching to static. A wrong subnet can make the address look valid while breaking routing. A wrong gateway can do the same thing. A duplicate address can work for a moment and then fail after a reboot or when another device claims the same address.
If your ISP gave you a block of static addresses, use only the exact gateway and DNS values they provided. Do not guess which address should be used where. If the handoff sheet is unclear, stop and ask the ISP to read the values back to you.
Recheck the Orbi WAN settings that matter most
After the static values match, go back through the Orbi WAN page and check the settings that most often get overlooked.
First, confirm the router is still in router mode if that is how your network is meant to run. If the Orbi was switched into AP mode or another mode by mistake, the WAN settings will not behave the way you expect.
Next, recheck DNS. If the IP, subnet, and gateway are correct but names still do not resolve, bad DNS can make the connection look broken even when the route is actually up.
If the ISP documentation mentions a required MTU, set it only if the provider tells you to. Don’t change MTU just to experiment; a wrong value can create a new problem on top of the one you already have.
If your ISP uses PPPoE, VLAN tagging, or MAC registration, treat those as required parts of the WAN setup, not optional extras. A plain static IP is not always enough.
Restart in the right order
After you save the corrected WAN settings, reboot the devices in the right order: modem or ONT first, then Orbi.
- Save or note the current Orbi WAN settings so you can put them back if needed.
- Power off the Orbi.
- Power off the modem or ONT.
- Wait long enough for the modem or ONT to clear its session.
- Power on the modem or ONT and wait until it is fully online.
- Power on the Orbi and let it finish booting.
- Check whether the WAN status and internet access return.
If you reboot the Orbi first, it can hold onto a stale WAN state and keep failing even after the upstream device comes back. The upstream device needs to be fully up before the Orbi asks for the connection again.
Use a rollback test to prove the cause
If the static setup still fails, switch the Orbi back to the last working DHCP or automatic WAN configuration as a rollback test. This is the quickest way to prove whether the problem is specifically the static-IP config or something broader.
If internet comes back right away on DHCP, that tells you the Orbi hardware and the line can work, and the static details or ISP requirements are the part that needs attention. If it still fails even after rolling back, the issue is more likely upstream, in the modem or ONT, or in the ISP service itself.
This test is worth doing before you make more changes. It keeps you from chasing three problems at once and makes the next step much clearer.
When to stop and call the ISP or reset the Orbi
Stop local troubleshooting and contact the ISP if the upstream device is healthy, the static values match, and the Orbi still will not pass traffic. Ask the ISP to confirm the assigned static block, the correct gateway, whether the service needs tagged VLAN traffic, whether PPPoE is required, and whether MAC registration is part of the setup.
If the WAN link stays up but traffic still fails, that is usually an ISP handoff or provisioning issue, not a Wi-Fi issue. If DHCP works and static does not, that also points to a mismatch in the static details or an extra ISP requirement that has not been applied.
A factory reset is a last resort, not the first move. Do it only after you have written down the working WAN details, tried the rollback test, and confirmed that the ISP cannot find a provisioning problem. Resetting can clear a bad saved state, but it also wipes your setup and forces you to rebuild it.
Verify the fix
The fix worked if the Orbi comes back online after the upstream device and the router reboot in the correct order, the WAN status shows a valid connection, and internet access stays up after a few minutes of normal use.
Check one site by name and, if needed, one known direct IP address to separate DNS trouble from routing trouble. If web names fail but direct IP access works, DNS still needs attention. If both fail, the gateway, subnet, or ISP handoff is still wrong.
If the connection stays stable on the static setup, you’re done. If it only works on DHCP, the static-IP values or the ISP’s extra WAN requirements still need correction.
Conclusion
If the Orbi only fails after you switch to a static IP, keep the focus on the WAN handoff, not the Wi-Fi. The next step is usually to correct the ISP values or have the ISP confirm whether PPPoE, VLAN tagging, or MAC registration is also required.
Frequently Asked Questions
How do I tell if it is a DNS problem instead of a routing problem?
If local devices still work but websites by name do not, DNS is a likely suspect. If even direct internet IPs do not respond, the gateway, subnet, or ISP handoff is more likely wrong. Start by checking whether the route is up, then compare name resolution separately.
What if the ISP says I have a static IP but Orbi still will not connect?
That usually means the ISP has not given you the full WAN requirements, or one value is wrong. Ask them to confirm the static IP, subnet mask, default gateway, DNS servers, and whether PPPoE, VLAN tagging, or MAC registration is also required. Then recheck the Orbi WAN page against that list.