Date: Wed, 27 Feb 2002 17:30:44 +0100 From: "Bas v.d. Wiel" <bas@kompas-media.nl> To: <freebsd-questions@freebsd.org> Subject: SMB over IPSEC with filtered ports still possible? Message-ID: <LOEJICFDGCPPJOMJCJKDIEDECHAA.bas@kompas-media.nl>
next in thread | raw e-mail | index | archive | help
Hello everyone, This question may have been asked before, but I couldn't find any reference to my problem on google or in the archives. I'll soon be building a VPN between two locations of a small company. The main location uses fully open ADSL while the second location uses cable (residential service due to lack of alternatives) to access the net. This cable connection has its tcp port 139 filtered at the upstream router. I've read a few articles on VPN using IPSec on FreeBSD and I think I'll manage setting this up for mail and the like since those ports are unfiltered. The articles however don't mention any restrictions on either end of the pipe and how to deal with such a situation. I'd like to be able to have my Windows network clients browse and use resources on either side of the tunnel. With tcp port 139 being filtered on one end, and my ISP unwilling to remove the filter, I'm worried. Is there a way to circumvent this? Should I redirect port 139 to some high port between the gateways? My servers are all FreeBSD (4.5 RELEASE) running Samba 2.2.2 so it's possible to set the listening port differently on them, but will my Windows 2000 clients be able to adjust their ports as well? I've read something about changing lines in an inetd.conf-like file called 'services' inside Windows' main directory, but I have no such file. Should I create it myself and have it contain only exceptions from the defaults? Any help on this subject is very welcome. Thanks in advance, Bas v.d. Wiel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?LOEJICFDGCPPJOMJCJKDIEDECHAA.bas>