View Single Post
Commander
Join Date: Jun 2012
Posts: 441
# 234
12-08-2012, 11:08 PM
Quote:
Originally Posted by azntrigboi View Post
I'm having the same issues here. The game will just be completely unresponsive or have massive rubberbanding. By the end of it, I usually just get disconnected. It's making the game pretty much unplayable.

The results of the two tests are below.

Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:


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 7 ms 23 ms 8 ms 96.120.14.113
3 8 ms 9 ms * te-6-7-ur08.sacramento.ca.ccal.comcast.net [69.1
39.197.245]
4 8 ms 9 ms 10 ms te-0-2-0-0-ar03.sacramento.ca.sacra.comcast.net
[68.87.200.189]
5 10 ms 10 ms 11 ms pos-0-1-0-0-cr01.sacramento.ca.ibone.comcast.net
[68.86.90.133]
6 16 ms 15 ms 15 ms pos-0-9-0-0-cr01.sanjose.ca.ibone.comcast.net [6
8.86.85.181]
7 15 ms 13 ms 13 ms pos-0-2-0-0-pe01.529bryant.ca.ibone.comcast.net
[68.86.87.6]
8 55 ms 55 ms 54 ms te0-7-0-12.ccr21.sjc04.atlas.cogentco.com [154.5
4.11.109]
9 63 ms 47 ms 48 ms te0-0-0-6.ccr21.sfo01.atlas.cogentco.com [154.54
.7.173]
10 56 ms 64 ms 60 ms te0-3-0-1.ccr22.mci01.atlas.cogentco.com [154.54
.6.41]
11 71 ms 69 ms 70 ms te0-3-0-7.mpd22.ord01.atlas.cogentco.com [154.54
.84.86]
12 100 ms 103 ms 94 ms te0-1-0-6.ccr21.bos01.atlas.cogentco.com [154.54
.43.190]
13 165 ms 216 ms 207 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
134]

14 94 ms 107 ms 91 ms 38.111.40.114
15 91 ms 95 ms 91 ms 208.95.185.41

