network troubleshooting commands: A layered workflow for diagnosing connectivity: address configuration, routing, DNS, ports and HTTP response. Work from simple tests to deeper inspection. This guide explains what each command does, its syntax, practical examples, useful options, and common mistakes. Commands are shown for typical installations; flags can vary across operating-system and tool versions.
Before you start
Open a terminal appropriate for the operating system shown in the examples. Check that the required tool is installed and that you are running it with the permissions needed for your task. Replace sample names, paths, hostnames and IDs with values from your own environment.
Syntax at a glance
Square brackets usually indicate optional arguments, while uppercase words such as FILE, HOST and PACKAGE are placeholders that you replace. Keep quotes around paths or text that contains spaces. Commands should be tested on a safe sample before being used in production.
Quick command reference
| Command | What it does | Example | Useful options |
|---|---|---|---|
ping | Check basic reachability and latency | ping -c 4 1.1.1.1 | Windows uses -n for count; Linux/macOS commonly use -c |
traceroute / tracert | Inspect hops on the route to a destination | tracert example.com | Options differ by OS; -n skips DNS names on many tools |
curl -I | Check whether an HTTP endpoint responds | curl -I https://example.com | -L follows redirects; -v provides TLS/connection details |
ss / netstat | Inspect local listening ports and connections | netstat -ano | Linux uses ss; Windows includes netstat -ano |
dig / nslookup | Verify name resolution | nslookup example.com | Specify a resolver to compare answers |
Command syntax and examples explained
1. ping
Purpose: Check basic reachability and latency.
Syntax
ping HOSTExample
ping -c 4 1.1.1.1Options and notes: Windows uses -n for count; Linux/macOS commonly use -c.
ICMP filtering means a failed ping does not prove the application is offline.
2. traceroute / tracert
Purpose: Inspect hops on the route to a destination.
Syntax
traceroute HOSTExample
tracert example.comOptions and notes: Options differ by OS; -n skips DNS names on many tools.
Missing hops often reflect router policies rather than a broken route.
3. curl -I
Purpose: Check whether an HTTP endpoint responds.
Syntax
curl -I URLExample
curl -I https://example.comOptions and notes: -L follows redirects; -v provides TLS/connection details.
Some endpoints do not support HEAD even though GET works.
4. ss / netstat
Purpose: Inspect local listening ports and connections.
Syntax
ss -tulpnExample
netstat -anoOptions and notes: Linux uses ss; Windows includes netstat -ano.
An open local port is not necessarily reachable through the firewall.
5. dig / nslookup
Purpose: Verify name resolution.
Syntax
dig NAMEExample
nslookup example.comOptions and notes: Specify a resolver to compare answers.
Separate DNS issues from routing/firewall/application problems by testing each layer.
Common mistakes and troubleshooting
- Command not found: confirm the tool is installed and available on your PATH; open a new terminal after changing PATH.
- Permission denied: verify the current account, file permissions and target path. Use administrator/root privileges only when genuinely required.
- Unexpected output: check the command version, quoting, current directory and exact arguments. Consult the local help or manual for options supported by your build.
- Destructive operations: preview the target and keep a backup before deleting data, rewriting history, flashing a partition or changing system configuration.
Safety tips
Review every command before running it, especially commands that delete files, change permissions, flash firmware, alter a database or expose a network service. For network scanning and remote administration, work only on devices and systems you own or are authorized to test. Keep credentials, private keys, access tokens and log files private.
Frequently asked questions
Do these commands work on every system?
Not always. Some commands are specific to Windows, Linux, Android, a particular package manager or an installed tool version. Use the syntax shown for your platform and check local help when a flag is unavailable.
Can I copy and run every example exactly?
Use the examples as templates. Replace placeholders such as filenames, package IDs, hostnames and paths with your own values, and verify the effect before executing a command that changes data or system state.
Conclusion
Use this reference as a starting point, then confirm flags in the tool’s official help or manual for your installed version. A clear understanding of syntax, options and side effects makes command-line work more reliable.