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
Zoe Kush
Froody Goons Spaceship Business
#121 - 2012-07-10 22:24:32 UTC  |  Edited by: Zoe Kush
Quote:
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.

tried myself to download things from my mobile, listening at youtube, installing things from the app-market..... no socket closed at all. It did happen today again in a "new way". I was logged on 3 of my accounts for hours..... all was fine. I closed them, did stuff in RL, came back after some time on another client: socket closed after 5 mins (lucky that I was still docked and reading comms)

Quote:
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.

I have a wired connection on my pc. My setup it's something like that: main modem/router <---> switch <--- my pc and another wi-fi router plugged in the switch ----> second pc and mobile sharing the wi-fi connection occasionally (very rarely, when I'm playing EVE the 2nd pc and mobile are off or have no wi-fi activated)

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

yesterday I was in a SB fleet with 20-30 bad guys. It happened 5 times in a couple of hrs that people got the socket closed, dc'd and uncloacked us all Evil
Of course we all were on TS screaming and shouting!

just saying it's *something else* CCP has to work on. If it's not an FBI virus who went crazy harassing dns' around the www Big smile
Sven Viko VIkolander
In space we are briefly free
#122 - 2012-07-11 14:40:42 UTC
I too am getting this (double window) socket loss message and about once an hour but sometimes multiple times an hour. I only rarely got disconnected from Eve prior to Inferno 1.1 (maybe once every 30 hours of play time) yet since then it has been persistent. If I go afk or tab out for more than 5-10 minutes I get such a disconnect almost without exception.
Heligos
Imperial Shipment
Amarr Empire
#123 - 2012-07-11 21:49:12 UTC
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?

I encountered this problem 3 times within 10 minutes, after having played without any problem for two hours. During those 10 minutes I was afk drone ratting, meaning I basically didn't press anything at all...

I will try to see if the time before the connection drops is constant, because then there's a chance this might not be very far away from the truth...
Inspiration
#124 - 2012-07-11 22:10:09 UTC
I had it a few times when a client was idle, so i did not think much of it. But just I had an alt go into low sec and warp to a station + dock command via autopilot. Just as i sat at the undock, i got the socket issue again (on an active account), ofc, the server docked me in this instance, but it does give a bad feeling.

Sorry for not having any useful information (other then that i got a stellar Internet connection, most people would kill for).

I am serious!

Vincent Athena
Photosynth
#125 - 2012-07-12 01:27:08 UTC  |  Edited by: Vincent Athena
Heligos wrote:
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?...

Could something like this explain my experience at the hotel Im at? The continuous traffic due to TS is keeping a socket open? Or maybe tricking whatever makes sockets for this hotel to keep all of them open due to traffic on one?

Edit: running a ping to TQ also seems to hold the socket open, at least in the odd situation I seem to be in.

Know a Frozen fan? Check this out

Frozen fanfiction

Forger Lanis
The Augen Nation.
#126 - 2012-07-12 18:54:20 UTC
Something has changed, I never had this problem before. EVE ran flawlessly for almost three months (started in January) then at the beginning of April the problem showed up. It's not all the time either. Some days I can play with no disconnects, other days I get disconnected literally every 2 minutes which makes it unplayable.
Yabba Addict
Perkone
Caldari State
#127 - 2012-07-12 20:50:52 UTC
Same here, never had problems before now constant DCs. Lost a hawk to this last night
Epic Hunter
Gildinous Vangaurd
The Initiative.
#128 - 2012-07-13 17:28:22 UTC  |  Edited by: Epic Hunter
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.

I did a tracert while running eve and searching the internet and one just running eve


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

1 2 ms 2 ms 2 ms 192.168.1.1
2 9 ms 7 ms 7 ms 10.175.0.1
3 13 ms 9 ms 8 ms ip68-6-12-39.sd.sd.cox.net [68.6.12.39]
4 10 ms 14 ms 12 ms fed1sysc01-tec191.sd.sd.cox.net [68.6.8.206]
5 9 ms 12 ms 15 ms fed1dsrj01-xe130.0.rd.sd.cox.net [68.6.8.0]
6 * 24 ms 31 ms paltbprj01-ae2.0.rd.pt.cox.net [68.1.2.98]
7 34 ms 36 ms 33 ms 146.82.54.233
8 153 ms 153 ms 154 ms 204.245.39.38
9 255 ms 154 ms 159 ms srv248-e.ccp.cc [87.237.36.248]
10 154 ms 153 ms 154 ms srv200-g.ccp.cc [87.237.38.200]

