Same problem, launcher won't update, yada yada, internet fine, connecting from New York City area, no point posting a trouceroute will show same as others, frustrating...
So... is it possible to avoid routing through 38.111.40.114 (Cogent Communications) and route through somewhere else? Seeing as Cogent is the issue and has been an issue several times over the past few years.
Yes, via mobile networks (which is why I think it could be a load balancing issue).
1 11 ms 23 ms 21 ms 10.95.52.1
2 13 ms 13 ms 15 ms haye-core-1a-ge22.network.virginmedia.net [80.3
176.233]
3 32 ms 8 ms 15 ms haye-core-2a-ae3-0.network.virginmedia.net [212
43.163.117]
4 21 ms 10 ms 18 ms brnt-bb-1c-ae9-0.network.virginmedia.net [62.25
.174.181]
5 9 ms 13 ms 13 ms popl-bb-1c-ae5-0.network.virginmedia.net [62.25
.174.133]
6 24 ms 16 ms 10 ms popl-bb-1a-ae7-0.network.virginmedia.net [213.1
5.159.185]
7 71 ms 14 ms 18 ms popl-tmr-1-ae4-0.network.virginmedia.net [213.1
5.159.2]
8 40 ms 22 ms 48 ms amst-ic-1-as0-0.network.virginmedia.net [213.10
.175.6]
9 21 ms 24 ms 20 ms te0-7-0-10.ccr21.ams04.atlas.cogentco.com [130.
17.15.5]
10 1622 ms 19 ms 23 ms te0-0-0-7.mpd21.ams03.atlas.cogentco.com [130.1
7.2.61]
11 28 ms 35 ms 24 ms te0-1-0-7.ccr22.lpl01.atlas.cogentco.com [154.5
.37.114]
12 95 ms 108 ms 106 ms te0-5-0-4.ccr21.bos01.atlas.cogentco.com [154.5
.85.213]
13 96 ms 119 ms 87 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.2
4]
14 * * * Request timed out.
15 * * * Request timed out.
16 * * 93 ms 208.95.185.41
Using posting guides, my values are within normal range and do not call for copy and paste. Have tested connection with other games and am experiencing no lag. Have Metrocast as an ISP. Problem is not with my machine or connection.
Find the new guy and torture him for what went wrong.
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.
still can not logon....is anyone at cryptic even working on this....they should at least post a message here or on the web page stating they are working on it...the support page does not load...u can not even send an email....come on cryptic get yor act together....
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 *
Comments
Yes, via mobile networks (which is why I think it could be a load balancing issue).
if i use my moblie to play will that send my moblie bill througth the roof?
contacting nettest server..
Local IP:
Ping: 90.9 msec
Port: 80: 505 KB/sec 16 KB/sec 531 KB/sec 500
Port: 80: 501 KB/sec 16 KB/sec 527 KB/sec 500
Port: 443: 497 KB/sec 14 KB/sec 523 KB/sec 500
Port: 443: 503 KB/sec 14 KB/sec 530 KB/sec 500
Port: 7255: 474 KB/sec 14 KB/sec 499 KB/sec 500
Port: 7255: 449 KB/sec 13 KB/sec 474 KB/sec 500
Port: 7003: 465 KB/sec 13 KB/sec 490 KB/sec 500
Port: 7003: 495 KB/sec 15 KB/sec 522 KB/sec 500
Port: 7202: 473 KB/sec 14 KB/sec 499 KB/sec 500
Port: 7202: 499 KB/sec 14 KB/sec 525 KB/sec 500
Port: 7499: 501 KB/sec 14 KB/sec 527 KB/sec 500
Port: 7499: 472 KB/sec 15 KB/sec 497 KB/sec 500
Port: 80: 499 KB/sec 16 KB/sec 524 KB/sec 500
Idle NIC bandwidth Send: 0 KB/sec Recv: 0 KB/sec
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
2 13 ms 10 ms 9 ms
3 8 ms 9 ms 11 ms croy-core-2b-ae7-719.network.virginmedia.net [81
.96.225.173]
4 19 ms 9 ms 8 ms popl-bb-1c-ae10-0.network.virginmedia.net [81.96
.226.5]
5 11 ms 8 ms 10 ms popl-bb-1a-ae7-0.network.virginmedia.net [213.10
5.159.185]
6 8 ms 11 ms 11 ms popl-tmr-1-ae4-0.network.virginmedia.net [213.10
5.159.2]
7 18 ms 15 ms 15 ms amst-ic-1-as0-0.network.virginmedia.net [213.105
.175.6]
8 16 ms 17 ms 17 ms te0-7-0-10.ccr21.ams04.atlas.cogentco.com [130.1
17.15.5]
9 17 ms 17 ms 19 ms te0-0-0-7.ccr21.ams03.atlas.cogentco.com [130.11
7.49.13]
10 20 ms 33 ms 22 ms te0-3-0-2.ccr21.lpl01.atlas.cogentco.com [154.54
.37.94]
11 87 ms 88 ms 87 ms te0-2-0-3.ccr21.bos01.atlas.cogentco.com [154.54
.31.189]
12 88 ms 86 ms 87 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42
]
13 * 117 ms * 38.111.40.114
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.
1 1 ms <1 ms <1 ms 192.168.0.1
2 26 ms 28 ms 25 ms b01a7afe.bb.sky.com [176.26.122.254]
3 * * * Request timed out.
4 34 ms 31 ms 32 ms ip-84-38-37-34.easynet.co.uk [84.38.37.34]
5 35 ms 31 ms 31 ms 027808fa.bb.sky.com [2.120.8.250]
6 30 ms 30 ms 28 ms ae-3.r02.londen03.uk.bb.gin.ntt.net [83.231.221.
45]
7 28 ms 56 ms 28 ms te2-4.ccr01.lon02.atlas.cogentco.com [130.117.14
.249]
8 28 ms 29 ms 29 ms te0-0-0-2.ccr22.lon01.atlas.cogentco.com [130.11
7.1.18]
9 29 ms 30 ms 29 ms te0-0-0-2.ccr22.lon01.atlas.cogentco.com [130.11
7.1.18]
10 29 ms 104 ms 105 ms te0-0-0-4.ccr22.bos01.atlas.cogentco.com [130.11
7.0.46]
11 109 ms 105 ms 105 ms te0-0-0-4.ccr22.bos01.atlas.cogentco.com [130.11
7.0.46]
12 105 ms 105 ms 105 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.
130]
13 113 ms * * playstartrekonline.eu [208.95.185.44]
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.
What is happening? and when will this be fixed?
2 13 ms 13 ms 15 ms haye-core-1a-ge22.network.virginmedia.net [80.3
176.233]
3 32 ms 8 ms 15 ms haye-core-2a-ae3-0.network.virginmedia.net [212
43.163.117]
4 21 ms 10 ms 18 ms brnt-bb-1c-ae9-0.network.virginmedia.net [62.25
.174.181]
5 9 ms 13 ms 13 ms popl-bb-1c-ae5-0.network.virginmedia.net [62.25
.174.133]
6 24 ms 16 ms 10 ms popl-bb-1a-ae7-0.network.virginmedia.net [213.1
5.159.185]
7 71 ms 14 ms 18 ms popl-tmr-1-ae4-0.network.virginmedia.net [213.1
5.159.2]
8 40 ms 22 ms 48 ms amst-ic-1-as0-0.network.virginmedia.net [213.10
.175.6]
9 21 ms 24 ms 20 ms te0-7-0-10.ccr21.ams04.atlas.cogentco.com [130.
17.15.5]
10 1622 ms 19 ms 23 ms te0-0-0-7.mpd21.ams03.atlas.cogentco.com [130.1
7.2.61]
11 28 ms 35 ms 24 ms te0-1-0-7.ccr22.lpl01.atlas.cogentco.com [154.5
.37.114]
12 95 ms 108 ms 106 ms te0-5-0-4.ccr21.bos01.atlas.cogentco.com [154.5
.85.213]
13 96 ms 119 ms 87 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.2
4]
14 * * * Request timed out.
15 * * * Request timed out.
16 * * 93 ms 208.95.185.41
Trace complete.
>Join Date: Jan 2013
wat
Find the new guy and torture him for what went wrong.
why the hell should we pay for mobile connection when we paid already for the game.
:mad: :mad: :mad: :mad:
Yes, however, just turn off your mobile, it should return you to the game login screen, just re-login and it should work.
After you turn on your normal network...
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.
Don't be silly, they cannot afford Me, they're Pentium 1's with a 50mhz clock on Win 3.1 :-p
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 *