Afrihost CAPPED ADSL Feedback (MTN)

Status
Not open for further replies.
eddief1

eddief1

Expert Member
Joined
Feb 26, 2008
Messages
1,523
Reaction score
301
I thought I should start a thread for Afrihost's Capped products on the MTN network in anticipation of the move tomorrow.

1) Will smtp.afrihost.co.za still be the outgoing mail server once the changeover has taken place?

2) Are the DNS servers for the capped products on the MTN network, the same as the uncapped ones, namely:
primary: 196.7.7.7
secondary: 196.7.142.133

3) Will the change over happen at night or at a random time during business hours ?

4) When will we be able to access the Cape Town IPC as latencies for us in the cape are going to dramatically increase when the move takes place

ED


Mod_note: These threads are clearly designed/intended for customers to provide feedback to their respective ISPs - not for disgruntled former customers to vent, not for other ISPs to promote their services, etc - and, one hopes, for the relevant ISP to respond.
 
Last edited by a moderator:
eddief1 said:
I thought I should start a thread for Afrihost's Capped products on the MTN network in anticipation of the move tomorrow.

1) Will smtp.afrihost.co.za still be the outgoing mail server once the changeover has taken place?

2) Are the DNS servers for the capped products on the MTN network, the same as the uncapped ones, namely:
primary: 196.7.7.7
secondary: 196.7.142.133

3) Will the change over happen at night or at a random time during business hours ?

4) When will we be able to access the Cape Town IPC as latencies for us in the cape are going to dramatically increase when the move takes place

ED
Click to expand...

Thanks for this thread, it definitely makes sense to ask all the questions you have.

1) smtp.afrihost.co.za will stay as the outgoing mail server, some changes will happen on the back end, but there will be nothing to change on your end, unless you are using a different server like ISDSL. Best to change to the standard server on Port 25.

2) Yes, DNS will be the same for capped and uncapped.

3) The change over will happen over the evening, but from the user perspective you will continue to have connectivity, you'll just be routed differently the next time you authenticate.

4) even using JHB IPC the latency is not expected to be significant. MTN already have the IPC in CT and DBN as I understand, but we want to stabilise the network in a controlled environment first, and JHB makes sense as our skills are based here.
 
Everything running smoothly on the Capped accounts for me after the migration to MTN, failed to get IP's after authenticating this morning but that seems to be sorted now...latency to JHB is surprisingly low, can't wait for the CT IPC to come online.
 
OK found an issue...when sending mail using smtp.afrihost.co.za the mail gets returned...what is the IP address of the new mail server, think the smtp.afrihost.co.za DNS records have not been updated yet
 
The secondary DNS listed is actually incorrect. Use 196.7.7.7 and 196.7.8.9. If you are querying any of those two DNS servers and you are on the new ADSL network (105.236.0.0) IP address you should be able to resolve smtp.afrihost.co.za to the new IPs which are as follows:

smtp.afrihost.co.za has address 41.181.159.132
smtp.afrihost.co.za has address 41.181.159.136
smtp.afrihost.co.za has address 41.181.159.168
smtp.afrihost.co.za has address 41.181.159.164
 
everything looking fine on my side, except that according to speedtest I'm no longer in Jo'burg
 
ukj said:
The secondary DNS listed is actually incorrect. Use 196.7.7.7 and 196.7.8.9. If you are querying any of those two DNS servers and you are on the new ADSL network (105.236.0.0) IP address you should be able to resolve smtp.afrihost.co.za to the new IPs which are as follows:

smtp.afrihost.co.za has address 41.181.159.132
smtp.afrihost.co.za has address 41.181.159.136
smtp.afrihost.co.za has address 41.181.159.168
smtp.afrihost.co.za has address 41.181.159.164
Click to expand...

I get a requested timed out when pinging smtp.afrihost.co.za which does resolve to one of the above addresses.
 
eddief1 said:
I get a requested timed out when pinging smtp.afrihost.co.za which does resolve to one of the above addresses.
Click to expand...

That's OK. The servers block pings. You should be able to telnet to port 25 on any one of them though.
 
Sorted it was a cached DNS entry on our SBS server, flushed the cache and we good...blind
 
Speedtest early this am was the best I have had since my upgrade to 1meg. Didn't get a chance to check dl speeds again.
 
ShaunSA said:
Speedtest early this am was the best I have had since my upgrade to 1meg. Didn't get a chance to check dl speeds again.
Click to expand...

+1 I'm getting full line speed on 4mbps...A good start so far, youtube seems better than it was on IS...holdthumbs
 
Everything seems good, went down for me for about 2 minutes, rebooted and everything back to normal...speeds are line speed...keep up the good work!
 
AfriMan said:
So all good here?

:)
Click to expand...

At the moment yeah, having to move 10 + clients to a different realm was a nightmare. Having a heartattack thinking ones network has fallen over only to find routing between IS and Telkom went for a ball of crap for about 45 mins, not so much fun either. Then outgoing failing ... what a morning.
 
Now smtp.mtnbusiness.co.za is on McAfee rolling block list :mad::mad:

SMTP error from remote mail server after RCPT TO:<@lantic.net>:
host lantic.net.inbound10.dotnetwork2.co.za [41.77.56.12]:
551 Mailhost is on our global block list. See http://mcaf.ee/5xxhelp (Mode:
normal)
 
Last edited:
Well i think congrats are in order - well done to Afrihost and Afriman.Switched over this morning and it was reasonably painless.So far results are promising and hopefully CT users will have their own IPC soon.
 
Getting good speeds and ping is not that bad. Local ping to J.Burg for me is actually better now.

Well done so far AH.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X