169.254.x.x self-assigned IP (DHCP failed) Networking Origin: Network OSI layer 7 · Application Last updated 5 Nov 2026

Networking: IPv4 address 169.254.x.x (Autoconfiguration / APIPA) — the PC couldn't get an address from DHCP

With no DHCP answer, the computer gave itself a link-local 169.254.x.x address, which only works on the local segment.

Exact message you may see 169.254 addressAutoconfiguration IPv4 Address 169.254self-assigned IP address 169.254Ethernet doesn't have a valid IP configuration
Explore the map of this error Full error map →
Seen on: Windows Networking

Meaning

A 169.254 address means the DHCP request got no usable reply. Check cable/Wi-Fi, DHCP server health and scope, VLAN and DHCP relay/helper, then ipconfig /release and /renew. Power-cycle the router if it is a home network.

Common causes

  • DHCP server down or scope exhausted
  • Cable/Wi-Fi problem between client and server
  • Wrong VLAN or missing DHCP relay (ip helper-address)
  • Firewall or switch DHCP snooping blocking replies
  • Router needs a restart

⚡ Quick fix

  1. Renew: ipconfig /release then ipconfig /renew
  2. Check the DHCP server and scope
  3. Verify the VLAN and DHCP relay configuration

Detailed fix by platform

Windows

  1. powershell
    ipconfig /release
ipconfig /renew
ipconfig /all | findstr /i "autoconfiguration dhcp"

How to diagnose

  1. Address — 169.254.x.x?
  2. DHCP server — Reachable, free leases?
  3. VLAN/relay — Correct?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: Network. Errors that are often confused with or caused by this one (click to open):

DHCPDISCOVER ... No DHCPOFFERS received — Networking: dhclient: DHCPDISCOVER on eth0 ... No DHCPOFFERS received. No working leases in persistent database - sleeping. (Networking)DHCPDISCOVER ... No D…DHCPDISCOVER: no free leases — Networking: dhcpd: DHCPDISCOVER from aa:bb:cc:dd:ee:ff via eth0: network 192.168.1.0/24: no free leases (Networking)DHCPDISCOVER: no free…PING: transmit failed. General failure. — Networking: PING: transmit failed. General failure. / ping: sendmsg: Operation not permitted (Networking)PING: transmit failed…Rogue DHCP server hands out wrong gateway/DNS — Networking: Clients receive the wrong default gateway or DNS server — a rogue DHCP server (often a home router) answers first (Networking)Rogue DHCP server han…The specified network name is no longer available (64) — Networking: Windows error 64: The specified network name is no longer available — SMB session dropped (Networking)The specified network…Windows has detected an IP address conflict — Networking: Windows has detected an IP address conflict / Duplicate address detected by 00:aa:bb:cc:dd:ee (Networking)Windows has detected …Windows: Default gateway is not available — Networking: Windows: Default gateway is not available / Diagnose Connection Problems: DHCP not enabled (Networking)Windows: Default gate…Wrong subnet mask: hosts can't reach each other — Networking: Two hosts on one LAN can't talk — subnet mask or network address mismatch (Networking)Wrong subnet mask: ho…169.254.x…

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.