Cleaning up old connection is back

[Adro]

Stuck logging in at cleaning up old connection with 0.01 kb/s after I got stuck in a loading screen for a long time recalling from gianthold ruins to gianthold on the Thelanis server. Character name Affliction.

[Adro]

after waiting 15minutes or so I can now log in again.... I REALLY HOPE THIS DOES NOT BECOME A TREND. I've heard of plenty of people leaving over the lag, this would be a bad development.

[arminius]

I have the same thing now, hours spent on trying to do Ghola Fan and Shrieking Mines and not even making it into the quests. When I and my teammates bail, we get Cleaning up Old Connection.

On Fern- , er, Ghallanda.

_

[Altumus]

I'm sorry you were experiencing an issue but often times getting disconnected can be because of other network issues as well. Unfortunately thats all we can trouble shoot via the forums. When you experiene lag or other issues you may want to try first doing a tracert to gls.ddo.com and posting the results here. Also check your firewall and router configs.

Thanks.

[arminius]

I'm sorry you were experiencing an issue but often times getting disconnected can be because of other network issues as well. Unfortunately thats all we can trouble shoot via the forums. When you experiene lag or other issues you may want to try first doing a tracert to gls.ddo.com and posting the results here. Also check your firewall and router configs.

Thanks.

Thanks for the tracert address. Clearly, tho, for a party of random people located all over the country, local configs don't affect the results if they are all experiencing the exact same problem.

The strangest thing about these problems were that they were so specific to the Restless Isles. Guildies not in the Restless Isles had no problem. Guildies who came to the Restless Isles to see what was going on and help us troubleshoot got the same problem.

The same players eventually abandoned the Restless Isles after hours of trying, and then had no problems at all in the Gianthold. Odd.

_

[miceelf88]

This same thing just happened to my party as well. On Restless Isles.

We spent about an hour logging and re-logging, trying to get into ghola fan. We gave up, recalled, got stuck in loading screens, and now I am stuck on "cleaning up old connection."

Lovely.

[Altumus]

If you are able, please log onto another server and contact ingame support, they should be able to assist you.

[miceelf88]

Eventually, it went away. Only took about 40 minutes.

But honestly, is there a plan to fix the buggy restless isles thing? About half the time, no more than two members of the party could enter the area with the quest givers. And those two members who COULD enter, entered a completely empty area. No quest giver, no villagers, nothing. Just an empty village and the shrines.

[JXS]

tried entering sorrowdusk island and got stuck.
tried recalling and got stuck on the load screen.
alt+f4 the game and tried reloading and got stuck with "cleaning up old connection"

heres my trace results

Host Name IP Address Hop Ping Time Ping Avg % Loss Pkts r/s Ping best/worst
* Unknown Host * 192.168.1.1 1 1ms 0ms 0% 4 / 4 0ms / 1ms
* Unknown Host * 10.177.56.1 2 9ms 100% 0 / 4
gw01.ajax.phub.net.cable.rogers.c66.185.90.33 3 10ms 10ms 0% 4 / 4 7ms / 13ms
gw01.ajax.phub.net.cable.rogers.c66.185.81.197 4 8ms 100% 0 / 4
so-4-2-0.gw02.mtnk.phub.net.cable66.185.81.133 5 8ms 100% 0 / 4
gw02.bloor.phub.net.cable.rogers.66.185.80.9 6 10ms 100% 0 / 4
pos-1-0-0.igw01.vaash.phub.net.ca66.185.80.190 7 26ms 100% 0 / 4
POS2-1.ar2.DCA3.gblx.net 208.51.239.201 8 28ms 32ms 0% 4 / 4 28ms / 45ms
* Unknown Host * 192.205.34.109 9 32ms 35ms 0% 4 / 4 32ms / 40ms
tbr2.wswdc.ip.att.net 12.122.80.18 10 46ms 100% 0 / 4
cr2.wswdc.ip.att.net 12.122.16.109 11 42ms 100% 0 / 4
cr2.n54ny.ip.att.net 12.122.3.37 12 43ms 100% 0 / 4
* Unknown Host * 12.122.16.214 13 55ms 100% 0 / 4
tbr1.cb1ma.ip.att.net 12.122.10.21 14 54ms 100% 0 / 3
* Unknown Host * 12.127.5.109 15 44ms 100% 0 / 3
12-122-254-14.attens.net 12.122.254.14 16 42ms 100% 0 / 3
mdf001c7613r0004-gig-12-1.bos1.at12.130.0.174 17 40ms 45ms 0% 3 / 3 40ms / 55ms
* Unknown Host * 12.130.10.69 18 44ms 44ms 0% 3 / 3 44ms / 44ms
* Unknown Host * 206.16.13.87 19 46ms 47ms 0% 3 / 3 43ms / 52ms

