First, check the logs. If you've started the daemons, the message "smbd version
some_number started" should appear. If it doesn't, you will need to restart the Samba daemons.
If the daemon reports that it has indeed started, look out for "bind failed on port 139 socket_addr=0 (Address already in use)". This means another daemon has been started on port 139 (
smbd ). Also,
nmbd will report a similar failure if it cannot bind to port 137. Either you've started them twice, or the
inetd server has tried to provide a daemon for you. If it's the latter, we'll diagnose that in a moment.