test content
What is the Arc Client?
Install Arc

Random Disconnects and Intermittant Rubberbanding aka (Lag/Latency) Issues

SystemSystem Member, NoReporting Posts: 178,019 Arc User
So I am running Window's Vista and have been experiencing various lag/latency issues intermittently for the past month or so. Recently I am experiencing random disconnects while on the US Proxy server as well. I had tried the US Proxy Server recently and all my issues vanished with latency and lag until today when I began experiencing lag and latency issues. I have checked with my ISP and modem errors and SNR are all within normal operating parameters. I would like some help from Cryptic diagnosing the cause of this issue, I have restarted the modem and router in both Proxy and No Proxy scenarios as well. I have also tested in low graphics and medium graphics mode to no effect, and experienced no issues until today on the US Proxy in medium graphics mode. Perhaps Cryptic Operations would be willing to perform a Wireshark on me during high peak usage times to help determine the cause of the issue. I have included the info from various network tests below.


Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

nettest
contacting nettest server..
Local IP: 68.148.xx.xx
Ping: 111.1 msec
Port: 80: 176 KB/sec 13 KB/sec 189 KB/sec 500
Port: 80: 323 KB/sec 19 KB/sec 344 KB/sec 500
Port: 443: 629 KB/sec 28 KB/sec 666 KB/sec 500
Port: 443: 627 KB/sec 19 KB/sec 660 KB/sec 500
Port: 7255: 575 KB/sec 19 KB/sec 605 KB/sec 500
Port: 7255: 607 KB/sec 28 KB/sec 644 KB/sec 500
Port: 7003: 549 KB/sec 24 KB/sec 582 KB/sec 500
Port: 7003: 259 KB/sec 18 KB/sec 275 KB/sec 500
Port: 7202: 554 KB/sec 24 KB/sec 587 KB/sec 500
Port: 7202: 547 KB/sec 21 KB/sec 576 KB/sec 500
Port: 7499: 168 KB/sec 11 KB/sec 179 KB/sec 500
Port: 7499: 421 KB/sec 17 KB/sec 447 KB/sec 500
Port: 80: 552 KB/sec 16 KB/sec 582 KB/sec 500
Idle NIC bandwidth Send: 2 KB/sec Recv: 2 KB/sec
hit return to exit


tracert 208.95.184.170

Tracing route to 208.95.184.170 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms PETER-CANADAS- [10.0.1.1]
2 * * * Request timed out.
3 11 ms 10 ms 10 ms rc1we-tge0-0-1-0-6.ed.shawcable.net [64.59.189.50]
4 25 ms 27 ms 29 ms rc2ch-pos14-0-0.il.shawcable.net [66.163.76.62]
5 51 ms 51 ms 50 ms rc1sh-pos13-0.mt.shawcable.net [66.163.76.73]
6 * 64 ms 63 ms rc1hu-pos2-0-0.ny.shawcable.net [66.163.76.54]
7 66 ms 90 ms 68 ms cr2-nyiix-peer.nym009.internap.net [198.32.160.185]
8 81 ms 64 ms 64 ms cr2-cr1.nym009.internap.net [66.79.146.198]
9 70 ms 71 ms 71 ms bsn006-nym009-9-cr1.bsn006.internap.net [66.79.158.9]
10 * 69 ms 99 ms bsn004-bsn006-792-mpr1.bsn004.internap.net [66.79.145.34]
11 75 ms 74 ms 71 ms border12.te8-1-bbnet2.bsn.pnap.net [63.251.128.105]
12 83 ms 88 ms 89 ms cryptic-1.border12.bsn.pnap.net [63.251.130.10]
13 82 ms 83 ms 113 ms 208.95.184.170

Trace complete.

tracert 208.95.184.170 >042710NetworkTrace

tracert 208.95.184.108 >042710NetworkTraceProxy

tracert us1 >042710NetworkTraceProxykTraceProxy1

tracert 208.95.184.108

Tracing route to 208.95.184.108 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms PETER-CANADAS- [10.0.1.1]
2 * * * Request timed out.
3 11 ms 11 ms 13 ms rc1we-tge0-0-1-0-6.ed.shawcable.net [64.59.189.50]
4 34 ms 40 ms 33 ms rc2ch-pos2-0-0.il.shawcable.net [66.163.77.65]
5 * 53 ms 72 ms rc1sh-pos15-0.mt.shawcable.net [66.163.76.221]
6 63 ms 64 ms 63 ms rc1hu-pos2-0-0.ny.shawcable.net [66.163.76.54]
7 68 ms 66 ms * cr2-nyiix-peer.nym009.internap.net [198.32.160.185]
8 64 ms 63 ms 65 ms cr2-cr1.nym009.internap.net [66.79.146.198]
9 70 ms 71 ms 70 ms bsn006-nym009-9-cr1.bsn006.internap.net [66.79.158.9]
10 70 ms 82 ms 71 ms bsn004-bsn006-792-mpr1.bsn004.internap.net [66.79.145.34]
11 69 ms 69 ms 82 ms border12.te8-1-bbnet2.bsn.pnap.net [63.251.128.105]
12 94 ms 89 ms 89 ms cryptic-1.border12.bsn.pnap.net [63.251.130.10]
13 73 ms 72 ms 78 ms 208.95.184.108

