similar to: windows workstations needing reboot to validate passwords.

I am (earlier reported under the subject "Peculiar Problem") having an issue that started several weeks ago, where windows (10 pro, server 2019) computers randomly get into a state where they refuse to validate passwords. Rebooting (sometimes several times) makes the problem go away. You can also log in if you disconnect the PC from the network and then reconnect. List of changes around

Have you setup Samba audit logging? This may aid in your efforts to see the reasons for not authenticating from the servers perspective. https://wiki.samba.org/index.php/Setting_up_Audit_Logging -----Original Message----- From: samba <samba-bounces at lists.samba.org> On Behalf Of Ray Klassen via samba Sent: Thursday, November 16, 2023 1:11 PM To: samba at lists.samba.org Subject:

Thank you for the suggestion. Audit logging enabled. On Thu, 2023-11-16 at 13:27 -0500, James Atwell via samba wrote: > Have you setup Samba audit logging? This may aid in your efforts to > see the reasons for not authenticating from the servers perspective.? > > https://wiki.samba.org/index.php/Setting_up_Audit_Logging > > > > > -----Original Message----- >

Audit logging has been a bust. The failed attempt by the workstation to validate the password does not show up in the logs. On Thu, 2023-11-16 at 10:38 -0800, Ray Klassen via samba wrote: > Thank you for the suggestion. Audit logging enabled. > > On Thu, 2023-11-16 at 13:27 -0500, James Atwell via samba wrote: > > Have you setup Samba audit logging? This may aid in your efforts

> -----Original Message----- > From: samba <samba-bounces at lists.samba.org> On Behalf Of Ray Klassen via > samba > Sent: Monday, November 20, 2023 1:09 PM > To: samba at lists.samba.org > Subject: Re: [Samba] windows workstations needing reboot to validate > passwords. --ADDENDUM > > Audit logging has been a bust. The failed attempt by the workstation to >

On Mon, 2023-11-20 at 13:43 -0500, James Atwell via samba wrote: > > > > -----Original Message----- > > From: samba <samba-bounces at lists.samba.org> On Behalf Of Ray > > Klassen via > > samba > > Sent: Monday, November 20, 2023 1:09 PM > > To: samba at lists.samba.org > > Subject: Re: [Samba] windows workstations needing reboot to > >

> -----Original Message----- > From: samba <samba-bounces at lists.samba.org> On Behalf Of Ray Klassen via > samba > Sent: Monday, November 20, 2023 2:10 PM > To: samba at lists.samba.org > Subject: Re: [Samba] windows workstations needing reboot to validate > passwords. --ADDENDUM > > > > On Mon, 2023-11-20 at 13:43 -0500, James Atwell via samba wrote:

On Wed, 2023-11-22 at 15:02 -0800, Ray Klassen via samba wrote: > > > On Tue, 2023-11-21 at 09:19 -0800, Ray Klassen via samba wrote: > > > > > > On Tue, 2023-11-21 at 12:00 -0500, James Atwell via samba wrote: > > > > > > > > > > -----Original Message----- > > > > From: samba <samba-bounces at lists.samba.org> On

