<title>Miscellaneous Controls</title>
<para>
- The parameter documented in <link linkend="mcoc">Other Controls</link> are often used by administrators
+ The parameters documented in <link linkend="mcoc">Other Controls</link> are often used by administrators
in ways that create inadvertent barriers to file access. Such are the consequences of not understanding the
full implications of &smb.conf; file settings.
</para>
<indexterm><primary>ACLs on share</primary></indexterm>
<indexterm><primary>Sharing</primary></indexterm>
<indexterm><primary>Permissions</primary></indexterm>
- On <application>MS Windows NT4/200x/XP</application> system, ACLs on the share itself are set using native
- tools, usually from File Manager. For example, in Windows 200x, right-click on the shared folder,
+ On <application>MS Windows NT4/200x/XP</application> systems, ACLs on the share itself are set using
+ tools like the MS Explorer. For example, in Windows 200x, right-click on the shared folder,
then select <guimenuitem>Sharing</guimenuitem>, then click on <guilabel>Permissions</guilabel>. The default
- Windows NT4/200x permission allows "Everyone" full control on the share.
+ Windows NT4/200x permissions allow the group "Everyone" full control on the share.
</para>
<para>
<indexterm><primary>MMC</primary></indexterm>
<indexterm><primary>tool</primary></indexterm>
MS Windows 200x and later versions come with a tool called the <application>Computer Management</application>
- snap-in for the MMC. This tool is located by clicking on <guimenu>Control Panel ->
+ snap-in for the MMC. This tool can be accessed via <guimenu>Control Panel ->
Administrative Tools -> Computer Management</guimenu>.
</para>
<indexterm><primary>NetServerEnum2</primary></indexterm>
<indexterm><primary>synchronization</primary></indexterm>
<indexterm><primary>browse lists</primary></indexterm>
-Once N2_B knows the address of the DMB, it tells it that is the LMB for subnet 2 by sending a
-<emphasis>MasterAnnouncement</emphasis> packet as a UDP port 138 packet. It then synchronizes with it by
-doing a <emphasis>NetServerEnum2</emphasis> call. This tells the DMB to send it all the server names it knows
+Once N2_B knows the address of the DMB, it tells the DMB that it is the LMB
+for subnet 2 by sending the DMB a
+<emphasis>MasterAnnouncement</emphasis> packet to UDP port 138. It then
+synchronizes with the DMB by
+doing a <emphasis>NetServerEnum2</emphasis> call. This tells the DMB to
+send the sender all the server names it knows
about. Once the DMB receives the <emphasis>MasterAnnouncement</emphasis> packet, it schedules a
synchronization request to the sender of that packet. After both synchronizations are complete, the browse
lists look like those in <link linkend="brsbex">Browse Subnet Example 2</link>
Windows networking user account names are case-insensitive, meaning that upper-case and lower-case characters
in the account name are considered equivalent. They are said to be case-preserving, but not case significant.
Windows and LanManager systems previous to Windows NT version 3.10 have case-insensitive passwords that were
-not necessarilty case-preserving. All Windows NT family systems treat passwords as case-preserving and
+not necessarily case-preserving. All Windows NT family systems treat passwords as case-preserving and
case-sensitive.
</para>
In share-level security, the client authenticates itself separately for each share. It sends a password along
with each tree connection request (share mount), but it does not explicitly send a username with this
operation. The client expects a password to be associated with each share, independent of the user. This means
-that Samba has to work out what username the client probably wants to use, the SMB server is not explicitly
-sent the username. Some commercial SMB servers such as NT actually associate passwords directly with shares
+that Samba has to work out what username the client probably wants to use,
+because the username is not explicitly sent to the SMB server. Some commercial SMB servers such as NT actually associate passwords directly with shares
in share-level security, but Samba always uses the UNIX authentication scheme where it is a username/password
pair that is authenticated, not a share/password pair.
</para>
git.samba.org / amitay / samba.git / commitdiff