F
Former member 61586
Guest
My issues have been sorted out and internet is back up and running as normal.
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
No wow... again.... haven't been able to play properly since Saturday.....
Well all my scheduled downloads failed at night again.
So, here is my description of the last 7 days with iBurst.
Last weekend in the middle of work, iBurst service goes down. Takes forever to come up, no one answers ANY phones at the call center.
iBurst in its infinite wisdom then tells people to check the international outage status updates on Twitter. An international site. #FAIL.
Now I am capped (connected with Blackberry), but alas, the page cannot be displayed when I try to top up.
Time to go hunt down a 3G router.
You appear to be asking a question there so I'll answer: not a fvcking chance; not no way, not no how; not a snowball's chance in hell ...you see where I'm going with this?You can log into the iBurst page when capped?
You appear to be asking a question there so I'll answer: not a fvcking chance; not no way, not no how; not a snowball's chance in hell ...you see where I'm going with this?
Thankfully I have my speedstick as an alternative to get in to the itbust page so I can buy a booster. So, you know, well done with how that works.
That's all well and good but "works for you" != "works for me" and, as it happens, I'm rather more interested in "works for me".Thanks for your feedback. I have logged in with an account, been capped and am still able to log into the iBurst web page and buy boosters.
Nothing works. At all. And, given that all I was going for was www.iburst.co.za, I call that a failure.What are the symptoms of what you experience when capped?
You know, I thought you had me there: I really didn't know whether I had non-iBurst DNS in my router and a check showed that I have nothing non-iBurst loaded.If you use a third party DNS like OpenDNS, then either revert back to the automatic iBurst DNS servers or add www.iburst.co.za [196.2.125.95] as an entry in the hosts file of your router or computer.
That's all well and good but "works for you" != "works for me" and, as it happens, I'm rather more interested in "works for me".
Nothing works. At all. And, given that all I was going for was www.iburst.co.za, I call that a failure.
You know, I thought you had me there: I really didn't know whether I had non-iBurst DNS in my router and a check showed that I have nothing non-iBurst loaded.
So that's not it either.
Which brings me back to it's all good and well that you SAY it works, but it doesn't really help me/us when it doesn't ...so, back to you.
PS, on a side issue: 'revert' already means 'change back' so 'revert back', she no work.You should use 'change back' or 'revert'.
C:\>nslookup www.iburst.co.zaCan you please post the results of nslookup www.iburst.co.za
C:\>tracert 196.2.97.124tracert 196.2.97.124
C:\>nslookup www.iburst.co.za
Server: fred
Address: 10.0.0.1
Non-authoritative answer:
Name: www.iburst.co.za
Address: 196.2.125.95
fred's my router (unning DD-WRT) and, in the DNS entries, has nothing*.
C:\>tracert 196.2.97.124
Tracing route to iburst-97-2-196-124.iburst.co.za [196.2.97.124]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms fred [10.0.0.1]
2 58 ms 44 ms 44 ms iburst-41-213-32-1.iburst.co.za [41.213.32.1]
3 65 ms 43 ms 44 ms 192.168.0.97
4 64 ms 44 ms 43 ms iburst-97-2-196-124.iburst.co.za [196.2.97.124]
Trace complete.
*...but, with no small amount of chagrin, I found the culprit and, in the end, you got me: it's all well and good for my router to be on iBurst DNS but it really doesn't help that my WLAN NIC was ...yes, that's right, Open-bloody-DNS(I found it when I first issued nslookup).
So, in this case, I'll shut up and skulk off to wipe the egg off my face and mull, once more, over the dictum "the devil is in the details"