Is 169.254 a virus or a hardware fault?

No. It's an automatic fallback address that Windows sets when no DHCP server answers.

Can I just set a static IP address?

As a test, yes. As a fix, no: the cause (DHCP server, VLAN or relay) remains and other devices are still affected.

169.254.x.x IP address (APIPA): what it means and how to fix it

A Windows computer assigns itself an address from 169.254.0.0/16 when it gets no answer from a DHCP server (APIPA, Automatic Private IP Addressing). With it, it can reach at most neighbours on the same segment, but no gateway and no internet.

1. Recognise the symptom

ipconfig shows an address starting with 169.254, the subnet mask 255.255.0.0 and no default gateway. This isn't a client misconfiguration. It's a sign that DHCP is missing.

$ ipconfigIPv4 Address: 169.254.x.x, no default gateway

2. Check the physical layer and the network

Check the cable or Wi-Fi connection, the right switch port and the right VLAN. A port in the wrong VLAN will never reach the DHCP server.

3. Request an address again

Request a new lease. If the client still gets 169.254, the DHCP server is not answering.

$ ipconfig /releaserelease the old address

$ ipconfig /renewrequest a new address

4. Check the DHCP server

Typical server-side causes: the service is stopped, the scope is full or disabled, the wrong interface after a migration, or a missing DHCP relay (ip helper) on the router between networks.

$ systemctl status isc-dhcp-serverLinux: is the service running?

$ journalctl -u isc-dhcp-server -n 30start errors, e.g. a wrong interface

FAQ

Is 169.254 a virus or a hardware fault?: No. It's an automatic fallback address that Windows sets when no DHCP server answers.
Can I just set a static IP address?: As a test, yes. As a fix, no: the cause (DHCP server, VLAN or relay) remains and other devices are still affected.

Last updated: 2026-11-08