lists at zxt10d.de
2024-Jan-04 10:19 UTC
[Samba] Fresh ad installation - Win2022 can't join
Am 04.01.2024 um 10:37 schrieb Rowland Penny via samba:> On Thu, 4 Jan 2024 08:16:44 +0100 > lists--- via samba <samba at lists.samba.org> wrote: > >> Good morning, and a Happy New Year ? >> >> I'd like to setup a test-enviroment, based on Debian Bookworm and >> mjt's 4.19.3 packages. >> samba is running as a Hyper-V vm, its ip is 192.168.178.37, its name >> is dc.augusta.domain.tld >> >> My idea is to use this dc for two networks (192.168.178.0/24 and >> 192.168.180.0/24) and for testing one Windows 2022 server >> (192.168.178.34/24). >> I used these two guides: >> https://wiki.samba.org/index.php/Setting_up_Samba_as_an_Active_Directory_Domain_Controller >> https://wiki.samba.org/index.php/DNS_Administration >> Plus I added an computer-account by using "samba-tool computer add >> %name%" So far, so good ... ? >> >> When trying to add the Windows 2022 server to the domain I get this >> error message (in german): >> Beim Abfragen von DNS ?ber den Ressourceneintrag der >> Dienstidentifizierung (SRV), der zur Suche eines Active >> Directory-Dom?nencontrollers (AD DC) f?r die Dom?ne >> "augusta.domain.tld" verwendet wird, ist ein Fehler aufgetreten. >> >> Fehler: "Bei der DNS-Abfrage wurden keine Eintr?ge gefunden." >> (Fehlercode 0x0000251D DNS_INFO_NO_RECORDS) >> >> Es handelt sich um die Abfrage des Dienstidentifizierungseintrags f?r >> _ldap._tcp.dc._msdcs.augusta.domain.tld. >> >> So: what did I wrong, or what is missing? >> > > Lets start with the obvious, does the record exist, running the > following command should produce a record for every DC: > > host -t SRV _ldap._tcp.dc._msdcs.augusta.domain.tld.root at dc:/home/torsten# host -t SRV _ldap._tcp.dc._msdcs.augusta.domain.tld. _ldap._tcp.dc._msdcs.augusta.domain.tld has SRV record 0 100 389 dc.augusta.domain.tld.> How are you trying to join the 2022 machine ? As a DC or a domain > member ?As a domain member> The Latter should work, but there is this bug report: > > https://bugzilla.samba.org/show_bug.cgi?id=15495But its a bug report regarding "joining a *nix machine to an existing MS-based AD", isn't it?> RowlandCheers, Torsten
On Thu, 4 Jan 2024 11:19:17 +0100 lists--- via samba <samba at lists.samba.org> wrote:> Am 04.01.2024 um 10:37 schrieb Rowland Penny via samba:> > Lets start with the obvious, does the record exist, running the > > following command should produce a record for every DC: > > > > host -t SRV _ldap._tcp.dc._msdcs.augusta.domain.tld. > > root at dc:/home/torsten# host -t SRV > _ldap._tcp.dc._msdcs.augusta.domain.tld. > _ldap._tcp.dc._msdcs.augusta.domain.tld has SRV record 0 100 389 > dc.augusta.domain.tld.That shows the 'missing' record does exist.> > > How are you trying to join the 2022 machine ? As a DC or a domain > > member ? > > As a domain memberThen it should work.> > > The Latter should work, but there is this bug report: > > > > https://bugzilla.samba.org/show_bug.cgi?id=15495 > > But its a bug report regarding "joining a *nix machine to an existing > MS-based AD", isn't it? >That doesn't preclude it also not working in the reverse direction. The problem seems to be that the Windows server cannot find a record that you have now proved exists, so is the windows server using the DC as its nameserver ? Rowland