similar to: Joining Windows 10 Domain Member to Samba AD/DC

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

On Sun, 22 Nov 2020 09:56:07 Rowland penny <rpenny at samba.org> wrote: > > On 22/11/2020 02:04, Mark Foley via samba wrote: > > 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

On Wed Jan 17 06:13:56 2024 Luis Peromarta via samba <samba at lists.samba.org> > > I have the impression your DC?s ntp server is not working properly for whatever reason. Your windows machines try to grab time for them, can?t, and then default to local coms clock or some other time source. > > From a windows member machine, can you try : > > w32tm /stripchart

On Wed, 18 Nov 2020, Mark Foley via samba wrote: > 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 >

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 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 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 Mon, 30 Jan 2017 12:16:30 -0500 James B. Byrne wrote: > I set the client's w32tm configuration this way: > > w32tm /config /update /manualpeerlist:"time.nrc.ca time.chu.nrc.ca" > /syncfromflags:ALL > > And when I check the status with > > w32tm /query /status > > then I see this: > > Leap Indicator: 0(no warning) > Stratum: 3 (secondary

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 work fine with my old 4.8.2 DC, so I know it works in principle. I have

Hi ! Actually, problem was located on client side, not samba side. w32time has "disappeared" from services list (!) the w32tm /unregister and w32tm /register solve the problem My clients seem to be correctly synchronised with my AD DC now. If i find out why w32time has disappeared, I'll post a message here. Thank you for your help ! 2015-04-22 16:02 GMT+02:00 Andrey Repin

Hi Marco, As far i can see here. Are all your ADDC servers set to the same source NTP ( preffered a stratum 1 or 2 ) server. ( and not pool ntp sources ) Because below i see stratum 4 and stratum 3 servers and a timeout on one server. When i look at this. > C:\Users\gaio>w32tm /query /peers > N. peer: 1

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

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

Hello Andrey Thanks for the trick. I'll try it. But it's a pity it doesn't work natively, right ? 2015-04-22 14:08 GMT+02:00 Andrey Repin <anrdaemon at yandex.ru>: > Greetings, William LIM! > > > Hi, > > > I have set a Samba AD DC on my network. Version is 4.1.17 on a Debian > > Wheezy. > > > I have an issue on my Windows XP SP3 clients :

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

I have the impression your DC?s ntp server is not working properly for whatever reason. Your windows machines try to grab time for them, can?t, and then default to local coms clock or some other time source. From a windows member machine, can you try : w32tm /stripchart /computer:us.pool.ntp.org /dataonly /samples:5 That should work. Then try: w32tm /stripchart /computer:your.dc.address

We have a Samba-4.3 AD-DC hosted on a FreeBSD-10.3 system. We have just discovered that for some reason our domain workstations are not synchronising their time with the AD-DC. We have not altered the default GPO nor have we created a special GPO to handle time services. I have been working on several of the domain clients and I cannot seem to get them to source from the Samba server. I have

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

On Thu Jan 4 19:46:02 2024 Mark Foley via samba <samba at lists.samba.org> 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. > > [deleted] The above references the first in a long thread I started having