Commander
Join Date: Dec 2012
Posts: 307
# 2101
01-28-2013, 02:25 PM
Quote:
Originally Posted by linyive View Post
As someone who lives south of Boston, I can assure you that the culprit was Deval Patrick or a Kennedy.
Hahaha oh god. This thread's better than ingame Zone chat.
I really wonder why they still havn't all been assassinated or died to their curse.

He's dead, Jim.
Lieutenant
Join Date: Jun 2012
Posts: 53
# 2102
01-28-2013, 02:25 PM
12 174 ms 179 ms 177 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.
130]

13 204 ms 208 ms 216 ms 38.111.40.114
14 154 ms 154 ms 154 ms 208.95.185.41

This Atlas works.

te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42
]

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 139 ms * * 208.95.185.41

THAT Atlas fails. It really MIGHT be Atlas' internal routing.
Ensign
Join Date: Dec 2012
Posts: 7
# 2103
01-28-2013, 02:25 PM
the problems started when q arrived .... ironic really , severe lagging more people getting stuck and melded with walls last night it was getting slower and slower last thing i saw and the reason i logged off was q sticking out of the floor and me as an undine melded to the chair jumping up and down ....
Ensign
Join Date: Jul 2012
Posts: 7
# 2104 tracert report
01-28-2013, 02:25 PM
G:\Users\******>tracert launcher.startrekonline.com

Tracing route to launcher.startrekonline.com [208.95.185.44]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms home.gateway.home.gateway [***********]
2 51 ms * 52 ms ***.***.***.***.static.exetel.com.au [***.***.***.***]
3 61 ms 52 ms 52 ms pe-5017327-akinginte01.gw.aapt.com.au [203.174.182.105]
4 72 ms 71 ms 73 ms gi1-1.akingdist01.aapt.net.au [203.131.63.14]
5 76 ms 75 ms 76 ms te2-1-110.akingdist02.aapt.net.au [202.10.12.159]
6 74 ms 73 ms 73 ms te0-3-4-0.akingcore02.aapt.net.au [202.10.12.37]

7 74 ms 73 ms 73 ms gi0-0-0-0.mburncore01.aapt.net.au [202.10.10.80]

8 73 ms 73 ms 73 ms bu2.sclarcore01.aapt.net.au [202.10.10.74]
9 73 ms 73 ms 72 ms te2-2.sclardist01.aapt.net.au [202.10.12.2]
10 75 ms 75 ms 75 ms po6.sclarbrdr01.aapt.net.au [202.10.14.3]
11 83 ms 75 ms 76 ms vlan-2755.tkbr4.global-gateway.net.nz [122.56.118.189]
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 221 ms 220 ms 221 ms xe-10-1-0.edge2.LosAngeles9.Level3.net [4.53.230.13]
16 233 ms 232 ms 232 ms ae-4-90.edge1.LosAngeles6.Level3.net [4.69.144.208]
17 256 ms 256 ms 256 ms te0-0-0-3.ccr21.lax04.atlas.cogentco.com [154.54.13.145]
18 222 ms 221 ms 234 ms te0-4-0-7.ccr21.lax01.atlas.cogentco.com [154.54.84.117]
19 289 ms 259 ms 259 ms te0-3-0-6.mpd21.iah01.atlas.cogentco.com [154.54.0.230]
20 279 ms 279 ms 278 ms te0-2-0-7.mpd21.atl01.atlas.cogentco.com [154.54.2.221]
21 291 ms 301 ms 291 ms te0-1-0-2.mpd21.dca01.atlas.cogentco.com [154.54.28.226]
22 305 ms 303 ms 302 ms te0-1-0-3.ccr21.jfk02.atlas.cogentco.com [154.54.5.245]
23 320 ms 312 ms 303 ms te0-2-0-1.ccr21.bos01.atlas.cogentco.com [154.54.44.10]
24 310 ms 310 ms 310 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.130]
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.
Ensign
Join Date: Jan 2013
Posts: 16
# 2105
01-28-2013, 02:25 PM
Quote:
Originally Posted by bobcarella View Post
Ok, I too will try to say something without the community turning. To all of the people who are just going to the last page and not actually reading anything on them... they are NOT blaming you people. They are simply saying it is not a global problem with the server but rather the ISP. If you read you will see they are not necessarily saying it is YOUR isp or YOUR computer. Please stop reacting like this is a personal attack. It does appear to be an ISP problem. Theirs.
i get your point, but when there are over 200 pages...i dont want to read every single page. And since I didn't find any Dev posts while going along except the 1 its very easy to think that game creators are all like...MEH... about the situtation.
Starfleet Veteran
Join Date: Dec 2012
Posts: 35
# 2106
01-28-2013, 02:25 PM
Have our intrepid engineers checked the permissions on the patch? It sounds like someone failed to set the permissions so that people outside of Cryptic/PWE network cannot get in. Using a VPN would be read by their network as a back door, and thus as within it.

Try setting the permissions to 5. Also, check and make sure that all end-of-line punctuation is present.

P.S.: If I'm right and this is the problem, I want a Temporal Destroyer as my consulting fee.
Lt. Commander
Join Date: Jul 2012
Posts: 101
# 2107
01-28-2013, 02:26 PM
Quote:
Originally Posted by x3o3 View Post
Quick fix would be a role back till they can figure it out.

Then test it on the test server so they can locate the issue.
It looks like a routing problem, not an issue on the STO servers directly. From my own and glancing at a few other traceroutes, routing through Cogent is screwed up. They need to get Cogent on the line and have them fix the routing. One of Cogent's routers is probably broadcasting garbage routes.
Career Officer
Join Date: Dec 2012
Posts: 121
# 2108
01-28-2013, 02:26 PM
Quote:
Originally Posted by lexofborg View Post
the problems started when q arrived .... ironic really , severe lagging more people getting stuck and melded with walls last night it was getting slower and slower last thing i saw and the reason i logged off was q sticking out of the floor and me as an undine melded to the chair jumping up and down ....
this sounds like the philadelphia experiment all over again lol
Ensign
Join Date: Sep 2012
Posts: 23
# 2109
01-28-2013, 02:26 PM
so i assume its a wast of time to think that we will be playing the game anytime soon? im missing some good pvp oppertunities here, so i either want the game back up soon or to be told that it wont be back up for how ever long its going to be . . .
Ensign
Join Date: Nov 2012
Posts: 17
# 2110
01-28-2013, 02:27 PM
Quote:
Originally Posted by schreader1718 View Post
Have our intrepid engineers checked the permissions on the patch? It sounds like someone failed to set the permissions so that people outside of Cryptic/PWE network cannot get in. Using a VPN would be read by their network as a back door, and thus as within it.

Try setting the permissions to 5. Also, check and make sure that all end-of-line punctuation is present.

P.S.: If I'm right and this is the problem, I want a Temporal Destroyer as my consulting fee.
If you are correct, they should give you a job...
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 02:39 PM.