lima
26-07-2005, 17:10
Hi forum.
Since the upgrade to Harrogate touchwood everything has been sailing along nicely but this morning I started getting slow web surfing and email "time outs".
Cured the web surfing by nominating a different cache.
Can't cure the email though! I'm managing to connect to my webhosts (not NTL webspace) mailserver located in Manchester about once in every 3 goes and very slowly. I also can't FTP to my (not NTL) webspace because of the packet loss.
Had a similar thing a month ago and although my webhosting company said the webserver was fine their end they moved me to another web server and all was well again. I suspect the change of IP cured the bad link?
Following the support guidelines here's what I've done today:
Problem started this morning about 10am with slow web and no/slow email retreival via Outlook 2000.
Changed cache which cured web surfing (with no proxy selected just "direct connection to Internet" its slow but with Manc Cache 8 manually specified its speedy again)
Rang webhost. No problems with my webspace server their end. Can ping 100% no packet loss.
Rang NTL support. Spoke to guy in India. He can ping my webserver 100% no packet loss from there but I'm getting up to 50% loss from the other side of the M62 :D No resolution really only "see if it clears".
Running XP via a lynksys router BEFSR41.
Slow email/ packet loss on the one other PC connected to the router as well.
Here are the tests I've done. What is weird is that I get 37% loss on pings to my mailserver and no loss on pings to the BBC site, yet the Traceroute shows packet loss for both.
Retrieving mail for my BT Internet accounts and my 1&1 account is fine. It seems like there's just a block to my webhosting server which is on IP 82.219.38.135
Ping test to my mailserver in Manchester
Pinging 82.219.38.135 with 32 bytes of data:
Request timed out.
Reply from 82.219.38.135: bytes=32 time=16ms TTL=56
Reply from 82.219.38.135: bytes=32 time=20ms TTL=56
Reply from 82.219.38.135: bytes=32 time=18ms TTL=56
Request timed out.
Request timed out.
Request timed out.
Reply from 82.219.38.135: bytes=32 time=16ms TTL=56
Request timed out.
Request timed out.
Reply from 82.219.38.135: bytes=32 time=24ms TTL=56
Reply from 82.219.38.135: bytes=32 time=17ms TTL=56
Reply from 82.219.38.135: bytes=32 time=17ms TTL=56
Reply from 82.219.38.135: bytes=32 time=17ms TTL=56
Reply from 82.219.38.135: bytes=32 time=20ms TTL=56
Reply from 82.219.38.135: bytes=32 time=16ms TTL=56
Request timed out.
Reply from 82.219.38.135: bytes=32 time=16ms TTL=56
Request timed out.
Reply from 82.219.38.135: bytes=32 time=16ms TTL=56
Reply from 82.219.38.135: bytes=32 time=16ms TTL=56
Reply from 82.219.38.135: bytes=32 time=25ms TTL=56
Request timed out.
Request timed out.
Reply from 82.219.38.135: bytes=32 time=16ms TTL=56
Reply from 82.219.38.135: bytes=32 time=17ms TTL=56
Reply from 82.219.38.135: bytes=32 time=17ms TTL=56
Ping statistics for 82.219.38.135:
Packets: Sent = 27, Received = 17, Lost = 10 (37% lo
Approximate round trip times in milli-seconds:
Minimum = 16ms, Maximum = 25ms, Average = 17ms
Ping test to BBC
Pinging www.bbc.net.uk (http://www.bbc.net.uk) [212.58.224.116] with 32 bytes of data:
Reply from 212.58.224.116: bytes=32 time=23ms TTL=245
Reply from 212.58.224.116: bytes=32 time=19ms TTL=245
Reply from 212.58.224.116: bytes=32 time=20ms TTL=245
Reply from 212.58.224.116: bytes=32 time=20ms TTL=245
Reply from 212.58.224.116: bytes=32 time=19ms TTL=245
Reply from 212.58.224.116: bytes=32 time=19ms TTL=245
Reply from 212.58.224.116: bytes=32 time=26ms TTL=245
Reply from 212.58.224.116: bytes=32 time=22ms TTL=245
Reply from 212.58.224.116: bytes=32 time=21ms TTL=245
Reply from 212.58.224.116: bytes=32 time=20ms TTL=245
Reply from 212.58.224.116: bytes=32 time=19ms TTL=245
Reply from 212.58.224.116: bytes=32 time=21ms TTL=245
Reply from 212.58.224.116: bytes=32 time=20ms TTL=245
Reply from 212.58.224.116: bytes=32 time=22ms TTL=245
Reply from 212.58.224.116: bytes=32 time=24ms TTL=245
Reply from 212.58.224.116: bytes=32 time=28ms TTL=245
Reply from 212.58.224.116: bytes=32 time=20ms TTL=245
Ping statistics for 212.58.224.116:
Packets: Sent = 17, Received = 17, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 19ms, Maximum = 28ms, Average = 21ms
Traceroute to my mailserver
Tracing route to foxtrot.fastwebhosting.net [82.219.38.135]
over a maximum of 30 hops:
1 12 ms 7 ms 8 ms 10.21.208.1
2 9 ms 7 ms 8 ms leed-t2cam1-a-v116.inet.ntl.com [80.0.54.145]
3 8 ms 8 ms * leed-t2core-a-ge-wan63.inet.ntl.com [80.0.241.61
]
4 * 11 ms 11 ms lee-bb-a-so-120-0.inet.ntl.com [62.253.185.17]
5 * * 14 ms pop-bb-b-so-100-0.inet.ntl.com [62.253.185.238]
6 * * 13 ms pop-bb-a-ae0-0.inet.ntl.com [213.105.172.78]
7 25 ms 16 ms * tele-ic-2-so-010-0.inet.ntl.com [62.253.185.86]
8 16 ms * 21 ms ntl-gw.telecomplete.net [213.160.97.41]
9 * * * Request timed out.
10 17 ms 17 ms * exanetworks-gw.telecomplete.net [213.160.121.50]
11 * 18 ms * 7120-2.u3.tcw.uk.l3.ipv4.exa.net.uk [82.219.1.82
]
12 * 15 ms * foxtrot.fastwebhosting.net [82.219.38.135]
13 * 30 ms * foxtrot.fastwebhosting.net [82.219.38.135]
14 * 18 ms 17 ms foxtrot.fastwebhosting.net [82.219.38.135]
Trace complete.
Traceroute to BBC
Tracing route to www.bbc.net.uk (http://www.bbc.net.uk) [212.58.224.121]
over a maximum of 30 hops:
1 8 ms 7 ms 8 ms 10.21.208.1
2 11 ms 10 ms 8 ms leed-t2cam1-a-v116.inet.ntl.com [80.0.54.145]
3 * * 22 ms leed-t2core-a-ge-wan63.inet.ntl.com [80.0.241.61
]
4 * * 8 ms lee-bb-a-so-120-0.inet.ntl.com [62.253.185.17]
5 13 ms * * pop-bb-b-so-100-0.inet.ntl.com [62.253.185.238]
6 * * * Request timed out.
7 15 ms * 35 ms tele-ic-2-so-010-0.inet.ntl.com [62.253.185.86]
8 * 16 ms * ntl-ge2-8.prt0.thdo.bbc.co.uk [212.58.239.217]
9 20 ms 19 ms 19 ms 212.58.238.129
10 19 ms * * www21.thdo.bbc.co.uk [212.58.224.121]
11 * 18 ms 20 ms www21.thdo.bbc.co.uk [212.58.224.121]
Trace complete.
At the time of compiling this (1710) email is still very slow and intermittent. Sometimes Outlook connects and retrieves mail, other times it times out.
If any gurus out there could please look at the above info and see if there's a block in the pipes between Harrogate and Manchester I'd be really grateful!
Cheers
Lima
Since the upgrade to Harrogate touchwood everything has been sailing along nicely but this morning I started getting slow web surfing and email "time outs".
Cured the web surfing by nominating a different cache.
Can't cure the email though! I'm managing to connect to my webhosts (not NTL webspace) mailserver located in Manchester about once in every 3 goes and very slowly. I also can't FTP to my (not NTL) webspace because of the packet loss.
Had a similar thing a month ago and although my webhosting company said the webserver was fine their end they moved me to another web server and all was well again. I suspect the change of IP cured the bad link?
Following the support guidelines here's what I've done today:
Problem started this morning about 10am with slow web and no/slow email retreival via Outlook 2000.
Changed cache which cured web surfing (with no proxy selected just "direct connection to Internet" its slow but with Manc Cache 8 manually specified its speedy again)
Rang webhost. No problems with my webspace server their end. Can ping 100% no packet loss.
Rang NTL support. Spoke to guy in India. He can ping my webserver 100% no packet loss from there but I'm getting up to 50% loss from the other side of the M62 :D No resolution really only "see if it clears".
Running XP via a lynksys router BEFSR41.
Slow email/ packet loss on the one other PC connected to the router as well.
Here are the tests I've done. What is weird is that I get 37% loss on pings to my mailserver and no loss on pings to the BBC site, yet the Traceroute shows packet loss for both.
Retrieving mail for my BT Internet accounts and my 1&1 account is fine. It seems like there's just a block to my webhosting server which is on IP 82.219.38.135
Ping test to my mailserver in Manchester
Pinging 82.219.38.135 with 32 bytes of data:
Request timed out.
Reply from 82.219.38.135: bytes=32 time=16ms TTL=56
Reply from 82.219.38.135: bytes=32 time=20ms TTL=56
Reply from 82.219.38.135: bytes=32 time=18ms TTL=56
Request timed out.
Request timed out.
Request timed out.
Reply from 82.219.38.135: bytes=32 time=16ms TTL=56
Request timed out.
Request timed out.
Reply from 82.219.38.135: bytes=32 time=24ms TTL=56
Reply from 82.219.38.135: bytes=32 time=17ms TTL=56
Reply from 82.219.38.135: bytes=32 time=17ms TTL=56
Reply from 82.219.38.135: bytes=32 time=17ms TTL=56
Reply from 82.219.38.135: bytes=32 time=20ms TTL=56
Reply from 82.219.38.135: bytes=32 time=16ms TTL=56
Request timed out.
Reply from 82.219.38.135: bytes=32 time=16ms TTL=56
Request timed out.
Reply from 82.219.38.135: bytes=32 time=16ms TTL=56
Reply from 82.219.38.135: bytes=32 time=16ms TTL=56
Reply from 82.219.38.135: bytes=32 time=25ms TTL=56
Request timed out.
Request timed out.
Reply from 82.219.38.135: bytes=32 time=16ms TTL=56
Reply from 82.219.38.135: bytes=32 time=17ms TTL=56
Reply from 82.219.38.135: bytes=32 time=17ms TTL=56
Ping statistics for 82.219.38.135:
Packets: Sent = 27, Received = 17, Lost = 10 (37% lo
Approximate round trip times in milli-seconds:
Minimum = 16ms, Maximum = 25ms, Average = 17ms
Ping test to BBC
Pinging www.bbc.net.uk (http://www.bbc.net.uk) [212.58.224.116] with 32 bytes of data:
Reply from 212.58.224.116: bytes=32 time=23ms TTL=245
Reply from 212.58.224.116: bytes=32 time=19ms TTL=245
Reply from 212.58.224.116: bytes=32 time=20ms TTL=245
Reply from 212.58.224.116: bytes=32 time=20ms TTL=245
Reply from 212.58.224.116: bytes=32 time=19ms TTL=245
Reply from 212.58.224.116: bytes=32 time=19ms TTL=245
Reply from 212.58.224.116: bytes=32 time=26ms TTL=245
Reply from 212.58.224.116: bytes=32 time=22ms TTL=245
Reply from 212.58.224.116: bytes=32 time=21ms TTL=245
Reply from 212.58.224.116: bytes=32 time=20ms TTL=245
Reply from 212.58.224.116: bytes=32 time=19ms TTL=245
Reply from 212.58.224.116: bytes=32 time=21ms TTL=245
Reply from 212.58.224.116: bytes=32 time=20ms TTL=245
Reply from 212.58.224.116: bytes=32 time=22ms TTL=245
Reply from 212.58.224.116: bytes=32 time=24ms TTL=245
Reply from 212.58.224.116: bytes=32 time=28ms TTL=245
Reply from 212.58.224.116: bytes=32 time=20ms TTL=245
Ping statistics for 212.58.224.116:
Packets: Sent = 17, Received = 17, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 19ms, Maximum = 28ms, Average = 21ms
Traceroute to my mailserver
Tracing route to foxtrot.fastwebhosting.net [82.219.38.135]
over a maximum of 30 hops:
1 12 ms 7 ms 8 ms 10.21.208.1
2 9 ms 7 ms 8 ms leed-t2cam1-a-v116.inet.ntl.com [80.0.54.145]
3 8 ms 8 ms * leed-t2core-a-ge-wan63.inet.ntl.com [80.0.241.61
]
4 * 11 ms 11 ms lee-bb-a-so-120-0.inet.ntl.com [62.253.185.17]
5 * * 14 ms pop-bb-b-so-100-0.inet.ntl.com [62.253.185.238]
6 * * 13 ms pop-bb-a-ae0-0.inet.ntl.com [213.105.172.78]
7 25 ms 16 ms * tele-ic-2-so-010-0.inet.ntl.com [62.253.185.86]
8 16 ms * 21 ms ntl-gw.telecomplete.net [213.160.97.41]
9 * * * Request timed out.
10 17 ms 17 ms * exanetworks-gw.telecomplete.net [213.160.121.50]
11 * 18 ms * 7120-2.u3.tcw.uk.l3.ipv4.exa.net.uk [82.219.1.82
]
12 * 15 ms * foxtrot.fastwebhosting.net [82.219.38.135]
13 * 30 ms * foxtrot.fastwebhosting.net [82.219.38.135]
14 * 18 ms 17 ms foxtrot.fastwebhosting.net [82.219.38.135]
Trace complete.
Traceroute to BBC
Tracing route to www.bbc.net.uk (http://www.bbc.net.uk) [212.58.224.121]
over a maximum of 30 hops:
1 8 ms 7 ms 8 ms 10.21.208.1
2 11 ms 10 ms 8 ms leed-t2cam1-a-v116.inet.ntl.com [80.0.54.145]
3 * * 22 ms leed-t2core-a-ge-wan63.inet.ntl.com [80.0.241.61
]
4 * * 8 ms lee-bb-a-so-120-0.inet.ntl.com [62.253.185.17]
5 13 ms * * pop-bb-b-so-100-0.inet.ntl.com [62.253.185.238]
6 * * * Request timed out.
7 15 ms * 35 ms tele-ic-2-so-010-0.inet.ntl.com [62.253.185.86]
8 * 16 ms * ntl-ge2-8.prt0.thdo.bbc.co.uk [212.58.239.217]
9 20 ms 19 ms 19 ms 212.58.238.129
10 19 ms * * www21.thdo.bbc.co.uk [212.58.224.121]
11 * 18 ms 20 ms www21.thdo.bbc.co.uk [212.58.224.121]
Trace complete.
At the time of compiling this (1710) email is still very slow and intermittent. Sometimes Outlook connects and retrieves mail, other times it times out.
If any gurus out there could please look at the above info and see if there's a block in the pipes between Harrogate and Manchester I'd be really grateful!
Cheers
Lima