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.
 

The Server you are connecting to could not be reached.

First post
Author
Previous Topic Next Topic
Grenn Putubi
Sebiestor Tribe
Minmatar Republic
#1 - 2014-12-14 15:02:05 UTC  |  Edited by: Grenn Putubi
So I'm unable to get EVE started today. The launcher can't reach http://cdn1.eveonline.com/852129/RepairData_852129.dat

When trying to launch from the exefile.exe it tells me I have the wrong version.

Judging from what I've found on the forums about this error happening in the past I'm guessing there's some sort of DNS issue stopping me from connecting properly and since I don't see the forums flooded with posts or a thread a mile long I'm also guessing that it's probably localized to the Pittsburgh, PA area.

Anyone else getting this right now?
Nailo Nimbletong
Moar Oar Corp
#2 - 2014-12-14 15:06:00 UTC  |  Edited by: Nailo Nimbletong
Same issue here,

I did get to fix it by doing what this guy said:

https://forums.eveonline.com/default.aspx?g=posts&m=4957587#post4957587

- Cheers

Edit: Amsterdam here.
Elderian en Gravonere
Survivors of Thaloss Hand
#3 - 2014-12-14 15:07:38 UTC
same here.
I'm in Germany. Another PC using the same internet connection can start EVE without problems.

Also the repair tool does not work with the same URL in the lod files.
Aesir North
State War Academy
Caldari State
#4 - 2014-12-14 15:13:26 UTC
Same here from Germany, Provider Kabel Deutschland.
Ke11y Divine
Center for Advanced Studies
Gallente Federation
#5 - 2014-12-14 15:17:02 UTC
Having this problem today. I'm in the US. Adding google's DNS servers behind my regular DNS servers in the adapters IP 4 config resolved it.
Grenn Putubi
Sebiestor Tribe
Minmatar Republic
#6 - 2014-12-14 15:20:12 UTC
Nailo Nimbletong wrote:
Same issue here,

I did get to fix it by doing what this guy said:

https://forums.eveonline.com/default.aspx?g=posts&m=4957587#post4957587

- Cheers

Edit: Amsterdam here.


I was also able to fix it by switching to Google's public DNS. Thanks for that :)
Elderian en Gravonere
Survivors of Thaloss Hand
#7 - 2014-12-14 15:45:54 UTC
me too. Now i can play. Thanks for the tip!
CCP Habakuk
C C P
C C P Alliance
#8 - 2014-12-14 16:10:25 UTC
Is anybody still having these problems (without switching to Google's public DNS)? I had the same problem on my home connection, but it seems like it fixed itself.

CCP Habakuk | EVE Quality Assurance | Team Five 0 | (Team Gridlock)

Bug reporting | Mass Testing
miss fits
New Eden Economic Block
#9 - 2014-12-17 13:56:44 UTC
The launcher works for me, I can login, but cannot connect to server. In Brisbane Australia, but looks like the problem may be in the UK from the tracert - see below.

I have cycled modem, same result. Been like this since Rhea deployed. I have no other network/connection issues and been playing ok for last few years...


---
C:\Users\P>tracert 87.237.38.200

Tracing route to srv200-g.ccp.cc [87.237.38.200]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 7 ms 7 ms 6 ms 10.205.64.1
3 9 ms 7 ms 7 ms 58.160.16.204
4 8 ms 10 ms 8 ms 58.160.23.226
5 12 ms 6 ms 9 ms bundle-ether4.woo-edge902.brisbane.telstra.net [203.50.44.42]
6 11 ms 11 ms 11 ms bundle-ether6.woo-core1.brisbane.telstra.net [203.50.11.138]
7 20 ms 22 ms 20 ms bundle-ether11.chw-core10.sydney.telstra.net [203.50.11.70]
8 23 ms 23 ms 23 ms Bundle-ether17.oxf-gw2.sydney.telstra.net [203.50.13.70]
9 23 ms 23 ms 23 ms bundle-ether1.sydo-core01.sydney.reach.com [203.50.13.38]
10 23 ms 19 ms 19 ms i-0-2-0-6.sydo-core02.bi.telstraglobal.net [202.84.223.46]
11 165 ms 163 ms 163 ms i-0-2-0-7.1wlt-core01.bx.telstraglobal.net [202.84.143.149]
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.

Trace complete.