[Samba] DNS Help Request

[Rob Campbell]

I set up DC01 as the AD DC.  I set up DC02 as a member (or I was trying to
set it up as a member).  I did try to start the winbind service but it
didn't start.  If I don't need to start it, I won't.  I was trying anything
to get DC02 to register in DNS.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In all things, Be Intentional.


On Fri, Sep 9, 2022 at 11:46 AM Rowland Penny via samba <
samba at lists.samba.org> wrote:

> On Fri, 2022-09-09 at 10:52 -0400, Rob Campbell via samba wrote:
> > I was able to set up my DC using
> >
> https://wiki.samba.org/index.php/Setting_up_Samba_as_an_Active_Directory_Domain_Controller
> .
> > I followed
> >
> https://wiki.samba.org/index.php/Setting_up_Samba_as_a_Domain_Member#Preparing_the_Installation
> > to join a computer but there seems to be a problem with DNS.
>
> Why, if you have set up a DC, did you then follow a wiki page to set up
> a Unix domain member ?
> Or am I missing something ?
>
> >   My DHCP is my
> > router and I followed
> > https://www.server-world.info/en/note?os=Debian_11&p=samba&f=4 to
> > setup
> > winbind but I'm getting errors:
> >
> > journalctl -xe
> > Sep 09 10:01:16 DC01 systemd[1]: Starting Samba Winbind Daemon...
> > ░░ Subject: A start job for unit winbind.service has begun execution
> > ░░ Defined-By: systemd
> > ░░ Support: https://www.debian.org/support
> > ░░
> > ░░ A start job for unit winbind.service has begun execution.
> > ░░
> > ░░ The job identifier is 1824854.
> > Sep 09 10:01:17 DC01 systemd[1]: winbind.service: Supervising process
> > 1718403 which is not our child. We'll most likely not notice when it
> > exits.
> > Sep 09 10:02:47 DC01 systemd[1]: winbind.service: start operation
> > timed
> > out. Terminating.
> > Sep 09 10:02:47 DC01 systemd[1]: winbind.service: Killing process
> > 1718403
> > (winbindd) with signal SIGKILL.
> > Sep 09 10:02:47 DC01 systemd[1]: winbind.service: Killing process
> > 1718403
> > (winbindd) with signal SIGKILL.
> > Sep 09 10:02:47 DC01 systemd[1]: winbind.service: Failed with result
> > 'timeout'.
> > ░░ Subject: Unit failed
> > ░░ Defined-By: systemd
> > ░░ Support: https://www.debian.org/support
> > ░░
> > ░░ The unit winbind.service has entered the 'failed' state with
> > result
> > 'timeout'.
> > Sep 09 10:02:47 DC01 systemd[1]: Failed to start Samba Winbind
> > Daemon.
> > ░░ Subject: A start job for unit winbind.service has failed
> > ░░ Defined-By: systemd
> > ░░ Support: https://www.debian.org/support
> > ░░
> > ░░ A start job for unit winbind.service has finished with a failure.
> > ░░
> > ░░ The job identifier is 1824854 and the job result is failed.
> > Sep 09 10:02:47 DC01 samba[1718397]: [2022/09/09 10:02:47.165063,  0]
> > ../../source4/winbind/winbindd.c:46(winbindd_done)
> > Sep 09 10:02:47 DC01 samba[1718397]:   winbindd daemon died with exit
> > status 9
> > Sep 09 10:02:47 DC01 samba[1718397]: [2022/09/09 10:02:47.165370,  0]
> > ../../source4/smbd/service_task.c:36(task_server_terminate)
> > Sep 09 10:02:47 DC01 samba[1718397]:   task_server_terminate:
> > task_server_terminate: [winbindd child process exited]
> > Sep 09 10:02:47 DC01 samba[1718363]: [2022/09/09 10:02:47.168857,  0]
> > ../../source4/smbd/server.c:391(samba_terminate)
> > Sep 09 10:02:47 DC01 samba[1718363]:   samba_terminate:
> > samba_terminate of
> > samba 1718363: winbindd child process exited
>
> It looks like you have set up a Samba AD DC and then started winbind as
> a separate daemon instead of just letting the samba Daemon start it.
>
> If this isn't what you did, please explain exactly what you did.
>
> Rowland
>
>
>
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba
>