Re: [Samba] Upgraded > Samba no longer listening on 192.168.0.x
- Date: Wed, 17 May 2017 12:58:10 +0200
- From: Marc Muehlfeld via samba <samba@xxxxxxxxxxxxxxx>
- Subject: Re: [Samba] Upgraded > Samba no longer listening on 192.168.0.x
Am 17.05.2017 um 12:17 schrieb Winfried via samba:
Samba runs as a stand-alone server at home, ...
> Notice the "At this time the 'samba' binary should
> only be used for either" at the end:
> ...> May 17 12:03:30 debian samba: At this time the 'samba'
only be used for either:
May 17 12:03:30 debian samba: 'server role = active directory domain
controller' or to access the ntvfs file server with 'server services = +smb'
or the rpc proxy with 'dcerpc endpoint servers = remote'
May 17 12:03:30 debian samba: You should start smbd/nmbd/winbindd
instead for domain member and standalone file server tasks
May 17 12:03:30 debian samba: [2017/05/17 12:03:30.650724, 0]
May 17 12:03:30 debian samba: STATUS=daemon failed to start: Samba
detected misconfigured 'server role' and exited. Check logs for details,
And I notice that Samba mentions "samba-ad-dc" when running the init.d
root@debian:~# /etc/init.d/samba restart
[ ok ] Restarting nmbd (via systemctl): nmbd.service.
[ ok ] Restarting smbd (via systemctl): smbd.service.
[ ok ] Restarting samba-ad-dc (via systemctl): samba-ad-dc.service.
This is not a Samba problem. It looks like the update enabled a systemd
service that starts the "samba" binary - which is the Samba AD DC.
Because your config is not for a DC, Samba logs this error.
* Disable the samba and samba-ad-dc services
* Enable the nmbd and smbd services
To unsubscribe from this list go to the following URL and read the