search for: nt5ds

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 a standard set of??test so we all agree...

...e weekend. I tested an old version of a bookworm dc with Samba version 4.17.5 and a Windows 10 Pro version 1903 The dc is running chrony version 4.3-1+b1. The Windows machine has no amendments to its time settings, no GPO no registry settings, so when it was joined to the domain the Type is NT5DS when w32tm /query /configuration command is run. Ie it's out of the box. With this setup the time synchronisation works OK, with the w32tm /query /status giving successful result and citing the dc as its source. I then removed the Windows machine from that domain and joined it to a domain wh...

...(default installation, no special setups made on the clients) cannot receive the correct time of my samba 4.0.4 AD domain controller. Windows XP and 7 work fine though. The problem occurs at three W2k test clients I tried with. The default behavior of Windows clients is to use the update type "Nt5DS" which means, that the client tries to get the time of its domain controller. Unfortunately this fails for my W2k clients in conjunction with Samba 4.0.4 and also an error in event log appears, that says that the time couldnt be retrieved of my samba4 server "mysmb4srv.ad.mycompany.com&qu...

...; > I tested an old version of a bookworm dc with Samba version 4.17.5 and a Windows 10 Pro version 1903 > The dc is running chrony version 4.3-1+b1. The Windows machine has no amendments to its time settings, no GPO no registry settings, so when it was joined to the domain the Type is NT5DS when w32tm /query /configuration command is run. Ie it's out of the box. With this setup the time synchronisation works OK, with the w32tm /query /status giving successful result and citing the dc as its source. Forgive my ignorance... Did w32tm actually use NT5DS in this case? Or did it sil...

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 (expected) > -Join domain again: time syncs OK with NT5DS. > > I can?t reproduce. OK, so I test again -...

Hi Andrew, what is it for? I got a revision_match_error. Could this be the reason why my windows clients can't sync the time via nt5ds? How can I solve this? Regards Tim Am 28. Februar 2015 20:36:42 MEZ, schrieb Andrew Bartlett <abartlet at samba.org>: >On Fri, 2015-02-27 at 12:52 +0100, Peter Serbe wrote: >> >> L.P.H. van Belle schrieb am 27.02.2015 12:45: >> >> > Ok.. very strange .. &gt...

On 28/02/15 23:57, Andrew Bartlett wrote: > On Sat, 2015-02-28 at 20:43 +0100, Tim wrote: >> Hi Andrew, >> >> what is it for? I got a revision_match_error. Could this be the reason >> why my windows clients can't sync the time via nt5ds? > I'm not aware of Windows clients using this interface. They use SNTP, > which we don't have a client for (see ntpdate). Hi Andrew, you do know that ntpdate was depreciated before samba 4.0 was released ? you should be using ntpd Rowland > > What we don't have is a cl...

...g the page. > > Rowland > Hi Rowland, Many thanks for all your help to Samba Users, much appreciated. I had a look at your new WiKi page and noticed this statement which immediately raised questions in my mind: "By default domain joined Windows clients synchronize their clock via NT5DS with the AD-DC which holds the PDC-emulator FSMO role." I had always thought that Windows domain members used any DC providing Time Services, and didn't necessarily contact the DC holding the PDC emulator role. The Microsoft article which you cite in the para "Default time source&quo...

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

L.P.H. van Belle schrieb am 27.02.2015 12:45: > Ok.. very strange .. For me it looks like this: It will work, if I ask for the time on one of my DCs. It will fail, if I ask some other ntp server. That should give the direction for looking deeper.

...z 2015 00:57:22 MEZ, schrieb Andrew Bartlett <abartlet at samba.org>: >On Sat, 2015-02-28 at 20:43 +0100, Tim wrote: >> Hi Andrew, >> >> what is it for? I got a revision_match_error. Could this be the >reason >> why my windows clients can't sync the time via nt5ds? > >I'm not aware of Windows clients using this interface. They use SNTP, >which we don't have a client for (see ntpdate). > >What we don't have is a client tool that uses the same protocol as >windows. This is indeed an oversight, and means you can't trigger th...

...wrote: > On 28/02/15 23:57, Andrew Bartlett wrote: > > On Sat, 2015-02-28 at 20:43 +0100, Tim wrote: > >> Hi Andrew, > >> > >> what is it for? I got a revision_match_error. Could this be the reason > >> why my windows clients can't sync the time via nt5ds? > > I'm not aware of Windows clients using this interface. They use SNTP, > > which we don't have a client for (see ntpdate). > > Hi Andrew, you do know that ntpdate was depreciated before samba 4.0 was > released ? you should be using ntpd Well, given the recent p...

...23:57, Andrew Bartlett wrote: >> > On Sat, 2015-02-28 at 20:43 +0100, Tim wrote: >> >> Hi Andrew, >> >> >> >> what is it for? I got a revision_match_error. Could this be the >reason >> >> why my windows clients can't sync the time via nt5ds? >> > I'm not aware of Windows clients using this interface. They use >SNTP, >> > which we don't have a client for (see ntpdate). >> >> Hi Andrew, you do know that ntpdate was depreciated before samba 4.0 >was >> released ? you should be using nt...

...nks for all your help to Samba Users, much > appreciated. I had a look > > at your new WiKi page and noticed this statement which > immediately raised > > questions in my mind: > > > > "By default domain joined Windows clients synchronize their > clock via NT5DS with > > the AD-DC which holds the PDC-emulator FSMO role." > > > > I had always thought that Windows domain members used any > DC providing Time > > Services, and didn't necessarily contact the DC holding the > PDC emulator role. > > The Microsoft art...

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 with 4.21.1 (or 4.21.3). I guess it is possible that all of the Windows'

OK, it seems to be an authentication issue. At least w.r.t. the member server. When I add the user name, it does ask me for the password and succeeds. I don't see any difference when using IP numbers instead of host names. root at circe:~# samba-tool time ulysses -U peter Password for [HOME\peter]: Fri Feb 27 14:31:46 2015 CET

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 from dc1.xxxx.pl RefID: time.cloudflare.com [162.159.200.123] Stratum: 4 dc2.xxxx.pl[192.168.45.9:123]: ICMP: 1ms delay NTP: -0.0001207s

...auth suceeded. So at this point I am authenticated against my samba4 AD domain. Now I can re-execute "net time" and it works fine. After this authentication the windows client automatically was able to sync its time with my samba4 AD domain controller, as the default update mechanism Nt5DS is used (=that stands for time sync with the dc in the domain). Now I don't understand, why I had to authenticate first at my domain, to allow this to work?? Win7 and WinXP hosts don't show this behavior, they work from scratch and can sync their time. I did not have applied any GPOs b...

...55.255.0 mssntp ntpsigndsocket /var/run/samba4/ntp_signd/ The Windows 7 client should now sync its clock to the DC. From Windows 7 run: C:> w32tm /resync /rediscover This should report successful completion. If not check: C:> w32tm /query /configuration The time provider should be type NT5DS. If not try: C:> w32tm /config /syncfromflags:domhier /update C:> net stop w32time && net start w32time When it's working the command C:> w32tm /monitor will report on the time source of the DC. Initially my Windows 7 VM would not sync. I believe the problem was, before join...