01 — Command Quick Reference
| Command |
Purpose |
Key Output to Watch |
| ipconfig |
Shows IP address, subnet mask, and default gateway. |
APIPA address (169.254.x.x) = DHCP failure. Compare gateway between machines on the same subnet. |
| ipconfig /all |
Adds DNS server addresses and MAC address to the output. |
DNS = 0.0.0.0 = no connectivity to DNS servers. Confirms whether assignment is DHCP or static. |
| ping |
Tests end-to-end connectivity and round-trip time. |
Timeouts = no path; consistently high ms = latency problem; variable ms = jitter; mixed = congestion or loss. |
| ping -n [count] |
Extended test using more packets for a more reliable pattern. |
More packets reveal intermittent loss that 4-packet default ping misses. Use -n 10 or -n 20 for better data. |
| tracert |
Shows each hop (router) on the path to the destination. |
First-hop latency is critical. Where does the delay start? A slow hop 1 points to a local routing issue. |
| pathping |
Combined tracert and extended ping with per-hop statistics. |
Loss% per hop. Distinguishes link loss (between two hops) from node loss (at a specific hop). |
| netstat -e |
Shows cumulative Ethernet interface error and byte counts. |
High error count = physical layer problem (cable, NIC, switch port). Near-zero errors = hardware is healthy. |
| nslookup |
Tests DNS name resolution for the target host. |
Failure = DNS server unreachable or misconfigured. DNS working + connectivity issues = routing problem, not DNS. |
02 — Reading IP Configuration
- 169.254.x.x — APIPA address. Windows assigned itself a fallback address because DHCP did not respond. No gateway, no DNS, no internet. First check: physical connection.
- Gateway 0.0.0.0 — No default route configured. Packets have nowhere to go beyond the local subnet. Usually accompanies an APIPA address.
- DNS 0.0.0.0 — DNS server is unreachable or was never assigned. DNS failures cascade into application failures — the softphone cannot resolve the VoIP server hostname.
- Mismatched gateways between two machines on the same subnet — One machine is routing through a different path. Compare the Default Gateway field between the problem machine and a healthy machine side by side. A difference here is a critical clue.
03 — VoIP Quality Thresholds
| Metric |
Good |
Acceptable |
Poor |
| Latency |
< 100ms |
100–150ms |
> 150ms |
| Jitter |
< 20ms |
20–30ms |
> 30ms |
| Packet Loss |
< 1% |
1–5% |
> 5% |
| MOS Score |
> 4.0 |
3.0–4.0 |
< 3.0 |
MOS (Mean Opinion Score) is a composite voice quality rating. Below 3.0, callers will notice degradation. Below 2.0 is effectively unusable for business communication.
04 — Troubleshooting Approach: The Comparison Method
When one site has VoIP problems and another does not, always compare ipconfig output between the problem machine and a healthy machine on the same network first. Look for differences in these fields:
- IP Address range — Are both machines in the same subnet? An APIPA address immediately tells you DHCP failed.
- Default Gateway — Are both machines pointing to the same router? A different gateway means different routing paths — and potentially very different latency.
- DNS Servers — Are both machines using the same DNS? DNS failure looks different from connectivity failure — nslookup distinguishes them.
The difference between the two machines is your first clue. Start there before running any other commands.
05 — Common Output Patterns
| What You See |
Likely Cause |
Where to Look Next |
| APIPA address + 100% ping loss |
No physical or DHCP connectivity |
Check cable, switch port, NIC, wireless adapter |
| Valid IP + high latency + 0% loss |
Routing through a slow path |
Compare gateways between machines; check tracert hop 1 |
| Valid IP + variable ping times |
Wireless interference or network congestion |
Check signal strength; run pathping for pattern over time |
| Valid IP + 20–30% loss |
Congestion or a bad link |
pathping to identify which hop drops packets |
| DNS timeout but ping works |
DNS server unreachable or misconfigured |
Run nslookup; verify DNS server IP in ipconfig /all |
06 — Real-World Context
- Static IP vs. DHCP: DHCP is convenient but hands gateway assignment to the DHCP server. A misconfigured DHCP server delivers the wrong gateway to every machine that requests an address. Assigning a static IP lets the technician manually specify the correct gateway — bypassing the bad DHCP assignment. This is a temporary fix; the DHCP server should be corrected afterward.
- Physical layer first: Network troubleshooting almost always starts physical. A disconnected cable, a failed switch port, or a bad NIC will produce the same symptoms as a complex routing problem. Eliminate physical causes before chasing configuration issues.
netstat -e error counts and APIPA addresses both point toward the physical layer.
- Comparison is a superpower: A healthy machine on the same network is the fastest diagnostic tool available. If you cannot explain why the problem machine's output differs from the healthy machine's output, you have not found the root cause yet. Run the same commands on both machines and diff the results.