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!
EruvWeather, I am at a TOTAL loss here...
Before my wife got up I rebooted the router. Of course NET VIEW worked after that just fine. I went and had breakfast and for over an hour my PC say idle, and even the display and hard disk went to 'sleep'. Woke it up and ran NET VIEW:
C:\>net view
Server Name Remark
---------------------------------------
\\IRV8700 Irv's 8700
\\LARAINE-XPS8500
\\READYSHARE readyshare
The command completed successfully.
Still working, good. Since my wife's PC is now on I went to it since it is a W10 PRO. Surprise, it gets a 1231 error from NET VIEW!!!
This is all very confusing to me? We both have the same W10 release, 1709, and even similar h/w but one is HOME edition and the other PRO? I know you have similar results, one W10 PC works, the other doesn't?
I almost suspect some sort of 'connection' needs to be made between the router and PC when the router comes up or reboots? Once up and another PC comes on-line it will not work for that PC maybe? Might explain why when it was working fine one night before I shutdown it failed the next morning?
The PC must talk to the Router when it starts, if nothing else, to get its IP Address and Internet access. Hmm, this could be a large clue! Both of these PC's have a router assigned/reserved IP Address. Wonder if that could have something to do with it? On the one that fails for you, it is a reserved IP Address and the other isn't?
Both computers are running W10 Pro x64. I am thinking it may some sort of "master browser" issue, but it sure seems like the computer in question is just not refreshing the network list.