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?
PeterD2 wrote:
If I open up an Explorer windows and put in the static IP (192.168.1.9) it opens the content in my Web Browser, not an Explorer window.
You need to enter \\192.168.1.9 into the file explorer address bar. Just entering the IP address (or using the wrong slash direction) will open your browser. That's Windows behavior, not the NAS.
PeterD2 wrote:
Furthermore, every connect attempt results in a credentials challenge.
Likely you've been using guest (everyone) access with the NAS. Open the Windows Credential Manager on the PC, and select "Windows Credentials". Delete any credentials that are already stored for NAS or 192.168.1.9. Then create two new windows credential - one for the host name, and one for the IP address. If the only user account you have on the NAS is the built-in admin account, then consider adding a new user account to use for these credentials.
PeterD2 wrote:
The device shows under "network" but cannot be accessed. Clicking the NAS icon results in a Windows Network Error (Windows cannot access \\NAS Check the spelling of the name, Otherwise there might be a problem with your network, etc).
This can be the trickiest to fix. Make sure you have access by the IP address before looking at this one. Then enter \\NAS in the file explorer address bar, and see if that gives you the expected share list. If it doesn't, then the simplest work-around is to enter NAS (and it's IP address) into the Windows HOSTS file. This overides any other name lookup method, and will make sure that \\NAS is resolved to 192.168.1.9.
Basic instructions are:
- Type Notepad in the Wiondows search field.
- In the search results, right-click Notepad and select Run as administrator.
-
From Notepad, open the following file (you can copy/paste it into File > Open):
c:\Windows\System32\Drivers\etc\hosts
-
Add a new line that says 192.168.1.9<tab>NAS (using the real tab key as the separator)
- Select File > Save to save your changes.
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.
If you put the NAS address into Hosts and re-booted, and the NAS name is still not resolved, then you made an error somehow. One possibility is that you followed the examples exactly. But they start with #, which comments them out. Your entries should not. Typos are, of course, another possibility.
No, it was entered correctly. There is somethng actively preventing the new W10 iteration from accessing the old Duo. The PCs (both of them with 19033) were restarted to no effect. Here are the first few lines of my hosts file:
# Copyright (c) 1993-2009 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host# localhost name resolution is handled within DNS itself.
# 127.0.0.1 localhost
# ::1 localhost192.168.1.9 NAS
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.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
