Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 [20] .. 26 :: one page |
|
Author |
Thread Statistics | Show CCP posts - 6 post(s) |
Zeus Maximo
Mentally Assured Destruction Whores in space
116
|
Posted - 2013.04.15 03:40:00 -
[571] - Quote
I tried this possible fix to slow down the amount of socket closed error messages that I received but it did not work.
I would like to thank all troubleshooters in this thread so far as I have tried all of them. Ever since the patch a few months ago playing eve has become a burden..... I do hope CCP takes the blame for this and works faster on a fix! |
Zarquon Beeblebrox
Invicta.
0
|
Posted - 2013.04.15 16:26:00 -
[572] - Quote
Ive had this happening for a while now, and i realised that it only happens when im running the lowest graphical settings (due to dual accounting). If im running a single account on max settings, i have no issues at all. |
Zeus Maximo
Mentally Assured Destruction Whores in space
116
|
Posted - 2013.04.16 09:08:00 -
[573] - Quote
I tend to run 4-5 accounts daily and my socket closed errors either effect all of my accounts or just a few.
1 of my accounts is running maxed settings while the others are running minimal settings. The disconnects, for me, do not discriminate by what graphical settings I use to my knowledge. |
Chaplain Silkor
Imperial Collective
3
|
Posted - 2013.04.16 18:56:00 -
[574] - Quote
Hey,
I've been having 'socket closed' issues for quite a while now. Some days worse than others and this week begun even more terrible than usual. And so I decided to try one of the fixes proposed in here.
I'm currently trying out Lirp's Ping Plotter fix. It seems to be working. Haven't dc'd yet while using it. I'll come back in a week or so to tell you guys my final opinion about it.
Cheers
Chap
|
Zeus Maximo
Mentally Assured Destruction Whores in space
116
|
Posted - 2013.04.16 21:27:00 -
[575] - Quote
Doesnt ping plotter cost real money? I couldnt find a free trial anywhere :/ |
Tonto Auri
Vhero' Multipurpose Corp
75
|
Posted - 2013.04.16 21:31:00 -
[576] - Quote
Zeus Maximo wrote:Doesnt ping plotter cost real money? I couldnt find a free trial anywhere :/ It doesn't, but DoS'ing servers is a bad idea. |
Chaplain Silkor
Imperial Collective
3
|
Posted - 2013.04.17 20:09:00 -
[577] - Quote
Chaplain Silkor wrote:Hey,
I've been having 'socket closed' issues for quite a while now. Some days worse than others and this week begun even more terrible than usual. And so I decided to try one of the fixes proposed in here.
I'm currently trying out Lirp's Ping Plotter fix. It seems to be working. Haven't dc'd yet while using it. I'll come back in a week or so to tell you guys my final opinion about it.
Cheers
Chap
Back earlier then expected, but I got the socket error a dozen times whille running Eve together with Ping Plotter.
Gonna try some other stuff, in the meantime, here's my tracert
Microsoft Windows [versie 6.1.7601] Copyright (c) 2009 Microsoft Corporation. Alle rechten voorbehouden.
Traceren van de route naar srv92-h.ccp.cc [87.237.39.92] via maximaal 30 hops:
1 3 ms 2 ms 3 ms 192.168.1.1 2 12 ms 12 ms 12 ms bras05.sn.be.edpnet.net [213.219.132.17] 3 12 ms 11 ms 11 ms router01.sn.be.edpnet.net [212.71.11.61] 4 16 ms 15 ms 15 ms router03.adamtel.nl.edpnet.net [212.71.1.225] 5 61 ms 23 ms 16 ms er1.ams1.nl.above.net [195.69.144.122] 6 * 15 ms 17 ms xe-1-0-1.mpr1.ams10.nl.above.net [64.125.22.237] 7 16 ms 15 ms 17 ms xe-1-2-1.cr1.ams10.nl.above.net [64.125.22.41] 8 42 ms 27 ms 20 ms xe-4-0-0.mpr1.lhr2.uk.above.net [64.125.24.73] 9 21 ms 26 ms 22 ms xe-8-3-1.mpr2.lhr3.uk.above.net [64.125.24.122] 10 22 ms 21 ms 23 ms 213-152.240-250.PXu259.above.net [213.152.240.250] 11 21 ms 21 ms 23 ms srv250-f.ccp.cc [87.237.37.250] 12 24 ms 22 ms 29 ms srv92-h.ccp.cc [87.237.39.92]
De trace is voltooid.
|
CaptainMac
IMMORTALS
0
|
Posted - 2013.04.20 06:00:00 -
[578] - Quote
This particular thread was commenced in May 2012......and clearly is continuing. In speaking to many of my Eve friends, they are experiencing "closed socket" problems......to varying degrees of experience.
My experience is that I could no longer play either of my two main characters (each just under 100m SP) on my two accounts, as one cannot play in null sec when continually being disconnected. However, Eve has been part of my life for so long now, I started playing an alt on each account......totally juniors.......just to get my 'Eve fix'.
Now I can no longer even play those characters, as I am getting disconnected every 2 mins on either account. Like most of the people who have taken the time to add something to this thread, I played around to the extent of my knowledge, in order to try and over come this problem. I found that this is the only game that behaves this way........ I also found that I have a reasonable ping to the server (87.237.38.200)................
Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>ping 87.237.38.200
Pinging 87.237.38.200 with 32 bytes of data: Reply from 87.237.38.200: bytes=32 time=323ms TTL=234 Reply from 87.237.38.200: bytes=32 time=347ms TTL=234 Reply from 87.237.38.200: bytes=32 time=348ms TTL=234 Reply from 87.237.38.200: bytes=32 time=344ms TTL=234
Ping statistics for 87.237.38.200: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 323ms, Maximum = 348ms, Average = 340ms
C:\Windows\system32>
..............especially considering I am playing the game from Australia. Nor is a trace a great deal of help, as it seems to me that testing in a very small section of time, fails to pick up the source of this problem:-
Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>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 (null).iiNet [10.1.1.1] 2 97 ms 29 ms 72 ms nexthop.vic.iinet.net.au [203.215.7.251] 3 100 ms 63 ms 68 ms te7-2.mel-pipe-bdr1.iinet.net.au [203.215.6.10]
4 168 ms 41 ms 97 ms xe-7-1-11-0.syd-ult-core1.on.ii.net [203.215.20. 102] 5 39 ms 42 ms 40 ms unknown.telstraglobal.net [134.159.126.189] 6 131 ms 154 ms 168 ms i-0-7-1-0.sydo-core02.bi.telstraglobal.net [202. 84.223.1] 7 189 ms 274 ms 178 ms i-0-2-0-2.1wlt-core01.bx.telstraglobal.net [202. 84.140.21] 8 282 ms 337 ms 268 ms i-0-4-0-0.eqla01.bi.telstraglobal.net [202.84.25 1.174] 9 222 ms 433 ms 369 ms gblx-peer.eqla01.pr.telstraglobal.net [134.159.6 3.202] 10 450 ms 374 ms 466 ms 204.245.39.42 11 331 ms 327 ms 323 ms srv246-f.ccp.cc [87.237.37.246] 12 372 ms 322 ms 322 ms srv200-g.ccp.cc [87.237.38.200]
Trace complete.
C:\Windows\system32>
I read a thread in the Whirlpool forum ( http://forums.whirlpool.net.au/archive/1593590 ) in which a comment from a CCP representative was quoted:-
"It is more than a tad annoying on our side as well. There is an important principle of network theory called the End to End Principle GÇô which essentially states that it is the endpoints that make protocol decisions, and only the endpoints. However, as so often happens, the nice tidy world of network theory meets real life, and it doesn't all quite work out as the designers intended. The ISP's doing this kind of filtering is a violation of that principle, a somewhat necessary one from their perspective, but still.
As CCP Sreegs has explained, we changed our protocol exchange to improve it a little, and discovered it was being used as an identifier for EVE traffic. It was never intended for that purpose, and nobody asked us if it would be a good idea to use it for that.
If you contact your ISP, this should be an easy issue for them to fix on their side. Ask them to contact us, at [email protected] and we will provide any assistance they need. This sort of thing happens fairly frequently unfortunately. There's a lot of sorting out behind the scenes that goes on between ISP's and network providers that isn't usually exposed to public view."
Clearly a change was made on the CCP end to "improve it a little" in that well quoted patch, but as a result of the unseen or inexperience as to the consequences.....it failed to "improve it a little".......rather it has worsened it for many many Eve lovers.
I also contacted my ISP..........and managed to find an interested tech.........and gave him all that I knew about this problem...including the CCP email contact; [email protected].
Meanwhile.....I appear to be paying for two accounts.......for a service, if you will...........but am failing to receive the service at a level that would generally be held by the community as fair and appropriate. My feeling is, that should this problem not be fixed shortly (this thread gives an indication as to how long it's been a problem), then I would be justified in asking for a return of the cost of this failed service.
For interest..I am running a gaming machine , the build of which, was completed a few months back. It is watercooled and sits in a Silverstone TJ11 case. It includes an Asus 1155 Extreme MB....an Intel 3770K.....16 gigs of Corsair platinum......two EVGA 690 hydrocopper video cars. My delta temp is between 1.5C and 4.5C. I am connected via ADSL and my speed varies between 3400 and 4000,
Cheers..................
|
Tonto Auri
Vhero' Multipurpose Corp
84
|
Posted - 2013.04.20 09:41:00 -
[579] - Quote
For me, it was not the case for any filtering, rather, a local issue with EVE trying to pretend that it know more about network protocols, than it supposed to care. I.e. it should not be affected by checksum ofloading mechanism, which is designed to save the CPU time and do this work on hardware instead, but evidently, disabling this oprimization stopped an issue from happening on my end. |
Sky Marshal
Deep Core Mining Inc. Caldari State
3
|
Posted - 2013.04.24 14:59:00 -
[580] - Quote
Hi,
I don't play much since months, but I noticed than since Retribution, I have now some closed socket errors each time I play. It can happen at any moment, whatever the situation (docked, outside, no shoot, etc.). I didn't have this problem before the last expansion.
My ISP is Free in France, I have a 20 Mbits connection (a pretty stable one btw) and I am located at less than 500 meters from the dslam... My ping to the Tranquillity server is nearly constantly at 32 ms (on 166 tries, 6% goes > 30 but < 60)...
I don't know if CCP did something or if it is a mere coincidence and my ISP screwed it in fact, but something is wrong... I also wonder if Hamachi don't cause this problem so I will try to disable it to test. Until then, I can't really play beside standard hauling missions... and that is annoying |
|
Marty MacGyver
Center for Advanced Studies Gallente Federation
0
|
Posted - 2013.04.25 09:50:00 -
[581] - Quote
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. |
Altrue
Exploration Frontier inc
358
|
Posted - 2013.04.25 14:03:00 -
[582] - Quote
We've had socket closed twice, one today and one yesterday, at the same time, me and a friend living in the same city.
Don't know if it can be of some use, but it proves that it is certainly not caused by your local modem or anything. G££ <= Me |
leyo690
Asocial Club
8
|
Posted - 2013.04.26 10:14:00 -
[583] - Quote
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. |
Puissant
Tempora Heroica
6
|
Posted - 2013.04.26 16:57:00 -
[584] - Quote
I see this silly argument in the English Help channel all the time:
How many of you are using Wireless to connect to your Router at home? The solution is simple: Get Wired!
EVE Client is sensitive to dropped packets. Wireless is notorious for dropping packets. There's usually nothing wrong with your internet access ckt / cable modem / router / CCP server when you get the socket error and you are connecting to your home router wirelessly -- getting wired will solve your issues.
I've seen many people posting here saying they don't have issues with closed socket errors on their desktops but they do on their laptops. Why? Because they are relying on a solid wireless connection (which is almost impossible now that everyone has neighbors with wireless).
Get wired, folks. |
Oli Ala
Pane e Panelle
0
|
Posted - 2013.04.27 19:05:00 -
[585] - Quote
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 |
Jace Itinen
Red.Dot
0
|
Posted - 2013.04.29 18:19:00 -
[586] - Quote
I have started getting this socket closed crap today. I played for 7 hours yesterday without a single disconnect. I've been disconnected today over 20 times in 3 hours. The game is unplayable at this point. I am staying logged off for awhile. Looks like WoW gets my money today. |
Kaelnor Heidan
Supermassive Singularity
0
|
Posted - 2013.05.01 17:16:00 -
[587] - Quote
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" ? |
Reppyk
Yarrbear Inc. BricK sQuAD.
412
|
Posted - 2013.05.03 07:10:00 -
[588] - Quote
Confirming that I'm still getting socket errors and I'm a Free customer as well. I AM SPACE CAPTAIN REPPYK. -áI AM A LOWSEC GANKER, HIGHSEC SCUM, NULLSEC BASTARD, WORMHOLE INVADER. Welcome to, welcome to, welcome to my scramble. GÖÑ |
Mac deKiev
Elemental Souls Invictus Void
0
|
Posted - 2013.05.10 13:09:00 -
[589] - Quote
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
|
Minty Aroma
The Metalocalypse is Coming
3
|
Posted - 2013.05.10 17:51:00 -
[590] - Quote
Since the patch, I can't stay logged on for more than a minute or two before getting a socket closed error - how is this resolved? |
|
Ines Tegator
Towels R Us
279
|
Posted - 2013.05.10 18:53:00 -
[591] - Quote
Lirp wrote: #524 Posted: 2013.03.04 20:42 | Report So I have stumbled across something that has worked for me the last 2 days with NO disconnects at all..
I have been running Ping Plotter against CCP server IP 87.237.38.200 with the following settings-
Sampling= Unlimited Trace Interval= 1 sec Samples to include= ALL
I am running all 3 of my accounts on the same system with no Socket Disconnect problems. But if I try and play without PP running I get disconnected right away.
This is a strange workaround, but at least I can play!
Lirp out...
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. - Mission Overhaul - Bridging the PVP / PVE Gap - -áIf the game stops teaching people to fear lowsec, maybe people will start going there? |
QUIZZA
CRANK INC.
19
|
Posted - 2013.05.14 05:51:00 -
[592] - Quote
I am having this Farkin problem too, I'm in Australia and continue to play other online games without problems. I have 4 accounts and may not be playing much longer unless you fix it.
Pissed off.
|
Cebraio
4S Corporation RAZOR Alliance
299
|
Posted - 2013.05.15 11:21:00 -
[593] - Quote
QUIZZA wrote:I am having this Farkin problem too, I'm in Australia and continue to play other online games without problems. I have 4 accounts and may not be playing much longer unless you fix it.
Pissed off. 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. |
Kaelnor Heidan
Supermassive Singularity
2
|
Posted - 2013.05.20 14:55:00 -
[594] - Quote
My socket closed errors seem to have disappeared since last patch. |
Cosmo Blink
Blue Republic RvB - BLUE Republic
0
|
Posted - 2013.06.01 12:41:00 -
[595] - Quote
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? |
Tuberider
Blue Republic RvB - BLUE Republic
0
|
Posted - 2013.06.01 15:01:00 -
[596] - Quote
Game is unplayable i'm constantly getting socket closed on all 3 accounts on different pc's.
ITS NOT MY ISP its related to the the last launcher update.
We went down this road of denial 4 years ago CCP, please sort your **** out |
Tuberider
Blue Republic RvB - BLUE Republic
0
|
Posted - 2013.06.02 09:10:00 -
[597] - Quote
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. |
Tuberider
Blue Republic RvB - BLUE Republic
0
|
Posted - 2013.06.02 10:37:00 -
[598] - Quote
I by passed the new launcher completely by using the EXE from the bin folder and guess what. I'm still connected after 30 mins and all 3 accounts are running well.
Not a launcher issue ? will see how long it lasts |
Cosmo Blink
Blue Republic RvB - BLUE Republic
0
|
Posted - 2013.06.08 15:18:00 -
[599] - Quote
ok this is just getting old ffs I want to play this game -.- I'm just dcing every minute |
caelestis calametis
Arms Unlimited Academy
1
|
Posted - 2013.06.09 10:18:00 -
[600] - Quote
CCP Sputnik wrote:Sladd Manos wrote:I was also having this issue. I tried restarting my laptop, modem, and router, none of that helped. I realized I began having the problem after I started using steam. I opened task manager and steam was running in the background. Ended that process and havent had the error since. Can somebody else verify that Steam is causing Close Socket errors?
i have steam installed aswell but at the time of my socket closures i twas never running as a process. |
|
|
|
|
Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 [20] .. 26 :: one page |
First page | Previous page | Next page | Last page |