To test network installations for bad cabling or bad anything else I would run some traffic over it. There are a few ways to do it.
Copy some files. Tough to saturate the network since there are disk drives and the utterly horrible microsoft network file protocol (CIFS) getting in the way. Can be done with no special expertise. One way round this is to use ftp, say Filezilla client and server pair. This is a much more efficient protocol. You can copy some big files and do several at once (>1 thread).
Robocopy can copy multiple files at once generating more traffic. /MT. Default is 8 which with big files will be quite a bit of traffic.
A simple ping can generate a surprising amount of traffic if a number of copies and large packets are used.
start cmd /c ping 192.168.1.87 /l 64000 /n 10
To run 3 copies:-
FOR /L %y IN (0, 1, 3) DO start cmd /c ping 192.168.1.87 /l 64000 /n 10
You will learn to check carefully and test with a small number of instances once you have had to close 200 windows manually when it all goes wrong.
Look at psping - a microsoft tool.
https://learn.microsoft.com/en-us/sy...wnloads/psping
The real tool is ttcp, the MS version is NTttcp. Not so easy to use.
https://github.com/microsoft/ntttcp/releases/tag/v5.39
You can look at interface error counts with perfmon or
netstat -e.
There is also iperf but I am not so familiar with it.