samba - Jan 2022 - No Domain Logon Possible after last Windows 11 Insider Update

Shall i make an additional level 10 debug log with current release, which
works?

-----Urspr?ngliche Nachricht-----
Von: samba <samba-bounces at lists.samba.org> Im Auftrag von Dirk Laurenz
via
samba
Gesendet: Dienstag, 18. Januar 2022 16:59
An: 'Rowland Penny' <rpenny at samba.org>; 'sambalist'
<samba at lists.samba.org>
Betreff: Re: [Samba] No Domain Logon Possible after last Windows 11 Insider
Update

So nothing changed - same behaviour. Here's a level 10 debug log

https://www.dropbox.com/s/r4i50j7hhld2z4j/192.168.2.80.log?dl=0


-----Urspr?ngliche Nachricht-----
Von: samba <samba-bounces at lists.samba.org> Im Auftrag von Rowland Penny
via
samba
Gesendet: Dienstag, 18. Januar 2022 12:31
An: sambalist <samba at lists.samba.org>
Betreff: Re: [Samba] No Domain Logon Possible after last Windows 11 Insider
Update

On Tue, 2022-01-18 at 11:46 +0100, samba at laurenz.ws
wrote:
> Hi,
> 
> it's two samba ad/dcs.
> 
> root at dc01:~# cat /etc/samba/smb.conf
> # Global parameters
> [global]
>         netbios name = DC01
>         realm = SAMBA.LAURENZ.WS
>         workgroup = SAMBA
>         server role = active directory domain controller
>         idmap_ldb:use rfc2307 = yes
>         client ldap sasl wrapping = sign
>         server services = -dns
>         host msdfs = yes
>         dns update command = /usr/sbin/samba_dnsupdate --use-samba- 
> tool
>         log file = /var/log/samba/%m.log
>         log level = 4
> #       max log size = 10000
> 
> 
> 
> [netlogon]
>         path = /var/lib/samba/sysvol/samba.laurenz.ws/scripts
>         read only = No
> 
> [sysvol]
>         path = /var/lib/samba/sysvol
>         read only = No
> 
> root at dc02:~# cat /etc/samba/smb.conf
> # Global parameters
> [global]
>         netbios name = DC02
>         realm = SAMBA.LAURENZ.WS
>         workgroup = SAMBA
>         server role = active directory domain controller
>         idmap_ldb:use rfc2307 = yes
>         client ldap sasl wrapping = sign
>         server services = -dns
>         host msdfs = yes
>         dns update command = /usr/sbin/samba_dnsupdate --use-samba- 
> tool
>         log file = /var/log/samba/%m.log
>         log level = 4
> #       max log size = 10000
> 
> [netlogon]
>         path = /var/lib/samba/sysvol/samba.laurenz.ws/scripts
>         read only = No
> 
> [sysvol]
>         path = /var/lib/samba/sysvol
>         read only = No
> 
> root at dc02:~# samba -V
> Version 4.11.17-Debian
> root at dc02:~# dpkg -l | grep samba
> ii  python3-samba                         2:4.11.17+dfsg-0.1raspbian1
> armhf        Python 3 bindings for Samba
> ii  samba                                 2:4.11.17+dfsg-0.1raspbian1
> armhf        SMB/CIFS file, print, and login server for Unix
> ii  samba-common                          2:4.11.17+dfsg-0.1raspbian1
> all          common files used by both the Samba server and client
> ii  samba-common-bin                      2:4.11.17+dfsg-0.1raspbian1
> armhf        Samba common files used by both the server and the
> client
> ii  samba-dsdb-modules:armhf              2:4.11.17+dfsg-0.1raspbian1
> armhf        Samba Directory Services Database
> ii  samba-libs:armhf                      2:4.11.17+dfsg-0.1raspbian1
> armhf        Samba core libraries
> ii  samba-vfs-modules:armhf               2:4.11.17+dfsg-0.1raspbian1
> armhf        Samba Virtual FileSystem plugins
Can I suggest you upgrade Samba, you can find packages here:

https://apt.van-belle.nl/

With the repo setup instructions here:

https://apt.van-belle.nl/simple-repo-setup.txt

Samba 4.11.17 is very old, better to use the latest version.

Rowland
 



--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba


--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

On Tue, 2022-01-18 at 23:17 +0100, Dirk Laurenz wrote:
> Shall i make an additional level 10 debug log with current release,
> which
> works?
> 
It will not hurt, something seems to have changed on Win11. It sounds
like you were running a test version of Win11, have you upgraded this
to the final released version ? Or have you tried with a new install of
Win11 ? I am not holding out much hope of it being fixed in the
released version of Win11, but you never know, Microsoft do strange
things :-)

Rowland