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!
IrvSp wrote:
It can't be dead. Otherwise why would it work sometimes? Also part of it is still installed. On the Control Panel, Programs and Features, Turn Windows Features on or Off, there is SMB 1.0/CIFS File Sharing Support. 2 of the 3 parts are enabled, the Automatic Removal and the Server. h Client is NOT installed (by default). So I'd think some of it does work?
I think this is answered elsewhere in that Microsoft thread:
If I set any other PC to be the master browser, windows version irrelevant other than not 1703, then all the computers can run "Net View" and return the list of computers (hence a bunch of other network commands work).
My guess is that things work whenever your Netgear is the master browser. If either of your two W10 PCs are the master browser, then it doesn't work.
In any case, the writing is on the wall. Stop using NET VIEW. Maybe you can eke a little more use out of it, but its days are numbered, if not already passed.
The MS articles you cited ... I came across those about a month ago when I was first trying to unravel this issue. The depreciation of SMB 1.0 is a tantalizing clue, but the other Win10 Pro machine on our network is not exhibiting the same behavior, so that does not necessarily align.
Network discovery, etc. is already up and running on the machine in question, otherwise I would not even be able to connect to readyshare or other network shares.
Interesting clues for me include the following:
1) In the Windows Exporer "network" list, other computers show up, but not readyshare or the printers,
2) If I click on network within Windows Explorer, the other computers do show up, and the printers are there under "printers, scanners," etc.
3) I can access readyshare by entering \\readyshare in the address of explorer. At first, I get a a "windows cannot access ... bad address or issue with network ... do you want to diagnose network issues" box. However, if I wait between 15 and 30 seconds, and try to access readyshare again, it is fully accessable. Also, if I do "diagnose" network issues, none are found ... but after the process of "diagnosing," readyshare is accessable (but never shows up in the Network places list).
3a) While the above is true now ... the 15-30 second delay used to be true for the other computer I access files from for awhile, but seems to have gone away. After the router update from .14 to .18, the computer in question did not show itself (!) in the network list until I changed Function Discovery Resource Publcation from "manual" to "automatic." That is the only tweak I have made thus far, in order to not make the situation potentially worse. Another tantalizing clue, but it clearly has not resolved the larger issue.
4) Despite the above, printing to/scanning from network printers works just fine and as expected.
I have tried to research how to manually make the R7000 the master browser, but have not found any clues of how to do that.
This seems like some combination of W10 not using SMB 1.0 anymore, and a master browser issue ... but not consistent from system to system.
So at this point - it is "cosemtic" in that I can still do and get to everything I need, but some cache somewhere is not being updated and I do not know how to force a refresh.
EruvWeather wrote:I have tried to research how to manually make the R7000 the master browser, but have not found any clues of how to do that.
Look here, https://technet.microsoft.com/en-us/library/cc959923.aspx for details. The Registry for W10 should have the MaintainServerList already set to yes. If you REALLY want to force it, then add IsDomainMaster to the registry subkey. I did that and it made no difference so I removed it.
Don't think the R7000's OS is exposed and you can't make it the Master Browser.
