test content
  • Games
  • Social
  • Arc News
  • Support
  • Zen
What is the Arc Client?
Install Arc
Forums > Home› Support› PC, Network, and Other Technical Issues› Windows and General: PC, Network, and Other Technical Issues

Game unplayable with rubberbanding and DCs

cptlankfordcptlankford Member Posts: 0 Arc User
edited October 2013 in Windows and General: PC, Network, and Other Technical Issues
I can't tell you how many times I have been knocked off the servers today. Yes i am frustrated but I know ranting about it won't help. I am in the northwest part of South Carolina and have AT&T U-verse service. Here are my test results as outlined in your forum sticky.

Be advised that this is the first time I have had ANY issue with connecting to the game.

CMD.exe Test:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\system32>tracert patchserver.crypticstudios.com

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

1 2 ms 2 ms 1 ms homeportal [192.168.1.254]
2 33 ms 28 ms 27 ms 99-26-244-3.lightspeed.gnvlsc.sbcglobal.net [99.
26.244.3]
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 27 ms 27 ms 28 ms 72.157.40.148
7 43 ms 37 ms 36 ms 12.81.44.58
8 37 ms 36 ms 36 ms 65.83.239.94
9 37 ms 36 ms 36 ms 12.81.34.5
10 48 ms 50 ms 36 ms 12.81.104.175
11 37 ms 44 ms 40 ms 12.81.46.3
12 38 ms 40 ms 38 ms 12.81.56.6
13 37 ms 36 ms 36 ms 12.81.56.15
14 38 ms 38 ms 41 ms 74.175.192.58
15 51 ms 51 ms 50 ms cr2.rlgnc.ip.att.net [12.123.152.110]
16 50 ms 51 ms 51 ms cr1.wswdc.ip.att.net [12.122.3.170]
17 48 ms 48 ms 47 ms gar13.n54ny.ip.att.net [12.122.81.245]
18 88 ms 87 ms 91 ms 192.205.37.106
19 92 ms 93 ms 91 ms be2177.ccr22.dca01.atlas.cogentco.com [154.54.41
.206]
20 56 ms 54 ms 56 ms be2151.mpd22.jfk02.atlas.cogentco.com [154.54.40
.74]
21 61 ms 62 ms 62 ms be2095.ccr21.bos01.atlas.cogentco.com [154.54.30
.38]
22 62 ms 62 ms 62 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42
]
23 67 ms 70 ms 71 ms 38.111.40.114
24 61 ms 61 ms 64 ms 208.95.185.41

Trace complete.

C:\Windows\system32>

Nettest Results:

contacting nettest server..
Local IP: 99.26.247.0
Ping: 100.0 msec
Port: 80: 370 KB/sec 18 KB/sec 394 KB/sec 500
Port: 80: 630 KB/sec 21 KB/sec 666 KB/sec 500
Port: 443: 590 KB/sec 19 KB/sec 622 KB/sec 500
Port: 443: 672 KB/sec 22 KB/sec 710 KB/sec 500
Port: 7255: 637 KB/sec 20 KB/sec 672 KB/sec 500
Port: 7255: 602 KB/sec 19 KB/sec 635 KB/sec 500
Port: 7003: 578 KB/sec 18 KB/sec 610 KB/sec 500
Port: 7003: 685 KB/sec 22 KB/sec 723 KB/sec 500
Port: 7202: 694 KB/sec 22 KB/sec 733 KB/sec 500
Port: 7202: 574 KB/sec 18 KB/sec 606 KB/sec 500
Port: 7499: 714 KB/sec 23 KB/sec 754 KB/sec 500
Port: 7499: 599 KB/sec 19 KB/sec 634 KB/sec 500
Port: 80: 603 KB/sec 19 KB/sec 637 KB/sec 500
Idle NIC bandwidth Send: 0 KB/sec Recv: 0 KB/sec
hit return to exit

