Announcement

Collapse
No announcement yet.

High pings

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

  • High pings

    I have been getting a ping b/t 250-450 for a few days now. I ran a speed test on my connention which was 557 down and 245 up (kbps). I have refromatted my HDs removed the router from the network and I still get that healthy ping on the TG server and no ping less than 300 on any server in the serach screen. WHat is going on here? I called my ISP and they are sending someone out. But it looks like the speed test ran fine. Also, how do you protect a computer from spyware and what not wuth hardware only. I dontlike having things running in the background eating my FPS. thanks.

  • #2
    Re: High pings

    Speed tests will give very little indication of network latency... You need something like PingPlotter to see where your connection is going bad...
    Become a supporting member!
    Buy a Tactical Duck!
    Take the world's smallest political quiz! "I was touched by His Noodly Appendage."
    TacticalGamer TX LAN/BBQ Veteran:

    Comment


    • #3
      Re: High pings

      That is a neat little program.....WHat do I do now that i know the address that is causing the slow down?

      Comment


      • #4
        Re: High pings

        I'm curious.. is it a level3.net address?
        Steam Community? Add me. | Free Remote, Encrypted Backup

        Darkilla: In short, NS is pretty much really fast chess. With guns. Apophis: I haven't seen anyone say that SM's are better than non-SMs. Nordbomber: This is THE first server I've seen where either side can comeback from out of seemingly nowhere with the right teamwork. en4rcment: I have NEVER experienced the type of gameplay that I have found here. Nightly I am amazed at the personalities and gaming talent. Zephyr: Apophis is clearly a highly sophisticated self-aware AI construct that runs on a highly modified toaster oven in Wyzcrak's basement.

        Comment


        • #5
          Re: High pings

          AT&T WorldNet Services ATT (NET-12-0-0-0-1)
          12.0.0.0 - 12.255.255.255
          AT&T Worldnet Services ATTSVI-12-124-4-0-1 (NET-12-124-4-0-1)
          12.124.4.0 - 12.124.95.255
          I googled and it looks like this has been an ongoing issue for some people. I have read posts dated 2002. I dont think there is anything I can do since I am not an ATT customer. I am no internet guru, but I think it is a routing issue with ATT hardware.

          Comment


          • #6
            Re: High pings

            My favorite suite of freeware spyware tools is:

            Ad-aware (removal scans only)
            Spybot - Search & Destroy (removal and prevention)
            Spywareblaster (prevention only)

            Now that that's out of the way...

            Do you have a cable modem connection? From your upspeed it looks like it. If so, many cable ISP's are converting to the new QAM 256 system from the QAM 64 system. I have Comcast where I live and they have just converted. The new system is DOCSIS 2.0 compliant and many older modems are only DOCSIS 1.0. This theoretically should not be a problem, but typically is. When they converted here, my numbers went out of spec and I had to purchase a new modem to get them inline again.

            There are three important numbers when it comes to your cable signal:

            - Downstream SNR (signal to noise ratio)
            - Downstream Channel Power
            - Upstream Channel Power

            If you're on the QAM 256:

            - SNR should be 33 dB or higher
            - Downstream Power should be from -15 dBmV to +15 dBmV
            - Upstream Power should be +30 to +55 dBmV

            Values close to the upper or lower limits will likely cause problems.

            Newer modems have a web-based configuration page that is normally accessed on:
            192.168.100.1 (but may vary)
            Through this utility you can read the above values. If you have an older modem you can call your provider and ask them to give you the values. A lot of the people you talk to won't know what you're talking about at first, or think they do, but give you the wrong values. Just be patient and verify with them that the up and down power levels are in dBmV (decibel millivolts) and the SNR is in dB (decibels). Then you're getting the right numbers.

            It seems like the QAM 256 system (at least in my area) is pickier about connection quality than the old QAM 64 system. You have to check all your connections from your "drop" (feed line from the pole or underground system) to your modem.

            If you're in an apartment / condo you likely won't have access to the drop which makes things tough. If you're in a house though, the drop will attach to a grounding block attached to the siding or inside a service box (usually accessible). The grounding block is important so don't disconnect it. It's usually the first thing to get that white powdery corrosion dust though. If it has the dust it should be replaced, if not they're usually OK. Check all your splitters for problems as well. Dust, loose connectors, etc.

            Splitters and lines should be up to spec. Meaning the splitters should be at least 1000 MHz (1 GHz) quality. It's usually printed right on the splitter. Cables should be Quad Shield RG6 for lowest signal loss. Again, usually printed on the cable.

            Long cable runs and splitters add signal loss to your system, it's unavoidable, but you have to manage it. Two-way splitters usually have a -3.5/-4.0 dB loss per side. Newer three, four, etc-way splitters typically have one low loss output. For example, a three way splitter will have one -4 dB output and two -8 dB outputs. In this case you would run the line that goes to the cable modem off the -4 dB output.

            It's also possible that your run from the drop to your modem is so squeaky clean and spanking new that you don't have enough signal loss, "Huh?". Your cable modem controls the upstream signal and will only push as hard as it has to, which can inadvertently cause problems (intermittent / dropped connections). This can be determined by your upstream signal power. If you're below 30 dBmV, you don't have enough noise on your line (signal loss). This is easily rectified by "padding out" your line. Simply put a two-way splitter on the line to cable modem and recheck your upstream power level. If it's still not pushed over the 30 mark, add another one or try a three/four way.

            Basically it's a balance between up and down power levels. You can't change one without affecting the other.

            If you have DSL please disregard everything... hehe. Hopefully this will help the cable people though.

            Good Luck!
            Beware of Flying Dogs....

            Comment


            • #7
              Re: High pings

              192.168.100.1 that number is associated with my modem. It seems that the connectiion cleans during off peak hours.
              Downstream Receive Power Level: -7.9 dBmV
              Downstream SNR: 33.2 dB
              Upstream Transmit Power Level: 46.0 dBmV

              During off peak hours, my ping drops to around 150, not good but playable. I am giving Charter a week to fix this then I am going to DSL.

              THANKS FOR THE GREAT RESPONSE!!

              Comment


              • #8
                Re: High pings

                Here is the repot from pingplotter

                Target Name: 170.67-19-90.reverse.theplanet.com
                IP: 67.19.90.170
                Date/Time: 9/10/2005 10:50:25 PM

                1 7 ms 10 ms 8 ms 9 ms [10.129.224.1]
                2 11 ms 9 ms 9 ms 11 ms [172.22.32.33]
                3 25 ms 8 ms 12 ms 9 ms [172.22.32.138]
                4 9 ms 8 ms 9 ms 12 ms [172.22.32.106]
                5 358 ms 362 ms 374 ms 360 ms [12.124.58.105]
                6 377 ms 378 ms 397 ms 370 ms tbr2-p011904.attga.ip.att.net [12.123.21.78]
                7 374 ms 381 ms 394 ms 371 ms tbr1-cl1.dlstx.ip.att.net [12.122.2.89]
                8 375 ms 382 ms 392 ms 366 ms gar1-p360.dlrtx.ip.att.net [12.123.196.101]
                9 * * * N/A [-] TOTAL PACKET LOSS
                10 N/A N/A N/A 370 ms vl31.dsr02.dllstx3.theplanet.com [70.85.127.30]
                11 N/A 374 ms 401 ms 370 ms dist-vlan-42.dsr2-2.dllstx4.theplanet.com [70.85.127.91]
                12 375 ms N/A 401 ms 368 ms gig1-0-1.sm-car6-7.dllstx4.theplanet.com [67.19.255.26]
                13 377 ms 373 ms 400 ms 374 ms 170.67-19-90.reverse.theplanet.com [67.19.90.170]

                Ping statistics for 170.67-19-90.reverse.theplanet.com
                Packets: Sent = 4, Received = 4, Lost = 0 (0.0%)
                Round Trip Times: Minimum = 373ms, Maximum = 400ms, Average = 381ms

                Comment


                • #9
                  Re: High pings

                  Let pingplotter run for a few minutes to give you some good average numbers to work with...

                  Hopefully, Apophis has reconfigured TG's firewall/ID software to not identify PingPlotter as a malicious attack... :icon26:
                  Become a supporting member!
                  Buy a Tactical Duck!
                  Take the world's smallest political quiz! "I was touched by His Noodly Appendage."
                  TacticalGamer TX LAN/BBQ Veteran:

                  Comment


                  • #10
                    Re: High pings

                    I had it running for a while and the above post represents the results.....

                    Comment


                    • #11
                      Re: High pings

                      Your service provider has a over utilized link to AT&T. Go with the DSL it shouldn't be any worse!




                      Originally posted by ><JohnGalt><
                      Here is the repot from pingplotter

                      Target Name: 170.67-19-90.reverse.theplanet.com
                      IP: 67.19.90.170
                      Date/Time: 9/10/2005 10:50:25 PM

                      1 7 ms 10 ms 8 ms 9 ms [10.129.224.1]
                      2 11 ms 9 ms 9 ms 11 ms [172.22.32.33]
                      3 25 ms 8 ms 12 ms 9 ms [172.22.32.138]
                      4 9 ms 8 ms 9 ms 12 ms [172.22.32.106]
                      5 358 ms 362 ms 374 ms 360 ms [12.124.58.105]
                      6 377 ms 378 ms 397 ms 370 ms tbr2-p011904.attga.ip.att.net [12.123.21.78]
                      7 374 ms 381 ms 394 ms 371 ms tbr1-cl1.dlstx.ip.att.net [12.122.2.89]
                      8 375 ms 382 ms 392 ms 366 ms gar1-p360.dlrtx.ip.att.net [12.123.196.101]
                      9 * * * N/A [-] TOTAL PACKET LOSS
                      10 N/A N/A N/A 370 ms vl31.dsr02.dllstx3.theplanet.com [70.85.127.30]
                      11 N/A 374 ms 401 ms 370 ms dist-vlan-42.dsr2-2.dllstx4.theplanet.com [70.85.127.91]
                      12 375 ms N/A 401 ms 368 ms gig1-0-1.sm-car6-7.dllstx4.theplanet.com [67.19.255.26]
                      13 377 ms 373 ms 400 ms 374 ms 170.67-19-90.reverse.theplanet.com [67.19.90.170]

                      Ping statistics for 170.67-19-90.reverse.theplanet.com
                      Packets: Sent = 4, Received = 4, Lost = 0 (0.0%)
                      Round Trip Times: Minimum = 373ms, Maximum = 400ms, Average = 381ms

                      Comment

                      Connect

                      Collapse

                      TeamSpeak 3 Server

                      Collapse

                      Advertisement

                      Collapse

                      Twitter Feed

                      Collapse

                      Working...
                      X