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...
In addition to the deprecation of SMBv1 in Win10, Microsoft has also been tightening up on guest access. Your problem could be related to the credentials Windows is using.
Try running the windows command prompt (CMD) and enter
net use * /delete
net use t: \\nas-ip-address\c /user:admin nas-admin-password
using the real IP address and admin password of course. Be careful on the typing, particularly spaces and the slash direction.
The first command terminates any open network sessions - it might tell you there are none, or it might prompt for confirmation. If it prompts, let it proceed.
The second command attempts to map the NAS data volume to drive letter T. That requires NAS admin credentials, and it won't work if your NAS admin password is still set to the default netgear1.
Let us know if this works (and if not, what errors you get).
There are a couple other possibilities you could check:
- Internet Security Software might be blocking access, so try disabling that software if it's installed on the PC
- If the network connection is classified as public, then Windows will block SMB access by default.
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.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
