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!
I am having the exact same issue on my Windows 10 system. Latest R7000 firmware. My Windows 7 system has no issues, nor does another Win10 system on my network.
The Win10 system in question can reach the other computer in the network listing in Explorer, but readyshare only by manually entering the \\readyshare address in the address bar.
I am also getting the 1231 error when running net view at the command prompt.
I noticed the behavior when upgrading from 1.0.7.12 to 1.0.9.14 and now .18.
Have not tried toggling UPnP.
Seems cosmetic at one level, since I can reach the other systems and network printers -- and even readyshare after a delay in explorer, but the network listing in explorer does not include readyshare or the printers. The only culprit left from my own digging on this issue is the router ... and it is quite frustrating.
Interesting...
EruvWeather wrote:I am having the exact same issue on my Windows 10 system. Latest R7000 firmware. My Windows 7 system has no issues, nor does another Win10 system on my network.
The Win10 system in question can reach the other computer in the network listing in Explorer, but readyshare only by manually entering the \\readyshare address in the address bar.
I am also getting the 1231 error when running net view at the command prompt.
I noticed the behavior when upgrading from 1.0.7.12 to 1.0.9.14 and now .18.
What is the difference between the W10 PC that works and the one that doesn't? At they the same? Same W10 version, same edition (Pro/Home)?
Although both rebooting the router and changing things like UPnP's state will make my W10 Home 1709 version work, it is only temporary.
