search for: syncfromflag

...Now' always gives "Time synchronization failed". For Windows 7 workstations, several years ago, I followed the advice in https://www.meinbergglobal.com/english/info/ntp-w32time.htm which was to do the following on the Windows 7 workstations: w32tm /config /manualpeerlist:mail,0x8 /syncfromflags:MANUAL w32tm /config /update Check the configuration: w32tm /query /source This worked and time was in-sync on the WIN7 computers for many years. I did this after upgrading/installing each Windows 10 workstation during 2019 Q4 and 2020 Q1, but apparently that didn't work. For the Windows...

...problem, and don't know were to start > > investigating. > > > Has anybody got this issue ? > > Got exactly your problem two days ago. > From elevated shell: > > w32tm /unregister > reboot > w32tm /register > w32tm /config /manualpeerlist:time.example.com /syncfromflags:MANUAL > /update > time /T (To test if synchronization done correctly) > > time.example.com is your domain time server - either AD DC or an NTP > server it > is synchronized with. I prefer NTP, though. Domain time service seems to be > unreliable in my setup, or needs to be en...

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 reference - synced by (S)NTP) > Precision: -6 (15.62ms per tick) > Root Delay: 0.0313721s > Root Dispersion: 0.297334...

...> > Has anybody got this issue ? > >> > >> Got exactly your problem two days ago. > >> From elevated shell: > >> > >> w32tm /unregister > >> reboot > >> w32tm /register > >> w32tm /config /manualpeerlist:time.example.com /syncfromflags:MANUAL > >> /update > >> time /T (To test if synchronization done correctly) > >> > >> time.example.com is your domain time server - either AD DC or an NTP > >> server it > >> is synchronized with. I prefer NTP, though. Domain time service seem...

...ows 7 workstations, several years ago, I followed the advice in > > > https://www.meinbergglobal.com/english/info/ntp-w32time.htm which was to do the following on > > > the Windows 7 workstations: > > > > > > > > > w32tm /config /manualpeerlist:mail,0x8 /syncfromflags:MANUAL > > > w32tm /config /update > > > > > > Check the configuration: > > > > > > w32tm /query /source > > > > > > This worked and time was in-sync on the WIN7 computers for many years. I did this after > > > upgrading/inst...

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 : the time on these computers is not synchronized with my Domain Controler. Big problem is, if time difference is considerable (more or less 5 minutes), users can not log in. On the other hand, my server is correctly synchronized with NTP server. I don't

...erver. I have confirmed that ntpd is running on the AD-DC and listening on udp:123. I have also confirmed that udp:123 is not blocked by the firewall at either end. 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 reference - synced by (S)NTP) Precision: -6 (15.62ms per tick) Root Delay: 0.0313721s Root Dispersion: 0.2973346s ReferenceId: 0x84F60BE3 (source IP: 132.246.11.227) L...

...t;> > investigating. >> >> > Has anybody got this issue ? >> >> Got exactly your problem two days ago. >> From elevated shell: >> >> w32tm /unregister >> reboot >> w32tm /register >> w32tm /config /manualpeerlist:time.example.com /syncfromflags:MANUAL >> /update >> time /T (To test if synchronization done correctly) >> >> time.example.com is your domain time server - either AD DC or an NTP >> server it >> is synchronized with. I prefer NTP, though. Domain time >service seems to be >> unreliab...

...go, I followed the advice in > >>>> https://www.meinbergglobal.com/english/info/ntp-w32time.htm which was to do the following on > >>>> the Windows 7 workstations: > >>>> > >>>> > >>>> w32tm /config /manualpeerlist:mail,0x8 /syncfromflags:MANUAL > >>>> w32tm /config /update > >>>> > >>>> Check the configuration: > >>>> > >>>> w32tm /query /source > >>>> > >>>> This worked and time was in-sync on the WIN7 computers for many years...

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