I hope to resolve this issue soon if in fact it is on your end. If not then lets hope AT&T has a weekend hotline :(

edit: I would also like to add that i did try resetting my IP address (per the sticky instructions) and while it did work beautifully, the results only lasted about 20 minutes before the problem came back same as it was before.
Post edited by cptlankford on

Comments

  • linyivelinyive Member Posts: 1,086 Arc User
    edited October 2013
    I am currently on my second reinstall. When I got down to the end of the first install, I encountered some type of issue. I wonder if they are related. I am located in the Boston area.
  • grouchyotakugrouchyotaku Member Posts: 0 Arc User
    edited October 2013
    cptlankford wrote: »

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

    1 2 ms 2 ms 1 ms homeportal [192.168.1.254]
    2 33 ms 28 ms 27 ms 99-26-244-3.lightspeed.gnvlsc.sbcglobal.net [99.
    26.244.3]
    3 * * * Request timed out.
    4 * * * Request timed out.
    5 * * * Request timed out.
    6 27 ms 27 ms 28 ms 72.157.40.148
    7 43 ms 37 ms 36 ms 12.81.44.58
    8 37 ms 36 ms 36 ms 65.83.239.94
    9 37 ms 36 ms 36 ms 12.81.34.5
    10 48 ms 50 ms 36 ms 12.81.104.175
    11 37 ms 44 ms 40 ms 12.81.46.3
    12 38 ms 40 ms 38 ms 12.81.56.6
    13 37 ms 36 ms 36 ms 12.81.56.15
    14 38 ms 38 ms 41 ms 74.175.192.58
    15 51 ms 51 ms 50 ms cr2.rlgnc.ip.att.net [12.123.152.110]
    16 50 ms 51 ms 51 ms cr1.wswdc.ip.att.net [12.122.3.170]
    17 48 ms 48 ms 47 ms gar13.n54ny.ip.att.net [12.122.81.245]
    18 88 ms 87 ms 91 ms 192.205.37.106
    19 92 ms 93 ms 91 ms be2177.ccr22.dca01.atlas.cogentco.com [154.54.41
    .206]
    20 56 ms 54 ms 56 ms be2151.mpd22.jfk02.atlas.cogentco.com [154.54.40
    .74]
    21 61 ms 62 ms 62 ms be2095.ccr21.bos01.atlas.cogentco.com [154.54.30
    .38]
    22 62 ms 62 ms 62 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42
    ]
    23 67 ms 70 ms 71 ms 38.111.40.114
    24 61 ms 61 ms 64 ms 208.95.185.41

    Trace complete.

    C:\Windows\system32>

    Nettest Results:

    contacting nettest server..
    Local IP: 99.26.247.0
    Ping: 100.0 msec
    Port: 80: 370 KB/sec 18 KB/sec 394 KB/sec 500
    Port: 80: 630 KB/sec 21 KB/sec 666 KB/sec 500
    Port: 443: 590 KB/sec 19 KB/sec 622 KB/sec 500
    Port: 443: 672 KB/sec 22 KB/sec 710 KB/sec 500
    Port: 7255: 637 KB/sec 20 KB/sec 672 KB/sec 500
    Port: 7255: 602 KB/sec 19 KB/sec 635 KB/sec 500
    Port: 7003: 578 KB/sec 18 KB/sec 610 KB/sec 500
    Port: 7003: 685 KB/sec 22 KB/sec 723 KB/sec 500
    Port: 7202: 694 KB/sec 22 KB/sec 733 KB/sec 500
    Port: 7202: 574 KB/sec 18 KB/sec 606 KB/sec 500
    Port: 7499: 714 KB/sec 23 KB/sec 754 KB/sec 500
    Port: 7499: 599 KB/sec 19 KB/sec 634 KB/sec 500
    Port: 80: 603 KB/sec 19 KB/sec 637 KB/sec 500
    Idle NIC bandwidth Send: 0 KB/sec Recv: 0 KB/sec
    hit return to exit

    .....

    Now assuming that there are no dropped packets, your 'Trace Route' and 'Net Test' statistics are actually pretty good...

    Now I haven't had and disconnects from my connection from the Silicon Valley, so we can assume that there is nothing wrong with the STO Servers, and there is a suspicious increase in latency on the gateway between ATT and Cogent which could be a indication of localized network congestion...

    Unfortunately, neither 'Net Test' or 'Trace Route' are good tools for diagnosing dropped packets, and since you are having problems, we can assume you are suffering from excessive packet drop somewhere along the route between your ISP and the STO servers.

    You could try googling around for a better tool to diagnose packet drop, or you can contact your ISP and ask them to help diagnose a suspected packet drop issue connecting to the STO servers. If your problems are being caused by dropped packets, then this is a ISP issue, and only the ISP can correct the problem. And packet drop issues are usually intermittent in nature, and are usually associated with heavy network traffic load...
  • cptlankfordcptlankford Member Posts: 0 Arc User
    edited October 2013
    I used the cmd.exe to ping the patch server. I hope that was the correct server to ping since I dont know another one to test with. Anyway I pinged in 100 times which was probably overkill but here are the results. Now the game is actually running quite well for me this morning but as I write this it is already slowing down and popping up that server timeout message at the top of the screen so I don't know if it is going to revert to an unplayable state as the day goes on or not. It looks like it is probably traffic congestion causing the issue but I wanted to update the post in case there is anything cryptic can do to help.

    CMD.EXE ping test to patchserver.crypticstudios.com:

    C:\Windows\system32>ping -n 100 patchserver.crypticstudios.com

    Pinging patchserver.crypticstudios.com [208.95.185.41] with 32 bytes of data:
    Reply from 208.95.185.41: bytes=32 time=70ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=87ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=141ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=60ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=149ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=69ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=62ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=80ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=96ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=75ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=104ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=60ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=60ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=96ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=69ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=63ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=65ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=115ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=88ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=98ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=65ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=87ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=66ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=123ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=122ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=83ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=132ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=84ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=62ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=93ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=162ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=70ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=73ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=89ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=114ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=92ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=66ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=129ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=99ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=81ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=78ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=88ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=67ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=60ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=91ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=72ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=74ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=69ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=96ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=69ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=98ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=89ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=84ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=76ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=74ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=78ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=80ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=86ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=61ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=83ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=88ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=75ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=62ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=93ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=60ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=66ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=69ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=97ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=87ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=71ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=77ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=61ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=67ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=71ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=61ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=114ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=67ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=64ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=89ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=71ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=81ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=61ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=92ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=112ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=104ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=87ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=106ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=84ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=106ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=64ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=115ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=87ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=79ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=62ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=60ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=63ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=112ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=70ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=62ms TTL=44
    Reply from 208.95.185.41: bytes=32 time=111ms TTL=44

    Ping statistics for 208.95.185.41:
    Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 60ms, Maximum = 162ms, Average = 84ms

    C:\Windows\system32>
  • cptlankfordcptlankford Member Posts: 0 Arc User
    edited October 2013
    Well i lost access to the game again about 3 hours ago. Same problem as before only even worse. I can't even log in now. I am pretty sure its a connection issue somewhere along the line from me to the server. I am also pretty sure it is not an issue on Cryptic's end but I figured I'd post an update anyways, to see if anyone had any advice. here is the last CMD.exe ping test results to the patch server.

    Ping statistics for 208.95.185.41:
    Packets: Sent = 1000, Received = 863, Lost = 137 (13% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 60ms, Maximum = 390ms, Average = 114ms

    C:\Windows\system32>

    I will be calling AT&T in the morning to see if they have any information but from what I can tell it may or may not be an issue with them but an issue with a connection somewhere past their network.
  • paxfederaticapaxfederatica Member Posts: 1,496 Arc User
    edited October 2013
    I also have AT&T U-verse (in the Milwaukee, WI area) and am having the same issue now. The launcher will take my password, but then stalls when checking the patch server.

    Earlier this afternoon I was able to log in, but was experiencing severe rubberbanding.

    Here are my ping results:
    Pinging patchserver.crypticstudios.com [208.95.185.41] with 32 bytes of data:
    Reply from 208.95.185.41: bytes=32 time=95ms TTL=49
    Reply from 208.95.185.41: bytes=32 time=92ms TTL=49
    Request timed out.
    Reply from 208.95.185.41: bytes=32 time=85ms TTL=49
    Reply from 208.95.185.41: bytes=32 time=85ms TTL=49
    Reply from 208.95.185.41: bytes=32 time=89ms TTL=49
    Reply from 208.95.185.41: bytes=32 time=88ms TTL=49
    Request timed out.
    Reply from 208.95.185.41: bytes=32 time=88ms TTL=49
    Reply from 208.95.185.41: bytes=32 time=81ms TTL=49
    Reply from 208.95.185.41: bytes=32 time=80ms TTL=49
    Reply from 208.95.185.41: bytes=32 time=87ms TTL=49
    Reply from 208.95.185.41: bytes=32 time=86ms TTL=49
    Reply from 208.95.185.41: bytes=32 time=91ms TTL=49
    Request timed out.
    Reply from 208.95.185.41: bytes=32 time=89ms TTL=49
    Request timed out.
    Reply from 208.95.185.41: bytes=32 time=87ms TTL=49
    Reply from 208.95.185.41: bytes=32 time=88ms TTL=49
    Request timed out.
    Reply from 208.95.185.41: bytes=32 time=81ms TTL=49
    Reply from 208.95.185.41: bytes=32 time=84ms TTL=49
    Request timed out.
    Reply from 208.95.185.41: bytes=32 time=92ms TTL=49
    Reply from 208.95.185.41: bytes=32 time=89ms TTL=49

    Ping statistics for 208.95.185.41:
    Packets: Sent = 25, Received = 19, Lost = 6 (24% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 80ms, Maximum = 95ms, Average = 87ms

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

    1 4 ms 1 ms 1 ms homeportal [192.168.1.254]
    2 56 ms 24 ms 25 ms 99-122-68-3.lightspeed.milwwi.sbcglobal.net [99.122.68.3]
    3 * * * Request timed out.
    4 26 ms 24 ms 27 ms 12.83.79.141
    5 49 ms 50 ms 51 ms cgcil02jt.ip.att.net [12.122.81.21]
    6 98 ms 92 ms 91 ms be2000.ccr21.ord03.atlas.cogentco.com [154.54.12.85]
    7 101 ms 95 ms * be2004.mpd22.ord01.atlas.cogentco.com [154.54.5.9]
    8 * * 93 ms be2140.ccr22.bos01.atlas.cogentco.com [154.54.43.186]
    9 116 ms 115 ms 100 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42]
    10 92 ms * 89 ms 38.111.40.114
    11 86 ms * * 208.95.185.41
    12 * 91 ms * 208.95.185.41
    13 * * 91 ms 208.95.185.41

    Trace complete.

    Most worrisome of all, nettest wouldn't even run - it timed out almost immediately after launch.

    Update: Late Sunday night, I was able to log in and work in the Foundry with no issues. Hopefully that means whatever bottleneck was causing the connection issues has gone away.
    STAR TREK ONLINE: THE PEACEMAKERS
    My Foundry missions | My STO Wiki page | My Twitter home page
  • ccintronccintron Member Posts: 0 Arc User
    edited October 2013
    I have also been having issues with STO overall for the past couple of weeks. Rubberbanding and Lag (where everything on screen freezes for a few seconds) making the game unplayable. After one of these pause cycles its not uncommon to find my ship has taken a ton of damage during the pause.

    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


    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.
  • grouchyotakugrouchyotaku Member Posts: 0 Arc User
    edited October 2013
    ccintron wrote: »
    ...
    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...
    ccintron wrote: »

    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...
  • ccintronccintron Member Posts: 0 Arc User
    edited October 2013
    grouchyotaku wrote: »
    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...


    How do I explain this to ISP support? Because calling them is the equivalent to beating my head against a wall. Even speaking to a "supervisor" all I get is... "lets test your speed" and they give me the phone version of a deer in headlights when I try and get them back on subject of the routing issue.
  • grouchyotakugrouchyotaku Member Posts: 0 Arc User
    edited October 2013
    ccintron wrote: »
    How do I explain this to ISP support? Because calling them is the equivalent to beating my head against a wall. Even speaking to a "supervisor" all I get is... "lets test your speed" and they give me the phone version of a deer in headlights when I try and get them back on subject of the routing issue.

    Just tell them you need to have them diagnose a problem with PACKET DROP on the connection to the STO servers...
  • jbmonroejbmonroe Member Posts: 809 Arc User
    edited October 2013
    grouchyotaku wrote: »
    Just tell them you need to have them diagnose a problem with PACKET DROP on the connection to the STO servers...

    I sent the results of my trace to both Brighthouse and Cogent. I'm not expecting much to happen--particularly since they'll just tag it as "another whining gamer complaint."
    boldly-watched.png
  • ccintronccintron Member Posts: 0 Arc User
    edited October 2013
    jbmonroe wrote: »
    I sent the results of my trace to both Brighthouse and Cogent. I'm not expecting much to happen--particularly since they'll just tag it as "another whining gamer complaint."

    I did the same as I too have Brighthouse. After being bounced around multiple tech support people. the last finally took took the info and gave me a ticket number. I'm not expecting this to be fixed short of Cogent deciding to stop being terrible. Aggravating as this started in Oct, up until then there were no issues. I also don't have this issue connecting to anything but STO. :(
  • grouchyotakugrouchyotaku Member Posts: 0 Arc User
    edited October 2013
    ccintron wrote: »
    I did the same as I too have Brighthouse. After being bounced around multiple tech support people. the last finally took took the info and gave me a ticket number. I'm not expecting this to be fixed short of Cogent deciding to stop being terrible. Aggravating as this started in Oct, up until then there were no issues. I also don't have this issue connecting to anything but STO. :(

    Its most likely not being caused by Cogent Communications, as they provide more then enough bandwidth to support their hosted services (which includes Netflix, which continues to have a logarithmic growth rate in network bandwidth use...) Its more likely that its Road Runner who hasn't expanded their gateway bandwidth to keep up with growing demand from their subscribers... (And after all, Road Runner isn't making any $$$ from Netflix traffic, so they really don't have much motivation to do so, until enough subscribers start complaining...)
  • inkrunnerinkrunner Member Posts: 407 Arc User
    edited October 2013
    I live in Northwestern South Carolina as well, and I have AT&T U-Verse.

    I'm having the same exact issues you are.
    2iBFtmg.png
  • lincolninspacelincolninspace Member Posts: 1,843 Arc User
    edited October 2013
    ccintron wrote: »
    I have also been having issues with STO overall for the past couple of weeks. Rubberbanding and Lag (where everything on screen freezes for a few seconds) making the game unplayable. After one of these pause cycles its not uncommon to find my ship has taken a ton of damage during the pause.

    Had the same problem tonight.
    A TIME TO SEARCH: ENTER MY FOUNDRY MISSION at the RISA SYSTEM
    Parallels: my second mission for Fed aligned Romulans.
  • ccintronccintron Member Posts: 0 Arc User
    edited October 2013
    Working with Brighthouse to try and resolve. They have been testing routing to 208.95.185.41 and aren't seeing any issue.

    They've asked if I can get Perfect Worlds to run a trace back to my ip to see if the problem is the return path which is not always identical.

    Thus far no word back from Perfect Worlds on getting me that information.

    Logged in to see and there is still the consistent pause very 10 - 12 seconds. However as I had tried a clean install (which took forever to install at an average of 30kbs) entering a system tends to prompt a download before actually getting into the system.

    Each of these system mini downloads were listing 20kbs in the top left corner of the loading screen.

    I'm starting to wonder if this may not be the real issue, we aren't getting data BACK from the STO server fast enough.
  • captbrack814captbrack814 Member Posts: 7 Arc User
    edited October 2013
    Ever since the last patch a few nights ago I can't stay in any non-sector map for more than a few seconds without getting "server not responding" messages and eventually getting booted. It's become a test of patience to just get in and get myself back out into sector space. While in sector space the game runs normally. Every other service I use online (streaming, other MMOs) run just fine, it's only this game and only when I enter a combat space zone or ground zone. It's getting ridiculous, and I can't see how it has anything to do with my connection. I think their latest patch must've broke something.

    EDIT - Here's my tracert results

    Microsoft Windows [Version 6.1.7601]

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

    1 29 ms 7 ms 10 ms 10.0.0.1
    2 16 ms 35 ms 29 ms 73.96.20.1
    3 15 ms 18 ms 33 ms te-0-0-0-11-ur09.everett.wa.seattle.comcast.net
    [68.86.98.161]
    4 21 ms 15 ms 32 ms ae-29-0-ar03.burien.wa.seattle.comcast.net [69.1
    39.164.213]
    5 25 ms 31 ms 18 ms ae-2-0-ar03.seattle.wa.seattle.comcast.net [68.8
    6.177.146]
    6 46 ms 27 ms 23 ms he-1-4-0-0-10-cr01.seattle.wa.ibone.comcast.net
    [68.86.94.237]
    7 24 ms 18 ms 14 ms be-11-pe03.seattle.wa.ibone.comcast.net [68.86.8
    4.78]
    8 * 62 ms 67 ms as174.seattle.wa.ibone.comcast.net [66.208.228.1
    10]
    9 65 ms 65 ms 49 ms be2085.ccr21.slc01.atlas.cogentco.com [154.54.2.
    198]
    10 61 ms 81 ms 47 ms be2127.ccr22.den01.atlas.cogentco.com [154.54.25
    .69]
    11 93 ms 68 ms 70 ms be2129.mpd21.mci01.atlas.cogentco.com [154.54.26
    .114]
    12 100 ms 115 ms 97 ms be2157.ccr22.ord01.atlas.cogentco.com [154.54.6.
    118]
    13 149 ms 149 ms 146 ms be2137.ccr21.bos01.atlas.cogentco.com [154.54.43
    .194]
    14 140 ms 160 ms 146 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
    134]
    15 101 ms 96 ms 99 ms 38.111.40.114
    16 108 ms 99 ms 109 ms 208.95.185.41

    Trace complete.

    Everything but the last three cogentco pings are nominal.

    EDIT 2: Ran the ispconfig/renew command, seems to have worked. Nevermind!
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    "Go into battle expecting to die. Then, fight like you want to live." - Huren Hewnoak
Sign In or Register to comment.