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.
How is this new computer connected to the network:
- Ethernet?
- WiFi?
Does the Orbi web interface Attached Devices display match the computer information? (IP address, MAC address?)
Is there any pattern to the IP addresses that cannot be reached?
Thanks for asking. The new Intel NUC computer is connected via Ethernet and shows in the Orbi Router Config interface in Attached Devices under Connected Devices with matching MAC and static IP, as well as in Access Control as "Allowed".
There does not appear to be a pattern in the IP's it cannot seem to communicate with, other than that they are connected via WiFi, but it sees all the other WiFi devices. Most of the ones it cannot see are 2.4 Ghz, while two are 5 Ghz. Oddly, it 'sees' plenty others on both bands of the same brand, config, firmware, etc.
I did find one article pointing to the Bios C-State setting as the cause of a computer not seeing all network devices, however, the Bios of the Intel NUC does not even show that setting (or it is called something different). So back to square one..
Three computers behave normally and one does not. "points the finger" at some obscure setting on the Intel machine.
Might be useful to switch the connection to WiFi. The Intel AX201 is more advanced than the Orbi WiFi, but should be backward compatible.
Agreed.. All is good with 3-4 other computers on the same network with the same other devices. The only issue is with the new computer so something definitely is as issue with it.
I did switch it to WiFi connection (Disconnected Ethernet cable, enabed WiFi, connected to my WiFi network), still the same issue. I rebooted, checked again, same. Checked network settings again, I can't seem to find what setting may be causing some IP devices to not be visible while others are.
DanInGA wrote:
Agreed.. All is good with 3-4 other computers on the same network with the same other devices. The only issue is with the new computer so something definitely is as issue with it.
Any chance that it is the usual "public network" issue in Windows?
Windows likes to protect us from new networks that might be evil. In reality, it often shuts us out of safe networks.
One thought is that you could tell Windows that you are on a "private network".
- Network and Internet settings
- Properties
- Private
This has worked for me and others in the same boat.
