[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [suse-security] SuSEfirewall 2 configuration - computer name problem

Hi Andy,

Perhaps your settings in "/etc/sysconfig/SuSEfirewall2" are not right.

# 9.)
# Common: smtp domain
FW_SERVICES_EXT_TCP="ssh 139 ..."

# Common: domain
FW_SERVICES_EXT_UDP="domain 139 ..."
# Common: domain

# 12.)
# set to "yes" if this server is running a samba server. You still have to # open the tcp port 139 to allow remote access to SAMBA.

# 22.)
# Allow/Ignore IP Broadcasts?
# If set to yes, the firewall will not filter broadcasts by default. # This is needed e.g. for Netbios/Samba, RIP, OSPF where the
broadcast # option is used. # If you do not want to allow them however ignore the annoying log entries, # set FW_IGNORE_FW_BROADCAST
to yes. # # Choice: "yes" or "no", if not set defaults to "no" # FW_ALLOW_FW_BROADCAST="yes" FW_IGNORE_FW_BROADCAST="yes"

-----Original Message-----
From: Andrei Bintintan [mailto:klodoma@xxxxxxxxx] 
Sent: Saturday, October 18, 2003 8:08 PM
To: suse-security@xxxxxxxx
Subject: [suse-security] SuSEfirewall 2 configuration - computer name problem


I saw there was a little discuttion about suse firewall and samba, but I have another problem here.

First of all I'm new in linux, so sorry if I ask stupid things... everyone has to learn right?

I have a server in LAN which is web, mail, db server. Samba is also installed. Everything worked fine, but when I activate suse
firewall I cannot see the computer name anymore. I have access with samba, I can ping the server but only with the IP address of the
server, not with the name. Shortly the server name is not recognized anymore. I waste a lot of time with this... and I couldn't find
the problem. The strange part is that I installed the same configuration under vmware and it works fine. I activated port 53 (domain
name) but still doesn't work.

Please advise. 

Thanx in advance. 


Check the headers for your unsubscription address
For additional commands, e-mail: suse-security-help@xxxxxxxx
Security-related bug reports go to security@xxxxxxx, not here