If your ASUS router stopped working right after you set a static IP, the cause is usually the WAN settings, the LAN subnet, or one device with a bad manual address. First, identify which one you changed. A wrong WAN static IP can take the whole house offline. A bad client IP can make only one PC, printer, or NAS disappear.
Start here: which static IP changed?
A static IP can mean three different things. The fix depends on which one changed: the router’s WAN address, the router’s LAN address, or the address on one device behind the router.
Use this quick split:
- If every device lost internet right after the change, check the router’s WAN settings.
- If only one device stopped working, check that device’s own IP settings.
- If local devices still talk to each other but the internet is gone, suspect the WAN side or DNS.
That split matters. A bad static IP on a client device can make the router look broken even when the router is fine.
If the whole router lost internet, check the WAN static IP
When the whole ASUS router goes offline after a WAN static IP change, compare what you entered with the ISP or the upstream modem settings. The WAN IP address, subnet mask, default gateway, and DNS server all need to match what the provider expects. If any one is wrong, the router may still link to the modem but fail to reach the internet.
Check these WAN fields first:
- IP address
- Subnet mask
- Default gateway
- DNS server
A static WAN IP outside the ISP-assigned range can break the connection. The same goes for a gateway that belongs to a different subnet, even when the cable and modem are fine. If the router worked on DHCP before and failed as soon as you switched to manual values, back out to DHCP unless you have the exact static details from the ISP.
If your ISP requires MAC address cloning for service handoff, use it only when the provider or upstream modem setup calls for it. Do not guess at that step. If the WAN fields look right but the router still will not come back, check the upstream modem settings before you keep changing the ASUS router.
If only one device broke, check its own static IP
If one PC, printer, or NAS stopped working while the rest of the network still works, the router probably is not the problem. A bad static IP on that device can block only that device’s access, which is why people often think the router failed.
Check the device’s manual IP settings against the ASUS LAN:
- Its IP address needs to be in the same local subnet as the router.
- Its subnet mask needs to match the rest of the LAN.
- Its default gateway needs to point to the ASUS router’s LAN address.
- Its DNS server needs to be valid, not a stale address from an old network.
A common mistake is hard-coding an address that used to work, then changing the router’s LAN subnet or moving the device to a different network. The device still has an IP, but it no longer belongs on that network, so it drops off until you fix the numbers.
Match the subnet and look for address conflicts
If the ASUS router’s LAN subnet overlaps the upstream modem or another router, traffic can get confused even when the static IP values look right. The ASUS LAN side needs its own subnet, and it should not collide with the modem’s network or any other router sitting upstream.
Check for these two problems:
- The ASUS LAN network should not overlap the modem’s network.
- The static address should not duplicate another device’s address.
A duplicate address is an IP conflict. It can cause random disconnects, missing local access, or a device that works for a moment and then drops again. If you recently changed the router’s LAN address, verify that the modem, the ASUS router, and any other router in the path are not using the same subnet. If they are, move one of them to a different network range before you do anything else.
If you are unsure which side owns which subnet, stop and check the upstream modem settings first. It is safer to fix the network layout than to keep editing addresses blindly.
Use reservations, then reboot in the right order
For a device on the LAN, a DHCP reservation is usually the safer alternative to hard-coding a static IP on the device itself. ASUS supports assigning a specific address to a device through the router, so the device keeps getting the same IP without you manually setting gateway, DNS, and subnet mask on the client. That is the cleaner choice for most printers, NAS units, and similar devices.
A practical recovery sequence is:
- Put the device back on automatic IP settings if it has a manual static IP.
- Create a DHCP reservation in the ASUS router for that device instead of hard-coding the address on the device.
- Save the changes.
- Reboot the router.
- Reboot the modem after the router if the WAN still does not come back.
That reboot order matters after WAN changes. If the modem and router were not power-cycled in the right sequence, the old lease or MAC binding can keep the new WAN setup from taking effect. If the router still fails after the WAN fields look correct, back out to DHCP and verify the ISP or upstream modem settings before trying a factory reset. If only one device was affected, leave the router alone and move that device back to DHCP or a reservation.
Conclusion
Once the network is stable again, leave the router on DHCP unless your ISP gave you explicit static WAN details. Use DHCP reservations for devices you want to keep on the same address.
Frequently Asked Questions
Should I use a static IP or a DHCP reservation for my printer or NAS?
Use a DHCP reservation in the ASUS router in most cases. It keeps the device on the same address without manual IP settings on the device itself. ASUS supports assigning a specific address to a device through the router.
Why does DNS matter if the ASUS router still connects to the modem?
DNS can be the missing piece even when the WAN link is up. The router may reach the network but not translate website names into addresses. If the IP, subnet mask, and gateway are right but browsing still fails, DNS is one of the first fields to recheck.