FREE NETWORK TROUBLESHOOTING LEARNING PATH

WikiFree original practice workbook

The packet route

CASE STATUS: fictional/synthetic teaching material. Do not present the example as real research, employment experience or measured business performance.

OUTCOME
Produce a reproducible network incident report that separates local connectivity, name resolution, transport and application evidence.

BEFORE YOU START
Basic computer use and access to your own computer or an authorized practice environment.

CASE
The fictional Elm Office reports that a learning website is unreachable. Supplied observations: local network interface is connected; the gateway is reachable; another HTTPS site opens; the affected hostname fails to resolve; a colleague using another resolver can resolve it. These observations narrow hypotheses but do not prove a root cause.

INPUTS
Check,Supplied observation
Local interface,Connected
Gateway,Reachable
Other HTTPS website,Loads
Affected hostname lookup,Fails
Colleague lookup,Succeeds


ENTRY CHECK

Question: Does ping failure prove a host is down?

Self-check: No. ICMP may be filtered.

Question: Can a DNS error be fixed by reinstalling an application automatically?

Self-check: That action is not justified by the evidence.

Question: What should precede a change?

Self-check: A hypothesis, a safe test and a recorded baseline.

STAGE 1: Map the connection path

Prerequisite: Basic computer use and access to your own computer or an authorized practice environment.

Instruction: A request passes through local connectivity, addressing, routing, name resolution and the application protocol. Draw these dependencies before troubleshooting. Different tools observe different parts of the path, and a successful check at one layer does not prove every later layer works. Start with scope: one device, one site, one time period or a broader outage.

Practice task: Draw the path from the learner computer to a website and write five scoping questions.

Deliverable: A dependency map and incident scope.

Acceptance check: The map separates DNS from the eventual HTTPS connection.

If stuck: Do not treat the internet as a single binary working-or-broken component.

Record your work, decisions and evidence:




Record your result against the acceptance check:



STAGE 2: Inspect local and routing evidence

Prerequisite: Bring your previous output: A dependency map and incident scope.

Instruction: Read the local interface and route information without changing settings. Record the active interface, gateway and whether a route exists. A gateway response supports local reachability but says little about a remote application. Use your own computer and approved destinations; the learning task requires observation, not broad network scanning or configuration changes.

Practice task: Record interface and default-route information using the supplied operating-system command guide. Interpret the given gateway result.

Deliverable: A timestamped local-connectivity evidence sheet.

Acceptance check: Every observation names the tool and what it does and does not establish.

If stuck: Avoid copying full private network details into a public portfolio; use the synthetic case there.

Record your work, decisions and evidence:




Record your result against the acceptance check:



STAGE 3: Test the naming hypothesis

Prerequisite: Bring your previous output: A timestamped local-connectivity evidence sheet.

Instruction: A hostname must resolve to an address before many application requests can proceed. A failed lookup can involve the local resolver path, a cached result or the authoritative data; it does not identify the exact cause by itself. Compare a known-good hostname and the affected hostname, record the resolver used and preserve the error text.

Practice task: Use the supplied synthetic lookup transcript to compare the two hostnames. Write the next least-disruptive test and its possible interpretations.

Deliverable: A DNS hypothesis and evidence comparison.

Acceptance check: The report narrows the issue to name resolution without claiming a proven resolver defect.

If stuck: Do not replace a hypothesis with a confident root-cause label before the discriminating test.

Record your work, decisions and evidence:




Record your result against the acceptance check:



STAGE 4: Separate transport from application

Prerequisite: Bring your previous output: A DNS hypothesis and evidence comparison.

Instruction: Once a name resolves, a connection can still fail at transport, TLS or the application. HTTP response codes are application evidence; a DNS success is not. A certificate warning is a different symptom from a timeout. Capture the exact observed result rather than collapsing every failure into network down, and never bypass a security warning as a troubleshooting shortcut.

Practice task: Classify four supplied outcomes: lookup failure, connection timeout, certificate error and HTTP 404. Identify the next responsible team for each.

Deliverable: A symptom-to-layer triage table.

Acceptance check: HTTP 404 is distinguished from failure to reach the server at all.

