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

Status
Not open for further replies.
Prometheus said:
You can install is without flashing the modem.
Click to expand...
Not quite any more - if you remain current... The earlier versions of Huawei included a 9MB odd ISO from which you could get the install and drivers. The latest on their web-site is much smaller than the earlier 15MB - appr 7.xMB - and does not include the ISO, only the flash program. I think it is March 2007. This is is the one I have on my E220 now, and it works best of all.
For me it has been worth the "risk" as opposed to having some Huawei and some Vodafone in use.
One also has to remove/uninstall everything you can find relating to prev software and drivers after the update, then un-plug, wait, plug in. It then autoruns, installs as intended by Huawei. Suspect you are not far from me - can come see mine if you want.

Prometheus said:
For gprs on Vodacom it shows something like 56k on gprs, they don't have edge here. The 3.6Mbps is merely an indication of the maximum connection speed between tower and modem. There is no way for the modem to know that the tower does not use the encodings that makes 3.6Mbps possible.
Click to expand...
Just checked mine - shows 236.8k on GPRS. Either way - it is the port speed, and yes, no way they modem knows what the tower stuff is doing.
Incidently - have pushed MTN and Virgin sims in mine - says EDGE for them - which is correct.

Just notice the generator/ups comments - have to add a note of precaution!
Even without the power issues being experienced - it is not a good idea to flash modem (and mainboard BIOS for that matter) without the PC running off a working UPS. Any disruption of this nature will most probably leave the half programmed device dead.:sick:
 
Last edited:
Prometheus said:
That's what I want to know from you. If packets are not fragmented (and I can't see how since it's single packets) then what is causing the delay. And physics as an answer just doesn't cut it. I took the maximum MTU for ethernet which is most of the internet and probably a large portion of Vodacom's network as well.
Click to expand...

I've before asked you to buy a book on networking and IP, and again implore you to do so. This is simple networking-101.

Fortunately, networks do run according to the laws of physics and thus can be understood by anyone willing to take the time to learn how it all works. You don't need to guess. It's all in the maths.

Latency is a function of transmission physics (~.7c/clock) plus the elements in the path (especially store and forward device, of which there are many where you must add the clock-in, processing and clock-out latencies, again dictated by physics) overlayed with a higher level protocol (such as TCP) that requires turn-around at some point (called handshaking) which resets the one-direction latency.

If you do the maths you'll come up with the latency you measured with something like a ping.

It's really not black magic and no-one is introducing latency just to be spiteful.

I can type up a (very long) post explaining it all, but it's just so well documented, anyone can read up on it. Google is your friend......
 
Last edited:
Somebody told me before not to hijack a thread, what does batteries have to do with Problems: Slow Throughput, trying to Connect, DNS, High Latency ??
So I agree lets keep the threads clean.
:p ;)
 
Download Speed: 941 kbps (117.6 KB/sec transfer rate)
Upload Speed: 270 kbps (33.8 KB/sec transfer rate)

All is well this side of SA. :D
 
:mad: Not again... my connection finally became stable after the hassles a month or two ago, very little time-outs and great pings to international sites at 280ms, but now its all back to the broken time-outs every few pings and latency of 480ms and higher... anyone else having this problem in Brackenfell area?
 
