Match each wired or wireless network troubleshooting symptom on the left with its corresponding root cause on the right.
- A workstation cannot access internet resources but can ping local hosts; system IP configuration shows a valid local IP of and a default gateway of .Misconfigured or missing default gateway IP address on the host.
- An unshielded twisted-pair Ethernet cable routed alongside high-voltage fluorescent lighting ballasts suffers from high frame error rates and packet corruption.Electromagnetic interference (EMI) inducing electrical noise onto copper conductors.
- A legacy 802.11b client connecting to a 2.4 GHz wireless network causes overall throughput degradation for all active 802.11n clients.Backward-compatibility protection mechanisms and slower preamble transmission rates.
- Users in an enterprise office report frequent packet drops and wireless performance degradation where adjacent access points are configured on channels 1, 2, and 3.Adjacent-channel interference caused by spectrum overlap on the 2.4 GHz band.
Answer
Each symptom matches its specific root cause: a gateway of blocks remote routing; high-voltage lighting induces EMI on unshielded copper cabling; 802.11b legacy clients force protection frame overhead on 2.4 GHz networks; and assigning adjacent 2.4 GHz channels (1, 2, 3) causes severe frequency overlap.
Each diagnostic symptom aligns directly with its underlying network root cause: a missing/invalid default gateway () restricts host communication strictly to the local subnet; UTP cables near high-voltage light ballasts suffer from EMI; legacy 802.11b clients require airtime-consuming backward-compatibility protection frames; and deploying adjacent 2.4 GHz channels (1, 2, 3) leads to severe frequency overlap and adjacent-channel interference.
Step-by-Step Solution
Key Concept
Diagnosing common wired cabling interference, IP gateway configuration errors, and 2.4 GHz wireless channel and legacy standard issues.