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.
 

Socket Closed - Launcher only

First post First post
Author
Previous Topic Next Topic
pajedas
Doomheim
#81 - 2016-01-30 00:48:28 UTC
Silent Samurai wrote:
I post a small Guide for narrowing down the node on your route that causes the problems. Glad if I can help somebody. Sadly this forums seem to have no spoiler function, so I have to make a double post because of character limit.

That would be awesome IMO.

🐇
Silent Samurai
Federal Navy Academy
Gallente Federation
#82 - 2016-01-30 00:49:49 UTC  |  Edited by: Silent Samurai
Narrow-Down-Method by ping -t:

Currently there are 2 types of problems reported, one is normal game & download speed for updates / no problems with multiple clients / but constant socket closes caused by packet loss (my problem). The other reported is awkward low download speed for updates (hrs for small patches) and massive problems logging in more than one client, which seems to be caused by traffic-shaping of net owners towards the cloud hosters (Telekom to cloudfront in Germany). My method is for problem one.

1.

Open the networks diagnostics of the launcher, do 1 Traceroute test. That will give you the IP-Route from your PC to the EVE servers. You get 3 traceroutes, first 2 for binaries.eveonline.com / resources.eveonline.com (they are outsourced to cloud-hosters, cloudfront for Germany in Frankfurt, updates are hosted there f.e.) and client.eveonline.com, thats THE game server in London. This result never shows success on the last hop as this server is not answering pings (DDoS-protection). If it shows "timeout" you have a packet loss, if it shows"target not reachable" that packet was successful. if you see 3 stars as result for the ping time and timeout instead of IP, these servers do not answer ping as DDos-protection too but let packets pass.

Here you see a perfect result (phew, no spoiler function):

Quote:
start tracert for binaries.eveonline.com

traceroute to d17ueqc3zm9j8o.cloudfront.net [54.230.200.178] over max. 30 hops:

1 <1 ms <1 ms <1 ms fritz.box [192.168.178.1]
2 19 ms 24 ms 19 ms dslb-088-073-176-001.088.073.pools.vodafone-ip.de [88.73.176.1]
3 19 ms 19 ms 19 ms 188.111.213.204
4 20 ms 19 ms 19 ms 88.79.24.12
5 20 ms 23 ms 23 ms 92.79.212.181
6 30 ms 31 ms 31 ms 92.79.213.178
7 29 ms 29 ms 28 ms decix2.amazon.com [80.81.195.152]
8 28 ms 28 ms 28 ms 54.239.4.112
9 31 ms 31 ms 31 ms 54.239.4.89
10 * * * timeout
11 * * * timeout
12 * * * timeout
13 28 ms 28 ms 28 ms server-54-230-200-178.fra50.r.cloudfront.net [54.230.200.178]

traceroute finished

start tracert for res.eveonline.ccpgames.com

traceroute to dm794883twbxj.cloudfront.net [54.230.200.152] over max. 30 hops:

1 1 ms <1 ms <1 ms fritz.box [192.168.178.1]
2 31 ms 19 ms 19 ms dslb-088-073-176-001.088.073.pools.vodafone-ip.de [88.73.176.1]
3 19 ms 19 ms 18 ms 188.111.213.204
4 23 ms 19 ms 19 ms 88.79.24.4
5 23 ms 19 ms 20 ms 92.79.212.173
6 30 ms 27 ms 28 ms 92.79.213.170
7 27 ms 28 ms 27 ms decix2.amazon.com [80.81.195.152]
8 27 ms 28 ms 28 ms 54.239.4.86
9 27 ms 27 ms 27 ms 54.239.4.63
10 * * * timeout
11 * * * timeout
12 * * * timeout
13 30 ms 30 ms 30 ms server-54-230-200-152.fra50.r.cloudfront.net [54.230.200.152]

traceroute finished

start tracert for client.eveonline.com

traceroute to client.eveonline.com [87.237.39.208] over max. 30 hops:

