I turned off VPN to test and was disconnected 10 minutes into the game. VPN fixes the problem, at least for me.

VPN should not fix your problem, the problem is with CCP.....dont patch things up for them.

VPN should not fix your problem, the problem is with CCP.....dont patch things up for them.

I set up a VPN to the UK since im from the states. so far, i haven't gotten disconnected yet.

Hi guys sorry I've posted this in another thread but I am having the exact same issue
Location: New Zealand
ISP: slingshot

I don't have any packet loss when it happens for me. ping -t was this at all times from log in to "Socket was closed":
Reply from 87.237.38.200: bytes=32 time=301ms TTL=108

and tracert was this:

2 11 ms 11 ms 11 ms cpiak1-l9-G-internet.tranzpeer.net [202.180.81.32]
3 12 ms 10 ms 11 ms vlan93-cpcak3-e1.tranzpeer.net [202.180.76.68]
4 11 ms 11 ms 10 ms vlan7-cpcak3-s1.tranzpeer.net [202.180.81.49]
5 44 ms 11 ms 12 ms x7-1-0-101.akbr5.global-gateway.net.nz [202.50.234.61]
6 12 ms 11 ms 12 ms ae1-2.akbr4.global-gateway.net.nz [202.50.232.77]
7 12 ms 12 ms 11 ms ae1-10.tkbr9.global-gateway.net.nz [202.50.232.37]
8 135 ms 142 ms 136 ms xe7-0-0.labr5.global-gateway.net.nz [202.50.232.18]
9 168 ms 167 ms 173 ms ae1-3.sjbr2.global-gateway.net.nz [203.96.120.94]
10 167 ms 169 ms 149 ms ae0.pabr4.global-gateway.net.nz [203.96.120.74]
11 169 ms 168 ms 138 ms vlan60.csw1.SanJose1.Level3.net [4.69.152.62]
12 146 ms 147 ms 149 ms vlan60.csw1.SanJose1.Level3.net [4.69.152.62]
13 141 ms 141 ms 211 ms ae-2-2.ebr2.NewYork1.Level3.net [4.69.135.186]
14 208 ms 211 ms 205 ms ae-92-92.csw4.NewYork1.Level3.net [4.69.148.46]
15 220 ms 209 ms 212 ms ae-92-92.csw4.NewYork1.Level3.net [4.69.148.46]
16 274 ms 208 ms 208 ms ae-91-91.ebr1.NewYork1.Level3.net [4.69.134.77]
17 285 ms 278 ms 284 ms ae-56-221.csw2.London1.Level3.net [4.69.153.130]
18 274 ms 273 ms 278 ms ae-56-221.csw2.London1.Level3.net [4.69.153.130]
19 * 273 ms 277 ms ae-2-52.edge4.London1.Level3.net [4.69.139.106]
20 278 ms 283 ms 302 ms srv248-e.ccp.cc [87.237.36.248]
21 305 ms 311 ms 307 ms srv248-e.ccp.cc [87.237.36.248]
22 307 ms 302 ms 312 ms srv200-g.ccp.cc [87.237.38.200]

hope this helps..

will throw my hat in the ring here, since Inferno i have had 8 disconnects for a closed socket, prior to inferno i never even knew this window existed. And now i get disconnected and oddly get 2 popups at the same time for the error every time lol

I was also having this issue. I tried restarting my laptop, modem, and router, none of that helped. I realized I began having the problem after I started using steam. I opened task manager and steam was running in the background. Ended that process and havent had the error since.

Can somebody else verify that Steam is causing Close Socket errors?

If VPN is fixing the problem then it sounds like the issue is ISP based. I have asked those who submitted bug reports on this issue to confirm their location and ISP but neither of them have gotten back to me yet. If others experiencing the problem can do likewise it will help us confirm one way or the other.

I never had the problem. Now the game is unplayable, it crashes continuously, I never get more than 30 minutes between crashes. Steam or anything else I have tried makes no difference.

Can somebody else verify that Steam is causing Close Socket errors?

