Connection problems lately [Tracert needed]

[kemor]

Connection problems lately [Tracert needed] Updated

UPDATE
Now, i need traceroutes from players who do NOT have problems while their friends are dropping like flies all around the realms.
Same procedure, with just a different subject : [CLEAN TRACERT]

Thanks.

Some things i wanted to clear about the connection problems lately:
1) This is not server related at all. Since patch, we noticed only 2 server crashes, Avalon (rebooted automatically around 11pm CET on Sunday) and Ys (crashed due a problem in the translation files on Sunday morning around 9am CET).
2) After contacting Opentransit (our ISP), we got the confirmation that there was nothing wrong on their side lately. However, many ISPs companies, big and small, are closing their doors all over Europe lately and this is causing some chaos in the European Internet platform overall.


That said, we want to push the investigation even further, but for that, we need you.

I’m sure someone will explain how and where to get a “tracert” to our servers, so I’ll skip that part. What I need for now is a “tracert” to the server you play on, during a period of trouble (disconnection, packet loss, etc).
Save it in an easy format (text file or screenshot) and send it to kemor@goa.com with [TRACERT] as header.

You will NOT get an answer from me; I’ll just grab all those tracerts and will give them to the admin guys.

Thanks.


Ps: Thank you to the one of you who will post how to do tracert and how to use them, I’m sure lots of you got way more technical skills than I to do this

 

[Jupitus]

Producing a traceroute

To make a trace, you need to start a Command (or DOS) prompt first. Most systems will let you do this by selecting 'Start', 'Run' and entering "cmd" before hitting ok.

type

cd c:\ <return>

and you should just have a 'c:\>' prompt in the DOS window. Next, type

tracert 193.252.123.13 > mytrace.txt <RETURN>

and the traceroute will log the responses over the network in a file called 'mytrace.txt' which will be in the main C drive folder on your system. This is the file you should attach to your email to Kemor.

The command given above uses the address for the Prydwen server. If you play on Excalibur, please type:

tracert 193.252.123.33 > mytrace.txt <RETURN>

instead.

It is important to do this quickly if you go l/d, as the problems do seem to come and go quite suddenley. I suggest having this window up before you even play DAoC with the command ready to go as you exit the game leaving your character flailing madly at pygmy goblins Test it first by simply typing:

tracert 193.252.123.13 <RETURN>

which should display the full trace in the DOS window.

Cheers,
Jup.

 

[oldnick]

<<< Noob


whats the IP's?

Nick

 

[Jupitus]

Re: Producing a traceroute

Originally posted by Jupitus

tracert 193.252.123.13 > mytrace.txt <RETURN>

The command given above uses the address for the Prydwen server. If you play on Excalibur, please type:

tracert 193.252.123.33 > mytrace.txt <RETURN>

IP addresses are the ones I have given .....

 

[old.cutgrass]

For people who don't want to use Dos prompts go to the following url:

http://www.netsys.com/tools.html

Select Traceroute from the left hand side, put the IP address in (from above mail) and hit enter.

Make sure you dont include spaces at the end of the IP or you will get errors.

Then just cut and paste the results into an email.

 

[oldnick]

Re: Re: Producing a traceroute

Originally posted by Jupitus



IP addresses are the ones I have given .....

oops me bad

Thanks

nick

 

[Flimgoblin]

That'll give you a traceroute from the netsys server... and not your home machine... which for me was a ping of 86 ms...

from home machine on 'tracert' it was 1451ms

 

[old.Soldier]

Nice

2 16 ms 9 ms 12 ms gsr01-wv.blueyonder.co.uk [62.31.176.33]

3 15 ms 15 ms 16 ms kno-rab-wol-pos.telewest.net [194.117.136.49]

4 20 ms 21 ms 17 ms tele2-kno-rab-pos.telewest.net [194.117.136.70]

5 17 ms 18 ms 17 ms ge51-linx-gw1.cableinet.net [194.117.154.9]

6 21 ms 22 ms 15 ms 195.50.116.173

7 19 ms 17 ms 20 ms pos8-0.core2.London1.Level3.net [212.113.0.118]

8 19 ms 23 ms 19 ms P1-0.LONBB1.London.opentransit.net [193.251.240.217]

9 25 ms 27 ms 26 ms P13-0.PASCR1.Pastourelle.opentransit.net [193.251.154.225]

10 25 ms 24 ms 24 ms P4-0.BAGCR3.Bagnolet.opentransit.net [193.251.241.118]

