link dead all the time

I can be playing away quite happily on shrouded isles when the game will go link dead. I will try to reconnect and the game will patch itself for some reason. (am playing UK version of game)

Once the patch has completed I am unable to login as it tells me that my username or password is incorrect. The only thing that seems to resolve the issue is a reinstallation of shrouded isles, until I go link dead again. Then I have to repeat the process.

This is starting to wear thin as you can imagine as I've had to reinstall the damn thing twice this evening all ready, anyone have any solutions to my little problem ?

thankyou

http://forums.barrysworld.com/showthread.php?threadid=66526

That will solve the patching problem but it will not solve this problem

9 28 ms 29 ms 29 ms P9-0.BAGBB2.Bagnolet.opentransit.net [193.251.241.254]
10 * * * Request timed out.
11 29 ms 30 ms 30 ms 193.252.122.14

Seems this evening, for me anyway, that

WanadooPortails.GW.opentransit.net [193.251.251.54] is playing up

I assume from your symptoms (being identical to mine) that this lil router aint playing properly.
I have rightnow'd and am looking forward to a responce.

Im having same problem from nildram isp in the uk

I have exactly the same issue - i'm also with Nildram and have been having LDs since yesterday evening (played all night friday without any hiccups so this must be new). Impossible to play atm.

Mercurial Lazarus L50 Cleric
Eidolon Strange L50 Infiltrator
Proud Member of The Phoenix Legion

Had issues saturday night - also on nildram, was ok sunday tho, havent tried today.

Same here, also on Nildram.

I've emailed nildram support with the problem, maybe if u guys do to it will speed stuff up :]

http://support.nildram.net/email.php

Quite confusing that we are all on Nildram yet the problem lies at the Wanado router (for me and snoz anyway)

Whats the IP of Prydwen ? cant find out from work - would like to include that in my support call to Nildram.

193.252.122.14

Nildram user with same problem here. I also posted about it here:

http://forums.barrysworld.com/showthread.php?&threadid=71650

and started a thread on the adslguide forum:

http://bbs.adslguide.org.uk/showflat.php?Cat=&Board=nildram&Number=799982

Some tracerts and/or emails to nildram may help to speed up a fix for it.

I'm also with Nildram ADSL (the lite version £23 per month one) but *not* having any problems. Strange but I'm not complaining ...

Suffering from the same problems, however, i use Andrews & Arnold as an ISP.

Watching my net activity tonight with VisualRoute, i had the following report.

( on average, over a 2 hour period i dropped suffiecient packets to cause LD about every 5 minutes )

================================================
=== VisualRoute report on 21-Jul-03 19:19:33 ===
================================================

Report for 193.252.123.24

Analysis: '193.252.123.24' was found in 15 hops (TTL=49). But, problems starting at hop 10 in network "France Telecom Long Distance" are causing IP packets to be dropped.

------------------------------------------------------------------------------------------------------------------------------
| Hop | %Loss | IP Address | Node Name | Location | Tzone | ms | | Network
---------------------------------------------------------------------------------------------------------------------------------
| 0 | | ************* | ME MACHINE | * | | | | None specified
| 1 | | ************* | - | (United Kingdom) | * | 0 | | None specified
| 2 | | 217.47.56.73 | aa1-hg2.ilford.broadband.bt.net | Ilford, London | * | 23 | | RAS Boxes
| 3 | | 217.47.56.1 | aa1-fer1G30.ilford.broadband.bt.net | Ilford, London | * | 24 | | RAS Boxes
| 4 | | 217.47.56.110 | aa1-nteatm2.2.ilford.broadband.bt.net | Ilford, London | * | 30 | | RAS Boxes
| 5 | | 217.169.20.3 | aimless.aaisp.net.uk | ?(United Kingdom) | * | 26 | | Customer rack space
| 6 | | 213.161.69.147 | 186.ge1-0.er1b.lhr4.uk.above.net | London, UK | * | 24 | | AboveNet UK
| 7 | | 208.184.231.133 | so-3-2-0.cr2.lhr4.uk.above.net | London, UK | * | 25 | | Abovenet
| 8 | | 208.184.231.169 | pos7-3.mpr2.lhr1.uk.above.net | London, UK | * | 18 | | Abovenet
| 9 | | 193.251.154.65 | P8-3.LONBB1.London.opentransit.net | London, UK | * | 22 | | France Telecom Long
| 10 | 10 | 193.251.128.185 | P10-0.AUVCR1.Aubervilliers.opentransit.net | Aubervilliers, France | +01:00 | 37 | | France Telecom
| 11 | 10 | 193.251.241.93 | P6-0.BAGCR1.Bagnolet.opentransit.net | Bagnolet, France | +01:00 | 27 | | France Telecom
| 12 | 10 | 193.251.241.254 | P9-0.BAGBB2.Bagnolet.opentransit.net | Bagnolet, France | +01:00 | 30 | | France Telecom
| 13 | 100 | ?193.251.251.54 | WanadooPortails.GW.opentransit.net | | | | | France Telecom
| 14 | 10 | 193.252.122.14 | - | ?(France) | +01:00 | 37 | | Wanadoo Portails
| 15 | 10 | 193.252.123.24 | - | ?(France) | +01:00 | 37 | | Wanadoo Portails
---------------------------------------------------------------------------------------------------------------------------------------------
Roundtrip time to 193.252.123.24, average = 37ms, min = 27ms, max = 55ms -- 21-Jul-03 19:19:33

hope the formatting is ok. <edit, nope, in fact formatting is terrible, but might be good enough >

not sure if the problem is Wanadoo or not, as report suggests problems occuring earlier down the line, but if thats the case i wonder why only a few ISP users are suffering this ?

I am also with Nildram ADSL and also having problems with going LD within seconds of logging in.... has anyone actually contacted Nildram about this?

If so can we have details of what they said here?

Ok, I just spoke to Nildram support....

All Nildram users who are experiencing this problem please send an email to Nildram by clicking this link: http://support.nildram.net/email.php

Please include where you are connecting from, a trace route and any and all other relevant information that you can

hopefully we can get a speedy resolution pushed through....

aye same here nildram also ..e-mailed sunday afternoon

Seams fine for me tonight - on nildram

[nxs@spellfire nxs]$ /usr/sbin/traceroute 193.252.123.24
traceroute to 193.252.123.24 (193.252.123.24), 30 hops max, 38 byte packets
1 192.168.100.200 (192.168.100.200) 0.706 ms 0.373 ms 0.332 ms
2 lon1-adsl6.nildram.net (213.208.106.124) 20.310 ms 18.495 ms 19.006 ms
3 lon1-9.nildram.net (213.208.106.194) 20.471 ms 19.552 ms 21.751 ms
4 lon1-6.nildram.net (195.149.20.132) 19.961 ms 19.431 ms 19.628 ms
5 246.ge6-0.mpr1.lhr1.uk.above.net (213.161.78.109) 19.313 ms 20.255 ms 20.328 ms
6 pos5-0.mpr2.lhr1.uk.mfnx.net (208.185.156.14) 20.158 ms 19.428 ms 19.636 ms
7 P8-3.LONBB1.London.opentransit.net (193.251.154.65) 20.277 ms 19.236 ms 19.739 ms
8 P10-0.AUVCR1.Aubervilliers.opentransit.net (193.251.128.185) 27.716 ms 26.781 ms 27.731 ms
9 P6-0.BAGCR1.Bagnolet.opentransit.net (193.251.241.93) 28.447 ms 28.923 ms 27.836 ms
10 P9-0.BAGBB2.Bagnolet.opentransit.net (193.251.241.254) 27.428 ms 30.055 ms 29.613 ms
11 WanadooPortails.GW.opentransit.net (193.251.251.54) 29.652 ms 28.170 ms 27.172 ms
12 193.252.122.14 (193.252.122.14) 29.056 ms 28.433 ms 28.379 ms
13 193.252.123.24 (193.252.123.24) 27.630 ms 28.437 ms 29.090 ms

Exactly same problems here, only then with Cistron ADSL in Holland

I spammed a few tracerts for a couple of mins or two to the excaliber ip and all seemed fine. Connected to the server and within about 3 mins, lag spike, packet loss, linkdead :/
I think some kind of packet monitoring program is needed, as it seems to occur periodically, although very regularly. Any suggestions?

hmmm on second thoughts it could be ........

Tracing route to 193.252.123.23 over a maximum of 30 hops

1 1 ms <1 ms <1 ms my.personal.ip.address
2 17 ms 16 ms 18 ms lon1-adsl5.nildram.net [213.208.106.112]
3 18 ms 16 ms 15 ms lon1-9.nildram.net [213.208.106.194]
4 17 ms 16 ms 17 ms lon1-6.nildram.net [195.149.20.132]
5 20 ms 23 ms 19 ms 246.ge6-0.mpr1.lhr1.uk.above.net [213.161.78.109]
6 18 ms 16 ms 17 ms pos5-0.mpr2.lhr1.uk.mfnx.net [208.185.156.14]
7 18 ms 18 ms 16 ms P8-3.LONBB1.London.opentransit.net [193.251.154.65]
8 26 ms 25 ms 25 ms P10-0.AUVCR1.Aubervilliers.opentransit.net [193.251.128.185]
9 27 ms 25 ms 26 ms P6-0.BAGCR1.Bagnolet.opentransit.net [193.251.241.93]
10 26 ms 26 ms 27 ms P9-0.BAGBB2.Bagnolet.opentransit.net [193.251.241.254]
11 * * * Request timed out.
12 27 ms 25 ms 27 ms 193.252.122.14
13 26 ms 27 ms 28 ms 193.252.123.23

