The following are steps for doing this (derived from this posting):įirst, add the Loopback Adapter to the Windows client machine: Thus, assuming that you will likely want to keep both your Windows and Samba shares, you will need to create a loopback device and tunnel port 139 to this new device.
If you have ‘File and Printer Sharing’ enabled for your network device, Windows will not allow you to tunnel from another source to the samba port 139 for that network device. We tunnel it through SSH to keep the connection secure. (see sshfs)įor Windows or Mac drive mapping, SSH is not enough Samba service is required. The option is likely available through the GUI if not, it is fairly easy to pull off in the terminal. If SSH tunneling is sluggish, try setting the compression level and/or cipher options.įor Linux (Redhat/CentOS/Fedora, Ubuntu, Debian), you can use SSH directly.
Ssh linux mac os update#
Update (): Hopefully newer OS versions make this process easier.
Ssh linux mac os mac os#
Tested on Windows XP-SP3/7, Linux (Redhat/Fedora, Ubuntu), and Mac OS (Snow Leopard 10.6). Problem: Mapping a remote network drive via SSH on Linux, Windows and Mac OS.