Pages: 1 [2] 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 .. 19 :: one page |
|
Author |
Thread Statistics | Show CCP posts - 4 post(s) |
BRooDJeRo
Cutting Edge Incorporated RAZOR Alliance
2
|
Posted - 2013.05.10 12:23:00 -
[31] - Quote
At this moment things seemed to have cleared up. I can login again with fast loads etc.
Now fingers crossed. |
MD74
No Self Esteem Invictus Void
14
|
Posted - 2013.05.10 13:51:00 -
[32] - Quote
All ok here now, lemme try logging on my second account.
may the force be with me.. |
Eternus3
Perkone Caldari State
47
|
Posted - 2013.05.10 17:58:00 -
[33] - Quote
Also having socket closed problems. Have had them in the past as well, always after a patch and not ISP related. |
Pyro Nymphomania
Praetorian Black Guard Frater Adhuc Excessum
0
|
Posted - 2013.05.10 20:14:00 -
[34] - Quote
I'm having this problem since the expansions to start the interaction with dust 514. I have played this game for going on 3 yrs very soon. I've never seen these problems til now. y is ccp not doing anything about it. its making it impossible to do anything involving combat. all I can do is mine and even thats scretchy cause it keeps dropping out making it impossible to mine very much at a time. its not as bad as some ppls but I do get a socket error every few hrs. and I am wired straight to a box with 60mbps download and 10mbps upload speed. my net is very fast and this is rediculous. I got that speed just for this game and now I'm wasting money. I'm not sure how much longer I can stand this before I just let my subscription cancel. I love this game but this just makes it where I dont even wanna bother playing when I'm on lately. |
Ines Tegator
Towels R Us
279
|
Posted - 2013.05.10 21:30:00 -
[35] - Quote
head to http://winmtr.net/ and use it to trace your network path. It should help you identify whether the problem is local or with your ISP, and can create logs that you can send your ISP as part of a complaint. - Mission Overhaul - Bridging the PVP / PVE Gap - -áIf the game stops teaching people to fear lowsec, maybe people will start going there? |
BRooDJeRo
Cutting Edge Incorporated RAZOR Alliance
2
|
Posted - 2013.05.10 23:59:00 -
[36] - Quote
This socket closed problemthread is directed at dutch Ziggo users. When you you don't live in The Netherlands and have Ziggo as ISP, then you could have a similar problem, but it's not the same issue. Keep that in mind. You need to investigate your lines and hardware first and rule out anything else. Many causes can lead to the same problem.
In this case the issue was distinctively between CCP and Ziggo, nothing else was showing issues. The funny thing is that Ziggo couldnt find anything. Maybe they did find anything, but these companies have internal rules about handing out negative information that could potentially damage the brand in economicaly heavier times. Sofar CCP says nothing, they see us talking about it and acting on it and maybe found a solution and fixed it. Maybe they didn't know either and it was related to other systems like datacenters your signal passes or new security systems on the military front on information bordercontrol. It could all be a coincidence and everything got together like Murphy's law describes.
But for me it was realy clear that around 13:00 EVE-Time somebody somewhere did something, because both my clients go from 0% functionality to 300% functionaly instantaneous.
Im very curious by nature so here I ask CCP again if they saw or did something that was related to this problem. For me it seems solved for now by one of the above reasons. Also when nothing was done or nothing could be found I would like to know to be even able to thank that person for his/hers effort and spend time. |
|
GM Karidor
Game Masters C C P Alliance
892
|
Posted - 2013.05.11 03:58:00 -
[37] - Quote
To my knowledge, there have been no changes in our network infrastructure or connectivity whatsoever, so whatever caused BRooDJeRo to be able to properly connect again has been well beyond our circle of influence.
As for the "The Socket was closed" error message I would like to share a few words, though, as there appear to be quite some misconceptions about it....
The thing with that message is that it is as generic as "Apples are fruit" and it actually means nothing other than that the connection was lost (as in: "No data could be submitted successfully for some reason", not "the server kicked you"). It is in itself not very helpful and in almost all cases is the result of the TCP protocol having to resend the same package too many times (this error happens on the network protocol layer, not in the client or server). This can happen for each connection your computer makes independently and as such it is entirely possible that only one client gets this while another one is somehow still working at the same time as it gets at least some packages through (or did not have to send anything yet).
The exact reasons for those errors can range from squeezed network cables or interference on a wireless connection to other problems somewhere along the route that neither your ISPs nor us have any direct influence on. In rare cases, this may also be the result of bandwidth starvation (i.e. when BitTorrent clients with unlimited Bandwidth usage are gobbling up your upload bandwidth completely and the client doesn't get to send the few bytes it needs to) or even traffic shaping that randomly disrupts transmissions on port 26000 (in an attempt to thwart Peer to Peer downloads, as a lot of those applications use this as default port as well).
There are a few ways that can eventually alleviate those connectivity problems, albeit all of them are very dependent on the actual issue causing it: * disconnect your router and modem from their power supplies for a few minutes to reset them and rule out problems there as much as possible, also check your network cables for any damage. * If you have access to a VPN service that lets you connect via other parts of the world, try to connect to TQ via a different route through that. Oftentimes those services will use their own infrastructure and potentially use different peering partners than your ISP for their connections, and as such this can often circumvent routing issues. * If traffic shaping on port 26000 is the case (oftentimes recognizable by the issue only popping up during a specific time of day), it is (still) possible to make the client connect to TQ through port 3724 rather than 26000. This can be changed within the "prefs.ini" that can be found in the settings folder of the client (change the line "port=26000" to "port=3724") * see the following article on the EVElopedia that provides you with some guidance for a (very) basic diagnosis of your connection to TQ: http://wiki.eveonline.com/en/wiki/Network_Guide
Last but not least I can only assure you that all of TQs connectivity hardware is heavily monitored for its performance and reliablity and that we have measures in place that will attempt to make sure that the server sends data to your client through the best available routes (there were also some dev blogs on this matter quite some time ago), as well as metrics that will inform us very early if anything in TQs connectivity that we can have an influence on is amiss. We are also constantly looking into new peering options with various providers in order to keep the routes to our servers as short as possible for everyone. GM Karidor | Senior Game Master |
|
Shaden Nightwalker
Tryblium Sanguinis
6
|
Posted - 2013.05.11 07:55:00 -
[38] - Quote
GM Karidor, thanks for the insightful clarification.
I used to be heavily affected by this problem until 2009, and none of the measures I took (including all of the above) solved the problem for me.
After hours on end of pingplotting and talking to my ISP, I could track the problem down to their end: they took in more and more end users without upgrading the infrastructure, which meant also a decrease in overall speed for me, especially in peak hours.
I bore with for some months, at which time I could even provoke the "Socket Closed" error message by simply doing a full 360 D-Scan in a populated System, after which it would take 15-30 seconds until I was disconnected with said error message.
In the end the only thing that could alleviate the problem for me was switching my ISP to Kabel Deutschland. Not one error in the last 4 years. |
BRooDJeRo
Cutting Edge Incorporated RAZOR Alliance
2
|
Posted - 2013.05.11 11:10:00 -
[39] - Quote
Thx for your answer and clarification GM Karidor. |
Melrakal
Gangbang-Gang Alpha Volley Union
2
|
Posted - 2013.05.15 16:53:00 -
[40] - Quote
Same problem with "socket closed" here...
Provider: UnityMedia (Germany)
tried to ping 87.237.38.200, no packet losses, but response times between 20 and 40ms
traceroute:
Quote: 1 55 ms 55 ms 56 ms xxx.xxx.xxx.xxx 2 53 ms 9 ms 6 ms 1512A-MX80-01-ae10-1020.gek.unity-media.net [81.210.131.133] 3 7 ms 6 ms 8 ms 1512A-MX80-02-ae0.gek.unity-media.net [80.69.107.190] 4 11 ms 7 ms 7 ms 1211F-MX960-02-ae6.dtm.unity-media.net [80.69.107.198] 5 61 ms 17 ms 14 ms 7111A-MX960-02-ae9.fra.unity-media.net [80.69.107.22] 6 * 16 ms 16 ms 7111A-MX960-01-ae0.fra.unity-media.net [80.69.107.213] 7 * * * Zeit++berschreitung der Anforderung. 8 61 ms 65 ms 76 ms de-fra01a-ri2-xe-5-1-1.aorta.net [84.116.133.114] 9 14 ms 14 ms 15 ms 84.116.132.178 10 59 ms 18 ms 13 ms 4.68.62.237 11 67 ms 21 ms 22 ms vlan70.csw2.Frankfurt1.Level3.net [4.69.154.126] 12 25 ms 23 ms 27 ms ae-72-72.ebr2.Frankfurt1.Level3.net [4.69.140.21] 13 23 ms 25 ms 21 ms ae-23-23.ebr2.London1.Level3.net [4.69.148.193] 14 25 ms 25 ms 27 ms ae-58-223.csw2.London1.Level3.net [4.69.153.138] 15 22 ms 21 ms 21 ms ae-25-52.car5.London1.Level3.net [4.69.139.102] 16 69 ms 22 ms 34 ms PACKET-EXCH.car5.London1.Level3.net [212.187.160.62] 17 22 ms 21 ms 22 ms srv250-f.ccp.cc [87.237.37.250] 18 45 ms 21 ms 21 ms srv200-g.ccp.cc [87.237.38.200]
tried it with different PC's, but after a few seconds... socket closed... also restarted Router (no changes in the last time), also reinstalled network cards...
i know some other guys from Germany having the same problem
Greetings,
Mel |
|
|
GM Karidor
Game Masters C C P Alliance
895
|
Posted - 2013.05.16 11:01:00 -
[41] - Quote
Melrakal wrote:Same problem with "socket closed" here...
Provider: UnityMedia (Germany)
tried to ping 87.237.38.200, no packet losses, but response times between 20 and 40ms
traceroute:
...
tried it with different PC's, but after a few seconds... socket closed... also restarted Router (no changes in the last time), also reinstalled network cards...
No problems with other games, just Eve...
i know some other guys from Germany having the same problem
Greetings,
Mel
Please try using the alternate port 3724 to connect to Tranqulity here by changing the prefs.ini as described in my previous post. GM Karidor | Senior Game Master |
|
Melrakal
Gangbang-Gang Alpha Volley Union
2
|
Posted - 2013.05.16 17:57:00 -
[42] - Quote
Same problem after changing port :( Also tried connecting via VPN... |
Kitty Bear
Disturbed Friends Of Diazepam Tribal Band
663
|
Posted - 2013.05.19 22:48:00 -
[43] - Quote
After having an much increased spate of disconnects, including 'we were ganked' forum time-outs I've just ran ping/tracert for extra info
Quote:ping 87.237.38.200
Pinging 87.237.38.200 with 32 bytes of data: Reply from 87.237.38.200: bytes=32 time=76ms TTL=248 Request timed out. Reply from 87.237.38.200: bytes=32 time=3893ms TTL=248 Request timed out.
Ping statistics for 87.237.38.200: Packets: Sent = 4, Received = 2, Lost = 2 (50% loss), Approximate round trip times in milli-seconds: Minimum = 76ms, Maximum = 3893ms, Average = 1984ms
Quote: tracert 87.237.38.200
Tracing route to srv200-g.ccp.cc [87.237.38.200] over a maximum of 30 hops:
1 812 ms 143 ms 2816 ms cpc1-mapp11-2-0-gw.12-4.cable.virginmedia.com [86.13.172.1] 2 1084 ms 34 ms 13 ms nott-core-2a-ae7-2367.network.virginmedia.net [62.255.214.29] 3 1212 ms 42 ms 1615 ms leed-bb-1c-ae4-0.network.virginmedia.net [62.253.174.61] 4 * * * Request timed out. 5 * * * Request timed out. 6 1283 ms 1224 ms 3163 ms tele-ic-4-ae0-0.network.virginmedia.net [62.253.174.18] 7 * * 37 ms ccpgames.com [195.66.226.23] 8 2973 ms 1033 ms * srv246-f.ccp.cc [87.237.37.246] 9 130 ms * 56 ms srv200-g.ccp.cc [87.237.38.200]
Trace complete.
none of it makes a huge amount of sense to me .. net-traffic has never been my field |
BRooDJeRo
Cutting Edge Incorporated RAZOR Alliance
2
|
Posted - 2013.05.30 15:13:00 -
[44] - Quote
I'm gradualy receiving more socket closed messages since yesterday. Only seems to be the connection to EvE again that drops. |
Ankari Lytaken
Inept Astronomics
7
|
Posted - 2013.05.30 19:36:00 -
[45] - Quote
BRooDJeRo wrote:I'm gradually receiving more socket closed messages since yesterday. Only seems to be the connection to EvE again that drops.
I have the same experience. Just wanted to add more numbers to this, in the hopes that CCP will file a complaint with some ISP that might eventually dig up the cable or reset the router that is dropping our connections.
=) |
swissboney3
Patchwork Counter Force
0
|
Posted - 2013.05.30 21:20:00 -
[46] - Quote
I've been having the same issue, and I did a ping (just like Kitty Bear), however I ran the ping for an hour, and the loss on that was unreal. I'm in the UK with Sky Broadband, and they've checked everything their end and my end and all is ok (apparently). |
Melrakal
Gangbang-Gang Alpha Volley Union
3
|
Posted - 2013.05.31 09:49:00 -
[47] - Quote
receiving socket closed messages again... no problem since my last comments here... but this morning... the same **** again. |
Michael MitchellM
Facepunch Industries
7
|
Posted - 2013.05.31 10:24:00 -
[48] - Quote
Was incursioning and half the fleet was socket closed, people in multiple countries, multiple ISPs
This has to be a CCP issue! |
Tiffgrl Donier
Hard Rock University Hearts And Minds Alliance
0
|
Posted - 2013.05.31 10:26:00 -
[49] - Quote
Came to the forums to post about this. Never had an issue with the game until this morning. |
Hybrid 808
Pyromaniacs Anonymous
0
|
Posted - 2013.05.31 10:30:00 -
[50] - Quote
Yea, I was incursioning and our Logi's and half of our DPS were unresponsive, stuck in client, sockets closed, Server status: unknown... Multiple countries, Multiple ISP's... it has to be originating from CCP and/or their servers.
Please fix soon. It hasn't happend to me EVER until within the past hour... |
|
Tectonixx
Aggressive Narcissists Circle-Of-Two
2
|
Posted - 2013.05.31 10:48:00 -
[51] - Quote
Same problems here, entire fleet and many others in alliance from all over the world so I don't think its a local issue. |
Rolix FallenOne
Minimal Solutions Aurora Irae
0
|
Posted - 2013.05.31 11:02:00 -
[52] - Quote
Today 1 hour+ before maintenance and all the time up to maintenance all of my corporation and half of alliance got the socket closed error. Not to mention some ships were destroyed in the mission in progress, some good ships.
Everyone had exactly the same error, and exactly the same behaviour after error, not able to connect to eveonline.com, not able to launch the launcher. We are from different countries, different ISP's.
It is time to start to search for problems elsewhere, not in the users ISP's or computers. |
GiantJack
Heavy Rains German Freakshow
0
|
Posted - 2013.05.31 11:02:00 -
[53] - Quote
same here 3 times today in about 40 mins CL
fix it pls |
Aconum
Dragon's of Twilight
1
|
Posted - 2013.05.31 11:03:00 -
[54] - Quote
same here, last hour, got d/c 3-4 times. |
Cydrone
EntroPrelatial Industria EntroPraetorian Aegis
1
|
Posted - 2013.05.31 11:05:00 -
[55] - Quote
This is somewhat of a necro post, so this really should get its own thread since it's apparently a separate issue.
About 40 min. before DT is when it started for me. |
Melrakal
Gangbang-Gang Alpha Volley Union
3
|
Posted - 2013.05.31 11:36:00 -
[56] - Quote
Cydrone wrote:This is somewhat of a necro post, so this really should get its own thread since it's apparently a separate issue.
About 40 min. before DT is when it started for me. Same Message, right thread ;) |
Baggam
Minmatar Ship Construction Services Ushra'Khan
0
|
Posted - 2013.05.31 11:38:00 -
[57] - Quote
We lost half our fleet to the same disconnects... Not ideal |
Jindo Minian
SteamWar
0
|
Posted - 2013.05.31 11:42:00 -
[58] - Quote
Same here. Started last night around 21:45 and hasn't let up since. The problem seems to be in London seeing as multiple ISP's in multiple countries are having it. Level3.net service, although i guess it could be Amsterdam too. Easy to prove, do Americans or the Irish route through Amsterdamn and if not, are you having the same issue? |
Bl00dyAngel
Soul Extermination X-intercept
3
|
Posted - 2013.05.31 11:50:00 -
[59] - Quote
Same here, also from Low Saxony.
Eve massaged a closed socket. The problem appears today, yesterday all was fine for me. Started to repeatedly ping tq, and in the time i got a closed socket error even a ping can't get tough.
It seams to be a routing problem. Maybe it isn't CCP's fault, but if the dc still happen cpp had i investigate future more. |
Isuki Akozzi
Aggressive Narcissists Circle-Of-Two
9
|
Posted - 2013.05.31 11:54:00 -
[60] - Quote
CCP you need to pull your fingers out of your arse and stop wasting our money. Get the damn game working. |
|
|
|
|
Pages: 1 [2] 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 .. 19 :: one page |
First page | Previous page | Next page | Last page |