| Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 30 40 50 .. 52 :: one page |
| Author |
Thread Statistics | Show CCP posts - 8 post(s) |

Marlona Sky
D00M. RED.OverLord
|
Posted - 2010.04.27 07:47:00 -
[1381]
just lost 5x augmented ogres on my mission alt due to this socket bull****. thanks ccp! 
|

Ender Locke
|
Posted - 2010.05.12 22:30:00 -
[1382]
Just staretd playing again and have gotten this error ALL day today. litterally every 5 minutes.
|

Eraggan Sadarr
Phoenix Tribe Cult of War
|
Posted - 2010.05.29 00:42:00 -
[1383]
I have had this problem too for ages (Think it was after Quantum Rise). It seems that my router is dropping packets from the eve server (87.237.38.200):
Quote: May 29 02:12:11 unknown user.warn kernel: DROP IN=vlan1 OUT= MAC=00:11:95:0e:a7:bf:00:11:22:33:44:55:08:00:45:00:00:29 SRC=87.237.38.200 DST=[My IP] LEN=41 TOS=0x00 PREC=0x00 TTL=115 ID=29024 DF PROTO=TCP SPT=26000 DPT=1912 WINDOW=63928 RES=0x00 ACK URGP=0
But i really have no clue why. I know that i don't get the socket closed when i put the machine in the DMZ zone. So they must have changed something in the socket implementation after QR.
Eve Market Scanner - Marketlog comparisons |

Archon Grimnir
|
Posted - 2010.05.29 03:53:00 -
[1384]
wahoo. the socket closed error is back again. this is NOT a router issue. been fine on dominion for months. not a single socket error. tyrannis comes out and im getting nailed with them left and right. sometimes its an hour between socket close errors. and sometimes its as little as five minutes. had 4 of them in the past hour or two. its starting to **** me off.
its like they brought back apocrypha. 
|

Healer Axim
|
Posted - 2010.05.29 12:23:00 -
[1385]
Eraggan, can you try upping your TCP timeouts? try something rediculously high.
see my post here: http://www.eveonline.com/ingameboard.asp?a=topic&threadID=1038603&page=12#351
|

Eraggan Sadarr
Phoenix Tribe Cult of War
|
Posted - 2010.05.29 22:50:00 -
[1386]
Edited by: Eraggan Sadarr on 29/05/2010 22:50:55 No problem!! I solved it, for me at least. It turns out that my router was blocking some DHCP packets from my ISP's DHCP server, which in turn would result in a restart of dnsmasq running on the router. That in turn would result in the firewall blocking the eve server IP.
I found my solution here: http://www.genmay.com/showthread.php?t=822727
And i solved it by creating the following firewall rules in the Web UI (Administration>Scripts>Firewall) in my linksys WRTGL541.1 router, with tomato firmware 1.27:
Allow my specific ISP DHCP server ports: iptables -I INPUT -p UDP -i vlan1 --dport 68 --sport 67 --source <Your_DHCP_server_IP> -j ACCEPT
Allow TCP traffic from the EVE server: iptables -I INPUT -p TCP -i vlan1 --sport 26000 --source 87.237.38.200 -j ACCEPT
Hope this helps anyone.
Eve Market Scanner - Marketlog comparisons |

Tehrock
|
Posted - 2010.06.01 21:57:00 -
[1387]
Originally by: Eraggan Sadarr Edited by: Eraggan Sadarr on 30/05/2010 00:39:15
No problem!! I solved it, for me at least. It turns out that my router was blocking some DHCP packets from my ISP's DHCP server, which in turn would result in a restart of dnsmasq running on the router. That in turn would result in the firewall blocking the eve server IP.
I found my solution here: http://www.genmay.com/showthread.php?t=822727
And i solved it by creating the following firewall rules in the Web UI (Administration>Scripts>Firewall) in my linksys WRTGL541.1 router, with tomato firmware 1.27:
Allow my specific ISP DHCP server ports: iptables -I INPUT -p UDP -i vlan1 --dport 68 --sport 67 --source <Your_DHCP_server_IP> -j ACCEPT
Allow TCP traffic from the EVE server: iptables -I INPUT -p TCP -i vlan1 --sport 26000 --source 87.237.38.200 -j ACCEPT
Hope this helps someone.
I haven't the slightest idea how to do this with my router. The most I can do is port forwarding/triggering, and that doesn't have an option to enter the EVE server ip like the KB article suggests, only open up a port on your router.
|

Needle Juice
Interstellar Brotherhood of Gravediggers
|
Posted - 2010.06.02 03:38:00 -
[1388]
i normally run 2 or 3 accounts on the same comp at once, and since tyrannis, i get 1 account that drops out every 5 minutes or less... nothing has changed on my end, and i have no firewalls or restrictions.
has there been any statement by ccp for any of these issues? in bed |