1 1 ms <1 ms <1 ms fritz.box [192.168.178.1]
2 19 ms 19 ms 19 ms dslb-088-073-176-001.088.073.pools.vodafone-ip.de [88.73.176.1]
3 19 ms 19 ms 19 ms 188.111.213.204
4 19 ms 19 ms 19 ms 88.79.24.4
5 19 ms 19 ms 19 ms 92.79.212.173
6 29 ms 31 ms 31 ms 92.79.213.170
7 31 ms 31 ms 31 ms xe-1-2-0.mpr1.fra4.de.above.net [80.81.194.26]
8 48 ms 41 ms 40 ms ae27.cs1.fra9.de.eth.zayo.com [64.125.30.254]
9 42 ms 42 ms 42 ms ae0.cs1.fra6.de.eth.zayo.com [64.125.29.54]
10 43 ms 43 ms 44 ms ae2.cs1.ams17.nl.eth.zayo.com [64.125.29.59]
11 41 ms 42 ms 41 ms ae0.cs1.ams10.nl.eth.zayo.com [64.125.29.80]
12 43 ms 68 ms 44 ms ae2.cs1.lhr15.uk.eth.zayo.com [64.125.29.17]
13 42 ms 42 ms 42 ms ae27.mpr3.lhr3.uk.zip.zayo.com [64.125.30.235]
14 41 ms 41 ms 41 ms ae6.mpr2.lhr3.uk.zip.zayo.com [64.125.21.22]
15 213-152.240-250.PXu259.above.net [213.152.240.250] meldet: target not reachable.

Traceroute-Diagnose finished



Anyway, tracerts are often irritating as I said before, they never showed any loss on the first hop for me, but they give you the IP-Adresses you need for the pings you need to do.
First hop IP is always your router (note it, you might know that anyway), 2nd one is your ISPs node (note too). Optional you can note also all IPs on the route that show themselves. I did for the decix2.amazon.com, as it is one of the busiest internal german gateways (thus only shows on first 2 routes as these servers are in Germany) and the 3rd hop, 1st behind my ISP on all routes.

2.

Open as many DOS-Input-Consoles (Eingabeaufforderung for Germany) as you need to, I did 5.
Type this lines each one into one window:

ping -t ***.***.***.*** (insert router IP / 1st hop)
ping -t ***.***.***.*** (insert ISP IP / 2nd hop)
ping -t ***.***.***.*** (insert 1st IP after ISP / 3rd hop)
ping -t ***.***.***.*** (insert large gateway IP / f.e. decix2.amazon.com in Germany)
ping -t ***.***.***.*** (insert last answering IP before game server / ae6.mpr2.lhr3.uk.zip.zayo.com [64.125.21.22] in London for me)

Let them run for at least 10-15 minutes. Stop them by hitting Ctrl+C inside the consoles, which will type out the statistic result. You should have 0% (max. 1%) packet loss on all results. If not find the first node they are starting to increase and you found the badboy. If it is indeed your router, do as I and test every possible way of connection.

Thats it. Glad if I could help someone, as this is a really annoying issue where you don't have to expect much support from CCP.
pajedas
Doomheim
#83 - 2016-01-30 01:15:20 UTC

Thanks Silent Samurai.

Testing now as Eve is currently unplayable.

🐇
General Guardian
Perkone
Caldari State
#84 - 2016-01-30 21:30:31 UTC
Seems my problem wasn't fixed, must have been coincidence, as I have the exact same issue again.

Must be a time of day thing, is there too much congestion on networks in London this time of day?
pajedas
Doomheim
#85 - 2016-02-01 02:56:38 UTC
Network diagnostics - EVE Launcher

Starting traceroute diagnostics - this may take several minutes

Starting tracert for binaries.eveonline.com

Tracing route to d17ueqc3zm9j8o.cloudfront.net [54.230.160.29]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms attunitepro.lan [192.168.1.1]
2 56 ms 58 ms 55 ms 172.26.96.169
3 55 ms 71 ms 47 ms 172.18.236.228
4 64 ms 69 ms 60 ms 12.249.2.17
5 61 ms 64 ms 63 ms 12.83.170.18
6 59 ms 63 ms 59 ms 12.122.141.233
7 71 ms 62 ms 63 ms 192.205.36.158
8 59 ms 63 ms 57 ms ae-6.r03.atlnga05.us.bb.gin.ntt.net [129.250.5.188]
9 77 ms 70 ms 76 ms xe-0-1-0-17.r03.atlnga05.us.ce.gin.ntt.net [204.2.241.98]
10 72 ms 72 ms 78 ms server-54-230-160-29.jax1.r.cloudfront.net [54.230.160.29]