[DZX]

I REALLY HOPE THIS DOES NOT BECOME A TREND.

It's becoming a trend, a really annoying trend.

[FoeHammer]

This is the 3rd or 4th thread detailing a very similar issue. I also doubt that this is a local\individual server\ISP issue.

Here is my traclet results:

1 2ms <1ms <1ms 192.168.1.1
2 * * * request timed out
3 * * * request timed out
etc
repeats 'request timed out' all the way to
30


I have no other internet issues or problems with connections or issues with online games. I can 'ping' gls.ddo.com and get a reply forever without a missed or timed out request.

[Kerrn_Siff]

I just got this in GH now on Sarlona Serlona.. whatever.

[Schmackdown]

Just got it on Argo out of GH. I can log in to Ghallanda, but not Argonnessen. I highly doubt it is a network issue.

Regardless:

4 14 ms 14 ms 15 ms ge-4-1-166.ipcolo1.Chicago1.Level3.net [166.90.7
3.81]
5 14 ms 15 ms 15 ms ae-14-51.car4.Chicago1.Level3.net [4.68.101.8]
6 14 ms 15 ms 14 ms ggr2-p3110.cgcil.ip.att.net [192.205.33.185]
7 49 ms 45 ms 44 ms tbr2.cgcil.ip.att.net [12.123.6.38]
8 46 ms 45 ms 45 ms tbr2.cb1ma.ip.att.net [12.122.10.105]
9 46 ms 45 ms 45 ms 12.127.5.89
10 48 ms 45 ms 45 ms 12-122-254-14.attens.net [12.122.254.14]
11 47 ms 44 ms 46 ms mdf001c7613r0003-gig-10-1.bos1.attens.net [12.13
0.0.170]
12 43 ms 46 ms 45 ms 12.130.10.69
13 54 ms 87 ms 103 ms 206.16.13.87

Trace complete.

[maddong]

I think it is a buggy instance thing.

It happens when you are somewhere like restless isles, threnal, or sorrowdusk. You get so that when you reenter the instance from the Inn you are lagged out, but others already in the instance are fine. Everyone that comes into the instance then gets lagged out.

I've been able to recall out and come back in and get lagged out again. We fixed it by disbanding and regrouping with everyone out of the instance to create a new instance.

I got the cleaning up old connection when I lagged out on a loading screen trying to recall out to do this. I disconnected and then got stuck on the cleaning up old connection bit.

[Karch]

The cause of this is network corruption. When your character enters an instance, information is passed from one server to another, and then syncs with your computer. If there is packet loss in your DNS table leading to your computer, corruption can occur. If the packet loss is bad enough, our servers will not be able to recover immediately. That's when you find yourself disconnected, and our servers automatically clean up the connection and reset you to the last known "good" location.

