It is not working for me and my original OW login does not work anymore either.
Not that I am worrying about it. I'm using Networx to monitor usage on 3 of the 4 PC's just to get a rough estimate.
-
Join the MyBroadband community
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
-
Question of the Day: Do you think Bafana Bafana will win tonight?
OpenWeb ADSL Feedback Thread
- Thread starter MrBEEP
- Start date
- Status
It is not working for me and my original OW login does not work anymore either.
Not that I am worrying about it. I'm using Networx to monitor usage on 3 of the 4 PC's just to get a rough estimate.
I'm almost to afraid to post with the grammar police around. Its not always easy for a boertjie
"...almost TOO afraid...".
Welcome fellow boertjie.
That's why I use google and F7 in word to fix my grammer grammar, but sometimes something slips through, LOL.
Hi Hooligan,
Welcome to MyBB
Kindly PM me your details so that I can see what is wrong here.
Welcome to MyBB
Kindly PM me your details so that I can see what is wrong here.
May I suggest you click the little triangle with the exclamation mark in and report him.
I will no longer be responding to the individuals posts as he refuses to PM me with details of his problem.
I will no longer be responding to the individuals posts as he refuses to PM me with details of his problem.
Snail,
Jy is al lank genoeg op MyBB om te weet jy moet mooi spel!
Ons hou nie van snaakse engels nie!
(How was my attempt at Afrikaans?)
Jy is al lank genoeg op MyBB om te weet jy moet mooi spel!
Ons hou nie van snaakse engels nie!
(How was my attempt at Afrikaans?)
There are no general issues with streaming currently.
****Youtube's super slow tonight!
May I borrow a gun?
I would prefer to shoot him, at point blank range, as he is an idiot.
I would prefer to shoot him, at point blank range, as he is an idiot.
My Utube is running ok. It buffered a little earlier, but now its smooth sailing.
****
AthenianOwl
Executive Member
- Joined
- Feb 9, 2009
- Messages
- 8,897
- Reaction score
- 4
Code:
C:\Users\******>ping mybroadband.co.za -n 100
Pinging mybroadband.co.za [197.242.89.170] with 32 bytes of data:
Reply from 197.242.89.170: bytes=32 time=70ms TTL=51
Reply from 197.242.89.170: bytes=32 time=69ms TTL=51
Reply from 197.242.89.170: bytes=32 time=69ms TTL=51
Reply from 197.242.89.170: bytes=32 time=68ms TTL=51
Reply from 197.242.89.170: bytes=32 time=69ms TTL=51
Reply from 197.242.89.170: bytes=32 time=69ms TTL=51
Reply from 197.242.89.170: bytes=32 time=68ms TTL=51
Reply from 197.242.89.170: bytes=32 time=69ms TTL=51
Reply from 197.242.89.170: bytes=32 time=69ms TTL=51
Reply from 197.242.89.170: bytes=32 time=69ms TTL=51
Reply from 197.242.89.170: bytes=32 time=69ms TTL=51
Reply from 197.242.89.170: bytes=32 time=69ms TTL=51
Reply from 197.242.89.170: bytes=32 time=69ms TTL=51
Reply from 197.242.89.170: bytes=32 time=69ms TTL=51
Reply from 197.242.89.170: bytes=32 time=69ms TTL=51
Reply from 197.242.89.170: bytes=32 time=70ms TTL=51
Reply from 197.242.89.170: bytes=32 time=69ms TTL=51
Reply from 197.242.89.170: bytes=32 time=69ms TTL=51
Reply from 197.242.89.170: bytes=32 time=68ms TTL=51
Reply from 197.242.89.170: bytes=32 time=68ms TTL=51
Reply from 197.242.89.170: bytes=32 time=69ms TTL=51
Reply from 197.242.89.170: bytes=32 time=70ms TTL=51
Reply from 197.242.89.170: bytes=32 time=69ms TTL=51
Reply from 197.242.89.170: bytes=32 time=69ms TTL=51
Reply from 197.242.89.170: bytes=32 time=68ms TTL=51
Reply from 197.242.89.170: bytes=32 time=68ms TTL=51
Reply from 197.242.89.170: bytes=32 time=69ms TTL=51
Reply from 197.242.89.170: bytes=32 time=69ms TTL=51
Request timed out.
Reply from 197.242.89.170: bytes=32 time=69ms TTL=51
Reply from 197.242.89.170: bytes=32 time=68ms TTL=51
Reply from 197.242.89.170: bytes=32 time=69ms TTL=51
Reply from 197.242.89.170: bytes=32 time=69ms TTL=51
Reply from 197.242.89.170: bytes=32 time=69ms TTL=51
Reply from 197.242.89.170: bytes=32 time=68ms TTL=51
Reply from 197.242.89.170: bytes=32 time=69ms TTL=51
Reply from 197.242.89.170: bytes=32 time=68ms TTL=51
Reply from 197.242.89.170: bytes=32 time=69ms TTL=51
Reply from 197.242.89.170: bytes=32 time=71ms TTL=51
Reply from 197.242.89.170: bytes=32 time=69ms TTL=51
Reply from 197.242.89.170: bytes=32 time=68ms TTL=51
Reply from 197.242.89.170: bytes=32 time=69ms TTL=51
Reply from 197.242.89.170: bytes=32 time=69ms TTL=51
Reply from 197.242.89.170: bytes=32 time=69ms TTL=51
Reply from 197.242.89.170: bytes=32 time=69ms TTL=51
Reply from 197.242.89.170: bytes=32 time=69ms TTL=51
Reply from 197.242.89.170: bytes=32 time=68ms TTL=51
Reply from 197.242.89.170: bytes=32 time=68ms TTL=51
Reply from 197.242.89.170: bytes=32 time=69ms TTL=51
Reply from 197.242.89.170: bytes=32 time=68ms TTL=51
Reply from 197.242.89.170: bytes=32 time=69ms TTL=51
Reply from 197.242.89.170: bytes=32 time=68ms TTL=51
Reply from 197.242.89.170: bytes=32 time=69ms TTL=51
Reply from 197.242.89.170: bytes=32 time=69ms TTL=51
Reply from 197.242.89.170: bytes=32 time=68ms TTL=51
Reply from 197.242.89.170: bytes=32 time=68ms TTL=51
Reply from 197.242.89.170: bytes=32 time=68ms TTL=51
Request timed out.
Request timed out.
Reply from 197.242.89.170: bytes=32 time=69ms TTL=51
Reply from 197.242.89.170: bytes=32 time=69ms TTL=51
Reply from 197.242.89.170: bytes=32 time=68ms TTL=51
Reply from 197.242.89.170: bytes=32 time=68ms TTL=51
Reply from 197.242.89.170: bytes=32 time=69ms TTL=51
Reply from 197.242.89.170: bytes=32 time=69ms TTL=51
Reply from 197.242.89.170: bytes=32 time=68ms TTL=51
Reply from 197.242.89.170: bytes=32 time=69ms TTL=51
Reply from 197.242.89.170: bytes=32 time=69ms TTL=51
Reply from 197.242.89.170: bytes=32 time=68ms TTL=51
Reply from 197.242.89.170: bytes=32 time=69ms TTL=51
Reply from 197.242.89.170: bytes=32 time=69ms TTL=51
Reply from 197.242.89.170: bytes=32 time=69ms TTL=51
Reply from 197.242.89.170: bytes=32 time=68ms TTL=51
Reply from 197.242.89.170: bytes=32 time=69ms TTL=51
Reply from 197.242.89.170: bytes=32 time=68ms TTL=51
Reply from 197.242.89.170: bytes=32 time=69ms TTL=51
Reply from 197.242.89.170: bytes=32 time=69ms TTL=51
Reply from 197.242.89.170: bytes=32 time=69ms TTL=51
Reply from 197.242.89.170: bytes=32 time=69ms TTL=51
Reply from 197.242.89.170: bytes=32 time=68ms TTL=51
Reply from 197.242.89.170: bytes=32 time=69ms TTL=51
Reply from 197.242.89.170: bytes=32 time=69ms TTL=51
Reply from 197.242.89.170: bytes=32 time=68ms TTL=51
Reply from 197.242.89.170: bytes=32 time=68ms TTL=51
Reply from 197.242.89.170: bytes=32 time=69ms TTL=51
Reply from 197.242.89.170: bytes=32 time=69ms TTL=51
Reply from 197.242.89.170: bytes=32 time=68ms TTL=51
Reply from 197.242.89.170: bytes=32 time=69ms TTL=51
Reply from 197.242.89.170: bytes=32 time=69ms TTL=51
Reply from 197.242.89.170: bytes=32 time=68ms TTL=51
Reply from 197.242.89.170: bytes=32 time=68ms TTL=51
Reply from 197.242.89.170: bytes=32 time=69ms TTL=51
Reply from 197.242.89.170: bytes=32 time=69ms TTL=51
Reply from 197.242.89.170: bytes=32 time=68ms TTL=51
Reply from 197.242.89.170: bytes=32 time=69ms TTL=51
Reply from 197.242.89.170: bytes=32 time=69ms TTL=51
Reply from 197.242.89.170: bytes=32 time=69ms TTL=51
Reply from 197.242.89.170: bytes=32 time=69ms TTL=51
Reply from 197.242.89.170: bytes=32 time=69ms TTL=51
Reply from 197.242.89.170: bytes=32 time=69ms TTL=51
[B]Ping statistics for 197.242.89.170:
Packets: Sent = 100, Received = 97, Lost = 3 (3% loss),
Approximate round trip times in milli-seconds:
Minimum = 68ms, Maximum = 71ms, Average = 68ms[/B]
C:\Users\******>Not good
****, I hate Telkom! Maybe I should ask them to downgrade my line back to 2Mbps from 4Mbps tomorrow.Baie goed. Kan ons dit asb meer gereeld sien?
And thank you for the quick fix - speed is great once again.
I extend a virtual HI-5, as well as a small apology for sounding a bit sarcastic in my previous comment due to frustration.
I am out of here.
I will try improve my grammar so people dont get upset.
Report me? For what? Please explain what I have done that is against the rules.
I have shown twice I am a client. I should not need to be one to get straight answers. But I have still proven I am. I dont want to message you any details.
I have said before my problem is daytime speeds with accounts that cost more that is advertised as being higher priority. But then someone on a lower account has no problems. This is inconsistent. This is the most reported on issue in this thread. Why do the accounts so often become slow after a few months like mine?
Then the next most reported issue, which I have not been affected with yet. I am curious about the nonstop authentication problems. Each time people gets told to message you and they get a new account. No explanation for those wondering. What happened to the old account?
Each time I have asked this I get called a troll, I get told to message my details, no answers or explanations given. And not for any other customer either, only message me the problem and you talk about it in private without an explanation for the people that is curious because they experiencing the same problem.
Then the next problem which is now becoming reported more here. I am curious about the talk of account sharing.
You said:
You say there have been a few cases in the past where the system is to blame.
Then why do so many people see duplicates in the IS user stats if it is just "a few cases"?
Is the system to blame for this too?
If anyone thinks I am trolling I challenge you to show me where!
Captain Beer
Executive Member
@MrBeep, what is the reason for some of us having to constantly get new usernames? The accounts seem to die after a few weeks and then Leon or Dane will assign a new account.
Dade Murphy
Senior Member
Thought there was problems with my ADSL line until I just saw full speed on torrents now. Looks like Leon Gold accounts are getting quite heavily shaped during the day.
TEXTILE GUY
Honorary Master
Firstly - let me say I feel the pain with slow daytime browsing, but it seems to be fixed for now.
As for the account changes - as was explained to me by Leon - it had to do with alternate routing to find something that works for me. Of course Telkom line issues are a different matter, and often resetting the port on Telkoms side fixes all sorts of issues (but not the daytime speed).
Secondly - IMHO, if you had sent a PM to OW, and they had still not attempted resolution then sure, rant, and you have the right to because you did what was asked of you. I has a similar experience with OW last year - but after proving that I had indeed done what they had asked and was still having issues - they very quickly made it all good and called me back to check I was happy. That impressed the sh.t out of me.
Thirdly - On the issue of trolling - I believe I am somewhat of an expert in this field - ask MWEB guy.
Having said that its possibly not the issues you have raised (which are valid IMHO) but the WAY or TONE in which the issue was raised. Looking at your sig, I can see that you a reasonable kind of guy.
Finally - You really have two options - to either follow OWs suggested path ie PM Mr. Beep and take it from there, or dump OW and try another ISP. Sometimes, certain ISPs in certain areas just work for certain needs. WA, AH, Plugg and (heaven forbid the threshold cr.p) MWEB are all good alternatives.
Good luck buddy - I hope it comes right for you, but seriously, I would suggest starting with that PM.
Orbiter
Senior Member
If a product does not work for you, find another one and move on...no need to suffer, or let others suffer...life does not need to be so complicated...
i.got~issues
Expert Member
I would like to know info about account authentication issues and whats been said by others to be account sharing. There are a lot of people that want to know.
1) What happens to the accounts that they start not authenticating? Why are new account details given? What happened to the old one?
The accounts also become slow and then new ones given as this person asked. Will he get answered?
2) If usernames are not assigned more than once and there have only been a few cases in the past of a system error, then why is multiple people sharing account details being brought up quite often? What is the explanation?
The customers deserves to know about these without needing to only PM if there is a problem. People thinking of signing up should also know I feel.
Its the ignoring of questions and the ''cloack and dagger'' dealing with everything in PM that leads to these questions and bad ways and tones for which I apologize. But no answer is ever given.
1) What happens to the accounts that they start not authenticating? Why are new account details given? What happened to the old one?
The accounts also become slow and then new ones given as this person asked. Will he get answered?
2) If usernames are not assigned more than once and there have only been a few cases in the past of a system error, then why is multiple people sharing account details being brought up quite often? What is the explanation?
The customers deserves to know about these without needing to only PM if there is a problem. People thinking of signing up should also know I feel.
Its the ignoring of questions and the ''cloack and dagger'' dealing with everything in PM that leads to these questions and bad ways and tones for which I apologize. But no answer is ever given.
Firstly - let me say I feel the pain with slow daytime browsing, but it seems to be fixed for now.
As for the account changes - as was explained to me by Leon - it had to do with alternate routing to find something that works for me. Of course Telkom line issues are a different matter, and often resetting the port on Telkoms side fixes all sorts of issues (but not the daytime speed).
Secondly - IMHO, if you had sent a PM to OW, and they had still not attempted resolution then sure, rant, and you have the right to because you did what was asked of you. I has a similar experience with OW last year - but after proving that I had indeed done what they had asked and was still having issues - they very quickly made it all good and called me back to check I was happy. That impressed the sh.t out of me.
Thirdly - On the issue of trolling - I believe I am somewhat of an expert in this field - ask MWEB guy.
Having said that its possibly not the issues you have raised (which are valid IMHO) but the WAY or TONE in which the issue was raised. Looking at your sig, I can see that you a reasonable kind of guy.
Finally - You really have two options - to either follow OWs suggested path ie PM Mr. Beep and take it from there, or dump OW and try another ISP. Sometimes, certain ISPs in certain areas just work for certain needs. WA, AH, Plugg and (heaven forbid the threshold cr.p) MWEB are all good alternatives.
Good luck buddy - I hope it comes right for you, but seriously, I would suggest starting with that PM.
What's this slow daytime speeds I hear of?
I'm on Gold and I get full daytime speeds - Just downloaded 100mb in 9 minutes.
Oh wait, this is Openweb - where some accounts are more equal than others.
Both these questions have been answered in the past.
1) What happens to the accounts that they start not authenticating? Why are new account details given? What happened to the old one?
The accounts also become slow and then new ones given as this person asked. Will he get answered?
We have a different approach to troubleshooting at OpenWeb. Many ISPs will simply drag the matter along for weeks and weeks without the client getting any sort of meaningful solution. We do not agree with this method, therefore generally tend to assign a new username that have a different set of backend rules or that would use a different route to the DC or sometimes even a completely different network alltogether. This has produced many positive results, and more than likely the new route suits the client better in the long run.
2) If usernames are not assigned more than once and there have only been a few cases in the past of a system error, then why is multiple people sharing account details being brought up quite often? What is the explanation?
Both cases that were reported had different reasons. The first issue was related to an error on the backend where two clients ordered a package seconds after each other. The system assigned two different usernames and passwords and sent it to the relevant clients. However, on the backend report for some reason it combined the stats of the two different usernames into one. The other instance we could not see a second connection on the clients account. We have since changed the client to an account that monitors usage stats accurately, and assigned him a very strong password and enabled his ability to change his own password.
Edit:
Let me add this one as well:
Then why do so many people see duplicates in the IS user stats if it is just "a few cases"?
OpenWeb runs its own capacity with IS. 'Sharing' accounts on purpose would be a futile excercise as we already pay for the total pipe irrelevant of the amount of users we load onto it.
We do NOT by default log usage stats on uncapped. This is a policy we adopted early as many folks do not want their ISP to know how much and what they are doing on the web. We have discussed this a few times, but it seems like the sentiment has changed over the last while. We are therefore building in a full set of usage monitoring tools in the future and these will be activated by default as the demand for this is up.
In a way we are sharing capacity, but this is on a large scale, as we would buy x amount of Mbps and sell y amount of accounts with the y being a larger number than the x. This is called contention ratio. This is where Gold etc comes into play, as a Gold member you 'share' with less people thus the overall improved experience.
1) What happens to the accounts that they start not authenticating? Why are new account details given? What happened to the old one?
The accounts also become slow and then new ones given as this person asked. Will he get answered?
We have a different approach to troubleshooting at OpenWeb. Many ISPs will simply drag the matter along for weeks and weeks without the client getting any sort of meaningful solution. We do not agree with this method, therefore generally tend to assign a new username that have a different set of backend rules or that would use a different route to the DC or sometimes even a completely different network alltogether. This has produced many positive results, and more than likely the new route suits the client better in the long run.
2) If usernames are not assigned more than once and there have only been a few cases in the past of a system error, then why is multiple people sharing account details being brought up quite often? What is the explanation?
Both cases that were reported had different reasons. The first issue was related to an error on the backend where two clients ordered a package seconds after each other. The system assigned two different usernames and passwords and sent it to the relevant clients. However, on the backend report for some reason it combined the stats of the two different usernames into one. The other instance we could not see a second connection on the clients account. We have since changed the client to an account that monitors usage stats accurately, and assigned him a very strong password and enabled his ability to change his own password.
Edit:
Let me add this one as well:
Then why do so many people see duplicates in the IS user stats if it is just "a few cases"?
OpenWeb runs its own capacity with IS. 'Sharing' accounts on purpose would be a futile excercise as we already pay for the total pipe irrelevant of the amount of users we load onto it.
We do NOT by default log usage stats on uncapped. This is a policy we adopted early as many folks do not want their ISP to know how much and what they are doing on the web. We have discussed this a few times, but it seems like the sentiment has changed over the last while. We are therefore building in a full set of usage monitoring tools in the future and these will be activated by default as the demand for this is up.
In a way we are sharing capacity, but this is on a large scale, as we would buy x amount of Mbps and sell y amount of accounts with the y being a larger number than the x. This is called contention ratio. This is where Gold etc comes into play, as a Gold member you 'share' with less people thus the overall improved experience.
Last edited:
- Status