NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
New Intel NUC Computer - Cannot communicate with or ping some network IP devices
I recently purchased this device (device details below) as a replacement for an existing HP laptop I used as a home security and automation server. After full configuration, I have run into a ...
I wish that was the issue, since I've had it set to "Private Network" since day one, that would have saved me a lot of time and aggravation.
So one thing that came to mind was that maybe the issue could be that I have the Netgear Router with an IP Reservation for this and 4 other computers. While it worked fine for the others, including the one this NUC is replacing, I though maybe something in the NUC does not handle that well. So I deleted the IP reservation, set the DHCP settings on the NUC to manual and assigned it the needed static IP there. Problem continued. Some devices were visible on the NUC, some where not. Hmmm...
Finally, I FOUND THE PROBLEM and temporary solution/workaround... Netgear Orbi's ACCESS CONTROL. I've always had access control enabled, and set to "Block all new devices from connecting". This allows new devices to connect to the WiFi, but then lists them as "Blocked" allowing you to either "Allow" or leave blocked if not recognized. I mean, who knew this could be the issue?!?! It is supposed to either block or allow the connection, not allow it and only let the device see some devices but not others.. Well, apparently, setting the Intel NUC's connection to "Allow" is not sufficient as it doesn't fully open all communication.
On a hunch, I figured I would try disabling access control completely, and suddenly all network devices were visible on the Intel NUC. To confirm, I enabled Access control again, the issue came back. Disabled, the issue was gone again.
So, that is my fix/workaround for now. I would still like to figure out a way to make the NUC's network connection work properly and fully with access control enabled, but for now, I'm happy to finally pinpoint the culprit.
If anyone knows of any setting, etc. that can correct this behavior, I welcome your input.
Hello DanInGA ,
Welcome to the NETGEAR Community!
I understand that you are having issues with your access control with your RBR50 on firmware version 2.7.4.24. I have also noted that you did not have an issue with this configuration before. Please try updating your RBR50 to the most recent firmware version 2.4.5.4 and then enabling the access control after you designated a static IP address to restart your NUC.
Navigate to the link below for the download file for your RBR50:
https://www.netgear.com/support/product/RBK50#download
For step-by-step instructions on how to manually update your RBK50 please navigate to the link below:
https://kb.netgear.com/31573/How-do-I-manually-upgrade-firmware-on-my-Orbi-router-using-orbilogin-com
Best,
Kevin
Community Team
Thank you. One of the first things I did was check for firmware updates for all devices in question, including the Netgear RBR50 and satellite and it showed up to date. I checked again just now and same.
As I would rather not be a beta tester for firmware, can you advise as to when this firmware update became available and why it does not show on the router firmware check?
Some FW updates are not pushed by NG and need to be manually updated thus won't be seen on the RBRs check FW option.
The version mentioned was released in February of this year and is available for download and manually updating:
DanInGA wrote:
One of the first things I did was check for firmware updates for all devices in question, including the Netgear RBR50 and satellite and it showed up to date.
As FURRYe38 says, this is not a reliable test. It is so bad that Netgear really needs to put some effort into fixing the problem.
There are various ways of checking for firmware updates – automatic updates, apps and tests in the browser graphical user interface (GUI) for example – but only one test is reliable. All the others have proved to be wrong in the past.
Use the GUI to find out which version you have. Then visit the support pages for your device and look for the newest version.
Visit the support pages:
Support | NETGEAR
Feed in your model number and check the documentation for your hardware.
Look for the model number on the label on the device.
That site will have a library of firmware for your device. Look for the newest.Thanks everyone. I am familiar with the manual update process as I've done it that way several times. However having been one to always jump on the latest and greatest and keep firmware on the newest version, I have learned that this isn't always necessarily a good thing. Firmware update, especially relatively recent ones can sometimes cause other unexpected issues.
So, since the problem is fixed by simply disabling Access Control, and I do not have time to run into new potential problems, I will take my time now researching this new firmware version to see if anyone has experienced any issues with it. Once I am comfortable with moving forward have more time to do so, I will perform the firmware update, reboots, testing, etc.
Thanks again all!
