Advertisement

ASUS router does not assign IP to one PC: what to check

If only one PC won’t get an address from your ASUS router, start with the symptom: no IP, a 169.254 APIPA address, or an IP conflict. Then check the PC’s DHCP, static IP, saved profile, cable, port, and only after that move to router settings.

Networking 7 min read
A desktop PC is connected to an ethernet cable on a home desk.

If only one PC on your ASUS router won’t get an IP address while other devices do, the PC, its saved network settings, or its link to the router is usually the first place to check. Start by checking whether the PC has no address, a self-assigned `169.254.x.x` APIPA address, or an IP conflict. Then work from the PC outward before you change router settings. In practice, the fastest fixes are to make the PC use DHCP, clear any static IP or bad saved profile, and then test another cable, port, band, or network name.

What the PC is actually showing

If the PC shows no IPv4 address at all, the adapter is not completing DHCP. If it shows 169.254.x.x, that usually means Windows gave itself an APIPA address after it did not get a lease from the router. If you see an IP conflict warning, the PC may have a duplicate address or a stale reservation somewhere on the network.

That symptom split matters because it tells you where to look first. When only one device fails and everything else on the ASUS router is fine, I’d suspect the PC, its profile, or its adapter before I blame the router.

Before you start

Use the PC that is failing, and check it on the same network name, cable, or router port that the other devices are using. If you can, test both Ethernet and Wi‑Fi so you can tell whether the problem follows the PC or only one connection type.

On the PC, make sure you can change network settings. For Windows, ASUS support specifically says the adapter should be set to obtain an IP address automatically. It also says to check that the browser is not using a proxy server when you are troubleshooting router access issues. That proxy check is not the main fix here, but it is a useful sanity check if the PC has a lot of old network software on it.

If the PC has a VPN client, a network bridge, or a virtual switch, stop and disable those for the test. Those layers can keep the machine from using normal DHCP even when the Wi‑Fi or Ethernet icon looks connected.

Fix the PC first

  1. Check that the adapter is set to get an address automatically.
Windows network setting
Obtain an IP address automatically

If the PC was set to a static address, that can block DHCP until you change it back. If the setting was already automatic, move on.

  1. Remove any bad saved profile for that network.

For Wi‑Fi, forget the network and reconnect with the correct password. For Ethernet, disable and re-enable the adapter, then reconnect the cable. A stale profile can keep an old IP, gateway, or authentication state alive even after the router is fine.

  1. Reboot the PC and try the lease again.

A restart clears a surprising amount of bad adapter state. If the PC comes back with a valid address after the restart, the problem was likely local to that machine.

  1. Renew the lease from Windows.
Command Prompt
ipconfig /release
ipconfig /renew

If the adapter was stuck on a bad lease, this often fixes it quickly. If the command finishes but the PC still comes back with 169.254.x.x or no address, the PC is still not talking to DHCP properly.

  1. Test another cable, port, band, or network name.

Use a different Ethernet cable and a different LAN port on the ASUS router if you are wired. If you are on Wi‑Fi, switch between 2.4 GHz and 5 GHz, or connect to the other SSID if your router uses separate network names. The point is to see whether the failure follows the PC or only one radio path.

If the PC works on one path but not the other, the router itself is less likely to be at fault. If it fails on both after the PC-side checks, the adapter, driver, or OS is starting to look like the real problem.

Check the ASUS router settings that can block one device

If the router is handing out addresses to other devices, the DHCP server itself is probably working. In that case, look for settings that can stop only one PC from getting a lease.

A DHCP pool that is too small or already full can leave one device out. A bad reservation can point the PC at the wrong address. ASUS support also notes that if you want to change a manual IP binding, you may need to delete the existing rule and apply the change before creating a new one in the web GUI. The router app can edit the IP address directly in the IP binding list. That matters because a stale or wrong binding can look like a DHCP failure on just one machine.

Also check access control and MAC filtering. If the router is filtering that PC’s MAC address, or if you have a rule tied to the wrong adapter MAC, the router may simply refuse to serve it while other devices keep working.

If you do change a router rule, save it and then test again from the affected PC. If the router already has a visible manual assignment or binding for that device and the PC still cannot lease an address, the next thing to check is whether the PC is actually using the MAC address you think it is. Some Wi‑Fi adapters and privacy settings can change the apparent MAC address, which makes a reservation miss the target.

When the adapter, driver, or OS is the real problem

The PC is the likely culprit when the ASUS router gives valid leases to other devices, the cable or Wi‑Fi path has been ruled out, and this one machine still cannot get a normal address after you set DHCP, clear the saved profile, and renew the lease.

That is the point where I stop chasing the router and start looking at the network adapter driver, the adapter itself, or the operating system network stack. A driver rollback, a driver update from the current ASUS or device vendor download source, or a full network reset can help. I would only go that far after the basic DHCP and profile checks above have failed.

How to confirm it is actually fixed

After the change, the PC should show a normal private IPv4 address in the same range as the rest of the network. It should not show 169.254.x.x, and it should not have an address that conflicts with another device. It should also show a default gateway that matches the ASUS router and be able to reach the local network, not just show as connected.

A good final check is simple: renew the lease, confirm the new address, then open the router page or ping another local device on the same network. If the PC can reach the router and other LAN devices, the fix held. If it gets a lease but still cannot reach anything, the problem has moved from DHCP to another layer of the connection.

Conclusion

If the PC still cannot get an address after these checks, the next step is driver or adapter-level troubleshooting on that machine, not more random router resets.

Frequently Asked Questions

How do I know if the ASUS router is actually the problem?

It is more likely the router if multiple devices fail at once, the DHCP pool is exhausted, or a router rule blocks more than one device. If every other device gets an IP normally and only one PC fails, the PC, its profile, or its adapter is the better place to look first.

Should I reboot the router or the PC first?

Restart the PC first, then renew the lease. That clears stale adapter state without changing router settings. Reboot the ASUS router only after you have checked the PC settings, the cable or Wi‑Fi path, and any reservation, access control, or MAC filter rules.

Sources