Skip to content
FixingBook
Verifiedintermediateest. 15 minutes

Fix APIPA 169.254.x.x IP Address (DHCP Failure)

A device assigns itself a 169.254.x.x Automatic Private IP Address because it cannot reach a DHCP server to obtain a valid IP.

dhcpapipa169.254ip-address

Confirmed working on: Windows 10 · Windows 11 · macOS

Before you begin

Match the environmentUse this guide only for Windows 10, Windows 11, macOS or a clearly compatible setup.
Protect recoveryBack up important data and save encryption or account recovery keys before changing system state.
Know when to stopMake one change at a time and stop if the result differs from what the guide describes.

Problem overview

Your computer cannot access the network. When you check your IP address, it starts with 169.254. This indicates a failure to communicate with your router’s DHCP server, forcing the OS to assign itself a fallback address.

Common causes

  • The router is frozen or its DHCP service crashed
  • MAC address filtering is blocking your device on the router
  • IP address pool exhaustion on the router
  • Network driver or Winsock corruption

Solution 1: Restart your router

  1. Unplug the power cable from your router and modem.
  2. Wait 30 seconds.
  3. Plug them back in and wait for the lights to indicate a stable connection.
  4. Restart your computer and check if you receive a valid IP address (usually starting with 192.168 or 10.0).

Solution 2: Release and renew IP via command line

  1. Open Command Prompt as administrator.
  2. Run the following commands in order:
    ipconfig /release
    ipconfig /flushdns
    ipconfig /renew
  3. If /renew hangs and then returns an error, your computer is physically unable to reach the router.
Expert Tip

If you are on Wi-Fi, try forgetting the network and rejoining it. Sometimes cached authentication errors block the DHCP negotiation.

Solution 3: Assign a static IP as a workaround

  1. Find the IP scheme of your network from another working device (e.g., if another phone has 192.168.1.15, your scheme is 192.168.1.x).
  2. Press Windows Key + R, type ncpa.cpl, and press Enter.
  3. Right-click your adapter -> Properties -> Internet Protocol Version 4 (TCP/IPv4) -> Properties.
  4. Choose Use the following IP address.
  5. Set the IP address to a high number in the subnet to avoid conflicts (e.g., 192.168.1.200).
  6. Set the Subnet mask to 255.255.255.0.
  7. Set the Default gateway to your router’s IP (e.g., 192.168.1.1).
  8. Click OK. If internet works, the issue is strictly DHCP related on the router.

Solution 4: Disable MAC address filtering

  1. Log into your router’s admin interface using a device that has a working connection.
  2. Navigate to the Wireless, Security, or Access Control section.
  3. Look for MAC Address Filtering or Access Control List.
  4. If it is enabled, either turn it off or manually add your computer’s MAC address to the allowlist.
  5. Save settings and restart the router.
Critical

If multiple devices on the network are receiving 169.254 addresses, your router’s DHCP server has failed entirely. A factory reset of the router may be required.

Confirm the result

  1. Repeat the exact action that originally triggered the problem.
  2. Confirm the original error or symptom is gone and no new warning has appeared.
  3. If the guide changed a driver, service, package, or system setting, restart once and test again.
  4. If the result is worse or unexpected, stop. Reverse only the last change using its documented restore option; if none is documented, use your backup or qualified support.

Questions about this fix

What is a 169.254 address?

It is an Automatic Private IP Address (APIPA). Your OS assigns it when it cannot find a DHCP server to give it a proper address.

Can a 169 IP access the internet?

No, APIPA addresses are strictly for local link communication and cannot be routed to the internet.

Did this fix work for you?

Weighted Consensus Protocol

Consensus0%
Required100% (Weight 3)
Contributors0
Verified By YouNo
Your Weight--

Did this solution resolve your issue?

Confirming if this works strengthens verification statistics on the registry.

Sign In to VerifySign in required to verify

FixingTeam10,000 rep

Official Project Maintainers

The core engineering and moderation team behind FixingBook. We curate, verify, and maintain the standards of the troubleshooting ledger.

Spotted something outdated? Suggest an edit. Maintainers review submissions within 48 hours.
Share:XReddit

Discussion (0)

No comments yet. Share your experience or verify if this fixed your issue!

Join the Discussion