From owner-freebsd-stable Fri Aug 18 3: 1:16 2000 Delivered-To: freebsd-stable@freebsd.org Received: from ipamzlx.physik.uni-mainz.de (ipamzlx.Physik.Uni-Mainz.DE [134.93.180.54]) by hub.freebsd.org (Postfix) with ESMTP id DE13537B423; Fri, 18 Aug 2000 03:01:04 -0700 (PDT) Received: from ipamzlx.Physik.Uni-Mainz.DE (ipamzlx.Physik.Uni-Mainz.DE [134.93.180.54]) by ipamzlx.physik.uni-mainz.de (8.9.3/8.9.3) with ESMTP id MAA02192; Fri, 18 Aug 2000 12:03:24 +0200 (CEST) (envelope-from ohartman@ipamzlx.physik.uni-mainz.de) Date: Fri, 18 Aug 2000 12:03:24 +0200 (CEST) From: "O. Hartmann" To: freebsd-questions@freebsd.org Cc: freebsd-stable@freebsd.org Subject: SAMBA and IP filtering Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is anybody out here who has IP filtering (IPFIREWALL) on and has still full SAMBA access via NT clients? I have the following problem: IP filtering is enabled and working well on our FBSD 4.1 box running samba. One of the first rules is to allow all traffic from and to the server via the local network, that means no restrictions. With many services this runs well - but not for SAMBA! When trying to access a ip-filtering SAMBA server, I see its icon in the network neightborhood environment, but when clicking on its icon, I get the error message "Access denied, network path not found" after a while. Stopping Ip-filtering solves the problem, but that is not the right solution, I think. My question is, how to solve this problem. Many, many thanks in advance, Gruss O. Hartmann ------------------------------------------------------------------- ohartman@ipamzlx.physik.uni-mainz.de Klimadatenserver des IPA, Universitaet Mainz Netzwerk- und Systembetreuung To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message