NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Win 10 suddenly can't connect ReadyNas DUO
Hi all, After a few Microsoft updates to Windows 10, I am no longer able to access my ReadyNas Duo using either a UNC path or mapped drives. The device shows under "network" but cannot be accessed. ...
PeterD2 wrote:
Unfortunately this didn't solve the problem. Added the static IP to the hosts file as directed, verified it's there after saving, but no go. If I enter "ping nas" at the command line it resolves to 192.168.1.9 and pings out fine.
What happens when you enter \\NAS in the windows explorer line?
Maybe also open CMD and enter
net use * /delete /y
net use t: \\NAS\C /user:admin nas-admin-password
and tell us what happens there too?
Unfortunately this didn't solve the problem. Added the static IP to the hosts file as directed, verified it's there after saving, but no go. If I enter "ping nas" at the command line it resolves to 192.168.1.9 and pings out fine.
I can only enter the shares by putting in \\192.168.1.9 into an Explorer window. All my backups are failing now too. I'm not really looking for a workaround, I need to actually fix the problem. It works from my laptop that's on an earlier version of Windows, but from the second PC in the house that's also on Win10 version 19033 (Nov update), it's suffering the same fate.
PeterD2 wrote:
Unfortunately this didn't solve the problem. Added the static IP to the hosts file as directed, verified it's there after saving, but no go. If I enter "ping nas" at the command line it resolves to 192.168.1.9 and pings out fine.
What happens when you enter \\NAS in the windows explorer line?
Maybe also open CMD and enter
net use * /delete /y
net use t: \\NAS\C /user:admin nas-admin-password
and tell us what happens there too?
OK, now we're getting somewhere! After clearing out the mappings and re-mapping T: I was able to get everything working.
Clearing out the old mappings alone probably solved the problem but I'm not 100% sure. I don't know if it was a combination of that and the modified hosts file, but I'm going to put the hosts file back the way it was and see. If it works, great; if not, I'll put it back. I will have to re-map the other dozen or so network drives, though.
OK, so I put the hosts file back the way it was, and was able to map drives. So I'd probably recommend clearing out all the existing mappings if anyone is having the same issue after installing the latest Win 10 update in future.
I'm glad you got it sorted out.
One limitation in Windows is that you can only use one credential with an IP address or hostname at a time. So it is possible that your old mappings were using a different credential that was getting in the way.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
