Advertisement

Ubiquiti UniFi access point does not assign IP to one PC

Start with the affected PC, then work outward to the SSID, VLAN, and DHCP path. This article shows how to prove whether the fault lives on the client, the UniFi setup, or the network behind it—without guessing.

Networking 7 min read

If one PC connects to a UniFi Wi‑Fi network but never gets a usable IP address, the fastest fix is usually on the PC, the SSID/VLAN mapping, or the DHCP path—not the access point itself. Start by forcing a new lease and checking the adapter on that PC. Then confirm it joined the intended SSID and VLAN. After that, check UniFi isolation, MAC filtering, reservations, switch tagging, and DHCP delivery.

If one PC joins Wi‑Fi but never gets an IP address

What you’re seeing means the PC can associate with the access point. The DHCP part of the connection is failing. That is why the Wi‑Fi icon can look fine while the machine still can’t reach the network.

If the PC shows a self-assigned 169.254.x.x address, it tried to get a lease and didn’t get one. If the adapter shows no usable address at all, the problem may be earlier in the connection. It could be the driver, adapter state, or a blocked network profile. In either case, a one-device failure usually points to a client issue, the wrong wireless network path, or DHCP traffic not reaching the right server.

Check the PC before you touch UniFi

Start with the affected PC. In practice, prove the client is healthy before changing Wi‑Fi settings. A stale adapter state can look exactly like a network fault.

  1. Forget the Wi‑Fi network, then reconnect to it.

This clears the saved profile and forces the PC to rebuild the connection. If it comes back with a valid address, the old profile was the problem.

  1. Make sure the wireless adapter is enabled and not stuck.

Check that the adapter is on, airplane mode is off, and the connection has not been left in a bad state by sleep, docking, or a failed reconnect. If needed, disable and re-enable the adapter, then try again.

  1. Renew the lease.

If the PC is already on the SSID, force it to ask for a fresh address.

Command Prompt
ipconfig /release
ipconfig /renew

If the renew fails, the PC still is not getting a DHCP offer. That keeps the problem in the network path or on the client, not in the browser, DNS, or anything above that.

  1. Check the Wi‑Fi driver.

A stale or broken driver can leave the PC associated to Wi‑Fi but unable to complete DHCP. Update the driver from the PC maker or adapter vendor, not just a generic updater. If the issue started after a driver update, roll back and test again.

  1. Rule out MAC randomization and local security software.

If the adapter uses a randomized MAC address, the network may see the PC as a different client each time it reconnects. For this test, turn off MAC randomization for that SSID. If endpoint security is filtering DHCP traffic, pause it long enough to see whether the lease starts working again. Then restore it and adjust policy if needed.

Make sure the PC is on the right SSID and VLAN

A one-device DHCP failure often turns out to be a path problem rather than a radio problem. The PC may be joining the right access point but the wrong wireless network. It may also land on a guest or VLAN-backed network that does not reach the DHCP server you expect.

Check the exact SSID on the PC and compare it with the wireless network the UniFi controller shows for that client. Do not rely on the SSID name alone if you have multiple profiles with similar names.

In the current UniFi interface, verify that the SSID is mapped to the intended network and VLAN. If the VLAN tag is wrong, the client can end up on a subnet where DHCP is blocked or never arrives.

Also check whether the SSID is set up as a guest network or has client isolation enabled. Those settings do not always stop DHCP directly, but they can change the path the client takes or the rules that apply to it. If other devices work and only one PC fails, compare the failing client’s network and VLAN assignment with a known-good device.

If you recently changed SSID-to-network mapping, band steering behavior, or VLAN tags, confirm those changes against a working client before you chase anything else. A mismatch can look random until you inspect the actual client path.

Use the UniFi client entry to narrow the fault

The UniFi client entry is usually the fastest way to tell whether the AP sees the device, whether it stayed associated, and whether it ever got an address. If you are using a newer UniFi interface in 2026, verify the exact labels in your current app or console, because menu names can change.

Look for these things in the client view:

  • Whether the client is connected or only briefly appears and drops off
  • Which band it joined
  • Whether the IP field is blank, self-assigned, or valid
  • Repeated reconnects or reauths
  • Any blocked, denied, or isolated status
  • Whether the client appears on the AP but never receives a lease

If the AP shows the client and the radio link looks stable, but the IP field stays blank or self-assigned, the wireless link is probably not the problem. If the client never appears properly, you are more likely dealing with authentication, SSID selection, or a policy block.

The usual mistake here is to stop at the Wi‑Fi icon. A client can be associated to Wi‑Fi and still fail DHCP because the network path underneath is wrong.

What to change if the problem stays with the PC or the SSID

Use the pattern of failure to decide where to change something. If the problem follows the PC, fix the client. If it stays with the SSID, fix the network path.

If it follows the PC:

  1. Update or roll back the wireless driver.
  2. Forget the network and reconnect.
  3. Disable and re-enable the adapter, then renew the lease again.
  4. Reset the Windows network stack if the machine is still stuck.
  5. Turn off MAC randomization for that SSID.
  6. Check local security software that may be blocking DHCP.

If it stays with the SSID:

  1. Check UniFi for MAC filtering, blocked clients, or a deny rule that hits only that device.
  2. Review client isolation and guest network settings.
  3. Verify the SSID maps to the right VLAN and network.
  4. Check the switch port and upstream router to make sure that VLAN is actually being carried.
  5. Confirm that the DHCP reservation or scope for that network is healthy.
  6. Verify that the DHCP server is receiving requests from that VLAN and sending offers back.

For DHCP testing, the key question is simple: do requests leave the PC, reach the router or DHCP server, and get a reply? If requests never reach the server, look at VLAN tagging, switch ports, and isolation rules. If requests reach the server but no offer comes back, check the scope, reservations, relay, or server health.

If those checks pass and only one PC still fails, the access point is probably not the part to blame. At that point, keep working the client, its driver state, or the upstream DHCP path instead of changing the AP again.

Frequently Asked Questions

How do I tell if the PC is really connected or just seeing the Wi‑Fi signal?

Check the IP state, not just the signal icon. If the address is blank or `169.254.x.x`, the PC associated to Wi‑Fi but did not finish DHCP.

Should I blame the UniFi access point first?

Usually not. If other devices get addresses on the same SSID, the AP is probably passing traffic and the fault is more likely on that one PC, the SSID/VLAN mapping, or the DHCP path.