11 27 ms 26 ms 26 ms P1-0.BAGBB1.Bagnolet.opentransit.net [193.251.241.145]

12 24 ms 23 ms 24 ms P2-0-0.BAGAR1.Bagnolet.opentransit.net [193.251.128.102]

13 1622 ms 1401 ms 1450 ms WanadooPortails.GW.opentransit.net [193.251.251.214]

14 1748 ms 1627 ms 1614 ms 193.252.123.70

15 1824 ms * 1641 ms

 

[Flimgoblin]

email it to kemor@goa.com with [TRACERT] in the subject

 

[frogster]

13 29 ms 30 ms 30 ms P1-0.BAGBB1.Bagnolet.opentransit.net [193.251.241.145]

14 29 ms 33 ms 28 ms P2-0-0.BAGAR1.Bagnolet.opentransit.net [193.251.128.102]

15 1722 ms 1737 ms 1772 ms WanadooPortails.GW.opentransit.net [193.251.251.214]

16 1716 ms 1659 ms 1771 ms 193.252.123.70

17 1652 ms * 1837 ms 193.252.123.13



Trace complete.

Me think we have found the problem

 

[Lanceloc]

tracert to prydwen from btopenworld adsl customer

C:\Documents and Settings\James>tracert 193.252.123.13

Tracing route to 193.252.123.13 over a maximum of 30 hops

1 25 ms 29 ms 27 ms 217.35.198.203
2 29 ms 29 ms 29 ms 217.35.198.129
3 39 ms 29 ms 29 ms 217.35.198.234
4 59 ms 49 ms 29 ms inh2cs01-601.imsnet2.btopenworld.com [62.7.250.129]
5 29 ms 19 ms 29 ms 213.120.62.149
6 29 ms 19 ms 29 ms 62.6.206.97
7 49 ms 30 ms 28 ms core1-pos4-2.bletchley.ukcore.bt.net [62.6.197.133]
8 29 ms 29 ms 29 ms core1-pos13-3.ilford.ukcore.bt.net [62.6.196.218]
9 29 ms 29 ms 29 ms transit1-pos3-0.ilford.ukcore.bt.net [194.72.20.226]
10 29 ms 29 ms 29 ms transit1-pos3-0.tufnell.ukcore.bt.net [194.72.20.138]
11 29 ms 29 ms 29 ms t2a4-p9-0.uk-lon2.concert.net [166.49.209.13]
12 29 ms 29 ms 29 ms t2c1-ge6-0.uk-lon2.concert.net [166.49.176.11]
13 29 ms 29 ms 29 ms t2c3-p0-0-0.uk-lon1.concert.net [166.49.208.122]
14 39 ms 29 ms 29 ms t2a2-ge8-0-0.uk-lon1.concert.net [166.49.135.50]
15 99 ms 49 ms 39 ms london.opentransit.net [195.66.224.83]
16 39 ms 39 ms 39 ms P13-0.PASCR1.Pastourelle.opentransit.net [193.251.154.225]
17 39 ms 39 ms 59 ms P4-0.BAGCR3.Bagnolet.opentransit.net [193.251.241.118]
18 39 ms 39 ms 59 ms P1-0.BAGBB1.Bagnolet.opentransit.net [193.251.241.145]
19 39 ms 59 ms 39 ms P2-0-0.BAGAR1.Bagnolet.opentransit.net [193.251.128.102]
20 1702 ms 1891 ms 2002 ms WanadooPortails.GW.opentransit.net [193.251.251.214]
21 * 1862 ms 1779 ms 193.252.123.70
22 1699 ms 1772 ms 1742 ms 193.252.123.13

Trace complete.

Bold entry is the offending router IMO.

Emailed to Kemor.

 

[Orin Askhammare]

Tracing route to 193.252.123.33 over a maximum of 30 hops



1 14 ms <10 ms 14 ms d140001.upc-d.chello.nl [213.46.140.1]

2 83 ms 68 ms 14 ms Gig6-0.zp00rt01.brain.upc.nl [212.142.23.193]

3 <10 ms <10 ms 14 ms srp13-0.ah00rt02.brain.upc.nl [212.142.32.138]

4 28 ms 41 ms 14 ms srp0-0.am00rt01.brain.upc.nl [212.142.32.1]

5 69 ms 55 ms 55 ms srp0-0.am00rt05.brain.upc.nl [212.142.32.43]

