All cable Modem Users

Collapse
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • ThePatriot
    #1

    All cable Modem Users

    Anyone on a cable modem could you quickly run into dos and type in ping some stuff for me. In dos simply type in ping, then the adress, do these 3 things plz


    ping www.yahoo.com tell me min ms, max ms, and avg ms
    ping 168.143.176.194 same as above
    ping 10.65.105.12 same as above


    Also list your locations plz


    I am doing this because my modem has been extremely slow and i have been having it out with Adelphia cable recently. They claim i am lying and i finally got them to come to my house and i want some proof, i have logs showing my yahoo ping going from 130 to 50 then to 70, my ping is all over the damned place. Thnx guys.
    Tags: None
    • speedballbanks
      i love cops...wives
      • Jul 2001
      • 1546
      #2
      hey tell me this i don't know much about ping but what is a good ping and how do you get a bad one fixed because i think my cousins ping sucks! let me know man thatnks and i would test for you but he has an i-mac.
      good traders- agdmagman2001, magdude25,Geoff Noble, than205, X-plosive, speedball4life, CoFFey[NiTrO], Snakebite78, zads27

        Comment

        • Potatoboy
          Hamburgers should be high

          • Sep 2001
          • 2533
          #3
          Even though it doesn't really mean anything I did it.

          Ferndale, MI feeding off the Royal Oak MI comcast node.

          C:\>ping www.yahoo.com

          Pinging www.yahoo.akadns.net [66.218.71.86] with 32 bytes of data:

          Reply from 66.218.71.86: bytes=32 time=80ms TTL=51
          Reply from 66.218.71.86: bytes=32 time=70ms TTL=51
          Reply from 66.218.71.86: bytes=32 time=70ms TTL=51
          Reply from 66.218.71.86: bytes=32 time=70ms TTL=51

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

          C:\>ping 168.143.176.194

          Pinging 168.143.176.194 with 32 bytes of data:

          Reply from 168.143.176.194: bytes=32 time=50ms TTL=113
          Reply from 168.143.176.194: bytes=32 time=40ms TTL=113
          Reply from 168.143.176.194: bytes=32 time=40ms TTL=113
          Reply from 168.143.176.194: bytes=32 time=40ms TTL=113

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

          C:\>ping 10.65.105.12

          Pinging 10.65.105.12 with 32 bytes of data:

          Request timed out.
          Request timed out.
          Request timed out.
          Request timed out.

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

          It sounds like your box may have been comprimised and is running a server. Try updating your virus scanner, and doing a complete search. Also, stop all IIS services if applicable and make sure you have the latest security updates.
          Potatoboy!

            Comment

            • dogEmedic
              Fluff Your Garfield
              • Oct 2001
              • 240
              #4
              I was bored and gave it a try to.

              monmouth co nj comcast.net

              C:\WINDOWS>ping www.yahoo.com

              Pinging www.yahoo.akadns.net [64.58.76.227] with 32 bytes of data:

              Reply from 64.58.76.227: bytes=32 time=20ms TTL=240
              Reply from 64.58.76.227: bytes=32 time=17ms TTL=240
              Reply from 64.58.76.227: bytes=32 time=18ms TTL=240
              Reply from 64.58.76.227: bytes=32 time=17ms TTL=240

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


              C:\WINDOWS>ping 168.143.176.194

              Pinging 168.143.176.194 with 32 bytes of data:

              Reply from 168.143.176.194: bytes=32 time=29ms TTL=113
              Reply from 168.143.176.194: bytes=32 time=20ms TTL=113
              Reply from 168.143.176.194: bytes=32 time=24ms TTL=113
              Reply from 168.143.176.194: bytes=32 time=22ms TTL=113

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


              C:\WINDOWS>ping 13.65.105.12

              Pinging 13.65.105.12 with 32 bytes of data:

              Request timed out.
              Request timed out.
              Request timed out.
              Request timed out.

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

                Comment

                • Restola
                  Certificated Cloud Buster
                  • May 2001
                  • 2230
                  #5
                  Time Warner Cable's roadrunner in northeast ohio (on a home network with 3 other computers through a linksys router).

                  Microsoft Windows XP [Version 5.1.2600]
                  (C) Copyright 1985-2001 Microsoft Corp.

                  C:\ping www.yahoo.com

                  Pinging www.yahoo.akadns.net [64.58.76.228] with 32 bytes of data:

                  Reply from 64.58.76.228: bytes=32 time=29ms TTL=242
                  Reply from 64.58.76.228: bytes=32 time=48ms TTL=242
                  Reply from 64.58.76.228: bytes=32 time=34ms TTL=242
                  Reply from 64.58.76.228: bytes=32 time=53ms TTL=242

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

                  C:\ping 168.143.176.194

                  Pinging 168.143.176.194 with 32 bytes of data:

                  Reply from 168.143.176.194: bytes=32 time=114ms TTL=114
                  Reply from 168.143.176.194: bytes=32 time=55ms TTL=114
                  Reply from 168.143.176.194: bytes=32 time=41ms TTL=114
                  Reply from 168.143.176.194: bytes=32 time=32ms TTL=114

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

                  C:\ping 10.65.105.12

                  Pinging 10.65.105.12 with 32 bytes of data:

                  Reply from 24.95.81.200: TTL expired in transit.
                  Reply from 24.95.81.200: TTL expired in transit.
                  Reply from 24.95.81.200: TTL expired in transit.
                  Reply from 24.95.81.200: TTL expired in transit.

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

                  AO Feedback / Ebay Feedback / AOPA / JeepForum.com / IPR

                    Comment

                    • ThePatriot
                      #6
                      Thnx guys...turns out it wasnt as slow as i thought. When they installed the modem(s), we have 3 cable modems in our house now :\ they kinda put 3 splitters. They made 1 for TV's, 1 for modems, and 1 extra, so all my power was being divided into 3, and the 3rd splitter was empty. So the cable guy repaired it and everything was ok. Well now i am spiking like 750-1500 pings on a CS server and getting some mad packet loss(cl_flushentitypacket.) Thing is i ping about 60 off the server(thats the 168.143.176.194) but when im in the game its really bad. I think its my windows 98, i have had it up for over 2 years and maybe its just not takin info like it used to so i think i am gonna reformat, because the cable company(i have spent i would say 8 hours on the phone w/ them in past 3 days) said there is nothing wrong w/ my cable service.

                        Comment

                        • CoFFeY[NiTrO]
                          battle royale
                          • Sep 2001
                          • 3222
                          #7
                          https://www.dfw.speakeasy.net


                          Try that...

                          My download : 1066kbps

                          My upload : 99kbps


                          Thats pretty low for my but the only thing you are supposed to have open is Internet Explorer and not anything else (I had aim 2 windows open and music playing...)

                          Instant Message Me
                          ~3rd-Party Trades~

                            Comment

                            • ThePatriot
                              #8
                              If you *****, they will comply. Well, after about 5 days of non stop calls to Adelphia, and the entire staff thinking i am insane, i got what i wanted. They added more bandwith to the server, and my modem is now running ship shape and perfect, if you have a problem and complain enough it will get solved.

                                Comment

                                Previous template Next
                                Working...