[Samba] How can I setup a Domain Controller and File Server on the same hardware

Linda W samba at tlinx.org
Sat Nov 5 19:15:49 UTC 2016

Marc Muehlfeld via samba wrote:
> Hi John,
> Am 05.11.2016 um 17:33 schrieb John te Bokkel via samba:
>> I understand from the wiki that I shouldn't have the domain controller also
>> be the file server.
>> Is it possible to to setup the domain controller in a chroot and have the
>> file server run under regular root?
>> Would it be better to setup a VM for the domain controller and have file
>> server run on the main OS or vice-versa?
> to run two Samba instances on the same host, you can create a NIC alias
> with an additional IP address and bind the Samba DC to one IP and the
> file server to the second. Of course you need two separate smb.conf
> files and configure individual database directories. And then start the
> daemons with the "-c" parameter and the path to the smb.conf file.
    Is there a target date for when the 4.x server will be able to
support 1 samba instance being the domain controller and serving files
as the 3.x server is able to do?

    I have been waiting for the 4.x server to become a full server
before upgrading from 3.6.22, but it is getting a bit long in the tooth.
The requirement that in upgrading to 4.x I'll still need to run
a 3.6 server made the upgrade seem like alot of work for little gain
(I only have a few users and most of them are "virtual me's"...).

    I guess I don't understand why the 3.6.x file-serving code wasn't
just included in the 4.x.  On some level, at *worst*, it seems like
the 4.x code could include all the 3.6 file-serving code and just fork the
that portion for files to be shared -- not ideal, but it *seems*
better than "recommending" multiple machines.  I did say "seems",
as I don't know why it is suggested they be separate, so please
forgive my ignorance in advance.  I've been off the list (not by choice)
due to some mail-server snafu that only affects the samba list, so
it's been impossible to track.  For some reason the problem has, (at
least temporarily) gone away (I hate unexplained solutions almost as
much as unexplained problems).



More information about the samba mailing list