| Author |
Thread Statistics | Show CCP posts - 9 post(s) |
|
CCP Explorer
   |
Posted - 2008.06.27 20:56:00 -
[1]
Sounds like a firewall blocking access.
Erlendur S. Thorsteinsson
Software Director
EVE Online, CCP Games |
|
|
CCP Mindstar
|
Posted - 2008.06.30 11:10:00 -
[2]
Could those of you on Hornet please run a tracert to 87.237.38.200 and post the result here.
To do this, go to start -> run, type in "cmd" and in the black window that appears, type "tracert 87.237.38.200".
-- |
|
|
CCP Mindstar
|
Posted - 2008.06.30 13:40:00 -
[3]
Thanks for the traceroutes. We have identified one potential fix to this, so please try and connect again, and post with the results.
-- |
|
|
CCP Mindstar
|
Posted - 2008.06.30 14:01:00 -
[4]
Could you try putting the following command in the cmd box:
"telnet 87.237.38.200 26000"
You should see some garbled text ending at "LIVE@ccp".
This will tell us if there is an issue with the port that EVE uses, from your computer.
-- |
|
|
CCP Mindstar
|
Posted - 2008.06.30 14:21:00 -
[5]
 Originally by: Bladen Kerst
I got this
C:\>telnet 87.237.38.200 26000
'telnet' is not recognized as an internal or external command,
operable program or batch file.
Ahh, I think telnet is not installed by default under Windows Vista. This page shows how to install it.
-- |
|
|
CCP Mindstar
|
Posted - 2008.06.30 14:46:00 -
[6]
Originally by: Goatface Man
Trying the telnet, I get this:
*~¦♠♦¦+☻└X
ffffff¦@♦"¦LIVE@ccp
Could you please submit a bug report with a logserver file of trying to connect attached - see here for details on how to run it.
Cheers
Mindstar
-- |
|
|
CCP Mindstar
|
Posted - 2008.06.30 15:23:00 -
[7]
Thanks for the bug reports. We have the info we need now, but the reports themselves will just be closed, so don't worry too much if that happens 
-- |
|
|
CCP Mindstar
|
Posted - 2008.06.30 15:28:00 -
[8]
Working through a few more options you could try - there is an alternate port to 26000 you can use to connect.
See here for how to set it up.
-- |
|
|
CCP Mindstar
|
Posted - 2008.07.03 14:39:00 -
[9]
Originally by: Goatface Man
Apparently it was Hornet, they just didn't know how they'd fixed it.
Chris came to see me today and we did a few connection tests while they disabled and enabled things at their end to find out what would make it stop working again. It should all be fine now.
That is good to know. Glad they could get it fixed for you 
-- |
|
| |
|