

In most cases, you can face this problem when accessing old NAS devices (usually guest access is enabled on them for ease of setup) or when opening shared folders on legacy Windows 7/2008 R2/Windows XP/2003 devices with anonymous (guest) access enabled (see the table of supported SMB protocol versions in different Windows editions).

This error says that your computer (client) blocks non-authenticated access under the Guest account.

If you try to open a shared network folder using the SMB v2 protocol under the guest account, the following error will appear in the Event Viewer of your computer (SMB client): Log Name: Microsoft-Windows-SmbClient/Security
LOCAL NETWORK FILE SHARING WINDOWS 8 WINDOWS 10
These changes are not applied on Windows 10 Home editions and the network access under the guest account is working fine. When accessing a network folder under a guest account over the SMBv1/v2 protocol, such methods of traffic protection as SMB signing and encryption are not used, which makes your session vulnerable to the MiTM (man-in-the-middle) attacks. Guest (anonymous) means access to a shared network folder without authentication. The point is that in modern versions of Windows 10 (build 1709+), the guest access to the shared folders using the SMBv2 protocol is disabled by default. Moreover, on other computers with Windows 8.1, Windows 7, or Windows 10 with a build of up to 1709, the same shared network folders open normally. These policies help protect your PC from unsafe or malicious devices on the network. Microsoft Windows Network: You can’t access this shared folder because your organization’s security policies block unauthenticated guest access.
LOCAL NETWORK FILE SHARING WINDOWS 8 UPDATE
Starting with Windows 10 build 1709 Fall Creators Update (Enterprise and Education editions), users began to complain that when they tried to open a network shared folder on a neighboring computer, an error appeared: Restoring Network ConnectionsĪn error occurs when you try to open a network folder:Īn error occurred while reconnecting Y: to Other Fixes: Windows Cannot Access Shared FoldersĬan’t Access Shared Folder Because Security Policies Block Unauthenticated Guest Access.Windows Cannot Access Shared Folder: You Don’t Have Permissions.Can’t Connect to the File Share Because It’s Not Secure and Requires the Obsolete SMB1 Protocol.Can’t Access Shared Folder Because Security Policies Block Unauthenticated Guest Access.
