"Is it my Line" Report Tool

Zertop · Aug 30, 2015

This is some serious BS

Zertop's "Is it my Line" Results
Date/Time: Sun Aug 30 17:21:10 WAT 2015

Basic Report:

Your packet loss was 0%.
Your average ping was 1630ms.
Your maximum ping was 2575ms.

Looking at your average ping, there is definitely something wrong with your line! Please post the results (at the end of the program) into the forum for advice!

Detailed Report:

Code:

Pinging 155.239.255.250 with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=2095ms TTL=63
Reply from 155.239.255.250: bytes=32 time=2142ms TTL=63
Reply from 155.239.255.250: bytes=32 time=2231ms TTL=63
Reply from 155.239.255.250: bytes=32 time=2164ms TTL=63
Reply from 155.239.255.250: bytes=32 time=2263ms TTL=63
Reply from 155.239.255.250: bytes=32 time=2242ms TTL=63
Reply from 155.239.255.250: bytes=32 time=2493ms TTL=63
Reply from 155.239.255.250: bytes=32 time=2171ms TTL=63
Reply from 155.239.255.250: bytes=32 time=2096ms TTL=63
Reply from 155.239.255.250: bytes=32 time=2135ms TTL=63
Reply from 155.239.255.250: bytes=32 time=2307ms TTL=63
Reply from 155.239.255.250: bytes=32 time=2177ms TTL=63
Reply from 155.239.255.250: bytes=32 time=2269ms TTL=63
Reply from 155.239.255.250: bytes=32 time=2575ms TTL=63
Reply from 155.239.255.250: bytes=32 time=2314ms TTL=63
Reply from 155.239.255.250: bytes=32 time=2083ms TTL=63
Reply from 155.239.255.250: bytes=32 time=321ms TTL=63
Reply from 155.239.255.250: bytes=32 time=448ms TTL=63
Reply from 155.239.255.250: bytes=32 time=260ms TTL=63
Reply from 155.239.255.250: bytes=32 time=206ms TTL=63
Reply from 155.239.255.250: bytes=32 time=480ms TTL=63
Reply from 155.239.255.250: bytes=32 time=70ms TTL=63
Reply from 155.239.255.250: bytes=32 time=205ms TTL=63
Reply from 155.239.255.250: bytes=32 time=325ms TTL=63
Reply from 155.239.255.250: bytes=32 time=784ms TTL=63
Reply from 155.239.255.250: bytes=32 time=1600ms TTL=63
Reply from 155.239.255.250: bytes=32 time=2188ms TTL=63
Reply from 155.239.255.250: bytes=32 time=2183ms TTL=63
Reply from 155.239.255.250: bytes=32 time=1914ms TTL=63
Reply from 155.239.255.250: bytes=32 time=2170ms TTL=63

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

Anyone in brackenfell area with issues?

Ask 10210 for a port reset

This is often a temporary issue before exchange issues...

Z

PPLdude · Aug 30, 2015

Zertop said:
Ask 10210 for a port reset This is often a temporary issue before exchange issues...

Z

Homephone keeps cutting the connection, and I don't have airtime lol. Was fine earlier

Zertop · Sep 9, 2015

static_sa said:
Homephone keeps cutting the connection, and I don't have airtime lol. Was fine earlier

Make sure you have a filter on your adsl line!

Zertop · Sep 9, 2015

New Release: V2.1.4

Fixed bug where Windows Notepad did not separate line breaks
Added indication of test failure upon 100% packet loss.
Updated for Windows 10 Capability

Zertop · Sep 10, 2015

New Release: V2.1.6
https://github.com/Zertop/LineTool-Core/releases/tag/V2.1.6

Kierenblade · Sep 11, 2015

My ping is all over the place. Line issue?

Zertop's "Is it my Line" Results
Date/Time: Fri Sep 11 22:14:10 CAT 2015

Basic Report:

Your packet loss was 0%.
Your average ping was 65ms.
Your maximum ping was 77ms.

Looking at your average ping, your line seems to be a bit dodgy. This may account for any slow speeds you may be experiencing. However, it could just be related to a high-latency home network (eg... Wi-Fi). If you feel the need, please post the results (at the end of the program) into the forum for advice!

Detailed Report:

Code:

Pinging 197.245.17.1 with 32 bytes of data:
Reply from 197.245.17.1: bytes=32 time=54ms TTL=254
Reply from 197.245.17.1: bytes=32 time=73ms TTL=254
Reply from 197.245.17.1: bytes=32 time=47ms TTL=254
Reply from 197.245.17.1: bytes=32 time=58ms TTL=254
Reply from 197.245.17.1: bytes=32 time=72ms TTL=254
Reply from 197.245.17.1: bytes=32 time=69ms TTL=254
Reply from 197.245.17.1: bytes=32 time=60ms TTL=254
Reply from 197.245.17.1: bytes=32 time=71ms TTL=254
Reply from 197.245.17.1: bytes=32 time=74ms TTL=254
Reply from 197.245.17.1: bytes=32 time=77ms TTL=254
Reply from 197.245.17.1: bytes=32 time=67ms TTL=254
Reply from 197.245.17.1: bytes=32 time=67ms TTL=254
Reply from 197.245.17.1: bytes=32 time=75ms TTL=254
Reply from 197.245.17.1: bytes=32 time=76ms TTL=254
Reply from 197.245.17.1: bytes=32 time=63ms TTL=254
Reply from 197.245.17.1: bytes=32 time=76ms TTL=254
Reply from 197.245.17.1: bytes=32 time=76ms TTL=254
Reply from 197.245.17.1: bytes=32 time=63ms TTL=254
Reply from 197.245.17.1: bytes=32 time=65ms TTL=254
Reply from 197.245.17.1: bytes=32 time=75ms TTL=254
Reply from 197.245.17.1: bytes=32 time=67ms TTL=254
Reply from 197.245.17.1: bytes=32 time=53ms TTL=254
Reply from 197.245.17.1: bytes=32 time=49ms TTL=254
Reply from 197.245.17.1: bytes=32 time=30ms TTL=254
Reply from 197.245.17.1: bytes=32 time=47ms TTL=254
Reply from 197.245.17.1: bytes=32 time=64ms TTL=254
Reply from 197.245.17.1: bytes=32 time=76ms TTL=254
Reply from 197.245.17.1: bytes=32 time=70ms TTL=254
Reply from 197.245.17.1: bytes=32 time=65ms TTL=254
Reply from 197.245.17.1: bytes=32 time=76ms TTL=254

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

Drifter · Sep 12, 2015

Having issues with this under Win 10. Doesnt run at all.

atomcrusher · Sep 12, 2015

Drifter said:
Having issues with this under Win 10. Doesnt run at all.

I get this when running the tool on Win 10 Pro 64-bit

Sorry, the tool was unable to detect an IP to ping.
Please ensure that you are connected to the internet.

Detailed:
java.lang.IllegalStateException: No match found

Tracing route to zertop.com [154.127.61.124]
over a maximum of 2 hops:

1 <1 ms <1 ms <1 ms 192.168.123.254
2 * * * Request timed out.

Trace complete.

Drifter · Sep 12, 2015

atomcrusher said:
I get this when running the tool on Win 10 Pro 64-bit

Mine does nothing, just starts then stops. No reports or anything.

Zertop · Sep 12, 2015

Kierenblade said:

My ping is all over the place. Line issue?

Zertop's "Is it my Line" Results
Date/Time: Fri Sep 11 22:14:10 CAT 2015

Basic Report:

Your packet loss was 0%.
Your average ping was 65ms.
Your maximum ping was 77ms.

Looking at your average ping, your line seems to be a bit dodgy. This may account for any slow speeds you may be experiencing. However, it could just be related to a high-latency home network (eg... Wi-Fi). If you feel the need, please post the results (at the end of the program) into the forum for advice!

Detailed Report:

Code:

Pinging 197.245.17.1 with 32 bytes of data:
Reply from 197.245.17.1: bytes=32 time=54ms TTL=254
Reply from 197.245.17.1: bytes=32 time=73ms TTL=254
Reply from 197.245.17.1: bytes=32 time=47ms TTL=254
Reply from 197.245.17.1: bytes=32 time=58ms TTL=254
Reply from 197.245.17.1: bytes=32 time=72ms TTL=254
Reply from 197.245.17.1: bytes=32 time=69ms TTL=254
Reply from 197.245.17.1: bytes=32 time=60ms TTL=254
Reply from 197.245.17.1: bytes=32 time=71ms TTL=254
Reply from 197.245.17.1: bytes=32 time=74ms TTL=254
Reply from 197.245.17.1: bytes=32 time=77ms TTL=254
Reply from 197.245.17.1: bytes=32 time=67ms TTL=254
Reply from 197.245.17.1: bytes=32 time=67ms TTL=254
Reply from 197.245.17.1: bytes=32 time=75ms TTL=254
Reply from 197.245.17.1: bytes=32 time=76ms TTL=254
Reply from 197.245.17.1: bytes=32 time=63ms TTL=254
Reply from 197.245.17.1: bytes=32 time=76ms TTL=254
Reply from 197.245.17.1: bytes=32 time=76ms TTL=254
Reply from 197.245.17.1: bytes=32 time=63ms TTL=254
Reply from 197.245.17.1: bytes=32 time=65ms TTL=254
Reply from 197.245.17.1: bytes=32 time=75ms TTL=254
Reply from 197.245.17.1: bytes=32 time=67ms TTL=254
Reply from 197.245.17.1: bytes=32 time=53ms TTL=254
Reply from 197.245.17.1: bytes=32 time=49ms TTL=254
Reply from 197.245.17.1: bytes=32 time=30ms TTL=254
Reply from 197.245.17.1: bytes=32 time=47ms TTL=254
Reply from 197.245.17.1: bytes=32 time=64ms TTL=254
Reply from 197.245.17.1: bytes=32 time=76ms TTL=254
Reply from 197.245.17.1: bytes=32 time=70ms TTL=254
Reply from 197.245.17.1: bytes=32 time=65ms TTL=254
Reply from 197.245.17.1: bytes=32 time=76ms TTL=254

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

