Wired, Wi-Fi, and Cellular Access Methods

Wired, Wi-Fi, and Cellular

Endpoint connectivity uses one of three access methods, and each leaves different evidence. Wired Ethernet depends on a NIC, cable, wall jack, patch panel, and switch port. Wi-Fi depends on a radio, an SSID, authentication, access-point coverage, and radio conditions. Cellular depends on a carrier, a SIM or embedded SIM (eSIM) profile, signal, and a data plan. Many devices support two or three at once, so the first job is confirming which path is active.

Wired Ethernet

Wired Ethernet is usually the most predictable method: a dedicated physical link from the endpoint to a switch port. It is standard for desktops, printers, IP phones, access points, cameras, and servers. Healthy clues are obvious: cable plugged in, link light on, OS shows connected, switch port up at the expected speed. It still fails from damaged patch cords, the wrong wall jack, an administratively disabled port, a bad dock, a wrong VLAN assignment, 802.1X authentication failure, or a static-IP typo.

Wi-Fi

A Wi-Fi client joins a Service Set Identifier (SSID) advertised by an access point and must match its security, commonly Wi-Fi Protected Access 2 (WPA2) or WPA3. Wi-Fi uses radio bands:

Association happens in stages: radio on, SSID visible or manually entered, correct passphrase or enterprise credentials, association to an access point, then valid IP settings. A client can read "connected" yet have no internet because DHCP failed, DNS is wrong, a captive portal is pending, or the upstream is down. Always separate "joined the SSID" from "reaches resources."

Cellular

Cellular uses a mobile carrier rather than a local switch or access point, over 4G LTE or 5G. Phones, tablets, laptops with cellular modems, hotspots, and cellular routers all use it. Cellular can be the primary link for mobile workers, a backup WAN for a branch router, or a temporary hotspot. Troubleshooting checks signal strength, airplane mode, SIM/eSIM status, the carrier plan and roaming, data limits, hotspot settings, and whether the app is allowed to use cellular data.

Automatic Path Selection Is the Big Trap

Devices pick paths on their own. A phone may prefer Wi-Fi but jump to cellular when Wi-Fi has no internet. A laptop may use wired when docked, Wi-Fi when not, and a VPN for corporate apps. Some operating systems keep several interfaces up and route by priority metric. So a user who says "the network works" may be browsing over cellular while the corporate Wi-Fi is actually failing. Disable or disconnect alternate paths only when appropriate, then test the intended path directly.

Avoid absolutes: wired is not always fastest (a link can negotiate low), Wi-Fi is not always flaky (good design and light load perform well), and cellular is not always "just backup" if the business runs on it. The real question is whether the endpoint is on the correct method, holding correct settings, and reaching the expected service.

Separating Association from Reachability

The most testable Wi-Fi concept is that joining a network is not the same as using it, and the same idea applies to wired and cellular paths. A client can be associated to an access point, show a strong signal, and still be unable to reach anything because DHCP never handed it an address, because it received an address but no usable gateway, because DNS is wrong, or because a captive portal is intercepting traffic until the user signs in. Walk the layers in order: confirmed association, valid IP and gateway, gateway reachable by ping, DNS resolving names, then the actual application.

If you skip to "the website is down" before confirming the client even has a gateway, you will chase the wrong layer. This layered habit is identical across wired, Wi-Fi, and cellular, which is why the exam frames it as one workflow with three sets of physical clues.

Quick Comparison of the Three Access Methods

• Wired Ethernet: dedicated link, easiest to verify, fails on cable, port, dock, VLAN, 802.1X, or static-IP errors; check link light and switch port first.
• Wi-Fi: mobile and shared, fails on SSID/security mismatch, weak signal, congestion, captive portals, or DHCP/DNS after association; check association then addressing.
• Cellular: carrier-dependent, fails on signal, SIM/eSIM, roaming, data limits, or per-app data restrictions; check signal and plan, and confirm it is not silently substituting for Wi-Fi or for the docked wired connection the user assumes is active.

A disciplined technician names the active method out loud, verifies the layers for that method, and only then concludes whether the network or the endpoint is at fault, which keeps escalations precise and prevents the all-too-common report that "the internet is broken" when only one path is.