Anyone else getting network grief?

OldBloke · March 16, 2004, 08:09:01 AM

QuoteOriginally posted by DarkAngel@Mar 15 2004, 11:11 PM
Think we may be having the same problem down here i thought about phoning in but no need as im moving. Oldie didnt you say you had some problems as well?

Yep. ntl forum's are full of disgruntled bods. :angry:

Stryker · March 16, 2004, 10:29:26 AM

I think there may be issues with one of Crosswired's upstreams upstream... erm if you get my drift.

Rest assured I'm looking into it :ph34r:

DarkAngel · March 16, 2004, 01:54:15 PM

QuoteYep. ntl forum's are full of disgruntled bods.

Gonna see if its any better here at my sisters as started move today think they got 128 see if i can play online with it

. Anyone know much about wireless cable supposed to be getting 1mb wireless dish connection in new house when we move in <_< then better once the place upgrades. Wondered if any1 has it or used it?

Sn00ks · March 16, 2004, 06:29:05 PM

You know I said that my ping problems had been resolved, well, they're back again

and it's the same router again!

C:\>tracert 193.110.88.20

Tracing route to homer.deadmen.co.uk [193.110.88.20]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 18 ms 18 ms 18 ms btdhg522-hg2.ealing.broadband.bt.net [217.47.135
.201]
3 19 ms 18 ms 20 ms 217.47.135.161
4 19 ms 20 ms 21 ms 217.47.135.238
5 20 ms 19 ms 22 ms inh3cs02-500.imsnet3.btopenworld.com [213.1.119.
62]
6 256 ms 260 ms 257 ms btfl02-gig7-7.imsnet3.btopenworld.com [213.1.119
.149]
7 251 ms 251 ms 272 ms core1-pos4-3.ealing.ukcore.bt.net [194.72.9.241]

8 274 ms 277 ms 273 ms core1-pos10-0.redbus.ukcore.bt.net [194.74.65.25
4]
9 274 ms 280 ms 276 ms linx2.telecomplete.net [195.66.226.139]
10 279 ms 282 ms 272 ms r1.tcw.telecomplete.net [193.0.255.230]
11 336 ms 281 ms 265 ms netserve-gw.cust.telecomplete.net [213.160.121.2
6]
12 257 ms 258 ms 256 ms homer.deadmen.co.uk [193.110.88.20]

Trace complete.

Oh well back to BT to find out what they're going to do about it. :angry:

suicidal_monkey · March 16, 2004, 06:56:22 PM

I got ADSL via virgin.net but I can see a few ntl boxes in that there there trace! :help:

Tracing route to homer.deadmen.co.uk [193.110.88.20]
over a maximum of 30 hops:

1 17 ms 17 ms 16 ms glfd-bam-1.inet.ntl.com [194.145.148.4]
2 17 ms 16 ms 17 ms gfd-t2core-b-ge-wan63.inet.ntl.com [62.254.207.173]
3 16 ms 18 ms 17 ms gfd-bb-b-so-300-0.inet.ntl.com [62.253.185.29]
4 20 ms 18 ms 18 ms tele-ic-2-so-100-0.inet.ntl.com [62.253.185.74]
5 19 ms 18 ms 18 ms ntl-gw.telecomplete.net [213.160.97.41]
6 29 ms 27 ms 27 ms r1.tcw.telecomplete.net [193.0.255.230]
7 29 ms 28 ms 29 ms netserve-gw.cust.telecomplete.net [213.160.121.26]
8 30 ms 29 ms 28 ms homer.deadmen.co.uk [193.110.88.20]

Trace complete.

Stryker · March 17, 2004, 09:57:11 AM

QuoteOriginally posted by Sn00ks@Mar 16 2004, 06:29 PM
You know I said that my ping problems had been resolved, well, they're back again and it's the same router again!

C:\>tracert 193.110.88.20

