Afrihost Business Uncapped Feedback

Zertop · Jun 17, 2014

AfriMan said:
I'm not aware of any issues like this. I was playing videos via FB this weekend over my home WiFi and it seemed pretty normal.

Did the video just never load or did you get an error? Maybe the video wasn't cached locally and took longer to load?

Yea, it's a bit weird.

Now that I'm at home - I can test again. It just basically says "Failed to open video" on every single video tried on a mobile device. But I will try troubleshoot

Z

coolfuze · Jun 17, 2014

Zertop said:
Yea, doesn't look great

How does it perform with another account?

Z

Unfortunately don't have another account to test with.

AfriGuy · Jun 17, 2014

coolfuze said:
Unfortunately don't have another account to test with.

Give the Telkom guest account a shot, it'll show the response between your router and the exchange

Zertop · Jun 17, 2014

coolfuze said:
Unfortunately don't have another account to test with.

You could try with the telkom guest account

Username: guest1@telkomadsl
Password: guest1

Z

EDIT: AfriGuy beat me too it

coolfuze · Jun 17, 2014

Thanks, I tried the guest account but I don't seem to be able to do anything except ping or tracert telkom and visit their website, remind me how do i check connection between me and exchange again, I assume tracert.

Zertop · Jun 17, 2014

coolfuze said:
Thanks, I tried the guest account but I don't seem to be able to do anything except ping or tracert telkom and visit their website, remind me how do i check connection between me and exchange again, I assume tracert.

You can just run my second tool again

Z

coolfuze · Jun 17, 2014

Zertop said:
You can just run my second tool again

Z

I tried but it wouldn't go past the checking for updates screen

Zertop · Jun 17, 2014

coolfuze said:
I tried but it wouldn't go past the checking for updates screen

Hmm.. Weird. It should just skip it. Okay - let me troubleshoot that

AfriGuy · Jun 17, 2014

coolfuze said:
I tried but it wouldn't go past the checking for updates screen

You can give our network test app a shot too

Should show the response times between hop 1 and 2.

coolfuze · Jun 17, 2014

AfriGuy said:
You can give our network test app a shot too Should show the response times between hop 1 and 2.

Thanks, I'll give it a try and let you know, btw your app file size is listed wrong on https://www.afrihost.com/site/page/afrihost_network_test

It shows that it's 50MB but it's actually half that

AfriGuy · Jun 17, 2014

coolfuze said:
Thanks, I'll give it a try and let you know, btw your app file size is listed wrong on https://www.afrihost.com/site/page/afrihost_network_test

It shows that it's 50MB but it's actually half that

Thanks, I'll check it out and let our guys know

coolfuze · Jun 17, 2014

From AH's network test app i get
Ping Test:

ping 197.242.144.102

Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5

ping 8.8.8.8

Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5

Trace Test:

traceroute -n 197.242.144.102

1 192.168.1.1 1 ms 1 ms
2 165.145.112.1 8 ms 11 ms
3 Request timed out * *
4 Request timed out * *
5 Request timed out * *
6 Request timed out * *
7 Request timed out * *
8 Request timed out * *
9 Request timed out * *
10 Request timed out * *
11 Request timed out * *
12 Request timed out * *
13 Request timed out * *
14 Request timed out * *
15 Request timed out * *
16 Request timed out * *
17 Request timed out * *
18 Request timed out * *
19 Request timed out * *
20 Request timed out * *
21 Request timed out * *
22 Request timed out * *
23 Request timed out * *
24 Request timed out * *
25 Request timed out * *
26 Request timed out * *
27 Request timed out * *
28 Request timed out * *
29 Request timed out * *
30 Request timed out * *

traceroute -n 8.8.8.8

1 192.168.1.1 1 ms
2 165.145.112.1 7 ms
3 Request timed out *
4 Request timed out *
5 Request timed out *
6 Request timed out *
7 Request timed out *
8 Request timed out *
9 Request timed out *
10 Request timed out *
11 Request timed out *
12 Request timed out *
13 Request timed out *
14 Request timed out *
15 Request timed out *
16 Request timed out *
17 Request timed out *
18 Request timed out *
19 Request timed out *
20 Request timed out *
21 Request timed out *
22 Request timed out *
23 Request timed out *
24 Request timed out *
25 Request timed out *
26 Request timed out *
27 Request timed out *
28 Request timed out *
29 Request timed out *
30 Request timed out *

DNS Test:

nslookup www.afrihost.com

Name: www.afrihost.com
Address: 197.242.144.102

nslookup www.google.com

