Seguimi in Twitter Seguimi in Facebook Seguimi in Pinterest Seguimi in LinkedIn Seguimi in Google+ Seguimi  in Stumbleupon seguimi  in instagram Sottoscrivi il feed
Blender, graphic, software, open source, Linux LibreOffice, open source, openoffice Gimp, graphic, software, open source, Linux kernel, Linux, software, open source Linux, distributions, Ubuntu, Linux Mint, Fedora, Mandriva Jamin, gpl, library, open source matroska, multimedia, container, linux pcman, file manager, linux LuninuX, distribition, Linux, open source Linux, infographic, history
Home » » Samba HOWTO Collection: Fast Start, Cure for Impatience

Samba HOWTO Collection: Fast Start, Cure for Impatience

When we first asked for suggestions for inclusion in the Samba HOWTO documentation, someone wrote asking for example configurations — and lots of them. That is remarkably
di cult to do, without losing a lot of value that can be derived from presenting many extracts from working systems. That is what the rest of this document do es. It do es so with extensive descriptions of the configuration possibilities within the context of the chapter
that covers it. We hope that this chapter is the medicine that has been requested.

Features and Benefits

Samba needs very little configuration to create a basic working system. In this chapter we
progress from the simple to the complex, for each providing all steps and configuration file
changes needed to make each work. Please note that a comprehensively configured system
will likely employ additional smart features. The additional features are covered in the
remainder of this do cument.
The examples used here have been obtained from a number of people who made requests
for example configurations. All identities have been obscured to protect the guilty and any
resemblance to unreal non-existent sites is deliberate.

Description of Example Sites
In the first set of configuration examples we consider the case of exceptionally simple system
requirements. There is a real temptation to make something that should require little e ort
much to o complex.

Worked Examples

The next example is of a secure o ce file and print server that will be accessible only to users
who have an account on the system. This server is meant to closely resemble a Workgroup
file and print server, but has to be more secure than an anonymous access machine. This
type of system will typically suit the needs of a small o ce. The server does not provide
network logon facilities, o ers no Domain Control, instead it is just a network attached
storage (NAS) device and a print server.
Finally, we start lo oking at more complex systems that will either integrate into existing
Microsoft Windows networks, or replace them entirely. The examples provided cover domain
member servers as well as Samba Domain Control (PDC/BDC) and finally describes in detail
a large distributed network with branch o ces in remote lo cations.

The configuration examples are designed to cover everything necessary to get Samba run-
ning. They do not cover basic operating system platform configuration, which is clearly
beyond the scope of this text.
It is also assumed that Samba has been correctly installed, either by way of installation of
the packages that are provided by the operating system vendor, or through other means.

Stand-alone Server
A Stand-alone Server implies no more than the fact that it is not a Domain Controller and
it does not participate in Domain Control. It can be a simple workgroup-like server, or it
may be a complex server that is a member of a domain security context.

Anonymous Read-Only Document Server
The purpose of this type of server is to make available to any user any documents or files
that are placed on the shared resource. The shared resource could be a CD-ROM drive, a
CD-ROM image, or a file storage area.
As the examples are developed, every attempt is made to progress the system toward greater
capability, just as one might expect would happen in a real business o ce as that o ce grows
in size and its needs change.
The configuration file is:
• The file system share point will be /export.
• All files will be owned by a user called Jack Baumbach. Jack’s login name will be jackb.
His password will be m0r3pa1n — of course, that’s just the example we are using; do
not use this in a production environment because all readers of this document will
know it.
Installation Procedure Read-Only Server
1. Add user to system (with creation of the users’ home directory):

