Last night i was connecting up to a direct connect server, as i do fairly often, and tried a search. The server booted me off, claiming my IP was set incorrectly (you can't search from a different IP than the hub thinks you're connected from).
Either way, it reported i had an ip in the '82.25.44.*' range, where as it used to be '213.106.127.*'. Strange.
So i telnet into my router, and give it a reboot. Sure enough it picks up the new IP, and everything works fine, with regards to actually having a connection.
While it would be nice to know why the IP range was changed, this comes second to discovering why performance has completely degraded since the switch. Ping times are fine to all for corners of the earth, but packetloss is sometimes hitting 50%, without load on the line - not good!
I'm in the Manchester area (specifically Pendleton, Salford).
spc1-ward3-3-1-cust***.bagu.broadband.ntl.com
Anyone else having problems?
__________________
Following..
2 simultaneous pings to two servers, one in the .US, one in .NL.
To US server:
Quote:
Request timed out.
Request timed out.
Request timed out.
Reply from 80.247.199.35: bytes=32 time=182ms TTL=51
Reply from 80.247.199.35: bytes=32 time=27ms TTL=51
Request timed out.
Reply from 80.247.199.35: bytes=32 time=33ms TTL=51
Request timed out.
Reply from 80.247.199.35: bytes=32 time=81ms TTL=51
Request timed out.
Reply from 80.247.199.35: bytes=32 time=32ms TTL=51
Reply from 80.247.199.35: bytes=32 time=29ms TTL=51
Reply from 80.247.199.35: bytes=32 time=33ms TTL=51
Reply from 80.247.199.35: bytes=32 time=31ms TTL=51
Reply from 80.247.199.35: bytes=32 time=27ms TTL=51
Reply from 80.247.199.35: bytes=32 time=119ms TTL=51
Reply from 80.247.199.35: bytes=32 time=35ms TTL=51
Reply from 80.247.199.35: bytes=32 time=96ms TTL=51
Reply from 80.247.199.35: bytes=32 time=35ms TTL=51
Reply from 80.247.199.35: bytes=32 time=28ms TTL=51
Reply from 80.247.199.35: bytes=32 time=28ms TTL=51
Reply from 80.247.199.35: bytes=32 time=30ms TTL=51
Reply from 80.247.199.35: bytes=32 time=110ms TTL=51
Request timed out.
|
To .NL server:
Quote:
Request timed out.
Request timed out.
Request timed out.
Reply from 70.86.12.11: bytes=32 time=221ms TTL=113
Reply from 70.86.12.11: bytes=32 time=121ms TTL=113
Request timed out.
Reply from 70.86.12.11: bytes=32 time=142ms TTL=113
Request timed out.
Reply from 70.86.12.11: bytes=32 time=197ms TTL=113
Request timed out.
Reply from 70.86.12.11: bytes=32 time=132ms TTL=113
Reply from 70.86.12.11: bytes=32 time=123ms TTL=113
Reply from 70.86.12.11: bytes=32 time=159ms TTL=113
Reply from 70.86.12.11: bytes=32 time=134ms TTL=113
Reply from 70.86.12.11: bytes=32 time=122ms TTL=113
Reply from 70.86.12.11: bytes=32 time=158ms TTL=113
Reply from 70.86.12.11: bytes=32 time=159ms TTL=113
Reply from 70.86.12.11: bytes=32 time=172ms TTL=113
Reply from 70.86.12.11: bytes=32 time=128ms TTL=113
Reply from 70.86.12.11: bytes=32 time=139ms TTL=113
Reply from 70.86.12.11: bytes=32 time=124ms TTL=113
Reply from 70.86.12.11: bytes=32 time=123ms TTL=113
Reply from 70.86.12.11: bytes=32 time=228ms TTL=113
Request timed out.
|
And for good measure, a tracert to smtp.ntlworld.com:
Quote:
1 1 ms 1 ms 1 ms 192.168.0.1
2 12 ms 10 ms 11 ms 10.19.128.1
3 62 ms * * oldh-t2cam1-b-ge-wan44-130.inet.ntl.com [80.5.165.193]
4 * 36 ms 41 ms mant-t2core-b-ge-wan81.inet.ntl.com [213.104.242.201]
5 * 143 ms * man-bb-b-so-210-0.inet.ntl.com [62.253.184.61]
6 * 67 ms 79 ms win-bb-a-so-300-0.inet.ntl.com [62.253.185.138]
7 80 ms 125 ms * win-dc-a-v903.inet.ntl.com [213.105.174.34]
8 21 ms 25 ms 18 ms smtp.ispmail.ntl.com [81.103.221.11]
|