|
[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]
|
Re: [PLUG] SMB + FC3 = GRRRRR!
|
Can you just try clearing all your firewall rules and seeing if
that has any effect? I don't know the requirements well enough to know if
the stuff listed below is right or not.
Aaron
On Mon, 16 May 2005 jazzman@exdomain.org wrote:
> When I do a "ps aux| grep mbd" I get:
>
> root 15012 0.0 2.3 10108 2720 ? Ss 20:42 0:00 smbd -D
> root 15013 0.0 2.2 10108 2700 ? S 20:42 0:00 smbd -D
> root 15017 0.0 1.6 8752 1952 ? Ss 20:42 0:00 nmbd -D
>
> So it appears nmbd is running, and when I do an "/sbin/iptables -L" I get:
>
> [root@vault marc]# /sbin/iptables -L
> Chain INPUT (policy ACCEPT)
> target prot opt source destination
> RH-Firewall-1-INPUT all -- anywhere anywhere
>
> Chain FORWARD (policy ACCEPT)
> target prot opt source destination
> RH-Firewall-1-INPUT all -- anywhere anywhere
>
> Chain OUTPUT (policy ACCEPT)
> target prot opt source destination
>
> Chain RH-Firewall-1-INPUT (2 references)
> target prot opt source destination
> ACCEPT all -- anywhere anywhere
> ACCEPT icmp -- anywhere anywhere icmp any
> ACCEPT ipv6-crypt-- anywhere anywhere
> ACCEPT ipv6-auth-- anywhere anywhere
> ACCEPT udp -- anywhere 224.0.0.251 udp dpt:5353
> ACCEPT udp -- anywhere anywhere udp dpt:ipp
> ACCEPT all -- anywhere anywhere state
> RELATED,ESTABLISHED
> ACCEPT tcp -- anywhere anywhere state NEW tcp
> dpt:http
> ACCEPT tcp -- anywhere anywhere state NEW tcp
> dpt:https
> ACCEPT tcp -- anywhere anywhere state NEW tcp
> dpt:ssh
> ACCEPT tcp -- anywhere anywhere state NEW tcp
> dpt:smtp
> ACCEPT tcp -- anywhere anywhere state NEW tcp
> dpt:135
> ACCEPT tcp -- anywhere anywhere state NEW tcp
> dpt:136
> ACCEPT tcp -- anywhere anywhere state NEW tcp
> dpt:netbios-ns
> ACCEPT tcp -- anywhere anywhere state NEW tcp
> dpt:netbios-dgm
> ACCEPT tcp -- anywhere anywhere state NEW tcp
> dpt:netbios-ssn
> REJECT all -- anywhere anywhere reject-with
> icmp-host-prohibited
>
> So everything there looks ok (though I thought I had opened UDP as well
> for the netbios ports... could that be the issue?)
>
> If I use nmblookup from VAULT to look up ANY host (including itself) I get
> an error about name_entry not being found by broadcast.
>
> Thanks
> Marc
>
> ___________________________________________________________________________
> Philadelphia Linux Users Group -- http://www.phillylinux.org
> Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce
> General Discussion -- http://lists.phillylinux.org/mailman/listinfo/plug
>
___________________________________________________________________________
Philadelphia Linux Users Group -- http://www.phillylinux.org
Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce
General Discussion -- http://lists.phillylinux.org/mailman/listinfo/plug
|
|