My 3G kicked out a few times now… reconnected, and I’m back on GPRS. :( Connection dropped again. Yay, and I’m back on 3G. Am I alone on this?
 
I'm getting error 619s trying to connect this afternoon (was OK this morning). 155 are going to phone me back. Is anyone else experiencing this problem - or alternatively connecting fine? I'm in Sandton, using an E220 USB modem, with a prepaid data bundle (not used up and not expired).

Aside 1: From numerous past threads I know that the infamous error 619 doesn't mean anything useful. Is there any way the connectivity issue could be diagnosed or isolated to something more specific, even if it means programming? (If so maybe we could persuade ginngs to add it into his tool.)

Aside 2: I thought this thread was sticky?
 
ic said:
- the recent low volume of posts in this thread indicates that the previous widespread problems are no longer widespread.
Click to expand...
Let's hope!

ic said:
It would however be preferable if forumites experiencing problems, continued to post in this thread instead of the usual 20 other threads that mushroom up when there are problems - concentrating the posts here should give an idea of how widespread any particular set of problems is.
Click to expand...
Agree with this. Although being unable to connect is qualitatively different from slow throughput / high latency ... perhaps a different "error 619 "/ "could not establish a connection" thread is called for. I'll certainly feel like starting one if this hits me again.

ic said:
About the 619s you're getting, IMO it means drop in signal quality &| signal strength, assuming you're using 3G|HSDPA with your E220 and have it set to a 3G-only profile, then you might be experiencing increased base-station load, and the resulting intermittent effects of [searchforum]Cell Breathing[/searchforum].
Click to expand...
It's not the signal strength. That was around -69dBM / 70% when I posted this afternoon.

You have just taught me two things: the [ searchforum ] tag and the term "cell breathing"! :D

I was set to "3G Preferred" this afternoon.

I am now in the Randburg area. The connect issue is the same. Have tried with 3G Preferred, GPRS/EDGE only, and 3G Only. I'm getting -59dBM/87% on GPRS, -75dBm/61% on 3G.
 
Hey - more details in windows' modem log (C:\WINDOWS\ModemLog_HUAWEI Mobile Connect - 3G Modem.txt or similar):
06-21-2007 19:52:01.323 - Dialing.
06-21-2007 19:52:01.323 - TSP Completing Async Operation(0x00010230) Status 0x00000000
06-21-2007 19:52:01.323 - TSP(0000): LINEEVENT: LINECALLSTATE_DIALING
06-21-2007 19:52:01.323 - TSP(0000): LINEEVENT: LINECALLSTATE_PROCEEDING
06-21-2007 19:52:01.333 - Send: ATDT*###<cr>
06-21-2007 19:52:01.343 - Recv: <cr><lf>CONNECT 53600<cr><lf>
06-21-2007 19:52:01.343 - Interpreted response: Connect
06-21-2007 19:52:01.343 - Receive Connect but CD was low, Waiting for signal to go high
06-21-2007 19:52:01.363 - After waiting 20ms CD is still low.
06-21-2007 19:52:01.383 - CD has been raised
06-21-2007 19:52:01.383 - Connection established at 53600bps.
06-21-2007 19:52:01.383 - Error-control off or unknown.
06-21-2007 19:52:01.383 - Data compression off or unknown.
06-21-2007 19:52:01.383 - TSP(0000): LINEEVENT: LINECALLSTATE_CONNECTED
06-21-2007 19:52:02.815 - CD dropped--Remote modem hung up. ModemStatus=00000030
06-21-2007 19:52:02.815 - TSP(0000): LINEEVENT: LINECALLSTATE_DISCONNECTED(0x1)
06-21-2007 19:52:02.815 - TSP(0000): Dropping Call
06-21-2007 19:52:02.815 - Hanging up the modem.
Click to expand...
This is a clip from the middle - the whole connect log is quite long.

I don't suppose it tells us anything useful though.:(
 
Ahh yes another day of crawling ahead....

[83.138.172.42] with 32 bytes of data:

Reply from 83.138.172.42: bytes=32 time=1482ms TTL=46
Reply from 83.138.172.42: bytes=32 time=1468ms TTL=46
Reply from 83.138.172.42: bytes=32 time=1449ms TTL=46
Reply from 83.138.172.42: bytes=32 time=1469ms TTL=46
Reply from 83.138.172.42: bytes=32 time=1469ms TTL=46
Reply from 83.138.172.42: bytes=32 time=1479ms TTL=46
Reply from 83.138.172.42: bytes=32 time=1470ms TTL=46
Reply from 83.138.172.42: bytes=32 time=1468ms TTL=46
Reply from 83.138.172.42: bytes=32 time=1499ms TTL=46
Reply from 83.138.172.42: bytes=32 time=1459ms TTL=46
Reply from 83.138.172.42: bytes=32 time=1494ms TTL=46
Reply from 83.138.172.42: bytes=32 time=1504ms TTL=46
Reply from 83.138.172.42: bytes=32 time=1459ms TTL=46
Reply from 83.138.172.42: bytes=32 time=2298ms TTL=46
Reply from 83.138.172.42: bytes=32 time=1459ms TTL=46
Reply from 83.138.172.42: bytes=32 time=1459ms TTL=46
Reply from 83.138.172.42: bytes=32 time=1469ms TTL=46
Reply from 83.138.172.42: bytes=32 time=1450ms TTL=46
Reply from 83.138.172.42: bytes=32 time=1533ms TTL=46
Reply from 83.138.172.42: bytes=32 time=1464ms TTL=46
Reply from 83.138.172.42: bytes=32 time=1463ms TTL=46
Reply from 83.138.172.42: bytes=32 time=1459ms TTL=46
Reply from 83.138.172.42: bytes=32 time=1459ms TTL=46
Reply from 83.138.172.42: bytes=32 time=1460ms TTL=46
Reply from 83.138.172.42: bytes=32 time=1478ms TTL=46
Reply from 83.138.172.42: bytes=32 time=1469ms TTL=46
Reply from 83.138.172.42: bytes=32 time=1450ms TTL=46
Reply from 83.138.172.42: bytes=32 time=1498ms TTL=46
Reply from 83.138.172.42: bytes=32 time=1479ms TTL=46
Reply from 83.138.172.42: bytes=32 time=1479ms TTL=46
Reply from 83.138.172.42: bytes=32 time=1460ms TTL=46
Reply from 83.138.172.42: bytes=32 time=1458ms TTL=46
Reply from 83.138.172.42: bytes=32 time=1459ms TTL=46
Reply from 83.138.172.42: bytes=32 time=1459ms TTL=46
Reply from 83.138.172.42: bytes=32 time=1459ms TTL=46
Reply from 83.138.172.42: bytes=32 time=1479ms TTL=46
Reply from 83.138.172.42: bytes=32 time=1689ms TTL=46
Reply from 83.138.172.42: bytes=32 time=1449ms TTL=46
Reply from 83.138.172.42: bytes=32 time=1459ms TTL=46
Reply from 83.138.172.42: bytes=32 time=1468ms TTL=46
Reply from 83.138.172.42: bytes=32 time=1469ms TTL=46
Reply from 83.138.172.42: bytes=32 time=1479ms TTL=46
Reply from 83.138.172.42: bytes=32 time=1479ms TTL=46
Reply from 83.138.172.42: bytes=32 time=1479ms TTL=46
Reply from 83.138.172.42: bytes=32 time=1499ms TTL=46
Reply from 83.138.172.42: bytes=32 time=1479ms TTL=46
Reply from 83.138.172.42: bytes=32 time=1469ms TTL=46
Reply from 83.138.172.42: bytes=32 time=1469ms TTL=46
 
SecretCode said:
Hey - more details in windows' modem log (C:\WINDOWS\ModemLog_HUAWEI Mobile Connect - 3G Modem.txt or similar):

This is a clip from the middle - the whole connect log is quite long.

I don't suppose it tells us anything useful though.:(
Click to expand...

Not bad signal then you have been stopped your data has been used up so you get no signal.
 
SecretCode said:
Hey - more details in windows' modem log (C:\WINDOWS\ModemLog_HUAWEI Mobile Connect - 3G Modem.txt or similar):

This is a clip from the middle - the whole connect log is quite long.

I don't suppose it tells us anything useful though.:(
Click to expand...

ERROR 619 is the port is disconnected.

06-21-2007 19:52:02.815 - CD dropped--Remote modem hung up. ModemStatus=00000030.

The remote Modem has disconnected the line due to being told this guy has no more money. :o :p

Hoes en betaal is die wet van transvaal sorry (VODACOM).

:p :p
 
Last edited:
no reply from the dnsserver

hi all

Durban - Glenwood
Huawei E620
IMEI - 357130001439490
Revision: I:11.16.09.06.19

ive been having problem for the last while its a work card and laptop and i gave it to the IT guy at work and he said that i wasnt getting a dnsserver response. i heard that my cap might be 500mb but its currently sitting about 330mb.
though if i look in my logs i also go this "CD dropped--Remote modem hung up. ModemStatus=00000030"

just tried a ipconfig/flushdns command and a ipconfig/registerdns and i still got nothing on both 3g and gprs. modem shows the right LED's for the current profiles that i choose but i dont get a response.

and whats it mean if i get a sms from vodacom to my dashboard saying "you have been added to the call limit system"

thanks for the help
Angelus
 
Last edited:
vodacom3g said:
619 is a high-level, catch-all error code for 'connection broken'. Can be caused by many things and is pretty useless in trying to find the cause for the broken connection.
Click to expand...

True.

As @Secretcode says all is ok eccept when he tries to connect. How about trying to find an easy solution. Maybe with ppdb's it tries to connect and finds it has been blocked or softlocked and then just drops the line. This then becomes an error 619. As per the log file it is CD(carrier detect gone). I suppose it depends on how the system works.
 
Csnoopy said:
Not bad signal then you have been stopped your data has been used up so you get no signal.
Click to expand...
Csnoopy said:
The remote Modem has disconnected the line due to being told this guy has no more money. :o :p
Click to expand...
Thanks for the suggestions, csnoopy (also the one about being locked), but nope. Connected fine today. Data balance was ample, window expiry was not due. And as I said, signal strength was good.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X