Network Troubleshooting Commands
A field reference for the built-in Windows commands used constantly in radio-system network troubleshooting (dispatch PCs, gateways, site LANs). Each entry: what it answers, and the radio-support situation it fits. Linux equivalents noted where they differ meaningfully.
The Core Kit
| Command | Question it answers | Notes |
|---|---|---|
ping <ip> |
"Is the IP path to this device alive right now?" | Sustained: ping -t. Size/DF probing for MTU: ping -f -l <bytes>. Interpretation caveats on ICMP and Ping — silence ≠ down. |
tracert <ip> |
"Where along the path does it die or slow down?" | Linux: traceroute/mtr. Middle-hop ICMP suppression is normal — judge end-to-end. |
ipconfig /all |
"What is this PC's actual network config?" | The first command on any misbehaving dispatch PC: confirms address, mask, gateway, DNS, DHCP lease, and which adapter has them — multi-adapter confusion is a documented failure source (Windows PC Configuration). Linux: ip addr. |
ipconfig /release + /renew |
"Force a fresh DHCP lease." | The standard 169.254.x.x (APIPA) recovery step once the DHCP path is fixed. |
ipconfig /flushdns |
"Stop using a cached, stale DNS answer." | After DNS record changes; see DNS. |
arp -a |
"What MAC does this IP resolve to locally?" | Duplicate-IP hunting: a flapping MAC for one IP is the smoking gun (ARP). Linux: ip neigh. |
nslookup <name> |
"What does DNS actually return for this name, from this resolver?" | Isolates name-resolution failures from path failures. Linux also: dig. |
netstat -ano |
"What ports is this PC listening on / connected to, and which process owns them?" | Port-conflict and is-the-service-listening checks (e.g., confirming a dispatch client's connection to a gateway's port 48222). Linux: ss -tulpn. |
route print |
"Which interface/gateway will traffic to X actually use?" | Multi-adapter and VPN-routing puzzles; interface metric surprises. Linux: ip route. |
A Standard Escalation Sequence
The layered methodology in Troubleshooting RoIP and Gateway Connectivity maps to commands roughly as: ipconfig /all (is this end sane?) → ping same-subnet target (local reachability) → ping far end (routing) → tracert if it fails mid-path → nslookup if names misbehave → netstat/port test at the application layer → packet capture as ground truth when the commands disagree with the symptoms.
Cautions
- Run from the relevant machine: a healthy ping from the technician's laptop proves nothing about the dispatch PC's path.
- Command output is a snapshot; intermittent faults need sustained tests and logging, not one-shot checks.
Related Pages
- Networking: ICMP and Ping
- Networking: ARP
- Networking: DNS
- Networking: DHCP
- Troubleshooting RoIP and Gateway Connectivity
- Wireshark and Packet Capture
References
This article is part of the CTI Products Knowledge Base. Questions about RadioPro or MCN products? Call +1 (513) 595-5900 or email info@ctiproducts.com.
Informational only. This article is general background and is not engineering, safety, legal or regulatory advice. Verify requirements with the equipment manufacturer and the applicable authority before relying on it. Product names and trademarks belong to their respective owners.