NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Can't access NAS by its name in the network after 6.10 upgrade
Before the 6.10 upgrade I was able to access all our shares simply by accessing \\NAS01. After the update, none of our Windows PCs was able to open the location, receiveing a Windows Explorer error s...
No, the IP is static and hasn’t changed.
If the IP address is static, then it can't be caching (since the cached hostname would still be correct).
It isn't clear to me why changing the credential made a difference. If you still have PCs that can't access the NAS, perhaps try rebooting them instead, and see if that works.
It isn't clear to my either, which is why I posted it here. I never had to manually add credentials, but for some reason I had to this time. The weird thing is I didn't need to add credentials when I changed the NASs hostname.
I'll report back tomorrow morning after everyone boots up their PCs at the office. If I get a ton of calls and IMs it means it didn't work and everyone will have to manually enter their login details.
You are not the only one that has suffered from their NAS not being accessable by name in precisely the manner you describe. I added the IP address to the HOSTS file to "solve" it. I have mentioned this many times here in the forum, and all I get are responses about things I have checked long ago.
Sandshark wrote:
You are not the only one that has suffered from their NAS not being accessable by name in precisely the manner you describe. ... I have mentioned this many times here in the forum, and all I get are responses about things I have checked long ago.
Agreed. Discovery is hit-or-miss in all the ReadyNAS I've owned (4.1.x, 4.2.x, and 6.x.x) using both Windows 7 and Windows 10. Often experimentation seems to cure it, but I think it's more of an accidental side effect. FWIW, I've found similar problems posted for other NAS and linux systems.
There is an "Legacy Windows Discovery" checkbox in the web ui (system->settings->services->SMB) that you could also try (particularly if you are using older versions of Windows). It might not help, but shouldn't do any harm.
Sandshark wrote:
I added the IP address to the HOSTS file to "solve" it.
This will of course work, but doesn't scale well if you have lots of PCs that need access.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
