These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

Issues, Workarounds & Localization

 
  • Topic is locked indefinitely.
 

possible fix for Closed Socket error.

First post
Author
Previous Topic Next Topic
freebree
Brutor Tribe
Minmatar Republic
#441 - 2013-01-18 18:41:40 UTC
Lando Antilles wrote:
Vaerah Vahrokha wrote:
I play EvE on 3+ computers (I have several accounts).
..........
Now, without doing *anything at all* since the last patch one of my clients (a laptop, nVidia card) gets a Closed socket error at least 10 times a day.


Maybe they'll listen to VV?

If CCP fixes this with a public explanation of what they did, I promise to:
resub 2 accts
donate several hundred mill ISK to VV's charity fund.

who else is with me?
let's commit to doing something good (PLEX for charity)
if CCP does something it should (allow their customers to play their game)

Lando


CCP is not to blame.

Look at any other MMO game forum and you will see 500+ post complaining about connection issues the last 24hours.
Check with your ISP, unless someone put a muzzle on them.
Lando Antilles
#442 - 2013-01-18 20:39:56 UTC
freebree wrote:
CCP is not to blame.

The issues here are the pervasivness of the issue, across ISPs, and after changes to the game code.

CCP did things that made many have issues they didn't have before. They can find a better way to do those things that don't contribute to disconnects.

Until they do, I will blame them.
Violent Tempest
KarmaFleet
Goonswarm Federation
#443 - 2013-01-19 08:24:02 UTC
I have recently been having the same issue. Sometimes it happens and one account drops and other times all my accounts drop at the same time. I started looking around and reading through the multiple forums and such and decided to try to do somethign a little different. After being frustrated yesterday from having my Alts booted like every 3 minutes I decided to disable Windows Firewall and install Comodo Firewall and route my DNS traffic to the Comodo DNS servers. I have been going all day today without a single disconnect. Maybe just lucky today but thought I would post anyway. I will post again if this continues to work or not. Since its a traffic issue it could be firewall related and WFW could be closing the incoming connection for some odd reason.

I do know that when CCP released the expasion prior to this one they changed their handshake method a bit. Meaning the client now said hey CCP you there, CCP says yes we are here but what is your client version, you send client version, CCP validates, if ok you log in and if not you get sent to autodownload the client update. This changed their handshake bits from 6 to 7. Because of this it changed their signature and thus it was different for a time from the signature on many providers whitelists so they were getting blocked connections. That should have been fully fixed back in 2010. However it would seem that either there is an issue with the software, a firewall compatability issue, or there are possibly still companies that have not whitelisted the new handshake signature. Just some thoughts and I will keep you all posted as to how my clients are doing after I made the changes today.
Beldaen Adoudel
Khan Exploration Society
#444 - 2013-01-19 17:10:40 UTC  |  Edited by: Beldaen Adoudel
Got DC'd three times in thirty minutes this morning. ISP is CenturyLink in Tucson, Arizona.

Tracing route to srv200-g.ccp.cc [87.237.38.200]
over a maximum of 30 hops:

2 50 ms 50 ms 50 ms tcso-dsl-gw14-206.tcso.qwest.net []
3 51 ms 52 ms * tcso-agw1.inet.qwest.net [75.160.2
4 63 ms 63 ms 61 ms lap-brdr-03.inet.qwest.net [67.14.
5 62 ms 67 ms 76 ms xe-0-1-0.mpr1.lax12.us.above.net [
6 75 ms 66 ms 63 ms xe-3-0-0.cr2.lax112.us.above.net [
7 90 ms 89 ms 89 ms xe-3-2-0.cr2.iah1.us.above.net [64
8 149 ms 116 ms 120 ms xe-2-1-0.cr2.dca2.us.above.net [64
9 188 ms 188 ms 189 ms xe-4-1-0.mpr1.lhr3.uk.above.net [6
10 188 ms 188 ms 188 ms 213-152.240-250.PXu259.above.net [0]
11 188 ms 193 ms 188 ms srv248-e.ccp.cc [87.237.36.248]
12 189 ms 190 ms 188 ms srv200-g.ccp.cc [87.237.38.200]

Pinging 87.237.38.200 with 32 bytes of data:
Reply from 87.237.38.200: bytes=32 time=191ms TTL=245
Reply from 87.237.38.200: bytes=32 time=190ms TTL=245
Reply from 87.237.38.200: bytes=32 time=193ms TTL=245
Reply from 87.237.38.200: bytes=32 time=194ms TTL=245

Ping statistics for 87.237.38.200:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 190ms, Maximum = 194ms, Average = 192ms

Pings are very consistent; never see any loss.
Jerricho Vincent
Sebiestor Tribe
Minmatar Republic
#445 - 2013-01-19 19:34:00 UTC
many times today receaved "socket has closed" error and been disconnected and unable to reconnect . lost my expencivly fitted wolf by NPC's behind enemy lines, contacted my ISP iinet Australia. Was unable to reconnect happend 5 times couldn't connect to any EVE web page but internet was still working fine for all others. It seemed to coincide with many others suffering the same issue. have read many posts and had to dissable Windows firewall to connect to eve forums. Seems issue is with handshake. I owe an appolagy to my ISP as I called them 3 times after power cycling my router 3 times and disconnecting my phone etc. have submited a patition to get my WOLF back. what a weekend ruiner!
Vaerah Vahrokha
Vahrokh Consulting
#446 - 2013-01-19 20:46:37 UTC  |  Edited by: Vaerah Vahrokha
freebree wrote:


CCP is not to blame.

Look at any other MMO game forum and you will see 500+ post complaining about connection issues the last 24hours.
Check with your ISP, unless someone put a muzzle on them.


ATM I have open: 4 EvE clients, 2 Istaria clients (another sandbox MMO), 1 GW2 client AND pondering to play WH Online as well.

As soon as I close one EvE client on this computer I am using to post and start it on the other computer (that ran EvE since 2010 with never one error) it dies with Socket Closed within 15-20 minutes.

This also happens after I reboot everything including hub and modem/router and only start 1 client on said computer. Even disabling windows firewall and antivirus.

With this behavior, It REALLY has to be my ISP. Roll


If only we were told what to use to send a petition or report.
It's pointless to send a ping / traceroute showing all it's ok including when that computer gets socket closed. There should be something else smarter, like a client trace dump about why the connection died.

EvE Online portal | EvE markets tutorials
Pihtari
Imperial Shipment
Amarr Empire
#447 - 2013-01-19 22:04:41 UTC
Not completely the ISP.

At the moment WOT (world of tanks) server is down (i need to run WOT client on the background to run eve) , i wrote a message about it before and i cant connect to it = i get socked closed in 1min when i launch eve client.
I tried to keep my "connection" open by "ping -t -l 8000 SOMEIP" but it just doesnt work.
Beldaen Adoudel
Khan Exploration Society
#448 - 2013-01-20 07:14:43 UTC
I've now realized, and added to a bug report, that most if not all of my dozen DC's today occured during session changes. Plus, it's taking an insane amount of time to dock/undock even when it doesn't time out.

So there ya go...the problem is entirely on CCP's side; proven by the fact that dozens of different players, with dozens of different ISP's all over the world are suddenly deluged during the same time frame. Fair to say, I've had more DC's in the past week than the previous six years.

Keeping the connection healthy on our side might give the servers as much leeway as possible to avoid timing out; but nothing we do will solve the problem. For me, it started exactly at the point that Dust was patched into TQ. I'll bet rl money that's not coincedence.
Violent Tempest
KarmaFleet
Goonswarm Federation
#449 - 2013-01-21 04:44:27 UTC
OK everyone I am on my second day without a single disconnect since I implemented my change on my system. That being I installed Comodo's free Firewall which turned off the Windows firewall. Also during the installation I said yes to having Comodo route my traffic to their DNS servers. So far so good. I would recommend giving it a shot and seeing if it works for you!
Marangwe
Native Freshfood
Minmatar Republic
#450 - 2013-01-21 23:01:08 UTC
I too have had Socket Closed Error messages. 2 in the last 20 minutes.

Tracing route to srv200-g.ccp.cc [87.237.38.200]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms dslrouter.westell.com [10.0.0.1]
2 12 ms 12 ms 11 ms 69-179-118-1.dyn.centurytel.net [69.179.118.1]
3 12 ms 12 ms 14 ms ge-0-0-0-0-j1-rt.pell.centurytel.net [64.91.92.4]
4 15 ms 17 ms 25 ms bb-atlngamv-jx9-01-ae4-597.core.centurytel.net [208.110.249.164]
5 17 ms 37 ms 15 ms bb-atlngamv-jx9-02-ae0.core.centurytel.net [206.51.69.66]
6 15 ms 15 ms 15 ms atx-edge-03.inet.qwest.net [65.124.11.241]
7 16 ms 16 ms 17 ms atx-brdr-01.inet.qwest.net [205.171.21.49]
8 15 ms 15 ms 16 ms te4-2-10G.ar1.ATL1.gblx.net [64.208.27.201]
9 315 ms 216 ms 210 ms te6-4-10G.ar6.LON3.gblx.net [67.16.141.137]
10 106 ms 106 ms 106 ms 204.245.39.42
11 130 ms 130 ms 130 ms srv246-f.ccp.cc [87.237.37.246]
12 127 ms 126 ms 128 ms srv200-g.ccp.cc [87.237.38.200]

Trace complete.
Dimca
Perkone
#451 - 2013-01-24 11:33:05 UTC
Dimca wrote:
Megnamon wrote:
I can play fine for 30 minutes or so, or I can be discontinued 5 seconds after logging in. Ran Pingplotter and was getting this...

Target Name: srv200-g.ccp.cc
IP: 87.237.38.200
Date/Time: 12/16/2012 7:50:03 PM to 12/16/2012 7:51:48 PM

1 3 ms 31 ms 31 ms 89 ms 18 ms 2 ms 31 ms 15 ms MyRouter.Home [xxxxxxxxxxxxxxxxxxxx]]
2 34 ms 47 ms 35 ms 92 ms 62 ms 59 ms 62 ms 43 ms h1.64.21.98.dynamic.ip.windstream.net [98.21.64.1]
3 47 ms 47 ms 47 ms 64 ms 62 ms 32 ms 62 ms 62 ms h208.246.189.173.static.ip.windstream.net [173.189.246.208]
4 55 ms 62 ms 53 ms 155 ms 53 ms 50 ms 52 ms 62 ms h178.17.213.151.static.ip.windstream.net [151.213.17.178]
5 56 ms 61 ms 46 ms 279 ms 47 ms 62 ms 43 ms 50 ms h197.189.91.75.dynamic.ip.windstream.net [75.91.189.197]
6 61 ms 62 ms 62 ms 248 ms 103 ms 62 ms 62 ms 205 ms xe-10-0-0.bar2.Cleveland1.Level3.net [4.53.194.9]
7 93 ms 62 ms 124 ms 217 ms 56 ms 48 ms 47 ms 222 ms ae-0-11.bar1.Cleveland1.Level3.net [4.69.136.185]
8 58 ms 55 ms 62 ms 186 ms 62 ms 62 ms 53 ms 392 ms ae-6-6.ebr1.Washington1.Level3.net [4.69.136.190]
9 56 ms 60 ms 62 ms 155 ms 62 ms 60 ms 62 ms 361 ms ae-8-8.ebr1.Washington12.Level3.net [4.69.143.218]
10 62 ms 60 ms 61 ms 187 ms 62 ms 62 ms 62 ms 330 ms ae-1-100.ebr2.Washington12.Level3.net [4.69.143.214]
11 76 ms 65 ms 64 ms 184 ms 93 ms 65 ms 93 ms 299 ms [4.69.148.49]
12 138 ms 129 ms 156 ms 203 ms 156 ms 156 ms 156 ms 267 ms ae-41-41.ebr2.London1.Level3.net [4.69.137.65]
13 136 ms 128 ms 135 ms 163 ms 127 ms 156 ms 156 ms 236 ms ae-56-221.csw2.London1.Level3.net [4.69.153.130]
14 141 ms 187 ms 139 ms * * * * 218 ms ae-2-52.edge4.London1.Level3.net [4.69.139.106]
15 142 ms 127 ms 156 ms 141 ms 140 ms 128 ms 130 ms 432 ms [195.50.122.214]
16 140 ms 132 ms 156 ms 130 ms 129 ms 133 ms 156 ms 401 ms srv248-e.ccp.cc [87.237.36.248]
17 136 ms 156 ms 133 ms 156 ms 140 ms 141 ms 141 ms 369 ms srv200-g.ccp.cc [87.237.38.200]

Ping statistics for srv200-g.ccp.cc
Packets: Sent = 8, Received = 8, Lost = 0 (0.0%)
Round Trip Times: Minimum = 133ms, Maximum = 369ms, Average = 171ms

Which is fairly representative of most pings. It looks like I am frequently losing packets (around 50%) in the London bounces. Anyone have any fixes to route around that area?


Same thing here. Each and every day , for two weeks already, I cannot access Eve in the period of time between 16:00 to 20:00 (EVE time). Even if I manage to enter someway - I have constant disconnects and lags. My overall internet surfing is ok, but EVE.
After some chatting with ISP tech service, they managed to route me through Frankfurt, and I could play EVE, but yesterday the route have returned and crap! same thing happens again.
Ping Plotter says, there's over 50% packet loss at node 4.49.139.106 ae-2-52.edge4.London1.Level3.net ((.
Can anyone advice smth on issue, as soon as it seems like THAT London connection is bad for capsuleers?


Here's an update on my case - I have changed my ISP and thus got rid of that traffic route via London. Flying smoothly for now, no dC's or any other problem for 2 weeks already. As I've read through last posts - there are at least 2 people posted here traceroutes leading through London.level3.net (seems to be kind of incoming European hub) - try changing your ISP guys, that should help.
Sam Korak
Doomheim
#452 - 2013-01-24 17:46:49 UTC
Lando Antilles wrote:

let's commit to doing something good (PLEX for charity)
if CCP does something it should (allow their customers to play their game)

Lando


Why not quit playing games like a 10 years old and just give all our monthly sub fees to charity instead? :P

But really now... Any progress on fixing it?
SkysLee
The Scope
Gallente Federation
#453 - 2013-01-24 20:03:31 UTC
Keep getting socket loss as well. Been getting it for 3 days now but today nonstop

Target Name: srv200-g.ccp.cc
IP: 87.237.38.200
Date/Time: 1/24/2013 1:56:16 PM to 1/24/2013 2:02:47 PM

Hop Sent Err PL% Min Max Avg Host Name / [IP]
1 157 0 0.0 0 1 0 [192.168.1.1]
2 156 156 100.0 0 0 0 [-]
3 156 133 85.3 9 25 16 crr03fdulwi-tge-0-4-0-5.fdul.wi.charter.com [96.34.20.114]
4 156 132 84.6 15 28 21 crr02euclwi-tge-0-4-0-2.eucl.wi.charter.com [96.34.17.232]
5 156 132 84.6 17 24 19 bbr02euclwi-tge-0-1-0-0.eucl.wi.charter.com [96.34.2.146]
6 156 132 84.6 24 36 29 bbr01chcgil-bue-1.chcg.il.charter.com [96.34.0.9]
7 156 132 84.6 23 51 26 chi-bb1-link.telia.net [80.239.167.89]
8 156 132 84.6 44 146 59 nyk-bb1-link.telia.net [80.91.249.109]
9 156 134 85.9 115 178 119 ldn-bb1-link.telia.net [213.248.65.89]
10 156 135 86.5 115 156 119 ldn-b3-link.telia.net [80.91.247.86]
11 156 137 87.8 115 118 116 eveonline-ic-138015-ldn-b3.c.telia.net [213.248.83.198]
12 156 136 87.2 115 118 116 srv250-f.ccp.cc [87.237.37.250]
13 156 133 85.3 115 168 118 srv200-g.ccp.cc [87.237.38.200]

Hope this helps
DEALING DEL
Call-2-Power
#454 - 2013-01-24 20:37:33 UTC
Same problem

Location = UK

ISP = BT (infinity)

is it possible the ports you may have changed conflict with the ports that the ISP put a limit on as there used by popular P2P file sharing programs??

i have played other games where the software company's did this.
magikalcoffee
Garoun Investment Bank
Gallente Federation
#455 - 2013-01-24 20:50:54 UTC  |  Edited by: magikalcoffee
i have started getting this error today, it started off as occasionally and now it happens every time i log in, i cant even log in via the website to file a petition, and am having issues connecting to all ccp websites,


ye sorry im based in the uk and am using bt infinity with 75 meg connection
Deros
Black Omega Security
Minmatar Fleet Alliance
#456 - 2013-01-24 21:03:53 UTC
DEALING DEL wrote:
Same problem

Location = UK

ISP = BT (infinity)


Same issue started today.

Internet is fine, been streaming football all night, and other sites/apps/games work fine.
Banjo String
Steel Winters Stellar Enterprises
#457 - 2013-01-24 21:06:56 UTC
Deros wrote:
DEALING DEL wrote:
Same problem

Location = UK

ISP = BT (infinity)


Same issue started today.

Internet is fine, been streaming football all night, and other sites/apps/games work fine.





Same here, minus the football.

Maidenhead UK
magikalcoffee
Garoun Investment Bank
Gallente Federation
#458 - 2013-01-24 21:08:32 UTC
Beldaen Adoudel wrote:
I've now realized, and added to a bug report, that most if not all of my dozen DC's today occured during session changes. Plus, it's taking an insane amount of time to dock/undock even when it doesn't time out.

So there ya go...the problem is entirely on CCP's side; proven by the fact that dozens of different players, with dozens of different ISP's all over the world are suddenly deluged during the same time frame. Fair to say, I've had more DC's in the past week than the previous six years.

Keeping the connection healthy on our side might give the servers as much leeway as possible to avoid timing out; but nothing we do will solve the problem. For me, it started exactly at the point that Dust was patched into TQ. I'll bet rl money that's not coincedence.





ye was thinking the same thing myself that this was tied into the dust patch
Blue Absinthe
Wardec U
#459 - 2013-01-24 21:16:15 UTC
i started playing 3 days ago and this suddenly started happening today, i can't play more than a couple of minutes without a disconnect.

i hope they fix it or else i'm definitely won't be playing eve. an easy choice for new players with not a lot of time sunk into it (it's a shame though, was really enjoying the game).
Danny Centauri
Republic University
Minmatar Republic
#460 - 2013-01-24 21:18:53 UTC  |  Edited by: Danny Centauri
Same problem here today, both my Dust and EVE keep dying painful death, EVE disconnects a few mins after login (when it lets me), forums are slow and unresponsive for both EVE and Dust.

ISP: BT (Infinity)
Location: England - Sheffield
Speedtest: 41Mbps down 11Mbps up 22ms ping (worst results)

Everything other than EVE and Dust is working Youtube, TS the works... anything other than what I want to be doing.

Being honest this is beyond ridiculous now, an intermittant problem thats been going on for a small small minority of players for over a year.

EVE Manufacturing Guide - Simple guides to manufacturing in EVE for both beginners and more experienced players.