Sometimes the packet loss isn't caused by a bad network, but is because of ISP "features" such as traffic shaping or packet shaping. Essentially, this puts your gaming connection at a lower priority than other things. This isn't always the case, and can also be caused by the client computer being overworked (turning down detail levels can help, if that's the problem) while loading the new instance and syncing with the server. Also, it can be because of a router feature called SPI or certain Internet Security Suits (though this is rare). A tracert from everyone affected would really help a lot to determine the cause, because we can check on certain DNS tables to see if any servers have been reporting packet loss.

One last note: if a member cannot connect to the other members in the group (for the previously mentioned reasons), that can cause every other member of the group to experience the same problem until that member drops their connection and is removed from the group.

[maddong]

Why is it that someone may be in the instance fine. But then one person enters the instance and cannot move/is lagged. Every single person entering after him is lagged out. But the person that is in there already is fine. I've had whole groups lock up that way.

And everyone that hasn't entered the instance yet is fine.

The cleaning up old connections needs to be a lot faster so that if we disconnect we can get right into the party instead of waiting 30 minutes.

???

[Katrina]

Happened to me tonight

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

1 * * * Request timed out.
2 12 ms 35 ms 22 ms rd1so-ge3-0-0-2.cg.shawcable.net [64.59.142.82]

3 24 ms 24 ms 35 ms rc1so-ge6-0.cg.shawcable.net [66.163.71.129]
4 43 ms 52 ms 45 ms rc1wh-pos12-0.vc.shawcable.net [66.163.76.10]
5 37 ms 41 ms 47 ms rc1wt-pos1-0-0.wa.shawcable.net [66.163.76.2]
6 39 ms 50 ms 42 ms sl-gw12-sea-1-0.sprintlink.net [144.228.93.149]

7 54 ms 45 ms 46 ms sl-bb21-sea-4-0-0.sprintlink.net [144.232.6.123]

8 89 ms 74 ms 71 ms sprint-gw.st6wa.ip.att.net [192.205.32.173]
9 107 ms 116 ms 105 ms tbr2.st6wa.ip.att.net [12.127.6.173]
10 87 ms 88 ms 98 ms tbr2.cgcil.ip.att.net [12.122.10.61]
11 91 ms 103 ms 94 ms tbr2.cb1ma.ip.att.net [12.122.10.105]
12 95 ms 112 ms 98 ms 12.127.5.97
13 101 ms 96 ms 89 ms 12-122-254-14.attens.net [12.122.254.14]
14 311 ms 234 ms 215 ms mdf001c7613r0004-gig-12-1.bos1.attens.net [12.13
0.0.174]
15 102 ms 101 ms 94 ms 12.130.10.69
16 95 ms 93 ms 90 ms 206.16.13.87

Trace complete.

[Renegade444]

and another one, this time GH on Khyber.... took 15 minutes to clear up connection. Very annoying. Lost my party because of it.

[taangle]

The cause of this is network corruption. When your character enters an instance, information is passed from one server to another, and then syncs with your computer. If there is packet loss in your DNS table leading to your computer, corruption can occur. If the packet loss is bad enough, our servers will not be able to recover immediately. That's when you find yourself disconnected, and our servers automatically clean up the connection and reset you to the last known "good" location.

Sometimes the packet loss isn't caused by a bad network, but is because of ISP "features" such as traffic shaping or packet shaping. Essentially, this puts your gaming connection at a lower priority than other things. This isn't always the case, and can also be caused by the client computer being overworked (turning down detail levels can help, if that's the problem) while loading the new instance and syncing with the server. Also, it can be because of a router feature called SPI or certain Internet Security Suits (though this is rare). A tracert from everyone affected would really help a lot to determine the cause, because we can check on certain DNS tables to see if any servers have been reporting packet loss.

One last note: if a member cannot connect to the other members in the group (for the previously mentioned reasons), that can cause every other member of the group to experience the same problem until that member drops their connection and is removed from the group.

Funny it is never their fault. I have the same problem and here is my tracert.

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

1 <1 ms <1 ms <1 ms 192.168.0.254
2 58 ms 45 ms 43 ms oh-67-76-159-129.sta.embarqhsd.net [67.76.159.129]
3 41 ms 41 ms 40 ms crohmnfd01 [69.34.30.245]
4 49 ms 49 ms 51 ms sl-gw31-chi-4-1.sprintlink.net [160.81.42.5]
5 49 ms 50 ms 49 ms sl-bb21-chi-4-0.sprintlink.net [144.232.26.29]
6 49 ms 50 ms 49 ms sl-bb22-chi-15-0.sprintlink.net [144.232.26.97]
7 50 ms 50 ms 50 ms sl-st21-chi-13-0-0.sprintlink.net [144.232.20.91]
8 50 ms 52 ms 50 ms ggr3-p330.cgcil.ip.att.net [192.205.33.157]
9 77 ms 78 ms 77 ms tbr2.cgcil.ip.att.net [12.122.86.138]
10 77 ms 77 ms 80 ms tbr2.cb1ma.ip.att.net [12.122.10.105]
11 76 ms 75 ms 76 ms 12.127.5.89
12 76 ms 76 ms 76 ms 12-122-254-14.attens.net [12.122.254.14]
13 76 ms 77 ms 75 ms mdf001c7613r0004-gig-12-1.bos1.attens.net [12.130.0.174]
14 76 ms 76 ms 76 ms 12.130.10.69
15 77 ms 77 ms 77 ms 206.16.13.87

Trace complete.

[DZX]

I think it is a buggy instance thing.

It happens when you are somewhere like restless isles, threnal, or sorrowdusk. You get so that when you reenter the instance from the Inn you are lagged out, but others already in the instance are fine. Everyone that comes into the instance then gets lagged out.

I've been able to recall out and come back in and get lagged out again. We fixed it by disbanding and regrouping with everyone out of the instance to create a new instance.

I got the cleaning up old connection when I lagged out on a loading screen trying to recall out to do this. I disconnected and then got stuck on the cleaning up old connection bit.

I will have to agree that I believe this is in fact a buggy instance thing. The instance of Threnal I was in tonight was completely messed up. 5-6 of the encounters were just not there. Then when a guild friend of mine zoned in he got the load screen of doom and then the cleaning error.

Last week when I reported this problem the instance we were in was messed up as well. There is clearly something wrong on your side Turbine. Maybe issues on our side are making a smaller issue worse, but whatever is going on here is not all because of problems on the customers side.