Afrihost New Network Feedback - Part 2

Status
Not open for further replies.
Certainly not Sir. I hope they fix it soon.

Have you tried to use Zertops line tool? and what does your own router diagnostics say?

BTW, just done a trace route from PTA to Afrihost and the results are terrible .......

It is just too easy to sweep issues under the "its your line" or "its the exchange" blanket ...
 
Cape Town region.

C:\>tracert www.afrihost.co.za

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

1 <1 ms <1 ms <1 ms 10.0.0.2
2 11 ms 11 ms 11 ms 169-0-44-1.ip.afrihost.co.za [169.0.44.1]
3 1516 ms 936 ms * cpt-up1.ip.adsl.co.za [169.1.5.105] <<<<<<<<<<<<---bottleneck
4 13 ms 13 ms 13 ms cpt-in1.ip.adsl.co.za [169.1.5.118]
5 20 ms 26 ms 12 ms 169-1-5-132.ip.afrihost.co.za [169.1.5.132]
6 13 ms 13 ms 16 ms optinet.ct1.napafrica.net [196.10.140.15]
7 35 ms 34 ms 35 ms bu-ether1.cpt-p-1.optinet.net [197.84.7.33]
8 47 ms 98 ms 74 ms te0-0-0-0.vic-p-2.optinet.net [197.84.4.35]
9 34 ms 34 ms 33 ms 102.te0-0-2-0.vic-tr-1.optinet.net [197.80.7.36]
10 33 ms 33 ms 32 ms 197-81-226-77.jhb.mweb.co.za [197.81.226.77]
11 36 ms 38 ms 36 ms 197-81-226-53.jhb.mweb.co.za [197.81.226.53]
12 34 ms 34 ms 34 ms 197-81-229-2.jhb.mweb.co.za [197.81.229.2]
13 34 ms 32 ms 32 ms 197-81-229-9.jhb.mweb.co.za [197.81.229.9]
14 32 ms 32 ms 32 ms 41-86-112-68.mweb.co.za [41.86.112.68]

Trace complete.

Cape Town area to international IP

C:\>tracert www.google.com

Tracing route to www.google.com [216.58.210.36]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.2
2 14 ms 10 ms 10 ms 169-0-44-1.ip.afrihost.co.za [169.0.44.1]

3 * * * Request timed out. <<<---Bottleneck

4 14 ms 12 ms 13 ms cpt-in1.ip.adsl.co.za [169.1.5.118]
5 12 ms 13 ms 12 ms 169-1-5-132.ip.afrihost.co.za [169.1.5.132]
6 12 ms 12 ms 12 ms 41.164.52.42
7 33 ms 34 ms 35 ms 172.18.1.162
8 56 ms 34 ms 35 ms 72.14.194.206
9 204 ms 204 ms 205 ms 66.249.95.8
10 197 ms 197 ms 196 ms 216.239.59.5
11 195 ms 195 ms 196 ms 108.170.232.105
12 204 ms 204 ms 204 ms lhr25s11-in-f4.1e100.net [216.58.210.36]

Trace complete.

No virus, no malware, no torrent software running in background...

It's not quite a bottleneck in the strictest sense of the word, the traceroute is still able to resolve to the target destination. That specific network point could be under more load than usual, which means it will de-prioritize non-essential traffic such as ICMP traffic requests.

I've asked our Team to check what's going on.
 
This Afrihost only go LAG LAG LAG..

Test on A WISP network with more than 10 wifi hops and get perfect networ

In the day I am getting 80ms on first hop after router on Afrihost... 20ms in WISP network!!!

This is the Service we getting for Bussiness Account!!!
 
This Afrihost only go LAG LAG LAG..

Test on A WISP network with more than 10 wifi hops and get perfect networ

In the day I am getting 80ms on first hop after router on Afrihost... 20ms in WISP network!!!

This is the Service we getting for Bussiness Account!!!

If the latency starts on the second hop, that sounds there may be an issue on your line or Exchange. :(

Do you maybe have a traceroute I can look at?
 
krusty, i added my router. Log in details ie admin and pasword but says unable to login. Do i have to be connected to ethernet to do this test?
Make sure your password is not longer than fifteen characters. :)
 
