open All Channels
seplocked Issues, Workarounds & Localization
blankseplocked The socket was closed ?!?!
 
This thread is older than 90 days and has been locked due to inactivity.


 
Author Topic

Xantor Bludberry
Amarr
Posted - 2008.10.08 13:49:00 - [1]
 

Edited by: Xantor Bludberry on 08/10/2008 13:50:24
Typing pass and get message "The socket was closed". What is goin on? I cant connect about an hour. Help me what to do!!
Cant login whit classic and premium clients.

Xantor Bludberry
Amarr
Posted - 2008.10.08 14:24:00 - [2]
 

Edited by: Xantor Bludberry on 08/10/2008 15:10:52
Help me somebody! I just cant log in. Even when I use wrong login and password I get same message: "The socket was closed".
I loggid out in Isenairos, as I remember, near Saila.

CCP Lingorm


C C P
Posted - 2008.10.08 14:45:00 - [3]
 

open a windows command line and run the following commands.

Ping 87.237.38.200
tracert 87.237.38.200

post the results to this forum.

Xantor Bludberry
Amarr
Posted - 2008.10.08 15:09:00 - [4]
 

1 <1 мс <1 мс <1 мс 192.168.1.1
2 66 ms 64 ms 40 ms mcc-nso.38.ncc.sibirtelecom.ru [213.228.116.38]
3 39 ms 40 ms 39 ms mcc-nso.233.ncc.sibirtelecom.ru [213.228.117.233]
4 39 ms 40 ms 40 ms mcc-nso.206.ncc.sibirtelecom.ru [213.228.117.206]
5 68 ms 67 ms 69 ms kyk15.kyk25.transtelecom.net [217.150.50.14]
6 200 ms 196 ms 195 ms linx.telecityredbus.net [195.66.224.82]
7 200 ms 198 ms 200 ms 85.90.226.205
8 200 ms 198 ms 194 ms 532-dist65-01.lon3.telecity.net [217.20.44.226]
9 180 ms 185 ms 183 ms ipt-ccp-games-1-as35834.lon3.telecity.net [217.2
0.44.138]
10 191 ms 190 ms 194 ms 87.237.38.200

C:\WINDOWS>ping 87.237.38.200
Обмен пакетами с 87.237.38.200 по 32 байт:
Ответ от 87.237.38.200: число байт=32 время=190мс TTL=252
Ответ от 87.237.38.200: число байт=32 время=207мс TTL=252
Ответ от 87.237.38.200: число байт=32 время=192мс TTL=252
Ответ от 87.237.38.200: число байт=32 время=195мс TTL=252
Статистика Ping для 87.237.38.200:
Пакетов: отправлено = 4, получено = 4, потеряно = 0 (0% потерь),
Приблизительное время приема-передачи в мс:
Минимальное = 190мсек, Максимальное = 207 мсек, Среднее = 196 мсек

Sorry, only russian Windows, I`ll hope you`ll can get it.

Xantor Bludberry
Amarr
Posted - 2008.10.08 15:13:00 - [5]
 