Hey,

Yeah that looks like it would be :/

Z

Zertop · Sep 12, 2015

Drifter said:
Having issues with this under Win 10. Doesnt run at all.

atomcrusher said:
I get this when running the tool on Win 10 Pro 64-bit

Apologies, I stuffed up

I'll fix it quickly!

Z

Zertop · Sep 12, 2015

Program Update:
https://github.com/Zertop/LineTool-Core/releases/tag/V2.1.8

Download: https://zertop.com/releases/linetool

Zertop · Sep 12, 2015

Drifter said:
Having issues with this under Win 10. Doesnt run at all.

Do you have Java installed?

Z

ogkspaz · Sep 13, 2015

Peak hour seems to slow my line to a crawl. Only after 1am or so does my line get anything close to normal again. Can hardly do any online gaming at the moment.

Zertop's "Is it my Line" Results
Date/Time: Sun Sep 13 20:50:13 CAT 2015

Basic Report:

Your packet loss was 3%.
Your average ping was 450ms.
Your maximum ping was 569ms.

You seem to have some packet loss. This indicates an issue on the line.
Looking at your average ping, there is definitely something wrong with your line! Please post the results (at the end of the program) into the forum for advice!

Detailed Report:

Code:

Pinging 196.210.150.1 with 32 bytes of data:
Reply from 196.210.150.1: bytes=32 time=418ms TTL=254
Reply from 196.210.150.1: bytes=32 time=336ms TTL=254
Reply from 196.210.150.1: bytes=32 time=569ms TTL=254
Reply from 196.210.150.1: bytes=32 time=558ms TTL=254
Reply from 196.210.150.1: bytes=32 time=403ms TTL=254
Reply from 196.210.150.1: bytes=32 time=438ms TTL=254
Reply from 196.210.150.1: bytes=32 time=499ms TTL=254
Reply from 196.210.150.1: bytes=32 time=423ms TTL=254
Reply from 196.210.150.1: bytes=32 time=446ms TTL=254
Request timed out.
Reply from 196.210.150.1: bytes=32 time=406ms TTL=254
Reply from 196.210.150.1: bytes=32 time=374ms TTL=254
Reply from 196.210.150.1: bytes=32 time=487ms TTL=254
Reply from 196.210.150.1: bytes=32 time=547ms TTL=254
Reply from 196.210.150.1: bytes=32 time=469ms TTL=254
Reply from 196.210.150.1: bytes=32 time=522ms TTL=254
Reply from 196.210.150.1: bytes=32 time=424ms TTL=254
Reply from 196.210.150.1: bytes=32 time=440ms TTL=254
Reply from 196.210.150.1: bytes=32 time=475ms TTL=254
Reply from 196.210.150.1: bytes=32 time=503ms TTL=254
Reply from 196.210.150.1: bytes=32 time=459ms TTL=254
Reply from 196.210.150.1: bytes=32 time=489ms TTL=254
Reply from 196.210.150.1: bytes=32 time=354ms TTL=254
Reply from 196.210.150.1: bytes=32 time=438ms TTL=254
Reply from 196.210.150.1: bytes=32 time=465ms TTL=254
Reply from 196.210.150.1: bytes=32 time=299ms TTL=254
Reply from 196.210.150.1: bytes=32 time=566ms TTL=254
Reply from 196.210.150.1: bytes=32 time=496ms TTL=254
Reply from 196.210.150.1: bytes=32 time=254ms TTL=254
Reply from 196.210.150.1: bytes=32 time=497ms TTL=254

Ping statistics for 196.210.150.1:
    Packets: Sent = 30, Received = 29, Lost = 1 (3% loss),
Approximate round trip times in milli-seconds:
    Minimum = 254ms, Maximum = 569ms, Average = 450ms

capetown.spdtst.saix.net result

Last Result:
Download Speed: 826 kbps (103.3 KB/sec transfer rate)
Upload Speed: 274 kbps (34.3 KB/sec transfer rate)
Latency: 358 ms
9/13/2015, 8:49:02 PM

