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 wrote:
Ignore the ARP for 192.168.1.6 for now. It's a red herring.
NET_VIEW.JPG doesn't work. All I see is a tiny white square. Did you attach the right file?
Did you post Wireshark capture file somewhere? I don't see it.
You have to D/L the file and change .jpg to .pcapng, then it will work by double clicking on it wherever you did the D/L to. Worked for me when I tested it.
Oh, sorry. Ok, I can view it with Wireshark.
AFAICT, I can see standard NetBios Queries and responses. I also see a successful connection to READYSHARE. So, it looks good there.
I also see LLMNR queries, but no responses. As I mentioned earlier, LLMNR is kind of dead, so it's no great surprise that the router is ignoring them. Nor is there any harm.
The next bit is where NET VIEW comes into play. For reference, these two articles are pretty good at describing how the Windows Computer Browser service works:
Name Resolution and Browsing (look for Browsing in a Windows Network)
How Computer Browser Service Works
In the packet capture, you can see packets 56 and 58 are Computer Browser Service packets. Packet 56 is a Get Backup List Request from 192.168.1.30. This is a request to find a server that can provide the list of Windows servers on the network. Packet 58 contains a Get Backup List response from the Netgear, stating that READYSHARE is a server.
Now, it's my understanding that what should happen next is that 192.168.1.30 should contact the server (in this case READYSHARE) and ask for the list of Windows servers via a NetServerEnum request. It appears that 192.168.1.30 never does this. This might explain why the NET VIEW command is returning nothing. The command has nothing to display because the computer never sent a NetServerEnum request. Why? I don't know.
Anyway, it looks like the Computer Browser Service operates on 12 minute cycles. That is, every 12 minutes computers that have File Sharing enabled will announce their presence. You could run Wireshare through an entire 12 minute cycle and see what happens, although I'm not sure if a whole lot will be learned from it.
Both of my Win10 systems are up to v1709. The one with the issue is hard-wired into the router, the one not exhibiting the issue is connecting via WiFi on the 5GHz network.
Looking at that stuff and I almost get the feeling that there is a MASTER BROWSER problem? Look at https://social.technet.microsoft.com/Forums/en-US/bd0af6aa-51ec-477a-8c81-888a4e60bd94/master-browser-service-broken-after-creator-update?forum=win10itpronetworking, and from the 2nd post:
===
Hi,
As I understand it, the issue you are experiencing is: After Creator Update, Windows 10 cannot use "net view" to list other computers but itself. And only Master Browser server can list all computers.
1.In “Network and Sharing Center”, click “Change Advanced sharing settings”, turn on “network discovery”
2.In “Network and Sharing Center”, click “Change Adapter Settings”, go to NIC Properties\IPv4 Properties\Advenced\Wins tab, select “Enable NetBIOS over TCP/IP”
3.In Services console, ensure “Computer Browser” and “Workstation” services are running
4.Run “regedit” to open Registry Editor, navigate to “\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services \Browser\Parameters”, ensure the “MaintainServerList” is set to Yes or Auto
5.In the same location of registry, ensure that at least one computer in each subnet, has the “IsDomainMaster” REG_SZ key set as True.
After that, please wait for about 12 minutes and try “net view” again on these Windows 10 computers.
Also, please open the Network in Explorer, and check if computers will be listed in Network.
Hope it will be helpful to you
===========
Step #5 I don't have?
I did an NBTSTAT on READYSHARE
=========
C:\>nbtstat -a readyshare
Ethernet:
Node IpAddress: [192.168.1.30] Scope Id: []
NetBIOS Remote Machine
Name Table Name Type Status
---------------------------------------------
READYSHARE -00- UNIQUE Registered
READYSHARE -03- UNIQUE Registered
READYSHARE -20- UNIQUE Registered
☺☻__MSBROWSE__☻ -01- GROUP Registered
HOME -00- GROUP Registered
HOME -1D- UNIQUE Registered
HOME -1E- GROUP Registered
MAC Address = 00-00-00-00-00-00
===========
It pointed to my PC? Further more, I found this digging through some links, https://social.technet.microsoft.com/Forums/en-US/e105ef02-962e-437f-aaf3-ad3b533571fb/master-browser-not-working-for-non-windows-devices-in-build-1709-and-1703?forum=win10itpronetworking, which basically says Master Browser is NOT working (end of thread). Same link, post on Saturday, October 28, 2017 6:27 AM shows that the IsDomainMaster IS needed, so I added it.
I see packet 56 and 58, but the REAL question I have is 'WHO IS' Readyshare? See the NBTSTAT above, 192.168.1.30?
I ran a few NBTSTATS:
==========
C:\>nbtstat -a 192.168.1.1
Ethernet:
Node IpAddress: [192.168.1.30] Scope Id: []
NetBIOS Remote Machine Name Table
Name Type Status
---------------------------------------------
READYSHARE <00> UNIQUE Registered
READYSHARE <03> UNIQUE Registered
READYSHARE <20> UNIQUE Registered
☺☻__MSBROWSE__☻<01> GROUP Registered
HOME <00> GROUP Registered
HOME <1D> UNIQUE Registered
HOME <1E> GROUP Registered
MAC Address = 00-00-00-00-00-00
Bluetooth Network Connection:
Node IpAddress: [0.0.0.0] Scope Id: []
Host not found.
C:\>nbtstat -a readyshare
Ethernet:
Node IpAddress: [192.168.1.30] Scope Id: []
NetBIOS Remote Machine Name Table
Name Type Status
---------------------------------------------
READYSHARE <00> UNIQUE Registered
READYSHARE <03> UNIQUE Registered
READYSHARE <20> UNIQUE Registered
☺☻__MSBROWSE__☻<01> GROUP Registered
HOME <00> GROUP Registered
HOME <1D> UNIQUE Registered
HOME <1E> GROUP Registered
MAC Address = 00-00-00-00-00-00
Bluetooth Network Connection:
Node IpAddress: [0.0.0.0] Scope Id: []
Host not found.
C:\>nbtstat -a irv8700
Ethernet:
Node IpAddress: [192.168.1.30] Scope Id: []
Host not found.
Bluetooth Network Connection:
Node IpAddress: [0.0.0.0] Scope Id: []
Host not found.
============
They ALL except the last now point back to my PC, 192,168.1.30? Guess what, NET VIEW now returns the 1231 error? Looks like my PC is the Master Browser and hasn't got one as far as it thinks?
Very confused here, W10 bug???
IrvSp wrote:
Looking at that stuff and I almost get the feeling that there is a MASTER BROWSER problem? Look at https://social.technet.microsoft.com/Forums/en-US/bd0af6aa-51ec-477a-8c81-888a4e60bd94/master-browser-service-broken-after-creator-update?forum=win10itpronetworking, and from the 2nd post:
Further down in that thread, I found something that appears to explain it all.
SMB 1.0 is being discontinued or "deprecated". Totally reasonable, improves security.
The Computer Browser service is dependant on SMB 1.0, Microsoft have decided to remove the service rather than upgrade Computer Browser so the functionality remains. The result being Network Neighbourhood browsing is gone for Workgroups and users cannot so easily ascertain which PCs are available in the Workgroup.
So, there you have it. Network browsing is dead. And means NET VIEW, too.
