Afrihost Network Test App

Spaj

Well-Known Member
Joined
Jan 27, 2010
Messages
227
Reaction score
97
Location
Durban
Hi

Any tried the Afrihost Network App yet!

My attempt crashed on install :wtf:! (Win7)
 
Hi

Any tried the Afrihost Network App yet!

My attempt crashed on install :wtf:! (Win7)

Mine installed fine (maybe a corrupt sip file? download again) but doesn't produce accurate results. There are random timeouts on the ping and tracert, if I do these tests manually then there isn't a problem, and I don't have a problem, was just trying out the app.
 
Mine installed fine (maybe a corrupt sip file? download again) but doesn't produce accurate results. There are random timeouts on the ping and tracert, if I do these tests manually then there isn't a problem, and I don't have a problem, was just trying out the app.

It's pretty accurate for me. Results correlate well with manual test.
 
On a Mac. Installed and ran fine.

Did manual testing. Seems to be accurate.
 
I just launched it again now to show you guys, but it came up with "update available".

Busy downloading now and will post the results.
 
New AH App, same issue:

Ping Test:

ping 197.242.144.102

64 bytes from 197.242.144.102: icmp_req=1 ttl=55 time=40 ms
64 bytes from 197.242.144.102: icmp_req=2 ttl=55 time=60 ms
64 bytes from 197.242.144.102: icmp_req=3 ttl=55 time=43 ms
64 bytes from 197.242.144.102: icmp_req=4 ttl=55 time=176 ms
64 bytes from 197.242.144.102: icmp_req=5 ttl=55 time=24 ms


ping 8.8.8.8

Request timeout for icmp_seq 1
64 bytes from 8.8.8.8: icmp_req=2 ttl=44 time=220 ms
64 bytes from 8.8.8.8: icmp_req=3 ttl=44 time=232 ms
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 196.210.157.1 29 ms 31 ms
3 196.38.73.2 24 ms 49 ms
4 196.38.73.9 43 ms
168.209.1.1 189 ms
5 168.209.1.1 58 ms
196.26.0.1 69 ms
6 41.208.29.1 169 ms
196.44.0.2 46 ms
7 196.44.0.2 31 ms
196.44.31.9 61 ms
8 196.44.31.9 41 ms
196.30.1.3 39 ms
9 196.31.220.2 41 ms 42 ms
10 196.31.63.1 48 ms 39 ms
11 197.242.144.1 37 ms 121 ms


traceroute -n 8.8.8.8

1 192.168.1.1 1 ms 1 ms
2 196.210.157.1 25 ms 52 ms
3 196.38.73.9 41 ms
196.38.73.2 38 ms
4 168.209.1.1 26 ms
196.38.73.9 37 ms
5 196.26.0.1 43 ms
168.209.1.1 21 ms
6 74.125.49.6 43 ms
196.26.0.1 27 ms
7 66.249.95.8 212 ms
74.125.49.6 43 ms
8 Request timed out *
66.249.95.8 209 ms
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: 74.125.233.83
Name: www.google.com
Address: 74.125.233.81
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.82


nslookup thishouldfail.afrihost.com

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

Manual tests:

ping 197.242.144.102 -t

Pinging 197.242.144.102 with 32 bytes of data:
Reply from 197.242.144.102: bytes=32 time=24ms TTL=55
Reply from 197.242.144.102: bytes=32 time=29ms TTL=55
Reply from 197.242.144.102: bytes=32 time=26ms TTL=55
Reply from 197.242.144.102: bytes=32 time=23ms TTL=55
Reply from 197.242.144.102: bytes=32 time=24ms TTL=55
Reply from 197.242.144.102: bytes=32 time=26ms TTL=55
Reply from 197.242.144.102: bytes=32 time=23ms TTL=55
Reply from 197.242.144.102: bytes=32 time=23ms TTL=55
Reply from 197.242.144.102: bytes=32 time=24ms TTL=55
Reply from 197.242.144.102: bytes=32 time=33ms TTL=55
Reply from 197.242.144.102: bytes=32 time=25ms TTL=55
Reply from 197.242.144.102: bytes=32 time=25ms TTL=55
Reply from 197.242.144.102: bytes=32 time=24ms TTL=55
Reply from 197.242.144.102: bytes=32 time=24ms TTL=55
Reply from 197.242.144.102: bytes=32 time=24ms TTL=55

