3.3Endpoint devices

If switches and routers are the "roads," the "users" of those roads are the endpoints. An endpoint is the collective term for devices at the edge of the network that produce or receive data—spanning the PCs and smartphones we touch daily, business IP phones and printers, service-providing servers, and the rapidly growing IoT devices. This section builds the ability to identify "what role each device provides," so that when something will not connect you have a first step of isolation like "is this a client, or the side that serves."

3.3.1Client devices people use

• PC (desktop/laptop) is the general-purpose device a user operates directly. Most act as a client, on the consuming side of services like web or file sharing provided by servers. It connects by wire (RJ-45) or wireless (Wi-Fi).
• Mobile devices (smartphones/tablets) are meant to be carried, switching between Wi-Fi and cellular (mobile lines). Because they move, the radio environment changes easily, making isolation of wireless-specific drops and slowdowns important.
• An IP phone carries voice over the IP network. Many run on PoE (Power over Ethernet—powered through the LAN cable), and some setups daisy-chain a PC into the phone's rear port. Because voice is real-time-critical, it is sensitive to delay (latency).

3.3.2Serving devices and many small devices

• A server is the device on the providing side of services—web, mail, file, DNS, and so on. Receiving requests from many clients, it demands stability, speed, and security, and usually runs continuously on wired. Grasp it by role: a server is "the party a client uses."
• A network printer connects directly to the network and is shared for printing by multiple PCs. It is a kind of endpoint with its own IP address, and for a "cannot print" fault you separate "the printer's IP/power/paper" from "the PC-side settings."
• IoT devices are the many small devices on the network—sensors, cameras, smart appliances, industrial gear. Large in number and easily overlooked in management, they tend to become a security weak point. The first step is recognizing that "these too are full endpoints on the network."

A "cannot print on the shared printer" inquiry is dispatched quickly when you keep endpoint roles in mind. The first thing to isolate is whether the problem is on "the side requesting the print (the client PC)" or "the side doing the printing (the network printer, an endpoint)." If several people cannot all print to the same printer, the cause likely lies not on each PC but in the shared printer itself—it is powered off, out of paper, or its IP address changed so no one can reach it. Then the sensible move is to check whether the printer's own IP answers ping and whether its panel shows an error. Conversely, if only that one person cannot print while others are fine, suspicion shifts to that PC's settings (the printer driver or the destination IP). The same thinking applies to servers. If "no one can reach a certain web service," it is more efficient to first check whether the providing-side server is down, rather than suspecting each client one by one. The key is to split devices by role into "clients (consuming side)" and "servers/shared devices (providing side)," and switch which side you suspect depending on whether the symptom is "everyone" or "only that person." Additionally, keeping the view that easily overlooked IoT devices (network cameras, sensors) are full endpoints—and, being numerous, tend to slip out of the asset register and become a security hole—connects to the later security chapter.

3.3.3Section summary

• Endpoints are edge devices that produce/use data: PCs, mobiles, IP phones, printers, servers, IoT
• Distinguish clients (consuming) from servers (providing) by role; switch the suspect side by whether the symptom is "everyone" or "only that person"
• An IP phone is PoE-powered and delay-sensitive; IoT devices are numerous, easily missed, and prone to being a security weak point