Instead edit a regedit rule, you can edit a Local Group Policy. This only works on Windows 11 Pro
You can’t access this shared folder because your organization’s security policies block unauthenticated guest access
Hi Sir
i have two PCs:
PC-A: Windows 10 1909
PC-B: Windows 7 (have a shared folder)
everything working well when PC-A is Windows 10 1803, after upgrade to 1909,
i will get below error when accessing PC-B shared folder "You can’t access this shared folder because your organization’s security policies block unauthenticated guest access"
after search on google, get the common solution is enable "Insecure guest logons" in GPO.
https://support.microsoft.com/en-us/help/4046019/guest-access-in-smb2-disabled-by-default-in-windows-10-and-windows-ser
but i do not want to enable the insecure setting in GPO.
so the question is how can i config the PC-B that can meet the Win10-1909 security policy in order to allow me to access the PC-B shared folder?
Thanks,
Ray
Windows for business | Windows Client for IT Pros | Networking | Network connectivity and file sharing
Windows for business | Windows Client for IT Pros | Devices and deployment | Configure application groups
Windows for business | Windows Client for IT Pros | User experience | Other
13 answers
Sort by: Most helpful
-
-
Qamar Idrees 0 Reputation points
2024-05-24T08:31:04.2066667+00:00 This is happening in mostly the newer version of windows 11 and windows server 2019 and above for security reasons. Here is the solution if you want to bypass this Unauthenticated Guest Access
https://blog.itgranules.com/how-to-fix-the-unauthenticated-guest-access-issue-in-shared-folders
-
Chris 0 Reputation points
2024-02-20T16:49:23.2466667+00:00 I believe I was seeing this issue when I tried to access a network share folder. I had the correct logon credentials for the network share, but it didn't allow me to enter the credentials when I tried to access the network share folder. Confusingly, a different account on the same machine was able to provide credentials and open the shared folder.
What ended up working for me was adding the credential information to the Windows Credential vault for the network location of the share. By just adding the username, I was able to enter the credentials when I attempted to open the shared folder. Adding the credential to the vault appears to satisfy the network logon requirement for non-guest access.