Retroceda um nível de serviço. A solução é:
service samba start
não é possível iniciar o samba
root@callserver:~# service smbd start
Job for smbd.service failed because the control process exited with error code. See "systemctl status smbd.service" and "journalctl -xe" for details.
root@callserver:~# systemctl status smbd.service
* smbd.service - Samba SMB Daemon
Loaded: loaded (/lib/systemd/system/smbd.service; disabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Mon 2018-10-15 16:25:48 +06; 6s ago
Docs: man:smbd(8)
man:samba(7)
man:smb.conf(5)
Process: 21859 ExecStart=/usr/sbin/smbd $SMBDOPTIONS (code=exited, status=1/FAILURE)
Main PID: 21859 (code=exited, status=1/FAILURE)
Oct 15 16:25:48 callserver systemd[1]: Starting Samba SMB Daemon...
Oct 15 16:25:48 callserver smbd[21859]: [2018/10/15 16:25:48.560635, 0] ../source3/smbd/server.c:1704(main)
Oct 15 16:25:48 callserver smbd[21859]: server role = 'active directory domain controller' not compatible with running smbd standalone.
Oct 15 16:25:48 callserver smbd[21859]: You should start 'samba' instead, and it will control starting smbd if required
Oct 15 16:25:48 callserver systemd[1]: smbd.service: Main process exited, code=exited, status=1/FAILURE
Oct 15 16:25:48 callserver systemd[1]: Failed to start Samba SMB Daemon.
Oct 15 16:25:48 callserver systemd[1]: smbd.service: Unit entered failed state.
Oct 15 16:25:48 callserver systemd[1]: smbd.service: Failed with result 'exit-code'.