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 want to use a mapped network drive and Windows explorer. (Nothing remote or fancy.)
Any Ideas on how to fix this?
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.
20 Replies
Replies have been turned off for this discussion
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
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.
- Upgraded to Windows10 Home today and ReadyNAS102 disappeared from networks in Explorer. It is ping-able and I can get to admin by typing it's IP. Taking steps from here and the Synology Link, it is now working. Steps: On ReadyNAS go to Apps and install SMB Plus. Launch it. Select tab for SMB Version. Choose SMB 1. Restart ReadyNAS On PC: Run regedit. Locate HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/Windows/CurrentVersion/Policies/System. Create a new DWORD entry with the name EnableLinkedConnections and value 1. Command Prompt Admin Mode: sc.exe config lanmanworkstation depend= bowser/mrxsmb10/nsi sc.exe config mrxsmb20 start= disabled Restart your computer. My Readynas now appears in explorer under networks. I guess the sum of this is to force SMB1 on NAS and in Win 10. The last step is to make a huge mental note that if Ms or Netgear ever release a patch to SMB3.x you will need to undo the above :) Thats it. Good luck!
Hello Destne,
Thanks for sharing. Welcome to the community!
Regards,
Upgraded to Windows10 Home today and ReadyNAS102 disappeared from networks in Explorer. It is ping-able and I can get to admin by typing it's IP. Taking steps from here and the Synology Link, it is now working.
Steps:
On ReadyNAS go to Apps and install SMB Plus. Launch it. Select tab for SMB Version. Choose SMB 1. Restart ReadyNAS
On PC:
Run regedit. Locate HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/Windows/CurrentVersion/Policies/System. Createa new DWORD entry with the name EnableLinkedConnections and value 1. Command Prompt Admin Mode:
sc.exe config lanmanworkstation depend= bowser/mrxsmb10/nsi
sc.exe config mrxsmb20 start= disabled
Restart your computer.
My Readynas now appears in explorer under networks. I guess the sum of this is to force SMB1 on NAS and in Win 10.
The last step is to make a huge mental note that if Ms or Netgear ever release a patch to SMB3.x you will need to undo the above
Thats it. Good luck!
NB Reposted as formatting lost on previous post...
Destne wrote:Upgraded to Windows10 Home today and ReadyNAS102 disappeared from networks in Explorer. It is ping-able and I can get to admin by typing it's IP. Taking steps from here and the Synology Link, it is now working.
Steps:
On ReadyNAS go to Apps and install SMB Plus. Launch it. Select tab for SMB Version. Choose SMB 1. Restart ReadyNAS
On PC:
Run regedit. Locate HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/Windows/CurrentVersion/Policies/System. Createa new DWORD entry with the name EnableLinkedConnections and value 1. Command Prompt Admin Mode:
sc.exe config lanmanworkstation depend= bowser/mrxsmb10/nsi
sc.exe config mrxsmb20 start= disabled
Restart your computer.
My Readynas now appears in explorer under networks. I guess the sum of this is to force SMB1 on NAS and in Win 10.
The last step is to make a huge mental note that if Ms or Netgear ever release a patch to SMB3.x you will need to undo the above
Thats it. Good luck!
NB Reposted as formatting lost on previous post...
If you're using the preview releases of Windows 10, you might check to see if it works without dropping down to SMB1 now...
I'm currently on the "Fast Ring" for the Windows 10 previews, and after the last update (Build 11099), it started working as expected with no changes needed. I would think this means that if you choose not to use the preview releases of Windows 10, it will work when the next "stable" build comes out.
Hi I have two Netgear 4 disk RN104s with firmware 6.5.1 (upgraded this monring from 6.5) along with Windows 10 home edition build 10586.420 and up until this last weekend (18 June 2016) I was able to access the NAS by mapping them as a network drive or as netwrok locations. Since June 18 I cannot access the NAS via a mapped drive or via a network location. I can get to them via ip and login.
I ran the entire pathch recommended and intstalled the SMB app as well as ran the recommended changes to windows registry and command line etc. It did not fix my problem. I now need to know how to undo the whol thing. Espescially need to know how to undo the command line portion: "sc.exe config lanmanworkstation depend= bowser/mrxsmb10/nsi" and "sc.exe config mrxsmb20 start= disabled" Also if there is a new fix since this post, please let me know.
Thanks,
DM
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
