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

Hi ，

>>can i upgrade the PC-B to Windows 10 1909, will it resolve the insecure issue?

No.

In your case, the main reason is because Guest account access to a remote server is disabled in windows 10 1709 and later version.

If you are using guest account on windows 10 and cannot enable insecure Guest logons by registry or GPO, then whatever PC-B's OS version is windows 10 or not, you still cannot resolve the insecure issue.

As you can see from the following article :

https://support.microsoft.com/en-us/help/4046019/guest-access-in-smb2-disabled-by-default-in-windows-10-and-windows-ser

---Please Accept as answer if the reply is helpful---

Best Regards,

Candy

@Anonymous

The issue resolved after turn on "Password protected sharing" in PC A network sharing center.

also thanks for your answers for Win10 side.

Best Regards,
Ray

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!!

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.

1- Run and write GPEdit Enter

2- follow the graph