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) |
caelestis calametis
Arms Unlimited Academy
1
|
Posted - 2013.06.09 10:27:00 -
[601] - Quote
i have since found a workaround for it though. when i was making a bug report with info from screenshots and such ping command caught it as i was in the middle of cycling it to show my father how the cmd (ping -t)prompt was recording things.
so after pressing ctrl-c to end the continuous pings it summarized the information i showed it to him and then i restarted it
( this all the while i had eve in the background running)
so i restarted the cmd and i it turned on right in the middle of the event of the socket closures cause. ( this is in my bug report on the matter)
it told me destination net ( the IP address) was un-reachable for several seconds then told me time out and started to record good quality packets. but rated the info with minimal packet loss despite the destination unreachable chunks.
so i have run this cmd program ever since when ever i played EVE and something interesting has happened...
i haven't had socket closures while this cmd was running. when i earlier caught it with this program the cmd program was
not running i managed to luckily(lucky timing wise not application wise) restart it when the error was occurring.
to prove this i ran eve one day and forgot to run the cmd ping program on TQ's server IP address.
not un-coincidentally the socket closure made its return. having turned the cmd program back on every time i play eve socket closures are gone.
i dont know how
i have a W.A.G on the why
and i dont know if it will work for you.
INSTRUCTIONS IN WINDOWS 7 TERMINOLOGY ( CONVERT TO YOUR OWN OPERATING SYSTEM AS NEEDED)
1.goto your windows key or task manager.
2a. in the search program or files box type cmd and hit enter
2b. for task manager go to file drop box and click run... type cmd there and hit enter
3. if you have completed steps 1 and 2 you should have a small black background window with simplified programmer UI
4. type with no alterations and minus the brackets (ping 87.237.38.200 -t) remember no brackets and space only where
spaced in between them. the ping tells it to ping something.
the address tells it where to send these packetss.
the -t at the end makes it do it until you tell it to stop with ctrl-c
5. start eve through the launcher. while this is running in the back ground. it takes almost no cpu to run this so unless your
running eve on a K-pro you should be fine.
6. profit???????????
7. close eve after a hardcore night of screwing over your fellow man out of his iskies with internet spaceships
8. select cmd prompt window press control C to end the ping series it will summarize how many packets were sent how many weren't , your minimum ping ( in ms) avg ping, and maximum ping.
now as to the wild a**ed guess on why this works for me.
a long time ago i used to play wow on a different computer. there was a script going around that modifed your network in an effort to reduce lag.
it stated ( it may have been full of crap) that your computer sent and returned packets in pairs instead of 1-1. so when a game server sent you a packet it looked like this conversation.
server : hello computer : ........ server : are you there? computer : yeah I'm here whats up? server : why didn't you answer me the first time? computer : ...........
the cycle would continue like that more or less through out your game sessions. so he had a modified script that converted your computer from responding in pairs to responding to each and every individual packet/ping from a game server.
so the convo would then look like this
server : hello computer : hello server : status? computer : logging in. server: success
now while this is not exactly accurate on how a server talks to your computer it illustrates the lag in packet pairing responses.
now the socket closures, i think we can all agree, is eve terminating the connection because it thinks your either De-synching with the game client or disconnected / timing out.
i suspect eve/client sends regular pings to your computer/server confirming that it is logged in along with every other
action that generates a packet. ( im probably wrong as im explaining this as what it is a wild guess) so then something
occurs and your stop sending these confirmation packets that tell TQ that your online eve then promptly cuts the connection
closing the socket.
so i theorize that the socket closures dont happen during a game session with this cmd prompt because eve is
receiving status packets from the cmd prompt.
they may not have any relevant data but maybe its enough for the client to
see that im still sending continuous data and am connected.
end of eve technical amatueristic tomfoolery manual....
if this fix works for you reply if it doesn't state your OS and some relevant info so we might see if there is a pattern to this
weirdness.....
hope this works for you as well as it works for me still confuzzled, caelestis calametis |
Zak Breen
Breen Enterprises
108
|
Posted - 2013.06.09 12:27:00 -
[602] - Quote
CCP has stated several times that the "socket closed" error is just a general way of saying "hey, the server is unreachable, sorry". It doesn't mean it is CCPs fault OR your fault. It could be a lot of things.
It's like trying to diagnose why a cable modem keeps dropping the signal. Bad splitters? Bad modem? Bad line in or out of the house? Bad connections at the wall? Or it could be a problem within the area itself or the main hub at the cable company. The internet is very complicated and one weak link inbetween your computer and CCPs servers could cause it. Maturity, one discovers, has everything to do with the acceptance of not knowing. http://www.di.fm/spacemusic |
caelestis calametis
Arms Unlimited Academy
1
|
Posted - 2013.06.09 20:05:00 -
[603] - Quote
well i don't know that its a hardware problem( at least not for everyone) for me if this ping cmd running in the background causes my back to back to back socket closures to not occur
what we need to do is compile a list thread for all the different workarounds(confirmed to work for them) into one area and call it the socket closure fix list or something. then if those dont fix your problem then see devs |
Jita Cleanupcrew
Shadowland Rangers Eternal Syndicate
0
|
Posted - 2013.06.10 15:17:00 -
[604] - Quote
caelestis calametis wrote:i have since found a workaround for it though. when i was making a bug report with info from screenshots and such ping command caught it as i was in the middle of cycling it to show my father how the cmd (ping -t)prompt was recording things.
so after pressing ctrl-c to end the continuous pings it summarized the information i showed it to him and then i restarted it
( this all the while i had eve in the background running)
so i restarted the cmd and i it turned on right in the middle of the event of the socket closures cause. ( this is in my bug report on the matter)
it told me destination net ( the IP address) was un-reachable for several seconds then told me time out and started to record good quality packets. but rated the info with minimal packet loss despite the destination unreachable chunks.
so i have run this cmd program ever since when ever i played EVE and something interesting has happened...
i haven't had socket closures while this cmd was running. when i earlier caught it with this program the cmd program was
not running i managed to luckily(lucky timing wise not application wise) restart it when the error was occurring.
to prove this i ran eve one day and forgot to run the cmd ping program on TQ's server IP address.
not un-coincidentally the socket closure made its return. having turned the cmd program back on every time i play eve socket closures are gone.
i dont know how
i have a W.A.G on the why
and i dont know if it will work for you.
INSTRUCTIONS IN WINDOWS 7 TERMINOLOGY ( CONVERT TO YOUR OWN OPERATING SYSTEM AS NEEDED)
1.goto your windows key or task manager.
2a. in the search program or files box type cmd and hit enter
2b. for task manager go to file drop box and click run... type cmd there and hit enter
3. if you have completed steps 1 and 2 you should have a small black background window with simplified programmer UI
4. type with no alterations and minus the brackets (ping 87.237.38.200 -t) remember no brackets and space only where
spaced in between them. the ping tells it to ping something.
the address tells it where to send these packetss.
the -t at the end makes it do it until you tell it to stop with ctrl-c
5. start eve through the launcher. while this is running in the back ground. it takes almost no cpu to run this so unless your
running eve on a K-pro you should be fine.
6. profit???????????
7. close eve after a hardcore night of screwing over your fellow man out of his iskies with internet spaceships
8. select cmd prompt window press control C to end the ping series it will summarize how many packets were sent how many weren't , your minimum ping ( in ms) avg ping, and maximum ping.
now as to the wild a**ed guess on why this works for me.
a long time ago i used to play wow on a different computer. there was a script going around that modifed your network in an effort to reduce lag.
it stated ( it may have been full of crap) that your computer sent and returned packets in pairs instead of 1-1. so when a game server sent you a packet it looked like this conversation.
server : hello computer : ........ server : are you there? computer : yeah I'm here whats up? server : why didn't you answer me the first time? computer : ...........
the cycle would continue like that more or less through out your game sessions. so he had a modified script that converted your computer from responding in pairs to responding to each and every individual packet/ping from a game server.
so the convo would then look like this
server : hello computer : hello server : status? computer : logging in. server: success
now while this is not exactly accurate on how a server talks to your computer it illustrates the lag in packet pairing responses.
now the socket closures, i think we can all agree, is eve terminating the connection because it thinks your either De-synching with the game client or disconnected / timing out.
i suspect eve/client sends regular pings to your computer/server confirming that it is logged in along with every other
action that generates a packet. ( im probably wrong as im explaining this as what it is a wild guess) so then something
occurs and your stop sending these confirmation packets that tell TQ that your online eve then promptly cuts the connection
closing the socket.
so i theorize that the socket closures dont happen during a game session with this cmd prompt because eve is
receiving status packets from the cmd prompt.
they may not have any relevant data but maybe its enough for the client to
see that im still sending continuous data and am connected.
end of eve technical amatueristic tomfoolery manual....
if this fix works for you reply if it doesn't state your OS and some relevant info so we might see if there is a pattern to this
weirdness.....
hope this works for you as well as it works for me still confuzzled, caelestis calametis
Only thing this changes is that I get 1 "socket was closed" window instead of 2.
|
Eight Bit
Volition Cult The Volition Cult
0
|
Posted - 2013.06.11 08:27:00 -
[605] - Quote
Just wanted to mention that I too have socket closed issues. I play other more constant stream critical games, (like quake live) with no problems at all.
I-Śm wired on a cable connection of 50mbit. Usually have no problems at all. |
Sentinari
Senti Global Holdings
0
|
Posted - 2013.06.13 18:48:00 -
[606] - Quote
I've been seeing this error for the first time ever in all my years of playing Eve. Even when playing at my parents on AOHell (AOL)
I followed all the instructions and downloaded PingPlotter and set it running on the IP for Tranquillity.
Sorry CCP, but guess where I saw the packet loss. On Tranquillity srv200-g.ccp.cc (87.237.38.200)
PingPlotter was reporting about 10% packet loss.
I've taken a screen shot, but was unable to paste it in here.
I'm with Fast.co.uk and never had any problems with them as an ISP. In fact I highly recommend them to anyone.
I did also notice some packet loss further up the chain as I left PingPlotter running, bdr6.lon-th1.as8401.net (195.82.97.239)
I also tried using ROG Game First II and giving maximum priority to the Eve clients network packets.
I haven't been able to connect properly now since the Retribution Patch.
Tracert for infomation,
1 <1 ms <1 ms <1 ms [192.168.1.1] 2 31 ms 31 ms 31 ms 88-212-191-131.rdns.as8401.net [88.212.191.131]
3 30 ms 31 ms 30 ms bdr6.lon-th1.as8401.net [195.82.97.239] 4 152 ms 31 ms 31 ms ge-5-2-0-1105.ar3.lon2.gblx.net [204.246.200.5]
5 31 ms 31 ms 33 ms 204.245.39.42 6 32 ms 30 ms 31 ms srv246-f.ccp.cc [87.237.37.246] 7 32 ms 31 ms 31 ms srv200-g.ccp.cc [87.237.38.200] |
Lord Damo Boirelle
Killing is Business Get Off My Lawn
2
|
Posted - 2013.06.14 10:00:00 -
[607] - Quote
Whats going on ccp, it's getting like cod or battlefield with the consumers trying to fix your problems, so far i have missed out on 3 killmails and nearly lost my cane twice. 3 disconnects in 1 hour and its not my computer its your game.... |
Tuberider
Blue Republic RvB - BLUE Republic
0
|
Posted - 2013.06.14 16:28:00 -
[608] - Quote
I been ok all week then it hits the weekend and bam can't keep any of my accounts connected for more than a couple of mins.
started pinging the server like suggested and guess what all 3 accounts are stable. WTF! |
Sky Marshal
Deep Core Mining Inc. Caldari State
8
|
Posted - 2013.06.14 17:51:00 -
[609] - Quote
I get some "socket was closed" since Retribution. I didn't get them before, or so rarely that I didn't notice them.
Just few minutes ago, I was outside helping a neighbour for some computer problems... Once returned, I see that I got one closed socket. There was a good moment since the last time... But with something different :
I had TWO clients launched, both was docked in the same station, but only ONE of them got this error. The second one was fine and is still online right now. I loaded the market and do stuff to check if it wasn't just apparent, and I got no problem.
|
Tuberider
Blue Republic RvB - BLUE Republic
0
|
Posted - 2013.06.15 10:08:00 -
[610] - Quote
FIX this ******* issue please |
|
Sentinari
Senti Global Holdings
0
|
Posted - 2013.06.16 07:04:00 -
[611] - Quote
Here is what I've tried,
CMD line ping 87.237.38.200 -t while running the game client. Restart all networking equipment. Ensure PC is the only thing attached to my network
Now here is what I've found to work for me.
My game was being started with the launcher. I thought just on the off chance I'll find the main .exe and start with that,
(Install Location)CPP\EVE\bin\ExeFile.exe
Starts the game the old fashioned way so you login once the client starts.
I'm going to keep testing this just in case it truely is a network issue somewhere beyond our ISPs. I know recently BT had rather a lot of cabling stolen which caused a major network outage. Could this still be affecting customers, I don't know. |
Tuberider
Blue Republic RvB - BLUE Republic
0
|
Posted - 2013.06.16 08:58:00 -
[612] - Quote
Sentinari wrote:Here is what I've tried,
CMD line ping 87.237.38.200 -t while running the game client. Restart all networking equipment. Ensure PC is the only thing attached to my network
Now here is what I've found to work for me.
My game was being started with the launcher. I thought just on the off chance I'll find the main .exe and start with that,
(Install Location)CPP\EVE\bin\ExeFile.exe
Starts the game the old fashioned way so you login once the client starts.
I'm going to keep testing this just in case it truely is a network issue somewhere beyond our ISPs. I know recently BT had rather a lot of cabling stolen which caused a major network outage. Could this still be affecting customers, I don't know.
Worked for a while for me too but now it just kicks any of my clients after a couple of mins on this too. I didn't last long enough to say Hi in corp chat
|
Tuberider
Blue Republic RvB - BLUE Republic
0
|
Posted - 2013.06.16 10:06:00 -
[613] - Quote
After using the pingplotter the only packet loss i get is from 'eveonline-ic-138015-ldn-b3.c.telia.net' ip= '213.248.83.198'
i'm pretty sure theres nothing i or my ISP can do to fix this CCP |
Tuberider
Blue Republic RvB - BLUE Republic
0
|
Posted - 2013.06.16 10:24:00 -
[614] - Quote
Downloaded and Installed a fresh client with none of my old settings to see how long that would last. Typed one line in corp then 'Socket Closed'
Getting extremely frustrated that i can't play a game i'm PAYING for. Wasting my own valuable time to trying to fix a problem lots are suffering from and nothing its seems is being done about. |
Col Angel
10TH Wolf Brothers of Tangra
0
|
Posted - 2013.06.16 10:43:00 -
[615] - Quote
Can only say: 2 times socket closed within 5 min. |
Tuberider
Blue Republic RvB - BLUE Republic
0
|
Posted - 2013.06.16 10:48:00 -
[616] - Quote
log in and the moment i say anything in any chat windows its 'socket closed' |
OptionalExtra
Pothouse Cartel
0
|
Posted - 2013.06.16 10:54:00 -
[617] - Quote
Getting extremely bored of this problem |
Tuberider
Blue Republic RvB - BLUE Republic
0
|
Posted - 2013.06.16 11:18:00 -
[618] - Quote
Well DT didn't fix it
I'd like a refund for the subs for the last month please Its only fair since i've had no game to play and yet you took my money anyway |
Col Angel
10TH Wolf Brothers of Tangra
0
|
Posted - 2013.06.16 12:56:00 -
[619] - Quote
Again 2 time socket closed. |
Sakura Tse
Native Freshfood Minmatar Republic
0
|
Posted - 2013.06.16 20:08:00 -
[620] - Quote
2 different machines, 2 different ISPs, same issue, random socket errors (from minutes to hours). Very annoying. |
|
Col Angel
10TH Wolf Brothers of Tangra
0
|
Posted - 2013.06.16 20:24:00 -
[621] - Quote
Target Name: www.eve-online.com IP: 87.237.39.91 Date/Time: 6/16/2013 10:20:22 PM
1 0 ms 0 ms 0 ms 0 ms [192.168.1.1] 2 * * * * [-] 3 N/A N/A 10 ms 8 ms transit-01-gs.zeelandnet.nl [82.176.63.254] 4 12 ms * * 11 ms GigabitEthernet3-7.ar4.AMS2.gblx.net [64.212.225.65] 5 N/A 18 ms * 19 ms [204.245.39.38] 6 735 ms 19 ms 19 ms 20 ms srv250-f.ccp.cc [87.237.37.250] 7 704 ms 20 ms * 18 ms srv91-h.ccp.cc [87.237.39.91]
Ping statistics for www.eve-online.com Packets: Sent = 4, Received = 3, Lost = 1 (25.0%) Round Trip Times: Minimum = 18ms, Maximum = 704ms, Average = 247ms |
Tuberider
Blue Republic RvB - BLUE Republic
0
|
Posted - 2013.06.17 16:08:00 -
[622] - Quote
Weekends over and now i got no connection issues WTF |
Sakura Tse
Native Freshfood Minmatar Republic
0
|
Posted - 2013.06.17 21:09:00 -
[623] - Quote
Today unusally normal, without these discos. |
Tuberider
Blue Republic RvB - BLUE Republic
0
|
Posted - 2013.06.18 16:23:00 -
[624] - Quote
Oh well back to not being able to connect for more than a couple of mins. Nothing changed at my end since yesterday when i had no disconnects |
Alkatosh Moz'tazul
THE AESIR. Get in the Van.
1
|
Posted - 2013.06.19 00:48:00 -
[625] - Quote
Col Angel wrote:Can only say: 2 times socket closed within 5 min.
Same thing here...this was after patch...
1. I restart the game 2. I restart my computer 3. I turn the circuit breaker to where it's sets
and instead of 5 minutes, now I'm disconnected the moment I entered the game... |
Tuberider
Blue Republic RvB - BLUE Republic
0
|
Posted - 2013.06.19 14:02:00 -
[626] - Quote
Found an issue with my internets. Where all though i'm with Orange, i'm connected not with my external IP to tranq but via an IP address associated with BT. This IP does not show up during a Traceroute which is weird.
Until i can get to chat with someone who isn't indian and can understand what i'm saying its hard getting Orange to understand what the issue is. |
Sentinari
Senti Global Holdings
0
|
Posted - 2013.06.23 19:26:00 -
[627] - Quote
Tuberider wrote:Found an issue with my internets. Where all though i'm with Orange, i'm connected not with my external IP to tranq but via an IP address associated with BT. This IP does not show up during a Traceroute which is weird.
Until i can get to chat with someone who isn't indian and can understand what I'm saying its hard getting Orange to understand what the issue is.
My disconnection problems have disappeared just as quickly as they started.
Some routers are programmed not to respond with a name. This is done on purpose to prevent certain information from being exposed.
I escalated my issue after an initial ticket being placed with CCP. The last few patches may have had a fix or CCP may have pushed harder with their ISP to trace were the issue is.
Hopefully many others have had their disconnections resolved.
Fly Safe. |
ELGORDIO
Zero Atmosphere Ex Cinere Scriptor
1
|
Posted - 2013.06.24 00:11:00 -
[628] - Quote
I've had this issue for 2 days now, nothing has changed from when it didnt happened till now.
I have 10 accounts and 2 computers with different modems connected to each (same ISP, 2x independant internet connections)
weirdly, only 1 of them is the one having the problem, checked with ISP, no issues on their side, changed all my infrastructure, cables/routers/modems/etc... still happening, cant be online for more than 10 minutes if much.
Just now, i barely made it to the character selection screen on the accounts having the issue, and BAM! socket closed...
Opened a petition since yesterday, i woulda tought this kind of issus regarding connections should be CCP's priority, as we are NOT getting the game we paying for.
I cant enjoy the game by connectiong sessions of 10 minutes with 5 min downtime (Server status unknown (Offline mode)) after each socket closed error
Literally, if this keeps happening CCP will end up losing at least 10 subscriptions from me, and perhaps many others that wont bare with the 4 years of not being able to fix this issue.
im willing to provide logs and what not, but either way, if the tracet log is not hlpful i would like to know WHAT is.
P.S. really 4 years and still happening? shoulda been more than enough time for CCP and their "l33t team" to fix it or at least provide a workaround |
Tuberider
Blue Republic RvB - BLUE Republic
0
|
Posted - 2013.06.24 10:39:00 -
[629] - Quote
Amazing
Since the latest patch i'm having no issues at all, strange that seeing as it was supposed out of CCP's hands (according to them) Probably spoke to soon, after reactivating my accounts again yesterday it will be broken tonight.
I live in hope its fixed but i bet Red fed don't |
Chizad
Turalyon Plus
0
|
Posted - 2013.06.25 01:27:00 -
[630] - Quote
I have had this problem a lot, even after Odyssey. However, as silly as it sounds, if I ping Tranquility before I start the game and leave it pinging, I have never gotten another socket closed error. Any time I forget to do this I always get the socket closed error.
I think it forces the hit to avoid lost packets. Not sure but it works for me, perhaps it will work for you too. |
|
|
|
|
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 |