AP Networking 2.1: Missed Connection, Troubleshooting My SOHO Network

When the whole lab loses its connection at once, the fault is almost never ten broken laptops. It is one piece of shared gear: the modem, router, switch, or access point. This guide teaches you to scope the outage, read the free evidence, and fix it cheapest-first, the way a tech-support team does.

Topic 1.1 taught the five-step troubleshooting loop on a single device. Topic 2.1 runs the same loop on a small office / home office (SOHO) network, and adds the most powerful question in network troubleshooting: who is affected? One device down points at that endpoint; many point upstream, at the gear they all share. Answer that first and the suspect list drops to a handful of boxes.

• What is a SOHO network?
• The scope rule: one device or many?
• The diagnostic toolkit
• Restart in order
• Choosing the fix cheapest-first
• A full worked walkthrough
• Practice: LAN Down
• Three free practice questions
• Using AI safely
• Key terms
• Frequently asked questions

What is a SOHO network?

A SOHO (small office / home office) network is the kind in a home, classroom, or small business: one internet connection shared by a room of devices through a short chain of equipment. Every link in the chain is a place a fault can live.

Component	What it does	If it fails
Modem	Links the building to the ISP (internet service provider)	Internet dies for everyone; local traffic survives
Router	Directs traffic between devices and out to the internet	Everything fails, wired and wireless alike
Switch	Gives wired devices their ports	Wired drops; wireless keeps working
Access point (AP)	Provides the wireless signal	Wireless drops; wired keeps working
Endpoints	The laptops, desktops, phones, and printers	Only that one device has a problem

Home gear often combines modem, router, and AP in one box, but the roles and failure patterns stay separate. Learn each component's fingerprint and the network practically diagnoses itself.

The scope rule: one device or many?

Before you touch anything, count the victims. Thirty seconds of counting separates network troubleshooting from device troubleshooting.

Who is affected	Where the fault lives	Example
One device	That endpoint: its cable, port, or settings	Desktop 3 is offline; its neighbors are fine
All wireless, wired fine	The access point or wireless interference	Every laptop drops; desktops never blink
All wired, wireless fine	The switch or its uplink	Four desktops go dark at once
Everything, but local traffic works	The modem or the ISP connection	No internet anywhere, but printing still works
Everything, including local traffic	The router	No device can reach anything at all

The diagnostic toolkit: lights, cables, ping, and what changed

A SOHO network hands you four kinds of free evidence. Read all four before you change anything.

Status lights

Every box wears its health on its face. A dark power light: no power. A red internet light on the modem: the ISP link is down. A dark link light on a switch port: that port sees no device. Thirty seconds of looking replaces an hour of guessing.

Cable seating

Cables work loose: a cart bumps a shelf, a plug ends up half-in. Check that every cable on the suspect component clicks firmly at both ends. Reseating is free and fixes a remarkable share of real outages.

Ping and the loopback test

Ping sends a tiny message to an address and reports whether an answer came back and how fast. The loopback address 127.0.0.1 points at the device itself: if ping 127.0.0.1 succeeds, the device's own network software is healthy and the problem is beyond it, in the cable, port, or shared gear. Run it from a command prompt (Windows), Terminal (Mac), or crosh (Chromebook).

What changed?

Networks rarely fail for no reason: a new device joined, firmware updated, furniture moved, a storm cut power. The most recent change is your strongest lead, which is why technicians keep a change log (Topic 2.2 covers documenting your network). Ask "what changed?" before you blame any component.

Restart in order: modem, then router, then endpoints

"Turn it off and on again" is real, but on a network the order matters: the router cannot get its connection until the modem is online, and endpoints cannot get theirs until the router is up.

1. Modem first. Unplug for about 30 seconds, plug back in, and wait for a solid internet light; this can take a few minutes.
2. Router next. Power-cycle it and wait for its lights to settle; a separate access point comes back right after.
3. Endpoints last. Reconnect the devices that were failing, and watch what comes back.

The sequence is also a diagnostic. A modem light that never turns solid means an ISP fault; a healthy modem with devices still failing means the fault is further down the chain. Where the recovery stops is where the problem lives.

Choosing the fix cheapest-first

Unit 1's rule carries over: rank fixes by time, difficulty, and expense, and earn the expensive one. Here is the SOHO ladder, cheapest rung first.

Fix	Cost	When it is the right call
Reseat a cable	Free, seconds	Dark power or link light; anything moved recently
Power-cycle in order	Free, minutes	Whole-network outage; flakiness after a power event
Move the access point	Free, minutes	Weak signal in part of the room; metal or walls in the way
Change the wireless channel	Free, minutes	Wireless slow while wired is fast; neighboring networks
Update firmware	Free, needs care	A known bug, or a failed previous update
Replace hardware	Money, hours	Only after the free rungs failed and the part is confirmed dead

