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
arcca jeth
Dark Alliance
#81 - 2012-06-28 22:12:25 UTC
i run multiple clients, but confirmed that even 1 client will get socket error. this happens if flying around in system or even just hanging out in station.
Grunton
Aliastra
Gallente Federation
#82 - 2012-06-28 23:09:50 UTC
I'm not using Steam but Eve is unplayable atm
Altrue
Exploration Frontier inc
Tactical-Retreat
#83 - 2012-06-28 23:31:34 UTC
Two times in 1 hour and a half : Socket closed for my two accounts at the same time.

I verifyed in a cloaky third hidden account to see if it wasn't an attempt for a hacker to log in and steal my money, but no, my chars are not connected.

Signature Tanking Best Tanking

[Ex-F] CEO - Eve-guides.fr

Ultimate Citadel Guide - 2016 EVE Career Chart
Jaxom Silpheed
State War Academy
Caldari State
#84 - 2012-06-29 02:11:05 UTC
Update on my issue: Appears to be resolved.

I tested on a different net connection, and had no issues. Went back to my connection, and the issues seemed to be gone. Highly confusing. It wasn't until after the recent patch that I remembered I used a static IP for my computer on my connection. I changed back to the static IP, and tested some more - no problems found. Unfortunately, being unable to replicate the issue I can't troubleshoot any further. But if you have a static IP, give a dynamic one a go instead. I now play exactly the same as I used to, and have no problems.
Veryez
Hidden Agenda
Deep Space Engineering
#85 - 2012-06-29 08:58:27 UTC  |  Edited by: Veryez
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Documents and Settings>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 READYSHARE [xxx.xxx.x.x]
2 7 ms 8 ms 8 ms 10.240.164.9
3 * 12 ms 8 ms 67.59.230.169
4 * 13 ms 11 ms 67.83.233.13
5 20 ms * 13 ms 64.15.8.113
6 13 ms 13 ms 14 ms 64.15.0.230
7 12 ms 47 ms 11 ms ge-9-1-4.er2.lga5.us.above.net [64.125.13.29]
8 13 ms 13 ms * xe-0-1-0.cr2.lga5.us.above.net [64.125.27.66]
9 14 ms * 35 ms xe-0-0-0.cr1.lga5.us.above.net [64.125.29.41]
10 166 ms 80 ms 80 ms ge-2-1-0.mpr1.lhr3.uk.above.net [64.125.26.38]
11 * 81 ms 80 ms 213-152.240-254.PXu259.above.net [213.152.240.254]
12 * 95 ms 93 ms srv245-e.ccp.cc [87.237.36.245]
13 88 ms 90 ms 87 ms srv248-e.ccp.cc [87.237.36.248]
14 93 ms 94 ms 95 ms srv200-g.ccp.cc [87.237.38.200]

Trace complete.

C:\Documents and Settings>ping 87.237.38.200

Pinging 87.237.38.200 with 32 bytes of data:
Reply from 87.237.38.200: bytes=32 time=96ms TTL=115
Request timed out.
Reply from 87.237.38.200: bytes=32 time=94ms TTL=115
Reply from 87.237.38.200: bytes=32 time=105ms TTL=115

Ping statistics for 87.237.38.200:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 94ms, Maximum = 105ms, Average = 98ms

Eve at the moment is unplayable
Malakoma
HyperQuest Corp
#86 - 2012-06-29 17:44:03 UTC  |  Edited by: Malakoma
Malakoma wrote:
Malakoma wrote:
Anastasius Steiner wrote:
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!


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 !!!



I managed to get a couple of 2 hour mining sessions in using a mouse-mover set to 20 seconds and had no Socket Closes although it might have just been a fluke. Its not very practical though as having to wait for the mouse to move before clicking something soon becomes tiring.

I've had feedback from my "Socket Closed" petition but they basically said to check my router and firewall, and if the problem persists to get back to them.

By the way, they suggested making sure that port 26000 is open for both TCP and UDP although I certainly haven't changed my port settings in a long time but I'm going to double check.
Takahiro Tanaka
Tanaka Stuff and Supplies
#87 - 2012-06-29 19:46:08 UTC
I never had any problems until today. I got several times disconnected with the socket closed error.

