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. This registry setting can be found under Local Computer Policy -> Computer Configuration -> Administrative Templates ->Network -> Lanman Workstation -> Enable insecure guest logons:
Qfinder cannot map drive password#
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 registry of my Windows PC, I enabled insecure guest logons for the SMB client. I tried a different solution which I found here. Disabling all guest shares on the NAS to force Windows to show the network credentials dialog.Disabling Network Access Protection on the NAS.Creating a user account on the NAS with the same user name and password as on Windows.There are many threads about this issue on the QNAP forum proposing various solutions, such as: You can see the failed login attempts in the System Connection Logs (if enabled for SAMBA): Solutions If this fails too many times and Network Access Protection on your NAS is enabled, your PC’s IP address will be banned:
The reason: Windows will first try to connect to your NAS using your Windows login credentials. The NAS is still accessible from other PCs on the same network. The problem: You cannot access the SAMBA (SMB) shares on your QNAP NAS from the Windows File Explorer and after you tried, access to the web interface also stopped working.
0 kommentar(er)
