diff options
Diffstat (limited to 'docs/htmldocs')
64 files changed, 4738 insertions, 25513 deletions
diff --git a/docs/htmldocs/Samba-Developers-Guide.html b/docs/htmldocs/Samba-Developers-Guide.html index 5d9702e49e..b90d99bf66 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 and Client Caching of Printer Information</A +>ChangeID & Client Caching of Printer Information</A ></DT ><DT >10.5. <A @@ -810,26 +810,7 @@ HREF="#AEN3162" ><A NAME="SMBPASSWDFILEFORMAT" ></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 +>The smbpasswd file</A ></DT ></DL ></DD @@ -934,7 +915,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 @@ -2552,7 +2533,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 @@ -2900,14 +2881,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 @@ -7004,7 +6985,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 @@ -7669,18 +7650,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 @@ -7688,7 +7669,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 @@ -8374,7 +8355,7 @@ CLASS="SECT1" ><A NAME="AEN2959" ></A ->10.4. ChangeID and Client Caching of Printer Information</H2 +>10.4. ChangeID & Client Caching of Printer Information</H2 ><P >[To be filled in later]</P ></DIV @@ -8695,7 +8676,8 @@ 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 @@ -9120,7 +9102,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. @@ -9149,7 +9131,7 @@ CLASS="FILENAME" CLASS="FILENAME" >/etc/passwd </TT -> file use the following command:</P +> file use the following command :</P ><P ><TT CLASS="PROMPT" @@ -9320,97 +9302,6 @@ 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 deleted file mode 100644 index d758fbbe11..0000000000 --- a/docs/htmldocs/Samba-HOWTO-Collection.html +++ /dev/null @@ -1,17270 +0,0 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> -<HTML -><HEAD -><TITLE ->SAMBA Project Documentation</TITLE -><META -NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"></HEAD -><BODY -CLASS="BOOK" -BGCOLOR="#FFFFFF" -TEXT="#000000" -LINK="#0000FF" -VLINK="#840084" -ALINK="#0000FF" -><DIV -CLASS="BOOK" -><A -NAME="SAMBA-HOWTO-COLLECTION" -></A -><DIV -CLASS="TITLEPAGE" -><H1 -CLASS="TITLE" -><A -NAME="SAMBA-HOWTO-COLLECTION" -></A ->SAMBA Project Documentation</H1 -><H3 -CLASS="AUTHOR" -><A -NAME="AEN4" -></A ->SAMBA Team</H3 -><HR></DIV -><HR><H1 -><A -NAME="AEN8" -></A ->Abstract</H1 -><P -><SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->Last Update</I -></SPAN -> : 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 -than one person can maintain. The most recent version of this document -can be found at <A -HREF="http://www.samba.org/" -TARGET="_top" ->http://www.samba.org/</A -> -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) -version 2. A copy of the license is included with the Samba source -distribution. A copy can be found on-line at <A -HREF="http://www.fsf.org/licenses/gpl.txt" -TARGET="_top" ->http://www.fsf.org/licenses/gpl.txt</A -></P -><P ->Cheers, jerry</P -><DIV -CLASS="TOC" -><DL -><DT -><B ->Table of Contents</B -></DT -><DT ->I. <A -HREF="#INTRODUCTION" ->General installation</A -></DT -><DD -><DL -><DT ->1. <A -HREF="#INSTALL" ->How to Install and Test SAMBA</A -></DT -><DD -><DL -><DT ->1.1. <A -HREF="#AEN26" ->Read the man pages</A -></DT -><DT ->1.2. <A -HREF="#AEN36" ->Building the Binaries</A -></DT -><DT ->1.3. <A -HREF="#AEN64" ->The all important step</A -></DT -><DT ->1.4. <A -HREF="#AEN68" ->Create the smb configuration file.</A -></DT -><DT ->1.5. <A -HREF="#AEN82" ->Test your config file with - <B -CLASS="COMMAND" ->testparm</B -></A -></DT -><DT ->1.6. <A -HREF="#AEN90" ->Starting the smbd and nmbd</A -></DT -><DT ->1.7. <A -HREF="#AEN145" ->Try listing the shares available on your - server</A -></DT -><DT ->1.8. <A -HREF="#AEN154" ->Try connecting with the unix client</A -></DT -><DT ->1.9. <A -HREF="#AEN170" ->Try connecting from a DOS, WfWg, Win9x, WinNT, - Win2k, OS/2, etc... client</A -></DT -><DT ->1.10. <A -HREF="#AEN184" ->What If Things Don't Work?</A -></DT -></DL -></DD -><DT ->2. <A -HREF="#BROWSING-QUICK" ->Quick Cross Subnet Browsing / Cross Workgroup Browsing guide</A -></DT -><DD -><DL -><DT ->2.1. <A -HREF="#AEN230" ->Discussion</A -></DT -><DT ->2.2. <A -HREF="#AEN238" ->Use of the "Remote Announce" parameter</A -></DT -><DT ->2.3. <A -HREF="#AEN252" ->Use of the "Remote Browse Sync" parameter</A -></DT -><DT ->2.4. <A -HREF="#AEN257" ->Use of WINS</A -></DT -><DT ->2.5. <A -HREF="#AEN268" ->Do NOT use more than one (1) protocol on MS Windows machines</A -></DT -><DT ->2.6. <A -HREF="#AEN274" ->Name Resolution Order</A -></DT -></DL -></DD -><DT ->3. <A -HREF="#PASSDB" ->User information database</A -></DT -><DD -><DL -><DT ->3.1. <A -HREF="#AEN324" ->Introduction</A -></DT -><DT ->3.2. <A -HREF="#AEN331" ->Important Notes About Security</A -></DT -><DT ->3.3. <A -HREF="#AEN357" ->The smbpasswd Command</A -></DT -><DT ->3.4. <A -HREF="#AEN388" ->Plain text</A -></DT -><DT ->3.5. <A -HREF="#AEN393" ->TDB</A -></DT -><DT ->3.6. <A -HREF="#AEN396" ->LDAP</A -></DT -><DT ->3.7. <A -HREF="#AEN614" ->MySQL</A -></DT -><DT ->3.8. <A -HREF="#AEN662" ->Passdb XML plugin</A -></DT -></DL -></DD -></DL -></DD -><DT ->II. <A -HREF="#TYPE" ->Type of installation</A -></DT -><DD -><DL -><DT ->4. <A -HREF="#SECURITYLEVELS" ->User and Share security level (for servers not in a domain)</A -></DT -><DT ->5. <A -HREF="#SAMBA-PDC" ->Samba as a NT4 or Win2k Primary Domain Controller</A -></DT -><DD -><DL -><DT ->5.1. <A -HREF="#AEN722" ->Prerequisite Reading</A -></DT -><DT ->5.2. <A -HREF="#AEN728" ->Background</A -></DT -><DT ->5.3. <A -HREF="#AEN767" ->Configuring the Samba Domain Controller</A -></DT -><DT ->5.4. <A -HREF="#AEN810" ->Creating Machine Trust Accounts and Joining Clients to the -Domain</A -></DT -><DT ->5.5. <A -HREF="#AEN894" ->Common Problems and Errors</A -></DT -><DT ->5.6. <A -HREF="#AEN942" ->System Policies and Profiles</A -></DT -><DT ->5.7. <A -HREF="#AEN986" ->What other help can I get?</A -></DT -><DT ->5.8. <A -HREF="#AEN1100" ->Domain Control for Windows 9x/ME</A -></DT -><DT ->5.9. <A -HREF="#AEN1238" ->DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba</A -></DT -></DL -></DD -><DT ->6. <A -HREF="#SAMBA-BDC" ->How to Act as a Backup Domain Controller in a Purely Samba Controlled Domain</A -></DT -><DD -><DL -><DT ->6.1. <A -HREF="#AEN1274" ->Prerequisite Reading</A -></DT -><DT ->6.2. <A -HREF="#AEN1278" ->Background</A -></DT -><DT ->6.3. <A -HREF="#AEN1286" ->What qualifies a Domain Controller on the network?</A -></DT -><DT ->6.4. <A -HREF="#AEN1295" ->Can Samba be a Backup Domain Controller to an NT PDC?</A -></DT -><DT ->6.5. <A -HREF="#AEN1300" ->How do I set up a Samba BDC?</A -></DT -></DL -></DD -><DT ->7. <A -HREF="#ADS" ->Samba as a ADS domain member</A -></DT -><DD -><DL -><DT ->7.1. <A -HREF="#AEN1339" ->Installing the required packages for Debian</A -></DT -><DT ->7.2. <A -HREF="#AEN1346" ->Installing the required packages for RedHat</A -></DT -><DT ->7.3. <A -HREF="#AEN1356" ->Compile Samba</A -></DT -><DT ->7.4. <A -HREF="#AEN1371" ->Setup your /etc/krb5.conf</A -></DT -><DT ->7.5. <A -HREF="#AEN1381" ->Create the computer account</A -></DT -><DT ->7.6. <A -HREF="#AEN1393" ->Test your server setup</A -></DT -><DT ->7.7. <A -HREF="#AEN1398" ->Testing with smbclient</A -></DT -><DT ->7.8. <A -HREF="#AEN1401" ->Notes</A -></DT -></DL -></DD -><DT ->8. <A -HREF="#DOMAIN-SECURITY" ->Samba as a NT4 or Win2k domain member</A -></DT -><DD -><DL -><DT ->8.1. <A -HREF="#AEN1423" ->Joining an NT Domain with Samba 3.0</A -></DT -><DT ->8.2. <A -HREF="#AEN1478" ->Samba and Windows 2000 Domains</A -></DT -><DT ->8.3. <A -HREF="#AEN1481" ->Why is this better than security = server?</A -></DT -></DL -></DD -></DL -></DD -><DT ->III. <A -HREF="#OPTIONAL" ->Optional configuration</A -></DT -><DD -><DL -><DT ->9. <A -HREF="#INTEGRATE-MS-NETWORKS" ->Integrating MS Windows networks with Samba</A -></DT -><DD -><DL -><DT ->9.1. <A -HREF="#AEN1513" ->Agenda</A -></DT -><DT ->9.2. <A -HREF="#AEN1535" ->Name Resolution in a pure Unix/Linux world</A -></DT -><DT ->9.3. <A -HREF="#AEN1598" ->Name resolution as used within MS Windows networking</A -></DT -><DT ->9.4. <A -HREF="#AEN1643" ->How browsing functions and how to deploy stable and -dependable browsing using Samba</A -></DT -><DT ->9.5. <A -HREF="#AEN1653" ->MS Windows security options and how to configure -Samba for seemless integration</A -></DT -><DT ->9.6. <A -HREF="#AEN1723" ->Conclusions</A -></DT -></DL -></DD -><DT ->10. <A -HREF="#UNIX-PERMISSIONS" ->UNIX Permission Bits and Windows NT Access Control Lists</A -></DT -><DD -><DL -><DT ->10.1. <A -HREF="#AEN1744" ->Viewing and changing UNIX permissions using the NT - security dialogs</A -></DT -><DT ->10.2. <A -HREF="#AEN1748" ->How to view file security on a Samba share</A -></DT -><DT ->10.3. <A -HREF="#AEN1759" ->Viewing file ownership</A -></DT -><DT ->10.4. <A -HREF="#AEN1779" ->Viewing file or directory permissions</A -></DT -><DT ->10.5. <A -HREF="#AEN1815" ->Modifying file or directory permissions</A -></DT -><DT ->10.6. <A -HREF="#AEN1837" ->Interaction with the standard Samba create mask - parameters</A -></DT -><DT ->10.7. <A -HREF="#AEN1901" ->Interaction with the standard Samba file attribute - mapping</A -></DT -></DL -></DD -><DT ->11. <A -HREF="#PAM" ->Configuring PAM for distributed but centrally -managed authentication</A -></DT -><DD -><DL -><DT ->11.1. <A -HREF="#AEN1922" ->Samba and PAM</A -></DT -><DT ->11.2. <A -HREF="#AEN1966" ->Distributed Authentication</A -></DT -><DT ->11.3. <A -HREF="#AEN1973" ->PAM Configuration in smb.conf</A -></DT -></DL -></DD -><DT ->12. <A -HREF="#MSDFS" ->Hosting a Microsoft Distributed File System tree on Samba</A -></DT -><DD -><DL -><DT ->12.1. <A -HREF="#AEN1993" ->Instructions</A -></DT -></DL -></DD -><DT ->13. <A -HREF="#PRINTING" ->Printing Support</A -></DT -><DD -><DL -><DT ->13.1. <A -HREF="#AEN2054" ->Introduction</A -></DT -><DT ->13.2. <A -HREF="#AEN2076" ->Configuration</A -></DT -><DT ->13.3. <A -HREF="#AEN2184" ->The Imprints Toolset</A -></DT -><DT ->13.4. <A -HREF="#AEN2227" ->Diagnosis</A -></DT -></DL -></DD -><DT ->14. <A -HREF="#WINBIND" ->Unified Logons between Windows NT and UNIX using Winbind</A -></DT -><DD -><DL -><DT ->14.1. <A -HREF="#AEN2360" ->Abstract</A -></DT -><DT ->14.2. <A -HREF="#AEN2364" ->Introduction</A -></DT -><DT ->14.3. <A -HREF="#AEN2377" ->What Winbind Provides</A -></DT -><DT ->14.4. <A -HREF="#AEN2388" ->How Winbind Works</A -></DT -><DT ->14.5. <A -HREF="#AEN2431" ->Installation and Configuration</A -></DT -><DT ->14.6. <A -HREF="#AEN2680" ->Limitations</A -></DT -><DT ->14.7. <A -HREF="#AEN2690" ->Conclusion</A -></DT -></DL -></DD -><DT ->15. <A -HREF="#IMPROVED-BROWSING" ->Improved browsing in samba</A -></DT -><DD -><DL -><DT ->15.1. <A -HREF="#AEN2700" ->Overview of browsing</A -></DT -><DT ->15.2. <A -HREF="#AEN2704" ->Browsing support in samba</A -></DT -><DT ->15.3. <A -HREF="#AEN2713" ->Problem resolution</A -></DT -><DT ->15.4. <A -HREF="#AEN2720" ->Browsing across subnets</A -></DT -><DT ->15.5. <A -HREF="#AEN2760" ->Setting up a WINS server</A -></DT -><DT ->15.6. <A -HREF="#AEN2779" ->Setting up Browsing in a WORKGROUP</A -></DT -><DT ->15.7. <A -HREF="#AEN2797" ->Setting up Browsing in a DOMAIN</A -></DT -><DT ->15.8. <A -HREF="#AEN2807" ->Forcing samba to be the master</A -></DT -><DT ->15.9. <A -HREF="#AEN2816" ->Making samba the domain master</A -></DT -><DT ->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 ->16.1. <A -HREF="#AEN2855" ->Introduction and configuration</A -></DT -><DT ->16.2. <A -HREF="#AEN2864" ->Included modules</A -></DT -><DT ->16.3. <A -HREF="#AEN2918" ->VFS modules available elsewhere</A -></DT -></DL -></DD -><DT ->17. <A -HREF="#CVS-ACCESS" ->Access Samba source code via CVS</A -></DT -><DD -><DL -><DT ->17.1. <A -HREF="#AEN2942" ->Introduction</A -></DT -><DT ->17.2. <A -HREF="#AEN2947" ->CVS Access to samba.org</A -></DT -></DL -></DD -><DT ->18. <A -HREF="#GROUPMAPPING" ->Group mapping HOWTO</A -></DT -><DT ->19. <A -HREF="#SPEED" ->Samba performance issues</A -></DT -><DD -><DL -><DT ->19.1. <A -HREF="#AEN3033" ->Comparisons</A -></DT -><DT ->19.2. <A -HREF="#AEN3039" ->Socket options</A -></DT -><DT ->19.3. <A -HREF="#AEN3046" ->Read size</A -></DT -><DT ->19.4. <A -HREF="#AEN3051" ->Max xmit</A -></DT -><DT ->19.5. <A -HREF="#AEN3056" ->Log level</A -></DT -><DT ->19.6. <A -HREF="#AEN3059" ->Read raw</A -></DT -><DT ->19.7. <A -HREF="#AEN3064" ->Write raw</A -></DT -><DT ->19.8. <A -HREF="#AEN3068" ->Slow Clients</A -></DT -><DT ->19.9. <A -HREF="#AEN3072" ->Slow Logins</A -></DT -><DT ->19.10. <A -HREF="#AEN3075" ->Client tuning</A -></DT -></DL -></DD -><DT ->20. <A -HREF="#GROUPPROFILES" ->Creating Group Profiles</A -></DT -><DD -><DL -><DT ->20.1. <A -HREF="#AEN3123" ->Windows '9x</A -></DT -><DT ->20.2. <A -HREF="#AEN3132" ->Windows NT 4</A -></DT -><DT ->20.3. <A -HREF="#AEN3170" ->Windows 2000/XP</A -></DT -></DL -></DD -></DL -></DD -><DT ->IV. <A -HREF="#APPENDIXES" ->Appendixes</A -></DT -><DD -><DL -><DT ->21. <A -HREF="#PORTABILITY" ->Portability</A -></DT -><DD -><DL -><DT ->21.1. <A -HREF="#AEN3251" ->HPUX</A -></DT -><DT ->21.2. <A -HREF="#AEN3257" ->SCO Unix</A -></DT -><DT ->21.3. <A -HREF="#AEN3261" ->DNIX</A -></DT -><DT ->21.4. <A -HREF="#AEN3290" ->RedHat Linux Rembrandt-II</A -></DT -></DL -></DD -><DT ->22. <A -HREF="#OTHER-CLIENTS" ->Samba and other CIFS clients</A -></DT -><DD -><DL -><DT ->22.1. <A -HREF="#AEN3311" ->Macintosh clients?</A -></DT -><DT ->22.2. <A -HREF="#AEN3320" ->OS2 Client</A -></DT -><DT ->22.3. <A -HREF="#AEN3360" ->Windows for Workgroups</A -></DT -><DT ->22.4. <A -HREF="#AEN3381" ->Windows '95/'98</A -></DT -><DT ->22.5. <A -HREF="#AEN3397" ->Windows 2000 Service Pack 2</A -></DT -></DL -></DD -><DT ->23. <A -HREF="#BUGREPORT" ->Reporting Bugs</A -></DT -><DD -><DL -><DT ->23.1. <A -HREF="#AEN3421" ->Introduction</A -></DT -><DT ->23.2. <A -HREF="#AEN3431" ->General info</A -></DT -><DT ->23.3. <A -HREF="#AEN3437" ->Debug levels</A -></DT -><DT ->23.4. <A -HREF="#AEN3454" ->Internal errors</A -></DT -><DT ->23.5. <A -HREF="#AEN3464" ->Attaching to a running process</A -></DT -><DT ->23.6. <A -HREF="#AEN3467" ->Patches</A -></DT -></DL -></DD -><DT ->24. <A -HREF="#DIAGNOSIS" ->Diagnosing your samba server</A -></DT -><DD -><DL -><DT ->24.1. <A -HREF="#AEN3490" ->Introduction</A -></DT -><DT ->24.2. <A -HREF="#AEN3495" ->Assumptions</A -></DT -><DT ->24.3. <A -HREF="#AEN3505" ->Tests</A -></DT -><DT ->24.4. <A -HREF="#AEN3615" ->Still having troubles?</A -></DT -></DL -></DD -></DL -></DD -></DL -></DIV -><DIV -CLASS="PART" -><A -NAME="INTRODUCTION" -></A -><DIV -CLASS="TITLEPAGE" -><H1 -CLASS="TITLE" ->I. General installation</H1 -><DIV -CLASS="PARTINTRO" -><A -NAME="AEN21" -></A -><H1 ->Introduction</H1 -><P ->This part contains general info on how to install samba -and how to configure the parts of samba you will most likely need. -PLEASE read this.</P -></DIV -><DIV -CLASS="TOC" -><DL -><DT -><B ->Table of Contents</B -></DT -><DT ->1. <A -HREF="#INSTALL" ->How to Install and Test SAMBA</A -></DT -><DD -><DL -><DT ->1.1. <A -HREF="#AEN26" ->Read the man pages</A -></DT -><DT ->1.2. <A -HREF="#AEN36" ->Building the Binaries</A -></DT -><DT ->1.3. <A -HREF="#AEN64" ->The all important step</A -></DT -><DT ->1.4. <A -HREF="#AEN68" ->Create the smb configuration file.</A -></DT -><DT ->1.5. <A -HREF="#AEN82" ->Test your config file with - <B -CLASS="COMMAND" ->testparm</B -></A -></DT -><DT ->1.6. <A -HREF="#AEN90" ->Starting the smbd and nmbd</A -></DT -><DD -><DL -><DT ->1.6.1. <A -HREF="#AEN100" ->Starting from inetd.conf</A -></DT -><DT ->1.6.2. <A -HREF="#AEN129" ->Alternative: starting it as a daemon</A -></DT -></DL -></DD -><DT ->1.7. <A -HREF="#AEN145" ->Try listing the shares available on your - server</A -></DT -><DT ->1.8. <A -HREF="#AEN154" ->Try connecting with the unix client</A -></DT -><DT ->1.9. <A -HREF="#AEN170" ->Try connecting from a DOS, WfWg, Win9x, WinNT, - Win2k, OS/2, etc... client</A -></DT -><DT ->1.10. <A -HREF="#AEN184" ->What If Things Don't Work?</A -></DT -><DD -><DL -><DT ->1.10.1. <A -HREF="#AEN189" ->Diagnosing Problems</A -></DT -><DT ->1.10.2. <A -HREF="#AEN193" ->Scope IDs</A -></DT -><DT ->1.10.3. <A -HREF="#AEN196" ->Choosing the Protocol Level</A -></DT -><DT ->1.10.4. <A -HREF="#AEN205" ->Printing from UNIX to a Client PC</A -></DT -><DT ->1.10.5. <A -HREF="#AEN210" ->Locking</A -></DT -><DT ->1.10.6. <A -HREF="#AEN219" ->Mapping Usernames</A -></DT -></DL -></DD -></DL -></DD -><DT ->2. <A -HREF="#BROWSING-QUICK" ->Quick Cross Subnet Browsing / Cross Workgroup Browsing guide</A -></DT -><DD -><DL -><DT ->2.1. <A -HREF="#AEN230" ->Discussion</A -></DT -><DT ->2.2. <A -HREF="#AEN238" ->Use of the "Remote Announce" parameter</A -></DT -><DT ->2.3. <A -HREF="#AEN252" ->Use of the "Remote Browse Sync" parameter</A -></DT -><DT ->2.4. <A -HREF="#AEN257" ->Use of WINS</A -></DT -><DT ->2.5. <A -HREF="#AEN268" ->Do NOT use more than one (1) protocol on MS Windows machines</A -></DT -><DT ->2.6. <A -HREF="#AEN274" ->Name Resolution Order</A -></DT -></DL -></DD -><DT ->3. <A -HREF="#PASSDB" ->User information database</A -></DT -><DD -><DL -><DT ->3.1. <A -HREF="#AEN324" ->Introduction</A -></DT -><DT ->3.2. <A -HREF="#AEN331" ->Important Notes About Security</A -></DT -><DD -><DL -><DT ->3.2.1. <A -HREF="#AEN346" ->Advantages of SMB Encryption</A -></DT -><DT ->3.2.2. <A -HREF="#AEN351" ->Advantages of non-encrypted passwords</A -></DT -></DL -></DD -><DT ->3.3. <A -HREF="#AEN357" ->The smbpasswd Command</A -></DT -><DT ->3.4. <A -HREF="#AEN388" ->Plain text</A -></DT -><DT ->3.5. <A -HREF="#AEN393" ->TDB</A -></DT -><DT ->3.6. <A -HREF="#AEN396" ->LDAP</A -></DT -><DD -><DL -><DT ->3.6.1. <A -HREF="#AEN398" ->Introduction</A -></DT -><DT ->3.6.2. <A -HREF="#AEN418" ->Introduction</A -></DT -><DT ->3.6.3. <A -HREF="#AEN447" ->Supported LDAP Servers</A -></DT -><DT ->3.6.4. <A -HREF="#AEN452" ->Schema and Relationship to the RFC 2307 posixAccount</A -></DT -><DT ->3.6.5. <A -HREF="#AEN464" ->Configuring Samba with LDAP</A -></DT -><DT ->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 ->3.7. <A -HREF="#AEN614" ->MySQL</A -></DT -><DD -><DL -><DT ->3.7.1. <A -HREF="#AEN616" ->Building</A -></DT -><DT ->3.7.2. <A -HREF="#AEN622" ->Creating the database</A -></DT -><DT ->3.7.3. <A -HREF="#AEN632" ->Configuring</A -></DT -><DT ->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 ->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 -CLASS="CHAPTER" -><HR><H1 -><A -NAME="INSTALL" -></A ->Chapter 1. How to Install and Test SAMBA</H1 -><DIV -CLASS="SECT1" -><H2 -CLASS="SECT1" -><A -NAME="AEN26" -></A ->1.1. Read the man pages</H2 -><P ->The man pages distributed with SAMBA contain - lots of useful info that will help to get you started. - If you don't know how to read man pages then try - something like:</P -><P -><TT -CLASS="PROMPT" ->$ </TT -><TT -CLASS="USERINPUT" -><B ->man smbd.8</B -></TT -> - or - <TT -CLASS="PROMPT" ->$ </TT -><TT -CLASS="USERINPUT" -><B ->nroff -man smbd.8 | more - </B -></TT -> on older unixes.</P -><P ->Other sources of information are pointed to - by the Samba web site,<A -HREF="http://www.samba.org/" -TARGET="_top" -> http://www.samba.org</A -></P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN36" -></A ->1.2. Building the Binaries</H2 -><P ->To do this, first run the program <B -CLASS="COMMAND" ->./configure - </B -> in the source directory. This should automatically - configure Samba for your operating system. If you have unusual - needs then you may wish to run</P -><P -><TT -CLASS="PROMPT" ->root# </TT -><TT -CLASS="USERINPUT" -><B ->./configure --help - </B -></TT -></P -><P ->first to see what special options you can enable. - Then executing</P -><P -><TT -CLASS="PROMPT" ->root# </TT -><TT -CLASS="USERINPUT" -><B ->make</B -></TT -></P -><P ->will create the binaries. Once it's successfully - compiled you can use </P -><P -><TT -CLASS="PROMPT" ->root# </TT -><TT -CLASS="USERINPUT" -><B ->make install</B -></TT -></P -><P ->to install the binaries and manual pages. You can - separately install the binaries and/or man pages using</P -><P -><TT -CLASS="PROMPT" ->root# </TT -><TT -CLASS="USERINPUT" -><B ->make installbin - </B -></TT -></P -><P ->and</P -><P -><TT -CLASS="PROMPT" ->root# </TT -><TT -CLASS="USERINPUT" -><B ->make installman - </B -></TT -></P -><P ->Note that if you are upgrading for a previous version - of Samba you might like to know that the old versions of - the binaries will be renamed with a ".old" extension. You - can go back to the previous version with</P -><P -><TT -CLASS="PROMPT" ->root# </TT -><TT -CLASS="USERINPUT" -><B ->make revert - </B -></TT -></P -><P ->if you find this version a disaster!</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN64" -></A ->1.3. The all important step</H2 -><P ->At this stage you must fetch yourself a - coffee or other drink you find stimulating. Getting the rest - of the install right can sometimes be tricky, so you will - probably need it.</P -><P ->If you have installed samba before then you can skip - this step.</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN68" -></A ->1.4. Create the smb configuration file.</H2 -><P ->There are sample configuration files in the examples - subdirectory in the distribution. I suggest you read them - carefully so you can see how the options go together in - practice. See the man page for all the options.</P -><P ->The simplest useful configuration file would be - something like this:</P -><P -><PRE -CLASS="PROGRAMLISTING" -> [global] - workgroup = MYGROUP - - [homes] - guest ok = no - read only = no - </PRE -></P -><P ->which would allow connections by anyone with an - account on the server, using either their login name or - "homes" as the service name. (Note that I also set the - workgroup that Samba is part of. See BROWSING.txt for details)</P -><P ->Note that <B -CLASS="COMMAND" ->make install</B -> will not install - a <TT -CLASS="FILENAME" ->smb.conf</TT -> file. You need to create it - yourself. </P -><P ->Make sure you put the smb.conf file in the same place - you specified in the<TT -CLASS="FILENAME" ->Makefile</TT -> (the default is to - look for it in <TT -CLASS="FILENAME" ->/usr/local/samba/lib/</TT ->).</P -><P ->For more information about security settings for the - [homes] share please refer to the document UNIX_SECURITY.txt.</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN82" -></A ->1.5. Test your config file with - <B -CLASS="COMMAND" ->testparm</B -></H2 -><P ->It's important that you test the validity of your - <TT -CLASS="FILENAME" ->smb.conf</TT -> file using the testparm program. - If testparm runs OK then it will list the loaded services. If - not it will give an error message.</P -><P ->Make sure it runs OK and that the services look - reasonable before proceeding. </P -><P ->Always run testparm again when you change - <TT -CLASS="FILENAME" ->smb.conf</TT ->!</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN90" -></A ->1.6. Starting the smbd and nmbd</H2 -><P ->You must choose to start smbd and nmbd either - as daemons or from <B -CLASS="COMMAND" ->inetd</B ->. Don't try - to do both! Either you can put them in <TT -CLASS="FILENAME" -> inetd.conf</TT -> and have them started on demand - by <B -CLASS="COMMAND" ->inetd</B ->, or you can start them as - daemons either from the command line or in <TT -CLASS="FILENAME" -> /etc/rc.local</TT ->. See the man pages for details - on the command line options. Take particular care to read - the bit about what user you need to be in order to start - Samba. In many cases you must be root.</P -><P ->The main advantage of starting <B -CLASS="COMMAND" ->smbd</B -> - and <B -CLASS="COMMAND" ->nmbd</B -> using the recommended daemon method - is that they will respond slightly more quickly to an initial connection - request.</P -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN100" -></A ->1.6.1. Starting from inetd.conf</H3 -><P ->NOTE; The following will be different if - you use NIS or NIS+ to distributed services maps.</P -><P ->Look at your <TT -CLASS="FILENAME" ->/etc/services</TT ->. - What is defined at port 139/tcp. If nothing is defined - then add a line like this:</P -><P -><TT -CLASS="USERINPUT" -><B ->netbios-ssn 139/tcp</B -></TT -></P -><P ->similarly for 137/udp you should have an entry like:</P -><P -><TT -CLASS="USERINPUT" -><B ->netbios-ns 137/udp</B -></TT -></P -><P ->Next edit your <TT -CLASS="FILENAME" ->/etc/inetd.conf</TT -> - and add two lines something like this:</P -><P -><PRE -CLASS="PROGRAMLISTING" -> netbios-ssn stream tcp nowait root /usr/local/samba/bin/smbd smbd - netbios-ns dgram udp wait root /usr/local/samba/bin/nmbd nmbd - </PRE -></P -><P ->The exact syntax of <TT -CLASS="FILENAME" ->/etc/inetd.conf</TT -> - varies between unixes. Look at the other entries in inetd.conf - for a guide.</P -><P ->NOTE: Some unixes already have entries like netbios_ns - (note the underscore) in <TT -CLASS="FILENAME" ->/etc/services</TT ->. - You must either edit <TT -CLASS="FILENAME" ->/etc/services</TT -> or - <TT -CLASS="FILENAME" ->/etc/inetd.conf</TT -> to make them consistent.</P -><P ->NOTE: On many systems you may need to use the - "interfaces" option in smb.conf to specify the IP address - and netmask of your interfaces. Run <B -CLASS="COMMAND" ->ifconfig</B -> - as root if you don't know what the broadcast is for your - net. <B -CLASS="COMMAND" ->nmbd</B -> tries to determine it at run - time, but fails on some unixes. See the section on "testing nmbd" - for a method of finding if you need to do this.</P -><P ->!!!WARNING!!! Many unixes only accept around 5 - parameters on the command line in <TT -CLASS="FILENAME" ->inetd.conf</TT ->. - This means you shouldn't use spaces between the options and - arguments, or you should use a script, and start the script - from <B -CLASS="COMMAND" ->inetd</B ->.</P -><P ->Restart <B -CLASS="COMMAND" ->inetd</B ->, perhaps just send - it a HUP. If you have installed an earlier version of <B -CLASS="COMMAND" -> nmbd</B -> then you may need to kill nmbd as well.</P -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN129" -></A ->1.6.2. Alternative: starting it as a daemon</H3 -><P ->To start the server as a daemon you should create - a script something like this one, perhaps calling - it <TT -CLASS="FILENAME" ->startsmb</TT ->.</P -><P -><PRE -CLASS="PROGRAMLISTING" -> #!/bin/sh - /usr/local/samba/bin/smbd -D - /usr/local/samba/bin/nmbd -D - </PRE -></P -><P ->then make it executable with <B -CLASS="COMMAND" ->chmod - +x startsmb</B -></P -><P ->You can then run <B -CLASS="COMMAND" ->startsmb</B -> by - hand or execute it from <TT -CLASS="FILENAME" ->/etc/rc.local</TT -> - </P -><P ->To kill it send a kill signal to the processes - <B -CLASS="COMMAND" ->nmbd</B -> and <B -CLASS="COMMAND" ->smbd</B ->.</P -><P ->NOTE: If you use the SVR4 style init system then - you may like to look at the <TT -CLASS="FILENAME" ->examples/svr4-startup</TT -> - script to make Samba fit into that system.</P -></DIV -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN145" -></A ->1.7. Try listing the shares available on your - server</H2 -><P -><TT -CLASS="PROMPT" ->$ </TT -><TT -CLASS="USERINPUT" -><B ->smbclient -L - <TT -CLASS="REPLACEABLE" -><I ->yourhostname</I -></TT -></B -></TT -></P -><P ->You should get back a list of shares available on - your server. If you don't then something is incorrectly setup. - Note that this method can also be used to see what shares - are available on other LanManager clients (such as WfWg).</P -><P ->If you choose user level security then you may find - that Samba requests a password before it will list the shares. - See the <B -CLASS="COMMAND" ->smbclient</B -> man page for details. (you - can force it to list the shares without a password by - adding the option -U% to the command line. This will not work - with non-Samba servers)</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN154" -></A ->1.8. Try connecting with the unix client</H2 -><P -><TT -CLASS="PROMPT" ->$ </TT -><TT -CLASS="USERINPUT" -><B ->smbclient <TT -CLASS="REPLACEABLE" -><I -> //yourhostname/aservice</I -></TT -></B -></TT -></P -><P ->Typically the <TT -CLASS="REPLACEABLE" -><I ->yourhostname</I -></TT -> - would be the name of the host where you installed <B -CLASS="COMMAND" -> smbd</B ->. The <TT -CLASS="REPLACEABLE" -><I ->aservice</I -></TT -> is - any service you have defined in the <TT -CLASS="FILENAME" ->smb.conf</TT -> - file. Try your user name if you just have a [homes] section - in <TT -CLASS="FILENAME" ->smb.conf</TT ->.</P -><P ->For example if your unix host is bambi and your login - name is fred you would type:</P -><P -><TT -CLASS="PROMPT" ->$ </TT -><TT -CLASS="USERINPUT" -><B ->smbclient //bambi/fred - </B -></TT -></P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN170" -></A ->1.9. Try connecting from a DOS, WfWg, Win9x, WinNT, - Win2k, OS/2, etc... client</H2 -><P ->Try mounting disks. eg:</P -><P -><TT -CLASS="PROMPT" ->C:\WINDOWS\> </TT -><TT -CLASS="USERINPUT" -><B ->net use d: \\servername\service - </B -></TT -></P -><P ->Try printing. eg:</P -><P -><TT -CLASS="PROMPT" ->C:\WINDOWS\> </TT -><TT -CLASS="USERINPUT" -><B ->net use lpt1: - \\servername\spoolservice</B -></TT -></P -><P -><TT -CLASS="PROMPT" ->C:\WINDOWS\> </TT -><TT -CLASS="USERINPUT" -><B ->print filename - </B -></TT -></P -><P ->Celebrate, or send me a bug report!</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN184" -></A ->1.10. What If Things Don't Work?</H2 -><P ->If nothing works and you start to think "who wrote - this pile of trash" then I suggest you do step 2 again (and - again) till you calm down.</P -><P ->Then you might read the file DIAGNOSIS.txt and the - FAQ. If you are still stuck then try the mailing list or - newsgroup (look in the README for details). Samba has been - successfully installed at thousands of sites worldwide, so maybe - someone else has hit your problem and has overcome it. You could - also use the WWW site to scan back issues of the samba-digest.</P -><P ->When you fix the problem PLEASE send me some updates to the - documentation (or source code) so that the next person will find it - easier. </P -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN189" -></A ->1.10.1. Diagnosing Problems</H3 -><P ->If you have installation problems then go to the - <A -HREF="Diagnosis.html" -TARGET="_top" ->Diagnosis</A -> chapter to try to find the - problem.</P -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN193" -></A ->1.10.2. Scope IDs</H3 -><P ->By default Samba uses a blank scope ID. This means - all your windows boxes must also have a blank scope ID. - If you really want to use a non-blank scope ID then you will - need to use the 'netbios scope' smb.conf option. - All your PCs will need to have the same setting for - this to work. I do not recommend scope IDs.</P -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN196" -></A ->1.10.3. Choosing the Protocol Level</H3 -><P ->The SMB protocol has many dialects. Currently - Samba supports 5, called CORE, COREPLUS, LANMAN1, - LANMAN2 and NT1.</P -><P ->You can choose what maximum protocol to support - in the <TT -CLASS="FILENAME" ->smb.conf</TT -> file. The default is - NT1 and that is the best for the vast majority of sites.</P -><P ->In older versions of Samba you may have found it - necessary to use COREPLUS. The limitations that led to - this have mostly been fixed. It is now less likely that you - will want to use less than LANMAN1. The only remaining advantage - of COREPLUS is that for some obscure reason WfWg preserves - the case of passwords in this protocol, whereas under LANMAN1, - LANMAN2 or NT1 it uppercases all passwords before sending them, - forcing you to use the "password level=" option in some cases.</P -><P ->The main advantage of LANMAN2 and NT1 is support for - long filenames with some clients (eg: smbclient, Windows NT - or Win95). </P -><P ->See the smb.conf(5) manual page for more details.</P -><P ->Note: To support print queue reporting you may find - that you have to use TCP/IP as the default protocol under - WfWg. For some reason if you leave Netbeui as the default - it may break the print queue reporting on some systems. - It is presumably a WfWg bug.</P -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN205" -></A ->1.10.4. Printing from UNIX to a Client PC</H3 -><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 - smbclient program. You then need to install the script - "smbprint". Read the instruction in smbprint for more details. - </P -><P ->There is also a SYSV style script that does much - the same thing called smbprint.sysv. It contains instructions.</P -><P ->See the CUPS manual for information about setting up - printing from a unix host with CUPS to a smb-based server. </P -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN210" -></A ->1.10.5. Locking</H3 -><P ->One area which sometimes causes trouble is locking.</P -><P ->There are two types of locking which need to be - performed by a SMB server. The first is "record locking" - which allows a client to lock a range of bytes in a open file. - The second is the "deny modes" that are specified when a file - is open.</P -><P ->Record locking semantics under Unix is very - different from record locking under Windows. Versions - of Samba before 2.2 have tried to use the native - fcntl() unix system call to implement proper record - locking between different Samba clients. This can not - be fully correct due to several reasons. The simplest - is the fact that a Windows client is allowed to lock a - byte range up to 2^32 or 2^64, depending on the client - OS. The unix locking only supports byte ranges up to - 2^31. So it is not possible to correctly satisfy a - lock request above 2^31. There are many more - differences, too many to be listed here.</P -><P ->Samba 2.2 and above implements record locking - completely independent of the underlying unix - system. If a byte range lock that the client requests - happens to fall into the range 0-2^31, Samba hands - this request down to the Unix system. All other locks - can not be seen by unix anyway.</P -><P ->Strictly a SMB server should check for locks before - every read and write call on a file. Unfortunately with the - way fcntl() works this can be slow and may overstress the - rpc.lockd. It is also almost always unnecessary as clients - are supposed to independently make locking calls before reads - and writes anyway if locking is important to them. By default - Samba only makes locking calls when explicitly asked - to by a client, but if you set "strict locking = yes" then it will - make lock checking calls on every read and write. </P -><P ->You can also disable by range locking completely - using "locking = no". This is useful for those shares that - don't support locking or don't need it (such as cdroms). In - this case Samba fakes the return codes of locking calls to - tell clients that everything is OK.</P -><P ->The second class of locking is the "deny modes". These - are set by an application when it opens a file to determine - what types of access should be allowed simultaneously with - its open. A client may ask for DENY_NONE, DENY_READ, DENY_WRITE - or DENY_ALL. There are also special compatibility modes called - DENY_FCB and DENY_DOS.</P -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN219" -></A ->1.10.6. Mapping Usernames</H3 -><P ->If you have different usernames on the PCs and - the unix server then take a look at the "username map" option. - See the smb.conf man page for details.</P -></DIV -></DIV -></DIV -><DIV -CLASS="CHAPTER" -><HR><H1 -><A -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 -and / or across workgroups (or domains). WINS is the best tool for resolution -of NetBIOS names to IP addesses. WINS is NOT involved in browse list handling -except by way of name to address mapping.</P -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN230" -></A ->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 -implements NetBIOS by encapsulating it over TCP/IP. MS Windows products can -do likewise. NetBIOS based networking uses broadcast messaging to affect -browse list management. When running NetBIOS over TCP/IP this uses UDP -based messaging. UDP messages can be broadcast or unicast.</P -><P ->Normally, only unicast UDP messaging can be forwarded by routers. The -"remote announce" parameter to smb.conf helps to project browse announcements -to remote network segments via unicast UDP. Similarly, the "remote browse sync" -parameter of smb.conf implements browse list collation using unicast UDP.</P -><P ->Secondly, in those networks where Samba is the only SMB server technology -wherever possible nmbd should be configured on one (1) machine as the WINS -server. This makes it easy to manage the browsing environment. If each network -segment is configured with it's own Samba WINS server, then the only way to -get cross segment browsing to work is by using the "remote announce" and -the "remote browse sync" parameters to your smb.conf file.</P -><P ->If only one WINS server is used then the use of the "remote announce" and the -"remote browse sync" parameters should NOT be necessary.</P -><P ->Samba WINS does not support MS-WINS replication. This means that when setting up -Samba as a WINS server there must only be one nmbd configured as a WINS server -on the network. Some sites have used multiple Samba WINS servers for redundancy -(one server per subnet) and then used "remote browse sync" and "remote announce" -to affect browse list collation across all segments. Note that this means -clients will only resolve local names, and must be configured to use DNS to -resolve names on other subnets in order to resolve the IP addresses of the -servers they can see on other subnets. This setup is not recommended, but is -mentioned as a practical consideration (ie: an 'if all else fails' scenario).</P -><P ->Lastly, take note that browse lists are a collection of unreliable broadcast -messages that are repeated at intervals of not more than 15 minutes. This means -that it will take time to establish a browse list and it can take up to 45 -minutes to stabilise, particularly across network segments.</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN238" -></A ->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. -The syntax of the "remote announce" parameter is: -<PRE -CLASS="PROGRAMLISTING" -> remote announce = a.b.c.d [e.f.g.h] ...</PRE -> -_or_ -<PRE -CLASS="PROGRAMLISTING" -> remote announce = a.b.c.d/WORKGROUP [e.f.g.h/WORKGROUP] ...</PRE -> - -where: -<P -></P -><DIV -CLASS="VARIABLELIST" -><DL -><DT ->a.b.c.d and e.f.g.h</DT -><DD -><P ->is either the LMB (Local Master Browser) IP address -or the broadcst address of the remote network. -ie: the LMB is at 192.168.1.10, or the address -could be given as 192.168.1.255 where the netmask -is assumed to be 24 bits (255.255.255.0). -When the remote announcement is made to the broadcast -address of the remote network every host will receive -our announcements. This is noisy and therefore -undesirable but may be necessary if we do NOT know -the IP address of the remote LMB.</P -></DD -><DT ->WORKGROUP</DT -><DD -><P ->is optional and can be either our own workgroup -or that of the remote network. If you use the -workgroup name of the remote network then our -NetBIOS machine names will end up looking like -they belong to that workgroup, this may cause -name resolution problems and should be avoided.</P -></DD -></DL -></DIV -></P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN252" -></A ->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 -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 -> - -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 -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN257" -></A ->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 -name_type value for each of of several types of service it has available. -eg: It registers it's name directly as a unique (the type 0x03) name. -It also registers it's name if it is running the lanmanager compatible -server service (used to make shares and printers available to other users) -by registering the server (the type 0x20) name.</P -><P ->All NetBIOS names are up to 15 characters in length. The name_type variable -is added to the end of the name - thus creating a 16 character name. Any -name that is shorter than 15 characters is padded with spaces to the 15th -character. ie: All NetBIOS names are 16 characters long (including the -name_type information).</P -><P ->WINS can store these 16 character names as they get registered. A client -that wants to log onto the network can ask the WINS server for a list -of all names that have registered the NetLogon service name_type. This saves -broadcast traffic and greatly expedites logon processing. Since broadcast -name resolution can not be used across network segments this type of -information can only be provided via WINS _or_ via statically configured -"lmhosts" files that must reside on all clients in the absence of WINS.</P -><P ->WINS also serves the purpose of forcing browse list synchronisation by all -LMB's. LMB's must synchronise their browse list with the DMB (domain master -browser) and WINS helps the LMB to identify it's DMB. By definition this -will work only within a single workgroup. Note that the domain master browser -has NOTHING to do with what is referred to as an MS Windows NT Domain. The -later is a reference to a security environment while the DMB refers to the -master controller for browse list information only.</P -><P ->Use of WINS will work correctly only if EVERY client TCP/IP protocol stack -has been configured to use the WINS server/s. Any client that has not been -configured to use the WINS server will continue to use only broadcast based -name registration so that WINS may NEVER get to know about it. In any case, -machines that have not registered with a WINS server will fail name to address -lookup attempts by other clients and will therefore cause workstation access -errors.</P -><P ->To configure Samba as a WINS server just add "wins support = yes" to the -smb.conf file [globals] section.</P -><P ->To configure Samba to register with a WINS server just add -"wins server = a.b.c.d" to your smb.conf file [globals] section.</P -><P -><SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->DO NOT EVER</I -></SPAN -> use both "wins support = yes" together with "wins server = a.b.c.d" -particularly not using it's own IP address.</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN268" -></A ->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 -><P ->Every NetBIOS machine take part in a process of electing the LMB (and DMB) -every 15 minutes. A set of election criteria is used to determine the order -of precidence for winning this election process. A machine running Samba or -Windows NT will be biased so that the most suitable machine will predictably -win and thus retain it's role.</P -><P ->The election process is "fought out" so to speak over every NetBIOS network -interface. In the case of a Windows 9x machine that has both TCP/IP and IPX -installed and has NetBIOS enabled over both protocols the election will be -decided over both protocols. As often happens, if the Windows 9x machine is -the only one with both protocols then the LMB may be won on the NetBIOS -interface over the IPX protocol. Samba will then lose the LMB role as Windows -9x will insist it knows who the LMB is. Samba will then cease to function -as an LMB and thus browse list operation on all TCP/IP only machines will -fail.</P -><P ->The safest rule of all to follow it this - USE ONLY ONE PROTOCOL!</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN274" -></A ->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 -><P -></P -><TABLE -BORDER="0" -><TBODY -><TR -><TD ->WINS: the best tool!</TD -></TR -><TR -><TD ->LMHOSTS: is static and hard to maintain.</TD -></TR -><TR -><TD ->Broadcast: uses UDP and can not resolve names across remote segments.</TD -></TR -></TBODY -></TABLE -><P -></P -><P ->Alternative means of name resolution includes:</P -><P -></P -><TABLE -BORDER="0" -><TBODY -><TR -><TD ->/etc/hosts: is static, hard to maintain, and lacks name_type info</TD -></TR -><TR -><TD ->DNS: is a good choice but lacks essential name_type info.</TD -></TR -></TBODY -></TABLE -><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 -> -_or_ -<PRE -CLASS="PROGRAMLISTING" ->name resolve order = wins lmhosts (eliminates bcast and host)</PRE -> -The default is: -<PRE -CLASS="PROGRAMLISTING" ->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 -controlled by <TT -CLASS="FILENAME" ->/etc/host.conf</TT ->, <TT -CLASS="FILENAME" ->/etc/nsswitch.conf</TT -> and <TT -CLASS="FILENAME" ->/etc/resolv.conf</TT ->.</P -></DIV -></DIV -><DIV -CLASS="CHAPTER" -><HR><H1 -><A -NAME="PASSDB" -></A ->Chapter 3. User information database</H1 -><DIV -CLASS="SECT1" -><H2 -CLASS="SECT1" -><A -NAME="AEN324" -></A ->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 (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" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN331" -></A ->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 - 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" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN346" -></A ->3.2.1. Advantages of SMB Encryption</H3 -><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" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN351" -></A ->3.2.2. Advantages of non-encrypted passwords</H3 -><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" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN357" -></A ->3.3. The smbpasswd Command</H2 -><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" -><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="TYPE" -></A -><DIV -CLASS="TITLEPAGE" -><H1 -CLASS="TITLE" ->II. Type of installation</H1 -><DIV -CLASS="PARTINTRO" -><A -NAME="AEN678" -></A -><H1 ->Introduction</H1 -><P ->Samba can operate in various SMB networks. This part contains information on configuring samba -for various environments.</P -></DIV -><DIV -CLASS="TOC" -><DL -><DT -><B ->Table of Contents</B -></DT -><DT ->4. <A -HREF="#SECURITYLEVELS" ->User and Share security level (for servers not in a domain)</A -></DT -><DT ->5. <A -HREF="#SAMBA-PDC" ->Samba as a NT4 or Win2k Primary Domain Controller</A -></DT -><DD -><DL -><DT ->5.1. <A -HREF="#AEN722" ->Prerequisite Reading</A -></DT -><DT ->5.2. <A -HREF="#AEN728" ->Background</A -></DT -><DT ->5.3. <A -HREF="#AEN767" ->Configuring the Samba Domain Controller</A -></DT -><DT ->5.4. <A -HREF="#AEN810" ->Creating Machine Trust Accounts and Joining Clients to the -Domain</A -></DT -><DD -><DL -><DT ->5.4.1. <A -HREF="#AEN829" ->Manual Creation of Machine Trust Accounts</A -></DT -><DT ->5.4.2. <A -HREF="#AEN870" ->"On-the-Fly" Creation of Machine Trust Accounts</A -></DT -><DT ->5.4.3. <A -HREF="#AEN879" ->Joining the Client to the Domain</A -></DT -></DL -></DD -><DT ->5.5. <A -HREF="#AEN894" ->Common Problems and Errors</A -></DT -><DT ->5.6. <A -HREF="#AEN942" ->System Policies and Profiles</A -></DT -><DT ->5.7. <A -HREF="#AEN986" ->What other help can I get?</A -></DT -><DT ->5.8. <A -HREF="#AEN1100" ->Domain Control for Windows 9x/ME</A -></DT -><DD -><DL -><DT ->5.8.1. <A -HREF="#AEN1126" ->Configuration Instructions: Network Logons</A -></DT -><DT ->5.8.2. <A -HREF="#AEN1145" ->Configuration Instructions: Setting up Roaming User Profiles</A -></DT -></DL -></DD -><DT ->5.9. <A -HREF="#AEN1238" ->DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba</A -></DT -></DL -></DD -><DT ->6. <A -HREF="#SAMBA-BDC" ->How to Act as a Backup Domain Controller in a Purely Samba Controlled Domain</A -></DT -><DD -><DL -><DT ->6.1. <A -HREF="#AEN1274" ->Prerequisite Reading</A -></DT -><DT ->6.2. <A -HREF="#AEN1278" ->Background</A -></DT -><DT ->6.3. <A -HREF="#AEN1286" ->What qualifies a Domain Controller on the network?</A -></DT -><DD -><DL -><DT ->6.3.1. <A -HREF="#AEN1289" ->How does a Workstation find its domain controller?</A -></DT -><DT ->6.3.2. <A -HREF="#AEN1292" ->When is the PDC needed?</A -></DT -></DL -></DD -><DT ->6.4. <A -HREF="#AEN1295" ->Can Samba be a Backup Domain Controller to an NT PDC?</A -></DT -><DT ->6.5. <A -HREF="#AEN1300" ->How do I set up a Samba BDC?</A -></DT -><DD -><DL -><DT ->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 ->7. <A -HREF="#ADS" ->Samba as a ADS domain member</A -></DT -><DD -><DL -><DT ->7.1. <A -HREF="#AEN1339" ->Installing the required packages for Debian</A -></DT -><DT ->7.2. <A -HREF="#AEN1346" ->Installing the required packages for RedHat</A -></DT -><DT ->7.3. <A -HREF="#AEN1356" ->Compile Samba</A -></DT -><DT ->7.4. <A -HREF="#AEN1371" ->Setup your /etc/krb5.conf</A -></DT -><DT ->7.5. <A -HREF="#AEN1381" ->Create the computer account</A -></DT -><DD -><DL -><DT ->7.5.1. <A -HREF="#AEN1385" ->Possible errors</A -></DT -></DL -></DD -><DT ->7.6. <A -HREF="#AEN1393" ->Test your server setup</A -></DT -><DT ->7.7. <A -HREF="#AEN1398" ->Testing with smbclient</A -></DT -><DT ->7.8. <A -HREF="#AEN1401" ->Notes</A -></DT -></DL -></DD -><DT ->8. <A -HREF="#DOMAIN-SECURITY" ->Samba as a NT4 or Win2k domain member</A -></DT -><DD -><DL -><DT ->8.1. <A -HREF="#AEN1423" ->Joining an NT Domain with Samba 3.0</A -></DT -><DT ->8.2. <A -HREF="#AEN1478" ->Samba and Windows 2000 Domains</A -></DT -><DT ->8.3. <A -HREF="#AEN1481" ->Why is this better than security = server?</A -></DT -></DL -></DD -></DL -></DIV -></DIV -><DIV -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 5. Samba as a NT4 or Win2k Primary Domain Controller</H1 -><DIV -CLASS="SECT1" -><H2 -CLASS="SECT1" -><A -NAME="AEN722" -></A ->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 -in smb.conf and how to enable and administer password -encryption in Samba. Theses two topics are covered in the -<A -HREF="smb.conf.5.html" -TARGET="_top" -><TT -CLASS="FILENAME" ->smb.conf(5)</TT -></A -> -manpage and the <A -HREF="ENCRYPTION.html" -TARGET="_top" ->Encryption chapter</A -> -of this HOWTO Collection.</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN728" -></A ->5.2. Background</H2 -><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 -><SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->Author's Note:</I -></SPAN -> This document is a combination -of David Bannon's "Samba 2.2 PDC HOWTO" and "Samba NT Domain FAQ". -Both documents are superseded by this one.</P -></TD -></TR -></TABLE -></DIV -><P ->Versions of Samba prior to release 2.2 had marginal capabilities to act -as a Windows NT 4.0 Primary Domain Controller - -(PDC). With Samba 2.2.0, we are proud to announce official support for -Windows NT 4.0-style domain logons from Windows NT 4.0 and Windows -2000 clients. This article outlines the steps -necessary for configuring Samba as a PDC. It is necessary to have a -working Samba server prior to implementing the PDC functionality. If -you have not followed the steps outlined in <A -HREF="UNIX_INSTALL.html" -TARGET="_top" -> UNIX_INSTALL.html</A ->, please make sure -that your server is configured correctly before proceeding. Another -good resource in the <A -HREF="smb.conf.5.html" -TARGET="_top" ->smb.conf(5) man -page</A ->. The following functionality should work in 2.2:</P -><P -></P -><UL -><LI -><P -> domain logons for Windows NT 4.0/2000 clients. - </P -></LI -><LI -><P -> placing a Windows 9x client in user level security - </P -></LI -><LI -><P -> retrieving a list of users and groups from a Samba PDC to - Windows 9x/NT/2000 clients - </P -></LI -><LI -><P -> roving (roaming) user profiles - </P -></LI -><LI -><P -> Windows NT 4.0-style system policies - </P -></LI -></UL -><P ->The following pieces of functionality are not included in the 2.2 release:</P -><P -></P -><UL -><LI -><P -> Windows NT 4 domain trusts - </P -></LI -><LI -><P -> SAM replication with Windows NT 4.0 Domain Controllers - (i.e. a Samba PDC and a Windows NT BDC or vice versa) - </P -></LI -><LI -><P -> Adding users via the User Manager for Domains - </P -></LI -><LI -><P -> Acting as a Windows 2000 Domain Controller (i.e. Kerberos and - Active Directory) - </P -></LI -></UL -><P ->Please note that Windows 9x clients are not true members of a domain -for reasons outlined in this article. Therefore the protocol for -support Windows 9x-style domain logons is completely different -from NT4 domain logons and has been officially supported for some -time.</P -><P ->Implementing a Samba PDC can basically be divided into 2 broad -steps.</P -><P -></P -><OL -TYPE="1" -><LI -><P -> Configuring the Samba PDC - </P -></LI -><LI -><P -> Creating machine trust accounts and joining clients - to the domain - </P -></LI -></OL -><P ->There are other minor details such as user profiles, system -policies, etc... However, these are not necessarily specific -to a Samba PDC as much as they are related to Windows NT networking -concepts. They will be mentioned only briefly here.</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN767" -></A ->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 -attempt to re-explain the parameters here as they are more that -adequately covered in <A -HREF="smb.conf.5.html" -TARGET="_top" -> the smb.conf -man page</A ->. For convenience, the parameters have been -linked with the actual smb.conf description.</P -><P ->Here is an example <TT -CLASS="FILENAME" ->smb.conf</TT -> for acting as a PDC:</P -><P -><PRE -CLASS="PROGRAMLISTING" ->[global] - ; Basic server settings - <A -HREF="smb.conf.5.html#NETBIOSNAME" -TARGET="_top" ->netbios name</A -> = <TT -CLASS="REPLACEABLE" -><I ->POGO</I -></TT -> - <A -HREF="smb.conf.5.html#WORKGROUP" -TARGET="_top" ->workgroup</A -> = <TT -CLASS="REPLACEABLE" -><I ->NARNIA</I -></TT -> - - ; we should act as the domain and local master browser - <A -HREF="smb.conf.5.html#OSLEVEL" -TARGET="_top" ->os level</A -> = 64 - <A -HREF="smb.conf.5.html#PERFERREDMASTER" -TARGET="_top" ->preferred master</A -> = yes - <A -HREF="smb.conf.5.html#DOMAINMASTER" -TARGET="_top" ->domain master</A -> = yes - <A -HREF="smb.conf.5.html#LOCALMASTER" -TARGET="_top" ->local master</A -> = yes - - ; security settings (must user security = user) - <A -HREF="smb.conf.5.html#SECURITYEQUALSUSER" -TARGET="_top" ->security</A -> = user - - ; encrypted passwords are a requirement for a PDC - <A -HREF="smb.conf.5.html#ENCRYPTPASSWORDS" -TARGET="_top" ->encrypt passwords</A -> = yes - - ; support domain logons - <A -HREF="smb.conf.5.html#DOMAINLOGONS" -TARGET="_top" ->domain logons</A -> = yes - - ; where to store user profiles? - <A -HREF="smb.conf.5.html#LOGONPATH" -TARGET="_top" ->logon path</A -> = \\%N\profiles\%u - - ; where is a user's home directory and where should it - ; be mounted at? - <A -HREF="smb.conf.5.html#LOGONDRIVE" -TARGET="_top" ->logon drive</A -> = H: - <A -HREF="smb.conf.5.html#LOGONHOME" -TARGET="_top" ->logon home</A -> = \\homeserver\%u - - ; specify a generic logon script for all users - ; this is a relative **DOS** path to the [netlogon] share - <A -HREF="smb.conf.5.html#LOGONSCRIPT" -TARGET="_top" ->logon script</A -> = logon.cmd - -; necessary share for domain controller -[netlogon] - <A -HREF="smb.conf.5.html#PATH" -TARGET="_top" ->path</A -> = /usr/local/samba/lib/netlogon - <A -HREF="smb.conf.5.html#READONLY" -TARGET="_top" ->read only</A -> = yes - <A -HREF="smb.conf.5.html#WRITELIST" -TARGET="_top" ->write list</A -> = <TT -CLASS="REPLACEABLE" -><I ->ntadmin</I -></TT -> - -; share for storing user profiles -[profiles] - <A -HREF="smb.conf.5.html#PATH" -TARGET="_top" ->path</A -> = /export/smb/ntprofile - <A -HREF="smb.conf.5.html#READONLY" -TARGET="_top" ->read only</A -> = no - <A -HREF="smb.conf.5.html#CREATEMASK" -TARGET="_top" ->create mask</A -> = 0600 - <A -HREF="smb.conf.5.html#DIRECTORYMASK" -TARGET="_top" ->directory mask</A -> = 0700</PRE -></P -><P ->There are a couple of points to emphasize in the above configuration.</P -><P -></P -><UL -><LI -><P -> Encrypted passwords must be enabled. For more details on how - to do this, refer to <A -HREF="ENCRYPTION.html" -TARGET="_top" ->ENCRYPTION.html</A ->. - </P -></LI -><LI -><P -> The server must support domain logons and a - <TT -CLASS="FILENAME" ->[netlogon]</TT -> share - </P -></LI -><LI -><P -> The server must be the domain master browser in order for Windows - client to locate the server as a DC. Please refer to the various - Network Browsing documentation included with this distribution for - details. - </P -></LI -></UL -><P ->As Samba 2.2 does not offer a complete implementation of group mapping -between Windows NT groups and Unix groups (this is really quite -complicated to explain in a short space), you should refer to the -<A -HREF="smb.conf.5.html#DOMAINADMINGROUP" -TARGET="_top" ->domain admin -group</A -> smb.conf parameter for information of creating "Domain -Admins" style accounts.</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN810" -></A ->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 -authenticate a client machine (rather than a user) to the Samba -server. In Windows terminology, this is known as a "Computer -Account."</P -><P ->The password of a machine trust account acts as the shared secret for -secure communication with the Domain Controller. This is a security -feature to prevent an unauthorized machine with the same NetBIOS name -from joining the domain and gaining access to domain user/group -accounts. Windows NT and 2000 clients use machine trust accounts, but -Windows 9x clients do not. Hence, a Windows 9x client is never a true -member of a domain because it does not possess a machine trust -account, and thus has no shared secret with the domain controller.</P -><P ->A Windows PDC stores each machine trust account in the Windows -Registry. A Samba PDC, however, stores each machine trust account -in two parts, as follows: - -<P -></P -><UL -><LI -><P ->A Samba account, stored in the same location as user - LanMan and NT password hashes (currently - <TT -CLASS="FILENAME" ->smbpasswd</TT ->). The Samba account - possesses and uses only the NT password hash.</P -></LI -><LI -><P ->A corresponding Unix account, typically stored in - <TT -CLASS="FILENAME" ->/etc/passwd</TT ->. (Future releases will alleviate the need to - create <TT -CLASS="FILENAME" ->/etc/passwd</TT -> entries.) </P -></LI -></UL -></P -><P ->There are two ways to create machine trust accounts:</P -><P -></P -><UL -><LI -><P -> Manual creation. Both the Samba and corresponding - Unix account are created by hand.</P -></LI -><LI -><P -> "On-the-fly" creation. The Samba machine trust - account is automatically created by Samba at the time the client - is joined to the domain. (For security, this is the - recommended method.) The corresponding Unix account may be - created automatically or manually. </P -></LI -></UL -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN829" -></A ->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 -<TT -CLASS="FILENAME" ->/etc/passwd</TT ->. This can be done using -<B -CLASS="COMMAND" ->vipw</B -> or other 'add user' command that is normally -used to create new Unix accounts. The following is an example for a -Linux based Samba server:</P -><P -> <TT -CLASS="PROMPT" ->root# </TT -><B -CLASS="COMMAND" ->/usr/sbin/useradd -g 100 -d /dev/null -c <TT -CLASS="REPLACEABLE" -><I ->"machine -nickname"</I -></TT -> -s /bin/false <TT -CLASS="REPLACEABLE" -><I ->machine_name</I -></TT ->$ </B -></P -><P -><TT -CLASS="PROMPT" ->root# </TT -><B -CLASS="COMMAND" ->passwd -l <TT -CLASS="REPLACEABLE" -><I ->machine_name</I -></TT ->$</B -></P -><P ->On *BSD systems, this can be done using the 'chpass' utility:</P -><P -><TT -CLASS="PROMPT" ->root# </TT -><B -CLASS="COMMAND" ->chpass -a "<TT -CLASS="REPLACEABLE" -><I ->machine_name</I -></TT ->$:*:101:100::0:0:Workstation <TT -CLASS="REPLACEABLE" -><I ->machine_name</I -></TT ->:/dev/null:/sbin/nologin"</B -></P -><P ->The <TT -CLASS="FILENAME" ->/etc/passwd</TT -> entry will list the machine name -with a "$" appended, won't have a password, will have a null shell and no -home directory. For example a machine named 'doppy' would have an -<TT -CLASS="FILENAME" ->/etc/passwd</TT -> entry like this:</P -><P -><PRE -CLASS="PROGRAMLISTING" ->doppy$:x:505:501:<TT -CLASS="REPLACEABLE" -><I ->machine_nickname</I -></TT ->:/dev/null:/bin/false</PRE -></P -><P ->Above, <TT -CLASS="REPLACEABLE" -><I ->machine_nickname</I -></TT -> can be any -descriptive name for the client, i.e., BasementComputer. -<TT -CLASS="REPLACEABLE" -><I ->machine_name</I -></TT -> absolutely must be the NetBIOS -name of the client to be joined to the domain. The "$" must be -appended to the NetBIOS name of the client or Samba will not recognize -this as a machine trust account.</P -><P ->Now that the corresponding Unix account has been created, the next step is to create -the Samba account for the client containing the well-known initial -machine trust account password. This can be done using the <A -HREF="smbpasswd.8.html" -TARGET="_top" -><B -CLASS="COMMAND" ->smbpasswd(8)</B -></A -> command -as shown here:</P -><P -><TT -CLASS="PROMPT" ->root# </TT -><B -CLASS="COMMAND" ->smbpasswd -a -m <TT -CLASS="REPLACEABLE" -><I ->machine_name</I -></TT -></B -></P -><P ->where <TT -CLASS="REPLACEABLE" -><I ->machine_name</I -></TT -> is the machine's NetBIOS -name. The RID of the new machine account is generated from the UID of -the corresponding Unix account.</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 -><TH -ALIGN="LEFT" -VALIGN="CENTER" -><B ->Join the client to the domain immediately</B -></TH -></TR -><TR -><TD -> </TD -><TD -ALIGN="LEFT" -VALIGN="TOP" -><P -> Manually creating a machine trust account using this method is the - equivalent of creating a machine trust account on a Windows NT PDC using - the "Server Manager". From the time at which the account is created - to the time which the client joins the domain and changes the password, - your domain is vulnerable to an intruder joining your domain using a - a machine with the same NetBIOS name. A PDC inherently trusts - members of the domain and will serve out a large degree of user - information to such clients. You have been warned! - </P -></TD -></TR -></TABLE -></DIV -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN870" -></A ->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 -is joined to the domain. </P -><P ->Since each Samba machine trust account requires a corresponding -Unix account, a method for automatically creating the -Unix account is usually supplied; this requires configuration of the -<A -HREF="smb.conf.5.html#ADDUSERSCRIPT" -TARGET="_top" ->add user script</A -> -option in <TT -CLASS="FILENAME" ->smb.conf</TT ->. This -method is not required, however; corresponding Unix accounts may also -be created manually.</P -><P ->Below is an example for a RedHat 6.2 Linux system.</P -><P -><PRE -CLASS="PROGRAMLISTING" ->[global] - # <...remainder of parameters...> - add user script = /usr/sbin/useradd -d /dev/null -g 100 -s /bin/false -M %u </PRE -></P -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN879" -></A ->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 -><P -></P -><UL -><LI -><P -><SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->Windows 2000</I -></SPAN -></P -><P -> When the user elects to join the client to a domain, Windows prompts for - an account and password that is privileged to join the domain. A - Samba administrative account (i.e., a Samba account that has root - privileges on the Samba server) must be entered here; the - operation will fail if an ordinary user account is given. - The password for this account should be - set to a different password than the associated - <TT -CLASS="FILENAME" ->/etc/passwd</TT -> entry, for security - reasons. </P -><P ->The session key of the Samba administrative account acts as an - encryption key for setting the password of the machine trust - account. The machine trust account will be created on-the-fly, or - updated if it already exists.</P -></LI -><LI -><P -><SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->Windows NT</I -></SPAN -></P -><P -> If the machine trust account was created manually, on the - Identification Changes menu enter the domain name, but do not - check the box "Create a Computer Account in the Domain." In this case, - the existing machine trust account is used to join the machine to - the domain.</P -><P -> If the machine trust account is to be created - on-the-fly, on the Identification Changes menu enter the domain - name, and check the box "Create a Computer Account in the Domain." In - this case, joining the domain proceeds as above for Windows 2000 - (i.e., you must supply a Samba administrative account when - prompted).</P -></LI -></UL -></DIV -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN894" -></A ->5.5. Common Problems and Errors</H2 -><P -></P -><P -></P -><UL -><LI -><P -> <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->I cannot include a '$' in a machine name.</I -></SPAN -> - </P -><P -> A 'machine name' in (typically) <TT -CLASS="FILENAME" ->/etc/passwd</TT -> - of the machine name with a '$' appended. FreeBSD (and other BSD - systems?) won't create a user with a '$' in their name. - </P -><P -> The problem is only in the program used to make the entry, once - made, it works perfectly. So create a user without the '$' and - use <B -CLASS="COMMAND" ->vipw</B -> to edit the entry, adding the '$'. Or create - the whole entry with vipw if you like, make sure you use a - unique User ID ! - </P -></LI -><LI -><P -> <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->I get told "You already have a connection to the Domain...." - or "Cannot join domain, the credentials supplied conflict with an - existing set.." when creating a machine trust account.</I -></SPAN -> - </P -><P -> This happens if you try to create a machine trust account from the - machine itself and already have a connection (e.g. mapped drive) - to a share (or IPC$) on the Samba PDC. The following command - will remove all network drive connections: - </P -><P -> <TT -CLASS="PROMPT" ->C:\WINNT\></TT -> <B -CLASS="COMMAND" ->net use * /d</B -> - </P -><P -> Further, if the machine is a already a 'member of a workgroup' that - is the same name as the domain you are joining (bad idea) you will - get this message. Change the workgroup name to something else, it - does not matter what, reboot, and try again. - </P -></LI -><LI -><P -> <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->The system can not log you on (C000019B)....</I -></SPAN -> - </P -><P ->I joined the domain successfully but after upgrading - to a newer version of the Samba code I get the message, "The system - can not log you on (C000019B), Please try a gain or consult your - system administrator" when attempting to logon. - </P -><P -> This occurs when the domain SID stored in - <TT -CLASS="FILENAME" ->private/WORKGROUP.SID</TT -> is - changed. For example, you remove the file and <B -CLASS="COMMAND" ->smbd</B -> automatically - creates a new one. Or you are swapping back and forth between - versions 2.0.7, TNG and the HEAD branch code (not recommended). The - only way to correct the problem is to restore the original domain - SID or remove the domain client from the domain and rejoin. - </P -></LI -><LI -><P -> <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->The machine trust account for this computer either does not - exist or is not accessible.</I -></SPAN -> - </P -><P -> When I try to join the domain I get the message "The machine account - for this computer either does not exist or is not accessible". What's - wrong? - </P -><P -> This problem is caused by the PDC not having a suitable machine trust account. - If you are using the <TT -CLASS="PARAMETER" -><I ->add user script</I -></TT -> method to create - accounts then this would indicate that it has not worked. Ensure the domain - admin user system is working. - </P -><P -> Alternatively if you are creating account entries manually then they - have not been created correctly. Make sure that you have the entry - correct for the machine trust account in smbpasswd file on the Samba PDC. - If you added the account using an editor rather than using the smbpasswd - utility, make sure that the account name is the machine NetBIOS name - with a '$' appended to it ( i.e. computer_name$ ). There must be an entry - in both /etc/passwd and the smbpasswd file. Some people have reported - that inconsistent subnet masks between the Samba server and the NT - client have caused this problem. Make sure that these are consistent - for both client and server. - </P -></LI -><LI -><P -> <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->When I attempt to login to a Samba Domain from a NT4/W2K workstation, - I get a message about my account being disabled.</I -></SPAN -> - </P -><P -> This problem is caused by a PAM related bug in Samba 2.2.0. This bug is - fixed in 2.2.1. Other symptoms could be unaccessible shares on - NT/W2K member servers in the domain or the following error in your smbd.log: - passdb/pampass.c:pam_account(268) PAM: UNKNOWN ERROR for User: %user% - </P -><P -> At first be ensure to enable the useraccounts with <B -CLASS="COMMAND" ->smbpasswd -e - %user%</B ->, this is normally done, when you create an account. - </P -><P -> In order to work around this problem in 2.2.0, configure the - <TT -CLASS="PARAMETER" -><I ->account</I -></TT -> control flag in - <TT -CLASS="FILENAME" ->/etc/pam.d/samba</TT -> file as follows: - </P -><P -><PRE -CLASS="PROGRAMLISTING" -> account required pam_permit.so - </PRE -></P -><P -> If you want to remain backward compatibility to samba 2.0.x use - <TT -CLASS="FILENAME" ->pam_permit.so</TT ->, it's also possible to use - <TT -CLASS="FILENAME" ->pam_pwdb.so</TT ->. There are some bugs if you try to - use <TT -CLASS="FILENAME" ->pam_unix.so</TT ->, if you need this, be ensure to use - the most recent version of this file. - </P -></LI -></UL -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN942" -></A ->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 -implementing these same items in a Windows NT 4.0 domain. -You should read the white paper <A -HREF="http://www.microsoft.com/ntserver/management/deployment/planguide/prof_policies.asp" -TARGET="_top" ->Implementing -Profiles and Policies in Windows NT 4.0</A -> available from Microsoft.</P -><P ->Here are some additional details:</P -><P -></P -><UL -><LI -><P -> <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->What about Windows NT Policy Editor?</I -></SPAN -> - </P -><P -> To create or edit <TT -CLASS="FILENAME" ->ntconfig.pol</TT -> you must use - the NT Server Policy Editor, <B -CLASS="COMMAND" ->poledit.exe</B -> which - is included with NT Server but <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->not NT Workstation</I -></SPAN ->. - There is a Policy Editor on a NTws - but it is not suitable for creating <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->Domain Policies</I -></SPAN ->. - Further, although the Windows 95 - Policy Editor can be installed on an NT Workstation/Server, it will not - work with NT policies because the registry key that are set by the policy templates. - However, the files from the NT Server will run happily enough on an NTws. - You need <TT -CLASS="FILENAME" ->poledit.exe, common.adm</TT -> and <TT -CLASS="FILENAME" ->winnt.adm</TT ->. It is convenient - to put the two *.adm files in <TT -CLASS="FILENAME" ->c:\winnt\inf</TT -> which is where - the binary will look for them unless told otherwise. Note also that that - directory is 'hidden'. - </P -><P -> The Windows NT policy editor is also included with the Service Pack 3 (and - later) for Windows NT 4.0. Extract the files using <B -CLASS="COMMAND" ->servicepackname /x</B ->, - i.e. that's <B -CLASS="COMMAND" ->Nt4sp6ai.exe /x</B -> for service pack 6a. The policy editor, - <B -CLASS="COMMAND" ->poledit.exe</B -> and the associated template files (*.adm) should - be extracted as well. It is also possible to downloaded the policy template - files for Office97 and get a copy of the policy editor. Another possible - location is with the Zero Administration Kit available for download from Microsoft. - </P -></LI -><LI -><P -> <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->Can Win95 do Policies?</I -></SPAN -> - </P -><P -> Install the group policy handler for Win9x to pick up group - policies. Look on the Win98 CD in <TT -CLASS="FILENAME" ->\tools\reskit\netadmin\poledit</TT ->. - Install group policies on a Win9x client by double-clicking - <TT -CLASS="FILENAME" ->grouppol.inf</TT ->. Log off and on again a couple of - times and see if Win98 picks up group policies. Unfortunately this needs - to be done on every Win9x machine that uses group policies.... - </P -><P -> If group policies don't work one reports suggests getting the updated - (read: working) grouppol.dll for Windows 9x. The group list is grabbed - from /etc/group. - </P -></LI -><LI -><P -> <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->How do I get 'User Manager' and 'Server Manager'</I -></SPAN -> - </P -><P -> Since I don't need to buy an NT Server CD now, how do I get - the 'User Manager for Domains', the 'Server Manager'? - </P -><P -> Microsoft distributes a version of these tools called nexus for - installation on Windows 95 systems. The tools set includes - </P -><P -></P -><UL -><LI -><P ->Server Manager</P -></LI -><LI -><P ->User Manager for Domains</P -></LI -><LI -><P ->Event Viewer</P -></LI -></UL -><P -> Click here to download the archived file <A -HREF="ftp://ftp.microsoft.com/Softlib/MSLFILES/NEXUS.EXE" -TARGET="_top" ->ftp://ftp.microsoft.com/Softlib/MSLFILES/NEXUS.EXE</A -> - </P -><P -> The Windows NT 4.0 version of the 'User Manager for - Domains' and 'Server Manager' are available from Microsoft via ftp - from <A -HREF="ftp://ftp.microsoft.com/Softlib/MSLFILES/SRVTOOLS.EXE" -TARGET="_top" ->ftp://ftp.microsoft.com/Softlib/MSLFILES/SRVTOOLS.EXE</A -> - </P -></LI -></UL -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN986" -></A ->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 -with the samba distribution contain very good explanations of -general SMB topics such as browsing.</P -><P -></P -><UL -><LI -><P -> <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->What are some diagnostics tools I can use to debug the domain logon - process and where can I find them?</I -></SPAN -> - </P -><P -> One of the best diagnostic tools for debugging problems is Samba itself. - You can use the -d option for both smbd and nmbd to specify what - 'debug level' at which to run. See the man pages on smbd, nmbd and - smb.conf for more information on debugging options. The debug - level can range from 1 (the default) to 10 (100 for debugging passwords). - </P -><P -> Another helpful method of debugging is to compile samba using the - <B -CLASS="COMMAND" ->gcc -g </B -> flag. This will include debug - information in the binaries and allow you to attach gdb to the - running smbd / nmbd process. In order to attach gdb to an smbd - process for an NT workstation, first get the workstation to make the - connection. Pressing ctrl-alt-delete and going down to the domain box - is sufficient (at least, on the first time you join the domain) to - generate a 'LsaEnumTrustedDomains'. Thereafter, the workstation - maintains an open connection, and therefore there will be an smbd - process running (assuming that you haven't set a really short smbd - idle timeout) So, in between pressing ctrl alt delete, and actually - typing in your password, you can gdb attach and continue. - </P -><P -> Some useful samba commands worth investigating: - </P -><P -></P -><UL -><LI -><P ->testparam | more</P -></LI -><LI -><P ->smbclient -L //{netbios name of server}</P -></LI -></UL -><P -> An SMB enabled version of tcpdump is available from - <A -HREF="http://www.tcpdump.org/" -TARGET="_top" ->http://www.tcpdup.org/</A ->. - Ethereal, another good packet sniffer for Unix and Win32 - hosts, can be downloaded from <A -HREF="http://www.ethereal.com/" -TARGET="_top" ->http://www.ethereal.com</A ->. - </P -><P -> For tracing things on the Microsoft Windows NT, Network Monitor - (aka. netmon) is available on the Microsoft Developer Network CD's, - the Windows NT Server install CD and the SMS CD's. The version of - netmon that ships with SMS allows for dumping packets between any two - computers (i.e. placing the network interface in promiscuous mode). - The version on the NT Server install CD will only allow monitoring - of network traffic directed to the local NT box and broadcasts on the - local subnet. Be aware that Ethereal can read and write netmon - formatted files. - </P -></LI -><LI -><P -> <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->How do I install 'Network Monitor' on an NT Workstation - or a Windows 9x box?</I -></SPAN -> - </P -><P -> Installing netmon on an NT workstation requires a couple - of steps. The following are for installing Netmon V4.00.349, which comes - with Microsoft Windows NT Server 4.0, on Microsoft Windows NT - Workstation 4.0. The process should be similar for other version of - Windows NT / Netmon. You will need both the Microsoft Windows - NT Server 4.0 Install CD and the Workstation 4.0 Install CD. - </P -><P -> Initially you will need to install 'Network Monitor Tools and Agent' - on the NT Server. To do this - </P -><P -></P -><UL -><LI -><P ->Goto Start - Settings - Control Panel - - Network - Services - Add </P -></LI -><LI -><P ->Select the 'Network Monitor Tools and Agent' and - click on 'OK'.</P -></LI -><LI -><P ->Click 'OK' on the Network Control Panel. - </P -></LI -><LI -><P ->Insert the Windows NT Server 4.0 install CD - when prompted.</P -></LI -></UL -><P -> At this point the Netmon files should exist in - <TT -CLASS="FILENAME" ->%SYSTEMROOT%\System32\netmon\*.*</TT ->. - Two subdirectories exist as well, <TT -CLASS="FILENAME" ->parsers\</TT -> - which contains the necessary DLL's for parsing the netmon packet - dump, and <TT -CLASS="FILENAME" ->captures\</TT ->. - </P -><P -> In order to install the Netmon tools on an NT Workstation, you will - first need to install the 'Network Monitor Agent' from the Workstation - install CD. - </P -><P -></P -><UL -><LI -><P ->Goto Start - Settings - Control Panel - - Network - Services - Add</P -></LI -><LI -><P ->Select the 'Network Monitor Agent' and click - on 'OK'.</P -></LI -><LI -><P ->Click 'OK' on the Network Control Panel. - </P -></LI -><LI -><P ->Insert the Windows NT Workstation 4.0 install - CD when prompted.</P -></LI -></UL -><P -> Now copy the files from the NT Server in %SYSTEMROOT%\System32\netmon\*.* - to %SYSTEMROOT%\System32\netmon\*.* on the Workstation and set - permissions as you deem appropriate for your site. You will need - administrative rights on the NT box to run netmon. - </P -><P -> To install Netmon on a Windows 9x box install the network monitor agent - from the Windows 9x CD (\admin\nettools\netmon). There is a readme - file located with the netmon driver files on the CD if you need - information on how to do this. Copy the files from a working - Netmon installation. - </P -></LI -><LI -><P -> The following is a list if helpful URLs and other links: - </P -><P -></P -><UL -><LI -><P ->Home of Samba site <A -HREF="http://samba.org" -TARGET="_top" -> http://samba.org</A ->. We have a mirror near you !</P -></LI -><LI -><P -> The <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->Development</I -></SPAN -> document - on the Samba mirrors might mention your problem. If so, - it might mean that the developers are working on it.</P -></LI -><LI -><P ->See how Scott Merrill simulates a BDC behavior at - <A -HREF="http://www.skippy.net/linux/smb-howto.html" -TARGET="_top" -> http://www.skippy.net/linux/smb-howto.html</A ->. </P -></LI -><LI -><P ->Although 2.0.7 has almost had its day as a PDC, David Bannon will - keep the 2.0.7 PDC pages at <A -HREF="http://bioserve.latrobe.edu.au/samba" -TARGET="_top" -> http://bioserve.latrobe.edu.au/samba</A -> going for a while yet.</P -></LI -><LI -><P ->Misc links to CIFS information - <A -HREF="http://samba.org/cifs/" -TARGET="_top" ->http://samba.org/cifs/</A -></P -></LI -><LI -><P ->NT Domains for Unix <A -HREF="http://mailhost.cb1.com/~lkcl/ntdom/" -TARGET="_top" -> http://mailhost.cb1.com/~lkcl/ntdom/</A -></P -></LI -><LI -><P ->FTP site for older SMB specs: - <A -HREF="ftp://ftp.microsoft.com/developr/drg/CIFS/" -TARGET="_top" -> ftp://ftp.microsoft.com/developr/drg/CIFS/</A -></P -></LI -></UL -></LI -></UL -><P -></P -><UL -><LI -><P -> <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->How do I get help from the mailing lists?</I -></SPAN -> - </P -><P -> There are a number of Samba related mailing lists. Go to <A -HREF="http://samba.org" -TARGET="_top" ->http://samba.org</A ->, click on your nearest mirror - and then click on <B -CLASS="COMMAND" ->Support</B -> and then click on <B -CLASS="COMMAND" -> Samba related mailing lists</B ->. - </P -><P -> For questions relating to Samba TNG go to - <A -HREF="http://www.samba-tng.org/" -TARGET="_top" ->http://www.samba-tng.org/</A -> - It has been requested that you don't post questions about Samba-TNG to the - main stream Samba lists.</P -><P -> If you post a message to one of the lists please observe the following guide lines : - </P -><P -></P -><UL -><LI -><P -> Always remember that the developers are volunteers, they are - not paid and they never guarantee to produce a particular feature at - a particular time. Any time lines are 'best guess' and nothing more. - </P -></LI -><LI -><P -> Always mention what version of samba you are using and what - operating system its running under. You should probably list the - relevant sections of your smb.conf file, at least the options - in [global] that affect PDC support.</P -></LI -><LI -><P ->In addition to the version, if you obtained Samba via - CVS mention the date when you last checked it out.</P -></LI -><LI -><P -> Try and make your question clear and brief, lots of long, - convoluted questions get deleted before they are completely read ! - Don't post html encoded messages (if you can select colour or font - size its html).</P -></LI -><LI -><P -> If you run one of those nifty 'I'm on holidays' things when - you are away, make sure its configured to not answer mailing lists. - </P -></LI -><LI -><P -> Don't cross post. Work out which is the best list to post to - and see what happens, i.e. don't post to both samba-ntdom and samba-technical. - Many people active on the lists subscribe to more - than one list and get annoyed to see the same message two or more times. - Often someone will see a message and thinking it would be better dealt - with on another, will forward it on for you.</P -></LI -><LI -><P ->You might include <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->partial</I -></SPAN -> - log files written at a debug level set to as much as 20. - Please don't send the entire log but enough to give the context of the - error messages.</P -></LI -><LI -><P ->(Possibly) If you have a complete netmon trace ( from the opening of - the pipe to the error ) you can send the *.CAP file as well.</P -></LI -><LI -><P ->Please think carefully before attaching a document to an email. - Consider pasting the relevant parts into the body of the message. The samba - mailing lists go to a huge number of people, do they all need a copy of your - smb.conf in their attach directory?</P -></LI -></UL -></LI -><LI -><P -> <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->How do I get off the mailing lists?</I -></SPAN -> - </P -><P ->To have your name removed from a samba mailing list, go to the - same place you went to to get on it. Go to <A -HREF="http://lists.samba.org/" -TARGET="_top" ->http://lists.samba.org</A ->, - click on your nearest mirror and then click on <B -CLASS="COMMAND" ->Support</B -> and - then click on <B -CLASS="COMMAND" -> Samba related mailing lists</B ->. Or perhaps see - <A -HREF="http://lists.samba.org/mailman/roster/samba-ntdom" -TARGET="_top" ->here</A -> - </P -><P -> Please don't post messages to the list asking to be removed, you will just - be referred to the above address (unless that process failed in some way...) - </P -></LI -></UL -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN1100" -></A ->5.8. Domain Control for Windows 9x/ME</H2 -><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 ->The following section contains much of the original -DOMAIN.txt file previously included with Samba. Much of -the material is based on what went into the book <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->Special -Edition, Using Samba</I -></SPAN ->, by Richard Sharpe.</P -></TD -></TR -></TABLE -></DIV -><P ->A domain and a workgroup are exactly the same thing in terms of network -browsing. The difference is that a distributable authentication -database is associated with a domain, for secure login access to a -network. Also, different access rights can be granted to users if they -successfully authenticate against a domain logon server (NT server and -other systems based on NT server support this, as does at least Samba TNG now).</P -><P ->The SMB client logging on to a domain has an expectation that every other -server in the domain should accept the same authentication information. -Network browsing functionality of domains and workgroups is -identical and is explained in BROWSING.txt. It should be noted, that browsing -is totally orthogonal to logon support.</P -><P ->Issues related to the single-logon network model are discussed in this -section. Samba supports domain logons, network logon scripts, and user -profiles for MS Windows for workgroups and MS Windows 9X/ME clients -which will be the focus of this section.</P -><P ->When an SMB client in a domain wishes to logon it broadcast requests for a -logon server. The first one to reply gets the job, and validates its -password using whatever mechanism the Samba administrator has installed. -It is possible (but very stupid) to create a domain where the user -database is not shared between servers, i.e. they are effectively workgroup -servers advertising themselves as participating in a domain. This -demonstrates how authentication is quite different from but closely -involved with domains.</P -><P ->Using these features you can make your clients verify their logon via -the Samba server; make clients run a batch file when they logon to -the network and download their preferences, desktop and start menu.</P -><P ->Before launching into the configuration instructions, it is -worthwhile lookingat how a Windows 9x/ME client performs a logon:</P -><P -></P -><OL -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 - 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. - </P -></LI -><LI -><P -> The client then connects to that server, logs on (does an SMBsessetupX) and - then connects to the IPC$ share (using an SMBtconX). - </P -></LI -><LI -><P -> The client then does a NetWkstaUserLogon request, which retrieves the name - of the user's logon script. - </P -></LI -><LI -><P -> The client then connects to the NetLogon share and searches for this - and if it is found and can be read, is retrieved and executed by the client. - After this, the client disconnects from the NetLogon share. - </P -></LI -><LI -><P -> The client then sends a NetUserGetInfo request to the server, to retrieve - the user's home share, which is used to search for profiles. Since the - response to the NetUserGetInfo request does not contain much more - the user's home share, profiles for Win9X clients MUST reside in the user - home directory. - </P -></LI -><LI -><P -> The client then connects to the user's home share and searches for the - user's profile. As it turns out, you can specify the user's home share as - a sharename and path. For example, \\server\fred\.profile. - If the profiles are found, they are implemented. - </P -></LI -><LI -><P -> The client then disconnects from the user's home share, and reconnects to - the NetLogon share and looks for CONFIG.POL, the policies file. If this is - found, it is read and implemented. - </P -></LI -></OL -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN1126" -></A ->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 -><P -></P -><UL -><LI -><P ->Password encryption is not required for a Windows 9x logon server.</P -></LI -><LI -><P ->Windows 9x/ME clients do not possess machine trust accounts.</P -></LI -></UL -><P ->Therefore, a Samba PDC will also act as a Windows 9x logon -server.</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 -><TH -ALIGN="LEFT" -VALIGN="CENTER" -><B ->security mode and master browsers</B -></TH -></TR -><TR -><TD -> </TD -><TD -ALIGN="LEFT" -VALIGN="TOP" -><P ->There are a few comments to make in order to tie up some -loose ends. There has been much debate over the issue of whether -or not it is ok to configure Samba as a Domain Controller in security -modes other than <TT -CLASS="CONSTANT" ->USER</TT ->. The only security mode -which will not work due to technical reasons is <TT -CLASS="CONSTANT" ->SHARE</TT -> -mode security. <TT -CLASS="CONSTANT" ->DOMAIN</TT -> and <TT -CLASS="CONSTANT" ->SERVER</TT -> -mode security is really just a variation on SMB user level security.</P -><P ->Actually, this issue is also closely tied to the debate on whether -or not Samba must be the domain master browser for its workgroup -when operating as a DC. While it may technically be possible -to configure a server as such (after all, browsing and domain logons -are two distinctly different functions), it is not a good idea to -so. You should remember that the DC must register the DOMAIN#1b NetBIOS -name. This is the name used by Windows clients to locate the DC. -Windows clients do not distinguish between the DC and the DMB. -For this reason, it is very wise to configure the Samba DC as the DMB.</P -><P ->Now back to the issue of configuring a Samba DC to use a mode other -than "security = user". If a Samba host is configured to use -another SMB server or DC in order to validate user connection -requests, then it is a fact that some other machine on the network -(the "password server") knows more about user than the Samba host. -99% of the time, this other host is a domain controller. Now -in order to operate in domain mode security, the "workgroup" parameter -must be set to the name of the Windows NT domain (which already -has a domain controller, right?)</P -><P ->Therefore configuring a Samba box as a DC for a domain that -already by definition has a PDC is asking for trouble. -Therefore, you should always configure the Samba DC to be the DMB -for its domain.</P -></TD -></TR -></TABLE -></DIV -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN1145" -></A ->5.8.2. Configuration Instructions: Setting up Roaming User Profiles</H3 -><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 -><SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->NOTE!</I -></SPAN -> Roaming profiles support is different -for Win9X and WinNT.</P -></TD -></TR -></TABLE -></DIV -><P ->Before discussing how to configure roaming profiles, it is useful to see how -Win9X and WinNT clients implement these features.</P -><P ->Win9X clients send a NetUserGetInfo request to the server to get the user's -profiles location. However, the response does not have room for a separate -profiles location field, only the user's home share. This means that Win9X -profiles are restricted to being in the user's home directory.</P -><P ->WinNT clients send a NetSAMLogon RPC request, which contains many fields, -including a separate field for the location of the user's profiles. -This means that support for profiles is different for Win9X and WinNT.</P -><DIV -CLASS="SECT3" -><HR><H4 -CLASS="SECT3" -><A -NAME="AEN1153" -></A ->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 -><P -><PRE -CLASS="PROGRAMLISTING" ->logon path = \\profileserver\profileshare\profilepath\%U\moreprofilepath</PRE -></P -><P ->The default for this option is \\%N\%U\profile, namely -\\sambaserver\username\profile. The \\N%\%U service is created -automatically by the [homes] service. -If you are using a samba server for the profiles, you _must_ make the -share specified in the logon path browseable. </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 ->[lkcl 26aug96 - we have discovered a problem where Windows clients can -maintain a connection to the [homes] share in between logins. The -[homes] share must NOT therefore be used in a profile path.]</P -></TD -></TR -></TABLE -></DIV -></DIV -><DIV -CLASS="SECT3" -><HR><H4 -CLASS="SECT3" -><A -NAME="AEN1161" -></A ->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 -on the "logon home" parameter.</P -><P ->By using the logon home parameter, you are restricted to putting Win9X -profiles in the user's home directory. But wait! There is a trick you -can use. If you set the following in the [global] section of your -smb.conf file:</P -><P -><PRE -CLASS="PROGRAMLISTING" ->logon home = \\%L\%U\.profiles</PRE -></P -><P ->then your Win9X clients will dutifully put their clients in a subdirectory -of your home directory called .profiles (thus making them hidden).</P -><P ->Not only that, but 'net use/home' will also work, because of a feature in -Win9X. It removes any directory stuff off the end of the home directory area -and only uses the server and share portion. That is, it looks like you -specified \\%L\%U for "logon home".</P -></DIV -><DIV -CLASS="SECT3" -><HR><H4 -CLASS="SECT3" -><A -NAME="AEN1169" -></A ->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 -><P -><PRE -CLASS="PROGRAMLISTING" ->logon home = \\%L\%U\.profiles -logon path = \\%L\profiles\%U</PRE -></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 ->I have not checked what 'net use /home' does on NT when "logon home" is -set as above.</P -></TD -></TR -></TABLE -></DIV -></DIV -><DIV -CLASS="SECT3" -><HR><H4 -CLASS="SECT3" -><A -NAME="AEN1176" -></A ->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". -These directories and their contents will be merged with the local -versions stored in c:\windows\profiles\username on subsequent logins, -taking the most recent from each. You will need to use the [global] -options "preserve case = yes", "short preserve case = yes" and -"case sensitive = no" in order to maintain capital letters in shortcuts -in any of the profile folders.</P -><P ->The user.DAT file contains all the user's preferences. If you wish to -enforce a set of preferences, rename their user.DAT file to user.MAN, -and deny them write access to this file.</P -><P -></P -><OL -TYPE="1" -><LI -><P -> On the Windows 95 machine, go to Control Panel | Passwords and - select the User Profiles tab. Select the required level of - roaming preferences. Press OK, but do _not_ allow the computer - to reboot. - </P -></LI -><LI -><P -> On the Windows 95 machine, go to Control Panel | Network | - Client for Microsoft Networks | Preferences. Select 'Log on to - NT Domain'. Then, ensure that the Primary Logon is 'Client for - Microsoft Networks'. Press OK, and this time allow the computer - to reboot. - </P -></LI -></OL -><P ->Under Windows 95, Profiles are downloaded from the Primary Logon. -If you have the Primary Logon as 'Client for Novell Networks', then -the profiles and logon script will be downloaded from your Novell -Server. If you have the Primary Logon as 'Windows Logon', then the -profiles will be loaded from the local machine - a bit against the -concept of roaming profiles, if you ask me.</P -><P ->You will now find that the Microsoft Networks Login box contains -[user, password, domain] instead of just [user, password]. Type in -the samba server's domain name (or any other domain known to exist, -but bear in mind that the user will be authenticated against this -domain and profiles downloaded from it, if that domain logon server -supports it), user name and user's password.</P -><P ->Once the user has been successfully validated, the Windows 95 machine -will inform you that 'The user has not logged on before' and asks you -if you wish to save the user's preferences? Select 'yes'.</P -><P ->Once the Windows 95 client comes up with the desktop, you should be able -to examine the contents of the directory specified in the "logon path" -on the samba server and verify that the "Desktop", "Start Menu", -"Programs" and "Nethood" folders have been created.</P -><P ->These folders will be cached locally on the client, and updated when -the user logs off (if you haven't made them read-only by then :-). -You will find that if the user creates further folders or short-cuts, -that the client will merge the profile contents downloaded with the -contents of the profile directory already on the local client, taking -the newest folders and short-cuts from each set.</P -><P ->If you have made the folders / files read-only on the samba server, -then you will get errors from the w95 machine on logon and logout, as -it attempts to merge the local and the remote profile. Basically, if -you have any errors reported by the w95 machine, check the Unix file -permissions and ownership rights on the profile directory contents, -on the samba server.</P -><P ->If you have problems creating user profiles, you can reset the user's -local desktop cache, as shown below. When this user then next logs in, -they will be told that they are logging in "for the first time".</P -><P -></P -><OL -TYPE="1" -><LI -><P -> instead of logging in under the [user, password, domain] dialog, - press escape. - </P -></LI -><LI -><P -> run the regedit.exe program, and look in: - </P -><P -> HKEY_LOCAL_MACHINE\Windows\CurrentVersion\ProfileList - </P -><P -> you will find an entry, for each user, of ProfilePath. Note the - contents of this key (likely to be c:\windows\profiles\username), - then delete the key ProfilePath for the required user. - </P -><P -> [Exit the registry editor]. - </P -></LI -><LI -><P -> <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->WARNING</I -></SPAN -> - before deleting the contents of the - directory listed in - the ProfilePath (this is likely to be c:\windows\profiles\username), - ask them if they have any important files stored on their desktop - or in their start menu. delete the contents of the directory - ProfilePath (making a backup if any of the files are needed). - </P -><P -> This will have the effect of removing the local (read-only hidden - system file) user.DAT in their profile directory, as well as the - local "desktop", "nethood", "start menu" and "programs" folders. - </P -></LI -><LI -><P -> search for the user's .PWL password-caching file in the c:\windows - directory, and delete it. - </P -></LI -><LI -><P -> log off the windows 95 client. - </P -></LI -><LI -><P -> check the contents of the profile path (see "logon path" described - above), and delete the user.DAT or user.MAN file for the user, - making a backup if required. - </P -></LI -></OL -><P ->If all else fails, increase samba's debug log levels to between 3 and 10, -and / or run a packet trace program such as tcpdump or netmon.exe, and -look for any error reports.</P -><P ->If you have access to an NT server, then first set up roaming profiles -and / or netlogons on the NT server. Make a packet trace, or examine -the example packet traces provided with NT server, and see what the -differences are with the equivalent samba trace.</P -></DIV -><DIV -CLASS="SECT3" -><HR><H4 -CLASS="SECT3" -><A -NAME="AEN1212" -></A ->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 -through the "logon path" parameter. </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 ->[lkcl 10aug97 - i tried setting the path to -\\samba-server\homes\profile, and discovered that this fails because -a background process maintains the connection to the [homes] share -which does _not_ close down in between user logins. you have to -have \\samba-server\%L\profile, where user is the username created -from the [homes] share].</P -></TD -></TR -></TABLE -></DIV -><P ->There is a parameter that is now available for use with NT Profiles: -"logon drive". This should be set to "h:" or any other drive, and -should be used in conjunction with the new "logon home" parameter.</P -><P ->The entry for the NT 4.0 profile is a _directory_ not a file. The NT -help on profiles mentions that a directory is also created with a .PDS -extension. The user, while logging in, must have write permission to -create the full profile path (and the folder with the .PDS extension) -[lkcl 10aug97 - i found that the creation of the .PDS directory failed, -and had to create these manually for each user, with a shell script. -also, i presume, but have not tested, that the full profile path must -be browseable just as it is for w95, due to the manner in which they -attempt to create the full profile path: test existence of each path -component; create path component].</P -><P ->In the profile directory, NT creates more folders than 95. It creates -"Application Data" and others, as well as "Desktop", "Nethood", -"Start Menu" and "Programs". The profile itself is stored in a file -NTuser.DAT. Nothing appears to be stored in the .PDS directory, and -its purpose is currently unknown.</P -><P ->You can use the System Control Panel to copy a local profile onto -a samba server (see NT Help on profiles: it is also capable of firing -up the correct location in the System Control Panel for you). The -NT Help file also mentions that renaming NTuser.DAT to NTuser.MAN -turns a profile into a mandatory one.</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 ->[lkcl 10aug97 - i notice that NT Workstation tells me that it is -downloading a profile from a slow link. whether this is actually the -case, or whether there is some configuration issue, as yet unknown, -that makes NT Workstation _think_ that the link is a slow one is a -matter to be resolved].</P -><P ->[lkcl 20aug97 - after samba digest correspondence, one user found, and -another confirmed, that profiles cannot be loaded from a samba server -unless "security = user" and "encrypt passwords = yes" (see the file -ENCRYPTION.txt) or "security = server" and "password server = ip.address. -of.yourNTserver" are used. Either of these options will allow the NT -workstation to access the samba server using LAN manager encrypted -passwords, without the user intervention normally required by NT -workstation for clear-text passwords].</P -><P ->[lkcl 25aug97 - more comments received about NT profiles: the case of -the profile _matters_. the file _must_ be called NTuser.DAT or, for -a mandatory profile, NTuser.MAN].</P -></TD -></TR -></TABLE -></DIV -></DIV -><DIV -CLASS="SECT3" -><HR><H4 -CLASS="SECT3" -><A -NAME="AEN1225" -></A ->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 -profile be stored on a samba server, or any other SMB server, as long as -that SMB server supports encrypted passwords.</P -></DIV -><DIV -CLASS="SECT3" -><HR><H4 -CLASS="SECT3" -><A -NAME="AEN1228" -></A ->5.8.2.7. Sharing Profiles between W95 and NT Workstation 4.0</H4 -><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 -><TH -ALIGN="LEFT" -VALIGN="CENTER" -><B ->Potentially outdated or incorrect material follows</B -></TH -></TR -><TR -><TD -> </TD -><TD -ALIGN="LEFT" -VALIGN="TOP" -><P ->I think this is all bogus, but have not deleted it. (Richard Sharpe)</P -></TD -></TR -></TABLE -></DIV -><P ->The default logon path is \\%N\%U. NT Workstation will attempt to create -a directory "\\samba-server\username.PDS" if you specify the logon path -as "\\samba-server\username" with the NT User Manager. Therefore, you -will need to specify (for example) "\\samba-server\username\profile". -NT 4.0 will attempt to create "\\samba-server\username\profile.PDS", which -is more likely to succeed.</P -><P ->If you then want to share the same Start Menu / Desktop with W95, you will -need to specify "logon path = \\samba-server\username\profile" [lkcl 10aug97 -this has its drawbacks: i created a shortcut to telnet.exe, which attempts -to run from the c:\winnt\system32 directory. this directory is obviously -unlikely to exist on a Win95-only host].</P -><P -> If you have this set up correctly, you will find separate user.DAT and -NTuser.DAT files in the same profile directory.</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 ->[lkcl 25aug97 - there are some issues to resolve with downloading of -NT profiles, probably to do with time/date stamps. i have found that -NTuser.DAT is never updated on the workstation after the first time that -it is copied to the local workstation profile directory. this is in -contrast to w95, where it _does_ transfer / update profiles correctly].</P -></TD -></TR -></TABLE -></DIV -></DIV -></DIV -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN1238" -></A ->5.9. DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba</H2 -><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 -><TH -ALIGN="LEFT" -VALIGN="CENTER" -><B ->Possibly Outdated Material</B -></TH -></TR -><TR -><TD -> </TD -><TD -ALIGN="LEFT" -VALIGN="TOP" -><P -> This appendix was originally authored by John H Terpstra of - the Samba Team and is included here for posterity. - </P -></TD -></TR -></TABLE -></DIV -><P -><SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->NOTE :</I -></SPAN -> -The term "Domain Controller" and those related to it refer to one specific -method of authentication that can underly an SMB domain. Domain Controllers -prior to Windows NT Server 3.1 were sold by various companies and based on -private extensions to the LAN Manager 2.1 protocol. Windows NT introduced -Microsoft-specific ways of distributing the user authentication database. -See DOMAIN.txt for examples of how Samba can participate in or create -SMB domains based on shared authentication database schemes other than the -Windows NT SAM.</P -><P ->Windows NT Server can be installed as either a plain file and print server -(WORKGROUP workstation or server) or as a server that participates in Domain -Control (DOMAIN member, Primary Domain controller or Backup Domain controller). -The same is true for OS/2 Warp Server, Digital Pathworks and other similar -products, all of which can participate in Domain Control along with Windows NT.</P -><P ->To many people these terms can be confusing, so let's try to clear the air.</P -><P ->Every Windows NT system (workstation or server) has a registry database. -The registry contains entries that describe the initialization information -for all services (the equivalent of Unix Daemons) that run within the Windows -NT environment. The registry also contains entries that tell application -software where to find dynamically loadable libraries that they depend upon. -In fact, the registry contains entries that describes everything that anything -may need to know to interact with the rest of the system.</P -><P ->The registry files can be located on any Windows NT machine by opening a -command prompt and typing:</P -><P -><TT -CLASS="PROMPT" ->C:\WINNT\></TT -> dir %SystemRoot%\System32\config</P -><P ->The environment variable %SystemRoot% value can be obtained by typing:</P -><P -><TT -CLASS="PROMPT" ->C:\WINNT></TT ->echo %SystemRoot%</P -><P ->The active parts of the registry that you may want to be familiar with are -the files called: default, system, software, sam and security.</P -><P ->In a domain environment, Microsoft Windows NT domain controllers participate -in replication of the SAM and SECURITY files so that all controllers within -the domain have an exactly identical copy of each.</P -><P ->The Microsoft Windows NT system is structured within a security model that -says that all applications and services must authenticate themselves before -they can obtain permission from the security manager to do what they set out -to do.</P -><P ->The Windows NT User database also resides within the registry. This part of -the registry contains the user's security identifier, home directory, group -memberships, desktop profile, and so on.</P -><P ->Every Windows NT system (workstation as well as server) will have its own -registry. Windows NT Servers that participate in Domain Security control -have a database that they share in common - thus they do NOT own an -independent full registry database of their own, as do Workstations and -plain Servers.</P -><P ->The User database is called the SAM (Security Access Manager) database and -is used for all user authentication as well as for authentication of inter- -process authentication (i.e. to ensure that the service action a user has -requested is permitted within the limits of that user's privileges).</P -><P ->The Samba team have produced a utility that can dump the Windows NT SAM into -smbpasswd format: see ENCRYPTION.txt for information on smbpasswd and -/pub/samba/pwdump on your nearest Samba mirror for the utility. This -facility is useful but cannot be easily used to implement SAM replication -to Samba systems.</P -><P ->Windows for Workgroups, Windows 95, and Windows NT Workstations and Servers -can participate in a Domain security system that is controlled by Windows NT -servers that have been correctly configured. Almost every domain will have -ONE Primary Domain Controller (PDC). It is desirable that each domain will -have at least one Backup Domain Controller (BDC).</P -><P ->The PDC and BDCs then participate in replication of the SAM database so that -each Domain Controlling participant will have an up to date SAM component -within its registry.</P -></DIV -></DIV -><DIV -CLASS="CHAPTER" -><HR><H1 -><A -NAME="SAMBA-BDC" -></A ->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="AEN1274" -></A ->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 -as described in the <A -HREF="Samba-PDC-HOWTO.html" -TARGET="_top" ->Samba-PDC-HOWTO</A ->.</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN1278" -></A ->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 -user logs into a Windows NT Workstation, the workstation connects to a -Domain Controller and asks him whether the username and password the -user typed in is correct. The Domain Controller replies with a lot of -information about the user, for example the place where the users -profile is stored, the users full name of the user. All this -information is stored in the NT user database, the so-called SAM.</P -><P ->There are two kinds of Domain Controller in a NT 4 compatible Domain: -A Primary Domain Controller (PDC) and one or more Backup Domain -Controllers (BDC). The PDC contains the master copy of the -SAM. Whenever the SAM has to change, for example when a user changes -his password, this change has to be done on the PDC. A Backup Domain -Controller is a machine that maintains a read-only copy of the -SAM. This way it is able to reply to logon requests and authenticate -users in case the PDC is not available. During this time no changes to -the SAM are possible. Whenever changes to the SAM are done on the PDC, -all BDC receive the changes from the PDC.</P -><P ->Since version 2.2 Samba officially supports domain logons for all -current Windows Clients, including Windows 2000 and XP. This text -assumes the domain to be named SAMBA. To be able to act as a PDC, some -parameters in the [global]-section of the smb.conf have to be set:</P -><P -><PRE -CLASS="PROGRAMLISTING" ->workgroup = SAMBA -domain master = yes -domain logons = yes</PRE -></P -><P ->Several other things like a [homes] and a [netlogon] share also may be -set along with settings for the profile path, the users home drive and -others. This will not be covered in this document.</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN1286" -></A ->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 -by broadcast on the local network. The PDC also registers the unique -NetBIOS name SAMBA#1b with the WINS server. The name type #1b is -normally reserved for the domain master browser, a role that has -nothing to do with anything related to authentication, but the -Microsoft Domain implementation requires the domain master browser to -be on the same machine as the PDC.</P -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN1289" -></A ->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 -this by doing a NetBIOS name query for the group name SAMBA#1c. It -assumes that each of the machines it gets back from the queries is a -domain controller and can answer logon requests. To not open security -holes both the workstation and the selected (TODO: How is the DC -chosen) domain controller authenticate each other. After that the -workstation sends the user's credentials (his name and password) to -the domain controller, asking for approval.</P -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN1292" -></A ->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 -for SAMBA#1b, assuming this machine maintains the master copy of the -SAM. The workstation contacts the PDC, both mutually authenticate and -the password change is done.</P -></DIV -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN1295" -></A ->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 -service logon requests whenever the PDC is down.</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN1300" -></A ->6.5. How do I set up a Samba BDC?</H2 -><P ->Several things have to be done:</P -><P -></P -><UL -><LI -><P ->The domain SID has to be the same on the PDC and the BDC. This used to -be stored in the file private/MACHINE.SID. This file is not created -anymore since Samba 2.2.5 or even earlier. Nowadays the domain SID is -stored in the file private/secrets.tdb. Simply copying the secrets.tdb -from the PDC to the BDC does not work, as the BDC would -generate a new SID for itself and override the domain SID with this -new BDC SID.</P -><P ->To retrieve the domain SID from the PDC or an existing BDC and store it in the -secrets.tdb, execute 'net rpc getsid' on the BDC.</P -></LI -><LI -><P ->The Unix user database has to be synchronized from the PDC to the -BDC. This means that both the /etc/passwd and /etc/group have to be -replicated from the PDC to the BDC. This can be done manually -whenever changes are made, or the PDC is set up as a NIS master -server and the BDC as a NIS slave server. To set up the BDC as a -mere NIS client would not be enough, as the BDC would not be able to -access its user database in case of a PDC failure.</P -></LI -><LI -><P ->The Samba password database in the file private/smbpasswd has to be -replicated from the PDC to the BDC. This is a bit tricky, see the -next section.</P -></LI -><LI -><P ->Any netlogon share has to be replicated from the PDC to the -BDC. This can be done manually whenever login scripts are changed, -or it can be done automatically together with the smbpasswd -synchronization.</P -></LI -></UL -><P ->Finally, the BDC has to be found by the workstations. This can be done -by setting</P -><P -><PRE -CLASS="PROGRAMLISTING" ->workgroup = samba -domain master = no -domain logons = yes</PRE -></P -><P ->in the [global]-section of the smb.conf of the BDC. This makes the BDC -only register the name SAMBA#1c with the WINS server. This is no -problem as the name SAMBA#1c is a NetBIOS group name that is meant to -be registered by more than one machine. The parameter 'domain master = -no' forces the BDC not to register SAMBA#1b which as a unique NetBIOS -name is reserved for the Primary Domain Controller.</P -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN1317" -></A ->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 -done in the smbpasswd file and has to be replicated to the BDC. So -replicating the smbpasswd file very often is necessary.</P -><P ->As the smbpasswd file contains plain text password equivalents, it -must not be sent unencrypted over the wire. The best way to set up -smbpasswd replication from the PDC to the BDC is to use the utility -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 -CLASS="CHAPTER" -><HR><H1 -><A -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 -><P -><P -></P -><TABLE -BORDER="0" -><TBODY -><TR -><TD ->a Windows 2000 server.</TD -></TR -><TR -><TD ->samba 3.0 or higher.</TD -></TR -><TR -><TD ->the MIT kerberos development libraries (either install from the above sources or use a package). The heimdal libraries will not work.</TD -></TR -><TR -><TD ->the OpenLDAP development libraries.</TD -></TR -></TBODY -></TABLE -><P -></P -></P -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN1339" -></A ->7.1. Installing the required packages for Debian</H2 -><P ->On Debian you need to install the following packages:</P -><P -><P -></P -><TABLE -BORDER="0" -><TBODY -><TR -><TD ->libkrb5-dev</TD -></TR -><TR -><TD ->krb5-user</TD -></TR -></TBODY -></TABLE -><P -></P -></P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN1346" -></A ->7.2. Installing the required packages for RedHat</H2 -><P ->On RedHat this means you should have at least: </P -><P -><P -></P -><TABLE -BORDER="0" -><TBODY -><TR -><TD ->krb5-workstation (for kinit)</TD -></TR -><TR -><TD ->krb5-libs (for linking with)</TD -></TR -><TR -><TD ->krb5-devel (because you are compiling from source)</TD -></TR -></TBODY -></TABLE -><P -></P -></P -><P ->in addition to the standard development environment.</P -><P ->Note that these are not standard on a RedHat install, and you may need -to get them off CD2.</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN1356" -></A ->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 it - generates contains - lines like this:</P -><P -><PRE -CLASS="PROGRAMLISTING" ->#define HAVE_KRB5 1 -#define HAVE_LDAP 1</PRE -></P -><P ->If it doesn't then configure did not find your krb5 libraries or - your ldap libraries. Look in config.log to figure out why and fix - it.</P -><P ->Then compile and install Samba as usual. You must use at least the - following 3 options in smb.conf:</P -><P -><PRE -CLASS="PROGRAMLISTING" -> realm = YOUR.KERBEROS.REALM - security = ADS - encrypt passwords = yes</PRE -></P -><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, 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 -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN1371" -></A ->7.4. Setup your /etc/krb5.conf</H2 -><P ->The minimal configuration for krb5.conf is:</P -><P -><PRE -CLASS="PROGRAMLISTING" ->[realms] - YOUR.KERBEROS.REALM = { - kdc = your.kerberos.server - }</PRE -></P -><P ->Test your config by doing a "kinit USERNAME@REALM" and making sure that - your password is accepted by the Win2000 KDC. </P -><P ->NOTE: The realm must be uppercase. </P -><P ->You also must ensure that you can do a reverse DNS lookup on the IP -address of your KDC. Also, the name that this reverse lookup maps to -must either be the netbios name of the KDC (ie. the hostname with no -domain attached) or it can alternatively be the netbios name -followed by the realm. </P -><P ->The easiest way to ensure you get this right is to add a /etc/hosts -entry mapping the IP address of your KDC to its netbios name. If you -don't get this right then you will get a "local error" when you try -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 for smbd and winbindd.</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN1381" -></A ->7.5. Create the computer account</H2 -><P ->As a user that has write permission on the Samba private directory -(usually root) run: -<B -CLASS="COMMAND" ->net ads join</B -></P -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN1385" -></A ->7.5.1. Possible errors</H3 -><P -><P -></P -><DIV -CLASS="VARIABLELIST" -><DL -><DT ->"ADS support not compiled in"</DT -><DD -><P ->Samba must be reconfigured (remove config.cache) and recompiled (make clean all install) after the kerberos libs and headers are installed.</P -></DD -></DL -></DIV -></P -></DIV -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN1393" -></A ->7.6. Test your server setup</H2 -><P ->On a Windows 2000 client try <B -CLASS="COMMAND" ->net use * \\server\share</B ->. You should -be logged in with kerberos without needing to know a password. If -this fails then run <B -CLASS="COMMAND" ->klist tickets</B ->. Did you get a ticket for the -server? Does it have an encoding type of DES-CBC-MD5 ? </P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN1398" -></A ->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 -specify the -k option to choose kerberos authentication.</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN1401" -></A ->7.8. Notes</H2 -><P ->You must change administrator password at least once after DC install, - to create the right encoding types</P -><P ->w2k doesn't seem to create the _kerberos._udp and _ldap._tcp in - their defaults DNS setup. Maybe fixed in service packs?</P -></DIV -></DIV -><DIV -CLASS="CHAPTER" -><HR><H1 -><A -NAME="DOMAIN-SECURITY" -></A ->Chapter 8. Samba as a NT4 or Win2k domain member</H1 -><DIV -CLASS="SECT1" -><H2 -CLASS="SECT1" -><A -NAME="AEN1423" -></A ->8.1. Joining an NT Domain with Samba 3.0</H2 -><P ->Assume you have a Samba 3.0 server with a NetBIOS name of - <TT -CLASS="CONSTANT" ->SERV1</TT -> and are joining an or Win2k NT domain called - <TT -CLASS="CONSTANT" ->DOM</TT ->, which has a PDC with a NetBIOS name - of <TT -CLASS="CONSTANT" ->DOMPDC</TT -> and two backup domain controllers - with NetBIOS names <TT -CLASS="CONSTANT" ->DOMBDC1</TT -> and <TT -CLASS="CONSTANT" ->DOMBDC2 - </TT ->.</P -><P ->Firstly, you must edit your <A -HREF="smb.conf.5.html" -TARGET="_top" -><TT -CLASS="FILENAME" ->smb.conf(5)</TT -> - </A -> file to tell Samba it should now use domain security.</P -><P ->Change (or add) your <A -HREF="smb.conf.5.html#SECURITY" -TARGET="_top" -> <TT -CLASS="PARAMETER" -><I ->security =</I -></TT -></A -> line in the [global] section - of your smb.conf to read:</P -><P -><B -CLASS="COMMAND" ->security = domain</B -> 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" -TARGET="_top" -><TT -CLASS="PARAMETER" -><I -> workgroup =</I -></TT -></A -> line in the [global] section to read: </P -><P -><B -CLASS="COMMAND" ->workgroup = DOM</B -></P -><P ->as this is the name of the domain we are joining. </P -><P ->You must also have the parameter <A -HREF="smb.conf.5.html#ENCRYPTPASSWORDS" -TARGET="_top" -> <TT -CLASS="PARAMETER" -><I ->encrypt passwords</I -></TT -></A -> set to <TT -CLASS="CONSTANT" ->yes - </TT -> in order for your users to authenticate to the NT PDC.</P -><P ->Finally, add (or modify) a <A -HREF="smb.conf.5.html#PASSWORDSERVER" -TARGET="_top" -> <TT -CLASS="PARAMETER" -><I ->password server =</I -></TT -></A -> line in the [global] - section to read: </P -><P -><B -CLASS="COMMAND" ->password server = DOMPDC DOMBDC1 DOMBDC2</B -></P -><P ->These are the primary and backup domain controllers Samba - will attempt to contact in order to authenticate users. Samba will - try to contact each of these servers in order, so you may want to - rearrange this list in order to spread out the authentication load - among domain controllers.</P -><P ->Alternatively, if you want smbd to automatically determine - the list of Domain controllers to use for authentication, you may - set this line to be :</P -><P -><B -CLASS="COMMAND" ->password server = *</B -></P -><P ->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 -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN1478" -></A ->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. The steps above apply -to both NT4 and Windows 2000.</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN1481" -></A ->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 - to your server. This means that if domain user <TT -CLASS="CONSTANT" ->DOM\fred - </TT -> attaches to your domain security Samba server, there needs - to be a local Unix user fred to represent that user in the Unix - filesystem. This is very similar to the older Samba security mode - <A -HREF="smb.conf.5.html#SECURITYEQUALSSERVER" -TARGET="_top" ->security = server</A ->, - where Samba would pass through the authentication request to a Windows - NT server in the same way as a Windows 95 or Windows 98 server would. - </P -><P ->Please refer to the <A -HREF="winbind.html" -TARGET="_top" ->Winbind - paper</A -> for information on a system to automatically - assign UNIX uids and gids to Windows NT Domain users and groups. - This code is available in development branches only at the moment, - but will be moved to release branches soon.</P -><P ->The advantage to domain-level security is that the - authentication in domain-level security is passed down the authenticated - RPC channel in exactly the same way that an NT server would do it. This - means Samba servers now participate in domain trust relationships in - exactly the same way NT servers do (i.e., you can add Samba servers into - a resource domain and have the authentication passed on from a resource - domain PDC to an account domain PDC.</P -><P ->In addition, with <B -CLASS="COMMAND" ->security = server</B -> every Samba - daemon on a server has to keep a connection open to the - authenticating server for as long as that daemon lasts. This can drain - the connection resources on a Microsoft NT server and cause it to run - out of available connections. With <B -CLASS="COMMAND" ->security = domain</B ->, - however, the Samba daemons connect to the PDC/BDC only for as long - as is necessary to authenticate the user, and then drop the connection, - thus conserving PDC connection resources.</P -><P ->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. </P -><P -><SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->NOTE:</I -></SPAN -> Much of the text of this document - was first published in the Web magazine <A -HREF="http://www.linuxworld.com" -TARGET="_top" -> - LinuxWorld</A -> as the article <A -HREF="http://www.linuxworld.com/linuxworld/lw-1998-10/lw-10-samba.html" -TARGET="_top" ->Doing - the NIS/NT Samba</A ->.</P -></DIV -></DIV -></DIV -><DIV -CLASS="PART" -><A -NAME="OPTIONAL" -></A -><DIV -CLASS="TITLEPAGE" -><H1 -CLASS="TITLE" ->III. Optional configuration</H1 -><DIV -CLASS="PARTINTRO" -><A -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 -part each cover one specific feature.</P -></DIV -><DIV -CLASS="TOC" -><DL -><DT -><B ->Table of Contents</B -></DT -><DT ->9. <A -HREF="#INTEGRATE-MS-NETWORKS" ->Integrating MS Windows networks with Samba</A -></DT -><DD -><DL -><DT ->9.1. <A -HREF="#AEN1513" ->Agenda</A -></DT -><DT ->9.2. <A -HREF="#AEN1535" ->Name Resolution in a pure Unix/Linux world</A -></DT -><DD -><DL -><DT ->9.2.1. <A -HREF="#AEN1551" -><TT -CLASS="FILENAME" ->/etc/hosts</TT -></A -></DT -><DT ->9.2.2. <A -HREF="#AEN1567" -><TT -CLASS="FILENAME" ->/etc/resolv.conf</TT -></A -></DT -><DT ->9.2.3. <A -HREF="#AEN1578" -><TT -CLASS="FILENAME" ->/etc/host.conf</TT -></A -></DT -><DT ->9.2.4. <A -HREF="#AEN1586" -><TT -CLASS="FILENAME" ->/etc/nsswitch.conf</TT -></A -></DT -></DL -></DD -><DT ->9.3. <A -HREF="#AEN1598" ->Name resolution as used within MS Windows networking</A -></DT -><DD -><DL -><DT ->9.3.1. <A -HREF="#AEN1610" ->The NetBIOS Name Cache</A -></DT -><DT ->9.3.2. <A -HREF="#AEN1615" ->The LMHOSTS file</A -></DT -><DT ->9.3.3. <A -HREF="#AEN1623" ->HOSTS file</A -></DT -><DT ->9.3.4. <A -HREF="#AEN1628" ->DNS Lookup</A -></DT -><DT ->9.3.5. <A -HREF="#AEN1631" ->WINS Lookup</A -></DT -></DL -></DD -><DT ->9.4. <A -HREF="#AEN1643" ->How browsing functions and how to deploy stable and -dependable browsing using Samba</A -></DT -><DT ->9.5. <A -HREF="#AEN1653" ->MS Windows security options and how to configure -Samba for seemless integration</A -></DT -><DD -><DL -><DT ->9.5.1. <A -HREF="#AEN1681" ->Use MS Windows NT as an authentication server</A -></DT -><DT ->9.5.2. <A -HREF="#AEN1689" ->Make Samba a member of an MS Windows NT security domain</A -></DT -><DT ->9.5.3. <A -HREF="#AEN1706" ->Configure Samba as an authentication server</A -></DT -></DL -></DD -><DT ->9.6. <A -HREF="#AEN1723" ->Conclusions</A -></DT -></DL -></DD -><DT ->10. <A -HREF="#UNIX-PERMISSIONS" ->UNIX Permission Bits and Windows NT Access Control Lists</A -></DT -><DD -><DL -><DT ->10.1. <A -HREF="#AEN1744" ->Viewing and changing UNIX permissions using the NT - security dialogs</A -></DT -><DT ->10.2. <A -HREF="#AEN1748" ->How to view file security on a Samba share</A -></DT -><DT ->10.3. <A -HREF="#AEN1759" ->Viewing file ownership</A -></DT -><DT ->10.4. <A -HREF="#AEN1779" ->Viewing file or directory permissions</A -></DT -><DD -><DL -><DT ->10.4.1. <A -HREF="#AEN1794" ->File Permissions</A -></DT -><DT ->10.4.2. <A -HREF="#AEN1808" ->Directory Permissions</A -></DT -></DL -></DD -><DT ->10.5. <A -HREF="#AEN1815" ->Modifying file or directory permissions</A -></DT -><DT ->10.6. <A -HREF="#AEN1837" ->Interaction with the standard Samba create mask - parameters</A -></DT -><DT ->10.7. <A -HREF="#AEN1901" ->Interaction with the standard Samba file attribute - mapping</A -></DT -></DL -></DD -><DT ->11. <A -HREF="#PAM" ->Configuring PAM for distributed but centrally -managed authentication</A -></DT -><DD -><DL -><DT ->11.1. <A -HREF="#AEN1922" ->Samba and PAM</A -></DT -><DT ->11.2. <A -HREF="#AEN1966" ->Distributed Authentication</A -></DT -><DT ->11.3. <A -HREF="#AEN1973" ->PAM Configuration in smb.conf</A -></DT -></DL -></DD -><DT ->12. <A -HREF="#MSDFS" ->Hosting a Microsoft Distributed File System tree on Samba</A -></DT -><DD -><DL -><DT ->12.1. <A -HREF="#AEN1993" ->Instructions</A -></DT -><DD -><DL -><DT ->12.1.1. <A -HREF="#AEN2028" ->Notes</A -></DT -></DL -></DD -></DL -></DD -><DT ->13. <A -HREF="#PRINTING" ->Printing Support</A -></DT -><DD -><DL -><DT ->13.1. <A -HREF="#AEN2054" ->Introduction</A -></DT -><DT ->13.2. <A -HREF="#AEN2076" ->Configuration</A -></DT -><DD -><DL -><DT ->13.2.1. <A -HREF="#AEN2084" ->Creating [print$]</A -></DT -><DT ->13.2.2. <A -HREF="#AEN2119" ->Setting Drivers for Existing Printers</A -></DT -><DT ->13.2.3. <A -HREF="#AEN2135" ->Support a large number of printers</A -></DT -><DT ->13.2.4. <A -HREF="#AEN2146" ->Adding New Printers via the Windows NT APW</A -></DT -><DT ->13.2.5. <A -HREF="#AEN2176" ->Samba and Printer Ports</A -></DT -></DL -></DD -><DT ->13.3. <A -HREF="#AEN2184" ->The Imprints Toolset</A -></DT -><DD -><DL -><DT ->13.3.1. <A -HREF="#AEN2188" ->What is Imprints?</A -></DT -><DT ->13.3.2. <A -HREF="#AEN2198" ->Creating Printer Driver Packages</A -></DT -><DT ->13.3.3. <A -HREF="#AEN2201" ->The Imprints server</A -></DT -><DT ->13.3.4. <A -HREF="#AEN2205" ->The Installation Client</A -></DT -></DL -></DD -><DT ->13.4. <A -HREF="#AEN2227" ->Diagnosis</A -></DT -><DD -><DL -><DT ->13.4.1. <A -HREF="#AEN2229" ->Introduction</A -></DT -><DT ->13.4.2. <A -HREF="#AEN2245" ->Debugging printer problems</A -></DT -><DT ->13.4.3. <A -HREF="#AEN2254" ->What printers do I have?</A -></DT -><DT ->13.4.4. <A -HREF="#AEN2262" ->Setting up printcap and print servers</A -></DT -><DT ->13.4.5. <A -HREF="#AEN2290" ->Job sent, no output</A -></DT -><DT ->13.4.6. <A -HREF="#AEN2301" ->Job sent, strange output</A -></DT -><DT ->13.4.7. <A -HREF="#AEN2313" ->Raw PostScript printed</A -></DT -><DT ->13.4.8. <A -HREF="#AEN2316" ->Advanced Printing</A -></DT -><DT ->13.4.9. <A -HREF="#AEN2319" ->Real debugging</A -></DT -></DL -></DD -></DL -></DD -><DT ->14. <A -HREF="#WINBIND" ->Unified Logons between Windows NT and UNIX using Winbind</A -></DT -><DD -><DL -><DT ->14.1. <A -HREF="#AEN2360" ->Abstract</A -></DT -><DT ->14.2. <A -HREF="#AEN2364" ->Introduction</A -></DT -><DT ->14.3. <A -HREF="#AEN2377" ->What Winbind Provides</A -></DT -><DD -><DL -><DT ->14.3.1. <A -HREF="#AEN2384" ->Target Uses</A -></DT -></DL -></DD -><DT ->14.4. <A -HREF="#AEN2388" ->How Winbind Works</A -></DT -><DD -><DL -><DT ->14.4.1. <A -HREF="#AEN2393" ->Microsoft Remote Procedure Calls</A -></DT -><DT ->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 ->14.4.4. <A -HREF="#AEN2416" ->Pluggable Authentication Modules</A -></DT -><DT ->14.4.5. <A -HREF="#AEN2424" ->User and Group ID Allocation</A -></DT -><DT ->14.4.6. <A -HREF="#AEN2428" ->Result Caching</A -></DT -></DL -></DD -><DT ->14.5. <A -HREF="#AEN2431" ->Installation and Configuration</A -></DT -><DD -><DL -><DT ->14.5.1. <A -HREF="#AEN2438" ->Introduction</A -></DT -><DT ->14.5.2. <A -HREF="#AEN2451" ->Requirements</A -></DT -><DT ->14.5.3. <A -HREF="#AEN2465" ->Testing Things Out</A -></DT -></DL -></DD -><DT ->14.6. <A -HREF="#AEN2680" ->Limitations</A -></DT -><DT ->14.7. <A -HREF="#AEN2690" ->Conclusion</A -></DT -></DL -></DD -><DT ->15. <A -HREF="#IMPROVED-BROWSING" ->Improved browsing in samba</A -></DT -><DD -><DL -><DT ->15.1. <A -HREF="#AEN2700" ->Overview of browsing</A -></DT -><DT ->15.2. <A -HREF="#AEN2704" ->Browsing support in samba</A -></DT -><DT ->15.3. <A -HREF="#AEN2713" ->Problem resolution</A -></DT -><DT ->15.4. <A -HREF="#AEN2720" ->Browsing across subnets</A -></DT -><DD -><DL -><DT ->15.4.1. <A -HREF="#AEN2725" ->How does cross subnet browsing work ?</A -></DT -></DL -></DD -><DT ->15.5. <A -HREF="#AEN2760" ->Setting up a WINS server</A -></DT -><DT ->15.6. <A -HREF="#AEN2779" ->Setting up Browsing in a WORKGROUP</A -></DT -><DT ->15.7. <A -HREF="#AEN2797" ->Setting up Browsing in a DOMAIN</A -></DT -><DT ->15.8. <A -HREF="#AEN2807" ->Forcing samba to be the master</A -></DT -><DT ->15.9. <A -HREF="#AEN2816" ->Making samba the domain master</A -></DT -><DT ->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 ->16.1. <A -HREF="#AEN2855" ->Introduction and configuration</A -></DT -><DT ->16.2. <A -HREF="#AEN2864" ->Included modules</A -></DT -><DD -><DL -><DT ->16.2.1. <A -HREF="#AEN2866" ->audit</A -></DT -><DT ->16.2.2. <A -HREF="#AEN2874" ->recycle</A -></DT -><DT ->16.2.3. <A -HREF="#AEN2911" ->netatalk</A -></DT -></DL -></DD -><DT ->16.3. <A -HREF="#AEN2918" ->VFS modules available elsewhere</A -></DT -><DD -><DL -><DT ->16.3.1. <A -HREF="#AEN2922" ->DatabaseFS</A -></DT -><DT ->16.3.2. <A -HREF="#AEN2930" ->vscan</A -></DT -></DL -></DD -></DL -></DD -><DT ->17. <A -HREF="#CVS-ACCESS" ->Access Samba source code via CVS</A -></DT -><DD -><DL -><DT ->17.1. <A -HREF="#AEN2942" ->Introduction</A -></DT -><DT ->17.2. <A -HREF="#AEN2947" ->CVS Access to samba.org</A -></DT -><DD -><DL -><DT ->17.2.1. <A -HREF="#AEN2950" ->Access via CVSweb</A -></DT -><DT ->17.2.2. <A -HREF="#AEN2955" ->Access via cvs</A -></DT -></DL -></DD -></DL -></DD -><DT ->18. <A -HREF="#GROUPMAPPING" ->Group mapping HOWTO</A -></DT -><DT ->19. <A -HREF="#SPEED" ->Samba performance issues</A -></DT -><DD -><DL -><DT ->19.1. <A -HREF="#AEN3033" ->Comparisons</A -></DT -><DT ->19.2. <A -HREF="#AEN3039" ->Socket options</A -></DT -><DT ->19.3. <A -HREF="#AEN3046" ->Read size</A -></DT -><DT ->19.4. <A -HREF="#AEN3051" ->Max xmit</A -></DT -><DT ->19.5. <A -HREF="#AEN3056" ->Log level</A -></DT -><DT ->19.6. <A -HREF="#AEN3059" ->Read raw</A -></DT -><DT ->19.7. <A -HREF="#AEN3064" ->Write raw</A -></DT -><DT ->19.8. <A -HREF="#AEN3068" ->Slow Clients</A -></DT -><DT ->19.9. <A -HREF="#AEN3072" ->Slow Logins</A -></DT -><DT ->19.10. <A -HREF="#AEN3075" ->Client tuning</A -></DT -></DL -></DD -><DT ->20. <A -HREF="#GROUPPROFILES" ->Creating Group Profiles</A -></DT -><DD -><DL -><DT ->20.1. <A -HREF="#AEN3123" ->Windows '9x</A -></DT -><DT ->20.2. <A -HREF="#AEN3132" ->Windows NT 4</A -></DT -><DD -><DL -><DT ->20.2.1. <A -HREF="#AEN3155" ->Side bar Notes</A -></DT -><DT ->20.2.2. <A -HREF="#AEN3159" ->Mandatory profiles</A -></DT -><DT ->20.2.3. <A -HREF="#AEN3162" ->moveuser.exe</A -></DT -><DT ->20.2.4. <A -HREF="#AEN3165" ->Get SID</A -></DT -></DL -></DD -><DT ->20.3. <A -HREF="#AEN3170" ->Windows 2000/XP</A -></DT -></DL -></DD -></DL -></DIV -></DIV -><DIV -CLASS="CHAPTER" -><HR><H1 -><A -NAME="INTEGRATE-MS-NETWORKS" -></A ->Chapter 9. Integrating MS Windows networks with Samba</H1 -><DIV -CLASS="SECT1" -><H2 -CLASS="SECT1" -><A -NAME="AEN1513" -></A ->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 -replacing MS Windows NT/2000 technology.</P -><P ->We will examine:</P -><P -></P -><OL -TYPE="1" -><LI -><P ->Name resolution in a pure Unix/Linux TCP/IP - environment - </P -></LI -><LI -><P ->Name resolution as used within MS Windows - networking - </P -></LI -><LI -><P ->How browsing functions and how to deploy stable - and dependable browsing using Samba - </P -></LI -><LI -><P ->MS Windows security options and how to - configure Samba for seemless integration - </P -></LI -><LI -><P ->Configuration of Samba as:</P -><P -></P -><OL -TYPE="a" -><LI -><P ->A stand-alone server</P -></LI -><LI -><P ->An MS Windows NT 3.x/4.0 security domain member - </P -></LI -><LI -><P ->An alternative to an MS Windows NT 3.x/4.0 Domain Controller - </P -></LI -></OL -></LI -></OL -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN1535" -></A ->9.2. Name Resolution in a pure Unix/Linux world</H2 -><P ->The key configuration files covered in this section are:</P -><P -></P -><UL -><LI -><P -><TT -CLASS="FILENAME" ->/etc/hosts</TT -></P -></LI -><LI -><P -><TT -CLASS="FILENAME" ->/etc/resolv.conf</TT -></P -></LI -><LI -><P -><TT -CLASS="FILENAME" ->/etc/host.conf</TT -></P -></LI -><LI -><P -><TT -CLASS="FILENAME" ->/etc/nsswitch.conf</TT -></P -></LI -></UL -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN1551" -></A ->9.2.1. <TT -CLASS="FILENAME" ->/etc/hosts</TT -></H3 -><P ->Contains a static list of IP Addresses and names. -eg:</P -><P -><PRE -CLASS="PROGRAMLISTING" -> 127.0.0.1 localhost localhost.localdomain - 192.168.1.1 bigbox.caldera.com bigbox alias4box</PRE -></P -><P ->The purpose of <TT -CLASS="FILENAME" ->/etc/hosts</TT -> is to provide a -name resolution mechanism so that uses do not need to remember -IP addresses.</P -><P ->Network packets that are sent over the physical network transport -layer communicate not via IP addresses but rather using the Media -Access Control address, or MAC address. IP Addresses are currently -32 bits in length and are typically presented as four (4) decimal -numbers that are separated by a dot (or period). eg: 168.192.1.1</P -><P ->MAC Addresses use 48 bits (or 6 bytes) and are typically represented -as two digit hexadecimal numbers separated by colons. eg: -40:8e:0a:12:34:56</P -><P ->Every network interfrace must have an MAC address. Associated with -a MAC address there may be one or more IP addresses. There is NO -relationship between an IP address and a MAC address, all such assignments -are arbitary or discretionary in nature. At the most basic level all -network communications takes place using MAC addressing. Since MAC -addresses must be globally unique, and generally remains fixed for -any particular interface, the assignment of an IP address makes sense -from a network management perspective. More than one IP address can -be assigned per MAC address. One address must be the primary IP address, -this is the address that will be returned in the ARP reply.</P -><P ->When a user or a process wants to communicate with another machine -the protocol implementation ensures that the "machine name" or "host -name" is resolved to an IP address in a manner that is controlled -by the TCP/IP configuration control files. The file -<TT -CLASS="FILENAME" ->/etc/hosts</TT -> is one such file.</P -><P ->When the IP address of the destination interface has been -determined a protocol called ARP/RARP is used to identify -the MAC address of the target interface. ARP stands for Address -Resolution Protocol, and is a broadcast oriented method that -uses UDP (User Datagram Protocol) to send a request to all -interfaces on the local network segment using the all 1's MAC -address. Network interfaces are programmed to respond to two -MAC addresses only; their own unique address and the address -ff:ff:ff:ff:ff:ff. The reply packet from an ARP request will -contain the MAC address and the primary IP address for each -interface.</P -><P ->The <TT -CLASS="FILENAME" ->/etc/hosts</TT -> file is foundational to all -Unix/Linux TCP/IP installations and as a minumum will contain -the localhost and local network interface IP addresses and the -primary names by which they are known within the local machine. -This file helps to prime the pump so that a basic level of name -resolution can exist before any other method of name resolution -becomes available.</P -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN1567" -></A ->9.2.2. <TT -CLASS="FILENAME" ->/etc/resolv.conf</TT -></H3 -><P ->This file tells the name resolution libraries:</P -><P -></P -><UL -><LI -><P ->The name of the domain to which the machine - belongs - </P -></LI -><LI -><P ->The name(s) of any domains that should be - automatically searched when trying to resolve unqualified - host names to their IP address - </P -></LI -><LI -><P ->The name or IP address of available Domain - Name Servers that may be asked to perform name to address - translation lookups - </P -></LI -></UL -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN1578" -></A ->9.2.3. <TT -CLASS="FILENAME" ->/etc/host.conf</TT -></H3 -><P -><TT -CLASS="FILENAME" ->/etc/host.conf</TT -> is the primary means by -which the setting in /etc/resolv.conf may be affected. It is a -critical configuration file. This file controls the order by -which name resolution may procede. The typical structure is:</P -><P -><PRE -CLASS="PROGRAMLISTING" -> order hosts,bind - multi on</PRE -></P -><P ->then both addresses should be returned. Please refer to the -man page for host.conf for further details.</P -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN1586" -></A ->9.2.4. <TT -CLASS="FILENAME" ->/etc/nsswitch.conf</TT -></H3 -><P ->This file controls the actual name resolution targets. The -file typically has resolver object specifications as follows:</P -><P -><PRE -CLASS="PROGRAMLISTING" -> # /etc/nsswitch.conf - # - # Name Service Switch configuration file. - # - - passwd: compat - # Alternative entries for password authentication are: - # passwd: compat files nis ldap winbind - shadow: compat - group: compat - - hosts: files nis dns - # Alternative entries for host name resolution are: - # hosts: files dns nis nis+ hesoid db compat ldap wins - networks: nis files dns - - ethers: nis files - protocols: nis files - rpc: nis files - services: nis files</PRE -></P -><P ->Of course, each of these mechanisms requires that the appropriate -facilities and/or services are correctly configured.</P -><P ->It should be noted that unless a network request/message must be -sent, TCP/IP networks are silent. All TCP/IP communications assumes a -principal of speaking only when necessary.</P -><P ->Starting with version 2.2.0 samba has Linux support for extensions to -the name service switch infrastructure so that linux clients will -be able to obtain resolution of MS Windows NetBIOS names to IP -Addresses. To gain this functionality Samba needs to be compiled -with appropriate arguments to the make command (ie: <B -CLASS="COMMAND" ->make -nsswitch/libnss_wins.so</B ->). The resulting library should -then be installed in the <TT -CLASS="FILENAME" ->/lib</TT -> directory and -the "wins" parameter needs to be added to the "hosts:" line in -the <TT -CLASS="FILENAME" ->/etc/nsswitch.conf</TT -> file. At this point it -will be possible to ping any MS Windows machine by it's NetBIOS -machine name, so long as that machine is within the workgroup to -which both the samba machine and the MS Windows machine belong.</P -></DIV -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN1598" -></A ->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 -the "computer name", "machine name", "networking name", "netbios name", -"SMB name". All terms mean the same thing with the exception of -"netbios name" which can apply also to the name of the workgroup or the -domain name. The terms "workgroup" and "domain" are really just a -simply name with which the machine is associated. All NetBIOS names -are exactly 16 characters in length. The 16th character is reserved. -It is used to store a one byte value that indicates service level -information for the NetBIOS name that is registered. A NetBIOS machine -name is therefore registered for each service type that is provided by -the client/server.</P -><P ->The following are typical NetBIOS name/service type registrations:</P -><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 - - 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 -></P -><P ->It should be noted that all NetBIOS machines register their own -names as per the above. This is in vast contrast to TCP/IP -installations where traditionally the system administrator will -determine in the /etc/hosts or in the DNS database what names -are associated with each IP address.</P -><P ->One further point of clarification should be noted, the <TT -CLASS="FILENAME" ->/etc/hosts</TT -> -file and the DNS records do not provide the NetBIOS name type information -that MS Windows clients depend on to locate the type of service that may -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 -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 ->The name "workgroup" or "domain" really can be confusing since these -have the added significance of indicating what is the security -architecture of the MS Windows network. The term "workgroup" indicates -that the primary nature of the network environment is that of a -peer-to-peer design. In a WORKGROUP all machines are responsible for -their own security, and generally such security is limited to use of -just a password (known as SHARE MODE security). In most situations -with peer-to-peer networking the users who control their own machines -will simply opt to have no security at all. It is possible to have -USER MODE security in a WORKGROUP environment, thus requiring use -of a user name and a matching password.</P -><P ->MS Windows networking is thus predetermined to use machine names -for all local and remote machine message passing. The protocol used is -called Server Message Block (SMB) and this is implemented using -the NetBIOS protocol (Network Basic Input Output System). NetBIOS can -be encapsulated using LLC (Logical Link Control) protocol - in which case -the resulting protocol is called NetBEUI (Network Basic Extended User -Interface). NetBIOS can also be run over IPX (Internetworking Packet -Exchange) protocol as used by Novell NetWare, and it can be run -over TCP/IP protocols - in which case the resulting protocol is called -NBT or NetBT, the NetBIOS over TCP/IP.</P -><P ->MS Windows machines use a complex array of name resolution mechanisms. -Since we are primarily concerned with TCP/IP this demonstration is -limited to this area.</P -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN1610" -></A ->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 -machines that that machine has communicated with over the -past 10-15 minutes. It is more efficient to obtain an IP address -for a machine from the local cache than it is to go through all the -configured name resolution mechanisms.</P -><P ->If a machine whose name is in the local name cache has been shut -down before the name had been expired and flushed from the cache, then -an attempt to exchange a message with that machine will be subject -to time-out delays. i.e.: Its name is in the cache, so a name resolution -lookup will succeed, but the machine can not respond. This can be -frustrating for users - but it is a characteristic of the protocol.</P -><P ->The MS Windows utility that allows examination of the NetBIOS -name cache is called "nbtstat". The Samba equivalent of this -is called "nmblookup".</P -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN1615" -></A ->9.3.2. The LMHOSTS file</H3 -><P ->This file is usually located in MS Windows NT 4.0 or -2000 in <TT -CLASS="FILENAME" ->C:\WINNT\SYSTEM32\DRIVERS\ETC</TT -> and contains -the IP Address and the machine name in matched pairs. The -<TT -CLASS="FILENAME" ->LMHOSTS</TT -> file performs NetBIOS name -to IP address mapping oriented.</P -><P ->It typically looks like:</P -><P -><PRE -CLASS="PROGRAMLISTING" -> # Copyright (c) 1998 Microsoft Corp. - # - # This is a sample LMHOSTS file used by the Microsoft Wins Client (NetBIOS - # over TCP/IP) stack for Windows98 - # - # This file contains the mappings of IP addresses to NT computernames - # (NetBIOS) names. Each entry should be kept on an individual line. - # The IP address should be placed in the first column followed by the - # corresponding computername. The address and the comptername - # should be separated by at least one space or tab. The "#" character - # is generally used to denote the start of a comment (see the exceptions - # below). - # - # This file is compatible with Microsoft LAN Manager 2.x TCP/IP lmhosts - # files and offers the following extensions: - # - # #PRE - # #DOM:<domain> - # #INCLUDE <filename> - # #BEGIN_ALTERNATE - # #END_ALTERNATE - # \0xnn (non-printing character support) - # - # Following any entry in the file with the characters "#PRE" will cause - # the entry to be preloaded into the name cache. By default, entries are - # not preloaded, but are parsed only after dynamic name resolution fails. - # - # Following an entry with the "#DOM:<domain>" tag will associate the - # entry with the domain specified by <domain>. This affects how the - # browser and logon services behave in TCP/IP environments. To preload - # the host name associated with #DOM entry, it is necessary to also add a - # #PRE to the line. The <domain> is always preloaded although it will not - # be shown when the name cache is viewed. - # - # Specifying "#INCLUDE <filename>" will force the RFC NetBIOS (NBT) - # software to seek the specified <filename> and parse it as if it were - # local. <filename> is generally a UNC-based name, allowing a - # centralized lmhosts file to be maintained on a server. - # It is ALWAYS necessary to provide a mapping for the IP address of the - # server prior to the #INCLUDE. This mapping must use the #PRE directive. - # In addtion the share "public" in the example below must be in the - # LanManServer list of "NullSessionShares" in order for client machines to - # be able to read the lmhosts file successfully. This key is under - # \machine\system\currentcontrolset\services\lanmanserver\parameters\nullsessionshares - # in the registry. Simply add "public" to the list found there. - # - # The #BEGIN_ and #END_ALTERNATE keywords allow multiple #INCLUDE - # statements to be grouped together. Any single successful include - # will cause the group to succeed. - # - # Finally, non-printing characters can be embedded in mappings by - # first surrounding the NetBIOS name in quotations, then using the - # \0xnn notation to specify a hex value for a non-printing character. - # - # The following example illustrates all of these extensions: - # - # 102.54.94.97 rhino #PRE #DOM:networking #net group's DC - # 102.54.94.102 "appname \0x14" #special app server - # 102.54.94.123 popular #PRE #source server - # 102.54.94.117 localsrv #PRE #needed for the include - # - # #BEGIN_ALTERNATE - # #INCLUDE \\localsrv\public\lmhosts - # #INCLUDE \\rhino\public\lmhosts - # #END_ALTERNATE - # - # In the above example, the "appname" server contains a special - # character in its name, the "popular" and "localsrv" server names are - # preloaded, and the "rhino" server name is specified so it can be used - # to later #INCLUDE a centrally maintained lmhosts file if the "localsrv" - # system is unavailable. - # - # Note that the whole file is parsed including comments on each lookup, - # so keeping the number of comments to a minimum will improve performance. - # Therefore it is not advisable to simply add lmhosts file entries onto the - # end of this file.</PRE -></P -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN1623" -></A ->9.3.3. HOSTS file</H3 -><P ->This file is usually located in MS Windows NT 4.0 or 2000 in -<TT -CLASS="FILENAME" ->C:\WINNT\SYSTEM32\DRIVERS\ETC</TT -> and contains -the IP Address and the IP hostname in matched pairs. It can be -used by the name resolution infrastructure in MS Windows, depending -on how the TCP/IP environment is configured. This file is in -every way the equivalent of the Unix/Linux <TT -CLASS="FILENAME" ->/etc/hosts</TT -> file.</P -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN1628" -></A ->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 -is followed the precise nature of which isdependant on what the NetBIOS -Node Type parameter is configured to. A Node Type of 0 means use -NetBIOS broadcast (over UDP broadcast) is first used if the name -that is the subject of a name lookup is not found in the NetBIOS name -cache. If that fails then DNS, HOSTS and LMHOSTS are checked. If set to -Node Type 8, then a NetBIOS Unicast (over UDP Unicast) is sent to the -WINS Server to obtain a lookup before DNS, HOSTS, LMHOSTS, or broadcast -lookup is used.</P -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN1631" -></A ->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 -the names and IP addresses that are registered by a Windows client -if the TCP/IP setup has been given at least one WINS Server IP Address.</P -><P ->To configure Samba to be a WINS server the following parameter needs -to be added to the <TT -CLASS="FILENAME" ->smb.conf</TT -> file:</P -><P -><PRE -CLASS="PROGRAMLISTING" -> wins support = Yes</PRE -></P -><P ->To configure Samba to use a WINS server the following parameters are -needed in the smb.conf file:</P -><P -><PRE -CLASS="PROGRAMLISTING" -> wins support = No - wins server = xxx.xxx.xxx.xxx</PRE -></P -><P ->where <TT -CLASS="REPLACEABLE" -><I ->xxx.xxx.xxx.xxx</I -></TT -> is the IP address -of the WINS server.</P -></DIV -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN1643" -></A ->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 -(i.e.: the machine name for each service type in operation) on start -up. Also, as stated above, the exact method by which this name registration -takes place is determined by whether or not the MS Windows client/server -has been given a WINS server address, whether or not LMHOSTS lookup -is enabled, or if DNS for NetBIOS name resolution is enabled, etc.</P -><P ->In the case where there is no WINS server all name registrations as -well as name lookups are done by UDP broadcast. This isolates name -resolution to the local subnet, unless LMHOSTS is used to list all -names and IP addresses. In such situations Samba provides a means by -which the samba server name may be forcibly injected into the browse -list of a remote MS Windows network (using the "remote announce" parameter).</P -><P ->Where a WINS server is used, the MS Windows client will use UDP -unicast to register with the WINS server. Such packets can be routed -and thus WINS allows name resolution to function across routed networks.</P -><P ->During the startup process an election will take place to create a -local master browser if one does not already exist. On each NetBIOS network -one machine will be elected to function as the domain master browser. This -domain browsing has nothing to do with MS security domain control. -Instead, the domain master browser serves the role of contacting each local -master browser (found by asking WINS or from LMHOSTS) and exchanging browse -list contents. This way every master browser will eventually obtain a complete -list of all machines that are on the network. Every 11-15 minutes an election -is held to determine which machine will be the master browser. By the nature of -the election criteria used, the machine with the highest uptime, or the -most senior protocol version, or other criteria, will win the election -as domain master browser.</P -><P ->Clients wishing to browse the network make use of this list, but also depend -on the availability of correct name resolution to the respective IP -address/addresses. </P -><P ->Any configuration that breaks name resolution and/or browsing intrinsics -will annoy users because they will have to put up with protracted -inability to use the network services.</P -><P ->Samba supports a feature that allows forced synchonisation -of browse lists across routed networks using the "remote -browse sync" parameter in the smb.conf file. This causes Samba -to contact the local master browser on a remote network and -to request browse list synchronisation. This effectively bridges -two networks that are separated by routers. The two remote -networks may use either broadcast based name resolution or WINS -based name resolution, but it should be noted that the "remote -browse sync" parameter provides browse list synchronisation - and -that is distinct from name to address resolution, in other -words, for cross subnet browsing to function correctly it is -essential that a name to address resolution mechanism be provided. -This mechanism could be via DNS, <TT -CLASS="FILENAME" ->/etc/hosts</TT ->, -and so on.</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN1653" -></A ->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 -challenege/response authentication model (a.k.a. NTLMv1) or -alone, or clear text strings for simple password based -authentication. It should be realized that with the SMB -protocol the password is passed over the network either -in plain text or encrypted, but not both in the same -authentication requets.</P -><P ->When encrypted passwords are used a password that has been -entered by the user is encrypted in two ways:</P -><P -></P -><UL -><LI -><P ->An MD4 hash of the UNICODE of the password - string. This is known as the NT hash. - </P -></LI -><LI -><P ->The password is converted to upper case, - and then padded or trucated to 14 bytes. This string is - then appended with 5 bytes of NULL characters and split to - form two 56 bit DES keys to encrypt a "magic" 8 byte value. - The resulting 16 bytes for the LanMan hash. - </P -></LI -></UL -><P ->You should refer to the <A -HREF="ENCRYPTION.html" -TARGET="_top" ->Password Encryption</A -> chapter in this HOWTO collection -for more details on the inner workings</P -><P ->MS Windows 95 pre-service pack 1, MS Windows NT versions 3.x -and version 4.0 pre-service pack 3 will use either mode of -password authentication. All versions of MS Windows that follow -these versions no longer support plain text passwords by default.</P -><P ->MS Windows clients have a habit of dropping network mappings that -have been idle for 10 minutes or longer. When the user attempts to -use the mapped drive connection that has been dropped, the client -re-establishes the connection using -a cached copy of the password.</P -><P ->When Microsoft changed the default password mode, they dropped support for -caching of the plain text password. This means that when the registry -parameter is changed to re-enable use of plain text passwords it appears to -work, but when a dropped mapping attempts to revalidate it will fail if -the remote authentication server does not support encrypted passwords. -This means that it is definitely not a good idea to re-enable plain text -password support in such clients.</P -><P ->The following parameters can be used to work around the -issue of Windows 9x client upper casing usernames and -password before transmitting them to the SMB server -when using clear text authentication.</P -><P -><PRE -CLASS="PROGRAMLISTING" -> <A -HREF="smb.conf.5.html#PASSWORDLEVEL" -TARGET="_top" ->passsword level</A -> = <TT -CLASS="REPLACEABLE" -><I ->integer</I -></TT -> - <A -HREF="smb.conf.5.html#USERNAMELEVEL" -TARGET="_top" ->username level</A -> = <TT -CLASS="REPLACEABLE" -><I ->integer</I -></TT -></PRE -></P -><P ->By default Samba will lower case the username before attempting -to lookup the user in the database of local system accounts. -Because UNIX usernames conventionally only contain lower case -character, the <TT -CLASS="PARAMETER" -><I ->username level</I -></TT -> parameter -is rarely even needed.</P -><P ->However, password on UNIX systems often make use of mixed case -characters. This means that in order for a user on a Windows 9x -client to connect to a Samba server using clear text authentication, -the <TT -CLASS="PARAMETER" -><I ->password level</I -></TT -> must be set to the maximum -number of upper case letter which <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->could</I -></SPAN -> appear -is a password. Note that is the server OS uses the traditional -DES version of crypt(), then a <TT -CLASS="PARAMETER" -><I ->password level</I -></TT -> -of 8 will result in case insensitive passwords as seen from Windows -users. This will also result in longer login times as Samba -hash to compute the permutations of the password string and -try them one by one until a match is located (or all combinations fail).</P -><P ->The best option to adopt is to enable support for encrypted passwords -where ever Samba is used. There are three configuration possibilities -for support of encrypted passwords:</P -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN1681" -></A ->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 -><P -><PRE -CLASS="PROGRAMLISTING" -> encrypt passwords = Yes - security = server - password server = "NetBIOS_name_of_PDC"</PRE -></P -><P ->There are two ways of identifying whether or not a username and -password pair was valid or not. One uses the reply information provided -as part of the authentication messaging process, the other uses -just and error code.</P -><P ->The down-side of this mode of configuration is the fact that -for security reasons Samba will send the password server a bogus -username and a bogus password and if the remote server fails to -reject the username and password pair then an alternative mode -of identification of validation is used. Where a site uses password -lock out after a certain number of failed authentication attempts -this will result in user lockouts.</P -><P ->Use of this mode of authentication does require there to be -a standard Unix account for the user, this account can be blocked -to prevent logons by other than MS Windows clients.</P -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN1689" -></A ->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 -><PRE -CLASS="PROGRAMLISTING" -> encrypt passwords = Yes - security = domain - workgroup = "name of NT domain" - password server = *</PRE -></P -><P ->The use of the "*" argument to "password server" will cause samba -to locate the domain controller in a way analogous to the way -this is done within MS Windows NT.</P -><P ->In order for this method to work the Samba server needs to join the -MS Windows NT security domain. This is done as follows:</P -><P -></P -><UL -><LI -><P ->On the MS Windows NT domain controller using - the Server Manager add a machine account for the Samba server. - </P -></LI -><LI -><P ->Next, on the Linux system execute: - <B -CLASS="COMMAND" ->smbpasswd -r PDC_NAME -j DOMAIN_NAME</B -> - </P -></LI -></UL -><P ->Use of this mode of authentication does require there to be -a standard Unix account for the user in order to assign -a uid once the account has been authenticated by the remote -Windows DC. This account can be blocked to prevent logons by -other than MS Windows clients by things such as setting an invalid -shell in the <TT -CLASS="FILENAME" ->/etc/passwd</TT -> entry.</P -><P ->An alternative to assigning UIDs to Windows users on a -Samba member server is presented in the <A -HREF="winbind.html" -TARGET="_top" ->Winbind Overview</A -> chapter in -this HOWTO collection.</P -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN1706" -></A ->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 -smbpasswd entry for the user. The Unix system account can be -locked if required as only the encrypted password will be -used for SMB client authentication.</P -><P ->This method involves addition of the following parameters to -the smb.conf file:</P -><P -><PRE -CLASS="PROGRAMLISTING" ->## please refer to the Samba PDC HOWTO chapter later in -## this collection for more details -[global] - encrypt passwords = Yes - security = user - domain logons = Yes - ; an OS level of 33 or more is recommended - os level = 33 - -[NETLOGON] - path = /somewhare/in/file/system - read only = yes</PRE -></P -><P ->in order for this method to work a Unix system account needs -to be created for each user, as well as for each MS Windows NT/2000 -machine. The following structure is required.</P -><DIV -CLASS="SECT3" -><HR><H4 -CLASS="SECT3" -><A -NAME="AEN1713" -></A ->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 -the procedure for creating an account.</P -><P -><PRE -CLASS="PROGRAMLISTING" -> # useradd -s /bin/bash -d /home/"userid" -m "userid" - # passwd "userid" - Enter Password: <pw> - - # smbpasswd -a "userid" - Enter Password: <pw></PRE -></P -></DIV -><DIV -CLASS="SECT3" -><HR><H4 -CLASS="SECT3" -><A -NAME="AEN1718" -></A ->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 -><P -><PRE -CLASS="PROGRAMLISTING" -> # useradd -s /bin/false -d /dev/null "machine_name"\$ - # passwd -l "machine_name"\$ - # smbpasswd -a -m "machine_name"</PRE -></P -></DIV -></DIV -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN1723" -></A ->9.6. Conclusions</H2 -><P ->Samba provides a flexible means to operate as...</P -><P -></P -><UL -><LI -><P ->A Stand-alone server - No special action is needed - other than to create user accounts. Stand-alone servers do NOT - provide network logon services, meaning that machines that use this - server do NOT perform a domain logon but instead make use only of - the MS Windows logon which is local to the MS Windows - workstation/server. - </P -></LI -><LI -><P ->An MS Windows NT 3.x/4.0 security domain member. - </P -></LI -><LI -><P ->An alternative to an MS Windows NT 3.x/4.0 - Domain Controller. - </P -></LI -></UL -></DIV -></DIV -><DIV -CLASS="CHAPTER" -><HR><H1 -><A -NAME="UNIX-PERMISSIONS" -></A ->Chapter 10. UNIX Permission Bits and Windows NT Access Control Lists</H1 -><DIV -CLASS="SECT1" -><H2 -CLASS="SECT1" -><A -NAME="AEN1744" -></A ->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 - NT clients to use their native security settings dialog box to - view and modify the underlying UNIX permissions.</P -><P ->Note that this ability is careful not to compromise - 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 -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN1748" -></A ->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 - drive letter or UNC path. When the menu pops-up, click - on the <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->Properties</I -></SPAN -> entry at the bottom of - the menu. This brings up the normal file properties dialog - box, but with Samba 2.0.4 this will have a new tab along the top - marked <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->Security</I -></SPAN ->. Click on this tab and you - will see three buttons, <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->Permissions</I -></SPAN ->, - <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->Auditing</I -></SPAN ->, and <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->Ownership</I -></SPAN ->. - The <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->Auditing</I -></SPAN -> button will cause either - an error message <SPAN -CLASS="ERRORNAME" ->A requested privilege is not held - by the client</SPAN -> to appear if the user is not the - NT Administrator, or a dialog which is intended to allow an - Administrator to add auditing requirements to a file if the - user is logged on as the NT Administrator. This dialog is - non-functional with a Samba share at this time, as the only - useful button, the <B -CLASS="COMMAND" ->Add</B -> button will not currently - allow a list of users to be seen.</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN1759" -></A ->10.3. Viewing file ownership</H2 -><P ->Clicking on the <B -CLASS="COMMAND" ->"Ownership"</B -> button - brings up a dialog box telling you who owns the given file. The - owner name will be of the form :</P -><P -><B -CLASS="COMMAND" ->"SERVER\user (Long name)"</B -></P -><P ->Where <TT -CLASS="REPLACEABLE" -><I ->SERVER</I -></TT -> is the NetBIOS name of - the Samba server, <TT -CLASS="REPLACEABLE" -><I ->user</I -></TT -> is the user name of - the UNIX user who owns the file, and <TT -CLASS="REPLACEABLE" -><I ->(Long name)</I -></TT -> - is the descriptive string identifying the user (normally found in the - GECOS field of the UNIX password database). Click on the <B -CLASS="COMMAND" ->Close - </B -> button to remove this dialog.</P -><P ->If the parameter <TT -CLASS="PARAMETER" -><I ->nt acl support</I -></TT -> - is set to <TT -CLASS="CONSTANT" ->false</TT -> then the file owner will - be shown as the NT user <B -CLASS="COMMAND" ->"Everyone"</B ->.</P -><P ->The <B -CLASS="COMMAND" ->Take Ownership</B -> button will not allow - you to change the ownership of this file to yourself (clicking on - it will display a dialog box complaining that the user you are - currently logged onto the NT client cannot be found). The reason - for this is that changing the ownership of a file is a privileged - operation in UNIX, available only to the <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->root</I -></SPAN -> - user. As clicking on this button causes NT to attempt to change - the ownership of a file to the current user logged into the NT - client this will not work with Samba at this time.</P -><P ->There is an NT chown command that will work with Samba - and allow a user with Administrator privilege connected - to a Samba 2.0.4 server as root to change the ownership of - files on both a local NTFS filesystem or remote mounted NTFS - or Samba drive. This is available as part of the <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->Seclib - </I -></SPAN -> NT security library written by Jeremy Allison of - the Samba Team, available from the main Samba ftp site.</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN1779" -></A ->10.4. Viewing file or directory permissions</H2 -><P ->The third button is the <B -CLASS="COMMAND" ->"Permissions"</B -> - button. Clicking on this brings up a dialog box that shows both - the permissions and the UNIX owner of the file or directory. - The owner is displayed in the form :</P -><P -><B -CLASS="COMMAND" ->"SERVER\user (Long name)"</B -></P -><P ->Where <TT -CLASS="REPLACEABLE" -><I ->SERVER</I -></TT -> is the NetBIOS name of - the Samba server, <TT -CLASS="REPLACEABLE" -><I ->user</I -></TT -> is the user name of - the UNIX user who owns the file, and <TT -CLASS="REPLACEABLE" -><I ->(Long name)</I -></TT -> - is the descriptive string identifying the user (normally found in the - GECOS field of the UNIX password database).</P -><P ->If the parameter <TT -CLASS="PARAMETER" -><I ->nt acl support</I -></TT -> - is set to <TT -CLASS="CONSTANT" ->false</TT -> then the file owner will - be shown as the NT user <B -CLASS="COMMAND" ->"Everyone"</B -> and the - permissions will be shown as NT "Full Control".</P -><P ->The permissions field is displayed differently for files - and directories, so I'll describe the way file permissions - are displayed first.</P -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN1794" -></A ->10.4.1. File Permissions</H3 -><P ->The standard UNIX user/group/world triple and - the corresponding "read", "write", "execute" permissions - triples are mapped by Samba into a three element NT ACL - with the 'r', 'w', and 'x' bits mapped into the corresponding - NT permissions. The UNIX world permissions are mapped into - the global NT group <B -CLASS="COMMAND" ->Everyone</B ->, followed - by the list of permissions allowed for UNIX world. The UNIX - owner and group permissions are displayed as an NT - <B -CLASS="COMMAND" ->user</B -> icon and an NT <B -CLASS="COMMAND" ->local - group</B -> icon respectively followed by the list - of permissions allowed for the UNIX user and group.</P -><P ->As many UNIX permission sets don't map into common - NT names such as <B -CLASS="COMMAND" ->"read"</B ->, <B -CLASS="COMMAND" -> "change"</B -> or <B -CLASS="COMMAND" ->"full control"</B -> then - usually the permissions will be prefixed by the words <B -CLASS="COMMAND" -> "Special Access"</B -> in the NT display list.</P -><P ->But what happens if the file has no permissions allowed - for a particular UNIX user group or world component ? In order - to allow "no permissions" to be seen and modified then Samba - overloads the NT <B -CLASS="COMMAND" ->"Take Ownership"</B -> ACL attribute - (which has no meaning in UNIX) and reports a component with - no permissions as having the NT <B -CLASS="COMMAND" ->"O"</B -> bit set. - This was chosen of course to make it look like a zero, meaning - zero permissions. More details on the decision behind this will - be given below.</P -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN1808" -></A ->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 - is the ACL set on the directory itself, this is usually displayed - in the first set of parentheses in the normal <B -CLASS="COMMAND" ->"RW"</B -> - NT style. This first set of permissions is created by Samba in - exactly the same way as normal file permissions are, described - above, and is displayed in the same way.</P -><P ->The second set of directory permissions has no real meaning - in the UNIX permissions world and represents the <B -CLASS="COMMAND" -> "inherited"</B -> permissions that any file created within - this directory would inherit.</P -><P ->Samba synthesises these inherited permissions for NT by - returning as an NT ACL the UNIX permission mode that a new file - created by Samba on this share would receive.</P -></DIV -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN1815" -></A ->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 - clicking the <B -CLASS="COMMAND" ->OK</B -> button. However, there are - limitations that a user needs to be aware of, and also interactions - with the standard Samba permission masks and mapping of DOS - attributes that need to also be taken into account.</P -><P ->If the parameter <TT -CLASS="PARAMETER" -><I ->nt acl support</I -></TT -> - is set to <TT -CLASS="CONSTANT" ->false</TT -> then any attempt to set - security permissions will fail with an <B -CLASS="COMMAND" ->"Access Denied" - </B -> message.</P -><P ->The first thing to note is that the <B -CLASS="COMMAND" ->"Add"</B -> - button will not return a list of users in Samba 2.0.4 (it will give - an error message of <B -CLASS="COMMAND" ->"The remote procedure call failed - and did not execute"</B ->). This means that you can only - manipulate the current user/group/world permissions listed in - the dialog box. This actually works quite well as these are the - only permissions that UNIX actually has.</P -><P ->If a permission triple (either user, group, or world) - is removed from the list of permissions in the NT dialog box, - then when the <B -CLASS="COMMAND" ->"OK"</B -> button is pressed it will - be applied as "no permissions" on the UNIX side. If you then - view the permissions again the "no permissions" entry will appear - as the NT <B -CLASS="COMMAND" ->"O"</B -> flag, as described above. This - allows you to add permissions back to a file or directory once - you have removed them from a triple component.</P -><P ->As UNIX supports only the "r", "w" and "x" bits of - an NT ACL then if other NT security attributes such as "Delete - access" are selected then they will be ignored when applied on - the Samba server.</P -><P ->When setting permissions on a directory the second - set of permissions (in the second set of parentheses) is - by default applied to all files within that directory. If this - is not what you want you must uncheck the <B -CLASS="COMMAND" ->"Replace - permissions on existing files"</B -> checkbox in the NT - dialog before clicking <B -CLASS="COMMAND" ->"OK"</B ->.</P -><P ->If you wish to remove all permissions from a - user/group/world component then you may either highlight the - component and click the <B -CLASS="COMMAND" ->"Remove"</B -> button, - or set the component to only have the special <B -CLASS="COMMAND" ->"Take - Ownership"</B -> permission (displayed as <B -CLASS="COMMAND" ->"O" - </B ->) highlighted.</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN1837" -></A ->10.6. Interaction with the standard Samba create mask - parameters</H2 -><P ->Note that with Samba 2.0.5 there are four new parameters - to control this interaction. These are :</P -><P -><TT -CLASS="PARAMETER" -><I ->security mask</I -></TT -></P -><P -><TT -CLASS="PARAMETER" -><I ->force security mode</I -></TT -></P -><P -><TT -CLASS="PARAMETER" -><I ->directory security mask</I -></TT -></P -><P -><TT -CLASS="PARAMETER" -><I ->force directory security mode</I -></TT -></P -><P ->Once a user clicks <B -CLASS="COMMAND" ->"OK"</B -> to apply the - permissions Samba maps the given permissions into a user/group/world - r/w/x triple set, and then will check the changed permissions for a - file against the bits set in the <A -HREF="smb.conf.5.html#SECURITYMASK" -TARGET="_top" -> - <TT -CLASS="PARAMETER" -><I ->security mask</I -></TT -></A -> parameter. Any bits that - were changed that are not set to '1' in this parameter are left alone - in the file permissions.</P -><P ->Essentially, zero bits in the <TT -CLASS="PARAMETER" -><I ->security mask</I -></TT -> - mask may be treated as a set of bits the user is <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->not</I -></SPAN -> - allowed to change, and one bits are those the user is allowed to change. - </P -><P ->If not set explicitly this parameter is set to the same value as - the <A -HREF="smb.conf.5.html#CREATEMASK" -TARGET="_top" -><TT -CLASS="PARAMETER" -><I ->create mask - </I -></TT -></A -> parameter to provide compatibility with Samba 2.0.4 - where this permission change facility was introduced. To allow a user to - modify all the user/group/world permissions on a file, set this parameter - to 0777.</P -><P ->Next Samba checks the changed permissions for a file against - the bits set in the <A -HREF="smb.conf.5.html#FORCESECURITYMODE" -TARGET="_top" -> <TT -CLASS="PARAMETER" -><I ->force security mode</I -></TT -></A -> parameter. Any bits - that were changed that correspond to bits set to '1' in this parameter - are forced to be set.</P -><P ->Essentially, bits set in the <TT -CLASS="PARAMETER" -><I ->force security mode - </I -></TT -> parameter may be treated as a set of bits that, when - modifying security on a file, the user has always set to be 'on'.</P -><P ->If not set explicitly this parameter is set to the same value - as the <A -HREF="smb.conf.5.html#FORCECREATEMODE" -TARGET="_top" -><TT -CLASS="PARAMETER" -><I ->force - create mode</I -></TT -></A -> parameter to provide compatibility - with Samba 2.0.4 where the permission change facility was introduced. - To allow a user to modify all the user/group/world permissions on a file - with no restrictions set this parameter to 000.</P -><P ->The <TT -CLASS="PARAMETER" -><I ->security mask</I -></TT -> and <TT -CLASS="PARAMETER" -><I ->force - security mode</I -></TT -> parameters are applied to the change - request in that order.</P -><P ->For a directory Samba will perform the same operations as - described above for a file except using the parameter <TT -CLASS="PARAMETER" -><I -> directory security mask</I -></TT -> instead of <TT -CLASS="PARAMETER" -><I ->security - mask</I -></TT ->, and <TT -CLASS="PARAMETER" -><I ->force directory security mode - </I -></TT -> parameter instead of <TT -CLASS="PARAMETER" -><I ->force security mode - </I -></TT ->.</P -><P ->The <TT -CLASS="PARAMETER" -><I ->directory security mask</I -></TT -> parameter - by default is set to the same value as the <TT -CLASS="PARAMETER" -><I ->directory mask - </I -></TT -> parameter and the <TT -CLASS="PARAMETER" -><I ->force directory security - mode</I -></TT -> parameter by default is set to the same value as - the <TT -CLASS="PARAMETER" -><I ->force directory mode</I -></TT -> parameter to provide - compatibility with Samba 2.0.4 where the permission change facility - was introduced.</P -><P ->In this way Samba enforces the permission restrictions that - an administrator can set on a Samba share, whilst still allowing users - to modify the permission bits within that restriction.</P -><P ->If you want to set up a share that allows users full control - in modifying the permission bits on their files and directories and - doesn't force any particular bits to be set 'on', then set the following - parameters in the <A -HREF="smb.conf.5.html" -TARGET="_top" -><TT -CLASS="FILENAME" ->smb.conf(5) - </TT -></A -> file in that share specific section :</P -><P -><TT -CLASS="PARAMETER" -><I ->security mask = 0777</I -></TT -></P -><P -><TT -CLASS="PARAMETER" -><I ->force security mode = 0</I -></TT -></P -><P -><TT -CLASS="PARAMETER" -><I ->directory security mask = 0777</I -></TT -></P -><P -><TT -CLASS="PARAMETER" -><I ->force directory security mode = 0</I -></TT -></P -><P ->As described, in Samba 2.0.4 the parameters :</P -><P -><TT -CLASS="PARAMETER" -><I ->create mask</I -></TT -></P -><P -><TT -CLASS="PARAMETER" -><I ->force create mode</I -></TT -></P -><P -><TT -CLASS="PARAMETER" -><I ->directory mask</I -></TT -></P -><P -><TT -CLASS="PARAMETER" -><I ->force directory mode</I -></TT -></P -><P ->were used instead of the parameters discussed here.</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN1901" -></A ->10.7. Interaction with the standard Samba file attribute - mapping</H2 -><P ->Samba maps some of the DOS attribute bits (such as "read - only") into the UNIX permissions of a file. This means there can - be a conflict between the permission bits set via the security - dialog and the permission bits set by the file attribute mapping. - </P -><P ->One way this can show up is if a file has no UNIX read access - for the owner it will show up as "read only" in the standard - file attributes tabbed dialog. Unfortunately this dialog is - the same one that contains the security info in another tab.</P -><P ->What this can mean is that if the owner changes the permissions - to allow themselves read access using the security dialog, clicks - <B -CLASS="COMMAND" ->"OK"</B -> to get back to the standard attributes tab - dialog, and then clicks <B -CLASS="COMMAND" ->"OK"</B -> on that dialog, then - NT will set the file permissions back to read-only (as that is what - the attributes still say in the dialog). This means that after setting - permissions and clicking <B -CLASS="COMMAND" ->"OK"</B -> to get back to the - attributes dialog you should always hit <B -CLASS="COMMAND" ->"Cancel"</B -> - rather than <B -CLASS="COMMAND" ->"OK"</B -> to ensure that your changes - are not overridden.</P -></DIV -></DIV -><DIV -CLASS="CHAPTER" -><HR><H1 -><A -NAME="PAM" -></A ->Chapter 11. Configuring PAM for distributed but centrally -managed authentication</H1 -><DIV -CLASS="SECT1" -><H2 -CLASS="SECT1" -><A -NAME="AEN1922" -></A ->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 -Modules (PAM) facility to provide all authentication, -authorization and resource control services. Prior to the -introduction of PAM, a decision to use an alternative to -the system password database (<TT -CLASS="FILENAME" ->/etc/passwd</TT ->) -would require the provision of alternatives for all programs that provide -security services. Such a choice would involve provision of -alternatives to such programs as: <B -CLASS="COMMAND" ->login</B ->, -<B -CLASS="COMMAND" ->passwd</B ->, <B -CLASS="COMMAND" ->chown</B ->, etc.</P -><P ->PAM provides a mechanism that disconnects these security programs -from the underlying authentication/authorization infrastructure. -PAM is configured either through one file <TT -CLASS="FILENAME" ->/etc/pam.conf</TT -> (Solaris), -or by editing individual files that are located in <TT -CLASS="FILENAME" ->/etc/pam.d</TT ->.</P -><P ->The following is an example <TT -CLASS="FILENAME" ->/etc/pam.d/login</TT -> configuration file. -This example had all options been uncommented is probably not usable -as it stacks many conditions before allowing successful completion -of the login process. Essentially all conditions can be disabled -by commenting them out except the calls to <TT -CLASS="FILENAME" ->pam_pwdb.so</TT ->.</P -><P -><PRE -CLASS="PROGRAMLISTING" ->#%PAM-1.0 -# The PAM configuration file for the `login' service -# -auth required pam_securetty.so -auth required pam_nologin.so -# auth required pam_dialup.so -# auth optional pam_mail.so -auth required pam_pwdb.so shadow md5 -# account requisite pam_time.so -account required pam_pwdb.so -session required pam_pwdb.so -# session optional pam_lastlog.so -# password required pam_cracklib.so retry=3 -password required pam_pwdb.so shadow md5</PRE -></P -><P ->PAM allows use of replacable modules. Those available on a -sample system include:</P -><P -><PRE -CLASS="PROGRAMLISTING" ->$ /bin/ls /lib/security -pam_access.so pam_ftp.so pam_limits.so -pam_ncp_auth.so pam_rhosts_auth.so pam_stress.so -pam_cracklib.so pam_group.so pam_listfile.so -pam_nologin.so pam_rootok.so pam_tally.so -pam_deny.so pam_issue.so pam_mail.so -pam_permit.so pam_securetty.so pam_time.so -pam_dialup.so pam_lastlog.so pam_mkhomedir.so -pam_pwdb.so pam_shells.so pam_unix.so -pam_env.so pam_ldap.so pam_motd.so -pam_radius.so pam_smbpass.so pam_unix_acct.so -pam_wheel.so pam_unix_auth.so pam_unix_passwd.so -pam_userdb.so pam_warn.so pam_unix_session.so</PRE -></P -><P ->The following example for the login program replaces the use of -the <TT -CLASS="FILENAME" ->pam_pwdb.so</TT -> module which uses the system -password database (<TT -CLASS="FILENAME" ->/etc/passwd</TT ->, -<TT -CLASS="FILENAME" ->/etc/shadow</TT ->, <TT -CLASS="FILENAME" ->/etc/group</TT ->) with -the module <TT -CLASS="FILENAME" ->pam_smbpass.so</TT -> which uses the Samba -database which contains the Microsoft MD4 encrypted password -hashes. This database is stored in either -<TT -CLASS="FILENAME" ->/usr/local/samba/private/smbpasswd</TT ->, -<TT -CLASS="FILENAME" ->/etc/samba/smbpasswd</TT ->, or in -<TT -CLASS="FILENAME" ->/etc/samba.d/smbpasswd</TT ->, depending on the -Samba implementation for your Unix/Linux system. The -<TT -CLASS="FILENAME" ->pam_smbpass.so</TT -> module is provided by -Samba version 2.2.1 or later. It can be compiled by specifying the -<B -CLASS="COMMAND" ->--with-pam_smbpass</B -> options when running Samba's -<TT -CLASS="FILENAME" ->configure</TT -> script. For more information -on the <TT -CLASS="FILENAME" ->pam_smbpass</TT -> module, see the documentation -in the <TT -CLASS="FILENAME" ->source/pam_smbpass</TT -> directory of the Samba -source distribution.</P -><P -><PRE -CLASS="PROGRAMLISTING" ->#%PAM-1.0 -# The PAM configuration file for the `login' service -# -auth required pam_smbpass.so nodelay -account required pam_smbpass.so nodelay -session required pam_smbpass.so nodelay -password required pam_smbpass.so nodelay</PRE -></P -><P ->The following is the PAM configuration file for a particular -Linux system. The default condition uses <TT -CLASS="FILENAME" ->pam_pwdb.so</TT ->.</P -><P -><PRE -CLASS="PROGRAMLISTING" ->#%PAM-1.0 -# The PAM configuration file for the `samba' service -# -auth required /lib/security/pam_pwdb.so nullok nodelay shadow audit -account required /lib/security/pam_pwdb.so audit nodelay -session required /lib/security/pam_pwdb.so nodelay -password required /lib/security/pam_pwdb.so shadow md5</PRE -></P -><P ->In the following example the decision has been made to use the -smbpasswd database even for basic samba authentication. Such a -decision could also be made for the passwd program and would -thus allow the smbpasswd passwords to be changed using the passwd -program.</P -><P -><PRE -CLASS="PROGRAMLISTING" ->#%PAM-1.0 -# The PAM configuration file for the `samba' service -# -auth required /lib/security/pam_smbpass.so nodelay -account required /lib/security/pam_pwdb.so audit nodelay -session required /lib/security/pam_pwdb.so nodelay -password required /lib/security/pam_smbpass.so nodelay smbconf=/etc/samba.d/smb.conf</PRE -></P -><P ->Note: PAM allows stacking of authentication mechanisms. It is -also possible to pass information obtained within one PAM module through -to the next module in the PAM stack. Please refer to the documentation for -your particular system implementation for details regarding the specific -capabilities of PAM in this environment. Some Linux implmentations also -provide the <TT -CLASS="FILENAME" ->pam_stack.so</TT -> module that allows all -authentication to be configured in a single central file. The -<TT -CLASS="FILENAME" ->pam_stack.so</TT -> method has some very devoted followers -on the basis that it allows for easier administration. As with all issues in -life though, every decision makes trade-offs, so you may want examine the -PAM documentation for further helpful information.</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN1966" -></A ->11.2. Distributed Authentication</H2 -><P ->The astute administrator will realize from this that the -combination of <TT -CLASS="FILENAME" ->pam_smbpass.so</TT ->, -<B -CLASS="COMMAND" ->winbindd</B ->, and <B -CLASS="COMMAND" ->rsync</B -> (see -<A -HREF="http://rsync.samba.org/" -TARGET="_top" ->http://rsync.samba.org/</A ->) -will allow the establishment of a centrally managed, distributed -user/password database that can also be used by all -PAM (eg: Linux) aware programs and applications. This arrangement -can have particularly potent advantages compared with the -use of Microsoft Active Directory Service (ADS) in so far as -reduction of wide area network authentication traffic.</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN1973" -></A ->11.3. PAM Configuration in smb.conf</H2 -><P ->There is an option in smb.conf called <A -HREF="smb.conf.5.html#OBEYPAMRESTRICTIONS" -TARGET="_top" ->obey pam restrictions</A ->. -The following is from the on-line help for this option in SWAT;</P -><P ->When Samba 2.2 is configure to enable PAM support (i.e. -<TT -CLASS="CONSTANT" ->--with-pam</TT ->), this parameter will -control whether or not Samba should obey PAM's account -and session management directives. The default behavior -is to use PAM for clear text authentication only and to -ignore any account or session management. Note that Samba always -ignores PAM for authentication in the case of -<A -HREF="smb.conf.5.html#ENCRYPTPASSWORDS" -TARGET="_top" ->encrypt passwords = yes</A ->. -The reason is that PAM modules cannot support the challenge/response -authentication mechanism needed in the presence of SMB -password encryption. </P -><P ->Default: <B -CLASS="COMMAND" ->obey pam restrictions = no</B -></P -></DIV -></DIV -><DIV -CLASS="CHAPTER" -><HR><H1 -><A -NAME="MSDFS" -></A ->Chapter 12. Hosting a Microsoft Distributed File System tree on Samba</H1 -><DIV -CLASS="SECT1" -><H2 -CLASS="SECT1" -><A -NAME="AEN1993" -></A ->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 - see from the actual physical locations of these resources on the - network. It allows for higher availability, smoother storage expansion, - load balancing etc. For more information about Dfs, refer to <A -HREF="http://www.microsoft.com/NTServer/nts/downloads/winfeatures/NTSDistrFile/AdminGuide.asp" -TARGET="_top" -> Microsoft documentation</A ->. </P -><P ->This document explains how to host a Dfs tree on a Unix - machine (for Dfs-aware clients to browse) using Samba.</P -><P ->To enable SMB-based DFS for Samba, configure it with the - <TT -CLASS="PARAMETER" -><I ->--with-msdfs</I -></TT -> option. Once built, a - Samba server can be made a Dfs server by setting the global - boolean <A -HREF="smb.conf.5.html#HOSTMSDFS" -TARGET="_top" -><TT -CLASS="PARAMETER" -><I -> host msdfs</I -></TT -></A -> parameter in the <TT -CLASS="FILENAME" ->smb.conf - </TT -> file. You designate a share as a Dfs root using the share - level boolean <A -HREF="smb.conf.5.html#MSDFSROOT" -TARGET="_top" -><TT -CLASS="PARAMETER" -><I -> msdfs root</I -></TT -></A -> parameter. A Dfs root directory on - Samba hosts Dfs links in the form of symbolic links that point - to other servers. For example, a symbolic link - <TT -CLASS="FILENAME" ->junction->msdfs:storage1\share1</TT -> in - the share directory acts as the Dfs junction. When Dfs-aware - clients attempt to access the junction link, they are redirected - to the storage location (in this case, \\storage1\share1).</P -><P ->Dfs trees on Samba work with all Dfs-aware clients ranging - from Windows 95 to 2000.</P -><P ->Here's an example of setting up a Dfs tree on a Samba - server.</P -><P -><PRE -CLASS="PROGRAMLISTING" -># The smb.conf file: -[global] - netbios name = SAMBA - host msdfs = yes - -[dfs] - path = /export/dfsroot - msdfs root = yes - </PRE -></P -><P ->In the /export/dfsroot directory we set up our dfs links to - other servers on the network.</P -><P -><TT -CLASS="PROMPT" ->root# </TT -><TT -CLASS="USERINPUT" -><B ->cd /export/dfsroot</B -></TT -></P -><P -><TT -CLASS="PROMPT" ->root# </TT -><TT -CLASS="USERINPUT" -><B ->chown root /export/dfsroot</B -></TT -></P -><P -><TT -CLASS="PROMPT" ->root# </TT -><TT -CLASS="USERINPUT" -><B ->chmod 755 /export/dfsroot</B -></TT -></P -><P -><TT -CLASS="PROMPT" ->root# </TT -><TT -CLASS="USERINPUT" -><B ->ln -s msdfs:storageA\\shareA linka</B -></TT -></P -><P -><TT -CLASS="PROMPT" ->root# </TT -><TT -CLASS="USERINPUT" -><B ->ln -s msdfs:serverB\\share,serverC\\share linkb</B -></TT -></P -><P ->You should set up the permissions and ownership of - the directory acting as the Dfs root such that only designated - users can create, delete or modify the msdfs links. Also note - that symlink names should be all lowercase. This limitation exists - to have Samba avoid trying all the case combinations to get at - the link name. Finally set up the symbolic links to point to the - network shares you want, and start Samba.</P -><P ->Users on Dfs-aware clients can now browse the Dfs tree - on the Samba server at \\samba\dfs. Accessing - links linka or linkb (which appear as directories to the client) - takes users directly to the appropriate shares on the network.</P -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN2028" -></A ->12.1.1. Notes</H3 -><P -></P -><UL -><LI -><P ->Windows clients need to be rebooted - if a previously mounted non-dfs share is made a dfs - root or vice versa. A better way is to introduce a - new share and make it the dfs root.</P -></LI -><LI -><P ->Currently there's a restriction that msdfs - symlink names should all be lowercase.</P -></LI -><LI -><P ->For security purposes, the directory - acting as the root of the Dfs tree should have ownership - and permissions set so that only designated users can - modify the symbolic links in the directory.</P -></LI -></UL -></DIV -></DIV -></DIV -><DIV -CLASS="CHAPTER" -><HR><H1 -><A -NAME="PRINTING" -></A ->Chapter 13. Printing Support</H1 -><DIV -CLASS="SECT1" -><H2 -CLASS="SECT1" -><A -NAME="AEN2054" -></A ->13.1. Introduction</H2 -><P ->Beginning with the 2.2.0 release, Samba supports -the native Windows NT printing mechanisms implemented via -MS-RPC (i.e. the SPOOLSS named pipe). Previous versions of -Samba only supported LanMan printing calls.</P -><P ->The additional functionality provided by the new -SPOOLSS support includes:</P -><P -></P -><UL -><LI -><P ->Support for downloading printer driver - files to Windows 95/98/NT/2000 clients upon demand. - </P -></LI -><LI -><P ->Uploading of printer drivers via the - Windows NT Add Printer Wizard (APW) or the - Imprints tool set (refer to <A -HREF="http://imprints.sourceforge.net" -TARGET="_top" ->http://imprints.sourceforge.net</A ->). - </P -></LI -><LI -><P ->Support for the native MS-RPC printing - calls such as StartDocPrinter, EnumJobs(), etc... (See - the MSDN documentation at <A -HREF="http://msdn.microsoft.com/" -TARGET="_top" ->http://msdn.microsoft.com/</A -> - for more information on the Win32 printing API) - </P -></LI -><LI -><P ->Support for NT Access Control Lists (ACL) - on printer objects</P -></LI -><LI -><P ->Improved support for printer queue manipulation - through the use of an internal databases for spooled job - information</P -></LI -></UL -><P ->There has been some initial confusion about what all this means -and whether or not it is a requirement for printer drivers to be -installed on a Samba host in order to support printing from Windows -clients. As a side note, Samba does not use these drivers in any way to process -spooled files. They are utilized entirely by the clients.</P -><P ->The following MS KB article, may be of some help if you are dealing with -Windows 2000 clients: <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->How to Add Printers with No User -Interaction in Windows 2000</I -></SPAN -></P -><P -><A -HREF="http://support.microsoft.com/support/kb/articles/Q189/1/05.ASP" -TARGET="_top" ->http://support.microsoft.com/support/kb/articles/Q189/1/05.ASP</A -></P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN2076" -></A ->13.2. Configuration</H2 -><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 -><TH -ALIGN="LEFT" -VALIGN="CENTER" -><B ->[print$] vs. [printer$]</B -></TH -></TR -><TR -><TD -> </TD -><TD -ALIGN="LEFT" -VALIGN="TOP" -><P ->Previous versions of Samba recommended using a share named [printer$]. -This name was taken from the printer$ service created by Windows 9x -clients when a printer was shared. Windows 9x printer servers always have -a printer$ service which provides read-only access via no -password in order to support printer driver downloads.</P -><P ->However, the initial implementation allowed for a -parameter named <TT -CLASS="PARAMETER" -><I ->printer driver location</I -></TT -> -to be used on a per share basis to specify the location of -the driver files associated with that printer. Another -parameter named <TT -CLASS="PARAMETER" -><I ->printer driver</I -></TT -> provided -a means of defining the printer driver name to be sent to -the client.</P -></TD -></TR -></TABLE -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN2084" -></A ->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$]. -The name of this share is hard coded in Samba's internals so -the name is very important (print$ is the service used by -Windows NT print servers to provide support for printer driver -download).</P -><P ->You should modify the server's smb.conf file to add the global -parameters and to create the -following file share (of course, some of the parameter values, -such as 'path' are arbitrary and should be replaced with -appropriate values for your site):</P -><P -><PRE -CLASS="PROGRAMLISTING" ->[global] - ; members of the ntadmin group should be able - ; to add drivers and set printer properties - ; root is implicitly a 'printer admin' - printer admin = @ntadmin - -[print$] - path = /usr/local/samba/printers - guest ok = yes - browseable = yes - read only = yes - ; since this share is configured as read only, then we need - ; a 'write list'. Check the file system permissions to make - ; sure this account can copy files to the share. If this - ; is setup to a non-root account, then it should also exist - ; as a 'printer admin' - write list = @ntadmin,root</PRE -></P -><P ->The <A -HREF="smb.conf.5.html#WRITELIST" -TARGET="_top" -><TT -CLASS="PARAMETER" -><I ->write list</I -></TT -></A -> is used to allow administrative -level user accounts to have write access in order to update files -on the share. See the <A -HREF="smb.conf.5.html" -TARGET="_top" ->smb.conf(5) -man page</A -> for more information on configuring file shares.</P -><P ->The requirement for <A -HREF="smb.conf.5.html#GUESTOK" -TARGET="_top" -><B -CLASS="COMMAND" ->guest -ok = yes</B -></A -> depends upon how your -site is configured. If users will be guaranteed to have -an account on the Samba host, then this is a non-issue.</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 -><TH -ALIGN="LEFT" -VALIGN="CENTER" -><B ->Author's Note</B -></TH -></TR -><TR -><TD -> </TD -><TD -ALIGN="LEFT" -VALIGN="TOP" -><P ->The non-issue is that if all your Windows NT users are guaranteed to be -authenticated by the Samba server (such as a domain member server and the NT -user has already been validated by the Domain Controller in -order to logon to the Windows NT console), then guest access -is not necessary. Of course, in a workgroup environment where -you just want to be able to print without worrying about -silly accounts and security, then configure the share for -guest access. You'll probably want to add <A -HREF="smb.conf.5.html#MAPTOGUEST" -TARGET="_top" -><B -CLASS="COMMAND" ->map to guest = Bad User</B -></A -> in the [global] section as well. Make sure -you understand what this parameter does before using it -though. --jerry</P -></TD -></TR -></TABLE -></DIV -><P ->In order for a Windows NT print server to support -the downloading of driver files by multiple client architectures, -it must create subdirectories within the [print$] service -which correspond to each of the supported client architectures. -Samba follows this model as well.</P -><P ->Next create the directory tree below the [print$] share -for each architecture you wish to support.</P -><P -><PRE -CLASS="PROGRAMLISTING" ->[print$]----- - |-W32X86 ; "Windows NT x86" - |-WIN40 ; "Windows 95/98" - |-W32ALPHA ; "Windows NT Alpha_AXP" - |-W32MIPS ; "Windows NT R4000" - |-W32PPC ; "Windows NT PowerPC"</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 -><TH -ALIGN="LEFT" -VALIGN="CENTER" -><B ->ATTENTION! REQUIRED PERMISSIONS</B -></TH -></TR -><TR -><TD -> </TD -><TD -ALIGN="LEFT" -VALIGN="TOP" -><P ->In order to currently add a new driver to you Samba host, -one of two conditions must hold true:</P -><P -></P -><UL -><LI -><P ->The account used to connect to the Samba host - must have a uid of 0 (i.e. a root account)</P -></LI -><LI -><P ->The account used to connect to the Samba host - must be a member of the <A -HREF="smb.conf.5.html#PRINTERADMIN" -TARGET="_top" -><TT -CLASS="PARAMETER" -><I ->printer - admin</I -></TT -></A -> list.</P -></LI -></UL -><P ->Of course, the connected account must still possess access -to add files to the subdirectories beneath [print$]. Remember -that all file shares are set to 'read only' by default.</P -></TD -></TR -></TABLE -></DIV -><P ->Once you have created the required [print$] service and -associated subdirectories, simply log onto the Samba server using -a root (or <TT -CLASS="PARAMETER" -><I ->printer admin</I -></TT ->) account -from a Windows NT 4.0/2k client. Open "Network Neighbourhood" or -"My Network Places" and browse for the Samba host. Once you have located -the server, navigate to the "Printers..." folder. -You should see an initial listing of printers -that matches the printer shares defined on your Samba host.</P -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN2119" -></A ->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 -to them. This defaults to a NULL string to allow the use -of the local Add Printer Wizard on NT/2000 clients. -Attempting to view the printer properties for a printer -which has this default driver assigned will result in -the error message:</P -><P -><SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->Device settings cannot be displayed. The driver -for the specified printer is not installed, only spooler -properties will be displayed. Do you want to install the -driver now?</I -></SPAN -></P -><P ->Click "No" in the error dialog and you will be presented with -the printer properties window. The way to assign a driver to a -printer is to either</P -><P -></P -><UL -><LI -><P ->Use the "New Driver..." button to install - a new printer driver, or</P -></LI -><LI -><P ->Select a driver from the popup list of - installed drivers. Initially this list will be empty.</P -></LI -></UL -><P ->If you wish to install printer drivers for client -operating systems other than "Windows NT x86", you will need -to use the "Sharing" tab of the printer properties dialog.</P -><P ->Assuming you have connected with a root account, you -will also be able modify other printer properties such as -ACLs and device settings using this dialog box.</P -><P ->A few closing comments for this section, it is possible -on a Windows NT print server to have printers -listed in the Printers folder which are not shared. Samba does -not make this distinction. By definition, the only printers of -which Samba is aware are those which are specified as shares in -<TT -CLASS="FILENAME" ->smb.conf</TT ->.</P -><P ->Another interesting side note is that Windows NT clients do -not use the SMB printer share, but rather can print directly -to any printer on another Windows NT host using MS-RPC. This -of course assumes that the printing client has the necessary -privileges on the remote host serving the printer. The default -permissions assigned by Windows NT to a printer gives the "Print" -permissions to the "Everyone" well-known group.</P -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN2135" -></A ->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 -100's of printers. Using the Windows NT APW is somewhat -awkward to say the list. If more than one printer are using the -same driver, the <A -HREF="rpcclient.1.html" -TARGET="_top" -><B -CLASS="COMMAND" ->rpcclient's -setdriver command</B -></A -> can be used to set the driver -associated with an installed driver. The following is example -of how this could be accomplished:</P -><P -><PRE -CLASS="PROGRAMLISTING" -> -<TT -CLASS="PROMPT" ->$ </TT ->rpcclient pogo -U root%secret -c "enumdrivers" -Domain=[NARNIA] OS=[Unix] Server=[Samba 2.2.0-alpha3] - -[Windows NT x86] -Printer Driver Info 1: - Driver Name: [HP LaserJet 4000 Series PS] - -Printer Driver Info 1: - Driver Name: [HP LaserJet 2100 Series PS] - -Printer Driver Info 1: - Driver Name: [HP LaserJet 4Si/4SiMX PS] - -<TT -CLASS="PROMPT" ->$ </TT ->rpcclient pogo -U root%secret -c "enumprinters" -Domain=[NARNIA] OS=[Unix] Server=[Samba 2.2.0-alpha3] - flags:[0x800000] - name:[\\POGO\hp-print] - description:[POGO\\POGO\hp-print,NO DRIVER AVAILABLE FOR THIS PRINTER,] - comment:[] - -<TT -CLASS="PROMPT" ->$ </TT ->rpcclient pogo -U root%secret \ -<TT -CLASS="PROMPT" ->> </TT -> -c "setdriver hp-print \"HP LaserJet 4000 Series PS\"" -Domain=[NARNIA] OS=[Unix] Server=[Samba 2.2.0-alpha3] -Successfully set hp-print to driver HP LaserJet 4000 Series PS.</PRE -></P -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN2146" -></A ->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" ->smb.conf</TT -> -in the "Printers..." folder. Also existing in this folder is the Windows NT -Add Printer Wizard icon. The APW will be show only if</P -><P -></P -><UL -><LI -><P ->The connected user is able to successfully - execute an OpenPrinterEx(\\server) with administrative - privileges (i.e. root or <TT -CLASS="PARAMETER" -><I ->printer admin</I -></TT ->). - </P -></LI -><LI -><P -><A -HREF="smb.conf.5.html#SHOWADDPRINTERWIZARD" -TARGET="_top" -><TT -CLASS="PARAMETER" -><I ->show - add printer wizard = yes</I -></TT -></A -> (the default). - </P -></LI -></UL -><P ->In order to be able to use the APW to successfully add a printer to a Samba -server, the <A -HREF="smb.conf.5.html#ADDPRINTERCOMMAND" -TARGET="_top" -><TT -CLASS="PARAMETER" -><I ->add -printer command</I -></TT -></A -> must have a defined value. The program -hook must successfully add the printer to the system (i.e. -<TT -CLASS="FILENAME" ->/etc/printcap</TT -> or appropriate files) and -<TT -CLASS="FILENAME" ->smb.conf</TT -> if necessary.</P -><P ->When using the APW from a client, if the named printer share does -not exist, <B -CLASS="COMMAND" ->smbd</B -> will execute the <TT -CLASS="PARAMETER" -><I ->add printer -command</I -></TT -> and reparse to the <TT -CLASS="FILENAME" ->smb.conf</TT -> -to attempt to locate the new printer share. If the share is still not defined, -an error of "Access Denied" is returned to the client. Note that the -<TT -CLASS="PARAMETER" -><I ->add printer program</I -></TT -> is executed under the context -of the connected user, not necessarily a root account.</P -><P ->There is a complementary <A -HREF="smb.conf.5.html#DELETEPRINTERCOMMAND" -TARGET="_top" -><TT -CLASS="PARAMETER" -><I ->delete -printer command</I -></TT -></A -> for removing entries from the "Printers..." -folder.</P -><P ->The following is an example <A -HREF="smb.conf.5.html#ADDPRINTERCOMMAN" -TARGET="_top" -><TT -CLASS="PARAMETER" -><I ->add printer command</I -></TT -></A -> script. It adds the appropriate entries to <TT -CLASS="FILENAME" ->/etc/printcap.local</TT -> (change that to what you need) and returns a line of 'Done' which is needed for the whole process to work.</P -><PRE -CLASS="PROGRAMLISTING" ->#!/bin/sh - -# Script to insert a new printer entry into printcap.local -# -# $1, printer name, used as the descriptive name -# $2, share name, used as the printer name for Linux -# $3, port name -# $4, driver name -# $5, location, used for the device file of the printer -# $6, win9x location - -# -# Make sure we use the location that RedHat uses for local printer defs -PRINTCAP=/etc/printcap.local -DATE=`date +%Y%m%d-%H%M%S` -LP=lp -RESTART="service lpd restart" - -# Keep a copy -cp $PRINTCAP $PRINTCAP.$DATE -# Add the printer to $PRINTCAP -echo "" >> $PRINTCAP -echo "$2|$1:\\" >> $PRINTCAP -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 - -mkdir /var/spool/lpd/$2 -chmod 700 /var/spool/lpd/$2 -chown $LP /var/spool/lpd/$2 -#echo $1 >> "/usr/local/samba/var/print/$5.prn" -#echo $2 >> "/usr/local/samba/var/print/$5.prn" -#echo $3 >> "/usr/local/samba/var/print/$5.prn" -#echo $4 >> "/usr/local/samba/var/print/$5.prn" -#echo $5 >> "/usr/local/samba/var/print/$5.prn" -#echo $6 >> "/usr/local/samba/var/print/$5.prn" -$RESTART >> "/usr/local/samba/var/print/$5.prn" -# Not sure if this is needed -touch /usr/local/samba/lib/smb.conf -# -# You need to return a value, but I am not sure what it means. -# -echo "Done" -exit 0</PRE -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN2176" -></A ->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 -concept of ports associated with a printer. By default, only one printer port, -named "Samba Printer Port", exists on a system. Samba does not really a port in -order to print, rather it is a requirement of Windows clients. </P -><P ->Note that Samba does not support the concept of "Printer Pooling" internally -either. This is when a logical printer is assigned to multiple ports as -a form of load balancing or fail over.</P -><P ->If you require that multiple ports be defined for some reason, -<TT -CLASS="FILENAME" ->smb.conf</TT -> possesses a <A -HREF="smb.conf.5.html#ENUMPORTSCOMMAND" -TARGET="_top" -><TT -CLASS="PARAMETER" -><I ->enumports -command</I -></TT -></A -> which can be used to define an external program -that generates a listing of ports on a system.</P -></DIV -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN2184" -></A ->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 - refer to the Imprints web site at <A -HREF="http://imprints.sourceforge.net/" -TARGET="_top" -> http://imprints.sourceforge.net/</A -> as well as the documentation - included with the imprints source distribution. This section will - only provide a brief introduction to the features of Imprints.</P -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN2188" -></A ->13.3.1. What is Imprints?</H3 -><P ->Imprints is a collection of tools for supporting the goals - of</P -><P -></P -><UL -><LI -><P ->Providing a central repository information - regarding Windows NT and 95/98 printer driver packages</P -></LI -><LI -><P ->Providing the tools necessary for creating - the Imprints printer driver packages.</P -></LI -><LI -><P ->Providing an installation client which - will obtain and install printer drivers on remote Samba - and Windows NT 4 print servers.</P -></LI -></UL -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN2198" -></A ->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 - with the Samba distribution for more information). In short, - an Imprints driver package is a gzipped tarball containing the - driver files, related INF files, and a control file needed by the - installation client.</P -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN2201" -></A ->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 - entry in the database has an associated URL for the actual - downloading of the package. Each package is digitally signed - via GnuPG which can be used to verify that package downloaded - is actually the one referred in the Imprints database. It is - <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->not</I -></SPAN -> recommended that this security check - be disabled.</P -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN2205" -></A ->13.3.4. The Installation Client</H3 -><P ->More information regarding the Imprints installation client - is available in the <TT -CLASS="FILENAME" ->Imprints-Client-HOWTO.ps</TT -> - file included with the imprints source package.</P -><P ->The Imprints installation client comes in two forms.</P -><P -></P -><UL -><LI -><P ->a set of command line Perl scripts</P -></LI -><LI -><P ->a GTK+ based graphical interface to - the command line perl scripts</P -></LI -></UL -><P ->The installation client (in both forms) provides a means - of querying the Imprints database server for a matching - list of known printer model names as well as a means to - download and install the drivers on remote Samba and Windows - NT print servers.</P -><P ->The basic installation process is in four steps and - perl code is wrapped around <B -CLASS="COMMAND" ->smbclient</B -> - and <B -CLASS="COMMAND" ->rpcclient</B ->.</P -><P -><PRE -CLASS="PROGRAMLISTING" -> -foreach (supported architecture for a given driver) -{ - 1. rpcclient: Get the appropriate upload directory - on the remote server - 2. smbclient: Upload the driver files - 3. rpcclient: Issues an AddPrinterDriver() MS-RPC -} - -4. rpcclient: Issue an AddPrinterEx() MS-RPC to actually - create the printer</PRE -></P -><P ->One of the problems encountered when implementing - the Imprints tool set was the name space issues between - various supported client architectures. For example, Windows - NT includes a driver named "Apple LaserWriter II NTX v51.8" - and Windows 95 calls its version of this driver "Apple - LaserWriter II NTX"</P -><P ->The problem is how to know what client drivers have - been uploaded for a printer. As astute reader will remember - that the Windows NT Printer Properties dialog only includes - space for one printer driver name. A quick look in the - Windows NT 4.0 system registry at</P -><P -><TT -CLASS="FILENAME" ->HKLM\System\CurrentControlSet\Control\Print\Environment - </TT -></P -><P ->will reveal that Windows NT always uses the NT driver - name. This is ok as Windows NT always requires that at least - the Windows NT version of the printer driver is present. - However, Samba does not have the requirement internally. - Therefore, how can you use the NT driver name if is has not - already been installed?</P -><P ->The way of sidestepping this limitation is to require - that all Imprints printer driver packages include both the Intel - Windows NT and 95/98 printer drivers and that NT driver is - installed first.</P -></DIV -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN2227" -></A ->13.4. Diagnosis</H2 -><DIV -CLASS="SECT2" -><H3 -CLASS="SECT2" -><A -NAME="AEN2229" -></A ->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 -client to a Samba server, not the other way around. For the reverse -see the examples/printing directory.</P -><P ->Ok, so you want to print to a Samba server from your PC. The first -thing you need to understand is that Samba does not actually do any -printing itself, it just acts as a middleman between your PC client -and your Unix printing subsystem. Samba receives the file from the PC -then passes the file to a external "print command". What print command -you use is up to you.</P -><P ->The whole things is controlled using options in smb.conf. The most -relevant options (which you should look up in the smb.conf man page) -are:</P -><P -><PRE -CLASS="PROGRAMLISTING" -> [global] - print command - send a file to a spooler - lpq command - get spool queue status - lprm command - remove a job - [printers] - path = /var/spool/lpd/samba</PRE -></P -><P ->The following are nice to know about:</P -><P -><PRE -CLASS="PROGRAMLISTING" -> queuepause command - stop a printer or print queue - queueresume command - start a printer or print queue</PRE -></P -><P ->Example:</P -><P -><PRE -CLASS="PROGRAMLISTING" -> print command = /usr/bin/lpr -r -P%p %s - lpq command = /usr/bin/lpq -P%p %s - lprm command = /usr/bin/lprm -P%p %j - queuepause command = /usr/sbin/lpc -P%p stop - queuepause command = /usr/sbin/lpc -P%p start</PRE -></P -><P ->Samba should set reasonable defaults for these depending on your -system type, but it isn't clairvoyant. It is not uncommon that you -have to tweak these for local conditions. The commands should -always have fully specified pathnames, as the smdb may not have -the correct PATH values.</P -><P ->When you send a job to Samba to be printed, it will make a temporary -copy of it in the directory specified in the [printers] section. -and it should be periodically cleaned out. The lpr -r option -requests that the temporary copy be removed after printing; If -printing fails then you might find leftover files in this directory, -and it should be periodically cleaned out. Samba used the lpq -command to determine the "job number" assigned to your print job -by the spooler.</P -><P ->The %>letter< are "macros" that get dynamically replaced with appropriate -values when they are used. The %s gets replaced with the name of the spool -file that Samba creates and the %p gets replaced with the name of the -printer. The %j gets replaced with the "job number" which comes from -the lpq output.</P -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN2245" -></A ->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 -of the print file. A simple example of this kind of things might -be:</P -><P -><PRE -CLASS="PROGRAMLISTING" -> print command = /tmp/saveprint %p %s - - #!/bin/saveprint - # we make sure that we are the right user - /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 -></P -><P ->Then you print a file and try removing it. You may find that the -print queue needs to be stopped in order to see the queue status -and remove the job:</P -><P -><PRE -CLASS="PROGRAMLISTING" -> h4: {42} % echo hi >/tmp/hi -h4: {43} % smbclient //localhost/lw4 -added interface ip=10.0.0.4 bcast=10.0.0.255 nmask=255.255.255.0 -Password: -Domain=[ASTART] OS=[Unix] Server=[Samba 2.0.7] -smb: \> print /tmp/hi -putting file /tmp/hi as hi-17534 (0.0 kb/s) (average 0.0 kb/s) -smb: \> queue -1049 3 hi-17534 -smb: \> cancel 1049 -Error cancelling job 1049 : code 0 -smb: \> cancel 1049 -Job 1049 cancelled -smb: \> queue -smb: \> exit</PRE -></P -><P ->The 'code 0' indicates that the job was removed. The comment -by the smbclient is a bit misleading on this. -You can observe the command output and then and look at the -/tmp/tmp.print file to see what the results are. You can quickly -find out if the problem is with your printing system. Often people -have problems with their /etc/printcap file or permissions on -various print queues.</P -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN2254" -></A ->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 -use:</P -><P -><PRE -CLASS="PROGRAMLISTING" -> testprns printer /etc/printcap</PRE -></P -><P ->Samba can get its printcap information from a file or from a program. -You can try the following to see the format of the extracted -information:</P -><P -><PRE -CLASS="PROGRAMLISTING" -> testprns -a printer /etc/printcap - - testprns -a printer '|/bin/cat printcap'</PRE -></P -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN2262" -></A ->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 -the print spooler to set up queues and printcap information.</P -><P ->Samba requires either a printcap or program to deliver printcap -information. This printcap information has the format:</P -><P -><PRE -CLASS="PROGRAMLISTING" -> name|alias1|alias2...:option=value:...</PRE -></P -><P ->For almost all printing systems, the printer 'name' must be composed -only of alphanumeric or underscore '_' characters. Some systems also -allow hyphens ('-') as well. An alias is an alternative name for the -printer, and an alias with a space in it is used as a 'comment' -about the printer. The printcap format optionally uses a \ at the end of lines -to extend the printcap to multiple lines.</P -><P ->Here are some examples of printcap files:</P -><P -><P -></P -><OL -TYPE="1" -><LI -><P ->pr just printer name</P -></LI -><LI -><P ->pr|alias printer name and alias</P -></LI -><LI -><P ->pr|My Printer printer name, alias used as comment</P -></LI -><LI -><P ->pr:sh:\ Same as pr:sh:cm= testing - :cm= \ - testing</P -></LI -><LI -><P ->pr:sh Same as pr:sh:cm= testing - :cm= testing</P -></LI -></OL -></P -><P ->Samba reads the printcap information when first started. If you make -changes in the printcap information, then you must do the following:</P -><P -></P -><OL -TYPE="1" -><LI -><P ->make sure that the print spooler is aware of these changes. -The LPRng system uses the 'lpc reread' command to do this.</P -></LI -><LI -><P ->make sure that the spool queues, etc., exist and have the -correct permissions. The LPRng system uses the 'checkpc -f' -command to do this.</P -></LI -><LI -><P ->You now should send a SIGHUP signal to the smbd server to have -it reread the printcap information.</P -></LI -></OL -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN2290" -></A ->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 -the command to send the file, but there was no output from the printer.</P -><P ->First, check to make sure that the job REALLY is getting to the -right print queue. If you are using a BSD or LPRng print spooler, -you can temporarily stop the printing of jobs. Jobs can still be -submitted, but they will not be printed. Use:</P -><P -><PRE -CLASS="PROGRAMLISTING" -> lpc -Pprinter stop</PRE -></P -><P ->Now submit a print job and then use 'lpq -Pprinter' to see if the -job is in the print queue. If it is not in the print queue then -you will have to find out why it is not being accepted for printing.</P -><P ->Next, you may want to check to see what the format of the job really -was. With the assistance of the system administrator you can view -the submitted jobs files. You may be surprised to find that these -are not in what you would expect to call a printable format. -You can use the UNIX 'file' utitily to determine what the job -format actually is:</P -><P -><PRE -CLASS="PROGRAMLISTING" -> cd /var/spool/lpd/printer # spool directory of print jobs - ls # find job files - file dfA001myhost</PRE -></P -><P ->You should make sure that your printer supports this format OR that -your system administrator has installed a 'print filter' that will -convert the file to a format appropriate for your printer.</P -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN2301" -></A ->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 -><P ->The most common problem is extra pages of output: banner pages -OR blank pages at the end.</P -><P ->If you are getting banner pages, check and make sure that the -printcap option or printer option is configured for no banners. -If you have a printcap, this is the :sh (suppress header or banner -page) option. You should have the following in your printer.</P -><P -><PRE -CLASS="PROGRAMLISTING" -> printer: ... :sh</PRE -></P -><P ->If you have this option and are still getting banner pages, there -is a strong chance that your printer is generating them for you -automatically. You should make sure that banner printing is disabled -for the printer. This usually requires using the printer setup software -or procedures supplied by the printer manufacturer.</P -><P ->If you get an extra page of output, this could be due to problems -with your job format, or if you are generating PostScript jobs, -incorrect setting on your printer driver on the MicroSoft client. -For example, under Win95 there is a option:</P -><P -><PRE -CLASS="PROGRAMLISTING" -> Printers|Printer Name|(Right Click)Properties|Postscript|Advanced|</PRE -></P -><P ->that allows you to choose if a Ctrl-D is appended to all jobs. -This is a very bad thing to do, as most spooling systems will -automatically add a ^D to the end of the job if it is detected as -PostScript. The multiple ^D may cause an additional page of output.</P -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN2313" -></A ->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 -the printer think the job is a text file, or your printer simply -does not support PostScript. You may need to enable 'Automatic -Format Detection' on your printer.</P -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN2316" -></A ->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. -Doing print accounting is easy by passing the %U option to a print -command shell script. You could even make the print command detect -the type of output and its size and send it to an appropriate -printer.</P -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN2319" -></A ->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 -></DIV -></DIV -></DIV -><DIV -CLASS="CHAPTER" -><HR><H1 -><A -NAME="WINBIND" -></A ->Chapter 14. Unified Logons between Windows NT and UNIX using Winbind</H1 -><DIV -CLASS="SECT1" -><H2 -CLASS="SECT1" -><A -NAME="AEN2360" -></A ->14.1. Abstract</H2 -><P ->Integration of UNIX and Microsoft Windows NT through - a unified logon has been considered a "holy grail" in heterogeneous - computing environments for a long time. We present - <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->winbind</I -></SPAN ->, a component of the Samba suite - of programs as a solution to the unified logon problem. Winbind - uses a UNIX implementation - of Microsoft RPC calls, Pluggable Authentication Modules, and the Name - Service Switch to allow Windows NT domain users to appear and operate - as UNIX users on a UNIX machine. This paper describes the winbind - system, explaining the functionality it provides, how it is configured, - and how it works internally.</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN2364" -></A ->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 - use different technologies for implementing them. This fact has - made it difficult to integrate the two systems in a satisfactory - manner.</P -><P ->One common solution in use today has been to create - identically named user accounts on both the UNIX and Windows systems - and use the Samba suite of programs to provide file and print services - between the two. This solution is far from perfect however, as - adding and deleting users on both sets of machines becomes a chore - and two sets of passwords are required both of which - can lead to synchronization problems between the UNIX and Windows - systems and confusion for users.</P -><P ->We divide the unified logon problem for UNIX machines into - three smaller problems:</P -><P -></P -><UL -><LI -><P ->Obtaining Windows NT user and group information - </P -></LI -><LI -><P ->Authenticating Windows NT users - </P -></LI -><LI -><P ->Password changing for Windows NT users - </P -></LI -></UL -><P ->Ideally, a prospective solution to the unified logon problem - would satisfy all the above components without duplication of - information on the UNIX machines and without creating additional - tasks for the system administrator when maintaining users and - groups on either system. The winbind system provides a simple - and elegant solution to all three components of the unified logon - problem.</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN2377" -></A ->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 - this is done the UNIX box will see NT users and groups as if - they were native UNIX users and groups, allowing the NT domain - to be used in much the same manner that NIS+ is used within - UNIX-only environments.</P -><P ->The end result is that whenever any - program on the UNIX machine asks the operating system to lookup - a user or group name, the query will be resolved by asking the - NT domain controller for the specified domain to do the lookup. - Because Winbind hooks into the operating system at a low level - (via the NSS name resolution modules in the C library) this - redirection to the NT domain controller is completely - transparent.</P -><P ->Users on the UNIX machine can then use NT user and group - names as they would use "native" UNIX names. They can chown files - so that they are owned by NT domain users or even login to the - UNIX machine and run a UNIX X-Window session as a domain user.</P -><P ->The only obvious indication that Winbind is being used is - that user and group names take the form DOMAIN\user and - DOMAIN\group. This is necessary as it allows Winbind to determine - that redirection to a domain controller is wanted for a particular - lookup and which trusted domain is being referenced.</P -><P ->Additionally, Winbind provides an authentication service - that hooks into the Pluggable Authentication Modules (PAM) system - to provide authentication via a NT domain to any PAM enabled - applications. This capability solves the problem of synchronizing - passwords between systems since all passwords are stored in a single - location (on the domain controller).</P -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN2384" -></A ->14.3.1. Target Uses</H3 -><P ->Winbind is targeted at organizations that have an - existing NT based domain infrastructure into which they wish - to put UNIX workstations or servers. Winbind will allow these - organizations to deploy UNIX workstations without having to - maintain a separate account infrastructure. This greatly - simplifies the administrative overhead of deploying UNIX - workstations into a NT based organization.</P -><P ->Another interesting way in which we expect Winbind to - be used is as a central part of UNIX based appliances. Appliances - that provide file and print services to Microsoft based networks - will be able to use Winbind to provide seamless integration of - the appliance into the domain.</P -></DIV -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN2388" -></A ->14.4. How Winbind Works</H2 -><P ->The winbind system is designed around a client/server - architecture. A long running <B -CLASS="COMMAND" ->winbindd</B -> daemon - listens on a UNIX domain socket waiting for requests - to arrive. These requests are generated by the NSS and PAM - clients and processed sequentially.</P -><P ->The technologies used to implement winbind are described - in detail below.</P -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN2393" -></A ->14.4.1. Microsoft Remote Procedure Calls</H3 -><P ->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 - Windows NT machines including remote management, user authentication - and print spooling. Although initially this work was done - to aid the implementation of Primary Domain Controller (PDC) - functionality in Samba, it has also yielded a body of code which - can be used for other purposes.</P -><P ->Winbind uses various MSRPC calls to enumerate domain users - and groups and to obtain detailed information about individual - users or groups. Other MSRPC calls can be used to authenticate - NT domain users and to change user passwords. By directly querying - a Windows PDC for user and group information, winbind maps the - NT account information onto UNIX user and group names.</P -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -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 ->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 - information such as hostnames, mail aliases and user information - to be resolved from different sources. For example, a standalone - UNIX workstation may resolve system information from a series of - flat files stored on the local filesystem. A networked workstation - may first attempt to resolve system information from local files, - and then consult a NIS database for user information or a DNS server - for hostname information.</P -><P ->The NSS application programming interface allows winbind - to present itself as a source of system information when - resolving UNIX usernames and groups. Winbind uses this interface, - and information obtained from a Windows NT server using MSRPC - calls to provide a new source of account enumeration. Using standard - UNIX library calls, one can enumerate the users and groups on - a UNIX machine running winbind and see all users and groups in - a NT domain plus any trusted domain as though they were local - users and groups.</P -><P ->The primary control file for NSS is - <TT -CLASS="FILENAME" ->/etc/nsswitch.conf</TT ->. - When a UNIX application makes a request to do a lookup - the C library looks in <TT -CLASS="FILENAME" ->/etc/nsswitch.conf</TT -> - for a line which matches the service type being requested, for - example the "passwd" service type is used when user or group names - are looked up. This config line species which implementations - of that service should be tried and in what order. If the passwd - config line is:</P -><P -><B -CLASS="COMMAND" ->passwd: files example</B -></P -><P ->then the C library will first load a module called - <TT -CLASS="FILENAME" ->/lib/libnss_files.so</TT -> followed by - the module <TT -CLASS="FILENAME" ->/lib/libnss_example.so</TT ->. The - C library will dynamically load each of these modules in turn - and call resolver functions within the modules to try to resolve - the request. Once the request is resolved the C library returns the - result to the application.</P -><P ->This NSS interface provides a very easy way for Winbind - to hook into the operating system. All that needs to be done - is to put <TT -CLASS="FILENAME" ->libnss_winbind.so</TT -> in <TT -CLASS="FILENAME" ->/lib/</TT -> - then add "winbind" into <TT -CLASS="FILENAME" ->/etc/nsswitch.conf</TT -> at - the appropriate place. The C library will then call Winbind to - resolve user and group names.</P -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN2416" -></A ->14.4.4. Pluggable Authentication Modules</H3 -><P ->Pluggable Authentication Modules, also known as PAM, - is a system for abstracting authentication and authorization - technologies. With a PAM module it is possible to specify different - authentication methods for different system applications without - having to recompile these applications. PAM is also useful - for implementing a particular policy for authorization. For example, - a system administrator may only allow console logins from users - stored in the local password file but only allow users resolved from - a NIS database to log in over the network.</P -><P ->Winbind uses the authentication management and password - management PAM interface to integrate Windows NT users into a - UNIX system. This allows Windows NT users to log in to a UNIX - machine and be authenticated against a suitable Primary Domain - Controller. These users can also change their passwords and have - this change take effect directly on the Primary Domain Controller. - </P -><P ->PAM is configured by providing control files in the directory - <TT -CLASS="FILENAME" ->/etc/pam.d/</TT -> for each of the services that - require authentication. When an authentication request is made - by an application the PAM code in the C library looks up this - control file to determine what modules to load to do the - authentication check and in what order. This interface makes adding - a new authentication service for Winbind very easy, all that needs - to be done is that the <TT -CLASS="FILENAME" ->pam_winbind.so</TT -> module - is copied to <TT -CLASS="FILENAME" ->/lib/security/</TT -> and the PAM - control files for relevant services are updated to allow - authentication via winbind. See the PAM documentation - for more details.</P -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN2424" -></A ->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 - slightly different to UNIX which has a range of numbers that are - used to identify users, and the same range in which to identify - groups. It is winbind's job to convert RIDs to UNIX id numbers and - vice versa. When winbind is configured it is given part of the UNIX - user id space and a part of the UNIX group id space in which to - store Windows NT users and groups. If a Windows NT user is - resolved for the first time, it is allocated the next UNIX id from - the range. The same process applies for Windows NT groups. Over - time, winbind will have mapped all Windows NT users and groups - to UNIX user ids and group ids.</P -><P ->The results of this mapping are stored persistently in - an ID mapping database held in a tdb database). This ensures that - RIDs are mapped to UNIX IDs in a consistent way.</P -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN2428" -></A ->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 - uses a caching scheme based on the SAM sequence number supplied - by NT domain controllers. User or group information returned - by a PDC is cached by winbind along with a sequence number also - returned by the PDC. This sequence number is incremented by - Windows NT whenever any user or group information is modified. If - a cached entry has expired, the sequence number is requested from - the PDC and compared against the sequence number of the cached entry. - If the sequence numbers do not match, then the cached information - is discarded and up to date information is requested directly - from the PDC.</P -></DIV -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN2431" -></A ->14.5. Installation and Configuration</H2 -><P ->Many thanks to John Trostel <A -HREF="mailto:jtrostel@snapserver.com" -TARGET="_top" ->jtrostel@snapserver.com</A -> -for providing the HOWTO for this section.</P -><P ->This HOWTO describes how to get winbind services up and running -to control access and authenticate users on your Linux box using -the winbind services which come with SAMBA 2.2.2.</P -><P ->There is also some Solaris specific information in -<TT -CLASS="FILENAME" ->docs/textdocs/Solaris-Winbind-HOWTO.txt</TT ->. -Future revisions of this document will incorporate that -information.</P -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN2438" -></A ->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 -and authentication control for Windows Domain users through an NT -or Win2K PDC for 'regular' services, such as telnet a nd ftp, as -well for SAMBA services.</P -><P ->This HOWTO has been written from a 'RedHat-centric' perspective, so if -you are using another distribution, you may have to modify the instructions -somewhat to fit the way your distribution works.</P -><P -></P -><UL -><LI -><P -> <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->Why should I to this?</I -></SPAN -> - </P -><P ->This allows the SAMBA administrator to rely on the - authentication mechanisms on the NT/Win2K PDC for the authentication - of domain members. NT/Win2K users no longer need to have separate - accounts on the SAMBA server. - </P -></LI -><LI -><P -> <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->Who should be reading this document?</I -></SPAN -> - </P -><P -> This HOWTO is designed for system administrators. If you are - implementing SAMBA on a file server and wish to (fairly easily) - integrate existing NT/Win2K users from your PDC onto the - SAMBA server, this HOWTO is for you. That said, I am no NT or PAM - expert, so you may find a better or easier way to accomplish - these tasks. - </P -></LI -></UL -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN2451" -></A ->14.5.2. Requirements</H3 -><P ->If you have a samba configuration file that you are currently -using... <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->BACK IT UP!</I -></SPAN -> If your system already uses PAM, -<SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->back up the <TT -CLASS="FILENAME" ->/etc/pam.d</TT -> directory -contents!</I -></SPAN -> If you haven't already made a boot disk, -<SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->MAKE ONE NOW!</I -></SPAN -></P -><P ->Messing with the pam configuration files can make it nearly impossible -to log in to yourmachine. That's why you want to be able to boot back -into your machine in single user mode and restore your -<TT -CLASS="FILENAME" ->/etc/pam.d</TT -> back to the original state they were in if -you get frustrated with the way things are going. ;-)</P -><P ->The latest version of SAMBA (version 3.0 as of this writing), now -includes a functioning winbindd daemon. Please refer to the -<A -HREF="http://samba.org/" -TARGET="_top" ->main SAMBA web page</A -> or, -better yet, your closest SAMBA mirror site for instructions on -downloading the source code.</P -><P ->To allow Domain users the ability to access SAMBA shares and -files, as well as potentially other services provided by your -SAMBA machine, PAM (pluggable authentication modules) must -be setup properly on your machine. In order to compile the -winbind modules, you should have at least the pam libraries resident -on your system. For recent RedHat systems (7.1, for instance), that -means <TT -CLASS="FILENAME" ->pam-0.74-22</TT ->. For best results, it is helpful to also -install the development packages in <TT -CLASS="FILENAME" ->pam-devel-0.74-22</TT ->.</P -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN2465" -></A ->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 -CLASS="COMMAND" ->smbd</B ->, -<B -CLASS="COMMAND" ->nmbd</B ->, and <B -CLASS="COMMAND" ->winbindd</B -> processes that may -be running. To use PAM, you will want to make sure that you have the -standard PAM package (for RedHat) which supplies the <TT -CLASS="FILENAME" ->/etc/pam.d</TT -> -directory structure, including the pam modules are used by pam-aware -services, several pam libraries, and the <TT -CLASS="FILENAME" ->/usr/doc</TT -> -and <TT -CLASS="FILENAME" ->/usr/man</TT -> entries for pam. Winbind built better -in SAMBA if the pam-devel package was also installed. This package includes -the header files needed to compile pam-aware applications. For instance, -my RedHat system has both <TT -CLASS="FILENAME" ->pam-0.74-22</TT -> and -<TT -CLASS="FILENAME" ->pam-devel-0.74-22</TT -> RPMs installed.</P -><DIV -CLASS="SECT3" -><HR><H4 -CLASS="SECT3" -><A -NAME="AEN2476" -></A ->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 -whether or not you have previously built the Samba binaries.</P -><P -><PRE -CLASS="PROGRAMLISTING" -><TT -CLASS="PROMPT" ->root#</TT -> <B -CLASS="COMMAND" ->autoconf</B -> -<TT -CLASS="PROMPT" ->root#</TT -> <B -CLASS="COMMAND" ->make clean</B -> -<TT -CLASS="PROMPT" ->root#</TT -> <B -CLASS="COMMAND" ->rm config.cache</B -> -<TT -CLASS="PROMPT" ->root#</TT -> <B -CLASS="COMMAND" ->./configure</B -> -<TT -CLASS="PROMPT" ->root#</TT -> <B -CLASS="COMMAND" ->make</B -> -<TT -CLASS="PROMPT" ->root#</TT -> <B -CLASS="COMMAND" ->make install</B -></PRE -></P -><P ->This will, by default, install SAMBA in <TT -CLASS="FILENAME" ->/usr/local/samba</TT ->. -See the main SAMBA documentation if you want to install SAMBA somewhere else. -It will also build the winbindd executable and libraries. </P -></DIV -><DIV -CLASS="SECT3" -><HR><H4 -CLASS="SECT3" -><A -NAME="AEN2495" -></A ->14.5.3.2. Configure <TT -CLASS="FILENAME" ->nsswitch.conf</TT -> and the -winbind libraries</H4 -><P ->The libraries needed to run the <B -CLASS="COMMAND" ->winbindd</B -> daemon -through nsswitch need to be copied to their proper locations, so</P -><P -><TT -CLASS="PROMPT" ->root#</TT -> <B -CLASS="COMMAND" ->cp ../samba/source/nsswitch/libnss_winbind.so /lib</B -></P -><P ->I also found it necessary to make the following symbolic link:</P -><P -><TT -CLASS="PROMPT" ->root#</TT -> <B -CLASS="COMMAND" ->ln -s /lib/libnss_winbind.so /lib/libnss_winbind.so.2</B -></P -><P ->And, in the case of Sun solaris:</P -><P -><TT -CLASS="PROMPT" ->root#</TT -> <B -CLASS="COMMAND" ->ln -s /usr/lib/libnss_winbind.so /usr/lib/libnss_winbind.so.1</B -> -<TT -CLASS="PROMPT" ->root#</TT -> <B -CLASS="COMMAND" ->ln -s /usr/lib/libnss_winbind.so /usr/lib/nss_winbind.so.1</B -> -<TT -CLASS="PROMPT" ->root#</TT -> <B -CLASS="COMMAND" ->ln -s /usr/lib/libnss_winbind.so /usr/lib/nss_winbind.so.2</B -></P -><P ->Now, as root you need to edit <TT -CLASS="FILENAME" ->/etc/nsswitch.conf</TT -> to -allow user and group entries to be visible from the <B -CLASS="COMMAND" ->winbindd</B -> -daemon. My <TT -CLASS="FILENAME" ->/etc/nsswitch.conf</TT -> file look like -this after editing:</P -><P -><PRE -CLASS="PROGRAMLISTING" -> passwd: files winbind - shadow: files - group: files winbind</PRE -></P -><P -> -The libraries needed by the winbind daemon will be automatically -entered into the <B -CLASS="COMMAND" ->ldconfig</B -> cache the next time -your system reboots, but it -is faster (and you don't need to reboot) if you do it manually:</P -><P -><TT -CLASS="PROMPT" ->root#</TT -> <B -CLASS="COMMAND" ->/sbin/ldconfig -v | grep winbind</B -></P -><P ->This makes <TT -CLASS="FILENAME" ->libnss_winbind</TT -> available to winbindd -and echos back a check to you.</P -></DIV -><DIV -CLASS="SECT3" -><HR><H4 -CLASS="SECT3" -><A -NAME="AEN2528" -></A ->14.5.3.3. Configure smb.conf</H4 -><P ->Several parameters are needed in the smb.conf file to control -the behavior of <B -CLASS="COMMAND" ->winbindd</B ->. Configure -<TT -CLASS="FILENAME" ->smb.conf</TT -> These are described in more detail in -the <A -HREF="winbindd.8.html" -TARGET="_top" ->winbindd(8)</A -> man page. My -<TT -CLASS="FILENAME" ->smb.conf</TT -> file was modified to -include the following entries in the [global] section:</P -><P -><PRE -CLASS="PROGRAMLISTING" ->[global] - <...> - # separate domain and username with '+', like DOMAIN+username - <A -HREF="winbindd.8.html#WINBINDSEPARATOR" -TARGET="_top" ->winbind separator</A -> = + - # use uids from 10000 to 20000 for domain users - <A -HREF="winbindd.8.html#WINBINDUID" -TARGET="_top" ->winbind uid</A -> = 10000-20000 - # use gids from 10000 to 20000 for domain groups - <A -HREF="winbindd.8.html#WINBINDGID" -TARGET="_top" ->winbind gid</A -> = 10000-20000 - # allow enumeration of winbind users and groups - <A -HREF="winbindd.8.html#WINBINDENUMUSERS" -TARGET="_top" ->winbind enum users</A -> = yes - <A -HREF="winbindd.8.html#WINBINDENUMGROUP" -TARGET="_top" ->winbind enum groups</A -> = yes - # give winbind users a real shell (only needed if they have telnet access) - <A -HREF="winbindd.8.html#TEMPLATEHOMEDIR" -TARGET="_top" ->template homedir</A -> = /home/winnt/%D/%U - <A -HREF="winbindd.8.html#TEMPLATESHELL" -TARGET="_top" ->template shell</A -> = /bin/bash</PRE -></P -></DIV -><DIV -CLASS="SECT3" -><HR><H4 -CLASS="SECT3" -><A -NAME="AEN2544" -></A ->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 -CLASS="REPLACEABLE" -><I ->DOMAIN</I -></TT -> is the name of -your Windows domain and <TT -CLASS="REPLACEABLE" -><I ->Administrator</I -></TT -> is -a domain user who has administrative privileges in the domain.</P -><P -><TT -CLASS="PROMPT" ->root#</TT -> <B -CLASS="COMMAND" ->/usr/local/samba/bin/net join -S PDC -U Administrator</B -></P -><P ->The proper response to the command should be: "Joined the domain -<TT -CLASS="REPLACEABLE" -><I ->DOMAIN</I -></TT ->" where <TT -CLASS="REPLACEABLE" -><I ->DOMAIN</I -></TT -> -is your DOMAIN name.</P -></DIV -><DIV -CLASS="SECT3" -><HR><H4 -CLASS="SECT3" -><A -NAME="AEN2555" -></A ->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 -SAMBA start, but it is possible to test out just the winbind -portion first. To start up winbind services, enter the following -command as root:</P -><P -><TT -CLASS="PROMPT" ->root#</TT -> <B -CLASS="COMMAND" ->/usr/local/samba/bin/winbindd</B -></P -><P ->I'm always paranoid and like to make sure the daemon -is really running...</P -><P -><TT -CLASS="PROMPT" ->root#</TT -> <B -CLASS="COMMAND" ->ps -ae | grep winbindd</B -></P -><P ->This command should produce output like this, if the daemon is running</P -><P ->3025 ? 00:00:00 winbindd</P -><P ->Now... for the real test, try to get some information about the -users on your PDC</P -><P -><TT -CLASS="PROMPT" ->root#</TT -> <B -CLASS="COMMAND" ->/usr/local/samba/bin/wbinfo -u</B -></P -><P -> -This should echo back a list of users on your Windows users on -your PDC. For example, I get the following response:</P -><P -><PRE -CLASS="PROGRAMLISTING" ->CEO+Administrator -CEO+burdell -CEO+Guest -CEO+jt-ad -CEO+krbtgt -CEO+TsInternetUser</PRE -></P -><P ->Obviously, I have named my domain 'CEO' and my <TT -CLASS="PARAMETER" -><I ->winbind -separator</I -></TT -> is '+'.</P -><P ->You can do the same sort of thing to get group information from -the PDC:</P -><P -><PRE -CLASS="PROGRAMLISTING" -><TT -CLASS="PROMPT" ->root#</TT -> <B -CLASS="COMMAND" ->/usr/local/samba/bin/wbinfo -g</B -> -CEO+Domain Admins -CEO+Domain Users -CEO+Domain Guests -CEO+Domain Computers -CEO+Domain Controllers -CEO+Cert Publishers -CEO+Schema Admins -CEO+Enterprise Admins -CEO+Group Policy Creator Owners</PRE -></P -><P ->The function 'getent' can now be used to get unified -lists of both local and PDC users and groups. -Try the following command:</P -><P -><TT -CLASS="PROMPT" ->root#</TT -> <B -CLASS="COMMAND" ->getent passwd</B -></P -><P ->You should get a list that looks like your <TT -CLASS="FILENAME" ->/etc/passwd</TT -> -list followed by the domain users with their new uids, gids, home -directories and default shells.</P -><P ->The same thing can be done for groups with the command</P -><P -><TT -CLASS="PROMPT" ->root#</TT -> <B -CLASS="COMMAND" ->getent group</B -></P -></DIV -><DIV -CLASS="SECT3" -><HR><H4 -CLASS="SECT3" -><A -NAME="AEN2591" -></A ->14.5.3.6. Fix the init.d startup scripts</H4 -><DIV -CLASS="SECT4" -><H5 -CLASS="SECT4" -><A -NAME="AEN2593" -></A ->14.5.3.6.1. Linux</H5 -><P ->The <B -CLASS="COMMAND" ->winbindd</B -> daemon needs to start up after the -<B -CLASS="COMMAND" ->smbd</B -> and <B -CLASS="COMMAND" ->nmbd</B -> daemons are running. -To accomplish this task, you need to modify the startup scripts of your system. They are located at <TT -CLASS="FILENAME" ->/etc/init.d/smb</TT -> in RedHat and -<TT -CLASS="FILENAME" ->/etc/init.d/samba</TT -> in Debian. -script to add commands to invoke this daemon in the proper sequence. My -startup script starts up <B -CLASS="COMMAND" ->smbd</B ->, -<B -CLASS="COMMAND" ->nmbd</B ->, and <B -CLASS="COMMAND" ->winbindd</B -> from the -<TT -CLASS="FILENAME" ->/usr/local/samba/bin</TT -> directory directly. The 'start' -function in the script looks like this:</P -><P -><PRE -CLASS="PROGRAMLISTING" ->start() { - KIND="SMB" - echo -n $"Starting $KIND services: " - daemon /usr/local/samba/bin/smbd $SMBDOPTIONS - RETVAL=$? - echo - KIND="NMB" - echo -n $"Starting $KIND services: " - daemon /usr/local/samba/bin/nmbd $NMBDOPTIONS - RETVAL2=$? - echo - KIND="Winbind" - echo -n $"Starting $KIND services: " - 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=1 - return $RETVAL -}</PRE -></P -><P ->The 'stop' function has a corresponding entry to shut down the -services and look s like this:</P -><P -><PRE -CLASS="PROGRAMLISTING" ->stop() { - KIND="SMB" - echo -n $"Shutting down $KIND services: " - killproc smbd - RETVAL=$? - echo - KIND="NMB" - echo -n $"Shutting down $KIND services: " - killproc nmbd - RETVAL2=$? - echo - KIND="Winbind" - 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 - echo "" - return $RETVAL -}</PRE -></P -></DIV -><DIV -CLASS="SECT4" -><HR><H5 -CLASS="SECT4" -><A -NAME="AEN2610" -></A ->14.5.3.6.2. Solaris</H5 -><P ->On solaris, you need to modify the -<TT -CLASS="FILENAME" ->/etc/init.d/samba.server</TT -> startup script. It usually -only starts smbd and nmbd but should now start winbindd too. If you -have samba installed in <TT -CLASS="FILENAME" ->/usr/local/samba/bin</TT ->, -the file could contains something like this:</P -><P -><PRE -CLASS="PROGRAMLISTING" ->## -## samba.server -## - -if [ ! -d /usr/bin ] -then # /usr not mounted - exit -fi - -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 -} - -# Start/stop processes required for samba server - -case "$1" in - -'start') -# -# Edit these lines to suit your installation (paths, workgroup, host) -# -echo Starting SMBD - /usr/local/samba/bin/smbd -D -s \ - /usr/local/samba/smb.conf - -echo Starting NMBD - /usr/local/samba/bin/nmbd -D -l \ - /usr/local/samba/var/log -s /usr/local/samba/smb.conf - -echo Starting Winbind Daemon - /usr/local/samba/bin/winbindd - ;; - -'stop') - killproc nmbd - killproc smbd - killproc winbindd - ;; - -*) - echo "Usage: /etc/init.d/samba.server { start | stop }" - ;; -esac</PRE -></P -></DIV -><DIV -CLASS="SECT4" -><HR><H5 -CLASS="SECT4" -><A -NAME="AEN2617" -></A ->14.5.3.6.3. Restarting</H5 -><P ->If you restart the <B -CLASS="COMMAND" ->smbd</B ->, <B -CLASS="COMMAND" ->nmbd</B ->, -and <B -CLASS="COMMAND" ->winbindd</B -> daemons at this point, you -should be able to connect to the samba server as a domain member just as -if you were a local user.</P -></DIV -></DIV -><DIV -CLASS="SECT3" -><HR><H4 -CLASS="SECT3" -><A -NAME="AEN2623" -></A ->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 -services, keep reading. The pam configuration files need to be altered in -this step. (Did you remember to make backups of your original -<TT -CLASS="FILENAME" ->/etc/pam.d</TT -> files? If not, do it now.)</P -><P ->You will need a pam module to use winbindd with these other services. This -module will be compiled in the <TT -CLASS="FILENAME" ->../source/nsswitch</TT -> directory -by invoking the command</P -><P -><TT -CLASS="PROMPT" ->root#</TT -> <B -CLASS="COMMAND" ->make nsswitch/pam_winbind.so</B -></P -><P ->from the <TT -CLASS="FILENAME" ->../source</TT -> directory. The -<TT -CLASS="FILENAME" ->pam_winbind.so</TT -> file should be copied to the location of -your other pam security modules. On my RedHat system, this was the -<TT -CLASS="FILENAME" ->/lib/security</TT -> directory. On Solaris, the pam security -modules reside in <TT -CLASS="FILENAME" ->/usr/lib/security</TT ->.</P -><P -><TT -CLASS="PROMPT" ->root#</TT -> <B -CLASS="COMMAND" ->cp ../samba/source/nsswitch/pam_winbind.so /lib/security</B -></P -><DIV -CLASS="SECT4" -><HR><H5 -CLASS="SECT4" -><A -NAME="AEN2640" -></A ->14.5.3.7.1. Linux/FreeBSD-specific PAM configuration</H5 -><P ->The <TT -CLASS="FILENAME" ->/etc/pam.d/samba</TT -> file does not need to be changed. I -just left this fileas it was:</P -><P -><PRE -CLASS="PROGRAMLISTING" ->auth required /lib/security/pam_stack.so service=system-auth -account required /lib/security/pam_stack.so service=system-auth</PRE -></P -><P ->The other services that I modified to allow the use of winbind -as an authentication service were the normal login on the console (or a terminal -session), telnet logins, and ftp service. In order to enable these -services, you may first need to change the entries in -<TT -CLASS="FILENAME" ->/etc/xinetd.d</TT -> (or <TT -CLASS="FILENAME" ->/etc/inetd.conf</TT ->). -RedHat 7.1 uses the new xinetd.d structure, in this case you need -to change the lines in <TT -CLASS="FILENAME" ->/etc/xinetd.d/telnet</TT -> -and <TT -CLASS="FILENAME" ->/etc/xinetd.d/wu-ftp</TT -> from </P -><P -><PRE -CLASS="PROGRAMLISTING" ->enable = no</PRE -></P -><P ->to</P -><P -><PRE -CLASS="PROGRAMLISTING" ->enable = yes</PRE -></P -><P -> -For ftp services to work properly, you will also need to either -have individual directories for the domain users already present on -the server, or change the home directory template to a general -directory for all domain users. These can be easily set using -the <TT -CLASS="FILENAME" ->smb.conf</TT -> global entry -<B -CLASS="COMMAND" ->template homedir</B ->.</P -><P ->The <TT -CLASS="FILENAME" ->/etc/pam.d/ftp</TT -> file can be changed -to allow winbind ftp access in a manner similar to the -samba file. My <TT -CLASS="FILENAME" ->/etc/pam.d/ftp</TT -> file was -changed to look like this:</P -><P -><PRE -CLASS="PROGRAMLISTING" ->auth required /lib/security/pam_listfile.so item=user sense=deny file=/etc/ftpusers onerr=succeed -auth sufficient /lib/security/pam_winbind.so -auth required /lib/security/pam_stack.so service=system-auth -auth required /lib/security/pam_shells.so -account sufficient /lib/security/pam_winbind.so -account required /lib/security/pam_stack.so service=system-auth -session required /lib/security/pam_stack.so service=system-auth</PRE -></P -><P ->The <TT -CLASS="FILENAME" ->/etc/pam.d/login</TT -> file can be changed nearly the -same way. It now looks like this:</P -><P -><PRE -CLASS="PROGRAMLISTING" ->auth required /lib/security/pam_securetty.so -auth sufficient /lib/security/pam_winbind.so -auth sufficient /lib/security/pam_unix.so use_first_pass -auth required /lib/security/pam_stack.so service=system-auth -auth required /lib/security/pam_nologin.so -account sufficient /lib/security/pam_winbind.so -account required /lib/security/pam_stack.so service=system-auth -password required /lib/security/pam_stack.so service=system-auth -session required /lib/security/pam_stack.so service=system-auth -session optional /lib/security/pam_console.so</PRE -></P -><P ->In this case, I added the <B -CLASS="COMMAND" ->auth sufficient /lib/security/pam_winbind.so</B -> -lines as before, but also added the <B -CLASS="COMMAND" ->required pam_securetty.so</B -> -above it, to disallow root logins over the network. I also added a -<B -CLASS="COMMAND" ->sufficient /lib/security/pam_unix.so use_first_pass</B -> -line after the <B -CLASS="COMMAND" ->winbind.so</B -> line to get rid of annoying -double prompts for passwords.</P -></DIV -><DIV -CLASS="SECT4" -><HR><H5 -CLASS="SECT4" -><A -NAME="AEN2673" -></A ->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 -that I made.You can customize the pam.conf file as per your requirements,but -be sure of those changes because in the worst case it will leave your system -nearly impossible to boot.</P -><P -><PRE -CLASS="PROGRAMLISTING" -># -#ident "@(#)pam.conf 1.14 99/09/16 SMI" -# -# Copyright (c) 1996-1999, Sun Microsystems, Inc. -# All Rights Reserved. -# -# PAM configuration -# -# Authentication management -# -login auth required /usr/lib/security/pam_winbind.so -login auth required /usr/lib/security/$ISA/pam_unix.so.1 try_first_pass -login auth required /usr/lib/security/$ISA/pam_dial_auth.so.1 try_first_pass -# -rlogin auth sufficient /usr/lib/security/pam_winbind.so -rlogin auth sufficient /usr/lib/security/$ISA/pam_rhosts_auth.so.1 -rlogin auth required /usr/lib/security/$ISA/pam_unix.so.1 try_first_pass -# -dtlogin auth sufficient /usr/lib/security/pam_winbind.so -dtlogin auth required /usr/lib/security/$ISA/pam_unix.so.1 try_first_pass -# -rsh auth required /usr/lib/security/$ISA/pam_rhosts_auth.so.1 -other auth sufficient /usr/lib/security/pam_winbind.so -other auth required /usr/lib/security/$ISA/pam_unix.so.1 try_first_pass -# -# Account management -# -login account sufficient /usr/lib/security/pam_winbind.so -login account requisite /usr/lib/security/$ISA/pam_roles.so.1 -login account required /usr/lib/security/$ISA/pam_unix.so.1 -# -dtlogin account sufficient /usr/lib/security/pam_winbind.so -dtlogin account requisite /usr/lib/security/$ISA/pam_roles.so.1 -dtlogin account required /usr/lib/security/$ISA/pam_unix.so.1 -# -other account sufficient /usr/lib/security/pam_winbind.so -other account requisite /usr/lib/security/$ISA/pam_roles.so.1 -other account required /usr/lib/security/$ISA/pam_unix.so.1 -# -# Session management -# -other session required /usr/lib/security/$ISA/pam_unix.so.1 -# -# Password management -# -#other password sufficient /usr/lib/security/pam_winbind.so -other password required /usr/lib/security/$ISA/pam_unix.so.1 -dtsession auth required /usr/lib/security/$ISA/pam_unix.so.1 -# -# Support for Kerberos V5 authentication (uncomment to use Kerberos) -# -#rlogin auth optional /usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass -#login auth optional /usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass -#dtlogin auth optional /usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass -#other auth optional /usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass -#dtlogin account optional /usr/lib/security/$ISA/pam_krb5.so.1 -#other account optional /usr/lib/security/$ISA/pam_krb5.so.1 -#other session optional /usr/lib/security/$ISA/pam_krb5.so.1 -#other password optional /usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass</PRE -></P -><P ->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 and try connecting through your application that you -configured in the pam.conf.</P -></DIV -></DIV -></DIV -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN2680" -></A ->14.6. Limitations</H2 -><P ->Winbind has a number of limitations in its current - released version that we hope to overcome in future - releases:</P -><P -></P -><UL -><LI -><P ->Winbind is currently only available for - 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 - Modules systems. This is becoming more common as NSS and - PAM gain support among UNIX vendors.</P -></LI -><LI -><P ->The mappings of Windows NT RIDs to UNIX ids - is not made algorithmically and depends on the order in which - unmapped users or groups are seen by winbind. It may be difficult - to recover the mappings of rid to UNIX id mapping if the file - containing this information is corrupted or destroyed.</P -></LI -><LI -><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, this is - instead up to the PDC to enforce.</P -></LI -></UL -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN2690" -></A ->14.7. Conclusion</H2 -><P ->The winbind system, through the use of the Name Service - Switch, Pluggable Authentication Modules, and appropriate - Microsoft RPC calls have allowed us to provide seamless - integration of Microsoft Windows NT domain users on a - UNIX system. The result is a great reduction in the administrative - cost of running a mixed UNIX and NT network.</P -></DIV -></DIV -><DIV -CLASS="CHAPTER" -><HR><H1 -><A -NAME="IMPROVED-BROWSING" -></A ->Chapter 15. Improved browsing in samba</H1 -><DIV -CLASS="SECT1" -><H2 -CLASS="SECT1" -><A -NAME="AEN2700" -></A ->15.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="AEN2704" -></A ->15.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="AEN2713" -></A ->15.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="AEN2720" -></A ->15.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="AEN2725" -></A ->15.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="AEN2760" -></A ->15.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="AEN2779" -></A ->15.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="AEN2797" -></A ->15.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="AEN2807" -></A ->15.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="AEN2816" -></A ->15.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="AEN2834" -></A ->15.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="AEN2837" -></A ->15.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="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 ->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 ->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 use the VFS modules, create a share similar to the one below. The -important parameter is the <B -CLASS="COMMAND" ->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" -> [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="AEN2864" -></A ->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 -><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 -></P -></P -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN2874" -></A ->16.2.2. recycle</H3 -><P ->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 ->Supported options: -<P -></P -><DIV -CLASS="VARIABLELIST" -><DL -><DT ->vfs_recycle_bin:repository</DT -><DD -><P ->FIXME</P -></DD -><DT ->vfs_recycle_bin:keeptree</DT -><DD -><P ->FIXME</P -></DD -><DT ->vfs_recycle_bin:versions</DT -><DD -><P ->FIXME</P -></DD -><DT ->vfs_recycle_bin:touch</DT -><DD -><P ->FIXME</P -></DD -><DT ->vfs_recycle_bin:maxsize</DT -><DD -><P ->FIXME</P -></DD -><DT ->vfs_recycle_bin:exclude</DT -><DD -><P ->FIXME</P -></DD -><DT ->vfs_recycle_bin:exclude_dir</DT -><DD -><P ->FIXME</P -></DD -><DT ->vfs_recycle_bin:noversions</DT -><DD -><P ->FIXME</P -></DD -></DL -></DIV -></P -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN2911" -></A ->16.2.3. netatalk</H3 -><P ->A netatalk module, that will ease co-existence of samba and -netatalk file sharing services.</P -><P ->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 -></P -></P -></DIV -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN2918" -></A ->16.3. VFS modules available elsewhere</H2 -><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 ->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 ->By <A -HREF="mailto:elorimer@css.tayloru.edu" -TARGET="_top" ->Eric Lorimer</A ->.</P -><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="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN2930" -></A ->16.3.2. vscan</H3 -><P ->URL: <A -HREF="http://www.openantivirus.org/" -TARGET="_top" ->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 -CLASS="CHAPTER" -><HR><H1 -><A -NAME="CVS-ACCESS" -></A ->Chapter 17. Access Samba source code via CVS</H1 -><DIV -CLASS="SECT1" -><H2 -CLASS="SECT1" -><A -NAME="AEN2942" -></A ->17.1. Introduction</H2 -><P ->Samba is developed in an open environment. Developers use CVS -(Concurrent Versioning System) to "checkin" (also known as -"commit") new source code. Samba's various CVS branches can -be accessed via anonymous CVS using the instructions -detailed in this chapter.</P -><P ->This document is a modified version of the instructions found at -<A -HREF="http://samba.org/samba/cvs.html" -TARGET="_top" ->http://samba.org/samba/cvs.html</A -></P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN2947" -></A ->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, -including samba, rsync and jitterbug. There are two main ways of -accessing the CVS server on this host.</P -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN2950" -></A ->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 -individual files in the repository and also to look at the revision -history and commit logs of individual files. You can also ask for a diff -listing between any two versions on the repository.</P -><P ->Use the URL : <A -HREF="http://samba.org/cgi-bin/cvsweb" -TARGET="_top" ->http://samba.org/cgi-bin/cvsweb</A -></P -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN2955" -></A ->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 -do with the repository and allows you to checkout whole source trees -and keep them up to date via normal cvs commands. This is the -preferred method of access if you are a developer and not -just a casual browser.</P -><P ->To download the latest cvs source code, point your -browser at the URL : <A -HREF="http://www.cyclic.com/" -TARGET="_top" ->http://www.cyclic.com/</A ->. -and click on the 'How to get cvs' link. CVS is free software under -the GNU GPL (as is Samba). Note that there are several graphical CVS clients -which provide a graphical interface to the sometimes mundane CVS commands. -Links to theses clients are also available from http://www.cyclic.com.</P -><P ->To gain access via anonymous cvs use the following steps. -For this example it is assumed that you want a copy of the -samba source code. For the other source code repositories -on this system just substitute the correct package name</P -><P -></P -><OL -TYPE="1" -><LI -><P -> Install a recent copy of cvs. All you really need is a - copy of the cvs client binary. - </P -></LI -><LI -><P -> Run the command - </P -><P -> <B -CLASS="COMMAND" ->cvs -d :pserver:cvs@samba.org:/cvsroot login</B -> - </P -><P -> When it asks you for a password type <TT -CLASS="USERINPUT" -><B ->cvs</B -></TT ->. - </P -></LI -><LI -><P -> Run the command - </P -><P -> <B -CLASS="COMMAND" ->cvs -d :pserver:cvs@samba.org:/cvsroot co samba</B -> - </P -><P -> This will create a directory called samba containing the - latest samba source code (i.e. the HEAD tagged cvs branch). This - currently corresponds to the 3.0 development tree. - </P -><P -> CVS branches other HEAD can be obtained by using the <TT -CLASS="PARAMETER" -><I ->-r</I -></TT -> - and defining a tag name. A list of branch tag names can be found on the - "Development" page of the samba web site. A common request is to obtain the - latest 2.2 release code. This could be done by using the following command. - </P -><P -> <B -CLASS="COMMAND" ->cvs -d :pserver:cvs@samba.org:/cvsroot co -r SAMBA_2_2 samba</B -> - </P -></LI -><LI -><P -> Whenever you want to merge in the latest code changes use - the following command from within the samba directory: - </P -><P -> <B -CLASS="COMMAND" ->cvs update -d -P</B -> - </P -></LI -></OL -></DIV -></DIV -></DIV -><DIV -CLASS="CHAPTER" -><HR><H1 -><A -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 -current method (likely to change) to manage the groups is a new command called -<B -CLASS="COMMAND" ->smbgroupedit</B ->.</P -><P ->The first immediate reason to use the group mapping on a PDC, is that -the <B -CLASS="COMMAND" ->domain admin group</B -> of <TT -CLASS="FILENAME" ->smb.conf</TT -> is -now gone. This parameter was used to give the listed users local admin rights -on their workstations. It was some magic stuff that simply worked but didn't -scale very well for complex setups.</P -><P ->Let me explain how it works on NT/W2K, to have this magic fade away. -When installing NT/W2K on a computer, the installer program creates some users -and groups. Notably the 'Administrators' group, and gives to that group some -privileges like the ability to change the date and time or to kill any process -(or close too) running on the local machine. The 'Administrator' user is a -member of the 'Administrators' group, and thus 'inherit' the 'Administrators' -group privileges. If a 'joe' user is created and become a member of the -'Administrator' group, 'joe' has exactly the same rights as 'Administrator'.</P -><P ->When a NT/W2K machine is joined to a domain, during that phase, the "Domain -Administrators' group of the PDC is added to the 'Administrators' group of the -workstation. Every members of the 'Domain Administrators' group 'inherit' the -rights of the 'Administrators' group when logging on the workstation.</P -><P ->You are now wondering how to make some of your samba PDC users members of the -'Domain Administrators' ? That's really easy.</P -><P -></P -><OL -TYPE="1" -><LI -><P ->create a unix group (usually in <TT -CLASS="FILENAME" ->/etc/group</TT ->), let's call it domadm</P -></LI -><LI -><P ->add to this group the users that must be Administrators. For example if you want joe,john and mary, your entry in <TT -CLASS="FILENAME" ->/etc/group</TT -> will look like:</P -><P -><PRE -CLASS="PROGRAMLISTING" ->domadm:x:502:joe,john,mary</PRE -></P -></LI -><LI -><P ->Map this domadm group to the <B -CLASS="COMMAND" ->domain admins</B -> group by running the command:</P -><P -><B -CLASS="COMMAND" ->smbgroupedit -c "Domain Admins" -u domadm</B -></P -></LI -></OL -><P ->You're set, joe, john and mary are domain administrators !</P -><P ->Like the Domain Admins group, you can map any arbitrary Unix group to any NT -group. You can also make any Unix group a domain group. For example, on a domain -member machine (an NT/W2K or a samba server running winbind), you would like to -give access to a certain directory to some users who are member of a group on -your samba PDC. Flag that group as a domain group by running:</P -><P -><B -CLASS="COMMAND" ->smbgroupedit -a unixgroup -td</B -></P -><P ->You can list the various groups in the mapping database like this</P -><P -><B -CLASS="COMMAND" ->smbgroupedit -v</B -></P -></DIV -><DIV -CLASS="CHAPTER" -><HR><H1 -><A -NAME="SPEED" -></A ->Chapter 19. Samba performance issues</H1 -><DIV -CLASS="SECT1" -><H2 -CLASS="SECT1" -><A -NAME="AEN3033" -></A ->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 -programs that use the same protocol. The most readily available -programs for file transfer that use TCP are ftp or another TCP based -SMB server.</P -><P ->If you want to test against something like a NT or WfWg server then -you will have to disable all but TCP on either the client or -server. Otherwise you may well be using a totally different protocol -(such as Netbeui) and comparisons may not be valid.</P -><P ->Generally you should find that Samba performs similarly to ftp at raw -transfer speed. It should perform quite a bit faster than NFS, -although this very much depends on your system.</P -><P ->Several people have done comparisons between Samba and Novell, NFS or -WinNT. In some cases Samba performed the best, in others the worst. I -suspect the biggest factor is not Samba vs some other system but the -hardware and drivers used on the various systems. Given similar -hardware Samba should certainly be competitive in speed with other -systems.</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN3039" -></A ->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 -><P ->The socket options that Samba uses are settable both on the command -line with the -O option, or in the smb.conf file.</P -><P ->The "socket options" section of the smb.conf manual page describes how -to set these and gives recommendations.</P -><P ->Getting the socket options right can make a big difference to your -performance, but getting them wrong can degrade it by just as -much. The correct settings are very dependent on your local network.</P -><P ->The socket option TCP_NODELAY is the one that seems to make the -biggest single difference for most networks. Many people report that -adding "socket options = TCP_NODELAY" doubles the read performance of -a Samba drive. The best explanation I have seen for this is that the -Microsoft TCP/IP stack is slow in sending tcp ACKs.</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN3046" -></A ->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 -several of the SMB commands (currently SMBwrite, SMBwriteX and -SMBreadbraw) is larger than this value then the server begins writing -the data before it has received the whole packet from the network, or -in the case of SMBreadbraw, it begins writing to the network before -all the data has been read from disk.</P -><P ->This overlapping works best when the speeds of disk and network access -are similar, having very little effect when the speed of one is much -greater than the other.</P -><P ->The default value is 16384, but very little experimentation has been -done yet to determine the optimal value, and it is likely that the best -value will vary greatly between systems anyway. A value over 65536 is -pointless and will cause you to allocate memory unnecessarily.</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN3051" -></A ->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 -maximum size that Samba will negotiate using the "max xmit = " option -in smb.conf. Note that this is the maximum size of SMB request that -Samba will accept, but not the maximum size that the *client* will accept. -The client maximum receive size is sent to Samba by the client and Samba -honours this limit.</P -><P ->It defaults to 65536 bytes (the maximum), but it is possible that some -clients may perform better with a smaller transmit unit. Trying values -of less than 2048 is likely to cause severe problems.</P -><P ->In most cases the default is the best option.</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN3056" -></A ->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 -server flushes the log file after each operation, which can be very -expensive. </P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN3059" -></A ->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, -however. and Samba makes support for "read raw" optional, with it -being enabled by default.</P -><P ->In some cases clients don't handle "read raw" very well and actually -get lower performance using it than they get using the conventional -read operations. </P -><P ->So you might like to try "read raw = no" and see what happens on your -network. It might lower, raise or not affect your performance. Only -testing can really tell.</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN3064" -></A ->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, -however. and Samba makes support for "write raw" optional, with it -being enabled by default.</P -><P ->Some machines may find "write raw" slower than normal write, in which -case you may wish to change this option.</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN3068" -></A ->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 -><P ->I suspect that his PC's (386sx16 based) were asking for more data than -they could chew. I suspect a similar speed could be had by setting -"read raw = no" and "max xmit = 2048", instead of changing the -protocol. Lowering the "read size" might also help.</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN3072" -></A ->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 -could also enable the "UFC crypt" option in the Makefile.</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN3075" -></A ->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 -performance.</P -><P ->See your client docs for details. In particular, I have heard rumours -that the WfWg options TCPWINDOWSIZE and TCPSEGMENTSIZE can have a -large impact on performance.</P -><P ->Also note that some people have found that setting DefaultRcvWindow in -the [MSTCP] section of the SYSTEM.INI file under WfWg to 3072 gives a -big improvement. I don't know why.</P -><P ->My own experience wth DefaultRcvWindow is that I get much better -performance with a large value (16384 or larger). Other people have -reported that anything over 3072 slows things down enourmously. One -person even reported a speed drop of a factor of 30 when he went from -3072 to 8192. I don't know why.</P -><P ->It probably depends a lot on your hardware, and the type of unix box -you have at the other end of the link.</P -><P ->Paul Cochrane has done some testing on client side tuning and come -to the following conclusions:</P -><P ->Install the W2setup.exe file from www.microsoft.com. This is an -update for the winsock stack and utilities which improve performance.</P -><P ->Configure the win95 TCPIP registry settings to give better -perfomance. I use a program called MTUSPEED.exe which I got off the -net. There are various other utilities of this type freely available. -The setting which give the best performance for me are:</P -><P -></P -><OL -TYPE="1" -><LI -><P ->MaxMTU Remove</P -></LI -><LI -><P ->RWIN Remove</P -></LI -><LI -><P ->MTUAutoDiscover Disable</P -></LI -><LI -><P ->MTUBlackHoleDetect Disable</P -></LI -><LI -><P ->Time To Live Enabled</P -></LI -><LI -><P ->Time To Live - HOPS 32</P -></LI -><LI -><P ->NDI Cache Size 0</P -></LI -></OL -><P ->I tried virtually all of the items mentioned in the document and -the only one which made a difference to me was the socket options. It -turned out I was better off without any!!!!!</P -><P ->In terms of overall speed of transfer, between various win95 clients -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 -><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</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 -running on. It's a crap machine!!!!</P -><P ->The updates mentioned in 1 and 2 brought up the transfer rates from -just over 100kB/s in some clients.</P -><P ->A new client is a P333 connected via a 100MB/s card and hub. The -transfer rates from this were good: 450-500kB/s on put and 600+kB/s -on get.</P -><P ->Looking at standard FTP throughput, Samba is a bit slower (100kB/s -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="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 ->20.2.3. moveuser.exe</H3 -><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 ->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" -><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="APPENDIXES" -></A -><DIV -CLASS="TITLEPAGE" -><H1 -CLASS="TITLE" ->IV. Appendixes</H1 -><DIV -CLASS="TOC" -><DL -><DT -><B ->Table of Contents</B -></DT -><DT ->21. <A -HREF="#PORTABILITY" ->Portability</A -></DT -><DD -><DL -><DT ->21.1. <A -HREF="#AEN3251" ->HPUX</A -></DT -><DT ->21.2. <A -HREF="#AEN3257" ->SCO Unix</A -></DT -><DT ->21.3. <A -HREF="#AEN3261" ->DNIX</A -></DT -><DT ->21.4. <A -HREF="#AEN3290" ->RedHat Linux Rembrandt-II</A -></DT -></DL -></DD -><DT ->22. <A -HREF="#OTHER-CLIENTS" ->Samba and other CIFS clients</A -></DT -><DD -><DL -><DT ->22.1. <A -HREF="#AEN3311" ->Macintosh clients?</A -></DT -><DT ->22.2. <A -HREF="#AEN3320" ->OS2 Client</A -></DT -><DD -><DL -><DT ->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 ->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 ->22.2.3. <A -HREF="#AEN3346" ->Are there any other issues when OS/2 (any version) - is used as a client?</A -></DT -><DT ->22.2.4. <A -HREF="#AEN3350" ->How do I get printer driver download working - for OS/2 clients?</A -></DT -></DL -></DD -><DT ->22.3. <A -HREF="#AEN3360" ->Windows for Workgroups</A -></DT -><DD -><DL -><DT ->22.3.1. <A -HREF="#AEN3362" ->Use latest TCP/IP stack from Microsoft</A -></DT -><DT ->22.3.2. <A -HREF="#AEN3367" ->Delete .pwl files after password change</A -></DT -><DT ->22.3.3. <A -HREF="#AEN3372" ->Configure WfW password handling</A -></DT -><DT ->22.3.4. <A -HREF="#AEN3376" ->Case handling of passwords</A -></DT -></DL -></DD -><DT ->22.4. <A -HREF="#AEN3381" ->Windows '95/'98</A -></DT -><DT ->22.5. <A -HREF="#AEN3397" ->Windows 2000 Service Pack 2</A -></DT -></DL -></DD -><DT ->23. <A -HREF="#BUGREPORT" ->Reporting Bugs</A -></DT -><DD -><DL -><DT ->23.1. <A -HREF="#AEN3421" ->Introduction</A -></DT -><DT ->23.2. <A -HREF="#AEN3431" ->General info</A -></DT -><DT ->23.3. <A -HREF="#AEN3437" ->Debug levels</A -></DT -><DT ->23.4. <A -HREF="#AEN3454" ->Internal errors</A -></DT -><DT ->23.5. <A -HREF="#AEN3464" ->Attaching to a running process</A -></DT -><DT ->23.6. <A -HREF="#AEN3467" ->Patches</A -></DT -></DL -></DD -><DT ->24. <A -HREF="#DIAGNOSIS" ->Diagnosing your samba server</A -></DT -><DD -><DL -><DT ->24.1. <A -HREF="#AEN3490" ->Introduction</A -></DT -><DT ->24.2. <A -HREF="#AEN3495" ->Assumptions</A -></DT -><DT ->24.3. <A -HREF="#AEN3505" ->Tests</A -></DT -><DD -><DL -><DT ->24.3.1. <A -HREF="#AEN3507" ->Test 1</A -></DT -><DT ->24.3.2. <A -HREF="#AEN3513" ->Test 2</A -></DT -><DT ->24.3.3. <A -HREF="#AEN3519" ->Test 3</A -></DT -><DT ->24.3.4. <A -HREF="#AEN3534" ->Test 4</A -></DT -><DT ->24.3.5. <A -HREF="#AEN3539" ->Test 5</A -></DT -><DT ->24.3.6. <A -HREF="#AEN3545" ->Test 6</A -></DT -><DT ->24.3.7. <A -HREF="#AEN3553" ->Test 7</A -></DT -><DT ->24.3.8. <A -HREF="#AEN3579" ->Test 8</A -></DT -><DT ->24.3.9. <A -HREF="#AEN3596" ->Test 9</A -></DT -><DT ->24.3.10. <A -HREF="#AEN3604" ->Test 10</A -></DT -><DT ->24.3.11. <A -HREF="#AEN3610" ->Test 11</A -></DT -></DL -></DD -><DT ->24.4. <A -HREF="#AEN3615" ->Still having troubles?</A -></DT -></DL -></DD -></DL -></DIV -></DIV -><DIV -CLASS="CHAPTER" -><HR><H1 -><A -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 -platform-specific information about compiling and using samba.</P -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN3251" -></A ->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 -/etc/logingroup; the system maps UIDs to numbers using the former, but -initgroups() reads the latter. Most system admins who know the ropes -symlink /etc/group to /etc/logingroup (hard link doesn't work for reasons -too stupid to go into here). initgroups() will complain if one of the -groups you're in in /etc/logingroup has what it considers to be an invalid -ID, which means outside the range [0..UID_MAX], where UID_MAX is (I think) -60000 currently on HP-UX. This precludes -2 and 65534, the usual 'nobody' -GIDs.</P -><P ->If you encounter this problem, make sure that the programs that are failing -to initgroups() be run as users not in any groups with GIDs outside the -allowed range.</P -><P ->This is documented in the HP manual pages under setgroups(2) and passwd(4).</P -><P ->On HPUX you must use gcc or the HP Ansi compiler. The free compiler -that comes with HP-UX is not Ansi compliant and cannot compile -Samba.</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN3257" -></A ->21.2. SCO Unix</H2 -><P -> -If you run an old version of SCO Unix then you may need to get important -TCP/IP patches for Samba to work correctly. Without the patch, you may -encounter corrupt data transfers using samba.</P -><P ->The patch you need is UOD385 Connection Drivers SLS. It is available from -SCO (ftp.sco.com, directory SLS, files uod385a.Z and uod385a.ltr.Z).</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN3261" -></A ->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 -C library for some reason.</P -><P ->For this reason Samba by default defines the macro NO_EID in the DNIX -section of includes.h. This works around the problem in a limited way, -but it is far from ideal, some things still won't work right.</P -><P -> -To fix the problem properly you need to assemble the following two -functions and then either add them to your C library or link them into -Samba.</P -><P -> -put this in the file <TT -CLASS="FILENAME" ->setegid.s</TT ->:</P -><P -><PRE -CLASS="PROGRAMLISTING" -> .globl _setegid -_setegid: - moveq #47,d0 - movl #100,a0 - moveq #1,d1 - movl 4(sp),a1 - trap #9 - bccs 1$ - jmp cerror -1$: - clrl d0 - rts</PRE -></P -><P ->put this in the file <TT -CLASS="FILENAME" ->seteuid.s</TT ->:</P -><P -><PRE -CLASS="PROGRAMLISTING" -> .globl _seteuid -_seteuid: - moveq #47,d0 - movl #100,a0 - moveq #0,d1 - movl 4(sp),a1 - trap #9 - bccs 1$ - jmp cerror -1$: - clrl d0 - rts</PRE -></P -><P ->after creating the above files you then assemble them using</P -><P -><B -CLASS="COMMAND" ->as seteuid.s</B -></P -><P -><B -CLASS="COMMAND" ->as setegid.s</B -></P -><P ->that should produce the files <TT -CLASS="FILENAME" ->seteuid.o</TT -> and -<TT -CLASS="FILENAME" ->setegid.o</TT -></P -><P ->then you need to add these to the LIBSM line in the DNIX section of -the Samba Makefile. Your LIBSM line will then look something like this:</P -><P -><PRE -CLASS="PROGRAMLISTING" ->LIBSM = setegid.o seteuid.o -ln</PRE -></P -><P -> -You should then remove the line:</P -><P -><PRE -CLASS="PROGRAMLISTING" ->#define NO_EID</PRE -></P -><P ->from the DNIX section of <TT -CLASS="FILENAME" ->includes.h</TT -></P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN3290" -></A ->21.4. RedHat Linux Rembrandt-II</H2 -><P ->By default RedHat Rembrandt-II during installation adds an -entry to /etc/hosts as follows: -<PRE -CLASS="PROGRAMLISTING" -> 127.0.0.1 loopback "hostname"."domainname"</PRE -></P -><P ->This causes Samba to loop back onto the loopback interface. -The result is that Samba fails to communicate correctly with -the world and therefor may fail to correctly negotiate who -is the master browse list holder and who is the master browser.</P -><P ->Corrective Action: Delete the entry after the word loopback - in the line starting 127.0.0.1</P -></DIV -></DIV -><DIV -CLASS="CHAPTER" -><HR><H1 -><A -NAME="OTHER-CLIENTS" -></A ->Chapter 22. Samba and other CIFS clients</H1 -><P ->This chapter contains client-specific information.</P -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN3311" -></A ->22.1. Macintosh clients?</H2 -><P ->Yes. <A -HREF="http://www.thursby.com/" -TARGET="_top" ->Thursby</A -> now have a CIFS Client / Server called DAVE - see</P -><P ->They test it against Windows 95, Windows NT and samba for -compatibility issues. At the time of writing, DAVE was at version -1.0.1. The 1.0.0 to 1.0.1 update is available as a free download from -the Thursby web site (the speed of finder copies has been greatly -enhanced, and there are bug-fixes included).</P -><P -> -Alternatives - There are two free implementations of AppleTalk for -several kinds of UNIX machnes, and several more commercial ones. -These products allow you to run file services and print services -natively to Macintosh users, with no additional support required on -the Macintosh. The two free omplementations are -<A -HREF="http://www.umich.edu/~rsug/netatalk/" -TARGET="_top" ->Netatalk</A ->, and -<A -HREF="http://www.cs.mu.oz.au/appletalk/atalk.html" -TARGET="_top" ->CAP</A ->. -What Samba offers MS -Windows users, these packages offer to Macs. For more info on these -packages, Samba, and Linux (and other UNIX-based systems) see -<A -HREF="http://www.eats.com/linux_mac_win.html" -TARGET="_top" ->http://www.eats.com/linux_mac_win.html</A -></P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN3320" -></A ->22.2. OS2 Client</H2 -><DIV -CLASS="SECT2" -><H3 -CLASS="SECT2" -><A -NAME="AEN3322" -></A ->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 - found on <A -HREF="http://carol.wins.uva.nl/~leeuw/samba/warp.html" -TARGET="_top" -> http://carol.wins.uva.nl/~leeuw/samba/warp.html</A ->.</P -><P ->Basically, you need three components:</P -><P -></P -><UL -><LI -><P ->The File and Print Client ('IBM Peer') - </P -></LI -><LI -><P ->TCP/IP ('Internet support') - </P -></LI -><LI -><P ->The "NetBIOS over TCP/IP" driver ('TCPBEUI') - </P -></LI -></UL -><P ->Installing the first two together with the base operating - system on a blank system is explained in the Warp manual. If Warp - has already been installed, but you now want to install the - networking support, use the "Selective Install for Networking" - object in the "System Setup" folder.</P -><P ->Adding the "NetBIOS over TCP/IP" driver is not described - in the manual and just barely in the online documentation. Start - MPTS.EXE, click on OK, click on "Configure LAPS" and click - on "IBM OS/2 NETBIOS OVER TCP/IP" in 'Protocols'. This line - is then moved to 'Current Configuration'. Select that line, - click on "Change number" and increase it from 0 to 1. Save this - configuration.</P -><P ->If the Samba server(s) is not on your local subnet, you - can optionally add IP names and addresses of these servers - to the "Names List", or specify a WINS server ('NetBIOS - Nameserver' in IBM and RFC terminology). For Warp Connect you - may need to download an update for 'IBM Peer' to bring it on - the same level as Warp 4. See the webpage mentioned above.</P -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -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?</H3 -><P ->You can use the free Microsoft LAN Manager 2.2c Client - for OS/2 from - <A -HREF="ftp://ftp.microsoft.com/BusSys/Clients/LANMAN.OS2/" -TARGET="_top" -> ftp://ftp.microsoft.com/BusSys/Clients/LANMAN.OS2/</A ->. - See <A -HREF="http://carol.wins.uva.nl/~leeuw/lanman.html" -TARGET="_top" -> http://carol.wins.uva.nl/~leeuw/lanman.html</A -> for - more information on how to install and use this client. In - a nutshell, edit the file \OS2VER in the root directory of - the OS/2 boot partition and add the lines:</P -><P -><PRE -CLASS="PROGRAMLISTING" -> 20=setup.exe - 20=netwksta.sys - 20=netvdd.sys - </PRE -></P -><P ->before you install the client. Also, don't use the - included NE2000 driver because it is buggy. Try the NE2000 - or NS2000 driver from - <A -HREF="ftp://ftp.cdrom.com/pub/os2/network/ndis/" -TARGET="_top" -> ftp://ftp.cdrom.com/pub/os2/network/ndis/</A -> instead. - </P -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN3346" -></A ->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 - Client Resource Browser", no Samba servers show up. This can - be fixed by a patch from <A -HREF="http://carol.wins.uva.nl/~leeuw/samba/fix.html" -TARGET="_top" -> http://carol.wins.uva.nl/~leeuw/samba/fix.html</A ->. - The patch will be included in a later version of Samba. It also - fixes a couple of other problems, such as preserving long - filenames when objects are dragged from the Workplace Shell - to the Samba server. </P -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN3350" -></A ->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 - world-readable. Copy your OS/2 driver files there. Note - that the .EA_ files must still be separate, so you will need - to use the original install files, and not copy an installed - driver from an OS/2 system.</P -><P ->Install the NT driver first for that printer. Then, - add to your smb.conf a parameter, os2 driver map = - <TT -CLASS="REPLACEABLE" -><I ->filename</I -></TT ->". Then, in the file - specified by <TT -CLASS="REPLACEABLE" -><I ->filename</I -></TT ->, map the - name of the NT driver name to the OS/2 driver name as - follows:</P -><P -><B -CLASS="COMMAND" ->nt driver name = os2 "driver - name"."device name"</B ->, e.g.: - HP LaserJet 5L = LASERJET.HP LaserJet 5L</P -><P ->You can have multiple drivers mapped in this file.</P -><P ->If you only specify the OS/2 driver name, and not the - device name, the first attempt to download the driver will - actually download the files, but the OS/2 client will tell - you the driver is not available. On the second attempt, it - will work. This is fixed simply by adding the device name - to the mapping, after which it will work on the first attempt. - </P -></DIV -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN3360" -></A ->22.3. Windows for Workgroups</H2 -><DIV -CLASS="SECT2" -><H3 -CLASS="SECT2" -><A -NAME="AEN3362" -></A ->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 -><P ->The early TCP/IP stacks had lots of bugs.</P -><P -> -Microsoft has released an incremental upgrade to their TCP/IP 32-Bit -VxD drivers. The latest release can be found on their ftp site at -ftp.microsoft.com, located in /peropsys/windows/public/tcpip/wfwt32.exe. -There is an update.txt file there that describes the problems that were -fixed. New files include WINSOCK.DLL, TELNET.EXE, WSOCK.386, VNBT.386, -WSTCP.386, TRACERT.EXE, NETSTAT.EXE, and NBTSTAT.EXE.</P -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN3367" -></A ->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 -delete the .pwl files in the windows directory. The PC will complain about not finding the files, but will soon get over it, allowing you to enter the new password.</P -><P -> -If you don't do this you may find that WfWg remembers and uses the old -password, even if you told it a new one.</P -><P -> -Often WfWg will totally ignore a password you give it in a dialog box.</P -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN3372" -></A ->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 -type EXPAND A:\ADMINCFG.EX_ C:\WINDOWS\ADMINCFG.EXE Then add an icon -for it via the "Progam Manager" "New" Menu. This program allows you -to control how WFW handles passwords. ie disable Password Caching etc -for use with <B -CLASS="COMMAND" ->security = user</B -></P -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN3376" -></A ->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" -TARGET="_top" ->smb.conf(5)</A -> information on <B -CLASS="COMMAND" ->password level</B -> to specify what characters samba should try to uppercase when checking.</P -></DIV -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN3381" -></A ->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 -updates have been installed.</P -><P -> -There are more updates than the ones mentioned here. You are referred to the -Microsoft Web site for all currently available updates to your specific version -of Windows 95.</P -><P -></P -><OL -TYPE="1" -><LI -><P ->Kernel Update: KRNLUPD.EXE</P -></LI -><LI -><P ->Ping Fix: PINGUPD.EXE</P -></LI -><LI -><P ->RPC Update: RPCRTUPD.EXE</P -></LI -><LI -><P ->TCP/IP Update: VIPUPD.EXE</P -></LI -><LI -><P ->Redirector Update: VRDRUPD.EXE</P -></LI -></OL -><P ->Also, if using MS OutLook it is desirable to install the OLEUPD.EXE fix. This -fix may stop your machine from hanging for an extended period when exiting -OutLook and you may also notice a significant speedup when accessing network -neighborhood services.</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN3397" -></A ->22.5. Windows 2000 Service Pack 2</H2 -><P -> -There are several annoyances with Windows 2000 SP2. One of which -only appears when using a Samba server to host user profiles -to Windows 2000 SP2 clients in a Windows domain. This assumes -that Samba is a member of the domain, but the problem will -likely occur if it is not.</P -><P -> -In order to server profiles successfully to Windows 2000 SP2 -clients (when not operating as a PDC), Samba must have -<B -CLASS="COMMAND" ->nt acl support = no</B -> -added to the file share which houses the roaming profiles. -If this is not done, then the Windows 2000 SP2 client will -complain about not being able to access the profile (Access -Denied) and create multiple copies of it on disk (DOMAIN.user.001, -DOMAIN.user.002, etc...). See the -<A -HREF="smb.conf.5.html" -TARGET="_top" ->smb.conf(5)</A -> man page -for more details on this option. Also note that the -<B -CLASS="COMMAND" ->nt acl support</B -> parameter was formally a global parameter in -releases prior to Samba 2.2.2.</P -><P -> -The following is a minimal profile share:</P -><P -><PRE -CLASS="PROGRAMLISTING" -> [profile] - path = /export/profile - create mask = 0600 - directory mask = 0700 - nt acl support = no - read only = no</PRE -></P -><P ->The reason for this bug is that the Win2k SP2 client copies -the security descriptor for the profile which contains -the Samba server's SID, and not the domain SID. The client -compares the SID for SAMBA\user and realizes it is -different that the one assigned to DOMAIN\user. Hence the reason -for the "access denied" message.</P -><P ->By disabling the <B -CLASS="COMMAND" ->nt acl support</B -> parameter, Samba will send -the Win2k client a response to the QuerySecurityDescriptor -trans2 call which causes the client to set a default ACL -for the profile. This default ACL includes </P -><P -><B -CLASS="COMMAND" ->DOMAIN\user "Full Control"</B -></P -><P -><SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->NOTE : This bug does not occur when using winbind to -create accounts on the Samba host for Domain users.</I -></SPAN -></P -></DIV -></DIV -><DIV -CLASS="CHAPTER" -><HR><H1 -><A -NAME="BUGREPORT" -></A ->Chapter 23. Reporting Bugs</H1 -><DIV -CLASS="SECT1" -><H2 -CLASS="SECT1" -><A -NAME="AEN3421" -></A ->23.1. Introduction</H2 -><P ->The email address for bug reports for stable releases is <A -HREF="samba@samba.org" -TARGET="_top" ->samba@samba.org</A ->. -Bug reports for alpha releases should go to <A -HREF="mailto:samba-technical@samba.org" -TARGET="_top" ->samba-technical@samba.org</A ->.</P -><P ->Please take the time to read this file before you submit a bug -report. Also, please see if it has changed between releases, as we -may be changing the bug reporting mechanism at some time.</P -><P ->Please also do as much as you can yourself to help track down the -bug. Samba is maintained by a dedicated group of people who volunteer -their time, skills and efforts. We receive far more mail about it than -we can possibly answer, so you have a much higher chance of an answer -and a fix if you send us a "developer friendly" bug report that lets -us fix it fast. </P -><P ->Do not assume that if you post the bug to the comp.protocols.smb -newsgroup or the mailing list that we will read it. If you suspect that your -problem is not a bug but a configuration problem then it is better to send -it to the Samba mailing list, as there are (at last count) 5000 other users on -that list that may be able to help you.</P -><P ->You may also like to look though the recent mailing list archives, -which are conveniently accessible on the Samba web pages -at <A -HREF="http://samba.org/samba/" -TARGET="_top" ->http://samba.org/samba/</A ->.</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN3431" -></A ->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 -you've misconfigured something and run testparm to test your config -file for correct syntax.</P -><P ->Have you run through the <A -HREF="Diagnosis.html" -TARGET="_top" ->diagnosis</A ->? -This is very important.</P -><P ->If you include part of a log file with your bug report then be sure to -annotate it with exactly what you were doing on the client at the -time, and exactly what the results were.</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN3437" -></A ->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 -be very useful. Depending on the problem a log level of between 3 and -10 showing the problem may be appropriate. A higher level givesmore -detail, but may use too much disk space.</P -><P ->To set the debug level use <B -CLASS="COMMAND" ->log level =</B -> in your -<TT -CLASS="FILENAME" ->smb.conf</TT ->. You may also find it useful to set the log -level higher for just one machine and keep separate logs for each machine. -To do this use:</P -><P -><PRE -CLASS="PROGRAMLISTING" ->log level = 10 -log file = /usr/local/samba/lib/log.%m -include = /usr/local/samba/lib/smb.conf.%m</PRE -></P -><P ->then create a file -<TT -CLASS="FILENAME" ->/usr/local/samba/lib/smb.conf.machine</TT -> where -"machine" is the name of the client you wish to debug. In that file -put any smb.conf commands you want, for example -<B -CLASS="COMMAND" ->log level=</B -> may be useful. This also allows you to -experiment with different security systems, protocol levels etc on just -one machine.</P -><P ->The <TT -CLASS="FILENAME" ->smb.conf</TT -> entry <B -CLASS="COMMAND" ->log level =</B -> -is synonymous with the entry <B -CLASS="COMMAND" ->debuglevel =</B -> that has been -used in older versions of Samba and is being retained for backwards -compatibility of smb.conf files.</P -><P ->As the <B -CLASS="COMMAND" ->log level =</B -> value is increased you will record -a significantly increasing level of debugging information. For most -debugging operations you may not need a setting higher than 3. Nearly -all bugs can be tracked at a setting of 10, but be prepared for a VERY -large volume of log data.</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN3454" -></A ->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 -segmentation fault and almost certainly means a bug in Samba (unless -you have faulty hardware or system software)</P -><P ->If the message came from smbd then it will probably be accompanied by -a message which details the last SMB message received by smbd. This -info is often very useful in tracking down the problem so please -include it in your bug report.</P -><P ->You should also detail how to reproduce the problem, if -possible. Please make this reasonably detailed.</P -><P ->You may also find that a core file appeared in a "corefiles" -subdirectory of the directory where you keep your samba log -files. This file is the most useful tool for tracking down the bug. To -use it you do this:</P -><P -><B -CLASS="COMMAND" ->gdb smbd core</B -></P -><P ->adding appropriate paths to smbd and core so gdb can find them. If you -don't have gdb then try "dbx". Then within the debugger use the -command "where" to give a stack trace of where the problem -occurred. Include this in your mail.</P -><P ->If you known any assembly language then do a "disass" of the routine -where the problem occurred (if its in a library routine then -disassemble the routine that called it) and try to work out exactly -where the problem is by looking at the surrounding code. Even if you -don't know assembly then incuding this info in the bug report can be -useful. </P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN3464" -></A ->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 -does often). To debug with this sort of system you could try to attach -to the running process using "gdb smbd PID" where you get PID from -smbstatus. Then use "c" to continue and try to cause the core dump -using the client. The debugger should catch the fault and tell you -where it occurred.</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN3467" -></A ->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 -CLASS="COMMAND" ->diff -u</B -> format if your version of -diff supports it, otherwise use <B -CLASS="COMMAND" ->diff -c4</B ->. Make sure -your do the diff against a clean version of the source and let me know -exactly what version you used. </P -></DIV -></DIV -><DIV -CLASS="CHAPTER" -><HR><H1 -><A -NAME="DIAGNOSIS" -></A ->Chapter 24. Diagnosing your samba server</H1 -><DIV -CLASS="SECT1" -><H2 -CLASS="SECT1" -><A -NAME="AEN3490" -></A ->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 -is if it fails any one of these steps. If it passes all these tests -then it is probably working fine.</P -><P ->You should do ALL the tests, in the order shown. We have tried to -carefully choose them so later tests only use capabilities verified in -the earlier tests.</P -><P ->If you send one of the samba mailing lists an email saying "it doesn't work" -and you have not followed this test procedure then you should not be surprised -your email is ignored.</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN3495" -></A ->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 -><P ->The procedure is similar for other types of clients.</P -><P ->It is also assumed you know the name of an available share in your -smb.conf. I will assume this share is called "tmp". You can add a -"tmp" share like by adding the following to smb.conf:</P -><P -><PRE -CLASS="PROGRAMLISTING" -> [tmp] - comment = temporary files - path = /tmp - read only = yes </PRE -></P -><P ->THESE TESTS ASSUME VERSION 3.0.0 OR LATER OF THE SAMBA SUITE. SOME -COMMANDS SHOWN DID NOT EXIST IN EARLIER VERSIONS</P -><P ->Please pay attention to the error messages you receive. If any error message -reports that your server is being unfriendly you should first check that you -IP name resolution is correctly set up. eg: Make sure your /etc/resolv.conf -file points to name servers that really do exist.</P -><P ->Also, if you do not have DNS server access for name resolution please check -that the settings for your smb.conf file results in "dns proxy = no". The -best way to check this is with "testparm smb.conf"</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN3505" -></A ->24.3. Tests</H2 -><DIV -CLASS="SECT2" -><H3 -CLASS="SECT2" -><A -NAME="AEN3507" -></A ->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 -configuration file is faulty.</P -><P ->Note: Your smb.conf file may be located in: <TT -CLASS="FILENAME" ->/etc/samba</TT -> - Or in: <TT -CLASS="FILENAME" ->/usr/local/samba/lib</TT -></P -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN3513" -></A ->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 -software is not correctly installed. </P -><P ->Note that you will need to start a "dos prompt" window on the PC to -run ping.</P -><P ->If you get a message saying "host not found" or similar then your DNS -software or /etc/hosts file is not correctly setup. It is possible to -run samba without DNS entries for the server and client, but I assume -you do have correct entries for the remainder of these tests. </P -><P ->Another reason why ping might fail is if your host is running firewall -software. You will need to relax the rules to let in the workstation -in question, perhaps by allowing access from another subnet (on Linux -this is done via the ipfwadm program.)</P -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN3519" -></A ->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 -><P ->If you get a error message containing the string "Bad password" then -you probably have either an incorrect "hosts allow", "hosts deny" or -"valid users" line in your smb.conf, or your guest account is not -valid. Check what your guest account is using "testparm" and -temporarily remove any "hosts allow", "hosts deny", "valid users" or -"invalid users" lines.</P -><P ->If you get a "connection refused" response then the smbd server may -not be running. If you installed it in inetd.conf then you probably edited -that file incorrectly. If you installed it as a daemon then check that -it is running, and check that the netbios-ssn port is in a LISTEN -state using "netstat -a".</P -><P ->If you get a "session request failed" then the server refused the -connection. If it says "Your server software is being unfriendly" then -its probably because you have invalid command line parameters to smbd, -or a similar fatal problem with the initial startup of smbd. Also -check your config file (smb.conf) for syntax errors with "testparm" -and that the various directories where samba keeps its log and lock -files exist.</P -><P ->There are a number of reasons for which smbd may refuse or decline -a session request. The most common of these involve one or more of -the following smb.conf file entries:</P -><P -><PRE -CLASS="PROGRAMLISTING" -> hosts deny = ALL - hosts allow = xxx.xxx.xxx.xxx/yy - bind interfaces only = Yes</PRE -></P -><P ->In the above, no allowance has been made for any session requests that -will automatically translate to the loopback adaptor address 127.0.0.1. -To solve this problem change these lines to:</P -><P -><PRE -CLASS="PROGRAMLISTING" -> hosts deny = ALL - hosts allow = xxx.xxx.xxx.xxx/yy 127.</PRE -></P -><P ->Do NOT use the "bind interfaces only" parameter where you may wish to -use the samba password change facility, or where smbclient may need to -access local service for name resolution or for local resource -connections. (Note: the "bind interfaces only" parameter deficiency -where it will not allow connections to the loopback address will be -fixed soon).</P -><P ->Another common cause of these two errors is having something already running -on port 139, such as Samba (ie: smbd is running from inetd already) or -something like Digital's Pathworks. Check your inetd.conf file before trying -to start smbd as a daemon, it can avoid a lot of frustration!</P -><P ->And yet another possible cause for failure of TEST 3 is when the subnet mask -and / or broadcast address settings are incorrect. Please check that the -network interface IP Address / Broadcast Address / Subnet Mask settings are -correct and that Samba has correctly noted these in the log.nmb file.</P -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN3534" -></A ->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 -><P ->If you don't then nmbd is incorrectly installed. Check your inetd.conf -if you run it from there, or that the daemon is running and listening -to udp port 137.</P -><P ->One common problem is that many inetd implementations can't take many -parameters on the command line. If this is the case then create a -one-line script that contains the right parameters and run that from -inetd.</P -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN3539" -></A ->24.3.5. Test 5</H3 -><P ->run the command <B -CLASS="COMMAND" ->nmblookup -B ACLIENT '*'</B -></P -><P ->You should get the PCs IP address back. If you don't then the client -software on the PC isn't installed correctly, or isn't started, or you -got the name of the PC wrong. </P -><P ->If ACLIENT doesn't resolve via DNS then use the IP address of the -client in the above test.</P -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN3545" -></A ->24.3.6. Test 6</H3 -><P ->Run the command <B -CLASS="COMMAND" ->nmblookup -d 2 '*'</B -></P -><P ->This time we are trying the same as the previous test but are trying -it via a broadcast to the default broadcast address. A number of -Netbios/TCPIP hosts on the network should respond, although Samba may -not catch all of the responses in the short time it listens. You -should see "got a positive name query response" messages from several -hosts.</P -><P ->If this doesn't give a similar result to the previous test then -nmblookup isn't correctly getting your broadcast address through its -automatic mechanism. In this case you should experiment use the -"interfaces" option in smb.conf to manually configure your IP -address, broadcast and netmask. </P -><P ->If your PC and server aren't on the same subnet then you will need to -use the -B option to set the broadcast address to the that of the PCs -subnet.</P -><P ->This test will probably fail if your subnet mask and broadcast address are -not correct. (Refer to TEST 3 notes above).</P -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN3553" -></A ->24.3.7. Test 7</H3 -><P ->Run the command <B -CLASS="COMMAND" ->smbclient //BIGSERVER/TMP</B ->. You should -then be prompted for a password. You should use the password of the account -you are logged into the unix box with. If you want to test with -another account then add the -U >accountname< option to the end of -the command line. eg: -<B -CLASS="COMMAND" ->smbclient //bigserver/tmp -Ujohndoe</B -></P -><P ->Note: It is possible to specify the password along with the username -as follows: -<B -CLASS="COMMAND" ->smbclient //bigserver/tmp -Ujohndoe%secret</B -></P -><P ->Once you enter the password you should get the "smb>" prompt. If you -don't then look at the error message. If it says "invalid network -name" then the service "tmp" is not correctly setup in your smb.conf.</P -><P ->If it says "bad password" then the likely causes are:</P -><P -></P -><OL -TYPE="1" -><LI -><P -> you have shadow passords (or some other password system) but didn't - compile in support for them in smbd - </P -></LI -><LI -><P -> your "valid users" configuration is incorrect - </P -></LI -><LI -><P -> you have a mixed case password and you haven't enabled the "password - level" option at a high enough level - </P -></LI -><LI -><P -> the "path =" line in smb.conf is incorrect. Check it with testparm - </P -></LI -><LI -><P -> you enabled password encryption but didn't create the SMB encrypted - password file - </P -></LI -></OL -><P ->Once connected you should be able to use the commands -<B -CLASS="COMMAND" ->dir</B -> <B -CLASS="COMMAND" ->get</B -> <B -CLASS="COMMAND" ->put</B -> etc. -Type <B -CLASS="COMMAND" ->help >command<</B -> for instructions. You should -especially check that the amount of free disk space shown is correct -when you type <B -CLASS="COMMAND" ->dir</B ->.</P -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN3579" -></A ->24.3.8. Test 8</H3 -><P ->On the PC type the command <B -CLASS="COMMAND" ->net view \\BIGSERVER</B ->. You will -need to do this from within a "dos prompt" window. You should get back a -list of available shares on the server.</P -><P ->If you get a "network name not found" or similar error then netbios -name resolution is not working. This is usually caused by a problem in -nmbd. To overcome it you could do one of the following (you only need -to choose one of them):</P -><P -></P -><OL -TYPE="1" -><LI -><P -> fixup the nmbd installation</P -></LI -><LI -><P -> add the IP address of BIGSERVER to the "wins server" box in the - advanced tcp/ip setup on the PC.</P -></LI -><LI -><P -> enable windows name resolution via DNS in the advanced section of - the tcp/ip setup</P -></LI -><LI -><P -> add BIGSERVER to your lmhosts file on the PC.</P -></LI -></OL -><P ->If you get a "invalid network name" or "bad password error" then the -same fixes apply as they did for the "smbclient -L" test above. In -particular, make sure your "hosts allow" line is correct (see the man -pages)</P -><P ->Also, do not overlook that fact that when the workstation requests the -connection to the samba server it will attempt to connect using the -name with which you logged onto your Windows machine. You need to make -sure that an account exists on your Samba server with that exact same -name and password.</P -><P ->If you get "specified computer is not receiving requests" or similar -it probably means that the host is not contactable via tcp services. -Check to see if the host is running tcp wrappers, and if so add an entry in -the hosts.allow file for your client (or subnet, etc.)</P -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN3596" -></A ->24.3.9. Test 9</H3 -><P ->Run the command <B -CLASS="COMMAND" ->net use x: \\BIGSERVER\TMP</B ->. You should -be prompted for a password then you should get a "command completed -successfully" message. If not then your PC software is incorrectly -installed or your smb.conf is incorrect. make sure your "hosts allow" -and other config lines in smb.conf are correct.</P -><P ->It's also possible that the server can't work out what user name to -connect you as. To see if this is the problem add the line "user = -USERNAME" to the [tmp] section of smb.conf where "USERNAME" is the -username corresponding to the password you typed. If you find this -fixes things you may need the username mapping option. </P -><P ->It might also be the case that your client only sends encrypted passwords -and you have <B -CLASS="COMMAND" ->encrypt passwords = no</B -> in <TT -CLASS="FILENAME" ->smb.conf</TT ->. -Turn it back on to fix.</P -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN3604" -></A ->24.3.10. Test 10</H3 -><P ->Run the command <B -CLASS="COMMAND" ->nmblookup -M TESTGROUP</B -> where -TESTGROUP is the name of the workgroup that your Samba server and -Windows PCs belong to. You should get back the IP address of the -master browser for that workgroup.</P -><P ->If you don't then the election process has failed. Wait a minute to -see if it is just being slow then try again. If it still fails after -that then look at the browsing options you have set in smb.conf. Make -sure you have <B -CLASS="COMMAND" ->preferred master = yes</B -> to ensure that -an election is held at startup.</P -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN3610" -></A ->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 -specified in smb.conf). You should be able to double click on the name -of the server and get a list of shares. If you get a "invalid -password" error when you do then you are probably running WinNT and it -is refusing to browse a server that has no encrypted password -capability and is in user level security mode. In this case either set -<B -CLASS="COMMAND" ->security = server</B -> AND -<B -CLASS="COMMAND" ->password server = Windows_NT_Machine</B -> in your -smb.conf file, or enable encrypted passwords AFTER compiling in support -for encrypted passwords (refer to the Makefile).</P -></DIV -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN3615" -></A ->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 -<A -HREF="mailto:samba@samba.org" -TARGET="_top" ->samba@samba.org</A ->. To find -out more about samba and how to subscribe to the mailing list check -out the samba web page at -<A -HREF="http://samba.org/samba" -TARGET="_top" ->http://samba.org/samba</A -></P -><P ->Also look at the other docs in the Samba package!</P -></DIV -></DIV -></DIV -></DIV -></BODY -></HTML ->
\ No newline at end of file diff --git a/docs/htmldocs/ads.html b/docs/htmldocs/ads.html index 2c556b61f3..26ec1d04a7 100644 --- a/docs/htmldocs/ads.html +++ b/docs/htmldocs/ads.html @@ -5,7 +5,8 @@ >Samba as a ADS domain member</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -16,7 +17,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 or Win2k domain member" +TITLE="Samba as a NT4 domain member" HREF="domain-security.html"></HEAD ><BODY CLASS="CHAPTER" @@ -72,16 +73,13 @@ WIDTH="100%"></DIV CLASS="CHAPTER" ><H1 ><A -NAME="ADS" -></A ->Chapter 7. Samba as a ADS domain member</H1 +NAME="ADS">Chapter 8. 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 -><P +>Pieces you need before you begin: +<P ></P ><TABLE BORDER="0" @@ -112,13 +110,10 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1339" -></A ->7.1. Installing the required packages for Debian</H1 -><P ->On Debian you need to install the following packages:</P -><P +NAME="AEN1187">8.1. Installing the required packages for Debian</H1 ><P +>On Debian you need to install the following packages: +<P ></P ><TABLE BORDER="0" @@ -142,13 +137,10 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1346" -></A ->7.2. Installing the required packages for RedHat</H1 -><P ->On RedHat this means you should have at least: </P -><P +NAME="AEN1193">8.2. Installing the required packages for RedHat</H1 ><P +>On RedHat this means you should have at least: +<P ></P ><TABLE BORDER="0" @@ -181,15 +173,12 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1356" -></A ->7.3. Compile Samba</H1 +NAME="AEN1202">8.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 it - generates contains +>After you run configure make sure that include/config.h contains lines like this:</P ><P ><PRE @@ -225,10 +214,9 @@ CLASS="PROGRAMLISTING" > ads server = your.kerberos.server</PRE ></P ><P ->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 +>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 required options will change soon when we get better active directory integration.</P ></DIV @@ -237,15 +225,13 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1371" -></A ->7.4. Setup your /etc/krb5.conf</H1 +NAME="AEN1217">8.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 @@ -269,18 +255,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 for smbd and winbindd.</P +support in smbd.</P ></DIV ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1381" -></A ->7.5. Create the computer account</H1 +NAME="AEN1227">8.5. Create the computer account</H1 ><P ->As a user that has write permission on the Samba private directory +>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 (usually root) run: <B CLASS="COMMAND" @@ -291,9 +277,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1385" -></A ->7.5.1. Possible errors</H2 +NAME="AEN1231">8.5.1. Possible errors</H2 ><P ><P ></P @@ -301,6 +285,12 @@ NAME="AEN1385" 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 @@ -316,9 +306,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1393" -></A ->7.6. Test your server setup</H1 +NAME="AEN1243">8.6. Test your server setup</H1 ><P >On a Windows 2000 client try <B CLASS="COMMAND" @@ -336,9 +324,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1398" -></A ->7.7. Testing with smbclient</H1 +NAME="AEN1248">8.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 @@ -349,9 +335,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1401" -></A ->7.8. Notes</H1 +NAME="AEN1251">8.8. Notes</H1 ><P >You must change administrator password at least once after DC install, to create the right encoding types</P @@ -418,7 +402,7 @@ ACCESSKEY="U" WIDTH="33%" ALIGN="right" VALIGN="top" ->Samba as a NT4 or Win2k domain member</TD +>Samba as a NT4 domain member</TD ></TR ></TABLE ></DIV diff --git a/docs/htmldocs/appendixes.html b/docs/htmldocs/appendixes.html index 469ef170cd..e7eefcb441 100644 --- a/docs/htmldocs/appendixes.html +++ b/docs/htmldocs/appendixes.html @@ -5,13 +5,14 @@ >Appendixes</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK REL="PREVIOUS" -TITLE="Creating Group Profiles" -HREF="groupprofiles.html"><LINK +TITLE="Samba performance issues" +HREF="speed.html"><LINK REL="NEXT" TITLE="Portability" HREF="portability.html"></HEAD @@ -42,7 +43,7 @@ WIDTH="10%" ALIGN="left" VALIGN="bottom" ><A -HREF="groupprofiles.html" +HREF="speed.html" ACCESSKEY="P" >Prev</A ></TD @@ -68,9 +69,7 @@ WIDTH="100%"></DIV ><DIV CLASS="PART" ><A -NAME="APPENDIXES" -></A -><DIV +NAME="APPENDIXES"><DIV CLASS="TITLEPAGE" ><H1 CLASS="TITLE" @@ -83,243 +82,243 @@ CLASS="TOC" >Table of Contents</B ></DT ><DT ->21. <A +>23. <A HREF="portability.html" >Portability</A ></DT ><DD ><DL ><DT ->21.1. <A -HREF="portability.html#AEN3251" +>23.1. <A +HREF="portability.html#AEN3139" >HPUX</A ></DT ><DT ->21.2. <A -HREF="portability.html#AEN3257" +>23.2. <A +HREF="portability.html#AEN3145" >SCO Unix</A ></DT ><DT ->21.3. <A -HREF="portability.html#AEN3261" +>23.3. <A +HREF="portability.html#AEN3149" >DNIX</A ></DT ><DT ->21.4. <A -HREF="portability.html#AEN3290" +>23.4. <A +HREF="portability.html#AEN3178" >RedHat Linux Rembrandt-II</A ></DT ></DL ></DD ><DT ->22. <A +>24. <A HREF="other-clients.html" >Samba and other CIFS clients</A ></DT ><DD ><DL ><DT ->22.1. <A -HREF="other-clients.html#AEN3311" +>24.1. <A +HREF="other-clients.html#AEN3199" >Macintosh clients?</A ></DT ><DT ->22.2. <A -HREF="other-clients.html#AEN3320" +>24.2. <A +HREF="other-clients.html#AEN3208" >OS2 Client</A ></DT ><DD ><DL ><DT ->22.2.1. <A -HREF="other-clients.html#AEN3322" +>24.2.1. <A +HREF="other-clients.html#AEN3210" >How can I configure OS/2 Warp Connect or OS/2 Warp 4 as a client for Samba?</A ></DT ><DT ->22.2.2. <A -HREF="other-clients.html#AEN3337" +>24.2.2. <A +HREF="other-clients.html#AEN3225" >How can I configure OS/2 Warp 3 (not Connect), OS/2 1.2, 1.3 or 2.x for Samba?</A ></DT ><DT ->22.2.3. <A -HREF="other-clients.html#AEN3346" +>24.2.3. <A +HREF="other-clients.html#AEN3234" >Are there any other issues when OS/2 (any version) is used as a client?</A ></DT ><DT ->22.2.4. <A -HREF="other-clients.html#AEN3350" +>24.2.4. <A +HREF="other-clients.html#AEN3238" >How do I get printer driver download working for OS/2 clients?</A ></DT ></DL ></DD ><DT ->22.3. <A -HREF="other-clients.html#AEN3360" +>24.3. <A +HREF="other-clients.html#AEN3248" >Windows for Workgroups</A ></DT ><DD ><DL ><DT ->22.3.1. <A -HREF="other-clients.html#AEN3362" +>24.3.1. <A +HREF="other-clients.html#AEN3250" >Use latest TCP/IP stack from Microsoft</A ></DT ><DT ->22.3.2. <A -HREF="other-clients.html#AEN3367" +>24.3.2. <A +HREF="other-clients.html#AEN3255" >Delete .pwl files after password change</A ></DT ><DT ->22.3.3. <A -HREF="other-clients.html#AEN3372" +>24.3.3. <A +HREF="other-clients.html#AEN3260" >Configure WfW password handling</A ></DT ><DT ->22.3.4. <A -HREF="other-clients.html#AEN3376" +>24.3.4. <A +HREF="other-clients.html#AEN3264" >Case handling of passwords</A ></DT ></DL ></DD ><DT ->22.4. <A -HREF="other-clients.html#AEN3381" +>24.4. <A +HREF="other-clients.html#AEN3269" >Windows '95/'98</A ></DT ><DT ->22.5. <A -HREF="other-clients.html#AEN3397" +>24.5. <A +HREF="other-clients.html#AEN3285" >Windows 2000 Service Pack 2</A ></DT ></DL ></DD ><DT ->23. <A +>25. <A HREF="bugreport.html" >Reporting Bugs</A ></DT ><DD ><DL ><DT ->23.1. <A -HREF="bugreport.html#AEN3421" +>25.1. <A +HREF="bugreport.html#AEN3309" >Introduction</A ></DT ><DT ->23.2. <A -HREF="bugreport.html#AEN3431" +>25.2. <A +HREF="bugreport.html#AEN3319" >General info</A ></DT ><DT ->23.3. <A -HREF="bugreport.html#AEN3437" +>25.3. <A +HREF="bugreport.html#AEN3325" >Debug levels</A ></DT ><DT ->23.4. <A -HREF="bugreport.html#AEN3454" +>25.4. <A +HREF="bugreport.html#AEN3342" >Internal errors</A ></DT ><DT ->23.5. <A -HREF="bugreport.html#AEN3464" +>25.5. <A +HREF="bugreport.html#AEN3352" >Attaching to a running process</A ></DT ><DT ->23.6. <A -HREF="bugreport.html#AEN3467" +>25.6. <A +HREF="bugreport.html#AEN3355" >Patches</A ></DT ></DL ></DD ><DT ->24. <A +>26. <A HREF="diagnosis.html" >Diagnosing your samba server</A ></DT ><DD ><DL ><DT ->24.1. <A -HREF="diagnosis.html#AEN3490" +>26.1. <A +HREF="diagnosis.html#AEN3378" >Introduction</A ></DT ><DT ->24.2. <A -HREF="diagnosis.html#AEN3495" +>26.2. <A +HREF="diagnosis.html#AEN3383" >Assumptions</A ></DT ><DT ->24.3. <A -HREF="diagnosis.html#AEN3505" +>26.3. <A +HREF="diagnosis.html#AEN3393" >Tests</A ></DT ><DD ><DL ><DT ->24.3.1. <A -HREF="diagnosis.html#AEN3507" +>26.3.1. <A +HREF="diagnosis.html#AEN3395" >Test 1</A ></DT ><DT ->24.3.2. <A -HREF="diagnosis.html#AEN3513" +>26.3.2. <A +HREF="diagnosis.html#AEN3401" >Test 2</A ></DT ><DT ->24.3.3. <A -HREF="diagnosis.html#AEN3519" +>26.3.3. <A +HREF="diagnosis.html#AEN3407" >Test 3</A ></DT ><DT ->24.3.4. <A -HREF="diagnosis.html#AEN3534" +>26.3.4. <A +HREF="diagnosis.html#AEN3422" >Test 4</A ></DT ><DT ->24.3.5. <A -HREF="diagnosis.html#AEN3539" +>26.3.5. <A +HREF="diagnosis.html#AEN3427" >Test 5</A ></DT ><DT ->24.3.6. <A -HREF="diagnosis.html#AEN3545" +>26.3.6. <A +HREF="diagnosis.html#AEN3433" >Test 6</A ></DT ><DT ->24.3.7. <A -HREF="diagnosis.html#AEN3553" +>26.3.7. <A +HREF="diagnosis.html#AEN3441" >Test 7</A ></DT ><DT ->24.3.8. <A -HREF="diagnosis.html#AEN3579" +>26.3.8. <A +HREF="diagnosis.html#AEN3467" >Test 8</A ></DT ><DT ->24.3.9. <A -HREF="diagnosis.html#AEN3596" +>26.3.9. <A +HREF="diagnosis.html#AEN3484" >Test 9</A ></DT ><DT ->24.3.10. <A -HREF="diagnosis.html#AEN3604" +>26.3.10. <A +HREF="diagnosis.html#AEN3492" >Test 10</A ></DT ><DT ->24.3.11. <A -HREF="diagnosis.html#AEN3610" +>26.3.11. <A +HREF="diagnosis.html#AEN3498" >Test 11</A ></DT ></DL ></DD ><DT ->24.4. <A -HREF="diagnosis.html#AEN3615" +>26.4. <A +HREF="diagnosis.html#AEN3503" >Still having troubles?</A ></DT ></DL @@ -344,7 +343,7 @@ WIDTH="33%" ALIGN="left" VALIGN="top" ><A -HREF="groupprofiles.html" +HREF="speed.html" ACCESSKEY="P" >Prev</A ></TD @@ -372,7 +371,7 @@ ACCESSKEY="N" WIDTH="33%" ALIGN="left" VALIGN="top" ->Creating Group Profiles</TD +>Samba performance issues</TD ><TD WIDTH="34%" ALIGN="center" diff --git a/docs/htmldocs/browsing-quick.html b/docs/htmldocs/browsing-quick.html index 680bdfc1de..8c597e001f 100644 --- a/docs/htmldocs/browsing-quick.html +++ b/docs/htmldocs/browsing-quick.html @@ -5,7 +5,8 @@ >Quick Cross Subnet Browsing / Cross Workgroup Browsing guide</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -13,11 +14,11 @@ REL="UP" TITLE="General installation" HREF="introduction.html"><LINK REL="PREVIOUS" -TITLE="How to Install and Test SAMBA" -HREF="install.html"><LINK +TITLE="Improved browsing in samba" +HREF="improved-browsing.html"><LINK REL="NEXT" -TITLE="User information database" -HREF="passdb.html"></HEAD +TITLE="LanMan and NT Password Encryption in Samba" +HREF="pwencrypt.html"></HEAD ><BODY CLASS="CHAPTER" BGCOLOR="#FFFFFF" @@ -45,7 +46,7 @@ WIDTH="10%" ALIGN="left" VALIGN="bottom" ><A -HREF="install.html" +HREF="improved-browsing.html" ACCESSKEY="P" >Prev</A ></TD @@ -59,7 +60,7 @@ WIDTH="10%" ALIGN="right" VALIGN="bottom" ><A -HREF="passdb.html" +HREF="pwencrypt.html" ACCESSKEY="N" >Next</A ></TD @@ -72,9 +73,7 @@ WIDTH="100%"></DIV CLASS="CHAPTER" ><H1 ><A -NAME="BROWSING-QUICK" -></A ->Chapter 2. Quick Cross Subnet Browsing / Cross Workgroup Browsing guide</H1 +NAME="BROWSING-QUICK">Chapter 3. 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 @@ -86,9 +85,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN230" -></A ->2.1. Discussion</H1 +NAME="AEN377">3.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 @@ -132,9 +129,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN238" -></A ->2.2. Use of the "Remote Announce" parameter</H1 +NAME="AEN385">3.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. @@ -190,9 +185,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN252" -></A ->2.3. Use of the "Remote Browse Sync" parameter</H1 +NAME="AEN399">3.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 @@ -200,10 +193,9 @@ 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 @@ -213,9 +205,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN257" -></A ->2.4. Use of WINS</H1 +NAME="AEN404">3.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 @@ -275,9 +265,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN268" -></A ->2.5. Do NOT use more than one (1) protocol on MS Windows machines</H1 +NAME="AEN415">3.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 @@ -305,14 +293,12 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN274" -></A ->2.6. Name Resolution Order</H1 +NAME="AEN421">3.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 -><P +are: +<P ></P ><TABLE BORDER="0" @@ -333,9 +319,10 @@ BORDER="0" ></TABLE ><P ></P +></P ><P ->Alternative means of name resolution includes:</P -><P +>Alternative means of name resolution includes: +<P ></P ><TABLE BORDER="0" @@ -352,23 +339,24 @@ 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 @@ -400,7 +388,7 @@ WIDTH="33%" ALIGN="left" VALIGN="top" ><A -HREF="install.html" +HREF="improved-browsing.html" ACCESSKEY="P" >Prev</A ></TD @@ -418,7 +406,7 @@ WIDTH="33%" ALIGN="right" VALIGN="top" ><A -HREF="passdb.html" +HREF="pwencrypt.html" ACCESSKEY="N" >Next</A ></TD @@ -428,7 +416,7 @@ ACCESSKEY="N" WIDTH="33%" ALIGN="left" VALIGN="top" ->How to Install and Test SAMBA</TD +>Improved browsing in samba</TD ><TD WIDTH="34%" ALIGN="center" @@ -442,7 +430,7 @@ ACCESSKEY="U" WIDTH="33%" ALIGN="right" VALIGN="top" ->User information database</TD +>LanMan and NT Password Encryption in Samba</TD ></TR ></TABLE ></DIV diff --git a/docs/htmldocs/bugreport.html b/docs/htmldocs/bugreport.html index 813d0055cc..fcc4b7e91a 100644 --- a/docs/htmldocs/bugreport.html +++ b/docs/htmldocs/bugreport.html @@ -5,7 +5,8 @@ >Reporting Bugs</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -72,17 +73,13 @@ WIDTH="100%"></DIV CLASS="CHAPTER" ><H1 ><A -NAME="BUGREPORT" -></A ->Chapter 23. Reporting Bugs</H1 +NAME="BUGREPORT">Chapter 25. Reporting Bugs</H1 ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3421" -></A ->23.1. Introduction</H1 +NAME="AEN3309">25.1. Introduction</H1 ><P >The email address for bug reports for stable releases is <A HREF="samba@samba.org" @@ -125,9 +122,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3431" -></A ->23.2. General info</H1 +NAME="AEN3319">25.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 @@ -150,9 +145,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3437" -></A ->23.3. Debug levels</H1 +NAME="AEN3325">25.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 @@ -220,9 +213,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3454" -></A ->23.4. Internal errors</H1 +NAME="AEN3342">25.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 @@ -264,9 +255,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3464" -></A ->23.5. Attaching to a running process</H1 +NAME="AEN3352">25.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 @@ -281,9 +270,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3467" -></A ->23.6. Patches</H1 +NAME="AEN3355">25.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 4e088faf70..73cd333805 100644 --- a/docs/htmldocs/cvs-access.html +++ b/docs/htmldocs/cvs-access.html @@ -2,10 +2,11 @@ <HTML ><HEAD ><TITLE ->Access Samba source code via CVS</TITLE +>HOWTO Access Samba source code via CVS</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -13,8 +14,8 @@ REL="UP" TITLE="Optional configuration" HREF="optional.html"><LINK REL="PREVIOUS" -TITLE="Stackable VFS modules" -HREF="vfs.html"><LINK +TITLE="Storing Samba's User/Machine Account information in an LDAP Directory" +HREF="samba-ldap-howto.html"><LINK REL="NEXT" TITLE="Group mapping HOWTO" HREF="groupmapping.html"></HEAD @@ -45,7 +46,7 @@ WIDTH="10%" ALIGN="left" VALIGN="bottom" ><A -HREF="vfs.html" +HREF="samba-ldap-howto.html" ACCESSKEY="P" >Prev</A ></TD @@ -72,17 +73,13 @@ WIDTH="100%"></DIV CLASS="CHAPTER" ><H1 ><A -NAME="CVS-ACCESS" -></A ->Chapter 17. Access Samba source code via CVS</H1 +NAME="CVS-ACCESS">Chapter 20. HOWTO Access Samba source code via CVS</H1 ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2942" -></A ->17.1. Introduction</H1 +NAME="AEN2964">20.1. Introduction</H1 ><P >Samba is developed in an open environment. Developers use CVS (Concurrent Versioning System) to "checkin" (also known as @@ -102,9 +99,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2947" -></A ->17.2. CVS Access to samba.org</H1 +NAME="AEN2969">20.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, @@ -115,9 +110,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2950" -></A ->17.2.1. Access via CVSweb</H2 +NAME="AEN2972">20.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 @@ -136,9 +129,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2955" -></A ->17.2.2. Access via cvs</H2 +NAME="AEN2977">20.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 @@ -256,7 +247,7 @@ WIDTH="33%" ALIGN="left" VALIGN="top" ><A -HREF="vfs.html" +HREF="samba-ldap-howto.html" ACCESSKEY="P" >Prev</A ></TD @@ -284,7 +275,7 @@ ACCESSKEY="N" WIDTH="33%" ALIGN="left" VALIGN="top" ->Stackable VFS modules</TD +>Storing Samba's User/Machine Account information in an LDAP Directory</TD ><TD WIDTH="34%" ALIGN="center" diff --git a/docs/htmldocs/diagnosis.html b/docs/htmldocs/diagnosis.html index 0c71043074..a7b2e59436 100644 --- a/docs/htmldocs/diagnosis.html +++ b/docs/htmldocs/diagnosis.html @@ -5,7 +5,8 @@ >Diagnosing your samba server</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -65,17 +66,13 @@ WIDTH="100%"></DIV CLASS="CHAPTER" ><H1 ><A -NAME="DIAGNOSIS" -></A ->Chapter 24. Diagnosing your samba server</H1 +NAME="DIAGNOSIS">Chapter 26. Diagnosing your samba server</H1 ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3490" -></A ->24.1. Introduction</H1 +NAME="AEN3378">26.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 @@ -95,9 +92,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3495" -></A ->24.2. Assumptions</H1 +NAME="AEN3383">26.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 @@ -133,17 +128,13 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3505" -></A ->24.3. Tests</H1 +NAME="AEN3393">26.3. Tests</H1 ><DIV CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3507" -></A ->24.3.1. Test 1</H2 +NAME="AEN3395">26.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 @@ -163,9 +154,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3513" -></A ->24.3.2. Test 2</H2 +NAME="AEN3401">26.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 @@ -189,9 +178,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3519" -></A ->24.3.3. Test 3</H2 +NAME="AEN3407">26.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 @@ -260,9 +247,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3534" -></A ->24.3.4. Test 4</H2 +NAME="AEN3422">26.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 @@ -281,9 +266,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3539" -></A ->24.3.5. Test 5</H2 +NAME="AEN3427">26.3.5. Test 5</H2 ><P >run the command <B CLASS="COMMAND" @@ -302,9 +285,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3545" -></A ->24.3.6. Test 6</H2 +NAME="AEN3433">26.3.6. Test 6</H2 ><P >Run the command <B CLASS="COMMAND" @@ -336,9 +317,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3553" -></A ->24.3.7. Test 7</H2 +NAME="AEN3441">26.3.7. Test 7</H2 ><P >Run the command <B CLASS="COMMAND" @@ -425,9 +404,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3579" -></A ->24.3.8. Test 8</H2 +NAME="AEN3467">26.3.8. Test 8</H2 ><P >On the PC type the command <B CLASS="COMMAND" @@ -485,9 +462,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3596" -></A ->24.3.9. Test 9</H2 +NAME="AEN3484">26.3.9. Test 9</H2 ><P >Run the command <B CLASS="COMMAND" @@ -519,9 +494,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3604" -></A ->24.3.10. Test 10</H2 +NAME="AEN3492">26.3.10. Test 10</H2 ><P >Run the command <B CLASS="COMMAND" @@ -545,9 +518,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3610" -></A ->24.3.11. Test 11</H2 +NAME="AEN3498">26.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 @@ -573,9 +544,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3615" -></A ->24.4. Still having troubles?</H1 +NAME="AEN3503">26.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 fcb40641e4..670d96ba5f 100644 --- a/docs/htmldocs/domain-security.html +++ b/docs/htmldocs/domain-security.html @@ -2,10 +2,11 @@ <HTML ><HEAD ><TITLE ->Samba as a NT4 or Win2k domain member</TITLE +>Samba as a NT4 domain member</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -72,23 +73,19 @@ WIDTH="100%"></DIV CLASS="CHAPTER" ><H1 ><A -NAME="DOMAIN-SECURITY" -></A ->Chapter 8. Samba as a NT4 or Win2k domain member</H1 +NAME="DOMAIN-SECURITY">Chapter 9. Samba as a NT4 domain member</H1 ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1423" -></A ->8.1. Joining an NT Domain with Samba 3.0</H1 +NAME="AEN1273">9.1. Joining an NT Domain with Samba 2.2</H1 ><P ->Assume you have a Samba 3.0 server with a NetBIOS name of +>Assume you have a Samba 2.x server with a NetBIOS name of <TT CLASS="CONSTANT" >SERV1</TT -> and are joining an or Win2k NT domain called +> and are joining an NT domain called <TT CLASS="CONSTANT" >DOM</TT @@ -106,7 +103,107 @@ CLASS="CONSTANT" </TT >.</P ><P ->Firstly, you must edit your <A +>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 HREF="smb.conf.5.html" TARGET="_top" ><TT @@ -131,12 +228,7 @@ CLASS="PARAMETER" ><B CLASS="COMMAND" >security = domain</B -> or - <B -CLASS="COMMAND" ->security = ads</B -> depending on if the PDC is - NT4 or running Active Directory respectivly.</P +></P ><P >Next change the <A HREF="smb.conf.5.html#WORKGROUP" @@ -203,77 +295,11 @@ CLASS="COMMAND" >password server = *</B ></P ><P ->This method, allows Samba to use exactly the same - mechanism that NT does. This +>This method, which was introduced in Samba 2.0.6, + 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 @@ -282,23 +308,30 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1478" -></A ->8.2. Samba and Windows 2000 Domains</H1 +NAME="AEN1337">9.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. The steps above apply -to both NT4 and Windows 2000.</P +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 ></DIV ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1481" -></A ->8.3. Why is this better than security = server?</H1 +NAME="AEN1342">9.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 @@ -354,7 +387,13 @@ 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. </P + 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 ><P ><SPAN CLASS="emphasis" diff --git a/docs/htmldocs/findsmb.1.html b/docs/htmldocs/findsmb.1.html index bf63db867c..af7100ed6f 100644 --- a/docs/htmldocs/findsmb.1.html +++ b/docs/htmldocs/findsmb.1.html @@ -1,11 +1,12 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"> <HTML ><HEAD ><TITLE >findsmb</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"></HEAD +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"></HEAD ><BODY CLASS="REFENTRY" BGCOLOR="#FFFFFF" @@ -15,9 +16,7 @@ VLINK="#840084" ALINK="#0000FF" ><H1 ><A -NAME="FINDSMB.1" -></A ->findsmb</H1 +NAME="FINDSMB">findsmb</H1 ><DIV CLASS="REFNAMEDIV" ><A @@ -30,15 +29,13 @@ NAME="AEN5" ><DIV CLASS="REFSYNOPSISDIV" ><A -NAME="AEN8" -></A -><H2 +NAME="AEN8"><H2 >Synopsis</H2 ><P ><B CLASS="COMMAND" >findsmb</B -> [subnet broadcast address]</P +> [subnet broadcast address]</P ></DIV ><DIV CLASS="REFSECT1" @@ -48,14 +45,11 @@ NAME="AEN12" ><H2 >DESCRIPTION</H2 ><P ->This perl script is part of the <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->Samba</SPAN ->(7)</SPAN -> - suite.</P +>This perl script is part of the <A +HREF="samba.7.html" +TARGET="_top" +> Samba</A +> suite.</P ><P ><B CLASS="COMMAND" @@ -63,27 +57,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 <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. + 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. </P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN26" +NAME="AEN22" ></A ><H2 >OPTIONS</H2 @@ -103,12 +97,13 @@ 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, <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->nmblookup</SPAN ->(1)</SPAN + If set, <A +HREF="nmblookup.1.html" +TARGET="_top" +><B +CLASS="COMMAND" +>nmblookup</B +></A > will be called with <TT CLASS="CONSTANT" @@ -124,22 +119,15 @@ CLASS="COMMAND" >findsmb </B > will probe the subnet of the machine where - <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 + <B +CLASS="COMMAND" +>findsmb</B +> is run. This value is passed + to <B +CLASS="COMMAND" +>nmblookup</B +> as part of the + <TT CLASS="CONSTANT" >-B</TT > option.</P @@ -150,7 +138,7 @@ CLASS="CONSTANT" ><DIV CLASS="REFSECT1" ><A -NAME="AEN50" +NAME="AEN41" ></A ><H2 >EXAMPLES</H2 @@ -178,14 +166,14 @@ CLASS="COMMAND" CLASS="CONSTANT" >-r</TT > option - must be run on a system without <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->nmbd</SPAN ->(8)</SPAN -> running. - + must be run on a system without <A +HREF="nmbd.8.html" +TARGET="_top" +><B +CLASS="COMMAND" +>nmbd</B +></A +> running. If <B CLASS="COMMAND" >nmbd</B @@ -204,14 +192,22 @@ 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] @@ -223,12 +219,17 @@ CLASS="SCREEN" 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]</PRE +192.168.35.97 HERBNT1 *[HERB-NT] [Windows NT 4.0] [NT LAN Manager 4.0] + </TT +></PRE +></TD +></TR +></TABLE ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN68" +NAME="AEN59" ></A ><H2 >VERSION</H2 @@ -239,37 +240,41 @@ NAME="AEN68" ><DIV CLASS="REFSECT1" ><A -NAME="AEN71" +NAME="AEN62" ></A ><H2 >SEE ALSO</H2 ><P -><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 +><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 > </P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN83" +NAME="AEN71" ></A ><H2 >AUTHOR</H2 @@ -281,14 +286,14 @@ NAME="AEN83" ><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. The conversion to DocBook - XML 4.2 for Samba 3.0 was done by Alexander Bokovoy.</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</P ></DIV ></BODY ></HTML diff --git a/docs/htmldocs/groupmapping.html b/docs/htmldocs/groupmapping.html index d7eafcb58f..84cf521fc9 100644 --- a/docs/htmldocs/groupmapping.html +++ b/docs/htmldocs/groupmapping.html @@ -5,7 +5,8 @@ >Group mapping HOWTO</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -13,7 +14,7 @@ REL="UP" TITLE="Optional configuration" HREF="optional.html"><LINK REL="PREVIOUS" -TITLE="Access Samba source code via CVS" +TITLE="HOWTO Access Samba source code via CVS" HREF="cvs-access.html"><LINK REL="NEXT" TITLE="Samba performance issues" @@ -72,9 +73,7 @@ WIDTH="100%"></DIV CLASS="CHAPTER" ><H1 ><A -NAME="GROUPMAPPING" -></A ->Chapter 18. Group mapping HOWTO</H1 +NAME="GROUPMAPPING">Chapter 21. Group mapping HOWTO</H1 ><P > Starting with Samba 3.0 alpha 2, a new group mapping function is available. The @@ -213,7 +212,7 @@ ACCESSKEY="N" WIDTH="33%" ALIGN="left" VALIGN="top" ->Access Samba source code via CVS</TD +>HOWTO Access Samba source code via CVS</TD ><TD WIDTH="34%" ALIGN="center" diff --git a/docs/htmldocs/groupprofiles.html b/docs/htmldocs/groupprofiles.html deleted file mode 100644 index c9184032aa..0000000000 --- a/docs/htmldocs/groupprofiles.html +++ /dev/null @@ -1,565 +0,0 @@ -<!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 b912cb57e5..4e9d7f639e 100644 --- a/docs/htmldocs/improved-browsing.html +++ b/docs/htmldocs/improved-browsing.html @@ -5,19 +5,20 @@ >Improved browsing in samba</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK REL="UP" -TITLE="Optional configuration" -HREF="optional.html"><LINK +TITLE="General installation" +HREF="introduction.html"><LINK REL="PREVIOUS" -TITLE="Unified Logons between Windows NT and UNIX using Winbind" -HREF="winbind.html"><LINK +TITLE="How to Install and Test SAMBA" +HREF="install.html"><LINK REL="NEXT" -TITLE="Stackable VFS modules" -HREF="vfs.html"></HEAD +TITLE="Quick Cross Subnet Browsing / Cross Workgroup Browsing guide" +HREF="browsing-quick.html"></HEAD ><BODY CLASS="CHAPTER" BGCOLOR="#FFFFFF" @@ -45,7 +46,7 @@ WIDTH="10%" ALIGN="left" VALIGN="bottom" ><A -HREF="winbind.html" +HREF="install.html" ACCESSKEY="P" >Prev</A ></TD @@ -59,7 +60,7 @@ WIDTH="10%" ALIGN="right" VALIGN="bottom" ><A -HREF="vfs.html" +HREF="browsing-quick.html" ACCESSKEY="N" >Next</A ></TD @@ -72,17 +73,13 @@ WIDTH="100%"></DIV CLASS="CHAPTER" ><H1 ><A -NAME="IMPROVED-BROWSING" -></A ->Chapter 15. Improved browsing in samba</H1 +NAME="IMPROVED-BROWSING">Chapter 2. Improved browsing in samba</H1 ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2700" -></A ->15.1. Overview of browsing</H1 +NAME="AEN229">2.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 @@ -104,9 +101,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2704" -></A ->15.2. Browsing support in samba</H1 +NAME="AEN233">2.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 @@ -149,9 +144,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2713" -></A ->15.3. Problem resolution</H1 +NAME="AEN242">2.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 @@ -183,9 +176,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2720" -></A ->15.4. Browsing across subnets</H1 +NAME="AEN249">2.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 @@ -214,9 +205,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2725" -></A ->15.4.1. How does cross subnet browsing work ?</H2 +NAME="AEN254">2.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 @@ -426,9 +415,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2760" -></A ->15.5. Setting up a WINS server</H1 +NAME="AEN289">2.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 @@ -509,9 +496,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2779" -></A ->15.6. Setting up Browsing in a WORKGROUP</H1 +NAME="AEN308">2.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 @@ -593,9 +578,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2797" -></A ->15.7. Setting up Browsing in a DOMAIN</H1 +NAME="AEN326">2.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. @@ -644,9 +627,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2807" -></A ->15.8. Forcing samba to be the master</H1 +NAME="AEN336">2.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 @@ -692,9 +673,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2816" -></A ->15.9. Making samba the domain master</H1 +NAME="AEN345">2.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 @@ -765,9 +744,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2834" -></A ->15.10. Note about broadcast addresses</H1 +NAME="AEN363">2.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 @@ -779,9 +756,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2837" -></A ->15.11. Multiple interfaces</H1 +NAME="AEN366">2.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" @@ -804,7 +779,7 @@ WIDTH="33%" ALIGN="left" VALIGN="top" ><A -HREF="winbind.html" +HREF="install.html" ACCESSKEY="P" >Prev</A ></TD @@ -822,7 +797,7 @@ WIDTH="33%" ALIGN="right" VALIGN="top" ><A -HREF="vfs.html" +HREF="browsing-quick.html" ACCESSKEY="N" >Next</A ></TD @@ -832,13 +807,13 @@ ACCESSKEY="N" WIDTH="33%" ALIGN="left" VALIGN="top" ->Unified Logons between Windows NT and UNIX using Winbind</TD +>How to Install and Test SAMBA</TD ><TD WIDTH="34%" ALIGN="center" VALIGN="top" ><A -HREF="optional.html" +HREF="introduction.html" ACCESSKEY="U" >Up</A ></TD @@ -846,7 +821,7 @@ ACCESSKEY="U" WIDTH="33%" ALIGN="right" VALIGN="top" ->Stackable VFS modules</TD +>Quick Cross Subnet Browsing / Cross Workgroup Browsing guide</TD ></TR ></TABLE ></DIV diff --git a/docs/htmldocs/install.html b/docs/htmldocs/install.html index e518e270bf..0ba79dbe26 100644 --- a/docs/htmldocs/install.html +++ b/docs/htmldocs/install.html @@ -5,7 +5,8 @@ >How to Install and Test SAMBA</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -16,8 +17,8 @@ REL="PREVIOUS" TITLE="General installation" HREF="introduction.html"><LINK REL="NEXT" -TITLE="Quick Cross Subnet Browsing / Cross Workgroup Browsing guide" -HREF="browsing-quick.html"></HEAD +TITLE="Improved browsing in samba" +HREF="improved-browsing.html"></HEAD ><BODY CLASS="CHAPTER" BGCOLOR="#FFFFFF" @@ -59,7 +60,7 @@ WIDTH="10%" ALIGN="right" VALIGN="bottom" ><A -HREF="browsing-quick.html" +HREF="improved-browsing.html" ACCESSKEY="N" >Next</A ></TD @@ -72,17 +73,13 @@ WIDTH="100%"></DIV CLASS="CHAPTER" ><H1 ><A -NAME="INSTALL" -></A ->Chapter 1. How to Install and Test SAMBA</H1 +NAME="INSTALL">Chapter 1. How to Install and Test SAMBA</H1 ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN26" -></A ->1.1. Read the man pages</H1 +NAME="AEN26">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. @@ -122,9 +119,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN36" -></A ->1.2. Building the Binaries</H1 +NAME="AEN36">1.2. Building the Binaries</H1 ><P >To do this, first run the program <B CLASS="COMMAND" @@ -221,9 +216,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN64" -></A ->1.3. The all important step</H1 +NAME="AEN64">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 @@ -238,9 +231,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN68" -></A ->1.4. Create the smb configuration file.</H1 +NAME="AEN68">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 @@ -294,9 +285,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN82" -></A ->1.5. Test your config file with +NAME="AEN82">1.5. Test your config file with <B CLASS="COMMAND" >testparm</B @@ -324,9 +313,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN90" -></A ->1.6. Starting the smbd and nmbd</H1 +NAME="AEN90">1.6. Starting the smbd and nmbd</H1 ><P >You must choose to start smbd and nmbd either as daemons or from <B @@ -364,9 +351,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN100" -></A ->1.6.1. Starting from inetd.conf</H2 +NAME="AEN100">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 @@ -468,9 +453,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN129" -></A ->1.6.2. Alternative: starting it as a daemon</H2 +NAME="AEN129">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 @@ -525,9 +508,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN145" -></A ->1.7. Try listing the shares available on your +NAME="AEN145">1.7. Try listing the shares available on your server</H1 ><P ><TT @@ -566,9 +547,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN154" -></A ->1.8. Try connecting with the unix client</H1 +NAME="AEN154">1.8. Try connecting with the unix client</H1 ><P ><TT CLASS="PROMPT" @@ -629,9 +608,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN170" -></A ->1.9. Try connecting from a DOS, WfWg, Win9x, WinNT, +NAME="AEN170">1.9. Try connecting from a DOS, WfWg, Win9x, WinNT, Win2k, OS/2, etc... client</H1 ><P >Try mounting disks. eg:</P @@ -678,9 +655,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN184" -></A ->1.10. What If Things Don't Work?</H1 +NAME="AEN184">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 @@ -701,9 +676,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN189" -></A ->1.10.1. Diagnosing Problems</H2 +NAME="AEN189">1.10.1. Diagnosing Problems</H2 ><P >If you have installation problems then go to the <A @@ -718,9 +691,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN193" -></A ->1.10.2. Scope IDs</H2 +NAME="AEN193">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. @@ -734,9 +705,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN196" -></A ->1.10.3. Choosing the Protocol Level</H2 +NAME="AEN196">1.10.3. Choosing the Protocol Level</H2 ><P >The SMB protocol has many dialects. Currently Samba supports 5, called CORE, COREPLUS, LANMAN1, @@ -775,9 +744,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN205" -></A ->1.10.4. Printing from UNIX to a Client PC</H2 +NAME="AEN205">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 @@ -796,9 +763,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN210" -></A ->1.10.5. Locking</H2 +NAME="AEN210">1.10.5. Locking</H2 ><P >One area which sometimes causes trouble is locking.</P ><P @@ -856,9 +821,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN219" -></A ->1.10.6. Mapping Usernames</H2 +NAME="AEN219">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. @@ -900,7 +863,7 @@ WIDTH="33%" ALIGN="right" VALIGN="top" ><A -HREF="browsing-quick.html" +HREF="improved-browsing.html" ACCESSKEY="N" >Next</A ></TD @@ -924,7 +887,7 @@ ACCESSKEY="U" WIDTH="33%" ALIGN="right" VALIGN="top" ->Quick Cross Subnet Browsing / Cross Workgroup Browsing guide</TD +>Improved browsing in samba</TD ></TR ></TABLE ></DIV diff --git a/docs/htmldocs/integrate-ms-networks.html b/docs/htmldocs/integrate-ms-networks.html index 8299a456bb..ad6aa9e225 100644 --- a/docs/htmldocs/integrate-ms-networks.html +++ b/docs/htmldocs/integrate-ms-networks.html @@ -5,7 +5,8 @@ >Integrating MS Windows networks with Samba</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -72,17 +73,13 @@ WIDTH="100%"></DIV CLASS="CHAPTER" ><H1 ><A -NAME="INTEGRATE-MS-NETWORKS" -></A ->Chapter 9. Integrating MS Windows networks with Samba</H1 +NAME="INTEGRATE-MS-NETWORKS">Chapter 10. Integrating MS Windows networks with Samba</H1 ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1513" -></A ->9.1. Agenda</H1 +NAME="AEN1374">10.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 @@ -147,9 +144,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1535" -></A ->9.2. Name Resolution in a pure Unix/Linux world</H1 +NAME="AEN1396">10.2. Name Resolution in a pure Unix/Linux world</H1 ><P >The key configuration files covered in this section are:</P ><P @@ -189,9 +184,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1551" -></A ->9.2.1. <TT +NAME="AEN1412">10.2.1. <TT CLASS="FILENAME" >/etc/hosts</TT ></H2 @@ -270,9 +263,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1567" -></A ->9.2.2. <TT +NAME="AEN1428">10.2.2. <TT CLASS="FILENAME" >/etc/resolv.conf</TT ></H2 @@ -308,9 +299,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1578" -></A ->9.2.3. <TT +NAME="AEN1439">10.2.3. <TT CLASS="FILENAME" >/etc/host.conf</TT ></H2 @@ -337,9 +326,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1586" -></A ->9.2.4. <TT +NAME="AEN1447">10.2.4. <TT CLASS="FILENAME" >/etc/nsswitch.conf</TT ></H2 @@ -406,9 +393,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1598" -></A ->9.3. Name resolution as used within MS Windows networking</H1 +NAME="AEN1459">10.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 @@ -428,16 +413,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 @@ -456,7 +441,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 @@ -491,9 +476,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1610" -></A ->9.3.1. The NetBIOS Name Cache</H2 +NAME="AEN1471">10.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 @@ -518,9 +501,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1615" -></A ->9.3.2. The LMHOSTS file</H2 +NAME="AEN1476">10.3.2. The LMHOSTS file</H2 ><P >This file is usually located in MS Windows NT 4.0 or 2000 in <TT @@ -621,9 +602,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1623" -></A ->9.3.3. HOSTS file</H2 +NAME="AEN1484">10.3.3. HOSTS file</H2 ><P >This file is usually located in MS Windows NT 4.0 or 2000 in <TT @@ -643,9 +622,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1628" -></A ->9.3.4. DNS Lookup</H2 +NAME="AEN1489">10.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 @@ -663,9 +640,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1631" -></A ->9.3.5. WINS Lookup</H2 +NAME="AEN1492">10.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 @@ -706,9 +681,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1643" -></A ->9.4. How browsing functions and how to deploy stable and +NAME="AEN1504">10.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 @@ -773,9 +746,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1653" -></A ->9.5. MS Windows security options and how to configure +NAME="AEN1514">10.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 @@ -910,9 +881,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1681" -></A ->9.5.1. Use MS Windows NT as an authentication server</H2 +NAME="AEN1542">10.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 @@ -946,9 +915,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1689" -></A ->9.5.2. Make Samba a member of an MS Windows NT security domain</H2 +NAME="AEN1550">10.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 @@ -1009,9 +976,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1706" -></A ->9.5.3. Configure Samba as an authentication server</H2 +NAME="AEN1567">10.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 @@ -1046,9 +1011,7 @@ CLASS="SECT3" ><H3 CLASS="SECT3" ><A -NAME="AEN1713" -></A ->9.5.3.1. Users</H3 +NAME="AEN1574">10.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 @@ -1069,9 +1032,7 @@ CLASS="SECT3" ><H3 CLASS="SECT3" ><A -NAME="AEN1718" -></A ->9.5.3.2. MS Windows NT Machine Accounts</H3 +NAME="AEN1579">10.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 @@ -1090,9 +1051,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1723" -></A ->9.6. Conclusions</H1 +NAME="AEN1584">10.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 a68950fede..762d56ba6a 100644 --- a/docs/htmldocs/introduction.html +++ b/docs/htmldocs/introduction.html @@ -5,7 +5,8 @@ >General installation</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -68,9 +69,7 @@ WIDTH="100%"></DIV ><DIV CLASS="PART" ><A -NAME="INTRODUCTION" -></A -><DIV +NAME="INTRODUCTION"><DIV CLASS="TITLEPAGE" ><H1 CLASS="TITLE" @@ -78,9 +77,7 @@ CLASS="TITLE" ><DIV CLASS="PARTINTRO" ><A -NAME="AEN21" -></A -><H1 +NAME="AEN21"><H1 >Introduction</H1 ><P >This part contains general info on how to install samba @@ -209,196 +206,152 @@ HREF="install.html#AEN219" ></DD ><DT >2. <A -HREF="browsing-quick.html" ->Quick Cross Subnet Browsing / Cross Workgroup Browsing guide</A +HREF="improved-browsing.html" +>Improved browsing in samba</A ></DT ><DD ><DL ><DT >2.1. <A -HREF="browsing-quick.html#AEN230" ->Discussion</A +HREF="improved-browsing.html#AEN229" +>Overview of browsing</A ></DT ><DT >2.2. <A -HREF="browsing-quick.html#AEN238" ->Use of the "Remote Announce" parameter</A +HREF="improved-browsing.html#AEN233" +>Browsing support in samba</A ></DT ><DT >2.3. <A -HREF="browsing-quick.html#AEN252" ->Use of the "Remote Browse Sync" parameter</A +HREF="improved-browsing.html#AEN242" +>Problem resolution</A ></DT ><DT >2.4. <A -HREF="browsing-quick.html#AEN257" ->Use of WINS</A -></DT -><DT ->2.5. <A -HREF="browsing-quick.html#AEN268" ->Do NOT use more than one (1) protocol on MS Windows machines</A +HREF="improved-browsing.html#AEN249" +>Browsing across subnets</A ></DT +><DD +><DL ><DT ->2.6. <A -HREF="browsing-quick.html#AEN274" ->Name Resolution Order</A +>2.4.1. <A +HREF="improved-browsing.html#AEN254" +>How does cross subnet browsing work ?</A ></DT ></DL ></DD ><DT ->3. <A -HREF="passdb.html" ->User information database</A -></DT -><DD -><DL -><DT ->3.1. <A -HREF="passdb.html#AEN324" ->Introduction</A +>2.5. <A +HREF="improved-browsing.html#AEN289" +>Setting up a WINS server</A ></DT ><DT ->3.2. <A -HREF="passdb.html#AEN331" ->Important Notes About Security</A +>2.6. <A +HREF="improved-browsing.html#AEN308" +>Setting up Browsing in a WORKGROUP</A ></DT -><DD -><DL ><DT ->3.2.1. <A -HREF="passdb.html#AEN346" ->Advantages of SMB Encryption</A +>2.7. <A +HREF="improved-browsing.html#AEN326" +>Setting up Browsing in a DOMAIN</A ></DT ><DT ->3.2.2. <A -HREF="passdb.html#AEN351" ->Advantages of non-encrypted passwords</A +>2.8. <A +HREF="improved-browsing.html#AEN336" +>Forcing samba to be the master</A ></DT -></DL -></DD ><DT ->3.3. <A -HREF="passdb.html#AEN357" ->The smbpasswd Command</A +>2.9. <A +HREF="improved-browsing.html#AEN345" +>Making samba the domain master</A ></DT ><DT ->3.4. <A -HREF="passdb.html#AEN388" ->Plain text</A +>2.10. <A +HREF="improved-browsing.html#AEN363" +>Note about broadcast addresses</A ></DT ><DT ->3.5. <A -HREF="passdb.html#AEN393" ->TDB</A +>2.11. <A +HREF="improved-browsing.html#AEN366" +>Multiple interfaces</A ></DT +></DL +></DD ><DT ->3.6. <A -HREF="passdb.html#AEN396" ->LDAP</A +>3. <A +HREF="browsing-quick.html" +>Quick Cross Subnet Browsing / Cross Workgroup Browsing guide</A ></DT ><DD ><DL ><DT ->3.6.1. <A -HREF="passdb.html#AEN398" ->Introduction</A -></DT -><DT ->3.6.2. <A -HREF="passdb.html#AEN418" ->Introduction</A -></DT -><DT ->3.6.3. <A -HREF="passdb.html#AEN447" ->Supported LDAP Servers</A -></DT -><DT ->3.6.4. <A -HREF="passdb.html#AEN452" ->Schema and Relationship to the RFC 2307 posixAccount</A +>3.1. <A +HREF="browsing-quick.html#AEN377" +>Discussion</A ></DT ><DT ->3.6.5. <A -HREF="passdb.html#AEN464" ->Configuring Samba with LDAP</A +>3.2. <A +HREF="browsing-quick.html#AEN385" +>Use of the "Remote Announce" parameter</A ></DT ><DT ->3.6.6. <A -HREF="passdb.html#AEN511" ->Accounts and Groups management</A +>3.3. <A +HREF="browsing-quick.html#AEN399" +>Use of the "Remote Browse Sync" parameter</A ></DT ><DT ->3.6.7. <A -HREF="passdb.html#AEN516" ->Security and sambaAccount</A +>3.4. <A +HREF="browsing-quick.html#AEN404" +>Use of WINS</A ></DT ><DT ->3.6.8. <A -HREF="passdb.html#AEN536" ->LDAP specials attributes for sambaAccounts</A +>3.5. <A +HREF="browsing-quick.html#AEN415" +>Do NOT use more than one (1) protocol on MS Windows machines</A ></DT ><DT ->3.6.9. <A -HREF="passdb.html#AEN606" ->Example LDIF Entries for a sambaAccount</A +>3.6. <A +HREF="browsing-quick.html#AEN421" +>Name Resolution Order</A ></DT ></DL ></DD ><DT ->3.7. <A -HREF="passdb.html#AEN614" ->MySQL</A +>4. <A +HREF="pwencrypt.html" +>LanMan and NT Password Encryption in Samba</A ></DT ><DD ><DL ><DT ->3.7.1. <A -HREF="passdb.html#AEN616" ->Building</A -></DT -><DT ->3.7.2. <A -HREF="passdb.html#AEN622" ->Creating the database</A -></DT -><DT ->3.7.3. <A -HREF="passdb.html#AEN632" ->Configuring</A -></DT -><DT ->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 +>4.1. <A +HREF="pwencrypt.html#AEN457" +>Introduction</A ></DT -></DL -></DD ><DT ->3.8. <A -HREF="passdb.html#AEN662" ->Passdb XML plugin</A +>4.2. <A +HREF="pwencrypt.html#AEN462" +>Important Notes About Security</A ></DT ><DD ><DL ><DT ->3.8.1. <A -HREF="passdb.html#AEN664" ->Building</A +>4.2.1. <A +HREF="pwencrypt.html#AEN481" +>Advantages of SMB Encryption</A ></DT ><DT ->3.8.2. <A -HREF="passdb.html#AEN670" ->Usage</A +>4.2.2. <A +HREF="pwencrypt.html#AEN488" +>Advantages of non-encrypted passwords</A ></DT ></DL ></DD +><DT +>4.3. <A +HREF="pwencrypt.html#AEN497" +>The smbpasswd Command</A +></DT ></DL ></DD ></DL diff --git a/docs/htmldocs/lmhosts.5.html b/docs/htmldocs/lmhosts.5.html index 2977cb1227..4d7f11e64b 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.5" +NAME="LMHOSTS" ></A >lmhosts</H1 ><DIV @@ -37,28 +37,24 @@ NAME="AEN8" ><TT CLASS="FILENAME" >lmhosts</TT -> is the <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->Samba</SPAN ->(7)</SPAN +> is the <A +HREF="samba.7.html" +TARGET="_top" +> Samba</A > NetBIOS name to IP address mapping file.</P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN14" +NAME="AEN12" ></A ><H2 >DESCRIPTION</H2 ><P ->This file is part of the <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->Samba</SPAN ->(7)</SPAN +>This file is part of the <A +HREF="samba.7.html" +TARGET="_top" +> Samba</A > suite.</P ><P ><TT @@ -82,7 +78,7 @@ CLASS="FILENAME" ><DIV CLASS="REFSECT1" ><A -NAME="AEN24" +NAME="AEN20" ></A ><H2 >FILE FORMAT</H2 @@ -90,7 +86,7 @@ NAME="AEN24" >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 @@ -111,7 +107,8 @@ NAME="AEN24" ></LI ></UL ><P ->An example follows:</P +>An example follows :</P +><P ><PRE CLASS="PROGRAMLISTING" ># @@ -121,6 +118,7 @@ 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" @@ -135,57 +133,58 @@ CLASS="PROGRAMLISTING" CLASS="FILENAME" >lmhosts</TT > file - is in the same directory as the <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smb.conf</SPAN ->(5)</SPAN + is in the same directory as the <A +HREF="smb.conf.5.html" +TARGET="_top" +> + smb.conf(5)></A > file.</P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN42" +NAME="AEN37" ></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 2.2 of + the Samba suite.</P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN45" +NAME="AEN40" ></A ><H2 >SEE ALSO</H2 ><P -><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 +><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 > </P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN57" +NAME="AEN48" ></A ><H2 >AUTHOR</H2 @@ -204,8 +203,7 @@ 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. The conversion to DocBook - XML 4.2 was done by Alexander Bokovoy.</P + Samba 2.2 was done by Gerald Carter</P ></DIV ></BODY ></HTML diff --git a/docs/htmldocs/msdfs.html b/docs/htmldocs/msdfs.html index f10e0995d5..f6fe1c7e1d 100644 --- a/docs/htmldocs/msdfs.html +++ b/docs/htmldocs/msdfs.html @@ -5,7 +5,8 @@ >Hosting a Microsoft Distributed File System tree on Samba</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -73,17 +74,13 @@ WIDTH="100%"></DIV CLASS="CHAPTER" ><H1 ><A -NAME="MSDFS" -></A ->Chapter 12. Hosting a Microsoft Distributed File System tree on Samba</H1 +NAME="MSDFS">Chapter 13. Hosting a Microsoft Distributed File System tree on Samba</H1 ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1993" -></A ->12.1. Instructions</H1 +NAME="AEN1859">13.1. Instructions</H1 ><P >The Distributed File System (or Dfs) provides a means of separating the logical view of files and directories that users @@ -229,9 +226,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2028" -></A ->12.1.1. Notes</H2 +NAME="AEN1894">13.1.1. Notes</H2 ><P ></P ><UL diff --git a/docs/htmldocs/net.8.html b/docs/htmldocs/net.8.html index 1652fb4141..b7ed1357c3 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.8" +NAME="NET" ></A >net</H1 ><DIV @@ -48,12 +48,10 @@ NAME="AEN31" ><H2 >DESCRIPTION</H2 ><P ->This tool is part of the <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->Samba</SPAN ->(7)</SPAN +>This tool is part of the <A +HREF="samba.7.html" +TARGET="_top" +> Samba</A > suite.</P ><P >The samba net utility is meant to work just like the net utility @@ -62,7 +60,7 @@ CLASS="REFENTRYTITLE" ><DIV CLASS="REFSECT1" ><A -NAME="AEN38" +NAME="AEN36" ></A ><H2 >OPTIONS</H2 @@ -83,8 +81,7 @@ 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 @@ -105,8 +102,7 @@ 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 @@ -134,8 +130,7 @@ 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 @@ -220,7 +215,7 @@ CLASS="FILENAME" ><DIV CLASS="REFSECT1" ><A -NAME="AEN118" +NAME="AEN116" ></A ><H2 >TIME</H2 @@ -250,10 +245,7 @@ CLASS="COMMAND" >SYSTEM</DT ><DD ><P -> Displays the time on the remote server in a format ready for <B -CLASS="COMMAND" ->/bin/date</B -> +> Displays the time on the remote server in a format ready for /bin/date </P ></DD ><DT @@ -261,10 +253,7 @@ CLASS="COMMAND" ><DD ><P > Tries to set the date and time of the local server to that on - the remote server using <B -CLASS="COMMAND" ->/bin/date</B ->. + the remote server using /bin/date. </P ></DD ><DT @@ -280,7 +269,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN142" +NAME="AEN138" ></A ><H2 >RPC</H2 @@ -331,7 +320,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 @@ -384,7 +373,7 @@ CLASS="VARIABLELIST" ><DIV CLASS="REFSECT1" ><A -NAME="AEN195" +NAME="AEN191" ></A ><H2 >VERSION</H2 @@ -395,7 +384,7 @@ NAME="AEN195" ><DIV CLASS="REFSECT1" ><A -NAME="AEN198" +NAME="AEN194" ></A ><H2 >AUTHOR</H2 diff --git a/docs/htmldocs/nmbd.8.html b/docs/htmldocs/nmbd.8.html index 87a042a912..1183a14522 100644 --- a/docs/htmldocs/nmbd.8.html +++ b/docs/htmldocs/nmbd.8.html @@ -1,11 +1,12 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"> <HTML ><HEAD ><TITLE >nmbd</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"></HEAD +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"></HEAD ><BODY CLASS="REFENTRY" BGCOLOR="#FFFFFF" @@ -15,9 +16,7 @@ VLINK="#840084" ALINK="#0000FF" ><H1 ><A -NAME="NMBD.8" -></A ->nmbd</H1 +NAME="NMBD">nmbd</H1 ><DIV CLASS="REFNAMEDIV" ><A @@ -30,15 +29,13 @@ NAME="AEN5" ><DIV CLASS="REFSYNOPSISDIV" ><A -NAME="AEN8" -></A -><H2 +NAME="AEN8"><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" @@ -48,13 +45,7 @@ NAME="AEN25" ><H2 >DESCRIPTION</H2 ><P ->This program is part of the <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->Samba</SPAN ->(7)</SPAN -> suite.</P +>This program is part of the Samba suite.</P ><P ><B CLASS="COMMAND" @@ -78,12 +69,9 @@ 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 <SPAN -CLASS="emphasis" -><I + but this can be overridden with the <I CLASS="EMPHASIS" >-n</I -></SPAN > option (see OPTIONS below). Thus <B CLASS="COMMAND" @@ -94,12 +82,13 @@ CLASS="COMMAND" CLASS="COMMAND" >nmbd</B > to respond on can be set - via parameters in the <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smb.conf</SPAN ->(5)</SPAN + via parameters in the <A +HREF="smb.conf.5.html" +TARGET="_top" +><TT +CLASS="FILENAME" +> smb.conf(5)</TT +></A > configuration file.</P ><P ><B @@ -122,7 +111,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN46" +NAME="AEN42" ></A ><H2 >OPTIONS</H2 @@ -215,9 +204,9 @@ CLASS="COMMAND" CLASS="COMMAND" >nmbd</B > also logs to standard - output, as if the <TT -CLASS="CONSTANT" ->-S</TT + output, as if the <B +CLASS="COMMAND" +>-S</B > parameter had been given. </P ></DD @@ -244,7 +233,7 @@ CLASS="COMMAND" >.</P ></DD ><DT ->-H <filename></DT +>-H <filename></DT ><DD ><P >NetBIOS lmhosts file. The lmhosts @@ -253,39 +242,28 @@ CLASS="COMMAND" resolution mechanism <A HREF="smb.conf.5.html#nameresolveorder" TARGET="_top" -><TT -CLASS="PARAMETER" -><I ->name resolve - order</I -></TT +> name resolve order</A +> described in <A +HREF="smb.conf.5.html" +TARGET="_top" +> <TT +CLASS="FILENAME" +>smb.conf(5)</TT ></A -> 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 +> + to resolve any NetBIOS name queries needed by the server. Note + that the contents of this file are <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 <SPAN -CLASS="emphasis" -><I + from this host <I CLASS="EMPHASIS" >ONLY</I -></SPAN >.</P ><P >The default path to this file is compiled into @@ -300,14 +278,17 @@ CLASS="FILENAME" > or <TT CLASS="FILENAME" ->/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 +>/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 ></DD ><DT >-V</DT @@ -320,7 +301,7 @@ CLASS="COMMAND" >.</P ></DD ><DT ->-d <debug level></DT +>-d <debug level></DT ><DD ><P >debuglevel is an integer @@ -344,23 +325,19 @@ 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="PARAMETER" -><I ->log level</I -></TT +CLASS="FILENAME" +> smb.conf(5)</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 @@ -380,12 +357,9 @@ CLASS="FILENAME" <TT CLASS="FILENAME" >/var/log/log.nmb</TT ->. <SPAN -CLASS="emphasis" -><I +>. <I CLASS="EMPHASIS" >Beware:</I -></SPAN > If the directory specified does not exist, <B CLASS="COMMAND" @@ -395,7 +369,7 @@ CLASS="COMMAND" </P ></DD ><DT ->-n <primary NetBIOS name></DT +>-n <primary NetBIOS name></DT ><DD ><P >This option allows you to override @@ -403,31 +377,24 @@ CLASS="COMMAND" to setting the <A HREF="smb.conf.5.html#netbiosname" TARGET="_top" -><TT -CLASS="PARAMETER" -><I ->NetBIOS - name</I -></TT +> NetBIOS name</A +> parameter in the <A +HREF="smb.conf.5.html" +TARGET="_top" +> + <TT +CLASS="FILENAME" +>smb.conf</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 - <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smb.conf</SPAN ->(5)</SPAN + <TT +CLASS="FILENAME" +>smb.conf</TT >.</P ></DD ><DT ->-p <UDP port number></DT +>-p <UDP port number></DT ><DD ><P >UDP port number is a positive integer value. @@ -440,7 +407,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 @@ -451,12 +418,13 @@ CLASS="FILENAME" this may be changed when Samba is autoconfigured.</P ><P >The file specified contains the configuration details - required by the server. See <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smb.conf</SPAN ->(5)</SPAN + required by the server. See <A +HREF="smb.conf.5.html" +TARGET="_top" +> <TT +CLASS="FILENAME" +>smb.conf(5)</TT +></A > for more information. </P ></DD @@ -466,7 +434,7 @@ CLASS="REFENTRYTITLE" ><DIV CLASS="REFSECT1" ><A -NAME="AEN162" +NAME="AEN148" ></A ><H2 >FILES</H2 @@ -489,9 +457,9 @@ CLASS="COMMAND" > meta-daemon, this file must contain suitable startup information for the meta-daemon. See the <A -HREF="install.html" +HREF="UNIX_INSTALL.html" TARGET="_top" ->install</A +>UNIX_INSTALL.html</A > document for details. </P @@ -509,9 +477,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="install.html" +HREF="UNIX_INSTALL.html" TARGET="_top" ->"How to Install and Test SAMBA"</A +>UNIX_INSTALL.html</A > document for details.</P ></DD @@ -530,9 +498,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="install.html" +HREF="UNIX_INSTALL.html" TARGET="_top" ->"How to Install and Test SAMBA"</A +>UNIX_INSTALL.html</A > document for details.</P ></DD @@ -543,39 +511,34 @@ CLASS="FILENAME" ></DT ><DD ><P ->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 +>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 install this file are <TT CLASS="FILENAME" >/usr/samba/lib/smb.conf</TT > and <TT CLASS="FILENAME" ->/etc/samba/smb.conf</TT +>/etc/smb.conf</TT >.</P ><P >When run as a WINS server (see the <A HREF="smb.conf.5.html#WINSSUPPORT" TARGET="_top" -><TT -CLASS="CONSTANT" ->wins support</TT -></A +>wins support</A > - parameter in the <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smb.conf</SPAN ->(5)</SPAN + parameter in the <TT +CLASS="FILENAME" +>smb.conf(5)</TT > man page), <B CLASS="COMMAND" @@ -594,27 +557,19 @@ CLASS="FILENAME" >If <B CLASS="COMMAND" >nmbd</B -> is acting as a <SPAN -CLASS="emphasis" -><I +> is acting as a <I CLASS="EMPHASIS" > browse master</I -></SPAN > (see the <A HREF="smb.conf.5.html#LOCALMASTER" TARGET="_top" -><TT -CLASS="CONSTANT" ->local master</TT -></A +>local master</A > - parameter in the <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smb.conf</SPAN ->(5)</SPAN -> man page, <B + parameter in the <TT +CLASS="FILENAME" +>smb.conf(5)</TT +> man page, + <B CLASS="COMMAND" >nmbd</B > @@ -635,7 +590,7 @@ CLASS="FILENAME" ><DIV CLASS="REFSECT1" ><A -NAME="AEN216" +NAME="AEN195" ></A ><H2 >SIGNALS</H2 @@ -644,12 +599,9 @@ NAME="AEN216" CLASS="COMMAND" >nmbd</B > process it is recommended - that SIGKILL (-9) <SPAN -CLASS="emphasis" -><I + that SIGKILL (-9) <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 @@ -684,22 +636,23 @@ CLASS="FILENAME" >log.nmb</TT > file.</P ><P ->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 +>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 at a normally low log level.</P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN233" +NAME="AEN211" ></A ><H2 >VERSION</H2 @@ -710,49 +663,54 @@ NAME="AEN233" ><DIV CLASS="REFSECT1" ><A -NAME="AEN236" +NAME="AEN214" ></A ><H2 >SEE ALSO</H2 ><P -> <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 +><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 CLASS="FILENAME" >rfc1001.txt</TT >, <TT @@ -770,7 +728,7 @@ TARGET="_top" ><DIV CLASS="REFSECT1" ><A -NAME="AEN260" +NAME="AEN231" ></A ><H2 >AUTHOR</H2 @@ -782,14 +740,14 @@ NAME="AEN260" ><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. The conversion to DocBook - XML 4.2 for Samba 3.0 was done by Alexander Bokovoy.</P + Samba 2.2 was done by Gerald Carter</P ></DIV ></BODY ></HTML diff --git a/docs/htmldocs/nmblookup.1.html b/docs/htmldocs/nmblookup.1.html index 9e6da1c7b2..2ce322990f 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,12 +48,10 @@ NAME="AEN25" ><H2 >DESCRIPTION</H2 ><P ->This tool is part of the <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->Samba</SPAN ->(7)</SPAN +>This tool is part of the <A +HREF="samba.7.html" +TARGET="_top" +> Samba</A > suite.</P ><P ><B @@ -68,7 +66,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN33" +NAME="AEN31" ></A ><H2 >OPTIONS</H2 @@ -111,7 +109,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 @@ -132,13 +130,12 @@ 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 <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->nmbd</SPAN ->(8)</SPAN -> daemon is running on this machine it also binds to this port. + 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. </P ></DD ><DT @@ -176,12 +173,9 @@ CLASS="PARAMETER" ></TT > </A -> parameter of the <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smb.conf</SPAN ->(5)</SPAN +> parameter of the <TT +CLASS="FILENAME" +>smb.conf (5)</TT > file. </P ></DD @@ -317,7 +311,7 @@ CLASS="EMPHASIS" ><DIV CLASS="REFSECT1" ><A -NAME="AEN121" +NAME="AEN115" ></A ><H2 >EXAMPLES</H2 @@ -330,11 +324,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" @@ -354,7 +348,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN133" +NAME="AEN127" ></A ><H2 >VERSION</H2 @@ -365,35 +359,34 @@ NAME="AEN133" ><DIV CLASS="REFSECT1" ><A -NAME="AEN136" +NAME="AEN130" ></A ><H2 >SEE ALSO</H2 ><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 +><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 ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN148" +NAME="AEN137" ></A ><H2 >AUTHOR</H2 @@ -405,14 +398,14 @@ NAME="AEN148" ><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. The conversion to DocBook - XML 4.2 for Samba 3.0 was done by Alexander Bokovoy.</P + Samba 2.2 was done by Gerald Carter</P ></DIV ></BODY ></HTML diff --git a/docs/htmldocs/optional.html b/docs/htmldocs/optional.html index b5564b9f26..b15515ddab 100644 --- a/docs/htmldocs/optional.html +++ b/docs/htmldocs/optional.html @@ -5,12 +5,13 @@ >Optional configuration</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK REL="PREVIOUS" -TITLE="Samba as a NT4 or Win2k domain member" +TITLE="Samba as a NT4 domain member" HREF="domain-security.html"><LINK REL="NEXT" TITLE="Integrating MS Windows networks with Samba" @@ -68,9 +69,7 @@ WIDTH="100%"></DIV ><DIV CLASS="PART" ><A -NAME="OPTIONAL" -></A -><DIV +NAME="OPTIONAL"><DIV CLASS="TITLEPAGE" ><H1 CLASS="TITLE" @@ -78,9 +77,7 @@ CLASS="TITLE" ><DIV CLASS="PARTINTRO" ><A -NAME="AEN1499" -></A -><H1 +NAME="AEN1360"><H1 >Introduction</H1 ><P >Samba has several features that you might want or might not want to use. The chapters in this @@ -94,51 +91,51 @@ CLASS="TOC" >Table of Contents</B ></DT ><DT ->9. <A +>10. <A HREF="integrate-ms-networks.html" >Integrating MS Windows networks with Samba</A ></DT ><DD ><DL ><DT ->9.1. <A -HREF="integrate-ms-networks.html#AEN1513" +>10.1. <A +HREF="integrate-ms-networks.html#AEN1374" >Agenda</A ></DT ><DT ->9.2. <A -HREF="integrate-ms-networks.html#AEN1535" +>10.2. <A +HREF="integrate-ms-networks.html#AEN1396" >Name Resolution in a pure Unix/Linux world</A ></DT ><DD ><DL ><DT ->9.2.1. <A -HREF="integrate-ms-networks.html#AEN1551" +>10.2.1. <A +HREF="integrate-ms-networks.html#AEN1412" ><TT CLASS="FILENAME" >/etc/hosts</TT ></A ></DT ><DT ->9.2.2. <A -HREF="integrate-ms-networks.html#AEN1567" +>10.2.2. <A +HREF="integrate-ms-networks.html#AEN1428" ><TT CLASS="FILENAME" >/etc/resolv.conf</TT ></A ></DT ><DT ->9.2.3. <A -HREF="integrate-ms-networks.html#AEN1578" +>10.2.3. <A +HREF="integrate-ms-networks.html#AEN1439" ><TT CLASS="FILENAME" >/etc/host.conf</TT ></A ></DT ><DT ->9.2.4. <A -HREF="integrate-ms-networks.html#AEN1586" +>10.2.4. <A +HREF="integrate-ms-networks.html#AEN1447" ><TT CLASS="FILENAME" >/etc/nsswitch.conf</TT @@ -147,140 +144,140 @@ CLASS="FILENAME" ></DL ></DD ><DT ->9.3. <A -HREF="integrate-ms-networks.html#AEN1598" +>10.3. <A +HREF="integrate-ms-networks.html#AEN1459" >Name resolution as used within MS Windows networking</A ></DT ><DD ><DL ><DT ->9.3.1. <A -HREF="integrate-ms-networks.html#AEN1610" +>10.3.1. <A +HREF="integrate-ms-networks.html#AEN1471" >The NetBIOS Name Cache</A ></DT ><DT ->9.3.2. <A -HREF="integrate-ms-networks.html#AEN1615" +>10.3.2. <A +HREF="integrate-ms-networks.html#AEN1476" >The LMHOSTS file</A ></DT ><DT ->9.3.3. <A -HREF="integrate-ms-networks.html#AEN1623" +>10.3.3. <A +HREF="integrate-ms-networks.html#AEN1484" >HOSTS file</A ></DT ><DT ->9.3.4. <A -HREF="integrate-ms-networks.html#AEN1628" +>10.3.4. <A +HREF="integrate-ms-networks.html#AEN1489" >DNS Lookup</A ></DT ><DT ->9.3.5. <A -HREF="integrate-ms-networks.html#AEN1631" +>10.3.5. <A +HREF="integrate-ms-networks.html#AEN1492" >WINS Lookup</A ></DT ></DL ></DD ><DT ->9.4. <A -HREF="integrate-ms-networks.html#AEN1643" +>10.4. <A +HREF="integrate-ms-networks.html#AEN1504" >How browsing functions and how to deploy stable and dependable browsing using Samba</A ></DT ><DT ->9.5. <A -HREF="integrate-ms-networks.html#AEN1653" +>10.5. <A +HREF="integrate-ms-networks.html#AEN1514" >MS Windows security options and how to configure Samba for seemless integration</A ></DT ><DD ><DL ><DT ->9.5.1. <A -HREF="integrate-ms-networks.html#AEN1681" +>10.5.1. <A +HREF="integrate-ms-networks.html#AEN1542" >Use MS Windows NT as an authentication server</A ></DT ><DT ->9.5.2. <A -HREF="integrate-ms-networks.html#AEN1689" +>10.5.2. <A +HREF="integrate-ms-networks.html#AEN1550" >Make Samba a member of an MS Windows NT security domain</A ></DT ><DT ->9.5.3. <A -HREF="integrate-ms-networks.html#AEN1706" +>10.5.3. <A +HREF="integrate-ms-networks.html#AEN1567" >Configure Samba as an authentication server</A ></DT ></DL ></DD ><DT ->9.6. <A -HREF="integrate-ms-networks.html#AEN1723" +>10.6. <A +HREF="integrate-ms-networks.html#AEN1584" >Conclusions</A ></DT ></DL ></DD ><DT ->10. <A +>11. <A HREF="unix-permissions.html" >UNIX Permission Bits and Windows NT Access Control Lists</A ></DT ><DD ><DL ><DT ->10.1. <A -HREF="unix-permissions.html#AEN1744" +>11.1. <A +HREF="unix-permissions.html#AEN1605" >Viewing and changing UNIX permissions using the NT security dialogs</A ></DT ><DT ->10.2. <A -HREF="unix-permissions.html#AEN1748" +>11.2. <A +HREF="unix-permissions.html#AEN1614" >How to view file security on a Samba share</A ></DT ><DT ->10.3. <A -HREF="unix-permissions.html#AEN1759" +>11.3. <A +HREF="unix-permissions.html#AEN1625" >Viewing file ownership</A ></DT ><DT ->10.4. <A -HREF="unix-permissions.html#AEN1779" +>11.4. <A +HREF="unix-permissions.html#AEN1645" >Viewing file or directory permissions</A ></DT ><DD ><DL ><DT ->10.4.1. <A -HREF="unix-permissions.html#AEN1794" +>11.4.1. <A +HREF="unix-permissions.html#AEN1660" >File Permissions</A ></DT ><DT ->10.4.2. <A -HREF="unix-permissions.html#AEN1808" +>11.4.2. <A +HREF="unix-permissions.html#AEN1674" >Directory Permissions</A ></DT ></DL ></DD ><DT ->10.5. <A -HREF="unix-permissions.html#AEN1815" +>11.5. <A +HREF="unix-permissions.html#AEN1681" >Modifying file or directory permissions</A ></DT ><DT ->10.6. <A -HREF="unix-permissions.html#AEN1837" +>11.6. <A +HREF="unix-permissions.html#AEN1703" >Interaction with the standard Samba create mask parameters</A ></DT ><DT ->10.7. <A -HREF="unix-permissions.html#AEN1901" +>11.7. <A +HREF="unix-permissions.html#AEN1767" >Interaction with the standard Samba file attribute mapping</A ></DT ></DL ></DD ><DT ->11. <A +>12. <A HREF="pam.html" >Configuring PAM for distributed but centrally managed authentication</A @@ -288,39 +285,39 @@ managed authentication</A ><DD ><DL ><DT ->11.1. <A -HREF="pam.html#AEN1922" +>12.1. <A +HREF="pam.html#AEN1788" >Samba and PAM</A ></DT ><DT ->11.2. <A -HREF="pam.html#AEN1966" +>12.2. <A +HREF="pam.html#AEN1832" >Distributed Authentication</A ></DT ><DT ->11.3. <A -HREF="pam.html#AEN1973" +>12.3. <A +HREF="pam.html#AEN1839" >PAM Configuration in smb.conf</A ></DT ></DL ></DD ><DT ->12. <A +>13. <A HREF="msdfs.html" >Hosting a Microsoft Distributed File System tree on Samba</A ></DT ><DD ><DL ><DT ->12.1. <A -HREF="msdfs.html#AEN1993" +>13.1. <A +HREF="msdfs.html#AEN1859" >Instructions</A ></DT ><DD ><DL ><DT ->12.1.1. <A -HREF="msdfs.html#AEN2028" +>13.1.1. <A +HREF="msdfs.html#AEN1894" >Notes</A ></DT ></DL @@ -328,130 +325,130 @@ HREF="msdfs.html#AEN2028" ></DL ></DD ><DT ->13. <A +>14. <A HREF="printing.html" >Printing Support</A ></DT ><DD ><DL ><DT ->13.1. <A -HREF="printing.html#AEN2054" +>14.1. <A +HREF="printing.html#AEN1920" >Introduction</A ></DT ><DT ->13.2. <A -HREF="printing.html#AEN2076" +>14.2. <A +HREF="printing.html#AEN1942" >Configuration</A ></DT ><DD ><DL ><DT ->13.2.1. <A -HREF="printing.html#AEN2084" +>14.2.1. <A +HREF="printing.html#AEN1950" >Creating [print$]</A ></DT ><DT ->13.2.2. <A -HREF="printing.html#AEN2119" +>14.2.2. <A +HREF="printing.html#AEN1985" >Setting Drivers for Existing Printers</A ></DT ><DT ->13.2.3. <A -HREF="printing.html#AEN2135" +>14.2.3. <A +HREF="printing.html#AEN2001" >Support a large number of printers</A ></DT ><DT ->13.2.4. <A -HREF="printing.html#AEN2146" +>14.2.4. <A +HREF="printing.html#AEN2012" >Adding New Printers via the Windows NT APW</A ></DT ><DT ->13.2.5. <A -HREF="printing.html#AEN2176" +>14.2.5. <A +HREF="printing.html#AEN2042" >Samba and Printer Ports</A ></DT ></DL ></DD ><DT ->13.3. <A -HREF="printing.html#AEN2184" +>14.3. <A +HREF="printing.html#AEN2050" >The Imprints Toolset</A ></DT ><DD ><DL ><DT ->13.3.1. <A -HREF="printing.html#AEN2188" +>14.3.1. <A +HREF="printing.html#AEN2054" >What is Imprints?</A ></DT ><DT ->13.3.2. <A -HREF="printing.html#AEN2198" +>14.3.2. <A +HREF="printing.html#AEN2064" >Creating Printer Driver Packages</A ></DT ><DT ->13.3.3. <A -HREF="printing.html#AEN2201" +>14.3.3. <A +HREF="printing.html#AEN2067" >The Imprints server</A ></DT ><DT ->13.3.4. <A -HREF="printing.html#AEN2205" +>14.3.4. <A +HREF="printing.html#AEN2071" >The Installation Client</A ></DT ></DL ></DD ><DT ->13.4. <A -HREF="printing.html#AEN2227" +>14.4. <A +HREF="printing.html#AEN2093" >Diagnosis</A ></DT ><DD ><DL ><DT ->13.4.1. <A -HREF="printing.html#AEN2229" +>14.4.1. <A +HREF="printing.html#AEN2095" >Introduction</A ></DT ><DT ->13.4.2. <A -HREF="printing.html#AEN2245" +>14.4.2. <A +HREF="printing.html#AEN2111" >Debugging printer problems</A ></DT ><DT ->13.4.3. <A -HREF="printing.html#AEN2254" +>14.4.3. <A +HREF="printing.html#AEN2120" >What printers do I have?</A ></DT ><DT ->13.4.4. <A -HREF="printing.html#AEN2262" +>14.4.4. <A +HREF="printing.html#AEN2128" >Setting up printcap and print servers</A ></DT ><DT ->13.4.5. <A -HREF="printing.html#AEN2290" +>14.4.5. <A +HREF="printing.html#AEN2156" >Job sent, no output</A ></DT ><DT ->13.4.6. <A -HREF="printing.html#AEN2301" +>14.4.6. <A +HREF="printing.html#AEN2167" >Job sent, strange output</A ></DT ><DT ->13.4.7. <A -HREF="printing.html#AEN2313" +>14.4.7. <A +HREF="printing.html#AEN2179" >Raw PostScript printed</A ></DT ><DT ->13.4.8. <A -HREF="printing.html#AEN2316" +>14.4.8. <A +HREF="printing.html#AEN2182" >Advanced Printing</A ></DT ><DT ->13.4.9. <A -HREF="printing.html#AEN2319" +>14.4.9. <A +HREF="printing.html#AEN2185" >Real debugging</A ></DT ></DL @@ -459,235 +456,205 @@ HREF="printing.html#AEN2319" ></DL ></DD ><DT ->14. <A +>15. <A HREF="winbind.html" >Unified Logons between Windows NT and UNIX using Winbind</A ></DT ><DD ><DL ><DT ->14.1. <A -HREF="winbind.html#AEN2360" +>15.1. <A +HREF="winbind.html#AEN2225" >Abstract</A ></DT ><DT ->14.2. <A -HREF="winbind.html#AEN2364" +>15.2. <A +HREF="winbind.html#AEN2229" >Introduction</A ></DT ><DT ->14.3. <A -HREF="winbind.html#AEN2377" +>15.3. <A +HREF="winbind.html#AEN2242" >What Winbind Provides</A ></DT ><DD ><DL ><DT ->14.3.1. <A -HREF="winbind.html#AEN2384" +>15.3.1. <A +HREF="winbind.html#AEN2249" >Target Uses</A ></DT ></DL ></DD ><DT ->14.4. <A -HREF="winbind.html#AEN2388" +>15.4. <A +HREF="winbind.html#AEN2253" >How Winbind Works</A ></DT ><DD ><DL ><DT ->14.4.1. <A -HREF="winbind.html#AEN2393" +>15.4.1. <A +HREF="winbind.html#AEN2258" >Microsoft Remote Procedure Calls</A ></DT ><DT ->14.4.2. <A -HREF="winbind.html#AEN2397" ->Microsoft Active Directory Services</A -></DT -><DT ->14.4.3. <A -HREF="winbind.html#AEN2400" +>15.4.2. <A +HREF="winbind.html#AEN2262" >Name Service Switch</A ></DT ><DT ->14.4.4. <A -HREF="winbind.html#AEN2416" +>15.4.3. <A +HREF="winbind.html#AEN2278" >Pluggable Authentication Modules</A ></DT ><DT ->14.4.5. <A -HREF="winbind.html#AEN2424" +>15.4.4. <A +HREF="winbind.html#AEN2286" >User and Group ID Allocation</A ></DT ><DT ->14.4.6. <A -HREF="winbind.html#AEN2428" +>15.4.5. <A +HREF="winbind.html#AEN2290" >Result Caching</A ></DT ></DL ></DD ><DT ->14.5. <A -HREF="winbind.html#AEN2431" +>15.5. <A +HREF="winbind.html#AEN2293" >Installation and Configuration</A ></DT ><DD ><DL ><DT ->14.5.1. <A -HREF="winbind.html#AEN2438" +>15.5.1. <A +HREF="winbind.html#AEN2300" >Introduction</A ></DT ><DT ->14.5.2. <A -HREF="winbind.html#AEN2451" +>15.5.2. <A +HREF="winbind.html#AEN2313" >Requirements</A ></DT ><DT ->14.5.3. <A -HREF="winbind.html#AEN2465" +>15.5.3. <A +HREF="winbind.html#AEN2327" >Testing Things Out</A ></DT ></DL ></DD ><DT ->14.6. <A -HREF="winbind.html#AEN2680" +>15.6. <A +HREF="winbind.html#AEN2542" >Limitations</A ></DT ><DT ->14.7. <A -HREF="winbind.html#AEN2690" +>15.7. <A +HREF="winbind.html#AEN2552" >Conclusion</A ></DT ></DL ></DD ><DT ->15. <A -HREF="improved-browsing.html" ->Improved browsing in samba</A +>16. <A +HREF="pdb-mysql.html" +>Passdb MySQL plugin</A ></DT ><DD ><DL ><DT ->15.1. <A -HREF="improved-browsing.html#AEN2700" ->Overview of browsing</A -></DT -><DT ->15.2. <A -HREF="improved-browsing.html#AEN2704" ->Browsing support in samba</A +>16.1. <A +HREF="pdb-mysql.html#AEN2566" +>Building</A ></DT ><DT ->15.3. <A -HREF="improved-browsing.html#AEN2713" ->Problem resolution</A +>16.2. <A +HREF="pdb-mysql.html#AEN2572" +>Configuring</A ></DT ><DT ->15.4. <A -HREF="improved-browsing.html#AEN2720" ->Browsing across subnets</A +>16.3. <A +HREF="pdb-mysql.html#AEN2589" +>Using plaintext passwords or encrypted password</A ></DT -><DD -><DL ><DT ->15.4.1. <A -HREF="improved-browsing.html#AEN2725" ->How does cross subnet browsing work ?</A +>16.4. <A +HREF="pdb-mysql.html#AEN2594" +>Getting non-column data from the table</A ></DT ></DL ></DD ><DT ->15.5. <A -HREF="improved-browsing.html#AEN2760" ->Setting up a WINS server</A -></DT -><DT ->15.6. <A -HREF="improved-browsing.html#AEN2779" ->Setting up Browsing in a WORKGROUP</A -></DT -><DT ->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 +>17. <A +HREF="pdb-xml.html" +>Passdb XML plugin</A ></DT +><DD +><DL ><DT ->15.10. <A -HREF="improved-browsing.html#AEN2834" ->Note about broadcast addresses</A +>17.1. <A +HREF="pdb-xml.html#AEN2613" +>Building</A ></DT ><DT ->15.11. <A -HREF="improved-browsing.html#AEN2837" ->Multiple interfaces</A +>17.2. <A +HREF="pdb-xml.html#AEN2619" +>Usage</A ></DT ></DL ></DD ><DT ->16. <A +>18. <A HREF="vfs.html" >Stackable VFS modules</A ></DT ><DD ><DL ><DT ->16.1. <A -HREF="vfs.html#AEN2855" +>18.1. <A +HREF="vfs.html#AEN2640" >Introduction and configuration</A ></DT ><DT ->16.2. <A -HREF="vfs.html#AEN2864" +>18.2. <A +HREF="vfs.html#AEN2649" >Included modules</A ></DT ><DD ><DL ><DT ->16.2.1. <A -HREF="vfs.html#AEN2866" +>18.2.1. <A +HREF="vfs.html#AEN2651" >audit</A ></DT ><DT ->16.2.2. <A -HREF="vfs.html#AEN2874" +>18.2.2. <A +HREF="vfs.html#AEN2659" >recycle</A ></DT ><DT ->16.2.3. <A -HREF="vfs.html#AEN2911" +>18.2.3. <A +HREF="vfs.html#AEN2696" >netatalk</A ></DT ></DL ></DD ><DT ->16.3. <A -HREF="vfs.html#AEN2918" +>18.3. <A +HREF="vfs.html#AEN2703" >VFS modules available elsewhere</A ></DT ><DD ><DL ><DT ->16.3.1. <A -HREF="vfs.html#AEN2922" +>18.3.1. <A +HREF="vfs.html#AEN2707" >DatabaseFS</A ></DT ><DT ->16.3.2. <A -HREF="vfs.html#AEN2930" +>18.3.2. <A +HREF="vfs.html#AEN2715" >vscan</A ></DT ></DL @@ -695,32 +662,105 @@ HREF="vfs.html#AEN2930" ></DL ></DD ><DT ->17. <A +>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 HREF="cvs-access.html" ->Access Samba source code via CVS</A +>HOWTO Access Samba source code via CVS</A ></DT ><DD ><DL ><DT ->17.1. <A -HREF="cvs-access.html#AEN2942" +>20.1. <A +HREF="cvs-access.html#AEN2964" >Introduction</A ></DT ><DT ->17.2. <A -HREF="cvs-access.html#AEN2947" +>20.2. <A +HREF="cvs-access.html#AEN2969" >CVS Access to samba.org</A ></DT ><DD ><DL ><DT ->17.2.1. <A -HREF="cvs-access.html#AEN2950" +>20.2.1. <A +HREF="cvs-access.html#AEN2972" >Access via CVSweb</A ></DT ><DT ->17.2.2. <A -HREF="cvs-access.html#AEN2955" +>20.2.2. <A +HREF="cvs-access.html#AEN2977" >Access via cvs</A ></DT ></DL @@ -728,117 +768,69 @@ HREF="cvs-access.html#AEN2955" ></DL ></DD ><DT ->18. <A +>21. <A HREF="groupmapping.html" >Group mapping HOWTO</A ></DT ><DT ->19. <A +>22. <A HREF="speed.html" >Samba performance issues</A ></DT ><DD ><DL ><DT ->19.1. <A -HREF="speed.html#AEN3033" +>22.1. <A +HREF="speed.html#AEN3055" >Comparisons</A ></DT ><DT ->19.2. <A -HREF="speed.html#AEN3039" +>22.2. <A +HREF="speed.html#AEN3061" >Socket options</A ></DT ><DT ->19.3. <A -HREF="speed.html#AEN3046" +>22.3. <A +HREF="speed.html#AEN3068" >Read size</A ></DT ><DT ->19.4. <A -HREF="speed.html#AEN3051" +>22.4. <A +HREF="speed.html#AEN3073" >Max xmit</A ></DT ><DT ->19.5. <A -HREF="speed.html#AEN3056" +>22.5. <A +HREF="speed.html#AEN3078" >Log level</A ></DT ><DT ->19.6. <A -HREF="speed.html#AEN3059" +>22.6. <A +HREF="speed.html#AEN3081" >Read raw</A ></DT ><DT ->19.7. <A -HREF="speed.html#AEN3064" +>22.7. <A +HREF="speed.html#AEN3086" >Write raw</A ></DT ><DT ->19.8. <A -HREF="speed.html#AEN3068" +>22.8. <A +HREF="speed.html#AEN3090" >Slow Clients</A ></DT ><DT ->19.9. <A -HREF="speed.html#AEN3072" +>22.9. <A +HREF="speed.html#AEN3094" >Slow Logins</A ></DT ><DT ->19.10. <A -HREF="speed.html#AEN3075" +>22.10. <A +HREF="speed.html#AEN3097" >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 @@ -887,7 +879,7 @@ ACCESSKEY="N" WIDTH="33%" ALIGN="left" VALIGN="top" ->Samba as a NT4 or Win2k domain member</TD +>Samba as a NT4 domain member</TD ><TD WIDTH="34%" ALIGN="center" diff --git a/docs/htmldocs/other-clients.html b/docs/htmldocs/other-clients.html index 7f0f99319e..130c9691e7 100644 --- a/docs/htmldocs/other-clients.html +++ b/docs/htmldocs/other-clients.html @@ -5,7 +5,8 @@ >Samba and other CIFS clients</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -72,9 +73,7 @@ WIDTH="100%"></DIV CLASS="CHAPTER" ><H1 ><A -NAME="OTHER-CLIENTS" -></A ->Chapter 22. Samba and other CIFS clients</H1 +NAME="OTHER-CLIENTS">Chapter 24. Samba and other CIFS clients</H1 ><P >This chapter contains client-specific information.</P ><DIV @@ -82,9 +81,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3311" -></A ->22.1. Macintosh clients?</H1 +NAME="AEN3199">24.1. Macintosh clients?</H1 ><P >Yes. <A HREF="http://www.thursby.com/" @@ -128,17 +125,13 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3320" -></A ->22.2. OS2 Client</H1 +NAME="AEN3208">24.2. OS2 Client</H1 ><DIV CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3322" -></A ->22.2.1. How can I configure OS/2 Warp Connect or +NAME="AEN3210">24.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 @@ -195,9 +188,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3337" -></A ->22.2.2. How can I configure OS/2 Warp 3 (not Connect), +NAME="AEN3225">24.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 @@ -239,9 +230,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3346" -></A ->22.2.3. Are there any other issues when OS/2 (any version) +NAME="AEN3234">24.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 @@ -261,9 +250,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3350" -></A ->22.2.4. How do I get printer driver download working +NAME="AEN3238">24.2.4. How do I get printer driver download working for OS/2 clients?</H2 ><P >First, create a share called [PRINTDRV] that is @@ -312,17 +299,13 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3360" -></A ->22.3. Windows for Workgroups</H1 +NAME="AEN3248">24.3. Windows for Workgroups</H1 ><DIV CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3362" -></A ->22.3.1. Use latest TCP/IP stack from Microsoft</H2 +NAME="AEN3250">24.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 @@ -342,9 +325,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3367" -></A ->22.3.2. Delete .pwl files after password change</H2 +NAME="AEN3255">24.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 @@ -362,9 +343,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3372" -></A ->22.3.3. Configure WfW password handling</H2 +NAME="AEN3260">24.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 @@ -381,9 +360,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3376" -></A ->22.3.4. Case handling of passwords</H2 +NAME="AEN3264">24.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" @@ -400,9 +377,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3381" -></A ->22.4. Windows '95/'98</H1 +NAME="AEN3269">24.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 @@ -448,9 +423,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3397" -></A ->22.5. Windows 2000 Service Pack 2</H1 +NAME="AEN3285">24.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 a64de2a1b4..ba2bf6c922 100644 --- a/docs/htmldocs/pam.html +++ b/docs/htmldocs/pam.html @@ -6,7 +6,8 @@ managed authentication</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -73,18 +74,14 @@ WIDTH="100%"></DIV CLASS="CHAPTER" ><H1 ><A -NAME="PAM" -></A ->Chapter 11. Configuring PAM for distributed but centrally +NAME="PAM">Chapter 12. Configuring PAM for distributed but centrally managed authentication</H1 ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1922" -></A ->11.1. Samba and PAM</H1 +NAME="AEN1788">12.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 @@ -296,9 +293,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1966" -></A ->11.2. Distributed Authentication</H1 +NAME="AEN1832">12.2. Distributed Authentication</H1 ><P >The astute administrator will realize from this that the combination of <TT @@ -329,9 +324,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1973" -></A ->11.3. PAM Configuration in smb.conf</H1 +NAME="AEN1839">12.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 deleted file mode 100644 index f53641624a..0000000000 --- a/docs/htmldocs/passdb.html +++ /dev/null @@ -1,1646 +0,0 @@ -<!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 e98d0c30d0..abca946f6f 100644 --- a/docs/htmldocs/pdb-mysql.html +++ b/docs/htmldocs/pdb-mysql.html @@ -5,7 +5,8 @@ >Passdb MySQL plugin</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -72,17 +73,13 @@ WIDTH="100%"></DIV CLASS="CHAPTER" ><H1 ><A -NAME="PDB-MYSQL" -></A ->Chapter 16. Passdb MySQL plugin</H1 +NAME="PDB-MYSQL">Chapter 16. Passdb MySQL plugin</H1 ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2562" -></A ->16.1. Building</H1 +NAME="AEN2566">16.1. Building</H1 ><P >To build the plugin, run <B CLASS="COMMAND" @@ -101,53 +98,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -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 +NAME="AEN2572">16.2. Configuring</H1 ><P >This plugin lacks some good documentation, but here is some short info:</P ><P @@ -238,9 +189,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2595" -></A ->16.4. Using plaintext passwords or encrypted password</H1 +NAME="AEN2589">16.3. Using plaintext passwords or encrypted password</H1 ><P >I strongly discourage the use of plaintext passwords, however, you can use them:</P ><P @@ -253,9 +202,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2600" -></A ->16.5. Getting non-column data from the table</H1 +NAME="AEN2594">16.4. 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 1b419dcc74..4d300d7be0 100644 --- a/docs/htmldocs/pdb-xml.html +++ b/docs/htmldocs/pdb-xml.html @@ -5,7 +5,8 @@ >Passdb XML plugin</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -72,17 +73,13 @@ WIDTH="100%"></DIV CLASS="CHAPTER" ><H1 ><A -NAME="PDB-XML" -></A ->Chapter 17. Passdb XML plugin</H1 +NAME="PDB-XML">Chapter 17. Passdb XML plugin</H1 ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2619" -></A ->17.1. Building</H1 +NAME="AEN2613">17.1. Building</H1 ><P >This module requires libxml2 to be installed.</P ><P @@ -100,9 +97,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2625" -></A ->17.2. Usage</H1 +NAME="AEN2619">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 14497f522c..e3cf1e4fba 100644 --- a/docs/htmldocs/pdbedit.8.html +++ b/docs/htmldocs/pdbedit.8.html @@ -1,11 +1,12 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"> <HTML ><HEAD ><TITLE >pdbedit</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"></HEAD +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"></HEAD ><BODY CLASS="REFENTRY" BGCOLOR="#FFFFFF" @@ -15,9 +16,7 @@ VLINK="#840084" ALINK="#0000FF" ><H1 ><A -NAME="PDBEDIT.8" -></A ->pdbedit</H1 +NAME="PDBEDIT">pdbedit</H1 ><DIV CLASS="REFNAMEDIV" ><A @@ -29,15 +28,13 @@ NAME="AEN5" ><DIV CLASS="REFSYNOPSISDIV" ><A -NAME="AEN8" -></A -><H2 +NAME="AEN8"><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" @@ -47,12 +44,10 @@ NAME="AEN30" ><H2 >DESCRIPTION</H2 ><P ->This tool is part of the <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->Samba</SPAN ->(7)</SPAN +>This tool is part of the <A +HREF="samba.7.html" +TARGET="_top" +> Samba</A > suite.</P ><P >The pdbedit program is used to manage the users accounts @@ -70,7 +65,7 @@ CLASS="REFENTRYTITLE" ><DIV CLASS="REFSECT1" ><A -NAME="AEN39" +NAME="AEN37" ></A ><H2 >OPTIONS</H2 @@ -93,10 +88,20 @@ CLASS="COMMAND" >pdbedit -l</B ></P ><P +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="90%" +><TR +><TD ><PRE -CLASS="SCREEN" ->sorce:500:Simo Sorce -samba:45:Test User</PRE +CLASS="PROGRAMLISTING" +> sorce:500:Simo Sorce + samba:45:Test User + </PRE +></TD +></TR +></TABLE ></P ></DD ><DT @@ -112,26 +117,36 @@ CLASS="COMMAND" >pdbedit -l -v</B ></P ><P +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="90%" +><TR +><TD ><PRE -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 +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 ></P ></DD ><DT @@ -144,23 +159,35 @@ Profile Path: \\BERSERKER\profile</PRE <TT CLASS="FILENAME" >smbpasswd</TT -> file format. (see the - <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbpasswd</SPAN ->(5)</SPAN +> file format. (see the <A +HREF="smbpasswd.5.html" +TARGET="_top" +><TT +CLASS="FILENAME" +>smbpasswd(5)</TT +></A > 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="SCREEN" ->sorce:500:508818B733CE64BEAAD3B435B51404EE:D2A2418EFC466A8A0F6B1DBB5C3DB80C:[UX ]:LCT-00000000: -samba:45:0F2B255F7B67A7A9AAD3B435B51404EE:BC281CE3F53B6A5146629CD4751D3490:[UX ]:LCT-3BFA1E8D:</PRE +CLASS="PROGRAMLISTING" +> sorce:500:508818B733CE64BEAAD3B435B51404EE:D2A2418EFC466A8A0F6B1DBB5C3DB80C:[UX ]:LCT-00000000: + samba:45:0F2B255F7B67A7A9AAD3B435B51404EE:BC281CE3F53B6A5146629CD4751D3490:[UX ]:LCT-3BFA1E8D: + </PRE +></TD +></TR +></TABLE +></P ></DD ><DT >-u username</DT @@ -168,19 +195,13 @@ samba:45:0F2B255F7B67A7A9AAD3B435B51404EE:BC281CE3F53B6A5146629CD4751D3490:[UX ><P >This option specifies the username to be used for the operation requested (listing, adding, removing). - It is <SPAN -CLASS="emphasis" -><I + It is <I CLASS="EMPHASIS" >required</I -></SPAN > in add, remove and modify - operations and <SPAN -CLASS="emphasis" -><I + operations and <I CLASS="EMPHASIS" >optional</I -></SPAN > in list operations.</P ></DD @@ -266,11 +287,21 @@ CLASS="COMMAND" CLASS="COMMAND" >pdbedit -a -u sorce</B > -<PRE + <TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="90%" +><TR +><TD +><PRE CLASS="PROGRAMLISTING" >new password: -retype new password</PRE -></P + retype new password</PRE +></TD +></TR +></TABLE +> + </P ></DD ><DT >-m</DT @@ -363,9 +394,19 @@ 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 +> account policy value for bad lockout attempt is 0 + </PRE +></TD +></TR +></TABLE ></P ></DD ><DT @@ -387,10 +428,20 @@ 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 +> account policy value for bad lockout attempt was 0 + account policy value for bad lockout attempt is now 3 + </PRE +></TD +></TR +></TABLE ></P ></DD ><DT @@ -441,7 +492,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 @@ -466,7 +517,7 @@ compile time.</P ><DIV CLASS="REFSECT1" ><A -NAME="AEN184" +NAME="AEN182" ></A ><H2 >NOTES</H2 @@ -476,7 +527,7 @@ NAME="AEN184" ><DIV CLASS="REFSECT1" ><A -NAME="AEN187" +NAME="AEN185" ></A ><H2 >VERSION</H2 @@ -487,29 +538,27 @@ NAME="AEN187" ><DIV CLASS="REFSECT1" ><A -NAME="AEN190" +NAME="AEN188" ></A ><H2 >SEE ALSO</H2 ><P -><SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbpasswd</SPAN ->(5)</SPAN ->, <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->samba</SPAN ->(7)</SPAN -></P +><A +HREF="smbpasswd.8.html" +TARGET="_top" +>smbpasswd(8)</A +>, + <A +HREF="samba.7.html" +TARGET="_top" +>samba(7)</A +> + </P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN199" +NAME="AEN193" ></A ><H2 >AUTHOR</H2 @@ -521,14 +570,14 @@ NAME="AEN199" ><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. The conversion to DocBook - XML 4.2 for Samba 3.0 was done by Alexander Bokovoy.</P + Samba 2.2 was done by Gerald Carter</P ></DIV ></BODY ></HTML diff --git a/docs/htmldocs/portability.html b/docs/htmldocs/portability.html index 4942cdb1bb..424fbe5c6c 100644 --- a/docs/htmldocs/portability.html +++ b/docs/htmldocs/portability.html @@ -5,7 +5,8 @@ >Portability</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -72,9 +73,7 @@ WIDTH="100%"></DIV CLASS="CHAPTER" ><H1 ><A -NAME="PORTABILITY" -></A ->Chapter 21. Portability</H1 +NAME="PORTABILITY">Chapter 23. 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 @@ -84,9 +83,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3251" -></A ->21.1. HPUX</H1 +NAME="AEN3139">23.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 @@ -114,9 +111,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3257" -></A ->21.2. SCO Unix</H1 +NAME="AEN3145">23.2. SCO Unix</H1 ><P > If you run an old version of SCO Unix then you may need to get important @@ -131,9 +126,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3261" -></A ->21.3. DNIX</H1 +NAME="AEN3149">23.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 @@ -238,9 +231,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3290" -></A ->21.4. RedHat Linux Rembrandt-II</H1 +NAME="AEN3178">23.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 92eb52c7cc..46ebbcdf84 100644 --- a/docs/htmldocs/printing.html +++ b/docs/htmldocs/printing.html @@ -5,7 +5,8 @@ >Printing Support</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -72,17 +73,13 @@ WIDTH="100%"></DIV CLASS="CHAPTER" ><H1 ><A -NAME="PRINTING" -></A ->Chapter 13. Printing Support</H1 +NAME="PRINTING">Chapter 14. Printing Support</H1 ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2054" -></A ->13.1. Introduction</H1 +NAME="AEN1920">14.1. Introduction</H1 ><P >Beginning with the 2.2.0 release, Samba supports the native Windows NT printing mechanisms implemented via @@ -163,9 +160,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2076" -></A ->13.2. Configuration</H1 +NAME="AEN1942">14.2. Configuration</H1 ><DIV CLASS="WARNING" ><P @@ -180,7 +175,7 @@ WIDTH="25" ALIGN="CENTER" VALIGN="TOP" ><IMG -SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/warning.gif" +SRC="../images/warning.gif" HSPACE="5" ALT="Warning"></TD ><TH @@ -229,9 +224,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2084" -></A ->13.2.1. Creating [print$]</H2 +NAME="AEN1950">14.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$]. @@ -310,7 +303,7 @@ WIDTH="25" ALIGN="CENTER" VALIGN="TOP" ><IMG -SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif" +SRC="../images/note.gif" HSPACE="5" ALT="Note"></TD ><TH @@ -381,7 +374,7 @@ WIDTH="25" ALIGN="CENTER" VALIGN="TOP" ><IMG -SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/warning.gif" +SRC="../images/warning.gif" HSPACE="5" ALT="Warning"></TD ><TH @@ -452,9 +445,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2119" -></A ->13.2.2. Setting Drivers for Existing Printers</H2 +NAME="AEN1985">14.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 @@ -524,9 +515,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2135" -></A ->13.2.3. Support a large number of printers</H2 +NAME="AEN2001">14.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 @@ -590,9 +579,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2146" -></A ->13.2.4. Adding New Printers via the Windows NT APW</H2 +NAME="AEN2012">14.2.4. Adding New Printers via the Windows NT APW</H2 ><P >By default, Samba offers all printer shares defined in <TT CLASS="FILENAME" @@ -733,8 +720,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 @@ -759,9 +746,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2176" -></A ->13.2.5. Samba and Printer Ports</H2 +NAME="AEN2042">14.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 @@ -796,9 +781,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2184" -></A ->13.3. The Imprints Toolset</H1 +NAME="AEN2050">14.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 @@ -814,9 +797,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2188" -></A ->13.3.1. What is Imprints?</H2 +NAME="AEN2054">14.3.1. What is Imprints?</H2 ><P >Imprints is a collection of tools for supporting the goals of</P @@ -846,9 +827,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2198" -></A ->13.3.2. Creating Printer Driver Packages</H2 +NAME="AEN2064">14.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 @@ -862,9 +841,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2201" -></A ->13.3.3. The Imprints server</H2 +NAME="AEN2067">14.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 @@ -886,9 +863,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2205" -></A ->13.3.4. The Installation Client</H2 +NAME="AEN2071">14.3.4. The Installation Client</H2 ><P >More information regarding the Imprints installation client is available in the <TT @@ -980,17 +955,13 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2227" -></A ->13.4. Diagnosis</H1 +NAME="AEN2093">14.4. Diagnosis</H1 ><DIV CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2229" -></A ->13.4.1. Introduction</H2 +NAME="AEN2095">14.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 @@ -1063,9 +1034,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2245" -></A ->13.4.2. Debugging printer problems</H2 +NAME="AEN2111">14.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 @@ -1081,7 +1050,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 @@ -1120,9 +1089,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2254" -></A ->13.4.3. What printers do I have?</H2 +NAME="AEN2120">14.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 @@ -1149,9 +1116,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2262" -></A ->13.4.4. Setting up printcap and print servers</H2 +NAME="AEN2128">14.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 @@ -1233,9 +1198,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2290" -></A ->13.4.5. Job sent, no output</H2 +NAME="AEN2156">14.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 @@ -1278,9 +1241,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2301" -></A ->13.4.6. Job sent, strange output</H2 +NAME="AEN2167">14.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 @@ -1324,9 +1285,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2313" -></A ->13.4.7. Raw PostScript printed</H2 +NAME="AEN2179">14.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 @@ -1339,9 +1298,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2316" -></A ->13.4.8. Advanced Printing</H2 +NAME="AEN2182">14.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. @@ -1355,9 +1312,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2319" -></A ->13.4.9. Real debugging</H2 +NAME="AEN2185">14.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 b15d74c5d0..9414399bf4 100644 --- a/docs/htmldocs/pwencrypt.html +++ b/docs/htmldocs/pwencrypt.html @@ -5,7 +5,8 @@ >LanMan and NT Password Encryption in Samba</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -16,8 +17,8 @@ REL="PREVIOUS" TITLE="Quick Cross Subnet Browsing / Cross Workgroup Browsing guide" HREF="browsing-quick.html"><LINK REL="NEXT" -TITLE="User information database" -HREF="passdb.html"></HEAD +TITLE="Type of installation" +HREF="type.html"></HEAD ><BODY CLASS="CHAPTER" BGCOLOR="#FFFFFF" @@ -59,7 +60,7 @@ WIDTH="10%" ALIGN="right" VALIGN="bottom" ><A -HREF="passdb.html" +HREF="type.html" ACCESSKEY="N" >Next</A ></TD @@ -72,17 +73,13 @@ WIDTH="100%"></DIV CLASS="CHAPTER" ><H1 ><A -NAME="PWENCRYPT" -></A ->Chapter 4. LanMan and NT Password Encryption in Samba</H1 +NAME="PWENCRYPT">Chapter 4. LanMan and NT Password Encryption in Samba</H1 ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN457" -></A ->4.1. Introduction</H1 +NAME="AEN457">4.1. Introduction</H1 ><P >Newer windows clients send encrypted passwords over the wire, instead of plain text passwords. The newest clients @@ -104,9 +101,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN462" -></A ->4.2. Important Notes About Security</H1 +NAME="AEN462">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 @@ -140,7 +135,7 @@ WIDTH="25" ALIGN="CENTER" VALIGN="TOP" ><IMG -SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/warning.gif" +SRC="../images/warning.gif" HSPACE="5" ALT="Warning"></TD ><TD @@ -206,9 +201,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN481" -></A ->4.2.1. Advantages of SMB Encryption</H2 +NAME="AEN481">4.2.1. Advantages of SMB Encryption</H2 ><P ></P ><UL @@ -235,9 +228,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN488" -></A ->4.2.2. Advantages of non-encrypted passwords</H2 +NAME="AEN488">4.2.2. Advantages of non-encrypted passwords</H2 ><P ></P ><UL @@ -266,9 +257,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN497" -></A ->4.3. The smbpasswd Command</H1 +NAME="AEN497">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 @@ -412,7 +401,7 @@ WIDTH="33%" ALIGN="right" VALIGN="top" ><A -HREF="passdb.html" +HREF="type.html" ACCESSKEY="N" >Next</A ></TD @@ -436,7 +425,7 @@ ACCESSKEY="U" WIDTH="33%" ALIGN="right" VALIGN="top" ->User information database</TD +>Type of installation</TD ></TR ></TABLE ></DIV diff --git a/docs/htmldocs/rpcclient.1.html b/docs/htmldocs/rpcclient.1.html index 611512a53b..e695663c8a 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.1" +NAME="RPCCLIENT" ></A >rpcclient</H1 ><DIV @@ -48,12 +48,10 @@ NAME="AEN23" ><H2 >DESCRIPTION</H2 ><P ->This tool is part of the <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->Samba</SPAN ->(7)</SPAN +>This tool is part of the <A +HREF="samba.7.html" +TARGET="_top" +> Samba</A > suite.</P ><P ><B @@ -68,7 +66,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN31" +NAME="AEN29" ></A ><H2 >OPTIONS</H2 @@ -92,12 +90,10 @@ CLASS="PARAMETER" >name resolve order</I ></TT ></A -> line from <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smb.conf</SPAN ->(5)</SPAN +> line from + <TT +CLASS="FILENAME" +>smb.conf(5)</TT >.</P ></DD ><DT @@ -111,9 +107,10 @@ CLASS="REFENTRYTITLE" ><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 @@ -127,12 +124,6 @@ domain = <value></PRE 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 @@ -174,6 +165,12 @@ 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 @@ -306,7 +303,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN111" +NAME="AEN107" ></A ><H2 >COMMANDS</H2 @@ -470,14 +467,15 @@ 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 @@ -707,7 +705,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN231" +NAME="AEN227" ></A ><H2 >BUGS</H2 @@ -726,7 +724,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 @@ -736,28 +734,23 @@ 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 <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, + 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, 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="AEN245" +NAME="AEN237" ></A ><H2 >VERSION</H2 @@ -768,7 +761,7 @@ NAME="AEN245" ><DIV CLASS="REFSECT1" ><A -NAME="AEN248" +NAME="AEN240" ></A ><H2 >AUTHOR</H2 @@ -781,8 +774,7 @@ NAME="AEN248" >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. The conversion to DocBook XML 4.2 for Samba 3.0 was - done by Alexander Bokovoy.</P + Carter.</P ></DIV ></BODY ></HTML diff --git a/docs/htmldocs/samba-bdc.html b/docs/htmldocs/samba-bdc.html index 42f653fb7d..ef06a89416 100644 --- a/docs/htmldocs/samba-bdc.html +++ b/docs/htmldocs/samba-bdc.html @@ -5,7 +5,8 @@ >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.77+"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -13,7 +14,7 @@ REL="UP" TITLE="Type of installation" HREF="type.html"><LINK REL="PREVIOUS" -TITLE="Samba as a NT4 or Win2k Primary Domain Controller" +TITLE="How to Configure Samba as a NT4 Primary Domain Controller" HREF="samba-pdc.html"><LINK REL="NEXT" TITLE="Samba as a ADS domain member" @@ -72,17 +73,13 @@ WIDTH="100%"></DIV CLASS="CHAPTER" ><H1 ><A -NAME="SAMBA-BDC" -></A ->Chapter 6. How to Act as a Backup Domain Controller in a Purely Samba Controlled Domain</H1 +NAME="SAMBA-BDC">Chapter 7. How to Act as a Backup Domain Controller in a Purely Samba Controlled Domain</H1 ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1274" -></A ->6.1. Prerequisite Reading</H1 +NAME="AEN1127">7.1. Prerequisite Reading</H1 ><P >Before you continue reading in this chapter, please make sure that you are comfortable with configuring a Samba PDC @@ -97,9 +94,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1278" -></A ->6.2. Background</H1 +NAME="AEN1131">7.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 @@ -142,9 +137,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1286" -></A ->6.3. What qualifies a Domain Controller on the network?</H1 +NAME="AEN1139">7.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 @@ -159,9 +152,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1289" -></A ->6.3.1. How does a Workstation find its domain controller?</H2 +NAME="AEN1142">7.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 @@ -178,9 +169,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1292" -></A ->6.3.2. When is the PDC needed?</H2 +NAME="AEN1145">7.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 @@ -194,19 +183,13 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1295" -></A ->6.4. Can Samba be a Backup Domain Controller to an NT PDC?</H1 +NAME="AEN1148">7.4. Can Samba be a Backup Domain Controller?</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 @@ -217,9 +200,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1300" -></A ->6.5. How do I set up a Samba BDC?</H1 +NAME="AEN1152">7.5. How do I set up a Samba BDC?</H1 ><P >Several things have to be done:</P ><P @@ -284,9 +265,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1317" -></A ->6.5.1. How do I replicate the smbpasswd file?</H2 +NAME="AEN1169">7.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 @@ -300,21 +279,6 @@ 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 @@ -361,7 +325,7 @@ ACCESSKEY="N" WIDTH="33%" ALIGN="left" VALIGN="top" ->Samba as a NT4 or Win2k Primary Domain Controller</TD +>How to Configure Samba as a NT4 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 82e29206ac..0062e257dc 100644 --- a/docs/htmldocs/samba-howto-collection.html +++ b/docs/htmldocs/samba-howto-collection.html @@ -5,7 +5,8 @@ >SAMBA Project Documentation</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="NEXT" TITLE="General installation" HREF="introduction.html"></HEAD @@ -19,28 +20,20 @@ ALINK="#0000FF" ><DIV CLASS="BOOK" ><A -NAME="SAMBA-HOWTO-COLLECTION" -></A -><DIV +NAME="SAMBA-HOWTO-COLLECTION"><DIV CLASS="TITLEPAGE" ><H1 CLASS="TITLE" ><A -NAME="SAMBA-HOWTO-COLLECTION" -></A ->SAMBA Project Documentation</H1 +NAME="SAMBA-HOWTO-COLLECTION">SAMBA Project Documentation</H1 ><H3 CLASS="AUTHOR" ><A -NAME="AEN4" -></A ->SAMBA Team</H3 +NAME="AEN4">SAMBA Team</H3 ><HR></DIV ><H1 ><A -NAME="AEN8" -></A ->Abstract</H1 +NAME="AEN8">Abstract</H1 ><P ><SPAN CLASS="emphasis" @@ -159,89 +152,128 @@ HREF="install.html#AEN184" ></DD ><DT >2. <A -HREF="browsing-quick.html" ->Quick Cross Subnet Browsing / Cross Workgroup Browsing guide</A +HREF="improved-browsing.html" +>Improved browsing in samba</A ></DT ><DD ><DL ><DT >2.1. <A -HREF="browsing-quick.html#AEN230" ->Discussion</A +HREF="improved-browsing.html#AEN229" +>Overview of browsing</A ></DT ><DT >2.2. <A -HREF="browsing-quick.html#AEN238" ->Use of the "Remote Announce" parameter</A +HREF="improved-browsing.html#AEN233" +>Browsing support in samba</A ></DT ><DT >2.3. <A -HREF="browsing-quick.html#AEN252" ->Use of the "Remote Browse Sync" parameter</A +HREF="improved-browsing.html#AEN242" +>Problem resolution</A ></DT ><DT >2.4. <A -HREF="browsing-quick.html#AEN257" ->Use of WINS</A +HREF="improved-browsing.html#AEN249" +>Browsing across subnets</A ></DT ><DT >2.5. <A -HREF="browsing-quick.html#AEN268" ->Do NOT use more than one (1) protocol on MS Windows machines</A +HREF="improved-browsing.html#AEN289" +>Setting up a WINS server</A ></DT ><DT >2.6. <A -HREF="browsing-quick.html#AEN274" ->Name Resolution Order</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 ></DT ></DL ></DD ><DT >3. <A -HREF="passdb.html" ->User information database</A +HREF="browsing-quick.html" +>Quick Cross Subnet Browsing / Cross Workgroup Browsing guide</A ></DT ><DD ><DL ><DT >3.1. <A -HREF="passdb.html#AEN324" ->Introduction</A +HREF="browsing-quick.html#AEN377" +>Discussion</A ></DT ><DT >3.2. <A -HREF="passdb.html#AEN331" ->Important Notes About Security</A +HREF="browsing-quick.html#AEN385" +>Use of the "Remote Announce" parameter</A ></DT ><DT >3.3. <A -HREF="passdb.html#AEN357" ->The smbpasswd Command</A +HREF="browsing-quick.html#AEN399" +>Use of the "Remote Browse Sync" parameter</A ></DT ><DT >3.4. <A -HREF="passdb.html#AEN388" ->Plain text</A +HREF="browsing-quick.html#AEN404" +>Use of WINS</A ></DT ><DT >3.5. <A -HREF="passdb.html#AEN393" ->TDB</A +HREF="browsing-quick.html#AEN415" +>Do NOT use more than one (1) protocol on MS Windows machines</A ></DT ><DT >3.6. <A -HREF="passdb.html#AEN396" ->LDAP</A +HREF="browsing-quick.html#AEN421" +>Name Resolution Order</A ></DT +></DL +></DD ><DT ->3.7. <A -HREF="passdb.html#AEN614" ->MySQL</A +>4. <A +HREF="pwencrypt.html" +>LanMan and NT Password Encryption in Samba</A ></DT +><DD +><DL ><DT ->3.8. <A -HREF="passdb.html#AEN662" ->Passdb XML plugin</A +>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 ></DT ></DL ></DD @@ -255,168 +287,168 @@ HREF="type.html" ><DD ><DL ><DT ->4. <A +>5. <A HREF="securitylevels.html" >User and Share security level (for servers not in a domain)</A ></DT ><DT ->5. <A +>6. <A HREF="samba-pdc.html" ->Samba as a NT4 or Win2k Primary Domain Controller</A +>How to Configure Samba as a NT4 Primary Domain Controller</A ></DT ><DD ><DL ><DT ->5.1. <A -HREF="samba-pdc.html#AEN722" +>6.1. <A +HREF="samba-pdc.html#AEN575" >Prerequisite Reading</A ></DT ><DT ->5.2. <A -HREF="samba-pdc.html#AEN728" +>6.2. <A +HREF="samba-pdc.html#AEN581" >Background</A ></DT ><DT ->5.3. <A -HREF="samba-pdc.html#AEN767" +>6.3. <A +HREF="samba-pdc.html#AEN620" >Configuring the Samba Domain Controller</A ></DT ><DT ->5.4. <A -HREF="samba-pdc.html#AEN810" +>6.4. <A +HREF="samba-pdc.html#AEN663" >Creating Machine Trust Accounts and Joining Clients to the Domain</A ></DT ><DT ->5.5. <A -HREF="samba-pdc.html#AEN894" +>6.5. <A +HREF="samba-pdc.html#AEN747" >Common Problems and Errors</A ></DT ><DT ->5.6. <A -HREF="samba-pdc.html#AEN942" +>6.6. <A +HREF="samba-pdc.html#AEN795" >System Policies and Profiles</A ></DT ><DT ->5.7. <A -HREF="samba-pdc.html#AEN986" +>6.7. <A +HREF="samba-pdc.html#AEN839" >What other help can I get?</A ></DT ><DT ->5.8. <A -HREF="samba-pdc.html#AEN1100" +>6.8. <A +HREF="samba-pdc.html#AEN953" >Domain Control for Windows 9x/ME</A ></DT ><DT ->5.9. <A -HREF="samba-pdc.html#AEN1238" ->DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba</A +>6.9. <A +HREF="samba-pdc.html#AEN1091" +>DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba</A ></DT ></DL ></DD ><DT ->6. <A +>7. <A HREF="samba-bdc.html" >How to Act as a Backup Domain Controller in a Purely Samba Controlled Domain</A ></DT ><DD ><DL ><DT ->6.1. <A -HREF="samba-bdc.html#AEN1274" +>7.1. <A +HREF="samba-bdc.html#AEN1127" >Prerequisite Reading</A ></DT ><DT ->6.2. <A -HREF="samba-bdc.html#AEN1278" +>7.2. <A +HREF="samba-bdc.html#AEN1131" >Background</A ></DT ><DT ->6.3. <A -HREF="samba-bdc.html#AEN1286" +>7.3. <A +HREF="samba-bdc.html#AEN1139" >What qualifies a Domain Controller on the network?</A ></DT ><DT ->6.4. <A -HREF="samba-bdc.html#AEN1295" ->Can Samba be a Backup Domain Controller to an NT PDC?</A +>7.4. <A +HREF="samba-bdc.html#AEN1148" +>Can Samba be a Backup Domain Controller?</A ></DT ><DT ->6.5. <A -HREF="samba-bdc.html#AEN1300" +>7.5. <A +HREF="samba-bdc.html#AEN1152" >How do I set up a Samba BDC?</A ></DT ></DL ></DD ><DT ->7. <A +>8. <A HREF="ads.html" >Samba as a ADS domain member</A ></DT ><DD ><DL ><DT ->7.1. <A -HREF="ads.html#AEN1339" +>8.1. <A +HREF="ads.html#AEN1187" >Installing the required packages for Debian</A ></DT ><DT ->7.2. <A -HREF="ads.html#AEN1346" +>8.2. <A +HREF="ads.html#AEN1193" >Installing the required packages for RedHat</A ></DT ><DT ->7.3. <A -HREF="ads.html#AEN1356" +>8.3. <A +HREF="ads.html#AEN1202" >Compile Samba</A ></DT ><DT ->7.4. <A -HREF="ads.html#AEN1371" +>8.4. <A +HREF="ads.html#AEN1217" >Setup your /etc/krb5.conf</A ></DT ><DT ->7.5. <A -HREF="ads.html#AEN1381" +>8.5. <A +HREF="ads.html#AEN1227" >Create the computer account</A ></DT ><DT ->7.6. <A -HREF="ads.html#AEN1393" +>8.6. <A +HREF="ads.html#AEN1243" >Test your server setup</A ></DT ><DT ->7.7. <A -HREF="ads.html#AEN1398" +>8.7. <A +HREF="ads.html#AEN1248" >Testing with smbclient</A ></DT ><DT ->7.8. <A -HREF="ads.html#AEN1401" +>8.8. <A +HREF="ads.html#AEN1251" >Notes</A ></DT ></DL ></DD ><DT ->8. <A +>9. <A HREF="domain-security.html" ->Samba as a NT4 or Win2k domain member</A +>Samba as a NT4 domain member</A ></DT ><DD ><DL ><DT ->8.1. <A -HREF="domain-security.html#AEN1423" ->Joining an NT Domain with Samba 3.0</A +>9.1. <A +HREF="domain-security.html#AEN1273" +>Joining an NT Domain with Samba 2.2</A ></DT ><DT ->8.2. <A -HREF="domain-security.html#AEN1478" +>9.2. <A +HREF="domain-security.html#AEN1337" >Samba and Windows 2000 Domains</A ></DT ><DT ->8.3. <A -HREF="domain-security.html#AEN1481" +>9.3. <A +HREF="domain-security.html#AEN1342" >Why is this better than security = server?</A ></DT ></DL @@ -431,95 +463,95 @@ HREF="optional.html" ><DD ><DL ><DT ->9. <A +>10. <A HREF="integrate-ms-networks.html" >Integrating MS Windows networks with Samba</A ></DT ><DD ><DL ><DT ->9.1. <A -HREF="integrate-ms-networks.html#AEN1513" +>10.1. <A +HREF="integrate-ms-networks.html#AEN1374" >Agenda</A ></DT ><DT ->9.2. <A -HREF="integrate-ms-networks.html#AEN1535" +>10.2. <A +HREF="integrate-ms-networks.html#AEN1396" >Name Resolution in a pure Unix/Linux world</A ></DT ><DT ->9.3. <A -HREF="integrate-ms-networks.html#AEN1598" +>10.3. <A +HREF="integrate-ms-networks.html#AEN1459" >Name resolution as used within MS Windows networking</A ></DT ><DT ->9.4. <A -HREF="integrate-ms-networks.html#AEN1643" +>10.4. <A +HREF="integrate-ms-networks.html#AEN1504" >How browsing functions and how to deploy stable and dependable browsing using Samba</A ></DT ><DT ->9.5. <A -HREF="integrate-ms-networks.html#AEN1653" +>10.5. <A +HREF="integrate-ms-networks.html#AEN1514" >MS Windows security options and how to configure Samba for seemless integration</A ></DT ><DT ->9.6. <A -HREF="integrate-ms-networks.html#AEN1723" +>10.6. <A +HREF="integrate-ms-networks.html#AEN1584" >Conclusions</A ></DT ></DL ></DD ><DT ->10. <A +>11. <A HREF="unix-permissions.html" >UNIX Permission Bits and Windows NT Access Control Lists</A ></DT ><DD ><DL ><DT ->10.1. <A -HREF="unix-permissions.html#AEN1744" +>11.1. <A +HREF="unix-permissions.html#AEN1605" >Viewing and changing UNIX permissions using the NT security dialogs</A ></DT ><DT ->10.2. <A -HREF="unix-permissions.html#AEN1748" +>11.2. <A +HREF="unix-permissions.html#AEN1614" >How to view file security on a Samba share</A ></DT ><DT ->10.3. <A -HREF="unix-permissions.html#AEN1759" +>11.3. <A +HREF="unix-permissions.html#AEN1625" >Viewing file ownership</A ></DT ><DT ->10.4. <A -HREF="unix-permissions.html#AEN1779" +>11.4. <A +HREF="unix-permissions.html#AEN1645" >Viewing file or directory permissions</A ></DT ><DT ->10.5. <A -HREF="unix-permissions.html#AEN1815" +>11.5. <A +HREF="unix-permissions.html#AEN1681" >Modifying file or directory permissions</A ></DT ><DT ->10.6. <A -HREF="unix-permissions.html#AEN1837" +>11.6. <A +HREF="unix-permissions.html#AEN1703" >Interaction with the standard Samba create mask parameters</A ></DT ><DT ->10.7. <A -HREF="unix-permissions.html#AEN1901" +>11.7. <A +HREF="unix-permissions.html#AEN1767" >Interaction with the standard Samba file attribute mapping</A ></DT ></DL ></DD ><DT ->11. <A +>12. <A HREF="pam.html" >Configuring PAM for distributed but centrally managed authentication</A @@ -527,304 +559,323 @@ managed authentication</A ><DD ><DL ><DT ->11.1. <A -HREF="pam.html#AEN1922" +>12.1. <A +HREF="pam.html#AEN1788" >Samba and PAM</A ></DT ><DT ->11.2. <A -HREF="pam.html#AEN1966" +>12.2. <A +HREF="pam.html#AEN1832" >Distributed Authentication</A ></DT ><DT ->11.3. <A -HREF="pam.html#AEN1973" +>12.3. <A +HREF="pam.html#AEN1839" >PAM Configuration in smb.conf</A ></DT ></DL ></DD ><DT ->12. <A +>13. <A HREF="msdfs.html" >Hosting a Microsoft Distributed File System tree on Samba</A ></DT ><DD ><DL ><DT ->12.1. <A -HREF="msdfs.html#AEN1993" +>13.1. <A +HREF="msdfs.html#AEN1859" >Instructions</A ></DT ></DL ></DD ><DT ->13. <A +>14. <A HREF="printing.html" >Printing Support</A ></DT ><DD ><DL ><DT ->13.1. <A -HREF="printing.html#AEN2054" +>14.1. <A +HREF="printing.html#AEN1920" >Introduction</A ></DT ><DT ->13.2. <A -HREF="printing.html#AEN2076" +>14.2. <A +HREF="printing.html#AEN1942" >Configuration</A ></DT ><DT ->13.3. <A -HREF="printing.html#AEN2184" +>14.3. <A +HREF="printing.html#AEN2050" >The Imprints Toolset</A ></DT ><DT ->13.4. <A -HREF="printing.html#AEN2227" +>14.4. <A +HREF="printing.html#AEN2093" >Diagnosis</A ></DT ></DL ></DD ><DT ->14. <A +>15. <A HREF="winbind.html" >Unified Logons between Windows NT and UNIX using Winbind</A ></DT ><DD ><DL ><DT ->14.1. <A -HREF="winbind.html#AEN2360" +>15.1. <A +HREF="winbind.html#AEN2225" >Abstract</A ></DT ><DT ->14.2. <A -HREF="winbind.html#AEN2364" +>15.2. <A +HREF="winbind.html#AEN2229" >Introduction</A ></DT ><DT ->14.3. <A -HREF="winbind.html#AEN2377" +>15.3. <A +HREF="winbind.html#AEN2242" >What Winbind Provides</A ></DT ><DT ->14.4. <A -HREF="winbind.html#AEN2388" +>15.4. <A +HREF="winbind.html#AEN2253" >How Winbind Works</A ></DT ><DT ->14.5. <A -HREF="winbind.html#AEN2431" +>15.5. <A +HREF="winbind.html#AEN2293" >Installation and Configuration</A ></DT ><DT ->14.6. <A -HREF="winbind.html#AEN2680" +>15.6. <A +HREF="winbind.html#AEN2542" >Limitations</A ></DT ><DT ->14.7. <A -HREF="winbind.html#AEN2690" +>15.7. <A +HREF="winbind.html#AEN2552" >Conclusion</A ></DT ></DL ></DD ><DT ->15. <A -HREF="improved-browsing.html" ->Improved browsing in samba</A +>16. <A +HREF="pdb-mysql.html" +>Passdb MySQL plugin</A ></DT ><DD ><DL ><DT ->15.1. <A -HREF="improved-browsing.html#AEN2700" ->Overview of browsing</A +>16.1. <A +HREF="pdb-mysql.html#AEN2566" +>Building</A ></DT ><DT ->15.2. <A -HREF="improved-browsing.html#AEN2704" ->Browsing support in samba</A +>16.2. <A +HREF="pdb-mysql.html#AEN2572" +>Configuring</A ></DT ><DT ->15.3. <A -HREF="improved-browsing.html#AEN2713" ->Problem resolution</A +>16.3. <A +HREF="pdb-mysql.html#AEN2589" +>Using plaintext passwords or encrypted password</A ></DT ><DT ->15.4. <A -HREF="improved-browsing.html#AEN2720" ->Browsing across subnets</A +>16.4. <A +HREF="pdb-mysql.html#AEN2594" +>Getting non-column data from the table</A ></DT +></DL +></DD ><DT ->15.5. <A -HREF="improved-browsing.html#AEN2760" ->Setting up a WINS server</A +>17. <A +HREF="pdb-xml.html" +>Passdb XML plugin</A ></DT +><DD +><DL ><DT ->15.6. <A -HREF="improved-browsing.html#AEN2779" ->Setting up Browsing in a WORKGROUP</A +>17.1. <A +HREF="pdb-xml.html#AEN2613" +>Building</A ></DT ><DT ->15.7. <A -HREF="improved-browsing.html#AEN2797" ->Setting up Browsing in a DOMAIN</A +>17.2. <A +HREF="pdb-xml.html#AEN2619" +>Usage</A ></DT +></DL +></DD ><DT ->15.8. <A -HREF="improved-browsing.html#AEN2807" ->Forcing samba to be the master</A +>18. <A +HREF="vfs.html" +>Stackable VFS modules</A ></DT +><DD +><DL ><DT ->15.9. <A -HREF="improved-browsing.html#AEN2816" ->Making samba the domain master</A +>18.1. <A +HREF="vfs.html#AEN2640" +>Introduction and configuration</A ></DT ><DT ->15.10. <A -HREF="improved-browsing.html#AEN2834" ->Note about broadcast addresses</A +>18.2. <A +HREF="vfs.html#AEN2649" +>Included modules</A ></DT ><DT ->15.11. <A -HREF="improved-browsing.html#AEN2837" ->Multiple interfaces</A +>18.3. <A +HREF="vfs.html#AEN2703" +>VFS modules available elsewhere</A ></DT ></DL ></DD ><DT ->16. <A -HREF="vfs.html" ->Stackable VFS modules</A +>19. <A +HREF="samba-ldap-howto.html" +>Storing Samba's User/Machine Account information in an LDAP Directory</A ></DT ><DD ><DL ><DT ->16.1. <A -HREF="vfs.html#AEN2855" ->Introduction and configuration</A +>19.1. <A +HREF="samba-ldap-howto.html#AEN2737" +>Purpose</A ></DT ><DT ->16.2. <A -HREF="vfs.html#AEN2864" ->Included modules</A +>19.2. <A +HREF="samba-ldap-howto.html#AEN2757" +>Introduction</A ></DT ><DT ->16.3. <A -HREF="vfs.html#AEN2918" ->VFS modules available elsewhere</A +>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 +></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 ->17. <A +>20. <A HREF="cvs-access.html" ->Access Samba source code via CVS</A +>HOWTO Access Samba source code via CVS</A ></DT ><DD ><DL ><DT ->17.1. <A -HREF="cvs-access.html#AEN2942" +>20.1. <A +HREF="cvs-access.html#AEN2964" >Introduction</A ></DT ><DT ->17.2. <A -HREF="cvs-access.html#AEN2947" +>20.2. <A +HREF="cvs-access.html#AEN2969" >CVS Access to samba.org</A ></DT ></DL ></DD ><DT ->18. <A +>21. <A HREF="groupmapping.html" >Group mapping HOWTO</A ></DT ><DT ->19. <A +>22. <A HREF="speed.html" >Samba performance issues</A ></DT ><DD ><DL ><DT ->19.1. <A -HREF="speed.html#AEN3033" +>22.1. <A +HREF="speed.html#AEN3055" >Comparisons</A ></DT ><DT ->19.2. <A -HREF="speed.html#AEN3039" +>22.2. <A +HREF="speed.html#AEN3061" >Socket options</A ></DT ><DT ->19.3. <A -HREF="speed.html#AEN3046" +>22.3. <A +HREF="speed.html#AEN3068" >Read size</A ></DT ><DT ->19.4. <A -HREF="speed.html#AEN3051" +>22.4. <A +HREF="speed.html#AEN3073" >Max xmit</A ></DT ><DT ->19.5. <A -HREF="speed.html#AEN3056" +>22.5. <A +HREF="speed.html#AEN3078" >Log level</A ></DT ><DT ->19.6. <A -HREF="speed.html#AEN3059" +>22.6. <A +HREF="speed.html#AEN3081" >Read raw</A ></DT ><DT ->19.7. <A -HREF="speed.html#AEN3064" +>22.7. <A +HREF="speed.html#AEN3086" >Write raw</A ></DT ><DT ->19.8. <A -HREF="speed.html#AEN3068" +>22.8. <A +HREF="speed.html#AEN3090" >Slow Clients</A ></DT ><DT ->19.9. <A -HREF="speed.html#AEN3072" +>22.9. <A +HREF="speed.html#AEN3094" >Slow Logins</A ></DT ><DT ->19.10. <A -HREF="speed.html#AEN3075" +>22.10. <A +HREF="speed.html#AEN3097" >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 @@ -835,132 +886,132 @@ HREF="appendixes.html" ><DD ><DL ><DT ->21. <A +>23. <A HREF="portability.html" >Portability</A ></DT ><DD ><DL ><DT ->21.1. <A -HREF="portability.html#AEN3251" +>23.1. <A +HREF="portability.html#AEN3139" >HPUX</A ></DT ><DT ->21.2. <A -HREF="portability.html#AEN3257" +>23.2. <A +HREF="portability.html#AEN3145" >SCO Unix</A ></DT ><DT ->21.3. <A -HREF="portability.html#AEN3261" +>23.3. <A +HREF="portability.html#AEN3149" >DNIX</A ></DT ><DT ->21.4. <A -HREF="portability.html#AEN3290" +>23.4. <A +HREF="portability.html#AEN3178" >RedHat Linux Rembrandt-II</A ></DT ></DL ></DD ><DT ->22. <A +>24. <A HREF="other-clients.html" >Samba and other CIFS clients</A ></DT ><DD ><DL ><DT ->22.1. <A -HREF="other-clients.html#AEN3311" +>24.1. <A +HREF="other-clients.html#AEN3199" >Macintosh clients?</A ></DT ><DT ->22.2. <A -HREF="other-clients.html#AEN3320" +>24.2. <A +HREF="other-clients.html#AEN3208" >OS2 Client</A ></DT ><DT ->22.3. <A -HREF="other-clients.html#AEN3360" +>24.3. <A +HREF="other-clients.html#AEN3248" >Windows for Workgroups</A ></DT ><DT ->22.4. <A -HREF="other-clients.html#AEN3381" +>24.4. <A +HREF="other-clients.html#AEN3269" >Windows '95/'98</A ></DT ><DT ->22.5. <A -HREF="other-clients.html#AEN3397" +>24.5. <A +HREF="other-clients.html#AEN3285" >Windows 2000 Service Pack 2</A ></DT ></DL ></DD ><DT ->23. <A +>25. <A HREF="bugreport.html" >Reporting Bugs</A ></DT ><DD ><DL ><DT ->23.1. <A -HREF="bugreport.html#AEN3421" +>25.1. <A +HREF="bugreport.html#AEN3309" >Introduction</A ></DT ><DT ->23.2. <A -HREF="bugreport.html#AEN3431" +>25.2. <A +HREF="bugreport.html#AEN3319" >General info</A ></DT ><DT ->23.3. <A -HREF="bugreport.html#AEN3437" +>25.3. <A +HREF="bugreport.html#AEN3325" >Debug levels</A ></DT ><DT ->23.4. <A -HREF="bugreport.html#AEN3454" +>25.4. <A +HREF="bugreport.html#AEN3342" >Internal errors</A ></DT ><DT ->23.5. <A -HREF="bugreport.html#AEN3464" +>25.5. <A +HREF="bugreport.html#AEN3352" >Attaching to a running process</A ></DT ><DT ->23.6. <A -HREF="bugreport.html#AEN3467" +>25.6. <A +HREF="bugreport.html#AEN3355" >Patches</A ></DT ></DL ></DD ><DT ->24. <A +>26. <A HREF="diagnosis.html" >Diagnosing your samba server</A ></DT ><DD ><DL ><DT ->24.1. <A -HREF="diagnosis.html#AEN3490" +>26.1. <A +HREF="diagnosis.html#AEN3378" >Introduction</A ></DT ><DT ->24.2. <A -HREF="diagnosis.html#AEN3495" +>26.2. <A +HREF="diagnosis.html#AEN3383" >Assumptions</A ></DT ><DT ->24.3. <A -HREF="diagnosis.html#AEN3505" +>26.3. <A +HREF="diagnosis.html#AEN3393" >Tests</A ></DT ><DT ->24.4. <A -HREF="diagnosis.html#AEN3615" +>26.4. <A +HREF="diagnosis.html#AEN3503" >Still having troubles?</A ></DT ></DL diff --git a/docs/htmldocs/samba-ldap-howto.html b/docs/htmldocs/samba-ldap-howto.html index fa966d8eb1..884bb756c1 100644 --- a/docs/htmldocs/samba-ldap-howto.html +++ b/docs/htmldocs/samba-ldap-howto.html @@ -5,7 +5,8 @@ >Storing Samba's User/Machine Account information in an LDAP Directory</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -72,17 +73,13 @@ WIDTH="100%"></DIV CLASS="CHAPTER" ><H1 ><A -NAME="SAMBA-LDAP-HOWTO" -></A ->Chapter 17. Storing Samba's User/Machine Account information in an LDAP Directory</H1 +NAME="SAMBA-LDAP-HOWTO">Chapter 19. Storing Samba's User/Machine Account information in an LDAP Directory</H1 ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2957" -></A ->17.1. Purpose</H1 +NAME="AEN2737">19.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 @@ -148,9 +145,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2977" -></A ->17.2. Introduction</H1 +NAME="AEN2757">19.2. Introduction</H1 ><P >Traditionally, when configuring <A HREF="smb.conf.5.html#ENCRYPTPASSWORDS" @@ -265,9 +260,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3006" -></A ->17.3. Supported LDAP Servers</H1 +NAME="AEN2786">19.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 @@ -290,9 +283,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3011" -></A ->17.4. Schema and Relationship to the RFC 2307 posixAccount</H1 +NAME="AEN2791">19.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 @@ -349,17 +340,13 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3023" -></A ->17.5. Configuring Samba with LDAP</H1 +NAME="AEN2803">19.5. Configuring Samba with LDAP</H1 ><DIV CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3025" -></A ->17.5.1. OpenLDAP configuration</H2 +NAME="AEN2805">19.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 @@ -439,9 +426,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3042" -></A ->17.5.2. Configuring Samba</H2 +NAME="AEN2822">19.5.2. Configuring Samba</H2 ><P >The following parameters are available in smb.conf only with <TT CLASS="PARAMETER" @@ -559,9 +544,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3070" -></A ->17.6. Accounts and Groups management</H1 +NAME="AEN2850">19.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 @@ -584,9 +567,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3075" -></A ->17.7. Security and sambaAccount</H1 +NAME="AEN2855">19.7. Security and sambaAccount</H1 ><P >There are two important points to remember when discussing the security of sambaAccount entries in the directory.</P @@ -663,9 +644,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3095" -></A ->17.8. LDAP specials attributes for sambaAccounts</H1 +NAME="AEN2875">19.8. LDAP specials attributes for sambaAccounts</H1 ><P >The sambaAccount objectclass is composed of the following attributes:</P ><P @@ -874,9 +853,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3165" -></A ->17.9. Example LDIF Entries for a sambaAccount</H1 +NAME="AEN2945">19.9. Example LDIF Entries for a sambaAccount</H1 ><P >The following is a working LDIF with the inclusion of the posixAccount objectclass:</P ><P @@ -932,9 +909,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3173" -></A ->17.10. Comments</H1 +NAME="AEN2953">19.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 63a52129d0..93bbc727d4 100644 --- a/docs/htmldocs/samba-pdc.html +++ b/docs/htmldocs/samba-pdc.html @@ -2,10 +2,11 @@ <HTML ><HEAD ><TITLE ->Samba as a NT4 or Win2k Primary Domain Controller</TITLE +>How to Configure Samba as a NT4 Primary Domain Controller</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -72,17 +73,13 @@ WIDTH="100%"></DIV CLASS="CHAPTER" ><H1 ><A -NAME="SAMBA-PDC" -></A ->Chapter 5. Samba as a NT4 or Win2k Primary Domain Controller</H1 +NAME="SAMBA-PDC">Chapter 6. How to Configure Samba as a NT4 Primary Domain Controller</H1 ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN722" -></A ->5.1. Prerequisite Reading</H1 +NAME="AEN575">6.1. Prerequisite Reading</H1 ><P >Before you continue reading in this chapter, please make sure that you are comfortable with configuring basic files services @@ -108,9 +105,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN728" -></A ->5.2. Background</H1 +NAME="AEN581">6.2. Background</H1 ><DIV CLASS="NOTE" ><P @@ -125,7 +120,7 @@ WIDTH="25" ALIGN="CENTER" VALIGN="TOP" ><IMG -SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif" +SRC="../images/note.gif" HSPACE="5" ALT="Note"></TD ><TD @@ -260,9 +255,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN767" -></A ->5.3. Configuring the Samba Domain Controller</H1 +NAME="AEN620">6.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 @@ -472,9 +465,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN810" -></A ->5.4. Creating Machine Trust Accounts and Joining Clients to the +NAME="AEN663">6.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 @@ -546,9 +537,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN829" -></A ->5.4.1. Manual Creation of Machine Trust Accounts</H2 +NAME="AEN682">6.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 @@ -700,7 +689,7 @@ WIDTH="25" ALIGN="CENTER" VALIGN="TOP" ><IMG -SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/warning.gif" +SRC="../images/warning.gif" HSPACE="5" ALT="Warning"></TD ><TH @@ -736,9 +725,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN870" -></A ->5.4.2. "On-the-Fly" Creation of Machine Trust Accounts</H2 +NAME="AEN723">6.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 @@ -764,7 +751,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 @@ -773,9 +760,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN879" -></A ->5.4.3. Joining the Client to the Domain</H2 +NAME="AEN732">6.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 @@ -841,9 +826,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN894" -></A ->5.5. Common Problems and Errors</H1 +NAME="AEN747">6.5. Common Problems and Errors</H1 ><P ></P ><P @@ -1051,9 +1034,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN942" -></A ->5.6. System Policies and Profiles</H1 +NAME="AEN795">6.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 @@ -1228,9 +1209,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN986" -></A ->5.7. What other help can I get?</H1 +NAME="AEN839">6.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 @@ -1648,9 +1627,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1100" -></A ->5.8. Domain Control for Windows 9x/ME</H1 +NAME="AEN953">6.8. Domain Control for Windows 9x/ME</H1 ><DIV CLASS="NOTE" ><P @@ -1665,7 +1642,7 @@ WIDTH="25" ALIGN="CENTER" VALIGN="TOP" ><IMG -SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif" +SRC="../images/note.gif" HSPACE="5" ALT="Note"></TD ><TD @@ -1727,7 +1704,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. @@ -1782,9 +1759,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1126" -></A ->5.8.1. Configuration Instructions: Network Logons</H2 +NAME="AEN979">6.8.1. Configuration Instructions: Network Logons</H2 ><P >The main difference between a PDC and a Windows 9x logon server configuration is that</P @@ -1817,7 +1792,7 @@ WIDTH="25" ALIGN="CENTER" VALIGN="TOP" ><IMG -SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/warning.gif" +SRC="../images/warning.gif" HSPACE="5" ALT="Warning"></TD ><TH @@ -1888,9 +1863,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1145" -></A ->5.8.2. Configuration Instructions: Setting up Roaming User Profiles</H2 +NAME="AEN998">6.8.2. Configuration Instructions: Setting up Roaming User Profiles</H2 ><DIV CLASS="WARNING" ><P @@ -1905,7 +1878,7 @@ WIDTH="25" ALIGN="CENTER" VALIGN="TOP" ><IMG -SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/warning.gif" +SRC="../images/warning.gif" HSPACE="5" ALT="Warning"></TD ><TD @@ -1941,9 +1914,7 @@ CLASS="SECT3" ><H3 CLASS="SECT3" ><A -NAME="AEN1153" -></A ->5.8.2.1. Windows NT Configuration</H3 +NAME="AEN1006">6.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 @@ -1972,7 +1943,7 @@ WIDTH="25" ALIGN="CENTER" VALIGN="TOP" ><IMG -SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif" +SRC="../images/note.gif" HSPACE="5" ALT="Note"></TD ><TD @@ -1992,9 +1963,7 @@ CLASS="SECT3" ><H3 CLASS="SECT3" ><A -NAME="AEN1161" -></A ->5.8.2.2. Windows 9X Configuration</H3 +NAME="AEN1014">6.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 @@ -2023,9 +1992,7 @@ CLASS="SECT3" ><H3 CLASS="SECT3" ><A -NAME="AEN1169" -></A ->5.8.2.3. Win9X and WinNT Configuration</H3 +NAME="AEN1022">6.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 @@ -2049,7 +2016,7 @@ WIDTH="25" ALIGN="CENTER" VALIGN="TOP" ><IMG -SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif" +SRC="../images/note.gif" HSPACE="5" ALT="Note"></TD ><TD @@ -2068,9 +2035,7 @@ CLASS="SECT3" ><H3 CLASS="SECT3" ><A -NAME="AEN1176" -></A ->5.8.2.4. Windows 9X Profile Setup</H3 +NAME="AEN1029">6.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". @@ -2228,9 +2193,7 @@ CLASS="SECT3" ><H3 CLASS="SECT3" ><A -NAME="AEN1212" -></A ->5.8.2.5. Windows NT Workstation 4.0</H3 +NAME="AEN1065">6.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 @@ -2249,7 +2212,7 @@ WIDTH="25" ALIGN="CENTER" VALIGN="TOP" ><IMG -SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif" +SRC="../images/note.gif" HSPACE="5" ALT="Note"></TD ><TD @@ -2307,7 +2270,7 @@ WIDTH="25" ALIGN="CENTER" VALIGN="TOP" ><IMG -SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif" +SRC="../images/note.gif" HSPACE="5" ALT="Note"></TD ><TD @@ -2342,9 +2305,7 @@ CLASS="SECT3" ><H3 CLASS="SECT3" ><A -NAME="AEN1225" -></A ->5.8.2.6. Windows NT Server</H3 +NAME="AEN1078">6.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 @@ -2356,9 +2317,7 @@ CLASS="SECT3" ><H3 CLASS="SECT3" ><A -NAME="AEN1228" -></A ->5.8.2.7. Sharing Profiles between W95 and NT Workstation 4.0</H3 +NAME="AEN1081">6.8.2.7. Sharing Profiles between W95 and NT Workstation 4.0</H3 ><DIV CLASS="WARNING" ><P @@ -2373,7 +2332,7 @@ WIDTH="25" ALIGN="CENTER" VALIGN="TOP" ><IMG -SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/warning.gif" +SRC="../images/warning.gif" HSPACE="5" ALT="Warning"></TD ><TH @@ -2425,7 +2384,7 @@ WIDTH="25" ALIGN="CENTER" VALIGN="TOP" ><IMG -SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif" +SRC="../images/note.gif" HSPACE="5" ALT="Note"></TD ><TD @@ -2449,9 +2408,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1238" -></A ->5.9. DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba</H1 +NAME="AEN1091">6.9. DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba</H1 ><DIV CLASS="WARNING" ><P @@ -2466,7 +2423,7 @@ WIDTH="25" ALIGN="CENTER" VALIGN="TOP" ><IMG -SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/warning.gif" +SRC="../images/warning.gif" HSPACE="5" ALT="Warning"></TD ><TH diff --git a/docs/htmldocs/samba.7.html b/docs/htmldocs/samba.7.html index 796bce7d20..0851e99bd5 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.7" +NAME="SAMBA" ></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,37 +63,29 @@ TARGET="_top" CLASS="VARIABLELIST" ><DL ><DT -><SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbd</SPAN ->(8)</SPAN +><B +CLASS="COMMAND" +>smbd</B ></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 <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smb.conf</SPAN ->(5)</SPAN + for this daemon is described in <TT +CLASS="FILENAME" +>smb.conf</TT > </P ></DD ><DT -><SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->nmbd</SPAN ->(8)</SPAN +><B +CLASS="COMMAND" +>nmbd</B ></DT ><DD ><P @@ -103,21 +95,15 @@ CLASS="COMMAND" > daemon provides NetBIOS nameservice and browsing support. The configuration file for this daemon - is described in <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smb.conf</SPAN ->(5)</SPAN + is described in <TT +CLASS="FILENAME" +>smb.conf</TT ></P ></DD ><DT -><SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbclient</SPAN ->(1)</SPAN +><B +CLASS="COMMAND" +>smbclient</B ></DT ><DD ><P @@ -132,12 +118,9 @@ CLASS="COMMAND" any SMB server (such as a PC running Windows NT).</P ></DD ><DT -><SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->testparm</SPAN ->(1)</SPAN +><B +CLASS="COMMAND" +>testparm</B ></DT ><DD ><P @@ -145,21 +128,16 @@ CLASS="REFENTRYTITLE" CLASS="COMMAND" >testparm</B > - utility is a simple syntax checker for Samba's <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smb.conf</SPAN ->(5)</SPAN -> configuration file.</P + utility is a simple syntax checker for Samba's + <TT +CLASS="FILENAME" +>smb.conf</TT +>configuration file.</P ></DD ><DT -><SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->testprns</SPAN ->(1)</SPAN +><B +CLASS="COMMAND" +>testprns</B ></DT ><DD ><P @@ -175,12 +153,9 @@ CLASS="FILENAME" by Samba.</P ></DD ><DT -><SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbstatus</SPAN ->(1)</SPAN +><B +CLASS="COMMAND" +>smbstatus</B ></DT ><DD ><P @@ -195,12 +170,9 @@ CLASS="COMMAND" >.</P ></DD ><DT -><SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->nmblookup</SPAN ->(1)</SPAN +><B +CLASS="COMMAND" +>nmblookup</B ></DT ><DD ><P @@ -212,30 +184,26 @@ CLASS="COMMAND" from a UNIX host.</P ></DD ><DT -><SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbgroupedit</SPAN ->(8)</SPAN +><B +CLASS="COMMAND" +>make_smbcodepage</B ></DT ><DD ><P >The <B CLASS="COMMAND" ->smbgroupedit</B +>make_smbcodepage</B > - 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 + utility provides a means of creating SMB code page + definition files for your <B +CLASS="COMMAND" +>smbd</B +> server.</P ></DD ><DT -><SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbpasswd</SPAN ->(8)</SPAN +><B +CLASS="COMMAND" +>smbpasswd</B ></DT ><DD ><P @@ -252,7 +220,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN99" +NAME="AEN76" ></A ><H2 >COMPONENTS</H2 @@ -281,7 +249,7 @@ TARGET="_top" ><DIV CLASS="REFSECT1" ><A -NAME="AEN105" +NAME="AEN82" ></A ><H2 >AVAILABILITY</H2 @@ -306,8 +274,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 Mozilla - or Konqueror) then you will also find lots of useful information, +>If you have access to a WWW viewer (such as Netscape + or Mosaic) then you will also find lots of useful information, including back issues of the Samba mailing list, at <A HREF="http://lists.samba.org/" @@ -318,18 +286,18 @@ TARGET="_top" ><DIV CLASS="REFSECT1" ><A -NAME="AEN113" +NAME="AEN90" ></A ><H2 >VERSION</H2 ><P ->This man page is correct for version 3.0 of the +>This man page is correct for version 2.2 of the Samba suite. </P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN116" +NAME="AEN93" ></A ><H2 >CONTRIBUTIONS</H2 @@ -349,8 +317,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 @@ -358,7 +326,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN123" +NAME="AEN100" ></A ><H2 >CONTRIBUTORS</H2 @@ -390,7 +358,7 @@ TARGET="_top" ><DIV CLASS="REFSECT1" ><A -NAME="AEN130" +NAME="AEN107" ></A ><H2 >AUTHOR</H2 @@ -402,14 +370,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. The conversion to DocBook XML - 4.2 for Samba 3.0 was done by Alexander Bokovoy.</P + Samba 2.2 was done by Gerald Carter</P ></DIV ></BODY ></HTML diff --git a/docs/htmldocs/securitylevels.html b/docs/htmldocs/securitylevels.html index 9501fa5c6a..f1b9967540 100644 --- a/docs/htmldocs/securitylevels.html +++ b/docs/htmldocs/securitylevels.html @@ -5,7 +5,8 @@ >User and Share security level (for servers not in a domain)</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -16,7 +17,7 @@ REL="PREVIOUS" TITLE="Type of installation" HREF="type.html"><LINK REL="NEXT" -TITLE="Samba as a NT4 or Win2k Primary Domain Controller" +TITLE="How to Configure Samba as a NT4 Primary Domain Controller" HREF="samba-pdc.html"></HEAD ><BODY CLASS="CHAPTER" @@ -72,9 +73,7 @@ WIDTH="100%"></DIV CLASS="CHAPTER" ><H1 ><A -NAME="SECURITYLEVELS" -></A ->Chapter 4. User and Share security level (for servers not in a domain)</H1 +NAME="SECURITYLEVELS">Chapter 5. 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 @@ -226,7 +225,7 @@ ACCESSKEY="U" WIDTH="33%" ALIGN="right" VALIGN="top" ->Samba as a NT4 or Win2k Primary Domain Controller</TD +>How to Configure Samba as a NT4 Primary Domain Controller</TD ></TR ></TABLE ></DIV diff --git a/docs/htmldocs/smb.conf.5.html b/docs/htmldocs/smb.conf.5.html index 5a8bfe7d67..9c1ee7a67b 100644 --- a/docs/htmldocs/smb.conf.5.html +++ b/docs/htmldocs/smb.conf.5.html @@ -1,11 +1,12 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"> <HTML ><HEAD ><TITLE >smb.conf</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"></HEAD +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"></HEAD ><BODY CLASS="REFENTRY" BGCOLOR="#FFFFFF" @@ -15,9 +16,7 @@ VLINK="#840084" ALINK="#0000FF" ><H1 ><A -NAME="SMB.CONF.5" -></A ->smb.conf</H1 +NAME="SMB.CONF">smb.conf</H1 ><DIV CLASS="REFNAMEDIV" ><A @@ -37,29 +36,31 @@ 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 <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 +> 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 ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN17" +NAME="AEN16" ></A ><H2 >FILE FORMAT</H2 @@ -109,7 +110,7 @@ CLASS="REPLACEABLE" ><DIV CLASS="REFSECT1" ><A -NAME="AEN29" +NAME="AEN28" ></A ><H2 >SECTION DESCRIPTIONS</H2 @@ -122,12 +123,9 @@ NAME="AEN29" ><P >There are three special sections, [global], [homes] and [printers], which are - described under <SPAN -CLASS="emphasis" -><I + described under <I CLASS="EMPHASIS" >special sections</I -></SPAN >. The following notes apply to ordinary section descriptions.</P ><P @@ -141,20 +139,14 @@ CLASS="EMPHASIS" printable services (used by the client to access print services on the host running the server).</P ><P ->Sections may be designated <SPAN -CLASS="emphasis" -><I +>Sections may be designated <I CLASS="EMPHASIS" >guest</I -></SPAN > services, in which case no password is required to access them. A specified - UNIX <SPAN -CLASS="emphasis" -><I + UNIX <I CLASS="EMPHASIS" >guest account</I -></SPAN > is used to define access privileges in this case.</P ><P @@ -176,49 +168,68 @@ 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 +> [foo] + path = /home/bar + read only = no + </TT +> + </PRE +></TD +></TR +></TABLE ><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 <SPAN -CLASS="emphasis" -><I + spool file. The <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 +> [aprinter] + path = /usr/spool/public + read only = yes + printable = yes + guest ok = yes + </TT +> + </PRE +></TD +></TR +></TABLE ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN49" +NAME="AEN48" ></A ><H2 >SPECIAL SECTIONS</H2 ><DIV CLASS="REFSECT2" ><A -NAME="AEN51" +NAME="AEN50" ></A ><H3 >The [global] section</H3 @@ -231,7 +242,7 @@ NAME="AEN51" ><DIV CLASS="REFSECT2" ><A -NAME="AEN54" +NAME="AEN53" ></A ><H3 >The [homes] section</H3 @@ -264,12 +275,9 @@ NAME="AEN54" ></LI ></UL ><P ->If you decide to use a <SPAN -CLASS="emphasis" -><I +>If you decide to use a <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 @@ -298,48 +306,47 @@ 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 +> [homes] + read only = no + </TT +> + </PRE +></TD +></TR +></TABLE ><P >An important point is that if guest access is specified in the [homes] section, all home directories will be - visible to all clients <SPAN -CLASS="emphasis" -><I + visible to all clients <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 <SPAN -CLASS="emphasis" -><I + would be wise to also specify <I CLASS="EMPHASIS" >read only access</I -></SPAN >.</P ><P ->Note that the <SPAN -CLASS="emphasis" -><I +>Note that the <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 <SPAN -CLASS="emphasis" -><I + it means setting <I CLASS="EMPHASIS" >browseable = no</I -></SPAN > in the [homes] section will hide the [homes] share but make any auto home directories visible.</P @@ -347,7 +354,7 @@ CLASS="EMPHASIS" ><DIV CLASS="REFSECT2" ><A -NAME="AEN80" +NAME="AEN79" ></A ><H3 >The [printers] section</H3 @@ -399,27 +406,48 @@ NAME="AEN80" 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 +> alias|alias|alias|alias... + </TT +> + </PRE +></TD +></TR +></TABLE ><P >Each alias should be an acceptable printer name for your printing subsystem. In the [global] section, specify @@ -443,7 +471,7 @@ CLASS="COMPUTEROUTPUT" ><DIV CLASS="REFSECT1" ><A -NAME="AEN103" +NAME="AEN102" ></A ><H2 >PARAMETERS</H2 @@ -451,44 +479,29 @@ NAME="AEN103" >parameters define the specific attributes of sections.</P ><P >Some parameters are specific to the [global] section - (e.g., <SPAN -CLASS="emphasis" -><I + (e.g., <I CLASS="EMPHASIS" >security</I -></SPAN >). Some parameters are usable - in all sections (e.g., <SPAN -CLASS="emphasis" -><I + in all sections (e.g., <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 <SPAN -CLASS="emphasis" -><I + sections will be considered normal. The letter <I CLASS="EMPHASIS" >G</I -></SPAN > in parentheses indicates that a parameter is specific to the - [global] section. The letter <SPAN -CLASS="emphasis" -><I + [global] section. The letter <I CLASS="EMPHASIS" >S</I -></SPAN > indicates that a parameter can be specified in a service specific - section. Note that all <SPAN -CLASS="emphasis" -><I + section. Note that all <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 @@ -501,7 +514,7 @@ CLASS="EMPHASIS" ><DIV CLASS="REFSECT1" ><A -NAME="AEN113" +NAME="AEN112" ></A ><H2 >VARIABLE SUBSTITUTIONS</H2 @@ -678,12 +691,9 @@ 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 <SPAN -CLASS="emphasis" -><I + not compiled Samba with the <I CLASS="EMPHASIS" >--with-automount</I -></SPAN > option then this value will be the same as %L.</P ></DD @@ -704,7 +714,7 @@ CLASS="EMPHASIS" ><DIV CLASS="REFSECT1" ><A -NAME="AEN206" +NAME="AEN205" ></A ><H2 >NAME MANGLING</H2 @@ -733,12 +743,9 @@ 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 <SPAN -CLASS="emphasis" -><I + Default <I CLASS="EMPHASIS" >no</I -></SPAN >.</P ></DD ><DT @@ -747,12 +754,9 @@ 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 <SPAN -CLASS="emphasis" -><I + names. Default <I CLASS="EMPHASIS" >no</I -></SPAN >.</P ></DD ><DT @@ -760,12 +764,9 @@ CLASS="EMPHASIS" ><DD ><P >controls what the default case is for new - filenames. Default <SPAN -CLASS="emphasis" -><I + filenames. Default <I CLASS="EMPHASIS" >lower</I -></SPAN >.</P ></DD ><DT @@ -774,12 +775,9 @@ 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 <SPAN -CLASS="emphasis" -><I + "default" case. Default <I CLASS="EMPHASIS" >yes</I -></SPAN >. </P ></DD @@ -792,12 +790,9 @@ 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 <SPAN -CLASS="emphasis" -><I + are lowercased. Default <I CLASS="EMPHASIS" >yes</I -></SPAN >.</P ></DD ></DL @@ -809,7 +804,7 @@ CLASS="EMPHASIS" ><DIV CLASS="REFSECT1" ><A -NAME="AEN239" +NAME="AEN238" ></A ><H2 >NOTE ABOUT USERNAME/PASSWORD VALIDATION</H2 @@ -887,7 +882,7 @@ CLASS="FILENAME" ><DIV CLASS="REFSECT1" ><A -NAME="AEN258" +NAME="AEN257" ></A ><H2 >COMPLETE LIST OF GLOBAL PARAMETERS</H2 @@ -3182,7 +3177,7 @@ CLASS="PARAMETER" ><DIV CLASS="REFSECT1" ><A -NAME="AEN1022" +NAME="AEN1021" ></A ><H2 >COMPLETE LIST OF SERVICE PARAMETERS</H2 @@ -4697,7 +4692,7 @@ CLASS="PARAMETER" ><DIV CLASS="REFSECT1" ><A -NAME="AEN1526" +NAME="AEN1525" ></A ><H2 >EXPLANATION OF EACH PARAMETER</H2 @@ -4710,23 +4705,22 @@ 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 <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbd</SPAN ->(8)</SPAN -> that + 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 should stop a shutdown procedure issued by the <A HREF="#SHUTDOWNSCRIPT" ><TT @@ -4739,12 +4733,9 @@ CLASS="PARAMETER" ><P >This command will be run as user.</P ><P ->Default: <SPAN -CLASS="emphasis" -><I +>Default: <I CLASS="EMPHASIS" >None</I -></SPAN >.</P ><P >Example: <B @@ -4756,7 +4747,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 @@ -4780,12 +4771,14 @@ CLASS="PARAMETER" CLASS="FILENAME" >smb.conf</TT > file in order that it can be - shared by <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbd</SPAN ->(8)</SPAN + shared by <A +HREF="smbd.8.html" +TARGET="_top" +><B +CLASS="COMMAND" +>smbd(8)</B +> + </A >.</P ><P >The <TT @@ -4795,7 +4788,7 @@ CLASS="PARAMETER" ></TT > is automatically invoked with the following parameter (in - order):</P + order:</P ><P ></P ><UL @@ -4909,12 +4902,9 @@ CLASS="PARAMETER" ></A ></P ><P ->Default: <SPAN -CLASS="emphasis" -><I +>Default: <I CLASS="EMPHASIS" >none</I -></SPAN ></P ><P >Example: <B @@ -4927,7 +4917,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 @@ -5053,12 +5043,9 @@ CLASS="PARAMETER" >. </P ><P ->Default: <SPAN -CLASS="emphasis" -><I +>Default: <I CLASS="EMPHASIS" >none</I -></SPAN ></P ><P >Example: <B @@ -5070,17 +5057,15 @@ 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 <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbd</SPAN ->(8)</SPAN -> when a machine is added + be run by <A +HREF="smbd.8.html" +TARGET="_top" +>smbd(8)</A +> 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 @@ -5089,7 +5074,7 @@ CLASS="REFENTRYTITLE" ><P >Default: <B CLASS="COMMAND" ->add machine script = <empty string> +>add machine script = <empty string> </B ></P ><P @@ -5103,7 +5088,7 @@ CLASS="COMMAND" ><A NAME="ADSSERVER" ></A ->>ads server (G)</DT +>ads server (G)</DT ><DD ><P >If this option is specified, samba does @@ -5125,22 +5110,18 @@ 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 <SPAN -CLASS="emphasis" -><I + be run <I CLASS="EMPHASIS" >AS ROOT</I -></SPAN -> by <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbd</SPAN ->(8)</SPAN +> by <A +HREF="smbd.8.html" +TARGET="_top" +>smbd(8) + </A > under special circumstances described below.</P ><P >Normally, a Samba server requires that UNIX users are @@ -5152,26 +5133,19 @@ HREF="smbd.8.html" TARGET="_top" >smbd</A > to create the required UNIX users - <SPAN -CLASS="emphasis" -><I + <I CLASS="EMPHASIS" >ON DEMAND</I -></SPAN > when a user accesses the Samba server.</P ><P ->In order to use this option, <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbd</SPAN ->(8)</SPAN -> must <SPAN -CLASS="emphasis" -><I +>In order to use this option, <A +HREF="smbd.8.html" +TARGET="_top" +>smbd</A +> + must <I CLASS="EMPHASIS" >NOT</I -></SPAN > be set to <TT CLASS="PARAMETER" ><I @@ -5194,12 +5168,10 @@ 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, <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbd</SPAN ->(8)</SPAN + at login (session setup in the SMB protocol) time, <A +HREF="smbd.8.html" +TARGET="_top" +> smbd</A > contacts the <TT CLASS="PARAMETER" ><I @@ -5222,12 +5194,9 @@ CLASS="PARAMETER" CLASS="COMMAND" >smbd</B > will - call the specified script <SPAN -CLASS="emphasis" -><I + call the specified script <I CLASS="EMPHASIS" >AS ROOT</I -></SPAN >, expanding any <TT CLASS="PARAMETER" @@ -5274,7 +5243,7 @@ CLASS="PARAMETER" ><P >Default: <B CLASS="COMMAND" ->add user script = <empty string> +>add user script = <empty string> </B ></P ><P @@ -5288,22 +5257,17 @@ 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 <SPAN -CLASS="emphasis" -><I + be run <I CLASS="EMPHASIS" >AS ROOT</I -></SPAN -> by <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbd</SPAN ->(8)</SPAN +> by <A +HREF="smbd.8.html" +TARGET="_top" +>smbd(8)</A > when a new group is requested. It will expand any <TT @@ -5324,7 +5288,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 @@ -5335,12 +5299,9 @@ NAME="ADMINUSERS" this list will be able to do anything they like on the share, irrespective of file permissions.</P ><P ->Default: <SPAN -CLASS="emphasis" -><I +>Default: <I CLASS="EMPHASIS" >no admin users</I -></SPAN ></P ><P >Example: <B @@ -5352,36 +5313,32 @@ 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 <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbd</SPAN ->(8)</SPAN -> <SPAN -CLASS="emphasis" -><I + tools. It will be run by <A +HREF="smbd.8.html" +TARGET="_top" +>smbd(8)</A +> + <I CLASS="EMPHASIS" >AS ROOT</I -></SPAN ->. - Any <TT +>. 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 @@ -5398,7 +5355,7 @@ CLASS="COMMAND" ><A NAME="ALLOWHOSTS" ></A ->>allow hosts (S)</DT +>allow hosts (S)</DT ><DD ><P >Synonym for <A @@ -5415,7 +5372,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 @@ -5447,7 +5404,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 @@ -5493,16 +5450,19 @@ CLASS="COMMAND" ><A NAME="ANNOUNCEAS" ></A ->>announce as (G)</DT +>announce as (G)</DT ><DD ><P ->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 +>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 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, @@ -5526,7 +5486,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 @@ -5548,7 +5508,7 @@ CLASS="COMMAND" ><A NAME="AUTOSERVICES" ></A ->>auto services (G)</DT +>auto services (G)</DT ><DD ><P >This is a synonym for the <A @@ -5565,7 +5525,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 @@ -5590,7 +5550,7 @@ CLASS="PARAMETER" ><P >Default: <B CLASS="COMMAND" ->auth methods = <empty string></B +>auth methods = <empty string></B ></P ><P >Example: <B @@ -5602,7 +5562,7 @@ CLASS="COMMAND" ><A NAME="AVAILABLE" ></A ->>available (S)</DT +>available (S)</DT ><DD ><P >This parameter lets you "turn off" a service. If @@ -5611,12 +5571,9 @@ CLASS="PARAMETER" ><I >available = no</I ></TT ->, then <SPAN -CLASS="emphasis" -><I +>, then <I CLASS="EMPHASIS" >ALL</I -></SPAN > attempts to connect to the service will fail. Such failures are logged.</P @@ -5630,24 +5587,22 @@ 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 <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 + 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 ><P >For name service it causes <B CLASS="COMMAND" @@ -5702,14 +5657,12 @@ CLASS="COMMAND" >nmbd</B >.</P ><P ->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 +>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 HREF="#INTERFACES" > interfaces</A > parameter. This restricts the networks that @@ -5727,42 +5680,40 @@ CLASS="PARAMETER" >bind interfaces only</I ></TT > is set then - unless the network address <SPAN -CLASS="emphasis" -><I + unless the network address <I CLASS="EMPHASIS" >127.0.0.1</I -></SPAN > is added to the <TT CLASS="PARAMETER" ><I >interfaces</I ></TT -> 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 +> 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 ><P >To change a users SMB password, the <B CLASS="COMMAND" >smbpasswd</B > - by default connects to the <SPAN -CLASS="emphasis" -><I + by default connects to the <I CLASS="EMPHASIS" >localhost - 127.0.0.1</I -></SPAN > address as an SMB client to issue the password change request. If <TT @@ -5771,12 +5722,9 @@ CLASS="PARAMETER" >bind interfaces only</I ></TT > is set then unless the - network address <SPAN -CLASS="emphasis" -><I + network address <I CLASS="EMPHASIS" >127.0.0.1</I -></SPAN > is added to the <TT CLASS="PARAMETER" @@ -5791,13 +5739,10 @@ CLASS="COMMAND" CLASS="COMMAND" >smbpasswd</B > can be forced to use the primary IP interface - of the local host by using its <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbpasswd</SPAN ->(8)</SPAN -> <TT + of the local host by using its <A +HREF="smbpasswd.8.html#minusr" +TARGET="_top" +> <TT CLASS="PARAMETER" ><I >-r <TT @@ -5808,7 +5753,8 @@ CLASS="REPLACEABLE" ></I ></TT > - parameter, with <TT + </A +> parameter, with <TT CLASS="REPLACEABLE" ><I >remote machine</I @@ -5827,19 +5773,13 @@ CLASS="COMMAND" CLASS="COMMAND" >nmbd</B > at the address - <SPAN -CLASS="emphasis" -><I + <I CLASS="EMPHASIS" >127.0.0.1</I -></SPAN > to determine if they are running. - Not adding <SPAN -CLASS="emphasis" -><I + Not adding <I CLASS="EMPHASIS" >127.0.0.1</I -></SPAN > will cause <B CLASS="COMMAND" > smbd</B @@ -5868,16 +5808,13 @@ CLASS="COMMAND" ><A NAME="BLOCKINGLOCKS" ></A ->>blocking locks (S)</DT +>blocking locks (S)</DT ><DD ><P ->This parameter controls the behavior - of <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbd</SPAN ->(8)</SPAN +>This parameter controls the behavior of <A +HREF="smbd.8.html" +TARGET="_top" +>smbd(8)</A > 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 @@ -5904,15 +5841,14 @@ CLASS="COMMAND" ><A NAME="BLOCKSIZE" ></A ->>block size (S)</DT +>block size (S)</DT ><DD ><P ->This parameter controls the behavior of <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbd</SPAN ->(8)</SPAN +>This parameter controls the behavior of + <A +HREF="smbd.8.html" +TARGET="_top" +>smbd(8)</A > when reporting disk free sizes. By default, this reports a disk block size of 1024 bytes. </P @@ -5927,12 +5863,22 @@ CLASS="REFENTRYTITLE" ><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 @@ -5949,15 +5895,16 @@ CLASS="PARAMETER" ><A NAME="BROWSELIST" ></A ->>browse list (G)</DT +>browse list (G)</DT ><DD ><P ->This controls whether <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbd</SPAN ->(8)</SPAN +>This controls whether <A +HREF="smbd.8.html" +TARGET="_top" +> <B +CLASS="COMMAND" +>smbd(8)</B +></A > will serve a browse list to a client doing a <B CLASS="COMMAND" @@ -5978,7 +5925,7 @@ CLASS="COMMAND" ><A NAME="BROWSEABLE" ></A ->>browseable (S)</DT +>browseable (S)</DT ><DD ><P >This controls whether this share is seen in @@ -5993,11 +5940,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="#AEN206" +HREF="#AEN205" >NAME MANGLING</A >.</P ><P @@ -6010,7 +5957,7 @@ CLASS="COMMAND" ><A NAME="CASESIGNAMES" ></A ->>casesignames (S)</DT +>casesignames (S)</DT ><DD ><P >Synonym for <A @@ -6023,18 +5970,19 @@ 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 <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbd</SPAN ->(8)</SPAN + a directory is expensive under UNIX, hence an <A +HREF="smbd.8.html" +TARGET="_top" +> <B +CLASS="COMMAND" +>smbd(8)</B +></A > daemon only performs such a scan on each requested directory once every <TT CLASS="PARAMETER" @@ -6060,7 +6008,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 @@ -6177,12 +6125,9 @@ CLASS="PARAMETER" >. </P ><P ->Default: <SPAN -CLASS="emphasis" -><I +>Default: <I CLASS="EMPHASIS" >none</I -></SPAN ></P ><P >Example: <B @@ -6194,7 +6139,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 @@ -6216,12 +6161,9 @@ CLASS="PARAMETER" ></A > parameter.</P ><P ->Default: <SPAN -CLASS="emphasis" -><I +>Default: <I CLASS="EMPHASIS" >No comment string</I -></SPAN ></P ><P >Example: <B @@ -6233,7 +6175,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 @@ -6265,7 +6207,7 @@ CLASS="COMMAND" ><A NAME="COPY" ></A ->>copy (S)</DT +>copy (S)</DT ><DD ><P >This parameter allows you to "clone" service @@ -6278,12 +6220,9 @@ NAME="COPY" copied must occur earlier in the configuration file than the service doing the copying.</P ><P ->Default: <SPAN -CLASS="emphasis" -><I +>Default: <I CLASS="EMPHASIS" >no value</I -></SPAN ></P ><P >Example: <B @@ -6295,7 +6234,7 @@ CLASS="COMMAND" ><A NAME="CREATEMASK" ></A ->>create mask (S)</DT +>create mask (S)</DT ><DD ><P >A synonym for this parameter is @@ -6314,12 +6253,9 @@ 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 <SPAN -CLASS="emphasis" -><I + MASK for the UNIX modes of a file. Any bit <I CLASS="EMPHASIS" >not</I -></SPAN > set here will be removed from the modes set on a file when it is created.</P @@ -6406,7 +6342,7 @@ CLASS="COMMAND" ><A NAME="CREATEMODE" ></A ->>create mode (S)</DT +>create mode (S)</DT ><DD ><P >This is a synonym for <A @@ -6423,16 +6359,13 @@ CLASS="PARAMETER" ><A NAME="CSCPOLICY" ></A ->>csc policy (S)</DT +>csc policy (S)</DT ><DD ><P ->This stands for <SPAN -CLASS="emphasis" -><I +>This stands for <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 @@ -6461,7 +6394,7 @@ CLASS="COMMAND" ><A NAME="DEADTIME" ></A ->>deadtime (G)</DT +>deadtime (G)</DT ><DD ><P >The value of the parameter (a decimal integer) @@ -6496,7 +6429,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 @@ -6524,7 +6457,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 @@ -6556,7 +6489,7 @@ CLASS="COMMAND" ><A NAME="DEBUGTIMESTAMP" ></A ->>debug timestamp (G)</DT +>debug timestamp (G)</DT ><DD ><P >Samba debug log messages are timestamped @@ -6581,7 +6514,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 @@ -6609,7 +6542,7 @@ CLASS="COMMAND" ><A NAME="DEBUGLEVEL" ></A ->>debuglevel (G)</DT +>debuglevel (G)</DT ><DD ><P >Synonym for <A @@ -6626,7 +6559,7 @@ CLASS="PARAMETER" ><A NAME="DEFAULT" ></A ->>default (G)</DT +>default (G)</DT ><DD ><P >A synonym for <A @@ -6643,11 +6576,11 @@ CLASS="PARAMETER" ><A NAME="DEFAULTCASE" ></A ->>default case (S)</DT +>default case (S)</DT ><DD ><P >See the section on <A -HREF="#AEN206" +HREF="#AEN205" > NAME MANGLING</A >. Also note the <A HREF="#SHORTPRESERVECASE" @@ -6668,7 +6601,7 @@ CLASS="COMMAND" ><A NAME="DEFAULTDEVMODE" ></A ->>default devmode (S)</DT +>default devmode (S)</DT ><DD ><P >This parameter is only applicable to <A @@ -6719,17 +6652,14 @@ 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 <SPAN -CLASS="emphasis" -><I + be found. Note that the square brackets are <I CLASS="EMPHASIS" >NOT</I -></SPAN > given in the parameter value (see example below).</P ><P @@ -6771,50 +6701,53 @@ 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 + path = /%S + </PRE +></TD +></TR +></TABLE ></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 <SPAN -CLASS="emphasis" -><I + be run <I CLASS="EMPHASIS" >AS ROOT</I -></SPAN -> <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbd</SPAN ->(8)</SPAN -> when a group is requested to be deleted. - It will expand any <TT +> by <A +HREF="smbd.8.html" +TARGET="_top" +>smbd(8)</A +> 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 @@ -6896,12 +6829,9 @@ CLASS="PARAMETER" ></A ></P ><P ->Default: <SPAN -CLASS="emphasis" -><I +>Default: <I CLASS="EMPHASIS" >none</I -></SPAN ></P ><P >Example: <B @@ -6914,7 +6844,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. @@ -6933,7 +6863,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 @@ -7037,12 +6967,9 @@ CLASS="PARAMETER" >. </P ><P ->Default: <SPAN -CLASS="emphasis" -><I +>Default: <I CLASS="EMPHASIS" >none</I -></SPAN ></P ><P >Example: <B @@ -7054,18 +6981,19 @@ 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 <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbd</SPAN ->(8)</SPAN -> when managing users - with remote RPC (NT) tools. + 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. </P ><P >This script is called when a remote client removes a user @@ -7081,7 +7009,7 @@ CLASS="COMMAND" ><P >Default: <B CLASS="COMMAND" ->delete user script = <empty string> +>delete user script = <empty string> </B ></P ><P @@ -7095,36 +7023,32 @@ 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 <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbd</SPAN ->(8)</SPAN -> <SPAN -CLASS="emphasis" -><I + tools. It will be run by <A +HREF="smbd.8.html" +TARGET="_top" +>smbd(8)</A +> + <I CLASS="EMPHASIS" >AS ROOT</I -></SPAN ->. - Any <TT +>. 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 @@ -7141,7 +7065,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 @@ -7202,7 +7126,7 @@ CLASS="COMMAND" ><A NAME="DENYHOSTS" ></A ->>deny hosts (S)</DT +>deny hosts (S)</DT ><DD ><P >Synonym for <A @@ -7220,7 +7144,7 @@ CLASS="PARAMETER" ><A NAME="DFREECOMMAND" ></A ->>dfree command (G)</DT +>dfree command (G)</DT ><DD ><P >The <TT @@ -7251,23 +7175,17 @@ CLASS="FILENAME" third return value can give the block size in bytes. The default blocksize is 1024 bytes.</P ><P ->Note: Your script should <SPAN -CLASS="emphasis" -><I +>Note: Your script should <I CLASS="EMPHASIS" >NOT</I -></SPAN > be setuid or setgid and should be owned by (and writeable only by) root!</P ><P ->Default: <SPAN -CLASS="emphasis" -><I +>Default: <I CLASS="EMPHASIS" >By default internal routines for determining the disk capacity and remaining space will be used. </I -></SPAN ></P ><P >Example: <B @@ -7278,20 +7196,40 @@ 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 + #!/bin/sh + df $1 | tail -1 | awk '{print $2" "$4}' + </PRE +></TD +></TR +></TABLE ></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 + #!/bin/sh + /usr/bin/df -k $1 | tail -1 | awk '{print $3" "$5}' + </PRE +></TD +></TR +></TABLE ></P ><P >Note that you may have to replace the command names @@ -7301,7 +7239,7 @@ CLASS="PROGRAMLISTING" ><A NAME="DIRECTORY" ></A ->>directory (S)</DT +>directory (S)</DT ><DD ><P >Synonym for <A @@ -7319,7 +7257,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 @@ -7330,12 +7268,9 @@ 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 <SPAN -CLASS="emphasis" -><I + the UNIX modes of a directory. Any bit <I CLASS="EMPHASIS" >not</I -></SPAN > set here will be removed from the modes set on a directory when it is created.</P @@ -7426,7 +7361,7 @@ CLASS="COMMAND" ><A NAME="DIRECTORYMODE" ></A ->>directory mode (S)</DT +>directory mode (S)</DT ><DD ><P >Synonym for <A @@ -7443,7 +7378,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 @@ -7461,12 +7396,9 @@ 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. @@ -7518,7 +7450,7 @@ CLASS="COMMAND" ><A NAME="DISABLENETBIOS" ></A ->>disable netbios (G)</DT +>disable netbios (G)</DT ><DD ><P >Enabling this parameter will disable netbios support @@ -7543,7 +7475,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 @@ -7555,12 +7487,9 @@ 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. - <SPAN -CLASS="emphasis" -><I + <I CLASS="EMPHASIS" >Be very careful about enabling this parameter.</I -></SPAN > </P ><P @@ -7579,7 +7508,7 @@ CLASS="COMMAND" ><A NAME="DISPLAYCHARSET" ></A ->>display charset (G)</DT +>display charset (G)</DT ><DD ><P >Specifies the charset that samba will use @@ -7604,19 +7533,18 @@ CLASS="COMMAND" ><A NAME="DNSPROXY" ></A ->>dns proxy (G)</DT +>dns proxy (G)</DT ><DD ><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 +>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 ><P >Note that the maximum length for a NetBIOS name is 15 characters, so the DNS name (or DNS alias) can likewise only be @@ -7648,7 +7576,7 @@ CLASS="COMMAND" ><A NAME="DOMAINLOGONS" ></A ->>domain logons (G)</DT +>domain logons (G)</DT ><DD ><P >If set to <TT @@ -7681,15 +7609,16 @@ CLASS="COMMAND" ><A NAME="DOMAINMASTER" ></A ->>domain master (G)</DT +>domain master (G)</DT ><DD ><P ->Tell <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbd</SPAN ->(8)</SPAN +>Tell <A +HREF="nmbd.8.html" +TARGET="_top" +><B +CLASS="COMMAND" +> nmbd(8)</B +></A > to enable WAN-wide browse list collation. Setting this option causes <B CLASS="COMMAND" @@ -7715,16 +7644,18 @@ CLASS="PARAMETER" CLASS="COMMAND" >nmbd</B > their local browse lists, - 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 + 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 ><P >Note that Windows NT Primary Domain Controllers expect to be able to claim this <TT @@ -7790,7 +7721,7 @@ CLASS="COMMAND" ><A NAME="DONTDESCEND" ></A ->>dont descend (S)</DT +>dont descend (S)</DT ><DD ><P >There are certain directories on some systems @@ -7812,13 +7743,10 @@ CLASS="FILENAME" >. Experimentation is the best policy :-) </P ><P ->Default: <SPAN -CLASS="emphasis" -><I +>Default: <I CLASS="EMPHASIS" >none (i.e., all directories are OK to descend)</I -></SPAN ></P ><P >Example: <B @@ -7830,7 +7758,7 @@ CLASS="COMMAND" ><A NAME="DOSCHARSET" ></A ->>dos charset (G)</DT +>dos charset (G)</DT ><DD ><P >DOS SMB clients assume the server has @@ -7840,12 +7768,11 @@ 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 <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->testparm</SPAN ->(1)</SPAN + case it is not available. Run <A +HREF="testparm.1.html" +TARGET="_top" +>testparm(1) + </A > to check the default on your system. </P ></DD @@ -7853,7 +7780,7 @@ CLASS="REFENTRYTITLE" ><A NAME="DOSFILEMODE" ></A ->>dos filemode (S)</DT +>dos filemode (S)</DT ><DD ><P > The default behavior in Samba is to provide @@ -7876,19 +7803,21 @@ 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 <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbd</SPAN ->(8)</SPAN + resolution is made to <A +HREF="smbd.8.html" +TARGET="_top" +><B +CLASS="COMMAND" +>smbd(8)</B +> + </A >.</P ><P >This option is mainly used as a compatibility option for Visual @@ -7911,7 +7840,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 @@ -7925,12 +7854,10 @@ CLASS="COMMAND" on behalf of is not the file owner. Setting this option to <TT CLASS="CONSTANT" > yes</TT -> allows DOS semantics and <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbd</SPAN ->(8)</SPAN +> allows DOS semantics and <A +HREF="smbd.8.html" +TARGET="_top" +>smbd</A > will change the file timestamp as DOS requires.</P ><P @@ -7943,7 +7870,7 @@ CLASS="COMMAND" ><A NAME="ENCRYPTPASSWORDS" ></A ->>encrypt passwords (G)</DT +>encrypt passwords (G)</DT ><DD ><P >This boolean controls whether encrypted passwords @@ -7957,25 +7884,29 @@ CLASS="FILENAME" > shipped with the source code.</P ><P >In order for encrypted passwords to work correctly - <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbd</SPAN ->(8)</SPAN + <A +HREF="smbd.8.html" +TARGET="_top" +><B +CLASS="COMMAND" +>smbd(8)</B +></A > must either - 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 + 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 > program for information on how to set up and maintain this file), or set the <A HREF="#SECURITY" @@ -7996,7 +7927,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 @@ -8027,7 +7958,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 @@ -8059,12 +7990,9 @@ CLASS="PARAMETER" to standard output. This listing will then be used in response to the level 1 and 2 EnumPorts() RPC.</P ><P ->Default: <SPAN -CLASS="emphasis" -><I +>Default: <I CLASS="EMPHASIS" >no enumports command</I -></SPAN ></P ><P >Example: <B @@ -8077,7 +8005,7 @@ CLASS="COMMAND" ><A NAME="EXEC" ></A ->>exec (S)</DT +>exec (S)</DT ><DD ><P >This is a synonym for <A @@ -8094,7 +8022,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 @@ -8132,7 +8060,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 @@ -8185,18 +8113,19 @@ CLASS="COMMAND" ><A NAME="FOLLOWSYMLINKS" ></A ->>follow symlinks (S)</DT +>follow symlinks (S)</DT ><DD ><P >This parameter allows the Samba administrator - to stop <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbd</SPAN ->(8)</SPAN -> from following symbolic - links in a particular share. Setting this + 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 parameter to <TT CLASS="CONSTANT" >no</TT @@ -8225,16 +8154,13 @@ 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 <SPAN -CLASS="emphasis" -><I + permissions that will <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 @@ -8288,16 +8214,13 @@ 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 <SPAN -CLASS="emphasis" -><I + permissions that will <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 @@ -8350,7 +8273,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 @@ -8367,12 +8290,9 @@ 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. @@ -8421,7 +8341,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 @@ -8482,12 +8402,9 @@ CLASS="PARAMETER" ></A >.</P ><P ->Default: <SPAN -CLASS="emphasis" -><I +>Default: <I CLASS="EMPHASIS" >no forced group</I -></SPAN ></P ><P >Example: <B @@ -8499,7 +8416,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 @@ -8517,12 +8434,9 @@ 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. @@ -8571,7 +8485,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 @@ -8601,12 +8515,9 @@ CLASS="PARAMETER" ></A ></P ><P ->Default: <SPAN -CLASS="emphasis" -><I +>Default: <I CLASS="EMPHASIS" >no forced user</I -></SPAN ></P ><P >Example: <B @@ -8618,17 +8529,19 @@ 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 <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbd</SPAN ->(8)</SPAN + is using that is reported by <A +HREF="smbd.8.html" +TARGET="_top" +><B +CLASS="COMMAND" +>smbd(8) + </B +></A > when a client queries the filesystem type for a share. The default type is <TT CLASS="CONSTANT" @@ -8658,7 +8571,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 @@ -8687,7 +8600,7 @@ CLASS="COMMAND" ><A NAME="GROUP" ></A ->>group (S)</DT +>group (S)</DT ><DD ><P >Synonym for <A @@ -8705,7 +8618,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 @@ -8743,13 +8656,10 @@ CLASS="COMMAND" many parts of the system require this value to be constant for correct operation.</P ><P ->Default: <SPAN -CLASS="emphasis" -><I +>Default: <I CLASS="EMPHASIS" >specified at compile time, usually "nobody"</I -></SPAN ></P ><P >Example: <B @@ -8761,7 +8671,7 @@ CLASS="COMMAND" ><A NAME="GUESTOK" ></A ->>guest ok (S)</DT +>guest ok (S)</DT ><DD ><P >If this parameter is <TT @@ -8779,18 +8689,6 @@ 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 @@ -8811,7 +8709,7 @@ CLASS="COMMAND" ><A NAME="GUESTONLY" ></A ->>guest only (S)</DT +>guest only (S)</DT ><DD ><P >If this parameter is <TT @@ -8849,7 +8747,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 @@ -8864,7 +8762,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 @@ -8913,12 +8811,9 @@ CLASS="PARAMETER" ></A >.</P ><P ->Default: <SPAN -CLASS="emphasis" -><I +>Default: <I CLASS="EMPHASIS" >no file are hidden</I -></SPAN ></P ><P >Example: <B @@ -8940,7 +8835,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 @@ -8955,7 +8850,7 @@ CLASS="COMMAND" ><A NAME="HIDEUNREADABLE" ></A ->>hide unreadable (G)</DT +>hide unreadable (G)</DT ><DD ><P >This parameter prevents clients from seeing the @@ -8970,7 +8865,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 @@ -8987,7 +8882,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 @@ -9004,7 +8899,7 @@ CLASS="COMMAND" ><A NAME="HOMEDIRMAP" ></A ->>homedir map (G)</DT +>homedir map (G)</DT ><DD ><P >If<A @@ -9019,12 +8914,13 @@ CLASS="PARAMETER" > is <TT CLASS="CONSTANT" >yes</TT ->, and <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbd</SPAN ->(8)</SPAN +>, and <A +HREF="smbd.8.html" +TARGET="_top" +><B +CLASS="COMMAND" +>smbd(8)</B +></A > is also acting as a Win95/98 <TT CLASS="PARAMETER" @@ -9046,12 +8942,9 @@ 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 @@ -9077,7 +8970,7 @@ CLASS="PARAMETER" ><P >Default: <B CLASS="COMMAND" ->homedir map = <empty string></B +>homedir map = <empty string></B ></P ><P >Example: <B @@ -9089,7 +8982,7 @@ CLASS="COMMAND" ><A NAME="HOSTMSDFS" ></A ->>host msdfs (G)</DT +>host msdfs (G)</DT ><DD ><P >This boolean parameter is only available @@ -9129,7 +9022,7 @@ CLASS="COMMAND" ><A NAME="HOSTNAMELOOKUPS" ></A ->>hostname lookups (G)</DT +>hostname lookups (G)</DT ><DD ><P >Specifies whether samba should use (expensive) @@ -9158,7 +9051,7 @@ CLASS="COMMAND" ><A NAME="HOSTSALLOW" ></A ->>hosts allow (S)</DT +>hosts allow (S)</DT ><DD ><P >A synonym for this parameter is <TT @@ -9203,12 +9096,9 @@ CLASS="PARAMETER" ><P >You can also specify hosts by network/netmask pairs and by netgroup names if your system supports netgroups. The - <SPAN -CLASS="emphasis" -><I + <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 @@ -9248,22 +9138,21 @@ CLASS="COMMAND" ><P >Note that access still requires suitable user-level passwords.</P ><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 +>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 ><P ->Default: <SPAN -CLASS="emphasis" -><I +>Default: <I CLASS="EMPHASIS" >none (i.e., all hosts permitted access) </I -></SPAN ></P ><P >Example: <B @@ -9276,7 +9165,7 @@ CLASS="COMMAND" ><A NAME="HOSTSDENY" ></A ->>hosts deny (S)</DT +>hosts deny (S)</DT ><DD ><P >The opposite of <TT @@ -9285,12 +9174,9 @@ CLASS="PARAMETER" >hosts allow</I ></TT > - - hosts listed here are <SPAN -CLASS="emphasis" -><I + - hosts listed here are <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 @@ -9301,13 +9187,10 @@ CLASS="PARAMETER" > list takes precedence.</P ><P ->Default: <SPAN -CLASS="emphasis" -><I +>Default: <I CLASS="EMPHASIS" >none (i.e., no hosts specifically excluded) </I -></SPAN ></P ><P >Example: <B @@ -9320,7 +9203,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, @@ -9345,12 +9228,9 @@ 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 @@ -9367,21 +9247,15 @@ 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 <SPAN -CLASS="emphasis" -><I + your spouse and kids. And only if you <I CLASS="EMPHASIS" >really</I -></SPAN > trust them :-).</P ><P ->Default: <SPAN -CLASS="emphasis" -><I +>Default: <I CLASS="EMPHASIS" >no host equivalences</I -></SPAN ></P ><P >Example: <B @@ -9393,7 +9267,7 @@ CLASS="COMMAND" ><A NAME="INCLUDE" ></A ->>include (G)</DT +>include (G)</DT ><DD ><P >This allows you to include one config file @@ -9419,12 +9293,9 @@ CLASS="PARAMETER" >. </P ><P ->Default: <SPAN -CLASS="emphasis" -><I +>Default: <I CLASS="EMPHASIS" >no file included</I -></SPAN ></P ><P >Example: <B @@ -9437,7 +9308,7 @@ CLASS="COMMAND" ><A NAME="INHERITACLS" ></A ->>inherit acls (S)</DT +>inherit acls (S)</DT ><DD ><P >This parameter can be used to ensure @@ -9459,7 +9330,7 @@ CLASS="COMMAND" ><A NAME="INHERITPERMISSIONS" ></A ->>inherit permissions (S)</DT +>inherit permissions (S)</DT ><DD ><P >The permissions on new files and directories @@ -9534,12 +9405,9 @@ CLASS="PARAMETER" </A > as usual.</P ><P ->Note that the setuid bit is <SPAN -CLASS="emphasis" -><I +>Note that the setuid bit is <I CLASS="EMPHASIS" >never</I -></SPAN > set via inheritance (the code explicitly prohibits this).</P ><P @@ -9592,7 +9460,7 @@ CLASS="COMMAND" ><A NAME="INTERFACES" ></A ->>interfaces (G)</DT +>interfaces (G)</DT ><DD ><P >This option allows you to override the default @@ -9659,29 +9527,23 @@ CLASS="PARAMETER" ></A >.</P ><P ->Default: <SPAN -CLASS="emphasis" -><I +>Default: <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 <SPAN -CLASS="emphasis" -><I + to login to this service. This is really a <I CLASS="EMPHASIS" >paranoid</I -></SPAN > check to absolutely ensure an improper setting does not breach your security.</P @@ -9692,20 +9554,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 @@ -9730,12 +9592,9 @@ CLASS="PARAMETER" ></A >.</P ><P ->Default: <SPAN -CLASS="emphasis" -><I +>Default: <I CLASS="EMPHASIS" >no invalid users</I -></SPAN ></P ><P >Example: <B @@ -9748,7 +9607,7 @@ CLASS="COMMAND" ><A NAME="KEEPALIVE" ></A ->>keepalive (G)</DT +>keepalive (G)</DT ><DD ><P >The value of the parameter (an integer) represents @@ -9788,7 +9647,7 @@ CLASS="COMMAND" ><A NAME="KERNELOPLOCKS" ></A ->>kernel oplocks (G)</DT +>kernel oplocks (G)</DT ><DD ><P >For UNIXes that support kernel based <A @@ -9810,21 +9669,20 @@ CLASS="PARAMETER" </I ></TT > to be broken whenever a local UNIX process or NFS operation - 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 + 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 CLASS="EMPHASIS" >very</I -></SPAN -> cool feature :-).</P +> + cool feature :-).</P ><P >This parameter defaults to <TT CLASS="CONSTANT" @@ -9862,19 +9720,18 @@ CLASS="COMMAND" ><A NAME="LANMANAUTH" ></A ->>lanman auth (G)</DT +>lanman auth (G)</DT ><DD ><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 +>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 ><P >Default : <B CLASS="COMMAND" @@ -9885,17 +9742,15 @@ CLASS="COMMAND" ><A NAME="LARGEREADWRITE" ></A ->>large readwrite (G)</DT +>large readwrite (G)</DT ><DD ><P ->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 +>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 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 @@ -9912,7 +9767,7 @@ CLASS="COMMAND" ><A NAME="LDAPADMINDN" ></A ->>ldap admin dn (G)</DT +>ldap admin dn (G)</DT ><DD ><P > The <TT @@ -9933,29 +9788,27 @@ CLASS="PARAMETER" CLASS="FILENAME" >private/secrets.tdb</TT > file. See the - <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbpasswd</SPAN ->(8)</SPAN -> man page for more information on how - to accmplish this. + <A +HREF="smbpasswd.8.html" +TARGET="_top" +><B +CLASS="COMMAND" +>smbpasswd(8)</B +></A +> man + page for more information on how to accmplish this. </P ><P ->Default : <SPAN -CLASS="emphasis" -><I +>Default : <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. @@ -9972,14 +9825,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 @@ -10023,7 +9876,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 @@ -10047,17 +9900,14 @@ 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 <SPAN -CLASS="emphasis" -><I + This is <I CLASS="EMPHASIS" >NOT</I -></SPAN > related to Samba's previous SSL support which was enabled by specifying the <B @@ -10139,7 +9989,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 @@ -10150,56 +10000,47 @@ CLASS="COMMAND" >ldap machine suffix</B >. It also used as the base dn for all ldap searches. </P ><P ->Default : <SPAN -CLASS="emphasis" -><I +>Default : <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 : <SPAN -CLASS="emphasis" -><I +>Default : <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 : <SPAN -CLASS="emphasis" -><I +>Default : <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 @@ -10257,7 +10098,7 @@ CLASS="COMMAND" ><A NAME="LDAPTRUSTIDS" ></A ->>ldap trust ids (G)</DT +>ldap trust ids (G)</DT ><DD ><P >Normally, Samba validates each entry @@ -10286,7 +10127,7 @@ CLASS="COMMAND" ><A NAME="LEVEL2OPLOCKS" ></A ->>level2 oplocks (S)</DT +>level2 oplocks (S)</DT ><DD ><P >This parameter controls whether Samba supports @@ -10370,15 +10211,16 @@ CLASS="COMMAND" ><A NAME="LMANNOUNCE" ></A ->>lm announce (G)</DT +>lm announce (G)</DT ><DD ><P ->This parameter determines if <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->nmbd</SPAN ->(8)</SPAN +>This parameter determines if <A +HREF="nmbd.8.html" +TARGET="_top" +> <B +CLASS="COMMAND" +>nmbd(8)</B +></A > 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 @@ -10449,7 +10291,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 @@ -10497,13 +10339,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="#AEN80" +HREF="#AEN79" >printers</A > section for more details.</P @@ -10517,15 +10359,16 @@ CLASS="COMMAND" ><A NAME="LOCALMASTER" ></A ->>local master (G)</DT +>local master (G)</DT ><DD ><P ->This option allows <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->nmbd</SPAN ->(8)</SPAN +>This option allows <A +HREF="nmbd.8.html" +TARGET="_top" +><B +CLASS="COMMAND" +> nmbd(8)</B +></A > to try and become a local master browser on a subnet. If set to <TT CLASS="CONSTANT" @@ -10542,22 +10385,16 @@ CLASS="CONSTANT" CLASS="CONSTANT" >yes</TT > doesn't - mean that Samba will <SPAN -CLASS="emphasis" -><I + mean that Samba will <I CLASS="EMPHASIS" >become</I -></SPAN > the local master browser on a subnet, just that <B CLASS="COMMAND" >nmbd</B -> will <SPAN -CLASS="emphasis" -><I +> will <I CLASS="EMPHASIS" > participate</I -></SPAN > in elections for local master browser.</P ><P >Setting this value to <TT @@ -10567,12 +10404,9 @@ CLASS="CONSTANT" CLASS="COMMAND" >nmbd</B > - <SPAN -CLASS="emphasis" -><I + <I CLASS="EMPHASIS" >never</I -></SPAN > to become a local master browser.</P ><P >Default: <B @@ -10584,7 +10418,7 @@ CLASS="COMMAND" ><A NAME="LOCKDIR" ></A ->>lock dir (G)</DT +>lock dir (G)</DT ><DD ><P >Synonym for <A @@ -10601,7 +10435,7 @@ CLASS="PARAMETER" ><A NAME="LOCKDIRECTORY" ></A ->>lock directory (G)</DT +>lock directory (G)</DT ><DD ><P >This option specifies the directory where lock @@ -10632,7 +10466,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 @@ -10655,7 +10489,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 @@ -10682,7 +10516,7 @@ CLASS="COMMAND" ><A NAME="LOCKING" ></A ->>locking (S)</DT +>locking (S)</DT ><DD ><P >This controls whether or not locking will be @@ -10702,19 +10536,13 @@ CLASS="COMMAND" >, real locking will be performed by the server.</P ><P ->This option <SPAN -CLASS="emphasis" -><I +>This option <I CLASS="EMPHASIS" >may</I -></SPAN > be useful for read-only - filesystems which <SPAN -CLASS="emphasis" -><I + filesystems which <I CLASS="EMPHASIS" >may</I -></SPAN > not need locking (such as CDROM drives), although setting this parameter of <TT CLASS="CONSTANT" @@ -10735,7 +10563,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 @@ -10754,7 +10582,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 @@ -10780,7 +10608,7 @@ CLASS="COMMAND" ><A NAME="LOGONDRIVE" ></A ->>logon drive (G)</DT +>logon drive (G)</DT ><DD ><P >This parameter specifies the local path to @@ -10812,7 +10640,7 @@ CLASS="COMMAND" ><A NAME="LOGONHOME" ></A ->>logon home (G)</DT +>logon home (G)</DT ><DD ><P >This parameter specifies the home directory @@ -10893,7 +10721,7 @@ CLASS="COMMAND" ><A NAME="LOGONPATH" ></A ->>logon path (G)</DT +>logon path (G)</DT ><DD ><P >This parameter specifies the home directory @@ -10939,12 +10767,9 @@ 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 <SPAN -CLASS="emphasis" -><I + achieve the desired effect (a <I CLASS="EMPHASIS" >MAN</I -></SPAN >datory profile). </P ><P @@ -10974,7 +10799,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 @@ -11034,12 +10859,9 @@ CLASS="COMMAND" >This option is only useful if Samba is set up as a logon server.</P ><P ->Default: <SPAN -CLASS="emphasis" -><I +>Default: <I CLASS="EMPHASIS" >no logon script defined</I -></SPAN ></P ><P >Example: <B @@ -11051,7 +10873,7 @@ CLASS="COMMAND" ><A NAME="LPPAUSECOMMAND" ></A ->>lppause command (S)</DT +>lppause command (S)</DT ><DD ><P >This parameter specifies the command to be @@ -11149,7 +10971,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 @@ -11214,7 +11036,7 @@ CLASS="COMMAND" ><A NAME="LPQCOMMAND" ></A ->>lpq command (S)</DT +>lpq command (S)</DT ><DD ><P >This parameter specifies the command to be @@ -11284,9 +11106,7 @@ CLASS="PARAMETER" ></A > parameter.</P ><P ->Default: <SPAN -CLASS="emphasis" -><I +>Default: <I CLASS="EMPHASIS" >depends on the setting of <TT CLASS="PARAMETER" @@ -11294,7 +11114,6 @@ CLASS="PARAMETER" > printing</I ></TT ></I -></SPAN ></P ><P >Example: <B @@ -11306,7 +11125,7 @@ CLASS="COMMAND" ><A NAME="LPRESUMECOMMAND" ></A ->>lpresume command (S)</DT +>lpresume command (S)</DT ><DD ><P >This parameter specifies the command to be @@ -11403,7 +11222,7 @@ CLASS="COMMAND" ><A NAME="LPRMCOMMAND" ></A ->>lprm command (S)</DT +>lprm command (S)</DT ><DD ><P >This parameter specifies the command to be @@ -11446,9 +11265,7 @@ CLASS="PARAMETER" ></A > parameter.</P ><P ->Default: <SPAN -CLASS="emphasis" -><I +>Default: <I CLASS="EMPHASIS" >depends on the setting of <TT CLASS="PARAMETER" @@ -11457,7 +11274,6 @@ CLASS="PARAMETER" </I ></TT ></I -></SPAN ></P ><P >Example 1: <B @@ -11476,7 +11292,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 @@ -11497,12 +11313,14 @@ 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 <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbpasswd</SPAN ->(8)</SPAN +>See also <A +HREF="smbpasswd.8.html" +TARGET="_top" +><B +CLASS="COMMAND" +>smbpasswd(8) + </B +></A >, and the <A HREF="#SECURITYEQUALSDOMAIN" > security = domain</A @@ -11517,7 +11335,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 @@ -11544,7 +11362,7 @@ CLASS="PARAMETER" ><P >Default: <B CLASS="COMMAND" ->magic output = <magic script name>.out +>magic output = <magic script name>.out </B ></P ><P @@ -11557,7 +11375,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, @@ -11583,36 +11401,24 @@ 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 - <SPAN -CLASS="emphasis" -><I + <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 <SPAN -CLASS="emphasis" -><I +>Magic scripts are <I CLASS="EMPHASIS" >EXPERIMENTAL</I -></SPAN > and - should <SPAN -CLASS="emphasis" -><I + should <I CLASS="EMPHASIS" >NOT</I -></SPAN > be relied upon.</P ><P ->Default: <SPAN -CLASS="emphasis" -><I +>Default: <I CLASS="EMPHASIS" >None. Magic scripts disabled.</I -></SPAN ></P ><P >Example: <B @@ -11624,11 +11430,11 @@ CLASS="COMMAND" ><A NAME="MANGLECASE" ></A ->>mangle case (S)</DT +>mangle case (S)</DT ><DD ><P >See the section on <A -HREF="#AEN206" +HREF="#AEN205" > NAME MANGLING</A ></P ><P @@ -11641,7 +11447,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 @@ -11679,12 +11485,9 @@ 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: <SPAN -CLASS="emphasis" -><I +>Default: <I CLASS="EMPHASIS" >no mangled map</I -></SPAN ></P ><P >Example: <B @@ -11696,7 +11499,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 @@ -11704,7 +11507,7 @@ NAME="MANGLEDNAMES" or whether non-DOS names should simply be ignored.</P ><P >See the section on <A -HREF="#AEN206" +HREF="#AEN205" > NAME MANGLING</A > for details on how to control the mangling process.</P ><P @@ -11781,7 +11584,7 @@ CLASS="COMMAND" ><A NAME="MANGLINGMETHOD" ></A ->>mangling method (G)</DT +>mangling method (G)</DT ><DD ><P > controls the algorithm used for the generating @@ -11807,7 +11610,7 @@ CLASS="COMMAND" ><A NAME="MANGLEPREFIX" ></A ->>mangle prefix (G)</DT +>mangle prefix (G)</DT ><DD ><P > controls the number of prefix @@ -11830,16 +11633,14 @@ 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 <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbd</SPAN ->(8)</SPAN + that should be cached in the Samba server <A +HREF="smbd.8.html" +TARGET="_top" +> smbd(8)</A >.</P ><P >This stack is a list of recently mangled base names @@ -11869,18 +11670,15 @@ CLASS="COMMAND" ><A NAME="MANGLINGCHAR" ></A ->>mangling char (S)</DT +>mangling char (S)</DT ><DD ><P >This controls what character is used as - the <SPAN -CLASS="emphasis" -><I + the <I CLASS="EMPHASIS" >magic</I -></SPAN > character in <A -HREF="#AEN206" +HREF="#AEN205" >name mangling</A >. The default is a '~' but this may interfere with some software. Use this option to set @@ -11900,7 +11698,7 @@ CLASS="COMMAND" ><A NAME="MAPARCHIVE" ></A ->>map archive (S)</DT +>map archive (S)</DT ><DD ><P >This controls whether the DOS archive attribute @@ -11936,7 +11734,7 @@ CLASS="COMMAND" ><A NAME="MAPHIDDEN" ></A ->>map hidden (S)</DT +>map hidden (S)</DT ><DD ><P >This controls whether DOS style hidden files @@ -11968,7 +11766,7 @@ CLASS="COMMAND" ><A NAME="MAPSYSTEM" ></A ->>map system (S)</DT +>map system (S)</DT ><DD ><P >This controls whether DOS style system files @@ -12000,7 +11798,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 @@ -12025,12 +11823,10 @@ CLASS="CONSTANT" >.</P ><P >This parameter can take three different values, which tell - <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbd</SPAN ->(8)</SPAN + <A +HREF="smbd.8.html" +TARGET="_top" +>smbd(8)</A > what to do with user login requests that don't match a valid UNIX user in some way.</P ><P @@ -12081,12 +11877,9 @@ 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 - <SPAN -CLASS="emphasis" -><I + <I CLASS="EMPHASIS" >hate</I -></SPAN > you if you set the <TT CLASS="PARAMETER" ><I @@ -12105,12 +11898,9 @@ CLASS="PARAMETER" ></TT > modes other than share. This is because in these modes the name of the resource being - requested is <SPAN -CLASS="emphasis" -><I + requested is <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 @@ -12136,7 +11926,7 @@ CLASS="COMMAND" ><A NAME="MAXCONNECTIONS" ></A ->>max connections (S)</DT +>max connections (S)</DT ><DD ><P >This option allows the number of simultaneous @@ -12176,7 +11966,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 @@ -12221,7 +12011,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 @@ -12248,7 +12038,7 @@ CLASS="COMMAND" ><A NAME="MAXMUX" ></A ->>max mux (G)</DT +>max mux (G)</DT ><DD ><P >This option controls the maximum number of @@ -12264,16 +12054,14 @@ 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 <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbd</SPAN ->(8)</SPAN + open files that one <A +HREF="smbd.8.html" +TARGET="_top" +>smbd(8)</A > 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 @@ -12292,17 +12080,18 @@ 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, <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbd</SPAN ->(8)</SPAN + If this number is exceeded, <A +HREF="smbd.8.html" +TARGET="_top" +><B +CLASS="COMMAND" +> smbd(8)</B +></A > will remote "Out of Space" to the client. See all <A HREF="#TOTALPRINTJOBS" @@ -12330,7 +12119,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 @@ -12361,12 +12150,9 @@ CLASS="CONSTANT" ><TT CLASS="CONSTANT" >LANMAN1</TT ->: First <SPAN -CLASS="emphasis" -><I +>: First <I CLASS="EMPHASIS" > modern</I -></SPAN > version of the protocol. Long filename support.</P ></LI @@ -12417,7 +12203,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 @@ -12433,12 +12219,10 @@ 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 <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbd</SPAN ->(8)</SPAN + conditions, each user will have an <A +HREF="smbd.8.html" +TARGET="_top" +>smbd</A > associated with him or her to handle connections to all shares from a given host. </P @@ -12457,15 +12241,13 @@ CLASS="COMMAND" ><A NAME="MAXTTL" ></A ->>max ttl (G)</DT +>max ttl (G)</DT ><DD ><P ->This option tells <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->nmbd</SPAN ->(8)</SPAN +>This option tells <A +HREF="nmbd.8.html" +TARGET="_top" +>nmbd(8)</A > what the default 'time to live' of NetBIOS names should be (in seconds) when <B @@ -12484,15 +12266,14 @@ CLASS="COMMAND" ><A NAME="MAXWINSTTL" ></A ->>max wins ttl (G)</DT +>max wins ttl (G)</DT ><DD ><P ->This option tells <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbd</SPAN ->(8)</SPAN +>This option tells <A +HREF="nmbd.8.html" +TARGET="_top" +>nmbd(8) + </A > when acting as a WINS server (<A HREF="#WINSSUPPORT" > <TT @@ -12529,7 +12310,7 @@ CLASS="COMMAND" ><A NAME="MAXXMIT" ></A ->>max xmit (G)</DT +>max xmit (G)</DT ><DD ><P >This option controls the maximum packet size @@ -12552,7 +12333,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 @@ -12566,7 +12347,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 @@ -12574,15 +12355,12 @@ CLASS="COMMAND" CLASS="COMMAND" >xedit</B >, then - removes it afterwards. <SPAN -CLASS="emphasis" -><I + removes it afterwards. <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 @@ -12646,7 +12424,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 @@ -12662,25 +12440,22 @@ CLASS="COMMAND" >message command = rm %s</B ></P ><P ->Default: <SPAN -CLASS="emphasis" -><I +>Default: <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 @@ -12697,7 +12472,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 @@ -12744,7 +12519,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 @@ -12777,7 +12552,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 @@ -12827,15 +12602,13 @@ CLASS="COMMAND" ><A NAME="MINWINSTTL" ></A ->>min wins ttl (G)</DT +>min wins ttl (G)</DT ><DD ><P ->This option tells <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->nmbd</SPAN ->(8)</SPAN +>This option tells <A +HREF="nmbd.8.html" +TARGET="_top" +>nmbd(8)</A > when acting as a WINS server (<A HREF="#WINSSUPPORT" @@ -12862,7 +12635,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 @@ -12895,14 +12668,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 @@ -12918,15 +12691,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.html" +HREF="msdfs_setup.html" TARGET="_top" ->"Hosting a Microsoft - Distributed File System tree on Samba"</A -> document.</P +>msdfs_setup.html + </A +>.</P ><P >See also <A HREF="#HOSTMSDFS" @@ -12948,7 +12721,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 @@ -12970,7 +12743,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 @@ -13075,7 +12848,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 @@ -13101,12 +12874,9 @@ CLASS="PARAMETER" ></A >.</P ><P ->Default: <SPAN -CLASS="emphasis" -><I +>Default: <I CLASS="EMPHASIS" >empty string (no additional names)</I -></SPAN ></P ><P >Example: <B @@ -13118,7 +12888,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 @@ -13139,12 +12909,9 @@ CLASS="PARAMETER" ></A >.</P ><P ->Default: <SPAN -CLASS="emphasis" -><I +>Default: <I CLASS="EMPHASIS" >machine DNS name</I -></SPAN ></P ><P >Example: <B @@ -13156,7 +12923,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 @@ -13167,7 +12934,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 @@ -13211,7 +12978,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 @@ -13229,7 +12996,7 @@ NAME="NONUNIXACCOUNTRANGE" ><P >Default: <B CLASS="COMMAND" ->non unix account range = <empty string> +>non unix account range = <empty string> </B ></P ><P @@ -13242,7 +13009,7 @@ CLASS="COMMAND" ><A NAME="NTACLSUPPORT" ></A ->>nt acl support (S)</DT +>nt acl support (S)</DT ><DD ><P >This boolean parameter controls whether @@ -13264,16 +13031,14 @@ CLASS="COMMAND" ><A NAME="NTPIPESUPPORT" ></A ->>nt pipe support (G)</DT +>nt pipe support (G)</DT ><DD ><P >This boolean parameter controls whether - <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbd</SPAN ->(8)</SPAN + <A +HREF="smbd.8.html" +TARGET="_top" +>smbd(8)</A > will allow Windows NT clients to connect to the NT SMB specific <TT CLASS="CONSTANT" @@ -13291,7 +13056,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 @@ -13319,18 +13084,16 @@ 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 <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbpasswd</SPAN ->(5)</SPAN +>See also <A +HREF="smbpasswd.5.html" +TARGET="_top" +>smbpasswd (5)</A >.</P ><P >Default: <B @@ -13342,7 +13105,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 @@ -13372,7 +13135,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 @@ -13432,7 +13195,7 @@ CLASS="COMMAND" ><A NAME="ONLYGUEST" ></A ->>only guest (S)</DT +>only guest (S)</DT ><DD ><P >A synonym for <A @@ -13449,7 +13212,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 @@ -13460,13 +13223,10 @@ 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 @@ -13478,15 +13238,12 @@ CLASS="COMMAND" ><A NAME="OPLOCKCONTENTIONLIMIT" ></A ->>oplock contention limit (S)</DT +>oplock contention limit (S)</DT ><DD ><P ->This is a <SPAN -CLASS="emphasis" -><I +>This is a <I CLASS="EMPHASIS" >very</I -></SPAN > advanced <A HREF="smbd.8.html" @@ -13496,27 +13253,23 @@ 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 <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 +>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 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 @@ -13528,7 +13281,7 @@ CLASS="COMMAND" ><A NAME="OPLOCKS" ></A ->>oplocks (S)</DT +>oplocks (S)</DT ><DD ><P >This boolean option tells <B @@ -13598,16 +13351,13 @@ CLASS="COMMAND" ><A NAME="NTLMAUTH" ></A ->>ntlm auth (G)</DT +>ntlm auth (G)</DT ><DD ><P ->This parameter determines - whether or not <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbd</SPAN ->(8)</SPAN +>This parameter determines whether or not <A +HREF="smbd.8.html" +TARGET="_top" +>smbd</A > will attempt to authenticate users using the NTLM password hash. If disabled, only the lanman password hashes will be used. @@ -13616,8 +13366,7 @@ CLASS="REFENTRYTITLE" >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 @@ -13629,17 +13378,15 @@ 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 <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->nmbd</SPAN ->(8)</SPAN + parameter determines whether <A +HREF="nmbd.8.html" +TARGET="_top" +>nmbd(8)</A > has a chance of becoming a local master browser for the <TT CLASS="PARAMETER" @@ -13648,12 +13395,9 @@ 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 @@ -13682,15 +13426,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 @@ -13701,16 +13445,21 @@ CLASS="COMMAND" ><P >The need for the file is due to the printer driver namespace problem described in the <A -HREF="printing.html" +HREF="printer_driver2.html" TARGET="_top" >Samba Printing HOWTO</A >. For more details on OS/2 clients, please - refer to the OS2-Client-HOWTO containing in the Samba documentation.</P + refer to the <A +HREF="OS2-Client-HOWTO.html" +TARGET="_top" +>OS2-Client-HOWTO + </A +> containing in the Samba documentation.</P ><P >Default: <B CLASS="COMMAND" ->os2 driver map = <empty string> +>os2 driver map = <empty string> </B ></P ></DD @@ -13718,7 +13467,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, @@ -13756,28 +13505,25 @@ 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 <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 + 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 ><P >Default: <B CLASS="COMMAND" ->panic action = <empty string></B +>panic action = <empty string></B ></P ><P >Example: <B @@ -13789,19 +13535,15 @@ 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 @@ -13811,7 +13553,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 @@ -14023,30 +13765,23 @@ CLASS="COMMAND" ><A NAME="PASSWDCHAT" ></A ->>passwd chat (G)</DT +>passwd chat (G)</DT ><DD ><P ->This string controls the <SPAN -CLASS="emphasis" -><I +>This string controls the <I CLASS="EMPHASIS" >"chat"</I -></SPAN > - conversation that takes places between <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbd</SPAN ->(8)</SPAN + conversation that takes places between <A +HREF="smbd.8.html" +TARGET="_top" +>smbd</A > and the local password changing program to change the user's password. The string describes a - sequence of response-receive pairs that <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbd</SPAN ->(8)</SPAN + sequence of response-receive pairs that <A +HREF="smbd.8.html" +TARGET="_top" +> smbd(8)</A > uses to determine what to send to the <A HREF="#PASSWDPROGRAM" @@ -14077,12 +13812,9 @@ CLASS="PARAMETER" CLASS="CONSTANT" >yes</TT >. This - sequence is then called <SPAN -CLASS="emphasis" -><I + sequence is then called <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 @@ -14103,16 +13835,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. @@ -14177,14 +13909,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 @@ -14192,24 +13924,19 @@ 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 <SPAN -CLASS="emphasis" -><I + parameter is run in <I CLASS="EMPHASIS" >debug</I -></SPAN > mode. In this mode the strings passed to and received from the passwd chat are printed - in the <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbd</SPAN ->(8)</SPAN + in the <A +HREF="smbd.8.html" +TARGET="_top" +>smbd(8)</A > log with a <A HREF="#DEBUGLEVEL" @@ -14287,7 +14014,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 @@ -14300,24 +14027,18 @@ 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 <SPAN -CLASS="emphasis" -><I +>Also note that many passwd programs insist in <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 @@ -14328,12 +14049,9 @@ CLASS="PARAMETER" CLASS="CONSTANT" >yes </TT -> then this program is called <SPAN -CLASS="emphasis" -><I +> then this program is called <I CLASS="EMPHASIS" >AS ROOT</I -></SPAN > before the SMB password in the <A HREF="smbpasswd.5.html" @@ -14353,19 +14071,13 @@ CLASS="PARAMETER" >unix password sync</I ></TT > parameter - is set this parameter <SPAN -CLASS="emphasis" -><I + is set this parameter <I CLASS="EMPHASIS" >MUST USE ABSOLUTE PATHS</I -></SPAN > - for <SPAN -CLASS="emphasis" -><I + for <I CLASS="EMPHASIS" >ALL</I -></SPAN > programs called, and must be examined for security implications. Note that by default <TT CLASS="PARAMETER" @@ -14404,7 +14116,7 @@ CLASS="COMMAND" ><A NAME="PASSWORDLEVEL" ></A ->>password level (G)</DT +>password level (G)</DT ><DD ><P >Some client/server combinations have difficulty @@ -14464,7 +14176,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 @@ -14504,21 +14216,15 @@ 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. <SPAN -CLASS="emphasis" -><I + password server. <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 @@ -14575,7 +14281,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 @@ -14653,7 +14359,7 @@ CLASS="PARAMETER" ><P >Default: <B CLASS="COMMAND" ->password server = <empty string></B +>password server = <empty string></B > </P ><P @@ -14672,7 +14378,7 @@ CLASS="COMMAND" ><A NAME="PATH" ></A ->>path (S)</DT +>path (S)</DT ><DD ><P >This parameter specifies a directory to which @@ -14713,12 +14419,9 @@ CLASS="PARAMETER" ></A > if one was specified.</P ><P ->Default: <SPAN -CLASS="emphasis" -><I +>Default: <I CLASS="EMPHASIS" >none</I -></SPAN ></P ><P >Example: <B @@ -14730,7 +14433,7 @@ CLASS="COMMAND" ><A NAME="PIDDIRECTORY" ></A ->>pid directory (G)</DT +>pid directory (G)</DT ><DD ><P >This option specifies the directory where pid @@ -14751,15 +14454,16 @@ CLASS="COMMAND" ><A NAME="POSIXLOCKING" ></A ->>posix locking (S)</DT +>posix locking (S)</DT ><DD ><P ->The <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbd</SPAN ->(8)</SPAN +>The <A +HREF="smbd.8.html" +TARGET="_top" +><B +CLASS="COMMAND" +>smbd(8)</B +></A > daemon maintains an database of file locks obtained by SMB clients. The default behavior is to map this internal database to POSIX @@ -14777,7 +14481,7 @@ CLASS="COMMAND" ><A NAME="POSTEXEC" ></A ->>postexec (S)</DT +>postexec (S)</DT ><DD ><P >This option specifies a command to be run @@ -14804,26 +14508,23 @@ CLASS="PARAMETER" </A >.</P ><P ->Default: <SPAN -CLASS="emphasis" -><I +>Default: <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 @@ -14846,7 +14547,7 @@ CLASS="COMMAND" ><A NAME="PREEXEC" ></A ->>preexec (S)</DT +>preexec (S)</DT ><DD ><P >This option specifies a command to be run whenever @@ -14859,7 +14560,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 @@ -14884,25 +14585,22 @@ CLASS="PARAMETER" ></A >.</P ><P ->Default: <SPAN -CLASS="emphasis" -><I +>Default: <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 @@ -14926,7 +14624,7 @@ CLASS="COMMAND" ><A NAME="PREFERREDMASTER" ></A ->>preferred master (G)</DT +>preferred master (G)</DT ><DD ><P >This boolean parameter controls if <A @@ -14988,7 +14686,7 @@ CLASS="COMMAND" ><A NAME="PREFEREDMASTER" ></A ->>prefered master (G)</DT +>prefered master (G)</DT ><DD ><P >Synonym for <A @@ -15005,7 +14703,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 @@ -15024,12 +14722,9 @@ CLASS="PARAMETER" ></A > option is easier.</P ><P ->Default: <SPAN -CLASS="emphasis" -><I +>Default: <I CLASS="EMPHASIS" >no preloaded services</I -></SPAN ></P ><P >Example: <B @@ -15041,7 +14736,7 @@ CLASS="COMMAND" ><A NAME="PRESERVECASE" ></A ->>preserve case (S)</DT +>preserve case (S)</DT ><DD ><P > This controls if new filenames are created @@ -15063,7 +14758,7 @@ CLASS="COMMAND" ></P ><P >See the section on <A -HREF="#AEN206" +HREF="#AEN205" >NAME MANGLING</A > for a fuller discussion.</P @@ -15072,7 +14767,7 @@ HREF="#AEN206" ><A NAME="PRINTCOMMAND" ></A ->>print command (S)</DT +>print command (S)</DT ><DD ><P >After a print job has finished spooling to @@ -15105,12 +14800,9 @@ CLASS="COMMAND" >%z - the size of the spooled print job (in bytes)</P ><P ->The print command <SPAN -CLASS="emphasis" -><I +>The print command <I CLASS="EMPHASIS" >MUST</I -></SPAN > contain at least one occurrence of <TT CLASS="PARAMETER" @@ -15168,7 +14860,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 @@ -15244,7 +14936,7 @@ CLASS="COMMAND" ><A NAME="PRINTOK" ></A ->>print ok (S)</DT +>print ok (S)</DT ><DD ><P >Synonym for <A @@ -15261,7 +14953,7 @@ CLASS="PARAMETER" ><A NAME="PRINTABLE" ></A ->>printable (S)</DT +>printable (S)</DT ><DD ><P >If this parameter is <TT @@ -15294,7 +14986,7 @@ CLASS="COMMAND" ><A NAME="PRINTCAP" ></A ->>printcap (G)</DT +>printcap (G)</DT ><DD ><P >Synonym for <A @@ -15311,7 +15003,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 @@ -15319,7 +15011,7 @@ NAME="PRINTCAPNAME" CLASS="FILENAME" > /etc/printcap</TT >). See the discussion of the <A -HREF="#AEN80" +HREF="#AEN79" >[printers]</A > section above for reasons why you might want to do this.</P @@ -15368,25 +15060,32 @@ 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 +> print1|My Printer 1 + print2|My Printer 2 + print3|My Printer 3 + print4|My Printer 4 + print5|My Printer 5 + </PRE +></TD +></TR +></TABLE ></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" @@ -15415,7 +15114,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 @@ -15425,7 +15124,7 @@ NAME="PRINTERADMIN" ><P >Default: <B CLASS="COMMAND" ->printer admin = <empty string></B +>printer admin = <empty string></B > </P ><P @@ -15438,20 +15137,17 @@ 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="printing.html" +HREF="printer_driver2.html" TARGET="_top" >Samba 2.2. Printing HOWTO</A @@ -15500,20 +15196,17 @@ 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="printing.html" +HREF="printer_driver2.html" TARGET="_top" >Samba 2.2. Printing HOWTO</A @@ -15561,12 +15254,9 @@ CLASS="PARAMETER" ></A >.</P ><P ->Default: <SPAN -CLASS="emphasis" -><I +>Default: <I CLASS="EMPHASIS" >None (set in compile).</I -></SPAN ></P ><P >Example: <B @@ -15579,20 +15269,17 @@ 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="printing.html" +HREF="printer_driver2.html" TARGET="_top" >Samba 2.2. Printing HOWTO</A @@ -15646,7 +15333,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 @@ -15656,16 +15343,13 @@ NAME="PRINTERNAME" name given will be used for any printable service that does not have its own printer name specified.</P ><P ->Default: <SPAN -CLASS="emphasis" -><I +>Default: <I CLASS="EMPHASIS" >none (but may be <TT CLASS="CONSTANT" >lp</TT > on many systems)</I -></SPAN ></P ><P >Example: <B @@ -15677,7 +15361,7 @@ CLASS="COMMAND" ><A NAME="PRINTER" ></A ->>printer (S)</DT +>printer (S)</DT ><DD ><P >Synonym for <A @@ -15694,7 +15378,7 @@ CLASS="PARAMETER" ><A NAME="PRINTING" ></A ->>printing (S)</DT +>printing (S)</DT ><DD ><P >This parameters controls how printer status @@ -15774,7 +15458,7 @@ TARGET="_top" >This option can be set on a per printer basis</P ><P >See also the discussion in the <A -HREF="#AEN80" +HREF="#AEN79" > [printers]</A > section.</P ></DD @@ -15782,7 +15466,7 @@ HREF="#AEN80" ><A NAME="PRIVATEDIR" ></A ->>private dir (G)</DT +>private dir (G)</DT ><DD ><P >This parameters defines the directory @@ -15805,7 +15489,7 @@ CLASS="COMMAND" ><A NAME="PROTOCOL" ></A ->>protocol (G)</DT +>protocol (G)</DT ><DD ><P >Synonym for <A @@ -15822,7 +15506,7 @@ CLASS="PARAMETER" ><A NAME="PUBLIC" ></A ->>public (S)</DT +>public (S)</DT ><DD ><P >Synonym for <A @@ -15840,7 +15524,7 @@ CLASS="PARAMETER" ><A NAME="QUEUEPAUSECOMMAND" ></A ->>queuepause command (S)</DT +>queuepause command (S)</DT ><DD ><P >This parameter specifies the command to be @@ -15867,9 +15551,7 @@ CLASS="PARAMETER" path in the command as the PATH may not be available to the server.</P ><P ->Default: <SPAN -CLASS="emphasis" -><I +>Default: <I CLASS="EMPHASIS" >depends on the setting of <TT CLASS="PARAMETER" @@ -15878,7 +15560,6 @@ CLASS="PARAMETER" </I ></TT ></I -></SPAN ></P ><P >Example: <B @@ -15890,7 +15571,7 @@ CLASS="COMMAND" ><A NAME="QUEUERESUMECOMMAND" ></A ->>queueresume command (S)</DT +>queueresume command (S)</DT ><DD ><P >This parameter specifies the command to be @@ -15927,9 +15608,7 @@ CLASS="PARAMETER" path in the command as the PATH may not be available to the server.</P ><P ->Default: <SPAN -CLASS="emphasis" -><I +>Default: <I CLASS="EMPHASIS" >depends on the setting of <A HREF="#PRINTING" @@ -15940,7 +15619,6 @@ CLASS="PARAMETER" ></TT ></A ></I -></SPAN > </P ><P @@ -15954,7 +15632,7 @@ CLASS="COMMAND" ><A NAME="READBMPX" ></A ->>read bmpx (G)</DT +>read bmpx (G)</DT ><DD ><P >This boolean parameter controls whether <A @@ -15978,7 +15656,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 @@ -16024,7 +15702,7 @@ CLASS="PARAMETER" ><P >Default: <B CLASS="COMMAND" ->read list = <empty string></B +>read list = <empty string></B ></P ><P >Example: <B @@ -16036,7 +15714,7 @@ CLASS="COMMAND" ><A NAME="READONLY" ></A ->>read only (S)</DT +>read only (S)</DT ><DD ><P >An inverted synonym is <A @@ -16060,12 +15738,9 @@ CLASS="CONSTANT" CLASS="COMMAND" >printable = yes</B >) - will <SPAN -CLASS="emphasis" -><I + will <I CLASS="EMPHASIS" >ALWAYS</I -></SPAN > allow writing to the directory (user privileges permitting), but only via spooling operations.</P ><P @@ -16078,7 +15753,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 @@ -16113,7 +15788,7 @@ CLASS="COMMAND" ><A NAME="READSIZE" ></A ->>read size (G)</DT +>read size (G)</DT ><DD ><P >The option <TT @@ -16154,7 +15829,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 @@ -16179,7 +15854,7 @@ CLASS="COMMAND" ><A NAME="REMOTEANNOUNCE" ></A ->>remote announce (G)</DT +>remote announce (G)</DT ><DD ><P >This option allows you to setup <A @@ -16223,10 +15898,9 @@ 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 <A -HREF="improved-browsing.html" -TARGET="_top" ->BROWSING</A +>See the documentation file <TT +CLASS="FILENAME" +>BROWSING.txt</TT > in the <TT CLASS="FILENAME" @@ -16235,7 +15909,7 @@ CLASS="FILENAME" ><P >Default: <B CLASS="COMMAND" ->remote announce = <empty string> +>remote announce = <empty string> </B ></P ></DD @@ -16243,7 +15917,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 @@ -16285,7 +15959,7 @@ CLASS="COMMAND" ><P >Default: <B CLASS="COMMAND" ->remote browse sync = <empty string> +>remote browse sync = <empty string> </B ></P ></DD @@ -16293,7 +15967,7 @@ CLASS="COMMAND" ><A NAME="RESTRICTANONYMOUS" ></A ->>restrict anonymous (G)</DT +>restrict anonymous (G)</DT ><DD ><P >This is a integer parameter, and @@ -16313,7 +15987,7 @@ CLASS="COMMAND" ><A NAME="ROOT" ></A ->>root (G)</DT +>root (G)</DT ><DD ><P >Synonym for <A @@ -16330,7 +16004,7 @@ CLASS="PARAMETER" ><A NAME="ROOTDIR" ></A ->>root dir (G)</DT +>root dir (G)</DT ><DD ><P >Synonym for <A @@ -16347,7 +16021,7 @@ CLASS="PARAMETER" ><A NAME="ROOTDIRECTORY" ></A ->>root directory (G)</DT +>root directory (G)</DT ><DD ><P >The server will <B @@ -16384,12 +16058,9 @@ CLASS="PARAMETER" >root directory</I ></TT > - option, <SPAN -CLASS="emphasis" -><I + option, <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 @@ -16421,7 +16092,7 @@ CLASS="COMMAND" ><A NAME="ROOTPOSTEXEC" ></A ->>root postexec (S)</DT +>root postexec (S)</DT ><DD ><P >This is the same as the <TT @@ -16446,7 +16117,7 @@ CLASS="PARAMETER" ><P >Default: <B CLASS="COMMAND" ->root postexec = <empty string> +>root postexec = <empty string> </B ></P ></DD @@ -16454,7 +16125,7 @@ CLASS="COMMAND" ><A NAME="ROOTPREEXEC" ></A ->>root preexec (S)</DT +>root preexec (S)</DT ><DD ><P >This is the same as the <TT @@ -16487,7 +16158,7 @@ CLASS="PARAMETER" ><P >Default: <B CLASS="COMMAND" ->root preexec = <empty string> +>root preexec = <empty string> </B ></P ></DD @@ -16495,7 +16166,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 @@ -16533,7 +16204,7 @@ CLASS="COMMAND" ><A NAME="SECURITY" ></A ->>security (G)</DT +>security (G)</DT ><DD ><P >This option affects how clients respond to @@ -16543,12 +16214,11 @@ CLASS="FILENAME" > file.</P ><P >The option sets the "security mode bit" in replies to - protocol negotiations with <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbd</SPAN ->(8)</SPAN + protocol negotiations with <A +HREF="smbd.8.html" +TARGET="_top" +>smbd(8) + </A > 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 @@ -16623,12 +16293,9 @@ CLASS="PARAMETER" >It is possible to use <B CLASS="COMMAND" >smbd</B -> in a <SPAN -CLASS="emphasis" -><I +> in a <I CLASS="EMPHASIS" > hybrid mode</I -></SPAN > where it is offers both user and share level security under different <A HREF="#NETBIOSALIASES" @@ -16645,13 +16312,10 @@ 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 @@ -16669,12 +16333,9 @@ CLASS="COMMAND" >Note that <B CLASS="COMMAND" >smbd</B -> <SPAN -CLASS="emphasis" -><I +> <I CLASS="EMPHASIS" >ALWAYS</I -></SPAN > uses a valid UNIX user to act on behalf of the client, even in <B @@ -16734,13 +16395,10 @@ CLASS="PARAMETER" ></LI ><LI ><P ->If the client did a previous <SPAN -CLASS="emphasis" -><I +>If the client did a previous <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 @@ -16795,34 +16453,28 @@ CLASS="PARAMETER" >, then this guest user will be used, otherwise access is denied.</P ><P ->Note that it can be <SPAN -CLASS="emphasis" -><I +>Note that it can be <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="#AEN239" +HREF="#AEN238" > 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 3.0. +>This is the default security setting in Samba 2.2. 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" @@ -16862,19 +16514,13 @@ 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 <SPAN -CLASS="emphasis" -><I + requested is <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 @@ -16899,87 +16545,62 @@ CLASS="PARAMETER" > parameter for details on doing this.</P ><P >See also the section <A -HREF="#AEN239" +HREF="#AEN238" > NOTE ABOUT USERNAME/PASSWORD VALIDATION</A >.</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 <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 -></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 +>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 ><P -><SPAN -CLASS="emphasis" ><I CLASS="EMPHASIS" >Note</I -></SPAN -> that from the client's point - of view <B +> 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 <SPAN -CLASS="emphasis" -><I + requested is <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 @@ -17004,7 +16625,7 @@ CLASS="PARAMETER" > parameter for details on doing this.</P ><P >See also the section <A -HREF="#AEN239" +HREF="#AEN238" > NOTE ABOUT USERNAME/PASSWORD VALIDATION</A >.</P ><P @@ -17029,24 +16650,20 @@ CLASS="PARAMETER" > parameter.</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 ->. It expects the <A +>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 HREF="#ENCRYPTPASSWORDS" ><TT CLASS="PARAMETER" @@ -17055,76 +16672,42 @@ CLASS="PARAMETER" ></TT > </A -> parameter to be set to - <TT +> parameter to be set to <TT CLASS="CONSTANT" >yes</TT ->, 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 +>. 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 -></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" +> 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 ><I CLASS="EMPHASIS" >Note</I -></SPAN -> that from the client's point of - view <B +> 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 <SPAN -CLASS="emphasis" -><I + requested is <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 @@ -17148,8 +16731,22 @@ 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="#AEN239" +HREF="#AEN238" > NOTE ABOUT USERNAME/PASSWORD VALIDATION</A >.</P ><P @@ -17187,7 +16784,7 @@ CLASS="COMMAND" ><A NAME="SECURITYMASK" ></A ->>security mask (S)</DT +>security mask (S)</DT ><DD ><P >This parameter controls what UNIX permission @@ -17205,12 +16802,9 @@ 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 @@ -17262,7 +16856,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 @@ -17307,7 +16901,7 @@ CLASS="COMMAND" ><A NAME="SETDIRECTORY" ></A ->>set directory (S)</DT +>set directory (S)</DT ><DD ><P >If <B @@ -17333,7 +16927,7 @@ CLASS="COMMAND" ><A NAME="SHAREMODES" ></A ->>share modes (S)</DT +>share modes (S)</DT ><DD ><P >This enables or disables the honoring of @@ -17377,12 +16971,9 @@ CLASS="CONSTANT" >This option gives full share compatibility and enabled by default.</P ><P ->You should <SPAN -CLASS="emphasis" -><I +>You should <I CLASS="EMPHASIS" >NEVER</I -></SPAN > turn this parameter off as many Windows applications will break if you do so.</P ><P @@ -17395,7 +16986,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 @@ -17421,7 +17012,7 @@ CLASS="COMMAND" names are lowered. </P ><P >See the section on <A -HREF="#AEN206" +HREF="#AEN205" > NAME MANGLING</A >.</P ><P @@ -17434,7 +17025,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 @@ -17465,12 +17056,9 @@ CLASS="PARAMETER" ></TT > parameter will always cause the OpenPrinterEx() on the server - to fail. Thus the APW icon will never be displayed. <SPAN -CLASS="emphasis" -><I + to fail. Thus the APW icon will never be displayed. <I CLASS="EMPHASIS" > Note :</I -></SPAN >This does not prevent the same user from having administrative privilege on an individual printer.</P ><P @@ -17510,15 +17098,12 @@ 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 @@ -17559,12 +17144,9 @@ CLASS="PARAMETER" >%r</I ></TT > will be substituted with the - switch <SPAN -CLASS="emphasis" -><I + switch <I CLASS="EMPHASIS" >-r</I -></SPAN >. It means reboot after shutdown for NT. </P @@ -17575,21 +17157,15 @@ CLASS="PARAMETER" >%f</I ></TT > will be substituted with the - switch <SPAN -CLASS="emphasis" -><I + switch <I CLASS="EMPHASIS" >-f</I -></SPAN >. It means force the shutdown even if applications do not respond for NT.</P ><P ->Default: <SPAN -CLASS="emphasis" -><I +>Default: <I CLASS="EMPHASIS" >None</I -></SPAN >.</P ><P >Example: <B @@ -17598,15 +17174,25 @@ CLASS="COMMAND" ></P ><P >Shutdown script example: -<PRE + <TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="90%" +><TR +><TD +><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 + /sbin/shutdown $3 $4 +$time $1 & + </PRE +></TD +></TR +></TABLE > Shutdown does not return so we need to launch it in background. </P @@ -17625,7 +17211,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 @@ -17648,7 +17234,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 @@ -17664,7 +17250,7 @@ CLASS="COMMAND" ><A NAME="SOCKETADDRESS" ></A ->>socket address (G)</DT +>socket address (G)</DT ><DD ><P >This option allows you to control what @@ -17685,7 +17271,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 @@ -17766,12 +17352,9 @@ TARGET="_top" ></LI ></UL ><P ->Those marked with a <SPAN -CLASS="emphasis" -><I +>Those marked with a <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 @@ -17819,7 +17402,7 @@ CLASS="COMMAND" ><A NAME="SOURCEENVIRONMENT" ></A ->>source environment (G)</DT +>source environment (G)</DT ><DD ><P >This parameter causes Samba to set environment @@ -17843,12 +17426,9 @@ CLASS="COMMAND" >SAMBA_NETBIOS_NAME = myhostname</B ></P ><P ->Default: <SPAN -CLASS="emphasis" -><I +>Default: <I CLASS="EMPHASIS" >No default value</I -></SPAN ></P ><P >Examples: <B @@ -17867,37 +17447,27 @@ 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. - Unless further issues are discovered with our SPNEGO - implementation, there is no reason this should ever be - disabled.</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 ><P ->Default: <SPAN -CLASS="emphasis" -><I +>Default: <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 <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbd</SPAN ->(8)</SPAN +>This parameter determines if <A +HREF="smbd.8.html" +TARGET="_top" +>smbd(8)</A > will use a cache in order to speed up case insensitive name mappings. You should never need to change this parameter.</P @@ -17911,7 +17481,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 @@ -17932,7 +17502,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 @@ -17969,7 +17539,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 @@ -18002,7 +17572,7 @@ CLASS="COMMAND" ><A NAME="STRICTSYNC" ></A ->>strict sync (S)</DT +>strict sync (S)</DT ><DD ><P >Many Windows applications (including the Windows @@ -18015,12 +17585,10 @@ NAME="STRICTSYNC" CLASS="CONSTANT" >no</TT > (the - default) means that <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbd</SPAN ->(8)</SPAN + default) means that <A +HREF="smbd.8.html" +TARGET="_top" +>smbd</A > 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 @@ -18048,7 +17616,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 @@ -18064,7 +17632,7 @@ CLASS="COMMAND" ><A NAME="SYNCALWAYS" ></A ->>sync always (S)</DT +>sync always (S)</DT ><DD ><P >This is a boolean parameter that controls @@ -18115,7 +17683,7 @@ CLASS="COMMAND" ><A NAME="SYSLOG" ></A ->>syslog (G)</DT +>syslog (G)</DT ><DD ><P >This parameter maps how Samba debug messages @@ -18150,7 +17718,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 @@ -18166,7 +17734,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 @@ -18200,16 +17768,14 @@ 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 <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->winbindd</SPAN ->(8)</SPAN + user, the <A +HREF="winbindd.8.html" +TARGET="_top" +>winbindd(8)</A > daemon uses this parameter to fill in the login shell for that user.</P ><P @@ -18222,7 +17788,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 @@ -18244,15 +17810,14 @@ CLASS="COMMAND" ><A NAME="TIMESERVER" ></A ->>time server (G)</DT +>time server (G)</DT ><DD ><P ->This parameter determines if <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->nmbd</SPAN ->(8)</SPAN +>This parameter determines if <A +HREF="nmbd.8.html" +TARGET="_top" +> + nmbd(8)</A > advertises itself as a time server to Windows clients.</P ><P @@ -18265,7 +17830,7 @@ CLASS="COMMAND" ><A NAME="TIMESTAMPLOGS" ></A ->>timestamp logs (G)</DT +>timestamp logs (G)</DT ><DD ><P >Synonym for <A @@ -18282,18 +17847,16 @@ 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 <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbd</SPAN ->(8)</SPAN + by a client which will exceed this number, then <A +HREF="smbd.8.html" +TARGET="_top" +>smbd</A > 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 @@ -18324,7 +17887,7 @@ CLASS="COMMAND" ><A NAME="UNICODE" ></A ->>unicode (G)</DT +>unicode (G)</DT ><DD ><P >Specifies whether Samba should try @@ -18341,7 +17904,7 @@ CLASS="COMMAND" ><A NAME="UNIXCHARSET" ></A ->>unix charset (G)</DT +>unix charset (G)</DT ><DD ><P >Specifies the charset the unix machine @@ -18351,19 +17914,19 @@ NAME="UNIXCHARSET" ><P >Default: <B CLASS="COMMAND" ->unix charset = UTF8</B +>unix charset = ASCII</B ></P ><P >Example: <B CLASS="COMMAND" ->unix charset = ASCII</B +>unix charset = UTF8</B ></P ></DD ><DT ><A NAME="UNIXEXTENSIONS" ></A ->>unix extensions(G)</DT +>unix extensions(G)</DT ><DD ><P >This boolean parameter controls whether Samba @@ -18382,7 +17945,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 @@ -18397,12 +17960,9 @@ CLASS="PARAMETER" >passwd program</I ></TT ->parameter is called <SPAN -CLASS="emphasis" -><I +>parameter is called <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 @@ -18436,7 +17996,7 @@ CLASS="COMMAND" ><A NAME="UPDATEENCRYPTED" ></A ->>update encrypted (G)</DT +>update encrypted (G)</DT ><DD ><P >This boolean parameter allows a user logging @@ -18491,7 +18051,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 @@ -18520,14 +18080,11 @@ 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. <SPAN -CLASS="emphasis" -><I + call to succeed. <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 @@ -18545,7 +18102,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 @@ -18569,7 +18126,7 @@ CLASS="COMMAND" ><A NAME="USERHOSTS" ></A ->>use rhosts (G)</DT +>use rhosts (G)</DT ><DD ><P >If this global parameter is <TT @@ -18583,12 +18140,9 @@ 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 @@ -18614,7 +18168,7 @@ CLASS="COMMAND" ><A NAME="USER" ></A ->>user (S)</DT +>user (S)</DT ><DD ><P >Synonym for <A @@ -18631,7 +18185,7 @@ CLASS="PARAMETER" ><A NAME="USERS" ></A ->>users (S)</DT +>users (S)</DT ><DD ><P >Synonym for <A @@ -18648,7 +18202,7 @@ CLASS="PARAMETER" ><A NAME="USERNAME" ></A ->>username (S)</DT +>username (S)</DT ><DD ><P >Multiple users may be specified in a comma-delimited @@ -18714,7 +18268,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 @@ -18724,7 +18278,7 @@ CLASS="PARAMETER" search.</P ><P >See the section <A -HREF="#AEN239" +HREF="#AEN238" >NOTE ABOUT USERNAME/PASSWORD VALIDATION</A > for more information on how @@ -18733,7 +18287,7 @@ HREF="#AEN239" >Default: <B CLASS="COMMAND" >The guest account if a guest service, - else <empty string>.</B + else <empty string>.</B ></P ><P >Examples:<B @@ -18746,7 +18300,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 @@ -18780,7 +18334,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 @@ -18870,10 +18424,20 @@ 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 +> !sys = mary fred + guest = * + </PRE +></TD +></TR +></TABLE ></P ><P >Note that the remapping is applied to all occurrences @@ -18910,12 +18474,9 @@ CLASS="PARAMETER" trouble deleting print jobs as PrintManager under WfWg will think they don't own the print job.</P ><P ->Default: <SPAN -CLASS="emphasis" -><I +>Default: <I CLASS="EMPHASIS" >no username map</I -></SPAN ></P ><P >Example: <B @@ -18928,7 +18489,7 @@ CLASS="COMMAND" ><A NAME="USESENDFILE" ></A ->>use sendfile (S)</DT +>use sendfile (S)</DT ><DD ><P >If this parameter is <TT @@ -18952,7 +18513,7 @@ CLASS="COMMAND" ><A NAME="UTMP" ></A ->>utmp (G)</DT +>utmp (G)</DT ><DD ><P >This boolean parameter is only available if @@ -18992,7 +18553,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 @@ -19017,12 +18578,9 @@ CLASS="FILENAME" >/var/run/utmp</TT > on Linux).</P ><P ->Default: <SPAN -CLASS="emphasis" -><I +>Default: <I CLASS="EMPHASIS" >no utmp directory</I -></SPAN ></P ><P >Example: <B @@ -19034,7 +18592,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 @@ -19063,12 +18621,9 @@ CLASS="FILENAME" >/var/run/wtmp</TT > on Linux).</P ><P ->Default: <SPAN -CLASS="emphasis" -><I +>Default: <I CLASS="EMPHASIS" >no wtmp directory</I -></SPAN ></P ><P >Example: <B @@ -19080,11 +18635,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" @@ -19121,13 +18676,10 @@ CLASS="PARAMETER" ></A ></P ><P ->Default: <SPAN -CLASS="emphasis" -><I +>Default: <I CLASS="EMPHASIS" >No valid users list (anyone can login) </I -></SPAN ></P ><P >Example: <B @@ -19139,7 +18691,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 @@ -19149,12 +18701,9 @@ NAME="VETOFILES" or directories as in DOS wildcards.</P ><P >Each entry must be a unix path, not a DOS path and - must <SPAN -CLASS="emphasis" -><I + must <I CLASS="EMPHASIS" >not</I -></SPAN > include the unix directory separator '/'.</P ><P @@ -19170,12 +18719,9 @@ 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 <SPAN -CLASS="emphasis" -><I + deletion will <I CLASS="EMPHASIS" >fail</I -></SPAN > unless you also set the <TT CLASS="PARAMETER" @@ -19213,16 +18759,19 @@ CLASS="PARAMETER" ></A >.</P ><P ->Default: <SPAN -CLASS="emphasis" -><I +>Default: <I CLASS="EMPHASIS" >No files or directories are vetoed. </I -></SPAN ></P ><P ->Examples:<PRE +>Examples:<TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="90%" +><TR +><TD +><PRE CLASS="PROGRAMLISTING" >; Veto any files containing the word Security, ; any ending in .tmp, and any directory containing the @@ -19232,13 +18781,16 @@ 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 @@ -19264,13 +18816,10 @@ CLASS="PARAMETER" > parameter.</P ><P ->Default: <SPAN -CLASS="emphasis" -><I +>Default: <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 @@ -19294,7 +18843,7 @@ CLASS="COMMAND" ><A NAME="VFSPATH" ></A ->>vfs path (S)</DT +>vfs path (S)</DT ><DD ><P >This parameter specifies the directory @@ -19319,7 +18868,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 @@ -19327,19 +18876,16 @@ NAME="VFSOBJECT" disk I/O operations are used but these can be overloaded with one or more VFS objects. </P ><P ->Default : <SPAN -CLASS="emphasis" -><I +>Default : <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 @@ -19354,38 +18900,32 @@ CLASS="PARAMETER" ></A >.</P ><P ->Default : <SPAN -CLASS="emphasis" -><I +>Default : <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: <SPAN -CLASS="emphasis" -><I +>Default: <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 @@ -19407,16 +18947,14 @@ 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 <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->winbindd</SPAN ->(8)</SPAN +>This parameter specifies the number of seconds the + <A +HREF="winbindd.8.html" +TARGET="_top" +>winbindd(8)</A > daemon will cache user and group information before querying a Windows NT server again.</P @@ -19430,19 +18968,19 @@ CLASS="COMMAND" ><A NAME="WINBINDENUMUSERS" ></A ->>winbind enum users (G)</DT +>winbind enum users (G)</DT ><DD ><P ->On large installations using <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->winbindd</SPAN ->(8)</SPAN +>On large installations using + <A +HREF="winbindd.8.html" +TARGET="_top" +>winbindd(8)</A > 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" @@ -19467,12 +19005,9 @@ 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 @@ -19488,19 +19023,19 @@ CLASS="COMMAND" ><A NAME="WINBINDENUMGROUPS" ></A ->>winbind enum groups (G)</DT +>winbind enum groups (G)</DT ><DD ><P ->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 +>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 CLASS="COMMAND" ->setgrent()</B +> setgrent()</B >, <B CLASS="COMMAND" @@ -19525,12 +19060,9 @@ 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 @@ -19545,23 +19077,21 @@ 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 <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->winbindd</SPAN ->(8)</SPAN + ids that are allocated by the <A +HREF="winbindd.8.html" +TARGET="_top" +> winbindd(8)</A > 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 @@ -19574,7 +19104,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 @@ -19618,23 +19148,21 @@ 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 <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->winbindd</SPAN ->(8)</SPAN + ids that are allocated by the <A +HREF="winbindd.8.html" +TARGET="_top" +> winbindd(8)</A > 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 @@ -19644,27 +19172,25 @@ CLASS="COMMAND" ></P ></DD ><DT -><A +>winbind use default domain, <A NAME="WINBINDUSEDEFAULTDOMAIN" ></A ->>winbind use default domain (G)</DT +>winbind use default domain (G)</DT ><DD ><P ->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. +>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. 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 @@ -19677,7 +19203,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 @@ -19742,7 +19268,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 @@ -19765,45 +19291,36 @@ 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 <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->nmbd</SPAN ->(8)</SPAN + address for preference) of the WINS server that <A +HREF="nmbd.8.html" +TARGET="_top" +> nmbd(8)</A > 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 <A -HREF="improved-browsing.html" -TARGET="_top" ->BROWSING</A +>See the documentation file <TT +CLASS="FILENAME" +>BROWSING.txt</TT > in the docs/ directory of your Samba source distribution.</P ><P ->Default: <SPAN -CLASS="emphasis" -><I +>Default: <I CLASS="EMPHASIS" >not enabled</I -></SPAN ></P ><P >Example: <B @@ -19815,15 +19332,14 @@ CLASS="COMMAND" ><A NAME="WINSSUPPORT" ></A ->>wins support (G)</DT +>wins support (G)</DT ><DD ><P ->This boolean controls if the <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->nmbd</SPAN ->(8)</SPAN +>This boolean controls if the <A +HREF="nmbd.8.html" +TARGET="_top" +> + nmbd(8)</A > process in Samba will act as a WINS server. You should not set this to <TT CLASS="CONSTANT" @@ -19833,12 +19349,9 @@ CLASS="CONSTANT" CLASS="COMMAND" >nmbd</B > to be your WINS server. - Note that you should <SPAN -CLASS="emphasis" -><I + Note that you should <I CLASS="EMPHASIS" >NEVER</I -></SPAN > set this to <TT CLASS="CONSTANT" >yes</TT @@ -19854,7 +19367,7 @@ CLASS="COMMAND" ><A NAME="WORKGROUP" ></A ->>workgroup (G)</DT +>workgroup (G)</DT ><DD ><P >This controls what workgroup your server will @@ -19868,12 +19381,9 @@ CLASS="COMMAND" > setting.</P ><P ->Default: <SPAN -CLASS="emphasis" -><I +>Default: <I CLASS="EMPHASIS" >set at compile time to WORKGROUP</I -></SPAN ></P ><P >Example: <B @@ -19885,7 +19395,7 @@ CLASS="COMMAND" ><A NAME="WRITABLE" ></A ->>writable (S)</DT +>writable (S)</DT ><DD ><P >Synonym for <A @@ -19902,17 +19412,14 @@ 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 <SPAN -CLASS="emphasis" -><I + (it does <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. @@ -19946,7 +19453,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 @@ -19979,7 +19486,7 @@ CLASS="PARAMETER" ><P >Default: <B CLASS="COMMAND" ->write list = <empty string> +>write list = <empty string> </B ></P ><P @@ -19993,7 +19500,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 @@ -20017,7 +19524,7 @@ CLASS="COMMAND" ><A NAME="WRITEOK" ></A ->>write ok (S)</DT +>write ok (S)</DT ><DD ><P >Inverted synonym for <A @@ -20034,7 +19541,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 @@ -20050,7 +19557,7 @@ CLASS="COMMAND" ><A NAME="WRITEABLE" ></A ->>writeable (S)</DT +>writeable (S)</DT ><DD ><P >Inverted synonym for <A @@ -20069,7 +19576,7 @@ CLASS="PARAMETER" ><DIV CLASS="REFSECT1" ><A -NAME="AEN6323" +NAME="AEN6195" ></A ><H2 >WARNINGS</H2 @@ -20080,12 +19587,11 @@ NAME="AEN6323" problem - but be aware of the possibility.</P ><P >On a similar note, many clients - especially DOS clients - - limit service names to eight characters. <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbd</SPAN ->(8)</SPAN + limit service names to eight characters. <A +HREF="smbd.8.html" +TARGET="_top" +>smbd(8) + </A > 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 @@ -20100,81 +19606,97 @@ CLASS="REFENTRYTITLE" ><DIV CLASS="REFSECT1" ><A -NAME="AEN6331" +NAME="AEN6201" ></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="AEN6334" +NAME="AEN6204" ></A ><H2 >SEE ALSO</H2 ><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 +><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 ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN6364" +NAME="AEN6224" ></A ><H2 >AUTHOR</H2 @@ -20186,14 +19708,14 @@ NAME="AEN6364" ><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. The conversion to DocBook XML 4.2 - for Samba 3.0 was done by Alexander Bokovoy.</P + Samba 2.2 was done by Gerald Carter</P ></DIV ></BODY ></HTML diff --git a/docs/htmldocs/smbcacls.1.html b/docs/htmldocs/smbcacls.1.html index 66dbf8d2f9..e0425d481d 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.1" +NAME="SMBCACLS" ></A >smbcacls</H1 ><DIV @@ -47,12 +47,10 @@ NAME="AEN22" ><H2 >DESCRIPTION</H2 ><P ->This tool is part of the <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->Samba</SPAN ->(7)</SPAN +>This tool is part of the <A +HREF="samba.7.html" +TARGET="_top" +> Samba</A > suite.</P ><P >The <B @@ -64,7 +62,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN30" +NAME="AEN28" ></A ><H2 >OPTIONS</H2 @@ -119,12 +117,9 @@ 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 <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smb.conf</SPAN ->(5)</SPAN + workgroup specified in the <TT +CLASS="FILENAME" +>smb.conf</TT > file is used, or "username%password" or "DOMAIN\username%password" and the password and workgroup names are used as provided. </P @@ -187,7 +182,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN79" +NAME="AEN75" ></A ><H2 >ACL FORMAT</H2 @@ -201,7 +196,8 @@ 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 @@ -215,45 +211,34 @@ ACL:<sid or name>:<type>/<flags>/<mask></PRE 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 -><TT -CLASS="CONSTANT" ->#define SEC_ACE_FLAG_OBJECT_INHERIT 0x1</TT -></P +>#define SEC_ACE_FLAG_OBJECT_INHERIT 0x1</P ></LI ><LI ><P -><TT -CLASS="CONSTANT" ->#define SEC_ACE_FLAG_CONTAINER_INHERIT 0x2</TT -></P +>#define SEC_ACE_FLAG_CONTAINER_INHERIT 0x2</P ></LI ><LI ><P -><TT -CLASS="CONSTANT" ->#define SEC_ACE_FLAG_NO_PROPAGATE_INHERIT 0x4</TT -></P +>#define SEC_ACE_FLAG_NO_PROPAGATE_INHERIT 0x4 + </P ></LI ><LI ><P -><TT -CLASS="CONSTANT" ->#define SEC_ACE_FLAG_INHERIT_ONLY 0x8</TT -></P +>#define SEC_ACE_FLAG_INHERIT_ONLY 0x8</P ></LI ></UL ><P @@ -371,7 +356,7 @@ CLASS="EMPHASIS" ><DIV CLASS="REFSECT1" ><A -NAME="AEN133" +NAME="AEN125" ></A ><H2 >EXIT STATUS</H2 @@ -395,17 +380,18 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN139" +NAME="AEN131" ></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="AEN142" +NAME="AEN134" ></A ><H2 >AUTHOR</H2 @@ -422,8 +408,7 @@ CLASS="COMMAND" and Tim Potter.</P ><P >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 + by Gerald Carter</P ></DIV ></BODY ></HTML diff --git a/docs/htmldocs/smbclient.1.html b/docs/htmldocs/smbclient.1.html index 8ae4f84fe3..ca8cafd312 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.1" +NAME="SMBCLIENT" ></A >smbclient</H1 ><DIV @@ -38,22 +38,20 @@ 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] [-k]</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]</P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN34" +NAME="AEN33" ></A ><H2 >DESCRIPTION</H2 ><P ->This tool is part of the <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->Samba</SPAN ->(7)</SPAN +>This tool is part of the <A +HREF="samba.7.html" +TARGET="_top" +> Samba</A > suite.</P ><P ><B @@ -61,12 +59,9 @@ 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 <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->ftp</SPAN ->(1)</SPAN + similar to that of the ftp program (see <B +CLASS="COMMAND" +>ftp(1)</B >). Operations include things like getting files from the server to the local machine, putting files from the local machine to @@ -76,7 +71,7 @@ CLASS="REFENTRYTITLE" ><DIV CLASS="REFSECT1" ><A -NAME="AEN45" +NAME="AEN40" ></A ><H2 >OPTIONS</H2 @@ -131,13 +126,9 @@ CLASS="PARAMETER" CLASS="COMMAND" >smbclient</B > or - using the name resolve order parameter in - the <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smb.conf</SPAN ->(5)</SPAN + using the name resolve order parameter in the <TT +CLASS="FILENAME" +>smb.conf</TT > file, allowing an administrator to change the order and methods by which server names are looked up. </P @@ -187,13 +178,10 @@ CLASS="PARAMETER" >-s smb.conf</DT ><DD ><P ->Specifies the location of the all - important <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smb.conf</SPAN ->(5)</SPAN +>Specifies the location of the all important + <TT +CLASS="FILENAME" +>smb.conf</TT > file. </P ></DD ><DT @@ -201,14 +189,10 @@ CLASS="REFENTRYTITLE" ><DD ><P >TCP socket options to set on the client - 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 + socket. See the socket options parameter in the <TT +CLASS="FILENAME" +> smb.conf (5)</TT +> manpage for the list of valid options. </P ></DD ><DT @@ -221,7 +205,7 @@ CLASS="REFENTRYTITLE" 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 @@ -230,15 +214,12 @@ CLASS="REFENTRYTITLE" ><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 <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->lmhosts</SPAN ->(5)</SPAN + 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.</P ></LI @@ -247,7 +228,7 @@ CLASS="REFENTRYTITLE" ><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 @@ -267,7 +248,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 @@ -282,7 +263,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" @@ -297,12 +278,9 @@ CLASS="PARAMETER" ></UL ><P >If this parameter is not set then the name resolve order - defined in the <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smb.conf</SPAN ->(5)</SPAN + defined in the <TT +CLASS="FILENAME" +>smb.conf</TT > file parameter (name resolve order) will be used. </P ><P @@ -313,12 +291,9 @@ CLASS="PARAMETER" >name resolve order </I ></TT -> parameter of the <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smb.conf</SPAN ->(5)</SPAN +> parameter of the <TT +CLASS="FILENAME" +>smb.conf</TT > file the name resolution methods will be attempted in this order. </P ></DD @@ -368,17 +343,9 @@ CLASS="PARAMETER" > options useful, as they allow you to control the FROM and TO parts of the message. </P ><P ->See the <TT -CLASS="PARAMETER" -><I ->message command</I -></TT -> parameter in the <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smb.conf</SPAN ->(5)</SPAN +>See the message command parameter in the <TT +CLASS="FILENAME" +> smb.conf(5)</TT > for a description of how to handle incoming WinPopup messages in Samba. </P ><P @@ -647,7 +614,8 @@ 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 @@ -722,14 +690,12 @@ CLASS="COMMAND" ><DD ><P >Override the default workgroup (domain) specified - 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 + 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 ></DD ><DT >-T tar options</DT @@ -939,7 +905,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 @@ -1034,21 +1000,13 @@ 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="AEN336" +NAME="AEN310" ></A ><H2 >OPERATIONS</H2 @@ -1061,7 +1019,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 @@ -1538,7 +1496,7 @@ CLASS="REPLACEABLE" ><DIV CLASS="REFSECT1" ><A -NAME="AEN527" +NAME="AEN501" ></A ><H2 >NOTES</H2 @@ -1559,7 +1517,7 @@ NAME="AEN527" ><DIV CLASS="REFSECT1" ><A -NAME="AEN532" +NAME="AEN506" ></A ><H2 >ENVIRONMENT VARIABLES</H2 @@ -1592,7 +1550,7 @@ CLASS="ENVAR" ><DIV CLASS="REFSECT1" ><A -NAME="AEN540" +NAME="AEN514" ></A ><H2 >INSTALLATION</H2 @@ -1623,12 +1581,10 @@ 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 <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbd</SPAN ->(8)</SPAN + running SMB/CIFS server. It is possible to run <B +CLASS="COMMAND" +>smbd(8) + </B > 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 @@ -1636,7 +1592,7 @@ CLASS="REFENTRYTITLE" ><DIV CLASS="REFSECT1" ><A -NAME="AEN552" +NAME="AEN524" ></A ><H2 >DIAGNOSTICS</H2 @@ -1652,17 +1608,18 @@ NAME="AEN552" ><DIV CLASS="REFSECT1" ><A -NAME="AEN556" +NAME="AEN528" ></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="AEN559" +NAME="AEN531" ></A ><H2 >AUTHOR</H2 @@ -1674,14 +1631,14 @@ NAME="AEN559" ><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. The conversion to DocBook XML 4.2 for Samba 3.0 - was done by Alexander Bokovoy.</P + Samba 2.2 was done by Gerald Carter</P ></DIV ></BODY ></HTML diff --git a/docs/htmldocs/smbcontrol.1.html b/docs/htmldocs/smbcontrol.1.html index 25c8e33e08..12662dcc04 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.1" +NAME="SMBCONTROL" ></A >smbcontrol</H1 ><DIV @@ -52,42 +52,37 @@ NAME="AEN17" ><H2 >DESCRIPTION</H2 ><P ->This tool is part of the <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->Samba</SPAN ->(7)</SPAN +>This tool is part of the <A +HREF="samba.7.html" +TARGET="_top" +> Samba</A > suite.</P ><P ><B CLASS="COMMAND" >smbcontrol</B > is a very small program, which - 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 + 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 ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN34" +NAME="AEN26" ></A ><H2 >OPTIONS</H2 @@ -114,7 +109,8 @@ CLASS="PARAMETER" ><I >nmbd</I ></TT ->, <TT +> + <TT CLASS="PARAMETER" ><I >smbd</I @@ -326,7 +322,7 @@ CLASS="CONSTANT" ><DIV CLASS="REFSECT1" ><A -NAME="AEN110" +NAME="AEN102" ></A ><H2 >VERSION</H2 @@ -337,29 +333,33 @@ NAME="AEN110" ><DIV CLASS="REFSECT1" ><A -NAME="AEN113" +NAME="AEN105" ></A ><H2 >SEE ALSO</H2 ><P -><SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->nmbd</SPAN ->(8)</SPAN -> and <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbd</SPAN ->(8)</SPAN ->.</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 ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN122" +NAME="AEN112" ></A ><H2 >AUTHOR</H2 @@ -371,14 +371,14 @@ NAME="AEN122" ><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. The conversion to DocBook XML 4.2 for - Samba 3.0 was done by Alexander Bokovoy.</P + Samba 2.2 was done by Gerald Carter</P ></DIV ></BODY ></HTML diff --git a/docs/htmldocs/smbd.8.html b/docs/htmldocs/smbd.8.html index 47788cdb36..65f5f95b8d 100644 --- a/docs/htmldocs/smbd.8.html +++ b/docs/htmldocs/smbd.8.html @@ -1,11 +1,12 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"> <HTML ><HEAD ><TITLE >smbd</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"></HEAD +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"></HEAD ><BODY CLASS="REFENTRY" BGCOLOR="#FFFFFF" @@ -15,9 +16,7 @@ VLINK="#840084" ALINK="#0000FF" ><H1 ><A -NAME="SMBD.8" -></A ->smbd</H1 +NAME="SMBD">smbd</H1 ><DIV CLASS="REFNAMEDIV" ><A @@ -29,15 +28,13 @@ NAME="AEN5" ><DIV CLASS="REFSYNOPSISDIV" ><A -NAME="AEN8" -></A -><H2 +NAME="AEN8"><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" @@ -47,13 +44,7 @@ NAME="AEN23" ><H2 >DESCRIPTION</H2 ><P ->This program is part of the <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->Samba</SPAN ->(7)</SPAN -> suite.</P +>This program is part of the Samba suite.</P ><P ><B CLASS="COMMAND" @@ -70,24 +61,28 @@ 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 <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smb.conf</SPAN ->(5)</SPAN + services (see <A +HREF="smb.conf.5.html" +TARGET="_top" +><TT +CLASS="FILENAME" +>smb.conf(5) + </TT +></A >. 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 <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smb.conf</SPAN ->(5)</SPAN -> manual page should be regarded as mandatory reading before + 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 proceeding with installation.</P ><P >A session is created whenever a client requests one. @@ -109,7 +104,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN42" +NAME="AEN37" ></A ><H2 >OPTIONS</H2 @@ -227,7 +222,7 @@ CLASS="COMMAND" Samba was built.</P ></DD ><DT ->-d <debug level></DT +>-d <debug level></DT ><DD ><P ><TT @@ -256,23 +251,19 @@ CLASS="REPLACEABLE" override the <A HREF="smb.conf.5.html#loglevel" TARGET="_top" -><TT -CLASS="PARAMETER" -><I >log - level</I -></TT + level</A +> parameter in the <A +HREF="smb.conf.5.html" +TARGET="_top" +> <TT +CLASS="FILENAME" +>smb.conf(5)</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, @@ -289,25 +280,18 @@ 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="PARAMETER" -><I ->max log size</I -></TT +CLASS="FILENAME" +> smb.conf(5)</TT ></A -> - option in the <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smb.conf</SPAN ->(5)</SPAN -> file. <SPAN -CLASS="emphasis" -><I +> file. <I CLASS="EMPHASIS" >Beware:</I -></SPAN > If the directory specified does not exist, <B CLASS="COMMAND" @@ -320,29 +304,26 @@ 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="PARAMETER" -><I ->socket options</I -></TT +CLASS="FILENAME" +>smb.conf(5) + </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 @@ -373,7 +354,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 @@ -381,12 +362,13 @@ 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 <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smb.conf</SPAN ->(5)</SPAN + to provide. See <A +HREF="smb.conf.5.html" +TARGET="_top" +><TT +CLASS="FILENAME" +> smb.conf(5)</TT +></A > for more information. The default configuration file name is determined at compile time.</P @@ -397,7 +379,7 @@ CLASS="REFENTRYTITLE" ><DIV CLASS="REFSECT1" ><A -NAME="AEN135" +NAME="AEN123" ></A ><H2 >FILES</H2 @@ -420,9 +402,9 @@ CLASS="COMMAND" > meta-daemon, this file must contain suitable startup information for the meta-daemon. See the <A -HREF="install.html" +HREF="UNIX_INSTALL.html" TARGET="_top" ->"How to Install and Test SAMBA"</A +>UNIX_INSTALL.html</A > document for details. </P @@ -440,9 +422,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="install.html" +HREF="UNIX_INSTALL.html" TARGET="_top" ->"How to Install and Test SAMBA"</A +>UNIX_INSTALL.html</A > document for details.</P ></DD @@ -461,9 +443,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="install.html" +HREF="UNIX_INSTALL.html" TARGET="_top" ->"How to Install and Test SAMBA"</A +>UNIX_INSTALL.html</A > document for details.</P ></DD @@ -474,30 +456,34 @@ CLASS="FILENAME" ></DT ><DD ><P ->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 +>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 install this file are <TT CLASS="FILENAME" >/usr/samba/lib/smb.conf</TT > and <TT CLASS="FILENAME" ->/etc/samba/smb.conf</TT +>/etc/smb.conf</TT >.</P ><P >This file describes all the services the server - is to make available to clients. See <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smb.conf</SPAN ->(5)</SPAN -> for more information.</P + 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 ></DD ></DL ></DIV @@ -505,7 +491,7 @@ CLASS="REFENTRYTITLE" ><DIV CLASS="REFSECT1" ><A -NAME="AEN173" +NAME="AEN159" ></A ><H2 >LIMITATIONS</H2 @@ -524,7 +510,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN177" +NAME="AEN163" ></A ><H2 >ENVIRONMENT VARIABLES</H2 @@ -555,7 +541,7 @@ CLASS="CONSTANT" ><DIV CLASS="REFSECT1" ><A -NAME="AEN186" +NAME="AEN172" ></A ><H2 >PAM INTERACTION</H2 @@ -563,35 +549,22 @@ NAME="AEN186" >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" -><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: +>obey pam restricions</A +> + smb.conf 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 @@ -600,12 +573,9 @@ 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. @@ -618,7 +588,7 @@ CLASS="EMPHASIS" ><DIV CLASS="REFSECT1" ><A -NAME="AEN201" +NAME="AEN183" ></A ><H2 >VERSION</H2 @@ -629,7 +599,7 @@ NAME="AEN201" ><DIV CLASS="REFSECT1" ><A -NAME="AEN204" +NAME="AEN186" ></A ><H2 >DIAGNOSTICS</H2 @@ -652,7 +622,7 @@ NAME="AEN204" ><DIV CLASS="REFSECT1" ><A -NAME="AEN209" +NAME="AEN191" ></A ><H2 >SIGNALS</H2 @@ -674,12 +644,9 @@ CLASS="COMMAND" that <B CLASS="COMMAND" >SIGKILL (-9)</B -> <SPAN -CLASS="emphasis" -><I +> <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 @@ -693,14 +660,16 @@ CLASS="COMMAND" CLASS="COMMAND" >smbd</B > may be raised - 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, + 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, whilst still running at a normally low log level.</P ><P >Note that as the signal handlers send a debug write, @@ -719,55 +688,55 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN227" +NAME="AEN208" ></A ><H2 >SEE ALSO</H2 ><P -><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 +>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 CLASS="FILENAME" >rfc1001.txt</TT >, <TT @@ -785,7 +754,7 @@ TARGET="_top" ><DIV CLASS="REFSECT1" ><A -NAME="AEN254" +NAME="AEN225" ></A ><H2 >AUTHOR</H2 @@ -797,14 +766,14 @@ NAME="AEN254" ><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. The conversion to DocBook XML 4.2 for - Samba 3.0 was done by Alexander Bokovoy.</P + Samba 2.2 was done by Gerald Carter</P ></DIV ></BODY ></HTML diff --git a/docs/htmldocs/smbgroupedit.8.html b/docs/htmldocs/smbgroupedit.8.html index 856c778cb4..e20b34883c 100644 --- a/docs/htmldocs/smbgroupedit.8.html +++ b/docs/htmldocs/smbgroupedit.8.html @@ -1,11 +1,12 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"> <HTML ><HEAD ><TITLE >smbgroupedit</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"></HEAD +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"></HEAD ><BODY CLASS="REFENTRY" BGCOLOR="#FFFFFF" @@ -15,9 +16,7 @@ VLINK="#840084" ALINK="#0000FF" ><H1 ><A -NAME="SMBGROUPEDIT.8" -></A ->smbgroupedit</H1 +NAME="SMBGROUPEDIT">smbgroupedit</H1 ><DIV CLASS="REFNAMEDIV" ><A @@ -29,15 +28,13 @@ NAME="AEN5" ><DIV CLASS="REFSYNOPSISDIV" ><A -NAME="AEN8" -></A -><H2 +NAME="AEN8"><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" @@ -47,13 +44,12 @@ NAME="AEN13" ><H2 >DESCRIPTION</H2 ><P ->This program is part of the <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->Samba</SPAN ->(7)</SPAN -> suite.</P +>This program is part of the <A +HREF="samba.7.html" +TARGET="_top" +>Samba</A +> +suite.</P ><P >The smbgroupedit command allows for mapping unix groups to NT Builtin, Domain, or Local groups. Also @@ -63,7 +59,7 @@ etc.</P ><DIV CLASS="REFSECT1" ><A -NAME="AEN20" +NAME="AEN18" ></A ><H2 >OPTIONS</H2 @@ -90,6 +86,12 @@ 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" @@ -98,10 +100,20 @@ CLASS="PROGRAMLISTING" Group type : Comment : Privilege :</PRE +></TD +></TR +></TABLE ></P ><P ->For example: -<PRE +>For examples,</P +><P +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="90%" +><TR +><TD +><PRE CLASS="PROGRAMLISTING" >Users SID : S-1-5-32-545 @@ -109,6 +121,9 @@ CLASS="PROGRAMLISTING" Group type: Local group Comment : Privilege : No privilege</PRE +></TD +></TR +></TABLE ></P ></DD ><DT @@ -117,15 +132,34 @@ 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: -<PRE +>For example,</P +><P +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="90%" +><TR +><TD +><PRE CLASS="PROGRAMLISTING" >Users (S-1-5-32-545) -> -1</PRE +></TD +></TR +></TABLE ></P ></DD ></DL @@ -199,15 +233,23 @@ 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 @@ -218,13 +260,24 @@ 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: -<PRE + </P +><P +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="90%" +><TR +><TD +><PRE CLASS="PROGRAMLISTING" ><TT CLASS="PROMPT" @@ -235,14 +288,14 @@ CLASS="COMMAND" -c S-1-5-21-1108995562-3116817432-1375597819-512 \ -u domadm -td</B ></PRE +></TD +></TR +></TABLE ></P ><P -><SPAN -CLASS="emphasis" -><I +> <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 @@ -251,8 +304,15 @@ CLASS="EMPHASIS" ></LI ></OL ><P ->To verify that your mapping has taken effect: -<PRE +>To verify that your mapping has taken effect:</P +><P +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="100%" +><TR +><TD +><PRE CLASS="PROGRAMLISTING" ><TT CLASS="PROMPT" @@ -262,12 +322,22 @@ 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: -<PRE +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 CLASS="PROGRAMLISTING" ><TT CLASS="PROMPT" @@ -276,12 +346,15 @@ CLASS="PROMPT" CLASS="COMMAND" >smbgroupedit -a unixgroup -td</B ></PRE +></TD +></TR +></TABLE ></P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN87" +NAME="AEN90" ></A ><H2 >VERSION</H2 @@ -292,23 +365,21 @@ the Samba suite.</P ><DIV CLASS="REFSECT1" ><A -NAME="AEN90" +NAME="AEN93" ></A ><H2 >SEE ALSO</H2 ><P -><SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smb.conf</SPAN ->(5)</SPAN +><A +HREF="smb.conf.5.html" +TARGET="_top" +>smb.conf(5)</A ></P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN96" +NAME="AEN97" ></A ><H2 >AUTHOR</H2 @@ -323,8 +394,7 @@ 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. The conversion -to DocBook XML 4.2 for Samba 3.0 was done by Alexander Bokovoy.</P +by the Samba Team in the same fashion as the Samba source code.</P ></DIV ></BODY ></HTML diff --git a/docs/htmldocs/smbmnt.8.html b/docs/htmldocs/smbmnt.8.html index de3af0b0a4..06b9fb1fd3 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.8" +NAME="SMBMNT" ></A >smbmnt</H1 ><DIV @@ -65,12 +65,14 @@ CLASS="COMMAND" CLASS="COMMAND" >smbmnt</B > program is normally invoked - by <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbmount</SPAN ->(8)</SPAN + by <A +HREF="smbmount.8.html" +TARGET="_top" +><B +CLASS="COMMAND" +>smbmount(8)</B +> + </A >. It should not be invoked directly by users. </P ><P >smbmount searches the normal PATH for smbmnt. You must ensure @@ -79,7 +81,7 @@ CLASS="REFENTRYTITLE" ><DIV CLASS="REFSECT1" ><A -NAME="AEN31" +NAME="AEN30" ></A ><H2 >OPTIONS</H2 @@ -137,7 +139,7 @@ CLASS="VARIABLELIST" ><DIV CLASS="REFSECT1" ><A -NAME="AEN58" +NAME="AEN57" ></A ><H2 >AUTHOR</H2 @@ -170,8 +172,7 @@ TARGET="_top" </P ><P >The conversion of this manpage for Samba 2.2 was performed - by Gerald Carter. The conversion to DocBook XML 4.2 for Samba 3.0 - was done by Alexander Bokovoy.</P + by Gerald Carter</P ></DIV ></BODY ></HTML diff --git a/docs/htmldocs/smbmount.8.html b/docs/htmldocs/smbmount.8.html index bc9fcf72e2..81a3ac04b2 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.8" +NAME="SMBMOUNT" ></A >smbmount</H1 ><DIV @@ -55,12 +55,9 @@ CLASS="COMMAND" CLASS="COMMAND" >mount.smbfs</B > by - the <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->mount</SPAN ->(8)</SPAN + the <B +CLASS="COMMAND" +>mount(8)</B > command when using the "-t smbfs" option. This command only works in Linux, and the kernel must support the smbfs filesystem. </P @@ -83,9 +80,10 @@ 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 @@ -98,12 +96,9 @@ CLASS="EMPHASIS" CLASS="COMMAND" >smbmount</B > - calls <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbmnt</SPAN ->(8)</SPAN + calls <B +CLASS="COMMAND" +>smbmnt(8)</B > to do the actual mount. You must make sure that <B CLASS="COMMAND" @@ -114,7 +109,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN35" +NAME="AEN31" ></A ><H2 >OPTIONS</H2 @@ -164,13 +159,16 @@ CLASS="COMMAND" >credentials=<filename></DT ><DD ><P ->specifies a file that contains a username and/or password. -The format of the file is: -<PRE +>specifies a file that contains a username + and/or password. The format of the file is:</P +><P +> <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 @@ -257,12 +255,10 @@ CLASS="FILENAME" >sets the TCP socket options. See the <A HREF="smb.conf.5.html#SOCKETOPTIONS" TARGET="_top" -><SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smb.conf</SPAN ->(5)</SPAN +><TT +CLASS="FILENAME" +>smb.conf + </TT ></A > <TT CLASS="PARAMETER" @@ -336,7 +332,7 @@ CLASS="PARAMETER" ><DIV CLASS="REFSECT1" ><A -NAME="AEN130" +NAME="AEN125" ></A ><H2 >ENVIRONMENT VARIABLES</H2 @@ -368,7 +364,7 @@ CLASS="ENVAR" ><DIV CLASS="REFSECT1" ><A -NAME="AEN138" +NAME="AEN133" ></A ><H2 >BUGS</H2 @@ -403,7 +399,7 @@ NAME="AEN138" ><DIV CLASS="REFSECT1" ><A -NAME="AEN147" +NAME="AEN142" ></A ><H2 >SEE ALSO</H2 @@ -413,19 +409,22 @@ NAME="AEN147" ><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 <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 +>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 ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN155" +NAME="AEN149" ></A ><H2 >AUTHOR</H2 @@ -458,8 +457,7 @@ TARGET="_top" </P ><P >The conversion of this manpage for Samba 2.2 was performed - by Gerald Carter. The conversion to DocBook XML 4.2 for Samba 3.0 - was done by Alexander Bokovoy.</P + by Gerald Carter</P ></DIV ></BODY ></HTML diff --git a/docs/htmldocs/smbpasswd.5.html b/docs/htmldocs/smbpasswd.5.html index a07be03b41..ac3ab94691 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.5" +NAME="SMBPASSWD" ></A >smbpasswd</H1 ><DIV @@ -47,12 +47,10 @@ NAME="AEN11" ><H2 >DESCRIPTION</H2 ><P ->This tool is part of the <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->Samba</SPAN ->(7)</SPAN +>This tool is part of the <A +HREF="samba.7.html" +TARGET="_top" +> Samba</A > suite.</P ><P >smbpasswd is the Samba encrypted password file. It contains @@ -64,7 +62,7 @@ CLASS="REFENTRYTITLE" ><DIV CLASS="REFSECT1" ><A -NAME="AEN18" +NAME="AEN16" ></A ><H2 >FILE FORMAT</H2 @@ -206,7 +204,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 following characters: + The contents of this field may be any of the characters. </P ><P ></P @@ -243,12 +241,10 @@ CLASS="PARAMETER" > parameter is set in the <A HREF="smb.conf.5.html#NULLPASSWORDS" TARGET="_top" -><SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smb.conf</SPAN ->(5)</SPAN +><TT +CLASS="FILENAME" +>smb.conf(5) + </TT ></A > config file. </P ></LI @@ -261,7 +257,8 @@ 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 @@ -299,7 +296,7 @@ CLASS="EMPHASIS" ><DIV CLASS="REFSECT1" ><A -NAME="AEN77" +NAME="AEN73" ></A ><H2 >VERSION</H2 @@ -310,23 +307,23 @@ NAME="AEN77" ><DIV CLASS="REFSECT1" ><A -NAME="AEN80" +NAME="AEN76" ></A ><H2 >SEE ALSO</H2 ><P -><SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbpasswd</SPAN ->(8)</SPAN ->, <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->Samba</SPAN ->(7)</SPAN +><A +HREF="smbpasswd.8.html" +TARGET="_top" +><B +CLASS="COMMAND" +>smbpasswd(8)</B +></A +>, + <A +HREF="samba.7.html" +TARGET="_top" +>samba(7)</A >, and the Internet RFC1321 for details on the MD4 algorithm. </P @@ -334,7 +331,7 @@ CLASS="REFENTRYTITLE" ><DIV CLASS="REFSECT1" ><A -NAME="AEN89" +NAME="AEN82" ></A ><H2 >AUTHOR</H2 @@ -346,14 +343,14 @@ NAME="AEN89" ><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. The conversion to DocBook XML 4.2 - for Samba 3.0 was done by Alexander Bokovoy.</P + Samba 2.2 was done by Gerald Carter</P ></DIV ></BODY ></HTML diff --git a/docs/htmldocs/smbpasswd.8.html b/docs/htmldocs/smbpasswd.8.html index 223cd02521..da3cb9f601 100644 --- a/docs/htmldocs/smbpasswd.8.html +++ b/docs/htmldocs/smbpasswd.8.html @@ -1,11 +1,12 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"> <HTML ><HEAD ><TITLE >smbpasswd</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"></HEAD +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"></HEAD ><BODY CLASS="REFENTRY" BGCOLOR="#FFFFFF" @@ -15,9 +16,7 @@ VLINK="#840084" ALINK="#0000FF" ><H1 ><A -NAME="SMBPASSWD.8" -></A ->smbpasswd</H1 +NAME="SMBPASSWD">smbpasswd</H1 ><DIV CLASS="REFNAMEDIV" ><A @@ -29,15 +28,13 @@ NAME="AEN5" ><DIV CLASS="REFSYNOPSISDIV" ><A -NAME="AEN8" -></A -><H2 +NAME="AEN8"><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" @@ -47,23 +44,18 @@ NAME="AEN27" ><H2 >DESCRIPTION</H2 ><P ->This tool is part of the <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->Samba</SPAN ->(7)</SPAN +>This tool is part of the <A +HREF="samba.7.html" +TARGET="_top" +> Samba</A > suite.</P ><P >The smbpasswd program has several different - functions, depending on whether it is run by the <SPAN -CLASS="emphasis" -><I + functions, depending on whether it is run by the <I CLASS="EMPHASIS" >root</I -></SPAN -> user - or not. When run as a normal user it allows the user to change +> + 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 @@ -72,33 +64,25 @@ 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 <SPAN -CLASS="emphasis" -><I + however in that it is not <I CLASS="EMPHASIS" >setuid root</I -></SPAN > but works in - a client-server mode and communicates with a - locally running <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbd</SPAN ->(8)</SPAN + a client-server mode and communicates with a locally running + <B +CLASS="COMMAND" +>smbd(8)</B >. 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 <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbpasswd</SPAN ->(5)</SPAN + the <TT +CLASS="FILENAME" +>smbpasswd(5)</TT > file. </P ><P >When run by an ordinary user with no options, smbpasswd @@ -107,28 +91,18 @@ CLASS="REFENTRYTITLE" 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 (<TT -CLASS="PARAMETER" -><I ->-r</I -></TT ->) and <TT -CLASS="PARAMETER" -><I ->-U</I -></TT -> options - below. </P + Controllers. See the (-r) and -U 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 @@ -136,7 +110,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN51" +NAME="AEN43" ></A ><H2 >OPTIONS</H2 @@ -151,7 +125,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 @@ -195,12 +169,10 @@ 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 <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbpasswd</SPAN ->(5)</SPAN + this information and the command will FAIL. See <B +CLASS="COMMAND" +>smbpasswd(5) + </B > for details on the 'old' and new password file formats. </P ><P @@ -224,12 +196,9 @@ CLASS="CONSTANT" CLASS="COMMAND" > smbpasswd</B > will FAIL to enable the account. - See <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbpasswd</SPAN ->(5)</SPAN + See <B +CLASS="COMMAND" +>smbpasswd (5)</B > for details on the 'old' and new password file formats. </P ><P @@ -325,12 +294,9 @@ 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 @@ -344,7 +310,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 @@ -353,14 +319,12 @@ 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 <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->lmhosts</SPAN ->(5)</SPAN + 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.</P ></LI @@ -369,7 +333,7 @@ CLASS="REFENTRYTITLE" ><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 @@ -389,7 +353,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 @@ -404,7 +368,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" @@ -421,12 +385,10 @@ CLASS="PARAMETER" CLASS="COMMAND" >lmhosts, host, wins, bcast</B > - and without this parameter or any entry in the <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smb.conf</SPAN ->(5)</SPAN + and without this parameter or any entry in the + <TT +CLASS="FILENAME" +>smb.conf</TT > file the name resolution methods will be attempted in this order. </P ></DD @@ -512,7 +474,7 @@ CLASS="PARAMETER" >. Note that the password is stored in the <TT CLASS="FILENAME" ->secrets.tdb</TT +>private/secrets.tdb</TT > and is keyed off of the admin's DN. This means that if the value of <TT CLASS="PARAMETER" @@ -547,12 +509,9 @@ CLASS="PARAMETER" ><DD ><P >This specifies the username for all of the - <SPAN -CLASS="emphasis" -><I + <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. @@ -564,7 +523,7 @@ CLASS="EMPHASIS" ><DIV CLASS="REFSECT1" ><A -NAME="AEN189" +NAME="AEN173" ></A ><H2 >NOTES</H2 @@ -578,71 +537,70 @@ 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 either <TT +> running on the local machine by specifying a + <TT CLASS="PARAMETER" ><I ->allow - hosts</I +>allow hosts</I ></TT > or <TT CLASS="PARAMETER" ><I >deny hosts</I ></TT -> entry in - the <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smb.conf</SPAN ->(5)</SPAN +> + entry in the <TT +CLASS="FILENAME" +>smb.conf</TT > 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 document <A -HREF="pwencrypt.html" -TARGET="_top" -> "LanMan and NT Password Encryption in Samba"</A + has been set up to use encrypted passwords. See the file + <TT +CLASS="FILENAME" +>ENCRYPTION.txt</TT > in the docs directory for details on how to do this. </P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN201" +NAME="AEN183" ></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="AEN204" +NAME="AEN186" ></A ><H2 >SEE ALSO</H2 ><P -><SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbpasswd</SPAN ->(5)</SPAN ->, <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->Samba</SPAN ->(7)</SPAN ->.</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 ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN213" +NAME="AEN192" ></A ><H2 >AUTHOR</H2 @@ -654,14 +612,14 @@ NAME="AEN213" ><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. The conversion to DocBook XML 4.2 - for Samba 3.0 was done by Alexander Bokovoy.</P + Samba 2.2 was done by Gerald Carter</P ></DIV ></BODY ></HTML diff --git a/docs/htmldocs/smbsh.1.html b/docs/htmldocs/smbsh.1.html index c8c61fb6fe..bab2b45cdd 100644 --- a/docs/htmldocs/smbsh.1.html +++ b/docs/htmldocs/smbsh.1.html @@ -1,11 +1,12 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"> <HTML ><HEAD ><TITLE >smbsh</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"></HEAD +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"></HEAD ><BODY CLASS="REFENTRY" BGCOLOR="#FFFFFF" @@ -15,9 +16,7 @@ VLINK="#840084" ALINK="#0000FF" ><H1 ><A -NAME="SMBSH.1" -></A ->smbsh</H1 +NAME="SMBSH">smbsh</H1 ><DIV CLASS="REFNAMEDIV" ><A @@ -30,15 +29,13 @@ NAME="AEN5" ><DIV CLASS="REFSYNOPSISDIV" ><A -NAME="AEN8" -></A -><H2 +NAME="AEN8"><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" @@ -48,12 +45,10 @@ NAME="AEN18" ><H2 >DESCRIPTION</H2 ><P ->This tool is part of the <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->Samba</SPAN ->(7)</SPAN +>This tool is part of the <A +HREF="samba.7.html" +TARGET="_top" +> Samba</A > suite.</P ><P ><B @@ -79,7 +74,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN30" +NAME="AEN28" ></A ><H2 >OPTIONS</H2 @@ -93,12 +88,9 @@ CLASS="VARIABLELIST" ><DD ><P >Override the default workgroup specified in the - workgroup parameter of the <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smb.conf</SPAN ->(5)</SPAN + workgroup parameter of the <TT +CLASS="FILENAME" +>smb.conf</TT > file for this session. This may be needed to connect to some servers. </P @@ -120,17 +112,14 @@ CLASS="REFENTRYTITLE" >This option allows the user to set the directory prefix for SMB access. The default value if this option is not specified is - <SPAN -CLASS="emphasis" -><I + <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 @@ -138,7 +127,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 @@ -148,18 +137,16 @@ 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 <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->lmhosts</SPAN ->(5)</SPAN -> for details) - then any name type matches for lookup. + (see the <A +HREF="lmhosts.5.html" +TARGET="_top" +>lmhosts(5)</A +> + for details) then any name type matches for lookup. </P ></LI ><LI @@ -167,7 +154,7 @@ CLASS="REFENTRYTITLE" ><TT CLASS="CONSTANT" >host</TT ->: +> : Do a standard host name to IP address resolution, using the system <TT CLASS="FILENAME" @@ -189,7 +176,7 @@ CLASS="FILENAME" ><TT CLASS="CONSTANT" >wins</TT ->: +> : Query a name with the IP address listed in the <TT CLASS="PARAMETER" @@ -206,7 +193,7 @@ CLASS="PARAMETER" ><TT CLASS="CONSTANT" >bcast</TT ->: +> : Do a broadcast on each of the known local interfaces listed in the <TT CLASS="PARAMETER" @@ -222,19 +209,11 @@ CLASS="PARAMETER" ></UL ><P >If this parameter is not set then the name resolve order - defined in the <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smb.conf</SPAN ->(5)</SPAN + defined in the <TT +CLASS="FILENAME" +>smb.conf</TT > file parameter - (<TT -CLASS="PARAMETER" -><I ->name resolve order</I -></TT ->) will be used. </P + (name resolve order) will be used. </P ><P >The default order is lmhosts, host, wins, bcast. Without this parameter or any entry in the <TT @@ -243,17 +222,15 @@ CLASS="PARAMETER" >name resolve order </I ></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 +> parameter of the <TT +CLASS="FILENAME" +>smb.conf</TT +> + 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 @@ -262,12 +239,9 @@ CLASS="REFENTRYTITLE" is zero.</P ><P >The higher this value, the more detail will be logged - about the activities of <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->nmblookup</SPAN ->(1)</SPAN + about the activities of <B +CLASS="COMMAND" +>nmblookup</B >. At level 0, only critical errors and serious warnings will be logged. </P @@ -310,7 +284,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN104" +NAME="AEN91" ></A ><H2 >EXAMPLES</H2 @@ -323,10 +297,17 @@ 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. -<PRE + operating system.</P +><P +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="100%" +><TR +><TD +><PRE CLASS="PROGRAMLISTING" -><TT +> <TT CLASS="PROMPT" >system% </TT ><TT @@ -335,7 +316,7 @@ CLASS="USERINPUT" >smbsh</B ></TT > -<TT + <TT CLASS="PROMPT" >Username: </TT ><TT @@ -344,7 +325,7 @@ CLASS="USERINPUT" >user</B ></TT > -<TT + <TT CLASS="PROMPT" >Password: </TT ><TT @@ -352,7 +333,11 @@ CLASS="USERINPUT" ><B >XXXXXXX</B ></TT -></PRE +> + </PRE +></TD +></TR +></TABLE ></P ><P >Any dynamically linked command you execute from @@ -372,7 +357,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" @@ -389,17 +374,18 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN124" +NAME="AEN112" ></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="AEN127" +NAME="AEN115" ></A ><H2 >BUGS</H2 @@ -432,29 +418,30 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN136" +NAME="AEN124" ></A ><H2 >SEE ALSO</H2 ><P -><SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbd</SPAN ->(8)</SPAN ->, <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smb.conf</SPAN ->(5)</SPAN -></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 ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN145" +NAME="AEN130" ></A ><H2 >AUTHOR</H2 @@ -466,14 +453,14 @@ NAME="AEN145" ><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. The conversion to DocBook XML 4.2 - for Samba 3.0 was done by Alexander Bokovoy.</P + Samba 2.2 was done by Gerald Carter</P ></DIV ></BODY ></HTML diff --git a/docs/htmldocs/smbspool.8.html b/docs/htmldocs/smbspool.8.html index b66d08381d..8dc2fbbd63 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.8" +NAME="SMBSPOOL" ></A >smbspool</H1 ><DIV @@ -47,12 +47,10 @@ NAME="AEN17" ><H2 >DESCRIPTION</H2 ><P ->This tool is part of the <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->Samba</SPAN ->(7)</SPAN +>This tool is part of the <A +HREF="samba.7.html" +TARGET="_top" +> Samba</A > suite.</P ><P >smbspool is a very small print spooling program that @@ -89,7 +87,8 @@ CLASS="EMPHASIS" ></LI ><LI ><P ->smb://username:password@workgroup/server/printer</P +>smb://username:password@workgroup/server/printer + </P ></LI ></UL ><P @@ -113,7 +112,7 @@ CLASS="ENVAR" ><DIV CLASS="REFSECT1" ><A -NAME="AEN41" +NAME="AEN39" ></A ><H2 >OPTIONS</H2 @@ -162,39 +161,41 @@ NAME="AEN41" ><DIV CLASS="REFSECT1" ><A -NAME="AEN56" +NAME="AEN54" ></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="AEN59" +NAME="AEN57" ></A ><H2 >SEE ALSO</H2 ><P -><SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbd</SPAN ->(8)</SPAN -> and <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->Samba</SPAN ->(7)</SPAN ->.</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 ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN68" +NAME="AEN63" ></A ><H2 >AUTHOR</H2 @@ -212,14 +213,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. The conversion to DocBook XML 4.2 - for Samba 3.0 was done by Alexander Bokovoy.</P + Samba 2.2 was done by Gerald Carter</P ></DIV ></BODY ></HTML diff --git a/docs/htmldocs/smbstatus.1.html b/docs/htmldocs/smbstatus.1.html index 47b7ef112f..fb7e14fadd 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.1" +NAME="SMBSTATUS" ></A >smbstatus</H1 ><DIV @@ -47,12 +47,10 @@ NAME="AEN21" ><H2 >DESCRIPTION</H2 ><P ->This tool is part of the <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->Samba</SPAN ->(7)</SPAN +>This tool is part of the <A +HREF="samba.7.html" +TARGET="_top" +> Samba</A > suite.</P ><P ><B @@ -64,7 +62,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN29" +NAME="AEN27" ></A ><H2 >OPTIONS</H2 @@ -116,12 +114,13 @@ CLASS="VARIABLELIST" >-p|--processes</DT ><DD ><P ->print a list of <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbd</SPAN ->(8)</SPAN +>print a list of <A +HREF="smbd.8.html" +TARGET="_top" +> <B +CLASS="COMMAND" +>smbd(8)</B +></A > processes and exit. Useful for scripting.</P ></DD @@ -137,12 +136,14 @@ CLASS="REFENTRYTITLE" ><P >The default configuration file name is determined at compile time. The file specified contains the - configuration details required by the server. See <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smb.conf</SPAN ->(5)</SPAN + configuration details required by the server. See <A +HREF="smb.conf.5.html" +TARGET="_top" +><TT +CLASS="FILENAME" +>smb.conf(5)</TT +> + </A > for more information.</P ></DD ><DT @@ -163,7 +164,7 @@ CLASS="PARAMETER" ><DIV CLASS="REFSECT1" ><A -NAME="AEN79" +NAME="AEN75" ></A ><H2 >VERSION</H2 @@ -174,29 +175,29 @@ NAME="AEN79" ><DIV CLASS="REFSECT1" ><A -NAME="AEN82" +NAME="AEN78" ></A ><H2 >SEE ALSO</H2 ><P -><SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbd</SPAN ->(8)</SPAN -> and <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smb.conf</SPAN ->(5)</SPAN +><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 >.</P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN91" +NAME="AEN84" ></A ><H2 >AUTHOR</H2 @@ -208,14 +209,14 @@ NAME="AEN91" ><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. The conversion to DocBook XML 4.2 - for Samba 3.0 was done by Alexander Bokovoy.</P + Samba 2.2 was done by Gerald Carter</P ></DIV ></BODY ></HTML diff --git a/docs/htmldocs/smbtar.1.html b/docs/htmldocs/smbtar.1.html index 1eb0017417..d3215c6901 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.1" +NAME="SMBTAR" ></A >smbtar</H1 ><DIV @@ -48,30 +48,30 @@ NAME="AEN26" ><H2 >DESCRIPTION</H2 ><P ->This tool is part of the <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->Samba</SPAN ->(7)</SPAN +>This tool is part of the <A +HREF="samba.7.html" +TARGET="_top" +> Samba</A > suite.</P ><P ><B CLASS="COMMAND" >smbtar</B > is a very small shell script on top - of <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbclient</SPAN ->(1)</SPAN -> which dumps SMB shares directly to tape.</P + of <A +HREF="smbclient.1.html" +TARGET="_top" +><B +CLASS="COMMAND" +>smbclient(1)</B +></A +> + which dumps SMB shares directly to tape. </P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN37" +NAME="AEN34" ></A ><H2 >OPTIONS</H2 @@ -193,13 +193,11 @@ CLASS="PARAMETER" ><I >-d</I ></TT -> flag of <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbclient</SPAN ->(1)</SPAN ->.</P +> flag of <B +CLASS="COMMAND" +>smbclient(1) + </B +>. </P ></DD ></DL ></DIV @@ -207,7 +205,7 @@ CLASS="REFENTRYTITLE" ><DIV CLASS="REFSECT1" ><A -NAME="AEN100" +NAME="AEN95" ></A ><H2 >ENVIRONMENT VARIABLES</H2 @@ -224,7 +222,7 @@ CLASS="PARAMETER" ><DIV CLASS="REFSECT1" ><A -NAME="AEN104" +NAME="AEN99" ></A ><H2 >BUGS</H2 @@ -238,7 +236,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN108" +NAME="AEN103" ></A ><H2 >CAVEATS</H2 @@ -251,7 +249,7 @@ NAME="AEN108" ><DIV CLASS="REFSECT1" ><A -NAME="AEN111" +NAME="AEN106" ></A ><H2 >DIAGNOSTICS</H2 @@ -262,18 +260,21 @@ CLASS="emphasis" CLASS="EMPHASIS" >DIAGNOSTICS</I ></SPAN -> section for the <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbclient</SPAN ->(1)</SPAN +> section for the + <A +HREF="smbclient.1.html" +TARGET="_top" +><B +CLASS="COMMAND" +>smbclient(1)</B +> + </A > command.</P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN118" +NAME="AEN112" ></A ><H2 >VERSION</H2 @@ -284,35 +285,38 @@ NAME="AEN118" ><DIV CLASS="REFSECT1" ><A -NAME="AEN121" +NAME="AEN115" ></A ><H2 >SEE ALSO</H2 ><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 +><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 ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN133" +NAME="AEN123" ></A ><H2 >AUTHOR</H2 @@ -338,14 +342,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. The conversion to DocBook XML 4.2 for - Samba 3.0 was done by Alexander Bokovoy.</P + Samba 2.2 was done by Gerald Carter.</P ></DIV ></BODY ></HTML diff --git a/docs/htmldocs/smbumount.8.html b/docs/htmldocs/smbumount.8.html index 83041b796c..993436f0c6 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.8" +NAME="SMBUMOUNT" ></A >smbumount</H1 ><DIV @@ -88,18 +88,20 @@ NAME="AEN23" ><H2 >SEE ALSO</H2 ><P -><SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbmount</SPAN ->(8)</SPAN +><A +HREF="smbmount.8.html" +TARGET="_top" +><B +CLASS="COMMAND" +>smbmount(8)</B +> + </A ></P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN29" +NAME="AEN28" ></A ><H2 >AUTHOR</H2 @@ -132,8 +134,7 @@ TARGET="_top" </P ><P >The conversion of this manpage for Samba 2.2 was performed - by Gerald Carter. The conversion to DocBook XML 4.2 for Samba 3.0 - was done by Alexander Bokovoy.</P + by Gerald Carter</P ></DIV ></BODY ></HTML diff --git a/docs/htmldocs/speed.html b/docs/htmldocs/speed.html index c99a49142c..1a05706f92 100644 --- a/docs/htmldocs/speed.html +++ b/docs/htmldocs/speed.html @@ -5,7 +5,8 @@ >Samba performance issues</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -16,8 +17,8 @@ REL="PREVIOUS" TITLE="Group mapping HOWTO" HREF="groupmapping.html"><LINK REL="NEXT" -TITLE="Creating Group Profiles" -HREF="groupprofiles.html"></HEAD +TITLE="Appendixes" +HREF="appendixes.html"></HEAD ><BODY CLASS="CHAPTER" BGCOLOR="#FFFFFF" @@ -59,7 +60,7 @@ WIDTH="10%" ALIGN="right" VALIGN="bottom" ><A -HREF="groupprofiles.html" +HREF="appendixes.html" ACCESSKEY="N" >Next</A ></TD @@ -72,17 +73,13 @@ WIDTH="100%"></DIV CLASS="CHAPTER" ><H1 ><A -NAME="SPEED" -></A ->Chapter 19. Samba performance issues</H1 +NAME="SPEED">Chapter 22. Samba performance issues</H1 ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3033" -></A ->19.1. Comparisons</H1 +NAME="AEN3055">22.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 @@ -111,9 +108,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3039" -></A ->19.2. Socket options</H1 +NAME="AEN3061">22.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 @@ -139,9 +134,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3046" -></A ->19.3. Read size</H1 +NAME="AEN3068">22.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 @@ -165,9 +158,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3051" -></A ->19.4. Max xmit</H1 +NAME="AEN3073">22.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 @@ -188,9 +179,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3056" -></A ->19.5. Log level</H1 +NAME="AEN3078">22.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 @@ -202,9 +191,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3059" -></A ->19.6. Read raw</H1 +NAME="AEN3081">22.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, @@ -224,9 +211,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3064" -></A ->19.7. Write raw</H1 +NAME="AEN3086">22.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, @@ -241,9 +226,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3068" -></A ->19.8. Slow Clients</H1 +NAME="AEN3090">22.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 @@ -258,9 +241,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3072" -></A ->19.9. Slow Logins</H1 +NAME="AEN3094">22.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 @@ -271,9 +252,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3075" -></A ->19.10. Client tuning</H1 +NAME="AEN3097">22.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 @@ -407,7 +386,7 @@ WIDTH="33%" ALIGN="right" VALIGN="top" ><A -HREF="groupprofiles.html" +HREF="appendixes.html" ACCESSKEY="N" >Next</A ></TD @@ -431,7 +410,7 @@ ACCESSKEY="U" WIDTH="33%" ALIGN="right" VALIGN="top" ->Creating Group Profiles</TD +>Appendixes</TD ></TR ></TABLE ></DIV diff --git a/docs/htmldocs/swat.8.html b/docs/htmldocs/swat.8.html index 0c65e7b1d6..f101a7bc26 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.8" +NAME="SWAT" ></A >swat</H1 ><DIV @@ -47,24 +47,23 @@ NAME="AEN13" ><H2 >DESCRIPTION</H2 ><P ->This tool is part of the <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->Samba</SPAN ->(7)</SPAN +>This tool is part of the <A +HREF="samba.7.html" +TARGET="_top" +> Samba</A > suite.</P ><P ><B CLASS="COMMAND" >swat</B > allows a Samba administrator to - configure the complex <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smb.conf</SPAN ->(5)</SPAN + configure the complex <A +HREF="smb.conf.5.html" +TARGET="_top" +><TT +CLASS="FILENAME" +> smb.conf(5)</TT +></A > file via a Web browser. In addition, a <B CLASS="COMMAND" @@ -87,7 +86,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN29" +NAME="AEN26" ></A ><H2 >OPTIONS</H2 @@ -102,14 +101,11 @@ CLASS="VARIABLELIST" ><P >The default configuration file path is determined at compile time. The file specified contains - the configuration details required by the <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbd</SPAN ->(8)</SPAN -> server. This is the file - that <B + the configuration details required by the <B +CLASS="COMMAND" +>smbd + </B +> server. This is the file that <B CLASS="COMMAND" >swat</B > will modify. @@ -151,7 +147,7 @@ CLASS="EMPHASIS" ><DIV CLASS="REFSECT1" ><A -NAME="AEN49" +NAME="AEN44" ></A ><H2 >INSTALLATION</H2 @@ -185,7 +181,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT2" ><A -NAME="AEN61" +NAME="AEN56" ></A ><H3 >Inetd Installation</H3 @@ -258,7 +254,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT2" ><A -NAME="AEN83" +NAME="AEN78" ></A ><H3 >Launching</H3 @@ -275,7 +271,7 @@ NAME="AEN83" ><DIV CLASS="REFSECT1" ><A -NAME="AEN87" +NAME="AEN82" ></A ><H2 >FILES</H2 @@ -312,12 +308,10 @@ CLASS="FILENAME" ></DT ><DD ><P ->This is the default location of the <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smb.conf</SPAN ->(5)</SPAN +>This is the default location of the <TT +CLASS="FILENAME" +>smb.conf(5) + </TT > server configuration file that swat edits. Other common places that systems install this file are <TT CLASS="FILENAME" @@ -335,7 +329,7 @@ CLASS="FILENAME" ><DIV CLASS="REFSECT1" ><A -NAME="AEN110" +NAME="AEN103" ></A ><H2 >WARNINGS</H2 @@ -343,12 +337,10 @@ NAME="AEN110" ><B CLASS="COMMAND" >swat</B -> will rewrite your <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smb.conf</SPAN ->(5)</SPAN +> will rewrite your <TT +CLASS="FILENAME" +>smb.conf + </TT > file. It will rearrange the entries and delete all comments, <TT CLASS="PARAMETER" @@ -369,17 +361,18 @@ CLASS="FILENAME" ><DIV CLASS="REFSECT1" ><A -NAME="AEN120" +NAME="AEN111" ></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="AEN123" +NAME="AEN114" ></A ><H2 >SEE ALSO</H2 @@ -387,24 +380,26 @@ NAME="AEN123" ><B CLASS="COMMAND" >inetd(5)</B ->, <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbd</SPAN ->(8)</SPAN ->, <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smb.conf</SPAN ->(5)</SPAN -></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 ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN133" +NAME="AEN121" ></A ><H2 >AUTHOR</H2 @@ -416,14 +411,14 @@ NAME="AEN133" ><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. The conversion to DocBook XML 4.2 for - Samba 3.0 was done by Alexander Bokovoy.</P + Samba 2.2 was done by Gerald Carter</P ></DIV ></BODY ></HTML diff --git a/docs/htmldocs/testparm.1.html b/docs/htmldocs/testparm.1.html index 52413a1c27..baf11bacac 100644 --- a/docs/htmldocs/testparm.1.html +++ b/docs/htmldocs/testparm.1.html @@ -1,11 +1,12 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"> <HTML ><HEAD ><TITLE >testparm</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"></HEAD +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"></HEAD ><BODY CLASS="REFENTRY" BGCOLOR="#FFFFFF" @@ -15,9 +16,7 @@ VLINK="#840084" ALINK="#0000FF" ><H1 ><A -NAME="TESTPARM.1" -></A ->testparm</H1 +NAME="TESTPARM">testparm</H1 ><DIV CLASS="REFNAMEDIV" ><A @@ -30,15 +29,13 @@ NAME="AEN5" ><DIV CLASS="REFSYNOPSISDIV" ><A -NAME="AEN8" -></A -><H2 +NAME="AEN8"><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" @@ -48,24 +45,19 @@ NAME="AEN18" ><H2 >DESCRIPTION</H2 ><P ->This tool is part of the <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->Samba</SPAN ->(7)</SPAN +>This tool is part of the <A +HREF="samba.7.html" +TARGET="_top" +> Samba</A > suite.</P ><P ><B CLASS="COMMAND" >testparm</B > is a very simple test program - to check an <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbd</SPAN ->(8)</SPAN + to check an <B +CLASS="COMMAND" +>smbd</B > configuration file for internal correctness. If this program reports no problems, you can use the configuration file with confidence that <B @@ -74,12 +66,9 @@ CLASS="COMMAND" </B > will successfully load the configuration file.</P ><P ->Note that this is <SPAN -CLASS="emphasis" -><I +>Note that this is <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 @@ -105,7 +94,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN37" +NAME="AEN33" ></A ><H2 >OPTIONS</H2 @@ -149,13 +138,12 @@ CLASS="REPLACEABLE" ><DD ><P >If this option is specified, testparm - 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 + will also output all options that were not used in + <TT +CLASS="FILENAME" +>smb.conf</TT +> and are thus set to + their defaults.</P ></DD ><DT >-t encoding</DT @@ -170,12 +158,9 @@ CLASS="REFENTRYTITLE" ><P >This is the name of the configuration file to check. If this parameter is not present then the - default <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smb.conf</SPAN ->(5)</SPAN + default <TT +CLASS="FILENAME" +>smb.conf</TT > file will be checked. </P ></DD @@ -199,12 +184,9 @@ CLASS="PARAMETER" >hosts deny</I ></TT > - parameters in the <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smb.conf</SPAN ->(5)</SPAN + parameters in the <TT +CLASS="FILENAME" +>smb.conf</TT > file to determine if the hostname with this IP address would be allowed access to the <B @@ -228,7 +210,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN87" +NAME="AEN77" ></A ><H2 >FILES</H2 @@ -238,22 +220,16 @@ NAME="AEN87" CLASS="VARIABLELIST" ><DL ><DT -><SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smb.conf</SPAN ->(5)</SPAN +><TT +CLASS="FILENAME" +>smb.conf</TT ></DT ><DD ><P >This is usually the name of the configuration - file used by <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbd</SPAN ->(8)</SPAN + file used by <B +CLASS="COMMAND" +>smbd</B >. </P ></DD @@ -263,7 +239,7 @@ CLASS="REFENTRYTITLE" ><DIV CLASS="REFSECT1" ><A -NAME="AEN100" +NAME="AEN86" ></A ><H2 >DIAGNOSTICS</H2 @@ -277,7 +253,7 @@ NAME="AEN100" ><DIV CLASS="REFSECT1" ><A -NAME="AEN103" +NAME="AEN89" ></A ><H2 >VERSION</H2 @@ -288,29 +264,33 @@ NAME="AEN103" ><DIV CLASS="REFSECT1" ><A -NAME="AEN106" +NAME="AEN92" ></A ><H2 >SEE ALSO</H2 ><P -><SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smb.conf</SPAN ->(5)</SPAN ->, <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbd</SPAN ->(8)</SPAN -></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 ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN115" +NAME="AEN99" ></A ><H2 >AUTHOR</H2 @@ -322,14 +302,14 @@ NAME="AEN115" ><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. The conversion to DocBook XML 4.2 - for Samba 3.0 was done by Alexander Bokovoy.</P + Samba 2.2 was done by Gerald Carter</P ></DIV ></BODY ></HTML diff --git a/docs/htmldocs/testprns.1.html b/docs/htmldocs/testprns.1.html index 07513566af..0225aad9d5 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.1" +NAME="TESTPRNS" ></A >testprns</H1 ><DIV @@ -47,12 +47,10 @@ NAME="AEN13" ><H2 >DESCRIPTION</H2 ><P ->This tool is part of the <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->Samba</SPAN ->(7)</SPAN +>This tool is part of the <A +HREF="samba.7.html" +TARGET="_top" +> Samba</A > suite.</P ><P ><B @@ -60,13 +58,14 @@ 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 <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbd</SPAN ->(8)</SPAN ->.</P + a service to be provided by <A +HREF="smbd.8.html" +TARGET="_top" +><B +CLASS="COMMAND" +> smbd(8)</B +></A +>. </P ><P >"Valid" in this context means "can be found in the printcap specified". This program is very stupid - so stupid in @@ -76,7 +75,7 @@ CLASS="REFENTRYTITLE" ><DIV CLASS="REFSECT1" ><A -NAME="AEN25" +NAME="AEN22" ></A ><H2 >OPTIONS</H2 @@ -104,12 +103,10 @@ CLASS="COMMAND" <B CLASS="COMMAND" >testprns</B -> finds the printer then <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbd</SPAN ->(8)</SPAN +> finds the printer then + <B +CLASS="COMMAND" +>smbd</B > should do so as well. </P ></DD ><DT @@ -132,7 +129,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN44" +NAME="AEN39" ></A ><H2 >FILES</H2 @@ -161,7 +158,7 @@ CLASS="FILENAME" ><DIV CLASS="REFSECT1" ><A -NAME="AEN53" +NAME="AEN48" ></A ><H2 >DIAGNOSTICS</H2 @@ -189,7 +186,7 @@ CLASS="FILENAME" ><DIV CLASS="REFSECT1" ><A -NAME="AEN60" +NAME="AEN55" ></A ><H2 >VERSION</H2 @@ -200,7 +197,7 @@ NAME="AEN60" ><DIV CLASS="REFSECT1" ><A -NAME="AEN63" +NAME="AEN58" ></A ><H2 >SEE ALSO</H2 @@ -209,24 +206,28 @@ NAME="AEN63" CLASS="FILENAME" >printcap(5)</TT >, - <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbd</SPAN ->(8)</SPAN ->, <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbclient</SPAN ->(1)</SPAN -></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 +> + </P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN73" +NAME="AEN66" ></A ><H2 >AUTHOR</H2 @@ -238,14 +239,14 @@ NAME="AEN73" ><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. The conversion to DocBook XML 4.2 - for Samba 3.0 was done by Alexander Bokovoy.</P + Samba 2.2 was done by Gerald Carter</P ></DIV ></BODY ></HTML diff --git a/docs/htmldocs/type.html b/docs/htmldocs/type.html index be7e722b2e..e3f09acc18 100644 --- a/docs/htmldocs/type.html +++ b/docs/htmldocs/type.html @@ -5,13 +5,14 @@ >Type of installation</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK REL="PREVIOUS" -TITLE="User information database" -HREF="passdb.html"><LINK +TITLE="LanMan and NT Password Encryption in Samba" +HREF="pwencrypt.html"><LINK REL="NEXT" TITLE="User and Share security level (for servers not in a domain)" HREF="securitylevels.html"></HEAD @@ -42,7 +43,7 @@ WIDTH="10%" ALIGN="left" VALIGN="bottom" ><A -HREF="passdb.html" +HREF="pwencrypt.html" ACCESSKEY="P" >Prev</A ></TD @@ -68,9 +69,7 @@ WIDTH="100%"></DIV ><DIV CLASS="PART" ><A -NAME="TYPE" -></A -><DIV +NAME="TYPE"><DIV CLASS="TITLEPAGE" ><H1 CLASS="TITLE" @@ -78,9 +77,7 @@ CLASS="TITLE" ><DIV CLASS="PARTINTRO" ><A -NAME="AEN678" -></A -><H1 +NAME="AEN531"><H1 >Introduction</H1 ><P >Samba can operate in various SMB networks. This part contains information on configuring samba @@ -94,238 +91,233 @@ CLASS="TOC" >Table of Contents</B ></DT ><DT ->4. <A +>5. <A HREF="securitylevels.html" >User and Share security level (for servers not in a domain)</A ></DT ><DT ->5. <A +>6. <A HREF="samba-pdc.html" ->Samba as a NT4 or Win2k Primary Domain Controller</A +>How to Configure Samba as a NT4 Primary Domain Controller</A ></DT ><DD ><DL ><DT ->5.1. <A -HREF="samba-pdc.html#AEN722" +>6.1. <A +HREF="samba-pdc.html#AEN575" >Prerequisite Reading</A ></DT ><DT ->5.2. <A -HREF="samba-pdc.html#AEN728" +>6.2. <A +HREF="samba-pdc.html#AEN581" >Background</A ></DT ><DT ->5.3. <A -HREF="samba-pdc.html#AEN767" +>6.3. <A +HREF="samba-pdc.html#AEN620" >Configuring the Samba Domain Controller</A ></DT ><DT ->5.4. <A -HREF="samba-pdc.html#AEN810" +>6.4. <A +HREF="samba-pdc.html#AEN663" >Creating Machine Trust Accounts and Joining Clients to the Domain</A ></DT ><DD ><DL ><DT ->5.4.1. <A -HREF="samba-pdc.html#AEN829" +>6.4.1. <A +HREF="samba-pdc.html#AEN682" >Manual Creation of Machine Trust Accounts</A ></DT ><DT ->5.4.2. <A -HREF="samba-pdc.html#AEN870" +>6.4.2. <A +HREF="samba-pdc.html#AEN723" >"On-the-Fly" Creation of Machine Trust Accounts</A ></DT ><DT ->5.4.3. <A -HREF="samba-pdc.html#AEN879" +>6.4.3. <A +HREF="samba-pdc.html#AEN732" >Joining the Client to the Domain</A ></DT ></DL ></DD ><DT ->5.5. <A -HREF="samba-pdc.html#AEN894" +>6.5. <A +HREF="samba-pdc.html#AEN747" >Common Problems and Errors</A ></DT ><DT ->5.6. <A -HREF="samba-pdc.html#AEN942" +>6.6. <A +HREF="samba-pdc.html#AEN795" >System Policies and Profiles</A ></DT ><DT ->5.7. <A -HREF="samba-pdc.html#AEN986" +>6.7. <A +HREF="samba-pdc.html#AEN839" >What other help can I get?</A ></DT ><DT ->5.8. <A -HREF="samba-pdc.html#AEN1100" +>6.8. <A +HREF="samba-pdc.html#AEN953" >Domain Control for Windows 9x/ME</A ></DT ><DD ><DL ><DT ->5.8.1. <A -HREF="samba-pdc.html#AEN1126" +>6.8.1. <A +HREF="samba-pdc.html#AEN979" >Configuration Instructions: Network Logons</A ></DT ><DT ->5.8.2. <A -HREF="samba-pdc.html#AEN1145" +>6.8.2. <A +HREF="samba-pdc.html#AEN998" >Configuration Instructions: Setting up Roaming User Profiles</A ></DT ></DL ></DD ><DT ->5.9. <A -HREF="samba-pdc.html#AEN1238" ->DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba</A +>6.9. <A +HREF="samba-pdc.html#AEN1091" +>DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba</A ></DT ></DL ></DD ><DT ->6. <A +>7. <A HREF="samba-bdc.html" >How to Act as a Backup Domain Controller in a Purely Samba Controlled Domain</A ></DT ><DD ><DL ><DT ->6.1. <A -HREF="samba-bdc.html#AEN1274" +>7.1. <A +HREF="samba-bdc.html#AEN1127" >Prerequisite Reading</A ></DT ><DT ->6.2. <A -HREF="samba-bdc.html#AEN1278" +>7.2. <A +HREF="samba-bdc.html#AEN1131" >Background</A ></DT ><DT ->6.3. <A -HREF="samba-bdc.html#AEN1286" +>7.3. <A +HREF="samba-bdc.html#AEN1139" >What qualifies a Domain Controller on the network?</A ></DT ><DD ><DL ><DT ->6.3.1. <A -HREF="samba-bdc.html#AEN1289" +>7.3.1. <A +HREF="samba-bdc.html#AEN1142" >How does a Workstation find its domain controller?</A ></DT ><DT ->6.3.2. <A -HREF="samba-bdc.html#AEN1292" +>7.3.2. <A +HREF="samba-bdc.html#AEN1145" >When is the PDC needed?</A ></DT ></DL ></DD ><DT ->6.4. <A -HREF="samba-bdc.html#AEN1295" ->Can Samba be a Backup Domain Controller to an NT PDC?</A +>7.4. <A +HREF="samba-bdc.html#AEN1148" +>Can Samba be a Backup Domain Controller?</A ></DT ><DT ->6.5. <A -HREF="samba-bdc.html#AEN1300" +>7.5. <A +HREF="samba-bdc.html#AEN1152" >How do I set up a Samba BDC?</A ></DT ><DD ><DL ><DT ->6.5.1. <A -HREF="samba-bdc.html#AEN1317" +>7.5.1. <A +HREF="samba-bdc.html#AEN1169" >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 ->7. <A +>8. <A HREF="ads.html" >Samba as a ADS domain member</A ></DT ><DD ><DL ><DT ->7.1. <A -HREF="ads.html#AEN1339" +>8.1. <A +HREF="ads.html#AEN1187" >Installing the required packages for Debian</A ></DT ><DT ->7.2. <A -HREF="ads.html#AEN1346" +>8.2. <A +HREF="ads.html#AEN1193" >Installing the required packages for RedHat</A ></DT ><DT ->7.3. <A -HREF="ads.html#AEN1356" +>8.3. <A +HREF="ads.html#AEN1202" >Compile Samba</A ></DT ><DT ->7.4. <A -HREF="ads.html#AEN1371" +>8.4. <A +HREF="ads.html#AEN1217" >Setup your /etc/krb5.conf</A ></DT ><DT ->7.5. <A -HREF="ads.html#AEN1381" +>8.5. <A +HREF="ads.html#AEN1227" >Create the computer account</A ></DT ><DD ><DL ><DT ->7.5.1. <A -HREF="ads.html#AEN1385" +>8.5.1. <A +HREF="ads.html#AEN1231" >Possible errors</A ></DT ></DL ></DD ><DT ->7.6. <A -HREF="ads.html#AEN1393" +>8.6. <A +HREF="ads.html#AEN1243" >Test your server setup</A ></DT ><DT ->7.7. <A -HREF="ads.html#AEN1398" +>8.7. <A +HREF="ads.html#AEN1248" >Testing with smbclient</A ></DT ><DT ->7.8. <A -HREF="ads.html#AEN1401" +>8.8. <A +HREF="ads.html#AEN1251" >Notes</A ></DT ></DL ></DD ><DT ->8. <A +>9. <A HREF="domain-security.html" ->Samba as a NT4 or Win2k domain member</A +>Samba as a NT4 domain member</A ></DT ><DD ><DL ><DT ->8.1. <A -HREF="domain-security.html#AEN1423" ->Joining an NT Domain with Samba 3.0</A +>9.1. <A +HREF="domain-security.html#AEN1273" +>Joining an NT Domain with Samba 2.2</A ></DT ><DT ->8.2. <A -HREF="domain-security.html#AEN1478" +>9.2. <A +HREF="domain-security.html#AEN1337" >Samba and Windows 2000 Domains</A ></DT ><DT ->8.3. <A -HREF="domain-security.html#AEN1481" +>9.3. <A +HREF="domain-security.html#AEN1342" >Why is this better than security = server?</A ></DT ></DL @@ -350,7 +342,7 @@ WIDTH="33%" ALIGN="left" VALIGN="top" ><A -HREF="passdb.html" +HREF="pwencrypt.html" ACCESSKEY="P" >Prev</A ></TD @@ -378,7 +370,7 @@ ACCESSKEY="N" WIDTH="33%" ALIGN="left" VALIGN="top" ->User information database</TD +>LanMan and NT Password Encryption in Samba</TD ><TD WIDTH="34%" ALIGN="center" diff --git a/docs/htmldocs/unix-permissions.html b/docs/htmldocs/unix-permissions.html index 71198ecaa6..f29d450e6d 100644 --- a/docs/htmldocs/unix-permissions.html +++ b/docs/htmldocs/unix-permissions.html @@ -5,7 +5,8 @@ >UNIX Permission Bits and Windows NT Access Control Lists</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -73,17 +74,13 @@ WIDTH="100%"></DIV CLASS="CHAPTER" ><H1 ><A -NAME="UNIX-PERMISSIONS" -></A ->Chapter 10. UNIX Permission Bits and Windows NT Access Control Lists</H1 +NAME="UNIX-PERMISSIONS">Chapter 11. UNIX Permission Bits and Windows NT Access Control Lists</H1 ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1744" -></A ->10.1. Viewing and changing UNIX permissions using the NT +NAME="AEN1605">11.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 @@ -94,15 +91,33 @@ NAME="AEN1744" 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="AEN1748" -></A ->10.2. How to view file security on a Samba share</H1 +NAME="AEN1614">11.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 @@ -170,9 +185,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1759" -></A ->10.3. Viewing file ownership</H1 +NAME="AEN1625">11.3. Viewing file ownership</H1 ><P >Clicking on the <B CLASS="COMMAND" @@ -264,9 +277,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1779" -></A ->10.4. Viewing file or directory permissions</H1 +NAME="AEN1645">11.4. Viewing file or directory permissions</H1 ><P >The third button is the <B CLASS="COMMAND" @@ -326,9 +337,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1794" -></A ->10.4.1. File Permissions</H2 +NAME="AEN1660">11.4.1. File Permissions</H2 ><P >The standard UNIX user/group/world triple and the corresponding "read", "write", "execute" permissions @@ -388,9 +397,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1808" -></A ->10.4.2. Directory Permissions</H2 +NAME="AEN1674">11.4.2. Directory Permissions</H2 ><P >Directories on an NT NTFS file system have two different sets of permissions. The first set of permissions @@ -420,9 +427,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1815" -></A ->10.5. Modifying file or directory permissions</H1 +NAME="AEN1681">11.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 @@ -518,9 +523,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1837" -></A ->10.6. Interaction with the standard Samba create mask +NAME="AEN1703">11.6. Interaction with the standard Samba create mask parameters</H1 ><P >Note that with Samba 2.0.5 there are four new parameters @@ -795,9 +798,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1901" -></A ->10.7. Interaction with the standard Samba file attribute +NAME="AEN1767">11.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 0e39297ebb..11934ae47c 100644 --- a/docs/htmldocs/vfs.html +++ b/docs/htmldocs/vfs.html @@ -5,7 +5,8 @@ >Stackable VFS modules</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -13,11 +14,11 @@ REL="UP" TITLE="Optional configuration" HREF="optional.html"><LINK REL="PREVIOUS" -TITLE="Improved browsing in samba" -HREF="improved-browsing.html"><LINK +TITLE="Passdb XML plugin" +HREF="pdb-xml.html"><LINK REL="NEXT" -TITLE="Access Samba source code via CVS" -HREF="cvs-access.html"></HEAD +TITLE="Storing Samba's User/Machine Account information in an LDAP Directory" +HREF="samba-ldap-howto.html"></HEAD ><BODY CLASS="CHAPTER" BGCOLOR="#FFFFFF" @@ -45,7 +46,7 @@ WIDTH="10%" ALIGN="left" VALIGN="bottom" ><A -HREF="improved-browsing.html" +HREF="pdb-xml.html" ACCESSKEY="P" >Prev</A ></TD @@ -59,7 +60,7 @@ WIDTH="10%" ALIGN="right" VALIGN="bottom" ><A -HREF="cvs-access.html" +HREF="samba-ldap-howto.html" ACCESSKEY="N" >Next</A ></TD @@ -72,17 +73,13 @@ WIDTH="100%"></DIV CLASS="CHAPTER" ><H1 ><A -NAME="VFS" -></A ->Chapter 16. Stackable VFS modules</H1 +NAME="VFS">Chapter 18. Stackable VFS modules</H1 ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2855" -></A ->16.1. Introduction and configuration</H1 +NAME="AEN2640">18.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. @@ -121,17 +118,13 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2864" -></A ->16.2. Included modules</H1 +NAME="AEN2649">18.2. Included modules</H1 ><DIV CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2866" -></A ->16.2.1. audit</H2 +NAME="AEN2651">18.2.1. audit</H2 ><P >A simple module to audit file access to the syslog facility. The following operations are logged: @@ -167,9 +160,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2874" -></A ->16.2.2. recycle</H2 +NAME="AEN2659">18.2.2. recycle</H2 ><P >A recycle-bin like modules. When used any unlink call will be intercepted and files moved to the recycle @@ -238,9 +229,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2911" -></A ->16.2.3. netatalk</H2 +NAME="AEN2696">18.2.3. netatalk</H2 ><P >A netatalk module, that will ease co-existence of samba and netatalk file sharing services.</P @@ -271,9 +260,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2918" -></A ->16.3. VFS modules available elsewhere</H1 +NAME="AEN2703">18.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 @@ -287,9 +274,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2922" -></A ->16.3.1. DatabaseFS</H2 +NAME="AEN2707">18.3.1. DatabaseFS</H2 ><P >URL: <A HREF="http://www.css.tayloru.edu/~elorimer/databasefs/index.php" @@ -321,9 +306,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2930" -></A ->16.3.2. vscan</H2 +NAME="AEN2715">18.3.2. vscan</H2 ><P >URL: <A HREF="http://www.openantivirus.org/" @@ -355,7 +338,7 @@ WIDTH="33%" ALIGN="left" VALIGN="top" ><A -HREF="improved-browsing.html" +HREF="pdb-xml.html" ACCESSKEY="P" >Prev</A ></TD @@ -373,7 +356,7 @@ WIDTH="33%" ALIGN="right" VALIGN="top" ><A -HREF="cvs-access.html" +HREF="samba-ldap-howto.html" ACCESSKEY="N" >Next</A ></TD @@ -383,7 +366,7 @@ ACCESSKEY="N" WIDTH="33%" ALIGN="left" VALIGN="top" ->Improved browsing in samba</TD +>Passdb XML plugin</TD ><TD WIDTH="34%" ALIGN="center" @@ -397,7 +380,7 @@ ACCESSKEY="U" WIDTH="33%" ALIGN="right" VALIGN="top" ->Access Samba source code via CVS</TD +>Storing Samba's User/Machine Account information in an LDAP Directory</TD ></TR ></TABLE ></DIV diff --git a/docs/htmldocs/vfstest.1.html b/docs/htmldocs/vfstest.1.html index 56c409288a..1fd7880805 100644 --- a/docs/htmldocs/vfstest.1.html +++ b/docs/htmldocs/vfstest.1.html @@ -1,11 +1,12 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"> <HTML ><HEAD ><TITLE >vfstest</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"></HEAD +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"></HEAD ><BODY CLASS="REFENTRY" BGCOLOR="#FFFFFF" @@ -15,9 +16,7 @@ VLINK="#840084" ALINK="#0000FF" ><H1 ><A -NAME="VFSTEST.1" -></A ->vfstest</H1 +NAME="VFSTEST">vfstest</H1 ><DIV CLASS="REFNAMEDIV" ><A @@ -29,15 +28,13 @@ NAME="AEN5" ><DIV CLASS="REFSYNOPSISDIV" ><A -NAME="AEN8" -></A -><H2 +NAME="AEN8"><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" @@ -47,12 +44,10 @@ NAME="AEN15" ><H2 >DESCRIPTION</H2 ><P ->This tool is part of the <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->Samba</SPAN ->(7)</SPAN +>This tool is part of the <A +HREF="samba.7.html" +TARGET="_top" +> Samba</A > suite.</P ><P ><B @@ -67,7 +62,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN23" +NAME="AEN21" ></A ><H2 >OPTIONS</H2 @@ -149,17 +144,14 @@ CLASS="CONSTANT" ><DIV CLASS="REFSECT1" ><A -NAME="AEN50" +NAME="AEN48" ></A ><H2 >COMMANDS</H2 ><P -><SPAN -CLASS="emphasis" ><I CLASS="EMPHASIS" >VFS COMMANDS</I -></SPAN ></P ><P ></P @@ -168,14 +160,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 @@ -183,7 +175,7 @@ CLASS="COMMAND" ><P ><B CLASS="COMMAND" ->showdata [<offset> <len>]</B +>showdata [<offset> <len>]</B > - Show data currently in data buffer </P ></LI @@ -420,12 +412,9 @@ CLASS="COMMAND" ></LI ></UL ><P -><SPAN -CLASS="emphasis" ><I CLASS="EMPHASIS" >GENERAL COMMANDS</I -></SPAN ></P ><P ></P @@ -434,21 +423,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 @@ -470,7 +459,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN181" +NAME="AEN179" ></A ><H2 >VERSION</H2 @@ -481,7 +470,7 @@ NAME="AEN181" ><DIV CLASS="REFSECT1" ><A -NAME="AEN184" +NAME="AEN182" ></A ><H2 >AUTHOR</H2 diff --git a/docs/htmldocs/wbinfo.1.html b/docs/htmldocs/wbinfo.1.html index cf46eca0ef..a8aa065eed 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.1" +NAME="WBINFO" ></A >wbinfo</H1 ><DIV @@ -47,32 +47,28 @@ NAME="AEN27" ><H2 >DESCRIPTION</H2 ><P ->This tool is part of the <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->Samba</SPAN ->(7)</SPAN +>This tool is part of the <A +HREF="samba.7.html" +TARGET="_top" +> Samba</A > suite.</P ><P >The <B CLASS="COMMAND" >wbinfo</B > program queries and returns information - created and used by the <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->winbindd</SPAN ->(8)</SPAN + created and used by the <A +HREF="winbindd.8.html" +TARGET="_top" +><B +CLASS="COMMAND" +> winbindd(8)</B +></A > daemon. </P ><P ->The <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->winbindd</SPAN ->(8)</SPAN +>The <B +CLASS="COMMAND" +>winbindd(8)</B > daemon must be configured and running for the <B CLASS="COMMAND" @@ -83,7 +79,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN43" +NAME="AEN38" ></A ><H2 >OPTIONS</H2 @@ -97,43 +93,33 @@ CLASS="VARIABLELIST" ><DD ><P >This option will list all users available - in the Windows NT domain for which the <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->winbindd</SPAN ->(8)</SPAN + in the Windows NT domain for which the <B +CLASS="COMMAND" +>winbindd(8) + </B > 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 <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->winbindd</SPAN ->(8)</SPAN -> - .</P + user ids to any users that have not already been seen by + <B +CLASS="COMMAND" +>winbindd(8)</B +>.</P ></DD ><DT >-g</DT ><DD ><P >This option will list all groups available - in the Windows NT domain for which the <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->Samba</SPAN ->(7)</SPAN + in the Windows NT domain for which the <B +CLASS="COMMAND" +>winbindd(8) + </B > 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 <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->winbindd</SPAN ->(8)</SPAN + group ids to any groups that have not already been seen by + <B +CLASS="COMMAND" +>winbindd(8)</B >. </P ></DD ><DT @@ -146,12 +132,9 @@ CLASS="PARAMETER" >-N</I ></TT > option - queries <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->winbindd</SPAN ->(8)</SPAN + queries <B +CLASS="COMMAND" +>winbindd(8)</B > to query the WINS server for the IP address associated with the NetBIOS name specified by the <TT @@ -172,12 +155,9 @@ CLASS="PARAMETER" >-I</I ></TT > option - queries <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->winbindd</SPAN ->(8)</SPAN + queries <B +CLASS="COMMAND" +>winbindd(8)</B > to send a node status request to get the NetBIOS name associated with the IP address specified by the <TT @@ -198,28 +178,22 @@ CLASS="PARAMETER" >-n</I ></TT > option - queries <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->winbindd</SPAN ->(8)</SPAN + queries <B +CLASS="COMMAND" +>winbindd(8)</B > 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 <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smb.conf</SPAN ->(5)</SPAN -> <TT + domain used is the one specified in the <TT +CLASS="FILENAME" +>smb.conf</TT +> + <TT CLASS="PARAMETER" ><I ->workgroup - </I +>workgroup</I ></TT > parameter. </P ></DD @@ -264,12 +238,9 @@ CLASS="PARAMETER" ><DD ><P >Convert a SID to a UNIX user id. If the SID - does not correspond to a UNIX user mapped by <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->winbindd</SPAN ->(8)</SPAN + does not correspond to a UNIX user mapped by <B +CLASS="COMMAND" +> winbindd(8)</B > then the operation will fail. </P ></DD ><DT @@ -277,14 +248,10 @@ CLASS="REFENTRYTITLE" ><DD ><P >Convert a SID to a UNIX group id. If the SID - 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 + does not correspond to a UNIX group mapped by <B +CLASS="COMMAND" +> winbindd(8)</B +> then the operation will fail. </P ></DD ><DT >-t</DT @@ -299,12 +266,9 @@ CLASS="REFENTRYTITLE" ><DD ><P >Produce a list of domains trusted by the - Windows NT server <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->winbindd</SPAN ->(8)</SPAN + Windows NT server <B +CLASS="COMMAND" +>winbindd(8)</B > contacts when resolving names. This list does not include the Windows NT domain the server is a Primary Domain Controller for. @@ -344,18 +308,16 @@ CLASS="REFENTRYTITLE" ><DIV CLASS="REFSECT1" ><A -NAME="AEN147" +NAME="AEN120" ></A ><H2 >EXIT STATUS</H2 ><P >The wbinfo program returns 0 if the operation - succeeded, or 1 if the operation failed. If the <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->winbindd</SPAN ->(8)</SPAN + succeeded, or 1 if the operation failed. If the <B +CLASS="COMMAND" +>winbindd(8) + </B > daemon is not working <B CLASS="COMMAND" >wbinfo</B @@ -365,7 +327,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN154" +NAME="AEN125" ></A ><H2 >VERSION</H2 @@ -376,23 +338,25 @@ NAME="AEN154" ><DIV CLASS="REFSECT1" ><A -NAME="AEN157" +NAME="AEN128" ></A ><H2 >SEE ALSO</H2 ><P -><SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->winbindd</SPAN ->(8)</SPAN +><A +HREF="winbindd.8.html" +TARGET="_top" +><B +CLASS="COMMAND" +>winbindd(8)</B +> + </A ></P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN163" +NAME="AEN133" ></A ><H2 >AUTHOR</H2 @@ -412,8 +376,7 @@ CLASS="COMMAND" were written by Tim Potter.</P ><P >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 + by Gerald Carter</P ></DIV ></BODY ></HTML diff --git a/docs/htmldocs/winbind.html b/docs/htmldocs/winbind.html index d587696817..1558512a61 100644 --- a/docs/htmldocs/winbind.html +++ b/docs/htmldocs/winbind.html @@ -5,7 +5,8 @@ >Unified Logons between Windows NT and UNIX using Winbind</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -16,8 +17,8 @@ REL="PREVIOUS" TITLE="Printing Support" HREF="printing.html"><LINK REL="NEXT" -TITLE="Improved browsing in samba" -HREF="improved-browsing.html"></HEAD +TITLE="Passdb MySQL plugin" +HREF="pdb-mysql.html"></HEAD ><BODY CLASS="CHAPTER" BGCOLOR="#FFFFFF" @@ -59,7 +60,7 @@ WIDTH="10%" ALIGN="right" VALIGN="bottom" ><A -HREF="improved-browsing.html" +HREF="pdb-mysql.html" ACCESSKEY="N" >Next</A ></TD @@ -72,17 +73,13 @@ WIDTH="100%"></DIV CLASS="CHAPTER" ><H1 ><A -NAME="WINBIND" -></A ->Chapter 14. Unified Logons between Windows NT and UNIX using Winbind</H1 +NAME="WINBIND">Chapter 15. Unified Logons between Windows NT and UNIX using Winbind</H1 ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2360" -></A ->14.1. Abstract</H1 +NAME="AEN2225">15.1. Abstract</H1 ><P >Integration of UNIX and Microsoft Windows NT through a unified logon has been considered a "holy grail" in heterogeneous @@ -107,9 +104,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2364" -></A ->14.2. Introduction</H1 +NAME="AEN2229">15.2. Introduction</H1 ><P >It is well known that UNIX and Microsoft Windows NT have different models for representing user and group information and @@ -161,9 +156,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2377" -></A ->14.3. What Winbind Provides</H1 +NAME="AEN2242">15.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 @@ -203,9 +196,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2384" -></A ->14.3.1. Target Uses</H2 +NAME="AEN2249">15.3.1. Target Uses</H2 ><P >Winbind is targeted at organizations that have an existing NT based domain infrastructure into which they wish @@ -227,9 +218,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2388" -></A ->14.4. How Winbind Works</H1 +NAME="AEN2253">15.4. How Winbind Works</H1 ><P >The winbind system is designed around a client/server architecture. A long running <B @@ -247,11 +236,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2393" -></A ->14.4.1. Microsoft Remote Procedure Calls</H2 +NAME="AEN2258">15.4.1. Microsoft Remote Procedure Calls</H2 ><P ->Over the last few years, efforts have been underway +>Over the last two 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 @@ -273,28 +260,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -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 +NAME="AEN2262">15.4.2. 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 @@ -372,9 +338,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2416" -></A ->14.4.4. Pluggable Authentication Modules</H2 +NAME="AEN2278">15.4.3. Pluggable Authentication Modules</H2 ><P >Pluggable Authentication Modules, also known as PAM, is a system for abstracting authentication and authorization @@ -421,9 +385,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2424" -></A ->14.4.5. User and Group ID Allocation</H2 +NAME="AEN2286">15.4.4. 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 @@ -447,9 +409,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2428" -></A ->14.4.6. Result Caching</H2 +NAME="AEN2290">15.4.5. 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 @@ -470,9 +430,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2431" -></A ->14.5. Installation and Configuration</H1 +NAME="AEN2293">15.5. Installation and Configuration</H1 ><P >Many thanks to John Trostel <A HREF="mailto:jtrostel@snapserver.com" @@ -497,9 +455,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2438" -></A ->14.5.1. Introduction</H2 +NAME="AEN2300">15.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 @@ -556,9 +512,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2451" -></A ->14.5.2. Requirements</H2 +NAME="AEN2313">15.5.2. Requirements</H2 ><P >If you have a samba configuration file that you are currently using... <SPAN @@ -626,9 +580,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2465" -></A ->14.5.3. Testing Things Out</H2 +NAME="AEN2327">15.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 @@ -671,9 +623,7 @@ CLASS="SECT3" ><H3 CLASS="SECT3" ><A -NAME="AEN2476" -></A ->14.5.3.1. Configure and compile SAMBA</H3 +NAME="AEN2338">15.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 @@ -707,7 +657,7 @@ CLASS="PROMPT" >root#</TT > <B CLASS="COMMAND" ->./configure</B +>./configure --with-winbind</B > <TT CLASS="PROMPT" @@ -737,9 +687,7 @@ CLASS="SECT3" ><H3 CLASS="SECT3" ><A -NAME="AEN2495" -></A ->14.5.3.2. Configure <TT +NAME="AEN2357">15.5.3.2. Configure <TT CLASS="FILENAME" >nsswitch.conf</TT > and the @@ -842,9 +790,7 @@ CLASS="SECT3" ><H3 CLASS="SECT3" ><A -NAME="AEN2528" -></A ->14.5.3.3. Configure smb.conf</H3 +NAME="AEN2390">15.5.3.3. Configure smb.conf</H3 ><P >Several parameters are needed in the smb.conf file to control the behavior of <B @@ -869,7 +815,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" @@ -917,9 +863,7 @@ CLASS="SECT3" ><H3 CLASS="SECT3" ><A -NAME="AEN2544" -></A ->14.5.3.4. Join the SAMBA server to the PDC domain</H3 +NAME="AEN2406">15.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 @@ -941,7 +885,7 @@ CLASS="PROMPT" >root#</TT > <B CLASS="COMMAND" ->/usr/local/samba/bin/net join -S PDC -U Administrator</B +>/usr/local/samba/bin/net rpc join -S PDC -U Administrator</B ></P ><P >The proper response to the command should be: "Joined the domain @@ -963,9 +907,7 @@ CLASS="SECT3" ><H3 CLASS="SECT3" ><A -NAME="AEN2555" -></A ->14.5.3.5. Start up the winbindd daemon and test it!</H3 +NAME="AEN2417">15.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 @@ -1086,17 +1028,13 @@ CLASS="SECT3" ><H3 CLASS="SECT3" ><A -NAME="AEN2591" -></A ->14.5.3.6. Fix the init.d startup scripts</H3 +NAME="AEN2453">15.5.3.6. Fix the init.d startup scripts</H3 ><DIV CLASS="SECT4" ><H4 CLASS="SECT4" ><A -NAME="AEN2593" -></A ->14.5.3.6.1. Linux</H4 +NAME="AEN2455">15.5.3.6.1. Linux</H4 ><P >The <B CLASS="COMMAND" @@ -1153,7 +1091,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 @@ -1179,7 +1117,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 @@ -1190,9 +1128,7 @@ CLASS="SECT4" ><H4 CLASS="SECT4" ><A -NAME="AEN2610" -></A ->14.5.3.6.2. Solaris</H4 +NAME="AEN2472">15.5.3.6.2. Solaris</H4 ><P >On solaris, you need to modify the <TT @@ -1221,7 +1157,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 @@ -1261,9 +1197,7 @@ CLASS="SECT4" ><H4 CLASS="SECT4" ><A -NAME="AEN2617" -></A ->14.5.3.6.3. Restarting</H4 +NAME="AEN2479">15.5.3.6.3. Restarting</H4 ><P >If you restart the <B CLASS="COMMAND" @@ -1285,9 +1219,7 @@ CLASS="SECT3" ><H3 CLASS="SECT3" ><A -NAME="AEN2623" -></A ->14.5.3.7. Configure Winbind and PAM</H3 +NAME="AEN2485">15.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 @@ -1343,9 +1275,7 @@ CLASS="SECT4" ><H4 CLASS="SECT4" ><A -NAME="AEN2640" -></A ->14.5.3.7.1. Linux/FreeBSD-specific PAM configuration</H4 +NAME="AEN2502">15.5.3.7.1. Linux/FreeBSD-specific PAM configuration</H4 ><P >The <TT CLASS="FILENAME" @@ -1472,9 +1402,7 @@ CLASS="SECT4" ><H4 CLASS="SECT4" ><A -NAME="AEN2673" -></A ->14.5.3.7.2. Solaris-specific configuration</H4 +NAME="AEN2535">15.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 @@ -1548,7 +1476,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 and try connecting through your application that you +>Now restart your Samba & try connecting through your application that you configured in the pam.conf.</P ></DIV ></DIV @@ -1559,9 +1487,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2680" -></A ->14.6. Limitations</H1 +NAME="AEN2542">15.6. Limitations</H1 ><P >Winbind has a number of limitations in its current released version that we hope to overcome in future @@ -1572,7 +1498,7 @@ NAME="AEN2680" ><LI ><P >Winbind is currently only available for - the Linux, Solaris and IRIX operating systems, although ports to other operating + the Linux operating system, 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 @@ -1591,8 +1517,7 @@ NAME="AEN2680" ><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, this is - instead up to the PDC to enforce.</P + that may be been set for Windows NT users.</P ></LI ></UL ></DIV @@ -1601,9 +1526,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2690" -></A ->14.7. Conclusion</H1 +NAME="AEN2552">15.7. Conclusion</H1 ><P >The winbind system, through the use of the Name Service Switch, Pluggable Authentication Modules, and appropriate @@ -1647,7 +1570,7 @@ WIDTH="33%" ALIGN="right" VALIGN="top" ><A -HREF="improved-browsing.html" +HREF="pdb-mysql.html" ACCESSKEY="N" >Next</A ></TD @@ -1671,7 +1594,7 @@ ACCESSKEY="U" WIDTH="33%" ALIGN="right" VALIGN="top" ->Improved browsing in samba</TD +>Passdb MySQL plugin</TD ></TR ></TABLE ></DIV diff --git a/docs/htmldocs/winbindd.8.html b/docs/htmldocs/winbindd.8.html index dba9988e30..fb8c9c0458 100644 --- a/docs/htmldocs/winbindd.8.html +++ b/docs/htmldocs/winbindd.8.html @@ -1,11 +1,12 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"> <HTML ><HEAD ><TITLE >winbindd</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"></HEAD +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"></HEAD ><BODY CLASS="REFENTRY" BGCOLOR="#FFFFFF" @@ -15,9 +16,7 @@ VLINK="#840084" ALINK="#0000FF" ><H1 ><A -NAME="WINBINDD.8" -></A ->winbindd</H1 +NAME="WINBINDD">winbindd</H1 ><DIV CLASS="REFNAMEDIV" ><A @@ -30,15 +29,13 @@ NAME="AEN5" ><DIV CLASS="REFSYNOPSISDIV" ><A -NAME="AEN8" -></A -><H2 +NAME="AEN8"><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" @@ -48,12 +45,10 @@ NAME="AEN18" ><H2 >DESCRIPTION</H2 ><P ->This program is part of the <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->Samba</SPAN ->(7)</SPAN +>This program is part of the <A +HREF="samba.7.html" +TARGET="_top" +> Samba</A > suite.</P ><P ><B @@ -171,11 +166,22 @@ CLASS="FILENAME" CLASS="FILENAME" >/etc/group</TT > and then from the - Windows NT server. -<PRE + Windows NT server. </P +><P +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="100%" +><TR +><TD +><PRE CLASS="PROGRAMLISTING" >passwd: files winbind -group: files winbind</PRE +group: files winbind + </PRE +></TD +></TR +></TABLE ></P ><P >The following simple configuration in the @@ -192,7 +198,7 @@ CLASS="FILENAME" ><DIV CLASS="REFSECT1" ><A -NAME="AEN62" +NAME="AEN61" ></A ><H2 >OPTIONS</H2 @@ -304,12 +310,9 @@ CLASS="COMMAND" ><DD ><P >Specifies the location of the all-important - <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smb.conf</SPAN ->(5)</SPAN + <TT +CLASS="FILENAME" +>smb.conf</TT > file. </P ></DD ></DL @@ -318,7 +321,7 @@ CLASS="REFENTRYTITLE" ><DIV CLASS="REFSECT1" ><A -NAME="AEN106" +NAME="AEN103" ></A ><H2 >NAME AND ID RESOLUTION</H2 @@ -349,7 +352,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN112" +NAME="AEN109" ></A ><H2 >CONFIGURATION</H2 @@ -358,12 +361,10 @@ NAME="AEN112" CLASS="COMMAND" >winbindd</B > daemon - is done through configuration parameters in the <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smb.conf</SPAN ->(5)</SPAN + is done through configuration parameters in the <TT +CLASS="FILENAME" +>smb.conf(5) + </TT > file. All parameters should be specified in the [global] section of smb.conf. </P ><P @@ -491,7 +492,7 @@ CLASS="PARAMETER" ><DIV CLASS="REFSECT1" ><A -NAME="AEN156" +NAME="AEN151" ></A ><H2 >EXAMPLE SETUP</H2 @@ -504,37 +505,60 @@ NAME="AEN156" CLASS="FILENAME" >/etc/nsswitch.conf</TT > put the - following: -<PRE + following:</P +><P +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="100%" +><TR +><TD +><PRE CLASS="PROGRAMLISTING" >passwd: files winbind -group: files winbind</PRE +group: files winbind + </PRE +></TD +></TR +></TABLE ></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: -<PRE +> lines with something like this: </P +><P +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="100%" +><TR +><TD +><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 +auth required /lib/security/pam_pwdb.so use_first_pass shadow nullok + </PRE +></TD +></TR +></TABLE ></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 @@ -557,7 +581,8 @@ CLASS="COMMAND" ><P ><B CLASS="COMMAND" ->net join -S PDC -U Administrator</B +>smbpasswd -j DOMAIN -r PDC -U + Administrator</B ></P ><P >The username after the <TT @@ -567,7 +592,8 @@ CLASS="PARAMETER" ></TT > can be any Domain user that has administrator privileges on the machine. - Substitute the name or IP of your PDC for "PDC".</P + Substitute your domain name for "DOMAIN" and the name of your PDC + for "PDC".</P ><P >Next copy <TT CLASS="FILENAME" @@ -578,9 +604,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 @@ -598,15 +624,19 @@ CLASS="FILENAME" >/lib/libnss_winbind.so.1</TT >.</P ><P ->Finally, setup a <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smb.conf</SPAN ->(5)</SPAN +>Finally, setup a <TT +CLASS="FILENAME" +>smb.conf</TT > containing directives like the - following: -<PRE + following: </P +><P +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="100%" +><TR +><TD +><PRE CLASS="PROGRAMLISTING" >[global] winbind separator = + @@ -617,7 +647,11 @@ CLASS="PROGRAMLISTING" winbind gid = 10000-20000 workgroup = DOMAIN security = domain - password server = *</PRE + password server = * + </PRE +></TD +></TR +></TABLE ></P ><P >Now start winbindd and you should find that your user and @@ -636,7 +670,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN194" +NAME="AEN190" ></A ><H2 >NOTES</H2 @@ -647,12 +681,9 @@ CLASS="COMMAND" >winbindd</B >: </P ><P -><SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->nmbd</SPAN ->(8)</SPAN +><B +CLASS="COMMAND" +>nmbd</B > must be running on the local machine for <B CLASS="COMMAND" @@ -660,8 +691,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 @@ -697,7 +728,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN212" +NAME="AEN206" ></A ><H2 >SIGNALS</H2 @@ -716,14 +747,11 @@ CLASS="VARIABLELIST" >SIGHUP</DT ><DD ><P ->Reload the <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smb.conf</SPAN ->(5)</SPAN -> file and - apply any parameter changes to the running +>Reload the <TT +CLASS="FILENAME" +>smb.conf(5)</TT +> + 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 @@ -751,7 +779,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN231" +NAME="AEN223" ></A ><H2 >FILES</H2 @@ -827,7 +855,7 @@ CLASS="FILENAME" ><DIV CLASS="REFSECT1" ><A -NAME="AEN260" +NAME="AEN252" ></A ><H2 >VERSION</H2 @@ -838,7 +866,7 @@ NAME="AEN260" ><DIV CLASS="REFSECT1" ><A -NAME="AEN263" +NAME="AEN255" ></A ><H2 >SEE ALSO</H2 @@ -846,30 +874,27 @@ NAME="AEN263" ><TT CLASS="FILENAME" >nsswitch.conf(5)</TT ->, <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 +>, + <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 ></P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN276" +NAME="AEN262" ></A ><H2 >AUTHOR</H2 @@ -885,12 +910,11 @@ 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. The conversion to DocBook XML 4.2 for - Samba 3.0 was done by Alexander Bokovoy.</P + by Gerald Carter</P ></DIV ></BODY ></HTML |