On Friday 29 September 2006 5:23 pm, Darryl Gregorash wrote:
On 28/09/06 18:20, Paul Abrahams wrote:
I thought I had solved the problem of Samba access within my LAN by setting FW_TRUSTED_NETS to 192.168.0.0/24. I don't know now why that seemed to be the case, but right now I have FW_TRUSTED_NETS set to that value and Samba access is being blocked (the other machine shows a request for username/password that can't be satisfied). Turning off the firewall makes Samba work again on the far end.
If it is possible, please set FW_TRUSTED_NETS to just 192.168.0.0/24, restart the firewall, and then run:
iptables-save
The results of this should tell us what is going on.This should work without having to specify a bunch of protocol/port options.
That's in an earlier post. I just discovered another strange thing. With the firewall on and with FW_TRUSTED_NETS set to 192.168.0.0/24, Windows machines get an access error if they try to look at the Samba shares. However, Linux machines can see those same shares. With firewall off, everyone sees the Samba shares. Paul