NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
DrXtreme
Dec 11, 2016Tutor
R7300 DST, QOS, Automatically update performance optimization database fails
Is there a setting that I need to change to get the QOS database update to work? When I click "Update Now" to check for new data it returns "Attempting to connect to Netgear Server. Please Wait..."...
jphall69
Jan 11, 2017Aspirant
Has this problem been rectified?
I have the latest firmware. Cannot update the performance optimization database.
Thank you
- strubinskyJan 11, 2017Guide
I am waiting for ElaineM. She has a beta version - I think - that fixes the problem.
What surprises me is that this product appeared the first time around a year ago. I know for a fact, that the update did not work and assumed that there was none since the update function failed back then while it now tells you what version you could have but -naa-na-na-na-naaa-naaa- will not get. You can watch, but not download.
I would have hoped that this problem -which seems common for the r7300dst- would have been fixed after 1 year. But it is not. This router seems to be treated like the red-haired orphan since you won't even get any kind of support through the normal channels but only through the GeekSquad who is too geeky to even know that they are supposed to support this router. I found that out via phone and in person.
I wished it would receive some TLC from the Netgear geeks! Its OS can also not be replaced with the DD-WRT as opposed to many others of this family and I have the feeling that the hardware can support way more than it does momentarily.
- ElaineMJan 11, 2017NETGEAR Employee Retired
strubinsky Did you receive the beta yet?
- strubinskyJan 11, 2017Guide
The link from dec must have expired. I received a 404
- strubinskyJan 17, 2017Guide
The version Elaine offers did solve the update problem. But the router asks now every time if I want to update to a newer shinier newer version. I was on this newer version and it had the bug for which we all come here for to begone.
My question is now: How will we know when it's time to get back into the herd and rejoin the production codebase? What we have is beta and well, beta is not fully tested-. I have had some strange experiences, but they may very well be the result of a privacy software that I loaded pretty simultaneously with the beta. So it can very well be that our firmware is just fine but my privacy thingi may be momentarily a bit too paranoid.
Concluding: How can we find out when there will be a version that is PRD status and openly available AND has our problem fixed and we should give into the (well meant and appreciated) nagging of our router to go get the newest firmware??