Ping statistics for 197.242.144.102:
Packets: Sent = 15, Received = 15, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 23ms, Maximum = 33ms, Average = 25ms
Control-C
^C

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=199ms TTL=44
Reply from 8.8.8.8: bytes=32 time=201ms TTL=44
Reply from 8.8.8.8: bytes=32 time=198ms TTL=44
Reply from 8.8.8.8: bytes=32 time=202ms TTL=44
Reply from 8.8.8.8: bytes=32 time=297ms TTL=44
Reply from 8.8.8.8: bytes=32 time=213ms TTL=44
Reply from 8.8.8.8: bytes=32 time=205ms TTL=44
Reply from 8.8.8.8: bytes=32 time=276ms TTL=44
Reply from 8.8.8.8: bytes=32 time=216ms TTL=44
Reply from 8.8.8.8: bytes=32 time=215ms TTL=44
Reply from 8.8.8.8: bytes=32 time=198ms TTL=44
Reply from 8.8.8.8: bytes=32 time=202ms TTL=44

Ping statistics for 8.8.8.8:
Packets: Sent = 12, Received = 12, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 198ms, Maximum = 297ms, Average = 218ms
Control-C

tracert 197.242.144.102

Tracing route to cms-gm.afrihost.com [197.242.144.102]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 12 ms 13 ms 9 ms 196-210-157-1.dynamic.isadsl.co.za [196.210.157.
1]
3 22 ms 22 ms 26 ms cdsl2-rba-vl2563.ip.isnet.net [196.38.73.213]
4 39 ms 34 ms 33 ms cdsl2-rba-vl150.ip.isnet.net [196.38.73.9]
5 20 ms 20 ms 25 ms 168.209.1.140
6 43 ms 24 ms 23 ms 196.26.0.130
7 84 ms 54 ms 46 ms 41-208-29-126.mtnns.net [41.208.29.126]
8 22 ms 22 ms 22 ms jh-cr-2.za--jh-pr-1.za.mtnns.net [196.44.0.223]

9 21 ms 21 ms 21 ms 196.44.31.99
10 40 ms 43 ms 41 ms 196.30.1.39
11 27 ms 22 ms 22 ms tengigabitethernet1-1.gw21.jnb6.za.mtnbusiness.n
et [196.31.220.21]
12 27 ms 23 ms 21 ms tengigabitethernet5-2.hr15.jnb6.za.mtnbusiness.n
et [196.31.63.194]
13 22 ms 21 ms 22 ms cms-gm.afrihost.com [197.242.144.102]

Trace complete.

tracert 8.8.8.8

Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 10 ms 9 ms 9 ms 196-210-157-1.dynamic.isadsl.co.za [196.210.157.
1]
3 74 ms 21 ms 21 ms cdsl2-rba-vl2563.ip.isnet.net [196.38.73.213]
4 24 ms 30 ms 29 ms cdsl2-rba-vl150.ip.isnet.net [196.38.73.9]
5 51 ms 21 ms 20 ms 168.209.1.140
6 23 ms 25 ms 23 ms 196.26.0.130
7 21 ms 20 ms 25 ms 74.125.49.66
8 197 ms 196 ms 195 ms 66.249.95.8
9 194 ms 196 ms 195 ms 209.85.244.240
10 205 ms 244 ms 213 ms 72.14.242.166
11 199 ms 205 ms 201 ms 209.85.252.83
12 * * * Request timed out.
13 200 ms 199 ms 200 ms google-public-dns-a.google.com [8.8.8.8]

Trace complete.

Like I said, I don't have any issues so this doesn't faze me. Nice idea tho for the people that are noobs, just a bit concerned that it will complicate matters when it's showing problems when there are none.
 
Its a good App, but those programmers need some lessons on programming, how the hell is the most simple ping/trace app 93MB? seriously, im sure someone could remake it under 2MB.
 
Top
Sign up to the MyBroadband newsletter
X