Frequently Asked Question

Troubleshooting Network Connectivity Issues

Last Updated 3 months ago

1. Initial Assessment (SOP)Before deep-diving into configurations, define the scope to isolate the point of failure.

Isolate the Scope: Determine if the issue affects a single device (likely a local hardware/software fault) or multiple devices (likely a broader infrastructure issue like a switch, router, or ISP outage).
Verify Physical Layer: Inspect all ethernet cables for damage and ensure they are firmly seated. Check for LED link lights on network ports; no lights usually indicate a physical break or a powered-down device.
Power Cycle: Standard IT practice is to reboot the PC, then the router and modem if needed. Unplug them for at least 30–60 seconds to clear temporary glitches.

2. Logical Connectivity & IP VerificationUse command-line tools to verify that the device is correctly communicating with the network stack.

Check IP Address: Run ipconfig (Windows) or ifconfig (Linux/Mac).
- APIPA Address (169.254.x.x): Indicates the device failed to reach a DHCP server.
- Refresh IP: Run ipconfig /release followed by ipconfig /renew to request a new lease.
Test Connectivity (Ping):
1. Loopback: ping 127.0.0.1 to test the local TCP/IP stack.
2. Default Gateway: Ping your router's IP (e.g., 192.168.1.1) to test the local connection.
3. External IP: Ping a public DNS like 8.8.8.8 to test internet reachability without DNS.

3. DNS & Domain ResolutionIf you can ping an IP address (8.8.8.8) but cannot browse websites, the issue is likely DNS-related.

Flush DNS Cache: Run ipconfig /flushdns to clear potentially corrupted resolution data.
NSLookup: Use nslookup [website.com] to see if your configured DNS server can resolve the hostname to an IP address.
Change DNS Server: If the primary DNS is failing, temporarily switch to a public provider (e.g., Google's 8.8.8.8 or Cloudflare's 1.1.1.1).

4. Advanced Infrastructure DiagnosticsFor persistent or complex issues, use these professional tools to locate bottlenecks:

Trace Path: Use tracert (Windows) or traceroute (Linux/Mac) to identify where packets are being dropped along the path to a destination.
Check for IP Conflicts: Ensure no two devices have the same static IP address.
Inspect Firewall/ACLs: Verify that firewall rules or Access Control Lists (ACLs) are not inadvertently blocking required ports or traffic types.
Analyze Traffic: For intermittent issues, use a protocol analyzer like Wireshark to inspect packet-level data for errors or high latency.

5. Summary Checklist for 2025

For a visual walkthrough of essential network troubleshooting commands and hardware checks: