Connection problems lately [Tracert needed]

[Jupitus]

Cerverloc,

that's kinda quirky - the fact that you can connect fine to one but not the other, I mean.

At a time when this is definitely happening, do 2 traceroutes, one to each of the addresses I have given at the start of this thread, then paste the results up here or send them to RightNow with a description of your problem.

 

[krill-nyd]

After a week of no problems, I got what looked like the lag problem back this afternoon. But a tracert doesn't show terrible changes at opentransit (which I got from past tracerts when this problem happened, like most others). I just got lots of requests timed out. Anyone know what this means?

Tracing route to 193.252.123.13 over a maximum of 30 hops

1 1 ms <1 ms 1 ms 192.168.0.1
2 * * * Request timed out.
3 9 ms 48 ms 48 ms gsr01-hw.blueyonder.co.uk [62.30.144.129]
4 27 ms * * 172.18.28.33
5 * 10 ms 11 ms tele2-har-pos.telewest.net [194.117.136.26]
6 12 ms 30 ms * ge51-linx-gw1.cableinet.net [194.117.154.9]
7 * 10 ms 30 ms gigabitethernet4-0-136.metro2-londencyh00.London1.Level3.net [212.187.151.97]
8 11 ms 12 ms 11 ms pos8-0.core2.London1.Level3.net [212.113.0.118]
9 49 ms 54 ms 28 ms P1-0.LONBB1.London.opentransit.net [193.251.240.217]
10 * * 17 ms P13-0.PASCR1.Pastourelle.opentransit.net [193.251.154.225]
11 19 ms 18 ms 20 ms P4-0.BAGCR3.Bagnolet.opentransit.net [193.251.241.118]
12 17 ms 17 ms 56 ms P1-0.BAGBB1.Bagnolet.opentransit.net [193.251.241.145]
13 * * 17 ms P2-0-0.BAGAR1.Bagnolet.opentransit.net [193.251.128.102]
14 * * 19 ms WanadooPortails.GW.opentransit.net [193.251.251.214]
15 20 ms 146 ms * 193.252.123.70
16 20 ms 21 ms 20 ms 193.252.123.13

Trace complete.

 

[Jupitus]

Each '*' entry next to a node represent a timeout (I think) which means this is showing fairly horrible, sporadic timeouts at a number of different nodes between you and the servers:


1 1 ms <1 ms 1 ms 192.168.0.1
2 * * * Request timed out.
3 9 ms 48 ms 48 ms gsr01-hw.blueyonder.co.uk [62.30.144.129]
4 27 ms * * 172.18.28.33 <<<<< Here
5 * 10 ms 11 ms tele2-har-pos.telewest.net [194.117.136.26] <<<<< Here
6 12 ms 30 ms * ge51-linx-gw1.cableinet.net [194.117.154.9] <<<<< Here
7 * 10 ms 30 ms gigabitethernet4-0-136.metro2-londencyh00.London1.Level3.net [212.187.151.97]
8 11 ms 12 ms 11 ms pos8-0.core2.London1.Level3.net [212.113.0.118]
9 49 ms 54 ms 28 ms P1-0.LONBB1.London.opentransit.net [193.251.240.217]
10 * * 17 ms P13-0.PASCR1.Pastourelle.opentransit.net [193.251.154.225] <<<<< Here
11 19 ms 18 ms 20 ms P4-0.BAGCR3.Bagnolet.opentransit.net [193.251.241.118]
12 17 ms 17 ms 56 ms P1-0.BAGBB1.Bagnolet.opentransit.net [193.251.241.145]
13 * * 17 ms P2-0-0.BAGAR1.Bagnolet.opentransit.net [193.251.128.102]
14 * * 19 ms WanadooPortails.GW.opentransit.net [193.251.251.214]
15 20 ms 146 ms * 193.252.123.70
16 20 ms 21 ms 20 ms 193.252.123.13

