Learn / Answers

Why doesn't my device get an IP address?

A device without an address sends a DHCP Discover and waits for an Offer. If no Offer comes back, no DHCP server answered: the server is down, out of addresses, or on a different network the request can't reach. The device then falls back to a self-assigned 169.254.x.x address and can't reach the internet.

What it looks like in the packets

  • DHCP Discover messages from 0.0.0.0 to the broadcast address 255.255.255.255, repeated.
  • No Offer, ACK, or NAK in reply.
  • Later, traffic from a 169.254.x.x address.

Common causes

  • The DHCP server (often the router) is down or its address pool is full.
  • A VLAN or switch-port problem keeps the device off the right network.
  • A missing DHCP relay (ip helper) on a routed network.
  • The capture point can't see the server's replies.

What to check

  1. Restart or check the DHCP server and its free addresses.
  2. Check the device is on the right VLAN or Wi-Fi network.
  3. On routed networks, check the relay configuration on the router.

Wireshark display filters

  • dhcpall DHCP messages
  • dhcp.option.dhcp == 1Discover messages

How Blame Finder flags it

Warning. Upload a capture and the finding links straight to the packets behind it, with the most likely culprit at the top.