Case Study: The Office Without Internet
Where you are: Module 14 — Case Studies and Final Assessment · Lesson 14.1 · Based on Chapter 14 (Case Study 1) of Dr. Tahseen Al Doori's Troubleshooting Essentials.
What you'll be able to do
- Trace the book's Case Study 1 through all seven steps and state the output of each step.
- Identify the single test that proved the fault lay outside the office network.
- Name the isolation techniques and quick wins used, and evaluate each decision.
- Prepare the information a provider needs when a fault is escalated to Tier 4.
Watch: Case Study: The Office Without Internet
The video replays the case on a timeline, animates the connectivity tests along the network path from a laptop to the internet, and pauses at each decision to ask whether it was the right one. As you watch, ask:
- What did the fact that file sharing still worked tell the team?
- Which test moved the fault from "somewhere" to "outside the building"?
- Why was the provider contacted only after the power-cycle?
The case as the book tells it
Here are the facts of Case Study 1, step by step. Keep them exactly as stated: the evaluation below depends on them.
| Step | What happened (book, Case Study 1) |
|---|---|
| 1 Identify | At 08:30, all fifteen staff in a small office report no internet access. Internal file sharing still works. A power cut occurred overnight. |
| 2 Theory | Because every device is affected but the local network works, the fault is likely the modem, router or provider. |
| 3 Test | A laptop receives a valid IP address and can ping the router, but not 8.8.8.8. The modem's internet light is red. |
| 4–5 Plan and implement | The modem and router are power-cycled in order. The internet light remains red, so the provider is contacted, with the modem model and light status ready. |
| 6 Verify | The provider resets the line remotely; all staff confirm access. |
| 7 Document and prevent | The incident is logged, and a small UPS is purchased for the modem and router to ride through short power cuts. |
A UPS (uninterruptible power supply) is a battery unit that keeps equipment powered for a short time when the mains supply fails.
Step by step, with the reasoning
Step 1: three facts, three meanings
The identify step produced three facts, and each one narrows the search:
- All fifteen staff are affected. Chapter 9 calls "one device or all?" the first question, because it halves the problem immediately. When every device fails, the fault lies in shared equipment (switch, router, modem) or with the provider, not in fifteen separate laptops.
- Internal file sharing still works. The local network, including the switch and cabling, is passing traffic. That removes a large part of the shared equipment from suspicion.
- A power cut occurred overnight. This is the answer to what changed? Systems that worked yesterday and fail today usually fail because something changed in between, and a power cut is on the book's own list of typical changes.
Step 2: a short, ranked list
The theory, modem, router or provider, follows directly from the evidence. Notice what is not on the list: individual laptops, Wi-Fi settings and the switch have all been ruled out by Step 1, so no time is spent on them.
Step 3: following the path
The test applies the five-command connectivity sequence from Chapter 7, which is the half-split method applied to the network path:
ipconfig # valid IP address and default gateway: the laptop's side is fine
ping 192.168.1.1 # replies: the router is reachable (illustrative address)
ping 8.8.8.8 # Request timed out: the internet cannot be reached by IP address
The first command that fails shows where the fault lies. The laptop has a valid address and reaches the router, so everything from the laptop to the router works. It cannot reach 8.8.8.8, so the break is beyond the router. The red internet light on the modem is physical evidence that agrees: Chapter 2's principle observe before acting in practice. This is the single test that proved the fault was outside the office network (Chapter 14, review question 1): a valid address and a successful ping to the router, with a failed ping to 8.8.8.8.
Steps 4 and 5: quick win first, then escalate
The plan uses the Chapter 5 restart check for network faults: power-cycle in order, modem first, wait 60 seconds, then the router. Order matters: the modem re-establishes the line first, so that the router can then connect through it. This is cheap, safe and reversible, so it is the right first action.
When the light stays red, the team has met an escalation trigger: the fix is beyond their authority or access, because the line belongs to the provider. That is Tier 4 in Figure 13.1. They contact the provider with the modem model and light status ready, which is a small but real handover.
Step 6: everyone confirms
The provider resets the line remotely. Verification is not "the light is green": all staff confirm access. That matches Step 6 and Chapter 13's rule to confirm with users before closing.
Step 7: document and prevent
The incident is logged, and a UPS is bought so that the modem and router can ride through short power cuts. The power cut was the change that triggered the fault, so the preventive measure targets it directly.
Evaluating the decisions
| Decision | Technique or principle | Assessment |
|---|---|---|
| Asked whether all devices were affected | Scoping (Chapter 9); halves the problem | Strong: ruled out fifteen individual devices at once |
| Noted that file sharing still worked | Comparison of what works with what fails | Strong: cleared the local network |
| Ran ipconfig, then pinged the router and 8.8.8.8 | Follow the path; half-split on the network path | Strong: located the break beyond the router |
| Looked at the modem's lights | Observe before acting | Strong: physical evidence agreed with the test |
| Power-cycled modem, then router | Quick win (restart), in the correct order | Correct: cheap and safe before escalating |
| Contacted the provider with evidence | Escalation to Tier 4 with a handover | Correct: the fault was beyond the office's access |
| Logged the incident and bought a UPS | Documentation and prevention | Good: addresses the triggering change |
What might you do differently? The book invites this question. Here are points worth discussing (our commentary, not part of the case):
- Give the provider a fuller handover. Applying Lesson 13.2, the call could also include when the outage started, the overnight power cut, the tests already run and their results, and that fifteen users are affected. That stops the provider asking you to repeat checks.
- Keep users informed. A short message at 08:35, "Internet is down for everyone; we're on it and will update you by 09:15", applies the Chapter 13 communication principles and prevents fifteen separate reports.
- Confirm what the UPS protects. A UPS rides through short power cuts; a long cut will still drop the connection. The log should say so, so that nobody assumes the risk has disappeared.
Scope first, then follow the path. One question (one device or all?) and one sequence of tests (address, router, internet by IP) moved the fault outside the building before anyone touched a cable.
Try it
Use a training computer or a virtual machine, or do this as a paper exercise. Do not power-cycle shared equipment at work or home without permission, because it disconnects everyone.
- On a computer you are allowed to use, run
ipconfig(Windows),ifconfig(macOS) orip addr(Linux) and note your IP address and default gateway. - Ping your default gateway, then 8.8.8.8, then a website name. Record each result.
- Write which part of the path each command tested.
- Now imagine the gateway ping succeeds but 8.8.8.8 fails. Write the information you would give the provider.
Completion criteria: four results recorded; each command matched to the part of the path it tests; a provider handover containing at least the start time, the tests and results, the equipment model and light status, and the number of users affected.
Knowledge check
In Case Study 1, which single test proved the fault was outside the office network?
Why did the team suspect the modem, router or provider rather than the staff laptops?
What is the correct order for power-cycling network equipment in Chapter 5?
Which tier in Figure 13.1 did the team escalate to?
Answers explained
- c — Reaching the router but not 8.8.8.8 places the break beyond the router; file sharing only cleared the local network, the power cut was the change, and restarting a laptop tests nothing outside it.
- a — All devices failing with a working local network points to shared equipment or the provider; no update, announcement or dark power light appears in the case.
- b — The modem must be up before the router can connect through it; other orders or simultaneous restarts can leave the router without a connection.
- d — The internet service provider is external, which is Tier 4.
Key takeaways
- "One device or all?" plus "what still works?" located the fault in shared equipment or the provider within minutes.
- The connectivity sequence is half-split on the network path: the first failure marks the break.
- A cheap, safe quick win came before escalation, and escalation went to the right tier with evidence ready.
- Verification was confirmation by all staff; prevention targeted the change that caused the fault.
Sources
- Dr. Tahseen Al Doori — Troubleshooting Essentials, University Edition (2026), Chapter 14 Case Study 1 and review question 1, §2.2–2.3, §5.3, §6.1, §6.4, §7.3, §9.1, §9.3, §13.1–13.3, Figure 13.1
