Virgo Pärna
2025-Jan-24 09:30 UTC
[Samba] Windows 11 24H2, Samba 4.21.3 AD DC and domain users cannot log in
On 24.01.2025 11:23, Rowland Penny via samba wrote:> > Yes, I did look at the MSK years, but ignored them because everything > should be using EET and the time isn't stored like that in AD. >I suspect, that internally everything is in UTC and when logging into file it is converted to string by server location locale and timezone... Europe/Tallinn. Just really strange value for what must be null value... Yesterday it happened to be exactly same day on weekday, just 50 years ago... -- Virgo P?rna virgo.parna at mail.ee
Virgo Pärna
2025-Jan-24 09:37 UTC
[Samba] Windows 11 24H2, Samba 4.21.3 AD DC and domain users cannot log in
On 24.01.2025 11:30, Virgo P?rna via samba wrote:> On 24.01.2025 11:23, Rowland Penny via samba wrote: >> >> Yes, I did look at the MSK years, but ignored them because everything >> should be using EET and the time isn't stored like that in AD. >> > > ????I suspect, that internally everything is in UTC and when logging > into file it is converted to string by server location locale and > timezone... Europe/Tallinn. > ????Just really strange value for what must be null value... Yesterday > it happened to be exactly same day on weekday, just 50 years ago... >Googling 1975-01-22 22:55:33 first result seems to explain it. Again another red herring... "The value 7FFFFFFFFFFFFFFF or 0 will mean that the account never expires" Probably logging code does not handle this value logistically. Another red herring. -- Virgo P?rna virgo.parna at mail.ee
Apparently Analagous Threads
- Windows 11 24H2, Samba 4.21.3 AD DC and domain users cannot log in
- Windows 11 24H2, Samba 4.21.3 AD DC and domain users cannot log in
- Windows 11 24H2, Samba 4.21.3 AD DC and domain users cannot log in
- Windows 11 24H2, Samba 4.21.3 AD DC and domain users cannot log in
- Windows 11 24H2, Samba 4.21.3 AD DC and domain users cannot log in