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:
-------------
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, 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:
-------------
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!
IrvSp... So, it does look like something realted to SMB1.0!
On my system, there are three checkboxes beneath SMB 1.0 ...
> ... Automatic Removal
> ... Client
> ... Server
NONE of the boxes are checked.
On the other Win10 system on my network, ALL the boxes were checked.
So, to clarify ... you only checked the "client" box, an no others, and that resolved the issue for you?
If so, I may try that. Although, given the security considerations, and the fact that mapping the ReadyShare drive makes it easily accessable, and everything else works, I may just leave things alone.
Regardless, this is fascinating on so many levels, and of course - it would be good if there was some real clarity from Microsoft as to how these changes are being rolled out and the impact to users.
EruvWeather, sorry, wasn't complete in my post. Both Auto Removal and Client are now both checked on both PC's. Before my PC had Server Checked but NOT Client, and the two were reversed on my wife's PC. Turning off Server and on Client fixed my PC's problem. We went out for a few hours and when both were re-booted when we came home BOTH PC's NET VIEW works.
I have a 'theory' why the fresh clean install of W10 Pro x64 Ver. 1709 worked and the other PC didn't...
WannaCry used SMB1 and MS released its fix on May, but I know it worked well after that. So I suspect some other 'protection' I had must have changed mine. What it was, can't tell?
However, that link you provided, https://support.microsoft.com/en-us/help/4034314/smbv1-is-not-installed-windows-10-and-windows-server-version-1709, either is WRONG, or did it?
That link has a lot of statements:
That LAST one probably explains the problem, I guess it DOES need the Server? I don't know if Windows Explorer when NETWORK is selected uses the same code NET VIEW does, but since neither works, I'm sure some parts or calls were.
Disecting the above comments I clipped out:
The first 3 are just contradictory in my mind.
However, the 4th could have been my problem? I know I installed V1709 on 10/18. 15 days will get me to Early Nov., but we were out of town until 11/12. PC was first turned on then. Quite possibly it was sometime close to that I first discovered the NEW VIEW problem?
Quite possible it just deleted/uninstalled the SERVER and left the other 2 features... ???
In any event, I've got it working and Windows Explorer as well as Explorer++ has no problems at all with the Network.