Name: www.google.com
Address: 74.125.233.82
Name: www.google.com
Address: 74.125.233.83
Name: www.google.com
Address: 74.125.233.80
Name: www.google.com
Address: 74.125.233.84
Name: www.google.com
Address: 74.125.233.81

nslookup thishouldfail.afrihost.com

** server can't find thisshouldfail.com: NXDOMAIN

[EDIT] Also with the linetool I get 80 was unexpected at this time. I edited the bat file to delete the update part

AfriGuy · Jun 17, 2014

coolfuze said:
From AH's network test app i get
Ping Test:

ping 197.242.144.102

Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5

ping 8.8.8.8

Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5

Trace Test:

traceroute -n 197.242.144.102

1 192.168.1.1 1 ms 1 ms
2 165.145.112.1 8 ms 11 ms
3 Request timed out * *
4 Request timed out * *
5 Request timed out * *
6 Request timed out * *
7 Request timed out * *
8 Request timed out * *
9 Request timed out * *
10 Request timed out * *
11 Request timed out * *
12 Request timed out * *
13 Request timed out * *
14 Request timed out * *
15 Request timed out * *
16 Request timed out * *
17 Request timed out * *
18 Request timed out * *
19 Request timed out * *
20 Request timed out * *
21 Request timed out * *
22 Request timed out * *
23 Request timed out * *
24 Request timed out * *
25 Request timed out * *
26 Request timed out * *
27 Request timed out * *
28 Request timed out * *
29 Request timed out * *
30 Request timed out * *

traceroute -n 8.8.8.8

1 192.168.1.1 1 ms
2 165.145.112.1 7 ms
3 Request timed out *
4 Request timed out *
5 Request timed out *
6 Request timed out *
7 Request timed out *
8 Request timed out *
9 Request timed out *
10 Request timed out *
11 Request timed out *
12 Request timed out *
13 Request timed out *
14 Request timed out *
15 Request timed out *
16 Request timed out *
17 Request timed out *
18 Request timed out *
19 Request timed out *
20 Request timed out *
21 Request timed out *
22 Request timed out *
23 Request timed out *
24 Request timed out *
25 Request timed out *
26 Request timed out *
27 Request timed out *
28 Request timed out *
29 Request timed out *
30 Request timed out *

DNS Test:

nslookup www.afrihost.com

Name: www.afrihost.com
Address: 197.242.144.102

nslookup www.google.com

Name: www.google.com
Address: 74.125.233.82
Name: www.google.com
Address: 74.125.233.83
Name: www.google.com
Address: 74.125.233.80
Name: www.google.com
Address: 74.125.233.84
Name: www.google.com
Address: 74.125.233.81

nslookup thishouldfail.afrihost.com

** server can't find thisshouldfail.com: NXDOMAIN

The exchange is looking OK here, do you see the same results when testing from your Afrihost account?

coolfuze · Jun 17, 2014

On my AH account, which is 2Mb business I get
Ping Test:

ping 197.242.144.102

64 bytes from 197.242.144.102: icmp_req=1 ttl=58 time=21 ms
Request timeout for icmp_seq 2
64 bytes from 197.242.144.102: icmp_req=3 ttl=58 time=19 ms
64 bytes from 197.242.144.102: icmp_req=4 ttl=58 time=19 ms
64 bytes from 197.242.144.102: icmp_req=5 ttl=58 time=18 ms

ping 8.8.8.8

64 bytes from 8.8.8.8: icmp_req=1 ttl=42 time=185 ms
64 bytes from 8.8.8.8: icmp_req=2 ttl=42 time=184 ms
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
64 bytes from 8.8.8.8: icmp_req=5 ttl=42 time=183 ms

Trace Test:

traceroute -n 197.242.144.102

1 192.168.1.1 1 ms 1 ms 1 ms
2 105.236.14.1 7 ms 8 ms 8 ms
3 41.181.221.2 17 ms 17 ms 17 ms
4 41.181.165.1 17 ms 20 ms
196.44.31.1 19 ms
5 196.44.31.1 19 ms 22 ms
196.44.31.9 19 ms
6 196.44.0.2 19 ms
196.30.1.3 18 ms
196.44.31.9 18 ms
7 196.30.1.3 19 ms 20 ms
196.31.220.2 20 ms
8 196.31.220.2 19 ms 20 ms
196.31.63.2 18 ms
9 196.30.42.1 17 ms 20 ms
196.31.63.2 18 ms
10 197.242.144.1 19 ms 19 ms
196.30.42.1 18 ms
11 197.242.144.1 19 ms

traceroute -n 8.8.8.8