If stuck: If all outcomes receive the same fix, return to the layer-specific evidence.

Record your work, decisions and evidence:




Record your result against the acceptance check:



STAGE 5: Write the escalation and verification

Prerequisite: Bring your previous output: A symptom-to-layer triage table.

Instruction: A useful incident report separates facts, hypotheses, attempted changes and results. Include a minimal reproduction, timestamps, scope and an explicit unresolved question. After an approved fix, rerun the same checks and verify the user task. One successful ping is not enough to close an incident about loading a learning page.

Practice task: Write the incident report and a closure checklist for the Elm case. Keep the root cause unresolved if the supplied evidence is insufficient.

Deliverable: A reproducible troubleshooting and escalation report.

Acceptance check: The report includes before/after checks and verifies the actual HTTPS page task.

If stuck: Do not invent a successful fix or a packet capture that was not performed.

Record your work, decisions and evidence:




Record your result against the acceptance check:



WORKED CASE
The supplied evidence makes a broad local-network outage less likely and points toward a name-resolution problem. It does not prove which resolver component is at fault. A good escalation preserves the failed lookup and proposes a discriminating test before changing settings.

FINAL PROJECT
Submit the path map, evidence sheet, hypothesis log, symptom table and incident report. Add a scenario where DNS succeeds but HTTPS times out and explain how the next test changes.

REQUIRED CRITICAL CHECK
Observed evidence is separated from hypotheses and no unperformed test or fix is reported as successful.

SCORING
Score each of the five stage acceptance checks from 0–16 (0 missing/incorrect; 8 partially supported; 16 complete and evidenced). Score the final integrated project from 0–20 (0 missing; 10 incomplete handover; 20 complete, reproducible and consistent with the case). Target: at least 80/100 AND the critical check must pass. A total score never overrides a failed critical check.

SCOPE LIMIT
This covers introductory diagnosis on authorized systems, not network engineering certification, packet forensics or penetration testing.

SOURCES AND ACCESS
Assigned public videos can be watched free. Complete the original case in a text editor, on paper or in a spreadsheet you already have. No paid course, exam or provider certificate is included.

Free Computer Networking Course by Google
WikiFree: https://wikifree.com/courses/google-computer-networking-free-video-course/
Official source: https://www.youtube.com/playlist?list=PLTZYG7bZ1u6o6wz9EF9tQt1JS-pUmmKTj
Why selected: Google public networking lessons cover layers, DNS, services and troubleshooting in a coherent sequence.

Stage 1 selected lessons:

1. How Computers Communicate in a Network (41:22)
https://www.youtube.com/watch?v=Z_hU2zm4_S8&list=PLTZYG7bZ1u6o6wz9EF9tQt1JS-pUmmKTj&index=1

Stage 2 selected lessons:

2. Understanding the Components of the Network Layer (1:01:52)
https://www.youtube.com/watch?v=I026REnvoMQ&list=PLTZYG7bZ1u6o6wz9EF9tQt1JS-pUmmKTj&index=2

Stage 3 selected lessons:

4. Networking Services: What is DNS? (36:20)
https://www.youtube.com/watch?v=X-pgKykKHfs&list=PLTZYG7bZ1u6o6wz9EF9tQt1JS-pUmmKTj&index=4

Stage 4 selected lessons:

3. Exploring the Transport and Application Layers (41:34)
https://www.youtube.com/watch?v=mnkfhMdIlEY&list=PLTZYG7bZ1u6o6wz9EF9tQt1JS-pUmmKTj&index=3

5. Networking Services: Best Practices and Technologies (30:52)
https://www.youtube.com/watch?v=-dp2YQ5kwOw&list=PLTZYG7bZ1u6o6wz9EF9tQt1JS-pUmmKTj&index=5

Stage 5 selected lessons:

7. Troubleshooting Internet Connections (49:17)
https://www.youtube.com/watch?v=-xa6dAs3h6c&list=PLTZYG7bZ1u6o6wz9EF9tQt1JS-pUmmKTj&index=7

REUSE
Original WikiFree teaching text and synthetic fixtures are supplied for personal learning and adaptation with attribution. Provider lessons remain on their original sites and retain their own terms. No provider certificate is included.