Hands-on tutorial
Tutorials · Troubleshooting
How to Troubleshoot Intermittent Network Drops
Find the cause of connections that drop for seconds at random times: logs, interface counters, spanning tree changes, duplex and cable faults, power, DHCP and Wi-Fi roaming.
Before you start
- Access to switch and gateway logs with correct time (NTP)
- A way to record when drops happen
- Continuous ping or monitoring from affected and unaffected locations
Step by step
Measure it
Run continuous pings from an affected device to the gateway, to a server and to the internet, with timestamps. Where the loss starts tells you which segment fails.
Check logs at the drop times
Look for link up/down, spanning tree topology changes, PoE resets, DHCP conflicts and VPN renegotiations at the same timestamps.
Check interface counters
Rising CRC errors, runts or late collisions point to cabling, connectors or duplex mismatch.
show interfaces gi1/0/10 counters errors show interfaces gi1/0/10 status
Watch spanning tree
Frequent topology changes flush MAC tables and cause short outages. Find the port causing them and fix loops or flapping edge ports.
show spanning-tree detail | include changesCheck power and environment
Devices that reboot at the same time may share a power problem or an overloaded PoE budget.
For Wi-Fi users
Check roaming events, signal levels and interference at the times of drops.
Change one thing at a time
Replace a cable or port, apply one fix, and measure again.
Commands are generic, industry-standard examples. Exact syntax and menu names vary by model and firmware; check your device's manual on the Documentation page.
Pro tips
- Correct time on all devices is essential to correlate events.
- Keep a simple incident log of when users notice drops.
- Swap suspect cables early; they are a common cause.
FAQ
Frequently asked questions
Why do drops happen at the same time every day?
Scheduled tasks: backups saturating links, PoE schedules, DHCP lease timing or a nightly process on a device.
Can a single bad cable affect many users?
Yes, if it is an uplink or causes spanning tree changes.
Keep learning
Related guides
Ping, traceroute and MTR
Read more →Why is my network slow?
Read more →Loop detection and storm control
Read more →How to Troubleshoot Network Problems With Ping, Traceroute and MTR
Find where a connection breaks or slows down in minutes. Use ping for reachability and loss, traceroute for the path, and MTR to see loss and latency on every hop at once.
Read more →How to Capture and Read Network Traffic With Wireshark and tcpdump
When logs are not enough, look at the packets. Capture traffic with tcpdump or Wireshark, filter it down to the problem, and spot retransmissions, DNS failures, DHCP issues and TLS errors.
Read more →How to Test Network Speed Between Two Points With iperf3
Internet speed tests do not tell you how fast your LAN, Wi-Fi or site-to-site link really is. iperf3 measures throughput, loss and jitter between two machines you control.
Read more →Stuck on a step?
Ask Navijin technical support or an authorised partner for help with your configuration.