I get a socket closed about 3 or 4 times an hour, its cost me a fortune in lost drones and the occasional ship - which CCP wont reimburse.

Thank you Sione Tolutau.

I wanted to highlight your post to show people which information they should include in their petitions about the socket closed issue. Having all this information makes it a lot easier for us to figure out who, in this long trace, is responsible for dropping the ball/package.

PS. You might not see the package loss via ping -t if only packages within specific port rages get dropped.

I have the same "Connection Lost" "The Socket was closed" Problem.

It all started after the Installation of the Inferno Patch.
All Workarounds (closing Steam, etc ... ) wont work.

As long as i do/clcik smth i am fine. but the moment i went "afk", it closes my Client.


A Hotfix for it would be quite nice, cause its non playable the way it is atm!

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Def_Monk>tracert 87.237.38.200

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

1 1 ms 1 ms 1 ms Vlan206.cc.stevens-tech.edu [155.246.70.1]
2 * * * Request timed out.
3 1 ms 1 ms 1 ms ge-8-37.car1.Newark1.Level3.net [4.28.0.173]
4 12 ms 1 ms 1 ms ae-31-51.ebr1.Newark1.Level3.net [4.69.156.30]
5 1 ms 1 ms 2 ms ae-2-2.ebr1.NewYork1.Level3.net [4.69.132.97]
6 70 ms 70 ms 70 ms ae-42-42.ebr2.London1.Level3.net [4.69.137.69]
7 79 ms 74 ms 74 ms ae-58-223.csw2.London1.Level3.net [4.69.153.138]
8 70 ms 70 ms 70 ms ae-2-52.edge4.London1.Level3.net [4.69.139.106]
9 70 ms 70 ms 70 ms 195.50.122.214
10 70 ms 71 ms 70 ms srv248-e.ccp.cc [87.237.36.248]
11 70 ms 70 ms 72 ms srv200-g.ccp.cc [87.237.38.200]

Trace complete.

C:\Users\Def_Monk>tracert 87.237.38.200

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

1 2 ms 1 ms 2 ms Vlan206.cc.stevens-tech.edu [155.246.70.1]
2 * * * Request timed out.
3 35 ms 3 ms 28 ms ge-8-37.car1.Newark1.Level3.net [4.28.0.173]
4 1 ms 1 ms 12 ms ae-31-51.ebr1.Newark1.Level3.net [4.69.156.30]
5 1 ms 1 ms 3 ms ae-2-2.ebr1.NewYork1.Level3.net [4.69.132.97]
6 71 ms 70 ms 70 ms ae-42-42.ebr2.London1.Level3.net [4.69.137.69]
7 70 ms 70 ms 72 ms ae-58-223.csw2.London1.Level3.net [4.69.153.138]
8 * 70 ms 70 ms ae-2-52.edge4.London1.Level3.net [4.69.139.106]
9 70 ms 70 ms 70 ms 195.50.122.214
10 70 ms 70 ms 70 ms srv248-e.ccp.cc [87.237.36.248]
11 70 ms 70 ms 70 ms srv200-g.ccp.cc [87.237.38.200]

Trace complete.

C:\Users\Def_Monk>tracert google.com

Tracing route to google.com [173.194.43.14]
over a maximum of 30 hops:

1 3 ms 2 ms 3 ms Vlan206.cc.stevens-tech.edu [155.246.70.1]
2 * * * Request timed out.
3 1 ms 1 ms 1 ms ge-8-37.car1.Newark1.Level3.net [4.28.0.173]
4 7 ms 1 ms 1 ms ae-31-51.ebr1.Newark1.Level3.net [4.69.156.30]
5 2 ms 3 ms 1 ms ae-2-2.ebr1.NewYork1.Level3.net [4.69.132.97]
6 1 ms 1 ms 2 ms ae-81-81.csw3.NewYork1.Level3.net [4.69.134.74]
7 1 ms 1 ms 1 ms ae-3-80.edge1.NewYork1.Level3.net [4.69.155.142]
8 1 ms 1 ms 1 ms GOOGLE-INC.edge1.NewYork1.Level3.net [4.71.172.86]
9 2 ms 1 ms 2 ms 209.85.255.68
10 2 ms 2 ms 2 ms 72.14.237.252
11 1 ms 1 ms 1 ms lga15s34-in-f14.1e100.net [173.194.43.14]

