NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

mc64's avatar
mc64
Tutor
Oct 22, 2018

Access Control Bug in Orbi V2.2.1.210

Until the last firmware upgrade, access control worked fine. I had "prevent new devices from connecting" enabled as well. When I recently installed a new device and went to allow it to connect as I'v...
Features
marquisT's avatar
marquisT
Aspirant
Feb 01, 2019
I assume the PC, not the Orbi, since that is the new component in the mix. According to the Device Manager, it an Intel Ethernet Connection I217-LM. There are about 20 properties that can be set (Device Manager | Network adapters | Intel Ethernet Connection I217-LM| Properties|Advanced). Any thoughts about any of those parameters that might avoid this supposed conflict? Thanks.
FURRYe38's avatar
FURRYe38
Guru - Experienced User
Feb 01, 2019

You might contact Intel support and see if there is any specific settings in the adapters properties that could elliviate this issue.

 

You might file a support ticked as well with NG and have someone review it:

https://www.netgear.com/mynetgear/registration/login.aspx

 

I would also ask NG for a beta to see if it may have been fixed:

https://community.netgear.com/t5/Orbi/Looking-for-a-select-group-of-Orbi-Community-members-that-are/td-p/1624103/jump-to/first-unread-message

 

marquisT wrote:
I assume the PC, not the Orbi, since that is the new component in the mix. According to the Device Manager, it an Intel Ethernet Connection I217-LM. There are about 20 properties that can be set (Device Manager | Network adapters | Intel Ethernet Connection I217-LM| Properties|Advanced). Any thoughts about any of those parameters that might avoid this supposed conflict? Thanks.