On Mon, Oct 11, 2021 at 2:19 PM Rowland Penny via samba <samba at lists.samba.org> wrote:> > # systemctl start smbd nmbd winbind > > Failed to start smbd.service: Unit smbd.service is masked. > > Failed to start nmbd.service: Unit nmbd.service is masked. > > Failed to start winbind.service: Unit winbind.service is masked. > > Unmask 'winbind', but you shouldn't start Samba until you have joined > the domain.I wonder why these are masked. On a stock Debian install, if you are installing a domain controller (not a member), then you should: systemctl stop smbd nmbd winbind systemctl disable smbd nmbd winbind systemctl mask smbd nmbd winbind systemctl unmask samba-ad-dc systemctl enable samba-ad-dc Did the OP follow directions for a DC? I'm seeing names like "FSDC" which sounds like OP is confused.
On Mon, 2021-10-11 at 14:29 -0400, Jonathon Reinhart wrote:> On Mon, Oct 11, 2021 at 2:19 PM Rowland Penny via samba > <samba at lists.samba.org> wrote: > > > # systemctl start smbd nmbd winbind > > > Failed to start smbd.service: Unit smbd.service is masked. > > > Failed to start nmbd.service: Unit nmbd.service is masked. > > > Failed to start winbind.service: Unit winbind.service is masked. > > > > Unmask 'winbind', but you shouldn't start Samba until you have > > joined > > the domain. > > I wonder why these are masked. On a stock Debian install, if you are > installing a domain controller (not a member), then you should: > > systemctl stop smbd nmbd winbind > systemctl disable smbd nmbd winbind > systemctl mask smbd nmbd winbind > systemctl unmask samba-ad-dc > systemctl enable samba-ad-dc > > Did the OP follow directions for a DC? > > I'm seeing names like "FSDC" which sounds like OP is confused.Your confused, I have been confused for some time, I did mention that having 'DC' in a hostname sounds like it is a DC. The OP assures that it isn't a DC, but I am not convinced :-/ Rowland
The Debian DC DC01 seems to be just fine. I have no issues with that. FSDC02 is Fedora Server which I was told could be a member or a standalone server. I want to use it as a member. It seems that I am able to join it as a member but the DNS is not registering. FSDC02 was test-server.lan before I was told that I needed to use Debian as the first DC. So I changed test-server.lan to FSDC02 and removed the samba configuration I had successfully running on it as a standalone file server, created a Debian vm, changed test-server.lan to fsdc02 and set Debian to DC01.test-server.lan. I then went through the wiki for Samba as an AD DC. Once that was working as expected I started working on setting fsdc02 up as a member. I can rename it to FS01 for clarity but last time I had a problem removing but I can try it again. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ In all things, Be Intentional. On Mon, Oct 11, 2021 at 2:30 PM Jonathon Reinhart via samba < samba at lists.samba.org> wrote:> On Mon, Oct 11, 2021 at 2:19 PM Rowland Penny via samba > <samba at lists.samba.org> wrote: > > > # systemctl start smbd nmbd winbind > > > Failed to start smbd.service: Unit smbd.service is masked. > > > Failed to start nmbd.service: Unit nmbd.service is masked. > > > Failed to start winbind.service: Unit winbind.service is masked. > > > > Unmask 'winbind', but you shouldn't start Samba until you have joined > > the domain. > > I wonder why these are masked. On a stock Debian install, if you are > installing a domain controller (not a member), then you should: > > systemctl stop smbd nmbd winbind > systemctl disable smbd nmbd winbind > systemctl mask smbd nmbd winbind > systemctl unmask samba-ad-dc > systemctl enable samba-ad-dc > > Did the OP follow directions for a DC? > > I'm seeing names like "FSDC" which sounds like OP is confused. > > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/options/samba >