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!
IrvSpI have read a pleathora of articles, these three were new to me, so thanks for sharing. All are tantalizing, and at least reassuring the we are not alone. One thing is certain, tracking down the exact cause on a given system is seemingly impossible. One thing I will check later today, is if SMBv1 is still active on my other Win10 system where the issue is not manifesting.
Perhaps the scheduled removal of SMB1 has not yet taken place on that system.
Even if so, I would be hesitant to re-enable due to security issues (the cure perhaps being worse than the disease).
Clearly, there is some combination of Windows networking updates, the router employed, specific network configuration, and specific system settings that are at play here. I am guessing the issue with the R7000 does have something to do with SMB1 being supported, but perhaps not later versions. Regardless, this is clearly a fairly widespread issue, and therefore, Microsoft may be the primary culprit.
Agree with you also --- since I already have a USB drive attached, that is likely not going to solve the issue. FWIW ... I shut down our entire network every Friday evening (for Shabbat). I literally power down the modem, the router, etc. So, when I start up the next evening, the order is boot modem, boot router, power up readyshare drive, connect devices to WiFi. The only two devices that would connect immediately upon reboot are my two Amazon Fire TV sticks, but they are certainly not being assigned MB duties! (Also, I confirmed that "Readyshare"/router is the MB). The issue persists from network restart to network restart.
Keep me posted if you learn anything more. I will do likewise!
EruvWeather wrote:IrvSpI have read a pleathora of articles, these three were new to me, so thanks for sharing. All are tantalizing, and at least reassuring the we are not alone. One thing is certain, tracking down the exact cause on a given system is seemingly impossible. One thing I will check later today, is if SMBv1 is still active on my other Win10 system where the issue is not manifesting.
Perhaps the scheduled removal of SMB1 has not yet taken place on that system.
No, the SMB1 I think is a red herring here. First of all SOME SMB1 stuff is still enabled on W10. If you go to Control Panel, Programs and Features, and on the left select Turn Windows Features on or off, and scroll down to SMB 1.0/CIFS File Sharing Support, you'll see ONLY yhe SMB 1.0/CIFS Client is not installed. The other 2 parts are installed.
This would only effect SMB 1.0 network devices anyway I think?
IrvSpI agree that SMB1 is likely not the issue. However, on my system, none of the SMB1.0 components are checked as installed. It is completely removed at this time.
EruvWeather wrote:IrvSpI agree that SMB1 is likely not the issue. However, on my system, none of the SMB1.0 components are checked as installed. It is completely removed at this time.
Hmm, wonder why 2 parts are on in mine? Hmm, checked wife's PC, her's are ALL off?
Shouldn't matter but I wonder why mine are on? Possibly some other s/w I'm running? We've got the same Internet Security Suite, Norton's, but at one point I did have McAfee? My PC is newer even, and we both came from W8.1? Her's is also a Dell and Dell says her PC isn't supported for W10 but it works fine?
