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!
TheEther, there are some things in my mind that rule out Windows... NOT one report of this on the latest Fall Update version, 1709. The other link I posted to a thread here that had both W10 and W7 doing it.
My first posting had shown only HARD WIRED stuff between my PC (IRV8700) and the Router (192.168.1.1) and the USB drive (READYSHARE). Later posting showing my Wife's PC coming on-line and that is WIRELESS. There are other devices that are wireless connected all the time though, like Amazon FireTV stick and Echo, iPad's, and when on, a SmartTV. Nothing else. All those were on when I ran NET VIEW.
Saw the FIRST link and I did change the SERVICES to AUTOMATIC with no change.
2nd link is for a BETA and almost 2 years old.
3rd one had a fairly recent response and claimed 1709 fixed the problem.
My thought right now lead me to the FIRMWARE. I really suspect 'over time' something drops or changes in the Router and it can't respond to the broadcast and W10 can't handle the 'error' or it sends back something W10 can't handle and posts the error.
Well, I just tried NET VIEW again:
C:\>net view
System error 1231 has occurred.
The network location cannot be reached. For information about network troubleshooting, see Windows Help.
Nothing has changed on either PC... sometime between may last post 8:54AM and now it started to fail again. I'm sure if I reboot the router (or possibly disable UPnP) it will be working again.
It could very well be connected to the USB share too? It seems strange to me that when my iPad's program I use that has both a DLNA and SAMBA client if the DLNA client can't see the share other than the router itself, but the SAMBA client has no problem, it is somehow connected to what the Router is presenting to the LAN. That takes W10's PC out of the equation, no?
Thinking along the lines that it might be the USB share, I did the Safely Remove and once it was ran NET VIEW again, and got a COMPLETELY different error :
C:\>net view
System error 53 has occurred.
The network path was not found.
Weird??? Adding MORE questions... I pulled the USB cable and plugged it back in. Immediately ran NET VIEW (disk is active, probably rebuilding the DLNA catalog as the light shows drive being read, and got this:
C:\>net view
Server Name Remark
---------------------------------------
\\IRV8700 Irv's 8700
\\LARAINE-XPS8500
The command completed successfully.
Just removing the USB drive allowed NET VIEW to show me the REST of the LAN?
Ahh, waiting for the USB Drive light to stop flickering:
C:\>net view
Server Name Remark
----------------------------------------
\\IRV8700 Irv's 8700
\\LARAINE-XPS8500
\\READYSHARE readyshare
The command completed successfully.
At this point I'm 'declaring' it IS NOT W10, but something to do with the firmware, probably similar to WIFI being lost, but this has to do with the USB Drive, and it is causing responses back to the NEW VIEW command in Windows to be 'bad' and W10, if anything' doesn't know how to handle it and throws a useless error...
Now the REAL question is do OTHERS have this problem? I did 'report' this in the lastest firmware thread, even using JamesGL but never got an answer.
Again, NOTHING was changed in either PC or other attached device, and all done here on my W10 1709 release PC as I entered the NET VIEWS.
