NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Unable to access NAS via WIN11 File Manager
My ReadyNAS 214 (Firmware Ver.6.1010) is no longer available using Windows11 File Explorer. The error message is "\\WOODSIDE is not accessible. You might not have permission to use this network re...
No rocket science, and answered at least a dozen times here and elsewhere: Open your "Turn on and Off Windows Features" (most simple by typing "Windows Features" t0 the search field, or head to the Control Panel and locate it), and Enable both the "SMB 1.0/CIFS Client" and the "SMB 1.0/CIFS Server", click OK, and reboot once required.
This will add the CIFS NetBIOS name resolution requires the SMB 1.0 transport protocol feature installed.
Regards,
-Kurt.
schumaku wrote:
No rocket science, and answered at least a dozen times here and elsewhere: Open your "Turn on and Off Windows Features" (most simple by typing "Windows Features" t0 the search field, or head to the Control Panel and locate it), and Enable both the "SMB 1.0/CIFS Client" and the "SMB 1.0/CIFS Server", click OK, and reboot once required.
OS-6 NAS (RN214) do not require SMB 1.0
StephenB wrote:
schumaku wrote:
No rocket science, and answered at least a dozen times here and elsewhere: Open your "Turn on and Off Windows Features" (most simple by typing "Windows Features" t0 the search field, or head to the Control Panel and locate it), and Enable both the "SMB 1.0/CIFS Client" and the "SMB 1.0/CIFS Server", click OK, and reboot once required.
OS-6 NAS (RN214) do not require SMB 1.0
Wrong. The point is -not- the SMB 1.0 transport, the missing feature is the NetBIOS CIFS name resolution. That's why the \\[NAS-IP-address]\ does likely list the shared folder, but not \\[NAS-name]\ ... figure. No idea why you are ALWAYS coming up stating the same wrong feedback...
schumaku wrote:
The point is -not- the SMB 1.0 transport, the missing feature is the NetBIOS CIFS name resolution. That's why the \\[NAS-IP-address]\ does likely list the shared folder, but not \\[NAS-name]\ ... figure.If you'd said "Although you don't need SMB 1.0, this will enable NetBIOS CIFS name resolution on the PC", I wouldn't have said what I did. But you didn't say that.
Your wording suggests that you are not certain your suggestion will work - is that the case? FWIW, I've seen this issue on some PCs that do have SMB 1 enabled, but I haven't looked for that lately. When I have a chance I will disable SMB 1 on a PC and see if that results in a name resolution failure.
Well, let's start here: In no way, my responsibility is to argue for on behalf Microsoft or Netgear.
The point that the SMB 1.,0 "feature" does also install an addental name resolution protocol, and list it in a logical sequence. Please don't argue about language - these days, I'm more communicating in Chiunglish than in my native Swiss German, German, Swiss French, than in English. In brief, this is what Microsoft has published a long time ago:
===
Host name resolution generally uses the following sequence The client checks to see if the name queried is its own:
- The client then searches a local Hosts file, a list of IP address and names stored on the local computer.
- Domain Name System (DNS) servers are queried.
- If the name is still not resolved, NetBIOS name resolution sequence is used as a backup.
This order can be changed by configuring the NetBIOS node type of the client. Not that I would suggest, however, it's possible,
===
Sure, you could figure out if uninstalling the two feature. I -guess- NetBIOS name resolution (the client and the resolver) would be removed, too.
In order for enabling SMB1 (and, thus, NetBIOS name resolution) to help, you must also enable "Legacy Windows Discovery" in the SMB settings. I don't recall whether or not that's the default. But you also need to have a device that assumes the roll of NetBIOS Master Browser. I have no idea whether versions of Windows after Win7 or the ReadyNAS can assume that roll. But if schumaku has seen this as a solution, then I guess one of them can.
OS6 does support current network discovery modes, but I have seen it fail for reasons I have been unable to identify. And I have seen similar issues on other forums related to other Linux implementations, so it's not just a ReadyNAS issue.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
