If you still want to use samba.service you could try:
$ cd /lib/systemd/system && ln -sf smbd.service samba.service
I don't know if the above command has side effects though.

It would be nice if the package name and service name matched, but
"service smbd status" works and I don't know systemd, so I will leave it
alone.

It is the safest approach, but you should familiorize yourself with
Systemd! :)

On 12/2/18 11:49 PM, john doe wrote:

Correction, 'ad-dc' is controled by the 'samba-ad-dc.service' and not
by the nmbd.service.

Ok.
But what do the error messages mean?

You can use samba in two ways:
- Active directory domain controller (1)
- Samba daemons and related services (smbd,nmbd,winbind) (2)
You either use one or the other.
Debian provides both possibilities that is why 'samba-ad-dc' is also
included but masked (see (3) for what "mask"ed means).
If you have a "small domain" and want to use the DC as a file server you
will still need winbind (not recommended by the samba team) (1).

Contacting the script maintainer directly has its benefits, but I
believe it would be best for me to use the issue tracking infrastructure
and start at the obvious beginning, so that people with more knowledge
and skill (like yourself) can better track and resolve the issue: