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!
I am having the exact same issue on my Windows 10 system. Latest R7000 firmware. My Windows 7 system has no issues, nor does another Win10 system on my network.
The Win10 system in question can reach the other computer in the network listing in Explorer, but readyshare only by manually entering the \\readyshare address in the address bar.
I am also getting the 1231 error when running net view at the command prompt.
I noticed the behavior when upgrading from 1.0.7.12 to 1.0.9.14 and now .18.
Have not tried toggling UPnP.
Seems cosmetic at one level, since I can reach the other systems and network printers -- and even readyshare after a delay in explorer, but the network listing in explorer does not include readyshare or the printers. The only culprit left from my own digging on this issue is the router ... and it is quite frustrating.
Interesting...
EruvWeather wrote:I am having the exact same issue on my Windows 10 system. Latest R7000 firmware. My Windows 7 system has no issues, nor does another Win10 system on my network.
The Win10 system in question can reach the other computer in the network listing in Explorer, but readyshare only by manually entering the \\readyshare address in the address bar.
I am also getting the 1231 error when running net view at the command prompt.
I noticed the behavior when upgrading from 1.0.7.12 to 1.0.9.14 and now .18.
What is the difference between the W10 PC that works and the one that doesn't? At they the same? Same W10 version, same edition (Pro/Home)?
Although both rebooting the router and changing things like UPnP's state will make my W10 Home 1709 version work, it is only temporary.
EruvWeather, I am at a TOTAL loss here...
Before my wife got up I rebooted the router. Of course NET VIEW worked after that just fine. I went and had breakfast and for over an hour my PC say idle, and even the display and hard disk went to 'sleep'. Woke it up and ran NET VIEW:
C:\>net view
Server Name Remark
---------------------------------------
\\IRV8700 Irv's 8700
\\LARAINE-XPS8500
\\READYSHARE readyshare
The command completed successfully.
Still working, good. Since my wife's PC is now on I went to it since it is a W10 PRO. Surprise, it gets a 1231 error from NET VIEW!!!
This is all very confusing to me? We both have the same W10 release, 1709, and even similar h/w but one is HOME edition and the other PRO? I know you have similar results, one W10 PC works, the other doesn't?
I almost suspect some sort of 'connection' needs to be made between the router and PC when the router comes up or reboots? Once up and another PC comes on-line it will not work for that PC maybe? Might explain why when it was working fine one night before I shutdown it failed the next morning?
The PC must talk to the Router when it starts, if nothing else, to get its IP Address and Internet access. Hmm, this could be a large clue! Both of these PC's have a router assigned/reserved IP Address. Wonder if that could have something to do with it? On the one that fails for you, it is a reserved IP Address and the other isn't?
I wouldn't expect to see the actual words "NET VIEW" in a packet capture. It's just a Windows command. You certainly don't see "PING" in a ping packet, which is just an ICMP echo request.
224.0.0.252 is the address used for LLMNR (Link Local Multicast Name Resolution). It was designed by Microsoft and is very similar to mDNS. I found an interesting read on the controversy between LLMNR and mDNS. It seems that LLMNR has "lost" the battle with mDNS, but I guess Windows is still using it.
No idea what's going on with the ARP for 192.168.1.9. Perhaps there was a device at that address in the past.
As to why NET VIEW might be returning immediately with no traffic, it's likely that Windows is just returning cached results. You might consider re-running Wireshark and just capture everything. There could be some important exchanges going on via broadcast that might be filtered out with a "host 192.168.1.30" filter. You can always filter after a capture.
Yeah, that is why I don't know how to find the 'thread' for Net View, don't know what to look for? I'm sure there are other things going on at the same time too, as I see an e-mail check as well during that time.
mDNS, makes sense, saw some DNS requests...
As for 192.168.1.9, I might have had that many pool requests at one time but not now. Only 2 - 5 were assigned to active devices. Didn't see anything for 192.168.1.6/7/8 either? Makes no sense?
I created the capture with a filter "ip.addr == 192.168.1.30" and adding in the "host 192.168.1.30" didn't seem to shorten it?
I did read somewhere that NET VIEW will use a cache and it can be up to 25 minutes before a device is dropped out of the cache as it is renew after that time. Maybe that explains the fast trace in WireShark. Since NEW VIEW is still working and very fast, I suspect that the cache renew is not happening. Only when something on the LAN changes is it updated I suspect? Maybe the router signals that, I don't know.
I've uploaded NET_VIEW.JPG, it is the capture in case you want to look at it. D/L and change the extension to .pcapng and then use that to open WireShark.
At this point, I'm really thinking something is wrong with the firmware, especially since someone else also has this happening and working on one PC and not another.
Also the delay in opening the router in a browser that michaelkenward also has, is new, and doesn't always happen, but new with .20 for sure. Suspect a cache involved there too maybe?
I don't want to go too far back in firmware for fear of losing some security updates, and that supposed fix for the IP Address dropping on a RENEW of the IP Address which is happening often for me. Right now I'm sort of stuck. I do transfer files from my PC to the router USB drive often, and use Explorer++ to do that as I can select a file and drag it to the share folder on the router in the network, but if I can't see the network share in Explorer++ I can't do that. I know I can using NET USE assign a drive letter to the share, that works, just like NET VIEW \\readyshare, can then use Explorer++ for transfers... so I do have a work-around. Still, I think the firmware is involved and would like it fixed, as it did work before for a long time until recently.
NOTE/EDIT: I checked the file, d/l'ed it and changed the extension and then double clicked on it, opened WireShark and it is all there.
Both computers are running W10 Pro x64. I am thinking it may some sort of "master browser" issue, but it sure seems like the computer in question is just not refreshing the network list.
No reserved addressess. Everything is dynamic.
