Advertisement
If you have a new account but are having problems posting or verifying your account, please email us on hello@boards.ie for help. Thanks :)
Hello all! Please ensure that you are posting a new thread or question in the appropriate forum. The Feedback forum is overwhelmed with questions that are having to be moved elsewhere. If you need help to verify your account contact hello@boards.ie
NTL Problem!
Comments
-
-
-
-
-
-
Advertisement
-
-
Same crap here for the last few days. I've been on NTL here in Tallaght for over 2 years (probably closer to 3) and it's never been this bad.
The best ping I can get to game server is now around 200ms. Before I was getting as low as 40ms on some.
I've spent 13 hours in work fixing a Lotus Notes Server problem and just wanted to pla some Day of Defeat
*sigh*
Again there's no problems with this PC and spyware or viruses. There's no problems with my router. There's no problems with my network cards.
The problem is with NTL.
0 -
-
ntlbell wrote:Yesterday at 8.30ish when my pings were at their worst.
Thats strange because NTL Ireland users go through the gfd-bb-b-so-500-0.inet.ntl.com[213.105.172.130] server.
Why do the NTL UK users not have the same problem going through that server aswell ??
0 -
I've been told today by NTL that the problem was fixed yesterday morning, but as of last night I have seen no improvement.
If anyone could forward a tracert from last night to NTL it may help.
so what happenens now, when they say that they have done all they can do..........apart from changing s.p. of course 0 -
Advertisement
-
-
-
If it was two different interfaces i could have a guess at why, but as it's the same I can't think of anything except "prioritising"MickFarr wrote:Thats strange because NTL Ireland users go through the gfd-bb-b-so-500-0.inet.ntl.com[213.105.172.130] server.
Why do the NTL UK users not have the same problem going through that server aswell ??
now it wouldn't suprise me if ntl do this, it would suprise me even less that someone tried to do it and make a complete arse of it.
the story back from ntl this morning was the work last night didn't fix it. no **** charlie. and more work was carried out, cards changed etc.
so we wait another night
WAN NTL0 -
joe monkey won't give two ****s if you pay your bill or not.Lenny wrote:Lads, have any of you lot rang them up and told them your not paying your BB bill this month?
I ain't ranged them and told them that it hasn't been great
but would be tempted to to see their responce,..
and you'll more than an isp problem when your tv is cut off
0 -
-
-
-
-
-
-
Advertisement
-
-
-
-
-
-
credit were credits due
Tracing route to clarity.jolt.co.uk [195.149.21.11]
over a maximum of 30 hops:
1 7 ms 9 ms 10 ms 10.135.55.254
2 7 ms 7 ms 8 ms host82-9-146-9.not-set-yet.ntli.net
3 11 ms 7 ms 7 ms dub-core-a-pos1100.inet.ntl.com
4 16 ms 16 ms 18 ms man-bb-a-atm010-228.inet.ntl.com
5 39 ms 23 ms 41 ms man-bb-b-ae0-0.inet.ntl.com [62.253.187.178]
6 22 ms 33 ms 52 ms win-bb-a-so-300-0.inet.ntl.com
7 23 ms 24 ms 32 ms gfd-bb-b-so-500-0.inet.ntl.com
8 27 ms 30 ms 27 ms tele-ic-2-so-100-0.inet.ntl.com
9 45 ms 67 ms 41 ms lon1-10.nildram.net [213.208.106.169]
10 23 ms 30 ms 24 ms lon1-9.nildram.net [195.149.20.130]
11 23 ms 27 ms 38 ms jolt-gw.nildram.net [195.149.20.126]
12 23 ms 36 ms 27 ms clarity.jolt.co.uk [195.149.21.11]
Pinging 195.149.21.11 with 32 bytes of data:
Reply from 195.149.21.11: bytes=32 time=32ms TTL=53
Reply from 195.149.21.11: bytes=32 time=62ms TTL=53
Reply from 195.149.21.11: bytes=32 time=22ms TTL=53
Reply from 195.149.21.11: bytes=32 time=25ms TTL=53
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 22ms, Maximum = 62ms, Average = 35ms
0 -
C:\>tracert [url]www.jolt.co.uk[/url] Tracing route to clarity.jolt.co.uk [195.149.21.11] over a maximum of 30 hops: 1 8 ms 11 ms 12 ms 10.135.63.254 2 14 ms 7 ms 14 ms host82-9-146-9.not-set-yet.ntli.net [82.9.146.9] 3 8 ms 8 ms 11 ms dub-core-a-pos1100.inet.ntl.com [62.254.96.137] 4 48 ms 15 ms 35 ms man-bb-a-atm010-230.inet.ntl.com [62.253.188.78] 5 23 ms 16 ms 20 ms man-bb-b-ae0-0.inet.ntl.com [62.253.187.178] 6 27 ms 30 ms 25 ms win-bb-a-so-300-0.inet.ntl.com [62.253.185.138] 7 54 ms 26 ms 26 ms gfd-bb-b-so-500-0.inet.ntl.com [213.105.172.130] 8 35 ms 23 ms 31 ms tele-ic-2-so-100-0.inet.ntl.com [62.253.185.74] 9 25 ms 30 ms 27 ms lon1-10.nildram.net [213.208.106.169] 10 26 ms 27 ms 26 ms lon1-9.nildram.net [195.149.20.130] 11 38 ms 31 ms 58 ms jolt-gw.nildram.net [195.149.20.126] 12 76 ms 25 ms 25 ms clarity.jolt.co.uk [195.149.21.11] Trace complete. C:\>ping [url]www.joly.co.uk[/url] Pinging bed.uk.clara.net [195.8.71.207] with 32 bytes of data: Reply from 195.8.71.207: bytes=32 time=35ms TTL=44 Reply from 195.8.71.207: bytes=32 time=36ms TTL=44 Reply from 195.8.71.207: bytes=32 time=37ms TTL=44 Reply from 195.8.71.207: bytes=32 time=36ms TTL=44 Ping statistics for 195.8.71.207: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 35ms, Maximum = 37ms, Average = 36ms
Taken just now, WHILE Socom2 is being played over the connection, needless to say I am smiling at the moment!
[Edit] Heh, needless to say, the ping isn't to jolt.co.uk... LOL Damn stupid brain! Averaging 24ms to jolt (with Ps2 gaming over same connection at same time). 0 -
-
-
Advertisement
-
Yeah !! At last!!!
C:\Documents and Settings\Michael Farrell>tracert www.jolt.co.uk
Tracing route to clarity.jolt.co.uk [195.149.21.11]
over a maximum of 30 hops:
1 8 ms 9 ms 7 ms 10.135.31.254
2 7 ms 8 ms 8 ms host82-9-146-5.not-set-yet.ntli.net [82.9.146.5]
3 8 ms 34 ms 10 ms dub-core-a-pos1100.inet.ntl.com [62.254.96.137]
4 17 ms 23 ms 16 ms man-bb-a-atm010-228.inet.ntl.com [62.253.187.122]
5 80 ms 25 ms 21 ms man-bb-b-ae0-0.inet.ntl.com [62.253.187.178]
6 23 ms 75 ms 22 ms win-bb-a-so-300-0.inet.ntl.com [62.253.185.138]
7 26 ms 24 ms 23 ms gfd-bb-b-so-500-0.inet.ntl.com [213.105.172.130]
8 35 ms 27 ms 28 ms tele-ic-2-so-100-0.inet.ntl.com [62.253.185.74]
9 22 ms 23 ms 30 ms lon1-10.nildram.net [213.208.106.169]
10 25 ms 24 ms 24 ms lon1-9.nildram.net [195.149.20.130]
11 62 ms 26 ms 24 ms jolt-gw.nildram.net [195.149.20.126]
12 23 ms 26 ms 23 ms clarity.jolt.co.uk [195.149.21.11]
Trace complete.
C:\Documents and Settings\Michael Farrell>ping www.jolt.co.uk
Pinging clarity.jolt.co.uk [195.149.21.11] with 32 bytes of data:
Reply from 195.149.21.11: bytes=32 time=29ms TTL=53
Reply from 195.149.21.11: bytes=32 time=26ms TTL=53
Reply from 195.149.21.11: bytes=32 time=27ms TTL=53
Reply from 195.149.21.11: bytes=32 time=24ms TTL=53
Ping statistics for 195.149.21.11:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 24ms, Maximum = 29ms, Average = 26ms
C:\Documents and Settings\Michael Farrell>
Now for some good online gaming without the lag 0
Advertisement