diff options
Diffstat (limited to 'docs/htmldocs')
| -rw-r--r-- | docs/htmldocs/Samba-HOWTO-Collection.html | 1014 | ||||
| -rw-r--r-- | docs/htmldocs/UNIX_INSTALL.html | 18 | ||||
| -rw-r--r-- | docs/htmldocs/net.8.html | 106 | ||||
| -rw-r--r-- | docs/htmldocs/nmbd.8.html | 61 | ||||
| -rw-r--r-- | docs/htmldocs/smb.conf.5.html | 214 | ||||
| -rw-r--r-- | docs/htmldocs/smbclient.1.html | 97 | ||||
| -rw-r--r-- | docs/htmldocs/smbd.8.html | 113 | ||||
| -rw-r--r-- | docs/htmldocs/smbgroupedit.8.html | 402 | ||||
| -rw-r--r-- | docs/htmldocs/smbpasswd.8.html | 93 | ||||
| -rw-r--r-- | docs/htmldocs/smbsh.1.html | 229 | ||||
| -rw-r--r-- | docs/htmldocs/wbinfo.1.html | 78 | ||||
| -rw-r--r-- | docs/htmldocs/winbind.html | 4 | ||||
| -rw-r--r-- | docs/htmldocs/winbindd.8.html | 57 |
13 files changed, 841 insertions, 1645 deletions
diff --git a/docs/htmldocs/Samba-HOWTO-Collection.html b/docs/htmldocs/Samba-HOWTO-Collection.html index 50d9dea7e30..870b0ec6e82 100644 --- a/docs/htmldocs/Samba-HOWTO-Collection.html +++ b/docs/htmldocs/Samba-HOWTO-Collection.html @@ -668,231 +668,155 @@ HREF="#AEN1602" ></DD ><DT >9. <A -HREF="#SAMBA-BDC" ->How to a Purely Samba Controlled Domain</A -></DT -><DD -><DL -><DT ->9.1. <A -HREF="#AEN1638" ->Prerequisite Reading</A -></DT -><DT ->9.2. <A -HREF="#AEN1642" ->Background</A -></DT -><DT ->9.3. <A -HREF="#AEN1650" ->What qualifies a Domain Controller on the network?</A -></DT -><DD -><DL -><DT ->9.3.1. <A -HREF="#AEN1653" ->How does a Workstation find its domain controller?</A -></DT -><DT ->9.3.2. <A -HREF="#AEN1656" ->When is the PDC needed?</A -></DT -></DL -></DD -><DT ->9.4. <A -HREF="#AEN1659" ->Can Samba be a Backup Domain Controller?</A -></DT -><DT ->9.5. <A -HREF="#AEN1663" ->How do I set up a Samba BDC?</A -></DT -><DD -><DL -><DT ->9.5.1. <A -HREF="#AEN1679" ->How do I replicate the smbpasswd file?</A -></DT -></DL -></DD -></DL -></DD -><DT ->10. <A HREF="#SAMBA-LDAP-HOWTO" >Storing Samba's User/Machine Account information in an LDAP Directory</A ></DT ><DD ><DL ><DT ->10.1. <A -HREF="#AEN1700" +>9.1. <A +HREF="#AEN1638" >Purpose</A ></DT ><DT ->10.2. <A -HREF="#AEN1720" +>9.2. <A +HREF="#AEN1652" >Introduction</A ></DT ><DT ->10.3. <A -HREF="#AEN1749" +>9.3. <A +HREF="#AEN1677" >Supported LDAP Servers</A ></DT ><DT ->10.4. <A -HREF="#AEN1754" +>9.4. <A +HREF="#AEN1682" >Schema and Relationship to the RFC 2307 posixAccount</A ></DT ><DT ->10.5. <A -HREF="#AEN1766" ->Configuring Samba with LDAP</A -></DT -><DD -><DL -><DT ->10.5.1. <A -HREF="#AEN1768" ->OpenLDAP configuration</A -></DT -><DT ->10.5.2. <A -HREF="#AEN1785" ->Configuring Samba</A -></DT -></DL -></DD -><DT ->10.6. <A -HREF="#AEN1813" ->Accounts and Groups management</A +>9.5. <A +HREF="#AEN1706" +>smb.conf LDAP parameters</A ></DT ><DT ->10.7. <A -HREF="#AEN1818" +>9.6. <A +HREF="#AEN1734" >Security and sambaAccount</A ></DT ><DT ->10.8. <A -HREF="#AEN1838" ->LDAP specials attributes for sambaAccounts</A +>9.7. <A +HREF="#AEN1753" +></A ></DT ><DT ->10.9. <A -HREF="#AEN1908" +>9.8. <A +HREF="#AEN1773" >Example LDIF Entries for a sambaAccount</A ></DT ><DT ->10.10. <A -HREF="#AEN1916" +>9.9. <A +HREF="#AEN1781" >Comments</A ></DT ></DL ></DD ><DT ->11. <A +>10. <A HREF="#WINBIND" >Unified Logons between Windows NT and UNIX using Winbind</A ></DT ><DD ><DL ><DT ->11.1. <A -HREF="#AEN1945" +>10.1. <A +HREF="#AEN1810" >Abstract</A ></DT ><DT ->11.2. <A -HREF="#AEN1949" +>10.2. <A +HREF="#AEN1814" >Introduction</A ></DT ><DT ->11.3. <A -HREF="#AEN1962" +>10.3. <A +HREF="#AEN1827" >What Winbind Provides</A ></DT ><DD ><DL ><DT ->11.3.1. <A -HREF="#AEN1969" +>10.3.1. <A +HREF="#AEN1834" >Target Uses</A ></DT ></DL ></DD ><DT ->11.4. <A -HREF="#AEN1973" +>10.4. <A +HREF="#AEN1838" >How Winbind Works</A ></DT ><DD ><DL ><DT ->11.4.1. <A -HREF="#AEN1978" +>10.4.1. <A +HREF="#AEN1843" >Microsoft Remote Procedure Calls</A ></DT ><DT ->11.4.2. <A -HREF="#AEN1982" +>10.4.2. <A +HREF="#AEN1847" >Name Service Switch</A ></DT ><DT ->11.4.3. <A -HREF="#AEN1998" +>10.4.3. <A +HREF="#AEN1863" >Pluggable Authentication Modules</A ></DT ><DT ->11.4.4. <A -HREF="#AEN2006" +>10.4.4. <A +HREF="#AEN1871" >User and Group ID Allocation</A ></DT ><DT ->11.4.5. <A -HREF="#AEN2010" +>10.4.5. <A +HREF="#AEN1875" >Result Caching</A ></DT ></DL ></DD ><DT ->11.5. <A -HREF="#AEN2013" +>10.5. <A +HREF="#AEN1878" >Installation and Configuration</A ></DT ><DD ><DL ><DT ->11.5.1. <A -HREF="#AEN2018" +>10.5.1. <A +HREF="#AEN1883" >Introduction</A ></DT ><DT ->11.5.2. <A -HREF="#AEN2031" +>10.5.2. <A +HREF="#AEN1896" >Requirements</A ></DT ><DT ->11.5.3. <A -HREF="#AEN2045" +>10.5.3. <A +HREF="#AEN1910" >Testing Things Out</A ></DT ><DD ><DL ><DT ->11.5.3.1. <A -HREF="#AEN2056" +>10.5.3.1. <A +HREF="#AEN1921" >Configure and compile SAMBA</A ></DT ><DT ->11.5.3.2. <A -HREF="#AEN2075" +>10.5.3.2. <A +HREF="#AEN1940" >Configure <TT CLASS="FILENAME" >nsswitch.conf</TT @@ -900,31 +824,31 @@ CLASS="FILENAME" winbind libraries</A ></DT ><DT ->11.5.3.3. <A -HREF="#AEN2100" +>10.5.3.3. <A +HREF="#AEN1965" >Configure smb.conf</A ></DT ><DT ->11.5.3.4. <A -HREF="#AEN2116" +>10.5.3.4. <A +HREF="#AEN1981" >Join the SAMBA server to the PDC domain</A ></DT ><DT ->11.5.3.5. <A -HREF="#AEN2127" +>10.5.3.5. <A +HREF="#AEN1992" >Start up the winbindd daemon and test it!</A ></DT ><DT ->11.5.3.6. <A -HREF="#AEN2163" +>10.5.3.6. <A +HREF="#AEN2028" >Fix the <TT CLASS="FILENAME" >/etc/rc.d/init.d/smb</TT > startup files</A ></DT ><DT ->11.5.3.7. <A -HREF="#AEN2185" +>10.5.3.7. <A +HREF="#AEN2050" >Configure Winbind and PAM</A ></DT ></DL @@ -932,52 +856,52 @@ HREF="#AEN2185" ></DL ></DD ><DT ->11.6. <A -HREF="#AEN2232" +>10.6. <A +HREF="#AEN2097" >Limitations</A ></DT ><DT ->11.7. <A -HREF="#AEN2242" +>10.7. <A +HREF="#AEN2107" >Conclusion</A ></DT ></DL ></DD ><DT ->12. <A +>11. <A HREF="#OS2" >OS2 Client HOWTO</A ></DT ><DD ><DL ><DT ->12.1. <A -HREF="#AEN2256" +>11.1. <A +HREF="#AEN2121" >FAQs</A ></DT ><DD ><DL ><DT ->12.1.1. <A -HREF="#AEN2258" +>11.1.1. <A +HREF="#AEN2123" >How can I configure OS/2 Warp Connect or OS/2 Warp 4 as a client for Samba?</A ></DT ><DT ->12.1.2. <A -HREF="#AEN2273" +>11.1.2. <A +HREF="#AEN2138" >How can I configure OS/2 Warp 3 (not Connect), OS/2 1.2, 1.3 or 2.x for Samba?</A ></DT ><DT ->12.1.3. <A -HREF="#AEN2282" +>11.1.3. <A +HREF="#AEN2147" >Are there any other issues when OS/2 (any version) is used as a client?</A ></DT ><DT ->12.1.4. <A -HREF="#AEN2286" +>11.1.4. <A +HREF="#AEN2151" >How do I get printer driver download working for OS/2 clients?</A ></DT @@ -986,32 +910,32 @@ HREF="#AEN2286" ></DL ></DD ><DT ->13. <A +>12. <A HREF="#CVS-ACCESS" >HOWTO Access Samba source code via CVS</A ></DT ><DD ><DL ><DT ->13.1. <A -HREF="#AEN2302" +>12.1. <A +HREF="#AEN2167" >Introduction</A ></DT ><DT ->13.2. <A -HREF="#AEN2307" +>12.2. <A +HREF="#AEN2172" >CVS Access to samba.org</A ></DT ><DD ><DL ><DT ->13.2.1. <A -HREF="#AEN2310" +>12.2.1. <A +HREF="#AEN2175" >Access via CVSweb</A ></DT ><DT ->13.2.2. <A -HREF="#AEN2315" +>12.2.2. <A +HREF="#AEN2180" >Access via cvs</A ></DT ></DL @@ -1020,7 +944,7 @@ HREF="#AEN2315" ></DD ><DT ><A -HREF="#AEN2343" +HREF="#AEN2208" >Index</A ></DT ></DL @@ -1278,15 +1202,15 @@ NAME="AEN78" >1.6. Step 5: Starting the smbd and nmbd</A ></H1 ><P ->You must choose to start smbd and nmbd either +>You must choose to start smbd and nmbd either as daemons or from <B CLASS="COMMAND" >inetd</B ->. Don't try +>. Don't try to do both! Either you can put them in <TT CLASS="FILENAME" > inetd.conf</TT -> and have them started on demand +> and have them started on demand by <B CLASS="COMMAND" >inetd</B @@ -1294,9 +1218,9 @@ CLASS="COMMAND" 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 +>. 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 @@ -1306,9 +1230,9 @@ CLASS="COMMAND" 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 +> as a daemon is that they will + respond slightly more quickly to an initial connection + request. This is, however, unlikely to be a problem.</P ><DIV CLASS="SECT2" ><HR><H2 @@ -7963,262 +7887,20 @@ within its registry.</P CLASS="CHAPTER" ><HR><H1 ><A -NAME="SAMBA-BDC" ->Chapter 9. How to a Purely Samba Controlled Domain</A -></H1 -><DIV -CLASS="SECT1" -><H1 -CLASS="SECT1" -><A -NAME="AEN1638" ->9.1. Prerequisite Reading</A -></H1 -><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><H1 -CLASS="SECT1" -><A -NAME="AEN1642" ->9.2. Background</A -></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 -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 -><TABLE -BORDER="0" -BGCOLOR="#E0E0E0" -WIDTH="100%" -><TR -><TD -><PRE -CLASS="PROGRAMLISTING" ->workgroup = SAMBA -domain master = yes -domain logons = yes</PRE -></TD -></TR -></TABLE -></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><H1 -CLASS="SECT1" -><A -NAME="AEN1650" ->9.3. What qualifies a Domain Controller on the network?</A -></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 -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><H2 -CLASS="SECT2" -><A -NAME="AEN1653" ->9.3.1. How does a Workstation find its domain controller?</A -></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 -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><H2 -CLASS="SECT2" -><A -NAME="AEN1656" ->9.3.2. When is the PDC needed?</A -></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 -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><H1 -CLASS="SECT1" -><A -NAME="AEN1659" ->9.4. Can Samba be a Backup Domain Controller?</A -></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 ->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><H1 -CLASS="SECT1" -><A -NAME="AEN1663" ->9.5. How do I set up a Samba BDC?</A -></H1 -><P ->Several things have to be done:</P -><P -></P -><UL -><LI -><P ->The file private/MACHINE.SID identifies the domain. When a samba -server is first started, it is created on the fly and must never be -changed again. This file has to be the same on the PDC and the BDC, -so the MACHINE.SID has to be copied from the PDC to 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 -><TABLE -BORDER="0" -BGCOLOR="#E0E0E0" -WIDTH="100%" -><TR -><TD -><PRE -CLASS="PROGRAMLISTING" ->workgroup = samba -domain master = no -domain logons = yes</PRE -></TD -></TR -></TABLE -></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><H2 -CLASS="SECT2" -><A -NAME="AEN1679" ->9.5.1. How do I replicate the smbpasswd file?</A -></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 -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 -></DIV -><DIV -CLASS="CHAPTER" -><HR><H1 -><A NAME="SAMBA-LDAP-HOWTO" ->Chapter 10. Storing Samba's User/Machine Account information in an LDAP Directory</A +>Chapter 9. Storing Samba's User/Machine Account information in an LDAP Directory</A ></H1 ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1700" ->10.1. Purpose</A +NAME="AEN1638" +>9.1. Purpose</A ></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 +account information normally 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 @@ -8251,38 +7933,21 @@ TARGET="_top" 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 +>It may also be helpful to supplement the reading of the HOWTO with +the <A HREF="http://www.unav.es/cti/ldap-smb/ldap-smb-2_2-howto.html" TARGET="_top" >Samba-PDC-LDAP-HOWTO</A > - maintained by Ignacio Coupeau.</P -></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 +maintained by Ignacio Coupeau.</P ></DIV ><DIV CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN1720" ->10.2. Introduction</A +NAME="AEN1652" +>9.2. Introduction</A ></H1 ><P >Traditionally, when configuring <A @@ -8302,17 +7967,11 @@ CLASS="FILENAME" 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 +is non-optimal. What is needed is an indexed approach such as is used in +databases.</P ><P >The second problem is that administrators who desired to replicate a smbpasswd file to more than one Samba server were left to use external @@ -8324,19 +7983,15 @@ 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 +is 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" @@ -8398,8 +8053,8 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN1749" ->10.3. Supported LDAP Servers</A +NAME="AEN1677" +>9.3. Supported LDAP Servers</A ></H1 ><P >The LDAP samdb code in 2.2.3 has been developed and tested using the OpenLDAP @@ -8423,8 +8078,8 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN1754" ->10.4. Schema and Relationship to the RFC 2307 posixAccount</A +NAME="AEN1682" +>9.4. Schema and Relationship to the RFC 2307 posixAccount</A ></H1 ><P >Samba 2.2.3 includes the necessary schema file for OpenLDAP 2.0 in @@ -8449,7 +8104,7 @@ CLASS="PROGRAMLISTING" MAY ( cn $ lmPassword $ ntPassword $ pwdLastSet $ logonTime $ logoffTime $ kickoffTime $ pwdCanChange $ pwdMustChange $ acctFlags $ displayName $ smbHome $ homeDrive $ scriptPath $ profilePath $ - description $ userWorkstations $ primaryGroupID $ domain ))</PRE + description $ userWorkstations $ primaryGroupID ))</PRE ></TD ></TR ></TABLE @@ -8485,23 +8140,6 @@ 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="SECT1" -><HR><H1 -CLASS="SECT1" -><A -NAME="AEN1766" ->10.5. Configuring Samba with LDAP</A -></H1 -><DIV -CLASS="SECT2" -><H2 -CLASS="SECT2" -><A -NAME="AEN1768" ->10.5.1. OpenLDAP configuration</A -></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 @@ -8561,47 +8199,15 @@ include /etc/openldap/schema/samba.schema ></TR ></TABLE ></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 -><TABLE -BORDER="0" -BGCOLOR="#E0E0E0" -WIDTH="100%" -><TR -><TD -><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 -></TD -></TR -></TABLE -></P ></DIV ><DIV -CLASS="SECT2" -><HR><H2 -CLASS="SECT2" +CLASS="SECT1" +><HR><H1 +CLASS="SECT1" ><A -NAME="AEN1785" ->10.5.2. Configuring Samba</A -></H2 +NAME="AEN1706" +>9.5. smb.conf LDAP parameters</A +></H1 ><P >The following parameters are available in smb.conf only with <TT CLASS="PARAMETER" @@ -8699,7 +8305,7 @@ CLASS="REPLACEABLE" >' 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" + ldap admin dn = "cn=Manager,dc=samba,dc=org" # specify the LDAP server's hostname (defaults to locahost) ldap server = ahab.samba.org @@ -8722,39 +8328,13 @@ CLASS="REPLACEABLE" ></TABLE ></P ></DIV -></DIV -><DIV -CLASS="SECT1" -><HR><H1 -CLASS="SECT1" -><A -NAME="AEN1813" ->10.6. Accounts and Groups management</A -></H1 -><P ->As users accounts are managed thru the sambaAccount objectclass, you should -modify you existing administration tools to deal with sambaAccount attributes.</P -><P ->Machines accounts are managed with the sambaAccount objectclass, just -like users accounts. However, it's up to you to stored thoses accounts -in a different tree of you LDAP namespace: you should use -"ou=Groups,dc=plainjoe,dc=org" to store groups and -"ou=People,dc=plainjoe,dc=org" to store users. Just configure your -NSS and PAM accordingly (usually, in the /etc/ldap.conf configuration -file).</P -><P ->In Samba release 2.2.3, the group management system is based on posix -groups. This meand that Samba make usage of the posixGroup objectclass. -For now, there is no NT-like group system management (global and local -groups).</P -></DIV ><DIV CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN1818" ->10.7. Security and sambaAccount</A +NAME="AEN1734" +>9.6. Security and sambaAccount</A ></H1 ><P >There are two important points to remember when discussing the security @@ -8779,12 +8359,7 @@ of sambaAccount entries in the directory.</P ></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 +the user without deriving the original clear text strings.</P ><P >To remedy the first security issue, the "ldap ssl" smb.conf parameter defaults to require an encrypted session (<B @@ -8800,10 +8375,6 @@ 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 @@ -8819,200 +8390,60 @@ WIDTH="100%" ><TD ><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 +>## allow users to update their own password, but not to browse others +access to attrs=userPassword,lmPassword,ntPassword + by self write + by * auth</PRE ></TD ></TR ></TABLE ></P +><P +>You may of course, add in write access to administrative DN's as necessary.</P ></DIV ><DIV CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN1838" ->10.8. LDAP specials attributes for sambaAccounts</A +NAME="AEN1753" +>9.7. </A ></H1 ><P ->The sambaAccount objectclass is composed of the following attributes:</P +>There are currently four sambaAccount attributes which map directly onto +<TT +CLASS="FILENAME" +>smb.conf</TT +> parameters.</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 +>smbHome -> "logon home"</P ></LI ><LI ><P -><TT -CLASS="CONSTANT" ->userWorkstation</TT ->: character string value currently unused. - </P +>profilePath -> "logon path"</P ></LI ><LI ><P -><TT -CLASS="CONSTANT" ->rid</TT ->: the integer representation of the user's relative identifier - (RID).</P +>homeDrive -> "logon drive"</P ></LI ><LI ><P -><TT -CLASS="CONSTANT" ->primaryGroupID</TT ->: the relative identifier (RID) of the primary group - of the user.</P +>scriptPath -> "logon script"</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 +>First of all, these parameters are only used when Samba is acting as a +PDC or 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 +> +for details on how to configure Samba as a Primary Domain Controller). +Furthermore, 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" @@ -9027,8 +8458,9 @@ 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", +> string is expanded to \\TASHTEGO\becky.</P +><P +>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" @@ -9044,8 +8476,8 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN1908" ->10.9. Example LDIF Entries for a sambaAccount</A +NAME="AEN1773" +>9.8. Example LDIF Entries for a sambaAccount</A ></H1 ><P >The following is a working LDIF with the inclusion of the posixAccount objectclass:</P @@ -9120,8 +8552,8 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN1916" ->10.10. Comments</A +NAME="AEN1781" +>9.9. Comments</A ></H1 ><P >Please mail all comments regarding this HOWTO to <A @@ -9137,15 +8569,15 @@ CLASS="CHAPTER" ><HR><H1 ><A NAME="WINBIND" ->Chapter 11. Unified Logons between Windows NT and UNIX using Winbind</A +>Chapter 10. Unified Logons between Windows NT and UNIX using Winbind</A ></H1 ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1945" ->11.1. Abstract</A +NAME="AEN1810" +>10.1. Abstract</A ></H1 ><P >Integration of UNIX and Microsoft Windows NT through @@ -9167,8 +8599,8 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN1949" ->11.2. Introduction</A +NAME="AEN1814" +>10.2. Introduction</A ></H1 ><P >It is well known that UNIX and Microsoft Windows NT have @@ -9221,8 +8653,8 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN1962" ->11.3. What Winbind Provides</A +NAME="AEN1827" +>10.3. What Winbind Provides</A ></H1 ><P >Winbind unifies UNIX and Windows NT account management by @@ -9263,8 +8695,8 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN1969" ->11.3.1. Target Uses</A +NAME="AEN1834" +>10.3.1. Target Uses</A ></H2 ><P >Winbind is targeted at organizations that have an @@ -9287,8 +8719,8 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN1973" ->11.4. How Winbind Works</A +NAME="AEN1838" +>10.4. How Winbind Works</A ></H1 ><P >The winbind system is designed around a client/server @@ -9307,8 +8739,8 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN1978" ->11.4.1. Microsoft Remote Procedure Calls</A +NAME="AEN1843" +>10.4.1. Microsoft Remote Procedure Calls</A ></H2 ><P >Over the last two years, efforts have been underway @@ -9333,8 +8765,8 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN1982" ->11.4.2. Name Service Switch</A +NAME="AEN1847" +>10.4.2. Name Service Switch</A ></H2 ><P >The Name Service Switch, or NSS, is a feature that is @@ -9413,8 +8845,8 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN1998" ->11.4.3. Pluggable Authentication Modules</A +NAME="AEN1863" +>10.4.3. Pluggable Authentication Modules</A ></H2 ><P >Pluggable Authentication Modules, also known as PAM, @@ -9462,8 +8894,8 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN2006" ->11.4.4. User and Group ID Allocation</A +NAME="AEN1871" +>10.4.4. User and Group ID Allocation</A ></H2 ><P >When a user or group is created under Windows NT @@ -9488,8 +8920,8 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN2010" ->11.4.5. Result Caching</A +NAME="AEN1875" +>10.4.5. Result Caching</A ></H2 ><P >An active system can generate a lot of user and group @@ -9511,8 +8943,8 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN2013" ->11.5. Installation and Configuration</A +NAME="AEN1878" +>10.5. Installation and Configuration</A ></H1 ><P >Many thanks to John Trostel <A @@ -9530,8 +8962,8 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN2018" ->11.5.1. Introduction</A +NAME="AEN1883" +>10.5.1. Introduction</A ></H2 ><P >This HOWTO describes the procedures used to get winbind up and @@ -9581,8 +9013,8 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN2031" ->11.5.2. Requirements</A +NAME="AEN1896" +>10.5.2. Requirements</A ></H2 ><P >If you have a samba configuration file that you are currently @@ -9639,8 +9071,8 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN2045" ->11.5.3. Testing Things Out</A +NAME="AEN1910" +>10.5.3. Testing Things Out</A ></H2 ><P >Before starting, it is probably best to kill off all the SAMBA @@ -9684,8 +9116,8 @@ CLASS="SECT3" ><HR><H3 CLASS="SECT3" ><A -NAME="AEN2056" ->11.5.3.1. Configure and compile SAMBA</A +NAME="AEN1921" +>10.5.3.1. Configure and compile SAMBA</A ></H3 ><P >The configuration and compilation of SAMBA is pretty straightforward. @@ -9759,8 +9191,8 @@ CLASS="SECT3" ><HR><H3 CLASS="SECT3" ><A -NAME="AEN2075" ->11.5.3.2. Configure <TT +NAME="AEN1940" +>10.5.3.2. Configure <TT CLASS="FILENAME" >nsswitch.conf</TT > and the @@ -9849,8 +9281,8 @@ CLASS="SECT3" ><HR><H3 CLASS="SECT3" ><A -NAME="AEN2100" ->11.5.3.3. Configure smb.conf</A +NAME="AEN1965" +>10.5.3.3. Configure smb.conf</A ></H3 ><P >Several parameters are needed in the smb.conf file to control @@ -9933,8 +9365,8 @@ CLASS="SECT3" ><HR><H3 CLASS="SECT3" ><A -NAME="AEN2116" ->11.5.3.4. Join the SAMBA server to the PDC domain</A +NAME="AEN1981" +>10.5.3.4. Join the SAMBA server to the PDC domain</A ></H3 ><P >Enter the following command to make the SAMBA server join the @@ -9957,7 +9389,7 @@ CLASS="PROMPT" >root#</TT > <B CLASS="COMMAND" ->/usr/local/samba/bin/net rpc join -s PDC -U Administrator</B +>/usr/local/samba/bin/smbpasswd -j DOMAIN -r PDC -U Administrator</B ></P ><P >The proper response to the command should be: "Joined the domain @@ -9979,8 +9411,8 @@ CLASS="SECT3" ><HR><H3 CLASS="SECT3" ><A -NAME="AEN2127" ->11.5.3.5. Start up the winbindd daemon and test it!</A +NAME="AEN1992" +>10.5.3.5. Start up the winbindd daemon and test it!</A ></H3 ><P >Eventually, you will want to modify your smb startup script to @@ -10049,7 +9481,7 @@ CEO+TsInternetUser</PRE >Obviously, I have named my domain 'CEO' and my <TT CLASS="PARAMETER" ><I ->winbind +>winbindd separator</I ></TT > is '+'.</P @@ -10120,8 +9552,8 @@ CLASS="SECT3" ><HR><H3 CLASS="SECT3" ><A -NAME="AEN2163" ->11.5.3.6. Fix the <TT +NAME="AEN2028" +>10.5.3.6. Fix the <TT CLASS="FILENAME" >/etc/rc.d/init.d/smb</TT > startup files</A @@ -10250,8 +9682,8 @@ CLASS="SECT3" ><HR><H3 CLASS="SECT3" ><A -NAME="AEN2185" ->11.5.3.7. Configure Winbind and PAM</A +NAME="AEN2050" +>10.5.3.7. Configure Winbind and PAM</A ></H3 ><P >If you have made it this far, you know that winbindd and samba are working @@ -10472,8 +9904,8 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN2232" ->11.6. Limitations</A +NAME="AEN2097" +>10.6. Limitations</A ></H1 ><P >Winbind has a number of limitations in its current @@ -10513,8 +9945,8 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN2242" ->11.7. Conclusion</A +NAME="AEN2107" +>10.7. Conclusion</A ></H1 ><P >The winbind system, through the use of the Name Service @@ -10530,23 +9962,23 @@ CLASS="CHAPTER" ><HR><H1 ><A NAME="OS2" ->Chapter 12. OS2 Client HOWTO</A +>Chapter 11. OS2 Client HOWTO</A ></H1 ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2256" ->12.1. FAQs</A +NAME="AEN2121" +>11.1. FAQs</A ></H1 ><DIV CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2258" ->12.1.1. How can I configure OS/2 Warp Connect or +NAME="AEN2123" +>11.1.1. How can I configure OS/2 Warp Connect or OS/2 Warp 4 as a client for Samba?</A ></H2 ><P @@ -10604,8 +10036,8 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN2273" ->12.1.2. How can I configure OS/2 Warp 3 (not Connect), +NAME="AEN2138" +>11.1.2. How can I configure OS/2 Warp 3 (not Connect), OS/2 1.2, 1.3 or 2.x for Samba?</A ></H2 ><P @@ -10657,8 +10089,8 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN2282" ->12.1.3. Are there any other issues when OS/2 (any version) +NAME="AEN2147" +>11.1.3. Are there any other issues when OS/2 (any version) is used as a client?</A ></H2 ><P @@ -10679,8 +10111,8 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN2286" ->12.1.4. How do I get printer driver download working +NAME="AEN2151" +>11.1.4. How do I get printer driver download working for OS/2 clients?</A ></H2 ><P @@ -10728,15 +10160,15 @@ CLASS="CHAPTER" ><HR><H1 ><A NAME="CVS-ACCESS" ->Chapter 13. HOWTO Access Samba source code via CVS</A +>Chapter 12. HOWTO Access Samba source code via CVS</A ></H1 ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2302" ->13.1. Introduction</A +NAME="AEN2167" +>12.1. Introduction</A ></H1 ><P >Samba is developed in an open environment. Developers use CVS @@ -10757,8 +10189,8 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN2307" ->13.2. CVS Access to samba.org</A +NAME="AEN2172" +>12.2. CVS Access to samba.org</A ></H1 ><P >The machine samba.org runs a publicly accessible CVS @@ -10770,8 +10202,8 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN2310" ->13.2.1. Access via CVSweb</A +NAME="AEN2175" +>12.2.1. Access via CVSweb</A ></H2 ><P >You can access the source code via your @@ -10791,8 +10223,8 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN2315" ->13.2.2. Access via cvs</A +NAME="AEN2180" +>12.2.2. Access via cvs</A ></H2 ><P >You can also access the source code via a @@ -10897,7 +10329,7 @@ CLASS="COMMAND" ></DIV ><HR><H1 ><A -NAME="AEN2343" +NAME="AEN2208" >Index</A ></H1 ><DL diff --git a/docs/htmldocs/UNIX_INSTALL.html b/docs/htmldocs/UNIX_INSTALL.html index 35b1d9b01bc..7194e1154ec 100644 --- a/docs/htmldocs/UNIX_INSTALL.html +++ b/docs/htmldocs/UNIX_INSTALL.html @@ -260,15 +260,15 @@ NAME="AEN63" >Step 5: Starting the smbd and nmbd</A ></H1 ><P ->You must choose to start smbd and nmbd either +>You must choose to start smbd and nmbd either as daemons or from <B CLASS="COMMAND" >inetd</B ->. Don't try +>. Don't try to do both! Either you can put them in <TT CLASS="FILENAME" > inetd.conf</TT -> and have them started on demand +> and have them started on demand by <B CLASS="COMMAND" >inetd</B @@ -276,9 +276,9 @@ CLASS="COMMAND" 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 +>. 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 @@ -288,9 +288,9 @@ CLASS="COMMAND" 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 +> as a daemon is that they will + respond slightly more quickly to an initial connection + request. This is, however, unlikely to be a problem.</P ><DIV CLASS="SECT2" ><HR><H2 diff --git a/docs/htmldocs/net.8.html b/docs/htmldocs/net.8.html deleted file mode 100644 index 77cb2b2b380..00000000000 --- a/docs/htmldocs/net.8.html +++ /dev/null @@ -1,106 +0,0 @@ -<HTML -><HEAD -><TITLE ->net</TITLE -><META -NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.57"></HEAD -><BODY -CLASS="REFENTRY" -BGCOLOR="#FFFFFF" -TEXT="#000000" -LINK="#0000FF" -VLINK="#840084" -ALINK="#0000FF" -><H1 -><A -NAME="NET" ->net</A -></H1 -><DIV -CLASS="REFNAMEDIV" -><A -NAME="AEN5" -></A -><H2 ->Name</H2 ->net -- Tool for administration of Samba and remote - CIFS servers.</DIV -><DIV -CLASS="REFSYNOPSISDIV" -><A -NAME="AEN8" -></A -><H2 ->Synopsis</H2 -><P -><B -CLASS="COMMAND" ->net</B -> {<ads|rap|rpc>}</P -></DIV -><DIV -CLASS="REFSECT1" -><A -NAME="AEN12" -></A -><H2 ->DESCRIPTION</H2 -><P ->This tool is part of the <A -HREF="samba.7.html" -TARGET="_top" -> Samba</A -> suite.</P -></DIV -><DIV -CLASS="REFSECT1" -><A -NAME="AEN16" -></A -><H2 ->OPTIONS</H2 -><P -></P -></DIV -><DIV -CLASS="REFSECT1" -><A -NAME="AEN19" -></A -><H2 ->COMMANDS</H2 -><P -></P -></DIV -><DIV -CLASS="REFSECT1" -><A -NAME="AEN22" -></A -><H2 ->VERSION</H2 -><P ->This man page is incomplete for version 3.0 of the Samba - suite.</P -></DIV -><DIV -CLASS="REFSECT1" -><A -NAME="AEN25" -></A -><H2 ->AUTHOR</H2 -><P ->The original Samba software and related utilities - were created by Andrew Tridgell. Samba is now developed - by the Samba Team as an Open Source project similar - to the way the Linux kernel is developed.</P -><P ->The original Samba man pages were written by Karl Auer. - The current set of manpages and documentation is maintained - by the Samba Team in the same fashion as the Samba source code.</P -></DIV -></BODY -></HTML ->
\ No newline at end of file diff --git a/docs/htmldocs/nmbd.8.html b/docs/htmldocs/nmbd.8.html index 4e5993f3bc4..b18ae23aa21 100644 --- a/docs/htmldocs/nmbd.8.html +++ b/docs/htmldocs/nmbd.8.html @@ -340,31 +340,30 @@ CLASS="FILENAME" ><DD ><P >UDP port number is a positive integer value. - This option changes the default UDP port number (normally 137) + This option changes the default UDP port number (normally 137) that <B CLASS="COMMAND" >nmbd</B -> responds to name queries on. Don't - use this option unless you are an expert, in which case you +> responds to name queries on. Don't + use this option unless you are an expert, in which case you won't need help!</P ></DD ><DT >-s <configuration file></DT ><DD ><P ->The default configuration file name +>The default configuration file name is set at build time, typically as <TT CLASS="FILENAME" > /usr/local/samba/lib/smb.conf</TT >, but this may be changed when Samba is autoconfigured.</P ><P ->The file specified contains the configuration details +>The file specified contains the configuration details required by the server. See <A HREF="smb.conf.5.html" TARGET="_top" -> - <TT +> <TT CLASS="FILENAME" >smb.conf(5)</TT ></A @@ -393,12 +392,12 @@ CLASS="FILENAME" ></DT ><DD ><P ->If the server is to be run by the +>If the server is to be run by the <B CLASS="COMMAND" >inetd</B -> meta-daemon, this file - must contain suitable startup information for the +> meta-daemon, this file + must contain suitable startup information for the meta-daemon. See the <A HREF="UNIX_INSTALL.html" TARGET="_top" @@ -414,11 +413,11 @@ CLASS="FILENAME" ></DT ><DD ><P ->or whatever initialization script your +>or whatever initialization script your system uses).</P ><P ->If running the server as a daemon at startup, - this file will need to contain an appropriate startup +>If running the server as a daemon at startup, + this file will need to contain an appropriate startup sequence for the server. See the <A HREF="UNIX_INSTALL.html" TARGET="_top" @@ -433,13 +432,13 @@ CLASS="FILENAME" ></DT ><DD ><P ->If running the server via the +>If running the server via the meta-daemon <B CLASS="COMMAND" >inetd</B ->, this file - must contain a mapping of service name (e.g., netbios-ssn) - to service port (e.g., 139) and protocol type (e.g., tcp). +>, this file + must contain a mapping of service name (e.g., netbios-ssn) + to service port (e.g., 139) and protocol type (e.g., tcp). See the <A HREF="UNIX_INSTALL.html" TARGET="_top" @@ -454,7 +453,7 @@ CLASS="FILENAME" ></DT ><DD ><P ->This is the default location of the +>This is the default location of the <A HREF="smb.conf.5.html" TARGET="_top" @@ -463,17 +462,17 @@ CLASS="FILENAME" >smb.conf</TT ></A > - server configuration file. Other common places that systems + server configuration file. Other common places that systems install this file are <TT CLASS="FILENAME" >/usr/samba/lib/smb.conf</TT -> +> and <TT CLASS="FILENAME" >/etc/smb.conf</TT >.</P ><P ->When run as a WINS server (see the +>When run as a WINS server (see the <A HREF="smb.conf.5.html#WINSSUPPORT" TARGET="_top" @@ -490,11 +489,11 @@ CLASS="COMMAND" will store the WINS database in the file <TT CLASS="FILENAME" >wins.dat</TT -> +> in the <TT CLASS="FILENAME" >var/locks</TT -> directory configured under +> directory configured under wherever Samba was configured to install itself.</P ><P >If <B @@ -540,21 +539,21 @@ NAME="AEN177" >To shut down an <B CLASS="COMMAND" >nmbd</B -> process it is recommended +> process it is recommended that SIGKILL (-9) <EM >NOT</EM -> be used, except as a last - resort, as this may leave the name database in an inconsistent state. +> be used, except as a last + resort, as this may leave the name database in an inconsistent state. The correct way to terminate <B CLASS="COMMAND" >nmbd</B -> is to send it +> is to send it a SIGTERM (-15) signal and wait for it to die on its own.</P ><P ><B CLASS="COMMAND" >nmbd</B -> will accept SIGHUP, which will cause +> will accept SIGHUP, which will cause it to dump out its namelists into the file <TT CLASS="FILENAME" >namelist.debug @@ -562,12 +561,12 @@ CLASS="FILENAME" > in the <TT CLASS="FILENAME" >/usr/local/samba/var/locks</TT -> +> directory (or the <TT CLASS="FILENAME" >var/locks</TT -> directory configured - under wherever Samba was configured to install itself). This will also +> directory configured + under wherever Samba was configured to install itself). This will also cause <B CLASS="COMMAND" >nmbd</B diff --git a/docs/htmldocs/smb.conf.5.html b/docs/htmldocs/smb.conf.5.html index 1438b1436ba..aaf38a0cb2b 100644 --- a/docs/htmldocs/smb.conf.5.html +++ b/docs/htmldocs/smb.conf.5.html @@ -957,18 +957,6 @@ CLASS="PARAMETER" ><LI ><P ><A -HREF="#AUTHMETHODS" -><TT -CLASS="PARAMETER" -><I ->auth methods</I -></TT -></A -></P -></LI -><LI -><P -><A HREF="#AUTOSERVICES" ><TT CLASS="PARAMETER" @@ -1965,11 +1953,11 @@ CLASS="PARAMETER" ><LI ><P ><A -HREF="#NONUNIXACCOUNTRANGE" +HREF="#NTPIPESUPPORT" ><TT CLASS="PARAMETER" ><I ->non unix account range</I +>nt pipe support</I ></TT ></A ></P @@ -1977,11 +1965,11 @@ CLASS="PARAMETER" ><LI ><P ><A -HREF="#NTPIPESUPPORT" +HREF="#NTSMBSUPPORT" ><TT CLASS="PARAMETER" ><I ->nt pipe support</I +>nt smb support</I ></TT ></A ></P @@ -2073,18 +2061,6 @@ CLASS="PARAMETER" ><LI ><P ><A -HREF="#PASSDBBACKEND" -><TT -CLASS="PARAMETER" -><I ->passdb backend</I -></TT -></A -></P -></LI -><LI -><P -><A HREF="#PASSWDCHAT" ><TT CLASS="PARAMETER" @@ -2961,18 +2937,6 @@ CLASS="PARAMETER" ><LI ><P ><A -HREF="#WINBINDUSEDEFAULTDOMAIN" -><TT -CLASS="PARAMETER" -><I ->winbind use default domain</I -></TT -></A -></P -></LI -><LI -><P -><A HREF="#WINSHOOK" ><TT CLASS="PARAMETER" @@ -3047,7 +3011,7 @@ CLASS="PARAMETER" ><DIV CLASS="REFSECT1" ><A -NAME="AEN986" +NAME="AEN974" ></A ><H2 >COMPLETE LIST OF SERVICE PARAMETERS</H2 @@ -4490,7 +4454,7 @@ CLASS="PARAMETER" ><DIV CLASS="REFSECT1" ><A -NAME="AEN1466" +NAME="AEN1454" ></A ><H2 >EXPLANATION OF EACH PARAMETER</H2 @@ -5187,43 +5151,6 @@ CLASS="PARAMETER" ></DD ><DT ><A -NAME="AUTHMETHODS" -></A ->auth methods (G)</DT -><DD -><P ->This option allows the administrator to chose what - authentication methods <B -CLASS="COMMAND" ->smbd</B -> will use when authenticating - a user. This option defaults to sensible values based on <A -HREF="#SECURITY" -><TT -CLASS="PARAMETER" -><I -> security</I -></TT -></A ->. - - Each entry in the list attempts to authenticate the user in turn, until - the user authenticates. In practice only one method will ever actually - be able to complete the authentication. - </P -><P ->Default: <B -CLASS="COMMAND" ->auth methods = <empty string></B -></P -><P ->Example: <B -CLASS="COMMAND" ->auth methods = guest sam ntdomain</B -></P -></DD -><DT -><A NAME="AVAILABLE" ></A >available (S)</DT @@ -8073,7 +8000,7 @@ CLASS="COMMAND" > program for information on how to set up and maintain this file), or set the <A HREF="#SECURITY" ->security = [server|domain|ads]</A +>security = [server|domain]</A > parameter which causes <B CLASS="COMMAND" @@ -8083,7 +8010,7 @@ CLASS="COMMAND" ><P >Default: <B CLASS="COMMAND" ->encrypt passwords = yes</B +>encrypt passwords = no</B ></P ></DD ><DT @@ -12724,37 +12651,6 @@ CLASS="COMMAND" ></DD ><DT ><A -NAME="NONUNIXACCOUNTRANGE" -></A ->non unix account range (G)</DT -><DD -><P ->The non unix account range parameter specifies - the range of 'user ids' that are allocated by the various 'non unix - account' passdb backends. These backends allow - the storage of passwords for users who don't exist in /etc/passwd. - This is most often used for machine account creation. - This range of ids should have no existing local or NIS users within - it as strange conflicts can occur otherwise.</P -><P ->NOTE: These userids never appear on the system and Samba will never - 'become' these users. They are used only to ensure that the algorithmic - RID mapping does not conflict with normal users. - </P -><P ->Default: <B -CLASS="COMMAND" ->non unix account range = <empty string> - </B -></P -><P ->Example: <B -CLASS="COMMAND" ->non unix account range = 10000-20000</B -></P -></DD -><DT -><A NAME="NTACLSUPPORT" ></A >nt acl support (S)</DT @@ -12802,6 +12698,40 @@ CLASS="COMMAND" ></DD ><DT ><A +NAME="NTSMBSUPPORT" +></A +>nt smb support (G)</DT +><DD +><P +>This boolean parameter controls whether <A +HREF="smbd.8.html" +TARGET="_top" +>smbd(8)</A +> will negotiate NT specific SMB + support with Windows NT clients. Although this is a developer + debugging option and should be left alone, benchmarking has discovered + that Windows NT clients give faster performance with this option + set to <TT +CLASS="CONSTANT" +>no</TT +>. This is still being investigated. + If this option is set to <TT +CLASS="CONSTANT" +>no</TT +> then Samba offers + exactly the same SMB calls that versions prior to Samba 2.0 offered. + This information may be of use if any users are having problems + with NT SMB support.</P +><P +>You should not need to ever disable this parameter.</P +><P +>Default: <B +CLASS="COMMAND" +>nt smb support = yes</B +></P +></DD +><DT +><A NAME="NULLPASSWORDS" ></A >null passwords (G)</DT @@ -13222,30 +13152,6 @@ CLASS="COMMAND" ></DD ><DT ><A -NAME="PASSDBBACKEND" -></A ->passdb backend (G)</DT -><DD -><P ->This option allows the administrator to chose what - backend in which to store passwords. This allows (for example) both - smbpasswd and tdbsam to be used without a recompile. Only one can - be used at a time however, and experimental backends must still be selected - (eg --with-tdbsam) at configure time. - </P -><P ->Default: <B -CLASS="COMMAND" ->passdb backend = smbpasswd</B -></P -><P ->Example: <B -CLASS="COMMAND" ->passdb backend = tdbsam</B -></P -></DD -><DT -><A NAME="PASSWDCHAT" ></A >passwd chat (G)</DT @@ -19013,34 +18919,6 @@ CLASS="COMMAND" ></P ></DD ><DT ->winbind use default domain, <A -NAME="WINBINDUSEDEFAULTDOMAIN" -></A ->winbind use default domain</DT -><DD -><P ->This parameter specifies whether the <A -HREF="winbindd.8.html" -TARGET="_top" -> winbindd(8)</A -> - daemon should operate on users without domain component in their username. - 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 = <falseg> - </B -></P -><P ->Example: <B -CLASS="COMMAND" ->winbind use default domain = true</B -></P -></DD -><DT ><A NAME="WINSHOOK" ></A @@ -19409,7 +19287,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN6125" +NAME="AEN6082" ></A ><H2 >WARNINGS</H2 @@ -19439,7 +19317,7 @@ TARGET="_top" ><DIV CLASS="REFSECT1" ><A -NAME="AEN6131" +NAME="AEN6088" ></A ><H2 >VERSION</H2 @@ -19450,7 +19328,7 @@ NAME="AEN6131" ><DIV CLASS="REFSECT1" ><A -NAME="AEN6134" +NAME="AEN6091" ></A ><H2 >SEE ALSO</H2 @@ -19529,7 +19407,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN6154" +NAME="AEN6111" ></A ><H2 >AUTHOR</H2 diff --git a/docs/htmldocs/smbclient.1.html b/docs/htmldocs/smbclient.1.html index 6c15873787d..96448bc6b1a 100644 --- a/docs/htmldocs/smbclient.1.html +++ b/docs/htmldocs/smbclient.1.html @@ -1051,6 +1051,42 @@ CLASS="REPLACEABLE" </P ></DD ><DT +>altname file</DT +><DD +><P +>The client will request that the server return + the "alternate" name (the 8.3 name) for a file or directory. + </P +></DD +><DT +>cancel jobid0 [jobid1] ... [jobidN]</DT +><DD +><P +>The client will request that the server cancel + the printjobs identified by the given numeric print job ids. + </P +></DD +><DT +>chmod file mode in octal</DT +><DD +><P +>This command depends on the server supporting the CIFS + UNIX extensions and will fail if the server does not. The client requests that the server + change the UNIX permissions to the given octal mode, in standard UNIX format. + </P +></DD +><DT +>chown file uid gid</DT +><DD +><P +>This command depends on the server supporting the CIFS + UNIX extensions and will fail if the server does not. The client requests that the server + change the UNIX user and group ownership to the given decimal values. Note there is + currently no way to remotely look up the UNIX uid and gid values for a given name. + This may be addressed in future versions of the CIFS UNIX extensions. + </P +></DD +><DT >cd [directory name]</DT ><DD ><P @@ -1139,6 +1175,16 @@ CLASS="REPLACEABLE" </P ></DD ><DT +>link source destination</DT +><DD +><P +>This command depends on the server supporting the CIFS + UNIX extensions and will fail if the server does not. The client requests that the server + create a hard link between the source and destination files. The source file + must not exist. + </P +></DD +><DT >lowercase</DT ><DD ><P @@ -1352,6 +1398,31 @@ CLASS="REPLACEABLE" privileges permitting) from the server. </P ></DD ><DT +>setmode <filename> <perm=[+|\-]rsha></DT +><DD +><P +>A version of the DOS attrib command to set + file permissions. For example: </P +><P +><B +CLASS="COMMAND" +>setmode myfile +r </B +></P +><P +>would make myfile read only. </P +></DD +><DT +>symlink source destination</DT +><DD +><P +>This command depends on the server supporting the CIFS + UNIX extensions and will fail if the server does not. The client requests that the server + create a symbolic hard link between the source and destination files. The source file + must not exist. Note that the server will not create a link to any path that lies + outside the currently connected share. This is enforced by the Samba server. + </P +></DD +><DT >tar <c|x>[IXbgNa]</DT ><DD ><P @@ -1391,27 +1462,13 @@ CLASS="REPLACEABLE" tar will reset the archive bit on all files it backs up (implies read/write share). </P ></DD -><DT ->setmode <filename> <perm=[+|\-]rsha></DT -><DD -><P ->A version of the DOS attrib command to set - file permissions. For example: </P -><P -><B -CLASS="COMMAND" ->setmode myfile +r </B -></P -><P ->would make myfile read only. </P -></DD ></DL ></DIV ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN477" +NAME="AEN501" ></A ><H2 >NOTES</H2 @@ -1432,7 +1489,7 @@ NAME="AEN477" ><DIV CLASS="REFSECT1" ><A -NAME="AEN482" +NAME="AEN506" ></A ><H2 >ENVIRONMENT VARIABLES</H2 @@ -1465,7 +1522,7 @@ CLASS="ENVAR" ><DIV CLASS="REFSECT1" ><A -NAME="AEN490" +NAME="AEN514" ></A ><H2 >INSTALLATION</H2 @@ -1503,7 +1560,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN500" +NAME="AEN524" ></A ><H2 >DIAGNOSTICS</H2 @@ -1519,7 +1576,7 @@ NAME="AEN500" ><DIV CLASS="REFSECT1" ><A -NAME="AEN504" +NAME="AEN528" ></A ><H2 >VERSION</H2 @@ -1530,7 +1587,7 @@ NAME="AEN504" ><DIV CLASS="REFSECT1" ><A -NAME="AEN507" +NAME="AEN531" ></A ><H2 >AUTHOR</H2 diff --git a/docs/htmldocs/smbd.8.html b/docs/htmldocs/smbd.8.html index 72fc10e2e42..2a7d6d59f8d 100644 --- a/docs/htmldocs/smbd.8.html +++ b/docs/htmldocs/smbd.8.html @@ -36,12 +36,12 @@ NAME="AEN8" ><B CLASS="COMMAND" >smbd</B -> [-D] [-a] [-i] [-o] [-P] [-h] [-V] [-b] [-d <debug level>] [-l <log directory>] [-p <port number>] [-O <socket option>] [-s <configuration file>]</P +> [-D] [-a] [-i] [-o] [-P] [-h] [-V] [-d <debug level>] [-l <log directory>] [-p <port number>] [-O <socket option>] [-s <configuration file>]</P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN24" +NAME="AEN23" ></A ><H2 >DESCRIPTION</H2 @@ -84,7 +84,7 @@ CLASS="FILENAME" >smb.conf(5)</TT ></A > - manpage should be regarded as mandatory reading before + manpage should be regarded as mandatory reading before proceeding with installation.</P ><P >A session is created whenever a client requests one. @@ -106,7 +106,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN38" +NAME="AEN37" ></A ><H2 >OPTIONS</H2 @@ -198,13 +198,6 @@ CLASS="COMMAND" >.</P ></DD ><DT ->-b</DT -><DD -><P ->Prints information about how - Samba was built.</P -></DD -><DT >-d <debug level></DT ><DD ><P @@ -221,7 +214,7 @@ CLASS="REPLACEABLE" logged to the log files about the activities of the server. At level 0, only critical errors and serious warnings will be logged. Level 1 is a reasonable level for - day to day running - it generates a small amount of + day to day running - it generates a small amount of information about operations carried out.</P ><P >Levels above 1 will generate considerable @@ -306,14 +299,14 @@ CLASS="REPLACEABLE" ><I >port number</I ></TT -> is a positive integer +> is a positive integer value. The default value if this parameter is not specified is 139.</P ><P >This number is the port number that will be used when making connections to the server from client software. The standard (well-known) port number for the - SMB over TCP is 139, hence the default. If you wish to + SMB over TCP is 139, hence the default. If you wish to run the server as an ordinary user rather than as root, most systems will require you to use a port number greater than 1024 - ask your system administrator @@ -345,7 +338,7 @@ CLASS="FILENAME" > smb.conf(5)</TT ></A > for more information. - The default configuration file name is determined at + The default configuration file name is determined at compile time.</P ></DD ></DL @@ -354,7 +347,7 @@ CLASS="FILENAME" ><DIV CLASS="REFSECT1" ><A -NAME="AEN120" +NAME="AEN115" ></A ><H2 >FILES</H2 @@ -370,7 +363,7 @@ CLASS="FILENAME" ></DT ><DD ><P ->If the server is to be run by the +>If the server is to be run by the <B CLASS="COMMAND" >inetd</B @@ -391,11 +384,11 @@ CLASS="FILENAME" ></DT ><DD ><P ->or whatever initialization script your +>or whatever initialization script your system uses).</P ><P ->If running the server as a daemon at startup, - this file will need to contain an appropriate startup +>If running the server as a daemon at startup, + this file will need to contain an appropriate startup sequence for the server. See the <A HREF="UNIX_INSTALL.html" TARGET="_top" @@ -410,13 +403,13 @@ CLASS="FILENAME" ></DT ><DD ><P ->If running the server via the +>If running the server via the meta-daemon <B CLASS="COMMAND" >inetd</B ->, this file - must contain a mapping of service name (e.g., netbios-ssn) - to service port (e.g., 139) and protocol type (e.g., tcp). +>, this file + must contain a mapping of service name (e.g., netbios-ssn) + to service port (e.g., 139) and protocol type (e.g., tcp). See the <A HREF="UNIX_INSTALL.html" TARGET="_top" @@ -431,7 +424,7 @@ CLASS="FILENAME" ></DT ><DD ><P ->This is the default location of the +>This is the default location of the <A HREF="smb.conf.5.html" TARGET="_top" @@ -440,17 +433,17 @@ CLASS="FILENAME" >smb.conf</TT ></A > - server configuration file. Other common places that systems + server configuration file. Other common places that systems install this file are <TT CLASS="FILENAME" >/usr/samba/lib/smb.conf</TT -> +> and <TT CLASS="FILENAME" >/etc/smb.conf</TT >.</P ><P ->This file describes all the services the server +>This file describes all the services the server is to make available to clients. See <A HREF="smb.conf.5.html" TARGET="_top" @@ -466,7 +459,7 @@ CLASS="FILENAME" ><DIV CLASS="REFSECT1" ><A -NAME="AEN156" +NAME="AEN151" ></A ><H2 >LIMITATIONS</H2 @@ -474,10 +467,10 @@ NAME="AEN156" >On some systems <B CLASS="COMMAND" >smbd</B -> cannot change uid back - to root after a setuid() call. Such systems are called - trapdoor uid systems. If you have such a system, - you will be unable to connect from a client (such as a PC) as +> cannot change uid back + to root after a setuid() call. Such systems are called + trapdoor uid systems. If you have such a system, + you will be unable to connect from a client (such as a PC) as two different users at once. Attempts to connect the second user will result in access denied or similar.</P @@ -485,7 +478,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN160" +NAME="AEN155" ></A ><H2 >ENVIRONMENT VARIABLES</H2 @@ -516,15 +509,15 @@ CLASS="CONSTANT" ><DIV CLASS="REFSECT1" ><A -NAME="AEN169" +NAME="AEN164" ></A ><H2 >PAM INTERACTION</H2 ><P ->Samba uses PAM for authentication (when presented with a plaintext +>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 + by the limitations of the SMB protocol and the <A HREF="smb.conf.5.html#OBEYPAMRESRICTIONS" TARGET="_top" @@ -550,7 +543,7 @@ TARGET="_top" ><EM >Session Management</EM >: When not using share - level secuirty, users must pass PAM's session checks before access + level secuirty, users must pass PAM's session checks before access is granted. Note however, that this is bypassed in share level secuirty. Note also that some older pam configuration files may need a line added for session support. @@ -561,41 +554,41 @@ TARGET="_top" ><DIV CLASS="REFSECT1" ><A -NAME="AEN180" +NAME="AEN175" ></A ><H2 >VERSION</H2 ><P ->This man page is correct for version 2.2 of +>This man page is correct for version 2.2 of the Samba suite.</P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN183" +NAME="AEN178" ></A ><H2 >DIAGNOSTICS</H2 ><P ->Most diagnostics issued by the server are logged - in a specified log file. The log file name is specified +>Most diagnostics issued by the server are logged + in a specified log file. The log file name is specified at compile time, but may be overridden on the command line.</P ><P ->The number and nature of diagnostics available depends - on the debug level used by the server. If you have problems, set +>The number and nature of diagnostics available depends + on the debug level used by the server. If you have problems, set the debug level to 3 and peruse the log files.</P ><P ->Most messages are reasonably self-explanatory. Unfortunately, - at the time this man page was created, there are too many diagnostics - available in the source code to warrant describing each and every - diagnostic. At this stage your best bet is still to grep the - source code and inspect the conditions that gave rise to the +>Most messages are reasonably self-explanatory. Unfortunately, + at the time this man page was created, there are too many diagnostics + available in the source code to warrant describing each and every + diagnostic. At this stage your best bet is still to grep the + source code and inspect the conditions that gave rise to the diagnostics you are seeing.</P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN188" +NAME="AEN183" ></A ><H2 >SIGNALS</H2 @@ -603,29 +596,29 @@ NAME="AEN188" >Sending the <B CLASS="COMMAND" >smbd</B -> a SIGHUP will cause it to +> a SIGHUP will cause it to reload its <TT CLASS="FILENAME" >smb.conf</TT -> configuration +> configuration file within a short period of time.</P ><P >To shut down a user's <B CLASS="COMMAND" >smbd</B -> process it is recommended +> process it is recommended that <B CLASS="COMMAND" >SIGKILL (-9)</B > <EM >NOT</EM -> +> be used, except as a last resort, as this may leave the shared - memory area in an inconsistent state. The safe way to terminate + memory area in an inconsistent state. The safe way to terminate an <B CLASS="COMMAND" >smbd</B -> is to send it a SIGTERM (-15) signal and wait for +> is to send it a SIGTERM (-15) signal and wait for it to die on its own.</P ><P >The debug log level of <B @@ -641,7 +634,7 @@ CLASS="COMMAND" </B ></A > program (SIGUSR[1|2] signals are no longer used in - Samba 2.2). This is to allow transient problems to be diagnosed, + 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, @@ -660,7 +653,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN205" +NAME="AEN200" ></A ><H2 >SEE ALSO</H2 @@ -726,7 +719,7 @@ TARGET="_top" ><DIV CLASS="REFSECT1" ><A -NAME="AEN222" +NAME="AEN217" ></A ><H2 >AUTHOR</H2 diff --git a/docs/htmldocs/smbgroupedit.8.html b/docs/htmldocs/smbgroupedit.8.html deleted file mode 100644 index 4af49672caf..00000000000 --- a/docs/htmldocs/smbgroupedit.8.html +++ /dev/null @@ -1,402 +0,0 @@ -<HTML -><HEAD -><TITLE ->smbgroupedit</TITLE -><META -NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.57"></HEAD -><BODY -CLASS="REFENTRY" -BGCOLOR="#FFFFFF" -TEXT="#000000" -LINK="#0000FF" -VLINK="#840084" -ALINK="#0000FF" -><H1 -><A -NAME="SMBGROUPEDIT" ->smbgroupedit</A -></H1 -><DIV -CLASS="REFNAMEDIV" -><A -NAME="AEN5" -></A -><H2 ->Name</H2 ->smbgroupedit -- Query/set/change UNIX - Windows NT group mapping</DIV -><DIV -CLASS="REFSYNOPSISDIV" -><A -NAME="AEN8" -></A -><H2 ->Synopsis</H2 -><P -><B -CLASS="COMMAND" ->smbroupedit</B -> [-v [l|s]] [-a UNIX-groupname [-d NT-groupname|-p prividge|]</P -></DIV -><DIV -CLASS="REFSECT1" -><A -NAME="AEN13" -></A -><H2 ->DESCRIPTION</H2 -><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 -allows setting privileges for that group, such as saAddUser, -etc.</P -></DIV -><DIV -CLASS="REFSECT1" -><A -NAME="AEN18" -></A -><H2 ->OPTIONS</H2 -><P -></P -><DIV -CLASS="VARIABLELIST" -><DL -><DT ->-v[l|s]</DT -><DD -><P ->This option will list all groups available - in the Windows NT domain in which samba is operating. - </P -><P -></P -><DIV -CLASS="VARIABLELIST" -><DL -><DT ->-l</DT -><DD -><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" - SID : - Unix group : - Group type : - Comment : - Privilege :</PRE -></TD -></TR -></TABLE -></P -><P ->For examples,</P -><P -><TABLE -BORDER="0" -BGCOLOR="#E0E0E0" -WIDTH="90%" -><TR -><TD -><PRE -CLASS="PROGRAMLISTING" ->Users - SID : S-1-5-32-545 - Unix group: -1 - Group type: Local group - Comment : - Privilege : No privilege</PRE -></TD -></TR -></TABLE -></P -></DD -><DT ->-s</DT -><DD -><P ->display a short listing of the format:</P -><P -><TABLE -BORDER="0" -BGCOLOR="#E0E0E0" -WIDTH="90%" -><TR -><TD -><PRE -CLASS="PROGRAMLISTING" ->NTGroupName(SID) -> UnixGroupName</PRE -></TD -></TR -></TABLE -></P -><P ->For example,</P -><P -><TABLE -BORDER="0" -BGCOLOR="#E0E0E0" -WIDTH="90%" -><TR -><TD -><PRE -CLASS="PROGRAMLISTING" ->Users (S-1-5-32-545) -> -1</PRE -></TD -></TR -></TABLE -></P -></DD -></DL -></DIV -></DD -></DL -></DIV -></DIV -><DIV -CLASS="REFSECT1" -><A -NAME="AEN44" -></A -><H2 ->FILES</H2 -><P -></P -></DIV -><DIV -CLASS="REFSECT1" -><A -NAME="AEN47" -></A -><H2 ->EXIT STATUS</H2 -><P -><B -CLASS="COMMAND" ->smbgroupedit</B -> returns a status of 0 if the -operation completed successfully, and a value of 1 in the event -of a failure.</P -></DIV -><DIV -CLASS="REFSECT1" -><A -NAME="AEN51" -></A -><H2 ->EXAMPLES</H2 -><P ->To make a subset of your samba PDC users members of -the 'Domain Admins' Global group:</P -><P -></P -><OL -TYPE="1" -><LI -><P ->create a unix group (usually in - <TT -CLASS="FILENAME" ->/etc/group</TT ->), let's call it <TT -CLASS="CONSTANT" ->domadm</TT ->. - </P -></LI -><LI -><P ->add to this group the users that you want to be - domain administrators. For example if you want joe, john and mary, - your entry in <TT -CLASS="FILENAME" ->/etc/group</TT -> will look like: - </P -><P ->domadm:x:502:joe,john,mary</P -></LI -><LI -><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 -><P -><TABLE -BORDER="0" -BGCOLOR="#E0E0E0" -WIDTH="90%" -><TR -><TD -><PRE -CLASS="PROGRAMLISTING" -><TT -CLASS="PROMPT" ->root# </TT -><B -CLASS="COMMAND" ->smbgroupedit -vs | grep "Domain Admins"</B -> -Domain Admins (S-1-5-21-1108995562-3116817432-1375597819-512) -> -1</PRE -></TD -></TR -></TABLE -></P -></LI -><LI -><P ->map the unix domadm group to the Windows NT - "Domain Admins" group, by running the command: - </P -><P -><TABLE -BORDER="0" -BGCOLOR="#E0E0E0" -WIDTH="90%" -><TR -><TD -><PRE -CLASS="PROGRAMLISTING" -><TT -CLASS="PROMPT" ->root# </TT -><B -CLASS="COMMAND" ->smbgroupedit \ --c S-1-5-21-1108995562-3116817432-1375597819-512 \ --u domadm</B -></PRE -></TD -></TR -></TABLE -></P -><P -> <EM ->warning:</EM -> don't copy and paste this sample, the - Domain Admins SID (the S-1-5-21-...-512) is different for every PDC. - </P -></LI -></OL -></LI -></OL -><P ->To verify that you mapping has taken effect:</P -><P -><TABLE -BORDER="0" -BGCOLOR="#E0E0E0" -WIDTH="100%" -><TR -><TD -><PRE -CLASS="PROGRAMLISTING" -><TT -CLASS="PROMPT" ->root# </TT -><B -CLASS="COMMAND" ->smbgroupedit -vs|grep "Domain Admins"</B -> -Domain Admins (S-1-5-21-1108995562-3116817432-1375597819-512) -> domadm</PRE -></TD -></TR -></TABLE -></P -><P ->To give access to a certain directory on a domain member machine (an -NT/W2K or a samba server running winbind) to some users who are member -of a group on your samba PDC, flag that group as a domain group:</P -><P -><TABLE -BORDER="0" -BGCOLOR="#E0E0E0" -WIDTH="100%" -><TR -><TD -><PRE -CLASS="PROGRAMLISTING" -><TT -CLASS="PROMPT" ->root# </TT -><B -CLASS="COMMAND" ->smbgroupedit -a unixgroup -td</B -></PRE -></TD -></TR -></TABLE -></P -></DIV -><DIV -CLASS="REFSECT1" -><A -NAME="AEN90" -></A -><H2 ->VERSION</H2 -><P ->This man page is correct for the 3.0alpha releases of -the Samba suite.</P -></DIV -><DIV -CLASS="REFSECT1" -><A -NAME="AEN93" -></A -><H2 ->SEE ALSO</H2 -><P -><A -HREF="smb.conf.5.html" -TARGET="_top" ->smb.conf(5)</A -></P -></DIV -><DIV -CLASS="REFSECT1" -><A -NAME="AEN97" -></A -><H2 ->AUTHOR</H2 -><P ->The original Samba software and related utilities -were created by Andrew Tridgell. Samba is now developed -by the Samba Team as an Open Source project similar -to the way the Linux kernel is developed.</P -><P -><B -CLASS="COMMAND" ->smbgroupedit</B -> was written by Jean Francois Micouleau. -The current set of manpages and documentation is maintained -by the Samba Team in the same fashion as the Samba source code.</P -></DIV -></BODY -></HTML ->
\ No newline at end of file diff --git a/docs/htmldocs/smbpasswd.8.html b/docs/htmldocs/smbpasswd.8.html index a8b39b37e57..c8f97c89d13 100644 --- a/docs/htmldocs/smbpasswd.8.html +++ b/docs/htmldocs/smbpasswd.8.html @@ -128,13 +128,12 @@ CLASS="VARIABLELIST" 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 - the user to already exist in the system password file (usually - <TT + password command. Note that the user to be added must already exist + in the system password file (usually <TT CLASS="FILENAME" >/etc/passwd</TT ->), else the request to add the - user will fail. </P +>) + else the request to add the user will fail. </P ><P >This option is only available when running smbpasswd as root. </P @@ -169,7 +168,8 @@ CLASS="CONSTANT" ><P >If the smbpasswd file is in the 'old' format (pre-Samba 2.0 format) there is no space in the user's password entry to write - this information and the command will FAIL. See <B + this information and so the user is disabled by writing 'X' characters + into the password space in the smbpasswd file. See <B CLASS="COMMAND" >smbpasswd(5) </B @@ -195,8 +195,15 @@ CLASS="CONSTANT" >If the smbpasswd file is in the 'old' format, then <B CLASS="COMMAND" > smbpasswd</B -> will FAIL to enable the account. - See <B +> will prompt for a new password for this user, + otherwise the account will be enabled by removing the <TT +CLASS="CONSTANT" +>'D' + </TT +> flag from account control space in the <TT +CLASS="FILENAME" +> smbpasswd</TT +> file. See <B CLASS="COMMAND" >smbpasswd (5)</B > for @@ -403,6 +410,66 @@ CLASS="FILENAME" </P ></DD ><DT +>-j DOMAIN</DT +><DD +><P +>This option is used to add a Samba server + into a Windows NT Domain, as a Domain member capable of authenticating + user accounts to any Domain Controller in the same way as a Windows + NT Server. See the <B +CLASS="COMMAND" +>security = domain</B +> option in + the <TT +CLASS="FILENAME" +>smb.conf(5)</TT +> man page. </P +><P +>In order to be used in this way, the Administrator for + the Windows NT Domain must have used the program "Server Manager + for Domains" to add the primary NetBIOS name of the Samba server + as a member of the Domain. </P +><P +>After this has been done, to join the Domain invoke <B +CLASS="COMMAND" +> smbpasswd</B +> with this parameter. smbpasswd will then + look up the Primary Domain Controller for the Domain (found in + the <TT +CLASS="FILENAME" +>smb.conf</TT +> file in the parameter + <TT +CLASS="PARAMETER" +><I +>password server</I +></TT +> and change the machine account + password used to create the secure Domain communication. This + password is then stored by smbpasswd in a TDB, writeable only by root, + called <TT +CLASS="FILENAME" +>secrets.tdb</TT +> </P +><P +>Once this operation has been performed the <TT +CLASS="FILENAME" +> smb.conf</TT +> file may be updated to set the <B +CLASS="COMMAND" +> security = domain</B +> option and all future logins + to the Samba server will be authenticated to the Windows NT + PDC. </P +><P +>Note that even though the authentication is being + done to the PDC all users accessing the Samba server must still + have a valid UNIX account on that machine. </P +><P +>This option is only available when running smbpasswd as root. + </P +></DD +><DT >-U username</DT ><DD ><P @@ -503,7 +570,7 @@ CLASS="PARAMETER" ><DIV CLASS="REFSECT1" ><A -NAME="AEN163" +NAME="AEN182" ></A ><H2 >NOTES</H2 @@ -546,18 +613,18 @@ CLASS="FILENAME" ><DIV CLASS="REFSECT1" ><A -NAME="AEN173" +NAME="AEN192" ></A ><H2 >VERSION</H2 ><P ->This man page is correct for version 3.0 of +>This man page is correct for version 2.2 of the Samba suite.</P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN176" +NAME="AEN195" ></A ><H2 >SEE ALSO</H2 @@ -580,7 +647,7 @@ TARGET="_top" ><DIV CLASS="REFSECT1" ><A -NAME="AEN182" +NAME="AEN201" ></A ><H2 >AUTHOR</H2 diff --git a/docs/htmldocs/smbsh.1.html b/docs/htmldocs/smbsh.1.html index 66081bbe22c..ba2cc7b4928 100644 --- a/docs/htmldocs/smbsh.1.html +++ b/docs/htmldocs/smbsh.1.html @@ -37,12 +37,12 @@ NAME="AEN8" ><B CLASS="COMMAND" >smbsh</B -> </P +> [-W workgroup] [-U username] [-P prefix] [-R <name resolve order>] [-d <debug level>] [-l logfile] [-L libdir]</P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN11" +NAME="AEN18" ></A ><H2 >DESCRIPTION</H2 @@ -72,6 +72,223 @@ CLASS="COMMAND" >smbsh</B > to work correctly.</P +></DIV +><DIV +CLASS="REFSECT1" +><A +NAME="AEN28" +></A +><H2 +>OPTIONS</H2 +><P +></P +><DIV +CLASS="VARIABLELIST" +><DL +><DT +>-W WORKGROUP</DT +><DD +><P +>Override the default workgroup specified in the + workgroup parameter of the <TT +CLASS="FILENAME" +>smb.conf</TT +> file + for this session. This may be needed to connect to some + servers. </P +></DD +><DT +>-U username[%pass]</DT +><DD +><P +>Sets the SMB username or username and password. + If this option is not specified, the user will be prompted for + both the username and the password. If %pass is not specified, + the user will be prompted for the password. + </P +></DD +><DT +>-P prefix</DT +><DD +><P +>This option allows + the user to set the directory prefix for SMB access. The + default value if this option is not specified is + <EM +>smb</EM +>. + </P +></DD +><DT +>-R <name resolve order></DT +><DD +><P +>This option is used to determine what naming + services and in what order to resolve + 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". + They cause names to be resolved as follows :</P +><P +></P +><UL +><LI +><P +><TT +CLASS="CONSTANT" +>lmhosts</TT +> : + Lookup an IP address in the Samba lmhosts file. If the + line in lmhosts has no name type attached to the + NetBIOS name + (see the <A +HREF="lmhosts.5.html" +TARGET="_top" +>lmhosts(5)</A +> + for details) then any name type matches for lookup. + </P +></LI +><LI +><P +><TT +CLASS="CONSTANT" +>host</TT +> : + Do a standard host name to IP address resolution, using + the system <TT +CLASS="FILENAME" +>/etc/hosts</TT +>, NIS, or DNS + lookups. This method of name resolution is operating + system dependent, for instance on IRIX or Solaris this + may be controlled by the <TT +CLASS="FILENAME" +>/etc/nsswitch.conf + </TT +> file). Note that this method is only used + if the NetBIOS name type being queried is the 0x20 + (server) name type, otherwise it is ignored. + </P +></LI +><LI +><P +><TT +CLASS="CONSTANT" +>wins</TT +> : + Query a name with the IP address listed in the + <TT +CLASS="PARAMETER" +><I +>wins server</I +></TT +> parameter. If no + WINS server has been specified this method will be + ignored. + </P +></LI +><LI +><P +><TT +CLASS="CONSTANT" +>bcast</TT +> : + Do a broadcast on each of the known local interfaces + listed in the <TT +CLASS="PARAMETER" +><I +>interfaces</I +></TT +> + parameter. This is the least reliable of the name + resolution methods as it depends on the target host + being on a locally connected subnet. + </P +></LI +></UL +><P +>If this parameter is not set then the name resolve order + defined in the <TT +CLASS="FILENAME" +>smb.conf</TT +> file parameter + (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 +CLASS="PARAMETER" +><I +>name resolve order + </I +></TT +> parameter of the <TT +CLASS="FILENAME" +>smb.conf</TT +> + file, the name resolution methods will be attempted in this + order. </P +></DD +><DT +>-d <debug level></DT +><DD +><P +>debug level is an integer from 0 to 10.</P +><P +>The default value if this parameter is not specified + is zero.</P +><P +>The higher this value, the more detail will be logged + about the activities of <B +CLASS="COMMAND" +>nmblookup</B +>. At level + 0, only critical errors and serious warnings will be logged. + </P +></DD +><DT +>-l logfilename</DT +><DD +><P +>If specified causes all debug messages to be + written to the file specified by <TT +CLASS="REPLACEABLE" +><I +>logfilename + </I +></TT +>. If not specified then all messages will be + written to<TT +CLASS="REPLACEABLE" +><I +>stderr</I +></TT +>. + </P +></DD +><DT +>-L libdir</DT +><DD +><P +>This parameter specifies the location of the + shared libraries used by <B +CLASS="COMMAND" +>smbsh</B +>. The default + value is specified at compile time. + </P +></DD +></DL +></DIV +></DIV +><DIV +CLASS="REFSECT1" +><A +NAME="AEN91" +></A +><H2 +>EXAMPLES</H2 ><P >To use the <B CLASS="COMMAND" @@ -158,7 +375,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN40" +NAME="AEN112" ></A ><H2 >VERSION</H2 @@ -169,7 +386,7 @@ NAME="AEN40" ><DIV CLASS="REFSECT1" ><A -NAME="AEN43" +NAME="AEN115" ></A ><H2 >BUGS</H2 @@ -202,7 +419,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN52" +NAME="AEN124" ></A ><H2 >SEE ALSO</H2 @@ -225,7 +442,7 @@ TARGET="_top" ><DIV CLASS="REFSECT1" ><A -NAME="AEN58" +NAME="AEN130" ></A ><H2 >AUTHOR</H2 diff --git a/docs/htmldocs/wbinfo.1.html b/docs/htmldocs/wbinfo.1.html index 4cc0ef423f5..fe218a8f676 100644 --- a/docs/htmldocs/wbinfo.1.html +++ b/docs/htmldocs/wbinfo.1.html @@ -36,12 +36,12 @@ NAME="AEN8" ><B CLASS="COMMAND" >wbinfo</B -> [-u] [-g] [-n name] [-s sid] [-U uid] [-G gid] [-S sid] [-Y sid] [-t] [-m] [-a user%password] [-p]</P +> [-u] [-g] [-h name] [-i ip] [-n name] [-s sid] [-U uid] [-G gid] [-S sid] [-Y sid] [-t] [-m] [-r user] [-a user%password] [-A user%password]</P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN23" +NAME="AEN26" ></A ><H2 >DESCRIPTION</H2 @@ -78,7 +78,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN34" +NAME="AEN37" ></A ><H2 >OPTIONS</H2 @@ -122,6 +122,52 @@ CLASS="COMMAND" >. </P ></DD ><DT +>-h name</DT +><DD +><P +>The <TT +CLASS="PARAMETER" +><I +>-h</I +></TT +> option + 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 +CLASS="PARAMETER" +><I +>name</I +></TT +> parameter. + </P +></DD +><DT +>-i ip</DT +><DD +><P +>The <TT +CLASS="PARAMETER" +><I +>-i</I +></TT +> option + 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 +CLASS="PARAMETER" +><I +>ip</I +></TT +> parameter. + </P +></DD +><DT >-n name</DT ><DD ><P @@ -228,6 +274,15 @@ CLASS="COMMAND" </P ></DD ><DT +>-r username</DT +><DD +><P +>Try to obtain the list of UNIX group ids + to which the user belongs. This only works for users + defined on a Domain Controller. + </P +></DD +><DT >-a username%password</DT ><DD ><P @@ -236,11 +291,14 @@ CLASS="COMMAND" </P ></DD ><DT ->-p</DT +>-A username%password</DT ><DD ><P ->Attempt a simple 'ping' check that the winbindd - is indeed alive. +>Store username and password used by winbindd + during session setup to a domain controller. This enables + winbindd to operate in a Windows 2000 domain with Restrict + Anonymous turned on (a.k.a. Permissions compatiable with + Windows 2000 servers only). </P ></DD ></DL @@ -249,7 +307,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN98" +NAME="AEN119" ></A ><H2 >EXIT STATUS</H2 @@ -268,7 +326,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN103" +NAME="AEN124" ></A ><H2 >VERSION</H2 @@ -279,7 +337,7 @@ NAME="AEN103" ><DIV CLASS="REFSECT1" ><A -NAME="AEN106" +NAME="AEN127" ></A ><H2 >SEE ALSO</H2 @@ -297,7 +355,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN111" +NAME="AEN132" ></A ><H2 >AUTHOR</H2 diff --git a/docs/htmldocs/winbind.html b/docs/htmldocs/winbind.html index 60638282227..5148b4bc85f 100644 --- a/docs/htmldocs/winbind.html +++ b/docs/htmldocs/winbind.html @@ -820,7 +820,7 @@ CLASS="PROMPT" >root#</TT > <B CLASS="COMMAND" ->/usr/local/samba/bin/net rpc join -s PDC -U Administrator</B +>/usr/local/samba/bin/smbpasswd -j DOMAIN -r PDC -U Administrator</B ></P ><P >The proper response to the command should be: "Joined the domain @@ -903,7 +903,7 @@ CEO+TsInternetUser</PRE >Obviously, I have named my domain 'CEO' and my <TT CLASS="PARAMETER" ><I ->winbind +>winbindd separator</I ></TT > is '+'.</P diff --git a/docs/htmldocs/winbindd.8.html b/docs/htmldocs/winbindd.8.html index 51a70042b18..5d76dae2fdc 100644 --- a/docs/htmldocs/winbindd.8.html +++ b/docs/htmldocs/winbindd.8.html @@ -109,6 +109,22 @@ CLASS="FILENAME" CLASS="VARIABLELIST" ><DL ><DT +>hosts</DT +><DD +><P +>User information traditionally stored in + the <TT +CLASS="FILENAME" +>hosts(5)</TT +> file and used by + <B +CLASS="COMMAND" +>gethostbyname(3)</B +> functions. Names are + resolved through the WINS server or by broadcast. + </P +></DD +><DT >passwd</DT ><DD ><P @@ -169,11 +185,22 @@ group: files winbind ></TR ></TABLE ></P +><P +>The following simple configuration in the + <TT +CLASS="FILENAME" +>/etc/nsswitch.conf</TT +> file can be used to initially + resolve hostnames from <TT +CLASS="FILENAME" +>/etc/hosts</TT +> and then from the + WINS server.</P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN48" +NAME="AEN57" ></A ><H2 >OPTIONS</H2 @@ -212,7 +239,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN61" +NAME="AEN70" ></A ><H2 >NAME AND ID RESOLUTION</H2 @@ -243,7 +270,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN67" +NAME="AEN76" ></A ><H2 >CONFIGURATION</H2 @@ -502,30 +529,6 @@ CLASS="COMMAND" > </P ></DD -><DT ->winbind use default domain</DT -><DD -><P ->This parameter specifies whether the <B -CLASS="COMMAND" ->winbindd</B -> - 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 = <falseg> - </B -></P -><P ->Example: <B -CLASS="COMMAND" ->winbind use default domain = true</B -></P -></DD ></DL ></DIV ></DIV |