Icemanbrfc
Honorary Master
You going to have to email or phone them buddy for support.
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
Broken again, slow and sluggish as hell
same problem here
Provide them with tests, without tests they cannot fix the issue.
And remember to send them an invoice for your time, because you're now doing their work for them.
Provide them with tests, without tests they cannot fix the issue.
And remember to send them an invoice for your time, because you're now doing their work for them. Bill it at R2k an hour and tell them you bill for full hours, not partial hours.
You going to have to email or phone them buddy for support.
+1lol why use them if you have so many issues. It is not the end of the world to do tests worth five minutes of your time.
lol why use them if you have so many issues. It is not the end of the world to do tests worth five minutes of your time.
Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. All rights reserved.
C:\Users\Lara>tracert google.com
Tracing route to google.com [216.58.223.46]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 24 ms 23 ms 24 ms cpt-tx2.ip.adsl.co.za [169.1.5.81]
4 24 ms 23 ms 23 ms cpt-rx2.ip.adsl.co.za [169.1.5.82]
5 27 ms 25 ms 23 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 17 ms 17 ms 18 ms 41.164.52.40
7 44 ms 45 ms 45 ms 172.18.1.162
8 46 ms 45 ms 45 ms 72.14.194.206
9 39 ms 39 ms 39 ms 72.14.239.129
10 45 ms 45 ms 45 ms jnb01s08-in-f46.1e100.net [216.58.223.46]
Trace complete.
C:\Users\Lara>ping bras.afrihost.com
Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=6ms TTL=63
Reply from 155.239.255.250: bytes=32 time=6ms TTL=63
Reply from 155.239.255.250: bytes=32 time=6ms TTL=63
Reply from 155.239.255.250: bytes=32 time=6ms TTL=63
Ping statistics for 155.239.255.250:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 6ms, Maximum = 6ms, Average = 6ms
Mine isn't that high.
Code:Microsoft Windows [Version 10.0.10586] (c) 2015 Microsoft Corporation. All rights reserved. C:\Users\Lara>tracert google.com Tracing route to google.com [216.58.223.46] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.1.1 2 * * * Request timed out. 3 24 ms 23 ms 24 ms cpt-tx2.ip.adsl.co.za [169.1.5.81] 4 24 ms 23 ms 23 ms cpt-rx2.ip.adsl.co.za [169.1.5.82] 5 27 ms 25 ms 23 ms cpt-net1.ip.adsl.co.za [169.1.5.128] 6 17 ms 17 ms 18 ms 41.164.52.40 7 44 ms 45 ms 45 ms 172.18.1.162 8 46 ms 45 ms 45 ms 72.14.194.206 9 39 ms 39 ms 39 ms 72.14.239.129 10 45 ms 45 ms 45 ms jnb01s08-in-f46.1e100.net [216.58.223.46] Trace complete. C:\Users\Lara>ping bras.afrihost.com Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data: Reply from 155.239.255.250: bytes=32 time=6ms TTL=63 Reply from 155.239.255.250: bytes=32 time=6ms TTL=63 Reply from 155.239.255.250: bytes=32 time=6ms TTL=63 Reply from 155.239.255.250: bytes=32 time=6ms TTL=63 Ping statistics for 155.239.255.250: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 6ms, Maximum = 6ms, Average = 6ms
I must admit reading all of this compared to the praise given in the CW forum is a bit disconcerting... I only get my line installed tomo but jumped the gun and signed up since it was only R1. Either way it doesn't give me long to test and not sure if I must risk handing my line to AH either....