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

On Thu, 23 Jan 2025 16:38:08 +0200
Virgo P?rna via samba <samba at lists.samba.org> wrote:
> 	It is quite possible, that NT_STATUS_TIME_DIFFERENCE_AT_DC is
> some kind of red herring. I found thread from July, where it was
> suggested, that "Samba seems to return it as an error code as a
> backstop". I did add log level = 10 with custom IP based filename to
> get additional logs. But it seems, that with
> log level = 1 auth_audit:5@/var/log/samba/auth_audit.log
> in main config... auth audit log goes still there.
> 
> 	One additional strange thing I did notice in that log, was,
> that Samba seems to be using strange 0 datetime in logs... In data
> structures were values like
> creation_time   : N jaan  23 08:26:52 2025 EET
> expiration_time : N jaan  23 01:55:33 1975 MSK
> (Default locale is et_EE locale... jaan - jan, N - Thu.)
Hmm, why, if you are in Estonia, is moscow time being used ?
It might just be, if you sort that, your problems may go away.

Rowland

On 24.01.2025 11:05, Rowland Penny via samba wrote:
> On Thu, 23 Jan 2025 16:38:08 +0200
> Virgo P?rna via samba <samba at lists.samba.org> wrote:
>> creation_time   : N jaan  23 08:26:52 2025 EET
>> expiration_time : N jaan  23 01:55:33 1975 MSK
>> (Default locale is et_EE locale... jaan - jan, N - Thu.)
> 
> Hmm, why, if you are in Estonia, is moscow time being used ?
> It might just be, if you sort that, your problems may go away.
> 
	Did you look at the year? At 1975 Estonia was under Soviet occupation. 
And in Soviet union we had officially Moscow time.

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