Why did this work? Apparently, Windows only tried to use the current user credentials once when connecting to the NAS and then used guest access. Clicking on a protected folder brought up the Enter network credentials dialog: Now (and after the IP ban period has expired, of course) it was possible to access the NAS through the file explorer. On other PCs running Windows 10, the described behavior was correct and the entire problem never appeared. Note: The description says that “if you do not configure this policy setting, the SMB client will allow insecure guest logons.” This was not true for me on Windows 11 21H2, the setting had to be explicitly enabled. In the Local Group Policy Editor, the setting can be found under Local Computer Policy -> Computer Configuration -> Administrative Templates ->Network -> Lanman Workstation -> Enable insecure guest logons: To start the Local Group Policy Editor, press your Windows key and start typing “group policy” (then select “Edit group policy”):Īlternatively, you can also press the Windows key and R, then type “gpedit.msc” and click on OK: It is primarily included in the Professional, Enterprise, and Education editions of these operating systems. Note: The Group Policy Editor (gpedit.msc) is not available in all versions of Windows 10 and Windows 11. This allows the PC to connect to SAMBA shares which are not protected by a password (such as the Public folder on a QNAP NAS). In the local group policy settings of my Windows PC, I enabled insecure guest logons for the SMB client. I tried a different solution which I found here.
0 Comments
Leave a Reply. |