Afrihost New Network Feedback

[AfriGuy]

Now torrents stopped just after 18:00. Did all the tests and posted them on the ticket.

Sitting at downloading metadata for the past 24 mins, the torrent is 50mb

Have you tried this yet?

Please test using our DNS servers to see if the experience is the same.
Both sites open quickly for me.

 

[KinsZA]

Have you tried this yet?

Tracing route to twitter.com [199.16.156.230]

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 20 ms 20 ms 20 ms dbn-up2.ip.adsl.co.za [169.1.5.174]
4 19 ms 19 ms 19 ms 169-1-5-208.ip.afrihost.co.za [169.1.5.208]
5 20 ms 20 ms 20 ms 41.162.84.194
6 28 ms 28 ms 28 ms 172.18.1.162
7 28 ms 28 ms 28 ms if-ae-7-0.tcore2.jso-johannesburg.as6453.net [41.206.179.13]
8 300 ms 284 ms 274 ms if-ae-6-2.tcore2.klt-cape-town.as6453.net [41.206.179.10]
9 360 ms 403 ms 373 ms if-ae-2-2.tcore1.klt-cape-town.as6453.net [41.206.164.253]
10 207 ms 207 ms 207 ms if-ae-5-40.tcore2.pv9-lisbon.as6453.net [80.231.159.89]
11 291 ms 293 ms 293 ms if-ae-2-2.tcore1.pv9-lisbon.as6453.net [80.231.158.5]
12 379 ms 376 ms 356 ms if-ae-1-3.tcore1.sv8-highbridge.as6453.net [80.231.158.30]
13 291 ms * 290 ms if-ae-19-2.tcore2.l78-london.as6453.net [80.231.138.22]
14 208 ms 208 ms 208 ms if-ae-2-2.tcore1.l78-london.as6453.net [80.231.131.2]
15 195 ms 197 ms 194 ms if-ae-17-2.tcore1.ldn-london.as6453.net [80.231.130.130]
16 202 ms 202 ms 203 ms 195.219.83.102
17 359 ms 362 ms 362 ms ae-236-3612.edge5.london1.level3.net [4.69.166.61]
18 215 ms 198 ms 198 ms twitter-inc.edge5.london1.level3.net [195.50.120.66]
19 * * * Request timed out.
20 365 ms 371 ms 374 ms 199.16.156.102


Tracing route to twitter.com [199.16.156.230]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 21 ms 19 ms 20 ms dbn-up2.ip.adsl.co.za [169.1.5.174]
4 19 ms 18 ms 20 ms 169-1-5-208.ip.afrihost.co.za [169.1.5.208]
5 20 ms 19 ms 20 ms 41.162.84.194
6 28 ms 28 ms 28 ms 172.18.1.162
7 27 ms 28 ms 28 ms if-ae-7-0.tcore1.jso-johannesburg.as6453.net [41.206.178.29]
8 198 ms 195 ms 199 ms if-ae-2-2.tcore2.jso-johannesburg.as6453.net [216.6.55.86]
9 305 ms 304 ms 298 ms if-ae-6-2.tcore2.klt-cape-town.as6453.net [41.206.179.10]
10 378 ms 358 ms 353 ms if-ae-2-2.tcore1.klt-cape-town.as6453.net [41.206.164.253]
11 * 364 ms 365 ms if-ae-5-90.tcore2.pv9-lisbon.as6453.net [80.231.159.109]
12 294 ms 296 ms 293 ms if-ae-2-2.tcore1.pv9-lisbon.as6453.net [80.231.158.5]
13 369 ms 371 ms 378 ms if-ae-1-3.tcore1.sv8-highbridge.as6453.net [80.231.158.30]
14 374 ms 373 ms 376 ms if-ae-2-2.tcore2.sv8-highbridge.as6453.net [80.231.139.1]
15 205 ms 201 ms 208 ms if-ae-11-2.tcore1.l78-london.as6453.net [80.231.139.42]
16 205 ms 212 ms 215 ms if-ae-17-2.tcore1.ldn-london.as6453.net [80.231.130.130]
17 202 ms 202 ms 203 ms 195.219.83.102
18 200 ms 199 ms 201 ms ae-126-3512.edge5.london1.level3.net [4.69.166.45]
19 199 ms 199 ms 199 ms twitter-inc.edge5.london1.level3.net [195.50.120.66]
20 * * * Request timed out.
21 279 ms 279 ms 279 ms 199.16.156.230

 