I have a very reliable cable connection that never failed me so far, so I took a look into the router logs and found something:

Quote:

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 x'ed out my IP address.

The sequence number belongs to layer-4 (TCP/UDP) and is not altered or even being looked at by routers along the way. So its definately a problem coming from the source, which is an CCP server.
Tex' Winchester
The Scope
Gallente Federation
#88 - 2012-06-30 10:06:00 UTC
This problem must have something to do with either CCP's server or with the inferno Update.

Why would someone think its a steam problem? I bought Eve online through steam, and never had a problem until Inferno.

I have the socket closed issue every 10 to 15 minutes. The game really is unplayable, losses of drones e.c.t.

Not to forget that i payed for the game time while its impossible to play.

Checked my ports, my router, reinstalled the game without using steam, doesn't help at all.

I tried other mmos, no disconnection from their servers.


Hope there will be a fix soon.
Cerebral Wolf
N.A.G.A Too
Domain Research and Mining Inst.
#89 - 2012-06-30 10:30:05 UTC
My sockets get closed both at my place and my GF's....any ideas?
Sabren Bel
Doomheim
#90 - 2012-06-30 21:43:27 UTC
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. "
Juggati
Illuminated
Goonswarm Federation
#91 - 2012-07-01 11:39:27 UTC
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).
Cerebral Wolf
N.A.G.A Too
Domain Research and Mining Inst.
#92 - 2012-07-01 14:10:18 UTC
Juggati wrote:
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).



CCP don't know how to fix it or whats wrong, hence the fix's from the community.
Abstract Mind
School of Applied Knowledge
Caldari State
#93 - 2012-07-01 15:34:11 UTC
Verizon FIOS here.

Laptop socket closes and a few minutes later the desktop sockets close.

All the while I have other stuff running fine on the network.

Just need to restart EVE to fix the problem but annoying as hell.
Pollychrest
Phantom Space
Space Madness.
#94 - 2012-07-01 16:12:06 UTC
I have this problem as well as the low FPS problem. Life sucks.
Cerebral Wolf
N.A.G.A Too
Domain Research and Mining Inst.
#95 - 2012-07-01 19:26:45 UTC
Sabren Bel wrote:
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. "


Sorry, didn't work. Client still likes to **** itself in the middle of a fleet and tell me that someone closed a socket somewhere.
Prince aikka
#96 - 2012-07-01 21:59:58 UTC
Just started getting this error about an hour ago. First on my main client, then about 5 min later on the other. then about 30 min later the main went down again, also getting some lag on my main client, and both clients are on the same sys and in the same sys in game.
Zoe Kush
Froody Goons Spaceship Business
Goonswarm Federation
#97 - 2012-07-02 00:27:02 UTC
same stuff here, never happened before inferno. I'd say the average it's once per day, and most of the times it happens after I docked and went afk as someone else also reported. Once, only once it happened at a gate in lowsec just when I was jumping (session change also has been reported in the thread). That time the client freezed (impossible to interact but no crash) for a good 30 seconds before I had that socket closed thing. After restarting it I found myself in warp (as "usual" with disconnections) heading to the gate in the system in which I was supposed to jump, and no flashy, went in my CQ, got some tobacco. Darn!

It happened on my old rig and the new one I'm playing from now. I did a clean install both of win and the EVE client. NO steam, NO win firewall, NO vpn, NO other online games installed = CCP fail Cry


tracert 87.237.39.92

