Did you try just disabling smbv1 and not actually removing the windowsfeature?
edit: by running this command in an elevated powershell prompt:
Set-SmbServerConfiguration -EnableSMB1Protocol $false
NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
EruvWeather, TheEther, guys, this is driving me nuts...
As it stands NOW my wife's PC continues to have NET VIEW work properly, and has since I did a clean install of her X64 W10 Pro Ver. 1709. On the other hand mine will only work IF I reboot the Router and her PC is not on. Once her's comes on, it no longer works, and will never work again until I reboot the router.
I opened the POWERSHELL on both PC's and ran "get-smbserverconfiguration" and compared results.
Interesting, on mine EnableSMB1Protocol is set to True, but on her's, it is set to False?
Checking Features installed I have SMB1 Server checked where her's has Client checked?
Odd, what do you have?
I've set mine to Client now but need to re-boot. Will update when I come back on.
EDIT:
FIXED IT!!!!
GET-SMBSERVERCONFIGURATION now matches her's and it WORKS as expected!!!
C:\>net view
Server Name Remark
---------------------------------------------
\\IRV8700 Irv's 8700
\\LARAINE-XPS8500 Laraine's XPS8500
\\READYSHARE readyshare
The command completed successfully.
I don't KNOW how my SMB1 features were set or when, or even why.
Suspect at this point a change happened during one of MS's Updates?
Searching the web I found this page, https://community.spiceworks.com/topic/1995592-disabling-smb1-stops-domain-authentication marked SOLVED.... in it:
-------------
M Boyle May 17, 2017 at 10:37 AM
Did you try just disabling smbv1 and not actually removing the windowsfeature?
edit: by running this command in an elevated powershell prompt:
Set-SmbServerConfiguration -EnableSMB1Protocol $false
---------------------
Wonder if I did that it would have fixed it as well?
EruvWeathergive this a try... might just work!
A few more clues:
This is going to likely come down to weighing the security risk over the aesthetics of the Network places Explorer. Really leaning toward this being a SMB 1.0 issue and the R7000.
NETGEAR ... if anyone is reading this, some official insight would be beneficial.
IrvSpread through the comments at https://blogs.technet.microsoft.com/filecab/2017/06/01/smb1-product-clearinghouse/ ...
Specifically:
Greg Zoll
Computer Browser is used for the Workgroups, because SMBv2 & 3 require that service to discover other shared or available devices on the Network. It has nothing to do about the Domain alone, since the Domain has to use SMB protocols.
A fix needs to be pushed when SMBv1 is removed through the next update cycle, that Computer Browser Service stays and is changed from Manual to Automatic. Also Windows needs to be able to figure out that when a SMB Share off of a Server or NAS is set as Master Browser, that Windows does not just give an error message. Windows needs to be able to find out that it is not the Master of the Workgroup or Domain and in Settings under Network.
Reply
NedPyle [MSFT]
When SMB1 is gone, there is nothing for Computer Browser to use as a transport – it relies on SMB1. The goal is not to make NetBIOS/bowser work if we care about security.