[PurSpyk!!]

Have you tried this yet?

These open fine now, given up on the torrent, I am currently downloading the latest Windows 10 Insider build ( I need to actually get some work done), amazing how fast this downloads and its over 4GB, but a 50mb torrent sits for 24 minutes not doing a thing.

I have now done all the tests I was asked to do, so please don't say I have not been willing to do my part. Now its up to you to sort this out, and get this to Critical Care if normal support is unable to assist. I don't see why I must rehash all of this if there is a support ticket that can be sent to them.

 

[AfriGuy]

Tracing route to twitter.com [199.16.156.230]

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 20 ms 20 ms 20 ms dbn-up2.ip.adsl.co.za [169.1.5.174]
4 19 ms 19 ms 19 ms 169-1-5-208.ip.afrihost.co.za [169.1.5.208]
5 20 ms 20 ms 20 ms 41.162.84.194
6 28 ms 28 ms 28 ms 172.18.1.162
7 28 ms 28 ms 28 ms if-ae-7-0.tcore2.jso-johannesburg.as6453.net [41.206.179.13]
8 300 ms 284 ms 274 ms if-ae-6-2.tcore2.klt-cape-town.as6453.net [41.206.179.10]
9 360 ms 403 ms 373 ms if-ae-2-2.tcore1.klt-cape-town.as6453.net [41.206.164.253]
10 207 ms 207 ms 207 ms if-ae-5-40.tcore2.pv9-lisbon.as6453.net [80.231.159.89]
11 291 ms 293 ms 293 ms if-ae-2-2.tcore1.pv9-lisbon.as6453.net [80.231.158.5]
12 379 ms 376 ms 356 ms if-ae-1-3.tcore1.sv8-highbridge.as6453.net [80.231.158.30]
13 291 ms * 290 ms if-ae-19-2.tcore2.l78-london.as6453.net [80.231.138.22]
14 208 ms 208 ms 208 ms if-ae-2-2.tcore1.l78-london.as6453.net [80.231.131.2]
15 195 ms 197 ms 194 ms if-ae-17-2.tcore1.ldn-london.as6453.net [80.231.130.130]
16 202 ms 202 ms 203 ms 195.219.83.102
17 359 ms 362 ms 362 ms ae-236-3612.edge5.london1.level3.net [4.69.166.61]
18 215 ms 198 ms 198 ms twitter-inc.edge5.london1.level3.net [195.50.120.66]
19 * * * Request timed out.
20 365 ms 371 ms 374 ms 199.16.156.102


Tracing route to twitter.com [199.16.156.230]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 21 ms 19 ms 20 ms dbn-up2.ip.adsl.co.za [169.1.5.174]
4 19 ms 18 ms 20 ms 169-1-5-208.ip.afrihost.co.za [169.1.5.208]
5 20 ms 19 ms 20 ms 41.162.84.194
6 28 ms 28 ms 28 ms 172.18.1.162
7 27 ms 28 ms 28 ms if-ae-7-0.tcore1.jso-johannesburg.as6453.net [41.206.178.29]
8 198 ms 195 ms 199 ms if-ae-2-2.tcore2.jso-johannesburg.as6453.net [216.6.55.86]
9 305 ms 304 ms 298 ms if-ae-6-2.tcore2.klt-cape-town.as6453.net [41.206.179.10]
10 378 ms 358 ms 353 ms if-ae-2-2.tcore1.klt-cape-town.as6453.net [41.206.164.253]
11 * 364 ms 365 ms if-ae-5-90.tcore2.pv9-lisbon.as6453.net [80.231.159.109]
12 294 ms 296 ms 293 ms if-ae-2-2.tcore1.pv9-lisbon.as6453.net [80.231.158.5]
13 369 ms 371 ms 378 ms if-ae-1-3.tcore1.sv8-highbridge.as6453.net [80.231.158.30]
14 374 ms 373 ms 376 ms if-ae-2-2.tcore2.sv8-highbridge.as6453.net [80.231.139.1]
15 205 ms 201 ms 208 ms if-ae-11-2.tcore1.l78-london.as6453.net [80.231.139.42]
16 205 ms 212 ms 215 ms if-ae-17-2.tcore1.ldn-london.as6453.net [80.231.130.130]
17 202 ms 202 ms 203 ms 195.219.83.102
18 200 ms 199 ms 201 ms ae-126-3512.edge5.london1.level3.net [4.69.166.45]
19 199 ms 199 ms 199 ms twitter-inc.edge5.london1.level3.net [195.50.120.66]
20 * * * Request timed out.
21 279 ms 279 ms 279 ms 199.16.156.230

