1
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
5
>Configuring Server Settings</TITLE
8
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
11
TITLE="Samba Server Configuration"
12
HREF="index.html"><LINK
15
HREF="intro.html"><LINK
17
TITLE="Managing Samba Users"
18
HREF="users.html"><LINK
21
HREF="rhdocs-man.css"></HEAD
32
SUMMARY="Header navigation table"
41
>Samba Server Configuration</TH
78
>Chapter 2. Configuring Server Settings</H1
80
> The first step in configuring a Samba server is to configure the
81
basic settings for the server and a few security options. After
82
starting the application, select <B
93
> tab is displayed as shown in
95
HREF="configuring.html#FIG-SAMBA-BASIC"
102
NAME="FIG-SAMBA-BASIC"
108
SRC="./figs/r-c-samba-basic.png"></P
112
>Figure 2-1. Configuring Basic Server Settings</B
119
> tab, specify which workgroup the
120
computer should be in as well as a brief description of the
121
computer. They correspond to the <TT
137
NAME="FIG-SAMBA-SECURITY"
143
SRC="./figs/r-c-samba-security.png"></P
147
>Figure 2-2. Configuring Security Server Settings</B
154
> tab contains the following
164
>Authentication Mode</B
166
corresponds to the <TT
170
one of the following types of authentication.</P
179
> — The Samba server acts
180
as a domain member in an Active Directory Domain (ADS)
181
realm. For this option, Kerberos must be installed and
182
configured on the server, and Samba must become a member of
183
the ADS realm using the <TT
191
package. Refer to the <TT
195
details. This option does not configure Samba to be an ADS
203
> — The Samba server
204
relies on a Windows NT Primary or Backup Domain Controller to
205
verify the user. The server passes the username and password
206
to the Controller and waits for it to return. Specify the
207
NetBIOS name of the Primary or Backup Domain Controller in the
210
>Authentication Server</B
215
>Encrypted Passwords</B
220
> if this is selected.</P
227
> — The Samba server
228
tries to verify the username and password combination by
229
passing them to another Samba server. If it can not, the
230
server tries to verify using the user authentication
231
mode. Specify the NetBIOS name of the other Samba server in
234
>Authentication Server</B
242
> — Samba users do not
243
have to enter a username and password combination on a per
244
Samba server basis. They are not prompted for a username and
245
password until they try to connect to a specific shared
246
directory from a Samba server.</P
253
> — (Default) Samba users
254
must provide a valid username and password on a per Samba
255
server basis. Select this option if you want the
259
> option to work. Refer
263
>Managing Samba Users</I
273
>Encrypt Passwords</B
274
> — This option
275
must be enabled if the clients are connecting from a Windows 98,
276
Windows NT 4.0 with Service Pack 3, or other more recent
277
versions of Microsoft Windows. The passwords are transfered
278
between the server and the client in an encrypted format instead
279
of in as a plain-text word that can be intercepted. This
280
corresponds to the <TT
282
>encrypted passwords</TT
291
> — When users or
292
guest users log into a Samba server, they must be mapped to a
293
valid user on the server. Select one of the existing usernames on
294
the system to be the guest Samba account. When guests logs in to
295
the Samba server, they have the same privileges as this
296
user. This corresponds to the <TT
307
>, the changes are written to
308
the configuration file and the daemon is restart; thus, the changes
309
take effect immediately.
317
SUMMARY="Footer navigation table"
366
>Managing Samba Users</TD
b'\\ No newline at end of file'
added
removed
doc/configuring.html
