NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
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 specifying the username before attempting to connect (the other one works fine). I can connect to both of them from Windows 10 without any issues. For the troublesome one I see the following behavior:
C:\ >NET USE Z: \\NAS1\BACKUP
System error 53 has occurred.
The network path was not found.
C:\> NET VIEW \\NAS1
System error 53 has occurred.
The network path was not found.
C:\>NET VIEW
Server Name Remark
-------------------------------------------------------------------------------
…
\\NAS1 NAS1
\\NAS2 NAS2
…
The command completed successfully.
C:\>NET USE Z: \\NAS1\BACKUP /USER:admin
Enter the password for 'admin' to connect to 'NAS1':
The command completed successfully.
C:\>
After mapping the drive letter to the NAS (NAS1), I can then access the NAS fine. With the good NAS (NAS2), if I don't specify a username, it simply asks for a username and password rather than giving a path was not found. Windows Explorer gives also gives errors just like the NET USE command does. I tried enabling insecure guest authentication on the Windows servers, but that didn't help and wouldn't explain why the servers have no problem with one of the NAS units but do with the other. The reason this is a problem for me is that my backup software gives an unknown errors as soon as it starts trying to access the troublesome NAS and I suspect that it has something to do with this difference in behavior between the 2 NAS units. The backup software can access the other NAS unit without a problem. The only significant difference between the 2 NAS units that I could find was that the troublesome one had ReadyCloud enabled which I have since removed. SMB settings between the two NAS units are identical and I have run out of things to try.
15 Replies
Replies have been turned off for this discussion
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.
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.
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).
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
