Vodacom Problems: Slow Throughput, trying to Connect, DNS, High Latency

Status
Not open for further replies.
For the issue with not connecting to things such as email and mxit, my phone, a Gigabyte Gsmart i, connects directly to gprs using "internet" as its APN and has no issues using Mxit or Opera Mini. Also I have no issues with sending mail with mail on the internet APN on 3G.

Now on my son's phone a Sony Ericsson m600i I have the same issues as mentioned. Browsing is perfect but he cannot access anything through services like email (gmail app), mxit, or opera mini. He has tried various APN settings that should work:
wap.GPRS
internet
internet.GPRS
and various combinations with and without proxies, and with a set DNS instead of a dynamic one, and the problem stays. On another note, "internet" as an APN doesnt connect at all.

Example os settings tried:
http://www.3g.co.za/content/view/41/33/
Operator: Vodacom
Service: Internet
- APN: internet
- Pre-paid support: Yes
Service: MMS
- APN: mms.vodacom.net
- Pre-paid support: Yes
- WAP Gateway: 196.6.128.6 Port: 9201
- MMSC: http://mmsc.vodacom4me.co.za/
 
Last edited:
Yes, it turns out the fix we got from the vendor for the Jaco Kroon SACK problem is causing some handsets problems with certain protocols.

We reverted back and the phones are now working (obviously the SACK problem will be back).

We've escalated to the vendor.

Any Idea which phones were affected by this?
I know all the changes/upgrades Vodacom have made so far have not affected the Gigabyte.
 
Any Idea which phones were affected by this?
I know all the changes/upgrades Vodacom have made so far have not affected the Gigabyte.

No, and that's the problem and why we had to roll back.

The changes made to accommodate SACK on the Cisco firewalls obviously caused some handsets' IP stacks grief, but we've got no idea which ones they are.

At least we have three handsets from this thread to test with, so we'll now test in the lab.

This is actually a good example of the complexities one face in a multi-vendor world where inter-operability is supposed to be in the standards but is not always so in the actual products.
 
No, and that's the problem and why we had to roll back.

The changes made to accommodate SACK on the Cisco firewalls obviously caused some handsets' IP stacks grief, but we've got no idea which ones they are.

At least we have three handsets from this thread to test with, so we'll now test in the lab.

This is actually a good example of the complexities one face in a multi-vendor world where inter-operability is supposed to be in the standards but is not always so in the actual products.

issue resolved. had a call from Peet who diagnosed the problem.
i have to say i'm pretty impressed with the way this was handled, however i pity the average user who has no knowledge of mybroadband forums and tries to get issues like this resolved by dialing 111. I didn't even know about the 155 number until i read about it here. Vodacom needs to make this kind of info more easy to find.

great to have my email working again!
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X