similar to: C6: ntpd time reset +277092510.162464 s

Hai, Flavio, Yes, it looks good, but i suggest, if you setting up a new DC on debian.. Go here: https://github.com/thctlo/samba4/tree/master/howtos And read the file: stretch-base-2-samba-minimal-ad.txt This should works also for debian Jessie, if it errors only remove the words " limited" from the line restrict. Now, review the code below, you need to make a few small changes.

A shell script is deployed to synchronize time, the script is invoked hourly by crontab, and its content is as follows: #!/bin/bash service ntpd stop ntpdate 192.168.0.191 #it's a valid ntpd server in LAN service ntpd start chkconfig ntpd on Inspected the Linux log(Centos6.4 /var/log/messages), found the following fragment: Jan 7 14:00:01 host1 ntpd[32101]: ntpd exiting on signal 15 Jan 7

Em 13/09/2017 10:36, L.P.H. van Belle via samba escreveu: > Hai, Flavio, > > Yes, it looks good, but i suggest, if you setting up a new DC on debian.. > Go here: https://github.com/thctlo/samba4/tree/master/howtos > And read the file: stretch-base-2-samba-minimal-ad.txt > > This should works also for debian Jessie, if it errors only remove the words " limited" from

Hi, on my Samba Server i use this config for the ntpd: server 127.127.1.0 fudge 127.127.1.0 stratum 10 server 0.gentoo.pool.ntp.org iburst prefer server 1.gentoo.pool.ntp.org iburst prefer server 2.gentoo.pool.ntp.org iburst prefer server 3.gentoo.pool.ntp.org iburst prefer driftfile /var/lib/ntp/ntp.drift logfile /var/log/ntp ntpsigndsocket /var/lib/samba/ntp_signd/ restrict default kod

On 13/02/15 17:26, Bob of Donelson Trophy wrote: > > > Copied Roweland's DC ntp.conf file into my two DC's. Restarted (all) > ntp. Member still timing out! > > (I am starting to think that there is 'something' about the sernet > packages that "they" do differently.) > > Rowland, Could I ask you to copy the ntp.conf from your client (appears

Hai Guy, Yes, it make a backup of your previous version so you can revert if needed. And review your config after your run it, you micht see a these line : restrict > -4 default kod notrap nomodify nopeer noquery mssntp mssntp ( check if you dont see mssntp 2 x, if so, remove 1 of them ) This is because normaly this is run against a "default" ntp.conf And change the variables

On 13/02/15 19:48, Bob of Donelson Trophy wrote: > > > Thank you, Rowland. > > Copied your simpler ntp.conf file into my member server. Made the > appropriate changes. Restarted all the ntp service on all machines (just > in case.) Ran 'ntpq -p' (on member server) and got the correct answer. > Proper connection to DC's. > --- > >

On my member server, running 'ntpq -p' yields: ntpq -p localhost: timed out, nothing received ***Request timed out The ntp.conf file is trying to use the DC's hostnames addresses: user at DC01:~# cat /etc/ntp.conf # /etc/ntp.conf, configuration for ntpd; see ntp.conf(5) for help driftfile /var/lib/ntp/ntp.drift # Enable this if you want statistics to be logged. #statsdir

On Wed, 25 Oct 2023 11:10:57 -0700 (PDT) James Browning via samba <samba at lists.samba.org> wrote: > > On 10/25/2023 9:53 AM PDT Ham via samba <samba at lists.samba.org> > > wrote: > > > > > > It appears that none of our windows clients are syncing their time > > with the samba DC.??? From what I can tell they are not able to get > > a

On 13/02/15 16:43, Bob of Donelson Trophy wrote: > > > Made the suggested adjustments (4 locations in the member server > ntp.conf file) and restarted ntp. > > Still (member server) timing out. > > Not sure what you mean about removing "server 0.debian.pool.ntp.org > iburst" lines. Those on the DC's. Aren't they necessary? > > Running 'ntpq

On Wed, 25 Oct 2023 11:53:07 -0500 Ham via samba <samba at lists.samba.org> wrote: > It appears that none of our windows clients are syncing their time > with the samba DC.??? From what I can tell they are not able to get a > response from the DC.? For example, where the DC is named athena: > > >w32tm /monitor /computers:athena > > athena[10.10.1.10:123]

On Wed, 25 Oct 2023 11:25:14 -0700 (PDT) James Browning via samba <samba at lists.samba.org> wrote: > > On 10/25/2023 11:16 AM PDT Rowland Penny via samba > > <samba at lists.samba.org> wrote: > > > > > > On Wed, 25 Oct 2023 11:53:07 -0500 > > Ham via samba <samba at lists.samba.org> wrote: > > > > > It appears that none of

Hm, the bind setup looks ok ,to me, its a debian Jessie as far i can see. Its a default setup, almost the same im using and bind is configured to 9.9 So i think one of these 4 problems. Incorrect rights on /var/lib/samba/ntp_signd chown root:ntp /var/lib/samba/ntp_signd chmod 750 /var/lib/samba/ntp_signd OR The time on the pc is more than 5 min off. OR The pc has just joined the

> On 10/25/2023 9:53 AM PDT Ham via samba <samba at lists.samba.org> wrote: > > > It appears that none of our windows clients are syncing their time with > the samba DC.??? From what I can tell they are not able to get a > response from the DC.? For example, where the DC is named athena: > > >w32tm /monitor /computers:athena > >

> On 10/25/2023 11:16 AM PDT Rowland Penny via samba <samba at lists.samba.org> wrote: > > > On Wed, 25 Oct 2023 11:53:07 -0500 > Ham via samba <samba at lists.samba.org> wrote: > > > It appears that none of our windows clients are syncing their time > > with the samba DC.??? From what I can tell they are not able to get a > > response from the

I guess your DC take the time from an external ntps server. But I want to serve time from the same DC, so this is my ntp config: #nano /etc/ntp.conf server 127.127.1.0 fudge 127.127.1.0 stratum 12 ntpsigndsocket /var/lib/samba/ntp_signd/restrict default mssntp ___________________________________________ Felipe_ González_Santiago KNOW THAT EVERYTHING WILL HAPPEN AT JUST THE RIGHT TIME,

On Tue, 8 Jan 2019 14:32:45 +0100 Viktor Trojanovic via samba <samba at lists.samba.org> wrote: > I’m currently trying to install a new (primary) AD DC in a Linux > container. It seems to me that being in a container, the DC is easier > to maintain and backup than on bare metal, and I prefer a container > over a VM for performance reasons. If the container setup will prove >

bob. server dc02.dts***m.lan. iburst prefer server dc01.dts***m.lan. iburst prefer remove the . after lan and try like this server dc02.dts***m.lan server dc01.dts***m.lan and optional, i advice, remove all lines : server 0.debian.pool.ntp.org iburst Louis ' >-----Oorspronkelijk bericht----- >Van: bob at donelsontrophy.net >[mailto:samba-bounces at lists.samba.org] Namens

It appears that none of our windows clients are syncing their time with the samba DC.??? From what I can tell they are not able to get a response from the DC.? For example, where the DC is named athena: >w32tm /monitor /computers:athena athena[10.10.1.10:123] ? ICMP: 0ms delay ? NTP: error ERROR_TIMEOUT - no response from server in 1000ms From a Linux machine there is

Hai Viktor, I've seen some answers already and all are correct. What i would do different here, when running in a container.. apt-get remove --purge ntpd ;-) The hosts that are running AD DC containers these need all up to use the same time source. And you dont install ntpd, you still have the same time in you AD. NTPD is not obligated to setup AD DC's. Its obligated to have