Scenario
Marigold Press is a three-room print shop. This morning the
front-desk machine, LOBBY-PC, can no longer reach the file server
PRESS-SRV in the back utility room — orders won't save and the shared price
list won't open. The only thing that changed: the front-desk staffer slid the desk over
last night to wedge in a new label printer, rolling her chair across the floor cabling a
few times in the process. Everything else on the 10.20.5.0/24 network is fine.
You're the part-time tech. Work the problem from the bottom layer up: confirm the symptom, read the diagnostic signals, find the root cause, fix it with a known-good spare, and verify. Use the console, the link-status bay, the status page, and the bench.
Network map
Link-status bay — click a jack to inspect
Diagnostic tools
Physical-layer actions. Try the cheapest, least-disruptive fix first, then escalate to a known-good spare if the link stays down.