search for: svedr

...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, you can remove that line, if it is, why ? When getting NTP working on the DCs, I found a blog post (https://blog.svedr.in/posts/configuring-ntpd-for-a-samba-4-domain.html) that used the following command to figure out where the socket was: netstat -xpln | grep signd On my DCs, that returns: # netstat -xpln | grep signd unix 2 [ ACC ] STREAM LISTENING 28320 972/samba /var/run/samba/...

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

...g, 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 where Samba wants to put the ntp_signd socket: > >> > >> # netstat -xpln | grep signd > >> unix 2 [ ACC ] STREAM LISTENING 2071520535 19381/samba /var/lib/samba...

...$NF}' > > > > # samba -b | grep NTP_SIGND_SOCKET_DIR > NTP_SIGND_SOCKET_DIR: /var/lib/samba/ntp_signd > > > > If it isn't, you can remove that line, if it is, why ? > > When getting NTP working on the DCs, I found a blog post > (https://blog.svedr.in/posts/configuring-ntpd-for-a-samba-4-domain.html) > that used the following command to figure out where the socket was: > netstat -xpln | grep signd > > On my DCs, that returns: > # netstat -xpln | grep signd > unix 2 [ ACC ] STREAM LISTENING 28320 > 972/...

...>> # samba -b | grep NTP_SIGND_SOCKET_DIR >> NTP_SIGND_SOCKET_DIR: /var/lib/samba/ntp_signd >> >> >> > If it isn't, you can remove that line, if it is, why ? >> >> When getting NTP working on the DCs, I found a blog post >> (https://blog.svedr.in/posts/configuring-ntpd-for-a-samba-4-domain.html) >> that used the following command to figure out where the socket was: >> netstat -xpln | grep signd >> >> On my DCs, that returns: >> # netstat -xpln | grep signd >> unix 2 [ ACC ] STREAM LISTE...

...d >= 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 where Samba wants to put the ntp_signd socket: > > # netstat -xpln | grep signd > unix 2 [ ACC ] STREAM LISTENING 2071520535 19381/samba /var/lib/samba/ntp_signd/socket > > This loc...

----- On Apr 24, 2019, at 1:42 AM, samba samba at lists.samba.org wrote: > Hai > > 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