NewAI Content Creation is now live in Early Access
Turning Point Training Instituteby Training Center
Skip to content
0%
Module 7 — Essential Diagnostic ToolsLesson 4 of 5
5 min readBeginner

Where you are: Module 7 — Essential Diagnostic Tools · Checkpoint and Lab · Based on Chapter 7 of Dr. Tahseen Al Doori's Troubleshooting Essentials, including the chapter's lab exercise.

Recap

Tools turn guesses into evidence. Monitors (Task Manager, Resource Monitor, Activity Monitor, top/htop) show what a system is doing now; Device Manager shows device and driver status. Event logs (Event Viewer, Console, journalctl, /var/log) show what went wrong; the entry that matters is the one logged at the same time as the fault. Network commands show where a connection breaks, and the five-command sequence (loopback, ipconfig, gateway, 8.8.8.8, a name) applies the half-split method to the network path: the first failure shows where the fault lies. Recovery tools (troubleshooters, safe mode, System Restore/Time Machine, disk checkers, SFC) support isolation and repair: check before you repair, and back up first. Hardware tools test from the outside; disconnect power, use anti-static protection and never open power supplies or monitors.

Checkpoint quiz

A laptop is slow only while one particular application is open. Which tool gives the quickest evidence of which resource that application is consuming?

A user reports that their PC restarted unexpectedly at 14:05. What is the most useful thing to do in Event Viewer?

Running the five-command sequence: ping 127.0.0.1 works, ipconfig shows 192.168.1.40 with gateway 192.168.1.1, ping 192.168.1.1 works, ping 8.8.8.8 times out. Where is the fault most likely to be?

A fault began immediately after last night's update. Which recovery tool applies the rollback technique?

Which statement about hardware safety is correct according to the book?

Lab: Run the toolkit

Adapted from the book's Chapter 7 lab exercise.

Goal: run each essential network command, record its output, and then use the five-command sequence to show exactly which step fails first when the network is disconnected.

Safe setup: a lab computer or a virtual machine with a network connection you are allowed to disconnect. Steps 1–6 only read information and are also safe on your own computer. Step 7 (ipconfig /release and /renew) disconnects the machine: do it only on the lab computer or VM, never over a remote connection and never on someone else's device. Do not run any disk repair in this lab.

Steps:

  1. Run ipconfig /all (Windows), ip addr (Linux) or ifconfig (macOS). Record the IP address, subnet mask, default gateway and DNS servers.
  2. Run ping 127.0.0.1 and record the reply times.
  3. Run ping to your default gateway, then ping 8.8.8.8. Record replies or timeouts.
  4. Run tracert 8.8.8.8 (Windows) or traceroute 8.8.8.8 (macOS/Linux). Record the number of hops and any hop where delays jump or replies stop.
  5. Run nslookup for a site you use. Record the address returned and which DNS server answered.
  6. Run netstat -an (or ss -tuln on Linux). Record two listening ports and one established connection.
  7. On the lab machine only: run ipconfig /release, confirm the address is gone, then ipconfig /renew and record the new address. Run ipconfig /flushdns and note the confirmation message.
  8. Disconnect the network cable (or turn off Wi-Fi). Run the five-command sequence in order and stop at the first failure.
  9. Reconnect and run the sequence again to verify that every step passes.

What to record: a table of every command with its key output (one line each); a second table of the five steps after disconnection, marking pass or fail; the step that failed first and the exact message shown; and one sentence explaining what that first failure proves about the location of the fault.

Completion criteria:

  • All nine steps recorded, with real output from your machine.
  • The first failing step after disconnection correctly identified and explained.
  • A final run showing all five steps passing after reconnection (verification).
  • No disk repair commands run, and the lab machine left with a working connection.

Answers explained — 1: a monitor shows live per-process resource use; Event Viewer is history, SFC repairs system files and a cable tester checks cables. 2: match the time of the fault in the System log; clearing logs destroys evidence, and the Security log and alphabetical sorting do not target the event. 3: steps 1–3 prove the stack, address and local link, so the first failure lies beyond the router; DNS cannot be judged yet because step 4 already failed. 4: System Restore returns the system to an earlier state; the other items are hardware or diagnostic tools that change nothing. 5: the book's Safety First box says power supplies and monitors can hold dangerous charges even when unplugged; the other statements are not supported.

Sources