Wow.. big drop with the first 7499 Port... I got a Badda-ding Ping... :eek:
STO Member since February 2009. I Was A Trekkie Before It Was Cool ... Sept. 8th, 1966 ... Not To Mention Before Most Folks Around Here Were Born! Forever a STO Veteran-Minion
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 10.0.0.1
2 1 ms <1 ms <1 ms 192.168.1.254
3 9 ms 8 ms 8 ms adsl-65-9-8-1.mia.bellsouth.net [65.9.8.1]
4 22 ms 10 ms 10 ms 70.159.200.221
5 11 ms 11 ms 10 ms 70.159.202.20
6 13 ms 10 ms 14 ms 12.81.20.54
7 12 ms 14 ms 11 ms 12.81.104.2
8 11 ms 9 ms 9 ms 12.81.8.67
9 16 ms 15 ms 15 ms 74.175.192.166
10 26 ms 26 ms 26 ms cr81.fldfl.ip.att.net [12.122.106.94]
11 29 ms 26 ms 26 ms cr2.ormfl.ip.att.net [12.122.1.45]
12 29 ms 31 ms 29 ms cr1.attga.ip.att.net [12.122.5.142]
13 28 ms 30 ms 26 ms gar3.brhal.ip.att.net [12.122.141.189]
14 26 ms 26 ms 26 ms te2-5.ccr01.atl02.atlas.cogentco.com [154.54.10.
69]
15 27 ms 26 ms 26 ms te0-4-0-7.mpd21.atl01.atlas.cogentco.com [154.54
.88.209]
16 37 ms 37 ms 37 ms te0-3-0-2.mpd21.dca01.atlas.cogentco.com [154.54
.28.17]
17 44 ms 44 ms 44 ms te0-7-0-20.mpd21.jfk02.atlas.cogentco.com [154.5
4.1.106]
18 50 ms 49 ms 50 ms te0-6-0-0.ccr21.bos01.atlas.cogentco.com [154.54
.0.29]
19 50 ms 49 ms 50 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
134]
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.
The internet or world wide web, is made up of many computers all linking together, when connecting to a pc on the other side of the world, or even next door, you do not make a direct connection. The signal gets sent to a server, who sends it to another server and so on, this is called Routing. What Cryptic have asked us to do, is trace that routing, and show them where the problem is. Without this information they cannot diagnose and fix the problem.
Feel free to Say no to posting the info, but the more info the quicker the problem can be diagnosed and therefore resolved.
SCM - Infected(S) - DMG Out: 11,776,567 DPS: 114,224.70 (28.7% of Team) - Pinky@ukcaptain420 I reserve the right to have a completely different standpoint depending on my mood.
so im not the only one unable to access the servers in any way, well strangely that makes me feel slightly better but not to much better , geuss instead of playing i might as well do some ...ugh work
If this problem keeps persisiting i may just log into battlestar galactica online out of boredom and frusteration.
God even the thought of playing that dreadfull game again makes my stomach turn in knots but atleast id be able to play it.
Tracing route to de.playstartrekonline.eu [208.95.185.44]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 5 ms 7 ms 6 ms L100.PHLAPA-VFTTP-146.verizon-gni.net [108.2.125
.1]
3 8 ms 7 ms 7 ms G0-6-4-7.PHLAPA-LCR-21.verizon-gni.net [130.81.1
77.250]
4 7 ms 7 ms 7 ms 130.81.199.18
5 10 ms 10 ms 10 ms xe-3-1-0-0.NWRK-BB-RTR1.verizon-gni.net [130.81.
23.223]
6 10 ms 16 ms 11 ms 0.xe-7-2-0.XL3.NYC1.ALTER.NET [152.63.6.145]
7 21 ms 20 ms 21 ms 0.ge-4-0-0.XL3.BOS4.ALTER.NET [152.63.17.30]
8 21 ms 21 ms 20 ms POS6-0.GW5.BOS4.ALTER.NET [152.63.25.69]
9 26 ms 25 ms 24 ms internap-gw.customer.alter.net [65.207.236.58]
10 26 ms 23 ms 24 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.4
1]
11 30 ms 36 ms 35 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
12 * * * Request timed out.
This is a Cogent network issue, nothing to do with the patch, it's not YOUR connection either, it's that you are sending network traffic, and cogent are dropping it (what would appear to be at one of their routers). Occasionally *Some* data does get through, but 95% it's dropped.
Mine appears to be after it reaches Perfect World. Relevant part in RED.
Tracing route to launcher.startrekonline.com [208.95.185.44]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 8 ms 6 ms 8 ms L100.LSANCA-VFTTP-148.verizon-gni.net [173.60.130.1]
3 11 ms 12 ms 12 ms G0-5-2-3.LSANCA-LCR-22.verizon-gni.net [130.81.55.110]
4 8 ms 10 ms 9 ms ae0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.22.246]
5 16 ms 14 ms 14 ms 0.xe-6-1-1.XL3.LAX15.ALTER.NET [152.63.5.233]
6 98 ms 96 ms 97 ms 0.ge-4-3-0.XL3.BOS4.ALTER.NET [152.63.16.34]
7 97 ms 98 ms 96 ms POS6-0.GW5.BOS4.ALTER.NET [152.63.25.69]
8 98 ms 99 ms 99 ms internap-gw.customer.alter.net [65.207.236.58]
9 98 ms 99 ms 99 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.104] 10 99 ms * 105 ms perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * 100 ms 208.95.185.44
Routenverfolgung zu launcher.startrekonline.com [208.95.185.44] ?ber maximal 30
Abschnitte:
1 <1 ms 1 ms <1 ms fritz.box [192.168.1.254]
2 35 ms 35 ms 35 ms rdsl-osbk-de01.nw.mediaways.net [213.20.59.4]
3 35 ms 35 ms 49 ms xmws-osbk-de03-chan-18.nw.mediaways.net [195.71.
224.146]
4 44 ms 50 ms 90 ms rmwc-frnk-de01-xe-4-0-6-0.nw.mediaways.net [195.
71.254.77]
5 47 ms 93 ms 47 ms 176.52.173.177
6 64 ms 64 ms 81 ms 84.16.13.234
7 58 ms 58 ms 57 ms 195.50.118.201
8 59 ms 60 ms 61 ms ae-51-51.csw1.London1.Level3.net [4.69.139.88]
9 58 ms 58 ms 59 ms ae-116-3502.edge3.London1.Level3.net [4.69.166.1
34]
10 * 70 ms 71 ms te0-7-0-1.ccr21.lon01.atlas.cogentco.com [130.11
7.15.241]
11 77 ms 77 ms 74 ms te0-2-0-4.mpd21.lon13.atlas.cogentco.com [154.54
.57.94]
12 143 ms 142 ms 142 ms te0-7-0-27.ccr21.bos01.atlas.cogentco.com [154.5
4.1.93]
13 141 ms 141 ms 142 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
134]
14 151 ms * 158 ms 38.111.40.114
15 * * * Zeit?berschreitung der Anforderung.
16 * * * Zeit?berschreitung der Anforderung.
17 * 138 ms * www.playstartrek.fr [208.95.185.44]
18 * * * Zeit?berschreitung der Anforderung.
19 * * 138 ms www.playstartrek.fr [208.95.185.44]
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms *******************************
2 5 ms 5 ms 5 ms 217.32.141.134
3 5 ms 5 ms 5 ms 217.32.141.190
4 10 ms 9 ms 9 ms 213.120.161.74
5 10 ms 9 ms 9 ms 31.55.164.247
6 9 ms 9 ms 9 ms 31.55.164.109
7 10 ms 9 ms 9 ms acc2-10GigE-0-5-0-6.bm.21cn-ipp.bt.net [109.159.
248.228]
8 18 ms 15 ms 15 ms core1-te0-3-0-16.ilford.ukcore.bt.net [109.159.2
48.156]
9 14 ms 14 ms 14 ms core1-pos9-1.telehouse.ukcore.bt.net [194.74.65.
114]
10 14 ms 14 ms 13 ms t2as1-tge1-4.uk-lon1.eu.bt.net [166.49.211.141]
11 13 ms 13 ms 13 ms t2a1-ge7-0-0.uk-lon1.eu.bt.net [166.49.135.49]
12 14 ms 13 ms 13 ms te0-7-0-3.ccr21.lon01.atlas.cogentco.com [130.11
7.14.49]
13 16 ms 15 ms 15 ms te0-0-0-4.mpd21.lon13.atlas.cogentco.com [154.54
.57.102]
14 100 ms 87 ms 87 ms te0-2-0-4.ccr21.bos01.atlas.cogentco.com [66.28.
4.189]
15 87 ms 91 ms 94 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42
]
16 * 92 ms * 38.111.40.114
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 87 ms * * 208.95.185.41
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.
Looks like a DNS/domain registration? Goes thru the UK points but once it hops out of the UK that's where it gets odd.
I don't mean to be rude.. But I find it funny that whenever I look at any MMO tech support forum.. It's always the same thing. Different problems, same reaction.. people seething with rage at how tech support is doing nothing and how they can't believe that there would ever be an error and how dare there be any kind of problem keeping them from playing (either the mmo's fault or not).. Shtuff happens Ladies and Gents.. Look at almost any other MMO forum.. You get about the same amount of response from tech support. They are working hard on our problems. Give them any info they ask.. and remember it is a game.. yes you may pay a monthly subscription to play this game.. but it's a game.. Go do something else for a few hrs and check back.. Or if you have to go to work soon.. just go do something else before work instead of staring at the forums and going to work grumpy.. Again.. hope I'm not offending anyone.. Just an observation. Don't worry y'all be happy lol
its a strange one. Simple fix for those with a mobile connection... I created a wifi hotspot on my phone and got the update and launched the game fine, then switched back to dsl and all is dandy.
Hope it helps.
Not quite, but good idea
Switch to Hotspot, Launcher loads, patches, game runs.
Switch to DSL, InGame Login appears, Game continues to run.
Quit game, (still on DSL), Launcher goes back to not running.
Router has been reset. Tracerts are pretty much the same as everyone elses.
(Except one where I was passing through France!)
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms ***.***.*.*
2 * * * Request timed out.
3 11 ms 11 ms 10 ms 67.59.227.53
4 17 ms 11 ms 9 ms opti34-137.nassau.cv.net [167.206.34.137]
5 20 ms 10 ms 15 ms 64.15.5.254
6 12 ms 12 ms 14 ms 451be085.cst.lightpath.net [65.19.120.133]
7 * * * Request timed out.
8 11 ms 14 ms 13 ms te0-3-0-2.mpd22.jfk02.atlas.cogentco.com [154.54
.44.73]
9 18 ms 19 ms 18 ms te0-0-0-1.ccr22.bos01.atlas.cogentco.com [154.54
.25.114]
10 148 ms 217 ms 221 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.25
4]
11 29 ms * * 38.111.40.114
12 * * 38 ms 208.95.185.41
Tracing route to launcher.startrekonline.com [208.95.185.44]
over a maximum of 30 hops:
5 61 ms 76 ms 59 ms agg21.klaohias-ccr01.hawaii.rr.com [72.129.45.48
]
6 65 ms 67 ms 66 ms agg21.kmlahi07-ccr01.hawaii.rr.com [72.129.45.50
]
7 81 ms 71 ms 71 ms agg31.tustcaft-ccr01.socal.rr.com [72.129.45.2]
8 70 ms 71 ms 71 ms ae-5-0.cr0.lax30.tbone.rr.com [66.109.6.64]
9 66 ms 66 ms 67 ms 66.109.9.26
10 65 ms 63 ms 63 ms te0-0-0-19.ccr21.lax05.atlas.cogentco.com [154.5
4.10.249]
11 111 ms 64 ms 65 ms te0-0-0-2.mpd21.lax01.atlas.cogentco.com [154.54
.30.189]
12 102 ms 104 ms 105 ms te0-2-0-3.mpd21.iah01.atlas.cogentco.com [154.54
.44.249]
13 125 ms 130 ms 127 ms te0-0-0-2.ccr21.atl01.atlas.cogentco.com [154.54
.24.17]
14 134 ms 134 ms 133 ms te0-0-0-3.ccr21.dca01.atlas.cogentco.com [154.54
.28.201]
15 135 ms 137 ms 137 ms te0-7-0-20.mpd21.jfk02.atlas.cogentco.com [154.5
4.1.106]
16 140 ms 140 ms 156 ms te0-1-0-4.ccr21.bos01.atlas.cogentco.com [154.54
.6.1]
17 142 ms 140 ms 143 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.
130]
18 143 ms 139 ms 146 ms 38.111.40.114
19 139 ms 139 ms * fr.playstartrekonline.eu [208.95.185.44]
20 * * * Request timed out.
21 * * * Request timed out.
22 142 ms 151 ms * fr.playstartrekonline.eu [208.95.185.44]
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 142 ms * * fr.playstartrekonline.eu [208.95.185.44]
27 * * * Request timed out.
28 * * 140 ms fr.playstartrekonline.eu [208.95.185.44]
Trace complete.
There certainly seems something odd at the end looping back to fr.playstartrekonline.eu multiple times.
It might be one of their outbound switches that got fried - and this might not show up in diagnostics easily since it's the last leg within their network.
It would be nice if the community manager would at least update us here as too what they think it is, what they are doing about it, and an estimate about how long this is going to take.... The silence from Cryptic is really frustrating.
I do not have time for this, especially with the lack of communication from the STO team.
I am sure he will. Just as soon as he knows something. I mean its that or should be post every 5 minutes nothing new yet?
I don't mean to be rude.. But I find it funny that whenever I look at any MMO tech support forum.. It's always the same thing. Different problems, same reaction.. people seething with rage at how tech support is doing nothing and how they can't believe that there would ever be an error and how dare there be any kind of problem keeping them from playing (either the mmo's fault or not).. Shtuff happens Ladies and Gents.. Look at almost any other MMO forum.. You get about the same amount of response from tech support. They are working hard on our problems. Give them any info they ask.. and remember it is a game.. yes you may pay a monthly subscription to play this game.. but it's a game.. Go do something else for a few hrs and check back.. Or if you have to go to work soon.. just go do something else before work instead of staring at the forums and going to work grumpy.. Again.. hope I'm not offending anyone.. Just an observation. Don't worry y'all be happy lol
I'm fine with there being technical problems. What is pissing me off so much is someone is employed as the community manager and that person is NOT communicating with us. We have not been told what they think it is, weather or not they have a clue yet, or what they are doing, or when they expect to have a solution.... in fact, there has been 0 communication.
Communication isn't a whole lot to ask and it would do wonders at cooling the "seething rage" that happens when problems arise.
Tracing route to launcher.startrekonline.com [208.95.185.44]
over a maximum of 30 hops:
1 2 ms <1 ms <1 ms BTHomeHub.home [192.168.1.254]
2 4 ms 8 ms 11 ms 217.32.143.35
3 6 ms 5 ms 5 ms 217.32.143.62
4 6 ms 6 ms 6 ms 213.120.163.74
5 7 ms 6 ms 6 ms 31.55.165.241
6 7 ms 6 ms 6 ms 31.55.165.109
7 6 ms 6 ms 5 ms acc1-10GigE-1-3-0.mr.21cn-ipp.bt.net [109.159.25
0.214]
8 14 ms 15 ms 22 ms core1-te0-13-0-13.ilford.ukcore.bt.net [109.159.
250.172]
9 13 ms 13 ms 12 ms core1-pos9-1.telehouse.ukcore.bt.net [194.74.65.
114]
10 14 ms 13 ms 15 ms t2as1-tge4-4.uk-lon1.eu.bt.net [166.49.211.145]
11 13 ms 13 ms 13 ms t2a1-ge4-0-0.uk-lon1.eu.bt.net [166.49.135.17]
12 15 ms 16 ms 15 ms te0-7-0-3.ccr21.lon01.atlas.cogentco.com [130.11
7.14.49]
13 15 ms 14 ms 15 ms te0-1-0-4.ccr21.lon13.atlas.cogentco.com [154.54
.57.106]
14 87 ms 89 ms 89 ms te0-7-0-33.ccr21.bos01.atlas.cogentco.com [154.5
4.5.161]
15 141 ms 219 ms 250 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42
]
16 96 ms 95 ms 91 ms 38.111.40.114
17 * * * Request timed out.
18 88 ms * * playstartrek.fr [208.95.185.44]
19 * * 89 ms playstartrek.fr [208.95.185.44]
Trace complete.
Commanding Officer the 10th Fleet
the user formally known as kiss.my.rear.admiral
I'm in Dallas TX, and when I attempt to open my launcher, I either get:
1) A small box saying "trying to update the launcher", which times out after 3 attempts, or
2) It opens the launcher but stalls at a white box saying "Loading. Please wait."
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 5 ms 4 ms 4 ms L100.DLLSTX-VFTTP-24.verizon-gni.net [71.123.203.1]
3 6 ms 7 ms 7 ms G0-3-0-4.DLLSTX-LCR-22.verizon-gni.net [130.81.59.174]
4 8 ms 7 ms 7 ms so-5-0-0-0.DFW9-BB-RTR2.verizon-gni.net [130.81.199.36]
5 42 ms 19 ms 7 ms 0.xe-0-0-0.XT4.DFW9.ALTER.NET [152.63.96.197]
6 63 ms 64 ms 64 ms 0.so-7-1-0.XL4.BOS4.ALTER.NET [152.63.0.221]
7 61 ms 62 ms 62 ms POS7-0.GW5.BOS4.ALTER.NET [152.63.25.57]
8 60 ms 59 ms 59 ms internap-gw.customer.alter.net [65.207.236.58]
9 60 ms 74 ms 79 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.104]
10 58 ms 67 ms 72 ms perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
11 * * * Request timed out.
12 * 58 ms * 208.95.185.41
13 * * * Request timed out.
14 * * * Request timed out.
15 * 58 ms * 208.95.185.41
16 * * * Request timed out.
17 60 ms * * 208.95.185.41
18 * * 60 ms 208.95.185.41
Trace complete.
It appears that the problem is that your server at 208.95.185.41 is failing to respond.
I'm fine with there being technical problems. What is pissing me off so much is someone is employed as the community manager and that person is NOT communicating with us. We have not been told what they think it is, weather or not they have a clue yet, or what they are doing, or when they expect to have a solution.... in fact, there has been 0 communication.
Communication isn't a whole lot to ask and it would do wonders at cooling the "seething rage" that happens when problems arise.
He could at least post every 15 min. or so what they have done the last 15 min.... even a "We are still working on tracking down the problem, your patience is appreaciated. We hope to have this resolved within the hour/4hours..." would be nice.... Just something.
Comments
My Launcher comes up, but never connects or gives a time out warning.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\David>tracert patchserver.crypticstudios.com
Tracing route to patchserver.crypticstudios.com over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms ***.***.**.*.
2 39 ms 27 ms 31 ms cable-mac1.schnny52-ar4003.nyroc.rr.com [67.242.192.1]
3 10 ms 10 ms 12 ms gig8-45.schnny52-rtr001.alb.northeast.rr.com [24.29.46.197]
4 11 ms 12 ms 12 ms rdc-74-76-241-78.alb.northeast.rr.com [74.76.241.78]
5 22 ms 23 ms 23 ms rdc-74-76-241-193.alb.northeast.rr.com [74.76.241.193]
6 28 ms 24 ms 23 ms ae-5-0.cr0.nyc30.tbone.rr.com [66.109.6.74]
7 19 ms 22 ms 21 ms 107.14.19.147
8 19 ms 22 ms 22 ms te0-0-0-5.ccr21.jfk05.atlas.cogentco.com [154.54.13.185]
9 22 ms 21 ms 22 ms te0-1-0-5.mpd21.jfk02.atlas.cogentco.com [154.54.3.97]
10 27 ms 28 ms 27 ms te0-1-0-4.ccr21.bos01.atlas.cogentco.com [154.54.6.1]
11 199 ms 332 ms 211 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.134]
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.
This is a first for me.. never had this happen in 3 years of playing the game.
My nettest results...
contacting nettest server..
Local IP: **.***.***.**
Ping: 25.9 msec
Port: 80: 1475 KB/sec 49 KB/sec 1560 KB/sec 500
Port: 80: 2072 KB/sec 68 KB/sec 2199 KB/sec 500
Port: 443: 1994 KB/sec 66 KB/sec 2116 KB/sec 500
Port: 443: 2117 KB/sec 65 KB/sec 2245 KB/sec 500
Port: 7255: 2012 KB/sec 60 KB/sec 2132 KB/sec 500
Port: 7255: 2099 KB/sec 64 KB/sec 2226 KB/sec 500
Port: 7003: 2022 KB/sec 66 KB/sec 2144 KB/sec 500
Port: 7003: 1957 KB/sec 60 KB/sec 2074 KB/sec 500
Port: 7202: 1978 KB/sec 59 KB/sec 2097 KB/sec 500
Port: 7202: 1970 KB/sec 66 KB/sec 2089 KB/sec 500
Port: 7499: 272 KB/sec 8 KB/sec 286 KB/sec 500
Port: 7499: 1526 KB/sec 46 KB/sec 1614 KB/sec 500
Port: 80: 1921 KB/sec 58 KB/sec 2036 KB/sec 500
Idle NIC bandwidth Send: 0 KB/sec Recv: 0 KB/sec
Wow.. big drop with the first 7499 Port... I got a Badda-ding Ping... :eek:
I Was A Trekkie Before It Was Cool ... Sept. 8th, 1966 ... Not To Mention Before Most Folks Around Here Were Born!
Forever a STO Veteran-Minion
Tracert Results
nettest results
Think about this:
American Football has been in open beta for 144 years. ~Kotaku
The internet or world wide web, is made up of many computers all linking together, when connecting to a pc on the other side of the world, or even next door, you do not make a direct connection. The signal gets sent to a server, who sends it to another server and so on, this is called Routing. What Cryptic have asked us to do, is trace that routing, and show them where the problem is. Without this information they cannot diagnose and fix the problem.
Feel free to Say no to posting the info, but the more info the quicker the problem can be diagnosed and therefore resolved.
I reserve the right to have a completely different standpoint depending on my mood.
If this problem keeps persisiting i may just log into battlestar galactica online out of boredom and frusteration.
God even the thought of playing that dreadfull game again makes my stomach turn in knots but atleast id be able to play it.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
HEY **** HEADS U SEE THIS?!
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 5 ms 7 ms 6 ms L100.PHLAPA-VFTTP-146.verizon-gni.net [108.2.125
.1]
3 8 ms 7 ms 7 ms G0-6-4-7.PHLAPA-LCR-21.verizon-gni.net [130.81.1
77.250]
4 7 ms 7 ms 7 ms 130.81.199.18
5 10 ms 10 ms 10 ms xe-3-1-0-0.NWRK-BB-RTR1.verizon-gni.net [130.81.
23.223]
6 10 ms 16 ms 11 ms 0.xe-7-2-0.XL3.NYC1.ALTER.NET [152.63.6.145]
7 21 ms 20 ms 21 ms 0.ge-4-0-0.XL3.BOS4.ALTER.NET [152.63.17.30]
8 21 ms 21 ms 20 ms POS6-0.GW5.BOS4.ALTER.NET [152.63.25.69]
9 26 ms 25 ms 24 ms internap-gw.customer.alter.net [65.207.236.58]
10 26 ms 23 ms 24 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.4
1]
11 30 ms 36 ms 35 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
12 * * * Request timed out.
Abschnitte:
1 <1 ms 1 ms <1 ms fritz.box [192.168.1.254]
2 35 ms 35 ms 35 ms rdsl-osbk-de01.nw.mediaways.net [213.20.59.4]
3 35 ms 35 ms 49 ms xmws-osbk-de03-chan-18.nw.mediaways.net [195.71.
224.146]
4 44 ms 50 ms 90 ms rmwc-frnk-de01-xe-4-0-6-0.nw.mediaways.net [195.
71.254.77]
5 47 ms 93 ms 47 ms 176.52.173.177
6 64 ms 64 ms 81 ms 84.16.13.234
7 58 ms 58 ms 57 ms 195.50.118.201
8 59 ms 60 ms 61 ms ae-51-51.csw1.London1.Level3.net [4.69.139.88]
9 58 ms 58 ms 59 ms ae-116-3502.edge3.London1.Level3.net [4.69.166.1
34]
10 * 70 ms 71 ms te0-7-0-1.ccr21.lon01.atlas.cogentco.com [130.11
7.15.241]
11 77 ms 77 ms 74 ms te0-2-0-4.mpd21.lon13.atlas.cogentco.com [154.54
.57.94]
12 143 ms 142 ms 142 ms te0-7-0-27.ccr21.bos01.atlas.cogentco.com [154.5
4.1.93]
13 141 ms 141 ms 142 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
134]
14 151 ms * 158 ms 38.111.40.114
15 * * * Zeit?berschreitung der Anforderung.
16 * * * Zeit?berschreitung der Anforderung.
17 * 138 ms * www.playstartrek.fr [208.95.185.44]
18 * * * Zeit?berschreitung der Anforderung.
19 * * 138 ms www.playstartrek.fr [208.95.185.44]
Ablaufverfolgung beendet.
C:\Users\************>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 5 ms 5 ms 5 ms 217.32.141.134
3 5 ms 5 ms 5 ms 217.32.141.190
4 10 ms 9 ms 9 ms 213.120.161.74
5 10 ms 9 ms 9 ms 31.55.164.247
6 9 ms 9 ms 9 ms 31.55.164.109
7 10 ms 9 ms 9 ms acc2-10GigE-0-5-0-6.bm.21cn-ipp.bt.net [109.159.
248.228]
8 18 ms 15 ms 15 ms core1-te0-3-0-16.ilford.ukcore.bt.net [109.159.2
48.156]
9 14 ms 14 ms 14 ms core1-pos9-1.telehouse.ukcore.bt.net [194.74.65.
114]
10 14 ms 14 ms 13 ms t2as1-tge1-4.uk-lon1.eu.bt.net [166.49.211.141]
11 13 ms 13 ms 13 ms t2a1-ge7-0-0.uk-lon1.eu.bt.net [166.49.135.49]
12 14 ms 13 ms 13 ms te0-7-0-3.ccr21.lon01.atlas.cogentco.com [130.11
7.14.49]
13 16 ms 15 ms 15 ms te0-0-0-4.mpd21.lon13.atlas.cogentco.com [154.54
.57.102]
14 100 ms 87 ms 87 ms te0-2-0-4.ccr21.bos01.atlas.cogentco.com [66.28.
4.189]
15 87 ms 91 ms 94 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42
]
16 * 92 ms * 38.111.40.114
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 87 ms * * 208.95.185.41
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.
Looks like a DNS/domain registration? Goes thru the UK points but once it hops out of the UK that's where it gets odd.
Hope that helps.
Cheers
Rich
Not quite, but good idea
Switch to Hotspot, Launcher loads, patches, game runs.
Switch to DSL, InGame Login appears, Game continues to run.
Quit game, (still on DSL), Launcher goes back to not running.
Router has been reset. Tracerts are pretty much the same as everyone elses.
(Except one where I was passing through France!)
Im in the UK.
come on
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms ***.***.*.*
2 * * * Request timed out.
3 11 ms 11 ms 10 ms 67.59.227.53
4 17 ms 11 ms 9 ms opti34-137.nassau.cv.net [167.206.34.137]
5 20 ms 10 ms 15 ms 64.15.5.254
6 12 ms 12 ms 14 ms 451be085.cst.lightpath.net [65.19.120.133]
7 * * * Request timed out.
8 11 ms 14 ms 13 ms te0-3-0-2.mpd22.jfk02.atlas.cogentco.com [154.54
.44.73]
9 18 ms 19 ms 18 ms te0-0-0-1.ccr22.bos01.atlas.cogentco.com [154.54
.25.114]
10 148 ms 217 ms 221 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.25
4]
11 29 ms * * 38.111.40.114
12 * * 38 ms 208.95.185.41
Trace complete.
C:\Windows\system32>
Tracing route to launcher.startrekonline.com [208.95.185.44]
over a maximum of 30 hops:
5 61 ms 76 ms 59 ms agg21.klaohias-ccr01.hawaii.rr.com [72.129.45.48
]
6 65 ms 67 ms 66 ms agg21.kmlahi07-ccr01.hawaii.rr.com [72.129.45.50
]
7 81 ms 71 ms 71 ms agg31.tustcaft-ccr01.socal.rr.com [72.129.45.2]
8 70 ms 71 ms 71 ms ae-5-0.cr0.lax30.tbone.rr.com [66.109.6.64]
9 66 ms 66 ms 67 ms 66.109.9.26
10 65 ms 63 ms 63 ms te0-0-0-19.ccr21.lax05.atlas.cogentco.com [154.5
4.10.249]
11 111 ms 64 ms 65 ms te0-0-0-2.mpd21.lax01.atlas.cogentco.com [154.54
.30.189]
12 102 ms 104 ms 105 ms te0-2-0-3.mpd21.iah01.atlas.cogentco.com [154.54
.44.249]
13 125 ms 130 ms 127 ms te0-0-0-2.ccr21.atl01.atlas.cogentco.com [154.54
.24.17]
14 134 ms 134 ms 133 ms te0-0-0-3.ccr21.dca01.atlas.cogentco.com [154.54
.28.201]
15 135 ms 137 ms 137 ms te0-7-0-20.mpd21.jfk02.atlas.cogentco.com [154.5
4.1.106]
16 140 ms 140 ms 156 ms te0-1-0-4.ccr21.bos01.atlas.cogentco.com [154.54
.6.1]
17 142 ms 140 ms 143 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.
130]
18 143 ms 139 ms 146 ms 38.111.40.114
19 139 ms 139 ms * fr.playstartrekonline.eu [208.95.185.44]
20 * * * Request timed out.
21 * * * Request timed out.
22 142 ms 151 ms * fr.playstartrekonline.eu [208.95.185.44]
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 142 ms * * fr.playstartrekonline.eu [208.95.185.44]
27 * * * Request timed out.
28 * * 140 ms fr.playstartrekonline.eu [208.95.185.44]
Trace complete.
There certainly seems something odd at the end looping back to fr.playstartrekonline.eu multiple times.
He's dead, Jim.
I dont get that i get
ssvagent.exe is requesting to make changes to your machine
and it keeps wanting to download oracle to my laptop which as ive mentioned already has oracle.
I am sure he will. Just as soon as he knows something. I mean its that or should be post every 5 minutes nothing new yet?
I'm fine with there being technical problems. What is pissing me off so much is someone is employed as the community manager and that person is NOT communicating with us. We have not been told what they think it is, weather or not they have a clue yet, or what they are doing, or when they expect to have a solution.... in fact, there has been 0 communication.
Communication isn't a whole lot to ask and it would do wonders at cooling the "seething rage" that happens when problems arise.
When will you invest into decent servers at all : tired of getting random disconnections every now and then.
over a maximum of 30 hops:
1 2 ms <1 ms <1 ms BTHomeHub.home [192.168.1.254]
2 4 ms 8 ms 11 ms 217.32.143.35
3 6 ms 5 ms 5 ms 217.32.143.62
4 6 ms 6 ms 6 ms 213.120.163.74
5 7 ms 6 ms 6 ms 31.55.165.241
6 7 ms 6 ms 6 ms 31.55.165.109
7 6 ms 6 ms 5 ms acc1-10GigE-1-3-0.mr.21cn-ipp.bt.net [109.159.25
0.214]
8 14 ms 15 ms 22 ms core1-te0-13-0-13.ilford.ukcore.bt.net [109.159.
250.172]
9 13 ms 13 ms 12 ms core1-pos9-1.telehouse.ukcore.bt.net [194.74.65.
114]
10 14 ms 13 ms 15 ms t2as1-tge4-4.uk-lon1.eu.bt.net [166.49.211.145]
11 13 ms 13 ms 13 ms t2a1-ge4-0-0.uk-lon1.eu.bt.net [166.49.135.17]
12 15 ms 16 ms 15 ms te0-7-0-3.ccr21.lon01.atlas.cogentco.com [130.11
7.14.49]
13 15 ms 14 ms 15 ms te0-1-0-4.ccr21.lon13.atlas.cogentco.com [154.54
.57.106]
14 87 ms 89 ms 89 ms te0-7-0-33.ccr21.bos01.atlas.cogentco.com [154.5
4.5.161]
15 141 ms 219 ms 250 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42
]
16 96 ms 95 ms 91 ms 38.111.40.114
17 * * * Request timed out.
18 88 ms * * playstartrek.fr [208.95.185.44]
19 * * 89 ms playstartrek.fr [208.95.185.44]
Trace complete.
the user formally known as kiss.my.rear.admiral
1) A small box saying "trying to update the launcher", which times out after 3 attempts, or
2) It opens the launcher but stalls at a white box saying "Loading. Please wait."
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 5 ms 4 ms 4 ms L100.DLLSTX-VFTTP-24.verizon-gni.net [71.123.203.1]
3 6 ms 7 ms 7 ms G0-3-0-4.DLLSTX-LCR-22.verizon-gni.net [130.81.59.174]
4 8 ms 7 ms 7 ms so-5-0-0-0.DFW9-BB-RTR2.verizon-gni.net [130.81.199.36]
5 42 ms 19 ms 7 ms 0.xe-0-0-0.XT4.DFW9.ALTER.NET [152.63.96.197]
6 63 ms 64 ms 64 ms 0.so-7-1-0.XL4.BOS4.ALTER.NET [152.63.0.221]
7 61 ms 62 ms 62 ms POS7-0.GW5.BOS4.ALTER.NET [152.63.25.57]
8 60 ms 59 ms 59 ms internap-gw.customer.alter.net [65.207.236.58]
9 60 ms 74 ms 79 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.104]
10 58 ms 67 ms 72 ms perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
11 * * * Request timed out.
12 * 58 ms * 208.95.185.41
13 * * * Request timed out.
14 * * * Request timed out.
15 * 58 ms * 208.95.185.41
16 * * * Request timed out.
17 60 ms * * 208.95.185.41
18 * * 60 ms 208.95.185.41
Trace complete.
It appears that the problem is that your server at 208.95.185.41 is failing to respond.
The team is continuing to investigate. There are tons of players in-game, and tons more loading in, so it's not affecting everyone.
Cheers,
Brandon =/\=
He could at least post every 15 min. or so what they have done the last 15 min.... even a "We are still working on tracking down the problem, your patience is appreaciated. We hope to have this resolved within the hour/4hours..." would be nice.... Just something.