on 10-01-2011 08:59
Yes, another one...
We got 50mbit installed in November, though we did not move into our new place until the weekend. It seemed to work fine, but I only used 1 device with it.
Now that I have all my devices attached (NAS, Sonos, iPad, PC, laptops, PS3, AV Amp etc etc) it seems to drop out randomnly, first time it done it within 2 hours, second time 12 hours. Each time it does it, the modem lights flash and cannoy connect to the modem through ethernet or WLAN.
I've read around and seen that disabling Firewall / IP Flood protection helps. The SNR is good (42db if I recall correctly) and the speed tests are always good. Astraweb is also nice and fast.
Is this likely the cause of my problem? Or do I need to get a new superhub? Coming from a Draytek 2820n on 24mbit ADSL2, which I rebooted once to upgrade firmware in over a year or so, this is hugely disappointing.
Or are there any other proper modems out there?
on 10-01-2011 11:35
I have read people turning off the firewall to solve the problem your describing. However I have the superhub with firewall on with more devices connected than you have mentioned and never had a drop out.
on 10-01-2011 16:49
Thanks, sadly it is still doing it ![]()
What should I do? When it disconnects, the router is completely unresponsive and has to be rebooted. It basically drops internet connection, and you cannot connect to the WLAN or ethernet.
So it won't be the line right if it is not responding at all to network devices
on 10-01-2011 21:13
You can attach your Draytek router to the hub and bypass the hub's router functions. As you may know, VM are providing a firmware update to allow you to turn the router function off. Heaven knows why those fools who decide these things didn't release the hub with this important disabling feature in it.
In the meantime, you could do the following (adapted from a post by DJ-Shadow):
on 11-01-2011 01:02
Thanks but want a working superhub ![]()
This is what happens in the event log..
Time Priority Description
Mon Jan 10 23:25:49 2011 Critical (3) No UCDs Received - Timeout;;CM-MAC=macaddress1;CMTS-MAC=**:**:**:**:*
Mon Jan 10 23:25:32 2011 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=macaddress1;CMTS-MAC=**:**:**:**:**
Mon Jan 10 23:25:24 2011 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=macaddress1;CMTS-MAC=macaddress2;C
Mon Jan 10 23:25:07 2011 Critical (3) DHCP FAILED - Requested Info not supported.;CM-MAC=macaddress1;CMTS-MAC=macaddress2
Mon Jan 10 23:24:49 2011 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=macaddress1;CMTS-MAC=macaddress2;C
Mon Jan 10 23:23:59 2011 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=macaddress1;CMTS-MAC=macaddress2;CM-QOS
And, the line stats....
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Anything look suspect at all?
Thanks
on 11-01-2011 09:57
Your problem as I see it is that downstream power is too high and needs to be brought down below 6 dBmv, preferably to 0 dBmv.
The router question is one of taste and functionality which appeared to need addressing from the thread context.
on 11-01-2011 13:21
Thanks. Yes I presumed it was the router at fault, I was puzzled why it freezes completely (hence assuming it was router related) rahter than just dropping and router still works.
What's the best way of getting resolved, waiting for a tech to PM me?
Thanks
on 11-01-2011 13:24
They won't PM you unless you've posted from elsewhere on another connection. Just hang on here 2-3 days and they'll get to you.
Or ring 0800 052 0431 and hope you get UK support (mornings seem best).
on 11-01-2011 19:00
Hi I am having the same problems with random disconnects with the superhub..
on 11-01-2011 19:02
xXJordanBXx44 wrote:Hi I am having the same problems with random disconnects with the superhub..
Don't hijack this thread as all you are doing is delaying a response from support for the OP. Start your own thread.