NewAI Content Creation is now live in Early Access
Turning Point Training Instituteby Training Center
Skip to content
0%
Course Toolkit — Printable ResourcesLesson 4 of 10
4 min readBeginner
Downloads & resources
Download this lesson's materials, ready to use.

Toolkit 4 of 10 · Half-Split Isolation Worksheet · Based on §6.1 and §7.3 of Dr. Tahseen Al Doori's Troubleshooting Essentials, University Edition (2026). Worksheet layout by the course.

How to use this sheet

Use the half-split (divide and conquer) method when a fault lies somewhere along a long chain of components or stages, such as a network path or a signal passing through several devices. Divide the chain into two halves and test the point between them. If the first half works, the fault must lie in the second; divide that half again. Each test removes half of the remaining possibilities.

  1. List every component in order from source to destination in Part 1.
  2. Work out the maximum number of tests in Part 2.
  3. Record each test in Part 3: the midpoint you tested, the result, and which half remains.
  4. Stop when one component remains, then confirm it (for example by substitution with a known-good part).

Part 1 — The chain

Number the components from the source (1) to the destination (n).

#Component or stage#Component or stage
19
210
311
412
513
614
715
816

Source: __________________ Destination: __________________ Number of components (n): ______

Part 2 — Maximum number of tests

Each test halves the remaining possibilities, so the maximum number of tests is the number of times n can be halved until one component remains.

Components (n)Maximum tests
21
42
83
164
325
1,00010

For a number between these, round up: for example, 12 components need at most 4 tests.

My chain needs at most ______ tests.

Part 3 — Test record

TestRemaining range (from # to #)Midpoint testedHow testedResult (pass / fail)Fault now lies between # and #
11 to n
2
3
4
5

Isolated component: __________________

Confirmation test (for example, substitute a known-good part): __________________ Result: ________

Part 4 — The network path as a half-split

The book's five-command connectivity sequence applies the half-split idea to every network fault: each command tests one more part of the path, and the first command that fails shows where the fault lies.

#Command (Windows)What it provesResult
1ping 127.0.0.1The TCP/IP stack works locally
2ipconfigThe device has a valid IP address and gateway
3ping <default gateway>The device can reach its router
4ping 8.8.8.8The device can reach the internet by IP address
5ping <a name, e.g. example.com>Name resolution (DNS) works

First step that failed: ______ What this tells me: __________________

Worked illustration

(Fictional scenario.) A laptop on office Wi-Fi cannot open a website. The path has eight stages: 1 laptop, 2 Wi-Fi adapter, 3 access point, 4 switch, 5 router, 6 modem, 7 provider's network, 8 web server. With 8 stages, at most 3 tests are needed.

TestRangeMidpoint testedResultFault now lies in
11–8Stage 4: can the laptop reach a device on the switch? (ping the office file server)PassStages 5–8
25–8Stage 6: can the laptop reach the modem? (ping the modem's local address)PassStages 7–8
37–8Stage 7: does tracert to the web server stop at the first hop beyond the modem?Replies stop thereStage 7: the provider's network

Confirmation: the modem's internet light is red, other websites fail too, and the provider confirms a line fault. The modem's own connection to the line should be part of the provider's check, because test 2 proves only the modem's local side.

Sources

  • Dr. Tahseen Al Doori — Troubleshooting Essentials, University Edition (2026), §6.1 and Fig 6.1, §6.2, §7.3, §11.1