search for: nt_status_time_difference_at_dc

...0.x, although I expect that is purely coincidental and the issue might well be a recent Windows update or similar. I happen to have extra logging turned on on one of my DCs, and did see some messages in the log at the same time I tried to log in. An example is below; I saw the same status code of NT_STATUS_TIME_DIFFERENCE_AT_DC against the user account as well as the computer account which is shown in the log extract below. NTP (well, chrony) is running on the DC and the time on the client looks to be reasonably correct (within 10-20 seconds), so I'm not sure what/where the time difference is.. Interestingly on one o...

After enabling auth_audit logging at samba, there are lot of messages with status NT_STATUS_TIME_DIFFERENCE_AT_DC But clock is synced and same in workstation and in server... -- Virgo P?rna virgo.parna at mail.ee

On Wed, 22 Jan 2025 15:46:44 +0200 Virgo P?rna via samba <samba at lists.samba.org> wrote: > After enabling auth_audit logging at samba, there are lot of messages > with status NT_STATUS_TIME_DIFFERENCE_AT_DC > But clock is synced and same in workstation and in server... > From the looks of it, your workstation thinks differently, could it be a timezone problem ? If I run 'date' on my PDC_emulator DC, I get this: Wed 22 Jan 14:13:01 GMT 2025 And the same command run immediately on a U...

On 22.01.2025 16:16, Rowland Penny via samba wrote: > On Wed, 22 Jan 2025 15:46:44 +0200 > Virgo P?rna via samba <samba at lists.samba.org> wrote: > >> After enabling auth_audit logging at samba, there are lot of messages >> with status NT_STATUS_TIME_DIFFERENCE_AT_DC >> But clock is synced and same in workstation and in server... >> > > From the looks of it, your workstation thinks differently, could it be > a timezone problem ? > Windows is set to UTC +02:00.. And date command in DC shows EET (East European Time). Both appear to h...

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/sam...

..., which is 'The user name or password is incorrect.', but. as you don't seem to have a SID, might mean your win11 computer cannot, for some reason, contact the DC, so have you tried the standard Windows fix ? Also known as turning it off and on again ;-) I think you can ignore the 'NT_STATUS_TIME_DIFFERENCE_AT_DC', Samba seems to return it as an error code as a backstop, try turning up the loglevel to 2 on the DCs, that should make another error message pop out. Rowland

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...

...from windows xp using netbios name. Though I can access it using its IP address. I can access that samba share from windows 7 with no problem at all. samba server is v3.5.6, member server of active directory (samba4) the logs show: error packet at smbd/sesssetup.c(334) cmd=115 (SMBsesssetupX) NT_STATUS_TIME_DIFFERENCE_AT_DC It all began after adjusting time zone in samba4 server and samba 3 server to US/Eastern. Change from EDT to EST should take place on November 3rd. Running in my windows xp box: net time \\ad yields: Current time at \\AD is 10/31/2013 9:09AM Local time (GMT-04:00) at \\AD is 10/31/2013 10:09AM...

One more detail... I'm working currently remotely, so I'm accessing that Windows 11 computer over remote desktop. If I actually supply incorrect password, then that error shows up on password promt dialog (The logon attempt failed). If I supply correct password, then connection is establised. I'll get Windows console view with "The username or password is incorrect. Try