1 192.168.1.1 1 ms 1 ms 1 ms
2 105.236.14.1 7 ms 7 ms 8 ms
3 41.181.221.2 31 ms 17 ms 17 ms
4 41.181.165.1 18 ms 20 ms 17 ms
5 196.44.31.1 19 ms 21 ms 18 ms
6 41.181.139.1 33 ms 20 ms 24 ms
7 72.14.194.7 18 ms 22 ms 19 ms
8 66.249.95.8 179 ms
Request timed out * *
9 Request timed out *

DNS Test:

nslookup www.afrihost.com

Name: www.afrihost.com
Address: 197.242.144.102

nslookup www.google.com

Name: www.google.com
Address: 173.194.41.82
Name: www.google.com
Address: 173.194.41.83
Name: www.google.com
Address: 173.194.41.84
Name: www.google.com
Address: 173.194.41.80
Name: www.google.com
Address: 173.194.41.81

nslookup thishouldfail.afrihost.com

** server can't find thisshouldfail.com: NXDOMAIN

Zertop · Jun 17, 2014

coolfuze said:
/SNIP/

Please would you run this while on your telkom account

ping 165.145.112.1 -n 30

And post results here

Z

coolfuze · Jun 17, 2014

Here we go, from the telkom account
Pinging 165.145.112.1 with 32 bytes of data:
Reply from 165.145.112.1: bytes=32 time=9ms TTL=254
Reply from 165.145.112.1: bytes=32 time=10ms TTL=254
Reply from 165.145.112.1: bytes=32 time=11ms TTL=254
Reply from 165.145.112.1: bytes=32 time=11ms TTL=254
Reply from 165.145.112.1: bytes=32 time=11ms TTL=254
Reply from 165.145.112.1: bytes=32 time=9ms TTL=254
Reply from 165.145.112.1: bytes=32 time=10ms TTL=254
Reply from 165.145.112.1: bytes=32 time=10ms TTL=254
Reply from 165.145.112.1: bytes=32 time=10ms TTL=254
Reply from 165.145.112.1: bytes=32 time=10ms TTL=254
Reply from 165.145.112.1: bytes=32 time=10ms TTL=254
Reply from 165.145.112.1: bytes=32 time=10ms TTL=254
Reply from 165.145.112.1: bytes=32 time=10ms TTL=254
Reply from 165.145.112.1: bytes=32 time=10ms TTL=254
Reply from 165.145.112.1: bytes=32 time=10ms TTL=254
Reply from 165.145.112.1: bytes=32 time=9ms TTL=254
Reply from 165.145.112.1: bytes=32 time=9ms TTL=254
Reply from 165.145.112.1: bytes=32 time=13ms TTL=254
Reply from 165.145.112.1: bytes=32 time=10ms TTL=254
Reply from 165.145.112.1: bytes=32 time=11ms TTL=254
Reply from 165.145.112.1: bytes=32 time=9ms TTL=254
Reply from 165.145.112.1: bytes=32 time=16ms TTL=254
Reply from 165.145.112.1: bytes=32 time=9ms TTL=254
Reply from 165.145.112.1: bytes=32 time=13ms TTL=254
Reply from 165.145.112.1: bytes=32 time=12ms TTL=254
Reply from 165.145.112.1: bytes=32 time=13ms TTL=254
Reply from 165.145.112.1: bytes=32 time=9ms TTL=254
Reply from 165.145.112.1: bytes=32 time=9ms TTL=254
Reply from 165.145.112.1: bytes=32 time=10ms TTL=254
Reply from 165.145.112.1: bytes=32 time=10ms TTL=254

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

Zertop · Jun 17, 2014

coolfuze said:
Here we go, from the telkom account
Pinging 165.145.112.1 with 32 bytes of data:
Reply from 165.145.112.1: bytes=32 time=9ms TTL=254
Reply from 165.145.112.1: bytes=32 time=10ms TTL=254
Reply from 165.145.112.1: bytes=32 time=11ms TTL=254
Reply from 165.145.112.1: bytes=32 time=11ms TTL=254
Reply from 165.145.112.1: bytes=32 time=11ms TTL=254
Reply from 165.145.112.1: bytes=32 time=9ms TTL=254
Reply from 165.145.112.1: bytes=32 time=10ms TTL=254
Reply from 165.145.112.1: bytes=32 time=10ms TTL=254
Reply from 165.145.112.1: bytes=32 time=10ms TTL=254
Reply from 165.145.112.1: bytes=32 time=10ms TTL=254
Reply from 165.145.112.1: bytes=32 time=10ms TTL=254
Reply from 165.145.112.1: bytes=32 time=10ms TTL=254
Reply from 165.145.112.1: bytes=32 time=10ms TTL=254
Reply from 165.145.112.1: bytes=32 time=10ms TTL=254
Reply from 165.145.112.1: bytes=32 time=10ms TTL=254
Reply from 165.145.112.1: bytes=32 time=9ms TTL=254
Reply from 165.145.112.1: bytes=32 time=9ms TTL=254
Reply from 165.145.112.1: bytes=32 time=13ms TTL=254
Reply from 165.145.112.1: bytes=32 time=10ms TTL=254
Reply from 165.145.112.1: bytes=32 time=11ms TTL=254
Reply from 165.145.112.1: bytes=32 time=9ms TTL=254
Reply from 165.145.112.1: bytes=32 time=16ms TTL=254
Reply from 165.145.112.1: bytes=32 time=9ms TTL=254
Reply from 165.145.112.1: bytes=32 time=13ms TTL=254
Reply from 165.145.112.1: bytes=32 time=12ms TTL=254
Reply from 165.145.112.1: bytes=32 time=13ms TTL=254
Reply from 165.145.112.1: bytes=32 time=9ms TTL=254
Reply from 165.145.112.1: bytes=32 time=9ms TTL=254
Reply from 165.145.112.1: bytes=32 time=10ms TTL=254
Reply from 165.145.112.1: bytes=32 time=10ms TTL=254

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

