"www' was in the default file. I added the 139. I am using Samba on my LAN and for VMware. Should I do this differently ? Brian Marr On Friday 04 October 2002 19:51, Togan Muftuoglu wrote:

* Brian Marr; on 04 Oct, 2002 wrote:

...

This is working for me - but you will need to check it with others who have more expertise. Brian Marr FW_SERVICES_EXT_TCP="www 139"

Offering netbies to the world ? bad practice

Hmmmmm I think I have got this config wrong somehow : ( The link below did not work here. Brian Marr On Friday 04 October 2002 20:29, Togan Muftuoglu wrote:

* Brian Marr; on 04 Oct, 2002 wrote:

...

"www' was in the default file. I added the 139. I am using Samba on my LAN and for VMware. Should I do this differently ?

default should be (and is ) empty. I suggest you have a closer look to the documentation. I can obly suggest it should be somewhere along the lines FW_SERVICES_INT_UDP. I would personally limit it only to specific IP's of the local LAN

There is a draft( meaning incomplete) howto for SuSEfirewall2 at http://dinamizm.ath.cx/articles/firewall2.pdf You may want to consider to have a look at that

Thanks for you prompting Togan. I have removed the offending rule. Am now running with FW_SERVICE_SAMBA="yes" and FW_SERVICES_INT_TCP="139" Samba seems to be working ok thus far. Brian Marr NB not sure about the link. KGhostview has not opened it yet. On Friday 04 October 2002 20:49, Togan Muftuoglu wrote:

* Brian Marr; on 04 Oct, 2002 wrote:

...

Hmmmmm I think I have got this config wrong somehow : ( The link below did not work here.

? you should be able to get that

wget http://dinamizm.ath.cx/articles/firewall2.pdf