Yes this is frustrating. I think we should all get a free ship or something for all the frustration we are going through. I love to play Star Trek on line to relax and get rid of frustrations.
3 65 ms 52 ms 43 ms dtr01blvlil-tge-0-4-0-7.blvl.il.charter.com [96.
34.54.12]
4 38 ms 24 ms 23 ms bbr01blvlil-tge-0-2-0-0.blvl.il.charter.com [96.
34.1.112]
5 59 ms 58 ms 46 ms 206.181.23.109
6 64 ms 24 ms 60 ms vb1720.rar3.chicago-il.us.xo.net [216.156.0.177]
7 44 ms * * 207.88.14.194.ptr.us.xo.net [207.88.14.194]
8 55 ms 52 ms 63 ms 0.xe-3-3-0.BR3.CHI13.ALTER.NET [204.255.168.97]
9 86 ms 92 ms 101 ms 0.ge-3-1-0.XL3.BOS4.ALTER.NET [152.63.20.217]
10 91 ms 87 ms 95 ms POS6-0.GW5.BOS4.ALTER.NET [152.63.25.69]
11 68 ms 77 ms 77 ms internap-gw.customer.alter.net [65.207.236.58]
12 95 ms 75 ms 99 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.1
04]
13 130 ms 72 ms 68 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
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 73 ms 94 ms * fr.playstartrekonline.eu [208.95.185.44]
23 * * * Request timed out.
24 * * * Request timed out.
25 * 69 ms * fr.playstartrekonline.eu [208.95.185.44]
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
So.. it occurred to me that if we're all running tracerts.. aren't we effectively ddos'ing ourselves?
Going in game at all and just staying there will still pose the same problem. Any time it needs to connect to the patch server at all it will eventually fail to respond. Any map changes, etc, will fail.
If internap is anything like most datacenters, replacing the hardware isn't like ordering fries at mcdonalds, its gonna take a bit.
Its not being fixed, you're just repetitively trying to connect and occasionally getting past the network problem.
You are misunderstanding the false positive of being able to connect. You aren't actually encountering any resolution at all - your network connection is merely taking a working route temporarily and then reverting back to the bad route.
PWE hasn't fixed or broken anything, I would even go so far as to say its not even patch related and its an unfortunately disastrous coincidental hardware failure.
NO...
In a word NO.
Look if it was a coincidental hardware failure it would be one site somewhere and 1 group of people would be unable to connect or ALL of them
Not groups of people dotted all over the world
Its the patch
Im an easy going guy and i can accept coincidence but this intermitant problem experienced by multiple people dotted all over the world
on the day of a major content patch and its a coincidence
Yeah right, you might have just gotten off the last banana boat but i dident.
Ever since perfect world took over this game its been a Joke in terms of service
Networks are organic, and they are able to repair themselves rather well. It just takes time. Unfortunately though, some of the automatic solutions only auto correct for a bit and then go back to bad. This is usually because of bad redundancy setups.
(In response to other posts that are blaming PWE)
I'm going to have to reiterate though... everyone who is blaming PWE may see the cliche behind pointing fingers, but you would be surprised at how little power even the largest companies have when they're in a datacenter and they don't own the space.
I'm not that network pro...
But I would never blame people for technical difficulties I don't know anything about.
I think you are right.
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 3 ms 3 ms 3 ms L100.HRBGPA-VFTTP-12.verizon-gni.net [98.117.0.1]
3 6 ms 6 ms 6 ms G10-0-8-112.HRBGPA-LCR-01.verizon-gni.net [130.81.184.148]
4 18 ms 18 ms 19 ms P12-0-0.HRBGPA-LCR-02.verizon-gni.net [130.81.27.185]
5 18 ms 18 ms 17 ms so-12-1-0-0.RES-BB-RTR1.verizon-gni.net [130.81.28.254]
6 72 ms 18 ms 18 ms xe-1-0-0-0.NWRK-BB-RTR2.verizon-gni.net [130.81.23.158]
7 21 ms 20 ms 20 ms 0.xe-8-0-0.XL4.NYC1.ALTER.NET [152.63.5.217]
8 32 ms 30 ms 30 ms 0.ge-3-1-0.XL4.BOS4.ALTER.NET [152.63.20.218]
9 29 ms 27 ms 29 ms POS7-0.GW5.BOS4.ALTER.NET [152.63.25.57]
10 30 ms 29 ms 30 ms internap-gw.customer.alter.net [65.207.236.58]
11 28 ms 29 ms 29 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.41]
12 30 ms 35 ms 35 ms perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
13 31 ms * * de.playstartrekonline.eu [208.95.185.44]
14 * * * Request timed out.
15 * * * Request timed out.
Then I did a control+C because it would just give a request timed out for the rest of the hops...
Its not being fixed, you're just repetitively trying to connect and occasionally getting past the network problem.
You are misunderstanding the false positive of being able to connect. You aren't actually encountering any resolution at all - your network connection is merely taking a working route temporarily and then reverting back to the bad route.
PWE hasn't fixed or broken anything, I would even go so far as to say its not even patch related and its an unfortunately disastrous coincidental hardware failure.
I thought they brought it down for maintenance early when I lost my connection 30 minutes before the scheduled downtime. Now I'm starting to think it was this network issue (same symptoms) and the timing was just unfortunate.
Assuming it was caused by the patching has probably delayed the resolution significantly.
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 * * * Request timed out.
2 9 ms 9 ms 9 ms unalloc-024-031-202-137.sc.rr.com [24.31.202.137
]
3 11 ms 13 ms 11 ms ge-3-0-0.chrlncpop-rtr1.southeast.rr.com [24.93.
64.62]
4 16 ms 23 ms 15 ms 107.14.19.46
5 49 ms 39 ms 38 ms ae-0-0.cr1.atl20.tbone.rr.com [66.109.6.35]
6 39 ms 38 ms 39 ms ae-4-0.cr0.dca10.tbone.rr.com [66.109.6.33]
7 34 ms 33 ms 33 ms ae-2-0.pr0.dca10.tbone.rr.com [66.109.6.169]
8 34 ms 33 ms 33 ms 107.14.16.34
9 35 ms 40 ms 36 ms cr2-tengig0-8-5-0.washington.savvis.net [204.70.
206.241]
10 42 ms 40 ms 45 ms cr2-te-0-3-1-0.nyr.savvis.net [204.70.192.2]
11 40 ms 43 ms 40 ms er1-te-2-1.newyorknyd.savvis.net [204.70.196.70]
12 46 ms 46 ms 47 ms msr1-te-0-3-0-0.bos.savvis.net [206.28.97.205]
13 47 ms 47 ms 46 ms 206.28.97.137
14 46 ms 47 ms 46 ms internap.Boston.savvis.net [208.172.51.230]
15 99 ms 238 ms 245 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.1
04]
16 52 ms 53 ms 53 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * 46 ms * 208.95.185.41
22 * * 48 ms 208.95.185.41
Traza a la direcci?n launcher.startrekonline.com [208.95.185.44]
sobre un m?ximo de 30 saltos:
1 2 ms 1 ms 1 ms mygateway1.ar7 [192.168.1.1]
2 43 ms 41 ms 42 ms 142.Red-80-58-67.staticIP.rima-tde.net []
3 54 ms 56 ms 53 ms 45.Red-80-58-87.staticIP.rima-tde.net []
4 52 ms 54 ms 51 ms 93.Red-80-58-87.staticIP.rima-tde.net []
5 53 ms 53 ms 53 ms 94.142.103.197
6 85 ms 85 ms 118 ms 176.52.250.226
7 152 ms 85 ms 86 ms 195.50.118.201
8 86 ms 88 ms 87 ms ae-2-52.edge4.London1.Level3.net [4.69.139.106]
9 86 ms 86 ms 86 ms IntelQ-Tinet-level3-2x10G.London.Level3.net [4.6
8.110.114]
10 235 ms 166 ms 166 ms xe-3-0-0.bos11.ip4.tinet.net [141.136.109.138]
11 165 ms 164 ms 164 ms internap-gw.ip4.tinet.net [77.67.77.54]
12 451 ms 445 ms 331 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.4
1]
13 559 ms 445 ms 332 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
14 * * * Tiempo de espera agotado para esta solicitud.
15 * * * Tiempo de espera agotado para esta solicitud.
16 * * 169 ms launcher.startrekonline.com [208.95.185.44]
Traza completa.
But it still doesn't work for me... the launcher says the same as my router wasn't on.
And another one (this one's "funny") :
Traza a la direcci?n launcher.startrekonline.com [208.95.185.44]
sobre un m?ximo de 30 saltos:
1 1 ms 1 ms 1 ms mygateway1.ar7 [192.168.1.1]
2 42 ms 42 ms 42 ms 142.Red-80-58-67.staticIP.rima-tde.net []
3 52 ms 54 ms 55 ms 45.Red-80-58-87.staticIP.rima-tde.net []
4 54 ms 54 ms 51 ms 93.Red-80-58-87.staticIP.rima-tde.net []
5 53 ms 56 ms 59 ms et7-0-0-1-GRTBCNES1.red.telefonica-wholesale.net
[94.142.103.197]
6 175 ms 98 ms 96 ms 176.52.250.226
7 86 ms 83 ms 86 ms 195.50.90.165
8 * * 86 ms ae-2-52.edge4.London1.Level3.net [4.69.139.106]
9 86 ms 95 ms 86 ms IntelQ-Tinet-level3-2x10G.London.Level3.net [4.6
8.110.114]
10 165 ms 207 ms 165 ms xe-3-0-0.bos11.ip4.tinet.net [141.136.109.138]
11 164 ms 163 ms 164 ms internap-gw.ip4.tinet.net [77.67.77.54]
12 168 ms 168 ms 168 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.4
1]
13 172 ms 160 ms 161 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
14 525 ms * * launcher.startrekonline.com [208.95.185.44]
15 * * * Tiempo de espera agotado para esta solicitud.
16 * 167 ms * launcher.startrekonline.com [208.95.185.44]
17 * * * Tiempo de espera agotado para esta solicitud.
18 * * * Tiempo de espera agotado para esta solicitud.
19 170 ms * * launcher.startrekonline.com [208.95.185.44]
20 * * * Tiempo de espera agotado para esta solicitud.
21 * * * Tiempo de espera agotado para esta solicitud.
22 * 171 ms * launcher.startrekonline.com [208.95.185.44]
23 * * * Tiempo de espera agotado para esta solicitud.
24 173 ms * * launcher.startrekonline.com [208.95.185.44]
25 * 163 ms * launcher.startrekonline.com [208.95.185.44]
26 * * * Tiempo de espera agotado para esta solicitud.
27 * * * Tiempo de espera agotado para esta solicitud.
28 * * * Tiempo de espera agotado para esta solicitud.
29 * * * Tiempo de espera agotado para esta solicitud.
30 * * * Tiempo de espera agotado para esta solicitud.
Well I waited all day to play and it worked for about 2 hours and stopped working again. Its doing the same thing it was all day long. I hope you guys get it fixed. I left WoW to play STO. Does this happen all the time? I just started playing a couple days ago. Just wondering.
Microsoft Windows [Version *******]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\Me>ping 216.52.61.78
Pinging 216.52.61.78 with 32 bytes of data:
Reply from 216.52.61.78: bytes=32 time=36ms TTL=252
Request timed out.
Reply from 216.52.61.78: bytes=32 time=30ms TTL=252
Reply from 216.52.61.78: bytes=32 time=34ms TTL=252
Ping statistics for 216.52.61.78:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 30ms, Maximum = 36ms, Average = 33ms
C:\Users\Me>
Pinged the IP and this is what I got...tell me another one. :mad:
Launcher worked at around 6:45 PM EST today, though it is now 10:30 PM EST and once again the same issue. The launcher is failing to open properly. All I am getting is a white screen that says "Loading. Please Wait".
Look if it was a coincidental hardware failure it would be one site somewhere and 1 group of people would be unable to connect or ALL of them
Not groups of people dotted all over the world
Its the patch
Im an easy going guy and i can accept coincidence but this intermitant problem experienced by multiple people dotted all over the world
on the day of a major content patch and its a coincidence
Yeah right, you might have just gotten off the last banana boat but i dident.
Ever since perfect world took over this game its been a Joke in terms of service
I mean totaly pathetic
Routes into a datacenter have nothing to do with geographical location. When you reach the destination itself, no matter what you think or believe, there is not a router for each country in the world.
PWE does not operate UK servers. We all live on one single server globally. Whether you want to see that or not, isn't really relevant to the problem at hand.
No matter where you come from or what you do, you will always hit stohttppatching.crypticstudios.com, and if there is any logic to their network design then chances are the border routers are aligned redundantly.
Anyone who has ever worked in a high traffic environment knows that redundancy is a false sense of security. A hundred things can go wrong with routed traffic and it can easily not work, or not update routing tables, or a billion other things.
If you ever run your own dns, or look into the possible errors and bad situations you can have with it, you'll learn that the global TTL values for any updates to any DNS or routing tables can take up to 48 hours depending on how they are done, and routing tables are the worst of them all. There is still 30 year old hardware handling some internet routing.
If it was a patch related issue we would be connecting and getting kicked out, there would be crashing, and the information people would be giving would be of a game related nature. People are having connection issues, and I know of only one MMO on this planet that has networking code embedded into the software of the game itself to the degree that it would be able to act as evidence towards the software claim, and thats EVE.
Routers fail, especially the ones datacenters use for private customer cabinet space, and even more so when it pertains to games.
Well I waited all day to play and it worked for about 2 hours and stopped working again. Its doing the same thing it was all day long. I hope you guys get it fixed. I left WoW to play STO. Does this happen all the time? I just started playing a couple days ago. Just wondering.
It was working fine under Cryptic, but then Perfect World took control directly and the CS has gone to TRIBBLE. The CS seems to be as bad as Star Wars The Old Republic. Like there, it seems to be policy to blame the customers rather than fix the issue. The game was working fine until this effing patched effed it up.
why is game still doing this ... Clean your bugs up :mad: i got booted form server and now waiting to get launcher to launcher....:( this worst part of the every time you offer something new these crashes come with it. I'm lifetime form 3 years back look this issue with launcher was never fixed stop pooing on me please it would be nice i like to play your game a spend more money :mad: think you guys need make up for this launcher issue... and do something... Evertime locks up you send keys out to everyone posted about the issue.
[SIGPIC][/SIGPIC] DELTA RISING FIXS THERE NEVER COMING WHY I'M I WASTING MY TIME ASKING FOR THEM ???
I can trace it completely from my modem, but not from my pc.
Traceroute to 208.95.185.44 (timer gran. 10 ms)...
30 hops max, 56 byte packets
1 74.232.85.1 20 ms 30 ms 20 ms
2 70.159.176.205 30 ms 20 ms 30 ms
3 70.159.178.141 20 ms 30 ms 20 ms
4 70.159.176.38 30 ms 20 ms 30 ms
5 12.81.16.32 30 ms 20 ms 30 ms
6 12.81.16.15 30 ms 20 ms 30 ms
7 74.175.192.62 20 ms 30 ms 30 ms
8 12.122.141.186 30 ms 30 ms 40 ms
9 12.123.22.25 80 ms 100 ms 30 ms
10 144.232.1.65 20 ms 30 ms 30 ms
11 144.232.1.219 20 ms 30 ms 30 ms
12 144.232.5.114 20 ms 30 ms 30 ms
13 144.232.5.211 40 ms 40 ms 30 ms
14 144.232.10.46 50 ms 40 ms 50 ms
15 144.232.8.165 40 ms 50 ms 50 ms
16 144.232.20.164 50 ms 60 ms 60 ms
17 144.232.25.23 60 ms 60 ms 60 ms
18 144.232.8.48 60 ms 60 ms 60 ms
19 144.223.45.50 60 ms 70 ms 60 ms
20 63.251.128.104 150 ms 220 ms *
21 216.52.61.78 80 ms 90 ms 90 ms
22 208.95.185.44 80 ms ! * *
Traceroute complete - host found
Tracing route to launcher.startrekonline.com [208.95.185.44]
over a maximum of 30 hops:
1 1 ms 1 ms <1 ms 192.168.0.1
2 1 ms 1 ms 2 ms 192.168.1.254
3 30 ms 26 ms 27 ms adsl-74-232-85-1.asm.bellsouth.net [74.232.85.1]
4 26 ms 26 ms 26 ms 70.159.176.205
5 26 ms 25 ms 26 ms 70.159.178.141
6 28 ms 26 ms 35 ms 70.159.176.38
7 28 ms 33 ms 29 ms 12.81.16.32
8 25 ms 25 ms 26 ms 12.81.16.15
9 26 ms 26 ms 27 ms 74.175.192.62
10 31 ms 33 ms 28 ms cr1.attga.ip.att.net [12.122.141.186]
11 90 ms 34 ms 26 ms attga02jt.ip.att.net [12.123.22.25]
12 26 ms 51 ms 27 ms 144.232.1.65
13 30 ms 27 ms 28 ms sl-crs4-atl-.sprintlink.net [144.232.1.219]
14 29 ms 27 ms 28 ms sl-crs2-atl-0-3-0-0.sprintlink.net [144.232.5.114]
15 35 ms 31 ms 31 ms 144.232.5.211
16 45 ms 45 ms 46 ms 144.232.10.46
17 47 ms 47 ms 47 ms sl-crs2-rly-0-0-3-0.sprintlink.net [144.232.8.165]
18 58 ms 62 ms 57 ms sl-crs2-nyc-0-4-0-0.sprintlink.net [144.232.20.164]
19 68 ms 62 ms 64 ms sl-crs2-spr-0-0-2-0.sprintlink.net [144.232.25.23]
20 62 ms 62 ms 64 ms sl-st20-bos-0-0-0.sprintlink.net [144.232.8.48]
21 198 ms 201 ms 375 ms sl-internap-190725-0.sprintlink.net [144.223.45.50]
22 67 ms 76 ms 78 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.104]
23 * 85 ms * perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
24 * * * Request timed out.
25 * * * Request timed out.
26 83 ms * * de.startrekonline.com [208.95.185.44]
27 * * * Request timed out.
28 81 ms * 81 ms de.startrekonline.com [208.95.185.44]
Trace complete.
Every so often, I can get the logon window to pop up, but even if it eventually draws completely, the logon box doesn't function.
Tracing route to launcher.startrekonline.com [208.95.185.44]
over a maximum of 30 hops:
1 82 ms 83 ms 84 ms 10.9.120.1
2 106 ms 97 ms 90 ms 50.117.78.129
3 96 ms 122 ms 131 ms xe-4-0-4.ar2.sjc1.us.nlayer.net [69.22.130.5]
4 94 ms 92 ms 89 ms TenGigE0-2-2-0.GW3.SJC7.ALTER.NET [152.179.48.21
]
5 88 ms 86 ms 108 ms 0.xe-2-1-4.XL3.SJC7.ALTER.NET [152.63.51.65]
6 164 ms 165 ms 169 ms 0.ge-7-0-0.XL3.BOS4.ALTER.NET [152.63.0.165]
7 165 ms 165 ms 174 ms POS6-0.GW5.BOS4.ALTER.NET [152.63.25.69]
8 161 ms 158 ms 169 ms internap-gw.customer.alter.net [65.207.236.58]
9 182 ms 165 ms 160 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.1
04]
10 160 ms 162 ms 169 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
11 181 ms 176 ms 177 ms 208.95.185.44
Trace complete.
Non-Working (Using Time Warner cable near Charlotte, NC)
C:\Users\ncbwilson>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 DD-WRT [192.168.1.1]
2 * * * Request timed out.
3 11 ms 21 ms 17 ms chrlncmh-qt61.carolina.rr.com [24.93.75.106]
4 16 ms 59 ms 32 ms ae18.chrlncpop-rtr1.southeast.rr.com [24.93.64.6
]
5 36 ms 30 ms 48 ms 107.14.19.18
6 28 ms 40 ms 31 ms ae-0-0.cr1.atl20.tbone.rr.com [66.109.6.35]
7 40 ms 32 ms 39 ms ae-4-0.cr0.dca10.tbone.rr.com [66.109.6.33]
8 26 ms 25 ms 27 ms 107.14.19.133
9 26 ms 23 ms 23 ms 107.14.16.34
10 29 ms 27 ms 26 ms cr2-tengig0-8-5-0.washington.savvis.net [204.70.
206.241]
11 34 ms 35 ms 34 ms cr2-te-0-3-1-0.nyr.savvis.net [204.70.192.2]
12 91 ms 52 ms 46 ms er1-te-2-1.newyorknyd.savvis.net [204.70.196.70]
13 41 ms 45 ms 48 ms msr1-te-0-3-0-0.bos.savvis.net [206.28.97.205]
14 54 ms 57 ms 52 ms 206.28.97.137
15 40 ms 49 ms 51 ms internap.Boston.savvis.net [208.172.51.230]
16 71 ms 44 ms 39 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.1
04]
17 63 ms 51 ms 38 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
18 * * * Request timed out.
19 * * 39 ms www.playstartrek.fr [208.95.185.44]
Trace complete.
Here is the pcl log as well during the above:
130129 03:11:44 1 [1]: Using HTTP patching: server stohttppatch.crypticstudios.com port 80 prefix Startrek
130129 03:11:46 2 [1]: Syncing files
130129 03:11:46 3 [1]: Scanning hogg C:/Program Files (x86)/Steam/steamapps/common/Star Trek Online/Star Trek Online/Live/piggs/bins3.hogg
130129 03:11:46 4 [1]: Scanning hogg C:/Program Files (x86)/Steam/steamapps/common/Star Trek Online/Star Trek Online/Live/piggs/bins2.hogg
130129 03:11:46 5 [1]: Scanning hogg C:/Program Files (x86)/Steam/steamapps/common/Star Trek Online/Star Trek Online/Live/piggs/bins.hogg
130129 03:11:46 6 [1]: Scanning hogg C:/Program Files (x86)/Steam/steamapps/common/Star Trek Online/Star Trek Online/Live/piggs/character.hogg
130129 03:11:46 7 [1]: Scanning hogg C:/Program Files (x86)/Steam/steamapps/common/Star Trek Online/Star Trek Online/Live/piggs/object.hogg
130129 03:11:46 8 [1]: Scanning hogg C:/Program Files (x86)/Steam/steamapps/common/Star Trek Online/Star Trek Online/Live/piggs/sound.hogg
130129 03:11:46 9 [1]: Scanning hogg C:/Program Files (x86)/Steam/steamapps/common/Star Trek Online/Star Trek Online/Live/piggs/texture3.hogg
130129 03:11:46 10 [1]: Scanning hogg C:/Program Files (x86)/Steam/steamapps/common/Star Trek Online/Star Trek Online/Live/piggs/texture2.hogg
130129 03:11:46 11 [1]: Scanning hogg C:/Program Files (x86)/Steam/steamapps/common/Star Trek Online/Star Trek Online/Live/piggs/texture.hogg
130129 03:11:46 12 [1]: Scanning hogg C:/Program Files (x86)/Steam/steamapps/common/Star Trek Online/Star Trek Online/Live/piggs/data.hogg
130129 03:11:47 13 [1]: Scanning hogg C:/Program Files (x86)/Steam/steamapps/common/Star Trek Online/Star Trek Online/Live/piggs/exes.hogg
130129 03:11:47 14 [1]: HTTP patching connected to stohttppatch.crypticstudios.com:80
130129 03:11:47 15 [1]: HTTP patching connected to stohttppatch.crypticstudios.com:80
130129 03:11:48 16 [1]: HTTP patching connected to stohttppatch.crypticstudios.com:80
130129 03:11:48 17 [1]: HTTP patching connected to stohttppatch.crypticstudios.com:80
130129 03:11:58 18 [1]: HTTP patching connected to stohttppatch.crypticstudios.com:80
130129 03:22:09 19 [1]: HTTP patching disconnected from stohttppatch.crypticstudios.com:80: socket was shutdown(10054:Connection reset by remote host)
130129 03:22:09 20 [1]: HTTP patching connected to stohttppatch.crypticstudios.com:80
130129 03:22:09 21 [1]: HTTP patching disconnected from stohttppatch.crypticstudios.com:80: socket was shutdown(10054:Connection reset by remote host)
130129 03:22:09 22 [1]: HTTP patching connected to stohttppatch.crypticstudios.com:80
130129 03:23:53 23 [1]: HTTP patching disconnected from stohttppatch.crypticstudios.com:80: socket was shutdown(0:No error)
130129 03:25:25 24 [1]: HTTP patching disconnected from stohttppatch.crypticstudios.com:80: socket was shutdown(10053:Connection reset locally)
130129 03:25:25 25 [1]: HTTP patching disconnected from stohttppatch.crypticstudios.com:80: socket was shutdown(10053:Connection reset locally)
130129 03:25:25 26 [1]: HTTP patching disconnected from stohttppatch.crypticstudios.com:80: socket was shutdown(10053:Connection reset locally)
130129 03:25:25 27 [1]: HTTP patching disconnected from stohttppatch.crypticstudios.com:80: socket was shutdown(10053:Connection reset locally)
130129 03:25:25 28 [1] ESC : Error: The patchclientlib is internally recording error code : 14\nThe connection to the server was lost - unexpectedly disconnected
Comments
And why u didnt Restart the Server to check if that Fix the Problem?
Still not Possible to Play the Game Since Maintance.
34.54.12]
4 38 ms 24 ms 23 ms bbr01blvlil-tge-0-2-0-0.blvl.il.charter.com [96.
34.1.112]
5 59 ms 58 ms 46 ms 206.181.23.109
6 64 ms 24 ms 60 ms vb1720.rar3.chicago-il.us.xo.net [216.156.0.177]
7 44 ms * * 207.88.14.194.ptr.us.xo.net [207.88.14.194]
8 55 ms 52 ms 63 ms 0.xe-3-3-0.BR3.CHI13.ALTER.NET [204.255.168.97]
9 86 ms 92 ms 101 ms 0.ge-3-1-0.XL3.BOS4.ALTER.NET [152.63.20.217]
10 91 ms 87 ms 95 ms POS6-0.GW5.BOS4.ALTER.NET [152.63.25.69]
11 68 ms 77 ms 77 ms internap-gw.customer.alter.net [65.207.236.58]
12 95 ms 75 ms 99 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.1
04]
13 130 ms 72 ms 68 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
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 73 ms 94 ms * fr.playstartrekonline.eu [208.95.185.44]
23 * * * Request timed out.
24 * * * Request timed out.
25 * 69 ms * fr.playstartrekonline.eu [208.95.185.44]
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
So.. it occurred to me that if we're all running tracerts.. aren't we effectively ddos'ing ourselves?
If internap is anything like most datacenters, replacing the hardware isn't like ordering fries at mcdonalds, its gonna take a bit.
Hubby says to tell you "You Developer TRIBBLE! You killed my Game!"
As frustrating as this is we understand these things happen... and we are confident you will find a solution soon. Good Luck Guys (and Gals).
Thanks!
hope its fixed soon
NO...
In a word NO.
Look if it was a coincidental hardware failure it would be one site somewhere and 1 group of people would be unable to connect or ALL of them
Not groups of people dotted all over the world
Its the patch
Im an easy going guy and i can accept coincidence but this intermitant problem experienced by multiple people dotted all over the world
on the day of a major content patch and its a coincidence
Yeah right, you might have just gotten off the last banana boat but i dident.
Ever since perfect world took over this game its been a Joke in terms of service
I mean totaly pathetic
I'm not that network pro...
But I would never blame people for technical difficulties I don't know anything about.
I think you are right.
Best regards
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 3 ms 3 ms 3 ms L100.HRBGPA-VFTTP-12.verizon-gni.net [98.117.0.1]
3 6 ms 6 ms 6 ms G10-0-8-112.HRBGPA-LCR-01.verizon-gni.net [130.81.184.148]
4 18 ms 18 ms 19 ms P12-0-0.HRBGPA-LCR-02.verizon-gni.net [130.81.27.185]
5 18 ms 18 ms 17 ms so-12-1-0-0.RES-BB-RTR1.verizon-gni.net [130.81.28.254]
6 72 ms 18 ms 18 ms xe-1-0-0-0.NWRK-BB-RTR2.verizon-gni.net [130.81.23.158]
7 21 ms 20 ms 20 ms 0.xe-8-0-0.XL4.NYC1.ALTER.NET [152.63.5.217]
8 32 ms 30 ms 30 ms 0.ge-3-1-0.XL4.BOS4.ALTER.NET [152.63.20.218]
9 29 ms 27 ms 29 ms POS7-0.GW5.BOS4.ALTER.NET [152.63.25.57]
10 30 ms 29 ms 30 ms internap-gw.customer.alter.net [65.207.236.58]
11 28 ms 29 ms 29 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.41]
12 30 ms 35 ms 35 ms perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
13 31 ms * * de.playstartrekonline.eu [208.95.185.44]
14 * * * Request timed out.
15 * * * Request timed out.
Then I did a control+C because it would just give a request timed out for the rest of the hops...
then it goes to loading please wait on launcher.....
then it gives me that Internet explorer can not display the webpage.
Seems to me that the problem with autopatcher of the launcher has been fixed and now they are just working the kinks of the launcher itself
I thought they brought it down for maintenance early when I lost my connection 30 minutes before the scheduled downtime. Now I'm starting to think it was this network issue (same symptoms) and the timing was just unfortunate.
Assuming it was caused by the patching has probably delayed the resolution significantly.
over a maximum of 30 hops:
1 * * * Request timed out.
2 9 ms 9 ms 9 ms unalloc-024-031-202-137.sc.rr.com [24.31.202.137
]
3 11 ms 13 ms 11 ms ge-3-0-0.chrlncpop-rtr1.southeast.rr.com [24.93.
64.62]
4 16 ms 23 ms 15 ms 107.14.19.46
5 49 ms 39 ms 38 ms ae-0-0.cr1.atl20.tbone.rr.com [66.109.6.35]
6 39 ms 38 ms 39 ms ae-4-0.cr0.dca10.tbone.rr.com [66.109.6.33]
7 34 ms 33 ms 33 ms ae-2-0.pr0.dca10.tbone.rr.com [66.109.6.169]
8 34 ms 33 ms 33 ms 107.14.16.34
9 35 ms 40 ms 36 ms cr2-tengig0-8-5-0.washington.savvis.net [204.70.
206.241]
10 42 ms 40 ms 45 ms cr2-te-0-3-1-0.nyr.savvis.net [204.70.192.2]
11 40 ms 43 ms 40 ms er1-te-2-1.newyorknyd.savvis.net [204.70.196.70]
12 46 ms 46 ms 47 ms msr1-te-0-3-0-0.bos.savvis.net [206.28.97.205]
13 47 ms 47 ms 46 ms 206.28.97.137
14 46 ms 47 ms 46 ms internap.Boston.savvis.net [208.172.51.230]
15 99 ms 238 ms 245 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.1
04]
16 52 ms 53 ms 53 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * 46 ms * 208.95.185.41
22 * * 48 ms 208.95.185.41
Trace complete.
NETTEST
Ping: 50.0 msec
Port: 80: 275 KB/sec 14 KB/sec 320 KB/sec 500
Port: 80: 316 KB/sec 17 KB/sec 379 KB/sec 500
Port: 443: 468 KB/sec 19 KB/sec 521 KB/sec 500
Port: 443: 405 KB/sec 20 KB/sec 437 KB/sec 500
Port: 7255: 463 KB/sec 21 KB/sec 533 KB/sec 500
Port: 7255: 1028 KB/sec 34 KB/sec 1089 KB/sec 500
Port: 7003: 501 KB/sec 19 KB/sec 535 KB/sec 500
Port: 7003: 496 KB/sec 18 KB/sec 527 KB/sec 500
Port: 7202: 479 KB/sec 18 KB/sec 518 KB/sec 500
Port: 7202: 460 KB/sec 14 KB/sec 497 KB/sec 500
Port: 7499: 448 KB/sec 18 KB/sec 496 KB/sec 500
Port: 7499: 415 KB/sec 16 KB/sec 450 KB/sec 500
Port: 80: 301 KB/sec 15 KB/sec 345 KB/sec 500
Idle NIC bandwidth Send: 2 KB/sec Recv: 24 KB/sec
hit return to exit
Traza a la direcci?n launcher.startrekonline.com [208.95.185.44]
sobre un m?ximo de 30 saltos:
1 2 ms 1 ms 1 ms mygateway1.ar7 [192.168.1.1]
2 43 ms 41 ms 42 ms 142.Red-80-58-67.staticIP.rima-tde.net []
3 54 ms 56 ms 53 ms 45.Red-80-58-87.staticIP.rima-tde.net []
4 52 ms 54 ms 51 ms 93.Red-80-58-87.staticIP.rima-tde.net []
5 53 ms 53 ms 53 ms 94.142.103.197
6 85 ms 85 ms 118 ms 176.52.250.226
7 152 ms 85 ms 86 ms 195.50.118.201
8 86 ms 88 ms 87 ms ae-2-52.edge4.London1.Level3.net [4.69.139.106]
9 86 ms 86 ms 86 ms IntelQ-Tinet-level3-2x10G.London.Level3.net [4.6
8.110.114]
10 235 ms 166 ms 166 ms xe-3-0-0.bos11.ip4.tinet.net [141.136.109.138]
11 165 ms 164 ms 164 ms internap-gw.ip4.tinet.net [77.67.77.54]
12 451 ms 445 ms 331 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.4
1]
13 559 ms 445 ms 332 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
14 * * * Tiempo de espera agotado para esta solicitud.
15 * * * Tiempo de espera agotado para esta solicitud.
16 * * 169 ms launcher.startrekonline.com [208.95.185.44]
Traza completa.
But it still doesn't work for me... the launcher says the same as my router wasn't on.
And another one (this one's "funny") :
Traza a la direcci?n launcher.startrekonline.com [208.95.185.44]
sobre un m?ximo de 30 saltos:
1 1 ms 1 ms 1 ms mygateway1.ar7 [192.168.1.1]
2 42 ms 42 ms 42 ms 142.Red-80-58-67.staticIP.rima-tde.net []
3 52 ms 54 ms 55 ms 45.Red-80-58-87.staticIP.rima-tde.net []
4 54 ms 54 ms 51 ms 93.Red-80-58-87.staticIP.rima-tde.net []
5 53 ms 56 ms 59 ms et7-0-0-1-GRTBCNES1.red.telefonica-wholesale.net
[94.142.103.197]
6 175 ms 98 ms 96 ms 176.52.250.226
7 86 ms 83 ms 86 ms 195.50.90.165
8 * * 86 ms ae-2-52.edge4.London1.Level3.net [4.69.139.106]
9 86 ms 95 ms 86 ms IntelQ-Tinet-level3-2x10G.London.Level3.net [4.6
8.110.114]
10 165 ms 207 ms 165 ms xe-3-0-0.bos11.ip4.tinet.net [141.136.109.138]
11 164 ms 163 ms 164 ms internap-gw.ip4.tinet.net [77.67.77.54]
12 168 ms 168 ms 168 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.4
1]
13 172 ms 160 ms 161 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
14 525 ms * * launcher.startrekonline.com [208.95.185.44]
15 * * * Tiempo de espera agotado para esta solicitud.
16 * 167 ms * launcher.startrekonline.com [208.95.185.44]
17 * * * Tiempo de espera agotado para esta solicitud.
18 * * * Tiempo de espera agotado para esta solicitud.
19 170 ms * * launcher.startrekonline.com [208.95.185.44]
20 * * * Tiempo de espera agotado para esta solicitud.
21 * * * Tiempo de espera agotado para esta solicitud.
22 * 171 ms * launcher.startrekonline.com [208.95.185.44]
23 * * * Tiempo de espera agotado para esta solicitud.
24 173 ms * * launcher.startrekonline.com [208.95.185.44]
25 * 163 ms * launcher.startrekonline.com [208.95.185.44]
26 * * * Tiempo de espera agotado para esta solicitud.
27 * * * Tiempo de espera agotado para esta solicitud.
28 * * * Tiempo de espera agotado para esta solicitud.
29 * * * Tiempo de espera agotado para esta solicitud.
30 * * * Tiempo de espera agotado para esta solicitud.
Traza completa.
Join date 20 Sept 2008
And now the launcher is being cranky again
(1) connecting to VPN before launching STO gets me in.
(2) Logged off but kept launcher off after disconnecting from VPN. No problem.
(3) Exiting then re-launching again does not work. Evidently more an issue than just updating the launcher once successfully connecting.
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\Me>ping 216.52.61.78
Pinging 216.52.61.78 with 32 bytes of data:
Reply from 216.52.61.78: bytes=32 time=36ms TTL=252
Request timed out.
Reply from 216.52.61.78: bytes=32 time=30ms TTL=252
Reply from 216.52.61.78: bytes=32 time=34ms TTL=252
Ping statistics for 216.52.61.78:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 30ms, Maximum = 36ms, Average = 33ms
C:\Users\Me>
Pinged the IP and this is what I got...tell me another one. :mad:
When will Cryptic fix this godforsaken issue???
Routes into a datacenter have nothing to do with geographical location. When you reach the destination itself, no matter what you think or believe, there is not a router for each country in the world.
PWE does not operate UK servers. We all live on one single server globally. Whether you want to see that or not, isn't really relevant to the problem at hand.
No matter where you come from or what you do, you will always hit stohttppatching.crypticstudios.com, and if there is any logic to their network design then chances are the border routers are aligned redundantly.
Anyone who has ever worked in a high traffic environment knows that redundancy is a false sense of security. A hundred things can go wrong with routed traffic and it can easily not work, or not update routing tables, or a billion other things.
If you ever run your own dns, or look into the possible errors and bad situations you can have with it, you'll learn that the global TTL values for any updates to any DNS or routing tables can take up to 48 hours depending on how they are done, and routing tables are the worst of them all. There is still 30 year old hardware handling some internet routing.
If it was a patch related issue we would be connecting and getting kicked out, there would be crashing, and the information people would be giving would be of a game related nature. People are having connection issues, and I know of only one MMO on this planet that has networking code embedded into the software of the game itself to the degree that it would be able to act as evidence towards the software claim, and thats EVE.
Routers fail, especially the ones datacenters use for private customer cabinet space, and even more so when it pertains to games.
It was working fine under Cryptic, but then Perfect World took control directly and the CS has gone to TRIBBLE. The CS seems to be as bad as Star Wars The Old Republic. Like there, it seems to be policy to blame the customers rather than fix the issue. The game was working fine until this effing patched effed it up.
DELTA RISING FIXS THERE NEVER COMING WHY I'M I WASTING MY TIME ASKING FOR THEM ???
Traceroute to 208.95.185.44 (timer gran. 10 ms)...
30 hops max, 56 byte packets
1 74.232.85.1 20 ms 30 ms 20 ms
2 70.159.176.205 30 ms 20 ms 30 ms
3 70.159.178.141 20 ms 30 ms 20 ms
4 70.159.176.38 30 ms 20 ms 30 ms
5 12.81.16.32 30 ms 20 ms 30 ms
6 12.81.16.15 30 ms 20 ms 30 ms
7 74.175.192.62 20 ms 30 ms 30 ms
8 12.122.141.186 30 ms 30 ms 40 ms
9 12.123.22.25 80 ms 100 ms 30 ms
10 144.232.1.65 20 ms 30 ms 30 ms
11 144.232.1.219 20 ms 30 ms 30 ms
12 144.232.5.114 20 ms 30 ms 30 ms
13 144.232.5.211 40 ms 40 ms 30 ms
14 144.232.10.46 50 ms 40 ms 50 ms
15 144.232.8.165 40 ms 50 ms 50 ms
16 144.232.20.164 50 ms 60 ms 60 ms
17 144.232.25.23 60 ms 60 ms 60 ms
18 144.232.8.48 60 ms 60 ms 60 ms
19 144.223.45.50 60 ms 70 ms 60 ms
20 63.251.128.104 150 ms 220 ms *
21 216.52.61.78 80 ms 90 ms 90 ms
22 208.95.185.44 80 ms ! * *
Traceroute complete - host found
Tracing route to launcher.startrekonline.com [208.95.185.44]
over a maximum of 30 hops:
1 1 ms 1 ms <1 ms 192.168.0.1
2 1 ms 1 ms 2 ms 192.168.1.254
3 30 ms 26 ms 27 ms adsl-74-232-85-1.asm.bellsouth.net [74.232.85.1]
4 26 ms 26 ms 26 ms 70.159.176.205
5 26 ms 25 ms 26 ms 70.159.178.141
6 28 ms 26 ms 35 ms 70.159.176.38
7 28 ms 33 ms 29 ms 12.81.16.32
8 25 ms 25 ms 26 ms 12.81.16.15
9 26 ms 26 ms 27 ms 74.175.192.62
10 31 ms 33 ms 28 ms cr1.attga.ip.att.net [12.122.141.186]
11 90 ms 34 ms 26 ms attga02jt.ip.att.net [12.123.22.25]
12 26 ms 51 ms 27 ms 144.232.1.65
13 30 ms 27 ms 28 ms sl-crs4-atl-.sprintlink.net [144.232.1.219]
14 29 ms 27 ms 28 ms sl-crs2-atl-0-3-0-0.sprintlink.net [144.232.5.114]
15 35 ms 31 ms 31 ms 144.232.5.211
16 45 ms 45 ms 46 ms 144.232.10.46
17 47 ms 47 ms 47 ms sl-crs2-rly-0-0-3-0.sprintlink.net [144.232.8.165]
18 58 ms 62 ms 57 ms sl-crs2-nyc-0-4-0-0.sprintlink.net [144.232.20.164]
19 68 ms 62 ms 64 ms sl-crs2-spr-0-0-2-0.sprintlink.net [144.232.25.23]
20 62 ms 62 ms 64 ms sl-st20-bos-0-0-0.sprintlink.net [144.232.8.48]
21 198 ms 201 ms 375 ms sl-internap-190725-0.sprintlink.net [144.223.45.50]
22 67 ms 76 ms 78 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.104]
23 * 85 ms * perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
24 * * * Request timed out.
25 * * * Request timed out.
26 83 ms * * de.startrekonline.com [208.95.185.44]
27 * * * Request timed out.
28 81 ms * 81 ms de.startrekonline.com [208.95.185.44]
Trace complete.
Every so often, I can get the logon window to pop up, but even if it eventually draws completely, the logon box doesn't function.
C:\Users\ncbwilson>tracert launcher.startrekonline.com
Tracing route to launcher.startrekonline.com [208.95.185.44]
over a maximum of 30 hops:
1 82 ms 83 ms 84 ms 10.9.120.1
2 106 ms 97 ms 90 ms 50.117.78.129
3 96 ms 122 ms 131 ms xe-4-0-4.ar2.sjc1.us.nlayer.net [69.22.130.5]
4 94 ms 92 ms 89 ms TenGigE0-2-2-0.GW3.SJC7.ALTER.NET [152.179.48.21
]
5 88 ms 86 ms 108 ms 0.xe-2-1-4.XL3.SJC7.ALTER.NET [152.63.51.65]
6 164 ms 165 ms 169 ms 0.ge-7-0-0.XL3.BOS4.ALTER.NET [152.63.0.165]
7 165 ms 165 ms 174 ms POS6-0.GW5.BOS4.ALTER.NET [152.63.25.69]
8 161 ms 158 ms 169 ms internap-gw.customer.alter.net [65.207.236.58]
9 182 ms 165 ms 160 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.1
04]
10 160 ms 162 ms 169 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
11 181 ms 176 ms 177 ms 208.95.185.44
Trace complete.
Non-Working (Using Time Warner cable near Charlotte, NC)
C:\Users\ncbwilson>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 DD-WRT [192.168.1.1]
2 * * * Request timed out.
3 11 ms 21 ms 17 ms chrlncmh-qt61.carolina.rr.com [24.93.75.106]
4 16 ms 59 ms 32 ms ae18.chrlncpop-rtr1.southeast.rr.com [24.93.64.6
]
5 36 ms 30 ms 48 ms 107.14.19.18
6 28 ms 40 ms 31 ms ae-0-0.cr1.atl20.tbone.rr.com [66.109.6.35]
7 40 ms 32 ms 39 ms ae-4-0.cr0.dca10.tbone.rr.com [66.109.6.33]
8 26 ms 25 ms 27 ms 107.14.19.133
9 26 ms 23 ms 23 ms 107.14.16.34
10 29 ms 27 ms 26 ms cr2-tengig0-8-5-0.washington.savvis.net [204.70.
206.241]
11 34 ms 35 ms 34 ms cr2-te-0-3-1-0.nyr.savvis.net [204.70.192.2]
12 91 ms 52 ms 46 ms er1-te-2-1.newyorknyd.savvis.net [204.70.196.70]
13 41 ms 45 ms 48 ms msr1-te-0-3-0-0.bos.savvis.net [206.28.97.205]
14 54 ms 57 ms 52 ms 206.28.97.137
15 40 ms 49 ms 51 ms internap.Boston.savvis.net [208.172.51.230]
16 71 ms 44 ms 39 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.1
04]
17 63 ms 51 ms 38 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
18 * * * Request timed out.
19 * * 39 ms www.playstartrek.fr [208.95.185.44]
Trace complete.
Here is the pcl log as well during the above:
130129 03:11:44 1 [1]: Using HTTP patching: server stohttppatch.crypticstudios.com port 80 prefix Startrek
130129 03:11:46 2 [1]: Syncing files
130129 03:11:46 3 [1]: Scanning hogg C:/Program Files (x86)/Steam/steamapps/common/Star Trek Online/Star Trek Online/Live/piggs/bins3.hogg
130129 03:11:46 4 [1]: Scanning hogg C:/Program Files (x86)/Steam/steamapps/common/Star Trek Online/Star Trek Online/Live/piggs/bins2.hogg
130129 03:11:46 5 [1]: Scanning hogg C:/Program Files (x86)/Steam/steamapps/common/Star Trek Online/Star Trek Online/Live/piggs/bins.hogg
130129 03:11:46 6 [1]: Scanning hogg C:/Program Files (x86)/Steam/steamapps/common/Star Trek Online/Star Trek Online/Live/piggs/character.hogg
130129 03:11:46 7 [1]: Scanning hogg C:/Program Files (x86)/Steam/steamapps/common/Star Trek Online/Star Trek Online/Live/piggs/object.hogg
130129 03:11:46 8 [1]: Scanning hogg C:/Program Files (x86)/Steam/steamapps/common/Star Trek Online/Star Trek Online/Live/piggs/sound.hogg
130129 03:11:46 9 [1]: Scanning hogg C:/Program Files (x86)/Steam/steamapps/common/Star Trek Online/Star Trek Online/Live/piggs/texture3.hogg
130129 03:11:46 10 [1]: Scanning hogg C:/Program Files (x86)/Steam/steamapps/common/Star Trek Online/Star Trek Online/Live/piggs/texture2.hogg
130129 03:11:46 11 [1]: Scanning hogg C:/Program Files (x86)/Steam/steamapps/common/Star Trek Online/Star Trek Online/Live/piggs/texture.hogg
130129 03:11:46 12 [1]: Scanning hogg C:/Program Files (x86)/Steam/steamapps/common/Star Trek Online/Star Trek Online/Live/piggs/data.hogg
130129 03:11:47 13 [1]: Scanning hogg C:/Program Files (x86)/Steam/steamapps/common/Star Trek Online/Star Trek Online/Live/piggs/exes.hogg
130129 03:11:47 14 [1]: HTTP patching connected to stohttppatch.crypticstudios.com:80
130129 03:11:47 15 [1]: HTTP patching connected to stohttppatch.crypticstudios.com:80
130129 03:11:48 16 [1]: HTTP patching connected to stohttppatch.crypticstudios.com:80
130129 03:11:48 17 [1]: HTTP patching connected to stohttppatch.crypticstudios.com:80
130129 03:11:58 18 [1]: HTTP patching connected to stohttppatch.crypticstudios.com:80
130129 03:22:09 19 [1]: HTTP patching disconnected from stohttppatch.crypticstudios.com:80: socket was shutdown(10054:Connection reset by remote host)
130129 03:22:09 20 [1]: HTTP patching connected to stohttppatch.crypticstudios.com:80
130129 03:22:09 21 [1]: HTTP patching disconnected from stohttppatch.crypticstudios.com:80: socket was shutdown(10054:Connection reset by remote host)
130129 03:22:09 22 [1]: HTTP patching connected to stohttppatch.crypticstudios.com:80
130129 03:23:53 23 [1]: HTTP patching disconnected from stohttppatch.crypticstudios.com:80: socket was shutdown(0:No error)
130129 03:25:25 24 [1]: HTTP patching disconnected from stohttppatch.crypticstudios.com:80: socket was shutdown(10053:Connection reset locally)
130129 03:25:25 25 [1]: HTTP patching disconnected from stohttppatch.crypticstudios.com:80: socket was shutdown(10053:Connection reset locally)
130129 03:25:25 26 [1]: HTTP patching disconnected from stohttppatch.crypticstudios.com:80: socket was shutdown(10053:Connection reset locally)
130129 03:25:25 27 [1]: HTTP patching disconnected from stohttppatch.crypticstudios.com:80: socket was shutdown(10053:Connection reset locally)
130129 03:25:25 28 [1] ESC : Error: The patchclientlib is internally recording error code : 14\nThe connection to the server was lost - unexpectedly disconnected
Its a hardware issue and the timing is just bad.