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
lists at zxt10d.de
2024-Jan-04 11:12 UTC
[Samba] Fresh ad installation - Win2022 can't join
Am 04.01.2024 um 11:55 schrieb Rowland Penny via samba:> 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 member > > Then 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 ?Yes. The first nameserver is the ip-address of the samba-ad-dc, the second is the routers ip-address.> RowlandCheers, Torsten