Packet loss HG5 Harrogate to Manchester server

lima · 26-07-2005, 16: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

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 [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 [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

Ignition · 26-07-2005, 16:23

Usual thing, fault between Leeds PoP and Leeds Seacroft.

Not a fat lot I can do about it probably needs some fibre cleaning work or a new card between Leeds North and Leeds Seacroft sites.

As no-one has actually bothered to look into the ongoing probs here I'm a bit powerless.

lima · 26-07-2005, 17:22

Hi Ignition

Thanks for the quick reply m8

Would be good to be able to send the tracroute text to someone at NTL? as I can see calls to the support desk aren't likely to resolve this without some supporting evidence.

Any ideas who to send to?

Cheers

Lima

lima · 27-07-2005, 08:37

Update:

Spoke to a helpful chap at support this morning and mailed over some traceroutes. He is escalating to the server support network people as like Ignition says, there is a problem somewhere between leaving HG and getting to Leeds.

Will keep the thread updated.

Lima

KevAmiga · 27-07-2005, 08:43

Sure did

Ill keep you posted.

Kev

ollie79 · 27-07-2005, 14:31

Hi Lima et al,

Im based in Headingley with NTL 1meg and am getting this same problem (from what I can tell) as of yesterday/day before and my search for solutions has led me here. When connecting to an online game server in Edinburgh (via the South I presume), only about 1 in 4 moves make it from me to the server side. Its pretty much crippled the game which is all I use the PC for.

I know jack all when it comes to net terminology so if anyone can advise me how I can sort it I'd be well grateful! Although Im guessing all I can do is sit pretty and watch this thread(?).

Cheers in advance

Ollie

KevAmiga · 27-07-2005, 14:57

if you know the server address and how to trace route, post one up and someone will be able to help you...

sam2656 · 27-07-2005, 15:43

Hi folks, i'm from Roundhay, Leeds and aslo having problems since yesterday. Constant lag/disconnects makes the game unplayable

I'm trying to connect to a server based in france(http://daoc.goa.com/en/)

traceroute #1 to Excalibur

Tracing route to 193.252.123.33 over a maximum of 30 hops
1 1 ms 1 ms 1 ms 192.168.2.1
2 11 ms 19 ms 10 ms 10.76.144.1
3 13 ms 11 ms 20 ms leed-t2cam1-a-ge911.inet.ntl.com [80.0.54.25]
4 * 12 ms 11 ms leed-t2core-a-ge-wan63.inet.ntl.com [80.0.241.61
]
5 * 9 ms 16 ms lee-bb-a-so-120-0.inet.ntl.com [62.253.185.17]
6 14 ms 39 ms 16 ms nth-bb-b-so-000-0.inet.ntl.com [62.253.185.101]
7 * 68 ms * nth-bb-a-ae0-0.inet.ntl.com [62.253.185.117]
8 17 ms * 17 ms so-5-0-0-0.loncr2.london.opentransit.net [193.25
1.254.141]
9 * 17 ms 18 ms po2-0.loncr3.london.opentransit.net [193.251.242
.21]
10 27 ms 28 ms * po7-0.pascr3.paris.opentransit.net [193.251.242.
17]
11 26 ms * * po9-0.pascr1.paris.opentransit.net [193.251.129.
61]
12 27 ms 27 ms * wanadooportails-1.gw.opentransit.net [193.251.25
1.54]
13 * * * Request timed out.
14 * 42 ms 27 ms 193.252.123.33

traceroute #2 to Excalibur

Tracing route to 193.252.123.33 over a maximum of 30 hops
1 2 ms 1 ms 1 ms 192.168.2.1
2 31 ms 19 ms 11 ms 10.76.144.1
3 12 ms 11 ms 11 ms leed-t2cam1-a-ge911.inet.ntl.com [80.0.54.25]
4 11 ms * * leed-t2core-a-ge-wan63.inet.ntl.com [80.0.241.61
]
5 * 22 ms 11 ms lee-bb-a-so-120-0.inet.ntl.com [62.253.185.17]
6 17 ms * * nth-bb-b-so-000-0.inet.ntl.com [62.253.185.101]
7 * 16 ms * nth-bb-a-ae0-0.inet.ntl.com [62.253.185.117]
8 28 ms 16 ms * so-5-0-0-0.loncr2.london.opentransit.net [193.25
1.254.141]
9 27 ms 17 ms * po2-0.loncr3.london.opentransit.net [193.251.242
.21]
10 * 27 ms 48 ms po7-0.pascr3.paris.opentransit.net [193.251.242.
17]
11 * * * Request timed out.
12 24 ms 26 ms 24 ms wanadooportails-1.gw.opentransit.net [193.251.25
1.54]
13 30 ms 25 ms * 193.252.122.14
14 * 28 ms * 193.252.123.33
15 * * * Request timed out.
16 27 ms * * 193.252.123.33
17 37 ms * 37 ms 193.252.123.33

A traceroute to Excaliburs sister server, Prydwen shows no problems

traceroute #1 to Prydwen

Tracing route to 193.252.123.177 over a maximum of 30 hops
1 1 ms 1 ms 1 ms 192.168.2.1
2 12 ms 12 ms 10 ms 10.76.144.1
3 11 ms 9 ms 28 ms leed-t2cam1-b-ge911.inet.ntl.com [80.0.55.25]
4 12 ms 12 ms 16 ms leed-t2core-b-ge-wan62.inet.ntl.com [80.0.241.18
5]
5 21 ms 13 ms 64 ms lee-bb-b-so-120-0.inet.ntl.com [62.253.185.21]
6 14 ms 15 ms 13 ms man-bb-a-so-700-0.inet.ntl.com [62.253.185.193]
7 12 ms 60 ms 14 ms man-bb-b-ae0-0.inet.ntl.com [62.253.187.178]
8 11 ms 14 ms 11 ms po6-0.mctbb1.manchester.opentransit.net [193.251
.250.105]
9 22 ms 28 ms 20 ms po10-0.brsbb1.bristol.opentransit.net [193.251.2
42.133]
10 48 ms 28 ms 31 ms po4-0.auvbb1.aubervilliers.opentransit.net [193.
251.243.238]
11 35 ms 29 ms 38 ms po11-0.auvcr1.aubervilliers.opentransit.net [193
.251.243.161]
12 37 ms 31 ms 29 ms po1-0.pascr1.paris.opentransit.net [193.251.243.
30]
13 32 ms 37 ms 28 ms wanadooportails-1.gw.opentransit.net [193.251.25
1.54]
14 46 ms 31 ms 45 ms 193.252.122.14
15 31 ms 31 ms 31 ms 193.252.123.177
Trace complete.

Sam

KevAmiga · 27-07-2005, 16:04

Definatly an NTL routing issue, look at the 2 traces.

Trace 1 goes via :

leed-t2core-a-ge-wan63.inet.ntl.com

on hop 4, giving issues.

Trace 2 goes via :

leed-t2core-b-ge-wan62.inet.ntl.com

On hop 4 with no problems .... ill see about getting this escalated to the right people for you.

Kev

ollie79 · 27-07-2005, 18:10

Hi Kev, thanks for the reply. Im located pretty much in the middle of the other areas mentioned in this thread, but assuming that doesnt mean my problem will be fixed when theirs is, I'll work out how to trace a route

KevAmiga · 27-07-2005, 18:20

Hi ollie / all

This is now an official NTL fault. I will keep you updated on any updates.

Thanks for the trace submissions
__________________

@ ollie, to trace (on a windows PC)...

Click Start > Run

Type command

In DOS box type

tracert (servernamehere)

ie : tracert www.ntlworld.com

Press Enter

Should trace OK.

ollie79 · 27-07-2005, 18:28

Thanks Kev - not sure how to clipboard the DOS text so here's a dump (so to speak!)

Ignition · 27-07-2005, 18:30

Was an official fault just over an hour ago, and fixed 40 mins ago

KevAmiga · 27-07-2005, 18:39

Excellent...

__________________

Ollie, you still having problems?

ollie79 · 27-07-2005, 19:29

Nope - back up to speed like magic

Thanks for the help. Much appreciated