Trace complete.

C:\Users\Def_Monk>

Thanks for the info about doing something (clicking) that keeps it working for you.

I'm testing a mouse mover utility and so far have received no socket closed dialog boxes for the past 3 hours even though my ship is sitting cloaked in a safe spot and I haven't touched the mouse or keyboard during this period. Normally it would give a socket closed error between a few minutes to an hour max.
The mouse mover just moves the mouse to a random position every 10 seconds although perhaps a minute or more might work.

This fix, if it works, won't be to everyone's liking. I'm often mining and have to interact with the ship at least every 6 minutes or the mining lasers stop working. Anyhow I'm going to keep this test on overnight to see if it works.

Will be great when a fix comes out because these socket closed errors are making Eve unplayable.

I'm not sure if socket closed errors occur when docked?

Well my idea didn't seem to work as Socket Closes seem connected with actual in-world activity and not with lack of activity.

Mouse mover kept client alive with no Socket Closes for over 12 hours.
I then tried to let client sit for 25 minutes with no KB or mouse interaction at all - result was no Socket Closes.
Next decided to try some mining but with out mouse mover - result after 40 minutes Socket Close !!!

Fri, 2012-06-29 21:32:21 - TCP packet - Source: 87.237.38.200 - Destination: xxx.xxx.xxx.xxx - [Invalid sequence number received with Reset, dropping packet Src 26000 Dst 2506 from WAN]

I used to get multiple game freezes (lost a scimi, petition returned no issues found....) now I get game disconnects with the socket closed.
Never had this issue until Inferno, I cannot believe that the game just magically starts screwing up since certain patches were implemented.
I am not tech minded so have no idea what half of you are babbling on about, can someone from ccp give us a plain answer as to what they are going to do about it (if anything).

See if this helps at all. It was picked up from an old EVE forum post.

I've been crashing too, but it's happened a lot less frequently after doing this.

"In Windows press the Windows button + R and in the command window type cmd and press enter

In the terminal window type "netsh winsock reset catalog" without the "

This will reset your Winsock protocols and prompt you to restart your computer, after you've restarted see if you are able to connect to EVE again. "

it's still happening.

Already lost one ship to this, which was petitioned and rejected.

Hello guys, i may discovered something interesting here.

The problem occurs when I'm logged in eve, and my girlfriend access the internet on her iPhone on the same wi-fi. Every time she try to download any page or content, the "socket was closed" problem happens.

im not joking, every time she does that. Eve crash.

Actually you might be on to something, most of the time I get the socket closed error message is when I'm looking something up on the browser not associated with Eve. I'll try to stop to see if that helps.. though still only most of the time seems to happen when viewing another web page, but still some of the times it just happens when I'm warping somewhere, or otherwise in game not using anything else outside of the game and no one else using my router for internet access. So, this might be a quick fix, I don't believe it is the overall problem. But still great advice and will try it out :)

Hello guys, i may discovered something interesting here.

The problem occurs when I'm logged in eve, and my girlfriend access the internet on her iPhone on the same wi-fi. Every time she try to download any page or content, the "socket was closed" problem happens.

im not joking, every time she does that. Eve crash.

