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) |
Bumbum George
|
Posted - 2008.12.04 16:44:00 -
[91]
Originally by: GM Retrofire See if the following works for any of you.
In Windows press the Windows button + R and in the command window type cmd and press enter
In the terminal window type "netsh winsock reset catalog" without the "
This will reset your Winsock protocols and prompt you to restart your computer, after you've restarted see if you are able to connect to EVE again.
tried it, didn't work!
i'm playing on to computers at the same time, both get the closed socket error simultaneously, always. i've reset the winsock protocols on both computers today, got the first socket close after about 30 min of playing
i sure hope there will be a fix for that problem soon, till then no more eve for me
|
Rusty Nals
Amarr Empire Logistics and Holding Co.
|
Posted - 2008.12.04 20:28:00 -
[92]
Originally by: GM Retrofire See if the following works for any of you.
In Windows press the Windows button + R and in the command window type cmd and press enter
In the terminal window type "netsh winsock reset catalog" without the "
This will reset your Winsock protocols and prompt you to restart your computer, after you've restarted see if you are able to connect to EVE again.
Well Tried it yesterday and it "Seemed" to work" I had no problems for approx 6 hours today and then it started again when the server reached 32,000 users..both accounts.. Running cach size at medium setting....Hope this gets fixed soon!!! It has severely limited a lot of players from doing what they normally do...
|
ardik
GoonFleet GoonSwarm
|
Posted - 2008.12.04 22:46:00 -
[93]
Originally by: ardik i got this error like 4 times in an hour, then i changed cache from small to high or whatever its called. havent had any issues since.
seriously this works, send me isk for solving all your probs tia
|
Rramar Claime
Amarr Task Force Zener Atlas Alliance
|
Posted - 2008.12.04 22:51:00 -
[94]
Originally by: ardik
Originally by: ardik i got this error like 4 times in an hour, then i changed cache from small to high or whatever its called. havent had any issues since.
seriously this works, send me isk for solving all your probs tia
This might explain why i dont have this problem since the last patch where they say they corrected the mem leak and we can use high memory settings again. Will check if i get dc with low mem settings Still its a problem for htose who dont have 3 or more gigs of memory i guess.
------- "I cherish the memories of a question my grandson asked me the other day, when he said; 'Grandpa, were you a hero in the war?' Grandpa said, 'No, but I served in a company of heroes." |
Goldfrapp
|
Posted - 2008.12.05 13:27:00 -
[95]
Well for over 24 hrs i sat in station doing nothing but some chat now and then and all was fine. Today i decided to venture out of station right after DT and within 30 mins socket closed came up. Ive changed cache from small to high and back again and it hasnt helped me sadly so its back to sitting in station again for me.
|
Rramar Claime
Amarr Task Force Zener Atlas Alliance
|
Posted - 2008.12.05 21:18:00 -
[96]
Just got socket closed again, so the high memory settings didnt fix it.
------- "I cherish the memories of a question my grandson asked me the other day, when he said; 'Grandpa, were you a hero in the war?' Grandpa said, 'No, but I served in a company of heroes." |
Blue Puppet
Eve University Ivy League
|
Posted - 2008.12.06 16:29:00 -
[97]
Bump
Still waiting for a fix for this
|
Rusty Nals
Amarr Empire Logistics and Holding Co.
|
Posted - 2008.12.06 17:46:00 -
[98]
Here we go again...Total login time before Socket Close 3 minutes...
|
Auri Hella
Downwind Trading Guild
|
Posted - 2008.12.06 20:15:00 -
[99]
Lost connection a dozen or so times today because of this. Can't do anything because of it, I disconnect every half hour (at best). Suffice to say I severely dislike this and would welcome a fix other than the useless one the GM suggested.
Sigh.
|
Princess Ventil
Gallente The Undertakers
|
Posted - 2008.12.07 11:25:00 -
[100]
BUMP!
|
|
THE R3APER
No Slack
|
Posted - 2008.12.07 16:18:00 -
[101]
I am having the socket closed problem on my laptop running windows XP on a wireless connection (right next to the modem though). I however am not having this problem on my macintosh with lepoard on a wired connection. I haven't done anymore troubleshooting on this yet. -------------------- NO BREATHER FROM WORK NO RELIEF FROM COMBAT NO REQUEST FOR RESPITE NO SLACK! |
Piotr Varens
|
Posted - 2008.12.07 18:15:00 -
[102]
According to the last post by THE R3APER, where everything runs smoothly on Leopard, I believe this StacklessIO's implementation is not Microsoft friendly. I wouldn't be surprised that majority (if not all) Linux players don't have such problems.
I moved Friday on Vista 64 and things went worse, all my applications over the net disconnected regularly. EVE was just losing connection with server within 10 minutes. So I spent few hours doing my homeworks and I fixed it, all is running well now. Beside the MTU issue, it looks like that there is more latency on client side mainly because packets are getting more filtered by some security softwares, it's the impression I have, it is more related to client OS settings. If this is the case, it won't be an easy one.
If this could be of any help, here are the operations I did: XP and Vista64 Fixed MTU XP Only Never used integrated security solutions, nor Jack-of-all-trades products Vista64 only - deactivated IPv6 and QoS (this might not be needed), turned off Windows Firewall and BitDefender and using Webroot Firewall only, others are on demand only. Updated network drivers (a must)
And please send bug reports people.
|
Blue Puppet
Eve University Ivy League
|
Posted - 2008.12.08 22:33:00 -
[103]
Bump
|
Astro Glyde
|
Posted - 2008.12.09 04:51:00 -
[104]
BUMP
CCP, can we have a remedy, please?
It's been almost a month since I dare undock! HALP!!! |
Poor Decision
|
Posted - 2008.12.09 07:54:00 -
[105]
same problem here, netsh winsock reset catalog didn't help.
Cheers, Anc
|
Poor Decision
|
Posted - 2008.12.09 08:11:00 -
[106]
i am getting a socket closed issue as well, the specific error reported in Log Server is Socket Error 10054 -- some googling revealed this is a server-side connection drop but I can't figure out why. I am going to attempt to change my cache size as suggested above...
... hmm i have to be logged in to change the cache size ...
bug report and log server lbw to follow
|
BullEyesTBE
|
Posted - 2008.12.09 10:33:00 -
[107]
Hi just came back from 5 moths sailing wanted to play some eve finaly but cleaned up the pc first with a complete new istallation
installed game and every thing and every 2 to 3 min socked closed and i see i'm not the only one with the problem hope it get fixed soon because after 5 moths missing eve and back home i can note play again whell it feels like being put in the ground alive it scary
|
|
CCP Casqade
|
Posted - 2008.12.09 15:32:00 -
[108]
Hi all.
"Socket closed" is a generic connection error.
Those of you who are experiencing this please send us a bug report. What we need is two things:
1. Ping plotter results from 15 minutes or more before the "Socket Closed" error occurs and 15 minutes after it occurs. - Please let us know the time the disconnection took place 2. Logserver logs from when you got the "Socket closed". - This log has to be from the same time as the ping plotter so make sure you run them at the same time and note it down in the bug report, when it occurs.
Several people have already sent in bug reports, but none with the above mentioned information detailed.
Information about ping plotter:
Download available at http://www.pingplotter.com/downloads/pngplt_2.exe If you are running a hardware firewall (SPI Firewall) on your router you will need to disable it, as otherwise this program won't work.
After starting up pingplotter do the following in the program:
1) Under "Adress to trace" put the following value in the box: 87.237.38.200 2) In the bottom left corner in the box "# of times to trace" put the value 1500 3) In the bottom left corner in the box "Trace Intervals" change it to 2.5 seconds 4) In the bottom left corner in the box "Samples to include" change it to 1500. 5) Click on "Trace" button in the bottom left corner.
Remember: You need to run this minimum 15 minutes before and after the "socket closed" error occurs.
6) Then save the file as a sample set. 7) Compress it using winzip or winrar. 8) Attach it to the bug report together with the logserver log.
Information about Logserver:
Can be found here: http://oldforums.eveonline.com/?a=topic&threadID=585921
|
|
Rramar Claime
Amarr Task Force Zener Atlas Alliance
|
Posted - 2008.12.10 17:07:00 -
[109]
Originally by: CCP Casqade
Several people have already sent in bug reports, but none with the above mentioned information detailed.
I was in the middle of my petition, ive sent in several ping plotter results, and while i was still gathering logserver results the petition closed (automatically it seems) cause i didnt reply within one week. Kinda hard to help you guys fix it when you close the petition, and i didnt see it anywhere that i'd have to reply within a week.
Well nevermind i think i wont bother with it again cause it took me too long to even accept the fact that the "socket closed" disconnects are not related to our ISPs and only appear since QR is out. Not to mention the copy paste default messages i received like i was talking to robots who didnt even read what i wrote, even better they didnt understand a word of it. (like i wrote down about a thousand times how random the dc is and then asking me to reproduce and write down the exact steps how i got the dc was kind of ... well it makes you a bit angry)
Was too much effort to "play" beta testing for eve, with all the epic buglist i wrote in my thread. So ... well... lets hope i wont get it that often again. And good luck to you devs for fixing it.
------- "I cherish the memories of a question my grandson asked me the other day, when he said; 'Grandpa, were you a hero in the war?' Grandpa said, 'No, but I served in a company of heroes." |
Kassa Daisho
|
Posted - 2008.12.10 18:20:00 -
[110]
Bump this thread since I don't want to start another one. I'm having a similar issue with the same error message but in my case I've never been kicked off the server, I've just not able to log in for over 12 hrs.
If anyone finds a solution for this please let me know.
|
|
Riddick Richard
|
Posted - 2008.12.10 20:38:00 -
[111]
Bump
Still getting the socket was closed(had those since QR was launched). Petitioned for few times and end result from gm was that it's my isp fault not ccp's. Friend of mine who also plays eve tried to play at my apartment and had no issues(he's running xp and i have a 32bit vista) in whole weekend.
|
Rramar Claime
Amarr Task Force Zener Atlas Alliance
|
Posted - 2008.12.10 22:08:00 -
[112]
Originally by: Rid**** Richard Bump
Still getting the socket was closed(had those since QR was launched). Petitioned for few times and end result from gm was that it's my isp fault not ccp's. Friend of mine who also plays eve tried to play at my apartment and had no issues(he's running xp and i have a 32bit vista) in whole weekend.
My advice for those stupid copy paste replies is you stand up for yourself and dont be afraid to rage out. Not necessarily cause hes evil but every worker is lazy as hell, especially those dealing with customers. If they think they can get away with it they WILL f*** you up and tell you to go to your ISP although its pretty obvious that EVE changed with QR and not the whole world's ISPs changed at the same moment QR came out. Of course its nice to think eve can influence the behaviour of THE Internet but...
Dont forget they do look at you like the last dumb 5 year old boy on the world, just dont let yourself get fooled and stand up for yourself if its THAT obvious they are wrong. If he can close the petition and finish his job cause you will start bothering the ISP rather than him then who the hell would like to work and try to fix the problem. everybody would love to go home to their wife and kids and it will take a few months for you and the same ***hole employees at the ISP to figure out the problem is also not on their side.
In the end all the failures they make will have to make them realize that not even their ubermegaamazing marketing campaign can keep up with the unsatisfied customers telling all their friends about eve online...
But. Bumping wont help. Keep gathering info about the disconnects and saving them in logserver and pingplotter and then attaching them to the bugreport and the petition.
------- "I cherish the memories of a question my grandson asked me the other day, when he said; 'Grandpa, were you a hero in the war?' Grandpa said, 'No, but I served in a company of heroes." |
Kassa Daisho
|
Posted - 2008.12.10 22:50:00 -
[113]
Edited by: Kassa Daisho on 10/12/2008 22:52:38 Nvm, just realized the reply wasn't to me.
|
reznik
|
Posted - 2008.12.11 00:58:00 -
[114]
http://www.dslreports.com/routerwatch/hbg-bb2-link.telia.net
So I'm runing Ping Plotter and it CHOKES on: ldn-bb2-pos6-0-0-.telia.net ldn.b4-link.telia.net and then has consistent packet loss from the eve servers at about 10%WTF?
I'm dropping all the time.
|
Alericom
|
Posted - 2008.12.11 06:44:00 -
[115]
I also have this same problem. I'm running eve on 2 computers, one pc wired and the other laptop wireless. I concurrently run ventrillo while playing and notice the disconnect first from the noise vent makes when it disconnects; since eve doesnt immediately give me the socket error until I press escape and try to log off. The only thing eve does immediately is not let me change any current orders and seems to freeze but allows you to open menus just not make any selections, mining drones even continue to mine and cycles continue on my strip miners, just no yields. I can escape to the logout screen and logout normally though and this is when i get the socket error. I am always able to log back in, but sometimes lately I have been placed in que to get back on. I found this strange because the number of people on at the time changes. I have been in que with as few as 25000 people on or as many as 35000 people on. Also on several occassions I will minimize eve to check another program and I see 2 copies of eve running instead of one. I think this is because I have eve set to auto restart after a disconnect. What I have noticed though is that if I close the second copy of eve on the computer I get the socket error again at a random time later, but if I leave the second copy running I have yet to get another socket error. I also use to run 2 clients on the same computer and never had this problem until I got my laptop and started running them on seperate computers. Not sure if that helps though. I've tested my modem and the router and they are fine with the most up to date drivers installed. I've noticed different pings when this problem occurs also, seems pretty random to me. I'm gona try the 3 fixes mentioned in these forums and see how they change the data even though everyone is saying they dont work completely just make the error occur less often. The 3 fixes sound silly to me but hey I'll try anything once. Maybe eve will fix this issue soon and we can all go back to pew pewing each other, hehe. Anyways fly safe and good luck guys.
|
yonpytr
Amarr
|
Posted - 2008.12.11 23:13:00 -
[116]
This bug is very random, some days i don't get any, some days (like today) i get several disconnects, but it began with the QR patch.
It's very annoying to get disconnected in the middle of a mission and hoping the ship is not destroyed. drones should get back to the drone bay automatically if you get the socket closed message or at least they should not be attacked by npc rats. I already have had a bs reimbursed because i lost it because of this bug, but the drones lost in space are not covered.
If i do all the data gathering and reporting, will i get a reimbursement of my lost drones?
|
Navtiqes
Noob Mercs
|
Posted - 2008.12.12 23:39:00 -
[117]
Edited by: Navtiqes on 12/12/2008 23:42:51 Back for 5 days now. Got the socket disconnect thing like 6 times in 15 minutes now, never seen it earlier.
You're not getting a ping plot. That's the generic request places like Blizzard forums and Sony demands to keep your attention away from the fact that something isn't running right in the game. Sorry for sounding hostile though, just putting it bluntly :) We're not 14 year old tools. We're old tools :P
But if it helps, it seems as though EFT and Evemon are unable to connect with the API during the socket induced disconnect. |
Jahlina Kantar
|
Posted - 2008.12.13 06:47:00 -
[118]
Same here. Classic. Killer computer and internet connection. Never had an issue with eve, or any online game for that matter.
Was excited to be back in eve. One of the selling points was this wizz bang new server they were boasting about. Eve always performed well for me, apart from the odd crazy fleet fight. So I thought it would be even slicker now!
The eve server seems to be horrible. Stuff lags out for 60 seconds at a time for no apparent reason. Getting randomly disconnected like crazy. Takes ages to get past the log in screen (if at all).
>>> eve is simply unplayable <<<
And I'm a pretty patient person when it comes to MMO's. I'm realistic about lag. If it doesn't improve by next billing cycle, I probably wont resubscribe. I'm paying for a service that I cannot even use.
|
Zorglubos
|
Posted - 2008.12.13 12:46:00 -
[119]
Edited by: Zorglubos on 13/12/2008 12:46:48 Hi,
Same problem. Random disconnects.
Socket error.
No problem before patch. Since patch -> Problems.
Game is unplayable.
|
Zfactor
United Federation of Technocracy Movement
|
Posted - 2008.12.13 13:03:00 -
[120]
Same problem here. Before last patch there were no problems. I noticed, while I get this Socket close thing and my Eve client is rebooting, I cannot resolve http://eve-online.com as well. No answer. Any other URL works perfect, only Eve-online wont resolve.
|
|
|
|
|
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 |