#Qfinder cant find nas install
#Qfinder cant find nas update
#Qfinder cant find nas windows 10
#Qfinder cant find nas software

#Qfinder cant find nas windows 10

I have installed Qfinder Pro on Windows 10 and it says it can't find a device.

#Qfinder cant find nas software

I searched for the software and what I ended up with was not a Windows program.

#Qfinder cant find nas install

The web view said I had to install some software but there was no link. I waited over 24 hours for the device lights to stop flashing then tried everything again and still no connection. I went to the cloud setup and I thought I logged into everything and set things up but I can't connect to my device. I have installed the 2x WD Red drives that were supplied in my package.

#Qfinder cant find nas update

Update March 28, 2023: Added a clarification that the Group Policy Editor (gpedit.msc) is only available on certain editions of Windows and changed the title accordingly.I feel ashamed to have to ask for help but I have been banging my head against a brick wall trying to get my new NAS working. Update February 15, 2023: A previous version of this article mentioned making changes to the registry, however the screenshot showed the Local Group Policy Editor (gpedit.msc) and not the registry editor (regedit.exe). As this resulted only in a single failed access attempt, the PC’s IP address was not banned.įor further support, please visit the QNAP forum 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: However, you can use a tool called ‘Policy Plus’ to add it to the home edition. 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.

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.