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.
TheEther wrote:
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.
Not sure the R7000 ever became the Master Browser? If it could then not other would become the Master Browser. W10's default it not to become one, see (https://technet.microsoft.com/en-us/library/cc959923.aspx) as the default it not to take over that function if one exists. My default is yes. That link doesn't call out W10, but it appears to apply. This is the YES function:
==========
This value makes the computer a browser. Upon startup, the computer attempts to contact the master browser to get a current browse list. If the master browser cannot be found, the computer will force a browser election. The computer will either be elected master browser or become a backup browser.
===========
As I read it, the W10 on boot will look for the master browser. If none there it becomes it, otherwise it is the backup (should the 'real' master browser go down, like another PC on the LAN). So in essence, the PC's will all get the current Browse list from the R7000 (I assume). Once the function fails on the R7000, the first booted W10 and still on-line will become the Master Browser. I think that sort of explains a lot too. Remember when my NET VIEW's came back instantly? Yet my wife's PC got the 1231 error? Her PC did not get the list because my PC was the backup when she booted (I suspect). With the R7000 still thinking it was the Master Browser but not functioning, her PC came back with the 1231 error. My PC since it was a backup Master Browser and had the 'current' list showed that. Again, just my logical conclusion for the problem. Also, adding to that and supporting it, once I rebooted the next morning after shutting down with NET VIEW working fine, I too got the 1231 error, why, because at that time the R7000 which had been on all night, on the PC boot it could NOT get the list from the R7000, so my PC gave out the 1231 error.
Now maybe my logic is unfounded and false, but that if correct points back to the R7000 as the cause of the problem.
Too many people must be using the Windows Explorer's Navigation pane's NETWORK to see shares and folders so they could copy files from a drive to the USB drive on the Router. It uses the SAME NEW VIEW type function. If that didn't work in W10 the noise level would be terrible. That said, that Explorer expansion of NETWORK would still work even with the R7000 not able to supply data, it just takes longer to open up. So I guess if there wasn't a need to move files from the PC to a USB drive location on the R7000 (or possibly other routers) no one would be complaining?
I agree that it is most likely something related to a bug in the R7000 firmware, and you explanation makes sense to me based on my research/experience. The symptoms first appearaed after I upgraed from 1.0.7.10 to 1.0.9.14 (skipped the interim builds due to another readyshare issue that was introduced with 1.0.7.12). While I cannot reproduce this on other systems -- I *have* seen other complaints about this type of issue on W10 after the Fall Creators Update. The missing link in all those posts was no one was talking about which router they were using. Is it possible the firmware on the R7000 is not fully compatabile with SMB 2/3?
Regardless, thank you for your post. At least there is the cold comfort that it is not something I did "wrong." ;-). A friend of mine in IT who specializes in networking was also stumpped. He basically said, since I can get to network shares without too much trouble, that it was not worth too much more trouble shooting time (this was after several weeks of my trying to figure it out). His guess is, there will be a future firmware and/or W10 update after which the problem will magically disappear (or get worse).
Hopefully someone from Netgear will chime in here. I am guessing the lack of mainstream complaints is because the vast majority of home users don't exchange files between computers, and those on business networks have IT folks who are doing the complaining and/or have their networks setup on a domain, etc. where the setup would be different. Also, as noted ... the other computers on my network are showing up in the Explorer list, so the average user might not notice that the printers are missing (why would they care?) from the list. Each example of this issue has somewhat different manifestations, which of course, makes it that much harder to nail down the issue.
