Can't see W10 machine in networking view but *can* map a network drive

Hello!

I've got two Windows 10(home) machines on the same LAN at my house. The NAS machine has a large HDD which I'd like to use a part of to relocate my Google Drive folder to(50GB!). Anyway, I have sharing turned on for the folder on the NAS machine, but that machine does not show up in file explorer when I click 'Network'. Oddly, I was able to map that folder and it works in the sense that I can transfer files from Machine 1 to the NAS.

I really need it to show up as part of the Windows network though, because Google Drive wants me to choose a destination, and I can't manually enter \\NAS\shared_folder.

I'm aware that this is likely an issue from a Windows update (1709 I think) where SMB 1.0 was removed. I have found ways to fix my problem using Group Policy Editor, but my Windows versions are both Home and that's not an option.

I have verified that File sharing is on, and Network discovery.

What can I do?

Hey burgertime,
On some NAS units you can change what SMB version it uses, so I would check that first and see if you can set it to SMBv2 or SMBv3. If you can't change the NAS SMB version, then you'll have to re-install the SMBv1 Client & Server on your W10 PC's - Enable or Disable SMB1 File Sharing Protocol in Windows | Windows 10 Tutorials

Note:
1. If you do re-install SMBv1, do not check the Automatic Removal.
2. You may only need SMBv1 Client, but don't quote me on that.

Eagle51 said:

Hey burgertime,
On some NAS units you can change what SMB version it uses, so I would check that first and see if you can set it to SMBv2 or SMBv3. If you can't change the NAS SMB version, then you'll have to re-install the SMBv1 Client & Server on your W10 PC's - Enable or Disable SMB1 File Sharing Protocol in Windows | Windows 10 Tutorials

Note:
1. If you do re-install SMBv1, do not check the Automatic Removal.
2. You may only need SMBv1 Client, but don't quote me on that.

Well it's option 2 for me then. My 'NAS' unit is nothing more than a headless, gutted tower Windows 10 Home machine.

So I would have reinstalled SMB1 by now but everywhere I read about SMB1 I am seeing that it's a big security vulnerability. Does that not apply to me since I'm just on a home network behind a router?

So I would have reinstalled SMB1 by now but everywhere I read about SMB1 I am seeing that it's a big security vulnerability. Does that not apply to me since I'm just on a home network behind a router?

SMBv1 was patched and on a home network the risk is very low IMO.

Well it's option 2 for me then. My 'NAS' unit is nothing more than a headless, gutted tower Windows 10 Home machine.

Before you re-install SMBv1 ... Check that the following Windows Services are running and their startup type is set to Automatic (Delayed Start) and see if your NAS/W10PC will show up.

Function Discovery Provider Host - Running | Startup Type Automatic (Delayed Start)
Function Discovery Resource Publication - Running | Startup Type Automatic (Delayed Start)

Note: It can take a couple of minutes for the PC's to show up in File Explorer > Network

Eagle51 said:

Before you re-install SMBv1 ... Check that the following Windows Services are running and their startup type is set to Automatic (Delayed Start) and see if your NAS/W10PC will show up.

Function Discovery Provider Host - Running | Startup Type Automatic (Delayed Start)
Function Discovery Resource Publication - Running | Startup Type Automatic (Delayed Start)

Note: It can take a couple of minutes for the PC's to show up in File Explorer > Network

One of the two worked. Not sure if it was SMB1 or not. I had already enabled the other two settings you recommended earlier in the day but hadn't checked before you posted that. All is working now - thanks!