search for: signd

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

...'m using > >> ntpd, not chrony. Rechecking the > >> https://wiki.samba.org/index.php/Time_Synchronisation link I noted that it said, "Requirements: > >> ntpd >= 4.2.6 from http://www.ntp.org, compiled with enabled signed ntp support > >> (--enable-ntp-signd)". I didn't know if my version of ntpd was compile with --enable-ntp-signd. > >> > >> While trying to figure that out I came across the potentially very useful webpage > >> https://blog.svedr.in/posts/configuring-ntpd-for-a-samba-4-domain. It gave the following &...

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 SlackBuilds repo and have no idea how it was built. Is there an option to chronyd to list build options? I didn't see one in the manpage. > Also for comparison: &g...

...samba <samba at lists.samba.org> wrote: > On Sat Feb 10 15:31:47 2024 Sonic <sonicsmith at gmail.com> wrote: > > On Sat, Feb 10, 2024 at 2:20?PM Mark Foley via samb<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 SlackBuilds repo and > > have no idea how it was built. Is there an option to chronyd to list build > > options? I didn't see one in the manp...

...t appear to be competely working). I'm using > ntpd, not chrony. Rechecking the > https://wiki.samba.org/index.php/Time_Synchronisation link I noted that it said, "Requirements: > ntpd >= 4.2.6 from http://www.ntp.org, compiled with enabled signed ntp support > (--enable-ntp-signd)". I didn't know if my version of ntpd was compile with --enable-ntp-signd. > > While trying to figure that out I came across the potentially very useful webpage > https://blog.svedr.in/posts/configuring-ntpd-for-a-samba-4-domain. It gave the following > instruction to see wher...

...about the internet. > These DNS forwarders are other internal servers. They provide connectivity to non-domain systems and the internet. >> idmap_ldb:use rfc2307 = yes >> ldap server require strong auth = no >> netbios name = dc5 >> ntp signd socket directory = /var/run/samba/ntp_signd > > Is the above different from the output of: > samba -b | grep 'NTP_SIGND_SOCKET_DIR' | awk '{print $NF}' > # samba -b | grep NTP_SIGND_SOCKET_DIR NTP_SIGND_SOCKET_DIR: /var/lib/samba/ntp_signd > If it isn't,...

The output is: alexei at ubuntu-dc:~$ sudo samba -b | grep 'SIGND' NTP_SIGND_SOCKET_DIR: /var/lib/samba/ntp_signd On Sun, Jun 3, 2018 at 5:32 PM Rowland Penny via samba <samba at lists.samba.org> wrote: > > On Sun, 3 Jun 2018 17:11:47 +0300 > Alexei Rozenvaser <alexei.roz at gmail.com> wrote: > > > On Sun, Jun 3, 2018 at 4:51...

