It looks to me that this network ports are not the problem. For testing I changed the portnumbers to +1000 smb.cnf: smb ports = 1139 1445 This doesn't change anything in the problem On 29/12/09 11:09, Josef Karliak wrote:
Hi, I don't know how in suse firewall, but in me used firewall Shorewall if it is shorewall stopped or crashed, no traffic is alowed (security reason). Except exception in the configuration of shorewall - "routesstoped". Did you tried to "nmap" your machine's open ports ? Or "netstat" ? Seems like some daemon is running on samba port (or samba is not fully stopped) J.K.
Hans de Faber píše v Út 29. 12. 2009 v 10:38 +0100:
On 29/12/09 10:31, Bogdan Cristea wrote:
On Tuesday 29 December 2009 11:06:58 Hans de Faber wrote:
On my fresh installed OpenSuse KDE system I tried to startup Samba for the first time.
Samba was not accessible by the webinterface (localhost:901). I get this error in logsmbd:
[2009/12/29 09:56:02, 0] smbd/server.c:1065(main) smbd version 3.4.2-1.1.3.1-2229-SUSE-SL11.2 started. Copyright Andrew Tridgell and the Samba Team 1992-2009 [2009/12/29 09:56:03, 0] smbd/server.c:457(smbd_open_one_socket) smbd_open_once_socket: open_socket_in: Address already in use
Where should I look for this problem, I can't find it.
Another question how should I start and stop Samba from the commandline. Its now started on bootup.
For Samba server configuration it's easier to use the yast module. You need also to enable samba browsing from Firewall configuration module.
In the firewall there are only 2 sambamodules sambaserver and sambaclient.
Stopping the firewall has no effect !
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org