Try to set gateway for windows machines to 192.168.0.99 also - i think setting FW_SERVICE_SAMBA="yes" in Suse firewall is not enough, you have to enable/add in section 9 of /etc/sysconfig/SuSEfirewall2 FW_SERVICES_INT_TCP="137 139" FW_SERVICES_INT_UDP="137 139" if your winboxes are connecting to "internal" interface (e.g. eth1) of linux Ivan -----Original Message----- From: FX Fraipont [mailto:fxf@skynet.be] Sent: Saturday, January 04, 2003 3:26 PM To: suse Subject: Re: [SLE] no Samba server in network neighborhood Ivan Mojzis wrote:
Be sure you have on each win98 boxes correctly set-up TCP/IP protocol as default You can delete all protocols except tcpip. If you don't have dhcp daemon (server)
done already
you have to setup manualy win98 boxes - e.g.: linux has ip address 192.168.0.1 win98box1 - 192.168.0.10, netmask 255.255.255.0, gateway 192.168.0.1 ... win98box1 - 192.168.0.14, netmask 255.255.255.0, gateway 192.168.0.1
done already smb server 192.168.0.99 winboxes 192.168.0.98/7/6/5 I said that the network and samba were working properly, except for the samba server not appearing in network neighborhood.
also check if you have correctly set-up firewall (if any present).
Susefirewall 2. :FW_SERVICE_SAMBA="yes" So it must be something else.... Thanks anyway Fx -- ______________________ Courtesy of SuSE Linux nibz.org -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com __________ Informacia od NOD32 1.339 (20021230) __________ Tato sprava bola preverena systemom NOD32 pre Exchange. http://www.eset.sk