Access issues after upgrade to Win10 V1803 (I think it's a Windows issue, not a NAS one).

---

TheEther wrote:

StephenB:
WS-Discovery is different from NetBIOS name resolution.

I know it is different.  When I expand into "network" in windows file explorer on Windows 10, select "details" as the view, and then add the "Discovery Method" column, I see the NAS showing up in the computer list with the "discovery method" set to WSD.  It also shows up as a storage device also (discovery method SSDP).

I haven't done any special to enable this, so I am thinking that it works by default.

I do have SMB v1 enabled on the PCs though, so that might color the result.

The computer that's behaving differently was clean loaded with an early public release version of Win10 and the others were upgrades from Win7 a few months later.  Maybe that's a clue.  But SMBV1 doesn't seem to be the issue.  It was actually on on both desktops and off on the laptop.  The IPC$ connections didn't persist through a power cycle.

I did this;

map network drive

down on bottom "connect to website to store docs files"

entered my local server path "ftp://admin@192.168.x.x/"  which i obtained from my cel phone file explorer. promted for NAS login creds and boom.

it worked

Yes, I can access the NAS using the IP address using SMB (I don't know why you'd resort to FTP), I just can't access it via it's name.  That's not an issue with mapped drives, I just re-mapped them using the IP instead of the name.  But it's an issue for shares I don't (and don't want to) map.  I can no longer click on the NAS in "Network" and access it.  What's driving me nuts is that the computer clearly sees the NAS on the network, since it's there in the "Network" Explorer window.  But when I try to access it, it says it can't find it (not that I don't have permission to use it), and it takes a long time to decide that; as if it's trying a lot of options.  It never even asks me for a password, whihc would be the normal next step since I've not stored one (and don't want to)..

Did you resolve your issue--having same exact symptoms with 2 Windows 10 PCs-build 1803. Thanks!

Nope, and it "migrated" to my other PC's.  Oddly, I put a NAS I don't generally use online, and I could access it by name with no issue.  And I have one machine that can dual-boot to Win7, which has no issue.

All of our Windows 7 PCs can access it fine. The new Windows 10 PCs (Windows 10 was installed when purchased) cannot access it by name (just IP). However, the one we upgraded from Windows 7 to Wins10 can access it by name.

Just to avoid any confusion: Do these Windows 10 systems in question have any **** 3rd party Internet Security packages on board?

We are using ESET ENDPOINT SECURITY on all systems, including our Windows 7 PCs (over 40 of those) and they can access to the NAS by UNC Hostname fine.  All Windows10 and Windows 7 systems can access the NAS by IP address in Windows Explorer and the WebGUI. This seems to be related to SMB and or NFS settings that Windows10 will like.

---

sos4net wrote:

We are using ESET ENDPOINT SECURITY on all systems, including our Windows 7 PCs (over 40 of those) and they can access to the NAS by UNC Hostname fine.  All Windows10 and Windows 7 systems can access the NAS by IP address in Windows Explorer and the WebGUI. This seems to be related to SMB and or NFS settings that Windows10 will like.

---

No, this does proof the WS-Discovery (WSD) based name resolution does not work on your Eset Endpoint Security "protected" Windows 10 systems when attempting to access a shared folder on a device properly announced. 

Windows 7 most likely works because you still use NetBIOS there - for ReadyNAS discovery and for the name resolution. 

Have shown you several times where to check the discovery method in Windows Explorer - up to you.

And sorry, my trust to any of these Internet Security vendors is ways below zero - beyond of a "good feeling" KPI for the management having security measurements in place, the effective value is limited - and the risk that these security companies are breaking things are huge.

We uninstalled ESET on one of the Windows10 PCs and the problem persist--please explain.  Also, we have a Windows 10PC that was an upgrade from Windows7 and is works fine--with ESET. Network discovery has always been ON. They are on a domain and can connect to shares on servers and other PCs-just not the NAS by name. If you do some research you'll see that this is a common problem  with other manufacturers os NAS units (Synology for example). 

Today, two of my NASes have decided they can be accessed by name.  One still can't.  An interesting thing I noted is that when the user name and password window opened, it had in red near the bottom "The user name and password are incorrect", as if Windows were trying to pass improper credentials to it first (nulls, maybe?).

My NASes all show up in the Windows Explorer Network window as discovered by WSD.  NetBIOS is enabled as well, just in case.  One NAS has SMB Plus installed, the others do not.  I run Norton Security, and the first thing I tried was turning it off.  Besides, why would that prevent access by name and not by IP address?  It matters not if I double-click on the icon in Windows Explorer, type in the name in an Explorer window, or try to map them to a drive in Explorer or a command prompt (including with a user name and password).  When it's not working, Windows takes a good long while to think about it and, never having even offered me an opportunity to enter a user name and password, finally decides it cannot access the device.

One thing I have done recently is booted my dual-boot machine into Windows 7 because the Win10 installation kept crashing.  That sounds something like it is really using NetBIOS and needed a master browser, but that doesn't explain why one NAS is still unaccessable by name and why the discovery method is listed as WSD.  The Win7 machine can access all by name just fine.

Adding the IPadressofNAS  Hostname  to the Widnows 10 host file seems to have resolved my issue so far.  Example:

192.168.0.1  nasname

directions on editing host file here:  https://www.thewindowsclub.com/hosts-file-in-windows