-
Ask a question and get free supportUnlock new privileges and see hidden discussionsWin prizes and earn reputation
-
Question of the day ~ How often do you braai?
-
Afristay giveaway.Win a 2-night stay for two people at an establishment of your choice with R1,000 in spending money. Enter here.
Sign up with Google"Is it my Line" Report Tool
- Thread starter Zertop
- Start date
Zertop
Expert Member
- Joined
- Mar 9, 2013
- Messages
- 3,105
Sigh.
This is an issue that I will be fixing soon. My domain host refused to release my domain - and therefore I am unable to renew it.
Z
Zertop
Expert Member
- Joined
- Mar 9, 2013
- Messages
- 3,105
Zertop
Expert Member
- Joined
- Mar 9, 2013
- Messages
- 3,105
In light of the loss of my main domain (read up here) - the tool will unfortunately be a bit troublesome for the next few days.
For now, you can download the tools using the following links:
Please note. Auto update will report that the system is offline. This is just as it is unable to reach my server (it will skip after a few seconds). If not, you will have to manually download the new version below.
EXE (Easy) - http://zertop.tk/files/LineTool/Windows/Current/linetool.exe
ZIP (Advanced-ish) - http://zertop.tk/files/LineTool/Windows/Current/linetool.zip
Thanks,
Z
For now, you can download the tools using the following links:
Please note. Auto update will report that the system is offline. This is just as it is unable to reach my server (it will skip after a few seconds). If not, you will have to manually download the new version below.
EXE (Easy) - http://zertop.tk/files/LineTool/Windows/Current/linetool.exe
ZIP (Advanced-ish) - http://zertop.tk/files/LineTool/Windows/Current/linetool.zip
Thanks,
Z
Last edited:
Zertop
Expert Member
- Joined
- Mar 9, 2013
- Messages
- 3,105
Yea. Sorry about that. New version out.
9. 13-11-2014
- Zertop.com domain down. Reworked tool to run off Zertop.tk domain instead.
Z
Zertop
Expert Member
- Joined
- Mar 9, 2013
- Messages
- 3,105
Hi,
Sorry about that. My domain was taken down due to a transfer request that went wrong. Please see the links above
Z
squirrel
Expert Member
- Joined
- Jun 11, 2005
- Messages
- 1,979
And now my results :/
Zertop's "Is it my Line" Results
Basic Report:
Your average ping was 938ms
Your maximum ping was 1055ms
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
Zertop's "Is it my Line" Results
Basic Report:
Your average ping was 938ms
Your maximum ping was 1055ms
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:
Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert)
Pinging 196.210.170.129 with 32 bytes of data:
Reply from 196.210.170.129: bytes=32 time=847ms TTL=254
Reply from 196.210.170.129: bytes=32 time=882ms TTL=254
Reply from 196.210.170.129: bytes=32 time=943ms TTL=254
Reply from 196.210.170.129: bytes=32 time=1036ms TTL=254
Reply from 196.210.170.129: bytes=32 time=924ms TTL=254
Reply from 196.210.170.129: bytes=32 time=967ms TTL=254
Reply from 196.210.170.129: bytes=32 time=1055ms TTL=254
Reply from 196.210.170.129: bytes=32 time=969ms TTL=254
Reply from 196.210.170.129: bytes=32 time=947ms TTL=254
Reply from 196.210.170.129: bytes=32 time=975ms TTL=254
Reply from 196.210.170.129: bytes=32 time=803ms TTL=254
Reply from 196.210.170.129: bytes=32 time=890ms TTL=254
Reply from 196.210.170.129: bytes=32 time=977ms TTL=254
Reply from 196.210.170.129: bytes=32 time=918ms TTL=254
Reply from 196.210.170.129: bytes=32 time=971ms TTL=254
Reply from 196.210.170.129: bytes=32 time=995ms TTL=254
Reply from 196.210.170.129: bytes=32 time=861ms TTL=254
Reply from 196.210.170.129: bytes=32 time=928ms TTL=254
Reply from 196.210.170.129: bytes=32 time=966ms TTL=254
Reply from 196.210.170.129: bytes=32 time=878ms TTL=254
Reply from 196.210.170.129: bytes=32 time=892ms TTL=254
Reply from 196.210.170.129: bytes=32 time=1018ms TTL=254
Reply from 196.210.170.129: bytes=32 time=998ms TTL=254
Reply from 196.210.170.129: bytes=32 time=980ms TTL=254
Reply from 196.210.170.129: bytes=32 time=922ms TTL=254
Reply from 196.210.170.129: bytes=32 time=920ms TTL=254
Reply from 196.210.170.129: bytes=32 time=978ms TTL=254
Reply from 196.210.170.129: bytes=32 time=933ms TTL=254
Reply from 196.210.170.129: bytes=32 time=868ms TTL=254
Reply from 196.210.170.129: bytes=32 time=918ms TTL=254
Ping statistics for 196.210.170.129:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 803ms, Maximum = 1055ms, Average = 938ms
Thu 11/13/2014 20:47:57.84Zertop
Expert Member
- Joined
- Mar 9, 2013
- Messages
- 3,105
Wow.
Sorry to say - but that looks horrid. Could you try with a guest account to confirm? The telkom guest account/a web africa free gig/afrihost free gig account will work fine
Z
squirrel
Expert Member
- Joined
- Jun 11, 2005
- Messages
- 1,979
It's been like this for a few years. I did that on a WebAfrica Capped account that I use at another house (about 3km away) and never had problems. Telkom and alarm technicians have come in over the years and 'fixed' problems. Sometimes the line drops and re-syncs at a slower speed. A friend lives in the same road and sometimes has the same problems. He tried upgrading his line but the line keeps dropping
Upstream 512 kbps
Downstream 2048 kbps
Noise Margin (Upstream) 13.0 db
Noise Margin (Downstream) 14.0 db
Attenuation (Upstream) 26.0 db
Attenuation (Downstream) 48.0 db
Upstream 512 kbps
Downstream 2048 kbps
Noise Margin (Upstream) 13.0 db
Noise Margin (Downstream) 14.0 db
Attenuation (Upstream) 26.0 db
Attenuation (Downstream) 48.0 db
wingnut771
Honorary Master
- Joined
- Feb 15, 2011
- Messages
- 28,144
For a long time now, the tool just closes after I "press and key" at the end where it used to open the results in notepad.
What am I doing wrong?
EDIT: Don't know what I did, think I pressed spacebar instead of enter and it worked now.
What am I doing wrong?
EDIT: Don't know what I did, think I pressed spacebar instead of enter and it worked now.
Last edited:
squirrel
Expert Member
- Joined
- Jun 11, 2005
- Messages
- 1,979
Zertop: Telkom guest account
Zertop's "Is it my Line" Results
Basic Report:
Your average ping was 701ms
Your maximum ping was 946ms
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
Zertop's "Is it my Line" Results
Basic Report:
Your average ping was 701ms
Your maximum ping was 946ms
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:
Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert)
Pinging 165.145.66.1 with 32 bytes of data:
Reply from 165.145.66.1: bytes=32 time=627ms TTL=254
Request timed out.
Reply from 165.145.66.1: bytes=32 time=751ms TTL=254
Reply from 165.145.66.1: bytes=32 time=542ms TTL=254
Reply from 165.145.66.1: bytes=32 time=600ms TTL=254
Reply from 165.145.66.1: bytes=32 time=761ms TTL=254
Reply from 165.145.66.1: bytes=32 time=823ms TTL=254
Reply from 165.145.66.1: bytes=32 time=833ms TTL=254
Request timed out.
Reply from 165.145.66.1: bytes=32 time=706ms TTL=254
Reply from 165.145.66.1: bytes=32 time=719ms TTL=254
Reply from 165.145.66.1: bytes=32 time=847ms TTL=254
Reply from 165.145.66.1: bytes=32 time=946ms TTL=254
Reply from 165.145.66.1: bytes=32 time=699ms TTL=254
Reply from 165.145.66.1: bytes=32 time=705ms TTL=254
Reply from 165.145.66.1: bytes=32 time=734ms TTL=254
Reply from 165.145.66.1: bytes=32 time=607ms TTL=254
Reply from 165.145.66.1: bytes=32 time=719ms TTL=254
Reply from 165.145.66.1: bytes=32 time=820ms TTL=254
Reply from 165.145.66.1: bytes=32 time=649ms TTL=254
Reply from 165.145.66.1: bytes=32 time=618ms TTL=254
Reply from 165.145.66.1: bytes=32 time=686ms TTL=254
Reply from 165.145.66.1: bytes=32 time=758ms TTL=254
Reply from 165.145.66.1: bytes=32 time=733ms TTL=254
Reply from 165.145.66.1: bytes=32 time=800ms TTL=254
Reply from 165.145.66.1: bytes=32 time=549ms TTL=254
Reply from 165.145.66.1: bytes=32 time=476ms TTL=254
Reply from 165.145.66.1: bytes=32 time=652ms TTL=254
Reply from 165.145.66.1: bytes=32 time=725ms TTL=254
Reply from 165.145.66.1: bytes=32 time=553ms TTL=254
Ping statistics for 165.145.66.1:
Packets: Sent = 30, Received = 28, Lost = 2 (6% loss),
Approximate round trip times in milli-seconds:
Minimum = 476ms, Maximum = 946ms, Average = 701ms
Thu 11/13/2014 21:01:13.26wingnut771
Honorary Master
- Joined
- Feb 15, 2011
- Messages
- 28,144
Zertop's "Is it my Line" Results
Basic Report:
Your average ping was 10ms
Your maximum ping was 58ms
Looking at your average ping, your line seems to be running perfectly
Looking at your maximum ping, however, it seems as though there could be a slight intermittant issue on the line. If required, please post the results to a forum post.
Detailed Report
Code:
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=9ms 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=9ms TTL=254
Reply from 196.210.157.1: bytes=32 time=9ms TTL=254
Reply from 196.210.157.1: bytes=32 time=9ms 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=9ms TTL=254
Reply from 196.210.157.1: bytes=32 time=10ms TTL=254
Reply from 196.210.157.1: bytes=32 time=9ms TTL=254
Reply from 196.210.157.1: bytes=32 time=58ms TTL=254
Reply from 196.210.157.1: bytes=32 time=9ms TTL=254
Reply from 196.210.157.1: bytes=32 time=9ms TTL=254
Reply from 196.210.157.1: bytes=32 time=9ms TTL=254
Reply from 196.210.157.1: bytes=32 time=9ms TTL=254
Reply from 196.210.157.1: bytes=32 time=9ms TTL=254
Reply from 196.210.157.1: bytes=32 time=9ms TTL=254
Reply from 196.210.157.1: bytes=32 time=10ms TTL=254
Reply from 196.210.157.1: bytes=32 time=9ms TTL=254
Reply from 196.210.157.1: bytes=32 time=9ms TTL=254
Reply from 196.210.157.1: bytes=32 time=10ms TTL=254
Reply from 196.210.157.1: bytes=32 time=9ms TTL=254
Reply from 196.210.157.1: bytes=32 time=9ms TTL=254
Reply from 196.210.157.1: bytes=32 time=9ms TTL=254
Reply from 196.210.157.1: bytes=32 time=10ms TTL=254
Reply from 196.210.157.1: bytes=32 time=9ms TTL=254
Reply from 196.210.157.1: bytes=32 time=9ms 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 = 9ms, Maximum = 58ms, Average = 10ms
2014/11/13 21:03:12.10Zertop
Expert Member
- Joined
- Mar 9, 2013
- Messages
- 3,105
Zertop's "Is it my Line" Results
Basic Report:
Your average ping was 10ms
Your maximum ping was 58ms
Looking at your average ping, your line seems to be running perfectly
Looking at your maximum ping, however, it seems as though there could be a slight intermittant issue on the line. If required, please post the results to a forum post.
Detailed Report
Code: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=9ms 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=9ms TTL=254 Reply from 196.210.157.1: bytes=32 time=9ms TTL=254 Reply from 196.210.157.1: bytes=32 time=9ms 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=9ms TTL=254 Reply from 196.210.157.1: bytes=32 time=10ms TTL=254 Reply from 196.210.157.1: bytes=32 time=9ms TTL=254 Reply from 196.210.157.1: bytes=32 time=58ms TTL=254 Reply from 196.210.157.1: bytes=32 time=9ms TTL=254 Reply from 196.210.157.1: bytes=32 time=9ms TTL=254 Reply from 196.210.157.1: bytes=32 time=9ms TTL=254 Reply from 196.210.157.1: bytes=32 time=9ms TTL=254 Reply from 196.210.157.1: bytes=32 time=9ms TTL=254 Reply from 196.210.157.1: bytes=32 time=9ms TTL=254 Reply from 196.210.157.1: bytes=32 time=10ms TTL=254 Reply from 196.210.157.1: bytes=32 time=9ms TTL=254 Reply from 196.210.157.1: bytes=32 time=9ms TTL=254 Reply from 196.210.157.1: bytes=32 time=10ms TTL=254 Reply from 196.210.157.1: bytes=32 time=9ms TTL=254 Reply from 196.210.157.1: bytes=32 time=9ms TTL=254 Reply from 196.210.157.1: bytes=32 time=9ms TTL=254 Reply from 196.210.157.1: bytes=32 time=10ms TTL=254 Reply from 196.210.157.1: bytes=32 time=9ms TTL=254 Reply from 196.210.157.1: bytes=32 time=9ms 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 = 9ms, Maximum = 58ms, Average = 10ms 2014/11/13 21:03:12.10
Looking good!
Z
Zertop
Expert Member
- Joined
- Mar 9, 2013
- Messages
- 3,105
Zertop
Expert Member
- Joined
- Mar 9, 2013
- Messages
- 3,105
wingnut771
Honorary Master
- Joined
- Feb 15, 2011
- Messages
- 28,144
Shouldn't make a difference. Haha I'll check it out anyway,
Z
or I could have typed "y" instead of "yes"
Zertop
Expert Member
- Joined
- Mar 9, 2013
- Messages
- 3,105
or I could have typed "y" instead of "yes"
Aah - that's it.
Maybe ill accept y - just for you
Z
wingnut771
Honorary Master
- Joined
- Feb 15, 2011
- Messages
- 28,144
Aah - that's it.
Maybe ill accept y - just for you
Z
Okay, it's definitely if I press enter at the end crashes the app, if I press spacebar instead then it works, whether I type y or yes.
EDIT: Hang on... now its doing it all the time :wtf:
Last edited: