The configuration file (/etc/sysconfig/SuSEfirewall2) has inside lots of comments that explains what each option does. Did you read it?
Yep. When Yast failed I read it and tried everything I could before restoring my backup SuSEfirewall2 script and starting this thread. I get the bit about FW_TRUSTED_NETS="192.168.1.4/32" opening all ports but strangely enough after I did that it only used 139 and finally connected with the firewall running. Security wise it doesn;t matter since it's just a NAS sitting beneath my televisor and it's behind my wireless router firewall anyway. I'm just so glad I don't have to use Samba in the workplace. It seems so unpredictable. But then so does SuSEfirewall2. I'm disillusioned that something as simple as this has taken so long to understand. BTW my NAS is a T50 from the Gallegos. It's a great idea but crippled by bugs in Busybox, out of date firmware, processor and lack of memory. For the price I could have got a little Acer with an hdmi port, AMD 64, 1024 memory and avoided all this Samba nonsense. They even look good too. Caveat E. Cheers and thanks for all your patience. L x -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org