Displaying 3 results from an estimated 3 matches for "bindcmdaddress".
2019 Nov 16
2
I can't get Win10 clients to sync time with the DC
On 16.11.2019 15:17, Sonic wrote:
> On Thu, Nov 14, 2019 at 1:56 PM Viktor Trojanovic via samba
> <samba at lists.samba.org> wrote:
>> I'm running a Samba AD DC v4.9.9 with Windows 10 clients connected to it
>> and just noticed that the clients are not synchronizing time with the
>> server. I'm not sure why not.
>>
>> My setup is a bit special in
2019 Nov 16
0
I can't get Win10 clients to sync time with the DC
...ork.
chrony.conf:
===========================
pool us.pool.ntp.org iburst
keyfile /etc/chrony/chrony.keys
driftfile /var/lib/chrony/chrony.drift
logdir /var/log/chrony
maxupdateskew 100.0
directive.
hwclockfile /etc/adjtime
directive.
rtcsync
makestep 1 3
local stratum 8
manual
allow 192.168.1.0/24
bindcmdaddress 192.168.1.1
ntpsigndsocket /mnt/containers/dc/rootfs/usr/local/samba/var/lib/ntp_signd
===========================
As can be seen the socket for chrony, which is running on the host, is
inside the container (/mnt/containers/dc/rootfs/), both the host OS
and the container OS have access to it.
Chr...
2019 Nov 17
2
I can't get Win10 clients to sync time with the DC
...g iburst
> keyfile /etc/chrony/chrony.keys
> driftfile /var/lib/chrony/chrony.drift
> logdir /var/log/chrony
> maxupdateskew 100.0
> directive.
> hwclockfile /etc/adjtime
> directive.
> rtcsync
> makestep 1 3
> local stratum 8
> manual
> allow 192.168.1.0/24
> bindcmdaddress 192.168.1.1
> ntpsigndsocket /mnt/containers/dc/rootfs/usr/local/samba/var/lib/ntp_signd
> ===========================
>
> As can be seen the socket for chrony, which is running on the host, is
> inside the container (/mnt/containers/dc/rootfs/), both the host OS
> and the contain...