similar to: I can't get Win10 clients to sync time with the DC

On Thu, 2019-10-24 at 16:27 +0100, Rowland penny via samba wrote: > On 24/10/2019 16:10, S?rgio Basto via samba wrote: > > Hi, > > As Centos 7 and Fedora defaults to chronyd [2] , should I use ntpd > > for > > some reason [3] ? I based my configurations on [1] which use ntpd > > ... > > but I thinking change for chronyd , change ntp deamons could outage >

Further investigations reveal: --- C:\WINDOWS\system32> w32tm /monitor GetDcList failed with error code: 0x800706BA. Exiting with error 0x800706BA --- error 0x800706BA indicates that the RPC server is unavailable. Any ideas? Thanks, Jonathan Kreider On Tue, Nov 6, 2018 at 5:48 PM Jonathan Kreider <jonathan.kreider at gmail.com> wrote: > > Thanks Robert & Marco. > >

On 16.11.2019 15:17, Sonic wrote: > On Thu, Nov 14, 2019 at 1:56 PM Viktor Trojanovic via samba > <samba at lists.samba.org> wrote: >> I'm running a Samba AD DC v4.9.9 with Windows 10 clients connected to it >> and just noticed that the clients are not synchronizing time with the >> server. I'm not sure why not. >> >> My setup is a bit special in

After reading the instructions at https://wiki.samba.org/index.php/Time_Synchronisation, I still have questions about how samba interacts with nptd. The issue is that LXD doesn't want containers setting the time and so won't start ntpd at container startup even though it's enabled in systemd. The host does sync it's time with a national time server, so we can assume that the

Hi, As Centos 7 and Fedora defaults to chronyd [2] , should I use ntpd for some reason [3] ? I based my configurations on [1] which use ntpd ... but I thinking change for chronyd , change ntp deamons could outage the samba service and client computers ? Thanks [1] https://negativo17.org/samba-4-active-directory-with-bind-dlz-zones-dynamic-dns-updates-windows-static-rpc-2/ [2]

On Thu Jan 18 10:52:55 2024 Sonic <sonicsmith at gmail.com> wrote: > > I'm with Luis in thinking that the fault is with the DC and not the > clients. I recently switched from using a GPO to set the time source to > using the "natural" time sync with the DC at one site due to the fact that > I was running the DC in a container which due to age could not run a

After trying all the suggestions in the below listed excerpts from this thread, I've taken time since my last posting on January 6th to continue this issue with the Microsoft forum: https://learn.microsoft.com/en-us/answers/questions/1480474/unable-to-time-sync-with-domain-controller?page=1&orderby=helpful&comment=answer-1411748#newest-answer-comment I likewise had no solution

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. > > I've created the Group Policy for the "Time Sources". This doesn't seem to be > working. This did

After our office upgraded to Windows 10, time sync stopped working with the Windows workstations. This used to work fine with Windows 7 and still works with linux domain members (although that's not surprising). The Windows 10 workstations ended up operating off the CMOS clock. We didn't notice this for a long time since the CMOS clock drift is slow, but after several months users started

You think ntp works with samba but it doesn?t. You *must* use chrony. It will take you exactly 5 minutes to get it up and running. On 5 Jan 2024 at 20:21 +0000, Mark Foley <mfoley at novatec-inc.com>, wrote: > > > > How do you know you're syncing with the DC? What does your 'w32tm /query /source' > give you? It?s all here :

On 17.11.2019 15:58, Sonic wrote: > On Sun, Nov 17, 2019 at 5:37 AM Viktor Trojanovic <viktor at troja.ch> wrote: >> I'm not sure I understand your setup. It seems like you are running >> Chrony on the host only and you just share the socket with the >> container, no chrony running there. > Yes, you have it correct. That's exactly what I'm doing. >

Hi Louis, In general, this sounds like the solution I was looking for. But I’m still a bit unclear about the practical implementation. So, the DC can be setup without ntpd as it will work based on the system clock which, in turn, is actually being updated by the container host using NTP. Which means we’ve got the DC itself covered. But if ntpd is not installed, then how can the DC serve time

Hello, It is debian 11, and it is ntp, as you can see below my ntp.conf. Ntp service is running fine . Some , not all, W10/11 clients do not sync with the dc (samba 4.19). What i did on the clients: net stop w32time w32tm /unregister w32tm /register net start w32time But after some time the wrong time shows up again? Greetings Daniel -----Urspr?ngliche Nachricht----- Von: Luis Peromarta

On 16.11.2019 23:37, Sonic wrote: > On Sat, Nov 16, 2019 at 10:34 AM Viktor Trojanovic <viktor at troja.ch> wrote: >> I think you may be confusing privileged with unprivileged containers, >> what you describe is perfectly possible with a privileged container but >> would be a bit more complicated to set up with an unprivileged one >> (since the user id's in the

Hello, I have a question regarding signed NTP support for Samba4 on Ubuntu 12.04. I have followed most of the steps outlined here: https://wiki.samba.org/index.php/Configure_NTP These steps I did differently are: * I did not install from source because the latest Ubuntu package for ntp available on Ubuntu 12.04 includes ntp-signd support already * I did not install Samba4 to /usr/local/samba, so

Hi, using SLES10 I''m unable to synchronize the time of DomU with that of Dom0. There is a persistent offset of about 3 seconds! Here''s a small history (not actual output): remote refid st t when poll reach delay offset jitter rkdvmso1.dvm.kl 192.168.0.11 5 u - 64 1 0.136 -2977.1 0.099 *rkdvmso1.dvm.kl 192.168.0.11 5 u 2 64

How you so sure about it? Even at https://packages.ubuntu.com/bionic/samba chrony mentioned as suggested related package . On Sun, Jun 3, 2018 at 6:13 PM Rowland Penny via samba <samba at lists.samba.org> wrote: > > On Sun, 3 Jun 2018 16:59:38 +0200 > Reindl Harald via samba <samba at lists.samba.org> wrote: > > > > > > > Am 03.06.2018 um 16:48 schrieb

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 3 June 2018 at 17:54, Rowland Penny via samba <samba at lists.samba.org> wrote: > On Sun, 3 Jun 2018 18:45:37 +0300 > Alexei Rozenvaser <alexei.roz at gmail.com> wrote: > > > How you so sure about it? > > Even at https://packages.ubuntu.com/bionic/samba chrony mentioned as > > suggested related package > > . > > Ubuntu can recommend what they

From: Mark Foley via samba <samba at lists.samba.org> To: "samba at lists.samba.org" <samba at lists.samba.org> Subject: Re: [Samba] Time sync not working with Windows 10 Date: Thu, 19 Nov 2020 22:13:40 +0000 > > On Wed, 18 Nov 2020 08:41:03 -0500 me at tdiehl.org wrote: > > > > On Wed, 18 Nov 2020, Mark Foley via samba wrote: > > > > > After