Match each wired or wireless network troubleshooting symptom to its most likely underlying root cause.
- A workstation receives an IPv4 address of 169.254.14.88 and can only communicate with other clients on the local broadcast domain.DHCP server unreachability or scope exhaustion causing the client to self-assign an APIPA address.
- A user can successfully ping remote server IP addresses such as 1.1.1.1, but browser requests to website domain names time out.DNS server configuration issue or failure in name-to-IP address resolution.
- Laptops connected to a 2.4 GHz WLAN experience frequent packet loss and high latency near operating microwave ovens.Electromagnetic interference (EMI) and frequency channel overlap on the 2.4 GHz ISM band.
- A newly installed Ethernet wall outlet negotiates at 100 Mbps half-duplex with high late collisions despite being connected to a Gigabit switch port.Physical cable impairment such as a damaged conductor, split pair, or duplex mismatch.
Answer
169.254.x.x IP address assignment matches DHCP server unreachability (APIPA). Successful ping to raw IP with website name failure matches DNS resolution issue. Wi-Fi performance drops near microwave ovens match 2.4 GHz frequency EMI/channel overlap. Ethernet fallback to 100 Mbps half-duplex with collisions matches physical cable impairments or duplex mismatches.
Each diagnostic symptom directly correlates with a specific Layer 1 through Layer 7 network failure mode: APIPA (169.254.x.x) signals missing DHCP services; IP ping success with URL failure indicates DNS lookup errors; 2.4 GHz Wi-Fi drops near appliances stem from electromagnetic/RF interference; and speed/duplex negotiation failure to 100 Mbps half-duplex indicates physical cabling defects.
Step-by-Step Solution
Key Concept
Wired and Wireless Network Troubleshooting Symptoms and Root Causes