You can’t access this shared folder because your organization’s security policies block unauthenticated guest access

Question

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

Answer 1

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.

Answer 2

1- Run and write GPEdit Enter

2- follow the graph

Answer 3

I just had this same problem and struggled to get it resolved. Trying the phone number as a user name did not work for me unfortunately. What I ended up using was GUEST as the user name and left the password blank, finally worked. Why on earth I couldn't access with the computer's microsoft credentials is beyond me.

Answer 4

The registry hack didn't work for me. My company is on an Azure network and the group policies don't work with the local system. I had to support and fix this in two ways. I have multiple users not on the Azure network that need to access it via SMB1 (guest access) and those on the Azure network to use a username and password. The difficulty in figuring this out is the Linux Samba share would first attempt to log the user in with the Windows username (which doesn't have samba access) and fails over to guest since the linux [global] is set to map to guest = Bad User but allows guest access to certain folders. I needed to create a user on the linux machine and give it samba access. Then on the windows machine, I needed to open the Credential Manager and add a new credential. Add the server's name, the new username you created on the linux machine and the samba password. The windows machine will use this credential instead of the windows username and it gave me access.

The best answer is to map to guest = Never and make all the users use the samba user name and password, but they will all eventually move to the Azure network and this way I can support them via a slow support set versus trying to support 100+ users all at once.

Answer 5

The reg hack and enabling SMB1 let me access a shared drive on a Raspberry Pi again, which stopped working after a power outage yesterday. I'm on 20H2. Thanks, everyone!!