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 spe...
I may have found out what is behind my misbehaving NAS. On the bad NAS the following lines are in the Samba smb.conf file (space added between the ":" and the "o" since I can't figure out how to avoid a :o):
#dashboard: allow trusted domains = 0
dos charset = CP1252
hostname lookups = 0
map to guest = bad user
oplocks = 1
spotlight:fts = 1
#dashboard:#dashboard: orgunit =
#dashboard:#dashboard:no_sync_ads = 0
But the good NAS has the following lines:
#dashboard: allow trusted domains =
dos charset = CP1252
hostname lookups = 0
map to guest = never
oplocks = 1
spotlight:fts = 1
#dashboard:#dashboard: orgunit =
#dashboard:#dashboard:no_sync_ads =
It looks like the bad NAS is configured to assign the guest account if there are no locally matching credentials (bad user) rather than denying access so that credentials can be specified. I would like to change this config, but I don't want to modify the config files directly as they say: "This file is auto-generated. Do not modify!". Is there a way from the GUI to get the bad NAS to change its Samba config to match the Samba config good NAS? I searched everywhere that I could think of in the GUI, but can't find where to change this. I suspect that these lines a a remnant from when the NAS was previously setup for AD or cloud integration.
I managed to change share permissions on the bad NAS to get the smb.conf to have the following lines:
#dashboard: allow trusted domains = 0
dos charset = CP1252
hostname lookups = 0
map to guest = never
oplocks = 1
spotlight:fts = 1
#dashboard:#dashboard: orgunit =
#dashboard:#dashboard:no_sync_ads =
But, I still have the same problem with accessing it with Windows 2016 and WIndows 2019.
The symptoms are slightly different after getting "map to guest = never" in the smb.conf file. Instead of "path was not found", I am now getting Error 0x80004005 (Unspecified error) from explorer and System error 87 (The parameter is incorrect) from net use. but when I do a net view command I still get a path not found error for the bad NAS instead of a access denied error as with the good nas:
C:\>NET VIEW \\NAS1
System error 53 has occured.
The network path was not found.
C:\>NET VIEW \\NAS2
System error 5 has occured.
Access is denied.
Have you tried using the IP address in place of the NAS name?
Even though it is not a name resolution problem (as I can map drives if I first specify the username), I did try specifying the IP address and also the FQDN, just in case the Windows system had something cached for the name (although the problem with the bad NAS appears to occur with whatever Windows Server 2016 and 2019 system that I try). I am in the process of comparing all of the configuration files that are in human readable text format to see if I can find any difference between the 2 NAS units that may be causing the problem with one of the units.
After running a script to compare all of the configuration files between the good and bad NAS, I couldn't see any configuration differences that would cause one the behavior that I saw on the bad NAS. As a workaround I ended up enabling AD integration on the bad NAS, and Windows 2016 and 2019 can now see it normally again, and my backup software can access it correctly. I would prefer to have AD integration on this particular NAS anyway. It previously had AD integration, but I removed it to enable cloud access and then removed cloud access to see if that was causing the problem (as I no longer required cloud access for that NAS). I assume that adding either AD integration or cloud access made some configuration change that wasn't completely undone during the removal process. Even though I plan on keeping AD integration enabled for this NAS, I still would like to figure out why it behaves different from my other ReadyNAS 2312. For now, I will just be cautious about adding AD integration to any of my Netgear NAS units if I plan to remove it again later.
If you need remote access again, you can look into VPN options. I personally like ZeroTier, but I'm not using it in a business environment. Other options implemented via your router/Internet gateway may be better for your situation.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
