NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Since June 18 cannot map NAS as network drive to Windows 10
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 ac...
SOLVED
At least as a workaround this works, until there is an update/patch from Netgear available to make readynas compatible with Windows 10 credential Manager:
1- Log in the local ReadyNAS via the web browser "https://192.168.1.xx/admin/" and enter your password.
2- Click on the "Shares" on the top grey banner
3- Click on the Gear icon to the right of the folder(s) ("/data", etc.) that needs to be mapped/mounted and select setting.
4- Select Network Access on the top grey banner for the folder.
5- select (checkmark) the "allow anonymous access"
6- Click Apply
You are now all set to map NAS as a network location or drive in Windows 10
On Win 10 you should now be able to use the file explorer, go to "This PC", select Computer from the top file explorer menu, and click "map network drive" or "add a network location". You can then either use the windows network map to navigate to the network drive and assign it to a letter drive ("X:, Y:, Z:" etc.) or you can type the ip address of the NAS followed by the shared folder name ("//192.168.1.xx/data") to map it.
DM
Hi Stephenb,
You wrote "If you have a share with the same name as the data volume, then you should rename the share". I see your point about "data" being a nas reserved system folder. My share folder is actually a different name. "Mydata" or "Myvideo". I just used "data" as a generic folder reference for my instructions above.
That said, i also agree that there is more to it. After my post above, i rebooted my pc and the problem with not being able to access the share folder via network mapping returned. I then during the network drive mapping had to use a secondary local account login credential to map the share drive.
I still insisit that all of the above is a temporary workaround until the root cause for this Windows10/ReadyNas incompatibility (in either credential management or SMB) is resolved.
DM
You wrote "If you have a share with the same name as the data volume, then you should rename the share". I see your point about "data" being a nas reserved system folder. My share folder is actually a different name. "Mydata" or "Myvideo". I just used "data" as a generic folder reference for my instructions above.
That said, i also agree that there is more to it. After my post above, i rebooted my pc and the problem with not being able to access the share folder via network mapping returned. I then during the network drive mapping had to use a secondary local account login credential to map the share drive.
I still insisit that all of the above is a temporary workaround until the root cause for this Windows10/ReadyNas incompatibility (in either credential management or SMB) is resolved.
DM
motamedd wrote:
I still insisit that all of the above is a temporary workaround until the root cause for this Windows10/ReadyNas incompatibility (in either credential management or SMB) is resolved.Perhaps PM mdgm-ntgr or Skywalker and ask if development wants to look into it. There are quite a few recent cases of people having problems with credentials after they upgraded to 6.5.1.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
