NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
cburgess002
Dec 09, 2021Aspirant
Network path was not found
I have 2 similarly configured ReadyNAS 2312 units and am getting a "Network path was not found" error when I try to connect to one of them from Windows Server 2016 and Windows Server 2019 without spe...
StephenB
Dec 09, 2021Guru - Experienced User
What firmware are you running?
If you can't sort out what is going on with name resolution, one option is to just put them in the HOSTS file.
FWIW, I reserve the NAS IP addresses, and use the IP addresses in my NAS backup jobs.
- cburgess002Dec 09, 2021Aspirant
I was running the latest Long-Term Support Release (6.9.6), but upgraded to the most recent Stable Release (6.10.6) to see if it would fix the issue because the NAS that worked without issues had the most recent stable firmware. It is not a name resolution problem as I can map a drive if I first specify the username. The issue is that if I don't specify a username, Windows Server 2016 and Windows Server 2019 give a path not found error rather than asking for a username. For most things this isn't an issue, but it appears to be causing my backup software to fail when accessing the NAS. I just have no idea why one NAS is behaving different from the other. I thought that it might have something to do with insecure guest access being disabled on Windows (although it doesn't explain why one would work), but enabling it didn't help.
- StephenBDec 09, 2021Guru - Experienced User
cburgess002 wrote:
It is not a name resolution problem as I can map a drive if I first specify the username.
Have you tried creating running the Windows Credential Manager on the problem machines? Delete any credentials that are stored there for the NAS. Then try entering a new one (either with the username, or with the username and password).
- cburgess002Dec 09, 2021Aspirant
I had checked and there were no stored credentials on any of the systems. I also tried adding stored credentials and that worked as expected (but I didn't try my backup software with Windows stored credentials only with credentials stored in the backup software). I don't want to have Windows Credential Manager stored credentials for the NAS as it would give any malware that I might encounter access to destroy backups on the NAS.
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!