Then verify from the right place: retest on the devices that were failing, not just the box you touched. Green lights prove the router is up, not that the laptops recovered. If the problem persists, you have more than one fault or the wrong suspect: loop back, and write down each step.

A full worked walkthrough

The whole process on the unit scenario: the lab is disconnected on a Monday morning and you are on tech-support duty.

Scope. All ten wireless laptops show no networks available; the four wired desktops work normally. Wireless-only victims point at the access point.

Read the evidence. Modem and router lights are normal. The AP's power light is dark, and a bookshelf was moved next to it on Friday.

Fix cheapest-first. Behind the bookshelf, the AP's power cable is half out. Reseat it firmly at both ends. Free, twenty seconds.

Verify from the victims. The AP's light comes on, and two of the failing laptops reconnect and load a page. Confirmed.

Document. Log the symptom, cause, fix, and a note to keep furniture clear of the AP, so a teammate could handle the repeat.

Practice: LAN Down

Now run the process yourself. Read who is affected, the lights, and the documented change, isolate the failing component, then pick the cheapest-first fix. Cases and choices are shuffled every time, so reason from the evidence.

Three free practice questions

Try these before opening the answers. Each pairs two facts the way the AP exam does.

1. Every device lost internet access, but students can still print to the lab printer. The modem's internet light is red. Where is the fault?

The ISP link. Printing proves the LAN, switch, and router are healthy; the red internet light confirms the upstream path is down. Power-cycle the modem first and wait for its light.

2. Wireless devices crawl every afternoon, but wired desktops stay fast. The AP's lights are normal. What is the cheapest fix worth trying first?

Change the AP's wireless channel. Wireless-only slowness with healthy lights fits channel congestion, often from a neighboring network. The channel change is free; replacing the AP is the last rung, not the first.

3. One desktop is offline, its switch port's link light is dark, and ping 127.0.0.1 on it succeeds. What do you do?

Reseat, then swap, its patch cable. The loopback success clears the desktop's own network software, and a single victim with a dark link light points at its cable or port, not shared gear.

Using AI to troubleshoot a network, safely

Describe the symptoms to an AI assistant and it proposes a fault and a fix in seconds. But it only knows what you typed and cannot see the lights, so it will confidently condemn a router while the actual access point sits unplugged behind a bookshelf.

The Unit 1 rule carries over word for word: AI proposes, you confirm. Check the theory against the scope evidence, then climb the ladder for the component the evidence convicts. If the AI names the right component but jumps straight to buying hardware, keep the diagnosis and discard the fix: reseat and power-cycle come first.

Key terms

SOHO network

A small office / home office network: one shared internet connection for a room of devices.

Modem

Connects the building to the ISP; its internet light reports that link's health.

Router

Directs traffic between local devices and out to the internet.

Switch

Gives wired devices their ports; each port's link light shows a connected device.

Access point (AP)

Broadcasts the wireless network. Wireless-only outages usually trace here.

Ping

A test message that asks an address: are you there, and how fast?

Loopback address (127.0.0.1)

The device itself; pinging it tests the device's own network software.

Scope

How many and which devices a symptom affects; the first evidence to gather.

Frequently asked questions

Why is the Wi-Fi not working on any device?

Count the victims. Wireless-only down with wired working points at the access point: check its power light and cables. Everything down means work back through router and modem.

Why do I have Wi-Fi but no internet?

They are different links. Your device is connected to the access point, but the modem's ISP link is down. Check its internet light, then power-cycle the modem first.

What order should I restart my modem and router in?

Modem first, then the router, then the devices. Each layer needs the one before it, so wait for each box's lights to settle before starting the next.

What does ping 127.0.0.1 actually test?

127.0.0.1 is the loopback address, the device itself. If the ping succeeds, the device's own network software works, so the fault is in the cable, port, or shared gear.

Why is Wi-Fi slow but wired internet fast?

That pattern points at the wireless side: channel congestion, interference, or distance. Change the wireless channel or move the access point before buying hardware.

Only one computer will not connect. Is the network broken?

Probably not. A single victim points at that endpoint: reseat and swap its cable, check its port's link light, run a loopback ping. Shared faults produce multiple victims.

Should I update my router's firmware to fix a problem?

It is a middle rung, not the first. Reseat and power-cycle first; update when release notes name your bug or a failed update started the problem.

Can I just ask an AI what is wrong with my network?

Ask, then verify. The assistant cannot see your lights or count victims, so treat its answer as a theory, confirm the component against the evidence, and fix cheapest-first.

AP is a trademark of the College Board, which was not involved in the production of, and does not endorse, this resource.