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!
See my response to TheEther and some more discovery I did.
See the last part though when I disconnected and reconnected the USB drive from the Router. Merely disconnecting it changed the error code that Windows produced. Reconnecting it 'repaired' NET VIEW. Yes, reconnecting it would allert the router there was an added share to handle, but that was INTERNAL to the router. At first the USB Drive is not really available as the disk was being read, but that was enough to make NET VIEW work again, and once the disk was read, a subsequent NET VIEW did add that share. All done with no change on either PC.
So let us assume 'something' I'm running would cause this to break? It isn't my wife's machine either, and that wasn't on the last time this happened. I can't trust letting the PC sit and 'things' happen all the time when connected to the Inet. Also I've had this happen when ALL PC's were off, just last night for instance. Before I shutdown this PC (only one on) I did a NET VIEW and the Router Share was seen. It WAS not when I booted this PC this morning, and the reason I opened this topic.
I am NOT discounting it could still be a W10 or some program doing something to damage the ability to see the LAN with NET VIEW, but again, since I know the SHARE names even when NET VIEW itself fails, NET VIEW \\SHARENAME works, so that too sort of rules out possibly a W10 problem, no?
I am at a loss how to CAPTURE the real culprit here? Surprised others (other than that one link I posted) are not experencing this too? Not many use USB drives? USB drive problem? It all worked fine before though?
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???
TheEther, tried WireShark. I guess I don't know how to really capture NET VIEW. I did set the filter to show everything from my PC, 192.168.1.30, and I started the capture before I issued NET VIEW and stopped it after I got the 1231 error. However I can NOT find the actual command in the capture. I do see a lot of traffic back and forth from my PC to the router (192.168.1.1)? Only a 26K file so I've attached it here (it was removed, wrong ext, sigh... PM me and I can send it to you if interested). If you can, can you look at it? In the capture I see a LOT of references to READYSHARE (share name of the router), but at an odd IP Address, 224.0.0.252? Could that be the internal Router USB address?
I see in the list a lot of requests to tell my PC who has 192.168.1.9? However I only have 192.168.1.2-5 attached wirelessly now and my PC at 192.168.1.30 on-line? Screen capture of some of those attached...
Do you know how I can capture only the NET VIEW traffic?
TheEther@, I am totally shocked?
I rebooted the router and of course NET VIEW worked:
C:\>net view
Server Name Remark
------------------------------------
\\IRV8700 Irv's 8700
\\READYSHARE readyshare
The command completed successfully.
So I started WIRESHARK. Same filter and this time I got hardly any lines (see capture attached). It was so fast I did it twice and all the traffic is shown in the capture.
I think I can 'fool' the s/w here by renaming the original WireShark capture extension from .pcapng to .jpg and then if you can d/l it change it back and view it? It seems when I RMB on a link and try to open it in a NEW TAB I get a chance to save it to disk or open it in a viewer (maybe the way my Firefox is setup though). If you can do this, the changing of extension should work.
