[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Tunneling SMB (139) through SSH



Matthew Kopishke wrote:

I'm not sure if this is exactly a firewall question, but this list seem like the best place to ask the question.

Here's the problem, our ISP has blocked off port 139 on all the routers (for security reasons) and refuses to open it back up. We (a school district) run software for our lunch program, serving line to be exact. This software has one major flaw (and a bunch of minor ones too) in that it runs off an access database that the software has to accessed locally, ie through a windows share. See the problem?

The solution I came up with is to tunnel port 139 via ssh to the server where the data is stored. It works great using OpenSSH on my Mac (OS 10.3, kind of ironic really), it seems to work fine on an XP machine, but it will not work on the Windows 98 machines that I desperately need to get running. I've uninstalled file and printer sharing, and I've also tried not logging into the windows network (just windows login) but when ever I go to access //127.0.0.1/<sharepoint> I get "The network name cannot be found.".

I guess that editing the c:\windows\lmhosts file would solve your problem.
AFAIK win98 must use lm-names and cannot resolve ip-numbers.
(To be clear: lmhosts: "pooter   127.0.0.1" and use "\\pooter\sharepoint")

I also guess that you already checked that windows is not binding on port 139 even if you remove the sharing?
Please let me know if it works.



Does anyone see any gotchyas in there? The other thing is I have a linux firewall in each building, so if some one has a better idea using them I'm all ears!

Thanks,

Matt

Best regards
Martin




Reply to: