search for: sambda

...ds "172.18.0.1" as the DNS option over its DHCP server. The samba AD server has its DNS forwarder set to "172.18.0.1". The only thing to add is that 172.18.0.1 runs dnsmasq. samba is used with Windows Desktops for AD and home shares, and with Linux servers for AD with sssd (sambda's Winbind wasn't quite there when this was set up). Nothing really relies on DNS from samba; unless you know something about this point that I do not. I could also manually add the local entries to samba's DNS. Not crazy about this option. Thanks, --Pat

Hello, This question is about best practice of introducing sambda-ad-dc to an organization that already has networking, and being minimally disruptive about it. I guess this question applies equally to adding a Windows AD server, but most people with that setup would let it be the primary DNS, etc. For this example: - Network: 172.18.0.0/24 - Domain: network...

Hello, I have now spent 30 hours trying to get this working, so it's time to get some professinoal help. :) In a nutshell, I would like to have a sambda AD PDC that authenticates both Windows and Debian. On Linux, I would like to use SSSD. I have followed the steps on the wiki: - https://wiki.samba.org/index.php/Samba_AD_DC_HOWTO - https://wiki.samba.org/index.php/Local_user_management_and_authentication/sssd Those worked great! The first allow...

On Thu, 12 Oct 2017 11:00:35 -0400 Pat Suwalski via samba <samba at lists.samba.org> wrote: > Hello, > > This question is about best practice of introducing sambda-ad-dc to > an organization that already has networking, and being minimally > disruptive about it. I guess this question applies equally to adding > a Windows AD server, but most people with that setup would let it be > the primary DNS, etc. > > For this example: > - Network:...

...as the DNS option over its DHCP server. The samba AD > server has its DNS forwarder set to "172.18.0.1". > > > The only thing to add is that 172.18.0.1 runs dnsmasq. samba is used with > Windows Desktops for AD and home shares, and with Linux servers for AD with > sssd (sambda's Winbind wasn't quite there when this was set up). Nothing > really relies on DNS from samba; unless you know something about this point > that I do not. > > I could also manually add the local entries to samba's DNS. Not crazy > about this option. > > Thanks, >...

On 2017-10-12 11:47 AM, Rowland Penny via samba wrote: > If you already have a domain, I would set up Active Directory as a > subdomain of this, e.g. instead of using 'network.ca', use > 'ad.network.ca' and the FQDN 'dc1.ad.network.ca' for the DC. Thanks for the reply. I think that ship's already sailed, the domain has been running as network.ca since Samba4

...ion over its DHCP > server. > The samba AD server has its DNS forwarder set to "172.18.0.1". > > > The only thing to add is that 172.18.0.1 runs dnsmasq. samba is used > with Windows Desktops for AD and home shares, and with Linux servers > for > AD with sssd (sambda's Winbind wasn't quite there when this was set > up). > Nothing really relies on DNS from samba; unless you know something > about > this point that I do not. > > I could also manually add the local entries to samba's DNS. Not > crazy > about this option. &gt...