Join us now. It is free, and it takes less than 1 minute to register.
Register now
Subscribe to our daily newsletter. It is free, and it comes with many benefits.


+ Reply to Thread
Page 1 of 45 1234511 ... LastLast
Results 1 to 15 of 674

Thread: "Is it my Line" Report Tool

  1. #1

    Default "Is it my Line" Report Tool [V2]

    Hi All,
    This tool pings the last possible hardware on the telkom network - to help deduce whether a fault lies with Telkom or with the user's ISP

    I am very strict with regards to malware, and will never distribute something that potentially has any form of harmful file attached to it.

    Download JAR: https://zertop.github.io/releases/latest/

    Download Android App: https://github.com/Zertop/LineToolAndroid/releases

    Changelog: https://github.com/Zertop/LineTool/releases


    Last edited by Zertop; 27-03-2017 at 08:42 PM.
    "1) Help me fix my Internet" Tool | "2) Is it my Line" Tool
    "Also, are you alive? That's important, should have asked that first." - Wheatly P2

  2. #2

    Default

    nice tool

    Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert)

    Pinging 196.215.156.1 with 32 bytes of data:
    Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
    Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
    Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
    Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
    Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
    Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
    Reply from 196.215.156.1: bytes=32 time=10ms TTL=254
    Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
    Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
    Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
    Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
    Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
    Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
    Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
    Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
    Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
    Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
    Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
    Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
    Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
    Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
    Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
    Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
    Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
    Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
    Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
    Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
    Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
    Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
    Reply from 196.215.156.1: bytes=32 time=9ms TTL=254

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

    Fri 03/28/2014 20:51:36.65
    i7 [email protected]|EVGA 970|8GB1866|TP 750w|H55|asrock z68E7G3|G710+4.4TB|40" sammy|uncap 10mb

  3. #3

    Default

    Quote Originally Posted by sybertiger View Post
    nice tool

    Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert)

    Pinging 196.215.156.1 with 32 bytes of data:
    Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
    Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
    Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
    Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
    Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
    Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
    Reply from 196.215.156.1: bytes=32 time=10ms TTL=254
    Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
    Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
    Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
    Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
    Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
    Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
    Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
    Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
    Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
    Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
    Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
    Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
    Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
    Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
    Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
    Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
    Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
    Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
    Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
    Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
    Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
    Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
    Reply from 196.215.156.1: bytes=32 time=9ms TTL=254

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

    Fri 03/28/2014 20:51:36.65
    Solid Stuff Thanks :-)
    "1) Help me fix my Internet" Tool | "2) Is it my Line" Tool
    "Also, are you alive? That's important, should have asked that first." - Wheatly P2

  4. #4
    Super Grandmaster wabbit16's Avatar
    Join Date
    Dec 2006
    Location
    Planet Ęth
    Posts
    5,863

    Default

    Your tool just called my line dodgy! JK, here is my result (WA 4meg capped account):

    Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert)

    Pinging 196.210.145.129 with 32 bytes of data:
    Reply from 196.210.145.129: bytes=32 time=29ms TTL=254
    Reply from 196.210.145.129: bytes=32 time=31ms TTL=254
    Reply from 196.210.145.129: bytes=32 time=28ms TTL=254
    Reply from 196.210.145.129: bytes=32 time=29ms TTL=254
    Reply from 196.210.145.129: bytes=32 time=30ms TTL=254
    Reply from 196.210.145.129: bytes=32 time=35ms TTL=254
    Reply from 196.210.145.129: bytes=32 time=32ms TTL=254
    Reply from 196.210.145.129: bytes=32 time=29ms TTL=254
    Reply from 196.210.145.129: bytes=32 time=29ms TTL=254
    Reply from 196.210.145.129: bytes=32 time=31ms TTL=254
    Reply from 196.210.145.129: bytes=32 time=35ms TTL=254
    Reply from 196.210.145.129: bytes=32 time=29ms TTL=254
    Reply from 196.210.145.129: bytes=32 time=30ms TTL=254
    Reply from 196.210.145.129: bytes=32 time=29ms TTL=254
    Reply from 196.210.145.129: bytes=32 time=29ms TTL=254
    Reply from 196.210.145.129: bytes=32 time=29ms TTL=254
    Reply from 196.210.145.129: bytes=32 time=31ms TTL=254
    Reply from 196.210.145.129: bytes=32 time=31ms TTL=254
    Reply from 196.210.145.129: bytes=32 time=29ms TTL=254
    Reply from 196.210.145.129: bytes=32 time=29ms TTL=254
    Reply from 196.210.145.129: bytes=32 time=29ms TTL=254
    Reply from 196.210.145.129: bytes=32 time=30ms TTL=254
    Reply from 196.210.145.129: bytes=32 time=29ms TTL=254
    Reply from 196.210.145.129: bytes=32 time=37ms TTL=254
    Reply from 196.210.145.129: bytes=32 time=29ms TTL=254
    Reply from 196.210.145.129: bytes=32 time=34ms TTL=254
    Reply from 196.210.145.129: bytes=32 time=41ms TTL=254
    Reply from 196.210.145.129: bytes=32 time=33ms TTL=254
    Reply from 196.210.145.129: bytes=32 time=29ms TTL=254
    Reply from 196.210.145.129: bytes=32 time=29ms TTL=254

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

    2014/03/28 21:13:22.05
    EDIT: I am using a wireless USB stick (Draft N 300mpbs )connected to a router down the passage, if it makes any difference. Landlord said we aren't allowed to run cables

  5. #5

    Default

    Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert)

    Pinging 105.224.132.1 with 32 bytes of data:
    Reply from 105.224.132.1: bytes=32 time=759ms TTL=254
    Reply from 105.224.132.1: bytes=32 time=824ms TTL=254
    Reply from 105.224.132.1: bytes=32 time=864ms TTL=254
    Reply from 105.224.132.1: bytes=32 time=847ms TTL=254
    Reply from 105.224.132.1: bytes=32 time=819ms TTL=254
    Reply from 105.224.132.1: bytes=32 time=769ms TTL=254
    Reply from 105.224.132.1: bytes=32 time=825ms TTL=254
    Reply from 105.224.132.1: bytes=32 time=947ms TTL=254
    Reply from 105.224.132.1: bytes=32 time=893ms TTL=254
    Reply from 105.224.132.1: bytes=32 time=792ms TTL=254
    Reply from 105.224.132.1: bytes=32 time=855ms TTL=254
    Reply from 105.224.132.1: bytes=32 time=866ms TTL=254
    Reply from 105.224.132.1: bytes=32 time=802ms TTL=254
    Reply from 105.224.132.1: bytes=32 time=720ms TTL=254
    Reply from 105.224.132.1: bytes=32 time=688ms TTL=254
    Reply from 105.224.132.1: bytes=32 time=718ms TTL=254
    Reply from 105.224.132.1: bytes=32 time=790ms TTL=254
    Reply from 105.224.132.1: bytes=32 time=838ms TTL=254
    Reply from 105.224.132.1: bytes=32 time=933ms TTL=254
    Reply from 105.224.132.1: bytes=32 time=932ms TTL=254
    Reply from 105.224.132.1: bytes=32 time=718ms TTL=254
    Reply from 105.224.132.1: bytes=32 time=612ms TTL=254
    Reply from 105.224.132.1: bytes=32 time=575ms TTL=254
    Reply from 105.224.132.1: bytes=32 time=688ms TTL=254
    Reply from 105.224.132.1: bytes=32 time=737ms TTL=254
    Reply from 105.224.132.1: bytes=32 time=776ms TTL=254
    Reply from 105.224.132.1: bytes=32 time=788ms TTL=254
    Reply from 105.224.132.1: bytes=32 time=842ms TTL=254
    Reply from 105.224.132.1: bytes=32 time=869ms TTL=254
    Reply from 105.224.132.1: bytes=32 time=908ms TTL=254

    Ping statistics for 105.224.132.1:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 575ms, Maximum = 947ms, Average = 799ms

    2014/03/28 21:29:20.67


    fault is being fixed though

  6. #6
    Still a Mod MickeyD's Avatar
    Join Date
    Oct 2010
    Location
    Nelson Mandela Bay
    Posts
    137,685

    Default

    running tool

    cannot create the text file...

  7. #7

    Default

    Quote Originally Posted by MickeyD View Post
    running tool

    cannot create the text file...
    Did you extract the file?

    If so - please PM me with the full output on screen :-)

    Z
    "1) Help me fix my Internet" Tool | "2) Is it my Line" Tool
    "Also, are you alive? That's important, should have asked that first." - Wheatly P2

  8. #8

    Default

    Quote Originally Posted by (-(-_(-_-)_-)-) View Post
    Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert)

    Pinging 105.224.132.1 with 32 bytes of data:
    Reply from 105.224.132.1: bytes=32 time=759ms TTL=254
    Reply from 105.224.132.1: bytes=32 time=824ms TTL=254
    Reply from 105.224.132.1: bytes=32 time=864ms TTL=254
    Reply from 105.224.132.1: bytes=32 time=847ms TTL=254
    Reply from 105.224.132.1: bytes=32 time=819ms TTL=254
    Reply from 105.224.132.1: bytes=32 time=769ms TTL=254
    Reply from 105.224.132.1: bytes=32 time=825ms TTL=254
    Reply from 105.224.132.1: bytes=32 time=947ms TTL=254
    Reply from 105.224.132.1: bytes=32 time=893ms TTL=254
    Reply from 105.224.132.1: bytes=32 time=792ms TTL=254
    Reply from 105.224.132.1: bytes=32 time=855ms TTL=254
    Reply from 105.224.132.1: bytes=32 time=866ms TTL=254
    Reply from 105.224.132.1: bytes=32 time=802ms TTL=254
    Reply from 105.224.132.1: bytes=32 time=720ms TTL=254
    Reply from 105.224.132.1: bytes=32 time=688ms TTL=254
    Reply from 105.224.132.1: bytes=32 time=718ms TTL=254
    Reply from 105.224.132.1: bytes=32 time=790ms TTL=254
    Reply from 105.224.132.1: bytes=32 time=838ms TTL=254
    Reply from 105.224.132.1: bytes=32 time=933ms TTL=254
    Reply from 105.224.132.1: bytes=32 time=932ms TTL=254
    Reply from 105.224.132.1: bytes=32 time=718ms TTL=254
    Reply from 105.224.132.1: bytes=32 time=612ms TTL=254
    Reply from 105.224.132.1: bytes=32 time=575ms TTL=254
    Reply from 105.224.132.1: bytes=32 time=688ms TTL=254
    Reply from 105.224.132.1: bytes=32 time=737ms TTL=254
    Reply from 105.224.132.1: bytes=32 time=776ms TTL=254
    Reply from 105.224.132.1: bytes=32 time=788ms TTL=254
    Reply from 105.224.132.1: bytes=32 time=842ms TTL=254
    Reply from 105.224.132.1: bytes=32 time=869ms TTL=254
    Reply from 105.224.132.1: bytes=32 time=908ms TTL=254

    Ping statistics for 105.224.132.1:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 575ms, Maximum = 947ms, Average = 799ms

    2014/03/28 21:29:20.67


    fault is being fixed though
    I was about to say

    Haha - hope it gets fixed soon

    Z
    "1) Help me fix my Internet" Tool | "2) Is it my Line" Tool
    "Also, are you alive? That's important, should have asked that first." - Wheatly P2

  9. #9

    Default

    Quote Originally Posted by wabbit16 View Post
    Your tool just called my line dodgy! JK, here is my result (WA 4meg capped account):



    EDIT: I am using a wireless USB stick (Draft N 300mpbs )connected to a router down the passage, if it makes any difference. Landlord said we aren't allowed to run cables

    Haha - Yea thats probably it Long-Distance wifi does influence ping :P

    Z
    Last edited by Zertop; 28-03-2014 at 10:28 PM. Reason: Grammar Nazi inside of me had to
    "1) Help me fix my Internet" Tool | "2) Is it my Line" Tool
    "Also, are you alive? That's important, should have asked that first." - Wheatly P2

  10. #10
    Still a Mod MickeyD's Avatar
    Join Date
    Oct 2010
    Location
    Nelson Mandela Bay
    Posts
    137,685

    Default

    Quote Originally Posted by Zertop View Post
    Did you extract the file?

    If so - please PM me with the full output on screen :-)

    Z
    EXE file gives the issue.
    Saved the ZIP file - works.
    ******************

    Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert)

    Pinging 105.224.168.1 with 32 bytes of data:

    Reply from 105.224.168.1: bytes=32 time=28ms TTL=254
    Reply from 105.224.168.1: bytes=32 time=27ms TTL=254
    Reply from 105.224.168.1: bytes=32 time=90ms TTL=254
    Reply from 105.224.168.1: bytes=32 time=39ms TTL=254
    Reply from 105.224.168.1: bytes=32 time=26ms TTL=254
    Reply from 105.224.168.1: bytes=32 time=30ms TTL=254
    Reply from 105.224.168.1: bytes=32 time=26ms TTL=254
    Reply from 105.224.168.1: bytes=32 time=31ms TTL=254
    Reply from 105.224.168.1: bytes=32 time=29ms TTL=254
    Reply from 105.224.168.1: bytes=32 time=29ms TTL=254
    Reply from 105.224.168.1: bytes=32 time=35ms TTL=254
    Reply from 105.224.168.1: bytes=32 time=26ms TTL=254
    Reply from 105.224.168.1: bytes=32 time=43ms TTL=254
    Reply from 105.224.168.1: bytes=32 time=140ms TTL=254
    Reply from 105.224.168.1: bytes=32 time=129ms TTL=254
    Reply from 105.224.168.1: bytes=32 time=26ms TTL=254
    Reply from 105.224.168.1: bytes=32 time=26ms TTL=254
    Reply from 105.224.168.1: bytes=32 time=43ms TTL=254
    Reply from 105.224.168.1: bytes=32 time=47ms TTL=254
    Reply from 105.224.168.1: bytes=32 time=85ms TTL=254
    Reply from 105.224.168.1: bytes=32 time=63ms TTL=254
    Reply from 105.224.168.1: bytes=32 time=47ms TTL=254
    Reply from 105.224.168.1: bytes=32 time=60ms TTL=254
    Reply from 105.224.168.1: bytes=32 time=91ms TTL=254
    Reply from 105.224.168.1: bytes=32 time=81ms TTL=254
    Reply from 105.224.168.1: bytes=32 time=56ms TTL=254
    Reply from 105.224.168.1: bytes=32 time=26ms TTL=254
    Reply from 105.224.168.1: bytes=32 time=27ms TTL=254
    Reply from 105.224.168.1: bytes=32 time=27ms TTL=254
    Reply from 105.224.168.1: bytes=32 time=27ms TTL=254

    Ping statistics for 105.224.168.1:

    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),

    Approximate round trip times in milli-seconds:

    Minimum = 26ms, Maximum = 140ms, Average = 48ms

    2014/03/28 21:57:12.37

  11. #11

    Default

    Quote Originally Posted by MickeyD View Post
    EXE file gives the issue.
    Saved the ZIP file - works.
    2014/03/28 21:57:12.37
    Okay cool - I'll look into it!

    Z
    "1) Help me fix my Internet" Tool | "2) Is it my Line" Tool
    "Also, are you alive? That's important, should have asked that first." - Wheatly P2

  12. #12

    Default

    UPDATE:
    -Fixed error when text file is deleted before it is opened. (Thanks MickyD).
    -Results are now attached to the clipboard.
    -Fixed intelligence report on Good result.

    Z
    "1) Help me fix my Internet" Tool | "2) Is it my Line" Tool
    "Also, are you alive? That's important, should have asked that first." - Wheatly P2

  13. #13
    Super Grandmaster DrJohnZoidberg's Avatar
    Join Date
    Jul 2006
    Location
    Table View
    Posts
    19,528

    Default

    Nice work Zertop.

    One idea to get the correct external IP is to start from the top (of the traceroute) and accept the first IP which is not a private address and is not the clients IP.
    Quote Originally Posted by Zolani99 View Post
    The atheists won't be forced to bow their heads, they can just imagine themselves burning in hell.

  14. #14

    Default

    Quote Originally Posted by DrJohnZoidberg View Post
    Nice work Zertop.

    One idea to get the correct external IP is to start from the top (of the traceroute) and accept the first IP which is not a private address and is not the clients IP.
    Thanks Man!

    Good Idea - I will try implement that
    "1) Help me fix my Internet" Tool | "2) Is it my Line" Tool
    "Also, are you alive? That's important, should have asked that first." - Wheatly P2

  15. #15

    Default

    VOX:

    Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert)

    Pinging 197.245.30.1 with 32 bytes of data:
    Reply from 197.245.30.1: bytes=32 time=22ms TTL=254
    Reply from 197.245.30.1: bytes=32 time=20ms TTL=254
    Reply from 197.245.30.1: bytes=32 time=20ms TTL=254
    Reply from 197.245.30.1: bytes=32 time=20ms TTL=254
    Reply from 197.245.30.1: bytes=32 time=21ms TTL=254
    Reply from 197.245.30.1: bytes=32 time=21ms TTL=254
    Reply from 197.245.30.1: bytes=32 time=21ms TTL=254
    Reply from 197.245.30.1: bytes=32 time=21ms TTL=254
    Reply from 197.245.30.1: bytes=32 time=20ms TTL=254
    Reply from 197.245.30.1: bytes=32 time=20ms TTL=254
    Reply from 197.245.30.1: bytes=32 time=21ms TTL=254
    Reply from 197.245.30.1: bytes=32 time=21ms TTL=254
    Reply from 197.245.30.1: bytes=32 time=21ms TTL=254
    Reply from 197.245.30.1: bytes=32 time=21ms TTL=254
    Reply from 197.245.30.1: bytes=32 time=20ms TTL=254
    Reply from 197.245.30.1: bytes=32 time=20ms TTL=254
    Reply from 197.245.30.1: bytes=32 time=21ms TTL=254
    Reply from 197.245.30.1: bytes=32 time=20ms TTL=254
    Reply from 197.245.30.1: bytes=32 time=20ms TTL=254
    Reply from 197.245.30.1: bytes=32 time=21ms TTL=254
    Reply from 197.245.30.1: bytes=32 time=21ms TTL=254
    Reply from 197.245.30.1: bytes=32 time=20ms TTL=254
    Reply from 197.245.30.1: bytes=32 time=20ms TTL=254
    Reply from 197.245.30.1: bytes=32 time=21ms TTL=254
    Reply from 197.245.30.1: bytes=32 time=20ms TTL=254
    Reply from 197.245.30.1: bytes=32 time=20ms TTL=254
    Reply from 197.245.30.1: bytes=32 time=21ms TTL=254
    Reply from 197.245.30.1: bytes=32 time=21ms TTL=254
    Reply from 197.245.30.1: bytes=32 time=20ms TTL=254
    Reply from 197.245.30.1: bytes=32 time=21ms TTL=254

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

    2014/03/28 23:09:39.54

    Connection:

    Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert)

    Pinging 196.210.157.1 with 32 bytes of data:
    Reply from 196.210.157.1: bytes=32 time=10ms TTL=254
    Reply from 196.210.157.1: bytes=32 time=11ms TTL=254
    Reply from 196.210.157.1: bytes=32 time=10ms TTL=254
    Reply from 196.210.157.1: bytes=32 time=10ms TTL=254
    Reply from 196.210.157.1: bytes=32 time=11ms TTL=254
    Reply from 196.210.157.1: bytes=32 time=10ms TTL=254
    Reply from 196.210.157.1: bytes=32 time=10ms TTL=254
    Reply from 196.210.157.1: bytes=32 time=12ms TTL=254
    Reply from 196.210.157.1: bytes=32 time=10ms TTL=254
    Reply from 196.210.157.1: bytes=32 time=11ms TTL=254
    Reply from 196.210.157.1: bytes=32 time=10ms TTL=254
    Reply from 196.210.157.1: bytes=32 time=10ms TTL=254
    Reply from 196.210.157.1: bytes=32 time=10ms TTL=254
    Reply from 196.210.157.1: bytes=32 time=10ms TTL=254
    Reply from 196.210.157.1: bytes=32 time=10ms TTL=254
    Reply from 196.210.157.1: bytes=32 time=10ms TTL=254
    Reply from 196.210.157.1: bytes=32 time=10ms TTL=254
    Reply from 196.210.157.1: bytes=32 time=10ms TTL=254
    Reply from 196.210.157.1: bytes=32 time=10ms TTL=254
    Reply from 196.210.157.1: bytes=32 time=11ms TTL=254
    Reply from 196.210.157.1: bytes=32 time=10ms TTL=254
    Reply from 196.210.157.1: bytes=32 time=10ms TTL=254
    Reply from 196.210.157.1: bytes=32 time=10ms TTL=254
    Reply from 196.210.157.1: bytes=32 time=11ms TTL=254
    Reply from 196.210.157.1: bytes=32 time=10ms TTL=254
    Reply from 196.210.157.1: bytes=32 time=10ms TTL=254
    Reply from 196.210.157.1: bytes=32 time=10ms TTL=254
    Reply from 196.210.157.1: bytes=32 time=11ms TTL=254
    Reply from 196.210.157.1: bytes=32 time=10ms TTL=254
    Reply from 196.210.157.1: bytes=32 time=10ms TTL=254

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

    2014/03/28 23:14:25.03

+ Reply to Thread
Page 1 of 45 1234511 ... LastLast

Similar Threads

  1. "Help me fix my internet" report tool
    By Zertop in forum ADSL and VDSL ISP Discussions
    Replies: 155
    Last Post: 09-01-2016, 06:54 AM
  2. Hulu and "Anonymous Proxy Tool" warning.
    By DominionZA in forum TV Services, including DStv, Video on Demand, Video Streaming
    Replies: 35
    Last Post: 24-04-2014, 09:05 PM
  3. Replies: 6
    Last Post: 09-07-2013, 06:25 PM
  4. "Security Tool" rogue antivirus application removal HELP!
    By BigBear in forum Networking and Security
    Replies: 11
    Last Post: 12-10-2010, 10:24 PM
  5. Please Scrap the Thread "Tool Tips"
    By Charlie. in forum First Posts, Intros, Forum Questions
    Replies: 8
    Last Post: 15-07-2008, 05:44 PM

Bookmarks

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •