An unexpected disconnection has occured
Hi, for the past few days I've been disconnecting from the game and getting this error message. It usually happens after 5-15 minutes of play. I looked at similar threads and ran WinMTR while playing. I started it shortly before connecting to the Washington server and stopped it about a minute after I was disconnected. During this time, I had about 10 "hitches" (momentary losses of interactivity).
I would very much like to get back to playing this excellent game, and would appreciate any help with my issue. Thanks!
Spoiler
|------------------------------------------------------------------------------------------|
| WinMTR statistics | | Host - % | Sent | Recv | Best | Avrg | Wrst | Last | |------------------------------------------------|------|------|------|------|------|------| | Wireless_Broadband_Router.home - 1 | 1100 | 1097 | 0 | 2 | 51 | 1 | |lo0-100.WASHDC-VFTTP-348.verizon-gni.net - 2 | 1054 | 1040 | 3 | 17 | 1865 | 21 | | T2-9-0-8.WASHDC-LCR-21.verizon-gni.net - 2 | 1054 | 1040 | 4 | 18 | 1872 | 24 | | No response from host - 100 | 222 | 0 | 0 | 0 | 0 | 0 | | 0.ae3.BR2.IAD8.ALTER.NET - 2 | 1054 | 1040 | 5 | 20 | 1871 | 23 | | ae17.edge1.washingtondc12.level3.net - 76 | 262 | 64 | 7 | 1521 | 4982 | 4315 | | No response from host - 100 | 222 | 0 | 0 | 0 | 0 | 0 | | Destination host unreachable. - 100 | 224 | 2 | 0 | 905 | 1802 | 9 | | ae-94-94.csw4.Washington1.Level3.net - 2 | 1054 | 1040 | 6 | 20 | 1874 | 25 | | ae-4-90.edge1.Washington4.Level3.net - 2 | 1054 | 1040 | 6 | 22 | 1873 | 54 | |SOFTLAYER-T.edge1.Washington4.Level3.net - 2 | 1054 | 1040 | 6 | 21 | 1878 | 25 | | ae1.dar01.wdc01.networklayer.com - 2 | 1054 | 1040 | 7 | 21 | 1884 | 26 | | po1.fcr01.sr01.wdc01.networklayer.com - 2 | 1054 | 1040 | 7 | 21 | 1882 | 26 | | speedtest.wdc01.softlayer.com - 2 | 1054 | 1040 | 6 | 26 | 1878 | 25 | |________________________________________________|______|______|______|______|______|______| WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Butt Provider |
|
It seems to have fixed iteself.
|
|