That's not looking so good
I'll check with our network team, in the mean time - is there anyone else in Durbs that's seeing this?

 

[Rickster]

My international online games keep bombing out.

PS C:\Users\Ricky> tracert 195.122.135.127

Tracing route to 195.122.135.127 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 25 ms 26 ms 25 ms jhb-up7.ip.adsl.co.za [169.1.5.6]
4 25 ms 24 ms 26 ms jhb-net1.ip.adsl.co.za [169.1.5.52]
5 26 ms 24 ms 25 ms 169-1-5-74.ip.afrihost.co.za [169.1.5.74]
6 26 ms 26 ms 24 ms 41.169.57.216
7 * * * Request timed out.
8 197 ms 234 ms * if-xe-1-2-0-0.tcore2.KLT-Cape-Town.as6453.net [41.206.165.17]
9 207 ms 207 ms 221 ms if-ae-2-2.tcore1.KLT-Cape-Town.as6453.net [41.206.164.253]
10 188 ms 188 ms 187 ms if-ae-5-30.tcore2.PV9-Lisbon.as6453.net [80.231.159.85]
11 199 ms 224 ms 200 ms if-ae-2-2.tcore1.PV9-Lisbon.as6453.net [80.231.158.5]
12 206 ms 219 ms 201 ms if-ae-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.158.30]
13 189 ms 190 ms 189 ms if-ae-2-2.tcore2.SV8-Highbridge.as6453.net [80.231.139.1]
14 189 ms 188 ms 188 ms if-ae-11-2.tcore1.L78-London.as6453.net [80.231.139.42]
15 197 ms 196 ms 196 ms if-ae-17-2.tcore1.LDN-London.as6453.net [80.231.130.130]
16 196 ms 193 ms 193 ms 195.219.83.186
17 200 ms 202 ms 248 ms ae-4.r22.londen03.uk.bb.gin.ntt.net [129.250.5.24]
18 204 ms 215 ms 208 ms ae-6.r21.frnkge03.de.bb.gin.ntt.net [129.250.3.13]
19 326 ms 318 ms 318 ms ae-1.r02.frnkge03.de.bb.gin.ntt.net [129.250.4.163]
20 207 ms 206 ms 210 ms 83.231.214.54
21 236 ms 209 ms 210 ms 195.122.135.127


Either that router is failing or the link is damaged.

 

[AfriGuy]

These open fine now, given up on the torrent, I am currently downloading the latest Windows 10 Insider build ( I need to actually get some work done), amazing how fast this downloads and its over 4GB, but a 50mb torrent sits for 24 minutes not doing a thing.

I have now done all the tests I was asked to do, so please don't say I have not been willing to do my part. Now its up to you to sort this out, and get this to Critical Care if normal support is unable to assist. I don't see why I must rehash all of this if there is a support ticket that can be sent to them.

Something is stopping your torrents here - if your trackers aren't even able to connect then I highly doubt it's an issue on our end.
Let me know when you're ready to run more tests - I'm here until 8pm tonight.

 

[AfriGuy]

My international online games keep bombing out.

PS C:\Users\Ricky> tracert 195.122.135.127