Trace complete.

Starting tracert for res.eveonline.ccpgames.com

Tracing route to dm794883twbxj.cloudfront.net [54.230.160.9]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms attunitepro.lan [192.168.1.1]
2 58 ms 57 ms 56 ms 172.26.96.169
3 61 ms 63 ms 68 ms 172.18.236.228
4 63 ms 51 ms 55 ms 12.249.2.17
5 65 ms 59 ms 67 ms 12.83.170.18
6 73 ms 60 ms 59 ms 12.122.141.233
7 62 ms 62 ms 59 ms 192.205.36.158
8 69 ms 61 ms 68 ms ae-6.r03.atlnga05.us.bb.gin.ntt.net [129.250.5.188]
9 76 ms 82 ms 78 ms ae-0.amazon.atlnga05.us.bb.gin.ntt.net [129.250.195.174]
10 75 ms 79 ms 80 ms server-54-230-160-9.jax1.r.cloudfront.net [54.230.160.9]

Trace complete.

Starting tracert for client.eveonline.com

Tracing route to client.eveonline.com [87.237.39.208]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms attunitepro.lan [192.168.1.1]
2 60 ms 64 ms 60 ms 172.26.96.169
3 64 ms 64 ms 56 ms 172.18.236.228
4 55 ms 59 ms 59 ms 12.249.2.17
5 58 ms 71 ms 68 ms 12.83.170.18
6 59 ms 60 ms 59 ms gar24.attga.ip.att.net [12.122.141.181]
7 58 ms 58 ms 50 ms 192.205.33.42
8 70 ms 74 ms 68 ms ash-bb3-link.telia.net [62.115.115.77]
9 165 ms 162 ms 157 ms ldn-bb3-link.telia.net [80.91.246.69]
10 147 ms 152 ms 152 ms ldn-b3-link.telia.net [62.115.140.241]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

Traceroute diagnostics finished

I WILL PAY CASH MONEY OR ISK FOR A PROPER SOLUTION TO THIS "SOCKET WAS CLOSED" ERROR!

🐇
General Guardian
Perkone
Caldari State
#86 - 2016-02-01 10:00:34 UTC
I've installed a Trial VPN (hide-me) cause there's no sign up for it, just to check how my data route changes. And I am able to connect to eve.

Turns out for some reason, my data is being routed the wrong way across my country, then across the US (the wrong way around) and eventually to london, but because the trip is so long the packets are 50 to 90% lost.

My Provider doesn't know why this routing has occured, but the VPN goes straight through Singapore like my data was meant to in the first place.

So somewhere along the line, some networking company is routing my ISP the wrong way around the entire planet.
pajedas
Doomheim
#87 - 2016-02-01 14:35:01 UTC
Mine does fine until it gets to:

62.115.140.241 United Kingdom England London Teliasonera Ab

Seems to get stuck there.

I'm in the United States.

One PLEX for a real fix?

🐇
General Guardian
Perkone
Caldari State
#88 - 2016-02-01 17:28:16 UTC
pajedas wrote:
Mine does fine until it gets to:

62.115.140.241 United Kingdom England London Teliasonera Ab

Seems to get stuck there.

I'm in the United States.

One PLEX for a real fix?


Try a trial of a VPN, then do another traceroute. See how you go.
Nerbert
Abominable Arses of Aggression
#89 - 2016-02-03 09:54:05 UTC
My problem is similar, except I can't even connect. This started right after downtime tuesday. Launcher won't download the update and I get the following from a traceroute. There's >17k on tranquility (which apparently the launcher is able to get), but I've been trying to get on for 2 days with no success. Anyone that can interpret the below info, it would be greatly appreciated.

Starting traceroute diagnostics - this may take several minutes

Starting tracert for binaries.eveonline.com

Tracing route to d17ueqc3zm9j8o.cloudfront.net [54.192.234.210]
over a maximum of 30 hops:

1 1 ms 1 ms <1 ms TGT [10.0.1.1]
2 19 ms 8 ms 13 ms 203.205.114.1
3 8 ms 8 ms 7 ms 172.16.1.5
4 8 ms 10 ms 7 ms 172.16.100.1
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 19 ms 18 ms 16 ms server-54-192-234-210.nrt12.r.cloudfront.net [54.192.234.210]

