So I have 3 computers on my home network. 2 almost identical mini computers and a laptop. I recently decided to start using file sharing but ran into a strange problem. I set up a shared folder on each. Read/write access was given to "everyone" on each folder. All 3 have Network discovery, file and print sharing, and public folder sharing turned on. All 3 have "set up network connected devices automatically" checked, and password protected sharing turned off. Mini1 can access the shared folder on Mini2 and the laptop, no issues. The laptop can access the folders on Mini1 and Mini2, no issues. Mini2, however, gets a Network Error window saying it cannot access either mini1 or the laptop when I click on their links. If I type in the location of the folders (ie: //LAPTOP/folder) it will bring up a windows security window asking for credentials to connect, but none of the passwords I try are working and it says "You can't access this shared folder because your organization's security policies block unauthenticated guest access" I have tried all the credentials I can, and still no luck. Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. Anonymous 2025-01-30T08:19:19+00:00 Hi to, I'm Sumit, here to answer your query at the Microsoft Community. Apologies for any inconvenience you are experiencing. I am happy to help you today. Some changes were made in Windows 11 24H2 for network drives which is causing this. https://www.yourwindowsguide.com/2025/01/mapped... Open the Windows search bar and type “powershell” Right-click on PowerShell and select “Run as administrator” Execute the following commands: Set-SmbClientConfiguration -RequireSecuritySignature $false Set-SmbClientConfiguration -EnableInsecureGuestLogons $true These commands will disable the requirement for security signatures and enable insecure guest logons, which should resolve issues with accessing mapped drives. Hope that helps, and rely on us for any further inquiries. All the best. A Windows MVP writes content on the above website, so it is safe. However, do watch out for the ads. It should translate into your Browser language automatically. 0 comments No comments I'm Sumit, here to answer your query at the Microsoft Community. Apologies for any inconvenience you are experiencing. I am happy to help you today. Some changes were made in Windows 11 24H2 for network drives which is causing this. https://www.yourwindowsguide.com/2025/01/mapped... Open the Windows search bar and type “powershell” Right-click on PowerShell and select “Run as administrator” Execute the following commands: Set-SmbClientConfiguration -RequireSecuritySignature $false

Set-SmbClientConfiguration -EnableInsecureGuestLogons $true These commands will disable the requirement for security signatures and enable insecure guest logons, which should resolve issues with accessing mapped drives. Hope that helps, and rely on us for any further inquiries. All the best. A Windows MVP writes content on the above website, so it is safe. However, do watch out for the ads. It should translate into your Browser language automatically. Anonymous 2025-02-01T02:55:53+00:00 Thank you. The requiresecurity parameter does not need a space after "-" which is the root cause why command does not work. Notice the star. Set-SmbClientConfiguration -*RequireSecuritySignature $false 0 comments No comments The requiresecurity parameter does not need a space after "-" which is the root cause why command does not work. Notice the star. Set-SmbClientConfiguration -*RequireSecuritySignature $false Anonymous 2025-01-31T21:00:59+00:00 This is what I got. 0 comments No comments This is what I got. Anonymous 2025-02-01T06:25:13+00:00 Thanks for that. I thought I tried it, but will try again tomorrow. I am using this forum from my phone, so the misunderstanding came from your original post looking like this: 0 comments No comments Thanks for that. I thought I tried it, but will try again tomorrow. I am using this forum from my phone, so the misunderstanding came from your original post looking like this: Anonymous 2025-01-31T13:14:47+00:00 This didn't exactly work, but led me to what did. I have no idea what I was doing wrong, but Powershell with admin cred would not accept my commands. I got an error every time I tried. It said that "-" wasn't recognized. I tried all sorts of approaches with the command (dashes with spaces, dashes without spaces, just spaces, commas etc) and it would not work. I could type set-smbclientconfiguration and it recognized that, saying I needed to specify what I wanted, but as soon as I tried adding the rest, it didn't work. I had no trouble using get-smbclientconfiguration to see all the values. Luckily, the requiresecuritysignature was already off and I ran the gpedit.msc to turn the insecure guest login on. Would love to know what I was doing wrong in powershell though. Thanks 0 comments No comments This didn't exactly work, but led me to what did. I have no idea what I was doing wrong, but Powershell with admin cred would not accept my commands. I got an error every time I tried. It said that "-" wasn't recognized. I tried all sorts of approaches with the command (dashes with spaces, dashes without spaces, just spaces, commas etc) and it would not work. I could type set-smbclientconfiguration and it recognized that, saying I needed to specify what I wanted, but as soon as I tried adding the rest, it didn't work. I had no trouble using get-smbclientconfiguration to see all the values. Luckily, the requiresecuritysignature was already off and I ran the gpedit.msc to turn the insecure guest login on. Would love to know what I was doing wrong in powershell though.