NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Windows 10 Pro: no longer able to access NAS shares
I have been living in the past -- running an in home workgroup with a half-dozen machines mostly running XP, backed up and with files shared on two ReadyNAS NV+ and one ReadyNAS Duo. All machines ha...
StephenB --
Thanks. Just spent 90 minutes on a response, and then lost all the work due to some sort of authentification failure on the forum. Here's the short version, including that I initially misdescribed the problem: the share is sometimes mapped but is not accessible. The network is private and all machines and storage devices use a common username and password.
Attempting to map a share (as z: ) using the map network drive function produces at best the error message ""Z: is not accessible. An unexpected network error occurred." But the mapped share is visible as Z: in File Explorer; but when an attempt is made to access it the same error message is received.
Attempting to map a share using the command processor as you describe (describing the share to be mapped using \\nas-ip-address\sharename") produces the message "System error 86 has occurred. The specified network password is not correct." Mapping it exactly as you specifiy (using \\nas-ip-address\c") produces "The command completed successfully." and the share is again visible as the assigned drive but attempting to access it again produces a "not accessible" error message.
Attempting to map a shared drive on another local machine using either method was successful when attempted on a machine running XP32 and the drive could be accessed; while attempting to do so on a(n old but still functioning) machine running NT 4.0 again mapped the drives but they were not accessible.
I encounted a couple of other anomalies, but this summarizes the basic situation a little more succinctly than my lost message.
Thanks again. Any further thoughts?
What firmware is running on the various NAS?
Is the behavior with the duo different from the two NV+?
Is the security mode on the NV+ set to user security or share security? You'll find this in frontview (security->security mode). You might not see "share" security as an option there.
All devices are running 4.1.15 [1.00a043]
Security on both NV+ is share
Behavior of duo was different (error message 53 or 58); I'll try again and report back.
Share security was deprecated quite a while ago, because it was misbehaving with newer versions of windows.
I recommend changing to user-mode security. You can use a single user account for that (including the built-in admin account), and enter the user/password for the account into Win10's credential manager. There is a guide for the NAS part of this here: http://readynas.sphardy.com/2010/09/how-to-migrate-to-user-security-mode_4917.html
Interim update: the second NV+ and Duo were both not accessible with net use . . .
The NV+ returned "System error 53 has ocurred. The network path was not found", even though the machine is clearly visible on the network by Win10 with the IP address used in the command.
The Duo returned " ... error 58 ... The specified server cannot perform the requested operation."
I will try altering the security settings on the NV+'s as you suggest. As I recall the admin menu on the Duo it does not seem to offer differing security modes, but I will check.
Thank you.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