Tracing route to 195.122.135.127 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 25 ms 26 ms 25 ms jhb-up7.ip.adsl.co.za [169.1.5.6]
4 25 ms 24 ms 26 ms jhb-net1.ip.adsl.co.za [169.1.5.52]
5 26 ms 24 ms 25 ms 169-1-5-74.ip.afrihost.co.za [169.1.5.74]
6 26 ms 26 ms 24 ms 41.169.57.216
7 * * * Request timed out.
8 197 ms 234 ms * if-xe-1-2-0-0.tcore2.KLT-Cape-Town.as6453.net [41.206.165.17]
9 207 ms 207 ms 221 ms if-ae-2-2.tcore1.KLT-Cape-Town.as6453.net [41.206.164.253]
10 188 ms 188 ms 187 ms if-ae-5-30.tcore2.PV9-Lisbon.as6453.net [80.231.159.85]
11 199 ms 224 ms 200 ms if-ae-2-2.tcore1.PV9-Lisbon.as6453.net [80.231.158.5]
12 206 ms 219 ms 201 ms if-ae-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.158.30]
13 189 ms 190 ms 189 ms if-ae-2-2.tcore2.SV8-Highbridge.as6453.net [80.231.139.1]
14 189 ms 188 ms 188 ms if-ae-11-2.tcore1.L78-London.as6453.net [80.231.139.42]
15 197 ms 196 ms 196 ms if-ae-17-2.tcore1.LDN-London.as6453.net [80.231.130.130]
16 196 ms 193 ms 193 ms 195.219.83.186
17 200 ms 202 ms 248 ms ae-4.r22.londen03.uk.bb.gin.ntt.net [129.250.5.24]
18 204 ms 215 ms 208 ms ae-6.r21.frnkge03.de.bb.gin.ntt.net [129.250.3.13]
19 326 ms 318 ms 318 ms ae-1.r02.frnkge03.de.bb.gin.ntt.net [129.250.4.163]
20 207 ms 206 ms 210 ms 83.231.214.54
21 236 ms 209 ms 210 ms 195.122.135.127


Either that router is failing or the link is damaged.

Thanks for confirming - I've also passed this onto our network team, not really sure what's happening here
All looks good up until the highlighted hops. What happens if you ping 41.206.165.17?

 

[PurSpyk!!]

Something is stopping your torrents here - if your trackers aren't even able to connect then I highly doubt it's an issue on our end.
Let me know when you're ready to run more tests - I'm here until 8pm tonight.

What more test must be done, I have been doing test 3 days in a row now?? You know how irritating this is, I submit test after and nothing gets done. Is this in the hope things will eventually just work. I have been extremely accommodating considering the product you are selling is not working.

Its only my Afrihost account that has this issue, so how cannot it not be on your side??

 

[Rickster]

Thanks for confirming - I've also passed this onto our network team, not really sure what's happening here
All looks good up until the highlighted hops. What happens if you ping 41.206.165.17?

PS C:\Users\Ricky> ping -n 50 41.206.165.17