I think I have identified the problem at my end. As soon as I bypass the Wi-Fi router (usually have a cable from one of it's ports) and plugged in my modem directly, the problem disappeared.

My theory:.... *leave TS on*....

I'm only 50% sure about this, but I believe internet sockets close automatically after being idle for a predefined time span. By being idle I mean that the socket isn't transferring any data. Could it be this simple, that unless you actively click or interact with the game every now and then, the sockets would close automatically?...

Confirming I have closed sockets about every 5 minutes since today
(and probably up to 4 days back as I have been offline those days.)

My ping tracer is fine, my internet connection is stable, and this is a
clean system which runs Eve and Eve alone (okay, Teamspeak and
Mumble, too)

CCP must realize that it is their software that is bugged.
Please dont send us talking to our ISPs, thank you.

I have found that while playing eve if i make a connection to the internet via web browser, itunes, windows update etc i will get the double window error within a minute. I did 10 attempts of being connected to eve would open a browser go to Google (in game browser and out of game browser produced the same outcome) Search for anything look back in the eve window to find socket error 9/10 times.

-½ SpeedGuide.net TCP Analyzer Results -+
Tested on: 2012.07.16 16:31
IP address: 94.134.xx.xxx
Client OS/browser: Windows 7 (Firefox 13.0.1)

TCP options string: 020405ac0103030301010402
MSS: 1452
MTU: 1492
TCP Window: 522720 (multiple of MSS)
RWIN Scaling: 3 bits (2^3=8)
Unscaled RWIN : 65340
Recommended RWINs: 63888, 127776, 255552, 511104, 1022208
BDP limit (200ms): 20909kbps (2614KBytes/s)
BDP limit (500ms): 8364kbps (1045KBytes/s)
MTU Discovery: ON
TTL: 52
Timestamps: OFF
SACKs: ON
IP ToS: 00000000 (0)

I've been playing in my laptop for months, without a SINGLE disconnect, through my wifi router.

Yesterday, I started experiencing Closed socket errors and double pop-up closed socket errors.

I checked that:

-Broadband was working properly. I could fire up a browser, and Team Speak would not close at all. It was just EvE failing and falling.
-I got disconnected several times in 1 hour and a half, with two closed socket errors in 15 minutes.
-I am completely SURE that there was nothing running on the computer but EvE and Team Speak. No browser, no other programs but Avast and such.
-I do not have Steam installed.
-I was actively playing: moving, warping, activating modules, etc.
-I only had ONE client open.

I am a bit pissed off because I lost my connection when I was hugging a 0.0 gate in my Hurricane, and while I frantically tried to relog in, a Talos landed on top of me and I enjoyed quite a few awesome seconds of my fleet pals narrating how my Hurri was being manhandled by the Talos at point blank.

I did not lose the ship, but it was VERY, VERY close. I cannot risk it in these conditions.

The only things I can think they're causing this would be:

-The last TS3 update from yesterday.
-A problem within EvE itself.
-Avast antivirus or something?

I have absolutely zero computer expertise, so in order to provide info after a closed socket, please let me know to create a tracert report.

I think that you can rule out 1 and 3. A lot of people seems to have had this problem for months now and considering that I doubt it is any specific software that causes it.

I had this tonight again after having been able to play for two days with no problems. Now it's back and I could literally not play. After the first disconnect I couldn't dock because it closed again just as the warping back was finished.

The window for the disconnect is new with Inferno - before Inferno your client restarted automatically after being disconnected (without giving a reason on what happened). Getting 2 popups at the same time might be a (minor) bug - please make a screenshot the next time this happens and attach it to a bugreport (please add my name in the subject of the bugreport).

I had these socket losses too a few days ago after reinstalling windows...

But after deactivating the windows 7 firewall and installing a third party firewall everyting was working fine again. You should try this, maybe this helps!

I had no closed Socket errors after deactivating the windows firewall so far!

Thanks guys for testing if Steam caused trouble, I will poke people about this again. Sorry there is not a lot I personally can do about this issue .

Just adding to the chorus of double Socket Closeds, East Coast USA.

Maddeningly inconsistent, sometimes happen twice in five minutes, sometimes fine for hours. Makes it pretty much impossible to pew-pew in confidence. Messing with routers/firewalls hasn't resolved the issue.

tracert 87.237.38.200

D+¬termination de l'itin+¬raire vers srv200-g.ccp.cc [87.237.38.200]
avec un maximum de 30 sauts-á:

1 2 ms 1 ms 2 ms livebox.home [192.168.1.1]
2 36 ms 36 ms 35 ms ARouen-552-1-123-1.w92-152.abo.wanadoo.fr [92.152.234.1]
3 34 ms 35 ms 35 ms 10.125.158.74
4 36 ms 36 ms 61 ms ge-3-1-0-0.ncrou101.Rouen.francetelecom.net [193.253.83.250]
5 68 ms 38 ms 38 ms ae44-0.niaub201.Aubervilliers.francetelecom.net[193.252.159.65]
6 40 ms 39 ms 39 ms 81.253.184.10
7 38 ms 38 ms 36 ms te1-3.parse1.Paris.opentransit.net [193.251.128.162]
8 39 ms 38 ms 39 ms kpn-1.GW.opentransit.net [193.251.252.246]
9 57 ms 63 ms 57 ms sdns-s1-rou-1101.FR.eurorings.net [134.222.232.97]
10 58 ms 66 ms 56 ms ldn-s1-rou-1021.UK.eurorings.net [134.222.232.121]
11 56 ms 51 ms 52 ms ldn-s2-rou-1021.UK.eurorings.net [134.222.231.166]
12 56 ms 56 ms 55 ms ldn-s2-rou-1041.UK.eurorings.net [134.222.228.94]
13 52 ms 51 ms 52 ms 134.222.109.115
14 75 ms 51 ms 52 ms srv248-e.ccp.cc [87.237.36.248]
15 52 ms 51 ms 52 ms srv200-g.ccp.cc [87.237.38.200]

Itin+¬raire d+¬termin+¬.

$ traceroute 87.237.38.200
traceroute to 87.237.38.200 (87.237.38.200), 30 hops max, 60 byte packets
1 dslrouter.codav-home.net (192.168.10.254) 0.196 ms 0.291 ms 0.365 ms
2 lo1.br01.wup.de.hansenet.net (213.191.89.30) 33.015 ms 35.071 ms 35.136 ms
3 ae1-108.cr01.dus.de.hansenet.net (62.109.112.189) 41.146 ms 41.209 ms 41.277 ms
4 so-1-0-0-0.cr01.weham.de.hansenet.net (213.191.66.5) 49.182 ms 51.252 ms 53.298 ms
5 ae1-0.xd01.asham.de.hansenet.net (62.109.72.6) 53.295 ms 55.717 ms 55.714 ms
6 ae0-0.pr01.asham.de.hansenet.net (213.191.66.162) 56.963 ms ae1-0.pr01.asham.de.hansenet.net (213.191.66.154) 50.861 ms 52.652 ms
7 rmwc-hmbg-de03-chan-0-0.nw.mediaways.net (213.20.88.202) 54.640 ms 40.629 ms 41.814 ms
8 rmwc-hmbg-de04-xe-0-0-2-0.nw.mediaways.net (195.71.250.74) 46.010 ms 40.979 ms rmwc-hmbg-de04-xe-0-0-0-0.nw.mediaways.net (62.53.171.14) 48.765 ms
9 xmwc-lond-uk01-chan-1-0.nw.mediaways.net (195.71.254.130) 64.508 ms 58.541 ms 59.564 ms
10 ge1-0.ar2.lon2.gblx.net (195.66.224.112) 58.386 ms 58.775 ms 59.290 ms
11 204.245.39.42 (204.245.39.42) 57.543 ms !X 59.048 ms !X 53.933 ms !X

I've tried on singularity if the client is stable. It is for the moment. No socket closed error, no lag. I've run a bandwidth test, all is ok.

You should try guys.

as i said, try on test server to see if any change is coming with the new patch before incriminating ccp work.

I've this problem since one week, I've test on sisi, no problem since now +2 hours...

Oh the test server is working? That's ok then. As long as the test server is working, there is no problem with the actual game and it must be Australia's fault. Or something.

If VPN is fixing the problem then it sounds like the issue is ISP based. I have asked those who submitted bug reports on this issue to confirm their location and ISP but neither of them have gotten back to me yet. If others experiencing the problem can do likewise it will help us confirm one way or the other.