In this setup, one machine acts as an SMB/Samba Server and the other as an SMB/Samba client. There are other possible filesystems (such as NFS) but they are not native to Windows, unlike SMB/Samba which is the native Windows network file sharing protocol. To my mind, it is easier to have Windows act as the server since Windows can do that anyway - rather than install and configure sharing software on your Pi. It doesn't make any difference which machine is the server and which is the client really, so let's set up Windows as the server and the Pi as the client so you don't need to install any extra software anywhere.Ĭreate a shared folder with very insecure permissions until you get set up and working properly - you can always close things down and tighten things up later. So you choose a folder to share, right-click on it and choose "Share" and then set it up for sharing - with loose permissions.Īs an alternative, you can do this at the command prompt: NET SHARE sharename=drive:pathĬheck that Windows is indeed sharing a folder when you are done. Now mount the shared directory so it appears on the Pi: sudo mount -t cifs -o username=username,password=password //WINDOWS_IP_ADDRESS/share-name /WINDOWS NET SHAREĬreate a mount point where you would like the Windows files to appear: sudo mkdir /WINDOWS There is no point doing anything on your Raspberry Pi until the following command shows you are sharing a folder from the Windows side. If you want to unmount the shared directory: sudo umount /WINDOWS You should now see all your Windows files in /WINDOWS and you should be able to put files there and see them from your Windows machine You can also use the Windows machine name rather than its IP address.
0 kommentar(er)
