Lesson 8: Troubleshooting Methodology
Week of Mon, Nov 9 · lesson closes Sun, Nov 15
By the end of this lesson you can:
- →Diagnose and resolve common network connectivity problems using systematic isolation techniques. CCR-5 MSDE-CTE-IT-2.1 MSDE-CTE-IT-4.1 FC0-U71 2.4
- →Apply the CompTIA 7-step troubleshooting methodology to solve technical problems. CCR-5 MSDE-CTE-IT-2.1 MSDE-CTE-IT-4.1 FC0-U71 2.4
- →Use diagnostic tools including ping, tracert, ipconfig, and nslookup to identify issues. CCR-5 MSDE-CTE-IT-2.1 MSDE-CTE-IT-4.1 FC0-U71 2.4
- →Resolve Windows system issues using Safe Mode, sfc, DISM, and Device Manager. CCR-5 MSDE-CTE-IT-2.1 MSDE-CTE-IT-4.1 FC0-U71 3.2
Take Meerk's quiz for Lesson 8
This lesson's items
Exact due times are in Canvas.
Watch — Professor Messer
Professor Messer's Free A+ 220-1202 Training Course
Free, independent educational resource. Not affiliated with or endorsed by CompTIA. Watch, then read the notes below.
Know these cold
Troubleshooting Process
- CompTIA 7-step process: 1-Identify the problem, 2-Establish a theory, 3-Test the theory, 4-Establish an action plan, 5-Implement the solution, 6-Verify full functionality, 7-Document findings.
- Identify: gather information (what changed? when did it start? who is affected?); reproduce the problem if possible.
- Establish a theory: start with the simplest explanation (Occam's Razor) — is it plugged in? Is it on? Is the service running?
- Document: write what you found, what you tried, and what fixed it — future you (or a colleague) will be grateful.
Diagnostic Tools
- ping: sends ICMP echo to test reachability; response time in ms shows latency.
- ipconfig (Windows) / ifconfig or ip addr (Linux): shows IP address, subnet mask, default gateway, DNS.
- nslookup/dig: queries DNS to resolve a hostname or verify DNS is working.
- netstat: shows active TCP/UDP connections, listening ports, and routing table.
Windows Troubleshooting
- Startup failure: boot into Safe Mode (F8 or Shift+F8); run sfc /scannow to repair system files.
- Blue Screen of Death (BSOD): stop code indicates cause; check Event Viewer System log for the crash dump.
- Slow performance: check Task Manager (high CPU/RAM process?), disk usage (SSD near full?), run Disk Cleanup.
- Device Manager: yellow ! = driver issue; update or reinstall driver; use rollback if update caused the problem.
Network Troubleshooting
- Cannot connect to internet: check physical cable/Wi-Fi, ping 127.0.0.1 (loopback), ping default gateway, ping 8.8.8.8, then ping google.com — isolates where the failure is.
- Wrong IP (169.254.x.x = APIPA): DHCP server unreachable; check cable, check DHCP server, try ipconfig /release and /renew.
- Duplicate IP: two devices have the same IP; ARP conflict warning appears; identify and change one IP.
- DNS failure: can ping IP but not hostname; check DNS server setting (ipconfig /all); try nslookup or change DNS to 8.8.8.8.
Quick check — before the quiz
1. What is the FIRST step in the CompTIA A+ troubleshooting methodology?
2. A Windows PC receives the IP address 169.254.45.12. What does this indicate?
Meerk's quiz — open the Lesson 8 gate
10 questions, no time limit. 85% on your first attempt in a 24-hour window opens the gate. Retakes inside the window are practice — they help you learn, they don't count. Work alone; the point is to know it, not to have seen it.
Stuck?
Raise your hand. Mr. James gets a message right away and can help you remotely. Nothing else is stored — just your last name, grade, and where you're stuck.
Dinner Table Question
Ask at home: Describe a time when you fixed a tech problem by trying the simplest solution first.
En español: Describe una vez en que arreglaste un problema de tecnología intentando primero la solución más sencilla.