For those that just posted their tracerts above (mrbaconsah daeceis and zetaeffritt), if you can, can you re-run and paste your results here after pointing to accounts.crypticstudios.com? For those that are planning to post, please post tracerts for launcher.startrekonline.com and accounts.crypticstudios.com -- this info will be very helpful to the Engineers.
Cheers,
Brandon =/\=
As requested:
Tracing route to launcher.startrekonline.com [208.95.185.44]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 11 ms 9 ms 20 ms 089-101-002001.ntlworld.ie [89.101.2.1]
3 18 ms 7 ms 8 ms 188.141.126.33
4 14 ms 9 ms 20 ms 84.116.239.78
5 24 ms 16 ms 20 ms 84.116.238.198
6 15 ms 16 ms 18 ms 213.46.165.94
7 98 ms 100 ms 101 ms xe-1-2-0.bos11.ip4.tinet.net [89.149.183.13]
8 101 ms 102 ms 105 ms internap-gw.ip4.tinet.net [77.67.77.54]
9 110 ms 100 ms 100 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.4
1]
10 107 ms 125 ms 106 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
11 * * * Request timed out.
12 * * * Request timed out.
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 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
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 107 ms * * startrekonline.com [208.95.185.44]
Tracing route to accounts.crypticstudios.com [208.95.185.165]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 9 ms 7 ms 6 ms 089-101-002001.ntlworld.ie [89.101.2.1]
3 9 ms 6 ms 7 ms 188.141.127.33
4 14 ms 14 ms 22 ms 84.116.238.198
5 40 ms 17 ms 14 ms 213.46.165.94
6 101 ms 100 ms 129 ms xe-1-2-0.bos11.ip4.tinet.net [89.149.183.13]
7 102 ms 106 ms 101 ms internap-gw.ip4.tinet.net [77.67.77.54]
8 100 ms 99 ms 99 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.4
1]
9 110 ms 106 ms 106 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
10 101 ms 101 ms 101 ms accounts.crypticstudios.com [208.95.185.165]
Trace complete.
Seems I can't get through the perfectworld border... any chance I can get a visa? ^^
I'm trying to find a way around it messing around with http responses.
I have no idea what the client expects to see when it queries the server for patch information, if anyone knows that I can put up a web server that replies and we can move past their testing. If not, I'll keep digging and see if I can't find the response myself.
I just checked in with the team and they are running some tests with our external routing vendor to try and identify where the cause of yesterday's issues lies. If you're having receiving an error, please try again in a few minutes as they are completing their tests.
Cheers,
Brandon =/\=
*hovers mouse over CMD.exe and slowly moves over to SWTOR_setup.exe*
I am tired of this mess. I will try signing into "Star Trek: Online" later tonight.
Ok so you broke the patch server yesterday even for the eastern half of the US then you "Fixed it". I was playing then changing screens and disconnected from the server and the problem returns. When are you going to actually fix this issue? Don't blow smoke up our nacelles. If you are actually running a few tests then it might be in your best interest to actually send out a system message stating that and give estimated time for bringing the server back up. Simply giving me a 3 sentence explanation is non-existent customer support. Take this message and fix your issue- don't tell me to post my damn target trace isp infomation- hire some intelligent network/system engineers that actually know what they are doing. The only thing that your tests are doing is making your game lose money
Man I had my wallet next to my computer about to lay down some cash and possibly go gold, but for this game to be out now for awhile and this to be happening as if it were still in BETA is nuts. Wallet is back in my pocket.
It's simply amazing how many people were just about to spend some money but have decided not to. I bet it correlates to the number of legal & WWII experts online...
I'm trying to find a way around it messing around with http responses.
I have no idea what the client expects to see when it queries the server for patch information, if anyone knows that I can put up a web server that replies and we can move past their testing. If not, I'll keep digging and see if I can't find the response myself.
You can use a free VPN client like PrivitizeVPN or Hotspotshield.
I love how they have to underline that it's their 'top priority' like they don't believe themselves or something. >.>
Its stands as a cruel indication that even Cryptic knows the playerbase has little faith in anything they say or promise. The real kicker is rubbing the customer nose in the fact OTHER players are not affected.
Yeah, thanks for telling me others can play while I cant for the second day in a row. Apparantly, Cryptic only really give a TRIBBLE if a problem is serious enough to affect the ENTIRE community.
Otherwise, as long as some folks are buying lockboxes who cares ?
It's simply amazing how many people were just about to spend some money but have decided not to. I bet it correlates to the number of legal & WWII experts online...
I'm the other way around, I already spent some money and now I can't use my nifty-grifty ship! Q.Q
Daily basis, it was happening before the patch, and it happened for 10+ hours yesterday.
260+ pages on this fault and all we get is a "we are investigating".
Maybe the word "sorry" doesn't exist in STO's dictionary.
You might want to look at the first page. If you do, you will notice that the first post is from November 17, 2011. This thread covers more than one issue.
Routenverfolgung zu launcher.startrekonline.com [208.95.185.44] ?ber maximal 30
Abschnitte:
1 2 ms 2 ms 1 ms fritz.fonwlan.box [192.168.178.1]
2 32 ms 32 ms 33 ms 84.116.231.160
3 36 ms 33 ms 33 ms 84.116.229.201
4 33 ms 33 ms 34 ms at-vie-xion-pe02-vl-2056.upc.at [84.116.228.205]
5 35 ms 35 ms 34 ms at-vie15a-rd1-vl-2051.aorta.net [84.116.229.1]
6 33 ms 33 ms 65 ms 213.46.173.125
7 34 ms 34 ms 34 ms at-inn01a-ra1-so-1-0-0-0.aorta.net [213.46.173.2
26]
8 150 ms 149 ms 148 ms xe-3-0-0.bos11.ip4.tinet.net [141.136.109.138]
9 142 ms 142 ms 141 ms internap-gw.ip4.tinet.net [77.67.77.54]
10 141 ms 143 ms 141 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.1
04]
11 153 ms 141 ms 144 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
12 * * * Zeit?berschreitung der Anforderung.
13 * * * Zeit?berschreitung der Anforderung.
14 * * * Zeit?berschreitung der Anforderung.
15 * * * Zeit?berschreitung der Anforderung.
16 * * * Zeit?berschreitung der Anforderung.
17 * * * Zeit?berschreitung der Anforderung.
18 * * * Zeit?berschreitung der Anforderung.
19 * * * Zeit?berschreitung der Anforderung.
20 * * * Zeit?berschreitung der Anforderung.
21 144 ms * * playstartrekonline.eu [208.95.185.44]
22 * * * Zeit?berschreitung der Anforderung.
23 * * * Zeit?berschreitung der Anforderung.
24 * * * Zeit?berschreitung der Anforderung.
25 * * * Zeit?berschreitung der Anforderung.
26 * * * Zeit?berschreitung der Anforderung.
27 * * * Zeit?berschreitung der Anforderung.
28 * * * Zeit?berschreitung der Anforderung.
29 * * * Zeit?berschreitung der Anforderung.
30 * * * Zeit?berschreitung der Anforderung.
Ablaufverfolgung beendet.
Routenverfolgung zu accounts.crypticstudios.com [208.95.185.165] ?ber maximal 30
Abschnitte:
1 1 ms 1 ms 2 ms fritz.fonwlan.box [192.168.178.1]
2 31 ms 31 ms 32 ms 84.116.231.160
3 33 ms 33 ms 32 ms 84.116.229.201
4 34 ms 34 ms 34 ms at-vie-xion-pe01-vl-2055.upc.at [84.116.229.9]
5 35 ms 32 ms 44 ms at-vie01a-rd1-vl-2050.aorta.net [84.116.228.193]
6 66 ms 33 ms 33 ms at-vie05b-ri2-xe-3-2-0.aorta.net [213.46.173.117
]
7 34 ms 35 ms 35 ms at-inn01a-ra1-so-1-0-0-0.aorta.net [213.46.173.2
26]
8 146 ms 146 ms 147 ms xe-3-0-0.bos11.ip4.tinet.net [141.136.109.138]
9 141 ms 151 ms 158 ms internap-gw.ip4.tinet.net [77.67.77.54]
10 140 ms 138 ms 142 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.1
04]
11 152 ms 142 ms 144 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
12 143 ms 142 ms 141 ms accounts.crypticstudios.com [208.95.185.165]
Cryptic is still talking about "launcher issues" while the problem is the availability of their patchserver.
The on-demand patching ingame doesn't work properly either.
This also allows only one conclusion: Cryptic is lying. They did not find any sort of solution yesterday - they probably didn't do anything.
The whole diagnostic thing is another sham to mask their inactivity. They're doing nothing again.
Tomorrow it will be an "emergency downtime" to address this - just another ruse for Cryptic not doing anything and the issue just going away some time.
Tracing route to launcher.startrekonline.com [208.95.185.44]
over a maximum of 30 hops:
1 8 ms 11 ms 7 ms 10.28.48.1
2 16 ms 9 ms 11 ms 173-219-242-132-link.sta.suddenlink.net [173.219
.242.132]
3 9 ms 10 ms 16 ms 173-219-242-130-link.sta.suddenlink.net [173.219
.242.130]
4 30 ms 33 ms 41 ms cdm-**-****-*.lfkn.suddenlink.net [**.**.**.*]
5 40 ms 32 ms 29 ms 66-76-232-37.tyrd.suddenlink.net [66.76.232.37]
6 37 ms 31 ms 29 ms xe-2-2-0.er1.ord7.us.above.net [64.124.200.189]
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 155 ms 198 ms 373 ms 10.28.48.1
2 276 ms 163 ms 588 ms 173-219-242-132-link.sta.suddenlink.net [173.219
.242.132]
3 298 ms 335 ms 227 ms 173-219-242-130-link.sta.suddenlink.net [173.219
.242.130]
4 220 ms 255 ms 232 ms cdm-**-**-**-*.lfkn.suddenlink.net [**.**.**.*]
5 238 ms 182 ms 248 ms 66-76-232-37.tyrd.suddenlink.net [66.76.232.37]
6 221 ms 296 ms 268 ms xe-2-2-0.er1.ord7.us.above.net [64.124.200.189]
7 209 ms 279 ms 263 ms xe-0-0-0.er2.ord7.us.above.net [64.125.26.246]
8 328 ms 199 ms 278 ms te0-7-0-4.ccr21.ord03.atlas.cogentco.com [154.54
.10.197]
9 263 ms 290 ms 336 ms te0-3-0-1.mpd22.ord01.atlas.cogentco.com [154.54
.2.97]
10 302 ms 247 ms 221 ms te0-7-0-8.ccr21.bos01.atlas.cogentco.com [154.54
.24.53]
11 219 ms 320 ms 313 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
134]
12 314 ms 339 ms * 38.111.40.114
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 * * * Request timed out.
22 * * 70 ms 208.95.185.41
I had this problem some last night but after the first time it happened the game worked fine. I'm on the West Coast and I'm having the same problem as everyone else is. Only my message says It can't connect to the internet. So I reset modem and router, restarted laptop and even stupid as it was re installed the game (which sometimes works when PWE?CRYPTIC does fail which seems to happen a lot lately.) I hope it gets fixed soon. This is really getting old.
Its stands as a cruel indication that even Cryptic knows the playerbase has little faith in anything they say or promise. The real kicker is rubbing the customer nose in the fact OTHER players are not affected.
Yeah, thanks for telling me others can play while I cant for the second day in a row. Apparantly, Cryptic only really give a TRIBBLE if a problem is serious enough to affect the ENTIRE community.
Otherwise, as long as some folks are buying lockboxes who cares ?
And if they didn't, someone would come in here saying they could get in and everyone who could still not connect would come right back her pissing and moaning about how it came up & went back down again.
You can use a free VPN client like PrivitizeVPN or Hotspotshield.
You aren't understanding me correctly.
So, last night VPN resolved the issue fine. The problem last night was network routes, which if you change your route you would get in.
Today, this is not a route problem. This is a server problem. In order to facilitate their testing, they turned off the patch server. This is, for all intensive purposes, basically the same thing they do when they are patching/maintenance, except instead of putting server down they just turned the thing off.
The patcher/launcher server is strictly exactly that, it reports patch information and (if necessary) allows retrieval of updates.
If I knew the response code that the launcher waits for when it sends the request to http://launcher.crypticstudios.com, then bypassing the stupid check would be easy.
This is the same thing that most companies do when they want to test a server that recently failed for load - they point you at a dummy server that simply says things are fine while they test and you are never the wiser. It doesn't bypass logins or anything, it merely allows the launcher to move on and do its business without care to patching.
I have a vpn, i have 3 actually. I used them to play last night. But, right now, they're useless.
meh setting up SWTOR now....damn this mess:rolleyes:
*shrugs*
Seriously, before the patch was applied yesterday, I had absolutely no problem with logging into the system. Everything ran smoothly. Once the system went down, I ran that darn test four times. I waited an entire day, so that I could sign into the game.
If Cryptic is able to repeat the issue in-house, the problem originated with code they implemented in-house.
D?termination de l'itin?raire vers patchserver.crypticstudios.com [208.95.185.41]
avec un maximum de 30 sauts*:
1 1 ms <1 ms 1 ms FREEBOX [192.168.0.254]
2 36 ms 51 ms 25 ms 82.224.213.254
3 * 25 ms 55 ms vlq-6k-2-a5.routers.proxad.net [213.228.4.254]
4 26 ms 24 ms 34 ms th2-crs16-1-be1002.intf.routers.proxad.net [212.27.57.217]
5 57 ms 50 ms 44 ms bzn-crs16-1-be2000.intf.routers.proxad.net [212.27.57.210]
6 51 ms 46 ms 51 ms bzn-crs16-2-be1000.intf.routers.proxad.net [212.27.59.102]
7 70 ms 48 ms 90 ms te0-1-0-5.365.mag21.par01.atlas.cogentco.com [149.6.160.101]
8 59 ms 47 ms 64 ms te0-0-0-7.ccr21.par01.atlas.cogentco.com [130.117.49.81]
9 54 ms 63 ms 83 ms te0-2-0-1.ccr21.lon13.atlas.cogentco.com [130.117.51.29]
10 125 ms 138 ms 126 ms te0-7-0-33.ccr21.bos01.atlas.cogentco.com [154.54.5.161]
11 128 ms 128 ms 172 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.134]
12 * * * D?lai d'attente de la demande d?pass?.
13 * * * D?lai d'attente de la demande d?pass?.
14 * * * D?lai d'attente de la demande d?pass?.
15 * * * D?lai d'attente de la demande d?pass?.
16 * * * D?lai d'attente de la demande d?pass?.
17 * * * D?lai d'attente de la demande d?pass?.
18 * * * D?lai d'attente de la demande d?pass?.
19 * * * D?lai d'attente de la demande d?pass?.
20 * * * D?lai d'attente de la demande d?pass?.
21 * * * D?lai d'attente de la demande d?pass?.
22 * * * D?lai d'attente de la demande d?pass?.
23 * * * D?lai d'attente de la demande d?pass?.
24 * * * D?lai d'attente de la demande d?pass?.
25 * * * D?lai d'attente de la demande d?pass?.
26 * * * D?lai d'attente de la demande d?pass?.
27 * * 133 ms 208.95.185.41
Seriously, before the patch was applied yesterday, I had absolutely no problem with logging into the system. Everything ran smoothly. Once the system went down, I ran that darn test four times. I waited an entire day, so that I could sign into the game.
If Cryptic is able to repeat the issue in-house, the problem originated with code they implemented in-house.
The issue appeared before the patch yesterday, so it's unrelated.
I have a vpn, i have 3 actually. I used them to play last night. But, right now, they're useless.
Okay. My tracerts show that its the launcher address and patchserver address causing the block (not accounts), but I can still access the game using a vpn client.
Seriously, before the patch was applied yesterday, I had absolutely no problem with logging into the system. Everything ran smoothly. Once the system went down, I ran that darn test four times. I waited an entire day, so that I could sign into the game.
If Cryptic is able to repeat the issue in-house, the problem originated with code they implemented in-house.
I was playing just fine until a map change and then boom.......the system go BOOM!!!!!!!
Comments
It was great. lol
No it isn't. I have the issue and Pando doesn't run on my system.
As requested:
Seems I can't get through the perfectworld border... any chance I can get a visa? ^^
I have no idea what the client expects to see when it queries the server for patch information, if anyone knows that I can put up a web server that replies and we can move past their testing. If not, I'll keep digging and see if I can't find the response myself.
I am tired of this mess. I will try signing into "Star Trek: Online" later tonight.
I ran the test four times yesterday.
:mad:
It's simply amazing how many people were just about to spend some money but have decided not to. I bet it correlates to the number of legal & WWII experts online...
You can use a free VPN client like PrivitizeVPN or Hotspotshield.
Its stands as a cruel indication that even Cryptic knows the playerbase has little faith in anything they say or promise. The real kicker is rubbing the customer nose in the fact OTHER players are not affected.
Yeah, thanks for telling me others can play while I cant for the second day in a row. Apparantly, Cryptic only really give a TRIBBLE if a problem is serious enough to affect the ENTIRE community.
Otherwise, as long as some folks are buying lockboxes who cares ?
:mad:
I'm the other way around, I already spent some money and now I can't use my nifty-grifty ship! Q.Q
You might want to look at the first page. If you do, you will notice that the first post is from November 17, 2011. This thread covers more than one issue.
--->Ground Combat General Bugs Directory
Real join date: March 2012 / PvP Veteran since May 2012 (Ground and Space)
Ied rather play no game than SWTOR
Routenverfolgung zu launcher.startrekonline.com [208.95.185.44] ?ber maximal 30
Abschnitte:
1 2 ms 2 ms 1 ms fritz.fonwlan.box [192.168.178.1]
2 32 ms 32 ms 33 ms 84.116.231.160
3 36 ms 33 ms 33 ms 84.116.229.201
4 33 ms 33 ms 34 ms at-vie-xion-pe02-vl-2056.upc.at [84.116.228.205]
5 35 ms 35 ms 34 ms at-vie15a-rd1-vl-2051.aorta.net [84.116.229.1]
6 33 ms 33 ms 65 ms 213.46.173.125
7 34 ms 34 ms 34 ms at-inn01a-ra1-so-1-0-0-0.aorta.net [213.46.173.2
26]
8 150 ms 149 ms 148 ms xe-3-0-0.bos11.ip4.tinet.net [141.136.109.138]
9 142 ms 142 ms 141 ms internap-gw.ip4.tinet.net [77.67.77.54]
10 141 ms 143 ms 141 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.1
04]
11 153 ms 141 ms 144 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
12 * * * Zeit?berschreitung der Anforderung.
13 * * * Zeit?berschreitung der Anforderung.
14 * * * Zeit?berschreitung der Anforderung.
15 * * * Zeit?berschreitung der Anforderung.
16 * * * Zeit?berschreitung der Anforderung.
17 * * * Zeit?berschreitung der Anforderung.
18 * * * Zeit?berschreitung der Anforderung.
19 * * * Zeit?berschreitung der Anforderung.
20 * * * Zeit?berschreitung der Anforderung.
21 144 ms * * playstartrekonline.eu [208.95.185.44]
22 * * * Zeit?berschreitung der Anforderung.
23 * * * Zeit?berschreitung der Anforderung.
24 * * * Zeit?berschreitung der Anforderung.
25 * * * Zeit?berschreitung der Anforderung.
26 * * * Zeit?berschreitung der Anforderung.
27 * * * Zeit?berschreitung der Anforderung.
28 * * * Zeit?berschreitung der Anforderung.
29 * * * Zeit?berschreitung der Anforderung.
30 * * * Zeit?berschreitung der Anforderung.
Ablaufverfolgung beendet.
Routenverfolgung zu accounts.crypticstudios.com [208.95.185.165] ?ber maximal 30
Abschnitte:
1 1 ms 1 ms 2 ms fritz.fonwlan.box [192.168.178.1]
2 31 ms 31 ms 32 ms 84.116.231.160
3 33 ms 33 ms 32 ms 84.116.229.201
4 34 ms 34 ms 34 ms at-vie-xion-pe01-vl-2055.upc.at [84.116.229.9]
5 35 ms 32 ms 44 ms at-vie01a-rd1-vl-2050.aorta.net [84.116.228.193]
6 66 ms 33 ms 33 ms at-vie05b-ri2-xe-3-2-0.aorta.net [213.46.173.117
]
7 34 ms 35 ms 35 ms at-inn01a-ra1-so-1-0-0-0.aorta.net [213.46.173.2
26]
8 146 ms 146 ms 147 ms xe-3-0-0.bos11.ip4.tinet.net [141.136.109.138]
9 141 ms 151 ms 158 ms internap-gw.ip4.tinet.net [77.67.77.54]
10 140 ms 138 ms 142 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.1
04]
11 152 ms 142 ms 144 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
12 143 ms 142 ms 141 ms accounts.crypticstudios.com [208.95.185.165]
Ablaufverfolgung beendet.
looks to me the same issue like yesterday
The on-demand patching ingame doesn't work properly either.
This also allows only one conclusion:
Cryptic is lying. They did not find any sort of solution yesterday - they probably didn't do anything.
The whole diagnostic thing is another sham to mask their inactivity. They're doing nothing again.
Tomorrow it will be an "emergency downtime" to address this - just another ruse for Cryptic not doing anything and the issue just going away some time.
He's dead, Jim.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>tracert launcher.startrekonline.com
Tracing route to launcher.startrekonline.com [208.95.185.44]
over a maximum of 30 hops:
1 8 ms 11 ms 7 ms 10.28.48.1
2 16 ms 9 ms 11 ms 173-219-242-132-link.sta.suddenlink.net [173.219
.242.132]
3 9 ms 10 ms 16 ms 173-219-242-130-link.sta.suddenlink.net [173.219
.242.130]
4 30 ms 33 ms 41 ms cdm-**-****-*.lfkn.suddenlink.net [**.**.**.*]
5 40 ms 32 ms 29 ms 66-76-232-37.tyrd.suddenlink.net [66.76.232.37]
6 37 ms 31 ms 29 ms xe-2-2-0.er1.ord7.us.above.net [64.124.200.189]
7 56 ms 35 ms 30 ms xe-1-0-0.er2.ord7.us.above.net [64.125.26.6]
8 27 ms 37 ms 37 ms te0-7-0-4.ccr21.ord03.atlas.cogentco.com [154.54
.10.197]
9 34 ms 29 ms 30 ms te0-3-0-0.mpd22.ord01.atlas.cogentco.com [154.54
.5.9]
10 70 ms 64 ms 63 ms te0-3-0-1.ccr21.bos01.atlas.cogentco.com [154.54
.7.82]
11 69 ms 58 ms 60 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42
]
12 * * * Request timed out.
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 * * * Request timed out.
22 97 ms * * startrekonline.com [208.95.185.44]
23 * * * Request timed out.
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 99 ms * * startrekonline.com [208.95.185.44]
Trace complete.
patchserver.crypticstudios.com
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>tracert patchserver.crypticstudios.com
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 155 ms 198 ms 373 ms 10.28.48.1
2 276 ms 163 ms 588 ms 173-219-242-132-link.sta.suddenlink.net [173.219
.242.132]
3 298 ms 335 ms 227 ms 173-219-242-130-link.sta.suddenlink.net [173.219
.242.130]
4 220 ms 255 ms 232 ms cdm-**-**-**-*.lfkn.suddenlink.net [**.**.**.*]
5 238 ms 182 ms 248 ms 66-76-232-37.tyrd.suddenlink.net [66.76.232.37]
6 221 ms 296 ms 268 ms xe-2-2-0.er1.ord7.us.above.net [64.124.200.189]
7 209 ms 279 ms 263 ms xe-0-0-0.er2.ord7.us.above.net [64.125.26.246]
8 328 ms 199 ms 278 ms te0-7-0-4.ccr21.ord03.atlas.cogentco.com [154.54
.10.197]
9 263 ms 290 ms 336 ms te0-3-0-1.mpd22.ord01.atlas.cogentco.com [154.54
.2.97]
10 302 ms 247 ms 221 ms te0-7-0-8.ccr21.bos01.atlas.cogentco.com [154.54
.24.53]
11 219 ms 320 ms 313 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
134]
12 314 ms 339 ms * 38.111.40.114
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 * * * Request timed out.
22 * * 70 ms 208.95.185.41
Trace complete.
And if they didn't, someone would come in here saying they could get in and everyone who could still not connect would come right back her pissing and moaning about how it came up & went back down again.
You aren't understanding me correctly.
So, last night VPN resolved the issue fine. The problem last night was network routes, which if you change your route you would get in.
Today, this is not a route problem. This is a server problem. In order to facilitate their testing, they turned off the patch server. This is, for all intensive purposes, basically the same thing they do when they are patching/maintenance, except instead of putting server down they just turned the thing off.
The patcher/launcher server is strictly exactly that, it reports patch information and (if necessary) allows retrieval of updates.
If I knew the response code that the launcher waits for when it sends the request to http://launcher.crypticstudios.com, then bypassing the stupid check would be easy.
This is the same thing that most companies do when they want to test a server that recently failed for load - they point you at a dummy server that simply says things are fine while they test and you are never the wiser. It doesn't bypass logins or anything, it merely allows the launcher to move on and do its business without care to patching.
I have a vpn, i have 3 actually. I used them to play last night. But, right now, they're useless.
Seriously, before the patch was applied yesterday, I had absolutely no problem with logging into the system. Everything ran smoothly. Once the system went down, I ran that darn test four times. I waited an entire day, so that I could sign into the game.
If Cryptic is able to repeat the issue in-house, the problem originated with code they implemented in-house.
I don't believe in coincidences.
Copyright (c) 2009 Microsoft Corporation. Tous droits r?serv?s.
C:\Users\HOME>tracert patchserver.crypticstudios.com
D?termination de l'itin?raire vers patchserver.crypticstudios.com [208.95.185.41]
avec un maximum de 30 sauts*:
1 1 ms <1 ms 1 ms FREEBOX [192.168.0.254]
2 36 ms 51 ms 25 ms 82.224.213.254
3 * 25 ms 55 ms vlq-6k-2-a5.routers.proxad.net [213.228.4.254]
4 26 ms 24 ms 34 ms th2-crs16-1-be1002.intf.routers.proxad.net [212.27.57.217]
5 57 ms 50 ms 44 ms bzn-crs16-1-be2000.intf.routers.proxad.net [212.27.57.210]
6 51 ms 46 ms 51 ms bzn-crs16-2-be1000.intf.routers.proxad.net [212.27.59.102]
7 70 ms 48 ms 90 ms te0-1-0-5.365.mag21.par01.atlas.cogentco.com [149.6.160.101]
8 59 ms 47 ms 64 ms te0-0-0-7.ccr21.par01.atlas.cogentco.com [130.117.49.81]
9 54 ms 63 ms 83 ms te0-2-0-1.ccr21.lon13.atlas.cogentco.com [130.117.51.29]
10 125 ms 138 ms 126 ms te0-7-0-33.ccr21.bos01.atlas.cogentco.com [154.54.5.161]
11 128 ms 128 ms 172 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.134]
12 * * * D?lai d'attente de la demande d?pass?.
13 * * * D?lai d'attente de la demande d?pass?.
14 * * * D?lai d'attente de la demande d?pass?.
15 * * * D?lai d'attente de la demande d?pass?.
16 * * * D?lai d'attente de la demande d?pass?.
17 * * * D?lai d'attente de la demande d?pass?.
18 * * * D?lai d'attente de la demande d?pass?.
19 * * * D?lai d'attente de la demande d?pass?.
20 * * * D?lai d'attente de la demande d?pass?.
21 * * * D?lai d'attente de la demande d?pass?.
22 * * * D?lai d'attente de la demande d?pass?.
23 * * * D?lai d'attente de la demande d?pass?.
24 * * * D?lai d'attente de la demande d?pass?.
25 * * * D?lai d'attente de la demande d?pass?.
26 * * * D?lai d'attente de la demande d?pass?.
27 * * 133 ms 208.95.185.41
Itin?raire d?termin
The issue appeared before the patch yesterday, so it's unrelated.
Cheers,
Brandon =/\=
Okay. My tracerts show that its the launcher address and patchserver address causing the block (not accounts), but I can still access the game using a vpn client.