Independent home-network planning tools
GUIDE / TROUBLESHOOTING

Home network troubleshooting checklist

Narrow the fault from power and physical link through DHCP, gateway, DNS and WAN.

Define the scope first

Determine whether one client, every client on an AP, or the whole wired and wireless network is affected. Record the start time and last change, then compare with a working client.

StageCheckIf it fails
1 PowerLEDs, adapter, UPS, heatCheck the power path and ratings
2 LinkPort LED, cable, negotiated rateCross-test a known-good cable and port
3 AddressIP, mask, gateway, DHCP lease169.254.x.x points to the DHCP path
4 LocalPing gateway, open management UICheck VLAN, Wi-Fi association and host firewall
5 DNSTest an external IP and a nameIf only IP works, inspect DNS
6 WANRouter WAN IP and carrier stateCheck ONT/modem and ISP status

Fast symptom branches

  • Wi-Fi connects but is slow: compare RSSI, congestion, band and wired backhaul.
  • Only the NAS is missing: test reservation, VLAN firewall and direct IP instead of DNS name.
  • Only some sites fail: separate DNS, MTU, IPv6 path and browser issues.
  • Intermittent drops: correlate logs, temperature, DHCP renewals and cable error counters.
Change one variable at a time Retest the same way after each change. Resetting several devices together destroys evidence and extends recovery.

Incident record

Record time / affected clients / wired or wireless / IP / gateway / DNS / WAN / last change / test result to compare recurring faults.

Field case

Assume a laptop joins Wi-Fi but websites do not open. Do not reboot everything together; compare a working phone and preserve evidence through link, address, gateway, external IP and DNS.

Step-by-step verification

1. Record IP, mask and gateway. 2. Test the gateway. 3. Test an external IP and a domain separately. 4. Change one item and repeat the same test.

Interpretation

External IP success with name failure points to DNS. Gateway failure points to local link, VLAN or addressing. Whole-network WAN failure points toward ONT or ISP.

Applicability limits

Blocked ping does not itself prove service failure. Preserve configuration and logs before reset, and correlate intermittent faults with time, heat, DHCP and counters.

Completion criteria

  • Decisions and assumptions are written down.
  • Capacity, security and rollback checks are complete.
  • The design was tested against actual device, ISP and local requirements.

Open related worksheet/tool