169.254 IP Address: What APIPA Means and How to Fix It
A 169.254.x.x address means DHCP failed and Windows self-assigned a link-local address. Learn the causes and the built-in repairs, in order.
A 169.254.x.x address on an adapter is Windows telling you that DHCP did not complete. The machine asked for an address, heard nothing back, and fell back to Automatic Private IP Addressing (APIPA), the link-local range 169.254.0.0/16 that Windows assigns itself when no DHCP server answers. The address is the symptom. The DHCP failure is the problem, and every repair below is aimed at the reason the reply never arrived. The four-message DHCP exchange itself is covered on the DHCP page; this page is about tracing the failure to a layer and acting on it.
What the address tells you
APIPA exists so a machine can still talk to other link-local hosts on the same physical segment when no DHCP server is reachable. It is not a routable address and it carries no default gateway, so a host holding one can reach nothing beyond its own segment. When ipconfig shows 169.254.x.x with a subnet mask of 255.255.0.0 and an empty Default Gateway, the adapter never received a lease. The same symptom appears whether the cause is a disconnected cable, a Wi-Fi association that never completed, a router with DHCP switched off, or a DHCP pool that has run dry.
Causes, least destructive first
Work down this list. Each step rules out a layer before the next one is attempted.
1. The physical link or the Wi-Fi association
A cable that is unplugged, a dead switch port, or a Wi-Fi adapter that has not associated will produce APIPA because the DHCP request never leaves the machine. Check the link light on the adapter and the switch, and confirm the Wi-Fi profile is connected rather than merely saved. A wrong Wi-Fi passphrase normally shows as a failed connection rather than as an address problem, because the adapter never joins the network.
2. The router’s DHCP server
If the link is up, the next question is whether anything is answering DHCP. A router with its DHCP server disabled, or one whose address pool is exhausted, will leave every new client on APIPA while existing leases continue to work. This is the case the reader often cannot fix: on a managed network, a carrier-supplied router, or an ISP gateway, the DHCP server belongs to the provider. The correct action there is to report the symptom and the time it began, not to reset equipment the provider owns.
3. A static address left on the adapter
An adapter configured with a static address in a different subnet will not use DHCP at all, and Windows will not fall back to APIPA while a static address is set, so this case shows a wrong address rather than a 169.254 one. It belongs on the list because it produces the same loss of connectivity and the same “no valid IP configuration” complaint. If the adapter shows a static address that does not match the network, clear it and return the adapter to automatic addressing. This is a configuration error, not a fault.
4. Security software or a VPN adapter
A VPN client that installs a virtual adapter, or a firewall that filters DHCP, can prevent the request or the reply from crossing the stack. Disable the virtual adapter or the filtering component temporarily to see whether the lease returns. If it does, the interference is in that product’s configuration, not in Windows.
5. A switch port or upstream segment issue
On wired networks, a switch port assigned to a VLAN with no DHCP server, or a port that has been shut down administratively, produces APIPA on the connected host. This is again frequently outside the reader’s control on managed infrastructure.
Commands and what their output means
Run these from an elevated Command Prompt. One command per line.
ipconfig /releaseReleases the current lease. If the adapter holds an APIPA address, the release may report an error or appear to do nothing; that is expected, because APIPA is not a DHCP lease.
ipconfig /renewRequests a new lease. An error such as An error occurred while renewing interface Ethernet: unable to contact your DHCP server confirms the request went out and no reply came back. That points at causes 2 or 5, not at the local stack.
ipconfig /allShows every adapter, its DHCP status, and the lease details. Use it to confirm which adapter holds the 169.254 address and whether DHCP Enabled is Yes.
netsh winsock resetResets the Winsock catalog to a clean state. Use it when a VPN or security product has left broken layered service providers behind. A restart is required before the reset takes effect.
netsh int ip resetRewrites the TCP/IP stack registry settings to their default state. It does not remove the adapter or its driver. A restart is required. Neither reset command assigns an address; they clear corrupted state that can prevent the DHCP client from working.
sc query dhcpConfirms the DHCP Client service is running. If it is stopped, the machine cannot request a lease at all.
What people get wrong
The common misdiagnosis is to treat the 169.254 address as the fault and try to assign a static address in that range, or to conclude the network card has failed. The address is working as designed: it is the fallback Windows uses when no lease arrives. Pinning a static 169.254 address makes the machine reachable only on its own segment and hides the real problem, which is that DHCP is not completing. Replacing the adapter is a natural next step because the symptom appears on the adapter, but a link-local address says nothing about the card, because Windows assigns it whether or not anything answered. Trying the same cable and port with another device is the quicker check.
A second mistake is to reset the TCP/IP stack first. The resets are useful when a VPN or filter driver has corrupted the stack, but they do not fix a disabled DHCP server or an exhausted pool, and they cost a restart. The order above puts them after the link, the server, and the adapter configuration because those are cheaper to check and more often the cause.
When the cause is not yours to fix
| Cause | Symptom | When this does NOT apply |
|---|---|---|
| Cable or Wi-Fi association | No link light, or Wi-Fi not connected | Link is up and Wi-Fi shows connected |
| Router DHCP off or pool exhausted | Other new devices also on 169.254 | Only one machine affected while others lease fine |
| Static address left set | Adapter shows a fixed address, DHCP disabled | ipconfig /all shows DHCP Enabled: Yes |
| VPN or security filter | APIPA appears only with the product active | Lease fails with the product uninstalled |
| Switch port or VLAN | Wired only, one port affected | Wi-Fi also fails on the same network |
If the router or the switch belongs to an ISP or a carrier, the DHCP server and the port configuration are theirs. A customer-side reset of provider equipment can drop other services and is not a repair the reader should attempt. Report the failure with the time it started and the adapters affected.
Common questions
Why does my IP keep showing 169.254?
Windows assigns a 169.254 address when its DHCP request gets no reply. The address will keep returning until a DHCP server answers, the link is restored, or a static setting is cleared. Check `ipconfig /all` to confirm the adapter is set to DHCP.
Does a 169.254 address mean my network card is broken?
Usually not. Windows assigns a link-local address whether or not anything answered, so the address says nothing about the card. The failure is that no DHCP reply arrived, which is usually a server, link, or configuration problem. Trying the same cable and port with another device settles it.
Can I just set a static 169.254 address to fix it?
That hides the symptom. A 169.254 address is not routable and has no gateway, so the machine can reach only its own segment. The repair is to restore DHCP, not to pin a link-local address.
What does 'unable to contact your DHCP server' mean?
It means `ipconfig /renew` sent the request and received no reply. The local stack is working; the failure is at the DHCP server, the link, or a filter between them. That points at the router, the switch port, or a security product rather than at Windows.
Do netsh winsock reset and netsh int ip reset fix a 169.254 address?
Only when a VPN or security product has corrupted the stack. They do not assign an address and do not fix a disabled DHCP server. Both require a restart, so run them after the link, server, and adapter settings have been checked.
Read next
- Wi-Fi Keeps Disconnecting: Separating the Layers Three layers fail differently: the adapter, the wireless link, the internet beyond it. Power saving, band steering and roaming each look like a drop.
- Double NAT: What It Is and How to Fix It Double NAT occurs when two routers translate your traffic. Learn how to detect it, fix it with bridge mode, DMZ, or port forwarding, and know when you can't fix it.
- Packet Loss vs Latency: Diagnosing Lag Learn the difference between packet loss, latency, and jitter, how to measure each, and which network issues you can fix yourself.
- How DHCP Works: DORA, Leases, and Failure Modes Understand DHCP: the DORA exchange, lease lifecycle, renewal timing, and failure modes like exhausted scopes and conflicting servers.
- What Is NAT? Network Address Translation Explained Learn what NAT does, why it breaks inbound connections, and what it does and doesn't do for security. Understand the NAT table and common misconceptions.