Qnap qfinder cannot find nas how to#
Qnap qfinder cannot find nas update#
Qnap qfinder cannot find nas windows 10#

I guess client devices are all Windows 10 machines (all running 20H2), a Macbook Pro (Catalina), a Raspberry Pi, and an Ubuntu 20.04 box. A couple of Android devices (running Android 9 and Android 11). The devices that are able to connect via SMB: the Macbook when using AFP only, both Android devices and 1 Windows 10 box.

Qnap qfinder cannot find nas update#

#Qfinder cannot find nas after update android The rest return errors that basically says 'the network device doesn't exist'. UPDATE: Seems that replacing the old SMB config files with the system default (i.e. Have you upgraded any of your clients, in other words, are they running a recent version of SMB? (same goes for the NAS)įuture visitors from Google-verse, jump to this post to see what I had to run in SSH. So for example, in Windows (10) I've tried using the 'Run' and then \192.168.1.x as well as Īs (yes, I've named it 'nas' to keep things simple). Both return the same 'eh? nothing exists by that name' types of errors. I've also gone to Windows Explorer, 'Network', and then double-clicked on the 'NAS' object that shows up there, so clearly Windows can see that it exists, but it just doesn't want to communicate with it (via SMB, I'm presuming).Īll my Windows machines are Windows 10 20H2, though some might be one minor build older than others. #Qfinder cannot find nas after update updateīut they are all as up-to-date builds as say April 2021 and newer - I just let Windows update itself, so whatever schedule each machine is on is its own thing. I believe all Windows 10 versions come with SMB v3, and is automatically preferred over SMB 2 (if the host supports it). #Qfinder cannot find nas after update windows 10 So I don't think anything has been upgraded? That is, I don't think the SMB versions have been upgraded since they come built into the OS (Windows and QNAP OS) and aren't likely to be updated frequently.įor the NAS host itself, it is running SMB v2, v2.1, and v3. There is the option to support SMB v1, but I've disabled that since I figured it's not bundled with Windows and therefore isn't needed since almost any modern OS supports SMB v2 and above. That said, Yes, I have tested to see if using SMBv1 would work, but it didn't make a difference. It's very possible to run DNS through the NAS too so it might be good to have that setup and tell the router to give out the NAS as a/the DNS server for the network. I use pfSense because then I can use NAT reflection to access my local servers by going somewhere like Any new device on my network can automagically be accessed with its hostname as the subdomain, without having to mess with a zone file manually. You can probably do this with any DNS server and configuring your router right, but this is a piece of cake to do graphically with pfSense.

Qnap qfinder cannot find nas how to#

I need to learn how to do Split DNS, though, and use that instead.īut most home users have their router as the DNS servers, so that would be my second suggestion to the OP, if DNS is the issue, after trying the IP address directly. #Qfinder cannot find nas after update android.#Qfinder cannot find nas after update windows 10.#Qfinder cannot find nas after update update.#Qfinder cannot find nas after update how to.