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
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:
-------------
M Boyle May 17, 2017 at 10:37 AM
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 wrote:
Well, there's always Wireshark. At least, that's what I would do to see what's going on the wire.
I've never trusted ReadyShare. Too many reports of corrupted or flaky shares, and performance is basically terrible. Use a real NAS, like Synology or QNAP. Leave the router to do what it does best: route.
Yes, I was thinking of firing Wireshark up. Wasn't too sure what to look for? Since my PC is on a fixed 192.168.1.30 IP Address I guess I could filter for anything going in or out from that address.
Oh, I forgot to mention, it takes a good amount of time when I enter NET VIEW and get back the 1231 error... all other times, even the 53 error come back immediately. All the more reason I think the router isn't responding or possibly W10 TCP/IP is retry and/or timing out and throwing the error. Possible that it got an error but didn't have a message for it so threw the catch-all error?
My USB drive is 2.0 and connected to 2.0 port and has worked 'forever', although in the beginning I did have problems with bad DLNA catalog when I first got the router years ago. Worked with NG Support and eventually got it fixed. Everything worked fine until recently. Of course there could be a possibility of some disk corruption too I guess causing problems? When I get a chance I'll take it to the PC to be sure. I have already used NET USE to assign it a drive letter and ran CHKDSK on it and it was clean???