Trace complete.

Starting tracert for res.eveonline.ccpgames.com

Tracing route to dm794883twbxj.cloudfront.net [54.192.234.43]
over a maximum of 30 hops:

1 1 ms 1 ms <1 ms TGT [10.0.1.1]
2 9 ms 7 ms 10 ms 203.205.114.1
3 15 ms 8 ms 10 ms 172.16.1.5
4 8 ms 7 ms 9 ms 172.16.100.1
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 15 ms 25 ms 15 ms server-54-192-234-43.nrt12.r.cloudfront.net [54.192.234.43]

Trace complete.

Starting tracert for client.eveonline.com

Tracing route to client.eveonline.com [87.237.39.208]
over a maximum of 30 hops:

1 5 ms 3 ms <1 ms TGT [10.0.1.1]
2 26 ms 8 ms 8 ms 203.205.114.1
3 11 ms 8 ms 7 ms 172.16.1.5
4 12 ms 10 ms 10 ms 172.16.100.1
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

Traceroute diagnostics finished
Miles Winter
The Scope
Gallente Federation
#90 - 2016-02-03 23:10:59 UTC  |  Edited by: Miles Winter
incorrect info in post, can't delete, so edited.
Enabran' Tain
Viziam
Amarr Empire
#91 - 2016-02-04 18:28:54 UTC
Still experiencing this problem almost daily.
Lady Val Inara
Brutor Tribe
Minmatar Republic
#92 - 2016-02-06 17:27:29 UTC
Enabran' Tain wrote:
Still experiencing this problem almost daily.


Same here, any progress?
Vindictive Misanthrope
Brutor Tribe
Minmatar Republic
#93 - 2016-02-07 17:43:02 UTC
CCP, I have tried to give you money over the years. But you just throw it right back at me every damn time.

Why won't you love me? Straight
Tosuro
State War Academy
Caldari State
#94 - 2016-02-09 04:20:59 UTC
Did what Silent Samurai said. 0% loss on everything. Please open your sockets for me EVE :(
Rastigan
Caldari Provisions
Caldari State
#95 - 2016-02-10 06:30:38 UTC
Same problem as everyone else, and just like everyone else who has multiple clients running , not all of them disconnect

simultaneously.
Nakito Kobara
Yamagata Syndicate
Northern Coalition.
#96 - 2016-02-10 10:20:52 UTC
Been having a lot of disconnects the last month..didn't have this problem before. I notice a few replies are KPN Netherlands. I'm also KPN. But I don't loose connection to anything else like mumble.

Yamagata Syndicate - Null sec - PvP - Join today!
3ulldog
GOODBYE EVE THANKS FOR THE FISH
#97 - 2016-02-14 12:51:21 UTC
Multiple Threads and still no word from CCP.
Still get socket closed messages on one of my accounts whilst the others stay active.
Have now started taking notes on times and dates and will put a petition in for each one and so on until this is resolved.
Maybe all doing the same and flooding the Petition center with this problem might get a response.
Luukje
The Vendetta Mercenaries
Vendetta Mercenary Group
#98 - 2016-02-14 14:40:08 UTC
Donald MacRury wrote:
I'm getting the same problem as others here. Started shortly after getting the new launcher in late December. Frequent socket is closed errors, at least once a day at random times and some days is worse than others. Everything else works on my internet perfectly fine when this happens and my isp says there is nothing wrong on their end.

I have ran several tracerts in the diagnostic tools in the launcher and usually when I have this problem there are disruptions but always on networks between my isp and ccp.


Ditto, having 4 accounts, i usually get 2 socket close at a time, never all of my accounts at once.
Made tickets about this, every response feels like a copy paste standard message "It's not us, its ur ISP". Even when you say allot of our alliance are having these issues.
3ulldog
GOODBYE EVE THANKS FOR THE FISH
#99 - 2016-02-14 19:17:28 UTC
6 socket closed anomalies so far today.
6 Petitions sent.
Did get a reply from one of them but was same automated response.
Have linked them this forum post to get my point across.
Latanai Nitsoo
Imperial Academy
Amarr Empire
#100 - 2016-02-15 20:31:27 UTC  |  Edited by: Latanai Nitsoo
Oops. Wrong topic