On Mon, 30 Aug 2004 16:13:03 -0400, Scot L. Harris wrote: > On Mon, 2004-08-30 at 15:46, Marc Williams wrote: > >> Well wha'dyaknow? I apparently stumbled upon the answer to my problem. >> I inserted: "domain master = yes" into smb.conf on the Samba server and >> things just started working. Here is my entire, working, smb.conf: >> >> > So all FC2 systems have to be configured as domain masters? I thought > that was for setting up a sever as a PDC. > I don't know, but I would doubt it. I have a feeling that in my case it works because I don't have any other PDC. > >> So it would seem that my Samba troubles are history, knock on wood. > > Was this working correctly when you had iptables active with that set of > ports cut through? > My iptables is part of IPCop firewall and is running on yet another Linux machine dedicated to firewalling the network so I never did have iptables running on the Samba server or any clients. What I did change on the IPCop machine though was to tweak some rules that I never before noticed needed tweaking. That's a side benefit, I suppose, of looking through lots of things trying to get Samba to work. But here's the relevant portion of those rules in case you're wondering (this might wrap and look like crap): /sbin/iptables -A CUSTOMINPUT -p tcp -s ! 192.168.0.0/16 --dport 135 -j DROP /sbin/iptables -A CUSTOMINPUT -p udp -s ! 192.168.0.0/16 --dport 135 -j DROP /sbin/iptables -A CUSTOMINPUT -p tcp -s ! 192.168.0.0/16 --dport 137 -j DROP /sbin/iptables -A CUSTOMINPUT -p udp -s ! 192.168.0.0/16 --dport 137 -j DROP /sbin/iptables -A CUSTOMINPUT -p tcp -s ! 192.168.0.0/16 --dport 139 -j DROP /sbin/iptables -A CUSTOMINPUT -p udp -s ! 192.168.0.0/16 --dport 139 -j DROP /sbin/iptables -A CUSTOMINPUT -p tcp -s ! 192.168.0.0/16 --dport 445 -j DROP /sbin/iptables -A CUSTOMINPUT -p udp -s ! 192.168.0.0/16 --dport 445 -j DROP
