MattMatt wrote:
What I can tell you all, confirmed just now, is that hitting 'pause' on the app for my desktop cause the "This Device Is Blocked..." from the R8000. But a simple click brought up the shared directories on my Windows Server.

I suspect the Pause / Device block does deny _new_ sessions on some implementations?

For https Web pages, you get the "This device is Blocked..." message, too?

MattMatt wrote:
I don't have Wireless Client Separation enabled (I seem to remember that setting on a router, but at the moment I can't put my hands on that setting), not that it would matter as both my desktop and the server are on a wired connection.

No such control for the "primary" wireless, available only on the Guest networks for the Nighthawk Routers.

MattMatt wrote:
So, don't know what to tell you. Pause doesn't block someone from the local network. Not on my LAN anyway.

I remember, you had some questions about reading between the lines. It looks to me like established sessions (at least to the LAN) might remain available - so when you worked with your desktop before, the sessions are established, the Windows server name might be cached anyway, so that's why you can continue accessing the Windows Server even after Pause is selected.

When doing the similar test here on the R9000 on the primary WLAN - which does clearly state it does block any network connection - even established sessions to the NAS are stopped, no ping to any, ... as expected.

Now the curiosity came up and we connected a (Windows 10) test system direct to a router LAN port. And it behaved the same like the wireless above.

Needless to say, when using a port on the attached switch (an S8000/GS808E) here, the LAN connectivity to the switch ports can't be prohibited, except of the data flowing to the router switch port of course ... which behaves blocking as expected again.

At this point the bigger problem - even after resuming (allow network access again) the DNS caching does still bring us to the "This device is blocked" (for http, port 80) resp, a "dead end" (for https, port 443). So either flushing DNS cache or reboot is the way to re-establish connectivity and full usability.

Forum Discussion

Netgear Genie app does not open