Mandi! Paul Littlefield via samba In chel di` si favelave... > >Does 'timesync' know about signed support ? > >e.g. /var/lib/samba/ntp_signd > No, it doesn't... so I will changing my routine, and RTFM. > https://wiki.samba.org/index.php/Time_Synchronisation Absolutely true for DCs, where ntpd with --enable-ntp-signd is needed, to provide NTP service to windows client/member. But for linux DM, what make differences to have...

...> > I would suggest first. > > Whats the OS? Linux 18.04 > And sharing your smb.conf might help. [global] dns forwarder = 192.168.2.101 192.168.2.102 idmap_ldb:use rfc2307 = yes ldap server require strong auth = no netbios name = dc5 ntp signd socket directory = /var/run/samba/ntp_signd realm = REALM.COM server role = active directory domain controller workgroup = REALM acl:search = no load printers = no ntp signd socket directory = /var/run/samba/ntp_signd printcap name = /dev/null...

Congratulations. Happy to hear you got it running. Just out of curiosity and apologies if this has been answered before, but why Slack and not Debian when general consensus is Debian is great for Samba ? Building a Samba AD on Debian is painless and takes 20m from start to finish. Anyway, glad you sort it. LP. On 11 Feb 2024 at 05:11 +0100, Mark Foley <mfoley at novatec-inc.com>, wrote:

On Sun, Jun 3, 2018 at 4:51 PM Rowland Penny via samba <samba at lists.samba.org> wrote: > > On Sun, 3 Jun 2018 16:29:04 +0300 > Alexei Rozenvaser via samba <samba at lists.samba.org> wrote: > > > Hi > > > > I'm running samba 4.7.6 on ubuntu 18.04 as (backup / secondary) domain > > controller > > No your not, you are just running Samba as

...hat worked right out of the box, no problems. And, I was able to provision with the BIND9_FLATFILE back end which let me migrate from my existing bind/named config rather painlessly. So, I was pretty happy with Slackware. The only issue then, as now, is that ntpd wasn't built with --enable-ntp-signd, but I was able to build ntpd from sources with that option and everything ran fine for the next 10 years with subsequent kernel and samba updates. Since then I've simply continued to use Slackware as I'm familiar with it and I don't feel like investing time in converting everything to...

On Wed, 24 Apr 2019 14:07:37 -0500 (CDT) Mike Ray <mray at xes-inc.com> wrote: > >> idmap_ldb:use rfc2307 = yes > >> ldap server require strong auth = no > >> netbios name = dc5 > >> ntp signd socket directory = /var/run/samba/ntp_signd > > > > Is the above different from the output of: > > samba -b | grep 'NTP_SIGND_SOCKET_DIR' | awk '{print $NF}' > > > > # samba -b | grep NTP_SIGND_SOCKET_DIR > NTP_SIGND_SOCKET_DIR: /var/lib/s...

Am 03.06.2018 um 16:48 schrieb Rowland Penny via samba: > On Sun, 3 Jun 2018 17:37:45 +0300 > Alexei Rozenvaser <alexei.roz at gmail.com> wrote: > >> The output is: >> alexei at ubuntu-dc:~$ sudo samba -b | grep 'SIGND' >> NTP_SIGND_SOCKET_DIR: /var/lib/samba/ntp_signd > > First three letters are NTP and at the moment, Samba only supports the > use of ntp, whilst other time servers may claim to work with a Samba > DC, they are not supported please don't confuse ntp as protocol and n...

...hanges, as directed in the how-to. I assume the error is coming from the line addition "%{_mandir}/man8/ntpdtime.8*", however I'm not sure of the fix. It seems like that should be included in the source RPM? < --enable-linuxcaps --- > --enable-linuxcaps --enable-ntp-signd 330a331 > %{_sbindir}/sntp 348,349c349,350 < %{_mandir}/man8/ntptime.8* < %{_mandir}/man8/tickadj.8* --- > %{_mandir}/man8/ntpdtime.8* > #%{_mandir}/man8/tickadj.8* 355c356 < %{_mandir}/man8/ntp-wait.8* --- > #%{_mandir}/man8/ntp-wait.8*

...ork, I just hope they do not follow ntpsec down > the same path. > > The other thing that you have to know, Mark Foley is using Slackware, > > Rowland In this case, I think Slackware is not a factor. For one thing, I downloaded the ntp 4.2.8p17 source and built it using --enable-ntp-signd; not the as-shipped Slackware version. Also, I've used ntp 4.2.8p15 for several years, also with --enable-ntp-signd, on my current Slackware DC and all Windows domain members were able to use it as the time source. As well, the fact that I am getting "Local CMOS Clock" when I do ...

...to guest = Bad User rndc command = /bin/true # server role = STANDALONE netbios name = filer cache directory = /local/samba-config/common/cache lock directory = /local/samba-config/common/lock log file = /local/samba-config/common/log/%m ntp signd socket directory = /local/samba-config/common/signd pid directory = /local/samba-config/common/pid private dir = /local/samba-config/common/private state directory = /local/samba-config/common/state [iso] comment = ISO browseable = No public = Yes...

...t; the same path. > > > > The other thing that you have to know, Mark Foley is using > > Slackware, > > > > Rowland > > In this case, I think Slackware is not a factor. For one thing, I > downloaded the ntp 4.2.8p17 source and built it using > --enable-ntp-signd; not the as-shipped Slackware version. > I was trying to point out that your version of 'ntp' might be okay because it came from Slackware (which seemingly it doesn't). The problem with 'ntp' became apparent on Debian 12, where the 'ntp' package was replaced by the...

...garding 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 also modified that part of ntp.conf * Ubuntu uses AppArmor instead of SELinux - I found that the apparmor profile for ntp already includes support for ntp-signd for Samba4: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/93026...

Hi, hpa wrote: > On PowerPC (I think) "unsigned char" is the default. In any case it seems a good idea to interpret the character more explicitely. To my experience, one signdness change causes a little tree of consequential signedness changes or questionable cast operations. How about the following instead ? if ((c >= 0 && c <= ' ') || c == '\x7f') { Besides code improvement there is the riddle of how gcc 5 can spoil the result. >...