clide1
|
Posted - 2010.06.02 18:19:00 -
[1389]
same here i get my socket closed all the time and i pvp alomnsot every secodn the day and when your screen syas secket clsoed right in middle of a fight welll thats not good
|

Eraggan Sadarr
Phoenix Tribe Cult of War
|
Posted - 2010.06.02 20:21:00 -
[1390]
Edited by: Eraggan Sadarr on 02/06/2010 20:22:32
Originally by: Tehrock
Originally by: Eraggan Sadarr Edited by: Eraggan Sadarr on 30/05/2010 00:39:15
No problem!! I solved it, for me at least. It turns out that my router was blocking some DHCP packets from my ISP's DHCP server, which in turn would result in a restart of dnsmasq running on the router. That in turn would result in the firewall blocking the eve server IP.
I found my solution here: http://www.genmay.com/showthread.php?t=822727
And i solved it by creating the following firewall rules in the Web UI (Administration>Scripts>Firewall) in my linksys WRTGL541.1 router, with tomato firmware 1.27:
Allow my specific ISP DHCP server ports: iptables -I INPUT -p UDP -i vlan1 --dport 68 --sport 67 --source <Your_DHCP_server_IP> -j ACCEPT
Allow TCP traffic from the EVE server: iptables -I INPUT -p TCP -i vlan1 --sport 26000 --source 87.237.38.200 -j ACCEPT
Hope this helps someone.
I haven't the slightest idea how to do this with my router. The most I can do is port forwarding/triggering, and that doesn't have an option to enter the EVE server ip like the KB article suggests, only open up a port on your router.
Well, it realy depends on your router and router firmware, but the commands i gave are really just firewall rules that allow certain ip adresses and ports, much like your port forwarding, only this is in the firewall on the router.
iptables -I INPUT -p UDP -i vlan1 --dport 68 --sport 67 --source <Your_DHCP_server_IP> -j ACCEPT translates to: Open for UDP traffic from <Your_DHCP_server_IP> port 67 to <your_router> port 68. - the trick here is to get the ip of your ISP's DHCP server. If in doubt call them. I found mine in the router log.
iptables -I INPUT -p TCP -i vlan1 --sport 26000 --source 87.237.38.200 -j ACCEPT translates to: Open for TCP traffic from 87.237.38.200 port 26000 to <your_router> port ANY. - where 87.237.38.200 is the IP of the eve server
Don't know if that helps you.
Eve Market Scanner - Marketlog comparisons |

Toshiro Hasegawa
Caldari Phoenix Rising Incorporated
|
Posted - 2010.06.02 23:22:00 -
[1391]
Edited by: Toshiro Hasegawa on 02/06/2010 23:24:38 i got the issue too .. just getting starting to look into it. pretty sure only experienced it tonight after update. -
History is the Study of Change |

Bla QuaZebra
Oberon Incorporated Morsus Mihi
|
Posted - 2010.06.03 19:55:00 -
[1392]
Originally by: Toshiro Hasegawa Edited by: Toshiro Hasegawa on 02/06/2010 23:29:15 Edited by: Toshiro Hasegawa on 02/06/2010 23:24:38 i got the issue too .. just getting starting to look into it. pretty sure only experienced it tonight after update.
dito
|

Jita alternative
|
Posted - 2010.06.06 16:49:00 -
[1393]
I'm getting the lost connection socket closed about 20 sec after I get in game.
My ping is fine on speedtest.net and other online games dont seem to have problems.
|

Myke Falkon
|
Posted - 2010.06.07 00:28:00 -
[1394]
Got the same problem...the socket is closed...I thought I was having connection issues, so I bypassed my router. Still having problems so I went to my internet provider (cable company) and got a new modem. Problem remains, so I had a service technician come out today and check my wiring, all was fine. Played a good bit today with no crashes, but then suddenly at about 8 pm my socket was closed again...real annoying!
|

Jocca Quinn
Matari BackBone Fate Weavers
|
Posted - 2010.06.07 12:37:00 -
[1395]
I have had this issue on and off for at least a year (if not more). What I do is once I get the first disconnect I run a constant ping to the Eve server, that (usually) stops it happening again (for me at least).
ping -l 1 87.237.38.200 -t
JQ none of us are free as long as one of us is chained none of us are free |

Dead Cal
Macabre Votum Morsus Mihi
|
Posted - 2010.06.07 15:04:00 -
[1396]
Ever since the expansion launched, I've been getting this socket error with disconnects. However, it only seems to happen when I have my goddamn drones out and every single time I lose every last one. It's NOT my ISP, as this game "worked" before the expansion. At least enough so that it was playable. Now it is not.
|

