samba - Feb 2025 - Windows 11 24H2, Samba 4.21.3 AD DC and domain users cannot log in

On Tue, 4 Feb 2025 16:01:48 +0200
Virgo P?rna via samba <samba at lists.samba.org> wrote:
> On 04.02.2025 15:43, Rowland Penny via samba wrote:
> > 
> > After a bit more investigation, that might be the same 'fix' I
> > pointed to earlier, but from a different direction.
> > 
> > So I dug deeper and found this:
> > 
> >
https://answers.microsoft.com/en-us/windowsclient/forum/all/after-update-to-latest-win-11-24h2-rdp-kerberos/d0f95e77-eb25-4604-bfd7-526d14a585a1?page=3
> > 
> > Which appears to be a lot closer to what the problem the OP is
> > getting. If it is, then it appears to be a Windows bug that they
> > are not accepting.
> > 
> 
> 	I'll check this also. Changing allowed kerberos algorihms had
> no effect. Although for me fully updated 23H2 is also not working.
> That is why I started suspecting, that Windows expects something of
> Samba side, that is not working anymore.  The whole schema update
> part. 
> 	I did disable deprecated settings in Samba side.
> 
If it is a Samba problem, I would have expected to have seen multiple
reports of it, but I haven't seen them. What I have seen (after doing
an internet search) is lots of reports of similar problems with Windows
24H2 and the real fix appears to be, do not use 24H2.

Rowland

On 05.02.2025 10:49, Rowland Penny via samba wrote:
> 
> If it is a Samba problem, I would have expected to have seen multiple
> reports of it, but I haven't seen them. What I have seen (after doing
> an internet search) is lots of reports of similar problems with Windows
> 24H2 and the real fix appears to be, do not use 24H2.
> 
	I thought, that it might be something about my specific 
configuration/dc history (some kind of configuration issue). That is, 
why I started checking changes and then I discovered that schema update 
part.

	Whatever it is, it seems to affect other Windows 11 versions also (23H2 
test vm has same problem). And even Windows 10 computers are having some 
issues (that started with January update and before Samba upgrade). 
Although, with win10 issues are only with rdp and ssh login and restart 
has fixed them (at least until now).

	

-- 
Virgo P?rna
virgo.parna at mail.ee