Line faults are very tricky at the moment, especially with ASSIA, often when the Team replies with the distance from Exchange answer that is the feedback that we receive directly from Telkom. :(

If there is any ever doubt I would recommend PM'ing us here.

So, I was told that the line should be synced at 2 megs .... I begged your support to ask Telkom NOT to do this. The response was that they have asked Telkom to resync the line at 4 megs ..... and tonight I sit at 2megs.
Why we spoke the last two days is beyond me.

The SNR is at 6db. Please can someone log a fault. It was at 11.5 db and quite stable.

If I wanted to do this myself, I wouldnt have handed my line over to you.


Please try to explain this to them as I seem to be battling with it ....

The line was fine at 4 megs for years. Its faulty. Please log a fault. Its that simple.

Sorry to be negative ... and sorry if I come across as aggressive ... but your support is really tough to deal with at times.
 
Last edited:
Lol no its not. But this is the app Krusty suggested i use where i cant seem to get in to check SNR stats etc
Also downloaded it and password length was the reason I couldn't log in. It doesn't provide any stats though. Maybe it is because there isn't a Windows x64 version. :(
 
Ok so i'm not having fun tonight -_-

speedtest shows everything a-ok



Though i'm struggling to download greenshot to take screenshots
 
Also downloaded it and password length was the reason I couldn't log in. It doesn't provide any stats though. Maybe it is because there isn't a Windows x64 version. :(
Make sure your router is on the list of supported devices.
Ok so i'm not having fun tonight -_-

speedtest shows everything a-ok



Though i'm struggling to download greenshot to take screenshots

If it's a game, run it in window mode.
 
Also downloaded it and password length was the reason I couldn't log in. It doesn't provide any stats though. Maybe it is because there isn't a Windows x64 version. :(
My router is there.. Admin and password is correct. But can i run this over wifi or must it be via ethernet?
 
My router is there.. Admin and password is correct. But can i run this over wifi or must it be via ethernet?
In theory there should be no difference between wired and wireless. Both interfaces are usually bridged on routers. Just check for options like SSH access and SNMP. Enable them if they are disabled and try again.
 
So, I was told that the line should be synced at 2 megs .... I begged your support to ask Telkom NOT to do this. The response was that they have asked Telkom to resync the line at 4 megs ..... and tonight I sit at 2megs.
Why we spoke the last two days is beyond me.

The SNR is at 6db. Please can someone log a fault. It was at 11.5 db and quite stable.

If I wanted to do this myself, I wouldnt have handed my line over to you.


Please try to explain this to them as I seem to be battling with it ....

The line was fine at 4 megs for years. Its faulty. Please log a fault. Its that simple.

Sorry to be negative ... and sorry if I come across as aggressive ... but your support is really tough to deal with at times.

Hi

Line stats hardly ever stay the same, there are so many factors that bring in change.
Either way, I'll happily log a fault for you - please PM me the affected number and the ticket ref#.
 
Hi

Line stats hardly ever stay the same, there are so many factors that bring in change.
Either way, I'll happily log a fault for you - please PM me the affected number and the ticket ref#.

I'm sorry, but I have to disagree with you there.

My SNR never changed (well, twice, one line fault and one faulty router) in 7 years at my previous house, and now at my second house which I've been living at for a year.
 
I'm sorry, but I have to disagree with you there.

My SNR never changed (well, twice, one line fault and one faulty router) in 7 years at my previous house, and now at my second house which I've been living at for a year.

It's a pretty big generalisation, but line stats can and do change.
 
Make sure your router is on the list of supported devices.


If it's a game, run it in window mode.

My router is a Dlink 2750u and its running fine on the 2740b Model :), I'm using Ethernet to answer Iceman's Question. If its a telkom router, it could be blocking the Telnet port :P, if that's the case. Create a port forwarding rule for port 23 and add a static IP on your computer and assign the port to that IP and try again. Just remember to delete the port afterwards and set you pc back to DHCP :). Also note the Netgear message about debug mode.

DSL.PNG
 
Last edited:
My router is a Dlink 2750u and its running fine on the 2740b Model :), I'm using Ethernet to answer Iceman's Question. If its a telkom router, it could be blocking the Telnet port :P, if that's the case. Create a port forwarding rule for port 23 and add a static IP on your computer and assign the port to that IP and try again. Just remember to delete the port afterwards and set you pc back to DHCP :). Also note the Netgear message about debug mode.

View attachment 364634
Cheers will have a look again tonight lol
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X