www.google.co.za tracert

Code:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

>tracert www.google.co.za

Tracing route to www.google.co.za [196.23.168.166]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.0.0.2
  2   511 ms   541 ms   563 ms  196-210-150-1.dynamic.isadsl.co.za [196.210.150.1]
  3     *      558 ms   619 ms  cdsl1-ctn-vl2173.ip.isnet.net [196.38.72.113]
  4   462 ms   474 ms   498 ms  196.35.115.128
  5     *      566 ms   571 ms  mi-za-cpt-p8-te0-0-0-0.ip.isnet.net [168.209.6.13]
  6   558 ms   570 ms   591 ms  mi-za-cpt-p7-te0-7-0-0.ip.isnet.net [168.209.2.12]
  7   528 ms   606 ms   611 ms  168.209.100.101
  8     *      431 ms   409 ms  csw5-pkl-te1-7.ip.isnet.net [196.26.0.188]
  9     *      568 ms   616 ms  196.23.168.166

Trace complete.

atomcrusher · Sep 14, 2015

Zertop said:
Apologies, I stuffed up

I'll fix it quickly!

Z

Thanks Zertop. Seems to work OK now on my Win 10 Pro 64-bit laptop
(Telkom ISP 4Mbps ADSL)

Now I get this:

Zertop's "Is it my Line" Results
Date/Time: Mon Sep 14 14:19:27 CAT 2015

Basic Report:

Your packet loss was 0%.
Your average ping was 12ms.
Your maximum ping was 14ms.

Looking at your average ping, your line seems to be running perfectly.
It seems that your maximum ping is also good. If there are any issues, they most probably lie with your ISP

Detailed Report:

Code:

Pinging 155.239.255.250 with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=14ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=14ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63

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

BigBear · Sep 14, 2015

V. 2.1.9 Great as Always !

Win 7 x64 JAVA JRE Version 8 Update 60
Telkom 10 Mbps ADSL, VOX Telcom Fatpipe

Code:

Adsl Line Status	SHOWTIME.
Adsl Mode	G992.1
Up Stream	640 kbps
Down Stream	8128 kbps
Attenuation Down Stream	24
Attenuation Up Stream	15
SNR Margin Down Stream	13.1
SNR Margin Up Stream	12.0

Zertop's "Is it my Line" Results
Date/Time: Mon Sep 14 22:09:48 CAT 2015

Basic Report:

Your packet loss was 0%.
Your average ping was 8ms.
Your maximum ping was 11ms.

Looking at your average ping, your line seems to be running perfectly.
It seems that your maximum ping is also good. If there are any issues, they most probably lie with your ISP

Detailed Report:

Code:

Pinging 155.239.255.250 with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63

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

Zertop · Sep 15, 2015

BigBear said:

V. 2.1.9 Great as Always !

Win 7 x64 JAVA JRE Version 8 Update 60
Telkom 10 Mbps ADSL, VOX Telcom Fatpipe

Code:

Adsl Line Status	SHOWTIME.
Adsl Mode	G992.1
Up Stream	640 kbps
Down Stream	8128 kbps
Attenuation Down Stream	24
Attenuation Up Stream	15
SNR Margin Down Stream	13.1
SNR Margin Up Stream	12.0

Zertop's "Is it my Line" Results
Date/Time: Mon Sep 14 22:09:48 CAT 2015

Basic Report:

Your packet loss was 0%.
Your average ping was 8ms.
Your maximum ping was 11ms.

Looking at your average ping, your line seems to be running perfectly.
It seems that your maximum ping is also good. If there are any issues, they most probably lie with your ISP

Detailed Report:

Code:

Pinging 155.239.255.250 with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63

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

Looking Excellent!

Z

Zertop · Sep 15, 2015

atomcrusher said:
Thanks Zertop. Seems to work OK now on my Win 10 Pro 64-bit laptop
(Telkom ISP 4Mbps ADSL)

Now I get this:

Cool beans,

That looks good too!

Z

ABCpt · Sep 15, 2015

Getting error when trying to run the tool.
Java virtual machine Launcher
Could not find the main class: Control.engine. Program will exit.

Zertop · Sep 15, 2015

ABCpt said:
Getting error when trying to run the tool.
Java virtual machine Launcher
Could not find the main class: Control.engine. Program will exit.

:wtf:

Was it Control.Engine or Control.engine? If it was the latter, I have no idea what has happened?

Z

"Is it my Line" Report Tool

Expert Member

Expert Member

Expert Member

Expert Member

Expert Member

New Member

Honorary Master

Expert Member

Honorary Master

Expert Member

Expert Member

Expert Member

Expert Member

Member

Expert Member

Expert Member

Expert Member

Expert Member

Expert Member

Expert Member