Basic Networking Concepts
Build a mental model of how devices exchange data through local networks, the internet, and shared protocols.
- Certification
- CompTIA Network+
- Recommended study time
- 6h 10m
- Status
- Not started
Recommended study time
About 6h 10m in total, measured from the material on this page. At your session length of 45 minutes that is 9 sittings.
- Read the lesson20 min
About 2,606 words at a careful technical reading pace.
- Second pass with notes12 min
Re-read the harder parts and write your own notes.
- Work through the examples1h 40m
5 worked examples and 15 practice questions.
- Recall from memory12 min
2 written recall questions.
- Practice decision12 min
One applied decision with feedback.
- Teach it back20 min
Write the topic in your own words.
- Real-world scenario15 min
Read the situation and justify your decision in writing.
- Hands-on practice2h
Labs, commands and configuration until you can do it unaided.
- Spaced review1h
4 short review sessions spread over the following weeks.
Learning objectives
- Describe clients, servers, network interfaces, switches, routers, and access points.
- Explain why protocols and layered communication are necessary.
- Follow a request from a local device toward a remote service.
Start here
About 18 minutes of reading, in 9 short parts.
Networking is the study of how a message gets from one program on one machine to another program on a different machine. The whole subject becomes tractable once you accept a single idea: the work is divided into layers, and each layer solves exactly one delivery problem.
Where you meet it: Wi-Fi complaints, 'the internet is down', printers that vanish, VPN problems, and every cloud application your organisation depends on.
The lesson, part by part
Open one part at a time. Each part stands on its own, so you can stop and come back.
A network is a set of devices that agree on protocols — shared rules for formatting, addressing, and sequencing data. Most communication follows the client-server model: a client initiates a request, a server listens on a known port and responds. Peer-to-peer networks let each device act as both.
Devices are grouped by scale: a LAN covers one site, a WAN links sites over provider circuits, a WLAN is the wireless portion of a LAN, and the internet is the global interconnection of independently operated networks.
Key ideas
If you remember nothing else from this topic, remember these.
- Every networking symptom can be placed at a specific OSI layer, and identifying that layer immediately tells you which class of device or setting is responsible, which is the entire point of learning the model.
- Encapsulation means each layer wraps the layer above it in its own header on the way out, and the receiving device strips those headers in the exact reverse order, so a header mismatch at any single layer breaks delivery cleanly at that layer alone.
- A switch operates within one broadcast domain using MAC addresses, while a router joins separate IP networks together, which is why a device can be perfectly connected to a switch and still have zero connectivity beyond its own subnet.
- TCP's three-way handshake (SYN, SYN-ACK, ACK) establishes a reliable connection before any application data moves, while UDP sends immediately with no such handshake, trading reliability for speed.
- Scope of impact is the fastest diagnostic tool in networking: one device points at that device, one room points at a switch or access point, one application for everyone points at a server or port, and everything for everyone points at the router, ISP, or DNS.
- Comparing a broken device against a known-good device on the identical network eliminates the entire shared infrastructure in a single test, which is why it should usually be the first troubleshooting move, not the last.
Isolating a printer that vanished from the network
A worked example, step by step.
A networked office printer that worked yesterday no longer appears in anyone's print dialog. Three staff have already reported it as 'the printer is broken.'
- 01Establish scopeAsk whether anything else on that same switch, like a nearby workstation, is also affected. Only the printer is reported down, narrowing scope to that one device or its cable.
- 02Check Layer 1Walk to the printer and check the link light on its network port: it is off, meaning no physical link is currently established.
- 03Inspect the physical connectionThe Ethernet cable is seated at the printer end, but wiggling the switch end reveals it had come loose from the port.
- 04Reseat and confirm linkPush the cable fully into the switch port until it clicks; the link light on both the switch port and the printer NIC turn green.
- 05Check Layer 3 addressingFrom the printer's own network settings screen, confirm it shows a valid IP address such as 192.168.10.52 rather than an APIPA address, meaning DHCP succeeded.
- 06Test reachabilityFrom a laptop on the same subnet, run ping 192.168.10.52; replies return successfully, confirming Layer 3 connectivity is restored.
- 07Test the application layerPrint a test page from that laptop; it succeeds, confirming the print spooler and driver path both work end to end.
- 08Verify from originally affected machinesAsk the three original users to retry; the printer reappears in their print dialog since it is now broadcasting correctly on the segment.
Outcome: The root cause was a loose Ethernet cable at the switch, a pure Layer 1 physical fault, and reseating it restored Layer 1 through Layer 7 connectivity without any configuration change being needed.
Layered Networking Facts Worth Memorising
Worth keeping at hand while you work.
- OSI Layer 1
- Physical: cables, radio, connectors, light; symptom is no link light
- OSI Layer 2
- Data Link: MAC addresses, switches, VLANs; symptom is local-only communication
- OSI Layer 3
- Network: IP addresses, routers, ICMP; symptom is local works, remote fails
- OSI Layer 4
- Transport: TCP and UDP, port numbers; symptom is ping works but one service is blocked
- TCP three-way handshake
- SYN, SYN-ACK, ACK, establishing a reliable ordered connection
- ARP
- Resolves a known IP address to the MAC address needed to build the frame
- Default gateway
- The router interface a host sends traffic to when the destination is off its own subnet
- Broadcast domain
- The set of devices that receive a Layer 2 broadcast; bounded by routers, not switches
- Access point
- Layer 2 device converting wireless frames to wired frames; does not route by itself
- Spanning Tree Protocol
- Prevents switching loops and the broadcast storms they cause
- NAT
- Translates private internal addresses to a public address at the router/firewall boundary
- traceroute / tracert
- Shows each hop along a path, useful for finding where along a route a failure begins
Common misunderstandings
What most beginners get wrong here.
If a device is connected to Wi-Fi, it has internet access.
Wi-Fi association only guarantees Layer 2 connectivity; internet access still depends on DHCP, a working default gateway, and DNS resolution above that layer.
Ping failing always means the network is down.
Ping tests ICMP specifically; many firewalls block ICMP while still allowing the actual application traffic, so a failed ping does not always mean a broken network.
A router and a switch do the same job, just at different speeds.
A switch forwards frames by MAC address within one network, while a router forwards packets by IP address between separate networks; they solve different problems entirely.
Restarting the modem/router fixes most home network issues because networking hardware is unreliable.
It works because most home devices combine modem, router, switch, access point, and firewall in one box, so a reboot resets several independent functions at once, not because networking hardware is inherently flaky.
TCP is always better than UDP because it is reliable.
TCP's reliability comes with overhead and latency that make it a poor fit for real-time voice and video, where UDP's speed and tolerance for dropped packets is the better trade-off.
Exam traps
How the question writers try to catch you out.
- A scenario describing 'can reach local devices but not the internet' is testing Layer 3 identification: the fault is the gateway or routing, not the local switch or cabling.
- Questions distinguishing a switch from a router expect you to know a switch operates within a single broadcast domain while a router joins separate ones.
- Expect the exam to test that an access point is a Layer 2 device; a question may describe successful Wi-Fi association with no internet access specifically to test this distinction.
- Port-based questions expect you to separate reachability (ping/ICMP) from service availability (a blocked port), since these are commonly tested as two different failure types.
- When the exam describes 'one device affected' versus 'the whole floor affected,' it is testing whether you can map symptom scope to the correct device layer without being told directly.
Check yourself
Answer in your head first, then reveal. This is not scored.
A laptop is connected to Wi-Fi with full signal strength but cannot load any website. What layers have succeeded and which should you check next?
Why can a switch not connect two different IP subnets together on its own?
A user can ping a server successfully but their application to that server times out. What does this tell you?
Why is comparing against a known-good device on the same network such an effective first troubleshooting step?
What specifically does a switching loop cause, and what protocol exists to prevent it?
Quick reference
A condensed summary of the lesson above, for revision.
What It Is
A computer network is a group of connected devices that exchange data. End devices such as laptops and servers use network interfaces. Switches move local traffic, access points connect wireless clients, and routers move packets between networks. Protocols define how participants format, send, receive, and acknowledge information.
Why It Matters
Modern applications depend on networks even when they appear local. IT professionals need to know where a communication path can fail: the device, its local link, a switch or access point, the router, an internet provider, or the remote service. A clear mental model prevents random troubleshooting.
How It Works
- Clients and servers exchange data according to protocols.
- Switches forward local frames, routers move packets between networks, and access points bridge wireless clients.
- Layering lets each part of the path solve a defined delivery problem.
Where You See It
- Home Wi-Fi, office LANs, cloud applications, printers, cameras, and internet services.
Key Terms
- Client
- A device or program that requests a service.
- Server
- A device or program that provides a service to clients.
- Switch
- A device that forwards frames between devices on a local network.
- Router
- A device that forwards packets between separate networks.
- Protocol
- An agreed set of rules for communication.
Examples
- A laptop sends a web request through Wi-Fi to an access point, then through a router toward a remote web server.
- An office switch connects workstations and printers on the same local network while the router provides access to other networks.
Common Problems
- Disconnected links
- Wrong network selection
- Unavailable gateway
- Remote service outage
How It Fails
- A device may have a local Wi-Fi connection but no routed internet path.
- A switch loop or failed uplink can disrupt many local devices.
- A server can be down while the network remains healthy.
How to Troubleshoot
- Define who and what is affected.
- Check link, local configuration, gateway reachability, and remote service in order.
- Compare a working device on the same network.
Practical Knowledge
- Draw the path before changing settings.
- Separate local-network, internet-path, and application-service tests.
Exam Coverage
- Client-server roles
- Switch, router, and access-point functions
- Basic layered troubleshooting
Interview Questions
- What is the difference between a switch and a router?
- A laptop shows connected to Wi-Fi but websites fail. What would you test?
Worked examples
Each calculation is shown one step at a time, then you try it yourself before revealing the answer.
Convert binary to decimal
Convert the 8-bit binary number 11000000 to decimal.
- 1. Write the place valuesAn 8-bit number has fixed place values, left to right: 128, 64, 32, 16, 8, 4, 2, 1.
- 2. Line the bits up under the place values128→1, 64→1, 32→0, 16→0, 8→0, 4→0, 2→0, 1→0.
- 3. Keep only the place values above a 1The 128 column and the 64 column hold a 1. Every other column holds 0 and contributes nothing.
- 4. Add them128 + 64 = 192.
Answer: 11000000 = 192. This is why a /24 subnet mask octet of 11000000 reads as 192 in dotted decimal.
Now you try
Convert 10101010 to decimal.
Convert 11111111 to decimal.
Convert 00011100 to decimal.
Convert decimal to binary
Convert the decimal number 172 to 8-bit binary.
- 1. Start at the largest place valueAsk: does 128 fit into 172? Yes. Write a 1 and subtract: 172 − 128 = 44.
- 2. Next column, 6464 does not fit into 44. Write 0. Remainder stays 44.
- 3. Next column, 3232 fits into 44. Write 1. 44 − 32 = 12.
- 4. Continue down16 into 12? No → 0. 8 into 12? Yes → 1, remainder 4. 4 into 4? Yes → 1, remainder 0. 2 → 0. 1 → 0.
- 5. Read the bits in order1, 0, 1, 0, 1, 1, 0, 0.
Answer: 172 = 10101100. Check it by adding the on-bits back: 128 + 32 + 8 + 4 = 172.
Now you try
Convert 200 to binary.
Convert 19 to binary.
Convert 255 to binary.
Convert binary to hexadecimal
Convert 11011110 to hexadecimal (the form used by MAC and IPv6 addresses).
- 1. Split into 4-bit groups11011110 becomes 1101 and 1110.
- 2. Convert each group with place values 8, 4, 2, 11101 = 8 + 4 + 1 = 13. 1110 = 8 + 4 + 2 = 14.
- 3. Replace values over 9 with letters10=A, 11=B, 12=C, 13=D, 14=E, 15=F. So 13 = D and 14 = E.
- 4. Join the digitsD followed by E.
Answer: 11011110 = DE in hex, which is 222 in decimal. Each pair of hex digits is exactly one byte, which is why a MAC address is six hex pairs.
Now you try
Convert 10101111 to hex.
Convert hex 3C to binary.
Convert hex FF to decimal.
Work out a network address and host range
A host is configured as 192.168.10.77 with the mask 255.255.255.192 (/26). What is its network address, broadcast address and usable host range?
- 1. Find the interesting octetThe first three octets of the mask are 255, so only the fourth octet matters. 192 in binary is 11000000, so 2 host-network bits are borrowed.
- 2. Find the block size256 − 192 = 64. Subnets step in blocks of 64: 0, 64, 128, 192.
- 3. Place the host77 falls between 64 and 127, so the host sits in the 192.168.10.64 subnet.
- 4. Name the boundariesNetwork address = 192.168.10.64. Broadcast = one below the next block = 192.168.10.127.
- 5. Usable hostsEverything between the two boundaries: .65 through .126.
Answer: Network 192.168.10.64, broadcast 192.168.10.127, usable range 192.168.10.65–192.168.10.126 (62 usable addresses).
Now you try
Same question for 10.0.0.200 /26.
What mask is /28 in dotted decimal, and what is its block size?
How many usable hosts in a /29?
Count usable hosts from a CIDR prefix
How many usable host addresses does a /22 network provide?
- 1. Count host bitsAn IPv4 address is 32 bits. 32 − 22 = 10 host bits.
- 2. Raise 2 to that power2^10 = 1024 total addresses in the block.
- 3. Remove the two reserved addressesThe lowest address is the network address and the highest is the broadcast address: 1024 − 2.
Answer: 1022 usable host addresses. The general formula is 2^(32 − prefix) − 2.
Now you try
Usable hosts in a /30?
You need 500 hosts on one subnet. What is the smallest prefix?
Total addresses in a /16?
Watch and read
Verified official and reputable sources for this topic. Links open in a new tab.
Video training
Reading and courses
Lesson notes and bookmark
Notes and bookmarks for this lesson, saved with everything else you have marked.
No notes on this item yet.
Learning progress
0% across six evidence areas. Reading alone does not change progress.
Prerequisites
Next steps
- 01Draw the path from one device in your home to a public website.
- 02Identify which device provides Wi-Fi and which device routes traffic to the internet.