LCA: A Samba 4 update
LCA: A Samba 4 update
Posted Jan 18, 2012 22:47 UTC (Wed) by jonabbey (guest, #2736)Parent article: LCA: A Samba 4 update
Posted Jan 18, 2012 23:07 UTC (Wed)
by foom (subscriber, #14868)
[Link] (3 responses)
Posted Jan 19, 2012 6:22 UTC (Thu)
by abartlet (subscriber, #3928)
[Link]
restrict default mssntp
We didn't wish to reimplement this protocol if we could avoid it. The option to point to a different NTP signing deamon (a samba service, on by default) is:
ntpsigndsocket /var/run/ntp_signd/
The NTPd on the system must have been configured with --enable-ntp-signd
Andrew Bartlett
Posted Jan 19, 2012 22:19 UTC (Thu)
by codewiz (subscriber, #63050)
[Link] (1 responses)
I hope it gets an integral TCP/IP stack too. It's needed in order to communicate with the clients :)
Seriously, does Samba *really* need to rewrite custom versions of everything? I used to run an enterprise network in which Windows clients had to coexist with Linux and MacOS clients. Most corporate networks already have their own dns, dhcp, ldap and kerberos services and all they need the Samba DC to integrate with them--not replace them.
Posted Jan 20, 2012 0:14 UTC (Fri)
by dlang (guest, #313)
[Link]
I agree with you that it's far better to integrate with an existing project rather than recreating it, but in this case it sounds like they tried
LCA: A Samba 4 update
LCA: A Samba 4 update
LCA: A Samba 4 update
> correct time for Kerberos to work, and it sure would be a pain to have
> to configure NTPd and samba separately!
LCA: A Samba 4 update
