Issues, Workarounds & Localization

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

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

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.

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....

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 but EVE was online... 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.

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.

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

Can only say: 2 times socket closed within 5 min.

Getting extremely bored of this problem

Again 2 time socket closed.