1 <1 ms <1 ms <1 ms . [192.168.1.1]
2 26 ms 25 ms 25 ms 192.168.100.1
3 26 ms 25 ms 26 ms host***-***-static.**-**-b.business.telecomitalia.it [**********]
4 26 ms 26 ms 26 ms 80.17.209.142
5 33 ms 33 ms 33 ms 172.17.8.221
6 34 ms 33 ms 33 ms 172.17.6.93
7 41 ms 42 ms 38 ms bundle-ether12.milano26.mil.seabone.net [93.186.128.205]
8 81 ms 71 ms 69 ms xe-0-2-0.franco31.fra.seabone.net [195.22.211.103]
9 66 ms 66 ms 66 ms xe-2-0-0.mpr1.fra4.de.above.net [64.125.13.49]
10 64 ms 126 ms 73 ms xe-0-1-0.mpr2.cdg12.fr.above.net [64.125.24.94]
11 75 ms 74 ms 73 ms xe-5-2-0.mpr1.lhr3.uk.above.net [64.125.24.81]
12 93 ms 199 ms 203 ms 213-152.240-254.PXu259.above.net [213.152.240.254]
13 70 ms 70 ms 70 ms srv245-e.ccp.cc [87.237.36.245]
14 70 ms 69 ms 70 ms srv248-e.ccp.cc [87.237.36.248]
15 74 ms 75 ms 74 ms srv92-h.ccp.cc [87.237.39.92]


go fix it NAO!! X
Prince aikka
#98 - 2012-07-02 02:25:21 UTC
Everett WA
Comcast cable

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

1 <1 ms <1 ms 1 ms 10.0.0.1
2 8 ms 7 ms 9 ms **.**.**.*
3 9 ms 15 ms 11 ms te-5-8-ur02.everett.wa.seattle.comcast.net [68.87.205.169]
4 9 ms 8 ms 16 ms ae-12-0-ar03.seattle.wa.seattle.comcast.net [69.139.164.93]
5 19 ms 12 ms 23 ms he-1-8-0-0-10-cr01.seattle.wa.ibone.comcast.net [68.86.94.229]
6 41 ms 40 ms 38 ms pos-0-8-0-0-cr01.denver.co.ibone.comcast.net [68.86.85.210]
7 52 ms 53 ms 52 ms pos-2-7-0-0-cr01.dallas.tx.ibone.comcast.net [68.86.85.54]
8 72 ms 75 ms 75 ms pos-0-15-0-0-cr01.atlanta.ga.ibone.comcast.net [68.86.85.150]
9 96 ms 94 ms 95 ms 68.86.89.169
10 86 ms 84 ms 85 ms be-14-pe04.ashburn.va.ibone.comcast.net [68.86.84.218]
11 169 ms 169 ms 169 ms 202-126-245-83.packetexchange.net [83.245.126.202]
12 172 ms 170 ms 174 ms srv245-e.ccp.cc [87.237.36.245]
13 171 ms 171 ms 171 ms srv248-e.ccp.cc [87.237.36.248]
14 176 ms 170 ms 173 ms srv200-g.ccp.cc [87.237.38.200]

Trace complete.

I cant even play now its getting so bad, every few min i get dumped
Calvmar
Federal Navy Academy
Gallente Federation
#99 - 2012-07-02 05:09:31 UTC
traceroute to 87.237.38.200 (87.237.38.200), 30 hops max, 60 byte packets
1 * * *
2 hos-tr3.juniper2.rz13.hetzner.de 213.239.224.65 de 0.138 ms
hos-tr4.juniper2.rz13.hetzner.de 213.239.224.97 de 0.270 ms
hos-tr2.juniper1.rz13.hetzner.de 213.239.224.33 de 0.165 ms
3 hos-bb2.juniper4.ffm.hetzner.de 213.239.240.150 de 5.841 ms 5.838 ms 5.828 ms
4 r1fra1.core.init7.net 82.197.166.85 ch 14.368 ms 14.441 ms 14.513 ms
5 xe-1-2-0.mpr1.fra4.de.above.net 80.81.194.26 de 6.511 ms 6.589 ms 6.313 ms
6 xe-0-1-0.mpr2.cdg12.fr.above.net 64.125.24.94 us 15.814 ms 15.480 ms 15.478 ms
7 xe-5-2-0.mpr1.lhr3.uk.above.net 64.125.24.81 us 27.899 ms 28.014 ms 27.964 ms
8 * * *
9 213-152.240-254.PXu259.above.net 213.152.240.254 gb 28.250 ms
us
SalubriousSky Rinah
Cryptic Spear
#100 - 2012-07-03 16:34:32 UTC
CCP - I suggest you fix this problem asap. Logically if we are all having the same problem in several different geographical locations with several different ISPs then the problem lies with your servers. Thank you.