Gorgoth Amadeus
Helljumpers
|
Posted - 2010.06.08 08:14:00 -
[1397]
I'm getting the socket closed error all the time this morning it seems. I can be logged in for a few minutes, or just a few seconds some times. I've never experienced any problems like this before. It seems more likely to crash when I'm logged in on multiple accounts at the same time. And all my accounts get logged of at the same time on different computers.
|

HRYEA
|
Posted - 2010.06.12 11:14:00 -
[1398]
NOW THIS IS P***ING ME OFF NOW socket closed socket closed socket closed socket closed socket closed every 2 mins off the day been doing this for a few days NOW how can we play while this happen's i never had this prob's in last patch at all and its not my internet that is FINE my freind down the road he dont have this probs what the hell is going on i run the same thing's as my freind dose grrrrr GRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR
|

Aclyn Seriy
Gallente Hollow World Mining Corporation
|
Posted - 2010.06.14 02:25:00 -
[1399]
grrrr, cant login, when i do i get dosconnected and now i cant stay logged into the damn forums. not bloody impressed to be honest.
Originally by: Slinkus Gallentus They're actually in free fall but they keep missing the earth.
|

Cutter Isaacson
Minmatar wiggle Tech. MPA
|
Posted - 2010.06.14 11:04:00 -
[1400]
PLEASE WOULD SOMEONE FROM CCP PAY ATTENTION. Thanks, hopefully you noticed that. Now, this socket closed error is really getting on my nerves, constant disconnects and now a complete inability to login at all. I ran the log server and I get one particular message that stood out from the rest
"Creating Closed Packet: The socket was closed exception:error(10054, 'Connection reset by peer', 'IOCompletionWsaGetOverlappedResult failed with error 10054: An existing connection was forcibly closed by the remote host.\r\n')"
Can someone from CCP please tell me what this means?? And don't bother asking me for a petition or a bug report, I've had to login into the website 3 dozen times or more in the last 24 hours just to post one reply on a thread. It took me 4 hours to post a new thread and I really don't have the patience for it today.
Originally by: Haks'he Lirky Some people should just stick to Pac Man.
|

Miss Steeley
Wrong Indeed
|
Posted - 2010.06.14 14:46:00 -
[1401]
can not log in, i get socket closes on character selection after selecting a character to log into. Highly annoying as im on my lunch break.... tried repairing client etc ----------------------------------------------- Vote Mynxee for CSM |

CommanderShepard1
|
Posted - 2010.06.15 00:25:00 -
[1402]
CCP, Please fix this! The game is unplayable, as soon as i get in the game it gets the socket closed error and happens every time i log on and been doing so since yesterday...This is very annoying and making me very very angry. 
|

sgt 808
Caldari Blanchards Innovative Technologies
|
Posted - 2010.06.15 11:20:00 -
[1403]
i gotta tell ya i was getting kicked off using an aircard but my fix is open the help channel in game for some reason it keeps me ingame never kicked off again works for me maybe for you too anyway good luck
|

Gareth Walker
|
Posted - 2010.06.15 21:23:00 -
[1404]
Same here.
Suddenly getting kicked out of EVE all the time with the socket closed message since the last patch. I have noted a solution given by a poster regarding technical changes to a router. I know a little about computers but that solution was way too technical to be of any use. I can't find anything official from the makers of the game, except a thread where they seem to say "Not our problem". If it's my problem then fair enough, but how about giving me some suggestions on how I might fix it!
Is there anywhere you can register your problem with CCP and provide them with details of your setup. I've had a very frustrating morning on the game today.
|
|

CCP Warlock

