Client won't recover from lost packets

[Steven]

I am running windows vista 32 bit. I can get in the game and even play for awhile but if at anytime i lose enough packets to start losing connection the client won't recover. I run a ping in the background it shows where I lose a few packets normally no more than 4 to 5 packets but once the packets start coming in again the client will not recover. Any idea's? (As an interm fix i can close the client and relog back in and everything works fine again but such a pain to keep having to close and reopen game in a dungeon.)

[Theboz]

Call your ISP and tell them you have a issue with your connection, Dont tell them you are playing a online game they will just put blame on that and not get anything fixed.


Do a Tracert gls.ddo.com
and post what you get on here,


if you have DSL make sure your filters on your telephone line are working or are not missing

If you have Dsl and and use wireless try to connect directlly to the router using a CAt5 cable or to the modem to see if that fixes the problem.

Also, you can go to Broadbandreports.com and navigate to their Test section and do some testing to see if and where you are having the issue. use that info to help getting your ISP to fix the problem.

[Steven]

Here is the tracert I don't believe it's a connection issue. I have run ping tests and tracerts repeatedly. It appears that for some reason the client just stop listening for packets as it still sends them but will say 0.0 recieved even if i have a ping test running in the back ground that says the connection is fine. Here is the last ping test i recieved. I have to admit starting to believe it's a vista issue as i had the same set up under xp and never had this issue.

Tracing route to gls.ddo.com [206.16.13.87]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms wl.Belkin [192.168.2.1]
2 11 ms 10 ms 7 ms 76.43.192.1
3 29 ms 9 ms 10 ms gig2-1.kscymoplat-rtr1.kc.rr.com [24.94.164.110]
4 10 ms 16 ms 10 ms so0-0-0.kscymoL3-rtr1.kc.rr.com [24.94.160.1]
5 22 ms 22 ms 20 ms so0-0-2.chcgilL3-rtr1.kc.rr.com [24.94.161.106]
6 21 ms 41 ms 22 ms xe-9-1-0.edge1.Chicago2.Level3.net [4.71.248.1]
7 21 ms 27 ms 21 ms vlan51.ebr1.Chicago2.Level3.net [4.69.138.158]
8 25 ms 22 ms 29 ms ae-6.ebr1.Chicago1.Level3.net [4.69.140.189]
9 26 ms 24 ms 24 ms ae-24-56.car4.Chicago1.Level3.net [4.68.101.168]
10 26 ms 24 ms 24 ms 192.205.33.185
11 52 ms 54 ms 56 ms tbr1.cgcil.ip.att.net [12.123.6.30]
12 58 ms 49 ms 55 ms cr1.cgcil.ip.att.net [12.122.17.137]
13 52 ms 51 ms 51 ms cr1.n54ny.ip.att.net [12.122.1.189]
14 55 ms 50 ms 52 ms cr2.n54ny.ip.att.net [12.122.2.14]
15 54 ms 52 ms 52 ms cr1.cb1ma.ip.att.net [12.122.31.126]
16 50 ms 59 ms 54 ms tbr1.cb1ma.ip.att.net [12.122.20.146]
17 51 ms 55 ms 50 ms 12.127.5.109
18 53 ms 55 ms 54 ms 12-122-254-14.attens.net [12.122.254.14]
19 61 ms 58 ms 57 ms mdf001c7613r0004-gig-12-1.bos1.attens.net [12.130.0.174]
20 56 ms 54 ms 56 ms 12.130.10.69
21 53 ms 56 ms 58 ms 206.16.13.87

Trace complete.

[Altumus]

A tracert is not going to reveal packetloss usually, try a pingplotter trace, that will show the packetlos while you're playing then you can post the picture of that (just run it while you are playing ddo then when you get the packetloss tab out and stop the pingplotter - it's a trial app you can get at pingplotter.com)