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 ...
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.
If it were linked to SMB1, I don't get why it wouldn't have the same effect on all three computers. But I can try enabling it.
I thought I had previously set my local internet as "sites allowed", but maybe whatever caused this reset it. If I can get rid of that damned prompt, I can live with what I've got. But it still makes me wonder why I have to.
I know I did a NET USE on one of the other computers and it didn't add an IPC$ connection.
That's the odd thing I can't figure out. Why did this happen on only one of three computers? But thatnks for the suggestions. I'll let you know what more I find out.
@StephenB:
WS-Discovery is different from NetBIOS name resolution. You can see in this link how WS-Discovery is listed separately from NetBIOS. I don't think WS-Discovery is enabled by default.Read the Microsoft article. Depending on various circumstances, Windows 10 can decide to remove SMBv1 support. For example, a clean installation will remove client support if it is not used after 15 days. OTOH, a system upgraded from an earlier version of Windows won't uninstall it. This could explain why you see different behavior on your computers.
Here is the full link:
https://support.microsoft.com/en-us/help/4034314/smbv1-is-not-installed-by-default-in-windows
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