Pinging 41.206.165.17 with 32 bytes of data:
Reply from 41.206.165.17: bytes=32 time=208ms TTL=57
Reply from 41.206.165.17: bytes=32 time=206ms TTL=57
Reply from 41.206.165.17: bytes=32 time=45ms TTL=57
Reply from 41.206.165.17: bytes=32 time=45ms TTL=57
Reply from 41.206.165.17: bytes=32 time=46ms TTL=57
Reply from 41.206.165.17: bytes=32 time=214ms TTL=57
Reply from 41.206.165.17: bytes=32 time=45ms TTL=57
Reply from 41.206.165.17: bytes=32 time=103ms TTL=57
Reply from 41.206.165.17: bytes=32 time=45ms TTL=57
Reply from 41.206.165.17: bytes=32 time=46ms TTL=57
Reply from 41.206.165.17: bytes=32 time=198ms TTL=57
Reply from 41.206.165.17: bytes=32 time=46ms TTL=57
Reply from 41.206.165.17: bytes=32 time=202ms TTL=57
Reply from 41.206.165.17: bytes=32 time=210ms TTL=57
Reply from 41.206.165.17: bytes=32 time=45ms TTL=57
Reply from 41.206.165.17: bytes=32 time=196ms TTL=57
Reply from 41.206.165.17: bytes=32 time=46ms TTL=57
Reply from 41.206.165.17: bytes=32 time=46ms TTL=57
Reply from 41.206.165.17: bytes=32 time=204ms TTL=57
Reply from 41.206.165.17: bytes=32 time=218ms TTL=57
Reply from 41.206.165.17: bytes=32 time=46ms TTL=57
Reply from 41.206.165.17: bytes=32 time=47ms TTL=57
Reply from 41.206.165.17: bytes=32 time=234ms TTL=57
Reply from 41.206.165.17: bytes=32 time=45ms TTL=57
Reply from 41.206.165.17: bytes=32 time=47ms TTL=57
Reply from 41.206.165.17: bytes=32 time=45ms TTL=57
Reply from 41.206.165.17: bytes=32 time=45ms TTL=57
Reply from 41.206.165.17: bytes=32 time=46ms TTL=57
Reply from 41.206.165.17: bytes=32 time=219ms TTL=57
Reply from 41.206.165.17: bytes=32 time=216ms TTL=57
Reply from 41.206.165.17: bytes=32 time=205ms TTL=57
Reply from 41.206.165.17: bytes=32 time=45ms TTL=57
Reply from 41.206.165.17: bytes=32 time=45ms TTL=57
Reply from 41.206.165.17: bytes=32 time=200ms TTL=57
Reply from 41.206.165.17: bytes=32 time=217ms TTL=57
Reply from 41.206.165.17: bytes=32 time=45ms TTL=57
Reply from 41.206.165.17: bytes=32 time=200ms TTL=57
Reply from 41.206.165.17: bytes=32 time=46ms TTL=57
Reply from 41.206.165.17: bytes=32 time=83ms TTL=57
Reply from 41.206.165.17: bytes=32 time=47ms TTL=57
Reply from 41.206.165.17: bytes=32 time=46ms TTL=57
Reply from 41.206.165.17: bytes=32 time=216ms TTL=57
Reply from 41.206.165.17: bytes=32 time=207ms TTL=57
Reply from 41.206.165.17: bytes=32 time=195ms TTL=57
Reply from 41.206.165.17: bytes=32 time=47ms TTL=57
Reply from 41.206.165.17: bytes=32 time=225ms TTL=57
Reply from 41.206.165.17: bytes=32 time=213ms TTL=57
Reply from 41.206.165.17: bytes=32 time=45ms TTL=57
Reply from 41.206.165.17: bytes=32 time=47ms TTL=57
Reply from 41.206.165.17: bytes=32 time=222ms TTL=57

Ping statistics for 41.206.165.17:
    Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 45ms, Maximum = 234ms, Average = 120ms

 

[AfriGuy]

What more test must be done, I have been doing test 3 days in a row now?? You know how irritating this is, I submit test after and nothing gets done. Is this in the hope things will eventually just work. I have been extremely accommodating considering the product you are selling is not working.

Its only my Afrihost account that has this issue, so how cannot it not be on your side??

We need to determine:

a) What's causing your trackers to not connect/ serve you peers and
b) Why those utorrent sites aren't opening correctly.

Don't think it's fair to say the product isn't working.
I'm happy to continue to troubleshoot here, otherwise if you'd prefer to keep information in one place you can do so via our Support team or reaching our to our Critical Care team as we discussed last night.

Let me know how you'd like to proceed.

 

[AfriGuy]

PS C:\Users\Ricky> ping -n 50 41.206.165.17



Ping statistics for 41.206.165.17:
    Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 45ms, Maximum = 234ms, Average = 120ms

Crikey... that's a little erratic :/
I've passed this onto our network team to check out.

Can you confirm what DNS servers you're using please?

 

[Rickster]

Crikey... that's a little erratic :/
I've passed this onto our network team to check out.

Can you confirm what DNS servers you're using please?

Google for that one then AH's for this one:

Ping statistics for 41.206.165.17:
    Packets: Sent = 50, Received = 49, Lost = 1 (2% loss),
Approximate round trip times in milli-seconds:
    Minimum = 44ms, Maximum = 292ms, Average = 93ms

 

[PurSpyk!!]

We need to determine:

a) What's causing your trackers to not connect/ serve you peers and
b) Why those utorrent sites aren't opening correctly.

Don't think it's fair to say the product isn't working.
I'm happy to continue to troubleshoot here, otherwise if you'd prefer to keep information in one place you can do so via our Support team or reaching our to our Critical Care team as we discussed last night.

Let me know how you'd like to proceed.

1) Trackers not loading that's your job to determine, othjer ISPs work, simapl fact and I have provided proof of this

2) I said the site now laod without any issues

What other tests do you want I was told the tracert would highlight the problem, this seem to be another time waster, and now I am asked to do more tests, surely you can understand how frustrating this is.

Your product is not working, I am unable to download what I want when I want, therefore its not working. I don't go to the spur order a burger the give a roll and told well there you go, its ok, you got most of what you paid for.

