
Module 6 Checkpoint and Lab: Find the Hidden Fault
Where you are: Module 6 — Isolation Techniques · Checkpoint · Based on Chapter 6 of Dr. Tahseen Al Doori's Troubleshooting Essentials, including its laboratory exercise.
Recap
When the quick wins fail, isolate the fault: shrink the area where it could lie until one cause remains. The book's six techniques:
Half-split tests the midpoint and keeps the half that holds the fault; each test halves the suspects, so 8 components need at most 3 tests, 16 need 4 and 1,000 need 10. Substitution swaps in a known-good part; comparison finds the difference from a working twin; following the path works bottom-up, top-down or along the flow of data; remove-and-restore strips to the minimum and restores items one at a time; rollback undoes the last change. The book's table matches each situation to a technique.
Knowledge check
Using half-split, what is the maximum number of tests needed for a chain of 32 components?
A user's headset does not work on their laptop. You plug the same headset into a colleague's laptop and it works perfectly. Which technique did you use, and what does it suggest?
How does safe mode support the remove-and-restore technique?
Twenty identical classroom PCs share a standard configuration. One cannot connect to the shared drive. Which technique is most suitable to start with?
Only the accounting application crashes on a PC; email, the browser and everything else work. Which approach fits best?
Lab: Find the Hidden Fault (simulated)
This lab adapts the book's Chapter 6 laboratory exercise, in which a computer is connected to a printer through a network switch, the instructor introduces one hidden fault (cable, port, IP setting or driver), and students use half-split to locate it, recording each test and its result. Here it runs as a simulated paper exercise so that it needs no lab equipment and changes nothing on real devices.
Goal: locate one hidden fault in a computer → switch → printer path using half-split, in no more than three tests, with every test and result recorded.
Safe setup
- Work in pairs: an instructor (who hides the fault) and a troubleshooter. Solo learners can ask someone to write a number from 1 to 8 on a folded slip of paper.
- No real equipment is touched. If your tutor runs the original lab on real lab equipment, follow their instructions and never change settings on devices outside the lab.
The model path. Treat the print job as a signal travelling through eight stages, in order:
| Stage | Component | Typical hidden fault (from the book's list) |
|---|---|---|
| 1 | Printer driver on the computer | Wrong or corrupt driver |
| 2 | Computer's IP settings | Incorrect IP setting |
| 3 | Computer's network cable | Faulty cable |
| 4 | Switch port (computer side) | Dead port |
| 5 | Switch port (printer side) | Dead port |
| 6 | Printer's network cable | Faulty cable |
| 7 | Printer's IP settings | Incorrect IP setting |
| 8 | Printer's network interface | Printer not accepting jobs |
Steps
- The instructor secretly chooses one stage (1–8) as faulty and writes it down.
- The troubleshooter writes a problem statement: "Since [time], the computer cannot print to the network printer; no pages are produced." The quick-win checks are assumed done with no change.
- Test 1: choose the midpoint, between stages 4 and 5. Name a realistic check for that point (for example: the computer's traffic reaches the switch; the link light on port 4 is lit; the computer can reach another known-good device on the same switch). The instructor answers OK here if the fault lies after stage 4, or missing here if it lies at or before stage 4. In this model, "OK" means the print job itself arrives correctly at that point. Note that a network-only check, such as reaching another device, would not reveal a driver fault at stage 1; in a real lab, choose checks that follow the actual print job (for example, does the job appear in the printer's queue?), which is why half-split works best alongside follow the flow.
- Record the result and cross out the four cleared stages.
- Test 2: choose the midpoint of the remaining four stages, name a realistic check, and record the instructor's answer.
- Test 3: choose the midpoint of the remaining two stages, name a realistic check, and record the answer. One stage should now remain.
- Confirm with a second technique: describe how you would prove it, for example substitution (a known-good cable or port), comparison (the correct IP settings from the network documentation) or rollback (the previous driver).
- The instructor reveals the hidden stage. Swap roles and repeat at least three times, with the fault in a different half each time.
What to record (one table per round): each test number, the test point, the realistic check you named, the result, the stages remaining after the test, the confirming technique, and the time taken.
Completion criteria: at least three rounds; every round isolates the correct stage in no more than three tests; each test point is a true midpoint of the remaining stages (or a justified nearby point); each round names a sensible confirming technique; and a short reflection explains how many tests the same method would need for a path of 16 stages, and why.
Answers explained
- C. Each test halves the suspects: 32 → 16 → 8 → 4 → 2 → 1, which is five tests. Thirty-one is the worst case for one-by-one checking; 16 is a single halving.
- A. Moving the suspect part to a known-good system is substitution used in reverse. The headset works there, so it is not the cause; the first laptop (its settings, port or driver) is. Nothing suggests a recent change or a single application.
- B. Safe mode loads only essential drivers and software, giving remove-and-restore its minimal starting point. It does not repair files, roll back updates or compare with a baseline.
- C. An identical working system exists, and many devices share a standard configuration, which the book says makes comparison especially effective. There is a clear starting point, and no known change or add-ons are mentioned.
- A. When only one application is affected, start top-down. Everything else works, so the physical layers, network and monitor are clearly fine.
Sources
- Dr. Tahseen Al Doori — Troubleshooting Essentials, University Edition (2026), Chapter 6 (§6.1–6.7, Figure 6.1, Key Takeaway, Lab Exercise, Summary and Review Questions)
