search for: creation_tim

...al 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.) I would assume, that this 50 years in past date is some kind of null values. Although, I do not think that there is actual time syncing issue. Because I hav...

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

...info0 : * info0: struct smbXsrv_session_global0 db_rec : * session_global_id : 0x0d54b3be (223654846) session_wire_id : 0x000000000d54b3be (223654846) creation_time : Wed Aug 26 09:53:02 AM 2020 CEST expiration_time : Thu Jan 1 01:00:00 AM 1970 CET auth_time : NTTIME(0) auth_session_info_seqnum : 0x00000000 (0) auth_session_info : NULL...

Mandi! Rowland penny via samba In chel di` si favelave... > Even though your users may have the same username in AD as in the NT4-style > domain, they are different users, so a few thoughts. You have 'map to guest > = bad user', so I take it you must have 'guest ok = yes' set in the shares > (you haven't shown us the shares), so try changing 'bad user' to

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

On Fri, 24 Jan 2025 11:12:06 +0200 Virgo P?rna via samba <samba at lists.samba.org> wrote: > 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...

...360) > task_id : 0x00000000 (0) > vnn : 0xffffffff (4294967295) > unique_id : 0x015078ee87970d64 (94708558047153508) > creation_time : Fri Oct 16 01:43:47 PM 2020 CEST > share_name : NULL > encryption_flags : 0x00 (0) > 0: SMBXSRV_ENCRYPTION_REQUIRED > 0: SMBXSRV_ENCR...

...0002 (2) info : union smbXsrv_session_globalU(case 0) info0: struct smbXsrv_session_global0 session_global_id : 0xfeda2f8e (4275711886) session_wire_id : 0x00000000feda2f8e (4275711886) creation_time : Thu Mar 12 03:44:01 PM 2015 CET expiration_time : Thu Jan 1 01:00:00 AM 1970 CET auth_session_info_seqnum : 0x00000001 (1) auth_session_info: struct auth_session_info security_token: stru...

https://bugs.freedesktop.org/show_bug.cgi?id=86006 Bug ID: 86006 Summary: [NV84] Nvidia GeForce 8600 GT VDPAU h264 hardware acceleration Product: xorg Version: 7.6 (2010.12) Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium

...: union >smbXsrv_session_globalU(case 0) > info0: struct smbXsrv_session_global0 > session_global_id : 0xfeda2f8e (4275711886) > session_wire_id : >0x00000000feda2f8e (4275711886) > creation_time : Thu Mar 12 >03:44:01 PM 2015 CET > expiration_time : Thu Jan 1 >01:00:00 AM 1970 CET > auth_session_info_seqnum : 0x00000001 (1) > auth_session_info: struct auth_session_info >...

Hi, Reading the microsoft troubleshooting guide, it seems that password hash sync issues can be caused by: > The Active Directory account used by Azure AD Connect to communicate > with on-premises Active Directory is not granted Replicate Directory > Changes and Replicate Directory Changes All permissions, which are > required for password synchronization. How to verify existance or

...info0 : * info0: struct smbXsrv_session_global0 db_rec : * session_global_id : 0xb266fec4 (2993094340) session_wire_id : 0x00000000b266fec4 (2993094340) creation_time : Thu Mar 19 18:07:34 2020 CET expiration_time : Thu Jan 1 01:00:00 1970 CET auth_time : Thu Mar 19 18:07:34 2020 CET auth_session_info_seqnum : 0x00000001 (1) auth_session_info : *...

...info0 : * info0: struct smbXsrv_session_global0 db_rec : NULL session_global_id : 0x65eb71f1 (1709928945) session_wire_id : 0x0000000065eb71f1 (1709928945) creation_time : Thu Nov 19 05:35:46 PM 2020 UTC expiration_time : Thu Sep 14 02:48:05 AM 30828 UTC auth_time : Thu Nov 19 05:35:47 PM 2020 UTC auth_session_info_seqnum : 0x00000001 (1) auth_session_info...

...global: struct smbXsrv_session_global0 db_rec : NULL session_global_id : 0xe752a8c6 (3880954054) session_wire_id : 0x00000000e752a8c6 (3880954054) creation_time : Mon Mar 9 10:30:42 2020 NZDT expiration_time : Thu Jan 1 12:00:00 1970 NZST auth_time : Mon Mar 9 10:30:42 2020 NZDT auth_session_info_seqnum : 0x00000001 (1)...

https://bugs.freedesktop.org/show_bug.cgi?id=109952 Bug ID: 109952 Summary: nv106 nv108 confusion Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau at