thenry
25-07-2011, 14:27
I posted the following on VM offical forum > http://community.virginmedia.com/t5/Up-to-30Mb-and-50Mb-broadband/Superhub-problem-solver-possibly/td-p/622085
your all going to think I'm nuts, you probably already think so but heres something I tried and it seems to be working with regards to disconnections. I tried various things suggested my members and staff but they failed. Also I never once turned off the superhub firewall. Apologies to those thinking that does the trick, to even think of turning off the firewall to get something working is a stupid idea. A firewall is there to protect and although the current firmware has bugs, the firewall itself was built around and for something so it should be active. Anyway heres what I done with regards to disconnections and its been fine since. VM please don't toy with my connection I think I may of solved my issue not sure whether it will solve others but please don't toy with it, the superhubs have been dubbed as extremely sensitive if thats correct to say. Lastly I got so annoyed I tried whats below that might just be dubbed as insane;
Disconnect the cable feed from your superhub
Connect your old modem before recieving the superhub if you still have it > just the cable feed and power. it obviously wont work but leave it on for a few minutes then disconnect the cable feed and power that modem down and put it away. leave the cable feed alone while you do the following,
Push the tiny button on the side for 20 seconds, once the 3 blue lights come on Power down for 5 minutes.
-
Power up and again push the tiny button on the side for 20 seconds but this time let the 3 blue lights turn off while in reboot then power down
Leave the superhub alone for 5 minutes.
connect to the superhub via ethernet and make your changes then power down for a few minutes
power up and check over settings making sure their saved they should be
Now the insane bit,
go to event log and clear it
after you've cleared it and refresh the page a sync and dhcp error will probably come up. these errors come up within a time gap so try know when the error will appear in the log by refreshing the page. you basically want to clear that log, have it empty and power down at the same time so its clear when booting up again. its tricky, i sat at my desk for a good few minutes refreshing getting to know the timing of the errors so on my next boot the logs clear.
once you've mastered the events and cleared them as well as quickly powering down leave it be for another 5 minutes.
then connect the cable feed only for 10-20minutes
then power up and let it do its thing properly, just walk away do something else
if it plays up again then try the clear log thing again not the whole reboot of settings etc.
I was told I had high latency in my area etc. and I was getting numerous disconnections but ever since I tried this insane step of mine I've had none.
Again please VM don't toy with it, I've got it working somehow
lastly don't laugh at this post, I'm just sharing what worked for me :)
your all going to think I'm nuts, you probably already think so but heres something I tried and it seems to be working with regards to disconnections. I tried various things suggested my members and staff but they failed. Also I never once turned off the superhub firewall. Apologies to those thinking that does the trick, to even think of turning off the firewall to get something working is a stupid idea. A firewall is there to protect and although the current firmware has bugs, the firewall itself was built around and for something so it should be active. Anyway heres what I done with regards to disconnections and its been fine since. VM please don't toy with my connection I think I may of solved my issue not sure whether it will solve others but please don't toy with it, the superhubs have been dubbed as extremely sensitive if thats correct to say. Lastly I got so annoyed I tried whats below that might just be dubbed as insane;
Disconnect the cable feed from your superhub
Connect your old modem before recieving the superhub if you still have it > just the cable feed and power. it obviously wont work but leave it on for a few minutes then disconnect the cable feed and power that modem down and put it away. leave the cable feed alone while you do the following,
Push the tiny button on the side for 20 seconds, once the 3 blue lights come on Power down for 5 minutes.
-
Power up and again push the tiny button on the side for 20 seconds but this time let the 3 blue lights turn off while in reboot then power down
Leave the superhub alone for 5 minutes.
connect to the superhub via ethernet and make your changes then power down for a few minutes
power up and check over settings making sure their saved they should be
Now the insane bit,
go to event log and clear it
after you've cleared it and refresh the page a sync and dhcp error will probably come up. these errors come up within a time gap so try know when the error will appear in the log by refreshing the page. you basically want to clear that log, have it empty and power down at the same time so its clear when booting up again. its tricky, i sat at my desk for a good few minutes refreshing getting to know the timing of the errors so on my next boot the logs clear.
once you've mastered the events and cleared them as well as quickly powering down leave it be for another 5 minutes.
then connect the cable feed only for 10-20minutes
then power up and let it do its thing properly, just walk away do something else
if it plays up again then try the clear log thing again not the whole reboot of settings etc.
I was told I had high latency in my area etc. and I was getting numerous disconnections but ever since I tried this insane step of mine I've had none.
Again please VM don't toy with it, I've got it working somehow
lastly don't laugh at this post, I'm just sharing what worked for me :)