Connection problems today...

[kemor]

Hiyas everyone,

It seems that some players are having trouble to connect to our network (forums/homepage) and to the game (black character screen).

We are investigating but what i could use for now is :
- your ISP
- a nice little pingplotter screenshot or a log of a tracert to our servers. (Trace to one of these IPs : 193.252.123.33 or
193.252.123.13 )

Stay tune...

 

[ajeroth]

Tracert

Didnt include details of where to send it, so :

C:\>tracert 193.252.123.13

Tracing route to 193.252.123.13 over a maximum of 30 hops

1 31 ms 31 ms 31 ms lon1-adsl1-tt1.nildram.net [195.149.20.11]
2 31 ms 31 ms 31 ms lon1-1.nildram.net [195.112.4.1]
3 31 ms 31 ms 32 ms lon1-9.nildram.net [195.149.20.109]
4 32 ms 31 ms 31 ms lon1-4.nildram.net [195.149.20.144]
5 32 ms 31 ms 31 ms ldn-th-i3-feth3-0.telia.net [213.248.75.65]
6 31 ms 31 ms 31 ms ldn-hex-b1-srp5-0.telia.net [193.45.0.129]
7 47 ms 47 ms 47 ms london.opentransit.net [195.66.224.83]
8 47 ms 46 ms 47 ms P13-0.PASCR1.Pastourelle.opentransit.net [193.251.154.225]

9 47 ms 47 ms 47 ms P4-0.BAGCR3.Bagnolet.opentransit.net [193.251.241.118]
10 47 ms 47 ms 47 ms P1-0.BAGBB1.Bagnolet.opentransit.net [193.251.241.145]
11 47 ms 47 ms 47 ms P2-0-0.BAGAR1.Bagnolet.opentransit.net [193.251.128.102]
12 47 ms 46 ms 47 ms WanadooPortails.GW.opentransit.net [193.251.251.214]
13 47 ms 47 ms 47 ms 193.252.123.70
14 47 ms 47 ms 47 ms 193.252.123.13

And for the other ip:

C:\>tracert 193.252.123.33

Tracing route to 193.252.123.33 over a maximum of 30 hops

1 47 ms 31 ms 31 ms lon1-adsl1-tt1.nildram.net [195.149.20.11]
2 32 ms 31 ms 31 ms lon1-1.nildram.net [195.112.4.1]
3 31 ms 31 ms 31 ms lon1-9.nildram.net [195.149.20.109]
4 47 ms 31 ms 31 ms lon1-4.nildram.net [195.149.20.144]
5 32 ms 31 ms 31 ms ldn-th-i3-feth3-0.telia.net [213.248.75.65]
6 31 ms 31 ms 31 ms ldn-thoe-b1-srp9-0.telia.net [193.45.0.134]
7 47 ms 46 ms 47 ms london.opentransit.net [195.66.224.83]
8 47 ms 47 ms 47 ms P13-0.PASCR1.Pastourelle.opentransit.net [193.251.154.225]

9 47 ms 47 ms 47 ms P4-0.BAGCR3.Bagnolet.opentransit.net [193.251.241.118]
10 47 ms 47 ms 47 ms P1-0.BAGBB1.Bagnolet.opentransit.net [193.251.241.145]
11 47 ms 46 ms 47 ms P2-0-0.BAGAR1.Bagnolet.opentransit.net [193.251.128.102]
12 47 ms 47 ms 47 ms WanadooPortails.GW.opentransit.net [193.251.251.214]
13 47 ms 47 ms 47 ms 193.252.123.70
14 47 ms 47 ms 47 ms 193.252.123.33

Both gotten to quite happily...I still cant connect to the web pages, and have a blank character selector screen. Nildram havent gotten back to me about their 'upstream issues'.

[edit]
What I find strange, is that the login bit works fine, and the game claims to have opened and made a connection to the server. I can even view the status of the servers, and whether they are open or not (selected by no quickstart)...I just cant log in as a character, or even select/create a character.

Ta, Jorath.

 

[kemor]

