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 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 used recovery to earlier Windows updates and spend 3 hours with Microsoft chat at no avail. I can get to teh NAS drives via ip (https://192.168.1.XX/admin/) and login.
I have also applied this patch from Netgear, but that has not worked either. Also looking into Netgear SMB solution, but not sure how to proceed as the solution is vague. Any help would be appreciated.
DM
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
17 Replies
Replies have been turned off for this discussion
- Update: Netgear admin team worked with me and after identifying the fact that i have two seperate readycloud accounts, they attributed the issue to SMB aliases. As a temporary workaround they removed the aliases. Temporary because it will be overwritten by config changes done in the GUI. Netgear admin will work with the Samba team on getting a real fix soon.
- 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
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.
Open windows explorer and try \\{nas-ip}\share, no need to map the drive for this test.
Neither method works for mapping or openning the shared location. I get the following message in either case: "Network Error, Windows cannot access \\192.168.1.16\share
check the spelling of the name. Otherwise there might be a problem with your network. To try to identify and resovle netwrork problem, click Diagnose... Error code 0x80004005 Unspecified error" and of course the Diagnose does nothing returning " Troubleshooting couldn't identify the problem"
I get the same result if I use the map Network drive and select the previously mapped network location (which is mapped within the etc/host file to this ip: \\ReadyNAS01)
DM
Hello motamedd,
If you have multiple users and the share permissions are set to Everyone, can you try removing Everyone from one of them and try accessing that share then log in using at least one of the users that are allowed to access it. Then try other folders, once done, try other users too.
Regards,
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
