Hands-on tutorial
Tutorials · Troubleshooting
How to Troubleshoot Devices That Get No IP Address (DHCP Problems)
When a device shows a 169.254 address or 'no IP', find whether the cause is the cable, the VLAN, the DHCP server, a full pool or DHCP snooping, and fix it.
Before you start
- Access to the switch and the DHCP server or gateway
- A laptop to test on the same port and VLAN
Step by step
Read the symptom
An address starting 169.254 means the device asked for an address and got no answer. A wrong subnet means it got an answer from the wrong DHCP server.
Check the link and the VLAN
Confirm the port is up and in the right access VLAN, or that the trunk carries the VLAN to the next switch.
show interfaces gi1/0/5 status show vlan brief
Check the DHCP server
Is the scope for this VLAN active, and are there free addresses? A full pool is common on guest networks with long lease times.
Check the relay
If the DHCP server is on another subnet, the Layer 3 switch or gateway needs a DHCP relay (helper address) on the VLAN interface.
interface vlan 20 ip helper-address 10.0.0.10
Check DHCP snooping
If DHCP snooping is enabled, the uplink towards the real DHCP server must be trusted, or offers are dropped.
show ip dhcp snoopingLook for a rogue DHCP server
If devices get a wrong address, find the device answering. A home router plugged in backwards is the usual cause; DHCP snooping prevents it.
Capture if needed
Capture on the client or a mirror port: you should see Discover, Offer, Request and Ack. Where the sequence stops shows where the problem is.
Commands are generic, industry-standard examples. Exact syntax and menu names vary by model and firmware; check your device's manual on the Documentation page.
Pro tips
- Shorten lease times on busy guest networks.
- Reserve addresses for printers and cameras rather than setting them statically in the pool.
- Monitor pool usage and alert at 80%.
FAQ
Frequently asked questions
What does 169.254.x.x mean?
Automatic private addressing: the device found no DHCP server and assigned itself an address, which cannot reach the internet.
Why do only some devices fail?
Usually a full pool, a VLAN missing on one trunk, or snooping blocking one switch.
Keep learning
Related guides
DHCP scopes and reservations
Read more →DHCP snooping and ARP inspection
Read more →Find and fix IP address conflicts
Read more →How to Troubleshoot Network Problems With Ping, Traceroute and MTR
Find where a connection breaks or slows down in minutes. Use ping for reachability and loss, traceroute for the path, and MTR to see loss and latency on every hop at once.
Read more →How to Capture and Read Network Traffic With Wireshark and tcpdump
When logs are not enough, look at the packets. Capture traffic with tcpdump or Wireshark, filter it down to the problem, and spot retransmissions, DNS failures, DHCP issues and TLS errors.
Read more →How to Test Network Speed Between Two Points With iperf3
Internet speed tests do not tell you how fast your LAN, Wi-Fi or site-to-site link really is. iperf3 measures throughput, loss and jitter between two machines you control.
Read more →Stuck on a step?
Ask Navijin technical support or an authorised partner for help with your configuration.