Ok, as i posted on the DaoC EU forums, some ISPs are having "peering" problems with OpenTransit.
It means that they have a too small "cable" linking their network to the European Network and sometimes, like now, that can cause some problems (that's what the techies told me, i think

This is not really on GOA's side, but we contacted our ISP, who is working on something to try and fix that.

Mostly Nildram users are experiencing problems today and i do not ahve any ETA yet. Put some pressure on Nildram so they buy a bigger cable or something

Stay tuned..

 

[old.dc.snoz]

My isp is nildram

and heres my tracert

Tracing route to 193.252.123.13 over a maximum of 30 hops

1 <10 ms <10 ms <10 ms TONY-L33TPC [192.168.0.1]
2 20 ms 20 ms 30 ms lon1-adsl1-tt2.nildram.net [195.149.20.12]
3 20 ms 20 ms 30 ms lon1-1.nildram.net [195.112.4.1]
4 20 ms 20 ms 30 ms lon1-9.nildram.net [195.149.20.109]
5 20 ms 30 ms 20 ms lon1-4.nildram.net [195.149.20.144]
6 20 ms 30 ms 30 ms ldn-th-i3-feth3-0.telia.net [213.248.75.65]
7 20 ms 30 ms 20 ms ldn-thoe-b1-srp9-0.telia.net [193.45.0.134]
8 30 ms 40 ms 30 ms london.opentransit.net [195.66.224.83]
9 31 ms 40 ms 40 ms P13-0.PASCR1.Pastourelle.opentransit.net [193.25
1.154.225]
10 30 ms 40 ms 40 ms P4-0.BAGCR3.Bagnolet.opentransit.net [193.251.24
1.118]
11 30 ms 40 ms 30 ms P1-0.BAGBB1.Bagnolet.opentransit.net [193.251.24
1.145]
12 30 ms 40 ms 40 ms P2-0-0.BAGAR1.Bagnolet.opentransit.net [193.251.
128.102]
13 30 ms 40 ms 120 ms WanadooPortails.GW.opentransit.net [193.251.251.
214]
14 121 ms 40 ms 40 ms 193.252.123.70
15 40 ms 40 ms 30 ms 193.252.123.13


and

Tracing route to 193.252.123.33 over a maximum of 30 hops

1 <10 ms <10 ms <10 ms TONY-L33TPC [192.168.0.1]
2 20 ms 30 ms 20 ms lon1-adsl1-tt2.nildram.net [195.149.20.12]
3 20 ms 20 ms 30 ms lon1-1.nildram.net [195.112.4.1]
4 20 ms 30 ms 20 ms lon1-9.nildram.net [195.149.20.109]
5 20 ms 30 ms 20 ms lon1-4.nildram.net [195.149.20.144]
6 20 ms 30 ms 30 ms ldn-th-i3-feth3-0.telia.net [213.248.75.65]
7 20 ms 30 ms 30 ms ldn-thoe-b1-srp9-0.telia.net [193.45.0.134]
8 30 ms 40 ms 30 ms london.opentransit.net [195.66.224.83]
9 30 ms 40 ms 40 ms P13-0.PASCR1.Pastourelle.opentransit.net [193.25
1.154.225]
10 30 ms 40 ms 40 ms P4-0.BAGCR3.Bagnolet.opentransit.net [193.251.24
1.118]
11 30 ms 40 ms 30 ms P1-0.BAGBB1.Bagnolet.opentransit.net [193.251.24
1.145]
12 30 ms 40 ms 30 ms P2-0-0.BAGAR1.Bagnolet.opentransit.net [193.251.
128.102]
13 30 ms 40 ms 40 ms WanadooPortails.GW.opentransit.net [193.251.251.
214]
14 30 ms 40 ms 40 ms 193.252.123.70
15 30 ms 160 ms 40 ms 193.252.123.33


Same as guy above ... i cant access your website or even get paste the patch updater :| but i reach the ip fine

 

[ajeroth]

Nildram problems

I can get past the patcher, and can even get onto the server provided I dont choose a character to log in as. Even then, I am faced with a blank character selector screen..so cant actually do anything anyway

Looks like hope is running out for tonight, so Nildram have really let us down this time. So much for my recommendation as one of the best ADSL isp's out there.

Ta, Jo.

 

[old.Mjr tOm]

looks like i'm watchin telly for the first time in 6 weeks tonight....

i've emailed nildram with the url of this thread so hopefully they will be on the case but im not hopeful of playin tonight

 

[ajeroth]

for nildram

They performed a simple fix at nearly 8, then fixed it properly at 10. Nice, thats what I call prompt and decent service.

Ta, Jorath.

 

[old.dc.snoz]

also from what i read on adsl guide ... was not nildram fault either ... shame the whole net is not run by nilly tbh ...