Isn’t re-booting the router the IT crowd solution?
Thinking is,
Everything else is fast but peer to peer is slow. What’s different in that scenario? p2p, the packets have to go to the router, which then routes, hence the name, back to the other host. This is reportedly slow. Ergo, the problem is probably piss poor routing.
There’s a million reasons for this. Corrupt ARP table could be one, offhand. Bug in the router which is causing performance issues, overheating, something’s crashed on the protocol stack, etc etc. Which is easier, “log on to the router and attempt to flush the ARP cache” or “turn it off and back on again”?
It’s a cliché, but there’s often a complex technical reason behind simple fixes.
A reboot is step one, incidentally. Could just be that it’s a cheap shit router ofc, and this is just what it does. Could be that there’s some sort of translation required, maybe one device is 802.11g and one 802.11n (*handwave*). Maybe it’s decrypting the WPA encoded packets and reencrypting again, introducing an overhead. Could be that there’s merely a small latency issue (hence slower pings) but the actual data throughput is fine and the entire thing is a red herring; worth timing file transfers to see. Could be there’s updated firmware available which fixes it. I could go on. Generally though, there’s little point in fielding every possible scenario for a given problem because it’s a waste of time if step one actually fixes it. Why type half a dozen paragraphs when a sentence may suffice?
Y’know, just in case anyone else thinks we make this shit up.