Match each wired or wireless network troubleshooting symptom to its most likely underlying root cause.
- A workstation receives an IP address starting with 169.254.x.x and cannot communicate beyond the local subnet.Unreachable or exhausted DHCP server leading to APIPA configuration.
- A Gigabit Ethernet network adapter links at only 100 Mbps when connected to a newly punched-down Cat 6 wall jack.Damaged or improperly wired cable pair preventing full 1000BASE-T 4-pair operation.
- Wireless clients on a 2.4 GHz network in a multi-tenant office building experience severe latency spikes and packet loss.Co-channel interference caused by overlapping 2.4 GHz access point channels.
- A user can access internal file servers using their IP addresses, but web browsers fail to load sites using domain names.Misconfigured or unreachable local DNS server failing hostname resolution.
Answer
The correct pairings match each network symptom to its root cause: APIPA (169.254.x.x) matches unreachable DHCP; Cat 6 linking at 100 Mbps matches damaged wire pairs preventing 4-pair Gigabit signaling; 2.4 GHz latency/loss matches co-channel interference; and IP access working without domain name loading matches DNS resolution failure.
Correctly diagnosing network issues requires matching observable Layer 1 through Layer 7 symptoms with their specific technical root causes: APIPA addresses result from failed DHCP acquisition; 100 Mbps negotiation on Gigabit links points to cable/pair defects; 2.4 GHz performance degradation stems from channel overlap; and functional IP routing paired with domain failure isolates DNS issues.
Step-by-Step Solution
Key Concept
Diagnosing common wired and wireless troubleshooting symptoms across physical, network, and service layers.