D7000 V1.0.1.54_1.0.1 scheduling issues

[eleced]

Hi,

D7000 with V1.0.1.54_1.0.1 has a regression with scheduling.  Prior versions used to work fine, but now when I enter scheduling start and end times, after hitting apply the end time moves to the start time box and the start time sets to 0.

The router has had a restart since this version (WiFi instability with some devices - another regression?!).  But I'll do another restart just to be sure.

Any suggestions?  Or new FW version coming soon ...

Regards

  Ed

[eleced · Accepted solution]

Hi,

I've had enough of no support from Netgear.  Modem went back to the store today (as it is faulty and not working as it should), and store credit against a nice TP-Link Archer VR2800.  they offer free 24 hour tech support, 3 year warranty and much better parental controls / schedulling (by MAC address, as it should be done).

Regards

   Ed

[tony-99]

Hi,

I had the same issue and it is bloody frustrating. Anyway I found a way to work around it -

go back to V1.0.1.52 and the schedule works fine...then if you want, you can update it back to V1.0.1.54 as the schedule data still available. But don't attempt to update the schedule again, as V1.0.1.54 will screw up the start & end block time.

Hope, Netgear techo would will fix up this silly bug for the next release of firmware for D7000.

Tony

[eleced]

V1.0.1.64_1.0.1 still has the issue.

[eleced · Accepted solution]

Hi,

I've had enough of no support from Netgear.  Modem went back to the store today (as it is faulty and not working as it should), and store credit against a nice TP-Link Archer VR2800.  they offer free 24 hour tech support, 3 year warranty and much better parental controls / schedulling (by MAC address, as it should be done).

Regards

   Ed

[badsac]

Should the original poster sending the modem back and buying a different brand really be the accepted solution to this problem?

I've got the same problem with my D7000v1. I'm trying to block sites by schedule. Try to set the schedule time and get the above mentioned behaviour. This is on 64. I really hope Netgear is doing something to fix this. This functionality is very important to our situation.

[tominwi]

Clearly since this thread is marked Solved you should start a new one!