Trace complete.

ping 208.95.184.108

Pinging 208.95.184.108 with 32 bytes of data:
Reply from 208.95.184.108: bytes=32 time=74ms TTL=113
Reply from 208.95.184.108: bytes=32 time=75ms TTL=113
Reply from 208.95.184.108: bytes=32 time=73ms TTL=113
Reply from 208.95.184.108: bytes=32 time=72ms TTL=113

Ping statistics for 208.95.184.108:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 72ms, Maximum = 75ms, Average = 73ms

ping 208.95.184.170

Pinging 208.95.184.170 with 32 bytes of data:
Reply from 208.95.184.170: bytes=32 time=82ms TTL=115
Reply from 208.95.184.170: bytes=32 time=82ms TTL=115
Reply from 208.95.184.170: bytes=32 time=83ms TTL=115
Reply from 208.95.184.170: bytes=32 time=82ms TTL=115

Ping statistics for 208.95.184.170:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 82ms, Maximum = 83ms, Average = 82ms

ping 208.95.184.107

Pinging 208.95.184.107 with 32 bytes of data:
Reply from 208.95.184.107: bytes=32 time=83ms TTL=115
Reply from 208.95.184.107: bytes=32 time=81ms TTL=115
Reply from 208.95.184.107: bytes=32 time=82ms TTL=115
Reply from 208.95.184.107: bytes=32 time=90ms TTL=115

Ping statistics for 208.95.184.107:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 81ms, Maximum = 90ms, Average = 84ms
Post edited by Unknown User on

Comments

  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited April 2010
    Same problems.... Awful......
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited April 2010
    Same problems.... Awful......

    Yeah well I'm trying to eliminate issues on my end that would cause i, and determine if its a issueon Cryptic's end for sure. But this real hard to figure out.
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited April 2010
    Use Pingplotter with TCP 7xxx (7xxx being the port that you are on during the latency problems, No Proxy set) for a trend of the server you are having problems playing on. If the lag issue is constant then a 100 or 200 sample run should be sufficient. If it comes and goes you might want to run 1000 samples (2.5 sec interval) while you play.

    http://forums.startrekonline.com/showthread.php?p=2281229#post2281229
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited April 2010
    Use Pingplotter with TCP 7xxx (7xxx being the port that you are on during the latency problems, No Proxy set) for a trend of the server you are having problems playing on. If the lag issue is constant then a 100 or 200 sample run should be sufficient. If it comes and goes you might want to run 1000 samples (2.5 sec interval) while you play.

    http://forums.startrekonline.com/showthread.php?p=2281229#post2281229

    Thank you I will test and report back.
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited April 2010
    Use Pingplotter with TCP 7xxx (7xxx being the port that you are on during the latency problems, No Proxy set) for a trend of the server you are having problems playing on. If the lag issue is constant then a 100 or 200 sample run should be sufficient. If it comes and goes you might want to run 1000 samples (2.5 sec interval) while you play.

    http://forums.startrekonline.com/showthread.php?p=2281229#post2281229

    Is there an easy way to tell which current port number the game is using?
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited April 2010
    the game uses the full range 7000-7500. everytime you transfer maps to a new server you get a random port in that range.
    You can always run a sniffer and packet capture during the game until you disconnect and see the last server a port you were using.
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited April 2010
    PegasusMD wrote:
    the game uses the full range 7000-7500. everytime you transfer maps to a new server you get a random port in that range.
    You can always run a sniffer and packet capture during the game until you disconnect and see the last server a port you were using.

    Work on the issues sidelined for today........so waiting until my ISP fixes the ongoing intermittent issues in the area that it recently discovered in the last 24 hours........sighs and I know its been getting progressively worse since a month ago. We'll see if that fixes my issues after they fix the problem.
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited April 2010
    Same problems here however i found a solution.

    Vista apparently in microsofts endless wisdom, checks every packet that comes into the system from the internet.

    So when i learned about this i had two options go buy windows 7 or get something that would turn this off.

    I downloaded a program for free called Vista Anti-Lag. It turns this off while im playing games. I just start it up hit activate and i go back to the game and it doesn't lag anymore.

    i too thought it was due to the ports not being forwarded in my firewall and worked long and hard to find out just what was happening. Now i know. It's absolutely Vista itself. I would also recommend the program called Game booster its free too and turns off all the unnecessary extra TRIBBLE windows likes to run in the background at all times.
Sign In or Register to comment.