similar to: Samba domain time sync woes (Debian Bookworm)

FWIW, I looked at the settings in our domain (all of which I did myself). I used to explicitly set up ntp time sources in our network for all windows workstations before, and I continued to provide these after conversion from nt4-style domain to samba AD-DC. The NTP records are provided by DHCP, and are configured in the GPO, both with regional differences (choosing the local NTP servers within

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

On 20 January 2025 15:18 Luis Peromarta wrote: > > I hope to be able to do the same kind of tests, > On 20 Jan 2025 at 15:10 +0000, Peter Milesson <miles at atmos.eu>, wrote: > > > > I have tested with Windows 7 Pro (SP1), Windows 10 Pro (22H2), and > > Windows 11 Pro (24H2). All those clients report CMOS clock as time > > source. I also suspect that

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 >

I hope to be able to do the same kind of tests, On 20 Jan 2025 at 15:10 +0000, Peter Milesson <miles at atmos.eu>, wrote: > > I have tested with Windows 7 Pro (SP1), Windows 10 Pro (22H2), and > Windows 11 Pro (24H2). All those clients report CMOS clock as time > source. I also suspect that something broke in Samba since I posted > about this problem on 9 August 2023. Then I

On 20.01.2025 15:14, Sonic via samba wrote: > On Mon, Jan 20, 2025 at 5:53?AM Rowland Penny via samba < > samba at lists.samba.org> wrote: > >> I cannot get Chrony to work with MS-SNTP from a Windows client, now >> this could be a Samba problem.... >> > The reason I think it's a Samba issue is that it worked perfectly with > 4.19.3 but no longer works

On Mon, Jan 20, 2025 at 2:19?PM spindles seven via samba <samba at lists.samba.org> wrote: > > On 20 January 2025 15:18 Luis Peromarta wrote: > > > > I hope to be able to do the same kind of tests, > > On 20 Jan 2025 at 15:10 +0000, Peter Milesson <miles at atmos.eu>, wrote: > > > > > > I have tested with Windows 7 Pro (SP1), Windows 10 Pro

My tests: -Boot a backed up ?new? VM with chrony 4.3 and samba 4.19 installed, joined a new Win 10 machine, time syncs OK with Type: NT5DS. -Updated DC samba to 4.21.3 without removing the Windows machine from domain. Time syncs OK with NT5DS. -Leave domain, try to w32tm /monitor -> error can?t reach DCs (expected) -Join domain again: time syncs OK with NT5DS. I can?t reproduce. Can we make

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 after seeing this > thread I decided to see what was different about my configuration that > allowed it to work so seamlessly and I was

Hello Rowland, >> >> I guess this is because this specific machine has an old samba >> >> version (4.6.4) which lacks the necessary functions. >> >> >> >> What are my options now? >> >> a) update Samba on the old machine to a current version? (not >> >> preferred) >> > Excelent idea. Try: >> >>

> On 10/25/2023 9:53 AM PDT Ham via samba <samba at lists.samba.org> wrote: > > > It appears that none of our windows clients are syncing their time with > the samba DC.??? From what I can tell they are not able to get a > response from the DC.? For example, where the DC is named athena: > > >w32tm /monitor /computers:athena > >

On Wed, 25 Oct 2023 11:10:57 -0700 (PDT) James Browning via samba <samba at lists.samba.org> wrote: > > On 10/25/2023 9:53 AM PDT Ham via samba <samba at lists.samba.org> > > wrote: > > > > > > It appears that none of our windows clients are syncing their time > > with the samba DC.??? From what I can tell they are not able to get > > a

I'm a little late to the game on this. Just upgraded a few of our Samba servers to Ubuntu 24.04 and was pleased to see ntpsec... And today I see that time is not syncing on the windows machines. Before I saw the registry entry work around on this mailing list, I did some testing. Found that I can sync older Linux machines with the newer ntpsec servers without problems (tested with ntpdate),

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

On 30/04/2023 09:37, Peter Milesson via samba wrote: > > > On 30.04.2023 10:20, Rowland Penny via samba wrote: >> >> >> On 30/04/2023 09:06, Peter Milesson via samba wrote: >>> Hi Yvan, >>> >>> Thanks for the information, really useful. Essentially, it means I >>> need to wait for the official release of Debian Bookworm, and then

On 30-04-2023 10:46, Rowland Penny via samba wrote: > > > On 30/04/2023 09:37, Peter Milesson via samba wrote: >> >> >> On 30.04.2023 10:20, Rowland Penny via samba wrote: >>> >>> >>> On 30/04/2023 09:06, Peter Milesson via samba wrote: >>>> Hi Yvan, >>>> >>>> Thanks for the information, really useful.

On 30.04.2023 10:51, Kees van Vloten via samba wrote: > > On 30-04-2023 10:46, Rowland Penny via samba wrote: >> >> >> On 30/04/2023 09:37, Peter Milesson via samba wrote: >>> >>> >>> On 30.04.2023 10:20, Rowland Penny via samba wrote: >>>> >>>> >>>> On 30/04/2023 09:06, Peter Milesson via samba 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 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 30.04.2023 10:20, Rowland Penny via samba wrote: > > > On 30/04/2023 09:06, Peter Milesson via samba wrote: >> Hi Yvan, >> >> Thanks for the information, really useful. Essentially, it means I >> need to wait for the official release of Debian Bookworm, and then >> getting the newest Samba packages from Bookworm backports. It's just >> a

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.