![]()
You could also have a bad switch, which can be tested by swapping in a known good switch to each suspect switch.ģ. ![]() Someone suggested you also check for loops, one port plugged into another. There's an old rule of thumb called the 5-4-3 rule when ethernet was still young and hard coax with vampire taps had strict limits of performance. Daisy chained switches congregate traffic into a single port, then again on upstream daisy-chained switches. That process will likely uncover the next issue.Ģ. If you find bad crimps consider replacing with commercial cables. Corrupted frames tell you there's a wiring problem, probably a bad crimp. SPICEWORKS NETWORK SPEED TESTER PLUSYou are looking for multiple DNS and DHCP sources to start, plus corrupted retries. You'll need to temporarily span ports to see anything. Start at the inside port on the firewall and drill down to each switch. Check from multiple points in the LAN, don't worry about the WAN side yet since multiple reports say it is unsaturated. Others have suggested wireshark and I agree. ![]() Bad wiring can be hidden by low network traffic volumes, but becomes too much as re-transmits really go crazy under busy network volumes.īut if it were me, sniff the network to see what's happening at the logical level.ġ. The connection appeared to work until network traffic volume got up (and the network retransmits overwhelmed the shared LAN).and chopping off the head of that wire and re-connecting a new RJ-45 head on it fixed the problem. I've had one bad wired connection cause this sort of problem in the past. For example, are the docking stations connected using physical wired connections? If so, start not allowing one of the docking stations (at a time) from being active.and see if the problem stays away when one of the docking stations is not plugged in. But you will get some idea of who's complaining about what.that can point you in the right direction.Īlso, when trying to troubleshoot an unknown network problem, work the problem from the ground up and top down. You're likely going to see lots of retransmissions and FIN-ACKs on the bad segment. Realistically you would sniff a known good time and a known likely bad time and compare the results. Get Wireshark and sniff the network at one of the bad connection points. Apart from all the above, what else can I do? ![]() SPICEWORKS NETWORK SPEED TESTER MACWhat else can I check? I'd say the issue is either with a Mac or the docking station but I want to make be definite that the network isn't the issue. The only thing I notice is that on YouTube the videos seem sluggish but nothing major. SPICEWORKS NETWORK SPEED TESTER WINDOWSI'm running a Windows machine and am sat in the office which is now empty. SPICEWORKS NETWORK SPEED TESTER DOWNLOAD
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |