Going Linkdeath after 5 min online..

[Vigo_Twister]

Always going linkdeath after 1-5 min ingame, this not happens with other online games so i doubt it will be an ISP problem and the tracert it´s ok..

I´m using:
Win Xp
AMD Athlon xp 2000+
256 RAM
Geforce4 mx440 (last drivers)
Adsl with wanadoo on a zyxel router 642 r-11 (multimode)
Motherboard k7s5a (last drivers)

I played this game ok 1 week later without any problems (same config) and run out of ideas plz help).

 

[Jebelious]

what happens after the LD? and is you computer the main internet sharer? could be a problem with a server or somehtin. can you still browse the net after the ld etc?

 

[Vigo_Twister]

..

what happens after the LD?

It appears a screen with the mensage: You have gone linkdead, your client stopped receiving mensages from the server or something like that.

can you still browse the net after the ld etc?

Yes, i can browse the web after this and reconnect to daoc and going again linkdead .

and is you computer the main internet sharer?

Yes, well, the router is in multimode not for me, it came in that mode, but my computer is the only one connected to it.

 

[Addlcove]

well for startes get a real GF4 not the ugly MXversion

won't help your LD's but will make your system better
---

ok on topic, try starting a ping of the server you play (IP's can be obtained from inhere somewhere )

just to check if your connection is slowing down for you to go LD or if it gets "timeouts"

(if it only slows down put game in minimum settings and try again)

check bcak when you´ve done that and tell us what happened

 

[Vigo_Twister]

Not much.. connection it´s ok almost it seems to be.

Respuesta desde 193.252.123.13: bytes=32 tiempo=207ms TTL=45
Respuesta desde 193.252.123.13: bytes=32 tiempo=207ms TTL=45
Respuesta desde 193.252.123.13: bytes=32 tiempo=206ms TTL=45
Respuesta desde 193.252.123.13: bytes=32 tiempo=208ms TTL=45
Respuesta desde 193.252.123.13: bytes=32 tiempo=206ms TTL=45
Respuesta desde 193.252.123.13: bytes=32 tiempo=205ms TTL=45
Respuesta desde 193.252.123.13: bytes=32 tiempo=207ms TTL=45
Respuesta desde 193.252.123.13: bytes=32 tiempo=208ms TTL=45
Respuesta desde 193.252.123.13: bytes=32 tiempo=207ms TTL=45
Respuesta desde 193.252.123.13: bytes=32 tiempo=209ms TTL=45
Respuesta desde 193.252.123.13: bytes=32 tiempo=210ms TTL=45
Respuesta desde 193.252.123.13: bytes=32 tiempo=207ms TTL=45
Respuesta desde 193.252.123.13: bytes=32 tiempo=206ms TTL=45
Respuesta desde 193.252.123.13: bytes=32 tiempo=208ms TTL=45
Respuesta desde 193.252.123.13: bytes=32 tiempo=206ms TTL=45
Respuesta desde 193.252.123.13: bytes=32 tiempo=207ms TTL=45
Respuesta desde 193.252.123.13: bytes=32 tiempo=207ms TTL=45
Respuesta desde 193.252.123.13: bytes=32 tiempo=208ms TTL=45
Respuesta desde 193.252.123.13: bytes=32 tiempo=207ms TTL=45
Respuesta desde 193.252.123.13: bytes=32 tiempo=208ms TTL=45
Respuesta desde 193.252.123.13: bytes=32 tiempo=208ms TTL=45
Respuesta desde 193.252.123.13: bytes=32 tiempo=207ms TTL=45
Respuesta desde 193.252.123.13: bytes=32 tiempo=210ms TTL=45
Respuesta desde 193.252.123.13: bytes=32 tiempo=209ms TTL=45
Respuesta desde 193.252.123.13: bytes=32 tiempo=111ms TTL=45
Respuesta desde 193.252.123.13: bytes=32 tiempo=109ms TTL=45
Respuesta desde 193.252.123.13: bytes=32 tiempo=113ms TTL=45
Respuesta desde 193.252.123.13: bytes=32 tiempo=112ms TTL=45
Respuesta desde 193.252.123.13: bytes=32 tiempo=206ms TTL=45
Respuesta desde 193.252.123.13: bytes=32 tiempo=210ms TTL=45
Respuesta desde 193.252.123.13: bytes=32 tiempo=207ms TTL=45

It´s in spanish, but you will see that the ping is fairly good with the Prydwen server (i think is that ip ).

 

[Addlcove]

that should rule out loss of con then, now did you try to turn all the settings to minimum? (standard classic client settings)

 

[Vigo_Twister]

did you try to turn all the settings to minimum? (standard classic client settings)

Aye, i´m running with the lowest resolution and without any spell effects (running classic client). And still going LD

 

[Addlcove]

when did it start doing this? or are you a new player who just started playing?

 

[Vigo_Twister]

..

I play since january 2003, and i had no problems except 1 week ago that i have this issue.

 

[Addlcove]

well, what did you change on your system 1 week ago?`

 

[Vigo_Twister]

Nothing changed, that´s for what i run out of ideas

 

[Addlcove]

you didn´t install anything on your computer? or change any settings?

 

[Addlcove]

in general I want to know ALL the changes mae on your system, not just the changes related to daoc

 

[Vigo_Twister]

The first thing i think was that something was changed, so i format and reinstall win xp again and only daoc to make sure that was not a problem on my comp. But was wrong when i tried it, it still went LD all over again.. So i intall the new grafic drivers and again the same problem., then i try to deactivate all the filters of my router, but the problem persisted. That´s all i do atm.

One thing that i saw on the tracert is that one node changes from one time to another.. see it.

Target Name: (resolving host name)
IP: 193.252.123.13
Date/Time: 30/10/2002 20:15:40

1 0 ms [192.168.1.1]
2 58 ms MADR-R25-NRP4.red.retevision.es [62.81.124.196]
3 53 ms MADR-R15.red.retevision.es [62.81.3.69]
4 53 ms MADR-R16.red.retevision.es [62.81.3.70]
5 52 ms MADR-R00.red.retevision.es [62.81.4.97]
6 85 ms mil5-retevision-12-es.seabone.net [195.22.196.57]
7 88 ms mil14-mil7-racc1.mil.seabone.net [195.22.208.46]
8 111 ms iar2-so-2-3-0.Thamesside.cw.net [166.63.214.145]
9 114 ms bcr2.Thamesside.cw.net [166.63.210.62]
10 114 ms zcr2-loopback.Londonlnt.cw.net [166.63.210.19]
11 114 ms zpr1-ge-0-3-0.Londonlnt.cw.net [166.63.222.134]
12 115 ms So2-2-2.LONCR1.London.opentransit.net [193.251.254.17]
13 114 ms P1-0.PASCR3.Pastourelle.opentransit.net [193.251.128.222]
14 118 ms P12-0.BAGCR1.Bagnolet.opentransit.net [193.251.241.130]
15 115 ms P3-0.BAGCR3.Bagnolet.opentransit.net [193.251.241.110]
16 116 ms P1-0.BAGBB1.Bagnolet.opentransit.net [193.251.241.145]
17 114 ms WanadooPortails1.GW.opentransit.net [193.251.251.58]
18 119 ms [193.252.122.10]
19 115 ms [193.252.123.13]

Hoop number 3 changes often to 62.81.0.101, i doubt it can be a problem but it happens. In hop 6 there are some lost packets (5 of 100) but i think they mostly will cause lag but not a loss of con in daoc.

When my copy of SI arrives i will see if the problem persist in hat client, it can be an exceptional bug on the classic client.. who knows

 

[Jebelious]

can u get another pc and try it out ? could be the actual router etc?

 

[Vigo_Twister]

Solved

It´s soved now). Was a logic error on one of the filters of the router, was "cheking next rule" but there was not any "next rule" cuz it was the last one of a set . So it was bloking a lot of trafic that should not.

Thx for helping me)