Still pursuing my strange problem with windows clients randomly (2 or 3 a day on a network of about 200 pc's) ?not allowing logins until reboot. Nailing down some best practises in an attempt to fix. My best guess is that it's a Kerberos issue --sensitive to time sync and DNS. -- Installed chrony instead of ntpsec (seems to perform as advertised) -- (Today) moved to BIND9_DLZ instead of

Op 20-01-2025 om 11:52 schreef Rowland Penny via samba: > On Sun, 19 Jan 2025 17:51:54 +0100 > Peter Milesson via samba <samba at lists.samba.org> wrote: > >> >> >> On 19.01.2025 17:30, Sonic via samba wrote: >>> When I first did a Samba upgrade to 4.19.3 on Debian Bookworm back >>> in December of 2023 Chrony was working just fine for a natural

TLDW: I have a Samba install, and I can use help getting the signing socket to return a signature with either Chrony or NTPsec; I would appreciate some guidance on what I am doing incorrectly. I partially followed the instructions at [1]; after checking and revising, I saw that adding a line to start signd appeared to have broken everything else. I have attached a list of most of the steps I

On Sat, 06 Jan 2024 13:06:48 -0500 Mark Foley via samba <samba at lists.samba.org> wrote: > On Sat Jan 6 03:34:43 2024 Rowland Penny via samba > <samba at lists.samba.org> wrote: > > > > On Fri, 5 Jan 2024 23:53:52 +0000 > > Luis Peromarta via samba <samba at lists.samba.org> wrote: > > > > > You think ntp works with samba but it doesn?t.

On Sun, 19 Jan 2025 17:51:54 +0100 Peter Milesson via samba <samba at lists.samba.org> wrote: > > > > On 19.01.2025 17:30, Sonic via samba wrote: > > When I first did a Samba upgrade to 4.19.3 on Debian Bookworm back > > in December of 2023 Chrony was working just fine for a natural > > domain time sync to the DC - no special config or GPO necessary. So >

On 9/19/24 09:23, Rowland Penny via samba wrote: > On Thu, 19 Sep 2024 06:44:13 -0700 (PDT) > James Browning via samba <samba at lists.samba.org> wrote: > >> TLDW: I have a Samba install, and I can use help getting the signing >> socket to return a signature with either Chrony or NTPsec; I would >> appreciate some guidance on what I am doing incorrectly. I

On Thu, 19 Sep 2024 06:44:13 -0700 (PDT) James Browning via samba <samba at lists.samba.org> wrote: > TLDW: I have a Samba install, and I can use help getting the signing > socket to return a signature with either Chrony or NTPsec; I would > appreciate some guidance on what I am doing incorrectly. I partially > followed the instructions at [1]; after checking and revising, I saw

On Sat Jan 6 03:34:43 2024 Rowland Penny via samba <samba at lists.samba.org> wrote: > > On Fri, 5 Jan 2024 23:53:52 +0000 > Luis Peromarta via samba <samba at lists.samba.org> wrote: > > > You think ntp works with samba but it doesn?t. > > Sorry, but 'ntp' does work, it is the rewrite for more security > 'ntpsec' that doesn't seem to

Hi there, In my experience NTP has been trouble lately with the NTPsec implementation. A few months back I decided to remove NTPsec and go with Chrony. These are my notes: http://samba.bigbird.es/doku.php?id=samba:install-chrony Hope it helps. On Oct 25, 2023 at 19:04 +0200, Ham <ham at kc0dxf.net>, wrote: > > Any ideas on what the problem is?

I was able to switch to Chony and verify that it is working. Clients are now getting time from the DC. Luis has good notes! On 10/25/23 12:06, Luis Peromarta via samba wrote: > Hi there, > > In my experience NTP has been trouble lately with the NTPsec implementation. > > A few months back I decided to remove NTPsec and go with Chrony. > > These are my notes: > >

On Fri, 5 Jan 2024 23:53:52 +0000 Luis Peromarta via samba <samba at lists.samba.org> wrote: > You think ntp works with samba but it doesn?t. Sorry, but 'ntp' does work, it is the rewrite for more security 'ntpsec' that doesn't seem to work. > > You *must* use chrony. It will take you exactly 5 minutes to get it > up and running. Chrony does seem to

On Fri Jan 5 03:23:48 2024 Peter Milesson via samba <samba at lists.samba.org> wrote: > > On 05.01.2024 1:28, Mark Foley via samba wrote: > > I've added a Windows 10 domain member to my Domain. I'm now following the > > procedure in https://wiki.samba.org/index.php/Time_Synchronisation#Configuring_Time_Synchronisation_on_a_Windows_Domain_Member. > > > >