Use addressing symptoms to localize the first failed decision
IPv4 addressing failures often look identical to users, but the packet behavior is very different. A wrong mask changes local-versus-remote classification. A wrong gateway breaks routed destinations. APIPA points toward missing expected DHCP configuration. A duplicate address changes ownership over time. The strongest diagnosis starts by identifying which addressing decision is failing.
Symptom → likely boundary → best next artifact
| Observed clue | What it supports | Best next artifact | Do not overclaim |
|---|---|---|---|
| 169.254.x.x | Expected DHCP configuration missing | DHCP state, VLAN, scope/relay path | Not proof the DHCP server itself is down |
| Wrong gateway | Remote traffic failure | Subnet math, peer config, gateway reachability | Same-subnet traffic may still work |
| Mask too broad | Remote destination misclassified local | Prefix + ARP target | Router may be healthy |
| Mask too narrow | Local destination misclassified remote | Prefix + route/on-link table | Gateway use may be unnecessary |
| Duplicate IPv4 | Competing ownership | ARP alternation, DHCP/static inventory | Identify both owners first |
| Wrong DNS server | Name resolution issue | Resolver config + nslookup/dig | Not automatically an IP forwarding failure |
| Wrong VLAN scope | Logical placement mismatch | DHCP subnet, access VLAN, SSID mapping | Do not “fix” by changing only the mask |
| Network/broadcast assigned | Invalid ordinary host assignment | Network/broadcast calculation | Recalculate from the prefix |
| Overlapping networks | Route/VPN ambiguity | Prefix intersection + route table | Similar-looking ranges are not enough |
Swipe horizontally to see the full database table.
APIPA: 169.254.x.x
What it means
The client self-assigned an address in 169.254.0.0/16 because expected DHCP configuration was not obtained.
Inspect next
Client DHCP state, access VLAN or SSID mapping, relay/helper path, scope availability, and server reachability.
Wrong default gateway
A wrong gateway often leaves local peers reachable while remote destinations fail. Verify that the configured gateway lies inside the host's local subnet.
Subnet mask too broad
A too-broad mask makes the host believe more addresses are local than the design intends. The host may ARP directly for a remote destination instead of using its default gateway.
Subnet mask too narrow
A too-narrow mask can make a truly local destination appear remote, sending traffic toward the gateway unnecessarily.
Duplicate IPv4 address
Duplicate addresses often create intermittent or wrong-device symptoms because ARP ownership changes over time. Preserve the evidence before clearing caches.
Static address inside a dynamic DHCP pool
A static device can use a mathematically valid host address and still collide with DHCP if the pool includes that address.
Reserve or exclude static infrastructure addresses from the pool.
Wrong DNS server
If remote numeric IPs work but names fail, preserve the forwarding success and inspect the resolver configuration.
Address from the wrong VLAN scope
A valid-looking lease can still belong to the wrong logical network. The lease itself can expose the placement mistake.
Invalid network or broadcast host assignment
In conventional IPv4 subnetting, the network and broadcast addresses are not ordinary host assignments.
Overlapping IPv4 networks
Overlaps can create route ambiguity in VPNs and merged private address spaces. Calculate the ranges and prove the intersection.
DHCP scope exhaustion
A DHCP server can be reachable while the intended scope has no free leases. Existing clients may continue working while new clients fail to receive expected configuration.
Server reachable
Infrastructure responds.
Scope full
No free lease remains.
Symptom
New clients fail while existing leases persist.
Connected route changed by the wrong prefix
A wrong interface prefix can create an on-link route that keeps traffic local when the design expects the default gateway.
Compare six fields before changing anything
| Field | Why compare it |
|---|---|
| IP range | Wrong scope or static address |
| Prefix | Local/remote classification |
| Gateway | Remote forwarding |
| DNS | Name resolution |
| VLAN/SSID | Logical placement |
| DHCP lease/source | Scope and lease state |
Swipe horizontally to see the comparison table.
ARP can reveal the host's local-versus-remote decision
Local destination: ARP for the destination. Remote destination: ARP for the gateway. That makes ARP a powerful wrong-mask clue.
Use this order before moving to higher-layer troubleshooting
APIPA, wrong scope, and scope exhaustion are different failures
APIPA
No expected lease obtained.
Wrong scope
Lease obtained from the wrong logical network.
Scope exhaustion
Correct scope exists but has no free leases.
Guest Wi-Fi receives the Staff subnet
Do not repair this by changing only the client mask or gateway.
Only remote destinations fail after a static change
The gateway is the first failed dependency.
One IP intermittently reaches two different devices
Re-test the exact boundary you corrected
After fixing a mask, prove both local and remote behavior. After fixing a gateway, prove a remote destination. After fixing VLAN placement, renew the lease and confirm the intended subnet. After fixing a duplicate IP, confirm ARP ownership remains stable.
Use symptom combinations to separate similar addressing faults
One clue rarely tells the whole story. The combination of local reachability, remote reachability, ARP behavior, DHCP state, and name-resolution behavior is much more useful than any single symptom.
| Local peer | Gateway | Remote IP | Name | Stronger branch |
|---|---|---|---|---|
| Works | Fails | Fails | Fails | Gateway config / local first hop |
| Works | Works | Fails | Fails | Route / NAT / WAN / firewall |
| Works | Works | Works | Fails | DNS configuration |
| Selective | Works | Selective | Varies | Wrong mask / overlapping route |
| Intermittent | Intermittent | Intermittent | Intermittent | Duplicate address / unstable ownership |
Swipe horizontally to compare failure patterns.
Different DHCP symptoms point to different stages of the lease process
If no expected lease appears, start with client state, VLAN placement, relay path, scope availability, and server reachability. If a lease appears but from the wrong subnet, the client clearly reached a DHCP path—but not the correct logical network. If the correct scope exists but no free addresses remain, the path may be healthy while the scope is exhausted.
No lease
Path, relay, server, VLAN, or scope availability.
Wrong lease
Wrong VLAN, wrong relay target, or wrong scope-selection logic.
No free lease
Correct scope but exhausted address pool.
Prove competing ownership before changing either endpoint
Duplicate IPv4 problems are easiest to diagnose when you correlate three artifacts: ARP ownership, switch MAC learning, and address-source records. One ARP snapshot is not enough because the mapping may flip over time.
If the address alternates between two MAC addresses and both devices are physically present, the conflict is established. Then determine which assignment violates the address plan.
Too-broad and too-narrow masks fail in opposite directions
Too broad
Remote destinations can look local. The host may ARP for addresses that should be reached through the gateway.
Too narrow
Local destinations can look remote. The host may send traffic toward the gateway unnecessarily.
Both can produce partial connectivity, which is why calculating the actual network boundary is more reliable than guessing from the IP address format.
Wrong gateway and unreachable gateway are different failures
A gateway value can be mathematically local but operationally unreachable. For example, the address may fall inside the subnet while the router interface is down, the VLAN is wrong, or ARP cannot resolve. Separate the configuration question from the reachability question.
This prevents the common mistake of assuming a numerically valid gateway must be a working gateway.
Prove overlap by comparing address intervals
Overlapping networks matter because two different locations or routes may claim the same destination space. This often appears in VPNs, acquisitions, nested labs, and private-cloud links.
Once overlap is proven, inspect which route wins and whether the endpoint treats the destination as local, remote, or reachable through a tunnel.
Record where every important address came from
A useful addressing audit distinguishes static configuration, DHCP lease, DHCP reservation, router interface, VPN-assigned address, and manually entered DNS settings. Many “mystery” failures come from mixing address-management methods without documenting ownership.
| Address item | Source to record | Why it matters |
|---|---|---|
| Client IPv4 | Static or DHCP | Determines who owns configuration |
| Gateway | Static or DHCP option | Controls remote forwarding |
| DNS | DHCP, VPN, or manual | Explains resolver mismatches |
| Infrastructure IP | Static/reserved | Should not collide with dynamic pool |
| VPN address | VPN pool | May create route overlap |
Swipe horizontally to see the address-source audit.
Translate database records into scenario-based answers
A strong exam answer does not stop at naming “wrong gateway” or “duplicate IP.” It explains why the observed artifact supports that mechanism and why nearby distractors are weaker.
This structure turns memorized symptom labels into evidence-based reasoning.
Use each record as a six-part troubleshooting entry
Observed
Capture the exact value or symptom.
Expected
State the intended configuration.
Boundary
Calculate subnet or ownership limits.
Artifact
Choose the evidence that can confirm or disprove.
Correction
Make the narrowest supported change.
Verification
Repeat the original failed operation.
One endpoint shows three addressing clues at once
This capstone shows why the database should be used as a reasoning tool rather than a symptom dictionary. The DNS result is useful because it eliminates a tempting but weaker explanation, while the ARP behavior directly exposes the host's incorrect on-link classification.
24 IP Addressing Error Symptoms digital flashcards
Practice APIPA, wrong gateways, mask errors, duplicate IPv4 ownership, DHCP scopes, VLAN placement, DNS configuration, invalid host assignments, overlap, route implications, and verification.