Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I believe I have read in the past that mapping a drive over an ssh tunnel is not possible. However, if you use UltraVNC on both ends of the connection you can probably use its file transfer option.
Distribution: Mac OS X Leopard 10.6.2, Windows 2003 Server/Vista/7/XP/2000/NT/98, Ubuntux64, CentOS4.8/5.4
Posts: 2,986
Original Poster
Rep:
Quote:
Originally Posted by acid_kewpie
no, it's easy enough, done it a few times for smb / cifs drives at least. would be harder with nfs using portmapping and such.
Is there a guide you can point me to? The ones I have seen on Google talk about uninstalling the File and Print Sharing feature in Windows. I find that a little odd. How will this affect my file and print sharing with other computers in my LAN?
well smb shares are just port 445, if that's the port being tunnelled, then that's what you'll connect to at the other side. i assume there are complications with netbios logons and such, but basic stuff is simple.
I am using putty to create a tunnel to my samba machine at home
source port: 139
destination: localhost:139
on my home samba machine I have /shares folder - make sure the following ports are open on your linux machine .
netbios-ns 137/udp # NETBIOS Name Service
netbios-dgm 138/udp # NETBIOS Datagram Service
netbios-ssn 139/tcp # NETBIOS Session Service
microsoft-ds 445/tcp # Microsoft-DS
now once you login with putty to ur home machine run netstat -an and u should see:
tcp 0 0 0.0.0.0:139 0.0.0.0:* LISTEN
on ur work machine map a netwrok drive
drive : Q
folder: \\127.0.0.1\shares
connect using a different user:
username: the samba user name
password is the samba user password
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.