Superhub 3 won't do gigabit connection on longer Ethernet cables
27-12-201617:53 - edited 27-12-201617:55
Our house is fully patched in with cat 5e network cables. When I initially set everything up, I had to use another wireless router connected to the superhub (for various reasons, including the superhub 3 didn't used to work with Chromecast 1s - it does now). Everything worked as expected and I could get decent speeds)
I now need to move that router to somewhere else on the house. This has presented a new problem - the superhub won't connect above 10Mbps (megabits) on the same cable run. I've got 3 x 20 meter cables pulled back from a gigabit switch to the same spot in the office and they all behave the same with the superhub, however I can clock a sustained 90MBps+ (megabytes - I.e. near maximum theoretical speed for gigabit Ethernet) using any of the same cables with my home server and desktop or laptop.
The only solution I have at the moment is to stick another cheap old gigabit switch in-between the superhub and wallplate. This shouldn't be necessary though - it's another device I have to run that draws power.
So, the question: is there a known problem with the chipset in the device when used with longer cable runs? Are they bad at handling potential noise or interference, or do I have a faulty one? I'm confident my cabling is OK, otherwise I'd see issues with latency or bandwidth!
Re: Superhub 3 won't do gigabit connection on longer Ethernet cables
Hmm, that sounds bad and could explain why someone else had problems copying files via the switch in the hub.
Is the 10Mbps connection determined leds on the switch or pc netowork card properties at the other end or is it based on throughput.
I could imagine it possibly dropping to 100Mbps but 10!!!
I can manage a 1gig connection through standard cat5 (no easy way to upgrade at the moment), although only about 300Mbps throughput, however my hub is connected in modem mode so I've never tried a long connection to it directly.