These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

Issues, Workarounds & Localization

 
  • Topic is locked indefinitely.
 

Launcher Offline, Cannot Connect to Eve Servers.

First post
Author
Previous Topic Next Topic
Calerin Lye
Phoenicia Acquisitions
#1 - 2014-12-13 13:47:57 UTC
Since Thursday's patch (the 2nd Rhea patch) I seem to have a problem connecting to the Eve Servers, and as such I am unable to play the game.

This has manifested itself in several ways:

1) The Launcher is nearly always in Offline Mode. Sometimes just a white box opens and then freezes. Other times it appears to work, but then flashes up an error message about failing to retrieve something.

2) If I try to force Eve by using Launcher in .bin folder than takes you to the pre-Launcher Log-In screen, it tells me it cannot establish a connection to the Eve server.

3) The 2 times I did manage to connect on Thursday, just after DT, I had Sockets close after no longer than 2 minutes in game.

I have tried manually downloading Launcher and Repair Tool from links posted on these Forums. I have uninstalled, redownloaded and reinstalled game client twice. I have tried to use as many Launchers as I could find in the Eve folders. I have changed Port from the normal one to the back-up one, again as discovered in these Forums. I have even contacted my ISP to check whether there are any problems with my internet connection.

Obviously all of these have failed. Is anyone else having similar problems? Or are there any fixes I have not tried yet?
Telle Kosava
TelleKosava0ffshore LLC
#2 - 2014-12-16 10:13:57 UTC
I have had the same issue since Rhea on my PC but not on my laptop... =/

I submitted a ticket December 12th:

2014-12-12 05:12:
--I received a speedy reply from GM Fox requesting me to bypass the launcher (using CCP/EVE/bin/exefile). My login screen read "Unable to connect to 87.237.38.200 on port 26000 ... Version #: 8.49.848647".

2014-12-12 05:35:
-- I replied

2014-12-12 06:00
Quote:
Posted: 2014-12-12 06:00
GM Fox
Greetings, I am GM Fox.

Ticket will now be passed to the attention of my colleagues in the Technical department who will be happy to investigate and then provide the requested information. Please be aware that there may be a delay in responding to this ticket and as such your patience is appreciated.

Best regards,
GM Fox
CCP Customer Support | EVE Online | DUST 514



Aaaaaand I haven't heard anything since.
Mnemet
School of Applied Knowledge
Caldari State
#3 - 2014-12-16 14:24:42 UTC  |  Edited by: Mnemet
I've got almost the same problem. Today, about 03:00 am EVE time was mass disconnect. I run incursion fleet this time. I've lost connect in 20-30 min after mass DC and i can't connect to server since that time. I live in China, but tarcert log shows on issue in GB.


P.S. Fixed
Telle Kosava
TelleKosava0ffshore LLC
#4 - 2014-12-16 15:28:56 UTC
And the repair tool fails every time... I forgot to mention that.
TheShadowSys
The Created
#5 - 2014-12-17 06:54:16 UTC
I have the same issue. I can open the launcher and sign in there, but when the game launches I get "Connection Failed: The connection to the server was closed.". If I try to launch the client bypassing the launcher I start the login process and then I get the same error.
miss fits
New Eden Economic Block
#6 - 2014-12-17 14:10:52 UTC  |  Edited by: miss fits
Same issue as above - launcher is fine, updates are fine, but cannot connect to the game server.

Client fails with "cannot connect to 87.237.38.200 on port 26000"

ping and tracert report destination net unreachable. The problem seems to be in the UK, at least from my tracert result, here is the last bit:

Tracing route to srv200-g.ccp.cc [87.237.38.200]
over a maximum of 30 hops:
...
12 164 ms 162 ms 163 ms i-0-0-0-0.tlot02.bi.telstraglobal.net [202.40.149.142]
13 * * * Request timed out.
14 * * * Request timed out.
15 163 ms 162 ms 183 ms ae0.cr2.lax112.us.zip.zayo.com [64.125.32.78]
16 194 ms 195 ms 195 ms ae3.cr2.iah1.us.zip.zayo.com [64.125.21.85]
17 219 ms 219 ms 220 ms ae14.cr2.dca2.us.zip.zayo.com [64.125.21.53]
18 333 ms 335 ms 333 ms xe-5-1-0.mpr3.lhr3.uk.zip.zayo.com [64.125.31.185]
19 327 ms 327 ms 327 ms ae6.mpr2.lhr3.uk.zip.zayo.com [64.125.21.22]
20 * 213-152.240-250.PXu259.above.net [213.152.240.250] reports: Destination net unreachable.

Should I take this up with my ISP or (since it seems to be in the UK) is it more of a CCP thing?

(connecting from Brisbane, Australia)
GM Arcade
Game Masters
C C P Alliance
#7 - 2014-12-17 16:37:17 UTC
The server may simply not be setup to respond to trace pings, which would account for it not being reachable.

When the launcher shows as offline it generally means that it is being blocked from querying a web site that it relies upon to check the current launcher and client version.

Most often we find that security applications (firewall and anti-malware) are responsible for the blocks. Adding exceptions for the launcher (launcher.exe) to these security applications will help in most cases.

We have also found that the use of a proxy will sometimes stop the launcher from working. You can see below the steps to see if Windows is setup to use a proxy:


  • Open the "Internet Options" from the Windows Control Panel
  • Go to the "Connections" tab and click on the "LAN Settings" button
  • Make sure that only "Automatically detect settings" is checked and all other entry fields are empty.


If the launcher continues to show offline then please submit a ticket in the Technical -> Installation and Patching category. Please let us know what security applications you are using as it could be pertinent.

Lead GM Arcade | Customer Support Manager
miss fits
New Eden Economic Block
#8 - 2014-12-19 09:07:06 UTC
Fixed now.

Wasn't due to antivirus/firewall, or faulty settings

Seems it was probably a flaky modem/router, or something strange with the ISP that was fixed when I was allocated a new IP address (or whatever they do with a new cable modem).

You were right about the tracert being nonsense, client now works fine but trace is the same. Ping also returns "destination net unreachable". I didn't try pingplotter.