The "Connect a Wired and Wireless LAN" activity looks like the easy one — just drag cables between devices — and then half the links come up red and nothing pings. The lab (the NetAcad 4.6.5 / 4.2.4.4 Packet Tracer activity) isn't really about wireless at all; it's about picking the right cable for each pair of devices. Get the cable rules straight and the whole topology lights up green. This guide explains those rules, walks the wired-plus-wireless topology, and shows how to verify it.
The short version: in Cisco Packet Tracer, the cable depends on the pair of devices — straight-through for unlike devices (PC↔switch, switch↔router), crossover for like devices (switch↔switch, router↔router, PC↔router), and serial for a WAN link between two routers. A red link almost always means the wrong cable. If you'd rather not guess, NetPilot builds the wired-and-wireless topology with every cable already correct, hands you a working
.pkt, and explains each choice.
The real lesson: which cable goes where
This is the rule the activity is testing. In Packet Tracer:
| Cable | Connects | Examples |
|---|---|---|
| Copper straight-through | unlike devices | PC ↔ switch · switch ↔ router · PC ↔ hub |
| Copper crossover | like devices | switch ↔ switch · router ↔ router (Ethernet) · PC ↔ router · PC ↔ PC |
| Serial (DCE/DTE) | two routers over a WAN | Router ↔ Router via Serial interfaces |
| Console (rollover) | management, not data | PC ↔ a device's console port |
The shortcut is the "Automatically Choose Connection Type" tool — the gold lightning-bolt icon in the device toolbar. It picks the correct cable for you, which is great for speed but won't teach you the rule, so it's worth wiring a few links by hand first.
Why a link shows red: a solid red dot on a copper link means the cable type is wrong for that device pair (a straight-through where you needed a crossover, usually). Amber means the port is still negotiating; give it a moment. Green on both ends means the physical link is good.
Wiring the topology
A typical wired-and-wireless lab chains an ISP-style edge into a home network:
- Edge router to the cloud. Connect the router's FastEthernet port to the Cloud with a copper straight-through cable (the Cloud behaves like a switch here).
- Router to router over the WAN. If the lab has two routers, link their Serial interfaces with a serial cable — one end is the DCE and needs a
clock rate. - Modem to the wireless router. Connect the cable/DSL modem to the Internet port of the wireless router (a WRT300N), so the home network gets its uplink.
- Wireless router to the wired PCs. Use copper straight-through from the wireless router's Ethernet ports to each wired PC or switch.
- The wireless clients. Laptops and smartphones associate over Wi-Fi — no cable. Match each device's SSID (and WPA2 key, if set) to the wireless router under Config → Wireless, and swap a laptop's wired card for the WPC300N wireless card first.
That mix — cabled PCs on the Ethernet side, laptops over Wi-Fi — is the whole point of "wired and wireless."
Verify the connections
The activity ends by proving end-to-end reachability, usually to a named server:
ping netacad.pkaOpen a wired PC's Desktop → Command Prompt and ping the server name; then open the Web Browser and load http://netacad.pka. From a wireless laptop, repeat the ping to confirm the Wi-Fi side reaches the same destination. If a ping fails, work backwards: link lights green? correct cable? device has an IP? SSID/security matched on the wireless clients?
The faster path: describe it, get a working .pkt
Cabling errors are tedious precisely because Packet Tracer only tells you "red" — not why. The alternative is to describe the topology and let an AI tutor wire it:
"Build a Packet Tracer lab with an edge router to a cloud, a wireless router (WRT300N) behind a modem, two wired PCs, and two wireless laptops — all cabled correctly and reachable."
NetPilot generates the topology with every cable type correct, the wireless clients associated, and addressing in place, hands you a .pkt to open in Packet Tracer, and explains why each link uses the cable it does — so you learn the straight-through-vs-crossover rule instead of brute-forcing it. No 870 MB download, no NetAcad account; it runs in your browser.
FAQ
What cable connects a PC to a switch in Cisco Packet Tracer?
A copper straight-through cable — a PC and a switch are unlike devices, and unlike devices use straight-through. The same cable connects a switch to a router. You only need a crossover cable between like devices, such as switch-to-switch or PC-to-router.
Why are my cable links showing red dots in Packet Tracer?
A solid red dot on a copper link almost always means the wrong cable type for that device pair — most often a straight-through cable where the devices needed a crossover (or vice versa). Swap the cable to match the rule (straight-through for unlike devices, crossover for like devices). Amber dots just mean the link is still negotiating and usually turn green on their own.
What's the difference between a straight-through and a crossover cable?
A straight-through cable wires pin-to-pin and connects unlike devices (PC↔switch, switch↔router); a crossover cable swaps the transmit and receive pairs and connects like devices (switch↔switch, router↔router, PC↔router). The distinction exists because two like devices would otherwise both transmit on the same pair. Real modern gear auto-corrects with Auto-MDIX, but Packet Tracer activities still test the classic rule.
How do I connect the cloud or a modem in Packet Tracer?
Connect a router or modem to the Cloud with a copper straight-through cable on the Ethernet side (the Cloud acts like a switch); a cable modem then connects to the Internet port of a wireless router to provide the uplink. If you're unsure which port or cable to use, the gold "Automatically Choose Connection Type" tool picks a working cable for the pair.
Related guides: How to Configure Wireless in Cisco Packet Tracer (WRT300N, AP & WLC) · Cisco Packet Tracer Module 12 & 13 Wireless Labs Explained · Cisco Packet Tracer Wireless · Cisco Packet Tracer Online
Want the cabling done right the first time? Describe your topology to NetPilot and get a working, fully explained .pkt in about two minutes — no download required.