Basic Connectivity Checks

Summary

This note gives a simple first-pass workflow for checking whether a host has basic network connectivity. It is meant as a calm starting point before diving into deeper troubleshooting.

Why this matters

  • basic checks often solve or narrow the issue quickly
  • they stop troubleshooting from turning into random guessing
  • the same pattern is useful in Linux, Windows, servers, homelab, and cloud labs

Environment / Scope

ItemValue
Topicfirst-pass network troubleshooting
Best use for this noteworkstation, VM, or server connectivity checks
Main focusinterface, IP, gateway, DNS
Safe to practise?yes

Key concepts

  • start local before testing remote systems
  • separate IP connectivity from DNS resolution
  • verify what the host believes before blaming the network

Steps / Workflow

1. Check interface state

Confirm the interface is up and has an address.

ip addr

2. Check the route and default gateway

ip route

3. Test the local gateway

ping <gateway-ip>

4. Test external IP connectivity

ping 8.8.8.8

5. Test DNS resolution

nslookup github.com

or:

dig github.com

Commands / Examples

CommandPurpose
ip addrshow interface addresses
ip routeshow route table and default gateway
ping <gateway-ip>test local path to the gateway
ping 8.8.8.8test external IP reachability
nslookup github.comtest basic DNS resolution

Verification

CheckExpected result
Interface checkinterface is up and has expected IP config
Gateway testgateway replies if reachable
External IP testexternal IP is reachable if routing works
DNS testname resolves to an IP address

Pitfalls / Troubleshooting

ProblemLikely causeWhat to check
No IP addressDHCP failure or interface issueinterface state, DHCP lease
Gateway ping failslocal network issue or wrong gatewayroute table, VLAN, cable, Wi-Fi
IP works but names failDNS issueDNS server settings
DNS works but app still failsservice-specific issueports, firewall, app health

Key takeaways

  • check local interface state before testing the internet
  • separate IP reachability from DNS resolution
  • use a repeatable sequence so troubleshooting stays calm and fast