bignose:
cat5 should be able to handle gigabit over short-ish runs unless it's trully awful, given your link speed is only 100mbits there's a good chance you've got issues either at the patch board or at the wall sockets and don't have all 4 pairs wired correctly (100 only needs the outer pairs) - grab yourself a cheap ethernet cable tester and check for crossed-over pairs etc (you'll need it anyway if you go ahead and replace that awful/ugly patch board with a proper modern distribution panel)
Purchasing a tester as we speak!
What modern distribution panel do you recommend?
Talkiet:
TimmyJackson:
Gotcha yes the Latency dose increase to around 34 ms when testing to the local spark server in Christchurch, that to me also seams abnormally high?
Yes, that's too high... Try pinging 219.88.188.134 please... If you're in Chch it should be 2-4ms...
Cheers - N
ping 219.88.188.134
PING 219.88.188.134 (219.88.188.134) 56(84) bytes of data.
64 bytes from 219.88.188.134: icmp_seq=1 ttl=59 time=39.0 ms
64 bytes from 219.88.188.134: icmp_seq=2 ttl=59 time=34.4 ms
64 bytes from 219.88.188.134: icmp_seq=3 ttl=59 time=34.4 ms
64 bytes from 219.88.188.134: icmp_seq=4 ttl=59 time=34.4 ms
64 bytes from 219.88.188.134: icmp_seq=5 ttl=59 time=33.5 ms
^C
--- 219.88.188.134 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4005ms
rtt min/avg/max/mdev = 33.589/35.194/39.008/1.940 ms
traceroute to 219.88.188.134 (219.88.188.134), 30 hops max, 60 byte packets
1 localdomain (192.168.1.1) 0.579 ms 0.745 ms 0.915 ms
2 100.72.0.1 (100.72.0.1) 34.656 ms 34.667 ms 34.708 ms
3 10.200.1.24 (10.200.1.24) 34.816 ms 34.855 ms 34.893 ms
4 10.200.1.24 (10.200.1.24) 34.749 ms * *
5 x1-1-1-200.akcr11.global-gateway.net.nz (122.56.118.89) 34.933 ms 34.973 ms 35.012 ms
6 mdr-ip24-dom.msc.global-gateway.net.nz (122.56.116.10) 35.076 ms 34.384 ms 34.406 ms
7 cache.google.com (219.88.188.129) 36.383 ms 34.272 ms 34.250 ms
Yeah Christchurch based.. ManOhMan there is some serious issues here!