Skip to content
FALCON CORETECHNOLOGIES

// Troubleshooting guide

DHCP clients get 169.254.x.x instead of an address

Find where DHCP breaks — the client VLAN, the relay, the server pool, or switch security features — using the four DORA messages as a map.
2 min read#ccna#dhcp#troubleshooting

Symptoms

  • Windows clients show a 169.254.x.x address
  • Clients in one VLAN get addresses, another VLAN does not
  • Some clients get addresses from the wrong subnet
  • DHCP worked until DHCP snooping was enabled

The map: four messages

  1. Discover — client broadcast.
  2. Offer — from the server (or via the relay).
  3. Request — client broadcast.
  4. Ack — server confirms.

A 169.254.x.x address (APIPA) means the client never received an Offer. Find where the Discover stops.

Is the server on the same subnet?

Yes — the broadcast reaches the server directly. Check the pool:

show ip dhcp pool
show ip dhcp binding
show ip dhcp conflict
show running-config | include excluded
  • Pool exhausted? Compare "Leased addresses" with "Total addresses".
  • Wrong network statement — the pool must match the interface's subnet.
  • Excluded range covering the whole pool.
  • Many conflicts: the router pings before offering, and any reply means a conflict. Clear with clear ip dhcp conflict * once you have found the static devices.

No — routers do not forward broadcasts. The gateway interface for the client subnet needs:

interface GigabitEthernet0/0/0.20
 ip helper-address 192.168.30.5

On the server: there must be a pool whose network contains the relay's interface address (the giaddr), and the server needs a route back to that subnet.

Is the client in the right VLAN?

show mac address-table address <client-mac> shows the port and VLAN. A port in the wrong VLAN gets an address from the wrong pool — or none.

DHCP snooping

If snooping is on:

  • The port towards the real server (uplink) must be ip dhcp snooping trust. Otherwise every Offer is dropped.
  • Option 82: the switch inserts it by default; some servers or relays drop such packets. no ip dhcp snooping information option is the common lab fix.
  • A rate limit too low on access ports may err-disable them during a storm of requests.

show ip dhcp snooping statistics and the log show what was dropped.

On the client

ipconfig /release
ipconfig /renew
ipconfig /all

Check that the NIC is enabled for DHCP and that the cable/Wi-Fi link is up. debug ip dhcp server events on a lab router shows each request arriving.