What has been done on my account, and anything been changed on your side to see if its a configuration issue. I don't see how anymore tests can help if the current tests are not helping.

 

[AfriGuy]

Google for that one then AH's for this one:

Ping statistics for 41.206.165.17:
    Packets: Sent = 50, Received = 49, Lost = 1 (2% loss),
Approximate round trip times in milli-seconds:
    Minimum = 44ms, Maximum = 292ms, Average = 93ms

Cool, so both seem to give similar results here.
I'm in touch with our network guys to see what's going on

 

[AfriGuy]

1) Trackers not loading that's your job to determine, othjer ISPs work, simapl fact and I have provided proof of this

2) I said the site now laod without any issues

What other tests do you want I was told the tracert would highlight the problem, this seem to be another time waster, and now I am asked to do more tests, surely you can understand how frustrating this is.

Your product is not working, I am unable to download what I want when I want, therefore its not working. I don't go to the spur order a burger the give a roll and told well there you go, its ok, you got most of what you paid for.

What has been done on my account, and anything been changed on your side to see if its a configuration issue. I don't see how anymore tests can help if the current tests are not helping.

Have you tested with our DNS though? There's a stack of other tests to run through to see why your trackers don't connect.
As I said before though, I'm happy to help and to run through various options - even test your account on my home line if that's what it takes. In order to do so, and move forward from this - we need to do so in a civil manner.

At the moment, I get the feeling that you're more interested in arguing that resolving this.

 

[PurSpyk!!]

Have you tested with our DNS though? There's a stack of other tests to run through to see why your trackers don't connect.
As I said before though, I'm happy to help and to run through various options - even test your account on my home line if that's what it takes. In order to do so, and move forward from this - we need to do so in a civil manner.

At the moment, I get the feeling that you're more interested in arguing that resolving this.

I have change the dns, as I have said numerous times, what other tests are required?

 

[AfriGuy]

I have change the dns, as I have said numerous times, what other tests are required?

Have you tried removing utorrent completely and re-adding it to your firewall?
Are you able to replicate the issue on another machine on your network?
Have you tried changing ports/ a config on uTorrent to see this work?
There are also some good options to run through here:

https://forum.utorrent.com/topic/94462-torrents-will-not-connect-to-peerstrackers/
https://forum.utorrent.com/topic/93898-constant-connecting-to-peers-and-red-availibility/

 

[PurSpyk!!]

Have you tried removing utorrent completely and re-adding it to your firewall?
Are you able to replicate the issue on another machine on your network?
Have you tried changing ports/ a config on uTorrent to see this work?
There are also some good options to run through here:

https://forum.utorrent.com/topic/94462-torrents-will-not-connect-to-peerstrackers/
https://forum.utorrent.com/topic/93898-constant-connecting-to-peers-and-red-availibility/

Uninstalled utorrent, and as stated yesterday with a totally different client the issue still exists

Same issue on all 6 computers on network, running different operating systems

Reset the ports, also deleted the file mentions in these forums.

Once again, switching accounts and there are no issues, so how can it possibly be my setup. Has anyone actually checked my account, done any resets, checked if its configured correctly, has Telkom been contacted as you get paid for the adsl part of my line? I very much doubt it because I have seen zero improvement, and all I get told we need to solve this in a civil manner. You mentioned publically in these forums that I was not doing the tests you asked for when In fact I posted that I had.

you also mention I have used support a lot, or how did you put it something like exceeded your support resources. Sorry, I have a problem I pay you, I will contact you as much as I want until my issue gets resolve, I know I can move to a different ISP, but I wont, I want the product I am paying for.

Have you actually read those forum links you posted, many of the fixes don't work, and its mentioned as well that ISP have been the issue with the trackers?

 

[Dianysis]

International speeds suck at the moment.

 

[Gaza365]

The News Server is definitely still active, it should use your DSL details to authenticate on the server. Which News Server Client are you using?

Afrihost News Group Server news.afrihost.co.za 119

straight from here: http://www.afrihost.com/site/page/internet_configuration_settings

It used to work with no settings configured for username and password, then it stopped working, so I added my DSL Account details some months back but that didn't help anything

just tested with account details configured and blank, same response when testing "502 Authentication Failed"