[Samba] Samba4 acting as standalone server, smb.conf parameters and run daemons !
rowlandpenny at googlemail.com
Fri Feb 28 09:39:36 MST 2014
On 28/02/14 16:14, Computer service SPb. wrote:
> Rowland, you are not right. I started and start nmbd daemon with samba
> But I don' t know requirements for server services as for started
> daemons for standalone server.
> 2014-02-28 14:44 GMT+04:00 Rowland Penny <rowlandpenny at googlemail.com
> <mailto:rowlandpenny at googlemail.com>>:
> On 28/02/14 09:24, Denis Cardon wrote:
> Hi Computer service SPb
> > I have built Samba4 4.1.5 from sources and provisioned as
> server. I don' t need to act Samba4 as DC.
> I need fully working server, including shares access,
> network neighborhood
> browsing, LDAP (I suupose it should be anyway by default) .
> LDAP is used in DC environment to store user, group, machine
> accounts and many other things. If you are planning to have a
> simple workgroup server, I think your users should be stored
> in standard SAM like tdb files, like in the 3.x serie.
> What values should be added to smb.conf, in particular to
> server services ?
> Is dcerpc endpoint servers parameter necassary ?
> What daemons should be started,smbd, nmbd, winbindd, samba ?
> "samba" process is for DC role, so you shouldn't need it. I
> have no experience of running nmbd independantly of "samba"
> process, in a DC environmenent smbd et nmbd are started
> automatically by "samba" process. And there is some caveat
> with the samba4 version of winbind.
> If you provision samba4 with 'samba-tool domain provision' you can
> then only start the samba daemon, this in turn starts the smbd
> daemon, the daemons nmbd & winbindd will not start at all, even if
> you try to!
> If you want to use samba4 as a standalone server, just follow the
> howtos out on the internet for samba3, but refer to 'man smb.conf'
> to ensure that the parameters in smb.conf are still valid etc.
> Where is able to read for it.
> Because of there is info for Samba4 DC in the most
> internet resources.
> samba4 developpement is focused on DC support, so that is
> Hope this helps,
Sorry for that, but I could have sworn that nmbd was made to not run if
the samba daemon was running. If the samba daemon is running, you should
not run the nmbd or winbind daemons.
If you want a 'classic samba' setup, you can run the smbd, nmbd and
winbind daemons, just like an S3 setup, you just shouldn't try to start
any of these daemons manually if you start the samba daemon.
So, to try and explain it:
Starting the samba daemon and the smbd daemon that it starts
automatically = Active Directory server
Start the smbd, nmbd and possibly the winbind daemons = anything that a
samba3 setup can do i.e. a standalone machine, PDC server, client etc.
More information about the samba