on 27-08-2012 11:58
Only very occasionally, and then only after a re-boot - sometimes - can I get in to my Super(not)hub from 192.168.0.1.
I can ping it no problem
I guess my best bet is to disable to router part and use it in modem-only mode.
But I need to get in to set this up...
Anybody able to offer any advice?
on 27-08-2012 14:59
on 27-08-2012 16:33
on 27-08-2012 19:37
Might be worth a try with a different web browser, I remember them saying some people were experiencing difficulties with one of them with R36
on 28-08-2012 13:33
Thanks guys - just tried Opera - no difference.
Will take my gonads in hand tonight and try 'modem only' mode. - assuming I can get into router via direct ethernet connection to change setting...
on 29-08-2012 02:12
The problem of not being able to login to the Superhub has been an issue for months and months, and has affected many Virgin customers (as proved by posts on several other threads). For example, it has been a major issue for myself from the day I first received a Superhub in Jan'12.
Customers find they can only see the Superhub login page after a reset or power cycle, but after a few days any attempt to access the login page (192.168.0.1) results in a time out. Clearly, it is unacceptable to expect customers to reset their Superhub every few days.
The issue is due to a Superhub firmware bug in R30, that was never fixed in R36 i.e. the issue has been there for many, many months.
Regardless of what Virgin staff may believe, it is not a Chrome related issue. For example, I have never run Chrome, yet have always had the issue. I have only every run Internet Explorer(on two seperate PCs) and Safari(on two separate iPads, plus on an iPod Touch) i.e. the issue is seen on five separate devices, none of which runs Chrome. Also, many other customers have posted that they have not been using Chrome.
I do wish this issue was taken more seriously by Virgin, and given some effort to fix, and also not confused as a Chrome related issue.
FYI, another thread has been running for many months describing the same issue. So far that thread has nine pages of posts i.e. many posts from many users covering both R30 & R36. Maybe you should add your comments there are well in the hope of getting some action from Virgin to fix the generic firmware bug.
on 30-08-2012 14:23
Sorry to see that you've experienced problems with our equipment, just to clarify - have you performed a factory reset on the Superhub?