NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
File sharing - WINDOWS 10 - ReadyNAS no longer connecting
Cannot see/access/satisfy-password on ReadyNAS NV+ and ReadyNAS 516 on Windows 10 home -- after the Windows update last week. Now: Windows 10 home, Version 1511, OS Build 10586.11 I simply ...
For OS6 models we'd recommend running 6.5.2 or later. 6.5.0 and later has the new WSD discovery service.
With Windows 10 you also want the workgroup on the NAS to match the one on your PC.
What firmware are you running? Are you using share security mode or user security mode?
Are you using the microsoft login, or a local user login on the laptop?
If you are running user security mode, then try entering cmd in the bottom search bar, and enter
net use * /delete
net use t: \\nasipaddress\C /user:admin password
nasipaddress is the ip address of the nas (name likely works too)
password is the NAS admin password
That should mount the NAS data volume as drive letter T.
If you are using share security mode, you probably need to switch to user security mode. There is some guidance here: http://readynas.sphardy.com/2010/09/how-to-migrate-to-user-security-mode_4917.html
Other things you can try.
In Win10 10240 I had to do the following:
1) There is a setting in windows Local Security Policy which is incorrectly set by default for viewing an older communication protocol NAS.
To access said setting go to the control panel in Windows 7, in Category view click on the text "System and Security", then click on the text "Administrative Tools".
Now double click and open "Local Security Policy".
In the Local Security Policy screen on the left navigation tree, expand the "Local Policies --> Security Options" then about 2/3rd's the way down the list you'll see a Policy called "Network Security: LAN Manager authentication level". Double click and change the setting to be "Send LM & NTLM - use NTLMv2 session security if negotiated."
Then just press OK and close all of the open windows and then try again
2) Run regedit. Locate HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/Windows/CurrentVersion/Policies/System. Create a new DWORD entry with the name EnableLinkedConnections and value 1. Restart your computer.
On 10586 in addition I had to run from an admin cmd window:
sc.exe config lanmanworkstation depend= bowser/mrxsmb10/nsi
sc.exe config mrxsmb20 start= disabledand reboot.
Forgot - also needed the following for 10586:
Administrative Tools -> Local Security Policy -> Local Policies -> Security Options
Microsoft network client: Digitally sign communications x2 -> Disabled
Microsoft network server: Digitally sign communications x2 -> Disabled
Andy
powellandy1 wrote:
...1) There is a setting in windows Local Security Policy which is incorrectly set by default for viewing an older communication protocol NAS...
My 2 Win10 systems access my NV+ and my two OS6 systems with no issues with no registry changes (an w/o the SC.exe config). I am running 10586. So there is perhaps a windows mystery here.
Start with the RN516, since share security mode isn't an issue there.
If my net use commands work, then powellandy's changes aren't needed.
If they fail, then I'd try them.
On the NV+, start with changing share security to user security (if you aren't using it already)
Then upgrade the firmware if it is downrev (since you might get a newer version of samba).
Then use the same steps. if net use fails, try powellandy's changes.
Sorry both.
I mis-read the question - I missed the mapping bit.
I have answered the question - How do I get my ReadyNAS to appear under the Computer section of Network in Windows Explorer - which I had problems with in both TH1 and TH2 versions of Windows 10.
Sorry
Andy
The answer above worked for me. The only change is where 'C' is listed in the command line it will need to reflect for actual volume name - that maybe 'C' or 'data', etc. or it will fail.
net use * /delete
net use t: \\nasipaddress\C /user:admin password
nasipaddress is the ip address of the nas (name likely works too)
C is the name of your nas volume
password is the NAS admin password
MacRory wrote:
The answer above worked for me. The only change is where 'C' is listed in the command line it will need to reflect for actual volume name - that maybe 'C' or 'data', etc. or it will fail.
Yes, you need to use an actual data volume name. My intial post was focussed on the NV+ v1 NAS, which has a volume of C (with potentially additional D,E, and F volumes if flexraid/jbod is used).
OS6 names are of course different.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
