Week 9: Network Tools and Troubleshooting

A toolbox full of equipment does not make someone a technician.

Neither does memorizing ping, ipconfig, nslookup, and tracert.

The useful skill is knowing which question you are trying to answer before you reach for a tool.

A cable tester can tell you something about a copper cable path. It cannot tell you whether DNS returned the correct record. nslookup can tell you something about name resolution. It cannot prove a wall jack is wired correctly. A Wi-Fi analyzer can show radio conditions. It cannot prove an application server is healthy.

The tool matters because the boundary matters.

The system question

What evidence do I need next, and which tool can actually answer that question without changing the system first?

Use the same reasoning structure we have used since Week 1:

user report
   ↓
observable symptom
   ↓
last proven-good boundary
   ↓
first failed or uncertain boundary
   ↓
best evidence source
   ↓
controlled test
   ↓
correction
   ↓
verification

How the chapter moves

Lesson 1 turns vague network reports into a layered troubleshooting path and teaches the last-proven-good-boundary method.

Lesson 2 covers the complete named A+ tool set: crimper, cable stripper, Wi-Fi analyzer, toner probe, punchdown tool, cable tester, loopback plug, and network tap, plus software evidence tools where they help.

Lesson 3 teaches command output as bounded evidence. Interface state, IP configuration, routes, ping, traceroute, DNS output, and logs only support the claims they actually observed.

Lesson 4 works the full Core 1 network symptom set as patterns: intermittent connectivity, speed, limited connectivity, jitter, VoIP quality, port flapping, latency, interference, authentication, and intermittent internet service.

Lesson 5 turns one mixed incident into a defensible technician record with competing theories, controlled correction, verification, and remaining uncertainty.

Do not collect output because it looks technical.

Do not change three settings because you are impatient.

Do not run every tool you know.

Ask one useful question. Get evidence. Narrow the system. Repeat.