[Samba] Unable to join domain

[Rob Campbell]

Made a lot of progress but:
net ads join -U administrator
Enter administrator's password:
Using short domain name -- DC01
Joined 'FSDC02' to dns domain 'dc01.test-server.lan'
DNS Update for fsdc02.test-server.lan failed: ERROR_DNS_UPDATE_FAILED
DNS update failed: NT_STATUS_UNSUCCESSFUL

Does this mean there is a problem somewhere?

The first DC is 10.0.0.13 dc01.test-server.lan

This server is 10.0.0.10

The two guides I used are
https://wiki.samba.org/index.php/Setting_up_Samba_as_an_Active_Directory_Domain_Controller
for 10.0.0.13 and
https://wiki.samba.org/index.php/Setting_up_Samba_as_a_Domain_Member for
10.0.0.10.  I'm stuck on 'net ads join -U administrator' on
https://wiki.samba.org/index.php/Setting_up_Samba_as_a_Domain_Member for
10.0.0.10

systemctl start smbd nmbd winbindd
Failed to start smbd.service: Unit smbd.service is masked.
Failed to start nmbd.service: Unit nmbd.service is masked.
Failed to start winbindd.service: Unit winbindd.service not found.

wbinfo --ping-dc
could not obtain winbind interface details: WBC_ERR_WINBIND_NOT_AVAILABLE
could not obtain winbind domain name!
checking the NETLOGON for domain[] dc connection to "" failed
failed to call wbcPingDc: WBC_ERR_WINBIND_NOT_AVAILABLE


[Sun Oct 10 23:09:28] [root at fsdc02~$] nslookup dc1.dc01.test-server.lan
Server: 10.0.0.13
Address: 10.0.0.13#53

Name: dc1.dc01.test-server.lan
Address: 10.0.0.13

[Sun Oct 10 23:09:46] [root at fsdc02~$] nslookup 10.0.0.13
13.0.0.10.in-addr.arpa name = test.dc01.test-server.lan.

[Sun Oct 10 23:09:53] [root at fsdc02~$] nslookup
> set type=SRV
> _ldap._tcp.dc01.test-server.lan
Server: 10.0.0.13
Address: 10.0.0.13#53

_ldap._tcp.dc01.test-server.lan service = 0 100 389
dc1.dc01.test-server.lan.
> exit

[Sun Oct 10 23:11:07] [root at fsdc02~$] host -t SRV
_ldap._tcp.dc01.test-server.lan
_ldap._tcp.dc01.test-server.lan has SRV record 0 100 389
dc1.dc01.test-server.lan.
[Sun Oct 10 23:11:18] [root at fsdc02~$] getent hosts MI
[Sun Oct 10 23:11:36] [root at fsdc02~$] getent hosts DC1
10.0.0.13       DC1.dc01.test-server.lan



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


On Sat, Oct 9, 2021 at 10:11 AM Rob Campbell <robcampbell08105 at gmail.com>
wrote:

> >> # nslookup 10.0.0.13
> >> ** server can't find 13.0.0.10.in-addr.arpa: NXDOMAIN
> >>
> >> # samba-tool dns zonecreate 10.0.0.13 0.0.10.in-addr.arpa -U
> >> Administrator
> >> Password for [DC01\Administrator]:
> >> ERROR(runtime): uncaught exception - (9609,
> >> 'WERR_DNS_ERROR_ZONE_ALREADY_EXISTS')
> >>   File "/usr/lib/python3/dist-packages/samba/netcmd/__init__.py",
> >> line 186, in _run
> >>     return self.run(*args, **kwargs)
> >>   File "/usr/lib/python3/dist-packages/samba/netcmd/dns.py", line
> >> 735, in run
> >>     res = dns_conn.DnssrvOperation2(client_version, 0, server, None,
>
> > You cannot create something that already exists.
>
> I was showing that it already exists but it doesn't resolve.
>
> >> On top of that, samba keeps crashing:
> >> daemon.log:
> >> 11161 Oct  8 22:15:24 DC1 systemd[1]: Starting Samba SMB Daemon...
> >> 11162 Oct  8 22:15:24 DC1 smbd[27618]: [2021/10/08 22:15:24.956122,
> >>  0] ../../source3/smbd/server.c:1851(main)
> >> 11163 Oct  8 22:15:24 DC1 smbd[27618]:   server role = 'active
> >> directory domain controller' not compatible with running smbd
> >> standalone.
>
> > Are you attempting to start the smbd binary yourself ?
> > you should just start the samba binary and that will start the smbd &
> > winbind binaries.
>
> I was showing that I can't start the service and when I did start the
> binary, it stopped for some reason.
>
> > You appear to be running systemd-timedated as well, stop it, it isn't
> > compatible with a Samba AD DC.
>
> It was already stopped.  When I disabled the service, it actually started
> so I stopped it again.
>
> [Sat Oct 09 09:56:22] [root at DC1/var/log$] systemctl status
> systemd-timedated
> ● systemd-timedated.service - Time & Date Service
>      Loaded: loaded (/lib/systemd/system/systemd-timedated.service; static)
>      Active: inactive (dead)
>        Docs: man:systemd-timedated.service(8)
>              man:localtime(5)
>              man:org.freedesktop.timedate1(5)
>
> Oct 09 09:53:56 DC1 systemd[1]: Started Time & Date Service.
> Oct 09 09:54:26 DC1 systemd[1]: systemd-timedated.service: Succeeded.
> Oct 09 09:54:56 DC1 systemd[1]: Starting Time & Date Service...
> Oct 09 09:54:56 DC1 systemd[1]: Started Time & Date Service.
> Oct 09 09:55:26 DC1 systemd[1]: systemd-timedated.service: Succeeded.
> Oct 09 09:55:56 DC1 systemd[1]: Starting Time & Date Service...
> Oct 09 09:55:56 DC1 systemd[1]: Started Time & Date Service.
> Oct 09 09:56:22 DC1 systemd[1]: Stopping Time & Date Service...
> Oct 09 09:56:22 DC1 systemd[1]: systemd-timedated.service: Succeeded.
> Oct 09 09:56:22 DC1 systemd[1]: Stopped Time & Date Service.
>
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> In all things, Be Intentional.
>
>
> On Sat, Oct 9, 2021 at 4:05 AM Rowland Penny via samba <
> samba at lists.samba.org> wrote:
>
>> On Fri, 2021-10-08 at 22:35 -0400, Rob Campbell wrote:
>> > 10.0.0.222 is the dhcp address before I set the static ip to
>> > 10.0.0.13 but it is still registered with ntpd.
>> >
>>
>> You appear to be running systemd-timedated as well, stop it, it isn't
>> compatible with a Samba AD DC.
>>
>> Rowland
>>
>>
>>
>> --
>> To unsubscribe from this list go to the following URL and read the
>> instructions:  https://lists.samba.org/mailman/options/samba
>>
>