On Fri, 2004-01-09 at 02:06, Andrew Robinson wrote: > dalen wrote: > > Andrew Robinson wrote: > > > >> I'm transitioning myself from Red Hat 9 to Fedora Core 1. I had Samba > >> working on RH9 for my home network. I haven't gotten there yet with > >> Fedora. When I try to access the disk shares from Windows 2000, I see > >> the server under the Workgroup in "My Network Places". When I > >> double-click on the server icon, I get an error dialog declaring > >> "\\Orpheus is not accessible. The network path was not found." > >> > >> I'll start looking for a Samba Howto. In the meantime, I thought I > >> would see if this error message meant anything specific to anyone on > >> the list. > >> > > I had a similar problem that turned out to be the firewall. I opened > > ports 137-139,445 in /etc/sysconfig/iptables, restarted iptables, and > > the problem went away. > > > > Knowing less about iptables than smb.conf and based on what I found in > the existing /etc/sysconfig/iptables, I added these two lines: > > -A RH-Firewall-1-INPUT -m state --state > NEW -m tcp -p tcp --dport 137:139 -j ACCEPT > -A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 445 -j > ACCEPT > > Are these the entries I _should_ add to iptables? > > Thanks! > > Andrew Robinson > You don't have to, and I don't think you should, include the state-option. First of all, why restrict on a connection being new, second, this can possibly stop the session after the first syn-package is sent, other than that it seems right... Sturla
