NetworkingNetwork+

DHCP Troubleshooting for CompTIA Network+ N10-009

DHCP troubleshooting is a core Network+ N10-009 skill tested in the Troubleshooting domain. When DHCP fails, devices cannot obtain IP configuration automatically — they fall back to APIPA (169.254.x.x) or have no IP, losing network connectivity. You must diagnose why DHCP is failing and distinguish between different failure modes.

7 min

2 sections · 7 exam key points

1 practice questions

DHCP Troubleshooting Process

Symptom identification: device has 169.254.x.x IP (APIPA) = DHCP failed. Device has 'wrong' IP (old lease, wrong scope) = DHCP assigned from wrong server or wrong scope. 'Limited connectivity' or no default gateway = DHCP provided partial config.

Verify DHCP client: 'ipconfig /release' then 'ipconfig /renew' forces a new DHCP request. If renewal succeeds, the previous lease may have been stale. If renewal fails with APIPA, the DHCP server is unreachable.

Check DHCP server reachability: DHCP uses broadcasts — broadcasts don't cross routers. If the device is on a different subnet than the DHCP server, a DHCP relay agent (IP helper) must be configured on the router. Verify: 'ip helper-address' on the router interface (Cisco), DHCP relay on the gateway appliance.

Check DHCP server and scope: Is the DHCP service running? Is the scope enabled? Is the address pool exhausted (no free leases)? Check DHCP server logs for errors. If the pool is exhausted: increase pool size, reduce lease time, or check for MAC address spoofing consuming leases.

Common DHCP Failures

Rogue DHCP server: an unauthorized DHCP server on the network responds to DISCOVER messages before the legitimate server — clients get wrong IP configuration (wrong gateway = no internet). Mitigation: DHCP snooping. Detection: check the gateway IP assigned — if it's not the real gateway, there's a rogue server.

DHCP scope exhaustion: all IPs in the pool are leased. New clients cannot get IPs. Fix: expand the address range, reduce lease time, check for devices holding leases indefinitely (especially printers with old leases from decommissioned IPs), add a second DHCP server.

DHCP relay misconfiguration: relay agent IP (ip helper-address) points to wrong server or is missing. Clients on remote subnets can't get IPs even though the DHCP server is working for local clients.

Key exam facts — Network+

APIPA (169.254.x.x) = DHCP failed — check server, relay agent, scope
'ipconfig /release' then '/renew' forces new DHCP lease attempt
DHCP relay (ip helper-address): required for DHCP across routed segments
DHCP pool exhaustion: no free IPs — expand pool, reduce lease time
Rogue DHCP server: DHCP snooping prevents; wrong gateway IP in DHCP = indicator
DHCP server logs: check for scope errors, lease conflicts
DHCP snooping: blocks rogue DHCP server responses on untrusted switch ports

Common exam traps

APIPA means the network cable is unplugged

APIPA (169.254.x.x) means DHCP failed — the cable may be connected and Layer 2 working, but the DHCP server or relay is not responding. No link light = disconnected; APIPA = DHCP failure

Practice questions — DHCP Troubleshooting

These questions are representative of what you will see on Network+ exams. The correct answer and explanation are shown immediately below each question.

Q1.All devices on a specific floor suddenly have 169.254.x.x addresses and cannot access the network. Devices on other floors work fine. The DHCP server has available leases. What is the most likely cause?

A.DHCP server is down

B.The DHCP relay agent (IP helper) on the affected floor's router interface is missing or misconfigured

C.The DHCP scope is exhausted

D.A rogue DHCP server is assigning wrong addresses

Explanation: Only one floor is affected, other floors work, and the DHCP server has available leases — this points to a relay agent problem for that specific subnet. DHCP broadcasts from the affected floor aren't reaching the DHCP server because the IP helper address is missing or wrong on the router interface serving that floor. Other floors have correctly configured relay agents and work normally.

Frequently asked questions — DHCP Troubleshooting

How do I determine if a DHCP pool is exhausted?

On Windows DHCP Server: open DHCP console, expand the scope, and look at the Address Pool and Active Leases sections. Compare available IPs to active leases. PowerShell: 'Get-DhcpServerv4ScopeStatistics'. On Linux ISC DHCP: check /var/lib/dhcpd/dhcpd.leases file. Monitoring tools (PRTG, SolarWinds) can alert when pool utilization exceeds a threshold (e.g., 80%).

Practice this topic

Network+practice questions

Test yourself on DHCP Troubleshooting

JT Exams routes you to questions in your exact weak areas — automatically, after every session.

Free practice test Start 7-Day Free Trial

No credit card · Cancel anytime