Short answer
Run LANtester, point it at a shared folder on another PC or NAS that contains a large file, and press Start test. The program reads the file over and over while pinging the other side five times a second. Leave it running for at least an hour. A healthy card shows a flat throughput line and zero Dropouts; a faulty one falls to zero for a few seconds, and the ping drops out at the same moment.
Step by step
-
Prepare a shared folder with a large file
On a second PC or NAS, share a folder with at least one large file, ideally 1 GB or more. The program finds all files over 64 kB and starts with the largest.
-
Run LANtester and enter the path
A single
LANtester.exe, nothing to install. Type e.g.\\192.168.1.100\shareinto the Share / drive field, or pick the folder with Browse…. A bare\\192.168.1.100is not enough because the share name is missing, but Browse… lists the shares for you. If the folder needs another account, fill in the user and password. -
Check Ping host and Bypass cache
Ping host fills itself in from the path. Leave Bypass cache on: otherwise Windows would serve the file from memory after the first read and the network card would sit idle.
-
Start the test and let it run
Start test starts the load, which runs until you stop it. The top chart shows throughput in MB/s and Mb/s, the bottom one latency. Occasional dropouts need time: an hour is the minimum, overnight is certainty.
-
Save the report
Save report… saves an HTML file with a verdict (stable, stable with reservations, problems found), statistics, charts for the whole run, the log and the network adapters including link speed.
How to read the result
| What you see | What it means |
|---|---|
| Flat throughput, ping without spikes, Dropouts 0 | The connection holds up even under sustained load. |
| Throughput drops to zero for a few seconds, ping drops out at the same time, I/O ERROR and TRANSFER DROPOUT in the log | The typical picture of a failing or overheating network card, or a faulty cable or port. |
| Throughput holds, but the ping spikes | The connection does not drop but gets congested under load; look at an overloaded switch, Wi-Fi or the other side. |
| Around 11 MB/s instead of 110 MB/s | The link negotiated only 100 Mb/s. Usually a cable with a bad pair or a connector; the link speed is in the report next to the adapter. |
A transfer dropout is counted when no data arrives for more than a second. A lost ping shows as a red vertical line and a gap in the curve.
Things to keep in mind
- To find out what is faulty, change one thing at a time: another cable, another switch port, another PC on the other side, and repeat the test.
- If the other side does not answer ping (firewall), the latency chart stays empty. Ping host can be changed, for example to the router.
- Absolute ping values are 0.3–0.5 ms higher because of how they are measured. For spotting spikes and losses that does not matter.
- For a 10 Gb/s link raise Threads to 8–16; for 1 Gb/s the default 4 is enough.
- What is on the network and where is shown by LanAtlas; its Watch feature reports when a device drops out.