6 28 ms 14 ms 13 ms gigabitethernet5-2.hsa2.Amsterdam1.Level3.net [213.244.164.57]

7 41 ms 14 ms <10 ms ge-4-3-1-12.mp2.Amsterdam1.Level3.net [213.244.165.34]

8 14 ms 55 ms 41 ms so-3-0-0.mp2.London1.Level3.net [212.187.128.57]

9 14 ms 55 ms * unknown.Level3.net [212.187.131.182]

10 28 ms * 41 ms P1-0.LONBB1.London.opentransit.net [193.251.240.217]

11 55 ms 55 ms 82 ms P13-0.PASCR1.Pastourelle.opentransit.net [193.251.154.225]

12 * 41 ms 82 ms P4-0.BAGCR3.Bagnolet.opentransit.net [193.251.241.118]

13 68 ms 28 ms 96 ms P1-0.BAGBB1.Bagnolet.opentransit.net [193.251.241.145]

14 151 ms 274 ms 165 ms P2-0-0.BAGAR1.Bagnolet.opentransit.net [193.251.128.102]

15 1551 ms 1579 ms 1332 ms WanadooPortails.GW.opentransit.net [193.251.251.214]

16 1387 ms 1757 ms 1497 ms 193.252.123.70

17 1428 ms 1469 ms 1455 ms 193.252.123.33



Trace complete.

That's me... definately a trend

I'm on Chello cable in the Netherlands.

 

[Belsameth]

same here. all is fine untill it reaches Wanadoo
ping plotter txt is in the mail

 

[old.Biffsmash]

Host Name IP Address Hop Ping Time Ping Avg % Loss Pkts r/s Ping best/worst
* Unknown Host * 10.75.0.1 1 32ms
gsr01-pb.blueyonder.co.uk 62.30.192.33 2 7ms
tele2-witt-pos.telewest.net 194.117.136.18 3 12ms
ge51-linx-gw1.cableinet.net 194.117.154.9 4 11ms
gigabitethernet4-0-136.metro2-londencyh00.London1.Level3.net 212.187.151.97 5 12ms
pos8-0.core2.London1.Level3.net 212.113.0.118 6 11ms
P1-0.LONBB1.London.opentransit.net 193.251.240.217 7 11ms
P13-0.PASCR1.Pastourelle.opentransit.net 193.251.154.225 8 18ms
P4-0.BAGCR3.Bagnolet.opentransit.net 193.251.241.118 9 19ms
P1-0.BAGBB1.Bagnolet.opentransit.net 193.251.241.145 10 24ms
P2-0-0.BAGAR1.Bagnolet.opentransit.net 193.251.128.102 11 21ms
WanadooPortails.GW.opentransit.net 193.251.251.214 12 1724ms
* Unknown Host * 193.252.123.70 13 1745ms
* Unknown Host * 193.252.123.13 14 1807ms

in England on Blueyonder Cable, 1mb con

ok so if its not wanadoo/opentransits fault... who is the opentransit server with 1724 ms eh ??

get it sorted m8, the isp needs a kick up the arse, all isp's tell you it aint their fault when it is, blueyonder used to and BT at work do it to me all the time

good luck, wicked game, the work you doin on it is wicked, now you just need to get wanadoo sorted

 

[new_leumas]

Lag is insane for me lately. Every action take roughly 20 sec to get any response. Here my trace.....Tracing route to 193.252.123.33 over a maximum of 30 hops



1 18 ms 10 ms 7 ms 10.223.0.1

2 10 ms 10 ms 15 ms 172.20.23.1

3 21 ms 15 ms 10 ms 172.20.2.87

4 20 ms 10 ms 15 ms 172.20.6.3

5 12 ms 13 ms 12 ms 202.160.243.213

6 11 ms 18 ms 51 ms POS3-0.tp-core2.ix.singtel.com [202.160.250.173]

7 199 ms 200 ms 200 ms p5-1.plapx-cr1.ix.singtel.com [203.208.172.30]

8 198 ms 204 ms 203 ms g0-0-0.plapx-ar1.ix.singtel.com [203.208.172.46]

9 206 ms 217 ms 206 ms gig-paix.palbb2.opentransit.net [198.32.176.128]

10 230 ms 228 ms 237 ms P12-0.PALBB1.Palo-alto.opentransit.net [193.251.240.25]

11 217 ms 207 ms 214 ms P10-0.SJOCR1.San-jose.opentransit.net [193.251.242.93]

