After reading hundreds of posts about this error, there is no fix, this game sucks, no fix not even from the dev team, this doesn't happen in wow, rift or d3, only here, I guess this gives you the long sight of the future of this game = Going Nowhere.
Star Trek Online = FAIL
BTW If someone says reinstall Windows 7, this is not a fix this is there way of telling you to stop whinging.
the problem is with both the game and the internet.
there is a rouge ip block on the server thet is causing this prob.
it blocks the ip address and area of the game. wait for the next patch, your area will hopefully be allowed access.
Hope it helps.
The first time it lasted about a day and then just took care of itself. I had tried several things like removing power from the router, turning off protection software and firewall, etc. I had finally given up and gone to bed. The next day it was working again, so I just assumed that it had been a problem on the other end of the connection.
Yesterday it happened again. I tried many of the same things, gave up and went to bed, but this time I still couldn't connect when I woke up. In the USA a lot of people with cable modem rent their routers. I rent mine from my provider. The set up in my home has two routers, actually. One is wireless and one is direct cable. I usually have my gaming PC hooked to the direct router. Out of desperation I switched it to the wireless router.
That seems to have worked. I can now log in to the game. This whole problem might be a router issue. I use Charter Cable, the router that stopped working for this game (but would still work for the rest of the internet) was a Touchstone Telephony Modem, and the wireless router that now lets me connect to the launcher is made by Ubee.
I hope that helps somebody else troubleshoot their issue.
3 25 ms 23 ms 29 ms ************ [*.*.*.*]
4 28 ms 31 ms 35 ms ************ [*.*.*.*]
5 24 ms 25 ms 23 ms ae-1.r00.londen01.uk.bb.gin.ntt.net [184.108.40.206]
6 25 ms 26 ms 24 ms ae-6.r02.londen03.uk.bb.gin.ntt.net [220.127.116.11]
7 24 ms 25 ms 24 ms te2-4.mag01.lon02.atlas.cogentco.com [18.104.22.168]
8 149 ms 205 ms 205 ms te7-2.ccr01.lon02.atlas.cogentco.com [22.214.171.124]
9 27 ms 27 ms 24 ms te0-0-0-2.ccr21.lon01.atlas.cogentco.com [126.96.36.199]
10 29 ms 31 ms 27 ms te0-1-0-4.mpd21.lon13.atlas.cogentco.com [188.8.131.52]
11 103 ms 102 ms 103 ms te0-3-0-4.ccr21.bos01.atlas.cogentco.com [184.108.40.206]
12 104 ms 108 ms 99 ms te4-4.ccr01.bos06.atlas.cogentco.com [220.127.116.11]
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * ^C
Same, clearly a routing issue between Cogentco and whomever hosts the STO network.