HELP! 3G SMTP problem

[lombruan]

Have anyone noticed that Vodacom 3G now assigns IPs from a 105.x.x.x range in addition to the 41.x.x.x. range they always did. For some reason when I (and all of our staff) get a 105.x.x.x IP address, we cannot connect to our SMTP server, only to the Vodacom (smtp.vodacom.co.za) one, but when we get a 41.x.x.x IP address everything works fine.

The guys at 082155 has been no help whatsoever, they just tell us to disconnect and reconnect. It doesn't help - only sometimes when you're lucky enough to get a 41.x.x.x IP address then everything works fine. On a 105.x.x.x IP address I can ping my SMTP server, but it just won't allow an SMTP connection to it. We don't use a VPN and our APN settings is set to "internet".

We have about 250 Vodacom 3G contracts and I can't have each user change their outgoing server settings. This problem started intermittently last week, but more of our staff are now experiencing it.

[lombruan]

UPDATE:

I just received an email from Vodacom (Mobile Data Support Specialist) in answer to my question as in my original post:

They will need to apply for the ‘internetvpn’ APN.

InternetVPN APN will give them a public IP always or 41.x so that they can connect to their SMTP mail server.

What a ridiculous"solution". How are we supposed to change the APN setting on each rep's laptop (200+) all over the country? You'd think customers would be informed of major changes such as these. Surely we can't be the only ones affected by this or do everybody use Vodacom's SMTP servers?

[PsyWulf]

I'd rather look into why your SMTP isn't allowing access from that IP range

Could you do a telnet to your mail server and post a session log? Would love to see what's happening

[lombruan]

I have no restrictions on IP addresses setup on that server, it only requires authentication. Staff travelling abroad can even connect from wifi hotspots on any IP range. I don't think the IP range is the problem, I think Vodacom isn't allowing SMTP to other servers on that IP range. I'll post the telnet info in any case, maybe there's a clue there. Just need to get my hands on a laptop with the issue currently since they randomly get a 41 or 105 IP assigned. Thank you

[PsyWulf]

Vodacom isn't allowing SMTP to other servers on that IP range.

Possible,but even then you should be able to use port587 alternate submission ( the default I use for any clients with mobile users so they aren't ISP dependant )

[Billwill]

OK this explains why over the last few days I have been unable to log into www.e30zone.net....occassionaly it works.
This is from my 3G dongle running on Windows XP.

I get the message: Your attention please! You have attempted to access this site with an invalid IP.

Remote Address: 105.242.48.52
Client IP: none
Forwarded For: none

I can see even before attempting to log into that site that it will not work because I can see in the Internet Connections screen on Windows that I have the range of 105.242.xx.yy assigned......set by DHCP. When I see the range of 41.xxx.yyy I know it will work.

I am not a DHCP expert on Windows so I do not know how to circumvent this problem.....surely Vodacom should confer with us before they make changes?

[sajunky]

I agree with lombruan. It is ordinary outgoing connection, no need for unrestricted APN. It shouldn't be such kind of restrictions. Something is wrong with Vodacom, not acceptable.

[PsyWulf]

OK this explains why over the last few days I have been unable to log into www.e30zone.net....occassionaly it works.
This is from my 3G dongle running on Windows XP.

I get the message: Your attention please! You have attempted to access this site with an invalid IP.

Remote Address: 105.242.48.52
Client IP: none
Forwarded For: none

I can see even before attempting to log into that site that it will not work because I can see in the Internet Connections screen on Windows that I have the range of 105.242.xx.yy assigned......set by DHCP. When I see the range of 41.xxx.yyy I know it will work.

I am not a DHCP expert on Windows so I do not know how to circumvent this problem.....surely Vodacom should confer with us before they make changes?

IP Address: 105.242.48.52
Source: whois.ripe.net
Prefix: 105/8
Designation: IANA
Status: UNALLOCATED

Read more: http://www.whatismyip.com/tools/ip-w...#ixzz20t1S1qS8

Unallocated IP range could be causing hassles with any kind of Geotagging

*Edit,i see the range is allocated to AfriNic,will check more indept,maybe it's a fresh range

[PsyWulf]

% Information related to '105.242.0.0 - 105.242.255.255'

inetnum: 105.242.0.0 - 105.242.255.255
netname: Vodacom_UMTS_Pretoria_Silverton_North_Gauteng_INTE RNET_APN
descr: Legal IP Block for Internet APN - Pretoria Silverton Northern Gauteng
country: ZA
admin-c: JH2-AFRINIC
tech-c: JH2-AFRINIC
status: ASSIGNED PA
mnt-by: VODACOM-MNT
remarks: Legal IP Block for Internet APN - Pretoria Silverton Northern Gauteng
source: AFRINIC # Filtered
parent: 105.240.0.0 - 105.255.255.255

[lombruan]

@PsyWulf. I changed the port of the SMTP client to send through 587 and opened that on my firewall, it seems to work. Thank you for the suggestion!
I am however concerned about other ports/protocols that might be closed/restricted on this IP range that we have not noticed yet. Imagine the antivirus not being able to update etc. It could be a disaster. In any case, Vodacom still hasn't replied to my emails, but at least I can assist staff that phone. It's a work-around, not a solution yet.

[PsyWulf]

Do go ahead and still post a telnet session log to 25 to just try see what's happening more indepth

[jannievanzyl]

I'll have a look. Might be our new allocation.

Which areas are you guys getting 105.x.x.x and seeing issues?

[lombruan]

Hi Jannie

We're getting it randomly in Gauteng and Limpopo. A person will connect and sometimes get a 105 IP and other times a 41. We haven't had support requests regarding this from other provinces yet.

[jannievanzyl]

Hi Jannie

We're getting it randomly in Gauteng and Limpopo. A person will connect and sometimes get a 105 IP and other times a 41. We haven't had support requests regarding this from other provinces yet.

Should work now. Will you test please?