"Attached devices" and "Access Control" not working on Nighthawk X10

Thank you for link, I was able to successfully update router. Unfortunately it did not fixed my issue. I assume that factory default is required which btw is very poor solution. Anyone tried to do backup, factory default and restore backup? Do we know if that will work?

Can we get some official response from Netgear?

bbaraniec wrote:

Thank you for link, I was able to successfully update router. Unfortunately it did not fixed my issue. I assume that factory default is required which btw is very poor solution.

Can't agree more - however thats not a new complaint.

@@bbaranie wrote:

Anyone tried to do backup, factory default and restore backup? Do we know if that will work?

In my understanding, you will backup a potentially corrupted configuration, which might end on the backup storage complete or incomplete - restore will revert what the factory reset has hopefully fixed before. There is no validity checking, consistency testing, syntax check, whatever on these consumer devices.

bbaraniec wrote:

Can we get some official response from Netgear?

ChristineT@ please. Why ever, I can't add Alex using @....

Is it possible to wipe Access Control config via telnet? Surerly better solution than factory defaults. Yeah we need a Netgear Engineer.

The factory reset is required for it to take into effect. 

What really bothers me:

1.0.4.2 is realesed 18th May 2018

First post in this topic is 4 days later. Over month later Netgear provides some hush hush RC firmware that prevents the issue if it still isn't broken.

Another month goes by and still no official release. How many users could have been "saved"? 

ChibiKev are you Netgear employee? 

I'm not, I'm just saying the procedures of solving the issues. 

If you read what I sent before, you would have seen that after you install the firmware, you have to reset your router. 

I also sent a screenshot of the Netgear representative that helped me solve the issue.

Right, I got confused here somehow. Anyway, Netgear wants you to factory default every single firmware update. I'm still hoping this can be fixed without it. 

I saved the image file just in case Netgear nukes me again. I can always fall back to it.

Now if they could fix the problem if the router dropping my securety cameras. It has to be in the router beacuse 

when I check the signal on the camera software it's 100%. I wish there was a way to put a outside antenna on the 

router but from what I understand the antennas are also amplified and I see no way to remove them with out breaking 

something.

ChristineT can we get some feedback from Netgear please?

bbaraniec, Thanks for the mention! Let me see what I can find out about this issue and get back to you. 

Thank you ChristineT for chiming back. The problems far to many Nighthawk users in general, and specifically on the newest leading edge router models, is that a factory reset does commonly recover from this issue. However, new added devices to the network, and/or Web Genie based operations (ie. access control), and/or Genie App, and/or the Nightawk apps, and probably more does lead to the similar issue again. This does read to me like a inconsistent or non-existing validity checking of data, including the device names coming in from systems doing the DHCP process.

Has anyone tried to load the new firwmare factory reset and then load your config file back onto the device does this work? if not let me know.

DarrenM 

Smuttyfox at any point did you get access control to work?

Smuttyfox just to clarirify, by downgrading you mean going from latest official 1.0.4.2 (the one that broken AC) to previous one or from RC firmware that was posted on forum?

---

bbaraniec wrote:

... latest official 1.0.4.2 (the one that broken AC) ...

---

Doubt this is right - either there are existing suspect corrupt config or whatever admin operations.

Let's just forget about restoring config from backup but fresh config with old firmware should work right?

Another day and there is no support from Netgear. 

bbaraniec, this is a Community Forum. It is not manned by trained NG support people but it is monitored with NG Moderator's (those with the NG icon after the name). Those moderators try to help, but they may not have the same capabilities and information as the Support team does.

If you need/want true support help you have to contact them be Support and My Support links. Depending where you live the ability to do that could be as low as 90 days after purchase.

Other than that all you can get here is help from other users like yourself and the NG Moderators...  Something new or unusual, the harder it is to help. Insufficient information also hurts the chance of getting a solution. A true firmware bug, you'll have to wait for NG to fix it, but if it hasn't been reported to them, who knows when it will get fixed.

Just trying to set the right expectations here.

IrvSp I know what community forum means and that why I was asking for Netgear opinion on this matter.

ChristineT has been mentioned first time in this topic on 23rd of May. For the next month still nothing from NG but ChibiKev posts info about RC firmware. So at this point NG is aware of the issue and may have/may be working on solution.

I'm finding this topic another month later, there is still no information from NG, there is no official firmware either, there is no clear solution to this matter. ChristineT gets mentioned again and we wait.

You see we are in the dark here. We don't know even if they were able to find the bug, yet to fix it. 

I've contacted L3 engineer but he is on vacation so all what I'm left with is contacting standard L1 support, going through all the steps explaining what's wrong, when we have already 50 posts describing the issue but no one from NG wont comment here.

I have been using Netgear App and Genie App from time to time and never before I had problems with AC not loading. First after ugrading to latest firmware and changing device name **bleep** hit the fan.

bbaraniec, at least you have an active problem being worked. I've got one on SMB 1 since 3/31 of this year... every response back to me says it is a Windows 10 problem and I must use SMB 1 to see the network shares. Well over 1 year ago MS declared the use of SMB 1 to be dangerous and END USER H/W needed to make changes to not use it. Over a YEAR ago a NG Moderator said Support was aware of it and working it. STILL nothing although some routers do seem to have moved up to SMB 3 and even allow selection of SMB 2 or 3. However on the R7000 and R8000 I have even though this has been enabled they have done a half a**** job as it isn't exposed. One STILL needs SMB 1 to make shares be used like it should be, NETBIOS names are NOT resolved without it. Yet I still get the same answer, it is a Windows problem.

Very frustrating to say the least.

IrvSp Windows is using WSDD now and Linux has no support yet for that.

SMB1 is dangerous and you should not use it, unfortunately is pain in ass without Network Discovery for some.  There is a workaround for Linux written in python: https://github.com/christgau/wsdd 

bbaraniec, I am well aware of that fact. So it seems are the moderators here. Support, doesn't seem like it?

I actually is WSD, https://docs.microsoft.com/en-us/windows/desktop/WsdApi/wsd-portal, it seems that most routers do NOT support this. Enabling SMB 3 on the R7000 and R8000 which HAS been done, isn't enough.

Just run NET VIEW on a Windows PC that is NOT running SMB 1. You get a 1231 error I recall? Even if the PC is running SMB 1 (such as W8.x or older) when a W10 PC without SMB 1 (a fresh install or an updated V1709 or later Windows PC that doesn't use SMB 1 and 30 days later W10 turns it off) no machine will work with that command. Computer Browser and Master Browser function breaks it.

There is a long thread here about this. Any time you see a thread about one can't see a share, the cause is this problem, and there are many here. One I was in over SMB1 and even used WireShark to see what was going on, https://community.netgear.com/t5/Nighthawk-WiFi-Routers/Problem-with-NET-VIEW-W10-R7000-most-recent-firmware-including/td-p/1473063 if you are interested.

Even on MS site are instructions to turn on SMB 1 for sharing, and this one is quite complete and more has to do with W10 V1803 (Spring Creator Update) turning off/Deleting HOMEGROUPS, https://answers.microsoft.com/en-us/windows/forum/windows_10-networking/connecting-pcs-and-users-for-sharing/fb92e439-5dbc-4367-9857-1ef360e9ffdf.

If you think this is only a Netgear router, thing again, I've seen reports of ASUS routers with this problem too.

Still, I feel the onus is on NG to make NET VIEW work properly with their routers. It works with SMB1 but doesn't without it... and it appears that just enabling SMB 3 and dropping SMB 1 in the router isn't enough.