[TriLUG] SMB with SSH Linux->Windows?

[Brian Weaver]

Michael,

I've got a really strange question, but if your running a Win32
machine will not some of those TCP/IP ports already be in use?
On my Win32 machine port 139 is already open and listening for
SMB request to that machine. Have you run a simple 'netstat -na'
on the local Win32 machine before you fire up SSH?

I'm betting that the Win32 environment already has some of those
resources in use. If so then you should probably setup a private
network between you Win32 box and the desired SAMBA server.

Weave

Michael Czeiszperger [czei at webperformanceinc.com] wrote:
> Has anyone ever managed to get a Linux Samba share visible to a remote 
> Windows box over ssh?
> 
> I'm trying to securely access my office's samba server from a home 
> VMware/Windows installation. (*)  Since I only need file sharing on the 
> windows box, and no other protocols, I thought that SSH would be easiest to 
> use. So far I've:
> 
> 1. Installed cygwin with ssh on Windows 2000.
> 
> 2. Turned on NETBIOS over TCP/IP.
> 
> 3. Executed the following on windows:
> ssh -v -L 137:remotehost:137 -L 138:remotehost:138 -L 139:remotehost:139 
> remotednsname.
> 
> 4. On the windows machine I can telnet to port 139 at 127.0.0.1, which is 
> correctly routed. I've also tried other ports, such as 143 for IMAP, and the 
> protocol worked fine.
> 
> 5. net use g: \\127.0.0.1\sharename gives "System error 67 has occurred. The 
> network name could not be found."
> 
> Any ideas for something to try. I looked at some other options, but the ones 
> I looked at were all for configuring Linux firewalls, while I'm using Linksys 
> firewalls on both sides...
> 
> Thanks for any help,
> 
> Michael Czeiszperger
> _______________________________________________
> TriLUG mailing list
> http://www.trilug.org/mailman/listinfo/trilug