I believe all Windows 10 versions come with SMB v3, and is automatically preferred over SMB 2 (if the host supports it).
But 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'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. Both return the same "eh? nothing exists by that name" types of errors. 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). Have you upgraded any of your clients, in other words, are they running a recent version of SMB? (same goes for the NAS) Future visitors from Google-verse, jump to this post to see what I had to run in SSH.
UPDATE: Seems that replacing the old SMB config files with the system default (i.e. The rest return errors that basically says "the network device doesn't exist".
The devices that are able to connect via SMB: the Macbook when using AFP only, both Android devices and 1 Windows 10 box. A couple of Android devices (running Android 9 and Android 11). 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. Happy to provide more info once I know what to provide. I'm not really sure what info is needed to troubleshoot this further. It seems that these problematic clients just can't see the NAS over SMB. I don't think it's a credentials issue, because I'm able to change the credentials on the working clients just fine. I'm looking for help to troubleshoot SMB issues both in Windows and on QTS. The NAS in question is QNAP running the latest QTS version 4.5.3. I know it's a SMB issue because macOS can connect just fine via AFP:// but fails with smb://. Three devices still have access, others don't.Īs device doesn't exist, even though it can see the device on the network. Not sure how or why, but I've suddenly lost the ability to connect to the NAS via SMBon some client machines.