12 284 ms 284 ms 291 ms P3-0.NYKCR2.New-york.opentransit.net [193.251.241.209]

13 387 ms 381 ms 380 ms P4-0.PASCR1.Pastourelle.opentransit.net [193.251.241.133]

14 359 ms 362 ms 358 ms P4-0.BAGCR3.Bagnolet.opentransit.net [193.251.241.118]

15 380 ms 383 ms 385 ms P1-0.BAGBB1.Bagnolet.opentransit.net [193.251.241.145]

16 393 ms 396 ms 398 ms P2-0-0.BAGAR1.Bagnolet.opentransit.net [193.251.128.102]

17 2116 ms 2363 ms 2199 ms WanadooPortails.GW.opentransit.net [193.251.251.214]

18 2123 ms 2182 ms 2128 ms 193.252.123.70

19 2096 ms 2164 ms 2111 ms 193.252.123.33



Trace complete.

ps : Just notice everyone have insane ping at wannadoo.

 

[frogster]

Also in the mail

 

[Jupitus]

Originally posted by kemor
2) After contacting Opentransit (our ISP), we got the confirmation that there was nothing wrong on their side lately.

Sorry Kemor, but that looks to me like Bull**** with a Capital 'B' I would suggest someone pulls the head of the representative at Opentransit who told you this ....

 

[old.Marabeth]

Mine is bonkers at Wanadoo as well, damn them.

 

[Wij]

Same result.

Can't be bothered mailing a virtual duplicate of everyone else's problem

 

[kemor]

Alright folks, will do a bigger news tomorrow once we have more news but, after shoving..err..showing the problem and the tracerts to the opentransit folks, we got some different news :

ps : bear with me, i'm not a network monkey

"for reasons still unknown (but they are actively looking for them), it seems that there is a problem on one of the Opentransit router. However, this problem is a bit weird and could be related to a more important problem affecting the european internet network.

As you may know, many companies dealing with internet connection went/are going bankrupt lately and a lot of people are re-routed on the same routers causing what some call a "bottleneck".

The problem we have lately with connection seems to be "upstream" (like at the top of a river, some rocks blocking the flow of the water, slow the whole current). Many ISPs are trying to rout their clients to opentransit network, and they are slowing down everyone.

Some players can play without ANY problem, with a perfect ping to our servers, while some are stopped on Opentransit router.

Really cannot give more information right now, but hopefully the night will bring us more details....

Stay tuned, more details tomorrow...


__________________

 

[Lydek]

Just to point out... this is the same router thats caused pretty much every other connection problem since release.

Doesn't sound especially likely that the recent collapse of KPNQwest would be the cause of a problem that first occured well before yesterday when Ebone was finally put of its misery.

 

[Orin Askhammare]

No, but KPNQwest and Ebone's demise might have been the straw that REALLY broke the camel's back though

 

[Lanceloc]

Go to http://www.ripe.net/ click on WhoisDB and enter the offending routers IP address which is 193.251.251.214 and you get the owners of that network as follows. These are the guys GOA need to contact and I'm sure they will...

EDIT: Its possible the router is overloaded which means surrounding routers are using this particular router too much. There are several routes to any destination computer hooked up to the Internet and routers need their routing tables configured well or bottlenecking occurs. I agree with what Kemor is saying.

% This is the RIPE Whois server.
% The objects are in RPSL format.
% Please visit http://www.ripe.net/rpsl for more information.
% Rights restricted by copyright.
% See http://www.ripe.net/ripencc/pub-services/db/copyright.html

inetnum: 193.251.240.0 - 193.251.255.59
netname: OPENTRANSIT-BACKBONE
descr: France Telecom Long Distance
descr: 246 rue de Bercy 75012 Paris
country: FR
admin-c: JQ74-RIPE
tech-c: SD2707-RIPE
tech-c: CC254-RIPE
status: ASSIGNED PA
mnt-by: FT-BRX
changed: gestionip.ft@francetelecom.fr 20001024
source: RIPE

route: 193.251.240.0/20
descr: France Telecom
descr: OPENTRANSIT
origin: AS5511
mnt-by: FT-BRX
changed: gestionip.ft@francetelecom.fr 20010130
source: RIPE

person: Jean Quevarec
address: France Telecom Long Distance
address: 7, avenue Gambetta
address: 93177 Bagnolet Cedex
phone: +33 1 49 93 84 61
fax-no: +33 1 43 63 01 17
e-mail: jean.quevarec@francetelecom.com
nic-hdl: JQ74-RIPE
notify: admin@opentransit.net
mnt-by: FTRSI
changed: noc@rain.fr 19990209
changed: jean.quevarec@francetelecom.fr 19990913
changed: admin@opentransit.net 20010516
source: RIPE

person: Stephane Duverneix
address: France Telecom Long Distance
address: 7, avenue Gambetta
address: 93177 Bagnolet Cedex
address: France
phone: +33 1 49 93 85 47
fax-no: +33 1 43 63 01 17
e-mail: stephane.duverneix@francetelecom.com
e-mail: duvernei@opentransit.net
nic-hdl: SD2707-RIPE
notify: admin@opentransit.net
mnt-by: FTRSI
changed: jean.quevarec@francetelecom.fr 20000117
changed: admin@opentransit.net 20010516
source: RIPE

person: Christophe Chaillot
address: France Telecom Long Distance
address: FTLD/IAP/WIN
address: 61, rue des Archives
address: 75003 Paris
address: France
phone: +33 1 40 29 66 73
e-mail: christophe.chaillot@francetelecom.com
nic-hdl: CC254-RIPE
notify: admin@opentransit.net
mnt-by: FTRSI
changed: noc@rain.fr 19981125
changed: admin@opentransit.net 20010516
changed: admin@opentransit.net 20020325
source: RIPE

 

[censi]

Kemor, the lack of concern coming from GOA about this problem is a disgrace. ( and yes I understand its a networking fault outside your domain)

Get a post out on the main DAOC europa site, stating about this problem (that is effecting your whole customer base)

Keep this post updated at least 3 times a day untill the problem is corrected.

This is the absolute bare minimum GOA should be doing to keep us informed.

You have no idea how angry everyone is about this... You just arn't keeping us informed.

There are much better diagonstics you could be doing than getting customers to provide you with trace routes. Thats just gonna give you a snapshot well after the point of hi latency when they were LD'd. The latency spike will be long gone by the time they run the trace.

Ill give up now before I say something Ill regret about your company.

**lights hamlet**

 

[Cro Bar]

>>
There are much better diagonstics you could be doing than getting customers to provide you with trace routes. Thats just gonna give you a snapshot well after the point of hi latency when they were LD'd. The latency spike will be long gone by the time they run the trace.
<<

censi, Thats a bit strong mate, the problem we have is not a spike.... I sat lastnight and waited for half an hour for this Router to free up, Good ol Kemor needed a bit of ammo to throw at the ISP... and what better than a S*it load of Tracers from all over all pointing to thier router.....

I do think the Webby could be updated much more often or else a nice BIG link to the BW forums....

 

[Grym]

Well i feel sad of you all that had lagg

mohahhaha (evul laugh) I did not get a singel ld or nothing no lagg did not get ld when server crashed

For once im happy with Telia Adsl 0,5 mb

but only for gameing when downloading stuff thats another thing

 

[old.Biffsmash]

well i have been personally been getting bad lag on the game for a good month now i think, dont think its anything to do with internet companies going bump, just the opentransit/wanadoo servers. I can get exellent connection to other gaming servers, UO servers and just about any website I try,.

I think this is just a shoddy Isp problem (opentransit or whoever they are called) and nothing more.

 

[Jupitus]

Kemor posted in the general area and not here, so quoting:

Originally posted by kemor
As updated in the threads...

UPDATE
Now, i need traceroutes from players who do NOT have problems while their friends are dropping like flies all around the realms.
Same procedure, with just a different subject : [CLEAN TRACERT]

Thanks.

More info to gather guys..... if you see a mass l/d happen but stay ingame without lag, then please take the time to quit a while and run a tracert as described above.

 

[old.Zuljin]

Oh well. here we go again.. i must say to all the People that lives in Denmark, got TDC as ISP and got "NetExpress". Check if you can get online and if you cant.. call TDC customer support at 80808036 and ask them to reset your line.
the reason i say that is that 6/10 of all my LD's have been my own ISP's fault and i have spend hours just to get it up again ( got a total of 67 Resets the past 2 month ) so plz do GoA that favor and call TDC, they might be able to help you

 

[Cerverloc]

I think its time GOA sat around the table with a few Wanadoo guys because you are going to lose customers because of this. I haven't had any problems until recently and its only on Excalibur server atm (where my main char is ) When I log on Prywden I got no lag and when I log on Excal its unplayable.

Im not paying money every month for this kinda crap. This failing router should be dealt with quick!!!