similar to: ntpd appears to not be able to query ntp servers automatically?

Hi guys, I don't use virtual machine. The 192.168.0.191 is an internal ntpd server configured by administrator, so i can not see what ntp server it synchronizes to or what is its time reference. But i have added a new line "server 192.168.0.191" into file "/etc/ntp.conf" on ntpd client machines, and the output to execute command ntpstat is as follows: synchronised to NTP

On 2/11/2015 11:12 PM, David chen wrote: > Hi guys, > Thanks for your reply. > I originally used the following command to synchronize time: > ntpdate 192.168.0.191 > but got the error: ntpdate[16715]: the NTP socket is in use, exiting > So i used the way of stopping ntpd service. > Now I have known that using command "ntpdate -u 192.168.0.191" can solve the above

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

Hai, Sorry for the long responce on this one, had a few days off. Some importent extra info here. If you run systemctl status ntp, you wil see if ntp is running correctly. The PC's, wil get there time through samba AD ( via /var/lib/samba/ntp_signd ) Linux clients needs ntp, point to the AD server(s) Windows ( domain joined ) clients get time through AD. Windows standalone, you need

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

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 >

I use systemd-timesyncd to sync time with the rest of the internet. Then, I use ntpd to allow my samba4 dc to share it's time with joined domain members. Most likely my ntpd.conf is horribly insecure and broken, but it's what I was able to figure out. /etc/ntpd.conf: # This bizarre rule makes ntp fall back to reading from the # bios clock if no network connection is available. server

Hi Louis, In general, this sounds like the solution I was looking for. But I’m still a bit unclear about the practical implementation. So, the DC can be setup without ntpd as it will work based on the system clock which, in turn, is actually being updated by the container host using NTP. Which means we’ve got the DC itself covered. But if ntpd is not installed, then how can the DC serve time

What Marco and Robert already did say.   This is what i mean ( and Robert ). Marco's option to disable though kernel is also an option.   Maybe a bit cryptic but like this.   HOST              - CONTAINER - SambaDC- samba-AD distibuting time to PC's. ||                         ||| HOST_its_NTP_Service  => get Internet time  |||| OTHERHOSTS NTP Client - COINTAINER - SambaMember  -

Hi CentOS users We are running CentOS 4.5 with NTP 4.2.0. # cat /etc/ntp.conf restrict default ignore restrict dns1.xxx.xxx mask 255.255.255.0 nomodify notrap noquery restrict dns2.xxx.xxx mask 255.255.255.0 nomodify notrap noquery restrict 127.0.0.1 server dns1.xxx.xxx server dns2.xxx.xxx fudge 127.127.1.0 stratum 10 driftfile /etc/ntp/drift broadcastdelay 0.008 authenticate no The problem is

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

Hi guys, Thanks for your reply. I originally used the following command to synchronize time: ntpdate 192.168.0.191 but got the error: ntpdate[16715]: the NTP socket is in use, exiting So i used the way of stopping ntpd service. Now I have known that using command "ntpdate -u 192.168.0.191" can solve the above error, and also know using ntpdate command is an improper way, i.e. should use

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

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

Running CentOS 3.4, I enabled the ntpd service and noticed that it opens up a hole in the firewall for ntp from 127.127.1.0. I look in the ntpd initscript and see that it's reading in servers from /etc/ntp/step-tickers. However, that file is empty... /etc/ntp/ntpservers contains clock.redhat.com and clock2.redhat.com, but ntpservers isn't used *anywhere*. This looks like a bug, but

Hello, I have a question regarding signed NTP support for Samba4 on Ubuntu 12.04. I have followed most of the steps outlined here: https://wiki.samba.org/index.php/Configure_NTP These steps I did differently are: * I did not install from source because the latest Ubuntu package for ntp available on Ubuntu 12.04 includes ntp-signd support already * I did not install Samba4 to /usr/local/samba, so

On Wed, January 2, 2013 03:53, Robert Dinse wrote: > > Friday, I moved our servers to a new co-lo facility and ran into > an interesting problem with virtual machines. > > I did an orderly shutdown of the CentOS 6.3 host, and it in > turn suspends all the guests. It took about an hour and a half > to move and fire up the host. > > The guests, being

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

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

On 03/09/2015 03:42 PM, Paul Heinlein wrote: > On Mon, 9 Mar 2015, C.L. Martinez wrote: > >> Hi all, >> >> I have a problem with ntpd daemon in my CentOS7 vm. When I try to list >> peers, command fails: [....] >> >> [root at c7tst ntpstats]# ntpq >> ntpq> pe >> ntpq: read: Connection refused >> ntpq> > > Does "ntpq -4 -c