Tracing route to homer.deadmen.co.uk [193.110.88.20]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 18 ms 18 ms 18 ms btdhg522-hg2.ealing.broadband.bt.net [217.47.135
.201]
3 19 ms 18 ms 20 ms 217.47.135.161
4 19 ms 20 ms 21 ms 217.47.135.238
5 20 ms 19 ms 22 ms inh3cs02-500.imsnet3.btopenworld.com [213.1.119.
62]
6 256 ms 260 ms 257 ms btfl02-gig7-7.imsnet3.btopenworld.com [213.1.119
.149]
7 251 ms 251 ms 272 ms core1-pos4-3.ealing.ukcore.bt.net [194.72.9.241]

8 274 ms 277 ms 273 ms core1-pos10-0.redbus.ukcore.bt.net [194.74.65.25
4]
9 274 ms 280 ms 276 ms linx2.telecomplete.net [195.66.226.139]
10 279 ms 282 ms 272 ms r1.tcw.telecomplete.net [193.0.255.230]
11 336 ms 281 ms 265 ms netserve-gw.cust.telecomplete.net [213.160.121.2
6]
12 257 ms 258 ms 256 ms homer.deadmen.co.uk [193.110.88.20]

Trace complete.

Oh well back to BT to find out what they're going to do about it. :angry:

Snooks, your problem is quite clearly with BT, get on the phone to them!

Gh0st Face Killah · March 17, 2004, 10:11:16 AM

Who do you work for again Sn00ks?

TeaLeaf · March 17, 2004, 04:35:06 PM

Strange :unsure:

On ISDN via Fast24 r1.tcw.telecomplete.net [193.0.255.230]
was giving me grief last night. I tracked it through on PingPlotter. But in the post above it seems clear

TL.

Anonymous · March 17, 2004, 04:51:03 PM

QuoteOriginally posted by TeaLeaf@Mar 17 2004, 04:35 PM
Strange :unsure:

On ISDN via Fast24 r1.tcw.telecomplete.net [193.0.255.230]
was giving me grief last night. I tracked it through on PingPlotter. But in the post above it seems clear

TL.

Clear? I wouldn't call

Quote10 279 ms 282 ms 272 ms r1.tcw.telecomplete.net [193.0.255.230]

particularly clear or were you getting seriously nutty mad mental horrible grief?

TeaLeaf · March 17, 2004, 05:31:59 PM

Nope, I was looking at suicidal_monkey's post.

Quote29 ms 27 ms 27 ms r1.tcw.telecomplete.net

I hadn't noticed Snooks, but it looks like the big nasty for him starts well before r1.tcw.telecomplete.net

I'll have a go at my ISP too though

TL.

Grimnar · March 17, 2004, 06:04:46 PM

Microsoft Windows XP [versie 5.1.2600]
© Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Dhr. Klok>cd \
C:\>tracert 193.110.88.20
Bezig met het traceren van de route naar homer.deadmen.co.uk [193.110.88.20]
via maximaal 30 hops:
1 2 ms 1 ms 1 ms SpeedTouch.lan [10.0.0.138]
2 12 ms 11 ms 10 ms 195.190.241.248
3 27 ms 17 ms 25 ms iawxsrt-pbw-bb13a.wxs.nl [195.121.255.193]
4 16 ms 16 ms 16 ms iawxsrt-m6-bb14a.wxs.nl [195.121.0.149]
5 28 ms 26 ms 27 ms amsix1.telecomplete.net [195.69.144.178]
6 36 ms 36 ms 35 ms r1.tcw.telecomplete.net [193.0.255.230]
7 36 ms 36 ms 36 ms netserve-gw.cust.telecomplete.net [213.160.121.26]
8 37 ms 36 ms 37 ms homer.deadmen.co.uk [193.110.88.20]
De trace is voltooid.

Stryker · March 22, 2004, 10:49:22 AM

It is very rate we have an issue via telecomplete. Also the crosswired router that peers with that upstream is due an upgrade.... watch out in the server issues forum.