Trace complete.


Eve + Web browser playing you tube video searched for on google.

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

1 2 ms 2 ms 2 ms 192.168.1.1
2 9 ms 7 ms 7 ms 10.175.0.1
3 13 ms 9 ms 8 ms ip68-6-12-39.sd.sd.cox.net [68.6.12.39]
4 10 ms 14 ms 12 ms fed1sysc01-tec191.sd.sd.cox.net [68.6.8.206]
5 9 ms 12 ms 15 ms fed1dsrj01-xe130.0.rd.sd.cox.net [68.6.8.0]
6 * 24 ms 31 ms paltbprj01-ae2.0.rd.pt.cox.net [68.1.2.98]
7 34 ms 36 ms 33 ms 146.82.54.233
8 153 ms 153 ms 154 ms 204.245.39.38
9 255 ms 154 ms 159 ms srv248-e.ccp.cc [87.237.36.248]
10 154 ms 153 ms 154 ms srv200-g.ccp.cc [87.237.38.200]

Trace complete.

I have forwarded port 2600 to my PC for eve. Disabled all firewalls.

As a side note i can run Teamspeak flawlessly for hours with no drops. The second i load the web browser i get socket error.

CCP please fix this issue, i pay to play i would like to consistently do the playing part or maybe we should just all "drop" payments but still get to play.

Edit:

Location: Southern California
Provider: Cox Communications
Samurai Pumpkin
The Tebo Corp
#129 - 2012-07-13 18:27:51 UTC  |  Edited by: Samurai Pumpkin
Having this problem as of yesterday at around ~10pm central standard time.

I get "socket closed" and when this occurs I briefly lose access to the internet. Skype, Ventrilo, and all other applications lose access to the internet for around 10 seconds.

My router's event log does not show any events. Contacted my provider and they said the same thing. They just updated the firmware on my Motorola Surfboard SBG6580 modem but I am still experiencing the issue.

A moment ago I lost connectivity and noticed that ONLY the computer that I was using with Eve on it had a brief lapse in connectivity. I had the other computer constantly pinging timewarnercable.com with the -t switch and it did not have any issues.

I am using wired connections.

This can happen when I am outside in space relatively idle. I have active shield hardeners on and I'm not doing much. Just mining.


Provider: Time Warner Cable ( roadrunner )
Location: Richardson Texas , United States



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

C:\Users\Admin>tracert 87.237.38.200

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

1 60 ms 37 ms 27 ms cpe-76-184-128-1.tx.res.rr.com [76.184.128.1]
2 19 ms 20 ms 21 ms tengig1-2.dllatxchn-rtr1.tx.rr.com [24.164.211.2
21]
3 24 ms 34 ms 32 ms tge2-4.dllatx1h-tr01.texas.rr.com [24.175.37.188
]
4 29 ms 32 ms 32 ms be21.dllatx1k-cr01.texas.rr.com [24.175.36.193]

5 23 ms 31 ms 27 ms 24.175.49.0
6 33 ms 28 ms 28 ms 107.14.17.136
7 25 ms 22 ms 21 ms ae-1-0.pr0.dfw10.tbone.rr.com [66.109.6.179]
8 26 ms 30 ms 26 ms TenGigabitEthernet2-1.ar4.DAL2.gblx.net [64.211.
60.81]
9 143 ms 140 ms 140 ms 204.245.39.42
10 137 ms 135 ms 134 ms srv245-e.ccp.cc [87.237.36.245]
11 135 ms 133 ms 139 ms srv248-e.ccp.cc [87.237.36.248]
12 137 ms 136 ms 132 ms srv200-g.ccp.cc [87.237.38.200]

Trace complete.


