Issues, Workarounds & Localization

I just went through this myself and thought I'd share some advice.

Comcast (my ISP) always seems to do network maintenance things after 2am. It's very infrequent where I currently live (seemed like a nightly occurrence in my last region), but tonight I saw the dreaded socket error as I was docking.

Needless to say, I didn't want to be offline and free-floating at that precise moment.

Though everything seemed ok otherwise, I shut off Windows firewall, restarted the machine and finally found this thread. Pinging Tranquility (87.237.38.200) showed severe packet loss - but where?

Enter MTR (multiple traceroute). Traceroute is a built-in network utility in Windows and Linux that lets you see what's going on by pinging each server in your connection path, showing where the packets are probably getting lost. MTR is a particular type of traceroute that runs traceroutes in parallel (if you're 10 hops from the destination it'll ping each server in that path, repeatedly). Great for seeing trends.

Note that some devices will show 100% loss - in my case, the cable modem itself (which isn't configured to be pingable). But other servers down the line should show little or no loss.

I personally use WinMTR in Windows, and whatever's out there on the package servers when in Linux. When I ran it tonight, I quickly saw the failure was likely because of a server a few hops away dropping packets. Once that server's congestion cleared I was able to log in... and happily found myself already docked.

Then, as I wrote this, the socket closed again, and MTR suggests that the same intermediate server in my ISP's domain is to blame. Perhaps it's telling me that it's time for sleep...

Edit: An hour later and everything is back to normal now.

Me and 99.98% of my mates are suffering an important socket close spawnrate since last patch and it's everlasting longer and longer. I was not surprised to see that it's the same problem for most of the players in Eve.

What's CCP position about this ? The problem might be on the player side and only him is expected to work on resolving it ?

I have the same feeling when U.S government is asked about the trillions of dollars missing and replying "what was the other question ?".



If we loose high value stuff due to socket closed, are we considerated as responsible as if we loose it due to game mechanics ?



CCP might understand that even all the world's goodwill we could use to try to play at Eve, won't be enough against a technical problem which will let us no other choice than stopping to play, despite of our real desire to play.

Heya guys,

I'm running 3 accounts and 1 or 2 out of 3 get disconnected 2-3 times/day. At least 1 keeps always connected.

I've cleared cache and tried whatever, no fix for me

My ISP is Tiscali and I'm Italian. Never had socket error problem with EVE before and I play since 2005!

cCCP fix da thing kkthxbye

That is a kind of weird network problem. I did have this socket closed error on my laptop before but not on my desktop. I suspect it was ESET Smart Security that caused problems because I don't have it on my desktop and disabling it worked fine. I think some of us might have this generic socket closed message even though it is not related to their ISP nor CCP.
Try uninstalling your firewall / AV for a bit, get a good quality wired connection (usually it solves a lot of network issues), restart you modem/router, or even get a fresh OS install as I did.

Now to the real problem.

Since a month or two I'm having the same issue on my desktop too. I tried everything I could think of but no result so far. I guess it is ISP based since 2 friends of mine with the same ISP (Free in France) are having the socket closed error at the EXACT same time as me.
But what's troubling is that it doesn't seem to be specific to some ISP nor route given the very diffrent trace route provided so far. The post on the whirlpool forums is really interesting. I thought of a weird QoS policy that could drop some EvE packets when the link is a bit saturated but the problem is to determine which link(s). I bet it is closer to the servers that it is to the client. I may be wrong but it could explain some socket closed errors.


Here is my tracert :

1 1 ms 1 ms <1 ms 192.168.0.254
2 31 ms 23 ms 20 ms ***.***.***.***
3 20 ms 21 ms 20 ms nancy-6k-1-a5.routers.proxad.net [213.228.13.62]
4 40 ms 38 ms 31 ms strasbourg-6k-1-v800.intf.routers.proxad.net [212.27.50.130]
5 28 ms 29 ms 30 ms th2-crs16-1-be1101.intf.routers.proxad.net [212.27.50.9]
6 29 ms 29 ms 29 ms bzn-crs16-1-be2000.intf.routers.proxad.net [212.27.57.210]
7 30 ms 31 ms 32 ms bzn-crs16-2-be1000.intf.routers.proxad.net [212.27.59.102]
8 39 ms 42 ms 30 ms te0-1-0-4.377.mag21.par01.atlas.cogentco.com [149.6.115.25]
9 29 ms 28 ms 28 ms prs-b2-link.telia.net [213.248.86.169]
10 29 ms 29 ms 29 ms prs-bb1-link.telia.net [213.155.135.190]
11 88 ms 41 ms 43 ms ldn-bb1-link.telia.net [80.91.247.7]
12 46 ms 46 ms 42 ms ldn-b3-link.telia.net [80.91.245.27]
13 38 ms 40 ms 40 ms eveonline-ic-138015-ldn-b3.c.telia.net [213.248.83.198]
14 42 ms 41 ms 36 ms srv250-f.ccp.cc [87.237.37.250]
15 36 ms 36 ms 35 ms srv200-g.ccp.cc [87.237.38.200]

proxad.net are Free's routers.


I'm a network engineer so if any dev working on the network part wants some more data I can try to provide it. I'll try to get a wireshark trace of when this error happens, it might provide some additional information.

EDIT: Post #581 is interesting, I'll try MTR too.

By the way, is there any chance to get a more detailed error message or log other than the generic "Socket closed" ?

EDIT 2: Found the Logserver.exe program in Eve folder to generate logs. launch this and then play eve as usual. You coul then provide the results as a bug report when you get a socket closed error.

EDIT 3: Disabling the Checksum offload didn't fix the issue. I spotted the error on the wireshark trace but it's just wireshark related and is not the cause of the problem for me.

SOCKET LOST PROBLEM SOLVED

Hello,

For all the people with "socket lost " problems with ISP ziggo Read this .

i have called with Ziggo helpdesk and they gave me number off other ziggo service with bether tecki's

this guy took over my pc and letts me reset my wifi router and modem by taking down the power and do a reboot.

i have config my router again and all problems where solved.

i hope this issue is now in the past. (with ziggo you never know)


i hope that this is the solution and we ( all Ziggo clients) can fly again to be victories or not.


best regard,

Mac

I believe I've discovered the explanation for this. I think my local hub is timing out on an idle connection, and PP stops it from going idle.

I've been using MTR (multiple traceroute) for the past day or two, taking records to bring to my ISP later. I discovered that starting the ping without doing other internet things first, I always had 100% packet loss for the first 2-3 packets. As if there was no connection to the internet. Which is exactly what I think is happening, the router doesn't detect any activity, and idles the connection. Since EVE only requires 5 lost packets to disconnect, and I'm losing at least 3 to restart the connection, this would almost always trigger the error.

I'll report back with results from using PP to keep the connection open in a day or two. In the meantime, anyone with more expertise know how to disable the idle on a router/network adapter? I've already got power saving turned off and TX power to 100% on my desktop adapter.

This thread is a year old. Just because many people have had this problem over the course of this time, it does not mean it's the same problem. This is most probably a collection of errors with many different sources.

For example, I have had this problem for a while in the past. I remember changing to wired connection from PC to my router at one point because my packet losses were bad. This has helped me and was a configuration/setup issue in my house.

So CCP may not be able to fix YOUR problem with YOUR connection.

However, the EVE client seems to be particularly sensitive about packet losses and that's something CCP could probably look into and improve.

Game is unplayable as I get socket error within a minute after logging in

Also it seems it lets me play after my tz has passed which is also annoying

I thought there was a fix on SiSi which was meant to be used to fix this?

So i try to log in today after passing the russian log in even though mine is meant to be in english.
i get connected for a whopping 2 mins then i lose all 3 accounts 1 after the other to 'Socket Closed'.

I hope CCP are going to reinburse the 1 hour long phone call to my isp at a premium rate yesterday trying to sort this problem?

This is not a broken router,an isp issue,a lan issue or a pc problem.
Its a CCP problem please fix it ASAP.

How can you bring out a major patch in 2 days when half of eve can't even connect for 2 mins?

Surely the fact you can't even control the language in the launcher shows you're having problems there somewhere.

---

Just tried to log in again stayed connected for a few mins then 'Socket Closed'
Just cancelled subs on all accounts until this is fixed even the subs section is in Russian.
Been hacked ?
I ain't paying to play a broken game

ok this is just getting old ffs I want to play this game -.- I'm just dcing every minute