I'd imagine its something to do with the order in which your smb/nmb services are starting. Perhaps they are trying to start before the network interfaces are active or suchlike, i.e at too low a runlevel. Try setting them such that they only start at runlevel 3 (console multi-user on redhat) and above ...
/sbin/chkconfig --level 345 smb on
/sbin/chkconfig --level 345 nmb on
If you're <not> running Redhat, find out the correct runlevels for your distribution and do something similar. For example, with Suse the equivalent runlevels to redhat's 3 (Multi-user console) & 5 (X-Gui) are 2 & 3. With Suse you'd use 'rctab -l' to list runlevels and 'rctab -e' to edit. You may also be able to do it with Yast/Yast2 but I'm not too sure..
it worked
btw:
the daemons were "started" after initializing any network interfaces
and i think in runlevel 3 as the messages about started services appeared after message "entering runlevel 3" or something similar to that
I had the same problem! Followed advice to look in the samba log files
/var/log/samba/log.smb (and log.nmb)
There was "can't find host qwert.domain" I changed the host name in /etc/host file to qwert.domain and away it went!
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.