![]() This morning's situation seems worse, though. the NAS shows in QFinder Pro, but attempting to connect from there yields the dreaded "Cannot connect to device" error. I'm also unable to ping the IP that QFinder Pro displays, getting "General failure." I've manually configured my IP settings as detailed by. If somebody could suggest a way out of this I'd be immensely grateful! Let me know if you need any more details. Update: You could have predicted I'd find the issue as soon as I posted this: it helps to disconnect from the VPN I use before attempting the direct connection. I'm now able to log in to the NAS, and re-entering my WiFi connection details resolved the problem. Sorry to waste your time, hopefully this is useful to somebody else.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. The NAS is still accessible from other PCs on the same network. 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. I tried a different solution which I found here. ![]() In the local group policy settings of my Windows PC, I enabled insecure guest logons for the SMB client. 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). Note: The Group Policy Editor (gpedit.msc) is not available in all versions of Windows 10 and Windows 11. 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 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. ![]() On other PCs running Windows 10, the described behavior was correct and the entire problem never appeared. 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.Ĭlicking 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. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |