For ‘Destination’, enter ‘localhost:139′. For ‘Source port’, enter ‘10.0.0.1:139′ (replacing IP as needed if a different loopback address was chosen before in step 13).Enable two boxes “Don’t start a shell or command at all” and “Enable Compression”.Using the configuration window on the left, navigate to Connection > SSH.
![mac network drive write accees mac network drive write accees](https://ag.montana.edu/it/support/images/connect-to-server.png)
Restart you computer (even though Windows does not prompt for this step).Click the ‘Advanced’ button and on the ‘WINS’ tab.This will be the IP of your loopback adapter make note of it for later. Enter ‘10.0.0.1′ for ‘IP address’ (or any other valid and unused local address: 10.x.x.x, 172.16.x.x, and .x).Highlight ‘Internet Protocol (TCP/IP)’ and click the ‘Properties’ button.Uncheck all items listed except for ‘Internet Protocol (TCP/IP).Open the adapters properties dialogue (Start > Control Panel > Network Connections and then right click on the adapter and choose properties).For ‘Network Adapter’ choose ‘Microsoft Loopback Adapter’.Under ‘Manufacturer’ you want ‘Microsoft’.Now choose ‘Install the hardware that I manually select from a list (Advanced)’.Scroll to the bottom of the ‘Installed hardware’ list box and choose ‘Add new hardware device’.Choose ‘Yes, I have already connected the hardware’.Click next and wait for search to conclude nothing was found.Open up the Add Hardware control panel (Start > Control Panel > Add Hardware).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.
![mac network drive write accees mac network drive write accees](https://www.stratospherix.com/img/guides/mac_prefs_02.png)
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.
![mac network drive write accees mac network drive write accees](https://i.ytimg.com/vi/7mx2XOFBp8M/maxresdefault.jpg)
(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.
#Mac network drive write accees update
Update (): Hopefully newer OS versions make this process easier.
#Mac network drive write accees 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.