hop 11 appears to be

WanadooPortails.GW.opentransit.net [193.251.251.54]

I am having the same problem with Direct IP/ADSLnow. It is fine during the day, but once it gets to about 6pm I'll end up LDing every couple of minutes. Ran viruscheck, scanned for spybots and that sorta thing, cleaned all the leads, no change. It is simply unplayable at the moment.

And when my trace dies, it dies at the same place. I think it started when that router blew the other day...

Still screwed this morning, No reply from nildram or GOA here ..



Target Name: N/A
IP: 193.252.123.177
Date/Time: 22/07/2003 08:32:09 to 22/07/2003 08:37:29

Hop Sent Err PL% Min Max Avg Host Name / [IP]
1 33 0 0.0 0 0 0 TONY [192.168.0.1]
2 33 0 0.0 16 21 18 lon1-adsl6.nildram.net [213.208.106.124]
3 33 0 0.0 16 21 18 lon1-9.nildram.net [213.208.106.194]
4 33 0 0.0 16 22 18 lon1-6.nildram.net [195.149.20.132]
5 33 0 0.0 17 24 19 246.ge6-0.mpr1.lhr1.uk.above.net [213.161.78.109]
6 33 0 0.0 17 40 19 pos5-0.mpr2.lhr1.uk.mfnx.net [208.185.156.14]
7 33 0 0.0 16 61 19 P8-3.LONBB1.London.opentransit.net [193.251.154.65]
8 33 3 9.1 25 88 29 P10-0.AUVCR1.Aubervilliers.opentransit.net [193.251.128.185]
9 33 3 9.1 24 126 29 P6-0.BAGCR1.Bagnolet.opentransit.net [193.251.241.93]
10 33 3 9.1 24 114 29 P9-0.BAGBB2.Bagnolet.opentransit.net [193.251.241.254]
11 33 10 30.3 25 90 29 WanadooPortails.GW.opentransit.net [193.251.251.54]
12 33 9 27.3 26 66 29 [193.252.122.14]
13 33 9 27.3 26 44 28 [193.252.123.177]


Sucks

just got normal reply from nildram ;


Thank you for contacting Nildram Support.

One of our engineers is currently investigating the problem
and will be in contact as soon as possible.

Your reference for this is 138686 please quote this in any correspondence.

Kind Regards,
Nildram Customer Support

excellent, I still don't have a reply

Same reply as Snoz from Nildram, as yet no reply from GOA...

Hmm

I was fine all last night, untill about 11.30.

Then LD, loging, LD, loggin, LD etc etc.

Gave up in the end, and havn't tried today yet (since i am at work)

Am with BT Broadband though.

been on now since 11am now 12.05 am no lag at all ... maybe fixed

my packet loss is down from average 65% to 1 or 2% but my lag spikes have increased but over all my ping average is only up by 10

Target Name: N/A
IP: 193.252.123.33
Date/Time: 7/23/2003 3:04:20 PM to 7/23/2003 3:29:41 PM

Hop Sent Err PL% Min Max Avg Host Name / [IP]
1 1487 0 0.0 0 13 0 [192.168.0.200]
2 1487 0 0.0 17 89 20 gw-216-11.sms-1.ams-tel.cistron.net [62.216.11.1]
3 1487 0 0.0 18 97 21 ve-21.rtr-1.ams-sar.cistron.net [62.216.31.161]
4 1487 0 0.0 18 120 22 ams31-cistron-nl.ams.seabone.net [195.22.213.133]
5 1487 4 0.3 18 117 21 amsix1-ams31-racc1.ams.seabone.net [195.22.213.201]
6 1487 5 0.3 26 105 29 lon7-lon1-racc1.lon.seabone.net [195.22.209.98]
7 1487 1 0.1 26 175 30 So2-2-1.LONCR1.London.opentransit.net [193.251.129.45]
8 1487 74 5.0 36 161 39 P1-0.PASCR3.Pastourelle.opentransit.net [193.251.128.222]
9 1487 75 5.0 36 143 43 P12-0.BAGCR1.Bagnolet.opentransit.net [193.251.241.130]
10 1487 79 5.3 36 115 39 P9-0.BAGBB2.Bagnolet.opentransit.net [193.251.241.254]
11 1487 76 5.1 36 135 43 WanadooPortails.GW.opentransit.net [193.251.251.54]
12 1487 74 5.0 38 192 44 [193.252.122.14]
13 1487 73 4.9 37 165 41 [193.252.123.33]


For me its always P1-0.PASCR3.Pastourelle.opentransit.net thats acting up

Its become such a problem for me that I cant even play properly because its not constant packetloss its spikes... Every x minutes I get a spike of 100% packetloss for 10-30s ...