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 ...
FWIW, I had some similar issues after the last windows update, and ended up remapping the drive letters to IP address.
Sandshark wrote:
But when I go to move a file, I get a Windows security warning that my internet security settings suggest that one or more of the files may be harmful and I have to click OK for every single file.
Open "Internet Options" on the PC, and click on "security". Then select "local intranet", click on the "sites" button, followed by "advanced". Enter your LAN subnet into the "add this website into the zone" dialog - for instance 192.168.0.*
That should eliminate the warning after you close and reopen your file explorer windows.
Sandshark wrote:
This is the only thing I don't know wasn't there before, but I suspect it wasn't because I had no drive mappings using the NAS IP address. NET USE shows me an undesignated (no drive letter) connection to 192.169.0.42\IPC$. That is my NAS's address, and Microsoft says this is the "Interprecess Communications Share", apparely linked to anonomous users, even though I never use anonomous access.
192.168.0.42?
IPC$ used for anonymous requests (like enumerating SMB shares with net use nas-ip-address), not so much with anonymous access. You shouldn't be seeing a persistent connection to it though, normally it doesn't show up at all in net use. Maybe one of your net use or net view queries is hanging? Does this still show up after a reboot?
This could be the result of Microsoft deprecating SMB1. The link offers some suggestions for restoring some of the functionality. Microsoft is trying very hard to sunset SMB1, so even those tips might not work.
TheEther wrote:
This could be the result of Microsoft deprecating SMB1.
No. Sandshark runs OS 6 on his ReadyNAS, and that supports SMB 3.
StephenB wrote:
TheEther wrote:
This could be the result of Microsoft deprecating SMB1.
No. Sandshark runs OS 6 on his ReadyNAS, and that supports SMB 3.
Sure. But one of the functions lost with SMB1 is the Computer Browser, which uses NetBIOS. That means that displaying computers through the Windows Explorer as well as the NET VIEW command no longer work. This is consistent with Sandshark's symptoms.
TheEther wrote:
Sure. But one of the functions lost with SMB1 is the Computer Browser, which uses NetBIOS. That means that displaying computers through the Windows Explorer as well as the NET VIEW command no longer work. This is consistent with Sandshark's symptoms.
Not completely consistent. OS 6 supports WS-Discovery, so \\RN512A in the file address bar should work with Windows 10. It's easy to test though, all Sandshark would need to do is enable the SMB 1.0 client on one of the systems, reboot and then retest.
Though in my experience, the computer browser has always been a bit hit-or-miss with linux systems. I reserve the NAS IP addresses, and generally use them on my home network.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
