Right, I'm going to go take a nap or something and check back in a few hours, keep up the good work cryptic, and don't let the haters get ya down.
Good work? The whole point of cryptic being here is that the game should work. If it doesn't work, it's their job to fix it. Doing your job isn't good work, its a job.
Also, "haters"? Do you mean people who aren't fanboys who blindly follow where cryptic follow?
I don't really think this is cogent at fault here. on most of these tracerts it reads bos6.cogent as the last line active. the next on some reads the ip address:
38.111.40.114
which is one perfectworld's servers. so it could be that system that is playing up and the cogent system is pointing at it correctly.
Although having said that, doesn't explain the packets that DO get through on broadband.
ping 38.111.40.114
Pinging 38.111.40.114 with 32 bytes of data:
Reply from 38.111.40.114: bytes=32 time=119ms TTL=16
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 38.111.40.114:
Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
Approximate round trip times in milli-seconds:
Minimum - 119ms, Maximum = 119ms, Average = 119ms
About two weeks ago, a peerage problem during peak usage was noticed in a bottleneck from Cox Communications through Cogent. Cogent suggested that the end user ISP reroute the traffic away from Cogent. I'm not sure how each of us can solve this independently, so the onus still falls on PW/Cryptic to solve this routing issue.
The very fact that this exact problem occurred with another MMO game just 2 weeks ago says that the devs aren't doing their research. They performed an unscheduled patch, which put an unexpected load on Cogents servers. Seems like load balancing would be part of the network admins / devs jobs.
Please do your jobs.
And let us continue to funnel money through our bank accounts to you :P I'm sure some would rather save their money than sit waiting patiently for an avoidable problem to be solved.
Is the PWE staff to incompetant to build in a manual patch option for the cases where the real world bites em on the TRIBBLE$ ? Your talking maybe an hours worth of work to bundle the (existing)patch test the exe and multible point source link the file. That gets complaints down to a faint roar, gives you breathing space to address the real issue with fewer time preassures, and prevents creating an avoidable black eye. I fail to see the downside.
Routenverfolgung zu patchserver.crypticstudios.com [208.95.185.41] ?ber maximal
30 Abschnitte:
1 2 ms 2 ms 2 ms fritz.box [192.168.178.1]
2 12 ms 14 ms 10 ms 10.144.0.1
3 12 ms 14 ms 15 ms 7111A-MX960-01-ae10-1210.fra.unity-media.net [81
.210.128.65]
4 22 ms 10 ms 13 ms 84-116-131-149.aorta.net [84.116.131.149]
5 16 ms 12 ms 11 ms de-fra01a-ri2-xe-5-1-1.aorta.net [84.116.133.114
]
6 26 ms 9 ms 13 ms 84.116.132.198
7 10 ms 11 ms 11 ms xe-10-2-2.fra23.ip4.tinet.net [141.136.99.97]
8 124 ms 134 ms 115 ms xe-3-0-0.bos11.ip4.tinet.net [141.136.109.138]
9 120 ms 125 ms 116 ms internap-gw.ip4.tinet.net [77.67.77.54]
10 118 ms 113 ms 114 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.4
1]
11 118 ms 112 ms 123 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 * * * Zeit?berschreitung der Anforderung.
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.
____________________________
C:\Users\User>tracert launcher.startrekonline.com
Routenverfolgung zu launcher.startrekonline.com [208.95.185.44] ?ber maximal 30
Abschnitte:
1 2 ms 3 ms 3 ms fritz.box [192.168.178.1]
2 9 ms 9 ms 13 ms 10.144.0.1
3 16 ms 13 ms 12 ms 7111A-MX960-01-ae10-1210.fra.unity-media.net [81
.210.128.65]
4 * 20 ms 19 ms 84-116-131-149.aorta.net [84.116.131.149]
5 14 ms 12 ms 10 ms 84.116.132.169
6 12 ms 13 ms 12 ms 84.116.132.166
7 11 ms 13 ms 20 ms xe-5-1-1.fra23.ip4.tinet.net [77.67.73.105]
8 205 ms 112 ms 117 ms xe-3-0-0.bos11.ip4.tinet.net [141.136.109.138]
9 119 ms 110 ms 131 ms internap-gw.ip4.tinet.net [77.67.77.54]
10 111 ms 105 ms 106 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.1
04]
11 119 ms 111 ms 119 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 * * * Zeit?berschreitung der Anforderung.
22 * * * Zeit?berschreitung der Anforderung.
23 * * * Zeit?berschreitung der Anforderung.
24 * * * Zeit?berschreitung der Anforderung.
25 * * * Zeit?berschreitung der Anforderung.
26 106 ms * * launcher.startrekonline.com [208.95.185.44]
27 * * * Zeit?berschreitung der Anforderung.
28 * * * Zeit?berschreitung der Anforderung.
29 * * * Zeit?berschreitung der Anforderung.
30 * * * Zeit?berschreitung der Anforderung.
1 3 ms 1 ms 1 ms BThomehub.home [***.***.*.***]
2 6 ms 6 ms 6 ms 217.32.141.134
3 6 ms 6 ms 6 ms 217.32.141.174
4 11 ms 10 ms 10 ms 213.120.161.74
5 11 ms 17 ms 14 ms 31.55.164.245
6 11 ms 11 ms 11 ms 31.55.164.109
7 12 ms 11 ms 11 ms acc2-10GigE-0-5-0-6.bm.21cn-ipp.bt.net [109.159.
248.228]
8 20 ms 15 ms 15 ms core1-te0-13-0-17.ilford.ukcore.bt.net [109.159.
248.172]
9 14 ms 14 ms 14 ms core1-pos9-1.telehouse.ukcore.bt.net [194.74.65.
114]
10 16 ms 16 ms 15 ms t2as1-tge1-4.uk-lon1.eu.bt.net [166.49.211.141]
The team is investigating, but this does not seem to affect all players and may be regional. 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.
Cheers,
Brandon =/\=
herMicrosoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
i did the update on my moblie, but then i switched back to my normal internet it still will not connect?
if i use my moblie to play will that send my moblie bill througth the roof?
You don't need to stay on your mobile connection to play. Just use it to patch and launch the game, once you get to the character selection screen switch to your normal ISP, you will disconnect but you can login again just fine from the ingame login screen, the problem is just with the launcher servers.
Its borked plain and simple, and there really slow in addressing the problem. The speeds I get when it needs to patch in game are tragic to say the least. Im so glad I dont have to pay for this TRIBBLE.
A friend has the same problem.
At my connection no problems:
e.g. (a working route) (from germany)
traceroute patchserver.crypticstudios.com
traceroute to patchserver.crypticstudios.com (208.95.185.41), 30 hops max, 40 byte packets using UDP
1 172.26.64.1 (172.26.64.1) 14.604 ms 18.353 ms 17.149 ms
2 78.35.33.41 (78.35.33.41) 16.058 ms 14.945 ms 13.786 ms
3 core-maw1-vl206.netcologne.de (78.35.18.73) 12.502 ms 11.322 ms 10.164 ms
4 core-pg2-t14.netcologne.de (78.35.33.113) 9.005 ms 7.877 ms 7.348 ms
5 rtint3-po5.netcologne.de (87.79.16.254) 10.073 ms 7.136 ms 7.841 ms
6 212.162.17.1 (212.162.17.1) 8.311 ms 7.157 ms 10.080 ms
7 vl-3101-ve-128.ebr1.Dusseldorf1.Level3.net (4.69.161.129) 22.273 ms 21.055 ms 15.641 ms
8 ae-48-48.ebr3.Frankfurt1.Level3.net (4.69.143.178) 12.953 ms 12.398 ms ae-47-47.ebr3.Frankfurt1.Level3.net (4.69.143.174) 13.248 ms
9 ae-83-83.csw3.Frankfurt1.Level3.net (4.69.163.10) 13.552 ms 21.194 ms ae-93-93.csw4.Frankfurt1.Level3.net (4.69.163.14) 10.580 ms
10 * ae-4-90.edge5.Frankfurt1.Level3.net (4.69.154.201) 22.234 ms *
11 Cogent-level3-1x10G.Frankfurt.Level3.net (4.68.70.118) 19.933 ms Cogent-level3-1x10G.Frankfurt.Level3.net (4.68.70.114) 24.152 ms 22.934 ms
12 te0-1-0-5.mpd21.fra03.atlas.cogentco.com (130.117.49.37) 22.079 ms 154.54.76.61 (154.54.76.61) 20.887 ms te0-2-0-6.mpd22.fra03.atlas.cogentco.com (154.54.36.66) 19.751 ms
13 te0-4-0-2.mpd21.ams03.atlas.cogentco.com (154.54.39.173) 15.693 ms te0-3-0-2.ccr21.ams03.atlas.cogentco.com (154.54.39.177) 15.544 ms te0-1-0-2.ccr22.ams03.atlas.cogentco.com (130.117.2.230) 19.214 ms
14 te0-0-0-7.ccr21.lpl01.atlas.cogentco.com (154.54.37.74) 29.717 ms te0-5-0-0.ccr21.lpl01.atlas.cogentco.com (130.117.48.29) 28.537 ms te0-5-0-0.ccr22.lpl01.atlas.cogentco.com (130.117.49.65) 28.069 ms
15 te0-7-0-3.ccr21.bos01.atlas.cogentco.com (154.54.31.169) 98.338 ms te0-4-0-2.ccr21.bos01.atlas.cogentco.com (154.54.44.197) 98.194 ms te0-3-0-3.ccr21.bos01.atlas.cogentco.com (154.54.31.229) 98.163 ms
16 te0-5-0-4.ccr22.bos01.atlas.cogentco.com (154.54.85.217) 101.024 ms te3-2.ccr01.bos06.atlas.cogentco.com (154.54.46.130) 98.598 ms te3-4.ccr01.bos06.atlas.cogentco.com (154.54.46.134) 99.859 ms
17 38.111.40.114 (38.111.40.114) 106.802 ms * *
18 208.95.185.41 (208.95.185.41) 99.500 ms 38.111.40.114 (38.111.40.114) 102.011 ms *
Pinging 38.111.40.114 with 32 bytes of data:
Reply from 38.111.40.114: bytes=32 time=119ms TTL=16
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 38.111.40.114:
Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
Approximate round trip times in milli-seconds:
Minimum - 119ms, Maximum = 119ms, Average = 119ms
I'm in Massachusetts and here's my traceroute. I don't know how helpful it may be coming in this late but I hope it helps somewhat:
Tracing route to launcher.startrekonline.com [208.95.185.44]
over a maximum of 30 hops:
1 11 ms 9 ms 9 ms
2 9 ms 9 ms 8 ms crr02wrcsma-tge-0-2-0- .wrcs.ma.charter.com [96.34.84.168]
3 13 ms 13 ms 14 ms crr03oxfrma-tge-0-3-0-5.oxfr.ma.charter.com [96.34.80.228]
4 9 ms 10 ms 11 ms bbr01oxfrma-bue-1.oxfr.ma.charter.com [96.34.2.12]
5 * * * Request timed out.
6 25 ms 32 ms 25 ms bbr02ashbva-bue-2.ashb.va.charter.com [96.34.0.48]
7 22 ms 21 ms 21 ms te0-7-0-17.mpd22.iad02.atlas.cogentco.com [38.122.62.21]
8 22 ms 23 ms 23 ms te0-3-0-1.mpd22.dca01.atlas.cogentco.com [154.54.30.117]
9 22 ms 23 ms 22 ms te0-3-0-6.mpd22.jfk02.atlas.cogentco.com [154.54.3.234]
10 28 ms 27 ms 27 ms te0-5-0-7.ccr21.bos01.atlas.cogentco.com [154.54.47.237]
11 31 ms 28 ms 29 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 * * * 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 * * * Request timed out.
Trace complete.
Disclaimer: This post is in no way intended to be a troll or flame or slur of any other kind towards anyone or anything either directly or indirectly involved in or with, or not involved in or with, Star Trek Online and I proffer my sincerest apologies to anyone who believes it is directed to the aforementioned.
Is the PWE staff to incompetant to build in a manual patch option for the cases where the real world bites em on the TRIBBLE$ ? Your talking maybe an hours worth of work to bundle the (existing)patch test the exe and multible point source link the file. That gets complaints down to a faint roar, gives you breathing space to address the real issue with fewer time preassures, and prevents creating an avoidable black eye. I fail to see the downside.
The downside is that even with a fully patched game, gameclient.exe will still try to connect to the patcher and the patcher server is the problem.
Also, when in game content is still downloaded. For example in Foundry.
As usually. Cryptic and its crapy provider Cogent Communication are not able to provide full services.
There is no problem from users.
The problem has a name: Cryptic devs & Cogent communication.
The best team of incompetent people
This such IP doesn't respond. And what is this IP ? Cogent Communication !! http://whois.domaintools.com/38.111.40.114
My tracert
C:\Documents and Settings\Olivier>Tracert launcher.startrekonline.com
D?termination de l'itin?raire vers launcher.startrekonline.com [208.95.185.44]
avec un maximum de 30 sauts*:
1 22 ms 20 ms 20 ms 78.225.73.254
2 20 ms 20 ms 20 ms 78.225.73.254
3 21 ms 21 ms 22 ms 213.228.36.254
4 22 ms 23 ms 22 ms bzn-crs16-1-be1105.intf.routers.proxad.net [212.
27.56.197]
5 26 ms 23 ms 24 ms bzn-crs16-2-be1000.intf.routers.proxad.net [212.
27.59.102]
6 25 ms 24 ms 24 ms te0-1-0-4.377.mag21.par01.atlas.cogentco.com [14
9.6.115.25]
7 23 ms 23 ms 24 ms te0-0-0-10.ccr21.par01.atlas.cogentco.com [154.5
4.74.133]
8 32 ms 31 ms 30 ms te0-4-0-6.ccr21.lon13.atlas.cogentco.com [154.54
.37.177]
9 103 ms 103 ms 103 ms te0-7-0-33.ccr21.bos01.atlas.cogentco.com [154.5
4.5.161]
10 105 ms 107 ms 110 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
134]
11 * * 118 ms 38.111.40.114
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 * * * D?lai d'attente de la demande d?pass?.
28 * * * D?lai d'attente de la demande d?pass?.
29 * * * D?lai d'attente de la demande d?pass?.
30 * * * D?lai d'attente de la demande d?pass?.
We are aware of an issue with the launcher where some players may be getting an error upon launching it.
Damn, that's downright insulting.
SOME players MAY be getting an ERROR upon launching it. MAYBE - a VERY MINOR ERROR, SOMETIMES.
Community team: you're full of bs.
Your "error" is utter nonfunction of the game due to a failure in your network.
Your "some players" number in the thousands.
And the people "maybe" getting this "error" certainly get it with astonishing frequency.
Had exactly the same prob....but I think I have a solution called 'Expatshield'
http://expatshield.com/ - Expatshield is a free VPN (Virtual Private Network) from AnchorFree. Yes, the same guys how made Hotspotshield, but this one assigns a UK IP address. Very nice to have if want to watch BBC TV or stuff from their iPlayer by the way And I always use this when I do online banking and for some Youtube stuff that is not accessable with my 'normal' IP...
So I've started Expatshield first, load up the launcher and deactivitated/disconnect it when I had the character selection screen up and running. And there we are running the game nicely
Don't forget to disconnect from the VPN...otherwise you might facing a very laggy game performance.
Hope this works for you like it did for me
Do yourself a favor and DON'T do this. This expatshield thing takes over your browser, inserts advertising and re-directs your home page. And browsing with it is slow, slow, slow. Save yourself the trouble.
These are my results just quoting them to seperate them for this little bit of post.
The results are from Manchester United Kingdom using Sky Broadband ISP
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
We are aware of an issue with the launcher where some players may be getting an error upon launching it. Our team is investigating your reports and we hope to have a resolution as soon as possible -- it is our top priority. Again, not all players are affected, but if you are, please read this post.
Thanks you and we hope to have you back in-game ASAP.
- The Star Trek Online Community Team
"Thanks you"? They can't even sort out their spelling and grammar.
You're just a machine. And machines can be broken.
Glad it's their top priority but really find the dev who fubared this and put them out on their TRIBBLE.
Whoever broke this may not be a dev at all. The problem manifested before the downtime. It is also clearly something in the larger scheme of the internet. There is a bad device(s) somewhere malfunctioning, and it may not even be anything under Cryptic's purview.
Comments
I got that part, I meant for your home connection. Or does that take some serious hacker software/skills to do? =P
Also, "haters"? Do you mean people who aren't fanboys who blindly follow where cryptic follow?
ok will give it a go
thanks
ping 38.111.40.114
Pinging 38.111.40.114 with 32 bytes of data:
Reply from 38.111.40.114: bytes=32 time=119ms TTL=16
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 38.111.40.114:
Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
Approximate round trip times in milli-seconds:
Minimum - 119ms, Maximum = 119ms, Average = 119ms
---
Tracerts for Mobile ISP and DSL:
http://sto-forum.perfectworld.com/showpost.php?p=7690471&postcount=490
About two weeks ago, a peerage problem during peak usage was noticed in a bottleneck from Cox Communications through Cogent. Cogent suggested that the end user ISP reroute the traffic away from Cogent. I'm not sure how each of us can solve this independently, so the onus still falls on PW/Cryptic to solve this routing issue.
The very fact that this exact problem occurred with another MMO game just 2 weeks ago says that the devs aren't doing their research. They performed an unscheduled patch, which put an unexpected load on Cogents servers. Seems like load balancing would be part of the network admins / devs jobs.
Please do your jobs.
And let us continue to funnel money through our bank accounts to you :P I'm sure some would rather save their money than sit waiting patiently for an avoidable problem to be solved.
U know it baybay. Jan 2013'rs represent.
Routenverfolgung zu patchserver.crypticstudios.com [208.95.185.41] ?ber maximal
30 Abschnitte:
1 2 ms 2 ms 2 ms fritz.box [192.168.178.1]
2 12 ms 14 ms 10 ms 10.144.0.1
3 12 ms 14 ms 15 ms 7111A-MX960-01-ae10-1210.fra.unity-media.net [81
.210.128.65]
4 22 ms 10 ms 13 ms 84-116-131-149.aorta.net [84.116.131.149]
5 16 ms 12 ms 11 ms de-fra01a-ri2-xe-5-1-1.aorta.net [84.116.133.114
]
6 26 ms 9 ms 13 ms 84.116.132.198
7 10 ms 11 ms 11 ms xe-10-2-2.fra23.ip4.tinet.net [141.136.99.97]
8 124 ms 134 ms 115 ms xe-3-0-0.bos11.ip4.tinet.net [141.136.109.138]
9 120 ms 125 ms 116 ms internap-gw.ip4.tinet.net [77.67.77.54]
10 118 ms 113 ms 114 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.4
1]
11 118 ms 112 ms 123 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 * * * Zeit?berschreitung der Anforderung.
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.
____________________________
C:\Users\User>tracert launcher.startrekonline.com
Routenverfolgung zu launcher.startrekonline.com [208.95.185.44] ?ber maximal 30
Abschnitte:
1 2 ms 3 ms 3 ms fritz.box [192.168.178.1]
2 9 ms 9 ms 13 ms 10.144.0.1
3 16 ms 13 ms 12 ms 7111A-MX960-01-ae10-1210.fra.unity-media.net [81
.210.128.65]
4 * 20 ms 19 ms 84-116-131-149.aorta.net [84.116.131.149]
5 14 ms 12 ms 10 ms 84.116.132.169
6 12 ms 13 ms 12 ms 84.116.132.166
7 11 ms 13 ms 20 ms xe-5-1-1.fra23.ip4.tinet.net [77.67.73.105]
8 205 ms 112 ms 117 ms xe-3-0-0.bos11.ip4.tinet.net [141.136.109.138]
9 119 ms 110 ms 131 ms internap-gw.ip4.tinet.net [77.67.77.54]
10 111 ms 105 ms 106 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.1
04]
11 119 ms 111 ms 119 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 * * * Zeit?berschreitung der Anforderung.
22 * * * Zeit?berschreitung der Anforderung.
23 * * * Zeit?berschreitung der Anforderung.
24 * * * Zeit?berschreitung der Anforderung.
25 * * * Zeit?berschreitung der Anforderung.
26 106 ms * * launcher.startrekonline.com [208.95.185.44]
27 * * * Zeit?berschreitung der Anforderung.
28 * * * Zeit?berschreitung der Anforderung.
29 * * * Zeit?berschreitung der Anforderung.
30 * * * Zeit?berschreitung der Anforderung.
Ablaufverfolgung beendet.
2 6 ms 6 ms 6 ms 217.32.141.134
3 6 ms 6 ms 6 ms 217.32.141.174
4 11 ms 10 ms 10 ms 213.120.161.74
5 11 ms 17 ms 14 ms 31.55.164.245
6 11 ms 11 ms 11 ms 31.55.164.109
7 12 ms 11 ms 11 ms acc2-10GigE-0-5-0-6.bm.21cn-ipp.bt.net [109.159.
248.228]
8 20 ms 15 ms 15 ms core1-te0-13-0-17.ilford.ukcore.bt.net [109.159.
248.172]
9 14 ms 14 ms 14 ms core1-pos9-1.telehouse.ukcore.bt.net [194.74.65.
114]
10 16 ms 16 ms 15 ms t2as1-tge1-4.uk-lon1.eu.bt.net [166.49.211.141]
11 15 ms 14 ms 14 ms t2a1-ge4-0-0.uk-lon1.eu.bt.net [166.49.135.17]
12 16 ms 15 ms 15 ms te0-7-0-3.ccr21.lon01.atlas.cogentco.com [130.11
7.14.49]
13 16 ms 15 ms 15 ms te0-4-0-5.mpd21.lon13.atlas.cogentco.com [130.11
7.0.5]
14 88 ms 88 ms 87 ms te0-2-0-4.ccr21.bos01.atlas.cogentco.com [66.28.
4.189]
15 92 ms 89 ms 88 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
134]
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 * * * Request timed out.
Trace complete.
Less gimmicks MORE fixes. = happy customers how you find this hard to achieve baffles me.
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Sir Timothy>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 192.168.1.1
2 9 ms 7 ms 6 ms 10.113.176.1
3 11 ms 9 ms 9 ms gig5-1-20.nhvlny01-rtr001.cny.northeast.rr.com [
24.94.35.112]
4 17 ms 10 ms 9 ms rdc-74-74-109-170.cny.northeast.rr.com [74.74.10
9.170]
5 15 ms 17 ms 14 ms rdc-74-74-109-66.cny.northeast.rr.com [74.74.109
.66]
6 15 ms 15 ms 16 ms rdc-74-74-109-46.cny.northeast.rr.com [74.74.109
.46]
7 17 ms 14 ms 15 ms ae2-0.vstlny11-rtr000.nyroc.rr.com [74.74.108.11
8]
8 38 ms 34 ms 32 ms bundle-ether1.albynyyf-rtr000.nyroc.rr.com [24.2
4.21.208]
9 33 ms 32 ms 30 ms ae-5-0.cr0.nyc30.tbone.rr.com [66.109.6.74]
10 27 ms 28 ms 25 ms 107.14.19.147
11 28 ms 26 ms 27 ms te0-0-0-5.ccr21.jfk05.atlas.cogentco.com [154.54
.13.185]
12 28 ms 29 ms 27 ms te0-1-0-5.mpd21.jfk02.atlas.cogentco.com [154.54
.3.97]
13 33 ms 32 ms 34 ms te0-6-0-0.ccr21.bos01.atlas.cogentco.com [154.54
.0.29]
14 33 ms 34 ms 34 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
134]
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 * * * Request timed out.
Trace complete.
C:\Users\Sir Timothy>e is my test
You don't need to stay on your mobile connection to play. Just use it to patch and launch the game, once you get to the character selection screen switch to your normal ISP, you will disconnect but you can login again just fine from the ingame login screen, the problem is just with the launcher servers.
At my connection no problems:
e.g. (a working route) (from germany)
traceroute patchserver.crypticstudios.com
traceroute to patchserver.crypticstudios.com (208.95.185.41), 30 hops max, 40 byte packets using UDP
1 172.26.64.1 (172.26.64.1) 14.604 ms 18.353 ms 17.149 ms
2 78.35.33.41 (78.35.33.41) 16.058 ms 14.945 ms 13.786 ms
3 core-maw1-vl206.netcologne.de (78.35.18.73) 12.502 ms 11.322 ms 10.164 ms
4 core-pg2-t14.netcologne.de (78.35.33.113) 9.005 ms 7.877 ms 7.348 ms
5 rtint3-po5.netcologne.de (87.79.16.254) 10.073 ms 7.136 ms 7.841 ms
6 212.162.17.1 (212.162.17.1) 8.311 ms 7.157 ms 10.080 ms
7 vl-3101-ve-128.ebr1.Dusseldorf1.Level3.net (4.69.161.129) 22.273 ms 21.055 ms 15.641 ms
8 ae-48-48.ebr3.Frankfurt1.Level3.net (4.69.143.178) 12.953 ms 12.398 ms ae-47-47.ebr3.Frankfurt1.Level3.net (4.69.143.174) 13.248 ms
9 ae-83-83.csw3.Frankfurt1.Level3.net (4.69.163.10) 13.552 ms 21.194 ms ae-93-93.csw4.Frankfurt1.Level3.net (4.69.163.14) 10.580 ms
10 * ae-4-90.edge5.Frankfurt1.Level3.net (4.69.154.201) 22.234 ms *
11 Cogent-level3-1x10G.Frankfurt.Level3.net (4.68.70.118) 19.933 ms Cogent-level3-1x10G.Frankfurt.Level3.net (4.68.70.114) 24.152 ms 22.934 ms
12 te0-1-0-5.mpd21.fra03.atlas.cogentco.com (130.117.49.37) 22.079 ms 154.54.76.61 (154.54.76.61) 20.887 ms te0-2-0-6.mpd22.fra03.atlas.cogentco.com (154.54.36.66) 19.751 ms
13 te0-4-0-2.mpd21.ams03.atlas.cogentco.com (154.54.39.173) 15.693 ms te0-3-0-2.ccr21.ams03.atlas.cogentco.com (154.54.39.177) 15.544 ms te0-1-0-2.ccr22.ams03.atlas.cogentco.com (130.117.2.230) 19.214 ms
14 te0-0-0-7.ccr21.lpl01.atlas.cogentco.com (154.54.37.74) 29.717 ms te0-5-0-0.ccr21.lpl01.atlas.cogentco.com (130.117.48.29) 28.537 ms te0-5-0-0.ccr22.lpl01.atlas.cogentco.com (130.117.49.65) 28.069 ms
15 te0-7-0-3.ccr21.bos01.atlas.cogentco.com (154.54.31.169) 98.338 ms te0-4-0-2.ccr21.bos01.atlas.cogentco.com (154.54.44.197) 98.194 ms te0-3-0-3.ccr21.bos01.atlas.cogentco.com (154.54.31.229) 98.163 ms
16 te0-5-0-4.ccr22.bos01.atlas.cogentco.com (154.54.85.217) 101.024 ms te3-2.ccr01.bos06.atlas.cogentco.com (154.54.46.130) 98.598 ms te3-4.ccr01.bos06.atlas.cogentco.com (154.54.46.134) 99.859 ms
17 38.111.40.114 (38.111.40.114) 106.802 ms * *
18 208.95.185.41 (208.95.185.41) 99.500 ms 38.111.40.114 (38.111.40.114) 102.011 ms *
You got a reply, hence my 'some packets do get through'.
Still convinced it's a load balancer.
Tracing route to launcher.startrekonline.com [208.95.185.44]
over a maximum of 30 hops:
1 11 ms 9 ms 9 ms
2 9 ms 9 ms 8 ms crr02wrcsma-tge-0-2-0- .wrcs.ma.charter.com [96.34.84.168]
3 13 ms 13 ms 14 ms crr03oxfrma-tge-0-3-0-5.oxfr.ma.charter.com [96.34.80.228]
4 9 ms 10 ms 11 ms bbr01oxfrma-bue-1.oxfr.ma.charter.com [96.34.2.12]
5 * * * Request timed out.
6 25 ms 32 ms 25 ms bbr02ashbva-bue-2.ashb.va.charter.com [96.34.0.48]
7 22 ms 21 ms 21 ms te0-7-0-17.mpd22.iad02.atlas.cogentco.com [38.122.62.21]
8 22 ms 23 ms 23 ms te0-3-0-1.mpd22.dca01.atlas.cogentco.com [154.54.30.117]
9 22 ms 23 ms 22 ms te0-3-0-6.mpd22.jfk02.atlas.cogentco.com [154.54.3.234]
10 28 ms 27 ms 27 ms te0-5-0-7.ccr21.bos01.atlas.cogentco.com [154.54.47.237]
11 31 ms 28 ms 29 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 * * * 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 * * * Request timed out.
Trace complete.
The downside is that even with a fully patched game, gameclient.exe will still try to connect to the patcher and the patcher server is the problem.
Also, when in game content is still downloaded. For example in Foundry.
There is no problem from users.
The problem has a name: Cryptic devs & Cogent communication.
The best team of incompetent people
This such IP doesn't respond. And what is this IP ? Cogent Communication !! http://whois.domaintools.com/38.111.40.114
My tracert
C:\Documents and Settings\Olivier>Tracert launcher.startrekonline.com
D?termination de l'itin?raire vers launcher.startrekonline.com [208.95.185.44]
avec un maximum de 30 sauts*:
1 22 ms 20 ms 20 ms 78.225.73.254
2 20 ms 20 ms 20 ms 78.225.73.254
3 21 ms 21 ms 22 ms 213.228.36.254
4 22 ms 23 ms 22 ms bzn-crs16-1-be1105.intf.routers.proxad.net [212.
27.56.197]
5 26 ms 23 ms 24 ms bzn-crs16-2-be1000.intf.routers.proxad.net [212.
27.59.102]
6 25 ms 24 ms 24 ms te0-1-0-4.377.mag21.par01.atlas.cogentco.com [14
9.6.115.25]
7 23 ms 23 ms 24 ms te0-0-0-10.ccr21.par01.atlas.cogentco.com [154.5
4.74.133]
8 32 ms 31 ms 30 ms te0-4-0-6.ccr21.lon13.atlas.cogentco.com [154.54
.37.177]
9 103 ms 103 ms 103 ms te0-7-0-33.ccr21.bos01.atlas.cogentco.com [154.5
4.5.161]
10 105 ms 107 ms 110 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
134]
11 * * 118 ms 38.111.40.114
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 * * * D?lai d'attente de la demande d?pass?.
28 * * * D?lai d'attente de la demande d?pass?.
29 * * * D?lai d'attente de la demande d?pass?.
30 * * * D?lai d'attente de la demande d?pass?.
Itin?raire d?termin?.
C:\Documents and Settings\Olivier>
I'd concur, it seems like it is load balancing through bad routes.
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Mike>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 192.168.1.1
2 12 ms 7 ms 10 ms 10.240.185.9
3 7 ms 13 ms 14 ms ool-4353df11.dyn.optonline.net [67.83.223.17]
4 11 ms 10 ms 12 ms rtr3-ge1-7.mhe.hcvlny.cv.net [167.206.34.1]
5 10 ms 15 ms 12 ms 451be0b1.cst.lightpath.net [65.19.99.177]
6 55 ms 81 ms 107 ms 451be085.cst.lightpath.net [65.19.120.133]
7 * * * Request timed out.
8 10 ms 11 ms 13 ms te0-1-0-0.mpd21.jfk02.atlas.cogentco.com [154.54
.44.69]
9 20 ms 16 ms 18 ms te0-3-0-5.ccr21.bos01.atlas.cogentco.com [154.54
.44.34]
10 22 ms 44 ms 69 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.25
4]
11 * 24 ms * 38.111.40.114
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 * * 102 ms 208.95.185.41
Trace complete.
Damn, that's downright insulting.
SOME players MAY be getting an ERROR upon launching it. MAYBE - a VERY MINOR ERROR, SOMETIMES.
Community team: you're full of bs.
Your "error" is utter nonfunction of the game due to a failure in your network.
Your "some players" number in the thousands.
And the people "maybe" getting this "error" certainly get it with astonishing frequency.
Do you think we don't know what tracert does?
He's dead, Jim.
Do yourself a favor and DON'T do this. This expatshield thing takes over your browser, inserts advertising and re-directs your home page. And browsing with it is slow, slow, slow. Save yourself the trouble.
The results are from Manchester United Kingdom using Sky Broadband ISP
Update: Launcher worked fine through my Mobile Phone's internet if this helps narrow the problem.
Yes, there is;
"Thanks you"? They can't even sort out their spelling and grammar.
Whoever broke this may not be a dev at all. The problem manifested before the downtime. It is also clearly something in the larger scheme of the internet. There is a bad device(s) somewhere malfunctioning, and it may not even be anything under Cryptic's purview.