Please would you do a tracert to google.co.za,
I might have broken something haha
Z
-
Join the MyBroadband community
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
-
Question of the Day: How do you normally pay for purchases in stores?
"Is it my Line" Report Tool
- Thread starter Zertop
- Start date
Please would you do a tracert to google.co.za,
I might have broken something haha
Z
Luke7777
Executive Member
- Joined
- Apr 22, 2004
- Messages
- 9,744
- Reaction score
- 2,110
- Location
- Menlo Park, Pretoria.. AH/OS 500/250
Still getting the error on 223Please try again. I have fixed this in the new version! (V2.2.3)
Z
atomcrusher
Expert Member
This test on my Telkom ISP 4Mbps line
-------------------------------------------
Zertop's LineTool Results
Date/Time: Sun Nov 29 12:11:51 CAT 2015
Basic Report:
Your packet loss was 0%.
Your average ping was 12ms.
Your maximum ping was 21ms.
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:
-------------------------------------------
Zertop's LineTool Results
Date/Time: Sun Nov 29 12:11:51 CAT 2015
Basic Report:
Your packet loss was 0%.
Your average ping was 12ms.
Your maximum ping was 21ms.
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=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=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63atomcrusher
Expert Member
And this using tracert command:
Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>tracert google.com
Tracing route to google.com [216.58.208.78]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.123.254
2 * * * Request timed out.
3 14 ms 13 ms 13 ms ipc-1-up.south.dsl.telkomsa.net [105.226.0.6]
4 14 ms 13 ms 13 ms ipc-aggr-1.south.dsl.telkomsa.net [105.226.0.13]
5 13 ms 13 ms 13 ms blv-pr-02-be200-vl1.net.telkomsa.net [105.226.0.54]
6 35 ms 35 ms 34 ms 105.187.249.246
7 34 ms 34 ms 35 ms 105.187.249.246
8 34 ms 35 ms 34 ms jb1-google-gw.net.telkomsa.net [105.187.249.22]
9 198 ms 208 ms 197 ms 66.249.95.8
10 198 ms 198 ms 197 ms 216.239.51.233
11 199 ms 198 ms 199 ms lhr14s27-in-f78.1e100.net [216.58.208.78]
Trace complete.
C:\WINDOWS\system32>
Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>tracert google.com
Tracing route to google.com [216.58.208.78]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.123.254
2 * * * Request timed out.
3 14 ms 13 ms 13 ms ipc-1-up.south.dsl.telkomsa.net [105.226.0.6]
4 14 ms 13 ms 13 ms ipc-aggr-1.south.dsl.telkomsa.net [105.226.0.13]
5 13 ms 13 ms 13 ms blv-pr-02-be200-vl1.net.telkomsa.net [105.226.0.54]
6 35 ms 35 ms 34 ms 105.187.249.246
7 34 ms 34 ms 35 ms 105.187.249.246
8 34 ms 35 ms 34 ms jb1-google-gw.net.telkomsa.net [105.187.249.22]
9 198 ms 208 ms 197 ms 66.249.95.8
10 198 ms 198 ms 197 ms 216.239.51.233
11 199 ms 198 ms 199 ms lhr14s27-in-f78.1e100.net [216.58.208.78]
Trace complete.
C:\WINDOWS\system32>
atomcrusher
Expert Member
Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>tracert google.co.za
Tracing route to google.co.za [216.58.223.35]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.123.254
2 * * * Request timed out.
3 21 ms 13 ms 14 ms ipc-1-up.south.dsl.telkomsa.net [105.226.0.6]
4 13 ms 13 ms 13 ms ipc-aggr-1.south.dsl.telkomsa.net [105.226.0.13]
5 37 ms 37 ms 36 ms jb1-pr-01-te1-0.net.telkomsa.net [105.187.249.6]
6 36 ms 36 ms 36 ms jb1-pr-01-te1-0.net.telkomsa.net [105.187.249.6]
7 36 ms 36 ms 35 ms jb1-google-gw.net.telkomsa.net [105.187.249.22]
8 36 ms 36 ms 42 ms 72.14.239.129
9 37 ms 37 ms 37 ms jnb01s08-in-f35.1e100.net [216.58.223.35]
Trace complete.
C:\WINDOWS\system32>
(c) 2015 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>tracert google.co.za
Tracing route to google.co.za [216.58.223.35]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.123.254
2 * * * Request timed out.
3 21 ms 13 ms 14 ms ipc-1-up.south.dsl.telkomsa.net [105.226.0.6]
4 13 ms 13 ms 13 ms ipc-aggr-1.south.dsl.telkomsa.net [105.226.0.13]
5 37 ms 37 ms 36 ms jb1-pr-01-te1-0.net.telkomsa.net [105.187.249.6]
6 36 ms 36 ms 36 ms jb1-pr-01-te1-0.net.telkomsa.net [105.187.249.6]
7 36 ms 36 ms 35 ms jb1-google-gw.net.telkomsa.net [105.187.249.22]
8 36 ms 36 ms 42 ms 72.14.239.129
9 37 ms 37 ms 37 ms jnb01s08-in-f35.1e100.net [216.58.223.35]
Trace complete.
C:\WINDOWS\system32>
Have been having issues with my connection. Am busy exploring various avenues. Something I noticed was that the router report that on my 4Mb line, I am syncing at Downstream 5120 kbps. Using the testing utility, give the following:
Zertop's LineTool Results
Date/Time: Thu Dec 03 21:27:23 CAT 2015
Basic Report:
Your packet loss was 16%.
Your average ping was 245ms.
Your maximum ping was 387ms.
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:
Could the 4/5 thing be related to the problem?
Zertop's LineTool Results
Date/Time: Thu Dec 03 21:27:23 CAT 2015
Basic Report:
Your packet loss was 16%.
Your average ping was 245ms.
Your maximum ping was 387ms.
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 155.239.255.250 with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=200ms TTL=63
Reply from 155.239.255.250: bytes=32 time=231ms TTL=63
Reply from 155.239.255.250: bytes=32 time=263ms TTL=63
Reply from 155.239.255.250: bytes=32 time=176ms TTL=63
Reply from 155.239.255.250: bytes=32 time=288ms TTL=63
Request timed out.
Request timed out.
Reply from 155.239.255.250: bytes=32 time=195ms TTL=63
Reply from 155.239.255.250: bytes=32 time=245ms TTL=63
Reply from 155.239.255.250: bytes=32 time=308ms TTL=63
Reply from 155.239.255.250: bytes=32 time=198ms TTL=63
Reply from 155.239.255.250: bytes=32 time=159ms TTL=63
Reply from 155.239.255.250: bytes=32 time=45ms TTL=63
Reply from 155.239.255.250: bytes=32 time=337ms TTL=63
Request timed out.
Reply from 155.239.255.250: bytes=32 time=307ms TTL=63
Reply from 155.239.255.250: bytes=32 time=198ms TTL=63
Reply from 155.239.255.250: bytes=32 time=280ms TTL=63
Reply from 155.239.255.250: bytes=32 time=363ms TTL=63
Reply from 155.239.255.250: bytes=32 time=346ms TTL=63
Reply from 155.239.255.250: bytes=32 time=136ms TTL=63
Reply from 155.239.255.250: bytes=32 time=151ms TTL=63
Reply from 155.239.255.250: bytes=32 time=387ms TTL=63
Reply from 155.239.255.250: bytes=32 time=319ms TTL=63
Reply from 155.239.255.250: bytes=32 time=220ms TTL=63
Reply from 155.239.255.250: bytes=32 time=369ms TTL=63
Request timed out.
Reply from 155.239.255.250: bytes=32 time=185ms TTL=63
Request timed out.
Reply from 155.239.255.250: bytes=32 time=223ms TTL=63
Ping statistics for 155.239.255.250:
Packets: Sent = 30, Received = 25, Lost = 5 (16% loss),
Approximate round trip times in milli-seconds:
Minimum = 45ms, Maximum = 387ms, Average = 245msCould the 4/5 thing be related to the problem?
There is definitely an issue between your house and your local exchange. This means that the fault lies on the Telkom network, and not with your ISP. Do you experience this at specific times, or is it a constant issue?
Z
The best I can describe it is like a yo-yo. Work well, then down, then up. Definitely not associated with specific times.
One issue I am also exploring is the possibility that it could be the Wi-Fi connection - maybe the router has issues. Too many devices in the house competing for the same resources? The router we have was bought at the beginning of 2008, when 1Gig was a lot of data. Now there is a surveillance system and printer connected, as well as laptops and cell phones.
Connected yesterday by using a direct cable connection, things are better but still not 100% for the short time which I was able to try it. Will look at it again through the day today and update when I have more information.
I am just short of buying a new router, but not entirely convinced yet.
Thanks a stack for getting back, much appreciated.
One issue I am also exploring is the possibility that it could be the Wi-Fi connection - maybe the router has issues. Too many devices in the house competing for the same resources? The router we have was bought at the beginning of 2008, when 1Gig was a lot of data. Now there is a surveillance system and printer connected, as well as laptops and cell phones.
Connected yesterday by using a direct cable connection, things are better but still not 100% for the short time which I was able to try it. Will look at it again through the day today and update when I have more information.
I am just short of buying a new router, but not entirely convinced yet.
Thanks a stack for getting back, much appreciated.
Last edited:
Icemanbrfc
Honorary Master
Any chance of an Android app?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.com/releases/linetool/
Changelog: https://github.com/Zertop/LineTool/releases
Doesn't sound like exchange congestion then, but something worse, unfortunately.
I don't know how a faulty router could cause these types of issues. Out of interest - what does your router's status page show?
Z
Any chance of an Android app?
Well, it's a possibility haha.
I don't know what the demand would be, though :/
Z
Icemanbrfc
Honorary Master
Cool, just thought I'd askWell, it's a possibility haha.
I don't know what the demand would be, though :/
Z
Icemanbrfc
Honorary Master
hahaha, thanks. would be quite cool to have an Android app
Right! So it took me 3 hours to realise that the reason it wasn't working was because I had to tell Android that my app needed to access the internet.
Frightfully irritating.
Icemanbrfc
Honorary Master
so when is the Beta version ready?