Skip to content

8. Network Hardware and Troubleshooting

Network hardware, by job

Device Job
Switch Connects devices on the same network, forwarding traffic only to the right port
Router Connects different networks together, deciding how to get from one to the other
Firewall Filters traffic in or out, based on rules
Access point Bridges wireless devices onto a wired network

A home "router" is usually all four of these in one box. The lab's own network separates some of these roles — pve1 acts as gateway/router for the lab's 192.168.137.0/24 network, and also runs the DNS workaround from Lesson 3.

The six-step method, applied to networking

Same method from the PC Building Lab's troubleshooting lesson — it isn't hardware-specific, it's a general approach: identify → theorize → test → plan and implement → verify → document.

Common network symptoms

Symptom Likely cause (check in this order)
No connectivity at all Cable/link light, then IP configuration
Can reach devices by IP, not by name DNS, not connectivity
Can reach local devices, not the internet Default gateway misconfigured, or the router's own uplink
Intermittent wireless drops Signal strength/interference, or an overloaded access point
"IP address conflict" error Two devices given the same static address, or a DHCP scope overlap

Final project

In Packet Tracer, build a topology with at least 3 PCs, 1 switch, and 1 router — then introduce one deliberate problem (a wrong subnet mask, an unplugged cable, a mismatched wireless password) and have a classmate find and fix it using the six-step method, writing up what they found at each step.

Try it

Either break your own topology on purpose and challenge a classmate to fix it, or ask a classmate to break theirs for you. Document all six steps as you go, not just the final fix.

Tip

"Can you reach it by IP but not by name?" is one of the fastest diagnostic questions in all of networking — it instantly separates a DNS problem from everything else.

Play it

Try the Network Troubleshooting Lab for hands-on practice diagnosing broken network scenarios using the six-step method.