Establish the failure boundary before touching the network
Intermittent connectivity is difficult because users report what an application did, not necessarily what failed in the network. A web page may stall because DNS returns the wrong address, a wireless client is retrying frames, an identity service is slow, or a remote API has stopped responding. Rebooting a router before collecting evidence can erase the information needed to distinguish these cases. The first task is to establish scope: which applications, people, devices, locations and time periods are affected.
Record an exact timestamp, client address, access method, error text and the last known successful attempt. Compare a failing client with another client on the same access point, VLAN or wired switch. Verify whether only internet destinations fail or local services fail as well. A fault affecting one computer is usually diagnosed differently from one affecting every office, while a fault seen only during a shift change may suggest authentication, capacity or lease-renewal behaviour.
Use reversible observations before changing configuration. Checking interface status, address information, route tables and name resolution is safer than changing firewall policy in the hope that something improves. When a change is required, record the original state and have a rollback. This discipline helps isolate causes and protects users from a series of uncontrolled ‘quick fixes’.
Physical connectivity, addressing and gateway reachability
At the physical and data-link layer, check that the expected interface is enabled and linked, with no abnormal error, discard or flap counters. A damaged Ethernet cable, unstable transceiver, incorrect switch-port VLAN, or power problem on a wireless access point can produce symptoms that higher-layer application tests cannot explain. In wireless environments, association to an SSID does not prove that the client has a usable network path.
Next inspect the client’s IP address, subnet mask or prefix length, default gateway and DNS servers. An address from an automatic private addressing range on a network expecting DHCP is a clue that normal assignment may have failed. An apparently valid address can still be wrong if it belongs to a neighbouring subnet or an unauthorised static configuration. Verify the DHCP scope and whether the gateway is reachable from that exact address.
Address assignment is a common source of confusion in multi-VLAN networks. A client broadcast may require a router or switch configured to forward requests to a central server; an incorrect DHCP relay can leave some segments without leases while other users continue working. Check scope exhaustion, reservations, relay destinations, denied addresses, and competing DHCP servers. Replace guesses with evidence from client lease status and server logs.
Duplicate addresses and IP exhaustion are distinct faults
Two devices configured with the same IPv4 address may cause intermittent connectivity as neighbour tables or address-resolution entries change. Symptoms can include reachability that alternates between devices, duplicate-address warnings, or unexpected traffic reaching the wrong host. Correlate switch MAC tables, ARP records, static assignments and DHCP leases; do not merely choose a different address at random, because the original conflict may return.
IP exhaustion means an allocation pool cannot supply enough usable addresses. The effect may appear when new users arrive, guest devices join, or leases remain allocated after equipment is removed. Confirm the scope size, lease duration, reservations and actual occupancy before expanding it. A larger subnet without updated routing and firewall policy may create a different problem, and shortening lease duration may be inadequate when legitimate simultaneous demand exceeds capacity.
A reliable fix also addresses the administrative cause. Reserve static infrastructure addresses, document exclusions, identify rogue DHCP services and monitor exhaustion trends. When users have assigned their own addresses, provide a supported configuration route rather than assuming the issue is solely technical. Incidents can recur if the configuration policy remains unclear.
DNS failures can look like total connectivity loss
If an application fails by name but succeeds by IP address, DNS is a leading suspect, though TLS hostnames and application routing require care when testing. Check the resolver assigned to the client, whether it responds, the records returned, and which suffix search rules are applied. Split-horizon DNS and private cloud zones may intentionally resolve a service differently inside and outside the company network.
Time-based failures may involve stale caches, invalid changes, missing records or a resolver that is intermittently unavailable. Compare authoritative answers with recursive-resolver responses and account for TTL values. Be careful with ‘flush DNS’ as a universal fix: it may temporarily change symptoms while the underlying server record or forwarding configuration remains wrong.
Some applications depend on service-discovery or specific network paths after name resolution. An apparently correct DNS answer is not proof that the destination listens on the expected port or that a firewall permits the flow. Validate the sequence from name to address, route, transport connection and application response instead of stopping after a successful ping.
Routes, filtering and network boundaries
Routing problems often affect a subset of destinations. Examine the client’s default route, interface metrics, and where a packet should travel through VLAN gateways, virtual networks, VPNs and cloud environments. A correct-looking default route does not rule out a missing more-specific route or asymmetric return path. Trace tools can help identify changes in the forwarding path but their output must be interpreted with awareness of ICMP filtering and rate limiting.
Firewall and security-policy problems demand disciplined checks. First identify the source, destination, protocol and direction of the failing flow. Review the effective rules and associated logs rather than disabling an entire policy to test a hypothesis. An ACL allowing TCP connections in one direction may not establish the required stateful response, and security devices can use application identification or identity constraints beyond simple ports.
Change records matter. If reachability failed after a deployment, compare intended and actual route entries, security groups, NAT rules or VPN parameters. Roll back only when the scope and risks support doing so. Network changes have dependencies, so restoring service to one flow must not silently remove isolation for another tenant or subnet.
Wireless interference and contention require radio evidence
Wireless clients share airtime and adapt transmission rates in response to signal conditions. Weak signal, co-channel traffic, overlapping channels, hidden devices and repeated retransmissions can cause delay even when a signal icon shows a strong connection. Identify the client band, access point, channel, signal and noise conditions, and observed utilisation before assuming the solution is higher transmit power.
Antenna placement and building materials shape coverage. Moving an access point or selecting a more appropriate channel can help, but a crowded area may need additional capacity and a better cell plan. Wireless extenders can increase apparent reach while consuming scarce airtime on the backhaul. Test user experience with actual application traffic under representative load rather than one isolated speed-test result.
A common troubleshooting error is conflating Wi-Fi channel contention with Ethernet collisions or WAN bandwidth limits. Full-duplex switched Ethernet behaves differently from a shared wireless channel. Foundational concepts in Network+ help distinguish these layers, while switch counters, packet captures and wireless telemetry establish what the local network is doing. The troubleshooting process should identify the constrained resource before changing hardware.
Measure slowness with latency, loss and throughput separately
A network can carry large files quickly but handle video calls poorly if delay and jitter vary greatly. Conversely, an application can feel slow because of server-side processing even when packet delivery is healthy. Measure loss, round-trip time and throughput along the relevant paths, then correlate with interface utilisation and application logs. Avoid comparing tests made at unrelated times or over different network paths.
For a saturated uplink, investigate which traffic classes consume bandwidth and whether the expected quality-of-service settings apply. For a storage or database application, distinguish network throughput from disk latency, CPU contention or transaction locking. TCP retransmissions may be a useful clue but do not automatically indicate a bad physical link; congestion and endpoint behaviour can also cause them.
Useful monitoring baselines include availability, interface errors, congestion indicators, DNS response time, WAN latency, DHCP pool occupancy and important application transaction time. A baseline turns an occasional report that the network is ‘slow’ into a measurable deviation and helps determine whether a fix actually improved service.
Resolve, verify and prevent recurrence
A network incident should have a reproducible symptom and an explicit verification threshold. Record the affected source and destination, test resolution and routing separately, and compare the result against a healthy host or site when possible. If a change is made to DNS, wireless channel planning, an address pool or a firewall rule, verify the original failing application flow rather than treating a successful ping as full recovery. A durable incident record includes the likely fault boundary, the configuration change, the monitoring signal that confirms it, and the condition that would justify rolling the change back.
Once a likely cause is established, apply the narrowest approved correction. If a DHCP relay is misconfigured, correct that path and test address acquisition from an affected segment. If a route is missing, update the authorised route and validate both forward and return reachability. If radio interference dominates, adjust channel or access-point design and measure airtime and user experience again under normal conditions.
Verification should include the original user workflow, not just an isolated command. A successful ping cannot prove that a login, file share, voice call or business application is restored. Ask the affected user or an authorised representative to repeat the failing task while monitoring the related systems, and check for regressions in neighbouring services.
Document the original symptoms, evidence, root cause when established, exact configuration changes and follow-up monitoring. Where the cause remains uncertain, label it explicitly and arrange further observation rather than inventing a confident explanation. Repeated incidents may justify a formal problem investigation, better alerting, or an architectural change. The lasting goal is a network that can be diagnosed reliably when it fails, not one that depends on routine rebooting and guesswork.