search for: dlopoel

On Wed, 21 Aug 2024 14:11:52 +0200 L?o <dlopoel at gmail.com> wrote: > Hello Rowland, > > Here it is: > > smb.conf: > --- > [global] > dns forwarder = 9.9.9.9 > netbios name = DC1 > realm = AD.EXAMPLE.COM > server role = active directory domain controller > workgroup = AD > idmap_ldb:use rfc2307 = ye...

Hello Rowland, Here it is: smb.conf: --- [global] dns forwarder = 9.9.9.9 netbios name = DC1 realm = AD.EXAMPLE.COM server role = active directory domain controller workgroup = AD idmap_ldb:use rfc2307 = yes min protocol = SMB2 ntlm auth = mschapv2-and-ntlmv2-only restrict anonymous = 2 disable netbios = yes smb ports = 445 printcap name = /dev/null load printers = no disable spoolss = yes

> > ntlm auth = mschapv2-and-ntlmv2-only > > Why do you need the line above ? This is part of security hardening, to prevent the use of NTLMv1 authentication protocol (except for MSCHAPv2 authentication scheme) > > restrict anonymous = 2 > > disable netbios = yes > > I am not sure that is the correct way to do it on a DC, I do know that > the 'nbt' server

Hello, I come to you after several days of research about my problem: I cannot make windows clients join my Samba AD domain anymore. My domain is built with two Samba AD DCs, dc1 and dc2, that are both debian 12.6 up to date and use the debian samba packages (4.17.12+dfsg-0+deb12u1). dc1 has all FSMO roles. When I try to make a Windows computer join the domain, I get an error saying the domain