NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
SMB1 solution?
Hi guys, I'm assuming my RN312 unit (bought in 2017) is using SMB1 but how do I know? I was doing a fresh wipe of my readnas system at the same time as upgrading from Windows 7 to Windows 10. I co...
Blanker-2 wrote:
..., I created a user in the nas with the same name as my windows profile and the same password as my user on the nas (I just use admin on the nas).
1. Every time I want one of my computers in my home to access the nas will I have to create another user on the nas with the same name as the profile of that windows user? What about cell phones, my dune, etc? This sounds pretty undesirable.
A user is to identify the user - not a specific system. Ideally, users are combined into groups with similar/same access rights. And the shared folder access is based on groups, not individual users.
An exception might be Dune or other media players potentially using DLNA/UPnP AV - in DLNA, there is no user access right design, so watch your steps.
Blanker-2 wrote:
This worked but I also see the volume shares and other folders - no big deal. I'm assuming that my nas is using SMB1? So what are my options here?
3. I saw the SMB plus app on my readynas, would this help?
ReadyNAS OS 6 and most consumer NAS have the share enumeration wide open, this will allow to browse the shared folders by using a non-authenticated connection. The competition has introduced controls to the readily available SAMBA "access based share enum" with recent updates.
Blanker-2 wrote:
2. I understand this is a Windows thing but is Netgear providing any solutions?
Amazingly (not so...), Netgear promoting ReadyNAS more for the business environment is always behind - my requests to add these controls to OS 6 were ignored - there it went your business, Netgear.
The SMB plus app has controls for the SAMBA "hide unreadable" and "hide unwriteable" affecting (sub-)folders and files only, so it's only a part of what you are behind.
Edit: All this is independent of the SMB 1.0, 2.0, 2.1, or 3.0 protocol level used to access the NAS.
Thanks for the help. I'm not sure I understand all of what you are saying. I need a crash course on user controls. I use my 312 in a home environment, mainly to stream movies to my dunes throughout the house via smb, not dlna. I also take advantage of btrfs self healing for my repository of personal files that I share on the network.
If you are accessing the NAS by name, try switching to IP address. I had to do that after the latest Windows 10 update.
Sandshark wrote:
If you are accessing the NAS by name, try switching to IP address. I had to do that after the latest Windows 10 update.
ReadyNAS OS 6.9.4 (current) and a few builds before already introduced the WS-Discovery, and have disabled NetBIOS discovery name resolution by default.
Permitting the Windows 10 system is configured into a trusted private network (not a public network), all the systems are configured to the correct IP subnet, and there is no borked network device blocking Multicast, the ReadyNAS will show up in Windows Explorer, and the name is resolveable, too. Open Windows Explorer, and make the Discovery Method visible, you will see the WSD devices:
No tricks, no rocket science.
If you have legacy NAS systems (e.g. old RAIDiator systems), you must open the Windows Features and enable both the CIFS/SMB 1.0 Client and CIFS/SMB 1.0 Server (to bring back the NetBIOS name resolution and discovery).If this answer was intended for me, please use the correct thread (Using-your-ReadyNAS/Access-issues-after-upgrade-to-Win10-V1803 instead of hijackng the other user's thread for something that may not apply.
Not the solution, BTW. Still looking for one.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
