NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Cannot login to share when it's protected by password
Hi,
I read a few topics related with this issue, but I failed. I have shares on my NAS, that I would like to have private and protected with password. I created shares and users in “Security”, ...
Retired_Member wrote:
StephenB wrote "Your NAS requires the use of SMB 1, which Microsoft is deprecating"
Hi StephenB, from several posts I learned, that you recommended to overcome various problems related to Radiator firmware by upgrading it to OS6. Please correct me, but would that not also be a valid option in Ayahuasca's case?
He has a duo v2, so converting to OS-6 not an option for him. It would be if he had an Ultra or a Pro.
Thank you for your replies,
Yes, I have the last firmware available and cannot upgrade it. I was thinking about this samba, because windows 10 doesn't support v1 and yes I had to added it, and I tried to uninstall and install this again as you said, but it doesn't work still, and I see it's worse even because I cannot do anything with data which is on one previously protected share. I cannot rename folders, delete etc. as it requires some "Unix permissions" so it seems there is a problem with file attributes so I think there is no point to use this NAS more.
I don't understand Netgear policy, cannot they at least update samba protocol in this device ? it would work still fine. I know they don't want, because it's better for them if someone buy new device, for what update the old one. But for example old D-link DNS-320L has samba v1 too, and there is alternative firmware with samba v3, or even addon with samba v3 update, and for this netgear what is ? nothing. I won't buy any netgear device again, without support and updates buying such electronic equipment is not long term investment.
Thank you for your help.
Well, Ayahuasca, I did not try, but you could run a virtual Windows8 machine on your Windows10 workstation to do the necessary. Just an idea. Depends a bit on how intensively you need to use this nas.
Kind regards
Ayahuasca wrote:
..., because windows 10 doesn't support v1 ...
Simply wrong. Microsoft does continue to support SMB 1.0 (and the related NetBIOS name resolution) for a while as it is still required for legacy devices like your NAS. As SMB 1.0/CIFS (and NEtBIOS) is legacy, and Microsoft does not need it, they made it an optional component. Head to your Windows 10 Features, scroll down to the SMB 1.0/CIFS and tick both the Client and Server component.
You blame Netgear for something Microsoft has changed in their Windows 10 release cycle specs and builds. And again for the records - the bigger problem for many users is the device discovery (so it appears in the Explorer Network Environment) and that it can be clicked as \\NASname - and this is NetBIOS (a feature part of the SMB 1.0/CIFS Server feature).
Last, before we hear a lecture on security: The SMB 1.0/CIFS security vulnerabilities are fixed for a longer time in the SAMBA packages. I have no idea of Netgear has updated SAMBA on the legacy devices. Microsoft has done their home work for sure. Of course the legacy SMB 1.0 does not support enhanced features like protocol encryption, flexible windowing (essential for well performing VPN access as well as for performing LAN access - permitting the infrastructure does support Jumbo Frames), or protocol signing.
schumaku wrote:
Last, before we hear a lecture on security: The SMB 1.0/CIFS security vulnerabilities are fixed for a longer time in the SAMBA packages. I have no idea of Netgear has updated SAMBA on the legacy devices.Netgear back-ported the fixes for Samba CVE-2017-7494 in the final firmware release (5.3.13, May 2017), and back-ported the fixes for SAMBA CVE-2012-6150, CVE-2013-4496, CVE-2014-3493, and CVE-2015-0240 in 5.3.12.
Ayahuasca, if enabling SMB 1 in the PC still isn't solving the problem, then try this test. Open CMD, and then enter
net use * /delete
net use t: \\nas-ip-address\sharename /user:username userpassword
using the real nas ip address, a real NAS username/password and a sharename that is giving you trouble.
Be careful on the slash direction and the spaces.
The first command terminates any open SMB sessions - please let it proceed if it prompts you. It will give you a status message if there are no open sessions.
The second command attempts to mount the share as drive letter t.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