I ran another tracert a bit after that and got this.


C:\Users\Samurai Pumpkin>tracert 87.237.38.200

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

1 38 ms 27 ms 55 ms cpe-76-184-128-1.tx.res.rr.com [76.184.128.1]
2 10 ms 12 ms 12 ms tengig1-2.dllatxchn-rtr1.tx.rr.com [24.164.211.2
21]
3 21 ms 23 ms 23 ms tge2-4.dllatx1h-tr01.texas.rr.com [24.175.37.188
]
4 23 ms 23 ms 23 ms be21.dllatx1k-cr01.texas.rr.com [24.175.36.193]

5 13 ms 11 ms 23 ms 24.175.49.0
6 Transmit error: code 1231.

Trace complete.


I have sent a bug report but could not attach the last tracert due to the 3000 character limit.

Another update:

The second computer that I have "survived" the disconnect. My primary computer is the only one that is effected. Going to uninstall/reinstall eve.
Slik
Wildlands Tactical Response Unit
Great Wildlands Conservation Society
#130 - 2012-07-14 14:10:57 UTC
this is still an issue any more word from devs? this is becoming a real pain in the ass.

I've already submitted a petition with tracerts etc etc
Alexi Falstaff
The Scope
Gallente Federation
#131 - 2012-07-15 00:01:31 UTC
Getting progressively worse all day. I went from stretches as long as 30 minutes to now getting socket close errors at the character selection screen. Repaired, re installed, re downloaded and installed. Also turned off all firewalls, tried direct modem connection etc.... The game is truly unplayable.
Laechyd Eldgorn
Avanto
Hole Control
#132 - 2012-07-15 14:20:30 UTC
Archinquisitor wrote:
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.


Are you sure your problem is not mumble? The program is not stable and is known to have caused connection problems for several people while playing eve. As it is I do not recommend mumble to anyone playing eve, or any other game either.


Khalia Nestune
Mad Stacks
#133 - 2012-07-15 16:59:48 UTC
I'm getting client disconnects more than once an hour. It's extremely frustrating.

ISP: AT&T DSL


2 2 ms 1 ms 1 ms 192.168.0.1
3 21 ms 31 ms 20 ms bras10-l0.mrdnct.sbcglobal.net [204.60.4.46]
4 20 ms 20 ms 19 ms dist2-vlan50.mrdnct.sbcglobal.net [66.159.184.195]
5 19 ms 19 ms 19 ms bb2-10g2-0.mrdnct.sbcglobal.net [151.164.92.153]
6 22 ms 22 ms 23 ms n54ny03jt.ip.att.net [12.122.86.9]
7 27 ms 22 ms 23 ms 192.205.36.106
8 23 ms 25 ms 23 ms xe-4-1-0.cr2.lga5.us.above.net [64.125.30.209]
9 23 ms 27 ms 24 ms ge-1-2-0.mpr2.lga5.us.above.net [64.125.29.58]
10 90 ms 91 ms 89 ms so-3-0-0.mpr1.lhr3.uk.above.net [64.125.28.65]
11 99 ms 90 ms 92 ms 213-152.240-254.PXu259.above.net [213.152.240.254]
12 91 ms 94 ms 92 ms srv245-e.ccp.cc [87.237.36.245]
13 92 ms 97 ms 93 ms srv248-e.ccp.cc [87.237.36.248]
14 96 ms 100 ms 96 ms srv200-g.ccp.cc [87.237.38.200]

http://www.mylootyourtears.com

Khalia Nestune
Mad Stacks
#134 - 2012-07-15 17:04:03 UTC
Epic Hunter wrote:
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.


^ This is the same behavior I have.

http://www.mylootyourtears.com

Ceptia Cyna
The Scope
Gallente Federation
#135 - 2012-07-16 20:29:14 UTC  |  Edited by: Ceptia Cyna
Problems:

A) Suddenly Disconnects, no response, no message, nothing responding, no drones, no agent popupwindow, no undock, nothing. Sometimes i can logoff/quit sometimes i need to terminate eve via taskmanager.
B) Sockets Closed Message or Double Sockets Closed Messages.

