What Is Computer Networking and How Do Devices Communicate?
Updated
Computer networking is the practice of connecting two or more devices so they can exchange data and share resources. A network exists the moment two devices can send information to each other — whether that's a laptop and a printer on the same desk, or a phone on one continent reaching a server on another. The devices don't need to be the same type, and the connection doesn't need to be a cable; what defines a network is the ability to move data between endpoints. This article covers the building blocks: the types of networks, the hardware that makes them work, and the path a piece of data takes from one machine to another.
The core idea: shared resources and communication
Before networks, moving a file between two computers meant a floppy disk or a serial cable. Networking replaced that with a persistent link that any connected device can use. Two things happen on that link:
- Communication — devices send messages, requests, and responses to each other (a browser asking a web server for a page).
- Resource sharing — devices use hardware or services they don't physically own (a shared printer, a file server, an internet connection).
Both depend on the same underlying mechanism: breaking data into small units, addressing them, and moving them across a medium.
Common network types and where they fit
Networks are usually classified by how far they reach. The boundaries are practical, not strict.
| Type | Stands for | Typical reach | Example |
|---|---|---|---|
| LAN | Local Area Network | One building or home | Your home Wi-Fi and wired devices |
| WLAN | Wireless LAN | Same as LAN, but wireless | Wi-Fi network in an office |
| WAN | Wide Area Network | Cities, countries, global | The internet, or a company link between offices |
| MAN | Metropolitan Area Network | A city | A campus or ISP network spanning a metro area |
The internet itself is the largest WAN — a network of networks, where each participating network agrees to pass traffic to the others. A home network is a LAN that connects to that WAN through an internet service provider.
The hardware and the role each part plays
A small network needs surprisingly few components, but each one has a distinct job.
- Network interface card (NIC) — the hardware inside a device that actually sends and receives signals. Wired NICs use an Ethernet port; wireless NICs use a radio. Every networked device has at least one.
- Switch — connects devices within a LAN. It forwards data only to the port where the intended recipient is connected, rather than shouting to everyone.
- Access point (AP) — the wireless equivalent of a switch port. It bridges Wi-Fi devices into the wired LAN.
- Router — connects different networks and decides where traffic should go next. In a home setup, the router is the box that links your LAN to your ISP's WAN.
- Modem — converts the signal from your ISP's medium (cable, fiber, DSL) into something your router can use. Often combined with the router in one device.
A common point of confusion: a switch moves data inside one network, a router moves data between networks. Home "routers" usually contain a switch, an access point, and a router in a single box, which is why the distinction blurs in practice.
How data actually travels from one device to another
When you load a page or send a message, the data doesn't travel as one block. It's split into packets — small chunks that can be routed independently and reassembled at the destination.
The basic flow:
- Addressing. Every device on a network has an IP address, which identifies it on that network. Data is sent to a destination IP, not to a physical device name.
- Packaging. The sending device breaks the data into packets and labels each one with the source and destination IP addresses.
- Local delivery. Within the LAN, the switch forwards packets to the correct port using the device's hardware (MAC) address.
- Routing. If the destination is outside the LAN, the router examines the destination IP and forwards the packet toward the next network, hop by hop, until it reaches one that can deliver it locally.
- Reassembly. The receiving device collects the packets, puts them back in order, and hands the complete data to the application.
This is why a single lost packet doesn't usually break a download — the protocol requests it again. It's also why the same IP address can't be used by two devices on the same network at the same time: the addressing would be ambiguous.
Wired vs. wireless: what actually differs
The choice between a cable and a radio affects speed, stability, and convenience more than it affects how networking works.
- Wired (Ethernet) — a physical cable carries the signal. It's typically faster and more consistent, and it doesn't suffer from interference or walls. It requires the device to be near a port.
- Wireless (Wi-Fi) — a radio link between the device and an access point. It's convenient and works anywhere in range, but speed drops with distance, obstacles, and interference from other networks.
For a fixed desktop or a server, wired is usually the better default. For phones, laptops, and anything that moves, wireless is the practical choice. Many networks use both: wired for the backbone and stationary devices, wireless for everything else.
A minimal home or small-office network
A working setup can be as simple as:
- An ISP connection coming into a modem/router.
- The router providing DHCP, which automatically assigns IP addresses to devices so you don't configure each one by hand.
- A switch if you need more wired ports than the router offers.
- An access point (or the router's built-in Wi-Fi) for wireless devices.
- Devices — computers, phones, printers, a NAS — each with a NIC and an assigned IP address.
From there, everything on the LAN can reach everything else, and the router handles the path out to the internet. That's the whole model: address the data, move it locally with a switch, route it between networks with a router, and reassemble it at the other end.