iBurst system upgrade this weekend.

Had a random disconnect and haven't been able to reconnect for 15 minutes now with constant username/password errors.

I can see this escalating to become quite a nuisance at this rate......*sigh*

[Update]

Reconnected at last, then had ANOTHER random disconnect 5 minutes later and after reconnecting getting the capped crap again: http://www.iburst.co.za/default.aspx?link=cap_reached

It's not much of a threat coming from me but at this rate you're going to be at least one more customer less.
 
Last edited:
Gentlemen, please check the speed of your antivirus updates... my suspicion is that the site's norton was unable to update itself successfully, and thus kept on retrying, therefore depleting all bandwidth.

Still awaiting the logs from iburst to see just what happened.
 
Can somebody else give a printout of a traceroute to liveupdate.symantec.com?

I receive the following :

C:\>tracert liveupdate.symantec.com

Tracing route to a568.d.akamai.net [165.165.39.209]
over a maximum of 30 hops:

1 57 ms 65 ms 54 ms wbs-196-2-100-1.wbs.co.za [196.2.100.1]
2 122 ms 60 ms 99 ms 192.168.0.97
3 73 ms 54 ms 60 ms 192.168.0.114
4 114 ms 115 ms 169 ms iburst-41-213-126-21.iburst.co.za [41.213.126.21]
5 74 ms 59 ms 54 ms 41.0.4.225
6 107 ms 115 ms 110 ms rrba-akamai-209.telkom-ipnet.co.za [165.165.39.209]

Trace complete.
Click to expand...

Something's not right somewhere... maybe it's telkom again? :(

It should be fast, seeing that it's only 6 hops...
 
Ok - Could log in now.

Same issues as reported by other users re. bandwidth usage - Indicates : 0
Also - Contract Term indicated as : 12 when it should be month to month.
 
C:\>tracert liveupdate.symantec.com

Tracing route to a568.d.akamai.net [165.165.39.209]
over a maximum of 30 hops:

1 57 ms 65 ms 54 ms wbs-196-2-100-1.wbs.co.za [196.2.100.1]
2 122 ms 60 ms 99 ms 192.168.0.97
3 73 ms 54 ms 60 ms 192.168.0.114
4 114 ms 115 ms 169 ms iburst-41-213-126-21.iburst.co.za [41.213.126.21]
5 74 ms 59 ms 54 ms 41.0.4.225
6 107 ms 115 ms 110 ms rrba-akamai-209.telkom-ipnet.co.za [165.165.39.209]

Cached locally by Akamai.

Probably iBurst being slow as usual, updates from m$ are going at a crawl.


D:\>wget -c -t0 ftp://ftp.is.co.za/ls-lR.bz
--2009-08-17 14:05:44-- ftp://ftp.is.co.za/ls-lR.bz
=> `ls-lR.bz'
Resolving ftp.is.co.za... 196.4.160.12
Connecting to ftp.is.co.za|196.4.160.12|:21... connected.
Logging in as anonymous ... Logged in!
==> SYST ... done. ==> PWD ... done.
==> TYPE I ... done. ==> CWD not needed.
==> SIZE ls-lR.bz ... 69725577
==> PASV ... done. ==> RETR ls-lR.bz ... done.
Length: 69725577 (66M)

0% [ ] 39,208 3.81K/s eta 6h 29m

^C

Sooner we cancel this service the better.
 
Still no change with regard to Bandwidth consumed details (Now at -1MB Downloaded , -13 MB Uploaded ??) as well as incorrect contract period (12 instead of 1 - Am assuming month to month would be one)...

Does this mean we can download like crazy? :D
 
I have just the (known) issue:

Received: -16MB
Sent: -8MB
Carried over: 0
Purchased: 0
Total: 25MB
Remaining: 1365.6882

Don't really get the minuses (-) but I do beleive that remaining is OK...(Pro Classis 3,5 package)....
 
Well, it's gone *mostly* well so far. Guys are still sorting problems here and there, so please keep on logging any issues.

This morning at about 4AM we got to a point where we knew we were not 100% but it was at a point where, if we rolled back, it would've put us back a week or two.

So we decided to push on and solve the gremlins as they pop up.

Thanks for the patience and understanding and especially for the feedback. Please keep on posting any problems.
 
Browsing is painfully slow tonight.

Me being patient...:cool:
 
Well I still can't log in so I'll try again tomorrow and post again :)

EDIT - Still can't login...
 
Last edited:
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X