similar to: Time synchronization problem. Chrony, ntp

On Sat, Jan 18, 2025 at 3:49?AM Programnet via samba <samba at lists.samba.org> wrote: > > I noticed a problem with time synchronization on all Windows endpoints. > I am using Samba 4.21.3 and Chrony 4.3-2. > > When I run the following command in Windows: > > w32tm /monitor > dc1.xxxx.pl *** PDC ***[192.168.45.10:123]: > ICMP: 1ms delay > NTP: +0.0000000s offset

On Mon, 20 Jan 2025 09:38:50 -0500 Jeffrey Walton via samba <samba at lists.samba.org> wrote: > On Sat, Jan 18, 2025 at 3:49?AM Programnet via samba > <samba at lists.samba.org> wrote: > > > > I noticed a problem with time synchronization on all Windows > > endpoints. I am using Samba 4.21.3 and Chrony 4.3-2. > > > > When I run the following command

In our network we found some client with clock differences. Some machine have effectively some troubles, eg have NO 'Windows Time' service defined, probably some glitches happened when moving from our old NT-like domain. Anyway, catching for that, we have found some other strangeness. Windows time service run: C:\Users\gaio>sc query w32time NOME_SERVIZIO: w32time TIPO

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 that the DC is running inside a (privileged) linux container. For that reason, it's not possible or necessary for the container to correct the system clock, this is done on the

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

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

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

Hi there. A few NTP experts around here lately. We need more info. Distro, and wether your are using NTP (nrpsec) or Chrony. Regards. LP On 16 Feb 2024 at 14:37 +0100, Daniel M?ller via samba <samba at lists.samba.org>, wrote: > Dear all, > > We just have a samba 4.19 domain running. And what i recognized ist hat some > windows 10/11 clients does not sync time with the dc.

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

Dear all, We just have a samba 4.19 domain running. And what i recognized ist hat some windows 10/11 clients does not sync time with the dc. The time is not the real time as on the dc, about 10 minutes back or several minutes in the future. Is this a bug or did spmething chance in the behaviour of samba? My ntp.conf/ Debian11: driftfile /var/lib/ntp/ntp.drift server 127.127.1.0 fudge

On Fri Feb 9 04:23:29 2024 Luis Peromarta via samba <samba at lists.samba.org> wrote: > > Are your clients talking to the DCs re. Time at all ? > > This is an example in one of my DCs: Run tcpdump on your DC: > > root at dwing:~# tcpdump??port 123 -v > [snip] > > Might be work examining that traffic for clues. > > Regards, LP Luis, excellent suggestion!

On 09.02.2024 17:02, Mark Foley via samba wrote: > On Fri Feb 9 04:23:29 2024 Luis Peromarta via samba<samba at lists.samba.org> wrote: >> Are your clients talking to the DCs re. Time at all ? >> >> This is an example in one of my DCs: Run tcpdump on your DC: >> >> root at dwing:~# tcpdump??port 123 -v >> [snip] >> >> Might be work

Are your clients talking to the DCs re. Time at all ? This is an example in one of my DCs: Run tcpdump on your DC: root at dwing:~# tcpdump??port 123 -v tcpdump: listening on enp1s0, link-type EN10MB (Ethernet), snapshot length 262144 bytes 10:20:41.655081 IP (tos 0x0, ttl 128, id 32113, offset 0, flags [none], proto UDP (17), length 96) ?? ?192.168.3.52.ntp > dwing.mad.mater.int.ntp: NTPv3,

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

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

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

On 20 January 2025 19:31 Luis Peromarta wrote: > > 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

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