Launcher timeout.

kojirohellfire

So after whatever modifications they made to the launcher today went through, the launcher refuses to connect. It just simply times out. This is for both CO and STO.

http://i778.photobucket.com/albums/yy70/KojiroJames/brokenlauncher_zpsc8c49417.jpg

Tracert and nettest:

tracert wrote:

Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Windows>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 97-126-93-220.tukw.qwest.net [192.168.10.1]
2 2 ms 2 ms 2 ms 192.168.0.1
3 * 42 ms 44 ms tukw-dsl-gw67.tukw.qwest.net [63.231.10.67]
4 41 ms 41 ms 41 ms tukw-agw1.inet.qwest.net [71.217.186.17]
5 61 ms 60 ms 61 ms sjp-brdr-04.inet.qwest.net [67.14.34.38]
6 99 ms 94 ms 98 ms te0-4-0-29.ccr21.sjc03.atlas.cogentco.com [154.5
4.12.189]
7 97 ms 104 ms 104 ms be2047.ccr22.sjc01.atlas.cogentco.com [154.54.5.
113]
8 105 ms 103 ms 97 ms be2167.mpd22.sfo01.atlas.cogentco.com [154.54.28
.77]
9 143 ms 143 ms 146 ms be2135.mpd22.mci01.atlas.cogentco.com [154.54.6.
34]
10 151 ms 150 ms 151 ms te0-7-0-1.mpd22.ord01.atlas.cogentco.com [154.54
.25.78]
11 177 ms 175 ms 173 ms be2137.ccr21.bos01.atlas.cogentco.com [154.54.43
.194]
12 163 ms 164 ms 165 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.25
4]
13 172 ms 181 ms 179 ms 38.111.40.114
14 167 ms 166 ms 163 ms 208.95.185.41

Trace complete.

C:\Windows>

nettest wrote:

contacting nettest server..timed out
hit return to exit

grouchyotaku

If your 'Net Test' can't connect to the test server. (Not STO, a test server, so STO is out of the picture, and only the Internet connection is involved) Then that means either your being blocked by something (Firewall, ISP throttling, etc.) or your being screwed by the connection path through the Internet to the STO network. (which is most likely the case)

The jump in latency between Qwest and the Cogent backbone looks suspicious. Try using the US Proxy setting in the option menu of the Launcher and see if this improves the condition (or not...)

kojirohellfire

grouchyotaku wrote: »

The jump in latency between Qwest and the Cogent backbone looks suspicious. Try using the US Proxy setting in the option menu of the Launcher and see if this improves the condition (or not...)

Perhaps you didn't notice, but the problem is the launcher timing out. That means I can't access that option.

grouchyotaku

kojirohellfire wrote: »

Perhaps you didn't notice, but the problem is the launcher timing out. That means I can't access that option.

Then you're basically stuck. Even if you were to download the latest version of the Launcher, the first thing the new Launcher would try to do is to check to see if its the current version. And if it can't connect to the patch server, then the same thing will happen.

Looks like its time to complain to your ISP about this...