-
Ask a question and get free supportUnlock new privileges and see hidden discussionsWin prizes and earn reputation
-
Question of the day ~ How often do you braai?
-
Afristay giveaway.Win a 2-night stay for two people at an establishment of your choice with R1,000 in spending money. Enter here.
Sign up with Google619 Errors
- Thread starter NeBo
- Start date
piranha786
Expert Member
- Joined
- Apr 28, 2005
- Messages
- 1,424
no, I am also struggling to get online, MTN has 1 bar signal ( at least I can be on myadsl) vodacom has full signal, but no internet connection
(
(Not only Cape Town...
Anyone else having 619s tonight?
I have done the whole re-insert process and am now online with my mtn sim at R2/MB
anyone?????????
Same problem here (Pietermaritzburg) between about 18:30 to 22:00 ...
My kid could not get onto MXiT (Vodacom GPRS) either.
- R
Anyone else having 619s tonight?
I have done the whole re-insert process and am now online with my mtn sim at R2/MB
anyone?????????
For this reason I got my ancient Vodacom phone out of the drawer and inserted my VC SIM into it - exclusively for voice.
Got myself a MTN sim @ R2 @ P&P and R30 topup.
Loaded R10 of the topup into a 10MB databundle - and for now I have a reliable - and much cheaper - GPRS connection.
Why not VM? Cell-C and VC are still to close to each other to guarentee reliability.
Last edited:
Affected Durban too. What does error 619 mean anyway?
Just to add that the 155 call-in service leaves much to be desired. After fumbling through the host of options, I end up leaving a call-back message. Call back comes within a minute "Please hold for the next available operator" *click* *disconnect tone*
Generally it means that your pc can't make contact with voda's pc. Next time it happens, click on 'more info' to read about possible causes.Affected Durban too. What does error 619 mean anyway?
Just to add that the 155 call-in service leaves much to be desired. After fumbling through the host of options, I end up leaving a call-back message. Call back comes within a minute "Please hold for the next available operator" *click* *disconnect tone*
The 619 error is extremely frustrating, made more so by the fact that, if you are creating the connection via the Vodafone dashboard, it takes so long to return the error.
If you create the connection manually, ie. by using the added connection "3G Only" then it appears, according to the dialog box that appears, that a connection is established very quickly onto Vodacom's netword, but the process stalls at the 'registering your computer' stage.
You can also create a modem log and this provides additional info that I am not an expert at interpreting, but I am 100% convinced that the error has nothing to do with my local setup or machine, but rather is on Vodacom's side - either to do with signal strength, or the ability to service the request at that time.
Of course rather than take ownership of the problem, it is much easier to tell the user just reboot, or eject and reinsert their card - all of which takes time and often the problem has disappeared in the iterim.
There are times when the problem is chronic though - can attempt connections for a number of hours without success.
If you create the connection manually, ie. by using the added connection "3G Only" then it appears, according to the dialog box that appears, that a connection is established very quickly onto Vodacom's netword, but the process stalls at the 'registering your computer' stage.
You can also create a modem log and this provides additional info that I am not an expert at interpreting, but I am 100% convinced that the error has nothing to do with my local setup or machine, but rather is on Vodacom's side - either to do with signal strength, or the ability to service the request at that time.
Of course rather than take ownership of the problem, it is much easier to tell the user just reboot, or eject and reinsert their card - all of which takes time and often the problem has disappeared in the iterim.
There are times when the problem is chronic though - can attempt connections for a number of hours without success.
619 errors are almost always [in my case] network related.
I am peddling a whole stack of sims from different operators with me these days and received 619s on all of them at different periods. But 99% of time if i get a 619 on Vodacom, i can
put in my MTN sim and connect, same thing if i get it on MTN [and i do ] i can switch to my Vodacom sim and continue.
MTN dissapeared about 22:00ish last night on me and it was 619s all over the place, switched to Vodacom sim and went on without problems.
This is also why i am against the whole card locking thing going on, i can very quickly determine these days that it is NOT my local setup if i can switch between 3 operators at any given moment when one fails.
I am peddling a whole stack of sims from different operators with me these days and received 619s on all of them at different periods. But 99% of time if i get a 619 on Vodacom, i can
put in my MTN sim and connect, same thing if i get it on MTN [and i do ] i can switch to my Vodacom sim and continue.
MTN dissapeared about 22:00ish last night on me and it was 619s all over the place, switched to Vodacom sim and went on without problems.
This is also why i am against the whole card locking thing going on, i can very quickly determine these days that it is NOT my local setup if i can switch between 3 operators at any given moment when one fails.
619 just means you could not connect, ANYTHING in the path could be causing this.
A (simplified) process:
VMC Dashboard->Windows OS->Drivers->PC hardware->Data card->radio tower->transmission line->Radio Controller->transmission line->authentication servers (some interconnected by transmission lines)
If any component, in the path, gives problems, the end-to-end connection can't be established and Windows will return a generic "I could not connect' error, the dreaded 619.
The above is just the physical path, there are also a lot of configuration parameters as well:
1) Is the SIM provisioned for data.
2) If on pre-paid, do you have credit.
3) Are you using the right APN. (I've made this mistake a few times )
4) Are the DNS settings, etc. correct.
Once you've been issued an IP, there still might be problems, but they'll typically give other errors such as HTTP, routing, DNS, firewall, etc. errors.
So, 619 is often more a pain than anything else, as it does not give any indication of where the problem might be. The only way to narrow it down is to look for common reports, thus the importance to get accurate location information. The call desk will then use the above path to try and find the cause.
1) If only one report comes from a specific area, it can very well be on the PC side.
The fact that so often a reboot fixes the error points to a problem on the PC side.
My own setup never gives 'local' 619's, I probably got two 619's in the last month and both times there was a actual network problem.
So it worth it spending time to get your PC side right. I know it's not always simple.
2) If multiple problems are reported form a specific area, it could be a tower or transmission line that's down.
3) If it comes from all over the show, probably a back-end system, etc.
When you guys reports problems here, the first thing I do is look at your location, but unfortunately not everyone completes the field.
Also, please report the problem. So often, you guys suffer in silence and no one knows there's a problem!
A (simplified) process:
VMC Dashboard->Windows OS->Drivers->PC hardware->Data card->radio tower->transmission line->Radio Controller->transmission line->authentication servers (some interconnected by transmission lines)
If any component, in the path, gives problems, the end-to-end connection can't be established and Windows will return a generic "I could not connect' error, the dreaded 619.
The above is just the physical path, there are also a lot of configuration parameters as well:
1) Is the SIM provisioned for data.
2) If on pre-paid, do you have credit.
3) Are you using the right APN. (I've made this mistake a few times
)4) Are the DNS settings, etc. correct.
Once you've been issued an IP, there still might be problems, but they'll typically give other errors such as HTTP, routing, DNS, firewall, etc. errors.
So, 619 is often more a pain than anything else, as it does not give any indication of where the problem might be. The only way to narrow it down is to look for common reports, thus the importance to get accurate location information. The call desk will then use the above path to try and find the cause.
1) If only one report comes from a specific area, it can very well be on the PC side.
The fact that so often a reboot fixes the error points to a problem on the PC side.
My own setup never gives 'local' 619's, I probably got two 619's in the last month and both times there was a actual network problem.
So it worth it spending time to get your PC side right. I know it's not always simple.
2) If multiple problems are reported form a specific area, it could be a tower or transmission line that's down.
3) If it comes from all over the show, probably a back-end system, etc.
When you guys reports problems here, the first thing I do is look at your location, but unfortunately not everyone completes the field.
Also, please report the problem. So often, you guys suffer in silence and no one knows there's a problem!
Heh, so a 619 is basically the equivalent of "A general error occurred" .
Maybe for future development these connect software that generates these vague errors must send off some sort of SMS via the SIM to report the error (unless they can generate more specific errors). Then the command center can have their dashboards light up when theirs a significant amount of errors coming from a specific tower/area.
I know for a fact, i am not going to phone the helpdesk everytime i get a 619, because i know it can basically be anything and the helpdesk can only tell me
"reboot your pc" or "oh you are the 50th person to call now, there must be problem in your area" . (Of course if i get it all the time for a week, i will have no choice..but by then everyone is already pretty pissed off)
End result, helpdesk will never know about the possibility of a network problem. I am sure eventually everyone will stop phoning on every 619 error.
Out of interest, i assume Vodacom has other means of detecting/monitoring problems their towers? Surely there is a huge screen on every regional IT control centre wall with each tower/area having a status of "red/blue/yellow" based on network activity ?
Maybe for future development these connect software that generates these vague errors must send off some sort of SMS via the SIM to report the error (unless they can generate more specific errors). Then the command center can have their dashboards light up when theirs a significant amount of errors coming from a specific tower/area.
I know for a fact, i am not going to phone the helpdesk everytime i get a 619, because i know it can basically be anything and the helpdesk can only tell me
"reboot your pc" or "oh you are the 50th person to call now, there must be problem in your area" . (Of course if i get it all the time for a week, i will have no choice..but by then everyone is already pretty pissed off)
End result, helpdesk will never know about the possibility of a network problem. I am sure eventually everyone will stop phoning on every 619 error.
Out of interest, i assume Vodacom has other means of detecting/monitoring problems their towers? Surely there is a huge screen on every regional IT control centre wall with each tower/area having a status of "red/blue/yellow" based on network activity ?
Last edited:
Remember, the 619 error is generated by Windows and not the VMC dashboard, so we need to bug Microsoft to provide better error codes!
The network is monitored by an array of Network Management Tools, but certain conditions are difficult to track. But in general, when you see an error, the tools would have seen it as well.