contacting nettest server..
Local IP: -----
Ping: 176.5 msec
Port: 80: 155 KB/sec 10 KB/sec 167 KB/sec 500
Port: 80: 377 KB/sec 17 KB/sec 399 KB/sec 500
Port: 443: 39 KB/sec 6 KB/sec 131 KB/sec 500
Port: 443: 177 KB/sec 10 KB/sec 196 KB/sec 500
Port: 7255: 474 KB/sec 30 KB/sec 1333 KB/sec 500
Port: 7255: 528 KB/sec 29 KB/sec 556 KB/sec 500
Port: 7003: 109 KB/sec 11 KB/sec 117 KB/sec 500
Port: 7003: 155 KB/sec 11 KB/sec 168 KB/sec 500
Port: 7202: timed out
Port: 7202: 474 KB/sec 20 KB/sec 503 KB/sec 500
Port: 7499: 462 KB/sec 37 KB/sec 1561 KB/sec 500
Port: 7499: 573 KB/sec 24 KB/sec 606 KB/sec 500
Port: 80: 507 KB/sec 15 KB/sec 537 KB/sec 500
Idle NIC bandwidth Send: 0 KB/sec Recv: 0 KB/sec
Bolded hop in your traceroute has been shown to be problematic on several traces by several players (I['ve posted this after having run more than a dozen traces over several times of day on the global forums). Sandy hit right before S7 went live, so I wouldn't be the least bit surprised to be shown there was a major bottleneck in that relay.

Also, your nettest is extremely spotty on many ports. A hardware reset might clear that up, if you get those same nettest results after a full hardware reset/power cycle, a talk with your ISP may be in order.

If you installed via the website (as opposed to having had a boxed copy of the game some time ago), make sure PMB is not installed/not running on your PC. PMB runs as a limited P2P client, and will allow other users to download the STO installer from your PC, as well as any other game installer that utilizes PMB for downloading, which will in turn eat up bandwidth like Pac-Man eating pellets.

And for the sake of security, hide your local IP in your nettest results....

Quote:
Originally Posted by adeonhawkwood View Post
I'm having exactly the same problem. It started on Friday. Sometimes the game will be fine but then it gets into a setup where it basically stops responding to commands. I (generally) seem to still be receiving data from the server regarding my environment (i.e. other players and NPCs keep moving on my screen) and the chat system continues to work fine but any commands I send take several minutes to show a response.

I ran the tests in the OP and the tracert was fine the nettest results were similar to those reported by others.

I don't think that this is an ISP problem unless we're all on the same ISP, I'm using Comcast Cable in California.

Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:

1 2 ms 2 ms 2 ms 192.168.1.1
2 47 ms 25 ms 29 ms 24.5.136.1
3 11 ms 10 ms 11 ms te-8-3-ur06.pleasanton.ca.sfba.comcast.net [68.8
7.196.101]
4 22 ms 21 ms 22 ms te-0-2-0-7-ar01.oakland.ca.sfba.comcast.net [69.
139.198.30]
5 17 ms 23 ms 25 ms te-0-1-0-5-cr01.seattle.wa.ibone.comcast.net [68
.86.90.121]
6 25 ms 22 ms 19 ms pos-0-6-0-0-cr01.sanjose.ca.ibone.comcast.net [6
8.86.86.202]
7 17 ms 18 ms 19 ms pos-0-5-0-0-pe01.529bryant.ca.ibone.comcast.net
[68.86.88.2]
8 64 ms 65 ms 64 ms te0-7-0-0.ccr21.sjc04.atlas.cogentco.com [154.54
.11.185]
9 66 ms 66 ms 71 ms te0-0-0-6.ccr21.sfo01.atlas.cogentco.com [154.54
.7.173]
10 62 ms * 65 ms te0-4-0-3.mpd22.mci01.atlas.cogentco.com [154.54
.45.85]
11 79 ms * 74 ms te0-3-0-7.mpd22.ord01.atlas.cogentco.com [154.54
.84.86]
12 106 ms 132 ms 103 ms te0-1-0-1.ccr22.bos01.atlas.cogentco.com [154.54
.6.21]
13 104 ms 104 ms 112 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
134]
14 125 ms 124 ms 122 ms 38.111.40.114
15 109 ms 104 ms 108 ms 208.95.185.41

Trace complete.

contacting nettest server..
Local IP: -------
Ping: 96.8 msec
Port: 80: 123 KB/sec 0 KB/sec 0 KB/sec 500
Port: 80: 371 KB/sec 0 KB/sec 0 KB/sec 500
Port: 443: 389 KB/sec 0 KB/sec 0 KB/sec 500
Port: 443: 427 KB/sec 0 KB/sec 0 KB/sec 500
Port: 7255: 382 KB/sec 0 KB/sec 0 KB/sec 500
Port: 7255: 446 KB/sec 0 KB/sec 0 KB/sec 500
Port: 7003: 484 KB/sec 0 KB/sec 0 KB/sec 500
Port: 7003: 413 KB/sec 0 KB/sec 0 KB/sec 500
Port: 7202: 496 KB/sec 0 KB/sec 0 KB/sec 500
Port: 7202: 419 KB/sec 0 KB/sec 0 KB/sec 500
Port: 7499: 375 KB/sec 0 KB/sec 0 KB/sec 500
Port: 7499: 403 KB/sec 0 KB/sec 0 KB/sec 500
Port: 80: 368 KB/sec 0 KB/sec 0 KB/sec 500
Idle NIC bandwidth Send: 0 KB/sec Recv: 0 KB/sec
hit return to exit
You've got a couple of partial misses in your trace (indicated by the asterisks, each hop on the trace receives three packets). That might explain the bit of lag time in your commands, but I can't be completely sure. The last few hops are a little high but not completely problematic.

Same as the above poster too: Unless you wish to unwittingly invite hackers into your PC, block out your local IP in your nettest results
****
Lagging, D/Cing, or rubberbanding? Here's some help.

Current ships: A lot. RTR 15 National Championships....and counting

Last edited by lewstelamon01; 12-09-2012 at 12:30 AM.