Stickfigure
Honorary Master
Full line speed but those hops, yuck.
-
Join the MyBroadband community
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
-
Question of the Day: What is your preferred Chinese car brand?
"Help me fix my internet" report tool
- Thread starter Zertop
- Start date
I'm getting this:
Can anyone advise what the hop 2 request timeout means?
I've been having a really rough time with the net lately. The line drops every time there is wind or rain, so there is definitely a cable fault. But Telkom doesn't actually fix it.
Last few days, I have voice line down, with just an open line with noise, but the adsl line has been fine.
Now I have the internet stop/starting constantly. Speeds stopping and going. Always seems to happen at around 6pm onwards.
Keep rebooting router, etc etc.
Checked my Vox account, and got frustrated. So tried Afrihost account, and same thing.
Now I am using Mweb...and it is going ok. The results above are from that.
Sucks when you don't know if it is your router, telkom line, isp or wifi dongle. Don't know where to even turn anymore.
Can anyone advise what the hop 2 request timeout means?
I've been having a really rough time with the net lately. The line drops every time there is wind or rain, so there is definitely a cable fault. But Telkom doesn't actually fix it.
Last few days, I have voice line down, with just an open line with noise, but the adsl line has been fine.
Now I have the internet stop/starting constantly. Speeds stopping and going. Always seems to happen at around 6pm onwards.
Keep rebooting router, etc etc.
Checked my Vox account, and got frustrated. So tried Afrihost account, and same thing.
Now I am using Mweb...and it is going ok. The results above are from that.
Sucks when you don't know if it is your router, telkom line, isp or wifi dongle. Don't know where to even turn anymore.
Wasp_21
Expert Member
Having the same issue almost word for word including line issue, and VOX ISP. Have reported to VOX 3 times now with no change, and Telkom has been twice. First time they found the voice line dead, and yesterday all is fine. Bought a new Netgear router to make sure it wasn't my side. Can only (more likely) be VOX in Durban?
Hey All!
The second hop timing out means you are activated on Telkom's new network (the second hop doesn't show up as it is cut off from responding to ping requests).
You can run my second tool (linked in my signature) to help diagnose the faults. Cut outs during rainly weather definitely points to a faulty cable connection somewhere.
Z
Those really aren't great :/ Please run my second tool linked below to diagnose fully!
Z
It sounds like you might have an exchange congestion issue (if the speed worsens at night or in the morning). Have you had a telkom technician out to check?
Z
Certainly a telkom problem if there is no widespread issue. Could you please run my second tool linked in my signature to confirm this.
Z
It sounds like you might have an exchange congestion issue (if the speed worsens at night or in the morning). Have you had a telkom technician out to check?
Z
That is my next step. Hopefully it is something minor.
Thanks for the reply.
Sometime's its as quick as a port reset! If you ask for one through the phone support, it might help fix it
Else a technician will be required :/Z
Hey All!
The second hop timing out means you are activated on Telkom's new network (the second hop doesn't show up as it is cut off from responding to ping requests).
You can run my second tool (linked in my signature) to help diagnose the faults. Cut outs during rainly weather definitely points to a faulty cable connection somewhere.
Z
Thansk Z. I know this is a ridiculous question, but for us novices, can you give some advice on running the file?
It is a .jar file...so Java right? is it just a matter of making sure Java Runtime Environment is installed, and double clicking the .jar file, or is there more to it?
Can download the .zip and extract, but then end up with a whole lot of .java files..not sure what to run and where.
Much appreciated.
Yip,
You just need to make sure java is installed (java.com/download), and then run the jar file
Z
Edit: Download jar here https://zertop.com/releases/linetool/
Think I am ready to either shoot my modem, my isp or someone from Telkom.
Zertop's LineTool Results
Date/Time: Wed Jan 06 20:24:13 CAT 2016
Basic Report:
Your packet loss was 0%.
Your average ping was 9ms.
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:
So all is fine. Except everything is still stop/start. I run it 2 minutes later, and it fails to even ping the first tests. Then run it again, and all fine. Reboot the modem every hour or so, takes a while to connect, then is fine for 30 minutes or so, and then goes to crap again.
Here's the test I ran 5 minutes after the last one:
Zertop's LineTool Results
Date/Time: Wed Jan 06 20:27:09 CAT 2016
Basic Report:
Your packet loss was 10%.
Your average ping was 9ms.
Your maximum ping was 11ms.
You seem to have some packet loss. This indicates an issue on the line.
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: Wed Jan 06 20:24:13 CAT 2016
Basic Report:
Your packet loss was 0%.
Your average ping was 9ms.
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=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms 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=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms 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 = 9ms, Maximum = 11ms, Average = 9msSo all is fine. Except everything is still stop/start. I run it 2 minutes later, and it fails to even ping the first tests. Then run it again, and all fine. Reboot the modem every hour or so, takes a while to connect, then is fine for 30 minutes or so, and then goes to crap again.
Here's the test I ran 5 minutes after the last one:
Zertop's LineTool Results
Date/Time: Wed Jan 06 20:27:09 CAT 2016
Basic Report:
Your packet loss was 10%.
Your average ping was 9ms.
Your maximum ping was 11ms.
You seem to have some packet loss. This indicates an issue on the line.
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:
Pinging 155.239.255.250 with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Request timed out.
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Request timed out.
Request timed out.
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms 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 = 27, Lost = 3 (10% loss),
Approximate round trip times in milli-seconds:
Minimum = 9ms, Maximum = 11ms, Average = 9ms
Last edited:
Definite line fault there!
Have you checked that all of your telephone connections (home phone, alarm etc) have ADSL filters on them?
Z
Yep.
Telkom been out numerous times. Each time they tell me something different, like I need to downgrade my speed (10 Meg line, set at 6 at the moment and was working fine for years at 6) or they are looking at replacing cables (but never do) or the fault must be at whatever neighbor's house that is not at home at the time, or the box down the road needs to be rebuilt, or we need to rewire the house cables, or they will come back (but they don't)
It's a never ending story.
And it is never the same Telkom technician, so it is always back to square one.
Not like I am in an outlying area either..middle of the suburbs.
I have 3 isp accounts, Netflix and Hulu, and can't make much use of any of them currently.
Ah well, not like bitching is going to help. I'd just love to be able to know exactly what the fault is, so I can force them to fix it.
Telkom been out numerous times. Each time they tell me something different, like I need to downgrade my speed (10 Meg line, set at 6 at the moment and was working fine for years at 6) or they are looking at replacing cables (but never do) or the fault must be at whatever neighbor's house that is not at home at the time, or the box down the road needs to be rebuilt, or we need to rewire the house cables, or they will come back (but they don't)
It's a never ending story.
And it is never the same Telkom technician, so it is always back to square one.
Not like I am in an outlying area either..middle of the suburbs.
I have 3 isp accounts, Netflix and Hulu, and can't make much use of any of them currently.
Ah well, not like bitching is going to help. I'd just love to be able to know exactly what the fault is, so I can force them to fix it.
Are these the WORST results ever seen here? We used to have an EXCELLENT 10 Meg line, running very fast, until Jan started.
This is from the work pc. Got back from holidays, and everyone is experiencing slow speeds, getting better later in the day. But terrible in the mornings.
While we were away, the IT consultant installed a new modem/router, added some silly Netgear firewall settings and just generally made a mess. But he's away, and I cannot tell if this is something he has done, or just a line problem.
Can you give some advice based on these shocking results:
Zertop's LineTool Results
Date/Time: Fri Jan 08 09:15:40 CAT 2016
Basic Report:
Your packet loss was 6%.
Your average ping was 1086ms.
Your maximum ping was 3096ms.
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:
This is from the work pc. Got back from holidays, and everyone is experiencing slow speeds, getting better later in the day. But terrible in the mornings.
While we were away, the IT consultant installed a new modem/router, added some silly Netgear firewall settings and just generally made a mess. But he's away, and I cannot tell if this is something he has done, or just a line problem.
Can you give some advice based on these shocking results:
Zertop's LineTool Results
Date/Time: Fri Jan 08 09:15:40 CAT 2016
Basic Report:
Your packet loss was 6%.
Your average ping was 1086ms.
Your maximum ping was 3096ms.
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=2820ms TTL=63
Reply from 155.239.255.250: bytes=32 time=1552ms TTL=63
Reply from 155.239.255.250: bytes=32 time=1005ms TTL=63
Request timed out.
Reply from 155.239.255.250: bytes=32 time=66ms TTL=63
Reply from 155.239.255.250: bytes=32 time=32ms TTL=63
Reply from 155.239.255.250: bytes=32 time=760ms TTL=63
Reply from 155.239.255.250: bytes=32 time=1657ms TTL=63
Reply from 155.239.255.250: bytes=32 time=3096ms TTL=63
Reply from 155.239.255.250: bytes=32 time=1786ms TTL=63
Reply from 155.239.255.250: bytes=32 time=1430ms TTL=63
Reply from 155.239.255.250: bytes=32 time=353ms TTL=63
Reply from 155.239.255.250: bytes=32 time=109ms TTL=63
Reply from 155.239.255.250: bytes=32 time=119ms TTL=63
Reply from 155.239.255.250: bytes=32 time=202ms TTL=63
Reply from 155.239.255.250: bytes=32 time=125ms TTL=63
Reply from 155.239.255.250: bytes=32 time=90ms TTL=63
Reply from 155.239.255.250: bytes=32 time=110ms TTL=63
Reply from 155.239.255.250: bytes=32 time=703ms TTL=63
Reply from 155.239.255.250: bytes=32 time=1391ms TTL=63
Reply from 155.239.255.250: bytes=32 time=2587ms TTL=63
Reply from 155.239.255.250: bytes=32 time=2764ms TTL=63
Reply from 155.239.255.250: bytes=32 time=1515ms TTL=63
Reply from 155.239.255.250: bytes=32 time=464ms TTL=63
Reply from 155.239.255.250: bytes=32 time=89ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=81ms TTL=63
Request timed out.
Reply from 155.239.255.250: bytes=32 time=2509ms TTL=63
Reply from 155.239.255.250: bytes=32 time=3009ms TTL=63
Ping statistics for 155.239.255.250:
Packets: Sent = 30, Received = 28, Lost = 2 (6% loss),
Approximate round trip times in milli-seconds:
Minimum = 8ms, Maximum = 3096ms, Average = 1086msThat is definitely, without question, an issue between your computer and the telkom network. Either Telkom has messed something up - or there is an issue with the firewall your IT technician set up.
Does anybody torrent on your network at home? Doing so would flood the firewall (if it is of a low usage recommendation) and display results like this!
Z