That’s networking samba if you please.
Weighing the options took a while. I have a full desktop PC which would be my primary source for files to be backed up, but that uses a lot of power so it’s not practical as a nas. I had a few hard drives as options. I have a raspberry pi currently configured as a Google cloud printer.
I started with the desktop and the raspberry. I was going through the setup meeting a few roadblocks where the desktop, running Windows 10, couldn’t see any of the other devices on the network. I had a Kodi setup and a Linux laptop that could see the Desktop files, but the desktop saw nothing either automatically or manually.
And I had a WAP (wireless access point)
bridge that might possibly do something. [see this previous article].
The web searches indicated a nas wasn’t supported in bridge mode. But, I tried anyway and I’m glad I did. The hard drive appeared available to everything, except the Windows 10 desktop. If I browsed with Chrome on the IP address, it sent me to a “Twonky” session, which I am no fan of and it didn’t have the functionality I was looking for.
Frustration led me back to the web. And then I had a light bulb moment.
I was taking it for granted that Windows was configured correctly to support nas file access across a network. And yet none of the forums or blogs mentioned this incredibly simple and basic thing related to Windows 10 (W10). I decided to check the features in W10.
Open Control Panel → Programs and Features → Turn Windows
Features On or Off → search the list and click:
1.0/CIFS File Sharing Support
Network Management Protocol – and anything under it [WMI SNMP
Once that was done, when I opened up the Network option under file manager for W10, everything I had hoped for showed up. Problem solved. Samba was online and file transfers between the NAS and other resources worked fine.
Lesson learned: Never take it for granted everything is already configured and just going to work.