NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Sandshark
May 27, 2018Sensei
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 ...
Sandshark
May 29, 2018Sensei
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.
TheEther
May 30, 2018Guru
@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
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!