I just create WoW trial acc. Log in whithout problems. But I dont want to play WoW, its bored! :( :( Sad

CCP Lingorm


C C P
Posted - 2008.10.08 15:16:00 - [6]
 

Edited by: CCP Lingorm on 08/10/2008 15:17:35
Originally by: Xantor Bludberry
1 <1 мс <1 мс <1 мс 192.168.1.1
2 66 ms 64 ms 40 ms mcc-nso.38.ncc.sibirtelecom.ru [213.228.116.38]
3 39 ms 40 ms 39 ms mcc-nso.233.ncc.sibirtelecom.ru [213.228.117.233]
4 39 ms 40 ms 40 ms mcc-nso.206.ncc.sibirtelecom.ru [213.228.117.206]
5 68 ms 67 ms 69 ms kyk15.kyk25.transtelecom.net [217.150.50.14]
6 200 ms 196 ms 195 ms linx.telecityredbus.net [195.66.224.82]
7 200 ms 198 ms 200 ms 85.90.226.205
8 200 ms 198 ms 194 ms 532-dist65-01.lon3.telecity.net [217.20.44.226]
9 180 ms 185 ms 183 ms ipt-ccp-games-1-as35834.lon3.telecity.net [217.2
0.44.138]
10 191 ms 190 ms 194 ms 87.237.38.200

C:\WINDOWS>ping 87.237.38.200
Обмен пакетами с 87.237.38.200 по 32 байт:
Ответ от 87.237.38.200: число байт=32 время=190мс TTL=252
Ответ от 87.237.38.200: число байт=32 время=207мс TTL=252
Ответ от 87.237.38.200: число байт=32 время=192мс TTL=252
Ответ от 87.237.38.200: число байт=32 время=195мс TTL=252
Статистика Ping для 87.237.38.200:
Пакетов: отправлено = 4, получено = 4, потеряно = 0 (0% потерь),
Приблизительное время приема-передачи в мс:
Минимальное = 190мсек, Максимальное = 207 мсек, Среднее = 196 мсек

Sorry, only russian Windows, I`ll hope you`ll can get it.



OK, everything appears to be running fine, the only thing I can think of is that some other server along the way is closing the port (blocking/restricting) the EVE uses.

Have you tried checking with your ISP (internet Service provider) and seeing if that are blocking port 26000? as that is the port EVE uses.

Also check this Knowledge Base Article for instruction on how to instruct EVE to use the same port as WOW.

Xantor Bludberry
Amarr
Posted - 2008.10.08 15:37:00 - [7]
 

Edited by: Xantor Bludberry on 08/10/2008 15:36:56
Change port. Dont work anyway. I can see the number of players on login screen, and EVEmon is working too, but just cant log in. ugh

/Trying to connect my ISP.

Xantor Bludberry
Amarr
Posted - 2008.10.08 15:52:00 - [8]
 

Edited by: Xantor Bludberry on 08/10/2008 15:53:14
Launch ExeFile.exe from "bin" directory. Have results:

EVE Client version 5.11 build 64451 starting 08.10.2008 23:45:23
Multi-Language System: Client using language [RU]
EVE Client version 5.11 build 64451 started 08.10.2008 23:45:25
Starting services
Service machoNet : 0.001 sec
Service dataconfig : 0.076 sec
Service objectCaching : 0.000 sec
Service counter : 0.000 sec
Service clientStatsSvc : 0.001 sec
Service invCache : 0.000 sec
Service godma : 0.000 sec
Service photo : 0.000 sec
Service LSC : 0.000 sec
Service patch : 0.045 sec
Service inv : 0.000 sec
Service michelle : 0.000 sec
Service billboard : 0.000 sec
Service pwn : 0.000 sec
Service focus : 0.000 sec
Service debug : 0.000 sec
Service jumpQueue : 0.000 sec
Starting services - Done
Service moonScan : 0.000 sec
Service fonts : 0.005 sec
Service ui : 0.000 sec
Service gameui : 0.110 sec
Service device : 0.009 sec
Service form : 0.000 sec
Service window : 0.000 sec
Service journal : 0.000 sec
Service insurance : 0.000 sec
Service station : 0.000 sec
Service cmd : 0.005 sec
Service draw : 0.000 sec
Service loading : 0.000 sec
Service connection : 0.000 sec
Service damage : 0.000 sec
Service envAudio : 0.000 sec
Service logger : 0.001 sec
Service audio : 0.000 sec
Service vivox : 0.000 sec
Service monitor : 0.000 sec
Service ownerprimer : 0.000 sec
Service petition : 0.001 sec
Service log : 0.000 sec
Service z : 0.000 sec
Service war : 0.000 sec
Service consider : 0.000 sec
Service webtools : 0.000 sec
Service ime : 0.008 sec
Service sites : 0.001 sec
Service neocom : 0.761 sec
(there, when apear window with "The socket was closed" message, I click "OK" and get the next:)
An exception has occurred. It has been logged in the log server as exception #1
(and when i was tryin again)
An exception has occurred. It has been logged in the log server as exception #2

Xantor Bludberry
Amarr
Posted - 2008.10.08 15:55:00 - [9]
 

Maybe its trouble with my IP adress?

Arrs Grazznic
Poena Executive Solutions
Posted - 2008.10.09 09:01:00 - [10]
 

I have had the same problem as the OP (full details in my post here.

I managed to solve my problem by running the latest version of WinSock XP Fix (download from here). I set a restore point, backed up the registry and ran the application. The utility 'fixes' your TCP/IP stack and following its execution all my IP applications still worked and EVE could connect through.

Please note that other users have tried using this tool and have not been successful, however it did work for me.

The question I have is what did the patch do to screw up my (and other peoples) IP stack? Is its some application we have installed (for example, do you have NDAS installed)?

Anyway, hope this helps.

Cheers,
Arrs

GM Retrofire


Game Masters
Posted - 2008.12.03 18:44:00 - [11]
 

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.

Mister Zero
Minmatar
Posted - 2008.12.04 01:23:00 - [12]
 

Filed a bug report along with my 'history.txt' attached, constant drops for the last few weeks. Makes EVE effectively unplayable. Ran a ping/trace and the only oddity I can see is at my router level. Somehow, I suspect most of us with these 'socket errors' are on routers, either wireless or otherwise. I'm hardwired via cat5.

Pinging 87.237.38.200 with 32 bytes of data:

Reply from 87.237.38.200: bytes=32 time=181ms TTL=112
Reply from 87.237.38.200: bytes=32 time=180ms TTL=111
Reply from 87.237.38.200: bytes=32 time=179ms TTL=112
Reply from 87.237.38.200: bytes=32 time=181ms TTL=111

Ping statistics for 87.237.38.200:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 179ms, Maximum = 181ms, Average = 180ms

Tracing route to 87.237.38.200 over a maximum of 30 hops

01 - * * * Request timed out.
02 - 23 ms 23 ms 23 ms L100.DSL-49.LSANCA.verizon-gni.net [96.229.38.1]
03 - 24 ms 23 ms 24 ms P11-0.LCR-04.LSANCA.verizon-gni.net [130.81.44.24]
04 - 25 ms 25 ms 25 ms so-6-2-0-0.BB-RTR2.LAX01.verizon-gni.net [130.81.28.229]
05 - 24 ms 24 ms 24 ms so-7-1-0-0.BB-RTR2.LAX01.verizon-gni.net [130.81.17.147]
06 - 24 ms 24 ms 24 ms ge2-6.br01.lax04.pccwbtn.net [63.218.51.29]
07 - 179 ms 179 ms 179 ms telecity.ge9-9.br02.ldn01.pccwbtn.net [63.218.13.222]
08 - 180 ms 180 ms 179 ms 532-dist65-01.lon3.telecity.net [217.20.44.226]
09 - 181 ms 180 ms 180 ms ipt-ccp-games-1-as35834.lon3.telecity.net [217.20.44.138]
10 - 182 ms 182 ms 181 ms 87.237.38.200

Trace complete.

Astro Glyde
Wormhole Rescue Service
Posted - 2008.12.04 17:51:00 - [13]
 

Any fix for this yet? Can't/won't play until there is. :(

Antonius Hari
BoB Enterprises
Veni Vidi Vici Alliance
Posted - 2008.12.11 21:17:00 - [14]
 

MY corp have been suffering this a lot.

We lost a few ships in a Fleet after 2/3 of us all got dropped by "Socket error", we petitioned it, but CCP woudl not acknowledge the loss


THe system was a back water pocket in NPC 0.0.
We had about 35 in local, we were battling on and off for abotu 15 minutes, warp wasnt workign and numerous other functions wouldnt not work, the enemy then undocked a carrier and as he launched fighters, it must have bugged the system, because most of our fleet and soem of theirs got this "socket error".

Unfortunetly for us, we lost to many of our fleet to defend compared to them, we had 12 ppl, they had the balance, it eneded up about 3 V about 10 of them.

We dont mind the loss, cause we were enjoying the battle, but i think if 2/3 your fleet suffers a "socket error", thats hardly our ISP's as CCP have explained away a failed petition.

We hate going to battle since the last pacth, as even our logistic ops suffers this, so its not about lossing ships, its jsut about continuity of play, and logging in is frustrating, when you have to do it a few times in a short space of time.

Tanaki Arus
Posted - 2008.12.12 00:37:00 - [15]
 

That happened to my client yesterday... Near as I can gather, that stuff only happens if BoB is losing titans.

Franz7657
Caldari
Franzminator Corp
Posted - 2008.12.12 16:25:00 - [16]
 

same problem for me too now, and all my corp members complain about this problem for the 2 last days now, i try both manip, and i keep you informed about the result

comrade captain
Posted - 2008.12.12 22:15:00 - [17]
 

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.


So far so good having done this, if it continues to work perfectly your on my christmas card list. Good man, many thanks

EvilTwin I
Twin Corp
Posted - 2008.12.13 14:44:00 - [18]
 

The socket was closed

same bug here

Atraxerxes
Caldari
22nd Black Rise Defensive Unit
OWN Alliance
Posted - 2008.12.13 14:46:00 - [19]
 

Whats going? I'm getting socket closed or if I'm really lucky I see I'm #150 in the que and there are 15,000 players logged in.


Rob Silverton
Posted - 2008.12.13 15:00:00 - [20]
 

All I got up a min ago was.

The EVE cluster has reached its maximum user limit. Please try logging in again later. You are #2102 in line for logon.

Before that it was just socket closed.

Jet River
Posted - 2008.12.13 15:17:00 - [21]
 

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.


Thanks, this worked for me. Laughing

EvilTwin I
Twin Corp
Posted - 2008.12.13 15:25:00 - [22]
 

I downloaded newest client and same problem ..then started eve-safemode .. got in changed all gfx etc setting .. closed and restarted the normal .. and voila got in :)

CCP Cascade

Posted - 2008.12.13 16:52:00 - [23]
 

Please note that "socket closed" errors today (the 13th) were related to problems with our proxies. This is not the same "Socket closed" problems which have been reported earlier in this thread.

Franz7657
Caldari
Franzminator Corp
Posted - 2008.12.13 23:37:00 - [24]
 

problem is solved on my side with both manip, thx

Glyken Touchon
Gallente
Independent Alchemists
Posted - 2008.12.14 03:25:00 - [25]
 

Edited by: Glyken Touchon on 14/12/2008 11:47:46
between about 01:30 and 02:30 (14th), I've been disconnected about a dozen times.

each time, I get the ingame message
"you have been logged out of audio chat"
then I get the socket closed error.

when the client closes, I find that my wireless connection has also fallen over, and usually requires a reboot in order to reconnect.

my other half's PC (not an eve player) continues with internet connection throughout on the same wireless router.

any ideas for workarounds/fixes?

Elkazar Shadowstep
Posted - 2008.12.14 05:25:00 - [26]
 

Well this is mine.

C:\Users\Mike>Ping 87.237.38.200

Pinging 87.237.38.200 with 32 bytes of data:
Reply from 87.237.38.200: bytes=32 time=226ms T
Reply from 87.237.38.200: bytes=32 time=225ms T
Reply from 87.237.38.200: bytes=32 time=220ms T
Reply from 87.237.38.200: bytes=32 time=226ms T

Ping statistics for 87.237.38.200:
Packets: Sent = 4, Received = 4, Lost = 0 (
Approximate round trip times in milli-seconds:
Minimum = 220ms, Maximum = 226ms, Average =

C:\Users\Mike>tracert 87.237.38.200

Tracing route to 87.237.38.200 over a maximum o

1 8 ms 7 ms 11 ms 73.98.4.1
2 8 ms 7 ms 6 ms 68.87.205.113
3 25 ms 11 ms 11 ms te-9-4-ar01.bur
.96.10]
4 15 ms 17 ms 17 ms 68.86.90.221
5 28 ms 28 ms 28 ms pos-0-7-0-0-cr0
[68.86.85.197]
6 31 ms 29 ms 30 ms pos-0-7-0-0-cr0
8.86.85.78]
7 33 ms 42 ms 33 ms Tenge13-3.br02.
8 176 ms 177 ms 178 ms telecity.ge9-9.
.222]
9 176 ms 178 ms 177 ms 532-dist65-01.l
10 225 ms 224 ms 224 ms ipt-ccp-games-1
0.44.138]
11 219 ms 218 ms 219 ms 87.237.38.200