|
Posted - 2010.06.16 16:15:00 -
[1405]
Quote: "Creating Closed Packet: The socket was closed exception:error(10054, 'Connection reset by peer', 'IOCompletionWsaGetOverlappedResult failed with error 10054: An existing connection was forcibly closed by the remote host.\r\n')"
Can someone from CCP please tell me what this means??
Strictly it means that there has been some kind of network interruption somewhere between your host computer and CCP's servers. Unfortunately, that's all it means - because of an infelicity in the underlying software, almost all network events are currently mapped to a single error message, which we fully recognise is extremely unhelpful to everybody. That is on the release plan to fix.
More generally on these errors. We did (finally) manage to track down and fix a problem for some players, that was being caused by home routers taking down the network connection because of a lack of network activity on it. The Eve client simulation is extremely efficient, and there can be times in game where there isn't any network traffic at all between your client and Eve's cluster for several minutes, which was triggering NAT timeouts on some home routers. This is strictly a violation of the end to end principle in networking, but NAT routers have their own set of problems to solve, and some of the boxes use very aggressive timeout periods. We solved that by turning on the TCP KEEPALIVE flag.
That leaves us with a situation where although we're fairly sure that remaining instances of this problem are probably on the client side, we can't be absolutely sure. As I said, we're currently working on putting improved network reporting in to the client. The GM's also have a checklist they will go through with you, and if necessary we will ask you to get us a wireshark trace that we can use for troubleshooting. So although i know you don't want to hear this, if you are experiencing consistent problems connecting to TQ, a petition is the best way to start getting it sorted out. Especially if it's the first time connecting, or if connection to Eve has never worked before on that computer.
In general - this is the Internet - nothing is guaranteed to work 100% all the time. Often when things have been working, and then don't work, it's because of some kind of transient problem in the routers and connections between the two endpoints. Most network maintenance by the backbone providers is done at weekends, so if your connection suddenly doesn't work on a Sunday evening, don't be at all surprised if it's fine on Monday.
Occasionally, there are also ISP related problems that occur at around the same time every day. There are a few ISP's that force a regular DHCP address update, and that can cause a disconnect. Occasionally there's a problem on one of the big trunks into the Eve cluster, and that can cause thousands of players to be dropped. Usually though, ISP related problems won't be occurring just with Eve, there will be other symptoms like web pages not loading.
We have some plans to try and address transient connectivity issues, beyond just improving their visibility on the client. In the meantime though, I would ask that you keep reporting any persistent problems, bearing in mind what I've said above. I do understand how frustrating these problems are.
|
|

Suyer
|
Posted - 2010.06.18 02:50:00 -
[1406]
Edited by: Suyer on 18/06/2010 02:55:00 As far as ISP related problems go, what can we do about those?
Sometimes I can play EVE perfectly fine, and other times as soon as I logon and try to load something up (like a contract list etc...) I get a socket closed error message. And it happens again, and again, and again over and over and over again for hours on end. At the same time I see IRC disconnecting occasionally, clearly meaning it's not on CCP's end.
However, I can still view all websites perfectly fine, and it almost seems like the disconnects I get are just little blips. I don't know how to deal with this, reseting the router etc... doesn't do any thing, and even while running a constant ping to the TQ server, I get disconnects but see nothing in the ping log thingy or whatever.
I have comcast internet if that matters.
Edit: I'm now seeing timed out messages in the command prompt, but they happen for only a short bit, then the connection is resumed. But the eve client seems to be unable to deal with this. Is there anything I can do about that? Or do I just have to sit here and QQ because comcast sucks and has probably oversold their network. :( |

VicturusTeSaluto
Metafarmers MeatSausage EXPRESS
|
Posted - 2010.06.18 19:37:00 -
[1407]
I keep getting the socket is closed since the latest expansion. Can't find any issue on my end, connection seems to be solid to everything other than eve.
|

Scorpio IV
|
Posted - 2010.06.18 23:06:00 -
[1408]
Can someone tell me how to run a constant ping in CMD?
I'm on win7 if that matters at all.
|

Trinity Faetal
Gallente Burn The Witch
|
Posted - 2010.06.19 02:50:00 -
[1409]
Originally by: Scorpio IV Can someone tell me how to run a constant ping in CMD?
I'm on win7 if that matters at all.
add -t switch after the adres like ping 127.0.0.1 -t ----------------------------------- woot, free zephyr, ccp won me back. |
|

CCP Warlock

|
Posted - 2010.06.21 10:41:00 -
[1410]
Originally by: Suyer Edited by: Suyer on 18/06/2010 03:47:21 Edited by: Suyer on 18/06/2010 02:55:00 As far as ISP related problems go, what can we do about those?
<snip> Edit: I'm now seeing timed out messages in the command prompt, but they happen for only a short bit, then the connection is resumed. But the eve client seems to be unable to deal with this. Is there anything I can do about that? Or do I just have to sit here and QQ because comcast sucks and has probably oversold their network. :(
Edit #2: Upon further inspection, the socket closed error seems to be distinct from the timed-out pings. I just got a slew of socket closed messages after logging in multiple times, but both my IRC and the pinging had no issues.
One thing just to check - if you or anybody on the same home network as you, is doing any kind of download in the background (bittorrent, etc.) - you may want to rate throttle it down so that it's not grabbing all the bandwidth.
Otherwise, it sounds like something is flaking out intermittently, but it could be anything. If at all possible, the next time this happens, could you get a Wireshark trace, and send it into the GM's, and we'll have a look at it.
We are planning to put in some better handling for small drop outs like this, but that won't be available for a while.
|
|
| |
|
| Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 30 40 50 .. 52 :: one page |
| First page | Previous page | Next page | Last page |