...rver. > I don't understand the reason of my problem, and don't know were to start > investigating. > Has anybody got this issue ? Got exactly your problem two days ago. From elevated shell: w32tm /unregister reboot w32tm /register w32tm /config /manualpeerlist:time.example.com /syncfromflags:MANUAL /update time /T (To test if synchronization done correctly) time.example.com is your domain time server - either AD DC or an NTP server it is synchronized with. I prefer NTP, though. Domain time service seems to be unreliable in my setup, or needs to be enabled manually. -- With best re...

...t;> > investigating. >> >> > Has anybody got this issue ? >> >> Got exactly your problem two days ago. >> From elevated shell: >> >> w32tm /unregister >> reboot >> w32tm /register >> w32tm /config /manualpeerlist:time.example.com /syncfromflags:MANUAL >> /update >> time /T (To test if synchronization done correctly) >> >> time.example.com is your domain time server - either AD DC or an NTP >> server it >> is synchronized with. I prefer NTP, though. Domain time service seems to be >> unreliable in...

Hi, The Windows and Linux workstations are not synchronizing the time with the Samba 4 DC. I have verified that the problem is permission. I'm using Samba 4.6.3 on Debian 8. In this way the stations are with different schedules from the DC. Do I need to configure any GPOs? What is the maximum time the computer clock can differ from DC ? Regards, Márcio

...e synchronization failed". > > For Windows 7 workstations, several years ago, I followed the advice in > https://www.meinbergglobal.com/english/info/ntp-w32time.htm which was to do the following on > the Windows 7 workstations: > > > w32tm /config /manualpeerlist:mail,0x8 /syncfromflags:MANUAL > w32tm /config /update > > Check the configuration: > > w32tm /query /source > > This worked and time was in-sync on the WIN7 computers for many years. I did this after > upgrading/installing each Windows 10 workstation during 2019 Q4 and 2020 Q1, but apparently &g...

...indows.com, not the DC. On my current Samba DC I had to set the NTP server on the Windows 10 computers when using the Samba DC. I missed a couple of commands in my previous post. On the Windows as Admin: net stop w32time w32tm /unregister w32tm /register w32tm /config /manualpeerlist:dc1,0x8 /syncfromflags:MANUAL net start w32time w32tm /config /update When I did the first 3 and last of the above command initially, 'w32tm /query /source' returned 'Local CMOS Clock', and this query has remained like that since, even doing all the commands listed above again and rebooting both Windows...

...worked. So did the one using my DC. I had actually tried that before and it worked before. My latest attempt was the following, in PowerShell (based on yet another post): stop-service w32time w32tm /unregister w32tm /register start-service w32time w32tm /config /manualpeerlist:0.pool.ntp.org /syncfromflags:manual /update w32tm /config /reliable:yes restart-service w32time w32tm /resync w32tm /query /source Notice that I'm not using my DC as the time source, so whether that source is a problem is eliminated as a variable. After the 'w32tm /resync' I got "the computer did not res...

...peers N. peer: 1 Peer: Stato: In sospeso Tempo rimanente: 178.3500000s Modalità: 0 (riservato) Strato: 0 (non specificato) PeerIntervallo di polling: 0 (non specificato) HostIntervallo di polling: 0 (non specificato) If i force a (re)configuration: C:\Users\gaio>w32tm /config /update /syncfromflags:DOMHIER Esecuzione comando riuscita. C:\Users\gaio>w32tm /query /peers...

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

...uot;The computer did not resync because no time data was available." I tried so many things on the PC. Restarting the time service, unregistering the service and registering it again, checking that the time service is not configured by group or local policy (it is not), running w32tm /config /syncfromflags:domhier /update, and last but not least, rebooting to no end. This is not on a laptop, this is happening on computers constantly connected to the host and therefore the DC via ethernet. Oh, and before I forget, here is my smb.conf, though the AD is otherwise functioning without issues: [global]...

...gt; Tempo rimanente: 178.3500000s > Modalità: 0 (riservato) > Strato: 0 (non specificato) > PeerIntervallo di polling: 0 (non specificato) > HostIntervallo di polling: 0 (non specificato) > > If i force a (re)configuration: > > C:\Users\gaio>w32tm /config /update /syncfromflags:DOMHIER > > Esecuzione comando riuscita. > > C:\Users\gaio>w32tm /query /peers >...