by vgbond
7 replies
Ping an ip address in Md-Dos command prompt results are not clear to me. Anyone help me to understand?


Code:
Pinging nhost.biz [66.96.249.197] with 32 bytes of data

Reply from 66.96.249.197: bytes=32 time=1026ms TTL=48
Reply from 66.96.249.197: bytes=32 time=839ms TTL=48
Reply from 66.96.249.197: bytes=32 time=793ms TTL=48
Reply from 66.96.249.197: bytes=32 time=629ms TTL=48

Ping statistics for 66.96.249.197:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
    Minimum = 629ms, Maximum = 1026ms, Average = 821ms
Here which terms denote what? This is necessary for me to learn. Please help.
#ping
  • Profile picture of the author Luke Graham
    bytes = the size of the packet sent (how much data you "pinged with")
    time = the time it took to get a response
    TTL = Time to Live; This is decreased by one for each router the packet passes through. If it gets to zero, the packet is discarded. It basically ensures the packet doesnt live forever.

    The response times, and packet loss should be fairly self explanatory, but if you are diagnosing network packet loss you should send at least 100 pings; ICMP (pings) is low priority traffic and may be discarded on an ISP router if its busy doing something else. In the above example, if one packet was dropped it would show 25% packet loss so isnt a good reflection.....

    You should also remember that a lot of routers will not respond to pings so although it may look like your getting "100% packet loss" to it, it may still be alive and kicking.

    Finally, in most cases you may want to use in conjuction with "tracert" if you are diagnosing network problems.
    Signature
    Best Ways To Make Money Online

    Eight bytes walk into a bar. The bartender asks, “Can I get you anything?”
    “Yeah,” reply the bytes. “Make us a double.”
    {{ DiscussionBoard.errors[1909199].message }}
    • Profile picture of the author vgbond
      Is it possible to be informed about a SERVER speed and quality from it?
      {{ DiscussionBoard.errors[1909410].message }}
      • Profile picture of the author Luke Graham
        Not really - no.

        It will only measure the time it takes for it to respond to an ICMP echo request.

        This is worthless when trying to measure speed. As mentioned before, ICMP is in most cases treated as low priority. Also, if the server isnt in the same country as you you may find speed of connection from you to it is poor - yet the server may be fine for everyone else. Other factors may include how busy it is, how busy your connection is, packet loss and so on ...

        You will get a better idea if you measure the speed of both text and binary files downloaded from it.

        If you are monitoring your own server hosted somewhere, it should be simple to create a script to send pings, and download (wget) files several times a day if you have access to a unix box.
        Signature
        Best Ways To Make Money Online

        Eight bytes walk into a bar. The bartender asks, “Can I get you anything?”
        “Yeah,” reply the bytes. “Make us a double.”
        {{ DiscussionBoard.errors[1909442].message }}
  • Profile picture of the author Nick M
    I would suggest that these times are on the high side.

    I just pinged it from Hong Kong and got:

    PING 66.96.249.197 (66.96.249.197): 56 data bytes
    64 bytes from 66.96.249.197: icmp_seq=0 ttl=57 time=263.677 ms
    64 bytes from 66.96.249.197: icmp_seq=1 ttl=57 time=265.760 ms
    64 bytes from 66.96.249.197: icmp_seq=2 ttl=57 time=281.454 ms
    64 bytes from 66.96.249.197: icmp_seq=3 ttl=57 time=266.767 ms

    My ping times are half yours. The IP is listed as being located in Washington DC, which is literally about as far from Hong Kong as two points on the earth can get, so whilst it isn't a hard and fast rule, if you're consistently getting ping times of over 600ms, there is something between you and that server which is slowing things down.
    {{ DiscussionBoard.errors[1921234].message }}
  • Profile picture of the author RichardHK
    If your pings are of concern you can do a 'tracert' command from your dos prompt too, and see each step in the journey from your machine to your test IP. Then you will know where the blockage is.

    Do a search on web for Trace IP or similar and you will find many free online tools for this work. Your hosting company may also have service.
    Signature

    Richard, Hong Kong
    Business Consulting

    {{ DiscussionBoard.errors[3159516].message }}
  • Profile picture of the author SteveJohnson
    Why are you resurrecting a 10-month old thread? Couldn't be for spamming your sig, could it?
    Signature

    The 2nd Amendment, 1789 - The Original Homeland Security.

    Gun control means never having to say, "I missed you."

    {{ DiscussionBoard.errors[3161784].message }}
    • Profile picture of the author adizam
      Pot.. meet Kettle.. Kettle.. meet Pot.

      -_-
      {{ DiscussionBoard.errors[3165657].message }}

Trending Topics