NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Cannot access ReadyNAS shares after Win10 Fall Creators Update installed
I cannot access the shares of my RN316 NAS ('NAS1') in W10 File Explorer (network section). When I click on the name I get error 0x80070035. My second NAS (NVX) called 'NAS2' shows all its shares whe...
cabwav wrote:Isn't there a clue anywhere in why both NASes show up in File Explorer and Net View, but only one can be 'pinged'?
Both should respond to the ping command if you use their IP addresses. You can try ping -a ip-address to see what hostname is associated with that address.
On the main problem - in my experience, discovery of ReadyNAS by windows systems has always been a bit hit-or-miss. I have seen many posts here from people who say it works from some PCs and not others on the same network. I've also seen reports that it is inconsistent (works today, but didn't yesterday). I've seen these reports on all platform types (OS 4, OS 5, and OS 6), but they do seem to be more prevalent with the newest versions of windows 10 and OS 6.
Personally I reserve the IP address in my router, and routinely use the IP address to access the NAS. You can add shortcuts on the desktop, or add a network location for each share to File Explorer to make this simpler.
One other option (assuming you have a reserved address) is to just add the hostname to the hosts file on the problem PCs. https://support.rackspace.com/how-to/modify-your-hosts-file/
If you find a better solution, then it'd be great to post it.
Discussion already going over here: Access-issues-after-upgrade-to-Win10-V1803. Nothing suggested has helped me solve the problem (and I'm far from a novice), but maybe something there will solve yours.
Thank you for your reply. I have read the discussion in the link you sent, and tried several suggestions but this didn't solve my problem. I can't understand why the shares on the older Netgear NAS are accessible by clicking on its name, but not the shares on the newer RN316. Is this a W10 problem or a problem with the RN316?
Isn't there a clue anywhere in why both NASes show up in File Explorer and Net View, but only one can be 'pinged'? And why I can access the shares on the RN316 if I use the IP address, but not if I use the name of the RN316?
cabwav wrote:Isn't there a clue anywhere in why both NASes show up in File Explorer and Net View, but only one can be 'pinged'?
Both should respond to the ping command if you use their IP addresses. You can try ping -a ip-address to see what hostname is associated with that address.
On the main problem - in my experience, discovery of ReadyNAS by windows systems has always been a bit hit-or-miss. I have seen many posts here from people who say it works from some PCs and not others on the same network. I've also seen reports that it is inconsistent (works today, but didn't yesterday). I've seen these reports on all platform types (OS 4, OS 5, and OS 6), but they do seem to be more prevalent with the newest versions of windows 10 and OS 6.
Personally I reserve the IP address in my router, and routinely use the IP address to access the NAS. You can add shortcuts on the desktop, or add a network location for each share to File Explorer to make this simpler.
One other option (assuming you have a reserved address) is to just add the hostname to the hosts file on the problem PCs. https://support.rackspace.com/how-to/modify-your-hosts-file/
If you find a better solution, then it'd be great to post it.
Thank you StephenB! Your last suggestion (adding the IP address and device name to the hosts file) solved my problem. It still eludes me why I don't have to do this for my second NAS, but hey, it works!
Thank you for your help
Kind regards
Cabwav
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
