CompTIA N10-009: DHCP Troubleshooting Workflow
DHCP troubleshooting begins with a deceptively simple question: why did this client fail to obtain an appropriate address and configuration? A self-assigned address, a lease from the wrong subnet, and a correct address with an invalid gateway can all produce the same user complaint. The most reliable way to distinguish them is to follow the client’s network state and the actual DHCP exchange rather than repeatedly restarting the device. DHCP has a defined request-response sequence, so technicians can test where an expected message failed to travel or where the server supplied the wrong information.
On this page
For candidates preparing for the CompTIA Network+ N10-009 exam, this is an applied networking-services problem, not simply a set of port numbers. The same reasoning appears in enterprise network engineering: Layer 2 reachability, relays, gateway routing, scope state and security policy can each affect whether a lease completes. The goal is to prove one stage at a time while keeping the initial failing state available as evidence.
Record the client state before changing anything
Begin with interface status, link or wireless association, assigned IPv4 address, mask, gateway, resolver addresses, lease expiration and the DHCP server identified by the client. Check whether the client is attached to the expected VLAN or SSID. An address in 169.254.0.0/16 is a useful clue that ordinary IPv4 address configuration may not have completed, but the presence of an address alone does not tell the whole story. A stale lease can remain valid while the client has moved to another network.
Compare an affected client with a working peer on the same segment. If peers receive the expected configuration, investigate the client interface, authentication, adapter selection and local security controls. If an entire VLAN is affected, prioritize the broadcast domain, DHCP relay, address scope and routes. Record outputs before release and renew: renewing changes state and can hide intermittent behavior that a later incident review needs to reproduce.
Follow the discover-offer-request-acknowledge sequence
In a common initial IPv4 lease exchange, a client sends DHCPDISCOVER; a server responds with DHCPOFFER; the client sends DHCPREQUEST; and the server confirms with DHCPACK. Retransmissions, missing responses or negative acknowledgments give diagnostic clues. A client may send a discover that never reaches the server because the access port is assigned to the wrong VLAN. The server may receive it but have no eligible addresses or policy matching that client.
A packet capture at the client or relay boundary can identify which messages exist and their timing. A client-side capture that contains requests but no offer does not prove the server is down; it only proves no offer returned to that observation point. Capture at the relay and server when necessary to distinguish a missing forward from a dropped response. Maintain synchronized clocks and enough packet context to compare the two locations.
Understand how relays cross subnet boundaries
DHCPDISCOVER is normally a local broadcast and does not automatically traverse a router. The configured DHCP relay forwards relevant requests to a server located elsewhere. Each routed VLAN should have an intentional relay address and a reachable path to the designated server. If one subnet fails while others work, verify that the relay is configured on the correct gateway interface and that firewall or ACL rules permit the expected exchanges.
The server must select the right scope, often using relay information about the originating subnet. If the relay points to an unexpected interface or scope, the client may receive a valid lease for the wrong network. Check the relay address, server scope association, route back to the relay and any DHCP security features that intentionally restrict server responses. Do not disable DHCP snooping or network access controls without confirming policy and root cause.
Check scope capacity and lease policy
A full address pool cannot satisfy new clients even when the DHCP service is running. Count free addresses, reservations, exclusions, declined addresses and active leases for the affected scope. Releasing one client lease may temporarily free space, but it does not resolve a scope that is consistently undersized for the population or burdened by unexpected lease churn. Diagnose whether new devices, shorter lease periods, guest traffic or abandoned reservations have changed demand.
Reservations and exclusions must be non-overlapping and consistent with the address plan. A manually configured device inside the dynamic pool can create an address conflict, while an incorrect reservation can repeatedly assign a device an unsuitable address. Where DHCP failover or split-scope designs exist, test one-server failure: aggregate free capacity can look healthy while the surviving partner lacks usable addresses under the configured policy.
A successful lease may still provide wrong options
The leased IP address is only part of configuration. Verify the subnet prefix, router option, DNS servers, search suffix and other approved settings that applications expect. If the gateway points outside the client’s actual network or to an unused address, local communication may work while off-subnet traffic fails. If the resolver address is wrong, users may describe an internet outage even when IP routing is healthy. Continue testing DNS resolution after DHCP if name-based symptoms remain.
Option inheritance can complicate interpretation. Global server options, scope-specific configuration, client classes and reservations may apply in different combinations. Inspect the options actually delivered in DHCPACK and accepted by the client instead of relying on one server configuration screen. A lease must be verified from the endpoint and through a representative application path before declaring a successful recovery.
Close the incident with capacity and path evidence
A good runbook includes the affected subnet and VLAN, gateway interface, relay destination, authoritative scope, expected option values and representative working client. Track free-address capacity, failed offers, decline rates and lease-renewal patterns in network baselines so scope exhaustion can be identified before users lose connectivity. Record relevant recent changes, such as VLAN moves, firewall updates or new DHCP security policy.
After repair, obtain a fresh lease, confirm expected options, reach the gateway, resolve a known name and establish a representative application connection. Explain what failed and where the evidence changed. A reliable DHCP workflow finishes with proof that the whole client path works, not merely with an address appearing in an interface summary.