NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RonV42
Dec 19, 2016Luminary
Access control page always shows one deviced blocked
On my access control page in the router one device always shows Blocked even though it's not blocked. I never set it to be blocked. If I remove the device the next one on the list shows blocked. I am on firmware 1.4.0.18 and this was happening on 1.4.0.16 also. I verified that the device isn't blocked so this is a cosmetic issue but needs to be fixed. See image below:
27 Replies
- jcavianiInitiate
I have the same issue with multiple devices. Trying to change them to allowed does not work.
- Dan_HApprentice
I have a device on my network (my wife's S7Edge specifically) that is having some issues when on the satellite.
- I cant rename it, it always shows up as "S7Edge<"
- It shows up as blocked
- The mac address shows up as /OrbiDevName1>
- It says it is connected "Wired"
What the heck!
However, when it is on the router and not on the satellite, then it is fine:
- RJG69Guide
Hey guys....I'm having the same issue with the blocked device...it's always my Samsung Galaxy S5....shows BLOCKED (but it ain't)....won't let me edit any information....doesn't show the MAC address.....and all this started immediately after I upgraded the firmware to 1.4.0.18.....any suggestion?
- VediusInitiate
I have the same issue as well as the issue of being unable to rename the device.
They are wired devices connected via the satellite.
It also shows my Sonos wireless speaker as being wired!?
Lots of issues with the access controls list. I am not even sure why they incorporated support for the blocking of wired devices. I would think that physical security would mean that they could just simplify the access control to wireless. I would like to see them broken out if possible. ie Allow all new wired. Deny all new wireless.
I was very reliant on mac access control with my linksys. With the new Orbi I would hope I could at least do what I was doing on my 5+ year old linksys
- RJG69Guide
Knock on wood.....but for the last 2 days, this anomoly seems to have been corrected....my phone no longer shows BLOCKED..it no longer shows as a WIRED device and it's mac address displays correctly.....I have made no setting changes to either my wifi system or my device....if anyone knows of something that was changed on Netgear's end, please let me know what it was, just for conversation sake if nothing else.
- RJG69Guide
Ok...out of curiosity, I have now determined that the weird BLOCKED anomoly with my phone only happens when it is connected to one of my satellites....It shows that it is BLOCKED, WIRED, and the mac address is only an "S"...ONLY when it is attached to a satellite....everything is perfect when it is connected directly to the router...so, sorry if this is of no help to anyone, but I'm just putting it out there.
- John01Initiate
I have the same problem. I have my solar plugged into the satilite and it shows it is blocked. Everything eles is allowed. I also tried to change the block to allow and it would not change.
same here...my apple tv is showing as blocked with a ridicoulous mac address.
we'd like to see a fix perhaps?
- DarrenMSr. NETGEAR Moderator
Hello aellul
Are you on the latest firmware of 1.4.0.34 this was fixed in this update.
DarrenM
- jcavianiInitiate
DarrenM,
I am on firmware 1.4.0.34 and no, it is not fixed
My Sony televison has a mac address of "/OrbiDevName1\>".
Also, the selection for QoS is not available. You have something wrong in one
of your HTML extensions
- tmv434Guide
I am on V1.4.0.34 and I have this problem too, with one device showing as Blocked. In the Attached Devices page, the Device Name for the blocked device shows up as 'Wemo-Switch<' and the MAC Address is '/OrbiDevName3>'. The Connection Type shows as Wired even though it is actually Wireless. When I click on the Device to edit it, in the Edit Device page, the Device name shows up as 'WeMo-Switch<' and the MAC Address is still '/OrbiDevName3>'.
The problem will go away for a bit if the router is rebooted. I have the Orbi with 2 satellites. What I observed immediately after a reboot is that my device that was previously blocked will get connected to Satellite #1. I can see this device when I go to the URL for this satellite, in my case, http://192.168.1.2/status.htm, then click on Connected Devices. At this point, the device is working fine and is not showing Blocked in Attached Devices. I can also go to the url for my Satellite #2 which is http://192.168.1.3/status.htm and I am able to view the Connected Devices there as well. However, several minutes later, this same device is showing as Blocked. Because this device is actually just a few feet away from Satellite #2, I think Orbi attempted to move it from Satellite #1 to Satellite #2, and that is when the error occurred... Because when I go check the Connected Devices for Satellite #1, the device no longer shows there. When I go check the Connected Devices for Satellite #2, that web page is now hung!! If this is an indication that I can no longer connect to this satellite, then this is a VERY critical bug.
- RJG69Guide
I've seen the anomoly you speak of with the page being all jacked up, but it resolves itself if you log out and back into your netgear account......I have moved my phone (Samsung Galxy S5) around the house from the router to each individual satellite, and checked it's staus as I moved it....without fail, it will always appear normal when under the router's domain, but it always appears as the blocked version when connecting through either of the 2 satellites. It is never actually blocked, so I've forced myself to stop fretting about it, until another firmware version becomes available. I somehow think this has something to do with the order in which a firmware update occurs...I cannot remember exactly what I read, but it was something along the lines of updating the satellites first or updating the router first...either way, I think that when I do a firmware update automatically, it does this process in the wrong order for everything to be ok...If I still have this issue after the next firmware update, I'm going to do a factory reset to see if it disappears afterwards.
- fortunate4everInitiateA have same issue. I'm using latest fw.