ISP: Versatel Germany
Line: ADSL 2+ 16Mbit tuned down.
OS: W7 Ultimate 64x
Router: TP Link TD-8840B (RJ45 Cable)

Router ADSL2+ Statistics Screenshot: http://www.abload.de/img/adslstatisticsx9ko2.png

Tracert:
Quote:
Routenverfolgung zu srv200-g.ccp.cc [87.237.38.200] über maximal 30 Abschnitte:

1 1 ms 1 ms <1 ms *censored*
2 27 ms 42 ms 47 ms esn001ibr003-xdsl.versatel.de [62.214.63.56]
3 25 ms 22 ms 24 ms ge-01-14-v521-xdsl.esn001ibr003.versatel.de [62.214.34.133]
4 26 ms 25 ms 23 ms 10g-9-1.dus002isp005.versatel.de [62.214.110.233]
5 42 ms 29 ms 28 ms 62.214.104.210
6 34 ms 33 ms * ffm-s1-rou-1006.DE.eurorings.net [80.81.192.22]
7 52 ms 54 ms 49 ms ffm-s1-rou-1102.DE.eurorings.net [134.222.230.221]
8 55 ms 59 ms 53 ms kehl-s2-rou-1103.DE.eurorings.net [134.222.227.178]
9 50 ms 50 ms 51 ms nntr-s1-rou-1022.FR.eurorings.net [134.222.227.122]
10 53 ms 61 ms 62 ms ldn-s2-rou-1021.UK.eurorings.net [134.222.231.162]
11 70 ms 51 ms 49 ms ldn-s2-rou-1041.UK.eurorings.net [134.222.228.94]
12 56 ms 50 ms 62 ms 134.222.109.173
13 66 ms 51 ms 47 ms srv245-e.ccp.cc [87.237.36.245]
14 51 ms 51 ms 47 ms srv248-e.ccp.cc [87.237.36.248]
15 49 ms 49 ms 48 ms srv200-g.ccp.cc [87.237.38.200]

Ablaufverfolgung beendet.


Quote:
« 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)
arcca jeth
Dark Alliance
#136 - 2012-07-17 00:01:10 UTC
MY SOCKET!
quit closing it, seriously. cannot even get one client past character selection screen. this is worse than the past few days where it would occasionally happen, now i have to come post about it....again. please find this bug and squash it. it's unacceptable CCP and you know it
Herr Hammer Draken
#137 - 2012-07-17 06:18:45 UTC
I also have a wifi router. I know the socket closed error is a new thing programed into eve with inferno. And it is my guess that program has something to do with the cause itself. Prior to inferno my eve client never lost connection to eve. I never had to restart a gamming session. I could play for 6 hours+ without an interuption.

After inferno I would get about 3 socket closed disconnects in a 4 hour eve session. I think the program that does the socket closed detection itself is programmed to tight and causes the issue. I think in the past if your client got a bit out of sync with the server it was no big deal as it would self correct after a bit and keep running. But now maybe it is because of tidi itself that the client no longer has the ability to have any slipage and the socket closed error checking is designed to shut down the client as soon as it detects a bit of lag? Guessing on some of this but it kinda makes sense.

Perhaps we always had some lag in the system and it was no big deal until tidi was improved with inferno.
Now the server can not tolerate any lag and we get socket closed. Server forces the issue.

I should note that I changed nothing on my end before/after inferno. Add to that the fact that many other people also began to have problems the same as me after inferno and it becomes obvious something has changed with eve itself. So what could that change be? Well the socket closed protocol for one. And the tidi programming changes with inferno for another.

Herr Hammer Draken "The Amarr Prophet"

Darius Brinn
The Scope
Gallente Federation
#138 - 2012-07-17 06:32:11 UTC  |  Edited by: Darius Brinn
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.
Darius Brinn
The Scope
Gallente Federation
#139 - 2012-07-17 06:32:44 UTC  |  Edited by: Darius Brinn
Duplicated post.
Forger Lanis
The Augen Nation.
#140 - 2012-07-17 20:20:48 UTC  |  Edited by: Forger Lanis
Darius Brinn wrote:
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.