1 # This is the main Samba configuration file. You should read the
2 # smb.conf(5) manual page in order to understand the options listed
3 # here. Samba has a huge number of configurable options (perhaps too
4 # many!) most of which are not shown in this example
6 # For a step to step guide on installing, configuring and using samba,
7 # read the Samba-HOWTO-Collection. This may be obtained from:
8 # http://www.samba.org/samba/docs/Samba-HOWTO-Collection.pdf
10 # Many working examples of smb.conf files can be found in the
11 # Samba-Guide which is generated daily and can be downloaded from:
12 # http://www.samba.org/samba/docs/Samba-Guide.pdf
14 # Any line which starts with a ; (semi-colon) or a # (hash)
15 # is a comment and is ignored. In this example we will use a #
16 # for commentry and a ; for parts of the config file that you
19 # NOTE: Whenever you modify this file you should run the command "testparm"
20 # to check that you have not made any basic syntactic errors.
22 #======================= Global Settings =====================================
25 # workgroup = NT-Domain-Name or Workgroup-Name, eg: MIDEARTH
28 # server string is the equivalent of the NT Description field
29 server string = Samba Server
31 # Server role. Defines in which mode Samba will operate. Possible
32 # values are "standalone server", "member server", "classic primary
33 # domain controller", "classic backup domain controller", "active
34 # directory domain controller".
36 # Most people will want "standalone sever" or "member server".
37 # Running as "active directory domain controller" will require first
38 # running "samba-tool domain provision" to wipe databases and create a
40 server role = standalone server
42 # This option is important for security. It allows you to restrict
43 # connections to machines which are on your local network. The
44 # following example restricts access to two C class networks and
45 # the "loopback" interface. For more examples of the syntax see
46 # the smb.conf man page
47 ; hosts allow = 192.168.1. 192.168.2. 127.
49 # Uncomment this if you want a guest account, you must add this to /etc/passwd
50 # otherwise the user "nobody" is used
51 ; guest account = pcguest
53 # this tells Samba to use a separate log file for each machine
55 log file = /usr/local/samba/var/log.%m
57 # Put a capping on the size of the log files (in Kb).
60 # Use password server option only with security = server
61 # The argument list may include:
62 # password server = My_PDC_Name [My_BDC_Name] [My_Next_BDC_Name]
63 # or to auto-locate the domain controller/s
65 ; password server = <NT-Server-Name>
67 # Use the realm option only with security = ads
68 # Specifies the Active Directory realm the host is part of
71 # Backend to store user information in. New installations should
72 # use either tdbsam or ldapsam. smbpasswd is available for backwards
73 # compatibility. tdbsam requires no further configuration.
74 ; passdb backend = tdbsam
76 # Using the following line enables you to customise your configuration
77 # on a per machine basis. The %m gets replaced with the netbios name
78 # of the machine that is connecting.
79 # Note: Consider carefully the location in the configuration file of
80 # this line. The included file is read at that point.
81 ; include = /usr/local/samba/lib/smb.conf.%m
83 # Configure Samba to use multiple interfaces
84 # If you have multiple network interfaces then you must list them
85 # here. See the man page for details.
86 ; interfaces = 192.168.12.2/24 192.168.13.2/24
88 # Browser Control Options:
89 # set local master to no if you don't want Samba to become a master
90 # browser on your network. Otherwise the normal election rules apply
93 # OS Level determines the precedence of this server in master browser
94 # elections. The default value should be reasonable
97 # Domain Master specifies Samba to be the Domain Master Browser. This
98 # allows Samba to collate browse lists between subnets. Don't use this
99 # if you already have a Windows NT domain controller doing this job
100 ; domain master = yes
102 # Preferred Master causes Samba to force a local browser election on startup
103 # and gives it a slightly higher chance of winning the election
104 ; preferred master = yes
106 # Enable this if you want Samba to be a domain logon server for
107 # Windows95 workstations.
108 ; domain logons = yes
110 # if you enable domain logons then you may want a per-machine or
111 # per user logon script
112 # run a specific logon batch file per workstation (machine)
113 ; logon script = %m.bat
114 # run a specific logon batch file per username
115 ; logon script = %U.bat
117 # Where to store roving profiles (only for Win95 and WinNT)
118 # %L substitutes for this servers netbios name, %U is username
119 # You must uncomment the [Profiles] share below
120 ; logon path = \\%L\Profiles\%U
122 # Windows Internet Name Serving Support Section:
123 # WINS Support - Tells the NMBD component of Samba to enable it's WINS Server
126 # WINS Server - Tells the NMBD components of Samba to be a WINS Client
127 # Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
128 ; wins server = w.x.y.z
130 # WINS Proxy - Tells Samba to answer name resolution queries on
131 # behalf of a non WINS capable client, for this to work there must be
132 # at least one WINS Server on the network. The default is NO.
135 # DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names
136 # via DNS nslookups. The default is NO.
139 # These scripts are used on a domain controller or stand-alone
140 # machine to add or delete corresponding unix accounts
141 ; add user script = /usr/sbin/useradd %u
142 ; add group script = /usr/sbin/groupadd %g
143 ; add machine script = /usr/sbin/adduser -n -g machines -c Machine -d /dev/null -s /bin/false %u
144 ; delete user script = /usr/sbin/userdel %u
145 ; delete user from group script = /usr/sbin/deluser %u %g
146 ; delete group script = /usr/sbin/groupdel %g
149 #============================ Share Definitions ==============================
151 comment = Home Directories
155 # Un-comment the following and create the netlogon directory for Domain Logons
157 ; comment = Network Logon Service
158 ; path = /usr/local/samba/lib/netlogon
164 # Un-comment the following to provide a specific roving profile share
165 # the default is to use the user's home directory
167 ; path = /usr/local/samba/profiles
172 # NOTE: If you have a BSD-style print system there is no need to
173 # specifically define each individual printer
175 comment = All Printers
176 path = /usr/spool/samba
178 # Set public = yes to allow user 'guest account' to print
183 # This one is useful for people to share files
185 ; comment = Temporary file space
190 # A publicly accessible directory, but read only, except for people in
193 ; comment = Public Stuff
198 ; write list = @staff
202 # A private printer, usable only by fred. Spool data will be placed in fred's
203 # home directory. Note that fred must have write access to the spool directory,
206 ; comment = Fred's Printer
209 ; printer = freds_printer
214 # A private directory, usable only by fred. Note that fred requires write
215 # access to the directory.
217 ; comment = Fred's Service
218 ; path = /usr/somewhere/private
224 # a service which has a different directory for each machine that connects
225 # this allows you to tailor configurations to incoming machines. You could
226 # also use the %U option to tailor it by user name.
227 # The %m gets replaced with the machine name that is connecting.
229 ; comment = PC Directories
234 # A publicly accessible directory, read/write to all users. Note that all files
235 # created in the directory by users will be owned by the default user, so
236 # any user with access can delete any other user's files. Obviously this
237 # directory must be writable by the default user. Another user could of course
238 # be specified, in which case all files would be owned by that user instead.
240 ; path = /usr/somewhere/else/public
246 # The following two entries demonstrate how to share a directory so that two
247 # users can place files there that will be owned by the specific users. In this
248 # setup, the directory should be writable by both users and should have the
249 # sticky bit set on it to prevent abuse. Obviously this could be extended to
250 # as many users as required.
252 ; comment = Mary's and Fred's stuff
253 ; path = /usr/somewhere/shared
254 ; valid users = mary fred