Looking solid

. This is the part where AfriMan/AfriGuy help some more

Z

AfriGuy · Jun 17, 2014

coolfuze said:
Here we go, from the telkom account
Pinging 165.145.112.1 with 32 bytes of data:
Reply from 165.145.112.1: bytes=32 time=9ms TTL=254
Reply from 165.145.112.1: bytes=32 time=10ms TTL=254
Reply from 165.145.112.1: bytes=32 time=11ms TTL=254
Reply from 165.145.112.1: bytes=32 time=11ms TTL=254
Reply from 165.145.112.1: bytes=32 time=11ms TTL=254
Reply from 165.145.112.1: bytes=32 time=9ms TTL=254
Reply from 165.145.112.1: bytes=32 time=10ms TTL=254
Reply from 165.145.112.1: bytes=32 time=10ms TTL=254
Reply from 165.145.112.1: bytes=32 time=10ms TTL=254
Reply from 165.145.112.1: bytes=32 time=10ms TTL=254
Reply from 165.145.112.1: bytes=32 time=10ms TTL=254
Reply from 165.145.112.1: bytes=32 time=10ms TTL=254
Reply from 165.145.112.1: bytes=32 time=10ms TTL=254
Reply from 165.145.112.1: bytes=32 time=10ms TTL=254
Reply from 165.145.112.1: bytes=32 time=10ms TTL=254
Reply from 165.145.112.1: bytes=32 time=9ms TTL=254
Reply from 165.145.112.1: bytes=32 time=9ms TTL=254
Reply from 165.145.112.1: bytes=32 time=13ms TTL=254
Reply from 165.145.112.1: bytes=32 time=10ms TTL=254
Reply from 165.145.112.1: bytes=32 time=11ms TTL=254
Reply from 165.145.112.1: bytes=32 time=9ms TTL=254
Reply from 165.145.112.1: bytes=32 time=16ms TTL=254
Reply from 165.145.112.1: bytes=32 time=9ms TTL=254
Reply from 165.145.112.1: bytes=32 time=13ms TTL=254
Reply from 165.145.112.1: bytes=32 time=12ms TTL=254
Reply from 165.145.112.1: bytes=32 time=13ms TTL=254
Reply from 165.145.112.1: bytes=32 time=9ms TTL=254
Reply from 165.145.112.1: bytes=32 time=9ms TTL=254
Reply from 165.145.112.1: bytes=32 time=10ms TTL=254
Reply from 165.145.112.1: bytes=32 time=10ms TTL=254

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

Drop me a PM with your DSL username, I'll check things out from my end

coolfuze · Jun 17, 2014

Zertop said:
Looking solid . This is the part where AfriMan/AfriGuy help some more

Z

Indeed, indeed

Weird thing is I called AH earlier and they helped me recreate the port, ever since then my TP-Link router has been showing a Download rate of 1536 instead of the usual 2048

Zertop · Jun 17, 2014

coolfuze said:
Indeed, indeed Weird thing is I called AH earlier and they helped me recreate the port, ever since then my TP-Link router has been showing a Download rate of 1536 instead of the usual 2048

That might have stabilised your line then! Could you please do a "Test my Line" from clientzone and post the results here

Z

Afrihost Business Uncapped Feedback

Expert Member

Member

Afrihost

Expert Member

Member

Expert Member

Member

Expert Member

Afrihost

Member

Afrihost

Member

Afrihost

Member

Expert Member

Member

Expert Member

Afrihost

Member

Expert Member