CompTIA Network+ Preparation · lesson 1 of 30 · 25 min
Network+ vs CCNA — Model Focus
The CompTIA Network+ N10-009 exam tests OSI and TCP/IP models from a vendor-neutral troubleshooting perspective. You need to know which layer a problem occurs at, which protocols operate at each layer, and how to use the models to isolate faults systematically. The OSI model is the primary troubleshooting framework — every Network+ scenario question maps to a specific layer.
The key skill is layer isolation: given a symptom, determine the lowest layer that could cause it, then work up or down from there. This is faster and more reliable than guessing.
OSI Model — Troubleshooting Focus
Layer memory trick
Top-down: All People Seem To Need Data Processing (Application → Physical)Bottom-up: Please Do Not Throw Sausage Pizza Away (Physical → Application)
Troubleshooting Approaches
TCP/IP Model Mapping
Encapsulation and Decapsulation
As data travels down the OSI stack (sending), each layer adds a header (and Layer 2 adds a trailer) — this is encapsulation. As data travels up the stack (receiving), each layer removes its header — this is decapsulation.
Sending path: Application data → Segment (L4 TCP/UDP header) → Packet (L3 IP header) → Frame (L2 MAC header + FCS trailer) → Bits (L1)
Receiving path: Bits → Frame (L2 checks FCS, removes header) → Packet (L3 checks IP, removes header) → Segment (L4 checks port, removes header) → Application data
Why FCS matters
The Frame Check Sequence (FCS) is a 4-byte CRC trailer added by Layer 2. The receiving device recalculates the CRC and compares it to the FCS. If they don’t match, the frame is discarded. High CRC error counts indicate physical layer problems — bad cable, interference, or duplex mismatch.
Layer-by-Layer Diagnostic Commands
Worked Scenario: Systematic Troubleshooting
Scenario
A user reports they cannot access the company intranet website at https://intranet.company.com. Other users on the same subnet can access it fine.
Step 1 — Layer 1: Check the link light on the NIC. It’s green — physical layer is OK.
Step 2 — Layer 3: Run ping 10.1.1.50 (the intranet server IP). Ping succeeds — IP routing is working.
Step 3 — Layer 7 (DNS): Run nslookup intranet.company.com. It resolves to 10.1.1.50 — DNS is working.
Step 4 — Layer 4: Run telnet 10.1.1.50 443. Connection refused — port 443 is not reachable from this device.
Root cause: A host-based firewall on the user’s PC is blocking outbound port 443. Layers 1–3 and DNS are fine; the problem is at Layer 4. Fix: adjust the local firewall rule.
Flashcard Drill
Bottom-up troubleshooting Start at Layer 1 (physical) and work up — used when there are physical symptoms like no link light. Top-down troubleshooting Start at Layer 7 (application) and work down — used when the app is failing but physical is OK. Divide and conquer Start at Layer 3 or 4 — used when ping works but the app fails. Layer 1 problem signs No link light, bad cable, NIC failure, wrong cable type, attenuation. Layer 2 problem signs Duplex mismatch, MAC conflict, high CRC errors, switch misconfiguration. Layer 3 problem signs Wrong IP/mask, no default gateway, routing failure — ping fails. Layer 4 problem signs Port blocked by firewall, wrong port number, connection refused. Layer 7 problem signs DNS failure, certificate error, wrong URL, app misconfiguration. Encapsulation Adding headers as data moves down the OSI stack — Application → Bits. FCS (Frame Check Sequence) Layer 2 CRC trailer — receiving device checks for frame corruption. High CRC errors = physical problem. PDU at Layer 4 Segment (TCP) or Datagram (UDP). PDU at Layer 2 Frame — contains source and destination MAC addresses plus FCS trailer.
Knowledge Check — 12 Questions
OSI & TCP/IP Troubleshooting (Network+)
A user reports “the app is not working but I can ping the server.” Which troubleshooting approach is best?
- Bottom-up from Layer 1
- Top-down from Layer 7
- Divide and conquer — start at Layer 4/5
- Replace the cable first
Answer: Divide and conquer — start at Layer 4/5
Ping works (Layer 3 OK), so skip to Layer 4+ — check ports, firewall, and application.
A workstation has no link light on its NIC. Which OSI layer is the problem?
- Layer 2
- Layer 3
- Layer 1
- Layer 4
Answer: Layer 1
No link light = physical layer (Layer 1) problem — cable, NIC, or port issue.
Adding headers as data moves down the OSI stack is called _____.
Answer: encapsulation
Encapsulation adds headers at each layer as data moves from Application to Physical.
Which layer handles logical addressing and routing?
- Layer 1
- Layer 2
- Layer 3
- Layer 4
Answer: Layer 3
Layer 3 (Network) handles IP addressing and routing between networks.
A connection is refused on port 443. Which layer is the likely problem?
- Layer 1
- Layer 2
- Layer 3
- Layer 4
Answer: Layer 4
Port 443 is a Layer 4 (Transport) concept — connection refused suggests a firewall or service issue at Layer 4.
Which TCP/IP layer maps to OSI Layers 5, 6, and 7?
- Transport
- Internet
- Application
- Network Access
Answer: Application
The TCP/IP Application layer encompasses OSI Layers 5 (Session), 6 (Presentation), and 7 (Application).
ARP operates at OSI Layer 3.
- True
- False
Answer: True
ARP (Address Resolution Protocol) maps Layer 3 IP addresses to Layer 2 MAC addresses — it operates at Layer 3.
Which layer adds a trailer (FCS) in addition to a header?
- Layer 1
- Layer 2
- Layer 3
- Layer 4
Answer: Layer 2
Layer 2 (Data Link) adds both a header (source/dest MAC) and a trailer (FCS for error detection).
DNS failure is a problem at which OSI layer?
- Layer 3
- Layer 4
- Layer 5
- Layer 7
Answer: Layer 7
DNS is an Application layer (Layer 7) protocol — DNS failure is a Layer 7 issue.
The process of removing headers as data moves up the OSI stack is called _____.
Answer: decapsulation
Decapsulation removes headers at each layer as data moves from Physical to Application.
High CRC error counts on a switch interface indicate a problem at which layer?
- Layer 3
- Layer 4
- Layer 1 or 2
- Layer 7
Answer: Layer 1 or 2
CRC errors are detected by the Layer 2 FCS, but they are usually caused by Layer 1 problems — bad cable, interference, or duplex mismatch.
A technician runs ping and it succeeds, then runs telnet to port 80 and it fails. The problem is at:
- Layer 1
- Layer 2
- Layer 3
- Layer 4 or above
- Answer: Layer 4 or above
Ping (ICMP) works = Layer 3 is fine. Telnet to port 80 fails = Layer 4 (port blocked) or Layer 7 (service not running).
Try it: Match the PDU to the layer
Back to CompTIA Network+ Preparation
Next lesson: Common ports and protocols: DNS, DHCP, HTTP/S, FTP, SSH, SMTP, SNMP, RDP