NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Access issues after upgrade to Win10 V1803 (I think it's a Windows issue, not a NAS one).
OK. So in the last week, Microsoft has upgraded my three Windows machines (two desktops and a laptop) to V1803. After the upgrade, only one of the desktops is acting strangely. All three machines ...
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
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
