Career Officer
Join Date: Jun 2012
Posts: 57
# 1381
01-28-2013, 11:12 AM
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 *
Lieutenant
Join Date: Dec 2012
Posts: 34
# 1382
01-28-2013, 11:13 AM
Quote:
Originally Posted by johocrol View Post
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/sh...&postcount=490

You got a reply, hence my 'some packets do get through'.

Still convinced it's a load balancer.
Career Officer
Join Date: Jul 2012
Posts: 73
# 1383
01-28-2013, 11:13 AM
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.
Starfleet Veteran
Join Date: Oct 2012
Posts: 32
# 1384
01-28-2013, 11:14 AM
Quote:
Originally Posted by daskippa View Post
Is the PWE staff to incompetant to build in a manual patch option for the cases where the real world bites em on the @$$ ? 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.
Empire Veteran
Join Date: Jun 2012
Posts: 228
# 1385
01-28-2013, 11:14 AM
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?.

Itin?raire d?termin?.

C:\Documents and Settings\Olivier>
http://i.imgur.com/RVocq.jpg
Lt. Commander
Join Date: Nov 2012
Posts: 119
# 1386
01-28-2013, 11:14 AM
Glad it's their top priority but really find the dev who fubared this and put them out on their arse.
Lieutenant
Join Date: Jan 2013
Posts: 32
# 1387
01-28-2013, 11:14 AM
Quote:
Originally Posted by mrbaconsah View Post
You got a reply, hence my 'some packets do get through'.

Still convinced it's a load balancer.

I'd concur, it seems like it is load balancing through bad routes.
Ensign
Join Date: Jun 2012
Posts: 11
Microsoft Windows [Version 6.1.7601]
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.
Commander
Join Date: Dec 2012
Posts: 307
# 1389
01-28-2013, 11:14 AM
Quote:
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.

Do you think we don't know what tracert does?

He's dead, Jim.

Last edited by lolimpicard; 01-28-2013 at 11:17 AM.
Lieutenant
Join Date: Jan 2013
Posts: 32
# 1390
01-28-2013, 11:15 AM
Any Update topics from the devs yet ?????
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


All times are GMT -7. The time now is 01:55 AM.