similar to: Time Sync

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 that the DC is running inside a (privileged) linux container. For that reason, it's not possible or necessary for the container to correct the system clock, this is done on the

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

Further investigations reveal: --- C:\WINDOWS\system32> w32tm /monitor GetDcList failed with error code: 0x800706BA. Exiting with error 0x800706BA --- error 0x800706BA indicates that the RPC server is unavailable. Any ideas? Thanks, Jonathan Kreider On Tue, Nov 6, 2018 at 5:48 PM Jonathan Kreider <jonathan.kreider at gmail.com> wrote: > > Thanks Robert & Marco. > >

After reading the instructions at https://wiki.samba.org/index.php/Time_Synchronisation, I still have questions about how samba interacts with nptd. The issue is that LXD doesn't want containers setting the time and so won't start ntpd at container startup even though it's enabled in systemd. The host does sync it's time with a national time server, so we can assume that the

Recently we have been having a lot of trouble with time synchronisation between our samba DC and the domain clients. We are not sure what started this issue since the Samba domain went live on October 11, 2016 and the issues only began to surface this past January but at some point the time on the clients and the DC diverged enough that we began to get strange network errors. Once we figured out

On 16.11.2019 23:37, Sonic wrote: > On Sat, Nov 16, 2019 at 10:34 AM Viktor Trojanovic <viktor at troja.ch> wrote: >> I think you may be confusing privileged with unprivileged containers, >> what you describe is perfectly possible with a privileged container but >> would be a bit more complicated to set up with an unprivileged one >> (since the user id's in the

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

Yeah, AppArmor is enabled, but I put everything (that I could find) into complain mode: $ sudo apparmor_status apparmor module is loaded. 12 profiles are loaded. 3 profiles are in enforce mode. lxc-container-default lxc-container-default-with-mounting lxc-container-default-with-nesting 9 profiles are in complain mode. /sbin/dhclient /usr/bin/lxc-start

On Sat Feb 10 15:31:47 2024 Mark Foley <mfoley at novatec-inc.com> wrote: > > On Sat, Feb 10, 2024 at 2:20?PM Mark Foley via samba > <samba at lists.samba.org> wrote: > > Does chrony have to be built in some special way to enable ntp-signd? > > Needs to be configured with "--enable-ntp-signd". I may have to build from sources. I downloaded from the

> > > Forgot to mention, are sure your time sync over AD is working correctly. > One to add to you list, check times of server and clients, (* yes again, > if needed just to be sure). > Yes, I have double check that time is correctly being synced. FYI, Rowland, the process outlined in the wiki for using chronyd does not work on Ubuntu 18.04 (my AD DC is on Ubuntu, but my file

Hello folks I've deployed Samba 4.0.26 using Sernet binary packages and running on active directory mode , everything works fine except that client machines don't sync time with server , ntp_signd is enabled in smb.conf , Ntpd is installed and running , is there anyway to debug this functionality on Samba ?

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

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, i want set selinux to usw with ntpd but when i run (as described in wiki) semanage -a -t ntpd_t "/usr/local/samba/var/lib/ntp_signd" i have that error " usage: semanage [-h] {import,export,login,user,port,ibpkey,ibendport,interface,module,node,fcontext,boolean,permissive,dontaudit} ... semanage: error: argument subcommand: invalid choice:

Further followups! We are correlating DEBUG-level output from libvirt with the libvirt 1.2.2 code to try to figure out what libvirt is doing under the hood. Even though we have the log level set to 1 (info) in our libvirtd.conf, we are not seeing the VIR_DEBUG() [1] statements being printed out. There are tons of other presumably-debug lines of output showing up in our log. We are sort of

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

After our office upgraded to Windows 10, time sync stopped working with the Windows workstations. This used to work fine with Windows 7 and still works with linux domain members (although that's not surprising). The Windows 10 workstations ended up operating off the CMOS clock. We didn't notice this for a long time since the CMOS clock drift is slow, but after several months users started

Sorry for the long post but attempted this several over the past year with no success but staying on an NT4 domain is no longer viable. Need to get this resolved so hopefully there will be a clue somewhere in this montage. The current PDC is samba-3.6.25 running on Gentoo using tdbsam backend. The new AD will be a Debian LXC container running on Debian Jessie using samba compiled from git

Me again! Think we've found it. By diving into the LXC logs for the specific container, we found this: 2014-04-17 21:07:06.066+0000: 2861: debug : virCgroupSetValueStr:678 : Set value '/sys/fs/cgroup/devices/machine/oshi32134.libvirt-lxc/devices.allow' to 'c 189:130 rw' Looks like libvirt the permission to 'rw', not 'rmw' [1], so no surprise that when it

Hello, I have multiple samba DC for different domains running on a single box. I read a little bit up on time synchronisation and now configured it. It seems to work. My question is, what happens when multiple DCs go to the same ntp_signd/socket, will it work? Or should I configure one socket per DC instance? Cheers, Thomas