AND what does my ping to CCP have to do with the game NOW refusing to even get to log in screen since the socket closed?

I've uninstalled TWICE now, the last time after running a virus scanner(even though it's been running the whole time).


"netsh winsock reset catalog" get's me "The requested operation requires elevation." It's now been over 12hrs since I got that socket closed message, and NOTHING from my petition...and these ideas are worthless.

And since I'm posting this on the main web site for Eve, telling me to check my internet connection would be stupid.Rolling Eyes

Elkazar Shadowstep
Posted - 2008.12.14 22:35:00 - [27]
 


Notice CCP isn't replying anymore. Too many people are getting smart and calling them on their screw up, and they shut up, and close ranks. There is plenty of threads in this forum to prove that more then just a few people are having, if not this problem, but a similar problem. And it's not just on windows OS's now...someone on a mac posted the same type of problem.
Petitioning it just gets you a reply that will make you think that the problem is on your side of the net, or your computer. It's not, CCP broke something with the latest patch, and will not own up to it.

And something is wrong with the petition server, since I'm attempting to reply to my petition, and I get the 'Oops' screen. The stupid thing, they want me to run the game with attributes, when neither the 'CCP ExeFile' or the 'CCP ExeFile-Safe Mode' works? With crashing on splash screen, how does one run the game?

CCP Cascade

Posted - 2008.12.15 01:28:00 - [28]
 



 

This thread is older than 90 days and has been locked due to inactivity.


 


The new forums are live

Please adjust your bookmarks to https://forums.eveonline.com

These forums are archived and read-only