Desktop W-10 Pro can see Laptop W-10 Home.
Laptop see's Desktop but says: "This folder is empty.
This is with SMB 1 and 2 active, NETBIOS enabled
Private (current profile)
"Turn on network discovery" is checked
"Turn on automatic setup of network-connected devices" is checked
"Turn on file and printer sharing" is checked
Using Password, not Pin
Turned off Firewalls
Tried all the above standing on my head
Still no luck.
I'm a new member but have followed this old (by now) thread. And I thought I might help.
I have two wireless computers on my home network. Both Run WIndows 10 Home Edition. One is 64 bit. The other is 32 bit.
When I run File Manager on the 32 bit machine, under Network, it shows the 32 bit and 64 bit machines in the right-hand View pane and again under an expanded Network in the left-hand Folder pane. But when I do the same thing on the 64 bit machine it only displays itself - the 64 bit machine. Both are completely up-to-date in terms of Microsoft updates.
But here's the interesting bit - one that was touched on in a very early reply to this thread. On the 64 bit machine, if I enter the name of the 32 bit machine - as in "\\computer name\ - in File Manager's search bar and hit enter That computer shows up listed under an expanded Network in the left-hand Folder pane. But at the same time only the 64 bit machine shows up in the right-hand View pane. And I have full access to it through File Manager.
So, all this time the 64 bit machine has been seeing the 32 bit machine. But the only utility I've been using to 'see' the 32 bit computer was File Manager. Know what? I think there is something in the 64 bit File Manager that's making it not show all the networked computers. If there is another utility that comes with Win 10 please tell me.
Finally, if I right-click on the entry for the 32 bit machine I pinned it to Quick Access. So I never have to enter that name again.
I should add this fact. If another computer is in Sleep Mode it will not be seen - period.
Last edited by Dave Dave; 22 Feb 2016 at 17:41. Reason: errata
Nah, nothing to do with 64 bit File Manager. What you are seeing is the whole point of this thread - broken file discovery.
My bet is that the 32 bit comp is the master browser so sees everything. Run nbtstat -n and that will tell you which comp is the MB.
I tried nbtstat -n but the run box simply flashes for an instant. Can't get any feedback from that.
Absolutely right! We have always known this. However, 'discovery' is not working.
Pointing windows to a particular share is very different from asking windows to find/discover all shares.
I disabled HomeGroups on all the computers in my office network as soon as I realized upgrading to Windows 10 created a new and separate HomeGroup for each computer upgraded. I had only ever used WorkGroup. My only outstanding issue is that, when the newest desktop computer assumes the Master Browser role, the laptop doesn't connect network shares properly, or it reports that the shares haven't connected ... even though clicking them proves they are connected.
I did check the laptop, which is traditionally a client, both SMB1 and SMB2 are showing True when I obtain the current state by running Get-SmbServerConfiguration | Select EnableSMB1Protocol, EnableSMB2Protocol. Therefore, I'm not sure that the upgrade blows away SMB1. Honestly, I never heard the acronym before I found and posted to this thread.
Is your suggestion to disable SMB1 and SMB2, and then re-enable them?
marjwyatt, I pointed you to a very good thread in post #193. This thread discusses SMB protocol issues in detail. The issues we all see in the 1511 release is not fixable by us users. The next release will likely fix this discovery nightmare.
The later Insider releases do resolve the problem by using NetBIOS protocols but we don't know whether those solutions will be exactly what will be in the next general release, hopefully in March.
I came across this thread whilst searching the internet. I've read through all the posts till now, and noticed a few things no one has mentioned yet. I had the same problem in a company environment where seeing each other is paramount. It was pretty straight forward to resolve.
The steps are as follows:
1.) Directly under the C Drive, create a folder of any name (I shall call it "Shared" for convenience). Right-click, Properties, Sharing Tab, Advanced Sharing. Tick the box to share this folder, Click "Permissions", Tick the "Full Control" box for the Everyone user. Then click "Add". In the Dialog box that appears, there are 3 text boxes. The lower one of the 3 is headed by "Enter the object names to select". In that box, type in NETWORK and click "Check Names". The list that pops up should have 2 entries. Select the one named NETWORK and click "OK". Then click "OK" again to go back another window.
You will now have the Everyone user and the NETWORK user listed under your permissions window. Select the NETWORK user, and tick the "Full Control" check box for it as well. Click "Apply" and click "OK". Now you're back on the Advanced Sharing dialog box. Click "Apply" and click "OK" to accept all the settings you just made.
You're back in the Shared Properties dialog now. Click on the "Share..." button, and in the dialog box that opens, click the arrow that appears to the left of the "Add" button on hover over, select Everyone, and click "Add". In the same drop down box, you will notice that NETWORK isn't listed. Type NETWORK into the box, and click "Add" to manually add it. Now below where Everyone and NETWORK is listed as Read, change their permission level from Read to Read/Write if you so prefer. Click "OK" to accept all the settings made, and you will find yourself back at the Shared Properties dialog box.
At the bottom of that box, is a blue hyperlink to Network and Sharing Center. Click to open, and go through the entire list of items to make sure that "Password protected sharing" is turned OFF. Do this under Guest, Private, Home, or any other type of network you're currently connected to.
For good measure, restart the PC.