Announcement

Collapse
No announcement yet.

bad hops to TG server

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • bad hops to TG server

    I keep getting dropped from the server, not because of play, but because of bad hops.

    I don't know if there is anything you can really do about it, but I thought you ought to know about them, as they're right on your front doorstep as it were.

    Code:
    Tracing route to bf2sb.tacticalgamer.com [64.34.161.157]
    over a maximum of 30 hops:
    
      1    <1 ms    <1 ms    <1 ms  192.168.0.1
      2    32 ms    31 ms    31 ms  v-static-145-254.avvanta.com [206.124.145.254]
      3    32 ms    31 ms    31 ms  bord-02-ge-2-0.sttl.isomedia.com [207.115.64.136]
      4   187 ms   187 ms    38 ms  ge-1-9.r00.sttlwa01.us.bb.gin.ntt.net [204.2.144.9]
      5    31 ms    31 ms    31 ms  xe-0.sprint.sttlwa01.us.bb.gin.ntt.net [129.250.8.54]
      6    76 ms    75 ms    75 ms  sl-bb25-chi-5-0.sprintlink.net [144.232.20.84]
      7   110 ms   109 ms   110 ms  sl-bb26-rly-10-0.sprintlink.net [144.232.20.88]
      8   110 ms   109 ms   112 ms  sl-bb25-rly-13-0.sprintlink.net [144.232.14.169]
      9   110 ms   110 ms   109 ms  sl-bb24-rly-12-0.sprintlink.net [144.232.14.149]
     10   110 ms   110 ms   110 ms  sl-st22-ash-5-0.sprintlink.net [144.232.20.155]
     11   109 ms   109 ms   109 ms  144.223.246.178
     12     *        *        *     Request timed out.
     13     *        *        *     Request timed out.
     14   112 ms   108 ms   112 ms  bf2sb.tacticalgamer.com [64.34.161.157]
    
    Trace complete.
    When this happens again, I will post a new tracert if it's any different pathing from this.

    I hope this helps some, as I know others have had the same issue, even if I couldn't find a thread (well, really... I didn't look for one).

    ON EDIT: I forgot to say that this really doesn't impact all that bad, as I can just jump back in, but it is annoying to be in the middle of a great play and have to spend a minute or so getting back in.
    Last edited by MostlyHarmless; 12-11-2007, 12:48 AM. Reason: more info

  • #2
    Re: bad hops to TG server

    and again... same set of bad hops

    Comment


    • #3
      Re: bad hops to TG server

      I've seen the same thing before. It is probably just gateways that don't respond to the trace route. Your ping to the next server doesn't jump really.

      Try running the trace route when the connection is fine, you will probably see the same results.



      Comment


      • #4
        Re: bad hops to TG server

        Barley and Hops?

        Comment


        • #5
          Re: bad hops to TG server

          See, this is why I'm thankful I'm ONE hop from the Datacenter, hence my single-digit ping.
          playing off the TG server feels like we're playing 2142 on easy mode~Fehmart

          I'm going to close my eyes until it's over~Experiment, commenting on my driving

          "Get it up quickly and beat it hard."~Jonan
          I don't get a bonus DVD? My life has lost all meaning.~Zoopy_T

          Comment


          • #6
            Re: bad hops to TG server

            Try using Ping instead. It is entirely possible that the server is passing packets correctly but not responding to Tracert.

            See http://www.more.net/technical/pingtrace.html for more info.
            Retired 6th DB

            Comment


            • #7
              Re: bad hops to TG server

              Originally posted by Wimpinator View Post
              Try using Ping instead. It is entirely possible that the server is passing packets correctly but not responding to Tracert.

              See http://www.more.net/technical/pingtrace.html for more info.
              I find the pingplotter freeware to be handy if you want to get a longitudinal history of your ping and packetloss. http://www.pingplotter.com/freeware.html

              Comment


              • #8
                Re: bad hops to TG server

                Thats a nice util. Here is my graph and this is the good version. I'll try it during the day too and maybe it'll show why I prefer distance weapons always :p




                If you find yourself in a fair fight, then you have obviously failed to plan properly.

                Comment


                • #9
                  Re: bad hops to TG server

                  Question..How do you fix bad hops? :-)

                  Comment


                  • #10
                    Re: bad hops to TG server

                    It depends on where the bad hops are occurring in your connection to the destination server.
                    However, as long as your final destination is not recording any packet loss the bad hops don't actually matter. http://www.nessoft.com/kb/24

                    Unfortunately, even a few seconds of PL at the final destination can cause a disconnect for online gaming, so it's worth identifying where it starts and liasing with your ISP about what you can do about it (probably not much, unless the PL occurs somewhere between your home and the ISP).

                    This following pingplot of 603 pings (pinged every 5 seconds), shows I had 9% packet loss travelling between destinations 3 to 4, but at the final destination only 1% of total packets were lost. Unfortunately, even 1% PL means a disconnect on average once every 50 minutes or so for me... This is an issue somewhere between the exchange and the ISP's central hardware. Not much I can do about it except change ISPs.

                    If you're having specific problems maybe try the Hardware forum.
                    Attached Files
                    Last edited by Nero; 12-13-2007, 04:42 PM.

                    Comment


                    • #11
                      Re: bad hops to TG server

                      Code:
                      Tracing route to bf2sb.tacticalgamer.com [64.34.161.157]
                      over a maximum of 30 hops:
                      
                        1    <1 ms    <1 ms    <1 ms  ba-he-corerouter-cisco-7513-vlan-admin-FastE3-0-
                      0.twcinci.com [10.200.1.1]
                        2    <1 ms     1 ms    <1 ms  cin-dx-fw-n-12-eth1.inf.twcable.com [165.237.216
                      .1]
                        3     1 ms    <1 ms    <1 ms  cindcrc01-vlan-100.oh.rcn.twcable.com [165.237.2
                      13.2]
                        4    <1 ms    <1 ms    <1 ms  cindcrc02-gig-1-48.oh.rcn.twcable.com [165.237.2
                      09.17]
                        5     4 ms     4 ms     4 ms  165.237.209.39
                        6     4 ms     4 ms     4 ms  165.237.214.11
                        7     4 ms     4 ms     4 ms  vln500.rdcoh1-p-rtr01.columbus.rr.com [65.189.10
                      1.193]
                        8     6 ms     5 ms     5 ms  tengig3-0-0.rdcoh1-p-rtr01.columbus.rr.com [65.1
                      89.100.137]
                        9    10 ms    10 ms    11 ms  tengig1-1.ncntoh1-p-rtr01.columbus.rr.com [65.18
                      9.100.45]
                       10    10 ms    10 ms    10 ms  gig4-0-0.ncntoh1-rtr0.neo.rr.com [65.189.100.62]
                      
                       11    12 ms    11 ms    11 ms  te-3-2.car1.cleveland1.level3.net [64.156.66.53]
                      
                       12    32 ms    20 ms    19 ms  ae-4-4.ebr1.washington1.level3.net [4.69.132.194
                      ]
                       13    29 ms    20 ms    19 ms  ae-61-61.csw1.washington1.level3.net [4.69.134.1
                      30]
                       14    20 ms    20 ms    21 ms  ae-13-69.car3.washington1.level3.net [4.68.17.5]
                      
                       15    20 ms    20 ms    21 ms  savvis-level3-te.washington1.level3.net [4.68.11
                      0.102]
                       16    21 ms    21 ms    20 ms  cpr1-ge-4-0-0.virginiaequinix.savvis.net [204.70
                      .193.5]
                       17    22 ms    22 ms    21 ms  208.173.10.194
                       18     *        *        *     Request timed out.
                       19     *        *        *     Request timed out.
                       20    23 ms    22 ms    24 ms  bf2sb.tacticalgamer.com [64.34.161.157]
                      Trace complete.

                      Don't think those last two hops mean anything tbh.
                      |TG-X|WAREHOUSE

                      Comment


                      • #12
                        Re: bad hops to TG server

                        I hate you guys with <25ms pings! Almost a reason to emigrate.

                        Comment


                        • #13
                          Re: bad hops to TG server



                          :)

                          sorry, I had to brag

                          I've got the same last two time-outs, but I've never had a problem

                          I didn't join a squad once and this guy named Nardini took me into the back room and beat me with a sock of oranges.

                          Comment


                          • #14
                            Re: bad hops to TG server

                            A ping of 5ms, now that is just sick that is...

                            Comment


                            • #15
                              Re: bad hops to TG server

                              Not all servers or routers will respond to a ping btw, its a security thing. Your home machine for example should be set to not accept pings but it will take normal traffic without loss. Ping type traffic can be used in denial of service type attacks I think


                              If you find yourself in a fair fight, then you have obviously failed to plan properly.

                              Comment

                              Connect

                              Collapse

                              TeamSpeak 3 Server

                              Collapse

                              Advertisement

                              Collapse

                              Twitter Feed

                              Collapse

                              Working...
                              X