Client keeps disconnecting (An unexpected disconnection has occured)
|
I keep getting kicked to the login screen after being in game for anywhere between 1 second and ~ 1 minute. I am not on a wireless network. I have a stable internet connection which works just fine with any other game. I have played PoE since Open Beta with no issues on this computer. My other computer (laptop) has had this issue since Open Beta and it is connected to the same network. The problem started happening on my current computer (desktop) right after patch 1.0.0 released.
I read this from the sticky: At random intervals This is a problem with your connection to our servers. Try changing your Gateway between America, Europe and Singapore. If all three are still resulting in disconnects, you’ll likely have to check the state of your router and contact your ISP about your connection problems. But I know it is NOT my ISP that is the problem. This has only started happening after the 1.0.0 patch. It has never happened before. I have contacted my ISP and they say the connection is fine. Anything else I can do here?? EDIT 1: Similar issues reported by other players courtesy of MeCarana: " My WinMTR " EDIT 2: Just wanted to post an update to anyone watching this thread. Using the Steam version which allows me to pick the Gateway, I said F it and tried Europe instead of America gateway and I managed to stay in-game for about 5 minutes! :D It's not much but it's much more than before (1-60 seconds). Managed to actually level my Scion to level 3 lol... Oh well, I was hoping it'd be a permanent fix but it looks like it still disconnects on the EU gateway, just takes a tiny bit longer. EDIT 3: Okay so I tested all four gateways. On Europe I consistently stay connected for 1-3 minutes. On America, Singapore and Australia, less than one minute. This is very interesting... If we could figure out what the difference is between these connections maybe the root cause can be identified? Last edited by Shmez#2963 on Oct 25, 2013, 5:51:26 PM
|
|
|
Bump. Any help for this would be greatly appreciated. I've been playing since OB and now I can't even play for 20 seconds without a crash. Still on level 2 with scion... Looks like it's getting nowhere. :(
|
|
|
Bump...
|
|
|
Bump
|
|
|
Yeah, I'm having the same problem. Ever since 1.0.0c patch.
I played all day just fine till that patch hit, now I can't stay connected for more than 10 min. Doesn't have to be combat or specific to anything in particular. Hell, I was even trying to get some stuff in the micro transactions window when I got dropped. Wasn't able to buy anything. Curious that we seam to be the only ones experiencing this. I'll try video drivers... |
|
|
Well, I updated my Video Drivers, NVIDIA 314.22 to 331.58, and nothing.
Still can't stay connected. |
|
|
Yeah. I actually experience the same issue on my laptop, but that has been going on since Open Beta. I posted the problem here and people said it must be an ISP issue. That doesn't make sense since the laptop is connected to the same network as the desktop. No matter, the desktop played it just fine... until patch 1.0.0.
Now neither of them work. I've tried contacting ISP (they report no packet loss issues). I've tried reintsalling the game. I've tried running it through steam. No fix in sight. :( |
|
|
Please post a WinMTR trace that is capturing when you get disconnected.
Instructions for the WinMTR can be found in the Consolidated Technical sticky post. |
|
|
|------------------------------------------------------------------------------------------|
| WinMTR statistics | | Host - % | Sent | Recv | Best | Avrg | Wrst | Last | |------------------------------------------------|------|------|------|------|------|------| | 192.168.10.1 - 0 | 89 | 89 | 0 | 0 | 0 | 0 | | No response from host - 0 | 89 | 89 | 3 | 9 | 19 | 7 | | ip68-100-3-129.dc.dc.cox.net - 0 | 89 | 89 | 5 | 10 | 19 | 9 | | ip68-100-2-33.dc.dc.cox.net - 0 | 89 | 89 | 5 | 10 | 20 | 9 | | mrfddsrj01gex070003.rd.dc.cox.net - 0 | 89 | 89 | 5 | 11 | 56 | 10 | | 68.1.4.133 - 0 | 89 | 89 | 6 | 13 | 61 | 10 | |xe-1-0-2.bbr02.eq01.wdc02.networklayer.com - 0 | 89 | 89 | 7 | 12 | 51 | 9 | | ae7.bbr01.eq01.wdc02.networklayer.com - 0 | 89 | 89 | 7 | 12 | 36 | 11 | | ae0.bbr01.tl01.atl01.networklayer.com - 6 | 69 | 65 | 0 | 22 | 26 | 21 | | ae13.bbr02.eq01.dal03.networklayer.com - 0 | 89 | 89 | 42 | 58 | 142 | 44 | | ae1.dar02.sr01.dal01.networklayer.com - 0 | 89 | 89 | 43 | 47 | 79 | 46 | | po2.fcr05.sr06.dal01.networklayer.com - 0 | 88 | 88 | 41 | 44 | 79 | 43 | |173.192.44.22-static.reverse.softlayer.com - 0 | 89 | 89 | 43 | 47 | 56 | 48 | |________________________________________________|______|______|______|______|______|______| WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider I've done this before. Was told it was an ISP issue. Unfortunately I know it's not an ISP issue :( Last edited by Shmez#2963 on Oct 24, 2013, 1:07:29 PM
|
|
" In this case, it is not an ISP issue (or doesn't seem to be). You're not getting any latency or packet loss of worry in your ISP section of the trace. There's a bit of packet loss in the networklayer side of things between DC and Atlanta... Not sure if that's causing your problem or not though. I'll pass along the packet loss to support staff so they can get it looked into just in case. |
|
