View Single Post
Career Officer
Join Date: Jun 2012
Posts: 2,166
# 8
10-14-2013, 01:41 PM
Quote:
Originally Posted by ccintron View Post
...
At this point I'm not sure if its the routing to the STO server or an issue with the server itself. All I know is that I can download large files from Blizzard, Steam, etc quickly but STO patching took over 12 hours after I deleted the live folder to see if it might be a corrupt file.

My Net Test results

contacting nettest server..
Local IP: 72.188.174.176
Ping: 176.5 msec
Port: 80: 41 KB/sec 2 KB/sec 44 KB/sec 500
Port: 80: 44 KB/sec 2 KB/sec 47 KB/sec 500
Port: 443: 43 KB/sec 2 KB/sec 47 KB/sec 500
Port: 443: 43 KB/sec 2 KB/sec 46 KB/sec 500
Port: 7255: 42 KB/sec 2 KB/sec 46 KB/sec 500
Port: 7255: 39 KB/sec 2 KB/sec 42 KB/sec 500
Port: 7003: 37 KB/sec 2 KB/sec 41 KB/sec 500
Port: 7003: 33 KB/sec 1 KB/sec 35 KB/sec 500
Port: 7202: 35 KB/sec 2 KB/sec 37 KB/sec 500
Port: 7202: 57 KB/sec 2 KB/sec 61 KB/sec 500
Port: 7499: 30 KB/sec 1 KB/sec 32 KB/sec 500
Port: 7499: 32 KB/sec 1 KB/sec 34 KB/sec 500
Port: 80: 41 KB/sec 2 KB/sec 44 KB/sec 500
Idle NIC bandwidth Send: 0 KB/sec Recv: 1 KB/sec
hit return to exit
Now keep in mind that 'Net Test' connects to a diagnostic server on the STO network, not to the STO Servers themselves. If you have issues with the 'Net Test' throughput (values should be in the 300 - 500 range) then that shows you have a Internet Route problem, as the STO Servers are out of the picture here...

Quote:
Originally Posted by ccintron View Post

my trace route results

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 11 ms 8 ms 9 ms ten0-7-0-0.orld51-ser1.bhn.net [72.31.193.210]
4 13 ms 14 ms 17 ms ten0-0-0-2.orld48-car1.bhn.net [71.44.61.86]
5 18 ms 22 ms 23 ms ten0-6-0-8.orld71-car1.bhn.net [72.31.195.174]
6 19 ms 14 ms 15 ms 72-31-193-133.net.bhntampa.com [72.31.193.133]
7 17 ms 18 ms 18 ms 10.bu-ether15.orldfljo00w-bcr00.tbone.rr.com [66
.109.6.98]
8 26 ms 26 ms 26 ms bu-ether18.atlngamq47w-bcr01.tbone.rr.com [66.10
9.1.72]
9 21 ms 22 ms 22 ms ae-1-0.pr0.atl20.tbone.rr.com [66.109.6.177]
10 98 ms 94 ms 95 ms te0-0-0-10.ccr21.atl02.atlas.cogentco.com [154.5
4.12.109]

11 93 ms 92 ms 91 ms be2053.mpd22.atl01.atlas.cogentco.com [154.54.3.
145]
12 99 ms 99 ms * be2169.ccr22.dca01.atlas.cogentco.com [154.54.31
.98]
13 105 ms 104 ms 105 ms be2151.mpd22.jfk02.atlas.cogentco.com [154.54.40
.74]
14 110 ms 108 ms 110 ms be2097.ccr22.bos01.atlas.cogentco.com [154.54.30
.118]
15 108 ms 108 ms 111 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42
]
16 116 ms 109 ms 120 ms 38.111.40.114
17 109 ms 109 ms 109 ms 208.95.185.41

Trace complete.
This shows the same issue as a previous Trace Route output. Since the 'Net Test' results hint that you are suffering from severe packet drop, the 'Trace Route' shows it is most likely occurring on the gateway between the Road Runner backbone and the Cogent backbone. This is a ISP issue, as only the ISP involved can correct this problem...