Networking fundamentals explained in one sentence: every device gets an address, a mask tells it which addresses are local, a gateway forwards everything else, DNS turns names into addresses, and ports decide which program on the far end receives the data. Understand those five mechanisms and roughly eighty percent of day-to-day network troubleshooting becomes obvious.
This article walks through nine concepts in the order a packet actually encounters them, then gives you the troubleshooting sequence that follows from them.
1. The IP Address
An IP address identifies one network interface. IPv4 addresses are four numbers from 0 to 255, like 192.168.1.40. IPv6 addresses are longer and hexadecimal, and they exist because IPv4 ran out of space.
Some ranges are private — reserved for use inside your own network and never routed across the public internet. 192.168.x.x, 10.x.x.x and 172.16–31.x.x are the ones you will meet constantly. Your home router hands out private addresses and keeps one public address for itself.
An address that starts 169.254 means the device asked for an address and got no answer. That single fact resolves a large share of “no internet” tickets.
2. The Subnet Mask
The mask is how a device decides whether a destination is local or remote. It splits the address into a network part and a host part.
With an address of 192.168.1.40 and a mask of 255.255.255.0 — written /24 — the first three numbers are the network. Anything starting 192.168.1 is a neighbour and gets reached directly. Anything else must go through the gateway.
| Notation | Mask | Usable hosts | Typical use |
|---|---|---|---|
| /24 | 255.255.255.0 | 254 | Standard office or home subnet |
| /25 | 255.255.255.128 | 126 | Splitting a /24 in two |
| /30 | 255.255.255.252 | 2 | Point-to-point links between routers |
| /16 | 255.255.0.0 | 65,534 | Large flat networks, usually a design smell |
Mismatched masks on the same wire are a classic fault. Two devices can be physically connected, correctly cabled, and still unable to see each other because one of them has decided the other is on a different network.
3. The Default Gateway
The gateway is the router interface that handles everything not local. If a device has no gateway, or the wrong one, it can reach its own subnet perfectly and nothing beyond it.
“I can reach the printer down the hall but not the internet” is almost always a gateway or DNS problem, and the first thing to check is which.
4. DHCP
DHCP hands out addresses automatically. A client boots, broadcasts a request, and a DHCP server replies with an address, a mask, a gateway and DNS server addresses, leased for a set period.
Things worth knowing:
- Leases expire and renew. A client holding a lease from a network it has left behaves strangely until the lease is released.
- Two DHCP servers on one network fight, and clients get inconsistent configuration.
- Servers, printers and network gear usually get static addresses or DHCP reservations so their addresses never move.
5. DNS
DNS translates names into addresses. You type a hostname, your resolver asks the DNS hierarchy, and you get an address back.
Record types you will use weekly:
- A — name to IPv4 address
- AAAA — name to IPv6 address
- CNAME — name to another name
- MX — where mail for a domain goes
- TXT — arbitrary text, used heavily for domain verification and mail authentication
- PTR — address back to a name, for reverse lookups
DNS caches aggressively at every layer — the application, the operating system, the local resolver, the upstream resolver. When a change does not appear to take effect, caching is the first suspect and the record’s time-to-live value tells you how long you may be waiting.
A DNS failure looks exactly like a total outage to a user, because nothing resolves. Testing by address rather than name separates the two instantly.
6. Ports and Protocols
An address gets data to the right machine. A port gets it to the right program on that machine.
| Port | Service | Notes |
|---|---|---|
| 22 | SSH | Remote shell, also used for secure file transfer |
| 53 | DNS | Uses both UDP and TCP |
| 80 | HTTP | Unencrypted web traffic |
| 443 | HTTPS | Encrypted web traffic, now the default |
| 3389 | RDP | Windows remote desktop |
| 445 | SMB | Windows file sharing |
TCP sets up a connection, numbers the segments, and retransmits what goes missing — correct but slower. UDP fires and forgets — fast but tolerant of loss. Web traffic and file transfers use TCP. Voice, video and DNS lookups lean on UDP, because a late packet is worse than a lost one.
7. NAT
Network Address Translation lets many private addresses share one public address. Your router rewrites outbound traffic to appear as if it came from itself and remembers the mapping so replies find their way back.
The consequence that matters: inbound connections do not work by default, because the router has no mapping to consult until the inside device starts the conversation. This is why hosting a service at home requires deliberate configuration, and why it is a bad idea to do so for a lab.
8. Switching Versus Routing
A switch moves frames within one network segment using hardware addresses. It learns which address lives on which port and forwards accordingly.
A router moves packets between networks using IP addresses and a routing table. Every hop a packet takes between networks is a routing decision.
VLANs let one physical switch carry several logically separate networks. Traffic cannot move between VLANs without passing through something that routes — which is precisely what makes VLANs a security control as well as a design convenience.
9. The Edge
At the boundary of a network sits the gear that decides what gets in. A firewall filters by address, port and protocol. Beyond it, modern deployments add WAF and DDoS protection to absorb volumetric attacks and filter malicious web requests before they reach an application, and Zero Trust approaches that authenticate every request rather than trusting anything by virtue of its network location.
You do not need depth here for an entry-level role. You do need the vocabulary, because it comes up in every conversation about how traffic reaches a service.
The Troubleshooting Order
Work outward. Stop at the first failure.
- Is the link up? Check the interface, the cable, the port lights.
- Does the device have a sensible address? Inspect it. A 169.254 address means DHCP failed.
- Can it reach its own gateway? Ping the gateway address.
- Can it reach something beyond the gateway by address? Ping a known public address.
- Can it resolve a name? Query DNS directly for a known hostname.
- Can it reach the specific service? Test the port, not just the host.
- Is something in between blocking it? Firewall rules, access lists, host-based filtering.
Six commands cover most of this: a tool to show your own configuration, ping, traceroute, a DNS query tool, a port-test tool, and something to list local listening ports. Learn those six on both Windows and Linux and you can triage almost anything.
Learn the Mechanism, Not the Acronym
Networking stops being intimidating the moment you stop memorising acronyms and start tracing the path. Address, mask, gateway, name resolution, port. Every fault you meet lives at one of those steps, and the troubleshooting order above finds it.
To put these fundamentals into practice against real configuration, open the IT Ops course category on Tech Skills Library and start with the networking track.