diff options
| author | Jelmer Vernooij <jelmer@samba.org> | 2003-02-18 22:14:04 +0000 |
|---|---|---|
| committer | Jelmer Vernooij <jelmer@samba.org> | 2003-02-18 22:14:04 +0000 |
| commit | ff78c3bf5c3a73cf90f6517d9b2d6b8c12d22d68 (patch) | |
| tree | deda0311c634bd433278a352e1a9daece40ff0f6 /docs/htmldocs | |
| parent | 4668623d62b3a7b133e26dd1397b956c4ddac335 (diff) | |
| download | samba-ff78c3bf5c3a73cf90f6517d9b2d6b8c12d22d68.tar.gz samba-ff78c3bf5c3a73cf90f6517d9b2d6b8c12d22d68.tar.bz2 samba-ff78c3bf5c3a73cf90f6517d9b2d6b8c12d22d68.zip | |
Regenerate
(This used to be commit 1ab5a3b17feb677425bb1071357c3dbabcc46c7e)
Diffstat (limited to 'docs/htmldocs')
64 files changed, 12359 insertions, 8466 deletions
diff --git a/docs/htmldocs/Samba-Developers-Guide.html b/docs/htmldocs/Samba-Developers-Guide.html index b90d99bf66..5d9702e49e 100644 --- a/docs/htmldocs/Samba-Developers-Guide.html +++ b/docs/htmldocs/Samba-Developers-Guide.html @@ -5,7 +5,7 @@ >SAMBA Developers Guide</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77"></HEAD +CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"></HEAD ><BODY CLASS="BOOK" BGCOLOR="#FFFFFF" @@ -687,7 +687,7 @@ HREF="#AEN2925" ><DT >10.4. <A HREF="#AEN2959" ->ChangeID & Client Caching of Printer Information</A +>ChangeID and Client Caching of Printer Information</A ></DT ><DT >10.5. <A @@ -810,7 +810,26 @@ HREF="#AEN3162" ><A NAME="SMBPASSWDFILEFORMAT" ></A ->The smbpasswd file</A +>>The smbpasswd file</A +></DT +></DL +></DD +><DT +>14. <A +HREF="#RPC-PLUGIN" +>RPC Pluggable Modules</A +></DT +><DD +><DL +><DT +>14.1. <A +HREF="#AEN3225" +>About</A +></DT +><DT +>14.2. <A +HREF="#AEN3228" +>General Overview</A ></DT ></DL ></DD @@ -915,7 +934,7 @@ NAME="AEN39" of, a 'NetBIOS Name Service'. NT/AS offers 'Windows Internet Name Service' which is fully rfc1001/2 compliant, but has had to take specific action with certain NetBIOS names in order to make it useful. (for example, it -deals with the registration of <1c> <1d> <1e> names all in different ways. +deals with the registration of <1c> <1d> <1e> names all in different ways. I recommend the reading of the Microsoft WINS Server Help files for full details).</P ><P @@ -2533,7 +2552,7 @@ NAME="AEN540" ><P >This is a short document that describes some of the issues that confront a SMB implementation on unix, and how Samba copes with -them. They may help people who are looking at unix<->PC +them. They may help people who are looking at unix<->PC interoperability.</P ><P >It was written to help out a person who was writing a paper on unix to @@ -2881,14 +2900,14 @@ example, if I'm using a csh style shell:</P ><P ><B CLASS="COMMAND" ->strace -f -p 3872 >& strace.out</B +>strace -f -p 3872 >& strace.out</B ></P ><P >or with a sh style shell:</P ><P ><B CLASS="COMMAND" ->strace -f -p 3872 > strace.out 2>&1</B +>strace -f -p 3872 > strace.out 2>&1</B ></P ><P >Note the "-f" option. This is only available on some systems, and @@ -6985,7 +7004,7 @@ CLASS="emphasis" ><I CLASS="EMPHASIS" >Note: mailslots will contain a response mailslot, to which the response - should be sent. the target NetBIOS name is REQUEST_NAME<20>, where + should be sent. the target NetBIOS name is REQUEST_NAME<20>, where REQUEST_NAME is the name of the machine that sent the request.</I ></SPAN ></P @@ -7650,18 +7669,18 @@ NAME="AEN2699" ></A >9.7.2. Protocol</H3 ><P ->C->S ReqChal,Cc S->C Cs</P +>C->S ReqChal,Cc S->C Cs</P ><P ->C & S compute session key Ks = E(PW[9..15],E(PW[0..6],Add(Cc,Cs)))</P +>C & S compute session key Ks = E(PW[9..15],E(PW[0..6],Add(Cc,Cs)))</P ><P >C: Rc = Cred(Ks,Cc) C->S Authenticate,Rc S: Rs = Cred(Ks,Cs), -assert(Rc == Cred(Ks,Cc)) S->C Rs C: assert(Rs == Cred(Ks,Cs))</P +assert(Rc == Cred(Ks,Cc)) S->C Rs C: assert(Rs == Cred(Ks,Cs))</P ><P >On joining the domain the client will optionally attempt to change its password and the domain controller may refuse to update it depending on registry settings. This will also occur weekly afterwards.</P ><P ->C: Tc = Time(), Rc' = Cred(Ks,Rc+Tc) C->S ServerPasswordSet,Rc',Tc, +>C: Tc = Time(), Rc' = Cred(Ks,Rc+Tc) C->S ServerPasswordSet,Rc',Tc, arc4(Ks[0..7,16],lmowf(randompassword()) C: Rc = Cred(Ks,Rc+Tc+1) S: assert(Rc' == Cred(Ks,Rc+Tc)), Ts = Time() S: Rs' = Cred(Ks,Rs+Tc+1) S->C Rs',Ts C: assert(Rs' == Cred(Ks,Rs+Tc+1)) S: Rs = Rs'</P @@ -7669,7 +7688,7 @@ S->C Rs',Ts C: assert(Rs' == Cred(Ks,Rs+Tc+1)) S: Rs = Rs'</P >User: U with password P wishes to login to the domain (incidental data such as workstation and domain omitted)</P ><P ->C: Tc = Time(), Rc' = Cred(Ks,Rc+Tc) C->S NetLogonSamLogon,Rc',Tc,U, +>C: Tc = Time(), Rc' = Cred(Ks,Rc+Tc) C->S NetLogonSamLogon,Rc',Tc,U, arc4(Ks[0..7,16],16,ntowf(P),16), arc4(Ks[0..7,16],16,lmowf(P),16) S: assert(Rc' == Cred(Ks,Rc+Tc)) assert(passwords match those in SAM) S: Ts = Time()</P @@ -8355,7 +8374,7 @@ CLASS="SECT1" ><A NAME="AEN2959" ></A ->10.4. ChangeID & Client Caching of Printer Information</H2 +>10.4. ChangeID and Client Caching of Printer Information</H2 ><P >[To be filled in later]</P ></DIV @@ -8676,8 +8695,7 @@ accessed.</P >For example, when you call </P ><PRE CLASS="PROGRAMLISTING" ->< -NTSTATUS sam_get_account_by_name(const SAM_CONTEXT *context, const +>NTSTATUS sam_get_account_by_name(const SAM_CONTEXT *context, const NT_USER_TOKEN *access_token, uint32 access_desired, const char *domain, const char *name, SAM_ACCOUNT_HANDLE **account)</PRE ><P @@ -9102,7 +9120,7 @@ NAME="AEN3162" >13.3. <A NAME="SMBPASSWDFILEFORMAT" ></A ->The smbpasswd file</H2 +>>The smbpasswd file</H2 ><P >In order for Samba to participate in the above protocol it must be able to look up the 16 byte hashed values given a user name. @@ -9131,7 +9149,7 @@ CLASS="FILENAME" CLASS="FILENAME" >/etc/passwd </TT -> file use the following command :</P +> file use the following command:</P ><P ><TT CLASS="PROMPT" @@ -9302,6 +9320,97 @@ CLASS="FILENAME" > file.</P ></DIV ></DIV +><DIV +CLASS="CHAPTER" +><HR><H1 +><A +NAME="RPC-PLUGIN" +></A +>Chapter 14. RPC Pluggable Modules</H1 +><DIV +CLASS="SECT1" +><H2 +CLASS="SECT1" +><A +NAME="AEN3225" +></A +>14.1. About</H2 +><P +>This document describes how to make use the new RPC Pluggable Modules features +of Samba 3.0. This architecture was added to increase the maintainability of +Samba allowing RPC Pipes to be worked on separately from the main CVS branch. +The RPM architecture will also allow third-party vendors to add functionality +to Samba through plug-ins.</P +></DIV +><DIV +CLASS="SECT1" +><HR><H2 +CLASS="SECT1" +><A +NAME="AEN3228" +></A +>14.2. General Overview</H2 +><P +>When an RPC call is sent to smbd, smbd tries to load a shared library by the +name <TT +CLASS="FILENAME" +>librpc_<pipename>.so</TT +> to handle the call if +it doesn't know how to handle the call internally. For instance, LSA calls +are handled by <TT +CLASS="FILENAME" +>librpc_lsass.so</TT +>.. +These shared libraries should be located in the <TT +CLASS="FILENAME" +><sambaroot>/lib/rpc</TT +>. smbd then attempts to call the rpc_pipe_init function within +the shared library.</P +><P +>In the rpc_pipe_init function, the library should call +rpc_pipe_register_commands(). This function takes the following arguments:</P +><P +><PRE +CLASS="PROGRAMLISTING" +>int rpc_pipe_register_commands(const char *clnt, const char *srv, + const struct api_struct *cmds, int size);</PRE +></P +><P +></P +><DIV +CLASS="VARIABLELIST" +><DL +><DT +>clnt</DT +><DD +><P +>the Client name of the named pipe</P +></DD +><DT +>srv</DT +><DD +><P +>the Server name of the named pipe</P +></DD +><DT +>cmds</DT +><DD +><P +>a list of api_structs that map RPC ordinal numbers to function calls</P +></DD +><DT +>size</DT +><DD +><P +>the number of api_structs contained in cmds</P +></DD +></DL +></DIV +><P +>See rpc_server/srv_reg.c and rpc_server/srv_reg_nt.c for a small example of +how to use this library.</P +></DIV +></DIV ></DIV ></BODY ></HTML diff --git a/docs/htmldocs/Samba-HOWTO-Collection.html b/docs/htmldocs/Samba-HOWTO-Collection.html index 2bb324d9f3..d758fbbe11 100644 --- a/docs/htmldocs/Samba-HOWTO-Collection.html +++ b/docs/htmldocs/Samba-HOWTO-Collection.html @@ -5,7 +5,7 @@ >SAMBA Project Documentation</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77"></HEAD +CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"></HEAD ><BODY CLASS="BOOK" BGCOLOR="#FFFFFF" @@ -45,7 +45,7 @@ CLASS="emphasis" CLASS="EMPHASIS" >Last Update</I ></SPAN -> : Thu Aug 15 12:48:45 CDT 2002</P +> : Wed Jan 15</P ><P >This book is a collection of HOWTOs added to Samba documentation over the years. I try to ensure that all are current, but sometimes the is a larger job @@ -59,6 +59,11 @@ on the "Documentation" page. Please send updates to <A HREF="mailto:jerry@samba.org" TARGET="_top" >jerry@samba.org</A +> or +<A +HREF="mailto:jelmer@samba.org" +TARGET="_top" +>jelmer@samba.org</A >.</P ><P >This documentation is distributed under the GNU General Public License (GPL) @@ -79,7 +84,7 @@ CLASS="TOC" ></DT ><DT >I. <A -HREF="#AEN18" +HREF="#INTRODUCTION" >General installation</A ></DT ><DD @@ -93,27 +98,27 @@ HREF="#INSTALL" ><DL ><DT >1.1. <A -HREF="#AEN25" +HREF="#AEN26" >Read the man pages</A ></DT ><DT >1.2. <A -HREF="#AEN35" +HREF="#AEN36" >Building the Binaries</A ></DT ><DT >1.3. <A -HREF="#AEN63" +HREF="#AEN64" >The all important step</A ></DT ><DT >1.4. <A -HREF="#AEN67" +HREF="#AEN68" >Create the smb configuration file.</A ></DT ><DT >1.5. <A -HREF="#AEN81" +HREF="#AEN82" >Test your config file with <B CLASS="COMMAND" @@ -122,171 +127,118 @@ CLASS="COMMAND" ></DT ><DT >1.6. <A -HREF="#AEN89" +HREF="#AEN90" >Starting the smbd and nmbd</A ></DT ><DT >1.7. <A -HREF="#AEN144" +HREF="#AEN145" >Try listing the shares available on your server</A ></DT ><DT >1.8. <A -HREF="#AEN153" +HREF="#AEN154" >Try connecting with the unix client</A ></DT ><DT >1.9. <A -HREF="#AEN169" +HREF="#AEN170" >Try connecting from a DOS, WfWg, Win9x, WinNT, Win2k, OS/2, etc... client</A ></DT ><DT >1.10. <A -HREF="#AEN183" +HREF="#AEN184" >What If Things Don't Work?</A ></DT ></DL ></DD ><DT >2. <A -HREF="#IMPROVED-BROWSING" ->Improved browsing in samba</A +HREF="#BROWSING-QUICK" +>Quick Cross Subnet Browsing / Cross Workgroup Browsing guide</A ></DT ><DD ><DL ><DT >2.1. <A -HREF="#AEN228" ->Overview of browsing</A +HREF="#AEN230" +>Discussion</A ></DT ><DT >2.2. <A -HREF="#AEN232" ->Browsing support in samba</A +HREF="#AEN238" +>Use of the "Remote Announce" parameter</A ></DT ><DT >2.3. <A -HREF="#AEN241" ->Problem resolution</A +HREF="#AEN252" +>Use of the "Remote Browse Sync" parameter</A ></DT ><DT >2.4. <A -HREF="#AEN248" ->Browsing across subnets</A +HREF="#AEN257" +>Use of WINS</A ></DT ><DT >2.5. <A -HREF="#AEN288" ->Setting up a WINS server</A +HREF="#AEN268" +>Do NOT use more than one (1) protocol on MS Windows machines</A ></DT ><DT >2.6. <A -HREF="#AEN307" ->Setting up Browsing in a WORKGROUP</A -></DT -><DT ->2.7. <A -HREF="#AEN325" ->Setting up Browsing in a DOMAIN</A -></DT -><DT ->2.8. <A -HREF="#AEN335" ->Forcing samba to be the master</A -></DT -><DT ->2.9. <A -HREF="#AEN344" ->Making samba the domain master</A -></DT -><DT ->2.10. <A -HREF="#AEN362" ->Note about broadcast addresses</A -></DT -><DT ->2.11. <A -HREF="#AEN365" ->Multiple interfaces</A +HREF="#AEN274" +>Name Resolution Order</A ></DT ></DL ></DD ><DT >3. <A -HREF="#OPLOCKS" ->Oplocks</A +HREF="#PASSDB" +>User information database</A ></DT ><DD ><DL ><DT >3.1. <A -HREF="#AEN377" ->What are oplocks?</A -></DT -></DL -></DD -><DT ->4. <A -HREF="#BROWSING-QUICK" ->Quick Cross Subnet Browsing / Cross Workgroup Browsing guide</A -></DT -><DD -><DL -><DT ->4.1. <A -HREF="#AEN392" ->Discussion</A -></DT -><DT ->4.2. <A -HREF="#AEN400" ->Use of the "Remote Announce" parameter</A -></DT -><DT ->4.3. <A -HREF="#AEN414" ->Use of the "Remote Browse Sync" parameter</A +HREF="#AEN324" +>Introduction</A ></DT ><DT ->4.4. <A -HREF="#AEN419" ->Use of WINS</A +>3.2. <A +HREF="#AEN331" +>Important Notes About Security</A ></DT ><DT ->4.5. <A -HREF="#AEN430" ->Do NOT use more than one (1) protocol on MS Windows machines</A +>3.3. <A +HREF="#AEN357" +>The smbpasswd Command</A ></DT ><DT ->4.6. <A -HREF="#AEN436" ->Name Resolution Order</A +>3.4. <A +HREF="#AEN388" +>Plain text</A ></DT -></DL -></DD ><DT ->5. <A -HREF="#PWENCRYPT" ->LanMan and NT Password Encryption in Samba</A +>3.5. <A +HREF="#AEN393" +>TDB</A ></DT -><DD -><DL ><DT ->5.1. <A -HREF="#AEN472" ->Introduction</A +>3.6. <A +HREF="#AEN396" +>LDAP</A ></DT ><DT ->5.2. <A -HREF="#AEN477" ->Important Notes About Security</A +>3.7. <A +HREF="#AEN614" +>MySQL</A ></DT ><DT ->5.3. <A -HREF="#AEN512" ->The smbpasswd Command</A +>3.8. <A +HREF="#AEN662" +>Passdb XML plugin</A ></DT ></DL ></DD @@ -294,169 +246,174 @@ HREF="#AEN512" ></DD ><DT >II. <A -HREF="#AEN544" +HREF="#TYPE" >Type of installation</A ></DT ><DD ><DL ><DT ->6. <A +>4. <A +HREF="#SECURITYLEVELS" +>User and Share security level (for servers not in a domain)</A +></DT +><DT +>5. <A HREF="#SAMBA-PDC" ->How to Configure Samba as a NT4 Primary Domain Controller</A +>Samba as a NT4 or Win2k Primary Domain Controller</A ></DT ><DD ><DL ><DT ->6.1. <A -HREF="#AEN566" +>5.1. <A +HREF="#AEN722" >Prerequisite Reading</A ></DT ><DT ->6.2. <A -HREF="#AEN572" +>5.2. <A +HREF="#AEN728" >Background</A ></DT ><DT ->6.3. <A -HREF="#AEN611" +>5.3. <A +HREF="#AEN767" >Configuring the Samba Domain Controller</A ></DT ><DT ->6.4. <A -HREF="#AEN654" +>5.4. <A +HREF="#AEN810" >Creating Machine Trust Accounts and Joining Clients to the Domain</A ></DT ><DT ->6.5. <A -HREF="#AEN738" +>5.5. <A +HREF="#AEN894" >Common Problems and Errors</A ></DT ><DT ->6.6. <A -HREF="#AEN786" +>5.6. <A +HREF="#AEN942" >System Policies and Profiles</A ></DT ><DT ->6.7. <A -HREF="#AEN830" +>5.7. <A +HREF="#AEN986" >What other help can I get?</A ></DT ><DT ->6.8. <A -HREF="#AEN944" +>5.8. <A +HREF="#AEN1100" >Domain Control for Windows 9x/ME</A ></DT ><DT ->6.9. <A -HREF="#AEN1082" ->DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba</A +>5.9. <A +HREF="#AEN1238" +>DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba</A ></DT ></DL ></DD ><DT ->7. <A +>6. <A HREF="#SAMBA-BDC" >How to Act as a Backup Domain Controller in a Purely Samba Controlled Domain</A ></DT ><DD ><DL ><DT ->7.1. <A -HREF="#AEN1118" +>6.1. <A +HREF="#AEN1274" >Prerequisite Reading</A ></DT ><DT ->7.2. <A -HREF="#AEN1122" +>6.2. <A +HREF="#AEN1278" >Background</A ></DT ><DT ->7.3. <A -HREF="#AEN1130" +>6.3. <A +HREF="#AEN1286" >What qualifies a Domain Controller on the network?</A ></DT ><DT ->7.4. <A -HREF="#AEN1139" ->Can Samba be a Backup Domain Controller?</A +>6.4. <A +HREF="#AEN1295" +>Can Samba be a Backup Domain Controller to an NT PDC?</A ></DT ><DT ->7.5. <A -HREF="#AEN1143" +>6.5. <A +HREF="#AEN1300" >How do I set up a Samba BDC?</A ></DT ></DL ></DD ><DT ->8. <A +>7. <A HREF="#ADS" >Samba as a ADS domain member</A ></DT ><DD ><DL ><DT ->8.1. <A -HREF="#AEN1178" +>7.1. <A +HREF="#AEN1339" >Installing the required packages for Debian</A ></DT ><DT ->8.2. <A -HREF="#AEN1184" +>7.2. <A +HREF="#AEN1346" >Installing the required packages for RedHat</A ></DT ><DT ->8.3. <A -HREF="#AEN1193" +>7.3. <A +HREF="#AEN1356" >Compile Samba</A ></DT ><DT ->8.4. <A -HREF="#AEN1205" +>7.4. <A +HREF="#AEN1371" >Setup your /etc/krb5.conf</A ></DT ><DT ->8.5. <A -HREF="#AEN1215" +>7.5. <A +HREF="#AEN1381" >Create the computer account</A ></DT ><DT ->8.6. <A -HREF="#AEN1231" +>7.6. <A +HREF="#AEN1393" >Test your server setup</A ></DT ><DT ->8.7. <A -HREF="#AEN1236" +>7.7. <A +HREF="#AEN1398" >Testing with smbclient</A ></DT ><DT ->8.8. <A -HREF="#AEN1239" +>7.8. <A +HREF="#AEN1401" >Notes</A ></DT ></DL ></DD ><DT ->9. <A +>8. <A HREF="#DOMAIN-SECURITY" ->Samba as a NT4 domain member</A +>Samba as a NT4 or Win2k domain member</A ></DT ><DD ><DL ><DT ->9.1. <A -HREF="#AEN1261" ->Joining an NT Domain with Samba 2.2</A +>8.1. <A +HREF="#AEN1423" +>Joining an NT Domain with Samba 3.0</A ></DT ><DT ->9.2. <A -HREF="#AEN1325" +>8.2. <A +HREF="#AEN1478" >Samba and Windows 2000 Domains</A ></DT ><DT ->9.3. <A -HREF="#AEN1330" +>8.3. <A +HREF="#AEN1481" >Why is this better than security = server?</A ></DT ></DL @@ -465,101 +422,101 @@ HREF="#AEN1330" ></DD ><DT >III. <A -HREF="#AEN1346" +HREF="#OPTIONAL" >Optional configuration</A ></DT ><DD ><DL ><DT ->10. <A +>9. <A HREF="#INTEGRATE-MS-NETWORKS" >Integrating MS Windows networks with Samba</A ></DT ><DD ><DL ><DT ->10.1. <A -HREF="#AEN1362" +>9.1. <A +HREF="#AEN1513" >Agenda</A ></DT ><DT ->10.2. <A -HREF="#AEN1384" +>9.2. <A +HREF="#AEN1535" >Name Resolution in a pure Unix/Linux world</A ></DT ><DT ->10.3. <A -HREF="#AEN1447" +>9.3. <A +HREF="#AEN1598" >Name resolution as used within MS Windows networking</A ></DT ><DT ->10.4. <A -HREF="#AEN1492" +>9.4. <A +HREF="#AEN1643" >How browsing functions and how to deploy stable and dependable browsing using Samba</A ></DT ><DT ->10.5. <A -HREF="#AEN1502" +>9.5. <A +HREF="#AEN1653" >MS Windows security options and how to configure Samba for seemless integration</A ></DT ><DT ->10.6. <A -HREF="#AEN1572" +>9.6. <A +HREF="#AEN1723" >Conclusions</A ></DT ></DL ></DD ><DT ->11. <A +>10. <A HREF="#UNIX-PERMISSIONS" >UNIX Permission Bits and Windows NT Access Control Lists</A ></DT ><DD ><DL ><DT ->11.1. <A -HREF="#AEN1593" +>10.1. <A +HREF="#AEN1744" >Viewing and changing UNIX permissions using the NT security dialogs</A ></DT ><DT ->11.2. <A -HREF="#AEN1602" +>10.2. <A +HREF="#AEN1748" >How to view file security on a Samba share</A ></DT ><DT ->11.3. <A -HREF="#AEN1613" +>10.3. <A +HREF="#AEN1759" >Viewing file ownership</A ></DT ><DT ->11.4. <A -HREF="#AEN1633" +>10.4. <A +HREF="#AEN1779" >Viewing file or directory permissions</A ></DT ><DT ->11.5. <A -HREF="#AEN1669" +>10.5. <A +HREF="#AEN1815" >Modifying file or directory permissions</A ></DT ><DT ->11.6. <A -HREF="#AEN1691" +>10.6. <A +HREF="#AEN1837" >Interaction with the standard Samba create mask parameters</A ></DT ><DT ->11.7. <A -HREF="#AEN1755" +>10.7. <A +HREF="#AEN1901" >Interaction with the standard Samba file attribute mapping</A ></DT ></DL ></DD ><DT ->12. <A +>11. <A HREF="#PAM" >Configuring PAM for distributed but centrally managed authentication</A @@ -567,350 +524,301 @@ managed authentication</A ><DD ><DL ><DT ->12.1. <A -HREF="#AEN1776" +>11.1. <A +HREF="#AEN1922" >Samba and PAM</A ></DT ><DT ->12.2. <A -HREF="#AEN1820" +>11.2. <A +HREF="#AEN1966" >Distributed Authentication</A ></DT ><DT ->12.3. <A -HREF="#AEN1827" +>11.3. <A +HREF="#AEN1973" >PAM Configuration in smb.conf</A ></DT ></DL ></DD ><DT ->13. <A +>12. <A HREF="#MSDFS" >Hosting a Microsoft Distributed File System tree on Samba</A ></DT ><DD ><DL ><DT ->13.1. <A -HREF="#AEN1847" +>12.1. <A +HREF="#AEN1993" >Instructions</A ></DT ></DL ></DD ><DT ->14. <A +>13. <A HREF="#PRINTING" >Printing Support</A ></DT ><DD ><DL ><DT ->14.1. <A -HREF="#AEN1908" +>13.1. <A +HREF="#AEN2054" >Introduction</A ></DT ><DT ->14.2. <A -HREF="#AEN1930" +>13.2. <A +HREF="#AEN2076" >Configuration</A ></DT ><DT ->14.3. <A -HREF="#AEN2038" +>13.3. <A +HREF="#AEN2184" >The Imprints Toolset</A ></DT ><DT ->14.4. <A -HREF="#AEN2081" +>13.4. <A +HREF="#AEN2227" >Diagnosis</A ></DT ></DL ></DD ><DT ->15. <A -HREF="#SECURITYLEVELS" ->Security levels</A -></DT -><DD -><DL -><DT ->15.1. <A -HREF="#AEN2186" ->Introduction</A -></DT -><DT ->15.2. <A -HREF="#AEN2197" ->More complete description of security levels</A -></DT -></DL -></DD -><DT ->16. <A +>14. <A HREF="#WINBIND" >Unified Logons between Windows NT and UNIX using Winbind</A ></DT ><DD ><DL ><DT ->16.1. <A -HREF="#AEN2249" +>14.1. <A +HREF="#AEN2360" >Abstract</A ></DT ><DT ->16.2. <A -HREF="#AEN2253" +>14.2. <A +HREF="#AEN2364" >Introduction</A ></DT ><DT ->16.3. <A -HREF="#AEN2266" +>14.3. <A +HREF="#AEN2377" >What Winbind Provides</A ></DT ><DT ->16.4. <A -HREF="#AEN2277" +>14.4. <A +HREF="#AEN2388" >How Winbind Works</A ></DT ><DT ->16.5. <A -HREF="#AEN2317" +>14.5. <A +HREF="#AEN2431" >Installation and Configuration</A ></DT ><DT ->16.6. <A -HREF="#AEN2566" +>14.6. <A +HREF="#AEN2680" >Limitations</A ></DT ><DT ->16.7. <A -HREF="#AEN2576" +>14.7. <A +HREF="#AEN2690" >Conclusion</A ></DT ></DL ></DD ><DT ->17. <A -HREF="#PDB-MYSQL" ->Passdb MySQL plugin</A +>15. <A +HREF="#IMPROVED-BROWSING" +>Improved browsing in samba</A ></DT ><DD ><DL ><DT ->17.1. <A -HREF="#AEN2590" ->Building</A -></DT -><DT ->17.2. <A -HREF="#AEN2596" ->Configuring</A -></DT -><DT ->17.3. <A -HREF="#AEN2611" ->Using plaintext passwords or encrypted password</A -></DT -><DT ->17.4. <A -HREF="#AEN2616" ->Getting non-column data from the table</A +>15.1. <A +HREF="#AEN2700" +>Overview of browsing</A ></DT -></DL -></DD ><DT ->18. <A -HREF="#PDB-XML" ->Passdb XML plugin</A +>15.2. <A +HREF="#AEN2704" +>Browsing support in samba</A ></DT -><DD -><DL ><DT ->18.1. <A -HREF="#AEN2635" ->Building</A +>15.3. <A +HREF="#AEN2713" +>Problem resolution</A ></DT ><DT ->18.2. <A -HREF="#AEN2641" ->Usage</A +>15.4. <A +HREF="#AEN2720" +>Browsing across subnets</A ></DT -></DL -></DD ><DT ->19. <A -HREF="#SAMBA-LDAP-HOWTO" ->Storing Samba's User/Machine Account information in an LDAP Directory</A +>15.5. <A +HREF="#AEN2760" +>Setting up a WINS server</A ></DT -><DD -><DL ><DT ->19.1. <A -HREF="#AEN2664" ->Purpose</A +>15.6. <A +HREF="#AEN2779" +>Setting up Browsing in a WORKGROUP</A ></DT ><DT ->19.2. <A -HREF="#AEN2684" ->Introduction</A +>15.7. <A +HREF="#AEN2797" +>Setting up Browsing in a DOMAIN</A ></DT ><DT ->19.3. <A -HREF="#AEN2713" ->Supported LDAP Servers</A +>15.8. <A +HREF="#AEN2807" +>Forcing samba to be the master</A ></DT ><DT ->19.4. <A -HREF="#AEN2718" ->Schema and Relationship to the RFC 2307 posixAccount</A +>15.9. <A +HREF="#AEN2816" +>Making samba the domain master</A ></DT ><DT ->19.5. <A -HREF="#AEN2730" ->Configuring Samba with LDAP</A +>15.10. <A +HREF="#AEN2834" +>Note about broadcast addresses</A ></DT ><DT ->19.6. <A -HREF="#AEN2777" ->Accounts and Groups management</A +>15.11. <A +HREF="#AEN2837" +>Multiple interfaces</A ></DT +></DL +></DD ><DT ->19.7. <A -HREF="#AEN2782" ->Security and sambaAccount</A +>16. <A +HREF="#VFS" +>Stackable VFS modules</A ></DT +><DD +><DL ><DT ->19.8. <A -HREF="#AEN2802" ->LDAP specials attributes for sambaAccounts</A +>16.1. <A +HREF="#AEN2855" +>Introduction and configuration</A ></DT ><DT ->19.9. <A -HREF="#AEN2872" ->Example LDIF Entries for a sambaAccount</A +>16.2. <A +HREF="#AEN2864" +>Included modules</A ></DT ><DT ->19.10. <A -HREF="#AEN2880" ->Comments</A +>16.3. <A +HREF="#AEN2918" +>VFS modules available elsewhere</A ></DT ></DL ></DD ><DT ->20. <A +>17. <A HREF="#CVS-ACCESS" ->HOWTO Access Samba source code via CVS</A +>Access Samba source code via CVS</A ></DT ><DD ><DL ><DT ->20.1. <A -HREF="#AEN2891" +>17.1. <A +HREF="#AEN2942" >Introduction</A ></DT ><DT ->20.2. <A -HREF="#AEN2896" +>17.2. <A +HREF="#AEN2947" >CVS Access to samba.org</A ></DT ></DL ></DD ><DT ->21. <A +>18. <A HREF="#GROUPMAPPING" >Group mapping HOWTO</A ></DT ><DT ->22. <A +>19. <A HREF="#SPEED" >Samba performance issues</A ></DT ><DD ><DL ><DT ->22.1. <A -HREF="#AEN2982" +>19.1. <A +HREF="#AEN3033" >Comparisons</A ></DT ><DT ->22.2. <A -HREF="#AEN2988" ->Oplocks</A -></DT -><DT ->22.3. <A -HREF="#AEN3008" +>19.2. <A +HREF="#AEN3039" >Socket options</A ></DT ><DT ->22.4. <A -HREF="#AEN3015" +>19.3. <A +HREF="#AEN3046" >Read size</A ></DT ><DT ->22.5. <A -HREF="#AEN3020" +>19.4. <A +HREF="#AEN3051" >Max xmit</A ></DT ><DT ->22.6. <A -HREF="#AEN3025" ->Locking</A -></DT -><DT ->22.7. <A -HREF="#AEN3029" ->Share modes</A -></DT -><DT ->22.8. <A -HREF="#AEN3034" +>19.5. <A +HREF="#AEN3056" >Log level</A ></DT ><DT ->22.9. <A -HREF="#AEN3037" ->Wide lines</A -></DT -><DT ->22.10. <A -HREF="#AEN3040" +>19.6. <A +HREF="#AEN3059" >Read raw</A ></DT ><DT ->22.11. <A -HREF="#AEN3045" +>19.7. <A +HREF="#AEN3064" >Write raw</A ></DT ><DT ->22.12. <A -HREF="#AEN3049" ->Read prediction</A +>19.8. <A +HREF="#AEN3068" +>Slow Clients</A ></DT ><DT ->22.13. <A -HREF="#AEN3056" ->Memory mapping</A +>19.9. <A +HREF="#AEN3072" +>Slow Logins</A ></DT ><DT ->22.14. <A -HREF="#AEN3061" ->Slow Clients</A +>19.10. <A +HREF="#AEN3075" +>Client tuning</A ></DT +></DL +></DD ><DT ->22.15. <A -HREF="#AEN3065" ->Slow Logins</A +>20. <A +HREF="#GROUPPROFILES" +>Creating Group Profiles</A ></DT +><DD +><DL ><DT ->22.16. <A -HREF="#AEN3068" ->Client tuning</A +>20.1. <A +HREF="#AEN3123" +>Windows '9x</A +></DT +><DT +>20.2. <A +HREF="#AEN3132" +>Windows NT 4</A ></DT ><DT ->22.17. <A -HREF="#AEN3100" ->My Results</A +>20.3. <A +HREF="#AEN3170" +>Windows 2000/XP</A ></DT ></DL ></DD @@ -918,138 +826,138 @@ HREF="#AEN3100" ></DD ><DT >IV. <A -HREF="#AEN3106" +HREF="#APPENDIXES" >Appendixes</A ></DT ><DD ><DL ><DT ->23. <A +>21. <A HREF="#PORTABILITY" >Portability</A ></DT ><DD ><DL ><DT ->23.1. <A -HREF="#AEN3115" +>21.1. <A +HREF="#AEN3251" >HPUX</A ></DT ><DT ->23.2. <A -HREF="#AEN3121" +>21.2. <A +HREF="#AEN3257" >SCO Unix</A ></DT ><DT ->23.3. <A -HREF="#AEN3125" +>21.3. <A +HREF="#AEN3261" >DNIX</A ></DT ><DT ->23.4. <A -HREF="#AEN3154" +>21.4. <A +HREF="#AEN3290" >RedHat Linux Rembrandt-II</A ></DT ></DL ></DD ><DT ->24. <A +>22. <A HREF="#OTHER-CLIENTS" >Samba and other CIFS clients</A ></DT ><DD ><DL ><DT ->24.1. <A -HREF="#AEN3175" +>22.1. <A +HREF="#AEN3311" >Macintosh clients?</A ></DT ><DT ->24.2. <A -HREF="#AEN3184" +>22.2. <A +HREF="#AEN3320" >OS2 Client</A ></DT ><DT ->24.3. <A -HREF="#AEN3224" +>22.3. <A +HREF="#AEN3360" >Windows for Workgroups</A ></DT ><DT ->24.4. <A -HREF="#AEN3245" +>22.4. <A +HREF="#AEN3381" >Windows '95/'98</A ></DT ><DT ->24.5. <A -HREF="#AEN3261" +>22.5. <A +HREF="#AEN3397" >Windows 2000 Service Pack 2</A ></DT ></DL ></DD ><DT ->25. <A +>23. <A HREF="#BUGREPORT" >Reporting Bugs</A ></DT ><DD ><DL ><DT ->25.1. <A -HREF="#AEN3285" +>23.1. <A +HREF="#AEN3421" >Introduction</A ></DT ><DT ->25.2. <A -HREF="#AEN3295" +>23.2. <A +HREF="#AEN3431" >General info</A ></DT ><DT ->25.3. <A -HREF="#AEN3301" +>23.3. <A +HREF="#AEN3437" >Debug levels</A ></DT ><DT ->25.4. <A -HREF="#AEN3318" +>23.4. <A +HREF="#AEN3454" >Internal errors</A ></DT ><DT ->25.5. <A -HREF="#AEN3328" +>23.5. <A +HREF="#AEN3464" >Attaching to a running process</A ></DT ><DT ->25.6. <A -HREF="#AEN3331" +>23.6. <A +HREF="#AEN3467" >Patches</A ></DT ></DL ></DD ><DT ->26. <A +>24. <A HREF="#DIAGNOSIS" >Diagnosing your samba server</A ></DT ><DD ><DL ><DT ->26.1. <A -HREF="#AEN3354" +>24.1. <A +HREF="#AEN3490" >Introduction</A ></DT ><DT ->26.2. <A -HREF="#AEN3359" +>24.2. <A +HREF="#AEN3495" >Assumptions</A ></DT ><DT ->26.3. <A -HREF="#AEN3369" +>24.3. <A +HREF="#AEN3505" >Tests</A ></DT ><DT ->26.4. <A -HREF="#AEN3479" +>24.4. <A +HREF="#AEN3615" >Still having troubles?</A ></DT ></DL @@ -1061,7 +969,7 @@ HREF="#AEN3479" ><DIV CLASS="PART" ><A -NAME="AEN18" +NAME="INTRODUCTION" ></A ><DIV CLASS="TITLEPAGE" @@ -1071,7 +979,7 @@ CLASS="TITLE" ><DIV CLASS="PARTINTRO" ><A -NAME="AEN20" +NAME="AEN21" ></A ><H1 >Introduction</H1 @@ -1096,27 +1004,27 @@ HREF="#INSTALL" ><DL ><DT >1.1. <A -HREF="#AEN25" +HREF="#AEN26" >Read the man pages</A ></DT ><DT >1.2. <A -HREF="#AEN35" +HREF="#AEN36" >Building the Binaries</A ></DT ><DT >1.3. <A -HREF="#AEN63" +HREF="#AEN64" >The all important step</A ></DT ><DT >1.4. <A -HREF="#AEN67" +HREF="#AEN68" >Create the smb configuration file.</A ></DT ><DT >1.5. <A -HREF="#AEN81" +HREF="#AEN82" >Test your config file with <B CLASS="COMMAND" @@ -1125,75 +1033,75 @@ CLASS="COMMAND" ></DT ><DT >1.6. <A -HREF="#AEN89" +HREF="#AEN90" >Starting the smbd and nmbd</A ></DT ><DD ><DL ><DT >1.6.1. <A -HREF="#AEN99" +HREF="#AEN100" >Starting from inetd.conf</A ></DT ><DT >1.6.2. <A -HREF="#AEN128" +HREF="#AEN129" >Alternative: starting it as a daemon</A ></DT ></DL ></DD ><DT >1.7. <A -HREF="#AEN144" +HREF="#AEN145" >Try listing the shares available on your server</A ></DT ><DT >1.8. <A -HREF="#AEN153" +HREF="#AEN154" >Try connecting with the unix client</A ></DT ><DT >1.9. <A -HREF="#AEN169" +HREF="#AEN170" >Try connecting from a DOS, WfWg, Win9x, WinNT, Win2k, OS/2, etc... client</A ></DT ><DT >1.10. <A -HREF="#AEN183" +HREF="#AEN184" >What If Things Don't Work?</A ></DT ><DD ><DL ><DT >1.10.1. <A -HREF="#AEN188" +HREF="#AEN189" >Diagnosing Problems</A ></DT ><DT >1.10.2. <A -HREF="#AEN192" +HREF="#AEN193" >Scope IDs</A ></DT ><DT >1.10.3. <A -HREF="#AEN195" +HREF="#AEN196" >Choosing the Protocol Level</A ></DT ><DT >1.10.4. <A -HREF="#AEN204" +HREF="#AEN205" >Printing from UNIX to a Client PC</A ></DT ><DT >1.10.5. <A -HREF="#AEN209" +HREF="#AEN210" >Locking</A ></DT ><DT >1.10.6. <A -HREF="#AEN218" +HREF="#AEN219" >Mapping Usernames</A ></DT ></DL @@ -1202,169 +1110,199 @@ HREF="#AEN218" ></DD ><DT >2. <A -HREF="#IMPROVED-BROWSING" ->Improved browsing in samba</A +HREF="#BROWSING-QUICK" +>Quick Cross Subnet Browsing / Cross Workgroup Browsing guide</A ></DT ><DD ><DL ><DT >2.1. <A -HREF="#AEN228" ->Overview of browsing</A +HREF="#AEN230" +>Discussion</A ></DT ><DT >2.2. <A -HREF="#AEN232" ->Browsing support in samba</A +HREF="#AEN238" +>Use of the "Remote Announce" parameter</A ></DT ><DT >2.3. <A -HREF="#AEN241" ->Problem resolution</A +HREF="#AEN252" +>Use of the "Remote Browse Sync" parameter</A ></DT ><DT >2.4. <A -HREF="#AEN248" ->Browsing across subnets</A -></DT -><DD -><DL -><DT ->2.4.1. <A -HREF="#AEN253" ->How does cross subnet browsing work ?</A +HREF="#AEN257" +>Use of WINS</A ></DT -></DL -></DD ><DT >2.5. <A -HREF="#AEN288" ->Setting up a WINS server</A +HREF="#AEN268" +>Do NOT use more than one (1) protocol on MS Windows machines</A ></DT ><DT >2.6. <A -HREF="#AEN307" ->Setting up Browsing in a WORKGROUP</A +HREF="#AEN274" +>Name Resolution Order</A ></DT +></DL +></DD ><DT ->2.7. <A -HREF="#AEN325" ->Setting up Browsing in a DOMAIN</A +>3. <A +HREF="#PASSDB" +>User information database</A ></DT +><DD +><DL ><DT ->2.8. <A -HREF="#AEN335" ->Forcing samba to be the master</A +>3.1. <A +HREF="#AEN324" +>Introduction</A ></DT ><DT ->2.9. <A -HREF="#AEN344" ->Making samba the domain master</A +>3.2. <A +HREF="#AEN331" +>Important Notes About Security</A ></DT +><DD +><DL ><DT ->2.10. <A -HREF="#AEN362" ->Note about broadcast addresses</A +>3.2.1. <A +HREF="#AEN346" +>Advantages of SMB Encryption</A ></DT ><DT ->2.11. <A -HREF="#AEN365" ->Multiple interfaces</A +>3.2.2. <A +HREF="#AEN351" +>Advantages of non-encrypted passwords</A ></DT ></DL ></DD ><DT ->3. <A -HREF="#OPLOCKS" ->Oplocks</A +>3.3. <A +HREF="#AEN357" +>The smbpasswd Command</A ></DT -><DD -><DL ><DT ->3.1. <A -HREF="#AEN377" ->What are oplocks?</A +>3.4. <A +HREF="#AEN388" +>Plain text</A ></DT -></DL -></DD ><DT ->4. <A -HREF="#BROWSING-QUICK" ->Quick Cross Subnet Browsing / Cross Workgroup Browsing guide</A +>3.5. <A +HREF="#AEN393" +>TDB</A +></DT +><DT +>3.6. <A +HREF="#AEN396" +>LDAP</A ></DT ><DD ><DL ><DT ->4.1. <A -HREF="#AEN392" ->Discussion</A +>3.6.1. <A +HREF="#AEN398" +>Introduction</A ></DT ><DT ->4.2. <A -HREF="#AEN400" ->Use of the "Remote Announce" parameter</A +>3.6.2. <A +HREF="#AEN418" +>Introduction</A ></DT ><DT ->4.3. <A -HREF="#AEN414" ->Use of the "Remote Browse Sync" parameter</A +>3.6.3. <A +HREF="#AEN447" +>Supported LDAP Servers</A ></DT ><DT ->4.4. <A -HREF="#AEN419" ->Use of WINS</A +>3.6.4. <A +HREF="#AEN452" +>Schema and Relationship to the RFC 2307 posixAccount</A ></DT ><DT ->4.5. <A -HREF="#AEN430" ->Do NOT use more than one (1) protocol on MS Windows machines</A +>3.6.5. <A +HREF="#AEN464" +>Configuring Samba with LDAP</A ></DT ><DT ->4.6. <A -HREF="#AEN436" ->Name Resolution Order</A +>3.6.6. <A +HREF="#AEN511" +>Accounts and Groups management</A +></DT +><DT +>3.6.7. <A +HREF="#AEN516" +>Security and sambaAccount</A +></DT +><DT +>3.6.8. <A +HREF="#AEN536" +>LDAP specials attributes for sambaAccounts</A +></DT +><DT +>3.6.9. <A +HREF="#AEN606" +>Example LDIF Entries for a sambaAccount</A ></DT ></DL ></DD ><DT ->5. <A -HREF="#PWENCRYPT" ->LanMan and NT Password Encryption in Samba</A +>3.7. <A +HREF="#AEN614" +>MySQL</A ></DT ><DD ><DL ><DT ->5.1. <A -HREF="#AEN472" ->Introduction</A +>3.7.1. <A +HREF="#AEN616" +>Building</A ></DT ><DT ->5.2. <A -HREF="#AEN477" ->Important Notes About Security</A +>3.7.2. <A +HREF="#AEN622" +>Creating the database</A ></DT -><DD -><DL ><DT ->5.2.1. <A -HREF="#AEN496" ->Advantages of SMB Encryption</A +>3.7.3. <A +HREF="#AEN632" +>Configuring</A ></DT ><DT ->5.2.2. <A -HREF="#AEN503" ->Advantages of non-encrypted passwords</A +>3.7.4. <A +HREF="#AEN649" +>Using plaintext passwords or encrypted password</A +></DT +><DT +>3.7.5. <A +HREF="#AEN654" +>Getting non-column data from the table</A ></DT ></DL ></DD ><DT ->5.3. <A -HREF="#AEN512" ->The smbpasswd Command</A +>3.8. <A +HREF="#AEN662" +>Passdb XML plugin</A +></DT +><DD +><DL +><DT +>3.8.1. <A +HREF="#AEN664" +>Building</A +></DT +><DT +>3.8.2. <A +HREF="#AEN670" +>Usage</A ></DT ></DL ></DD ></DL +></DD +></DL ></DIV ></DIV ><DIV @@ -1379,7 +1317,7 @@ CLASS="SECT1" ><H2 CLASS="SECT1" ><A -NAME="AEN25" +NAME="AEN26" ></A >1.1. Read the man pages</H2 ><P @@ -1421,7 +1359,7 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN35" +NAME="AEN36" ></A >1.2. Building the Binaries</H2 ><P @@ -1520,7 +1458,7 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN63" +NAME="AEN64" ></A >1.3. The all important step</H2 ><P @@ -1537,7 +1475,7 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN67" +NAME="AEN68" ></A >1.4. Create the smb configuration file.</H2 ><P @@ -1593,7 +1531,7 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN81" +NAME="AEN82" ></A >1.5. Test your config file with <B @@ -1623,7 +1561,7 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN89" +NAME="AEN90" ></A >1.6. Starting the smbd and nmbd</H2 ><P @@ -1663,7 +1601,7 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN99" +NAME="AEN100" ></A >1.6.1. Starting from inetd.conf</H3 ><P @@ -1767,7 +1705,7 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN128" +NAME="AEN129" ></A >1.6.2. Alternative: starting it as a daemon</H3 ><P @@ -1824,7 +1762,7 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN144" +NAME="AEN145" ></A >1.7. Try listing the shares available on your server</H2 @@ -1865,7 +1803,7 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN153" +NAME="AEN154" ></A >1.8. Try connecting with the unix client</H2 ><P @@ -1928,7 +1866,7 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN169" +NAME="AEN170" ></A >1.9. Try connecting from a DOS, WfWg, Win9x, WinNT, Win2k, OS/2, etc... client</H2 @@ -1977,7 +1915,7 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN183" +NAME="AEN184" ></A >1.10. What If Things Don't Work?</H2 ><P @@ -2000,7 +1938,7 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN188" +NAME="AEN189" ></A >1.10.1. Diagnosing Problems</H3 ><P @@ -2017,7 +1955,7 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN192" +NAME="AEN193" ></A >1.10.2. Scope IDs</H3 ><P @@ -2033,7 +1971,7 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN195" +NAME="AEN196" ></A >1.10.3. Choosing the Protocol Level</H3 ><P @@ -2074,7 +2012,7 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN204" +NAME="AEN205" ></A >1.10.4. Printing from UNIX to a Client PC</H3 ><P @@ -2095,7 +2033,7 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN209" +NAME="AEN210" ></A >1.10.5. Locking</H3 ><P @@ -2155,7 +2093,7 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN218" +NAME="AEN219" ></A >1.10.6. Mapping Usernames</H3 ><P @@ -2169,802 +2107,9 @@ NAME="AEN218" CLASS="CHAPTER" ><HR><H1 ><A -NAME="IMPROVED-BROWSING" -></A ->Chapter 2. Improved browsing in samba</H1 -><DIV -CLASS="SECT1" -><H2 -CLASS="SECT1" -><A -NAME="AEN228" -></A ->2.1. Overview of browsing</H2 -><P ->SMB networking provides a mechanism by which clients can access a list -of machines in a network, a so-called "browse list". This list -contains machines that are ready to offer file and/or print services -to other machines within the network. Thus it does not include -machines which aren't currently able to do server tasks. The browse -list is heavily used by all SMB clients. Configuration of SMB -browsing has been problematic for some Samba users, hence this -document.</P -><P ->Browsing will NOT work if name resolution from NetBIOS names to IP -addresses does not function correctly. Use of a WINS server is highly -recommended to aid the resolution of NetBIOS (SMB) names to IP addresses. -WINS allows remote segment clients to obtain NetBIOS name_type information -that can NOT be provided by any other means of name resolution.</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN232" -></A ->2.2. Browsing support in samba</H2 -><P ->Samba now fully supports browsing. The browsing is supported by nmbd -and is also controlled by options in the smb.conf file (see smb.conf(5)).</P -><P ->Samba can act as a local browse master for a workgroup and the ability -for samba to support domain logons and scripts is now available. See -DOMAIN.txt for more information on domain logons.</P -><P ->Samba can also act as a domain master browser for a workgroup. This -means that it will collate lists from local browse masters into a -wide area network server list. In order for browse clients to -resolve the names they may find in this list, it is recommended that -both samba and your clients use a WINS server.</P -><P ->Note that you should NOT set Samba to be the domain master for a -workgroup that has the same name as an NT Domain: on each wide area -network, you must only ever have one domain master browser per workgroup, -regardless of whether it is NT, Samba or any other type of domain master -that is providing this service.</P -><P ->[Note that nmbd can be configured as a WINS server, but it is not -necessary to specifically use samba as your WINS server. NTAS can -be configured as your WINS server. In a mixed NT server and -samba environment on a Wide Area Network, it is recommended that -you use the NT server's WINS server capabilities. In a samba-only -environment, it is recommended that you use one and only one nmbd -as your WINS server].</P -><P ->To get browsing to work you need to run nmbd as usual, but will need -to use the "workgroup" option in smb.conf to control what workgroup -Samba becomes a part of.</P -><P ->Samba also has a useful option for a Samba server to offer itself for -browsing on another subnet. It is recommended that this option is only -used for 'unusual' purposes: announcements over the internet, for -example. See "remote announce" in the smb.conf man page. </P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN241" -></A ->2.3. Problem resolution</H2 -><P ->If something doesn't work then hopefully the log.nmb file will help -you track down the problem. Try a debug level of 2 or 3 for finding -problems. Also note that the current browse list usually gets stored -in text form in a file called browse.dat.</P -><P ->Note that if it doesn't work for you, then you should still be able to -type the server name as \\SERVER in filemanager then hit enter and -filemanager should display the list of available shares.</P -><P ->Some people find browsing fails because they don't have the global -"guest account" set to a valid account. Remember that the IPC$ -connection that lists the shares is done as guest, and thus you must -have a valid guest account.</P -><P ->Also, a lot of people are getting bitten by the problem of too many -parameters on the command line of nmbd in inetd.conf. This trick is to -not use spaces between the option and the parameter (eg: -d2 instead -of -d 2), and to not use the -B and -N options. New versions of nmbd -are now far more likely to correctly find your broadcast and network -address, so in most cases these aren't needed.</P -><P ->The other big problem people have is that their broadcast address, -netmask or IP address is wrong (specified with the "interfaces" option -in smb.conf)</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN248" -></A ->2.4. Browsing across subnets</H2 -><P ->With the release of Samba 1.9.17(alpha1 and above) Samba has been -updated to enable it to support the replication of browse lists -across subnet boundaries. New code and options have been added to -achieve this. This section describes how to set this feature up -in different settings.</P -><P ->To see browse lists that span TCP/IP subnets (ie. networks separated -by routers that don't pass broadcast traffic) you must set up at least -one WINS server. The WINS server acts as a DNS for NetBIOS names, allowing -NetBIOS name to IP address translation to be done by doing a direct -query of the WINS server. This is done via a directed UDP packet on -port 137 to the WINS server machine. The reason for a WINS server is -that by default, all NetBIOS name to IP address translation is done -by broadcasts from the querying machine. This means that machines -on one subnet will not be able to resolve the names of machines on -another subnet without using a WINS server.</P -><P ->Remember, for browsing across subnets to work correctly, all machines, -be they Windows 95, Windows NT, or Samba servers must have the IP address -of a WINS server given to them by a DHCP server, or by manual configuration -(for Win95 and WinNT, this is in the TCP/IP Properties, under Network -settings) for Samba this is in the smb.conf file.</P -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN253" -></A ->2.4.1. How does cross subnet browsing work ?</H3 -><P ->Cross subnet browsing is a complicated dance, containing multiple -moving parts. It has taken Microsoft several years to get the code -that achieves this correct, and Samba lags behind in some areas. -However, with the 1.9.17 release, Samba is capable of cross subnet -browsing when configured correctly.</P -><P ->Consider a network set up as follows :</P -><P -><PRE -CLASS="PROGRAMLISTING" -> (DMB) - N1_A N1_B N1_C N1_D N1_E - | | | | | - ------------------------------------------------------- - | subnet 1 | - +---+ +---+ - |R1 | Router 1 Router 2 |R2 | - +---+ +---+ - | | - | subnet 2 subnet 3 | - -------------------------- ------------------------------------ - | | | | | | | | - N2_A N2_B N2_C N2_D N3_A N3_B N3_C N3_D - (WINS)</PRE -></P -><P ->Consisting of 3 subnets (1, 2, 3) connected by two routers -(R1, R2) - these do not pass broadcasts. Subnet 1 has 5 machines -on it, subnet 2 has 4 machines, subnet 3 has 4 machines. Assume -for the moment that all these machines are configured to be in the -same workgroup (for simplicities sake). Machine N1_C on subnet 1 -is configured as Domain Master Browser (ie. it will collate the -browse lists for the workgroup). Machine N2_D is configured as -WINS server and all the other machines are configured to register -their NetBIOS names with it.</P -><P ->As all these machines are booted up, elections for master browsers -will take place on each of the three subnets. Assume that machine -N1_C wins on subnet 1, N2_B wins on subnet 2, and N3_D wins on -subnet 3 - these machines are known as local master browsers for -their particular subnet. N1_C has an advantage in winning as the -local master browser on subnet 1 as it is set up as Domain Master -Browser.</P -><P ->On each of the three networks, machines that are configured to -offer sharing services will broadcast that they are offering -these services. The local master browser on each subnet will -receive these broadcasts and keep a record of the fact that -the machine is offering a service. This list of records is -the basis of the browse list. For this case, assume that -all the machines are configured to offer services so all machines -will be on the browse list.</P -><P ->For each network, the local master browser on that network is -considered 'authoritative' for all the names it receives via -local broadcast. This is because a machine seen by the local -master browser via a local broadcast must be on the same -network as the local master browser and thus is a 'trusted' -and 'verifiable' resource. Machines on other networks that -the local master browsers learn about when collating their -browse lists have not been directly seen - these records are -called 'non-authoritative'.</P -><P ->At this point the browse lists look as follows (these are -the machines you would see in your network neighborhood if -you looked in it on a particular network right now).</P -><P -><PRE -CLASS="PROGRAMLISTING" ->Subnet Browse Master List ------- ------------- ---- -Subnet1 N1_C N1_A, N1_B, N1_C, N1_D, N1_E - -Subnet2 N2_B N2_A, N2_B, N2_C, N2_D - -Subnet3 N3_D N3_A, N3_B, N3_C, N3_D</PRE -></P -><P ->Note that at this point all the subnets are separate, no -machine is seen across any of the subnets.</P -><P ->Now examine subnet 2. As soon as N2_B has become the local -master browser it looks for a Domain master browser to synchronize -its browse list with. It does this by querying the WINS server -(N2_D) for the IP address associated with the NetBIOS name -WORKGROUP>1B<. This name was registerd by the Domain master -browser (N1_C) with the WINS server as soon as it was booted.</P -><P ->Once N2_B knows the address of the Domain master browser it -tells it that is the local master browser for subnet 2 by -sending a MasterAnnouncement packet as a UDP port 138 packet. -It then synchronizes with it by doing a NetServerEnum2 call. This -tells the Domain Master Browser to send it all the server -names it knows about. Once the domain master browser receives -the MasterAnnouncement packet it schedules a synchronization -request to the sender of that packet. After both synchronizations -are done the browse lists look like :</P -><P -><PRE -CLASS="PROGRAMLISTING" ->Subnet Browse Master List ------- ------------- ---- -Subnet1 N1_C N1_A, N1_B, N1_C, N1_D, N1_E, - N2_A(*), N2_B(*), N2_C(*), N2_D(*) - -Subnet2 N2_B N2_A, N2_B, N2_C, N2_D - N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*) - -Subnet3 N3_D N3_A, N3_B, N3_C, N3_D - -Servers with a (*) after them are non-authoritative names.</PRE -></P -><P ->At this point users looking in their network neighborhood on -subnets 1 or 2 will see all the servers on both, users on -subnet 3 will still only see the servers on their own subnet.</P -><P ->The same sequence of events that occured for N2_B now occurs -for the local master browser on subnet 3 (N3_D). When it -synchronizes browse lists with the domain master browser (N1_A) -it gets both the server entries on subnet 1, and those on -subnet 2. After N3_D has synchronized with N1_C and vica-versa -the browse lists look like.</P -><P -><PRE -CLASS="PROGRAMLISTING" ->Subnet Browse Master List ------- ------------- ---- -Subnet1 N1_C N1_A, N1_B, N1_C, N1_D, N1_E, - N2_A(*), N2_B(*), N2_C(*), N2_D(*), - N3_A(*), N3_B(*), N3_C(*), N3_D(*) - -Subnet2 N2_B N2_A, N2_B, N2_C, N2_D - N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*) - -Subnet3 N3_D N3_A, N3_B, N3_C, N3_D - N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*), - N2_A(*), N2_B(*), N2_C(*), N2_D(*) - -Servers with a (*) after them are non-authoritative names.</PRE -></P -><P ->At this point users looking in their network neighborhood on -subnets 1 or 3 will see all the servers on all sunbets, users on -subnet 2 will still only see the servers on subnets 1 and 2, but not 3.</P -><P ->Finally, the local master browser for subnet 2 (N2_B) will sync again -with the domain master browser (N1_C) and will recieve the missing -server entries. Finally - and as a steady state (if no machines -are removed or shut off) the browse lists will look like :</P -><P -><PRE -CLASS="PROGRAMLISTING" ->Subnet Browse Master List ------- ------------- ---- -Subnet1 N1_C N1_A, N1_B, N1_C, N1_D, N1_E, - N2_A(*), N2_B(*), N2_C(*), N2_D(*), - N3_A(*), N3_B(*), N3_C(*), N3_D(*) - -Subnet2 N2_B N2_A, N2_B, N2_C, N2_D - N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*) - N3_A(*), N3_B(*), N3_C(*), N3_D(*) - -Subnet3 N3_D N3_A, N3_B, N3_C, N3_D - N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*), - N2_A(*), N2_B(*), N2_C(*), N2_D(*) - -Servers with a (*) after them are non-authoritative names.</PRE -></P -><P ->Synchronizations between the domain master browser and local -master browsers will continue to occur, but this should be a -steady state situation.</P -><P ->If either router R1 or R2 fails the following will occur:</P -><P -></P -><OL -TYPE="1" -><LI -><P -> Names of computers on each side of the inaccessible network fragments - will be maintained for as long as 36 minutes, in the network neighbourhood - lists. - </P -></LI -><LI -><P -> Attempts to connect to these inaccessible computers will fail, but the - names will not be removed from the network neighbourhood lists. - </P -></LI -><LI -><P -> If one of the fragments is cut off from the WINS server, it will only - be able to access servers on its local subnet, by using subnet-isolated - broadcast NetBIOS name resolution. The effects are similar to that of - losing access to a DNS server. - </P -></LI -></OL -></DIV -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN288" -></A ->2.5. Setting up a WINS server</H2 -><P ->Either a Samba machine or a Windows NT Server machine may be set up -as a WINS server. To set a Samba machine to be a WINS server you must -add the following option to the smb.conf file on the selected machine : -in the [globals] section add the line </P -><P -><B -CLASS="COMMAND" -> wins support = yes</B -></P -><P ->Versions of Samba previous to 1.9.17 had this parameter default to -yes. If you have any older versions of Samba on your network it is -strongly suggested you upgrade to 1.9.17 or above, or at the very -least set the parameter to 'no' on all these machines.</P -><P ->Machines with "<B -CLASS="COMMAND" ->wins support = yes</B ->" will keep a list of -all NetBIOS names registered with them, acting as a DNS for NetBIOS names.</P -><P ->You should set up only ONE wins server. Do NOT set the -"<B -CLASS="COMMAND" ->wins support = yes</B ->" option on more than one Samba -server.</P -><P ->To set up a Windows NT Server as a WINS server you need to set up -the WINS service - see your NT documentation for details. Note that -Windows NT WINS Servers can replicate to each other, allowing more -than one to be set up in a complex subnet environment. As Microsoft -refuse to document these replication protocols Samba cannot currently -participate in these replications. It is possible in the future that -a Samba->Samba WINS replication protocol may be defined, in which -case more than one Samba machine could be set up as a WINS server -but currently only one Samba server should have the "wins support = yes" -parameter set.</P -><P ->After the WINS server has been configured you must ensure that all -machines participating on the network are configured with the address -of this WINS server. If your WINS server is a Samba machine, fill in -the Samba machine IP address in the "Primary WINS Server" field of -the "Control Panel->Network->Protocols->TCP->WINS Server" dialogs -in Windows 95 or Windows NT. To tell a Samba server the IP address -of the WINS server add the following line to the [global] section of -all smb.conf files :</P -><P -><B -CLASS="COMMAND" ->wins server = >name or IP address<</B -></P -><P ->where >name or IP address< is either the DNS name of the WINS server -machine or its IP address.</P -><P ->Note that this line MUST NOT BE SET in the smb.conf file of the Samba -server acting as the WINS server itself. If you set both the -"<B -CLASS="COMMAND" ->wins support = yes</B ->" option and the -"<B -CLASS="COMMAND" ->wins server = >name<</B ->" option then -nmbd will fail to start.</P -><P ->There are two possible scenarios for setting up cross subnet browsing. -The first details setting up cross subnet browsing on a network containing -Windows 95, Samba and Windows NT machines that are not configured as -part of a Windows NT Domain. The second details setting up cross subnet -browsing on networks that contain NT Domains.</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN307" -></A ->2.6. Setting up Browsing in a WORKGROUP</H2 -><P ->To set up cross subnet browsing on a network containing machines -in up to be in a WORKGROUP, not an NT Domain you need to set up one -Samba server to be the Domain Master Browser (note that this is *NOT* -the same as a Primary Domain Controller, although in an NT Domain the -same machine plays both roles). The role of a Domain master browser is -to collate the browse lists from local master browsers on all the -subnets that have a machine participating in the workgroup. Without -one machine configured as a domain master browser each subnet would -be an isolated workgroup, unable to see any machines on any other -subnet. It is the presense of a domain master browser that makes -cross subnet browsing possible for a workgroup.</P -><P ->In an WORKGROUP environment the domain master browser must be a -Samba server, and there must only be one domain master browser per -workgroup name. To set up a Samba server as a domain master browser, -set the following option in the [global] section of the smb.conf file :</P -><P -><B -CLASS="COMMAND" ->domain master = yes</B -></P -><P ->The domain master browser should also preferrably be the local master -browser for its own subnet. In order to achieve this set the following -options in the [global] section of the smb.conf file :</P -><P -><PRE -CLASS="PROGRAMLISTING" -> domain master = yes - local master = yes - preferred master = yes - os level = 65</PRE -></P -><P ->The domain master browser may be the same machine as the WINS -server, if you require.</P -><P ->Next, you should ensure that each of the subnets contains a -machine that can act as a local master browser for the -workgroup. Any NT machine should be able to do this, as will -Windows 95 machines (although these tend to get rebooted more -often, so it's not such a good idea to use these). To make a -Samba server a local master browser set the following -options in the [global] section of the smb.conf file :</P -><P -><PRE -CLASS="PROGRAMLISTING" -> domain master = no - local master = yes - preferred master = yes - os level = 65</PRE -></P -><P ->Do not do this for more than one Samba server on each subnet, -or they will war with each other over which is to be the local -master browser.</P -><P ->The "local master" parameter allows Samba to act as a local master -browser. The "preferred master" causes nmbd to force a browser -election on startup and the "os level" parameter sets Samba high -enough so that it should win any browser elections.</P -><P ->If you have an NT machine on the subnet that you wish to -be the local master browser then you can disable Samba from -becoming a local master browser by setting the following -options in the [global] section of the smb.conf file :</P -><P -><PRE -CLASS="PROGRAMLISTING" -> domain master = no - local master = no - preferred master = no - os level = 0</PRE -></P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN325" -></A ->2.7. Setting up Browsing in a DOMAIN</H2 -><P ->If you are adding Samba servers to a Windows NT Domain then -you must not set up a Samba server as a domain master browser. -By default, a Windows NT Primary Domain Controller for a Domain -name is also the Domain master browser for that name, and many -things will break if a Samba server registers the Domain master -browser NetBIOS name (DOMAIN>1B<) with WINS instead of the PDC.</P -><P ->For subnets other than the one containing the Windows NT PDC -you may set up Samba servers as local master browsers as -described. To make a Samba server a local master browser set -the following options in the [global] section of the smb.conf -file :</P -><P -><PRE -CLASS="PROGRAMLISTING" -> domain master = no - local master = yes - preferred master = yes - os level = 65</PRE -></P -><P ->If you wish to have a Samba server fight the election with machines -on the same subnet you may set the "os level" parameter to lower -levels. By doing this you can tune the order of machines that -will become local master browsers if they are running. For -more details on this see the section "FORCING SAMBA TO BE THE MASTER" -below.</P -><P ->If you have Windows NT machines that are members of the domain -on all subnets, and you are sure they will always be running then -you can disable Samba from taking part in browser elections and -ever becoming a local master browser by setting following options -in the [global] section of the smb.conf file :</P -><P -><B -CLASS="COMMAND" -> domain master = no - local master = no - preferred master = no - os level = 0</B -></P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN335" -></A ->2.8. Forcing samba to be the master</H2 -><P ->Who becomes the "master browser" is determined by an election process -using broadcasts. Each election packet contains a number of parameters -which determine what precedence (bias) a host should have in the -election. By default Samba uses a very low precedence and thus loses -elections to just about anyone else.</P -><P ->If you want Samba to win elections then just set the "os level" global -option in smb.conf to a higher number. It defaults to 0. Using 34 -would make it win all elections over every other system (except other -samba systems!)</P -><P ->A "os level" of 2 would make it beat WfWg and Win95, but not NTAS. A -NTAS domain controller uses level 32.</P -><P ->The maximum os level is 255</P -><P ->If you want samba to force an election on startup, then set the -"preferred master" global option in smb.conf to "yes". Samba will -then have a slight advantage over other potential master browsers -that are not preferred master browsers. Use this parameter with -care, as if you have two hosts (whether they are windows 95 or NT or -samba) on the same local subnet both set with "preferred master" to -"yes", then periodically and continually they will force an election -in order to become the local master browser.</P -><P ->If you want samba to be a "domain master browser", then it is -recommended that you also set "preferred master" to "yes", because -samba will not become a domain master browser for the whole of your -LAN or WAN if it is not also a local master browser on its own -broadcast isolated subnet.</P -><P ->It is possible to configure two samba servers to attempt to become -the domain master browser for a domain. The first server that comes -up will be the domain master browser. All other samba servers will -attempt to become the domain master browser every 5 minutes. They -will find that another samba server is already the domain master -browser and will fail. This provides automatic redundancy, should -the current domain master browser fail.</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN344" -></A ->2.9. Making samba the domain master</H2 -><P ->The domain master is responsible for collating the browse lists of -multiple subnets so that browsing can occur between subnets. You can -make samba act as the domain master by setting "domain master = yes" -in smb.conf. By default it will not be a domain master.</P -><P ->Note that you should NOT set Samba to be the domain master for a -workgroup that has the same name as an NT Domain.</P -><P ->When samba is the domain master and the master browser it will listen -for master announcements (made roughly every twelve minutes) from local -master browsers on other subnets and then contact them to synchronise -browse lists.</P -><P ->If you want samba to be the domain master then I suggest you also set -the "os level" high enough to make sure it wins elections, and set -"preferred master" to "yes", to get samba to force an election on -startup.</P -><P ->Note that all your servers (including samba) and clients should be -using a WINS server to resolve NetBIOS names. If your clients are only -using broadcasting to resolve NetBIOS names, then two things will occur:</P -><P -></P -><OL -TYPE="1" -><LI -><P -> your local master browsers will be unable to find a domain master - browser, as it will only be looking on the local subnet. - </P -></LI -><LI -><P -> if a client happens to get hold of a domain-wide browse list, and - a user attempts to access a host in that list, it will be unable to - resolve the NetBIOS name of that host. - </P -></LI -></OL -><P ->If, however, both samba and your clients are using a WINS server, then:</P -><P -></P -><OL -TYPE="1" -><LI -><P -> your local master browsers will contact the WINS server and, as long as - samba has registered that it is a domain master browser with the WINS - server, your local master browser will receive samba's ip address - as its domain master browser. - </P -></LI -><LI -><P -> when a client receives a domain-wide browse list, and a user attempts - to access a host in that list, it will contact the WINS server to - resolve the NetBIOS name of that host. as long as that host has - registered its NetBIOS name with the same WINS server, the user will - be able to see that host. - </P -></LI -></OL -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN362" -></A ->2.10. Note about broadcast addresses</H2 -><P ->If your network uses a "0" based broadcast address (for example if it -ends in a 0) then you will strike problems. Windows for Workgroups -does not seem to support a 0's broadcast and you will probably find -that browsing and name lookups won't work.</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN365" -></A ->2.11. Multiple interfaces</H2 -><P ->Samba now supports machines with multiple network interfaces. If you -have multiple interfaces then you will need to use the "interfaces" -option in smb.conf to configure them. See smb.conf(5) for details.</P -></DIV -></DIV -><DIV -CLASS="CHAPTER" -><HR><H1 -><A -NAME="OPLOCKS" -></A ->Chapter 3. Oplocks</H1 -><DIV -CLASS="SECT1" -><H2 -CLASS="SECT1" -><A -NAME="AEN377" -></A ->3.1. What are oplocks?</H2 -><P ->When a client opens a file it can request an "oplock" or file -lease. This is (to simplify a bit) a guarentee that no one else -has the file open simultaneously. It allows the client to not -send any updates on the file to the server, thus reducing a -network file access to local access (once the file is in -client cache). An "oplock break" is when the server sends -a request to the client to flush all its changes back to -the server, so the file is in a consistent state for other -opens to succeed. If a client fails to respond to this -asynchronous request then the file can be corrupted. Hence -the "turn off oplocks" answer if people are having multi-user -file access problems.</P -><P ->Unless the kernel is "oplock aware" (SGI IRIX and Linux are -the only two UNIXes that are at the moment) then if a local -UNIX process accesses the file simultaneously then Samba -has no way of telling this is occuring, so the guarentee -to the client is broken. This can corrupt the file. Short -answer - it you have UNIX clients accessing the same file -as smbd locally or via NFS and you're not running Linux or -IRIX then turn off oplocks for that file or share.</P -><P ->"Share modes". These are modes of opening a file, that -guarentee an invarient - such as DENY_WRITE - which means -that if any other opens are requested with write access after -this current open has succeeded then they should be denied -with a "sharing violation" error message. Samba handles these -internally inside smbd. UNIX clients accessing the same file -ignore these invarients. Just proving that if you need simultaneous -file access from a Windows and UNIX client you *must* have an -application that is written to lock records correctly on both -sides. Few applications are written like this, and even fewer -are cross platform (UNIX and Windows) so in practice this isn't -much of a problem.</P -><P ->"Locking". This really means "byte range locking" - such as -lock 10 bytes at file offset 24 for write access. This is the -area in which well written UNIX and Windows apps will cooperate. -Windows locks (at least from NT or above) are 64-bit unsigned -offsets. UNIX locks are either 31 bit or 63 bit and are signed -(the top bit is used for the sign). Samba handles these by -first ensuring that all the Windows locks don't conflict (ie. -if other Windows clients have competing locks then just reject -immediately) - this allows us to support 64-bit Windows locks -on 32-bit filesystems. Secondly any locks that are valid are -then mapped onto UNIX fcntl byte range locks. These are the -locks that will be seen by UNIX processes. If there is a conflict -here the lock is rejected.</P -><P ->Note that if a client has an oplock then it "knows" that no -other client can have the file open so usually doesn't bother -to send to lock request to the server - this means once again -if you need to share files between UNIX and Windows processes -either use IRIX or Linux, or turn off oplocks for these -files/shares.</P -></DIV -></DIV -><DIV -CLASS="CHAPTER" -><HR><H1 -><A NAME="BROWSING-QUICK" ></A ->Chapter 4. Quick Cross Subnet Browsing / Cross Workgroup Browsing guide</H1 +>Chapter 2. Quick Cross Subnet Browsing / Cross Workgroup Browsing guide</H1 ><P >This document should be read in conjunction with Browsing and may be taken as the fast track guide to implementing browsing across subnets @@ -2976,9 +2121,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN392" +NAME="AEN230" ></A ->4.1. Discussion</H2 +>2.1. Discussion</H2 ><P >Firstly, all MS Windows networking is based on SMB (Server Message Block) based messaging. SMB messaging is implemented using NetBIOS. Samba @@ -3022,9 +2167,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN400" +NAME="AEN238" ></A ->4.2. Use of the "Remote Announce" parameter</H2 +>2.2. Use of the "Remote Announce" parameter</H2 ><P >The "remote announce" parameter of smb.conf can be used to forcibly ensure that all the NetBIOS names on a network get announced to a remote network. @@ -3073,16 +2218,16 @@ name resolution problems and should be avoided.</P ></DD ></DL ></DIV -> </P +></P ></DIV ><DIV CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN414" +NAME="AEN252" ></A ->4.3. Use of the "Remote Browse Sync" parameter</H2 +>2.3. Use of the "Remote Browse Sync" parameter</H2 ><P >The "remote browse sync" parameter of smb.conf is used to announce to another LMB that it must synchronise it's NetBIOS name list with our @@ -3090,9 +2235,10 @@ Samba LMB. It works ONLY if the Samba server that has this option is simultaneously the LMB on it's network segment.</P ><P >The syntax of the "remote browse sync" parameter is: + <PRE CLASS="PROGRAMLISTING" -> remote browse sync = a.b.c.d</PRE +>remote browse sync = a.b.c.d</PRE > where a.b.c.d is either the IP address of the remote LMB or else is the network broadcast address of the remote segment.</P @@ -3102,9 +2248,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN419" +NAME="AEN257" ></A ->4.4. Use of WINS</H2 +>2.4. Use of WINS</H2 ><P >Use of WINS (either Samba WINS _or_ MS Windows NT Server WINS) is highly recommended. Every NetBIOS machine registers it's name together with a @@ -3164,9 +2310,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN430" +NAME="AEN268" ></A ->4.5. Do NOT use more than one (1) protocol on MS Windows machines</H2 +>2.5. Do NOT use more than one (1) protocol on MS Windows machines</H2 ><P >A very common cause of browsing problems results from installing more than one protocol on an MS Windows machine.</P @@ -3194,14 +2340,14 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN436" +NAME="AEN274" ></A ->4.6. Name Resolution Order</H2 +>2.6. Name Resolution Order</H2 ><P >Resolution of NetBIOS names to IP addresses can take place using a number of methods. The only ones that can provide NetBIOS name_type information -are: -<P +are:</P +><P ></P ><TABLE BORDER="0" @@ -3222,10 +2368,9 @@ BORDER="0" ></TABLE ><P ></P -></P ><P ->Alternative means of name resolution includes: -<P +>Alternative means of name resolution includes:</P +><P ></P ><TABLE BORDER="0" @@ -3242,24 +2387,23 @@ BORDER="0" ></TABLE ><P ></P -></P ><P >Many sites want to restrict DNS lookups and want to avoid broadcast name resolution traffic. The "name resolve order" parameter is of great help here. The syntax of the "name resolve order" parameter is: <PRE CLASS="PROGRAMLISTING" -> name resolve order = wins lmhosts bcast host</PRE +>name resolve order = wins lmhosts bcast host</PRE > _or_ <PRE CLASS="PROGRAMLISTING" -> name resolve order = wins lmhosts (eliminates bcast and host)</PRE +>name resolve order = wins lmhosts (eliminates bcast and host)</PRE > The default is: <PRE CLASS="PROGRAMLISTING" -> name resolve order = host lmhost wins bcast</PRE +>name resolve order = host lmhost wins bcast</PRE >. where "host" refers the the native methods used by the Unix system to implement the gethostbyname() function call. This is normally @@ -3279,28 +2423,45 @@ CLASS="FILENAME" CLASS="CHAPTER" ><HR><H1 ><A -NAME="PWENCRYPT" +NAME="PASSDB" ></A ->Chapter 5. LanMan and NT Password Encryption in Samba</H1 +>Chapter 3. User information database</H1 ><DIV CLASS="SECT1" ><H2 CLASS="SECT1" ><A -NAME="AEN472" +NAME="AEN324" ></A ->5.1. Introduction</H2 +>3.1. Introduction</H2 +><P +>Old windows clients send plain text passwords over the wire. + Samba can check these passwords by crypting them and comparing them + to the hash stored in the unix user database. + </P ><P ->Newer windows clients send encrypted passwords over +> Newer windows clients send encrypted passwords (so-called + Lanman and NT hashes) over the wire, instead of plain text passwords. The newest clients will only send encrypted passwords and refuse to send plain text - passwords, unless their registry is tweaked.</P + passwords, unless their registry is tweaked. + </P ><P >These passwords can't be converted to unix style encrypted passwords. Because of that you can't use the standard unix user database, and you have to store the Lanman and NT hashes - somewhere else. For more information, see the documentation - about the <B + somewhere else. </P +><P +>Next to a differently encrypted passwords, + windows also stores certain data for each user + that is not stored in a unix user database, e.g. + workstations the user may logon from, the location where his/her + profile is stored, etc. + Samba retrieves and stores this information using a "passdb backend". + Commonly + available backends are LDAP, plain text file, MySQL and nisplus. + For more information, see the documentation about the + <B CLASS="COMMAND" >passdb backend = </B > parameter. @@ -3311,9 +2472,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN477" +NAME="AEN331" ></A ->5.2. Important Notes About Security</H2 +>3.2. Important Notes About Security</H2 ><P >The unix and SMB password encryption techniques seem similar on the surface. This similarity is, however, only skin deep. The unix @@ -3325,7 +2486,8 @@ NAME="AEN477" password from them, but they could potentially be used in a modified client to gain access to a server. This would require considerable technical knowledge on behalf of the attacker but is perfectly possible. - You should thus treat the smbpasswd file as though it contained the + You should thus treat the data stored in whatever + passdb backend you use (smbpasswd file, ldap, mysql) as though it contained the cleartext passwords of all your users. Its contents must be kept secret, and the file should be protected accordingly.</P ><P @@ -3347,7 +2509,7 @@ WIDTH="25" ALIGN="CENTER" VALIGN="TOP" ><IMG -SRC="/docbook-dsssl/warning.gif" +SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/warning.gif" HSPACE="5" ALT="Warning"></TD ><TD @@ -3372,26 +2534,31 @@ CLASS="EMPHASIS" this behavior includes</P ><P ></P -><UL -><LI -><P +><TABLE +BORDER="0" +><TBODY +><TR +><TD >MS DOS Network client 3.0 with - the basic network redirector installed</P -></LI -><LI -><P + the basic network redirector installed</TD +></TR +><TR +><TD >Windows 95 with the network redirector - update installed</P -></LI -><LI -><P ->Windows 98 [se]</P -></LI -><LI + update installed</TD +></TR +><TR +><TD +>Windows 98 [se]</TD +></TR +><TR +><TD +>Windows 2000</TD +></TR +></TBODY +></TABLE ><P ->Windows 2000</P -></LI -></UL +></P ><P ><SPAN CLASS="emphasis" @@ -3413,59 +2580,69 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN496" +NAME="AEN346" ></A ->5.2.1. Advantages of SMB Encryption</H3 +>3.2.1. Advantages of SMB Encryption</H3 ><P ></P -><UL -><LI -><P +><TABLE +BORDER="0" +><TBODY +><TR +><TD >plain text passwords are not passed across the network. Someone using a network sniffer cannot just - record passwords going to the SMB server.</P -></LI -><LI -><P + record passwords going to the SMB server.</TD +></TR +><TR +><TD >WinNT doesn't like talking to a server that isn't using SMB encrypted passwords. It will refuse to browse the server if the server is also in user level security mode. It will insist on prompting the user for the password on each connection, which is very annoying. The only things you can do to stop this is to use SMB encryption. - </P -></LI -></UL + </TD +></TR +></TBODY +></TABLE +><P +></P ></DIV ><DIV CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN503" +NAME="AEN351" ></A ->5.2.2. Advantages of non-encrypted passwords</H3 +>3.2.2. Advantages of non-encrypted passwords</H3 ><P ></P -><UL -><LI -><P +><TABLE +BORDER="0" +><TBODY +><TR +><TD >plain text passwords are not kept - on disk. </P -></LI -><LI -><P + on disk. </TD +></TR +><TR +><TD >uses same password file as other unix - services such as login and ftp</P -></LI -><LI -><P + services such as login and ftp</TD +></TR +><TR +><TD >you are probably already using other services (such as telnet and ftp) which send plain text passwords over the net, so sending them for SMB isn't - such a big deal.</P -></LI -></UL + such a big deal.</TD +></TR +></TBODY +></TABLE +><P +></P ></DIV ></DIV ><DIV @@ -3473,36 +2650,32 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN512" +NAME="AEN357" ></A ->5.3. The smbpasswd Command</H2 +>3.3. The smbpasswd Command</H2 ><P ->The smbpasswd command maintains the two 32 byte password fields - in the smbpasswd file. If you wish to make it similar to the unix +>The smbpasswd utility is a utility similar to the <B CLASS="COMMAND" >passwd</B > or <B CLASS="COMMAND" >yppasswd</B -> programs, - install it in <TT -CLASS="FILENAME" ->/usr/local/samba/bin/</TT -> (or your - main Samba binary directory).</P +> programs. + It maintains the two 32 byte password fields + in the passdb backend. </P ><P ><B CLASS="COMMAND" >smbpasswd</B -> now works in a client-server mode +> works in a client-server mode where it contacts the local smbd to change the user's password on its behalf. This has enormous benefits - as follows.</P ><P ><B CLASS="COMMAND" >smbpasswd</B -> now has the capability +> has the capability to change passwords on Windows NT servers (this only works when the request is sent to the NT Primary Domain Controller if you are changing an NT Domain user's password).</P @@ -3584,12 +2757,1184 @@ CLASS="COMMAND" > refer to the man page which will always be the definitive reference.</P ></DIV +><DIV +CLASS="SECT1" +><HR><H2 +CLASS="SECT1" +><A +NAME="AEN388" +></A +>3.4. Plain text</H2 +><P +>Older versions of samba retrieved user information from the unix user database +and eventually some other fields from the file <TT +CLASS="FILENAME" +>/etc/samba/smbpasswd</TT +> +or <TT +CLASS="FILENAME" +>/etc/smbpasswd</TT +>. When password encryption is disabled, no +data is stored at all.</P +></DIV +><DIV +CLASS="SECT1" +><HR><H2 +CLASS="SECT1" +><A +NAME="AEN393" +></A +>3.5. TDB</H2 +><P +>Samba can also store the user data in a "TDB" (Trivial Database). Using this backend +doesn't require any additional configuration. This backend is recommended for new installations who +don't require LDAP.</P +></DIV +><DIV +CLASS="SECT1" +><HR><H2 +CLASS="SECT1" +><A +NAME="AEN396" +></A +>3.6. LDAP</H2 +><DIV +CLASS="SECT2" +><H3 +CLASS="SECT2" +><A +NAME="AEN398" +></A +>3.6.1. Introduction</H3 +><P +>This document describes how to use an LDAP directory for storing Samba user +account information traditionally stored in the smbpasswd(5) file. It is +assumed that the reader already has a basic understanding of LDAP concepts +and has a working directory server already installed. For more information +on LDAP architectures and Directories, please refer to the following sites.</P +><P +></P +><UL +><LI +><P +>OpenLDAP - <A +HREF="http://www.openldap.org/" +TARGET="_top" +>http://www.openldap.org/</A +></P +></LI +><LI +><P +>iPlanet Directory Server - <A +HREF="http://iplanet.netscape.com/directory" +TARGET="_top" +>http://iplanet.netscape.com/directory</A +></P +></LI +></UL +><P +>Note that <A +HREF="http://www.ora.com/" +TARGET="_top" +>O'Reilly Publishing</A +> is working on +a guide to LDAP for System Administrators which has a planned release date of +early summer, 2002.</P +><P +>Two additional Samba resources which may prove to be helpful are</P +><P +></P +><UL +><LI +><P +>The <A +HREF="http://www.unav.es/cti/ldap-smb/ldap-smb-3-howto.html" +TARGET="_top" +>Samba-PDC-LDAP-HOWTO</A +> + maintained by Ignacio Coupeau.</P +></LI +><LI +><P +>The NT migration scripts from <A +HREF="http://samba.idealx.org/" +TARGET="_top" +>IDEALX</A +> that are + geared to manage users and group in such a Samba-LDAP Domain Controller configuration. + </P +></LI +></UL +></DIV +><DIV +CLASS="SECT2" +><HR><H3 +CLASS="SECT2" +><A +NAME="AEN418" +></A +>3.6.2. Introduction</H3 +><P +>Traditionally, when configuring <A +HREF="smb.conf.5.html#ENCRYPTPASSWORDS" +TARGET="_top" +>"encrypt +passwords = yes"</A +> in Samba's <TT +CLASS="FILENAME" +>smb.conf</TT +> file, user account +information such as username, LM/NT password hashes, password change times, and account +flags have been stored in the <TT +CLASS="FILENAME" +>smbpasswd(5)</TT +> file. There are several +disadvantages to this approach for sites with very large numbers of users (counted +in the thousands).</P +><P +></P +><UL +><LI +><P +>The first is that all lookups must be performed sequentially. Given that +there are approximately two lookups per domain logon (one for a normal +session connection such as when mapping a network drive or printer), this +is a performance bottleneck for lareg sites. What is needed is an indexed approach +such as is used in databases.</P +></LI +><LI +><P +>The second problem is that administrators who desired to replicate a +smbpasswd file to more than one Samba server were left to use external +tools such as <B +CLASS="COMMAND" +>rsync(1)</B +> and <B +CLASS="COMMAND" +>ssh(1)</B +> +and wrote custom, in-house scripts.</P +></LI +><LI +><P +>And finally, the amount of information which is stored in an +smbpasswd entry leaves no room for additional attributes such as +a home directory, password expiration time, or even a Relative +Identified (RID).</P +></LI +></UL +><P +>As a result of these defeciencies, a more robust means of storing user attributes +used by smbd was developed. The API which defines access to user accounts +is commonly referred to as the samdb interface (previously this was called the passdb +API, and is still so named in the CVS trees). In Samba 2.2.3, enabling support +for a samdb backend (e.g. <TT +CLASS="PARAMETER" +><I +>--with-ldapsam</I +></TT +> or +<TT +CLASS="PARAMETER" +><I +>--with-tdbsam</I +></TT +>) requires compile time support.</P +><P +>When compiling Samba to include the <TT +CLASS="PARAMETER" +><I +>--with-ldapsam</I +></TT +> autoconf +option, smbd (and associated tools) will store and lookup user accounts in +an LDAP directory. In reality, this is very easy to understand. If you are +comfortable with using an smbpasswd file, simply replace "smbpasswd" with +"LDAP directory" in all the documentation.</P +><P +>There are a few points to stress about what the <TT +CLASS="PARAMETER" +><I +>--with-ldapsam</I +></TT +> +does not provide. The LDAP support referred to in the this documentation does not +include:</P +><P +></P +><UL +><LI +><P +>A means of retrieving user account information from + an Windows 2000 Active Directory server.</P +></LI +><LI +><P +>A means of replacing /etc/passwd.</P +></LI +></UL +><P +>The second item can be accomplished by using LDAP NSS and PAM modules. LGPL +versions of these libraries can be obtained from PADL Software +(<A +HREF="http://www.padl.com/" +TARGET="_top" +>http://www.padl.com/</A +>). However, +the details of configuring these packages are beyond the scope of this document.</P +></DIV +><DIV +CLASS="SECT2" +><HR><H3 +CLASS="SECT2" +><A +NAME="AEN447" +></A +>3.6.3. Supported LDAP Servers</H3 +><P +>The LDAP samdb code in 2.2.3 has been developed and tested using the OpenLDAP +2.0 server and client libraries. The same code should be able to work with +Netscape's Directory Server and client SDK. However, due to lack of testing +so far, there are bound to be compile errors and bugs. These should not be +hard to fix. If you are so inclined, please be sure to forward all patches to +<A +HREF="samba-patches@samba.org" +TARGET="_top" +>samba-patches@samba.org</A +> and +<A +HREF="jerry@samba.org" +TARGET="_top" +>jerry@samba.org</A +>.</P +></DIV +><DIV +CLASS="SECT2" +><HR><H3 +CLASS="SECT2" +><A +NAME="AEN452" +></A +>3.6.4. Schema and Relationship to the RFC 2307 posixAccount</H3 +><P +>Samba 3.0 includes the necessary schema file for OpenLDAP 2.0 in +<TT +CLASS="FILENAME" +>examples/LDAP/samba.schema</TT +>. The sambaAccount objectclass is given here:</P +><P +><PRE +CLASS="PROGRAMLISTING" +>objectclass ( 1.3.1.5.1.4.1.7165.2.2.2 NAME 'sambaAccount' SUP top STRUCTURAL + DESC 'Samba Account' + MUST ( uid $ rid ) + MAY ( cn $ lmPassword $ ntPassword $ pwdLastSet $ logonTime $ + logoffTime $ kickoffTime $ pwdCanChange $ pwdMustChange $ acctFlags $ + displayName $ smbHome $ homeDrive $ scriptPath $ profilePath $ + description $ userWorkstations $ primaryGroupID $ domain ))</PRE +></P +><P +>The samba.schema file has been formatted for OpenLDAP 2.0. The OID's are +owned by the Samba Team and as such is legal to be openly published. +If you translate the schema to be used with Netscape DS, please +submit the modified schema file as a patch to <A +HREF="jerry@samba.org" +TARGET="_top" +>jerry@samba.org</A +></P +><P +>Just as the smbpasswd file is mean to store information which supplements a +user's <TT +CLASS="FILENAME" +>/etc/passwd</TT +> entry, so is the sambaAccount object +meant to supplement the UNIX user account information. A sambaAccount is a +<TT +CLASS="CONSTANT" +>STRUCTURAL</TT +> objectclass so it can be stored individually +in the directory. However, there are several fields (e.g. uid) which overlap +with the posixAccount objectclass outlined in RFC2307. This is by design.</P +><P +>In order to store all user account information (UNIX and Samba) in the directory, +it is necessary to use the sambaAccount and posixAccount objectclasses in +combination. However, smbd will still obtain the user's UNIX account +information via the standard C library calls (e.g. getpwnam(), et. al.). +This means that the Samba server must also have the LDAP NSS library installed +and functioning correctly. This division of information makes it possible to +store all Samba account information in LDAP, but still maintain UNIX account +information in NIS while the network is transitioning to a full LDAP infrastructure.</P +></DIV +><DIV +CLASS="SECT2" +><HR><H3 +CLASS="SECT2" +><A +NAME="AEN464" +></A +>3.6.5. Configuring Samba with LDAP</H3 +><DIV +CLASS="SECT3" +><H4 +CLASS="SECT3" +><A +NAME="AEN466" +></A +>3.6.5.1. OpenLDAP configuration</H4 +><P +>To include support for the sambaAccount object in an OpenLDAP directory +server, first copy the samba.schema file to slapd's configuration directory.</P +><P +><TT +CLASS="PROMPT" +>root# </TT +><B +CLASS="COMMAND" +>cp samba.schema /etc/openldap/schema/</B +></P +><P +>Next, include the <TT +CLASS="FILENAME" +>samba.schema</TT +> file in <TT +CLASS="FILENAME" +>slapd.conf</TT +>. +The sambaAccount object contains two attributes which depend upon other schema +files. The 'uid' attribute is defined in <TT +CLASS="FILENAME" +>cosine.schema</TT +> and +the 'displayName' attribute is defined in the <TT +CLASS="FILENAME" +>inetorgperson.schema</TT +> +file. Both of these must be included before the <TT +CLASS="FILENAME" +>samba.schema</TT +> file.</P +><P +><PRE +CLASS="PROGRAMLISTING" +>## /etc/openldap/slapd.conf + +## schema files (core.schema is required by default) +include /etc/openldap/schema/core.schema + +## needed for sambaAccount +include /etc/openldap/schema/cosine.schema +include /etc/openldap/schema/inetorgperson.schema +include /etc/openldap/schema/samba.schema + +## uncomment this line if you want to support the RFC2307 (NIS) schema +## include /etc/openldap/schema/nis.schema + +....</PRE +></P +><P +>It is recommended that you maintain some indices on some of the most usefull attributes, +like in the following example, to speed up searches made on sambaAccount objectclasses +(and possibly posixAccount and posixGroup as well).</P +><P +><PRE +CLASS="PROGRAMLISTING" +># Indices to maintain +## required by OpenLDAP 2.0 +index objectclass eq + +## support pb_getsampwnam() +index uid pres,eq +## support pdb_getsambapwrid() +index rid eq + +## uncomment these if you are storing posixAccount and +## posixGroup entries in the directory as well +##index uidNumber eq +##index gidNumber eq +##index cn eq +##index memberUid eq</PRE +></P +></DIV +><DIV +CLASS="SECT3" +><HR><H4 +CLASS="SECT3" +><A +NAME="AEN483" +></A +>3.6.5.2. Configuring Samba</H4 +><P +>The following parameters are available in smb.conf only with <TT +CLASS="PARAMETER" +><I +>--with-ldapsam</I +></TT +> +was included with compiling Samba.</P +><P +></P +><UL +><LI +><P +><A +HREF="smb.conf.5.html#LDAPSSL" +TARGET="_top" +>ldap ssl</A +></P +></LI +><LI +><P +><A +HREF="smb.conf.5.html#LDAPSERVER" +TARGET="_top" +>ldap server</A +></P +></LI +><LI +><P +><A +HREF="smb.conf.5.html#LDAPADMINDN" +TARGET="_top" +>ldap admin dn</A +></P +></LI +><LI +><P +><A +HREF="smb.conf.5.html#LDAPSUFFIX" +TARGET="_top" +>ldap suffix</A +></P +></LI +><LI +><P +><A +HREF="smb.conf.5.html#LDAPFILTER" +TARGET="_top" +>ldap filter</A +></P +></LI +><LI +><P +><A +HREF="smb.conf.5.html#LDAPPORT" +TARGET="_top" +>ldap port</A +></P +></LI +></UL +><P +>These are described in the <A +HREF="smb.conf.5.html" +TARGET="_top" +>smb.conf(5)</A +> man +page and so will not be repeated here. However, a sample smb.conf file for +use with an LDAP directory could appear as</P +><P +><PRE +CLASS="PROGRAMLISTING" +>## /usr/local/samba/lib/smb.conf +[global] + security = user + encrypt passwords = yes + + netbios name = TASHTEGO + workgroup = NARNIA + + # ldap related parameters + + # define the DN to use when binding to the directory servers + # The password for this DN is not stored in smb.conf. Rather it + # must be set by using 'smbpasswd -w <TT +CLASS="REPLACEABLE" +><I +>secretpw</I +></TT +>' to store the + # passphrase in the secrets.tdb file. If the "ldap admin dn" values + # changes, this password will need to be reset. + ldap admin dn = "cn=Samba Manager,ou=people,dc=samba,dc=org" + + # specify the LDAP server's hostname (defaults to locahost) + ldap server = ahab.samba.org + + # Define the SSL option when connecting to the directory + # ('off', 'start tls', or 'on' (default)) + ldap ssl = start tls + + # define the port to use in the LDAP session (defaults to 636 when + # "ldap ssl = on") + ldap port = 389 + + # specify the base DN to use when searching the directory + ldap suffix = "ou=people,dc=samba,dc=org" + + # generally the default ldap search filter is ok + # ldap filter = "(&(uid=%u)(objectclass=sambaAccount))"</PRE +></P +></DIV +></DIV +><DIV +CLASS="SECT2" +><HR><H3 +CLASS="SECT2" +><A +NAME="AEN511" +></A +>3.6.6. Accounts and Groups management</H3 +><P +>As users accounts are managed thru the sambaAccount objectclass, you should +modify you existing administration tools to deal with sambaAccount attributes.</P +><P +>Machines accounts are managed with the sambaAccount objectclass, just +like users accounts. However, it's up to you to stored thoses accounts +in a different tree of you LDAP namespace: you should use +"ou=Groups,dc=plainjoe,dc=org" to store groups and +"ou=People,dc=plainjoe,dc=org" to store users. Just configure your +NSS and PAM accordingly (usually, in the /etc/ldap.conf configuration +file).</P +><P +>In Samba release 3.0, the group management system is based on posix +groups. This means that Samba make usage of the posixGroup objectclass. +For now, there is no NT-like group system management (global and local +groups).</P +></DIV +><DIV +CLASS="SECT2" +><HR><H3 +CLASS="SECT2" +><A +NAME="AEN516" +></A +>3.6.7. Security and sambaAccount</H3 +><P +>There are two important points to remember when discussing the security +of sambaAccount entries in the directory.</P +><P +></P +><UL +><LI +><P +><SPAN +CLASS="emphasis" +><I +CLASS="EMPHASIS" +>Never</I +></SPAN +> retrieve the lmPassword or + ntPassword attribute values over an unencrypted LDAP session.</P +></LI +><LI +><P +><SPAN +CLASS="emphasis" +><I +CLASS="EMPHASIS" +>Never</I +></SPAN +> allow non-admin users to + view the lmPassword or ntPassword attribute values.</P +></LI +></UL +><P +>These password hashes are clear text equivalents and can be used to impersonate +the user without deriving the original clear text strings. For more information +on the details of LM/NT password hashes, refer to the <A +HREF="ENCRYPTION.html" +TARGET="_top" +>ENCRYPTION chapter</A +> of the Samba-HOWTO-Collection.</P +><P +>To remedy the first security issue, the "ldap ssl" smb.conf parameter defaults +to require an encrypted session (<B +CLASS="COMMAND" +>ldap ssl = on</B +>) using +the default port of 636 +when contacting the directory server. When using an OpenLDAP 2.0 server, it +is possible to use the use the StartTLS LDAP extended operation in the place of +LDAPS. In either case, you are strongly discouraged to disable this security +(<B +CLASS="COMMAND" +>ldap ssl = off</B +>).</P +><P +>Note that the LDAPS protocol is deprecated in favor of the LDAPv3 StartTLS +extended operation. However, the OpenLDAP library still provides support for +the older method of securing communication between clients and servers.</P +><P +>The second security precaution is to prevent non-administrative users from +harvesting password hashes from the directory. This can be done using the +following ACL in <TT +CLASS="FILENAME" +>slapd.conf</TT +>:</P +><P +><PRE +CLASS="PROGRAMLISTING" +>## allow the "ldap admin dn" access, but deny everyone else +access to attrs=lmPassword,ntPassword + by dn="cn=Samba Admin,ou=people,dc=plainjoe,dc=org" write + by * none</PRE +></P +></DIV +><DIV +CLASS="SECT2" +><HR><H3 +CLASS="SECT2" +><A +NAME="AEN536" +></A +>3.6.8. LDAP specials attributes for sambaAccounts</H3 +><P +>The sambaAccount objectclass is composed of the following attributes:</P +><P +></P +><UL +><LI +><P +><TT +CLASS="CONSTANT" +>lmPassword</TT +>: the LANMAN password 16-byte hash stored as a character + representation of a hexidecimal string.</P +></LI +><LI +><P +><TT +CLASS="CONSTANT" +>ntPassword</TT +>: the NT password hash 16-byte stored as a character + representation of a hexidecimal string.</P +></LI +><LI +><P +><TT +CLASS="CONSTANT" +>pwdLastSet</TT +>: The integer time in seconds since 1970 when the + <TT +CLASS="CONSTANT" +>lmPassword</TT +> and <TT +CLASS="CONSTANT" +>ntPassword</TT +> attributes were last set. + </P +></LI +><LI +><P +><TT +CLASS="CONSTANT" +>acctFlags</TT +>: string of 11 characters surrounded by square brackets [] + representing account flags such as U (user), W(workstation), X(no password expiration), and + D(disabled).</P +></LI +><LI +><P +><TT +CLASS="CONSTANT" +>logonTime</TT +>: Integer value currently unused</P +></LI +><LI +><P +><TT +CLASS="CONSTANT" +>logoffTime</TT +>: Integer value currently unused</P +></LI +><LI +><P +><TT +CLASS="CONSTANT" +>kickoffTime</TT +>: Integer value currently unused</P +></LI +><LI +><P +><TT +CLASS="CONSTANT" +>pwdCanChange</TT +>: Integer value currently unused</P +></LI +><LI +><P +><TT +CLASS="CONSTANT" +>pwdMustChange</TT +>: Integer value currently unused</P +></LI +><LI +><P +><TT +CLASS="CONSTANT" +>homeDrive</TT +>: specifies the drive letter to which to map the + UNC path specified by homeDirectory. The drive letter must be specified in the form "X:" + where X is the letter of the drive to map. Refer to the "logon drive" parameter in the + smb.conf(5) man page for more information.</P +></LI +><LI +><P +><TT +CLASS="CONSTANT" +>scriptPath</TT +>: The scriptPath property specifies the path of + the user's logon script, .CMD, .EXE, or .BAT file. The string can be null. The path + is relative to the netlogon share. Refer to the "logon script" parameter in the + smb.conf(5) man page for more information.</P +></LI +><LI +><P +><TT +CLASS="CONSTANT" +>profilePath</TT +>: specifies a path to the user's profile. + This value can be a null string, a local absolute path, or a UNC path. Refer to the + "logon path" parameter in the smb.conf(5) man page for more information.</P +></LI +><LI +><P +><TT +CLASS="CONSTANT" +>smbHome</TT +>: The homeDirectory property specifies the path of + the home directory for the user. The string can be null. If homeDrive is set and specifies + a drive letter, homeDirectory should be a UNC path. The path must be a network + UNC path of the form \\server\share\directory. This value can be a null string. + Refer to the "logon home" parameter in the smb.conf(5) man page for more information. + </P +></LI +><LI +><P +><TT +CLASS="CONSTANT" +>userWorkstation</TT +>: character string value currently unused. + </P +></LI +><LI +><P +><TT +CLASS="CONSTANT" +>rid</TT +>: the integer representation of the user's relative identifier + (RID).</P +></LI +><LI +><P +><TT +CLASS="CONSTANT" +>primaryGroupID</TT +>: the relative identifier (RID) of the primary group + of the user.</P +></LI +></UL +><P +>The majority of these parameters are only used when Samba is acting as a PDC of +a domain (refer to the <A +HREF="Samba-PDC-HOWTO.html" +TARGET="_top" +>Samba-PDC-HOWTO</A +> for details on +how to configure Samba as a Primary Domain Controller). The following four attributes +are only stored with the sambaAccount entry if the values are non-default values:</P +><P +></P +><UL +><LI +><P +>smbHome</P +></LI +><LI +><P +>scriptPath</P +></LI +><LI +><P +>logonPath</P +></LI +><LI +><P +>homeDrive</P +></LI +></UL +><P +>These attributes are only stored with the sambaAccount entry if +the values are non-default values. For example, assume TASHTEGO has now been +configured as a PDC and that <B +CLASS="COMMAND" +>logon home = \\%L\%u</B +> was defined in +its <TT +CLASS="FILENAME" +>smb.conf</TT +> file. When a user named "becky" logons to the domain, +the <TT +CLASS="PARAMETER" +><I +>logon home</I +></TT +> string is expanded to \\TASHTEGO\becky. +If the smbHome attribute exists in the entry "uid=becky,ou=people,dc=samba,dc=org", +this value is used. However, if this attribute does not exist, then the value +of the <TT +CLASS="PARAMETER" +><I +>logon home</I +></TT +> parameter is used in its place. Samba +will only write the attribute value to the directory entry is the value is +something other than the default (e.g. \\MOBY\becky).</P +></DIV +><DIV +CLASS="SECT2" +><HR><H3 +CLASS="SECT2" +><A +NAME="AEN606" +></A +>3.6.9. Example LDIF Entries for a sambaAccount</H3 +><P +>The following is a working LDIF with the inclusion of the posixAccount objectclass:</P +><P +><PRE +CLASS="PROGRAMLISTING" +>dn: uid=guest2, ou=people,dc=plainjoe,dc=org +ntPassword: 878D8014606CDA29677A44EFA1353FC7 +pwdMustChange: 2147483647 +primaryGroupID: 1201 +lmPassword: 552902031BEDE9EFAAD3B435B51404EE +pwdLastSet: 1010179124 +logonTime: 0 +objectClass: sambaAccount +uid: guest2 +kickoffTime: 2147483647 +acctFlags: [UX ] +logoffTime: 2147483647 +rid: 19006 +pwdCanChange: 0</PRE +></P +><P +>The following is an LDIF entry for using both the sambaAccount and +posixAccount objectclasses:</P +><P +><PRE +CLASS="PROGRAMLISTING" +>dn: uid=gcarter, ou=people,dc=plainjoe,dc=org +logonTime: 0 +displayName: Gerald Carter +lmPassword: 552902031BEDE9EFAAD3B435B51404EE +primaryGroupID: 1201 +objectClass: posixAccount +objectClass: sambaAccount +acctFlags: [UX ] +userPassword: {crypt}BpM2ej8Rkzogo +uid: gcarter +uidNumber: 9000 +cn: Gerald Carter +loginShell: /bin/bash +logoffTime: 2147483647 +gidNumber: 100 +kickoffTime: 2147483647 +pwdLastSet: 1010179230 +rid: 19000 +homeDirectory: /home/tashtego/gcarter +pwdCanChange: 0 +pwdMustChange: 2147483647 +ntPassword: 878D8014606CDA29677A44EFA1353FC7</PRE +></P +></DIV +></DIV +><DIV +CLASS="SECT1" +><HR><H2 +CLASS="SECT1" +><A +NAME="AEN614" +></A +>3.7. MySQL</H2 +><DIV +CLASS="SECT2" +><H3 +CLASS="SECT2" +><A +NAME="AEN616" +></A +>3.7.1. Building</H3 +><P +>To build the plugin, run <B +CLASS="COMMAND" +>make bin/pdb_mysql.so</B +> +in the <TT +CLASS="FILENAME" +>source/</TT +> directory of samba distribution. </P +><P +>Next, copy pdb_mysql.so to any location you want. I +strongly recommend installing it in $PREFIX/lib or /usr/lib/samba/</P +></DIV +><DIV +CLASS="SECT2" +><HR><H3 +CLASS="SECT2" +><A +NAME="AEN622" +></A +>3.7.2. Creating the database</H3 +><P +>You either can set up your own table and specify the field names to pdb_mysql (see below +for the column names) or use the default table. The file <TT +CLASS="FILENAME" +>examples/pdb/mysql/mysql.dump</TT +> +contains the correct queries to create the required tables. Use the command : + +<B +CLASS="COMMAND" +>mysql -u<TT +CLASS="REPLACEABLE" +><I +>username</I +></TT +> -h<TT +CLASS="REPLACEABLE" +><I +>hostname</I +></TT +> -p<TT +CLASS="REPLACEABLE" +><I +>password</I +></TT +> <TT +CLASS="REPLACEABLE" +><I +>databasename</I +></TT +> < <TT +CLASS="FILENAME" +>/path/to/samba/examples/pdb/mysql/mysql.dump</TT +></B +> </P +></DIV +><DIV +CLASS="SECT2" +><HR><H3 +CLASS="SECT2" +><A +NAME="AEN632" +></A +>3.7.3. Configuring</H3 +><P +>This plugin lacks some good documentation, but here is some short info:</P +><P +>Add a the following to the <B +CLASS="COMMAND" +>passdb backend</B +> variable in your <TT +CLASS="FILENAME" +>smb.conf</TT +>: +<PRE +CLASS="PROGRAMLISTING" +>passdb backend = [other-plugins] plugin:/location/to/pdb_mysql.so:identifier [other-plugins]</PRE +></P +><P +>The identifier can be any string you like, as long as it doesn't collide with +the identifiers of other plugins or other instances of pdb_mysql. If you +specify multiple pdb_mysql.so entries in 'passdb backend', you also need to +use different identifiers!</P +><P +>Additional options can be given thru the smb.conf file in the [global] section.</P +><P +><PRE +CLASS="PROGRAMLISTING" +>identifier:mysql host - host name, defaults to 'localhost' +identifier:mysql password +identifier:mysql user - defaults to 'samba' +identifier:mysql database - defaults to 'samba' +identifier:mysql port - defaults to 3306 +identifier:table - Name of the table containing users</PRE +></P +><DIV +CLASS="WARNING" +><P +></P +><TABLE +CLASS="WARNING" +WIDTH="100%" +BORDER="0" +><TR +><TD +WIDTH="25" +ALIGN="CENTER" +VALIGN="TOP" +><IMG +SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/warning.gif" +HSPACE="5" +ALT="Warning"></TD +><TD +ALIGN="LEFT" +VALIGN="TOP" +><P +>Since the password for the mysql user is stored in the +smb.conf file, you should make the the smb.conf file +readable only to the user that runs samba. This is considered a security +bug and will be fixed soon.</P +></TD +></TR +></TABLE +></DIV +><P +>Names of the columns in this table(I've added column types those columns should have first):</P +><P +><PRE +CLASS="PROGRAMLISTING" +>identifier:logon time column - int(9) +identifier:logoff time column - int(9) +identifier:kickoff time column - int(9) +identifier:pass last set time column - int(9) +identifier:pass can change time column - int(9) +identifier:pass must change time column - int(9) +identifier:username column - varchar(255) - unix username +identifier:domain column - varchar(255) - NT domain user is part of +identifier:nt username column - varchar(255) - NT username +identifier:fullname column - varchar(255) - Full name of user +identifier:home dir column - varchar(255) - Unix homedir path +identifier:dir drive column - varchar(2) - Directory drive path (eg: 'H:') +identifier:logon script column - varchar(255) - Batch file to run on client side when logging on +identifier:profile path column - varchar(255) - Path of profile +identifier:acct desc column - varchar(255) - Some ASCII NT user data +identifier:workstations column - varchar(255) - Workstations user can logon to (or NULL for all) +identifier:unknown string column - varchar(255) - unknown string +identifier:munged dial column - varchar(255) - ? +identifier:uid column - int(9) - Unix user ID (uid) +identifier:gid column - int(9) - Unix user group (gid) +identifier:user sid column - varchar(255) - NT user SID +identifier:group sid column - varchar(255) - NT group ID +identifier:lanman pass column - varchar(255) - encrypted lanman password +identifier:nt pass column - varchar(255) - encrypted nt passwd +identifier:plain pass column - varchar(255) - plaintext password +identifier:acct control column - int(9) - nt user data +identifier:unknown 3 column - int(9) - unknown +identifier:logon divs column - int(9) - ? +identifier:hours len column - int(9) - ? +identifier:unknown 5 column - int(9) - unknown +identifier:unknown 6 column - int(9) - unknown</PRE +></P +><P +>Eventually, you can put a colon (:) after the name of each column, which +should specify the column to update when updating the table. You can also +specify nothing behind the colon - then the data from the field will not be +updated. </P +></DIV +><DIV +CLASS="SECT2" +><HR><H3 +CLASS="SECT2" +><A +NAME="AEN649" +></A +>3.7.4. Using plaintext passwords or encrypted password</H3 +><P +>I strongly discourage the use of plaintext passwords, however, you can use them:</P +><P +>If you would like to use plaintext passwords, set 'identifier:lanman pass column' and 'identifier:nt pass column' to 'NULL' (without the quotes) and 'identifier:plain pass column' to the name of the column containing the plaintext passwords. </P +><P +>If you use encrypted passwords, set the 'identifier:plain pass column' to 'NULL' (without the quotes). This is the default.</P +></DIV +><DIV +CLASS="SECT2" +><HR><H3 +CLASS="SECT2" +><A +NAME="AEN654" +></A +>3.7.5. Getting non-column data from the table</H3 +><P +>It is possible to have not all data in the database and making some 'constant'.</P +><P +>For example, you can set 'identifier:fullname column' to : +<B +CLASS="COMMAND" +>CONCAT(First_name,' ',Sur_name)</B +></P +><P +>Or, set 'identifier:workstations column' to : +<B +CLASS="COMMAND" +>NULL</B +></P +><P +>See the MySQL documentation for more language constructs.</P +></DIV +></DIV +><DIV +CLASS="SECT1" +><HR><H2 +CLASS="SECT1" +><A +NAME="AEN662" +></A +>3.8. Passdb XML plugin</H2 +><DIV +CLASS="SECT2" +><H3 +CLASS="SECT2" +><A +NAME="AEN664" +></A +>3.8.1. Building</H3 +><P +>This module requires libxml2 to be installed.</P +><P +>To build pdb_xml, run: <B +CLASS="COMMAND" +>make bin/pdb_xml.so</B +> in +the directory <TT +CLASS="FILENAME" +>source/</TT +>. </P +></DIV +><DIV +CLASS="SECT2" +><HR><H3 +CLASS="SECT2" +><A +NAME="AEN670" +></A +>3.8.2. Usage</H3 +><P +>The usage of pdb_xml is pretty straightforward. To export data, use: + +<B +CLASS="COMMAND" +>pdbedit -e plugin:/usr/lib/samba/pdb_xml.so:filename</B +> + +(where filename is the name of the file to put the data in)</P +><P +>To import data, use: +<B +CLASS="COMMAND" +>pdbedit -i plugin:/usr/lib/samba/pdb_xml.so:filename -e current-pdb</B +> + +Where filename is the name to read the data from and current-pdb to put it in.</P +></DIV +></DIV ></DIV ></DIV ><DIV CLASS="PART" ><A -NAME="AEN544" +NAME="TYPE" ></A ><DIV CLASS="TITLEPAGE" @@ -3599,14 +3944,13 @@ CLASS="TITLE" ><DIV CLASS="PARTINTRO" ><A -NAME="AEN546" +NAME="AEN678" ></A ><H1 >Introduction</H1 ><P ->This part contains information on using samba in a (NT 4 or ADS) domain. -If you wish to run samba as a domain member or DC, read the appropriate chapter in -this part.</P +>Samba can operate in various SMB networks. This part contains information on configuring samba +for various environments.</P ></DIV ><DIV CLASS="TOC" @@ -3616,228 +3960,238 @@ CLASS="TOC" >Table of Contents</B ></DT ><DT ->6. <A +>4. <A +HREF="#SECURITYLEVELS" +>User and Share security level (for servers not in a domain)</A +></DT +><DT +>5. <A HREF="#SAMBA-PDC" ->How to Configure Samba as a NT4 Primary Domain Controller</A +>Samba as a NT4 or Win2k Primary Domain Controller</A ></DT ><DD ><DL ><DT ->6.1. <A -HREF="#AEN566" +>5.1. <A +HREF="#AEN722" >Prerequisite Reading</A ></DT ><DT ->6.2. <A -HREF="#AEN572" +>5.2. <A +HREF="#AEN728" >Background</A ></DT ><DT ->6.3. <A -HREF="#AEN611" +>5.3. <A +HREF="#AEN767" >Configuring the Samba Domain Controller</A ></DT ><DT ->6.4. <A -HREF="#AEN654" +>5.4. <A +HREF="#AEN810" >Creating Machine Trust Accounts and Joining Clients to the Domain</A ></DT ><DD ><DL ><DT ->6.4.1. <A -HREF="#AEN673" +>5.4.1. <A +HREF="#AEN829" >Manual Creation of Machine Trust Accounts</A ></DT ><DT ->6.4.2. <A -HREF="#AEN714" +>5.4.2. <A +HREF="#AEN870" >"On-the-Fly" Creation of Machine Trust Accounts</A ></DT ><DT ->6.4.3. <A -HREF="#AEN723" +>5.4.3. <A +HREF="#AEN879" >Joining the Client to the Domain</A ></DT ></DL ></DD ><DT ->6.5. <A -HREF="#AEN738" +>5.5. <A +HREF="#AEN894" >Common Problems and Errors</A ></DT ><DT ->6.6. <A -HREF="#AEN786" +>5.6. <A +HREF="#AEN942" >System Policies and Profiles</A ></DT ><DT ->6.7. <A -HREF="#AEN830" +>5.7. <A +HREF="#AEN986" >What other help can I get?</A ></DT ><DT ->6.8. <A -HREF="#AEN944" +>5.8. <A +HREF="#AEN1100" >Domain Control for Windows 9x/ME</A ></DT ><DD ><DL ><DT ->6.8.1. <A -HREF="#AEN970" +>5.8.1. <A +HREF="#AEN1126" >Configuration Instructions: Network Logons</A ></DT ><DT ->6.8.2. <A -HREF="#AEN989" +>5.8.2. <A +HREF="#AEN1145" >Configuration Instructions: Setting up Roaming User Profiles</A ></DT ></DL ></DD ><DT ->6.9. <A -HREF="#AEN1082" ->DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba</A +>5.9. <A +HREF="#AEN1238" +>DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba</A ></DT ></DL ></DD ><DT ->7. <A +>6. <A HREF="#SAMBA-BDC" >How to Act as a Backup Domain Controller in a Purely Samba Controlled Domain</A ></DT ><DD ><DL ><DT ->7.1. <A -HREF="#AEN1118" +>6.1. <A +HREF="#AEN1274" >Prerequisite Reading</A ></DT ><DT ->7.2. <A -HREF="#AEN1122" +>6.2. <A +HREF="#AEN1278" >Background</A ></DT ><DT ->7.3. <A -HREF="#AEN1130" +>6.3. <A +HREF="#AEN1286" >What qualifies a Domain Controller on the network?</A ></DT ><DD ><DL ><DT ->7.3.1. <A -HREF="#AEN1133" +>6.3.1. <A +HREF="#AEN1289" >How does a Workstation find its domain controller?</A ></DT ><DT ->7.3.2. <A -HREF="#AEN1136" +>6.3.2. <A +HREF="#AEN1292" >When is the PDC needed?</A ></DT ></DL ></DD ><DT ->7.4. <A -HREF="#AEN1139" ->Can Samba be a Backup Domain Controller?</A +>6.4. <A +HREF="#AEN1295" +>Can Samba be a Backup Domain Controller to an NT PDC?</A ></DT ><DT ->7.5. <A -HREF="#AEN1143" +>6.5. <A +HREF="#AEN1300" >How do I set up a Samba BDC?</A ></DT ><DD ><DL ><DT ->7.5.1. <A -HREF="#AEN1160" +>6.5.1. <A +HREF="#AEN1317" >How do I replicate the smbpasswd file?</A ></DT +><DT +>6.5.2. <A +HREF="#AEN1321" +>Can I do this all with LDAP?</A +></DT ></DL ></DD ></DL ></DD ><DT ->8. <A +>7. <A HREF="#ADS" >Samba as a ADS domain member</A ></DT ><DD ><DL ><DT ->8.1. <A -HREF="#AEN1178" +>7.1. <A +HREF="#AEN1339" >Installing the required packages for Debian</A ></DT ><DT ->8.2. <A -HREF="#AEN1184" +>7.2. <A +HREF="#AEN1346" >Installing the required packages for RedHat</A ></DT ><DT ->8.3. <A -HREF="#AEN1193" +>7.3. <A +HREF="#AEN1356" >Compile Samba</A ></DT ><DT ->8.4. <A -HREF="#AEN1205" +>7.4. <A +HREF="#AEN1371" >Setup your /etc/krb5.conf</A ></DT ><DT ->8.5. <A -HREF="#AEN1215" +>7.5. <A +HREF="#AEN1381" >Create the computer account</A ></DT ><DD ><DL ><DT ->8.5.1. <A -HREF="#AEN1219" +>7.5.1. <A +HREF="#AEN1385" >Possible errors</A ></DT ></DL ></DD ><DT ->8.6. <A -HREF="#AEN1231" +>7.6. <A +HREF="#AEN1393" >Test your server setup</A ></DT ><DT ->8.7. <A -HREF="#AEN1236" +>7.7. <A +HREF="#AEN1398" >Testing with smbclient</A ></DT ><DT ->8.8. <A -HREF="#AEN1239" +>7.8. <A +HREF="#AEN1401" >Notes</A ></DT ></DL ></DD ><DT ->9. <A +>8. <A HREF="#DOMAIN-SECURITY" ->Samba as a NT4 domain member</A +>Samba as a NT4 or Win2k domain member</A ></DT ><DD ><DL ><DT ->9.1. <A -HREF="#AEN1261" ->Joining an NT Domain with Samba 2.2</A +>8.1. <A +HREF="#AEN1423" +>Joining an NT Domain with Samba 3.0</A ></DT ><DT ->9.2. <A -HREF="#AEN1325" +>8.2. <A +HREF="#AEN1478" >Samba and Windows 2000 Domains</A ></DT ><DT ->9.3. <A -HREF="#AEN1330" +>8.3. <A +HREF="#AEN1481" >Why is this better than security = server?</A ></DT ></DL @@ -3849,17 +4203,117 @@ HREF="#AEN1330" CLASS="CHAPTER" ><HR><H1 ><A +NAME="SECURITYLEVELS" +></A +>Chapter 4. User and Share security level (for servers not in a domain)</H1 +><P +>A SMB server tells the client at startup what "security level" it is +running. There are two options "share level" and "user level". Which +of these two the client receives affects the way the client then tries +to authenticate itself. It does not directly affect (to any great +extent) the way the Samba server does security. I know this is +strange, but it fits in with the client/server approach of SMB. In SMB +everything is initiated and controlled by the client, and the server +can only tell the client what is available and whether an action is +allowed. </P +><P +>I'll describe user level security first, as its simpler. In user level +security the client will send a "session setup" command directly after +the protocol negotiation. This contains a username and password. The +server can either accept or reject that username/password +combination. Note that at this stage the server has no idea what +share the client will eventually try to connect to, so it can't base +the "accept/reject" on anything other than:</P +><P +></P +><OL +TYPE="1" +><LI +><P +>the username/password</P +></LI +><LI +><P +>the machine that the client is coming from</P +></LI +></OL +><P +>If the server accepts the username/password then the client expects to +be able to mount any share (using a "tree connection") without +specifying a password. It expects that all access rights will be as +the username/password specified in the "session setup". </P +><P +>It is also possible for a client to send multiple "session setup" +requests. When the server responds it gives the client a "uid" to use +as an authentication tag for that username/password. The client can +maintain multiple authentication contexts in this way (WinDD is an +example of an application that does this)</P +><P +>Ok, now for share level security. In share level security the client +authenticates itself separately for each share. It will send a +password along with each "tree connection" (share mount). It does not +explicitly send a username with this operation. The client is +expecting 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. It is never explicitly sent the +username. 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 that is authenticated, not a "share/password".</P +><P +>Many clients send a "session setup" even if the server is in share +level security. They normally send a valid username but no +password. Samba records this username in a list of "possible +usernames". When the client then does a "tree connection" it also adds +to this list the name of the share they try to connect to (useful for +home directories) and any users listed in the "user =" smb.conf +line. The password is then checked in turn against these "possible +usernames". If a match is found then the client is authenticated as +that user.</P +><P +>Finally "server level" security. In server level security the samba +server reports to the client that it is in user level security. The +client then does a "session setup" as described earlier. The samba +server takes the username/password that the client sends and attempts +to login to the "password server" by sending exactly the same +username/password that it got from the client. If that server is in +user level security and accepts the password then samba accepts the +clients connection. This allows the samba server to use another SMB +server as the "password server". </P +><P +>You should also note that at the very start of all this, where the +server tells the client what security level it is in, it also tells +the client if it supports encryption. If it does then it supplies the +client with a random "cryptkey". The client will then send all +passwords in encrypted form. You have to compile samba with encryption +enabled to support this feature, and you have to maintain a separate +smbpasswd file with SMB style encrypted passwords. It is +cryptographically impossible to translate from unix style encryption +to SMB style encryption, although there are some fairly simple management +schemes by which the two could be kept in sync.</P +><P +>"security = server" means that Samba reports to clients that +it is running in "user mode" but actually passes off all authentication +requests to another "user mode" server. This requires an additional +parameter "password server =" that points to the real authentication server. +That real authentication server can be another Samba server or can be a +Windows NT server, the later natively capable of encrypted password support.</P +></DIV +><DIV +CLASS="CHAPTER" +><HR><H1 +><A NAME="SAMBA-PDC" ></A ->Chapter 6. How to Configure Samba as a NT4 Primary Domain Controller</H1 +>Chapter 5. Samba as a NT4 or Win2k Primary Domain Controller</H1 ><DIV CLASS="SECT1" ><H2 CLASS="SECT1" ><A -NAME="AEN566" +NAME="AEN722" ></A ->6.1. Prerequisite Reading</H2 +>5.1. Prerequisite Reading</H2 ><P >Before you continue reading in this chapter, please make sure that you are comfortable with configuring basic files services @@ -3885,9 +4339,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN572" +NAME="AEN728" ></A ->6.2. Background</H2 +>5.2. Background</H2 ><DIV CLASS="NOTE" ><P @@ -3902,7 +4356,7 @@ WIDTH="25" ALIGN="CENTER" VALIGN="TOP" ><IMG -SRC="/docbook-dsssl/note.gif" +SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif" HSPACE="5" ALT="Note"></TD ><TD @@ -4037,9 +4491,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN611" +NAME="AEN767" ></A ->6.3. Configuring the Samba Domain Controller</H2 +>5.3. Configuring the Samba Domain Controller</H2 ><P >The first step in creating a working Samba PDC is to understand the parameters necessary in smb.conf. I will not @@ -4249,9 +4703,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN654" +NAME="AEN810" ></A ->6.4. Creating Machine Trust Accounts and Joining Clients to the +>5.4. Creating Machine Trust Accounts and Joining Clients to the Domain</H2 ><P >A machine trust account is a Samba account that is used to @@ -4323,9 +4777,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN673" +NAME="AEN829" ></A ->6.4.1. Manual Creation of Machine Trust Accounts</H3 +>5.4.1. Manual Creation of Machine Trust Accounts</H3 ><P >The first step in manually creating a machine trust account is to manually create the corresponding Unix account in @@ -4477,7 +4931,7 @@ WIDTH="25" ALIGN="CENTER" VALIGN="TOP" ><IMG -SRC="/docbook-dsssl/warning.gif" +SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/warning.gif" HSPACE="5" ALT="Warning"></TD ><TH @@ -4513,9 +4967,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN714" +NAME="AEN870" ></A ->6.4.2. "On-the-Fly" Creation of Machine Trust Accounts</H3 +>5.4.2. "On-the-Fly" Creation of Machine Trust Accounts</H3 ><P >The second (and recommended) way of creating machine trust accounts is simply to allow the Samba server to create them as needed when the client @@ -4541,7 +4995,7 @@ be created manually.</P ><PRE CLASS="PROGRAMLISTING" >[global] - # <...remainder of parameters...> + # <...remainder of parameters...> add user script = /usr/sbin/useradd -d /dev/null -g 100 -s /bin/false -M %u </PRE ></P ></DIV @@ -4550,9 +5004,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN723" +NAME="AEN879" ></A ->6.4.3. Joining the Client to the Domain</H3 +>5.4.3. Joining the Client to the Domain</H3 ><P >The procedure for joining a client to the domain varies with the version of Windows.</P @@ -4618,9 +5072,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN738" +NAME="AEN894" ></A ->6.5. Common Problems and Errors</H2 +>5.5. Common Problems and Errors</H2 ><P ></P ><P @@ -4828,9 +5282,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN786" +NAME="AEN942" ></A ->6.6. System Policies and Profiles</H2 +>5.6. System Policies and Profiles</H2 ><P >Much of the information necessary to implement System Policies and Roving User Profiles in a Samba domain is the same as that for @@ -5005,9 +5459,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN830" +NAME="AEN986" ></A ->6.7. What other help can I get?</H2 +>5.7. What other help can I get?</H2 ><P >There are many sources of information available in the form of mailing lists, RFC's and documentation. The docs that come @@ -5425,9 +5879,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN944" +NAME="AEN1100" ></A ->6.8. Domain Control for Windows 9x/ME</H2 +>5.8. Domain Control for Windows 9x/ME</H2 ><DIV CLASS="NOTE" ><P @@ -5442,7 +5896,7 @@ WIDTH="25" ALIGN="CENTER" VALIGN="TOP" ><IMG -SRC="/docbook-dsssl/note.gif" +SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif" HSPACE="5" ALT="Note"></TD ><TD @@ -5504,7 +5958,7 @@ TYPE="1" ><LI ><P > The client broadcasts (to the IP broadcast address of the subnet it is in) - a NetLogon request. This is sent to the NetBIOS name DOMAIN<1c> at the + a NetLogon request. This is sent to the NetBIOS name DOMAIN<1c> at the NetBIOS layer. The client chooses the first response it receives, which contains the NetBIOS name of the logon server to use in the format of \\SERVER. @@ -5559,9 +6013,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN970" +NAME="AEN1126" ></A ->6.8.1. Configuration Instructions: Network Logons</H3 +>5.8.1. Configuration Instructions: Network Logons</H3 ><P >The main difference between a PDC and a Windows 9x logon server configuration is that</P @@ -5594,7 +6048,7 @@ WIDTH="25" ALIGN="CENTER" VALIGN="TOP" ><IMG -SRC="/docbook-dsssl/warning.gif" +SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/warning.gif" HSPACE="5" ALT="Warning"></TD ><TH @@ -5665,9 +6119,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN989" +NAME="AEN1145" ></A ->6.8.2. Configuration Instructions: Setting up Roaming User Profiles</H3 +>5.8.2. Configuration Instructions: Setting up Roaming User Profiles</H3 ><DIV CLASS="WARNING" ><P @@ -5682,7 +6136,7 @@ WIDTH="25" ALIGN="CENTER" VALIGN="TOP" ><IMG -SRC="/docbook-dsssl/warning.gif" +SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/warning.gif" HSPACE="5" ALT="Warning"></TD ><TD @@ -5718,9 +6172,9 @@ CLASS="SECT3" ><HR><H4 CLASS="SECT3" ><A -NAME="AEN997" +NAME="AEN1153" ></A ->6.8.2.1. Windows NT Configuration</H4 +>5.8.2.1. Windows NT Configuration</H4 ><P >To support WinNT clients, in the [global] section of smb.conf set the following (for example):</P @@ -5749,7 +6203,7 @@ WIDTH="25" ALIGN="CENTER" VALIGN="TOP" ><IMG -SRC="/docbook-dsssl/note.gif" +SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif" HSPACE="5" ALT="Note"></TD ><TD @@ -5769,9 +6223,9 @@ CLASS="SECT3" ><HR><H4 CLASS="SECT3" ><A -NAME="AEN1005" +NAME="AEN1161" ></A ->6.8.2.2. Windows 9X Configuration</H4 +>5.8.2.2. Windows 9X Configuration</H4 ><P >To support Win9X clients, you must use the "logon home" parameter. Samba has now been fixed so that "net use/home" now works as well, and it, too, relies @@ -5800,9 +6254,9 @@ CLASS="SECT3" ><HR><H4 CLASS="SECT3" ><A -NAME="AEN1013" +NAME="AEN1169" ></A ->6.8.2.3. Win9X and WinNT Configuration</H4 +>5.8.2.3. Win9X and WinNT Configuration</H4 ><P >You can support profiles for both Win9X and WinNT clients by setting both the "logon home" and "logon path" parameters. For example:</P @@ -5826,7 +6280,7 @@ WIDTH="25" ALIGN="CENTER" VALIGN="TOP" ><IMG -SRC="/docbook-dsssl/note.gif" +SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif" HSPACE="5" ALT="Note"></TD ><TD @@ -5845,9 +6299,9 @@ CLASS="SECT3" ><HR><H4 CLASS="SECT3" ><A -NAME="AEN1020" +NAME="AEN1176" ></A ->6.8.2.4. Windows 9X Profile Setup</H4 +>5.8.2.4. Windows 9X Profile Setup</H4 ><P >When a user first logs in on Windows 9X, the file user.DAT is created, as are folders "Start Menu", "Desktop", "Programs" and "Nethood". @@ -6005,9 +6459,9 @@ CLASS="SECT3" ><HR><H4 CLASS="SECT3" ><A -NAME="AEN1056" +NAME="AEN1212" ></A ->6.8.2.5. Windows NT Workstation 4.0</H4 +>5.8.2.5. Windows NT Workstation 4.0</H4 ><P >When a user first logs in to a Windows NT Workstation, the profile NTuser.DAT is created. The profile location can be now specified @@ -6026,7 +6480,7 @@ WIDTH="25" ALIGN="CENTER" VALIGN="TOP" ><IMG -SRC="/docbook-dsssl/note.gif" +SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif" HSPACE="5" ALT="Note"></TD ><TD @@ -6084,7 +6538,7 @@ WIDTH="25" ALIGN="CENTER" VALIGN="TOP" ><IMG -SRC="/docbook-dsssl/note.gif" +SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif" HSPACE="5" ALT="Note"></TD ><TD @@ -6119,9 +6573,9 @@ CLASS="SECT3" ><HR><H4 CLASS="SECT3" ><A -NAME="AEN1069" +NAME="AEN1225" ></A ->6.8.2.6. Windows NT Server</H4 +>5.8.2.6. Windows NT Server</H4 ><P >There is nothing to stop you specifying any path that you like for the location of users' profiles. Therefore, you could specify that the @@ -6133,9 +6587,9 @@ CLASS="SECT3" ><HR><H4 CLASS="SECT3" ><A -NAME="AEN1072" +NAME="AEN1228" ></A ->6.8.2.7. Sharing Profiles between W95 and NT Workstation 4.0</H4 +>5.8.2.7. Sharing Profiles between W95 and NT Workstation 4.0</H4 ><DIV CLASS="WARNING" ><P @@ -6150,7 +6604,7 @@ WIDTH="25" ALIGN="CENTER" VALIGN="TOP" ><IMG -SRC="/docbook-dsssl/warning.gif" +SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/warning.gif" HSPACE="5" ALT="Warning"></TD ><TH @@ -6202,7 +6656,7 @@ WIDTH="25" ALIGN="CENTER" VALIGN="TOP" ><IMG -SRC="/docbook-dsssl/note.gif" +SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif" HSPACE="5" ALT="Note"></TD ><TD @@ -6226,9 +6680,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN1082" +NAME="AEN1238" ></A ->6.9. DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba</H2 +>5.9. DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba</H2 ><DIV CLASS="WARNING" ><P @@ -6243,7 +6697,7 @@ WIDTH="25" ALIGN="CENTER" VALIGN="TOP" ><IMG -SRC="/docbook-dsssl/warning.gif" +SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/warning.gif" HSPACE="5" ALT="Warning"></TD ><TH @@ -6365,15 +6819,15 @@ CLASS="CHAPTER" ><A NAME="SAMBA-BDC" ></A ->Chapter 7. How to Act as a Backup Domain Controller in a Purely Samba Controlled Domain</H1 +>Chapter 6. How to Act as a Backup Domain Controller in a Purely Samba Controlled Domain</H1 ><DIV CLASS="SECT1" ><H2 CLASS="SECT1" ><A -NAME="AEN1118" +NAME="AEN1274" ></A ->7.1. Prerequisite Reading</H2 +>6.1. Prerequisite Reading</H2 ><P >Before you continue reading in this chapter, please make sure that you are comfortable with configuring a Samba PDC @@ -6388,9 +6842,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN1122" +NAME="AEN1278" ></A ->7.2. Background</H2 +>6.2. Background</H2 ><P >What is a Domain Controller? It is a machine that is able to answer logon requests from workstations in a Windows NT Domain. Whenever a @@ -6433,9 +6887,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN1130" +NAME="AEN1286" ></A ->7.3. What qualifies a Domain Controller on the network?</H2 +>6.3. What qualifies a Domain Controller on the network?</H2 ><P >Every machine that is a Domain Controller for the domain SAMBA has to register the NetBIOS group name SAMBA#1c with the WINS server and/or @@ -6450,9 +6904,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN1133" +NAME="AEN1289" ></A ->7.3.1. How does a Workstation find its domain controller?</H3 +>6.3.1. How does a Workstation find its domain controller?</H3 ><P >A NT workstation in the domain SAMBA that wants a local user to be authenticated has to find the domain controller for SAMBA. It does @@ -6469,9 +6923,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN1136" +NAME="AEN1292" ></A ->7.3.2. When is the PDC needed?</H3 +>6.3.2. When is the PDC needed?</H3 ><P >Whenever a user wants to change his password, this has to be done on the PDC. To find the PDC, the workstation does a NetBIOS name query @@ -6485,15 +6939,19 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN1139" +NAME="AEN1295" ></A ->7.4. Can Samba be a Backup Domain Controller?</H2 +>6.4. Can Samba be a Backup Domain Controller to an NT PDC?</H2 ><P >With version 2.2, no. The native NT SAM replication protocols have not yet been fully implemented. The Samba Team is working on understanding and implementing the protocols, but this work has not been finished for version 2.2.</P ><P +>With version 3.0, the work on both the replication protocols and a +suitable storage mechanism has progressed, and some form of NT4 BDC +support is expected soon.</P +><P >Can I get the benefits of a BDC with Samba? Yes. The main reason for implementing a BDC is availability. If the PDC is a Samba machine, a second Samba machine can be set up to @@ -6504,9 +6962,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN1143" +NAME="AEN1300" ></A ->7.5. How do I set up a Samba BDC?</H2 +>6.5. How do I set up a Samba BDC?</H2 ><P >Several things have to be done:</P ><P @@ -6571,9 +7029,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN1160" +NAME="AEN1317" ></A ->7.5.1. How do I replicate the smbpasswd file?</H3 +>6.5.1. How do I replicate the smbpasswd file?</H3 ><P >Replication of the smbpasswd file is sensitive. It has to be done whenever changes to the SAM are made. Every user's password change is @@ -6587,6 +7045,21 @@ rsync. rsync can use ssh as a transport. ssh itself can be set up to accept *only* rsync transfer without requiring the user to type a password.</P ></DIV +><DIV +CLASS="SECT2" +><HR><H3 +CLASS="SECT2" +><A +NAME="AEN1321" +></A +>6.5.2. Can I do this all with LDAP?</H3 +><P +>The simple answer is YES. Samba's pdb_ldap code supports +binding to a replica LDAP server, and will also follow referrals and +rebind to the master if it ever needs to make a modification to the +database. (Normally BDCs are read only, so this will not occur +often).</P +></DIV ></DIV ></DIV ><DIV @@ -6595,15 +7068,14 @@ CLASS="CHAPTER" ><A NAME="ADS" ></A ->Chapter 8. Samba as a ADS domain member</H1 +>Chapter 7. Samba as a ADS domain member</H1 +><P +>This is a rough guide to setting up Samba 3.0 with kerberos authentication against a +Windows2000 KDC. </P +><P +>Pieces you need before you begin:</P ><P ->This is a VERY ROUGH guide to setting up the current (November 2001) -pre-alpha version of Samba 3.0 with kerberos authentication against a -Windows2000 KDC. The procedures listed here are likely to change as -the code develops.</P ><P ->Pieces you need before you begin: -<P ></P ><TABLE BORDER="0" @@ -6634,12 +7106,13 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN1178" +NAME="AEN1339" ></A ->8.1. Installing the required packages for Debian</H2 +>7.1. Installing the required packages for Debian</H2 +><P +>On Debian you need to install the following packages:</P +><P ><P ->On Debian you need to install the following packages: -<P ></P ><TABLE BORDER="0" @@ -6663,12 +7136,13 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN1184" +NAME="AEN1346" ></A ->8.2. Installing the required packages for RedHat</H2 +>7.2. Installing the required packages for RedHat</H2 +><P +>On RedHat this means you should have at least: </P +><P ><P ->On RedHat this means you should have at least: -<P ></P ><TABLE BORDER="0" @@ -6701,14 +7175,15 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN1193" +NAME="AEN1356" ></A ->8.3. Compile Samba</H2 +>7.3. Compile Samba</H2 ><P >If your kerberos libraries are in a non-standard location then remember to add the configure option --with-krb5=DIR.</P ><P ->After you run configure make sure that include/config.h contains +>After you run configure make sure that include/config.h it + generates contains lines like this:</P ><P ><PRE @@ -6727,17 +7202,27 @@ CLASS="PROGRAMLISTING" ><PRE CLASS="PROGRAMLISTING" > realm = YOUR.KERBEROS.REALM - ads server = your.kerberos.server security = ADS encrypt passwords = yes</PRE ></P ><P ->Strictly speaking, you can omit the realm name and you can use an IP - address for the ads server. In that case Samba will auto-detect these.</P +>In case samba can't figure out your ads server using your realm name, use the +<B +CLASS="COMMAND" +>ads server</B +> option in <TT +CLASS="FILENAME" +>smb.conf</TT +>: +<PRE +CLASS="PROGRAMLISTING" +> ads server = your.kerberos.server</PRE +></P ><P ->You do *not* need a smbpasswd file, although it won't do any harm - and if you have one then Samba will be able to fall back to normal - password security for older clients. I expect that the above +>You do *not* need a smbpasswd file, and older clients will + be authenticated as if "security = domain", although it won't do any harm + and allows you to have local users not in the domain. + I expect that the above required options will change soon when we get better active directory integration.</P ></DIV @@ -6746,15 +7231,15 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN1205" +NAME="AEN1371" ></A ->8.4. Setup your /etc/krb5.conf</H2 +>7.4. Setup your /etc/krb5.conf</H2 ><P >The minimal configuration for krb5.conf is:</P ><P ><PRE CLASS="PROGRAMLISTING" -> [realms] +>[realms] YOUR.KERBEROS.REALM = { kdc = your.kerberos.server }</PRE @@ -6778,20 +7263,18 @@ to join the realm.</P ><P >If all you want is kerberos support in smbclient then you can skip straight to step 5 now. Step 3 is only needed if you want kerberos -support in smbd.</P +support for smbd and winbindd.</P ></DIV ><DIV CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN1215" +NAME="AEN1381" ></A ->8.5. Create the computer account</H2 +>7.5. Create the computer account</H2 ><P ->Do a "kinit" as a user that has authority to change arbitrary -passwords on the KDC ("Administrator" is a good choice). Then as a -user that has write permission on the Samba private directory +>As a user that has write permission on the Samba private directory (usually root) run: <B CLASS="COMMAND" @@ -6802,9 +7285,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN1219" +NAME="AEN1385" ></A ->8.5.1. Possible errors</H3 +>7.5.1. Possible errors</H3 ><P ><P ></P @@ -6812,12 +7295,6 @@ NAME="AEN1219" CLASS="VARIABLELIST" ><DL ><DT ->"bash: kinit: command not found"</DT -><DD -><P ->kinit is in the krb5-workstation RPM on RedHat systems, and is in /usr/kerberos/bin, so it won't be in the path until you log in again (or open a new terminal)</P -></DD -><DT >"ADS support not compiled in"</DT ><DD ><P @@ -6833,9 +7310,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN1231" +NAME="AEN1393" ></A ->8.6. Test your server setup</H2 +>7.6. Test your server setup</H2 ><P >On a Windows 2000 client try <B CLASS="COMMAND" @@ -6853,9 +7330,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN1236" +NAME="AEN1398" ></A ->8.7. Testing with smbclient</H2 +>7.7. Testing with smbclient</H2 ><P >On your Samba server try to login to a Win2000 server or your Samba server using smbclient and kerberos. Use smbclient as usual, but @@ -6866,9 +7343,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN1239" +NAME="AEN1401" ></A ->8.8. Notes</H2 +>7.8. Notes</H2 ><P >You must change administrator password at least once after DC install, to create the right encoding types</P @@ -6883,21 +7360,21 @@ CLASS="CHAPTER" ><A NAME="DOMAIN-SECURITY" ></A ->Chapter 9. Samba as a NT4 domain member</H1 +>Chapter 8. Samba as a NT4 or Win2k domain member</H1 ><DIV CLASS="SECT1" ><H2 CLASS="SECT1" ><A -NAME="AEN1261" +NAME="AEN1423" ></A ->9.1. Joining an NT Domain with Samba 2.2</H2 +>8.1. Joining an NT Domain with Samba 3.0</H2 ><P ->Assume you have a Samba 2.x server with a NetBIOS name of +>Assume you have a Samba 3.0 server with a NetBIOS name of <TT CLASS="CONSTANT" >SERV1</TT -> and are joining an NT domain called +> and are joining an or Win2k NT domain called <TT CLASS="CONSTANT" >DOM</TT @@ -6915,107 +7392,7 @@ CLASS="CONSTANT" </TT >.</P ><P ->In order to join the domain, first stop all Samba daemons - and run the command:</P -><P -><TT -CLASS="PROMPT" ->root# </TT -><TT -CLASS="USERINPUT" -><B ->smbpasswd -j DOM -r DOMPDC - -U<TT -CLASS="REPLACEABLE" -><I ->Administrator%password</I -></TT -></B -></TT -></P -><P ->as we are joining the domain DOM and the PDC for that domain - (the only machine that has write access to the domain SAM database) - is DOMPDC. The <TT -CLASS="REPLACEABLE" -><I ->Administrator%password</I -></TT -> is - the login name and password for an account which has the necessary - privilege to add machines to the domain. If this is successful - you will see the message:</P -><P -><TT -CLASS="COMPUTEROUTPUT" ->smbpasswd: Joined domain DOM.</TT -> - </P -><P ->in your terminal window. See the <A -HREF="smbpasswd.8.html" -TARGET="_top" -> smbpasswd(8)</A -> man page for more details.</P -><P ->There is existing development code to join a domain - without having to create the machine trust account on the PDC - beforehand. This code will hopefully be available soon - in release branches as well.</P -><P ->This command goes through the machine account password - change protocol, then writes the new (random) machine account - password for this Samba server into a file in the same directory - in which an smbpasswd file would be stored - normally :</P -><P -><TT -CLASS="FILENAME" ->/usr/local/samba/private</TT -></P -><P ->In Samba 2.0.x, the filename looks like this:</P -><P -><TT -CLASS="FILENAME" -><TT -CLASS="REPLACEABLE" -><I -><NT DOMAIN NAME></I -></TT ->.<TT -CLASS="REPLACEABLE" -><I -><Samba - Server Name></I -></TT ->.mac</TT -></P -><P ->The <TT -CLASS="FILENAME" ->.mac</TT -> suffix stands for machine account - password file. So in our example above, the file would be called:</P -><P -><TT -CLASS="FILENAME" ->DOM.SERV1.mac</TT -></P -><P ->In Samba 2.2, this file has been replaced with a TDB - (Trivial Database) file named <TT -CLASS="FILENAME" ->secrets.tdb</TT ->. - </P -><P ->This file is created and owned by root and is not - readable by any other user. It is the key to the domain-level - security for your system, and should be treated as carefully - as a shadow password file.</P -><P ->Now, before restarting the Samba daemons you must - edit your <A +>Firstly, you must edit your <A HREF="smb.conf.5.html" TARGET="_top" ><TT @@ -7040,7 +7417,12 @@ CLASS="PARAMETER" ><B CLASS="COMMAND" >security = domain</B -></P +> or + <B +CLASS="COMMAND" +>security = ads</B +> depending on if the PDC is + NT4 or running Active Directory respectivly.</P ><P >Next change the <A HREF="smb.conf.5.html#WORKGROUP" @@ -7107,11 +7489,77 @@ CLASS="COMMAND" >password server = *</B ></P ><P ->This method, which was introduced in Samba 2.0.6, - allows Samba to use exactly the same mechanism that NT does. This +>This method, allows Samba to use exactly the same + mechanism that NT does. This method either broadcasts or uses a WINS database in order to find domain controllers to authenticate against.</P ><P +>In order to actually join the domain, you must run this + command:</P +><P +><TT +CLASS="PROMPT" +>root# </TT +><TT +CLASS="USERINPUT" +><B +>net join -S DOMPDC + -U<TT +CLASS="REPLACEABLE" +><I +>Administrator%password</I +></TT +></B +></TT +></P +><P +>as we are joining the domain DOM and the PDC for that domain + (the only machine that has write access to the domain SAM database) + is DOMPDC. The <TT +CLASS="REPLACEABLE" +><I +>Administrator%password</I +></TT +> is + the login name and password for an account which has the necessary + privilege to add machines to the domain. If this is successful + you will see the message:</P +><P +><TT +CLASS="COMPUTEROUTPUT" +>Joined domain DOM.</TT +> + or <TT +CLASS="COMPUTEROUTPUT" +>Joined 'SERV1' to realm 'MYREALM'</TT +> + </P +><P +>in your terminal window. See the <A +HREF="net.8.html" +TARGET="_top" +> net(8)</A +> man page for more details.</P +><P +>This process joins the server to thedomain + without having to create the machine trust account on the PDC + beforehand.</P +><P +>This command goes through the machine account password + change protocol, then writes the new (random) machine account + password for this Samba server into a file in the same directory + in which an smbpasswd file would be stored - normally :</P +><P +><TT +CLASS="FILENAME" +>/usr/local/samba/private/secrets.tdb</TT +></P +><P +>This file is created and owned by root and is not + readable by any other user. It is the key to the domain-level + security for your system, and should be treated as carefully + as a shadow password file.</P +><P >Finally, restart your Samba daemons and get ready for clients to begin using domain security!</P ></DIV @@ -7120,34 +7568,23 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN1325" +NAME="AEN1478" ></A ->9.2. Samba and Windows 2000 Domains</H2 +>8.2. Samba and Windows 2000 Domains</H2 ><P >Many people have asked regarding the state of Samba's ability to participate in a Windows 2000 Domain. Samba 3.0 is able to act as a member server of a Windows -2000 domain operating in mixed or native mode.</P -><P ->There is much confusion between the circumstances that require a "mixed" mode -Win2k DC and a when this host can be switched to "native" mode. A "mixed" mode -Win2k domain controller is only needed if Windows NT BDCs must exist in the same -domain. By default, a Win2k DC in "native" mode will still support -NetBIOS and NTLMv1 for authentication of legacy clients such as Windows 9x and -NT 4.0. Samba has the same requirements as a Windows NT 4.0 member server.</P -><P ->The steps for adding a Samba 2.2 host to a Win2k domain are the same as those -for adding a Samba server to a Windows NT 4.0 domain. The only exception is that -the "Server Manager" from NT 4 has been replaced by the "Active Directory Users and -Computers" MMC (Microsoft Management Console) plugin.</P +2000 domain operating in mixed or native mode. The steps above apply +to both NT4 and Windows 2000.</P ></DIV ><DIV CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN1330" +NAME="AEN1481" ></A ->9.3. Why is this better than security = server?</H2 +>8.3. Why is this better than security = server?</H2 ><P >Currently, domain security in Samba doesn't free you from having to create local Unix users to represent the users attaching @@ -7203,13 +7640,7 @@ CLASS="COMMAND" >And finally, acting in the same manner as an NT server authenticating to a PDC means that as part of the authentication reply, the Samba server gets the user identification information such - as the user SID, the list of NT groups the user belongs to, etc. All - this information will allow Samba to be extended in the future into - a mode the developers currently call appliance mode. In this mode, - no local Unix users will be necessary, and Samba will generate Unix - uids and gids from the information passed back from the PDC when a - user is authenticated, making a Samba server truly plug and play - in an NT domain environment. Watch for this code soon.</P + as the user SID, the list of NT groups the user belongs to, etc. </P ><P ><SPAN CLASS="emphasis" @@ -7235,7 +7666,7 @@ TARGET="_top" ><DIV CLASS="PART" ><A -NAME="AEN1346" +NAME="OPTIONAL" ></A ><DIV CLASS="TITLEPAGE" @@ -7245,7 +7676,7 @@ CLASS="TITLE" ><DIV CLASS="PARTINTRO" ><A -NAME="AEN1348" +NAME="AEN1499" ></A ><H1 >Introduction</H1 @@ -7261,51 +7692,51 @@ CLASS="TOC" >Table of Contents</B ></DT ><DT ->10. <A +>9. <A HREF="#INTEGRATE-MS-NETWORKS" >Integrating MS Windows networks with Samba</A ></DT ><DD ><DL ><DT ->10.1. <A -HREF="#AEN1362" +>9.1. <A +HREF="#AEN1513" >Agenda</A ></DT ><DT ->10.2. <A -HREF="#AEN1384" +>9.2. <A +HREF="#AEN1535" >Name Resolution in a pure Unix/Linux world</A ></DT ><DD ><DL ><DT ->10.2.1. <A -HREF="#AEN1400" +>9.2.1. <A +HREF="#AEN1551" ><TT CLASS="FILENAME" >/etc/hosts</TT ></A ></DT ><DT ->10.2.2. <A -HREF="#AEN1416" +>9.2.2. <A +HREF="#AEN1567" ><TT CLASS="FILENAME" >/etc/resolv.conf</TT ></A ></DT ><DT ->10.2.3. <A -HREF="#AEN1427" +>9.2.3. <A +HREF="#AEN1578" ><TT CLASS="FILENAME" >/etc/host.conf</TT ></A ></DT ><DT ->10.2.4. <A -HREF="#AEN1435" +>9.2.4. <A +HREF="#AEN1586" ><TT CLASS="FILENAME" >/etc/nsswitch.conf</TT @@ -7314,140 +7745,140 @@ CLASS="FILENAME" ></DL ></DD ><DT ->10.3. <A -HREF="#AEN1447" +>9.3. <A +HREF="#AEN1598" >Name resolution as used within MS Windows networking</A ></DT ><DD ><DL ><DT ->10.3.1. <A -HREF="#AEN1459" +>9.3.1. <A +HREF="#AEN1610" >The NetBIOS Name Cache</A ></DT ><DT ->10.3.2. <A -HREF="#AEN1464" +>9.3.2. <A +HREF="#AEN1615" >The LMHOSTS file</A ></DT ><DT ->10.3.3. <A -HREF="#AEN1472" +>9.3.3. <A +HREF="#AEN1623" >HOSTS file</A ></DT ><DT ->10.3.4. <A -HREF="#AEN1477" +>9.3.4. <A +HREF="#AEN1628" >DNS Lookup</A ></DT ><DT ->10.3.5. <A -HREF="#AEN1480" +>9.3.5. <A +HREF="#AEN1631" >WINS Lookup</A ></DT ></DL ></DD ><DT ->10.4. <A -HREF="#AEN1492" +>9.4. <A +HREF="#AEN1643" >How browsing functions and how to deploy stable and dependable browsing using Samba</A ></DT ><DT ->10.5. <A -HREF="#AEN1502" +>9.5. <A +HREF="#AEN1653" >MS Windows security options and how to configure Samba for seemless integration</A ></DT ><DD ><DL ><DT ->10.5.1. <A -HREF="#AEN1530" +>9.5.1. <A +HREF="#AEN1681" >Use MS Windows NT as an authentication server</A ></DT ><DT ->10.5.2. <A -HREF="#AEN1538" +>9.5.2. <A +HREF="#AEN1689" >Make Samba a member of an MS Windows NT security domain</A ></DT ><DT ->10.5.3. <A -HREF="#AEN1555" +>9.5.3. <A +HREF="#AEN1706" >Configure Samba as an authentication server</A ></DT ></DL ></DD ><DT ->10.6. <A -HREF="#AEN1572" +>9.6. <A +HREF="#AEN1723" >Conclusions</A ></DT ></DL ></DD ><DT ->11. <A +>10. <A HREF="#UNIX-PERMISSIONS" >UNIX Permission Bits and Windows NT Access Control Lists</A ></DT ><DD ><DL ><DT ->11.1. <A -HREF="#AEN1593" +>10.1. <A +HREF="#AEN1744" >Viewing and changing UNIX permissions using the NT security dialogs</A ></DT ><DT ->11.2. <A -HREF="#AEN1602" +>10.2. <A +HREF="#AEN1748" >How to view file security on a Samba share</A ></DT ><DT ->11.3. <A -HREF="#AEN1613" +>10.3. <A +HREF="#AEN1759" >Viewing file ownership</A ></DT ><DT ->11.4. <A -HREF="#AEN1633" +>10.4. <A +HREF="#AEN1779" >Viewing file or directory permissions</A ></DT ><DD ><DL ><DT ->11.4.1. <A -HREF="#AEN1648" +>10.4.1. <A +HREF="#AEN1794" >File Permissions</A ></DT ><DT ->11.4.2. <A -HREF="#AEN1662" +>10.4.2. <A +HREF="#AEN1808" >Directory Permissions</A ></DT ></DL ></DD ><DT ->11.5. <A -HREF="#AEN1669" +>10.5. <A +HREF="#AEN1815" >Modifying file or directory permissions</A ></DT ><DT ->11.6. <A -HREF="#AEN1691" +>10.6. <A +HREF="#AEN1837" >Interaction with the standard Samba create mask parameters</A ></DT ><DT ->11.7. <A -HREF="#AEN1755" +>10.7. <A +HREF="#AEN1901" >Interaction with the standard Samba file attribute mapping</A ></DT ></DL ></DD ><DT ->12. <A +>11. <A HREF="#PAM" >Configuring PAM for distributed but centrally managed authentication</A @@ -7455,39 +7886,39 @@ managed authentication</A ><DD ><DL ><DT ->12.1. <A -HREF="#AEN1776" +>11.1. <A +HREF="#AEN1922" >Samba and PAM</A ></DT ><DT ->12.2. <A -HREF="#AEN1820" +>11.2. <A +HREF="#AEN1966" >Distributed Authentication</A ></DT ><DT ->12.3. <A -HREF="#AEN1827" +>11.3. <A +HREF="#AEN1973" >PAM Configuration in smb.conf</A ></DT ></DL ></DD ><DT ->13. <A +>12. <A HREF="#MSDFS" >Hosting a Microsoft Distributed File System tree on Samba</A ></DT ><DD ><DL ><DT ->13.1. <A -HREF="#AEN1847" +>12.1. <A +HREF="#AEN1993" >Instructions</A ></DT ><DD ><DL ><DT ->13.1.1. <A -HREF="#AEN1882" +>12.1.1. <A +HREF="#AEN2028" >Notes</A ></DT ></DL @@ -7495,130 +7926,130 @@ HREF="#AEN1882" ></DL ></DD ><DT ->14. <A +>13. <A HREF="#PRINTING" >Printing Support</A ></DT ><DD ><DL ><DT ->14.1. <A -HREF="#AEN1908" +>13.1. <A +HREF="#AEN2054" >Introduction</A ></DT ><DT ->14.2. <A -HREF="#AEN1930" +>13.2. <A +HREF="#AEN2076" >Configuration</A ></DT ><DD ><DL ><DT ->14.2.1. <A -HREF="#AEN1938" +>13.2.1. <A +HREF="#AEN2084" >Creating [print$]</A ></DT ><DT ->14.2.2. <A -HREF="#AEN1973" +>13.2.2. <A +HREF="#AEN2119" >Setting Drivers for Existing Printers</A ></DT ><DT ->14.2.3. <A -HREF="#AEN1989" +>13.2.3. <A +HREF="#AEN2135" >Support a large number of printers</A ></DT ><DT ->14.2.4. <A -HREF="#AEN2000" +>13.2.4. <A +HREF="#AEN2146" >Adding New Printers via the Windows NT APW</A ></DT ><DT ->14.2.5. <A -HREF="#AEN2030" +>13.2.5. <A +HREF="#AEN2176" >Samba and Printer Ports</A ></DT ></DL ></DD ><DT ->14.3. <A -HREF="#AEN2038" +>13.3. <A +HREF="#AEN2184" >The Imprints Toolset</A ></DT ><DD ><DL ><DT ->14.3.1. <A -HREF="#AEN2042" +>13.3.1. <A +HREF="#AEN2188" >What is Imprints?</A ></DT ><DT ->14.3.2. <A -HREF="#AEN2052" +>13.3.2. <A +HREF="#AEN2198" >Creating Printer Driver Packages</A ></DT ><DT ->14.3.3. <A -HREF="#AEN2055" +>13.3.3. <A +HREF="#AEN2201" >The Imprints server</A ></DT ><DT ->14.3.4. <A -HREF="#AEN2059" +>13.3.4. <A +HREF="#AEN2205" >The Installation Client</A ></DT ></DL ></DD ><DT ->14.4. <A -HREF="#AEN2081" +>13.4. <A +HREF="#AEN2227" >Diagnosis</A ></DT ><DD ><DL ><DT ->14.4.1. <A -HREF="#AEN2083" +>13.4.1. <A +HREF="#AEN2229" >Introduction</A ></DT ><DT ->14.4.2. <A -HREF="#AEN2099" +>13.4.2. <A +HREF="#AEN2245" >Debugging printer problems</A ></DT ><DT ->14.4.3. <A -HREF="#AEN2108" +>13.4.3. <A +HREF="#AEN2254" >What printers do I have?</A ></DT ><DT ->14.4.4. <A -HREF="#AEN2116" +>13.4.4. <A +HREF="#AEN2262" >Setting up printcap and print servers</A ></DT ><DT ->14.4.5. <A -HREF="#AEN2144" +>13.4.5. <A +HREF="#AEN2290" >Job sent, no output</A ></DT ><DT ->14.4.6. <A -HREF="#AEN2155" +>13.4.6. <A +HREF="#AEN2301" >Job sent, strange output</A ></DT ><DT ->14.4.7. <A -HREF="#AEN2167" +>13.4.7. <A +HREF="#AEN2313" >Raw PostScript printed</A ></DT ><DT ->14.4.8. <A -HREF="#AEN2170" +>13.4.8. <A +HREF="#AEN2316" >Advanced Printing</A ></DT ><DT ->14.4.9. <A -HREF="#AEN2173" +>13.4.9. <A +HREF="#AEN2319" >Real debugging</A ></DT ></DL @@ -7626,273 +8057,268 @@ HREF="#AEN2173" ></DL ></DD ><DT ->15. <A -HREF="#SECURITYLEVELS" ->Security levels</A -></DT -><DD -><DL -><DT ->15.1. <A -HREF="#AEN2186" ->Introduction</A -></DT -><DT ->15.2. <A -HREF="#AEN2197" ->More complete description of security levels</A -></DT -></DL -></DD -><DT ->16. <A +>14. <A HREF="#WINBIND" >Unified Logons between Windows NT and UNIX using Winbind</A ></DT ><DD ><DL ><DT ->16.1. <A -HREF="#AEN2249" +>14.1. <A +HREF="#AEN2360" >Abstract</A ></DT ><DT ->16.2. <A -HREF="#AEN2253" +>14.2. <A +HREF="#AEN2364" >Introduction</A ></DT ><DT ->16.3. <A -HREF="#AEN2266" +>14.3. <A +HREF="#AEN2377" >What Winbind Provides</A ></DT ><DD ><DL ><DT ->16.3.1. <A -HREF="#AEN2273" +>14.3.1. <A +HREF="#AEN2384" >Target Uses</A ></DT ></DL ></DD ><DT ->16.4. <A -HREF="#AEN2277" +>14.4. <A +HREF="#AEN2388" >How Winbind Works</A ></DT ><DD ><DL ><DT ->16.4.1. <A -HREF="#AEN2282" +>14.4.1. <A +HREF="#AEN2393" >Microsoft Remote Procedure Calls</A ></DT ><DT ->16.4.2. <A -HREF="#AEN2286" +>14.4.2. <A +HREF="#AEN2397" +>Microsoft Active Directory Services</A +></DT +><DT +>14.4.3. <A +HREF="#AEN2400" >Name Service Switch</A ></DT ><DT ->16.4.3. <A -HREF="#AEN2302" +>14.4.4. <A +HREF="#AEN2416" >Pluggable Authentication Modules</A ></DT ><DT ->16.4.4. <A -HREF="#AEN2310" +>14.4.5. <A +HREF="#AEN2424" >User and Group ID Allocation</A ></DT ><DT ->16.4.5. <A -HREF="#AEN2314" +>14.4.6. <A +HREF="#AEN2428" >Result Caching</A ></DT ></DL ></DD ><DT ->16.5. <A -HREF="#AEN2317" +>14.5. <A +HREF="#AEN2431" >Installation and Configuration</A ></DT ><DD ><DL ><DT ->16.5.1. <A -HREF="#AEN2324" +>14.5.1. <A +HREF="#AEN2438" >Introduction</A ></DT ><DT ->16.5.2. <A -HREF="#AEN2337" +>14.5.2. <A +HREF="#AEN2451" >Requirements</A ></DT ><DT ->16.5.3. <A -HREF="#AEN2351" +>14.5.3. <A +HREF="#AEN2465" >Testing Things Out</A ></DT ></DL ></DD ><DT ->16.6. <A -HREF="#AEN2566" +>14.6. <A +HREF="#AEN2680" >Limitations</A ></DT ><DT ->16.7. <A -HREF="#AEN2576" +>14.7. <A +HREF="#AEN2690" >Conclusion</A ></DT ></DL ></DD ><DT ->17. <A -HREF="#PDB-MYSQL" ->Passdb MySQL plugin</A +>15. <A +HREF="#IMPROVED-BROWSING" +>Improved browsing in samba</A ></DT ><DD ><DL ><DT ->17.1. <A -HREF="#AEN2590" ->Building</A -></DT -><DT ->17.2. <A -HREF="#AEN2596" ->Configuring</A +>15.1. <A +HREF="#AEN2700" +>Overview of browsing</A ></DT ><DT ->17.3. <A -HREF="#AEN2611" ->Using plaintext passwords or encrypted password</A +>15.2. <A +HREF="#AEN2704" +>Browsing support in samba</A ></DT ><DT ->17.4. <A -HREF="#AEN2616" ->Getting non-column data from the table</A +>15.3. <A +HREF="#AEN2713" +>Problem resolution</A ></DT -></DL -></DD ><DT ->18. <A -HREF="#PDB-XML" ->Passdb XML plugin</A +>15.4. <A +HREF="#AEN2720" +>Browsing across subnets</A ></DT ><DD ><DL ><DT ->18.1. <A -HREF="#AEN2635" ->Building</A -></DT -><DT ->18.2. <A -HREF="#AEN2641" ->Usage</A +>15.4.1. <A +HREF="#AEN2725" +>How does cross subnet browsing work ?</A ></DT ></DL ></DD ><DT ->19. <A -HREF="#SAMBA-LDAP-HOWTO" ->Storing Samba's User/Machine Account information in an LDAP Directory</A +>15.5. <A +HREF="#AEN2760" +>Setting up a WINS server</A ></DT -><DD -><DL ><DT ->19.1. <A -HREF="#AEN2664" ->Purpose</A +>15.6. <A +HREF="#AEN2779" +>Setting up Browsing in a WORKGROUP</A ></DT ><DT ->19.2. <A -HREF="#AEN2684" ->Introduction</A +>15.7. <A +HREF="#AEN2797" +>Setting up Browsing in a DOMAIN</A ></DT ><DT ->19.3. <A -HREF="#AEN2713" ->Supported LDAP Servers</A +>15.8. <A +HREF="#AEN2807" +>Forcing samba to be the master</A ></DT ><DT ->19.4. <A -HREF="#AEN2718" ->Schema and Relationship to the RFC 2307 posixAccount</A +>15.9. <A +HREF="#AEN2816" +>Making samba the domain master</A ></DT ><DT ->19.5. <A -HREF="#AEN2730" ->Configuring Samba with LDAP</A +>15.10. <A +HREF="#AEN2834" +>Note about broadcast addresses</A +></DT +><DT +>15.11. <A +HREF="#AEN2837" +>Multiple interfaces</A +></DT +></DL +></DD +><DT +>16. <A +HREF="#VFS" +>Stackable VFS modules</A ></DT ><DD ><DL ><DT ->19.5.1. <A -HREF="#AEN2732" ->OpenLDAP configuration</A +>16.1. <A +HREF="#AEN2855" +>Introduction and configuration</A ></DT ><DT ->19.5.2. <A -HREF="#AEN2749" ->Configuring Samba</A +>16.2. <A +HREF="#AEN2864" +>Included modules</A ></DT -></DL -></DD +><DD +><DL ><DT ->19.6. <A -HREF="#AEN2777" ->Accounts and Groups management</A +>16.2.1. <A +HREF="#AEN2866" +>audit</A ></DT ><DT ->19.7. <A -HREF="#AEN2782" ->Security and sambaAccount</A +>16.2.2. <A +HREF="#AEN2874" +>recycle</A ></DT ><DT ->19.8. <A -HREF="#AEN2802" ->LDAP specials attributes for sambaAccounts</A +>16.2.3. <A +HREF="#AEN2911" +>netatalk</A ></DT +></DL +></DD ><DT ->19.9. <A -HREF="#AEN2872" ->Example LDIF Entries for a sambaAccount</A +>16.3. <A +HREF="#AEN2918" +>VFS modules available elsewhere</A ></DT +><DD +><DL ><DT ->19.10. <A -HREF="#AEN2880" ->Comments</A +>16.3.1. <A +HREF="#AEN2922" +>DatabaseFS</A +></DT +><DT +>16.3.2. <A +HREF="#AEN2930" +>vscan</A ></DT ></DL ></DD +></DL +></DD ><DT ->20. <A +>17. <A HREF="#CVS-ACCESS" ->HOWTO Access Samba source code via CVS</A +>Access Samba source code via CVS</A ></DT ><DD ><DL ><DT ->20.1. <A -HREF="#AEN2891" +>17.1. <A +HREF="#AEN2942" >Introduction</A ></DT ><DT ->20.2. <A -HREF="#AEN2896" +>17.2. <A +HREF="#AEN2947" >CVS Access to samba.org</A ></DT ><DD ><DL ><DT ->20.2.1. <A -HREF="#AEN2899" +>17.2.1. <A +HREF="#AEN2950" >Access via CVSweb</A ></DT ><DT ->20.2.2. <A -HREF="#AEN2904" +>17.2.2. <A +HREF="#AEN2955" >Access via cvs</A ></DT ></DL @@ -7900,120 +8326,114 @@ HREF="#AEN2904" ></DL ></DD ><DT ->21. <A +>18. <A HREF="#GROUPMAPPING" >Group mapping HOWTO</A ></DT ><DT ->22. <A +>19. <A HREF="#SPEED" >Samba performance issues</A ></DT ><DD ><DL ><DT ->22.1. <A -HREF="#AEN2982" +>19.1. <A +HREF="#AEN3033" >Comparisons</A ></DT ><DT ->22.2. <A -HREF="#AEN2988" ->Oplocks</A -></DT -><DD -><DL -><DT ->22.2.1. <A -HREF="#AEN2990" ->Overview</A -></DT -><DT ->22.2.2. <A -HREF="#AEN2998" ->Level2 Oplocks</A +>19.2. <A +HREF="#AEN3039" +>Socket options</A ></DT ><DT ->22.2.3. <A -HREF="#AEN3004" ->Old 'fake oplocks' option - deprecated</A +>19.3. <A +HREF="#AEN3046" +>Read size</A ></DT -></DL -></DD ><DT ->22.3. <A -HREF="#AEN3008" ->Socket options</A +>19.4. <A +HREF="#AEN3051" +>Max xmit</A ></DT ><DT ->22.4. <A -HREF="#AEN3015" ->Read size</A +>19.5. <A +HREF="#AEN3056" +>Log level</A ></DT ><DT ->22.5. <A -HREF="#AEN3020" ->Max xmit</A +>19.6. <A +HREF="#AEN3059" +>Read raw</A ></DT ><DT ->22.6. <A -HREF="#AEN3025" ->Locking</A +>19.7. <A +HREF="#AEN3064" +>Write raw</A ></DT ><DT ->22.7. <A -HREF="#AEN3029" ->Share modes</A +>19.8. <A +HREF="#AEN3068" +>Slow Clients</A ></DT ><DT ->22.8. <A -HREF="#AEN3034" ->Log level</A +>19.9. <A +HREF="#AEN3072" +>Slow Logins</A ></DT ><DT ->22.9. <A -HREF="#AEN3037" ->Wide lines</A +>19.10. <A +HREF="#AEN3075" +>Client tuning</A ></DT +></DL +></DD ><DT ->22.10. <A -HREF="#AEN3040" ->Read raw</A +>20. <A +HREF="#GROUPPROFILES" +>Creating Group Profiles</A ></DT +><DD +><DL ><DT ->22.11. <A -HREF="#AEN3045" ->Write raw</A +>20.1. <A +HREF="#AEN3123" +>Windows '9x</A ></DT ><DT ->22.12. <A -HREF="#AEN3049" ->Read prediction</A +>20.2. <A +HREF="#AEN3132" +>Windows NT 4</A ></DT +><DD +><DL ><DT ->22.13. <A -HREF="#AEN3056" ->Memory mapping</A +>20.2.1. <A +HREF="#AEN3155" +>Side bar Notes</A ></DT ><DT ->22.14. <A -HREF="#AEN3061" ->Slow Clients</A +>20.2.2. <A +HREF="#AEN3159" +>Mandatory profiles</A ></DT ><DT ->22.15. <A -HREF="#AEN3065" ->Slow Logins</A +>20.2.3. <A +HREF="#AEN3162" +>moveuser.exe</A ></DT ><DT ->22.16. <A -HREF="#AEN3068" ->Client tuning</A +>20.2.4. <A +HREF="#AEN3165" +>Get SID</A ></DT +></DL +></DD ><DT ->22.17. <A -HREF="#AEN3100" ->My Results</A +>20.3. <A +HREF="#AEN3170" +>Windows 2000/XP</A ></DT ></DL ></DD @@ -8026,15 +8446,15 @@ CLASS="CHAPTER" ><A NAME="INTEGRATE-MS-NETWORKS" ></A ->Chapter 10. Integrating MS Windows networks with Samba</H1 +>Chapter 9. Integrating MS Windows networks with Samba</H1 ><DIV CLASS="SECT1" ><H2 CLASS="SECT1" ><A -NAME="AEN1362" +NAME="AEN1513" ></A ->10.1. Agenda</H2 +>9.1. Agenda</H2 ><P >To identify the key functional mechanisms of MS Windows networking to enable the deployment of Samba as a means of extending and/or @@ -8099,9 +8519,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN1384" +NAME="AEN1535" ></A ->10.2. Name Resolution in a pure Unix/Linux world</H2 +>9.2. Name Resolution in a pure Unix/Linux world</H2 ><P >The key configuration files covered in this section are:</P ><P @@ -8141,9 +8561,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN1400" +NAME="AEN1551" ></A ->10.2.1. <TT +>9.2.1. <TT CLASS="FILENAME" >/etc/hosts</TT ></H3 @@ -8222,9 +8642,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN1416" +NAME="AEN1567" ></A ->10.2.2. <TT +>9.2.2. <TT CLASS="FILENAME" >/etc/resolv.conf</TT ></H3 @@ -8260,9 +8680,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN1427" +NAME="AEN1578" ></A ->10.2.3. <TT +>9.2.3. <TT CLASS="FILENAME" >/etc/host.conf</TT ></H3 @@ -8289,9 +8709,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN1435" +NAME="AEN1586" ></A ->10.2.4. <TT +>9.2.4. <TT CLASS="FILENAME" >/etc/nsswitch.conf</TT ></H3 @@ -8358,9 +8778,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN1447" +NAME="AEN1598" ></A ->10.3. Name resolution as used within MS Windows networking</H2 +>9.3. Name resolution as used within MS Windows networking</H2 ><P >MS Windows networking is predicated about the name each machine is given. This name is known variously (and inconsistently) as @@ -8380,16 +8800,16 @@ the client/server.</P ><PRE CLASS="PROGRAMLISTING" > Unique NetBIOS Names: - MACHINENAME<00> = Server Service is running on MACHINENAME - MACHINENAME<03> = Generic Machine Name (NetBIOS name) - MACHINENAME<20> = LanMan Server service is running on MACHINENAME - WORKGROUP<1b> = Domain Master Browser + MACHINENAME<00> = Server Service is running on MACHINENAME + MACHINENAME<03> = Generic Machine Name (NetBIOS name) + MACHINENAME<20> = LanMan Server service is running on MACHINENAME + WORKGROUP<1b> = Domain Master Browser Group Names: - WORKGROUP<03> = Generic Name registered by all members of WORKGROUP - WORKGROUP<1c> = Domain Controllers / Netlogon Servers - WORKGROUP<1d> = Local Master Browsers - WORKGROUP<1e> = Internet Name Resolvers</PRE + WORKGROUP<03> = Generic Name registered by all members of WORKGROUP + WORKGROUP<1c> = Domain Controllers / Netlogon Servers + WORKGROUP<1d> = Local Master Browsers + WORKGROUP<1e> = Internet Name Resolvers</PRE ></P ><P >It should be noted that all NetBIOS machines register their own @@ -8408,7 +8828,7 @@ be needed. An example of this is what happens when an MS Windows client wants to locate a domain logon server. It find this service and the IP address of a server that provides it by performing a lookup (via a NetBIOS broadcast) for enumeration of all machines that have -registered the name type *<1c>. A logon request is then sent to each +registered the name type *<1c>. A logon request is then sent to each IP address that is returned in the enumerated list of IP addresses. Which ever machine first replies then ends up providing the logon services.</P ><P @@ -8443,9 +8863,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN1459" +NAME="AEN1610" ></A ->10.3.1. The NetBIOS Name Cache</H3 +>9.3.1. The NetBIOS Name Cache</H3 ><P >All MS Windows machines employ an in memory buffer in which is stored the NetBIOS names and IP addresses for all external @@ -8470,9 +8890,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN1464" +NAME="AEN1615" ></A ->10.3.2. The LMHOSTS file</H3 +>9.3.2. The LMHOSTS file</H3 ><P >This file is usually located in MS Windows NT 4.0 or 2000 in <TT @@ -8573,9 +8993,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN1472" +NAME="AEN1623" ></A ->10.3.3. HOSTS file</H3 +>9.3.3. HOSTS file</H3 ><P >This file is usually located in MS Windows NT 4.0 or 2000 in <TT @@ -8595,9 +9015,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN1477" +NAME="AEN1628" ></A ->10.3.4. DNS Lookup</H3 +>9.3.4. DNS Lookup</H3 ><P >This capability is configured in the TCP/IP setup area in the network configuration facility. If enabled an elaborate name resolution sequence @@ -8615,9 +9035,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN1480" +NAME="AEN1631" ></A ->10.3.5. WINS Lookup</H3 +>9.3.5. WINS Lookup</H3 ><P >A WINS (Windows Internet Name Server) service is the equivaent of the rfc1001/1002 specified NBNS (NetBIOS Name Server). A WINS server stores @@ -8658,9 +9078,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN1492" +NAME="AEN1643" ></A ->10.4. How browsing functions and how to deploy stable and +>9.4. How browsing functions and how to deploy stable and dependable browsing using Samba</H2 ><P >As stated above, MS Windows machines register their NetBIOS names @@ -8725,9 +9145,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN1502" +NAME="AEN1653" ></A ->10.5. MS Windows security options and how to configure +>9.5. MS Windows security options and how to configure Samba for seemless integration</H2 ><P >MS Windows clients may use encrypted passwords as part of a @@ -8862,9 +9282,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN1530" +NAME="AEN1681" ></A ->10.5.1. Use MS Windows NT as an authentication server</H3 +>9.5.1. Use MS Windows NT as an authentication server</H3 ><P >This method involves the additions of the following parameters in the smb.conf file:</P @@ -8898,9 +9318,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN1538" +NAME="AEN1689" ></A ->10.5.2. Make Samba a member of an MS Windows NT security domain</H3 +>9.5.2. Make Samba a member of an MS Windows NT security domain</H3 ><P >This method involves additon of the following paramters in the smb.conf file:</P ><P @@ -8961,9 +9381,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN1555" +NAME="AEN1706" ></A ->10.5.3. Configure Samba as an authentication server</H3 +>9.5.3. Configure Samba as an authentication server</H3 ><P >This mode of authentication demands that there be on the Unix/Linux system both a Unix style account as well as an @@ -8998,9 +9418,9 @@ CLASS="SECT3" ><HR><H4 CLASS="SECT3" ><A -NAME="AEN1562" +NAME="AEN1713" ></A ->10.5.3.1. Users</H4 +>9.5.3.1. Users</H4 ><P >A user account that may provide a home directory should be created. The following Linux system commands are typical of @@ -9021,9 +9441,9 @@ CLASS="SECT3" ><HR><H4 CLASS="SECT3" ><A -NAME="AEN1567" +NAME="AEN1718" ></A ->10.5.3.2. MS Windows NT Machine Accounts</H4 +>9.5.3.2. MS Windows NT Machine Accounts</H4 ><P >These are required only when Samba is used as a domain controller. Refer to the Samba-PDC-HOWTO for more details.</P @@ -9042,9 +9462,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN1572" +NAME="AEN1723" ></A ->10.6. Conclusions</H2 +>9.6. Conclusions</H2 ><P >Samba provides a flexible means to operate as...</P ><P @@ -9080,15 +9500,15 @@ CLASS="CHAPTER" ><A NAME="UNIX-PERMISSIONS" ></A ->Chapter 11. UNIX Permission Bits and Windows NT Access Control Lists</H1 +>Chapter 10. UNIX Permission Bits and Windows NT Access Control Lists</H1 ><DIV CLASS="SECT1" ><H2 CLASS="SECT1" ><A -NAME="AEN1593" +NAME="AEN1744" ></A ->11.1. Viewing and changing UNIX permissions using the NT +>10.1. Viewing and changing UNIX permissions using the NT security dialogs</H2 ><P >New in the Samba 2.0.4 release is the ability for Windows @@ -9099,35 +9519,15 @@ NAME="AEN1593" the security of the UNIX host Samba is running on, and still obeys all the file permission rules that a Samba administrator can set.</P -><P ->In Samba 2.0.4 and above the default value of the - parameter <A -HREF="smb.conf.5.html#NTACLSUPPORT" -TARGET="_top" -><TT -CLASS="PARAMETER" -><I -> nt acl support</I -></TT -></A -> has been changed from - <TT -CLASS="CONSTANT" ->false</TT -> to <TT -CLASS="CONSTANT" ->true</TT ->, so - manipulation of permissions is turned on by default.</P ></DIV ><DIV CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN1602" +NAME="AEN1748" ></A ->11.2. How to view file security on a Samba share</H2 +>10.2. How to view file security on a Samba share</H2 ><P >From an NT 4.0 client, single-click with the right mouse button on any file or directory in a Samba mounted @@ -9195,9 +9595,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN1613" +NAME="AEN1759" ></A ->11.3. Viewing file ownership</H2 +>10.3. Viewing file ownership</H2 ><P >Clicking on the <B CLASS="COMMAND" @@ -9289,9 +9689,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN1633" +NAME="AEN1779" ></A ->11.4. Viewing file or directory permissions</H2 +>10.4. Viewing file or directory permissions</H2 ><P >The third button is the <B CLASS="COMMAND" @@ -9351,9 +9751,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN1648" +NAME="AEN1794" ></A ->11.4.1. File Permissions</H3 +>10.4.1. File Permissions</H3 ><P >The standard UNIX user/group/world triple and the corresponding "read", "write", "execute" permissions @@ -9413,9 +9813,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN1662" +NAME="AEN1808" ></A ->11.4.2. Directory Permissions</H3 +>10.4.2. Directory Permissions</H3 ><P >Directories on an NT NTFS file system have two different sets of permissions. The first set of permissions @@ -9445,9 +9845,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN1669" +NAME="AEN1815" ></A ->11.5. Modifying file or directory permissions</H2 +>10.5. Modifying file or directory permissions</H2 ><P >Modifying file and directory permissions is as simple as changing the displayed permissions in the dialog box, and @@ -9543,9 +9943,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN1691" +NAME="AEN1837" ></A ->11.6. Interaction with the standard Samba create mask +>10.6. Interaction with the standard Samba create mask parameters</H2 ><P >Note that with Samba 2.0.5 there are four new parameters @@ -9820,9 +10220,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN1755" +NAME="AEN1901" ></A ->11.7. Interaction with the standard Samba file attribute +>10.7. Interaction with the standard Samba file attribute mapping</H2 ><P >Samba maps some of the DOS attribute bits (such as "read @@ -9869,16 +10269,16 @@ CLASS="CHAPTER" ><A NAME="PAM" ></A ->Chapter 12. Configuring PAM for distributed but centrally +>Chapter 11. Configuring PAM for distributed but centrally managed authentication</H1 ><DIV CLASS="SECT1" ><H2 CLASS="SECT1" ><A -NAME="AEN1776" +NAME="AEN1922" ></A ->12.1. Samba and PAM</H2 +>11.1. Samba and PAM</H2 ><P >A number of Unix systems (eg: Sun Solaris), as well as the xxxxBSD family and Linux, now utilize the Pluggable Authentication @@ -10090,9 +10490,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN1820" +NAME="AEN1966" ></A ->12.2. Distributed Authentication</H2 +>11.2. Distributed Authentication</H2 ><P >The astute administrator will realize from this that the combination of <TT @@ -10123,9 +10523,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN1827" +NAME="AEN1973" ></A ->12.3. PAM Configuration in smb.conf</H2 +>11.3. PAM Configuration in smb.conf</H2 ><P >There is an option in smb.conf called <A HREF="smb.conf.5.html#OBEYPAMRESTRICTIONS" @@ -10165,15 +10565,15 @@ CLASS="CHAPTER" ><A NAME="MSDFS" ></A ->Chapter 13. Hosting a Microsoft Distributed File System tree on Samba</H1 +>Chapter 12. Hosting a Microsoft Distributed File System tree on Samba</H1 ><DIV CLASS="SECT1" ><H2 CLASS="SECT1" ><A -NAME="AEN1847" +NAME="AEN1993" ></A ->13.1. Instructions</H2 +>12.1. Instructions</H2 ><P >The Distributed File System (or Dfs) provides a means of separating the logical view of files and directories that users @@ -10319,9 +10719,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN1882" +NAME="AEN2028" ></A ->13.1.1. Notes</H3 +>12.1.1. Notes</H3 ><P ></P ><UL @@ -10354,15 +10754,15 @@ CLASS="CHAPTER" ><A NAME="PRINTING" ></A ->Chapter 14. Printing Support</H1 +>Chapter 13. Printing Support</H1 ><DIV CLASS="SECT1" ><H2 CLASS="SECT1" ><A -NAME="AEN1908" +NAME="AEN2054" ></A ->14.1. Introduction</H2 +>13.1. Introduction</H2 ><P >Beginning with the 2.2.0 release, Samba supports the native Windows NT printing mechanisms implemented via @@ -10443,9 +10843,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN1930" +NAME="AEN2076" ></A ->14.2. Configuration</H2 +>13.2. Configuration</H2 ><DIV CLASS="WARNING" ><P @@ -10460,7 +10860,7 @@ WIDTH="25" ALIGN="CENTER" VALIGN="TOP" ><IMG -SRC="/docbook-dsssl/warning.gif" +SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/warning.gif" HSPACE="5" ALT="Warning"></TD ><TH @@ -10509,9 +10909,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN1938" +NAME="AEN2084" ></A ->14.2.1. Creating [print$]</H3 +>13.2.1. Creating [print$]</H3 ><P >In order to support the uploading of printer driver files, you must first configure a file share named [print$]. @@ -10590,7 +10990,7 @@ WIDTH="25" ALIGN="CENTER" VALIGN="TOP" ><IMG -SRC="/docbook-dsssl/note.gif" +SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif" HSPACE="5" ALT="Note"></TD ><TH @@ -10661,7 +11061,7 @@ WIDTH="25" ALIGN="CENTER" VALIGN="TOP" ><IMG -SRC="/docbook-dsssl/warning.gif" +SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/warning.gif" HSPACE="5" ALT="Warning"></TD ><TH @@ -10732,9 +11132,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN1973" +NAME="AEN2119" ></A ->14.2.2. Setting Drivers for Existing Printers</H3 +>13.2.2. Setting Drivers for Existing Printers</H3 ><P >The initial listing of printers in the Samba host's Printers folder will have no real printer driver assigned @@ -10804,9 +11204,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN1989" +NAME="AEN2135" ></A ->14.2.3. Support a large number of printers</H3 +>13.2.3. Support a large number of printers</H3 ><P >One issue that has arisen during the development phase of Samba 2.2 is the need to support driver downloads for @@ -10870,9 +11270,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN2000" +NAME="AEN2146" ></A ->14.2.4. Adding New Printers via the Windows NT APW</H3 +>13.2.4. Adding New Printers via the Windows NT APW</H3 ><P >By default, Samba offers all printer shares defined in <TT CLASS="FILENAME" @@ -11013,8 +11413,8 @@ echo " :sd=/var/spool/lpd/$2:\\" >> $PRINTCAP echo " :mx=0:ml=0:sh:\\" >> $PRINTCAP echo " :lp=/usr/local/samba/var/print/$5.prn:" >> $PRINTCAP -touch "/usr/local/samba/var/print/$5.prn" >> /tmp/printadd.$$ 2>&1 -chown $LP "/usr/local/samba/var/print/$5.prn" >> /tmp/printadd.$$ 2>&1 +touch "/usr/local/samba/var/print/$5.prn" >> /tmp/printadd.$$ 2>&1 +chown $LP "/usr/local/samba/var/print/$5.prn" >> /tmp/printadd.$$ 2>&1 mkdir /var/spool/lpd/$2 chmod 700 /var/spool/lpd/$2 @@ -11039,9 +11439,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN2030" +NAME="AEN2176" ></A ->14.2.5. Samba and Printer Ports</H3 +>13.2.5. Samba and Printer Ports</H3 ><P >Windows NT/2000 print servers associate a port with each printer. These normally take the form of LPT1:, COM1:, FILE:, etc... Samba must also support the @@ -11076,9 +11476,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN2038" +NAME="AEN2184" ></A ->14.3. The Imprints Toolset</H2 +>13.3. The Imprints Toolset</H2 ><P >The Imprints tool set provides a UNIX equivalent of the Windows NT Add Printer Wizard. For complete information, please @@ -11094,9 +11494,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN2042" +NAME="AEN2188" ></A ->14.3.1. What is Imprints?</H3 +>13.3.1. What is Imprints?</H3 ><P >Imprints is a collection of tools for supporting the goals of</P @@ -11126,9 +11526,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN2052" +NAME="AEN2198" ></A ->14.3.2. Creating Printer Driver Packages</H3 +>13.3.2. Creating Printer Driver Packages</H3 ><P >The process of creating printer driver packages is beyond the scope of this document (refer to Imprints.txt also included @@ -11142,9 +11542,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN2055" +NAME="AEN2201" ></A ->14.3.3. The Imprints server</H3 +>13.3.3. The Imprints server</H3 ><P >The Imprints server is really a database server that may be queried via standard HTTP mechanisms. Each printer @@ -11166,9 +11566,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN2059" +NAME="AEN2205" ></A ->14.3.4. The Installation Client</H3 +>13.3.4. The Installation Client</H3 ><P >More information regarding the Imprints installation client is available in the <TT @@ -11260,17 +11660,17 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN2081" +NAME="AEN2227" ></A ->14.4. Diagnosis</H2 +>13.4. Diagnosis</H2 ><DIV CLASS="SECT2" ><H3 CLASS="SECT2" ><A -NAME="AEN2083" +NAME="AEN2229" ></A ->14.4.1. Introduction</H3 +>13.4.1. Introduction</H3 ><P >This is a short description of how to debug printing problems with Samba. This describes how to debug problems with printing from a SMB @@ -11343,9 +11743,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN2099" +NAME="AEN2245" ></A ->14.4.2. Debugging printer problems</H3 +>13.4.2. Debugging printer problems</H3 ><P >One way to debug printing problems is to start by replacing these command with shell scripts that record the arguments and the contents @@ -11361,7 +11761,7 @@ CLASS="PROGRAMLISTING" /usr/bin/id -p >/tmp/tmp.print # we run the command and save the error messages # replace the command with the one appropriate for your system - /usr/bin/lpr -r -P$1 $2 2>>&/tmp/tmp.print</PRE + /usr/bin/lpr -r -P$1 $2 2>>&/tmp/tmp.print</PRE ></P ><P >Then you print a file and try removing it. You may find that the @@ -11400,9 +11800,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN2108" +NAME="AEN2254" ></A ->14.4.3. What printers do I have?</H3 +>13.4.3. What printers do I have?</H3 ><P >You can use the 'testprns' program to check to see if the printer name you are using is recognized by Samba. For example, you can @@ -11429,9 +11829,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN2116" +NAME="AEN2262" ></A ->14.4.4. Setting up printcap and print servers</H3 +>13.4.4. Setting up printcap and print servers</H3 ><P >You may need to set up some printcaps for your Samba system to use. It is strongly recommended that you use the facilities provided by @@ -11513,9 +11913,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN2144" +NAME="AEN2290" ></A ->14.4.5. Job sent, no output</H3 +>13.4.5. Job sent, no output</H3 ><P >This is the most frustrating part of printing. You may have sent the job, verified that the job was forwarded, set up a wrapper around @@ -11558,9 +11958,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN2155" +NAME="AEN2301" ></A ->14.4.6. Job sent, strange output</H3 +>13.4.6. Job sent, strange output</H3 ><P >Once you have the job printing, you can then start worrying about making it print nicely.</P @@ -11604,9 +12004,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN2167" +NAME="AEN2313" ></A ->14.4.7. Raw PostScript printed</H3 +>13.4.7. Raw PostScript printed</H3 ><P >This is a problem that is usually caused by either the print spooling system putting information at the start of the print job that makes @@ -11619,9 +12019,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN2170" +NAME="AEN2316" ></A ->14.4.8. Advanced Printing</H3 +>13.4.8. Advanced Printing</H3 ><P >Note that you can do some pretty magic things by using your imagination with the "print command" option and some shell scripts. @@ -11635,9 +12035,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN2173" +NAME="AEN2319" ></A ->14.4.9. Real debugging</H3 +>13.4.9. Real debugging</H3 ><P >If the above debug tips don't help, then maybe you need to bring in the bug guns, system tracing. See Tracing.txt in this directory.</P @@ -11648,165 +12048,17 @@ the bug guns, system tracing. See Tracing.txt in this directory.</P CLASS="CHAPTER" ><HR><H1 ><A -NAME="SECURITYLEVELS" -></A ->Chapter 15. Security levels</H1 -><DIV -CLASS="SECT1" -><H2 -CLASS="SECT1" -><A -NAME="AEN2186" -></A ->15.1. Introduction</H2 -><P ->Samba supports the following options to the global smb.conf parameter</P -><P -><PRE -CLASS="PROGRAMLISTING" ->[global] -<A -HREF="smb.conf.5.html#SECURITY" -TARGET="_top" -><TT -CLASS="PARAMETER" -><I ->security</I -></TT -></A -> = [share|user(default)|server|domain|ads]</PRE -></P -><P ->Please refer to the smb.conf man page for usage information and to the document -<A -HREF="DOMAIN_MEMBER.html" -TARGET="_top" ->DOMAIN_MEMBER.html</A -> for further background details -on domain mode security. The Windows 2000 Kerberos domain security model -(security = ads) is described in the <A -HREF="ADS-HOWTO.html" -TARGET="_top" ->ADS-HOWTO.html</A ->.</P -><P ->Of the above, "security = server" means that Samba reports to clients that -it is running in "user mode" but actually passes off all authentication -requests to another "user mode" server. This requires an additional -parameter "password server =" that points to the real authentication server. -That real authentication server can be another Samba server or can be a -Windows NT server, the later natively capable of encrypted password support.</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN2197" -></A ->15.2. More complete description of security levels</H2 -><P ->A SMB server tells the client at startup what "security level" it is -running. There are two options "share level" and "user level". Which -of these two the client receives affects the way the client then tries -to authenticate itself. It does not directly affect (to any great -extent) the way the Samba server does security. I know this is -strange, but it fits in with the client/server approach of SMB. In SMB -everything is initiated and controlled by the client, and the server -can only tell the client what is available and whether an action is -allowed. </P -><P ->I'll describe user level security first, as its simpler. In user level -security the client will send a "session setup" command directly after -the protocol negotiation. This contains a username and password. The -server can either accept or reject that username/password -combination. Note that at this stage the server has no idea what -share the client will eventually try to connect to, so it can't base -the "accept/reject" on anything other than:</P -><P -></P -><OL -TYPE="1" -><LI -><P ->the username/password</P -></LI -><LI -><P ->the machine that the client is coming from</P -></LI -></OL -><P ->If the server accepts the username/password then the client expects to -be able to mount any share (using a "tree connection") without -specifying a password. It expects that all access rights will be as -the username/password specified in the "session setup". </P -><P ->It is also possible for a client to send multiple "session setup" -requests. When the server responds it gives the client a "uid" to use -as an authentication tag for that username/password. The client can -maintain multiple authentication contexts in this way (WinDD is an -example of an application that does this)</P -><P ->Ok, now for share level security. In share level security the client -authenticates itself separately for each share. It will send a -password along with each "tree connection" (share mount). It does not -explicitly send a username with this operation. The client is -expecting 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. It is never explicitly sent the -username. 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 that is authenticated, not a "share/password".</P -><P ->Many clients send a "session setup" even if the server is in share -level security. They normally send a valid username but no -password. Samba records this username in a list of "possible -usernames". When the client then does a "tree connection" it also adds -to this list the name of the share they try to connect to (useful for -home directories) and any users listed in the "user =" smb.conf -line. The password is then checked in turn against these "possible -usernames". If a match is found then the client is authenticated as -that user.</P -><P ->Finally "server level" security. In server level security the samba -server reports to the client that it is in user level security. The -client then does a "session setup" as described earlier. The samba -server takes the username/password that the client sends and attempts -to login to the "password server" by sending exactly the same -username/password that it got from the client. If that server is in -user level security and accepts the password then samba accepts the -clients connection. This allows the samba server to use another SMB -server as the "password server". </P -><P ->You should also note that at the very start of all this, where the -server tells the client what security level it is in, it also tells -the client if it supports encryption. If it does then it supplies the -client with a random "cryptkey". The client will then send all -passwords in encrypted form. You have to compile samba with encryption -enabled to support this feature, and you have to maintain a separate -smbpasswd file with SMB style encrypted passwords. It is -cryptographically impossible to translate from unix style encryption -to SMB style encryption, although there are some fairly simple management -schemes by which the two could be kept in sync.</P -></DIV -></DIV -><DIV -CLASS="CHAPTER" -><HR><H1 -><A NAME="WINBIND" ></A ->Chapter 16. Unified Logons between Windows NT and UNIX using Winbind</H1 +>Chapter 14. Unified Logons between Windows NT and UNIX using Winbind</H1 ><DIV CLASS="SECT1" ><H2 CLASS="SECT1" ><A -NAME="AEN2249" +NAME="AEN2360" ></A ->16.1. Abstract</H2 +>14.1. Abstract</H2 ><P >Integration of UNIX and Microsoft Windows NT through a unified logon has been considered a "holy grail" in heterogeneous @@ -11831,9 +12083,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN2253" +NAME="AEN2364" ></A ->16.2. Introduction</H2 +>14.2. Introduction</H2 ><P >It is well known that UNIX and Microsoft Windows NT have different models for representing user and group information and @@ -11885,9 +12137,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN2266" +NAME="AEN2377" ></A ->16.3. What Winbind Provides</H2 +>14.3. What Winbind Provides</H2 ><P >Winbind unifies UNIX and Windows NT account management by allowing a UNIX box to become a full member of a NT domain. Once @@ -11927,9 +12179,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN2273" +NAME="AEN2384" ></A ->16.3.1. Target Uses</H3 +>14.3.1. Target Uses</H3 ><P >Winbind is targeted at organizations that have an existing NT based domain infrastructure into which they wish @@ -11951,9 +12203,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN2277" +NAME="AEN2388" ></A ->16.4. How Winbind Works</H2 +>14.4. How Winbind Works</H2 ><P >The winbind system is designed around a client/server architecture. A long running <B @@ -11971,11 +12223,11 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN2282" +NAME="AEN2393" ></A ->16.4.1. Microsoft Remote Procedure Calls</H3 +>14.4.1. Microsoft Remote Procedure Calls</H3 ><P ->Over the last two years, efforts have been underway +>Over the last few years, efforts have been underway by various Samba Team members to decode various aspects of the Microsoft Remote Procedure Call (MSRPC) system. This system is used for most network related operations between @@ -11997,9 +12249,28 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN2286" +NAME="AEN2397" +></A +>14.4.2. Microsoft Active Directory Services</H3 +><P +> Since late 2001, Samba has gained the ability to + interact with Microsoft Windows 2000 using its 'Native + Mode' protocols, rather than the NT4 RPC services. + Using LDAP and Kerberos, a domain member running + winbind can enumerate users and groups in exactly the + same way as a Win2k client would, and in so doing + provide a much more efficient and + effective winbind implementation. + </P +></DIV +><DIV +CLASS="SECT2" +><HR><H3 +CLASS="SECT2" +><A +NAME="AEN2400" ></A ->16.4.2. Name Service Switch</H3 +>14.4.3. Name Service Switch</H3 ><P >The Name Service Switch, or NSS, is a feature that is present in many UNIX operating systems. It allows system @@ -12077,9 +12348,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN2302" +NAME="AEN2416" ></A ->16.4.3. Pluggable Authentication Modules</H3 +>14.4.4. Pluggable Authentication Modules</H3 ><P >Pluggable Authentication Modules, also known as PAM, is a system for abstracting authentication and authorization @@ -12126,9 +12397,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN2310" +NAME="AEN2424" ></A ->16.4.4. User and Group ID Allocation</H3 +>14.4.5. User and Group ID Allocation</H3 ><P >When a user or group is created under Windows NT is it allocated a numerical relative identifier (RID). This is @@ -12152,9 +12423,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN2314" +NAME="AEN2428" ></A ->16.4.5. Result Caching</H3 +>14.4.6. Result Caching</H3 ><P >An active system can generate a lot of user and group name lookups. To reduce the network cost of these lookups winbind @@ -12175,9 +12446,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN2317" +NAME="AEN2431" ></A ->16.5. Installation and Configuration</H2 +>14.5. Installation and Configuration</H2 ><P >Many thanks to John Trostel <A HREF="mailto:jtrostel@snapserver.com" @@ -12202,9 +12473,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN2324" +NAME="AEN2438" ></A ->16.5.1. Introduction</H3 +>14.5.1. Introduction</H3 ><P >This HOWTO describes the procedures used to get winbind up and running on my RedHat 7.1 system. Winbind is capable of providing access @@ -12261,9 +12532,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN2337" +NAME="AEN2451" ></A ->16.5.2. Requirements</H3 +>14.5.2. Requirements</H3 ><P >If you have a samba configuration file that you are currently using... <SPAN @@ -12331,9 +12602,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN2351" +NAME="AEN2465" ></A ->16.5.3. Testing Things Out</H3 +>14.5.3. Testing Things Out</H3 ><P >Before starting, it is probably best to kill off all the SAMBA related daemons running on your server. Kill off all <B @@ -12376,9 +12647,9 @@ CLASS="SECT3" ><HR><H4 CLASS="SECT3" ><A -NAME="AEN2362" +NAME="AEN2476" ></A ->16.5.3.1. Configure and compile SAMBA</H4 +>14.5.3.1. Configure and compile SAMBA</H4 ><P >The configuration and compilation of SAMBA is pretty straightforward. The first three steps may not be necessary depending upon @@ -12412,7 +12683,7 @@ CLASS="PROMPT" >root#</TT > <B CLASS="COMMAND" ->./configure --with-winbind</B +>./configure</B > <TT CLASS="PROMPT" @@ -12442,9 +12713,9 @@ CLASS="SECT3" ><HR><H4 CLASS="SECT3" ><A -NAME="AEN2381" +NAME="AEN2495" ></A ->16.5.3.2. Configure <TT +>14.5.3.2. Configure <TT CLASS="FILENAME" >nsswitch.conf</TT > and the @@ -12547,9 +12818,9 @@ CLASS="SECT3" ><HR><H4 CLASS="SECT3" ><A -NAME="AEN2414" +NAME="AEN2528" ></A ->16.5.3.3. Configure smb.conf</H4 +>14.5.3.3. Configure smb.conf</H4 ><P >Several parameters are needed in the smb.conf file to control the behavior of <B @@ -12574,7 +12845,7 @@ include the following entries in the [global] section:</P ><PRE CLASS="PROGRAMLISTING" >[global] - <...> + <...> # separate domain and username with '+', like DOMAIN+username <A HREF="winbindd.8.html#WINBINDSEPARATOR" @@ -12622,9 +12893,9 @@ CLASS="SECT3" ><HR><H4 CLASS="SECT3" ><A -NAME="AEN2430" +NAME="AEN2544" ></A ->16.5.3.4. Join the SAMBA server to the PDC domain</H4 +>14.5.3.4. Join the SAMBA server to the PDC domain</H4 ><P >Enter the following command to make the SAMBA server join the PDC domain, where <TT @@ -12646,7 +12917,7 @@ CLASS="PROMPT" >root#</TT > <B CLASS="COMMAND" ->/usr/local/samba/bin/net rpc join -S PDC -U Administrator</B +>/usr/local/samba/bin/net join -S PDC -U Administrator</B ></P ><P >The proper response to the command should be: "Joined the domain @@ -12668,9 +12939,9 @@ CLASS="SECT3" ><HR><H4 CLASS="SECT3" ><A -NAME="AEN2441" +NAME="AEN2555" ></A ->16.5.3.5. Start up the winbindd daemon and test it!</H4 +>14.5.3.5. Start up the winbindd daemon and test it!</H4 ><P >Eventually, you will want to modify your smb startup script to automatically invoke the winbindd daemon when the other parts of @@ -12791,17 +13062,17 @@ CLASS="SECT3" ><HR><H4 CLASS="SECT3" ><A -NAME="AEN2477" +NAME="AEN2591" ></A ->16.5.3.6. Fix the init.d startup scripts</H4 +>14.5.3.6. Fix the init.d startup scripts</H4 ><DIV CLASS="SECT4" ><H5 CLASS="SECT4" ><A -NAME="AEN2479" +NAME="AEN2593" ></A ->16.5.3.6.1. Linux</H5 +>14.5.3.6.1. Linux</H5 ><P >The <B CLASS="COMMAND" @@ -12858,7 +13129,7 @@ CLASS="PROGRAMLISTING" daemon /usr/local/samba/bin/winbindd RETVAL3=$? echo - [ $RETVAL -eq 0 -a $RETVAL2 -eq 0 -a $RETVAL3 -eq 0 ] && touch /var/lock/subsys/smb || \ + [ $RETVAL -eq 0 -a $RETVAL2 -eq 0 -a $RETVAL3 -eq 0 ] && touch /var/lock/subsys/smb || \ RETVAL=1 return $RETVAL }</PRE @@ -12884,7 +13155,7 @@ CLASS="PROGRAMLISTING" echo -n $"Shutting down $KIND services: " killproc winbindd RETVAL3=$? - [ $RETVAL -eq 0 -a $RETVAL2 -eq 0 -a $RETVAL3 -eq 0 ] && rm -f /var/lock/subsys/smb + [ $RETVAL -eq 0 -a $RETVAL2 -eq 0 -a $RETVAL3 -eq 0 ] && rm -f /var/lock/subsys/smb echo "" return $RETVAL }</PRE @@ -12895,9 +13166,9 @@ CLASS="SECT4" ><HR><H5 CLASS="SECT4" ><A -NAME="AEN2496" +NAME="AEN2610" ></A ->16.5.3.6.2. Solaris</H5 +>14.5.3.6.2. Solaris</H5 ><P >On solaris, you need to modify the <TT @@ -12926,7 +13197,7 @@ killproc() { # kill the named process(es) pid=`/usr/bin/ps -e | /usr/bin/grep -w $1 | /usr/bin/sed -e 's/^ *//' -e 's/ .*//'` - [ "$pid" != "" ] && kill $pid + [ "$pid" != "" ] && kill $pid } # Start/stop processes required for samba server @@ -12966,9 +13237,9 @@ CLASS="SECT4" ><HR><H5 CLASS="SECT4" ><A -NAME="AEN2503" +NAME="AEN2617" ></A ->16.5.3.6.3. Restarting</H5 +>14.5.3.6.3. Restarting</H5 ><P >If you restart the <B CLASS="COMMAND" @@ -12990,9 +13261,9 @@ CLASS="SECT3" ><HR><H4 CLASS="SECT3" ><A -NAME="AEN2509" +NAME="AEN2623" ></A ->16.5.3.7. Configure Winbind and PAM</H4 +>14.5.3.7. Configure Winbind and PAM</H4 ><P >If you have made it this far, you know that winbindd and samba are working together. If you want to use winbind to provide authentication for other @@ -13048,9 +13319,9 @@ CLASS="SECT4" ><HR><H5 CLASS="SECT4" ><A -NAME="AEN2526" +NAME="AEN2640" ></A ->16.5.3.7.1. Linux/FreeBSD-specific PAM configuration</H5 +>14.5.3.7.1. Linux/FreeBSD-specific PAM configuration</H5 ><P >The <TT CLASS="FILENAME" @@ -13177,9 +13448,9 @@ CLASS="SECT4" ><HR><H5 CLASS="SECT4" ><A -NAME="AEN2559" +NAME="AEN2673" ></A ->16.5.3.7.2. Solaris-specific configuration</H5 +>14.5.3.7.2. Solaris-specific configuration</H5 ><P >The /etc/pam.conf needs to be changed. I changed this file so that my Domain users can logon both locally as well as telnet.The following are the changes @@ -13253,7 +13524,7 @@ dtsession auth required /usr/lib/security/$ISA/pam_unix.so.1 >I also added a try_first_pass line after the winbind.so line to get rid of annoying double prompts for passwords.</P ><P ->Now restart your Samba & try connecting through your application that you +>Now restart your Samba and try connecting through your application that you configured in the pam.conf.</P ></DIV ></DIV @@ -13264,9 +13535,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN2566" +NAME="AEN2680" ></A ->16.6. Limitations</H2 +>14.6. Limitations</H2 ><P >Winbind has a number of limitations in its current released version that we hope to overcome in future @@ -13277,7 +13548,7 @@ NAME="AEN2566" ><LI ><P >Winbind is currently only available for - the Linux operating system, although ports to other operating + the Linux, Solaris and IRIX operating systems, although ports to other operating systems are certainly possible. For such ports to be feasible, we require the C library of the target operating system to support the Name Service Switch and Pluggable Authentication @@ -13296,7 +13567,8 @@ NAME="AEN2566" ><P >Currently the winbind PAM module does not take into account possible workstation and logon time restrictions - that may be been set for Windows NT users.</P + that may be been set for Windows NT users, this is + instead up to the PDC to enforce.</P ></LI ></UL ></DIV @@ -13305,9 +13577,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN2576" +NAME="AEN2690" ></A ->16.7. Conclusion</H2 +>14.7. Conclusion</H2 ><P >The winbind system, through the use of the Name Service Switch, Pluggable Authentication Modules, and appropriate @@ -13321,1081 +13593,991 @@ NAME="AEN2576" CLASS="CHAPTER" ><HR><H1 ><A -NAME="PDB-MYSQL" +NAME="IMPROVED-BROWSING" ></A ->Chapter 17. Passdb MySQL plugin</H1 +>Chapter 15. Improved browsing in samba</H1 ><DIV CLASS="SECT1" ><H2 CLASS="SECT1" ><A -NAME="AEN2590" +NAME="AEN2700" ></A ->17.1. Building</H2 +>15.1. Overview of browsing</H2 ><P ->To build the plugin, run <B -CLASS="COMMAND" ->make bin/pdb_mysql.so</B -> -in the <TT -CLASS="FILENAME" ->source/</TT -> directory of samba distribution. </P +>SMB networking provides a mechanism by which clients can access a list +of machines in a network, a so-called "browse list". This list +contains machines that are ready to offer file and/or print services +to other machines within the network. Thus it does not include +machines which aren't currently able to do server tasks. The browse +list is heavily used by all SMB clients. Configuration of SMB +browsing has been problematic for some Samba users, hence this +document.</P ><P ->Next, copy pdb_mysql.so to any location you want. I -strongly recommend installing it in $PREFIX/lib or /usr/lib/samba/</P +>Browsing will NOT work if name resolution from NetBIOS names to IP +addresses does not function correctly. Use of a WINS server is highly +recommended to aid the resolution of NetBIOS (SMB) names to IP addresses. +WINS allows remote segment clients to obtain NetBIOS name_type information +that can NOT be provided by any other means of name resolution.</P ></DIV ><DIV CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN2596" +NAME="AEN2704" ></A ->17.2. Configuring</H2 -><P ->This plugin lacks some good documentation, but here is some short info:</P +>15.2. Browsing support in samba</H2 ><P ->Add a the following to the <B -CLASS="COMMAND" ->passdb backend</B -> variable in your <TT -CLASS="FILENAME" ->smb.conf</TT ->: -<PRE -CLASS="PROGRAMLISTING" ->passdb backend = [other-plugins] plugin:/location/to/pdb_mysql.so:identifier [other-plugins]</PRE -></P +>Samba now fully supports browsing. The browsing is supported by nmbd +and is also controlled by options in the smb.conf file (see smb.conf(5)).</P ><P ->The identifier can be any string you like, as long as it doesn't collide with -the identifiers of other plugins or other instances of pdb_mysql. If you -specify multiple pdb_mysql.so entries in 'passdb backend', you also need to -use different identifiers!</P +>Samba can act as a local browse master for a workgroup and the ability +for samba to support domain logons and scripts is now available. See +DOMAIN.txt for more information on domain logons.</P ><P ->Additional options can be given thru the smb.conf file in the [global] section.</P +>Samba can also act as a domain master browser for a workgroup. This +means that it will collate lists from local browse masters into a +wide area network server list. In order for browse clients to +resolve the names they may find in this list, it is recommended that +both samba and your clients use a WINS server.</P ><P -><PRE -CLASS="PROGRAMLISTING" ->identifier:mysql host - host name, defaults to 'localhost' -identifier:mysql password -identifier:mysql user - defaults to 'samba' -identifier:mysql database - defaults to 'samba' -identifier:mysql port - defaults to 3306 -identifier:table - Name of the table containing users</PRE -></P +>Note that you should NOT set Samba to be the domain master for a +workgroup that has the same name as an NT Domain: on each wide area +network, you must only ever have one domain master browser per workgroup, +regardless of whether it is NT, Samba or any other type of domain master +that is providing this service.</P ><P ->Names of the columns in this table(I've added column types those columns should have first):</P +>[Note that nmbd can be configured as a WINS server, but it is not +necessary to specifically use samba as your WINS server. NTAS can +be configured as your WINS server. In a mixed NT server and +samba environment on a Wide Area Network, it is recommended that +you use the NT server's WINS server capabilities. In a samba-only +environment, it is recommended that you use one and only one nmbd +as your WINS server].</P ><P -><PRE -CLASS="PROGRAMLISTING" ->identifier:logon time column - int(9) -identifier:logoff time column - int(9) -identifier:kickoff time column - int(9) -identifier:pass last set time column - int(9) -identifier:pass can change time column - int(9) -identifier:pass must change time column - int(9) -identifier:username column - varchar(255) - unix username -identifier:domain column - varchar(255) - NT domain user is part of -identifier:nt username column - varchar(255) - NT username -identifier:fullname column - varchar(255) - Full name of user -identifier:home dir column - varchar(255) - Unix homedir path -identifier:dir drive column - varchar(2) - Directory drive path (eg: 'H:') -identifier:logon script column - varchar(255) - Batch file to run on client side when logging on -identifier:profile path column - varchar(255) - Path of profile -identifier:acct desc column - varchar(255) - Some ASCII NT user data -identifier:workstations column - varchar(255) - Workstations user can logon to (or NULL for all) -identifier:unknown string column - varchar(255) - unknown string -identifier:munged dial column - varchar(255) - ? -identifier:uid column - int(9) - Unix user ID (uid) -identifier:gid column - int(9) - Unix user group (gid) -identifier:user sid column - varchar(255) - NT user SID -identifier:group sid column - varchar(255) - NT group ID -identifier:lanman pass column - varchar(255) - encrypted lanman password -identifier:nt pass column - varchar(255) - encrypted nt passwd -identifier:plaintext pass column - varchar(255) - plaintext password -identifier:acct control column - int(9) - nt user data -identifier:unknown 3 column - int(9) - unknown -identifier:logon divs column - int(9) - ? -identifier:hours len column - int(9) - ? -identifier:unknown 5 column - int(9) - unknown -identifier:unknown 6 column - int(9) - unknown</PRE -></P +>To get browsing to work you need to run nmbd as usual, but will need +to use the "workgroup" option in smb.conf to control what workgroup +Samba becomes a part of.</P ><P ->Eventually, you can put a colon (:) after the name of each column, which -should specify the column to update when updating the table. You can also -specify nothing behind the colon - then the data from the field will not be -updated. </P +>Samba also has a useful option for a Samba server to offer itself for +browsing on another subnet. It is recommended that this option is only +used for 'unusual' purposes: announcements over the internet, for +example. See "remote announce" in the smb.conf man page. </P ></DIV ><DIV CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN2611" +NAME="AEN2713" ></A ->17.3. Using plaintext passwords or encrypted password</H2 +>15.3. Problem resolution</H2 ><P ->I strongly discourage the use of plaintext passwords, however, you can use them:</P +>If something doesn't work then hopefully the log.nmb file will help +you track down the problem. Try a debug level of 2 or 3 for finding +problems. Also note that the current browse list usually gets stored +in text form in a file called browse.dat.</P +><P +>Note that if it doesn't work for you, then you should still be able to +type the server name as \\SERVER in filemanager then hit enter and +filemanager should display the list of available shares.</P ><P ->If you would like to use plaintext passwords, set 'identifier:lanman pass column' and 'identifier:nt pass column' to 'NULL' (without the quotes) and 'identifier:plaintext pass column' to the name of the column containing the plaintext passwords. </P +>Some people find browsing fails because they don't have the global +"guest account" set to a valid account. Remember that the IPC$ +connection that lists the shares is done as guest, and thus you must +have a valid guest account.</P ><P ->If you use encrypted passwords, set the 'identifier:plaintext pass column' to 'NULL' (without the quotes). This is the default.</P +>Also, a lot of people are getting bitten by the problem of too many +parameters on the command line of nmbd in inetd.conf. This trick is to +not use spaces between the option and the parameter (eg: -d2 instead +of -d 2), and to not use the -B and -N options. New versions of nmbd +are now far more likely to correctly find your broadcast and network +address, so in most cases these aren't needed.</P +><P +>The other big problem people have is that their broadcast address, +netmask or IP address is wrong (specified with the "interfaces" option +in smb.conf)</P ></DIV ><DIV CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN2616" +NAME="AEN2720" ></A ->17.4. Getting non-column data from the table</H2 +>15.4. Browsing across subnets</H2 ><P ->It is possible to have not all data in the database and making some 'constant'.</P -><P ->For example, you can set 'identifier:fullname column' to : -<B -CLASS="COMMAND" ->CONCAT(First_name,' ',Sur_name)</B -></P +>With the release of Samba 1.9.17(alpha1 and above) Samba has been +updated to enable it to support the replication of browse lists +across subnet boundaries. New code and options have been added to +achieve this. This section describes how to set this feature up +in different settings.</P ><P ->Or, set 'identifier:workstations column' to : -<B -CLASS="COMMAND" ->NULL</B -></P +>To see browse lists that span TCP/IP subnets (ie. networks separated +by routers that don't pass broadcast traffic) you must set up at least +one WINS server. The WINS server acts as a DNS for NetBIOS names, allowing +NetBIOS name to IP address translation to be done by doing a direct +query of the WINS server. This is done via a directed UDP packet on +port 137 to the WINS server machine. The reason for a WINS server is +that by default, all NetBIOS name to IP address translation is done +by broadcasts from the querying machine. This means that machines +on one subnet will not be able to resolve the names of machines on +another subnet without using a WINS server.</P ><P ->See the MySQL documentation for more language constructs.</P -></DIV -></DIV -><DIV -CLASS="CHAPTER" -><HR><H1 -><A -NAME="PDB-XML" -></A ->Chapter 18. Passdb XML plugin</H1 +>Remember, for browsing across subnets to work correctly, all machines, +be they Windows 95, Windows NT, or Samba servers must have the IP address +of a WINS server given to them by a DHCP server, or by manual configuration +(for Win95 and WinNT, this is in the TCP/IP Properties, under Network +settings) for Samba this is in the smb.conf file.</P ><DIV -CLASS="SECT1" -><H2 -CLASS="SECT1" +CLASS="SECT2" +><HR><H3 +CLASS="SECT2" ><A -NAME="AEN2635" +NAME="AEN2725" ></A ->18.1. Building</H2 +>15.4.1. How does cross subnet browsing work ?</H3 ><P ->This module requires libxml2 to be installed.</P +>Cross subnet browsing is a complicated dance, containing multiple +moving parts. It has taken Microsoft several years to get the code +that achieves this correct, and Samba lags behind in some areas. +However, with the 1.9.17 release, Samba is capable of cross subnet +browsing when configured correctly.</P ><P ->To build pdb_xml, run: <B -CLASS="COMMAND" ->make bin/pdb_xml.so</B -> in -the directory <TT -CLASS="FILENAME" ->source/</TT ->. </P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN2641" -></A ->18.2. Usage</H2 +>Consider a network set up as follows :</P ><P ->The usage of pdb_xml is pretty straightforward. To export data, use: +><PRE +CLASS="PROGRAMLISTING" +> (DMB) + N1_A N1_B N1_C N1_D N1_E + | | | | | + ------------------------------------------------------- + | subnet 1 | + +---+ +---+ + |R1 | Router 1 Router 2 |R2 | + +---+ +---+ + | | + | subnet 2 subnet 3 | + -------------------------- ------------------------------------ + | | | | | | | | + N2_A N2_B N2_C N2_D N3_A N3_B N3_C N3_D + (WINS)</PRE +></P +><P +>Consisting of 3 subnets (1, 2, 3) connected by two routers +(R1, R2) - these do not pass broadcasts. Subnet 1 has 5 machines +on it, subnet 2 has 4 machines, subnet 3 has 4 machines. Assume +for the moment that all these machines are configured to be in the +same workgroup (for simplicities sake). Machine N1_C on subnet 1 +is configured as Domain Master Browser (ie. it will collate the +browse lists for the workgroup). Machine N2_D is configured as +WINS server and all the other machines are configured to register +their NetBIOS names with it.</P +><P +>As all these machines are booted up, elections for master browsers +will take place on each of the three subnets. Assume that machine +N1_C wins on subnet 1, N2_B wins on subnet 2, and N3_D wins on +subnet 3 - these machines are known as local master browsers for +their particular subnet. N1_C has an advantage in winning as the +local master browser on subnet 1 as it is set up as Domain Master +Browser.</P +><P +>On each of the three networks, machines that are configured to +offer sharing services will broadcast that they are offering +these services. The local master browser on each subnet will +receive these broadcasts and keep a record of the fact that +the machine is offering a service. This list of records is +the basis of the browse list. For this case, assume that +all the machines are configured to offer services so all machines +will be on the browse list.</P +><P +>For each network, the local master browser on that network is +considered 'authoritative' for all the names it receives via +local broadcast. This is because a machine seen by the local +master browser via a local broadcast must be on the same +network as the local master browser and thus is a 'trusted' +and 'verifiable' resource. Machines on other networks that +the local master browsers learn about when collating their +browse lists have not been directly seen - these records are +called 'non-authoritative'.</P +><P +>At this point the browse lists look as follows (these are +the machines you would see in your network neighborhood if +you looked in it on a particular network right now).</P +><P +><PRE +CLASS="PROGRAMLISTING" +>Subnet Browse Master List +------ ------------- ---- +Subnet1 N1_C N1_A, N1_B, N1_C, N1_D, N1_E -<B -CLASS="COMMAND" ->pdbedit -e plugin:/usr/lib/samba/pdb_xml.so:filename</B -> +Subnet2 N2_B N2_A, N2_B, N2_C, N2_D -(where filename is the name of the file to put the data in)</P +Subnet3 N3_D N3_A, N3_B, N3_C, N3_D</PRE +></P ><P ->To import data, use: -<B -CLASS="COMMAND" ->pdbedit -i plugin:/usr/lib/samba/pdb_xml.so:filename -e current-pdb</B -> - -Where filename is the name to read the data from and current-pdb to put it in.</P -></DIV -></DIV -><DIV -CLASS="CHAPTER" -><HR><H1 -><A -NAME="SAMBA-LDAP-HOWTO" -></A ->Chapter 19. Storing Samba's User/Machine Account information in an LDAP Directory</H1 -><DIV -CLASS="SECT1" -><H2 -CLASS="SECT1" -><A -NAME="AEN2664" -></A ->19.1. Purpose</H2 +>Note that at this point all the subnets are separate, no +machine is seen across any of the subnets.</P ><P ->This document describes how to use an LDAP directory for storing Samba user -account information traditionally stored in the smbpasswd(5) file. It is -assumed that the reader already has a basic understanding of LDAP concepts -and has a working directory server already installed. For more information -on LDAP architectures and Directories, please refer to the following sites.</P +>Now examine subnet 2. As soon as N2_B has become the local +master browser it looks for a Domain master browser to synchronize +its browse list with. It does this by querying the WINS server +(N2_D) for the IP address associated with the NetBIOS name +WORKGROUP>1B<. This name was registerd by the Domain master +browser (N1_C) with the WINS server as soon as it was booted.</P +><P +>Once N2_B knows the address of the Domain master browser it +tells it that is the local master browser for subnet 2 by +sending a MasterAnnouncement packet as a UDP port 138 packet. +It then synchronizes with it by doing a NetServerEnum2 call. This +tells the Domain Master Browser to send it all the server +names it knows about. Once the domain master browser receives +the MasterAnnouncement packet it schedules a synchronization +request to the sender of that packet. After both synchronizations +are done the browse lists look like :</P ><P +><PRE +CLASS="PROGRAMLISTING" +>Subnet Browse Master List +------ ------------- ---- +Subnet1 N1_C N1_A, N1_B, N1_C, N1_D, N1_E, + N2_A(*), N2_B(*), N2_C(*), N2_D(*) + +Subnet2 N2_B N2_A, N2_B, N2_C, N2_D + N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*) + +Subnet3 N3_D N3_A, N3_B, N3_C, N3_D + +Servers with a (*) after them are non-authoritative names.</PRE ></P -><UL -><LI ><P ->OpenLDAP - <A -HREF="http://www.openldap.org/" -TARGET="_top" ->http://www.openldap.org/</A +>At this point users looking in their network neighborhood on +subnets 1 or 2 will see all the servers on both, users on +subnet 3 will still only see the servers on their own subnet.</P +><P +>The same sequence of events that occured for N2_B now occurs +for the local master browser on subnet 3 (N3_D). When it +synchronizes browse lists with the domain master browser (N1_A) +it gets both the server entries on subnet 1, and those on +subnet 2. After N3_D has synchronized with N1_C and vica-versa +the browse lists look like.</P +><P +><PRE +CLASS="PROGRAMLISTING" +>Subnet Browse Master List +------ ------------- ---- +Subnet1 N1_C N1_A, N1_B, N1_C, N1_D, N1_E, + N2_A(*), N2_B(*), N2_C(*), N2_D(*), + N3_A(*), N3_B(*), N3_C(*), N3_D(*) + +Subnet2 N2_B N2_A, N2_B, N2_C, N2_D + N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*) + +Subnet3 N3_D N3_A, N3_B, N3_C, N3_D + N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*), + N2_A(*), N2_B(*), N2_C(*), N2_D(*) + +Servers with a (*) after them are non-authoritative names.</PRE ></P -></LI -><LI ><P ->iPlanet Directory Server - <A -HREF="http://iplanet.netscape.com/directory" -TARGET="_top" ->http://iplanet.netscape.com/directory</A +>At this point users looking in their network neighborhood on +subnets 1 or 3 will see all the servers on all sunbets, users on +subnet 2 will still only see the servers on subnets 1 and 2, but not 3.</P +><P +>Finally, the local master browser for subnet 2 (N2_B) will sync again +with the domain master browser (N1_C) and will recieve the missing +server entries. Finally - and as a steady state (if no machines +are removed or shut off) the browse lists will look like :</P +><P +><PRE +CLASS="PROGRAMLISTING" +>Subnet Browse Master List +------ ------------- ---- +Subnet1 N1_C N1_A, N1_B, N1_C, N1_D, N1_E, + N2_A(*), N2_B(*), N2_C(*), N2_D(*), + N3_A(*), N3_B(*), N3_C(*), N3_D(*) + +Subnet2 N2_B N2_A, N2_B, N2_C, N2_D + N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*) + N3_A(*), N3_B(*), N3_C(*), N3_D(*) + +Subnet3 N3_D N3_A, N3_B, N3_C, N3_D + N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*), + N2_A(*), N2_B(*), N2_C(*), N2_D(*) + +Servers with a (*) after them are non-authoritative names.</PRE ></P -></LI -></UL ><P ->Note that <A -HREF="http://www.ora.com/" -TARGET="_top" ->O'Reilly Publishing</A -> is working on -a guide to LDAP for System Administrators which has a planned release date of -early summer, 2002.</P +>Synchronizations between the domain master browser and local +master browsers will continue to occur, but this should be a +steady state situation.</P ><P ->Two additional Samba resources which may prove to be helpful are</P +>If either router R1 or R2 fails the following will occur:</P ><P ></P -><UL +><OL +TYPE="1" ><LI ><P ->The <A -HREF="http://www.unav.es/cti/ldap-smb/ldap-smb-2_2-howto.html" -TARGET="_top" ->Samba-PDC-LDAP-HOWTO</A -> - maintained by Ignacio Coupeau.</P +> Names of computers on each side of the inaccessible network fragments + will be maintained for as long as 36 minutes, in the network neighbourhood + lists. + </P ></LI ><LI ><P ->The NT migration scripts from <A -HREF="http://samba.idealx.org/" -TARGET="_top" ->IDEALX</A -> that are - geared to manage users and group in such a Samba-LDAP Domain Controller configuration. +> Attempts to connect to these inaccessible computers will fail, but the + names will not be removed from the network neighbourhood lists. </P ></LI -></UL +><LI +><P +> If one of the fragments is cut off from the WINS server, it will only + be able to access servers on its local subnet, by using subnet-isolated + broadcast NetBIOS name resolution. The effects are similar to that of + losing access to a DNS server. + </P +></LI +></OL +></DIV ></DIV ><DIV CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN2684" +NAME="AEN2760" ></A ->19.2. Introduction</H2 +>15.5. Setting up a WINS server</H2 ><P ->Traditionally, when configuring <A -HREF="smb.conf.5.html#ENCRYPTPASSWORDS" -TARGET="_top" ->"encrypt -passwords = yes"</A -> in Samba's <TT -CLASS="FILENAME" ->smb.conf</TT -> file, user account -information such as username, LM/NT password hashes, password change times, and account -flags have been stored in the <TT -CLASS="FILENAME" ->smbpasswd(5)</TT -> file. There are several -disadvantages to this approach for sites with very large numbers of users (counted -in the thousands).</P +>Either a Samba machine or a Windows NT Server machine may be set up +as a WINS server. To set a Samba machine to be a WINS server you must +add the following option to the smb.conf file on the selected machine : +in the [globals] section add the line </P ><P +><B +CLASS="COMMAND" +> wins support = yes</B ></P -><UL -><LI ><P ->The first is that all lookups must be performed sequentially. Given that -there are approximately two lookups per domain logon (one for a normal -session connection such as when mapping a network drive or printer), this -is a performance bottleneck for lareg sites. What is needed is an indexed approach -such as is used in databases.</P -></LI -><LI +>Versions of Samba previous to 1.9.17 had this parameter default to +yes. If you have any older versions of Samba on your network it is +strongly suggested you upgrade to 1.9.17 or above, or at the very +least set the parameter to 'no' on all these machines.</P ><P ->The second problem is that administrators who desired to replicate a -smbpasswd file to more than one Samba server were left to use external -tools such as <B -CLASS="COMMAND" ->rsync(1)</B -> and <B +>Machines with "<B CLASS="COMMAND" ->ssh(1)</B -> -and wrote custom, in-house scripts.</P -></LI -><LI -><P ->And finally, the amount of information which is stored in an -smbpasswd entry leaves no room for additional attributes such as -a home directory, password expiration time, or even a Relative -Identified (RID).</P -></LI -></UL +>wins support = yes</B +>" will keep a list of +all NetBIOS names registered with them, acting as a DNS for NetBIOS names.</P ><P ->As a result of these defeciencies, a more robust means of storing user attributes -used by smbd was developed. The API which defines access to user accounts -is commonly referred to as the samdb interface (previously this was called the passdb -API, and is still so named in the CVS trees). In Samba 2.2.3, enabling support -for a samdb backend (e.g. <TT -CLASS="PARAMETER" -><I ->--with-ldapsam</I -></TT -> or -<TT -CLASS="PARAMETER" -><I ->--with-tdbsam</I -></TT ->) requires compile time support.</P +>You should set up only ONE wins server. Do NOT set the +"<B +CLASS="COMMAND" +>wins support = yes</B +>" option on more than one Samba +server.</P ><P ->When compiling Samba to include the <TT -CLASS="PARAMETER" -><I ->--with-ldapsam</I -></TT -> autoconf -option, smbd (and associated tools) will store and lookup user accounts in -an LDAP directory. In reality, this is very easy to understand. If you are -comfortable with using an smbpasswd file, simply replace "smbpasswd" with -"LDAP directory" in all the documentation.</P +>To set up a Windows NT Server as a WINS server you need to set up +the WINS service - see your NT documentation for details. Note that +Windows NT WINS Servers can replicate to each other, allowing more +than one to be set up in a complex subnet environment. As Microsoft +refuse to document these replication protocols Samba cannot currently +participate in these replications. It is possible in the future that +a Samba->Samba WINS replication protocol may be defined, in which +case more than one Samba machine could be set up as a WINS server +but currently only one Samba server should have the "wins support = yes" +parameter set.</P ><P ->There are a few points to stress about what the <TT -CLASS="PARAMETER" -><I ->--with-ldapsam</I -></TT -> -does not provide. The LDAP support referred to in the this documentation does not -include:</P +>After the WINS server has been configured you must ensure that all +machines participating on the network are configured with the address +of this WINS server. If your WINS server is a Samba machine, fill in +the Samba machine IP address in the "Primary WINS Server" field of +the "Control Panel->Network->Protocols->TCP->WINS Server" dialogs +in Windows 95 or Windows NT. To tell a Samba server the IP address +of the WINS server add the following line to the [global] section of +all smb.conf files :</P ><P +><B +CLASS="COMMAND" +>wins server = >name or IP address<</B ></P -><UL -><LI ><P ->A means of retrieving user account information from - an Windows 2000 Active Directory server.</P -></LI -><LI +>where >name or IP address< is either the DNS name of the WINS server +machine or its IP address.</P ><P ->A means of replacing /etc/passwd.</P -></LI -></UL +>Note that this line MUST NOT BE SET in the smb.conf file of the Samba +server acting as the WINS server itself. If you set both the +"<B +CLASS="COMMAND" +>wins support = yes</B +>" option and the +"<B +CLASS="COMMAND" +>wins server = >name<</B +>" option then +nmbd will fail to start.</P ><P ->The second item can be accomplished by using LDAP NSS and PAM modules. LGPL -versions of these libraries can be obtained from PADL Software -(<A -HREF="http://www.padl.com/" -TARGET="_top" ->http://www.padl.com/</A ->). However, -the details of configuring these packages are beyond the scope of this document.</P +>There are two possible scenarios for setting up cross subnet browsing. +The first details setting up cross subnet browsing on a network containing +Windows 95, Samba and Windows NT machines that are not configured as +part of a Windows NT Domain. The second details setting up cross subnet +browsing on networks that contain NT Domains.</P ></DIV ><DIV CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN2713" +NAME="AEN2779" ></A ->19.3. Supported LDAP Servers</H2 +>15.6. Setting up Browsing in a WORKGROUP</H2 ><P ->The LDAP samdb code in 2.2.3 has been developed and tested using the OpenLDAP -2.0 server and client libraries. The same code should be able to work with -Netscape's Directory Server and client SDK. However, due to lack of testing -so far, there are bound to be compile errors and bugs. These should not be -hard to fix. If you are so inclined, please be sure to forward all patches to -<A -HREF="samba-patches@samba.org" -TARGET="_top" ->samba-patches@samba.org</A -> and -<A -HREF="jerry@samba.org" -TARGET="_top" ->jerry@samba.org</A ->.</P +>To set up cross subnet browsing on a network containing machines +in up to be in a WORKGROUP, not an NT Domain you need to set up one +Samba server to be the Domain Master Browser (note that this is *NOT* +the same as a Primary Domain Controller, although in an NT Domain the +same machine plays both roles). The role of a Domain master browser is +to collate the browse lists from local master browsers on all the +subnets that have a machine participating in the workgroup. Without +one machine configured as a domain master browser each subnet would +be an isolated workgroup, unable to see any machines on any other +subnet. It is the presense of a domain master browser that makes +cross subnet browsing possible for a workgroup.</P +><P +>In an WORKGROUP environment the domain master browser must be a +Samba server, and there must only be one domain master browser per +workgroup name. To set up a Samba server as a domain master browser, +set the following option in the [global] section of the smb.conf file :</P +><P +><B +CLASS="COMMAND" +>domain master = yes</B +></P +><P +>The domain master browser should also preferrably be the local master +browser for its own subnet. In order to achieve this set the following +options in the [global] section of the smb.conf file :</P +><P +><PRE +CLASS="PROGRAMLISTING" +> domain master = yes + local master = yes + preferred master = yes + os level = 65</PRE +></P +><P +>The domain master browser may be the same machine as the WINS +server, if you require.</P +><P +>Next, you should ensure that each of the subnets contains a +machine that can act as a local master browser for the +workgroup. Any NT machine should be able to do this, as will +Windows 95 machines (although these tend to get rebooted more +often, so it's not such a good idea to use these). To make a +Samba server a local master browser set the following +options in the [global] section of the smb.conf file :</P +><P +><PRE +CLASS="PROGRAMLISTING" +> domain master = no + local master = yes + preferred master = yes + os level = 65</PRE +></P +><P +>Do not do this for more than one Samba server on each subnet, +or they will war with each other over which is to be the local +master browser.</P +><P +>The "local master" parameter allows Samba to act as a local master +browser. The "preferred master" causes nmbd to force a browser +election on startup and the "os level" parameter sets Samba high +enough so that it should win any browser elections.</P +><P +>If you have an NT machine on the subnet that you wish to +be the local master browser then you can disable Samba from +becoming a local master browser by setting the following +options in the [global] section of the smb.conf file :</P +><P +><PRE +CLASS="PROGRAMLISTING" +> domain master = no + local master = no + preferred master = no + os level = 0</PRE +></P ></DIV ><DIV CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN2718" +NAME="AEN2797" ></A ->19.4. Schema and Relationship to the RFC 2307 posixAccount</H2 +>15.7. Setting up Browsing in a DOMAIN</H2 ><P ->Samba 2.2.3 includes the necessary schema file for OpenLDAP 2.0 in -<TT -CLASS="FILENAME" ->examples/LDAP/samba.schema</TT ->. (Note that this schema -file has been modified since the experimental support initially included -in 2.2.2). The sambaAccount objectclass is given here:</P +>If you are adding Samba servers to a Windows NT Domain then +you must not set up a Samba server as a domain master browser. +By default, a Windows NT Primary Domain Controller for a Domain +name is also the Domain master browser for that name, and many +things will break if a Samba server registers the Domain master +browser NetBIOS name (DOMAIN>1B<) with WINS instead of the PDC.</P +><P +>For subnets other than the one containing the Windows NT PDC +you may set up Samba servers as local master browsers as +described. To make a Samba server a local master browser set +the following options in the [global] section of the smb.conf +file :</P ><P ><PRE CLASS="PROGRAMLISTING" ->objectclass ( 1.3.1.5.1.4.1.7165.2.2.2 NAME 'sambaAccount' SUP top STRUCTURAL - DESC 'Samba Account' - MUST ( uid $ rid ) - MAY ( cn $ lmPassword $ ntPassword $ pwdLastSet $ logonTime $ - logoffTime $ kickoffTime $ pwdCanChange $ pwdMustChange $ acctFlags $ - displayName $ smbHome $ homeDrive $ scriptPath $ profilePath $ - description $ userWorkstations $ primaryGroupID $ domain ))</PRE +> domain master = no + local master = yes + preferred master = yes + os level = 65</PRE ></P ><P ->The samba.schema file has been formatted for OpenLDAP 2.0. The OID's are -owned by the Samba Team and as such is legal to be openly published. -If you translate the schema to be used with Netscape DS, please -submit the modified schema file as a patch to <A -HREF="jerry@samba.org" -TARGET="_top" ->jerry@samba.org</A -></P +>If you wish to have a Samba server fight the election with machines +on the same subnet you may set the "os level" parameter to lower +levels. By doing this you can tune the order of machines that +will become local master browsers if they are running. For +more details on this see the section "FORCING SAMBA TO BE THE MASTER" +below.</P ><P ->Just as the smbpasswd file is mean to store information which supplements a -user's <TT -CLASS="FILENAME" ->/etc/passwd</TT -> entry, so is the sambaAccount object -meant to supplement the UNIX user account information. A sambaAccount is a -<TT -CLASS="CONSTANT" ->STRUCTURAL</TT -> objectclass so it can be stored individually -in the directory. However, there are several fields (e.g. uid) which overlap -with the posixAccount objectclass outlined in RFC2307. This is by design.</P +>If you have Windows NT machines that are members of the domain +on all subnets, and you are sure they will always be running then +you can disable Samba from taking part in browser elections and +ever becoming a local master browser by setting following options +in the [global] section of the smb.conf file :</P ><P ->In order to store all user account information (UNIX and Samba) in the directory, -it is necessary to use the sambaAccount and posixAccount objectclasses in -combination. However, smbd will still obtain the user's UNIX account -information via the standard C library calls (e.g. getpwnam(), et. al.). -This means that the Samba server must also have the LDAP NSS library installed -and functioning correctly. This division of information makes it possible to -store all Samba account information in LDAP, but still maintain UNIX account -information in NIS while the network is transitioning to a full LDAP infrastructure.</P +><B +CLASS="COMMAND" +> domain master = no + local master = no + preferred master = no + os level = 0</B +></P ></DIV ><DIV CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN2730" +NAME="AEN2807" ></A ->19.5. Configuring Samba with LDAP</H2 -><DIV -CLASS="SECT2" -><H3 -CLASS="SECT2" -><A -NAME="AEN2732" -></A ->19.5.1. OpenLDAP configuration</H3 +>15.8. Forcing samba to be the master</H2 ><P ->To include support for the sambaAccount object in an OpenLDAP directory -server, first copy the samba.schema file to slapd's configuration directory.</P +>Who becomes the "master browser" is determined by an election process +using broadcasts. Each election packet contains a number of parameters +which determine what precedence (bias) a host should have in the +election. By default Samba uses a very low precedence and thus loses +elections to just about anyone else.</P ><P -><TT -CLASS="PROMPT" ->root# </TT -><B -CLASS="COMMAND" ->cp samba.schema /etc/openldap/schema/</B -></P +>If you want Samba to win elections then just set the "os level" global +option in smb.conf to a higher number. It defaults to 0. Using 34 +would make it win all elections over every other system (except other +samba systems!)</P ><P ->Next, include the <TT -CLASS="FILENAME" ->samba.schema</TT -> file in <TT -CLASS="FILENAME" ->slapd.conf</TT ->. -The sambaAccount object contains two attributes which depend upon other schema -files. The 'uid' attribute is defined in <TT -CLASS="FILENAME" ->cosine.schema</TT -> and -the 'displayName' attribute is defined in the <TT -CLASS="FILENAME" ->inetorgperson.schema</TT -> -file. Both of these must be included before the <TT -CLASS="FILENAME" ->samba.schema</TT -> file.</P +>A "os level" of 2 would make it beat WfWg and Win95, but not NTAS. A +NTAS domain controller uses level 32.</P ><P -><PRE -CLASS="PROGRAMLISTING" ->## /etc/openldap/slapd.conf - -## schema files (core.schema is required by default) -include /etc/openldap/schema/core.schema - -## needed for sambaAccount -include /etc/openldap/schema/cosine.schema -include /etc/openldap/schema/inetorgperson.schema -include /etc/openldap/schema/samba.schema - -## uncomment this line if you want to support the RFC2307 (NIS) schema -## include /etc/openldap/schema/nis.schema - -....</PRE -></P +>The maximum os level is 255</P ><P ->It is recommended that you maintain some indices on some of the most usefull attributes, -like in the following example, to speed up searches made on sambaAccount objectclasses -(and possibly posixAccount and posixGroup as well).</P +>If you want samba to force an election on startup, then set the +"preferred master" global option in smb.conf to "yes". Samba will +then have a slight advantage over other potential master browsers +that are not preferred master browsers. Use this parameter with +care, as if you have two hosts (whether they are windows 95 or NT or +samba) on the same local subnet both set with "preferred master" to +"yes", then periodically and continually they will force an election +in order to become the local master browser.</P ><P -><PRE -CLASS="PROGRAMLISTING" -># Indices to maintain -## required by OpenLDAP 2.0 -index objectclass eq - -## support pb_getsampwnam() -index uid pres,eq -## support pdb_getsambapwrid() -index rid eq - -## uncomment these if you are storing posixAccount and -## posixGroup entries in the directory as well -##index uidNumber eq -##index gidNumber eq -##index cn eq -##index memberUid eq</PRE -></P +>If you want samba to be a "domain master browser", then it is +recommended that you also set "preferred master" to "yes", because +samba will not become a domain master browser for the whole of your +LAN or WAN if it is not also a local master browser on its own +broadcast isolated subnet.</P +><P +>It is possible to configure two samba servers to attempt to become +the domain master browser for a domain. The first server that comes +up will be the domain master browser. All other samba servers will +attempt to become the domain master browser every 5 minutes. They +will find that another samba server is already the domain master +browser and will fail. This provides automatic redundancy, should +the current domain master browser fail.</P ></DIV ><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" +CLASS="SECT1" +><HR><H2 +CLASS="SECT1" ><A -NAME="AEN2749" +NAME="AEN2816" ></A ->19.5.2. Configuring Samba</H3 +>15.9. Making samba the domain master</H2 ><P ->The following parameters are available in smb.conf only with <TT -CLASS="PARAMETER" -><I ->--with-ldapsam</I -></TT -> -was included with compiling Samba.</P +>The domain master is responsible for collating the browse lists of +multiple subnets so that browsing can occur between subnets. You can +make samba act as the domain master by setting "domain master = yes" +in smb.conf. By default it will not be a domain master.</P ><P -></P -><UL -><LI +>Note that you should NOT set Samba to be the domain master for a +workgroup that has the same name as an NT Domain.</P +><P +>When samba is the domain master and the master browser it will listen +for master announcements (made roughly every twelve minutes) from local +master browsers on other subnets and then contact them to synchronise +browse lists.</P +><P +>If you want samba to be the domain master then I suggest you also set +the "os level" high enough to make sure it wins elections, and set +"preferred master" to "yes", to get samba to force an election on +startup.</P +><P +>Note that all your servers (including samba) and clients should be +using a WINS server to resolve NetBIOS names. If your clients are only +using broadcasting to resolve NetBIOS names, then two things will occur:</P ><P -><A -HREF="smb.conf.5.html#LDAPSSL" -TARGET="_top" ->ldap ssl</A ></P -></LI +><OL +TYPE="1" ><LI ><P -><A -HREF="smb.conf.5.html#LDAPSERVER" -TARGET="_top" ->ldap server</A -></P +> your local master browsers will be unable to find a domain master + browser, as it will only be looking on the local subnet. + </P ></LI ><LI ><P -><A -HREF="smb.conf.5.html#LDAPADMINDN" -TARGET="_top" ->ldap admin dn</A -></P +> if a client happens to get hold of a domain-wide browse list, and + a user attempts to access a host in that list, it will be unable to + resolve the NetBIOS name of that host. + </P ></LI -><LI +></OL +><P +>If, however, both samba and your clients are using a WINS server, then:</P ><P -><A -HREF="smb.conf.5.html#LDAPSUFFIX" -TARGET="_top" ->ldap suffix</A ></P -></LI +><OL +TYPE="1" ><LI ><P -><A -HREF="smb.conf.5.html#LDAPFILTER" -TARGET="_top" ->ldap filter</A -></P +> your local master browsers will contact the WINS server and, as long as + samba has registered that it is a domain master browser with the WINS + server, your local master browser will receive samba's ip address + as its domain master browser. + </P ></LI ><LI ><P -><A -HREF="smb.conf.5.html#LDAPPORT" -TARGET="_top" ->ldap port</A -></P +> when a client receives a domain-wide browse list, and a user attempts + to access a host in that list, it will contact the WINS server to + resolve the NetBIOS name of that host. as long as that host has + registered its NetBIOS name with the same WINS server, the user will + be able to see that host. + </P ></LI -></UL -><P ->These are described in the <A -HREF="smb.conf.5.html" -TARGET="_top" ->smb.conf(5)</A -> man -page and so will not be repeated here. However, a sample smb.conf file for -use with an LDAP directory could appear as</P -><P -><PRE -CLASS="PROGRAMLISTING" ->## /usr/local/samba/lib/smb.conf -[global] - security = user - encrypt passwords = yes - - netbios name = TASHTEGO - workgroup = NARNIA - - # ldap related parameters - - # define the DN to use when binding to the directory servers - # The password for this DN is not stored in smb.conf. Rather it - # must be set by using 'smbpasswd -w <TT -CLASS="REPLACEABLE" -><I ->secretpw</I -></TT ->' to store the - # passphrase in the secrets.tdb file. If the "ldap admin dn" values - # changes, this password will need to be reset. - ldap admin dn = "cn=Samba Manager,ou=people,dc=samba,dc=org" - - # specify the LDAP server's hostname (defaults to locahost) - ldap server = ahab.samba.org - - # Define the SSL option when connecting to the directory - # ('off', 'start tls', or 'on' (default)) - ldap ssl = start tls - - # define the port to use in the LDAP session (defaults to 636 when - # "ldap ssl = on") - ldap port = 389 - - # specify the base DN to use when searching the directory - ldap suffix = "ou=people,dc=samba,dc=org" - - # generally the default ldap search filter is ok - # ldap filter = "(&(uid=%u)(objectclass=sambaAccount))"</PRE -></P -></DIV +></OL ></DIV ><DIV CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN2777" +NAME="AEN2834" ></A ->19.6. Accounts and Groups management</H2 +>15.10. Note about broadcast addresses</H2 ><P ->As users accounts are managed thru the sambaAccount objectclass, you should -modify you existing administration tools to deal with sambaAccount attributes.</P -><P ->Machines accounts are managed with the sambaAccount objectclass, just -like users accounts. However, it's up to you to stored thoses accounts -in a different tree of you LDAP namespace: you should use -"ou=Groups,dc=plainjoe,dc=org" to store groups and -"ou=People,dc=plainjoe,dc=org" to store users. Just configure your -NSS and PAM accordingly (usually, in the /etc/ldap.conf configuration -file).</P -><P ->In Samba release 2.2.3, the group management system is based on posix -groups. This meand that Samba make usage of the posixGroup objectclass. -For now, there is no NT-like group system management (global and local -groups).</P +>If your network uses a "0" based broadcast address (for example if it +ends in a 0) then you will strike problems. Windows for Workgroups +does not seem to support a 0's broadcast and you will probably find +that browsing and name lookups won't work.</P ></DIV ><DIV CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN2782" +NAME="AEN2837" ></A ->19.7. Security and sambaAccount</H2 -><P ->There are two important points to remember when discussing the security -of sambaAccount entries in the directory.</P +>15.11. Multiple interfaces</H2 ><P -></P -><UL -><LI +>Samba now supports machines with multiple network interfaces. If you +have multiple interfaces then you will need to use the "interfaces" +option in smb.conf to configure them. See smb.conf(5) for details.</P +></DIV +></DIV +><DIV +CLASS="CHAPTER" +><HR><H1 +><A +NAME="VFS" +></A +>Chapter 16. Stackable VFS modules</H1 +><DIV +CLASS="SECT1" +><H2 +CLASS="SECT1" +><A +NAME="AEN2855" +></A +>16.1. Introduction and configuration</H2 ><P -><SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->Never</I -></SPAN -> retrieve the lmPassword or - ntPassword attribute values over an unencrypted LDAP session.</P -></LI -><LI +>Since samba 3.0, samba supports stackable VFS(Virtual File System) modules. +Samba passes each request to access the unix file system thru the loaded VFS modules. +This chapter covers all the modules that come with the samba source and references to +some external modules.</P ><P -><SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->Never</I -></SPAN -> allow non-admin users to - view the lmPassword or ntPassword attribute values.</P -></LI -></UL -><P ->These password hashes are clear text equivalents and can be used to impersonate -the user without deriving the original clear text strings. For more information -on the details of LM/NT password hashes, refer to the <A -HREF="ENCRYPTION.html" -TARGET="_top" ->ENCRYPTION chapter</A -> of the Samba-HOWTO-Collection.</P +>You may have problems to compile these modules, as shared libraries are +compiled and linked in different ways on different systems. +They currently have been tested against GNU/linux and IRIX.</P ><P ->To remedy the first security issue, the "ldap ssl" smb.conf parameter defaults -to require an encrypted session (<B -CLASS="COMMAND" ->ldap ssl = on</B ->) using -the default port of 636 -when contacting the directory server. When using an OpenLDAP 2.0 server, it -is possible to use the use the StartTLS LDAP extended operation in the place of -LDAPS. In either case, you are strongly discouraged to disable this security -(<B +>To use the VFS modules, create a share similar to the one below. The +important parameter is the <B CLASS="COMMAND" ->ldap ssl = off</B ->).</P -><P ->Note that the LDAPS protocol is deprecated in favor of the LDAPv3 StartTLS -extended operation. However, the OpenLDAP library still provides support for -the older method of securing communication between clients and servers.</P -><P ->The second security precaution is to prevent non-administrative users from -harvesting password hashes from the directory. This can be done using the -following ACL in <TT -CLASS="FILENAME" ->slapd.conf</TT ->:</P -><P -><PRE +>vfs object</B +> parameter which must point to +the exact pathname of the shared library objects. For example, to log all access +to files and use a recycle bin: + +<PRE CLASS="PROGRAMLISTING" ->## allow the "ldap admin dn" access, but deny everyone else -access to attrs=lmPassword,ntPassword - by dn="cn=Samba Admin,ou=people,dc=plainjoe,dc=org" write - by * none</PRE +> [audit] + comment = Audited /data directory + path = /data + vfs object = /path/to/audit.so /path/to/recycle.so + writeable = yes + browseable = yes</PRE ></P +><P +>The modules are used in the order they are specified.</P +><P +>Further documentation on writing VFS modules for Samba can be found in +the Samba Developers Guide.</P ></DIV ><DIV CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN2802" +NAME="AEN2864" ></A ->19.8. LDAP specials attributes for sambaAccounts</H2 -><P ->The sambaAccount objectclass is composed of the following attributes:</P +>16.2. Included modules</H2 +><DIV +CLASS="SECT2" +><H3 +CLASS="SECT2" +><A +NAME="AEN2866" +></A +>16.2.1. audit</H3 ><P +>A simple module to audit file access to the syslog +facility. The following operations are logged: +<P ></P -><UL -><LI -><P -><TT -CLASS="CONSTANT" ->lmPassword</TT ->: the LANMAN password 16-byte hash stored as a character - representation of a hexidecimal string.</P -></LI -><LI -><P -><TT -CLASS="CONSTANT" ->ntPassword</TT ->: the NT password hash 16-byte stored as a character - representation of a hexidecimal string.</P -></LI -><LI -><P -><TT -CLASS="CONSTANT" ->pwdLastSet</TT ->: The integer time in seconds since 1970 when the - <TT -CLASS="CONSTANT" ->lmPassword</TT -> and <TT -CLASS="CONSTANT" ->ntPassword</TT -> attributes were last set. - </P -></LI -><LI -><P -><TT -CLASS="CONSTANT" ->acctFlags</TT ->: string of 11 characters surrounded by square brackets [] - representing account flags such as U (user), W(workstation), X(no password expiration), and - D(disabled).</P -></LI -><LI -><P -><TT -CLASS="CONSTANT" ->logonTime</TT ->: Integer value currently unused</P -></LI -><LI -><P -><TT -CLASS="CONSTANT" ->logoffTime</TT ->: Integer value currently unused</P -></LI -><LI -><P -><TT -CLASS="CONSTANT" ->kickoffTime</TT ->: Integer value currently unused</P -></LI -><LI +><TABLE +BORDER="0" +><TBODY +><TR +><TD +>share</TD +></TR +><TR +><TD +>connect/disconnect</TD +></TR +><TR +><TD +>directory opens/create/remove</TD +></TR +><TR +><TD +>file open/close/rename/unlink/chmod</TD +></TR +></TBODY +></TABLE ><P -><TT -CLASS="CONSTANT" ->pwdCanChange</TT ->: Integer value currently unused</P -></LI -><LI +></P +></P +></DIV +><DIV +CLASS="SECT2" +><HR><H3 +CLASS="SECT2" +><A +NAME="AEN2874" +></A +>16.2.2. recycle</H3 ><P -><TT -CLASS="CONSTANT" ->pwdMustChange</TT ->: Integer value currently unused</P -></LI -><LI +>A recycle-bin like modules. When used any unlink call +will be intercepted and files moved to the recycle +directory instead of beeing deleted.</P ><P -><TT -CLASS="CONSTANT" ->homeDrive</TT ->: specifies the drive letter to which to map the - UNC path specified by homeDirectory. The drive letter must be specified in the form "X:" - where X is the letter of the drive to map. Refer to the "logon drive" parameter in the - smb.conf(5) man page for more information.</P -></LI -><LI +>Supported options: +<P +></P +><DIV +CLASS="VARIABLELIST" +><DL +><DT +>vfs_recycle_bin:repository</DT +><DD ><P -><TT -CLASS="CONSTANT" ->scriptPath</TT ->: The scriptPath property specifies the path of - the user's logon script, .CMD, .EXE, or .BAT file. The string can be null. The path - is relative to the netlogon share. Refer to the "logon script" parameter in the - smb.conf(5) man page for more information.</P -></LI -><LI +>FIXME</P +></DD +><DT +>vfs_recycle_bin:keeptree</DT +><DD ><P -><TT -CLASS="CONSTANT" ->profilePath</TT ->: specifies a path to the user's profile. - This value can be a null string, a local absolute path, or a UNC path. Refer to the - "logon path" parameter in the smb.conf(5) man page for more information.</P -></LI -><LI +>FIXME</P +></DD +><DT +>vfs_recycle_bin:versions</DT +><DD ><P -><TT -CLASS="CONSTANT" ->smbHome</TT ->: The homeDirectory property specifies the path of - the home directory for the user. The string can be null. If homeDrive is set and specifies - a drive letter, homeDirectory should be a UNC path. The path must be a network - UNC path of the form \\server\share\directory. This value can be a null string. - Refer to the "logon home" parameter in the smb.conf(5) man page for more information. - </P -></LI -><LI +>FIXME</P +></DD +><DT +>vfs_recycle_bin:touch</DT +><DD ><P -><TT -CLASS="CONSTANT" ->userWorkstation</TT ->: character string value currently unused. - </P -></LI -><LI +>FIXME</P +></DD +><DT +>vfs_recycle_bin:maxsize</DT +><DD ><P -><TT -CLASS="CONSTANT" ->rid</TT ->: the integer representation of the user's relative identifier - (RID).</P -></LI -><LI +>FIXME</P +></DD +><DT +>vfs_recycle_bin:exclude</DT +><DD ><P -><TT -CLASS="CONSTANT" ->primaryGroupID</TT ->: the relative identifier (RID) of the primary group - of the user.</P -></LI -></UL +>FIXME</P +></DD +><DT +>vfs_recycle_bin:exclude_dir</DT +><DD ><P ->The majority of these parameters are only used when Samba is acting as a PDC of -a domain (refer to the <A -HREF="Samba-PDC-HOWTO.html" -TARGET="_top" ->Samba-PDC-HOWTO</A -> for details on -how to configure Samba as a Primary Domain Controller). The following four attributes -are only stored with the sambaAccount entry if the values are non-default values:</P +>FIXME</P +></DD +><DT +>vfs_recycle_bin:noversions</DT +><DD ><P +>FIXME</P +></DD +></DL +></DIV ></P -><UL -><LI -><P ->smbHome</P -></LI -><LI -><P ->scriptPath</P -></LI -><LI +></DIV +><DIV +CLASS="SECT2" +><HR><H3 +CLASS="SECT2" +><A +NAME="AEN2911" +></A +>16.2.3. netatalk</H3 ><P ->logonPath</P -></LI -><LI +>A netatalk module, that will ease co-existence of samba and +netatalk file sharing services.</P ><P ->homeDrive</P -></LI -></UL +>Advantages compared to the old netatalk module: +<P +></P +><TABLE +BORDER="0" +><TBODY +><TR +><TD +>it doesn't care about creating of .AppleDouble forks, just keeps ones in sync</TD +></TR +><TR +><TD +>if share in smb.conf doesn't contain .AppleDouble item in hide or veto list, it will be added automatically</TD +></TR +></TBODY +></TABLE ><P ->These attributes are only stored with the sambaAccount entry if -the values are non-default values. For example, assume TASHTEGO has now been -configured as a PDC and that <B -CLASS="COMMAND" ->logon home = \\%L\%u</B -> was defined in -its <TT -CLASS="FILENAME" ->smb.conf</TT -> file. When a user named "becky" logons to the domain, -the <TT -CLASS="PARAMETER" -><I ->logon home</I -></TT -> string is expanded to \\TASHTEGO\becky. -If the smbHome attribute exists in the entry "uid=becky,ou=people,dc=samba,dc=org", -this value is used. However, if this attribute does not exist, then the value -of the <TT -CLASS="PARAMETER" -><I ->logon home</I -></TT -> parameter is used in its place. Samba -will only write the attribute value to the directory entry is the value is -something other than the default (e.g. \\MOBY\becky).</P +></P +></P +></DIV ></DIV ><DIV CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN2872" +NAME="AEN2918" ></A ->19.9. Example LDIF Entries for a sambaAccount</H2 +>16.3. VFS modules available elsewhere</H2 ><P ->The following is a working LDIF with the inclusion of the posixAccount objectclass:</P +>This section contains a listing of various other VFS modules that +have been posted but don't currently reside in the Samba CVS +tree for one reason ot another (e.g. it is easy for the maintainer +to have his or her own CVS tree).</P ><P -><PRE -CLASS="PROGRAMLISTING" ->dn: uid=guest2, ou=people,dc=plainjoe,dc=org -ntPassword: 878D8014606CDA29677A44EFA1353FC7 -pwdMustChange: 2147483647 -primaryGroupID: 1201 -lmPassword: 552902031BEDE9EFAAD3B435B51404EE -pwdLastSet: 1010179124 -logonTime: 0 -objectClass: sambaAccount -uid: guest2 -kickoffTime: 2147483647 -acctFlags: [UX ] -logoffTime: 2147483647 -rid: 19006 -pwdCanChange: 0</PRE +>No statemets about the stability or functionality any module +should be implied due to its presence here.</P +><DIV +CLASS="SECT2" +><HR><H3 +CLASS="SECT2" +><A +NAME="AEN2922" +></A +>16.3.1. DatabaseFS</H3 +><P +>URL: <A +HREF="http://www.css.tayloru.edu/~elorimer/databasefs/index.php" +TARGET="_top" +>http://www.css.tayloru.edu/~elorimer/databasefs/index.php</A ></P ><P ->The following is an LDIF entry for using both the sambaAccount and -posixAccount objectclasses:</P +>By <A +HREF="mailto:elorimer@css.tayloru.edu" +TARGET="_top" +>Eric Lorimer</A +>.</P ><P -><PRE -CLASS="PROGRAMLISTING" ->dn: uid=gcarter, ou=people,dc=plainjoe,dc=org -logonTime: 0 -displayName: Gerald Carter -lmPassword: 552902031BEDE9EFAAD3B435B51404EE -primaryGroupID: 1201 -objectClass: posixAccount -objectClass: sambaAccount -acctFlags: [UX ] -userPassword: {crypt}BpM2ej8Rkzogo -uid: gcarter -uidNumber: 9000 -cn: Gerald Carter -loginShell: /bin/bash -logoffTime: 2147483647 -gidNumber: 100 -kickoffTime: 2147483647 -pwdLastSet: 1010179230 -rid: 19000 -homeDirectory: /home/tashtego/gcarter -pwdCanChange: 0 -pwdMustChange: 2147483647 -ntPassword: 878D8014606CDA29677A44EFA1353FC7</PRE -></P +>I have created a VFS module which implements a fairly complete read-only +filesystem. It presents information from a database as a filesystem in +a modular and generic way to allow different databases to be used +(originally designed for organizing MP3s under directories such as +"Artists," "Song Keywords," etc... I have since applied it to a student +roster database very easily). The directory structure is stored in the +database itself and the module makes no assumptions about the database +structure beyond the table it requires to run.</P +><P +>Any feedback would be appreciated: comments, suggestions, patches, +etc... If nothing else, hopefully it might prove useful for someone +else who wishes to create a virtual filesystem.</P ></DIV ><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" +CLASS="SECT2" +><HR><H3 +CLASS="SECT2" ><A -NAME="AEN2880" +NAME="AEN2930" ></A ->19.10. Comments</H2 +>16.3.2. vscan</H3 ><P ->Please mail all comments regarding this HOWTO to <A -HREF="mailto:jerry@samba.org" +>URL: <A +HREF="http://www.openantivirus.org/" TARGET="_top" ->jerry@samba.org</A ->. This documents was -last updated to reflect the Samba 2.2.3 release. </P +>http://www.openantivirus.org/</A +></P +><P +>samba-vscan is a proof-of-concept module for Samba, which +uses the VFS (virtual file system) features of Samba 2.2.x/3.0 +alphaX. Of couse, Samba has to be compiled with VFS support. +samba-vscan supports various virus scanners and is maintained +by Rainer Link.</P +></DIV ></DIV ></DIV ><DIV @@ -14404,15 +14586,15 @@ CLASS="CHAPTER" ><A NAME="CVS-ACCESS" ></A ->Chapter 20. HOWTO Access Samba source code via CVS</H1 +>Chapter 17. Access Samba source code via CVS</H1 ><DIV CLASS="SECT1" ><H2 CLASS="SECT1" ><A -NAME="AEN2891" +NAME="AEN2942" ></A ->20.1. Introduction</H2 +>17.1. Introduction</H2 ><P >Samba is developed in an open environment. Developers use CVS (Concurrent Versioning System) to "checkin" (also known as @@ -14432,9 +14614,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN2896" +NAME="AEN2947" ></A ->20.2. CVS Access to samba.org</H2 +>17.2. CVS Access to samba.org</H2 ><P >The machine samba.org runs a publicly accessible CVS repository for access to the source code of several packages, @@ -14445,9 +14627,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN2899" +NAME="AEN2950" ></A ->20.2.1. Access via CVSweb</H3 +>17.2.1. Access via CVSweb</H3 ><P >You can access the source code via your favourite WWW browser. This allows you to access the contents of @@ -14466,9 +14648,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN2904" +NAME="AEN2955" ></A ->20.2.2. Access via cvs</H3 +>17.2.2. Access via cvs</H3 ><P >You can also access the source code via a normal cvs client. This gives you much more control over you can @@ -14576,7 +14758,7 @@ CLASS="CHAPTER" ><A NAME="GROUPMAPPING" ></A ->Chapter 21. Group mapping HOWTO</H1 +>Chapter 18. Group mapping HOWTO</H1 ><P > Starting with Samba 3.0 alpha 2, a new group mapping function is available. The @@ -14677,15 +14859,15 @@ CLASS="CHAPTER" ><A NAME="SPEED" ></A ->Chapter 22. Samba performance issues</H1 +>Chapter 19. Samba performance issues</H1 ><DIV CLASS="SECT1" ><H2 CLASS="SECT1" ><A -NAME="AEN2982" +NAME="AEN3033" ></A ->22.1. Comparisons</H2 +>19.1. Comparisons</H2 ><P >The Samba server uses TCP to talk to the client. Thus if you are trying to see if it performs well you should really compare it to @@ -14714,98 +14896,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN2988" -></A ->22.2. Oplocks</H2 -><DIV -CLASS="SECT2" -><H3 -CLASS="SECT2" -><A -NAME="AEN2990" -></A ->22.2.1. Overview</H3 -><P ->Oplocks are the way that SMB clients get permission from a server to -locally cache file operations. If a server grants an oplock -(opportunistic lock) then the client is free to assume that it is the -only one accessing the file and it will agressively cache file -data. With some oplock types the client may even cache file open/close -operations. This can give enormous performance benefits.</P -><P ->With the release of Samba 1.9.18 we now correctly support opportunistic -locks. This is turned on by default, and can be turned off on a share- -by-share basis by setting the parameter :</P -><P -><B -CLASS="COMMAND" ->oplocks = False</B -></P -><P ->We recommend that you leave oplocks on however, as current benchmark -tests with NetBench seem to give approximately a 30% improvement in -speed with them on. This is on average however, and the actual -improvement seen can be orders of magnitude greater, depending on -what the client redirector is doing.</P -><P ->Previous to Samba 1.9.18 there was a 'fake oplocks' option. This -option has been left in the code for backwards compatibility reasons -but it's use is now deprecated. A short summary of what the old -code did follows.</P -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN2998" -></A ->22.2.2. Level2 Oplocks</H3 -><P ->With Samba 2.0.5 a new capability - level2 (read only) oplocks is -supported (although the option is off by default - see the smb.conf -man page for details). Turning on level2 oplocks (on a share-by-share basis) -by setting the parameter :</P -><P -><B -CLASS="COMMAND" ->level2 oplocks = true</B -></P -><P ->should speed concurrent access to files that are not commonly written -to, such as application serving shares (ie. shares that contain common -.EXE files - such as a Microsoft Office share) as it allows clients to -read-ahread cache copies of these files.</P -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN3004" -></A ->22.2.3. Old 'fake oplocks' option - deprecated</H3 -><P ->Samba can also fake oplocks, by granting a oplock whenever a client -asks for one. This is controlled using the smb.conf option "fake -oplocks". If you set "fake oplocks = yes" then you are telling the -client that it may agressively cache the file data for all opens.</P -><P ->Enabling 'fake oplocks' on all read-only shares or shares that you know -will only be accessed from one client at a time you will see a big -performance improvement on many operations. If you enable this option -on shares where multiple clients may be accessing the files read-write -at the same time you can get data corruption.</P -></DIV -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN3008" +NAME="AEN3039" ></A ->22.3. Socket options</H2 +>19.2. Socket options</H2 ><P >There are a number of socket options that can greatly affect the performance of a TCP based server like Samba.</P @@ -14831,9 +14924,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN3015" +NAME="AEN3046" ></A ->22.4. Read size</H2 +>19.3. Read size</H2 ><P >The option "read size" affects the overlap of disk reads/writes with network reads/writes. If the amount of data being transferred in @@ -14857,9 +14950,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN3020" +NAME="AEN3051" ></A ->22.5. Max xmit</H2 +>19.4. Max xmit</H2 ><P >At startup the client and server negotiate a "maximum transmit" size, which limits the size of nearly all SMB commands. You can set the @@ -14880,56 +14973,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN3025" -></A ->22.6. Locking</H2 -><P ->By default Samba does not implement strict locking on each read/write -call (although it did in previous versions). If you enable strict -locking (using "strict locking = yes") then you may find that you -suffer a severe performance hit on some systems.</P -><P ->The performance hit will probably be greater on NFS mounted -filesystems, but could be quite high even on local disks.</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN3029" -></A ->22.7. Share modes</H2 -><P ->Some people find that opening files is very slow. This is often -because of the "share modes" code needed to fully implement the dos -share modes stuff. You can disable this code using "share modes = -no". This will gain you a lot in opening and closing files but will -mean that (in some cases) the system won't force a second user of a -file to open the file read-only if the first has it open -read-write. For many applications that do their own locking this -doesn't matter, but for some it may. Most Windows applications -depend heavily on "share modes" working correctly and it is -recommended that the Samba share mode support be left at the -default of "on".</P -><P ->The share mode code in Samba has been re-written in the 1.9.17 -release following tests with the Ziff-Davis NetBench PC Benchmarking -tool. It is now believed that Samba 1.9.17 implements share modes -similarly to Windows NT.</P -><P ->NOTE: In the most recent versions of Samba there is an option to use -shared memory via mmap() to implement the share modes. This makes -things much faster. See the Makefile for how to enable this.</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN3034" +NAME="AEN3056" ></A ->22.8. Log level</H2 +>19.5. Log level</H2 ><P >If you set the log level (also known as "debug level") higher than 2 then you may suffer a large drop in performance. This is because the @@ -14941,23 +14987,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN3037" -></A ->22.9. Wide lines</H2 -><P ->The "wide links" option is now enabled by default, but if you disable -it (for better security) then you may suffer a performance hit in -resolving filenames. The performance loss is lessened if you have -"getwd cache = yes", which is now the default.</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN3040" +NAME="AEN3059" ></A ->22.10. Read raw</H2 +>19.6. Read raw</H2 ><P >The "read raw" operation is designed to be an optimised, low-latency file read operation. A server may choose to not support it, @@ -14977,9 +15009,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN3045" +NAME="AEN3064" ></A ->22.11. Write raw</H2 +>19.7. Write raw</H2 ><P >The "write raw" operation is designed to be an optimised, low-latency file write operation. A server may choose to not support it, @@ -14994,56 +15026,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN3049" -></A ->22.12. Read prediction</H2 -><P ->Samba can do read prediction on some of the SMB commands. Read -prediction means that Samba reads some extra data on the last file it -read while waiting for the next SMB command to arrive. It can then -respond more quickly when the next read request arrives.</P -><P ->This is disabled by default. You can enable it by using "read -prediction = yes".</P -><P ->Note that read prediction is only used on files that were opened read -only.</P -><P ->Read prediction should particularly help for those silly clients (such -as "Write" under NT) which do lots of very small reads on a file.</P -><P ->Samba will not read ahead more data than the amount specified in the -"read size" option. It always reads ahead on 1k block boundaries.</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN3056" -></A ->22.13. Memory mapping</H2 -><P ->Samba supports reading files via memory mapping them. One some -machines this can give a large boost to performance, on others it -makes not difference at all, and on some it may reduce performance.</P -><P ->To enable you you have to recompile Samba with the -DUSE_MMAP option -on the FLAGS line of the Makefile.</P -><P ->Note that memory mapping is only used on files opened read only, and -is not used by the "read raw" operation. Thus you may find memory -mapping is more effective if you disable "read raw" using "read raw = -no".</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN3061" +NAME="AEN3068" ></A ->22.14. Slow Clients</H2 +>19.8. Slow Clients</H2 ><P >One person has reported that setting the protocol to COREPLUS rather than LANMAN2 gave a dramatic speed improvement (from 10k/s to 150k/s).</P @@ -15058,9 +15043,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN3065" +NAME="AEN3072" ></A ->22.15. Slow Logins</H2 +>19.9. Slow Logins</H2 ><P >Slow logins are almost always due to the password checking time. Using the lowest practical "password level" will improve things a lot. You @@ -15071,9 +15056,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN3068" +NAME="AEN3075" ></A ->22.16. Client tuning</H2 +>19.10. Client tuning</H2 ><P >Often a speed problem can be traced to the client. The client (for example Windows for Workgroups) can often be tuned for better TCP @@ -15148,11 +15133,13 @@ turned out I was better off without any!!!!!</P and a DX2-66 20MB server with a crappy NE2000 compatible and old IDE drive (Kernel 2.0.30). The transfer rate was reasonable for 10 baseT.</P ><P ->FIXME -The figures are: Put Get +><PRE +CLASS="PROGRAMLISTING" +>The figures are: Put Get P166 client 3Com card: 420-440kB/s 500-520kB/s P100 client 3Com card: 390-410kB/s 490-510kB/s -DX4-75 client NE2000: 370-380kB/s 330-350kB/s</P +DX4-75 client NE2000: 370-380kB/s 330-350kB/s</PRE +></P ><P >I based these test on transfer two files a 4.5MB text file and a 15MB textfile. The results arn't bad considering the hardware Samba is @@ -15170,41 +15157,442 @@ upwards). I suppose there is more going on in the samba protocol, but if it could get up to the rate of FTP the perfomance would be quite staggering.</P ></DIV +></DIV +><DIV +CLASS="CHAPTER" +><HR><H1 +><A +NAME="GROUPPROFILES" +></A +>Chapter 20. Creating Group Profiles</H1 +><DIV +CLASS="SECT1" +><H2 +CLASS="SECT1" +><A +NAME="AEN3123" +></A +>20.1. Windows '9x</H2 +><P +>You need the Win98 Group Policy Editor to +set Group Profiles up under Windows '9x. It can be found on the Original +full product Win98 installation CD under +<TT +CLASS="FILENAME" +>tools/reskit/netadmin/poledit</TT +>. You install this +using the Add/Remove Programs facility and then click on the 'Have Disk' +tab.</P +><P +>Use the Group Policy Editor to create a policy file that specifies the +location of user profiles and/or the <TT +CLASS="FILENAME" +>My Documents</TT +> etc. +stuff. You then save these settings in a file called +<TT +CLASS="FILENAME" +>Config.POL</TT +> that needs to be placed in +the root of the [NETLOGON] share. If your Win98 is configured to log onto +the Samba Domain, it will automatically read this file and update the +Win98 registry of the machine that is logging on.</P +><P +>All of this is covered in the Win98 Resource Kit documentation.</P +><P +>If you do not do it this way, then every so often Win98 will check the +integrity of the registry and will restore it's settings from the back-up +copy of the registry it stores on each Win98 machine. Hence, you will notice +things changing back to the original settings.</P +></DIV ><DIV CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN3100" +NAME="AEN3132" +></A +>20.2. Windows NT 4</H2 +><P +>Unfortunately, the Resource Kit info is Win NT4/2K version specific.</P +><P +>Here is a quick guide:</P +><P +></P +><UL +><LI +><P +>On your NT4 Domain Controller, right click on 'My Computer', then +select the tab labelled 'User Profiles'.</P +></LI +><LI +><P +>Select a user profile you want to migrate and click on it.</P +><DIV +CLASS="NOTE" +><P +></P +><TABLE +CLASS="NOTE" +WIDTH="90%" +BORDER="0" +><TR +><TD +WIDTH="25" +ALIGN="CENTER" +VALIGN="TOP" +><IMG +SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif" +HSPACE="5" +ALT="Note"></TD +><TD +ALIGN="LEFT" +VALIGN="TOP" +><P +>I am using the term "migrate" lossely. You can copy a profile to +create a group profile. You can give the user 'Everyone' rights to the +profile you copy this to. That is what you need to do, since your samba +domain is not a member of a trust relationship with your NT4 PDC.</P +></TD +></TR +></TABLE +></DIV +></LI +><LI +><P +>Click the 'Copy To' button.</P +></LI +><LI +><P +>In the box labelled 'Copy Profile to' add your new path, eg: +<TT +CLASS="FILENAME" +>c:\temp\foobar</TT +></P +></LI +><LI +><P +>Click on the button labelled 'Change' in the "Permitted to use" box.</P +></LI +><LI +><P +>Click on the group 'Everyone' and then click OK. This closes the +'chose user' box.</P +></LI +><LI +><P +>Now click OK.</P +></LI +></UL +><P +>Follow the above for every profile you need to migrate.</P +><DIV +CLASS="SECT2" +><HR><H3 +CLASS="SECT2" +><A +NAME="AEN3155" +></A +>20.2.1. Side bar Notes</H3 +><P +>You should obtain the SID of your NT4 domain. You can use smbpasswd to do +this. Read the man page.</P +><P +>With Samba-3.0.0 alpha code you can import all you NT4 domain accounts +using the net samsync method. This way you can retain your profile +settings as well as all your users.</P +></DIV +><DIV +CLASS="SECT2" +><HR><H3 +CLASS="SECT2" +><A +NAME="AEN3159" +></A +>20.2.2. Mandatory profiles</H3 +><P +>The above method can be used to create mandatory profiles also. To convert +a group profile into a mandatory profile simply locate the NTUser.DAT file +in the copied profile and rename it to NTUser.MAN.</P +></DIV +><DIV +CLASS="SECT2" +><HR><H3 +CLASS="SECT2" +><A +NAME="AEN3162" ></A ->22.17. My Results</H2 +>20.2.3. moveuser.exe</H3 ><P ->Some people want to see real numbers in a document like this, so here -they are. I have a 486sx33 client running WfWg 3.11 with the 3.11b -tcp/ip stack. It has a slow IDE drive and 20Mb of ram. It has a SMC -Elite-16 ISA bus ethernet card. The only WfWg tuning I've done is to -set DefaultRcvWindow in the [MSTCP] section of system.ini to 16384. My -server is a 486dx3-66 running Linux. It also has 20Mb of ram and a SMC -Elite-16 card. You can see my server config in the examples/tridge/ -subdirectory of the distribution.</P +>The W2K professional resource kit has moveuser.exe. moveuser.exe changes +the security of a profile from one user to another. This allows the account +domain to change, and/or the user name to change.</P +></DIV +><DIV +CLASS="SECT2" +><HR><H3 +CLASS="SECT2" +><A +NAME="AEN3165" +></A +>20.2.4. Get SID</H3 ><P ->I get 490k/s on reading a 8Mb file with copy. -I get 441k/s writing the same file to the samba server.</P +>You can identify the SID by using GetSID.exe from the Windows NT Server 4.0 +Resource Kit.</P ><P ->Of course, there's a lot more to benchmarks than 2 raw throughput -figures, but it gives you a ballpark figure.</P +>Windows NT 4.0 stores the local profile information in the registry under +the following key: +HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList</P ><P ->I've also tested Win95 and WinNT, and found WinNT gave me the best -speed as a samba client. The fastest client of all (for me) is -smbclient running on another linux box. Maybe I'll add those results -here someday ...</P +>Under the ProfileList key, there will be subkeys named with the SIDs of the +users who have logged on to this computer. (To find the profile information +for the user whose locally cached profile you want to move, find the SID for +the user with the GetSID.exe utility.) Inside of the appropriate user's +subkey, you will see a string value named ProfileImagePath.</P +></DIV +></DIV +><DIV +CLASS="SECT1" +><HR><H2 +CLASS="SECT1" +><A +NAME="AEN3170" +></A +>20.3. Windows 2000/XP</H2 +><P +>You must first convert the profile from a local profile to a domain +profile on the MS Windows workstation as follows:</P +><P +></P +><UL +><LI +><P +>Log on as the LOCAL workstation administrator.</P +></LI +><LI +><P +>Right click on the 'My Computer' Icon, select 'Properties'</P +></LI +><LI +><P +>Click on the 'User Profiles' tab</P +></LI +><LI +><P +>Select the profile you wish to convert (click on it once)</P +></LI +><LI +><P +>Click on the button 'Copy To'</P +></LI +><LI +><P +>In the "Permitted to use" box, click on the 'Change' button.</P +></LI +><LI +><P +>Click on the 'Look in" area that lists the machine name, when you click +here it will open up a selection box. Click on the domain to which the +profile must be accessible.</P +><DIV +CLASS="NOTE" +><P +></P +><TABLE +CLASS="NOTE" +WIDTH="90%" +BORDER="0" +><TR +><TD +WIDTH="25" +ALIGN="CENTER" +VALIGN="TOP" +><IMG +SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif" +HSPACE="5" +ALT="Note"></TD +><TD +ALIGN="LEFT" +VALIGN="TOP" +><P +>You will need to log on if a logon box opens up. Eg: In the connect +as: MIDEARTH\root, password: mypassword.</P +></TD +></TR +></TABLE +></DIV +></LI +><LI +><P +>To make the profile capable of being used by anyone select 'Everyone'</P +></LI +><LI +><P +>Click OK. The Selection box will close.</P +></LI +><LI +><P +>Now click on the 'Ok' button to create the profile in the path you +nominated.</P +></LI +></UL +><P +>Done. You now have a profile that can be editted using the samba-3.0.0 +profiles tool.</P +><DIV +CLASS="NOTE" +><P +></P +><TABLE +CLASS="NOTE" +WIDTH="100%" +BORDER="0" +><TR +><TD +WIDTH="25" +ALIGN="CENTER" +VALIGN="TOP" +><IMG +SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif" +HSPACE="5" +ALT="Note"></TD +><TD +ALIGN="LEFT" +VALIGN="TOP" +><P +>Under NT/2K the use of mandotory profiles forces the use of MS Exchange +storage of mail data. That keeps desktop profiles usable.</P +></TD +></TR +></TABLE +></DIV +><DIV +CLASS="NOTE" +><P +></P +><TABLE +CLASS="NOTE" +WIDTH="100%" +BORDER="0" +><TR +><TD +WIDTH="25" +ALIGN="CENTER" +VALIGN="TOP" +><IMG +SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif" +HSPACE="5" +ALT="Note"></TD +><TD +ALIGN="LEFT" +VALIGN="TOP" +><P +></P +><UL +><LI +><P +>This is a security check new to Windows XP (or maybe only +Windows XP service pack 1). It can be disabled via a group policy in +Active Directory. The policy is:</P +><P +>"Computer Configuration\Administrative Templates\System\User +Profiles\Do not check for user ownership of Roaming Profile Folders"</P +><P +>...and it should be set to "Enabled". +Does the new version of samba have an Active Directory analogue? If so, +then you may be able to set the policy through this.</P +><P +>If you cannot set group policies in samba, then you may be able to set +the policy locally on each machine. If you want to try this, then do +the following (N.B. I don't know for sure that this will work in the +same way as a domain group policy):</P +></LI +><LI +><P +>On the XP workstation log in with an Administrator account.</P +></LI +><LI +><P +>Click: "Start", "Run"</P +></LI +><LI +><P +>Type: "mmc"</P +></LI +><LI +><P +>Click: "OK"</P +></LI +><LI +><P +>A Microsoft Management Console should appear.</P +></LI +><LI +><P +>Click: File, "Add/Remove Snap-in...", "Add"</P +></LI +><LI +><P +>Double-Click: "Group Policy"</P +></LI +><LI +><P +>Click: "Finish", "Close"</P +></LI +><LI +><P +>Click: "OK"</P +></LI +><LI +><P +>In the "Console Root" window:</P +></LI +><LI +><P +>Expand: "Local Computer Policy", "Computer Configuration",</P +></LI +><LI +><P +>"Administrative Templates", "System", "User Profiles"</P +></LI +><LI +><P +>Double-Click: "Do not check for user ownership of Roaming Profile</P +></LI +><LI +><P +>Folders"</P +></LI +><LI +><P +>Select: "Enabled"</P +></LI +><LI +><P +>Click: OK"</P +></LI +><LI +><P +>Close the whole console. You do not need to save the settings (this +refers to the console settings rather than the policies you have +changed).</P +></LI +><LI +><P +>Reboot</P +></LI +></UL +></TD +></TR +></TABLE +></DIV ></DIV ></DIV ></DIV ><DIV CLASS="PART" ><A -NAME="AEN3106" +NAME="APPENDIXES" ></A ><DIV CLASS="TITLEPAGE" @@ -15219,243 +15607,243 @@ CLASS="TOC" >Table of Contents</B ></DT ><DT ->23. <A +>21. <A HREF="#PORTABILITY" >Portability</A ></DT ><DD ><DL ><DT ->23.1. <A -HREF="#AEN3115" +>21.1. <A +HREF="#AEN3251" >HPUX</A ></DT ><DT ->23.2. <A -HREF="#AEN3121" +>21.2. <A +HREF="#AEN3257" >SCO Unix</A ></DT ><DT ->23.3. <A -HREF="#AEN3125" +>21.3. <A +HREF="#AEN3261" >DNIX</A ></DT ><DT ->23.4. <A -HREF="#AEN3154" +>21.4. <A +HREF="#AEN3290" >RedHat Linux Rembrandt-II</A ></DT ></DL ></DD ><DT ->24. <A +>22. <A HREF="#OTHER-CLIENTS" >Samba and other CIFS clients</A ></DT ><DD ><DL ><DT ->24.1. <A -HREF="#AEN3175" +>22.1. <A +HREF="#AEN3311" >Macintosh clients?</A ></DT ><DT ->24.2. <A -HREF="#AEN3184" +>22.2. <A +HREF="#AEN3320" >OS2 Client</A ></DT ><DD ><DL ><DT ->24.2.1. <A -HREF="#AEN3186" +>22.2.1. <A +HREF="#AEN3322" >How can I configure OS/2 Warp Connect or OS/2 Warp 4 as a client for Samba?</A ></DT ><DT ->24.2.2. <A -HREF="#AEN3201" +>22.2.2. <A +HREF="#AEN3337" >How can I configure OS/2 Warp 3 (not Connect), OS/2 1.2, 1.3 or 2.x for Samba?</A ></DT ><DT ->24.2.3. <A -HREF="#AEN3210" +>22.2.3. <A +HREF="#AEN3346" >Are there any other issues when OS/2 (any version) is used as a client?</A ></DT ><DT ->24.2.4. <A -HREF="#AEN3214" +>22.2.4. <A +HREF="#AEN3350" >How do I get printer driver download working for OS/2 clients?</A ></DT ></DL ></DD ><DT ->24.3. <A -HREF="#AEN3224" +>22.3. <A +HREF="#AEN3360" >Windows for Workgroups</A ></DT ><DD ><DL ><DT ->24.3.1. <A -HREF="#AEN3226" +>22.3.1. <A +HREF="#AEN3362" >Use latest TCP/IP stack from Microsoft</A ></DT ><DT ->24.3.2. <A -HREF="#AEN3231" +>22.3.2. <A +HREF="#AEN3367" >Delete .pwl files after password change</A ></DT ><DT ->24.3.3. <A -HREF="#AEN3236" +>22.3.3. <A +HREF="#AEN3372" >Configure WfW password handling</A ></DT ><DT ->24.3.4. <A -HREF="#AEN3240" +>22.3.4. <A +HREF="#AEN3376" >Case handling of passwords</A ></DT ></DL ></DD ><DT ->24.4. <A -HREF="#AEN3245" +>22.4. <A +HREF="#AEN3381" >Windows '95/'98</A ></DT ><DT ->24.5. <A -HREF="#AEN3261" +>22.5. <A +HREF="#AEN3397" >Windows 2000 Service Pack 2</A ></DT ></DL ></DD ><DT ->25. <A +>23. <A HREF="#BUGREPORT" >Reporting Bugs</A ></DT ><DD ><DL ><DT ->25.1. <A -HREF="#AEN3285" +>23.1. <A +HREF="#AEN3421" >Introduction</A ></DT ><DT ->25.2. <A -HREF="#AEN3295" +>23.2. <A +HREF="#AEN3431" >General info</A ></DT ><DT ->25.3. <A -HREF="#AEN3301" +>23.3. <A +HREF="#AEN3437" >Debug levels</A ></DT ><DT ->25.4. <A -HREF="#AEN3318" +>23.4. <A +HREF="#AEN3454" >Internal errors</A ></DT ><DT ->25.5. <A -HREF="#AEN3328" +>23.5. <A +HREF="#AEN3464" >Attaching to a running process</A ></DT ><DT ->25.6. <A -HREF="#AEN3331" +>23.6. <A +HREF="#AEN3467" >Patches</A ></DT ></DL ></DD ><DT ->26. <A +>24. <A HREF="#DIAGNOSIS" >Diagnosing your samba server</A ></DT ><DD ><DL ><DT ->26.1. <A -HREF="#AEN3354" +>24.1. <A +HREF="#AEN3490" >Introduction</A ></DT ><DT ->26.2. <A -HREF="#AEN3359" +>24.2. <A +HREF="#AEN3495" >Assumptions</A ></DT ><DT ->26.3. <A -HREF="#AEN3369" +>24.3. <A +HREF="#AEN3505" >Tests</A ></DT ><DD ><DL ><DT ->26.3.1. <A -HREF="#AEN3371" +>24.3.1. <A +HREF="#AEN3507" >Test 1</A ></DT ><DT ->26.3.2. <A -HREF="#AEN3377" +>24.3.2. <A +HREF="#AEN3513" >Test 2</A ></DT ><DT ->26.3.3. <A -HREF="#AEN3383" +>24.3.3. <A +HREF="#AEN3519" >Test 3</A ></DT ><DT ->26.3.4. <A -HREF="#AEN3398" +>24.3.4. <A +HREF="#AEN3534" >Test 4</A ></DT ><DT ->26.3.5. <A -HREF="#AEN3403" +>24.3.5. <A +HREF="#AEN3539" >Test 5</A ></DT ><DT ->26.3.6. <A -HREF="#AEN3409" +>24.3.6. <A +HREF="#AEN3545" >Test 6</A ></DT ><DT ->26.3.7. <A -HREF="#AEN3417" +>24.3.7. <A +HREF="#AEN3553" >Test 7</A ></DT ><DT ->26.3.8. <A -HREF="#AEN3443" +>24.3.8. <A +HREF="#AEN3579" >Test 8</A ></DT ><DT ->26.3.9. <A -HREF="#AEN3460" +>24.3.9. <A +HREF="#AEN3596" >Test 9</A ></DT ><DT ->26.3.10. <A -HREF="#AEN3468" +>24.3.10. <A +HREF="#AEN3604" >Test 10</A ></DT ><DT ->26.3.11. <A -HREF="#AEN3474" +>24.3.11. <A +HREF="#AEN3610" >Test 11</A ></DT ></DL ></DD ><DT ->26.4. <A -HREF="#AEN3479" +>24.4. <A +HREF="#AEN3615" >Still having troubles?</A ></DT ></DL @@ -15469,7 +15857,7 @@ CLASS="CHAPTER" ><A NAME="PORTABILITY" ></A ->Chapter 23. Portability</H1 +>Chapter 21. Portability</H1 ><P >Samba works on a wide range of platforms but the interface all the platforms provide is not always compatible. This chapter contains @@ -15479,9 +15867,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN3115" +NAME="AEN3251" ></A ->23.1. HPUX</H2 +>21.1. HPUX</H2 ><P >HP's implementation of supplementary groups is, er, non-standard (for hysterical reasons). There are two group files, /etc/group and @@ -15509,9 +15897,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN3121" +NAME="AEN3257" ></A ->23.2. SCO Unix</H2 +>21.2. SCO Unix</H2 ><P > If you run an old version of SCO Unix then you may need to get important @@ -15526,9 +15914,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN3125" +NAME="AEN3261" ></A ->23.3. DNIX</H2 +>21.3. DNIX</H2 ><P >DNIX has a problem with seteuid() and setegid(). These routines are needed for Samba to work correctly, but they were left out of the DNIX @@ -15633,9 +16021,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN3154" +NAME="AEN3290" ></A ->23.4. RedHat Linux Rembrandt-II</H2 +>21.4. RedHat Linux Rembrandt-II</H2 ><P >By default RedHat Rembrandt-II during installation adds an entry to /etc/hosts as follows: @@ -15659,7 +16047,7 @@ CLASS="CHAPTER" ><A NAME="OTHER-CLIENTS" ></A ->Chapter 24. Samba and other CIFS clients</H1 +>Chapter 22. Samba and other CIFS clients</H1 ><P >This chapter contains client-specific information.</P ><DIV @@ -15667,9 +16055,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN3175" +NAME="AEN3311" ></A ->24.1. Macintosh clients?</H2 +>22.1. Macintosh clients?</H2 ><P >Yes. <A HREF="http://www.thursby.com/" @@ -15713,17 +16101,17 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN3184" +NAME="AEN3320" ></A ->24.2. OS2 Client</H2 +>22.2. OS2 Client</H2 ><DIV CLASS="SECT2" ><H3 CLASS="SECT2" ><A -NAME="AEN3186" +NAME="AEN3322" ></A ->24.2.1. How can I configure OS/2 Warp Connect or +>22.2.1. How can I configure OS/2 Warp Connect or OS/2 Warp 4 as a client for Samba?</H3 ><P >A more complete answer to this question can be @@ -15780,9 +16168,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN3201" +NAME="AEN3337" ></A ->24.2.2. How can I configure OS/2 Warp 3 (not Connect), +>22.2.2. How can I configure OS/2 Warp 3 (not Connect), OS/2 1.2, 1.3 or 2.x for Samba?</H3 ><P >You can use the free Microsoft LAN Manager 2.2c Client @@ -15824,9 +16212,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN3210" +NAME="AEN3346" ></A ->24.2.3. Are there any other issues when OS/2 (any version) +>22.2.3. Are there any other issues when OS/2 (any version) is used as a client?</H3 ><P >When you do a NET VIEW or use the "File and Print @@ -15846,9 +16234,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN3214" +NAME="AEN3350" ></A ->24.2.4. How do I get printer driver download working +>22.2.4. How do I get printer driver download working for OS/2 clients?</H3 ><P >First, create a share called [PRINTDRV] that is @@ -15897,17 +16285,17 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN3224" +NAME="AEN3360" ></A ->24.3. Windows for Workgroups</H2 +>22.3. Windows for Workgroups</H2 ><DIV CLASS="SECT2" ><H3 CLASS="SECT2" ><A -NAME="AEN3226" +NAME="AEN3362" ></A ->24.3.1. Use latest TCP/IP stack from Microsoft</H3 +>22.3.1. Use latest TCP/IP stack from Microsoft</H3 ><P >Use the latest TCP/IP stack from microsoft if you use Windows for workgroups.</P @@ -15927,9 +16315,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN3231" +NAME="AEN3367" ></A ->24.3.2. Delete .pwl files after password change</H3 +>22.3.2. Delete .pwl files after password change</H3 ><P >WfWg does a lousy job with passwords. I find that if I change my password on either the unix box or the PC the safest thing to do is to @@ -15947,9 +16335,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN3236" +NAME="AEN3372" ></A ->24.3.3. Configure WfW password handling</H3 +>22.3.3. Configure WfW password handling</H3 ><P >There is a program call admincfg.exe on the last disk (disk 8) of the WFW 3.11 disk set. To install it @@ -15966,9 +16354,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN3240" +NAME="AEN3376" ></A ->24.3.4. Case handling of passwords</H3 +>22.3.4. Case handling of passwords</H3 ><P >Windows for Workgroups uppercases the password before sending it to the server. Unix passwords can be case-sensitive though. Check the <A HREF="smb.conf.5.html" @@ -15985,9 +16373,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN3245" +NAME="AEN3381" ></A ->24.4. Windows '95/'98</H2 +>22.4. Windows '95/'98</H2 ><P >When using Windows 95 OEM SR2 the following updates are recommended where Samba is being used. Please NOTE that the above change will affect you once these @@ -16033,9 +16421,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN3261" +NAME="AEN3397" ></A ->24.5. Windows 2000 Service Pack 2</H2 +>22.5. Windows 2000 Service Pack 2</H2 ><P > There are several annoyances with Windows 2000 SP2. One of which @@ -16117,15 +16505,15 @@ CLASS="CHAPTER" ><A NAME="BUGREPORT" ></A ->Chapter 25. Reporting Bugs</H1 +>Chapter 23. Reporting Bugs</H1 ><DIV CLASS="SECT1" ><H2 CLASS="SECT1" ><A -NAME="AEN3285" +NAME="AEN3421" ></A ->25.1. Introduction</H2 +>23.1. Introduction</H2 ><P >The email address for bug reports for stable releases is <A HREF="samba@samba.org" @@ -16168,9 +16556,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN3295" +NAME="AEN3431" ></A ->25.2. General info</H2 +>23.2. General info</H2 ><P >Before submitting a bug report check your config for silly errors. Look in your log files for obvious messages that tell you that @@ -16193,9 +16581,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN3301" +NAME="AEN3437" ></A ->25.3. Debug levels</H2 +>23.3. Debug levels</H2 ><P >If the bug has anything to do with Samba behaving incorrectly as a server (like refusing to open a file) then the log files will probably @@ -16263,9 +16651,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN3318" +NAME="AEN3454" ></A ->25.4. Internal errors</H2 +>23.4. Internal errors</H2 ><P >If you get a "INTERNAL ERROR" message in your log files it means that Samba got an unexpected signal while running. It is probably a @@ -16307,9 +16695,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN3328" +NAME="AEN3464" ></A ->25.5. Attaching to a running process</H2 +>23.5. Attaching to a running process</H2 ><P >Unfortunately some unixes (in particular some recent linux kernels) refuse to dump a core file if the task has changed uid (which smbd @@ -16324,9 +16712,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN3331" +NAME="AEN3467" ></A ->25.6. Patches</H2 +>23.6. Patches</H2 ><P >The best sort of bug report is one that includes a fix! If you send us patches please use <B @@ -16347,15 +16735,15 @@ CLASS="CHAPTER" ><A NAME="DIAGNOSIS" ></A ->Chapter 26. Diagnosing your samba server</H1 +>Chapter 24. Diagnosing your samba server</H1 ><DIV CLASS="SECT1" ><H2 CLASS="SECT1" ><A -NAME="AEN3354" +NAME="AEN3490" ></A ->26.1. Introduction</H2 +>24.1. Introduction</H2 ><P >This file contains a list of tests you can perform to validate your Samba server. It also tells you what the likely cause of the problem @@ -16375,9 +16763,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN3359" +NAME="AEN3495" ></A ->26.2. Assumptions</H2 +>24.2. Assumptions</H2 ><P >In all of the tests it is assumed you have a Samba server called BIGSERVER and a PC called ACLIENT both in workgroup TESTGROUP.</P @@ -16413,17 +16801,17 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN3369" +NAME="AEN3505" ></A ->26.3. Tests</H2 +>24.3. Tests</H2 ><DIV CLASS="SECT2" ><H3 CLASS="SECT2" ><A -NAME="AEN3371" +NAME="AEN3507" ></A ->26.3.1. Test 1</H3 +>24.3.1. Test 1</H3 ><P >In the directory in which you store your smb.conf file, run the command "testparm smb.conf". If it reports any errors then your smb.conf @@ -16443,9 +16831,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN3377" +NAME="AEN3513" ></A ->26.3.2. Test 2</H3 +>24.3.2. Test 2</H3 ><P >Run the command "ping BIGSERVER" from the PC and "ping ACLIENT" from the unix box. If you don't get a valid response then your TCP/IP @@ -16469,9 +16857,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN3383" +NAME="AEN3519" ></A ->26.3.3. Test 3</H3 +>24.3.3. Test 3</H3 ><P >Run the command "smbclient -L BIGSERVER" on the unix box. You should get a list of available shares back. </P @@ -16540,9 +16928,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN3398" +NAME="AEN3534" ></A ->26.3.4. Test 4</H3 +>24.3.4. Test 4</H3 ><P >Run the command "nmblookup -B BIGSERVER __SAMBA__". You should get the IP address of your Samba server back.</P @@ -16561,9 +16949,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN3403" +NAME="AEN3539" ></A ->26.3.5. Test 5</H3 +>24.3.5. Test 5</H3 ><P >run the command <B CLASS="COMMAND" @@ -16582,9 +16970,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN3409" +NAME="AEN3545" ></A ->26.3.6. Test 6</H3 +>24.3.6. Test 6</H3 ><P >Run the command <B CLASS="COMMAND" @@ -16616,9 +17004,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN3417" +NAME="AEN3553" ></A ->26.3.7. Test 7</H3 +>24.3.7. Test 7</H3 ><P >Run the command <B CLASS="COMMAND" @@ -16705,9 +17093,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN3443" +NAME="AEN3579" ></A ->26.3.8. Test 8</H3 +>24.3.8. Test 8</H3 ><P >On the PC type the command <B CLASS="COMMAND" @@ -16765,9 +17153,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN3460" +NAME="AEN3596" ></A ->26.3.9. Test 9</H3 +>24.3.9. Test 9</H3 ><P >Run the command <B CLASS="COMMAND" @@ -16799,9 +17187,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN3468" +NAME="AEN3604" ></A ->26.3.10. Test 10</H3 +>24.3.10. Test 10</H3 ><P >Run the command <B CLASS="COMMAND" @@ -16825,9 +17213,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN3474" +NAME="AEN3610" ></A ->26.3.11. Test 11</H3 +>24.3.11. Test 11</H3 ><P >From file manager try to browse the server. Your samba server should appear in the browse list of your local workgroup (or the one you @@ -16853,9 +17241,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN3479" +NAME="AEN3615" ></A ->26.4. Still having troubles?</H2 +>24.4. Still having troubles?</H2 ><P >Try the mailing list or newsgroup, or use the ethereal utility to sniff the problem. The official samba mailing list can be reached at diff --git a/docs/htmldocs/ads.html b/docs/htmldocs/ads.html index 26ec1d04a7..2c556b61f3 100644 --- a/docs/htmldocs/ads.html +++ b/docs/htmldocs/ads.html @@ -5,8 +5,7 @@ >Samba as a ADS domain member</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ -"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -17,7 +16,7 @@ REL="PREVIOUS" TITLE="How to Act as a Backup Domain Controller in a Purely Samba Controlled Domain" HREF="samba-bdc.html"><LINK REL="NEXT" -TITLE="Samba as a NT4 domain member" +TITLE="Samba as a NT4 or Win2k domain member" HREF="domain-security.html"></HEAD ><BODY CLASS="CHAPTER" @@ -73,13 +72,16 @@ WIDTH="100%"></DIV CLASS="CHAPTER" ><H1 ><A -NAME="ADS">Chapter 8. Samba as a ADS domain member</H1 +NAME="ADS" +></A +>Chapter 7. Samba as a ADS domain member</H1 ><P >This is a rough guide to setting up Samba 3.0 with kerberos authentication against a Windows2000 KDC. </P ><P ->Pieces you need before you begin: -<P +>Pieces you need before you begin:</P +><P +><P ></P ><TABLE BORDER="0" @@ -110,10 +112,13 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1187">8.1. Installing the required packages for Debian</H1 +NAME="AEN1339" +></A +>7.1. Installing the required packages for Debian</H1 +><P +>On Debian you need to install the following packages:</P +><P ><P ->On Debian you need to install the following packages: -<P ></P ><TABLE BORDER="0" @@ -137,10 +142,13 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1193">8.2. Installing the required packages for RedHat</H1 +NAME="AEN1346" +></A +>7.2. Installing the required packages for RedHat</H1 +><P +>On RedHat this means you should have at least: </P +><P ><P ->On RedHat this means you should have at least: -<P ></P ><TABLE BORDER="0" @@ -173,12 +181,15 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1202">8.3. Compile Samba</H1 +NAME="AEN1356" +></A +>7.3. Compile Samba</H1 ><P >If your kerberos libraries are in a non-standard location then remember to add the configure option --with-krb5=DIR.</P ><P ->After you run configure make sure that include/config.h contains +>After you run configure make sure that include/config.h it + generates contains lines like this:</P ><P ><PRE @@ -214,9 +225,10 @@ CLASS="PROGRAMLISTING" > ads server = your.kerberos.server</PRE ></P ><P ->You do *not* need a smbpasswd file, although it won't do any harm - and if you have one then Samba will be able to fall back to normal - password security for older clients. I expect that the above +>You do *not* need a smbpasswd file, and older clients will + be authenticated as if "security = domain", although it won't do any harm + and allows you to have local users not in the domain. + I expect that the above required options will change soon when we get better active directory integration.</P ></DIV @@ -225,13 +237,15 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1217">8.4. Setup your /etc/krb5.conf</H1 +NAME="AEN1371" +></A +>7.4. Setup your /etc/krb5.conf</H1 ><P >The minimal configuration for krb5.conf is:</P ><P ><PRE CLASS="PROGRAMLISTING" -> [realms] +>[realms] YOUR.KERBEROS.REALM = { kdc = your.kerberos.server }</PRE @@ -255,18 +269,18 @@ to join the realm.</P ><P >If all you want is kerberos support in smbclient then you can skip straight to step 5 now. Step 3 is only needed if you want kerberos -support in smbd.</P +support for smbd and winbindd.</P ></DIV ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1227">8.5. Create the computer account</H1 +NAME="AEN1381" +></A +>7.5. Create the computer account</H1 ><P ->Do a "kinit" as a user that has authority to change arbitrary -passwords on the KDC ("Administrator" is a good choice). Then as a -user that has write permission on the Samba private directory +>As a user that has write permission on the Samba private directory (usually root) run: <B CLASS="COMMAND" @@ -277,7 +291,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1231">8.5.1. Possible errors</H2 +NAME="AEN1385" +></A +>7.5.1. Possible errors</H2 ><P ><P ></P @@ -285,12 +301,6 @@ NAME="AEN1231">8.5.1. Possible errors</H2 CLASS="VARIABLELIST" ><DL ><DT ->"bash: kinit: command not found"</DT -><DD -><P ->kinit is in the krb5-workstation RPM on RedHat systems, and is in /usr/kerberos/bin, so it won't be in the path until you log in again (or open a new terminal)</P -></DD -><DT >"ADS support not compiled in"</DT ><DD ><P @@ -306,7 +316,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1243">8.6. Test your server setup</H1 +NAME="AEN1393" +></A +>7.6. Test your server setup</H1 ><P >On a Windows 2000 client try <B CLASS="COMMAND" @@ -324,7 +336,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1248">8.7. Testing with smbclient</H1 +NAME="AEN1398" +></A +>7.7. Testing with smbclient</H1 ><P >On your Samba server try to login to a Win2000 server or your Samba server using smbclient and kerberos. Use smbclient as usual, but @@ -335,7 +349,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1251">8.8. Notes</H1 +NAME="AEN1401" +></A +>7.8. Notes</H1 ><P >You must change administrator password at least once after DC install, to create the right encoding types</P @@ -402,7 +418,7 @@ ACCESSKEY="U" WIDTH="33%" ALIGN="right" VALIGN="top" ->Samba as a NT4 domain member</TD +>Samba as a NT4 or Win2k domain member</TD ></TR ></TABLE ></DIV diff --git a/docs/htmldocs/appendixes.html b/docs/htmldocs/appendixes.html index e7eefcb441..469ef170cd 100644 --- a/docs/htmldocs/appendixes.html +++ b/docs/htmldocs/appendixes.html @@ -5,14 +5,13 @@ >Appendixes</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ -"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK REL="PREVIOUS" -TITLE="Samba performance issues" -HREF="speed.html"><LINK +TITLE="Creating Group Profiles" +HREF="groupprofiles.html"><LINK REL="NEXT" TITLE="Portability" HREF="portability.html"></HEAD @@ -43,7 +42,7 @@ WIDTH="10%" ALIGN="left" VALIGN="bottom" ><A -HREF="speed.html" +HREF="groupprofiles.html" ACCESSKEY="P" >Prev</A ></TD @@ -69,7 +68,9 @@ WIDTH="100%"></DIV ><DIV CLASS="PART" ><A -NAME="APPENDIXES"><DIV +NAME="APPENDIXES" +></A +><DIV CLASS="TITLEPAGE" ><H1 CLASS="TITLE" @@ -82,243 +83,243 @@ CLASS="TOC" >Table of Contents</B ></DT ><DT ->23. <A +>21. <A HREF="portability.html" >Portability</A ></DT ><DD ><DL ><DT ->23.1. <A -HREF="portability.html#AEN3139" +>21.1. <A +HREF="portability.html#AEN3251" >HPUX</A ></DT ><DT ->23.2. <A -HREF="portability.html#AEN3145" +>21.2. <A +HREF="portability.html#AEN3257" >SCO Unix</A ></DT ><DT ->23.3. <A -HREF="portability.html#AEN3149" +>21.3. <A +HREF="portability.html#AEN3261" >DNIX</A ></DT ><DT ->23.4. <A -HREF="portability.html#AEN3178" +>21.4. <A +HREF="portability.html#AEN3290" >RedHat Linux Rembrandt-II</A ></DT ></DL ></DD ><DT ->24. <A +>22. <A HREF="other-clients.html" >Samba and other CIFS clients</A ></DT ><DD ><DL ><DT ->24.1. <A -HREF="other-clients.html#AEN3199" +>22.1. <A +HREF="other-clients.html#AEN3311" >Macintosh clients?</A ></DT ><DT ->24.2. <A -HREF="other-clients.html#AEN3208" +>22.2. <A +HREF="other-clients.html#AEN3320" >OS2 Client</A ></DT ><DD ><DL ><DT ->24.2.1. <A -HREF="other-clients.html#AEN3210" +>22.2.1. <A +HREF="other-clients.html#AEN3322" >How can I configure OS/2 Warp Connect or OS/2 Warp 4 as a client for Samba?</A ></DT ><DT ->24.2.2. <A -HREF="other-clients.html#AEN3225" +>22.2.2. <A +HREF="other-clients.html#AEN3337" >How can I configure OS/2 Warp 3 (not Connect), OS/2 1.2, 1.3 or 2.x for Samba?</A ></DT ><DT ->24.2.3. <A -HREF="other-clients.html#AEN3234" +>22.2.3. <A +HREF="other-clients.html#AEN3346" >Are there any other issues when OS/2 (any version) is used as a client?</A ></DT ><DT ->24.2.4. <A -HREF="other-clients.html#AEN3238" +>22.2.4. <A +HREF="other-clients.html#AEN3350" >How do I get printer driver download working for OS/2 clients?</A ></DT ></DL ></DD ><DT ->24.3. <A -HREF="other-clients.html#AEN3248" +>22.3. <A +HREF="other-clients.html#AEN3360" >Windows for Workgroups</A ></DT ><DD ><DL ><DT ->24.3.1. <A -HREF="other-clients.html#AEN3250" +>22.3.1. <A +HREF="other-clients.html#AEN3362" >Use latest TCP/IP stack from Microsoft</A ></DT ><DT ->24.3.2. <A -HREF="other-clients.html#AEN3255" +>22.3.2. <A +HREF="other-clients.html#AEN3367" >Delete .pwl files after password change</A ></DT ><DT ->24.3.3. <A -HREF="other-clients.html#AEN3260" +>22.3.3. <A +HREF="other-clients.html#AEN3372" >Configure WfW password handling</A ></DT ><DT ->24.3.4. <A -HREF="other-clients.html#AEN3264" +>22.3.4. <A +HREF="other-clients.html#AEN3376" >Case handling of passwords</A ></DT ></DL ></DD ><DT ->24.4. <A -HREF="other-clients.html#AEN3269" +>22.4. <A +HREF="other-clients.html#AEN3381" >Windows '95/'98</A ></DT ><DT ->24.5. <A -HREF="other-clients.html#AEN3285" +>22.5. <A +HREF="other-clients.html#AEN3397" >Windows 2000 Service Pack 2</A ></DT ></DL ></DD ><DT ->25. <A +>23. <A HREF="bugreport.html" >Reporting Bugs</A ></DT ><DD ><DL ><DT ->25.1. <A -HREF="bugreport.html#AEN3309" +>23.1. <A +HREF="bugreport.html#AEN3421" >Introduction</A ></DT ><DT ->25.2. <A -HREF="bugreport.html#AEN3319" +>23.2. <A +HREF="bugreport.html#AEN3431" >General info</A ></DT ><DT ->25.3. <A -HREF="bugreport.html#AEN3325" +>23.3. <A +HREF="bugreport.html#AEN3437" >Debug levels</A ></DT ><DT ->25.4. <A -HREF="bugreport.html#AEN3342" +>23.4. <A +HREF="bugreport.html#AEN3454" >Internal errors</A ></DT ><DT ->25.5. <A -HREF="bugreport.html#AEN3352" +>23.5. <A +HREF="bugreport.html#AEN3464" >Attaching to a running process</A ></DT ><DT ->25.6. <A -HREF="bugreport.html#AEN3355" +>23.6. <A +HREF="bugreport.html#AEN3467" >Patches</A ></DT ></DL ></DD ><DT ->26. <A +>24. <A HREF="diagnosis.html" >Diagnosing your samba server</A ></DT ><DD ><DL ><DT ->26.1. <A -HREF="diagnosis.html#AEN3378" +>24.1. <A +HREF="diagnosis.html#AEN3490" >Introduction</A ></DT ><DT ->26.2. <A -HREF="diagnosis.html#AEN3383" +>24.2. <A +HREF="diagnosis.html#AEN3495" >Assumptions</A ></DT ><DT ->26.3. <A -HREF="diagnosis.html#AEN3393" +>24.3. <A +HREF="diagnosis.html#AEN3505" >Tests</A ></DT ><DD ><DL ><DT ->26.3.1. <A -HREF="diagnosis.html#AEN3395" +>24.3.1. <A +HREF="diagnosis.html#AEN3507" >Test 1</A ></DT ><DT ->26.3.2. <A -HREF="diagnosis.html#AEN3401" +>24.3.2. <A +HREF="diagnosis.html#AEN3513" >Test 2</A ></DT ><DT ->26.3.3. <A -HREF="diagnosis.html#AEN3407" +>24.3.3. <A +HREF="diagnosis.html#AEN3519" >Test 3</A ></DT ><DT ->26.3.4. <A -HREF="diagnosis.html#AEN3422" +>24.3.4. <A +HREF="diagnosis.html#AEN3534" >Test 4</A ></DT ><DT ->26.3.5. <A -HREF="diagnosis.html#AEN3427" +>24.3.5. <A +HREF="diagnosis.html#AEN3539" >Test 5</A ></DT ><DT ->26.3.6. <A -HREF="diagnosis.html#AEN3433" +>24.3.6. <A +HREF="diagnosis.html#AEN3545" >Test 6</A ></DT ><DT ->26.3.7. <A -HREF="diagnosis.html#AEN3441" +>24.3.7. <A +HREF="diagnosis.html#AEN3553" >Test 7</A ></DT ><DT ->26.3.8. <A -HREF="diagnosis.html#AEN3467" +>24.3.8. <A +HREF="diagnosis.html#AEN3579" >Test 8</A ></DT ><DT ->26.3.9. <A -HREF="diagnosis.html#AEN3484" +>24.3.9. <A +HREF="diagnosis.html#AEN3596" >Test 9</A ></DT ><DT ->26.3.10. <A -HREF="diagnosis.html#AEN3492" +>24.3.10. <A +HREF="diagnosis.html#AEN3604" >Test 10</A ></DT ><DT ->26.3.11. <A -HREF="diagnosis.html#AEN3498" +>24.3.11. <A +HREF="diagnosis.html#AEN3610" >Test 11</A ></DT ></DL ></DD ><DT ->26.4. <A -HREF="diagnosis.html#AEN3503" +>24.4. <A +HREF="diagnosis.html#AEN3615" >Still having troubles?</A ></DT ></DL @@ -343,7 +344,7 @@ WIDTH="33%" ALIGN="left" VALIGN="top" ><A -HREF="speed.html" +HREF="groupprofiles.html" ACCESSKEY="P" >Prev</A ></TD @@ -371,7 +372,7 @@ ACCESSKEY="N" WIDTH="33%" ALIGN="left" VALIGN="top" ->Samba performance issues</TD +>Creating Group Profiles</TD ><TD WIDTH="34%" ALIGN="center" diff --git a/docs/htmldocs/browsing-quick.html b/docs/htmldocs/browsing-quick.html index 8c597e001f..680bdfc1de 100644 --- a/docs/htmldocs/browsing-quick.html +++ b/docs/htmldocs/browsing-quick.html @@ -5,8 +5,7 @@ >Quick Cross Subnet Browsing / Cross Workgroup Browsing guide</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ -"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -14,11 +13,11 @@ REL="UP" TITLE="General installation" HREF="introduction.html"><LINK REL="PREVIOUS" -TITLE="Improved browsing in samba" -HREF="improved-browsing.html"><LINK +TITLE="How to Install and Test SAMBA" +HREF="install.html"><LINK REL="NEXT" -TITLE="LanMan and NT Password Encryption in Samba" -HREF="pwencrypt.html"></HEAD +TITLE="User information database" +HREF="passdb.html"></HEAD ><BODY CLASS="CHAPTER" BGCOLOR="#FFFFFF" @@ -46,7 +45,7 @@ WIDTH="10%" ALIGN="left" VALIGN="bottom" ><A -HREF="improved-browsing.html" +HREF="install.html" ACCESSKEY="P" >Prev</A ></TD @@ -60,7 +59,7 @@ WIDTH="10%" ALIGN="right" VALIGN="bottom" ><A -HREF="pwencrypt.html" +HREF="passdb.html" ACCESSKEY="N" >Next</A ></TD @@ -73,7 +72,9 @@ WIDTH="100%"></DIV CLASS="CHAPTER" ><H1 ><A -NAME="BROWSING-QUICK">Chapter 3. Quick Cross Subnet Browsing / Cross Workgroup Browsing guide</H1 +NAME="BROWSING-QUICK" +></A +>Chapter 2. Quick Cross Subnet Browsing / Cross Workgroup Browsing guide</H1 ><P >This document should be read in conjunction with Browsing and may be taken as the fast track guide to implementing browsing across subnets @@ -85,7 +86,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN377">3.1. Discussion</H1 +NAME="AEN230" +></A +>2.1. Discussion</H1 ><P >Firstly, all MS Windows networking is based on SMB (Server Message Block) based messaging. SMB messaging is implemented using NetBIOS. Samba @@ -129,7 +132,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN385">3.2. Use of the "Remote Announce" parameter</H1 +NAME="AEN238" +></A +>2.2. Use of the "Remote Announce" parameter</H1 ><P >The "remote announce" parameter of smb.conf can be used to forcibly ensure that all the NetBIOS names on a network get announced to a remote network. @@ -185,7 +190,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN399">3.3. Use of the "Remote Browse Sync" parameter</H1 +NAME="AEN252" +></A +>2.3. Use of the "Remote Browse Sync" parameter</H1 ><P >The "remote browse sync" parameter of smb.conf is used to announce to another LMB that it must synchronise it's NetBIOS name list with our @@ -193,9 +200,10 @@ Samba LMB. It works ONLY if the Samba server that has this option is simultaneously the LMB on it's network segment.</P ><P >The syntax of the "remote browse sync" parameter is: + <PRE CLASS="PROGRAMLISTING" -> remote browse sync = a.b.c.d</PRE +>remote browse sync = a.b.c.d</PRE > where a.b.c.d is either the IP address of the remote LMB or else is the network broadcast address of the remote segment.</P @@ -205,7 +213,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN404">3.4. Use of WINS</H1 +NAME="AEN257" +></A +>2.4. Use of WINS</H1 ><P >Use of WINS (either Samba WINS _or_ MS Windows NT Server WINS) is highly recommended. Every NetBIOS machine registers it's name together with a @@ -265,7 +275,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN415">3.5. Do NOT use more than one (1) protocol on MS Windows machines</H1 +NAME="AEN268" +></A +>2.5. Do NOT use more than one (1) protocol on MS Windows machines</H1 ><P >A very common cause of browsing problems results from installing more than one protocol on an MS Windows machine.</P @@ -293,12 +305,14 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN421">3.6. Name Resolution Order</H1 +NAME="AEN274" +></A +>2.6. Name Resolution Order</H1 ><P >Resolution of NetBIOS names to IP addresses can take place using a number of methods. The only ones that can provide NetBIOS name_type information -are: -<P +are:</P +><P ></P ><TABLE BORDER="0" @@ -319,10 +333,9 @@ BORDER="0" ></TABLE ><P ></P -></P ><P ->Alternative means of name resolution includes: -<P +>Alternative means of name resolution includes:</P +><P ></P ><TABLE BORDER="0" @@ -339,24 +352,23 @@ BORDER="0" ></TABLE ><P ></P -></P ><P >Many sites want to restrict DNS lookups and want to avoid broadcast name resolution traffic. The "name resolve order" parameter is of great help here. The syntax of the "name resolve order" parameter is: <PRE CLASS="PROGRAMLISTING" -> name resolve order = wins lmhosts bcast host</PRE +>name resolve order = wins lmhosts bcast host</PRE > _or_ <PRE CLASS="PROGRAMLISTING" -> name resolve order = wins lmhosts (eliminates bcast and host)</PRE +>name resolve order = wins lmhosts (eliminates bcast and host)</PRE > The default is: <PRE CLASS="PROGRAMLISTING" -> name resolve order = host lmhost wins bcast</PRE +>name resolve order = host lmhost wins bcast</PRE >. where "host" refers the the native methods used by the Unix system to implement the gethostbyname() function call. This is normally @@ -388,7 +400,7 @@ WIDTH="33%" ALIGN="left" VALIGN="top" ><A -HREF="improved-browsing.html" +HREF="install.html" ACCESSKEY="P" >Prev</A ></TD @@ -406,7 +418,7 @@ WIDTH="33%" ALIGN="right" VALIGN="top" ><A -HREF="pwencrypt.html" +HREF="passdb.html" ACCESSKEY="N" >Next</A ></TD @@ -416,7 +428,7 @@ ACCESSKEY="N" WIDTH="33%" ALIGN="left" VALIGN="top" ->Improved browsing in samba</TD +>How to Install and Test SAMBA</TD ><TD WIDTH="34%" ALIGN="center" @@ -430,7 +442,7 @@ ACCESSKEY="U" WIDTH="33%" ALIGN="right" VALIGN="top" ->LanMan and NT Password Encryption in Samba</TD +>User information database</TD ></TR ></TABLE ></DIV diff --git a/docs/htmldocs/bugreport.html b/docs/htmldocs/bugreport.html index fcc4b7e91a..813d0055cc 100644 --- a/docs/htmldocs/bugreport.html +++ b/docs/htmldocs/bugreport.html @@ -5,8 +5,7 @@ >Reporting Bugs</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ -"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -73,13 +72,17 @@ WIDTH="100%"></DIV CLASS="CHAPTER" ><H1 ><A -NAME="BUGREPORT">Chapter 25. Reporting Bugs</H1 +NAME="BUGREPORT" +></A +>Chapter 23. Reporting Bugs</H1 ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3309">25.1. Introduction</H1 +NAME="AEN3421" +></A +>23.1. Introduction</H1 ><P >The email address for bug reports for stable releases is <A HREF="samba@samba.org" @@ -122,7 +125,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3319">25.2. General info</H1 +NAME="AEN3431" +></A +>23.2. General info</H1 ><P >Before submitting a bug report check your config for silly errors. Look in your log files for obvious messages that tell you that @@ -145,7 +150,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3325">25.3. Debug levels</H1 +NAME="AEN3437" +></A +>23.3. Debug levels</H1 ><P >If the bug has anything to do with Samba behaving incorrectly as a server (like refusing to open a file) then the log files will probably @@ -213,7 +220,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3342">25.4. Internal errors</H1 +NAME="AEN3454" +></A +>23.4. Internal errors</H1 ><P >If you get a "INTERNAL ERROR" message in your log files it means that Samba got an unexpected signal while running. It is probably a @@ -255,7 +264,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3352">25.5. Attaching to a running process</H1 +NAME="AEN3464" +></A +>23.5. Attaching to a running process</H1 ><P >Unfortunately some unixes (in particular some recent linux kernels) refuse to dump a core file if the task has changed uid (which smbd @@ -270,7 +281,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3355">25.6. Patches</H1 +NAME="AEN3467" +></A +>23.6. Patches</H1 ><P >The best sort of bug report is one that includes a fix! If you send us patches please use <B diff --git a/docs/htmldocs/cvs-access.html b/docs/htmldocs/cvs-access.html index 73cd333805..4e088faf70 100644 --- a/docs/htmldocs/cvs-access.html +++ b/docs/htmldocs/cvs-access.html @@ -2,11 +2,10 @@ <HTML ><HEAD ><TITLE ->HOWTO Access Samba source code via CVS</TITLE +>Access Samba source code via CVS</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ -"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -14,8 +13,8 @@ REL="UP" TITLE="Optional configuration" HREF="optional.html"><LINK REL="PREVIOUS" -TITLE="Storing Samba's User/Machine Account information in an LDAP Directory" -HREF="samba-ldap-howto.html"><LINK +TITLE="Stackable VFS modules" +HREF="vfs.html"><LINK REL="NEXT" TITLE="Group mapping HOWTO" HREF="groupmapping.html"></HEAD @@ -46,7 +45,7 @@ WIDTH="10%" ALIGN="left" VALIGN="bottom" ><A -HREF="samba-ldap-howto.html" +HREF="vfs.html" ACCESSKEY="P" >Prev</A ></TD @@ -73,13 +72,17 @@ WIDTH="100%"></DIV CLASS="CHAPTER" ><H1 ><A -NAME="CVS-ACCESS">Chapter 20. HOWTO Access Samba source code via CVS</H1 +NAME="CVS-ACCESS" +></A +>Chapter 17. Access Samba source code via CVS</H1 ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2964">20.1. Introduction</H1 +NAME="AEN2942" +></A +>17.1. Introduction</H1 ><P >Samba is developed in an open environment. Developers use CVS (Concurrent Versioning System) to "checkin" (also known as @@ -99,7 +102,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2969">20.2. CVS Access to samba.org</H1 +NAME="AEN2947" +></A +>17.2. CVS Access to samba.org</H1 ><P >The machine samba.org runs a publicly accessible CVS repository for access to the source code of several packages, @@ -110,7 +115,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2972">20.2.1. Access via CVSweb</H2 +NAME="AEN2950" +></A +>17.2.1. Access via CVSweb</H2 ><P >You can access the source code via your favourite WWW browser. This allows you to access the contents of @@ -129,7 +136,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2977">20.2.2. Access via cvs</H2 +NAME="AEN2955" +></A +>17.2.2. Access via cvs</H2 ><P >You can also access the source code via a normal cvs client. This gives you much more control over you can @@ -247,7 +256,7 @@ WIDTH="33%" ALIGN="left" VALIGN="top" ><A -HREF="samba-ldap-howto.html" +HREF="vfs.html" ACCESSKEY="P" >Prev</A ></TD @@ -275,7 +284,7 @@ ACCESSKEY="N" WIDTH="33%" ALIGN="left" VALIGN="top" ->Storing Samba's User/Machine Account information in an LDAP Directory</TD +>Stackable VFS modules</TD ><TD WIDTH="34%" ALIGN="center" diff --git a/docs/htmldocs/diagnosis.html b/docs/htmldocs/diagnosis.html index a7b2e59436..0c71043074 100644 --- a/docs/htmldocs/diagnosis.html +++ b/docs/htmldocs/diagnosis.html @@ -5,8 +5,7 @@ >Diagnosing your samba server</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ -"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -66,13 +65,17 @@ WIDTH="100%"></DIV CLASS="CHAPTER" ><H1 ><A -NAME="DIAGNOSIS">Chapter 26. Diagnosing your samba server</H1 +NAME="DIAGNOSIS" +></A +>Chapter 24. Diagnosing your samba server</H1 ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3378">26.1. Introduction</H1 +NAME="AEN3490" +></A +>24.1. Introduction</H1 ><P >This file contains a list of tests you can perform to validate your Samba server. It also tells you what the likely cause of the problem @@ -92,7 +95,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3383">26.2. Assumptions</H1 +NAME="AEN3495" +></A +>24.2. Assumptions</H1 ><P >In all of the tests it is assumed you have a Samba server called BIGSERVER and a PC called ACLIENT both in workgroup TESTGROUP.</P @@ -128,13 +133,17 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3393">26.3. Tests</H1 +NAME="AEN3505" +></A +>24.3. Tests</H1 ><DIV CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3395">26.3.1. Test 1</H2 +NAME="AEN3507" +></A +>24.3.1. Test 1</H2 ><P >In the directory in which you store your smb.conf file, run the command "testparm smb.conf". If it reports any errors then your smb.conf @@ -154,7 +163,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3401">26.3.2. Test 2</H2 +NAME="AEN3513" +></A +>24.3.2. Test 2</H2 ><P >Run the command "ping BIGSERVER" from the PC and "ping ACLIENT" from the unix box. If you don't get a valid response then your TCP/IP @@ -178,7 +189,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3407">26.3.3. Test 3</H2 +NAME="AEN3519" +></A +>24.3.3. Test 3</H2 ><P >Run the command "smbclient -L BIGSERVER" on the unix box. You should get a list of available shares back. </P @@ -247,7 +260,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3422">26.3.4. Test 4</H2 +NAME="AEN3534" +></A +>24.3.4. Test 4</H2 ><P >Run the command "nmblookup -B BIGSERVER __SAMBA__". You should get the IP address of your Samba server back.</P @@ -266,7 +281,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3427">26.3.5. Test 5</H2 +NAME="AEN3539" +></A +>24.3.5. Test 5</H2 ><P >run the command <B CLASS="COMMAND" @@ -285,7 +302,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3433">26.3.6. Test 6</H2 +NAME="AEN3545" +></A +>24.3.6. Test 6</H2 ><P >Run the command <B CLASS="COMMAND" @@ -317,7 +336,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3441">26.3.7. Test 7</H2 +NAME="AEN3553" +></A +>24.3.7. Test 7</H2 ><P >Run the command <B CLASS="COMMAND" @@ -404,7 +425,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3467">26.3.8. Test 8</H2 +NAME="AEN3579" +></A +>24.3.8. Test 8</H2 ><P >On the PC type the command <B CLASS="COMMAND" @@ -462,7 +485,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3484">26.3.9. Test 9</H2 +NAME="AEN3596" +></A +>24.3.9. Test 9</H2 ><P >Run the command <B CLASS="COMMAND" @@ -494,7 +519,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3492">26.3.10. Test 10</H2 +NAME="AEN3604" +></A +>24.3.10. Test 10</H2 ><P >Run the command <B CLASS="COMMAND" @@ -518,7 +545,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3498">26.3.11. Test 11</H2 +NAME="AEN3610" +></A +>24.3.11. Test 11</H2 ><P >From file manager try to browse the server. Your samba server should appear in the browse list of your local workgroup (or the one you @@ -544,7 +573,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3503">26.4. Still having troubles?</H1 +NAME="AEN3615" +></A +>24.4. Still having troubles?</H1 ><P >Try the mailing list or newsgroup, or use the ethereal utility to sniff the problem. The official samba mailing list can be reached at diff --git a/docs/htmldocs/domain-security.html b/docs/htmldocs/domain-security.html index 670d96ba5f..fcb40641e4 100644 --- a/docs/htmldocs/domain-security.html +++ b/docs/htmldocs/domain-security.html @@ -2,11 +2,10 @@ <HTML ><HEAD ><TITLE ->Samba as a NT4 domain member</TITLE +>Samba as a NT4 or Win2k domain member</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ -"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -73,19 +72,23 @@ WIDTH="100%"></DIV CLASS="CHAPTER" ><H1 ><A -NAME="DOMAIN-SECURITY">Chapter 9. Samba as a NT4 domain member</H1 +NAME="DOMAIN-SECURITY" +></A +>Chapter 8. Samba as a NT4 or Win2k domain member</H1 ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1273">9.1. Joining an NT Domain with Samba 2.2</H1 +NAME="AEN1423" +></A +>8.1. Joining an NT Domain with Samba 3.0</H1 ><P ->Assume you have a Samba 2.x server with a NetBIOS name of +>Assume you have a Samba 3.0 server with a NetBIOS name of <TT CLASS="CONSTANT" >SERV1</TT -> and are joining an NT domain called +> and are joining an or Win2k NT domain called <TT CLASS="CONSTANT" >DOM</TT @@ -103,107 +106,7 @@ CLASS="CONSTANT" </TT >.</P ><P ->In order to join the domain, first stop all Samba daemons - and run the command:</P -><P -><TT -CLASS="PROMPT" ->root# </TT -><TT -CLASS="USERINPUT" -><B ->smbpasswd -j DOM -r DOMPDC - -U<TT -CLASS="REPLACEABLE" -><I ->Administrator%password</I -></TT -></B -></TT -></P -><P ->as we are joining the domain DOM and the PDC for that domain - (the only machine that has write access to the domain SAM database) - is DOMPDC. The <TT -CLASS="REPLACEABLE" -><I ->Administrator%password</I -></TT -> is - the login name and password for an account which has the necessary - privilege to add machines to the domain. If this is successful - you will see the message:</P -><P -><TT -CLASS="COMPUTEROUTPUT" ->smbpasswd: Joined domain DOM.</TT -> - </P -><P ->in your terminal window. See the <A -HREF="smbpasswd.8.html" -TARGET="_top" -> smbpasswd(8)</A -> man page for more details.</P -><P ->There is existing development code to join a domain - without having to create the machine trust account on the PDC - beforehand. This code will hopefully be available soon - in release branches as well.</P -><P ->This command goes through the machine account password - change protocol, then writes the new (random) machine account - password for this Samba server into a file in the same directory - in which an smbpasswd file would be stored - normally :</P -><P -><TT -CLASS="FILENAME" ->/usr/local/samba/private</TT -></P -><P ->In Samba 2.0.x, the filename looks like this:</P -><P -><TT -CLASS="FILENAME" -><TT -CLASS="REPLACEABLE" -><I -><NT DOMAIN NAME></I -></TT ->.<TT -CLASS="REPLACEABLE" -><I -><Samba - Server Name></I -></TT ->.mac</TT -></P -><P ->The <TT -CLASS="FILENAME" ->.mac</TT -> suffix stands for machine account - password file. So in our example above, the file would be called:</P -><P -><TT -CLASS="FILENAME" ->DOM.SERV1.mac</TT -></P -><P ->In Samba 2.2, this file has been replaced with a TDB - (Trivial Database) file named <TT -CLASS="FILENAME" ->secrets.tdb</TT ->. - </P -><P ->This file is created and owned by root and is not - readable by any other user. It is the key to the domain-level - security for your system, and should be treated as carefully - as a shadow password file.</P -><P ->Now, before restarting the Samba daemons you must - edit your <A +>Firstly, you must edit your <A HREF="smb.conf.5.html" TARGET="_top" ><TT @@ -228,7 +131,12 @@ CLASS="PARAMETER" ><B CLASS="COMMAND" >security = domain</B -></P +> or + <B +CLASS="COMMAND" +>security = ads</B +> depending on if the PDC is + NT4 or running Active Directory respectivly.</P ><P >Next change the <A HREF="smb.conf.5.html#WORKGROUP" @@ -295,11 +203,77 @@ CLASS="COMMAND" >password server = *</B ></P ><P ->This method, which was introduced in Samba 2.0.6, - allows Samba to use exactly the same mechanism that NT does. This +>This method, allows Samba to use exactly the same + mechanism that NT does. This method either broadcasts or uses a WINS database in order to find domain controllers to authenticate against.</P ><P +>In order to actually join the domain, you must run this + command:</P +><P +><TT +CLASS="PROMPT" +>root# </TT +><TT +CLASS="USERINPUT" +><B +>net join -S DOMPDC + -U<TT +CLASS="REPLACEABLE" +><I +>Administrator%password</I +></TT +></B +></TT +></P +><P +>as we are joining the domain DOM and the PDC for that domain + (the only machine that has write access to the domain SAM database) + is DOMPDC. The <TT +CLASS="REPLACEABLE" +><I +>Administrator%password</I +></TT +> is + the login name and password for an account which has the necessary + privilege to add machines to the domain. If this is successful + you will see the message:</P +><P +><TT +CLASS="COMPUTEROUTPUT" +>Joined domain DOM.</TT +> + or <TT +CLASS="COMPUTEROUTPUT" +>Joined 'SERV1' to realm 'MYREALM'</TT +> + </P +><P +>in your terminal window. See the <A +HREF="net.8.html" +TARGET="_top" +> net(8)</A +> man page for more details.</P +><P +>This process joins the server to thedomain + without having to create the machine trust account on the PDC + beforehand.</P +><P +>This command goes through the machine account password + change protocol, then writes the new (random) machine account + password for this Samba server into a file in the same directory + in which an smbpasswd file would be stored - normally :</P +><P +><TT +CLASS="FILENAME" +>/usr/local/samba/private/secrets.tdb</TT +></P +><P +>This file is created and owned by root and is not + readable by any other user. It is the key to the domain-level + security for your system, and should be treated as carefully + as a shadow password file.</P +><P >Finally, restart your Samba daemons and get ready for clients to begin using domain security!</P ></DIV @@ -308,30 +282,23 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1337">9.2. Samba and Windows 2000 Domains</H1 +NAME="AEN1478" +></A +>8.2. Samba and Windows 2000 Domains</H1 ><P >Many people have asked regarding the state of Samba's ability to participate in a Windows 2000 Domain. Samba 3.0 is able to act as a member server of a Windows -2000 domain operating in mixed or native mode.</P -><P ->There is much confusion between the circumstances that require a "mixed" mode -Win2k DC and a when this host can be switched to "native" mode. A "mixed" mode -Win2k domain controller is only needed if Windows NT BDCs must exist in the same -domain. By default, a Win2k DC in "native" mode will still support -NetBIOS and NTLMv1 for authentication of legacy clients such as Windows 9x and -NT 4.0. Samba has the same requirements as a Windows NT 4.0 member server.</P -><P ->The steps for adding a Samba 2.2 host to a Win2k domain are the same as those -for adding a Samba server to a Windows NT 4.0 domain. The only exception is that -the "Server Manager" from NT 4 has been replaced by the "Active Directory Users and -Computers" MMC (Microsoft Management Console) plugin.</P +2000 domain operating in mixed or native mode. The steps above apply +to both NT4 and Windows 2000.</P ></DIV ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1342">9.3. Why is this better than security = server?</H1 +NAME="AEN1481" +></A +>8.3. Why is this better than security = server?</H1 ><P >Currently, domain security in Samba doesn't free you from having to create local Unix users to represent the users attaching @@ -387,13 +354,7 @@ CLASS="COMMAND" >And finally, acting in the same manner as an NT server authenticating to a PDC means that as part of the authentication reply, the Samba server gets the user identification information such - as the user SID, the list of NT groups the user belongs to, etc. All - this information will allow Samba to be extended in the future into - a mode the developers currently call appliance mode. In this mode, - no local Unix users will be necessary, and Samba will generate Unix - uids and gids from the information passed back from the PDC when a - user is authenticated, making a Samba server truly plug and play - in an NT domain environment. Watch for this code soon.</P + as the user SID, the list of NT groups the user belongs to, etc. </P ><P ><SPAN CLASS="emphasis" diff --git a/docs/htmldocs/findsmb.1.html b/docs/htmldocs/findsmb.1.html index af7100ed6f..bf63db867c 100644 --- a/docs/htmldocs/findsmb.1.html +++ b/docs/htmldocs/findsmb.1.html @@ -1,12 +1,11 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"> +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <HTML ><HEAD ><TITLE >findsmb</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ -"></HEAD +CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"></HEAD ><BODY CLASS="REFENTRY" BGCOLOR="#FFFFFF" @@ -16,7 +15,9 @@ VLINK="#840084" ALINK="#0000FF" ><H1 ><A -NAME="FINDSMB">findsmb</H1 +NAME="FINDSMB.1" +></A +>findsmb</H1 ><DIV CLASS="REFNAMEDIV" ><A @@ -29,13 +30,15 @@ NAME="AEN5" ><DIV CLASS="REFSYNOPSISDIV" ><A -NAME="AEN8"><H2 +NAME="AEN8" +></A +><H2 >Synopsis</H2 ><P ><B CLASS="COMMAND" >findsmb</B -> [subnet broadcast address]</P +> [subnet broadcast address]</P ></DIV ><DIV CLASS="REFSECT1" @@ -45,11 +48,14 @@ NAME="AEN12" ><H2 >DESCRIPTION</H2 ><P ->This perl script is part of the <A -HREF="samba.7.html" -TARGET="_top" -> Samba</A -> suite.</P +>This perl script is part of the <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>Samba</SPAN +>(7)</SPAN +> + suite.</P ><P ><B CLASS="COMMAND" @@ -57,27 +63,27 @@ CLASS="COMMAND" > is a perl script that prints out several pieces of information about machines on a subnet that respond to SMB name query requests. - It uses <A -HREF="nmblookup.1.html" -TARGET="_top" -><B -CLASS="COMMAND" -> nmblookup(1)</B -></A -> and <A -HREF="smbclient.1.html" -TARGET="_top" -> <B -CLASS="COMMAND" ->smbclient(1)</B -></A -> to obtain this information. + It uses <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>nmblookup</SPAN +>(1)</SPAN +> + and <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbclient</SPAN +>(1)</SPAN +> + to obtain this information. </P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN22" +NAME="AEN26" ></A ><H2 >OPTIONS</H2 @@ -97,13 +103,12 @@ CLASS="COMMAND" bugs in Windows95 into account when trying to find a Netbios name registered of the remote machine. This option is disabled by default because it is specific to Windows 95 and Windows 95 machines only. - If set, <A -HREF="nmblookup.1.html" -TARGET="_top" -><B -CLASS="COMMAND" ->nmblookup</B -></A + If set, <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>nmblookup</SPAN +>(1)</SPAN > will be called with <TT CLASS="CONSTANT" @@ -119,15 +124,22 @@ CLASS="COMMAND" >findsmb </B > will probe the subnet of the machine where - <B -CLASS="COMMAND" ->findsmb</B -> is run. This value is passed - to <B -CLASS="COMMAND" ->nmblookup</B -> as part of the - <TT + <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>findsmb</SPAN +>(1)</SPAN +> + is run. This value is passed to + <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>nmblookup</SPAN +>(1)</SPAN +> + as part of the <TT CLASS="CONSTANT" >-B</TT > option.</P @@ -138,7 +150,7 @@ CLASS="CONSTANT" ><DIV CLASS="REFSECT1" ><A -NAME="AEN41" +NAME="AEN50" ></A ><H2 >EXAMPLES</H2 @@ -166,14 +178,14 @@ CLASS="COMMAND" CLASS="CONSTANT" >-r</TT > option - must be run on a system without <A -HREF="nmbd.8.html" -TARGET="_top" -><B -CLASS="COMMAND" ->nmbd</B -></A -> running. + must be run on a system without <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>nmbd</SPAN +>(8)</SPAN +> running. + If <B CLASS="COMMAND" >nmbd</B @@ -192,22 +204,14 @@ CLASS="COMMAND" >For example, running <B CLASS="COMMAND" >findsmb</B -> without - <TT +> + without <TT CLASS="CONSTANT" >-r</TT > option set would yield output similar to the following</P -><TABLE -BORDER="0" -BGCOLOR="#E0E0E0" -WIDTH="100%" -><TR -><TD ><PRE CLASS="SCREEN" -><TT -CLASS="COMPUTEROUTPUT" >IP ADDR NETBIOS NAME WORKGROUP/OS/VERSION --------------------------------------------------------------------- 192.168.35.10 MINESET-TEST1 [DMVENGR] @@ -219,17 +223,12 @@ CLASS="COMPUTEROUTPUT" 192.168.35.78 HERBDHCP1 +[HERB] 192.168.35.88 SCNT2 +[MVENGR] [Windows NT 4.0] [NT LAN Manager 4.0] 192.168.35.93 FROGSTAR-PC [MVENGR] [Windows 5.0] [Windows 2000 LAN Manager] -192.168.35.97 HERBNT1 *[HERB-NT] [Windows NT 4.0] [NT LAN Manager 4.0] - </TT -></PRE -></TD -></TR -></TABLE +192.168.35.97 HERBNT1 *[HERB-NT] [Windows NT 4.0] [NT LAN Manager 4.0]</PRE ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN59" +NAME="AEN68" ></A ><H2 >VERSION</H2 @@ -240,41 +239,37 @@ NAME="AEN59" ><DIV CLASS="REFSECT1" ><A -NAME="AEN62" +NAME="AEN71" ></A ><H2 >SEE ALSO</H2 ><P -><A -HREF="nmbd.8.html" -TARGET="_top" -><B -CLASS="COMMAND" ->nmbd(8)</B -></A ->, - <A -HREF="smbclient.1.html" -TARGET="_top" -><B -CLASS="COMMAND" ->smbclient(1) - </B -></A ->, and <A -HREF="nmblookup.1.html" -TARGET="_top" -> <B -CLASS="COMMAND" ->nmblookup(1)</B -></A +><SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>nmbd</SPAN +>(8)</SPAN +>, + <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbclient</SPAN +>(1)</SPAN +>, and <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>nmblookup</SPAN +>(1)</SPAN > </P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN71" +NAME="AEN83" ></A ><H2 >AUTHOR</H2 @@ -286,14 +281,14 @@ NAME="AEN71" ><P >The original Samba man pages were written by Karl Auer. The man page sources were converted to YODL format (another - excellent piece of Open Source software, available at - <A + excellent piece of Open Source software, available at <A HREF="ftp://ftp.icce.rug.nl/pub/unix/" TARGET="_top" -> ftp://ftp.icce.rug.nl/pub/unix/</A ->) and updated for the Samba 2.0 - release by Jeremy Allison. The conversion to DocBook for - Samba 2.2 was done by Gerald Carter</P +>ftp://ftp.icce.rug.nl/pub/unix/</A +>) + and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for + Samba 2.2 was done by Gerald Carter. The conversion to DocBook + XML 4.2 for Samba 3.0 was done by Alexander Bokovoy.</P ></DIV ></BODY ></HTML diff --git a/docs/htmldocs/groupmapping.html b/docs/htmldocs/groupmapping.html index 84cf521fc9..d7eafcb58f 100644 --- a/docs/htmldocs/groupmapping.html +++ b/docs/htmldocs/groupmapping.html @@ -5,8 +5,7 @@ >Group mapping HOWTO</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ -"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -14,7 +13,7 @@ REL="UP" TITLE="Optional configuration" HREF="optional.html"><LINK REL="PREVIOUS" -TITLE="HOWTO Access Samba source code via CVS" +TITLE="Access Samba source code via CVS" HREF="cvs-access.html"><LINK REL="NEXT" TITLE="Samba performance issues" @@ -73,7 +72,9 @@ WIDTH="100%"></DIV CLASS="CHAPTER" ><H1 ><A -NAME="GROUPMAPPING">Chapter 21. Group mapping HOWTO</H1 +NAME="GROUPMAPPING" +></A +>Chapter 18. Group mapping HOWTO</H1 ><P > Starting with Samba 3.0 alpha 2, a new group mapping function is available. The @@ -212,7 +213,7 @@ ACCESSKEY="N" WIDTH="33%" ALIGN="left" VALIGN="top" ->HOWTO Access Samba source code via CVS</TD +>Access Samba source code via CVS</TD ><TD WIDTH="34%" ALIGN="center" diff --git a/docs/htmldocs/groupprofiles.html b/docs/htmldocs/groupprofiles.html new file mode 100644 index 0000000000..c9184032aa --- /dev/null +++ b/docs/htmldocs/groupprofiles.html @@ -0,0 +1,565 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML +><HEAD +><TITLE +>Creating Group Profiles</TITLE +><META +NAME="GENERATOR" +CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK +REL="HOME" +TITLE="SAMBA Project Documentation" +HREF="samba-howto-collection.html"><LINK +REL="UP" +TITLE="Optional configuration" +HREF="optional.html"><LINK +REL="PREVIOUS" +TITLE="Samba performance issues" +HREF="speed.html"><LINK +REL="NEXT" +TITLE="Appendixes" +HREF="appendixes.html"></HEAD +><BODY +CLASS="CHAPTER" +BGCOLOR="#FFFFFF" +TEXT="#000000" +LINK="#0000FF" +VLINK="#840084" +ALINK="#0000FF" +><DIV +CLASS="NAVHEADER" +><TABLE +SUMMARY="Header navigation table" +WIDTH="100%" +BORDER="0" +CELLPADDING="0" +CELLSPACING="0" +><TR +><TH +COLSPAN="3" +ALIGN="center" +>SAMBA Project Documentation</TH +></TR +><TR +><TD +WIDTH="10%" +ALIGN="left" +VALIGN="bottom" +><A +HREF="speed.html" +ACCESSKEY="P" +>Prev</A +></TD +><TD +WIDTH="80%" +ALIGN="center" +VALIGN="bottom" +></TD +><TD +WIDTH="10%" +ALIGN="right" +VALIGN="bottom" +><A +HREF="appendixes.html" +ACCESSKEY="N" +>Next</A +></TD +></TR +></TABLE +><HR +ALIGN="LEFT" +WIDTH="100%"></DIV +><DIV +CLASS="CHAPTER" +><H1 +><A +NAME="GROUPPROFILES" +></A +>Chapter 20. Creating Group Profiles</H1 +><DIV +CLASS="SECT1" +><H1 +CLASS="SECT1" +><A +NAME="AEN3123" +></A +>20.1. Windows '9x</H1 +><P +>You need the Win98 Group Policy Editor to +set Group Profiles up under Windows '9x. It can be found on the Original +full product Win98 installation CD under +<TT +CLASS="FILENAME" +>tools/reskit/netadmin/poledit</TT +>. You install this +using the Add/Remove Programs facility and then click on the 'Have Disk' +tab.</P +><P +>Use the Group Policy Editor to create a policy file that specifies the +location of user profiles and/or the <TT +CLASS="FILENAME" +>My Documents</TT +> etc. +stuff. You then save these settings in a file called +<TT +CLASS="FILENAME" +>Config.POL</TT +> that needs to be placed in +the root of the [NETLOGON] share. If your Win98 is configured to log onto +the Samba Domain, it will automatically read this file and update the +Win98 registry of the machine that is logging on.</P +><P +>All of this is covered in the Win98 Resource Kit documentation.</P +><P +>If you do not do it this way, then every so often Win98 will check the +integrity of the registry and will restore it's settings from the back-up +copy of the registry it stores on each Win98 machine. Hence, you will notice +things changing back to the original settings.</P +></DIV +><DIV +CLASS="SECT1" +><H1 +CLASS="SECT1" +><A +NAME="AEN3132" +></A +>20.2. Windows NT 4</H1 +><P +>Unfortunately, the Resource Kit info is Win NT4/2K version specific.</P +><P +>Here is a quick guide:</P +><P +></P +><UL +><LI +><P +>On your NT4 Domain Controller, right click on 'My Computer', then +select the tab labelled 'User Profiles'.</P +></LI +><LI +><P +>Select a user profile you want to migrate and click on it.</P +><DIV +CLASS="NOTE" +><P +></P +><TABLE +CLASS="NOTE" +WIDTH="90%" +BORDER="0" +><TR +><TD +WIDTH="25" +ALIGN="CENTER" +VALIGN="TOP" +><IMG +SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif" +HSPACE="5" +ALT="Note"></TD +><TD +ALIGN="LEFT" +VALIGN="TOP" +><P +>I am using the term "migrate" lossely. You can copy a profile to +create a group profile. You can give the user 'Everyone' rights to the +profile you copy this to. That is what you need to do, since your samba +domain is not a member of a trust relationship with your NT4 PDC.</P +></TD +></TR +></TABLE +></DIV +></LI +><LI +><P +>Click the 'Copy To' button.</P +></LI +><LI +><P +>In the box labelled 'Copy Profile to' add your new path, eg: +<TT +CLASS="FILENAME" +>c:\temp\foobar</TT +></P +></LI +><LI +><P +>Click on the button labelled 'Change' in the "Permitted to use" box.</P +></LI +><LI +><P +>Click on the group 'Everyone' and then click OK. This closes the +'chose user' box.</P +></LI +><LI +><P +>Now click OK.</P +></LI +></UL +><P +>Follow the above for every profile you need to migrate.</P +><DIV +CLASS="SECT2" +><H2 +CLASS="SECT2" +><A +NAME="AEN3155" +></A +>20.2.1. Side bar Notes</H2 +><P +>You should obtain the SID of your NT4 domain. You can use smbpasswd to do +this. Read the man page.</P +><P +>With Samba-3.0.0 alpha code you can import all you NT4 domain accounts +using the net samsync method. This way you can retain your profile +settings as well as all your users.</P +></DIV +><DIV +CLASS="SECT2" +><H2 +CLASS="SECT2" +><A +NAME="AEN3159" +></A +>20.2.2. Mandatory profiles</H2 +><P +>The above method can be used to create mandatory profiles also. To convert +a group profile into a mandatory profile simply locate the NTUser.DAT file +in the copied profile and rename it to NTUser.MAN.</P +></DIV +><DIV +CLASS="SECT2" +><H2 +CLASS="SECT2" +><A +NAME="AEN3162" +></A +>20.2.3. moveuser.exe</H2 +><P +>The W2K professional resource kit has moveuser.exe. moveuser.exe changes +the security of a profile from one user to another. This allows the account +domain to change, and/or the user name to change.</P +></DIV +><DIV +CLASS="SECT2" +><H2 +CLASS="SECT2" +><A +NAME="AEN3165" +></A +>20.2.4. Get SID</H2 +><P +>You can identify the SID by using GetSID.exe from the Windows NT Server 4.0 +Resource Kit.</P +><P +>Windows NT 4.0 stores the local profile information in the registry under +the following key: +HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList</P +><P +>Under the ProfileList key, there will be subkeys named with the SIDs of the +users who have logged on to this computer. (To find the profile information +for the user whose locally cached profile you want to move, find the SID for +the user with the GetSID.exe utility.) Inside of the appropriate user's +subkey, you will see a string value named ProfileImagePath.</P +></DIV +></DIV +><DIV +CLASS="SECT1" +><H1 +CLASS="SECT1" +><A +NAME="AEN3170" +></A +>20.3. Windows 2000/XP</H1 +><P +>You must first convert the profile from a local profile to a domain +profile on the MS Windows workstation as follows:</P +><P +></P +><UL +><LI +><P +>Log on as the LOCAL workstation administrator.</P +></LI +><LI +><P +>Right click on the 'My Computer' Icon, select 'Properties'</P +></LI +><LI +><P +>Click on the 'User Profiles' tab</P +></LI +><LI +><P +>Select the profile you wish to convert (click on it once)</P +></LI +><LI +><P +>Click on the button 'Copy To'</P +></LI +><LI +><P +>In the "Permitted to use" box, click on the 'Change' button.</P +></LI +><LI +><P +>Click on the 'Look in" area that lists the machine name, when you click +here it will open up a selection box. Click on the domain to which the +profile must be accessible.</P +><DIV +CLASS="NOTE" +><P +></P +><TABLE +CLASS="NOTE" +WIDTH="90%" +BORDER="0" +><TR +><TD +WIDTH="25" +ALIGN="CENTER" +VALIGN="TOP" +><IMG +SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif" +HSPACE="5" +ALT="Note"></TD +><TD +ALIGN="LEFT" +VALIGN="TOP" +><P +>You will need to log on if a logon box opens up. Eg: In the connect +as: MIDEARTH\root, password: mypassword.</P +></TD +></TR +></TABLE +></DIV +></LI +><LI +><P +>To make the profile capable of being used by anyone select 'Everyone'</P +></LI +><LI +><P +>Click OK. The Selection box will close.</P +></LI +><LI +><P +>Now click on the 'Ok' button to create the profile in the path you +nominated.</P +></LI +></UL +><P +>Done. You now have a profile that can be editted using the samba-3.0.0 +profiles tool.</P +><DIV +CLASS="NOTE" +><P +></P +><TABLE +CLASS="NOTE" +WIDTH="100%" +BORDER="0" +><TR +><TD +WIDTH="25" +ALIGN="CENTER" +VALIGN="TOP" +><IMG +SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif" +HSPACE="5" +ALT="Note"></TD +><TD +ALIGN="LEFT" +VALIGN="TOP" +><P +>Under NT/2K the use of mandotory profiles forces the use of MS Exchange +storage of mail data. That keeps desktop profiles usable.</P +></TD +></TR +></TABLE +></DIV +><DIV +CLASS="NOTE" +><P +></P +><TABLE +CLASS="NOTE" +WIDTH="100%" +BORDER="0" +><TR +><TD +WIDTH="25" +ALIGN="CENTER" +VALIGN="TOP" +><IMG +SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif" +HSPACE="5" +ALT="Note"></TD +><TD +ALIGN="LEFT" +VALIGN="TOP" +><P +></P +><UL +><LI +><P +>This is a security check new to Windows XP (or maybe only +Windows XP service pack 1). It can be disabled via a group policy in +Active Directory. The policy is:</P +><P +>"Computer Configuration\Administrative Templates\System\User +Profiles\Do not check for user ownership of Roaming Profile Folders"</P +><P +>...and it should be set to "Enabled". +Does the new version of samba have an Active Directory analogue? If so, +then you may be able to set the policy through this.</P +><P +>If you cannot set group policies in samba, then you may be able to set +the policy locally on each machine. If you want to try this, then do +the following (N.B. I don't know for sure that this will work in the +same way as a domain group policy):</P +></LI +><LI +><P +>On the XP workstation log in with an Administrator account.</P +></LI +><LI +><P +>Click: "Start", "Run"</P +></LI +><LI +><P +>Type: "mmc"</P +></LI +><LI +><P +>Click: "OK"</P +></LI +><LI +><P +>A Microsoft Management Console should appear.</P +></LI +><LI +><P +>Click: File, "Add/Remove Snap-in...", "Add"</P +></LI +><LI +><P +>Double-Click: "Group Policy"</P +></LI +><LI +><P +>Click: "Finish", "Close"</P +></LI +><LI +><P +>Click: "OK"</P +></LI +><LI +><P +>In the "Console Root" window:</P +></LI +><LI +><P +>Expand: "Local Computer Policy", "Computer Configuration",</P +></LI +><LI +><P +>"Administrative Templates", "System", "User Profiles"</P +></LI +><LI +><P +>Double-Click: "Do not check for user ownership of Roaming Profile</P +></LI +><LI +><P +>Folders"</P +></LI +><LI +><P +>Select: "Enabled"</P +></LI +><LI +><P +>Click: OK"</P +></LI +><LI +><P +>Close the whole console. You do not need to save the settings (this +refers to the console settings rather than the policies you have +changed).</P +></LI +><LI +><P +>Reboot</P +></LI +></UL +></TD +></TR +></TABLE +></DIV +></DIV +></DIV +><DIV +CLASS="NAVFOOTER" +><HR +ALIGN="LEFT" +WIDTH="100%"><TABLE +SUMMARY="Footer navigation table" +WIDTH="100%" +BORDER="0" +CELLPADDING="0" +CELLSPACING="0" +><TR +><TD +WIDTH="33%" +ALIGN="left" +VALIGN="top" +><A +HREF="speed.html" +ACCESSKEY="P" +>Prev</A +></TD +><TD +WIDTH="34%" +ALIGN="center" +VALIGN="top" +><A +HREF="samba-howto-collection.html" +ACCESSKEY="H" +>Home</A +></TD +><TD +WIDTH="33%" +ALIGN="right" +VALIGN="top" +><A +HREF="appendixes.html" +ACCESSKEY="N" +>Next</A +></TD +></TR +><TR +><TD +WIDTH="33%" +ALIGN="left" +VALIGN="top" +>Samba performance issues</TD +><TD +WIDTH="34%" +ALIGN="center" +VALIGN="top" +><A +HREF="optional.html" +ACCESSKEY="U" +>Up</A +></TD +><TD +WIDTH="33%" +ALIGN="right" +VALIGN="top" +>Appendixes</TD +></TR +></TABLE +></DIV +></BODY +></HTML +>
\ No newline at end of file diff --git a/docs/htmldocs/improved-browsing.html b/docs/htmldocs/improved-browsing.html index 4e9d7f639e..b912cb57e5 100644 --- a/docs/htmldocs/improved-browsing.html +++ b/docs/htmldocs/improved-browsing.html @@ -5,20 +5,19 @@ >Improved browsing in samba</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ -"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK REL="UP" -TITLE="General installation" -HREF="introduction.html"><LINK +TITLE="Optional configuration" +HREF="optional.html"><LINK REL="PREVIOUS" -TITLE="How to Install and Test SAMBA" -HREF="install.html"><LINK +TITLE="Unified Logons between Windows NT and UNIX using Winbind" +HREF="winbind.html"><LINK REL="NEXT" -TITLE="Quick Cross Subnet Browsing / Cross Workgroup Browsing guide" -HREF="browsing-quick.html"></HEAD +TITLE="Stackable VFS modules" +HREF="vfs.html"></HEAD ><BODY CLASS="CHAPTER" BGCOLOR="#FFFFFF" @@ -46,7 +45,7 @@ WIDTH="10%" ALIGN="left" VALIGN="bottom" ><A -HREF="install.html" +HREF="winbind.html" ACCESSKEY="P" >Prev</A ></TD @@ -60,7 +59,7 @@ WIDTH="10%" ALIGN="right" VALIGN="bottom" ><A -HREF="browsing-quick.html" +HREF="vfs.html" ACCESSKEY="N" >Next</A ></TD @@ -73,13 +72,17 @@ WIDTH="100%"></DIV CLASS="CHAPTER" ><H1 ><A -NAME="IMPROVED-BROWSING">Chapter 2. Improved browsing in samba</H1 +NAME="IMPROVED-BROWSING" +></A +>Chapter 15. Improved browsing in samba</H1 ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN229">2.1. Overview of browsing</H1 +NAME="AEN2700" +></A +>15.1. Overview of browsing</H1 ><P >SMB networking provides a mechanism by which clients can access a list of machines in a network, a so-called "browse list". This list @@ -101,7 +104,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN233">2.2. Browsing support in samba</H1 +NAME="AEN2704" +></A +>15.2. Browsing support in samba</H1 ><P >Samba now fully supports browsing. The browsing is supported by nmbd and is also controlled by options in the smb.conf file (see smb.conf(5)).</P @@ -144,7 +149,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN242">2.3. Problem resolution</H1 +NAME="AEN2713" +></A +>15.3. Problem resolution</H1 ><P >If something doesn't work then hopefully the log.nmb file will help you track down the problem. Try a debug level of 2 or 3 for finding @@ -176,7 +183,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN249">2.4. Browsing across subnets</H1 +NAME="AEN2720" +></A +>15.4. Browsing across subnets</H1 ><P >With the release of Samba 1.9.17(alpha1 and above) Samba has been updated to enable it to support the replication of browse lists @@ -205,7 +214,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN254">2.4.1. How does cross subnet browsing work ?</H2 +NAME="AEN2725" +></A +>15.4.1. How does cross subnet browsing work ?</H2 ><P >Cross subnet browsing is a complicated dance, containing multiple moving parts. It has taken Microsoft several years to get the code @@ -415,7 +426,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN289">2.5. Setting up a WINS server</H1 +NAME="AEN2760" +></A +>15.5. Setting up a WINS server</H1 ><P >Either a Samba machine or a Windows NT Server machine may be set up as a WINS server. To set a Samba machine to be a WINS server you must @@ -496,7 +509,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN308">2.6. Setting up Browsing in a WORKGROUP</H1 +NAME="AEN2779" +></A +>15.6. Setting up Browsing in a WORKGROUP</H1 ><P >To set up cross subnet browsing on a network containing machines in up to be in a WORKGROUP, not an NT Domain you need to set up one @@ -578,7 +593,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN326">2.7. Setting up Browsing in a DOMAIN</H1 +NAME="AEN2797" +></A +>15.7. Setting up Browsing in a DOMAIN</H1 ><P >If you are adding Samba servers to a Windows NT Domain then you must not set up a Samba server as a domain master browser. @@ -627,7 +644,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN336">2.8. Forcing samba to be the master</H1 +NAME="AEN2807" +></A +>15.8. Forcing samba to be the master</H1 ><P >Who becomes the "master browser" is determined by an election process using broadcasts. Each election packet contains a number of parameters @@ -673,7 +692,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN345">2.9. Making samba the domain master</H1 +NAME="AEN2816" +></A +>15.9. Making samba the domain master</H1 ><P >The domain master is responsible for collating the browse lists of multiple subnets so that browsing can occur between subnets. You can @@ -744,7 +765,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN363">2.10. Note about broadcast addresses</H1 +NAME="AEN2834" +></A +>15.10. Note about broadcast addresses</H1 ><P >If your network uses a "0" based broadcast address (for example if it ends in a 0) then you will strike problems. Windows for Workgroups @@ -756,7 +779,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN366">2.11. Multiple interfaces</H1 +NAME="AEN2837" +></A +>15.11. Multiple interfaces</H1 ><P >Samba now supports machines with multiple network interfaces. If you have multiple interfaces then you will need to use the "interfaces" @@ -779,7 +804,7 @@ WIDTH="33%" ALIGN="left" VALIGN="top" ><A -HREF="install.html" +HREF="winbind.html" ACCESSKEY="P" >Prev</A ></TD @@ -797,7 +822,7 @@ WIDTH="33%" ALIGN="right" VALIGN="top" ><A -HREF="browsing-quick.html" +HREF="vfs.html" ACCESSKEY="N" >Next</A ></TD @@ -807,13 +832,13 @@ ACCESSKEY="N" WIDTH="33%" ALIGN="left" VALIGN="top" ->How to Install and Test SAMBA</TD +>Unified Logons between Windows NT and UNIX using Winbind</TD ><TD WIDTH="34%" ALIGN="center" VALIGN="top" ><A -HREF="introduction.html" +HREF="optional.html" ACCESSKEY="U" >Up</A ></TD @@ -821,7 +846,7 @@ ACCESSKEY="U" WIDTH="33%" ALIGN="right" VALIGN="top" ->Quick Cross Subnet Browsing / Cross Workgroup Browsing guide</TD +>Stackable VFS modules</TD ></TR ></TABLE ></DIV diff --git a/docs/htmldocs/install.html b/docs/htmldocs/install.html index 0ba79dbe26..e518e270bf 100644 --- a/docs/htmldocs/install.html +++ b/docs/htmldocs/install.html @@ -5,8 +5,7 @@ >How to Install and Test SAMBA</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ -"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -17,8 +16,8 @@ REL="PREVIOUS" TITLE="General installation" HREF="introduction.html"><LINK REL="NEXT" -TITLE="Improved browsing in samba" -HREF="improved-browsing.html"></HEAD +TITLE="Quick Cross Subnet Browsing / Cross Workgroup Browsing guide" +HREF="browsing-quick.html"></HEAD ><BODY CLASS="CHAPTER" BGCOLOR="#FFFFFF" @@ -60,7 +59,7 @@ WIDTH="10%" ALIGN="right" VALIGN="bottom" ><A -HREF="improved-browsing.html" +HREF="browsing-quick.html" ACCESSKEY="N" >Next</A ></TD @@ -73,13 +72,17 @@ WIDTH="100%"></DIV CLASS="CHAPTER" ><H1 ><A -NAME="INSTALL">Chapter 1. How to Install and Test SAMBA</H1 +NAME="INSTALL" +></A +>Chapter 1. How to Install and Test SAMBA</H1 ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN26">1.1. Read the man pages</H1 +NAME="AEN26" +></A +>1.1. Read the man pages</H1 ><P >The man pages distributed with SAMBA contain lots of useful info that will help to get you started. @@ -119,7 +122,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN36">1.2. Building the Binaries</H1 +NAME="AEN36" +></A +>1.2. Building the Binaries</H1 ><P >To do this, first run the program <B CLASS="COMMAND" @@ -216,7 +221,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN64">1.3. The all important step</H1 +NAME="AEN64" +></A +>1.3. The all important step</H1 ><P >At this stage you must fetch yourself a coffee or other drink you find stimulating. Getting the rest @@ -231,7 +238,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN68">1.4. Create the smb configuration file.</H1 +NAME="AEN68" +></A +>1.4. Create the smb configuration file.</H1 ><P >There are sample configuration files in the examples subdirectory in the distribution. I suggest you read them @@ -285,7 +294,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN82">1.5. Test your config file with +NAME="AEN82" +></A +>1.5. Test your config file with <B CLASS="COMMAND" >testparm</B @@ -313,7 +324,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN90">1.6. Starting the smbd and nmbd</H1 +NAME="AEN90" +></A +>1.6. Starting the smbd and nmbd</H1 ><P >You must choose to start smbd and nmbd either as daemons or from <B @@ -351,7 +364,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN100">1.6.1. Starting from inetd.conf</H2 +NAME="AEN100" +></A +>1.6.1. Starting from inetd.conf</H2 ><P >NOTE; The following will be different if you use NIS or NIS+ to distributed services maps.</P @@ -453,7 +468,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN129">1.6.2. Alternative: starting it as a daemon</H2 +NAME="AEN129" +></A +>1.6.2. Alternative: starting it as a daemon</H2 ><P >To start the server as a daemon you should create a script something like this one, perhaps calling @@ -508,7 +525,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN145">1.7. Try listing the shares available on your +NAME="AEN145" +></A +>1.7. Try listing the shares available on your server</H1 ><P ><TT @@ -547,7 +566,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN154">1.8. Try connecting with the unix client</H1 +NAME="AEN154" +></A +>1.8. Try connecting with the unix client</H1 ><P ><TT CLASS="PROMPT" @@ -608,7 +629,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN170">1.9. Try connecting from a DOS, WfWg, Win9x, WinNT, +NAME="AEN170" +></A +>1.9. Try connecting from a DOS, WfWg, Win9x, WinNT, Win2k, OS/2, etc... client</H1 ><P >Try mounting disks. eg:</P @@ -655,7 +678,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN184">1.10. What If Things Don't Work?</H1 +NAME="AEN184" +></A +>1.10. What If Things Don't Work?</H1 ><P >If nothing works and you start to think "who wrote this pile of trash" then I suggest you do step 2 again (and @@ -676,7 +701,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN189">1.10.1. Diagnosing Problems</H2 +NAME="AEN189" +></A +>1.10.1. Diagnosing Problems</H2 ><P >If you have installation problems then go to the <A @@ -691,7 +718,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN193">1.10.2. Scope IDs</H2 +NAME="AEN193" +></A +>1.10.2. Scope IDs</H2 ><P >By default Samba uses a blank scope ID. This means all your windows boxes must also have a blank scope ID. @@ -705,7 +734,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN196">1.10.3. Choosing the Protocol Level</H2 +NAME="AEN196" +></A +>1.10.3. Choosing the Protocol Level</H2 ><P >The SMB protocol has many dialects. Currently Samba supports 5, called CORE, COREPLUS, LANMAN1, @@ -744,7 +775,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN205">1.10.4. Printing from UNIX to a Client PC</H2 +NAME="AEN205" +></A +>1.10.4. Printing from UNIX to a Client PC</H2 ><P >To use a printer that is available via a smb-based server from a unix host with LPR you will need to compile the @@ -763,7 +796,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN210">1.10.5. Locking</H2 +NAME="AEN210" +></A +>1.10.5. Locking</H2 ><P >One area which sometimes causes trouble is locking.</P ><P @@ -821,7 +856,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN219">1.10.6. Mapping Usernames</H2 +NAME="AEN219" +></A +>1.10.6. Mapping Usernames</H2 ><P >If you have different usernames on the PCs and the unix server then take a look at the "username map" option. @@ -863,7 +900,7 @@ WIDTH="33%" ALIGN="right" VALIGN="top" ><A -HREF="improved-browsing.html" +HREF="browsing-quick.html" ACCESSKEY="N" >Next</A ></TD @@ -887,7 +924,7 @@ ACCESSKEY="U" WIDTH="33%" ALIGN="right" VALIGN="top" ->Improved browsing in samba</TD +>Quick Cross Subnet Browsing / Cross Workgroup Browsing guide</TD ></TR ></TABLE ></DIV diff --git a/docs/htmldocs/integrate-ms-networks.html b/docs/htmldocs/integrate-ms-networks.html index ad6aa9e225..8299a456bb 100644 --- a/docs/htmldocs/integrate-ms-networks.html +++ b/docs/htmldocs/integrate-ms-networks.html @@ -5,8 +5,7 @@ >Integrating MS Windows networks with Samba</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ -"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -73,13 +72,17 @@ WIDTH="100%"></DIV CLASS="CHAPTER" ><H1 ><A -NAME="INTEGRATE-MS-NETWORKS">Chapter 10. Integrating MS Windows networks with Samba</H1 +NAME="INTEGRATE-MS-NETWORKS" +></A +>Chapter 9. Integrating MS Windows networks with Samba</H1 ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1374">10.1. Agenda</H1 +NAME="AEN1513" +></A +>9.1. Agenda</H1 ><P >To identify the key functional mechanisms of MS Windows networking to enable the deployment of Samba as a means of extending and/or @@ -144,7 +147,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1396">10.2. Name Resolution in a pure Unix/Linux world</H1 +NAME="AEN1535" +></A +>9.2. Name Resolution in a pure Unix/Linux world</H1 ><P >The key configuration files covered in this section are:</P ><P @@ -184,7 +189,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1412">10.2.1. <TT +NAME="AEN1551" +></A +>9.2.1. <TT CLASS="FILENAME" >/etc/hosts</TT ></H2 @@ -263,7 +270,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1428">10.2.2. <TT +NAME="AEN1567" +></A +>9.2.2. <TT CLASS="FILENAME" >/etc/resolv.conf</TT ></H2 @@ -299,7 +308,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1439">10.2.3. <TT +NAME="AEN1578" +></A +>9.2.3. <TT CLASS="FILENAME" >/etc/host.conf</TT ></H2 @@ -326,7 +337,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1447">10.2.4. <TT +NAME="AEN1586" +></A +>9.2.4. <TT CLASS="FILENAME" >/etc/nsswitch.conf</TT ></H2 @@ -393,7 +406,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1459">10.3. Name resolution as used within MS Windows networking</H1 +NAME="AEN1598" +></A +>9.3. Name resolution as used within MS Windows networking</H1 ><P >MS Windows networking is predicated about the name each machine is given. This name is known variously (and inconsistently) as @@ -413,16 +428,16 @@ the client/server.</P ><PRE CLASS="PROGRAMLISTING" > Unique NetBIOS Names: - MACHINENAME<00> = Server Service is running on MACHINENAME - MACHINENAME<03> = Generic Machine Name (NetBIOS name) - MACHINENAME<20> = LanMan Server service is running on MACHINENAME - WORKGROUP<1b> = Domain Master Browser + MACHINENAME<00> = Server Service is running on MACHINENAME + MACHINENAME<03> = Generic Machine Name (NetBIOS name) + MACHINENAME<20> = LanMan Server service is running on MACHINENAME + WORKGROUP<1b> = Domain Master Browser Group Names: - WORKGROUP<03> = Generic Name registered by all members of WORKGROUP - WORKGROUP<1c> = Domain Controllers / Netlogon Servers - WORKGROUP<1d> = Local Master Browsers - WORKGROUP<1e> = Internet Name Resolvers</PRE + WORKGROUP<03> = Generic Name registered by all members of WORKGROUP + WORKGROUP<1c> = Domain Controllers / Netlogon Servers + WORKGROUP<1d> = Local Master Browsers + WORKGROUP<1e> = Internet Name Resolvers</PRE ></P ><P >It should be noted that all NetBIOS machines register their own @@ -441,7 +456,7 @@ be needed. An example of this is what happens when an MS Windows client wants to locate a domain logon server. It find this service and the IP address of a server that provides it by performing a lookup (via a NetBIOS broadcast) for enumeration of all machines that have -registered the name type *<1c>. A logon request is then sent to each +registered the name type *<1c>. A logon request is then sent to each IP address that is returned in the enumerated list of IP addresses. Which ever machine first replies then ends up providing the logon services.</P ><P @@ -476,7 +491,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1471">10.3.1. The NetBIOS Name Cache</H2 +NAME="AEN1610" +></A +>9.3.1. The NetBIOS Name Cache</H2 ><P >All MS Windows machines employ an in memory buffer in which is stored the NetBIOS names and IP addresses for all external @@ -501,7 +518,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1476">10.3.2. The LMHOSTS file</H2 +NAME="AEN1615" +></A +>9.3.2. The LMHOSTS file</H2 ><P >This file is usually located in MS Windows NT 4.0 or 2000 in <TT @@ -602,7 +621,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1484">10.3.3. HOSTS file</H2 +NAME="AEN1623" +></A +>9.3.3. HOSTS file</H2 ><P >This file is usually located in MS Windows NT 4.0 or 2000 in <TT @@ -622,7 +643,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1489">10.3.4. DNS Lookup</H2 +NAME="AEN1628" +></A +>9.3.4. DNS Lookup</H2 ><P >This capability is configured in the TCP/IP setup area in the network configuration facility. If enabled an elaborate name resolution sequence @@ -640,7 +663,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1492">10.3.5. WINS Lookup</H2 +NAME="AEN1631" +></A +>9.3.5. WINS Lookup</H2 ><P >A WINS (Windows Internet Name Server) service is the equivaent of the rfc1001/1002 specified NBNS (NetBIOS Name Server). A WINS server stores @@ -681,7 +706,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1504">10.4. How browsing functions and how to deploy stable and +NAME="AEN1643" +></A +>9.4. How browsing functions and how to deploy stable and dependable browsing using Samba</H1 ><P >As stated above, MS Windows machines register their NetBIOS names @@ -746,7 +773,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1514">10.5. MS Windows security options and how to configure +NAME="AEN1653" +></A +>9.5. MS Windows security options and how to configure Samba for seemless integration</H1 ><P >MS Windows clients may use encrypted passwords as part of a @@ -881,7 +910,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1542">10.5.1. Use MS Windows NT as an authentication server</H2 +NAME="AEN1681" +></A +>9.5.1. Use MS Windows NT as an authentication server</H2 ><P >This method involves the additions of the following parameters in the smb.conf file:</P @@ -915,7 +946,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1550">10.5.2. Make Samba a member of an MS Windows NT security domain</H2 +NAME="AEN1689" +></A +>9.5.2. Make Samba a member of an MS Windows NT security domain</H2 ><P >This method involves additon of the following paramters in the smb.conf file:</P ><P @@ -976,7 +1009,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1567">10.5.3. Configure Samba as an authentication server</H2 +NAME="AEN1706" +></A +>9.5.3. Configure Samba as an authentication server</H2 ><P >This mode of authentication demands that there be on the Unix/Linux system both a Unix style account as well as an @@ -1011,7 +1046,9 @@ CLASS="SECT3" ><H3 CLASS="SECT3" ><A -NAME="AEN1574">10.5.3.1. Users</H3 +NAME="AEN1713" +></A +>9.5.3.1. Users</H3 ><P >A user account that may provide a home directory should be created. The following Linux system commands are typical of @@ -1032,7 +1069,9 @@ CLASS="SECT3" ><H3 CLASS="SECT3" ><A -NAME="AEN1579">10.5.3.2. MS Windows NT Machine Accounts</H3 +NAME="AEN1718" +></A +>9.5.3.2. MS Windows NT Machine Accounts</H3 ><P >These are required only when Samba is used as a domain controller. Refer to the Samba-PDC-HOWTO for more details.</P @@ -1051,7 +1090,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1584">10.6. Conclusions</H1 +NAME="AEN1723" +></A +>9.6. Conclusions</H1 ><P >Samba provides a flexible means to operate as...</P ><P diff --git a/docs/htmldocs/introduction.html b/docs/htmldocs/introduction.html index 762d56ba6a..a68950fede 100644 --- a/docs/htmldocs/introduction.html +++ b/docs/htmldocs/introduction.html @@ -5,8 +5,7 @@ >General installation</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ -"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -69,7 +68,9 @@ WIDTH="100%"></DIV ><DIV CLASS="PART" ><A -NAME="INTRODUCTION"><DIV +NAME="INTRODUCTION" +></A +><DIV CLASS="TITLEPAGE" ><H1 CLASS="TITLE" @@ -77,7 +78,9 @@ CLASS="TITLE" ><DIV CLASS="PARTINTRO" ><A -NAME="AEN21"><H1 +NAME="AEN21" +></A +><H1 >Introduction</H1 ><P >This part contains general info on how to install samba @@ -206,155 +209,199 @@ HREF="install.html#AEN219" ></DD ><DT >2. <A -HREF="improved-browsing.html" ->Improved browsing in samba</A +HREF="browsing-quick.html" +>Quick Cross Subnet Browsing / Cross Workgroup Browsing guide</A ></DT ><DD ><DL ><DT >2.1. <A -HREF="improved-browsing.html#AEN229" ->Overview of browsing</A +HREF="browsing-quick.html#AEN230" +>Discussion</A ></DT ><DT >2.2. <A -HREF="improved-browsing.html#AEN233" ->Browsing support in samba</A +HREF="browsing-quick.html#AEN238" +>Use of the "Remote Announce" parameter</A ></DT ><DT >2.3. <A -HREF="improved-browsing.html#AEN242" ->Problem resolution</A +HREF="browsing-quick.html#AEN252" +>Use of the "Remote Browse Sync" parameter</A ></DT ><DT >2.4. <A -HREF="improved-browsing.html#AEN249" ->Browsing across subnets</A -></DT -><DD -><DL -><DT ->2.4.1. <A -HREF="improved-browsing.html#AEN254" ->How does cross subnet browsing work ?</A +HREF="browsing-quick.html#AEN257" +>Use of WINS</A ></DT -></DL -></DD ><DT >2.5. <A -HREF="improved-browsing.html#AEN289" ->Setting up a WINS server</A +HREF="browsing-quick.html#AEN268" +>Do NOT use more than one (1) protocol on MS Windows machines</A ></DT ><DT >2.6. <A -HREF="improved-browsing.html#AEN308" ->Setting up Browsing in a WORKGROUP</A +HREF="browsing-quick.html#AEN274" +>Name Resolution Order</A ></DT +></DL +></DD ><DT ->2.7. <A -HREF="improved-browsing.html#AEN326" ->Setting up Browsing in a DOMAIN</A +>3. <A +HREF="passdb.html" +>User information database</A ></DT +><DD +><DL ><DT ->2.8. <A -HREF="improved-browsing.html#AEN336" ->Forcing samba to be the master</A +>3.1. <A +HREF="passdb.html#AEN324" +>Introduction</A ></DT ><DT ->2.9. <A -HREF="improved-browsing.html#AEN345" ->Making samba the domain master</A +>3.2. <A +HREF="passdb.html#AEN331" +>Important Notes About Security</A ></DT +><DD +><DL ><DT ->2.10. <A -HREF="improved-browsing.html#AEN363" ->Note about broadcast addresses</A +>3.2.1. <A +HREF="passdb.html#AEN346" +>Advantages of SMB Encryption</A ></DT ><DT ->2.11. <A -HREF="improved-browsing.html#AEN366" ->Multiple interfaces</A +>3.2.2. <A +HREF="passdb.html#AEN351" +>Advantages of non-encrypted passwords</A ></DT ></DL ></DD ><DT ->3. <A -HREF="browsing-quick.html" ->Quick Cross Subnet Browsing / Cross Workgroup Browsing guide</A +>3.3. <A +HREF="passdb.html#AEN357" +>The smbpasswd Command</A +></DT +><DT +>3.4. <A +HREF="passdb.html#AEN388" +>Plain text</A +></DT +><DT +>3.5. <A +HREF="passdb.html#AEN393" +>TDB</A +></DT +><DT +>3.6. <A +HREF="passdb.html#AEN396" +>LDAP</A ></DT ><DD ><DL ><DT ->3.1. <A -HREF="browsing-quick.html#AEN377" ->Discussion</A +>3.6.1. <A +HREF="passdb.html#AEN398" +>Introduction</A ></DT ><DT ->3.2. <A -HREF="browsing-quick.html#AEN385" ->Use of the "Remote Announce" parameter</A +>3.6.2. <A +HREF="passdb.html#AEN418" +>Introduction</A ></DT ><DT ->3.3. <A -HREF="browsing-quick.html#AEN399" ->Use of the "Remote Browse Sync" parameter</A +>3.6.3. <A +HREF="passdb.html#AEN447" +>Supported LDAP Servers</A ></DT ><DT ->3.4. <A -HREF="browsing-quick.html#AEN404" ->Use of WINS</A +>3.6.4. <A +HREF="passdb.html#AEN452" +>Schema and Relationship to the RFC 2307 posixAccount</A ></DT ><DT ->3.5. <A -HREF="browsing-quick.html#AEN415" ->Do NOT use more than one (1) protocol on MS Windows machines</A +>3.6.5. <A +HREF="passdb.html#AEN464" +>Configuring Samba with LDAP</A ></DT ><DT ->3.6. <A -HREF="browsing-quick.html#AEN421" ->Name Resolution Order</A +>3.6.6. <A +HREF="passdb.html#AEN511" +>Accounts and Groups management</A +></DT +><DT +>3.6.7. <A +HREF="passdb.html#AEN516" +>Security and sambaAccount</A +></DT +><DT +>3.6.8. <A +HREF="passdb.html#AEN536" +>LDAP specials attributes for sambaAccounts</A +></DT +><DT +>3.6.9. <A +HREF="passdb.html#AEN606" +>Example LDIF Entries for a sambaAccount</A ></DT ></DL ></DD ><DT ->4. <A -HREF="pwencrypt.html" ->LanMan and NT Password Encryption in Samba</A +>3.7. <A +HREF="passdb.html#AEN614" +>MySQL</A ></DT ><DD ><DL ><DT ->4.1. <A -HREF="pwencrypt.html#AEN457" ->Introduction</A +>3.7.1. <A +HREF="passdb.html#AEN616" +>Building</A ></DT ><DT ->4.2. <A -HREF="pwencrypt.html#AEN462" ->Important Notes About Security</A +>3.7.2. <A +HREF="passdb.html#AEN622" +>Creating the database</A ></DT -><DD -><DL ><DT ->4.2.1. <A -HREF="pwencrypt.html#AEN481" ->Advantages of SMB Encryption</A +>3.7.3. <A +HREF="passdb.html#AEN632" +>Configuring</A ></DT ><DT ->4.2.2. <A -HREF="pwencrypt.html#AEN488" ->Advantages of non-encrypted passwords</A +>3.7.4. <A +HREF="passdb.html#AEN649" +>Using plaintext passwords or encrypted password</A +></DT +><DT +>3.7.5. <A +HREF="passdb.html#AEN654" +>Getting non-column data from the table</A ></DT ></DL ></DD ><DT ->4.3. <A -HREF="pwencrypt.html#AEN497" ->The smbpasswd Command</A +>3.8. <A +HREF="passdb.html#AEN662" +>Passdb XML plugin</A +></DT +><DD +><DL +><DT +>3.8.1. <A +HREF="passdb.html#AEN664" +>Building</A +></DT +><DT +>3.8.2. <A +HREF="passdb.html#AEN670" +>Usage</A ></DT ></DL ></DD ></DL +></DD +></DL ></DIV ></DIV ></DIV diff --git a/docs/htmldocs/lmhosts.5.html b/docs/htmldocs/lmhosts.5.html index 4d7f11e64b..2977cb1227 100644 --- a/docs/htmldocs/lmhosts.5.html +++ b/docs/htmldocs/lmhosts.5.html @@ -5,7 +5,7 @@ >lmhosts</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77"></HEAD +CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"></HEAD ><BODY CLASS="REFENTRY" BGCOLOR="#FFFFFF" @@ -15,7 +15,7 @@ VLINK="#840084" ALINK="#0000FF" ><H1 ><A -NAME="LMHOSTS" +NAME="LMHOSTS.5" ></A >lmhosts</H1 ><DIV @@ -37,24 +37,28 @@ NAME="AEN8" ><TT CLASS="FILENAME" >lmhosts</TT -> is the <A -HREF="samba.7.html" -TARGET="_top" -> Samba</A +> is the <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>Samba</SPAN +>(7)</SPAN > NetBIOS name to IP address mapping file.</P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN12" +NAME="AEN14" ></A ><H2 >DESCRIPTION</H2 ><P ->This file is part of the <A -HREF="samba.7.html" -TARGET="_top" -> Samba</A +>This file is part of the <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>Samba</SPAN +>(7)</SPAN > suite.</P ><P ><TT @@ -78,7 +82,7 @@ CLASS="FILENAME" ><DIV CLASS="REFSECT1" ><A -NAME="AEN20" +NAME="AEN24" ></A ><H2 >FILE FORMAT</H2 @@ -86,7 +90,7 @@ NAME="AEN20" >It is an ASCII file containing one line for NetBIOS name. The two fields on each line are separated from each other by white space. Any entry beginning with '#' is ignored. Each line - in the lmhosts file contains the following information :</P + in the lmhosts file contains the following information:</P ><P ></P ><UL @@ -107,8 +111,7 @@ NAME="AEN20" ></LI ></UL ><P ->An example follows :</P -><P +>An example follows:</P ><PRE CLASS="PROGRAMLISTING" ># @@ -118,7 +121,6 @@ CLASS="PROGRAMLISTING" 192.9.200.20 NTSERVER#20 192.9.200.21 SAMBASERVER </PRE -></P ><P >Contains three IP to NetBIOS name mappings. The first and third will be returned for any queries for the names "TESTPC" @@ -133,58 +135,57 @@ CLASS="PROGRAMLISTING" CLASS="FILENAME" >lmhosts</TT > file - is in the same directory as the <A -HREF="smb.conf.5.html" -TARGET="_top" -> - smb.conf(5)></A + is in the same directory as the <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smb.conf</SPAN +>(5)</SPAN > file.</P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN37" +NAME="AEN42" ></A ><H2 >VERSION</H2 ><P ->This man page is correct for version 2.2 of - the Samba suite.</P +>This man page is correct for version 3.0 of the Samba suite.</P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN40" +NAME="AEN45" ></A ><H2 >SEE ALSO</H2 ><P -><A -HREF="smbclient.1.html" -TARGET="_top" -><B -CLASS="COMMAND" ->smbclient(1) - </B -></A ->, <A -HREF="smb.conf.5.html#NAMERESOLVEORDER" -TARGET="_top" -> smb.conf(5)</A ->, and <A -HREF="smbpasswd.8.html" -TARGET="_top" -><B -CLASS="COMMAND" -> smbpasswd(8)</B -></A +><SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbclient</SPAN +>(1)</SPAN +>, <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smb.conf</SPAN +>(5)</SPAN +>, and <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbpasswd</SPAN +>(8)</SPAN > </P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN48" +NAME="AEN57" ></A ><H2 >AUTHOR</H2 @@ -203,7 +204,8 @@ TARGET="_top" > ftp://ftp.icce.rug.nl/pub/unix/</A >) and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for - Samba 2.2 was done by Gerald Carter</P + Samba 2.2 was done by Gerald Carter. The conversion to DocBook + XML 4.2 was done by Alexander Bokovoy.</P ></DIV ></BODY ></HTML diff --git a/docs/htmldocs/msdfs.html b/docs/htmldocs/msdfs.html index f6fe1c7e1d..f10e0995d5 100644 --- a/docs/htmldocs/msdfs.html +++ b/docs/htmldocs/msdfs.html @@ -5,8 +5,7 @@ >Hosting a Microsoft Distributed File System tree on Samba</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ -"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -74,13 +73,17 @@ WIDTH="100%"></DIV CLASS="CHAPTER" ><H1 ><A -NAME="MSDFS">Chapter 13. Hosting a Microsoft Distributed File System tree on Samba</H1 +NAME="MSDFS" +></A +>Chapter 12. Hosting a Microsoft Distributed File System tree on Samba</H1 ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1859">13.1. Instructions</H1 +NAME="AEN1993" +></A +>12.1. Instructions</H1 ><P >The Distributed File System (or Dfs) provides a means of separating the logical view of files and directories that users @@ -226,7 +229,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1894">13.1.1. Notes</H2 +NAME="AEN2028" +></A +>12.1.1. Notes</H2 ><P ></P ><UL diff --git a/docs/htmldocs/net.8.html b/docs/htmldocs/net.8.html index b7ed1357c3..1652fb4141 100644 --- a/docs/htmldocs/net.8.html +++ b/docs/htmldocs/net.8.html @@ -5,7 +5,7 @@ >net</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77"></HEAD +CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"></HEAD ><BODY CLASS="REFENTRY" BGCOLOR="#FFFFFF" @@ -15,7 +15,7 @@ VLINK="#840084" ALINK="#0000FF" ><H1 ><A -NAME="NET" +NAME="NET.8" ></A >net</H1 ><DIV @@ -48,10 +48,12 @@ NAME="AEN31" ><H2 >DESCRIPTION</H2 ><P ->This tool is part of the <A -HREF="samba.7.html" -TARGET="_top" -> Samba</A +>This tool is part of the <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>Samba</SPAN +>(7)</SPAN > suite.</P ><P >The samba net utility is meant to work just like the net utility @@ -60,7 +62,7 @@ TARGET="_top" ><DIV CLASS="REFSECT1" ><A -NAME="AEN36" +NAME="AEN38" ></A ><H2 >OPTIONS</H2 @@ -81,7 +83,8 @@ CLASS="VARIABLELIST" >-w target-workgroup</DT ><DD ><P -> Sets target workgroup or domain. You have to specify either this option or the IP address or the name of a server. +> Sets target workgroup or domain. You have to specify + either this option or the IP address or the name of a server. </P ></DD ><DT @@ -102,7 +105,8 @@ CLASS="VARIABLELIST" >-I ip-address</DT ><DD ><P -> IP address of target server to use. You have to specify either this option or a target workgroup or a target server. +> IP address of target server to use. You have to + specify either this option or a target workgroup or a target server. </P ></DD ><DT @@ -130,7 +134,8 @@ CLASS="VARIABLELIST" >-S server</DT ><DD ><P -> Name of target server. You should specify either this option or a target workgroup or a target IP address. +> Name of target server. You should specify either + this option or a target workgroup or a target IP address. </P ></DD ><DT @@ -215,7 +220,7 @@ CLASS="FILENAME" ><DIV CLASS="REFSECT1" ><A -NAME="AEN116" +NAME="AEN118" ></A ><H2 >TIME</H2 @@ -245,7 +250,10 @@ CLASS="COMMAND" >SYSTEM</DT ><DD ><P -> Displays the time on the remote server in a format ready for /bin/date +> Displays the time on the remote server in a format ready for <B +CLASS="COMMAND" +>/bin/date</B +> </P ></DD ><DT @@ -253,7 +261,10 @@ CLASS="COMMAND" ><DD ><P > Tries to set the date and time of the local server to that on - the remote server using /bin/date. + the remote server using <B +CLASS="COMMAND" +>/bin/date</B +>. </P ></DD ><DT @@ -269,7 +280,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN138" +NAME="AEN142" ></A ><H2 >RPC</H2 @@ -320,7 +331,7 @@ CLASS="VARIABLELIST" </P ></DD ><DT ->USER ADD <name> [password] [-F user flags] [misc. options</DT +>USER ADD <name> [password] [-F user flags] [misc. options]</DT ><DD ><P > Add specified user @@ -373,7 +384,7 @@ CLASS="VARIABLELIST" ><DIV CLASS="REFSECT1" ><A -NAME="AEN191" +NAME="AEN195" ></A ><H2 >VERSION</H2 @@ -384,7 +395,7 @@ NAME="AEN191" ><DIV CLASS="REFSECT1" ><A -NAME="AEN194" +NAME="AEN198" ></A ><H2 >AUTHOR</H2 diff --git a/docs/htmldocs/nmbd.8.html b/docs/htmldocs/nmbd.8.html index 1183a14522..87a042a912 100644 --- a/docs/htmldocs/nmbd.8.html +++ b/docs/htmldocs/nmbd.8.html @@ -1,12 +1,11 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"> +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <HTML ><HEAD ><TITLE >nmbd</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ -"></HEAD +CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"></HEAD ><BODY CLASS="REFENTRY" BGCOLOR="#FFFFFF" @@ -16,7 +15,9 @@ VLINK="#840084" ALINK="#0000FF" ><H1 ><A -NAME="NMBD">nmbd</H1 +NAME="NMBD.8" +></A +>nmbd</H1 ><DIV CLASS="REFNAMEDIV" ><A @@ -29,13 +30,15 @@ NAME="AEN5" ><DIV CLASS="REFSYNOPSISDIV" ><A -NAME="AEN8"><H2 +NAME="AEN8" +></A +><H2 >Synopsis</H2 ><P ><B CLASS="COMMAND" >nmbd</B -> [-D] [-F] [-S] [-a] [-i] [-o] [-h] [-V] [-d <debug level>] [-H <lmhosts file>] [-l <log directory>] [-n <primary netbios name>] [-p <port number>] [-s <configuration file>]</P +> [-D] [-F] [-S] [-a] [-i] [-o] [-h] [-V] [-d <debug level>] [-H <lmhosts file>] [-l <log directory>] [-n <primary netbios name>] [-p <port number>] [-s <configuration file>]</P ></DIV ><DIV CLASS="REFSECT1" @@ -45,7 +48,13 @@ NAME="AEN25" ><H2 >DESCRIPTION</H2 ><P ->This program is part of the Samba suite.</P +>This program is part of the <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>Samba</SPAN +>(7)</SPAN +> suite.</P ><P ><B CLASS="COMMAND" @@ -69,9 +78,12 @@ CLASS="COMMAND" specified it will respond with the IP number of the host it is running on. Its "own NetBIOS name" is by default the primary DNS name of the host it is running on, - but this can be overridden with the <I + but this can be overridden with the <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >-n</I +></SPAN > option (see OPTIONS below). Thus <B CLASS="COMMAND" @@ -82,13 +94,12 @@ CLASS="COMMAND" CLASS="COMMAND" >nmbd</B > to respond on can be set - via parameters in the <A -HREF="smb.conf.5.html" -TARGET="_top" -><TT -CLASS="FILENAME" -> smb.conf(5)</TT -></A + via parameters in the <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smb.conf</SPAN +>(5)</SPAN > configuration file.</P ><P ><B @@ -111,7 +122,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN42" +NAME="AEN46" ></A ><H2 >OPTIONS</H2 @@ -204,9 +215,9 @@ CLASS="COMMAND" CLASS="COMMAND" >nmbd</B > also logs to standard - output, as if the <B -CLASS="COMMAND" ->-S</B + output, as if the <TT +CLASS="CONSTANT" +>-S</TT > parameter had been given. </P ></DD @@ -233,7 +244,7 @@ CLASS="COMMAND" >.</P ></DD ><DT ->-H <filename></DT +>-H <filename></DT ><DD ><P >NetBIOS lmhosts file. The lmhosts @@ -242,28 +253,39 @@ CLASS="COMMAND" resolution mechanism <A HREF="smb.conf.5.html#nameresolveorder" TARGET="_top" -> name resolve order</A -> described in <A -HREF="smb.conf.5.html" -TARGET="_top" -> <TT -CLASS="FILENAME" ->smb.conf(5)</TT +><TT +CLASS="PARAMETER" +><I +>name resolve + order</I +></TT ></A -> - to resolve any NetBIOS name queries needed by the server. Note - that the contents of this file are <I +> described in <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smb.conf</SPAN +>(5)</SPAN +> to resolve any + NetBIOS name queries needed by the server. Note + that the contents of this file are <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >NOT</I +></SPAN > used by <B CLASS="COMMAND" >nmbd</B > to answer any name queries. Adding a line to this file affects name NetBIOS resolution - from this host <I + from this host <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >ONLY</I +></SPAN >.</P ><P >The default path to this file is compiled into @@ -278,17 +300,14 @@ CLASS="FILENAME" > or <TT CLASS="FILENAME" ->/etc/lmhosts</TT ->. See the - <A -HREF="lmhosts.5.html" -TARGET="_top" -><TT -CLASS="FILENAME" ->lmhosts(5)</TT -></A -> - man page for details on the contents of this file.</P +>/etc/samba/lmhosts</TT +>. See the <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>lmhosts</SPAN +>(5)</SPAN +> man page for details on the contents of this file.</P ></DD ><DT >-V</DT @@ -301,7 +320,7 @@ CLASS="COMMAND" >.</P ></DD ><DT ->-d <debug level></DT +>-d <debug level></DT ><DD ><P >debuglevel is an integer @@ -325,19 +344,23 @@ CLASS="COMMAND" the <A HREF="smb.conf.5.html#loglevel" TARGET="_top" ->log level</A -> - parameter in the <A -HREF="smb.conf.5.html" -TARGET="_top" ><TT -CLASS="FILENAME" -> smb.conf(5)</TT +CLASS="PARAMETER" +><I +>log level</I +></TT ></A +> + parameter in the <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smb.conf</SPAN +>(5)</SPAN > file.</P ></DD ><DT ->-l <log directory></DT +>-l <log directory></DT ><DD ><P >The -l parameter specifies a directory @@ -357,9 +380,12 @@ CLASS="FILENAME" <TT CLASS="FILENAME" >/var/log/log.nmb</TT ->. <I +>. <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >Beware:</I +></SPAN > If the directory specified does not exist, <B CLASS="COMMAND" @@ -369,7 +395,7 @@ CLASS="COMMAND" </P ></DD ><DT ->-n <primary NetBIOS name></DT +>-n <primary NetBIOS name></DT ><DD ><P >This option allows you to override @@ -377,24 +403,31 @@ CLASS="COMMAND" to setting the <A HREF="smb.conf.5.html#netbiosname" TARGET="_top" -> NetBIOS name</A -> parameter in the <A -HREF="smb.conf.5.html" -TARGET="_top" -> - <TT -CLASS="FILENAME" ->smb.conf</TT +><TT +CLASS="PARAMETER" +><I +>NetBIOS + name</I +></TT ></A +> parameter in the <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smb.conf</SPAN +>(5)</SPAN > file. However, a command line setting will take precedence over settings in - <TT -CLASS="FILENAME" ->smb.conf</TT + <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smb.conf</SPAN +>(5)</SPAN >.</P ></DD ><DT ->-p <UDP port number></DT +>-p <UDP port number></DT ><DD ><P >UDP port number is a positive integer value. @@ -407,7 +440,7 @@ CLASS="COMMAND" won't need help!</P ></DD ><DT ->-s <configuration file></DT +>-s <configuration file></DT ><DD ><P >The default configuration file name @@ -418,13 +451,12 @@ CLASS="FILENAME" this may be changed when Samba is autoconfigured.</P ><P >The file specified contains the configuration details - required by the server. See <A -HREF="smb.conf.5.html" -TARGET="_top" -> <TT -CLASS="FILENAME" ->smb.conf(5)</TT -></A + required by the server. See <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smb.conf</SPAN +>(5)</SPAN > for more information. </P ></DD @@ -434,7 +466,7 @@ CLASS="FILENAME" ><DIV CLASS="REFSECT1" ><A -NAME="AEN148" +NAME="AEN162" ></A ><H2 >FILES</H2 @@ -457,9 +489,9 @@ CLASS="COMMAND" > meta-daemon, this file must contain suitable startup information for the meta-daemon. See the <A -HREF="UNIX_INSTALL.html" +HREF="install.html" TARGET="_top" ->UNIX_INSTALL.html</A +>install</A > document for details. </P @@ -477,9 +509,9 @@ CLASS="FILENAME" >If running the server as a daemon at startup, this file will need to contain an appropriate startup sequence for the server. See the <A -HREF="UNIX_INSTALL.html" +HREF="install.html" TARGET="_top" ->UNIX_INSTALL.html</A +>"How to Install and Test SAMBA"</A > document for details.</P ></DD @@ -498,9 +530,9 @@ CLASS="COMMAND" must contain a mapping of service name (e.g., netbios-ssn) to service port (e.g., 139) and protocol type (e.g., tcp). See the <A -HREF="UNIX_INSTALL.html" +HREF="install.html" TARGET="_top" ->UNIX_INSTALL.html</A +>"How to Install and Test SAMBA"</A > document for details.</P ></DD @@ -511,34 +543,39 @@ CLASS="FILENAME" ></DT ><DD ><P ->This is the default location of the - <A -HREF="smb.conf.5.html" -TARGET="_top" -><TT -CLASS="FILENAME" ->smb.conf</TT -></A -> - server configuration file. Other common places that systems +>This is the default location of + the <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smb.conf</SPAN +>(5)</SPAN +> server + configuration file. Other common places that systems install this file are <TT CLASS="FILENAME" >/usr/samba/lib/smb.conf</TT > and <TT CLASS="FILENAME" ->/etc/smb.conf</TT +>/etc/samba/smb.conf</TT >.</P ><P >When run as a WINS server (see the <A HREF="smb.conf.5.html#WINSSUPPORT" TARGET="_top" ->wins support</A +><TT +CLASS="CONSTANT" +>wins support</TT +></A > - parameter in the <TT -CLASS="FILENAME" ->smb.conf(5)</TT + parameter in the <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smb.conf</SPAN +>(5)</SPAN > man page), <B CLASS="COMMAND" @@ -557,19 +594,27 @@ CLASS="FILENAME" >If <B CLASS="COMMAND" >nmbd</B -> is acting as a <I +> is acting as a <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" > browse master</I +></SPAN > (see the <A HREF="smb.conf.5.html#LOCALMASTER" TARGET="_top" ->local master</A +><TT +CLASS="CONSTANT" +>local master</TT +></A > - parameter in the <TT -CLASS="FILENAME" ->smb.conf(5)</TT -> man page, - <B + parameter in the <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smb.conf</SPAN +>(5)</SPAN +> man page, <B CLASS="COMMAND" >nmbd</B > @@ -590,7 +635,7 @@ CLASS="FILENAME" ><DIV CLASS="REFSECT1" ><A -NAME="AEN195" +NAME="AEN216" ></A ><H2 >SIGNALS</H2 @@ -599,9 +644,12 @@ NAME="AEN195" CLASS="COMMAND" >nmbd</B > process it is recommended - that SIGKILL (-9) <I + that SIGKILL (-9) <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >NOT</I +></SPAN > be used, except as a last resort, as this may leave the name database in an inconsistent state. The correct way to terminate <B @@ -636,23 +684,22 @@ CLASS="FILENAME" >log.nmb</TT > file.</P ><P ->The debug log level of nmbd may be raised or lowered using - <A -HREF="smbcontrol.1.html" -TARGET="_top" -><B -CLASS="COMMAND" ->smbcontrol(1)</B -> - </A -> (SIGUSR[1|2] signals are no longer used in Samba 2.2). This is - to allow transient problems to be diagnosed, whilst still running +>The debug log level of nmbd may be raised or lowered + using <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbcontrol</SPAN +>(1)</SPAN +> (SIGUSR[1|2] signals + are no longer used since Samba 2.2). This is to allow + transient problems to be diagnosed, whilst still running at a normally low log level.</P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN211" +NAME="AEN233" ></A ><H2 >VERSION</H2 @@ -663,54 +710,49 @@ NAME="AEN211" ><DIV CLASS="REFSECT1" ><A -NAME="AEN214" +NAME="AEN236" ></A ><H2 >SEE ALSO</H2 ><P -><B -CLASS="COMMAND" ->inetd(8)</B ->, <A -HREF="smbd.8.html" -TARGET="_top" -><B -CLASS="COMMAND" ->smbd(8)</B -></A ->, - <A -HREF="smb.conf.5.html" -TARGET="_top" -><TT -CLASS="FILENAME" ->smb.conf(5)</TT -> - </A ->, <A -HREF="smbclient.1.html" -TARGET="_top" -><B -CLASS="COMMAND" ->smbclient(1) - </B -></A ->, <A -HREF="testparm.1.html" -TARGET="_top" -><B -CLASS="COMMAND" -> testparm(1)</B -></A ->, <A -HREF="testprns.1.html" -TARGET="_top" -> <B -CLASS="COMMAND" ->testprns(1)</B -></A ->, and the Internet RFC's - <TT +> <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>inetd</SPAN +>(8)</SPAN +>, <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbd</SPAN +>(8)</SPAN +>, <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smb.conf</SPAN +>(5)</SPAN +>, <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbclient</SPAN +>(1)</SPAN +>, <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>testparm</SPAN +>(1)</SPAN +>, <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>testprns</SPAN +>(1)</SPAN +>, and the Internet + RFC's <TT CLASS="FILENAME" >rfc1001.txt</TT >, <TT @@ -728,7 +770,7 @@ TARGET="_top" ><DIV CLASS="REFSECT1" ><A -NAME="AEN231" +NAME="AEN260" ></A ><H2 >AUTHOR</H2 @@ -740,14 +782,14 @@ NAME="AEN231" ><P >The original Samba man pages were written by Karl Auer. The man page sources were converted to YODL format (another - excellent piece of Open Source software, available at - <A + excellent piece of Open Source software, available at <A HREF="ftp://ftp.icce.rug.nl/pub/unix/" TARGET="_top" > ftp://ftp.icce.rug.nl/pub/unix/</A >) and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for - Samba 2.2 was done by Gerald Carter</P + Samba 2.2 was done by Gerald Carter. The conversion to DocBook + XML 4.2 for Samba 3.0 was done by Alexander Bokovoy.</P ></DIV ></BODY ></HTML diff --git a/docs/htmldocs/nmblookup.1.html b/docs/htmldocs/nmblookup.1.html index 2ce322990f..9e6da1c7b2 100644 --- a/docs/htmldocs/nmblookup.1.html +++ b/docs/htmldocs/nmblookup.1.html @@ -5,7 +5,7 @@ >nmblookup</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77"></HEAD +CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"></HEAD ><BODY CLASS="REFENTRY" BGCOLOR="#FFFFFF" @@ -48,10 +48,12 @@ NAME="AEN25" ><H2 >DESCRIPTION</H2 ><P ->This tool is part of the <A -HREF="samba.7.html" -TARGET="_top" -> Samba</A +>This tool is part of the <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>Samba</SPAN +>(7)</SPAN > suite.</P ><P ><B @@ -66,7 +68,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN31" +NAME="AEN33" ></A ><H2 >OPTIONS</H2 @@ -109,7 +111,7 @@ CLASS="CONSTANT" query to a machine running a WINS server and the user wishes to query the names in the WINS server. If this bit is unset the normal (broadcast responding) NetBIOS processing code - on a machine is used instead. See rfc1001, rfc1002 for details. + on a machine is used instead. See RFC1001, RFC1002 for details. </P ></DD ><DT @@ -130,12 +132,13 @@ CLASS="CONSTANT" where it ignores the source port of the requesting packet and only replies to UDP port 137. Unfortunately, on most UNIX systems root privilege is needed to bind to this port, and - in addition, if the <A -HREF="nmbd.8.html" -TARGET="_top" ->nmbd(8)</A -> - daemon is running on this machine it also binds to this port. + in addition, if the <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>nmbd</SPAN +>(8)</SPAN +> daemon is running on this machine it also binds to this port. </P ></DD ><DT @@ -173,9 +176,12 @@ CLASS="PARAMETER" ></TT > </A -> parameter of the <TT -CLASS="FILENAME" ->smb.conf (5)</TT +> parameter of the <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smb.conf</SPAN +>(5)</SPAN > file. </P ></DD @@ -311,7 +317,7 @@ CLASS="EMPHASIS" ><DIV CLASS="REFSECT1" ><A -NAME="AEN115" +NAME="AEN121" ></A ><H2 >EXAMPLES</H2 @@ -324,11 +330,11 @@ CLASS="COMMAND" CLASS="COMMAND" >nslookup</B > is - used to query DNS servers). To query a WINS server, - <B + used to query DNS servers). To query a WINS server, <B CLASS="COMMAND" >nmblookup</B -> must be called like this:</P +> + must be called like this:</P ><P ><B CLASS="COMMAND" @@ -348,7 +354,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN127" +NAME="AEN133" ></A ><H2 >VERSION</H2 @@ -359,34 +365,35 @@ NAME="AEN127" ><DIV CLASS="REFSECT1" ><A -NAME="AEN130" +NAME="AEN136" ></A ><H2 >SEE ALSO</H2 ><P -><A -HREF="nmbd.8.html" -TARGET="_top" -><B -CLASS="COMMAND" ->nmbd(8)</B -></A ->, - <A -HREF="samba.7.html" -TARGET="_top" ->samba(7)</A ->, and <A -HREF="smb.conf.5.html" -TARGET="_top" ->smb.conf(5)</A -> - </P +><SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>nmbd</SPAN +>(8)</SPAN +>, <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>samba</SPAN +>(7)</SPAN +>, and <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smb.conf</SPAN +>(5)</SPAN +>.</P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN137" +NAME="AEN148" ></A ><H2 >AUTHOR</H2 @@ -398,14 +405,14 @@ NAME="AEN137" ><P >The original Samba man pages were written by Karl Auer. The man page sources were converted to YODL format (another - excellent piece of Open Source software, available at - <A + excellent piece of Open Source software, available at <A HREF="ftp://ftp.icce.rug.nl/pub/unix/" TARGET="_top" > ftp://ftp.icce.rug.nl/pub/unix/</A >) and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for - Samba 2.2 was done by Gerald Carter</P + Samba 2.2 was done by Gerald Carter. The conversion to DocBook + XML 4.2 for Samba 3.0 was done by Alexander Bokovoy.</P ></DIV ></BODY ></HTML diff --git a/docs/htmldocs/optional.html b/docs/htmldocs/optional.html index b15515ddab..b5564b9f26 100644 --- a/docs/htmldocs/optional.html +++ b/docs/htmldocs/optional.html @@ -5,13 +5,12 @@ >Optional configuration</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ -"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK REL="PREVIOUS" -TITLE="Samba as a NT4 domain member" +TITLE="Samba as a NT4 or Win2k domain member" HREF="domain-security.html"><LINK REL="NEXT" TITLE="Integrating MS Windows networks with Samba" @@ -69,7 +68,9 @@ WIDTH="100%"></DIV ><DIV CLASS="PART" ><A -NAME="OPTIONAL"><DIV +NAME="OPTIONAL" +></A +><DIV CLASS="TITLEPAGE" ><H1 CLASS="TITLE" @@ -77,7 +78,9 @@ CLASS="TITLE" ><DIV CLASS="PARTINTRO" ><A -NAME="AEN1360"><H1 +NAME="AEN1499" +></A +><H1 >Introduction</H1 ><P >Samba has several features that you might want or might not want to use. The chapters in this @@ -91,51 +94,51 @@ CLASS="TOC" >Table of Contents</B ></DT ><DT ->10. <A +>9. <A HREF="integrate-ms-networks.html" >Integrating MS Windows networks with Samba</A ></DT ><DD ><DL ><DT ->10.1. <A -HREF="integrate-ms-networks.html#AEN1374" +>9.1. <A +HREF="integrate-ms-networks.html#AEN1513" >Agenda</A ></DT ><DT ->10.2. <A -HREF="integrate-ms-networks.html#AEN1396" +>9.2. <A +HREF="integrate-ms-networks.html#AEN1535" >Name Resolution in a pure Unix/Linux world</A ></DT ><DD ><DL ><DT ->10.2.1. <A -HREF="integrate-ms-networks.html#AEN1412" +>9.2.1. <A +HREF="integrate-ms-networks.html#AEN1551" ><TT CLASS="FILENAME" >/etc/hosts</TT ></A ></DT ><DT ->10.2.2. <A -HREF="integrate-ms-networks.html#AEN1428" +>9.2.2. <A +HREF="integrate-ms-networks.html#AEN1567" ><TT CLASS="FILENAME" >/etc/resolv.conf</TT ></A ></DT ><DT ->10.2.3. <A -HREF="integrate-ms-networks.html#AEN1439" +>9.2.3. <A +HREF="integrate-ms-networks.html#AEN1578" ><TT CLASS="FILENAME" >/etc/host.conf</TT ></A ></DT ><DT ->10.2.4. <A -HREF="integrate-ms-networks.html#AEN1447" +>9.2.4. <A +HREF="integrate-ms-networks.html#AEN1586" ><TT CLASS="FILENAME" >/etc/nsswitch.conf</TT @@ -144,140 +147,140 @@ CLASS="FILENAME" ></DL ></DD ><DT ->10.3. <A -HREF="integrate-ms-networks.html#AEN1459" +>9.3. <A +HREF="integrate-ms-networks.html#AEN1598" >Name resolution as used within MS Windows networking</A ></DT ><DD ><DL ><DT ->10.3.1. <A -HREF="integrate-ms-networks.html#AEN1471" +>9.3.1. <A +HREF="integrate-ms-networks.html#AEN1610" >The NetBIOS Name Cache</A ></DT ><DT ->10.3.2. <A -HREF="integrate-ms-networks.html#AEN1476" +>9.3.2. <A +HREF="integrate-ms-networks.html#AEN1615" >The LMHOSTS file</A ></DT ><DT ->10.3.3. <A -HREF="integrate-ms-networks.html#AEN1484" +>9.3.3. <A +HREF="integrate-ms-networks.html#AEN1623" >HOSTS file</A ></DT ><DT ->10.3.4. <A -HREF="integrate-ms-networks.html#AEN1489" +>9.3.4. <A +HREF="integrate-ms-networks.html#AEN1628" >DNS Lookup</A ></DT ><DT ->10.3.5. <A -HREF="integrate-ms-networks.html#AEN1492" +>9.3.5. <A +HREF="integrate-ms-networks.html#AEN1631" >WINS Lookup</A ></DT ></DL ></DD ><DT ->10.4. <A -HREF="integrate-ms-networks.html#AEN1504" +>9.4. <A +HREF="integrate-ms-networks.html#AEN1643" >How browsing functions and how to deploy stable and dependable browsing using Samba</A ></DT ><DT ->10.5. <A -HREF="integrate-ms-networks.html#AEN1514" +>9.5. <A +HREF="integrate-ms-networks.html#AEN1653" >MS Windows security options and how to configure Samba for seemless integration</A ></DT ><DD ><DL ><DT ->10.5.1. <A -HREF="integrate-ms-networks.html#AEN1542" +>9.5.1. <A +HREF="integrate-ms-networks.html#AEN1681" >Use MS Windows NT as an authentication server</A ></DT ><DT ->10.5.2. <A -HREF="integrate-ms-networks.html#AEN1550" +>9.5.2. <A +HREF="integrate-ms-networks.html#AEN1689" >Make Samba a member of an MS Windows NT security domain</A ></DT ><DT ->10.5.3. <A -HREF="integrate-ms-networks.html#AEN1567" +>9.5.3. <A +HREF="integrate-ms-networks.html#AEN1706" >Configure Samba as an authentication server</A ></DT ></DL ></DD ><DT ->10.6. <A -HREF="integrate-ms-networks.html#AEN1584" +>9.6. <A +HREF="integrate-ms-networks.html#AEN1723" >Conclusions</A ></DT ></DL ></DD ><DT ->11. <A +>10. <A HREF="unix-permissions.html" >UNIX Permission Bits and Windows NT Access Control Lists</A ></DT ><DD ><DL ><DT ->11.1. <A -HREF="unix-permissions.html#AEN1605" +>10.1. <A +HREF="unix-permissions.html#AEN1744" >Viewing and changing UNIX permissions using the NT security dialogs</A ></DT ><DT ->11.2. <A -HREF="unix-permissions.html#AEN1614" +>10.2. <A +HREF="unix-permissions.html#AEN1748" >How to view file security on a Samba share</A ></DT ><DT ->11.3. <A -HREF="unix-permissions.html#AEN1625" +>10.3. <A +HREF="unix-permissions.html#AEN1759" >Viewing file ownership</A ></DT ><DT ->11.4. <A -HREF="unix-permissions.html#AEN1645" +>10.4. <A +HREF="unix-permissions.html#AEN1779" >Viewing file or directory permissions</A ></DT ><DD ><DL ><DT ->11.4.1. <A -HREF="unix-permissions.html#AEN1660" +>10.4.1. <A +HREF="unix-permissions.html#AEN1794" >File Permissions</A ></DT ><DT ->11.4.2. <A -HREF="unix-permissions.html#AEN1674" +>10.4.2. <A +HREF="unix-permissions.html#AEN1808" >Directory Permissions</A ></DT ></DL ></DD ><DT ->11.5. <A -HREF="unix-permissions.html#AEN1681" +>10.5. <A +HREF="unix-permissions.html#AEN1815" >Modifying file or directory permissions</A ></DT ><DT ->11.6. <A -HREF="unix-permissions.html#AEN1703" +>10.6. <A +HREF="unix-permissions.html#AEN1837" >Interaction with the standard Samba create mask parameters</A ></DT ><DT ->11.7. <A -HREF="unix-permissions.html#AEN1767" +>10.7. <A +HREF="unix-permissions.html#AEN1901" >Interaction with the standard Samba file attribute mapping</A ></DT ></DL ></DD ><DT ->12. <A +>11. <A HREF="pam.html" >Configuring PAM for distributed but centrally managed authentication</A @@ -285,39 +288,39 @@ managed authentication</A ><DD ><DL ><DT ->12.1. <A -HREF="pam.html#AEN1788" +>11.1. <A +HREF="pam.html#AEN1922" >Samba and PAM</A ></DT ><DT ->12.2. <A -HREF="pam.html#AEN1832" +>11.2. <A +HREF="pam.html#AEN1966" >Distributed Authentication</A ></DT ><DT ->12.3. <A -HREF="pam.html#AEN1839" +>11.3. <A +HREF="pam.html#AEN1973" >PAM Configuration in smb.conf</A ></DT ></DL ></DD ><DT ->13. <A +>12. <A HREF="msdfs.html" >Hosting a Microsoft Distributed File System tree on Samba</A ></DT ><DD ><DL ><DT ->13.1. <A -HREF="msdfs.html#AEN1859" +>12.1. <A +HREF="msdfs.html#AEN1993" >Instructions</A ></DT ><DD ><DL ><DT ->13.1.1. <A -HREF="msdfs.html#AEN1894" +>12.1.1. <A +HREF="msdfs.html#AEN2028" >Notes</A ></DT ></DL @@ -325,130 +328,130 @@ HREF="msdfs.html#AEN1894" ></DL ></DD ><DT ->14. <A +>13. <A HREF="printing.html" >Printing Support</A ></DT ><DD ><DL ><DT ->14.1. <A -HREF="printing.html#AEN1920" +>13.1. <A +HREF="printing.html#AEN2054" >Introduction</A ></DT ><DT ->14.2. <A -HREF="printing.html#AEN1942" +>13.2. <A +HREF="printing.html#AEN2076" >Configuration</A ></DT ><DD ><DL ><DT ->14.2.1. <A -HREF="printing.html#AEN1950" +>13.2.1. <A +HREF="printing.html#AEN2084" >Creating [print$]</A ></DT ><DT ->14.2.2. <A -HREF="printing.html#AEN1985" +>13.2.2. <A +HREF="printing.html#AEN2119" >Setting Drivers for Existing Printers</A ></DT ><DT ->14.2.3. <A -HREF="printing.html#AEN2001" +>13.2.3. <A +HREF="printing.html#AEN2135" >Support a large number of printers</A ></DT ><DT ->14.2.4. <A -HREF="printing.html#AEN2012" +>13.2.4. <A +HREF="printing.html#AEN2146" >Adding New Printers via the Windows NT APW</A ></DT ><DT ->14.2.5. <A -HREF="printing.html#AEN2042" +>13.2.5. <A +HREF="printing.html#AEN2176" >Samba and Printer Ports</A ></DT ></DL ></DD ><DT ->14.3. <A -HREF="printing.html#AEN2050" +>13.3. <A +HREF="printing.html#AEN2184" >The Imprints Toolset</A ></DT ><DD ><DL ><DT ->14.3.1. <A -HREF="printing.html#AEN2054" +>13.3.1. <A +HREF="printing.html#AEN2188" >What is Imprints?</A ></DT ><DT ->14.3.2. <A -HREF="printing.html#AEN2064" +>13.3.2. <A +HREF="printing.html#AEN2198" >Creating Printer Driver Packages</A ></DT ><DT ->14.3.3. <A -HREF="printing.html#AEN2067" +>13.3.3. <A +HREF="printing.html#AEN2201" >The Imprints server</A ></DT ><DT ->14.3.4. <A -HREF="printing.html#AEN2071" +>13.3.4. <A +HREF="printing.html#AEN2205" >The Installation Client</A ></DT ></DL ></DD ><DT ->14.4. <A -HREF="printing.html#AEN2093" +>13.4. <A +HREF="printing.html#AEN2227" >Diagnosis</A ></DT ><DD ><DL ><DT ->14.4.1. <A -HREF="printing.html#AEN2095" +>13.4.1. <A +HREF="printing.html#AEN2229" >Introduction</A ></DT ><DT ->14.4.2. <A -HREF="printing.html#AEN2111" +>13.4.2. <A +HREF="printing.html#AEN2245" >Debugging printer problems</A ></DT ><DT ->14.4.3. <A -HREF="printing.html#AEN2120" +>13.4.3. <A +HREF="printing.html#AEN2254" >What printers do I have?</A ></DT ><DT ->14.4.4. <A -HREF="printing.html#AEN2128" +>13.4.4. <A +HREF="printing.html#AEN2262" >Setting up printcap and print servers</A ></DT ><DT ->14.4.5. <A -HREF="printing.html#AEN2156" +>13.4.5. <A +HREF="printing.html#AEN2290" >Job sent, no output</A ></DT ><DT ->14.4.6. <A -HREF="printing.html#AEN2167" +>13.4.6. <A +HREF="printing.html#AEN2301" >Job sent, strange output</A ></DT ><DT ->14.4.7. <A -HREF="printing.html#AEN2179" +>13.4.7. <A +HREF="printing.html#AEN2313" >Raw PostScript printed</A ></DT ><DT ->14.4.8. <A -HREF="printing.html#AEN2182" +>13.4.8. <A +HREF="printing.html#AEN2316" >Advanced Printing</A ></DT ><DT ->14.4.9. <A -HREF="printing.html#AEN2185" +>13.4.9. <A +HREF="printing.html#AEN2319" >Real debugging</A ></DT ></DL @@ -456,205 +459,235 @@ HREF="printing.html#AEN2185" ></DL ></DD ><DT ->15. <A +>14. <A HREF="winbind.html" >Unified Logons between Windows NT and UNIX using Winbind</A ></DT ><DD ><DL ><DT ->15.1. <A -HREF="winbind.html#AEN2225" +>14.1. <A +HREF="winbind.html#AEN2360" >Abstract</A ></DT ><DT ->15.2. <A -HREF="winbind.html#AEN2229" +>14.2. <A +HREF="winbind.html#AEN2364" >Introduction</A ></DT ><DT ->15.3. <A -HREF="winbind.html#AEN2242" +>14.3. <A +HREF="winbind.html#AEN2377" >What Winbind Provides</A ></DT ><DD ><DL ><DT ->15.3.1. <A -HREF="winbind.html#AEN2249" +>14.3.1. <A +HREF="winbind.html#AEN2384" >Target Uses</A ></DT ></DL ></DD ><DT ->15.4. <A -HREF="winbind.html#AEN2253" +>14.4. <A +HREF="winbind.html#AEN2388" >How Winbind Works</A ></DT ><DD ><DL ><DT ->15.4.1. <A -HREF="winbind.html#AEN2258" +>14.4.1. <A +HREF="winbind.html#AEN2393" >Microsoft Remote Procedure Calls</A ></DT ><DT ->15.4.2. <A -HREF="winbind.html#AEN2262" +>14.4.2. <A +HREF="winbind.html#AEN2397" +>Microsoft Active Directory Services</A +></DT +><DT +>14.4.3. <A +HREF="winbind.html#AEN2400" >Name Service Switch</A ></DT ><DT ->15.4.3. <A -HREF="winbind.html#AEN2278" +>14.4.4. <A +HREF="winbind.html#AEN2416" >Pluggable Authentication Modules</A ></DT ><DT ->15.4.4. <A -HREF="winbind.html#AEN2286" +>14.4.5. <A +HREF="winbind.html#AEN2424" >User and Group ID Allocation</A ></DT ><DT ->15.4.5. <A -HREF="winbind.html#AEN2290" +>14.4.6. <A +HREF="winbind.html#AEN2428" >Result Caching</A ></DT ></DL ></DD ><DT ->15.5. <A -HREF="winbind.html#AEN2293" +>14.5. <A +HREF="winbind.html#AEN2431" >Installation and Configuration</A ></DT ><DD ><DL ><DT ->15.5.1. <A -HREF="winbind.html#AEN2300" +>14.5.1. <A +HREF="winbind.html#AEN2438" >Introduction</A ></DT ><DT ->15.5.2. <A -HREF="winbind.html#AEN2313" +>14.5.2. <A +HREF="winbind.html#AEN2451" >Requirements</A ></DT ><DT ->15.5.3. <A -HREF="winbind.html#AEN2327" +>14.5.3. <A +HREF="winbind.html#AEN2465" >Testing Things Out</A ></DT ></DL ></DD ><DT ->15.6. <A -HREF="winbind.html#AEN2542" +>14.6. <A +HREF="winbind.html#AEN2680" >Limitations</A ></DT ><DT ->15.7. <A -HREF="winbind.html#AEN2552" +>14.7. <A +HREF="winbind.html#AEN2690" >Conclusion</A ></DT ></DL ></DD ><DT ->16. <A -HREF="pdb-mysql.html" ->Passdb MySQL plugin</A +>15. <A +HREF="improved-browsing.html" +>Improved browsing in samba</A ></DT ><DD ><DL ><DT ->16.1. <A -HREF="pdb-mysql.html#AEN2566" ->Building</A +>15.1. <A +HREF="improved-browsing.html#AEN2700" +>Overview of browsing</A ></DT ><DT ->16.2. <A -HREF="pdb-mysql.html#AEN2572" ->Configuring</A +>15.2. <A +HREF="improved-browsing.html#AEN2704" +>Browsing support in samba</A ></DT ><DT ->16.3. <A -HREF="pdb-mysql.html#AEN2589" ->Using plaintext passwords or encrypted password</A +>15.3. <A +HREF="improved-browsing.html#AEN2713" +>Problem resolution</A ></DT ><DT ->16.4. <A -HREF="pdb-mysql.html#AEN2594" ->Getting non-column data from the table</A +>15.4. <A +HREF="improved-browsing.html#AEN2720" +>Browsing across subnets</A +></DT +><DD +><DL +><DT +>15.4.1. <A +HREF="improved-browsing.html#AEN2725" +>How does cross subnet browsing work ?</A ></DT ></DL ></DD ><DT ->17. <A -HREF="pdb-xml.html" ->Passdb XML plugin</A +>15.5. <A +HREF="improved-browsing.html#AEN2760" +>Setting up a WINS server</A ></DT -><DD -><DL ><DT ->17.1. <A -HREF="pdb-xml.html#AEN2613" ->Building</A +>15.6. <A +HREF="improved-browsing.html#AEN2779" +>Setting up Browsing in a WORKGROUP</A ></DT ><DT ->17.2. <A -HREF="pdb-xml.html#AEN2619" ->Usage</A +>15.7. <A +HREF="improved-browsing.html#AEN2797" +>Setting up Browsing in a DOMAIN</A +></DT +><DT +>15.8. <A +HREF="improved-browsing.html#AEN2807" +>Forcing samba to be the master</A +></DT +><DT +>15.9. <A +HREF="improved-browsing.html#AEN2816" +>Making samba the domain master</A +></DT +><DT +>15.10. <A +HREF="improved-browsing.html#AEN2834" +>Note about broadcast addresses</A +></DT +><DT +>15.11. <A +HREF="improved-browsing.html#AEN2837" +>Multiple interfaces</A ></DT ></DL ></DD ><DT ->18. <A +>16. <A HREF="vfs.html" >Stackable VFS modules</A ></DT ><DD ><DL ><DT ->18.1. <A -HREF="vfs.html#AEN2640" +>16.1. <A +HREF="vfs.html#AEN2855" >Introduction and configuration</A ></DT ><DT ->18.2. <A -HREF="vfs.html#AEN2649" +>16.2. <A +HREF="vfs.html#AEN2864" >Included modules</A ></DT ><DD ><DL ><DT ->18.2.1. <A -HREF="vfs.html#AEN2651" +>16.2.1. <A +HREF="vfs.html#AEN2866" >audit</A ></DT ><DT ->18.2.2. <A -HREF="vfs.html#AEN2659" +>16.2.2. <A +HREF="vfs.html#AEN2874" >recycle</A ></DT ><DT ->18.2.3. <A -HREF="vfs.html#AEN2696" +>16.2.3. <A +HREF="vfs.html#AEN2911" >netatalk</A ></DT ></DL ></DD ><DT ->18.3. <A -HREF="vfs.html#AEN2703" +>16.3. <A +HREF="vfs.html#AEN2918" >VFS modules available elsewhere</A ></DT ><DD ><DL ><DT ->18.3.1. <A -HREF="vfs.html#AEN2707" +>16.3.1. <A +HREF="vfs.html#AEN2922" >DatabaseFS</A ></DT ><DT ->18.3.2. <A -HREF="vfs.html#AEN2715" +>16.3.2. <A +HREF="vfs.html#AEN2930" >vscan</A ></DT ></DL @@ -662,105 +695,32 @@ HREF="vfs.html#AEN2715" ></DL ></DD ><DT ->19. <A -HREF="samba-ldap-howto.html" ->Storing Samba's User/Machine Account information in an LDAP Directory</A -></DT -><DD -><DL -><DT ->19.1. <A -HREF="samba-ldap-howto.html#AEN2737" ->Purpose</A -></DT -><DT ->19.2. <A -HREF="samba-ldap-howto.html#AEN2757" ->Introduction</A -></DT -><DT ->19.3. <A -HREF="samba-ldap-howto.html#AEN2786" ->Supported LDAP Servers</A -></DT -><DT ->19.4. <A -HREF="samba-ldap-howto.html#AEN2791" ->Schema and Relationship to the RFC 2307 posixAccount</A -></DT -><DT ->19.5. <A -HREF="samba-ldap-howto.html#AEN2803" ->Configuring Samba with LDAP</A -></DT -><DD -><DL -><DT ->19.5.1. <A -HREF="samba-ldap-howto.html#AEN2805" ->OpenLDAP configuration</A -></DT -><DT ->19.5.2. <A -HREF="samba-ldap-howto.html#AEN2822" ->Configuring Samba</A -></DT -></DL -></DD -><DT ->19.6. <A -HREF="samba-ldap-howto.html#AEN2850" ->Accounts and Groups management</A -></DT -><DT ->19.7. <A -HREF="samba-ldap-howto.html#AEN2855" ->Security and sambaAccount</A -></DT -><DT ->19.8. <A -HREF="samba-ldap-howto.html#AEN2875" ->LDAP specials attributes for sambaAccounts</A -></DT -><DT ->19.9. <A -HREF="samba-ldap-howto.html#AEN2945" ->Example LDIF Entries for a sambaAccount</A -></DT -><DT ->19.10. <A -HREF="samba-ldap-howto.html#AEN2953" ->Comments</A -></DT -></DL -></DD -><DT ->20. <A +>17. <A HREF="cvs-access.html" ->HOWTO Access Samba source code via CVS</A +>Access Samba source code via CVS</A ></DT ><DD ><DL ><DT ->20.1. <A -HREF="cvs-access.html#AEN2964" +>17.1. <A +HREF="cvs-access.html#AEN2942" >Introduction</A ></DT ><DT ->20.2. <A -HREF="cvs-access.html#AEN2969" +>17.2. <A +HREF="cvs-access.html#AEN2947" >CVS Access to samba.org</A ></DT ><DD ><DL ><DT ->20.2.1. <A -HREF="cvs-access.html#AEN2972" +>17.2.1. <A +HREF="cvs-access.html#AEN2950" >Access via CVSweb</A ></DT ><DT ->20.2.2. <A -HREF="cvs-access.html#AEN2977" +>17.2.2. <A +HREF="cvs-access.html#AEN2955" >Access via cvs</A ></DT ></DL @@ -768,69 +728,117 @@ HREF="cvs-access.html#AEN2977" ></DL ></DD ><DT ->21. <A +>18. <A HREF="groupmapping.html" >Group mapping HOWTO</A ></DT ><DT ->22. <A +>19. <A HREF="speed.html" >Samba performance issues</A ></DT ><DD ><DL ><DT ->22.1. <A -HREF="speed.html#AEN3055" +>19.1. <A +HREF="speed.html#AEN3033" >Comparisons</A ></DT ><DT ->22.2. <A -HREF="speed.html#AEN3061" +>19.2. <A +HREF="speed.html#AEN3039" >Socket options</A ></DT ><DT ->22.3. <A -HREF="speed.html#AEN3068" +>19.3. <A +HREF="speed.html#AEN3046" >Read size</A ></DT ><DT ->22.4. <A -HREF="speed.html#AEN3073" +>19.4. <A +HREF="speed.html#AEN3051" >Max xmit</A ></DT ><DT ->22.5. <A -HREF="speed.html#AEN3078" +>19.5. <A +HREF="speed.html#AEN3056" >Log level</A ></DT ><DT ->22.6. <A -HREF="speed.html#AEN3081" +>19.6. <A +HREF="speed.html#AEN3059" >Read raw</A ></DT ><DT ->22.7. <A -HREF="speed.html#AEN3086" +>19.7. <A +HREF="speed.html#AEN3064" >Write raw</A ></DT ><DT ->22.8. <A -HREF="speed.html#AEN3090" +>19.8. <A +HREF="speed.html#AEN3068" >Slow Clients</A ></DT ><DT ->22.9. <A -HREF="speed.html#AEN3094" +>19.9. <A +HREF="speed.html#AEN3072" >Slow Logins</A ></DT ><DT ->22.10. <A -HREF="speed.html#AEN3097" +>19.10. <A +HREF="speed.html#AEN3075" >Client tuning</A ></DT ></DL ></DD +><DT +>20. <A +HREF="groupprofiles.html" +>Creating Group Profiles</A +></DT +><DD +><DL +><DT +>20.1. <A +HREF="groupprofiles.html#AEN3123" +>Windows '9x</A +></DT +><DT +>20.2. <A +HREF="groupprofiles.html#AEN3132" +>Windows NT 4</A +></DT +><DD +><DL +><DT +>20.2.1. <A +HREF="groupprofiles.html#AEN3155" +>Side bar Notes</A +></DT +><DT +>20.2.2. <A +HREF="groupprofiles.html#AEN3159" +>Mandatory profiles</A +></DT +><DT +>20.2.3. <A +HREF="groupprofiles.html#AEN3162" +>moveuser.exe</A +></DT +><DT +>20.2.4. <A +HREF="groupprofiles.html#AEN3165" +>Get SID</A +></DT +></DL +></DD +><DT +>20.3. <A +HREF="groupprofiles.html#AEN3170" +>Windows 2000/XP</A +></DT +></DL +></DD ></DL ></DIV ></DIV @@ -879,7 +887,7 @@ ACCESSKEY="N" WIDTH="33%" ALIGN="left" VALIGN="top" ->Samba as a NT4 domain member</TD +>Samba as a NT4 or Win2k domain member</TD ><TD WIDTH="34%" ALIGN="center" diff --git a/docs/htmldocs/other-clients.html b/docs/htmldocs/other-clients.html index 130c9691e7..7f0f99319e 100644 --- a/docs/htmldocs/other-clients.html +++ b/docs/htmldocs/other-clients.html @@ -5,8 +5,7 @@ >Samba and other CIFS clients</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ -"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -73,7 +72,9 @@ WIDTH="100%"></DIV CLASS="CHAPTER" ><H1 ><A -NAME="OTHER-CLIENTS">Chapter 24. Samba and other CIFS clients</H1 +NAME="OTHER-CLIENTS" +></A +>Chapter 22. Samba and other CIFS clients</H1 ><P >This chapter contains client-specific information.</P ><DIV @@ -81,7 +82,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3199">24.1. Macintosh clients?</H1 +NAME="AEN3311" +></A +>22.1. Macintosh clients?</H1 ><P >Yes. <A HREF="http://www.thursby.com/" @@ -125,13 +128,17 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3208">24.2. OS2 Client</H1 +NAME="AEN3320" +></A +>22.2. OS2 Client</H1 ><DIV CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3210">24.2.1. How can I configure OS/2 Warp Connect or +NAME="AEN3322" +></A +>22.2.1. How can I configure OS/2 Warp Connect or OS/2 Warp 4 as a client for Samba?</H2 ><P >A more complete answer to this question can be @@ -188,7 +195,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3225">24.2.2. How can I configure OS/2 Warp 3 (not Connect), +NAME="AEN3337" +></A +>22.2.2. How can I configure OS/2 Warp 3 (not Connect), OS/2 1.2, 1.3 or 2.x for Samba?</H2 ><P >You can use the free Microsoft LAN Manager 2.2c Client @@ -230,7 +239,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3234">24.2.3. Are there any other issues when OS/2 (any version) +NAME="AEN3346" +></A +>22.2.3. Are there any other issues when OS/2 (any version) is used as a client?</H2 ><P >When you do a NET VIEW or use the "File and Print @@ -250,7 +261,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3238">24.2.4. How do I get printer driver download working +NAME="AEN3350" +></A +>22.2.4. How do I get printer driver download working for OS/2 clients?</H2 ><P >First, create a share called [PRINTDRV] that is @@ -299,13 +312,17 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3248">24.3. Windows for Workgroups</H1 +NAME="AEN3360" +></A +>22.3. Windows for Workgroups</H1 ><DIV CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3250">24.3.1. Use latest TCP/IP stack from Microsoft</H2 +NAME="AEN3362" +></A +>22.3.1. Use latest TCP/IP stack from Microsoft</H2 ><P >Use the latest TCP/IP stack from microsoft if you use Windows for workgroups.</P @@ -325,7 +342,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3255">24.3.2. Delete .pwl files after password change</H2 +NAME="AEN3367" +></A +>22.3.2. Delete .pwl files after password change</H2 ><P >WfWg does a lousy job with passwords. I find that if I change my password on either the unix box or the PC the safest thing to do is to @@ -343,7 +362,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3260">24.3.3. Configure WfW password handling</H2 +NAME="AEN3372" +></A +>22.3.3. Configure WfW password handling</H2 ><P >There is a program call admincfg.exe on the last disk (disk 8) of the WFW 3.11 disk set. To install it @@ -360,7 +381,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3264">24.3.4. Case handling of passwords</H2 +NAME="AEN3376" +></A +>22.3.4. Case handling of passwords</H2 ><P >Windows for Workgroups uppercases the password before sending it to the server. Unix passwords can be case-sensitive though. Check the <A HREF="smb.conf.5.html" @@ -377,7 +400,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3269">24.4. Windows '95/'98</H1 +NAME="AEN3381" +></A +>22.4. Windows '95/'98</H1 ><P >When using Windows 95 OEM SR2 the following updates are recommended where Samba is being used. Please NOTE that the above change will affect you once these @@ -423,7 +448,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3285">24.5. Windows 2000 Service Pack 2</H1 +NAME="AEN3397" +></A +>22.5. Windows 2000 Service Pack 2</H1 ><P > There are several annoyances with Windows 2000 SP2. One of which diff --git a/docs/htmldocs/pam.html b/docs/htmldocs/pam.html index ba2bf6c922..a64de2a1b4 100644 --- a/docs/htmldocs/pam.html +++ b/docs/htmldocs/pam.html @@ -6,8 +6,7 @@ managed authentication</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ -"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -74,14 +73,18 @@ WIDTH="100%"></DIV CLASS="CHAPTER" ><H1 ><A -NAME="PAM">Chapter 12. Configuring PAM for distributed but centrally +NAME="PAM" +></A +>Chapter 11. Configuring PAM for distributed but centrally managed authentication</H1 ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1788">12.1. Samba and PAM</H1 +NAME="AEN1922" +></A +>11.1. Samba and PAM</H1 ><P >A number of Unix systems (eg: Sun Solaris), as well as the xxxxBSD family and Linux, now utilize the Pluggable Authentication @@ -293,7 +296,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1832">12.2. Distributed Authentication</H1 +NAME="AEN1966" +></A +>11.2. Distributed Authentication</H1 ><P >The astute administrator will realize from this that the combination of <TT @@ -324,7 +329,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1839">12.3. PAM Configuration in smb.conf</H1 +NAME="AEN1973" +></A +>11.3. PAM Configuration in smb.conf</H1 ><P >There is an option in smb.conf called <A HREF="smb.conf.5.html#OBEYPAMRESTRICTIONS" diff --git a/docs/htmldocs/passdb.html b/docs/htmldocs/passdb.html new file mode 100644 index 0000000000..f53641624a --- /dev/null +++ b/docs/htmldocs/passdb.html @@ -0,0 +1,1646 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML +><HEAD +><TITLE +>User information database</TITLE +><META +NAME="GENERATOR" +CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK +REL="HOME" +TITLE="SAMBA Project Documentation" +HREF="samba-howto-collection.html"><LINK +REL="UP" +TITLE="General installation" +HREF="introduction.html"><LINK +REL="PREVIOUS" +TITLE="Quick Cross Subnet Browsing / Cross Workgroup Browsing guide" +HREF="browsing-quick.html"><LINK +REL="NEXT" +TITLE="Type of installation" +HREF="type.html"></HEAD +><BODY +CLASS="CHAPTER" +BGCOLOR="#FFFFFF" +TEXT="#000000" +LINK="#0000FF" +VLINK="#840084" +ALINK="#0000FF" +><DIV +CLASS="NAVHEADER" +><TABLE +SUMMARY="Header navigation table" +WIDTH="100%" +BORDER="0" +CELLPADDING="0" +CELLSPACING="0" +><TR +><TH +COLSPAN="3" +ALIGN="center" +>SAMBA Project Documentation</TH +></TR +><TR +><TD +WIDTH="10%" +ALIGN="left" +VALIGN="bottom" +><A +HREF="browsing-quick.html" +ACCESSKEY="P" +>Prev</A +></TD +><TD +WIDTH="80%" +ALIGN="center" +VALIGN="bottom" +></TD +><TD +WIDTH="10%" +ALIGN="right" +VALIGN="bottom" +><A +HREF="type.html" +ACCESSKEY="N" +>Next</A +></TD +></TR +></TABLE +><HR +ALIGN="LEFT" +WIDTH="100%"></DIV +><DIV +CLASS="CHAPTER" +><H1 +><A +NAME="PASSDB" +></A +>Chapter 3. User information database</H1 +><DIV +CLASS="SECT1" +><H1 +CLASS="SECT1" +><A +NAME="AEN324" +></A +>3.1. Introduction</H1 +><P +>Old windows clients send plain text passwords over the wire. + Samba can check these passwords by crypting them and comparing them + to the hash stored in the unix user database. + </P +><P +> Newer windows clients send encrypted passwords (so-called + Lanman and NT hashes) over + the wire, instead of plain text passwords. The newest clients + will only send encrypted passwords and refuse to send plain text + passwords, unless their registry is tweaked. + </P +><P +>These passwords can't be converted to unix style encrypted + passwords. Because of that you can't use the standard unix + user database, and you have to store the Lanman and NT hashes + somewhere else. </P +><P +>Next to a differently encrypted passwords, + windows also stores certain data for each user + that is not stored in a unix user database, e.g. + workstations the user may logon from, the location where his/her + profile is stored, etc. + Samba retrieves and stores this information using a "passdb backend". + Commonly + available backends are LDAP, plain text file, MySQL and nisplus. + For more information, see the documentation about the + <B +CLASS="COMMAND" +>passdb backend = </B +> parameter. + </P +></DIV +><DIV +CLASS="SECT1" +><H1 +CLASS="SECT1" +><A +NAME="AEN331" +></A +>3.2. Important Notes About Security</H1 +><P +>The unix and SMB password encryption techniques seem similar + on the surface. This similarity is, however, only skin deep. The unix + scheme typically sends clear text passwords over the network when + logging in. This is bad. The SMB encryption scheme never sends the + cleartext password over the network but it does store the 16 byte + hashed values on disk. This is also bad. Why? Because the 16 byte hashed + values are a "password equivalent". You cannot derive the user's + password from them, but they could potentially be used in a modified + client to gain access to a server. This would require considerable + technical knowledge on behalf of the attacker but is perfectly possible. + You should thus treat the data stored in whatever + passdb backend you use (smbpasswd file, ldap, mysql) as though it contained the + cleartext passwords of all your users. Its contents must be kept + secret, and the file should be protected accordingly.</P +><P +>Ideally we would like a password scheme which neither requires + plain text passwords on the net or on disk. Unfortunately this + is not available as Samba is stuck with being compatible with + other SMB systems (WinNT, WfWg, Win95 etc). </P +><DIV +CLASS="WARNING" +><P +></P +><TABLE +CLASS="WARNING" +WIDTH="100%" +BORDER="0" +><TR +><TD +WIDTH="25" +ALIGN="CENTER" +VALIGN="TOP" +><IMG +SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/warning.gif" +HSPACE="5" +ALT="Warning"></TD +><TD +ALIGN="LEFT" +VALIGN="TOP" +><P +>Note that Windows NT 4.0 Service pack 3 changed the + default for permissible authentication so that plaintext + passwords are <SPAN +CLASS="emphasis" +><I +CLASS="EMPHASIS" +>never</I +></SPAN +> sent over the wire. + The solution to this is either to switch to encrypted passwords + with Samba or edit the Windows NT registry to re-enable plaintext + passwords. See the document WinNT.txt for details on how to do + this.</P +><P +>Other Microsoft operating systems which also exhibit + this behavior includes</P +><P +></P +><TABLE +BORDER="0" +><TBODY +><TR +><TD +>MS DOS Network client 3.0 with + the basic network redirector installed</TD +></TR +><TR +><TD +>Windows 95 with the network redirector + update installed</TD +></TR +><TR +><TD +>Windows 98 [se]</TD +></TR +><TR +><TD +>Windows 2000</TD +></TR +></TBODY +></TABLE +><P +></P +><P +><SPAN +CLASS="emphasis" +><I +CLASS="EMPHASIS" +>Note :</I +></SPAN +>All current release of + Microsoft SMB/CIFS clients support authentication via the + SMB Challenge/Response mechanism described here. Enabling + clear text authentication does not disable the ability + of the client to participate in encrypted authentication.</P +></TD +></TR +></TABLE +></DIV +><DIV +CLASS="SECT2" +><H2 +CLASS="SECT2" +><A +NAME="AEN346" +></A +>3.2.1. Advantages of SMB Encryption</H2 +><P +></P +><TABLE +BORDER="0" +><TBODY +><TR +><TD +>plain text passwords are not passed across + the network. Someone using a network sniffer cannot just + record passwords going to the SMB server.</TD +></TR +><TR +><TD +>WinNT doesn't like talking to a server + that isn't using SMB encrypted passwords. It will refuse + to browse the server if the server is also in user level + security mode. It will insist on prompting the user for the + password on each connection, which is very annoying. The + only things you can do to stop this is to use SMB encryption. + </TD +></TR +></TBODY +></TABLE +><P +></P +></DIV +><DIV +CLASS="SECT2" +><H2 +CLASS="SECT2" +><A +NAME="AEN351" +></A +>3.2.2. Advantages of non-encrypted passwords</H2 +><P +></P +><TABLE +BORDER="0" +><TBODY +><TR +><TD +>plain text passwords are not kept + on disk. </TD +></TR +><TR +><TD +>uses same password file as other unix + services such as login and ftp</TD +></TR +><TR +><TD +>you are probably already using other + services (such as telnet and ftp) which send plain text + passwords over the net, so sending them for SMB isn't + such a big deal.</TD +></TR +></TBODY +></TABLE +><P +></P +></DIV +></DIV +><DIV +CLASS="SECT1" +><H1 +CLASS="SECT1" +><A +NAME="AEN357" +></A +>3.3. The smbpasswd Command</H1 +><P +>The smbpasswd utility is a utility similar to the + <B +CLASS="COMMAND" +>passwd</B +> or <B +CLASS="COMMAND" +>yppasswd</B +> programs. + It maintains the two 32 byte password fields + in the passdb backend. </P +><P +><B +CLASS="COMMAND" +>smbpasswd</B +> works in a client-server mode + where it contacts the local smbd to change the user's password on its + behalf. This has enormous benefits - as follows.</P +><P +><B +CLASS="COMMAND" +>smbpasswd</B +> has the capability + to change passwords on Windows NT servers (this only works when + the request is sent to the NT Primary Domain Controller if you + are changing an NT Domain user's password).</P +><P +>To run smbpasswd as a normal user just type :</P +><P +><TT +CLASS="PROMPT" +>$ </TT +><TT +CLASS="USERINPUT" +><B +>smbpasswd</B +></TT +></P +><P +><TT +CLASS="PROMPT" +>Old SMB password: </TT +><TT +CLASS="USERINPUT" +><B +><type old value here - + or hit return if there was no old password></B +></TT +></P +><P +><TT +CLASS="PROMPT" +>New SMB Password: </TT +><TT +CLASS="USERINPUT" +><B +><type new value> + </B +></TT +></P +><P +><TT +CLASS="PROMPT" +>Repeat New SMB Password: </TT +><TT +CLASS="USERINPUT" +><B +><re-type new value + </B +></TT +></P +><P +>If the old value does not match the current value stored for + that user, or the two new values do not match each other, then the + password will not be changed.</P +><P +>If invoked by an ordinary user it will only allow the user + to change his or her own Samba password.</P +><P +>If run by the root user smbpasswd may take an optional + argument, specifying the user name whose SMB password you wish to + change. Note that when run as root smbpasswd does not prompt for + or check the old password value, thus allowing root to set passwords + for users who have forgotten their passwords.</P +><P +><B +CLASS="COMMAND" +>smbpasswd</B +> is designed to work in the same way + and be familiar to UNIX users who use the <B +CLASS="COMMAND" +>passwd</B +> or + <B +CLASS="COMMAND" +>yppasswd</B +> commands.</P +><P +>For more details on using <B +CLASS="COMMAND" +>smbpasswd</B +> refer + to the man page which will always be the definitive reference.</P +></DIV +><DIV +CLASS="SECT1" +><H1 +CLASS="SECT1" +><A +NAME="AEN388" +></A +>3.4. Plain text</H1 +><P +>Older versions of samba retrieved user information from the unix user database +and eventually some other fields from the file <TT +CLASS="FILENAME" +>/etc/samba/smbpasswd</TT +> +or <TT +CLASS="FILENAME" +>/etc/smbpasswd</TT +>. When password encryption is disabled, no +data is stored at all.</P +></DIV +><DIV +CLASS="SECT1" +><H1 +CLASS="SECT1" +><A +NAME="AEN393" +></A +>3.5. TDB</H1 +><P +>Samba can also store the user data in a "TDB" (Trivial Database). Using this backend +doesn't require any additional configuration. This backend is recommended for new installations who +don't require LDAP.</P +></DIV +><DIV +CLASS="SECT1" +><H1 +CLASS="SECT1" +><A +NAME="AEN396" +></A +>3.6. LDAP</H1 +><DIV +CLASS="SECT2" +><H2 +CLASS="SECT2" +><A +NAME="AEN398" +></A +>3.6.1. Introduction</H2 +><P +>This document describes how to use an LDAP directory for storing Samba user +account information traditionally stored in the smbpasswd(5) file. It is +assumed that the reader already has a basic understanding of LDAP concepts +and has a working directory server already installed. For more information +on LDAP architectures and Directories, please refer to the following sites.</P +><P +></P +><UL +><LI +><P +>OpenLDAP - <A +HREF="http://www.openldap.org/" +TARGET="_top" +>http://www.openldap.org/</A +></P +></LI +><LI +><P +>iPlanet Directory Server - <A +HREF="http://iplanet.netscape.com/directory" +TARGET="_top" +>http://iplanet.netscape.com/directory</A +></P +></LI +></UL +><P +>Note that <A +HREF="http://www.ora.com/" +TARGET="_top" +>O'Reilly Publishing</A +> is working on +a guide to LDAP for System Administrators which has a planned release date of +early summer, 2002.</P +><P +>Two additional Samba resources which may prove to be helpful are</P +><P +></P +><UL +><LI +><P +>The <A +HREF="http://www.unav.es/cti/ldap-smb/ldap-smb-3-howto.html" +TARGET="_top" +>Samba-PDC-LDAP-HOWTO</A +> + maintained by Ignacio Coupeau.</P +></LI +><LI +><P +>The NT migration scripts from <A +HREF="http://samba.idealx.org/" +TARGET="_top" +>IDEALX</A +> that are + geared to manage users and group in such a Samba-LDAP Domain Controller configuration. + </P +></LI +></UL +></DIV +><DIV +CLASS="SECT2" +><H2 +CLASS="SECT2" +><A +NAME="AEN418" +></A +>3.6.2. Introduction</H2 +><P +>Traditionally, when configuring <A +HREF="smb.conf.5.html#ENCRYPTPASSWORDS" +TARGET="_top" +>"encrypt +passwords = yes"</A +> in Samba's <TT +CLASS="FILENAME" +>smb.conf</TT +> file, user account +information such as username, LM/NT password hashes, password change times, and account +flags have been stored in the <TT +CLASS="FILENAME" +>smbpasswd(5)</TT +> file. There are several +disadvantages to this approach for sites with very large numbers of users (counted +in the thousands).</P +><P +></P +><UL +><LI +><P +>The first is that all lookups must be performed sequentially. Given that +there are approximately two lookups per domain logon (one for a normal +session connection such as when mapping a network drive or printer), this +is a performance bottleneck for lareg sites. What is needed is an indexed approach +such as is used in databases.</P +></LI +><LI +><P +>The second problem is that administrators who desired to replicate a +smbpasswd file to more than one Samba server were left to use external +tools such as <B +CLASS="COMMAND" +>rsync(1)</B +> and <B +CLASS="COMMAND" +>ssh(1)</B +> +and wrote custom, in-house scripts.</P +></LI +><LI +><P +>And finally, the amount of information which is stored in an +smbpasswd entry leaves no room for additional attributes such as +a home directory, password expiration time, or even a Relative +Identified (RID).</P +></LI +></UL +><P +>As a result of these defeciencies, a more robust means of storing user attributes +used by smbd was developed. The API which defines access to user accounts +is commonly referred to as the samdb interface (previously this was called the passdb +API, and is still so named in the CVS trees). In Samba 2.2.3, enabling support +for a samdb backend (e.g. <TT +CLASS="PARAMETER" +><I +>--with-ldapsam</I +></TT +> or +<TT +CLASS="PARAMETER" +><I +>--with-tdbsam</I +></TT +>) requires compile time support.</P +><P +>When compiling Samba to include the <TT +CLASS="PARAMETER" +><I +>--with-ldapsam</I +></TT +> autoconf +option, smbd (and associated tools) will store and lookup user accounts in +an LDAP directory. In reality, this is very easy to understand. If you are +comfortable with using an smbpasswd file, simply replace "smbpasswd" with +"LDAP directory" in all the documentation.</P +><P +>There are a few points to stress about what the <TT +CLASS="PARAMETER" +><I +>--with-ldapsam</I +></TT +> +does not provide. The LDAP support referred to in the this documentation does not +include:</P +><P +></P +><UL +><LI +><P +>A means of retrieving user account information from + an Windows 2000 Active Directory server.</P +></LI +><LI +><P +>A means of replacing /etc/passwd.</P +></LI +></UL +><P +>The second item can be accomplished by using LDAP NSS and PAM modules. LGPL +versions of these libraries can be obtained from PADL Software +(<A +HREF="http://www.padl.com/" +TARGET="_top" +>http://www.padl.com/</A +>). However, +the details of configuring these packages are beyond the scope of this document.</P +></DIV +><DIV +CLASS="SECT2" +><H2 +CLASS="SECT2" +><A +NAME="AEN447" +></A +>3.6.3. Supported LDAP Servers</H2 +><P +>The LDAP samdb code in 2.2.3 has been developed and tested using the OpenLDAP +2.0 server and client libraries. The same code should be able to work with +Netscape's Directory Server and client SDK. However, due to lack of testing +so far, there are bound to be compile errors and bugs. These should not be +hard to fix. If you are so inclined, please be sure to forward all patches to +<A +HREF="samba-patches@samba.org" +TARGET="_top" +>samba-patches@samba.org</A +> and +<A +HREF="jerry@samba.org" +TARGET="_top" +>jerry@samba.org</A +>.</P +></DIV +><DIV +CLASS="SECT2" +><H2 +CLASS="SECT2" +><A +NAME="AEN452" +></A +>3.6.4. Schema and Relationship to the RFC 2307 posixAccount</H2 +><P +>Samba 3.0 includes the necessary schema file for OpenLDAP 2.0 in +<TT +CLASS="FILENAME" +>examples/LDAP/samba.schema</TT +>. The sambaAccount objectclass is given here:</P +><P +><PRE +CLASS="PROGRAMLISTING" +>objectclass ( 1.3.1.5.1.4.1.7165.2.2.2 NAME 'sambaAccount' SUP top STRUCTURAL + DESC 'Samba Account' + MUST ( uid $ rid ) + MAY ( cn $ lmPassword $ ntPassword $ pwdLastSet $ logonTime $ + logoffTime $ kickoffTime $ pwdCanChange $ pwdMustChange $ acctFlags $ + displayName $ smbHome $ homeDrive $ scriptPath $ profilePath $ + description $ userWorkstations $ primaryGroupID $ domain ))</PRE +></P +><P +>The samba.schema file has been formatted for OpenLDAP 2.0. The OID's are +owned by the Samba Team and as such is legal to be openly published. +If you translate the schema to be used with Netscape DS, please +submit the modified schema file as a patch to <A +HREF="jerry@samba.org" +TARGET="_top" +>jerry@samba.org</A +></P +><P +>Just as the smbpasswd file is mean to store information which supplements a +user's <TT +CLASS="FILENAME" +>/etc/passwd</TT +> entry, so is the sambaAccount object +meant to supplement the UNIX user account information. A sambaAccount is a +<TT +CLASS="CONSTANT" +>STRUCTURAL</TT +> objectclass so it can be stored individually +in the directory. However, there are several fields (e.g. uid) which overlap +with the posixAccount objectclass outlined in RFC2307. This is by design.</P +><P +>In order to store all user account information (UNIX and Samba) in the directory, +it is necessary to use the sambaAccount and posixAccount objectclasses in +combination. However, smbd will still obtain the user's UNIX account +information via the standard C library calls (e.g. getpwnam(), et. al.). +This means that the Samba server must also have the LDAP NSS library installed +and functioning correctly. This division of information makes it possible to +store all Samba account information in LDAP, but still maintain UNIX account +information in NIS while the network is transitioning to a full LDAP infrastructure.</P +></DIV +><DIV +CLASS="SECT2" +><H2 +CLASS="SECT2" +><A +NAME="AEN464" +></A +>3.6.5. Configuring Samba with LDAP</H2 +><DIV +CLASS="SECT3" +><H3 +CLASS="SECT3" +><A +NAME="AEN466" +></A +>3.6.5.1. OpenLDAP configuration</H3 +><P +>To include support for the sambaAccount object in an OpenLDAP directory +server, first copy the samba.schema file to slapd's configuration directory.</P +><P +><TT +CLASS="PROMPT" +>root# </TT +><B +CLASS="COMMAND" +>cp samba.schema /etc/openldap/schema/</B +></P +><P +>Next, include the <TT +CLASS="FILENAME" +>samba.schema</TT +> file in <TT +CLASS="FILENAME" +>slapd.conf</TT +>. +The sambaAccount object contains two attributes which depend upon other schema +files. The 'uid' attribute is defined in <TT +CLASS="FILENAME" +>cosine.schema</TT +> and +the 'displayName' attribute is defined in the <TT +CLASS="FILENAME" +>inetorgperson.schema</TT +> +file. Both of these must be included before the <TT +CLASS="FILENAME" +>samba.schema</TT +> file.</P +><P +><PRE +CLASS="PROGRAMLISTING" +>## /etc/openldap/slapd.conf + +## schema files (core.schema is required by default) +include /etc/openldap/schema/core.schema + +## needed for sambaAccount +include /etc/openldap/schema/cosine.schema +include /etc/openldap/schema/inetorgperson.schema +include /etc/openldap/schema/samba.schema + +## uncomment this line if you want to support the RFC2307 (NIS) schema +## include /etc/openldap/schema/nis.schema + +....</PRE +></P +><P +>It is recommended that you maintain some indices on some of the most usefull attributes, +like in the following example, to speed up searches made on sambaAccount objectclasses +(and possibly posixAccount and posixGroup as well).</P +><P +><PRE +CLASS="PROGRAMLISTING" +># Indices to maintain +## required by OpenLDAP 2.0 +index objectclass eq + +## support pb_getsampwnam() +index uid pres,eq +## support pdb_getsambapwrid() +index rid eq + +## uncomment these if you are storing posixAccount and +## posixGroup entries in the directory as well +##index uidNumber eq +##index gidNumber eq +##index cn eq +##index memberUid eq</PRE +></P +></DIV +><DIV +CLASS="SECT3" +><H3 +CLASS="SECT3" +><A +NAME="AEN483" +></A +>3.6.5.2. Configuring Samba</H3 +><P +>The following parameters are available in smb.conf only with <TT +CLASS="PARAMETER" +><I +>--with-ldapsam</I +></TT +> +was included with compiling Samba.</P +><P +></P +><UL +><LI +><P +><A +HREF="smb.conf.5.html#LDAPSSL" +TARGET="_top" +>ldap ssl</A +></P +></LI +><LI +><P +><A +HREF="smb.conf.5.html#LDAPSERVER" +TARGET="_top" +>ldap server</A +></P +></LI +><LI +><P +><A +HREF="smb.conf.5.html#LDAPADMINDN" +TARGET="_top" +>ldap admin dn</A +></P +></LI +><LI +><P +><A +HREF="smb.conf.5.html#LDAPSUFFIX" +TARGET="_top" +>ldap suffix</A +></P +></LI +><LI +><P +><A +HREF="smb.conf.5.html#LDAPFILTER" +TARGET="_top" +>ldap filter</A +></P +></LI +><LI +><P +><A +HREF="smb.conf.5.html#LDAPPORT" +TARGET="_top" +>ldap port</A +></P +></LI +></UL +><P +>These are described in the <A +HREF="smb.conf.5.html" +TARGET="_top" +>smb.conf(5)</A +> man +page and so will not be repeated here. However, a sample smb.conf file for +use with an LDAP directory could appear as</P +><P +><PRE +CLASS="PROGRAMLISTING" +>## /usr/local/samba/lib/smb.conf +[global] + security = user + encrypt passwords = yes + + netbios name = TASHTEGO + workgroup = NARNIA + + # ldap related parameters + + # define the DN to use when binding to the directory servers + # The password for this DN is not stored in smb.conf. Rather it + # must be set by using 'smbpasswd -w <TT +CLASS="REPLACEABLE" +><I +>secretpw</I +></TT +>' to store the + # passphrase in the secrets.tdb file. If the "ldap admin dn" values + # changes, this password will need to be reset. + ldap admin dn = "cn=Samba Manager,ou=people,dc=samba,dc=org" + + # specify the LDAP server's hostname (defaults to locahost) + ldap server = ahab.samba.org + + # Define the SSL option when connecting to the directory + # ('off', 'start tls', or 'on' (default)) + ldap ssl = start tls + + # define the port to use in the LDAP session (defaults to 636 when + # "ldap ssl = on") + ldap port = 389 + + # specify the base DN to use when searching the directory + ldap suffix = "ou=people,dc=samba,dc=org" + + # generally the default ldap search filter is ok + # ldap filter = "(&(uid=%u)(objectclass=sambaAccount))"</PRE +></P +></DIV +></DIV +><DIV +CLASS="SECT2" +><H2 +CLASS="SECT2" +><A +NAME="AEN511" +></A +>3.6.6. Accounts and Groups management</H2 +><P +>As users accounts are managed thru the sambaAccount objectclass, you should +modify you existing administration tools to deal with sambaAccount attributes.</P +><P +>Machines accounts are managed with the sambaAccount objectclass, just +like users accounts. However, it's up to you to stored thoses accounts +in a different tree of you LDAP namespace: you should use +"ou=Groups,dc=plainjoe,dc=org" to store groups and +"ou=People,dc=plainjoe,dc=org" to store users. Just configure your +NSS and PAM accordingly (usually, in the /etc/ldap.conf configuration +file).</P +><P +>In Samba release 3.0, the group management system is based on posix +groups. This means that Samba make usage of the posixGroup objectclass. +For now, there is no NT-like group system management (global and local +groups).</P +></DIV +><DIV +CLASS="SECT2" +><H2 +CLASS="SECT2" +><A +NAME="AEN516" +></A +>3.6.7. Security and sambaAccount</H2 +><P +>There are two important points to remember when discussing the security +of sambaAccount entries in the directory.</P +><P +></P +><UL +><LI +><P +><SPAN +CLASS="emphasis" +><I +CLASS="EMPHASIS" +>Never</I +></SPAN +> retrieve the lmPassword or + ntPassword attribute values over an unencrypted LDAP session.</P +></LI +><LI +><P +><SPAN +CLASS="emphasis" +><I +CLASS="EMPHASIS" +>Never</I +></SPAN +> allow non-admin users to + view the lmPassword or ntPassword attribute values.</P +></LI +></UL +><P +>These password hashes are clear text equivalents and can be used to impersonate +the user without deriving the original clear text strings. For more information +on the details of LM/NT password hashes, refer to the <A +HREF="ENCRYPTION.html" +TARGET="_top" +>ENCRYPTION chapter</A +> of the Samba-HOWTO-Collection.</P +><P +>To remedy the first security issue, the "ldap ssl" smb.conf parameter defaults +to require an encrypted session (<B +CLASS="COMMAND" +>ldap ssl = on</B +>) using +the default port of 636 +when contacting the directory server. When using an OpenLDAP 2.0 server, it +is possible to use the use the StartTLS LDAP extended operation in the place of +LDAPS. In either case, you are strongly discouraged to disable this security +(<B +CLASS="COMMAND" +>ldap ssl = off</B +>).</P +><P +>Note that the LDAPS protocol is deprecated in favor of the LDAPv3 StartTLS +extended operation. However, the OpenLDAP library still provides support for +the older method of securing communication between clients and servers.</P +><P +>The second security precaution is to prevent non-administrative users from +harvesting password hashes from the directory. This can be done using the +following ACL in <TT +CLASS="FILENAME" +>slapd.conf</TT +>:</P +><P +><PRE +CLASS="PROGRAMLISTING" +>## allow the "ldap admin dn" access, but deny everyone else +access to attrs=lmPassword,ntPassword + by dn="cn=Samba Admin,ou=people,dc=plainjoe,dc=org" write + by * none</PRE +></P +></DIV +><DIV +CLASS="SECT2" +><H2 +CLASS="SECT2" +><A +NAME="AEN536" +></A +>3.6.8. LDAP specials attributes for sambaAccounts</H2 +><P +>The sambaAccount objectclass is composed of the following attributes:</P +><P +></P +><UL +><LI +><P +><TT +CLASS="CONSTANT" +>lmPassword</TT +>: the LANMAN password 16-byte hash stored as a character + representation of a hexidecimal string.</P +></LI +><LI +><P +><TT +CLASS="CONSTANT" +>ntPassword</TT +>: the NT password hash 16-byte stored as a character + representation of a hexidecimal string.</P +></LI +><LI +><P +><TT +CLASS="CONSTANT" +>pwdLastSet</TT +>: The integer time in seconds since 1970 when the + <TT +CLASS="CONSTANT" +>lmPassword</TT +> and <TT +CLASS="CONSTANT" +>ntPassword</TT +> attributes were last set. + </P +></LI +><LI +><P +><TT +CLASS="CONSTANT" +>acctFlags</TT +>: string of 11 characters surrounded by square brackets [] + representing account flags such as U (user), W(workstation), X(no password expiration), and + D(disabled).</P +></LI +><LI +><P +><TT +CLASS="CONSTANT" +>logonTime</TT +>: Integer value currently unused</P +></LI +><LI +><P +><TT +CLASS="CONSTANT" +>logoffTime</TT +>: Integer value currently unused</P +></LI +><LI +><P +><TT +CLASS="CONSTANT" +>kickoffTime</TT +>: Integer value currently unused</P +></LI +><LI +><P +><TT +CLASS="CONSTANT" +>pwdCanChange</TT +>: Integer value currently unused</P +></LI +><LI +><P +><TT +CLASS="CONSTANT" +>pwdMustChange</TT +>: Integer value currently unused</P +></LI +><LI +><P +><TT +CLASS="CONSTANT" +>homeDrive</TT +>: specifies the drive letter to which to map the + UNC path specified by homeDirectory. The drive letter must be specified in the form "X:" + where X is the letter of the drive to map. Refer to the "logon drive" parameter in the + smb.conf(5) man page for more information.</P +></LI +><LI +><P +><TT +CLASS="CONSTANT" +>scriptPath</TT +>: The scriptPath property specifies the path of + the user's logon script, .CMD, .EXE, or .BAT file. The string can be null. The path + is relative to the netlogon share. Refer to the "logon script" parameter in the + smb.conf(5) man page for more information.</P +></LI +><LI +><P +><TT +CLASS="CONSTANT" +>profilePath</TT +>: specifies a path to the user's profile. + This value can be a null string, a local absolute path, or a UNC path. Refer to the + "logon path" parameter in the smb.conf(5) man page for more information.</P +></LI +><LI +><P +><TT +CLASS="CONSTANT" +>smbHome</TT +>: The homeDirectory property specifies the path of + the home directory for the user. The string can be null. If homeDrive is set and specifies + a drive letter, homeDirectory should be a UNC path. The path must be a network + UNC path of the form \\server\share\directory. This value can be a null string. + Refer to the "logon home" parameter in the smb.conf(5) man page for more information. + </P +></LI +><LI +><P +><TT +CLASS="CONSTANT" +>userWorkstation</TT +>: character string value currently unused. + </P +></LI +><LI +><P +><TT +CLASS="CONSTANT" +>rid</TT +>: the integer representation of the user's relative identifier + (RID).</P +></LI +><LI +><P +><TT +CLASS="CONSTANT" +>primaryGroupID</TT +>: the relative identifier (RID) of the primary group + of the user.</P +></LI +></UL +><P +>The majority of these parameters are only used when Samba is acting as a PDC of +a domain (refer to the <A +HREF="Samba-PDC-HOWTO.html" +TARGET="_top" +>Samba-PDC-HOWTO</A +> for details on +how to configure Samba as a Primary Domain Controller). The following four attributes +are only stored with the sambaAccount entry if the values are non-default values:</P +><P +></P +><UL +><LI +><P +>smbHome</P +></LI +><LI +><P +>scriptPath</P +></LI +><LI +><P +>logonPath</P +></LI +><LI +><P +>homeDrive</P +></LI +></UL +><P +>These attributes are only stored with the sambaAccount entry if +the values are non-default values. For example, assume TASHTEGO has now been +configured as a PDC and that <B +CLASS="COMMAND" +>logon home = \\%L\%u</B +> was defined in +its <TT +CLASS="FILENAME" +>smb.conf</TT +> file. When a user named "becky" logons to the domain, +the <TT +CLASS="PARAMETER" +><I +>logon home</I +></TT +> string is expanded to \\TASHTEGO\becky. +If the smbHome attribute exists in the entry "uid=becky,ou=people,dc=samba,dc=org", +this value is used. However, if this attribute does not exist, then the value +of the <TT +CLASS="PARAMETER" +><I +>logon home</I +></TT +> parameter is used in its place. Samba +will only write the attribute value to the directory entry is the value is +something other than the default (e.g. \\MOBY\becky).</P +></DIV +><DIV +CLASS="SECT2" +><H2 +CLASS="SECT2" +><A +NAME="AEN606" +></A +>3.6.9. Example LDIF Entries for a sambaAccount</H2 +><P +>The following is a working LDIF with the inclusion of the posixAccount objectclass:</P +><P +><PRE +CLASS="PROGRAMLISTING" +>dn: uid=guest2, ou=people,dc=plainjoe,dc=org +ntPassword: 878D8014606CDA29677A44EFA1353FC7 +pwdMustChange: 2147483647 +primaryGroupID: 1201 +lmPassword: 552902031BEDE9EFAAD3B435B51404EE +pwdLastSet: 1010179124 +logonTime: 0 +objectClass: sambaAccount +uid: guest2 +kickoffTime: 2147483647 +acctFlags: [UX ] +logoffTime: 2147483647 +rid: 19006 +pwdCanChange: 0</PRE +></P +><P +>The following is an LDIF entry for using both the sambaAccount and +posixAccount objectclasses:</P +><P +><PRE +CLASS="PROGRAMLISTING" +>dn: uid=gcarter, ou=people,dc=plainjoe,dc=org +logonTime: 0 +displayName: Gerald Carter +lmPassword: 552902031BEDE9EFAAD3B435B51404EE +primaryGroupID: 1201 +objectClass: posixAccount +objectClass: sambaAccount +acctFlags: [UX ] +userPassword: {crypt}BpM2ej8Rkzogo +uid: gcarter +uidNumber: 9000 +cn: Gerald Carter +loginShell: /bin/bash +logoffTime: 2147483647 +gidNumber: 100 +kickoffTime: 2147483647 +pwdLastSet: 1010179230 +rid: 19000 +homeDirectory: /home/tashtego/gcarter +pwdCanChange: 0 +pwdMustChange: 2147483647 +ntPassword: 878D8014606CDA29677A44EFA1353FC7</PRE +></P +></DIV +></DIV +><DIV +CLASS="SECT1" +><H1 +CLASS="SECT1" +><A +NAME="AEN614" +></A +>3.7. MySQL</H1 +><DIV +CLASS="SECT2" +><H2 +CLASS="SECT2" +><A +NAME="AEN616" +></A +>3.7.1. Building</H2 +><P +>To build the plugin, run <B +CLASS="COMMAND" +>make bin/pdb_mysql.so</B +> +in the <TT +CLASS="FILENAME" +>source/</TT +> directory of samba distribution. </P +><P +>Next, copy pdb_mysql.so to any location you want. I +strongly recommend installing it in $PREFIX/lib or /usr/lib/samba/</P +></DIV +><DIV +CLASS="SECT2" +><H2 +CLASS="SECT2" +><A +NAME="AEN622" +></A +>3.7.2. Creating the database</H2 +><P +>You either can set up your own table and specify the field names to pdb_mysql (see below +for the column names) or use the default table. The file <TT +CLASS="FILENAME" +>examples/pdb/mysql/mysql.dump</TT +> +contains the correct queries to create the required tables. Use the command : + +<B +CLASS="COMMAND" +>mysql -u<TT +CLASS="REPLACEABLE" +><I +>username</I +></TT +> -h<TT +CLASS="REPLACEABLE" +><I +>hostname</I +></TT +> -p<TT +CLASS="REPLACEABLE" +><I +>password</I +></TT +> <TT +CLASS="REPLACEABLE" +><I +>databasename</I +></TT +> < <TT +CLASS="FILENAME" +>/path/to/samba/examples/pdb/mysql/mysql.dump</TT +></B +> </P +></DIV +><DIV +CLASS="SECT2" +><H2 +CLASS="SECT2" +><A +NAME="AEN632" +></A +>3.7.3. Configuring</H2 +><P +>This plugin lacks some good documentation, but here is some short info:</P +><P +>Add a the following to the <B +CLASS="COMMAND" +>passdb backend</B +> variable in your <TT +CLASS="FILENAME" +>smb.conf</TT +>: +<PRE +CLASS="PROGRAMLISTING" +>passdb backend = [other-plugins] plugin:/location/to/pdb_mysql.so:identifier [other-plugins]</PRE +></P +><P +>The identifier can be any string you like, as long as it doesn't collide with +the identifiers of other plugins or other instances of pdb_mysql. If you +specify multiple pdb_mysql.so entries in 'passdb backend', you also need to +use different identifiers!</P +><P +>Additional options can be given thru the smb.conf file in the [global] section.</P +><P +><PRE +CLASS="PROGRAMLISTING" +>identifier:mysql host - host name, defaults to 'localhost' +identifier:mysql password +identifier:mysql user - defaults to 'samba' +identifier:mysql database - defaults to 'samba' +identifier:mysql port - defaults to 3306 +identifier:table - Name of the table containing users</PRE +></P +><DIV +CLASS="WARNING" +><P +></P +><TABLE +CLASS="WARNING" +WIDTH="100%" +BORDER="0" +><TR +><TD +WIDTH="25" +ALIGN="CENTER" +VALIGN="TOP" +><IMG +SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/warning.gif" +HSPACE="5" +ALT="Warning"></TD +><TD +ALIGN="LEFT" +VALIGN="TOP" +><P +>Since the password for the mysql user is stored in the +smb.conf file, you should make the the smb.conf file +readable only to the user that runs samba. This is considered a security +bug and will be fixed soon.</P +></TD +></TR +></TABLE +></DIV +><P +>Names of the columns in this table(I've added column types those columns should have first):</P +><P +><PRE +CLASS="PROGRAMLISTING" +>identifier:logon time column - int(9) +identifier:logoff time column - int(9) +identifier:kickoff time column - int(9) +identifier:pass last set time column - int(9) +identifier:pass can change time column - int(9) +identifier:pass must change time column - int(9) +identifier:username column - varchar(255) - unix username +identifier:domain column - varchar(255) - NT domain user is part of +identifier:nt username column - varchar(255) - NT username +identifier:fullname column - varchar(255) - Full name of user +identifier:home dir column - varchar(255) - Unix homedir path +identifier:dir drive column - varchar(2) - Directory drive path (eg: 'H:') +identifier:logon script column - varchar(255) - Batch file to run on client side when logging on +identifier:profile path column - varchar(255) - Path of profile +identifier:acct desc column - varchar(255) - Some ASCII NT user data +identifier:workstations column - varchar(255) - Workstations user can logon to (or NULL for all) +identifier:unknown string column - varchar(255) - unknown string +identifier:munged dial column - varchar(255) - ? +identifier:uid column - int(9) - Unix user ID (uid) +identifier:gid column - int(9) - Unix user group (gid) +identifier:user sid column - varchar(255) - NT user SID +identifier:group sid column - varchar(255) - NT group ID +identifier:lanman pass column - varchar(255) - encrypted lanman password +identifier:nt pass column - varchar(255) - encrypted nt passwd +identifier:plain pass column - varchar(255) - plaintext password +identifier:acct control column - int(9) - nt user data +identifier:unknown 3 column - int(9) - unknown +identifier:logon divs column - int(9) - ? +identifier:hours len column - int(9) - ? +identifier:unknown 5 column - int(9) - unknown +identifier:unknown 6 column - int(9) - unknown</PRE +></P +><P +>Eventually, you can put a colon (:) after the name of each column, which +should specify the column to update when updating the table. You can also +specify nothing behind the colon - then the data from the field will not be +updated. </P +></DIV +><DIV +CLASS="SECT2" +><H2 +CLASS="SECT2" +><A +NAME="AEN649" +></A +>3.7.4. Using plaintext passwords or encrypted password</H2 +><P +>I strongly discourage the use of plaintext passwords, however, you can use them:</P +><P +>If you would like to use plaintext passwords, set 'identifier:lanman pass column' and 'identifier:nt pass column' to 'NULL' (without the quotes) and 'identifier:plain pass column' to the name of the column containing the plaintext passwords. </P +><P +>If you use encrypted passwords, set the 'identifier:plain pass column' to 'NULL' (without the quotes). This is the default.</P +></DIV +><DIV +CLASS="SECT2" +><H2 +CLASS="SECT2" +><A +NAME="AEN654" +></A +>3.7.5. Getting non-column data from the table</H2 +><P +>It is possible to have not all data in the database and making some 'constant'.</P +><P +>For example, you can set 'identifier:fullname column' to : +<B +CLASS="COMMAND" +>CONCAT(First_name,' ',Sur_name)</B +></P +><P +>Or, set 'identifier:workstations column' to : +<B +CLASS="COMMAND" +>NULL</B +></P +><P +>See the MySQL documentation for more language constructs.</P +></DIV +></DIV +><DIV +CLASS="SECT1" +><H1 +CLASS="SECT1" +><A +NAME="AEN662" +></A +>3.8. Passdb XML plugin</H1 +><DIV +CLASS="SECT2" +><H2 +CLASS="SECT2" +><A +NAME="AEN664" +></A +>3.8.1. Building</H2 +><P +>This module requires libxml2 to be installed.</P +><P +>To build pdb_xml, run: <B +CLASS="COMMAND" +>make bin/pdb_xml.so</B +> in +the directory <TT +CLASS="FILENAME" +>source/</TT +>. </P +></DIV +><DIV +CLASS="SECT2" +><H2 +CLASS="SECT2" +><A +NAME="AEN670" +></A +>3.8.2. Usage</H2 +><P +>The usage of pdb_xml is pretty straightforward. To export data, use: + +<B +CLASS="COMMAND" +>pdbedit -e plugin:/usr/lib/samba/pdb_xml.so:filename</B +> + +(where filename is the name of the file to put the data in)</P +><P +>To import data, use: +<B +CLASS="COMMAND" +>pdbedit -i plugin:/usr/lib/samba/pdb_xml.so:filename -e current-pdb</B +> + +Where filename is the name to read the data from and current-pdb to put it in.</P +></DIV +></DIV +></DIV +><DIV +CLASS="NAVFOOTER" +><HR +ALIGN="LEFT" +WIDTH="100%"><TABLE +SUMMARY="Footer navigation table" +WIDTH="100%" +BORDER="0" +CELLPADDING="0" +CELLSPACING="0" +><TR +><TD +WIDTH="33%" +ALIGN="left" +VALIGN="top" +><A +HREF="browsing-quick.html" +ACCESSKEY="P" +>Prev</A +></TD +><TD +WIDTH="34%" +ALIGN="center" +VALIGN="top" +><A +HREF="samba-howto-collection.html" +ACCESSKEY="H" +>Home</A +></TD +><TD +WIDTH="33%" +ALIGN="right" +VALIGN="top" +><A +HREF="type.html" +ACCESSKEY="N" +>Next</A +></TD +></TR +><TR +><TD +WIDTH="33%" +ALIGN="left" +VALIGN="top" +>Quick Cross Subnet Browsing / Cross Workgroup Browsing guide</TD +><TD +WIDTH="34%" +ALIGN="center" +VALIGN="top" +><A +HREF="introduction.html" +ACCESSKEY="U" +>Up</A +></TD +><TD +WIDTH="33%" +ALIGN="right" +VALIGN="top" +>Type of installation</TD +></TR +></TABLE +></DIV +></BODY +></HTML +>
\ No newline at end of file diff --git a/docs/htmldocs/pdb-mysql.html b/docs/htmldocs/pdb-mysql.html index abca946f6f..e98d0c30d0 100644 --- a/docs/htmldocs/pdb-mysql.html +++ b/docs/htmldocs/pdb-mysql.html @@ -5,8 +5,7 @@ >Passdb MySQL plugin</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ -"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -73,13 +72,17 @@ WIDTH="100%"></DIV CLASS="CHAPTER" ><H1 ><A -NAME="PDB-MYSQL">Chapter 16. Passdb MySQL plugin</H1 +NAME="PDB-MYSQL" +></A +>Chapter 16. Passdb MySQL plugin</H1 ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2566">16.1. Building</H1 +NAME="AEN2562" +></A +>16.1. Building</H1 ><P >To build the plugin, run <B CLASS="COMMAND" @@ -98,7 +101,53 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2572">16.2. Configuring</H1 +NAME="AEN2568" +></A +>16.2. Creating the database</H1 +><P +>You either can set up your own table and specify the field names to pdb_mysql (see below +for the column names) or use the default table. The file <TT +CLASS="FILENAME" +>examples/pdb/mysql/mysql.dump</TT +> +contains the correct queries to create the required tables. Use the command : + +<B +CLASS="COMMAND" +>mysql -u<TT +CLASS="REPLACEABLE" +><I +>username</I +></TT +> -h<TT +CLASS="REPLACEABLE" +><I +>hostname</I +></TT +> -p<TT +CLASS="REPLACEABLE" +><I +>password</I +></TT +> <TT +CLASS="REPLACEABLE" +><I +>databasename</I +></TT +> < <TT +CLASS="FILENAME" +>/path/to/samba/examples/pdb/mysql/mysql.dump</TT +></B +> </P +></DIV +><DIV +CLASS="SECT1" +><H1 +CLASS="SECT1" +><A +NAME="AEN2578" +></A +>16.3. Configuring</H1 ><P >This plugin lacks some good documentation, but here is some short info:</P ><P @@ -189,7 +238,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2589">16.3. Using plaintext passwords or encrypted password</H1 +NAME="AEN2595" +></A +>16.4. Using plaintext passwords or encrypted password</H1 ><P >I strongly discourage the use of plaintext passwords, however, you can use them:</P ><P @@ -202,7 +253,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2594">16.4. Getting non-column data from the table</H1 +NAME="AEN2600" +></A +>16.5. Getting non-column data from the table</H1 ><P >It is possible to have not all data in the database and making some 'constant'.</P ><P diff --git a/docs/htmldocs/pdb-xml.html b/docs/htmldocs/pdb-xml.html index 4d300d7be0..1b419dcc74 100644 --- a/docs/htmldocs/pdb-xml.html +++ b/docs/htmldocs/pdb-xml.html @@ -5,8 +5,7 @@ >Passdb XML plugin</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ -"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -73,13 +72,17 @@ WIDTH="100%"></DIV CLASS="CHAPTER" ><H1 ><A -NAME="PDB-XML">Chapter 17. Passdb XML plugin</H1 +NAME="PDB-XML" +></A +>Chapter 17. Passdb XML plugin</H1 ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2613">17.1. Building</H1 +NAME="AEN2619" +></A +>17.1. Building</H1 ><P >This module requires libxml2 to be installed.</P ><P @@ -97,7 +100,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2619">17.2. Usage</H1 +NAME="AEN2625" +></A +>17.2. Usage</H1 ><P >The usage of pdb_xml is pretty straightforward. To export data, use: diff --git a/docs/htmldocs/pdbedit.8.html b/docs/htmldocs/pdbedit.8.html index e3cf1e4fba..14497f522c 100644 --- a/docs/htmldocs/pdbedit.8.html +++ b/docs/htmldocs/pdbedit.8.html @@ -1,12 +1,11 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"> +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <HTML ><HEAD ><TITLE >pdbedit</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ -"></HEAD +CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"></HEAD ><BODY CLASS="REFENTRY" BGCOLOR="#FFFFFF" @@ -16,7 +15,9 @@ VLINK="#840084" ALINK="#0000FF" ><H1 ><A -NAME="PDBEDIT">pdbedit</H1 +NAME="PDBEDIT.8" +></A +>pdbedit</H1 ><DIV CLASS="REFNAMEDIV" ><A @@ -28,13 +29,15 @@ NAME="AEN5" ><DIV CLASS="REFSYNOPSISDIV" ><A -NAME="AEN8"><H2 +NAME="AEN8" +></A +><H2 >Synopsis</H2 ><P ><B CLASS="COMMAND" >pdbedit</B -> [-l] [-v] [-w] [-u username] [-f fullname] [-h homedir] [-D drive] [-S script] [-p profile] [-a] [-m] [-x] [-i passdb-backend] [-e passdb-backend] [-b passdb-backend] [-d debuglevel] [-s configfile] [-P account-policy] [-V value]</P +> [-l] [-v] [-w] [-u username] [-f fullname] [-h homedir] [-D drive] [-S script] [-p profile] [-a] [-m] [-x] [-i passdb-backend] [-e passdb-backend] [-b passdb-backend] [-d debuglevel] [-s configfile] [-P account-policy] [-V value]</P ></DIV ><DIV CLASS="REFSECT1" @@ -44,10 +47,12 @@ NAME="AEN30" ><H2 >DESCRIPTION</H2 ><P ->This tool is part of the <A -HREF="samba.7.html" -TARGET="_top" -> Samba</A +>This tool is part of the <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>Samba</SPAN +>(7)</SPAN > suite.</P ><P >The pdbedit program is used to manage the users accounts @@ -65,7 +70,7 @@ TARGET="_top" ><DIV CLASS="REFSECT1" ><A -NAME="AEN37" +NAME="AEN39" ></A ><H2 >OPTIONS</H2 @@ -88,20 +93,10 @@ CLASS="COMMAND" >pdbedit -l</B ></P ><P -><TABLE -BORDER="0" -BGCOLOR="#E0E0E0" -WIDTH="90%" -><TR -><TD ><PRE -CLASS="PROGRAMLISTING" -> sorce:500:Simo Sorce - samba:45:Test User - </PRE -></TD -></TR -></TABLE +CLASS="SCREEN" +>sorce:500:Simo Sorce +samba:45:Test User</PRE ></P ></DD ><DT @@ -117,36 +112,26 @@ CLASS="COMMAND" >pdbedit -l -v</B ></P ><P -><TABLE -BORDER="0" -BGCOLOR="#E0E0E0" -WIDTH="90%" -><TR -><TD ><PRE -CLASS="PROGRAMLISTING" -> --------------- - username: sorce - user ID/Group: 500/500 - user RID/GRID: 2000/2001 - Full Name: Simo Sorce - Home Directory: \\BERSERKER\sorce - HomeDir Drive: H: - Logon Script: \\BERSERKER\netlogon\sorce.bat - Profile Path: \\BERSERKER\profile - --------------- - username: samba - user ID/Group: 45/45 - user RID/GRID: 1090/1091 - Full Name: Test User - Home Directory: \\BERSERKER\samba - HomeDir Drive: - Logon Script: - Profile Path: \\BERSERKER\profile - </PRE -></TD -></TR -></TABLE +CLASS="SCREEN" +>--------------- +username: sorce +user ID/Group: 500/500 +user RID/GRID: 2000/2001 +Full Name: Simo Sorce +Home Directory: \\BERSERKER\sorce +HomeDir Drive: H: +Logon Script: \\BERSERKER\netlogon\sorce.bat +Profile Path: \\BERSERKER\profile +--------------- +username: samba +user ID/Group: 45/45 +user RID/GRID: 1090/1091 +Full Name: Test User +Home Directory: \\BERSERKER\samba +HomeDir Drive: +Logon Script: +Profile Path: \\BERSERKER\profile</PRE ></P ></DD ><DT @@ -159,35 +144,23 @@ CLASS="PROGRAMLISTING" <TT CLASS="FILENAME" >smbpasswd</TT -> file format. (see the <A -HREF="smbpasswd.5.html" -TARGET="_top" -><TT -CLASS="FILENAME" ->smbpasswd(5)</TT -></A +> file format. (see the + <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbpasswd</SPAN +>(5)</SPAN > for details)</P ><P >Example: <B CLASS="COMMAND" >pdbedit -l -w</B ></P -><P -><TABLE -BORDER="0" -BGCOLOR="#E0E0E0" -WIDTH="90%" -><TR -><TD ><PRE -CLASS="PROGRAMLISTING" -> sorce:500:508818B733CE64BEAAD3B435B51404EE:D2A2418EFC466A8A0F6B1DBB5C3DB80C:[UX ]:LCT-00000000: - samba:45:0F2B255F7B67A7A9AAD3B435B51404EE:BC281CE3F53B6A5146629CD4751D3490:[UX ]:LCT-3BFA1E8D: - </PRE -></TD -></TR -></TABLE -></P +CLASS="SCREEN" +>sorce:500:508818B733CE64BEAAD3B435B51404EE:D2A2418EFC466A8A0F6B1DBB5C3DB80C:[UX ]:LCT-00000000: +samba:45:0F2B255F7B67A7A9AAD3B435B51404EE:BC281CE3F53B6A5146629CD4751D3490:[UX ]:LCT-3BFA1E8D:</PRE ></DD ><DT >-u username</DT @@ -195,13 +168,19 @@ CLASS="PROGRAMLISTING" ><P >This option specifies the username to be used for the operation requested (listing, adding, removing). - It is <I + It is <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >required</I +></SPAN > in add, remove and modify - operations and <I + operations and <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >optional</I +></SPAN > in list operations.</P ></DD @@ -287,21 +266,11 @@ CLASS="COMMAND" CLASS="COMMAND" >pdbedit -a -u sorce</B > - <TABLE -BORDER="0" -BGCOLOR="#E0E0E0" -WIDTH="90%" -><TR -><TD -><PRE +<PRE CLASS="PROGRAMLISTING" >new password: - retype new password</PRE -></TD -></TR -></TABLE -> - </P +retype new password</PRE +></P ></DD ><DT >-m</DT @@ -394,19 +363,9 @@ CLASS="COMMAND" >pdbedit -P "bad lockout attempt"</B ></P ><P -><TABLE -BORDER="0" -BGCOLOR="#E0E0E0" -WIDTH="90%" -><TR -><TD ><PRE CLASS="PROGRAMLISTING" -> account policy value for bad lockout attempt is 0 - </PRE -></TD -></TR -></TABLE +>account policy value for bad lockout attempt is 0</PRE ></P ></DD ><DT @@ -428,20 +387,10 @@ CLASS="COMMAND" >pdbedit -P "bad lockout attempt" -V 3</B ></P ><P -><TABLE -BORDER="0" -BGCOLOR="#E0E0E0" -WIDTH="90%" -><TR -><TD ><PRE CLASS="PROGRAMLISTING" -> account policy value for bad lockout attempt was 0 - account policy value for bad lockout attempt is now 3 - </PRE -></TD -></TR -></TABLE +>account policy value for bad lockout attempt was 0 +account policy value for bad lockout attempt is now 3</PRE ></P ></DD ><DT @@ -492,7 +441,7 @@ CLASS="FILENAME" >Print a summary of command line options.</P ></DD ><DT ->-s <configuration file></DT +>-s <configuration file></DT ><DD ><P >The file specified contains the @@ -517,7 +466,7 @@ compile time.</P ><DIV CLASS="REFSECT1" ><A -NAME="AEN182" +NAME="AEN184" ></A ><H2 >NOTES</H2 @@ -527,7 +476,7 @@ NAME="AEN182" ><DIV CLASS="REFSECT1" ><A -NAME="AEN185" +NAME="AEN187" ></A ><H2 >VERSION</H2 @@ -538,27 +487,29 @@ NAME="AEN185" ><DIV CLASS="REFSECT1" ><A -NAME="AEN188" +NAME="AEN190" ></A ><H2 >SEE ALSO</H2 ><P -><A -HREF="smbpasswd.8.html" -TARGET="_top" ->smbpasswd(8)</A ->, - <A -HREF="samba.7.html" -TARGET="_top" ->samba(7)</A -> - </P +><SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbpasswd</SPAN +>(5)</SPAN +>, <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>samba</SPAN +>(7)</SPAN +></P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN193" +NAME="AEN199" ></A ><H2 >AUTHOR</H2 @@ -570,14 +521,14 @@ NAME="AEN193" ><P >The original Samba man pages were written by Karl Auer. The man page sources were converted to YODL format (another - excellent piece of Open Source software, available at - <A + excellent piece of Open Source software, available at <A HREF="ftp://ftp.icce.rug.nl/pub/unix/" TARGET="_top" > ftp://ftp.icce.rug.nl/pub/unix/</A >) and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for - Samba 2.2 was done by Gerald Carter</P + Samba 2.2 was done by Gerald Carter. The conversion to DocBook + XML 4.2 for Samba 3.0 was done by Alexander Bokovoy.</P ></DIV ></BODY ></HTML diff --git a/docs/htmldocs/portability.html b/docs/htmldocs/portability.html index 424fbe5c6c..4942cdb1bb 100644 --- a/docs/htmldocs/portability.html +++ b/docs/htmldocs/portability.html @@ -5,8 +5,7 @@ >Portability</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ -"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -73,7 +72,9 @@ WIDTH="100%"></DIV CLASS="CHAPTER" ><H1 ><A -NAME="PORTABILITY">Chapter 23. Portability</H1 +NAME="PORTABILITY" +></A +>Chapter 21. Portability</H1 ><P >Samba works on a wide range of platforms but the interface all the platforms provide is not always compatible. This chapter contains @@ -83,7 +84,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3139">23.1. HPUX</H1 +NAME="AEN3251" +></A +>21.1. HPUX</H1 ><P >HP's implementation of supplementary groups is, er, non-standard (for hysterical reasons). There are two group files, /etc/group and @@ -111,7 +114,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3145">23.2. SCO Unix</H1 +NAME="AEN3257" +></A +>21.2. SCO Unix</H1 ><P > If you run an old version of SCO Unix then you may need to get important @@ -126,7 +131,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3149">23.3. DNIX</H1 +NAME="AEN3261" +></A +>21.3. DNIX</H1 ><P >DNIX has a problem with seteuid() and setegid(). These routines are needed for Samba to work correctly, but they were left out of the DNIX @@ -231,7 +238,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3178">23.4. RedHat Linux Rembrandt-II</H1 +NAME="AEN3290" +></A +>21.4. RedHat Linux Rembrandt-II</H1 ><P >By default RedHat Rembrandt-II during installation adds an entry to /etc/hosts as follows: diff --git a/docs/htmldocs/printing.html b/docs/htmldocs/printing.html index 46ebbcdf84..92eb52c7cc 100644 --- a/docs/htmldocs/printing.html +++ b/docs/htmldocs/printing.html @@ -5,8 +5,7 @@ >Printing Support</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ -"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -73,13 +72,17 @@ WIDTH="100%"></DIV CLASS="CHAPTER" ><H1 ><A -NAME="PRINTING">Chapter 14. Printing Support</H1 +NAME="PRINTING" +></A +>Chapter 13. Printing Support</H1 ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1920">14.1. Introduction</H1 +NAME="AEN2054" +></A +>13.1. Introduction</H1 ><P >Beginning with the 2.2.0 release, Samba supports the native Windows NT printing mechanisms implemented via @@ -160,7 +163,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1942">14.2. Configuration</H1 +NAME="AEN2076" +></A +>13.2. Configuration</H1 ><DIV CLASS="WARNING" ><P @@ -175,7 +180,7 @@ WIDTH="25" ALIGN="CENTER" VALIGN="TOP" ><IMG -SRC="../images/warning.gif" +SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/warning.gif" HSPACE="5" ALT="Warning"></TD ><TH @@ -224,7 +229,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1950">14.2.1. Creating [print$]</H2 +NAME="AEN2084" +></A +>13.2.1. Creating [print$]</H2 ><P >In order to support the uploading of printer driver files, you must first configure a file share named [print$]. @@ -303,7 +310,7 @@ WIDTH="25" ALIGN="CENTER" VALIGN="TOP" ><IMG -SRC="../images/note.gif" +SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif" HSPACE="5" ALT="Note"></TD ><TH @@ -374,7 +381,7 @@ WIDTH="25" ALIGN="CENTER" VALIGN="TOP" ><IMG -SRC="../images/warning.gif" +SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/warning.gif" HSPACE="5" ALT="Warning"></TD ><TH @@ -445,7 +452,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1985">14.2.2. Setting Drivers for Existing Printers</H2 +NAME="AEN2119" +></A +>13.2.2. Setting Drivers for Existing Printers</H2 ><P >The initial listing of printers in the Samba host's Printers folder will have no real printer driver assigned @@ -515,7 +524,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2001">14.2.3. Support a large number of printers</H2 +NAME="AEN2135" +></A +>13.2.3. Support a large number of printers</H2 ><P >One issue that has arisen during the development phase of Samba 2.2 is the need to support driver downloads for @@ -579,7 +590,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2012">14.2.4. Adding New Printers via the Windows NT APW</H2 +NAME="AEN2146" +></A +>13.2.4. Adding New Printers via the Windows NT APW</H2 ><P >By default, Samba offers all printer shares defined in <TT CLASS="FILENAME" @@ -720,8 +733,8 @@ echo " :sd=/var/spool/lpd/$2:\\" >> $PRINTCAP echo " :mx=0:ml=0:sh:\\" >> $PRINTCAP echo " :lp=/usr/local/samba/var/print/$5.prn:" >> $PRINTCAP -touch "/usr/local/samba/var/print/$5.prn" >> /tmp/printadd.$$ 2>&1 -chown $LP "/usr/local/samba/var/print/$5.prn" >> /tmp/printadd.$$ 2>&1 +touch "/usr/local/samba/var/print/$5.prn" >> /tmp/printadd.$$ 2>&1 +chown $LP "/usr/local/samba/var/print/$5.prn" >> /tmp/printadd.$$ 2>&1 mkdir /var/spool/lpd/$2 chmod 700 /var/spool/lpd/$2 @@ -746,7 +759,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2042">14.2.5. Samba and Printer Ports</H2 +NAME="AEN2176" +></A +>13.2.5. Samba and Printer Ports</H2 ><P >Windows NT/2000 print servers associate a port with each printer. These normally take the form of LPT1:, COM1:, FILE:, etc... Samba must also support the @@ -781,7 +796,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2050">14.3. The Imprints Toolset</H1 +NAME="AEN2184" +></A +>13.3. The Imprints Toolset</H1 ><P >The Imprints tool set provides a UNIX equivalent of the Windows NT Add Printer Wizard. For complete information, please @@ -797,7 +814,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2054">14.3.1. What is Imprints?</H2 +NAME="AEN2188" +></A +>13.3.1. What is Imprints?</H2 ><P >Imprints is a collection of tools for supporting the goals of</P @@ -827,7 +846,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2064">14.3.2. Creating Printer Driver Packages</H2 +NAME="AEN2198" +></A +>13.3.2. Creating Printer Driver Packages</H2 ><P >The process of creating printer driver packages is beyond the scope of this document (refer to Imprints.txt also included @@ -841,7 +862,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2067">14.3.3. The Imprints server</H2 +NAME="AEN2201" +></A +>13.3.3. The Imprints server</H2 ><P >The Imprints server is really a database server that may be queried via standard HTTP mechanisms. Each printer @@ -863,7 +886,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2071">14.3.4. The Installation Client</H2 +NAME="AEN2205" +></A +>13.3.4. The Installation Client</H2 ><P >More information regarding the Imprints installation client is available in the <TT @@ -955,13 +980,17 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2093">14.4. Diagnosis</H1 +NAME="AEN2227" +></A +>13.4. Diagnosis</H1 ><DIV CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2095">14.4.1. Introduction</H2 +NAME="AEN2229" +></A +>13.4.1. Introduction</H2 ><P >This is a short description of how to debug printing problems with Samba. This describes how to debug problems with printing from a SMB @@ -1034,7 +1063,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2111">14.4.2. Debugging printer problems</H2 +NAME="AEN2245" +></A +>13.4.2. Debugging printer problems</H2 ><P >One way to debug printing problems is to start by replacing these command with shell scripts that record the arguments and the contents @@ -1050,7 +1081,7 @@ CLASS="PROGRAMLISTING" /usr/bin/id -p >/tmp/tmp.print # we run the command and save the error messages # replace the command with the one appropriate for your system - /usr/bin/lpr -r -P$1 $2 2>>&/tmp/tmp.print</PRE + /usr/bin/lpr -r -P$1 $2 2>>&/tmp/tmp.print</PRE ></P ><P >Then you print a file and try removing it. You may find that the @@ -1089,7 +1120,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2120">14.4.3. What printers do I have?</H2 +NAME="AEN2254" +></A +>13.4.3. What printers do I have?</H2 ><P >You can use the 'testprns' program to check to see if the printer name you are using is recognized by Samba. For example, you can @@ -1116,7 +1149,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2128">14.4.4. Setting up printcap and print servers</H2 +NAME="AEN2262" +></A +>13.4.4. Setting up printcap and print servers</H2 ><P >You may need to set up some printcaps for your Samba system to use. It is strongly recommended that you use the facilities provided by @@ -1198,7 +1233,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2156">14.4.5. Job sent, no output</H2 +NAME="AEN2290" +></A +>13.4.5. Job sent, no output</H2 ><P >This is the most frustrating part of printing. You may have sent the job, verified that the job was forwarded, set up a wrapper around @@ -1241,7 +1278,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2167">14.4.6. Job sent, strange output</H2 +NAME="AEN2301" +></A +>13.4.6. Job sent, strange output</H2 ><P >Once you have the job printing, you can then start worrying about making it print nicely.</P @@ -1285,7 +1324,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2179">14.4.7. Raw PostScript printed</H2 +NAME="AEN2313" +></A +>13.4.7. Raw PostScript printed</H2 ><P >This is a problem that is usually caused by either the print spooling system putting information at the start of the print job that makes @@ -1298,7 +1339,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2182">14.4.8. Advanced Printing</H2 +NAME="AEN2316" +></A +>13.4.8. Advanced Printing</H2 ><P >Note that you can do some pretty magic things by using your imagination with the "print command" option and some shell scripts. @@ -1312,7 +1355,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2185">14.4.9. Real debugging</H2 +NAME="AEN2319" +></A +>13.4.9. Real debugging</H2 ><P >If the above debug tips don't help, then maybe you need to bring in the bug guns, system tracing. See Tracing.txt in this directory.</P diff --git a/docs/htmldocs/pwencrypt.html b/docs/htmldocs/pwencrypt.html index 9414399bf4..b15d74c5d0 100644 --- a/docs/htmldocs/pwencrypt.html +++ b/docs/htmldocs/pwencrypt.html @@ -5,8 +5,7 @@ >LanMan and NT Password Encryption in Samba</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ -"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -17,8 +16,8 @@ REL="PREVIOUS" TITLE="Quick Cross Subnet Browsing / Cross Workgroup Browsing guide" HREF="browsing-quick.html"><LINK REL="NEXT" -TITLE="Type of installation" -HREF="type.html"></HEAD +TITLE="User information database" +HREF="passdb.html"></HEAD ><BODY CLASS="CHAPTER" BGCOLOR="#FFFFFF" @@ -60,7 +59,7 @@ WIDTH="10%" ALIGN="right" VALIGN="bottom" ><A -HREF="type.html" +HREF="passdb.html" ACCESSKEY="N" >Next</A ></TD @@ -73,13 +72,17 @@ WIDTH="100%"></DIV CLASS="CHAPTER" ><H1 ><A -NAME="PWENCRYPT">Chapter 4. LanMan and NT Password Encryption in Samba</H1 +NAME="PWENCRYPT" +></A +>Chapter 4. LanMan and NT Password Encryption in Samba</H1 ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN457">4.1. Introduction</H1 +NAME="AEN457" +></A +>4.1. Introduction</H1 ><P >Newer windows clients send encrypted passwords over the wire, instead of plain text passwords. The newest clients @@ -101,7 +104,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN462">4.2. Important Notes About Security</H1 +NAME="AEN462" +></A +>4.2. Important Notes About Security</H1 ><P >The unix and SMB password encryption techniques seem similar on the surface. This similarity is, however, only skin deep. The unix @@ -135,7 +140,7 @@ WIDTH="25" ALIGN="CENTER" VALIGN="TOP" ><IMG -SRC="../images/warning.gif" +SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/warning.gif" HSPACE="5" ALT="Warning"></TD ><TD @@ -201,7 +206,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN481">4.2.1. Advantages of SMB Encryption</H2 +NAME="AEN481" +></A +>4.2.1. Advantages of SMB Encryption</H2 ><P ></P ><UL @@ -228,7 +235,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN488">4.2.2. Advantages of non-encrypted passwords</H2 +NAME="AEN488" +></A +>4.2.2. Advantages of non-encrypted passwords</H2 ><P ></P ><UL @@ -257,7 +266,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN497">4.3. The smbpasswd Command</H1 +NAME="AEN497" +></A +>4.3. The smbpasswd Command</H1 ><P >The smbpasswd command maintains the two 32 byte password fields in the smbpasswd file. If you wish to make it similar to the unix @@ -401,7 +412,7 @@ WIDTH="33%" ALIGN="right" VALIGN="top" ><A -HREF="type.html" +HREF="passdb.html" ACCESSKEY="N" >Next</A ></TD @@ -425,7 +436,7 @@ ACCESSKEY="U" WIDTH="33%" ALIGN="right" VALIGN="top" ->Type of installation</TD +>User information database</TD ></TR ></TABLE ></DIV diff --git a/docs/htmldocs/rpcclient.1.html b/docs/htmldocs/rpcclient.1.html index e695663c8a..611512a53b 100644 --- a/docs/htmldocs/rpcclient.1.html +++ b/docs/htmldocs/rpcclient.1.html @@ -5,7 +5,7 @@ >rpcclient</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77"></HEAD +CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"></HEAD ><BODY CLASS="REFENTRY" BGCOLOR="#FFFFFF" @@ -15,7 +15,7 @@ VLINK="#840084" ALINK="#0000FF" ><H1 ><A -NAME="RPCCLIENT" +NAME="RPCCLIENT.1" ></A >rpcclient</H1 ><DIV @@ -48,10 +48,12 @@ NAME="AEN23" ><H2 >DESCRIPTION</H2 ><P ->This tool is part of the <A -HREF="samba.7.html" -TARGET="_top" -> Samba</A +>This tool is part of the <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>Samba</SPAN +>(7)</SPAN > suite.</P ><P ><B @@ -66,7 +68,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN29" +NAME="AEN31" ></A ><H2 >OPTIONS</H2 @@ -90,10 +92,12 @@ CLASS="PARAMETER" >name resolve order</I ></TT ></A -> line from - <TT -CLASS="FILENAME" ->smb.conf(5)</TT +> line from <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smb.conf</SPAN +>(5)</SPAN >.</P ></DD ><DT @@ -107,10 +111,9 @@ CLASS="FILENAME" ><P ><PRE CLASS="PROGRAMLISTING" -> username = <value> - password = <value> - domain = <value> - </PRE +>username = <value> +password = <value> +domain = <value></PRE ></P ><P >Make certain that the permissions on the file restrict @@ -124,6 +127,12 @@ CLASS="PROGRAMLISTING" below)) </P ></DD ><DT +>-h|--help</DT +><DD +><P +>Print a summary of command line options.</P +></DD +><DT >-d|--debug=debuglevel</DT ><DD ><P @@ -165,12 +174,6 @@ CLASS="FILENAME" > file.</P ></DD ><DT ->-h|--help</DT -><DD -><P ->Print a summary of command line options.</P -></DD -><DT >-I IP-address</DT ><DD ><P @@ -303,7 +306,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN107" +NAME="AEN111" ></A ><H2 >COMMANDS</H2 @@ -467,15 +470,14 @@ CLASS="PARAMETER" ><P ><PRE CLASS="PROGRAMLISTING" -> Long Printer Name:\ - Driver File Name:\ - Data File Name:\ - Config File Name:\ - Help File Name:\ - Language Monitor Name:\ - Default Data Type:\ - Comma Separated list of Files - </PRE +>Long Printer Name:\ +Driver File Name:\ +Data File Name:\ +Config File Name:\ +Help File Name:\ +Language Monitor Name:\ +Default Data Type:\ +Comma Separated list of Files</PRE ></P ><P >Any empty fields should be enter as the string "NULL". </P @@ -705,7 +707,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN227" +NAME="AEN231" ></A ><H2 >BUGS</H2 @@ -724,7 +726,7 @@ CLASS="COMMAND" CLASS="emphasis" ><I CLASS="EMPHASIS" ->"WARNING!</I +>WARNING!</I ></SPAN > The MSRPC over SMB code has been developed from examining Network traces. No documentation is @@ -734,23 +736,28 @@ CLASS="EMPHASIS" to be... a bit flaky in places. </P ><P >The development of Samba's implementation is also a bit rough, - and as more of the services are understood, it can even result in - versions of <B -CLASS="COMMAND" ->smbd(8)</B -> and <B -CLASS="COMMAND" ->rpcclient(1)</B -> - that are incompatible for some commands or services. Additionally, + and as more of the services are understood, it can even result in + versions of <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbd</SPAN +>(8)</SPAN +> and <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>rpcclient</SPAN +>(1)</SPAN +> that are incompatible for some commands or services. Additionally, the developers are sending reports to Microsoft, and problems found or reported to Microsoft are fixed in Service Packs, which may - result in incompatibilities." </P + result in incompatibilities.</P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN237" +NAME="AEN245" ></A ><H2 >VERSION</H2 @@ -761,7 +768,7 @@ NAME="AEN237" ><DIV CLASS="REFSECT1" ><A -NAME="AEN240" +NAME="AEN248" ></A ><H2 >AUTHOR</H2 @@ -774,7 +781,8 @@ NAME="AEN240" >The original rpcclient man page was written by Matthew Geddes, Luke Kenneth Casson Leighton, and rewritten by Gerald Carter. The conversion to DocBook for Samba 2.2 was done by Gerald - Carter.</P + Carter. The conversion to DocBook XML 4.2 for Samba 3.0 was + done by Alexander Bokovoy.</P ></DIV ></BODY ></HTML diff --git a/docs/htmldocs/samba-bdc.html b/docs/htmldocs/samba-bdc.html index ef06a89416..42f653fb7d 100644 --- a/docs/htmldocs/samba-bdc.html +++ b/docs/htmldocs/samba-bdc.html @@ -5,8 +5,7 @@ >How to Act as a Backup Domain Controller in a Purely Samba Controlled Domain</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ -"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -14,7 +13,7 @@ REL="UP" TITLE="Type of installation" HREF="type.html"><LINK REL="PREVIOUS" -TITLE="How to Configure Samba as a NT4 Primary Domain Controller" +TITLE="Samba as a NT4 or Win2k Primary Domain Controller" HREF="samba-pdc.html"><LINK REL="NEXT" TITLE="Samba as a ADS domain member" @@ -73,13 +72,17 @@ WIDTH="100%"></DIV CLASS="CHAPTER" ><H1 ><A -NAME="SAMBA-BDC">Chapter 7. How to Act as a Backup Domain Controller in a Purely Samba Controlled Domain</H1 +NAME="SAMBA-BDC" +></A +>Chapter 6. How to Act as a Backup Domain Controller in a Purely Samba Controlled Domain</H1 ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1127">7.1. Prerequisite Reading</H1 +NAME="AEN1274" +></A +>6.1. Prerequisite Reading</H1 ><P >Before you continue reading in this chapter, please make sure that you are comfortable with configuring a Samba PDC @@ -94,7 +97,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1131">7.2. Background</H1 +NAME="AEN1278" +></A +>6.2. Background</H1 ><P >What is a Domain Controller? It is a machine that is able to answer logon requests from workstations in a Windows NT Domain. Whenever a @@ -137,7 +142,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1139">7.3. What qualifies a Domain Controller on the network?</H1 +NAME="AEN1286" +></A +>6.3. What qualifies a Domain Controller on the network?</H1 ><P >Every machine that is a Domain Controller for the domain SAMBA has to register the NetBIOS group name SAMBA#1c with the WINS server and/or @@ -152,7 +159,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1142">7.3.1. How does a Workstation find its domain controller?</H2 +NAME="AEN1289" +></A +>6.3.1. How does a Workstation find its domain controller?</H2 ><P >A NT workstation in the domain SAMBA that wants a local user to be authenticated has to find the domain controller for SAMBA. It does @@ -169,7 +178,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1145">7.3.2. When is the PDC needed?</H2 +NAME="AEN1292" +></A +>6.3.2. When is the PDC needed?</H2 ><P >Whenever a user wants to change his password, this has to be done on the PDC. To find the PDC, the workstation does a NetBIOS name query @@ -183,13 +194,19 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1148">7.4. Can Samba be a Backup Domain Controller?</H1 +NAME="AEN1295" +></A +>6.4. Can Samba be a Backup Domain Controller to an NT PDC?</H1 ><P >With version 2.2, no. The native NT SAM replication protocols have not yet been fully implemented. The Samba Team is working on understanding and implementing the protocols, but this work has not been finished for version 2.2.</P ><P +>With version 3.0, the work on both the replication protocols and a +suitable storage mechanism has progressed, and some form of NT4 BDC +support is expected soon.</P +><P >Can I get the benefits of a BDC with Samba? Yes. The main reason for implementing a BDC is availability. If the PDC is a Samba machine, a second Samba machine can be set up to @@ -200,7 +217,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1152">7.5. How do I set up a Samba BDC?</H1 +NAME="AEN1300" +></A +>6.5. How do I set up a Samba BDC?</H1 ><P >Several things have to be done:</P ><P @@ -265,7 +284,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1169">7.5.1. How do I replicate the smbpasswd file?</H2 +NAME="AEN1317" +></A +>6.5.1. How do I replicate the smbpasswd file?</H2 ><P >Replication of the smbpasswd file is sensitive. It has to be done whenever changes to the SAM are made. Every user's password change is @@ -279,6 +300,21 @@ rsync. rsync can use ssh as a transport. ssh itself can be set up to accept *only* rsync transfer without requiring the user to type a password.</P ></DIV +><DIV +CLASS="SECT2" +><H2 +CLASS="SECT2" +><A +NAME="AEN1321" +></A +>6.5.2. Can I do this all with LDAP?</H2 +><P +>The simple answer is YES. Samba's pdb_ldap code supports +binding to a replica LDAP server, and will also follow referrals and +rebind to the master if it ever needs to make a modification to the +database. (Normally BDCs are read only, so this will not occur +often).</P +></DIV ></DIV ></DIV ><DIV @@ -325,7 +361,7 @@ ACCESSKEY="N" WIDTH="33%" ALIGN="left" VALIGN="top" ->How to Configure Samba as a NT4 Primary Domain Controller</TD +>Samba as a NT4 or Win2k Primary Domain Controller</TD ><TD WIDTH="34%" ALIGN="center" diff --git a/docs/htmldocs/samba-howto-collection.html b/docs/htmldocs/samba-howto-collection.html index 0062e257dc..82e29206ac 100644 --- a/docs/htmldocs/samba-howto-collection.html +++ b/docs/htmldocs/samba-howto-collection.html @@ -5,8 +5,7 @@ >SAMBA Project Documentation</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ -"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK REL="NEXT" TITLE="General installation" HREF="introduction.html"></HEAD @@ -20,20 +19,28 @@ ALINK="#0000FF" ><DIV CLASS="BOOK" ><A -NAME="SAMBA-HOWTO-COLLECTION"><DIV +NAME="SAMBA-HOWTO-COLLECTION" +></A +><DIV CLASS="TITLEPAGE" ><H1 CLASS="TITLE" ><A -NAME="SAMBA-HOWTO-COLLECTION">SAMBA Project Documentation</H1 +NAME="SAMBA-HOWTO-COLLECTION" +></A +>SAMBA Project Documentation</H1 ><H3 CLASS="AUTHOR" ><A -NAME="AEN4">SAMBA Team</H3 +NAME="AEN4" +></A +>SAMBA Team</H3 ><HR></DIV ><H1 ><A -NAME="AEN8">Abstract</H1 +NAME="AEN8" +></A +>Abstract</H1 ><P ><SPAN CLASS="emphasis" @@ -152,128 +159,89 @@ HREF="install.html#AEN184" ></DD ><DT >2. <A -HREF="improved-browsing.html" ->Improved browsing in samba</A +HREF="browsing-quick.html" +>Quick Cross Subnet Browsing / Cross Workgroup Browsing guide</A ></DT ><DD ><DL ><DT >2.1. <A -HREF="improved-browsing.html#AEN229" ->Overview of browsing</A +HREF="browsing-quick.html#AEN230" +>Discussion</A ></DT ><DT >2.2. <A -HREF="improved-browsing.html#AEN233" ->Browsing support in samba</A +HREF="browsing-quick.html#AEN238" +>Use of the "Remote Announce" parameter</A ></DT ><DT >2.3. <A -HREF="improved-browsing.html#AEN242" ->Problem resolution</A +HREF="browsing-quick.html#AEN252" +>Use of the "Remote Browse Sync" parameter</A ></DT ><DT >2.4. <A -HREF="improved-browsing.html#AEN249" ->Browsing across subnets</A +HREF="browsing-quick.html#AEN257" +>Use of WINS</A ></DT ><DT >2.5. <A -HREF="improved-browsing.html#AEN289" ->Setting up a WINS server</A +HREF="browsing-quick.html#AEN268" +>Do NOT use more than one (1) protocol on MS Windows machines</A ></DT ><DT >2.6. <A -HREF="improved-browsing.html#AEN308" ->Setting up Browsing in a WORKGROUP</A -></DT -><DT ->2.7. <A -HREF="improved-browsing.html#AEN326" ->Setting up Browsing in a DOMAIN</A -></DT -><DT ->2.8. <A -HREF="improved-browsing.html#AEN336" ->Forcing samba to be the master</A -></DT -><DT ->2.9. <A -HREF="improved-browsing.html#AEN345" ->Making samba the domain master</A -></DT -><DT ->2.10. <A -HREF="improved-browsing.html#AEN363" ->Note about broadcast addresses</A -></DT -><DT ->2.11. <A -HREF="improved-browsing.html#AEN366" ->Multiple interfaces</A +HREF="browsing-quick.html#AEN274" +>Name Resolution Order</A ></DT ></DL ></DD ><DT >3. <A -HREF="browsing-quick.html" ->Quick Cross Subnet Browsing / Cross Workgroup Browsing guide</A +HREF="passdb.html" +>User information database</A ></DT ><DD ><DL ><DT >3.1. <A -HREF="browsing-quick.html#AEN377" ->Discussion</A +HREF="passdb.html#AEN324" +>Introduction</A ></DT ><DT >3.2. <A -HREF="browsing-quick.html#AEN385" ->Use of the "Remote Announce" parameter</A +HREF="passdb.html#AEN331" +>Important Notes About Security</A ></DT ><DT >3.3. <A -HREF="browsing-quick.html#AEN399" ->Use of the "Remote Browse Sync" parameter</A +HREF="passdb.html#AEN357" +>The smbpasswd Command</A ></DT ><DT >3.4. <A -HREF="browsing-quick.html#AEN404" ->Use of WINS</A +HREF="passdb.html#AEN388" +>Plain text</A ></DT ><DT >3.5. <A -HREF="browsing-quick.html#AEN415" ->Do NOT use more than one (1) protocol on MS Windows machines</A +HREF="passdb.html#AEN393" +>TDB</A ></DT ><DT >3.6. <A -HREF="browsing-quick.html#AEN421" ->Name Resolution Order</A +HREF="passdb.html#AEN396" +>LDAP</A ></DT -></DL -></DD ><DT ->4. <A -HREF="pwencrypt.html" ->LanMan and NT Password Encryption in Samba</A +>3.7. <A +HREF="passdb.html#AEN614" +>MySQL</A ></DT -><DD -><DL ><DT ->4.1. <A -HREF="pwencrypt.html#AEN457" ->Introduction</A -></DT -><DT ->4.2. <A -HREF="pwencrypt.html#AEN462" ->Important Notes About Security</A -></DT -><DT ->4.3. <A -HREF="pwencrypt.html#AEN497" ->The smbpasswd Command</A +>3.8. <A +HREF="passdb.html#AEN662" +>Passdb XML plugin</A ></DT ></DL ></DD @@ -287,168 +255,168 @@ HREF="type.html" ><DD ><DL ><DT ->5. <A +>4. <A HREF="securitylevels.html" >User and Share security level (for servers not in a domain)</A ></DT ><DT ->6. <A +>5. <A HREF="samba-pdc.html" ->How to Configure Samba as a NT4 Primary Domain Controller</A +>Samba as a NT4 or Win2k Primary Domain Controller</A ></DT ><DD ><DL ><DT ->6.1. <A -HREF="samba-pdc.html#AEN575" +>5.1. <A +HREF="samba-pdc.html#AEN722" >Prerequisite Reading</A ></DT ><DT ->6.2. <A -HREF="samba-pdc.html#AEN581" +>5.2. <A +HREF="samba-pdc.html#AEN728" >Background</A ></DT ><DT ->6.3. <A -HREF="samba-pdc.html#AEN620" +>5.3. <A +HREF="samba-pdc.html#AEN767" >Configuring the Samba Domain Controller</A ></DT ><DT ->6.4. <A -HREF="samba-pdc.html#AEN663" +>5.4. <A +HREF="samba-pdc.html#AEN810" >Creating Machine Trust Accounts and Joining Clients to the Domain</A ></DT ><DT ->6.5. <A -HREF="samba-pdc.html#AEN747" +>5.5. <A +HREF="samba-pdc.html#AEN894" >Common Problems and Errors</A ></DT ><DT ->6.6. <A -HREF="samba-pdc.html#AEN795" +>5.6. <A +HREF="samba-pdc.html#AEN942" >System Policies and Profiles</A ></DT ><DT ->6.7. <A -HREF="samba-pdc.html#AEN839" +>5.7. <A +HREF="samba-pdc.html#AEN986" >What other help can I get?</A ></DT ><DT ->6.8. <A -HREF="samba-pdc.html#AEN953" +>5.8. <A +HREF="samba-pdc.html#AEN1100" >Domain Control for Windows 9x/ME</A ></DT ><DT ->6.9. <A -HREF="samba-pdc.html#AEN1091" ->DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba</A +>5.9. <A +HREF="samba-pdc.html#AEN1238" +>DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba</A ></DT ></DL ></DD ><DT ->7. <A +>6. <A HREF="samba-bdc.html" >How to Act as a Backup Domain Controller in a Purely Samba Controlled Domain</A ></DT ><DD ><DL ><DT ->7.1. <A -HREF="samba-bdc.html#AEN1127" +>6.1. <A +HREF="samba-bdc.html#AEN1274" >Prerequisite Reading</A ></DT ><DT ->7.2. <A -HREF="samba-bdc.html#AEN1131" +>6.2. <A +HREF="samba-bdc.html#AEN1278" >Background</A ></DT ><DT ->7.3. <A -HREF="samba-bdc.html#AEN1139" +>6.3. <A +HREF="samba-bdc.html#AEN1286" >What qualifies a Domain Controller on the network?</A ></DT ><DT ->7.4. <A -HREF="samba-bdc.html#AEN1148" ->Can Samba be a Backup Domain Controller?</A +>6.4. <A +HREF="samba-bdc.html#AEN1295" +>Can Samba be a Backup Domain Controller to an NT PDC?</A ></DT ><DT ->7.5. <A -HREF="samba-bdc.html#AEN1152" +>6.5. <A +HREF="samba-bdc.html#AEN1300" >How do I set up a Samba BDC?</A ></DT ></DL ></DD ><DT ->8. <A +>7. <A HREF="ads.html" >Samba as a ADS domain member</A ></DT ><DD ><DL ><DT ->8.1. <A -HREF="ads.html#AEN1187" +>7.1. <A +HREF="ads.html#AEN1339" >Installing the required packages for Debian</A ></DT ><DT ->8.2. <A -HREF="ads.html#AEN1193" +>7.2. <A +HREF="ads.html#AEN1346" >Installing the required packages for RedHat</A ></DT ><DT ->8.3. <A -HREF="ads.html#AEN1202" +>7.3. <A +HREF="ads.html#AEN1356" >Compile Samba</A ></DT ><DT ->8.4. <A -HREF="ads.html#AEN1217" +>7.4. <A +HREF="ads.html#AEN1371" >Setup your /etc/krb5.conf</A ></DT ><DT ->8.5. <A -HREF="ads.html#AEN1227" +>7.5. <A +HREF="ads.html#AEN1381" >Create the computer account</A ></DT ><DT ->8.6. <A -HREF="ads.html#AEN1243" +>7.6. <A +HREF="ads.html#AEN1393" >Test your server setup</A ></DT ><DT ->8.7. <A -HREF="ads.html#AEN1248" +>7.7. <A +HREF="ads.html#AEN1398" >Testing with smbclient</A ></DT ><DT ->8.8. <A -HREF="ads.html#AEN1251" +>7.8. <A +HREF="ads.html#AEN1401" >Notes</A ></DT ></DL ></DD ><DT ->9. <A +>8. <A HREF="domain-security.html" ->Samba as a NT4 domain member</A +>Samba as a NT4 or Win2k domain member</A ></DT ><DD ><DL ><DT ->9.1. <A -HREF="domain-security.html#AEN1273" ->Joining an NT Domain with Samba 2.2</A +>8.1. <A +HREF="domain-security.html#AEN1423" +>Joining an NT Domain with Samba 3.0</A ></DT ><DT ->9.2. <A -HREF="domain-security.html#AEN1337" +>8.2. <A +HREF="domain-security.html#AEN1478" >Samba and Windows 2000 Domains</A ></DT ><DT ->9.3. <A -HREF="domain-security.html#AEN1342" +>8.3. <A +HREF="domain-security.html#AEN1481" >Why is this better than security = server?</A ></DT ></DL @@ -463,95 +431,95 @@ HREF="optional.html" ><DD ><DL ><DT ->10. <A +>9. <A HREF="integrate-ms-networks.html" >Integrating MS Windows networks with Samba</A ></DT ><DD ><DL ><DT ->10.1. <A -HREF="integrate-ms-networks.html#AEN1374" +>9.1. <A +HREF="integrate-ms-networks.html#AEN1513" >Agenda</A ></DT ><DT ->10.2. <A -HREF="integrate-ms-networks.html#AEN1396" +>9.2. <A +HREF="integrate-ms-networks.html#AEN1535" >Name Resolution in a pure Unix/Linux world</A ></DT ><DT ->10.3. <A -HREF="integrate-ms-networks.html#AEN1459" +>9.3. <A +HREF="integrate-ms-networks.html#AEN1598" >Name resolution as used within MS Windows networking</A ></DT ><DT ->10.4. <A -HREF="integrate-ms-networks.html#AEN1504" +>9.4. <A +HREF="integrate-ms-networks.html#AEN1643" >How browsing functions and how to deploy stable and dependable browsing using Samba</A ></DT ><DT ->10.5. <A -HREF="integrate-ms-networks.html#AEN1514" +>9.5. <A +HREF="integrate-ms-networks.html#AEN1653" >MS Windows security options and how to configure Samba for seemless integration</A ></DT ><DT ->10.6. <A -HREF="integrate-ms-networks.html#AEN1584" +>9.6. <A +HREF="integrate-ms-networks.html#AEN1723" >Conclusions</A ></DT ></DL ></DD ><DT ->11. <A +>10. <A HREF="unix-permissions.html" >UNIX Permission Bits and Windows NT Access Control Lists</A ></DT ><DD ><DL ><DT ->11.1. <A -HREF="unix-permissions.html#AEN1605" +>10.1. <A +HREF="unix-permissions.html#AEN1744" >Viewing and changing UNIX permissions using the NT security dialogs</A ></DT ><DT ->11.2. <A -HREF="unix-permissions.html#AEN1614" +>10.2. <A +HREF="unix-permissions.html#AEN1748" >How to view file security on a Samba share</A ></DT ><DT ->11.3. <A -HREF="unix-permissions.html#AEN1625" +>10.3. <A +HREF="unix-permissions.html#AEN1759" >Viewing file ownership</A ></DT ><DT ->11.4. <A -HREF="unix-permissions.html#AEN1645" +>10.4. <A +HREF="unix-permissions.html#AEN1779" >Viewing file or directory permissions</A ></DT ><DT ->11.5. <A -HREF="unix-permissions.html#AEN1681" +>10.5. <A +HREF="unix-permissions.html#AEN1815" >Modifying file or directory permissions</A ></DT ><DT ->11.6. <A -HREF="unix-permissions.html#AEN1703" +>10.6. <A +HREF="unix-permissions.html#AEN1837" >Interaction with the standard Samba create mask parameters</A ></DT ><DT ->11.7. <A -HREF="unix-permissions.html#AEN1767" +>10.7. <A +HREF="unix-permissions.html#AEN1901" >Interaction with the standard Samba file attribute mapping</A ></DT ></DL ></DD ><DT ->12. <A +>11. <A HREF="pam.html" >Configuring PAM for distributed but centrally managed authentication</A @@ -559,323 +527,304 @@ managed authentication</A ><DD ><DL ><DT ->12.1. <A -HREF="pam.html#AEN1788" +>11.1. <A +HREF="pam.html#AEN1922" >Samba and PAM</A ></DT ><DT ->12.2. <A -HREF="pam.html#AEN1832" +>11.2. <A +HREF="pam.html#AEN1966" >Distributed Authentication</A ></DT ><DT ->12.3. <A -HREF="pam.html#AEN1839" +>11.3. <A +HREF="pam.html#AEN1973" >PAM Configuration in smb.conf</A ></DT ></DL ></DD ><DT ->13. <A +>12. <A HREF="msdfs.html" >Hosting a Microsoft Distributed File System tree on Samba</A ></DT ><DD ><DL ><DT ->13.1. <A -HREF="msdfs.html#AEN1859" +>12.1. <A +HREF="msdfs.html#AEN1993" >Instructions</A ></DT ></DL ></DD ><DT ->14. <A +>13. <A HREF="printing.html" >Printing Support</A ></DT ><DD ><DL ><DT ->14.1. <A -HREF="printing.html#AEN1920" +>13.1. <A +HREF="printing.html#AEN2054" >Introduction</A ></DT ><DT ->14.2. <A -HREF="printing.html#AEN1942" +>13.2. <A +HREF="printing.html#AEN2076" >Configuration</A ></DT ><DT ->14.3. <A -HREF="printing.html#AEN2050" +>13.3. <A +HREF="printing.html#AEN2184" >The Imprints Toolset</A ></DT ><DT ->14.4. <A -HREF="printing.html#AEN2093" +>13.4. <A +HREF="printing.html#AEN2227" >Diagnosis</A ></DT ></DL ></DD ><DT ->15. <A +>14. <A HREF="winbind.html" >Unified Logons between Windows NT and UNIX using Winbind</A ></DT ><DD ><DL ><DT ->15.1. <A -HREF="winbind.html#AEN2225" +>14.1. <A +HREF="winbind.html#AEN2360" >Abstract</A ></DT ><DT ->15.2. <A -HREF="winbind.html#AEN2229" +>14.2. <A +HREF="winbind.html#AEN2364" >Introduction</A ></DT ><DT ->15.3. <A -HREF="winbind.html#AEN2242" +>14.3. <A +HREF="winbind.html#AEN2377" >What Winbind Provides</A ></DT ><DT ->15.4. <A -HREF="winbind.html#AEN2253" +>14.4. <A +HREF="winbind.html#AEN2388" >How Winbind Works</A ></DT ><DT ->15.5. <A -HREF="winbind.html#AEN2293" +>14.5. <A +HREF="winbind.html#AEN2431" >Installation and Configuration</A ></DT ><DT ->15.6. <A -HREF="winbind.html#AEN2542" +>14.6. <A +HREF="winbind.html#AEN2680" >Limitations</A ></DT ><DT ->15.7. <A -HREF="winbind.html#AEN2552" +>14.7. <A +HREF="winbind.html#AEN2690" >Conclusion</A ></DT ></DL ></DD ><DT ->16. <A -HREF="pdb-mysql.html" ->Passdb MySQL plugin</A +>15. <A +HREF="improved-browsing.html" +>Improved browsing in samba</A ></DT ><DD ><DL ><DT ->16.1. <A -HREF="pdb-mysql.html#AEN2566" ->Building</A +>15.1. <A +HREF="improved-browsing.html#AEN2700" +>Overview of browsing</A ></DT ><DT ->16.2. <A -HREF="pdb-mysql.html#AEN2572" ->Configuring</A +>15.2. <A +HREF="improved-browsing.html#AEN2704" +>Browsing support in samba</A ></DT ><DT ->16.3. <A -HREF="pdb-mysql.html#AEN2589" ->Using plaintext passwords or encrypted password</A +>15.3. <A +HREF="improved-browsing.html#AEN2713" +>Problem resolution</A ></DT ><DT ->16.4. <A -HREF="pdb-mysql.html#AEN2594" ->Getting non-column data from the table</A +>15.4. <A +HREF="improved-browsing.html#AEN2720" +>Browsing across subnets</A ></DT -></DL -></DD ><DT ->17. <A -HREF="pdb-xml.html" ->Passdb XML plugin</A +>15.5. <A +HREF="improved-browsing.html#AEN2760" +>Setting up a WINS server</A ></DT -><DD -><DL ><DT ->17.1. <A -HREF="pdb-xml.html#AEN2613" ->Building</A +>15.6. <A +HREF="improved-browsing.html#AEN2779" +>Setting up Browsing in a WORKGROUP</A ></DT ><DT ->17.2. <A -HREF="pdb-xml.html#AEN2619" ->Usage</A +>15.7. <A +HREF="improved-browsing.html#AEN2797" +>Setting up Browsing in a DOMAIN</A ></DT -></DL -></DD ><DT ->18. <A -HREF="vfs.html" ->Stackable VFS modules</A +>15.8. <A +HREF="improved-browsing.html#AEN2807" +>Forcing samba to be the master</A ></DT -><DD -><DL ><DT ->18.1. <A -HREF="vfs.html#AEN2640" ->Introduction and configuration</A +>15.9. <A +HREF="improved-browsing.html#AEN2816" +>Making samba the domain master</A ></DT ><DT ->18.2. <A -HREF="vfs.html#AEN2649" ->Included modules</A +>15.10. <A +HREF="improved-browsing.html#AEN2834" +>Note about broadcast addresses</A ></DT ><DT ->18.3. <A -HREF="vfs.html#AEN2703" ->VFS modules available elsewhere</A +>15.11. <A +HREF="improved-browsing.html#AEN2837" +>Multiple interfaces</A ></DT ></DL ></DD ><DT ->19. <A -HREF="samba-ldap-howto.html" ->Storing Samba's User/Machine Account information in an LDAP Directory</A +>16. <A +HREF="vfs.html" +>Stackable VFS modules</A ></DT ><DD ><DL ><DT ->19.1. <A -HREF="samba-ldap-howto.html#AEN2737" ->Purpose</A -></DT -><DT ->19.2. <A -HREF="samba-ldap-howto.html#AEN2757" ->Introduction</A -></DT -><DT ->19.3. <A -HREF="samba-ldap-howto.html#AEN2786" ->Supported LDAP Servers</A -></DT -><DT ->19.4. <A -HREF="samba-ldap-howto.html#AEN2791" ->Schema and Relationship to the RFC 2307 posixAccount</A -></DT -><DT ->19.5. <A -HREF="samba-ldap-howto.html#AEN2803" ->Configuring Samba with LDAP</A -></DT -><DT ->19.6. <A -HREF="samba-ldap-howto.html#AEN2850" ->Accounts and Groups management</A -></DT -><DT ->19.7. <A -HREF="samba-ldap-howto.html#AEN2855" ->Security and sambaAccount</A -></DT -><DT ->19.8. <A -HREF="samba-ldap-howto.html#AEN2875" ->LDAP specials attributes for sambaAccounts</A +>16.1. <A +HREF="vfs.html#AEN2855" +>Introduction and configuration</A ></DT ><DT ->19.9. <A -HREF="samba-ldap-howto.html#AEN2945" ->Example LDIF Entries for a sambaAccount</A +>16.2. <A +HREF="vfs.html#AEN2864" +>Included modules</A ></DT ><DT ->19.10. <A -HREF="samba-ldap-howto.html#AEN2953" ->Comments</A +>16.3. <A +HREF="vfs.html#AEN2918" +>VFS modules available elsewhere</A ></DT ></DL ></DD ><DT ->20. <A +>17. <A HREF="cvs-access.html" ->HOWTO Access Samba source code via CVS</A +>Access Samba source code via CVS</A ></DT ><DD ><DL ><DT ->20.1. <A -HREF="cvs-access.html#AEN2964" +>17.1. <A +HREF="cvs-access.html#AEN2942" >Introduction</A ></DT ><DT ->20.2. <A -HREF="cvs-access.html#AEN2969" +>17.2. <A +HREF="cvs-access.html#AEN2947" >CVS Access to samba.org</A ></DT ></DL ></DD ><DT ->21. <A +>18. <A HREF="groupmapping.html" >Group mapping HOWTO</A ></DT ><DT ->22. <A +>19. <A HREF="speed.html" >Samba performance issues</A ></DT ><DD ><DL ><DT ->22.1. <A -HREF="speed.html#AEN3055" +>19.1. <A +HREF="speed.html#AEN3033" >Comparisons</A ></DT ><DT ->22.2. <A -HREF="speed.html#AEN3061" +>19.2. <A +HREF="speed.html#AEN3039" >Socket options</A ></DT ><DT ->22.3. <A -HREF="speed.html#AEN3068" +>19.3. <A +HREF="speed.html#AEN3046" >Read size</A ></DT ><DT ->22.4. <A -HREF="speed.html#AEN3073" +>19.4. <A +HREF="speed.html#AEN3051" >Max xmit</A ></DT ><DT ->22.5. <A -HREF="speed.html#AEN3078" +>19.5. <A +HREF="speed.html#AEN3056" >Log level</A ></DT ><DT ->22.6. <A -HREF="speed.html#AEN3081" +>19.6. <A +HREF="speed.html#AEN3059" >Read raw</A ></DT ><DT ->22.7. <A -HREF="speed.html#AEN3086" +>19.7. <A +HREF="speed.html#AEN3064" >Write raw</A ></DT ><DT ->22.8. <A -HREF="speed.html#AEN3090" +>19.8. <A +HREF="speed.html#AEN3068" >Slow Clients</A ></DT ><DT ->22.9. <A -HREF="speed.html#AEN3094" +>19.9. <A +HREF="speed.html#AEN3072" >Slow Logins</A ></DT ><DT ->22.10. <A -HREF="speed.html#AEN3097" +>19.10. <A +HREF="speed.html#AEN3075" >Client tuning</A ></DT ></DL ></DD +><DT +>20. <A +HREF="groupprofiles.html" +>Creating Group Profiles</A +></DT +><DD +><DL +><DT +>20.1. <A +HREF="groupprofiles.html#AEN3123" +>Windows '9x</A +></DT +><DT +>20.2. <A +HREF="groupprofiles.html#AEN3132" +>Windows NT 4</A +></DT +><DT +>20.3. <A +HREF="groupprofiles.html#AEN3170" +>Windows 2000/XP</A +></DT +></DL +></DD ></DL ></DD ><DT @@ -886,132 +835,132 @@ HREF="appendixes.html" ><DD ><DL ><DT ->23. <A +>21. <A HREF="portability.html" >Portability</A ></DT ><DD ><DL ><DT ->23.1. <A -HREF="portability.html#AEN3139" +>21.1. <A +HREF="portability.html#AEN3251" >HPUX</A ></DT ><DT ->23.2. <A -HREF="portability.html#AEN3145" +>21.2. <A +HREF="portability.html#AEN3257" >SCO Unix</A ></DT ><DT ->23.3. <A -HREF="portability.html#AEN3149" +>21.3. <A +HREF="portability.html#AEN3261" >DNIX</A ></DT ><DT ->23.4. <A -HREF="portability.html#AEN3178" +>21.4. <A +HREF="portability.html#AEN3290" >RedHat Linux Rembrandt-II</A ></DT ></DL ></DD ><DT ->24. <A +>22. <A HREF="other-clients.html" >Samba and other CIFS clients</A ></DT ><DD ><DL ><DT ->24.1. <A -HREF="other-clients.html#AEN3199" +>22.1. <A +HREF="other-clients.html#AEN3311" >Macintosh clients?</A ></DT ><DT ->24.2. <A -HREF="other-clients.html#AEN3208" +>22.2. <A +HREF="other-clients.html#AEN3320" >OS2 Client</A ></DT ><DT ->24.3. <A -HREF="other-clients.html#AEN3248" +>22.3. <A +HREF="other-clients.html#AEN3360" >Windows for Workgroups</A ></DT ><DT ->24.4. <A -HREF="other-clients.html#AEN3269" +>22.4. <A +HREF="other-clients.html#AEN3381" >Windows '95/'98</A ></DT ><DT ->24.5. <A -HREF="other-clients.html#AEN3285" +>22.5. <A +HREF="other-clients.html#AEN3397" >Windows 2000 Service Pack 2</A ></DT ></DL ></DD ><DT ->25. <A +>23. <A HREF="bugreport.html" >Reporting Bugs</A ></DT ><DD ><DL ><DT ->25.1. <A -HREF="bugreport.html#AEN3309" +>23.1. <A +HREF="bugreport.html#AEN3421" >Introduction</A ></DT ><DT ->25.2. <A -HREF="bugreport.html#AEN3319" +>23.2. <A +HREF="bugreport.html#AEN3431" >General info</A ></DT ><DT ->25.3. <A -HREF="bugreport.html#AEN3325" +>23.3. <A +HREF="bugreport.html#AEN3437" >Debug levels</A ></DT ><DT ->25.4. <A -HREF="bugreport.html#AEN3342" +>23.4. <A +HREF="bugreport.html#AEN3454" >Internal errors</A ></DT ><DT ->25.5. <A -HREF="bugreport.html#AEN3352" +>23.5. <A +HREF="bugreport.html#AEN3464" >Attaching to a running process</A ></DT ><DT ->25.6. <A -HREF="bugreport.html#AEN3355" +>23.6. <A +HREF="bugreport.html#AEN3467" >Patches</A ></DT ></DL ></DD ><DT ->26. <A +>24. <A HREF="diagnosis.html" >Diagnosing your samba server</A ></DT ><DD ><DL ><DT ->26.1. <A -HREF="diagnosis.html#AEN3378" +>24.1. <A +HREF="diagnosis.html#AEN3490" >Introduction</A ></DT ><DT ->26.2. <A -HREF="diagnosis.html#AEN3383" +>24.2. <A +HREF="diagnosis.html#AEN3495" >Assumptions</A ></DT ><DT ->26.3. <A -HREF="diagnosis.html#AEN3393" +>24.3. <A +HREF="diagnosis.html#AEN3505" >Tests</A ></DT ><DT ->26.4. <A -HREF="diagnosis.html#AEN3503" +>24.4. <A +HREF="diagnosis.html#AEN3615" >Still having troubles?</A ></DT ></DL diff --git a/docs/htmldocs/samba-ldap-howto.html b/docs/htmldocs/samba-ldap-howto.html index 884bb756c1..fa966d8eb1 100644 --- a/docs/htmldocs/samba-ldap-howto.html +++ b/docs/htmldocs/samba-ldap-howto.html @@ -5,8 +5,7 @@ >Storing Samba's User/Machine Account information in an LDAP Directory</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ -"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -73,13 +72,17 @@ WIDTH="100%"></DIV CLASS="CHAPTER" ><H1 ><A -NAME="SAMBA-LDAP-HOWTO">Chapter 19. Storing Samba's User/Machine Account information in an LDAP Directory</H1 +NAME="SAMBA-LDAP-HOWTO" +></A +>Chapter 17. Storing Samba's User/Machine Account information in an LDAP Directory</H1 ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2737">19.1. Purpose</H1 +NAME="AEN2957" +></A +>17.1. Purpose</H1 ><P >This document describes how to use an LDAP directory for storing Samba user account information traditionally stored in the smbpasswd(5) file. It is @@ -145,7 +148,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2757">19.2. Introduction</H1 +NAME="AEN2977" +></A +>17.2. Introduction</H1 ><P >Traditionally, when configuring <A HREF="smb.conf.5.html#ENCRYPTPASSWORDS" @@ -260,7 +265,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2786">19.3. Supported LDAP Servers</H1 +NAME="AEN3006" +></A +>17.3. Supported LDAP Servers</H1 ><P >The LDAP samdb code in 2.2.3 has been developed and tested using the OpenLDAP 2.0 server and client libraries. The same code should be able to work with @@ -283,7 +290,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2791">19.4. Schema and Relationship to the RFC 2307 posixAccount</H1 +NAME="AEN3011" +></A +>17.4. Schema and Relationship to the RFC 2307 posixAccount</H1 ><P >Samba 2.2.3 includes the necessary schema file for OpenLDAP 2.0 in <TT @@ -340,13 +349,17 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2803">19.5. Configuring Samba with LDAP</H1 +NAME="AEN3023" +></A +>17.5. Configuring Samba with LDAP</H1 ><DIV CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2805">19.5.1. OpenLDAP configuration</H2 +NAME="AEN3025" +></A +>17.5.1. OpenLDAP configuration</H2 ><P >To include support for the sambaAccount object in an OpenLDAP directory server, first copy the samba.schema file to slapd's configuration directory.</P @@ -426,7 +439,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2822">19.5.2. Configuring Samba</H2 +NAME="AEN3042" +></A +>17.5.2. Configuring Samba</H2 ><P >The following parameters are available in smb.conf only with <TT CLASS="PARAMETER" @@ -544,7 +559,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2850">19.6. Accounts and Groups management</H1 +NAME="AEN3070" +></A +>17.6. Accounts and Groups management</H1 ><P >As users accounts are managed thru the sambaAccount objectclass, you should modify you existing administration tools to deal with sambaAccount attributes.</P @@ -567,7 +584,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2855">19.7. Security and sambaAccount</H1 +NAME="AEN3075" +></A +>17.7. Security and sambaAccount</H1 ><P >There are two important points to remember when discussing the security of sambaAccount entries in the directory.</P @@ -644,7 +663,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2875">19.8. LDAP specials attributes for sambaAccounts</H1 +NAME="AEN3095" +></A +>17.8. LDAP specials attributes for sambaAccounts</H1 ><P >The sambaAccount objectclass is composed of the following attributes:</P ><P @@ -853,7 +874,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2945">19.9. Example LDIF Entries for a sambaAccount</H1 +NAME="AEN3165" +></A +>17.9. Example LDIF Entries for a sambaAccount</H1 ><P >The following is a working LDIF with the inclusion of the posixAccount objectclass:</P ><P @@ -909,7 +932,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2953">19.10. Comments</H1 +NAME="AEN3173" +></A +>17.10. Comments</H1 ><P >Please mail all comments regarding this HOWTO to <A HREF="mailto:jerry@samba.org" diff --git a/docs/htmldocs/samba-pdc.html b/docs/htmldocs/samba-pdc.html index 93bbc727d4..63a52129d0 100644 --- a/docs/htmldocs/samba-pdc.html +++ b/docs/htmldocs/samba-pdc.html @@ -2,11 +2,10 @@ <HTML ><HEAD ><TITLE ->How to Configure Samba as a NT4 Primary Domain Controller</TITLE +>Samba as a NT4 or Win2k Primary Domain Controller</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ -"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -73,13 +72,17 @@ WIDTH="100%"></DIV CLASS="CHAPTER" ><H1 ><A -NAME="SAMBA-PDC">Chapter 6. How to Configure Samba as a NT4 Primary Domain Controller</H1 +NAME="SAMBA-PDC" +></A +>Chapter 5. Samba as a NT4 or Win2k Primary Domain Controller</H1 ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN575">6.1. Prerequisite Reading</H1 +NAME="AEN722" +></A +>5.1. Prerequisite Reading</H1 ><P >Before you continue reading in this chapter, please make sure that you are comfortable with configuring basic files services @@ -105,7 +108,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN581">6.2. Background</H1 +NAME="AEN728" +></A +>5.2. Background</H1 ><DIV CLASS="NOTE" ><P @@ -120,7 +125,7 @@ WIDTH="25" ALIGN="CENTER" VALIGN="TOP" ><IMG -SRC="../images/note.gif" +SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif" HSPACE="5" ALT="Note"></TD ><TD @@ -255,7 +260,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN620">6.3. Configuring the Samba Domain Controller</H1 +NAME="AEN767" +></A +>5.3. Configuring the Samba Domain Controller</H1 ><P >The first step in creating a working Samba PDC is to understand the parameters necessary in smb.conf. I will not @@ -465,7 +472,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN663">6.4. Creating Machine Trust Accounts and Joining Clients to the +NAME="AEN810" +></A +>5.4. Creating Machine Trust Accounts and Joining Clients to the Domain</H1 ><P >A machine trust account is a Samba account that is used to @@ -537,7 +546,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN682">6.4.1. Manual Creation of Machine Trust Accounts</H2 +NAME="AEN829" +></A +>5.4.1. Manual Creation of Machine Trust Accounts</H2 ><P >The first step in manually creating a machine trust account is to manually create the corresponding Unix account in @@ -689,7 +700,7 @@ WIDTH="25" ALIGN="CENTER" VALIGN="TOP" ><IMG -SRC="../images/warning.gif" +SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/warning.gif" HSPACE="5" ALT="Warning"></TD ><TH @@ -725,7 +736,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN723">6.4.2. "On-the-Fly" Creation of Machine Trust Accounts</H2 +NAME="AEN870" +></A +>5.4.2. "On-the-Fly" Creation of Machine Trust Accounts</H2 ><P >The second (and recommended) way of creating machine trust accounts is simply to allow the Samba server to create them as needed when the client @@ -751,7 +764,7 @@ be created manually.</P ><PRE CLASS="PROGRAMLISTING" >[global] - # <...remainder of parameters...> + # <...remainder of parameters...> add user script = /usr/sbin/useradd -d /dev/null -g 100 -s /bin/false -M %u </PRE ></P ></DIV @@ -760,7 +773,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN732">6.4.3. Joining the Client to the Domain</H2 +NAME="AEN879" +></A +>5.4.3. Joining the Client to the Domain</H2 ><P >The procedure for joining a client to the domain varies with the version of Windows.</P @@ -826,7 +841,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN747">6.5. Common Problems and Errors</H1 +NAME="AEN894" +></A +>5.5. Common Problems and Errors</H1 ><P ></P ><P @@ -1034,7 +1051,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN795">6.6. System Policies and Profiles</H1 +NAME="AEN942" +></A +>5.6. System Policies and Profiles</H1 ><P >Much of the information necessary to implement System Policies and Roving User Profiles in a Samba domain is the same as that for @@ -1209,7 +1228,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN839">6.7. What other help can I get?</H1 +NAME="AEN986" +></A +>5.7. What other help can I get?</H1 ><P >There are many sources of information available in the form of mailing lists, RFC's and documentation. The docs that come @@ -1627,7 +1648,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN953">6.8. Domain Control for Windows 9x/ME</H1 +NAME="AEN1100" +></A +>5.8. Domain Control for Windows 9x/ME</H1 ><DIV CLASS="NOTE" ><P @@ -1642,7 +1665,7 @@ WIDTH="25" ALIGN="CENTER" VALIGN="TOP" ><IMG -SRC="../images/note.gif" +SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif" HSPACE="5" ALT="Note"></TD ><TD @@ -1704,7 +1727,7 @@ TYPE="1" ><LI ><P > The client broadcasts (to the IP broadcast address of the subnet it is in) - a NetLogon request. This is sent to the NetBIOS name DOMAIN<1c> at the + a NetLogon request. This is sent to the NetBIOS name DOMAIN<1c> at the NetBIOS layer. The client chooses the first response it receives, which contains the NetBIOS name of the logon server to use in the format of \\SERVER. @@ -1759,7 +1782,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN979">6.8.1. Configuration Instructions: Network Logons</H2 +NAME="AEN1126" +></A +>5.8.1. Configuration Instructions: Network Logons</H2 ><P >The main difference between a PDC and a Windows 9x logon server configuration is that</P @@ -1792,7 +1817,7 @@ WIDTH="25" ALIGN="CENTER" VALIGN="TOP" ><IMG -SRC="../images/warning.gif" +SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/warning.gif" HSPACE="5" ALT="Warning"></TD ><TH @@ -1863,7 +1888,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN998">6.8.2. Configuration Instructions: Setting up Roaming User Profiles</H2 +NAME="AEN1145" +></A +>5.8.2. Configuration Instructions: Setting up Roaming User Profiles</H2 ><DIV CLASS="WARNING" ><P @@ -1878,7 +1905,7 @@ WIDTH="25" ALIGN="CENTER" VALIGN="TOP" ><IMG -SRC="../images/warning.gif" +SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/warning.gif" HSPACE="5" ALT="Warning"></TD ><TD @@ -1914,7 +1941,9 @@ CLASS="SECT3" ><H3 CLASS="SECT3" ><A -NAME="AEN1006">6.8.2.1. Windows NT Configuration</H3 +NAME="AEN1153" +></A +>5.8.2.1. Windows NT Configuration</H3 ><P >To support WinNT clients, in the [global] section of smb.conf set the following (for example):</P @@ -1943,7 +1972,7 @@ WIDTH="25" ALIGN="CENTER" VALIGN="TOP" ><IMG -SRC="../images/note.gif" +SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif" HSPACE="5" ALT="Note"></TD ><TD @@ -1963,7 +1992,9 @@ CLASS="SECT3" ><H3 CLASS="SECT3" ><A -NAME="AEN1014">6.8.2.2. Windows 9X Configuration</H3 +NAME="AEN1161" +></A +>5.8.2.2. Windows 9X Configuration</H3 ><P >To support Win9X clients, you must use the "logon home" parameter. Samba has now been fixed so that "net use/home" now works as well, and it, too, relies @@ -1992,7 +2023,9 @@ CLASS="SECT3" ><H3 CLASS="SECT3" ><A -NAME="AEN1022">6.8.2.3. Win9X and WinNT Configuration</H3 +NAME="AEN1169" +></A +>5.8.2.3. Win9X and WinNT Configuration</H3 ><P >You can support profiles for both Win9X and WinNT clients by setting both the "logon home" and "logon path" parameters. For example:</P @@ -2016,7 +2049,7 @@ WIDTH="25" ALIGN="CENTER" VALIGN="TOP" ><IMG -SRC="../images/note.gif" +SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif" HSPACE="5" ALT="Note"></TD ><TD @@ -2035,7 +2068,9 @@ CLASS="SECT3" ><H3 CLASS="SECT3" ><A -NAME="AEN1029">6.8.2.4. Windows 9X Profile Setup</H3 +NAME="AEN1176" +></A +>5.8.2.4. Windows 9X Profile Setup</H3 ><P >When a user first logs in on Windows 9X, the file user.DAT is created, as are folders "Start Menu", "Desktop", "Programs" and "Nethood". @@ -2193,7 +2228,9 @@ CLASS="SECT3" ><H3 CLASS="SECT3" ><A -NAME="AEN1065">6.8.2.5. Windows NT Workstation 4.0</H3 +NAME="AEN1212" +></A +>5.8.2.5. Windows NT Workstation 4.0</H3 ><P >When a user first logs in to a Windows NT Workstation, the profile NTuser.DAT is created. The profile location can be now specified @@ -2212,7 +2249,7 @@ WIDTH="25" ALIGN="CENTER" VALIGN="TOP" ><IMG -SRC="../images/note.gif" +SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif" HSPACE="5" ALT="Note"></TD ><TD @@ -2270,7 +2307,7 @@ WIDTH="25" ALIGN="CENTER" VALIGN="TOP" ><IMG -SRC="../images/note.gif" +SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif" HSPACE="5" ALT="Note"></TD ><TD @@ -2305,7 +2342,9 @@ CLASS="SECT3" ><H3 CLASS="SECT3" ><A -NAME="AEN1078">6.8.2.6. Windows NT Server</H3 +NAME="AEN1225" +></A +>5.8.2.6. Windows NT Server</H3 ><P >There is nothing to stop you specifying any path that you like for the location of users' profiles. Therefore, you could specify that the @@ -2317,7 +2356,9 @@ CLASS="SECT3" ><H3 CLASS="SECT3" ><A -NAME="AEN1081">6.8.2.7. Sharing Profiles between W95 and NT Workstation 4.0</H3 +NAME="AEN1228" +></A +>5.8.2.7. Sharing Profiles between W95 and NT Workstation 4.0</H3 ><DIV CLASS="WARNING" ><P @@ -2332,7 +2373,7 @@ WIDTH="25" ALIGN="CENTER" VALIGN="TOP" ><IMG -SRC="../images/warning.gif" +SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/warning.gif" HSPACE="5" ALT="Warning"></TD ><TH @@ -2384,7 +2425,7 @@ WIDTH="25" ALIGN="CENTER" VALIGN="TOP" ><IMG -SRC="../images/note.gif" +SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif" HSPACE="5" ALT="Note"></TD ><TD @@ -2408,7 +2449,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1091">6.9. DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba</H1 +NAME="AEN1238" +></A +>5.9. DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba</H1 ><DIV CLASS="WARNING" ><P @@ -2423,7 +2466,7 @@ WIDTH="25" ALIGN="CENTER" VALIGN="TOP" ><IMG -SRC="../images/warning.gif" +SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/warning.gif" HSPACE="5" ALT="Warning"></TD ><TH diff --git a/docs/htmldocs/samba.7.html b/docs/htmldocs/samba.7.html index 0851e99bd5..796bce7d20 100644 --- a/docs/htmldocs/samba.7.html +++ b/docs/htmldocs/samba.7.html @@ -5,7 +5,7 @@ >samba</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77"></HEAD +CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"></HEAD ><BODY CLASS="REFENTRY" BGCOLOR="#FFFFFF" @@ -15,7 +15,7 @@ VLINK="#840084" ALINK="#0000FF" ><H1 ><A -NAME="SAMBA" +NAME="SAMBA.7" ></A >samba</H1 ><DIV @@ -25,7 +25,7 @@ NAME="AEN5" ></A ><H2 >Name</H2 ->SAMBA -- A Windows SMB/CIFS fileserver for UNIX</DIV +>Samba -- A Windows SMB/CIFS fileserver for UNIX</DIV ><DIV CLASS="REFSYNOPSISDIV" ><A @@ -63,29 +63,37 @@ TARGET="_top" CLASS="VARIABLELIST" ><DL ><DT -><B -CLASS="COMMAND" ->smbd</B +><SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbd</SPAN +>(8)</SPAN ></DT ><DD ><P >The <B CLASS="COMMAND" ->smbd </B -> - daemon provides the file and print services to +>smbd</B +> daemon provides the file and print services to SMB clients, such as Windows 95/98, Windows NT, Windows for Workgroups or LanManager. The configuration file - for this daemon is described in <TT -CLASS="FILENAME" ->smb.conf</TT + for this daemon is described in <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smb.conf</SPAN +>(5)</SPAN > </P ></DD ><DT -><B -CLASS="COMMAND" ->nmbd</B +><SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>nmbd</SPAN +>(8)</SPAN ></DT ><DD ><P @@ -95,15 +103,21 @@ CLASS="COMMAND" > daemon provides NetBIOS nameservice and browsing support. The configuration file for this daemon - is described in <TT -CLASS="FILENAME" ->smb.conf</TT + is described in <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smb.conf</SPAN +>(5)</SPAN ></P ></DD ><DT -><B -CLASS="COMMAND" ->smbclient</B +><SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbclient</SPAN +>(1)</SPAN ></DT ><DD ><P @@ -118,9 +132,12 @@ CLASS="COMMAND" any SMB server (such as a PC running Windows NT).</P ></DD ><DT -><B -CLASS="COMMAND" ->testparm</B +><SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>testparm</SPAN +>(1)</SPAN ></DT ><DD ><P @@ -128,16 +145,21 @@ CLASS="COMMAND" CLASS="COMMAND" >testparm</B > - utility is a simple syntax checker for Samba's - <TT -CLASS="FILENAME" ->smb.conf</TT ->configuration file.</P + utility is a simple syntax checker for Samba's <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smb.conf</SPAN +>(5)</SPAN +> configuration file.</P ></DD ><DT -><B -CLASS="COMMAND" ->testprns</B +><SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>testprns</SPAN +>(1)</SPAN ></DT ><DD ><P @@ -153,9 +175,12 @@ CLASS="FILENAME" by Samba.</P ></DD ><DT -><B -CLASS="COMMAND" ->smbstatus</B +><SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbstatus</SPAN +>(1)</SPAN ></DT ><DD ><P @@ -170,9 +195,12 @@ CLASS="COMMAND" >.</P ></DD ><DT -><B -CLASS="COMMAND" ->nmblookup</B +><SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>nmblookup</SPAN +>(1)</SPAN ></DT ><DD ><P @@ -184,26 +212,30 @@ CLASS="COMMAND" from a UNIX host.</P ></DD ><DT -><B -CLASS="COMMAND" ->make_smbcodepage</B +><SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbgroupedit</SPAN +>(8)</SPAN ></DT ><DD ><P >The <B CLASS="COMMAND" ->make_smbcodepage</B +>smbgroupedit</B > - utility provides a means of creating SMB code page - definition files for your <B -CLASS="COMMAND" ->smbd</B -> server.</P + tool allows for mapping unix groups to NT Builtin, + Domain, or Local groups. Also it allows setting + priviledges for that group, such as saAddUser, etc.</P ></DD ><DT -><B -CLASS="COMMAND" ->smbpasswd</B +><SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbpasswd</SPAN +>(8)</SPAN ></DT ><DD ><P @@ -220,7 +252,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN76" +NAME="AEN99" ></A ><H2 >COMPONENTS</H2 @@ -249,7 +281,7 @@ TARGET="_top" ><DIV CLASS="REFSECT1" ><A -NAME="AEN82" +NAME="AEN105" ></A ><H2 >AVAILABILITY</H2 @@ -274,8 +306,8 @@ TARGET="_top" list. Details on how to join the mailing list are given in the README file that comes with Samba.</P ><P ->If you have access to a WWW viewer (such as Netscape - or Mosaic) then you will also find lots of useful information, +>If you have access to a WWW viewer (such as Mozilla + or Konqueror) then you will also find lots of useful information, including back issues of the Samba mailing list, at <A HREF="http://lists.samba.org/" @@ -286,18 +318,18 @@ TARGET="_top" ><DIV CLASS="REFSECT1" ><A -NAME="AEN90" +NAME="AEN113" ></A ><H2 >VERSION</H2 ><P ->This man page is correct for version 2.2 of the +>This man page is correct for version 3.0 of the Samba suite. </P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN93" +NAME="AEN116" ></A ><H2 >CONTRIBUTIONS</H2 @@ -317,8 +349,8 @@ HREF="http://devel.samba.org/" TARGET="_top" >http://devel.samba.org/</A > - for information on how to do it properly. We prefer patches in - <B + for information on how to do it properly. We prefer patches + in <B CLASS="COMMAND" >diff -u</B > format.</P @@ -326,7 +358,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN100" +NAME="AEN123" ></A ><H2 >CONTRIBUTORS</H2 @@ -358,7 +390,7 @@ TARGET="_top" ><DIV CLASS="REFSECT1" ><A -NAME="AEN107" +NAME="AEN130" ></A ><H2 >AUTHOR</H2 @@ -370,14 +402,14 @@ NAME="AEN107" ><P >The original Samba man pages were written by Karl Auer. The man page sources were converted to YODL format (another - excellent piece of Open Source software, available at - <A + excellent piece of Open Source software, available at <A HREF="ftp://ftp.icce.rug.nl/pub/unix/" TARGET="_top" > ftp://ftp.icce.rug.nl/pub/unix/</A >) and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for - Samba 2.2 was done by Gerald Carter</P + Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML + 4.2 for Samba 3.0 was done by Alexander Bokovoy.</P ></DIV ></BODY ></HTML diff --git a/docs/htmldocs/securitylevels.html b/docs/htmldocs/securitylevels.html index f1b9967540..9501fa5c6a 100644 --- a/docs/htmldocs/securitylevels.html +++ b/docs/htmldocs/securitylevels.html @@ -5,8 +5,7 @@ >User and Share security level (for servers not in a domain)</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ -"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -17,7 +16,7 @@ REL="PREVIOUS" TITLE="Type of installation" HREF="type.html"><LINK REL="NEXT" -TITLE="How to Configure Samba as a NT4 Primary Domain Controller" +TITLE="Samba as a NT4 or Win2k Primary Domain Controller" HREF="samba-pdc.html"></HEAD ><BODY CLASS="CHAPTER" @@ -73,7 +72,9 @@ WIDTH="100%"></DIV CLASS="CHAPTER" ><H1 ><A -NAME="SECURITYLEVELS">Chapter 5. User and Share security level (for servers not in a domain)</H1 +NAME="SECURITYLEVELS" +></A +>Chapter 4. User and Share security level (for servers not in a domain)</H1 ><P >A SMB server tells the client at startup what "security level" it is running. There are two options "share level" and "user level". Which @@ -225,7 +226,7 @@ ACCESSKEY="U" WIDTH="33%" ALIGN="right" VALIGN="top" ->How to Configure Samba as a NT4 Primary Domain Controller</TD +>Samba as a NT4 or Win2k Primary Domain Controller</TD ></TR ></TABLE ></DIV diff --git a/docs/htmldocs/smb.conf.5.html b/docs/htmldocs/smb.conf.5.html index 9c1ee7a67b..5a8bfe7d67 100644 --- a/docs/htmldocs/smb.conf.5.html +++ b/docs/htmldocs/smb.conf.5.html @@ -1,12 +1,11 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"> +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <HTML ><HEAD ><TITLE >smb.conf</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ -"></HEAD +CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"></HEAD ><BODY CLASS="REFENTRY" BGCOLOR="#FFFFFF" @@ -16,7 +15,9 @@ VLINK="#840084" ALINK="#0000FF" ><H1 ><A -NAME="SMB.CONF">smb.conf</H1 +NAME="SMB.CONF.5" +></A +>smb.conf</H1 ><DIV CLASS="REFNAMEDIV" ><A @@ -36,31 +37,29 @@ NAME="AEN8" >The <TT CLASS="FILENAME" >smb.conf</TT -> file is a configuration +> file is a configuration file for the Samba suite. <TT CLASS="FILENAME" >smb.conf</TT -> contains - runtime configuration information for the Samba programs. The - <TT +> contains + runtime configuration information for the Samba programs. The <TT CLASS="FILENAME" >smb.conf</TT -> file is designed to be configured and - administered by the <A -HREF="swat.8.html" -TARGET="_top" -><B -CLASS="COMMAND" ->swat(8)</B -> - </A -> program. The complete description of the file format and - possible parameters held within are here for reference purposes.</P +> file + is designed to be configured and administered by the <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>swat</SPAN +>(8)</SPAN +> program. The complete + description of the file format and possible parameters held within + are here for reference purposes.</P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN16" +NAME="AEN17" ></A ><H2 >FILE FORMAT</H2 @@ -110,7 +109,7 @@ CLASS="REPLACEABLE" ><DIV CLASS="REFSECT1" ><A -NAME="AEN28" +NAME="AEN29" ></A ><H2 >SECTION DESCRIPTIONS</H2 @@ -123,9 +122,12 @@ NAME="AEN28" ><P >There are three special sections, [global], [homes] and [printers], which are - described under <I + described under <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >special sections</I +></SPAN >. The following notes apply to ordinary section descriptions.</P ><P @@ -139,14 +141,20 @@ CLASS="EMPHASIS" printable services (used by the client to access print services on the host running the server).</P ><P ->Sections may be designated <I +>Sections may be designated <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >guest</I +></SPAN > services, in which case no password is required to access them. A specified - UNIX <I + UNIX <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >guest account</I +></SPAN > is used to define access privileges in this case.</P ><P @@ -168,68 +176,49 @@ CLASS="FILENAME" >/home/bar</TT >. The share is accessed via the share name "foo":</P -><TABLE -BORDER="0" -BGCOLOR="#E0E0E0" -WIDTH="100%" -><TR -><TD ><PRE CLASS="SCREEN" -> <TT +><TT CLASS="COMPUTEROUTPUT" -> [foo] - path = /home/bar - read only = no - </TT -> - </PRE -></TD -></TR -></TABLE +>[foo] + path = /home/bar + read only = no</TT +></PRE ><P >The following sample section defines a printable share. The share is readonly, but printable. That is, the only write access permitted is via calls to open, write to and close a - spool file. The <I + spool file. The <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >guest ok</I +></SPAN > parameter means access will be permitted as the default guest user (specified elsewhere):</P -><TABLE -BORDER="0" -BGCOLOR="#E0E0E0" -WIDTH="100%" -><TR -><TD ><PRE CLASS="SCREEN" -> <TT +><TT CLASS="COMPUTEROUTPUT" -> [aprinter] - path = /usr/spool/public - read only = yes - printable = yes - guest ok = yes - </TT -> - </PRE -></TD -></TR -></TABLE +>[aprinter] + path = /usr/spool/public + read only = yes + printable = yes + guest ok = yes</TT +></PRE ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN48" +NAME="AEN49" ></A ><H2 >SPECIAL SECTIONS</H2 ><DIV CLASS="REFSECT2" ><A -NAME="AEN50" +NAME="AEN51" ></A ><H3 >The [global] section</H3 @@ -242,7 +231,7 @@ NAME="AEN50" ><DIV CLASS="REFSECT2" ><A -NAME="AEN53" +NAME="AEN54" ></A ><H3 >The [homes] section</H3 @@ -275,9 +264,12 @@ NAME="AEN53" ></LI ></UL ><P ->If you decide to use a <I +>If you decide to use a <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >path =</I +></SPAN > line in your [homes] section then you may find it useful to use the %S macro. For example :</P @@ -306,47 +298,48 @@ CLASS="USERINPUT" a normal service section can specify, though some make more sense than others. The following is a typical and suitable [homes] section:</P -><TABLE -BORDER="0" -BGCOLOR="#E0E0E0" -WIDTH="100%" -><TR -><TD ><PRE CLASS="SCREEN" -> <TT +><TT CLASS="COMPUTEROUTPUT" -> [homes] - read only = no - </TT -> - </PRE -></TD -></TR -></TABLE +>[homes] + read only = no</TT +></PRE ><P >An important point is that if guest access is specified in the [homes] section, all home directories will be - visible to all clients <I + visible to all clients <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >without a password</I +></SPAN >. In the very unlikely event that this is actually desirable, it - would be wise to also specify <I + would be wise to also specify <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >read only access</I +></SPAN >.</P ><P ->Note that the <I +>Note that the <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >browseable</I +></SPAN > flag for auto home directories will be inherited from the global browseable flag, not the [homes] browseable flag. This is useful as - it means setting <I + it means setting <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >browseable = no</I +></SPAN > in the [homes] section will hide the [homes] share but make any auto home directories visible.</P @@ -354,7 +347,7 @@ CLASS="EMPHASIS" ><DIV CLASS="REFSECT2" ><A -NAME="AEN79" +NAME="AEN80" ></A ><H3 >The [printers] section</H3 @@ -406,48 +399,27 @@ NAME="AEN79" world-writeable spool directory with the sticky bit set on it. A typical [printers] entry would look like this:</P -><TABLE -BORDER="0" -BGCOLOR="#E0E0E0" -WIDTH="100%" -><TR -><TD ><PRE CLASS="SCREEN" ><TT CLASS="COMPUTEROUTPUT" -> [printers] - path = /usr/spool/public - guest ok = yes - printable = yes - </TT +>[printers] + path = /usr/spool/public + guest ok = yes + printable = yes </TT ></PRE -></TD -></TR -></TABLE ><P >All aliases given for a printer in the printcap file are legitimate printer names as far as the server is concerned. If your printing subsystem doesn't work like that, you will have to set up a pseudo-printcap. This is a file consisting of one or more lines like this:</P -><TABLE -BORDER="0" -BGCOLOR="#E0E0E0" -WIDTH="100%" -><TR -><TD ><PRE CLASS="SCREEN" -> <TT +><TT CLASS="COMPUTEROUTPUT" -> alias|alias|alias|alias... - </TT -> - </PRE -></TD -></TR -></TABLE +>alias|alias|alias|alias... </TT +></PRE ><P >Each alias should be an acceptable printer name for your printing subsystem. In the [global] section, specify @@ -471,7 +443,7 @@ CLASS="COMPUTEROUTPUT" ><DIV CLASS="REFSECT1" ><A -NAME="AEN102" +NAME="AEN103" ></A ><H2 >PARAMETERS</H2 @@ -479,29 +451,44 @@ NAME="AEN102" >parameters define the specific attributes of sections.</P ><P >Some parameters are specific to the [global] section - (e.g., <I + (e.g., <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >security</I +></SPAN >). Some parameters are usable - in all sections (e.g., <I + in all sections (e.g., <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >create mode</I +></SPAN >). All others are permissible only in normal sections. For the purposes of the following descriptions the [homes] and [printers] - sections will be considered normal. The letter <I + sections will be considered normal. The letter <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >G</I +></SPAN > in parentheses indicates that a parameter is specific to the - [global] section. The letter <I + [global] section. The letter <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >S</I +></SPAN > indicates that a parameter can be specified in a service specific - section. Note that all <I + section. Note that all <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >S</I +></SPAN > parameters can also be specified in the [global] section - in which case they will define the default behavior for all services.</P @@ -514,7 +501,7 @@ CLASS="EMPHASIS" ><DIV CLASS="REFSECT1" ><A -NAME="AEN112" +NAME="AEN113" ></A ><H2 >VARIABLE SUBSTITUTIONS</H2 @@ -691,9 +678,12 @@ CLASS="VARIABLELIST" ><P >the name of your NIS home directory server. This is obtained from your NIS auto.map entry. If you have - not compiled Samba with the <I + not compiled Samba with the <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >--with-automount</I +></SPAN > option then this value will be the same as %L.</P ></DD @@ -714,7 +704,7 @@ CLASS="EMPHASIS" ><DIV CLASS="REFSECT1" ><A -NAME="AEN205" +NAME="AEN206" ></A ><H2 >NAME MANGLING</H2 @@ -743,9 +733,12 @@ CLASS="VARIABLELIST" > controls if names that have characters that aren't of the "default" case are mangled. For example, if this is yes then a name like "Mail" would be mangled. - Default <I + Default <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >no</I +></SPAN >.</P ></DD ><DT @@ -754,9 +747,12 @@ CLASS="EMPHASIS" ><P >controls whether filenames are case sensitive. If they aren't then Samba must do a filename search and match on passed - names. Default <I + names. Default <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >no</I +></SPAN >.</P ></DD ><DT @@ -764,9 +760,12 @@ CLASS="EMPHASIS" ><DD ><P >controls what the default case is for new - filenames. Default <I + filenames. Default <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >lower</I +></SPAN >.</P ></DD ><DT @@ -775,9 +774,12 @@ CLASS="EMPHASIS" ><P >controls if new files are created with the case that the client passes, or if they are forced to be the - "default" case. Default <I + "default" case. Default <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >yes</I +></SPAN >. </P ></DD @@ -790,9 +792,12 @@ CLASS="EMPHASIS" upper case, or if they are forced to be the "default" case. This option can be use with "preserve case = yes" to permit long filenames to retain their case, while short names - are lowercased. Default <I + are lowercased. Default <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >yes</I +></SPAN >.</P ></DD ></DL @@ -804,7 +809,7 @@ CLASS="EMPHASIS" ><DIV CLASS="REFSECT1" ><A -NAME="AEN238" +NAME="AEN239" ></A ><H2 >NOTE ABOUT USERNAME/PASSWORD VALIDATION</H2 @@ -882,7 +887,7 @@ CLASS="FILENAME" ><DIV CLASS="REFSECT1" ><A -NAME="AEN257" +NAME="AEN258" ></A ><H2 >COMPLETE LIST OF GLOBAL PARAMETERS</H2 @@ -3177,7 +3182,7 @@ CLASS="PARAMETER" ><DIV CLASS="REFSECT1" ><A -NAME="AEN1021" +NAME="AEN1022" ></A ><H2 >COMPLETE LIST OF SERVICE PARAMETERS</H2 @@ -4692,7 +4697,7 @@ CLASS="PARAMETER" ><DIV CLASS="REFSECT1" ><A -NAME="AEN1525" +NAME="AEN1526" ></A ><H2 >EXPLANATION OF EACH PARAMETER</H2 @@ -4705,22 +4710,23 @@ CLASS="VARIABLELIST" ><A NAME="ABORTSHUTDOWNSCRIPT" ></A ->abort shutdown script (G)</DT +>>abort shutdown script (G)</DT ><DD ><P +><SPAN +CLASS="emphasis" ><I CLASS="EMPHASIS" >This parameter only exists in the HEAD cvs branch</I +></SPAN > - This a full path name to a script called by - <A -HREF="smbd.8.html" -TARGET="_top" -><B -CLASS="COMMAND" ->smbd(8)</B -></A -> that + This a full path name to a script called by <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbd</SPAN +>(8)</SPAN +> that should stop a shutdown procedure issued by the <A HREF="#SHUTDOWNSCRIPT" ><TT @@ -4733,9 +4739,12 @@ CLASS="PARAMETER" ><P >This command will be run as user.</P ><P ->Default: <I +>Default: <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >None</I +></SPAN >.</P ><P >Example: <B @@ -4747,7 +4756,7 @@ CLASS="COMMAND" ><A NAME="ADDPRINTERCOMMAND" ></A ->addprinter command (G)</DT +>>addprinter command (G)</DT ><DD ><P >With the introduction of MS-RPC based printing @@ -4771,14 +4780,12 @@ CLASS="PARAMETER" CLASS="FILENAME" >smb.conf</TT > file in order that it can be - shared by <A -HREF="smbd.8.html" -TARGET="_top" -><B -CLASS="COMMAND" ->smbd(8)</B -> - </A + shared by <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbd</SPAN +>(8)</SPAN >.</P ><P >The <TT @@ -4788,7 +4795,7 @@ CLASS="PARAMETER" ></TT > is automatically invoked with the following parameter (in - order:</P + order):</P ><P ></P ><UL @@ -4902,9 +4909,12 @@ CLASS="PARAMETER" ></A ></P ><P ->Default: <I +>Default: <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >none</I +></SPAN ></P ><P >Example: <B @@ -4917,7 +4927,7 @@ CLASS="COMMAND" ><A NAME="ADDSHARECOMMAND" ></A ->add share command (G)</DT +>>add share command (G)</DT ><DD ><P >Samba 2.2.0 introduced the ability to dynamically @@ -5043,9 +5053,12 @@ CLASS="PARAMETER" >. </P ><P ->Default: <I +>Default: <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >none</I +></SPAN ></P ><P >Example: <B @@ -5057,15 +5070,17 @@ CLASS="COMMAND" ><A NAME="ADDMACHINESCRIPT" ></A ->add machine script (G)</DT +>>add machine script (G)</DT ><DD ><P >This is the full pathname to a script that will - be run by <A -HREF="smbd.8.html" -TARGET="_top" ->smbd(8)</A -> when a machine is added + be run by <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbd</SPAN +>(8)</SPAN +> when a machine is added to it's domain using the administrator username and password method. </P ><P >This option is only required when using sam back-ends tied to the @@ -5074,7 +5089,7 @@ TARGET="_top" ><P >Default: <B CLASS="COMMAND" ->add machine script = <empty string> +>add machine script = <empty string> </B ></P ><P @@ -5088,7 +5103,7 @@ CLASS="COMMAND" ><A NAME="ADSSERVER" ></A ->ads server (G)</DT +>>ads server (G)</DT ><DD ><P >If this option is specified, samba does @@ -5110,18 +5125,22 @@ CLASS="COMMAND" ><A NAME="ADDUSERSCRIPT" ></A ->add user script (G)</DT +>>add user script (G)</DT ><DD ><P >This is the full pathname to a script that will - be run <I + be run <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >AS ROOT</I -> by <A -HREF="smbd.8.html" -TARGET="_top" ->smbd(8) - </A +></SPAN +> by <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbd</SPAN +>(8)</SPAN > under special circumstances described below.</P ><P >Normally, a Samba server requires that UNIX users are @@ -5133,19 +5152,26 @@ HREF="smbd.8.html" TARGET="_top" >smbd</A > to create the required UNIX users - <I + <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >ON DEMAND</I +></SPAN > when a user accesses the Samba server.</P ><P ->In order to use this option, <A -HREF="smbd.8.html" -TARGET="_top" ->smbd</A -> - must <I +>In order to use this option, <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbd</SPAN +>(8)</SPAN +> must <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >NOT</I +></SPAN > be set to <TT CLASS="PARAMETER" ><I @@ -5168,10 +5194,12 @@ CLASS="PARAMETER" the UNIX user name to create.</P ><P >When the Windows user attempts to access the Samba server, - at login (session setup in the SMB protocol) time, <A -HREF="smbd.8.html" -TARGET="_top" -> smbd</A + at login (session setup in the SMB protocol) time, <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbd</SPAN +>(8)</SPAN > contacts the <TT CLASS="PARAMETER" ><I @@ -5194,9 +5222,12 @@ CLASS="PARAMETER" CLASS="COMMAND" >smbd</B > will - call the specified script <I + call the specified script <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >AS ROOT</I +></SPAN >, expanding any <TT CLASS="PARAMETER" @@ -5243,7 +5274,7 @@ CLASS="PARAMETER" ><P >Default: <B CLASS="COMMAND" ->add user script = <empty string> +>add user script = <empty string> </B ></P ><P @@ -5257,17 +5288,22 @@ CLASS="COMMAND" ><A NAME="ADDGROUPSCRIPT" ></A ->add group script (G)</DT +>>add group script (G)</DT ><DD ><P >This is the full pathname to a script that will - be run <I + be run <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >AS ROOT</I -> by <A -HREF="smbd.8.html" -TARGET="_top" ->smbd(8)</A +></SPAN +> by <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbd</SPAN +>(8)</SPAN > when a new group is requested. It will expand any <TT @@ -5288,7 +5324,7 @@ CLASS="PARAMETER" ><A NAME="ADMINUSERS" ></A ->admin users (S)</DT +>>admin users (S)</DT ><DD ><P >This is a list of users who will be granted @@ -5299,9 +5335,12 @@ NAME="ADMINUSERS" this list will be able to do anything they like on the share, irrespective of file permissions.</P ><P ->Default: <I +>Default: <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >no admin users</I +></SPAN ></P ><P >Example: <B @@ -5313,32 +5352,36 @@ CLASS="COMMAND" ><A NAME="ADDUSERTOGROUPSCRIPT" ></A ->add user to group script (G)</DT +>>add user to group script (G)</DT ><DD ><P >Full path to the script that will be called when a user is added to a group using the Windows NT domain administration - tools. It will be run by <A -HREF="smbd.8.html" -TARGET="_top" ->smbd(8)</A -> - <I + tools. It will be run by <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbd</SPAN +>(8)</SPAN +> <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >AS ROOT</I ->. Any <TT +></SPAN +>. + Any <TT CLASS="PARAMETER" ><I >%g</I ></TT -> will be - replaced with the group name and any <TT +> will be replaced with the group name and + any <TT CLASS="PARAMETER" ><I >%u</I ></TT -> will - be replaced with the user name. +> will be replaced with the user name. </P ><P >Default: <B @@ -5355,7 +5398,7 @@ CLASS="COMMAND" ><A NAME="ALLOWHOSTS" ></A ->allow hosts (S)</DT +>>allow hosts (S)</DT ><DD ><P >Synonym for <A @@ -5372,7 +5415,7 @@ CLASS="PARAMETER" ><A NAME="ALGORITHMICRIDBASE" ></A ->algorithmic rid base (G)</DT +>>algorithmic rid base (G)</DT ><DD ><P >This determines how Samba will use its @@ -5404,7 +5447,7 @@ CLASS="COMMAND" ><A NAME="ALLOWTRUSTEDDOMAINS" ></A ->allow trusted domains (G)</DT +>>allow trusted domains (G)</DT ><DD ><P >This option only takes effect when the <A @@ -5450,19 +5493,16 @@ CLASS="COMMAND" ><A NAME="ANNOUNCEAS" ></A ->announce as (G)</DT +>>announce as (G)</DT ><DD ><P ->This specifies what type of server - <A -HREF="nmbd.8.html" -TARGET="_top" -><B -CLASS="COMMAND" ->nmbd</B -></A -> - will announce itself as, to a network neighborhood browse +>This specifies what type of server <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>nmbd</SPAN +>(8)</SPAN +> will announce itself as, to a network neighborhood browse list. By default this is set to Windows NT. The valid options are : "NT Server" (which can also be written as "NT"), "NT Workstation", "Win95" or "WfW" meaning Windows NT Server, @@ -5486,7 +5526,7 @@ CLASS="COMMAND" ><A NAME="ANNOUNCEVERSION" ></A ->announce version (G)</DT +>>announce version (G)</DT ><DD ><P >This specifies the major and minor version numbers @@ -5508,7 +5548,7 @@ CLASS="COMMAND" ><A NAME="AUTOSERVICES" ></A ->auto services (G)</DT +>>auto services (G)</DT ><DD ><P >This is a synonym for the <A @@ -5525,7 +5565,7 @@ CLASS="PARAMETER" ><A NAME="AUTHMETHODS" ></A ->auth methods (G)</DT +>>auth methods (G)</DT ><DD ><P >This option allows the administrator to chose what @@ -5550,7 +5590,7 @@ CLASS="PARAMETER" ><P >Default: <B CLASS="COMMAND" ->auth methods = <empty string></B +>auth methods = <empty string></B ></P ><P >Example: <B @@ -5562,7 +5602,7 @@ CLASS="COMMAND" ><A NAME="AVAILABLE" ></A ->available (S)</DT +>>available (S)</DT ><DD ><P >This parameter lets you "turn off" a service. If @@ -5571,9 +5611,12 @@ CLASS="PARAMETER" ><I >available = no</I ></TT ->, then <I +>, then <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >ALL</I +></SPAN > attempts to connect to the service will fail. Such failures are logged.</P @@ -5587,22 +5630,24 @@ CLASS="COMMAND" ><A NAME="BINDINTERFACESONLY" ></A ->bind interfaces only (G)</DT +>>bind interfaces only (G)</DT ><DD ><P >This global parameter allows the Samba admin to limit what interfaces on a machine will serve SMB requests. It - affects file service <A -HREF="smbd.8.html" -TARGET="_top" ->smbd(8)</A -> and - name service <A -HREF="nmbd.8.html" -TARGET="_top" ->nmbd(8)</A -> in slightly - different ways.</P + affects file service <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbd</SPAN +>(8)</SPAN +> and name service <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>nmbd</SPAN +>(8)</SPAN +> in a slightly different ways.</P ><P >For name service it causes <B CLASS="COMMAND" @@ -5657,12 +5702,14 @@ CLASS="COMMAND" >nmbd</B >.</P ><P ->For file service it causes <A -HREF="smbd.8.html" -TARGET="_top" ->smbd(8)</A -> - to bind only to the interface list given in the <A +>For file service it causes <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbd</SPAN +>(8)</SPAN +> to bind only to the interface list + given in the <A HREF="#INTERFACES" > interfaces</A > parameter. This restricts the networks that @@ -5680,40 +5727,42 @@ CLASS="PARAMETER" >bind interfaces only</I ></TT > is set then - unless the network address <I + unless the network address <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >127.0.0.1</I +></SPAN > is added to the <TT CLASS="PARAMETER" ><I >interfaces</I ></TT -> parameter list <A -HREF="smbpasswd.8.html" -TARGET="_top" -><B -CLASS="COMMAND" ->smbpasswd(8)</B -></A -> - and <A -HREF="swat.8.html" -TARGET="_top" -><B -CLASS="COMMAND" ->swat(8)</B -></A -> may - not work as expected due to the reasons covered below.</P +> parameter list <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbpasswd</SPAN +>(8)</SPAN +> and <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>swat</SPAN +>(8)</SPAN +> may not work as expected due to the reasons covered below.</P ><P >To change a users SMB password, the <B CLASS="COMMAND" >smbpasswd</B > - by default connects to the <I + by default connects to the <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >localhost - 127.0.0.1</I +></SPAN > address as an SMB client to issue the password change request. If <TT @@ -5722,9 +5771,12 @@ CLASS="PARAMETER" >bind interfaces only</I ></TT > is set then unless the - network address <I + network address <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >127.0.0.1</I +></SPAN > is added to the <TT CLASS="PARAMETER" @@ -5739,10 +5791,13 @@ CLASS="COMMAND" CLASS="COMMAND" >smbpasswd</B > can be forced to use the primary IP interface - of the local host by using its <A -HREF="smbpasswd.8.html#minusr" -TARGET="_top" -> <TT + of the local host by using its <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbpasswd</SPAN +>(8)</SPAN +> <TT CLASS="PARAMETER" ><I >-r <TT @@ -5753,8 +5808,7 @@ CLASS="REPLACEABLE" ></I ></TT > - </A -> parameter, with <TT + parameter, with <TT CLASS="REPLACEABLE" ><I >remote machine</I @@ -5773,13 +5827,19 @@ CLASS="COMMAND" CLASS="COMMAND" >nmbd</B > at the address - <I + <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >127.0.0.1</I +></SPAN > to determine if they are running. - Not adding <I + Not adding <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >127.0.0.1</I +></SPAN > will cause <B CLASS="COMMAND" > smbd</B @@ -5808,13 +5868,16 @@ CLASS="COMMAND" ><A NAME="BLOCKINGLOCKS" ></A ->blocking locks (S)</DT +>>blocking locks (S)</DT ><DD ><P ->This parameter controls the behavior of <A -HREF="smbd.8.html" -TARGET="_top" ->smbd(8)</A +>This parameter controls the behavior + of <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbd</SPAN +>(8)</SPAN > when given a request by a client to obtain a byte range lock on a region of an open file, and the request has a time limit associated with it.</P @@ -5841,14 +5904,15 @@ CLASS="COMMAND" ><A NAME="BLOCKSIZE" ></A ->block size (S)</DT +>>block size (S)</DT ><DD ><P ->This parameter controls the behavior of - <A -HREF="smbd.8.html" -TARGET="_top" ->smbd(8)</A +>This parameter controls the behavior of <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbd</SPAN +>(8)</SPAN > when reporting disk free sizes. By default, this reports a disk block size of 1024 bytes. </P @@ -5863,22 +5927,12 @@ TARGET="_top" ><P >Changing this option does not change the disk free reporting size, just the block size unit reported to the client.</P -><P ->Default: <B -CLASS="COMMAND" ->block size = 1024</B -></P -><P ->Example: <B -CLASS="COMMAND" ->block size = 65536</B -></P ></DD ><DT ><A NAME="BROWSABLE" ></A ->browsable (S)</DT +>>browsable (S)</DT ><DD ><P >See the <A @@ -5895,16 +5949,15 @@ CLASS="PARAMETER" ><A NAME="BROWSELIST" ></A ->browse list (G)</DT +>>browse list (G)</DT ><DD ><P ->This controls whether <A -HREF="smbd.8.html" -TARGET="_top" -> <B -CLASS="COMMAND" ->smbd(8)</B -></A +>This controls whether <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbd</SPAN +>(8)</SPAN > will serve a browse list to a client doing a <B CLASS="COMMAND" @@ -5925,7 +5978,7 @@ CLASS="COMMAND" ><A NAME="BROWSEABLE" ></A ->browseable (S)</DT +>>browseable (S)</DT ><DD ><P >This controls whether this share is seen in @@ -5940,11 +5993,11 @@ CLASS="COMMAND" ><A NAME="CASESENSITIVE" ></A ->case sensitive (S)</DT +>>case sensitive (S)</DT ><DD ><P >See the discussion in the section <A -HREF="#AEN205" +HREF="#AEN206" >NAME MANGLING</A >.</P ><P @@ -5957,7 +6010,7 @@ CLASS="COMMAND" ><A NAME="CASESIGNAMES" ></A ->casesignames (S)</DT +>>casesignames (S)</DT ><DD ><P >Synonym for <A @@ -5970,19 +6023,18 @@ HREF="#CASESENSITIVE" ><A NAME="CHANGENOTIFYTIMEOUT" ></A ->change notify timeout (G)</DT +>>change notify timeout (G)</DT ><DD ><P >This SMB allows a client to tell a server to "watch" a particular directory for any changes and only reply to the SMB request when a change has occurred. Such constant scanning of - a directory is expensive under UNIX, hence an <A -HREF="smbd.8.html" -TARGET="_top" -> <B -CLASS="COMMAND" ->smbd(8)</B -></A + a directory is expensive under UNIX, hence an <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbd</SPAN +>(8)</SPAN > daemon only performs such a scan on each requested directory once every <TT CLASS="PARAMETER" @@ -6008,7 +6060,7 @@ CLASS="COMMAND" ><A NAME="CHANGESHARECOMMAND" ></A ->change share command (G)</DT +>>change share command (G)</DT ><DD ><P >Samba 2.2.0 introduced the ability to dynamically @@ -6125,9 +6177,12 @@ CLASS="PARAMETER" >. </P ><P ->Default: <I +>Default: <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >none</I +></SPAN ></P ><P >Example: <B @@ -6139,7 +6194,7 @@ CLASS="COMMAND" ><A NAME="COMMENT" ></A ->comment (S)</DT +>>comment (S)</DT ><DD ><P >This is a text field that is seen next to a share @@ -6161,9 +6216,12 @@ CLASS="PARAMETER" ></A > parameter.</P ><P ->Default: <I +>Default: <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >No comment string</I +></SPAN ></P ><P >Example: <B @@ -6175,7 +6233,7 @@ CLASS="COMMAND" ><A NAME="CONFIGFILE" ></A ->config file (G)</DT +>>config file (G)</DT ><DD ><P >This allows you to override the config file @@ -6207,7 +6265,7 @@ CLASS="COMMAND" ><A NAME="COPY" ></A ->copy (S)</DT +>>copy (S)</DT ><DD ><P >This parameter allows you to "clone" service @@ -6220,9 +6278,12 @@ NAME="COPY" copied must occur earlier in the configuration file than the service doing the copying.</P ><P ->Default: <I +>Default: <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >no value</I +></SPAN ></P ><P >Example: <B @@ -6234,7 +6295,7 @@ CLASS="COMMAND" ><A NAME="CREATEMASK" ></A ->create mask (S)</DT +>>create mask (S)</DT ><DD ><P >A synonym for this parameter is @@ -6253,9 +6314,12 @@ CLASS="PARAMETER" calculated according to the mapping from DOS modes to UNIX permissions, and the resulting UNIX mode is then bit-wise 'AND'ed with this parameter. This parameter may be thought of as a bit-wise - MASK for the UNIX modes of a file. Any bit <I + MASK for the UNIX modes of a file. Any bit <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >not</I +></SPAN > set here will be removed from the modes set on a file when it is created.</P @@ -6342,7 +6406,7 @@ CLASS="COMMAND" ><A NAME="CREATEMODE" ></A ->create mode (S)</DT +>>create mode (S)</DT ><DD ><P >This is a synonym for <A @@ -6359,13 +6423,16 @@ CLASS="PARAMETER" ><A NAME="CSCPOLICY" ></A ->csc policy (S)</DT +>>csc policy (S)</DT ><DD ><P ->This stands for <I +>This stands for <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >client-side caching policy</I +></SPAN >, and specifies how clients capable of offline caching will cache the files in the share. The valid values are: manual, documents, programs, disable.</P @@ -6394,7 +6461,7 @@ CLASS="COMMAND" ><A NAME="DEADTIME" ></A ->deadtime (G)</DT +>>deadtime (G)</DT ><DD ><P >The value of the parameter (a decimal integer) @@ -6429,7 +6496,7 @@ CLASS="COMMAND" ><A NAME="DEBUGHIRESTIMESTAMP" ></A ->debug hires timestamp (G)</DT +>>debug hires timestamp (G)</DT ><DD ><P >Sometimes the timestamps in the log messages @@ -6457,7 +6524,7 @@ CLASS="COMMAND" ><A NAME="DEBUGPID" ></A ->debug pid (G)</DT +>>debug pid (G)</DT ><DD ><P >When using only one log file for more then one @@ -6489,7 +6556,7 @@ CLASS="COMMAND" ><A NAME="DEBUGTIMESTAMP" ></A ->debug timestamp (G)</DT +>>debug timestamp (G)</DT ><DD ><P >Samba debug log messages are timestamped @@ -6514,7 +6581,7 @@ CLASS="COMMAND" ><A NAME="DEBUGUID" ></A ->debug uid (G)</DT +>>debug uid (G)</DT ><DD ><P >Samba is sometimes run as root and sometime @@ -6542,7 +6609,7 @@ CLASS="COMMAND" ><A NAME="DEBUGLEVEL" ></A ->debuglevel (G)</DT +>>debuglevel (G)</DT ><DD ><P >Synonym for <A @@ -6559,7 +6626,7 @@ CLASS="PARAMETER" ><A NAME="DEFAULT" ></A ->default (G)</DT +>>default (G)</DT ><DD ><P >A synonym for <A @@ -6576,11 +6643,11 @@ CLASS="PARAMETER" ><A NAME="DEFAULTCASE" ></A ->default case (S)</DT +>>default case (S)</DT ><DD ><P >See the section on <A -HREF="#AEN205" +HREF="#AEN206" > NAME MANGLING</A >. Also note the <A HREF="#SHORTPRESERVECASE" @@ -6601,7 +6668,7 @@ CLASS="COMMAND" ><A NAME="DEFAULTDEVMODE" ></A ->default devmode (S)</DT +>>default devmode (S)</DT ><DD ><P >This parameter is only applicable to <A @@ -6652,14 +6719,17 @@ CLASS="COMMAND" ><A NAME="DEFAULTSERVICE" ></A ->default service (G)</DT +>>default service (G)</DT ><DD ><P >This parameter specifies the name of a service which will be connected to if the service actually requested cannot - be found. Note that the square brackets are <I + be found. Note that the square brackets are <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >NOT</I +></SPAN > given in the parameter value (see example below).</P ><P @@ -6701,53 +6771,50 @@ CLASS="PARAMETER" ><P >Example:</P ><P -><TABLE -BORDER="0" -BGCOLOR="#E0E0E0" -WIDTH="90%" -><TR -><TD ><PRE CLASS="PROGRAMLISTING" >[global] default service = pub [pub] - path = /%S - </PRE -></TD -></TR -></TABLE + path = /%S</PRE ></P ></DD ><DT ><A NAME="DELETEGROUPSCRIPT" ></A ->delete group script (G)</DT +>>delete group script (G)</DT ><DD ><P >This is the full pathname to a script that will - be run <I + be run <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >AS ROOT</I -> by <A -HREF="smbd.8.html" -TARGET="_top" ->smbd(8)</A -> when a group is requested to be deleted. It will expand any <TT +></SPAN +> <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbd</SPAN +>(8)</SPAN +> when a group is requested to be deleted. + It will expand any <TT CLASS="PARAMETER" ><I >%g</I ></TT -> to the group name passed. This script is only useful for installations using the Windows NT domain administration tools. +> to the group name passed. + This script is only useful for installations using the Windows NT domain administration tools. </P ></DD ><DT ><A NAME="DELETEPRINTERCOMMAND" ></A ->deleteprinter command (G)</DT +>>deleteprinter command (G)</DT ><DD ><P >With the introduction of MS-RPC based printer @@ -6829,9 +6896,12 @@ CLASS="PARAMETER" ></A ></P ><P ->Default: <I +>Default: <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >none</I +></SPAN ></P ><P >Example: <B @@ -6844,7 +6914,7 @@ CLASS="COMMAND" ><A NAME="DELETEREADONLY" ></A ->delete readonly (S)</DT +>>delete readonly (S)</DT ><DD ><P >This parameter allows readonly files to be deleted. @@ -6863,7 +6933,7 @@ CLASS="COMMAND" ><A NAME="DELETESHARECOMMAND" ></A ->delete share command (G)</DT +>>delete share command (G)</DT ><DD ><P >Samba 2.2.0 introduced the ability to dynamically @@ -6967,9 +7037,12 @@ CLASS="PARAMETER" >. </P ><P ->Default: <I +>Default: <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >none</I +></SPAN ></P ><P >Example: <B @@ -6981,19 +7054,18 @@ CLASS="COMMAND" ><A NAME="DELETEUSERSCRIPT" ></A ->delete user script (G)</DT +>>delete user script (G)</DT ><DD ><P >This is the full pathname to a script that will - be run by <A -HREF="smbd.8.html" -TARGET="_top" -><B -CLASS="COMMAND" ->smbd(8)</B -></A -> - when managing user's with remote RPC (NT) tools. + be run by <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbd</SPAN +>(8)</SPAN +> when managing users + with remote RPC (NT) tools. </P ><P >This script is called when a remote client removes a user @@ -7009,7 +7081,7 @@ CLASS="COMMAND" ><P >Default: <B CLASS="COMMAND" ->delete user script = <empty string> +>delete user script = <empty string> </B ></P ><P @@ -7023,32 +7095,36 @@ CLASS="COMMAND" ><A NAME="DELETEUSERFROMGROUPSCRIPT" ></A ->delete user from group script (G)</DT +>>delete user from group script (G)</DT ><DD ><P >Full path to the script that will be called when a user is removed from a group using the Windows NT domain administration - tools. It will be run by <A -HREF="smbd.8.html" -TARGET="_top" ->smbd(8)</A -> - <I + tools. It will be run by <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbd</SPAN +>(8)</SPAN +> <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >AS ROOT</I ->. Any <TT +></SPAN +>. + Any <TT CLASS="PARAMETER" ><I >%g</I ></TT -> will be - replaced with the group name and any <TT +> will be replaced with the group name and + any <TT CLASS="PARAMETER" ><I >%u</I ></TT -> will - be replaced with the user name. +> will be replaced with the user name. </P ><P >Default: <B @@ -7065,7 +7141,7 @@ CLASS="COMMAND" ><A NAME="DELETEVETOFILES" ></A ->delete veto files (S)</DT +>>delete veto files (S)</DT ><DD ><P >This option is used when Samba is attempting to @@ -7126,7 +7202,7 @@ CLASS="COMMAND" ><A NAME="DENYHOSTS" ></A ->deny hosts (S)</DT +>>deny hosts (S)</DT ><DD ><P >Synonym for <A @@ -7144,7 +7220,7 @@ CLASS="PARAMETER" ><A NAME="DFREECOMMAND" ></A ->dfree command (G)</DT +>>dfree command (G)</DT ><DD ><P >The <TT @@ -7175,17 +7251,23 @@ CLASS="FILENAME" third return value can give the block size in bytes. The default blocksize is 1024 bytes.</P ><P ->Note: Your script should <I +>Note: Your script should <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >NOT</I +></SPAN > be setuid or setgid and should be owned by (and writeable only by) root!</P ><P ->Default: <I +>Default: <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >By default internal routines for determining the disk capacity and remaining space will be used. </I +></SPAN ></P ><P >Example: <B @@ -7196,40 +7278,20 @@ CLASS="COMMAND" ><P >Where the script dfree (which must be made executable) could be:</P ><P -><TABLE -BORDER="0" -BGCOLOR="#E0E0E0" -WIDTH="90%" -><TR -><TD ><PRE CLASS="PROGRAMLISTING" > - #!/bin/sh - df $1 | tail -1 | awk '{print $2" "$4}' - </PRE -></TD -></TR -></TABLE +#!/bin/sh +df $1 | tail -1 | awk '{print $2" "$4}'</PRE ></P ><P >or perhaps (on Sys V based systems):</P ><P -><TABLE -BORDER="0" -BGCOLOR="#E0E0E0" -WIDTH="90%" -><TR -><TD ><PRE CLASS="PROGRAMLISTING" > - #!/bin/sh - /usr/bin/df -k $1 | tail -1 | awk '{print $3" "$5}' - </PRE -></TD -></TR -></TABLE +#!/bin/sh +/usr/bin/df -k $1 | tail -1 | awk '{print $3" "$5}'</PRE ></P ><P >Note that you may have to replace the command names @@ -7239,7 +7301,7 @@ CLASS="PROGRAMLISTING" ><A NAME="DIRECTORY" ></A ->directory (S)</DT +>>directory (S)</DT ><DD ><P >Synonym for <A @@ -7257,7 +7319,7 @@ CLASS="PARAMETER" ><A NAME="DIRECTORYMASK" ></A ->directory mask (S)</DT +>>directory mask (S)</DT ><DD ><P >This parameter is the octal modes which are @@ -7268,9 +7330,12 @@ NAME="DIRECTORYMASK" calculated according to the mapping from DOS modes to UNIX permissions, and the resulting UNIX mode is then bit-wise 'AND'ed with this parameter. This parameter may be thought of as a bit-wise MASK for - the UNIX modes of a directory. Any bit <I + the UNIX modes of a directory. Any bit <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >not</I +></SPAN > set here will be removed from the modes set on a directory when it is created.</P @@ -7361,7 +7426,7 @@ CLASS="COMMAND" ><A NAME="DIRECTORYMODE" ></A ->directory mode (S)</DT +>>directory mode (S)</DT ><DD ><P >Synonym for <A @@ -7378,7 +7443,7 @@ CLASS="PARAMETER" ><A NAME="DIRECTORYSECURITYMASK" ></A ->directory security mask (S)</DT +>>directory security mask (S)</DT ><DD ><P >This parameter controls what UNIX permission bits @@ -7396,9 +7461,12 @@ NAME="DIRECTORYSECURITYMASK" meaning a user is allowed to modify all the user/group/world permissions on a directory.</P ><P +><SPAN +CLASS="emphasis" ><I CLASS="EMPHASIS" >Note</I +></SPAN > that users who can access the Samba server through other means can easily bypass this restriction, so it is primarily useful for standalone "appliance" systems. @@ -7450,7 +7518,7 @@ CLASS="COMMAND" ><A NAME="DISABLENETBIOS" ></A ->disable netbios (G)</DT +>>disable netbios (G)</DT ><DD ><P >Enabling this parameter will disable netbios support @@ -7475,7 +7543,7 @@ CLASS="COMMAND" ><A NAME="DISABLESPOOLSS" ></A ->disable spoolss (G)</DT +>>disable spoolss (G)</DT ><DD ><P >Enabling this parameter will disable Samba's support @@ -7487,9 +7555,12 @@ NAME="DISABLESPOOLSS" Wizard or by using the NT printer properties dialog window. It will also disable the capability of Windows NT/2000 clients to download print drivers from the Samba host upon demand. - <I + <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >Be very careful about enabling this parameter.</I +></SPAN > </P ><P @@ -7508,7 +7579,7 @@ CLASS="COMMAND" ><A NAME="DISPLAYCHARSET" ></A ->display charset (G)</DT +>>display charset (G)</DT ><DD ><P >Specifies the charset that samba will use @@ -7533,18 +7604,19 @@ CLASS="COMMAND" ><A NAME="DNSPROXY" ></A ->dns proxy (G)</DT +>>dns proxy (G)</DT ><DD ><P ->Specifies that <A -HREF="nmbd.8.html" -TARGET="_top" ->nmbd(8)</A -> - when acting as a WINS server and finding that a NetBIOS name has not - been registered, should treat the NetBIOS name word-for-word as a DNS - name and do a lookup with the DNS server for that name on behalf of - the name-querying client.</P +>Specifies that <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>nmbd</SPAN +>(8)</SPAN +> when acting as a WINS server and + finding that a NetBIOS name has not been registered, should treat the + NetBIOS name word-for-word as a DNS name and do a lookup with the DNS server + for that name on behalf of the name-querying client.</P ><P >Note that the maximum length for a NetBIOS name is 15 characters, so the DNS name (or DNS alias) can likewise only be @@ -7576,7 +7648,7 @@ CLASS="COMMAND" ><A NAME="DOMAINLOGONS" ></A ->domain logons (G)</DT +>>domain logons (G)</DT ><DD ><P >If set to <TT @@ -7609,16 +7681,15 @@ CLASS="COMMAND" ><A NAME="DOMAINMASTER" ></A ->domain master (G)</DT +>>domain master (G)</DT ><DD ><P ->Tell <A -HREF="nmbd.8.html" -TARGET="_top" -><B -CLASS="COMMAND" -> nmbd(8)</B -></A +>Tell <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbd</SPAN +>(8)</SPAN > to enable WAN-wide browse list collation. Setting this option causes <B CLASS="COMMAND" @@ -7644,18 +7715,16 @@ CLASS="PARAMETER" CLASS="COMMAND" >nmbd</B > their local browse lists, - and then ask <A -HREF="smbd.8.html" -TARGET="_top" -><B -CLASS="COMMAND" ->smbd(8)</B -></A -> - for a complete copy of the browse list for the whole wide area - network. Browser clients will then contact their local master browser, - and will receive the domain-wide browse list, instead of just the list - for their broadcast-isolated subnet.</P + and then ask <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbd</SPAN +>(8)</SPAN +> for a complete copy of the browse + list for the whole wide area network. Browser clients will then contact + their local master browser, and will receive the domain-wide browse list, + instead of just the list for their broadcast-isolated subnet.</P ><P >Note that Windows NT Primary Domain Controllers expect to be able to claim this <TT @@ -7721,7 +7790,7 @@ CLASS="COMMAND" ><A NAME="DONTDESCEND" ></A ->dont descend (S)</DT +>>dont descend (S)</DT ><DD ><P >There are certain directories on some systems @@ -7743,10 +7812,13 @@ CLASS="FILENAME" >. Experimentation is the best policy :-) </P ><P ->Default: <I +>Default: <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >none (i.e., all directories are OK to descend)</I +></SPAN ></P ><P >Example: <B @@ -7758,7 +7830,7 @@ CLASS="COMMAND" ><A NAME="DOSCHARSET" ></A ->dos charset (G)</DT +>>dos charset (G)</DT ><DD ><P >DOS SMB clients assume the server has @@ -7768,11 +7840,12 @@ NAME="DOSCHARSET" ><P >The default depends on which charsets you have instaled. Samba tries to use charset 850 but falls back to ASCII in - case it is not available. Run <A -HREF="testparm.1.html" -TARGET="_top" ->testparm(1) - </A + case it is not available. Run <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>testparm</SPAN +>(1)</SPAN > to check the default on your system. </P ></DD @@ -7780,7 +7853,7 @@ TARGET="_top" ><A NAME="DOSFILEMODE" ></A ->dos filemode (S)</DT +>>dos filemode (S)</DT ><DD ><P > The default behavior in Samba is to provide @@ -7803,21 +7876,19 @@ CLASS="COMMAND" ><A NAME="DOSFILETIMERESOLUTION" ></A ->dos filetime resolution (S)</DT +>>dos filetime resolution (S)</DT ><DD ><P >Under the DOS and Windows FAT filesystem, the finest granularity on time resolution is two seconds. Setting this parameter for a share causes Samba to round the reported time down to the nearest two second boundary when a query call that requires one second - resolution is made to <A -HREF="smbd.8.html" -TARGET="_top" -><B -CLASS="COMMAND" ->smbd(8)</B -> - </A + resolution is made to <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbd</SPAN +>(8)</SPAN >.</P ><P >This option is mainly used as a compatibility option for Visual @@ -7840,7 +7911,7 @@ CLASS="COMMAND" ><A NAME="DOSFILETIMES" ></A ->dos filetimes (S)</DT +>>dos filetimes (S)</DT ><DD ><P >Under DOS and Windows, if a user can write to a @@ -7854,10 +7925,12 @@ CLASS="COMMAND" on behalf of is not the file owner. Setting this option to <TT CLASS="CONSTANT" > yes</TT -> allows DOS semantics and <A -HREF="smbd.8.html" -TARGET="_top" ->smbd</A +> allows DOS semantics and <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbd</SPAN +>(8)</SPAN > will change the file timestamp as DOS requires.</P ><P @@ -7870,7 +7943,7 @@ CLASS="COMMAND" ><A NAME="ENCRYPTPASSWORDS" ></A ->encrypt passwords (G)</DT +>>encrypt passwords (G)</DT ><DD ><P >This boolean controls whether encrypted passwords @@ -7884,29 +7957,25 @@ CLASS="FILENAME" > shipped with the source code.</P ><P >In order for encrypted passwords to work correctly - <A -HREF="smbd.8.html" -TARGET="_top" -><B -CLASS="COMMAND" ->smbd(8)</B -></A + <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbd</SPAN +>(8)</SPAN > must either - have access to a local <A -HREF="smbpasswd.5.html" -TARGET="_top" -><TT -CLASS="FILENAME" ->smbpasswd(5) - </TT -></A -> file (see the <A -HREF="smbpasswd.8.html" -TARGET="_top" -><B -CLASS="COMMAND" -> smbpasswd(8)</B -></A + have access to a local <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbpasswd</SPAN +>(5)</SPAN +> file (see the <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbpasswd</SPAN +>(8)</SPAN > program for information on how to set up and maintain this file), or set the <A HREF="#SECURITY" @@ -7927,7 +7996,7 @@ CLASS="COMMAND" ><A NAME="ENHANCEDBROWSING" ></A ->enhanced browsing (G)</DT +>>enhanced browsing (G)</DT ><DD ><P >This option enables a couple of enhancements to @@ -7958,7 +8027,7 @@ CLASS="COMMAND" ><A NAME="ENUMPORTSCOMMAND" ></A ->enumports command (G)</DT +>>enumports command (G)</DT ><DD ><P >The concept of a "port" is fairly foreign @@ -7990,9 +8059,12 @@ CLASS="PARAMETER" to standard output. This listing will then be used in response to the level 1 and 2 EnumPorts() RPC.</P ><P ->Default: <I +>Default: <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >no enumports command</I +></SPAN ></P ><P >Example: <B @@ -8005,7 +8077,7 @@ CLASS="COMMAND" ><A NAME="EXEC" ></A ->exec (S)</DT +>>exec (S)</DT ><DD ><P >This is a synonym for <A @@ -8022,7 +8094,7 @@ CLASS="PARAMETER" ><A NAME="FAKEDIRECTORYCREATETIMES" ></A ->fake directory create times (S)</DT +>>fake directory create times (S)</DT ><DD ><P >NTFS and Windows VFAT file systems keep a create @@ -8060,7 +8132,7 @@ CLASS="COMMAND" ><A NAME="FAKEOPLOCKS" ></A ->fake oplocks (S)</DT +>>fake oplocks (S)</DT ><DD ><P >Oplocks are the way that SMB clients get permission @@ -8113,19 +8185,18 @@ CLASS="COMMAND" ><A NAME="FOLLOWSYMLINKS" ></A ->follow symlinks (S)</DT +>>follow symlinks (S)</DT ><DD ><P >This parameter allows the Samba administrator - to stop <A -HREF="smbd.8.html" -TARGET="_top" -><B -CLASS="COMMAND" ->smbd(8)</B -></A -> - from following symbolic links in a particular share. Setting this + to stop <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbd</SPAN +>(8)</SPAN +> from following symbolic + links in a particular share. Setting this parameter to <TT CLASS="CONSTANT" >no</TT @@ -8154,13 +8225,16 @@ CLASS="COMMAND" ><A NAME="FORCECREATEMODE" ></A ->force create mode (S)</DT +>>force create mode (S)</DT ><DD ><P >This parameter specifies a set of UNIX mode bit - permissions that will <I + permissions that will <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >always</I +></SPAN > be set on a file created by Samba. This is done by bitwise 'OR'ing these bits onto the mode bits of a file that is being created or having its @@ -8214,13 +8288,16 @@ CLASS="COMMAND" ><A NAME="FORCEDIRECTORYMODE" ></A ->force directory mode (S)</DT +>>force directory mode (S)</DT ><DD ><P >This parameter specifies a set of UNIX mode bit - permissions that will <I + permissions that will <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >always</I +></SPAN > be set on a directory created by Samba. This is done by bitwise 'OR'ing these bits onto the mode bits of a directory that is being created. The default for this @@ -8273,7 +8350,7 @@ CLASS="COMMAND" ><A NAME="FORCEDIRECTORYSECURITYMODE" ></A ->force directory security mode (S)</DT +>>force directory security mode (S)</DT ><DD ><P >This parameter controls what UNIX permission bits @@ -8290,9 +8367,12 @@ NAME="FORCEDIRECTORYSECURITYMODE" allows a user to modify all the user/group/world permissions on a directory without restrictions.</P ><P +><SPAN +CLASS="emphasis" ><I CLASS="EMPHASIS" >Note</I +></SPAN > that users who can access the Samba server through other means can easily bypass this restriction, so it is primarily useful for standalone "appliance" systems. @@ -8341,7 +8421,7 @@ CLASS="COMMAND" ><A NAME="FORCEGROUP" ></A ->force group (S)</DT +>>force group (S)</DT ><DD ><P >This specifies a UNIX group name that will be @@ -8402,9 +8482,12 @@ CLASS="PARAMETER" ></A >.</P ><P ->Default: <I +>Default: <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >no forced group</I +></SPAN ></P ><P >Example: <B @@ -8416,7 +8499,7 @@ CLASS="COMMAND" ><A NAME="FORCESECURITYMODE" ></A ->force security mode (S)</DT +>>force security mode (S)</DT ><DD ><P >This parameter controls what UNIX permission @@ -8434,9 +8517,12 @@ NAME="FORCESECURITYMODE" and allows a user to modify all the user/group/world permissions on a file, with no restrictions.</P ><P +><SPAN +CLASS="emphasis" ><I CLASS="EMPHASIS" >Note</I +></SPAN > that users who can access the Samba server through other means can easily bypass this restriction, so it is primarily useful for standalone "appliance" systems. @@ -8485,7 +8571,7 @@ CLASS="COMMAND" ><A NAME="FORCEUSER" ></A ->force user (S)</DT +>>force user (S)</DT ><DD ><P >This specifies a UNIX user name that will be @@ -8515,9 +8601,12 @@ CLASS="PARAMETER" ></A ></P ><P ->Default: <I +>Default: <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >no forced user</I +></SPAN ></P ><P >Example: <B @@ -8529,19 +8618,17 @@ CLASS="COMMAND" ><A NAME="FSTYPE" ></A ->fstype (S)</DT +>>fstype (S)</DT ><DD ><P >This parameter allows the administrator to configure the string that specifies the type of filesystem a share - is using that is reported by <A -HREF="smbd.8.html" -TARGET="_top" -><B -CLASS="COMMAND" ->smbd(8) - </B -></A + is using that is reported by <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbd</SPAN +>(8)</SPAN > when a client queries the filesystem type for a share. The default type is <TT CLASS="CONSTANT" @@ -8571,7 +8658,7 @@ CLASS="COMMAND" ><A NAME="GETWDCACHE" ></A ->getwd cache (G)</DT +>>getwd cache (G)</DT ><DD ><P >This is a tuning option. When this is enabled a @@ -8600,7 +8687,7 @@ CLASS="COMMAND" ><A NAME="GROUP" ></A ->group (S)</DT +>>group (S)</DT ><DD ><P >Synonym for <A @@ -8618,7 +8705,7 @@ CLASS="PARAMETER" ><A NAME="GUESTACCOUNT" ></A ->guest account (S)</DT +>>guest account (S)</DT ><DD ><P >This is a username which will be used for access @@ -8656,10 +8743,13 @@ CLASS="COMMAND" many parts of the system require this value to be constant for correct operation.</P ><P ->Default: <I +>Default: <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >specified at compile time, usually "nobody"</I +></SPAN ></P ><P >Example: <B @@ -8671,7 +8761,7 @@ CLASS="COMMAND" ><A NAME="GUESTOK" ></A ->guest ok (S)</DT +>>guest ok (S)</DT ><DD ><P >If this parameter is <TT @@ -8689,6 +8779,18 @@ CLASS="PARAMETER" ></A >.</P ><P +>This paramater nullifies the benifits of setting + <A +HREF="#RESTRICTANONYMOUS" +><TT +CLASS="PARAMETER" +><I +>restrict + anonymous</I +></TT +></A +> = 2</P +><P >See the section below on <A HREF="#SECURITY" ><TT @@ -8709,7 +8811,7 @@ CLASS="COMMAND" ><A NAME="GUESTONLY" ></A ->guest only (S)</DT +>>guest only (S)</DT ><DD ><P >If this parameter is <TT @@ -8747,7 +8849,7 @@ CLASS="COMMAND" ><A NAME="HIDEDOTFILES" ></A ->hide dot files (S)</DT +>>hide dot files (S)</DT ><DD ><P >This is a boolean parameter that controls whether @@ -8762,7 +8864,7 @@ CLASS="COMMAND" ><A NAME="HIDEFILES" ></A ->hide files(S)</DT +>>hide files(S)</DT ><DD ><P >This is a list of files or directories that are not @@ -8811,9 +8913,12 @@ CLASS="PARAMETER" ></A >.</P ><P ->Default: <I +>Default: <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >no file are hidden</I +></SPAN ></P ><P >Example: <B @@ -8835,7 +8940,7 @@ TARGET="_top" ><A NAME="HIDELOCALUSERS" ></A ->hide local users(G)</DT +>>hide local users(G)</DT ><DD ><P >This parameter toggles the hiding of local UNIX @@ -8850,7 +8955,7 @@ CLASS="COMMAND" ><A NAME="HIDEUNREADABLE" ></A ->hide unreadable (G)</DT +>>hide unreadable (G)</DT ><DD ><P >This parameter prevents clients from seeing the @@ -8865,7 +8970,7 @@ CLASS="COMMAND" ><A NAME="HIDEUNWRITEABLEFILES" ></A ->hide unwriteable files (G)</DT +>>hide unwriteable files (G)</DT ><DD ><P >This parameter prevents clients from seeing @@ -8882,7 +8987,7 @@ CLASS="COMMAND" ><A NAME="HIDESPECIALFILES" ></A ->hide special files (G)</DT +>>hide special files (G)</DT ><DD ><P >This parameter prevents clients from seeing @@ -8899,7 +9004,7 @@ CLASS="COMMAND" ><A NAME="HOMEDIRMAP" ></A ->homedir map (G)</DT +>>homedir map (G)</DT ><DD ><P >If<A @@ -8914,13 +9019,12 @@ CLASS="PARAMETER" > is <TT CLASS="CONSTANT" >yes</TT ->, and <A -HREF="smbd.8.html" -TARGET="_top" -><B -CLASS="COMMAND" ->smbd(8)</B -></A +>, and <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbd</SPAN +>(8)</SPAN > is also acting as a Win95/98 <TT CLASS="PARAMETER" @@ -8942,9 +9046,12 @@ CLASS="COMMAND" that copes with different map formats and also Amd (another automounter) maps.</P ><P +><SPAN +CLASS="emphasis" ><I CLASS="EMPHASIS" >NOTE :</I +></SPAN >A working NIS client is required on the system for this option to work.</P ><P @@ -8970,7 +9077,7 @@ CLASS="PARAMETER" ><P >Default: <B CLASS="COMMAND" ->homedir map = <empty string></B +>homedir map = <empty string></B ></P ><P >Example: <B @@ -8982,7 +9089,7 @@ CLASS="COMMAND" ><A NAME="HOSTMSDFS" ></A ->host msdfs (G)</DT +>>host msdfs (G)</DT ><DD ><P >This boolean parameter is only available @@ -9022,7 +9129,7 @@ CLASS="COMMAND" ><A NAME="HOSTNAMELOOKUPS" ></A ->hostname lookups (G)</DT +>>hostname lookups (G)</DT ><DD ><P >Specifies whether samba should use (expensive) @@ -9051,7 +9158,7 @@ CLASS="COMMAND" ><A NAME="HOSTSALLOW" ></A ->hosts allow (S)</DT +>>hosts allow (S)</DT ><DD ><P >A synonym for this parameter is <TT @@ -9096,9 +9203,12 @@ CLASS="PARAMETER" ><P >You can also specify hosts by network/netmask pairs and by netgroup names if your system supports netgroups. The - <I + <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >EXCEPT</I +></SPAN > keyword can also be used to limit a wildcard list. The following examples may provide some help:</P ><P @@ -9138,21 +9248,22 @@ CLASS="COMMAND" ><P >Note that access still requires suitable user-level passwords.</P ><P ->See <A -HREF="testparm.1.html" -TARGET="_top" -><B -CLASS="COMMAND" ->testparm(1)</B -> - </A -> for a way of testing your host access to see if it does - what you expect.</P +>See <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>testparm</SPAN +>(1)</SPAN +> for a way of testing your host access + to see if it does what you expect.</P ><P ->Default: <I +>Default: <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >none (i.e., all hosts permitted access) </I +></SPAN ></P ><P >Example: <B @@ -9165,7 +9276,7 @@ CLASS="COMMAND" ><A NAME="HOSTSDENY" ></A ->hosts deny (S)</DT +>>hosts deny (S)</DT ><DD ><P >The opposite of <TT @@ -9174,9 +9285,12 @@ CLASS="PARAMETER" >hosts allow</I ></TT > - - hosts listed here are <I + - hosts listed here are <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >NOT</I +></SPAN > permitted access to services unless the specific services have their own lists to override this one. Where the lists conflict, the <TT @@ -9187,10 +9301,13 @@ CLASS="PARAMETER" > list takes precedence.</P ><P ->Default: <I +>Default: <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >none (i.e., no hosts specifically excluded) </I +></SPAN ></P ><P >Example: <B @@ -9203,7 +9320,7 @@ CLASS="COMMAND" ><A NAME="HOSTSEQUIV" ></A ->hosts equiv (G)</DT +>>hosts equiv (G)</DT ><DD ><P >If this global parameter is a non-null string, @@ -9228,9 +9345,12 @@ CLASS="PARAMETER" > may be useful for NT clients which will not supply passwords to Samba.</P ><P +><SPAN +CLASS="emphasis" ><I CLASS="EMPHASIS" >NOTE :</I +></SPAN > The use of <TT CLASS="PARAMETER" ><I @@ -9247,15 +9367,21 @@ CLASS="PARAMETER" ></TT > option be only used if you really know what you are doing, or perhaps on a home network where you trust - your spouse and kids. And only if you <I + your spouse and kids. And only if you <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >really</I +></SPAN > trust them :-).</P ><P ->Default: <I +>Default: <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >no host equivalences</I +></SPAN ></P ><P >Example: <B @@ -9267,7 +9393,7 @@ CLASS="COMMAND" ><A NAME="INCLUDE" ></A ->include (G)</DT +>>include (G)</DT ><DD ><P >This allows you to include one config file @@ -9293,9 +9419,12 @@ CLASS="PARAMETER" >. </P ><P ->Default: <I +>Default: <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >no file included</I +></SPAN ></P ><P >Example: <B @@ -9308,7 +9437,7 @@ CLASS="COMMAND" ><A NAME="INHERITACLS" ></A ->inherit acls (S)</DT +>>inherit acls (S)</DT ><DD ><P >This parameter can be used to ensure @@ -9330,7 +9459,7 @@ CLASS="COMMAND" ><A NAME="INHERITPERMISSIONS" ></A ->inherit permissions (S)</DT +>>inherit permissions (S)</DT ><DD ><P >The permissions on new files and directories @@ -9405,9 +9534,12 @@ CLASS="PARAMETER" </A > as usual.</P ><P ->Note that the setuid bit is <I +>Note that the setuid bit is <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >never</I +></SPAN > set via inheritance (the code explicitly prohibits this).</P ><P @@ -9460,7 +9592,7 @@ CLASS="COMMAND" ><A NAME="INTERFACES" ></A ->interfaces (G)</DT +>>interfaces (G)</DT ><DD ><P >This option allows you to override the default @@ -9527,23 +9659,29 @@ CLASS="PARAMETER" ></A >.</P ><P ->Default: <I +>Default: <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >all active interfaces except 127.0.0.1 that are broadcast capable</I +></SPAN ></P ></DD ><DT ><A NAME="INVALIDUSERS" ></A ->invalid users (S)</DT +>>invalid users (S)</DT ><DD ><P >This is a list of users that should not be allowed - to login to this service. This is really a <I + to login to this service. This is really a <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >paranoid</I +></SPAN > check to absolutely ensure an improper setting does not breach your security.</P @@ -9554,20 +9692,20 @@ CLASS="EMPHASIS" ><P >A name starting with '+' is interpreted only by looking in the UNIX group database. A name starting with - '&' is interpreted only by looking in the NIS netgroup database + '&' is interpreted only by looking in the NIS netgroup database (this requires NIS to be working on your system). The characters - '+' and '&' may be used at the start of the name in either order + '+' and '&' may be used at the start of the name in either order so the value <TT CLASS="PARAMETER" ><I ->+&group</I +>+&group</I ></TT > means check the UNIX group database, followed by the NIS netgroup database, and the value <TT CLASS="PARAMETER" ><I ->&+group</I +>&+group</I ></TT > means check the NIS netgroup database, followed by the UNIX group database (the @@ -9592,9 +9730,12 @@ CLASS="PARAMETER" ></A >.</P ><P ->Default: <I +>Default: <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >no invalid users</I +></SPAN ></P ><P >Example: <B @@ -9607,7 +9748,7 @@ CLASS="COMMAND" ><A NAME="KEEPALIVE" ></A ->keepalive (G)</DT +>>keepalive (G)</DT ><DD ><P >The value of the parameter (an integer) represents @@ -9647,7 +9788,7 @@ CLASS="COMMAND" ><A NAME="KERNELOPLOCKS" ></A ->kernel oplocks (G)</DT +>>kernel oplocks (G)</DT ><DD ><P >For UNIXes that support kernel based <A @@ -9669,20 +9810,21 @@ CLASS="PARAMETER" </I ></TT > to be broken whenever a local UNIX process or NFS operation - accesses a file that <A -HREF="smbd.8.html" -TARGET="_top" -><B -CLASS="COMMAND" ->smbd(8)</B -> - </A -> has oplocked. This allows complete data consistency between - SMB/CIFS, NFS and local file access (and is a <I + accesses a file that <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbd</SPAN +>(8)</SPAN +> has oplocked. This allows complete + data consistency between SMB/CIFS, NFS and local file access (and is + a <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >very</I -> - cool feature :-).</P +></SPAN +> cool feature :-).</P ><P >This parameter defaults to <TT CLASS="CONSTANT" @@ -9720,18 +9862,19 @@ CLASS="COMMAND" ><A NAME="LANMANAUTH" ></A ->lanman auth (G)</DT +>>lanman auth (G)</DT ><DD ><P ->This parameter determines whether or not <A -HREF="smbd.8.html" -TARGET="_top" ->smbd</A -> will - attempt to authenticate users using the LANMAN password hash. - If disabled, only clients which support NT password hashes (e.g. Windows - NT/2000 clients, smbclient, etc... but not Windows 95/98 or the MS DOS - network client) will be able to connect to the Samba host.</P +>This parameter determines whether or not <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbd</SPAN +>(8)</SPAN +> will attempt to authenticate users + using the LANMAN password hash. If disabled, only clients which support NT + password hashes (e.g. Windows NT/2000 clients, smbclient, etc... but not + Windows 95/98 or the MS DOS network client) will be able to connect to the Samba host.</P ><P >Default : <B CLASS="COMMAND" @@ -9742,15 +9885,17 @@ CLASS="COMMAND" ><A NAME="LARGEREADWRITE" ></A ->large readwrite (G)</DT +>>large readwrite (G)</DT ><DD ><P ->This parameter determines whether or not <A -HREF="smbd.8.html" -TARGET="_top" ->smbd</A -> - supports the new 64k streaming read and write varient SMB requests introduced +>This parameter determines whether or not <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbd</SPAN +>(8)</SPAN +> supports the new 64k streaming + read and write varient SMB requests introduced with Windows 2000. Note that due to Windows 2000 client redirector bugs this requires Samba to be running on a 64-bit capable operating system such as IRIX, Solaris or a Linux 2.4 kernel. Can improve performance by 10% with @@ -9767,7 +9912,7 @@ CLASS="COMMAND" ><A NAME="LDAPADMINDN" ></A ->ldap admin dn (G)</DT +>>ldap admin dn (G)</DT ><DD ><P > The <TT @@ -9788,27 +9933,29 @@ CLASS="PARAMETER" CLASS="FILENAME" >private/secrets.tdb</TT > file. See the - <A -HREF="smbpasswd.8.html" -TARGET="_top" -><B -CLASS="COMMAND" ->smbpasswd(8)</B -></A -> man - page for more information on how to accmplish this. + <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbpasswd</SPAN +>(8)</SPAN +> man page for more information on how + to accmplish this. </P ><P ->Default : <I +>Default : <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >none</I +></SPAN ></P ></DD ><DT ><A NAME="LDAPFILTER" ></A ->ldap filter (G)</DT +>>ldap filter (G)</DT ><DD ><P >This parameter specifies the RFC 2254 compliant LDAP search filter. @@ -9825,14 +9972,14 @@ CLASS="CONSTANT" ><P >Default : <B CLASS="COMMAND" ->ldap filter = (&(uid=%u)(objectclass=sambaAccount))</B +>ldap filter = (&(uid=%u)(objectclass=sambaAccount))</B ></P ></DD ><DT ><A NAME="LDAPPORT" ></A ->ldap port (G)</DT +>>ldap port (G)</DT ><DD ><P >This parameter is only available if Samba has been @@ -9876,7 +10023,7 @@ CLASS="COMMAND" ><A NAME="LDAPSERVER" ></A ->ldap server (G)</DT +>>ldap server (G)</DT ><DD ><P >This parameter is only available if Samba has been @@ -9900,14 +10047,17 @@ CLASS="COMMAND" ><A NAME="LDAPSSL" ></A ->ldap ssl (G)</DT +>>ldap ssl (G)</DT ><DD ><P >This option is used to define whether or not Samba should use SSL when connecting to the ldap server - This is <I + This is <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >NOT</I +></SPAN > related to Samba's previous SSL support which was enabled by specifying the <B @@ -9989,7 +10139,7 @@ CLASS="COMMAND" ><A NAME="LDAPSUFFIX" ></A ->ldap suffix (G)</DT +>>ldap suffix (G)</DT ><DD ><P >Specifies where user and machine accounts are added to the tree. Can be overriden by <B @@ -10000,47 +10150,56 @@ CLASS="COMMAND" >ldap machine suffix</B >. It also used as the base dn for all ldap searches. </P ><P ->Default : <I +>Default : <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >none</I +></SPAN ></P ></DD ><DT ><A NAME="LDAPUSERSUFFIX" ></A ->ldap user suffix (G)</DT +>>ldap user suffix (G)</DT ><DD ><P >It specifies where users are added to the tree. </P ><P ->Default : <I +>Default : <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >none</I +></SPAN ></P ></DD ><DT ><A NAME="LDAPMACHINESUFFIX" ></A ->ldap machine suffix (G)</DT +>>ldap machine suffix (G)</DT ><DD ><P >It specifies where machines should be added to the ldap tree. </P ><P ->Default : <I +>Default : <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >none</I +></SPAN ></P ></DD ><DT ><A NAME="LDAPPASSWDSYNC" ></A ->ldap passwd sync (G)</DT +>>ldap passwd sync (G)</DT ><DD ><P >This option is used to define whether @@ -10098,7 +10257,7 @@ CLASS="COMMAND" ><A NAME="LDAPTRUSTIDS" ></A ->ldap trust ids (G)</DT +>>ldap trust ids (G)</DT ><DD ><P >Normally, Samba validates each entry @@ -10127,7 +10286,7 @@ CLASS="COMMAND" ><A NAME="LEVEL2OPLOCKS" ></A ->level2 oplocks (S)</DT +>>level2 oplocks (S)</DT ><DD ><P >This parameter controls whether Samba supports @@ -10211,16 +10370,15 @@ CLASS="COMMAND" ><A NAME="LMANNOUNCE" ></A ->lm announce (G)</DT +>>lm announce (G)</DT ><DD ><P ->This parameter determines if <A -HREF="nmbd.8.html" -TARGET="_top" -> <B -CLASS="COMMAND" ->nmbd(8)</B -></A +>This parameter determines if <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>nmbd</SPAN +>(8)</SPAN > will produce Lanman announce broadcasts that are needed by OS/2 clients in order for them to see the Samba server in their browse list. This parameter can have three @@ -10291,7 +10449,7 @@ CLASS="COMMAND" ><A NAME="LMINTERVAL" ></A ->lm interval (G)</DT +>>lm interval (G)</DT ><DD ><P >If Samba is set to produce Lanman announce @@ -10339,13 +10497,13 @@ CLASS="COMMAND" ><A NAME="LOADPRINTERS" ></A ->load printers (G)</DT +>>load printers (G)</DT ><DD ><P >A boolean variable that controls whether all printers in the printcap will be loaded for browsing by default. See the <A -HREF="#AEN79" +HREF="#AEN80" >printers</A > section for more details.</P @@ -10359,16 +10517,15 @@ CLASS="COMMAND" ><A NAME="LOCALMASTER" ></A ->local master (G)</DT +>>local master (G)</DT ><DD ><P ->This option allows <A -HREF="nmbd.8.html" -TARGET="_top" -><B -CLASS="COMMAND" -> nmbd(8)</B -></A +>This option allows <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>nmbd</SPAN +>(8)</SPAN > to try and become a local master browser on a subnet. If set to <TT CLASS="CONSTANT" @@ -10385,16 +10542,22 @@ CLASS="CONSTANT" CLASS="CONSTANT" >yes</TT > doesn't - mean that Samba will <I + mean that Samba will <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >become</I +></SPAN > the local master browser on a subnet, just that <B CLASS="COMMAND" >nmbd</B -> will <I +> will <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" > participate</I +></SPAN > in elections for local master browser.</P ><P >Setting this value to <TT @@ -10404,9 +10567,12 @@ CLASS="CONSTANT" CLASS="COMMAND" >nmbd</B > - <I + <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >never</I +></SPAN > to become a local master browser.</P ><P >Default: <B @@ -10418,7 +10584,7 @@ CLASS="COMMAND" ><A NAME="LOCKDIR" ></A ->lock dir (G)</DT +>>lock dir (G)</DT ><DD ><P >Synonym for <A @@ -10435,7 +10601,7 @@ CLASS="PARAMETER" ><A NAME="LOCKDIRECTORY" ></A ->lock directory (G)</DT +>>lock directory (G)</DT ><DD ><P >This option specifies the directory where lock @@ -10466,7 +10632,7 @@ CLASS="COMMAND" ><A NAME="LOCKSPINCOUNT" ></A ->lock spin count (G)</DT +>>lock spin count (G)</DT ><DD ><P >This parameter controls the number of times @@ -10489,7 +10655,7 @@ CLASS="COMMAND" ><A NAME="LOCKSPINTIME" ></A ->lock spin time (G)</DT +>>lock spin time (G)</DT ><DD ><P >The time in microseconds that smbd should @@ -10516,7 +10682,7 @@ CLASS="COMMAND" ><A NAME="LOCKING" ></A ->locking (S)</DT +>>locking (S)</DT ><DD ><P >This controls whether or not locking will be @@ -10536,13 +10702,19 @@ CLASS="COMMAND" >, real locking will be performed by the server.</P ><P ->This option <I +>This option <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >may</I +></SPAN > be useful for read-only - filesystems which <I + filesystems which <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >may</I +></SPAN > not need locking (such as CDROM drives), although setting this parameter of <TT CLASS="CONSTANT" @@ -10563,7 +10735,7 @@ CLASS="COMMAND" ><A NAME="LOGFILE" ></A ->log file (G)</DT +>>log file (G)</DT ><DD ><P >This option allows you to override the name @@ -10582,7 +10754,7 @@ CLASS="COMMAND" ><A NAME="LOGLEVEL" ></A ->log level (G)</DT +>>log level (G)</DT ><DD ><P >The value of the parameter (a astring) allows @@ -10608,7 +10780,7 @@ CLASS="COMMAND" ><A NAME="LOGONDRIVE" ></A ->logon drive (G)</DT +>>logon drive (G)</DT ><DD ><P >This parameter specifies the local path to @@ -10640,7 +10812,7 @@ CLASS="COMMAND" ><A NAME="LOGONHOME" ></A ->logon home (G)</DT +>>logon home (G)</DT ><DD ><P >This parameter specifies the home directory @@ -10721,7 +10893,7 @@ CLASS="COMMAND" ><A NAME="LOGONPATH" ></A ->logon path (G)</DT +>>logon path (G)</DT ><DD ><P >This parameter specifies the home directory @@ -10767,9 +10939,12 @@ CLASS="FILENAME" >Thereafter, the directories and any of the contents can, if required, be made read-only. It is not advisable that the NTuser.dat file be made read-only - rename it to NTuser.man to - achieve the desired effect (a <I + achieve the desired effect (a <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >MAN</I +></SPAN >datory profile). </P ><P @@ -10799,7 +10974,7 @@ CLASS="COMMAND" ><A NAME="LOGONSCRIPT" ></A ->logon script (G)</DT +>>logon script (G)</DT ><DD ><P >This parameter specifies the batch file (.bat) or @@ -10859,9 +11034,12 @@ CLASS="COMMAND" >This option is only useful if Samba is set up as a logon server.</P ><P ->Default: <I +>Default: <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >no logon script defined</I +></SPAN ></P ><P >Example: <B @@ -10873,7 +11051,7 @@ CLASS="COMMAND" ><A NAME="LPPAUSECOMMAND" ></A ->lppause command (S)</DT +>>lppause command (S)</DT ><DD ><P >This parameter specifies the command to be @@ -10971,7 +11149,7 @@ CLASS="COMMAND" ><A NAME="LPQCACHETIME" ></A ->lpq cache time (G)</DT +>>lpq cache time (G)</DT ><DD ><P >This controls how long lpq info will be cached @@ -11036,7 +11214,7 @@ CLASS="COMMAND" ><A NAME="LPQCOMMAND" ></A ->lpq command (S)</DT +>>lpq command (S)</DT ><DD ><P >This parameter specifies the command to be @@ -11106,7 +11284,9 @@ CLASS="PARAMETER" ></A > parameter.</P ><P ->Default: <I +>Default: <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >depends on the setting of <TT CLASS="PARAMETER" @@ -11114,6 +11294,7 @@ CLASS="PARAMETER" > printing</I ></TT ></I +></SPAN ></P ><P >Example: <B @@ -11125,7 +11306,7 @@ CLASS="COMMAND" ><A NAME="LPRESUMECOMMAND" ></A ->lpresume command (S)</DT +>>lpresume command (S)</DT ><DD ><P >This parameter specifies the command to be @@ -11222,7 +11403,7 @@ CLASS="COMMAND" ><A NAME="LPRMCOMMAND" ></A ->lprm command (S)</DT +>>lprm command (S)</DT ><DD ><P >This parameter specifies the command to be @@ -11265,7 +11446,9 @@ CLASS="PARAMETER" ></A > parameter.</P ><P ->Default: <I +>Default: <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >depends on the setting of <TT CLASS="PARAMETER" @@ -11274,6 +11457,7 @@ CLASS="PARAMETER" </I ></TT ></I +></SPAN ></P ><P >Example 1: <B @@ -11292,7 +11476,7 @@ CLASS="COMMAND" ><A NAME="MACHINEPASSWORDTIMEOUT" ></A ->machine password timeout (G)</DT +>>machine password timeout (G)</DT ><DD ><P >If a Samba server is a member of a Windows @@ -11313,14 +11497,12 @@ CLASS="FILENAME" will be changed, in seconds. The default is one week (expressed in seconds), the same as a Windows NT Domain member server.</P ><P ->See also <A -HREF="smbpasswd.8.html" -TARGET="_top" -><B -CLASS="COMMAND" ->smbpasswd(8) - </B -></A +>See also <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbpasswd</SPAN +>(8)</SPAN >, and the <A HREF="#SECURITYEQUALSDOMAIN" > security = domain</A @@ -11335,7 +11517,7 @@ CLASS="COMMAND" ><A NAME="MAGICOUTPUT" ></A ->magic output (S)</DT +>>magic output (S)</DT ><DD ><P >This parameter specifies the name of a file @@ -11362,7 +11544,7 @@ CLASS="PARAMETER" ><P >Default: <B CLASS="COMMAND" ->magic output = <magic script name>.out +>magic output = <magic script name>.out </B ></P ><P @@ -11375,7 +11557,7 @@ CLASS="COMMAND" ><A NAME="MAGICSCRIPT" ></A ->magic script (S)</DT +>>magic script (S)</DT ><DD ><P >This parameter specifies the name of a file which, @@ -11401,24 +11583,36 @@ CLASS="PARAMETER" >Note that some shells are unable to interpret scripts containing CR/LF instead of CR as the end-of-line marker. Magic scripts must be executable - <I + <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >as is</I +></SPAN > on the host, which for some hosts and some shells will require filtering at the DOS end.</P ><P ->Magic scripts are <I +>Magic scripts are <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >EXPERIMENTAL</I +></SPAN > and - should <I + should <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >NOT</I +></SPAN > be relied upon.</P ><P ->Default: <I +>Default: <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >None. Magic scripts disabled.</I +></SPAN ></P ><P >Example: <B @@ -11430,11 +11624,11 @@ CLASS="COMMAND" ><A NAME="MANGLECASE" ></A ->mangle case (S)</DT +>>mangle case (S)</DT ><DD ><P >See the section on <A -HREF="#AEN205" +HREF="#AEN206" > NAME MANGLING</A ></P ><P @@ -11447,7 +11641,7 @@ CLASS="COMMAND" ><A NAME="MANGLEDMAP" ></A ->mangled map (S)</DT +>>mangled map (S)</DT ><DD ><P >This is for those who want to directly map UNIX @@ -11485,9 +11679,12 @@ CLASS="FILENAME" > off the ends of filenames on some CDROMs (only visible under some UNIXes). To do this use a map of (*;1 *;).</P ><P ->Default: <I +>Default: <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >no mangled map</I +></SPAN ></P ><P >Example: <B @@ -11499,7 +11696,7 @@ CLASS="COMMAND" ><A NAME="MANGLEDNAMES" ></A ->mangled names (S)</DT +>>mangled names (S)</DT ><DD ><P >This controls whether non-DOS names under UNIX @@ -11507,7 +11704,7 @@ NAME="MANGLEDNAMES" or whether non-DOS names should simply be ignored.</P ><P >See the section on <A -HREF="#AEN205" +HREF="#AEN206" > NAME MANGLING</A > for details on how to control the mangling process.</P ><P @@ -11584,7 +11781,7 @@ CLASS="COMMAND" ><A NAME="MANGLINGMETHOD" ></A ->mangling method (G)</DT +>>mangling method (G)</DT ><DD ><P > controls the algorithm used for the generating @@ -11610,7 +11807,7 @@ CLASS="COMMAND" ><A NAME="MANGLEPREFIX" ></A ->mangle prefix (G)</DT +>>mangle prefix (G)</DT ><DD ><P > controls the number of prefix @@ -11633,14 +11830,16 @@ CLASS="COMMAND" ><A NAME="MANGLEDSTACK" ></A ->mangled stack (G)</DT +>>mangled stack (G)</DT ><DD ><P >This parameter controls the number of mangled names - that should be cached in the Samba server <A -HREF="smbd.8.html" -TARGET="_top" -> smbd(8)</A + that should be cached in the Samba server <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbd</SPAN +>(8)</SPAN >.</P ><P >This stack is a list of recently mangled base names @@ -11670,15 +11869,18 @@ CLASS="COMMAND" ><A NAME="MANGLINGCHAR" ></A ->mangling char (S)</DT +>>mangling char (S)</DT ><DD ><P >This controls what character is used as - the <I + the <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >magic</I +></SPAN > character in <A -HREF="#AEN205" +HREF="#AEN206" >name mangling</A >. The default is a '~' but this may interfere with some software. Use this option to set @@ -11698,7 +11900,7 @@ CLASS="COMMAND" ><A NAME="MAPARCHIVE" ></A ->map archive (S)</DT +>>map archive (S)</DT ><DD ><P >This controls whether the DOS archive attribute @@ -11734,7 +11936,7 @@ CLASS="COMMAND" ><A NAME="MAPHIDDEN" ></A ->map hidden (S)</DT +>>map hidden (S)</DT ><DD ><P >This controls whether DOS style hidden files @@ -11766,7 +11968,7 @@ CLASS="COMMAND" ><A NAME="MAPSYSTEM" ></A ->map system (S)</DT +>>map system (S)</DT ><DD ><P >This controls whether DOS style system files @@ -11798,7 +12000,7 @@ CLASS="COMMAND" ><A NAME="MAPTOGUEST" ></A ->map to guest (G)</DT +>>map to guest (G)</DT ><DD ><P >This parameter is only useful in <A @@ -11823,10 +12025,12 @@ CLASS="CONSTANT" >.</P ><P >This parameter can take three different values, which tell - <A -HREF="smbd.8.html" -TARGET="_top" ->smbd(8)</A + <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbd</SPAN +>(8)</SPAN > what to do with user login requests that don't match a valid UNIX user in some way.</P ><P @@ -11877,9 +12081,12 @@ HREF="#GUESTACCOUNT" will not know the reason they cannot access files they think they should - there will have been no message given to them that they got their password wrong. Helpdesk services will - <I + <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >hate</I +></SPAN > you if you set the <TT CLASS="PARAMETER" ><I @@ -11898,9 +12105,12 @@ CLASS="PARAMETER" ></TT > modes other than share. This is because in these modes the name of the resource being - requested is <I + requested is <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >not</I +></SPAN > sent to the server until after the server has successfully authenticated the client so the server cannot make authentication decisions at the correct time (connection @@ -11926,7 +12136,7 @@ CLASS="COMMAND" ><A NAME="MAXCONNECTIONS" ></A ->max connections (S)</DT +>>max connections (S)</DT ><DD ><P >This option allows the number of simultaneous @@ -11966,7 +12176,7 @@ CLASS="COMMAND" ><A NAME="MAXDISKSIZE" ></A ->max disk size (G)</DT +>>max disk size (G)</DT ><DD ><P >This option allows you to put an upper limit @@ -12011,7 +12221,7 @@ CLASS="COMMAND" ><A NAME="MAXLOGSIZE" ></A ->max log size (G)</DT +>>max log size (G)</DT ><DD ><P >This option (an integer in kilobytes) specifies @@ -12038,7 +12248,7 @@ CLASS="COMMAND" ><A NAME="MAXMUX" ></A ->max mux (G)</DT +>>max mux (G)</DT ><DD ><P >This option controls the maximum number of @@ -12054,14 +12264,16 @@ CLASS="COMMAND" ><A NAME="MAXOPENFILES" ></A ->max open files (G)</DT +>>max open files (G)</DT ><DD ><P >This parameter limits the maximum number of - open files that one <A -HREF="smbd.8.html" -TARGET="_top" ->smbd(8)</A + open files that one <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbd</SPAN +>(8)</SPAN > file serving process may have open for a client at any one time. The default for this parameter is set very high (10,000) as Samba uses @@ -12080,18 +12292,17 @@ CLASS="COMMAND" ><A NAME="MAXPRINTJOBS" ></A ->max print jobs (S)</DT +>>max print jobs (S)</DT ><DD ><P >This parameter limits the maximum number of jobs allowable in a Samba printer queue at any given moment. - If this number is exceeded, <A -HREF="smbd.8.html" -TARGET="_top" -><B -CLASS="COMMAND" -> smbd(8)</B -></A + If this number is exceeded, <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbd</SPAN +>(8)</SPAN > will remote "Out of Space" to the client. See all <A HREF="#TOTALPRINTJOBS" @@ -12119,7 +12330,7 @@ CLASS="COMMAND" ><A NAME="MAXPROTOCOL" ></A ->max protocol (G)</DT +>>max protocol (G)</DT ><DD ><P >The value of the parameter (a string) is the highest @@ -12150,9 +12361,12 @@ CLASS="CONSTANT" ><TT CLASS="CONSTANT" >LANMAN1</TT ->: First <I +>: First <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" > modern</I +></SPAN > version of the protocol. Long filename support.</P ></LI @@ -12203,7 +12417,7 @@ CLASS="COMMAND" ><A NAME="MAXSMBDPROCESSES" ></A ->max smbd processes (G)</DT +>>max smbd processes (G)</DT ><DD ><P >This parameter limits the maximum number of @@ -12219,10 +12433,12 @@ CLASS="COMMAND" as a stopgap to prevent degrading service to clients in the event that the server has insufficient resources to handle more than this number of connections. Remember that under normal operating - conditions, each user will have an <A -HREF="smbd.8.html" -TARGET="_top" ->smbd</A + conditions, each user will have an <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbd</SPAN +>(8)</SPAN > associated with him or her to handle connections to all shares from a given host. </P @@ -12241,13 +12457,15 @@ CLASS="COMMAND" ><A NAME="MAXTTL" ></A ->max ttl (G)</DT +>>max ttl (G)</DT ><DD ><P ->This option tells <A -HREF="nmbd.8.html" -TARGET="_top" ->nmbd(8)</A +>This option tells <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>nmbd</SPAN +>(8)</SPAN > what the default 'time to live' of NetBIOS names should be (in seconds) when <B @@ -12266,14 +12484,15 @@ CLASS="COMMAND" ><A NAME="MAXWINSTTL" ></A ->max wins ttl (G)</DT +>>max wins ttl (G)</DT ><DD ><P ->This option tells <A -HREF="nmbd.8.html" -TARGET="_top" ->nmbd(8) - </A +>This option tells <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbd</SPAN +>(8)</SPAN > when acting as a WINS server (<A HREF="#WINSSUPPORT" > <TT @@ -12310,7 +12529,7 @@ CLASS="COMMAND" ><A NAME="MAXXMIT" ></A ->max xmit (G)</DT +>>max xmit (G)</DT ><DD ><P >This option controls the maximum packet size @@ -12333,7 +12552,7 @@ CLASS="COMMAND" ><A NAME="MESSAGECOMMAND" ></A ->message command (G)</DT +>>message command (G)</DT ><DD ><P >This specifies what command to run when the @@ -12347,7 +12566,7 @@ NAME="MESSAGECOMMAND" ><P ><B CLASS="COMMAND" ->message command = csh -c 'xedit %s;rm %s' &</B +>message command = csh -c 'xedit %s;rm %s' &</B > </P ><P @@ -12355,12 +12574,15 @@ CLASS="COMMAND" CLASS="COMMAND" >xedit</B >, then - removes it afterwards. <I + removes it afterwards. <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >NOTE THAT IT IS VERY IMPORTANT THAT THIS COMMAND RETURN IMMEDIATELY</I +></SPAN >. That's why I - have the '&' on the end. If it doesn't return immediately then + have the '&' on the end. If it doesn't return immediately then your PCs may freeze when sending messages (they should recover after 30 seconds, hopefully).</P ><P @@ -12424,7 +12646,7 @@ CLASS="PARAMETER" ><B CLASS="COMMAND" >message command = /bin/mail -s 'message from %f on - %m' root < %s; rm %s</B + %m' root < %s; rm %s</B ></P ><P >If you don't have a message command then the message @@ -12440,22 +12662,25 @@ CLASS="COMMAND" >message command = rm %s</B ></P ><P ->Default: <I +>Default: <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >no message command</I +></SPAN ></P ><P >Example: <B CLASS="COMMAND" >message command = csh -c 'xedit %s; - rm %s' &</B + rm %s' &</B ></P ></DD ><DT ><A NAME="MINPASSWDLENGTH" ></A ->min passwd length (G)</DT +>>min passwd length (G)</DT ><DD ><P >Synonym for <A @@ -12472,7 +12697,7 @@ CLASS="PARAMETER" ><A NAME="MINPASSWORDLENGTH" ></A ->min password length (G)</DT +>>min password length (G)</DT ><DD ><P >This option sets the minimum length in characters @@ -12519,7 +12744,7 @@ CLASS="COMMAND" ><A NAME="MINPRINTSPACE" ></A ->min print space (S)</DT +>>min print space (S)</DT ><DD ><P >This sets the minimum amount of free disk @@ -12552,7 +12777,7 @@ CLASS="COMMAND" ><A NAME="MINPROTOCOL" ></A ->min protocol (G)</DT +>>min protocol (G)</DT ><DD ><P >The value of the parameter (a string) is the @@ -12602,13 +12827,15 @@ CLASS="COMMAND" ><A NAME="MINWINSTTL" ></A ->min wins ttl (G)</DT +>>min wins ttl (G)</DT ><DD ><P ->This option tells <A -HREF="nmbd.8.html" -TARGET="_top" ->nmbd(8)</A +>This option tells <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>nmbd</SPAN +>(8)</SPAN > when acting as a WINS server (<A HREF="#WINSSUPPORT" @@ -12635,7 +12862,7 @@ CLASS="COMMAND" ><A NAME="MSDFSPROXY" ></A ->msdfs proxy (S)</DT +>>msdfs proxy (S)</DT ><DD ><P >This parameter indicates that the share is a @@ -12668,14 +12895,14 @@ CLASS="PARAMETER" ><P >Example: <B CLASS="COMMAND" ->msdfs proxy = \otherserver\someshare</B +>msdfs proxy = \\\\otherserver\\someshare</B ></P ></DD ><DT ><A NAME="MSDFSROOT" ></A ->msdfs root (S)</DT +>>msdfs root (S)</DT ><DD ><P >This boolean parameter is only available if @@ -12691,15 +12918,15 @@ CLASS="CONSTANT" Dfs links are specified in the share directory by symbolic links of the form <TT CLASS="FILENAME" ->msdfs:serverA\shareA,serverB\shareB</TT +>msdfs:serverA\\shareA,serverB\\shareB</TT > and so on. For more information on setting up a Dfs tree on Samba, refer to <A -HREF="msdfs_setup.html" +HREF="msdfs.html" TARGET="_top" ->msdfs_setup.html - </A ->.</P +>"Hosting a Microsoft + Distributed File System tree on Samba"</A +> document.</P ><P >See also <A HREF="#HOSTMSDFS" @@ -12721,7 +12948,7 @@ CLASS="COMMAND" ><A NAME="NAMECACHETIMEOUT" ></A ->name cache timeout (G)</DT +>>name cache timeout (G)</DT ><DD ><P >Specifies the number of seconds it takes before @@ -12743,7 +12970,7 @@ CLASS="COMMAND" ><A NAME="NAMERESOLVEORDER" ></A ->name resolve order (G)</DT +>>name resolve order (G)</DT ><DD ><P >This option is used by the programs in the Samba @@ -12848,7 +13075,7 @@ CLASS="COMMAND" ><A NAME="NETBIOSALIASES" ></A ->netbios aliases (G)</DT +>>netbios aliases (G)</DT ><DD ><P >This is a list of NetBIOS names that <A @@ -12874,9 +13101,12 @@ CLASS="PARAMETER" ></A >.</P ><P ->Default: <I +>Default: <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >empty string (no additional names)</I +></SPAN ></P ><P >Example: <B @@ -12888,7 +13118,7 @@ CLASS="COMMAND" ><A NAME="NETBIOSNAME" ></A ->netbios name (G)</DT +>>netbios name (G)</DT ><DD ><P >This sets the NetBIOS name by which a Samba @@ -12909,9 +13139,12 @@ CLASS="PARAMETER" ></A >.</P ><P ->Default: <I +>Default: <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >machine DNS name</I +></SPAN ></P ><P >Example: <B @@ -12923,7 +13156,7 @@ CLASS="COMMAND" ><A NAME="NETBIOSSCOPE" ></A ->netbios scope (G)</DT +>>netbios scope (G)</DT ><DD ><P >This sets the NetBIOS scope that Samba will @@ -12934,7 +13167,7 @@ NAME="NETBIOSSCOPE" ><A NAME="NISHOMEDIR" ></A ->nis homedir (G)</DT +>>nis homedir (G)</DT ><DD ><P >Get the home share server from a NIS map. For @@ -12978,7 +13211,7 @@ CLASS="COMMAND" ><A NAME="NONUNIXACCOUNTRANGE" ></A ->non unix account range (G)</DT +>>non unix account range (G)</DT ><DD ><P >The non unix account range parameter specifies @@ -12996,7 +13229,7 @@ NAME="NONUNIXACCOUNTRANGE" ><P >Default: <B CLASS="COMMAND" ->non unix account range = <empty string> +>non unix account range = <empty string> </B ></P ><P @@ -13009,7 +13242,7 @@ CLASS="COMMAND" ><A NAME="NTACLSUPPORT" ></A ->nt acl support (S)</DT +>>nt acl support (S)</DT ><DD ><P >This boolean parameter controls whether @@ -13031,14 +13264,16 @@ CLASS="COMMAND" ><A NAME="NTPIPESUPPORT" ></A ->nt pipe support (G)</DT +>>nt pipe support (G)</DT ><DD ><P >This boolean parameter controls whether - <A -HREF="smbd.8.html" -TARGET="_top" ->smbd(8)</A + <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbd</SPAN +>(8)</SPAN > will allow Windows NT clients to connect to the NT SMB specific <TT CLASS="CONSTANT" @@ -13056,7 +13291,7 @@ CLASS="COMMAND" ><A NAME="NTSTATUSSUPPORT" ></A ->nt status support (G)</DT +>>nt status support (G)</DT ><DD ><P >This boolean parameter controls whether <A @@ -13084,16 +13319,18 @@ CLASS="COMMAND" ><A NAME="NULLPASSWORDS" ></A ->null passwords (G)</DT +>>null passwords (G)</DT ><DD ><P >Allow or disallow client access to accounts that have null passwords. </P ><P ->See also <A -HREF="smbpasswd.5.html" -TARGET="_top" ->smbpasswd (5)</A +>See also <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbpasswd</SPAN +>(5)</SPAN >.</P ><P >Default: <B @@ -13105,7 +13342,7 @@ CLASS="COMMAND" ><A NAME="OBEYPAMRESTRICTIONS" ></A ->obey pam restrictions (G)</DT +>>obey pam restrictions (G)</DT ><DD ><P >When Samba 2.2 is configured to enable PAM support @@ -13135,7 +13372,7 @@ CLASS="COMMAND" ><A NAME="ONLYUSER" ></A ->only user (S)</DT +>>only user (S)</DT ><DD ><P >This is a boolean option that controls whether @@ -13195,7 +13432,7 @@ CLASS="COMMAND" ><A NAME="ONLYGUEST" ></A ->only guest (S)</DT +>>only guest (S)</DT ><DD ><P >A synonym for <A @@ -13212,7 +13449,7 @@ CLASS="PARAMETER" ><A NAME="OPLOCKBREAKWAITTIME" ></A ->oplock break wait time (G)</DT +>>oplock break wait time (G)</DT ><DD ><P >This is a tuning parameter added due to bugs in @@ -13223,10 +13460,13 @@ NAME="OPLOCKBREAKWAITTIME" is the amount of time Samba will wait before sending an oplock break request to such (broken) clients.</P ><P +><SPAN +CLASS="emphasis" ><I CLASS="EMPHASIS" >DO NOT CHANGE THIS PARAMETER UNLESS YOU HAVE READ AND UNDERSTOOD THE SAMBA OPLOCK CODE</I +></SPAN >.</P ><P >Default: <B @@ -13238,12 +13478,15 @@ CLASS="COMMAND" ><A NAME="OPLOCKCONTENTIONLIMIT" ></A ->oplock contention limit (S)</DT +>>oplock contention limit (S)</DT ><DD ><P ->This is a <I +>This is a <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >very</I +></SPAN > advanced <A HREF="smbd.8.html" @@ -13253,23 +13496,27 @@ TARGET="_top" improve the efficiency of the granting of oplocks under multiple client contention for the same file.</P ><P ->In brief it specifies a number, which causes <A -HREF="smbd.8.html" -TARGET="_top" ->smbd</A -> not to - grant an oplock even when requested if the approximate number of - clients contending for an oplock on the same file goes over this +>In brief it specifies a number, which causes <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbd</SPAN +>(8)</SPAN +>not to grant an oplock even when requested + if the approximate number of clients contending for an oplock on the same file goes over this limit. This causes <B CLASS="COMMAND" >smbd</B > to behave in a similar way to Windows NT.</P ><P +><SPAN +CLASS="emphasis" ><I CLASS="EMPHASIS" >DO NOT CHANGE THIS PARAMETER UNLESS YOU HAVE READ AND UNDERSTOOD THE SAMBA OPLOCK CODE</I +></SPAN >.</P ><P >Default: <B @@ -13281,7 +13528,7 @@ CLASS="COMMAND" ><A NAME="OPLOCKS" ></A ->oplocks (S)</DT +>>oplocks (S)</DT ><DD ><P >This boolean option tells <B @@ -13351,13 +13598,16 @@ CLASS="COMMAND" ><A NAME="NTLMAUTH" ></A ->ntlm auth (G)</DT +>>ntlm auth (G)</DT ><DD ><P ->This parameter determines whether or not <A -HREF="smbd.8.html" -TARGET="_top" ->smbd</A +>This parameter determines + whether or not <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbd</SPAN +>(8)</SPAN > will attempt to authenticate users using the NTLM password hash. If disabled, only the lanman password hashes will be used. @@ -13366,7 +13616,8 @@ TARGET="_top" >Please note that at least this option or <B CLASS="COMMAND" >lanman auth</B -> should be enabled in order to be able to log in. +> should + be enabled in order to be able to log in. </P ><P >Default : <B @@ -13378,15 +13629,17 @@ CLASS="COMMAND" ><A NAME="OSLEVEL" ></A ->os level (G)</DT +>>os level (G)</DT ><DD ><P >This integer value controls what level Samba advertises itself as for browse elections. The value of this - parameter determines whether <A -HREF="nmbd.8.html" -TARGET="_top" ->nmbd(8)</A + parameter determines whether <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>nmbd</SPAN +>(8)</SPAN > has a chance of becoming a local master browser for the <TT CLASS="PARAMETER" @@ -13395,9 +13648,12 @@ CLASS="PARAMETER" ></TT > in the local broadcast area.</P ><P +><SPAN +CLASS="emphasis" ><I CLASS="EMPHASIS" >Note :</I +></SPAN >By default, Samba will win a local master browsing election over all Microsoft operating systems except a Windows NT 4.0/2000 Domain Controller. This @@ -13426,15 +13682,15 @@ CLASS="COMMAND" ><A NAME="OS2DRIVERMAP" ></A ->os2 driver map (G)</DT +>>os2 driver map (G)</DT ><DD ><P >The parameter is used to define the absolute path to a file containing a mapping of Windows NT printer driver names to OS/2 printer driver names. The format is:</P ><P -><nt driver name> = <os2 driver - name>.<device name></P +><nt driver name> = <os2 driver + name>.<device name></P ><P >For example, a valid entry using the HP LaserJet 5 printer driver would appear as <B @@ -13445,21 +13701,16 @@ CLASS="COMMAND" ><P >The need for the file is due to the printer driver namespace problem described in the <A -HREF="printer_driver2.html" +HREF="printing.html" TARGET="_top" >Samba Printing HOWTO</A >. For more details on OS/2 clients, please - refer to the <A -HREF="OS2-Client-HOWTO.html" -TARGET="_top" ->OS2-Client-HOWTO - </A -> containing in the Samba documentation.</P + refer to the OS2-Client-HOWTO containing in the Samba documentation.</P ><P >Default: <B CLASS="COMMAND" ->os2 driver map = <empty string> +>os2 driver map = <empty string> </B ></P ></DD @@ -13467,7 +13718,7 @@ CLASS="COMMAND" ><A NAME="PAMPASSWORDCHANGE" ></A ->pam password change (G)</DT +>>pam password change (G)</DT ><DD ><P >With the addition of better PAM support in Samba 2.2, @@ -13505,25 +13756,28 @@ CLASS="COMMAND" ><A NAME="PANICACTION" ></A ->panic action (G)</DT +>>panic action (G)</DT ><DD ><P >This is a Samba developer option that allows a - system command to be called when either <A -HREF="smbd.8.html" -TARGET="_top" -> smbd(8)</A -> or <A -HREF="nmbd.8.html" -TARGET="_top" ->nmbd(8)</A -> - crashes. This is usually used to draw attention to the fact that - a problem occurred.</P + system command to be called when either <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbd</SPAN +>(8)</SPAN +> or <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbd</SPAN +>(8)</SPAN +> crashes. This is usually used to + draw attention to the fact that a problem occurred.</P ><P >Default: <B CLASS="COMMAND" ->panic action = <empty string></B +>panic action = <empty string></B ></P ><P >Example: <B @@ -13535,15 +13789,19 @@ CLASS="COMMAND" ><A NAME="PARANOIDSERVERSECURITY" ></A ->paranoid server security (G)</DT +>>paranoid server security (G)</DT ><DD ><P >Some version of NT 4.x allow non-guest users with a bad passowrd. When this option is enabled, samba will not use a broken NT 4.x server as password server, but instead complain - to the logs and exit. + to the logs and exit. </P ><P +>Disabling this option prevents Samba from making + this check, which involves deliberatly attempting a + bad logon to the remote server.</P +><P >Default: <B CLASS="COMMAND" >paranoid server security = yes</B @@ -13553,7 +13811,7 @@ CLASS="COMMAND" ><A NAME="PASSDBBACKEND" ></A ->passdb backend (G)</DT +>>passdb backend (G)</DT ><DD ><P >This option allows the administrator to chose which backends to retrieve and store passwords with. This allows (for example) both @@ -13765,23 +14023,30 @@ CLASS="COMMAND" ><A NAME="PASSWDCHAT" ></A ->passwd chat (G)</DT +>>passwd chat (G)</DT ><DD ><P ->This string controls the <I +>This string controls the <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >"chat"</I +></SPAN > - conversation that takes places between <A -HREF="smbd.8.html" -TARGET="_top" ->smbd</A + conversation that takes places between <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbd</SPAN +>(8)</SPAN > and the local password changing program to change the user's password. The string describes a - sequence of response-receive pairs that <A -HREF="smbd.8.html" -TARGET="_top" -> smbd(8)</A + sequence of response-receive pairs that <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbd</SPAN +>(8)</SPAN > uses to determine what to send to the <A HREF="#PASSWDPROGRAM" @@ -13812,9 +14077,12 @@ CLASS="PARAMETER" CLASS="CONSTANT" >yes</TT >. This - sequence is then called <I + sequence is then called <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >AS ROOT</I +></SPAN > when the SMB password in the smbpasswd file is being changed, without access to the old password cleartext. This means that root must be able to reset the user's password @@ -13835,16 +14103,16 @@ CLASS="PARAMETER" for the new password. The chat sequence can also contain the standard macros <TT CLASS="CONSTANT" ->\n</TT +>\\n</TT >, <TT CLASS="CONSTANT" ->\r</TT +>\\r</TT >, <TT CLASS="CONSTANT" -> \t</TT +> \\t</TT > and <TT CLASS="CONSTANT" ->\s</TT +>\\s</TT > to give line-feed, carriage-return, tab and space. The chat sequence string can also contain a '*' which matches any sequence of characters. @@ -13909,14 +14177,14 @@ CLASS="PARAMETER" ><P >Default: <B CLASS="COMMAND" ->passwd chat = *new*password* %n\n - *new*password* %n\n *changed*</B +>passwd chat = *new*password* %n\\n + *new*password* %n\\n *changed*</B ></P ><P >Example: <B CLASS="COMMAND" ->passwd chat = "*Enter OLD password*" %o\n - "*Enter NEW password*" %n\n "*Reenter NEW password*" %n\n "*Password +>passwd chat = "*Enter OLD password*" %o\\n + "*Enter NEW password*" %n\\n "*Reenter NEW password*" %n\\n "*Password changed*"</B ></P ></DD @@ -13924,19 +14192,24 @@ CLASS="COMMAND" ><A NAME="PASSWDCHATDEBUG" ></A ->passwd chat debug (G)</DT +>>passwd chat debug (G)</DT ><DD ><P >This boolean specifies if the passwd chat script - parameter is run in <I + parameter is run in <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >debug</I +></SPAN > mode. In this mode the strings passed to and received from the passwd chat are printed - in the <A -HREF="smbd.8.html" -TARGET="_top" ->smbd(8)</A + in the <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbd</SPAN +>(8)</SPAN > log with a <A HREF="#DEBUGLEVEL" @@ -14014,7 +14287,7 @@ CLASS="COMMAND" ><A NAME="PASSWDPROGRAM" ></A ->passwd program (G)</DT +>>passwd program (G)</DT ><DD ><P >The name of a program that can be used to set @@ -14027,18 +14300,24 @@ CLASS="PARAMETER" will be replaced with the user name. The user name is checked for existence before calling the password changing program.</P ><P ->Also note that many passwd programs insist in <I +>Also note that many passwd programs insist in <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >reasonable </I +></SPAN > passwords, such as a minimum length, or the inclusion of mixed case chars and digits. This can pose a problem as some clients (such as Windows for Workgroups) uppercase the password before sending it.</P ><P +><SPAN +CLASS="emphasis" ><I CLASS="EMPHASIS" >Note</I +></SPAN > that if the <TT CLASS="PARAMETER" ><I @@ -14049,9 +14328,12 @@ CLASS="PARAMETER" CLASS="CONSTANT" >yes </TT -> then this program is called <I +> then this program is called <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >AS ROOT</I +></SPAN > before the SMB password in the <A HREF="smbpasswd.5.html" @@ -14071,13 +14353,19 @@ CLASS="PARAMETER" >unix password sync</I ></TT > parameter - is set this parameter <I + is set this parameter <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >MUST USE ABSOLUTE PATHS</I +></SPAN > - for <I + for <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >ALL</I +></SPAN > programs called, and must be examined for security implications. Note that by default <TT CLASS="PARAMETER" @@ -14116,7 +14404,7 @@ CLASS="COMMAND" ><A NAME="PASSWORDLEVEL" ></A ->password level (G)</DT +>>password level (G)</DT ><DD ><P >Some client/server combinations have difficulty @@ -14176,7 +14464,7 @@ CLASS="COMMAND" ><A NAME="PASSWORDSERVER" ></A ->password server (G)</DT +>>password server (G)</DT ><DD ><P >By specifying the name of another SMB server (such @@ -14216,15 +14504,21 @@ CLASS="PARAMETER" the "LM1.2X002" or the "NT LM 0.12" protocol, and it must be in user level security mode.</P ><P +><SPAN +CLASS="emphasis" ><I CLASS="EMPHASIS" >NOTE:</I +></SPAN > Using a password server means your UNIX box (running Samba) is only as secure as your - password server. <I + password server. <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >DO NOT CHOOSE A PASSWORD SERVER THAT YOU DON'T COMPLETELY TRUST</I +></SPAN >.</P ><P >Never point a Samba server at itself for password @@ -14281,7 +14575,7 @@ CLASS="PARAMETER" Primary or Backup Domain controllers to authenticate against by doing a query for the name <TT CLASS="CONSTANT" ->WORKGROUP<1C></TT +>WORKGROUP<1C></TT > and then contacting each server returned in the list of IP addresses from the name resolution source. </P @@ -14359,7 +14653,7 @@ CLASS="PARAMETER" ><P >Default: <B CLASS="COMMAND" ->password server = <empty string></B +>password server = <empty string></B > </P ><P @@ -14378,7 +14672,7 @@ CLASS="COMMAND" ><A NAME="PATH" ></A ->path (S)</DT +>>path (S)</DT ><DD ><P >This parameter specifies a directory to which @@ -14419,9 +14713,12 @@ CLASS="PARAMETER" ></A > if one was specified.</P ><P ->Default: <I +>Default: <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >none</I +></SPAN ></P ><P >Example: <B @@ -14433,7 +14730,7 @@ CLASS="COMMAND" ><A NAME="PIDDIRECTORY" ></A ->pid directory (G)</DT +>>pid directory (G)</DT ><DD ><P >This option specifies the directory where pid @@ -14454,16 +14751,15 @@ CLASS="COMMAND" ><A NAME="POSIXLOCKING" ></A ->posix locking (S)</DT +>>posix locking (S)</DT ><DD ><P ->The <A -HREF="smbd.8.html" -TARGET="_top" -><B -CLASS="COMMAND" ->smbd(8)</B -></A +>The <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbd</SPAN +>(8)</SPAN > daemon maintains an database of file locks obtained by SMB clients. The default behavior is to map this internal database to POSIX @@ -14481,7 +14777,7 @@ CLASS="COMMAND" ><A NAME="POSTEXEC" ></A ->postexec (S)</DT +>>postexec (S)</DT ><DD ><P >This option specifies a command to be run @@ -14508,23 +14804,26 @@ CLASS="PARAMETER" </A >.</P ><P ->Default: <I +>Default: <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >none (no command executed)</I +></SPAN > </P ><P >Example: <B CLASS="COMMAND" >postexec = echo \"%u disconnected from %S - from %m (%I)\" >> /tmp/log</B + from %m (%I)\" >> /tmp/log</B ></P ></DD ><DT ><A NAME="POSTSCRIPT" ></A ->postscript (S)</DT +>>postscript (S)</DT ><DD ><P >This parameter forces a printer to interpret @@ -14547,7 +14846,7 @@ CLASS="COMMAND" ><A NAME="PREEXEC" ></A ->preexec (S)</DT +>>preexec (S)</DT ><DD ><P >This option specifies a command to be run whenever @@ -14560,7 +14859,7 @@ NAME="PREEXEC" ><B CLASS="COMMAND" >preexec = csh -c 'echo \"Welcome to %S!\" | - /usr/local/samba/bin/smbclient -M %m -I %I' & </B + /usr/local/samba/bin/smbclient -M %m -I %I' & </B ></P ><P >Of course, this could get annoying after a while :-)</P @@ -14585,22 +14884,25 @@ CLASS="PARAMETER" ></A >.</P ><P ->Default: <I +>Default: <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >none (no command executed)</I +></SPAN ></P ><P >Example: <B CLASS="COMMAND" >preexec = echo \"%u connected to %S from %m - (%I)\" >> /tmp/log</B + (%I)\" >> /tmp/log</B ></P ></DD ><DT ><A NAME="PREEXECCLOSE" ></A ->preexec close (S)</DT +>>preexec close (S)</DT ><DD ><P >This boolean option controls whether a non-zero @@ -14624,7 +14926,7 @@ CLASS="COMMAND" ><A NAME="PREFERREDMASTER" ></A ->preferred master (G)</DT +>>preferred master (G)</DT ><DD ><P >This boolean parameter controls if <A @@ -14686,7 +14988,7 @@ CLASS="COMMAND" ><A NAME="PREFEREDMASTER" ></A ->prefered master (G)</DT +>>prefered master (G)</DT ><DD ><P >Synonym for <A @@ -14703,7 +15005,7 @@ CLASS="PARAMETER" ><A NAME="PRELOAD" ></A ->preload (G)</DT +>>preload (G)</DT ><DD ><P >This is a list of services that you want to be @@ -14722,9 +15024,12 @@ CLASS="PARAMETER" ></A > option is easier.</P ><P ->Default: <I +>Default: <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >no preloaded services</I +></SPAN ></P ><P >Example: <B @@ -14736,7 +15041,7 @@ CLASS="COMMAND" ><A NAME="PRESERVECASE" ></A ->preserve case (S)</DT +>>preserve case (S)</DT ><DD ><P > This controls if new filenames are created @@ -14758,7 +15063,7 @@ CLASS="COMMAND" ></P ><P >See the section on <A -HREF="#AEN205" +HREF="#AEN206" >NAME MANGLING</A > for a fuller discussion.</P @@ -14767,7 +15072,7 @@ HREF="#AEN205" ><A NAME="PRINTCOMMAND" ></A ->print command (S)</DT +>>print command (S)</DT ><DD ><P >After a print job has finished spooling to @@ -14800,9 +15105,12 @@ CLASS="COMMAND" >%z - the size of the spooled print job (in bytes)</P ><P ->The print command <I +>The print command <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >MUST</I +></SPAN > contain at least one occurrence of <TT CLASS="PARAMETER" @@ -14860,7 +15168,7 @@ CLASS="PARAMETER" ><P ><B CLASS="COMMAND" ->print command = echo Printing %s >> +>print command = echo Printing %s >> /tmp/print.log; lpr -P %p %s; rm %s</B ></P ><P @@ -14936,7 +15244,7 @@ CLASS="COMMAND" ><A NAME="PRINTOK" ></A ->print ok (S)</DT +>>print ok (S)</DT ><DD ><P >Synonym for <A @@ -14953,7 +15261,7 @@ CLASS="PARAMETER" ><A NAME="PRINTABLE" ></A ->printable (S)</DT +>>printable (S)</DT ><DD ><P >If this parameter is <TT @@ -14986,7 +15294,7 @@ CLASS="COMMAND" ><A NAME="PRINTCAP" ></A ->printcap (G)</DT +>>printcap (G)</DT ><DD ><P >Synonym for <A @@ -15003,7 +15311,7 @@ CLASS="PARAMETER" ><A NAME="PRINTCAPNAME" ></A ->printcap name (G)</DT +>>printcap name (G)</DT ><DD ><P >This parameter may be used to override the @@ -15011,7 +15319,7 @@ NAME="PRINTCAPNAME" CLASS="FILENAME" > /etc/printcap</TT >). See the discussion of the <A -HREF="#AEN79" +HREF="#AEN80" >[printers]</A > section above for reasons why you might want to do this.</P @@ -15060,32 +15368,25 @@ CLASS="COMMAND" ><P >A minimal printcap file would look something like this:</P ><P -><TABLE -BORDER="0" -BGCOLOR="#E0E0E0" -WIDTH="90%" -><TR -><TD ><PRE CLASS="PROGRAMLISTING" -> print1|My Printer 1 - print2|My Printer 2 - print3|My Printer 3 - print4|My Printer 4 - print5|My Printer 5 - </PRE -></TD -></TR -></TABLE +>print1|My Printer 1 +print2|My Printer 2 +print3|My Printer 3 +print4|My Printer 4 +print5|My Printer 5</PRE ></P ><P >where the '|' separates aliases of a printer. The fact that the second alias has a space in it gives a hint to Samba that it's a comment.</P ><P +><SPAN +CLASS="emphasis" ><I CLASS="EMPHASIS" >NOTE</I +></SPAN >: Under AIX the default printcap name is <TT CLASS="FILENAME" @@ -15114,7 +15415,7 @@ CLASS="COMMAND" ><A NAME="PRINTERADMIN" ></A ->printer admin (S)</DT +>>printer admin (S)</DT ><DD ><P >This is a list of users that can do anything to @@ -15124,7 +15425,7 @@ NAME="PRINTERADMIN" ><P >Default: <B CLASS="COMMAND" ->printer admin = <empty string></B +>printer admin = <empty string></B > </P ><P @@ -15137,17 +15438,20 @@ CLASS="COMMAND" ><A NAME="PRINTERDRIVER" ></A ->printer driver (S)</DT +>>printer driver (S)</DT ><DD ><P +><SPAN +CLASS="emphasis" ><I CLASS="EMPHASIS" >Note :</I +></SPAN >This is a deprecated parameter and will be removed in the next major release following version 2.2. Please see the instructions in the <A -HREF="printer_driver2.html" +HREF="printing.html" TARGET="_top" >Samba 2.2. Printing HOWTO</A @@ -15196,17 +15500,20 @@ CLASS="COMMAND" ><A NAME="PRINTERDRIVERFILE" ></A ->printer driver file (G)</DT +>>printer driver file (G)</DT ><DD ><P +><SPAN +CLASS="emphasis" ><I CLASS="EMPHASIS" >Note :</I +></SPAN >This is a deprecated parameter and will be removed in the next major release following version 2.2. Please see the instructions in the <A -HREF="printer_driver2.html" +HREF="printing.html" TARGET="_top" >Samba 2.2. Printing HOWTO</A @@ -15254,9 +15561,12 @@ CLASS="PARAMETER" ></A >.</P ><P ->Default: <I +>Default: <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >None (set in compile).</I +></SPAN ></P ><P >Example: <B @@ -15269,17 +15579,20 @@ CLASS="COMMAND" ><A NAME="PRINTERDRIVERLOCATION" ></A ->printer driver location (S)</DT +>>printer driver location (S)</DT ><DD ><P +><SPAN +CLASS="emphasis" ><I CLASS="EMPHASIS" >Note :</I +></SPAN >This is a deprecated parameter and will be removed in the next major release following version 2.2. Please see the instructions in the <A -HREF="printer_driver2.html" +HREF="printing.html" TARGET="_top" >Samba 2.2. Printing HOWTO</A @@ -15333,7 +15646,7 @@ CLASS="COMMAND" ><A NAME="PRINTERNAME" ></A ->printer name (S)</DT +>>printer name (S)</DT ><DD ><P >This parameter specifies the name of the printer @@ -15343,13 +15656,16 @@ NAME="PRINTERNAME" name given will be used for any printable service that does not have its own printer name specified.</P ><P ->Default: <I +>Default: <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >none (but may be <TT CLASS="CONSTANT" >lp</TT > on many systems)</I +></SPAN ></P ><P >Example: <B @@ -15361,7 +15677,7 @@ CLASS="COMMAND" ><A NAME="PRINTER" ></A ->printer (S)</DT +>>printer (S)</DT ><DD ><P >Synonym for <A @@ -15378,7 +15694,7 @@ CLASS="PARAMETER" ><A NAME="PRINTING" ></A ->printing (S)</DT +>>printing (S)</DT ><DD ><P >This parameters controls how printer status @@ -15458,7 +15774,7 @@ TARGET="_top" >This option can be set on a per printer basis</P ><P >See also the discussion in the <A -HREF="#AEN79" +HREF="#AEN80" > [printers]</A > section.</P ></DD @@ -15466,7 +15782,7 @@ HREF="#AEN79" ><A NAME="PRIVATEDIR" ></A ->private dir (G)</DT +>>private dir (G)</DT ><DD ><P >This parameters defines the directory @@ -15489,7 +15805,7 @@ CLASS="COMMAND" ><A NAME="PROTOCOL" ></A ->protocol (G)</DT +>>protocol (G)</DT ><DD ><P >Synonym for <A @@ -15506,7 +15822,7 @@ CLASS="PARAMETER" ><A NAME="PUBLIC" ></A ->public (S)</DT +>>public (S)</DT ><DD ><P >Synonym for <A @@ -15524,7 +15840,7 @@ CLASS="PARAMETER" ><A NAME="QUEUEPAUSECOMMAND" ></A ->queuepause command (S)</DT +>>queuepause command (S)</DT ><DD ><P >This parameter specifies the command to be @@ -15551,7 +15867,9 @@ CLASS="PARAMETER" path in the command as the PATH may not be available to the server.</P ><P ->Default: <I +>Default: <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >depends on the setting of <TT CLASS="PARAMETER" @@ -15560,6 +15878,7 @@ CLASS="PARAMETER" </I ></TT ></I +></SPAN ></P ><P >Example: <B @@ -15571,7 +15890,7 @@ CLASS="COMMAND" ><A NAME="QUEUERESUMECOMMAND" ></A ->queueresume command (S)</DT +>>queueresume command (S)</DT ><DD ><P >This parameter specifies the command to be @@ -15608,7 +15927,9 @@ CLASS="PARAMETER" path in the command as the PATH may not be available to the server.</P ><P ->Default: <I +>Default: <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >depends on the setting of <A HREF="#PRINTING" @@ -15619,6 +15940,7 @@ CLASS="PARAMETER" ></TT ></A ></I +></SPAN > </P ><P @@ -15632,7 +15954,7 @@ CLASS="COMMAND" ><A NAME="READBMPX" ></A ->read bmpx (G)</DT +>>read bmpx (G)</DT ><DD ><P >This boolean parameter controls whether <A @@ -15656,7 +15978,7 @@ CLASS="COMMAND" ><A NAME="READLIST" ></A ->read list (S)</DT +>>read list (S)</DT ><DD ><P >This is a list of users that are given read-only @@ -15702,7 +16024,7 @@ CLASS="PARAMETER" ><P >Default: <B CLASS="COMMAND" ->read list = <empty string></B +>read list = <empty string></B ></P ><P >Example: <B @@ -15714,7 +16036,7 @@ CLASS="COMMAND" ><A NAME="READONLY" ></A ->read only (S)</DT +>>read only (S)</DT ><DD ><P >An inverted synonym is <A @@ -15738,9 +16060,12 @@ CLASS="CONSTANT" CLASS="COMMAND" >printable = yes</B >) - will <I + will <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >ALWAYS</I +></SPAN > allow writing to the directory (user privileges permitting), but only via spooling operations.</P ><P @@ -15753,7 +16078,7 @@ CLASS="COMMAND" ><A NAME="READRAW" ></A ->read raw (G)</DT +>>read raw (G)</DT ><DD ><P >This parameter controls whether or not the server @@ -15788,7 +16113,7 @@ CLASS="COMMAND" ><A NAME="READSIZE" ></A ->read size (G)</DT +>>read size (G)</DT ><DD ><P >The option <TT @@ -15829,7 +16154,7 @@ CLASS="COMMAND" ><A NAME="REALM" ></A ->realm (G)</DT +>>realm (G)</DT ><DD ><P > This option specifies the kerberos realm to use. The realm is @@ -15854,7 +16179,7 @@ CLASS="COMMAND" ><A NAME="REMOTEANNOUNCE" ></A ->remote announce (G)</DT +>>remote announce (G)</DT ><DD ><P >This option allows you to setup <A @@ -15898,9 +16223,10 @@ CLASS="PARAMETER" addresses of the remote networks, but can also be the IP addresses of known browse masters if your network config is that stable.</P ><P ->See the documentation file <TT -CLASS="FILENAME" ->BROWSING.txt</TT +>See the documentation file <A +HREF="improved-browsing.html" +TARGET="_top" +>BROWSING</A > in the <TT CLASS="FILENAME" @@ -15909,7 +16235,7 @@ CLASS="FILENAME" ><P >Default: <B CLASS="COMMAND" ->remote announce = <empty string> +>remote announce = <empty string> </B ></P ></DD @@ -15917,7 +16243,7 @@ CLASS="COMMAND" ><A NAME="REMOTEBROWSESYNC" ></A ->remote browse sync (G)</DT +>>remote browse sync (G)</DT ><DD ><P >This option allows you to setup <A @@ -15959,7 +16285,7 @@ CLASS="COMMAND" ><P >Default: <B CLASS="COMMAND" ->remote browse sync = <empty string> +>remote browse sync = <empty string> </B ></P ></DD @@ -15967,7 +16293,7 @@ CLASS="COMMAND" ><A NAME="RESTRICTANONYMOUS" ></A ->restrict anonymous (G)</DT +>>restrict anonymous (G)</DT ><DD ><P >This is a integer parameter, and @@ -15987,7 +16313,7 @@ CLASS="COMMAND" ><A NAME="ROOT" ></A ->root (G)</DT +>>root (G)</DT ><DD ><P >Synonym for <A @@ -16004,7 +16330,7 @@ CLASS="PARAMETER" ><A NAME="ROOTDIR" ></A ->root dir (G)</DT +>>root dir (G)</DT ><DD ><P >Synonym for <A @@ -16021,7 +16347,7 @@ CLASS="PARAMETER" ><A NAME="ROOTDIRECTORY" ></A ->root directory (G)</DT +>>root directory (G)</DT ><DD ><P >The server will <B @@ -16058,9 +16384,12 @@ CLASS="PARAMETER" >root directory</I ></TT > - option, <I + option, <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >including</I +></SPAN > some files needed for complete operation of the server. To maintain full operability of the server you will need to mirror some system files @@ -16092,7 +16421,7 @@ CLASS="COMMAND" ><A NAME="ROOTPOSTEXEC" ></A ->root postexec (S)</DT +>>root postexec (S)</DT ><DD ><P >This is the same as the <TT @@ -16117,7 +16446,7 @@ CLASS="PARAMETER" ><P >Default: <B CLASS="COMMAND" ->root postexec = <empty string> +>root postexec = <empty string> </B ></P ></DD @@ -16125,7 +16454,7 @@ CLASS="COMMAND" ><A NAME="ROOTPREEXEC" ></A ->root preexec (S)</DT +>>root preexec (S)</DT ><DD ><P >This is the same as the <TT @@ -16158,7 +16487,7 @@ CLASS="PARAMETER" ><P >Default: <B CLASS="COMMAND" ->root preexec = <empty string> +>root preexec = <empty string> </B ></P ></DD @@ -16166,7 +16495,7 @@ CLASS="COMMAND" ><A NAME="ROOTPREEXECCLOSE" ></A ->root preexec close (S)</DT +>>root preexec close (S)</DT ><DD ><P >This is the same as the <TT @@ -16204,7 +16533,7 @@ CLASS="COMMAND" ><A NAME="SECURITY" ></A ->security (G)</DT +>>security (G)</DT ><DD ><P >This option affects how clients respond to @@ -16214,11 +16543,12 @@ CLASS="FILENAME" > file.</P ><P >The option sets the "security mode bit" in replies to - protocol negotiations with <A -HREF="smbd.8.html" -TARGET="_top" ->smbd(8) - </A + protocol negotiations with <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbd</SPAN +>(8)</SPAN > to turn share level security on or off. Clients decide based on this bit whether (and how) to transfer user and password information to the server.</P @@ -16293,9 +16623,12 @@ CLASS="PARAMETER" >It is possible to use <B CLASS="COMMAND" >smbd</B -> in a <I +> in a <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" > hybrid mode</I +></SPAN > where it is offers both user and share level security under different <A HREF="#NETBIOSALIASES" @@ -16312,10 +16645,13 @@ CLASS="PARAMETER" ><A NAME="SECURITYEQUALSSHARE" ></A +>><SPAN +CLASS="emphasis" ><I CLASS="EMPHASIS" >SECURITY = SHARE </I +></SPAN ></P ><P >When clients connect to a share level security server they @@ -16333,9 +16669,12 @@ CLASS="COMMAND" >Note that <B CLASS="COMMAND" >smbd</B -> <I +> <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >ALWAYS</I +></SPAN > uses a valid UNIX user to act on behalf of the client, even in <B @@ -16395,10 +16734,13 @@ CLASS="PARAMETER" ></LI ><LI ><P ->If the client did a previous <I +>If the client did a previous <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >logon </I +></SPAN > request (the SessionSetup SMB call) then the username sent in this SMB will be added as a potential username. </P @@ -16453,28 +16795,34 @@ CLASS="PARAMETER" >, then this guest user will be used, otherwise access is denied.</P ><P ->Note that it can be <I +>Note that it can be <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >very</I +></SPAN > confusing in share-level security as to which UNIX username will eventually be used in granting access.</P ><P >See also the section <A -HREF="#AEN238" +HREF="#AEN239" > NOTE ABOUT USERNAME/PASSWORD VALIDATION</A >.</P ><P ><A NAME="SECURITYEQUALSUSER" ></A +>><SPAN +CLASS="emphasis" ><I CLASS="EMPHASIS" >SECURITY = USER </I +></SPAN ></P ><P ->This is the default security setting in Samba 2.2. +>This is the default security setting in Samba 3.0. With user-level security a client must first "log-on" with a valid username and password (which can be mapped using the <A HREF="#USERNAMEMAP" @@ -16514,13 +16862,19 @@ CLASS="PARAMETER" may change the UNIX user to use on this connection, but only after the user has been successfully authenticated.</P ><P +><SPAN +CLASS="emphasis" ><I CLASS="EMPHASIS" >Note</I +></SPAN > that the name of the resource being - requested is <I + requested is <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >not</I +></SPAN > sent to the server until after the server has successfully authenticated the client. This is why guest shares don't work in user level security without allowing @@ -16545,62 +16899,87 @@ CLASS="PARAMETER" > parameter for details on doing this.</P ><P >See also the section <A -HREF="#AEN238" +HREF="#AEN239" > NOTE ABOUT USERNAME/PASSWORD VALIDATION</A >.</P ><P ><A -NAME="SECURITYEQUALSSERVER" +NAME="SECURITYEQUALSDOMAIN" ></A +>><SPAN +CLASS="emphasis" ><I CLASS="EMPHASIS" ->SECURITY = SERVER +>SECURITY = DOMAIN + </I +></SPAN ></P ><P ->In this mode Samba will try to validate the username/password - by passing it to another SMB server, such as an NT box. If this - fails it will revert to <B -CLASS="COMMAND" ->security = user</B ->, but note - that if encrypted passwords have been negotiated then Samba cannot - revert back to checking the UNIX password file, it must have a valid - <TT -CLASS="FILENAME" ->smbpasswd</TT -> file to check users against. See the - documentation file in the <TT -CLASS="FILENAME" ->docs/</TT -> directory - <TT -CLASS="FILENAME" ->ENCRYPTION.txt</TT -> for details on how to set this - up.</P +>This mode will only work correctly if <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>net</SPAN +>(8)</SPAN +> has been used to add this + machine into a Windows NT Domain. It expects the <A +HREF="#ENCRYPTPASSWORDS" +><TT +CLASS="PARAMETER" +><I +>encrypted passwords</I +></TT +> + </A +> parameter to be set to <TT +CLASS="CONSTANT" +>yes</TT +>. In this + mode Samba will try to validate the username/password by passing + it to a Windows NT Primary or Backup Domain Controller, in exactly + the same way that a Windows NT Server would do.</P ><P +><SPAN +CLASS="emphasis" ><I CLASS="EMPHASIS" >Note</I -> that from the client's point of - view <B +></SPAN +> that a valid UNIX user must still + exist as well as the account on the Domain Controller to allow + Samba to have a valid UNIX account to map file access to.</P +><P +><SPAN +CLASS="emphasis" +><I +CLASS="EMPHASIS" +>Note</I +></SPAN +> that from the client's point + of view <B CLASS="COMMAND" ->security = server</B +>security = domain</B > is the same as <B CLASS="COMMAND" -> security = user</B ->. It only affects how the server deals - with the authentication, it does not in any way affect what the - client sees.</P +>security = user + </B +>. It only affects how the server deals with the authentication, + it does not in any way affect what the client sees.</P ><P +><SPAN +CLASS="emphasis" ><I CLASS="EMPHASIS" >Note</I +></SPAN > that the name of the resource being - requested is <I + requested is <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >not</I +></SPAN > sent to the server until after the server has successfully authenticated the client. This is why guest shares don't work in user level security without allowing @@ -16625,7 +17004,7 @@ CLASS="PARAMETER" > parameter for details on doing this.</P ><P >See also the section <A -HREF="#AEN238" +HREF="#AEN239" > NOTE ABOUT USERNAME/PASSWORD VALIDATION</A >.</P ><P @@ -16650,20 +17029,24 @@ CLASS="PARAMETER" > parameter.</P ><P ><A -NAME="SECURITYEQUALSDOMAIN" +NAME="SECURITYEQUALSSERVER" ></A +>><SPAN +CLASS="emphasis" ><I CLASS="EMPHASIS" ->SECURITY = DOMAIN +>SECURITY = SERVER </I +></SPAN ></P ><P ->This mode will only work correctly if <A -HREF="smbpasswd.8.html" -TARGET="_top" ->smbpasswd(8)</A -> has been used to add this - machine into a Windows NT Domain. It expects the <A +>In this mode Samba will try to validate the username/password + by passing it to another SMB server, such as an NT box. If this + fails it will revert to <B +CLASS="COMMAND" +>security = + user</B +>. It expects the <A HREF="#ENCRYPTPASSWORDS" ><TT CLASS="PARAMETER" @@ -16672,42 +17055,76 @@ CLASS="PARAMETER" ></TT > </A -> parameter to be set to <TT +> parameter to be set to + <TT CLASS="CONSTANT" >yes</TT ->. In this - mode Samba will try to validate the username/password by passing - it to a Windows NT Primary or Backup Domain Controller, in exactly - the same way that a Windows NT Server would do.</P +>, unless the remote server + does not support them. However note + that if encrypted passwords have been negotiated then Samba cannot + revert back to checking the UNIX password file, it must have a valid + <TT +CLASS="FILENAME" +>smbpasswd</TT +> file to check users against. See the + documentation file in the <TT +CLASS="FILENAME" +>docs/</TT +> directory + <TT +CLASS="FILENAME" +>ENCRYPTION.txt</TT +> for details on how to set this + up.</P ><P +><SPAN +CLASS="emphasis" ><I CLASS="EMPHASIS" >Note</I -> that a valid UNIX user must still - exist as well as the account on the Domain Controller to allow - Samba to have a valid UNIX account to map file access to.</P -><P +></SPAN +> this mode of operation + has significant pitfalls, due to the fact that is + activly initiates a man-in-the-middle attack on the + remote SMB server. In particular, this mode of + operation can cause significant resource consuption on + the PDC, as it must maintain an active connection for + the duration of the user's session. Furthermore, if + this connection is lost, there is no way to + reestablish it, and futher authenticaions to the Samba + server may fail. (From a single client, till it + disconnects). </P +><P +><SPAN +CLASS="emphasis" ><I CLASS="EMPHASIS" >Note</I -> that from the client's point - of view <B +></SPAN +> that from the client's point of + view <B CLASS="COMMAND" ->security = domain</B +>security = server</B > is the same as <B CLASS="COMMAND" ->security = user - </B ->. It only affects how the server deals with the authentication, - it does not in any way affect what the client sees.</P +> security = user</B +>. It only affects how the server deals + with the authentication, it does not in any way affect what the + client sees.</P ><P +><SPAN +CLASS="emphasis" ><I CLASS="EMPHASIS" >Note</I +></SPAN > that the name of the resource being - requested is <I + requested is <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >not</I +></SPAN > sent to the server until after the server has successfully authenticated the client. This is why guest shares don't work in user level security without allowing @@ -16731,22 +17148,8 @@ CLASS="PARAMETER" </A > parameter for details on doing this.</P ><P -><I -CLASS="EMPHASIS" ->BUG:</I -> There is currently a bug in the - implementation of <B -CLASS="COMMAND" ->security = domain</B -> with respect - to multi-byte character set usernames. The communication with a - Domain Controller must be done in UNICODE and Samba currently - does not widen multi-byte user names to UNICODE correctly, thus - a multi-byte username will not be recognized correctly at the - Domain Controller. This issue will be addressed in a future release.</P -><P >See also the section <A -HREF="#AEN238" +HREF="#AEN239" > NOTE ABOUT USERNAME/PASSWORD VALIDATION</A >.</P ><P @@ -16784,7 +17187,7 @@ CLASS="COMMAND" ><A NAME="SECURITYMASK" ></A ->security mask (S)</DT +>>security mask (S)</DT ><DD ><P >This parameter controls what UNIX permission @@ -16802,9 +17205,12 @@ NAME="SECURITYMASK" a user to modify all the user/group/world permissions on a file. </P ><P +><SPAN +CLASS="emphasis" ><I CLASS="EMPHASIS" >Note</I +></SPAN > that users who can access the Samba server through other means can easily bypass this restriction, so it is primarily useful for standalone @@ -16856,7 +17262,7 @@ CLASS="COMMAND" ><A NAME="SERVERSTRING" ></A ->server string (G)</DT +>>server string (G)</DT ><DD ><P >This controls what string will show up in the @@ -16901,7 +17307,7 @@ CLASS="COMMAND" ><A NAME="SETDIRECTORY" ></A ->set directory (S)</DT +>>set directory (S)</DT ><DD ><P >If <B @@ -16927,7 +17333,7 @@ CLASS="COMMAND" ><A NAME="SHAREMODES" ></A ->share modes (S)</DT +>>share modes (S)</DT ><DD ><P >This enables or disables the honoring of @@ -16971,9 +17377,12 @@ CLASS="CONSTANT" >This option gives full share compatibility and enabled by default.</P ><P ->You should <I +>You should <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >NEVER</I +></SPAN > turn this parameter off as many Windows applications will break if you do so.</P ><P @@ -16986,7 +17395,7 @@ CLASS="COMMAND" ><A NAME="SHORTPRESERVECASE" ></A ->short preserve case (S)</DT +>>short preserve case (S)</DT ><DD ><P >This boolean parameter controls if new files @@ -17012,7 +17421,7 @@ CLASS="COMMAND" names are lowered. </P ><P >See the section on <A -HREF="#AEN205" +HREF="#AEN206" > NAME MANGLING</A >.</P ><P @@ -17025,7 +17434,7 @@ CLASS="COMMAND" ><A NAME="SHOWADDPRINTERWIZARD" ></A ->show add printer wizard (G)</DT +>>show add printer wizard (G)</DT ><DD ><P >With the introduction of MS-RPC based printing support @@ -17056,9 +17465,12 @@ CLASS="PARAMETER" ></TT > parameter will always cause the OpenPrinterEx() on the server - to fail. Thus the APW icon will never be displayed. <I + to fail. Thus the APW icon will never be displayed. <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" > Note :</I +></SPAN >This does not prevent the same user from having administrative privilege on an individual printer.</P ><P @@ -17098,12 +17510,15 @@ CLASS="COMMAND" ><A NAME="SHUTDOWNSCRIPT" ></A ->shutdown script (G)</DT +>>shutdown script (G)</DT ><DD ><P +><SPAN +CLASS="emphasis" ><I CLASS="EMPHASIS" >This parameter only exists in the HEAD cvs branch</I +></SPAN > This a full path name to a script called by <A @@ -17144,9 +17559,12 @@ CLASS="PARAMETER" >%r</I ></TT > will be substituted with the - switch <I + switch <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >-r</I +></SPAN >. It means reboot after shutdown for NT. </P @@ -17157,15 +17575,21 @@ CLASS="PARAMETER" >%f</I ></TT > will be substituted with the - switch <I + switch <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >-f</I +></SPAN >. It means force the shutdown even if applications do not respond for NT.</P ><P ->Default: <I +>Default: <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >None</I +></SPAN >.</P ><P >Example: <B @@ -17174,25 +17598,15 @@ CLASS="COMMAND" ></P ><P >Shutdown script example: - <TABLE -BORDER="0" -BGCOLOR="#E0E0E0" -WIDTH="90%" -><TR -><TD -><PRE +<PRE CLASS="PROGRAMLISTING" -> #!/bin/bash +>#!/bin/bash - $time=0 - let "time/60" - let "time++" +$time=0 +let "time/60" +let "time++" - /sbin/shutdown $3 $4 +$time $1 & - </PRE -></TD -></TR -></TABLE +/sbin/shutdown $3 $4 +$time $1 &</PRE > Shutdown does not return so we need to launch it in background. </P @@ -17211,7 +17625,7 @@ CLASS="PARAMETER" ><A NAME="SMBPASSWDFILE" ></A ->smb passwd file (G)</DT +>>smb passwd file (G)</DT ><DD ><P >This option sets the path to the encrypted @@ -17234,7 +17648,7 @@ CLASS="COMMAND" ><A NAME="SMBPORTS" ></A ->smb ports (G)</DT +>>smb ports (G)</DT ><DD ><P >Specifies which ports the server should listen on @@ -17250,7 +17664,7 @@ CLASS="COMMAND" ><A NAME="SOCKETADDRESS" ></A ->socket address (G)</DT +>>socket address (G)</DT ><DD ><P >This option allows you to control what @@ -17271,7 +17685,7 @@ CLASS="COMMAND" ><A NAME="SOCKETOPTIONS" ></A ->socket options (G)</DT +>>socket options (G)</DT ><DD ><P >This option allows you to set socket options @@ -17352,9 +17766,12 @@ TARGET="_top" ></LI ></UL ><P ->Those marked with a <I +>Those marked with a <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >'*'</I +></SPAN > take an integer argument. The others can optionally take a 1 or 0 argument to enable or disable the option, by default they will be enabled if you @@ -17402,7 +17819,7 @@ CLASS="COMMAND" ><A NAME="SOURCEENVIRONMENT" ></A ->source environment (G)</DT +>>source environment (G)</DT ><DD ><P >This parameter causes Samba to set environment @@ -17426,9 +17843,12 @@ CLASS="COMMAND" >SAMBA_NETBIOS_NAME = myhostname</B ></P ><P ->Default: <I +>Default: <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >No default value</I +></SPAN ></P ><P >Examples: <B @@ -17447,27 +17867,37 @@ CLASS="COMMAND" ><A NAME="SPNEGO" ></A ->use spnego (G)</DT +>>use spnego (G)</DT ><DD ><P -> This variable controls controls whether samba will try to use Simple and Protected NEGOciation (as specified by rfc2478) with WindowsXP and Windows2000sp2 clients to agree upon an authentication mechanism. As of samba 3.0alpha it must be set to "no" for these clients to join a samba domain controller. It can be set to "yes" to allow samba to participate in an AD domain controlled by a Windows2000 domain controller.</P +> This variable controls controls whether samba will try + to use Simple and Protected NEGOciation (as specified by rfc2478) with + WindowsXP and Windows2000sp2 clients to agree upon an authentication mechanism. + Unless further issues are discovered with our SPNEGO + implementation, there is no reason this should ever be + disabled.</P ><P ->Default: <I +>Default: <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >use spnego = yes</I +></SPAN ></P ></DD ><DT ><A NAME="STATCACHE" ></A ->stat cache (G)</DT +>>stat cache (G)</DT ><DD ><P ->This parameter determines if <A -HREF="smbd.8.html" -TARGET="_top" ->smbd(8)</A +>This parameter determines if <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbd</SPAN +>(8)</SPAN > will use a cache in order to speed up case insensitive name mappings. You should never need to change this parameter.</P @@ -17481,7 +17911,7 @@ CLASS="COMMAND" ><A NAME="STATCACHESIZE" ></A ->stat cache size (G)</DT +>>stat cache size (G)</DT ><DD ><P >This parameter determines the number of @@ -17502,7 +17932,7 @@ CLASS="COMMAND" ><A NAME="STRICTALLOCATE" ></A ->strict allocate (S)</DT +>>strict allocate (S)</DT ><DD ><P >This is a boolean that controls the handling of @@ -17539,7 +17969,7 @@ CLASS="COMMAND" ><A NAME="STRICTLOCKING" ></A ->strict locking (S)</DT +>>strict locking (S)</DT ><DD ><P >This is a boolean that controls the handling of @@ -17572,7 +18002,7 @@ CLASS="COMMAND" ><A NAME="STRICTSYNC" ></A ->strict sync (S)</DT +>>strict sync (S)</DT ><DD ><P >Many Windows applications (including the Windows @@ -17585,10 +18015,12 @@ NAME="STRICTSYNC" CLASS="CONSTANT" >no</TT > (the - default) means that <A -HREF="smbd.8.html" -TARGET="_top" ->smbd</A + default) means that <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbd</SPAN +>(8)</SPAN > ignores the Windows applications requests for a sync call. There is only a possibility of losing data if the operating system itself that Samba is running on crashes, so there is @@ -17616,7 +18048,7 @@ CLASS="COMMAND" ><A NAME="STRIPDOT" ></A ->strip dot (G)</DT +>>strip dot (G)</DT ><DD ><P >This is a boolean that controls whether to @@ -17632,7 +18064,7 @@ CLASS="COMMAND" ><A NAME="SYNCALWAYS" ></A ->sync always (S)</DT +>>sync always (S)</DT ><DD ><P >This is a boolean parameter that controls @@ -17683,7 +18115,7 @@ CLASS="COMMAND" ><A NAME="SYSLOG" ></A ->syslog (G)</DT +>>syslog (G)</DT ><DD ><P >This parameter maps how Samba debug messages @@ -17718,7 +18150,7 @@ CLASS="COMMAND" ><A NAME="SYSLOGONLY" ></A ->syslog only (G)</DT +>>syslog only (G)</DT ><DD ><P >If this parameter is set then Samba debug @@ -17734,7 +18166,7 @@ CLASS="COMMAND" ><A NAME="TEMPLATEHOMEDIR" ></A ->template homedir (G)</DT +>>template homedir (G)</DT ><DD ><P >When filling out the user information for a Windows NT @@ -17768,14 +18200,16 @@ CLASS="COMMAND" ><A NAME="TEMPLATESHELL" ></A ->template shell (G)</DT +>>template shell (G)</DT ><DD ><P >When filling out the user information for a Windows NT - user, the <A -HREF="winbindd.8.html" -TARGET="_top" ->winbindd(8)</A + user, the <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>winbindd</SPAN +>(8)</SPAN > daemon uses this parameter to fill in the login shell for that user.</P ><P @@ -17788,7 +18222,7 @@ CLASS="COMMAND" ><A NAME="TIMEOFFSET" ></A ->time offset (G)</DT +>>time offset (G)</DT ><DD ><P >This parameter is a setting in minutes to add @@ -17810,14 +18244,15 @@ CLASS="COMMAND" ><A NAME="TIMESERVER" ></A ->time server (G)</DT +>>time server (G)</DT ><DD ><P ->This parameter determines if <A -HREF="nmbd.8.html" -TARGET="_top" -> - nmbd(8)</A +>This parameter determines if <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>nmbd</SPAN +>(8)</SPAN > advertises itself as a time server to Windows clients.</P ><P @@ -17830,7 +18265,7 @@ CLASS="COMMAND" ><A NAME="TIMESTAMPLOGS" ></A ->timestamp logs (G)</DT +>>timestamp logs (G)</DT ><DD ><P >Synonym for <A @@ -17847,16 +18282,18 @@ CLASS="PARAMETER" ><A NAME="TOTALPRINTJOBS" ></A ->total print jobs (G)</DT +>>total print jobs (G)</DT ><DD ><P >This parameter accepts an integer value which defines a limit on the maximum number of print jobs that will be accepted system wide at any given time. If a print job is submitted - by a client which will exceed this number, then <A -HREF="smbd.8.html" -TARGET="_top" ->smbd</A + by a client which will exceed this number, then <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbd</SPAN +>(8)</SPAN > will return an error indicating that no space is available on the server. The default value of 0 means that no such limit exists. This parameter @@ -17887,7 +18324,7 @@ CLASS="COMMAND" ><A NAME="UNICODE" ></A ->unicode (G)</DT +>>unicode (G)</DT ><DD ><P >Specifies whether Samba should try @@ -17904,7 +18341,7 @@ CLASS="COMMAND" ><A NAME="UNIXCHARSET" ></A ->unix charset (G)</DT +>>unix charset (G)</DT ><DD ><P >Specifies the charset the unix machine @@ -17914,19 +18351,19 @@ NAME="UNIXCHARSET" ><P >Default: <B CLASS="COMMAND" ->unix charset = ASCII</B +>unix charset = UTF8</B ></P ><P >Example: <B CLASS="COMMAND" ->unix charset = UTF8</B +>unix charset = ASCII</B ></P ></DD ><DT ><A NAME="UNIXEXTENSIONS" ></A ->unix extensions(G)</DT +>>unix extensions(G)</DT ><DD ><P >This boolean parameter controls whether Samba @@ -17945,7 +18382,7 @@ CLASS="COMMAND" ><A NAME="UNIXPASSWORDSYNC" ></A ->unix password sync (G)</DT +>>unix password sync (G)</DT ><DD ><P >This boolean parameter controls whether Samba @@ -17960,9 +18397,12 @@ CLASS="PARAMETER" >passwd program</I ></TT ->parameter is called <I +>parameter is called <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >AS ROOT</I +></SPAN > - to allow the new UNIX password to be set without access to the old UNIX password (as the SMB password change code has no @@ -17996,7 +18436,7 @@ CLASS="COMMAND" ><A NAME="UPDATEENCRYPTED" ></A ->update encrypted (G)</DT +>>update encrypted (G)</DT ><DD ><P >This boolean parameter allows a user logging @@ -18051,7 +18491,7 @@ CLASS="COMMAND" ><A NAME="USECLIENTDRIVER" ></A ->use client driver (S)</DT +>>use client driver (S)</DT ><DD ><P >This parameter applies only to Windows NT/2000 @@ -18080,11 +18520,14 @@ CLASS="COMMAND" >If this parameter is enabled for a printer, then any attempt to open the printer with the PRINTER_ACCESS_ADMINISTER right is mapped to PRINTER_ACCESS_USE instead. Thus allowing the OpenPrinterEx() - call to succeed. <I + call to succeed. <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >This parameter MUST not be able enabled on a print share which has valid print driver installed on the Samba server.</I +></SPAN ></P ><P >See also <A @@ -18102,7 +18545,7 @@ CLASS="COMMAND" ><A NAME="USEMMAP" ></A ->use mmap (G)</DT +>>use mmap (G)</DT ><DD ><P >This global parameter determines if the tdb internals of Samba can @@ -18126,7 +18569,7 @@ CLASS="COMMAND" ><A NAME="USERHOSTS" ></A ->use rhosts (G)</DT +>>use rhosts (G)</DT ><DD ><P >If this global parameter is <TT @@ -18140,9 +18583,12 @@ CLASS="FILENAME" will be read to find the names of hosts and users who will be allowed access without specifying a password.</P ><P +><SPAN +CLASS="emphasis" ><I CLASS="EMPHASIS" >NOTE:</I +></SPAN > The use of <TT CLASS="PARAMETER" ><I @@ -18168,7 +18614,7 @@ CLASS="COMMAND" ><A NAME="USER" ></A ->user (S)</DT +>>user (S)</DT ><DD ><P >Synonym for <A @@ -18185,7 +18631,7 @@ CLASS="PARAMETER" ><A NAME="USERS" ></A ->users (S)</DT +>>users (S)</DT ><DD ><P >Synonym for <A @@ -18202,7 +18648,7 @@ CLASS="PARAMETER" ><A NAME="USERNAME" ></A ->username (S)</DT +>>username (S)</DT ><DD ><P >Multiple users may be specified in a comma-delimited @@ -18268,7 +18714,7 @@ CLASS="PARAMETER" will be looked up only in the UNIX groups database and will expand to a list of all users in the group of that name.</P ><P ->If any of the usernames begin with a '&'then the name +>If any of the usernames begin with a '&' then the name will be looked up only in the NIS netgroups database (if Samba is compiled with netgroup support) and will expand to a list of all users in the netgroup group of that name.</P @@ -18278,7 +18724,7 @@ CLASS="PARAMETER" search.</P ><P >See the section <A -HREF="#AEN238" +HREF="#AEN239" >NOTE ABOUT USERNAME/PASSWORD VALIDATION</A > for more information on how @@ -18287,7 +18733,7 @@ HREF="#AEN238" >Default: <B CLASS="COMMAND" >The guest account if a guest service, - else <empty string>.</B + else <empty string>.</B ></P ><P >Examples:<B @@ -18300,7 +18746,7 @@ CLASS="COMMAND" ><A NAME="USERNAMELEVEL" ></A ->username level (G)</DT +>>username level (G)</DT ><DD ><P >This option helps Samba to try and 'guess' at @@ -18334,7 +18780,7 @@ CLASS="COMMAND" ><A NAME="USERNAMEMAP" ></A ->username map (G)</DT +>>username map (G)</DT ><DD ><P >This option allows you to specify a file containing @@ -18424,20 +18870,10 @@ CLASS="COMMAND" '!' to tell Samba to stop processing if it gets a match on that line.</P ><P -><TABLE -BORDER="0" -BGCOLOR="#E0E0E0" -WIDTH="90%" -><TR -><TD ><PRE CLASS="PROGRAMLISTING" -> !sys = mary fred - guest = * - </PRE -></TD -></TR -></TABLE +>!sys = mary fred +guest = *</PRE ></P ><P >Note that the remapping is applied to all occurrences @@ -18474,9 +18910,12 @@ CLASS="PARAMETER" trouble deleting print jobs as PrintManager under WfWg will think they don't own the print job.</P ><P ->Default: <I +>Default: <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >no username map</I +></SPAN ></P ><P >Example: <B @@ -18489,7 +18928,7 @@ CLASS="COMMAND" ><A NAME="USESENDFILE" ></A ->use sendfile (S)</DT +>>use sendfile (S)</DT ><DD ><P >If this parameter is <TT @@ -18513,7 +18952,7 @@ CLASS="COMMAND" ><A NAME="UTMP" ></A ->utmp (G)</DT +>>utmp (G)</DT ><DD ><P >This boolean parameter is only available if @@ -18553,7 +18992,7 @@ CLASS="COMMAND" ><A NAME="UTMPDIRECTORY" ></A ->utmp directory(G)</DT +>>utmp directory(G)</DT ><DD ><P >This parameter is only available if Samba has @@ -18578,9 +19017,12 @@ CLASS="FILENAME" >/var/run/utmp</TT > on Linux).</P ><P ->Default: <I +>Default: <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >no utmp directory</I +></SPAN ></P ><P >Example: <B @@ -18592,7 +19034,7 @@ CLASS="COMMAND" ><A NAME="WTMPDIRECTORY" ></A ->wtmp directory(G)</DT +>>wtmp directory(G)</DT ><DD ><P >This parameter is only available if Samba has @@ -18621,9 +19063,12 @@ CLASS="FILENAME" >/var/run/wtmp</TT > on Linux).</P ><P ->Default: <I +>Default: <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >no wtmp directory</I +></SPAN ></P ><P >Example: <B @@ -18635,11 +19080,11 @@ CLASS="COMMAND" ><A NAME="VALIDUSERS" ></A ->valid users (S)</DT +>>valid users (S)</DT ><DD ><P >This is a list of users that should be allowed - to login to this service. Names starting with '@', '+' and '&' + to login to this service. Names starting with '@', '+' and '&' are interpreted using the same rules as described in the <TT CLASS="PARAMETER" @@ -18676,10 +19121,13 @@ CLASS="PARAMETER" ></A ></P ><P ->Default: <I +>Default: <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >No valid users list (anyone can login) </I +></SPAN ></P ><P >Example: <B @@ -18691,7 +19139,7 @@ CLASS="COMMAND" ><A NAME="VETOFILES" ></A ->veto files(S)</DT +>>veto files(S)</DT ><DD ><P >This is a list of files and directories that @@ -18701,9 +19149,12 @@ NAME="VETOFILES" or directories as in DOS wildcards.</P ><P >Each entry must be a unix path, not a DOS path and - must <I + must <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >not</I +></SPAN > include the unix directory separator '/'.</P ><P @@ -18719,9 +19170,12 @@ CLASS="PARAMETER" is important to be aware of is Samba's behaviour when trying to delete a directory. If a directory that is to be deleted contains nothing but veto files this - deletion will <I + deletion will <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >fail</I +></SPAN > unless you also set the <TT CLASS="PARAMETER" @@ -18759,19 +19213,16 @@ CLASS="PARAMETER" ></A >.</P ><P ->Default: <I +>Default: <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >No files or directories are vetoed. </I +></SPAN ></P ><P ->Examples:<TABLE -BORDER="0" -BGCOLOR="#E0E0E0" -WIDTH="90%" -><TR -><TD -><PRE +>Examples:<PRE CLASS="PROGRAMLISTING" >; Veto any files containing the word Security, ; any ending in .tmp, and any directory containing the @@ -18781,16 +19232,13 @@ veto files = /*Security*/*.tmp/*root*/ ; Veto the Apple specific files that a NetAtalk server ; creates. veto files = /.AppleDouble/.bin/.AppleDesktop/Network Trash Folder/</PRE -></TD -></TR -></TABLE ></P ></DD ><DT ><A NAME="VETOOPLOCKFILES" ></A ->veto oplock files (S)</DT +>>veto oplock files (S)</DT ><DD ><P >This parameter is only valid when the <A @@ -18816,10 +19264,13 @@ CLASS="PARAMETER" > parameter.</P ><P ->Default: <I +>Default: <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >No files are vetoed for oplock grants</I +></SPAN ></P ><P >You might want to do this on files that you know will @@ -18843,7 +19294,7 @@ CLASS="COMMAND" ><A NAME="VFSPATH" ></A ->vfs path (S)</DT +>>vfs path (S)</DT ><DD ><P >This parameter specifies the directory @@ -18868,7 +19319,7 @@ CLASS="COMMAND" ><A NAME="VFSOBJECT" ></A ->vfs object (S)</DT +>>vfs object (S)</DT ><DD ><P >This parameter specifies a shared object files that @@ -18876,16 +19327,19 @@ NAME="VFSOBJECT" disk I/O operations are used but these can be overloaded with one or more VFS objects. </P ><P ->Default : <I +>Default : <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >no value</I +></SPAN ></P ></DD ><DT ><A NAME="VFSOPTIONS" ></A ->vfs options (S)</DT +>>vfs options (S)</DT ><DD ><P >This parameter allows parameters to be passed @@ -18900,32 +19354,38 @@ CLASS="PARAMETER" ></A >.</P ><P ->Default : <I +>Default : <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >no value</I +></SPAN ></P ></DD ><DT ><A NAME="VOLUME" ></A ->volume (S)</DT +>>volume (S)</DT ><DD ><P > This allows you to override the volume label returned for a share. Useful for CDROMs with installation programs that insist on a particular volume label.</P ><P ->Default: <I +>Default: <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >the name of the share</I +></SPAN ></P ></DD ><DT ><A NAME="WIDELINKS" ></A ->wide links (S)</DT +>>wide links (S)</DT ><DD ><P >This parameter controls whether or not links @@ -18947,14 +19407,16 @@ CLASS="COMMAND" ><A NAME="WINBINDCACHETIME" ></A ->winbind cache time (G)</DT +>>winbind cache time (G)</DT ><DD ><P ->This parameter specifies the number of seconds the - <A -HREF="winbindd.8.html" -TARGET="_top" ->winbindd(8)</A +>This parameter specifies the number of + seconds the <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>winbindd</SPAN +>(8)</SPAN > daemon will cache user and group information before querying a Windows NT server again.</P @@ -18968,19 +19430,19 @@ CLASS="COMMAND" ><A NAME="WINBINDENUMUSERS" ></A ->winbind enum users (G)</DT +>>winbind enum users (G)</DT ><DD ><P ->On large installations using - <A -HREF="winbindd.8.html" -TARGET="_top" ->winbindd(8)</A +>On large installations using <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>winbindd</SPAN +>(8)</SPAN > it may be - necessary to suppress the enumeration of users through the - <B + necessary to suppress the enumeration of users through the <B CLASS="COMMAND" -> setpwent()</B +>setpwent()</B >, <B CLASS="COMMAND" @@ -19005,9 +19467,12 @@ CLASS="COMMAND" > system call will not return any data. </P ><P +><SPAN +CLASS="emphasis" ><I CLASS="EMPHASIS" >Warning:</I +></SPAN > Turning off user enumeration may cause some programs to behave oddly. For example, the finger program relies on having access to the @@ -19023,19 +19488,19 @@ CLASS="COMMAND" ><A NAME="WINBINDENUMGROUPS" ></A ->winbind enum groups (G)</DT +>>winbind enum groups (G)</DT ><DD ><P ->On large installations using - <A -HREF="winbindd.8.html" -TARGET="_top" ->winbindd(8)</A -> it may be - necessary to suppress the enumeration of groups through the - <B +>On large installations using <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>winbindd</SPAN +>(8)</SPAN +> it may be necessary to suppress + the enumeration of groups through the <B CLASS="COMMAND" -> setgrent()</B +>setgrent()</B >, <B CLASS="COMMAND" @@ -19060,9 +19525,12 @@ CLASS="COMMAND" > system call will not return any data. </P ><P +><SPAN +CLASS="emphasis" ><I CLASS="EMPHASIS" >Warning:</I +></SPAN > Turning off group enumeration may cause some programs to behave oddly. </P @@ -19077,21 +19545,23 @@ CLASS="COMMAND" ><A NAME="WINBINDGID" ></A ->winbind gid (G)</DT +>>winbind gid (G)</DT ><DD ><P >The winbind gid parameter specifies the range of group - ids that are allocated by the <A -HREF="winbindd.8.html" -TARGET="_top" -> winbindd(8)</A + ids that are allocated by the <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>winbindd</SPAN +>(8)</SPAN > daemon. This range of group ids should have no existing local or NIS groups within it as strange conflicts can occur otherwise.</P ><P >Default: <B CLASS="COMMAND" ->winbind gid = <empty string> +>winbind gid = <empty string> </B ></P ><P @@ -19104,7 +19574,7 @@ CLASS="COMMAND" ><A NAME="WINBINDSEPARATOR" ></A ->winbind separator (G)</DT +>>winbind separator (G)</DT ><DD ><P >This parameter allows an admin to define the character @@ -19148,21 +19618,23 @@ CLASS="COMMAND" ><A NAME="WINBINDUID" ></A ->winbind uid (G)</DT +>>winbind uid (G)</DT ><DD ><P >The winbind gid parameter specifies the range of group - ids that are allocated by the <A -HREF="winbindd.8.html" -TARGET="_top" -> winbindd(8)</A + ids that are allocated by the <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>winbindd</SPAN +>(8)</SPAN > daemon. This range of ids should have no existing local or NIS users within it as strange conflicts can occur otherwise.</P ><P >Default: <B CLASS="COMMAND" ->winbind uid = <empty string> +>winbind uid = <empty string> </B ></P ><P @@ -19172,25 +19644,27 @@ CLASS="COMMAND" ></P ></DD ><DT ->winbind use default domain, <A +><A NAME="WINBINDUSEDEFAULTDOMAIN" ></A ->winbind use default domain (G)</DT +>>winbind use default domain (G)</DT ><DD ><P ->This parameter specifies whether the <A -HREF="winbindd.8.html" -TARGET="_top" -> winbindd(8)</A -> - daemon should operate on users without domain component in their username. +>This parameter specifies whether the <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>winbindd</SPAN +>(8)</SPAN +> daemon should operate on users + without domain component in their username. Users without a domain component are treated as is part of the winbindd server's own domain. While this does not benifit Windows users, it makes SSH, FTP and e-mail function in a way much closer to the way they would in a native unix system.</P ><P >Default: <B CLASS="COMMAND" ->winbind use default domain = <no> +>winbind use default domain = <no> </B ></P ><P @@ -19203,7 +19677,7 @@ CLASS="COMMAND" ><A NAME="WINSHOOK" ></A ->wins hook (G)</DT +>>wins hook (G)</DT ><DD ><P >When Samba is running as a WINS server this @@ -19268,7 +19742,7 @@ CLASS="COMMAND" ><A NAME="WINSPROXY" ></A ->wins proxy (G)</DT +>>wins proxy (G)</DT ><DD ><P >This is a boolean that controls if <A @@ -19291,36 +19765,45 @@ CLASS="COMMAND" ><A NAME="WINSSERVER" ></A ->wins server (G)</DT +>>wins server (G)</DT ><DD ><P >This specifies the IP address (or DNS name: IP - address for preference) of the WINS server that <A -HREF="nmbd.8.html" -TARGET="_top" -> nmbd(8)</A + address for preference) of the WINS server that <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>nmbd</SPAN +>(8)</SPAN > should register with. If you have a WINS server on your network then you should set this to the WINS server's IP.</P ><P >You should point this at your WINS server if you have a multi-subnetted network.</P ><P +><SPAN +CLASS="emphasis" ><I CLASS="EMPHASIS" >NOTE</I +></SPAN >. You need to set up Samba to point to a WINS server if you have multiple subnets and wish cross-subnet browsing to work correctly.</P ><P ->See the documentation file <TT -CLASS="FILENAME" ->BROWSING.txt</TT +>See the documentation file <A +HREF="improved-browsing.html" +TARGET="_top" +>BROWSING</A > in the docs/ directory of your Samba source distribution.</P ><P ->Default: <I +>Default: <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >not enabled</I +></SPAN ></P ><P >Example: <B @@ -19332,14 +19815,15 @@ CLASS="COMMAND" ><A NAME="WINSSUPPORT" ></A ->wins support (G)</DT +>>wins support (G)</DT ><DD ><P ->This boolean controls if the <A -HREF="nmbd.8.html" -TARGET="_top" -> - nmbd(8)</A +>This boolean controls if the <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>nmbd</SPAN +>(8)</SPAN > process in Samba will act as a WINS server. You should not set this to <TT CLASS="CONSTANT" @@ -19349,9 +19833,12 @@ CLASS="CONSTANT" CLASS="COMMAND" >nmbd</B > to be your WINS server. - Note that you should <I + Note that you should <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >NEVER</I +></SPAN > set this to <TT CLASS="CONSTANT" >yes</TT @@ -19367,7 +19854,7 @@ CLASS="COMMAND" ><A NAME="WORKGROUP" ></A ->workgroup (G)</DT +>>workgroup (G)</DT ><DD ><P >This controls what workgroup your server will @@ -19381,9 +19868,12 @@ CLASS="COMMAND" > setting.</P ><P ->Default: <I +>Default: <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >set at compile time to WORKGROUP</I +></SPAN ></P ><P >Example: <B @@ -19395,7 +19885,7 @@ CLASS="COMMAND" ><A NAME="WRITABLE" ></A ->writable (S)</DT +>>writable (S)</DT ><DD ><P >Synonym for <A @@ -19412,14 +19902,17 @@ CLASS="PARAMETER" ><A NAME="WRITECACHESIZE" ></A ->write cache size (S)</DT +>>write cache size (S)</DT ><DD ><P >If this integer parameter is set to non-zero value, Samba will create an in-memory cache for each oplocked file - (it does <I + (it does <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >not</I +></SPAN > do this for non-oplocked files). All writes that the client does not request to be flushed directly to disk will be stored in this cache if possible. @@ -19453,7 +19946,7 @@ CLASS="COMMAND" ><A NAME="WRITELIST" ></A ->write list (S)</DT +>>write list (S)</DT ><DD ><P >This is a list of users that are given read-write @@ -19486,7 +19979,7 @@ CLASS="PARAMETER" ><P >Default: <B CLASS="COMMAND" ->write list = <empty string> +>write list = <empty string> </B ></P ><P @@ -19500,7 +19993,7 @@ CLASS="COMMAND" ><A NAME="WINSPARTNERS" ></A ->wins partners (G)</DT +>>wins partners (G)</DT ><DD ><P >A space separated list of partners' IP addresses for @@ -19524,7 +20017,7 @@ CLASS="COMMAND" ><A NAME="WRITEOK" ></A ->write ok (S)</DT +>>write ok (S)</DT ><DD ><P >Inverted synonym for <A @@ -19541,7 +20034,7 @@ CLASS="PARAMETER" ><A NAME="WRITERAW" ></A ->write raw (G)</DT +>>write raw (G)</DT ><DD ><P >This parameter controls whether or not the server @@ -19557,7 +20050,7 @@ CLASS="COMMAND" ><A NAME="WRITEABLE" ></A ->writeable (S)</DT +>>writeable (S)</DT ><DD ><P >Inverted synonym for <A @@ -19576,7 +20069,7 @@ CLASS="PARAMETER" ><DIV CLASS="REFSECT1" ><A -NAME="AEN6195" +NAME="AEN6323" ></A ><H2 >WARNINGS</H2 @@ -19587,11 +20080,12 @@ NAME="AEN6195" problem - but be aware of the possibility.</P ><P >On a similar note, many clients - especially DOS clients - - limit service names to eight characters. <A -HREF="smbd.8.html" -TARGET="_top" ->smbd(8) - </A + limit service names to eight characters. <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbd</SPAN +>(8)</SPAN > has no such limitation, but attempts to connect from such clients will fail if they truncate the service names. For this reason you should probably keep your service names down to eight characters @@ -19606,97 +20100,81 @@ TARGET="_top" ><DIV CLASS="REFSECT1" ><A -NAME="AEN6201" +NAME="AEN6331" ></A ><H2 >VERSION</H2 ><P ->This man page is correct for version 3.0 of - the Samba suite.</P +>This man page is correct for version 3.0 of the Samba suite.</P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN6204" +NAME="AEN6334" ></A ><H2 >SEE ALSO</H2 ><P -><A -HREF="samba.7.html" -TARGET="_top" ->samba(7)</A ->, - <A -HREF="smbpasswd.8.html" -TARGET="_top" -><B -CLASS="COMMAND" ->smbpasswd(8)</B -></A ->, - <A -HREF="swat.8.html" -TARGET="_top" -><B -CLASS="COMMAND" ->swat(8)</B -></A ->, - <A -HREF="smbd.8.html" -TARGET="_top" -><B -CLASS="COMMAND" ->smbd(8)</B -></A ->, - <A -HREF="nmbd.8.html" -TARGET="_top" -><B -CLASS="COMMAND" ->nmbd(8)</B -></A ->, - <A -HREF="smbclient.1.html" -TARGET="_top" -><B -CLASS="COMMAND" ->smbclient(1)</B -></A ->, - <A -HREF="nmblookup.1.html" -TARGET="_top" -><B -CLASS="COMMAND" ->nmblookup(1)</B -></A ->, - <A -HREF="testparm.1.html" -TARGET="_top" -><B -CLASS="COMMAND" ->testparm(1)</B -></A ->, - <A -HREF="testprns.1.html" -TARGET="_top" -><B -CLASS="COMMAND" ->testprns(1)</B -></A -> - </P +> <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>samba</SPAN +>(7)</SPAN +>, <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbpasswd</SPAN +>(8)</SPAN +>, <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>swat</SPAN +>(8)</SPAN +>, <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbd</SPAN +>(8)</SPAN +>, <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>nmbd</SPAN +>(8)</SPAN +>, <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbclient</SPAN +>(1)</SPAN +>, <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>nmblookup</SPAN +>(1)</SPAN +>, <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>testparm</SPAN +>(1)</SPAN +>, <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>testprns</SPAN +>(1)</SPAN +>.</P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN6224" +NAME="AEN6364" ></A ><H2 >AUTHOR</H2 @@ -19708,14 +20186,14 @@ NAME="AEN6224" ><P >The original Samba man pages were written by Karl Auer. The man page sources were converted to YODL format (another - excellent piece of Open Source software, available at - <A + excellent piece of Open Source software, available at <A HREF="ftp://ftp.icce.rug.nl/pub/unix/" TARGET="_top" > ftp://ftp.icce.rug.nl/pub/unix/</A >) and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for - Samba 2.2 was done by Gerald Carter</P + Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 + for Samba 3.0 was done by Alexander Bokovoy.</P ></DIV ></BODY ></HTML diff --git a/docs/htmldocs/smbcacls.1.html b/docs/htmldocs/smbcacls.1.html index e0425d481d..66dbf8d2f9 100644 --- a/docs/htmldocs/smbcacls.1.html +++ b/docs/htmldocs/smbcacls.1.html @@ -5,7 +5,7 @@ >smbcacls</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77"></HEAD +CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"></HEAD ><BODY CLASS="REFENTRY" BGCOLOR="#FFFFFF" @@ -15,7 +15,7 @@ VLINK="#840084" ALINK="#0000FF" ><H1 ><A -NAME="SMBCACLS" +NAME="SMBCACLS.1" ></A >smbcacls</H1 ><DIV @@ -47,10 +47,12 @@ NAME="AEN22" ><H2 >DESCRIPTION</H2 ><P ->This tool is part of the <A -HREF="samba.7.html" -TARGET="_top" -> Samba</A +>This tool is part of the <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>Samba</SPAN +>(7)</SPAN > suite.</P ><P >The <B @@ -62,7 +64,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN28" +NAME="AEN30" ></A ><H2 >OPTIONS</H2 @@ -117,9 +119,12 @@ CLASS="VARIABLELIST" >Specifies a username used to connect to the specified service. The username may be of the form "username" in which case the user is prompted to enter in a password and the - workgroup specified in the <TT -CLASS="FILENAME" ->smb.conf</TT + workgroup specified in the <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smb.conf</SPAN +>(5)</SPAN > file is used, or "username%password" or "DOMAIN\username%password" and the password and workgroup names are used as provided. </P @@ -182,7 +187,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN75" +NAME="AEN79" ></A ><H2 >ACL FORMAT</H2 @@ -196,8 +201,7 @@ CLASS="PROGRAMLISTING" REVISION:<revision number> OWNER:<sid or name> GROUP:<sid or name> -ACL:<sid or name>:<type>/<flags>/<mask> - </PRE +ACL:<sid or name>:<type>/<flags>/<mask></PRE ></P ><P >The revision of the ACL specifies the internal Windows @@ -211,34 +215,45 @@ ACL:<sid or name>:<type>/<flags>/<mask> the file or directory resides. </P ><P >ACLs specify permissions granted to the SID. This SID again - can be specified in CWS-1-x-y-z format or as a name in which case - it is resolved against the server on which the file or directory - resides. The type, flags and mask values determine the type of - access granted to the SID. </P + can be specified in CWS-1-x-y-z format or as a name in which case + it is resolved against the server on which the file or directory + resides. The type, flags and mask values determine the type of + access granted to the SID. </P ><P >The type can be either 0 or 1 corresponding to ALLOWED or - DENIED access to the SID. The flags values are generally - zero for file ACLs and either 9 or 2 for directory ACLs. Some - common flags are: </P + DENIED access to the SID. The flags values are generally + zero for file ACLs and either 9 or 2 for directory ACLs. Some + common flags are: </P ><P ></P ><UL ><LI ><P ->#define SEC_ACE_FLAG_OBJECT_INHERIT 0x1</P +><TT +CLASS="CONSTANT" +>#define SEC_ACE_FLAG_OBJECT_INHERIT 0x1</TT +></P ></LI ><LI ><P ->#define SEC_ACE_FLAG_CONTAINER_INHERIT 0x2</P +><TT +CLASS="CONSTANT" +>#define SEC_ACE_FLAG_CONTAINER_INHERIT 0x2</TT +></P ></LI ><LI ><P ->#define SEC_ACE_FLAG_NO_PROPAGATE_INHERIT 0x4 - </P +><TT +CLASS="CONSTANT" +>#define SEC_ACE_FLAG_NO_PROPAGATE_INHERIT 0x4</TT +></P ></LI ><LI ><P ->#define SEC_ACE_FLAG_INHERIT_ONLY 0x8</P +><TT +CLASS="CONSTANT" +>#define SEC_ACE_FLAG_INHERIT_ONLY 0x8</TT +></P ></LI ></UL ><P @@ -356,7 +371,7 @@ CLASS="EMPHASIS" ><DIV CLASS="REFSECT1" ><A -NAME="AEN125" +NAME="AEN133" ></A ><H2 >EXIT STATUS</H2 @@ -380,18 +395,17 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN131" +NAME="AEN139" ></A ><H2 >VERSION</H2 ><P ->This man page is correct for version 2.2 of - the Samba suite.</P +>This man page is correct for version 2.2 of the Samba suite.</P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN134" +NAME="AEN142" ></A ><H2 >AUTHOR</H2 @@ -408,7 +422,8 @@ CLASS="COMMAND" and Tim Potter.</P ><P >The conversion to DocBook for Samba 2.2 was done - by Gerald Carter</P + by Gerald Carter. The conversion to DocBook XML 4.2 for Samba 3.0 was done + by Alexander Bokovoy.</P ></DIV ></BODY ></HTML diff --git a/docs/htmldocs/smbclient.1.html b/docs/htmldocs/smbclient.1.html index ca8cafd312..8ae4f84fe3 100644 --- a/docs/htmldocs/smbclient.1.html +++ b/docs/htmldocs/smbclient.1.html @@ -5,7 +5,7 @@ >smbclient</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77"></HEAD +CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"></HEAD ><BODY CLASS="REFENTRY" BGCOLOR="#FFFFFF" @@ -15,7 +15,7 @@ VLINK="#840084" ALINK="#0000FF" ><H1 ><A -NAME="SMBCLIENT" +NAME="SMBCLIENT.1" ></A >smbclient</H1 ><DIV @@ -38,20 +38,22 @@ NAME="AEN8" ><B CLASS="COMMAND" >smbclient</B -> {servicename} [password] [-b <buffer size>] [-d debuglevel] [-D Directory] [-U username] [-W workgroup] [-M <netbios name>] [-m maxprotocol] [-A authfile] [-N] [-l logfile] [-L <netbios name>] [-I destinationIP] [-E] [-c <command string>] [-i scope] [-O <socket options>] [-p port] [-R <name resolve order>] [-s <smb config file>] [-T<c|x>IXFqgbNan]</P +> {servicename} [password] [-b <buffer size>] [-d debuglevel] [-D Directory] [-U username] [-W workgroup] [-M <netbios name>] [-m maxprotocol] [-A authfile] [-N] [-l logfile] [-L <netbios name>] [-I destinationIP] [-E] [-c <command string>] [-i scope] [-O <socket options>] [-p port] [-R <name resolve order>] [-s <smb config file>] [-T<c|x>IXFqgbNan] [-k]</P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN33" +NAME="AEN34" ></A ><H2 >DESCRIPTION</H2 ><P ->This tool is part of the <A -HREF="samba.7.html" -TARGET="_top" -> Samba</A +>This tool is part of the <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>Samba</SPAN +>(7)</SPAN > suite.</P ><P ><B @@ -59,9 +61,12 @@ CLASS="COMMAND" >smbclient</B > is a client that can 'talk' to an SMB/CIFS server. It offers an interface - similar to that of the ftp program (see <B -CLASS="COMMAND" ->ftp(1)</B + similar to that of the ftp program (see <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>ftp</SPAN +>(1)</SPAN >). Operations include things like getting files from the server to the local machine, putting files from the local machine to @@ -71,7 +76,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN40" +NAME="AEN45" ></A ><H2 >OPTIONS</H2 @@ -126,9 +131,13 @@ CLASS="PARAMETER" CLASS="COMMAND" >smbclient</B > or - using the name resolve order parameter in the <TT -CLASS="FILENAME" ->smb.conf</TT + using the name resolve order parameter in + the <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smb.conf</SPAN +>(5)</SPAN > file, allowing an administrator to change the order and methods by which server names are looked up. </P @@ -178,10 +187,13 @@ CLASS="PARAMETER" >-s smb.conf</DT ><DD ><P ->Specifies the location of the all important - <TT -CLASS="FILENAME" ->smb.conf</TT +>Specifies the location of the all + important <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smb.conf</SPAN +>(5)</SPAN > file. </P ></DD ><DT @@ -189,10 +201,14 @@ CLASS="FILENAME" ><DD ><P >TCP socket options to set on the client - socket. See the socket options parameter in the <TT -CLASS="FILENAME" -> smb.conf (5)</TT -> manpage for the list of valid + socket. See the socket options parameter in + the <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smb.conf</SPAN +>(5)</SPAN +> manual page for the list of valid options. </P ></DD ><DT @@ -205,7 +221,7 @@ CLASS="FILENAME" string of different name resolution options.</P ><P >The options are :"lmhosts", "host", "wins" and "bcast". They - cause names to be resolved as follows :</P + cause names to be resolved as follows:</P ><P ></P ><UL @@ -214,12 +230,15 @@ CLASS="FILENAME" ><TT CLASS="CONSTANT" >lmhosts</TT -> : Lookup an IP +>: Lookup an IP address in the Samba lmhosts file. If the line in lmhosts has - no name type attached to the NetBIOS name (see the <A -HREF="lmhosts.5.html" -TARGET="_top" ->lmhosts(5)</A + no name type attached to the NetBIOS name (see + the <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>lmhosts</SPAN +>(5)</SPAN > for details) then any name type matches for lookup.</P ></LI @@ -228,7 +247,7 @@ TARGET="_top" ><TT CLASS="CONSTANT" >host</TT -> : Do a standard host +>: Do a standard host name to IP address resolution, using the system <TT CLASS="FILENAME" >/etc/hosts @@ -248,7 +267,7 @@ CLASS="FILENAME" ><TT CLASS="CONSTANT" >wins</TT -> : Query a name with +>: Query a name with the IP address listed in the <TT CLASS="PARAMETER" ><I @@ -263,7 +282,7 @@ CLASS="PARAMETER" ><TT CLASS="CONSTANT" >bcast</TT -> : Do a broadcast on +>: Do a broadcast on each of the known local interfaces listed in the <TT CLASS="PARAMETER" @@ -278,9 +297,12 @@ CLASS="PARAMETER" ></UL ><P >If this parameter is not set then the name resolve order - defined in the <TT -CLASS="FILENAME" ->smb.conf</TT + defined in the <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smb.conf</SPAN +>(5)</SPAN > file parameter (name resolve order) will be used. </P ><P @@ -291,9 +313,12 @@ CLASS="PARAMETER" >name resolve order </I ></TT -> parameter of the <TT -CLASS="FILENAME" ->smb.conf</TT +> parameter of the <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smb.conf</SPAN +>(5)</SPAN > file the name resolution methods will be attempted in this order. </P ></DD @@ -343,9 +368,17 @@ CLASS="PARAMETER" > options useful, as they allow you to control the FROM and TO parts of the message. </P ><P ->See the message command parameter in the <TT -CLASS="FILENAME" -> smb.conf(5)</TT +>See the <TT +CLASS="PARAMETER" +><I +>message command</I +></TT +> parameter in the <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smb.conf</SPAN +>(5)</SPAN > for a description of how to handle incoming WinPopup messages in Samba. </P ><P @@ -614,8 +647,7 @@ CLASS="COMMAND" CLASS="PROGRAMLISTING" >username = <value> password = <value> -domain = <value> - </PRE +domain = <value></PRE ></P ><P >If the domain parameter is missing the current workgroup name @@ -690,12 +722,14 @@ CLASS="COMMAND" ><DD ><P >Override the default workgroup (domain) specified - in the workgroup parameter of the <TT -CLASS="FILENAME" ->smb.conf</TT -> - file for this connection. This may be needed to connect to some - servers. </P + in the workgroup parameter of the <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smb.conf</SPAN +>(5)</SPAN +> file for this connection. This may be + needed to connect to some servers. </P ></DD ><DT >-T tar options</DT @@ -905,7 +939,7 @@ CLASS="EMPHASIS" ></SPAN ></P ><P ->All file names can be given as DOS path names (with '\' +>All file names can be given as DOS path names (with '\\' as the component separator) or as UNIX path names (with '/' as the component separator). </P ><P @@ -1000,13 +1034,21 @@ CLASS="COMMAND" >-c 'print -'</B >. </P ></DD +><DT +>-k</DT +><DD +><P +> Try to authenticate with kerberos. Only useful in + an Active Directory environment. + </P +></DD ></DL ></DIV ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN310" +NAME="AEN336" ></A ><H2 >OPERATIONS</H2 @@ -1019,7 +1061,7 @@ CLASS="PROMPT" >smb:\> </TT ></P ><P ->The backslash ("\") indicates the current working directory +>The backslash ("\\") indicates the current working directory on the server, and will change if the current working directory is changed. </P ><P @@ -1496,7 +1538,7 @@ CLASS="REPLACEABLE" ><DIV CLASS="REFSECT1" ><A -NAME="AEN501" +NAME="AEN527" ></A ><H2 >NOTES</H2 @@ -1517,7 +1559,7 @@ NAME="AEN501" ><DIV CLASS="REFSECT1" ><A -NAME="AEN506" +NAME="AEN532" ></A ><H2 >ENVIRONMENT VARIABLES</H2 @@ -1550,7 +1592,7 @@ CLASS="ENVAR" ><DIV CLASS="REFSECT1" ><A -NAME="AEN514" +NAME="AEN540" ></A ><H2 >INSTALLATION</H2 @@ -1581,10 +1623,12 @@ CLASS="EMPHASIS" and writeable only by the user. </P ><P >To test the client, you will need to know the name of a - running SMB/CIFS server. It is possible to run <B -CLASS="COMMAND" ->smbd(8) - </B + running SMB/CIFS server. It is possible to run <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbd</SPAN +>(8)</SPAN > as an ordinary user - running that server as a daemon on a user-accessible port (typically any port number over 1024) would provide a suitable test server. </P @@ -1592,7 +1636,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN524" +NAME="AEN552" ></A ><H2 >DIAGNOSTICS</H2 @@ -1608,18 +1652,17 @@ NAME="AEN524" ><DIV CLASS="REFSECT1" ><A -NAME="AEN528" +NAME="AEN556" ></A ><H2 >VERSION</H2 ><P ->This man page is correct for version 2.2 of - the Samba suite.</P +>This man page is correct for version 2.2 of the Samba suite.</P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN531" +NAME="AEN559" ></A ><H2 >AUTHOR</H2 @@ -1631,14 +1674,14 @@ NAME="AEN531" ><P >The original Samba man pages were written by Karl Auer. The man page sources were converted to YODL format (another - excellent piece of Open Source software, available at - <A + excellent piece of Open Source software, available at <A HREF="ftp://ftp.icce.rug.nl/pub/unix/" TARGET="_top" > ftp://ftp.icce.rug.nl/pub/unix/</A >) and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for - Samba 2.2 was done by Gerald Carter</P + Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 for Samba 3.0 + was done by Alexander Bokovoy.</P ></DIV ></BODY ></HTML diff --git a/docs/htmldocs/smbcontrol.1.html b/docs/htmldocs/smbcontrol.1.html index 12662dcc04..25c8e33e08 100644 --- a/docs/htmldocs/smbcontrol.1.html +++ b/docs/htmldocs/smbcontrol.1.html @@ -5,7 +5,7 @@ >smbcontrol</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77"></HEAD +CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"></HEAD ><BODY CLASS="REFENTRY" BGCOLOR="#FFFFFF" @@ -15,7 +15,7 @@ VLINK="#840084" ALINK="#0000FF" ><H1 ><A -NAME="SMBCONTROL" +NAME="SMBCONTROL.1" ></A >smbcontrol</H1 ><DIV @@ -52,37 +52,42 @@ NAME="AEN17" ><H2 >DESCRIPTION</H2 ><P ->This tool is part of the <A -HREF="samba.7.html" -TARGET="_top" -> Samba</A +>This tool is part of the <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>Samba</SPAN +>(7)</SPAN > suite.</P ><P ><B CLASS="COMMAND" >smbcontrol</B > is a very small program, which - sends messages to an <A -HREF="smbd.8.html" -TARGET="_top" ->smbd(8)</A ->, - an <A -HREF="nmbd.8.html" -TARGET="_top" ->nmbd(8)</A -> - or a <A -HREF="winbindd.8.html" -TARGET="_top" ->winbindd(8)</A -> - daemon running on the system.</P + sends messages to a <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbd</SPAN +>(8)</SPAN +>, a <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>nmbd</SPAN +>(8)</SPAN +>, or a <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>winbindd</SPAN +>(8)</SPAN +> daemon running on the system.</P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN26" +NAME="AEN34" ></A ><H2 >OPTIONS</H2 @@ -109,8 +114,7 @@ CLASS="PARAMETER" ><I >nmbd</I ></TT -> - <TT +>, <TT CLASS="PARAMETER" ><I >smbd</I @@ -322,7 +326,7 @@ CLASS="CONSTANT" ><DIV CLASS="REFSECT1" ><A -NAME="AEN102" +NAME="AEN110" ></A ><H2 >VERSION</H2 @@ -333,33 +337,29 @@ NAME="AEN102" ><DIV CLASS="REFSECT1" ><A -NAME="AEN105" +NAME="AEN113" ></A ><H2 >SEE ALSO</H2 ><P -><A -HREF="nmbd.8.html" -TARGET="_top" -><B -CLASS="COMMAND" ->nmbd(8)</B -></A ->, - and <A -HREF="smbd.8.html" -TARGET="_top" -><B -CLASS="COMMAND" ->smbd(8)</B -></A ->. - </P +><SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>nmbd</SPAN +>(8)</SPAN +> and <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbd</SPAN +>(8)</SPAN +>.</P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN112" +NAME="AEN122" ></A ><H2 >AUTHOR</H2 @@ -371,14 +371,14 @@ NAME="AEN112" ><P >The original Samba man pages were written by Karl Auer. The man page sources were converted to YODL format (another - excellent piece of Open Source software, available at - <A + excellent piece of Open Source software, available at <A HREF="ftp://ftp.icce.rug.nl/pub/unix/" TARGET="_top" > ftp://ftp.icce.rug.nl/pub/unix/</A >) and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for - Samba 2.2 was done by Gerald Carter</P + Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 for + Samba 3.0 was done by Alexander Bokovoy.</P ></DIV ></BODY ></HTML diff --git a/docs/htmldocs/smbd.8.html b/docs/htmldocs/smbd.8.html index 65f5f95b8d..47788cdb36 100644 --- a/docs/htmldocs/smbd.8.html +++ b/docs/htmldocs/smbd.8.html @@ -1,12 +1,11 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"> +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <HTML ><HEAD ><TITLE >smbd</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ -"></HEAD +CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"></HEAD ><BODY CLASS="REFENTRY" BGCOLOR="#FFFFFF" @@ -16,7 +15,9 @@ VLINK="#840084" ALINK="#0000FF" ><H1 ><A -NAME="SMBD">smbd</H1 +NAME="SMBD.8" +></A +>smbd</H1 ><DIV CLASS="REFNAMEDIV" ><A @@ -28,13 +29,15 @@ NAME="AEN5" ><DIV CLASS="REFSYNOPSISDIV" ><A -NAME="AEN8"><H2 +NAME="AEN8" +></A +><H2 >Synopsis</H2 ><P ><B CLASS="COMMAND" >smbd</B -> [-D] [-F] [-S] [-i] [-h] [-V] [-b] [-d <debug level>] [-l <log directory>] [-p <port number>] [-O <socket option>] [-s <configuration file>]</P +> [-D] [-F] [-S] [-i] [-h] [-V] [-b] [-d <debug level>] [-l <log directory>] [-p <port number>] [-O <socket option>] [-s <configuration file>]</P ></DIV ><DIV CLASS="REFSECT1" @@ -44,7 +47,13 @@ NAME="AEN23" ><H2 >DESCRIPTION</H2 ><P ->This program is part of the Samba suite.</P +>This program is part of the <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>Samba</SPAN +>(7)</SPAN +> suite.</P ><P ><B CLASS="COMMAND" @@ -61,28 +70,24 @@ CLASS="COMMAND" >An extensive description of the services that the server can provide is given in the man page for the configuration file controlling the attributes of those - services (see <A -HREF="smb.conf.5.html" -TARGET="_top" -><TT -CLASS="FILENAME" ->smb.conf(5) - </TT -></A + services (see <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smb.conf</SPAN +>(5)</SPAN >. This man page will not describe the services, but will concentrate on the administrative aspects of running the server.</P ><P >Please note that there are significant security - implications to running this server, and the <A -HREF="smb.conf.5.html" -TARGET="_top" -><TT -CLASS="FILENAME" ->smb.conf(5)</TT -></A -> - manpage should be regarded as mandatory reading before + implications to running this server, and the <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smb.conf</SPAN +>(5)</SPAN +> manual page should be regarded as mandatory reading before proceeding with installation.</P ><P >A session is created whenever a client requests one. @@ -104,7 +109,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN37" +NAME="AEN42" ></A ><H2 >OPTIONS</H2 @@ -222,7 +227,7 @@ CLASS="COMMAND" Samba was built.</P ></DD ><DT ->-d <debug level></DT +>-d <debug level></DT ><DD ><P ><TT @@ -251,19 +256,23 @@ CLASS="REPLACEABLE" override the <A HREF="smb.conf.5.html#loglevel" TARGET="_top" +><TT +CLASS="PARAMETER" +><I >log - level</A -> parameter in the <A -HREF="smb.conf.5.html" -TARGET="_top" -> <TT -CLASS="FILENAME" ->smb.conf(5)</TT + level</I +></TT ></A +> parameter in the <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smb.conf</SPAN +>(5)</SPAN > file.</P ></DD ><DT ->-l <log directory></DT +>-l <log directory></DT ><DD ><P >If specified, @@ -280,18 +289,25 @@ CLASS="REPLACEABLE" its size may be controlled by the <A HREF="smb.conf.5.html#maxlogsize" TARGET="_top" ->max log size</A -> - option in the <A -HREF="smb.conf.5.html" -TARGET="_top" ><TT -CLASS="FILENAME" -> smb.conf(5)</TT +CLASS="PARAMETER" +><I +>max log size</I +></TT ></A -> file. <I +> + option in the <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smb.conf</SPAN +>(5)</SPAN +> file. <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >Beware:</I +></SPAN > If the directory specified does not exist, <B CLASS="COMMAND" @@ -304,26 +320,29 @@ CLASS="COMMAND" compile time.</P ></DD ><DT ->-O <socket options></DT +>-O <socket options></DT ><DD ><P >See the <A HREF="smb.conf.5.html#socketoptions" TARGET="_top" ->socket options</A -> - parameter in the <A -HREF="smb.conf.5.html" -TARGET="_top" ><TT -CLASS="FILENAME" ->smb.conf(5) - </TT +CLASS="PARAMETER" +><I +>socket options</I +></TT ></A +> + parameter in the <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smb.conf</SPAN +>(5)</SPAN > file for details.</P ></DD ><DT ->-p <port number></DT +>-p <port number></DT ><DD ><P ><TT @@ -354,7 +373,7 @@ CLASS="REPLACEABLE" in the above situation.</P ></DD ><DT ->-s <configuration file></DT +>-s <configuration file></DT ><DD ><P >The file specified contains the @@ -362,13 +381,12 @@ CLASS="REPLACEABLE" information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is - to provide. See <A -HREF="smb.conf.5.html" -TARGET="_top" -><TT -CLASS="FILENAME" -> smb.conf(5)</TT -></A + to provide. See <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smb.conf</SPAN +>(5)</SPAN > for more information. The default configuration file name is determined at compile time.</P @@ -379,7 +397,7 @@ CLASS="FILENAME" ><DIV CLASS="REFSECT1" ><A -NAME="AEN123" +NAME="AEN135" ></A ><H2 >FILES</H2 @@ -402,9 +420,9 @@ CLASS="COMMAND" > meta-daemon, this file must contain suitable startup information for the meta-daemon. See the <A -HREF="UNIX_INSTALL.html" +HREF="install.html" TARGET="_top" ->UNIX_INSTALL.html</A +>"How to Install and Test SAMBA"</A > document for details. </P @@ -422,9 +440,9 @@ CLASS="FILENAME" >If running the server as a daemon at startup, this file will need to contain an appropriate startup sequence for the server. See the <A -HREF="UNIX_INSTALL.html" +HREF="install.html" TARGET="_top" ->UNIX_INSTALL.html</A +>"How to Install and Test SAMBA"</A > document for details.</P ></DD @@ -443,9 +461,9 @@ CLASS="COMMAND" must contain a mapping of service name (e.g., netbios-ssn) to service port (e.g., 139) and protocol type (e.g., tcp). See the <A -HREF="UNIX_INSTALL.html" +HREF="install.html" TARGET="_top" ->UNIX_INSTALL.html</A +>"How to Install and Test SAMBA"</A > document for details.</P ></DD @@ -456,34 +474,30 @@ CLASS="FILENAME" ></DT ><DD ><P ->This is the default location of the - <A -HREF="smb.conf.5.html" -TARGET="_top" -><TT -CLASS="FILENAME" ->smb.conf</TT -></A -> - server configuration file. Other common places that systems +>This is the default location of the <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smb.conf</SPAN +>(5)</SPAN +> server configuration file. Other common places that systems install this file are <TT CLASS="FILENAME" >/usr/samba/lib/smb.conf</TT > and <TT CLASS="FILENAME" ->/etc/smb.conf</TT +>/etc/samba/smb.conf</TT >.</P ><P >This file describes all the services the server - is to make available to clients. See <A -HREF="smb.conf.5.html" -TARGET="_top" -> <TT -CLASS="FILENAME" ->smb.conf(5)</TT -></A -> for more information.</P + is to make available to clients. See <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smb.conf</SPAN +>(5)</SPAN +> for more information.</P ></DD ></DL ></DIV @@ -491,7 +505,7 @@ CLASS="FILENAME" ><DIV CLASS="REFSECT1" ><A -NAME="AEN159" +NAME="AEN173" ></A ><H2 >LIMITATIONS</H2 @@ -510,7 +524,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN163" +NAME="AEN177" ></A ><H2 >ENVIRONMENT VARIABLES</H2 @@ -541,7 +555,7 @@ CLASS="CONSTANT" ><DIV CLASS="REFSECT1" ><A -NAME="AEN172" +NAME="AEN186" ></A ><H2 >PAM INTERACTION</H2 @@ -549,22 +563,35 @@ NAME="AEN172" >Samba uses PAM for authentication (when presented with a plaintext password), for account checking (is this account disabled?) and for session management. The degree too which samba supports PAM is restricted - by the limitations of the SMB protocol and the - <A + by the limitations of the SMB protocol and the <A HREF="smb.conf.5.html#OBEYPAMRESRICTIONS" TARGET="_top" ->obey pam restricions</A -> - smb.conf paramater. When this is set, the following restrictions apply: +><TT +CLASS="PARAMETER" +><I +>obey + pam restricions</I +></TT +></A +> <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smb.conf</SPAN +>(5)</SPAN +> paramater. When this is set, the following restrictions apply: </P ><P ></P ><UL ><LI ><P +><SPAN +CLASS="emphasis" ><I CLASS="EMPHASIS" >Account Validation</I +></SPAN >: All accesses to a samba server are checked against PAM to see if the account is vaild, not disabled and is permitted to @@ -573,9 +600,12 @@ CLASS="EMPHASIS" ></LI ><LI ><P +><SPAN +CLASS="emphasis" ><I CLASS="EMPHASIS" >Session Management</I +></SPAN >: When not using share level secuirty, users must pass PAM's session checks before access is granted. Note however, that this is bypassed in share level secuirty. @@ -588,7 +618,7 @@ CLASS="EMPHASIS" ><DIV CLASS="REFSECT1" ><A -NAME="AEN183" +NAME="AEN201" ></A ><H2 >VERSION</H2 @@ -599,7 +629,7 @@ NAME="AEN183" ><DIV CLASS="REFSECT1" ><A -NAME="AEN186" +NAME="AEN204" ></A ><H2 >DIAGNOSTICS</H2 @@ -622,7 +652,7 @@ NAME="AEN186" ><DIV CLASS="REFSECT1" ><A -NAME="AEN191" +NAME="AEN209" ></A ><H2 >SIGNALS</H2 @@ -644,9 +674,12 @@ CLASS="COMMAND" that <B CLASS="COMMAND" >SIGKILL (-9)</B -> <I +> <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >NOT</I +></SPAN > be used, except as a last resort, as this may leave the shared memory area in an inconsistent state. The safe way to terminate @@ -660,16 +693,14 @@ CLASS="COMMAND" CLASS="COMMAND" >smbd</B > may be raised - or lowered using <A -HREF="smbcontrol.1.html" -TARGET="_top" -><B -CLASS="COMMAND" ->smbcontrol(1) - </B -></A -> program (SIGUSR[1|2] signals are no longer used in - Samba 2.2). This is to allow transient problems to be diagnosed, + or lowered using <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbcontrol</SPAN +>(1)</SPAN +> program (SIGUSR[1|2] signals are no longer + used since Samba 2.2). This is to allow transient problems to be diagnosed, whilst still running at a normally low log level.</P ><P >Note that as the signal handlers send a debug write, @@ -688,55 +719,55 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN208" +NAME="AEN227" ></A ><H2 >SEE ALSO</H2 ><P ->hosts_access(5), <B -CLASS="COMMAND" ->inetd(8)</B ->, - <A -HREF="nmbd.8.html" -TARGET="_top" -><B -CLASS="COMMAND" ->nmbd(8)</B -></A ->, - <A -HREF="smb.conf.5.html" -TARGET="_top" -><TT -CLASS="FILENAME" ->smb.conf(5)</TT -> - </A ->, <A -HREF="smbclient.1.html" -TARGET="_top" -><B -CLASS="COMMAND" ->smbclient(1) - </B -></A ->, <A -HREF="testparm.1.html" -TARGET="_top" -><B -CLASS="COMMAND" -> testparm(1)</B -></A ->, <A -HREF="testprns.1.html" -TARGET="_top" -> <B -CLASS="COMMAND" ->testprns(1)</B -></A ->, and the Internet RFC's - <TT +><SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>hosts_access</SPAN +>(5)</SPAN +>, <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>inetd</SPAN +>(8)</SPAN +>, <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>nmbd</SPAN +>(8)</SPAN +>, <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smb.conf</SPAN +>(5)</SPAN +>, <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbclient</SPAN +>(1)</SPAN +>, <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>testparm</SPAN +>(1)</SPAN +>, <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>testprns</SPAN +>(1)</SPAN +>, and the + Internet RFC's <TT CLASS="FILENAME" >rfc1001.txt</TT >, <TT @@ -754,7 +785,7 @@ TARGET="_top" ><DIV CLASS="REFSECT1" ><A -NAME="AEN225" +NAME="AEN254" ></A ><H2 >AUTHOR</H2 @@ -766,14 +797,14 @@ NAME="AEN225" ><P >The original Samba man pages were written by Karl Auer. The man page sources were converted to YODL format (another - excellent piece of Open Source software, available at - <A + excellent piece of Open Source software, available at <A HREF="ftp://ftp.icce.rug.nl/pub/unix/" TARGET="_top" > ftp://ftp.icce.rug.nl/pub/unix/</A >) and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for - Samba 2.2 was done by Gerald Carter</P + Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 for + Samba 3.0 was done by Alexander Bokovoy.</P ></DIV ></BODY ></HTML diff --git a/docs/htmldocs/smbgroupedit.8.html b/docs/htmldocs/smbgroupedit.8.html index e20b34883c..856c778cb4 100644 --- a/docs/htmldocs/smbgroupedit.8.html +++ b/docs/htmldocs/smbgroupedit.8.html @@ -1,12 +1,11 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"> +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <HTML ><HEAD ><TITLE >smbgroupedit</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ -"></HEAD +CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"></HEAD ><BODY CLASS="REFENTRY" BGCOLOR="#FFFFFF" @@ -16,7 +15,9 @@ VLINK="#840084" ALINK="#0000FF" ><H1 ><A -NAME="SMBGROUPEDIT">smbgroupedit</H1 +NAME="SMBGROUPEDIT.8" +></A +>smbgroupedit</H1 ><DIV CLASS="REFNAMEDIV" ><A @@ -28,13 +29,15 @@ NAME="AEN5" ><DIV CLASS="REFSYNOPSISDIV" ><A -NAME="AEN8"><H2 +NAME="AEN8" +></A +><H2 >Synopsis</H2 ><P ><B CLASS="COMMAND" >smbroupedit</B -> [-v [l|s]] [-a UNIX-groupname [-d NT-groupname|-p privilege|]]</P +> [-v [l|s]] [-a UNIX-groupname [-d NT-groupname|-p privilege|]]</P ></DIV ><DIV CLASS="REFSECT1" @@ -44,12 +47,13 @@ NAME="AEN13" ><H2 >DESCRIPTION</H2 ><P ->This program is part of the <A -HREF="samba.7.html" -TARGET="_top" ->Samba</A -> -suite.</P +>This program is part of the <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>Samba</SPAN +>(7)</SPAN +> suite.</P ><P >The smbgroupedit command allows for mapping unix groups to NT Builtin, Domain, or Local groups. Also @@ -59,7 +63,7 @@ etc.</P ><DIV CLASS="REFSECT1" ><A -NAME="AEN18" +NAME="AEN20" ></A ><H2 >OPTIONS</H2 @@ -86,12 +90,6 @@ CLASS="VARIABLELIST" ><P >give a long listing, of the format:</P ><P -><TABLE -BORDER="0" -BGCOLOR="#E0E0E0" -WIDTH="90%" -><TR -><TD ><PRE CLASS="PROGRAMLISTING" >"NT Group Name" @@ -100,20 +98,10 @@ CLASS="PROGRAMLISTING" Group type : Comment : Privilege :</PRE -></TD -></TR -></TABLE ></P ><P ->For examples,</P -><P -><TABLE -BORDER="0" -BGCOLOR="#E0E0E0" -WIDTH="90%" -><TR -><TD -><PRE +>For example: +<PRE CLASS="PROGRAMLISTING" >Users SID : S-1-5-32-545 @@ -121,9 +109,6 @@ CLASS="PROGRAMLISTING" Group type: Local group Comment : Privilege : No privilege</PRE -></TD -></TR -></TABLE ></P ></DD ><DT @@ -132,34 +117,15 @@ CLASS="PROGRAMLISTING" ><P >display a short listing of the format:</P ><P -><TABLE -BORDER="0" -BGCOLOR="#E0E0E0" -WIDTH="90%" -><TR -><TD ><PRE CLASS="PROGRAMLISTING" >NTGroupName(SID) -> UnixGroupName</PRE -></TD -></TR -></TABLE ></P ><P ->For example,</P -><P -><TABLE -BORDER="0" -BGCOLOR="#E0E0E0" -WIDTH="90%" -><TR -><TD -><PRE +>For example: +<PRE CLASS="PROGRAMLISTING" >Users (S-1-5-32-545) -> -1</PRE -></TD -></TR -></TABLE ></P ></DD ></DL @@ -233,23 +199,15 @@ CLASS="FILENAME" ></LI ><LI ><P ->map this domadm group to the 'domain admins' group: - </P +>map this domadm group to the 'domain admins' group:</P ><P ></P ><OL TYPE="a" ><LI ><P ->Get the SID for the Windows NT "Domain Admins" - group:</P +>Get the SID for the Windows NT "Domain Admins" group:</P ><P -><TABLE -BORDER="0" -BGCOLOR="#E0E0E0" -WIDTH="90%" -><TR -><TD ><PRE CLASS="PROGRAMLISTING" ><TT @@ -260,24 +218,13 @@ CLASS="COMMAND" >smbgroupedit -vs | grep "Domain Admins"</B > Domain Admins (S-1-5-21-1108995562-3116817432-1375597819-512) -> -1</PRE -></TD -></TR -></TABLE ></P ></LI ><LI ><P >map the unix domadm group to the Windows NT "Domain Admins" group, by running the command: - </P -><P -><TABLE -BORDER="0" -BGCOLOR="#E0E0E0" -WIDTH="90%" -><TR -><TD -><PRE +<PRE CLASS="PROGRAMLISTING" ><TT CLASS="PROMPT" @@ -288,14 +235,14 @@ CLASS="COMMAND" -c S-1-5-21-1108995562-3116817432-1375597819-512 \ -u domadm -td</B ></PRE -></TD -></TR -></TABLE ></P ><P -> <I +><SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >warning:</I +></SPAN > don't copy and paste this sample, the Domain Admins SID (the S-1-5-21-...-512) is different for every PDC. </P @@ -304,15 +251,8 @@ CLASS="EMPHASIS" ></LI ></OL ><P ->To verify that your mapping has taken effect:</P -><P -><TABLE -BORDER="0" -BGCOLOR="#E0E0E0" -WIDTH="100%" -><TR -><TD -><PRE +>To verify that your mapping has taken effect: +<PRE CLASS="PROGRAMLISTING" ><TT CLASS="PROMPT" @@ -322,22 +262,12 @@ CLASS="COMMAND" >smbgroupedit -vs|grep "Domain Admins"</B > Domain Admins (S-1-5-21-1108995562-3116817432-1375597819-512) -> domadm</PRE -></TD -></TR -></TABLE ></P ><P >To give access to a certain directory on a domain member machine (an NT/W2K or a samba server running winbind) to some users who are member -of a group on your samba PDC, flag that group as a domain group:</P -><P -><TABLE -BORDER="0" -BGCOLOR="#E0E0E0" -WIDTH="100%" -><TR -><TD -><PRE +of a group on your samba PDC, flag that group as a domain group: +<PRE CLASS="PROGRAMLISTING" ><TT CLASS="PROMPT" @@ -346,15 +276,12 @@ CLASS="PROMPT" CLASS="COMMAND" >smbgroupedit -a unixgroup -td</B ></PRE -></TD -></TR -></TABLE ></P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN90" +NAME="AEN87" ></A ><H2 >VERSION</H2 @@ -365,21 +292,23 @@ the Samba suite.</P ><DIV CLASS="REFSECT1" ><A -NAME="AEN93" +NAME="AEN90" ></A ><H2 >SEE ALSO</H2 ><P -><A -HREF="smb.conf.5.html" -TARGET="_top" ->smb.conf(5)</A +><SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smb.conf</SPAN +>(5)</SPAN ></P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN97" +NAME="AEN96" ></A ><H2 >AUTHOR</H2 @@ -394,7 +323,8 @@ CLASS="COMMAND" >smbgroupedit</B > was written by Jean Francois Micouleau. The current set of manpages and documentation is maintained -by the Samba Team in the same fashion as the Samba source code.</P +by the Samba Team in the same fashion as the Samba source code. The conversion +to DocBook XML 4.2 for Samba 3.0 was done by Alexander Bokovoy.</P ></DIV ></BODY ></HTML diff --git a/docs/htmldocs/smbmnt.8.html b/docs/htmldocs/smbmnt.8.html index 06b9fb1fd3..de3af0b0a4 100644 --- a/docs/htmldocs/smbmnt.8.html +++ b/docs/htmldocs/smbmnt.8.html @@ -5,7 +5,7 @@ >smbmnt</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77"></HEAD +CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"></HEAD ><BODY CLASS="REFENTRY" BGCOLOR="#FFFFFF" @@ -15,7 +15,7 @@ VLINK="#840084" ALINK="#0000FF" ><H1 ><A -NAME="SMBMNT" +NAME="SMBMNT.8" ></A >smbmnt</H1 ><DIV @@ -65,14 +65,12 @@ CLASS="COMMAND" CLASS="COMMAND" >smbmnt</B > program is normally invoked - by <A -HREF="smbmount.8.html" -TARGET="_top" -><B -CLASS="COMMAND" ->smbmount(8)</B -> - </A + by <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbmount</SPAN +>(8)</SPAN >. It should not be invoked directly by users. </P ><P >smbmount searches the normal PATH for smbmnt. You must ensure @@ -81,7 +79,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN30" +NAME="AEN31" ></A ><H2 >OPTIONS</H2 @@ -139,7 +137,7 @@ CLASS="VARIABLELIST" ><DIV CLASS="REFSECT1" ><A -NAME="AEN57" +NAME="AEN58" ></A ><H2 >AUTHOR</H2 @@ -172,7 +170,8 @@ TARGET="_top" </P ><P >The conversion of this manpage for Samba 2.2 was performed - by Gerald Carter</P + by Gerald Carter. The conversion to DocBook XML 4.2 for Samba 3.0 + was done by Alexander Bokovoy.</P ></DIV ></BODY ></HTML diff --git a/docs/htmldocs/smbmount.8.html b/docs/htmldocs/smbmount.8.html index 81a3ac04b2..bc9fcf72e2 100644 --- a/docs/htmldocs/smbmount.8.html +++ b/docs/htmldocs/smbmount.8.html @@ -5,7 +5,7 @@ >smbmount</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77"></HEAD +CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"></HEAD ><BODY CLASS="REFENTRY" BGCOLOR="#FFFFFF" @@ -15,7 +15,7 @@ VLINK="#840084" ALINK="#0000FF" ><H1 ><A -NAME="SMBMOUNT" +NAME="SMBMOUNT.8" ></A >smbmount</H1 ><DIV @@ -55,9 +55,12 @@ CLASS="COMMAND" CLASS="COMMAND" >mount.smbfs</B > by - the <B -CLASS="COMMAND" ->mount(8)</B + the <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>mount</SPAN +>(8)</SPAN > command when using the "-t smbfs" option. This command only works in Linux, and the kernel must support the smbfs filesystem. </P @@ -80,10 +83,9 @@ CLASS="COMMAND" typically this output will end up in <TT CLASS="FILENAME" >log.smbmount</TT ->. The - <B +>. The <B CLASS="COMMAND" ->smbmount</B +> smbmount</B > process may also be called mount.smbfs.</P ><P ><SPAN @@ -96,9 +98,12 @@ CLASS="EMPHASIS" CLASS="COMMAND" >smbmount</B > - calls <B -CLASS="COMMAND" ->smbmnt(8)</B + calls <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbmnt</SPAN +>(8)</SPAN > to do the actual mount. You must make sure that <B CLASS="COMMAND" @@ -109,7 +114,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN31" +NAME="AEN35" ></A ><H2 >OPTIONS</H2 @@ -159,16 +164,13 @@ CLASS="COMMAND" >credentials=<filename></DT ><DD ><P ->specifies a file that contains a username - and/or password. The format of the file is:</P -><P -> <PRE +>specifies a file that contains a username and/or password. +The format of the file is: +<PRE CLASS="PROGRAMLISTING" -> username = <value> - password = <value> - </PRE -> - </P +>username = <value> +password = <value></PRE +></P ><P >This is preferred over having passwords in plaintext in a shared file, such as <TT @@ -255,10 +257,12 @@ CLASS="FILENAME" >sets the TCP socket options. See the <A HREF="smb.conf.5.html#SOCKETOPTIONS" TARGET="_top" -><TT -CLASS="FILENAME" ->smb.conf - </TT +><SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smb.conf</SPAN +>(5)</SPAN ></A > <TT CLASS="PARAMETER" @@ -332,7 +336,7 @@ CLASS="PARAMETER" ><DIV CLASS="REFSECT1" ><A -NAME="AEN125" +NAME="AEN130" ></A ><H2 >ENVIRONMENT VARIABLES</H2 @@ -364,7 +368,7 @@ CLASS="ENVAR" ><DIV CLASS="REFSECT1" ><A -NAME="AEN133" +NAME="AEN138" ></A ><H2 >BUGS</H2 @@ -399,7 +403,7 @@ NAME="AEN133" ><DIV CLASS="REFSECT1" ><A -NAME="AEN142" +NAME="AEN147" ></A ><H2 >SEE ALSO</H2 @@ -409,22 +413,19 @@ NAME="AEN142" ><P >FreeBSD also has a smbfs, but it is not related to smbmount</P ><P ->For Solaris, HP-UX and others you may want to look at - <A -HREF="smbsh.1.html" -TARGET="_top" -><B -CLASS="COMMAND" ->smbsh(1)</B -></A -> or at other - solutions, such as sharity or perhaps replacing the SMB server with - a NFS server.</P +>For Solaris, HP-UX and others you may want to look at <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbsh</SPAN +>(1)</SPAN +> or at other solutions, such as + Sharity or perhaps replacing the SMB server with a NFS server.</P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN149" +NAME="AEN155" ></A ><H2 >AUTHOR</H2 @@ -457,7 +458,8 @@ TARGET="_top" </P ><P >The conversion of this manpage for Samba 2.2 was performed - by Gerald Carter</P + by Gerald Carter. The conversion to DocBook XML 4.2 for Samba 3.0 + was done by Alexander Bokovoy.</P ></DIV ></BODY ></HTML diff --git a/docs/htmldocs/smbpasswd.5.html b/docs/htmldocs/smbpasswd.5.html index ac3ab94691..a07be03b41 100644 --- a/docs/htmldocs/smbpasswd.5.html +++ b/docs/htmldocs/smbpasswd.5.html @@ -5,7 +5,7 @@ >smbpasswd</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77"></HEAD +CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"></HEAD ><BODY CLASS="REFENTRY" BGCOLOR="#FFFFFF" @@ -15,7 +15,7 @@ VLINK="#840084" ALINK="#0000FF" ><H1 ><A -NAME="SMBPASSWD" +NAME="SMBPASSWD.5" ></A >smbpasswd</H1 ><DIV @@ -47,10 +47,12 @@ NAME="AEN11" ><H2 >DESCRIPTION</H2 ><P ->This tool is part of the <A -HREF="samba.7.html" -TARGET="_top" -> Samba</A +>This tool is part of the <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>Samba</SPAN +>(7)</SPAN > suite.</P ><P >smbpasswd is the Samba encrypted password file. It contains @@ -62,7 +64,7 @@ TARGET="_top" ><DIV CLASS="REFSECT1" ><A -NAME="AEN16" +NAME="AEN18" ></A ><H2 >FILE FORMAT</H2 @@ -204,7 +206,7 @@ CLASS="EMPHASIS" the attributes of the users account. In the Samba 2.2 release this field is bracketed by '[' and ']' characters and is always 13 characters in length (including the '[' and ']' characters). - The contents of this field may be any of the characters. + The contents of this field may be any of the following characters: </P ><P ></P @@ -241,10 +243,12 @@ CLASS="PARAMETER" > parameter is set in the <A HREF="smb.conf.5.html#NULLPASSWORDS" TARGET="_top" -><TT -CLASS="FILENAME" ->smb.conf(5) - </TT +><SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smb.conf</SPAN +>(5)</SPAN ></A > config file. </P ></LI @@ -257,8 +261,7 @@ CLASS="EMPHASIS" >D</I ></SPAN > - This means the account - is disabled and no SMB/CIFS logins will be allowed for - this user. </P + is disabled and no SMB/CIFS logins will be allowed for this user. </P ></LI ><LI ><P @@ -296,7 +299,7 @@ CLASS="EMPHASIS" ><DIV CLASS="REFSECT1" ><A -NAME="AEN73" +NAME="AEN77" ></A ><H2 >VERSION</H2 @@ -307,23 +310,23 @@ NAME="AEN73" ><DIV CLASS="REFSECT1" ><A -NAME="AEN76" +NAME="AEN80" ></A ><H2 >SEE ALSO</H2 ><P -><A -HREF="smbpasswd.8.html" -TARGET="_top" -><B -CLASS="COMMAND" ->smbpasswd(8)</B -></A ->, - <A -HREF="samba.7.html" -TARGET="_top" ->samba(7)</A +><SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbpasswd</SPAN +>(8)</SPAN +>, <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>Samba</SPAN +>(7)</SPAN >, and the Internet RFC1321 for details on the MD4 algorithm. </P @@ -331,7 +334,7 @@ TARGET="_top" ><DIV CLASS="REFSECT1" ><A -NAME="AEN82" +NAME="AEN89" ></A ><H2 >AUTHOR</H2 @@ -343,14 +346,14 @@ NAME="AEN82" ><P >The original Samba man pages were written by Karl Auer. The man page sources were converted to YODL format (another - excellent piece of Open Source software, available at - <A + excellent piece of Open Source software, available at <A HREF="ftp://ftp.icce.rug.nl/pub/unix/" TARGET="_top" > ftp://ftp.icce.rug.nl/pub/unix/</A >) and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for - Samba 2.2 was done by Gerald Carter</P + Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 + for Samba 3.0 was done by Alexander Bokovoy.</P ></DIV ></BODY ></HTML diff --git a/docs/htmldocs/smbpasswd.8.html b/docs/htmldocs/smbpasswd.8.html index da3cb9f601..223cd02521 100644 --- a/docs/htmldocs/smbpasswd.8.html +++ b/docs/htmldocs/smbpasswd.8.html @@ -1,12 +1,11 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"> +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <HTML ><HEAD ><TITLE >smbpasswd</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ -"></HEAD +CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"></HEAD ><BODY CLASS="REFENTRY" BGCOLOR="#FFFFFF" @@ -16,7 +15,9 @@ VLINK="#840084" ALINK="#0000FF" ><H1 ><A -NAME="SMBPASSWD">smbpasswd</H1 +NAME="SMBPASSWD.8" +></A +>smbpasswd</H1 ><DIV CLASS="REFNAMEDIV" ><A @@ -28,13 +29,15 @@ NAME="AEN5" ><DIV CLASS="REFSYNOPSISDIV" ><A -NAME="AEN8"><H2 +NAME="AEN8" +></A +><H2 >Synopsis</H2 ><P ><B CLASS="COMMAND" >smbpasswd</B -> [-a] [-x] [-d] [-e] [-D debuglevel] [-n] [-r <remote machine>] [-R <name resolve order>] [-m] [-U username[%password]] [-h] [-s] [-w pass] [-i] [-L] [username]</P +> [-a] [-x] [-d] [-e] [-D debuglevel] [-n] [-r <remote machine>] [-R <name resolve order>] [-m] [-U username[%password]] [-h] [-s] [-w pass] [-i] [-L] [username]</P ></DIV ><DIV CLASS="REFSECT1" @@ -44,18 +47,23 @@ NAME="AEN27" ><H2 >DESCRIPTION</H2 ><P ->This tool is part of the <A -HREF="samba.7.html" -TARGET="_top" -> Samba</A +>This tool is part of the <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>Samba</SPAN +>(7)</SPAN > suite.</P ><P >The smbpasswd program has several different - functions, depending on whether it is run by the <I + functions, depending on whether it is run by the <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >root</I -> - user or not. When run as a normal user it allows the user to change +></SPAN +> user + or not. When run as a normal user it allows the user to change the password used for their SMB sessions on any machines that store SMB passwords. </P ><P @@ -64,25 +72,33 @@ CLASS="EMPHASIS" similar to the way the <B CLASS="COMMAND" >passwd(1)</B -> program works. - <B +> program works. <B CLASS="COMMAND" ->smbpasswd</B +> smbpasswd</B > differs from how the passwd program works - however in that it is not <I + however in that it is not <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >setuid root</I +></SPAN > but works in - a client-server mode and communicates with a locally running - <B -CLASS="COMMAND" ->smbd(8)</B + a client-server mode and communicates with a + locally running <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbd</SPAN +>(8)</SPAN >. As a consequence in order for this to succeed the smbd daemon must be running on the local machine. On a UNIX machine the encrypted SMB passwords are usually stored in - the <TT -CLASS="FILENAME" ->smbpasswd(5)</TT + the <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbpasswd</SPAN +>(5)</SPAN > file. </P ><P >When run by an ordinary user with no options, smbpasswd @@ -91,18 +107,28 @@ CLASS="FILENAME" was typed correctly. No passwords will be echoed on the screen whilst being typed. If you have a blank SMB password (specified by the string "NO PASSWORD" in the smbpasswd file) then just press - the <Enter> key when asked for your old password. </P + the <Enter> key when asked for your old password. </P ><P >smbpasswd can also be used by a normal user to change their SMB password on remote machines, such as Windows NT Primary Domain - Controllers. See the (-r) and -U options below. </P + Controllers. See the (<TT +CLASS="PARAMETER" +><I +>-r</I +></TT +>) and <TT +CLASS="PARAMETER" +><I +>-U</I +></TT +> options + below. </P ><P >When run by root, smbpasswd allows new users to be added and deleted in the smbpasswd file, as well as allows changes to - the attributes of the user in this file to be made. When run by root, - <B + the attributes of the user in this file to be made. When run by root, <B CLASS="COMMAND" ->smbpasswd</B +> smbpasswd</B > accesses the local smbpasswd file directly, thus enabling changes to be made even if smbd is not running. </P @@ -110,7 +136,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN43" +NAME="AEN51" ></A ><H2 >OPTIONS</H2 @@ -125,7 +151,7 @@ CLASS="VARIABLELIST" ><P >This option specifies that the username following should be added to the local smbpasswd file, with the - new password typed (type <Enter> for the old password). This + new password typed (type <Enter> for the old password). This option is ignored if the username following already exists in the smbpasswd file and it is treated like a regular change password command. Note that the default passdb backends require @@ -169,10 +195,12 @@ CLASS="CONSTANT" ><P >If the smbpasswd file is in the 'old' format (pre-Samba 2.0 format) there is no space in the user's password entry to write - this information and the command will FAIL. See <B -CLASS="COMMAND" ->smbpasswd(5) - </B + this information and the command will FAIL. See <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbpasswd</SPAN +>(5)</SPAN > for details on the 'old' and new password file formats. </P ><P @@ -196,9 +224,12 @@ CLASS="CONSTANT" CLASS="COMMAND" > smbpasswd</B > will FAIL to enable the account. - See <B -CLASS="COMMAND" ->smbpasswd (5)</B + See <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbpasswd</SPAN +>(5)</SPAN > for details on the 'old' and new password file formats. </P ><P @@ -294,9 +325,12 @@ CLASS="PARAMETER" copy of the user account database and will not allow the password change).</P ><P +><SPAN +CLASS="emphasis" ><I CLASS="EMPHASIS" >Note</I +></SPAN > that Windows 95/98 do not have a real password database so it is not possible to change passwords specifying a Win95/98 machine as remote machine target. </P @@ -310,7 +344,7 @@ CLASS="EMPHASIS" name of the host being connected to. </P ><P >The options are :"lmhosts", "host", "wins" and "bcast". They - cause names to be resolved as follows : </P + cause names to be resolved as follows: </P ><P ></P ><UL @@ -319,12 +353,14 @@ CLASS="EMPHASIS" ><TT CLASS="CONSTANT" >lmhosts</TT -> : Lookup an IP +>: Lookup an IP address in the Samba lmhosts file. If the line in lmhosts has - no name type attached to the NetBIOS name (see the <A -HREF="lmhosts.5.html" -TARGET="_top" ->lmhosts(5)</A + no name type attached to the NetBIOS name (see the <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>lmhosts</SPAN +>(5)</SPAN > for details) then any name type matches for lookup.</P ></LI @@ -333,7 +369,7 @@ TARGET="_top" ><TT CLASS="CONSTANT" >host</TT -> : Do a standard host +>: Do a standard host name to IP address resolution, using the system <TT CLASS="FILENAME" >/etc/hosts @@ -353,7 +389,7 @@ CLASS="FILENAME" ><TT CLASS="CONSTANT" >wins</TT -> : Query a name with +>: Query a name with the IP address listed in the <TT CLASS="PARAMETER" ><I @@ -368,7 +404,7 @@ CLASS="PARAMETER" ><TT CLASS="CONSTANT" >bcast</TT -> : Do a broadcast on +>: Do a broadcast on each of the known local interfaces listed in the <TT CLASS="PARAMETER" @@ -385,10 +421,12 @@ CLASS="PARAMETER" CLASS="COMMAND" >lmhosts, host, wins, bcast</B > - and without this parameter or any entry in the - <TT -CLASS="FILENAME" ->smb.conf</TT + and without this parameter or any entry in the <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smb.conf</SPAN +>(5)</SPAN > file the name resolution methods will be attempted in this order. </P ></DD @@ -474,7 +512,7 @@ CLASS="PARAMETER" >. Note that the password is stored in the <TT CLASS="FILENAME" ->private/secrets.tdb</TT +>secrets.tdb</TT > and is keyed off of the admin's DN. This means that if the value of <TT CLASS="PARAMETER" @@ -509,9 +547,12 @@ CLASS="PARAMETER" ><DD ><P >This specifies the username for all of the - <I + <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >root only</I +></SPAN > options to operate on. Only root can specify this parameter as only root has the permission needed to modify attributes directly in the local smbpasswd file. @@ -523,7 +564,7 @@ CLASS="EMPHASIS" ><DIV CLASS="REFSECT1" ><A -NAME="AEN173" +NAME="AEN189" ></A ><H2 >NOTES</H2 @@ -537,70 +578,71 @@ CLASS="COMMAND" is to add a restriction to the hosts that may access the <B CLASS="COMMAND" > smbd</B -> running on the local machine by specifying a - <TT +> running on the local machine by specifying either <TT CLASS="PARAMETER" ><I ->allow hosts</I +>allow + hosts</I ></TT > or <TT CLASS="PARAMETER" ><I >deny hosts</I ></TT -> - entry in the <TT -CLASS="FILENAME" ->smb.conf</TT +> entry in + the <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smb.conf</SPAN +>(5)</SPAN > file and neglecting to allow "localhost" access to the smbd. </P ><P >In addition, the smbpasswd command is only useful if Samba - has been set up to use encrypted passwords. See the file - <TT -CLASS="FILENAME" ->ENCRYPTION.txt</TT + has been set up to use encrypted passwords. See the document <A +HREF="pwencrypt.html" +TARGET="_top" +> "LanMan and NT Password Encryption in Samba"</A > in the docs directory for details on how to do this. </P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN183" +NAME="AEN201" ></A ><H2 >VERSION</H2 ><P ->This man page is correct for version 3.0 of - the Samba suite.</P +>This man page is correct for version 3.0 of the Samba suite.</P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN186" +NAME="AEN204" ></A ><H2 >SEE ALSO</H2 ><P -><A -HREF="smbpasswd.5.html" -TARGET="_top" -><TT -CLASS="FILENAME" ->smbpasswd(5)</TT -></A ->, - <A -HREF="samba.7.html" -TARGET="_top" ->samba(7)</A -> - </P +><SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbpasswd</SPAN +>(5)</SPAN +>, <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>Samba</SPAN +>(7)</SPAN +>.</P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN192" +NAME="AEN213" ></A ><H2 >AUTHOR</H2 @@ -612,14 +654,14 @@ NAME="AEN192" ><P >The original Samba man pages were written by Karl Auer. The man page sources were converted to YODL format (another - excellent piece of Open Source software, available at - <A + excellent piece of Open Source software, available at <A HREF="ftp://ftp.icce.rug.nl/pub/unix/" TARGET="_top" > ftp://ftp.icce.rug.nl/pub/unix/</A >) and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for - Samba 2.2 was done by Gerald Carter</P + Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 + for Samba 3.0 was done by Alexander Bokovoy.</P ></DIV ></BODY ></HTML diff --git a/docs/htmldocs/smbsh.1.html b/docs/htmldocs/smbsh.1.html index bab2b45cdd..c8c61fb6fe 100644 --- a/docs/htmldocs/smbsh.1.html +++ b/docs/htmldocs/smbsh.1.html @@ -1,12 +1,11 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"> +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <HTML ><HEAD ><TITLE >smbsh</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ -"></HEAD +CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"></HEAD ><BODY CLASS="REFENTRY" BGCOLOR="#FFFFFF" @@ -16,7 +15,9 @@ VLINK="#840084" ALINK="#0000FF" ><H1 ><A -NAME="SMBSH">smbsh</H1 +NAME="SMBSH.1" +></A +>smbsh</H1 ><DIV CLASS="REFNAMEDIV" ><A @@ -29,13 +30,15 @@ NAME="AEN5" ><DIV CLASS="REFSYNOPSISDIV" ><A -NAME="AEN8"><H2 +NAME="AEN8" +></A +><H2 >Synopsis</H2 ><P ><B CLASS="COMMAND" >smbsh</B -> [-W workgroup] [-U username] [-P prefix] [-R <name resolve order>] [-d <debug level>] [-l logfile] [-L libdir]</P +> [-W workgroup] [-U username] [-P prefix] [-R <name resolve order>] [-d <debug level>] [-l logfile] [-L libdir]</P ></DIV ><DIV CLASS="REFSECT1" @@ -45,10 +48,12 @@ NAME="AEN18" ><H2 >DESCRIPTION</H2 ><P ->This tool is part of the <A -HREF="samba.7.html" -TARGET="_top" -> Samba</A +>This tool is part of the <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>Samba</SPAN +>(7)</SPAN > suite.</P ><P ><B @@ -74,7 +79,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN28" +NAME="AEN30" ></A ><H2 >OPTIONS</H2 @@ -88,9 +93,12 @@ CLASS="VARIABLELIST" ><DD ><P >Override the default workgroup specified in the - workgroup parameter of the <TT -CLASS="FILENAME" ->smb.conf</TT + workgroup parameter of the <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smb.conf</SPAN +>(5)</SPAN > file for this session. This may be needed to connect to some servers. </P @@ -112,14 +120,17 @@ CLASS="FILENAME" >This option allows the user to set the directory prefix for SMB access. The default value if this option is not specified is - <I + <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >smb</I +></SPAN >. </P ></DD ><DT ->-R <name resolve order></DT +>-R <name resolve order></DT ><DD ><P >This option is used to determine what naming @@ -127,7 +138,7 @@ CLASS="EMPHASIS" host names to IP addresses. The option takes a space-separated string of different name resolution options.</P ><P ->The options are :"lmhosts", "host", "wins" and "bcast". +>The options are: "lmhosts", "host", "wins" and "bcast". They cause names to be resolved as follows :</P ><P ></P @@ -137,16 +148,18 @@ CLASS="EMPHASIS" ><TT CLASS="CONSTANT" >lmhosts</TT -> : +>: Lookup an IP address in the Samba lmhosts file. If the line in lmhosts has no name type attached to the NetBIOS name - (see the <A -HREF="lmhosts.5.html" -TARGET="_top" ->lmhosts(5)</A -> - for details) then any name type matches for lookup. + (see the <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>lmhosts</SPAN +>(5)</SPAN +> for details) + then any name type matches for lookup. </P ></LI ><LI @@ -154,7 +167,7 @@ TARGET="_top" ><TT CLASS="CONSTANT" >host</TT -> : +>: Do a standard host name to IP address resolution, using the system <TT CLASS="FILENAME" @@ -176,7 +189,7 @@ CLASS="FILENAME" ><TT CLASS="CONSTANT" >wins</TT -> : +>: Query a name with the IP address listed in the <TT CLASS="PARAMETER" @@ -193,7 +206,7 @@ CLASS="PARAMETER" ><TT CLASS="CONSTANT" >bcast</TT -> : +>: Do a broadcast on each of the known local interfaces listed in the <TT CLASS="PARAMETER" @@ -209,11 +222,19 @@ CLASS="PARAMETER" ></UL ><P >If this parameter is not set then the name resolve order - defined in the <TT -CLASS="FILENAME" ->smb.conf</TT + defined in the <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smb.conf</SPAN +>(5)</SPAN > file parameter - (name resolve order) will be used. </P + (<TT +CLASS="PARAMETER" +><I +>name resolve order</I +></TT +>) will be used. </P ><P >The default order is lmhosts, host, wins, bcast. Without this parameter or any entry in the <TT @@ -222,15 +243,17 @@ CLASS="PARAMETER" >name resolve order </I ></TT -> parameter of the <TT -CLASS="FILENAME" ->smb.conf</TT -> - file, the name resolution methods will be attempted in this - order. </P +> parameter of the <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smb.conf</SPAN +>(5)</SPAN +> file, the name resolution methods + will be attempted in this order. </P ></DD ><DT ->-d <debug level></DT +>-d <debug level></DT ><DD ><P >debug level is an integer from 0 to 10.</P @@ -239,9 +262,12 @@ CLASS="FILENAME" is zero.</P ><P >The higher this value, the more detail will be logged - about the activities of <B -CLASS="COMMAND" ->nmblookup</B + about the activities of <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>nmblookup</SPAN +>(1)</SPAN >. At level 0, only critical errors and serious warnings will be logged. </P @@ -284,7 +310,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN91" +NAME="AEN104" ></A ><H2 >EXAMPLES</H2 @@ -297,17 +323,10 @@ CLASS="COMMAND" > smbsh</B > from the prompt and enter the username and password that authenticates you to the machine running the Windows NT - operating system.</P -><P -><TABLE -BORDER="0" -BGCOLOR="#E0E0E0" -WIDTH="100%" -><TR -><TD -><PRE + operating system. +<PRE CLASS="PROGRAMLISTING" -> <TT +><TT CLASS="PROMPT" >system% </TT ><TT @@ -316,7 +335,7 @@ CLASS="USERINPUT" >smbsh</B ></TT > - <TT +<TT CLASS="PROMPT" >Username: </TT ><TT @@ -325,7 +344,7 @@ CLASS="USERINPUT" >user</B ></TT > - <TT +<TT CLASS="PROMPT" >Password: </TT ><TT @@ -333,11 +352,7 @@ CLASS="USERINPUT" ><B >XXXXXXX</B ></TT -> - </PRE -></TD -></TR -></TABLE +></PRE ></P ><P >Any dynamically linked command you execute from @@ -357,7 +372,7 @@ CLASS="COMMAND" the workgroup MYGROUP. The command <B CLASS="COMMAND" ->ls /smb/MYGROUP/<machine-name></B +>ls /smb/MYGROUP/<machine-name></B > will show the share names for that machine. You could then, for example, use the <B CLASS="COMMAND" @@ -374,18 +389,17 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN112" +NAME="AEN124" ></A ><H2 >VERSION</H2 ><P ->This man page is correct for version 3.0 of - the Samba suite.</P +>This man page is correct for version 3.0 of the Samba suite.</P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN115" +NAME="AEN127" ></A ><H2 >BUGS</H2 @@ -418,30 +432,29 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN124" +NAME="AEN136" ></A ><H2 >SEE ALSO</H2 ><P -><A -HREF="smbd.8.html" -TARGET="_top" -><B -CLASS="COMMAND" ->smbd(8)</B -></A ->, - <A -HREF="smb.conf.5.html" -TARGET="_top" ->smb.conf(5)</A -> - </P +><SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbd</SPAN +>(8)</SPAN +>, <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smb.conf</SPAN +>(5)</SPAN +></P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN130" +NAME="AEN145" ></A ><H2 >AUTHOR</H2 @@ -453,14 +466,14 @@ NAME="AEN130" ><P >The original Samba man pages were written by Karl Auer. The man page sources were converted to YODL format (another - excellent piece of Open Source software, available at - <A + excellent piece of Open Source software, available at <A HREF="ftp://ftp.icce.rug.nl/pub/unix/" TARGET="_top" > ftp://ftp.icce.rug.nl/pub/unix/</A >) and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for - Samba 2.2 was done by Gerald Carter</P + Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 + for Samba 3.0 was done by Alexander Bokovoy.</P ></DIV ></BODY ></HTML diff --git a/docs/htmldocs/smbspool.8.html b/docs/htmldocs/smbspool.8.html index 8dc2fbbd63..b66d08381d 100644 --- a/docs/htmldocs/smbspool.8.html +++ b/docs/htmldocs/smbspool.8.html @@ -5,7 +5,7 @@ >smbspool</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77"></HEAD +CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"></HEAD ><BODY CLASS="REFENTRY" BGCOLOR="#FFFFFF" @@ -15,7 +15,7 @@ VLINK="#840084" ALINK="#0000FF" ><H1 ><A -NAME="SMBSPOOL" +NAME="SMBSPOOL.8" ></A >smbspool</H1 ><DIV @@ -47,10 +47,12 @@ NAME="AEN17" ><H2 >DESCRIPTION</H2 ><P ->This tool is part of the <A -HREF="samba.7.html" -TARGET="_top" -> Samba</A +>This tool is part of the <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>Samba</SPAN +>(7)</SPAN > suite.</P ><P >smbspool is a very small print spooling program that @@ -87,8 +89,7 @@ CLASS="EMPHASIS" ></LI ><LI ><P ->smb://username:password@workgroup/server/printer - </P +>smb://username:password@workgroup/server/printer</P ></LI ></UL ><P @@ -112,7 +113,7 @@ CLASS="ENVAR" ><DIV CLASS="REFSECT1" ><A -NAME="AEN39" +NAME="AEN41" ></A ><H2 >OPTIONS</H2 @@ -161,41 +162,39 @@ NAME="AEN39" ><DIV CLASS="REFSECT1" ><A -NAME="AEN54" +NAME="AEN56" ></A ><H2 >VERSION</H2 ><P ->This man page is correct for version 2.2 of - the Samba suite.</P +>This man page is correct for version 2.2 of the Samba suite.</P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN57" +NAME="AEN59" ></A ><H2 >SEE ALSO</H2 ><P -><A -HREF="smbd.8.html" -TARGET="_top" -><B -CLASS="COMMAND" ->smbd(8)</B -></A ->, - and <A -HREF="samba.7.html" -TARGET="_top" ->samba(7)</A ->. - </P +><SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbd</SPAN +>(8)</SPAN +> and <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>Samba</SPAN +>(7)</SPAN +>.</P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN63" +NAME="AEN68" ></A ><H2 >AUTHOR</H2 @@ -213,14 +212,14 @@ CLASS="COMMAND" ><P >The original Samba man pages were written by Karl Auer. The man page sources were converted to YODL format (another - excellent piece of Open Source software, available at - <A + excellent piece of Open Source software, available at <A HREF="ftp://ftp.icce.rug.nl/pub/unix/" TARGET="_top" > ftp://ftp.icce.rug.nl/pub/unix/</A >) and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for - Samba 2.2 was done by Gerald Carter</P + Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 + for Samba 3.0 was done by Alexander Bokovoy.</P ></DIV ></BODY ></HTML diff --git a/docs/htmldocs/smbstatus.1.html b/docs/htmldocs/smbstatus.1.html index fb7e14fadd..47b7ef112f 100644 --- a/docs/htmldocs/smbstatus.1.html +++ b/docs/htmldocs/smbstatus.1.html @@ -5,7 +5,7 @@ >smbstatus</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77"></HEAD +CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"></HEAD ><BODY CLASS="REFENTRY" BGCOLOR="#FFFFFF" @@ -15,7 +15,7 @@ VLINK="#840084" ALINK="#0000FF" ><H1 ><A -NAME="SMBSTATUS" +NAME="SMBSTATUS.1" ></A >smbstatus</H1 ><DIV @@ -47,10 +47,12 @@ NAME="AEN21" ><H2 >DESCRIPTION</H2 ><P ->This tool is part of the <A -HREF="samba.7.html" -TARGET="_top" -> Samba</A +>This tool is part of the <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>Samba</SPAN +>(7)</SPAN > suite.</P ><P ><B @@ -62,7 +64,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN27" +NAME="AEN29" ></A ><H2 >OPTIONS</H2 @@ -114,13 +116,12 @@ CLASS="VARIABLELIST" >-p|--processes</DT ><DD ><P ->print a list of <A -HREF="smbd.8.html" -TARGET="_top" -> <B -CLASS="COMMAND" ->smbd(8)</B -></A +>print a list of <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbd</SPAN +>(8)</SPAN > processes and exit. Useful for scripting.</P ></DD @@ -136,14 +137,12 @@ CLASS="COMMAND" ><P >The default configuration file name is determined at compile time. The file specified contains the - configuration details required by the server. See <A -HREF="smb.conf.5.html" -TARGET="_top" -><TT -CLASS="FILENAME" ->smb.conf(5)</TT -> - </A + configuration details required by the server. See <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smb.conf</SPAN +>(5)</SPAN > for more information.</P ></DD ><DT @@ -164,7 +163,7 @@ CLASS="PARAMETER" ><DIV CLASS="REFSECT1" ><A -NAME="AEN75" +NAME="AEN79" ></A ><H2 >VERSION</H2 @@ -175,29 +174,29 @@ NAME="AEN75" ><DIV CLASS="REFSECT1" ><A -NAME="AEN78" +NAME="AEN82" ></A ><H2 >SEE ALSO</H2 ><P -><A -HREF="smbd.8.html" -TARGET="_top" -><B -CLASS="COMMAND" ->smbd(8)</B -></A -> and - <A -HREF="smb.conf.5.html" -TARGET="_top" ->smb.conf(5)</A +><SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbd</SPAN +>(8)</SPAN +> and <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smb.conf</SPAN +>(5)</SPAN >.</P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN84" +NAME="AEN91" ></A ><H2 >AUTHOR</H2 @@ -209,14 +208,14 @@ NAME="AEN84" ><P >The original Samba man pages were written by Karl Auer. The man page sources were converted to YODL format (another - excellent piece of Open Source software, available at - <A + excellent piece of Open Source software, available at <A HREF="ftp://ftp.icce.rug.nl/pub/unix/" TARGET="_top" > ftp://ftp.icce.rug.nl/pub/unix/</A >) and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for - Samba 2.2 was done by Gerald Carter</P + Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 + for Samba 3.0 was done by Alexander Bokovoy.</P ></DIV ></BODY ></HTML diff --git a/docs/htmldocs/smbtar.1.html b/docs/htmldocs/smbtar.1.html index d3215c6901..1eb0017417 100644 --- a/docs/htmldocs/smbtar.1.html +++ b/docs/htmldocs/smbtar.1.html @@ -5,7 +5,7 @@ >smbtar</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77"></HEAD +CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"></HEAD ><BODY CLASS="REFENTRY" BGCOLOR="#FFFFFF" @@ -15,7 +15,7 @@ VLINK="#840084" ALINK="#0000FF" ><H1 ><A -NAME="SMBTAR" +NAME="SMBTAR.1" ></A >smbtar</H1 ><DIV @@ -48,30 +48,30 @@ NAME="AEN26" ><H2 >DESCRIPTION</H2 ><P ->This tool is part of the <A -HREF="samba.7.html" -TARGET="_top" -> Samba</A +>This tool is part of the <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>Samba</SPAN +>(7)</SPAN > suite.</P ><P ><B CLASS="COMMAND" >smbtar</B > is a very small shell script on top - of <A -HREF="smbclient.1.html" -TARGET="_top" -><B -CLASS="COMMAND" ->smbclient(1)</B -></A -> - which dumps SMB shares directly to tape. </P + of <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbclient</SPAN +>(1)</SPAN +> which dumps SMB shares directly to tape.</P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN34" +NAME="AEN37" ></A ><H2 >OPTIONS</H2 @@ -193,11 +193,13 @@ CLASS="PARAMETER" ><I >-d</I ></TT -> flag of <B -CLASS="COMMAND" ->smbclient(1) - </B ->. </P +> flag of <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbclient</SPAN +>(1)</SPAN +>.</P ></DD ></DL ></DIV @@ -205,7 +207,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN95" +NAME="AEN100" ></A ><H2 >ENVIRONMENT VARIABLES</H2 @@ -222,7 +224,7 @@ CLASS="PARAMETER" ><DIV CLASS="REFSECT1" ><A -NAME="AEN99" +NAME="AEN104" ></A ><H2 >BUGS</H2 @@ -236,7 +238,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN103" +NAME="AEN108" ></A ><H2 >CAVEATS</H2 @@ -249,7 +251,7 @@ NAME="AEN103" ><DIV CLASS="REFSECT1" ><A -NAME="AEN106" +NAME="AEN111" ></A ><H2 >DIAGNOSTICS</H2 @@ -260,21 +262,18 @@ CLASS="emphasis" CLASS="EMPHASIS" >DIAGNOSTICS</I ></SPAN -> section for the - <A -HREF="smbclient.1.html" -TARGET="_top" -><B -CLASS="COMMAND" ->smbclient(1)</B -> - </A +> section for the <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbclient</SPAN +>(1)</SPAN > command.</P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN112" +NAME="AEN118" ></A ><H2 >VERSION</H2 @@ -285,38 +284,35 @@ NAME="AEN112" ><DIV CLASS="REFSECT1" ><A -NAME="AEN115" +NAME="AEN121" ></A ><H2 >SEE ALSO</H2 ><P -><A -HREF="smbd.8.html" -TARGET="_top" -><B -CLASS="COMMAND" ->smbd(8)</B -></A ->, - <A -HREF="smbclient.1.html" -TARGET="_top" -><B -CLASS="COMMAND" ->smbclient(1)</B -></A ->, - <A -HREF="smb.conf.5.html" -TARGET="_top" ->smb.conf(5)</A ->, - </P +><SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbd</SPAN +>(8)</SPAN +>, <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbclient</SPAN +>(1)</SPAN +>, <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smb.conf</SPAN +>(5)</SPAN +>.</P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN123" +NAME="AEN133" ></A ><H2 >AUTHOR</H2 @@ -342,14 +338,14 @@ TARGET="_top" >. Many thanks to everyone who suggested extensions, improvements, bug fixes, etc. The man page sources were converted to YODL format (another - excellent piece of Open Source software, available at - <A + excellent piece of Open Source software, available at <A HREF="ftp://ftp.icce.rug.nl/pub/unix/" TARGET="_top" > ftp://ftp.icce.rug.nl/pub/unix/</A >) and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for - Samba 2.2 was done by Gerald Carter.</P + Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 for + Samba 3.0 was done by Alexander Bokovoy.</P ></DIV ></BODY ></HTML diff --git a/docs/htmldocs/smbumount.8.html b/docs/htmldocs/smbumount.8.html index 993436f0c6..83041b796c 100644 --- a/docs/htmldocs/smbumount.8.html +++ b/docs/htmldocs/smbumount.8.html @@ -5,7 +5,7 @@ >smbumount</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77"></HEAD +CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"></HEAD ><BODY CLASS="REFENTRY" BGCOLOR="#FFFFFF" @@ -15,7 +15,7 @@ VLINK="#840084" ALINK="#0000FF" ><H1 ><A -NAME="SMBUMOUNT" +NAME="SMBUMOUNT.8" ></A >smbumount</H1 ><DIV @@ -88,20 +88,18 @@ NAME="AEN23" ><H2 >SEE ALSO</H2 ><P -><A -HREF="smbmount.8.html" -TARGET="_top" -><B -CLASS="COMMAND" ->smbmount(8)</B -> - </A +><SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbmount</SPAN +>(8)</SPAN ></P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN28" +NAME="AEN29" ></A ><H2 >AUTHOR</H2 @@ -134,7 +132,8 @@ TARGET="_top" </P ><P >The conversion of this manpage for Samba 2.2 was performed - by Gerald Carter</P + by Gerald Carter. The conversion to DocBook XML 4.2 for Samba 3.0 + was done by Alexander Bokovoy.</P ></DIV ></BODY ></HTML diff --git a/docs/htmldocs/speed.html b/docs/htmldocs/speed.html index 1a05706f92..c99a49142c 100644 --- a/docs/htmldocs/speed.html +++ b/docs/htmldocs/speed.html @@ -5,8 +5,7 @@ >Samba performance issues</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ -"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -17,8 +16,8 @@ REL="PREVIOUS" TITLE="Group mapping HOWTO" HREF="groupmapping.html"><LINK REL="NEXT" -TITLE="Appendixes" -HREF="appendixes.html"></HEAD +TITLE="Creating Group Profiles" +HREF="groupprofiles.html"></HEAD ><BODY CLASS="CHAPTER" BGCOLOR="#FFFFFF" @@ -60,7 +59,7 @@ WIDTH="10%" ALIGN="right" VALIGN="bottom" ><A -HREF="appendixes.html" +HREF="groupprofiles.html" ACCESSKEY="N" >Next</A ></TD @@ -73,13 +72,17 @@ WIDTH="100%"></DIV CLASS="CHAPTER" ><H1 ><A -NAME="SPEED">Chapter 22. Samba performance issues</H1 +NAME="SPEED" +></A +>Chapter 19. Samba performance issues</H1 ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3055">22.1. Comparisons</H1 +NAME="AEN3033" +></A +>19.1. Comparisons</H1 ><P >The Samba server uses TCP to talk to the client. Thus if you are trying to see if it performs well you should really compare it to @@ -108,7 +111,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3061">22.2. Socket options</H1 +NAME="AEN3039" +></A +>19.2. Socket options</H1 ><P >There are a number of socket options that can greatly affect the performance of a TCP based server like Samba.</P @@ -134,7 +139,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3068">22.3. Read size</H1 +NAME="AEN3046" +></A +>19.3. Read size</H1 ><P >The option "read size" affects the overlap of disk reads/writes with network reads/writes. If the amount of data being transferred in @@ -158,7 +165,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3073">22.4. Max xmit</H1 +NAME="AEN3051" +></A +>19.4. Max xmit</H1 ><P >At startup the client and server negotiate a "maximum transmit" size, which limits the size of nearly all SMB commands. You can set the @@ -179,7 +188,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3078">22.5. Log level</H1 +NAME="AEN3056" +></A +>19.5. Log level</H1 ><P >If you set the log level (also known as "debug level") higher than 2 then you may suffer a large drop in performance. This is because the @@ -191,7 +202,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3081">22.6. Read raw</H1 +NAME="AEN3059" +></A +>19.6. Read raw</H1 ><P >The "read raw" operation is designed to be an optimised, low-latency file read operation. A server may choose to not support it, @@ -211,7 +224,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3086">22.7. Write raw</H1 +NAME="AEN3064" +></A +>19.7. Write raw</H1 ><P >The "write raw" operation is designed to be an optimised, low-latency file write operation. A server may choose to not support it, @@ -226,7 +241,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3090">22.8. Slow Clients</H1 +NAME="AEN3068" +></A +>19.8. Slow Clients</H1 ><P >One person has reported that setting the protocol to COREPLUS rather than LANMAN2 gave a dramatic speed improvement (from 10k/s to 150k/s).</P @@ -241,7 +258,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3094">22.9. Slow Logins</H1 +NAME="AEN3072" +></A +>19.9. Slow Logins</H1 ><P >Slow logins are almost always due to the password checking time. Using the lowest practical "password level" will improve things a lot. You @@ -252,7 +271,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3097">22.10. Client tuning</H1 +NAME="AEN3075" +></A +>19.10. Client tuning</H1 ><P >Often a speed problem can be traced to the client. The client (for example Windows for Workgroups) can often be tuned for better TCP @@ -386,7 +407,7 @@ WIDTH="33%" ALIGN="right" VALIGN="top" ><A -HREF="appendixes.html" +HREF="groupprofiles.html" ACCESSKEY="N" >Next</A ></TD @@ -410,7 +431,7 @@ ACCESSKEY="U" WIDTH="33%" ALIGN="right" VALIGN="top" ->Appendixes</TD +>Creating Group Profiles</TD ></TR ></TABLE ></DIV diff --git a/docs/htmldocs/swat.8.html b/docs/htmldocs/swat.8.html index f101a7bc26..0c65e7b1d6 100644 --- a/docs/htmldocs/swat.8.html +++ b/docs/htmldocs/swat.8.html @@ -5,7 +5,7 @@ >swat</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77"></HEAD +CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"></HEAD ><BODY CLASS="REFENTRY" BGCOLOR="#FFFFFF" @@ -15,7 +15,7 @@ VLINK="#840084" ALINK="#0000FF" ><H1 ><A -NAME="SWAT" +NAME="SWAT.8" ></A >swat</H1 ><DIV @@ -47,23 +47,24 @@ NAME="AEN13" ><H2 >DESCRIPTION</H2 ><P ->This tool is part of the <A -HREF="samba.7.html" -TARGET="_top" -> Samba</A +>This tool is part of the <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>Samba</SPAN +>(7)</SPAN > suite.</P ><P ><B CLASS="COMMAND" >swat</B > allows a Samba administrator to - configure the complex <A -HREF="smb.conf.5.html" -TARGET="_top" -><TT -CLASS="FILENAME" -> smb.conf(5)</TT -></A + configure the complex <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smb.conf</SPAN +>(5)</SPAN > file via a Web browser. In addition, a <B CLASS="COMMAND" @@ -86,7 +87,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN26" +NAME="AEN29" ></A ><H2 >OPTIONS</H2 @@ -101,11 +102,14 @@ CLASS="VARIABLELIST" ><P >The default configuration file path is determined at compile time. The file specified contains - the configuration details required by the <B -CLASS="COMMAND" ->smbd - </B -> server. This is the file that <B + the configuration details required by the <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbd</SPAN +>(8)</SPAN +> server. This is the file + that <B CLASS="COMMAND" >swat</B > will modify. @@ -147,7 +151,7 @@ CLASS="EMPHASIS" ><DIV CLASS="REFSECT1" ><A -NAME="AEN44" +NAME="AEN49" ></A ><H2 >INSTALLATION</H2 @@ -181,7 +185,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT2" ><A -NAME="AEN56" +NAME="AEN61" ></A ><H3 >Inetd Installation</H3 @@ -254,7 +258,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT2" ><A -NAME="AEN78" +NAME="AEN83" ></A ><H3 >Launching</H3 @@ -271,7 +275,7 @@ NAME="AEN78" ><DIV CLASS="REFSECT1" ><A -NAME="AEN82" +NAME="AEN87" ></A ><H2 >FILES</H2 @@ -308,10 +312,12 @@ CLASS="FILENAME" ></DT ><DD ><P ->This is the default location of the <TT -CLASS="FILENAME" ->smb.conf(5) - </TT +>This is the default location of the <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smb.conf</SPAN +>(5)</SPAN > server configuration file that swat edits. Other common places that systems install this file are <TT CLASS="FILENAME" @@ -329,7 +335,7 @@ CLASS="FILENAME" ><DIV CLASS="REFSECT1" ><A -NAME="AEN103" +NAME="AEN110" ></A ><H2 >WARNINGS</H2 @@ -337,10 +343,12 @@ NAME="AEN103" ><B CLASS="COMMAND" >swat</B -> will rewrite your <TT -CLASS="FILENAME" ->smb.conf - </TT +> will rewrite your <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smb.conf</SPAN +>(5)</SPAN > file. It will rearrange the entries and delete all comments, <TT CLASS="PARAMETER" @@ -361,18 +369,17 @@ CLASS="FILENAME" ><DIV CLASS="REFSECT1" ><A -NAME="AEN111" +NAME="AEN120" ></A ><H2 >VERSION</H2 ><P ->This man page is correct for version 2.2 of - the Samba suite.</P +>This man page is correct for version 2.2 of the Samba suite.</P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN114" +NAME="AEN123" ></A ><H2 >SEE ALSO</H2 @@ -380,26 +387,24 @@ NAME="AEN114" ><B CLASS="COMMAND" >inetd(5)</B ->, - <A -HREF="smbd.8.html" -TARGET="_top" -><B -CLASS="COMMAND" ->smbd(8)</B -></A ->, - <A -HREF="smb.conf.5.html" -TARGET="_top" ->smb.conf(5)</A -> - </P +>, <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbd</SPAN +>(8)</SPAN +>, <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smb.conf</SPAN +>(5)</SPAN +></P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN121" +NAME="AEN133" ></A ><H2 >AUTHOR</H2 @@ -411,14 +416,14 @@ NAME="AEN121" ><P >The original Samba man pages were written by Karl Auer. The man page sources were converted to YODL format (another - excellent piece of Open Source software, available at - <A + excellent piece of Open Source software, available at <A HREF="ftp://ftp.icce.rug.nl/pub/unix/" TARGET="_top" > ftp://ftp.icce.rug.nl/pub/unix/</A >) and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for - Samba 2.2 was done by Gerald Carter</P + Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 for + Samba 3.0 was done by Alexander Bokovoy.</P ></DIV ></BODY ></HTML diff --git a/docs/htmldocs/testparm.1.html b/docs/htmldocs/testparm.1.html index baf11bacac..52413a1c27 100644 --- a/docs/htmldocs/testparm.1.html +++ b/docs/htmldocs/testparm.1.html @@ -1,12 +1,11 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"> +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <HTML ><HEAD ><TITLE >testparm</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ -"></HEAD +CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"></HEAD ><BODY CLASS="REFENTRY" BGCOLOR="#FFFFFF" @@ -16,7 +15,9 @@ VLINK="#840084" ALINK="#0000FF" ><H1 ><A -NAME="TESTPARM">testparm</H1 +NAME="TESTPARM.1" +></A +>testparm</H1 ><DIV CLASS="REFNAMEDIV" ><A @@ -29,13 +30,15 @@ NAME="AEN5" ><DIV CLASS="REFSYNOPSISDIV" ><A -NAME="AEN8"><H2 +NAME="AEN8" +></A +><H2 >Synopsis</H2 ><P ><B CLASS="COMMAND" >testparm</B -> [-s] [-h] [-v] [-L <servername>] [-t <encoding>] {config filename} [hostname hostIP]</P +> [-s] [-h] [-v] [-L <servername>] [-t <encoding>] {config filename} [hostname hostIP]</P ></DIV ><DIV CLASS="REFSECT1" @@ -45,19 +48,24 @@ NAME="AEN18" ><H2 >DESCRIPTION</H2 ><P ->This tool is part of the <A -HREF="samba.7.html" -TARGET="_top" -> Samba</A +>This tool is part of the <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>Samba</SPAN +>(7)</SPAN > suite.</P ><P ><B CLASS="COMMAND" >testparm</B > is a very simple test program - to check an <B -CLASS="COMMAND" ->smbd</B + to check an <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbd</SPAN +>(8)</SPAN > configuration file for internal correctness. If this program reports no problems, you can use the configuration file with confidence that <B @@ -66,9 +74,12 @@ CLASS="COMMAND" </B > will successfully load the configuration file.</P ><P ->Note that this is <I +>Note that this is <SPAN +CLASS="emphasis" +><I CLASS="EMPHASIS" >NOT</I +></SPAN > a guarantee that the services specified in the configuration file will be available or will operate as expected. </P @@ -94,7 +105,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN33" +NAME="AEN37" ></A ><H2 >OPTIONS</H2 @@ -138,12 +149,13 @@ CLASS="REPLACEABLE" ><DD ><P >If this option is specified, testparm - will also output all options that were not used in - <TT -CLASS="FILENAME" ->smb.conf</TT -> and are thus set to - their defaults.</P + will also output all options that were not used in <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smb.conf</SPAN +>(5)</SPAN +> and are thus set to their defaults.</P ></DD ><DT >-t encoding</DT @@ -158,9 +170,12 @@ CLASS="FILENAME" ><P >This is the name of the configuration file to check. If this parameter is not present then the - default <TT -CLASS="FILENAME" ->smb.conf</TT + default <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smb.conf</SPAN +>(5)</SPAN > file will be checked. </P ></DD @@ -184,9 +199,12 @@ CLASS="PARAMETER" >hosts deny</I ></TT > - parameters in the <TT -CLASS="FILENAME" ->smb.conf</TT + parameters in the <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smb.conf</SPAN +>(5)</SPAN > file to determine if the hostname with this IP address would be allowed access to the <B @@ -210,7 +228,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN77" +NAME="AEN87" ></A ><H2 >FILES</H2 @@ -220,16 +238,22 @@ NAME="AEN77" CLASS="VARIABLELIST" ><DL ><DT -><TT -CLASS="FILENAME" ->smb.conf</TT +><SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smb.conf</SPAN +>(5)</SPAN ></DT ><DD ><P >This is usually the name of the configuration - file used by <B -CLASS="COMMAND" ->smbd</B + file used by <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbd</SPAN +>(8)</SPAN >. </P ></DD @@ -239,7 +263,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN86" +NAME="AEN100" ></A ><H2 >DIAGNOSTICS</H2 @@ -253,7 +277,7 @@ NAME="AEN86" ><DIV CLASS="REFSECT1" ><A -NAME="AEN89" +NAME="AEN103" ></A ><H2 >VERSION</H2 @@ -264,33 +288,29 @@ NAME="AEN89" ><DIV CLASS="REFSECT1" ><A -NAME="AEN92" +NAME="AEN106" ></A ><H2 >SEE ALSO</H2 ><P -><A -HREF="smb.conf.5.html" -TARGET="_top" -><TT -CLASS="FILENAME" ->smb.conf(5)</TT -></A ->, - <A -HREF="smbd.8.html" -TARGET="_top" -><B -CLASS="COMMAND" ->smbd(8)</B -></A -> - </P +><SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smb.conf</SPAN +>(5)</SPAN +>, <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbd</SPAN +>(8)</SPAN +></P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN99" +NAME="AEN115" ></A ><H2 >AUTHOR</H2 @@ -302,14 +322,14 @@ NAME="AEN99" ><P >The original Samba man pages were written by Karl Auer. The man page sources were converted to YODL format (another - excellent piece of Open Source software, available at - <A + excellent piece of Open Source software, available at <A HREF="ftp://ftp.icce.rug.nl/pub/unix/" TARGET="_top" > ftp://ftp.icce.rug.nl/pub/unix/</A >) and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for - Samba 2.2 was done by Gerald Carter</P + Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 + for Samba 3.0 was done by Alexander Bokovoy.</P ></DIV ></BODY ></HTML diff --git a/docs/htmldocs/testprns.1.html b/docs/htmldocs/testprns.1.html index 0225aad9d5..07513566af 100644 --- a/docs/htmldocs/testprns.1.html +++ b/docs/htmldocs/testprns.1.html @@ -5,7 +5,7 @@ >testprns</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77"></HEAD +CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"></HEAD ><BODY CLASS="REFENTRY" BGCOLOR="#FFFFFF" @@ -15,7 +15,7 @@ VLINK="#840084" ALINK="#0000FF" ><H1 ><A -NAME="TESTPRNS" +NAME="TESTPRNS.1" ></A >testprns</H1 ><DIV @@ -47,10 +47,12 @@ NAME="AEN13" ><H2 >DESCRIPTION</H2 ><P ->This tool is part of the <A -HREF="samba.7.html" -TARGET="_top" -> Samba</A +>This tool is part of the <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>Samba</SPAN +>(7)</SPAN > suite.</P ><P ><B @@ -58,14 +60,13 @@ CLASS="COMMAND" >testprns</B > is a very simple test program to determine whether a given printer name is valid for use in - a service to be provided by <A -HREF="smbd.8.html" -TARGET="_top" -><B -CLASS="COMMAND" -> smbd(8)</B -></A ->. </P + a service to be provided by <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbd</SPAN +>(8)</SPAN +>.</P ><P >"Valid" in this context means "can be found in the printcap specified". This program is very stupid - so stupid in @@ -75,7 +76,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN22" +NAME="AEN25" ></A ><H2 >OPTIONS</H2 @@ -103,10 +104,12 @@ CLASS="COMMAND" <B CLASS="COMMAND" >testprns</B -> finds the printer then - <B -CLASS="COMMAND" ->smbd</B +> finds the printer then <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbd</SPAN +>(8)</SPAN > should do so as well. </P ></DD ><DT @@ -129,7 +132,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN39" +NAME="AEN44" ></A ><H2 >FILES</H2 @@ -158,7 +161,7 @@ CLASS="FILENAME" ><DIV CLASS="REFSECT1" ><A -NAME="AEN48" +NAME="AEN53" ></A ><H2 >DIAGNOSTICS</H2 @@ -186,7 +189,7 @@ CLASS="FILENAME" ><DIV CLASS="REFSECT1" ><A -NAME="AEN55" +NAME="AEN60" ></A ><H2 >VERSION</H2 @@ -197,7 +200,7 @@ NAME="AEN55" ><DIV CLASS="REFSECT1" ><A -NAME="AEN58" +NAME="AEN63" ></A ><H2 >SEE ALSO</H2 @@ -206,28 +209,24 @@ NAME="AEN58" CLASS="FILENAME" >printcap(5)</TT >, - <A -HREF="smbd.8.html" -TARGET="_top" -><B -CLASS="COMMAND" ->smbd(8)</B -></A ->, - <A -HREF="smbclient.1.html" -TARGET="_top" -><B -CLASS="COMMAND" ->smbclient(1)</B -></A -> - </P + <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbd</SPAN +>(8)</SPAN +>, <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smbclient</SPAN +>(1)</SPAN +></P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN66" +NAME="AEN73" ></A ><H2 >AUTHOR</H2 @@ -239,14 +238,14 @@ NAME="AEN66" ><P >The original Samba man pages were written by Karl Auer. The man page sources were converted to YODL format (another - excellent piece of Open Source software, available at - <A + excellent piece of Open Source software, available at <A HREF="ftp://ftp.icce.rug.nl/pub/unix/" TARGET="_top" > ftp://ftp.icce.rug.nl/pub/unix/</A >) and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for - Samba 2.2 was done by Gerald Carter</P + Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 + for Samba 3.0 was done by Alexander Bokovoy.</P ></DIV ></BODY ></HTML diff --git a/docs/htmldocs/type.html b/docs/htmldocs/type.html index e3f09acc18..be7e722b2e 100644 --- a/docs/htmldocs/type.html +++ b/docs/htmldocs/type.html @@ -5,14 +5,13 @@ >Type of installation</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ -"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK REL="PREVIOUS" -TITLE="LanMan and NT Password Encryption in Samba" -HREF="pwencrypt.html"><LINK +TITLE="User information database" +HREF="passdb.html"><LINK REL="NEXT" TITLE="User and Share security level (for servers not in a domain)" HREF="securitylevels.html"></HEAD @@ -43,7 +42,7 @@ WIDTH="10%" ALIGN="left" VALIGN="bottom" ><A -HREF="pwencrypt.html" +HREF="passdb.html" ACCESSKEY="P" >Prev</A ></TD @@ -69,7 +68,9 @@ WIDTH="100%"></DIV ><DIV CLASS="PART" ><A -NAME="TYPE"><DIV +NAME="TYPE" +></A +><DIV CLASS="TITLEPAGE" ><H1 CLASS="TITLE" @@ -77,7 +78,9 @@ CLASS="TITLE" ><DIV CLASS="PARTINTRO" ><A -NAME="AEN531"><H1 +NAME="AEN678" +></A +><H1 >Introduction</H1 ><P >Samba can operate in various SMB networks. This part contains information on configuring samba @@ -91,233 +94,238 @@ CLASS="TOC" >Table of Contents</B ></DT ><DT ->5. <A +>4. <A HREF="securitylevels.html" >User and Share security level (for servers not in a domain)</A ></DT ><DT ->6. <A +>5. <A HREF="samba-pdc.html" ->How to Configure Samba as a NT4 Primary Domain Controller</A +>Samba as a NT4 or Win2k Primary Domain Controller</A ></DT ><DD ><DL ><DT ->6.1. <A -HREF="samba-pdc.html#AEN575" +>5.1. <A +HREF="samba-pdc.html#AEN722" >Prerequisite Reading</A ></DT ><DT ->6.2. <A -HREF="samba-pdc.html#AEN581" +>5.2. <A +HREF="samba-pdc.html#AEN728" >Background</A ></DT ><DT ->6.3. <A -HREF="samba-pdc.html#AEN620" +>5.3. <A +HREF="samba-pdc.html#AEN767" >Configuring the Samba Domain Controller</A ></DT ><DT ->6.4. <A -HREF="samba-pdc.html#AEN663" +>5.4. <A +HREF="samba-pdc.html#AEN810" >Creating Machine Trust Accounts and Joining Clients to the Domain</A ></DT ><DD ><DL ><DT ->6.4.1. <A -HREF="samba-pdc.html#AEN682" +>5.4.1. <A +HREF="samba-pdc.html#AEN829" >Manual Creation of Machine Trust Accounts</A ></DT ><DT ->6.4.2. <A -HREF="samba-pdc.html#AEN723" +>5.4.2. <A +HREF="samba-pdc.html#AEN870" >"On-the-Fly" Creation of Machine Trust Accounts</A ></DT ><DT ->6.4.3. <A -HREF="samba-pdc.html#AEN732" +>5.4.3. <A +HREF="samba-pdc.html#AEN879" >Joining the Client to the Domain</A ></DT ></DL ></DD ><DT ->6.5. <A -HREF="samba-pdc.html#AEN747" +>5.5. <A +HREF="samba-pdc.html#AEN894" >Common Problems and Errors</A ></DT ><DT ->6.6. <A -HREF="samba-pdc.html#AEN795" +>5.6. <A +HREF="samba-pdc.html#AEN942" >System Policies and Profiles</A ></DT ><DT ->6.7. <A -HREF="samba-pdc.html#AEN839" +>5.7. <A +HREF="samba-pdc.html#AEN986" >What other help can I get?</A ></DT ><DT ->6.8. <A -HREF="samba-pdc.html#AEN953" +>5.8. <A +HREF="samba-pdc.html#AEN1100" >Domain Control for Windows 9x/ME</A ></DT ><DD ><DL ><DT ->6.8.1. <A -HREF="samba-pdc.html#AEN979" +>5.8.1. <A +HREF="samba-pdc.html#AEN1126" >Configuration Instructions: Network Logons</A ></DT ><DT ->6.8.2. <A -HREF="samba-pdc.html#AEN998" +>5.8.2. <A +HREF="samba-pdc.html#AEN1145" >Configuration Instructions: Setting up Roaming User Profiles</A ></DT ></DL ></DD ><DT ->6.9. <A -HREF="samba-pdc.html#AEN1091" ->DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba</A +>5.9. <A +HREF="samba-pdc.html#AEN1238" +>DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba</A ></DT ></DL ></DD ><DT ->7. <A +>6. <A HREF="samba-bdc.html" >How to Act as a Backup Domain Controller in a Purely Samba Controlled Domain</A ></DT ><DD ><DL ><DT ->7.1. <A -HREF="samba-bdc.html#AEN1127" +>6.1. <A +HREF="samba-bdc.html#AEN1274" >Prerequisite Reading</A ></DT ><DT ->7.2. <A -HREF="samba-bdc.html#AEN1131" +>6.2. <A +HREF="samba-bdc.html#AEN1278" >Background</A ></DT ><DT ->7.3. <A -HREF="samba-bdc.html#AEN1139" +>6.3. <A +HREF="samba-bdc.html#AEN1286" >What qualifies a Domain Controller on the network?</A ></DT ><DD ><DL ><DT ->7.3.1. <A -HREF="samba-bdc.html#AEN1142" +>6.3.1. <A +HREF="samba-bdc.html#AEN1289" >How does a Workstation find its domain controller?</A ></DT ><DT ->7.3.2. <A -HREF="samba-bdc.html#AEN1145" +>6.3.2. <A +HREF="samba-bdc.html#AEN1292" >When is the PDC needed?</A ></DT ></DL ></DD ><DT ->7.4. <A -HREF="samba-bdc.html#AEN1148" ->Can Samba be a Backup Domain Controller?</A +>6.4. <A +HREF="samba-bdc.html#AEN1295" +>Can Samba be a Backup Domain Controller to an NT PDC?</A ></DT ><DT ->7.5. <A -HREF="samba-bdc.html#AEN1152" +>6.5. <A +HREF="samba-bdc.html#AEN1300" >How do I set up a Samba BDC?</A ></DT ><DD ><DL ><DT ->7.5.1. <A -HREF="samba-bdc.html#AEN1169" +>6.5.1. <A +HREF="samba-bdc.html#AEN1317" >How do I replicate the smbpasswd file?</A ></DT +><DT +>6.5.2. <A +HREF="samba-bdc.html#AEN1321" +>Can I do this all with LDAP?</A +></DT ></DL ></DD ></DL ></DD ><DT ->8. <A +>7. <A HREF="ads.html" >Samba as a ADS domain member</A ></DT ><DD ><DL ><DT ->8.1. <A -HREF="ads.html#AEN1187" +>7.1. <A +HREF="ads.html#AEN1339" >Installing the required packages for Debian</A ></DT ><DT ->8.2. <A -HREF="ads.html#AEN1193" +>7.2. <A +HREF="ads.html#AEN1346" >Installing the required packages for RedHat</A ></DT ><DT ->8.3. <A -HREF="ads.html#AEN1202" +>7.3. <A +HREF="ads.html#AEN1356" >Compile Samba</A ></DT ><DT ->8.4. <A -HREF="ads.html#AEN1217" +>7.4. <A +HREF="ads.html#AEN1371" >Setup your /etc/krb5.conf</A ></DT ><DT ->8.5. <A -HREF="ads.html#AEN1227" +>7.5. <A +HREF="ads.html#AEN1381" >Create the computer account</A ></DT ><DD ><DL ><DT ->8.5.1. <A -HREF="ads.html#AEN1231" +>7.5.1. <A +HREF="ads.html#AEN1385" >Possible errors</A ></DT ></DL ></DD ><DT ->8.6. <A -HREF="ads.html#AEN1243" +>7.6. <A +HREF="ads.html#AEN1393" >Test your server setup</A ></DT ><DT ->8.7. <A -HREF="ads.html#AEN1248" +>7.7. <A +HREF="ads.html#AEN1398" >Testing with smbclient</A ></DT ><DT ->8.8. <A -HREF="ads.html#AEN1251" +>7.8. <A +HREF="ads.html#AEN1401" >Notes</A ></DT ></DL ></DD ><DT ->9. <A +>8. <A HREF="domain-security.html" ->Samba as a NT4 domain member</A +>Samba as a NT4 or Win2k domain member</A ></DT ><DD ><DL ><DT ->9.1. <A -HREF="domain-security.html#AEN1273" ->Joining an NT Domain with Samba 2.2</A +>8.1. <A +HREF="domain-security.html#AEN1423" +>Joining an NT Domain with Samba 3.0</A ></DT ><DT ->9.2. <A -HREF="domain-security.html#AEN1337" +>8.2. <A +HREF="domain-security.html#AEN1478" >Samba and Windows 2000 Domains</A ></DT ><DT ->9.3. <A -HREF="domain-security.html#AEN1342" +>8.3. <A +HREF="domain-security.html#AEN1481" >Why is this better than security = server?</A ></DT ></DL @@ -342,7 +350,7 @@ WIDTH="33%" ALIGN="left" VALIGN="top" ><A -HREF="pwencrypt.html" +HREF="passdb.html" ACCESSKEY="P" >Prev</A ></TD @@ -370,7 +378,7 @@ ACCESSKEY="N" WIDTH="33%" ALIGN="left" VALIGN="top" ->LanMan and NT Password Encryption in Samba</TD +>User information database</TD ><TD WIDTH="34%" ALIGN="center" diff --git a/docs/htmldocs/unix-permissions.html b/docs/htmldocs/unix-permissions.html index f29d450e6d..71198ecaa6 100644 --- a/docs/htmldocs/unix-permissions.html +++ b/docs/htmldocs/unix-permissions.html @@ -5,8 +5,7 @@ >UNIX Permission Bits and Windows NT Access Control Lists</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ -"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -74,13 +73,17 @@ WIDTH="100%"></DIV CLASS="CHAPTER" ><H1 ><A -NAME="UNIX-PERMISSIONS">Chapter 11. UNIX Permission Bits and Windows NT Access Control Lists</H1 +NAME="UNIX-PERMISSIONS" +></A +>Chapter 10. UNIX Permission Bits and Windows NT Access Control Lists</H1 ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1605">11.1. Viewing and changing UNIX permissions using the NT +NAME="AEN1744" +></A +>10.1. Viewing and changing UNIX permissions using the NT security dialogs</H1 ><P >New in the Samba 2.0.4 release is the ability for Windows @@ -91,33 +94,15 @@ NAME="AEN1605">11.1. Viewing and changing UNIX permissions using the NT the security of the UNIX host Samba is running on, and still obeys all the file permission rules that a Samba administrator can set.</P -><P ->In Samba 2.0.4 and above the default value of the - parameter <A -HREF="smb.conf.5.html#NTACLSUPPORT" -TARGET="_top" -><TT -CLASS="PARAMETER" -><I -> nt acl support</I -></TT -></A -> has been changed from - <TT -CLASS="CONSTANT" ->false</TT -> to <TT -CLASS="CONSTANT" ->true</TT ->, so - manipulation of permissions is turned on by default.</P ></DIV ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1614">11.2. How to view file security on a Samba share</H1 +NAME="AEN1748" +></A +>10.2. How to view file security on a Samba share</H1 ><P >From an NT 4.0 client, single-click with the right mouse button on any file or directory in a Samba mounted @@ -185,7 +170,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1625">11.3. Viewing file ownership</H1 +NAME="AEN1759" +></A +>10.3. Viewing file ownership</H1 ><P >Clicking on the <B CLASS="COMMAND" @@ -277,7 +264,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1645">11.4. Viewing file or directory permissions</H1 +NAME="AEN1779" +></A +>10.4. Viewing file or directory permissions</H1 ><P >The third button is the <B CLASS="COMMAND" @@ -337,7 +326,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1660">11.4.1. File Permissions</H2 +NAME="AEN1794" +></A +>10.4.1. File Permissions</H2 ><P >The standard UNIX user/group/world triple and the corresponding "read", "write", "execute" permissions @@ -397,7 +388,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1674">11.4.2. Directory Permissions</H2 +NAME="AEN1808" +></A +>10.4.2. Directory Permissions</H2 ><P >Directories on an NT NTFS file system have two different sets of permissions. The first set of permissions @@ -427,7 +420,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1681">11.5. Modifying file or directory permissions</H1 +NAME="AEN1815" +></A +>10.5. Modifying file or directory permissions</H1 ><P >Modifying file and directory permissions is as simple as changing the displayed permissions in the dialog box, and @@ -523,7 +518,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1703">11.6. Interaction with the standard Samba create mask +NAME="AEN1837" +></A +>10.6. Interaction with the standard Samba create mask parameters</H1 ><P >Note that with Samba 2.0.5 there are four new parameters @@ -798,7 +795,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1767">11.7. Interaction with the standard Samba file attribute +NAME="AEN1901" +></A +>10.7. Interaction with the standard Samba file attribute mapping</H1 ><P >Samba maps some of the DOS attribute bits (such as "read diff --git a/docs/htmldocs/vfs.html b/docs/htmldocs/vfs.html index 11934ae47c..0e39297ebb 100644 --- a/docs/htmldocs/vfs.html +++ b/docs/htmldocs/vfs.html @@ -5,8 +5,7 @@ >Stackable VFS modules</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ -"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -14,11 +13,11 @@ REL="UP" TITLE="Optional configuration" HREF="optional.html"><LINK REL="PREVIOUS" -TITLE="Passdb XML plugin" -HREF="pdb-xml.html"><LINK +TITLE="Improved browsing in samba" +HREF="improved-browsing.html"><LINK REL="NEXT" -TITLE="Storing Samba's User/Machine Account information in an LDAP Directory" -HREF="samba-ldap-howto.html"></HEAD +TITLE="Access Samba source code via CVS" +HREF="cvs-access.html"></HEAD ><BODY CLASS="CHAPTER" BGCOLOR="#FFFFFF" @@ -46,7 +45,7 @@ WIDTH="10%" ALIGN="left" VALIGN="bottom" ><A -HREF="pdb-xml.html" +HREF="improved-browsing.html" ACCESSKEY="P" >Prev</A ></TD @@ -60,7 +59,7 @@ WIDTH="10%" ALIGN="right" VALIGN="bottom" ><A -HREF="samba-ldap-howto.html" +HREF="cvs-access.html" ACCESSKEY="N" >Next</A ></TD @@ -73,13 +72,17 @@ WIDTH="100%"></DIV CLASS="CHAPTER" ><H1 ><A -NAME="VFS">Chapter 18. Stackable VFS modules</H1 +NAME="VFS" +></A +>Chapter 16. Stackable VFS modules</H1 ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2640">18.1. Introduction and configuration</H1 +NAME="AEN2855" +></A +>16.1. Introduction and configuration</H1 ><P >Since samba 3.0, samba supports stackable VFS(Virtual File System) modules. Samba passes each request to access the unix file system thru the loaded VFS modules. @@ -118,13 +121,17 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2649">18.2. Included modules</H1 +NAME="AEN2864" +></A +>16.2. Included modules</H1 ><DIV CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2651">18.2.1. audit</H2 +NAME="AEN2866" +></A +>16.2.1. audit</H2 ><P >A simple module to audit file access to the syslog facility. The following operations are logged: @@ -160,7 +167,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2659">18.2.2. recycle</H2 +NAME="AEN2874" +></A +>16.2.2. recycle</H2 ><P >A recycle-bin like modules. When used any unlink call will be intercepted and files moved to the recycle @@ -229,7 +238,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2696">18.2.3. netatalk</H2 +NAME="AEN2911" +></A +>16.2.3. netatalk</H2 ><P >A netatalk module, that will ease co-existence of samba and netatalk file sharing services.</P @@ -260,7 +271,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2703">18.3. VFS modules available elsewhere</H1 +NAME="AEN2918" +></A +>16.3. VFS modules available elsewhere</H1 ><P >This section contains a listing of various other VFS modules that have been posted but don't currently reside in the Samba CVS @@ -274,7 +287,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2707">18.3.1. DatabaseFS</H2 +NAME="AEN2922" +></A +>16.3.1. DatabaseFS</H2 ><P >URL: <A HREF="http://www.css.tayloru.edu/~elorimer/databasefs/index.php" @@ -306,7 +321,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2715">18.3.2. vscan</H2 +NAME="AEN2930" +></A +>16.3.2. vscan</H2 ><P >URL: <A HREF="http://www.openantivirus.org/" @@ -338,7 +355,7 @@ WIDTH="33%" ALIGN="left" VALIGN="top" ><A -HREF="pdb-xml.html" +HREF="improved-browsing.html" ACCESSKEY="P" >Prev</A ></TD @@ -356,7 +373,7 @@ WIDTH="33%" ALIGN="right" VALIGN="top" ><A -HREF="samba-ldap-howto.html" +HREF="cvs-access.html" ACCESSKEY="N" >Next</A ></TD @@ -366,7 +383,7 @@ ACCESSKEY="N" WIDTH="33%" ALIGN="left" VALIGN="top" ->Passdb XML plugin</TD +>Improved browsing in samba</TD ><TD WIDTH="34%" ALIGN="center" @@ -380,7 +397,7 @@ ACCESSKEY="U" WIDTH="33%" ALIGN="right" VALIGN="top" ->Storing Samba's User/Machine Account information in an LDAP Directory</TD +>Access Samba source code via CVS</TD ></TR ></TABLE ></DIV diff --git a/docs/htmldocs/vfstest.1.html b/docs/htmldocs/vfstest.1.html index 1fd7880805..56c409288a 100644 --- a/docs/htmldocs/vfstest.1.html +++ b/docs/htmldocs/vfstest.1.html @@ -1,12 +1,11 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"> +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <HTML ><HEAD ><TITLE >vfstest</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ -"></HEAD +CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"></HEAD ><BODY CLASS="REFENTRY" BGCOLOR="#FFFFFF" @@ -16,7 +15,9 @@ VLINK="#840084" ALINK="#0000FF" ><H1 ><A -NAME="VFSTEST">vfstest</H1 +NAME="VFSTEST.1" +></A +>vfstest</H1 ><DIV CLASS="REFNAMEDIV" ><A @@ -28,13 +29,15 @@ NAME="AEN5" ><DIV CLASS="REFSYNOPSISDIV" ><A -NAME="AEN8"><H2 +NAME="AEN8" +></A +><H2 >Synopsis</H2 ><P ><B CLASS="COMMAND" >vfstest</B -> [-d debuglevel] [-c command] [-l logfile] [-h]</P +> [-d debuglevel] [-c command] [-l logfile] [-h]</P ></DIV ><DIV CLASS="REFSECT1" @@ -44,10 +47,12 @@ NAME="AEN15" ><H2 >DESCRIPTION</H2 ><P ->This tool is part of the <A -HREF="samba.7.html" -TARGET="_top" -> Samba</A +>This tool is part of the <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>Samba</SPAN +>(7)</SPAN > suite.</P ><P ><B @@ -62,7 +67,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN21" +NAME="AEN23" ></A ><H2 >OPTIONS</H2 @@ -144,14 +149,17 @@ CLASS="CONSTANT" ><DIV CLASS="REFSECT1" ><A -NAME="AEN48" +NAME="AEN50" ></A ><H2 >COMMANDS</H2 ><P +><SPAN +CLASS="emphasis" ><I CLASS="EMPHASIS" >VFS COMMANDS</I +></SPAN ></P ><P ></P @@ -160,14 +168,14 @@ CLASS="EMPHASIS" ><P ><B CLASS="COMMAND" ->load <module.so></B +>load <module.so></B > - Load specified VFS module </P ></LI ><LI ><P ><B CLASS="COMMAND" ->populate <char> <size></B +>populate <char> <size></B > - Populate a data buffer with the specified data </P ></LI @@ -175,7 +183,7 @@ CLASS="COMMAND" ><P ><B CLASS="COMMAND" ->showdata [<offset> <len>]</B +>showdata [<offset> <len>]</B > - Show data currently in data buffer </P ></LI @@ -412,9 +420,12 @@ CLASS="COMMAND" ></LI ></UL ><P +><SPAN +CLASS="emphasis" ><I CLASS="EMPHASIS" >GENERAL COMMANDS</I +></SPAN ></P ><P ></P @@ -423,21 +434,21 @@ CLASS="EMPHASIS" ><P ><B CLASS="COMMAND" ->conf <smb.conf></B +>conf <smb.conf></B > - Load a different configuration file</P ></LI ><LI ><P ><B CLASS="COMMAND" ->help [<command>]</B +>help [<command>]</B > - Get list of commands or info about specified command</P ></LI ><LI ><P ><B CLASS="COMMAND" ->debuglevel <level></B +>debuglevel <level></B > - Set debug level</P ></LI ><LI @@ -459,7 +470,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN179" +NAME="AEN181" ></A ><H2 >VERSION</H2 @@ -470,7 +481,7 @@ NAME="AEN179" ><DIV CLASS="REFSECT1" ><A -NAME="AEN182" +NAME="AEN184" ></A ><H2 >AUTHOR</H2 diff --git a/docs/htmldocs/wbinfo.1.html b/docs/htmldocs/wbinfo.1.html index a8aa065eed..cf46eca0ef 100644 --- a/docs/htmldocs/wbinfo.1.html +++ b/docs/htmldocs/wbinfo.1.html @@ -5,7 +5,7 @@ >wbinfo</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77"></HEAD +CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"></HEAD ><BODY CLASS="REFENTRY" BGCOLOR="#FFFFFF" @@ -15,7 +15,7 @@ VLINK="#840084" ALINK="#0000FF" ><H1 ><A -NAME="WBINFO" +NAME="WBINFO.1" ></A >wbinfo</H1 ><DIV @@ -47,28 +47,32 @@ NAME="AEN27" ><H2 >DESCRIPTION</H2 ><P ->This tool is part of the <A -HREF="samba.7.html" -TARGET="_top" -> Samba</A +>This tool is part of the <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>Samba</SPAN +>(7)</SPAN > suite.</P ><P >The <B CLASS="COMMAND" >wbinfo</B > program queries and returns information - created and used by the <A -HREF="winbindd.8.html" -TARGET="_top" -><B -CLASS="COMMAND" -> winbindd(8)</B -></A + created and used by the <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>winbindd</SPAN +>(8)</SPAN > daemon. </P ><P ->The <B -CLASS="COMMAND" ->winbindd(8)</B +>The <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>winbindd</SPAN +>(8)</SPAN > daemon must be configured and running for the <B CLASS="COMMAND" @@ -79,7 +83,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN38" +NAME="AEN43" ></A ><H2 >OPTIONS</H2 @@ -93,33 +97,43 @@ CLASS="VARIABLELIST" ><DD ><P >This option will list all users available - in the Windows NT domain for which the <B -CLASS="COMMAND" ->winbindd(8) - </B + in the Windows NT domain for which the <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>winbindd</SPAN +>(8)</SPAN > daemon is operating in. Users in all trusted domains will also be listed. Note that this operation does not assign - user ids to any users that have not already been seen by - <B -CLASS="COMMAND" ->winbindd(8)</B ->.</P + user ids to any users that have not already been seen by <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>winbindd</SPAN +>(8)</SPAN +> + .</P ></DD ><DT >-g</DT ><DD ><P >This option will list all groups available - in the Windows NT domain for which the <B -CLASS="COMMAND" ->winbindd(8) - </B + in the Windows NT domain for which the <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>Samba</SPAN +>(7)</SPAN > daemon is operating in. Groups in all trusted domains will also be listed. Note that this operation does not assign - group ids to any groups that have not already been seen by - <B -CLASS="COMMAND" ->winbindd(8)</B + group ids to any groups that have not already been + seen by <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>winbindd</SPAN +>(8)</SPAN >. </P ></DD ><DT @@ -132,9 +146,12 @@ CLASS="PARAMETER" >-N</I ></TT > option - queries <B -CLASS="COMMAND" ->winbindd(8)</B + queries <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>winbindd</SPAN +>(8)</SPAN > to query the WINS server for the IP address associated with the NetBIOS name specified by the <TT @@ -155,9 +172,12 @@ CLASS="PARAMETER" >-I</I ></TT > option - queries <B -CLASS="COMMAND" ->winbindd(8)</B + queries <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>winbindd</SPAN +>(8)</SPAN > to send a node status request to get the NetBIOS name associated with the IP address specified by the <TT @@ -178,22 +198,28 @@ CLASS="PARAMETER" >-n</I ></TT > option - queries <B -CLASS="COMMAND" ->winbindd(8)</B + queries <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>winbindd</SPAN +>(8)</SPAN > for the SID associated with the name specified. Domain names can be specified before the user name by using the winbind separator character. For example CWDOM1/Administrator refers to the Administrator user in the domain CWDOM1. If no domain is specified then the - domain used is the one specified in the <TT -CLASS="FILENAME" ->smb.conf</TT -> - <TT + domain used is the one specified in the <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smb.conf</SPAN +>(5)</SPAN +> <TT CLASS="PARAMETER" ><I ->workgroup</I +>workgroup + </I ></TT > parameter. </P ></DD @@ -238,9 +264,12 @@ CLASS="PARAMETER" ><DD ><P >Convert a SID to a UNIX user id. If the SID - does not correspond to a UNIX user mapped by <B -CLASS="COMMAND" -> winbindd(8)</B + does not correspond to a UNIX user mapped by <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>winbindd</SPAN +>(8)</SPAN > then the operation will fail. </P ></DD ><DT @@ -248,10 +277,14 @@ CLASS="COMMAND" ><DD ><P >Convert a SID to a UNIX group id. If the SID - does not correspond to a UNIX group mapped by <B -CLASS="COMMAND" -> winbindd(8)</B -> then the operation will fail. </P + does not correspond to a UNIX group mapped by <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>winbindd</SPAN +>(8)</SPAN +> then + the operation will fail. </P ></DD ><DT >-t</DT @@ -266,9 +299,12 @@ CLASS="COMMAND" ><DD ><P >Produce a list of domains trusted by the - Windows NT server <B -CLASS="COMMAND" ->winbindd(8)</B + Windows NT server <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>winbindd</SPAN +>(8)</SPAN > contacts when resolving names. This list does not include the Windows NT domain the server is a Primary Domain Controller for. @@ -308,16 +344,18 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN120" +NAME="AEN147" ></A ><H2 >EXIT STATUS</H2 ><P >The wbinfo program returns 0 if the operation - succeeded, or 1 if the operation failed. If the <B -CLASS="COMMAND" ->winbindd(8) - </B + succeeded, or 1 if the operation failed. If the <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>winbindd</SPAN +>(8)</SPAN > daemon is not working <B CLASS="COMMAND" >wbinfo</B @@ -327,7 +365,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN125" +NAME="AEN154" ></A ><H2 >VERSION</H2 @@ -338,25 +376,23 @@ NAME="AEN125" ><DIV CLASS="REFSECT1" ><A -NAME="AEN128" +NAME="AEN157" ></A ><H2 >SEE ALSO</H2 ><P -><A -HREF="winbindd.8.html" -TARGET="_top" -><B -CLASS="COMMAND" ->winbindd(8)</B -> - </A +><SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>winbindd</SPAN +>(8)</SPAN ></P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN133" +NAME="AEN163" ></A ><H2 >AUTHOR</H2 @@ -376,7 +412,8 @@ CLASS="COMMAND" were written by Tim Potter.</P ><P >The conversion to DocBook for Samba 2.2 was done - by Gerald Carter</P + by Gerald Carter. The conversion to DocBook XML 4.2 for Samba + 3.0 was done by Alexander Bokovoy.</P ></DIV ></BODY ></HTML diff --git a/docs/htmldocs/winbind.html b/docs/htmldocs/winbind.html index 1558512a61..d587696817 100644 --- a/docs/htmldocs/winbind.html +++ b/docs/htmldocs/winbind.html @@ -5,8 +5,7 @@ >Unified Logons between Windows NT and UNIX using Winbind</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ -"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -17,8 +16,8 @@ REL="PREVIOUS" TITLE="Printing Support" HREF="printing.html"><LINK REL="NEXT" -TITLE="Passdb MySQL plugin" -HREF="pdb-mysql.html"></HEAD +TITLE="Improved browsing in samba" +HREF="improved-browsing.html"></HEAD ><BODY CLASS="CHAPTER" BGCOLOR="#FFFFFF" @@ -60,7 +59,7 @@ WIDTH="10%" ALIGN="right" VALIGN="bottom" ><A -HREF="pdb-mysql.html" +HREF="improved-browsing.html" ACCESSKEY="N" >Next</A ></TD @@ -73,13 +72,17 @@ WIDTH="100%"></DIV CLASS="CHAPTER" ><H1 ><A -NAME="WINBIND">Chapter 15. Unified Logons between Windows NT and UNIX using Winbind</H1 +NAME="WINBIND" +></A +>Chapter 14. Unified Logons between Windows NT and UNIX using Winbind</H1 ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2225">15.1. Abstract</H1 +NAME="AEN2360" +></A +>14.1. Abstract</H1 ><P >Integration of UNIX and Microsoft Windows NT through a unified logon has been considered a "holy grail" in heterogeneous @@ -104,7 +107,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2229">15.2. Introduction</H1 +NAME="AEN2364" +></A +>14.2. Introduction</H1 ><P >It is well known that UNIX and Microsoft Windows NT have different models for representing user and group information and @@ -156,7 +161,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2242">15.3. What Winbind Provides</H1 +NAME="AEN2377" +></A +>14.3. What Winbind Provides</H1 ><P >Winbind unifies UNIX and Windows NT account management by allowing a UNIX box to become a full member of a NT domain. Once @@ -196,7 +203,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2249">15.3.1. Target Uses</H2 +NAME="AEN2384" +></A +>14.3.1. Target Uses</H2 ><P >Winbind is targeted at organizations that have an existing NT based domain infrastructure into which they wish @@ -218,7 +227,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2253">15.4. How Winbind Works</H1 +NAME="AEN2388" +></A +>14.4. How Winbind Works</H1 ><P >The winbind system is designed around a client/server architecture. A long running <B @@ -236,9 +247,11 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2258">15.4.1. Microsoft Remote Procedure Calls</H2 +NAME="AEN2393" +></A +>14.4.1. Microsoft Remote Procedure Calls</H2 ><P ->Over the last two years, efforts have been underway +>Over the last few years, efforts have been underway by various Samba Team members to decode various aspects of the Microsoft Remote Procedure Call (MSRPC) system. This system is used for most network related operations between @@ -260,7 +273,28 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2262">15.4.2. Name Service Switch</H2 +NAME="AEN2397" +></A +>14.4.2. Microsoft Active Directory Services</H2 +><P +> Since late 2001, Samba has gained the ability to + interact with Microsoft Windows 2000 using its 'Native + Mode' protocols, rather than the NT4 RPC services. + Using LDAP and Kerberos, a domain member running + winbind can enumerate users and groups in exactly the + same way as a Win2k client would, and in so doing + provide a much more efficient and + effective winbind implementation. + </P +></DIV +><DIV +CLASS="SECT2" +><H2 +CLASS="SECT2" +><A +NAME="AEN2400" +></A +>14.4.3. Name Service Switch</H2 ><P >The Name Service Switch, or NSS, is a feature that is present in many UNIX operating systems. It allows system @@ -338,7 +372,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2278">15.4.3. Pluggable Authentication Modules</H2 +NAME="AEN2416" +></A +>14.4.4. Pluggable Authentication Modules</H2 ><P >Pluggable Authentication Modules, also known as PAM, is a system for abstracting authentication and authorization @@ -385,7 +421,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2286">15.4.4. User and Group ID Allocation</H2 +NAME="AEN2424" +></A +>14.4.5. User and Group ID Allocation</H2 ><P >When a user or group is created under Windows NT is it allocated a numerical relative identifier (RID). This is @@ -409,7 +447,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2290">15.4.5. Result Caching</H2 +NAME="AEN2428" +></A +>14.4.6. Result Caching</H2 ><P >An active system can generate a lot of user and group name lookups. To reduce the network cost of these lookups winbind @@ -430,7 +470,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2293">15.5. Installation and Configuration</H1 +NAME="AEN2431" +></A +>14.5. Installation and Configuration</H1 ><P >Many thanks to John Trostel <A HREF="mailto:jtrostel@snapserver.com" @@ -455,7 +497,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2300">15.5.1. Introduction</H2 +NAME="AEN2438" +></A +>14.5.1. Introduction</H2 ><P >This HOWTO describes the procedures used to get winbind up and running on my RedHat 7.1 system. Winbind is capable of providing access @@ -512,7 +556,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2313">15.5.2. Requirements</H2 +NAME="AEN2451" +></A +>14.5.2. Requirements</H2 ><P >If you have a samba configuration file that you are currently using... <SPAN @@ -580,7 +626,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2327">15.5.3. Testing Things Out</H2 +NAME="AEN2465" +></A +>14.5.3. Testing Things Out</H2 ><P >Before starting, it is probably best to kill off all the SAMBA related daemons running on your server. Kill off all <B @@ -623,7 +671,9 @@ CLASS="SECT3" ><H3 CLASS="SECT3" ><A -NAME="AEN2338">15.5.3.1. Configure and compile SAMBA</H3 +NAME="AEN2476" +></A +>14.5.3.1. Configure and compile SAMBA</H3 ><P >The configuration and compilation of SAMBA is pretty straightforward. The first three steps may not be necessary depending upon @@ -657,7 +707,7 @@ CLASS="PROMPT" >root#</TT > <B CLASS="COMMAND" ->./configure --with-winbind</B +>./configure</B > <TT CLASS="PROMPT" @@ -687,7 +737,9 @@ CLASS="SECT3" ><H3 CLASS="SECT3" ><A -NAME="AEN2357">15.5.3.2. Configure <TT +NAME="AEN2495" +></A +>14.5.3.2. Configure <TT CLASS="FILENAME" >nsswitch.conf</TT > and the @@ -790,7 +842,9 @@ CLASS="SECT3" ><H3 CLASS="SECT3" ><A -NAME="AEN2390">15.5.3.3. Configure smb.conf</H3 +NAME="AEN2528" +></A +>14.5.3.3. Configure smb.conf</H3 ><P >Several parameters are needed in the smb.conf file to control the behavior of <B @@ -815,7 +869,7 @@ include the following entries in the [global] section:</P ><PRE CLASS="PROGRAMLISTING" >[global] - <...> + <...> # separate domain and username with '+', like DOMAIN+username <A HREF="winbindd.8.html#WINBINDSEPARATOR" @@ -863,7 +917,9 @@ CLASS="SECT3" ><H3 CLASS="SECT3" ><A -NAME="AEN2406">15.5.3.4. Join the SAMBA server to the PDC domain</H3 +NAME="AEN2544" +></A +>14.5.3.4. Join the SAMBA server to the PDC domain</H3 ><P >Enter the following command to make the SAMBA server join the PDC domain, where <TT @@ -885,7 +941,7 @@ CLASS="PROMPT" >root#</TT > <B CLASS="COMMAND" ->/usr/local/samba/bin/net rpc join -S PDC -U Administrator</B +>/usr/local/samba/bin/net join -S PDC -U Administrator</B ></P ><P >The proper response to the command should be: "Joined the domain @@ -907,7 +963,9 @@ CLASS="SECT3" ><H3 CLASS="SECT3" ><A -NAME="AEN2417">15.5.3.5. Start up the winbindd daemon and test it!</H3 +NAME="AEN2555" +></A +>14.5.3.5. Start up the winbindd daemon and test it!</H3 ><P >Eventually, you will want to modify your smb startup script to automatically invoke the winbindd daemon when the other parts of @@ -1028,13 +1086,17 @@ CLASS="SECT3" ><H3 CLASS="SECT3" ><A -NAME="AEN2453">15.5.3.6. Fix the init.d startup scripts</H3 +NAME="AEN2591" +></A +>14.5.3.6. Fix the init.d startup scripts</H3 ><DIV CLASS="SECT4" ><H4 CLASS="SECT4" ><A -NAME="AEN2455">15.5.3.6.1. Linux</H4 +NAME="AEN2593" +></A +>14.5.3.6.1. Linux</H4 ><P >The <B CLASS="COMMAND" @@ -1091,7 +1153,7 @@ CLASS="PROGRAMLISTING" daemon /usr/local/samba/bin/winbindd RETVAL3=$? echo - [ $RETVAL -eq 0 -a $RETVAL2 -eq 0 -a $RETVAL3 -eq 0 ] && touch /var/lock/subsys/smb || \ + [ $RETVAL -eq 0 -a $RETVAL2 -eq 0 -a $RETVAL3 -eq 0 ] && touch /var/lock/subsys/smb || \ RETVAL=1 return $RETVAL }</PRE @@ -1117,7 +1179,7 @@ CLASS="PROGRAMLISTING" echo -n $"Shutting down $KIND services: " killproc winbindd RETVAL3=$? - [ $RETVAL -eq 0 -a $RETVAL2 -eq 0 -a $RETVAL3 -eq 0 ] && rm -f /var/lock/subsys/smb + [ $RETVAL -eq 0 -a $RETVAL2 -eq 0 -a $RETVAL3 -eq 0 ] && rm -f /var/lock/subsys/smb echo "" return $RETVAL }</PRE @@ -1128,7 +1190,9 @@ CLASS="SECT4" ><H4 CLASS="SECT4" ><A -NAME="AEN2472">15.5.3.6.2. Solaris</H4 +NAME="AEN2610" +></A +>14.5.3.6.2. Solaris</H4 ><P >On solaris, you need to modify the <TT @@ -1157,7 +1221,7 @@ killproc() { # kill the named process(es) pid=`/usr/bin/ps -e | /usr/bin/grep -w $1 | /usr/bin/sed -e 's/^ *//' -e 's/ .*//'` - [ "$pid" != "" ] && kill $pid + [ "$pid" != "" ] && kill $pid } # Start/stop processes required for samba server @@ -1197,7 +1261,9 @@ CLASS="SECT4" ><H4 CLASS="SECT4" ><A -NAME="AEN2479">15.5.3.6.3. Restarting</H4 +NAME="AEN2617" +></A +>14.5.3.6.3. Restarting</H4 ><P >If you restart the <B CLASS="COMMAND" @@ -1219,7 +1285,9 @@ CLASS="SECT3" ><H3 CLASS="SECT3" ><A -NAME="AEN2485">15.5.3.7. Configure Winbind and PAM</H3 +NAME="AEN2623" +></A +>14.5.3.7. Configure Winbind and PAM</H3 ><P >If you have made it this far, you know that winbindd and samba are working together. If you want to use winbind to provide authentication for other @@ -1275,7 +1343,9 @@ CLASS="SECT4" ><H4 CLASS="SECT4" ><A -NAME="AEN2502">15.5.3.7.1. Linux/FreeBSD-specific PAM configuration</H4 +NAME="AEN2640" +></A +>14.5.3.7.1. Linux/FreeBSD-specific PAM configuration</H4 ><P >The <TT CLASS="FILENAME" @@ -1402,7 +1472,9 @@ CLASS="SECT4" ><H4 CLASS="SECT4" ><A -NAME="AEN2535">15.5.3.7.2. Solaris-specific configuration</H4 +NAME="AEN2673" +></A +>14.5.3.7.2. Solaris-specific configuration</H4 ><P >The /etc/pam.conf needs to be changed. I changed this file so that my Domain users can logon both locally as well as telnet.The following are the changes @@ -1476,7 +1548,7 @@ dtsession auth required /usr/lib/security/$ISA/pam_unix.so.1 >I also added a try_first_pass line after the winbind.so line to get rid of annoying double prompts for passwords.</P ><P ->Now restart your Samba & try connecting through your application that you +>Now restart your Samba and try connecting through your application that you configured in the pam.conf.</P ></DIV ></DIV @@ -1487,7 +1559,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2542">15.6. Limitations</H1 +NAME="AEN2680" +></A +>14.6. Limitations</H1 ><P >Winbind has a number of limitations in its current released version that we hope to overcome in future @@ -1498,7 +1572,7 @@ NAME="AEN2542">15.6. Limitations</H1 ><LI ><P >Winbind is currently only available for - the Linux operating system, although ports to other operating + the Linux, Solaris and IRIX operating systems, although ports to other operating systems are certainly possible. For such ports to be feasible, we require the C library of the target operating system to support the Name Service Switch and Pluggable Authentication @@ -1517,7 +1591,8 @@ NAME="AEN2542">15.6. Limitations</H1 ><P >Currently the winbind PAM module does not take into account possible workstation and logon time restrictions - that may be been set for Windows NT users.</P + that may be been set for Windows NT users, this is + instead up to the PDC to enforce.</P ></LI ></UL ></DIV @@ -1526,7 +1601,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2552">15.7. Conclusion</H1 +NAME="AEN2690" +></A +>14.7. Conclusion</H1 ><P >The winbind system, through the use of the Name Service Switch, Pluggable Authentication Modules, and appropriate @@ -1570,7 +1647,7 @@ WIDTH="33%" ALIGN="right" VALIGN="top" ><A -HREF="pdb-mysql.html" +HREF="improved-browsing.html" ACCESSKEY="N" >Next</A ></TD @@ -1594,7 +1671,7 @@ ACCESSKEY="U" WIDTH="33%" ALIGN="right" VALIGN="top" ->Passdb MySQL plugin</TD +>Improved browsing in samba</TD ></TR ></TABLE ></DIV diff --git a/docs/htmldocs/winbindd.8.html b/docs/htmldocs/winbindd.8.html index fb8c9c0458..dba9988e30 100644 --- a/docs/htmldocs/winbindd.8.html +++ b/docs/htmldocs/winbindd.8.html @@ -1,12 +1,11 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"> +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <HTML ><HEAD ><TITLE >winbindd</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ -"></HEAD +CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"></HEAD ><BODY CLASS="REFENTRY" BGCOLOR="#FFFFFF" @@ -16,7 +15,9 @@ VLINK="#840084" ALINK="#0000FF" ><H1 ><A -NAME="WINBINDD">winbindd</H1 +NAME="WINBINDD.8" +></A +>winbindd</H1 ><DIV CLASS="REFNAMEDIV" ><A @@ -29,13 +30,15 @@ NAME="AEN5" ><DIV CLASS="REFSYNOPSISDIV" ><A -NAME="AEN8"><H2 +NAME="AEN8" +></A +><H2 >Synopsis</H2 ><P ><B CLASS="COMMAND" >winbindd</B -> [-F] [-S] [-i] [-B] [-d <debug level>] [-s <smb config file>] [-n]</P +> [-F] [-S] [-i] [-B] [-d <debug level>] [-s <smb config file>] [-n]</P ></DIV ><DIV CLASS="REFSECT1" @@ -45,10 +48,12 @@ NAME="AEN18" ><H2 >DESCRIPTION</H2 ><P ->This program is part of the <A -HREF="samba.7.html" -TARGET="_top" -> Samba</A +>This program is part of the <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>Samba</SPAN +>(7)</SPAN > suite.</P ><P ><B @@ -166,22 +171,11 @@ CLASS="FILENAME" CLASS="FILENAME" >/etc/group</TT > and then from the - Windows NT server. </P -><P -><TABLE -BORDER="0" -BGCOLOR="#E0E0E0" -WIDTH="100%" -><TR -><TD -><PRE + Windows NT server. +<PRE CLASS="PROGRAMLISTING" >passwd: files winbind -group: files winbind - </PRE -></TD -></TR -></TABLE +group: files winbind</PRE ></P ><P >The following simple configuration in the @@ -198,7 +192,7 @@ CLASS="FILENAME" ><DIV CLASS="REFSECT1" ><A -NAME="AEN61" +NAME="AEN62" ></A ><H2 >OPTIONS</H2 @@ -310,9 +304,12 @@ CLASS="COMMAND" ><DD ><P >Specifies the location of the all-important - <TT -CLASS="FILENAME" ->smb.conf</TT + <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smb.conf</SPAN +>(5)</SPAN > file. </P ></DD ></DL @@ -321,7 +318,7 @@ CLASS="FILENAME" ><DIV CLASS="REFSECT1" ><A -NAME="AEN103" +NAME="AEN106" ></A ><H2 >NAME AND ID RESOLUTION</H2 @@ -352,7 +349,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN109" +NAME="AEN112" ></A ><H2 >CONFIGURATION</H2 @@ -361,10 +358,12 @@ NAME="AEN109" CLASS="COMMAND" >winbindd</B > daemon - is done through configuration parameters in the <TT -CLASS="FILENAME" ->smb.conf(5) - </TT + is done through configuration parameters in the <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smb.conf</SPAN +>(5)</SPAN > file. All parameters should be specified in the [global] section of smb.conf. </P ><P @@ -492,7 +491,7 @@ CLASS="PARAMETER" ><DIV CLASS="REFSECT1" ><A -NAME="AEN151" +NAME="AEN156" ></A ><H2 >EXAMPLE SETUP</H2 @@ -505,60 +504,37 @@ NAME="AEN151" CLASS="FILENAME" >/etc/nsswitch.conf</TT > put the - following:</P -><P -><TABLE -BORDER="0" -BGCOLOR="#E0E0E0" -WIDTH="100%" -><TR -><TD -><PRE + following: +<PRE CLASS="PROGRAMLISTING" >passwd: files winbind -group: files winbind - </PRE -></TD -></TR -></TABLE +group: files winbind</PRE ></P ><P >In <TT CLASS="FILENAME" >/etc/pam.d/*</TT -> replace the - <TT +> replace the <TT CLASS="PARAMETER" ><I ->auth</I +> auth</I ></TT -> lines with something like this: </P -><P -><TABLE -BORDER="0" -BGCOLOR="#E0E0E0" -WIDTH="100%" -><TR -><TD -><PRE +> lines with something like this: +<PRE CLASS="PROGRAMLISTING" >auth required /lib/security/pam_securetty.so auth required /lib/security/pam_nologin.so auth sufficient /lib/security/pam_winbind.so -auth required /lib/security/pam_pwdb.so use_first_pass shadow nullok - </PRE -></TD -></TR -></TABLE +auth required /lib/security/pam_pwdb.so use_first_pass shadow nullok</PRE ></P ><P >Note in particular the use of the <TT CLASS="PARAMETER" ><I ->sufficient</I +>sufficient + </I ></TT -> - keyword and the <TT +> keyword and the <TT CLASS="PARAMETER" ><I >use_first_pass</I @@ -581,8 +557,7 @@ CLASS="COMMAND" ><P ><B CLASS="COMMAND" ->smbpasswd -j DOMAIN -r PDC -U - Administrator</B +>net join -S PDC -U Administrator</B ></P ><P >The username after the <TT @@ -592,8 +567,7 @@ CLASS="PARAMETER" ></TT > can be any Domain user that has administrator privileges on the machine. - Substitute your domain name for "DOMAIN" and the name of your PDC - for "PDC".</P + Substitute the name or IP of your PDC for "PDC".</P ><P >Next copy <TT CLASS="FILENAME" @@ -604,9 +578,9 @@ CLASS="FILENAME" >/lib</TT > and <TT CLASS="FILENAME" ->pam_winbind.so</TT -> - to <TT +>pam_winbind.so + </TT +> to <TT CLASS="FILENAME" >/lib/security</TT >. A symbolic link needs to be @@ -624,19 +598,15 @@ CLASS="FILENAME" >/lib/libnss_winbind.so.1</TT >.</P ><P ->Finally, setup a <TT -CLASS="FILENAME" ->smb.conf</TT +>Finally, setup a <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smb.conf</SPAN +>(5)</SPAN > containing directives like the - following: </P -><P -><TABLE -BORDER="0" -BGCOLOR="#E0E0E0" -WIDTH="100%" -><TR -><TD -><PRE + following: +<PRE CLASS="PROGRAMLISTING" >[global] winbind separator = + @@ -647,11 +617,7 @@ CLASS="PROGRAMLISTING" winbind gid = 10000-20000 workgroup = DOMAIN security = domain - password server = * - </PRE -></TD -></TR -></TABLE + password server = *</PRE ></P ><P >Now start winbindd and you should find that your user and @@ -670,7 +636,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN190" +NAME="AEN194" ></A ><H2 >NOTES</H2 @@ -681,9 +647,12 @@ CLASS="COMMAND" >winbindd</B >: </P ><P -><B -CLASS="COMMAND" ->nmbd</B +><SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>nmbd</SPAN +>(8)</SPAN > must be running on the local machine for <B CLASS="COMMAND" @@ -691,8 +660,8 @@ CLASS="COMMAND" > to work. <B CLASS="COMMAND" >winbindd</B -> - queries the list of trusted domains for the Windows NT server +> queries + the list of trusted domains for the Windows NT server on startup and when a SIGHUP is received. Thus, for a running <B CLASS="COMMAND" > winbindd</B @@ -728,7 +697,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN206" +NAME="AEN212" ></A ><H2 >SIGNALS</H2 @@ -747,11 +716,14 @@ CLASS="VARIABLELIST" >SIGHUP</DT ><DD ><P ->Reload the <TT -CLASS="FILENAME" ->smb.conf(5)</TT -> - file and apply any parameter changes to the running +>Reload the <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smb.conf</SPAN +>(5)</SPAN +> file and + apply any parameter changes to the running version of winbindd. This signal also clears any cached user and group information. The list of other domains trusted by winbindd is also reloaded. </P @@ -779,7 +751,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN223" +NAME="AEN231" ></A ><H2 >FILES</H2 @@ -855,7 +827,7 @@ CLASS="FILENAME" ><DIV CLASS="REFSECT1" ><A -NAME="AEN252" +NAME="AEN260" ></A ><H2 >VERSION</H2 @@ -866,7 +838,7 @@ NAME="AEN252" ><DIV CLASS="REFSECT1" ><A -NAME="AEN255" +NAME="AEN263" ></A ><H2 >SEE ALSO</H2 @@ -874,27 +846,30 @@ NAME="AEN255" ><TT CLASS="FILENAME" >nsswitch.conf(5)</TT ->, - <A -HREF="samba.7.html" -TARGET="_top" ->samba(7)</A ->, - <A -HREF="wbinfo.1.html" -TARGET="_top" ->wbinfo(1)</A ->, - <A -HREF="smb.conf.5.html" -TARGET="_top" ->smb.conf(5)</A +>, <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>Samba</SPAN +>(7)</SPAN +>, <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>wbinfo</SPAN +>(8)</SPAN +>, <SPAN +CLASS="CITEREFENTRY" +><SPAN +CLASS="REFENTRYTITLE" +>smb.conf</SPAN +>(5)</SPAN ></P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN262" +NAME="AEN276" ></A ><H2 >AUTHOR</H2 @@ -910,11 +885,12 @@ CLASS="COMMAND" > and <B CLASS="COMMAND" >winbindd</B -> - were written by Tim Potter.</P +> were + written by Tim Potter.</P ><P >The conversion to DocBook for Samba 2.2 was done - by Gerald Carter</P + by Gerald Carter. The conversion to DocBook XML 4.2 for + Samba 3.0 was done by Alexander Bokovoy.</P ></DIV ></BODY ></HTML |