Anonymous Read-Only Server Configuration
# Global parameters
workgroup = MIDEARTH
netbios name = HOBBIT
security = share
comment = Data
path = /export
read only = Yes
guest ok = Yes
root# useradd -c "Jack Baumbach" -m -g users -p m0r3pa1n jackb
2. Create directory, and set permissions and ownership:
root# mkdir /export
root# chmod u+rwx,g+rx,o+rx /export
root# chown jackb.users /export
3. Copy the files that should be shared to the /export directory.
4. Install the Samba configuration file (/etc/samba/smb.conf) as shown.
5. Test the configuration file:
root# testparm
Note any error messages that might be pro duced. Do not proceed until you obtain
error-free output. An example of the output with the following file will list the file.
Load smb config files from /etc/samba/smb.conf
Processing section "[data]"
Loaded services file OK.
Press enter to see a dump of your service definitions
[Press enter]
# Global parameters
workgroup = MIDEARTH
netbios name = HOBBIT
security = share
comment = Data
path = /export
read only = Yes
guest only = Yes
6. Start Samba using the method applicable to your operating system platform.
7. Configure your Microsoft Windows client for workgroup MIDEARTH, set the machine
name to ROBBINS, rebo ot, wait a few (2 - 5) minutes, then open Windows Explorer
and visit the network neighborho od. The machine HOBBIT should be visible. When
you click this machine icon, it should open up to reveal the data share. After clicking
the share it, should open up to reveal the files previously placed in the /export
The information above (following # Global parameters) provides the complete contents of
the /etc/samba/smb.conf file.

Anonymous Read-Write Document Server
We should view this configuration as a progression from the previous example. The di erence
is that shared access is now forced to the user identity of jackb and to the primary group jackb
belongs to. One other refinement we can make is to add the user jackb to the smbpasswd
file. To do this execute:
root# smbpasswd -a jackb
New SMB password: m0r3pa1n
Retype new SMB password: m0r3pa1n
Added user jackb.
Addition of this user to the smbpasswd file allows all files to be displayed in the Explorer
Properties boxes as belonging to jackb instead of to User Unknown.

Anonymous Print Server
An anonymous print server serves two purposes:
• It allows printing to all printers from a single location.
• It reduces network tra c congestion due to many users trying to access a limited
number of printers.
In the simplest of anonymous print servers, it is common to require the installation of the
correct printer drivers on the Windows workstation. In this case the print server will be

Modified Anonymous Read-Write smb.conf
# Global parameters
workgroup = MIDEARTH
netbios name = HOBBIT
security = SHARE
comment = Data
path = /export
force user = jackb
force group = users
read only = No
guest ok = Yes
designed to just pass print jobs through to the spooler, and the spooler should be configured
to do raw pass-through to the printer. In other words, the print spooler should not filter or
pro cess the data stream being passed to the printer.
In this configuration it is undesirable to present the Add Printer Wizard and we do not
want to have automatic driver download, so we will disable it in the following configuration.
Example 2.3.3 is the resulting smb.conf file.
Example 2.3.3. Anonymous Print Server smb.conf
# Global parameters
workgroup = MIDEARTH
netbios name = LUTHIEN
security = share
printcap name = cups
disable spoolss = Yes
show add printer wizard = No
printing = cups
comment = All Printers
path = /var/spool/samba
guest ok = Yes
printable = Yes
use client driver = Yes
browseable = No
The above configuration is not ideal. It uses no smart features, and it deliberately presents
a less than elegant solution. But it is basic, and it does print.

Windows users will need to install a local printer and then change the
print to device after installation of the drivers. The print to device can
then be set to the network printer on this machine.
Make sure that the directory /var/spool/samba is capable of being used as intended. The
following steps must be taken to achieve this:
• The directory must be owned by the superuser (root) user and group:
root# chown root.root /var/spool/samba
• Directory permissions should be set for public read-write with the sticky-bit set as
root# chmod a+rw TX /var/spool/samba
On CUPS enabled systems there is a facility to pass raw data directly
to the printer without intermediate processing via CUPS print filters.
Where use of this mode of operation is desired it is necessary to config-
ure a raw printing device. It is also necessary to enable the raw mime
handler in the /etc/mime.conv and /etc/mime.types files.
Refer to

Secure Read-Write File and Print Server
We progress now from simple systems to a server that is slightly more complex.
Our new server will require a public data storage area in which only authenticated users
(i.e., those with a lo cal account) can store files, as well as a home directory. There will be
one printer that should be available for everyone to use.
In this hypothetical environment (no espionage was conducted to obtain this data), the site
is demanding a simple environment that is secure enough but not too di cult to use.

Site users will be: Jack Baumbach, Mary Orville and Amed Sehkah. Each will have a
password (not shown in further examples). Mary will be the printer administrator and will
own all files in the public share.
This configuration will be based on User Level Security that is the default, and for which
the default is to store Microsoft Windows-compatible encrypted passwords in a file called
/etc/samba/smbpasswd. The default smb.conf entry that makes this happen is: passdb
backend = smbpasswd, guest. Since this is the default it is not necessary to enter it into the
configuration file. Note that guest backend is added to the list of active passdb backends
not matter was it specified directly in Samba configuration file or not. Installing the Secure
O ce Server
1. Add all users to the Operating System:
root# useradd -c "Jack Baumbach" -m -g users -p m0r3pa1n jackb
root# useradd -c "Mary Orville" -m -g users -p secret maryo
root# useradd -c "Amed Sehkah" -m -g users -p secret ameds
2. Configure the Samba smb.conf file as shown in Example 2.3.4.
3. Initialize the Microsoft Windows password database with the new users:
root# smbpasswd -a root
New SMB password: bigsecret
Reenter smb password: bigsecret
Added user root.
root# smbpasswd -a jackb
New SMB password: m0r3pa1n
Retype new SMB password: m0r3pa1n
Added user jackb.
root# smbpasswd -a maryo
New SMB password: secret
Reenter smb password: secret
Added user maryo.
root# smbpasswd -a ameds
New SMB password: mysecret
Reenter smb password: mysecret
Added user ameds.
4. Install printer using the CUPS Web interface. Make certain that all printers that will
be shared with Microsoft Windows clients are installed as raw printing devices.
5. Start Samba using the operating system administrative interface. Alternately, this
can be done manually by running:
# Global parameters
workgroup = MIDEARTH
netbios name = OLORIN
printcap name = cups
disable spoolss = Yes
show add printer wizard = No
printing = cups
comment = Home Directories
valid users = %S
read only = No
browseable = No
comment = Data
path = /export
force user = maryo
force group = users
guest ok = Yes
read only = No
comment = All Printers
path = /var/spool/samba
printer admin = root, maryo
create mask = 0600
guest ok = Yes
printable = Yes
use client driver = Yes
browseable = No
root# nmbd; smbd;
6. Configure the /export directory:
root# mkdir /export
root# chown maryo.users /export
root# chmod u=rwx,g=rwx,o-rwx /export
7. Check that Samba is running correctly:
root# smbclient -L localhost -U%
Domain=[MIDEARTH] OS=[UNIX] Server=[Samba-3.0.0]
Sharename Type Comment
--------- ---- -------
public Disk Data
IPC$ IPC IPC Service (Samba-3.0.0)
ADMIN$ IPC IPC Service (Samba-3.0.0)
hplj4 Printer hplj4
Server Comment
--------- -------
OLORIN Samba-3.0.0
Workgroup Master
--------- -------
8. Connect to OLORIN as maryo:
root# smbclient //olorin/maryo -Umaryo%secret
OS=[UNIX] Server=[Samba-3.0.0]
smb: \> dir
D 0 Sat Jun 21 10:58:16 2003
D 0 Sat Jun 21 10:54:32 2003
D 0 Fri Apr 25 13:23:58 2003
D 0 Sat Jun 14 15:40:34 2003
OpenOffice.org D 0 Fri Apr 25 13:55:16 2003
H 1286 Fri Apr 25 13:23:58 2003
DH 0 Fri Apr 25 13:55:13 2003
DH 0 Wed Mar 5 11:50:50 2003
H 164 Fri Apr 25 13:23:58 2003
DH 0 Fri Apr 25 15:41:02 2003
55817 blocks of size 524288. 34725 blocks available
smb: \> q
By now you should be getting the hang of configuration basics. Clearly, it is time to explore
slightly more complex examples. For the remainder of this chapter we will abbreviate
instructions since there are previous examples.
2.3.2 Domain Member Server
In this instance we will consider the simplest server configuration we can get away with to
make an accounting department happy. Let’s be warned, the users are accountants and they
do have some nasty demands. There is a budget for only one server for this department.
The network is managed by an internal Information Services Group (ISG), to which we
belong. Internal politics are typical of a medium-sized organization; Human Resources is
of the opinion that they run the ISG because they are always adding and disabling users.
Also, departmental managers have to fight to oth and nail to gain basic network resources
access for their sta . Accounting is di erent though, they get exactly what they want. So
this should set the scene.
We will use the users from the last example. The accounting department has a general
printer that all departmental users may. There is also a check printer that may be used only
by the person who has authority to print checks. The Chief Financial O cer (CFO) wants
that printer to be completely restricted and for it to be located in the private storage area
in her o ce. It therefore must be a network printer.
Accounting department uses an accounting application called SpytFull that must be run
from a central application server. The software is licensed to run only o one server, there
are no workstation components, and it is run o a mapped share. The data store is in a
UNIX-based SQL backend. The UNIX gurus look after that, so is not our problem.
The accounting department manager (maryo) wants a general filing system as well as a
separate file storage area for form letters (nastygrams). The form letter area should be
read-only to all accounting sta except the manager. The general filing system has to have
a structured layout with a general area for all sta to store general documents, as well as a
separate file area for each member of her team that is private to that person, but she wants
full access to all areas. Users must have a private home share for personal work-related files
and for materials not related to departmental operations.

he server valinor will be a member server of the company domain. Accounting will have
only a local server. User accounts will be on the Domain Controllers as will desktop profiles
and all network policy files.
1. Do not add users to the UNIX/Linux server; all of this will run o the central domain.
2. Configure smb.conf according to Example 2.3.5 and Example 2.3.6.
3. Join the domain. Note: Do not start Samba until this step has been completed!
root# net rpc join -Uroot%’bigsecret’
Joined domain MIDEARTH.
4. Make absolutely certain that you disable (shut down) the nscd daemon on any system
on which winbind is configured to run.
5. Start Samba following the normal method for your operating system platform. If you
wish to this manually execute as ro ot:
# Global parameters
workgroup = MIDEARTH
netbios name = VALINOR
security = DOMAIN
printcap name = cups
disable spoolss = Yes
show add printer wizard = No
idmap uid = 15000-20000
idmap gid = 15000-20000
winbind use default domain = Yes
use sendfile = Yes
printing = cups
root# nmbd; smbd; winbindd;
6. Configure the name service switch control file on your system to resolve user and group
names via winbind. Edit the following lines in /etc/nsswitch.conf:
passwd: files winbind
group: files winbind
hosts: files dns winbind
7. Set the password for wbinfo to use:
root# wbinfo --set-auth-user=root%’bigsecret’
8. Validate that domain user and group credentials can be correctly resolved by executing:
root# wbinfo -u
root# wbinfo -g
MIDEARTH\Domain Users
MIDEARTH\Domain Admins
MIDEARTH\Domain Guests

Section 2.3. Worked Examples
Example 2.3.6. Member server smb.conf (shares and services)
comment = Home Directories
valid users = %S
read only = No
browseable = No
comment = Accounting Application Only
path = /export/spytfull
valid users = @Accounts
admin users = maryo
read only = Yes
comment = Data
path = /export/public
read only = No
comment = All Printers
path = /var/spool/samba
printer admin = root, maryo
create mask = 0600
guest ok = Yes
printable = Yes
use client driver = Yes
browseable = No
9. Check that winbind is working. The following demonstrates correct username reso-
lution via the getent system utility:
root# getent passwd maryo
maryo:x:15000:15003:Mary Orville:/home/MIDEARTH/maryo:/bin/false
10. A final test that we have this under control might be reassuring:
root# touch /export/a_file
root# chown maryo /export/a_file
root# ls -al /export/a_file

Fast Start: Cure for Impatience Chapter 2
-rw-r--r-- 1 maryo users 11234 Jun 21 15:32 a_file
root# rm /export/a_file

11. Configuration is now mostly complete, so this is an opportune time to configure the
directory structure for this site:
root# mkdir -p /export/{spytfull,public}
root# chmod ug=rwxS,o=x /export/{spytfull,public}
root# chown maryo.Accounts /export/{spytfull,public}
2.3.3 Domain Controller
For the remainder of this chapter the fo cus is on the configuration of Domain Control. The
examples that follow are for two implementation strategies. Remember, our objective is to
create a simple but working solution. The remainder of this book should help to highlight
opportunity for greater functionality and the complexity that go es with it.
A Domain Controller configuration can be achieved with a simple configuration using the
new tdbsam password backend. This type of configuration is go od for small o ces, but has
limited scalability (cannot be replicated) and performance can be expected to fall as the
size and complexity of the domain increases.
The use of tdbsam is best limited to sites that do not need more than a primary Domain
Controller (PDC). As the size of a domain grows the need for additional Domain Controllers
becomes apparent. Do not attempt to under-resource a Microsoft Windows network envi-
ronment; Domain Controllers provide essential authentication services. The following are
symptoms of an under-resourced Domain Control environment:
• Domain logons intermittently fail.
• File access on a Domain Member server intermittently fails, giving a permission denied
error message.
A more scalable Domain Control authentication backend option might use Microsoft Active
Directory, or an LDAP-based backend. Samba-3 provides for both options as a Domain
Member server. As a PDC Samba-3 is not able to provide an exact alternative to the
functionality that is available with Active Directory. Samba-3 can provide a scalable LDAP-
based PDC/BDC solution.
The tdbsam authentication backend provides no facility to replicate the contents of the
database, except by external means. (i.e., there is no self-contained protocol in Samba-3 for
Security Account Manager database [SAM] replication.)

Section 2.3. Worked Examples
If you need more than one Domain Controller, do not use a tdbsam
authentication backend. Example: Engineering O ce
The engineering o ce network server we present here is designed to demonstrate use of the
new tdbsam password backend. The tdbsam facility is new to Samba-3. It is designed to
provide many user and machine account controls that are possible with Microsoft Windows
NT4. It is safe to use this in smaller networks.
1. A working PDC configuration using the tdbsam password backend can be found in
Example 2.3.7 together with Example 2.3.8:
Example 2.3.7. Engineering O ce smb.conf (globals)
workgroup = MIDEARTH
netbios name = FRODO
passdb backend = tdbsam
printcap name = cups
add user script = /usr/sbin/useradd -m %u
delete user script = /usr/sbin/userdel -r %u
add group script = /usr/sbin/groupadd %g
delete group script = /usr/sbin/groupdel %g
add user to group script = /usr/sbin/usermod -G %g %u
add machine script = /usr/sbin/useradd -s /bin/false \
-d /dev/null %u
# Note: The following specifies the default logon script.
# Per user logon scripts can be specified in the user account using pdbedit
logon script = scripts\logon.bat
# This sets the default profile path. Set per user paths with pdbedit
logon path = \\%L\Profiles\%U
logon drive = H:
logon home = \\%L\%U
domain logons = Yes
os level = 35
preferred master = Yes
domain master = Yes
idmap uid = 15000-20000
idmap gid = 15000-20000
printing = cups

Fast Start: Cure for Impatience Chapter 2
2. Create UNIX group accounts as needed using a suitable operating system tool:
root# groupadd ntadmins
root# groupadd designers
root# groupadd engineers
root# groupadd qateam
3. Create user accounts on the system using the appropriate tool provided with the
operating system. Make sure all user home directories are created also. Add users to
groups as required for access control on files, directories, printers, and as required for
use in the Samba environment.
4. Assign each of the UNIX groups to NT groups: (It may be useful to copy this text to
a shell script called initGroups.sh.) Shell script for initializing group mappings
#### Keep this as a shell script for future re-use
# First assign well known groups
net groupmap modify ntgroup="Domain Admins" unixgroup=ntadmins rid=512
net groupmap modify ntgroup="Domain Users" unixgroup=users rid=513
net groupmap modify ntgroup="Domain Guests" unixgroup=nobody rid=514
# Now for our added Domain Groups
net groupmap add ntgroup="Designers" unixgroup=designers type=d rid=1112
net groupmap add ntgroup="Engineers" unixgroup=engineers type=d rid=1113
net groupmap add ntgroup="QA Team" unixgroup=qateam type=d rid=1114
5. Create the scripts directory for use in the [NETLOGON] share:
root# mkdir -p /var/lib/samba/netlogon/scripts
Place the logon scripts that will be used (batch or cmd scripts) in this directory.
The above configuration provides a functional Primary Domain Control (PDC) system to
which must be added file shares and printers as required. A Big Organization
In this section we finally get to review in brief a Samba-3 configuration that uses a Light
Weight Directory Access (LDAP)-based authentication backend. The main reasons for this
choice are to provide the ability to host primary and Backup Domain Control (BDC), as
well as to enable a higher degree of scalability to meet the needs of a very distributed

Section 2.3. Worked Examples
The Primary Domain Controller This is an example of a minimal configuration to run a
Samba-3 PDC using an LDAP authentication backend. It is assumed that the operating
system has been correctly configured.
The Idealx scripts (or equivalent) are needed to manage LDAP based Posix and/or Sam-
baSamAccounts. The Idealx scripts may be downloaded from the Idealx Web site. They may also be obtained from the Samba tarball. Linux distri-
butions tend to install the Idealx scripts in the /usr/share/doc/packages/sambaXXXXXX/
examples/LDAP/smbldap-tools directory. Idealx scripts version smbldap-tools-0.8.2 are
known to work well.
1. Obtain from the Samba sources ~/examples/LDAP/samba.schema and copy it to the
/etc/openldap/schema/ directory.
2. Set up the LDAP server. This example is suitable for OpenLDAP 2.1.x. The /etc/
openldap/slapd.conf file: Example slapd.conf file
# Note commented out lines have been removed
include /etc/openldap/schema/core.schema
include /etc/openldap/schema/cosine.schema
include /etc/openldap/schema/inetorgperson.schema
include /etc/openldap/schema/nis.schema
include /etc/openldap/schema/samba.schema
pidfile /var/run/slapd/slapd.pid
argsfile /var/run/slapd/slapd.args
database bdb
suffix "dc=quenya,dc=org"
rootdn "cn=Manager,dc=quenya,dc=org"
rootpw {SSHA}06qDkonA8hk6W6SSnRzWj0/pBcU3m0/P
# The password for the above is ’nastyon3’
directory /var/lib/ldap
index objectClass eq
index cn
index sn
index uid
index displayName pres,sub,eq
index uidNumber eq
index gidNumber eq
index memberUid eq
index sambaSID eq
index sambaPrimaryGroupSID eq
index sambaDomainName eq
index default sub

Fast Start: Cure for Impatience Chapter 2
3. Create the following file samba-ldap-init.ldif:
# Organization for SambaXP Demo
dn: dc=quenya,dc=org
objectclass: dcObject
objectclass: organization
dc: quenya
o: SambaXP Demo
description: The SambaXP Demo LDAP Tree
# Organizational Role for Directory Management
dn: cn=Manager,dc=quenya,dc=org
objectclass: organizationalRole
cn: Manager
description: Directory Manager
# Setting up the container for users
dn: ou=People, dc=quenya, dc=org
objectclass: top
objectclass: organizationalUnit
ou: People
# Set up an admin handle for People OU
dn: cn=admin, ou=People, dc=quenya, dc=org
cn: admin
objectclass: top
objectclass: organizationalRole
objectclass: simpleSecurityObject
userPassword: {SSHA}0jBHgQ1vp4EDX2rEMMfIudvRMJoGwjVb
# The password for above is ’mordonL8’
4. Load the initial data above into the LDAP database:
root# slapadd -v -l initdb.ldif
5. Start the LDAP server using the appropriate to ol or metho d for the operating system
platform on which it is installed.
6. Install the Idealx script files in the /usr/local/sbin directory, then configure the
smbldap conf.pm file to match your system configuration.
7. The smb.conf file that drives this backend can be found in example Example 2.3.9.
8. Add the LDAP password to the secrets.tdc file so Samba can update the LDAP
root# smbpasswd -w mordonL8

Section 2.3. Worked Examples
9. Add users and groups as required. Users and groups added using Samba to ols will
automatically be added to both the LDAP backend as well as to the operating system
as required.
Backup Domain Controller Example 2.3.10 shows the example configuration for the BDC.
1. Decide if the BDC should have its own LDAP server or not. If the BDC is to be the
LDAP server change the following smb.conf as indicated. The default configuration
in Example 2.3.10 uses a central LDAP server.
2. Configure the NETLOGON and PROFILES directory as for the PDC in Exam-
ple 2.3.10.

Fast Start: Cure for Impatience Chapter 2
Example 2.3.8. Engineering O ce smb.conf (shares and services)
comment = Home Directories
valid users = %S
read only = No
browseable = No
# Printing auto-share (makes printers available thru CUPS)
comment = All Printers
path = /var/spool/samba
printer admin = root, maryo
create mask = 0600
guest ok = Yes
printable = Yes
browseable = No
comment = Printer Drivers Share
path = /var/lib/samba/drivers
write list = maryo, root
printer admin = maryo, root
# Needed to support domain logons
comment = Network Logon Service
path = /var/lib/samba/netlogon
admin users = root, maryo
guest ok = Yes
browseable = No
# For profiles to work, create a user directory under the path
# shown. i.e., mkdir -p /var/lib/samba/profiles/maryo
comment = Roaming Profile Share
path = /var/lib/samba/profiles
read only = No
profile acls = Yes
# Other resource (share/printer) definitions would follow below.

Section 2.3. Worked Examples
Example 2.3.9. LDAP backend smb.conf for PDC
# Global parameters
workgroup = MIDEARTH
netbios name = FRODO
passdb backend = ldapsam:ldap://localhost
username map = /etc/samba/smbusers
printcap name = cups
add user script = /usr/local/sbin/smbldap-useradd.pl -m ’%u’
delete user script = /usr/local/sbin/smbldap-userdel.pl %u
add group script = /usr/local/sbin/smbldap-groupadd.pl -p ’%g’
delete group script = /usr/local/sbin/smbldap-groupdel.pl ’%g’
add user to group script = /usr/local/sbin/ \
smbldap-groupmod.pl -m ’%g’ ’%u’
delete user from group script = /usr/local/sbin/ \
smbldap-groupmod.pl -x ’%g’ ’%u’
set primary group script = /usr/local/sbin/ \
smbldap-usermod.pl -g ’%g’ ’%u’
add machine script = /usr/local/sbin/smbldap-useradd.pl -w ’%u’
logon script = scripts\logon.bat
logon path = \\%L\Profiles\%U
logon drive = H:
logon home = \\%L\%U
domain logons = Yes
os level = 35
preferred master = Yes
domain master = Yes
ldap suffix = dc=quenya,dc=org
ldap machine suffix = ou=People
ldap user suffix = ou=People
ldap group suffix = ou=People
ldap idmap suffix = ou=People
ldap admin dn = cn=Manager
ldap ssl = no
ldap passwd sync = Yes
idmap uid = 15000-20000
idmap gid = 15000-20000
printing = cups

Fast Start: Cure for Impatience Chapter 2
Example 2.3.10. Remote LDAP BDC smb.conf
# Global parameters
workgroup = MIDEARTH
netbios name = GANDALF
passdb backend = ldapsam:ldap://frodo.quenya.org
username map = /etc/samba/smbusers
printcap name = cups
logon script = scripts\logon.bat
logon path = \\%L\Profiles\%U
logon drive = H:
logon home = \\%L\%U
domain logons = Yes
os level = 33
preferred master = Yes
domain master = No
ldap suffix = dc=quenya,dc=org
ldap machine suffix = ou=People
ldap user suffix = ou=People
ldap group suffix = ou=People
ldap idmap suffix = ou=People
ldap admin dn = cn=Manager
ldap ssl = no
ldap passwd sync = Yes
idmap uid = 15000-20000
idmap gid = 15000-20000
printing = cups

Related Post

Yahoo!    Personals

123inkjets.com    - Printer Ink, Toner, & More

  • Get Paid     to Blog About the Things You Love

iPowerWeb    Web Hosting

Linux Links

0 commenti:

Post a Comment

Random Posts

My Blog List

Recent Posts

Recent Posts Widget

Popular Posts




Images Photo Gallery

page counter Mi Ping en TotalPing.com
Copyright © 2014 Linuxlandit & The Conqueror Penguin