similar to: broadcastclient does not work on CentOS 4.1

This ntp.conf file works fine with RedHat Enterprise 3.0 and below. However, it doesn't work with CentOS 4.1. #authenticate no #enable auth driftfile /etc/ntp/drift keys /etc/ntp/ntp.keys server 127.127.1.0 <http://127.127.1.0> fudge 127.127.1.0 <http://127.127.1.0> stratum 10 trustedkey 1 enable bclient broadcastclient This is the error reported in /var/log/messages: Sep 29

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

I have two DC's running Version 4.1.16-SerNet-Debian-9.wheezy and a member server running Version 4.1.11-Debian. When I 'ntpq -p' from the member server I get: localhost: timed out, nothing received ***Request timed out Member server ntp.conf file: cat /etc/ntp.conf # Local clock (this is not the localhost address!) server 127.127.1.0 fudge 127.127.1.0 stratum 10 # The source,

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 -p' on DC's results in correct response. --- ------------------------- Bob Wooden of

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 to be your laptop) so I could review it's contents? --- ------------------------- Bob

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. --- ------------------------- Bob Wooden of Donelson Trophy 615.885.2846 (main) www.donelsontrophy.com [1] "Everyone

On Tue, 12 Sep 2017 14:41:42 -0300 Flávio Silveira via samba <samba at lists.samba.org> wrote: > > Ok, I understand now, one question though: if realm is > AD.TECNOPON.COM.BR, does domain need to be AD? No, you can use anything you like, provided it is one word, 15 characters or less, without punctuation. > If I understand > correctly, realm is "full domain with

Hy Guys, My samba version: 4.0.13 ntp version: 4.2.6p3 Ubuntu 12.04.3 LTS I have a weird problem, I sat up the time service via https://wiki.samba.org/index.php/Configure_NTP On the servers I have no firewall. This port is open when i check with nmap, ntp runs. Looks like all of my Windows 7 clients works fine but w32tm /resync says Permission denied 0x8007005, so not that good :) Windows

Hai Flavio, > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Flávio Silveira via samba > Verzonden: woensdag 13 september 2017 16:19 > Aan: samba at lists.samba.org > Onderwerp: Re: [Samba] File server questions > > > > Em 13/09/2017 10:36, L.P.H. van Belle via samba escreveu: > > Hai, Flavio, > >

Hi, I configured my NTP server in samba 4 according to the article " https://wiki.samba.org/index.php/Time_Synchronisation" however I verified that the NTP server does not respond to requests from Windows NTPv3 clients, it only responds to NTPv4. Following my ntp.conf: # /etc/ntp.conf, configuration for ntpd; see ntp.conf(5) for help driftfile /var/lib/ntp/ntp.drift # Enable this if

Hello, I recently compiled Samba 4.0.6 (as an AD DC) and am running it on Ubuntu 12.04. I followed the instructions on the Samba wiki (https://wiki.samba.org/index.php/Configure_NTP) for how to configure ntp, however the domain clients are rejecting the DCs as being acceptable time sources. Below is my ntp.conf: server 127.127.1.0 fudge 127.127.1.0 stratum 10 server 0.pool.ntp.org iburst

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

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

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 to be too much of hassle, I’ll switch to a VM, though. The first issue I’m facing is time synchronization. An container cannot

Hi All, I am currently running a setup with a main DC ad1, that has ntpd installed and is currently configured to retrieve the time from the UK NTP time pool. I also have a second backup AD DC, ad2, on which I have not installed ntpd but I have installed ntpdate. My current understanding is that the setup I have just described is in-line with the recommended best practices outlined in the

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

We have a local time server and all of our machines are pointed at it for the time. How can the clock drift by a day and a half? [root at devserver21 ~]# date Fri Aug 13 14:43:29 EDT 2010 [root at devserver21 ~]# rdate -s 192.168.1.67 [root at devserver21 ~]# date Thu Aug 12 07:02:39 EDT 2010 [root at devserver21 ~]# cat /etc/ntp.conf | grep -v ^# | grep -v ^$ restrict default nomodify notrap

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.

Hi On 5.3 i have a situation where some boxes have been 3 or 4 seconds out and restarting ntpd has fixed the issue. What i dont understand is why the clocks did not drift to the correct time when the config seems correct in that restarting ntp did correct the time. Is there something 'special' i need to do in order for the drift to work? $ cat /etc/ntp.conf restrict default