Insights

Network Connectivity: How It Works and How to Check It

Network connectivity lets devices exchange data. Learn how wired and wireless links work and how to check reachability, DNS and application access.

Network connectivity: how it works and how to check it: USB Ethernet adapter with glowing link light, with the doxxnet wordmark.
On this page

Network connectivity is the ability of devices to communicate and exchange data across a network, over wired or wireless connections. It takes a working connection medium, compatible protocols, and the right addressing and network configuration. Being connected to Wi-Fi or Ethernet doesn't by itself mean you can reach the internet or a particular service.

In short:

  • "Connected" isn't "working." Name the two endpoints and the task you're testing.
  • Check one stage at a time: local link, addressing, local reachability, DNS, then the application.
  • Reachable doesn't mean permitted. Access controls are a separate layer.

A connection means you can exchange data

Connectivity describes whether you can communicate with a destination. It's not just a connected icon in the corner of your screen. Your laptop might reach a local printer while internet access is down. In that case the connection between the laptop and the printer works, even though the path to a remote website doesn't.

A local connection usually supports communication inside your local network. Reaching a remote destination also needs a working path beyond that network. Devices exchange information through hardware and software over a physical or wireless medium. That connection is one part of the path. It isn't proof that every destination is reachable.

When you check connectivity, name both endpoints and the task. "Can this laptop print?" is more useful than "Is the network working?" because it separates a working local connection from an unavailable remote destination.

How data reaches another device

A network adapter connects your device to the communication medium, such as a cable or a wireless signal. Protocols are the rules devices follow to exchange and interpret data. Data travels in packets, which are small units sent toward a destination.

Take a simple webpage request. DNS turns the website's hostname into an IP address. The hostname is the readable name, and the IP address identifies the destination on the network. Addressing and naming identify devices and resources, so even a working connection needs the right destination information.

Switches carry traffic within a local area network (LAN), like the network connecting your home devices. Your device's address and subnet mask help it decide whether a destination is local. The default gateway is the router it uses to reach other networks. Routers read each packet's destination IP address and use a routing table to decide where to send it next. A wide area network (WAN) connects networks over a larger area, and a request for a remote webpage needs a path beyond your LAN.

The destination service also has to accept and handle the request. Reaching a server's network address doesn't show that its website is available or that your account is allowed to use it. This matters when one application fails while other traffic works, because the problem may be at the service and not in your local connection.

Wired and wireless ways to connect

Network connections can be wired or wireless. Wired connections usually suit fixed devices, and wireless ones suit mobility or cases where you'd rather avoid a cable. The choice depends on the link you need. It isn't a universal ranking of speed or security.

Connection methodTypical usePractical limit
EthernetFixed local devices connected over copper or fiberNeeds a suitable cable connection and compatible equipment
Wi-FiMobile devices joining a local networkNeeds a working wireless link. Joining Wi-Fi doesn't guarantee internet access
BluetoothCommunication between nearby devicesA nearby-device connection doesn't give you a path to remote services
CellularWide-area access for mobile devicesNeeds coverage and an active service connection
SatelliteWide-area access through a satellite linkNeeds suitable equipment and a working service connection

Ethernet, Wi-Fi, Bluetooth, cellular and satellite are all ways to establish network connectivity. They can serve different parts of a communication path instead of replacing one another.

For example, your laptop may use Wi-Fi to reach your router, while your internet service provider supplies the path beyond your local network. A working Wi-Fi link can't make up for a failed connection further along. And working internet service can't help a laptop that has lost its local link to the router.

Reachability is not the same as performance

Reachability asks whether communication with a destination succeeds. Performance asks how well that communication supports your task. Bandwidth is the capacity for data flow, while latency is the delay before a response.

Throughput is the transfer rate you actually get, which isn't the same as the connection's capacity. Packet loss means some packets never arrive. Tracking packet loss, latency and bandwidth use helps diagnose network problems, but no single number describes every application's experience.

A file transfer needs sustained throughput, because the goal is to move data. A voice or video call is also sensitive to delay and loss, because a conversation needs timely delivery. So a connection can move files perfectly well and still make a call feel unreliable.

A ping availability check sends an Internet Control Message Protocol (ICMP) echo request to a destination. A successful reply only tells you about that tested path and response. It doesn't mean a website, file transfer or call will work well. Test the affected application and judge the measurements against what it needs, instead of relying on a universal "acceptable" number.

Check the path one stage at a time

Start with the affected device and destination, then work outward from the local link. Comparing another device or destination helps you separate a device-specific problem from a shared network or service problem.

  1. Identify what fails. Note the affected device, destination, application and any error message. If another device reaches the same destination, that path works and yours needs a closer look. If both fail, try a different destination to see whether one service is the problem or access is broadly affected.
  2. Inspect the local link. Check that the cable is plugged in or that the device has joined the right Wi-Fi network. A connected status only reports the state of the link. It says nothing about internet or application access. If there's no link, inspect the connection equipment, and compare with another authorized device on the same local network.
  3. Review addressing in network settings. Check the assigned IP address, subnet mask and default gateway against what the network should be using, since correct IP configuration matters for connectivity. Values being present doesn't mean they're correct. If settings are missing or unexpected, that suggests an addressing problem. Compare the pattern with a working device, but don't copy its individual address.
  4. Check local reachability. Try an approved local destination, such as your router or a known local service. A reply shows the tested local path works. A failure points to a local path, the destination or filtering. Try another local destination, and remember that an unanswered ping can mean filtering, not an outage.
  5. Separate external reachability from name resolution. Check an authorized external destination and whether DNS resolves the hostname you need. A successful external check shows that tested remote path works, and a successful lookup shows name resolution works. Neither shows the service itself is available. If local checks pass but remote ones fail, look at the onward path. If resolution fails, try another hostname before you blame DNS.
  6. Test the actual application. Open the affected service or repeat the action that failed. If it works, that operation works under current conditions. If it fails after the earlier checks pass, focus on the service, its configuration or its access requirements. Try the same application on another authorized device, or another service from the affected device.

Review firewall rules and access policies when legitimate traffic seems blocked, instead of turning protections off as a test. A restriction may be intentional. If you have to change a configuration, get authorization, record the original values and have a way to restore access before you make the change.

Keep private access separate from public reachability

Connectivity means communication is possible. It doesn't mean it's confidential or permitted. A reachable service may still need encrypted transport, identity checks and limits on who can use it. Access controls limit permission based on credentials or factors such as device or location.

For a self-hosted service, decide which devices or identities should have access before you set up the connection. If an agent needs to use that service, give it the access its task requires instead of assuming every connected participant should be allowed. Keep application authentication and certificate validation in place, and prefer private access for remote administration over exposing it directly to the public internet.

Blocked traffic is a connectivity fault when it stops intended access. It's the correct result when an access policy excludes that device or service. Check both outcomes with approved tests: an allowed device or identity should reach the service, and an excluded one shouldn't. If the result is different, check the relevant access policy before you change the network path.

Ask an AI assistant

Share this article

Private Everywhere

Stop giving the internet everything

Keep your browsing, messages, files, and agents private.