Looks pretty horrible - talking to your ISP about it might help, but this could just be the start of problems as KPNQwest shut down their network (see Kemor's Friday news )

I hope this helps explain the trace... sorry there is no magical cure for the delays....

 

[Cerverloc]

Same here. I think indeed that this lag is due to KPNQWEST. It started this morning and thats about the time they pulled plugs.

 

[Cerverloc]

I have been experiencing terrible connection problems on Excalibur server since friday. No problems on prywden btw. Here are my tracert files:

Prywden Server

Tracing route to 193.252.123.13 over a maximum of 30 hops



1 19 ms 21 ms 22 ms 195.190.241.103

2 24 ms 26 ms 26 ms 195.190.245.70

3 30 ms 23 ms 26 ms iawxsrt-pbw-bb13a.wxs.nl [195.121.244.2]

4 26 ms 26 ms 28 ms 212.72.45.229

5 29 ms 23 ms 23 ms unknown.Level3.net [213.244.165.65]

6 39 ms 40 ms 39 ms so-1-0-0.mp2.Paris1.Level3.net [212.187.128.34]

7 39 ms 39 ms 38 ms gige6-0.core2.Paris1.Level3.net [212.73.240.46]

8 39 ms 39 ms 38 ms P9-0.BOUBB2.Bourse.opentransit.net [193.251.240.213]

9 37 ms 39 ms 39 ms P2-0.BAGCR2.Bagnolet.opentransit.net [193.251.241.142]

10 40 ms 39 ms 43 ms P10-0.BAGBB2.Bagnolet.opentransit.net [193.251.241.250]

11 39 ms 40 ms 38 ms P12-0-0.BAGAR1.Bagnolet.opentransit.net [193.251.128.118]

12 41 ms 39 ms 39 ms WanadooPortails.GW.opentransit.net [193.251.251.214]

13 40 ms 38 ms 40 ms 193.252.123.70

14 51 ms 42 ms 44 ms 193.252.123.13



Trace complete.

Excalibur Server


Tracing route to 193.252.123.33 over a maximum of 30 hops



1 18 ms 18 ms 24 ms 195.190.241.103

2 24 ms 23 ms 26 ms 195.190.245.70

3 33 ms 42 ms 26 ms iawxsrt-pbw-bb13a.wxs.nl [195.121.244.2]

4 41 ms 26 ms 25 ms 212.72.45.229

5 * 22 ms * unknown.Level3.net [213.244.165.65]

6 * 37 ms 39 ms so-3-0-0.mp1.Paris1.Level3.net [212.187.128.38]

7 38 ms 38 ms 37 ms gige1-0.core2.Paris1.Level3.net [212.73.240.14]

8 170 ms 232 ms 199 ms P9-0.BOUBB2.Bourse.opentransit.net [193.251.240.213]

9 39 ms 46 ms 42 ms P2-0.BAGCR2.Bagnolet.opentransit.net [193.251.241.142]

10 40 ms 39 ms 39 ms P10-0.BAGBB2.Bagnolet.opentransit.net [193.251.241.250]

11 40 ms 39 ms 38 ms P12-0-0.BAGAR1.Bagnolet.opentransit.net [193.251.128.118]

12 * 40 ms 39 ms WanadooPortails.GW.opentransit.net [193.251.251.214]

13 41 ms 41 ms 40 ms 193.252.123.70

14 49 ms 42 ms 42 ms 193.252.123.33



Trace complete.

As you can see disturbing timeouts when connecting to Excalibur server making it unplayable.

 

[old.Tzeentch]

Originally posted by Cerverloc


Prywden Server

Tracing route to 193.252.123.13 over a maximum of 30 hops



1 19 ms 21 ms 22 ms 195.190.241.103

2 24 ms 26 ms 26 ms 195.190.245.70

3 30 ms 23 ms 26 ms iawxsrt-pbw-bb13a.wxs.nl [195.121.244.2]

4 26 ms 26 ms 28 ms 212.72.45.229

5 29 ms 23 ms 23 ms unknown.Level3.net [213.244.165.65]

6 39 ms 40 ms 39 ms so-1-0-0.mp2.Paris1.Level3.net [212.187.128.34]

7 39 ms 39 ms 38 ms gige6-0.core2.Paris1.Level3.net [212.73.240.46]

8 39 ms 39 ms 38 ms P9-0.BOUBB2.Bourse.opentransit.net [193.251.240.213]

9 37 ms 39 ms 39 ms P2-0.BAGCR2.Bagnolet.opentransit.net [193.251.241.142]

10 40 ms 39 ms 43 ms P10-0.BAGBB2.Bagnolet.opentransit.net [193.251.241.250]

11 39 ms 40 ms 38 ms P12-0-0.BAGAR1.Bagnolet.opentransit.net [193.251.128.118]

12 41 ms 39 ms 39 ms WanadooPortails.GW.opentransit.net [193.251.251.214]

13 40 ms 38 ms 40 ms 193.252.123.70

14 51 ms 42 ms 44 ms 193.252.123.13



Trace complete.

Excalibur Server


Tracing route to 193.252.123.33 over a maximum of 30 hops



1 18 ms 18 ms 24 ms 195.190.241.103

2 24 ms 23 ms 26 ms 195.190.245.70

3 33 ms 42 ms 26 ms iawxsrt-pbw-bb13a.wxs.nl [195.121.244.2]

4 41 ms 26 ms 25 ms 212.72.45.229

5 * 22 ms * unknown.Level3.net [213.244.165.65] ----- Strange... might be random though

6 * 37 ms 39 ms so-3-0-0.mp1.Paris1.Level3.net [212.187.128.38]

7 38 ms 38 ms 37 ms gige1-0.core2.Paris1.Level3.net [212.73.240.14]

8 170 ms 232 ms 199 ms P9-0.BOUBB2.Bourse.opentransit.net [193.251.240.213] <====== Something definitely screwy here...

9 39 ms 46 ms 42 ms P2-0.BAGCR2.Bagnolet.opentransit.net [193.251.241.142]

10 40 ms 39 ms 39 ms P10-0.BAGBB2.Bagnolet.opentransit.net [193.251.241.250]

11 40 ms 39 ms 38 ms P12-0-0.BAGAR1.Bagnolet.opentransit.net [193.251.128.118]

12 * 40 ms 39 ms WanadooPortails.GW.opentransit.net [193.251.251.214]

13 41 ms 41 ms 40 ms 193.252.123.70

14 49 ms 42 ms 42 ms 193.252.123.33



Trace complete.

As you can see disturbing timeouts when connecting to Excalibur server making it unplayable.

Made 2 comments on your trace to Exc.

I don't see any of the timeouts you mentioned.

The GOA network seems to be responding fine.

 

[Cerverloc]

You see those * in the excal trace. These * are timeouts. Compare with the first trace (prywden) you won't find any *. I have traced for 3 days now and the results are still the same. *(timeouts/ no response whatever you wanna call it) on Excalibur and healthy connection on Prywden.

* 40 ms 39 ms WanadooPortails.GW.opentransit.net [193.251.251.214] <=== you forgot one

 

[Jupitus]

Mmmmm strange, and getting to the limits of my knowledge, but what I can see is that your route is different to Excal from the route to Prydwen... notice the change in address within the level3 network at hop number 6? For some reason your connection is routing through different nodes in level3's network and I would certainly assume that this is where your problem lies. Perhaps try talking to your ISP and sending them this information to see if they can route both through the same nodes as the Prydwen route - not sure if they will be able to, of course, but good luck

 

[Cerverloc]

I don't think my ISP can do anything about it. Perhaps because of the KPNQWEST deal they needed to reroute certain stuff. Kemor already explained something about those routers and he is obviously aware of the fact that this problem exists. I hope there comes a solution soon because I just want to enjoy the game.

 

[Cerverloc]

I just received a message from Rightnow tech support:

Discussion Thread
---------------------------------------------------------------
Response (CS) - 07/15/2002 10:02 AM
Hello,

We are aware of the lag issue and are currently working on fixing it. Sorry for the inconvenience.

So guess its sit down relax and hope for the best time.

 

[SFXman]

Here is one that has no problems. I have a connection like this 99.9% of the time really...

Tracing route to 193.252.123.13 over a maximum of 30 hops



1 Bah, I'll leave the first one out.

2 27 ms 26 ms 79 ms rnal-08-GE-1-0-0-28.soon.fi [212.63.11.49]

3 20 ms 20 ms 19 ms 212.246.46.36

4 24 ms 26 ms 24 ms 139.97.3.217

5 24 ms 27 ms 25 ms 197-POS4-0-195.lanlink.datatie.net [139.97.2.133]

6 24 ms 22 ms 22 ms 198-GE3-0-197.lanlink.datatie.net [139.97.2.150]

7 30 ms 30 ms 21 ms msfc-pa2-ge-3-1.hel.kolumbus.net [193.229.1.249]

8 22 ms 29 ms 22 ms core-ka-v201.hel.kolumbus.net [193.229.255.34]

9 57 ms 47 ms 21 ms m10-ka-ge0-1.hel.kolumbus.net [193.229.255.99]

10 29 ms 31 ms 30 ms s-b4-pos0-3.telia.net [213.248.67.81]

11 36 ms 29 ms 33 ms s-bb1-pos0-3-0.telia.net [213.248.66.5]

12 29 ms 36 ms 39 ms s-b3-pos5-0.telia.net [213.248.66.2]

13 70 ms 70 ms 68 ms france-telecom-s.telia.net [213.248.67.126]

14 69 ms 72 ms 78 ms P10-0.STHBB1.Stockholm.opentransit.net [193.251.240.113]

15 71 ms 75 ms 77 ms P10-0.COPBB1.Copenhagen.opentransit.net [193.251.240.153]

16 73 ms 70 ms 78 ms P0-0.COPBB2.Copenhagen.opentransit.net [193.251.240.82]

17 69 ms 72 ms 87 ms P3-0.FFTBB1.Frankfurt.opentransit.net [193.251.242.45]

18 89 ms 78 ms 69 ms P6-0.FFTBB2.Frankfurt.opentransit.net [193.251.154.233]

19 73 ms 72 ms 71 ms P2-0.BAGCR1.Bagnolet.opentransit.net [193.251.154.209]

20 76 ms 69 ms 70 ms P3-0.BAGCR3.Bagnolet.opentransit.net [193.251.241.110]

21 72 ms 70 ms 70 ms P1-0.BAGBB1.Bagnolet.opentransit.net [193.251.241.145]

22 71 ms 71 ms 72 ms WanadooPortails1.GW.opentransit.net [193.251.251.58]

23 72 ms 83 ms 82 ms 193.252.122.10

24 73 ms 74 ms 75 ms 193.252.123.13



Trace complete.

 

[ImLestat]

This is an old thread, and has nothing to do with the current problems. Please let it die..

 

[Keri]

People .. please stop and think a minute before just getting angry at GOA/Wanadoo.

I have a possible cause for the problem, which no one else has mentioned:

This morning, I received an e-mail containing the new W32.Bugbear worm. This worm was delivered to me from a website. This website (or the server on which it is hosted) probably contains thousands of e-mail addresses. Now .. multiply this website by the thousands of others that are probably also infected, and multiply them by the thousands of e-mail addresses they contain .. and what do you have?????

You have one hell of a lot of extra traffic getting stuck in any existing bottlenecks. Now .. could this possibly be the reason why there is incredible lag, and also an unusually high number of l/ds? I think it is definitely a possibility. Some ISPs have shut down their mail servers ... I know for a fact that the major national high speed ISP here in Canada has done exactly that.

Give GOA a break ... they are obviously doing all they can to investigate and fix the problem.

And .. for those of you who don't read everything on the DAoC site, this weekend was supposed to be a weekend off for DAoC staff.

 

[ImLestat]

Still, you didn't read my post above yours. This is an old thread, and has nothing to do with the current problems.