
Module 9 Checkpoint and Lab: Four Network Faults
Where you are: Module 9 — Network Troubleshooting · Checkpoint · Based on Chapter 9 of Dr. Tahseen Al Doori's Troubleshooting Essentials, including the chapter's lab exercise (adapted here as a simulation).
Recap
Network faults become manageable when you use the OSI model as a map: each layer depends on the layers beneath it, so a low-level fault shows symptoms everywhere above. Ask first whether one device or all devices are affected; that halves the problem. Then work through the layers: cables, link lights and Wi-Fi at the bottom; address, subnet mask, gateway and DNS server at layer 3; name resolution at the application layer. The five-command connectivity sequence (local stack, IP configuration, gateway, internet by IP, internet by name) applies the half-split method to the path: the first failure shows the layer at fault. For slow networks, test wired, look for bandwidth users, use tracert, restart and update, and compare with the service plan.
Knowledge check
Which statement best explains why the OSI model is useful for troubleshooting?
One laptop in a busy office cannot reach any website. Everyone else is working normally. Where is the fault most likely to lie?
A desktop shows the address 169.254.40.12 and a blank default gateway. Which action does the book recommend?
Steps 1 to 4 of the connectivity sequence succeed, but ping google.com fails. What is the most useful next test?
Websites load slowly. A wired speed test is also slow, and tracert shows hop 2, the provider's first router, jumping to 150 ms for every later hop. What should you do?
Lab: Four network faults (simulated)
Goal. Adapt the book's Chapter 9 lab: diagnose four faults (a disconnected cable, an incorrect static IP address, a wrong default gateway and an incorrect DNS server). For each, record the test that revealed the fault and the OSI layer involved.
Safe setup. This is a paper simulation: the evidence below comes from a fictional lab network and needs no equipment. If your instructor runs the original lab, it must use dedicated lab or virtual machines set up by the instructor; never change the network settings of your own primary device or a production network.
The fictional lab network. Network 192.168.10.0 with subnet mask 255.255.255.0. The router (default gateway and DNS server) is 192.168.10.1. All four PCs should receive their settings automatically. Each PC has one fault.
| PC | Evidence collected (simulated) |
|---|---|
| PC-A | Link light on the network port is off. ipconfig shows Media disconnected. ping 127.0.0.1 succeeds. |
| PC-B | ping 127.0.0.1 succeeds. ipconfig shows IP 192.168.20.15, mask 255.255.255.0, gateway 192.168.10.1. A ping to 192.168.10.1 fails. |
| PC-C | ping 127.0.0.1 succeeds. ipconfig shows IP 192.168.10.23, mask 255.255.255.0, gateway 192.168.10.254. A ping to 192.168.10.254 returns Destination host unreachable. A ping to another lab PC, 192.168.10.30, succeeds. |
| PC-D | Steps 1 to 4 of the connectivity sequence succeed. ping google.com fails with could not find host. nslookup times out and shows the server 192.0.2.53. |
Steps.
- For each PC, run the five-command sequence in your head against the evidence, and mark the first step that fails.
- Decide which of the four faults the PC has. Use each fault once.
- Name the test that revealed the fault (for example "
ipconfig" or "step 5, ping by name") and the OSI layer involved, using the book's symptoms table. - Write the fix you would plan, as one change, and how you would verify it.
- For one PC of your choice, write a two-line ticket entry: cause and fix.
What to record. A table with five columns: PC · First failing step · Fault · Revealing test and OSI layer · Fix and verification.
Completion criteria. All four PCs are matched to a different fault; each row names a revealing test and a layer consistent with Figure 9.1 and the book's symptoms table; each fix is a single, reversible change with a verification step; one ticket entry is written.
Answers explained
- b — the dependency between layers is what turns the model into a testing order; it does not require memorising protocols, does not claim faults cluster at the top, and supports rather than replaces the seven steps.
- a — one device affected points to that device, its connection or its configuration; the provider, the shared router and the websites are working for everyone else.
- c — 169.254 means no DHCP response, so check the router and cable, then release and renew; DNS and browser actions sit at higher layers, and a permanent public DNS setting is not a fix for anything here.
- d — reachable by IP but not by name points to DNS, so
nslookupand the configured servers come next; the cable, modem and Wi-Fi are already proven by steps 1 to 4. - a — the delay begins at the provider's equipment and persists, and the wired test rules out Wi-Fi; present the measurements to the provider.
Lab check. PC-A: disconnected cable — first failure step 2 (ipconfig, Media disconnected), link light off; Physical (layer 1); reseat or replace the cable, verify the link light and a gateway ping. PC-B: incorrect static IP — revealed by ipconfig (address in the 192.168.20.x network, not 192.168.10.x), confirmed by the failed gateway ping; Network (layer 3); return to automatic addressing (or correct the static entry), verify a gateway ping. PC-C: wrong default gateway — ipconfig shows .254 instead of .1; the configured gateway does not answer while a local PC does; Network (layer 3); correct the gateway, verify a ping to the gateway and to 8.8.8.8. PC-D: incorrect DNS server — step 5 fails while 1 to 4 succeed, and nslookup names 192.0.2.53; Application (DNS); restore the correct DNS server (192.168.10.1, normally via DHCP), flush the cache, verify a ping by name.
Sources
- Dr. Tahseen Al Doori — Troubleshooting Essentials, University Edition (2026), Chapter 9 (Figure 9.1, §9.1–9.6, Lab Exercise); §7.3 (connectivity test sequence)
