So, unfortunately, Microsoft didn't find it useful to have separate error pages for server response timeout and dns. They are the same location in the address bar.
The even more unfortunate truth is that in all likelihood PWE has limited power in this issue. Depending on a large number of factors, all of which rest with the hosting company (Internap), there is truly no telling how long it could take to resolve the route issue.
Triage at datacenters is a difficult thing. Some of these routers are over $40,000 to replace, and that warrants some attempts at non-destructive resolution. How long they spend trying to resolve the issue is just never going to be fast enough to those having to deal with the issue.
Due to the difficulty of having to deal with a third party, even updating us isn't very easy to do. We all want to know how long and whats going on... but the unfortunate truth is they may only know what we know. Hosting companies aren't known for their efficiency, nor are they associated with transparent discussion of whats going on when **** hits the fan.
A fix that just worked for me is on http://sto-forum.perfectworld.com/showthread.php?t=225155. it was the sporadic ip address fix. You run CMD as admin type ipconfig /release and then ipconfig /renew. So for some of us the IP address was the issue.
After numerous attempts I finally got the launcher connect and present was appears to be a valid Login Splash. Oddly, when the splash dialog opened so did Internet Explorer with the following in the address bar:
A fix that just worked for me is on http://sto-forum.perfectworld.com/showthread.php?t=225155. it was the sporadic ip address fix. You run CMD as admin type ipconfig /release and then ipconfig /renew. So for some of us the IP address was the issue.
Though right now the issue looks to be resolved regardless.. if in the future we encounter this, be aware that this would have only been another temporary fix.
Doing this action clears the routing table cache on your system, and causes it to reobtain it, which due to the down node would choose a working route. When the route autocorrects to the route it wants to be, you'd have the problem over again.
How long that takes to happen is variable depending on any one of the 20+ hops that your connection traverses.
Been having the same problem but while it was patching changed the proxy from eu to us and started getting some download speed at least, only 4058mb update to go. Hope this anyone.
The team is continuing to investigate your reports, but this does not seem to affect all players -- again, the initial reports of this started before the patch this morning so it is not related to today's maintenance. To help in the investigation, please run a tracert (instructions for this process here) pointing to launcher.startrekonline.com and copy/ paste your results in this thread if you're comfortable doing so and making sure you star out your local IP address/ other sensitive data.
Cheers,
Brandon =/\=
Mines working again. I bet my ISP's local DNS started routing info through a different pipeline and now I have access.
Hi Brandon. Seems to be fixed but i do notice that on the After results that i do get a nasty hop at number 7 which is (7 238 ms 394 ms 207 ms internap-gw.ip4.tinet.net [77.67.77.54] ) I ran the tracert twice and similar results on that hop 7. Still tho much improved and working compared to the Before results which was when sto was unreachable.
Before:
Tracing route to launcher.startrekonline.com [208.95.185.44]
over a maximum of 30 hops:
1 10 ms 12 ms 10 ms ****starred out***
2 11 ms 11 ms 11 ms ****starred out***
3 14 ms 14 ms 14 ms leed-bb-1c-ae3-0.network.virginmedia.net [62.253
.174.45]
4 * 15 ms 17 ms nrth-bb-1c-ae9-0.network.virginmedia.net [62.253
.174.122]
5 15 ms 16 ms 17 ms nrth-bb-1a-ae3-0.network.virginmedia.net [62.253
.174.105]
6 17 ms 25 ms 16 ms nrth-tmr-1-ae1-0.network.virginmedia.net [213.10
5.159.30]
7 33 ms 31 ms 34 ms fran-ic-1-as0-0.network.virginmedia.net [62.253.
185.81]
8 34 ms 35 ms 35 ms te0-7-0-7.mpd22.fra03.atlas.cogentco.com [130.11
7.14.133]
9 36 ms 35 ms 35 ms te0-0-0-2.mpd22.ams03.atlas.cogentco.com [130.11
7.0.133]
10 44 ms 41 ms 44 ms te0-1-0-2.ccr22.lpl01.atlas.cogentco.com [154.54
.37.110]
11 110 ms 118 ms 109 ms te0-1-0-3.ccr22.bos01.atlas.cogentco.com [154.54
.42.105]
12 108 ms 107 ms 109 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.25
4]
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 * 108 ms * playstartrekonline.de [208.95.185.44]
21 * * * Request timed out.
22 * * * Request timed out.
23 * 110 ms * playstartrekonline.de [208.95.185.44]
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * 108 ms * playstartrekonline.de [208.95.185.44]
Trace complete.
After:
Tracing route to launcher.startrekonline.com [208.95.185.44]
over a maximum of 30 hops:
1 24 ms 106 ms 8 ms **starred out***
2 10 ms 8 ms 11 ms ***starred out***
3 12 ms 10 ms 12 ms midd-core-2b-ae1-0.network.virginmedia.net [62.2
54.64.194]
4 21 ms 20 ms 19 ms brhm-bb-1b-ae12-0.network.virginmedia.net [62.25
3.174.49]
5 21 ms 22 ms 20 ms ae1.lon25.ip4.tinet.net [77.67.65.161]
6 100 ms 98 ms 104 ms xe-3-0-0.bos11.ip4.tinet.net [141.136.109.138]
7 238 ms 394 ms 207 ms internap-gw.ip4.tinet.net [77.67.77.54]
8 101 ms 99 ms 103 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.4
1]
9 102 ms 105 ms 107 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
10 101 ms 100 ms 98 ms fr.startrekonline.com [208.95.185.44]
Was just letting brandon know the tracert results from when all this started to now when launcher works. BUT! I have tried twice to login and i get a "connection to the login server timed out", both times.
So the launcher seems to work fine now but i cannot use the login server for some reason.
Edit - 3rd time to try to login did the trick. Im now in.
At this time, we believe the issue has been resolved. We thank you very much for your patience today, and for all the tracerts posted in this thread. As you can see from the tracerts posted by your fellow players, the issues that you were running into were occurring during the "hops" before you actually got to the launcher -- we are now talking and working with our external routing provider to investigate why this was occurring.
Again, thank you for your patience and support, and we'll see you in-game!
At this time, we believe the issue has been resolved. We thank you very much for your patience today, and for all the tracerts posted in this thread. As you can see from the tracerts posted by your fellow players, the issues that you were running into were occurring during the "hops" before you actually got to the launcher -- we are now talking and working with our external routing provider to investigate why this was occurring.
Again, thank you for your patience and support, and we'll see you in-game!
Cheers,
Brandon =/\=
If this is a problem with an external services vendor, I will be in California two weeks hence... I can organize the angry mob and lead the march. Also, I have exclusive distribution rights to torches that meet California's strict air-quality rules along with pitchforks that meet or exceed California's product safety requirements.
Drop me a PM if I'm needed, otherwise I won't be in the neighborhood, my business is near Humboldt.
I don't suppose anyone else has noticed the problem of their Controller Keybinds having been totally screwed up ever since the resumption of being able to log in and not being able to do anything about it?
As of 22:30 pm est I still cannot log in to star trek online. I work nights so I will be checking in the morning. My Internet is not the issue because I played up until 5 minutes before shard maintenance on Monday morning.
If you can use something like a VPN or alternative network to start the launcher, click the button in the upper right that says Enable Proxy and pick US or EU from the drop-down as appropriate. Then try it with your regular network. That seems to have fixed it for me.
i had this problem and now (3:52 am EST) it seems to have resolved its self.
what i did while i had this problem for *FREE**FREE**FREE* was: 1) set up an account and downloaded Private Tunnel (PT).
2) ran PT with Connect to: San Jose CA
3) opened the game launcher. (couldnt get this far with out PT before)
4) entered log in info and the game loaded and popped up the character select screen.
5) disconnected and exited PT (brings the game back to the IN GAME log in screen.
6) re-entered log in and was off to kill more borg.
i had to do this a few times as i had fully closed out of STO to take dogs for a walk and run to the store. also to note PT only allows for 100 MB *FREE* of data to go through their lines you can also pay for more. so the trick is to get it to go past the launcher and disconnect from PT.
the first time i did it i forgot to disconnect from PT and ran out the 100 MB quickly. so i used a different email and re-signed up for it and was fine.
Still not working here - managed the VPN thing to update it, but I've lost the details, and the launcher still isn't working. Managed a quick bit of play last night, but that's only thanks to a forum member providing the VPN details
As you can see from the tracerts posted by your fellow players, the issues that you were running into were occurring during the "hops" before you actually got to the launcher -- we are now talking and working with our external routing provider to investigate why this was occurring.
Guys, if you are still having issues, please be patient. The problem as described by Brandon above is not a problem on YOUR end or THEIR [Cryptic's] end but in between. In laymen terms, you don't connect directly through to Cryptic but you "hop" along from one network segment to the next. Much like getting on a interstate to go from your house in New York to Cyrptic outside of San Fran, there is NOT a direct interstate route but you go from one interstate road to another as you need.
This is something that is external to Cryptic and thus not something that can be fixed "BY" them either. Again, thank you for understanding and your patience as the STO team (IMHO) wants everyone to be online for the 3 year anniversary.
Even though I can log into the game and have been able to throughout this random issue, I have included my trace route below in case it helps.
[Location - Columbus Ohio. Using Time Warner Cable Wideband (50Mbps) ]
Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms CISCOE3000 [10.10.1.254]
2 9 ms 8 ms 7 ms 10.88.128.1
3 17 ms 15 ms 15 ms ae0-1170.cr02.clmkohpe.midohio.rr.com [184.59.24
3.213]
4 14 ms 7 ms 15 ms network-065-029-001-034.midwest.rr.com [65.29.1.
34]
5 24 ms 23 ms 23 ms ae-9-0.cr0.chi30.tbone.rr.com [107.14.19.16]
6 42 ms 47 ms 47 ms ae15.120.pr0.dfw10.tbone.rr.com [66.109.9.41]
7 40 ms 40 ms 38 ms 107.14.17.232
8 60 ms 41 ms 96 ms 107.14.16.30
9 80 ms 89 ms 45 ms pr2-ge-7-0-0.daq.savvis.net [204.70.207.182]
10 41 ms 41 ms 41 ms cr1-tengig0-7-5-0.dallas.savvis.net [204.70.200.
170]
11 63 ms 61 ms 60 ms cr2-ten-0-3-2-0.nyr.savvis.net [204.70.224.210]
12 61 ms 61 ms 75 ms er1-te-2-1.newyorknyd.savvis.net [204.70.196.70]
13 68 ms 70 ms 67 ms msr1-te-0-3-0-0.bos.savvis.net [206.28.97.205]
14 66 ms 67 ms 69 ms 206.28.97.137
15 75 ms 72 ms 74 ms internap.boston.savvis.net [208.172.51.230]
16 72 ms 76 ms 71 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.4
1]
17 76 ms 71 ms 71 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
18 72 ms 70 ms 71 ms 208.95.185.41
Trace complete.
C:\Users\matt>
PS Commentary - Going back to my example of interstates, looks like I went from Ohio to Texas to New York to Boston MA. Man, that was a heck of a Commute in distance but the shortest in time.
Matt Miracle
Fleet Commander in Chief [Rank 7] for Covenant of Honor; a FED T5 Starbase
House Leader [Rank 7] for Honorable House of Mor'gue; a KDF T3 Starbase Find us at CovenantofHonor.com. My Twitter handle; @jmattmiracle
hi I' m still having problems loading the game, I was still having issues with the launcher and now that brings the cryptic logo up where the loading screen but doesn't load.any help or info would be nice. thank you
So I have to take this opportunity to apologize on behalf of all other times for the ignorant, but especially for all the impatient! And to you: It's really worrying that you obviously are not in a position, you to deal with something else. And anyone who has installed his game or Louncher new, and therefore now has even more problems, I can only write: "Even guilt."
Many thanks to the team, to have solved these problems as quickly.
PC-Info
MB: MSI MPG X570 GP 2.0
CPU: AMD Ryzen 7 3700X
Mem: Samsung DDR4 -2132 8GB (x2)
Graph: NVIDIA GeForce GTX 1060 6GB
System: Micrsft. Windows 10 Pro v.21H2
Comments
The even more unfortunate truth is that in all likelihood PWE has limited power in this issue. Depending on a large number of factors, all of which rest with the hosting company (Internap), there is truly no telling how long it could take to resolve the route issue.
Triage at datacenters is a difficult thing. Some of these routers are over $40,000 to replace, and that warrants some attempts at non-destructive resolution. How long they spend trying to resolve the issue is just never going to be fast enough to those having to deal with the issue.
Due to the difficulty of having to deal with a third party, even updating us isn't very easy to do. We all want to know how long and whats going on... but the unfortunate truth is they may only know what we know. Hosting companies aren't known for their efficiency, nor are they associated with transparent discussion of whats going on when **** hits the fan.
Same here! Both..
Though right now the issue looks to be resolved regardless.. if in the future we encounter this, be aware that this would have only been another temporary fix.
Doing this action clears the routing table cache on your system, and causes it to reobtain it, which due to the down node would choose a working route. When the route autocorrects to the route it wants to be, you'd have the problem over again.
How long that takes to happen is variable depending on any one of the 20+ hops that your connection traverses.
I Think u get a better Server Provider:cool:
Mines working again. I bet my ISP's local DNS started routing info through a different pipeline and now I have access.
But im on sooo im happy for now
Before:
Tracing route to launcher.startrekonline.com [208.95.185.44]
over a maximum of 30 hops:
1 10 ms 12 ms 10 ms ****starred out***
2 11 ms 11 ms 11 ms ****starred out***
3 14 ms 14 ms 14 ms leed-bb-1c-ae3-0.network.virginmedia.net [62.253
.174.45]
4 * 15 ms 17 ms nrth-bb-1c-ae9-0.network.virginmedia.net [62.253
.174.122]
5 15 ms 16 ms 17 ms nrth-bb-1a-ae3-0.network.virginmedia.net [62.253
.174.105]
6 17 ms 25 ms 16 ms nrth-tmr-1-ae1-0.network.virginmedia.net [213.10
5.159.30]
7 33 ms 31 ms 34 ms fran-ic-1-as0-0.network.virginmedia.net [62.253.
185.81]
8 34 ms 35 ms 35 ms te0-7-0-7.mpd22.fra03.atlas.cogentco.com [130.11
7.14.133]
9 36 ms 35 ms 35 ms te0-0-0-2.mpd22.ams03.atlas.cogentco.com [130.11
7.0.133]
10 44 ms 41 ms 44 ms te0-1-0-2.ccr22.lpl01.atlas.cogentco.com [154.54
.37.110]
11 110 ms 118 ms 109 ms te0-1-0-3.ccr22.bos01.atlas.cogentco.com [154.54
.42.105]
12 108 ms 107 ms 109 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.25
4]
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 * 108 ms * playstartrekonline.de [208.95.185.44]
21 * * * Request timed out.
22 * * * Request timed out.
23 * 110 ms * playstartrekonline.de [208.95.185.44]
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * 108 ms * playstartrekonline.de [208.95.185.44]
Trace complete.
After:
Tracing route to launcher.startrekonline.com [208.95.185.44]
over a maximum of 30 hops:
1 24 ms 106 ms 8 ms **starred out***
2 10 ms 8 ms 11 ms ***starred out***
3 12 ms 10 ms 12 ms midd-core-2b-ae1-0.network.virginmedia.net [62.2
54.64.194]
4 21 ms 20 ms 19 ms brhm-bb-1b-ae12-0.network.virginmedia.net [62.25
3.174.49]
5 21 ms 22 ms 20 ms ae1.lon25.ip4.tinet.net [77.67.65.161]
6 100 ms 98 ms 104 ms xe-3-0-0.bos11.ip4.tinet.net [141.136.109.138]
7 238 ms 394 ms 207 ms internap-gw.ip4.tinet.net [77.67.77.54]
8 101 ms 99 ms 103 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.4
1]
9 102 ms 105 ms 107 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
10 101 ms 100 ms 98 ms fr.startrekonline.com [208.95.185.44]
Trace complete.
So the launcher seems to work fine now but i cannot use the login server for some reason.
Edit - 3rd time to try to login did the trick. Im now in.
At this time, we believe the issue has been resolved. We thank you very much for your patience today, and for all the tracerts posted in this thread. As you can see from the tracerts posted by your fellow players, the issues that you were running into were occurring during the "hops" before you actually got to the launcher -- we are now talking and working with our external routing provider to investigate why this was occurring.
Again, thank you for your patience and support, and we'll see you in-game!
Cheers,
Brandon =/\=
If this is a problem with an external services vendor, I will be in California two weeks hence... I can organize the angry mob and lead the march. Also, I have exclusive distribution rights to torches that meet California's strict air-quality rules along with pitchforks that meet or exceed California's product safety requirements.
Drop me a PM if I'm needed, otherwise I won't be in the neighborhood, my business is near Humboldt.
Poland - Piotrk?w Trybunalski
Thanks for fixing it (at least for some players)
what i did while i had this problem for *FREE**FREE**FREE* was:
1) set up an account and downloaded Private Tunnel (PT).
2) ran PT with Connect to: San Jose CA
3) opened the game launcher. (couldnt get this far with out PT before)
4) entered log in info and the game loaded and popped up the character select screen.
5) disconnected and exited PT (brings the game back to the IN GAME log in screen.
6) re-entered log in and was off to kill more borg.
i had to do this a few times as i had fully closed out of STO to take dogs for a walk and run to the store. also to note PT only allows for 100 MB *FREE* of data to go through their lines you can also pay for more. so the trick is to get it to go past the launcher and disconnect from PT.
the first time i did it i forgot to disconnect from PT and ran out the 100 MB quickly. so i used a different email and re-signed up for it and was fine.
Guys, if you are still having issues, please be patient. The problem as described by Brandon above is not a problem on YOUR end or THEIR [Cryptic's] end but in between. In laymen terms, you don't connect directly through to Cryptic but you "hop" along from one network segment to the next. Much like getting on a interstate to go from your house in New York to Cyrptic outside of San Fran, there is NOT a direct interstate route but you go from one interstate road to another as you need.
This is something that is external to Cryptic and thus not something that can be fixed "BY" them either. Again, thank you for understanding and your patience as the STO team (IMHO) wants everyone to be online for the 3 year anniversary.
Even though I can log into the game and have been able to throughout this random issue, I have included my trace route below in case it helps.
[Location - Columbus Ohio. Using Time Warner Cable Wideband (50Mbps) ]
Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.
C:\Users\matt>tracert patchserver.crypticstudios.com
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms CISCOE3000 [10.10.1.254]
2 9 ms 8 ms 7 ms 10.88.128.1
3 17 ms 15 ms 15 ms ae0-1170.cr02.clmkohpe.midohio.rr.com [184.59.24
3.213]
4 14 ms 7 ms 15 ms network-065-029-001-034.midwest.rr.com [65.29.1.
34]
5 24 ms 23 ms 23 ms ae-9-0.cr0.chi30.tbone.rr.com [107.14.19.16]
6 42 ms 47 ms 47 ms ae15.120.pr0.dfw10.tbone.rr.com [66.109.9.41]
7 40 ms 40 ms 38 ms 107.14.17.232
8 60 ms 41 ms 96 ms 107.14.16.30
9 80 ms 89 ms 45 ms pr2-ge-7-0-0.daq.savvis.net [204.70.207.182]
10 41 ms 41 ms 41 ms cr1-tengig0-7-5-0.dallas.savvis.net [204.70.200.
170]
11 63 ms 61 ms 60 ms cr2-ten-0-3-2-0.nyr.savvis.net [204.70.224.210]
12 61 ms 61 ms 75 ms er1-te-2-1.newyorknyd.savvis.net [204.70.196.70]
13 68 ms 70 ms 67 ms msr1-te-0-3-0-0.bos.savvis.net [206.28.97.205]
14 66 ms 67 ms 69 ms 206.28.97.137
15 75 ms 72 ms 74 ms internap.boston.savvis.net [208.172.51.230]
16 72 ms 76 ms 71 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.4
1]
17 76 ms 71 ms 71 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
18 72 ms 70 ms 71 ms 208.95.185.41
Trace complete.
C:\Users\matt>
PS Commentary - Going back to my example of interstates, looks like I went from Ohio to Texas to New York to Boston MA. Man, that was a heck of a Commute in distance but the shortest in time.
Find us at CovenantofHonor.com. My Twitter handle; @jmattmiracle
Many thanks to the team, to have solved these problems as quickly.
MB: MSI MPG X570 GP 2.0
CPU: AMD Ryzen 7 3700X
Mem: Samsung DDR4 -2132 8GB (x2)
Graph: NVIDIA GeForce GTX 1060 6GB
System: Micrsft. Windows 10 Pro v.21H2
Now it says "Loading" in the Launcher...no more progress.
edit: InGame now, but Launcher is still not working properly.
Join The Space Invaders,..... Federation and KDF fleets.
Just tried to relaunch the game and it happened again! So the fix seems to have unfixed!