diff options
Diffstat (limited to 'docs/htmldocs')
70 files changed, 17610 insertions, 40177 deletions
diff --git a/docs/htmldocs/Samba-Developers-Guide.html b/docs/htmldocs/Samba-Developers-Guide.html index 142d9dc537..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.7"></HEAD +CONTENT="Modular DocBook HTML Stylesheet Version 1.77"></HEAD ><BODY CLASS="BOOK" BGCOLOR="#FFFFFF" @@ -24,8 +24,8 @@ CLASS="TITLEPAGE" CLASS="TITLE" ><A NAME="SAMBA-DEVELOPERS-GUIDE" ->SAMBA Developers Guide</A -></H1 +></A +>SAMBA Developers Guide</H1 ><H3 CLASS="AUTHOR" ><A @@ -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,92 +810,7 @@ HREF="#AEN3162" ><A NAME="SMBPASSWDFILEFORMAT" ></A ->>The smbpasswd file</A -></DT -></DL -></DD -><DT ->14. <A -HREF="#MODULES" ->Modules</A -></DT -><DD -><DL -><DT ->14.1. <A -HREF="#AEN3225" ->Advantages</A -></DT -><DT ->14.2. <A -HREF="#AEN3234" ->Loading modules</A -></DT -><DD -><DL -><DT ->14.2.1. <A -HREF="#AEN3240" ->Static modules</A -></DT -><DT ->14.2.2. <A -HREF="#AEN3247" ->Shared modules</A -></DT -></DL -></DD -><DT ->14.3. <A -HREF="#AEN3251" ->Writing modules</A -></DT -><DD -><DL -><DT ->14.3.1. <A -HREF="#AEN3262" ->Static/Shared selection in configure.in</A -></DT -></DL -></DD -></DL -></DD -><DT ->15. <A -HREF="#RPC-PLUGIN" ->RPC Pluggable Modules</A -></DT -><DD -><DL -><DT ->15.1. <A -HREF="#AEN3301" ->About</A -></DT -><DT ->15.2. <A -HREF="#AEN3304" ->General Overview</A -></DT -></DL -></DD -><DT ->16. <A -HREF="#PACKAGING" ->Notes to packagers</A -></DT -><DD -><DL -><DT ->16.1. <A -HREF="#AEN3337" ->Versioning</A -></DT -><DT ->16.2. <A -HREF="#AEN3343" ->Modules</A +>The smbpasswd file</A ></DT ></DL ></DD @@ -914,8 +829,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN24" ->1.1. NETBIOS</A -></H2 +></A +>1.1. NETBIOS</H2 ><P >NetBIOS runs over the following tranports: TCP/IP; NetBEUI and IPX/SPX. Samba only uses NetBIOS over TCP/IP. For details on the TCP/IP NetBIOS @@ -970,8 +885,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN35" ->1.2. BROADCAST NetBIOS</A -></H2 +></A +>1.2. BROADCAST NetBIOS</H2 ><P > Clients can claim names, and therefore offer services on successfully claimed @@ -993,8 +908,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN39" ->1.3. NBNS NetBIOS</A -></H2 +></A +>1.3. NBNS NetBIOS</H2 ><P >rfc1001.txt describes, amongst other things, the implementation and use of, a 'NetBIOS Name Service'. NT/AS offers 'Windows Internet Name Service' @@ -1053,8 +968,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN54" ->2.1. Introduction</A -></H2 +></A +>2.1. Introduction</H2 ><P >This document gives a general overview of how Samba works internally. The Samba Team has tried to come up with a model which is @@ -1088,8 +1003,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN65" ->2.2. Multithreading and Samba</A -></H2 +></A +>2.2. Multithreading and Samba</H2 ><P >People sometimes tout threads as a uniformly good thing. They are very nice in their place but are quite inappropriate for smbd. nmbd is @@ -1114,8 +1029,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN70" ->2.3. Threading smbd</A -></H2 +></A +>2.3. Threading smbd</H2 ><P >A few problems that would arise from a threaded smbd are:</P ><P @@ -1165,8 +1080,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN86" ->2.4. Threading nmbd</A -></H2 +></A +>2.4. Threading nmbd</H2 ><P >This would be ideal, but gets sunk by portability requirements.</P ><P @@ -1201,8 +1116,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN92" ->2.5. nbmd Design</A -></H2 +></A +>2.5. nbmd Design</H2 ><P >Originally Andrew used recursion to simulate a multi-threaded environment, which use the stack enormously and made for really @@ -1239,22 +1154,22 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN103" ->3.1. New Output Syntax</A -></H2 +></A +>3.1. New Output Syntax</H2 ><P > The syntax of a debugging log file is represented as:</P ><P ><PRE CLASS="PROGRAMLISTING" -> >debugfile< :== { >debugmsg< } +> >debugfile< :== { >debugmsg< } - >debugmsg< :== >debughdr< '\n' >debugtext< + >debugmsg< :== >debughdr< '\n' >debugtext< - >debughdr< :== '[' TIME ',' LEVEL ']' FILE ':' [FUNCTION] '(' LINE ')' + >debughdr< :== '[' TIME ',' LEVEL ']' FILE ':' [FUNCTION] '(' LINE ')' - >debugtext< :== { >debugline< } + >debugtext< :== { >debugline< } - >debugline< :== TEXT '\n'</PRE + >debugline< :== TEXT '\n'</PRE ></P ><P >TEXT is a string of characters excluding the newline character.</P @@ -1324,8 +1239,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN128" ->3.2. The DEBUG() Macro</A -></H2 +></A +>3.2. The DEBUG() Macro</H2 ><P >Use of the DEBUG() macro is unchanged. DEBUG() takes two parameters. The first is the message level, the second is the body of a function @@ -1404,8 +1319,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN151" ->3.3. The DEBUGADD() Macro</A -></H2 +></A +>3.3. The DEBUGADD() Macro</H2 ><P >In addition to the kludgey solution to the broken line problem described above, there is a clean solution. The DEBUGADD() macro never @@ -1435,8 +1350,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN159" ->3.4. The DEBUGLVL() Macro</A -></H2 +></A +>3.4. The DEBUGLVL() Macro</H2 ><P >One of the problems with the DEBUG() macro was that DEBUG() lines tended to get a bit long. Consider this example from @@ -1503,16 +1418,16 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN179" ->3.5. New Functions</A -></H2 +></A +>3.5. New Functions</H2 ><DIV CLASS="SECT2" ><H3 CLASS="SECT2" ><A NAME="AEN181" ->3.5.1. dbgtext()</A -></H3 +></A +>3.5.1. dbgtext()</H3 ><P >This function prints debug message text to the debug file (and possibly to syslog) via the format buffer. The function uses a @@ -1529,8 +1444,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN184" ->3.5.2. dbghdr()</A -></H3 +></A +>3.5.2. dbghdr()</H3 ><P >This is the function that writes a debug message header. Headers are not processed via the format buffer. Also note that @@ -1546,8 +1461,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN188" ->3.5.3. format_debug_text()</A -></H3 +></A +>3.5.3. format_debug_text()</H3 ><P >This is a static function in debug.c. It stores the output text for the body of the message in a buffer until it encounters a @@ -1792,8 +1707,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN284" ->5.1. Character Handling</A -></H2 +></A +>5.1. Character Handling</H2 ><P >This section describes character set handling in Samba, as implemented in Samba 3.0 and above</P @@ -1811,8 +1726,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN288" ->5.2. The new functions</A -></H2 +></A +>5.2. The new functions</H2 ><P >The new system works like this:</P ><P @@ -1922,8 +1837,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN317" ->5.3. Macros in byteorder.h</A -></H2 +></A +>5.3. Macros in byteorder.h</H2 ><P >This section describes the macros defined in byteorder.h. These macros are used extensively in the Samba code.</P @@ -1933,8 +1848,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN320" ->5.3.1. CVAL(buf,pos)</A -></H3 +></A +>5.3.1. CVAL(buf,pos)</H3 ><P >returns the byte at offset pos within buffer buf as an unsigned character.</P ></DIV @@ -1944,8 +1859,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN323" ->5.3.2. PVAL(buf,pos)</A -></H3 +></A +>5.3.2. PVAL(buf,pos)</H3 ><P >returns the value of CVAL(buf,pos) cast to type unsigned integer.</P ></DIV @@ -1955,8 +1870,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN326" ->5.3.3. SCVAL(buf,pos,val)</A -></H3 +></A +>5.3.3. SCVAL(buf,pos,val)</H3 ><P >sets the byte at offset pos within buffer buf to value val.</P ></DIV @@ -1966,8 +1881,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN329" ->5.3.4. SVAL(buf,pos)</A -></H3 +></A +>5.3.4. SVAL(buf,pos)</H3 ><P > returns the value of the unsigned short (16 bit) little-endian integer at offset pos within buffer buf. An integer of this type is sometimes @@ -1979,8 +1894,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN332" ->5.3.5. IVAL(buf,pos)</A -></H3 +></A +>5.3.5. IVAL(buf,pos)</H3 ><P >returns the value of the unsigned 32 bit little-endian integer at offset pos within buffer buf.</P @@ -1991,8 +1906,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN335" ->5.3.6. SVALS(buf,pos)</A -></H3 +></A +>5.3.6. SVALS(buf,pos)</H3 ><P >returns the value of the signed short (16 bit) little-endian integer at offset pos within buffer buf.</P @@ -2003,8 +1918,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN338" ->5.3.7. IVALS(buf,pos)</A -></H3 +></A +>5.3.7. IVALS(buf,pos)</H3 ><P >returns the value of the signed 32 bit little-endian integer at offset pos within buffer buf.</P @@ -2015,8 +1930,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN341" ->5.3.8. SSVAL(buf,pos,val)</A -></H3 +></A +>5.3.8. SSVAL(buf,pos,val)</H3 ><P >sets the unsigned short (16 bit) little-endian integer at offset pos within buffer buf to value val.</P @@ -2027,8 +1942,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN344" ->5.3.9. SIVAL(buf,pos,val)</A -></H3 +></A +>5.3.9. SIVAL(buf,pos,val)</H3 ><P >sets the unsigned 32 bit little-endian integer at offset pos within buffer buf to the value val.</P @@ -2039,8 +1954,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN347" ->5.3.10. SSVALS(buf,pos,val)</A -></H3 +></A +>5.3.10. SSVALS(buf,pos,val)</H3 ><P >sets the short (16 bit) signed little-endian integer at offset pos within buffer buf to the value val.</P @@ -2051,8 +1966,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN350" ->5.3.11. SIVALS(buf,pos,val)</A -></H3 +></A +>5.3.11. SIVALS(buf,pos,val)</H3 ><P >sets the signed 32 bit little-endian integer at offset pos withing buffer buf to the value val.</P @@ -2063,8 +1978,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN353" ->5.3.12. RSVAL(buf,pos)</A -></H3 +></A +>5.3.12. RSVAL(buf,pos)</H3 ><P >returns the value of the unsigned short (16 bit) big-endian integer at offset pos within buffer buf.</P @@ -2075,8 +1990,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN356" ->5.3.13. RIVAL(buf,pos)</A -></H3 +></A +>5.3.13. RIVAL(buf,pos)</H3 ><P >returns the value of the unsigned 32 bit big-endian integer at offset pos within buffer buf.</P @@ -2087,8 +2002,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN359" ->5.3.14. RSSVAL(buf,pos,val)</A -></H3 +></A +>5.3.14. RSSVAL(buf,pos,val)</H3 ><P >sets the value of the unsigned short (16 bit) big-endian integer at offset pos within buffer buf to value val. @@ -2100,8 +2015,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN362" ->5.3.15. RSIVAL(buf,pos,val)</A -></H3 +></A +>5.3.15. RSIVAL(buf,pos,val)</H3 ><P >sets the value of the unsigned 32 bit big-endian integer at offset pos within buffer buf to value val.</P @@ -2113,8 +2028,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN365" ->5.4. LAN Manager Samba API</A -></H2 +></A +>5.4. LAN Manager Samba API</H2 ><P >This section describes the functions need to make a LAN Manager RPC call. This information had been obtained by examining the Samba code and the LAN @@ -2135,8 +2050,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN371" ->5.4.1. Parameters</A -></H3 +></A +>5.4.1. Parameters</H3 ><P >The parameters are as follows:</P ><P @@ -2229,8 +2144,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN406" ->5.4.2. Return value</A -></H3 +></A +>5.4.2. Return value</H3 ><P >The returned parameters (pointed to by rparam), in their order of appearance are:</P @@ -2282,8 +2197,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN420" ->5.5. Code character table</A -></H2 +></A +>5.5. Code character table</H2 ><P >Certain data structures are described by means of ASCIIz strings containing code characters. These are the code characters:</P @@ -2347,8 +2262,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN451" ->6.1. Lexical Analysis</A -></H2 +></A +>6.1. Lexical Analysis</H2 ><P >Basically, the file is processed on a line by line basis. There are four types of lines that are recognized by the lexical analyzer @@ -2406,8 +2321,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN472" ->6.1.1. Handling of Whitespace</A -></H3 +></A +>6.1.1. Handling of Whitespace</H3 ><P >Whitespace is defined as all characters recognized by the isspace() function (see ctype(3C)) except for the newline character ('\n') @@ -2443,8 +2358,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN484" ->6.1.2. Handling of Line Continuation</A -></H3 +></A +>6.1.2. Handling of Line Continuation</H3 ><P >Long section header and parameter lines may be extended across multiple lines by use of the backslash character ('\\'). Line @@ -2483,8 +2398,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN495" ->6.1.3. Line Continuation Quirks</A -></H3 +></A +>6.1.3. Line Continuation Quirks</H3 ><P >Note the following example:</P ><P @@ -2543,17 +2458,17 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN515" ->6.2. Syntax</A -></H2 +></A +>6.2. Syntax</H2 ><P >The syntax of the smb.conf file is as follows:</P ><P ><PRE CLASS="PROGRAMLISTING" -> <file> :== { <section> } EOF - <section> :== <section header> { <parameter line> } - <section header> :== '[' NAME ']' - <parameter line> :== NAME '=' VALUE NL</PRE +> <file> :== { <section> } EOF + <section> :== <section header> { <parameter line> } + <section header> :== '[' NAME ']' + <parameter line> :== NAME '=' VALUE NL</PRE ></P ><P >Basically, this means that</P @@ -2590,8 +2505,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN530" ->6.2.1. About params.c</A -></H3 +></A +>6.2.1. About params.c</H3 ><P >The parsing of the config file is a bit unusual if you are used to lex, yacc, bison, etc. Both lexical analysis (scanning) and parsing @@ -2613,8 +2528,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN540" ->7.1. Introduction</A -></H2 +></A +>7.1. Introduction</H2 ><P >This is a short document that describes some of the issues that confront a SMB implementation on unix, and how Samba copes with @@ -2630,8 +2545,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN544" ->7.2. Usernames</A -></H2 +></A +>7.2. Usernames</H2 ><P >The SMB protocol has only a loose username concept. Early SMB protocols (such as CORE and COREPLUS) have no username concept at @@ -2676,8 +2591,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN552" ->7.3. File Ownership</A -></H2 +></A +>7.3. File Ownership</H2 ><P >The commonly used SMB protocols have no way of saying "you can't do that because you don't own the file". They have, in fact, no concept @@ -2703,8 +2618,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN557" ->7.4. Passwords</A -></H2 +></A +>7.4. Passwords</H2 ><P >Many SMB clients uppercase passwords before sending them. I have no idea why they do this. Interestingly WfWg uppercases the password only @@ -2734,8 +2649,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN563" ->7.5. Locking</A -></H2 +></A +>7.5. Locking</H2 ><P >Since samba 2.2, samba supports other types of locking as well. This section is outdated.</P @@ -2774,8 +2689,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN571" ->7.6. Deny Modes</A -></H2 +></A +>7.6. Deny Modes</H2 ><P >When a SMB client opens a file it asks for a particular "deny mode" to be placed on the file. These modes (DENY_NONE, DENY_READ, DENY_WRITE, @@ -2797,8 +2712,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN575" ->7.7. Trapdoor UIDs</A -></H2 +></A +>7.7. Trapdoor UIDs</H2 ><P >A SMB session can run with several uids on the one socket. This happens when a user connects to two shares with different @@ -2816,8 +2731,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN579" ->7.8. Port numbers</A -></H2 +></A +>7.8. Port numbers</H2 ><P >There is a convention that clients on sockets use high "unprivilaged" port numbers (>1000) and connect to servers on low "privilaged" port @@ -2848,8 +2763,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN584" ->7.9. Protocol Complexity</A -></H2 +></A +>7.9. Protocol Complexity</H2 ><P >There are many "protocol levels" in the SMB protocol. It seems that each time new functionality was added to a Microsoft operating system, @@ -3029,8 +2944,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN652" ->9.1. Introduction</A -></H2 +></A +>9.1. Introduction</H2 ><P >This document contains information to provide an NT workstation with login services, without the need for an NT server. It is the sgml version of <A @@ -3153,8 +3068,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN688" ->9.1.1. Sources</A -></H3 +></A +>9.1.1. Sources</H3 ><P ></P ><TABLE @@ -3187,8 +3102,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN695" ->9.1.2. Credits</A -></H3 +></A +>9.1.2. Credits</H3 ><P ></P ><TABLE @@ -3222,16 +3137,16 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN702" ->9.2. Notes and Structures</A -></H2 +></A +>9.2. Notes and Structures</H2 ><DIV CLASS="SECT2" ><H3 CLASS="SECT2" ><A NAME="AEN704" ->9.2.1. Notes</A -></H3 +></A +>9.2.1. Notes</H3 ><P ></P ><OL @@ -3282,16 +3197,16 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN717" ->9.2.2. Enumerations</A -></H3 +></A +>9.2.2. Enumerations</H3 ><DIV CLASS="SECT3" ><H4 CLASS="SECT3" ><A NAME="AEN719" ->9.2.2.1. MSRPC Header type</A -></H4 +></A +>9.2.2.1. MSRPC Header type</H4 ><P >command number in the msrpc packet header</P ><P @@ -3332,8 +3247,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN739" ->9.2.2.2. MSRPC Packet info</A -></H4 +></A +>9.2.2.2. MSRPC Packet info</H4 ><P >The meaning of these flags is undocumented</P ><P @@ -3399,16 +3314,16 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN775" ->9.2.3. Structures</A -></H3 +></A +>9.2.3. Structures</H3 ><DIV CLASS="SECT3" ><H4 CLASS="SECT3" ><A NAME="AEN777" ->9.2.3.1. VOID *</A -></H4 +></A +>9.2.3.1. VOID *</H4 ><P >sizeof VOID* is 32 bits.</P ></DIV @@ -3418,8 +3333,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN780" ->9.2.3.2. char</A -></H4 +></A +>9.2.3.2. char</H4 ><P >sizeof char is 8 bits.</P ></DIV @@ -3429,8 +3344,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN783" ->9.2.3.3. UTIME</A -></H4 +></A +>9.2.3.3. UTIME</H4 ><P >UTIME is 32 bits, indicating time in seconds since 01jan1970. documented in cifs6.txt (section 3.5 page, page 30).</P ></DIV @@ -3440,8 +3355,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN786" ->9.2.3.4. NTTIME</A -></H4 +></A +>9.2.3.4. NTTIME</H4 ><P >NTTIME is 64 bits. documented in cifs6.txt (section 3.5 page, page 30).</P ></DIV @@ -3451,8 +3366,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN789" ->9.2.3.5. DOM_SID (domain SID structure)</A -></H4 +></A +>9.2.3.5. DOM_SID (domain SID structure)</H4 ><P ></P ><DIV @@ -3505,8 +3420,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN814" ->9.2.3.6. STR (string)</A -></H4 +></A +>9.2.3.6. STR (string)</H4 ><P >STR (string) is a char[] : a null-terminated string of ascii characters.</P ></DIV @@ -3516,8 +3431,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN817" ->9.2.3.7. UNIHDR (unicode string header)</A -></H4 +></A +>9.2.3.7. UNIHDR (unicode string header)</H4 ><P ></P ><DIV @@ -3550,8 +3465,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN832" ->9.2.3.8. UNIHDR2 (unicode string header plus buffer pointer)</A -></H4 +></A +>9.2.3.8. UNIHDR2 (unicode string header plus buffer pointer)</H4 ><P ></P ><DIV @@ -3578,8 +3493,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN843" ->9.2.3.9. UNISTR (unicode string)</A -></H4 +></A +>9.2.3.9. UNISTR (unicode string)</H4 ><P ></P ><DIV @@ -3600,8 +3515,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN850" ->9.2.3.10. NAME (length-indicated unicode string)</A -></H4 +></A +>9.2.3.10. NAME (length-indicated unicode string)</H4 ><P ></P ><DIV @@ -3628,8 +3543,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN861" ->9.2.3.11. UNISTR2 (aligned unicode string)</A -></H4 +></A +>9.2.3.11. UNISTR2 (aligned unicode string)</H4 ><P ></P ><DIV @@ -3674,8 +3589,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN884" ->9.2.3.12. OBJ_ATTR (object attributes)</A -></H4 +></A +>9.2.3.12. OBJ_ATTR (object attributes)</H4 ><P ></P ><DIV @@ -3726,8 +3641,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN911" ->9.2.3.13. POL_HND (LSA policy handle)</A -></H4 +></A +>9.2.3.13. POL_HND (LSA policy handle)</H4 ><P ></P ><DIV @@ -3748,8 +3663,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN918" ->9.2.3.14. DOM_SID2 (domain SID structure, SIDS stored in unicode)</A -></H4 +></A +>9.2.3.14. DOM_SID2 (domain SID structure, SIDS stored in unicode)</H4 ><P ></P ><DIV @@ -3804,8 +3719,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN941" ->9.2.3.15. DOM_RID (domain RID structure)</A -></H4 +></A +>9.2.3.15. DOM_RID (domain RID structure)</H4 ><P ></P ><DIV @@ -3844,8 +3759,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN960" ->9.2.3.16. LOG_INFO (server, account, client structure)</A -></H4 +></A +>9.2.3.16. LOG_INFO (server, account, client structure)</H4 ><P ><SPAN CLASS="emphasis" @@ -3906,8 +3821,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN987" ->9.2.3.17. CLNT_SRV (server, client names structure)</A -></H4 +></A +>9.2.3.17. CLNT_SRV (server, client names structure)</H4 ><P ><SPAN CLASS="emphasis" @@ -3954,8 +3869,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN1008" ->9.2.3.18. CREDS (credentials + time stamp)</A -></H4 +></A +>9.2.3.18. CREDS (credentials + time stamp)</H4 ><P ></P ><DIV @@ -3982,8 +3897,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN1019" ->9.2.3.19. CLNT_INFO2 (server, client structure, client credentials)</A -></H4 +></A +>9.2.3.19. CLNT_INFO2 (server, client structure, client credentials)</H4 ><P ><SPAN CLASS="emphasis" @@ -4031,8 +3946,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN1040" ->9.2.3.20. CLNT_INFO (server, account, client structure, client credentials)</A -></H4 +></A +>9.2.3.20. CLNT_INFO (server, account, client structure, client credentials)</H4 ><P ><SPAN CLASS="emphasis" @@ -4067,8 +3982,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN1053" ->9.2.3.21. ID_INFO_1 (id info structure, auth level 1)</A -></H4 +></A +>9.2.3.21. ID_INFO_1 (id info structure, auth level 1)</H4 ><P ></P ><DIV @@ -4149,8 +4064,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN1100" ->9.2.3.22. SAM_INFO (sam logon/logoff id info structure)</A -></H4 +></A +>9.2.3.22. SAM_INFO (sam logon/logoff id info structure)</H4 ><P ><SPAN CLASS="emphasis" @@ -4212,8 +4127,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN1127" ->9.2.3.23. GID (group id info)</A -></H4 +></A +>9.2.3.23. GID (group id info)</H4 ><P ></P ><DIV @@ -4240,8 +4155,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN1138" ->9.2.3.24. DOM_REF (domain reference info)</A -></H4 +></A +>9.2.3.24. DOM_REF (domain reference info)</H4 ><P ></P ><DIV @@ -4310,8 +4225,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN1177" ->9.2.3.25. DOM_INFO (domain info, levels 3 and 5 are the same))</A -></H4 +></A +>9.2.3.25. DOM_INFO (domain info, levels 3 and 5 are the same))</H4 ><P ></P ><DIV @@ -4368,8 +4283,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN1208" ->9.2.3.26. USER_INFO (user logon info)</A -></H4 +></A +>9.2.3.26. USER_INFO (user logon info)</H4 ><P ><SPAN CLASS="emphasis" @@ -4620,8 +4535,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN1365" ->9.2.3.27. SH_INFO_1_PTR (pointers to level 1 share info strings)</A -></H4 +></A +>9.2.3.27. SH_INFO_1_PTR (pointers to level 1 share info strings)</H4 ><P ><SPAN CLASS="emphasis" @@ -4691,8 +4606,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN1388" ->9.2.3.28. SH_INFO_1_STR (level 1 share info strings)</A -></H4 +></A +>9.2.3.28. SH_INFO_1_STR (level 1 share info strings)</H4 ><P ></P ><DIV @@ -4719,8 +4634,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN1399" ->9.2.3.29. SHARE_INFO_1_CTR</A -></H4 +></A +>9.2.3.29. SHARE_INFO_1_CTR</H4 ><P >share container with 0 entries:</P ><P @@ -4806,8 +4721,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN1445" ->9.2.3.30. SERVER_INFO_101</A -></H4 +></A +>9.2.3.30. SERVER_INFO_101</H4 ><P ><SPAN CLASS="emphasis" @@ -5019,8 +4934,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN1571" ->9.3. MSRPC over Transact Named Pipe</A -></H2 +></A +>9.3. MSRPC over Transact Named Pipe</H2 ><P >For details on the SMB Transact Named Pipe, see cifs6.txt</P ><DIV @@ -5029,8 +4944,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN1574" ->9.3.1. MSRPC Pipes</A -></H3 +></A +>9.3.1. MSRPC Pipes</H3 ><P >The MSRPC is conducted over an SMB Transact Pipe with a name of <TT @@ -5089,8 +5004,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN1588" ->9.3.2. Header</A -></H3 +></A +>9.3.2. Header</H3 ><P >[section to be rewritten, following receipt of work by Duncan Stansfield]</P ><P @@ -5260,8 +5175,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN1649" ->9.3.2.1. RPC_Packet for request, response, bind and bind acknowledgement</A -></H4 +></A +>9.3.2.1. RPC_Packet for request, response, bind and bind acknowledgement</H4 ><P ></P ><DIV @@ -5330,8 +5245,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN1688" ->9.3.2.2. Interface identification</A -></H4 +></A +>9.3.2.2. Interface identification</H4 ><P >the interfaces are numbered. as yet I haven't seen more than one interface used on the same pipe name srvsvc</P ><P @@ -5347,8 +5262,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN1693" ->9.3.2.3. RPC_Iface RW</A -></H4 +></A +>9.3.2.3. RPC_Iface RW</H4 ><P ></P ><DIV @@ -5375,8 +5290,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN1704" ->9.3.2.4. RPC_ReqBind RW</A -></H4 +></A +>9.3.2.4. RPC_ReqBind RW</H4 ><P >the remainder of the packet after the header if "type" was Bind in the response header, "type" should be BindAck</P ><P @@ -5447,8 +5362,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN1744" ->9.3.2.5. RPC_Address RW</A -></H4 +></A +>9.3.2.5. RPC_Address RW</H4 ><P ></P ><DIV @@ -5475,8 +5390,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN1755" ->9.3.2.6. RPC_ResBind RW</A -></H4 +></A +>9.3.2.6. RPC_ResBind RW</H4 ><P >the response to place after the header in the reply packet</P ><P @@ -5553,8 +5468,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN1799" ->9.3.2.7. RPC_ReqNorm RW</A -></H4 +></A +>9.3.2.7. RPC_ReqNorm RW</H4 ><P >the remainder of the packet after the header for every other other request</P ><P @@ -5595,8 +5510,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN1819" ->9.3.2.8. RPC_ResNorm RW</A -></H4 +></A +>9.3.2.8. RPC_ResNorm RW</H4 ><P ></P ><DIV @@ -5642,8 +5557,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN1842" ->9.3.3. Tail</A -></H3 +></A +>9.3.3. Tail</H3 ><P >The end of each of the NTLSA and NETLOGON named pipes ends with:</P ><P @@ -5672,8 +5587,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN1854" ->9.3.4. RPC Bind / Bind Ack</A -></H3 +></A +>9.3.4. RPC Bind / Bind Ack</H3 ><P >RPC Binds are the process of associating an RPC pipe (e.g \PIPE\lsarpc) with a "transfer syntax" (see RPC_Iface structure). The purpose for doing @@ -5802,8 +5717,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN1898" ->9.3.5. NTLSA Transact Named Pipe</A -></H3 +></A +>9.3.5. NTLSA Transact Named Pipe</H3 ><P >The sequence of actions taken on this pipe are:</P ><P @@ -5901,8 +5816,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN1939" ->9.3.6. LSA Open Policy</A -></H3 +></A +>9.3.6. LSA Open Policy</H3 ><P ><SPAN CLASS="emphasis" @@ -5917,8 +5832,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN1943" ->9.3.6.1. Request</A -></H4 +></A +>9.3.6.1. Request</H4 ><P ></P ><DIV @@ -5957,8 +5872,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN1962" ->9.3.6.2. Response</A -></H4 +></A +>9.3.6.2. Response</H4 ><P ></P ><DIV @@ -5986,8 +5901,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN1973" ->9.3.7. LSA Query Info Policy</A -></H3 +></A +>9.3.7. LSA Query Info Policy</H3 ><P ><SPAN CLASS="emphasis" @@ -6002,8 +5917,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN1977" ->9.3.7.1. Request</A -></H4 +></A +>9.3.7.1. Request</H4 ><P ></P ><DIV @@ -6030,8 +5945,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN1988" ->9.3.7.2. Response</A -></H4 +></A +>9.3.7.2. Response</H4 ><P ></P ><DIV @@ -6071,16 +5986,16 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN2001" ->9.3.8. LSA Enumerate Trusted Domains</A -></H3 +></A +>9.3.8. LSA Enumerate Trusted Domains</H3 ><DIV CLASS="SECT3" ><H4 CLASS="SECT3" ><A NAME="AEN2003" ->9.3.8.1. Request</A -></H4 +></A +>9.3.8.1. Request</H4 ><P >no extra data</P ></DIV @@ -6090,8 +6005,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN2006" ->9.3.8.2. Response</A -></H4 +></A +>9.3.8.2. Response</H4 ><P ></P ><DIV @@ -6131,16 +6046,16 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN2025" ->9.3.9. LSA Open Secret</A -></H3 +></A +>9.3.9. LSA Open Secret</H3 ><DIV CLASS="SECT3" ><H4 CLASS="SECT3" ><A NAME="AEN2027" ->9.3.9.1. Request</A -></H4 +></A +>9.3.9.1. Request</H4 ><P >no extra data</P ></DIV @@ -6150,8 +6065,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN2030" ->9.3.9.2. Response</A -></H4 +></A +>9.3.9.2. Response</H4 ><P ></P ><DIV @@ -6199,16 +6114,16 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN2054" ->9.3.10. LSA Close</A -></H3 +></A +>9.3.10. LSA Close</H3 ><DIV CLASS="SECT3" ><H4 CLASS="SECT3" ><A NAME="AEN2056" ->9.3.10.1. Request</A -></H4 +></A +>9.3.10.1. Request</H4 ><P ></P ><DIV @@ -6229,8 +6144,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN2063" ->9.3.10.2. Response</A -></H4 +></A +>9.3.10.2. Response</H4 ><P ></P ><DIV @@ -6254,8 +6169,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN2071" ->9.3.11. LSA Lookup SIDS</A -></H3 +></A +>9.3.11. LSA Lookup SIDS</H3 ><P ><SPAN CLASS="emphasis" @@ -6270,8 +6185,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN2075" ->9.3.11.1. Request</A -></H4 +></A +>9.3.11.1. Request</H4 ><P ></P ><DIV @@ -6322,8 +6237,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN2102" ->9.3.11.2. Response</A -></H4 +></A +>9.3.11.2. Response</H4 ><P ></P ><DIV @@ -6377,8 +6292,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN2130" ->9.3.12. LSA Lookup Names</A -></H3 +></A +>9.3.12. LSA Lookup Names</H3 ><P ><SPAN CLASS="emphasis" @@ -6393,8 +6308,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN2134" ->9.3.12.1. Request</A -></H4 +></A +>9.3.12.1. Request</H4 ><P ></P ><DIV @@ -6451,8 +6366,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN2165" ->9.3.12.2. Response</A -></H4 +></A +>9.3.12.2. Response</H4 ><P ></P ><DIV @@ -6507,8 +6422,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN2193" ->9.4. NETLOGON rpc Transact Named Pipe</A -></H2 +></A +>9.4. NETLOGON rpc Transact Named Pipe</H2 ><P >The sequence of actions taken on this pipe are:</P ><P @@ -6607,8 +6522,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN2232" ->9.4.1. LSA Request Challenge</A -></H3 +></A +>9.4.1. LSA Request Challenge</H3 ><P ><SPAN CLASS="emphasis" @@ -6639,8 +6554,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN2240" ->9.4.1.1. Request</A -></H4 +></A +>9.4.1.1. Request</H4 ><P ></P ><DIV @@ -6679,8 +6594,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN2259" ->9.4.1.2. Response</A -></H4 +></A +>9.4.1.2. Response</H4 ><P ></P ><DIV @@ -6704,8 +6619,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN2267" ->9.4.2. LSA Authenticate 2</A -></H3 +></A +>9.4.2. LSA Authenticate 2</H3 ><P ><SPAN CLASS="emphasis" @@ -6736,8 +6651,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN2275" ->9.4.2.1. Request</A -></H4 +></A +>9.4.2.1. Request</H4 ><P ></P ><DIV @@ -6776,8 +6691,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN2294" ->9.4.2.2. Response</A -></H4 +></A +>9.4.2.2. Response</H4 ><P ></P ><DIV @@ -6807,8 +6722,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN2306" ->9.4.3. LSA Server Password Set</A -></H3 +></A +>9.4.3. LSA Server Password Set</H3 ><P ><SPAN CLASS="emphasis" @@ -6847,8 +6762,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN2316" ->9.4.3.1. Request</A -></H4 +></A +>9.4.3.1. Request</H4 ><P ></P ><DIV @@ -6875,8 +6790,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN2327" ->9.4.3.2. Response</A -></H4 +></A +>9.4.3.2. Response</H4 ><P ></P ><DIV @@ -6900,8 +6815,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN2335" ->9.4.4. LSA SAM Logon</A -></H3 +></A +>9.4.4. LSA SAM Logon</H3 ><P ><SPAN CLASS="emphasis" @@ -6917,8 +6832,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN2339" ->9.4.4.1. Request</A -></H4 +></A +>9.4.4.1. Request</H4 ><P ></P ><DIV @@ -6939,8 +6854,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN2346" ->9.4.4.2. Response</A -></H4 +></A +>9.4.4.2. Response</H4 ><P ></P ><DIV @@ -6991,8 +6906,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN2359" ->9.4.5. LSA SAM Logoff</A -></H3 +></A +>9.4.5. LSA SAM Logoff</H3 ><P ><SPAN CLASS="emphasis" @@ -7008,8 +6923,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN2363" ->9.4.5.1. Request</A -></H4 +></A +>9.4.5.1. Request</H4 ><P ></P ><DIV @@ -7030,8 +6945,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN2370" ->9.4.5.2. Response</A -></H4 +></A +>9.4.5.2. Response</H4 ><P ></P ><DIV @@ -7062,8 +6977,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN2382" ->9.5. \\MAILSLOT\NET\NTLOGON</A -></H2 +></A +>9.5. \\MAILSLOT\NET\NTLOGON</H2 ><P ><SPAN CLASS="emphasis" @@ -7080,8 +6995,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN2386" ->9.5.1. Query for PDC</A -></H3 +></A +>9.5.1. Query for PDC</H3 ><P ><SPAN CLASS="emphasis" @@ -7096,8 +7011,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN2390" ->9.5.1.1. Request</A -></H4 +></A +>9.5.1.1. Request</H4 ><P ></P ><DIV @@ -7160,8 +7075,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN2425" ->9.5.1.2. Response</A -></H4 +></A +>9.5.1.2. Response</H4 ><P ></P ><DIV @@ -7225,8 +7140,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN2460" ->9.5.2. SAM Logon</A -></H3 +></A +>9.5.2. SAM Logon</H3 ><P ><SPAN CLASS="emphasis" @@ -7257,8 +7172,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN2468" ->9.5.2.1. Request</A -></H4 +></A +>9.5.2.1. Request</H4 ><P ></P ><DIV @@ -7345,8 +7260,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN2519" ->9.5.2.2. Response</A -></H4 +></A +>9.5.2.2. Response</H4 ><P ></P ><DIV @@ -7405,8 +7320,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN2550" ->9.6. SRVSVC Transact Named Pipe</A -></H2 +></A +>9.6. SRVSVC Transact Named Pipe</H2 ><P >Defines for this pipe, identifying the query are:</P ><P @@ -7434,8 +7349,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN2562" ->9.6.1. Net Share Enum</A -></H3 +></A +>9.6.1. Net Share Enum</H3 ><P ><SPAN CLASS="emphasis" @@ -7458,8 +7373,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN2568" ->9.6.1.1. Request</A -></H4 +></A +>9.6.1.1. Request</H4 ><P ></P ><DIV @@ -7522,8 +7437,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN2603" ->9.6.1.2. Response</A -></H4 +></A +>9.6.1.2. Response</H4 ><P ></P ><DIV @@ -7565,8 +7480,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN2623" ->9.6.2. Net Server Get Info</A -></H3 +></A +>9.6.2. Net Server Get Info</H3 ><P ><SPAN CLASS="emphasis" @@ -7581,8 +7496,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN2627" ->9.6.2.1. Request</A -></H4 +></A +>9.6.2.1. Request</H4 ><P ></P ><DIV @@ -7609,8 +7524,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN2638" ->9.6.2.2. Response</A -></H4 +></A +>9.6.2.2. Response</H4 ><P ></P ><DIV @@ -7647,16 +7562,16 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN2654" ->9.7. Cryptographic side of NT Domain Authentication</A -></H2 +></A +>9.7. Cryptographic side of NT Domain Authentication</H2 ><DIV CLASS="SECT2" ><H3 CLASS="SECT2" ><A NAME="AEN2656" ->9.7.1. Definitions</A -></H3 +></A +>9.7.1. Definitions</H3 ><P ></P ><DIV @@ -7732,50 +7647,35 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN2699" ->9.7.2. Protocol</A -></H3 -><PRE -CLASS="PROGRAMLISTING" ->C->S ReqChal,Cc -S->C Cs</PRE -><PRE -CLASS="PROGRAMLISTING" ->C & S compute session key Ks = E(PW[9..15],E(PW[0..6],Add(Cc,Cs)))</PRE -><PRE -CLASS="PROGRAMLISTING" ->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))</PRE +></A +>9.7.2. Protocol</H3 +><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 +><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 ><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 -><PRE -CLASS="PROGRAMLISTING" ->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'</PRE +><P +>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 ><P >User: U with password P wishes to login to the domain (incidental data such as workstation and domain omitted)</P -><PRE -CLASS="PROGRAMLISTING" ->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()</PRE -><PRE -CLASS="PROGRAMLISTING" ->S->C Cred(Ks,Cred(Ks,Rc+Tc+1)),userinfo(logon script,UID,SIDs,etc) -C: assert(Rs == Cred(Ks,Cred(Rc+Tc+1)) -C: Rc = Cred(Ks,Rc+Tc+1)</PRE +><P +>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 +><P +>S->C Cred(Ks,Cred(Ks,Rc+Tc+1)),userinfo(logon script,UID,SIDs,etc) C: +assert(Rs == Cred(Ks,Cred(Rc+Tc+1)) C: Rc = Cred(Ks,Rc+Tc+1)</P ></DIV ><DIV CLASS="SECT2" @@ -7783,8 +7683,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN2709" ->9.7.3. Comments</A -></H3 +></A +>9.7.3. Comments</H3 ><P >On first joining the domain the session key could be computed by anyone listening in on the network as the machine password has a well @@ -7814,8 +7714,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN2716" ->9.8. SIDs and RIDs</A -></H2 +></A +>9.8. SIDs and RIDs</H2 ><P >SIDs and RIDs are well documented elsewhere.</P ><P @@ -7846,16 +7746,16 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN2724" ->9.8.1. Well-known SIDs</A -></H3 +></A +>9.8.1. Well-known SIDs</H3 ><DIV CLASS="SECT3" ><H4 CLASS="SECT3" ><A NAME="AEN2726" ->9.8.1.1. Universal well-known SIDs</A -></H4 +></A +>9.8.1.1. Universal well-known SIDs</H4 ><P ></P ><DIV @@ -7918,8 +7818,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN2761" ->9.8.1.2. NT well-known SIDs</A -></H4 +></A +>9.8.1.2. NT well-known SIDs</H4 ><P ></P ><DIV @@ -8007,8 +7907,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN2812" ->9.8.2. Well-known RIDS</A -></H3 +></A +>9.8.2. Well-known RIDS</H3 ><P >A RID is a sub-authority value, as part of either a SID, or in the case of Group RIDs, part of the DOM_GID structure, in the USER_INFO_1 @@ -8019,8 +7919,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN2815" ->9.8.2.1. Well-known RID users</A -></H4 +></A +>9.8.2.1. Well-known RID users</H4 ><P ><B >Groupname: </B @@ -8052,8 +7952,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN2829" ->9.8.2.2. Well-known RID groups</A -></H4 +></A +>9.8.2.2. Well-known RID groups</H4 ><P ><B >Groupname: </B @@ -8097,8 +7997,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN2847" ->9.8.2.3. Well-known RID aliases</A -></H4 +></A +>9.8.2.3. Well-known RID aliases</H4 ><P ><B >Groupname: </B @@ -8224,8 +8124,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN2896" ->10.1. Abstract</A -></H2 +></A +>10.1. Abstract</H2 ><P >The purpose of this document is to provide some insight into Samba's printing functionality and also to describe the semantics @@ -8237,13 +8137,13 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN2899" ->10.2. Printing Interface to Various Back ends</A -></H2 +></A +>10.2. Printing Interface to Various Back ends</H2 ><P >Samba uses a table of function pointers to seven functions. The -function prototypes are defined in the <VAR +function prototypes are defined in the <TT CLASS="VARNAME" ->printif</VAR +>printif</TT > structure declared in <TT CLASS="FILENAME" @@ -8305,8 +8205,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN2925" ->10.3. Print Queue TDB's</A -></H2 +></A +>10.3. Print Queue TDB's</H2 ><P >Samba provides periodic caching of the output from the "lpq command" for performance reasons. This cache time is configurable in seconds. @@ -8355,7 +8255,7 @@ struct printjob { for the UNIX job id returned from the "lpq command" and a Windows job ID (32-bit bounded by PRINT_MAX_JOBID). When a print job is returned by the "lpq command" that does not match an existing job in the queue's -TDB, a 32-bit job ID above the <*vance doesn't know what word is missing here*> is generating by adding UNIX_JOB_START to +TDB, a 32-bit job ID above the <*vance doesn't know what word is missing here*> is generating by adding UNIX_JOB_START to the id reported by lpq.</P ><P >In order to match a 32-bit Windows jobid onto a 16-bit lanman print job @@ -8375,12 +8275,14 @@ TYPE="1" ><P >Check to see if another smbd is currently in the process of updating the queue contents by checking the pid - stored in <CODE + stored in <TT CLASS="CONSTANT" ->LOCK/<VAR +>LOCK/<TT CLASS="REPLACEABLE" ->printer_name</VAR -></CODE +><I +>printer_name</I +></TT +></TT >. If so, then do not update the TDB.</P ></LI @@ -8452,8 +8354,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN2959" ->10.4. ChangeID and Client Caching of Printer Information</A -></H2 +></A +>10.4. ChangeID & Client Caching of Printer Information</H2 ><P >[To be filled in later]</P ></DIV @@ -8463,8 +8365,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN2962" ->10.5. Windows NT/2K Printer Change Notify</A -></H2 +></A +>10.5. Windows NT/2K Printer Change Notify</H2 ><P >When working with Windows NT+ clients, it is possible for a print server to use RPC to send asynchronous change notification @@ -8534,7 +8436,7 @@ C: Send a RFFPCN request with the previously obtained to monitor, or (b) a PRINTER_NOTIFY_OPTIONS structure containing the event information to monitor. The windows spooler has only been observed to use (b). -S: The <* another missing word*> opens a new TCP session to the client (thus requiring +S: The <* another missing word*> opens a new TCP session to the client (thus requiring all print clients to be CIFS servers as well) and sends a ReplyOpenPrinter() request to the client. C: The client responds with a printer handle that can be used to @@ -8612,9 +8514,9 @@ information</P ></LI ></UL ><P ->A <VAR +>A <TT CLASS="VARNAME" ->SPOOL_NOTIFY_INFO</VAR +>SPOOL_NOTIFY_INFO</TT > contains:</P ><P ></P @@ -8631,9 +8533,9 @@ in the SPOOL_NOTIFY_INFO_DATA array</P ></LI ></UL ><P ->The <VAR +>The <TT CLASS="VARNAME" ->SPOOL_NOTIFY_INFO_DATA</VAR +>SPOOL_NOTIFY_INFO_DATA</TT > entries contain:</P ><P ></P @@ -8689,8 +8591,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN3033" ->11.1. WINS Failover</A -></H2 +></A +>11.1. WINS Failover</H2 ><P >The current Samba codebase possesses the capability to use groups of WINS servers that share a common namespace for NetBIOS name registration and @@ -8699,7 +8601,7 @@ resolution. The formal parameter syntax is</P ><PRE CLASS="PROGRAMLISTING" > WINS_SERVER_PARAM = SERVER [ SEPARATOR SERVER_LIST ] - WINS_SERVER_PARAM = "wins server" + WINS_SERVER_PARAM = "wins server" SERVER = ADDR[:TAG] ADDR = ip_addr | fqdn TAG = string @@ -8716,7 +8618,7 @@ CLASS="PROGRAMLISTING" ></P ><P >In the event that no TAG is defined in for a SERVER in the list, smbd assigns a default -TAG of "*". A TAG is used to group servers of a shared NetBIOS namespace together. Upon +TAG of "*". A TAG is used to group servers of a shared NetBIOS namespace together. Upon startup, nmbd will attempt to register the netbios name value with one server in each tagged group.</P ><P @@ -8730,7 +8632,7 @@ CLASS="PROGRAMLISTING" ></P ><P >Using this configuration, nmbd would attempt to register the server's NetBIOS name -with one WINS server in each group. Because the "eth0" group has two servers, the +with one WINS server in each group. Because the "eth0" group has two servers, the second server would only be used when a registration (or resolution) request to the first server in that group timed out.</P ><P @@ -8757,8 +8659,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN3054" ->12.1. Security in the 'new SAM'</A -></H2 +></A +>12.1. Security in the 'new SAM'</H2 ><P >One of the biggest problems with passdb is it's implementation of 'security'. Access control is on a 'are you root at the moment' basis, @@ -8774,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 @@ -8831,8 +8734,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN3071" ->12.2. Standalone from UNIX</A -></H2 +></A +>12.2. Standalone from UNIX</H2 ><P >One of the primary tenants of the 'new SAM' is that it would not attempt to deal with 'what unix id for that'. This would be left to the 'SMS' @@ -8850,8 +8753,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN3075" ->12.3. Handles and Races in the new SAM</A -></H2 +></A +>12.3. Handles and Races in the new SAM</H2 ><P >One of the things that the 'new SAM' work has tried to face is both compatibility with existing code, and a closer alignment to the SAMR @@ -8893,16 +8796,16 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN3086" ->12.4. Layers</A -></H2 +></A +>12.4. Layers</H2 ><DIV CLASS="SECT2" ><H3 CLASS="SECT2" ><A NAME="AEN3088" ->12.4.1. Application</A -></H3 +></A +>12.4.1. Application</H3 ><P >This is where smbd, samtest and whatever end-user replacement we have for pdbedit sits. They use only the SAM interface, and do not get @@ -8914,8 +8817,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN3091" ->12.4.2. SAM Interface</A -></H3 +></A +>12.4.2. SAM Interface</H3 ><P >This level 'owns' the various handle structures, the get/set routines on those structures and provides the public interface. The application @@ -8934,8 +8837,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN3095" ->12.4.3. SAM Modules</A -></H3 +></A +>12.4.3. SAM Modules</H3 ><P >These do not communicate with the application directly, only by setting values in the handles, and receiving requests from the interface. These @@ -8952,16 +8855,16 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN3098" ->12.5. SAM Modules</A -></H2 +></A +>12.5. SAM Modules</H2 ><DIV CLASS="SECT2" ><H3 CLASS="SECT2" ><A NAME="AEN3100" ->12.5.1. Special Module: sam_passdb</A -></H3 +></A +>12.5.1. Special Module: sam_passdb</H3 ><P >In order for there to be a smooth transition, kai is writing a module that reads existing passdb backends, and translates them into SAM @@ -8975,8 +8878,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN3103" ->12.5.2. sam_ads</A -></H3 +></A +>12.5.2. sam_ads</H3 ><P >This is the first of the SAM modules to be committed to the tree - mainly because I needed to coordinate work with metze (who authored most @@ -8997,8 +8900,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN3107" ->12.6. Memory Management</A -></H2 +></A +>12.6. Memory Management</H2 ><P > The 'new SAM' development effort also concerned itself with getting a @@ -9053,8 +8956,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN3121" ->12.7. Testing</A -></H2 +></A +>12.7. Testing</H2 ><P >Testing is vital in any piece of software, and Samba is certainly no exception. In designing this new subsystem, we have taken care to ensure @@ -9073,9 +8976,9 @@ it particularly valuable.</P ><P >Example useage:</P ><P -><SAMP +><TT CLASS="PROMPT" ->$</SAMP +>$</TT > <B CLASS="COMMAND" >bin/samtest</B @@ -9111,8 +9014,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN3147" ->13.1. Introduction</A -></H2 +></A +>13.1. Introduction</H2 ><P >With the development of LanManager and Windows NT compatible password encryption for Samba, it is now able @@ -9130,8 +9033,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN3151" ->13.2. How does it work?</A -></H2 +></A +>13.2. How does it work?</H2 ><P >LanManager encryption is somewhat similar to UNIX password encryption. The server uses a file containing a @@ -9195,11 +9098,11 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN3162" +></A >13.3. <A NAME="SMBPASSWDFILEFORMAT" ></A ->>The smbpasswd file</A -></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. @@ -9228,26 +9131,30 @@ CLASS="FILENAME" CLASS="FILENAME" >/etc/passwd </TT -> file use the following command:</P +> file use the following command :</P ><P -><SAMP +><TT CLASS="PROMPT" ->$ </SAMP -><KBD +>$ </TT +><TT CLASS="USERINPUT" +><B >cat /etc/passwd | mksmbpasswd.sh - > /usr/local/samba/private/smbpasswd</KBD + > /usr/local/samba/private/smbpasswd</B +></TT ></P ><P >If you are running on a system that uses NIS, use</P ><P -><SAMP +><TT CLASS="PROMPT" ->$ </SAMP -><KBD +>$ </TT +><TT CLASS="USERINPUT" +><B >ypcat passwd | mksmbpasswd.sh - > /usr/local/samba/private/smbpasswd</KBD + > /usr/local/samba/private/smbpasswd</B +></TT ></P ><P >The <B @@ -9287,27 +9194,37 @@ CLASS="COMMAND" ><PRE CLASS="PROGRAMLISTING" >username:uid:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX: - [Account type]:LCT-<last-change-time>:Long name + [Account type]:LCT-<last-change-time>:Long name </PRE ></P ><P ->Although only the <VAR +>Although only the <TT CLASS="REPLACEABLE" ->username</VAR +><I +>username</I +></TT >, - <VAR + <TT CLASS="REPLACEABLE" ->uid</VAR ->, <VAR +><I +>uid</I +></TT +>, <TT CLASS="REPLACEABLE" -> XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX</VAR +><I +> XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX</I +></TT >, - [<VAR + [<TT CLASS="REPLACEABLE" ->Account type</VAR ->] and <VAR +><I +>Account type</I +></TT +>] and <TT CLASS="REPLACEABLE" -> last-change-time</VAR +><I +> last-change-time</I +></TT > sections are significant and are looked at in the Samba code.</P ><P @@ -9332,9 +9249,9 @@ CLASS="EMPHASIS" ><P >To set a user to have no password (not recommended), edit the file using vi, and replace the first 11 characters with the ascii text - <CODE + <TT CLASS="CONSTANT" ->"NO PASSWORD"</CODE +>"NO PASSWORD"</TT > (minus the quotes).</P ><P >For example, to clear the password for user bob, his smbpasswd file @@ -9385,374 +9302,6 @@ CLASS="FILENAME" > file.</P ></DIV ></DIV -><DIV -CLASS="CHAPTER" -><HR><H1 -><A -NAME="MODULES" -></A ->Chapter 14. Modules</H1 -><DIV -CLASS="SECT1" -><H2 -CLASS="SECT1" -><A -NAME="AEN3225" ->14.1. Advantages</A -></H2 -><P ->The new modules system has the following advantages:</P -><P -></P -><TABLE -BORDER="0" -><TBODY -><TR -><TD ->Transparent loading of static and shared modules (no need -for a subsystem to know about modules)</TD -></TR -><TR -><TD ->Simple selection between shared and static modules at configure time</TD -></TR -><TR -><TD ->"preload modules" option for increasing performance for stable modules</TD -></TR -><TR -><TD ->No nasty #define stuff anymore</TD -></TR -><TR -><TD ->All backends are available as plugin now (including pdb_ldap and pdb_tdb)</TD -></TR -></TBODY -></TABLE -><P -></P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN3234" ->14.2. Loading modules</A -></H2 -><P ->Some subsystems in samba use different backends. These backends can be -either statically linked in to samba or available as a plugin. A subsystem -should have a function that allows a module to register itself. For example, -the passdb subsystem has: </P -><P -><PRE -CLASS="PROGRAMLISTING" ->BOOL smb_register_passdb(const char *name, pdb_init_function init, int version);</PRE -></P -><P ->This function will be called by the initialisation function of the module to -register itself. </P -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN3240" ->14.2.1. Static modules</A -></H3 -><P ->The modules system compiles a list of initialisation functions for the -static modules of each subsystem. This is a define. For example, -it is here currently (from <TT -CLASS="FILENAME" ->include/config.h</TT ->): </P -><P -><PRE -CLASS="PROGRAMLISTING" ->/* Static init functions */ -#define static_init_pdb { pdb_mysql_init(); pdb_ldap_init(); pdb_smbpasswd_init(); pdb_tdbsam_init(); pdb_guest_init();}</PRE -></P -><P ->These functions should be called before the subsystem is used. That -should be done when the subsystem is initialised or first used. </P -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN3247" ->14.2.2. Shared modules</A -></H3 -><P ->If a subsystem needs a certain backend, it should check if it has -already been registered. If the backend hasn't been registered already, -the subsystem should call smb_probe_module(char *subsystem, char *backend). -This function tries to load the correct module from a certain path -($LIBDIR/subsystem/backend.so). If the first character in 'backend' -is a slash, smb_probe_module() tries to load the module from the -absolute path specified in 'backend'.</P -><P ->After smb_probe_module() has been executed, the subsystem -should check again if the module has been registered. </P -></DIV -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN3251" ->14.3. Writing modules</A -></H2 -><P ->Each module has an initialisation function. For modules that are -included with samba this name is '<VAR -CLASS="REPLACEABLE" ->subsystem</VAR ->_<VAR -CLASS="REPLACEABLE" ->backend</VAR ->_init'. For external modules (that will never be built-in, but only available as a module) this name is always 'init_module'. (In the case of modules included with samba, the configure system will add a #define subsystem_backend_init() init_module()). -The prototype for these functions is:</P -><P -><PRE -CLASS="PROGRAMLISTING" ->int init_module(void);</PRE -></P -><P ->This function should call one or more -registration functions. The function should return non-zero on success and zero on -failure.</P -><P ->For example, pdb_ldap_init() contains: </P -><P -><PRE -CLASS="PROGRAMLISTING" ->int pdb_ldap_init(void) -{ - smb_register_passdb("ldapsam", pdb_init_ldapsam, PASSDB_INTERFACE_VERSION); - smb_register_passdb("ldapsam_nua", pdb_init_ldapsam_nua, PASSDB_INTERFACE_VERSION); - return TRUE; -}</PRE -></P -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN3262" ->14.3.1. Static/Shared selection in configure.in</A -></H3 -><P ->Some macros in configure.in generate the various defines and substs that -are necessary for the system to work correct. All modules that should -be built by default have to be added to the variable 'default_modules'. -For example, if ldap is found, pdb_ldap is added to this variable.</P -><P ->On the bottom of configure.in, SMB_MODULE() should be called -for each module and SMB_SUBSYSTEM() for each subsystem.</P -><P ->Syntax:</P -><P -><PRE -CLASS="PROGRAMLISTING" ->SMB_MODULE(<VAR -CLASS="REPLACEABLE" ->subsystem</VAR ->_<VAR -CLASS="REPLACEABLE" ->backend</VAR ->, <VAR -CLASS="REPLACEABLE" ->object files</VAR ->, <VAR -CLASS="REPLACEABLE" ->plugin name</VAR ->, <VAR -CLASS="REPLACEABLE" ->subsystem name</VAR ->, <VAR -CLASS="REPLACEABLE" ->static_action</VAR ->, <VAR -CLASS="REPLACEABLE" ->shared_action</VAR ->) -SMB_SUBSYSTEM(<VAR -CLASS="REPLACEABLE" ->subsystem</VAR ->)</PRE -></P -><P ->Also, make sure to add the correct directives to -<TT -CLASS="FILENAME" ->Makefile.in</TT ->. <VAR -CLASS="REPLACEABLE" ->@SUBSYSTEM_STATIC@</VAR -> -will be replaced with a list of objects files of the modules that need to -be linked in statically. <VAR -CLASS="REPLACEABLE" ->@SUBSYSTEM_MODULES@</VAR -> will -be replaced with the names of the plugins to build.</P -><P ->You must make sure all .c files that contain defines that can -be changed by ./configure are rebuilded in the 'modules_clean' make target. -Practically, this means all c files that contain <B -CLASS="COMMAND" ->static_init_subsystem;</B -> calls need to be rebuilded.</P -></DIV -></DIV -></DIV -><DIV -CLASS="CHAPTER" -><HR><H1 -><A -NAME="RPC-PLUGIN" -></A ->Chapter 15. RPC Pluggable Modules</H1 -><DIV -CLASS="SECT1" -><H2 -CLASS="SECT1" -><A -NAME="AEN3301" ->15.1. About</A -></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="AEN3304" ->15.2. General Overview</A -></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 init_module function within -the shared library. Check the chapter on modules for more information.</P -><P ->In the init_module 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 -CLASS="CHAPTER" -><HR><H1 -><A -NAME="PACKAGING" -></A ->Chapter 16. Notes to packagers</H1 -><DIV -CLASS="SECT1" -><H2 -CLASS="SECT1" -><A -NAME="AEN3337" ->16.1. Versioning</A -></H2 -><P ->Please, please update the version number in -<TT -CLASS="FILENAME" ->source/include/version.h</TT -> to include the versioning of your package. This makes it easier to distinguish standard samba builds -from custom-build samba builds (distributions often patch packages). For -example, a good version would be: </P -><P -><PRE -CLASS="PROGRAMLISTING" ->Version 2.999+3.0.alpha21-5 for Debian</PRE -></P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN3343" ->16.2. Modules</A -></H2 -><P ->Samba now has support for building parts of samba as plugins. This -makes it possible to, for example, put ldap or mysql support in a seperate -package, thus making it possible to have a normal samba package not -depending on ldap or mysql. To build as much parts of samba -as a plugin, run: </P -><P -><PRE -CLASS="PROGRAMLISTING" ->./configure --with-shared-modules=rpc,vfs,auth,pdb,charset</PRE -></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 8c470203e7..0000000000 --- a/docs/htmldocs/Samba-HOWTO-Collection.html +++ /dev/null @@ -1,23076 +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.7"></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" ->SAMBA Project Documentation</A -></H1 -><H3 -CLASS="AUTHOR" -><A -NAME="AEN4" -></A ->SAMBA Team</H3 -><DIV -CLASS="AFFILIATION" -><DIV -CLASS="ADDRESS" -><P -CLASS="ADDRESS" -><CODE -CLASS="EMAIL" -><<A -HREF="mailto:samba@samba.org" ->samba@samba.org</A ->></CODE -></P -></DIV -></DIV -><H4 -CLASS="EDITEDBY" ->Edited by</H4 -><H3 -CLASS="EDITOR" ->John H Terpstra</H3 -><H3 -CLASS="EDITOR" ->Jelmer Vernooij</H3 -><H3 -CLASS="EDITOR" ->Gerald (Jerry) Carter</H3 -><DIV -><DIV -CLASS="ABSTRACT" -><P -></P -><A -NAME="AEN32" -></A -><P ->This book is a collection of HOWTOs added to Samba documentation over the years. -Samba is always under development, and so is it's documentation. -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 -></P -></DIV -></DIV -><DIV -CLASS="LEGALNOTICE" -><P -></P -><A -NAME="AEN37" -></A -><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 -></P -></DIV -><HR></DIV -><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="#AEN65" ->Obtaining and installing samba</A -></DT -><DT ->1.2. <A -HREF="#AEN71" ->Configuring samba</A -></DT -><DT ->1.3. <A -HREF="#AEN107" ->Try listing the shares available on your - server</A -></DT -><DT ->1.4. <A -HREF="#AEN116" ->Try connecting with the unix client</A -></DT -><DT ->1.5. <A -HREF="#AEN137" ->Try connecting from a DOS, WfWg, Win9x, WinNT, - Win2k, OS/2, etc... client</A -></DT -><DT ->1.6. <A -HREF="#AEN150" ->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="#AEN183" ->Discussion</A -></DT -><DT ->2.2. <A -HREF="#AEN204" ->How browsing functions and how to deploy stable and -dependable browsing using Samba</A -></DT -><DT ->2.3. <A -HREF="#AEN218" ->Use of the <B -CLASS="COMMAND" ->Remote Announce</B -> parameter</A -></DT -><DT ->2.4. <A -HREF="#AEN241" ->Use of the <B -CLASS="COMMAND" ->Remote Browse Sync</B -> parameter</A -></DT -><DT ->2.5. <A -HREF="#AEN252" ->Use of WINS</A -></DT -><DT ->2.6. <A -HREF="#AEN269" ->Do NOT use more than one (1) protocol on MS Windows machines</A -></DT -><DT ->2.7. <A -HREF="#AEN277" ->Name Resolution Order</A -></DT -></DL -></DD -><DT ->3. <A -HREF="#PASSDB" ->User information database</A -></DT -><DD -><DL -><DT ->3.1. <A -HREF="#AEN335" ->Introduction</A -></DT -><DT ->3.2. <A -HREF="#AEN342" ->Important Notes About Security</A -></DT -><DT ->3.3. <A -HREF="#AEN380" ->The smbpasswd Command</A -></DT -><DT ->3.4. <A -HREF="#AEN411" ->Plain text</A -></DT -><DT ->3.5. <A -HREF="#AEN416" ->TDB</A -></DT -><DT ->3.6. <A -HREF="#AEN419" ->LDAP</A -></DT -><DT ->3.7. <A -HREF="#AEN637" ->MySQL</A -></DT -><DT ->3.8. <A -HREF="#AEN679" ->XML</A -></DT -></DL -></DD -></DL -></DD -><DT ->II. <A -HREF="#TYPE" ->Type of installation</A -></DT -><DD -><DL -><DT ->4. <A -HREF="#SERVERTYPE" ->Nomenclature of Server Types</A -></DT -><DD -><DL -><DT ->4.1. <A -HREF="#AEN717" ->Stand Alone Server</A -></DT -><DT ->4.2. <A -HREF="#AEN724" ->Domain Member Server</A -></DT -><DT ->4.3. <A -HREF="#AEN730" ->Domain Controller</A -></DT -></DL -></DD -><DT ->5. <A -HREF="#SECURITYLEVELS" ->Samba as Stand-Alone Server</A -></DT -><DD -><DL -><DT ->5.1. <A -HREF="#AEN766" ->User and Share security level</A -></DT -></DL -></DD -><DT ->6. <A -HREF="#SAMBA-PDC" ->Samba as an NT4 or Win2k Primary Domain Controller</A -></DT -><DD -><DL -><DT ->6.1. <A -HREF="#AEN878" ->Prerequisite Reading</A -></DT -><DT ->6.2. <A -HREF="#AEN883" ->Background</A -></DT -><DT ->6.3. <A -HREF="#AEN923" ->Configuring the Samba Domain Controller</A -></DT -><DT ->6.4. <A -HREF="#AEN965" ->Creating Machine Trust Accounts and Joining Clients to the Domain</A -></DT -><DT ->6.5. <A -HREF="#AEN1073" ->Common Problems and Errors</A -></DT -><DT ->6.6. <A -HREF="#AEN1119" ->What other help can I get?</A -></DT -><DT ->6.7. <A -HREF="#AEN1233" ->Domain Control for Windows 9x/ME</A -></DT -></DL -></DD -><DT ->7. <A -HREF="#SAMBA-BDC" ->Samba Backup Domain Controller to Samba Domain Control</A -></DT -><DD -><DL -><DT ->7.1. <A -HREF="#AEN1286" ->Prerequisite Reading</A -></DT -><DT ->7.2. <A -HREF="#AEN1290" ->Background</A -></DT -><DT ->7.3. <A -HREF="#AEN1298" ->What qualifies a Domain Controller on the network?</A -></DT -><DT ->7.4. <A -HREF="#AEN1307" ->Can Samba be a Backup Domain Controller to an NT PDC?</A -></DT -><DT ->7.5. <A -HREF="#AEN1312" ->How do I set up a Samba BDC?</A -></DT -></DL -></DD -><DT ->8. <A -HREF="#ADS" ->Samba as a ADS domain member</A -></DT -><DD -><DL -><DT ->8.1. <A -HREF="#AEN1355" ->Setup your <TT -CLASS="FILENAME" ->smb.conf</TT -></A -></DT -><DT ->8.2. <A -HREF="#AEN1368" ->Setup your <TT -CLASS="FILENAME" ->/etc/krb5.conf</TT -></A -></DT -><DT ->8.3. <A -HREF="#ADS-CREATE-MACHINE-ACCOUNT" ->Create the computer account</A -></DT -><DT ->8.4. <A -HREF="#ADS-TEST-SERVER" ->Test your server setup</A -></DT -><DT ->8.5. <A -HREF="#ADS-TEST-SMBCLIENT" ->Testing with <SPAN -CLASS="APPLICATION" ->smbclient</SPAN -></A -></DT -><DT ->8.6. <A -HREF="#AEN1416" ->Notes</A -></DT -></DL -></DD -><DT ->9. <A -HREF="#DOMAIN-SECURITY" ->Samba as a NT4 or Win2k domain member</A -></DT -><DD -><DL -><DT ->9.1. <A -HREF="#AEN1439" ->Joining an NT Domain with Samba 3.0</A -></DT -><DT ->9.2. <A -HREF="#AEN1493" ->Why is this better than security = server?</A -></DT -></DL -></DD -></DL -></DD -><DT ->III. <A -HREF="#OPTIONAL" ->Advanced Configuration</A -></DT -><DD -><DL -><DT ->10. <A -HREF="#UNIX-PERMISSIONS" ->UNIX Permission Bits and Windows NT Access Control Lists</A -></DT -><DD -><DL -><DT ->10.1. <A -HREF="#AEN1525" ->Viewing and changing UNIX permissions using the NT - security dialogs</A -></DT -><DT ->10.2. <A -HREF="#AEN1531" ->How to view file security on a Samba share</A -></DT -><DT ->10.3. <A -HREF="#AEN1542" ->Viewing file ownership</A -></DT -><DT ->10.4. <A -HREF="#AEN1562" ->Viewing file or directory permissions</A -></DT -><DT ->10.5. <A -HREF="#AEN1598" ->Modifying file or directory permissions</A -></DT -><DT ->10.6. <A -HREF="#AEN1620" ->Interaction with the standard Samba create mask - parameters</A -></DT -><DT ->10.7. <A -HREF="#AEN1673" ->Interaction with the standard Samba file attribute - mapping</A -></DT -></DL -></DD -><DT ->11. <A -HREF="#GROUPMAPPING" ->Configuring Group Mapping</A -></DT -><DT ->12. <A -HREF="#PRINTING" ->Printing Support</A -></DT -><DD -><DL -><DT ->12.1. <A -HREF="#AEN1736" ->Introduction</A -></DT -><DT ->12.2. <A -HREF="#AEN1758" ->Configuration</A -></DT -><DT ->12.3. <A -HREF="#AEN1870" ->The Imprints Toolset</A -></DT -><DT ->12.4. <A -HREF="#AEN1913" ->Diagnosis</A -></DT -></DL -></DD -><DT ->13. <A -HREF="#CUPS-PRINTING" ->CUPS Printing Support</A -></DT -><DD -><DL -><DT ->13.1. <A -HREF="#AEN2025" ->Introduction</A -></DT -><DT ->13.2. <A -HREF="#AEN2032" ->Configuring <TT -CLASS="FILENAME" ->smb.conf</TT -> for CUPS</A -></DT -><DT ->13.3. <A -HREF="#AEN2052" ->CUPS - RAW Print Through Mode</A -></DT -><DT ->13.4. <A -HREF="#AEN2111" ->CUPS as a network PostScript RIP -- CUPS drivers working on server, Adobe -PostScript driver with CUPS-PPDs downloaded to clients</A -></DT -><DT ->13.5. <A -HREF="#AEN2132" ->Windows Terminal Servers (WTS) as CUPS clients</A -></DT -><DT ->13.6. <A -HREF="#AEN2136" ->Setting up CUPS for driver download</A -></DT -><DT ->13.7. <A -HREF="#AEN2149" ->Sources of CUPS drivers / PPDs</A -></DT -><DT ->13.8. <A -HREF="#AEN2205" ->The CUPS Filter Chains</A -></DT -><DT ->13.9. <A -HREF="#AEN2244" ->CUPS Print Drivers and Devices</A -></DT -><DT ->13.10. <A -HREF="#AEN2321" ->Limiting the number of pages users can print</A -></DT -><DT ->13.11. <A -HREF="#AEN2417" ->Advanced Postscript Printing from MS Windows</A -></DT -><DT ->13.12. <A -HREF="#AEN2432" ->Auto-Deletion of CUPS spool files</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="#AEN2506" ->Abstract</A -></DT -><DT ->14.2. <A -HREF="#AEN2510" ->Introduction</A -></DT -><DT ->14.3. <A -HREF="#AEN2523" ->What Winbind Provides</A -></DT -><DT ->14.4. <A -HREF="#AEN2534" ->How Winbind Works</A -></DT -><DT ->14.5. <A -HREF="#AEN2577" ->Installation and Configuration</A -></DT -><DT ->14.6. <A -HREF="#AEN2834" ->Limitations</A -></DT -><DT ->14.7. <A -HREF="#AEN2844" ->Conclusion</A -></DT -></DL -></DD -><DT ->15. <A -HREF="#ADVANCEDNETWORKMANAGEMENT" ->Advanced Network Manangement</A -></DT -><DD -><DL -><DT ->15.1. <A -HREF="#AEN2859" ->Configuring Samba Share Access Controls</A -></DT -><DT ->15.2. <A -HREF="#AEN2897" ->Remote Server Administration</A -></DT -><DT ->15.3. <A -HREF="#AEN2914" ->Network Logon Script Magic</A -></DT -></DL -></DD -><DT ->16. <A -HREF="#POLICYMGMT" ->System and Account Policies</A -></DT -><DD -><DL -><DT ->16.1. <A -HREF="#AEN2929" ->Creating and Managing System Policies</A -></DT -><DT ->16.2. <A -HREF="#AEN3002" ->Managing Account/User Policies</A -></DT -></DL -></DD -><DT ->17. <A -HREF="#PROFILEMGMT" ->Desktop Profile Management</A -></DT -><DD -><DL -><DT ->17.1. <A -HREF="#AEN3035" ->Roaming Profiles</A -></DT -><DT ->17.2. <A -HREF="#AEN3242" ->Mandatory profiles</A -></DT -><DT ->17.3. <A -HREF="#AEN3249" ->Creating/Managing Group Profiles</A -></DT -><DT ->17.4. <A -HREF="#AEN3255" ->Default Profile for Windows Users</A -></DT -></DL -></DD -><DT ->18. <A -HREF="#INTERDOMAINTRUSTS" ->Interdomain Trust Relationships</A -></DT -><DD -><DL -><DT ->18.1. <A -HREF="#AEN3386" ->Trust Relationship Background</A -></DT -><DT ->18.2. <A -HREF="#AEN3395" ->MS Windows NT4 Trust Configuration</A -></DT -><DT ->18.3. <A -HREF="#AEN3405" ->Configuring Samba Domain Trusts</A -></DT -></DL -></DD -><DT ->19. <A -HREF="#PAM" ->PAM Configuration for Centrally Managed Authentication</A -></DT -><DD -><DL -><DT ->19.1. <A -HREF="#AEN3440" ->Samba and PAM</A -></DT -><DT ->19.2. <A -HREF="#AEN3491" ->Distributed Authentication</A -></DT -><DT ->19.3. <A -HREF="#AEN3496" ->PAM Configuration in smb.conf</A -></DT -></DL -></DD -><DT ->20. <A -HREF="#VFS" ->Stackable VFS modules</A -></DT -><DD -><DL -><DT ->20.1. <A -HREF="#AEN3531" ->Introduction and configuration</A -></DT -><DT ->20.2. <A -HREF="#AEN3540" ->Included modules</A -></DT -><DT ->20.3. <A -HREF="#AEN3598" ->VFS modules available elsewhere</A -></DT -></DL -></DD -><DT ->21. <A -HREF="#MSDFS" ->Hosting a Microsoft Distributed File System tree on Samba</A -></DT -><DD -><DL -><DT ->21.1. <A -HREF="#AEN3626" ->Instructions</A -></DT -></DL -></DD -><DT ->22. <A -HREF="#INTEGRATE-MS-NETWORKS" ->Integrating MS Windows networks with Samba</A -></DT -><DD -><DL -><DT ->22.1. <A -HREF="#AEN3688" ->Name Resolution in a pure Unix/Linux world</A -></DT -><DT ->22.2. <A -HREF="#AEN3751" ->Name resolution as used within MS Windows networking</A -></DT -></DL -></DD -><DT ->23. <A -HREF="#IMPROVED-BROWSING" ->Improved browsing in samba</A -></DT -><DD -><DL -><DT ->23.1. <A -HREF="#AEN3804" ->Overview of browsing</A -></DT -><DT ->23.2. <A -HREF="#AEN3810" ->Browsing support in samba</A -></DT -><DT ->23.3. <A -HREF="#AEN3825" ->Problem resolution</A -></DT -><DT ->23.4. <A -HREF="#AEN3837" ->Browsing across subnets</A -></DT -><DT ->23.5. <A -HREF="#AEN3878" ->Setting up a WINS server</A -></DT -><DT ->23.6. <A -HREF="#AEN3901" ->Setting up Browsing in a WORKGROUP</A -></DT -><DT ->23.7. <A -HREF="#AEN3927" ->Setting up Browsing in a DOMAIN</A -></DT -><DT ->23.8. <A -HREF="#BROWSE-FORCE-MASTER" ->Forcing samba to be the master</A -></DT -><DT ->23.9. <A -HREF="#AEN3962" ->Making samba the domain master</A -></DT -><DT ->23.10. <A -HREF="#AEN3984" ->Note about broadcast addresses</A -></DT -><DT ->23.11. <A -HREF="#AEN3987" ->Multiple interfaces</A -></DT -></DL -></DD -><DT ->24. <A -HREF="#SECURING-SAMBA" ->Securing Samba</A -></DT -><DD -><DL -><DT ->24.1. <A -HREF="#AEN4003" ->Introduction</A -></DT -><DT ->24.2. <A -HREF="#AEN4006" ->Using host based protection</A -></DT -><DT ->24.3. <A -HREF="#AEN4016" ->Using interface protection</A -></DT -><DT ->24.4. <A -HREF="#AEN4025" ->Using a firewall</A -></DT -><DT ->24.5. <A -HREF="#AEN4032" ->Using a IPC$ share deny</A -></DT -><DT ->24.6. <A -HREF="#AEN4041" ->Upgrading Samba</A -></DT -></DL -></DD -><DT ->25. <A -HREF="#UNICODE" ->Unicode/Charsets</A -></DT -><DD -><DL -><DT ->25.1. <A -HREF="#AEN4056" ->What are charsets and unicode?</A -></DT -><DT ->25.2. <A -HREF="#AEN4065" ->Samba and charsets</A -></DT -></DL -></DD -></DL -></DD -><DT ->IV. <A -HREF="#APPENDIXES" ->Appendixes</A -></DT -><DD -><DL -><DT ->26. <A -HREF="#SWAT" ->SWAT - The Samba Web Admininistration Tool</A -></DT -><DD -><DL -><DT ->26.1. <A -HREF="#AEN4098" ->SWAT Features and Benefits</A -></DT -></DL -></DD -><DT ->27. <A -HREF="#NT4MIGRATION" ->Migration from NT4 PDC to Samba-3 PDC</A -></DT -><DD -><DL -><DT ->27.1. <A -HREF="#AEN4134" ->Planning and Getting Started</A -></DT -><DT ->27.2. <A -HREF="#AEN4143" ->Managing Samba-3 Domain Control</A -></DT -></DL -></DD -><DT ->28. <A -HREF="#SPEED" ->Samba performance issues</A -></DT -><DD -><DL -><DT ->28.1. <A -HREF="#AEN4163" ->Comparisons</A -></DT -><DT ->28.2. <A -HREF="#AEN4169" ->Socket options</A -></DT -><DT ->28.3. <A -HREF="#AEN4176" ->Read size</A -></DT -><DT ->28.4. <A -HREF="#AEN4181" ->Max xmit</A -></DT -><DT ->28.5. <A -HREF="#AEN4186" ->Log level</A -></DT -><DT ->28.6. <A -HREF="#AEN4189" ->Read raw</A -></DT -><DT ->28.7. <A -HREF="#AEN4194" ->Write raw</A -></DT -><DT ->28.8. <A -HREF="#AEN4198" ->Slow Clients</A -></DT -><DT ->28.9. <A -HREF="#AEN4202" ->Slow Logins</A -></DT -><DT ->28.10. <A -HREF="#AEN4205" ->Client tuning</A -></DT -></DL -></DD -><DT ->29. <A -HREF="#PORTABILITY" ->Portability</A -></DT -><DD -><DL -><DT ->29.1. <A -HREF="#AEN4249" ->HPUX</A -></DT -><DT ->29.2. <A -HREF="#AEN4255" ->SCO Unix</A -></DT -><DT ->29.3. <A -HREF="#AEN4259" ->DNIX</A -></DT -><DT ->29.4. <A -HREF="#AEN4288" ->RedHat Linux Rembrandt-II</A -></DT -><DT ->29.5. <A -HREF="#AEN4294" ->AIX</A -></DT -></DL -></DD -><DT ->30. <A -HREF="#OTHER-CLIENTS" ->Samba and other CIFS clients</A -></DT -><DD -><DL -><DT ->30.1. <A -HREF="#AEN4319" ->Macintosh clients?</A -></DT -><DT ->30.2. <A -HREF="#AEN4328" ->OS2 Client</A -></DT -><DT ->30.3. <A -HREF="#AEN4368" ->Windows for Workgroups</A -></DT -><DT ->30.4. <A -HREF="#AEN4392" ->Windows '95/'98</A -></DT -><DT ->30.5. <A -HREF="#AEN4408" ->Windows 2000 Service Pack 2</A -></DT -><DT ->30.6. <A -HREF="#AEN4425" ->Windows NT 3.1</A -></DT -></DL -></DD -><DT ->31. <A -HREF="#COMPILING" ->How to compile SAMBA</A -></DT -><DD -><DL -><DT ->31.1. <A -HREF="#AEN4446" ->Access Samba source code via CVS</A -></DT -><DT ->31.2. <A -HREF="#AEN4489" ->Accessing the samba sources via rsync and ftp</A -></DT -><DT ->31.3. <A -HREF="#AEN4495" ->Building the Binaries</A -></DT -><DT ->31.4. <A -HREF="#AEN4552" ->Starting the smbd and nmbd</A -></DT -></DL -></DD -><DT ->32. <A -HREF="#BUGREPORT" ->Reporting Bugs</A -></DT -><DD -><DL -><DT ->32.1. <A -HREF="#AEN4627" ->Introduction</A -></DT -><DT ->32.2. <A -HREF="#AEN4637" ->General info</A -></DT -><DT ->32.3. <A -HREF="#AEN4643" ->Debug levels</A -></DT -><DT ->32.4. <A -HREF="#AEN4664" ->Internal errors</A -></DT -><DT ->32.5. <A -HREF="#AEN4678" ->Attaching to a running process</A -></DT -><DT ->32.6. <A -HREF="#AEN4686" ->Patches</A -></DT -></DL -></DD -><DT ->33. <A -HREF="#DIAGNOSIS" ->The samba checklist</A -></DT -><DD -><DL -><DT ->33.1. <A -HREF="#AEN4709" ->Introduction</A -></DT -><DT ->33.2. <A -HREF="#AEN4714" ->Assumptions</A -></DT -><DT ->33.3. <A -HREF="#AEN4733" ->The tests</A -></DT -><DT ->33.4. <A -HREF="#AEN4900" ->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="AEN42" -></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="#AEN65" ->Obtaining and installing samba</A -></DT -><DT ->1.2. <A -HREF="#AEN71" ->Configuring samba</A -></DT -><DD -><DL -><DT ->1.2.1. <A -HREF="#AEN76" ->Editing the <TT -CLASS="FILENAME" ->smb.conf</TT -> file</A -></DT -><DT ->1.2.2. <A -HREF="#AEN101" ->SWAT</A -></DT -></DL -></DD -><DT ->1.3. <A -HREF="#AEN107" ->Try listing the shares available on your - server</A -></DT -><DT ->1.4. <A -HREF="#AEN116" ->Try connecting with the unix client</A -></DT -><DT ->1.5. <A -HREF="#AEN137" ->Try connecting from a DOS, WfWg, Win9x, WinNT, - Win2k, OS/2, etc... client</A -></DT -><DT ->1.6. <A -HREF="#AEN150" ->What If Things Don't Work?</A -></DT -><DD -><DL -><DT ->1.6.1. <A -HREF="#AEN156" ->Scope IDs</A -></DT -><DT ->1.6.2. <A -HREF="#AEN159" ->Locking</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="#AEN183" ->Discussion</A -></DT -><DT ->2.2. <A -HREF="#AEN204" ->How browsing functions and how to deploy stable and -dependable browsing using Samba</A -></DT -><DT ->2.3. <A -HREF="#AEN218" ->Use of the <B -CLASS="COMMAND" ->Remote Announce</B -> parameter</A -></DT -><DT ->2.4. <A -HREF="#AEN241" ->Use of the <B -CLASS="COMMAND" ->Remote Browse Sync</B -> parameter</A -></DT -><DT ->2.5. <A -HREF="#AEN252" ->Use of WINS</A -></DT -><DT ->2.6. <A -HREF="#AEN269" ->Do NOT use more than one (1) protocol on MS Windows machines</A -></DT -><DT ->2.7. <A -HREF="#AEN277" ->Name Resolution Order</A -></DT -></DL -></DD -><DT ->3. <A -HREF="#PASSDB" ->User information database</A -></DT -><DD -><DL -><DT ->3.1. <A -HREF="#AEN335" ->Introduction</A -></DT -><DT ->3.2. <A -HREF="#AEN342" ->Important Notes About Security</A -></DT -><DD -><DL -><DT ->3.2.1. <A -HREF="#AEN368" ->Advantages of SMB Encryption</A -></DT -><DT ->3.2.2. <A -HREF="#AEN374" ->Advantages of non-encrypted passwords</A -></DT -></DL -></DD -><DT ->3.3. <A -HREF="#AEN380" ->The smbpasswd Command</A -></DT -><DT ->3.4. <A -HREF="#AEN411" ->Plain text</A -></DT -><DT ->3.5. <A -HREF="#AEN416" ->TDB</A -></DT -><DT ->3.6. <A -HREF="#AEN419" ->LDAP</A -></DT -><DD -><DL -><DT ->3.6.1. <A -HREF="#AEN421" ->Introduction</A -></DT -><DT ->3.6.2. <A -HREF="#AEN441" ->Introduction</A -></DT -><DT ->3.6.3. <A -HREF="#AEN470" ->Supported LDAP Servers</A -></DT -><DT ->3.6.4. <A -HREF="#AEN475" ->Schema and Relationship to the RFC 2307 posixAccount</A -></DT -><DT ->3.6.5. <A -HREF="#AEN487" ->Configuring Samba with LDAP</A -></DT -><DT ->3.6.6. <A -HREF="#AEN534" ->Accounts and Groups management</A -></DT -><DT ->3.6.7. <A -HREF="#AEN539" ->Security and sambaAccount</A -></DT -><DT ->3.6.8. <A -HREF="#AEN559" ->LDAP specials attributes for sambaAccounts</A -></DT -><DT ->3.6.9. <A -HREF="#AEN629" ->Example LDIF Entries for a sambaAccount</A -></DT -></DL -></DD -><DT ->3.7. <A -HREF="#AEN637" ->MySQL</A -></DT -><DD -><DL -><DT ->3.7.1. <A -HREF="#AEN639" ->Creating the database</A -></DT -><DT ->3.7.2. <A -HREF="#AEN649" ->Configuring</A -></DT -><DT ->3.7.3. <A -HREF="#AEN666" ->Using plaintext passwords or encrypted password</A -></DT -><DT ->3.7.4. <A -HREF="#AEN671" ->Getting non-column data from the table</A -></DT -></DL -></DD -><DT ->3.8. <A -HREF="#AEN679" ->XML</A -></DT -></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="AEN65" ->1.1. Obtaining and installing samba</A -></H2 -><P ->Binary packages of samba are included in almost any Linux or - Unix distribution. There are also some packages available at - <A -HREF="http://samba.org/" -TARGET="_top" ->the samba homepage</A ->. - </P -><P ->If you need to compile samba from source, check the - <A -HREF="#COMPILING" ->appropriate appendix chapter</A ->.</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN71" ->1.2. Configuring samba</A -></H2 -><P ->Samba's configuration is stored in the smb.conf file, - that usually resides in <TT -CLASS="FILENAME" ->/etc/samba/smb.conf</TT -> - or <TT -CLASS="FILENAME" ->/usr/local/samba/lib/smb.conf</TT ->. You can either - edit this file yourself or do it using one of the many graphical - tools that are available, such as the web-based interface swat, that - is included with samba.</P -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN76" ->1.2.1. Editing the <TT -CLASS="FILENAME" ->smb.conf</TT -> file</A -></H3 -><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 - "<B -CLASS="COMMAND" ->homes</B ->" as the service name. (Note that I also set the - workgroup that Samba is part of. See BROWSING.txt for details)</P -><P ->Make sure you put the <TT -CLASS="FILENAME" ->smb.conf</TT -> 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 - <B -CLASS="COMMAND" ->[homes]</B -> share please refer to the chapter - <A -HREF="#SECURING-SAMBA" ->Securing Samba</A ->.</P -><DIV -CLASS="SECT3" -><HR><H4 -CLASS="SECT3" -><A -NAME="AEN92" ->1.2.1.1. Test your config file with - <B -CLASS="COMMAND" ->testparm</B -></A -></H4 -><P ->It's important that you test the validity of your - <TT -CLASS="FILENAME" ->smb.conf</TT -> file using the <SPAN -CLASS="APPLICATION" ->testparm</SPAN -> 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 -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN101" ->1.2.2. SWAT</A -></H3 -><P -> SWAT is a web-based interface that helps you configure samba. - SWAT might not be available in the samba package on your platform, - but in a seperate package. Please read the swat manpage - on compiling, installing and configuring swat from source. - </P -><P ->To launch SWAT just run your favorite web browser and - point it at "http://localhost:901/". Replace <VAR -CLASS="REPLACEABLE" ->localhost</VAR -> with the name of the computer you are running samba on if you - are running samba on a different computer then your browser.</P -><P ->Note that you can attach to SWAT from any IP connected - machine but connecting from a remote machine leaves your - connection open to password sniffing as passwords will be sent - in the clear over the wire. </P -></DIV -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN107" ->1.3. Try listing the shares available on your - server</A -></H2 -><P -><SAMP -CLASS="PROMPT" ->$ </SAMP -><KBD -CLASS="USERINPUT" ->smbclient -L - <VAR -CLASS="REPLACEABLE" ->yourhostname</VAR -></KBD -></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="AEN116" ->1.4. Try connecting with the unix client</A -></H2 -><P -><SAMP -CLASS="PROMPT" ->$ </SAMP -><KBD -CLASS="USERINPUT" ->smbclient <VAR -CLASS="REPLACEABLE" -> //yourhostname/aservice</VAR -></KBD -></P -><P ->Typically the <VAR -CLASS="REPLACEABLE" ->yourhostname</VAR -> - would be the name of the host where you installed <SPAN -CLASS="APPLICATION" ->smbd</SPAN ->. - The <VAR -CLASS="REPLACEABLE" ->aservice</VAR -> is - any service you have defined in the <TT -CLASS="FILENAME" ->smb.conf</TT -> - file. Try your user name if you just have a <B -CLASS="COMMAND" ->[homes]</B -> - section - in <TT -CLASS="FILENAME" ->smb.conf</TT ->.</P -><P ->For example if your unix host is <VAR -CLASS="REPLACEABLE" ->bambi</VAR -> - and your login name is <VAR -CLASS="REPLACEABLE" ->fred</VAR -> you would type:</P -><P -><SAMP -CLASS="PROMPT" ->$ </SAMP -><KBD -CLASS="USERINPUT" ->smbclient //<VAR -CLASS="REPLACEABLE" ->bambi</VAR ->/<VAR -CLASS="REPLACEABLE" ->fred</VAR -> - </KBD -></P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN137" ->1.5. Try connecting from a DOS, WfWg, Win9x, WinNT, - Win2k, OS/2, etc... client</A -></H2 -><P ->Try mounting disks. eg:</P -><P -><SAMP -CLASS="PROMPT" ->C:\WINDOWS\> </SAMP -><KBD -CLASS="USERINPUT" ->net use d: \\servername\service - </KBD -></P -><P ->Try printing. eg:</P -><P -><SAMP -CLASS="PROMPT" ->C:\WINDOWS\> </SAMP -><KBD -CLASS="USERINPUT" ->net use lpt1: - \\servername\spoolservice</KBD -></P -><P -><SAMP -CLASS="PROMPT" ->C:\WINDOWS\> </SAMP -><KBD -CLASS="USERINPUT" ->print filename - </KBD -></P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN150" ->1.6. What If Things Don't Work?</A -></H2 -><P ->Then you might read the file chapter - <A -HREF="#DIAGNOSIS" ->Diagnosis</A -> 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 <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->please</I -></SPAN -> send some - updates of the documentation (or source code) to one of - the documentation maintainers or the list. - </P -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN156" ->1.6.1. Scope IDs</A -></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="AEN159" ->1.6.2. Locking</A -></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 -></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="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 ->MS Windows 2000 and later can be configured to operate with NO NetBIOS -over TCP/IP. Samba-3 and later also supports this mode of operation.</P -></TD -></TR -></TABLE -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN183" ->2.1. Discussion</A -></H2 -><P ->Firstly, all MS Windows networking is based on SMB (Server Message -Block) based messaging. SMB messaging may be implemented using NetBIOS or -without 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 -<B -CLASS="COMMAND" ->remote announce</B -> -parameter to smb.conf helps to project browse announcements -to remote network segments via unicast UDP. Similarly, the -<B -CLASS="COMMAND" ->remote browse sync</B -> parameter of <TT -CLASS="FILENAME" ->smb.conf</TT -> -implements browse list collation using unicast UDP.</P -><P ->Secondly, in those networks where Samba is the only SMB server technology -wherever possible <SPAN -CLASS="APPLICATION" ->nmbd</SPAN -> 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 -<B -CLASS="COMMAND" ->remote announce</B -> and the <B -CLASS="COMMAND" ->remote browse sync</B -> -parameters to your <TT -CLASS="FILENAME" ->smb.conf</TT -> file.</P -><P ->If only one WINS server is used for an entire multi-segment network then -the use of the <B -CLASS="COMMAND" ->remote announce</B -> and the -<B -CLASS="COMMAND" ->remote browse sync</B -> parameters should NOT be necessary.</P -><P ->As of Samba 3 WINS replication is being worked on. The bulk of the code has -been committed, but it still needs maturation.</P -><P ->Right now samba WINS does not support MS-WINS replication. This means that -when setting up Samba as a WINS server there must only be one <SPAN -CLASS="APPLICATION" ->nmbd</SPAN -> 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 -<B -CLASS="COMMAND" ->remote browse sync</B -> and <B -CLASS="COMMAND" ->remote announce</B -> -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="AEN204" ->2.2. How browsing functions and how to deploy stable and -dependable browsing using Samba</A -></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 -<B -CLASS="COMMAND" ->remote announce</B -> 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 <B -CLASS="COMMAND" ->remote -browse sync</B -> parameter in the <TT -CLASS="FILENAME" ->smb.conf</TT -> 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 <B -CLASS="COMMAND" ->remote -browse sync</B -> 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="AEN218" ->2.3. Use of the <B -CLASS="COMMAND" ->Remote Announce</B -> parameter</A -></H2 -><P ->The <B -CLASS="COMMAND" ->remote announce</B -> parameter of -<TT -CLASS="FILENAME" ->smb.conf</TT -> can be used to forcibly ensure -that all the NetBIOS names on a network get announced to a remote network. -The syntax of the <B -CLASS="COMMAND" ->remote announce</B -> parameter is: -<PRE -CLASS="PROGRAMLISTING" -> remote announce = <VAR -CLASS="REPLACEABLE" ->a.b.c.d [e.f.g.h]</VAR -> ...</PRE -> -_or_ -<PRE -CLASS="PROGRAMLISTING" -> remote announce = <VAR -CLASS="REPLACEABLE" ->a.b.c.d/WORKGROUP [e.f.g.h/WORKGROUP]</VAR -> ...</PRE -> - -where: -<P -></P -><DIV -CLASS="VARIABLELIST" -><DL -><DT -><VAR -CLASS="REPLACEABLE" ->a.b.c.d</VAR -> and -<VAR -CLASS="REPLACEABLE" ->e.f.g.h</VAR -></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 -><VAR -CLASS="REPLACEABLE" ->WORKGROUP</VAR -></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="AEN241" ->2.4. Use of the <B -CLASS="COMMAND" ->Remote Browse Sync</B -> parameter</A -></H2 -><P ->The <B -CLASS="COMMAND" ->remote browse sync</B -> parameter of -<TT -CLASS="FILENAME" ->smb.conf</TT -> 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 <B -CLASS="COMMAND" ->remote browse sync</B -> parameter is: - -<PRE -CLASS="PROGRAMLISTING" ->remote browse sync = <VAR -CLASS="REPLACEABLE" ->a.b.c.d</VAR -></PRE -> - -where <VAR -CLASS="REPLACEABLE" ->a.b.c.d</VAR -> 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="AEN252" ->2.5. Use of WINS</A -></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 -<TT -CLASS="FILENAME" ->lmhosts</TT -> 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 -<B -CLASS="COMMAND" ->wins support = yes</B -> to the <TT -CLASS="FILENAME" ->smb.conf</TT -> -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 -><DIV -CLASS="IMPORTANT" -><P -></P -><TABLE -CLASS="IMPORTANT" -WIDTH="100%" -BORDER="0" -><TR -><TD -WIDTH="25" -ALIGN="CENTER" -VALIGN="TOP" -><IMG -SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/important.gif" -HSPACE="5" -ALT="Important"></TD -><TD -ALIGN="LEFT" -VALIGN="TOP" -><P ->Never use both <B -CLASS="COMMAND" ->wins support = yes</B -> together -with <B -CLASS="COMMAND" ->wins server = a.b.c.d</B -> -particularly not using it's own IP address. -Specifying both will cause <SPAN -CLASS="APPLICATION" ->nmbd</SPAN -> to refuse to start!</P -></TD -></TR -></TABLE -></DIV -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN269" ->2.6. Do NOT use more than one (1) protocol on MS Windows machines</A -></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 takes 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 -><SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->Windows 95, 98, 98se, Me are referred to generically as Windows 9x. -The Windows NT4, 2000, XP and 2003 use common protocols. These are roughly -referred to as the WinNT family, but it should be recognised that 2000 and -XP/2003 introduce new protocol extensions that cause them to behave -differently from MS Windows NT4. Generally, where a server does NOT support -the newer or extended protocol, these will fall back to the NT4 protocols.</I -></SPAN -></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="AEN277" ->2.7. Name Resolution Order</A -></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="AEN335" ->3.1. Introduction</A -></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="AEN342" ->3.2. Important Notes About Security</A -></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 -> These versions of MS Windows do not support full domain - security protocols, although they may log onto a domain environment. - Of these Only MS Windows XP Home does NOT support domain logons.</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 Me</TD -></TR -><TR -><TD ->Windows XP Home</TD -></TR -></TBODY -></TABLE -><P -></P -><P -> The following versions of MS Windows fully support domain - security protocols.</P -><P -></P -><TABLE -BORDER="0" -><TBODY -><TR -><TD ->Windows NT 3.5x</TD -></TR -><TR -><TD ->Windows NT 4.0</TD -></TR -><TR -><TD ->Windows 2000 Professional</TD -></TR -><TR -><TD ->Windows 200x Server/Advanced Server</TD -></TR -><TR -><TD ->Windows XP Professional</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 -><P ->MS Windows clients will cache the encrypted password alone. - Even when plain text passwords are re-enabled, through the appropriate - registry change, the plain text password is NEVER cached. This means that - in the event that a network connections should become disconnected (broken) - only the cached (encrypted) password will be sent to the resource server - to affect a auto-reconnect. If the resource server does not support encrypted - passwords the auto-reconnect will fail. <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->USE OF ENCRYPTED PASSWORDS - IS STRONGLY ADVISED.</I -></SPAN -></P -></TD -></TR -></TABLE -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN368" ->3.2.1. Advantages of SMB Encryption</A -></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 SM not support 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 -><TR -><TD ->Encrypted password support allows automatic share - (resource) reconnects.</TD -></TR -></TBODY -></TABLE -><P -></P -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN374" ->3.2.2. Advantages of non-encrypted passwords</A -></H3 -><P -></P -><TABLE -BORDER="0" -><TBODY -><TR -><TD ->Plain text passwords are not kept - on disk, and are NOT cached in memory. </TD -></TR -><TR -><TD ->Uses same password file as other unix - services such as login and ftp</TD -></TR -><TR -><TD ->Use of 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="AEN380" ->3.3. The smbpasswd Command</A -></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 -><SAMP -CLASS="PROMPT" ->$ </SAMP -><KBD -CLASS="USERINPUT" ->smbpasswd</KBD -></P -><P -><SAMP -CLASS="PROMPT" ->Old SMB password: </SAMP -><KBD -CLASS="USERINPUT" -><type old value here - - or hit return if there was no old password></KBD -></P -><P -><SAMP -CLASS="PROMPT" ->New SMB Password: </SAMP -><KBD -CLASS="USERINPUT" -><type new value> - </KBD -></P -><P -><SAMP -CLASS="PROMPT" ->Repeat New SMB Password: </SAMP -><KBD -CLASS="USERINPUT" -><re-type new value - </KBD -></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="AEN411" ->3.4. Plain text</A -></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="AEN416" ->3.5. TDB</A -></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="AEN419" ->3.6. LDAP</A -></H2 -><DIV -CLASS="SECT2" -><H3 -CLASS="SECT2" -><A -NAME="AEN421" ->3.6.1. Introduction</A -></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="AEN441" ->3.6.2. Introduction</A -></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. <VAR -CLASS="PARAMETER" ->--with-ldapsam</VAR -> or -<VAR -CLASS="PARAMETER" ->--with-tdbsam</VAR ->) requires compile time support.</P -><P ->When compiling Samba to include the <VAR -CLASS="PARAMETER" ->--with-ldapsam</VAR -> 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 <VAR -CLASS="PARAMETER" ->--with-ldapsam</VAR -> -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="AEN470" ->3.6.3. Supported LDAP Servers</A -></H3 -><P ->The LDAP samdb code in 2.2.3 (and later) 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="mailto:samba-patches@samba.org" -TARGET="_top" ->samba-patches@samba.org</A -> and -<A -HREF="mailto:jerry@samba.org" -TARGET="_top" ->jerry@samba.org</A ->.</P -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN475" ->3.6.4. Schema and Relationship to the RFC 2307 posixAccount</A -></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="mailto: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 -<CODE -CLASS="CONSTANT" ->STRUCTURAL</CODE -> 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="AEN487" ->3.6.5. Configuring Samba with LDAP</A -></H3 -><DIV -CLASS="SECT3" -><H4 -CLASS="SECT3" -><A -NAME="AEN489" ->3.6.5.1. OpenLDAP configuration</A -></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 -><SAMP -CLASS="PROMPT" ->root# </SAMP -><KBD -CLASS="USERINPUT" ->cp samba.schema /etc/openldap/schema/</KBD -></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="AEN506" ->3.6.5.2. Configuring Samba</A -></H4 -><P ->The following parameters are available in smb.conf only with <VAR -CLASS="PARAMETER" ->--with-ldapsam</VAR -> -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 <VAR -CLASS="REPLACEABLE" ->secretpw</VAR ->' 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="AEN534" ->3.6.6. Accounts and Groups management</A -></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="AEN539" ->3.6.7. Security and sambaAccount</A -></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="AEN559" ->3.6.8. LDAP specials attributes for sambaAccounts</A -></H3 -><P ->The sambaAccount objectclass is composed of the following attributes:</P -><P -></P -><UL -><LI -><P -><CODE -CLASS="CONSTANT" ->lmPassword</CODE ->: the LANMAN password 16-byte hash stored as a character - representation of a hexidecimal string.</P -></LI -><LI -><P -><CODE -CLASS="CONSTANT" ->ntPassword</CODE ->: the NT password hash 16-byte stored as a character - representation of a hexidecimal string.</P -></LI -><LI -><P -><CODE -CLASS="CONSTANT" ->pwdLastSet</CODE ->: The integer time in seconds since 1970 when the - <CODE -CLASS="CONSTANT" ->lmPassword</CODE -> and <CODE -CLASS="CONSTANT" ->ntPassword</CODE -> attributes were last set. - </P -></LI -><LI -><P -><CODE -CLASS="CONSTANT" ->acctFlags</CODE ->: 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 -><CODE -CLASS="CONSTANT" ->logonTime</CODE ->: Integer value currently unused</P -></LI -><LI -><P -><CODE -CLASS="CONSTANT" ->logoffTime</CODE ->: Integer value currently unused</P -></LI -><LI -><P -><CODE -CLASS="CONSTANT" ->kickoffTime</CODE ->: Integer value currently unused</P -></LI -><LI -><P -><CODE -CLASS="CONSTANT" ->pwdCanChange</CODE ->: Integer value currently unused</P -></LI -><LI -><P -><CODE -CLASS="CONSTANT" ->pwdMustChange</CODE ->: Integer value currently unused</P -></LI -><LI -><P -><CODE -CLASS="CONSTANT" ->homeDrive</CODE ->: 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 -><CODE -CLASS="CONSTANT" ->scriptPath</CODE ->: 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 -><CODE -CLASS="CONSTANT" ->profilePath</CODE ->: 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 -><CODE -CLASS="CONSTANT" ->smbHome</CODE ->: 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 -><CODE -CLASS="CONSTANT" ->userWorkstation</CODE ->: character string value currently unused. - </P -></LI -><LI -><P -><CODE -CLASS="CONSTANT" ->rid</CODE ->: the integer representation of the user's relative identifier - (RID).</P -></LI -><LI -><P -><CODE -CLASS="CONSTANT" ->primaryGroupID</CODE ->: 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 <VAR -CLASS="PARAMETER" ->logon home</VAR -> 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 <VAR -CLASS="PARAMETER" ->logon home</VAR -> 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="AEN629" ->3.6.9. Example LDIF Entries for a sambaAccount</A -></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="AEN637" ->3.7. MySQL</A -></H2 -><DIV -CLASS="SECT2" -><H3 -CLASS="SECT2" -><A -NAME="AEN639" ->3.7.1. Creating the database</A -></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<VAR -CLASS="REPLACEABLE" ->username</VAR -> -h<VAR -CLASS="REPLACEABLE" ->hostname</VAR -> -p<VAR -CLASS="REPLACEABLE" ->password</VAR -> <VAR -CLASS="REPLACEABLE" ->databasename</VAR -> < <TT -CLASS="FILENAME" ->/path/to/samba/examples/pdb/mysql/mysql.dump</TT -></B -> </P -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN649" ->3.7.2. Configuring</A -></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] mysql: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="AEN666" ->3.7.3. Using plaintext passwords or encrypted password</A -></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="AEN671" ->3.7.4. Getting non-column data from the table</A -></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="AEN679" ->3.8. XML</A -></H2 -><P ->This module requires libxml2 to be installed.</P -><P ->The usage of pdb_xml is pretty straightforward. To export data, use: - -<KBD -CLASS="USERINPUT" ->pdbedit -e xml:filename</KBD -> - -(where filename is the name of the file to put the data in)</P -><P ->To import data, use: -<KBD -CLASS="USERINPUT" ->pdbedit -i xml:filename -e current-pdb</KBD -> - -Where filename is the name to read the data from and current-pdb to put it in.</P -></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="AEN688" -></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="#SERVERTYPE" ->Nomenclature of Server Types</A -></DT -><DD -><DL -><DT ->4.1. <A -HREF="#AEN717" ->Stand Alone Server</A -></DT -><DT ->4.2. <A -HREF="#AEN724" ->Domain Member Server</A -></DT -><DT ->4.3. <A -HREF="#AEN730" ->Domain Controller</A -></DT -><DD -><DL -><DT ->4.3.1. <A -HREF="#AEN733" ->Domain Controller Types</A -></DT -></DL -></DD -></DL -></DD -><DT ->5. <A -HREF="#SECURITYLEVELS" ->Samba as Stand-Alone Server</A -></DT -><DD -><DL -><DT ->5.1. <A -HREF="#AEN766" ->User and Share security level</A -></DT -><DD -><DL -><DT ->5.1.1. <A -HREF="#AEN769" ->User Level Security</A -></DT -><DT ->5.1.2. <A -HREF="#AEN779" ->Share Level Security</A -></DT -><DT ->5.1.3. <A -HREF="#AEN785" ->Server Level Security</A -></DT -><DT ->5.1.4. <A -HREF="#AEN825" ->Domain Level Security</A -></DT -><DT ->5.1.5. <A -HREF="#AEN848" ->ADS Level Security</A -></DT -></DL -></DD -></DL -></DD -><DT ->6. <A -HREF="#SAMBA-PDC" ->Samba as an NT4 or Win2k Primary Domain Controller</A -></DT -><DD -><DL -><DT ->6.1. <A -HREF="#AEN878" ->Prerequisite Reading</A -></DT -><DT ->6.2. <A -HREF="#AEN883" ->Background</A -></DT -><DT ->6.3. <A -HREF="#AEN923" ->Configuring the Samba Domain Controller</A -></DT -><DT ->6.4. <A -HREF="#AEN965" ->Creating Machine Trust Accounts and Joining Clients to the Domain</A -></DT -><DD -><DL -><DT ->6.4.1. <A -HREF="#AEN1008" ->Manual Creation of Machine Trust Accounts</A -></DT -><DT ->6.4.2. <A -HREF="#AEN1049" ->"On-the-Fly" Creation of Machine Trust Accounts</A -></DT -><DT ->6.4.3. <A -HREF="#AEN1058" ->Joining the Client to the Domain</A -></DT -></DL -></DD -><DT ->6.5. <A -HREF="#AEN1073" ->Common Problems and Errors</A -></DT -><DT ->6.6. <A -HREF="#AEN1119" ->What other help can I get?</A -></DT -><DT ->6.7. <A -HREF="#AEN1233" ->Domain Control for Windows 9x/ME</A -></DT -><DD -><DL -><DT ->6.7.1. <A -HREF="#AEN1256" ->Configuration Instructions: Network Logons</A -></DT -></DL -></DD -></DL -></DD -><DT ->7. <A -HREF="#SAMBA-BDC" ->Samba Backup Domain Controller to Samba Domain Control</A -></DT -><DD -><DL -><DT ->7.1. <A -HREF="#AEN1286" ->Prerequisite Reading</A -></DT -><DT ->7.2. <A -HREF="#AEN1290" ->Background</A -></DT -><DT ->7.3. <A -HREF="#AEN1298" ->What qualifies a Domain Controller on the network?</A -></DT -><DD -><DL -><DT ->7.3.1. <A -HREF="#AEN1301" ->How does a Workstation find its domain controller?</A -></DT -><DT ->7.3.2. <A -HREF="#AEN1304" ->When is the PDC needed?</A -></DT -></DL -></DD -><DT ->7.4. <A -HREF="#AEN1307" ->Can Samba be a Backup Domain Controller to an NT PDC?</A -></DT -><DT ->7.5. <A -HREF="#AEN1312" ->How do I set up a Samba BDC?</A -></DT -><DD -><DL -><DT ->7.5.1. <A -HREF="#AEN1329" ->How do I replicate the smbpasswd file?</A -></DT -><DT ->7.5.2. <A -HREF="#AEN1333" ->Can I do this all with LDAP?</A -></DT -></DL -></DD -></DL -></DD -><DT ->8. <A -HREF="#ADS" ->Samba as a ADS domain member</A -></DT -><DD -><DL -><DT ->8.1. <A -HREF="#AEN1355" ->Setup your <TT -CLASS="FILENAME" ->smb.conf</TT -></A -></DT -><DT ->8.2. <A -HREF="#AEN1368" ->Setup your <TT -CLASS="FILENAME" ->/etc/krb5.conf</TT -></A -></DT -><DT ->8.3. <A -HREF="#ADS-CREATE-MACHINE-ACCOUNT" ->Create the computer account</A -></DT -><DD -><DL -><DT ->8.3.1. <A -HREF="#AEN1396" ->Possible errors</A -></DT -></DL -></DD -><DT ->8.4. <A -HREF="#ADS-TEST-SERVER" ->Test your server setup</A -></DT -><DT ->8.5. <A -HREF="#ADS-TEST-SMBCLIENT" ->Testing with <SPAN -CLASS="APPLICATION" ->smbclient</SPAN -></A -></DT -><DT ->8.6. <A -HREF="#AEN1416" ->Notes</A -></DT -></DL -></DD -><DT ->9. <A -HREF="#DOMAIN-SECURITY" ->Samba as a NT4 or Win2k domain member</A -></DT -><DD -><DL -><DT ->9.1. <A -HREF="#AEN1439" ->Joining an NT Domain with Samba 3.0</A -></DT -><DT ->9.2. <A -HREF="#AEN1493" ->Why is this better than security = server?</A -></DT -></DL -></DD -></DL -></DIV -></DIV -><DIV -CLASS="CHAPTER" -><HR><H1 -><A -NAME="SERVERTYPE" -></A ->Chapter 4. Nomenclature of Server Types</H1 -><P ->Adminstrators of Microsoft networks often refer to there being three -different type of servers:</P -><P -></P -><UL -><LI -><P ->Stand Alone Server</P -></LI -><LI -><P ->Domain Member Server</P -></LI -><LI -><P ->Domain Controller</P -><P -></P -><UL -><LI -><P ->Primary Domain Controller</P -></LI -><LI -><P ->Backup Domain Controller</P -></LI -><LI -><P ->ADS Domain Controller</P -></LI -></UL -></LI -></UL -><P ->A network administrator who is familiar with these terms and who -wishes to migrate to or use Samba will want to know what these terms mean -within a Samba context.</P -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN717" ->4.1. Stand Alone Server</A -></H2 -><P ->The term <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->stand alone server</I -></SPAN -> means that the server -will provide local authentication and access control for all resources -that are available from it. In general this means that there will be a -local user database. In more technical terms, it means that resources -on the machine will either be made available in either SHARE mode or in -USER mode. SHARE mode and USER mode security are documented under -discussions regarding "security mode". The smb.conf configuration parameters -that control security mode are: "security = user" and "security = share".</P -><P ->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 -><P ->Samba tends to blur the distinction a little in respect of what is -a stand alone server. This is because the authentication database may be -local or on a remote server, even if from the samba protocol perspective -the samba server is NOT a member of a domain security context.</P -><P ->Through the use of PAM (Pluggable Authentication Modules) and nsswitch -(the name service switcher) the source of authentication may reside on -another server. We would be inclined to call this the authentication server. -This means that the samba server may use the local Unix/Linux system -password database (/etc/passwd or /etc/shadow), may use a local smbpasswd -file (/etc/samba/smbpasswd or /usr/local/samba/lib/private/smbpasswd), or -may use an LDAP back end, or even via PAM and Winbind another CIFS/SMB -server for authentication.</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN724" ->4.2. Domain Member Server</A -></H2 -><P ->This mode of server operation involves the samba machine being made a member -of a domain security context. This means by definition that all user authentication -will be done from a centrally defined authentication regime. The authentication -regime may come from an NT3/4 style (old domain technology) server, or it may be -provided from an Active Directory server (ADS) running on MS Windows 2000 or later.</P -><P -><SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->Of course it should be clear that the authentication back end itself could be from any -distributed directory architecture server that is supported by Samba. This can be -LDAP (from OpenLDAP), or Sun's iPlanet, of NetWare Directory Server, etc.</I -></SPAN -></P -><P ->Please refer to the section on Howto configure Samba as a Primary Domain Controller -and for more information regarding how to create a domain machine account for a -domain member server as well as for information regading how to enable the samba -domain member machine to join the domain and to be fully trusted by it.</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN730" ->4.3. Domain Controller</A -></H2 -><P ->Over the years public perceptions of what Domain Control really is has taken on an -almost mystical nature. Before we branch into a brief overview of what Domain Control -is the following types of controller are known:</P -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN733" ->4.3.1. Domain Controller Types</A -></H3 -><P -></P -><TABLE -BORDER="0" -><TBODY -><TR -><TD ->Primary Domain Controller</TD -></TR -><TR -><TD ->Backup Domain Controller</TD -></TR -><TR -><TD ->ADS Domain Controller</TD -></TR -></TBODY -></TABLE -><P -></P -><P ->The <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->Primary Domain Controller</I -></SPAN -> or PDC plays an important role in the MS -Windows NT3 and NT4 Domain Control architecture, but not in the manner that so many -expect. The PDC seeds the Domain Control database (a part of the Windows registry) and -it plays a key part in synchronisation of the domain authentication database. </P -><P ->New to Samba-3.0.0 is the ability to use a back-end file that holds the same type of data as -the NT4 style SAM (Security Account Manager) database (one of the registry files). -The samba-3.0.0 SAM can be specified via the smb.conf file parameter "passwd backend" and -valid options include <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" -> smbpasswd tdbsam ldapsam nisplussam plugin unixsam</I -></SPAN ->. -The smbpasswd, tdbsam and ldapsam options can have a "_nua" suffix to indicate that No Unix -Accounts need to be created. In other words, the Samba SAM will be independant of Unix/Linux -system accounts, provided a uid range is defined from which SAM accounts can be created.</P -><P ->The <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->Backup Domain Controller</I -></SPAN -> or BDC plays a key role in servicing network -authentication requests. The BDC is biased to answer logon requests so that on a network segment -that has a BDC and a PDC the BDC will be most likely to service network logon requests. The PDC will -answer network logon requests when the BDC is too busy (high load). A BDC can be promoted to -a PDC. If the PDC is on line at the time that the BDC is promoted to PDC the previous PDC is -automatically demoted to a BDC.</P -><P ->At this time Samba is NOT capable of acting as an <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->ADS Domain Controller</I -></SPAN ->. </P -></DIV -></DIV -></DIV -><DIV -CLASS="CHAPTER" -><HR><H1 -><A -NAME="SECURITYLEVELS" -></A ->Chapter 5. Samba as Stand-Alone Server</H1 -><P ->In this section the function and purpose of Samba's <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->security</I -></SPAN -> -modes are described.</P -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN766" ->5.1. User and Share security level</A -></H2 -><P ->A SMB server tells the client at startup what "security level" it is -running. There are two options "share level" and "user level". Which -of these two the client receives affects the way the client then tries -to authenticate itself. It does not directly affect (to any great -extent) the way the Samba server does security. I know this is -strange, but it fits in with the client/server approach of SMB. In SMB -everything is initiated and controlled by the client, and the server -can only tell the client what is available and whether an action is -allowed. </P -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN769" ->5.1.1. User Level Security</A -></H3 -><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 -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN779" ->5.1.2. Share Level Security</A -></H3 -><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 <B -CLASS="COMMAND" ->user =</B -> <TT -CLASS="FILENAME" ->smb.conf</TT -> -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 -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN785" ->5.1.3. Server Level Security</A -></H3 -><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 -CLASS="SECT3" -><HR><H4 -CLASS="SECT3" -><A -NAME="AEN790" ->5.1.3.1. Configuring Samba for Seemless Windows Network Integration</A -></H4 -><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 requests.</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 ->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, support was dropped 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 -service connection 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 -> = <VAR -CLASS="REPLACEABLE" ->integer</VAR -> - <A -HREF="smb.conf.5.html#USERNAMELEVEL" -TARGET="_top" ->username level</A -> = <VAR -CLASS="REPLACEABLE" ->integer</VAR -></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 <VAR -CLASS="PARAMETER" ->username level</VAR -> parameter -is rarely needed.</P -><P ->However, passwords 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 <VAR -CLASS="PARAMETER" ->password level</VAR -> -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 <VAR -CLASS="PARAMETER" ->password level</VAR -> 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 -><DIV -CLASS="SECT3" -><HR><H4 -CLASS="SECT3" -><A -NAME="AEN816" ->5.1.3.2. Use MS Windows NT as an authentication server</A -></H4 -><P ->This method involves the additions of the following parameters in the <TT -CLASS="FILENAME" ->smb.conf</TT -> 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 -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN825" ->5.1.4. Domain Level Security</A -></H3 -><P ->When samba is operating in <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->security = domain</I -></SPAN -> mode this means that -the Samba server has a domain security trust account (a machine account) and will cause -all authentication requests to be passed through to the domain controllers.</P -><DIV -CLASS="SECT3" -><HR><H4 -CLASS="SECT3" -><A -NAME="AEN829" ->5.1.4.1. Samba as a member of an MS Windows NT security domain</A -></H4 -><P ->This method involves additon of the following paramters in the <TT -CLASS="FILENAME" ->smb.conf</TT -> 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 <B -CLASS="COMMAND" ->password server</B -> will cause samba to locate the -domain controller in a way analogous to the way this is done within MS Windows NT. -This is the default behaviour.</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 -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN848" ->5.1.5. ADS Level Security</A -></H3 -><P ->For information about the configuration option please refer to the entire section entitled -<SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->Samba as an ADS Domain Member.</I -></SPAN -></P -></DIV -></DIV -></DIV -><DIV -CLASS="CHAPTER" -><HR><H1 -><A -NAME="SAMBA-PDC" -></A ->Chapter 6. Samba as an NT4 or Win2k Primary Domain Controller</H1 -><DIV -CLASS="SECT1" -><H2 -CLASS="SECT1" -><A -NAME="AEN878" ->6.1. Prerequisite Reading</A -></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.</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN883" ->6.2. Background</A -></H2 -><P ->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.</P -><P -></P -><UL -><LI -><P -> Domain logons for Windows NT 4.0 / 200x / XP Professional clients. - </P -></LI -><LI -><P -> Placing Windows 9x / Me clients in user level security - </P -></LI -><LI -><P -> Retrieving a list of users and groups from a Samba PDC to - Windows 9x / Me / NT / 200x / XP Professional clients - </P -></LI -><LI -><P -> Roaming Profiles - </P -></LI -><LI -><P -> Network/System Policies - </P -></LI -></UL -><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 ->Roaming Profiles and System/Network policies are advanced network administration topics -that are covered separately in this document.</P -></TD -></TR -></TABLE -></DIV -><P ->The following functionalities are new to the Samba 3.0 release:</P -><P -></P -><UL -><LI -><P -> Windows NT 4 domain trusts - </P -></LI -><LI -><P -> Adding users via the User Manager for Domains - </P -></LI -></UL -><P ->The following functionalities are NOT provided by Samba 3.0:</P -><P -></P -><UL -><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 -> Acting as a Windows 2000 Domain Controller (i.e. Kerberos and - Active Directory) - </P -></LI -></UL -><P ->Please note that Windows 9x / Me / XP Home 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 / Win2k type domain logons and has been officially supported for some -time.</P -><P -><SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->MS Windows XP Home edition is NOT able to join a domain and does not permit -the use of domain logons.</I -></SPAN -></P -><P ->Implementing a Samba PDC can basically be divided into 3 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 -><LI -><P -> Adding and managing domain user accounts - </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.</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN923" ->6.3. Configuring the Samba Domain Controller</A -></H2 -><P ->The first step in creating a working Samba PDC is to -understand the parameters necessary in smb.conf. Here we -attempt to explain the parameters that are covered in -<A -HREF="smb.conf.5.html" -TARGET="_top" -> the smb.conf -man page</A ->.</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 -> = <VAR -CLASS="REPLACEABLE" ->POGO</VAR -> - <A -HREF="smb.conf.5.html#WORKGROUP" -TARGET="_top" ->workgroup</A -> = <VAR -CLASS="REPLACEABLE" ->NARNIA</VAR -> - - ; 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 -> = <VAR -CLASS="REPLACEABLE" ->ntadmin</VAR -> - -; 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="#PASSDB" ->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 ->Samba 3.0 offers a complete implementation of group mapping -between Windows NT groups and Unix groups (this is really quite -complicated to explain in a short space).</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN965" ->6.4. Creating Machine Trust Accounts and Joining Clients to the Domain</A -></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, 200x, XP Professional clients use machine trust -accounts, but Windows 9x / Me / XP Home clients do not. Hence, a -Windows 9x / Me / XP Home 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-3 PDC also has to stoe machine trust account information -in a suitable back-end data store. With Samba-3 there can be multiple back-ends -for this including:</P -><P -></P -><UL -><LI -><P -> <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->smbpaswd</I -></SPAN -> - the plain ascii file stored used by - earlier versions of Samba. This file configuration option requires - a Unix/Linux system account for EVERY entry (ie: both for user and for - machine accounts). This file will be located in the <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->private</I -></SPAN -> - directory (default is /usr/local/samba/lib/private or on linux /etc/samba). - </P -></LI -><LI -><P -> <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->smbpasswd_nua</I -></SPAN -> - This file is independant of the - system wide user accounts. The use of this back-end option requires - specification of the "non unix account range" option also. It is called - smbpasswd and will be located in the <TT -CLASS="FILENAME" ->private</TT -> directory. - </P -></LI -><LI -><P -> <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->tdbsam</I -></SPAN -> - a binary database backend that will be - stored in the <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->private</I -></SPAN -> directory in a file called - <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->passwd.tdb</I -></SPAN ->. The key benefit of this binary format - file is that it can store binary objects that can not be accomodated - in the traditional plain text smbpasswd file. - </P -></LI -><LI -><P -> <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->tdbsam_nua</I -></SPAN -> like the smbpasswd_nua option above, this - file allows the creation of arbitrary user and machine accounts without - requiring that account to be added to the system (/etc/passwd) file. It - too requires the specification of the "non unix account range" option - in the [globals] section of the smb.conf file. - </P -></LI -><LI -><P -> <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->ldapsam</I -></SPAN -> - An LDAP based back-end. Permits the - LDAP server to be specified. eg: ldap://localhost or ldap://frodo.murphy.com - </P -></LI -><LI -><P -> <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->ldapsam_nua</I -></SPAN -> - LDAP based back-end with no unix - account requirement, like smbpasswd_nua and tdbsam_nua above. - </P -></LI -></UL -><P ->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="AEN1008" ->6.4.1. Manual Creation of Machine Trust Accounts</A -></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 -> <SAMP -CLASS="PROMPT" ->root# </SAMP -><B -CLASS="COMMAND" ->/usr/sbin/useradd -g 100 -d /dev/null -c <VAR -CLASS="REPLACEABLE" ->"machine -nickname"</VAR -> -s /bin/false <VAR -CLASS="REPLACEABLE" ->machine_name</VAR ->$ </B -></P -><P -><SAMP -CLASS="PROMPT" ->root# </SAMP -><B -CLASS="COMMAND" ->passwd -l <VAR -CLASS="REPLACEABLE" ->machine_name</VAR ->$</B -></P -><P ->On *BSD systems, this can be done using the 'chpass' utility:</P -><P -><SAMP -CLASS="PROMPT" ->root# </SAMP -><B -CLASS="COMMAND" ->chpass -a "<VAR -CLASS="REPLACEABLE" ->machine_name</VAR ->$:*:101:100::0:0:Workstation <VAR -CLASS="REPLACEABLE" ->machine_name</VAR ->:/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:<VAR -CLASS="REPLACEABLE" ->machine_nickname</VAR ->:/dev/null:/bin/false</PRE -></P -><P ->Above, <VAR -CLASS="REPLACEABLE" ->machine_nickname</VAR -> can be any -descriptive name for the client, i.e., BasementComputer. -<VAR -CLASS="REPLACEABLE" ->machine_name</VAR -> 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 -><SAMP -CLASS="PROMPT" ->root# </SAMP -><B -CLASS="COMMAND" ->smbpasswd -a -m <VAR -CLASS="REPLACEABLE" ->machine_name</VAR -></B -></P -><P ->where <VAR -CLASS="REPLACEABLE" ->machine_name</VAR -> 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="AEN1049" ->6.4.2. "On-the-Fly" Creation of Machine Trust Accounts</A -></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="AEN1058" ->6.4.3. Joining the Client to the Domain</A -></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="AEN1073" ->6.5. Common Problems and Errors</A -></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 -> <SAMP -CLASS="PROMPT" ->C:\WINNT\></SAMP -> <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 again or consult your - system administrator" when attempting to logon. - </P -><P -> This occurs when the domain SID stored in the secrets.tdb database - is changed. The most common cause of a change in domain SID is when - the domain name and/or the server name (netbios name) is changed. - The only way to correct the problem is to restore the original domain - SID or remove the domain client from the domain and rejoin. The domain - SID may be reset using either the smbpasswd or rpcclient utilities. - </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 <VAR -CLASS="PARAMETER" ->add user script</VAR -> 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 - <VAR -CLASS="PARAMETER" ->account</VAR -> 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="AEN1119" ->6.6. What other help can I get?</A -></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="AEN1233" ->6.7. Domain Control for Windows 9x/ME</A -></H2 -><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. Samba-3 does this -now in the same way that MS Windows NT/2K.</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 this documentation under the browsing discussions. -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 are 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="AEN1256" ->6.7.1. Configuration Instructions: Network Logons</A -></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 <CODE -CLASS="CONSTANT" ->USER</CODE ->. The only security mode -which will not work due to technical reasons is <CODE -CLASS="CONSTANT" ->SHARE</CODE -> -mode security. <CODE -CLASS="CONSTANT" ->DOMAIN</CODE -> and <CODE -CLASS="CONSTANT" ->SERVER</CODE -> -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 -></DIV -><DIV -CLASS="CHAPTER" -><HR><H1 -><A -NAME="SAMBA-BDC" -></A ->Chapter 7. Samba Backup Domain Controller to Samba Domain Control</H1 -><DIV -CLASS="SECT1" -><H2 -CLASS="SECT1" -><A -NAME="AEN1286" ->7.1. Prerequisite Reading</A -></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="AEN1290" ->7.2. Background</A -></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="AEN1298" ->7.3. What qualifies a Domain Controller on the network?</A -></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="AEN1301" ->7.3.1. How does a Workstation find its domain controller?</A -></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="AEN1304" ->7.3.2. When is the PDC needed?</A -></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="AEN1307" ->7.4. Can Samba be a Backup Domain Controller to an NT PDC?</A -></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="AEN1312" ->7.5. How do I set up a Samba BDC?</A -></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="AEN1329" ->7.5.1. How do I replicate the smbpasswd file?</A -></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="AEN1333" ->7.5.2. Can I do this all with LDAP?</A -></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 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 -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN1355" ->8.1. Setup your <TT -CLASS="FILENAME" ->smb.conf</TT -></A -></H2 -><P ->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 -><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 ->You do *not* need a smbpasswd file, and older clients will - be authenticated as if <B -CLASS="COMMAND" ->security = domain</B ->, - 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 -></TD -></TR -></TABLE -></DIV -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN1368" ->8.2. Setup your <TT -CLASS="FILENAME" ->/etc/krb5.conf</TT -></A -></H2 -><P ->The minimal configuration for <TT -CLASS="FILENAME" ->krb5.conf</TT -> is:</P -><P -><PRE -CLASS="PROGRAMLISTING" ->[realms] - YOUR.KERBEROS.REALM = { - kdc = your.kerberos.server - }</PRE -></P -><P ->Test your config by doing a <KBD -CLASS="USERINPUT" ->kinit <VAR -CLASS="REPLACEABLE" ->USERNAME</VAR ->@<VAR -CLASS="REPLACEABLE" ->REALM</VAR -></KBD -> and making sure that - your password is accepted by the Win2000 KDC. </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 ->The realm must be uppercase. </P -></TD -></TR -></TABLE -></DIV -><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 -<TT -CLASS="FILENAME" ->/etc/hosts</TT -> 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 <SPAN -CLASS="APPLICATION" ->smbclient</SPAN -> then you can skip -straight to <A -HREF="#ADS-TEST-SMBCLIENT" ->Test with <SPAN -CLASS="APPLICATION" ->smbclient</SPAN -></A -> now. -<A -HREF="#ADS-CREATE-MACHINE-ACCOUNT" ->Creating a computer account</A -> -and <A -HREF="#ADS-TEST-SERVER" ->testing your servers</A -> -is only needed if you want kerberos -support for <SPAN -CLASS="APPLICATION" ->smbd</SPAN -> and <SPAN -CLASS="APPLICATION" ->winbindd</SPAN ->.</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="ADS-CREATE-MACHINE-ACCOUNT" ->8.3. Create the computer account</A -></H2 -><P ->As a user that has write permission on the Samba private directory -(usually root) run: -<KBD -CLASS="USERINPUT" ->net ads join</KBD -></P -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN1396" ->8.3.1. Possible errors</A -></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="ADS-TEST-SERVER" ->8.4. Test your server setup</A -></H2 -><P ->On a Windows 2000 client try <KBD -CLASS="USERINPUT" ->net use * \\server\share</KBD ->. You should -be logged in with kerberos without needing to know a password. If -this fails then run <KBD -CLASS="USERINPUT" ->klist tickets</KBD ->. 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="ADS-TEST-SMBCLIENT" ->8.5. Testing with <SPAN -CLASS="APPLICATION" ->smbclient</SPAN -></A -></H2 -><P ->On your Samba server try to login to a Win2000 server or your Samba -server using <SPAN -CLASS="APPLICATION" ->smbclient</SPAN -> and kerberos. Use <SPAN -CLASS="APPLICATION" ->smbclient</SPAN -> as usual, but -specify the <VAR -CLASS="PARAMETER" ->-k</VAR -> option to choose kerberos authentication.</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN1416" ->8.6. Notes</A -></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 9. Samba as a NT4 or Win2k domain member</H1 -><DIV -CLASS="SECT1" -><H2 -CLASS="SECT1" -><A -NAME="AEN1439" ->9.1. Joining an NT Domain with Samba 3.0</A -></H2 -><P ->Assume you have a Samba 3.0 server with a NetBIOS name of - <CODE -CLASS="CONSTANT" ->SERV1</CODE -> and are joining an or Win2k NT domain called - <CODE -CLASS="CONSTANT" ->DOM</CODE ->, which has a PDC with a NetBIOS name - of <CODE -CLASS="CONSTANT" ->DOMPDC</CODE -> and two backup domain controllers - with NetBIOS names <CODE -CLASS="CONSTANT" ->DOMBDC1</CODE -> and <CODE -CLASS="CONSTANT" ->DOMBDC2 - </CODE ->.</P -><P ->Firstly, you must edit your <TT -CLASS="FILENAME" ->smb.conf</TT -> 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" -> <VAR -CLASS="PARAMETER" ->security =</VAR -></A -> line in the [global] section - of your <TT -CLASS="FILENAME" ->smb.conf</TT -> to read:</P -><P -><B -CLASS="COMMAND" ->security = domain</B -></P -><P ->Next change the <A -HREF="smb.conf.5.html#WORKGROUP" -TARGET="_top" -><VAR -CLASS="PARAMETER" -> workgroup =</VAR -></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" -> <VAR -CLASS="PARAMETER" ->encrypt passwords</VAR -></A -> set to <CODE -CLASS="CONSTANT" ->yes - </CODE -> 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" -> <VAR -CLASS="PARAMETER" ->password server =</VAR -></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 -><SAMP -CLASS="PROMPT" ->root# </SAMP -><KBD -CLASS="USERINPUT" ->net rpc join -S DOMPDC - -U<VAR -CLASS="REPLACEABLE" ->Administrator%password</VAR -></KBD -></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 <VAR -CLASS="REPLACEABLE" ->Administrator%password</VAR -> 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 -><SAMP -CLASS="COMPUTEROUTPUT" ->Joined domain DOM.</SAMP -> - or <SAMP -CLASS="COMPUTEROUTPUT" ->Joined 'SERV1' to realm 'MYREALM'</SAMP -> - </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="AEN1493" ->9.2. Why is this better than security = server?</A -></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 <CODE -CLASS="CONSTANT" ->DOM\fred - </CODE -> 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 -><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 -> 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 -></TD -></TR -></TABLE -></DIV -></DIV -></DIV -></DIV -><DIV -CLASS="PART" -><A -NAME="OPTIONAL" -></A -><DIV -CLASS="TITLEPAGE" -><H1 -CLASS="TITLE" ->III. Advanced Configuration</H1 -><DIV -CLASS="PARTINTRO" -><A -NAME="AEN1511" -></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 ->10. <A -HREF="#UNIX-PERMISSIONS" ->UNIX Permission Bits and Windows NT Access Control Lists</A -></DT -><DD -><DL -><DT ->10.1. <A -HREF="#AEN1525" ->Viewing and changing UNIX permissions using the NT - security dialogs</A -></DT -><DT ->10.2. <A -HREF="#AEN1531" ->How to view file security on a Samba share</A -></DT -><DT ->10.3. <A -HREF="#AEN1542" ->Viewing file ownership</A -></DT -><DT ->10.4. <A -HREF="#AEN1562" ->Viewing file or directory permissions</A -></DT -><DD -><DL -><DT ->10.4.1. <A -HREF="#AEN1577" ->File Permissions</A -></DT -><DT ->10.4.2. <A -HREF="#AEN1591" ->Directory Permissions</A -></DT -></DL -></DD -><DT ->10.5. <A -HREF="#AEN1598" ->Modifying file or directory permissions</A -></DT -><DT ->10.6. <A -HREF="#AEN1620" ->Interaction with the standard Samba create mask - parameters</A -></DT -><DT ->10.7. <A -HREF="#AEN1673" ->Interaction with the standard Samba file attribute - mapping</A -></DT -></DL -></DD -><DT ->11. <A -HREF="#GROUPMAPPING" ->Configuring Group Mapping</A -></DT -><DT ->12. <A -HREF="#PRINTING" ->Printing Support</A -></DT -><DD -><DL -><DT ->12.1. <A -HREF="#AEN1736" ->Introduction</A -></DT -><DT ->12.2. <A -HREF="#AEN1758" ->Configuration</A -></DT -><DD -><DL -><DT ->12.2.1. <A -HREF="#AEN1766" ->Creating [print$]</A -></DT -><DT ->12.2.2. <A -HREF="#AEN1801" ->Setting Drivers for Existing Printers</A -></DT -><DT ->12.2.3. <A -HREF="#AEN1817" ->Support a large number of printers</A -></DT -><DT ->12.2.4. <A -HREF="#AEN1832" ->Adding New Printers via the Windows NT APW</A -></DT -><DT ->12.2.5. <A -HREF="#AEN1862" ->Samba and Printer Ports</A -></DT -></DL -></DD -><DT ->12.3. <A -HREF="#AEN1870" ->The Imprints Toolset</A -></DT -><DD -><DL -><DT ->12.3.1. <A -HREF="#AEN1874" ->What is Imprints?</A -></DT -><DT ->12.3.2. <A -HREF="#AEN1884" ->Creating Printer Driver Packages</A -></DT -><DT ->12.3.3. <A -HREF="#AEN1887" ->The Imprints server</A -></DT -><DT ->12.3.4. <A -HREF="#AEN1891" ->The Installation Client</A -></DT -></DL -></DD -><DT ->12.4. <A -HREF="#AEN1913" ->Diagnosis</A -></DT -><DD -><DL -><DT ->12.4.1. <A -HREF="#AEN1915" ->Introduction</A -></DT -><DT ->12.4.2. <A -HREF="#AEN1931" ->Debugging printer problems</A -></DT -><DT ->12.4.3. <A -HREF="#AEN1940" ->What printers do I have?</A -></DT -><DT ->12.4.4. <A -HREF="#AEN1948" ->Setting up printcap and print servers</A -></DT -><DT ->12.4.5. <A -HREF="#AEN1976" ->Job sent, no output</A -></DT -><DT ->12.4.6. <A -HREF="#AEN1987" ->Job sent, strange output</A -></DT -><DT ->12.4.7. <A -HREF="#AEN1999" ->Raw PostScript printed</A -></DT -><DT ->12.4.8. <A -HREF="#AEN2002" ->Advanced Printing</A -></DT -><DT ->12.4.9. <A -HREF="#AEN2005" ->Real debugging</A -></DT -></DL -></DD -></DL -></DD -><DT ->13. <A -HREF="#CUPS-PRINTING" ->CUPS Printing Support</A -></DT -><DD -><DL -><DT ->13.1. <A -HREF="#AEN2025" ->Introduction</A -></DT -><DT ->13.2. <A -HREF="#AEN2032" ->Configuring <TT -CLASS="FILENAME" ->smb.conf</TT -> for CUPS</A -></DT -><DT ->13.3. <A -HREF="#AEN2052" ->CUPS - RAW Print Through Mode</A -></DT -><DT ->13.4. <A -HREF="#AEN2111" ->CUPS as a network PostScript RIP -- CUPS drivers working on server, Adobe -PostScript driver with CUPS-PPDs downloaded to clients</A -></DT -><DT ->13.5. <A -HREF="#AEN2132" ->Windows Terminal Servers (WTS) as CUPS clients</A -></DT -><DT ->13.6. <A -HREF="#AEN2136" ->Setting up CUPS for driver download</A -></DT -><DT ->13.7. <A -HREF="#AEN2149" ->Sources of CUPS drivers / PPDs</A -></DT -><DD -><DL -><DT ->13.7.1. <A -HREF="#AEN2176" -><B -CLASS="COMMAND" ->cupsaddsmb</B -></A -></DT -></DL -></DD -><DT ->13.8. <A -HREF="#AEN2205" ->The CUPS Filter Chains</A -></DT -><DT ->13.9. <A -HREF="#AEN2244" ->CUPS Print Drivers and Devices</A -></DT -><DD -><DL -><DT ->13.9.1. <A -HREF="#AEN2251" ->Further printing steps</A -></DT -></DL -></DD -><DT ->13.10. <A -HREF="#AEN2321" ->Limiting the number of pages users can print</A -></DT -><DT ->13.11. <A -HREF="#AEN2417" ->Advanced Postscript Printing from MS Windows</A -></DT -><DT ->13.12. <A -HREF="#AEN2432" ->Auto-Deletion of CUPS spool files</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="#AEN2506" ->Abstract</A -></DT -><DT ->14.2. <A -HREF="#AEN2510" ->Introduction</A -></DT -><DT ->14.3. <A -HREF="#AEN2523" ->What Winbind Provides</A -></DT -><DD -><DL -><DT ->14.3.1. <A -HREF="#AEN2530" ->Target Uses</A -></DT -></DL -></DD -><DT ->14.4. <A -HREF="#AEN2534" ->How Winbind Works</A -></DT -><DD -><DL -><DT ->14.4.1. <A -HREF="#AEN2539" ->Microsoft Remote Procedure Calls</A -></DT -><DT ->14.4.2. <A -HREF="#AEN2543" ->Microsoft Active Directory Services</A -></DT -><DT ->14.4.3. <A -HREF="#AEN2546" ->Name Service Switch</A -></DT -><DT ->14.4.4. <A -HREF="#AEN2562" ->Pluggable Authentication Modules</A -></DT -><DT ->14.4.5. <A -HREF="#AEN2570" ->User and Group ID Allocation</A -></DT -><DT ->14.4.6. <A -HREF="#AEN2574" ->Result Caching</A -></DT -></DL -></DD -><DT ->14.5. <A -HREF="#AEN2577" ->Installation and Configuration</A -></DT -><DD -><DL -><DT ->14.5.1. <A -HREF="#AEN2582" ->Introduction</A -></DT -><DT ->14.5.2. <A -HREF="#AEN2595" ->Requirements</A -></DT -><DT ->14.5.3. <A -HREF="#AEN2609" ->Testing Things Out</A -></DT -></DL -></DD -><DT ->14.6. <A -HREF="#AEN2834" ->Limitations</A -></DT -><DT ->14.7. <A -HREF="#AEN2844" ->Conclusion</A -></DT -></DL -></DD -><DT ->15. <A -HREF="#ADVANCEDNETWORKMANAGEMENT" ->Advanced Network Manangement</A -></DT -><DD -><DL -><DT ->15.1. <A -HREF="#AEN2859" ->Configuring Samba Share Access Controls</A -></DT -><DD -><DL -><DT ->15.1.1. <A -HREF="#AEN2869" ->Share Permissions Management</A -></DT -></DL -></DD -><DT ->15.2. <A -HREF="#AEN2897" ->Remote Server Administration</A -></DT -><DT ->15.3. <A -HREF="#AEN2914" ->Network Logon Script Magic</A -></DT -></DL -></DD -><DT ->16. <A -HREF="#POLICYMGMT" ->System and Account Policies</A -></DT -><DD -><DL -><DT ->16.1. <A -HREF="#AEN2929" ->Creating and Managing System Policies</A -></DT -><DD -><DL -><DT ->16.1.1. <A -HREF="#AEN2943" ->Windows 9x/Me Policies</A -></DT -><DT ->16.1.2. <A -HREF="#AEN2955" ->Windows NT4 Style Policy Files</A -></DT -><DT ->16.1.3. <A -HREF="#AEN2973" ->MS Windows 200x / XP Professional Policies</A -></DT -></DL -></DD -><DT ->16.2. <A -HREF="#AEN3002" ->Managing Account/User Policies</A -></DT -><DD -><DL -><DT ->16.2.1. <A -HREF="#AEN3017" ->With Windows NT4/200x</A -></DT -><DT ->16.2.2. <A -HREF="#AEN3020" ->With a Samba PDC</A -></DT -></DL -></DD -></DL -></DD -><DT ->17. <A -HREF="#PROFILEMGMT" ->Desktop Profile Management</A -></DT -><DD -><DL -><DT ->17.1. <A -HREF="#AEN3035" ->Roaming Profiles</A -></DT -><DD -><DL -><DT ->17.1.1. <A -HREF="#AEN3042" ->Samba Configuration for Profile Handling</A -></DT -><DT ->17.1.2. <A -HREF="#AEN3077" ->Windows Client Profile Configuration Information</A -></DT -><DT ->17.1.3. <A -HREF="#AEN3197" ->Sharing Profiles between W9x/Me and NT4/200x/XP workstations</A -></DT -><DT ->17.1.4. <A -HREF="#AEN3204" ->Profile Migration from Windows NT4/200x Server to Samba</A -></DT -></DL -></DD -><DT ->17.2. <A -HREF="#AEN3242" ->Mandatory profiles</A -></DT -><DT ->17.3. <A -HREF="#AEN3249" ->Creating/Managing Group Profiles</A -></DT -><DT ->17.4. <A -HREF="#AEN3255" ->Default Profile for Windows Users</A -></DT -><DD -><DL -><DT ->17.4.1. <A -HREF="#AEN3259" ->MS Windows 9x/Me</A -></DT -><DT ->17.4.2. <A -HREF="#AEN3271" ->MS Windows NT4 Workstation</A -></DT -><DT ->17.4.3. <A -HREF="#AEN3325" ->MS Windows 200x/XP</A -></DT -></DL -></DD -></DL -></DD -><DT ->18. <A -HREF="#INTERDOMAINTRUSTS" ->Interdomain Trust Relationships</A -></DT -><DD -><DL -><DT ->18.1. <A -HREF="#AEN3386" ->Trust Relationship Background</A -></DT -><DT ->18.2. <A -HREF="#AEN3395" ->MS Windows NT4 Trust Configuration</A -></DT -><DD -><DL -><DT ->18.2.1. <A -HREF="#AEN3398" ->NT4 as the Trusting Domain</A -></DT -><DT ->18.2.2. <A -HREF="#AEN3401" ->NT4 as the Trusted Domain</A -></DT -></DL -></DD -><DT ->18.3. <A -HREF="#AEN3405" ->Configuring Samba Domain Trusts</A -></DT -><DD -><DL -><DT ->18.3.1. <A -HREF="#AEN3409" ->Samba3 as the Trusting Domain</A -></DT -><DT ->18.3.2. <A -HREF="#AEN3416" ->Samba3 as the Trusted Domain</A -></DT -></DL -></DD -></DL -></DD -><DT ->19. <A -HREF="#PAM" ->PAM Configuration for Centrally Managed Authentication</A -></DT -><DD -><DL -><DT ->19.1. <A -HREF="#AEN3440" ->Samba and PAM</A -></DT -><DT ->19.2. <A -HREF="#AEN3491" ->Distributed Authentication</A -></DT -><DT ->19.3. <A -HREF="#AEN3496" ->PAM Configuration in smb.conf</A -></DT -></DL -></DD -><DT ->20. <A -HREF="#VFS" ->Stackable VFS modules</A -></DT -><DD -><DL -><DT ->20.1. <A -HREF="#AEN3531" ->Introduction and configuration</A -></DT -><DT ->20.2. <A -HREF="#AEN3540" ->Included modules</A -></DT -><DD -><DL -><DT ->20.2.1. <A -HREF="#AEN3542" ->audit</A -></DT -><DT ->20.2.2. <A -HREF="#AEN3550" ->extd_audit</A -></DT -><DT ->20.2.3. <A -HREF="#AEN3554" ->recycle</A -></DT -><DT ->20.2.4. <A -HREF="#AEN3591" ->netatalk</A -></DT -></DL -></DD -><DT ->20.3. <A -HREF="#AEN3598" ->VFS modules available elsewhere</A -></DT -><DD -><DL -><DT ->20.3.1. <A -HREF="#AEN3602" ->DatabaseFS</A -></DT -><DT ->20.3.2. <A -HREF="#AEN3610" ->vscan</A -></DT -></DL -></DD -></DL -></DD -><DT ->21. <A -HREF="#MSDFS" ->Hosting a Microsoft Distributed File System tree on Samba</A -></DT -><DD -><DL -><DT ->21.1. <A -HREF="#AEN3626" ->Instructions</A -></DT -><DD -><DL -><DT ->21.1.1. <A -HREF="#AEN3661" ->Notes</A -></DT -></DL -></DD -></DL -></DD -><DT ->22. <A -HREF="#INTEGRATE-MS-NETWORKS" ->Integrating MS Windows networks with Samba</A -></DT -><DD -><DL -><DT ->22.1. <A -HREF="#AEN3688" ->Name Resolution in a pure Unix/Linux world</A -></DT -><DD -><DL -><DT ->22.1.1. <A -HREF="#AEN3704" -><TT -CLASS="FILENAME" ->/etc/hosts</TT -></A -></DT -><DT ->22.1.2. <A -HREF="#AEN3720" -><TT -CLASS="FILENAME" ->/etc/resolv.conf</TT -></A -></DT -><DT ->22.1.3. <A -HREF="#AEN3731" -><TT -CLASS="FILENAME" ->/etc/host.conf</TT -></A -></DT -><DT ->22.1.4. <A -HREF="#AEN3739" -><TT -CLASS="FILENAME" ->/etc/nsswitch.conf</TT -></A -></DT -></DL -></DD -><DT ->22.2. <A -HREF="#AEN3751" ->Name resolution as used within MS Windows networking</A -></DT -><DD -><DL -><DT ->22.2.1. <A -HREF="#AEN3763" ->The NetBIOS Name Cache</A -></DT -><DT ->22.2.2. <A -HREF="#AEN3768" ->The LMHOSTS file</A -></DT -><DT ->22.2.3. <A -HREF="#AEN3776" ->HOSTS file</A -></DT -><DT ->22.2.4. <A -HREF="#AEN3781" ->DNS Lookup</A -></DT -><DT ->22.2.5. <A -HREF="#AEN3784" ->WINS Lookup</A -></DT -></DL -></DD -></DL -></DD -><DT ->23. <A -HREF="#IMPROVED-BROWSING" ->Improved browsing in samba</A -></DT -><DD -><DL -><DT ->23.1. <A -HREF="#AEN3804" ->Overview of browsing</A -></DT -><DT ->23.2. <A -HREF="#AEN3810" ->Browsing support in samba</A -></DT -><DT ->23.3. <A -HREF="#AEN3825" ->Problem resolution</A -></DT -><DT ->23.4. <A -HREF="#AEN3837" ->Browsing across subnets</A -></DT -><DD -><DL -><DT ->23.4.1. <A -HREF="#AEN3843" ->How does cross subnet browsing work ?</A -></DT -></DL -></DD -><DT ->23.5. <A -HREF="#AEN3878" ->Setting up a WINS server</A -></DT -><DT ->23.6. <A -HREF="#AEN3901" ->Setting up Browsing in a WORKGROUP</A -></DT -><DT ->23.7. <A -HREF="#AEN3927" ->Setting up Browsing in a DOMAIN</A -></DT -><DT ->23.8. <A -HREF="#BROWSE-FORCE-MASTER" ->Forcing samba to be the master</A -></DT -><DT ->23.9. <A -HREF="#AEN3962" ->Making samba the domain master</A -></DT -><DT ->23.10. <A -HREF="#AEN3984" ->Note about broadcast addresses</A -></DT -><DT ->23.11. <A -HREF="#AEN3987" ->Multiple interfaces</A -></DT -></DL -></DD -><DT ->24. <A -HREF="#SECURING-SAMBA" ->Securing Samba</A -></DT -><DD -><DL -><DT ->24.1. <A -HREF="#AEN4003" ->Introduction</A -></DT -><DT ->24.2. <A -HREF="#AEN4006" ->Using host based protection</A -></DT -><DT ->24.3. <A -HREF="#AEN4016" ->Using interface protection</A -></DT -><DT ->24.4. <A -HREF="#AEN4025" ->Using a firewall</A -></DT -><DT ->24.5. <A -HREF="#AEN4032" ->Using a IPC$ share deny</A -></DT -><DT ->24.6. <A -HREF="#AEN4041" ->Upgrading Samba</A -></DT -></DL -></DD -><DT ->25. <A -HREF="#UNICODE" ->Unicode/Charsets</A -></DT -><DD -><DL -><DT ->25.1. <A -HREF="#AEN4056" ->What are charsets and unicode?</A -></DT -><DT ->25.2. <A -HREF="#AEN4065" ->Samba and charsets</A -></DT -></DL -></DD -></DL -></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="AEN1525" ->10.1. Viewing and changing UNIX permissions using the NT - security dialogs</A -></H2 -><P ->Windows NT clients can 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 -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 -> All access to Unix/Linux system file via Samba is controlled at - the operating system file access control level. When trying to - figure out file access problems it is vitally important to identify - the identity of the Windows user as it is presented by Samba at - the point of file access. This can best be determined from the - Samba log files. - </P -></TD -></TR -></TABLE -></DIV -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN1531" ->10.2. How to view file security on a Samba share</A -></H2 -><P ->From an NT4/2000/XP 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 file properties dialog - box. Click on the tab <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->Security</I -></SPAN -> 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="AEN1542" ->10.3. Viewing file ownership</A -></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 <VAR -CLASS="REPLACEABLE" ->SERVER</VAR -> is the NetBIOS name of - the Samba server, <VAR -CLASS="REPLACEABLE" ->user</VAR -> is the user name of - the UNIX user who owns the file, and <VAR -CLASS="REPLACEABLE" ->(Long name)</VAR -> - 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 <VAR -CLASS="PARAMETER" ->nt acl support</VAR -> - is set to <CODE -CLASS="CONSTANT" ->false</CODE -> 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 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="AEN1562" ->10.4. Viewing file or directory permissions</A -></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 <VAR -CLASS="REPLACEABLE" ->SERVER</VAR -> is the NetBIOS name of - the Samba server, <VAR -CLASS="REPLACEABLE" ->user</VAR -> is the user name of - the UNIX user who owns the file, and <VAR -CLASS="REPLACEABLE" ->(Long name)</VAR -> - is the descriptive string identifying the user (normally found in the - GECOS field of the UNIX password database).</P -><P ->If the parameter <VAR -CLASS="PARAMETER" ->nt acl support</VAR -> - is set to <CODE -CLASS="CONSTANT" ->false</CODE -> 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="AEN1577" ->10.4.1. File Permissions</A -></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="AEN1591" ->10.4.2. Directory Permissions</A -></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="AEN1598" ->10.5. Modifying file or directory permissions</A -></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 <VAR -CLASS="PARAMETER" ->nt acl support</VAR -> - is set to <CODE -CLASS="CONSTANT" ->false</CODE -> 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 (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="AEN1620" ->10.6. Interaction with the standard Samba create mask - parameters</A -></H2 -><P ->There are four parameters - to control interaction with the standard Samba create mask parameters. - These are :</P -><P -><VAR -CLASS="PARAMETER" ->security mask</VAR -></P -><P -><VAR -CLASS="PARAMETER" ->force security mode</VAR -></P -><P -><VAR -CLASS="PARAMETER" ->directory security mask</VAR -></P -><P -><VAR -CLASS="PARAMETER" ->force directory security mode</VAR -></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" -> - <VAR -CLASS="PARAMETER" ->security mask</VAR -></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 <VAR -CLASS="PARAMETER" ->security mask</VAR -> - 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" -><VAR -CLASS="PARAMETER" ->create mask - </VAR -></A -> parameter. 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" -> <VAR -CLASS="PARAMETER" ->force security mode</VAR -></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 <VAR -CLASS="PARAMETER" ->force security mode - </VAR -> 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" -><VAR -CLASS="PARAMETER" ->force - create mode</VAR -></A -> parameter. - 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 <VAR -CLASS="PARAMETER" ->security mask</VAR -> and <VAR -CLASS="PARAMETER" ->force - security mode</VAR -> 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 <VAR -CLASS="PARAMETER" -> directory security mask</VAR -> instead of <VAR -CLASS="PARAMETER" ->security - mask</VAR ->, and <VAR -CLASS="PARAMETER" ->force directory security mode - </VAR -> parameter instead of <VAR -CLASS="PARAMETER" ->force security mode - </VAR ->.</P -><P ->The <VAR -CLASS="PARAMETER" ->directory security mask</VAR -> parameter - by default is set to the same value as the <VAR -CLASS="PARAMETER" ->directory mask - </VAR -> parameter and the <VAR -CLASS="PARAMETER" ->force directory security - mode</VAR -> parameter by default is set to the same value as - the <VAR -CLASS="PARAMETER" ->force directory mode</VAR -> parameter. </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 <TT -CLASS="FILENAME" ->smb.conf</TT -> file in that share specific section :</P -><P -><VAR -CLASS="PARAMETER" ->security mask = 0777</VAR -></P -><P -><VAR -CLASS="PARAMETER" ->force security mode = 0</VAR -></P -><P -><VAR -CLASS="PARAMETER" ->directory security mask = 0777</VAR -></P -><P -><VAR -CLASS="PARAMETER" ->force directory security mode = 0</VAR -></P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN1673" ->10.7. Interaction with the standard Samba file attribute - mapping</A -></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="GROUPMAPPING" -></A ->Chapter 11. Configuring Group Mapping</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 -<SPAN -CLASS="APPLICATION" ->smbgroupedit</SPAN ->.</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 -><KBD -CLASS="USERINPUT" ->smbgroupedit -c "Domain Admins" -u domadm</KBD -></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 -><KBD -CLASS="USERINPUT" ->smbgroupedit -a unixgroup -td</KBD -></P -><P ->You can list the various groups in the mapping database like this</P -><P -><KBD -CLASS="USERINPUT" ->smbgroupedit -v</KBD -></P -></DIV -><DIV -CLASS="CHAPTER" -><HR><H1 -><A -NAME="PRINTING" -></A ->Chapter 12. Printing Support</H1 -><DIV -CLASS="SECT1" -><H2 -CLASS="SECT1" -><A -NAME="AEN1736" ->12.1. Introduction</A -></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="AEN1758" ->12.2. Configuration</A -></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 <VAR -CLASS="PARAMETER" ->printer driver location</VAR -> -to be used on a per share basis to specify the location of -the driver files associated with that printer. Another -parameter named <VAR -CLASS="PARAMETER" ->printer driver</VAR -> 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="AEN1766" ->12.2.1. Creating [print$]</A -></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" -><VAR -CLASS="PARAMETER" ->write list</VAR -></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 -><SAMP -CLASS="COMPUTEROUTPUT" ->[print$]----- - |-W32X86 ; "Windows NT x86" - |-WIN40 ; "Windows 95/98" - |-W32ALPHA ; "Windows NT Alpha_AXP" - |-W32MIPS ; "Windows NT R4000" - |-W32PPC ; "Windows NT PowerPC"</SAMP -></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" -><VAR -CLASS="PARAMETER" ->printer - admin</VAR -></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 <VAR -CLASS="PARAMETER" ->printer admin</VAR ->) 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="AEN1801" ->12.2.2. Setting Drivers for Existing Printers</A -></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="AEN1817" ->12.2.3. Support a large number of printers</A -></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 -><SAMP -CLASS="PROMPT" ->$ </SAMP -><KBD -CLASS="USERINPUT" ->rpcclient pogo -U root%secret -c "enumdrivers"</KBD -> -<PRE -CLASS="PROGRAMLISTING" -> -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]</PRE -> -<SAMP -CLASS="PROMPT" ->$ </SAMP -><KBD -CLASS="USERINPUT" ->rpcclient pogo -U root%secret -c "enumprinters"</KBD -> -<PRE -CLASS="PROGRAMLISTING" ->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:[] - </PRE -> -<SAMP -CLASS="PROMPT" ->$ </SAMP -><KBD -CLASS="USERINPUT" ->rpcclient pogo -U root%secret -c "setdriver hp-print \"HP LaserJet 4000 Series PS\""</KBD -> -<PRE -CLASS="PROGRAMLISTING" ->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="AEN1832" ->12.2.4. Adding New Printers via the Windows NT APW</A -></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 <VAR -CLASS="PARAMETER" ->printer admin</VAR ->). - </P -></LI -><LI -><P -><A -HREF="smb.conf.5.html#SHOWADDPRINTERWIZARD" -TARGET="_top" -><VAR -CLASS="PARAMETER" ->show - add printer wizard = yes</VAR -></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" -><VAR -CLASS="PARAMETER" ->add -printer command</VAR -></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 <VAR -CLASS="PARAMETER" ->add printer -command</VAR -> 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 -<VAR -CLASS="PARAMETER" ->add printer program</VAR -> 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" -><VAR -CLASS="PARAMETER" ->delete -printer command</VAR -></A -> for removing entries from the "Printers..." -folder.</P -><P ->The following is an example <A -HREF="smb.conf.5.html#ADDPRINTERCOMMAN" -TARGET="_top" -><VAR -CLASS="PARAMETER" ->add printer command</VAR -></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="AEN1862" ->12.2.5. Samba and Printer Ports</A -></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" -><VAR -CLASS="PARAMETER" ->enumports -command</VAR -></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="AEN1870" ->12.3. The Imprints Toolset</A -></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="AEN1874" ->12.3.1. What is Imprints?</A -></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="AEN1884" ->12.3.2. Creating Printer Driver Packages</A -></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="AEN1887" ->12.3.3. The Imprints server</A -></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="AEN1891" ->12.3.4. The Installation Client</A -></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="AEN1913" ->12.4. Diagnosis</A -></H2 -><DIV -CLASS="SECT2" -><H3 -CLASS="SECT2" -><A -NAME="AEN1915" ->12.4.1. Introduction</A -></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="AEN1931" ->12.4.2. Debugging printer problems</A -></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="AEN1940" ->12.4.3. What printers do I have?</A -></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="AEN1948" ->12.4.4. Setting up printcap and print servers</A -></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="AEN1976" ->12.4.5. Job sent, no output</A -></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="AEN1987" ->12.4.6. Job sent, strange output</A -></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="AEN1999" ->12.4.7. Raw PostScript printed</A -></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="AEN2002" ->12.4.8. Advanced Printing</A -></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="AEN2005" ->12.4.9. Real debugging</A -></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="CUPS-PRINTING" -></A ->Chapter 13. CUPS Printing Support</H1 -><DIV -CLASS="SECT1" -><H2 -CLASS="SECT1" -><A -NAME="AEN2025" ->13.1. Introduction</A -></H2 -><P ->The Common Unix Print System (CUPS) has become very popular, but to many it is -a very mystical tool. There is a great deal of uncertainty regarding CUPS and how -it works. The result is seen in a large number of posting on the samba mailing lists -expressing frustration when MS Windows printers appear not to work with a CUPS -backr-end. -/para> </P -><P ->This is a good time to point out how CUPS can be used and what it does. CUPS is more -than just a print spooling system - it is a complete printer management system that -complies with HTTP and IPP protocols. It can be managed remotely via a web browser -and it can print using http and ipp protocols.</P -><P ->CUPS allows to creation of RAW printers (ie: NO file format translation) as well as -SMART printers (ie: CUPS does file format conversion as required for the printer). In -many ways this gives CUPS similar capabilities to the MS Windows print monitoring -system. Of course, if you are a CUPS advocate, you would agrue that CUPS is better! -In any case, let us now move on to explore how one may configure CUPS for interfacing -with MS Windows print clients via Samba.</P -><P -><A -HREF="http://www.cups.org/" -TARGET="_top" ->CUPS</A -> is a newcomer in the UNIX printing scene, -which has convinced many people upon first trial already. However, it has quite a few -new features, which make it different from other, more traditional printing systems.</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN2032" ->13.2. Configuring <TT -CLASS="FILENAME" ->smb.conf</TT -> for CUPS</A -></H2 -><P ->Printing with CUPS in the most basic <TT -CLASS="FILENAME" ->smb.conf</TT -> -setup in Samba-3 only needs two settings: <B -CLASS="COMMAND" ->printing = cups</B -> and -<B -CLASS="COMMAND" ->printcap = cups</B ->. While CUPS itself doesn't need a printcap -anymore, the <TT -CLASS="FILENAME" ->cupsd.conf</TT -> configuration file knows two directives -(example: <B -CLASS="COMMAND" ->Printcap /etc/printcap</B -> and <B -CLASS="COMMAND" ->PrintcapFormat -BSD</B ->), which control if such a file should be created for the -convenience of third party applications. Make sure it is set! For details see -<B -CLASS="COMMAND" ->man cupsd.conf</B -> and other CUPS-related documentation.</P -><P ->If SAMBA is compiled against libcups, then <B -CLASS="COMMAND" ->printcap = cups</B -> uses the -CUPS API to list printers, submit jobs, etc. Otherwise it maps to the System V commands -with an additional <VAR -CLASS="PARAMETER" ->-oraw</VAR -> option for printing. On a Linux system, -you can use the <B -CLASS="COMMAND" ->ldd</B -> command to find out details (ldd may not be -present on other OS platforms, or its function may be embodied by a different command):</P -><P -><PRE -CLASS="PROGRAMLISTING" ->transmeta:/home/kurt # ldd `which smbd` - libssl.so.0.9.6 => /usr/lib/libssl.so.0.9.6 (0x4002d000) - libcrypto.so.0.9.6 => /usr/lib/libcrypto.so.0.9.6 (0x4005a000) - libcups.so.2 => /usr/lib/libcups.so.2 (0x40123000) - libdl.so.2 => /lib/libdl.so.2 (0x401e8000) - libnsl.so.1 => /lib/libnsl.so.1 (0x401ec000) - libpam.so.0 => /lib/libpam.so.0 (0x40202000) - libc.so.6 => /lib/libc.so.6 (0x4020b000) - /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)</PRE -></P -><P ->The line "libcups.so.2 => /usr/lib/libcups.so.2 -(0x40123000)" shows there is CUPS support compiled into this version of -Samba. If this is the case, and <B -CLASS="COMMAND" ->printing = cups</B -> is set, then any -otherwise manually set print command in <TT -CLASS="FILENAME" ->smb.conf</TT -> is ignored.</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN2052" ->13.3. CUPS - RAW Print Through Mode</A -></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 ->When used in raw print through mode is will be necessary to use the printer -vendor's drivers in each Windows client PC.</P -></TD -></TR -></TABLE -></DIV -><P ->When CUPS printers are configured for RAW print-through mode operation it is the -responsibility of the Samba client to fully render the print job (file) in a format -that is suitable for direct delivery to the printer. In this case CUPS will NOT -do any print file format conversion work.</P -><P ->The CUPS files that need to be correctly set for RAW mode printers to work are: - -<P -></P -><UL -><LI -><P -><TT -CLASS="FILENAME" ->/etc/cups/mime.types</TT -></P -><P -></P -></LI -><LI -><P -><TT -CLASS="FILENAME" ->/etc/cups/mime.convs</TT -></P -><P -></P -></LI -></UL -> - -Both contain entries that must be uncommented to allow <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->RAW</I -></SPAN -> mode -operation.</P -><P ->Firstly, to enable CUPS based printing from Samba the following options must be -enabled in your <TT -CLASS="FILENAME" ->smb.conf</TT -> file [globals] section: - -<P -></P -><UL -><LI -><P ->printing = CUPS</P -></LI -><LI -><P ->printcap = CUPS</P -></LI -></UL -> - -When these parameters are specified the print directives in <TT -CLASS="FILENAME" ->smb.conf</TT -> (as well as in -samba itself) will be ignored because samba will directly interface with CUPS through -it's application program interface (API) - so long as Samba has been compiled with -CUPS library (libcups) support. If samba has NOT been compiled with CUPS support then -printing will use the System V AT&T command set with the <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->-oraw</I -></SPAN -> -option automatically passing through.</P -><P ->Cupsomatic (an enhanced printing utility that is part of some CUPS implementations) -on the Samba/CUPS server does *not* add any features if a file is really -printed "raw". However, if you have loaded the driver for the Windows client from -the CUPS server, using the "cupsaddsmb" utility, and if this driver is one using -a "Foomatic" PPD, the PJL header in question is already added on the Windows client, -at the time when the driver initially generated the PostScript data and CUPS in true -"-oraw" manner doesn't remove this PJL header and passes the file "as is" to its -printer communication backend.</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 ->NOTE: editing in the "mime.convs" and the "mime.types" file does not *enforce* -"raw" printing, it only *allows* it.</P -></TD -></TR -></TABLE -></DIV -><P ->Print files that arrive from MS Windows printing are "auto-typed" by CUPS. This aids -the process of determining proper treatment while in the print queue system. - -<P -></P -><UL -><LI -><P -> Files generated by PCL drivers and directed at PCK printers get auto-typed as - <TT -CLASS="FILENAME" ->application/octet-stream</TT ->. Unknown file format types also - get auto-typed with this tag. - </P -></LI -><LI -><P -> Files generated by a Postscript driver and directed at a Postscript printer - are auto-typed depending on the auto-detected most suitable MIME type as: - - <P -></P -><UL -><LI -><P ->* application/postscript</P -></LI -><LI -><P ->* application/vnd.cups-postscript</P -></LI -></UL -> - </P -></LI -></UL -></P -><P ->"application/postscript" first goes thru the "pstops" filter (where the page counting -and accounting takes place). The outcome will be of MIME type -"application/vnd.cups-postscript". The pstopsfilter reads and uses information from -the PPD and inserts user-provided options into the PostScript file. As a consequence, -the filtered file could possibly have an unwanted PJL header.</P -><P ->"application/postscript" will be all files with a ".ps", ".ai", ".eps" suffix or which -have as their first character string one of "%!" or "<04>%".</P -><P ->"application/vnd.cups-postscript" will files which contain the string -"LANGUAGE=POSTSCRIPT" (or similar variations with different capitalization) in the -first 512 bytes, and also contain the "PJL super escape code" in the first 128 bytes -("<1B>%-12345X"). Very likely, most PostScript files generated on Windows using a CUPS -or other PPD, will have to be auto-typed as "vnd.cups-postscript". A file produced -with a "Generic PostScript driver" will just be tagged "application/postscript".</P -><P ->Once the file is in "application/vnd.cups-postscript" format, either "pstoraster" -or "cupsomatic" will take over (depending on the printer configuration, as -determined by the PPD in use).</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 ->A printer queue with *no* PPD associated to it is a "raw" printer and all files -will go directly there as received by the spooler. The exeptions are file types -"application/octet-stream" which need "passthrough feature" enabled. -"Raw" queues don't do any filtering at all, they hand the file directly to the -CUPS backend. This backend is responsible for the sending of the data to the device -(as in the "device URI" notation as lpd://, socket://, smb://, ipp://, http://, -parallel:/, serial:/, usb:/ etc.)</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 ->"cupsomatic"/Foomatic are *not* native CUPS drivers and they don't ship with CUPS. -They are a Third Party add-on, developed at Linuxprinting.org. As such, they are -a brilliant hack to make all models (driven by Ghostscript drivers/filters in -traditional spoolers) also work via CUPS, with the same (good or bad!) quality -as in these other spoolers. "cupsomatic" is only a vehicle to execute a ghostscript -commandline at that stage in the CUPS filtering chain, where "normally" the native -CUPS "pstoraster" filter would kick in. cupsomatic by-passes pstoraster, "kidnaps" -the printfile from CUPS away and re-directs it to go through Ghostscipt. CUPS accepts this, -because the associated CUPS-O-Matic-/Foomatic-PPD specifies:</P -><PRE -CLASS="PROGRAMLISTING" -> *cupsFilter: "application/vnd.cups-postscript 0 cupsomatic"</PRE -><P ->This line persuades CUPS to hand the file to cupsomatic, once it has successfully -converted it to the MIME type "application/vnd.cups-postscript". This conversion will not -happen for Jobs arriving from Windows which are auto-typed "application/octet-stream", -with the according changes in "/etc/cups/mime.types" in place.</P -></TD -></TR -></TABLE -></DIV -><P ->CUPS is widely configurable and flexible, even regarding its filtering mechanism. -Another workaround in some situations would be to have -in "/etc/cups/mime.types" entries as follows:</P -><PRE -CLASS="PROGRAMLISTING" -> application/postscript application/vnd.cups-raw 0 - - application/vnd.cups-postscript application/vnd.cups-raw 0 -</PRE -><P ->This would prevent all Postscript files from being filtered (rather, they will go -thru the virtual "nullfilter" denoted with "-"). This could only be useful for -PS printers. If you want to print PS code on non-PS printers an entry as follows -could be useful:</P -><PRE -CLASS="PROGRAMLISTING" -> */* application/vnd.cups-raw 0 -</PRE -><P ->and would effectively send *all* files to the backend without further processing.</P -><P ->Lastly, you could have the following entry:</P -><PRE -CLASS="PROGRAMLISTING" -> application/vnd.cups-postscript application/vnd.cups-raw 0 my_PJL_stripping_filter</PRE -><P ->You will need to write a "my_PJL_stripping_filter" (could be a shellscript) that -parses the PostScript and removes the unwanted PJL. This would need to conform to -CUPS filter design (mainly, receive and pass the parameters printername, job-id, -username, jobtitle, copies, print options and possibly the filename). It would -be installed as world executable into "/usr/lib/cups/filters/" and will be called -by CUPS if it encounters a MIME type "application/vnd.cups-postscript".</P -><P ->CUPS can handle "-o job-hold-until=indefinite". This keeps the job in the queue -"on hold". It will only be printed upon manual release by the printer operator. -This is a requirement in many "central reproduction departments", where a few -operators manage the jobs of hundreds of users on some big machine, where no -user is allowed to have direct access. (The operators often need to load the -proper paper type before running the 10.000 page job requested by marketing -for the mailing, etc.).</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN2111" ->13.4. CUPS as a network PostScript RIP -- CUPS drivers working on server, Adobe -PostScript driver with CUPS-PPDs downloaded to clients</A -></H2 -><P ->CUPS is perfectly able to use PPD files (PostScript -Printer Descriptions). PPDs can control all print device options. They -are usually provided by the manufacturer -- if you own a PostSript printer, -that is. PPD files are always a component of PostScript printer drivers on MS -Windows or Apple Mac OS systems. They are ASCII files containing -user-selectable print options, mapped to appropriate PostScript, PCL or PJL -commands for the target printer. Printer driver GUI dialogs translate these -options "on-the-fly" into buttons and drop-down lists for the user to -select.</P -><P ->CUPS can load, without any conversions, the PPD file from -any Windows (NT is recommended) PostScript driver and handle the options. -There is a web browser interface to the print options (select -http://localhost:631/printers/ and click on one "Configure Printer" button -to see it), a commandline interface (see <B -CLASS="COMMAND" ->man lpoptions</B -> or -try if you have <B -CLASS="COMMAND" ->lphelp</B -> on your system) plus some different GUI frontends on Linux -UNIX, which can present PPD options to the users. PPD options are normally -meant to become evaluated by the PostScript RIP on the real PostScript -printer.</P -><P ->CUPS doesn't stop at "real" PostScript printers in its -usage of PPDs. The CUPS developers have extended the PPD concept, to also -describe available device and driver options for non-PostScript printers -through CUPS-PPDs.</P -><P ->This is logical, as CUPS includes a fully featured -PostScript interpreter (RIP). This RIP is based on Ghostscript. It can -process all received PostScript (and additionally many other file formats) -from clients. All CUPS-PPDs geared to non-PostScript printers contain an -additional line, starting with the keyword <VAR -CLASS="PARAMETER" ->*cupsFilter</VAR ->. -This line -tells the CUPS print system which printer-specific filter to use for the -interpretation of the accompanying PostScript. Thus CUPS lets all its -printers appear as PostScript devices to its clients, because it can act as a -PostScript RIP for those printers, processing the received PostScript code -into a proper raster print format.</P -><P ->CUPS-PPDs can also be used on Windows-Clients, on top of a -PostScript driver (recommended is the Adobe one).</P -><P ->This feature enables CUPS to do a few tricks no other -spooler can do:</P -><P -></P -><UL -><LI -><P ->act as a networked PostScript RIP (Raster Image Processor), handling - printfiles from all client platforms in a uniform way;</P -></LI -><LI -><P ->act as a central accounting and billing server, as all files are passed - through the <B -CLASS="COMMAND" ->pstops</B -> Filter and are therefor logged in - the CUPS <TT -CLASS="FILENAME" ->page_log</TT ->. - <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->NOTE: </I -></SPAN ->this - can not happen with "raw" print jobs, which always remain unfiltered - per definition;</P -></LI -><LI -><P ->enable clients to consolidate on a single PostScript driver, even for - many different target printers.</P -></LI -></UL -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN2132" ->13.5. Windows Terminal Servers (WTS) as CUPS clients</A -></H2 -><P ->This setup may be of special interest to people -experiencing major problems in WTS environments. WTS need often a multitude -of non-PostScript drivers installed to run their clients' variety of -different printer models. This often imposes the price of much increased -instability. In many cases, in an attempt to overcome this problem, site -administrators have resorted to restrict the allowed drivers installed on -their WTS to one generic PCL- and one PostScript driver. This however -restricts the clients in the amount of printer options available for them -- -often they can't get out more then simplex prints from one standard paper -tray, while their devices could do much better, if driven by a different -driver!</P -><P ->Using an Adobe PostScript driver, enabled with a CUPS-PPD, -seems to be a very elegant way to overcome all these shortcomings. The -PostScript driver is not known to cause major stability problems on WTS (even -if used with many different PPDs). The clients will be able to (again) chose -paper trays, duplex printing and other settings. However, there is a certain -price for this too: a CUPS server acting as a PostScript RIP for its clients -requires more CPU and RAM than just to act as a "raw spooling" device. Plus, -this setup is not yet widely tested, although the first feedbacks look very -promising...</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN2136" ->13.6. Setting up CUPS for driver download</A -></H2 -><P ->The <B -CLASS="COMMAND" ->cupsadsmb</B -> utility (shipped with all current -CUPS versions) makes the sharing of any (or all) installed CUPS printers very -easy. Prior to using it, you need the following settings in <TT -CLASS="FILENAME" ->smb.conf</TT ->:</P -><P -><PRE -CLASS="PROGRAMLISTING" ->[global] - load printers = yes - printing = cups - printcap name = cups - - [printers] - comment = All Printers - path = /var/spool/samba - browseable = no - public = yes - guest ok = yes - writable = no - printable = yes - printer admin = root - - [print$] - comment = Printer Drivers - path = /etc/samba/drivers - browseable = yes - guest ok = no - read only = yes - write list = root - </PRE -></P -><P ->For licensing reasons the necessary files of the Adobe -Postscript driver can not be distributed with either Samba or CUPS. You need -to download them yourself from the Adobe website. Once extracted, create a -<TT -CLASS="FILENAME" ->drivers</TT -> directory in the CUPS data directory (usually -<TT -CLASS="FILENAME" ->/usr/share/cups/</TT ->). Copy the Adobe files using -UPPERCASE filenames, to this directory as follows:</P -><P -><PRE -CLASS="PROGRAMLISTING" -> ADFONTS.MFM - ADOBEPS4.DRV - ADOBEPS4.HLP - ADOBEPS5.DLL - ADOBEPSU.DLL - ADOBEPSU.HLP - DEFPRTR2.PPD - ICONLIB.DLL - </PRE -></P -><P ->Users of the ESP Print Pro software are able to install -their "Samba Drivers" package for this purpose with no problem.</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN2149" ->13.7. Sources of CUPS drivers / PPDs</A -></H2 -><P ->On the internet you can find now many thousand CUPS-PPD -files (with their companion filters), in many national languages, -supporting more than 1.000 non-PostScript models.</P -><P -></P -><UL -><LI -><P -><A -HREF="http://wwwl.easysw.com/printpro/" -TARGET="_top" ->ESP PrintPro - (http://wwwl.easysw.com/printpro/)</A -> - (commercial, non-Free) is packaged with more than 3.000 PPDs, ready for - successful usage "out of the box" on Linux, IBM-AIX, HP-UX, Sun-Solaris, - SGI-IRIX, Compaq Tru64, Digital Unix and some more commercial Unices (it - is written by the CUPS developers themselves and its sales help finance - the further development of CUPS, as they feed their creators)</P -></LI -><LI -><P ->the <A -HREF="http://gimp-print.sourceforge.net/" -TARGET="_top" ->Gimp-Print-Project - (http://gimp-print.sourceforge.net/)</A -> - (GPL, Free Software) provides around 120 PPDs (supporting nearly 300 - printers, many driven to photo quality output), to be used alongside the - Gimp-Print CUPS filters;</P -></LI -><LI -><P -><A -HREF="http://www.turboprint.com/" -TARGET="_top" ->TurboPrint - (http://www.turboprint.com/)</A -> - (Shareware, non-Freee) supports roughly the same amount of printers in - excellent quality;</P -></LI -><LI -><P -><A -HREF="http://www-124.ibm.com/developerworks/oss/linux/projects/omni/" -TARGET="_top" ->OMNI - (http://www-124.ibm.com/developerworks/oss/linux/projects/omni/)</A -> - (LPGL, Free) is a package made by IBM, now containing support for more - than 400 printers, stemming from the inheritance of IBM OS/2 KnowHow - ported over to Linux (CUPS support is in a Beta-stage at present);</P -></LI -><LI -><P -><A -HREF="http://hpinkjet.sourceforge.net/" -TARGET="_top" ->HPIJS - (http://hpinkjet.sourceforge.net/)</A -> - (BSD-style licnes, Free) supports around 120 of HP's own printers and is - also providing excellent print quality now;</P -></LI -><LI -><P -><A -HREF="http://www.linuxprinting.org/" -TARGET="_top" ->Foomatic/cupsomatic (http://www.linuxprinting.org/)</A -> - (LPGL, Free) from Linuxprinting.org are providing PPDs for practically every - Ghostscript filter known to the world, now usable with CUPS.</P -></LI -></UL -><P -><SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->NOTE: </I -></SPAN ->the cupsomatic trick from Linuxprinting.org is -working different from the other drivers. While the other drivers take the -generic CUPS raster (produced by CUPS' own pstoraster PostScript RIP) as -their input, cupsomatic "kidnaps" the PostScript inside CUPS, before -RIP-ping, deviates it to an external Ghostscript installation (which now -becomes the RIP) and gives it back to a CUPS backend once Ghostscript is -finished. -- CUPS versions from 1.1.15 and later will provide their pstoraster -PostScript RIP function again inside a system-wide Ghostscript -installation rather than in "their own" pstoraster filter. (This -CUPS-enabling Ghostscript version may be installed either as a -patch to GNU or AFPL Ghostscript, or as a complete ESP Ghostscript package). -However, this will not change the cupsomatic approach of guiding the printjob -along a different path through the filtering system than the standard CUPS -way...</P -><P ->Once you installed a printer inside CUPS with one of the -recommended methods (the lpadmin command, the web browser interface or one of -the available GUI wizards), you can use <B -CLASS="COMMAND" ->cupsaddsmb</B -> to share the -printer via Samba. <B -CLASS="COMMAND" ->cupsaddsmb</B -> prepares the driver files for -comfortable client download and installation upon their first contact with -this printer share.</P -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN2176" ->13.7.1. <B -CLASS="COMMAND" ->cupsaddsmb</B -></A -></H3 -><P ->The <B -CLASS="COMMAND" ->cupsaddsmb</B -> command copies the needed files -for convenient Windows client installations from the previously prepared CUPS -data directory to your [print$] share. Additionally, the PPD -associated with this printer is copied from <TT -CLASS="FILENAME" ->/etc/cups/ppd/</TT -> to -[print$].</P -><P -><PRE -CLASS="PROGRAMLISTING" -><SAMP -CLASS="PROMPT" ->root# </SAMP -> <B -CLASS="COMMAND" ->cupsaddsmb -U root infotec_IS2027</B -> -Password for root required to access localhost via SAMBA: <KBD -CLASS="USERINPUT" ->[type in password 'secret']</KBD -></PRE -></P -><P ->To share all printers and drivers, use the <VAR -CLASS="PARAMETER" ->-a</VAR -> -parameter instead of a printer name.</P -><P ->Probably you want to see what's going on. Use the -<VAR -CLASS="PARAMETER" ->-v</VAR -> parameter to get a more verbose output:</P -><P ->Probably you want to see what's going on. Use the -<VAR -CLASS="PARAMETER" ->-v</VAR -> parameter to get a more verbose output:</P -><P -><PRE -CLASS="PROGRAMLISTING" ->Note: The following line shave been wrapped so that information is not lost. - -<SAMP -CLASS="PROMPT" ->root# </SAMP -> cupsaddsmb -v -U root infotec_IS2027 - Password for root required to access localhost via SAMBA: - Running command: smbclient //localhost/print\$ -N -U'root%secret' -c 'mkdir W32X86;put - /var/spool/cups/tmp/3cd1cc66376c0 W32X86/infotec_IS2027.PPD;put /usr/share/cups/drivers/ - ADOBEPS5.DLL W32X86/ADOBEPS5.DLL;put /usr/share/cups/drivers/ADOBEPSU.DLLr - W32X86/ADOBEPSU.DLL;put /usr/share/cups/drivers/ADOBEPSU.HLP W32X86/ADOBEPSU.HLP' - added interface ip=10.160.16.45 bcast=10.160.31.255 nmask=255.255.240.0 - added interface ip=192.168.182.1 bcast=192.168.182.255 nmask=255.255.255.0 - added interface ip=172.16.200.1 bcast=172.16.200.255 nmask=255.255.255.0 - Domain=[TUX-NET] OS=[Unix] Server=[Samba 2.2.3a.200204262025cvs] - NT_STATUS_OBJECT_NAME_COLLISION making remote directory \W32X86 - putting file /var/spool/cups/tmp/3cd1cc66376c0 as \W32X86/infotec_IS2027.PPD (17394.6 kb/s) - (average 17395.2 kb/s) - putting file /usr/share/cups/drivers/ADOBEPS5.DLL as \W32X86/ADOBEPS5.DLL (10877.4 kb/s) - (average 11343.0 kb/s) - putting file /usr/share/cups/drivers/ADOBEPSU.DLL as \W32X86/ADOBEPSU.DLL (5095.2 kb/s) - (average 9260.4 kb/s) - putting file /usr/share/cups/drivers/ADOBEPSU.HLP as \W32X86/ADOBEPSU.HLP (8828.7 kb/s) - (average 9247.1 kb/s) - - Running command: smbclient //localhost/print\$ -N -U'root%secret' -c 'mkdir WIN40;put - /var/spool/cups/tmp/3cd1cc66376c0 WIN40/infotec_IS2027.PPD;put - /usr/share/cups/drivers/ADFONTS.MFM WIN40/ADFONTS.MFM;put - /usr/share/cups/drivers/ADOBEPS4.DRV WIN40/ADOBEPS4.DRV;put - /usr/share/cups/drivers/ADOBEPS4.HLP WIN40/ADOBEPS4.HLP;put - /usr/share/cups/drivers/DEFPRTR2.PPD WIN40/DEFPRTR2.PPD;put - /usr/share/cups/drivers/ICONLIB.DLL WIN40/ICONLIB.DLL;put - /usr/share/cups/drivers/PSMON.DLL WIN40/PSMON.DLL;' - added interface ip=10.160.16.45 bcast=10.160.31.255 nmask=255.255.240.0 - added interface ip=192.168.182.1 bcast=192.168.182.255 nmask=255.255.255.0 - added interface ip=172.16.200.1 bcast=172.16.200.255 nmask=255.255.255.0 - Domain=[TUX-NET] OS=[Unix] Server=[Samba 2.2.3a.200204262025cvs] - NT_STATUS_OBJECT_NAME_COLLISION making remote directory \WIN40 - putting file /var/spool/cups/tmp/3cd1cc66376c0 as \WIN40/infotec_IS2027.PPD (26091.5 kb/s) - (average 26092.8 kb/s) - putting file /usr/share/cups/drivers/ADFONTS.MFM as \WIN40/ADFONTS.MFM (11241.6 kb/s) - (average 11812.9 kb/s) - putting file /usr/share/cups/drivers/ADOBEPS4.DRV as \WIN40/ADOBEPS4.DRV (16640.6 kb/s) - (average 14679.3 kb/s) - putting file /usr/share/cups/drivers/ADOBEPS4.HLP as \WIN40/ADOBEPS4.HLP (11285.6 kb/s) - (average 14281.5 kb/s) - putting file /usr/share/cups/drivers/DEFPRTR2.PPD as \WIN40/DEFPRTR2.PPD (823.5 kb/s) - (average 12944.0 kb/s) - putting file /usr/share/cups/drivers/ICONLIB.DLL as \WIN40/ICONLIB.DLL (19226.2 kb/s) - (average 13169.7 kb/s) - putting file /usr/share/cups/drivers/PSMON.DLL as \WIN40/PSMON.DLL (18666.1 kb/s) - (average 13266.7 kb/s) - - Running command: rpcclient localhost -N -U'root%secret' -c 'adddriver "Windows NT x86" - "infotec_IS2027:ADOBEPS5.DLL:infotec_IS2027.PPD:ADOBEPSU.DLL:ADOBEPSU.HLP:NULL:RAW:NULL"' - cmd = adddriver "Windows NT x86" "infotec_IS2027:ADOBEPS5.DLL:infotec_IS2027.PPD:ADOBEPSU.DLL: - ADOBEPSU.HLP:NULL:RAW:NULL" - Printer Driver infotec_IS2027 successfully installed. - - Running command: rpcclient localhost -N -U'root%secret' -c 'adddriver "Windows 4.0" - "infotec_IS2027:ADOBEPS4.DRV:infotec_IS2027.PPD:NULL:ADOBEPS4.HLP:PSMON.DLL:RAW: - ADFONTS.MFM,DEFPRTR2.PPD,ICONLIB.DLL"' - cmd = adddriver "Windows 4.0" "infotec_IS2027:ADOBEPS4.DRV:infotec_IS2027.PPD:NULL: - ADOBEPS4.HLP:PSMON.DLL:RAW:ADFONTS.MFM,DEFPRTR2.PPD,ICONLIB.DLL" - Printer Driver infotec_IS2027 successfully installed. - - Running command: rpcclient localhost -N -U'root%secret' - -c 'setdriver infotec_IS2027 infotec_IS2027' - cmd = setdriver infotec_IS2027 infotec_IS2027 - Succesfully set infotec_IS2027 to driver infotec_IS2027. - - <SAMP -CLASS="PROMPT" ->root# </SAMP -></PRE -></P -><P ->If you look closely, you'll discover your root password was transfered unencrypted over -the wire, so beware! Also, if you look further her, you'll discover error messages like -<CODE -CLASS="CONSTANT" ->NT_STATUS_OBJECT_NAME_COLLISION</CODE -> in between. They occur, because -the directories <TT -CLASS="FILENAME" ->WIN40</TT -> and <TT -CLASS="FILENAME" ->W32X86</TT -> already -existed in the [print$] driver download share (from a previous driver -installation). They are harmless here.</P -><P ->Now your printer is prepared for the clients to use. From -a client, browse to the CUPS/Samba server, open the "Printers" -share, right-click on this printer and select "Install..." or -"Connect..." (depending on the Windows version you use). Now their -should be a new printer in your client's local "Printers" folder, -named (in my case) "infotec_IS2027 on kdebitshop"</P -><P -><SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->NOTE: </I -></SPAN -> -<B -CLASS="COMMAND" ->cupsaddsmb</B -> will only reliably work i -with CUPS version 1.1.15 or higher -and Samba from 2.2.4. If it doesn't work, or if the automatic printer -driver download to the clients doesn't succeed, you can still manually -install the CUPS printer PPD on top of the Adobe PostScript driver on -clients and then point the client's printer queue to the Samba printer -share for connection, should you desire to use the CUPS networked -PostScript RIP functions.</P -></DIV -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN2205" ->13.8. The CUPS Filter Chains</A -></H2 -><P ->The following diagrams reveal how CUPS handles print jobs.</P -><PRE -CLASS="PROGRAMLISTING" ->######################################################################### -# -# CUPS in and of itself has this (general) filter chain (CAPITAL -# letters are FILE-FORMATS or MIME types, other are filters (this is -# true for pre-1.1.15 of pre-4.3 versions of CUPS and ESP PrintPro): -# -# <VAR -CLASS="REPLACEABLE" ->SOMETHNG</VAR ->-FILEFORMAT -# | -# | -# V -# <VAR -CLASS="REPLACEABLE" ->something</VAR ->tops -# | -# | -# V -# APPLICATION/POSTSCRIPT -# | -# | -# V -# pstops -# | -# | -# V -# APPLICATION/VND.CUPS-POSTSCRIPT -# | -# | -# V -# pstoraster # as shipped with CUPS, independent from any Ghostscipt -# | # installation on the system -# | (= "postscipt interpreter") -# | -# V -# APPLICATION/VND.CUPS-RASTER -# | -# | -# V -# rasterto<VAR -CLASS="REPLACEABLE" ->something</VAR -> (f.e. Gimp-Print filters may be plugged in here) -# | (= "raster driver") -# | -# V -# SOMETHING-DEVICE-SPECIFIC -# | -# | -# V -# backend -# -# -# ESP PrintPro has some enhanced "rasterto<VAR -CLASS="REPLACEABLE" ->something</VAR ->" filters as compared to -# CUPS, and also a somewhat improved "pstoraster" filter. -# -# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to -# CUPS and ESP PrintPro plug-in where rasterto<VAR -CLASS="REPLACEABLE" ->something</VAR -> is noted. -# -#########################################################################</PRE -><PRE -CLASS="PROGRAMLISTING" ->######################################################################### -# -# This is how "cupsomatic" comes into play: -# ========================================= -# -# <VAR -CLASS="REPLACEABLE" ->SOMETHNG</VAR ->-FILEFORMAT -# | -# | -# V -# <VAR -CLASS="REPLACEABLE" ->something</VAR ->tops -# | -# | -# V -# APPLICATION/POSTSCRIPT -# | -# | -# V -# pstops -# | -# | -# V -# APPLICATION/VND.CUPS-POSTSCRIPT ----------------+ -# | | -# | V -# V cupsomatic -# pstoraster (constructs complicated -# | (= "postscipt interpreter") Ghostscript commandline -# | to let the file be -# V processed by a -# APPLICATION/VND.CUPS-RASTER "-sDEVICE=<VAR -CLASS="REPLACEABLE" ->s.th.</VAR ->" -# | call...) -# | | -# V | -# rasterto<VAR -CLASS="REPLACEABLE" ->something</VAR -> V -# | (= "raster driver") +-------------------------+ -# | | Ghostscript at work.... | -# V | | -# SOMETHING-DEVICE-SPECIFIC *-------------------------+ -# | | -# | | -# V | -# backend >------------------------------------+ -# | -# | -# V -# THE PRINTER -# -# -# Note, that cupsomatic "kidnaps" the printfile after the -# "APPLICATION/VND.CUPS-POSTSCRPT" stage and deviates it through -# the CUPS-external, systemwide Ghostscript installation, bypassing the -# "pstoraster" filter (therefor also bypassing the CUPS-raster-drivers -# "rasterto<VAR -CLASS="REPLACEABLE" ->something</VAR ->", and hands the rasterized file directly to the CUPS -# backend... -# -# cupsomatic is not made by the CUPS developers. It is an independent -# contribution to printing development, made by people from -# Linuxprinting.org. (see also http://www.cups.org/cups-help.html) -# -# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to -# CUPS and ESP PrintPro plug-in where rasterto<VAR -CLASS="REPLACEABLE" ->something</VAR -> is noted. -# -#########################################################################</PRE -><PRE -CLASS="PROGRAMLISTING" ->######################################################################### -# -# And this is how it works for ESP PrintPro from 4.3: -# =================================================== -# -# <VAR -CLASS="REPLACEABLE" ->SOMETHNG</VAR ->-FILEFORMAT -# | -# | -# V -# <VAR -CLASS="REPLACEABLE" ->something</VAR ->tops -# | -# | -# V -# APPLICATION/POSTSCRIPT -# | -# | -# V -# pstops -# | -# | -# V -# APPLICATION/VND.CUPS-POSTSCRIPT -# | -# | -# V -# gsrip -# | (= "postscipt interpreter") -# | -# V -# APPLICATION/VND.CUPS-RASTER -# | -# | -# V -# rasterto<VAR -CLASS="REPLACEABLE" ->something</VAR -> (f.e. Gimp-Print filters may be plugged in here) -# | (= "raster driver") -# | -# V -# SOMETHING-DEVICE-SPECIFIC -# | -# | -# V -# backend -# -# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to -# CUPS and ESP PrintPro plug-in where rasterto<VAR -CLASS="REPLACEABLE" ->something</VAR -> is noted. -# -#########################################################################</PRE -><PRE -CLASS="PROGRAMLISTING" ->######################################################################### -# -# This is how "cupsomatic" would come into play with ESP PrintPro: -# ================================================================ -# -# -# <VAR -CLASS="REPLACEABLE" ->SOMETHNG</VAR ->-FILEFORMAT -# | -# | -# V -# <VAR -CLASS="REPLACEABLE" ->something</VAR ->tops -# | -# | -# V -# APPLICATION/POSTSCRIPT -# | -# | -# V -# pstops -# | -# | -# V -# APPLICATION/VND.CUPS-POSTSCRIPT ----------------+ -# | | -# | V -# V cupsomatic -# gsrip (constructs complicated -# | (= "postscipt interpreter") Ghostscript commandline -# | to let the file be -# V processed by a -# APPLICATION/VND.CUPS-RASTER "-sDEVICE=<VAR -CLASS="REPLACEABLE" ->s.th.</VAR ->" -# | call...) -# | | -# V | -# rasterto<VAR -CLASS="REPLACEABLE" ->something</VAR -> V -# | (= "raster driver") +-------------------------+ -# | | Ghostscript at work.... | -# V | | -# SOMETHING-DEVICE-SPECIFIC *-------------------------+ -# | | -# | | -# V | -# backend >------------------------------------+ -# | -# | -# V -# THE PRINTER -# -# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to -# CUPS and ESP PrintPro plug-in where rasterto<VAR -CLASS="REPLACEABLE" ->something</VAR -> is noted. -# -#########################################################################</PRE -><PRE -CLASS="PROGRAMLISTING" ->######################################################################### -# -# And this is how it works for CUPS from 1.1.15: -# ============================================== -# -# <VAR -CLASS="REPLACEABLE" ->SOMETHNG</VAR ->-FILEFORMAT -# | -# | -# V -# <VAR -CLASS="REPLACEABLE" ->something</VAR ->tops -# | -# | -# V -# APPLICATION/POSTSCRIPT -# | -# | -# V -# pstops -# | -# | -# V -# APPLICATION/VND.CUPS-POSTSCRIPT-----+ -# | -# +------------------v------------------------------+ -# | Ghostscript | -# | at work... | -# | (with | -# | "-sDEVICE=cups") | -# | | -# | (= "postscipt interpreter") | -# | | -# +------------------v------------------------------+ -# | -# | -# APPLICATION/VND.CUPS-RASTER >-------+ -# | -# | -# V -# rasterto<VAR -CLASS="REPLACEABLE" ->something</VAR -> -# | (= "raster driver") -# | -# V -# SOMETHING-DEVICE-SPECIFIC -# | -# | -# V -# backend -# -# -# NOTE: since version 1.1.15 CUPS "outsourced" the pstoraster process to -# Ghostscript. GNU Ghostscript needs to be patched to handle the -# CUPS requirement; ESP Ghostscript has this builtin. In any case, -# "gs -h" needs to show up a "cups" device. pstoraster is now a -# calling an appropriate "gs -sDEVICE=cups..." commandline to do -# the job. It will output "application/vnd.cup-raster", which will -# be finally processed by a CUPS raster driver "rasterto<VAR -CLASS="REPLACEABLE" ->something</VAR ->" -# Note the difference to "cupsomatic", which will *not* output -# CUPS-raster, but a final version of the printfile, ready to be -# sent to the printer. cupsomatic also doesn't use the "cups" -# devicemode in Ghostscript, but one of the classical devicemodes.... -# -# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to -# CUPS and ESP PrintPro plug-in where rasterto<VAR -CLASS="REPLACEABLE" ->something</VAR -> is noted. -# -#########################################################################</PRE -><PRE -CLASS="PROGRAMLISTING" ->######################################################################### -# -# And this is how it works for CUPS from 1.1.15, with cupsomatic included: -# ======================================================================== -# -# <VAR -CLASS="REPLACEABLE" ->SOMETHNG</VAR ->-FILEFORMAT -# | -# | -# V -# <VAR -CLASS="REPLACEABLE" ->something</VAR ->tops -# | -# | -# V -# APPLICATION/POSTSCRIPT -# | -# | -# V -# pstops -# | -# | -# V -# APPLICATION/VND.CUPS-POSTSCRIPT-----+ -# | -# +------------------v------------------------------+ -# | Ghostscript . Ghostscript at work.... | -# | at work... . (with "-sDEVICE= | -# | (with . <VAR -CLASS="REPLACEABLE" ->s.th.</VAR ->" | -# | "-sDEVICE=cups") . | -# | . | -# | (CUPS standard) . (cupsomatic) | -# | . | -# | (= "postscript interpreter") | -# | . | -# +------------------v--------------v---------------+ -# | | -# | | -# APPLICATION/VND.CUPS-RASTER >-------+ | -# | | -# | | -# V | -# rasterto<VAR -CLASS="REPLACEABLE" ->something</VAR -> | -# | (= "raster driver") | -# | | -# V | -# SOMETHING-DEVICE-SPECIFIC >------------------------+ -# | -# | -# V -# backend -# -# -# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to -# CUPS and ESP PrintPro plug-in where rasterto<VAR -CLASS="REPLACEABLE" ->something</VAR -> is noted. -# -##########################################################################</PRE -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN2244" ->13.9. CUPS Print Drivers and Devices</A -></H2 -><P ->CUPS ships with good support for HP LaserJet type printers. You can install -the driver as follows: - -<P -></P -><UL -><LI -><P -> lpadmin -p laserjet4plus -v parallel:/dev/lp0 -E -m laserjet.ppd - </P -></LI -></UL -> - -(The "-m" switch will retrieve the "laserjet.ppd" from the standard repository -for not-yet-installed-PPDs, which CUPS typically stores in -<TT -CLASS="FILENAME" ->/usr/share/cups/model</TT ->. Alternatively, you may use -"-P /absolute/filesystem/path/to/where/there/is/PPD/your.ppd").</P -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN2251" ->13.9.1. Further printing steps</A -></H3 -><P ->Always also consult the database on linuxprinting.org for all recommendations -about which driver is best used for each printer:</P -><P -><A -HREF="http://www.linuxprinting.org/printer_list.cgi" -TARGET="_top" ->http://www.linuxprinting.org/printer_list.cgi</A -></P -><P ->There select your model and click on "Show". You'll arrive at a page listing -all drivers working with your model. There will always be *one* -<SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->recommended</I -></SPAN -> one. Try this one first. In your case -("HP LaserJet 4 Plus"), you'll arrive here:</P -><P -><A -HREF="http://www.linuxprinting.org/show_printer.cgi?recnum=75104" -TARGET="_top" ->http://www.linuxprinting.org/show_printer.cgi?recnum=75104</A -></P -><P ->The recommended driver is "ljet4". It has a link to the page for the ljet4 -driver too:</P -><P -><A -HREF="http://www.linuxprinting.org/show_driver.cgi?driver=ljet4" -TARGET="_top" ->http://www.linuxprinting.org/show_driver.cgi?driver=ljet4</A -> </P -><P ->On the driver's page, you'll find important and detailed info about how to use -that driver within the various available spoolers. You can generate a PPD for -CUPS. The PPD contains all the info about how to use your model and the driver; -this is, once installed, working transparently for the user -- you'll only -need to choose resolution, paper size etc. from the web-based menu or from -the print dialog GUI or from the commandline...</P -><P ->On the driver's page, choose to use the "PPD-O-Matic" online PPD generator -program. Select your model and click "Generate PPD file". When you safe the -appearing ASCII text file, don't use "cut'n'past" (as it could possiblly corrupt -line endings and tabs), but use "Save as..." in your browser's menu. Save it -at "/some/path/on/your/filesystem/somewhere/my-name-for-my-printer.ppd"</P -><P ->Then install the printer:</P -><P -><PRE -CLASS="PROGRAMLISTING" -> "lpadmin -p laserjet4plus -v parallel:/dev/lp0 -E \ - -P /some/path/on/your/filesystem/somewhere/my-name-for-my-printer.ppd"</PRE -></P -><P ->Note, that for all the "Foomatic-PPDs" from Linuxprinting.org, you also need -a special "CUPS filter" named "cupsomatic". Get the latest version of -"cupsomatic" from:</P -><P -><A -HREF="http://www.linuxprinting.org/cupsomatic" -TARGET="_top" ->http://www.linuxprinting.org/cupsomatic</A -></P -><P ->This needs to be copied to <TT -CLASS="FILENAME" ->/usr/lib/cups/filter/cupsomatic</TT -> -and be made world executable. This filter is needed to read and act upon the -specially encoded Foomatic comments, embedded in the printfile, which in turn -are used to construct (transparently for you, the user) the complicated -ghostscript command line needed for your printer/driver combo.</P -><P ->You can have a look at all the options for the Ghostscript commandline supported -by your printer and the ljet4 driver by going to the section "Execution details", -selecting your model (Laserjet 4 Plus) and clicking on "Show execution details". -This will bring up this web page:</P -><P -><A -HREF="http://www.linuxprinting.org/execution.cgi?driver=ljet4&printer=75104&.submit=Show+execution+details" -TARGET="_top" ->http://www.linuxprinting.org/execution.cgi?driver=ljet4&printer=75104&.submit=Show+execution+details</A -></P -><P ->The ingenious thing is that the database is kept current. If there -is a bug fix and an improvement somewhere in the database, you will -always get the most current and stable and feature-rich driver by following -the steps described above.</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 ->Till Kamppeter from MandrakeSoft is doing an excellent job here that too few -people are aware of. (So if you use it often, please send him a note showing -your appreciation).</P -></TD -></TR -></TABLE -></DIV -><P ->The latest and greatest improvement now is support for "custom page sizes" -for all those printers which support it.</P -><P ->"cupsomatic" is documented here:</P -><P -><A -HREF="http://www.linuxprinting.org/cups-doc.html" -TARGET="_top" ->http://www.linuxprinting.org/cups-doc.html</A -></P -><P ->More printing tutorial info may be found here:</P -><P -><A -HREF="http://www.linuxprinting.org/kpfeifle/LinuxKongress2002/Tutorial/" -TARGET="_top" ->http://www.linuxprinting.org/kpfeifle/LinuxKongress2002/Tutorial/</A -></P -><P ->Note, that *all* the Foomatic drivers listed on Linuxprinting.org (now -approaching the "all-time high" number of 1.000 for the supported models) -are using a special filtering chain involving Ghostscript, as described -in this document.</P -><P ->Summary - You need:</P -><P -><P -></P -><TABLE -BORDER="0" -><TBODY -><TR -><TD ->A "foomatic+<VAR -CLASS="REPLACEABLE" ->something</VAR ->" PPD is not enough to print with CUPS (but it is *one* important component)</TD -></TR -><TR -><TD ->The "cupsomatic" filter script (Perl) in <TT -CLASS="FILENAME" ->/usr/lib/cups/filters/</TT -></TD -></TR -><TR -><TD ->Perl to make cupsomatic run</TD -></TR -><TR -><TD ->Ghostscript (because it is called and controlled by the PPD/cupsomatic combo in a way to fit your printermodel/driver combo.</TD -></TR -><TR -><TD ->Ghostscript *must*, depending on the driver/model, contain support for a certain "device" (as shown by "gs -h")</TD -></TR -></TBODY -></TABLE -><P -></P -> </P -><P ->In the case of the "hpijs" driver, you need a Ghostscript version, which -has "ijs" amongst its supported devices in "gs -h". In the case of -"hpijs+foomatic", a valid ghostscript commandline would be reading like this:</P -><P -><PRE -CLASS="PROGRAMLISTING" -> gs -q -dBATCH -dPARANOIDSAFER -dQUIET -dNOPAUSE -sDEVICE=ijs \ - -sIjsServer=hpijs<VAR -CLASS="REPLACEABLE" ->PageSize</VAR -> -dDuplex=<VAR -CLASS="REPLACEABLE" ->Duplex</VAR -> <VAR -CLASS="REPLACEABLE" ->Model</VAR -> \ - -r<VAR -CLASS="REPLACEABLE" ->Resolution</VAR ->,PS:MediaPosition=<VAR -CLASS="REPLACEABLE" ->InputSlot</VAR -> -dIjsUseOutputFD \ - -sOutputFile=- -</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 ->Note, that with CUPS and the "hpijs+foomatic" PPD (plus Perl and cupsomatic) -you don't need to remember this. You can choose the available print options -thru a GUI print command (like "glp" from ESP's commercially supported -PrintPro software, or KDE's "kprinter", or GNOME's "gtklp" or the independent -"xpp") or the CUPS web interface via human-readable drop-down selection -menus.</P -></TD -></TR -></TABLE -></DIV -><P ->If you use "ESP Ghostscript" (also under the GPL, provided by Easy Software -Products, the makers of CUPS, downloadable from -<A -HREF="http://www.cups.org/software.html" -TARGET="_top" ->http://www.cups.org/software.html</A ->, -co-maintained by the developers of linuxprinting.org), you are guaranteed to -have in use the most uptodate, bug-fixed, enhanced and stable version of a Free -Ghostscript. It contains support for ~300 devices, whereas plain vanilla -GNU Ghostscript 7.05 only has ~200.</P -><P ->If you print only one CUPS test page, from the web interface and when you try to -print a windows test page, it acts like the job was never sent: - -<P -></P -><TABLE -BORDER="0" -><TBODY -><TR -><TD ->Can you print "standard" jobs from the CUPS machine?</TD -></TR -><TR -><TD ->Are the jobs from Windows visible in the Web interface on CUPS (http://localhost:631/)?</TD -></TR -><TR -><TD -><SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->Most important:</I -></SPAN -> What kind of printer driver are you using on the Windows clients?</TD -></TR -></TBODY -></TABLE -><P -></P -> - -You can try to get a more detailed debugging info by setting "LogLevel debug" in -<TT -CLASS="FILENAME" ->/etc/cups/cupsd.conf</TT ->, re-start cupsd and investigate <TT -CLASS="FILENAME" ->/var/log/cups/error_log</TT -> -for the whereabouts of your Windows-originating printjobs:</P -><P -></P -><TABLE -BORDER="0" -><TBODY -><TR -><TD ->what does the "auto-typing" line say? which is the "MIME type" CUPS thinks is arriving from the Windows clients?</TD -></TR -><TR -><TD ->are there "filter" available for this MIME type?</TD -></TR -><TR -><TD ->are there "filter rules" defined in "/etc/cups/mime.convs" for this MIME type?</TD -></TR -></TBODY -></TABLE -><P -></P -></DIV -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN2321" ->13.10. Limiting the number of pages users can print</A -></H2 -><P ->The feature you want is dependent on the real print subsystem you're using. -Samba's part is always to receive the job files from the clients (filtered -*or* unfiltered) and hand it over to this printing subsystem.</P -><P ->Of course one could "hack" things with one's own scripts.</P -><P ->But there is CUPS (Common Unix Printing System). CUPS supports "quotas". -Quotas can be based on sizes of jobs or on the number of pages or both, -and are spanning any time period you want.</P -><P ->This is an example command how root would set a print quota in CUPS, -assuming an existing printer named "quotaprinter":</P -><PRE -CLASS="PROGRAMLISTING" -> lpadmin -p quotaprinter -o job-quota-period=604800 -o job-k-limit=1024 \ - -o job-page-limit=100</PRE -><P ->This would limit every single user to print 100 pages or 1024 KB of -data (whichever comes first) within the last 604.800 seconds ( = 1 week).</P -><P ->For CUPS to count correctly, the printfile needs to pass the CUPS "pstops" filter, -otherwise it uses a "dummy" count of "1". Some printfiles don't pass it -(eg: image files) but then those are mostly 1 page jobs anyway. This also means, -proprietary drivers for the target printer running on the client computers and -CUPS/Samba then spooling these files as "raw" (i.e. leaving them untouched, not -filtering them), will be counted as "1-pagers" too!</P -><P ->You need to send PostScript from the clients (i.e. run a PostScript driver there) -for having the chance to get accounting done. If the printer is a non-PostScript model, -you need to let CUPS do the job to convert the file to a print-ready format for the -target printer. This will be working for currently ~1.000 different printer models, see</P -><PRE -CLASS="PROGRAMLISTING" -> http://www.linuxprinting.org/printer_list.cgi</PRE -><P ->Before CUPS-1.1.16 your only option was to use the Adobe PostScript -Driver on the Windows clients. The output of this driver was not always -passed thru the "pstops" filter on the CUPS/Samba side, and therefor was -not counted correctly (the reason is that it often --- depending on the -"PPD" being used --- did write a "PJL"-header in front of the real -PostScript which made CUPS to skip the pstops and go directy to -the "pstoraster" stage).</P -><P ->From CUPS-1.1.16 onward you can use the "CUPS PostScript Driver -for Windows NT/2K/XP clients" (it is tagged in the download area of -http://www.cups.org/ as the "cups-samba-1.1.16.tar.gz" package). -It is *not* working for Win9x/ME clients. But it:</P -><P -></P -><TABLE -BORDER="0" -><TBODY -><TR -><TD ->it guarantees to not write an PJL-header</TD -></TR -><TR -><TD ->it guarantees to still read and support all PJL-options named in the driver PPD with its own means</TD -></TR -><TR -><TD ->it guarantees the file going thru the "pstops" filter on the CUPS/Samba server</TD -></TR -><TR -><TD ->it guarantees to page-count correctly the printfile</TD -></TR -></TBODY -></TABLE -><P -></P -><P ->You can read more about the setup of this combination in the -manpage for "cupsaddsmb" (only present with CUPS installed, only -current with CUPS 1.1.16).</P -><P ->These are the items CUPS logs in the "page_log" for every single *page* of a job:</P -><P -><P -></P -><TABLE -BORDER="0" -><TBODY -><TR -><TD ->Printer name</TD -></TR -><TR -><TD ->User name</TD -></TR -><TR -><TD ->Job ID</TD -></TR -><TR -><TD ->Time of printing</TD -></TR -><TR -><TD ->the page number</TD -></TR -><TR -><TD ->the number of copies</TD -></TR -><TR -><TD ->a billing info string (optional)</TD -></TR -></TBODY -></TABLE -><P -></P -></P -><P ->Here is an extract of my CUPS server's page_log file to illustrate -the format and included items:</P -><P -><SAMP -CLASS="COMPUTEROUTPUT" -> infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 1 2 #marketing - infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 2 2 #marketing - infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 3 2 #marketing - infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 4 2 #marketing - infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 5 2 #marketing - infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 6 2 #marketing</SAMP -></P -><P ->This was Job ID "40", printed on "infotec_IS2027" by user "kurt", a 6-page job -printed in 2 copies and billed to "#marketing"...</P -><P ->What flaws or shortcomings are there?</P -><P -></P -><TABLE -BORDER="0" -><TBODY -><TR -><TD ->the ones named above</TD -></TR -><TR -><TD -> CUPS really counts the job pages being *processsed in software* - (going thru the "RIP") rather than the physical sheets successfully - leaving the printing device -- if there is a jam while printing - the 5th sheet out of 1000 and the job is aborted by the printer, - the "page count" will still show the figure of 1000 for that job - </TD -></TR -><TR -><TD -> all quotas are the same for all users (no flexibility to give the - boss a higher quota than the clerk) no support for groups - </TD -></TR -><TR -><TD -> no means to read out the current balance or "used-up" number of current quota - </TD -></TR -><TR -><TD -> a user having used up 99 sheets of 100 quota will still be able to send and print a 1.000 sheet job - </TD -></TR -><TR -><TD -> a user being denied a job because of a filled-up quota doesn't get a meaningful - error message from CUPS other than "client-error-not-possible". - </TD -></TR -></TBODY -></TABLE -><P -></P -><P ->But this is the best system out there currently. And there are -huge improvements under development:</P -><P -></P -><TABLE -BORDER="0" -><TBODY -><TR -><TD ->page counting will go into the "backends" (these talk - directly to the printer and will increase the count in sync with the - actual printing process -- a jam at the 5th sheet will lead to a stop in the counting)</TD -></TR -><TR -><TD ->quotas will be handled more flexibly</TD -></TR -><TR -><TD ->probably there will be support for users to inquire their "accounts" in advance</TD -></TR -><TR -><TD ->probably there will be support for some other tools around this topic</TD -></TR -></TBODY -></TABLE -><P -></P -><P ->Other than the current stage of the CUPS development, I don't -know any other ready-to-use tool which you could consider.</P -><P ->You can download the driver files from -<A -HREF="http://www.cups.org/software.html" -TARGET="_top" ->http://www.cups.org/software.html</A ->. -It is a separate package from the CUPS base software files, tagged as "CUPS 1.1.16 -Windows NT/2k/XP Printer Driver for SAMBA (tar.gz, 192k)". The filename to -download is "cups-samba-1.1.16.tar.gz". Upon untar-/unzip-ping it will reveal -the files:</P -><P -> <SAMP -CLASS="COMPUTEROUTPUT" -> cups-samba.install - cups-samba.license - cups-samba.readme - cups-samba.remove - cups-samba.ss - </SAMP -> - </P -><P ->These have been packaged with the ESP meta packager software "EPM". The -*.install and *.remove files are simple shell script, which untars the -*.ss (which is nothing else than a tar-archive) and puts its contents -into <TT -CLASS="FILENAME" ->/usr/share/cups/drivers/</TT ->. Its contents are 3 files:</P -><P -> <SAMP -CLASS="COMPUTEROUTPUT" -> cupsdrvr.dll - cupsui.dll - cups.hlp - </SAMP -> - </P -><DIV -CLASS="CAUTION" -><P -></P -><TABLE -CLASS="CAUTION" -WIDTH="100%" -BORDER="0" -><TR -><TD -WIDTH="25" -ALIGN="CENTER" -VALIGN="TOP" -><IMG -SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/caution.gif" -HSPACE="5" -ALT="Caution"></TD -><TD -ALIGN="LEFT" -VALIGN="TOP" -><P ->Due to a bug one CUPS release puts the <TT -CLASS="FILENAME" ->cups.hlp</TT -> -into <TT -CLASS="FILENAME" ->/usr/share/drivers/</TT -> instead of -<TT -CLASS="FILENAME" ->/usr/share/cups/drivers/</TT ->. To work around this, copy/move -the file after running the "./cups-samba.install" script manually to the right place:</P -><P -> <KBD -CLASS="USERINPUT" -> cp /usr/share/drivers/cups.hlp /usr/share/cups/drivers/ - </KBD -> - </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 ->This new CUPS PostScript driver is currently binary-only, but free -no source code is provided (yet). The reason is this: it has -been developed with the help of the Microsoft Driver Developer Kit (DDK) -and compiled with Microsoft Visual Studio 6. It is not clear to the driver -developers if they are allowed to distribute the whole of the source code -as Free Software. However, they will likely release the "diff" in source -code under the GPL, so anybody with a license of Visual Studio and a DDK -will be able to compile for him/herself.</P -><P ->Once you have run the install script (and possibly manually moved the -"cups.hlp" file to "/usr/share/cups/drivers/"), the driver is ready to be -put into Samba's [print$] share (which often maps to "/etc/samba/drivers/" -and contains a subdir tree with WIN40 and W32X86 branches), by running -"cupsaddsmb" (see also "man cupsaddsmb" for CUPS 1.1.16). [Don't forget to -put root into the smbpasswd file by running "smbpasswd" should you run -this whole procedure for the first time.] Once the driver files are in the -[print$] share, they are ready to be downloaded and installed by the -Win NT/2k/XP clients.</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 -> Win 9x/ME clients won't work with this driver. For these you'd - still need to use the ADOBE*.* drivers as previously. - </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 -> It is not harming if you've still the ADOBE*.* driver files from - previous installations in the "/usr/share/cups/drivers/" directory. - The new cupsaddsmb (from 1.1.16) will automatically use the - "newest" installed driver (which here then is the CUPS drivers). - </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 -> Should your Win clients have had the old ADOBE*.* files and the - Adobe PostScript drivers installed, the download and installation - of the new CUPS PostScript driver for Windows NT/2k/XP will fail - at first. - </P -><P -> It is not enough to "delete" the printer (as the driver files - will still be kept by the clients and re-used if you try to - re-install the printer). To really get rid of the Adobe driver - files on the clients, open the "Printers" folder (possibly via - "Start --> Settings --> Control Panel --> Printers"), right-click - onto the folder background and select "Server Properties". A - new dialog opens; select the "Drivers" tab; on the list select - the driver you want to delete and click on the "Delete" button. - (This will only work if there is no single printer left which - uses that particular driver -- you need to "delete" all printers - using this driver in the "Printers" folder first.) - </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 -> Once you have successfully downloaded the CUPS PostScript driver - to a client, you can easily switch all printers to this one - by proceeding as described elsewhere in the "Samba HOWTO - Collection" to change a driver for an existing printer. - </P -></TD -></TR -></TABLE -></DIV -><P ->What are the benefits with the "CUPS PostScript driver for Windows NT/2k/XP" -as compared to the Adobe drivers?</P -><P -><P -></P -><UL -><LI -><P -> no hassle with the Adobe EULA - </P -></LI -><LI -><P -> no hassle with the question "where do I get the ADOBE*.* driver files from?" - </P -></LI -><LI -><P -> the Adobe drivers (depending on the printer PPD associated with them) - often put a PJL header in front of the core PostScript part of the print - file (thus the file starts with "<VAR -CLASS="REPLACEABLE" ->1B</VAR ->%-12345X" or "<VAR -CLASS="REPLACEABLE" ->escape</VAR ->%-12345X" - instead of "%!PS"). This leads to the CUPS daemon autotyping the - arriving file as a print-ready file, not requiring a pass thru the - "pstops" filter (to speak more technical, it is not regarded as the - generic MIME type "application/postscript", but as the more special - MIME type "application/cups.vnd-postscript"), which therefore also - leads to the page accounting in "/var/log/cups/page_log" not receiving - the exact mumber of pages; instead the dummy page number of "1" is - logged in a standard setup) - </P -></LI -><LI -><P -> the Adobe driver has more options to "mis-configure" the PostScript - generated by it (like setting it inadvertedly to "Optimize for Speed", - instead of "Optimize for Portability", which could lead to CUPS being - unable to process it) - </P -></LI -><LI -><P -> the CUPS PostScript driver output sent by Windows clients to the CUPS - server will be guaranteed to be auto-typed as generic MIME type - "application/postscript", thusly passing thru the CUPS "pstops" filter - and logging the correct number of pages in the page_log for accounting - and quota purposes - </P -></LI -><LI -><P -> the CUPS PostScript driver supports the sending of additional print - options by the Win NT/2k/XP clients, such as naming the CUPS standard - banner pages (or the custom ones, should they be installed at the time - of driver download), using the CUPS "page-label" option, setting a - job-priority and setting the scheduled time of printing (with the option - to support additional useful IPP job attributes in the future). - </P -></LI -><LI -><P -> the CUPS PostScript driver supports the inclusion of the new - "*cupsJobTicket" comments at the beginnig of the PostScript file (which - could be used in the future for all sort of beneficial extensions on - the CUPS side, but which will not disturb any other application as those - will regard it as a comment and simply ignore it). - </P -></LI -><LI -><P -> the CUPS PostScript driver will be the heart of the fully fledged CUPS - IPP client for Windows NT/2k/XP to be released soon (probably alongside - the first Beta release for CUPS 1.2). - </P -></LI -></UL -></P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN2417" ->13.11. Advanced Postscript Printing from MS Windows</A -></H2 -><P ->Let the Windows Clients use a PostScript driver to deliver poistscript to -the samba print server (just like any Linux or Unix Client would also use -PostScript to send to the server)</P -><P ->Make the Unix printing subsystem to which Samba sends the job convert the -incoming PostScript files to the native print format of the target printers -(would be PCL if you have an HP printer)</P -><P ->Now if you are afraid that this would just mean using a *Generic* PostScript -driver for the clients that has no Simplex/Duplex selection, and no paper tray -choice, but you need them to be able to set up print jobs, with all the bells -and whistles of your printers:-</P -><P -></P -><TABLE -BORDER="0" -><TBODY -><TR -><TD ->Not possible with traditional spooling systems</TD -></TR -><TR -><TD -> But perfectly supported by CUPS (which uses "PPD" files to - describe how to control the print options for PostScript and - non-PostScript devices alike... - </TD -></TR -></TBODY -></TABLE -><P -></P -><P ->CUPS PPDs are working perfectly on Windows clients who use Adobe PostScript -drivers (or the new CUPS PostScript driver for Windows NT/2K/XP). Clients can use -them to setup the job to their liking and CUPS will use the received job options -to make the (PCL-, ESC/P- or PostScript-) printer behave as required.</P -><P ->If you want to have the additional benefit of page count logging and accounting -then the CUPS PostScript driver is the best choice (better than the Adobe one).</P -><P ->If you want to make the drivers downloadable for the clients then "cupsaddsmb" is -your friend. It will setup the [print$] share on the Samba host to be ready to serve -the clients for a "point and print" driver installation.</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 ->What strings are attached?</P -></TD -></TR -></TABLE -></DIV -><P ->There are some. But, given the sheer CPU power you can buy nowadays, -these can be overcome easily. The strings:</P -><P ->Well, if the CUPS/Samba side will have to print to many printers serving many users, -you probably will need to set up a second server (which can do automatic load balancing -with the first one, plus a degree of fail-over mechanism). Converting the incoming -PostScript jobs, "interpreting" them for non-PostScript printers, amounts to the work -of a "RIP" (Raster Image Processor) done in software. This requires more CPU and RAM -than for the mere "raw spooling" task your current setup is solving. It all depends -on the avarage and peak printing load the server should be able to handle.</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN2432" ->13.12. Auto-Deletion of CUPS spool files</A -></H2 -><P ->Samba print files pass thru two "spool" directories. One the incoming directory -managed by Samba, (set eg: in the <B -CLASS="COMMAND" ->path = /var/spool/samba</B -> directive in the [printers] -section of <TT -CLASS="FILENAME" ->smb.conf</TT ->). Second is the spool directory of your UNIX print subsystem. -For CUPS it is normally "/var/spool/cups/", as set by the cupsd.conf directive -"RequestRoot /var/spool/cups".</P -><P ->I am not sure, which one of your directories keeps the files. From what you say, -it is most likely the Samba part.</P -><P ->For the CUPS part, you may want to consult:</P -><P -></P -><TABLE -BORDER="0" -><TBODY -><TR -><TD ->http://localhost:631/sam.html#PreserveJobFiles</TD -></TR -><TR -><TD ->http://localhost:631/sam.html#PreserveJobHistory</TD -></TR -><TR -><TD ->http://localhost:631/sam.html#MaxJobs</TD -></TR -></TBODY -></TABLE -><P -></P -><P ->There are the settings described for your CUPS daemon, which could lead to completed -job files not being deleted.</P -><P ->"PreserveJobHistory Yes" -- keeps some details of jobs in -cupsd's mind (well it keeps the "c12345", "c12346" etc. files -in the CUPS spool directory, which do a similar job as the -old-fashioned BSD-LPD control files). This is set to "Yes" -as a default.</P -><P ->"PreserveJobFiles Yes" -- keeps the job files themselves in -cupsd's mind (well it keeps the "d12345", "d12346" etc. files -in the CUPS spool directory...). This is set to "No" as the -CUPS default.</P -><P ->"MaxJobs 500" -- this directive controls the maximum number -of jobs that are kept in memory. Once the number of jobs -reaches the limit, the oldest completed job is automatically -purged from the system to make room for the new one. If all -of the known jobs are still pending or active then the new -job will be rejected. Setting the maximum to 0 disables this -functionality. The default setting is 0.</P -><P ->(There are also additional settings for "MaxJobsPerUser" and -"MaxJobsPerPrinter"...)</P -><P ->For everything to work as announced, you need to have three things:</P -><P -></P -><TABLE -BORDER="0" -><TBODY -><TR -><TD -> a Samba-<SPAN -CLASS="APPLICATION" ->smbd</SPAN -> which is compiled against "libcups" (Check on Linux by running <KBD -CLASS="USERINPUT" ->ldd `which smbd`</KBD ->) - </TD -></TR -><TR -><TD -> a Samba-<TT -CLASS="FILENAME" ->smb.conf</TT -> setting of <B -CLASS="COMMAND" ->printing = cups</B -> - </TD -></TR -><TR -><TD -> another Samba-<TT -CLASS="FILENAME" ->smb.conf</TT -> setting of <B -CLASS="COMMAND" ->printcap = cups</B -> - </TD -></TR -></TBODY -></TABLE -><P -></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 ->Note, that in this case all other manually set printing-related -commands (like "print command", "lpq command", "lprm command", -"lppause command" or "lpresume command") are ignored and they -should normally have no influence what-so-ever on your printing.</P -></TD -></TR -></TABLE -></DIV -><P ->If you want to do things manually, replace the "printing = cups" -by "printing = bsd". Then your manually set commands may work -(haven't tested this), and a "print command = lp -d %P %s; rm %s" -may do what you need.</P -><P ->You forgot to mention the CUPS version you're using. If you did -set things up as described in the man pages, then the Samba -spool files should be deleted. Otherwise it may be a bug. On -the CUPS side, you can control the behaviour as described -above.</P -><P ->If you have more problems, post the output of these commands:</P -><P -><KBD -CLASS="USERINPUT" -> grep -v ^# /etc/cups/cupsd.conf | grep -v ^$ - grep -v ^# /etc/samba/smb.conf | grep -v ^$ | grep -v "^;"</KBD -></P -><P ->(adapt paths as needed). These commands sanitize the files -and cut out the empty lines and lines with comments, providing -the "naked settings" in a compact way.</P -></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="AEN2506" ->14.1. Abstract</A -></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="AEN2510" ->14.2. Introduction</A -></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="AEN2523" ->14.3. What Winbind Provides</A -></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="AEN2530" ->14.3.1. Target Uses</A -></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="AEN2534" ->14.4. How Winbind Works</A -></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="AEN2539" ->14.4.1. Microsoft Remote Procedure Calls</A -></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="AEN2543" ->14.4.2. Microsoft Active Directory Services</A -></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="AEN2546" ->14.4.3. Name Service Switch</A -></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="AEN2562" ->14.4.4. Pluggable Authentication Modules</A -></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="AEN2570" ->14.4.5. User and Group ID Allocation</A -></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="AEN2574" ->14.4.6. Result Caching</A -></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="AEN2577" ->14.5. Installation and Configuration</A -></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 -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN2582" ->14.5.1. Introduction</A -></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="AEN2595" ->14.5.2. Requirements</A -></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="AEN2609" ->14.5.3. Testing Things Out</A -></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="AEN2620" ->14.5.3.1. Configure and compile SAMBA</A -></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" -><SAMP -CLASS="PROMPT" ->root#</SAMP -> <B -CLASS="COMMAND" ->autoconf</B -> -<SAMP -CLASS="PROMPT" ->root#</SAMP -> <B -CLASS="COMMAND" ->make clean</B -> -<SAMP -CLASS="PROMPT" ->root#</SAMP -> <B -CLASS="COMMAND" ->rm config.cache</B -> -<SAMP -CLASS="PROMPT" ->root#</SAMP -> <B -CLASS="COMMAND" ->./configure</B -> -<SAMP -CLASS="PROMPT" ->root#</SAMP -> <B -CLASS="COMMAND" ->make</B -> -<SAMP -CLASS="PROMPT" ->root#</SAMP -> <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="AEN2639" ->14.5.3.2. Configure <TT -CLASS="FILENAME" ->nsswitch.conf</TT -> and the -winbind libraries</A -></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 -><SAMP -CLASS="PROMPT" ->root#</SAMP -> <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 -><SAMP -CLASS="PROMPT" ->root#</SAMP -> <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 -><SAMP -CLASS="PROMPT" ->root#</SAMP -> <B -CLASS="COMMAND" ->ln -s /usr/lib/libnss_winbind.so /usr/lib/libnss_winbind.so.1</B -> -<SAMP -CLASS="PROMPT" ->root#</SAMP -> <B -CLASS="COMMAND" ->ln -s /usr/lib/libnss_winbind.so /usr/lib/nss_winbind.so.1</B -> -<SAMP -CLASS="PROMPT" ->root#</SAMP -> <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 -><SAMP -CLASS="PROMPT" ->root#</SAMP -> <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="AEN2672" ->14.5.3.3. Configure smb.conf</A -></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="AEN2688" ->14.5.3.4. Join the SAMBA server to the PDC domain</A -></H4 -><P ->Enter the following command to make the SAMBA server join the -PDC domain, where <VAR -CLASS="REPLACEABLE" ->DOMAIN</VAR -> is the name of -your Windows domain and <VAR -CLASS="REPLACEABLE" ->Administrator</VAR -> is -a domain user who has administrative privileges in the domain.</P -><P -><SAMP -CLASS="PROMPT" ->root#</SAMP -> <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 -<VAR -CLASS="REPLACEABLE" ->DOMAIN</VAR ->" where <VAR -CLASS="REPLACEABLE" ->DOMAIN</VAR -> -is your DOMAIN name.</P -></DIV -><DIV -CLASS="SECT3" -><HR><H4 -CLASS="SECT3" -><A -NAME="AEN2699" ->14.5.3.5. Start up the winbindd daemon and test it!</A -></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 -><SAMP -CLASS="PROMPT" ->root#</SAMP -> <B -CLASS="COMMAND" ->/usr/local/samba/bin/winbindd</B -></P -><P ->Winbindd can now also run in 'dual daemon mode'. This will make it -run as 2 processes. The first will answer all requests from the cache, -thus making responses to clients faster. The other will -update the cache for the query that the first has just responded. -Advantage of this is that responses stay accurate and are faster. -You can enable dual daemon mode by adding '-B' to the commandline:</P -><P -><SAMP -CLASS="PROMPT" ->root#</SAMP -> <B -CLASS="COMMAND" ->/usr/local/samba/bin/winbindd -B</B -></P -><P ->I'm always paranoid and like to make sure the daemon -is really running...</P -><P -><SAMP -CLASS="PROMPT" ->root#</SAMP -> <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 -><SAMP -CLASS="PROMPT" ->root#</SAMP -> <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 <VAR -CLASS="PARAMETER" ->winbind -separator</VAR -> is '+'.</P -><P ->You can do the same sort of thing to get group information from -the PDC:</P -><P -><PRE -CLASS="PROGRAMLISTING" -><SAMP -CLASS="PROMPT" ->root#</SAMP -> <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 -><SAMP -CLASS="PROMPT" ->root#</SAMP -> <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 -><SAMP -CLASS="PROMPT" ->root#</SAMP -> <B -CLASS="COMMAND" ->getent group</B -></P -></DIV -><DIV -CLASS="SECT3" -><HR><H4 -CLASS="SECT3" -><A -NAME="AEN2739" ->14.5.3.6. Fix the init.d startup scripts</A -></H4 -><DIV -CLASS="SECT4" -><H5 -CLASS="SECT4" -><A -NAME="AEN2741" ->14.5.3.6.1. Linux</A -></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 ->If you would like to run winbindd in dual daemon mode, replace -the line -<PRE -CLASS="PROGRAMLISTING" -> daemon /usr/local/samba/bin/winbindd</PRE -> - -in the example above with: - -<PRE -CLASS="PROGRAMLISTING" -> daemon /usr/local/samba/bin/winbindd -B</PRE ->.</P -><P ->The 'stop' function has a corresponding entry to shut down the -services and looks 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="AEN2761" ->14.5.3.6.2. Solaris</A -></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 -><P ->Again, if you would like to run samba in dual daemon mode, replace -<PRE -CLASS="PROGRAMLISTING" -> /usr/local/samba/bin/winbindd</PRE -> - -in the script above with: - -<PRE -CLASS="PROGRAMLISTING" -> /usr/local/samba/bin/winbindd -B</PRE -></P -></DIV -><DIV -CLASS="SECT4" -><HR><H5 -CLASS="SECT4" -><A -NAME="AEN2771" ->14.5.3.6.3. Restarting</A -></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="AEN2777" ->14.5.3.7. Configure Winbind and PAM</A -></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 -><SAMP -CLASS="PROMPT" ->root#</SAMP -> <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 -><SAMP -CLASS="PROMPT" ->root#</SAMP -> <B -CLASS="COMMAND" ->cp ../samba/source/nsswitch/pam_winbind.so /lib/security</B -></P -><DIV -CLASS="SECT4" -><HR><H5 -CLASS="SECT4" -><A -NAME="AEN2794" ->14.5.3.7.1. Linux/FreeBSD-specific PAM configuration</A -></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="AEN2827" ->14.5.3.7.2. Solaris-specific configuration</A -></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="AEN2834" ->14.6. Limitations</A -></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="AEN2844" ->14.7. Conclusion</A -></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="ADVANCEDNETWORKMANAGEMENT" -></A ->Chapter 15. Advanced Network Manangement</H1 -><P ->This section attempts to document peripheral issues that are of great importance to network -administrators who want to improve network resource access control, to automate the user -environment, and to make their lives a little easier.</P -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN2859" ->15.1. Configuring Samba Share Access Controls</A -></H2 -><P ->This section deals with how to configure Samba per share access control restrictions. -By default samba sets no restrictions on the share itself. Restrictions on the share itself -can be set on MS Windows NT4/200x/XP shares. This can be a very effective way to limit who can -connect to a share. In the absence of specific restrictions the default setting is to allow -the global user <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->Everyone</I -></SPAN -> Full Control (ie: Full control, Change and Read).</P -><P ->At this time Samba does NOT provide a tool for configuring access control setting on the Share -itself. Samba does have the capacity to store and act on access control settings, but the only -way to create those settings is to use either the NT4 Server Manager or the Windows 200x MMC for -Computer Management.</P -><P ->Samba stores the per share access control settings in a file called <TT -CLASS="FILENAME" ->share_info.tdb</TT ->. -The location of this file on your system will depend on how samba was compiled. The default location -for samba's tdb files is under <TT -CLASS="FILENAME" ->/usr/local/samba/var</TT ->. If the <TT -CLASS="FILENAME" ->tdbdump</TT -> -utility has been compiled and installed on your system then you can examine the contents of this file -by: <KBD -CLASS="USERINPUT" ->tdbdump share_info.tdb</KBD ->.</P -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN2869" ->15.1.1. Share Permissions Management</A -></H3 -><P ->The best tool for the task is platform dependant. Choose the best tool for your environmemt.</P -><DIV -CLASS="SECT3" -><HR><H4 -CLASS="SECT3" -><A -NAME="AEN2872" ->15.1.1.1. Windows NT4 Workstation/Server</A -></H4 -><P ->The tool you need to use to manage share permissions on a Samba server is the NT Server Manager. -Server Manager is shipped with Windows NT4 Server products but not with Windows NT4 Workstation. -You can obtain the NT Server Manager for MS Windows NT4 Workstation from Microsoft - see details below.</P -><DIV -CLASS="PROCEDURE" -><P -><B ->Instructions</B -></P -><OL -TYPE="1" -><LI -><P ->Launch the NT4 Server Manager, click on the Samba server you want to administer, then from the menu -select Computer, then click on the Shared Directories entry.</P -></LI -><LI -><P -> Now click on the share that you wish to manage, then click on the Properties tab, next click on - the Permissions tab. Now you can Add or change access control settings as you wish.</P -></LI -></OL -></DIV -></DIV -><DIV -CLASS="SECT3" -><HR><H4 -CLASS="SECT3" -><A -NAME="AEN2881" ->15.1.1.2. Windows 200x/XP</A -></H4 -><P ->On MS Windows NT4/200x/XP system access control lists on the share itself are set using native -tools, usually from filemanager. For example, in Windows 200x: right click on the shared folder, -then select 'Sharing', then click on 'Permissions'. The default Windows NT4/200x permission allows -<SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->Everyone</I -></SPAN -> Full Control on the Share.</P -><P ->MS Windows 200x and later all comes with a tool called the 'Computer Management' snap-in for the -Microsoft Management Console (MMC). This tool is located by clicking on <TT -CLASS="FILENAME" ->Control Panel -> -Administrative Tools -> Computer Management</TT ->.</P -><DIV -CLASS="PROCEDURE" -><P -><B ->Instructions</B -></P -><OL -TYPE="1" -><LI -><P -> After launching the MMC with the Computer Management snap-in, click on the menu item 'Action', - select 'Connect to another computer'. If you are not logged onto a domain you will be prompted - to enter a domain login user identifier and a password. This will authenticate you to the domain. - If you where already logged in with administrative privilidge this step is not offered.</P -></LI -><LI -><P ->If the Samba server is not shown in the Select Computer box, then type in the name of the target -Samba server in the field 'Name:'. Now click on the [+] next to 'System Tools', then on the [+] -next to 'Shared Folders' in the left panel.</P -></LI -><LI -><P ->Now in the right panel, double-click on the share you wish to set access control permissions on. -Then click on the tab 'Share Permissions'. It is now possible to add access control entities -to the shared folder. Do NOT forget to set what type of access (full control, change, read) you -wish to assign for each entry.</P -></LI -></OL -></DIV -><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 ->Be careful. If you take away all permissions from the Everyone user without removing this user -then effectively no user will be able to access the share. This is a result of what is known as -ACL precidence. ie: Everyone with NO ACCESS means that MaryK who is part of the group Everyone -will have no access even if this user is given explicit full control access.</P -></TD -></TR -></TABLE -></DIV -></DIV -></DIV -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN2897" ->15.2. Remote Server Administration</A -></H2 -><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 NT4 Server, 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 9x / Me -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 -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN2914" ->15.3. Network Logon Script Magic</A -></H2 -><P ->This section needs work. Volunteer contributions most welcome. Please send your patches or updates -to <A -HREF="mailto:jht@samba.org" -TARGET="_top" ->John Terpstra</A ->.</P -></DIV -></DIV -><DIV -CLASS="CHAPTER" -><HR><H1 -><A -NAME="POLICYMGMT" -></A ->Chapter 16. System and Account Policies</H1 -><DIV -CLASS="SECT1" -><H2 -CLASS="SECT1" -><A -NAME="AEN2929" ->16.1. Creating and Managing System Policies</A -></H2 -><P ->Under MS Windows platforms, particularly those following the release of MS Windows -NT4 and MS Windows 95) it is possible to create a type of file that would be placed -in the NETLOGON share of a domain controller. As the client logs onto the network -this file is read and the contents initiate changes to the registry of the client -machine. This file allows changes to be made to those parts of the registry that -affect users, groups of users, or machines.</P -><P ->For MS Windows 9x/Me this file must be called <TT -CLASS="FILENAME" ->Config.POL</TT -> and may -be generated using a tool called <TT -CLASS="FILENAME" ->poledit.exe</TT ->, better known as the -Policy Editor. The policy editor was provided on the Windows 98 installation CD, but -dissappeared again with the introduction of MS Windows Me (Millenium Edition). From -comments from MS Windows network administrators it would appear that this tool became -a part of the MS Windows Me Resource Kit.</P -><P ->MS Windows NT4 Server products include the <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->System Policy Editor</I -></SPAN -> -under the <TT -CLASS="FILENAME" ->Start -> Programs -> Administrative Tools</TT -> menu item. -For MS Windows NT4 and later clients this file must be called <TT -CLASS="FILENAME" ->NTConfig.POL</TT ->.</P -><P ->New with the introduction of MS Windows 2000 was the Microsoft Management Console -or MMC. This tool is the new wave in the ever changing landscape of Microsoft -methods for management of network access and security. Every new Microsoft product -or technology seems to obsolete the old rules and to introduce newer and more -complex tools and methods. To Microsoft's credit though, the MMC does appear to -be a step forward, but improved functionality comes at a great price.</P -><P ->Before embarking on the configuration of network and system policies it is highly -advisable to read the documentation available from Microsoft's web site regarding -<A -HREF="http://www.microsoft.com/ntserver/management/deployment/planguide/prof_policies.asp" -TARGET="_top" ->Implementing Profiles and Policies in Windows NT 4.0 from http://www.microsoft.com/ntserver/management/deployment/planguide/prof_policies.asp</A -> available from Microsoft. -There are a large number of documents in addition to this old one that should also -be read and understood. Try searching on the Microsoft web site for "Group Policies".</P -><P ->What follows is a very discussion with some helpful notes. The information provided -here is incomplete - you are warned.</P -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN2943" ->16.1.1. Windows 9x/Me Policies</A -></H3 -><P ->You need the Win98 Group Policy Editor to set Group Profiles up under Windows 9x/Me. -It can be found on the Original full product Win98 installation CD under -<TT -CLASS="FILENAME" ->tools/reskit/netadmin/poledit</TT ->. 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. 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 Win98 is configured to log onto -the Samba Domain, it will automatically read this file and update the Win9x/Me registry -of the machine as it logs on.</P -><P ->Further details are covered in the Win98 Resource Kit documentation.</P -><P ->If you do not take the right steps, then every so often Win9x/Me 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 Win9x/Me machine. Hence, you will -occasionally notice things changing back to the original settings.</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/Me machine that uses group policies.</P -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN2955" ->16.1.2. Windows NT4 Style Policy Files</A -></H3 -><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 NT4 Server -but <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->not NT Workstation</I -></SPAN ->. There is a Policy Editor on a NT4 -Workstation 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 NT4 -Workstation/Server, it will not work with NT clients. However, the files from -the NT Server will run happily enough on an NT4 Workstation.</P -><P ->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 the <TT -CLASS="FILENAME" ->c:\winnt\inf</TT -> -directory which is where the binary will look for them unless told otherwise. Note also that that -directory is normally '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 -><DIV -CLASS="SECT3" -><HR><H4 -CLASS="SECT3" -><A -NAME="AEN2970" ->16.1.2.1. Registry Tattoos</A -></H4 -><P -> With NT4 style registry based policy changes, a large number of settings are not - automatically reversed as the user logs off. Since the settings that were in the - NTConfig.POL file were applied to the client machine registry and that apply to the - hive key HKEY_LOCAL_MACHINE are permanent until explicitly reversed. This is known - as tattooing. It can have serious consequences down-stream and the administrator must - be extremely careful not to lock out the ability to manage the machine at a later date. - </P -></DIV -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN2973" ->16.1.3. MS Windows 200x / XP Professional Policies</A -></H3 -><P ->Windows NT4 System policies allows setting of registry parameters specific to -users, groups and computers (client workstations) that are members of the NT4 -style domain. Such policy file will work with MS Windows 2000 / XP clients also.</P -><P ->New to MS Windows 2000 Microsoft introduced a new style of group policy that confers -a superset of capabilities compared with NT4 style policies. Obviously, the tool used -to create them is different, and the mechanism for implementing them is much changed.</P -><P ->The older NT4 style registry based policies are known as <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->Administrative Templates</I -></SPAN -> -in MS Windows 2000/XP Group Policy Objects (GPOs). The later includes ability to set various security -configurations, enforce Internet Explorer browser settings, change and redirect aspects of the -users' desktop (including: the location of <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->My Documents</I -></SPAN -> files (directory), as -well as intrinsics of where menu items will appear in the Start menu). An additional new -feature is the ability to make available particular software Windows applications to particular -users and/or groups.</P -><P ->Remember: NT4 policy files are named <TT -CLASS="FILENAME" ->NTConfig.POL</TT -> and are stored in the root -of the NETLOGON share on the domain controllers. A Windows NT4 user enters a username, a password -and selects the domain name to which the logon will attempt to take place. During the logon -process the client machine reads the NTConfig.POL file from the NETLOGON share on the authenticating -server, modifies the local registry values according to the settings in this file.</P -><P ->Windows 2K GPOs are very feature rich. They are NOT stored in the NETLOGON share, rather part of -a Windows 200x policy file is stored in the Active Directory itself and the other part is stored -in a shared (and replicated) volume called the SYSVOL folder. This folder is present on all Active -Directory domain controllers. The part that is stored in the Active Directory itself is called the -group policy container (GPC), and the part that is stored in the replicated share called SYSVOL is -known as the group policy template (GPT).</P -><P ->With NT4 clients the policy file is read and executed upon only aas each user log onto the network. -MS Windows 200x policies are much more complex - GPOs are processed and applied at client machine -startup (machine specific part) and when the user logs onto the network the user specific part -is applied. In MS Windows 200x style policy management each machine and/or user may be subject -to any number of concurently applicable (and applied) policy sets (GPOs). Active Directory allows -the administrator to also set filters over the policy settings. No such equivalent capability -exists with NT4 style policy files.</P -><DIV -CLASS="SECT3" -><HR><H4 -CLASS="SECT3" -><A -NAME="AEN2984" ->16.1.3.1. Administration of Win2K / XP Policies</A -></H4 -><DIV -CLASS="PROCEDURE" -><P -><B ->Instructions</B -></P -><P ->Instead of using the tool called "The System Policy Editor", commonly called Poledit (from the -executable name poledit.exe), GPOs are created and managed using a Microsoft Management Console -(MMC) snap-in as follows:</P -><OL -TYPE="1" -><LI -><P ->Go to the Windows 200x / XP menu <TT -CLASS="FILENAME" ->Start->Programs->Administrative Tools</TT -> - and select the MMC snap-in called "Active Directory Users and Computers"</P -><P -></P -></LI -><LI -><P ->Select the domain or organizational unit (OU) that you wish to manage, then right click -to open the context menu for that object, select the properties item.</P -></LI -><LI -><P ->Now left click on the Group Policy tab, then left click on the New tab. Type a name -for the new policy you will create.</P -></LI -><LI -><P ->Now left click on the Edit tab to commence the steps needed to create the GPO.</P -></LI -></OL -></DIV -><P ->All policy configuration options are controlled through the use of policy administrative -templates. These files have a .adm extension, both in NT4 as well as in Windows 200x / XP. -Beware however, since the .adm files are NOT interchangible across NT4 and Windows 200x. -The later introduces many new features as well as extended definition capabilities. It is -well beyond the scope of this documentation to explain how to program .adm files, for that -the adminsitrator is referred to the Microsoft Windows Resource Kit for your particular -version of MS Windows.</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 ->The MS Windows 2000 Resource Kit contains a tool called gpolmig.exe. This tool can be used -to migrate an NT4 NTConfig.POL file into a Windows 200x style GPO. Be VERY careful how you -use this powerful tool. Please refer to the resource kit manuals for specific usage information.</P -></TD -></TR -></TABLE -></DIV -></DIV -></DIV -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN3002" ->16.2. Managing Account/User Policies</A -></H2 -><P ->Policies can define a specific user's settings or the settings for a group of users. The resulting -policy file contains the registry settings for all users, groups, and computers that will be using -the policy file. Separate policy files for each user, group, or computer are not not necessary.</P -><P ->If you create a policy that will be automatically downloaded from validating domain controllers, -you should name the file NTconfig.POL. As system administrator, you have the option of renaming the -policy file and, by modifying the Windows NT-based workstation, directing the computer to update -the policy from a manual path. You can do this by either manually changing the registry or by using -the System Policy Editor. This path can even be a local path such that each machine has its own policy file, -but if a change is necessary to all machines, this change must be made individually to each workstation.</P -><P ->When a Windows NT4/200x/XP machine logs onto the network the NETLOGON share on the authenticating domain -controller for the presence of the NTConfig.POL file. If one exists it is downloaded, parsed and then -applied to the user's part of the registry.</P -><P ->MS Windows 200x/XP clients that log onto an MS Windows Active Directory security domain may additionally, -acquire policy settings through Group Policy Objects (GPOs) that are defined and stored in Active Directory -itself. The key benefit of using AS GPOs is that they impose no registry <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->tatooing</I -></SPAN -> effect. -This has considerable advanage compared with the use of NTConfig.POL (NT4) style policy updates.</P -><P ->Inaddition to user access controls that may be imposed or applied via system and/or group policies -in a manner that works in conjunction with user profiles, the user management environment under -MS Windows NT4/200x/XP allows per domain as well as per user account restrictions to be applied. -Common restrictions that are frequently used includes:</P -><P -><P -></P -><TABLE -BORDER="0" -><TBODY -><TR -><TD ->Logon Hours</TD -></TR -><TR -><TD ->Password Aging</TD -></TR -><TR -><TD ->Permitted Logon from certain machines only</TD -></TR -><TR -><TD ->Account type (Local or Global)</TD -></TR -><TR -><TD ->User Rights</TD -></TR -></TBODY -></TABLE -><P -></P -></P -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN3017" ->16.2.1. With Windows NT4/200x</A -></H3 -><P ->The tools that may be used to configure these types of controls from the MS Windows environment are: -The NT4 User Manager for domains, the NT4 System and Group Policy Editor, the registry editor (regedt32.exe). -Under MS Windows 200x/XP this is done using the Microsoft Managment Console (MMC) with approapriate -"snap-ins", the registry editor, and potentially also the NT4 System and Group Policy Editor.</P -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN3020" ->16.2.2. With a Samba PDC</A -></H3 -><P ->With a Samba Domain Controller, the new tools for managing of user account and policy information includes: -<TT -CLASS="FILENAME" ->smbpasswd, pdbedit, smbgroupedit, net, rpcclient.</TT ->. The administrator should read the -man pages for these tools and become familiar with their use.</P -></DIV -></DIV -></DIV -><DIV -CLASS="CHAPTER" -><HR><H1 -><A -NAME="PROFILEMGMT" -></A ->Chapter 17. Desktop Profile Management</H1 -><DIV -CLASS="SECT1" -><H2 -CLASS="SECT1" -><A -NAME="AEN3035" ->17.1. Roaming Profiles</A -></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 -><TD -ALIGN="LEFT" -VALIGN="TOP" -><P ->Roaming profiles support is different for Win9x / Me and Windows NT4/200x.</P -></TD -></TR -></TABLE -></DIV -><P ->Before discussing how to configure roaming profiles, it is useful to see how -Windows 9x / Me and Windows NT4/200x clients implement these features.</P -><P ->Windows 9x / Me 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/Me -profiles are restricted to being stored in the user's home directory.</P -><P ->Windows NT4/200x clients send a NetSAMLogon RPC request, which contains many fields, -including a separate field for the location of the user's profiles.</P -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN3042" ->17.1.1. Samba Configuration for Profile Handling</A -></H3 -><P ->This section documents how to configure Samba for MS Windows client profile support.</P -><DIV -CLASS="SECT3" -><HR><H4 -CLASS="SECT3" -><A -NAME="AEN3045" ->17.1.1.1. NT4/200x User Profiles</A -></H4 -><P ->To support Windowns NT4/200x 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 -> - - This is typically implemented like: - -<PRE -CLASS="PROGRAMLISTING" -> logon path = \\%L\Profiles\%u</PRE -> -where %L translates to the name of the Samba server and %u translates to the user name</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. Please refer to the man page for smb.conf in respect of the different -symantics of %L and %N, as well as %U and %u.</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 ->MS Windows NT/2K clients at times do not disconnect a connection to a server -between logons. It is recommended to NOT use the <B -CLASS="COMMAND" ->homes</B -> -meta-service name as part of the profile share path.</P -></TD -></TR -></TABLE -></DIV -></DIV -><DIV -CLASS="SECT3" -><HR><H4 -CLASS="SECT3" -><A -NAME="AEN3055" ->17.1.1.2. Windows 9x / Me User Profiles</A -></H4 -><P ->To support Windows 9x / Me clients, you must use the "logon home" parameter. Samba has -now been fixed so that <KBD -CLASS="USERINPUT" ->net use /home</KBD -> now works as well, and it, too, relies -on the <B -CLASS="COMMAND" ->logon home</B ->< parameter.</P -><P ->By using the logon home parameter, you are restricted to putting Win9x / Me -profiles in the user's home directory. But wait! There is a trick you -can use. If you set the following in the <B -CLASS="COMMAND" ->[global]</B -> section of your <TT -CLASS="FILENAME" ->smb.conf</TT -> file:</P -><P -><PRE -CLASS="PROGRAMLISTING" -> logon home = \\%L\%U\.profiles</PRE -></P -><P ->then your Windows 9x / Me clients will dutifully put their clients in a subdirectory -of your home directory called <TT -CLASS="FILENAME" ->.profiles</TT -> (thus making them hidden).</P -><P ->Not only that, but <KBD -CLASS="USERINPUT" ->net use/home</KBD -> will also work, because of a feature in -Windows 9x / Me. 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 <B -CLASS="COMMAND" ->logon home</B ->.</P -></DIV -><DIV -CLASS="SECT3" -><HR><H4 -CLASS="SECT3" -><A -NAME="AEN3070" ->17.1.1.3. Mixed Windows 9x / Me and Windows NT4/200x User Profiles</A -></H4 -><P ->You can support profiles for both Win9X and WinNT clients by setting both the -<B -CLASS="COMMAND" ->logon home</B -> and <B -CLASS="COMMAND" ->logon path</B -> parameters. For example:</P -><P -><PRE -CLASS="PROGRAMLISTING" -> logon home = \\%L\%u\.profiles - logon path = \\%L\profiles\%u</PRE -></P -></DIV -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN3077" ->17.1.2. Windows Client Profile Configuration Information</A -></H3 -><DIV -CLASS="SECT3" -><H4 -CLASS="SECT3" -><A -NAME="AEN3079" ->17.1.2.1. Windows 9x / Me Profile Setup</A -></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 9x / Me 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 9x / Me 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 9x / Me 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, it would seem!</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 9x / Me 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 9x / Me 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 Windows 9x / Me 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 Windows 9x / Me 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. - - [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 - <TT -CLASS="FILENAME" ->c:\windows\profiles\username)</TT ->, 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 9x / Me 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 ethereal or netmon.exe, and -look for error messages.</P -><P ->If you have access to an Windows NT4/200x server, then first set up roaming profiles -and / or netlogons on the Windows NT4/200x server. Make a packet trace, or examine -the example packet traces provided with Windows NT4/200x server, and see what the -differences are with the equivalent samba trace.</P -></DIV -><DIV -CLASS="SECT3" -><HR><H4 -CLASS="SECT3" -><A -NAME="AEN3115" ->17.1.2.2. Windows NT4 Workstation</A -></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 -><P ->There is a parameter that is now available for use with NT Profiles: -"logon drive". This should be set to <TT -CLASS="FILENAME" ->H:</TT -> or any other drive, and -should be used in conjunction with the new "logon home" parameter.</P -><P ->The entry for the NT4 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 -for those situations where it might be created.)</P -><P ->In the profile directory, Windows NT4 creates more folders than Windows 9x / Me. -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 -><P ->The case of the profile is significant. The file must be called -NTuser.DAT or, for a mandatory profile, NTuser.MAN.</P -></DIV -><DIV -CLASS="SECT3" -><HR><H4 -CLASS="SECT3" -><A -NAME="AEN3124" ->17.1.2.3. Windows 2000/XP Professional</A -></H4 -><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 -<TT -CLASS="FILENAME" ->profiles</TT -> 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="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN3197" ->17.1.3. Sharing Profiles between W9x/Me and NT4/200x/XP workstations</A -></H3 -><P ->Sharing of desktop profiles between Windows versions is NOT recommended. -Desktop profiles are an evolving phenomenon and profiles for later versions -of MS Windows clients add features that may interfere with earlier versions -of MS Windows clients. Probably the more salient reason to NOT mix profiles -is that when logging off an earlier version of MS Windows the older format -of profile contents may overwrite information that belongs to the newer -version resulting in loss of profile information content when that user logs -on again with the newer version of MS Windows.</P -><P ->If you then want to share the same Start Menu / Desktop with W9x/Me, you will -need to specify a common location for the profiles. The smb.conf parameters -that need to be common are <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->logon path</I -></SPAN -> and -<SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->logon home</I -></SPAN ->.</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 -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN3204" ->17.1.4. Profile Migration from Windows NT4/200x Server to Samba</A -></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 -profile be stored on a samba server, or any other SMB server, as long as -that SMB server supports encrypted passwords.</P -><DIV -CLASS="SECT3" -><HR><H4 -CLASS="SECT3" -><A -NAME="AEN3207" ->17.1.4.1. Windows NT4 Profile Management Tools</A -></H4 -><P ->Unfortunately, the Resource Kit information is specific to the version of MS Windows -NT4/200x. The correct resource kit is required for each platform.</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 -><DIV -CLASS="SECT3" -><HR><H4 -CLASS="SECT3" -><A -NAME="AEN3230" ->17.1.4.2. Side bar Notes</A -></H4 -><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="SECT3" -><HR><H4 -CLASS="SECT3" -><A -NAME="AEN3234" ->17.1.4.3. moveuser.exe</A -></H4 -><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="SECT3" -><HR><H4 -CLASS="SECT3" -><A -NAME="AEN3237" ->17.1.4.4. Get SID</A -></H4 -><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 -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN3242" ->17.2. Mandatory profiles</A -></H2 -><P ->A Mandatory Profile is a profile that the user does NOT have the ability to overwrite. -During the user's session it may be possible to change the desktop environment, but -as the user logs out all changes made will be lost. If it is desired to NOT allow the -user any ability to change the desktop environment then this must be done through -policy settings. See previous chapter.</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 NO circumstances should the profile directory (or it's contents) be made read-only -as this may render the profile un-usable.</P -></TD -></TR -></TABLE -></DIV -><P ->For MS Windows NT4/200x/XP 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 -><P ->For MS Windows 9x / Me it is the User.DAT file that must be renamed to User.MAN to -affect a mandatory profile.</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN3249" ->17.3. Creating/Managing Group Profiles</A -></H2 -><P ->Most organisations are arranged into departments. There is a nice benenfit in -this fact since usually most users in a department will require the same desktop -applications and the same desktop layout. MS Windows NT4/200x/XP will allow the -use of Group Profiles. A Group Profile is a profile that is created firstly using -a template (example) user. Then using the profile migration tool (see above) the -profile is assigned access rights for the user group that needs to be given access -to the group profile.</P -><P ->The next step is rather important. PLEASE NOTE: Instead of assigning a group profile -to users (ie: Using User Manager) on a "per user" basis, the group itself is assigned -the now modified profile.</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 -> Be careful with group profiles, if the user who is a member of a group also - has a personal profile, then the result will be a fusion (merge) of the two. - </P -></TD -></TR -></TABLE -></DIV -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN3255" ->17.4. Default Profile for Windows Users</A -></H2 -><P ->MS Windows 9x / Me and NT4/200x/XP will use a default profile for any user for whom -a profile does not already exist. Armed with a knowledge of where the default profile -is located on the Windows workstation, and knowing which registry keys affect the path -from which the default profile is created, it is possible to modify the default profile -to one that has been optimised for the site. This has significant administrative -advantages.</P -><P -></P -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN3259" ->17.4.1. MS Windows 9x/Me</A -></H3 -><P ->To enable default per use profiles in Windows 9x / Me you can either use the Windows 98 System -Policy Editor or change the registry directly.</P -><P ->To enable default per user profiles in Windows 9x / Me, launch the System Policy Editor, then -select File -> Open Registry, then click on the Local Computer icon, click on Windows 98 System, -select User Profiles, click on the enable box. Do not forget to save the registry changes.</P -><P ->To modify the registry directly, launch the Registry Editor (regedit.exe), select the hive -<TT -CLASS="FILENAME" ->HKEY_LOCAL_MACHINE\Network\Logon</TT ->. Now add a DWORD type key with the name -"User Profiles", to enable user profiles set the value to 1, to disable user profiles set it to 0.</P -><DIV -CLASS="SECT3" -><HR><H4 -CLASS="SECT3" -><A -NAME="AEN3265" ->17.4.1.1. How User Profiles Are Handled in Windows 9x / Me?</A -></H4 -><P ->When a user logs on to a Windows 9x / Me machine, the local profile path, -<TT -CLASS="FILENAME" ->HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\ProfileList</TT ->, is checked -for an existing entry for that user:</P -><P ->If the user has an entry in this registry location, Windows 9x / Me checks for a locally cached -version of the user profile. Windows 9x / Me also checks the user's home directory (or other -specified directory if the location has been modified) on the server for the User Profile. -If a profile exists in both locations, the newer of the two is used. If the User Profile exists -on the server, but does not exist on the local machine, the profile on the server is downloaded -and used. If the User Profile only exists on the local machine, that copy is used.</P -><P ->If a User Profile is not found in either location, the Default User Profile from the Windows 9x / Me -machine is used and is copied to a newly created folder for the logged on user. At log off, any -changes that the user made are written to the user's local profile. If the user has a roaming -profile, the changes are written to the user's profile on the server.</P -></DIV -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN3271" ->17.4.2. MS Windows NT4 Workstation</A -></H3 -><P ->On MS Windows NT4 the default user profile is obtained from the location -<TT -CLASS="FILENAME" ->%SystemRoot%\Profiles</TT -> which in a default installation will translate to -<TT -CLASS="FILENAME" ->C:\WinNT\Profiles</TT ->. Under this directory on a clean install there will be -three (3) directories: <TT -CLASS="FILENAME" ->Administrator, All Users, Default User</TT ->.</P -><P ->The <TT -CLASS="FILENAME" ->All Users</TT -> directory contains menu settings that are common across all -system users. The <TT -CLASS="FILENAME" ->Default User</TT -> directory contains menu entries that are -customisable per user depending on the profile settings chosen/created.</P -><P ->When a new user first logs onto an MS Windows NT4 machine a new profile is created from:</P -><P -></P -><TABLE -BORDER="0" -><TBODY -><TR -><TD ->All Users settings</TD -></TR -><TR -><TD ->Default User settings (contains the default NTUser.DAT file)</TD -></TR -></TBODY -></TABLE -><P -></P -><P ->When a user logs onto an MS Windows NT4 machine that is a member of a Microsoft security domain -the following steps are followed in respect of profile handling:</P -><P -></P -><OL -TYPE="1" -><LI -><P -> The users' account information which is obtained during the logon process contains - the location of the users' desktop profile. The profile path may be local to the - machine or it may be located on a network share. If there exists a profile at the location - of the path from the user account, then this profile is copied to the location - <TT -CLASS="FILENAME" ->%SystemRoot%\Profiles\%USERNAME%</TT ->. This profile then inherits the - settings in the <TT -CLASS="FILENAME" ->All Users</TT -> profile in the <TT -CLASS="FILENAME" ->%SystemRoot%\Profiles</TT -> - location. - </P -></LI -><LI -><P -> If the user account has a profile path, but at it's location a profile does not exist, - then a new profile is created in the <TT -CLASS="FILENAME" ->%SystemRoot%\Profiles\%USERNAME%</TT -> - directory from reading the <TT -CLASS="FILENAME" ->Default User</TT -> profile. - </P -></LI -><LI -><P -> If the NETLOGON share on the authenticating server (logon server) contains a policy file - (<TT -CLASS="FILENAME" ->NTConfig.POL</TT ->) then it's contents are applied to the <TT -CLASS="FILENAME" ->NTUser.DAT</TT -> - which is applied to the <TT -CLASS="FILENAME" ->HKEY_CURRENT_USER</TT -> part of the registry. - </P -></LI -><LI -><P -> When the user logs out, if the profile is set to be a roaming profile it will be written - out to the location of the profile. The <TT -CLASS="FILENAME" ->NTuser.DAT</TT -> file is then - re-created from the contents of the <TT -CLASS="FILENAME" ->HKEY_CURRENT_USER</TT -> contents. - Thus, should there not exist in the NETLOGON share an <TT -CLASS="FILENAME" ->NTConfig.POL</TT -> at the - next logon, the effect of the provious <TT -CLASS="FILENAME" ->NTConfig.POL</TT -> will still be held - in the profile. The effect of this is known as <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->tatooing</I -></SPAN ->. - </P -></LI -></OL -><P ->MS Windows NT4 profiles may be <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->Local</I -></SPAN -> or <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->Roaming</I -></SPAN ->. A Local profile -will stored in the <TT -CLASS="FILENAME" ->%SystemRoot%\Profiles\%USERNAME%</TT -> location. A roaming profile will -also remain stored in the same way, unless the following registry key is created:</P -><P -><PRE -CLASS="PROGRAMLISTING" -> HKEY_LOCAL_MACHINE\SYSTEM\Software\Microsoft\Windows NT\CurrentVersion\winlogon\ - "DeleteRoamingCache"=dword:00000001</PRE -> - -In which case, the local copy (in <TT -CLASS="FILENAME" ->%SystemRoot%\Profiles\%USERNAME%</TT ->) will be -deleted on logout.</P -><P ->Under MS Windows NT4 default locations for common resources (like <TT -CLASS="FILENAME" ->My Documents</TT -> -may be redirected to a network share by modifying the following registry keys. These changes may be affected -via use of the System Policy Editor (to do so may require that you create your owns template extension -for the policy editor to allow this to be done through the GUI. Another way to do this is by way of first -creating a default user profile, then while logged in as that user, run regedt32 to edit the key settings.</P -><P ->The Registry Hive key that affects the behaviour of folders that are part of the default user profile -are controlled by entries on Windows NT4 is:</P -><P -><PRE -CLASS="PROGRAMLISTING" -> HKEY_CURRENT_USER - \Software - \Microsoft - \Windows - \CurrentVersion - \Explorer - \User Shell Folders\</PRE -></P -><P ->The above hive key contains a list of automatically managed folders. The default entries are:</P -><P -> <PRE -CLASS="PROGRAMLISTING" -> Name Default Value - -------------- ----------------------------------------- - AppData %USERPROFILE%\Application Data - Desktop %USERPROFILE%\Desktop - Favorites %USERPROFILE%\Favorites - NetHood %USERPROFILE%\NetHood - PrintHood %USERPROFILE%\PrintHood - Programs %USERPROFILE%\Start Menu\Programs - Recent %USERPROFILE%\Recent - SendTo %USERPROFILE%\SendTo - Start Menu %USERPROFILE%\Start Menu - Startup %USERPROFILE%\Start Menu\Programs\Startup - </PRE -> - </P -><P ->The registry key that contains the location of the default profile settings is: - -<PRE -CLASS="PROGRAMLISTING" -> HKEY_LOCAL_MACHINE - \SOFTWARE - \Microsoft - \Windows - \CurrentVersion - \Explorer - \User Shell Folders</PRE -> - -The default entries are: - -<PRE -CLASS="PROGRAMLISTING" -> Common Desktop %SystemRoot%\Profiles\All Users\Desktop - Common Programs %SystemRoot%\Profiles\All Users\Programs - Common Start Menu %SystemRoot%\Profiles\All Users\Start Menu - Common Startu p %SystemRoot%\Profiles\All Users\Start Menu\Progams\Startup</PRE -></P -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN3325" ->17.4.3. MS Windows 200x/XP</A -></H3 -><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 -> MS Windows XP Home Edition does use default per user profiles, but can not participate - in domain security, can not log onto an NT/ADS style domain, and thus can obtain the profile - only from itself. While there are benefits in doing this the beauty of those MS Windows - clients that CAN participate in domain logon processes allows the administrator to create - a global default profile and to enforce it through the use of Group Policy Objects (GPOs). - </P -></TD -></TR -></TABLE -></DIV -><P ->When a new user first logs onto MS Windows 200x/XP machine the default profile is obtained from -<TT -CLASS="FILENAME" ->C:\Documents and Settings\Default User</TT ->. The administrator can modify (or change -the contents of this location and MS Windows 200x/XP will gladly user it. This is far from the optimum -arrangement since it will involve copying a new default profile to every MS Windows 200x/XP client -workstation. </P -><P ->When MS Windows 200x/XP participate in a domain security context, and if the default user -profile is not found, then the client will search for a default profile in the NETLOGON share -of the authenticating server. ie: In MS Windows parlance: -<TT -CLASS="FILENAME" ->%LOGONSERVER%\NETLOGON\Default User</TT -> and if one exits there it will copy this -to the workstation to the <TT -CLASS="FILENAME" ->C:\Documents and Settings\</TT -> under the Windows -login name of the user.</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 -> This path translates, in Samba parlance, to the smb.conf [NETLOGON] share. The directory - should be created at the root of this share and msut be called <TT -CLASS="FILENAME" ->Default Profile</TT ->. - </P -></TD -></TR -></TABLE -></DIV -><P ->If a default profile does not exist in this location then MS Windows 200x/XP will use the local -default profile.</P -><P ->On loging out, the users' desktop profile will be stored to the location specified in the registry -settings that pertain to the user. If no specific policies have been created, or passed to the client -during the login process (as Samba does automatically), then the user's profile will be written to -the local machine only under the path <TT -CLASS="FILENAME" ->C:\Documents and Settings\%USERNAME%</TT ->.</P -><P ->Those wishing to modify the default behaviour can do so through up to three methods:</P -><P -></P -><UL -><LI -><P -> Modify the registry keys on the local machine manually and place the new default profile in the - NETLOGON share root - NOT recommended as it is maintenance intensive. - </P -></LI -><LI -><P -> Create an NT4 style NTConfig.POL file that specified this behaviour and locate this file - in the root of the NETLOGON share along with the new default profile. - </P -></LI -><LI -><P -> Create a GPO that enforces this through Active Directory, and place the new default profile - in the NETLOGON share. - </P -></LI -></UL -><P ->The Registry Hive key that affects the behaviour of folders that are part of the default user profile -are controlled by entries on Windows 200x/XP is:</P -><P -><PRE -CLASS="PROGRAMLISTING" -> HKEY_CURRENT_USER - \Software - \Microsoft - \Windows - \CurrentVersion - \Explorer - \User Shell Folders\</PRE -></P -><P ->The above hive key contains a list of automatically managed folders. The default entries are:</P -><P -> <PRE -CLASS="PROGRAMLISTING" -> Name Default Value - -------------- ----------------------------------------- - AppData %USERPROFILE%\Application Data - Cache %USERPROFILE%\Local Settings\Temporary Internet Files - Cookies %USERPROFILE%\Cookies - Desktop %USERPROFILE%\Desktop - Favorites %USERPROFILE%\Favorites - History %USERPROFILE%\Local Settings\History - Local AppData %USERPROFILE%\Local Settings\Application Data - Local Settings %USERPROFILE%\Local Settings - My Pictures %USERPROFILE%\My Documents\My Pictures - NetHood %USERPROFILE%\NetHood - Personal %USERPROFILE%\My Documents - PrintHood %USERPROFILE%\PrintHood - Programs %USERPROFILE%\Start Menu\Programs - Recent %USERPROFILE%\Recent - SendTo %USERPROFILE%\SendTo - Start Menu %USERPROFILE%\Start Menu - Startup %USERPROFILE%\Start Menu\Programs\Startup - Templates %USERPROFILE%\Templates - </PRE -> - </P -><P ->There is also an entry called "Default" that has no value set. The default entry is of type REG_SZ, all -the others are of type REG_EXPAND_SZ.</P -><P ->It makes a huge difference to the speed of handling roaming user profiles if all the folders are -stored on a dedicated location on a network server. This means that it will NOT be necessary to -write Outlook PST file over the network for every login and logout.</P -><P ->To set this to a network location you could use the following examples: - -<PRE -CLASS="PROGRAMLISTING" -> %LOGONSERVER%\%USERNAME%\Default Folders</PRE -> - -This would store the folders in the user's home directory under a directory called "Default Folders" - -You could also use: - -<PRE -CLASS="PROGRAMLISTING" -> \\SambaServer\FolderShare\%USERNAME%</PRE -> - -in which case the default folders will be stored in the server named <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->SambaServer</I -></SPAN -> -in the share called <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->FolderShare</I -></SPAN -> under a directory that has the name of the MS Windows -user as seen by the Linux/Unix file system.</P -><P ->Please note that once you have created a default profile share, you MUST migrate a user's profile -(default or custom) to it.</P -><P ->MS Windows 200x/XP profiles may be <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->Local</I -></SPAN -> or <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->Roaming</I -></SPAN ->. -A roaming profile will be cached locally unless the following registry key is created:</P -><P -><PRE -CLASS="PROGRAMLISTING" -> HKEY_LOCAL_MACHINE\SYSTEM\Software\Microsoft\Windows NT\CurrentVersion\winlogon\ - "DeleteRoamingCache"=dword:00000001</PRE -> - -In which case, the local cache copy will be deleted on logout.</P -></DIV -></DIV -></DIV -><DIV -CLASS="CHAPTER" -><HR><H1 -><A -NAME="INTERDOMAINTRUSTS" -></A ->Chapter 18. Interdomain Trust Relationships</H1 -><P ->Samba-3 supports NT4 style domain trust relationships. This is feature that many sites -will want to use if they migrate to Samba-3 from and NT4 style domain and do NOT want to -adopt Active Directory or an LDAP based authentication back end. This section explains -some background information regarding trust relationships and how to create them. It is now -possible for Samba3 to NT4 trust (and vica versa), as well as Samba3 to Samba3 trusts.</P -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN3386" ->18.1. Trust Relationship Background</A -></H2 -><P ->MS Windows NT3.x/4.0 type security domains employ a non-hierchical security structure. -The limitations of this architecture as it affects the scalability of MS Windows networking -in large organisations is well known. Additionally, the flat-name space that results from -this design significantly impacts the delegation of administrative responsibilities in -large and diverse organisations.</P -><P ->Microsoft developed Active Directory Service (ADS), based on Kerberos and LDAP, as a means -of circumventing the limitations of the older technologies. Not every organisation is ready -or willing to embrace ADS. For small companies the older NT4 style domain security paradigm -is quite adequate, there thus remains an entrenched user base for whom there is no direct -desire to go through a disruptive change to adopt ADS.</P -><P ->Microsoft introduced with MS Windows NT the ability to allow differing security domains -to affect a mechanism so that users from one domain may be given access rights and privilidges -in another domain. The language that describes this capability is couched in terms of -<SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->Trusts</I -></SPAN ->. Specifically, one domain will <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->trust</I -></SPAN -> the users -from another domain. The domain from which users are available to another security domain is -said to be a trusted domain. The domain in which those users have assigned rights and privilidges -is the trusting domain. With NT3.x/4.0 all trust relationships are always in one direction only, -thus if users in both domains are to have privilidges and rights in each others' domain, then it is -necessary to establish two (2) relationships, one in each direction.</P -><P ->In an NT4 style MS security domain, all trusts are non-transitive. This means that if there -are three (3) domains (let's call them RED, WHITE, and BLUE) where RED and WHITE have a trust -relationship, and WHITE and BLUE have a trust relationship, then it holds that there is no -implied trust between the RED and BLUE domains. ie: Relationships are explicit and not -transitive.</P -><P ->New to MS Windows 2000 ADS security contexts is the fact that trust relationships are two-way -by default. Also, all inter-ADS domain trusts are transitive. In the case of the RED, WHITE and BLUE -domains above, with Windows 2000 and ADS the RED and BLUE domains CAN trust each other. This is -an inherent feature of ADS domains.</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN3395" ->18.2. MS Windows NT4 Trust Configuration</A -></H2 -><P ->There are two steps to creating an inter-domain trust relationship. </P -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN3398" ->18.2.1. NT4 as the Trusting Domain</A -></H3 -><P ->For MS Windows NT4, all domain trust relationships are configured using the Domain User Manager. -To affect a two way trust relationship it is necessary for each domain administrator to make -available (for use by an external domain) it's security resources. This is done from the Domain -User Manager Policies entry on the menu bar. From the Policy menu, select Trust Relationships, then -next to the lower box that is labelled "Permitted to Trust this Domain" are two buttons, "Add" and -"Remove". The "Add" button will open a panel in which needs to be entered the remote domain that -will be able to assign user rights to your domain. In addition it is necessary to enter a password -that is specific to this trust relationship. The password is added twice.</P -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN3401" ->18.2.2. NT4 as the Trusted Domain</A -></H3 -><P ->A trust relationship will work only when the other (trusting) domain makes the appropriate connections -with the trusted domain. To consumate the trust relationship the administrator will launch the -Domain User Manager, from the menu select Policies, then select Trust Relationships, then click on the -"Add" button that is next to the box that is labelled "Trusted Domains". A panel will open in -which must be entered the name of the remote domain as well as the password assigned to that trust.</P -><P -></P -></DIV -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN3405" ->18.3. Configuring Samba Domain Trusts</A -></H2 -><P ->This descitpion is meant to be a fairly short introduction about how to set up a Samba server so -that it could participate in interdomain trust relationships. Trust relationship support in Samba -is in its early stage, so lot of things don't work yet. Paricularly, the contents of this document -applies to NT4-style trusts.</P -><P ->Each of the procedures described below is treated as they were performed with Windows NT4 Server on -one end. The other end could just as well be another Samba3 domain. It can be clearly seen, after -reading this document, that combining Samba-specific parts of what's written below leads to trust -between domains in purely Samba environment.</P -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN3409" ->18.3.1. Samba3 as the Trusting Domain</A -></H3 -><P ->In order to set Samba PDC to be trusted party of the relationship first you need -to create special account for domain that will be the trusting party. To do that, -you can use 'smbpasswd' utility. Creating the trusted domain account is very -similiar to creating the connection to the trusting machine's account. Suppose, -your domain is called SAMBA, and the remote domain is called RUMBA. Your first -step will be to issue this command from your favourite shell:</P -><P -><PRE -CLASS="PROGRAMLISTING" -> deity# smbpasswd -a -i rumba - New SMB password: XXXXXXXX - Retype SMB password: XXXXXXXX - Added user rumba$ - - where: - -a means to add a new account into the passdb database - -i means create this account with the Inter-Domain trust flag - - The account name will be 'rumba$' (the name ofthe remote domain)</PRE -></P -><P ->fter issuing this command you'll be asked for typing account's -password. You can use any password you want, but be aware that Windows NT will -not change this password until 7 days have passed since account creating. -After command returns successfully, you can look at your new account's entry -(in the way depending on your configuration) and see that account's name is -really RUMBA$ and it has 'I' flag in the flags field. Now you're ready to confirm -the trust by establishing it from Windows NT Server.</P -><P ->Open 'User Manager for Domains' and from menu 'Policies' select 'Trust Relationships...'. -Right beside 'Trusted domains' list press 'Add...' button. You'll be prompted for -trusted domain name and the relationship's password. Type in SAMBA, as this is -your domain name and the password you've just used during account creation. -Press OK and if everything went fine, you will see 'Trusted domain relationship -successfully established' message. Well done.</P -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN3416" ->18.3.2. Samba3 as the Trusted Domain</A -></H3 -><P ->This time activities are somewhat reversed. Again, we'll assume that your domain -controlled by Samba PDC is called SAMBA and NT-controlled domain is called RUMBA.</P -><P ->The very first thing is to add account for SAMBA domain on RUMBA's PDC.</P -><P ->Launch the Domain User Manager, then from the menu select 'Policies', 'Trust Relationships'. -Now, next to 'Trusted Domains' box press the 'Add' button, and type in the name of the trusted -domein (SAMBA) and password securing the relationship.</P -><P ->Password can be arbitrarily chosen the more, because it's easy to change it -from Samba server whenever you want. After confirming password your account is -ready and waiting. Now it's Samba's turn.</P -><P ->Using your favourite shell while being logged on as root, issue this command:</P -><P -><PRE -CLASS="PROGRAMLISTING" -> deity# net rpc trustdom establish rumba</PRE -></P -><P ->You'll be prompted for password you've just typed on your Windows NT4 Server box. -Don't worry if you will see the error message with returned code of -<TT -CLASS="FILENAME" ->NT_STATUS_NOLOGON_INTERDOMAIN_TRUST_ACCOUNT</TT ->. It means the -password you gave is correct and the NT4 Server says the account is ready for trusting your domain -and not for ordinary connection. After that, be patient it can take a while (especially -in large networks), you should see 'Success' message. Contgratulations! Your trust -relationship has just been established.</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 ->Note that you have to run this command as root, since you need write access to -your secrets.tdb file.</P -></TD -></TR -></TABLE -></DIV -></DIV -></DIV -></DIV -><DIV -CLASS="CHAPTER" -><HR><H1 -><A -NAME="PAM" -></A ->Chapter 19. PAM Configuration for Centrally Managed Authentication</H1 -><DIV -CLASS="SECT1" -><H2 -CLASS="SECT1" -><A -NAME="AEN3440" ->19.1. Samba and PAM</A -></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 -><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 -> If the PAM authentication module (loadable link library file) is located in the - default location then it is not necessary to specify the path. In the case of - Linux, the default location is <TT -CLASS="FILENAME" ->/lib/security</TT ->. If the module - is located other than default then the path may be specified as: - - <PRE -CLASS="PROGRAMLISTING" -> auth required /other_path/pam_strange_module.so - </PRE -> - </P -></TD -></TR -></TABLE -></DIV -><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 -><SAMP -CLASS="PROMPT" ->$</SAMP -><KBD -CLASS="USERINPUT" ->/bin/ls /lib/security</KBD -> -<PRE -CLASS="PROGRAMLISTING" -> 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 pam_pwdb.so nullok nodelay shadow audit - account required pam_pwdb.so audit nodelay - session required pam_pwdb.so nodelay - password required 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 pam_smbpass.so nodelay - account required pam_pwdb.so audit nodelay - session required pam_pwdb.so nodelay - password required pam_smbpass.so nodelay smbconf=/etc/samba.d/smb.conf</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 ->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 -></TD -></TR -></TABLE -></DIV -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN3491" ->19.2. Distributed Authentication</A -></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 a distributed -passdb backend, such as ldap, 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="AEN3496" ->19.3. PAM Configuration in smb.conf</A -></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 is configured to enable PAM support (i.e. -<CODE -CLASS="CONSTANT" ->--with-pam</CODE ->), 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="VFS" -></A ->Chapter 20. Stackable VFS modules</H1 -><DIV -CLASS="SECT1" -><H2 -CLASS="SECT1" -><A -NAME="AEN3531" ->20.1. Introduction and configuration</A -></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="AEN3540" ->20.2. Included modules</A -></H2 -><DIV -CLASS="SECT2" -><H3 -CLASS="SECT2" -><A -NAME="AEN3542" ->20.2.1. audit</A -></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="AEN3550" ->20.2.2. extd_audit</A -></H3 -><P ->This module is identical with the <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->audit</I -></SPAN -> module above except -that it sends audit logs to both syslog as well as the smbd log file/s. The -loglevel for this module is set in the smb.conf file. At loglevel = 0, only file -and directory deletions and directory and file creations are logged. At loglevel = 1 -file opens are renames and permission changes are logged , while at loglevel = 2 file -open and close calls are logged also.</P -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN3554" ->20.2.3. recycle</A -></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="AEN3591" ->20.2.4. netatalk</A -></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="AEN3598" ->20.3. VFS modules available elsewhere</A -></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="AEN3602" ->20.3.1. DatabaseFS</A -></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="AEN3610" ->20.3.2. vscan</A -></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="MSDFS" -></A ->Chapter 21. Hosting a Microsoft Distributed File System tree on Samba</H1 -><DIV -CLASS="SECT1" -><H2 -CLASS="SECT1" -><A -NAME="AEN3626" ->21.1. Instructions</A -></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 - <VAR -CLASS="PARAMETER" ->--with-msdfs</VAR -> 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" -><VAR -CLASS="PARAMETER" -> host msdfs</VAR -></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" -><VAR -CLASS="PARAMETER" -> msdfs root</VAR -></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 -><SAMP -CLASS="PROMPT" ->root# </SAMP -><KBD -CLASS="USERINPUT" ->cd /export/dfsroot</KBD -></P -><P -><SAMP -CLASS="PROMPT" ->root# </SAMP -><KBD -CLASS="USERINPUT" ->chown root /export/dfsroot</KBD -></P -><P -><SAMP -CLASS="PROMPT" ->root# </SAMP -><KBD -CLASS="USERINPUT" ->chmod 755 /export/dfsroot</KBD -></P -><P -><SAMP -CLASS="PROMPT" ->root# </SAMP -><KBD -CLASS="USERINPUT" ->ln -s msdfs:storageA\\shareA linka</KBD -></P -><P -><SAMP -CLASS="PROMPT" ->root# </SAMP -><KBD -CLASS="USERINPUT" ->ln -s msdfs:serverB\\share,serverC\\share linkb</KBD -></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="AEN3661" ->21.1.1. Notes</A -></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="INTEGRATE-MS-NETWORKS" -></A ->Chapter 22. Integrating MS Windows networks with Samba</H1 -><P ->This section deals with NetBIOS over TCP/IP name to IP address resolution. If you -your MS Windows clients are NOT configured to use NetBIOS over TCP/IP then this -section does not apply to your installation. If your installation involves use of -NetBIOS over TCP/IP then this section may help you to resolve networking problems.</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 -> NetBIOS over TCP/IP has nothing to do with NetBEUI. NetBEUI is NetBIOS - over Logical Link Control (LLC). On modern networks it is highly advised - to NOT run NetBEUI at all. Note also that there is NO such thing as - NetBEUI over TCP/IP - the existence of such a protocol is a complete - and utter mis-apprehension.</P -></TD -></TR -></TABLE -></DIV -><P ->Since the introduction of MS Windows 2000 it is possible to run MS Windows networking -without the use of NetBIOS over TCP/IP. NetBIOS over TCP/IP uses UDP port 137 for NetBIOS -name resolution and uses TCP port 139 for NetBIOS session services. When NetBIOS over -TCP/IP is disabled on MS Windows 2000 and later clients then only TCP port 445 will be -used and UDP port 137 and TCP port 139 will not.</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 ->When using Windows 2000 or later clients, if NetBIOS over TCP/IP is NOT disabled, then -the client will use UDP port 137 (NetBIOS Name Service, also known as the Windows Internet -Name Service or WINS), TCP port 139 AND TCP port 445 (for actual file and print traffic).</P -></TD -></TR -></TABLE -></DIV -><P ->When NetBIOS over TCP/IP is disabled the use of DNS is essential. Most installations that -disable NetBIOS over TCP/IP today use MS Active Directory Service (ADS). ADS requires -Dynamic DNS with Service Resource Records (SRV RR) and with Incremental Zone Transfers (IXFR). -Use of DHCP with ADS is recommended as a further means of maintaining central control -over client workstation network configuration.</P -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN3688" ->22.1. Name Resolution in a pure Unix/Linux world</A -></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="AEN3704" ->22.1.1. <TT -CLASS="FILENAME" ->/etc/hosts</TT -></A -></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="AEN3720" ->22.1.2. <TT -CLASS="FILENAME" ->/etc/resolv.conf</TT -></A -></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="AEN3731" ->22.1.3. <TT -CLASS="FILENAME" ->/etc/host.conf</TT -></A -></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="AEN3739" ->22.1.4. <TT -CLASS="FILENAME" ->/etc/nsswitch.conf</TT -></A -></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="AEN3751" ->22.2. Name resolution as used within MS Windows networking</A -></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="AEN3763" ->22.2.1. The NetBIOS Name Cache</A -></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="AEN3768" ->22.2.2. The LMHOSTS file</A -></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="AEN3776" ->22.2.3. HOSTS file</A -></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="AEN3781" ->22.2.4. DNS Lookup</A -></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="AEN3784" ->22.2.5. WINS Lookup</A -></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 <TT -CLASS="FILENAME" ->smb.conf</TT -> file:</P -><P -><PRE -CLASS="PROGRAMLISTING" -> wins support = No - wins server = xxx.xxx.xxx.xxx</PRE -></P -><P ->where <VAR -CLASS="REPLACEABLE" ->xxx.xxx.xxx.xxx</VAR -> is the IP address -of the WINS server.</P -></DIV -></DIV -></DIV -><DIV -CLASS="CHAPTER" -><HR><H1 -><A -NAME="IMPROVED-BROWSING" -></A ->Chapter 23. Improved browsing in samba</H1 -><DIV -CLASS="SECT1" -><H2 -CLASS="SECT1" -><A -NAME="AEN3804" ->23.1. Overview of browsing</A -></H2 -><P ->SMB networking provides a mechanism by which clients can access a list -of machines in a network, a so-called <B -CLASS="COMMAND" ->browse list</B ->. 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 ->MS Windows 2000 and later, as with Samba 3 and later, can be -configured to not use NetBIOS over TCP/IP. When configured this way -it is imperative that name resolution (using DNS/LDAP/ADS) be correctly -configured and operative. Browsing will NOT work if name resolution -from SMB machine names to IP addresses does not function correctly.</P -><P ->Where NetBIOS over TCP/IP is enabled 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="AEN3810" ->23.2. Browsing support in samba</A -></H2 -><P ->Samba facilitates browsing. The browsing is supported by <SPAN -CLASS="APPLICATION" ->nmbd</SPAN -> -and is also controlled by options in the <TT -CLASS="FILENAME" ->smb.conf</TT -> file. -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.</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 -><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 ->Nmbd can be configured as a WINS server, but it is not -necessary to specifically use samba as your WINS server. MS Windows -NT4, Server or Advanced Server 2000 or 2003 can be configured as -your WINS server. In a mixed NT/2000/2003 server and samba environment on -a Wide Area Network, it is recommended that you use the Microsoft -WINS server capabilities. In a samba-only environment, it is -recommended that you use one and only one Samba server as your WINS server.</P -></TD -></TR -></TABLE -></DIV -><P ->To get browsing to work you need to run nmbd as usual, but will need -to use the <B -CLASS="COMMAND" ->workgroup</B -> option in <TT -CLASS="FILENAME" ->smb.conf</TT -> -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 <B -CLASS="COMMAND" ->remote announce</B -> in the -<TT -CLASS="FILENAME" ->smb.conf</TT -> man page. </P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN3825" ->23.3. Problem resolution</A -></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 <TT -CLASS="FILENAME" ->browse.dat</TT ->.</P -><P ->Note that if it doesn't work for you, then you should still be able to -type the server name as <TT -CLASS="FILENAME" ->\\SERVER</TT -> 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 -<B -CLASS="COMMAND" ->guest account</B -> 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 -><SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->MS Windows 2000 and upwards (as with Samba) can be configured to disallow -anonymous (ie: Guest account) access to the IPC$ share. In that case, the -MS Windows 2000/XP/2003 machine acting as an SMB/CIFS client will use the -name of the currently logged in user to query the IPC$ share. MS Windows -9X clients are not able to do this and thus will NOT be able to browse -server resources.</I -></SPAN -></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 <TT -CLASS="FILENAME" ->smb.conf</TT ->)</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN3837" ->23.4. Browsing across subnets</A -></H2 -><P ->Since the release of Samba 1.9.17(alpha1) 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 <TT -CLASS="FILENAME" ->smb.conf</TT -> file.</P -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN3843" ->23.4.1. How does cross subnet browsing work ?</A -></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. -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="AEN3878" ->23.5. Setting up a WINS server</A -></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 <TT -CLASS="FILENAME" ->smb.conf</TT -> 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 prior 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 a recent version, 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 -<B -CLASS="COMMAND" ->wins support = yes</B -> 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 <TT -CLASS="FILENAME" ->smb.conf</TT -> 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 <TT -CLASS="FILENAME" ->smb.conf</TT -> 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="AEN3901" ->23.6. Setting up Browsing in a WORKGROUP</A -></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 <TT -CLASS="FILENAME" ->smb.conf</TT -> 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 <TT -CLASS="FILENAME" ->smb.conf</TT -> 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 MS Windows NT/2K/XP/2003 machine should be -able to do this, as will Windows 9x 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 -<TT -CLASS="FILENAME" ->smb.conf</TT -> 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 <B -CLASS="COMMAND" ->local master</B -> parameter allows Samba to act as a -local master browser. The <B -CLASS="COMMAND" ->preferred master</B -> causes nmbd -to force a browser election on startup and the <B -CLASS="COMMAND" ->os level</B -> -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 <B -CLASS="COMMAND" ->[global]</B -> section of the -<TT -CLASS="FILENAME" ->smb.conf</TT -> 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="AEN3927" ->23.7. Setting up Browsing in a DOMAIN</A -></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 (<VAR -CLASS="REPLACEABLE" ->DOMAIN</VAR -><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 <B -CLASS="COMMAND" ->[global]</B -> section -of the <TT -CLASS="FILENAME" ->smb.conf</TT -> 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 <B -CLASS="COMMAND" ->os level</B -> 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 <A -HREF="#BROWSE-FORCE-MASTER" ->Forcing samba to be the master browser</A -> -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 <B -CLASS="COMMAND" ->[global]</B -> section of the <TT -CLASS="FILENAME" ->smb.conf</TT -> -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="BROWSE-FORCE-MASTER" ->23.8. Forcing samba to be the master</A -></H2 -><P ->Who becomes the <B -CLASS="COMMAND" ->master browser</B -> 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 <B -CLASS="COMMAND" ->os level</B -> global -option in <TT -CLASS="FILENAME" ->smb.conf</TT -> 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 <B -CLASS="COMMAND" ->os level</B -> of 2 would make it beat WfWg and Win95, but not MS Windows -NT/2K Server. A MS Windows NT/2K Server 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 -<B -CLASS="COMMAND" ->preferred master</B -> global option in <TT -CLASS="FILENAME" ->smb.conf</TT -> 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 <B -CLASS="COMMAND" ->preferred master</B -> 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 <B -CLASS="COMMAND" ->domain master browser</B ->, then it is -recommended that you also set <B -CLASS="COMMAND" ->preferred master</B -> 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="AEN3962" ->23.9. Making samba the domain master</A -></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 <B -CLASS="COMMAND" ->domain master = yes</B -> -in <TT -CLASS="FILENAME" ->smb.conf</TT ->. 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 <B -CLASS="COMMAND" ->os level</B -> high enough to make sure it wins elections, and set -<B -CLASS="COMMAND" ->preferred master</B -> 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="AEN3984" ->23.10. Note about broadcast addresses</A -></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="AEN3987" ->23.11. Multiple interfaces</A -></H2 -><P ->Samba now supports machines with multiple network interfaces. If you -have multiple interfaces then you will need to use the <B -CLASS="COMMAND" ->interfaces</B -> -option in <TT -CLASS="FILENAME" ->smb.conf</TT -> to configure them. </P -></DIV -></DIV -><DIV -CLASS="CHAPTER" -><HR><H1 -><A -NAME="SECURING-SAMBA" -></A ->Chapter 24. Securing Samba</H1 -><DIV -CLASS="SECT1" -><H2 -CLASS="SECT1" -><A -NAME="AEN4003" ->24.1. Introduction</A -></H2 -><P ->This note was attached to the Samba 2.2.8 release notes as it contained an -important security fix. The information contained here applies to Samba -installations in general.</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN4006" ->24.2. Using host based protection</A -></H2 -><P ->In many installations of Samba the greatest threat comes for outside -your immediate network. By default Samba will accept connections from -any host, which means that if you run an insecure version of Samba on -a host that is directly connected to the Internet you can be -especially vulnerable.</P -><P ->One of the simplest fixes in this case is to use the <B -CLASS="COMMAND" ->hosts allow</B -> and -<B -CLASS="COMMAND" ->hosts deny</B -> options in the Samba <TT -CLASS="FILENAME" ->smb.conf</TT -> configuration file to only -allow access to your server from a specific range of hosts. An example -might be:</P -><P -><PRE -CLASS="PROGRAMLISTING" -> hosts allow = 127.0.0.1 192.168.2.0/24 192.168.3.0/24 - hosts deny = 0.0.0.0/0</PRE -></P -><P ->The above will only allow SMB connections from 'localhost' (your own -computer) and from the two private networks 192.168.2 and -192.168.3. All other connections will be refused connections as soon -as the client sends its first packet. The refusal will be marked as a -'not listening on called name' error.</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN4016" ->24.3. Using interface protection</A -></H2 -><P ->By default Samba will accept connections on any network interface that -it finds on your system. That means if you have a ISDN line or a PPP -connection to the Internet then Samba will accept connections on those -links. This may not be what you want.</P -><P ->You can change this behaviour using options like the following:</P -><P -><PRE -CLASS="PROGRAMLISTING" -> interfaces = eth* lo - bind interfaces only = yes</PRE -></P -><P -></P -><P ->This tells Samba to only listen for connections on interfaces with a -name starting with 'eth' such as eth0, eth1, plus on the loopback -interface called 'lo'. The name you will need to use depends on what -OS you are using, in the above I used the common name for Ethernet -adapters on Linux.</P -><P ->If you use the above and someone tries to make a SMB connection to -your host over a PPP interface called 'ppp0' then they will get a TCP -connection refused reply. In that case no Samba code is run at all as -the operating system has been told not to pass connections from that -interface to any process.</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN4025" ->24.4. Using a firewall</A -></H2 -><P ->Many people use a firewall to deny access to services that they don't -want exposed outside their network. This can be a very good idea, -although I would recommend using it in conjunction with the above -methods so that you are protected even if your firewall is not active -for some reason.</P -><P ->If you are setting up a firewall then you need to know what TCP and -UDP ports to allow and block. Samba uses the following:</P -><P -><PRE -CLASS="PROGRAMLISTING" ->UDP/137 - used by nmbd -UDP/138 - used by nmbd -TCP/139 - used by smbd -TCP/445 - used by smbd</PRE -></P -><P ->The last one is important as many older firewall setups may not be -aware of it, given that this port was only added to the protocol in -recent years. </P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN4032" ->24.5. Using a IPC$ share deny</A -></H2 -><P ->If the above methods are not suitable, then you could also place a -more specific deny on the IPC$ share that is used in the recently -discovered security hole. This allows you to offer access to other -shares while denying access to IPC$ from potentially untrustworthy -hosts.</P -><P ->To do that you could use:</P -><P -><PRE -CLASS="PROGRAMLISTING" -> [ipc$] - hosts allow = 192.168.115.0/24 127.0.0.1 - hosts deny = 0.0.0.0/0</PRE -></P -><P ->this would tell Samba that IPC$ connections are not allowed from -anywhere but the two listed places (localhost and a local -subnet). Connections to other shares would still be allowed. As the -IPC$ share is the only share that is always accessible anonymously -this provides some level of protection against attackers that do not -know a username/password for your host.</P -><P ->If you use this method then clients will be given a 'access denied' -reply when they try to access the IPC$ share. That means that those -clients will not be able to browse shares, and may also be unable to -access some other resources. </P -><P ->This is not recommended unless you cannot use one of the other -methods listed above for some reason.</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN4041" ->24.6. Upgrading Samba</A -></H2 -><P ->Please check regularly on <A -HREF="http://www.samba.org/" -TARGET="_top" ->http://www.samba.org/</A -> for updates and -important announcements. Occasionally security releases are made and -it is highly recommended to upgrade Samba when a security vulnerability -is discovered.</P -></DIV -></DIV -><DIV -CLASS="CHAPTER" -><HR><H1 -><A -NAME="UNICODE" -></A ->Chapter 25. Unicode/Charsets</H1 -><DIV -CLASS="SECT1" -><H2 -CLASS="SECT1" -><A -NAME="AEN4056" ->25.1. What are charsets and unicode?</A -></H2 -><P ->Computers communicate in numbers. In texts, each number will be -translated to a corresponding letter. The meaning that will be assigned -to a certain number depends on the <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->character set(charset)</I -></SPAN -> that is used. -A charset can be seen as a table that is used to translate numbers to -letters. Not all computers use the same charset (there are charsets -with German umlauts, Japanese characters, etc). Usually a charset contains -256 characters, which means that storing a character with it takes -exactly one byte. </P -><P ->There are also charsets that support even more characters, -but those need twice(or even more) as much storage space. These -charsets can contain <B -CLASS="COMMAND" ->256 * 256 = 65536</B -> characters, which -is more then all possible characters one could think of. They are called -multibyte charsets (because they use more then one byte to -store one character). </P -><P ->A standardised multibyte charset is unicode, info available at -<A -HREF="http://www.unicode.org/" -TARGET="_top" ->www.unicode.org</A ->. -Big advantage of using a multibyte charset is that you only need one; no -need to make sure two computers use the same charset when they are -communicating.</P -><P ->Old windows clients used to use single-byte charsets, named -'codepages' by microsoft. However, there is no support for -negotiating the charset to be used in the smb protocol. Thus, you -have to make sure you are using the same charset when talking to an old client. -Newer clients (Windows NT, 2K, XP) talk unicode over the wire.</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN4065" ->25.2. Samba and charsets</A -></H2 -><P ->As of samba 3.0, samba can (and will) talk unicode over the wire. Internally, -samba knows of three kinds of character sets: </P -><P -></P -><DIV -CLASS="VARIABLELIST" -><DL -><DT ->unix charset</DT -><DD -><P -> This is the charset used internally by your operating system. - The default is <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->ASCII</I -></SPAN ->, which is fine for most - systems. - </P -></DD -><DT ->display charset</DT -><DD -><P ->This is the charset samba will use to print messages - on your screen. It should generally be the same as the <B -CLASS="COMMAND" ->unix charset</B ->. - </P -></DD -><DT ->dos charset</DT -><DD -><P ->This is the charset samba uses when communicating with - DOS and Windows 9x clients. It will talk unicode to all newer clients. - The default depends on the charsets you have installed on your system. - Run <B -CLASS="COMMAND" ->testparm -v | grep "dos charset"</B -> to see - what the default is on your system. - </P -></DD -></DL -></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 ->26. <A -HREF="#SWAT" ->SWAT - The Samba Web Admininistration Tool</A -></DT -><DD -><DL -><DT ->26.1. <A -HREF="#AEN4098" ->SWAT Features and Benefits</A -></DT -><DD -><DL -><DT ->26.1.1. <A -HREF="#AEN4101" ->The SWAT Home Page</A -></DT -><DT ->26.1.2. <A -HREF="#AEN4104" ->Global Settings</A -></DT -><DT ->26.1.3. <A -HREF="#AEN4107" ->The SWAT Wizard</A -></DT -><DT ->26.1.4. <A -HREF="#AEN4110" ->Share Settings</A -></DT -><DT ->26.1.5. <A -HREF="#AEN4113" ->Printing Settings</A -></DT -><DT ->26.1.6. <A -HREF="#AEN4116" ->The Status Page</A -></DT -><DT ->26.1.7. <A -HREF="#AEN4119" ->The Password Change Page</A -></DT -></DL -></DD -></DL -></DD -><DT ->27. <A -HREF="#NT4MIGRATION" ->Migration from NT4 PDC to Samba-3 PDC</A -></DT -><DD -><DL -><DT ->27.1. <A -HREF="#AEN4134" ->Planning and Getting Started</A -></DT -><DD -><DL -><DT ->27.1.1. <A -HREF="#AEN4137" ->Objectives</A -></DT -><DT ->27.1.2. <A -HREF="#AEN4140" ->Steps In Migration Process</A -></DT -></DL -></DD -><DT ->27.2. <A -HREF="#AEN4143" ->Managing Samba-3 Domain Control</A -></DT -></DL -></DD -><DT ->28. <A -HREF="#SPEED" ->Samba performance issues</A -></DT -><DD -><DL -><DT ->28.1. <A -HREF="#AEN4163" ->Comparisons</A -></DT -><DT ->28.2. <A -HREF="#AEN4169" ->Socket options</A -></DT -><DT ->28.3. <A -HREF="#AEN4176" ->Read size</A -></DT -><DT ->28.4. <A -HREF="#AEN4181" ->Max xmit</A -></DT -><DT ->28.5. <A -HREF="#AEN4186" ->Log level</A -></DT -><DT ->28.6. <A -HREF="#AEN4189" ->Read raw</A -></DT -><DT ->28.7. <A -HREF="#AEN4194" ->Write raw</A -></DT -><DT ->28.8. <A -HREF="#AEN4198" ->Slow Clients</A -></DT -><DT ->28.9. <A -HREF="#AEN4202" ->Slow Logins</A -></DT -><DT ->28.10. <A -HREF="#AEN4205" ->Client tuning</A -></DT -></DL -></DD -><DT ->29. <A -HREF="#PORTABILITY" ->Portability</A -></DT -><DD -><DL -><DT ->29.1. <A -HREF="#AEN4249" ->HPUX</A -></DT -><DT ->29.2. <A -HREF="#AEN4255" ->SCO Unix</A -></DT -><DT ->29.3. <A -HREF="#AEN4259" ->DNIX</A -></DT -><DT ->29.4. <A -HREF="#AEN4288" ->RedHat Linux Rembrandt-II</A -></DT -><DT ->29.5. <A -HREF="#AEN4294" ->AIX</A -></DT -><DD -><DL -><DT ->29.5.1. <A -HREF="#AEN4296" ->Sequential Read Ahead</A -></DT -></DL -></DD -></DL -></DD -><DT ->30. <A -HREF="#OTHER-CLIENTS" ->Samba and other CIFS clients</A -></DT -><DD -><DL -><DT ->30.1. <A -HREF="#AEN4319" ->Macintosh clients?</A -></DT -><DT ->30.2. <A -HREF="#AEN4328" ->OS2 Client</A -></DT -><DD -><DL -><DT ->30.2.1. <A -HREF="#AEN4330" ->How can I configure OS/2 Warp Connect or - OS/2 Warp 4 as a client for Samba?</A -></DT -><DT ->30.2.2. <A -HREF="#AEN4345" ->How can I configure OS/2 Warp 3 (not Connect), - OS/2 1.2, 1.3 or 2.x for Samba?</A -></DT -><DT ->30.2.3. <A -HREF="#AEN4354" ->Are there any other issues when OS/2 (any version) - is used as a client?</A -></DT -><DT ->30.2.4. <A -HREF="#AEN4358" ->How do I get printer driver download working - for OS/2 clients?</A -></DT -></DL -></DD -><DT ->30.3. <A -HREF="#AEN4368" ->Windows for Workgroups</A -></DT -><DD -><DL -><DT ->30.3.1. <A -HREF="#AEN4370" ->Use latest TCP/IP stack from Microsoft</A -></DT -><DT ->30.3.2. <A -HREF="#AEN4375" ->Delete .pwl files after password change</A -></DT -><DT ->30.3.3. <A -HREF="#AEN4380" ->Configure WfW password handling</A -></DT -><DT ->30.3.4. <A -HREF="#AEN4384" ->Case handling of passwords</A -></DT -><DT ->30.3.5. <A -HREF="#AEN4389" ->Use TCP/IP as default protocol</A -></DT -></DL -></DD -><DT ->30.4. <A -HREF="#AEN4392" ->Windows '95/'98</A -></DT -><DT ->30.5. <A -HREF="#AEN4408" ->Windows 2000 Service Pack 2</A -></DT -><DT ->30.6. <A -HREF="#AEN4425" ->Windows NT 3.1</A -></DT -></DL -></DD -><DT ->31. <A -HREF="#COMPILING" ->How to compile SAMBA</A -></DT -><DD -><DL -><DT ->31.1. <A -HREF="#AEN4446" ->Access Samba source code via CVS</A -></DT -><DD -><DL -><DT ->31.1.1. <A -HREF="#AEN4448" ->Introduction</A -></DT -><DT ->31.1.2. <A -HREF="#AEN4453" ->CVS Access to samba.org</A -></DT -></DL -></DD -><DT ->31.2. <A -HREF="#AEN4489" ->Accessing the samba sources via rsync and ftp</A -></DT -><DT ->31.3. <A -HREF="#AEN4495" ->Building the Binaries</A -></DT -><DD -><DL -><DT ->31.3.1. <A -HREF="#AEN4523" ->Compiling samba with Active Directory support</A -></DT -></DL -></DD -><DT ->31.4. <A -HREF="#AEN4552" ->Starting the smbd and nmbd</A -></DT -><DD -><DL -><DT ->31.4.1. <A -HREF="#AEN4562" ->Starting from inetd.conf</A -></DT -><DT ->31.4.2. <A -HREF="#AEN4596" ->Alternative: starting it as a daemon</A -></DT -></DL -></DD -></DL -></DD -><DT ->32. <A -HREF="#BUGREPORT" ->Reporting Bugs</A -></DT -><DD -><DL -><DT ->32.1. <A -HREF="#AEN4627" ->Introduction</A -></DT -><DT ->32.2. <A -HREF="#AEN4637" ->General info</A -></DT -><DT ->32.3. <A -HREF="#AEN4643" ->Debug levels</A -></DT -><DT ->32.4. <A -HREF="#AEN4664" ->Internal errors</A -></DT -><DT ->32.5. <A -HREF="#AEN4678" ->Attaching to a running process</A -></DT -><DT ->32.6. <A -HREF="#AEN4686" ->Patches</A -></DT -></DL -></DD -><DT ->33. <A -HREF="#DIAGNOSIS" ->The samba checklist</A -></DT -><DD -><DL -><DT ->33.1. <A -HREF="#AEN4709" ->Introduction</A -></DT -><DT ->33.2. <A -HREF="#AEN4714" ->Assumptions</A -></DT -><DT ->33.3. <A -HREF="#AEN4733" ->The tests</A -></DT -><DT ->33.4. <A -HREF="#AEN4900" ->Still having troubles?</A -></DT -></DL -></DD -></DL -></DIV -></DIV -><DIV -CLASS="CHAPTER" -><HR><H1 -><A -NAME="SWAT" -></A ->Chapter 26. SWAT - The Samba Web Admininistration Tool</H1 -><P ->This is a rough guide to SWAT.</P -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN4098" ->26.1. SWAT Features and Benefits</A -></H2 -><P ->You must use at least the following ...</P -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN4101" ->26.1.1. The SWAT Home Page</A -></H3 -><P ->Blah blah here.</P -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN4104" ->26.1.2. Global Settings</A -></H3 -><P ->Document steps right here!</P -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN4107" ->26.1.3. The SWAT Wizard</A -></H3 -><P ->Lots of blah blah here.</P -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN4110" ->26.1.4. Share Settings</A -></H3 -><P ->Document steps right here!</P -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN4113" ->26.1.5. Printing Settings</A -></H3 -><P ->Document steps right here!</P -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN4116" ->26.1.6. The Status Page</A -></H3 -><P ->Document steps right here!</P -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN4119" ->26.1.7. The Password Change Page</A -></H3 -><P ->Document steps right here!</P -></DIV -></DIV -></DIV -><DIV -CLASS="CHAPTER" -><HR><H1 -><A -NAME="NT4MIGRATION" -></A ->Chapter 27. Migration from NT4 PDC to Samba-3 PDC</H1 -><P ->This is a rough guide to assist those wishing to migrate from NT4 domain control to -Samba-3 based domain control.</P -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN4134" ->27.1. Planning and Getting Started</A -></H2 -><P ->You must use at least the following ...</P -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN4137" ->27.1.1. Objectives</A -></H3 -><P ->Blah blah objectives here.</P -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN4140" ->27.1.2. Steps In Migration Process</A -></H3 -><P ->Document steps right here!</P -></DIV -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN4143" ->27.2. Managing Samba-3 Domain Control</A -></H2 -><P ->Lots of blah blah here.</P -></DIV -></DIV -><DIV -CLASS="CHAPTER" -><HR><H1 -><A -NAME="SPEED" -></A ->Chapter 28. Samba performance issues</H1 -><DIV -CLASS="SECT1" -><H2 -CLASS="SECT1" -><A -NAME="AEN4163" ->28.1. Comparisons</A -></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="AEN4169" ->28.2. Socket options</A -></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="AEN4176" ->28.3. Read size</A -></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="AEN4181" ->28.4. Max xmit</A -></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="AEN4186" ->28.5. Log level</A -></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="AEN4189" ->28.6. Read raw</A -></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="AEN4194" ->28.7. Write raw</A -></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="AEN4198" ->28.8. Slow Clients</A -></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="AEN4202" ->28.9. Slow Logins</A -></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="AEN4205" ->28.10. Client tuning</A -></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="PORTABILITY" -></A ->Chapter 29. 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="AEN4249" ->29.1. HPUX</A -></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="AEN4255" ->29.2. SCO Unix</A -></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="AEN4259" ->29.3. DNIX</A -></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="AEN4288" ->29.4. RedHat Linux Rembrandt-II</A -></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 -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN4294" ->29.5. AIX</A -></H2 -><DIV -CLASS="SECT2" -><H3 -CLASS="SECT2" -><A -NAME="AEN4296" ->29.5.1. Sequential Read Ahead</A -></H3 -><P ->Disabling Sequential Read Ahead using <KBD -CLASS="USERINPUT" ->vmtune -r 0</KBD -> improves -samba performance significally.</P -></DIV -></DIV -></DIV -><DIV -CLASS="CHAPTER" -><HR><H1 -><A -NAME="OTHER-CLIENTS" -></A ->Chapter 30. Samba and other CIFS clients</H1 -><P ->This chapter contains client-specific information.</P -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN4319" ->30.1. Macintosh clients?</A -></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="AEN4328" ->30.2. OS2 Client</A -></H2 -><DIV -CLASS="SECT2" -><H3 -CLASS="SECT2" -><A -NAME="AEN4330" ->30.2.1. How can I configure OS/2 Warp Connect or - OS/2 Warp 4 as a client for Samba?</A -></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="AEN4345" ->30.2.2. How can I configure OS/2 Warp 3 (not Connect), - OS/2 1.2, 1.3 or 2.x for Samba?</A -></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="AEN4354" ->30.2.3. Are there any other issues when OS/2 (any version) - is used as a client?</A -></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="AEN4358" ->30.2.4. How do I get printer driver download working - for OS/2 clients?</A -></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 = - <VAR -CLASS="REPLACEABLE" ->filename</VAR ->". Then, in the file - specified by <VAR -CLASS="REPLACEABLE" ->filename</VAR ->, 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="AEN4368" ->30.3. Windows for Workgroups</A -></H2 -><DIV -CLASS="SECT2" -><H3 -CLASS="SECT2" -><A -NAME="AEN4370" ->30.3.1. Use latest TCP/IP stack from Microsoft</A -></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="AEN4375" ->30.3.2. Delete .pwl files after password change</A -></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="AEN4380" ->30.3.3. Configure WfW password handling</A -></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="AEN4384" ->30.3.4. Case handling of passwords</A -></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 -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN4389" ->30.3.5. Use TCP/IP as default protocol</A -></H3 -><P ->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 -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN4392" ->30.4. Windows '95/'98</A -></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="AEN4408" ->30.5. Windows 2000 Service Pack 2</A -></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 -><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 ->This bug does not occur when using winbind to -create accounts on the Samba host for Domain users.</P -></TD -></TR -></TABLE -></DIV -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN4425" ->30.6. Windows NT 3.1</A -></H2 -><P ->If you have problems communicating across routers with Windows -NT 3.1 workstations, read <A -HREF="http://support.microsoft.com/default.aspx?scid=kb;[LN];Q103765" -TARGET="_top" ->this Microsoft Knowledge Base article</A ->. </P -></DIV -></DIV -><DIV -CLASS="CHAPTER" -><HR><H1 -><A -NAME="COMPILING" -></A ->Chapter 31. How to compile SAMBA</H1 -><P ->You can obtain the samba source from the <A -HREF="http://samba.org/" -TARGET="_top" ->samba website</A ->. To obtain a development version, -you can download samba from CVS or using rsync. </P -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN4446" ->31.1. Access Samba source code via CVS</A -></H2 -><DIV -CLASS="SECT2" -><H3 -CLASS="SECT2" -><A -NAME="AEN4448" ->31.1.1. Introduction</A -></H3 -><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 chapter 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="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN4453" ->31.1.2. CVS Access to samba.org</A -></H3 -><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="SECT3" -><HR><H4 -CLASS="SECT3" -><A -NAME="AEN4456" ->31.1.2.1. Access via CVSweb</A -></H4 -><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="SECT3" -><HR><H4 -CLASS="SECT3" -><A -NAME="AEN4461" ->31.1.2.2. Access via cvs</A -></H4 -><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 -> <KBD -CLASS="USERINPUT" ->cvs -d :pserver:cvs@samba.org:/cvsroot login</KBD -> - </P -><P -> When it asks you for a password type <KBD -CLASS="USERINPUT" ->cvs</KBD ->. - </P -></LI -><LI -><P -> Run the command - </P -><P -> <KBD -CLASS="USERINPUT" ->cvs -d :pserver:cvs@samba.org:/cvsroot co samba</KBD -> - </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 <VAR -CLASS="PARAMETER" ->-r</VAR -> - 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 userinput. - </P -><P -> <KBD -CLASS="USERINPUT" ->cvs -d :pserver:cvs@samba.org:/cvsroot co -r SAMBA_2_2 samba</KBD -> - </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 -> <KBD -CLASS="USERINPUT" ->cvs update -d -P</KBD -> - </P -></LI -></OL -></DIV -></DIV -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN4489" ->31.2. Accessing the samba sources via rsync and ftp</A -></H2 -><P -> pserver.samba.org also exports unpacked copies of most parts of the CVS tree at <A -HREF="ftp://pserver.samba.org/pub/unpacked" -TARGET="_top" ->ftp://pserver.samba.org/pub/unpacked</A -> and also via anonymous rsync at rsync://pserver.samba.org/ftp/unpacked/. I recommend using rsync rather than ftp. - See <A -HREF="http://rsync.samba.org/" -TARGET="_top" ->the rsync homepage</A -> for more info on rsync. - </P -><P -> The disadvantage of the unpacked trees - is that they do not support automatic - merging of local changes like CVS does. - rsync access is most convenient for an - initial install. - </P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN4495" ->31.3. Building the Binaries</A -></H2 -><P ->To do this, first run the program <KBD -CLASS="USERINPUT" ->./configure - </KBD -> 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 -><SAMP -CLASS="PROMPT" ->root# </SAMP -><KBD -CLASS="USERINPUT" ->./configure --help - </KBD -></P -><P ->first to see what special options you can enable. - Then executing</P -><P -><SAMP -CLASS="PROMPT" ->root# </SAMP -><KBD -CLASS="USERINPUT" ->make</KBD -></P -><P ->will create the binaries. Once it's successfully - compiled you can use </P -><P -><SAMP -CLASS="PROMPT" ->root# </SAMP -><KBD -CLASS="USERINPUT" ->make install</KBD -></P -><P ->to install the binaries and manual pages. You can - separately install the binaries and/or man pages using</P -><P -><SAMP -CLASS="PROMPT" ->root# </SAMP -><KBD -CLASS="USERINPUT" ->make installbin - </KBD -></P -><P ->and</P -><P -><SAMP -CLASS="PROMPT" ->root# </SAMP -><KBD -CLASS="USERINPUT" ->make installman - </KBD -></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 -><SAMP -CLASS="PROMPT" ->root# </SAMP -><KBD -CLASS="USERINPUT" ->make revert - </KBD -></P -><P ->if you find this version a disaster!</P -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN4523" ->31.3.1. Compiling samba with Active Directory support</A -></H3 -><P ->In order to compile samba with ADS support, you need to have installed - on your system: - <P -></P -><TABLE -BORDER="0" -><TBODY -><TR -><TD ->the MIT kerberos development libraries (either install from the 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 -><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 <TT -CLASS="FILENAME" ->include/config.h</TT -> 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 -><DIV -CLASS="SECT3" -><HR><H4 -CLASS="SECT3" -><A -NAME="AEN4535" ->31.3.1.1. Installing the required packages for Debian</A -></H4 -><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="SECT3" -><HR><H4 -CLASS="SECT3" -><A -NAME="AEN4542" ->31.3.1.2. Installing the required packages for RedHat</A -></H4 -><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 -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN4552" ->31.4. Starting the smbd and nmbd</A -></H2 -><P ->You must choose to start smbd and nmbd either - as daemons or from <SPAN -CLASS="APPLICATION" ->inetd</SPAN ->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 <SPAN -CLASS="APPLICATION" ->inetd</SPAN ->, 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 <SPAN -CLASS="APPLICATION" ->smbd</SPAN -> - and <SPAN -CLASS="APPLICATION" ->nmbd</SPAN -> 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="AEN4562" ->31.4.1. Starting from inetd.conf</A -></H3 -><P ->NOTE; The following will be different if - you use NIS, NIS+ or LDAP to distribute 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 -><KBD -CLASS="USERINPUT" ->netbios-ssn 139/tcp</KBD -></P -><P ->similarly for 137/udp you should have an entry like:</P -><P -><KBD -CLASS="USERINPUT" ->netbios-ns 137/udp</KBD -></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 -><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 ->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 -></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 ->On many systems you may need to use the - <B -CLASS="COMMAND" ->interfaces</B -> option in <TT -CLASS="FILENAME" ->smb.conf</TT -> to specify the IP address - and netmask of your interfaces. Run <SPAN -CLASS="APPLICATION" ->ifconfig</SPAN -> - as root if you don't know what the broadcast is for your - net. <SPAN -CLASS="APPLICATION" ->nmbd</SPAN -> tries to determine it at run - time, but fails on some unixes. - </P -></TD -></TR -></TABLE -></DIV -><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 ->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 -></TD -></TR -></TABLE -></DIV -><P ->Restart <B -CLASS="COMMAND" ->inetd</B ->, perhaps just send - it a HUP. If you have installed an earlier version of <SPAN -CLASS="APPLICATION" -> nmbd</SPAN -> then you may need to kill nmbd as well.</P -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN4596" ->31.4.2. Alternative: starting it as a daemon</A -></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 -><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 ->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 -></TD -></TR -></TABLE -></DIV -></DIV -></DIV -></DIV -><DIV -CLASS="CHAPTER" -><HR><H1 -><A -NAME="BUGREPORT" -></A ->Chapter 32. Reporting Bugs</H1 -><DIV -CLASS="SECT1" -><H2 -CLASS="SECT1" -><A -NAME="AEN4627" ->32.1. Introduction</A -></H2 -><P ->The email address for bug reports for stable releases is <A -HREF="mailto: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="AEN4637" ->32.2. General info</A -></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" ->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="AEN4643" ->32.3. Debug levels</A -></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.<VAR -CLASS="REPLACEABLE" ->machine</VAR -></TT -> where -<VAR -CLASS="REPLACEABLE" ->machine</VAR -> is the name of the client you wish to debug. In that file -put any <TT -CLASS="FILENAME" ->smb.conf</TT -> 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 <TT -CLASS="FILENAME" ->smb.conf</TT -> 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="AEN4664" ->32.4. Internal errors</A -></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 <TT -CLASS="FILENAME" ->corefiles</TT -> -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 <KBD -CLASS="USERINPUT" ->dbx</KBD ->. Then within the debugger use the -command <KBD -CLASS="USERINPUT" ->where</KBD -> 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 <KBD -CLASS="USERINPUT" ->disass</KBD -> 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="AEN4678" ->32.5. Attaching to a running process</A -></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 <KBD -CLASS="USERINPUT" ->gdb smbd <VAR -CLASS="REPLACEABLE" ->PID</VAR -></KBD -> where you get <VAR -CLASS="REPLACEABLE" ->PID</VAR -> from -<SPAN -CLASS="APPLICATION" ->smbstatus</SPAN ->. Then use <KBD -CLASS="USERINPUT" ->c</KBD -> 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="AEN4686" ->32.6. Patches</A -></H2 -><P ->The best sort of bug report is one that includes a fix! If you send us -patches please use <KBD -CLASS="USERINPUT" ->diff -u</KBD -> format if your version of -diff supports it, otherwise use <KBD -CLASS="USERINPUT" ->diff -c4</KBD ->. 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 33. The samba checklist</H1 -><DIV -CLASS="SECT1" -><H2 -CLASS="SECT1" -><A -NAME="AEN4709" ->33.1. Introduction</A -></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="AEN4714" ->33.2. Assumptions</A -></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 -<TT -CLASS="FILENAME" ->smb.conf</TT ->. I will assume this share is called <VAR -CLASS="REPLACEABLE" ->tmp</VAR ->. -You can add a <VAR -CLASS="REPLACEABLE" ->tmp</VAR -> share like by adding the -following to <TT -CLASS="FILENAME" ->smb.conf</TT ->:</P -><P -><PRE -CLASS="PROGRAMLISTING" -> [tmp] - comment = temporary files - path = /tmp - read only = yes </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 ->These tests assume version 3.0 or later of the samba suite. Some commands shown did not exist in earlier versions. </P -></TD -></TR -></TABLE -></DIV -><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 <TT -CLASS="FILENAME" ->/etc/resolv.conf</TT -> -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 <TT -CLASS="FILENAME" ->smb.conf</TT -> file results in <B -CLASS="COMMAND" ->dns proxy = no</B ->. The -best way to check this is with <KBD -CLASS="USERINPUT" ->testparm smb.conf</KBD ->.</P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN4733" ->33.3. The tests</A -></H2 -><DIV -CLASS="PROCEDURE" -><P -><B ->Diagnosing your samba server</B -></P -><OL -TYPE="1" -><LI -><P ->In the directory in which you store your <TT -CLASS="FILENAME" ->smb.conf</TT -> file, run the command -<KBD -CLASS="USERINPUT" ->testparm smb.conf</KBD ->. If it reports any errors then your <TT -CLASS="FILENAME" ->smb.conf</TT -> -configuration file is faulty.</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 ->Your <TT -CLASS="FILENAME" ->smb.conf</TT -> file may be located in: <TT -CLASS="FILENAME" ->/etc/samba</TT -> -Or in: <TT -CLASS="FILENAME" ->/usr/local/samba/lib</TT -></P -></TD -></TR -></TABLE -></DIV -></LI -><LI -><P ->Run the command <KBD -CLASS="USERINPUT" ->ping BIGSERVER</KBD -> from the PC and -<KBD -CLASS="USERINPUT" ->ping ACLIENT</KBD -> 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 <TT -CLASS="FILENAME" ->/etc/hosts</TT -> 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 <SPAN -CLASS="APPLICATION" ->ipfwadm</SPAN -> program.)</P -></LI -><LI -><P ->Run the command <KBD -CLASS="USERINPUT" ->smbclient -L BIGSERVER</KBD -> 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 <B -CLASS="COMMAND" ->hosts allow</B ->, -<B -CLASS="COMMAND" ->hosts deny</B -> or <B -CLASS="COMMAND" ->valid users</B -> line in your -<TT -CLASS="FILENAME" ->smb.conf</TT ->, or your guest account is not -valid. Check what your guest account is using <SPAN -CLASS="APPLICATION" ->testparm</SPAN -> and -temporarily remove any <B -CLASS="COMMAND" ->hosts allow</B ->, <B -CLASS="COMMAND" ->hosts deny</B ->, <B -CLASS="COMMAND" ->valid users</B -> or <B -CLASS="COMMAND" ->invalid users</B -> 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 <KBD -CLASS="USERINPUT" ->netstat -a</KBD ->.</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 <SPAN -CLASS="APPLICATION" ->smbd</SPAN ->, -or a similar fatal problem with the initial startup of <SPAN -CLASS="APPLICATION" ->smbd</SPAN ->. Also -check your config file (<TT -CLASS="FILENAME" ->smb.conf</TT ->) for syntax errors with <SPAN -CLASS="APPLICATION" ->testparm</SPAN -> -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 <TT -CLASS="FILENAME" ->smb.conf</TT -> 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 <B -CLASS="COMMAND" ->bind interfaces only</B -> parameter where you -may wish to -use the samba password change facility, or where <SPAN -CLASS="APPLICATION" ->smbclient</SPAN -> may need to -access local service for name resolution or for local resource -connections. (Note: the <B -CLASS="COMMAND" ->bind interfaces only</B -> 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 <SPAN -CLASS="APPLICATION" ->inetd</SPAN -> already) or -something like Digital's Pathworks. Check your <TT -CLASS="FILENAME" ->inetd.conf</TT -> file before trying -to start <SPAN -CLASS="APPLICATION" ->smbd</SPAN -> as a daemon, it can avoid a lot of frustration!</P -><P ->And yet another possible cause for failure of this test 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 <TT -CLASS="FILENAME" ->log.nmb</TT -> file.</P -></LI -><LI -><P ->Run the command <KBD -CLASS="USERINPUT" ->nmblookup -B BIGSERVER __SAMBA__</KBD ->. You should get the -IP address of your Samba server back.</P -><P ->If you don't then nmbd is incorrectly installed. Check your <TT -CLASS="FILENAME" ->inetd.conf</TT -> -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 -></LI -><LI -><P ->run the command <KBD -CLASS="USERINPUT" ->nmblookup -B ACLIENT '*'</KBD -></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 -></LI -><LI -><P ->Run the command <KBD -CLASS="USERINPUT" ->nmblookup -d 2 '*'</KBD -></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 -<B -CLASS="COMMAND" ->interfaces</B -> option in <TT -CLASS="FILENAME" ->smb.conf</TT -> 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 <VAR -CLASS="PARAMETER" ->-B</VAR -> 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 -></LI -><LI -><P ->Run the command <KBD -CLASS="USERINPUT" ->smbclient //BIGSERVER/TMP</KBD ->. 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 <VAR -CLASS="PARAMETER" ->-U <VAR -CLASS="REPLACEABLE" ->accountname</VAR -></VAR -> option to the end of -the command line. eg: -<KBD -CLASS="USERINPUT" ->smbclient //bigserver/tmp -Ujohndoe</KBD -></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 ->It is possible to specify the password along with the username -as follows: -<KBD -CLASS="USERINPUT" ->smbclient //bigserver/tmp -Ujohndoe%secret</KBD -></P -></TD -></TR -></TABLE -></DIV -><P ->Once you enter the password you should get the <SAMP -CLASS="PROMPT" ->smb></SAMP -> 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 <TT -CLASS="FILENAME" ->smb.conf</TT ->.</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 <SPAN -CLASS="APPLICATION" ->smbd</SPAN -> - </P -></LI -><LI -><P -> your <B -CLASS="COMMAND" ->valid users</B -> configuration is incorrect - </P -></LI -><LI -><P -> you have a mixed case password and you haven't enabled the <B -CLASS="COMMAND" ->password - level</B -> option at a high enough level - </P -></LI -><LI -><P -> the <B -CLASS="COMMAND" ->path =</B -> line in <TT -CLASS="FILENAME" ->smb.conf</TT -> is incorrect. Check it with <SPAN -CLASS="APPLICATION" ->testparm</SPAN -> - </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 <VAR -CLASS="REPLACEABLE" ->command</VAR -></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 -></LI -><LI -><P ->On the PC type the command <KBD -CLASS="USERINPUT" ->net view \\BIGSERVER</KBD ->. 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 <SPAN -CLASS="APPLICATION" ->nmbd</SPAN -> installation</P -></LI -><LI -><P -> add the IP address of BIGSERVER to the <B -CLASS="COMMAND" ->wins server</B -> 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 <KBD -CLASS="USERINPUT" ->smbclient -L</KBD -> test above. In -particular, make sure your <B -CLASS="COMMAND" ->hosts allow</B -> 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 <TT -CLASS="FILENAME" ->hosts.allow</TT -> file for your client (or subnet, etc.)</P -></LI -><LI -><P ->Run the command <KBD -CLASS="USERINPUT" ->net use x: \\BIGSERVER\TMP</KBD ->. 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 <B -CLASS="COMMAND" ->hosts allow</B -> -and other config lines in <TT -CLASS="FILENAME" ->smb.conf</TT -> 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 <B -CLASS="COMMAND" ->user = -<VAR -CLASS="REPLACEABLE" ->username</VAR -></B -> to the <B -CLASS="COMMAND" ->[tmp]</B -> section of -<TT -CLASS="FILENAME" ->smb.conf</TT -> where <VAR -CLASS="REPLACEABLE" ->username</VAR -> 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 -></LI -><LI -><P ->Run the command <KBD -CLASS="USERINPUT" ->nmblookup -M <VAR -CLASS="REPLACEABLE" ->testgroup</VAR -></KBD -> where -<VAR -CLASS="REPLACEABLE" ->testgroup</VAR -> 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 <TT -CLASS="FILENAME" ->smb.conf</TT ->. Make -sure you have <B -CLASS="COMMAND" ->preferred master = yes</B -> to ensure that -an election is held at startup.</P -></LI -><LI -><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 -<TT -CLASS="FILENAME" ->smb.conf</TT -> file, or make sure <B -CLASS="COMMAND" ->encrypted passwords</B -> is -set to "yes".</P -></LI -></OL -></DIV -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN4900" ->33.4. Still having troubles?</A -></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 -></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 45236cda46..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.7"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -13,10 +14,10 @@ REL="UP" TITLE="Type of installation" HREF="type.html"><LINK REL="PREVIOUS" -TITLE="Samba Backup Domain Controller to Samba Domain Control" +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,25 +73,126 @@ WIDTH="100%"></DIV CLASS="CHAPTER" ><H1 ><A -NAME="ADS" -></A ->Chapter 8. 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 +><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" ><H1 CLASS="SECT1" ><A -NAME="AEN1355" ->8.1. Setup your <TT -CLASS="FILENAME" ->smb.conf</TT -></A -></H1 +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" +><TBODY +><TR +><TD +>libkrb5-dev</TD +></TR +><TR +><TD +>krb5-user</TD +></TR +></TBODY +></TABLE ><P ->You must use at least the following 3 options in smb.conf:</P +></P +></P +></DIV +><DIV +CLASS="SECT1" +><H1 +CLASS="SECT1" +><A +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" +><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" +><H1 +CLASS="SECT1" +><A +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 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" @@ -111,103 +213,34 @@ CLASS="FILENAME" CLASS="PROGRAMLISTING" > ads server = your.kerberos.server</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 ->You do *not* need a smbpasswd file, and older clients will - be authenticated as if <B -CLASS="COMMAND" ->security = domain</B ->, - 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 -></TD -></TR -></TABLE -></DIV +>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 ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1368" ->8.2. Setup your <TT -CLASS="FILENAME" ->/etc/krb5.conf</TT -></A -></H1 +NAME="AEN1217">8.4. Setup your /etc/krb5.conf</H1 ><P ->The minimal configuration for <TT -CLASS="FILENAME" ->krb5.conf</TT -> is:</P +>The minimal configuration for krb5.conf is:</P ><P ><PRE CLASS="PROGRAMLISTING" ->[realms] +> [realms] YOUR.KERBEROS.REALM = { kdc = your.kerberos.server }</PRE ></P ><P ->Test your config by doing a <KBD -CLASS="USERINPUT" ->kinit <VAR -CLASS="REPLACEABLE" ->USERNAME</VAR ->@<VAR -CLASS="REPLACEABLE" ->REALM</VAR -></KBD -> and making sure that +>Test your config by doing a "kinit USERNAME@REALM" and making sure that your password is accepted by the Win2000 KDC. </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 ->The realm must be uppercase. </P -></TD -></TR -></TABLE -></DIV +>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 @@ -215,65 +248,36 @@ 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 -<TT -CLASS="FILENAME" ->/etc/hosts</TT -> 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 <SPAN -CLASS="APPLICATION" ->smbclient</SPAN -> then you can skip -straight to <A -HREF="ads.html#ADS-TEST-SMBCLIENT" ->Test with <SPAN -CLASS="APPLICATION" ->smbclient</SPAN -></A -> now. -<A -HREF="ads.html#ADS-CREATE-MACHINE-ACCOUNT" ->Creating a computer account</A -> -and <A -HREF="ads.html#ADS-TEST-SERVER" ->testing your servers</A -> -is only needed if you want kerberos -support for <SPAN -CLASS="APPLICATION" ->smbd</SPAN -> and <SPAN -CLASS="APPLICATION" ->winbindd</SPAN ->.</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 in smbd.</P ></DIV ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="ADS-CREATE-MACHINE-ACCOUNT" ->8.3. Create the computer account</A -></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: -<KBD -CLASS="USERINPUT" ->net ads join</KBD +<B +CLASS="COMMAND" +>net ads join</B ></P ><DIV CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1396" ->8.3.1. Possible errors</A -></H2 +NAME="AEN1231">8.5.1. Possible errors</H2 ><P ><P ></P @@ -281,6 +285,12 @@ NAME="AEN1396" 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 @@ -296,18 +306,16 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="ADS-TEST-SERVER" ->8.4. Test your server setup</A -></H1 +NAME="AEN1243">8.6. Test your server setup</H1 ><P ->On a Windows 2000 client try <KBD -CLASS="USERINPUT" ->net use * \\server\share</KBD +>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 <KBD -CLASS="USERINPUT" ->klist tickets</KBD +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 @@ -316,37 +324,21 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="ADS-TEST-SMBCLIENT" ->8.5. Testing with <SPAN -CLASS="APPLICATION" ->smbclient</SPAN -></A -></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 <SPAN -CLASS="APPLICATION" ->smbclient</SPAN -> and kerberos. Use <SPAN -CLASS="APPLICATION" ->smbclient</SPAN -> as usual, but -specify the <VAR -CLASS="PARAMETER" ->-k</VAR -> option to choose kerberos authentication.</P +server using smbclient and kerberos. Use smbclient as usual, but +specify the -k option to choose kerberos authentication.</P ></DIV ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1416" ->8.6. Notes</A -></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 +>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 @@ -396,7 +388,7 @@ ACCESSKEY="N" WIDTH="33%" ALIGN="left" VALIGN="top" ->Samba Backup Domain Controller to Samba Domain Control</TD +>How to Act as a Backup Domain Controller in a Purely Samba Controlled Domain</TD ><TD WIDTH="34%" ALIGN="center" @@ -410,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 ff0588130c..e7eefcb441 100644 --- a/docs/htmldocs/appendixes.html +++ b/docs/htmldocs/appendixes.html @@ -5,16 +5,17 @@ >Appendixes</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><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="Unicode/Charsets" -HREF="unicode.html"><LINK +TITLE="Samba performance issues" +HREF="speed.html"><LINK REL="NEXT" -TITLE="SWAT - The Samba Web Admininistration Tool" -HREF="swat.html"></HEAD +TITLE="Portability" +HREF="portability.html"></HEAD ><BODY CLASS="PART" BGCOLOR="#FFFFFF" @@ -42,7 +43,7 @@ WIDTH="10%" ALIGN="left" VALIGN="bottom" ><A -HREF="unicode.html" +HREF="speed.html" ACCESSKEY="P" >Prev</A ></TD @@ -56,7 +57,7 @@ WIDTH="10%" ALIGN="right" VALIGN="bottom" ><A -HREF="swat.html" +HREF="portability.html" ACCESSKEY="N" >Next</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,424 +82,243 @@ CLASS="TOC" >Table of Contents</B ></DT ><DT ->26. <A -HREF="swat.html" ->SWAT - The Samba Web Admininistration Tool</A -></DT -><DD -><DL -><DT ->26.1. <A -HREF="swat.html#AEN4098" ->SWAT Features and Benefits</A -></DT -><DD -><DL -><DT ->26.1.1. <A -HREF="swat.html#AEN4101" ->The SWAT Home Page</A -></DT -><DT ->26.1.2. <A -HREF="swat.html#AEN4104" ->Global Settings</A -></DT -><DT ->26.1.3. <A -HREF="swat.html#AEN4107" ->The SWAT Wizard</A -></DT -><DT ->26.1.4. <A -HREF="swat.html#AEN4110" ->Share Settings</A -></DT -><DT ->26.1.5. <A -HREF="swat.html#AEN4113" ->Printing Settings</A -></DT -><DT ->26.1.6. <A -HREF="swat.html#AEN4116" ->The Status Page</A -></DT -><DT ->26.1.7. <A -HREF="swat.html#AEN4119" ->The Password Change Page</A -></DT -></DL -></DD -></DL -></DD -><DT ->27. <A -HREF="nt4migration.html" ->Migration from NT4 PDC to Samba-3 PDC</A -></DT -><DD -><DL -><DT ->27.1. <A -HREF="nt4migration.html#AEN4134" ->Planning and Getting Started</A -></DT -><DD -><DL -><DT ->27.1.1. <A -HREF="nt4migration.html#AEN4137" ->Objectives</A -></DT -><DT ->27.1.2. <A -HREF="nt4migration.html#AEN4140" ->Steps In Migration Process</A -></DT -></DL -></DD -><DT ->27.2. <A -HREF="nt4migration.html#AEN4143" ->Managing Samba-3 Domain Control</A -></DT -></DL -></DD -><DT ->28. <A -HREF="speed.html" ->Samba performance issues</A -></DT -><DD -><DL -><DT ->28.1. <A -HREF="speed.html#AEN4163" ->Comparisons</A -></DT -><DT ->28.2. <A -HREF="speed.html#AEN4169" ->Socket options</A -></DT -><DT ->28.3. <A -HREF="speed.html#AEN4176" ->Read size</A -></DT -><DT ->28.4. <A -HREF="speed.html#AEN4181" ->Max xmit</A -></DT -><DT ->28.5. <A -HREF="speed.html#AEN4186" ->Log level</A -></DT -><DT ->28.6. <A -HREF="speed.html#AEN4189" ->Read raw</A -></DT -><DT ->28.7. <A -HREF="speed.html#AEN4194" ->Write raw</A -></DT -><DT ->28.8. <A -HREF="speed.html#AEN4198" ->Slow Clients</A -></DT -><DT ->28.9. <A -HREF="speed.html#AEN4202" ->Slow Logins</A -></DT -><DT ->28.10. <A -HREF="speed.html#AEN4205" ->Client tuning</A -></DT -></DL -></DD -><DT ->29. <A +>23. <A HREF="portability.html" >Portability</A ></DT ><DD ><DL ><DT ->29.1. <A -HREF="portability.html#AEN4249" +>23.1. <A +HREF="portability.html#AEN3139" >HPUX</A ></DT ><DT ->29.2. <A -HREF="portability.html#AEN4255" +>23.2. <A +HREF="portability.html#AEN3145" >SCO Unix</A ></DT ><DT ->29.3. <A -HREF="portability.html#AEN4259" +>23.3. <A +HREF="portability.html#AEN3149" >DNIX</A ></DT ><DT ->29.4. <A -HREF="portability.html#AEN4288" +>23.4. <A +HREF="portability.html#AEN3178" >RedHat Linux Rembrandt-II</A ></DT -><DT ->29.5. <A -HREF="portability.html#AEN4294" ->AIX</A -></DT -><DD -><DL -><DT ->29.5.1. <A -HREF="portability.html#AEN4296" ->Sequential Read Ahead</A -></DT -></DL -></DD -><DT ->29.6. <A -HREF="portability.html#AEN4300" ->Solaris</A -></DT ></DL ></DD ><DT ->30. <A +>24. <A HREF="other-clients.html" >Samba and other CIFS clients</A ></DT ><DD ><DL ><DT ->30.1. <A -HREF="other-clients.html#AEN4326" +>24.1. <A +HREF="other-clients.html#AEN3199" >Macintosh clients?</A ></DT ><DT ->30.2. <A -HREF="other-clients.html#AEN4335" +>24.2. <A +HREF="other-clients.html#AEN3208" >OS2 Client</A ></DT ><DD ><DL ><DT ->30.2.1. <A -HREF="other-clients.html#AEN4337" +>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 ->30.2.2. <A -HREF="other-clients.html#AEN4352" +>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 ->30.2.3. <A -HREF="other-clients.html#AEN4361" +>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 ->30.2.4. <A -HREF="other-clients.html#AEN4365" +>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 ->30.3. <A -HREF="other-clients.html#AEN4375" +>24.3. <A +HREF="other-clients.html#AEN3248" >Windows for Workgroups</A ></DT ><DD ><DL ><DT ->30.3.1. <A -HREF="other-clients.html#AEN4377" +>24.3.1. <A +HREF="other-clients.html#AEN3250" >Use latest TCP/IP stack from Microsoft</A ></DT ><DT ->30.3.2. <A -HREF="other-clients.html#AEN4382" +>24.3.2. <A +HREF="other-clients.html#AEN3255" >Delete .pwl files after password change</A ></DT ><DT ->30.3.3. <A -HREF="other-clients.html#AEN4387" +>24.3.3. <A +HREF="other-clients.html#AEN3260" >Configure WfW password handling</A ></DT ><DT ->30.3.4. <A -HREF="other-clients.html#AEN4391" +>24.3.4. <A +HREF="other-clients.html#AEN3264" >Case handling of passwords</A ></DT -><DT ->30.3.5. <A -HREF="other-clients.html#AEN4396" ->Use TCP/IP as default protocol</A -></DT ></DL ></DD ><DT ->30.4. <A -HREF="other-clients.html#AEN4399" +>24.4. <A +HREF="other-clients.html#AEN3269" >Windows '95/'98</A ></DT ><DT ->30.5. <A -HREF="other-clients.html#AEN4415" +>24.5. <A +HREF="other-clients.html#AEN3285" >Windows 2000 Service Pack 2</A ></DT -><DT ->30.6. <A -HREF="other-clients.html#AEN4432" ->Windows NT 3.1</A -></DT ></DL ></DD ><DT ->31. <A -HREF="compiling.html" ->How to compile SAMBA</A +>25. <A +HREF="bugreport.html" +>Reporting Bugs</A ></DT ><DD ><DL ><DT ->31.1. <A -HREF="compiling.html#AEN4453" ->Access Samba source code via CVS</A +>25.1. <A +HREF="bugreport.html#AEN3309" +>Introduction</A ></DT -><DD -><DL ><DT ->31.1.1. <A -HREF="compiling.html#AEN4455" ->Introduction</A +>25.2. <A +HREF="bugreport.html#AEN3319" +>General info</A ></DT ><DT ->31.1.2. <A -HREF="compiling.html#AEN4460" ->CVS Access to samba.org</A +>25.3. <A +HREF="bugreport.html#AEN3325" +>Debug levels</A ></DT -></DL -></DD ><DT ->31.2. <A -HREF="compiling.html#AEN4496" ->Accessing the samba sources via rsync and ftp</A +>25.4. <A +HREF="bugreport.html#AEN3342" +>Internal errors</A ></DT ><DT ->31.3. <A -HREF="compiling.html#AEN4502" ->Building the Binaries</A +>25.5. <A +HREF="bugreport.html#AEN3352" +>Attaching to a running process</A ></DT -><DD -><DL ><DT ->31.3.1. <A -HREF="compiling.html#AEN4530" ->Compiling samba with Active Directory support</A +>25.6. <A +HREF="bugreport.html#AEN3355" +>Patches</A ></DT ></DL ></DD ><DT ->31.4. <A -HREF="compiling.html#AEN4559" ->Starting the smbd and nmbd</A +>26. <A +HREF="diagnosis.html" +>Diagnosing your samba server</A ></DT ><DD ><DL ><DT ->31.4.1. <A -HREF="compiling.html#AEN4569" ->Starting from inetd.conf</A +>26.1. <A +HREF="diagnosis.html#AEN3378" +>Introduction</A ></DT ><DT ->31.4.2. <A -HREF="compiling.html#AEN4603" ->Alternative: starting it as a daemon</A +>26.2. <A +HREF="diagnosis.html#AEN3383" +>Assumptions</A ></DT -></DL -></DD -></DL -></DD ><DT ->32. <A -HREF="bugreport.html" ->Reporting Bugs</A +>26.3. <A +HREF="diagnosis.html#AEN3393" +>Tests</A ></DT ><DD ><DL ><DT ->32.1. <A -HREF="bugreport.html#AEN4634" ->Introduction</A +>26.3.1. <A +HREF="diagnosis.html#AEN3395" +>Test 1</A ></DT ><DT ->32.2. <A -HREF="bugreport.html#AEN4644" ->General info</A +>26.3.2. <A +HREF="diagnosis.html#AEN3401" +>Test 2</A ></DT ><DT ->32.3. <A -HREF="bugreport.html#AEN4650" ->Debug levels</A +>26.3.3. <A +HREF="diagnosis.html#AEN3407" +>Test 3</A ></DT ><DT ->32.4. <A -HREF="bugreport.html#AEN4671" ->Internal errors</A +>26.3.4. <A +HREF="diagnosis.html#AEN3422" +>Test 4</A ></DT ><DT ->32.5. <A -HREF="bugreport.html#AEN4685" ->Attaching to a running process</A +>26.3.5. <A +HREF="diagnosis.html#AEN3427" +>Test 5</A ></DT ><DT ->32.6. <A -HREF="bugreport.html#AEN4693" ->Patches</A +>26.3.6. <A +HREF="diagnosis.html#AEN3433" +>Test 6</A ></DT -></DL -></DD ><DT ->33. <A -HREF="diagnosis.html" ->The samba checklist</A +>26.3.7. <A +HREF="diagnosis.html#AEN3441" +>Test 7</A ></DT -><DD -><DL ><DT ->33.1. <A -HREF="diagnosis.html#AEN4716" ->Introduction</A +>26.3.8. <A +HREF="diagnosis.html#AEN3467" +>Test 8</A ></DT ><DT ->33.2. <A -HREF="diagnosis.html#AEN4721" ->Assumptions</A +>26.3.9. <A +HREF="diagnosis.html#AEN3484" +>Test 9</A +></DT +><DT +>26.3.10. <A +HREF="diagnosis.html#AEN3492" +>Test 10</A ></DT ><DT ->33.3. <A -HREF="diagnosis.html#AEN4740" ->The tests</A +>26.3.11. <A +HREF="diagnosis.html#AEN3498" +>Test 11</A ></DT +></DL +></DD ><DT ->33.4. <A -HREF="diagnosis.html#AEN4907" +>26.4. <A +HREF="diagnosis.html#AEN3503" >Still having troubles?</A ></DT ></DL @@ -525,7 +343,7 @@ WIDTH="33%" ALIGN="left" VALIGN="top" ><A -HREF="unicode.html" +HREF="speed.html" ACCESSKEY="P" >Prev</A ></TD @@ -543,7 +361,7 @@ WIDTH="33%" ALIGN="right" VALIGN="top" ><A -HREF="swat.html" +HREF="portability.html" ACCESSKEY="N" >Next</A ></TD @@ -553,7 +371,7 @@ ACCESSKEY="N" WIDTH="33%" ALIGN="left" VALIGN="top" ->Unicode/Charsets</TD +>Samba performance issues</TD ><TD WIDTH="34%" ALIGN="center" @@ -563,7 +381,7 @@ VALIGN="top" WIDTH="33%" ALIGN="right" VALIGN="top" ->SWAT - The Samba Web Admininistration Tool</TD +>Portability</TD ></TR ></TABLE ></DIV diff --git a/docs/htmldocs/browsing-quick.html b/docs/htmldocs/browsing-quick.html index 95a1ca3504..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.7"><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 @@ -82,117 +81,43 @@ 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="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 ->MS Windows 2000 and later can be configured to operate with NO NetBIOS -over TCP/IP. Samba-3 and later also supports this mode of operation.</P -></TD -></TR -></TABLE -></DIV -><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN183" ->2.1. Discussion</A -></H1 +NAME="AEN377">3.1. Discussion</H1 ><P >Firstly, all MS Windows networking is based on SMB (Server Message -Block) based messaging. SMB messaging may be implemented using NetBIOS or -without 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 +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 -<B -CLASS="COMMAND" ->remote announce</B -> -parameter to smb.conf helps to project browse announcements -to remote network segments via unicast UDP. Similarly, the -<B -CLASS="COMMAND" ->remote browse sync</B -> parameter of <TT -CLASS="FILENAME" ->smb.conf</TT -> -implements browse list collation using unicast UDP.</P +"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 <SPAN -CLASS="APPLICATION" ->nmbd</SPAN -> should be configured on one (1) machine as the WINS +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 -<B -CLASS="COMMAND" ->remote announce</B -> and the <B -CLASS="COMMAND" ->remote browse sync</B -> -parameters to your <TT -CLASS="FILENAME" ->smb.conf</TT -> file.</P -><P ->If only one WINS server is used for an entire multi-segment network then -the use of the <B -CLASS="COMMAND" ->remote announce</B -> and the -<B -CLASS="COMMAND" ->remote browse sync</B -> parameters should NOT be necessary.</P -><P ->As of Samba 3 WINS replication is being worked on. The bulk of the code has -been committed, but it still needs maturation.</P -><P ->Right now samba WINS does not support MS-WINS replication. This means that -when setting up Samba as a WINS server there must only be one <SPAN -CLASS="APPLICATION" ->nmbd</SPAN -> 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 -<B -CLASS="COMMAND" ->remote browse sync</B -> and <B -CLASS="COMMAND" ->remote announce</B -> -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 +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 @@ -204,120 +129,19 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN204" ->2.2. How browsing functions and how to deploy stable and -dependable browsing using Samba</A -></H1 -><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 -<B -CLASS="COMMAND" ->remote announce</B -> 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 <B -CLASS="COMMAND" ->remote -browse sync</B -> parameter in the <TT -CLASS="FILENAME" ->smb.conf</TT -> 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 <B -CLASS="COMMAND" ->remote -browse sync</B -> 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" -><H1 -CLASS="SECT1" -><A -NAME="AEN218" ->2.3. Use of the <B -CLASS="COMMAND" ->Remote Announce</B -> parameter</A -></H1 +NAME="AEN385">3.2. Use of the "Remote Announce" parameter</H1 ><P ->The <B -CLASS="COMMAND" ->remote announce</B -> parameter of -<TT -CLASS="FILENAME" ->smb.conf</TT -> can be used to forcibly ensure +>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 <B -CLASS="COMMAND" ->remote announce</B -> parameter is: +The syntax of the "remote announce" parameter is: <PRE CLASS="PROGRAMLISTING" -> remote announce = <VAR -CLASS="REPLACEABLE" ->a.b.c.d [e.f.g.h]</VAR -> ...</PRE +> remote announce = a.b.c.d [e.f.g.h] ...</PRE > _or_ <PRE CLASS="PROGRAMLISTING" -> remote announce = <VAR -CLASS="REPLACEABLE" ->a.b.c.d/WORKGROUP [e.f.g.h/WORKGROUP]</VAR -> ...</PRE +> remote announce = a.b.c.d/WORKGROUP [e.f.g.h/WORKGROUP] ...</PRE > where: @@ -327,14 +151,7 @@ where: CLASS="VARIABLELIST" ><DL ><DT -><VAR -CLASS="REPLACEABLE" ->a.b.c.d</VAR -> and -<VAR -CLASS="REPLACEABLE" ->e.f.g.h</VAR -></DT +>a.b.c.d and e.f.g.h</DT ><DD ><P >is either the LMB (Local Master Browser) IP address @@ -349,10 +166,7 @@ undesirable but may be necessary if we do NOT know the IP address of the remote LMB.</P ></DD ><DT -><VAR -CLASS="REPLACEABLE" ->WORKGROUP</VAR -></DT +>WORKGROUP</DT ><DD ><P >is optional and can be either our own workgroup @@ -371,51 +185,27 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN241" ->2.4. Use of the <B -CLASS="COMMAND" ->Remote Browse Sync</B -> parameter</A -></H1 +NAME="AEN399">3.3. Use of the "Remote Browse Sync" parameter</H1 ><P ->The <B -CLASS="COMMAND" ->remote browse sync</B -> parameter of -<TT -CLASS="FILENAME" ->smb.conf</TT -> is used to announce to +>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 <B -CLASS="COMMAND" ->remote browse sync</B -> parameter is: - +>The syntax of the "remote browse sync" parameter is: <PRE CLASS="PROGRAMLISTING" ->remote browse sync = <VAR -CLASS="REPLACEABLE" ->a.b.c.d</VAR -></PRE +> remote browse sync = a.b.c.d</PRE > -where <VAR -CLASS="REPLACEABLE" ->a.b.c.d</VAR -> is either the IP address of the remote LMB or else is the network broadcast address of the remote segment.</P +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" ><H1 CLASS="SECT1" ><A -NAME="AEN252" ->2.5. Use of WINS</A -></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 @@ -437,11 +227,7 @@ 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 -<TT -CLASS="FILENAME" ->lmhosts</TT -> files that must reside on all clients in the -absence of WINS.</P +"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 @@ -459,70 +245,32 @@ 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 -<B -CLASS="COMMAND" ->wins support = yes</B -> to the <TT -CLASS="FILENAME" ->smb.conf</TT -> -file [globals] section.</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 -><DIV -CLASS="IMPORTANT" -><P -></P -><TABLE -CLASS="IMPORTANT" -WIDTH="100%" -BORDER="0" -><TR -><TD -WIDTH="25" -ALIGN="CENTER" -VALIGN="TOP" -><IMG -SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/important.gif" -HSPACE="5" -ALT="Important"></TD -><TD -ALIGN="LEFT" -VALIGN="TOP" ><P ->Never use both <B -CLASS="COMMAND" ->wins support = yes</B -> together -with <B -CLASS="COMMAND" ->wins server = a.b.c.d</B -> -particularly not using it's own IP address. -Specifying both will cause <SPAN -CLASS="APPLICATION" ->nmbd</SPAN -> to refuse to start!</P -></TD -></TR -></TABLE -></DIV +><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" ><H1 CLASS="SECT1" ><A -NAME="AEN269" ->2.6. Do NOT use more than one (1) protocol on MS Windows machines</A -></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 ><P ->Every NetBIOS machine takes part in a process of electing the LMB (and DMB) +>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 @@ -538,19 +286,6 @@ interface over the IPX protocol. Samba will then lose the LMB role as Windows as an LMB and thus browse list operation on all TCP/IP only machines will fail.</P ><P -><SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->Windows 95, 98, 98se, Me are referred to generically as Windows 9x. -The Windows NT4, 2000, XP and 2003 use common protocols. These are roughly -referred to as the WinNT family, but it should be recognised that 2000 and -XP/2003 introduce new protocol extensions that cause them to behave -differently from MS Windows NT4. Generally, where a server does NOT support -the newer or extended protocol, these will fall back to the NT4 protocols.</I -></SPAN -></P -><P >The safest rule of all to follow it this - USE ONLY ONE PROTOCOL!</P ></DIV ><DIV @@ -558,14 +293,12 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN277" ->2.7. Name Resolution Order</A -></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" @@ -586,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" @@ -605,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 @@ -653,7 +388,7 @@ WIDTH="33%" ALIGN="left" VALIGN="top" ><A -HREF="install.html" +HREF="improved-browsing.html" ACCESSKEY="P" >Prev</A ></TD @@ -671,7 +406,7 @@ WIDTH="33%" ALIGN="right" VALIGN="top" ><A -HREF="passdb.html" +HREF="pwencrypt.html" ACCESSKEY="N" >Next</A ></TD @@ -681,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" @@ -695,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 516d187e6a..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.7"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -13,10 +14,10 @@ REL="UP" TITLE="Appendixes" HREF="appendixes.html"><LINK REL="PREVIOUS" -TITLE="How to compile SAMBA" -HREF="compiling.html"><LINK +TITLE="Samba and other CIFS clients" +HREF="other-clients.html"><LINK REL="NEXT" -TITLE="The samba checklist" +TITLE="Diagnosing your samba server" HREF="diagnosis.html"></HEAD ><BODY CLASS="CHAPTER" @@ -45,7 +46,7 @@ WIDTH="10%" ALIGN="left" VALIGN="bottom" ><A -HREF="compiling.html" +HREF="other-clients.html" ACCESSKEY="P" >Prev</A ></TD @@ -72,20 +73,16 @@ WIDTH="100%"></DIV CLASS="CHAPTER" ><H1 ><A -NAME="BUGREPORT" -></A ->Chapter 32. Reporting Bugs</H1 +NAME="BUGREPORT">Chapter 25. Reporting Bugs</H1 ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN4634" ->32.1. Introduction</A -></H1 +NAME="AEN3309">25.1. Introduction</H1 ><P >The email address for bug reports for stable releases is <A -HREF="mailto:samba@samba.org" +HREF="samba@samba.org" TARGET="_top" >samba@samba.org</A >. @@ -125,9 +122,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN4644" ->32.2. General info</A -></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 @@ -135,7 +130,8 @@ 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" +HREF="Diagnosis.html" +TARGET="_top" >diagnosis</A >? This is very important.</P @@ -149,9 +145,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN4650" ->32.3. Debug levels</A -></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 @@ -180,19 +174,10 @@ include = /usr/local/samba/lib/smb.conf.%m</PRE >then create a file <TT CLASS="FILENAME" ->/usr/local/samba/lib/smb.conf.<VAR -CLASS="REPLACEABLE" ->machine</VAR -></TT +>/usr/local/samba/lib/smb.conf.machine</TT > where -<VAR -CLASS="REPLACEABLE" ->machine</VAR -> is the name of the client you wish to debug. In that file -put any <TT -CLASS="FILENAME" ->smb.conf</TT -> commands you want, for example +"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 @@ -212,10 +197,7 @@ CLASS="COMMAND" >debuglevel =</B > that has been used in older versions of Samba and is being retained for backwards -compatibility of <TT -CLASS="FILENAME" ->smb.conf</TT -> files.</P +compatibility of smb.conf files.</P ><P >As the <B CLASS="COMMAND" @@ -231,14 +213,12 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN4671" ->32.4. Internal errors</A -></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 segmentation fault and almost certainly means a bug in Samba (unless -you have faulty hardware or system software).</P +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 @@ -248,10 +228,7 @@ include it in your bug report.</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 <TT -CLASS="FILENAME" ->corefiles</TT -> +>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 @@ -262,20 +239,11 @@ CLASS="COMMAND" ></P ><P >adding appropriate paths to smbd and core so gdb can find them. If you -don't have gdb then try <KBD -CLASS="USERINPUT" ->dbx</KBD ->. Then within the debugger use the -command <KBD -CLASS="USERINPUT" ->where</KBD -> to give a stack trace of where the problem +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 <KBD -CLASS="USERINPUT" ->disass</KBD -> of the routine +>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 @@ -287,30 +255,13 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN4685" ->32.5. Attaching to a running process</A -></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 does often). To debug with this sort of system you could try to attach -to the running process using <KBD -CLASS="USERINPUT" ->gdb smbd <VAR -CLASS="REPLACEABLE" ->PID</VAR -></KBD -> where you get <VAR -CLASS="REPLACEABLE" ->PID</VAR -> from -<SPAN -CLASS="APPLICATION" ->smbstatus</SPAN ->. Then use <KBD -CLASS="USERINPUT" ->c</KBD -> to continue and try to cause the core dump +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 @@ -319,18 +270,16 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN4693" ->32.6. Patches</A -></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 <KBD -CLASS="USERINPUT" ->diff -u</KBD +patches please use <B +CLASS="COMMAND" +>diff -u</B > format if your version of -diff supports it, otherwise use <KBD -CLASS="USERINPUT" ->diff -c4</KBD +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 @@ -352,7 +301,7 @@ WIDTH="33%" ALIGN="left" VALIGN="top" ><A -HREF="compiling.html" +HREF="other-clients.html" ACCESSKEY="P" >Prev</A ></TD @@ -380,7 +329,7 @@ ACCESSKEY="N" WIDTH="33%" ALIGN="left" VALIGN="top" ->How to compile SAMBA</TD +>Samba and other CIFS clients</TD ><TD WIDTH="34%" ALIGN="center" @@ -394,7 +343,7 @@ ACCESSKEY="U" WIDTH="33%" ALIGN="right" VALIGN="top" ->The samba checklist</TD +>Diagnosing your samba server</TD ></TR ></TABLE ></DIV diff --git a/docs/htmldocs/compiling.html b/docs/htmldocs/compiling.html deleted file mode 100644 index c387dd72fb..0000000000 --- a/docs/htmldocs/compiling.html +++ /dev/null @@ -1,855 +0,0 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> -<HTML -><HEAD -><TITLE ->How to compile SAMBA</TITLE -><META -NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK -REL="HOME" -TITLE="SAMBA Project Documentation" -HREF="samba-howto-collection.html"><LINK -REL="UP" -TITLE="Appendixes" -HREF="appendixes.html"><LINK -REL="PREVIOUS" -TITLE="Samba and other CIFS clients" -HREF="other-clients.html"><LINK -REL="NEXT" -TITLE="Reporting Bugs" -HREF="bugreport.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="other-clients.html" -ACCESSKEY="P" ->Prev</A -></TD -><TD -WIDTH="80%" -ALIGN="center" -VALIGN="bottom" -></TD -><TD -WIDTH="10%" -ALIGN="right" -VALIGN="bottom" -><A -HREF="bugreport.html" -ACCESSKEY="N" ->Next</A -></TD -></TR -></TABLE -><HR -ALIGN="LEFT" -WIDTH="100%"></DIV -><DIV -CLASS="CHAPTER" -><H1 -><A -NAME="COMPILING" -></A ->Chapter 31. How to compile SAMBA</H1 -><P ->You can obtain the samba source from the <A -HREF="http://samba.org/" -TARGET="_top" ->samba website</A ->. To obtain a development version, -you can download samba from CVS or using rsync. </P -><DIV -CLASS="SECT1" -><H1 -CLASS="SECT1" -><A -NAME="AEN4453" ->31.1. Access Samba source code via CVS</A -></H1 -><DIV -CLASS="SECT2" -><H2 -CLASS="SECT2" -><A -NAME="AEN4455" ->31.1.1. Introduction</A -></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 chapter 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="SECT2" -><H2 -CLASS="SECT2" -><A -NAME="AEN4460" ->31.1.2. CVS Access to samba.org</A -></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="SECT3" -><H3 -CLASS="SECT3" -><A -NAME="AEN4463" ->31.1.2.1. Access via CVSweb</A -></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="SECT3" -><H3 -CLASS="SECT3" -><A -NAME="AEN4468" ->31.1.2.2. Access via cvs</A -></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 -> <KBD -CLASS="USERINPUT" ->cvs -d :pserver:cvs@samba.org:/cvsroot login</KBD -> - </P -><P -> When it asks you for a password type <KBD -CLASS="USERINPUT" ->cvs</KBD ->. - </P -></LI -><LI -><P -> Run the command - </P -><P -> <KBD -CLASS="USERINPUT" ->cvs -d :pserver:cvs@samba.org:/cvsroot co samba</KBD -> - </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 <VAR -CLASS="PARAMETER" ->-r</VAR -> - 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 userinput. - </P -><P -> <KBD -CLASS="USERINPUT" ->cvs -d :pserver:cvs@samba.org:/cvsroot co -r SAMBA_2_2 samba</KBD -> - </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 -> <KBD -CLASS="USERINPUT" ->cvs update -d -P</KBD -> - </P -></LI -></OL -></DIV -></DIV -></DIV -><DIV -CLASS="SECT1" -><H1 -CLASS="SECT1" -><A -NAME="AEN4496" ->31.2. Accessing the samba sources via rsync and ftp</A -></H1 -><P -> pserver.samba.org also exports unpacked copies of most parts of the CVS tree at <A -HREF="ftp://pserver.samba.org/pub/unpacked" -TARGET="_top" ->ftp://pserver.samba.org/pub/unpacked</A -> and also via anonymous rsync at rsync://pserver.samba.org/ftp/unpacked/. I recommend using rsync rather than ftp. - See <A -HREF="http://rsync.samba.org/" -TARGET="_top" ->the rsync homepage</A -> for more info on rsync. - </P -><P -> The disadvantage of the unpacked trees - is that they do not support automatic - merging of local changes like CVS does. - rsync access is most convenient for an - initial install. - </P -></DIV -><DIV -CLASS="SECT1" -><H1 -CLASS="SECT1" -><A -NAME="AEN4502" ->31.3. Building the Binaries</A -></H1 -><P ->To do this, first run the program <KBD -CLASS="USERINPUT" ->./configure - </KBD -> 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 -><SAMP -CLASS="PROMPT" ->root# </SAMP -><KBD -CLASS="USERINPUT" ->./configure --help - </KBD -></P -><P ->first to see what special options you can enable. - Then executing</P -><P -><SAMP -CLASS="PROMPT" ->root# </SAMP -><KBD -CLASS="USERINPUT" ->make</KBD -></P -><P ->will create the binaries. Once it's successfully - compiled you can use </P -><P -><SAMP -CLASS="PROMPT" ->root# </SAMP -><KBD -CLASS="USERINPUT" ->make install</KBD -></P -><P ->to install the binaries and manual pages. You can - separately install the binaries and/or man pages using</P -><P -><SAMP -CLASS="PROMPT" ->root# </SAMP -><KBD -CLASS="USERINPUT" ->make installbin - </KBD -></P -><P ->and</P -><P -><SAMP -CLASS="PROMPT" ->root# </SAMP -><KBD -CLASS="USERINPUT" ->make installman - </KBD -></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 -><SAMP -CLASS="PROMPT" ->root# </SAMP -><KBD -CLASS="USERINPUT" ->make revert - </KBD -></P -><P ->if you find this version a disaster!</P -><DIV -CLASS="SECT2" -><H2 -CLASS="SECT2" -><A -NAME="AEN4530" ->31.3.1. Compiling samba with Active Directory support</A -></H2 -><P ->In order to compile samba with ADS support, you need to have installed - on your system: - <P -></P -><TABLE -BORDER="0" -><TBODY -><TR -><TD ->the MIT kerberos development libraries (either install from the 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 -><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 <TT -CLASS="FILENAME" ->include/config.h</TT -> 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 -><DIV -CLASS="SECT3" -><H3 -CLASS="SECT3" -><A -NAME="AEN4542" ->31.3.1.1. Installing the required packages for Debian</A -></H3 -><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="SECT3" -><H3 -CLASS="SECT3" -><A -NAME="AEN4549" ->31.3.1.2. Installing the required packages for RedHat</A -></H3 -><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 -></DIV -><DIV -CLASS="SECT1" -><H1 -CLASS="SECT1" -><A -NAME="AEN4559" ->31.4. Starting the smbd and nmbd</A -></H1 -><P ->You must choose to start smbd and nmbd either - as daemons or from <SPAN -CLASS="APPLICATION" ->inetd</SPAN ->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 <SPAN -CLASS="APPLICATION" ->inetd</SPAN ->, 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 <SPAN -CLASS="APPLICATION" ->smbd</SPAN -> - and <SPAN -CLASS="APPLICATION" ->nmbd</SPAN -> using the recommended daemon method - is that they will respond slightly more quickly to an initial connection - request.</P -><DIV -CLASS="SECT2" -><H2 -CLASS="SECT2" -><A -NAME="AEN4569" ->31.4.1. Starting from inetd.conf</A -></H2 -><P ->NOTE; The following will be different if - you use NIS, NIS+ or LDAP to distribute 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 -><KBD -CLASS="USERINPUT" ->netbios-ssn 139/tcp</KBD -></P -><P ->similarly for 137/udp you should have an entry like:</P -><P -><KBD -CLASS="USERINPUT" ->netbios-ns 137/udp</KBD -></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 -><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 ->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 -></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 ->On many systems you may need to use the - <B -CLASS="COMMAND" ->interfaces</B -> option in <TT -CLASS="FILENAME" ->smb.conf</TT -> to specify the IP address - and netmask of your interfaces. Run <SPAN -CLASS="APPLICATION" ->ifconfig</SPAN -> - as root if you don't know what the broadcast is for your - net. <SPAN -CLASS="APPLICATION" ->nmbd</SPAN -> tries to determine it at run - time, but fails on some unixes. - </P -></TD -></TR -></TABLE -></DIV -><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 ->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 -></TD -></TR -></TABLE -></DIV -><P ->Restart <B -CLASS="COMMAND" ->inetd</B ->, perhaps just send - it a HUP. If you have installed an earlier version of <SPAN -CLASS="APPLICATION" -> nmbd</SPAN -> then you may need to kill nmbd as well.</P -></DIV -><DIV -CLASS="SECT2" -><H2 -CLASS="SECT2" -><A -NAME="AEN4603" ->31.4.2. Alternative: starting it as a daemon</A -></H2 -><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 -><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 ->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 -></TD -></TR -></TABLE -></DIV -></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="other-clients.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="bugreport.html" -ACCESSKEY="N" ->Next</A -></TD -></TR -><TR -><TD -WIDTH="33%" -ALIGN="left" -VALIGN="top" ->Samba and other CIFS clients</TD -><TD -WIDTH="34%" -ALIGN="center" -VALIGN="top" -><A -HREF="appendixes.html" -ACCESSKEY="U" ->Up</A -></TD -><TD -WIDTH="33%" -ALIGN="right" -VALIGN="top" ->Reporting Bugs</TD -></TR -></TABLE -></DIV -></BODY -></HTML ->
\ No newline at end of file diff --git a/docs/htmldocs/cvs-access.html b/docs/htmldocs/cvs-access.html new file mode 100644 index 0000000000..73cd333805 --- /dev/null +++ b/docs/htmldocs/cvs-access.html @@ -0,0 +1,298 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML +><HEAD +><TITLE +>HOWTO Access Samba source code via CVS</TITLE +><META +NAME="GENERATOR" +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 +REL="PREVIOUS" +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 +><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="samba-ldap-howto.html" +ACCESSKEY="P" +>Prev</A +></TD +><TD +WIDTH="80%" +ALIGN="center" +VALIGN="bottom" +></TD +><TD +WIDTH="10%" +ALIGN="right" +VALIGN="bottom" +><A +HREF="groupmapping.html" +ACCESSKEY="N" +>Next</A +></TD +></TR +></TABLE +><HR +ALIGN="LEFT" +WIDTH="100%"></DIV +><DIV +CLASS="CHAPTER" +><H1 +><A +NAME="CVS-ACCESS">Chapter 20. HOWTO Access Samba source code via CVS</H1 +><DIV +CLASS="SECT1" +><H1 +CLASS="SECT1" +><A +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 +"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" +><H1 +CLASS="SECT1" +><A +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, +including samba, rsync and jitterbug. There are two main ways of +accessing the CVS server on this host.</P +><DIV +CLASS="SECT2" +><H2 +CLASS="SECT2" +><A +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 +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" +><H2 +CLASS="SECT2" +><A +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 +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="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="samba-ldap-howto.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="groupmapping.html" +ACCESSKEY="N" +>Next</A +></TD +></TR +><TR +><TD +WIDTH="33%" +ALIGN="left" +VALIGN="top" +>Storing Samba's User/Machine Account information in an LDAP Directory</TD +><TD +WIDTH="34%" +ALIGN="center" +VALIGN="top" +><A +HREF="optional.html" +ACCESSKEY="U" +>Up</A +></TD +><TD +WIDTH="33%" +ALIGN="right" +VALIGN="top" +>Group mapping HOWTO</TD +></TR +></TABLE +></DIV +></BODY +></HTML +>
\ No newline at end of file diff --git a/docs/htmldocs/diagnosis.html b/docs/htmldocs/diagnosis.html index 43651c049d..a7b2e59436 100644 --- a/docs/htmldocs/diagnosis.html +++ b/docs/htmldocs/diagnosis.html @@ -2,10 +2,11 @@ <HTML ><HEAD ><TITLE ->The samba checklist</TITLE +>Diagnosing your samba server</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><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 33. The samba checklist</H1 +NAME="DIAGNOSIS">Chapter 26. Diagnosing your samba server</H1 ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN4716" ->33.1. Introduction</A -></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="AEN4721" ->33.2. Assumptions</A -></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 @@ -105,21 +100,8 @@ BIGSERVER and a PC called ACLIENT both in workgroup TESTGROUP.</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 -<TT -CLASS="FILENAME" ->smb.conf</TT ->. I will assume this share is called <VAR -CLASS="REPLACEABLE" ->tmp</VAR ->. -You can add a <VAR -CLASS="REPLACEABLE" ->tmp</VAR -> share like by adding the -following to <TT -CLASS="FILENAME" ->smb.conf</TT ->:</P +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" @@ -128,131 +110,53 @@ CLASS="PROGRAMLISTING" path = /tmp read only = yes </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 ->These tests assume version 3.0 or later of the samba suite. Some commands shown did not exist in earlier versions. </P -></TD -></TR -></TABLE -></DIV +>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 <TT -CLASS="FILENAME" ->/etc/resolv.conf</TT -> +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 <TT -CLASS="FILENAME" ->smb.conf</TT -> file results in <B -CLASS="COMMAND" ->dns proxy = no</B ->. The -best way to check this is with <KBD -CLASS="USERINPUT" ->testparm smb.conf</KBD ->.</P +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" ><H1 CLASS="SECT1" ><A -NAME="AEN4740" ->33.3. The tests</A -></H1 +NAME="AEN3393">26.3. Tests</H1 ><DIV -CLASS="PROCEDURE" -><P -><B ->Diagnosing your samba server</B -></P -><OL -TYPE="1" -><LI +CLASS="SECT2" +><H2 +CLASS="SECT2" +><A +NAME="AEN3395">26.3.1. Test 1</H2 ><P ->In the directory in which you store your <TT -CLASS="FILENAME" ->smb.conf</TT -> file, run the command -<KBD -CLASS="USERINPUT" ->testparm smb.conf</KBD ->. If it reports any errors then your <TT -CLASS="FILENAME" ->smb.conf</TT -> +>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 -><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 ->Your <TT -CLASS="FILENAME" ->smb.conf</TT -> file may be located in: <TT +>Note: Your smb.conf file may be located in: <TT CLASS="FILENAME" >/etc/samba</TT > -Or in: <TT + Or in: <TT CLASS="FILENAME" >/usr/local/samba/lib</TT ></P -></TD -></TR -></TABLE ></DIV -></LI -><LI +><DIV +CLASS="SECT2" +><H2 +CLASS="SECT2" +><A +NAME="AEN3401">26.3.2. Test 2</H2 ><P ->Run the command <KBD -CLASS="USERINPUT" ->ping BIGSERVER</KBD -> from the PC and -<KBD -CLASS="USERINPUT" ->ping ACLIENT</KBD -> from +>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 @@ -260,99 +164,49 @@ software is not correctly installed. </P run ping.</P ><P >If you get a message saying "host not found" or similar then your DNS -software or <TT -CLASS="FILENAME" ->/etc/hosts</TT -> file is not correctly setup. -It is possible to +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 <SPAN -CLASS="APPLICATION" ->ipfwadm</SPAN -> program.)</P -></LI -><LI +this is done via the ipfwadm program.)</P +></DIV +><DIV +CLASS="SECT2" +><H2 +CLASS="SECT2" +><A +NAME="AEN3407">26.3.3. Test 3</H2 ><P ->Run the command <KBD -CLASS="USERINPUT" ->smbclient -L BIGSERVER</KBD -> on the unix box. You +>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 <B -CLASS="COMMAND" ->hosts allow</B ->, -<B -CLASS="COMMAND" ->hosts deny</B -> or <B -CLASS="COMMAND" ->valid users</B -> line in your -<TT -CLASS="FILENAME" ->smb.conf</TT ->, or your guest account is not -valid. Check what your guest account is using <SPAN -CLASS="APPLICATION" ->testparm</SPAN -> and -temporarily remove any <B -CLASS="COMMAND" ->hosts allow</B ->, <B -CLASS="COMMAND" ->hosts deny</B ->, <B -CLASS="COMMAND" ->valid users</B -> or <B -CLASS="COMMAND" ->invalid users</B -> lines.</P +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 <KBD -CLASS="USERINPUT" ->netstat -a</KBD ->.</P +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 <SPAN -CLASS="APPLICATION" ->smbd</SPAN ->, -or a similar fatal problem with the initial startup of <SPAN -CLASS="APPLICATION" ->smbd</SPAN ->. Also -check your config file (<TT -CLASS="FILENAME" ->smb.conf</TT ->) for syntax errors with <SPAN -CLASS="APPLICATION" ->testparm</SPAN -> +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 <TT -CLASS="FILENAME" ->smb.conf</TT -> file entries:</P +the following smb.conf file entries:</P ><P ><PRE CLASS="PROGRAMLISTING" @@ -371,57 +225,34 @@ CLASS="PROGRAMLISTING" hosts allow = xxx.xxx.xxx.xxx/yy 127.</PRE ></P ><P ->Do NOT use the <B -CLASS="COMMAND" ->bind interfaces only</B -> parameter where you -may wish to -use the samba password change facility, or where <SPAN -CLASS="APPLICATION" ->smbclient</SPAN -> may need to +>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 <B -CLASS="COMMAND" ->bind interfaces only</B -> parameter deficiency +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 <SPAN -CLASS="APPLICATION" ->inetd</SPAN -> already) or -something like Digital's Pathworks. Check your <TT -CLASS="FILENAME" ->inetd.conf</TT -> file before trying -to start <SPAN -CLASS="APPLICATION" ->smbd</SPAN -> as a daemon, it can avoid a lot of frustration!</P -><P ->And yet another possible cause for failure of this test is when the subnet mask +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 <TT -CLASS="FILENAME" ->log.nmb</TT -> file.</P -></LI -><LI +correct and that Samba has correctly noted these in the log.nmb file.</P +></DIV +><DIV +CLASS="SECT2" +><H2 +CLASS="SECT2" +><A +NAME="AEN3422">26.3.4. Test 4</H2 ><P ->Run the command <KBD -CLASS="USERINPUT" ->nmblookup -B BIGSERVER __SAMBA__</KBD ->. You should get the +>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 <TT -CLASS="FILENAME" ->inetd.conf</TT -> +>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 @@ -429,12 +260,17 @@ to udp port 137.</P 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 -></LI -><LI +></DIV +><DIV +CLASS="SECT2" +><H2 +CLASS="SECT2" +><A +NAME="AEN3427">26.3.5. Test 5</H2 ><P ->run the command <KBD -CLASS="USERINPUT" ->nmblookup -B ACLIENT '*'</KBD +>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 @@ -443,12 +279,17 @@ 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 -></LI -><LI +></DIV +><DIV +CLASS="SECT2" +><H2 +CLASS="SECT2" +><A +NAME="AEN3433">26.3.6. Test 6</H2 ><P ->Run the command <KBD -CLASS="USERINPUT" ->nmblookup -d 2 '*'</KBD +>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 @@ -461,86 +302,46 @@ hosts.</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 -<B -CLASS="COMMAND" ->interfaces</B -> option in <TT -CLASS="FILENAME" ->smb.conf</TT -> to manually configure your IP +"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 <VAR -CLASS="PARAMETER" ->-B</VAR -> option to set the broadcast address to the that of the PCs +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 -></LI -><LI +></DIV +><DIV +CLASS="SECT2" +><H2 +CLASS="SECT2" +><A +NAME="AEN3441">26.3.7. Test 7</H2 ><P ->Run the command <KBD -CLASS="USERINPUT" ->smbclient //BIGSERVER/TMP</KBD +>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 <VAR -CLASS="PARAMETER" ->-U <VAR -CLASS="REPLACEABLE" ->accountname</VAR -></VAR -> option to the end of +another account then add the -U >accountname< option to the end of the command line. eg: -<KBD -CLASS="USERINPUT" ->smbclient //bigserver/tmp -Ujohndoe</KBD -></P -><DIV -CLASS="NOTE" -><P +<B +CLASS="COMMAND" +>smbclient //bigserver/tmp -Ujohndoe</B ></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 ->It is possible to specify the password along with the username +>Note: It is possible to specify the password along with the username as follows: -<KBD -CLASS="USERINPUT" ->smbclient //bigserver/tmp -Ujohndoe%secret</KBD +<B +CLASS="COMMAND" +>smbclient //bigserver/tmp -Ujohndoe%secret</B ></P -></TD -></TR -></TABLE -></DIV ><P ->Once you enter the password you should get the <SAMP -CLASS="PROMPT" ->smb></SAMP -> prompt. If you +>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 <TT -CLASS="FILENAME" ->smb.conf</TT ->.</P +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 @@ -550,41 +351,23 @@ TYPE="1" ><LI ><P > you have shadow passords (or some other password system) but didn't - compile in support for them in <SPAN -CLASS="APPLICATION" ->smbd</SPAN -> + compile in support for them in smbd </P ></LI ><LI ><P -> your <B -CLASS="COMMAND" ->valid users</B -> configuration is incorrect +> your "valid users" configuration is incorrect </P ></LI ><LI ><P -> you have a mixed case password and you haven't enabled the <B -CLASS="COMMAND" ->password - level</B -> option at a high enough level +> 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 <B -CLASS="COMMAND" ->path =</B -> line in <TT -CLASS="FILENAME" ->smb.conf</TT -> is incorrect. Check it with <SPAN -CLASS="APPLICATION" ->testparm</SPAN -> +> the "path =" line in smb.conf is incorrect. Check it with testparm </P ></LI ><LI @@ -608,22 +391,24 @@ CLASS="COMMAND" > etc. Type <B CLASS="COMMAND" ->help <VAR -CLASS="REPLACEABLE" ->command</VAR -></B +>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 -></LI -><LI +></DIV +><DIV +CLASS="SECT2" +><H2 +CLASS="SECT2" +><A +NAME="AEN3467">26.3.8. Test 8</H2 ><P ->On the PC type the command <KBD -CLASS="USERINPUT" ->net view \\BIGSERVER</KBD +>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 @@ -638,17 +423,11 @@ to choose one of them):</P TYPE="1" ><LI ><P -> fixup the <SPAN -CLASS="APPLICATION" ->nmbd</SPAN -> installation</P +> fixup the nmbd installation</P ></LI ><LI ><P -> add the IP address of BIGSERVER to the <B -CLASS="COMMAND" ->wins server</B -> box in the +> add the IP address of BIGSERVER to the "wins server" box in the advanced tcp/ip setup on the PC.</P ></LI ><LI @@ -663,14 +442,8 @@ CLASS="COMMAND" ></OL ><P >If you get a "invalid network name" or "bad password error" then the -same fixes apply as they did for the <KBD -CLASS="USERINPUT" ->smbclient -L</KBD -> test above. In -particular, make sure your <B -CLASS="COMMAND" ->hosts allow</B -> line is correct (see the man +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 @@ -682,47 +455,27 @@ name and password.</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 <TT -CLASS="FILENAME" ->hosts.allow</TT -> file for your client (or subnet, etc.)</P -></LI -><LI +the hosts.allow file for your client (or subnet, etc.)</P +></DIV +><DIV +CLASS="SECT2" +><H2 +CLASS="SECT2" +><A +NAME="AEN3484">26.3.9. Test 9</H2 ><P ->Run the command <KBD -CLASS="USERINPUT" ->net use x: \\BIGSERVER\TMP</KBD +>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 <B -CLASS="COMMAND" ->hosts allow</B -> -and other config lines in <TT -CLASS="FILENAME" ->smb.conf</TT -> are correct.</P +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 <B -CLASS="COMMAND" ->user = -<VAR -CLASS="REPLACEABLE" ->username</VAR -></B -> to the <B -CLASS="COMMAND" ->[tmp]</B -> section of -<TT -CLASS="FILENAME" ->smb.conf</TT -> where <VAR -CLASS="REPLACEABLE" ->username</VAR -> is the +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 @@ -733,38 +486,39 @@ CLASS="COMMAND" > in <TT CLASS="FILENAME" >smb.conf</TT -> +>. Turn it back on to fix.</P -></LI -><LI +></DIV +><DIV +CLASS="SECT2" +><H2 +CLASS="SECT2" +><A +NAME="AEN3492">26.3.10. Test 10</H2 ><P ->Run the command <KBD -CLASS="USERINPUT" ->nmblookup -M <VAR -CLASS="REPLACEABLE" ->testgroup</VAR -></KBD +>Run the command <B +CLASS="COMMAND" +>nmblookup -M TESTGROUP</B > where -<VAR -CLASS="REPLACEABLE" ->testgroup</VAR -> is the name of the workgroup that your Samba server and +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 <TT -CLASS="FILENAME" ->smb.conf</TT ->. Make +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 -></LI -><LI +></DIV +><DIV +CLASS="SECT2" +><H2 +CLASS="SECT2" +><A +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 @@ -781,16 +535,8 @@ CLASS="COMMAND" CLASS="COMMAND" >password server = Windows_NT_Machine</B > in your -<TT -CLASS="FILENAME" ->smb.conf</TT -> file, or make sure <B -CLASS="COMMAND" ->encrypted passwords</B -> is -set to "yes".</P -></LI -></OL +smb.conf file, or enable encrypted passwords AFTER compiling in support +for encrypted passwords (refer to the Makefile).</P ></DIV ></DIV ><DIV @@ -798,9 +544,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN4907" ->33.4. Still having troubles?</A -></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 @@ -814,8 +558,10 @@ out the samba web page at <A HREF="http://samba.org/samba" TARGET="_top" ->http://samba.org/samba/</A +>http://samba.org/samba</A ></P +><P +>Also look at the other docs in the Samba package!</P ></DIV ></DIV ><DIV diff --git a/docs/htmldocs/domain-security.html b/docs/htmldocs/domain-security.html index ddbc4624b8..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.7"><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="Samba as a ADS domain member" HREF="ads.html"><LINK REL="NEXT" -TITLE="Advanced Configuration" +TITLE="Optional configuration" HREF="optional.html"></HEAD ><BODY CLASS="CHAPTER" @@ -72,58 +73,157 @@ WIDTH="100%"></DIV CLASS="CHAPTER" ><H1 ><A -NAME="DOMAIN-SECURITY" -></A ->Chapter 9. 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="AEN1439" ->9.1. Joining an NT Domain with Samba 3.0</A -></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 - <CODE +>Assume you have a Samba 2.x server with a NetBIOS name of + <TT CLASS="CONSTANT" ->SERV1</CODE -> and are joining an or Win2k NT domain called - <CODE +>SERV1</TT +> and are joining an NT domain called + <TT CLASS="CONSTANT" ->DOM</CODE +>DOM</TT >, which has a PDC with a NetBIOS name - of <CODE + of <TT CLASS="CONSTANT" ->DOMPDC</CODE +>DOMPDC</TT > and two backup domain controllers - with NetBIOS names <CODE + with NetBIOS names <TT CLASS="CONSTANT" ->DOMBDC1</CODE -> and <CODE +>DOMBDC1</TT +> and <TT CLASS="CONSTANT" >DOMBDC2 - </CODE + </TT >.</P ><P ->Firstly, you must edit your <TT +>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" ->smb.conf</TT -> file to tell Samba it should - now use domain security.</P +><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 +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" -> <VAR +> <TT CLASS="PARAMETER" ->security =</VAR +><I +>security =</I +></TT ></A > line in the [global] section - of your <TT -CLASS="FILENAME" ->smb.conf</TT -> to read:</P + of your smb.conf to read:</P ><P ><B CLASS="COMMAND" @@ -133,9 +233,11 @@ CLASS="COMMAND" >Next change the <A HREF="smb.conf.5.html#WORKGROUP" TARGET="_top" -><VAR +><TT CLASS="PARAMETER" -> workgroup =</VAR +><I +> workgroup =</I +></TT ></A > line in the [global] section to read: </P ><P @@ -149,22 +251,26 @@ CLASS="COMMAND" >You must also have the parameter <A HREF="smb.conf.5.html#ENCRYPTPASSWORDS" TARGET="_top" -> <VAR +> <TT CLASS="PARAMETER" ->encrypt passwords</VAR +><I +>encrypt passwords</I +></TT ></A -> set to <CODE +> set to <TT CLASS="CONSTANT" >yes - </CODE + </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" -> <VAR +> <TT CLASS="PARAMETER" ->password server =</VAR +><I +>password server =</I +></TT ></A > line in the [global] section to read: </P @@ -189,89 +295,50 @@ 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 -><SAMP -CLASS="PROMPT" ->root# </SAMP -><KBD -CLASS="USERINPUT" ->net rpc join -S DOMPDC - -U<VAR -CLASS="REPLACEABLE" ->Administrator%password</VAR -></KBD -></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 <VAR -CLASS="REPLACEABLE" ->Administrator%password</VAR -> 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 -><SAMP -CLASS="COMPUTEROUTPUT" ->Joined domain DOM.</SAMP -> - or <SAMP -CLASS="COMPUTEROUTPUT" ->Joined 'SERV1' to realm 'MYREALM'</SAMP -> - </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 +>Finally, restart your Samba daemons and get ready for + clients to begin using domain security!</P +></DIV +><DIV +CLASS="SECT1" +><H1 +CLASS="SECT1" +><A +NAME="AEN1337">9.2. Samba and Windows 2000 Domains</H1 ><P -><TT -CLASS="FILENAME" ->/usr/local/samba/private/secrets.tdb</TT -></P +>Many people have asked regarding the state of Samba's ability to participate in +a Windows 2000 Domain. Samba 3.0 is able to act as a member server of a Windows +2000 domain operating in mixed or native mode.</P ><P ->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 +>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 ->Finally, restart your Samba daemons and get ready for - clients to begin using domain security!</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="AEN1493" ->9.2. Why is this better than security = server?</A -></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 - to your server. This means that if domain user <CODE + to your server. This means that if domain user <TT CLASS="CONSTANT" >DOM\fred - </CODE + </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 @@ -320,28 +387,20 @@ 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 -><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" + 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" +><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" @@ -354,10 +413,6 @@ TARGET="_top" >Doing the NIS/NT Samba</A >.</P -></TD -></TR -></TABLE -></DIV ></DIV ></DIV ><DIV @@ -418,7 +473,7 @@ ACCESSKEY="U" WIDTH="33%" ALIGN="right" VALIGN="top" ->Advanced Configuration</TD +>Optional configuration</TD ></TR ></TABLE ></DIV diff --git a/docs/htmldocs/findsmb.1.html b/docs/htmldocs/findsmb.1.html index bc0aec55c0..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.7"></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,16 +97,17 @@ 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 <CODE + will be called with <TT CLASS="CONSTANT" ->-B</CODE +>-B</TT > option.</P ></DD ><DT @@ -124,24 +119,17 @@ 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 <CODE + <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</CODE +>-B</TT > option.</P ></DD ></DL @@ -150,7 +138,7 @@ CLASS="CONSTANT" ><DIV CLASS="REFSECT1" ><A -NAME="AEN50" +NAME="AEN41" ></A ><H2 >EXAMPLES</H2 @@ -174,27 +162,27 @@ CLASS="COMMAND" not show any information about the operating system or server version.</P ><P ->The command with <CODE +>The command with <TT CLASS="CONSTANT" ->-r</CODE +>-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 > is running on the system, you will only get the IP address and the DNS name of the machine. To get proper responses from Windows 95 and Windows 98 machines, - the command must be run as root and with <CODE + the command must be run as root and with <TT CLASS="CONSTANT" ->-r</CODE +>-r</TT > option on a machine without <B CLASS="COMMAND" @@ -204,14 +192,22 @@ CLASS="COMMAND" >For example, running <B CLASS="COMMAND" >findsmb</B -> - without <CODE +> without + <TT CLASS="CONSTANT" ->-r</CODE +>-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 95a1ce107f..84cf521fc9 100644 --- a/docs/htmldocs/groupmapping.html +++ b/docs/htmldocs/groupmapping.html @@ -2,22 +2,23 @@ <HTML ><HEAD ><TITLE ->Configuring Group Mapping</TITLE +>Group mapping HOWTO</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><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="Advanced Configuration" +TITLE="Optional configuration" HREF="optional.html"><LINK REL="PREVIOUS" -TITLE="UNIX Permission Bits and Windows NT Access Control Lists" -HREF="unix-permissions.html"><LINK +TITLE="HOWTO Access Samba source code via CVS" +HREF="cvs-access.html"><LINK REL="NEXT" -TITLE="Printing Support" -HREF="printing.html"></HEAD +TITLE="Samba performance issues" +HREF="speed.html"></HEAD ><BODY CLASS="CHAPTER" BGCOLOR="#FFFFFF" @@ -45,7 +46,7 @@ WIDTH="10%" ALIGN="left" VALIGN="bottom" ><A -HREF="unix-permissions.html" +HREF="cvs-access.html" ACCESSKEY="P" >Prev</A ></TD @@ -59,7 +60,7 @@ WIDTH="10%" ALIGN="right" VALIGN="bottom" ><A -HREF="printing.html" +HREF="speed.html" ACCESSKEY="N" >Next</A ></TD @@ -72,16 +73,14 @@ WIDTH="100%"></DIV CLASS="CHAPTER" ><H1 ><A -NAME="GROUPMAPPING" -></A ->Chapter 11. Configuring Group Mapping</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 current method (likely to change) to manage the groups is a new command called -<SPAN -CLASS="APPLICATION" ->smbgroupedit</SPAN +<B +CLASS="COMMAND" +>smbgroupedit</B >.</P ><P >The first immediate reason to use the group mapping on a PDC, is that @@ -142,9 +141,9 @@ CLASS="COMMAND" >domain admins</B > group by running the command:</P ><P -><KBD -CLASS="USERINPUT" ->smbgroupedit -c "Domain Admins" -u domadm</KBD +><B +CLASS="COMMAND" +>smbgroupedit -c "Domain Admins" -u domadm</B ></P ></LI ></OL @@ -157,16 +156,16 @@ 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 -><KBD -CLASS="USERINPUT" ->smbgroupedit -a unixgroup -td</KBD +><B +CLASS="COMMAND" +>smbgroupedit -a unixgroup -td</B ></P ><P >You can list the various groups in the mapping database like this</P ><P -><KBD -CLASS="USERINPUT" ->smbgroupedit -v</KBD +><B +CLASS="COMMAND" +>smbgroupedit -v</B ></P ></DIV ><DIV @@ -185,7 +184,7 @@ WIDTH="33%" ALIGN="left" VALIGN="top" ><A -HREF="unix-permissions.html" +HREF="cvs-access.html" ACCESSKEY="P" >Prev</A ></TD @@ -203,7 +202,7 @@ WIDTH="33%" ALIGN="right" VALIGN="top" ><A -HREF="printing.html" +HREF="speed.html" ACCESSKEY="N" >Next</A ></TD @@ -213,7 +212,7 @@ ACCESSKEY="N" WIDTH="33%" ALIGN="left" VALIGN="top" ->UNIX Permission Bits and Windows NT Access Control Lists</TD +>HOWTO Access Samba source code via CVS</TD ><TD WIDTH="34%" ALIGN="center" @@ -227,7 +226,7 @@ ACCESSKEY="U" WIDTH="33%" ALIGN="right" VALIGN="top" ->Printing Support</TD +>Samba performance issues</TD ></TR ></TABLE ></DIV diff --git a/docs/htmldocs/groupprofiles.html b/docs/htmldocs/groupprofiles.html deleted file mode 100644 index 9c25717238..0000000000 --- a/docs/htmldocs/groupprofiles.html +++ /dev/null @@ -1,568 +0,0 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> -<HTML -><HEAD -><TITLE ->Creating Group Prolicy Files</TITLE -><META -NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><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="Securing Samba" -HREF="securing-samba.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="securing-samba.html" -ACCESSKEY="N" ->Next</A -></TD -></TR -></TABLE -><HR -ALIGN="LEFT" -WIDTH="100%"></DIV -><DIV -CLASS="CHAPTER" -><H1 -><A -NAME="GROUPPROFILES" -></A ->Chapter 21. Creating Group Prolicy Files</H1 -><DIV -CLASS="SECT1" -><H1 -CLASS="SECT1" -><A -NAME="AEN3410" ->21.1. Windows '9x</A -></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 -Win9x/Me 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 Win9x/Me 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 Win9x/Me machine. Hence, you will -occasionally notice things changing back to the original settings.</P -><P ->The following all refers to Windows NT/200x profile migration - not to policies. -We need a separate section on policies (NTConfig.Pol) for NT4/200x.</P -></DIV -><DIV -CLASS="SECT1" -><H1 -CLASS="SECT1" -><A -NAME="AEN3420" ->21.2. Windows NT 4</A -></H1 -><P ->Unfortunately, the Resource Kit info is Win NT4 or 200x 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="AEN3443" ->21.2.1. Side bar Notes</A -></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="AEN3447" ->21.2.2. Mandatory profiles</A -></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="AEN3450" ->21.2.3. moveuser.exe</A -></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="AEN3453" ->21.2.4. Get SID</A -></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="AEN3458" ->21.3. Windows 2000/XP</A -></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="securing-samba.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" ->Securing Samba</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 3817bbece8..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.7"><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="Advanced Configuration" -HREF="optional.html"><LINK +TITLE="General installation" +HREF="introduction.html"><LINK REL="PREVIOUS" -TITLE="Integrating MS Windows networks with Samba" -HREF="integrate-ms-networks.html"><LINK +TITLE="How to Install and Test SAMBA" +HREF="install.html"><LINK REL="NEXT" -TITLE="Securing Samba" -HREF="securing-samba.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="integrate-ms-networks.html" +HREF="install.html" ACCESSKEY="P" >Prev</A ></TD @@ -59,7 +60,7 @@ WIDTH="10%" ALIGN="right" VALIGN="bottom" ><A -HREF="securing-samba.html" +HREF="browsing-quick.html" ACCESSKEY="N" >Next</A ></TD @@ -72,23 +73,16 @@ WIDTH="100%"></DIV CLASS="CHAPTER" ><H1 ><A -NAME="IMPROVED-BROWSING" -></A ->Chapter 23. Improved browsing in samba</H1 +NAME="IMPROVED-BROWSING">Chapter 2. Improved browsing in samba</H1 ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3804" ->23.1. Overview of browsing</A -></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 <B -CLASS="COMMAND" ->browse list</B ->. This 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 @@ -96,13 +90,8 @@ list is heavily used by all SMB clients. Configuration of SMB browsing has been problematic for some Samba users, hence this document.</P ><P ->MS Windows 2000 and later, as with Samba 3 and later, can be -configured to not use NetBIOS over TCP/IP. When configured this way -it is imperative that name resolution (using DNS/LDAP/ADS) be correctly -configured and operative. Browsing will NOT work if name resolution -from SMB machine names to IP addresses does not function correctly.</P -><P ->Where NetBIOS over TCP/IP is enabled use of a WINS server is highly +>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 @@ -112,20 +101,14 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3810" ->23.2. Browsing support in samba</A -></H1 -><P ->Samba facilitates browsing. The browsing is supported by <SPAN -CLASS="APPLICATION" ->nmbd</SPAN -> -and is also controlled by options in the <TT -CLASS="FILENAME" ->smb.conf</TT -> file. -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.</P +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 +><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 @@ -138,123 +121,64 @@ 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 -><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 ->Nmbd can be configured as a WINS server, but it is not -necessary to specifically use samba as your WINS server. MS Windows -NT4, Server or Advanced Server 2000 or 2003 can be configured as -your WINS server. In a mixed NT/2000/2003 server and samba environment on -a Wide Area Network, it is recommended that you use the Microsoft -WINS server capabilities. In a samba-only environment, it is -recommended that you use one and only one Samba server as your WINS server.</P -></TD -></TR -></TABLE -></DIV +>[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 <B -CLASS="COMMAND" ->workgroup</B -> option in <TT -CLASS="FILENAME" ->smb.conf</TT -> -to control what workgroup Samba becomes a part of.</P +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 <B -CLASS="COMMAND" ->remote announce</B -> in the -<TT -CLASS="FILENAME" ->smb.conf</TT -> man page. </P +example. See "remote announce" in the smb.conf man page. </P ></DIV ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3825" ->23.3. Problem resolution</A -></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 problems. Also note that the current browse list usually gets stored -in text form in a file called <TT -CLASS="FILENAME" ->browse.dat</TT ->.</P +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 <TT -CLASS="FILENAME" ->\\SERVER</TT -> in filemanager then -hit enter and filemanager should display the list of available shares.</P +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 -<B -CLASS="COMMAND" ->guest account</B -> set to a valid account. Remember that the -IPC$ connection that lists the shares is done as guest, and thus you must +"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 -><SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->MS Windows 2000 and upwards (as with Samba) can be configured to disallow -anonymous (ie: Guest account) access to the IPC$ share. In that case, the -MS Windows 2000/XP/2003 machine acting as an SMB/CIFS client will use the -name of the currently logged in user to query the IPC$ share. MS Windows -9X clients are not able to do this and thus will NOT be able to browse -server resources.</I -></SPAN -></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 <TT -CLASS="FILENAME" ->smb.conf</TT ->)</P +in smb.conf)</P ></DIV ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3837" ->23.4. Browsing across subnets</A -></H1 +NAME="AEN249">2.4. Browsing across subnets</H1 ><P ->Since the release of Samba 1.9.17(alpha1) Samba has been +>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 @@ -275,23 +199,19 @@ another subnet without using a WINS server.</P 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 <TT -CLASS="FILENAME" ->smb.conf</TT -> file.</P +settings) for Samba this is in the smb.conf file.</P ><DIV CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3843" ->23.4.1. How does cross subnet browsing work ?</A -></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 that achieves this correct, and Samba lags behind in some areas. -Samba is capable of cross subnet browsing when configured correctly.</P +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 @@ -372,7 +292,7 @@ machine is seen across any of the subnets.</P 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 +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 @@ -495,16 +415,11 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3878" ->23.5. Setting up a WINS server</A -></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 -add the following option to the <TT -CLASS="FILENAME" ->smb.conf</TT -> file on the selected machine : +add the following option to the smb.conf file on the selected machine : in the [globals] section add the line </P ><P ><B @@ -512,22 +427,22 @@ CLASS="COMMAND" > wins support = yes</B ></P ><P ->Versions of Samba prior to 1.9.17 had this parameter default to +>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 a recent version, or at the very +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 +>Machines with "<B CLASS="COMMAND" >wins support = yes</B -> will keep a list of +>" 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 +"<B CLASS="COMMAND" >wins support = yes</B -> option on more than one Samba +>" 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 @@ -538,11 +453,8 @@ 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 -<B -CLASS="COMMAND" ->wins support = yes</B -> parameter set.</P +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 @@ -551,32 +463,26 @@ 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 <TT -CLASS="FILENAME" ->smb.conf</TT -> files :</P +all smb.conf files :</P ><P ><B CLASS="COMMAND" ->wins server = >name or IP address<</B +>wins server = >name or IP address<</B ></P ><P ->where >name or IP address< is either the DNS name of the WINS server +>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 <TT -CLASS="FILENAME" ->smb.conf</TT -> file of the Samba +>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 +"<B CLASS="COMMAND" >wins support = yes</B -> option and the -<B +>" option and the +"<B CLASS="COMMAND" ->wins server = <name></B -> option then +>wins server = >name<</B +>" option then nmbd will fail to start.</P ><P >There are two possible scenarios for setting up cross subnet browsing. @@ -590,9 +496,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3901" ->23.6. Setting up Browsing in a WORKGROUP</A -></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 @@ -609,10 +513,7 @@ cross subnet browsing possible for a workgroup.</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 <TT -CLASS="FILENAME" ->smb.conf</TT -> file :</P +set the following option in the [global] section of the smb.conf file :</P ><P ><B CLASS="COMMAND" @@ -621,17 +522,14 @@ CLASS="COMMAND" ><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 <TT -CLASS="FILENAME" ->smb.conf</TT -> file :</P +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 +> 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 @@ -639,60 +537,40 @@ 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 MS Windows NT/2K/XP/2003 machine should be -able to do this, as will Windows 9x 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 -<TT -CLASS="FILENAME" ->smb.conf</TT -> file :</P +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 +> 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 <B -CLASS="COMMAND" ->local master</B -> parameter allows Samba to act as a -local master browser. The <B -CLASS="COMMAND" ->preferred master</B -> causes nmbd -to force a browser election on startup and the <B -CLASS="COMMAND" ->os level</B -> -parameter sets Samba high enough so that it should win any browser elections.</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 <B -CLASS="COMMAND" ->[global]</B -> section of the -<TT -CLASS="FILENAME" ->smb.conf</TT -> file :</P +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 +> domain master = no + local master = no + preferred master = no + os level = 0</PRE ></P ></DIV ><DIV @@ -700,66 +578,41 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3927" ->23.7. Setting up Browsing in a DOMAIN</A -></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. 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 (<VAR -CLASS="REPLACEABLE" ->DOMAIN</VAR -><1B>) -with WINS instead of the PDC.</P +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 <B -CLASS="COMMAND" ->[global]</B -> section -of the <TT -CLASS="FILENAME" ->smb.conf</TT -> file :</P +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 +> 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 <B -CLASS="COMMAND" ->os level</B -> parameter -to lower levels. By doing this you can tune the order of machines that +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 <A -HREF="improved-browsing.html#BROWSE-FORCE-MASTER" ->Forcing samba to be the master browser</A -> +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 <B -CLASS="COMMAND" ->[global]</B -> section of the <TT -CLASS="FILENAME" ->smb.conf</TT -> -file :</P +in the [global] section of the smb.conf file :</P ><P ><B CLASS="COMMAND" @@ -774,64 +627,35 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="BROWSE-FORCE-MASTER" ->23.8. Forcing samba to be the master</A -></H1 +NAME="AEN336">2.8. Forcing samba to be the master</H1 ><P ->Who becomes the <B -CLASS="COMMAND" ->master browser</B -> is determined by an election -process using broadcasts. Each election packet contains a number of parameters +>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 <B -CLASS="COMMAND" ->os level</B -> global -option in <TT -CLASS="FILENAME" ->smb.conf</TT -> to a higher number. It defaults to 0. Using 34 +>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 <B -CLASS="COMMAND" ->os level</B -> of 2 would make it beat WfWg and Win95, but not MS Windows -NT/2K Server. A MS Windows NT/2K Server domain controller uses level 32.</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 -<B -CLASS="COMMAND" ->preferred master</B -> global option in <TT -CLASS="FILENAME" ->smb.conf</TT -> to "yes". Samba will +"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 <B -CLASS="COMMAND" ->preferred master</B -> to +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 <B -CLASS="COMMAND" ->domain master browser</B ->, then it is -recommended that you also set <B -CLASS="COMMAND" ->preferred master</B -> to "yes", because +>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 @@ -849,20 +673,12 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3962" ->23.9. Making samba the domain master</A -></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 -make samba act as the domain master by setting <B -CLASS="COMMAND" ->domain master = yes</B -> -in <TT -CLASS="FILENAME" ->smb.conf</TT ->. By default it will not be a domain master.</P +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 @@ -873,14 +689,8 @@ 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 <B -CLASS="COMMAND" ->os level</B -> high enough to make sure it wins elections, and set -<B -CLASS="COMMAND" ->preferred master</B -> to "yes", to get samba to force an election on +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 @@ -934,9 +744,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3984" ->23.10. Note about broadcast addresses</A -></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 @@ -948,19 +756,11 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3987" ->23.11. Multiple interfaces</A -></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 <B -CLASS="COMMAND" ->interfaces</B -> -option in <TT -CLASS="FILENAME" ->smb.conf</TT -> to configure them. </P +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 @@ -979,7 +779,7 @@ WIDTH="33%" ALIGN="left" VALIGN="top" ><A -HREF="integrate-ms-networks.html" +HREF="install.html" ACCESSKEY="P" >Prev</A ></TD @@ -997,7 +797,7 @@ WIDTH="33%" ALIGN="right" VALIGN="top" ><A -HREF="securing-samba.html" +HREF="browsing-quick.html" ACCESSKEY="N" >Next</A ></TD @@ -1007,13 +807,13 @@ ACCESSKEY="N" WIDTH="33%" ALIGN="left" VALIGN="top" ->Integrating MS Windows networks with Samba</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 @@ -1021,7 +821,7 @@ ACCESSKEY="U" WIDTH="33%" ALIGN="right" VALIGN="top" ->Securing Samba</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 cc2674ea1c..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.7"><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,65 +73,165 @@ 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="AEN65" ->1.1. Obtaining and installing samba</A -></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. + If you don't know how to read man pages then try + something like:</P ><P ->Binary packages of samba are included in almost any Linux or - Unix distribution. There are also some packages available at - <A -HREF="http://samba.org/" +><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" ->the samba homepage</A ->. - </P -><P ->If you need to compile samba from source, check the - <A -HREF="compiling.html" ->appropriate appendix chapter</A ->.</P +> http://www.samba.org</A +></P ></DIV ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN71" ->1.2. Configuring samba</A -></H1 +NAME="AEN36">1.2. Building the Binaries</H1 ><P ->Samba's configuration is stored in the smb.conf file, - that usually resides in <TT -CLASS="FILENAME" ->/etc/samba/smb.conf</TT -> - or <TT -CLASS="FILENAME" ->/usr/local/samba/lib/smb.conf</TT ->. You can either - edit this file yourself or do it using one of the many graphical - tools that are available, such as the web-based interface swat, that - is included with samba.</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="SECT2" -><H2 -CLASS="SECT2" +CLASS="SECT1" +><H1 +CLASS="SECT1" ><A -NAME="AEN76" ->1.2.1. Editing the <TT -CLASS="FILENAME" ->smb.conf</TT -> file</A -></H2 +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 + 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" +><H1 +CLASS="SECT1" +><A +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 @@ -142,27 +243,31 @@ CLASS="FILENAME" ><P ><PRE CLASS="PROGRAMLISTING" ->[global] - workgroup = MYGROUP +> [global] + workgroup = MYGROUP -[homes] - guest ok = no - read only = no + [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 - "<B -CLASS="COMMAND" ->homes</B ->" as the service name. (Note that I also set the + "homes" as the service name. (Note that I also set the workgroup that Samba is part of. See BROWSING.txt for details)</P ><P ->Make sure you put the <TT +>Note that <B +CLASS="COMMAND" +>make install</B +> will not install + a <TT CLASS="FILENAME" >smb.conf</TT -> file in the same place +> 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 @@ -173,35 +278,24 @@ CLASS="FILENAME" >).</P ><P >For more information about security settings for the - <B -CLASS="COMMAND" ->[homes]</B -> share please refer to the chapter - <A -HREF="securing-samba.html" ->Securing Samba</A ->.</P + [homes] share please refer to the document UNIX_SECURITY.txt.</P +></DIV ><DIV -CLASS="SECT3" -><H3 -CLASS="SECT3" +CLASS="SECT1" +><H1 +CLASS="SECT1" ><A -NAME="AEN92" ->1.2.1.1. Test your config file with +NAME="AEN82">1.5. Test your config file with <B CLASS="COMMAND" >testparm</B -></A -></H3 +></H1 ><P >It's important that you test the validity of your <TT CLASS="FILENAME" >smb.conf</TT -> file using the <SPAN -CLASS="APPLICATION" ->testparm</SPAN -> program. +> 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 @@ -214,33 +308,199 @@ CLASS="FILENAME" >smb.conf</TT >!</P ></DIV +><DIV +CLASS="SECT1" +><H1 +CLASS="SECT1" +><A +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 +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" +><H2 +CLASS="SECT2" +><A +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 +><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" ><H2 CLASS="SECT2" ><A -NAME="AEN101" ->1.2.2. SWAT</A -></H2 -><P -> SWAT is a web-based interface that helps you configure samba. - SWAT might not be available in the samba package on your platform, - but in a seperate package. Please read the swat manpage - on compiling, installing and configuring swat from source. - </P -><P ->To launch SWAT just run your favorite web browser and - point it at "http://localhost:901/". Replace <VAR -CLASS="REPLACEABLE" ->localhost</VAR -> with the name of the computer you are running samba on if you - are running samba on a different computer then your browser.</P -><P ->Note that you can attach to SWAT from any IP connected - machine but connecting from a remote machine leaves your - connection open to password sniffing as passwords will be sent - in the clear over the wire. </P +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 + 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 @@ -248,21 +508,23 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN107" ->1.3. Try listing the shares available on your - server</A -></H1 +NAME="AEN145">1.7. Try listing the shares available on your + server</H1 ><P -><SAMP +><TT CLASS="PROMPT" ->$ </SAMP -><KBD +>$ </TT +><TT CLASS="USERINPUT" +><B >smbclient -L - <VAR + <TT CLASS="REPLACEABLE" ->yourhostname</VAR -></KBD +><I +>yourhostname</I +></TT +></B +></TT ></P ><P >You should get back a list of shares available on @@ -285,69 +547,60 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN116" ->1.4. Try connecting with the unix client</A -></H1 +NAME="AEN154">1.8. Try connecting with the unix client</H1 ><P -><SAMP +><TT CLASS="PROMPT" ->$ </SAMP -><KBD +>$ </TT +><TT CLASS="USERINPUT" ->smbclient <VAR +><B +>smbclient <TT CLASS="REPLACEABLE" -> //yourhostname/aservice</VAR -></KBD +><I +> //yourhostname/aservice</I +></TT +></B +></TT ></P ><P ->Typically the <VAR +>Typically the <TT CLASS="REPLACEABLE" ->yourhostname</VAR +><I +>yourhostname</I +></TT > - would be the name of the host where you installed <SPAN -CLASS="APPLICATION" ->smbd</SPAN ->. - The <VAR + would be the name of the host where you installed <B +CLASS="COMMAND" +> smbd</B +>. The <TT CLASS="REPLACEABLE" ->aservice</VAR +><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 <B -CLASS="COMMAND" ->[homes]</B -> - section +> + 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 <VAR -CLASS="REPLACEABLE" ->bambi</VAR -> - and your login name is <VAR -CLASS="REPLACEABLE" ->fred</VAR -> you would type:</P +>For example if your unix host is bambi and your login + name is fred you would type:</P ><P -><SAMP +><TT CLASS="PROMPT" ->$ </SAMP -><KBD +>$ </TT +><TT CLASS="USERINPUT" ->smbclient //<VAR -CLASS="REPLACEABLE" ->bambi</VAR ->/<VAR -CLASS="REPLACEABLE" ->fred</VAR -> - </KBD +><B +>smbclient //bambi/fred + </B +></TT ></P ></DIV ><DIV @@ -355,86 +608,96 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN137" ->1.5. Try connecting from a DOS, WfWg, Win9x, WinNT, - Win2k, OS/2, etc... client</A -></H1 +NAME="AEN170">1.9. Try connecting from a DOS, WfWg, Win9x, WinNT, + Win2k, OS/2, etc... client</H1 ><P >Try mounting disks. eg:</P ><P -><SAMP +><TT CLASS="PROMPT" ->C:\WINDOWS\> </SAMP -><KBD +>C:\WINDOWS\> </TT +><TT CLASS="USERINPUT" +><B >net use d: \\servername\service - </KBD + </B +></TT ></P ><P >Try printing. eg:</P ><P -><SAMP +><TT CLASS="PROMPT" ->C:\WINDOWS\> </SAMP -><KBD +>C:\WINDOWS\> </TT +><TT CLASS="USERINPUT" +><B >net use lpt1: - \\servername\spoolservice</KBD + \\servername\spoolservice</B +></TT ></P ><P -><SAMP +><TT CLASS="PROMPT" ->C:\WINDOWS\> </SAMP -><KBD +>C:\WINDOWS\> </TT +><TT CLASS="USERINPUT" +><B >print filename - </KBD + </B +></TT ></P +><P +>Celebrate, or send me a bug report!</P ></DIV ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN150" ->1.6. What If Things Don't Work?</A -></H1 +NAME="AEN184">1.10. What If Things Don't Work?</H1 ><P ->Then you might read the file chapter - <A -HREF="diagnosis.html" ->Diagnosis</A -> and the +>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 <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->please</I -></SPAN -> send some - updates of the documentation (or source code) to one of - the documentation maintainers or the list. - </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" +><H2 +CLASS="SECT2" +><A +NAME="AEN189">1.10.1. Diagnosing Problems</H2 +><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" ><H2 CLASS="SECT2" ><A -NAME="AEN156" ->1.6.1. Scope IDs</A -></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. 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 + All your PCs will need to have the same setting for this to work. I do not recommend scope IDs.</P ></DIV ><DIV @@ -442,9 +705,65 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN159" ->1.6.2. Locking</A -></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, + 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" +><H2 +CLASS="SECT2" +><A +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 + 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" +><H2 +CLASS="SECT2" +><A +NAME="AEN210">1.10.5. Locking</H2 ><P >One area which sometimes causes trouble is locking.</P ><P @@ -497,6 +816,17 @@ NAME="AEN159" or DENY_ALL. There are also special compatibility modes called DENY_FCB and DENY_DOS.</P ></DIV +><DIV +CLASS="SECT2" +><H2 +CLASS="SECT2" +><A +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. + See the smb.conf man page for details.</P +></DIV ></DIV ></DIV ><DIV @@ -533,7 +863,7 @@ WIDTH="33%" ALIGN="right" VALIGN="top" ><A -HREF="browsing-quick.html" +HREF="improved-browsing.html" ACCESSKEY="N" >Next</A ></TD @@ -557,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 5d9e1cdaec..ad6aa9e225 100644 --- a/docs/htmldocs/integrate-ms-networks.html +++ b/docs/htmldocs/integrate-ms-networks.html @@ -5,19 +5,20 @@ >Integrating MS Windows networks with Samba</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><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="Advanced Configuration" +TITLE="Optional configuration" HREF="optional.html"><LINK REL="PREVIOUS" -TITLE="Hosting a Microsoft Distributed File System tree on Samba" -HREF="msdfs.html"><LINK +TITLE="Optional configuration" +HREF="optional.html"><LINK REL="NEXT" -TITLE="Improved browsing in samba" -HREF="improved-browsing.html"></HEAD +TITLE="UNIX Permission Bits and Windows NT Access Control Lists" +HREF="unix-permissions.html"></HEAD ><BODY CLASS="CHAPTER" BGCOLOR="#FFFFFF" @@ -45,7 +46,7 @@ WIDTH="10%" ALIGN="left" VALIGN="bottom" ><A -HREF="msdfs.html" +HREF="optional.html" ACCESSKEY="P" >Prev</A ></TD @@ -59,7 +60,7 @@ WIDTH="10%" ALIGN="right" VALIGN="bottom" ><A -HREF="improved-browsing.html" +HREF="unix-permissions.html" ACCESSKEY="N" >Next</A ></TD @@ -72,92 +73,78 @@ WIDTH="100%"></DIV CLASS="CHAPTER" ><H1 ><A -NAME="INTEGRATE-MS-NETWORKS" -></A ->Chapter 22. Integrating MS Windows networks with Samba</H1 -><P ->This section deals with NetBIOS over TCP/IP name to IP address resolution. If you -your MS Windows clients are NOT configured to use NetBIOS over TCP/IP then this -section does not apply to your installation. If your installation involves use of -NetBIOS over TCP/IP then this section may help you to resolve networking problems.</P +NAME="INTEGRATE-MS-NETWORKS">Chapter 10. Integrating MS Windows networks with Samba</H1 ><DIV -CLASS="NOTE" +CLASS="SECT1" +><H1 +CLASS="SECT1" +><A +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 +replacing MS Windows NT/2000 technology.</P +><P +>We will examine:</P ><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" +><OL +TYPE="1" +><LI ><P -> NetBIOS over TCP/IP has nothing to do with NetBEUI. NetBEUI is NetBIOS - over Logical Link Control (LLC). On modern networks it is highly advised - to NOT run NetBEUI at all. Note also that there is NO such thing as - NetBEUI over TCP/IP - the existence of such a protocol is a complete - and utter mis-apprehension.</P -></TD -></TR -></TABLE -></DIV +>Name resolution in a pure Unix/Linux TCP/IP + environment + </P +></LI +><LI ><P ->Since the introduction of MS Windows 2000 it is possible to run MS Windows networking -without the use of NetBIOS over TCP/IP. NetBIOS over TCP/IP uses UDP port 137 for NetBIOS -name resolution and uses TCP port 139 for NetBIOS session services. When NetBIOS over -TCP/IP is disabled on MS Windows 2000 and later clients then only TCP port 445 will be -used and UDP port 137 and TCP port 139 will not.</P -><DIV -CLASS="NOTE" +>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 -><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" +><OL +TYPE="a" +><LI ><P ->When using Windows 2000 or later clients, if NetBIOS over TCP/IP is NOT disabled, then -the client will use UDP port 137 (NetBIOS Name Service, also known as the Windows Internet -Name Service or WINS), TCP port 139 AND TCP port 445 (for actual file and print traffic).</P -></TD -></TR -></TABLE -></DIV +>A stand-alone server</P +></LI +><LI +><P +>An MS Windows NT 3.x/4.0 security domain member + </P +></LI +><LI ><P ->When NetBIOS over TCP/IP is disabled the use of DNS is essential. Most installations that -disable NetBIOS over TCP/IP today use MS Active Directory Service (ADS). ADS requires -Dynamic DNS with Service Resource Records (SRV RR) and with Incremental Zone Transfers (IXFR). -Use of DHCP with ADS is recommended as a further means of maintaining central control -over client workstation network configuration.</P +>An alternative to an MS Windows NT 3.x/4.0 Domain Controller + </P +></LI +></OL +></LI +></OL +></DIV ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3688" ->22.1. Name Resolution in a pure Unix/Linux world</A -></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 @@ -197,11 +184,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3704" ->22.1.1. <TT +NAME="AEN1412">10.2.1. <TT CLASS="FILENAME" >/etc/hosts</TT -></A ></H2 ><P >Contains a static list of IP Addresses and names. @@ -278,11 +263,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3720" ->22.1.2. <TT +NAME="AEN1428">10.2.2. <TT CLASS="FILENAME" >/etc/resolv.conf</TT -></A ></H2 ><P >This file tells the name resolution libraries:</P @@ -316,11 +299,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3731" ->22.1.3. <TT +NAME="AEN1439">10.2.3. <TT CLASS="FILENAME" >/etc/host.conf</TT -></A ></H2 ><P ><TT @@ -345,11 +326,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3739" ->22.1.4. <TT +NAME="AEN1447">10.2.4. <TT CLASS="FILENAME" >/etc/nsswitch.conf</TT -></A ></H2 ><P >This file controls the actual name resolution targets. The @@ -414,9 +393,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3751" ->22.2. Name resolution as used within MS Windows networking</A -></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 @@ -499,9 +476,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3763" ->22.2.1. The NetBIOS Name Cache</A -></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 @@ -526,9 +501,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3768" ->22.2.2. The LMHOSTS file</A -></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 @@ -563,8 +536,8 @@ CLASS="PROGRAMLISTING" # files and offers the following extensions: # # #PRE - # #DOM:<domain> - # #INCLUDE <filename> + # #DOM:<domain> + # #INCLUDE <filename> # #BEGIN_ALTERNATE # #END_ALTERNATE # \0xnn (non-printing character support) @@ -573,16 +546,16 @@ CLASS="PROGRAMLISTING" # 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 + # 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 + # #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 + # 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. @@ -629,9 +602,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3776" ->22.2.3. HOSTS file</A -></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 @@ -651,9 +622,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3781" ->22.2.4. DNS Lookup</A -></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 @@ -671,9 +640,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3784" ->22.2.5. WINS Lookup</A -></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 @@ -692,10 +659,7 @@ CLASS="PROGRAMLISTING" ></P ><P >To configure Samba to use a WINS server the following parameters are -needed in the <TT -CLASS="FILENAME" ->smb.conf</TT -> file:</P +needed in the smb.conf file:</P ><P ><PRE CLASS="PROGRAMLISTING" @@ -703,13 +667,419 @@ CLASS="PROGRAMLISTING" wins server = xxx.xxx.xxx.xxx</PRE ></P ><P ->where <VAR +>where <TT CLASS="REPLACEABLE" ->xxx.xxx.xxx.xxx</VAR +><I +>xxx.xxx.xxx.xxx</I +></TT > is the IP address of the WINS server.</P ></DIV ></DIV +><DIV +CLASS="SECT1" +><H1 +CLASS="SECT1" +><A +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 +(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" +><H1 +CLASS="SECT1" +><A +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 +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" +><H2 +CLASS="SECT2" +><A +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 +><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" +><H2 +CLASS="SECT2" +><A +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 +><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" +><H2 +CLASS="SECT2" +><A +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 +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" +><H3 +CLASS="SECT3" +><A +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 +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" +><H3 +CLASS="SECT3" +><A +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 +><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" +><H1 +CLASS="SECT1" +><A +NAME="AEN1584">10.6. Conclusions</H1 +><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="NAVFOOTER" @@ -727,7 +1097,7 @@ WIDTH="33%" ALIGN="left" VALIGN="top" ><A -HREF="msdfs.html" +HREF="optional.html" ACCESSKEY="P" >Prev</A ></TD @@ -745,7 +1115,7 @@ WIDTH="33%" ALIGN="right" VALIGN="top" ><A -HREF="improved-browsing.html" +HREF="unix-permissions.html" ACCESSKEY="N" >Next</A ></TD @@ -755,7 +1125,7 @@ ACCESSKEY="N" WIDTH="33%" ALIGN="left" VALIGN="top" ->Hosting a Microsoft Distributed File System tree on Samba</TD +>Optional configuration</TD ><TD WIDTH="34%" ALIGN="center" @@ -769,7 +1139,7 @@ ACCESSKEY="U" WIDTH="33%" ALIGN="right" VALIGN="top" ->Improved browsing in samba</TD +>UNIX Permission Bits and Windows NT Access Control Lists</TD ></TR ></TABLE ></DIV diff --git a/docs/htmldocs/introduction.html b/docs/htmldocs/introduction.html index e16808e8f3..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.7"><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="AEN42" -></A -><H1 +NAME="AEN21"><H1 >Introduction</H1 ><P >This part contains general info on how to install samba @@ -103,253 +100,257 @@ HREF="install.html" ><DL ><DT >1.1. <A -HREF="install.html#AEN65" ->Obtaining and installing samba</A +HREF="install.html#AEN26" +>Read the man pages</A ></DT ><DT >1.2. <A -HREF="install.html#AEN71" ->Configuring samba</A +HREF="install.html#AEN36" +>Building the Binaries</A +></DT +><DT +>1.3. <A +HREF="install.html#AEN64" +>The all important step</A +></DT +><DT +>1.4. <A +HREF="install.html#AEN68" +>Create the smb configuration file.</A +></DT +><DT +>1.5. <A +HREF="install.html#AEN82" +>Test your config file with + <B +CLASS="COMMAND" +>testparm</B +></A +></DT +><DT +>1.6. <A +HREF="install.html#AEN90" +>Starting the smbd and nmbd</A ></DT ><DD ><DL ><DT ->1.2.1. <A -HREF="install.html#AEN76" ->Editing the <TT -CLASS="FILENAME" ->smb.conf</TT -> file</A +>1.6.1. <A +HREF="install.html#AEN100" +>Starting from inetd.conf</A ></DT ><DT ->1.2.2. <A -HREF="install.html#AEN101" ->SWAT</A +>1.6.2. <A +HREF="install.html#AEN129" +>Alternative: starting it as a daemon</A ></DT ></DL ></DD ><DT ->1.3. <A -HREF="install.html#AEN107" +>1.7. <A +HREF="install.html#AEN145" >Try listing the shares available on your server</A ></DT ><DT ->1.4. <A -HREF="install.html#AEN116" +>1.8. <A +HREF="install.html#AEN154" >Try connecting with the unix client</A ></DT ><DT ->1.5. <A -HREF="install.html#AEN137" +>1.9. <A +HREF="install.html#AEN170" >Try connecting from a DOS, WfWg, Win9x, WinNT, Win2k, OS/2, etc... client</A ></DT ><DT ->1.6. <A -HREF="install.html#AEN150" +>1.10. <A +HREF="install.html#AEN184" >What If Things Don't Work?</A ></DT ><DD ><DL ><DT ->1.6.1. <A -HREF="install.html#AEN156" +>1.10.1. <A +HREF="install.html#AEN189" +>Diagnosing Problems</A +></DT +><DT +>1.10.2. <A +HREF="install.html#AEN193" >Scope IDs</A ></DT ><DT ->1.6.2. <A -HREF="install.html#AEN159" +>1.10.3. <A +HREF="install.html#AEN196" +>Choosing the Protocol Level</A +></DT +><DT +>1.10.4. <A +HREF="install.html#AEN205" +>Printing from UNIX to a Client PC</A +></DT +><DT +>1.10.5. <A +HREF="install.html#AEN210" >Locking</A ></DT +><DT +>1.10.6. <A +HREF="install.html#AEN219" +>Mapping Usernames</A +></DT ></DL ></DD ></DL ></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#AEN183" ->Discussion</A +HREF="improved-browsing.html#AEN229" +>Overview of browsing</A ></DT ><DT >2.2. <A -HREF="browsing-quick.html#AEN204" ->How browsing functions and how to deploy stable and -dependable browsing using Samba</A +HREF="improved-browsing.html#AEN233" +>Browsing support in samba</A ></DT ><DT >2.3. <A -HREF="browsing-quick.html#AEN218" ->Use of the <B -CLASS="COMMAND" ->Remote Announce</B -> parameter</A +HREF="improved-browsing.html#AEN242" +>Problem resolution</A ></DT ><DT >2.4. <A -HREF="browsing-quick.html#AEN241" ->Use of the <B -CLASS="COMMAND" ->Remote Browse Sync</B -> parameter</A +HREF="improved-browsing.html#AEN249" +>Browsing across subnets</A ></DT +><DD +><DL +><DT +>2.4.1. <A +HREF="improved-browsing.html#AEN254" +>How does cross subnet browsing work ?</A +></DT +></DL +></DD ><DT >2.5. <A -HREF="browsing-quick.html#AEN252" ->Use of WINS</A +HREF="improved-browsing.html#AEN289" +>Setting up a WINS server</A ></DT ><DT >2.6. <A -HREF="browsing-quick.html#AEN269" ->Do NOT use more than one (1) protocol on MS Windows machines</A +HREF="improved-browsing.html#AEN308" +>Setting up Browsing in a WORKGROUP</A ></DT ><DT >2.7. <A -HREF="browsing-quick.html#AEN277" ->Name Resolution Order</A -></DT -></DL -></DD -><DT ->3. <A -HREF="passdb.html" ->User information database</A +HREF="improved-browsing.html#AEN326" +>Setting up Browsing in a DOMAIN</A ></DT -><DD -><DL ><DT ->3.1. <A -HREF="passdb.html#AEN335" ->Introduction</A +>2.8. <A +HREF="improved-browsing.html#AEN336" +>Forcing samba to be the master</A ></DT ><DT ->3.2. <A -HREF="passdb.html#AEN342" ->Important Notes About Security</A +>2.9. <A +HREF="improved-browsing.html#AEN345" +>Making samba the domain master</A ></DT -><DD -><DL ><DT ->3.2.1. <A -HREF="passdb.html#AEN368" ->Advantages of SMB Encryption</A +>2.10. <A +HREF="improved-browsing.html#AEN363" +>Note about broadcast addresses</A ></DT ><DT ->3.2.2. <A -HREF="passdb.html#AEN374" ->Advantages of non-encrypted passwords</A +>2.11. <A +HREF="improved-browsing.html#AEN366" +>Multiple interfaces</A ></DT ></DL ></DD ><DT ->3.3. <A -HREF="passdb.html#AEN380" ->The smbpasswd Command</A -></DT -><DT ->3.4. <A -HREF="passdb.html#AEN411" ->Plain text</A -></DT -><DT ->3.5. <A -HREF="passdb.html#AEN416" ->TDB</A -></DT -><DT ->3.6. <A -HREF="passdb.html#AEN419" ->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#AEN421" ->Introduction</A -></DT -><DT ->3.6.2. <A -HREF="passdb.html#AEN441" ->Introduction</A -></DT -><DT ->3.6.3. <A -HREF="passdb.html#AEN470" ->Supported LDAP Servers</A -></DT -><DT ->3.6.4. <A -HREF="passdb.html#AEN475" ->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#AEN487" ->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#AEN534" ->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#AEN539" ->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#AEN559" ->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#AEN629" ->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#AEN637" ->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#AEN639" ->Creating the database</A +>4.1. <A +HREF="pwencrypt.html#AEN457" +>Introduction</A ></DT ><DT ->3.7.2. <A -HREF="passdb.html#AEN649" ->Configuring</A +>4.2. <A +HREF="pwencrypt.html#AEN462" +>Important Notes About Security</A ></DT +><DD +><DL ><DT ->3.7.3. <A -HREF="passdb.html#AEN666" ->Using plaintext passwords or encrypted password</A +>4.2.1. <A +HREF="pwencrypt.html#AEN481" +>Advantages of SMB Encryption</A ></DT ><DT ->3.7.4. <A -HREF="passdb.html#AEN671" ->Getting non-column data from the table</A +>4.2.2. <A +HREF="pwencrypt.html#AEN488" +>Advantages of non-encrypted passwords</A ></DT ></DL ></DD ><DT ->3.8. <A -HREF="passdb.html#AEN679" ->XML</A +>4.3. <A +HREF="pwencrypt.html#AEN497" +>The smbpasswd Command</A ></DT ></DL ></DD diff --git a/docs/htmldocs/lmhosts.5.html b/docs/htmldocs/lmhosts.5.html index 375fe5618d..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.7"></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 f05c8012ac..f6fe1c7e1d 100644 --- a/docs/htmldocs/msdfs.html +++ b/docs/htmldocs/msdfs.html @@ -5,19 +5,21 @@ >Hosting a Microsoft Distributed File System tree on Samba</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><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="Advanced Configuration" +TITLE="Optional configuration" HREF="optional.html"><LINK REL="PREVIOUS" -TITLE="Stackable VFS modules" -HREF="vfs.html"><LINK +TITLE="Configuring PAM for distributed but centrally +managed authentication" +HREF="pam.html"><LINK REL="NEXT" -TITLE="Integrating MS Windows networks with Samba" -HREF="integrate-ms-networks.html"></HEAD +TITLE="Printing Support" +HREF="printing.html"></HEAD ><BODY CLASS="CHAPTER" BGCOLOR="#FFFFFF" @@ -45,7 +47,7 @@ WIDTH="10%" ALIGN="left" VALIGN="bottom" ><A -HREF="vfs.html" +HREF="pam.html" ACCESSKEY="P" >Prev</A ></TD @@ -59,7 +61,7 @@ WIDTH="10%" ALIGN="right" VALIGN="bottom" ><A -HREF="integrate-ms-networks.html" +HREF="printing.html" ACCESSKEY="N" >Next</A ></TD @@ -72,17 +74,13 @@ WIDTH="100%"></DIV CLASS="CHAPTER" ><H1 ><A -NAME="MSDFS" -></A ->Chapter 21. 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="AEN3626" ->21.1. Instructions</A -></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 @@ -98,17 +96,21 @@ TARGET="_top" machine (for Dfs-aware clients to browse) using Samba.</P ><P >To enable SMB-based DFS for Samba, configure it with the - <VAR + <TT CLASS="PARAMETER" ->--with-msdfs</VAR +><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" -><VAR +><TT CLASS="PARAMETER" -> host msdfs</VAR +><I +> host msdfs</I +></TT ></A > parameter in the <TT CLASS="FILENAME" @@ -118,16 +120,18 @@ CLASS="FILENAME" level boolean <A HREF="smb.conf.5.html#MSDFSROOT" TARGET="_top" -><VAR +><TT CLASS="PARAMETER" -> msdfs root</VAR +><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 +>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 @@ -155,44 +159,54 @@ CLASS="PROGRAMLISTING" >In the /export/dfsroot directory we set up our dfs links to other servers on the network.</P ><P -><SAMP +><TT CLASS="PROMPT" ->root# </SAMP -><KBD +>root# </TT +><TT CLASS="USERINPUT" ->cd /export/dfsroot</KBD +><B +>cd /export/dfsroot</B +></TT ></P ><P -><SAMP +><TT CLASS="PROMPT" ->root# </SAMP -><KBD +>root# </TT +><TT CLASS="USERINPUT" ->chown root /export/dfsroot</KBD +><B +>chown root /export/dfsroot</B +></TT ></P ><P -><SAMP +><TT CLASS="PROMPT" ->root# </SAMP -><KBD +>root# </TT +><TT CLASS="USERINPUT" ->chmod 755 /export/dfsroot</KBD +><B +>chmod 755 /export/dfsroot</B +></TT ></P ><P -><SAMP +><TT CLASS="PROMPT" ->root# </SAMP -><KBD +>root# </TT +><TT CLASS="USERINPUT" ->ln -s msdfs:storageA\\shareA linka</KBD +><B +>ln -s msdfs:storageA\\shareA linka</B +></TT ></P ><P -><SAMP +><TT CLASS="PROMPT" ->root# </SAMP -><KBD +>root# </TT +><TT CLASS="USERINPUT" ->ln -s msdfs:serverB\\share,serverC\\share linkb</KBD +><B +>ln -s msdfs:serverB\\share,serverC\\share linkb</B +></TT ></P ><P >You should set up the permissions and ownership of @@ -212,9 +226,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3661" ->21.1.1. Notes</A -></H2 +NAME="AEN1894">13.1.1. Notes</H2 ><P ></P ><UL @@ -257,7 +269,7 @@ WIDTH="33%" ALIGN="left" VALIGN="top" ><A -HREF="vfs.html" +HREF="pam.html" ACCESSKEY="P" >Prev</A ></TD @@ -275,7 +287,7 @@ WIDTH="33%" ALIGN="right" VALIGN="top" ><A -HREF="integrate-ms-networks.html" +HREF="printing.html" ACCESSKEY="N" >Next</A ></TD @@ -285,7 +297,8 @@ ACCESSKEY="N" WIDTH="33%" ALIGN="left" VALIGN="top" ->Stackable VFS modules</TD +>Configuring PAM for distributed but centrally +managed authentication</TD ><TD WIDTH="34%" ALIGN="center" @@ -299,7 +312,7 @@ ACCESSKEY="U" WIDTH="33%" ALIGN="right" VALIGN="top" ->Integrating MS Windows networks with Samba</TD +>Printing Support</TD ></TR ></TABLE ></DIV diff --git a/docs/htmldocs/net.8.html b/docs/htmldocs/net.8.html index 63becc2071..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.7"></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 @@ -38,7 +38,7 @@ NAME="AEN8" ><B CLASS="COMMAND" >net</B -> {<ads|rap|rpc>} [-h] [-w workgroup] [-W myworkgroup] [-U user] [-I ip-address] [-p port] [-n myname] [-s conffile] [-S server] [-C comment] [-M maxusers] [-F flags] [-j jobid] [-l] [-r] [-f] [-t timeout] [-P] [-D debuglevel]</P +> {<ads|rap|rpc>} [-h] [-w workgroup] [-W myworkgroup] [-U user] [-I ip-address] [-p port] [-n myname] [-s conffile] [-S server] [-C comment] [-M maxusers] [-F flags] [-j jobid] [-l] [-r] [-f] [-t timeout] [-P] [-D debuglevel]</P ></DIV ><DIV CLASS="REFSECT1" @@ -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 @@ -317,21 +306,21 @@ CLASS="VARIABLELIST" </P ></DD ><DT ->USER DELETE <name> [misc options]</DT +>USER DELETE <name> [misc options]</DT ><DD ><P > delete specified user </P ></DD ><DT ->USER INFO <name> [misc options]</DT +>USER INFO <name> [misc options]</DT ><DD ><P > list the domain groups of the specified user </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 @@ -345,14 +334,14 @@ CLASS="VARIABLELIST" </P ></DD ><DT ->GROUP DELETE <name> [misc. options] [targets]</DT +>GROUP DELETE <name> [misc. options] [targets]</DT ><DD ><P > Delete specified group </P ></DD ><DT ->GROUP ADD <name> [-C comment]</DT +>GROUP ADD <name> [-C comment]</DT ><DD ><P > Create specified group @@ -366,14 +355,14 @@ CLASS="VARIABLELIST" </P ></DD ><DT ->SHARE ADD <name=serverpath> [misc. options] [targets]</DT +>SHARE ADD <name=serverpath> [misc. options] [targets]</DT ><DD ><P > Adds a share from a server (makes the export active) </P ></DD ><DT ->SHARE DELETE <sharenam</DT +>SHARE DELETE <sharenam</DT ><DD ><P ></P @@ -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 6b8161e02e..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.7"></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 @@ -196,6 +185,14 @@ CLASS="COMMAND" than a file.</P ></DD ><DT +>-a</DT +><DD +><P +>If this parameter is specified, each new + connection will append log messages to the log file. + This is the default.</P +></DD +><DT >-i</DT ><DD ><P @@ -207,17 +204,33 @@ CLASS="COMMAND" CLASS="COMMAND" >nmbd</B > also logs to standard - output, as if the <CODE -CLASS="CONSTANT" ->-S</CODE + output, as if the <B +CLASS="COMMAND" +>-S</B > parameter had been given. </P ></DD ><DT ->-h|--help</DT +>-o</DT ><DD ><P ->Print a summary of command line options.</P +>If this parameter is specified, the + log files will be overwritten when opened. By default, + <B +CLASS="COMMAND" +>smbd</B +> will append entries to the log + files.</P +></DD +><DT +>-h</DT +><DD +><P +>Prints the help information (usage) + for <B +CLASS="COMMAND" +>nmbd</B +>.</P ></DD ><DT >-H <filename></DT @@ -229,37 +242,28 @@ CLASS="CONSTANT" resolution mechanism <A HREF="smb.conf.5.html#nameresolveorder" TARGET="_top" -><VAR -CLASS="PARAMETER" ->name resolve - order</VAR +> 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 @@ -274,94 +278,120 @@ 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 ><DD ><P >Prints the version number for -<B + <B CLASS="COMMAND" ->smbd</B +>nmbd</B >.</P ></DD ><DT ->-s <configuration file></DT +>-d <debug level></DT ><DD ><P ->The file specified contains the -configuration details required by the server. The -information in this file includes server-specific -information such as what printcap file to use, as well -as descriptions of all the services that the server is -to provide. See <A +>debuglevel is an integer + from 0 to 10. The default value if this parameter is + not specified is zero.</P +><P +>The higher this value, the more detail will + be 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 + information about operations carried out.</P +><P +>Levels above 1 will generate considerable amounts + of log data, and should only be used when investigating + a problem. Levels above 3 are designed for use only by developers + and generate HUGE amounts of log data, most of which is extremely + cryptic.</P +><P +>Note that specifying this parameter here will override + the <A +HREF="smb.conf.5.html#loglevel" +TARGET="_top" +>log level</A +> + parameter in the <A HREF="smb.conf.5.html" TARGET="_top" ><TT CLASS="FILENAME" ->smb.conf(5)</TT +> smb.conf(5)</TT ></A -> for more information. -The default configuration file name is determined at -compile time.</P +> file.</P ></DD ><DT ->-d|--debug=debuglevel</DT +>-l <log directory></DT ><DD ><P -><VAR -CLASS="REPLACEABLE" ->debuglevel</VAR -> is an integer -from 0 to 10. The default value if this parameter is -not specified is zero.</P -><P ->The higher this value, the more detail will be -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 -information about operations carried out.</P -><P ->Levels above 1 will generate considerable -amounts of log data, and should only be used when -investigating a problem. Levels above 3 are designed for -use only by developers and generate HUGE amounts of log -data, most of which is extremely cryptic.</P -><P ->Note that specifying this parameter here will -override the <A -HREF="smb.conf.5.html#loglevel" +>The -l parameter specifies a directory + into which the "log.nmbd" log file will be created + for operational data from the running <B +CLASS="COMMAND" +>nmbd</B +> + server. The default log directory is compiled into Samba + as part of the build process. Common defaults are <TT +CLASS="FILENAME" +> /usr/local/samba/var/log.nmb</TT +>, <TT +CLASS="FILENAME" +> /usr/samba/var/log.nmb</TT +> or + <TT +CLASS="FILENAME" +>/var/log/log.nmb</TT +>. <I +CLASS="EMPHASIS" +>Beware:</I +> + If the directory specified does not exist, <B +CLASS="COMMAND" +>nmbd</B +> + will log to the default debug log location defined at compile time. + </P +></DD +><DT +>-n <primary NetBIOS name></DT +><DD +><P +>This option allows you to override + the NetBIOS name that Samba uses for itself. This is identical + to setting the <A +HREF="smb.conf.5.html#netbiosname" TARGET="_top" ->log -level</A +> NetBIOS name</A > parameter in the <A HREF="smb.conf.5.html" TARGET="_top" -><TT +> + <TT CLASS="FILENAME" ->smb.conf(5)</TT +>smb.conf</TT ></A -> file.</P -></DD -><DT ->-l|--logfile=logbasename</DT -><DD -><P ->File name for log/debug files. The extension -<CODE -CLASS="CONSTANT" ->".client"</CODE -> will be appended. The log file is -never removed by the client.</P +> file. However, a command + line setting will take precedence over settings in + <TT +CLASS="FILENAME" +>smb.conf</TT +>.</P ></DD ><DT >-p <UDP port number></DT @@ -376,13 +406,35 @@ CLASS="COMMAND" 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 + 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 + 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 ></DL ></DIV ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN131" +NAME="AEN148" ></A ><H2 >FILES</H2 @@ -405,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 @@ -425,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 @@ -446,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 @@ -459,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" -><CODE -CLASS="CONSTANT" ->wins support</CODE -></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" @@ -510,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" -><CODE -CLASS="CONSTANT" ->local master</CODE -></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 > @@ -551,7 +590,7 @@ CLASS="FILENAME" ><DIV CLASS="REFSECT1" ><A -NAME="AEN185" +NAME="AEN195" ></A ><H2 >SIGNALS</H2 @@ -560,12 +599,9 @@ NAME="AEN185" 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 @@ -600,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="AEN202" +NAME="AEN211" ></A ><H2 >VERSION</H2 @@ -626,49 +663,54 @@ NAME="AEN202" ><DIV CLASS="REFSECT1" ><A -NAME="AEN205" +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 @@ -686,7 +728,7 @@ TARGET="_top" ><DIV CLASS="REFSECT1" ><A -NAME="AEN229" +NAME="AEN231" ></A ><H2 >AUTHOR</H2 @@ -698,14 +740,14 @@ NAME="AEN229" ><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 cb1df2cd82..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.7"></HEAD +CONTENT="Modular DocBook HTML Stylesheet Version 1.77"></HEAD ><BODY CLASS="REFENTRY" BGCOLOR="#FFFFFF" @@ -38,7 +38,7 @@ NAME="AEN8" ><B CLASS="COMMAND" >nmblookup</B -> [-M] [-R] [-S] [-r] [-A] [-h] [-B <broadcast address>] [-U <unicast address>] [-d <debug level>] [-s <smb config file>] [-i <NetBIOS scope>] [-T] [-f] {name}</P +> [-M] [-R] [-S] [-r] [-A] [-h] [-B <broadcast address>] [-U <unicast address>] [-d <debug level>] [-s <smb config file>] [-i <NetBIOS scope>] [-T] [-f] {name}</P ></DIV ><DIV CLASS="REFSECT1" @@ -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 @@ -82,20 +80,24 @@ CLASS="VARIABLELIST" ><DD ><P >Searches for a master browser by looking - up the NetBIOS name <VAR + up the NetBIOS name <TT CLASS="REPLACEABLE" ->name</VAR +><I +>name</I +></TT > with a - type of <CODE + type of <TT CLASS="CONSTANT" ->0x1d</CODE ->. If <VAR +>0x1d</TT +>. If <TT CLASS="REPLACEABLE" -> name</VAR +><I +> name</I +></TT > is "-" then it does a lookup on the special name - <CODE + <TT CLASS="CONSTANT" ->__MSBROWSE__</CODE +>__MSBROWSE__</TT >.</P ></DD ><DT @@ -107,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 @@ -128,109 +130,34 @@ 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 >-A</DT ><DD ><P ->Interpret <VAR +>Interpret <TT CLASS="REPLACEABLE" ->name</VAR +><I +>name</I +></TT > as an IP Address and do a node status query on this address.</P ></DD ><DT ->-n <primary NetBIOS name></DT +>-h</DT ><DD ><P ->This option allows you to override -the NetBIOS name that Samba uses for itself. This is identical -to setting the <A -HREF="smb.conf.5.html#netbiosname" -TARGET="_top" -><VAR -CLASS="PARAMETER" ->NetBIOS -name</VAR -></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 ->.</P +>Print a help (usage) message.</P ></DD ><DT ->-i <scope></DT -><DD -><P ->This specifies a NetBIOS scope that -<B -CLASS="COMMAND" ->nmblookup</B -> will use to communicate with when -generating NetBIOS names. For details on the use of NetBIOS -scopes, see rfc1001.txt and rfc1002.txt. NetBIOS scopes are -<SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->very</I -></SPAN -> rarely used, only set this parameter -if you are the system administrator in charge of all the -NetBIOS systems you communicate with.</P -></DD -><DT ->-W|--workgroup=domain</DT -><DD -><P ->Set the SMB domain of the username. This -overrides the default domain which is the domain defined in -smb.conf. If the domain specified is the same as the servers -NetBIOS name, it causes the client to log on using the servers local -SAM (as opposed to the Domain SAM). </P -></DD -><DT ->-O socket options</DT -><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 -options. </P -></DD -><DT ->-h|--help</DT -><DD -><P ->Print a summary of command line options.</P -></DD -><DT ->-B <broadcast address></DT +>-B <broadcast address></DT ><DD ><P >Send the query to the given broadcast address. Without @@ -239,114 +166,106 @@ options. </P either auto-detected or defined in the <A HREF="smb.conf.5.html#INTERFACES" TARGET="_top" -><VAR +><TT CLASS="PARAMETER" ->interfaces</VAR +><I +>interfaces</I +></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 ><DT ->-U <unicast address></DT +>-U <unicast address></DT ><DD ><P >Do a unicast query to the specified address or - host <VAR + host <TT CLASS="REPLACEABLE" ->unicast address</VAR +><I +>unicast address</I +></TT >. This option - (along with the <VAR + (along with the <TT CLASS="PARAMETER" ->-R</VAR +><I +>-R</I +></TT > option) is needed to query a WINS server.</P ></DD ><DT ->-V</DT +>-d <debuglevel></DT ><DD ><P ->Prints the version number for -<B +>debuglevel 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" ->smbd</B ->.</P -></DD -><DT ->-s <configuration file></DT -><DD +>nmblookup</B +>. At level + 0, only critical errors and serious warnings will be logged.</P ><P ->The file specified contains the -configuration details required by the server. The -information in this file includes server-specific -information such as what printcap file to use, as well -as descriptions of all the services that the server is -to provide. See <A -HREF="smb.conf.5.html" +>Levels above 1 will generate considerable amounts of + log data, and should only be used when investigating a problem. + Levels above 3 are designed for use only by developers and + generate HUGE amounts of data, most of which is extremely cryptic.</P +><P +>Note that specifying this parameter here will override + the <A +HREF="smb.conf.5.html#LOGLEVEL" TARGET="_top" ><TT -CLASS="FILENAME" ->smb.conf(5)</TT +CLASS="PARAMETER" +><I +> log level</I +></TT ></A -> for more information. -The default configuration file name is determined at -compile time.</P +> parameter in the <TT +CLASS="FILENAME" +> smb.conf(5)</TT +> file.</P ></DD ><DT ->-d|--debug=debuglevel</DT +>-s <smb.conf></DT ><DD ><P -><VAR -CLASS="REPLACEABLE" ->debuglevel</VAR -> is an integer -from 0 to 10. The default value if this parameter is -not specified is zero.</P -><P ->The higher this value, the more detail will be -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 -information about operations carried out.</P -><P ->Levels above 1 will generate considerable -amounts of log data, and should only be used when -investigating a problem. Levels above 3 are designed for -use only by developers and generate HUGE amounts of log -data, most of which is extremely cryptic.</P -><P ->Note that specifying this parameter here will -override the <A -HREF="smb.conf.5.html#loglevel" -TARGET="_top" ->log -level</A -> parameter in the <A +>This parameter specifies the pathname to + the Samba configuration file, <A HREF="smb.conf.5.html" TARGET="_top" -><TT -CLASS="FILENAME" ->smb.conf(5)</TT -></A -> file.</P +> smb.conf(5)</A +>. This file controls all aspects of + the Samba setup on the machine.</P ></DD ><DT ->-l|--logfile=logbasename</DT +>-i <scope></DT ><DD ><P ->File name for log/debug files. The extension -<CODE -CLASS="CONSTANT" ->".client"</CODE -> will be appended. The log file is -never removed by the client.</P +>This specifies a NetBIOS scope that + <B +CLASS="COMMAND" +>nmblookup</B +> will use to communicate with when + generating NetBIOS names. For details on the use of NetBIOS + scopes, see rfc1001.txt and rfc1002.txt. NetBIOS scopes are + <SPAN +CLASS="emphasis" +><I +CLASS="EMPHASIS" +>very</I +></SPAN +> rarely used, only set this parameter + if you are the system administrator in charge of all the + NetBIOS systems you communicate with.</P ></DD ><DT >-T</DT @@ -382,7 +301,7 @@ CLASS="EMPHASIS" >This is the NetBIOS name being queried. Depending upon the previous options this may be a NetBIOS name or IP address. If a NetBIOS name then the different name types may be specified - by appending '#<type>' to the name. This name may also be + by appending '#<type>' to the name. This name may also be '*', which will return all registered names within a broadcast area.</P ></DD @@ -392,7 +311,7 @@ CLASS="EMPHASIS" ><DIV CLASS="REFSECT1" ><A -NAME="AEN154" +NAME="AEN115" ></A ><H2 >EXAMPLES</H2 @@ -405,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" @@ -429,7 +348,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN166" +NAME="AEN127" ></A ><H2 >VERSION</H2 @@ -440,35 +359,34 @@ NAME="AEN166" ><DIV CLASS="REFSECT1" ><A -NAME="AEN169" +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="AEN181" +NAME="AEN137" ></A ><H2 >AUTHOR</H2 @@ -480,14 +398,14 @@ NAME="AEN181" ><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/oplocks.html b/docs/htmldocs/oplocks.html new file mode 100644 index 0000000000..6aa91fb17f --- /dev/null +++ b/docs/htmldocs/oplocks.html @@ -0,0 +1,208 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML +><HEAD +><TITLE +>Oplocks</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="Improved browsing in samba" +HREF="improved-browsing.html"><LINK +REL="NEXT" +TITLE="Quick Cross Subnet Browsing / Cross Workgroup Browsing guide" +HREF="browsing-quick.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="improved-browsing.html" +ACCESSKEY="P" +>Prev</A +></TD +><TD +WIDTH="80%" +ALIGN="center" +VALIGN="bottom" +></TD +><TD +WIDTH="10%" +ALIGN="right" +VALIGN="bottom" +><A +HREF="browsing-quick.html" +ACCESSKEY="N" +>Next</A +></TD +></TR +></TABLE +><HR +ALIGN="LEFT" +WIDTH="100%"></DIV +><DIV +CLASS="CHAPTER" +><H1 +><A +NAME="OPLOCKS" +></A +>Chapter 3. Oplocks</H1 +><DIV +CLASS="SECT1" +><H1 +CLASS="SECT1" +><A +NAME="AEN378" +></A +>3.1. What are oplocks?</H1 +><P +>When a client opens a file it can request an "oplock" or file +lease. This is (to simplify a bit) a guarentee that no one else +has the file open simultaneously. It allows the client to not +send any updates on the file to the server, thus reducing a +network file access to local access (once the file is in +client cache). An "oplock break" is when the server sends +a request to the client to flush all its changes back to +the server, so the file is in a consistent state for other +opens to succeed. If a client fails to respond to this +asynchronous request then the file can be corrupted. Hence +the "turn off oplocks" answer if people are having multi-user +file access problems.</P +><P +>Unless the kernel is "oplock aware" (SGI IRIX and Linux are +the only two UNIXes that are at the moment) then if a local +UNIX process accesses the file simultaneously then Samba +has no way of telling this is occuring, so the guarentee +to the client is broken. This can corrupt the file. Short +answer - it you have UNIX clients accessing the same file +as smbd locally or via NFS and you're not running Linux or +IRIX then turn off oplocks for that file or share.</P +><P +>"Share modes". These are modes of opening a file, that +guarentee an invarient - such as DENY_WRITE - which means +that if any other opens are requested with write access after +this current open has succeeded then they should be denied +with a "sharing violation" error message. Samba handles these +internally inside smbd. UNIX clients accessing the same file +ignore these invarients. Just proving that if you need simultaneous +file access from a Windows and UNIX client you *must* have an +application that is written to lock records correctly on both +sides. Few applications are written like this, and even fewer +are cross platform (UNIX and Windows) so in practice this isn't +much of a problem.</P +><P +>"Locking". This really means "byte range locking" - such as +lock 10 bytes at file offset 24 for write access. This is the +area in which well written UNIX and Windows apps will cooperate. +Windows locks (at least from NT or above) are 64-bit unsigned +offsets. UNIX locks are either 31 bit or 63 bit and are signed +(the top bit is used for the sign). Samba handles these by +first ensuring that all the Windows locks don't conflict (ie. +if other Windows clients have competing locks then just reject +immediately) - this allows us to support 64-bit Windows locks +on 32-bit filesystems. Secondly any locks that are valid are +then mapped onto UNIX fcntl byte range locks. These are the +locks that will be seen by UNIX processes. If there is a conflict +here the lock is rejected.</P +><P +>Note that if a client has an oplock then it "knows" that no +other client can have the file open so usually doesn't bother +to send to lock request to the server - this means once again +if you need to share files between UNIX and Windows processes +either use IRIX or Linux, or turn off oplocks for these +files/shares.</P +></DIV +></DIV +><DIV +CLASS="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="improved-browsing.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="browsing-quick.html" +ACCESSKEY="N" +>Next</A +></TD +></TR +><TR +><TD +WIDTH="33%" +ALIGN="left" +VALIGN="top" +>Improved browsing in samba</TD +><TD +WIDTH="34%" +ALIGN="center" +VALIGN="top" +><A +HREF="introduction.html" +ACCESSKEY="U" +>Up</A +></TD +><TD +WIDTH="33%" +ALIGN="right" +VALIGN="top" +>Quick Cross Subnet Browsing / Cross Workgroup Browsing guide</TD +></TR +></TABLE +></DIV +></BODY +></HTML +>
\ No newline at end of file diff --git a/docs/htmldocs/optional.html b/docs/htmldocs/optional.html index 20bf1e4e21..b15515ddab 100644 --- a/docs/htmldocs/optional.html +++ b/docs/htmldocs/optional.html @@ -2,19 +2,20 @@ <HTML ><HEAD ><TITLE ->Advanced Configuration</TITLE +>Optional configuration</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><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="UNIX Permission Bits and Windows NT Access Control Lists" -HREF="unix-permissions.html"></HEAD +TITLE="Integrating MS Windows networks with Samba" +HREF="integrate-ms-networks.html"></HEAD ><BODY CLASS="PART" BGCOLOR="#FFFFFF" @@ -56,7 +57,7 @@ WIDTH="10%" ALIGN="right" VALIGN="bottom" ><A -HREF="unix-permissions.html" +HREF="integrate-ms-networks.html" ACCESSKEY="N" >Next</A ></TD @@ -68,22 +69,19 @@ WIDTH="100%"></DIV ><DIV CLASS="PART" ><A -NAME="OPTIONAL" -></A -><DIV +NAME="OPTIONAL"><DIV CLASS="TITLEPAGE" ><H1 CLASS="TITLE" ->III. Advanced Configuration</H1 +>III. Optional configuration</H1 ><DIV CLASS="PARTINTRO" ><A -NAME="AEN1511" -></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 part each cover one specific feature.</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" @@ -94,195 +92,363 @@ CLASS="TOC" ></DT ><DT >10. <A +HREF="integrate-ms-networks.html" +>Integrating MS Windows networks with Samba</A +></DT +><DD +><DL +><DT +>10.1. <A +HREF="integrate-ms-networks.html#AEN1374" +>Agenda</A +></DT +><DT +>10.2. <A +HREF="integrate-ms-networks.html#AEN1396" +>Name Resolution in a pure Unix/Linux world</A +></DT +><DD +><DL +><DT +>10.2.1. <A +HREF="integrate-ms-networks.html#AEN1412" +><TT +CLASS="FILENAME" +>/etc/hosts</TT +></A +></DT +><DT +>10.2.2. <A +HREF="integrate-ms-networks.html#AEN1428" +><TT +CLASS="FILENAME" +>/etc/resolv.conf</TT +></A +></DT +><DT +>10.2.3. <A +HREF="integrate-ms-networks.html#AEN1439" +><TT +CLASS="FILENAME" +>/etc/host.conf</TT +></A +></DT +><DT +>10.2.4. <A +HREF="integrate-ms-networks.html#AEN1447" +><TT +CLASS="FILENAME" +>/etc/nsswitch.conf</TT +></A +></DT +></DL +></DD +><DT +>10.3. <A +HREF="integrate-ms-networks.html#AEN1459" +>Name resolution as used within MS Windows networking</A +></DT +><DD +><DL +><DT +>10.3.1. <A +HREF="integrate-ms-networks.html#AEN1471" +>The NetBIOS Name Cache</A +></DT +><DT +>10.3.2. <A +HREF="integrate-ms-networks.html#AEN1476" +>The LMHOSTS file</A +></DT +><DT +>10.3.3. <A +HREF="integrate-ms-networks.html#AEN1484" +>HOSTS file</A +></DT +><DT +>10.3.4. <A +HREF="integrate-ms-networks.html#AEN1489" +>DNS Lookup</A +></DT +><DT +>10.3.5. <A +HREF="integrate-ms-networks.html#AEN1492" +>WINS Lookup</A +></DT +></DL +></DD +><DT +>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 +>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 +>10.5.1. <A +HREF="integrate-ms-networks.html#AEN1542" +>Use MS Windows NT as an authentication server</A +></DT +><DT +>10.5.2. <A +HREF="integrate-ms-networks.html#AEN1550" +>Make Samba a member of an MS Windows NT security domain</A +></DT +><DT +>10.5.3. <A +HREF="integrate-ms-networks.html#AEN1567" +>Configure Samba as an authentication server</A +></DT +></DL +></DD +><DT +>10.6. <A +HREF="integrate-ms-networks.html#AEN1584" +>Conclusions</A +></DT +></DL +></DD +><DT +>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#AEN1525" +>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#AEN1531" +>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#AEN1542" +>11.3. <A +HREF="unix-permissions.html#AEN1625" >Viewing file ownership</A ></DT ><DT ->10.4. <A -HREF="unix-permissions.html#AEN1562" +>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#AEN1577" +>11.4.1. <A +HREF="unix-permissions.html#AEN1660" >File Permissions</A ></DT ><DT ->10.4.2. <A -HREF="unix-permissions.html#AEN1591" +>11.4.2. <A +HREF="unix-permissions.html#AEN1674" >Directory Permissions</A ></DT ></DL ></DD ><DT ->10.5. <A -HREF="unix-permissions.html#AEN1598" +>11.5. <A +HREF="unix-permissions.html#AEN1681" >Modifying file or directory permissions</A ></DT ><DT ->10.6. <A -HREF="unix-permissions.html#AEN1620" +>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#AEN1673" +>11.7. <A +HREF="unix-permissions.html#AEN1767" >Interaction with the standard Samba file attribute mapping</A ></DT ></DL ></DD ><DT ->11. <A -HREF="groupmapping.html" ->Configuring Group Mapping</A +>12. <A +HREF="pam.html" +>Configuring PAM for distributed but centrally +managed authentication</A ></DT +><DD +><DL ><DT ->12. <A +>12.1. <A +HREF="pam.html#AEN1788" +>Samba and PAM</A +></DT +><DT +>12.2. <A +HREF="pam.html#AEN1832" +>Distributed Authentication</A +></DT +><DT +>12.3. <A +HREF="pam.html#AEN1839" +>PAM Configuration in smb.conf</A +></DT +></DL +></DD +><DT +>13. <A +HREF="msdfs.html" +>Hosting a Microsoft Distributed File System tree on Samba</A +></DT +><DD +><DL +><DT +>13.1. <A +HREF="msdfs.html#AEN1859" +>Instructions</A +></DT +><DD +><DL +><DT +>13.1.1. <A +HREF="msdfs.html#AEN1894" +>Notes</A +></DT +></DL +></DD +></DL +></DD +><DT +>14. <A HREF="printing.html" >Printing Support</A ></DT ><DD ><DL ><DT ->12.1. <A -HREF="printing.html#AEN1736" +>14.1. <A +HREF="printing.html#AEN1920" >Introduction</A ></DT ><DT ->12.2. <A -HREF="printing.html#AEN1758" +>14.2. <A +HREF="printing.html#AEN1942" >Configuration</A ></DT ><DD ><DL ><DT ->12.2.1. <A -HREF="printing.html#AEN1766" +>14.2.1. <A +HREF="printing.html#AEN1950" >Creating [print$]</A ></DT ><DT ->12.2.2. <A -HREF="printing.html#AEN1801" +>14.2.2. <A +HREF="printing.html#AEN1985" >Setting Drivers for Existing Printers</A ></DT ><DT ->12.2.3. <A -HREF="printing.html#AEN1817" +>14.2.3. <A +HREF="printing.html#AEN2001" >Support a large number of printers</A ></DT ><DT ->12.2.4. <A -HREF="printing.html#AEN1832" +>14.2.4. <A +HREF="printing.html#AEN2012" >Adding New Printers via the Windows NT APW</A ></DT ><DT ->12.2.5. <A -HREF="printing.html#AEN1862" +>14.2.5. <A +HREF="printing.html#AEN2042" >Samba and Printer Ports</A ></DT ></DL ></DD ><DT ->12.3. <A -HREF="printing.html#AEN1870" +>14.3. <A +HREF="printing.html#AEN2050" >The Imprints Toolset</A ></DT ><DD ><DL ><DT ->12.3.1. <A -HREF="printing.html#AEN1874" +>14.3.1. <A +HREF="printing.html#AEN2054" >What is Imprints?</A ></DT ><DT ->12.3.2. <A -HREF="printing.html#AEN1884" +>14.3.2. <A +HREF="printing.html#AEN2064" >Creating Printer Driver Packages</A ></DT ><DT ->12.3.3. <A -HREF="printing.html#AEN1887" +>14.3.3. <A +HREF="printing.html#AEN2067" >The Imprints server</A ></DT ><DT ->12.3.4. <A -HREF="printing.html#AEN1891" +>14.3.4. <A +HREF="printing.html#AEN2071" >The Installation Client</A ></DT ></DL ></DD ><DT ->12.4. <A -HREF="printing.html#AEN1913" +>14.4. <A +HREF="printing.html#AEN2093" >Diagnosis</A ></DT ><DD ><DL ><DT ->12.4.1. <A -HREF="printing.html#AEN1915" +>14.4.1. <A +HREF="printing.html#AEN2095" >Introduction</A ></DT ><DT ->12.4.2. <A -HREF="printing.html#AEN1931" +>14.4.2. <A +HREF="printing.html#AEN2111" >Debugging printer problems</A ></DT ><DT ->12.4.3. <A -HREF="printing.html#AEN1940" +>14.4.3. <A +HREF="printing.html#AEN2120" >What printers do I have?</A ></DT ><DT ->12.4.4. <A -HREF="printing.html#AEN1948" +>14.4.4. <A +HREF="printing.html#AEN2128" >Setting up printcap and print servers</A ></DT ><DT ->12.4.5. <A -HREF="printing.html#AEN1976" +>14.4.5. <A +HREF="printing.html#AEN2156" >Job sent, no output</A ></DT ><DT ->12.4.6. <A -HREF="printing.html#AEN1987" +>14.4.6. <A +HREF="printing.html#AEN2167" >Job sent, strange output</A ></DT ><DT ->12.4.7. <A -HREF="printing.html#AEN1999" +>14.4.7. <A +HREF="printing.html#AEN2179" >Raw PostScript printed</A ></DT ><DT ->12.4.8. <A -HREF="printing.html#AEN2002" +>14.4.8. <A +HREF="printing.html#AEN2182" >Advanced Printing</A ></DT ><DT ->12.4.9. <A -HREF="printing.html#AEN2005" +>14.4.9. <A +HREF="printing.html#AEN2185" >Real debugging</A ></DT ></DL @@ -290,409 +456,206 @@ HREF="printing.html#AEN2005" ></DL ></DD ><DT ->13. <A -HREF="cups-printing.html" ->CUPS Printing Support</A -></DT -><DD -><DL -><DT ->13.1. <A -HREF="cups-printing.html#AEN2025" ->Introduction</A -></DT -><DT ->13.2. <A -HREF="cups-printing.html#AEN2032" ->Configuring <TT -CLASS="FILENAME" ->smb.conf</TT -> for CUPS</A -></DT -><DT ->13.3. <A -HREF="cups-printing.html#AEN2052" ->CUPS - RAW Print Through Mode</A -></DT -><DT ->13.4. <A -HREF="cups-printing.html#AEN2111" ->CUPS as a network PostScript RIP -- CUPS drivers working on server, Adobe -PostScript driver with CUPS-PPDs downloaded to clients</A -></DT -><DT ->13.5. <A -HREF="cups-printing.html#AEN2132" ->Windows Terminal Servers (WTS) as CUPS clients</A -></DT -><DT ->13.6. <A -HREF="cups-printing.html#AEN2136" ->Setting up CUPS for driver download</A -></DT -><DT ->13.7. <A -HREF="cups-printing.html#AEN2149" ->Sources of CUPS drivers / PPDs</A -></DT -><DD -><DL -><DT ->13.7.1. <A -HREF="cups-printing.html#AEN2176" -><B -CLASS="COMMAND" ->cupsaddsmb</B -></A -></DT -></DL -></DD -><DT ->13.8. <A -HREF="cups-printing.html#AEN2205" ->The CUPS Filter Chains</A -></DT -><DT ->13.9. <A -HREF="cups-printing.html#AEN2244" ->CUPS Print Drivers and Devices</A -></DT -><DD -><DL -><DT ->13.9.1. <A -HREF="cups-printing.html#AEN2251" ->Further printing steps</A -></DT -></DL -></DD -><DT ->13.10. <A -HREF="cups-printing.html#AEN2321" ->Limiting the number of pages users can print</A -></DT -><DT ->13.11. <A -HREF="cups-printing.html#AEN2417" ->Advanced Postscript Printing from MS Windows</A -></DT -><DT ->13.12. <A -HREF="cups-printing.html#AEN2432" ->Auto-Deletion of CUPS spool files</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#AEN2506" +>15.1. <A +HREF="winbind.html#AEN2225" >Abstract</A ></DT ><DT ->14.2. <A -HREF="winbind.html#AEN2510" +>15.2. <A +HREF="winbind.html#AEN2229" >Introduction</A ></DT ><DT ->14.3. <A -HREF="winbind.html#AEN2523" +>15.3. <A +HREF="winbind.html#AEN2242" >What Winbind Provides</A ></DT ><DD ><DL ><DT ->14.3.1. <A -HREF="winbind.html#AEN2530" +>15.3.1. <A +HREF="winbind.html#AEN2249" >Target Uses</A ></DT ></DL ></DD ><DT ->14.4. <A -HREF="winbind.html#AEN2534" +>15.4. <A +HREF="winbind.html#AEN2253" >How Winbind Works</A ></DT ><DD ><DL ><DT ->14.4.1. <A -HREF="winbind.html#AEN2539" +>15.4.1. <A +HREF="winbind.html#AEN2258" >Microsoft Remote Procedure Calls</A ></DT ><DT ->14.4.2. <A -HREF="winbind.html#AEN2543" ->Microsoft Active Directory Services</A -></DT -><DT ->14.4.3. <A -HREF="winbind.html#AEN2546" +>15.4.2. <A +HREF="winbind.html#AEN2262" >Name Service Switch</A ></DT ><DT ->14.4.4. <A -HREF="winbind.html#AEN2562" +>15.4.3. <A +HREF="winbind.html#AEN2278" >Pluggable Authentication Modules</A ></DT ><DT ->14.4.5. <A -HREF="winbind.html#AEN2570" +>15.4.4. <A +HREF="winbind.html#AEN2286" >User and Group ID Allocation</A ></DT ><DT ->14.4.6. <A -HREF="winbind.html#AEN2574" +>15.4.5. <A +HREF="winbind.html#AEN2290" >Result Caching</A ></DT ></DL ></DD ><DT ->14.5. <A -HREF="winbind.html#AEN2577" +>15.5. <A +HREF="winbind.html#AEN2293" >Installation and Configuration</A ></DT ><DD ><DL ><DT ->14.5.1. <A -HREF="winbind.html#AEN2582" +>15.5.1. <A +HREF="winbind.html#AEN2300" >Introduction</A ></DT ><DT ->14.5.2. <A -HREF="winbind.html#AEN2595" +>15.5.2. <A +HREF="winbind.html#AEN2313" >Requirements</A ></DT ><DT ->14.5.3. <A -HREF="winbind.html#AEN2609" +>15.5.3. <A +HREF="winbind.html#AEN2327" >Testing Things Out</A ></DT ></DL ></DD ><DT ->14.6. <A -HREF="winbind.html#AEN2834" +>15.6. <A +HREF="winbind.html#AEN2542" >Limitations</A ></DT ><DT ->14.7. <A -HREF="winbind.html#AEN2844" +>15.7. <A +HREF="winbind.html#AEN2552" >Conclusion</A ></DT ></DL ></DD ><DT ->15. <A -HREF="advancednetworkmanagement.html" ->Advanced Network Manangement</A -></DT -><DD -><DL -><DT ->15.1. <A -HREF="advancednetworkmanagement.html#AEN2859" ->Configuring Samba Share Access Controls</A -></DT -><DD -><DL -><DT ->15.1.1. <A -HREF="advancednetworkmanagement.html#AEN2869" ->Share Permissions Management</A -></DT -></DL -></DD -><DT ->15.2. <A -HREF="advancednetworkmanagement.html#AEN2897" ->Remote Server Administration</A -></DT -><DT ->15.3. <A -HREF="advancednetworkmanagement.html#AEN2914" ->Network Logon Script Magic</A -></DT -></DL -></DD -><DT >16. <A -HREF="policymgmt.html" ->System and Account Policies</A +HREF="pdb-mysql.html" +>Passdb MySQL plugin</A ></DT ><DD ><DL ><DT >16.1. <A -HREF="policymgmt.html#AEN2929" ->Creating and Managing System Policies</A +HREF="pdb-mysql.html#AEN2566" +>Building</A ></DT -><DD -><DL -><DT ->16.1.1. <A -HREF="policymgmt.html#AEN2943" ->Windows 9x/Me Policies</A -></DT -><DT ->16.1.2. <A -HREF="policymgmt.html#AEN2955" ->Windows NT4 Style Policy Files</A -></DT -><DT ->16.1.3. <A -HREF="policymgmt.html#AEN2973" ->MS Windows 200x / XP Professional Policies</A -></DT -></DL -></DD ><DT >16.2. <A -HREF="policymgmt.html#AEN3002" ->Managing Account/User Policies</A +HREF="pdb-mysql.html#AEN2572" +>Configuring</A ></DT -><DD -><DL ><DT ->16.2.1. <A -HREF="policymgmt.html#AEN3017" ->With Windows NT4/200x</A +>16.3. <A +HREF="pdb-mysql.html#AEN2589" +>Using plaintext passwords or encrypted password</A ></DT ><DT ->16.2.2. <A -HREF="policymgmt.html#AEN3020" ->With a Samba PDC</A +>16.4. <A +HREF="pdb-mysql.html#AEN2594" +>Getting non-column data from the table</A ></DT ></DL ></DD -></DL -></DD ><DT >17. <A -HREF="profilemgmt.html" ->Desktop Profile Management</A +HREF="pdb-xml.html" +>Passdb XML plugin</A ></DT ><DD ><DL ><DT >17.1. <A -HREF="profilemgmt.html#AEN3035" ->Roaming Profiles</A +HREF="pdb-xml.html#AEN2613" +>Building</A ></DT -><DD -><DL -><DT ->17.1.1. <A -HREF="profilemgmt.html#AEN3042" ->Samba Configuration for Profile Handling</A -></DT -><DT ->17.1.2. <A -HREF="profilemgmt.html#AEN3077" ->Windows Client Profile Configuration Information</A -></DT -><DT ->17.1.3. <A -HREF="profilemgmt.html#AEN3197" ->Sharing Profiles between W9x/Me and NT4/200x/XP workstations</A -></DT -><DT ->17.1.4. <A -HREF="profilemgmt.html#AEN3204" ->Profile Migration from Windows NT4/200x Server to Samba</A -></DT -></DL -></DD ><DT >17.2. <A -HREF="profilemgmt.html#AEN3242" ->Mandatory profiles</A +HREF="pdb-xml.html#AEN2619" +>Usage</A ></DT -><DT ->17.3. <A -HREF="profilemgmt.html#AEN3249" ->Creating/Managing Group Profiles</A -></DT -><DT ->17.4. <A -HREF="profilemgmt.html#AEN3255" ->Default Profile for Windows Users</A -></DT -><DD -><DL -><DT ->17.4.1. <A -HREF="profilemgmt.html#AEN3259" ->MS Windows 9x/Me</A -></DT -><DT ->17.4.2. <A -HREF="profilemgmt.html#AEN3271" ->MS Windows NT4 Workstation</A -></DT -><DT ->17.4.3. <A -HREF="profilemgmt.html#AEN3325" ->MS Windows 200x/XP</A -></DT -></DL -></DD ></DL ></DD ><DT >18. <A -HREF="interdomaintrusts.html" ->Interdomain Trust Relationships</A +HREF="vfs.html" +>Stackable VFS modules</A ></DT ><DD ><DL ><DT >18.1. <A -HREF="interdomaintrusts.html#AEN3386" ->Trust Relationship Background</A +HREF="vfs.html#AEN2640" +>Introduction and configuration</A ></DT ><DT >18.2. <A -HREF="interdomaintrusts.html#AEN3395" ->MS Windows NT4 Trust Configuration</A +HREF="vfs.html#AEN2649" +>Included modules</A ></DT ><DD ><DL ><DT >18.2.1. <A -HREF="interdomaintrusts.html#AEN3398" ->NT4 as the Trusting Domain</A +HREF="vfs.html#AEN2651" +>audit</A ></DT ><DT >18.2.2. <A -HREF="interdomaintrusts.html#AEN3401" ->NT4 as the Trusted Domain</A +HREF="vfs.html#AEN2659" +>recycle</A +></DT +><DT +>18.2.3. <A +HREF="vfs.html#AEN2696" +>netatalk</A ></DT ></DL ></DD ><DT >18.3. <A -HREF="interdomaintrusts.html#AEN3405" ->Configuring Samba Domain Trusts</A +HREF="vfs.html#AEN2703" +>VFS modules available elsewhere</A ></DT ><DD ><DL ><DT >18.3.1. <A -HREF="interdomaintrusts.html#AEN3409" ->Samba3 as the Trusting Domain</A +HREF="vfs.html#AEN2707" +>DatabaseFS</A ></DT ><DT >18.3.2. <A -HREF="interdomaintrusts.html#AEN3416" ->Samba3 as the Trusted Domain</A +HREF="vfs.html#AEN2715" +>vscan</A ></DT ></DL ></DD @@ -700,325 +663,171 @@ HREF="interdomaintrusts.html#AEN3416" ></DD ><DT >19. <A -HREF="pam.html" ->PAM Configuration for Centrally Managed Authentication</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="pam.html#AEN3440" ->Samba and PAM</A +HREF="samba-ldap-howto.html#AEN2737" +>Purpose</A ></DT ><DT >19.2. <A -HREF="pam.html#AEN3491" ->Distributed Authentication</A +HREF="samba-ldap-howto.html#AEN2757" +>Introduction</A ></DT ><DT >19.3. <A -HREF="pam.html#AEN3496" ->PAM Configuration in smb.conf</A -></DT -></DL -></DD -><DT ->20. <A -HREF="vfs.html" ->Stackable VFS modules</A +HREF="samba-ldap-howto.html#AEN2786" +>Supported LDAP Servers</A ></DT -><DD -><DL ><DT ->20.1. <A -HREF="vfs.html#AEN3531" ->Introduction and configuration</A +>19.4. <A +HREF="samba-ldap-howto.html#AEN2791" +>Schema and Relationship to the RFC 2307 posixAccount</A ></DT ><DT ->20.2. <A -HREF="vfs.html#AEN3540" ->Included modules</A +>19.5. <A +HREF="samba-ldap-howto.html#AEN2803" +>Configuring Samba with LDAP</A ></DT ><DD ><DL ><DT ->20.2.1. <A -HREF="vfs.html#AEN3542" ->audit</A +>19.5.1. <A +HREF="samba-ldap-howto.html#AEN2805" +>OpenLDAP configuration</A ></DT ><DT ->20.2.2. <A -HREF="vfs.html#AEN3550" ->extd_audit</A -></DT -><DT ->20.2.3. <A -HREF="vfs.html#AEN3554" ->recycle</A -></DT -><DT ->20.2.4. <A -HREF="vfs.html#AEN3591" ->netatalk</A +>19.5.2. <A +HREF="samba-ldap-howto.html#AEN2822" +>Configuring Samba</A ></DT ></DL ></DD ><DT ->20.3. <A -HREF="vfs.html#AEN3598" ->VFS modules available elsewhere</A -></DT -><DD -><DL -><DT ->20.3.1. <A -HREF="vfs.html#AEN3602" ->DatabaseFS</A +>19.6. <A +HREF="samba-ldap-howto.html#AEN2850" +>Accounts and Groups management</A ></DT ><DT ->20.3.2. <A -HREF="vfs.html#AEN3610" ->vscan</A +>19.7. <A +HREF="samba-ldap-howto.html#AEN2855" +>Security and sambaAccount</A ></DT -></DL -></DD -></DL -></DD ><DT ->21. <A -HREF="msdfs.html" ->Hosting a Microsoft Distributed File System tree on Samba</A +>19.8. <A +HREF="samba-ldap-howto.html#AEN2875" +>LDAP specials attributes for sambaAccounts</A ></DT -><DD -><DL ><DT ->21.1. <A -HREF="msdfs.html#AEN3626" ->Instructions</A +>19.9. <A +HREF="samba-ldap-howto.html#AEN2945" +>Example LDIF Entries for a sambaAccount</A ></DT -><DD -><DL ><DT ->21.1.1. <A -HREF="msdfs.html#AEN3661" ->Notes</A +>19.10. <A +HREF="samba-ldap-howto.html#AEN2953" +>Comments</A ></DT ></DL ></DD -></DL -></DD -><DT ->22. <A -HREF="integrate-ms-networks.html" ->Integrating MS Windows networks with Samba</A -></DT -><DD -><DL ><DT ->22.1. <A -HREF="integrate-ms-networks.html#AEN3688" ->Name Resolution in a pure Unix/Linux world</A +>20. <A +HREF="cvs-access.html" +>HOWTO Access Samba source code via CVS</A ></DT ><DD ><DL ><DT ->22.1.1. <A -HREF="integrate-ms-networks.html#AEN3704" -><TT -CLASS="FILENAME" ->/etc/hosts</TT -></A -></DT -><DT ->22.1.2. <A -HREF="integrate-ms-networks.html#AEN3720" -><TT -CLASS="FILENAME" ->/etc/resolv.conf</TT -></A -></DT -><DT ->22.1.3. <A -HREF="integrate-ms-networks.html#AEN3731" -><TT -CLASS="FILENAME" ->/etc/host.conf</TT -></A -></DT -><DT ->22.1.4. <A -HREF="integrate-ms-networks.html#AEN3739" -><TT -CLASS="FILENAME" ->/etc/nsswitch.conf</TT -></A +>20.1. <A +HREF="cvs-access.html#AEN2964" +>Introduction</A ></DT -></DL -></DD ><DT ->22.2. <A -HREF="integrate-ms-networks.html#AEN3751" ->Name resolution as used within MS Windows networking</A +>20.2. <A +HREF="cvs-access.html#AEN2969" +>CVS Access to samba.org</A ></DT ><DD ><DL ><DT ->22.2.1. <A -HREF="integrate-ms-networks.html#AEN3763" ->The NetBIOS Name Cache</A -></DT -><DT ->22.2.2. <A -HREF="integrate-ms-networks.html#AEN3768" ->The LMHOSTS file</A -></DT -><DT ->22.2.3. <A -HREF="integrate-ms-networks.html#AEN3776" ->HOSTS file</A -></DT -><DT ->22.2.4. <A -HREF="integrate-ms-networks.html#AEN3781" ->DNS Lookup</A +>20.2.1. <A +HREF="cvs-access.html#AEN2972" +>Access via CVSweb</A ></DT ><DT ->22.2.5. <A -HREF="integrate-ms-networks.html#AEN3784" ->WINS Lookup</A +>20.2.2. <A +HREF="cvs-access.html#AEN2977" +>Access via cvs</A ></DT ></DL ></DD ></DL ></DD ><DT ->23. <A -HREF="improved-browsing.html" ->Improved browsing in samba</A -></DT -><DD -><DL -><DT ->23.1. <A -HREF="improved-browsing.html#AEN3804" ->Overview of browsing</A -></DT -><DT ->23.2. <A -HREF="improved-browsing.html#AEN3810" ->Browsing support in samba</A -></DT -><DT ->23.3. <A -HREF="improved-browsing.html#AEN3825" ->Problem resolution</A +>21. <A +HREF="groupmapping.html" +>Group mapping HOWTO</A ></DT ><DT ->23.4. <A -HREF="improved-browsing.html#AEN3837" ->Browsing across subnets</A +>22. <A +HREF="speed.html" +>Samba performance issues</A ></DT ><DD ><DL ><DT ->23.4.1. <A -HREF="improved-browsing.html#AEN3843" ->How does cross subnet browsing work ?</A -></DT -></DL -></DD -><DT ->23.5. <A -HREF="improved-browsing.html#AEN3878" ->Setting up a WINS server</A -></DT -><DT ->23.6. <A -HREF="improved-browsing.html#AEN3901" ->Setting up Browsing in a WORKGROUP</A -></DT -><DT ->23.7. <A -HREF="improved-browsing.html#AEN3927" ->Setting up Browsing in a DOMAIN</A -></DT -><DT ->23.8. <A -HREF="improved-browsing.html#BROWSE-FORCE-MASTER" ->Forcing samba to be the master</A -></DT -><DT ->23.9. <A -HREF="improved-browsing.html#AEN3962" ->Making samba the domain master</A -></DT -><DT ->23.10. <A -HREF="improved-browsing.html#AEN3984" ->Note about broadcast addresses</A -></DT -><DT ->23.11. <A -HREF="improved-browsing.html#AEN3987" ->Multiple interfaces</A -></DT -></DL -></DD -><DT ->24. <A -HREF="securing-samba.html" ->Securing Samba</A +>22.1. <A +HREF="speed.html#AEN3055" +>Comparisons</A ></DT -><DD -><DL ><DT ->24.1. <A -HREF="securing-samba.html#AEN4003" ->Introduction</A +>22.2. <A +HREF="speed.html#AEN3061" +>Socket options</A ></DT ><DT ->24.2. <A -HREF="securing-samba.html#AEN4006" ->Using host based protection</A +>22.3. <A +HREF="speed.html#AEN3068" +>Read size</A ></DT ><DT ->24.3. <A -HREF="securing-samba.html#AEN4016" ->Using interface protection</A +>22.4. <A +HREF="speed.html#AEN3073" +>Max xmit</A ></DT ><DT ->24.4. <A -HREF="securing-samba.html#AEN4025" ->Using a firewall</A +>22.5. <A +HREF="speed.html#AEN3078" +>Log level</A ></DT ><DT ->24.5. <A -HREF="securing-samba.html#AEN4032" ->Using a IPC$ share deny</A +>22.6. <A +HREF="speed.html#AEN3081" +>Read raw</A ></DT ><DT ->24.6. <A -HREF="securing-samba.html#AEN4041" ->Upgrading Samba</A +>22.7. <A +HREF="speed.html#AEN3086" +>Write raw</A ></DT -></DL -></DD ><DT ->25. <A -HREF="unicode.html" ->Unicode/Charsets</A +>22.8. <A +HREF="speed.html#AEN3090" +>Slow Clients</A ></DT -><DD -><DL ><DT ->25.1. <A -HREF="unicode.html#AEN4056" ->What are charsets and unicode?</A +>22.9. <A +HREF="speed.html#AEN3094" +>Slow Logins</A ></DT ><DT ->25.2. <A -HREF="unicode.html#AEN4065" ->Samba and charsets</A +>22.10. <A +HREF="speed.html#AEN3097" +>Client tuning</A ></DT ></DL ></DD @@ -1060,7 +869,7 @@ WIDTH="33%" ALIGN="right" VALIGN="top" ><A -HREF="unix-permissions.html" +HREF="integrate-ms-networks.html" ACCESSKEY="N" >Next</A ></TD @@ -1070,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" @@ -1080,7 +889,7 @@ VALIGN="top" WIDTH="33%" ALIGN="right" VALIGN="top" ->UNIX Permission Bits and Windows NT Access Control Lists</TD +>Integrating MS Windows networks with Samba</TD ></TR ></TABLE ></DIV diff --git a/docs/htmldocs/other-clients.html b/docs/htmldocs/other-clients.html index ac0cef9f14..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.7"><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="Portability" HREF="portability.html"><LINK REL="NEXT" -TITLE="How to compile SAMBA" -HREF="compiling.html"></HEAD +TITLE="Reporting Bugs" +HREF="bugreport.html"></HEAD ><BODY CLASS="CHAPTER" BGCOLOR="#FFFFFF" @@ -59,7 +60,7 @@ WIDTH="10%" ALIGN="right" VALIGN="bottom" ><A -HREF="compiling.html" +HREF="bugreport.html" ACCESSKEY="N" >Next</A ></TD @@ -72,9 +73,7 @@ WIDTH="100%"></DIV CLASS="CHAPTER" ><H1 ><A -NAME="OTHER-CLIENTS" -></A ->Chapter 30. 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="AEN4326" ->30.1. Macintosh clients?</A -></H1 +NAME="AEN3199">24.1. Macintosh clients?</H1 ><P >Yes. <A HREF="http://www.thursby.com/" @@ -128,18 +125,14 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN4335" ->30.2. OS2 Client</A -></H1 +NAME="AEN3208">24.2. OS2 Client</H1 ><DIV CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN4337" ->30.2.1. How can I configure OS/2 Warp Connect or - OS/2 Warp 4 as a client for Samba?</A -></H2 +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 found on <A @@ -195,10 +188,8 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN4352" ->30.2.2. How can I configure OS/2 Warp 3 (not Connect), - OS/2 1.2, 1.3 or 2.x for Samba?</A -></H2 +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 for OS/2 from @@ -239,10 +230,8 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN4361" ->30.2.3. Are there any other issues when OS/2 (any version) - is used as a client?</A -></H2 +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 Client Resource Browser", no Samba servers show up. This can @@ -261,10 +250,8 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN4365" ->30.2.4. How do I get printer driver download working - for OS/2 clients?</A -></H2 +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 world-readable. Copy your OS/2 driver files there. Note @@ -274,13 +261,17 @@ NAME="AEN4365" ><P >Install the NT driver first for that printer. Then, add to your smb.conf a parameter, os2 driver map = - <VAR + <TT CLASS="REPLACEABLE" ->filename</VAR +><I +>filename</I +></TT >". Then, in the file - specified by <VAR + specified by <TT CLASS="REPLACEABLE" ->filename</VAR +><I +>filename</I +></TT >, map the name of the NT driver name to the OS/2 driver name as follows:</P @@ -308,17 +299,13 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN4375" ->30.3. Windows for Workgroups</A -></H1 +NAME="AEN3248">24.3. Windows for Workgroups</H1 ><DIV CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN4377" ->30.3.1. Use latest TCP/IP stack from Microsoft</A -></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 @@ -338,9 +325,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN4382" ->30.3.2. Delete .pwl files after password change</A -></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 @@ -358,9 +343,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN4387" ->30.3.3. Configure WfW password handling</A -></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 @@ -377,9 +360,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN4391" ->30.3.4. Case handling of passwords</A -></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" @@ -390,30 +371,13 @@ CLASS="COMMAND" >password level</B > to specify what characters samba should try to uppercase when checking.</P ></DIV -><DIV -CLASS="SECT2" -><H2 -CLASS="SECT2" -><A -NAME="AEN4396" ->30.3.5. Use TCP/IP as default protocol</A -></H2 -><P ->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 ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN4399" ->30.4. Windows '95/'98</A -></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 @@ -459,9 +423,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN4415" ->30.5. Windows 2000 Service Pack 2</A -></H1 +NAME="AEN3285">24.5. Windows 2000 Service Pack 2</H1 ><P > There are several annoyances with Windows 2000 SP2. One of which @@ -526,49 +488,15 @@ for the profile. This default ACL includes </P CLASS="COMMAND" >DOMAIN\user "Full Control"</B ></P -><DIV -CLASS="NOTE" ><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 -><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 ->This bug does not occur when using winbind to -create accounts on the Samba host for Domain users.</P -></TD -></TR -></TABLE -></DIV -></DIV -><DIV -CLASS="SECT1" -><H1 -CLASS="SECT1" -><A -NAME="AEN4432" ->30.6. Windows NT 3.1</A -></H1 -><P ->If you have problems communicating across routers with Windows -NT 3.1 workstations, read <A -HREF="http://support.microsoft.com/default.aspx?scid=kb;[LN];Q103765" -TARGET="_top" ->this Microsoft Knowledge Base article</A ->. </P ></DIV ></DIV ><DIV @@ -605,7 +533,7 @@ WIDTH="33%" ALIGN="right" VALIGN="top" ><A -HREF="compiling.html" +HREF="bugreport.html" ACCESSKEY="N" >Next</A ></TD @@ -629,7 +557,7 @@ ACCESSKEY="U" WIDTH="33%" ALIGN="right" VALIGN="top" ->How to compile SAMBA</TD +>Reporting Bugs</TD ></TR ></TABLE ></DIV diff --git a/docs/htmldocs/p1346.html b/docs/htmldocs/p1346.html new file mode 100644 index 0000000000..e558561800 --- /dev/null +++ b/docs/htmldocs/p1346.html @@ -0,0 +1,917 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML +><HEAD +><TITLE +>Optional configuration</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="PREVIOUS" +TITLE="Samba as a NT4 domain member" +HREF="domain-security.html"><LINK +REL="NEXT" +TITLE="Integrating MS Windows networks with Samba" +HREF="integrate-ms-networks.html"></HEAD +><BODY +CLASS="PART" +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="domain-security.html" +ACCESSKEY="P" +>Prev</A +></TD +><TD +WIDTH="80%" +ALIGN="center" +VALIGN="bottom" +></TD +><TD +WIDTH="10%" +ALIGN="right" +VALIGN="bottom" +><A +HREF="integrate-ms-networks.html" +ACCESSKEY="N" +>Next</A +></TD +></TR +></TABLE +><HR +ALIGN="LEFT" +WIDTH="100%"></DIV +><DIV +CLASS="PART" +><A +NAME="AEN1346" +></A +><DIV +CLASS="TITLEPAGE" +><H1 +CLASS="TITLE" +>III. Optional configuration</H1 +><DIV +CLASS="PARTINTRO" +><A +NAME="AEN1348" +></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 +>10. <A +HREF="integrate-ms-networks.html" +>Integrating MS Windows networks with Samba</A +></DT +><DD +><DL +><DT +>10.1. <A +HREF="integrate-ms-networks.html#AEN1362" +>Agenda</A +></DT +><DT +>10.2. <A +HREF="integrate-ms-networks.html#AEN1384" +>Name Resolution in a pure Unix/Linux world</A +></DT +><DD +><DL +><DT +>10.2.1. <A +HREF="integrate-ms-networks.html#AEN1400" +><TT +CLASS="FILENAME" +>/etc/hosts</TT +></A +></DT +><DT +>10.2.2. <A +HREF="integrate-ms-networks.html#AEN1416" +><TT +CLASS="FILENAME" +>/etc/resolv.conf</TT +></A +></DT +><DT +>10.2.3. <A +HREF="integrate-ms-networks.html#AEN1427" +><TT +CLASS="FILENAME" +>/etc/host.conf</TT +></A +></DT +><DT +>10.2.4. <A +HREF="integrate-ms-networks.html#AEN1435" +><TT +CLASS="FILENAME" +>/etc/nsswitch.conf</TT +></A +></DT +></DL +></DD +><DT +>10.3. <A +HREF="integrate-ms-networks.html#AEN1447" +>Name resolution as used within MS Windows networking</A +></DT +><DD +><DL +><DT +>10.3.1. <A +HREF="integrate-ms-networks.html#AEN1459" +>The NetBIOS Name Cache</A +></DT +><DT +>10.3.2. <A +HREF="integrate-ms-networks.html#AEN1464" +>The LMHOSTS file</A +></DT +><DT +>10.3.3. <A +HREF="integrate-ms-networks.html#AEN1472" +>HOSTS file</A +></DT +><DT +>10.3.4. <A +HREF="integrate-ms-networks.html#AEN1477" +>DNS Lookup</A +></DT +><DT +>10.3.5. <A +HREF="integrate-ms-networks.html#AEN1480" +>WINS Lookup</A +></DT +></DL +></DD +><DT +>10.4. <A +HREF="integrate-ms-networks.html#AEN1492" +>How browsing functions and how to deploy stable and +dependable browsing using Samba</A +></DT +><DT +>10.5. <A +HREF="integrate-ms-networks.html#AEN1502" +>MS Windows security options and how to configure +Samba for seemless integration</A +></DT +><DD +><DL +><DT +>10.5.1. <A +HREF="integrate-ms-networks.html#AEN1530" +>Use MS Windows NT as an authentication server</A +></DT +><DT +>10.5.2. <A +HREF="integrate-ms-networks.html#AEN1538" +>Make Samba a member of an MS Windows NT security domain</A +></DT +><DT +>10.5.3. <A +HREF="integrate-ms-networks.html#AEN1555" +>Configure Samba as an authentication server</A +></DT +></DL +></DD +><DT +>10.6. <A +HREF="integrate-ms-networks.html#AEN1572" +>Conclusions</A +></DT +></DL +></DD +><DT +>11. <A +HREF="unix-permissions.html" +>UNIX Permission Bits and Windows NT Access Control Lists</A +></DT +><DD +><DL +><DT +>11.1. <A +HREF="unix-permissions.html#AEN1593" +>Viewing and changing UNIX permissions using the NT + security dialogs</A +></DT +><DT +>11.2. <A +HREF="unix-permissions.html#AEN1602" +>How to view file security on a Samba share</A +></DT +><DT +>11.3. <A +HREF="unix-permissions.html#AEN1613" +>Viewing file ownership</A +></DT +><DT +>11.4. <A +HREF="unix-permissions.html#AEN1633" +>Viewing file or directory permissions</A +></DT +><DD +><DL +><DT +>11.4.1. <A +HREF="unix-permissions.html#AEN1648" +>File Permissions</A +></DT +><DT +>11.4.2. <A +HREF="unix-permissions.html#AEN1662" +>Directory Permissions</A +></DT +></DL +></DD +><DT +>11.5. <A +HREF="unix-permissions.html#AEN1669" +>Modifying file or directory permissions</A +></DT +><DT +>11.6. <A +HREF="unix-permissions.html#AEN1691" +>Interaction with the standard Samba create mask + parameters</A +></DT +><DT +>11.7. <A +HREF="unix-permissions.html#AEN1755" +>Interaction with the standard Samba file attribute + mapping</A +></DT +></DL +></DD +><DT +>12. <A +HREF="pam.html" +>Configuring PAM for distributed but centrally +managed authentication</A +></DT +><DD +><DL +><DT +>12.1. <A +HREF="pam.html#AEN1776" +>Samba and PAM</A +></DT +><DT +>12.2. <A +HREF="pam.html#AEN1820" +>Distributed Authentication</A +></DT +><DT +>12.3. <A +HREF="pam.html#AEN1827" +>PAM Configuration in smb.conf</A +></DT +></DL +></DD +><DT +>13. <A +HREF="msdfs.html" +>Hosting a Microsoft Distributed File System tree on Samba</A +></DT +><DD +><DL +><DT +>13.1. <A +HREF="msdfs.html#AEN1847" +>Instructions</A +></DT +><DD +><DL +><DT +>13.1.1. <A +HREF="msdfs.html#AEN1882" +>Notes</A +></DT +></DL +></DD +></DL +></DD +><DT +>14. <A +HREF="printing.html" +>Printing Support</A +></DT +><DD +><DL +><DT +>14.1. <A +HREF="printing.html#AEN1908" +>Introduction</A +></DT +><DT +>14.2. <A +HREF="printing.html#AEN1930" +>Configuration</A +></DT +><DD +><DL +><DT +>14.2.1. <A +HREF="printing.html#AEN1938" +>Creating [print$]</A +></DT +><DT +>14.2.2. <A +HREF="printing.html#AEN1973" +>Setting Drivers for Existing Printers</A +></DT +><DT +>14.2.3. <A +HREF="printing.html#AEN1989" +>Support a large number of printers</A +></DT +><DT +>14.2.4. <A +HREF="printing.html#AEN2000" +>Adding New Printers via the Windows NT APW</A +></DT +><DT +>14.2.5. <A +HREF="printing.html#AEN2030" +>Samba and Printer Ports</A +></DT +></DL +></DD +><DT +>14.3. <A +HREF="printing.html#AEN2038" +>The Imprints Toolset</A +></DT +><DD +><DL +><DT +>14.3.1. <A +HREF="printing.html#AEN2042" +>What is Imprints?</A +></DT +><DT +>14.3.2. <A +HREF="printing.html#AEN2052" +>Creating Printer Driver Packages</A +></DT +><DT +>14.3.3. <A +HREF="printing.html#AEN2055" +>The Imprints server</A +></DT +><DT +>14.3.4. <A +HREF="printing.html#AEN2059" +>The Installation Client</A +></DT +></DL +></DD +><DT +>14.4. <A +HREF="printing.html#AEN2081" +>Diagnosis</A +></DT +><DD +><DL +><DT +>14.4.1. <A +HREF="printing.html#AEN2083" +>Introduction</A +></DT +><DT +>14.4.2. <A +HREF="printing.html#AEN2099" +>Debugging printer problems</A +></DT +><DT +>14.4.3. <A +HREF="printing.html#AEN2108" +>What printers do I have?</A +></DT +><DT +>14.4.4. <A +HREF="printing.html#AEN2116" +>Setting up printcap and print servers</A +></DT +><DT +>14.4.5. <A +HREF="printing.html#AEN2144" +>Job sent, no output</A +></DT +><DT +>14.4.6. <A +HREF="printing.html#AEN2155" +>Job sent, strange output</A +></DT +><DT +>14.4.7. <A +HREF="printing.html#AEN2167" +>Raw PostScript printed</A +></DT +><DT +>14.4.8. <A +HREF="printing.html#AEN2170" +>Advanced Printing</A +></DT +><DT +>14.4.9. <A +HREF="printing.html#AEN2173" +>Real debugging</A +></DT +></DL +></DD +></DL +></DD +><DT +>15. <A +HREF="securitylevels.html" +>Security levels</A +></DT +><DD +><DL +><DT +>15.1. <A +HREF="securitylevels.html#AEN2186" +>Introduction</A +></DT +><DT +>15.2. <A +HREF="securitylevels.html#AEN2197" +>More complete description of security levels</A +></DT +></DL +></DD +><DT +>16. <A +HREF="winbind.html" +>Unified Logons between Windows NT and UNIX using Winbind</A +></DT +><DD +><DL +><DT +>16.1. <A +HREF="winbind.html#AEN2249" +>Abstract</A +></DT +><DT +>16.2. <A +HREF="winbind.html#AEN2253" +>Introduction</A +></DT +><DT +>16.3. <A +HREF="winbind.html#AEN2266" +>What Winbind Provides</A +></DT +><DD +><DL +><DT +>16.3.1. <A +HREF="winbind.html#AEN2273" +>Target Uses</A +></DT +></DL +></DD +><DT +>16.4. <A +HREF="winbind.html#AEN2277" +>How Winbind Works</A +></DT +><DD +><DL +><DT +>16.4.1. <A +HREF="winbind.html#AEN2282" +>Microsoft Remote Procedure Calls</A +></DT +><DT +>16.4.2. <A +HREF="winbind.html#AEN2286" +>Name Service Switch</A +></DT +><DT +>16.4.3. <A +HREF="winbind.html#AEN2302" +>Pluggable Authentication Modules</A +></DT +><DT +>16.4.4. <A +HREF="winbind.html#AEN2310" +>User and Group ID Allocation</A +></DT +><DT +>16.4.5. <A +HREF="winbind.html#AEN2314" +>Result Caching</A +></DT +></DL +></DD +><DT +>16.5. <A +HREF="winbind.html#AEN2317" +>Installation and Configuration</A +></DT +><DD +><DL +><DT +>16.5.1. <A +HREF="winbind.html#AEN2324" +>Introduction</A +></DT +><DT +>16.5.2. <A +HREF="winbind.html#AEN2337" +>Requirements</A +></DT +><DT +>16.5.3. <A +HREF="winbind.html#AEN2351" +>Testing Things Out</A +></DT +></DL +></DD +><DT +>16.6. <A +HREF="winbind.html#AEN2566" +>Limitations</A +></DT +><DT +>16.7. <A +HREF="winbind.html#AEN2576" +>Conclusion</A +></DT +></DL +></DD +><DT +>17. <A +HREF="pdb-mysql.html" +>Passdb MySQL plugin</A +></DT +><DD +><DL +><DT +>17.1. <A +HREF="pdb-mysql.html#AEN2590" +>Building</A +></DT +><DT +>17.2. <A +HREF="pdb-mysql.html#AEN2596" +>Configuring</A +></DT +><DT +>17.3. <A +HREF="pdb-mysql.html#AEN2611" +>Using plaintext passwords or encrypted password</A +></DT +><DT +>17.4. <A +HREF="pdb-mysql.html#AEN2616" +>Getting non-column data from the table</A +></DT +></DL +></DD +><DT +>18. <A +HREF="pdb-xml.html" +>Passdb XML plugin</A +></DT +><DD +><DL +><DT +>18.1. <A +HREF="pdb-xml.html#AEN2635" +>Building</A +></DT +><DT +>18.2. <A +HREF="pdb-xml.html#AEN2641" +>Usage</A +></DT +></DL +></DD +><DT +>19. <A +HREF="samba-ldap-howto.html" +>Storing Samba's User/Machine Account information in an LDAP Directory</A +></DT +><DD +><DL +><DT +>19.1. <A +HREF="samba-ldap-howto.html#AEN2664" +>Purpose</A +></DT +><DT +>19.2. <A +HREF="samba-ldap-howto.html#AEN2684" +>Introduction</A +></DT +><DT +>19.3. <A +HREF="samba-ldap-howto.html#AEN2713" +>Supported LDAP Servers</A +></DT +><DT +>19.4. <A +HREF="samba-ldap-howto.html#AEN2718" +>Schema and Relationship to the RFC 2307 posixAccount</A +></DT +><DT +>19.5. <A +HREF="samba-ldap-howto.html#AEN2730" +>Configuring Samba with LDAP</A +></DT +><DD +><DL +><DT +>19.5.1. <A +HREF="samba-ldap-howto.html#AEN2732" +>OpenLDAP configuration</A +></DT +><DT +>19.5.2. <A +HREF="samba-ldap-howto.html#AEN2749" +>Configuring Samba</A +></DT +></DL +></DD +><DT +>19.6. <A +HREF="samba-ldap-howto.html#AEN2777" +>Accounts and Groups management</A +></DT +><DT +>19.7. <A +HREF="samba-ldap-howto.html#AEN2782" +>Security and sambaAccount</A +></DT +><DT +>19.8. <A +HREF="samba-ldap-howto.html#AEN2802" +>LDAP specials attributes for sambaAccounts</A +></DT +><DT +>19.9. <A +HREF="samba-ldap-howto.html#AEN2872" +>Example LDIF Entries for a sambaAccount</A +></DT +><DT +>19.10. <A +HREF="samba-ldap-howto.html#AEN2880" +>Comments</A +></DT +></DL +></DD +><DT +>20. <A +HREF="cvs-access.html" +>HOWTO Access Samba source code via CVS</A +></DT +><DD +><DL +><DT +>20.1. <A +HREF="cvs-access.html#AEN2891" +>Introduction</A +></DT +><DT +>20.2. <A +HREF="cvs-access.html#AEN2896" +>CVS Access to samba.org</A +></DT +><DD +><DL +><DT +>20.2.1. <A +HREF="cvs-access.html#AEN2899" +>Access via CVSweb</A +></DT +><DT +>20.2.2. <A +HREF="cvs-access.html#AEN2904" +>Access via cvs</A +></DT +></DL +></DD +></DL +></DD +><DT +>21. <A +HREF="groupmapping.html" +>Group mapping HOWTO</A +></DT +><DT +>22. <A +HREF="speed.html" +>Samba performance issues</A +></DT +><DD +><DL +><DT +>22.1. <A +HREF="speed.html#AEN2982" +>Comparisons</A +></DT +><DT +>22.2. <A +HREF="speed.html#AEN2988" +>Oplocks</A +></DT +><DD +><DL +><DT +>22.2.1. <A +HREF="speed.html#AEN2990" +>Overview</A +></DT +><DT +>22.2.2. <A +HREF="speed.html#AEN2998" +>Level2 Oplocks</A +></DT +><DT +>22.2.3. <A +HREF="speed.html#AEN3004" +>Old 'fake oplocks' option - deprecated</A +></DT +></DL +></DD +><DT +>22.3. <A +HREF="speed.html#AEN3008" +>Socket options</A +></DT +><DT +>22.4. <A +HREF="speed.html#AEN3015" +>Read size</A +></DT +><DT +>22.5. <A +HREF="speed.html#AEN3020" +>Max xmit</A +></DT +><DT +>22.6. <A +HREF="speed.html#AEN3025" +>Locking</A +></DT +><DT +>22.7. <A +HREF="speed.html#AEN3029" +>Share modes</A +></DT +><DT +>22.8. <A +HREF="speed.html#AEN3034" +>Log level</A +></DT +><DT +>22.9. <A +HREF="speed.html#AEN3037" +>Wide lines</A +></DT +><DT +>22.10. <A +HREF="speed.html#AEN3040" +>Read raw</A +></DT +><DT +>22.11. <A +HREF="speed.html#AEN3045" +>Write raw</A +></DT +><DT +>22.12. <A +HREF="speed.html#AEN3049" +>Read prediction</A +></DT +><DT +>22.13. <A +HREF="speed.html#AEN3056" +>Memory mapping</A +></DT +><DT +>22.14. <A +HREF="speed.html#AEN3061" +>Slow Clients</A +></DT +><DT +>22.15. <A +HREF="speed.html#AEN3065" +>Slow Logins</A +></DT +><DT +>22.16. <A +HREF="speed.html#AEN3068" +>Client tuning</A +></DT +><DT +>22.17. <A +HREF="speed.html#AEN3100" +>My Results</A +></DT +></DL +></DD +></DL +></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="domain-security.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="integrate-ms-networks.html" +ACCESSKEY="N" +>Next</A +></TD +></TR +><TR +><TD +WIDTH="33%" +ALIGN="left" +VALIGN="top" +>Samba as a NT4 domain member</TD +><TD +WIDTH="34%" +ALIGN="center" +VALIGN="top" +> </TD +><TD +WIDTH="33%" +ALIGN="right" +VALIGN="top" +>Integrating MS Windows networks with Samba</TD +></TR +></TABLE +></DIV +></BODY +></HTML +>
\ No newline at end of file diff --git a/docs/htmldocs/p18.html b/docs/htmldocs/p18.html new file mode 100644 index 0000000000..a8f2a3c53c --- /dev/null +++ b/docs/htmldocs/p18.html @@ -0,0 +1,438 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML +><HEAD +><TITLE +>General installation</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="PREVIOUS" +TITLE="SAMBA Project Documentation" +HREF="samba-howto-collection.html"><LINK +REL="NEXT" +TITLE="How to Install and Test SAMBA" +HREF="install.html"></HEAD +><BODY +CLASS="PART" +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="samba-howto-collection.html" +ACCESSKEY="P" +>Prev</A +></TD +><TD +WIDTH="80%" +ALIGN="center" +VALIGN="bottom" +></TD +><TD +WIDTH="10%" +ALIGN="right" +VALIGN="bottom" +><A +HREF="install.html" +ACCESSKEY="N" +>Next</A +></TD +></TR +></TABLE +><HR +ALIGN="LEFT" +WIDTH="100%"></DIV +><DIV +CLASS="PART" +><A +NAME="AEN18" +></A +><DIV +CLASS="TITLEPAGE" +><H1 +CLASS="TITLE" +>I. General installation</H1 +><DIV +CLASS="PARTINTRO" +><A +NAME="AEN20" +></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.html" +>How to Install and Test SAMBA</A +></DT +><DD +><DL +><DT +>1.1. <A +HREF="install.html#AEN25" +>Read the man pages</A +></DT +><DT +>1.2. <A +HREF="install.html#AEN35" +>Building the Binaries</A +></DT +><DT +>1.3. <A +HREF="install.html#AEN63" +>The all important step</A +></DT +><DT +>1.4. <A +HREF="install.html#AEN67" +>Create the smb configuration file.</A +></DT +><DT +>1.5. <A +HREF="install.html#AEN81" +>Test your config file with + <B +CLASS="COMMAND" +>testparm</B +></A +></DT +><DT +>1.6. <A +HREF="install.html#AEN89" +>Starting the smbd and nmbd</A +></DT +><DD +><DL +><DT +>1.6.1. <A +HREF="install.html#AEN99" +>Starting from inetd.conf</A +></DT +><DT +>1.6.2. <A +HREF="install.html#AEN128" +>Alternative: starting it as a daemon</A +></DT +></DL +></DD +><DT +>1.7. <A +HREF="install.html#AEN144" +>Try listing the shares available on your + server</A +></DT +><DT +>1.8. <A +HREF="install.html#AEN153" +>Try connecting with the unix client</A +></DT +><DT +>1.9. <A +HREF="install.html#AEN169" +>Try connecting from a DOS, WfWg, Win9x, WinNT, + Win2k, OS/2, etc... client</A +></DT +><DT +>1.10. <A +HREF="install.html#AEN183" +>What If Things Don't Work?</A +></DT +><DD +><DL +><DT +>1.10.1. <A +HREF="install.html#AEN188" +>Diagnosing Problems</A +></DT +><DT +>1.10.2. <A +HREF="install.html#AEN192" +>Scope IDs</A +></DT +><DT +>1.10.3. <A +HREF="install.html#AEN195" +>Choosing the Protocol Level</A +></DT +><DT +>1.10.4. <A +HREF="install.html#AEN204" +>Printing from UNIX to a Client PC</A +></DT +><DT +>1.10.5. <A +HREF="install.html#AEN209" +>Locking</A +></DT +><DT +>1.10.6. <A +HREF="install.html#AEN218" +>Mapping Usernames</A +></DT +></DL +></DD +></DL +></DD +><DT +>2. <A +HREF="improved-browsing.html" +>Improved browsing in samba</A +></DT +><DD +><DL +><DT +>2.1. <A +HREF="improved-browsing.html#AEN228" +>Overview of browsing</A +></DT +><DT +>2.2. <A +HREF="improved-browsing.html#AEN232" +>Browsing support in samba</A +></DT +><DT +>2.3. <A +HREF="improved-browsing.html#AEN241" +>Problem resolution</A +></DT +><DT +>2.4. <A +HREF="improved-browsing.html#AEN248" +>Browsing across subnets</A +></DT +><DD +><DL +><DT +>2.4.1. <A +HREF="improved-browsing.html#AEN253" +>How does cross subnet browsing work ?</A +></DT +></DL +></DD +><DT +>2.5. <A +HREF="improved-browsing.html#AEN288" +>Setting up a WINS server</A +></DT +><DT +>2.6. <A +HREF="improved-browsing.html#AEN307" +>Setting up Browsing in a WORKGROUP</A +></DT +><DT +>2.7. <A +HREF="improved-browsing.html#AEN325" +>Setting up Browsing in a DOMAIN</A +></DT +><DT +>2.8. <A +HREF="improved-browsing.html#AEN335" +>Forcing samba to be the master</A +></DT +><DT +>2.9. <A +HREF="improved-browsing.html#AEN344" +>Making samba the domain master</A +></DT +><DT +>2.10. <A +HREF="improved-browsing.html#AEN362" +>Note about broadcast addresses</A +></DT +><DT +>2.11. <A +HREF="improved-browsing.html#AEN365" +>Multiple interfaces</A +></DT +></DL +></DD +><DT +>3. <A +HREF="oplocks.html" +>Oplocks</A +></DT +><DD +><DL +><DT +>3.1. <A +HREF="oplocks.html#AEN377" +>What are oplocks?</A +></DT +></DL +></DD +><DT +>4. <A +HREF="browsing-quick.html" +>Quick Cross Subnet Browsing / Cross Workgroup Browsing guide</A +></DT +><DD +><DL +><DT +>4.1. <A +HREF="browsing-quick.html#AEN392" +>Discussion</A +></DT +><DT +>4.2. <A +HREF="browsing-quick.html#AEN400" +>Use of the "Remote Announce" parameter</A +></DT +><DT +>4.3. <A +HREF="browsing-quick.html#AEN414" +>Use of the "Remote Browse Sync" parameter</A +></DT +><DT +>4.4. <A +HREF="browsing-quick.html#AEN419" +>Use of WINS</A +></DT +><DT +>4.5. <A +HREF="browsing-quick.html#AEN430" +>Do NOT use more than one (1) protocol on MS Windows machines</A +></DT +><DT +>4.6. <A +HREF="browsing-quick.html#AEN436" +>Name Resolution Order</A +></DT +></DL +></DD +><DT +>5. <A +HREF="pwencrypt.html" +>LanMan and NT Password Encryption in Samba</A +></DT +><DD +><DL +><DT +>5.1. <A +HREF="pwencrypt.html#AEN472" +>Introduction</A +></DT +><DT +>5.2. <A +HREF="pwencrypt.html#AEN477" +>Important Notes About Security</A +></DT +><DD +><DL +><DT +>5.2.1. <A +HREF="pwencrypt.html#AEN496" +>Advantages of SMB Encryption</A +></DT +><DT +>5.2.2. <A +HREF="pwencrypt.html#AEN503" +>Advantages of non-encrypted passwords</A +></DT +></DL +></DD +><DT +>5.3. <A +HREF="pwencrypt.html#AEN512" +>The smbpasswd Command</A +></DT +></DL +></DD +></DL +></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="samba-howto-collection.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="install.html" +ACCESSKEY="N" +>Next</A +></TD +></TR +><TR +><TD +WIDTH="33%" +ALIGN="left" +VALIGN="top" +>SAMBA Project Documentation</TD +><TD +WIDTH="34%" +ALIGN="center" +VALIGN="top" +> </TD +><TD +WIDTH="33%" +ALIGN="right" +VALIGN="top" +>How to Install and Test SAMBA</TD +></TR +></TABLE +></DIV +></BODY +></HTML +>
\ No newline at end of file diff --git a/docs/htmldocs/p3106.html b/docs/htmldocs/p3106.html new file mode 100644 index 0000000000..9967d8fb59 --- /dev/null +++ b/docs/htmldocs/p3106.html @@ -0,0 +1,391 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML +><HEAD +><TITLE +>Appendixes</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="PREVIOUS" +TITLE="Samba performance issues" +HREF="speed.html"><LINK +REL="NEXT" +TITLE="Portability" +HREF="portability.html"></HEAD +><BODY +CLASS="PART" +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="portability.html" +ACCESSKEY="N" +>Next</A +></TD +></TR +></TABLE +><HR +ALIGN="LEFT" +WIDTH="100%"></DIV +><DIV +CLASS="PART" +><A +NAME="AEN3106" +></A +><DIV +CLASS="TITLEPAGE" +><H1 +CLASS="TITLE" +>IV. Appendixes</H1 +><DIV +CLASS="TOC" +><DL +><DT +><B +>Table of Contents</B +></DT +><DT +>23. <A +HREF="portability.html" +>Portability</A +></DT +><DD +><DL +><DT +>23.1. <A +HREF="portability.html#AEN3115" +>HPUX</A +></DT +><DT +>23.2. <A +HREF="portability.html#AEN3121" +>SCO Unix</A +></DT +><DT +>23.3. <A +HREF="portability.html#AEN3125" +>DNIX</A +></DT +><DT +>23.4. <A +HREF="portability.html#AEN3154" +>RedHat Linux Rembrandt-II</A +></DT +></DL +></DD +><DT +>24. <A +HREF="other-clients.html" +>Samba and other CIFS clients</A +></DT +><DD +><DL +><DT +>24.1. <A +HREF="other-clients.html#AEN3175" +>Macintosh clients?</A +></DT +><DT +>24.2. <A +HREF="other-clients.html#AEN3184" +>OS2 Client</A +></DT +><DD +><DL +><DT +>24.2.1. <A +HREF="other-clients.html#AEN3186" +>How can I configure OS/2 Warp Connect or + OS/2 Warp 4 as a client for Samba?</A +></DT +><DT +>24.2.2. <A +HREF="other-clients.html#AEN3201" +>How can I configure OS/2 Warp 3 (not Connect), + OS/2 1.2, 1.3 or 2.x for Samba?</A +></DT +><DT +>24.2.3. <A +HREF="other-clients.html#AEN3210" +>Are there any other issues when OS/2 (any version) + is used as a client?</A +></DT +><DT +>24.2.4. <A +HREF="other-clients.html#AEN3214" +>How do I get printer driver download working + for OS/2 clients?</A +></DT +></DL +></DD +><DT +>24.3. <A +HREF="other-clients.html#AEN3224" +>Windows for Workgroups</A +></DT +><DD +><DL +><DT +>24.3.1. <A +HREF="other-clients.html#AEN3226" +>Use latest TCP/IP stack from Microsoft</A +></DT +><DT +>24.3.2. <A +HREF="other-clients.html#AEN3231" +>Delete .pwl files after password change</A +></DT +><DT +>24.3.3. <A +HREF="other-clients.html#AEN3236" +>Configure WfW password handling</A +></DT +><DT +>24.3.4. <A +HREF="other-clients.html#AEN3240" +>Case handling of passwords</A +></DT +></DL +></DD +><DT +>24.4. <A +HREF="other-clients.html#AEN3245" +>Windows '95/'98</A +></DT +><DT +>24.5. <A +HREF="other-clients.html#AEN3261" +>Windows 2000 Service Pack 2</A +></DT +></DL +></DD +><DT +>25. <A +HREF="bugreport.html" +>Reporting Bugs</A +></DT +><DD +><DL +><DT +>25.1. <A +HREF="bugreport.html#AEN3285" +>Introduction</A +></DT +><DT +>25.2. <A +HREF="bugreport.html#AEN3295" +>General info</A +></DT +><DT +>25.3. <A +HREF="bugreport.html#AEN3301" +>Debug levels</A +></DT +><DT +>25.4. <A +HREF="bugreport.html#AEN3318" +>Internal errors</A +></DT +><DT +>25.5. <A +HREF="bugreport.html#AEN3328" +>Attaching to a running process</A +></DT +><DT +>25.6. <A +HREF="bugreport.html#AEN3331" +>Patches</A +></DT +></DL +></DD +><DT +>26. <A +HREF="diagnosis.html" +>Diagnosing your samba server</A +></DT +><DD +><DL +><DT +>26.1. <A +HREF="diagnosis.html#AEN3354" +>Introduction</A +></DT +><DT +>26.2. <A +HREF="diagnosis.html#AEN3359" +>Assumptions</A +></DT +><DT +>26.3. <A +HREF="diagnosis.html#AEN3369" +>Tests</A +></DT +><DD +><DL +><DT +>26.3.1. <A +HREF="diagnosis.html#AEN3371" +>Test 1</A +></DT +><DT +>26.3.2. <A +HREF="diagnosis.html#AEN3377" +>Test 2</A +></DT +><DT +>26.3.3. <A +HREF="diagnosis.html#AEN3383" +>Test 3</A +></DT +><DT +>26.3.4. <A +HREF="diagnosis.html#AEN3398" +>Test 4</A +></DT +><DT +>26.3.5. <A +HREF="diagnosis.html#AEN3403" +>Test 5</A +></DT +><DT +>26.3.6. <A +HREF="diagnosis.html#AEN3409" +>Test 6</A +></DT +><DT +>26.3.7. <A +HREF="diagnosis.html#AEN3417" +>Test 7</A +></DT +><DT +>26.3.8. <A +HREF="diagnosis.html#AEN3443" +>Test 8</A +></DT +><DT +>26.3.9. <A +HREF="diagnosis.html#AEN3460" +>Test 9</A +></DT +><DT +>26.3.10. <A +HREF="diagnosis.html#AEN3468" +>Test 10</A +></DT +><DT +>26.3.11. <A +HREF="diagnosis.html#AEN3474" +>Test 11</A +></DT +></DL +></DD +><DT +>26.4. <A +HREF="diagnosis.html#AEN3479" +>Still having troubles?</A +></DT +></DL +></DD +></DL +></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="portability.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" +> </TD +><TD +WIDTH="33%" +ALIGN="right" +VALIGN="top" +>Portability</TD +></TR +></TABLE +></DIV +></BODY +></HTML +>
\ No newline at end of file diff --git a/docs/htmldocs/p544.html b/docs/htmldocs/p544.html new file mode 100644 index 0000000000..502d978b5f --- /dev/null +++ b/docs/htmldocs/p544.html @@ -0,0 +1,388 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML +><HEAD +><TITLE +>Type of installation</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="PREVIOUS" +TITLE="LanMan and NT Password Encryption in Samba" +HREF="pwencrypt.html"><LINK +REL="NEXT" +TITLE="How to Configure Samba as a NT4 Primary Domain Controller" +HREF="samba-pdc.html"></HEAD +><BODY +CLASS="PART" +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="pwencrypt.html" +ACCESSKEY="P" +>Prev</A +></TD +><TD +WIDTH="80%" +ALIGN="center" +VALIGN="bottom" +></TD +><TD +WIDTH="10%" +ALIGN="right" +VALIGN="bottom" +><A +HREF="samba-pdc.html" +ACCESSKEY="N" +>Next</A +></TD +></TR +></TABLE +><HR +ALIGN="LEFT" +WIDTH="100%"></DIV +><DIV +CLASS="PART" +><A +NAME="AEN544" +></A +><DIV +CLASS="TITLEPAGE" +><H1 +CLASS="TITLE" +>II. Type of installation</H1 +><DIV +CLASS="PARTINTRO" +><A +NAME="AEN546" +></A +><H1 +>Introduction</H1 +><P +>This part contains information on using samba in a (NT 4 or ADS) domain. +If you wish to run samba as a domain member or DC, read the appropriate chapter in +this part.</P +></DIV +><DIV +CLASS="TOC" +><DL +><DT +><B +>Table of Contents</B +></DT +><DT +>6. <A +HREF="samba-pdc.html" +>How to Configure Samba as a NT4 Primary Domain Controller</A +></DT +><DD +><DL +><DT +>6.1. <A +HREF="samba-pdc.html#AEN566" +>Prerequisite Reading</A +></DT +><DT +>6.2. <A +HREF="samba-pdc.html#AEN572" +>Background</A +></DT +><DT +>6.3. <A +HREF="samba-pdc.html#AEN611" +>Configuring the Samba Domain Controller</A +></DT +><DT +>6.4. <A +HREF="samba-pdc.html#AEN654" +>Creating Machine Trust Accounts and Joining Clients to the +Domain</A +></DT +><DD +><DL +><DT +>6.4.1. <A +HREF="samba-pdc.html#AEN673" +>Manual Creation of Machine Trust Accounts</A +></DT +><DT +>6.4.2. <A +HREF="samba-pdc.html#AEN714" +>"On-the-Fly" Creation of Machine Trust Accounts</A +></DT +><DT +>6.4.3. <A +HREF="samba-pdc.html#AEN723" +>Joining the Client to the Domain</A +></DT +></DL +></DD +><DT +>6.5. <A +HREF="samba-pdc.html#AEN738" +>Common Problems and Errors</A +></DT +><DT +>6.6. <A +HREF="samba-pdc.html#AEN786" +>System Policies and Profiles</A +></DT +><DT +>6.7. <A +HREF="samba-pdc.html#AEN830" +>What other help can I get?</A +></DT +><DT +>6.8. <A +HREF="samba-pdc.html#AEN944" +>Domain Control for Windows 9x/ME</A +></DT +><DD +><DL +><DT +>6.8.1. <A +HREF="samba-pdc.html#AEN970" +>Configuration Instructions: Network Logons</A +></DT +><DT +>6.8.2. <A +HREF="samba-pdc.html#AEN989" +>Configuration Instructions: Setting up Roaming User Profiles</A +></DT +></DL +></DD +><DT +>6.9. <A +HREF="samba-pdc.html#AEN1082" +>DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba</A +></DT +></DL +></DD +><DT +>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 +>7.1. <A +HREF="samba-bdc.html#AEN1118" +>Prerequisite Reading</A +></DT +><DT +>7.2. <A +HREF="samba-bdc.html#AEN1122" +>Background</A +></DT +><DT +>7.3. <A +HREF="samba-bdc.html#AEN1130" +>What qualifies a Domain Controller on the network?</A +></DT +><DD +><DL +><DT +>7.3.1. <A +HREF="samba-bdc.html#AEN1133" +>How does a Workstation find its domain controller?</A +></DT +><DT +>7.3.2. <A +HREF="samba-bdc.html#AEN1136" +>When is the PDC needed?</A +></DT +></DL +></DD +><DT +>7.4. <A +HREF="samba-bdc.html#AEN1139" +>Can Samba be a Backup Domain Controller?</A +></DT +><DT +>7.5. <A +HREF="samba-bdc.html#AEN1143" +>How do I set up a Samba BDC?</A +></DT +><DD +><DL +><DT +>7.5.1. <A +HREF="samba-bdc.html#AEN1160" +>How do I replicate the smbpasswd file?</A +></DT +></DL +></DD +></DL +></DD +><DT +>8. <A +HREF="ads.html" +>Samba as a ADS domain member</A +></DT +><DD +><DL +><DT +>8.1. <A +HREF="ads.html#AEN1178" +>Installing the required packages for Debian</A +></DT +><DT +>8.2. <A +HREF="ads.html#AEN1184" +>Installing the required packages for RedHat</A +></DT +><DT +>8.3. <A +HREF="ads.html#AEN1193" +>Compile Samba</A +></DT +><DT +>8.4. <A +HREF="ads.html#AEN1205" +>Setup your /etc/krb5.conf</A +></DT +><DT +>8.5. <A +HREF="ads.html#AEN1215" +>Create the computer account</A +></DT +><DD +><DL +><DT +>8.5.1. <A +HREF="ads.html#AEN1219" +>Possible errors</A +></DT +></DL +></DD +><DT +>8.6. <A +HREF="ads.html#AEN1231" +>Test your server setup</A +></DT +><DT +>8.7. <A +HREF="ads.html#AEN1236" +>Testing with smbclient</A +></DT +><DT +>8.8. <A +HREF="ads.html#AEN1239" +>Notes</A +></DT +></DL +></DD +><DT +>9. <A +HREF="domain-security.html" +>Samba as a NT4 domain member</A +></DT +><DD +><DL +><DT +>9.1. <A +HREF="domain-security.html#AEN1261" +>Joining an NT Domain with Samba 2.2</A +></DT +><DT +>9.2. <A +HREF="domain-security.html#AEN1325" +>Samba and Windows 2000 Domains</A +></DT +><DT +>9.3. <A +HREF="domain-security.html#AEN1330" +>Why is this better than security = server?</A +></DT +></DL +></DD +></DL +></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="pwencrypt.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="samba-pdc.html" +ACCESSKEY="N" +>Next</A +></TD +></TR +><TR +><TD +WIDTH="33%" +ALIGN="left" +VALIGN="top" +>LanMan and NT Password Encryption in Samba</TD +><TD +WIDTH="34%" +ALIGN="center" +VALIGN="top" +> </TD +><TD +WIDTH="33%" +ALIGN="right" +VALIGN="top" +>How to Configure Samba as a NT4 Primary Domain Controller</TD +></TR +></TABLE +></DIV +></BODY +></HTML +>
\ No newline at end of file diff --git a/docs/htmldocs/pam.html b/docs/htmldocs/pam.html index a4530aa0a1..ba2bf6c922 100644 --- a/docs/htmldocs/pam.html +++ b/docs/htmldocs/pam.html @@ -2,22 +2,24 @@ <HTML ><HEAD ><TITLE ->PAM Configuration for Centrally Managed Authentication</TITLE +>Configuring PAM for distributed but centrally +managed authentication</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><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="Advanced Configuration" +TITLE="Optional configuration" HREF="optional.html"><LINK REL="PREVIOUS" -TITLE="Interdomain Trust Relationships" -HREF="interdomaintrusts.html"><LINK +TITLE="UNIX Permission Bits and Windows NT Access Control Lists" +HREF="unix-permissions.html"><LINK REL="NEXT" -TITLE="Stackable VFS modules" -HREF="vfs.html"></HEAD +TITLE="Hosting a Microsoft Distributed File System tree on Samba" +HREF="msdfs.html"></HEAD ><BODY CLASS="CHAPTER" BGCOLOR="#FFFFFF" @@ -45,7 +47,7 @@ WIDTH="10%" ALIGN="left" VALIGN="bottom" ><A -HREF="interdomaintrusts.html" +HREF="unix-permissions.html" ACCESSKEY="P" >Prev</A ></TD @@ -59,7 +61,7 @@ WIDTH="10%" ALIGN="right" VALIGN="bottom" ><A -HREF="vfs.html" +HREF="msdfs.html" ACCESSKEY="N" >Next</A ></TD @@ -72,17 +74,14 @@ WIDTH="100%"></DIV CLASS="CHAPTER" ><H1 ><A -NAME="PAM" -></A ->Chapter 19. PAM Configuration for Centrally Managed Authentication</H1 +NAME="PAM">Chapter 12. Configuring PAM for distributed but centrally +managed authentication</H1 ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3440" ->19.1. Samba and PAM</A -></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 @@ -117,45 +116,6 @@ or by editing individual files that are located in <TT CLASS="FILENAME" >/etc/pam.d</TT >.</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 -> If the PAM authentication module (loadable link library file) is located in the - default location then it is not necessary to specify the path. In the case of - Linux, the default location is <TT -CLASS="FILENAME" ->/lib/security</TT ->. If the module - is located other than default then the path may be specified as: - - <PRE -CLASS="PROGRAMLISTING" -> auth required /other_path/pam_strange_module.so - </PRE -> - </P -></TD -></TR -></TABLE -></DIV ><P >The following is an example <TT CLASS="FILENAME" @@ -171,46 +131,40 @@ CLASS="FILENAME" ><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 +>#%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 -><SAMP -CLASS="PROMPT" ->$</SAMP -><KBD -CLASS="USERINPUT" ->/bin/ls /lib/security</KBD -> -<PRE +><PRE CLASS="PROGRAMLISTING" -> 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 +>$ /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 @@ -273,13 +227,13 @@ 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 +>#%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 @@ -290,13 +244,13 @@ CLASS="FILENAME" ><P ><PRE CLASS="PROGRAMLISTING" -> #%PAM-1.0 - # The PAM configuration file for the `samba' service - # - auth required pam_pwdb.so nullok nodelay shadow audit - account required pam_pwdb.so audit nodelay - session required pam_pwdb.so nodelay - password required pam_pwdb.so shadow md5</PRE +>#%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 @@ -307,36 +261,16 @@ program.</P ><P ><PRE CLASS="PROGRAMLISTING" -> #%PAM-1.0 - # The PAM configuration file for the `samba' service - # - auth required pam_smbpass.so nodelay - account required pam_pwdb.so audit nodelay - session required pam_pwdb.so nodelay - password required pam_smbpass.so nodelay smbconf=/etc/samba.d/smb.conf</PRE +>#%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 -><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 ->PAM allows stacking of authentication mechanisms. It is +>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 @@ -353,19 +287,13 @@ CLASS="FILENAME" 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 -></TD -></TR -></TABLE -></DIV ></DIV ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3491" ->19.2. Distributed Authentication</A -></H1 +NAME="AEN1832">12.2. Distributed Authentication</H1 ><P >The astute administrator will realize from this that the combination of <TT @@ -375,9 +303,16 @@ CLASS="FILENAME" <B CLASS="COMMAND" >winbindd</B ->, and a distributed -passdb backend, such as ldap, will allow the establishment of a -centrally managed, distributed +>, 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 @@ -389,9 +324,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3496" ->19.3. PAM Configuration in smb.conf</A -></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" @@ -400,10 +333,10 @@ TARGET="_top" >. The following is from the on-line help for this option in SWAT;</P ><P ->When Samba is configured to enable PAM support (i.e. -<CODE +>When Samba 2.2 is configure to enable PAM support (i.e. +<TT CLASS="CONSTANT" ->--with-pam</CODE +>--with-pam</TT >), this parameter will control whether or not Samba should obey PAM's account and session management directives. The default behavior @@ -441,7 +374,7 @@ WIDTH="33%" ALIGN="left" VALIGN="top" ><A -HREF="interdomaintrusts.html" +HREF="unix-permissions.html" ACCESSKEY="P" >Prev</A ></TD @@ -459,7 +392,7 @@ WIDTH="33%" ALIGN="right" VALIGN="top" ><A -HREF="vfs.html" +HREF="msdfs.html" ACCESSKEY="N" >Next</A ></TD @@ -469,7 +402,7 @@ ACCESSKEY="N" WIDTH="33%" ALIGN="left" VALIGN="top" ->Interdomain Trust Relationships</TD +>UNIX Permission Bits and Windows NT Access Control Lists</TD ><TD WIDTH="34%" ALIGN="center" @@ -483,7 +416,7 @@ ACCESSKEY="U" WIDTH="33%" ALIGN="right" VALIGN="top" ->Stackable VFS modules</TD +>Hosting a Microsoft Distributed File System tree on Samba</TD ></TR ></TABLE ></DIV diff --git a/docs/htmldocs/pdb-mysql.html b/docs/htmldocs/pdb-mysql.html new file mode 100644 index 0000000000..abca946f6f --- /dev/null +++ b/docs/htmldocs/pdb-mysql.html @@ -0,0 +1,288 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML +><HEAD +><TITLE +>Passdb MySQL plugin</TITLE +><META +NAME="GENERATOR" +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 +REL="PREVIOUS" +TITLE="Unified Logons between Windows NT and UNIX using Winbind" +HREF="winbind.html"><LINK +REL="NEXT" +TITLE="Passdb XML plugin" +HREF="pdb-xml.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="winbind.html" +ACCESSKEY="P" +>Prev</A +></TD +><TD +WIDTH="80%" +ALIGN="center" +VALIGN="bottom" +></TD +><TD +WIDTH="10%" +ALIGN="right" +VALIGN="bottom" +><A +HREF="pdb-xml.html" +ACCESSKEY="N" +>Next</A +></TD +></TR +></TABLE +><HR +ALIGN="LEFT" +WIDTH="100%"></DIV +><DIV +CLASS="CHAPTER" +><H1 +><A +NAME="PDB-MYSQL">Chapter 16. Passdb MySQL plugin</H1 +><DIV +CLASS="SECT1" +><H1 +CLASS="SECT1" +><A +NAME="AEN2566">16.1. Building</H1 +><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="SECT1" +><H1 +CLASS="SECT1" +><A +NAME="AEN2572">16.2. Configuring</H1 +><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 +><P +><SPAN +CLASS="emphasis" +><I +CLASS="EMPHASIS" +>WARNING: 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.</I +></SPAN +></P +><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="SECT1" +><H1 +CLASS="SECT1" +><A +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 +>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="SECT1" +><H1 +CLASS="SECT1" +><A +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 +>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="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="winbind.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="pdb-xml.html" +ACCESSKEY="N" +>Next</A +></TD +></TR +><TR +><TD +WIDTH="33%" +ALIGN="left" +VALIGN="top" +>Unified Logons between Windows NT and UNIX using Winbind</TD +><TD +WIDTH="34%" +ALIGN="center" +VALIGN="top" +><A +HREF="optional.html" +ACCESSKEY="U" +>Up</A +></TD +><TD +WIDTH="33%" +ALIGN="right" +VALIGN="top" +>Passdb XML plugin</TD +></TR +></TABLE +></DIV +></BODY +></HTML +>
\ No newline at end of file diff --git a/docs/htmldocs/pdb-xml.html b/docs/htmldocs/pdb-xml.html new file mode 100644 index 0000000000..4d300d7be0 --- /dev/null +++ b/docs/htmldocs/pdb-xml.html @@ -0,0 +1,184 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML +><HEAD +><TITLE +>Passdb XML plugin</TITLE +><META +NAME="GENERATOR" +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 +REL="PREVIOUS" +TITLE="Passdb MySQL plugin" +HREF="pdb-mysql.html"><LINK +REL="NEXT" +TITLE="Stackable VFS modules" +HREF="vfs.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="pdb-mysql.html" +ACCESSKEY="P" +>Prev</A +></TD +><TD +WIDTH="80%" +ALIGN="center" +VALIGN="bottom" +></TD +><TD +WIDTH="10%" +ALIGN="right" +VALIGN="bottom" +><A +HREF="vfs.html" +ACCESSKEY="N" +>Next</A +></TD +></TR +></TABLE +><HR +ALIGN="LEFT" +WIDTH="100%"></DIV +><DIV +CLASS="CHAPTER" +><H1 +><A +NAME="PDB-XML">Chapter 17. Passdb XML plugin</H1 +><DIV +CLASS="SECT1" +><H1 +CLASS="SECT1" +><A +NAME="AEN2613">17.1. Building</H1 +><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="SECT1" +><H1 +CLASS="SECT1" +><A +NAME="AEN2619">17.2. Usage</H1 +><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 +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="pdb-mysql.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="vfs.html" +ACCESSKEY="N" +>Next</A +></TD +></TR +><TR +><TD +WIDTH="33%" +ALIGN="left" +VALIGN="top" +>Passdb MySQL plugin</TD +><TD +WIDTH="34%" +ALIGN="center" +VALIGN="top" +><A +HREF="optional.html" +ACCESSKEY="U" +>Up</A +></TD +><TD +WIDTH="33%" +ALIGN="right" +VALIGN="top" +>Stackable VFS modules</TD +></TR +></TABLE +></DIV +></BODY +></HTML +>
\ No newline at end of file diff --git a/docs/htmldocs/pdbedit.8.html b/docs/htmldocs/pdbedit.8.html index 5fb41fba4b..7b85e2bb80 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.7"></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,30 +28,26 @@ 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] [-g] [-b passdb-backend] [-g] [-d debuglevel] [-s configfile] [-P account-policy] [-C 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] [-g] [-b passdb-backend] [-d debuglevel] [-s configfile] [-P account-policy] [-V value]</P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN32" +NAME="AEN31" ></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 >The pdbedit program is used to manage the users accounts @@ -70,7 +65,7 @@ CLASS="REFENTRYTITLE" ><DIV CLASS="REFSECT1" ><A -NAME="AEN41" +NAME="AEN38" ></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,20 +287,32 @@ 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 ><DD ><P >This option may only be used in conjunction - with the <VAR + with the <TT CLASS="PARAMETER" ->-a</VAR +><I +>-a</I +></TT > option. It will make pdbedit to add a machine trust account instead of a user account (-u username will provide the machine name).</P @@ -339,35 +372,19 @@ CLASS="COMMAND" >-g</DT ><DD ><P ->If you specify <VAR -CLASS="PARAMETER" ->-g</VAR ->, - then <VAR -CLASS="PARAMETER" ->-i in-backend -e out-backend</VAR -> - applies to the group mapping instead of the user database. - - </P -><P ->This option will ease migration from one passdb backend to - another and will ease backing up.</P -></DD -><DT ->-g</DT -><DD -><P ->If you specify <VAR +>If you specify <TT CLASS="PARAMETER" ->-g</VAR +><I +>-g</I +></TT >, - then <VAR + then <TT CLASS="PARAMETER" ->-i in-backend -e out-backend</VAR +><I +>-i in-backend -e out-backend</I +></TT > applies to the group mapping instead of the user database. - </P ><P >This option will ease migration from one passdb backend to @@ -399,77 +416,65 @@ 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 ->-C account-policy-value</DT +>-V account-policy-value</DT ><DD ><P >Sets an account policy to a specified value. This option may only be used in conjunction - with the <VAR + with the <TT CLASS="PARAMETER" ->-P</VAR +><I +>-P</I +></TT > option. </P ><P >Example: <B CLASS="COMMAND" ->pdbedit -P "bad lockout attempt" -C 3</B +>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 ->-h|--help</DT -><DD -><P ->Print a summary of command line options.</P -></DD -><DT ->-V</DT -><DD -><P ->Prints the version number for -<B -CLASS="COMMAND" ->smbd</B ->.</P -></DD -><DT ->-s <configuration file></DT -><DD -><P ->The file specified contains the -configuration details required by the server. The -information in this file includes server-specific -information such as what printcap file to use, as well -as descriptions of all the services that the server is -to provide. See <A -HREF="smb.conf.5.html" -TARGET="_top" -><TT -CLASS="FILENAME" ->smb.conf(5)</TT -></A -> for more information. -The default configuration file name is determined at -compile time.</P -></DD -><DT >-d|--debug=debuglevel</DT ><DD ><P -><VAR +><TT CLASS="REPLACEABLE" ->debuglevel</VAR +><I +>debuglevel</I +></TT > is an integer from 0 to 10. The default value if this parameter is not specified is zero.</P @@ -503,15 +508,30 @@ CLASS="FILENAME" > file.</P ></DD ><DT ->-l|--logfile=logbasename</DT +>-h|--help</DT +><DD +><P +>Print a summary of command line options.</P +></DD +><DT +>-s <configuration file></DT ><DD ><P ->File name for log/debug files. The extension -<CODE -CLASS="CONSTANT" ->".client"</CODE -> will be appended. The log file is -never removed by the client.</P +>The file specified contains the +configuration details required by the server. The +information in this file includes server-specific +information such as what printcap file to use, as well +as descriptions of all the services that the server is +to provide. See <A +HREF="smb.conf.5.html" +TARGET="_top" +><TT +CLASS="FILENAME" +>smb.conf(5)</TT +></A +> for more information. +The default configuration file name is determined at +compile time.</P ></DD ></DL ></DIV @@ -519,7 +539,7 @@ never removed by the client.</P ><DIV CLASS="REFSECT1" ><A -NAME="AEN210" +NAME="AEN190" ></A ><H2 >NOTES</H2 @@ -529,7 +549,7 @@ NAME="AEN210" ><DIV CLASS="REFSECT1" ><A -NAME="AEN213" +NAME="AEN193" ></A ><H2 >VERSION</H2 @@ -540,29 +560,27 @@ NAME="AEN213" ><DIV CLASS="REFSECT1" ><A -NAME="AEN216" +NAME="AEN196" ></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="AEN225" +NAME="AEN201" ></A ><H2 >AUTHOR</H2 @@ -574,14 +592,14 @@ NAME="AEN225" ><P >The original Samba man pages were written by Karl Auer. The man page sources were converted to YODL format (another - excellent piece of Open Source software, available at <A + excellent piece of Open Source software, available at + <A HREF="ftp://ftp.icce.rug.nl/pub/unix/" TARGET="_top" > ftp://ftp.icce.rug.nl/pub/unix/</A >) and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for - Samba 2.2 was done by Gerald Carter. 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 52788e2f0a..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.7"><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="Appendixes" HREF="appendixes.html"><LINK REL="PREVIOUS" -TITLE="Samba performance issues" -HREF="speed.html"><LINK +TITLE="Appendixes" +HREF="appendixes.html"><LINK REL="NEXT" TITLE="Samba and other CIFS clients" HREF="other-clients.html"></HEAD @@ -45,7 +46,7 @@ WIDTH="10%" ALIGN="left" VALIGN="bottom" ><A -HREF="speed.html" +HREF="appendixes.html" ACCESSKEY="P" >Prev</A ></TD @@ -72,9 +73,7 @@ WIDTH="100%"></DIV CLASS="CHAPTER" ><H1 ><A -NAME="PORTABILITY" -></A ->Chapter 29. 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="AEN4249" ->29.1. HPUX</A -></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="AEN4255" ->29.2. SCO Unix</A -></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="AEN4259" ->29.3. DNIX</A -></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="AEN4288" ->29.4. RedHat Linux Rembrandt-II</A -></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: @@ -257,60 +248,6 @@ is the master browse list holder and who is the master browser.</P >Corrective Action: Delete the entry after the word loopback in the line starting 127.0.0.1</P ></DIV -><DIV -CLASS="SECT1" -><H1 -CLASS="SECT1" -><A -NAME="AEN4294" ->29.5. AIX</A -></H1 -><DIV -CLASS="SECT2" -><H2 -CLASS="SECT2" -><A -NAME="AEN4296" ->29.5.1. Sequential Read Ahead</A -></H2 -><P ->Disabling Sequential Read Ahead using <KBD -CLASS="USERINPUT" ->vmtune -r 0</KBD -> improves -samba performance significally.</P -></DIV -></DIV -><DIV -CLASS="SECT1" -><H1 -CLASS="SECT1" -><A -NAME="AEN4300" ->29.6. Solaris</A -></H1 -><P ->Some people have been experiencing problems with F_SETLKW64/fcntl -when running samba on solaris. The built in file locking mechanism was -not scalable. Performance would degrade to the point where processes would -get into loops of trying to lock a file. It woul try a lock, then fail, -then try again. The lock attempt was failing before the grant was -occurring. So the visible manifestation of this would be a handful of -processes stealing all of the CPU, and when they were trussed they would -be stuck if F_SETLKW64 loops.</P -><P ->Sun released patches for Solaris 2.6, 8, and 9. The patch for Solaris 7 -has not been released yet.</P -><P ->The patch revision for 2.6 is 105181-34 -for 8 is 108528-19 -and for 9 is 112233-04</P -><P ->After the install of these patches it is recommended to reconfigure -and rebuild samba.</P -><P ->Thanks to Joe Meslovich for reporting</P -></DIV ></DIV ><DIV CLASS="NAVFOOTER" @@ -328,7 +265,7 @@ WIDTH="33%" ALIGN="left" VALIGN="top" ><A -HREF="speed.html" +HREF="appendixes.html" ACCESSKEY="P" >Prev</A ></TD @@ -356,7 +293,7 @@ ACCESSKEY="N" WIDTH="33%" ALIGN="left" VALIGN="top" ->Samba performance issues</TD +>Appendixes</TD ><TD WIDTH="34%" ALIGN="center" diff --git a/docs/htmldocs/printing.html b/docs/htmldocs/printing.html index a123992b36..46ebbcdf84 100644 --- a/docs/htmldocs/printing.html +++ b/docs/htmldocs/printing.html @@ -5,19 +5,20 @@ >Printing Support</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><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="Advanced Configuration" +TITLE="Optional configuration" HREF="optional.html"><LINK REL="PREVIOUS" -TITLE="Configuring Group Mapping" -HREF="groupmapping.html"><LINK +TITLE="Hosting a Microsoft Distributed File System tree on Samba" +HREF="msdfs.html"><LINK REL="NEXT" -TITLE="CUPS Printing Support" -HREF="cups-printing.html"></HEAD +TITLE="Unified Logons between Windows NT and UNIX using Winbind" +HREF="winbind.html"></HEAD ><BODY CLASS="CHAPTER" BGCOLOR="#FFFFFF" @@ -45,7 +46,7 @@ WIDTH="10%" ALIGN="left" VALIGN="bottom" ><A -HREF="groupmapping.html" +HREF="msdfs.html" ACCESSKEY="P" >Prev</A ></TD @@ -59,7 +60,7 @@ WIDTH="10%" ALIGN="right" VALIGN="bottom" ><A -HREF="cups-printing.html" +HREF="winbind.html" ACCESSKEY="N" >Next</A ></TD @@ -72,17 +73,13 @@ WIDTH="100%"></DIV CLASS="CHAPTER" ><H1 ><A -NAME="PRINTING" -></A ->Chapter 12. Printing Support</H1 +NAME="PRINTING">Chapter 14. Printing Support</H1 ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1736" ->12.1. Introduction</A -></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="AEN1758" ->12.2. Configuration</A -></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 @@ -204,15 +199,19 @@ 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 <VAR +parameter named <TT CLASS="PARAMETER" ->printer driver location</VAR +><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 <VAR +parameter named <TT CLASS="PARAMETER" ->printer driver</VAR +><I +>printer driver</I +></TT > provided a means of defining the printer driver name to be sent to the client.</P @@ -225,9 +224,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1766" ->12.2.1. Creating [print$]</A -></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$]. @@ -266,9 +263,11 @@ CLASS="PROGRAMLISTING" >The <A HREF="smb.conf.5.html#WRITELIST" TARGET="_top" -><VAR +><TT CLASS="PARAMETER" ->write list</VAR +><I +>write list</I +></TT ></A > is used to allow administrative level user accounts to have write access in order to update files @@ -304,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 @@ -352,14 +351,14 @@ Samba follows this model as well.</P >Next create the directory tree below the [print$] share for each architecture you wish to support.</P ><P -><SAMP -CLASS="COMPUTEROUTPUT" +><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"</SAMP + |-W32PPC ; "Windows NT PowerPC"</PRE ></P ><DIV CLASS="WARNING" @@ -375,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 @@ -408,10 +407,12 @@ one of two conditions must hold true:</P must be a member of the <A HREF="smb.conf.5.html#PRINTERADMIN" TARGET="_top" -><VAR +><TT CLASS="PARAMETER" +><I >printer - admin</VAR + admin</I +></TT ></A > list.</P ></LI @@ -427,9 +428,11 @@ that all file shares are set to 'read only' by default.</P ><P >Once you have created the required [print$] service and associated subdirectories, simply log onto the Samba server using -a root (or <VAR +a root (or <TT CLASS="PARAMETER" ->printer admin</VAR +><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 @@ -442,9 +445,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1801" ->12.2.2. Setting Drivers for Existing Printers</A -></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 @@ -514,9 +515,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1817" ->12.2.3. Support a large number of printers</A -></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 @@ -534,16 +533,13 @@ setdriver command</B associated with an installed driver. The following is example of how this could be accomplished:</P ><P -><SAMP -CLASS="PROMPT" ->$ </SAMP -><KBD -CLASS="USERINPUT" ->rpcclient pogo -U root%secret -c "enumdrivers"</KBD -> -<PRE +><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] @@ -554,34 +550,27 @@ Printer Driver Info 1: Driver Name: [HP LaserJet 2100 Series PS] Printer Driver Info 1: - Driver Name: [HP LaserJet 4Si/4SiMX PS]</PRE -> -<SAMP + Driver Name: [HP LaserJet 4Si/4SiMX PS] + +<TT CLASS="PROMPT" ->$ </SAMP -><KBD -CLASS="USERINPUT" ->rpcclient pogo -U root%secret -c "enumprinters"</KBD -> -<PRE -CLASS="PROGRAMLISTING" ->Domain=[NARNIA] OS=[Unix] Server=[Samba 2.2.0-alpha3] +>$ </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:[] - </PRE -> -<SAMP + +<TT CLASS="PROMPT" ->$ </SAMP -><KBD -CLASS="USERINPUT" ->rpcclient pogo -U root%secret -c "setdriver hp-print \"HP LaserJet 4000 Series PS\""</KBD -> -<PRE -CLASS="PROGRAMLISTING" ->Domain=[NARNIA] OS=[Unix] Server=[Samba 2.2.0-alpha3] +>$ </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 @@ -590,9 +579,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1832" ->12.2.4. Adding New Printers via the Windows NT APW</A -></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" @@ -607,9 +594,11 @@ Add Printer Wizard icon. The APW will be show only if</P ><P >The connected user is able to successfully execute an OpenPrinterEx(\\server) with administrative - privileges (i.e. root or <VAR + privileges (i.e. root or <TT CLASS="PARAMETER" ->printer admin</VAR +><I +>printer admin</I +></TT >). </P ></LI @@ -618,10 +607,12 @@ CLASS="PARAMETER" ><A HREF="smb.conf.5.html#SHOWADDPRINTERWIZARD" TARGET="_top" -><VAR +><TT CLASS="PARAMETER" +><I >show - add printer wizard = yes</VAR + add printer wizard = yes</I +></TT ></A > (the default). </P @@ -632,10 +623,12 @@ CLASS="PARAMETER" server, the <A HREF="smb.conf.5.html#ADDPRINTERCOMMAND" TARGET="_top" -><VAR +><TT CLASS="PARAMETER" +><I >add -printer command</VAR +printer command</I +></TT ></A > must have a defined value. The program hook must successfully add the printer to the system (i.e. @@ -652,29 +645,35 @@ CLASS="FILENAME" not exist, <B CLASS="COMMAND" >smbd</B -> will execute the <VAR +> will execute the <TT CLASS="PARAMETER" +><I >add printer -command</VAR +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 -<VAR +<TT CLASS="PARAMETER" ->add printer program</VAR +><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" -><VAR +><TT CLASS="PARAMETER" +><I >delete -printer command</VAR +printer command</I +></TT ></A > for removing entries from the "Printers..." folder.</P @@ -682,9 +681,11 @@ folder.</P >The following is an example <A HREF="smb.conf.5.html#ADDPRINTERCOMMAN" TARGET="_top" -><VAR +><TT CLASS="PARAMETER" ->add printer command</VAR +><I +>add printer command</I +></TT ></A > script. It adds the appropriate entries to <TT CLASS="FILENAME" @@ -745,9 +746,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1862" ->12.2.5. Samba and Printer Ports</A -></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 @@ -766,10 +765,12 @@ CLASS="FILENAME" > possesses a <A HREF="smb.conf.5.html#ENUMPORTSCOMMAND" TARGET="_top" -><VAR +><TT CLASS="PARAMETER" +><I >enumports -command</VAR +command</I +></TT ></A > which can be used to define an external program that generates a listing of ports on a system.</P @@ -780,9 +781,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1870" ->12.3. The Imprints Toolset</A -></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 @@ -798,9 +797,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1874" ->12.3.1. What is Imprints?</A -></H2 +NAME="AEN2054">14.3.1. What is Imprints?</H2 ><P >Imprints is a collection of tools for supporting the goals of</P @@ -830,9 +827,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1884" ->12.3.2. Creating Printer Driver Packages</A -></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 @@ -846,9 +841,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1887" ->12.3.3. The Imprints server</A -></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 @@ -870,9 +863,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1891" ->12.3.4. The Installation Client</A -></H2 +NAME="AEN2071">14.3.4. The Installation Client</H2 ><P >More information regarding the Imprints installation client is available in the <TT @@ -964,17 +955,13 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1913" ->12.4. Diagnosis</A -></H1 +NAME="AEN2093">14.4. Diagnosis</H1 ><DIV CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1915" ->12.4.1. Introduction</A -></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 @@ -1036,7 +1023,7 @@ 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 +>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 @@ -1047,9 +1034,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1931" ->12.4.2. Debugging printer problems</A -></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 @@ -1104,9 +1089,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1940" ->12.4.3. What printers do I have?</A -></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 @@ -1133,9 +1116,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1948" ->12.4.4. Setting up printcap and print servers</A -></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 @@ -1217,9 +1198,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1976" ->12.4.5. Job sent, no output</A -></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 @@ -1262,9 +1241,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1987" ->12.4.6. Job sent, strange output</A -></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 @@ -1308,9 +1285,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1999" ->12.4.7. Raw PostScript printed</A -></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 @@ -1323,9 +1298,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2002" ->12.4.8. Advanced Printing</A -></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. @@ -1339,9 +1312,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2005" ->12.4.9. Real debugging</A -></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 @@ -1364,7 +1335,7 @@ WIDTH="33%" ALIGN="left" VALIGN="top" ><A -HREF="groupmapping.html" +HREF="msdfs.html" ACCESSKEY="P" >Prev</A ></TD @@ -1382,7 +1353,7 @@ WIDTH="33%" ALIGN="right" VALIGN="top" ><A -HREF="cups-printing.html" +HREF="winbind.html" ACCESSKEY="N" >Next</A ></TD @@ -1392,7 +1363,7 @@ ACCESSKEY="N" WIDTH="33%" ALIGN="left" VALIGN="top" ->Configuring Group Mapping</TD +>Hosting a Microsoft Distributed File System tree on Samba</TD ><TD WIDTH="34%" ALIGN="center" @@ -1406,7 +1377,7 @@ ACCESSKEY="U" WIDTH="33%" ALIGN="right" VALIGN="top" ->CUPS Printing Support</TD +>Unified Logons between Windows NT and UNIX using Winbind</TD ></TR ></TABLE ></DIV diff --git a/docs/htmldocs/pwencrypt.html b/docs/htmldocs/pwencrypt.html new file mode 100644 index 0000000000..9414399bf4 --- /dev/null +++ b/docs/htmldocs/pwencrypt.html @@ -0,0 +1,434 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML +><HEAD +><TITLE +>LanMan and NT Password Encryption in Samba</TITLE +><META +NAME="GENERATOR" +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><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="PWENCRYPT">Chapter 4. LanMan and NT Password Encryption in Samba</H1 +><DIV +CLASS="SECT1" +><H1 +CLASS="SECT1" +><A +NAME="AEN457">4.1. Introduction</H1 +><P +>Newer windows clients send encrypted passwords 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. 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="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 + 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 smbpasswd file 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="../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 +><UL +><LI +><P +>MS DOS Network client 3.0 with + the basic network redirector installed</P +></LI +><LI +><P +>Windows 95 with the network redirector + update installed</P +></LI +><LI +><P +>Windows 98 [se]</P +></LI +><LI +><P +>Windows 2000</P +></LI +></UL +><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="AEN481">4.2.1. Advantages of SMB Encryption</H2 +><P +></P +><UL +><LI +><P +>plain text passwords are not passed across + the network. Someone using a network sniffer cannot just + record passwords going to the SMB server.</P +></LI +><LI +><P +>WinNT doesn't like talking to a server + that isn't using SMB encrypted passwords. It will refuse + to browse the server if the server is also in user level + security mode. It will insist on prompting the user for the + password on each connection, which is very annoying. The + only things you can do to stop this is to use SMB encryption. + </P +></LI +></UL +></DIV +><DIV +CLASS="SECT2" +><H2 +CLASS="SECT2" +><A +NAME="AEN488">4.2.2. Advantages of non-encrypted passwords</H2 +><P +></P +><UL +><LI +><P +>plain text passwords are not kept + on disk. </P +></LI +><LI +><P +>uses same password file as other unix + services such as login and ftp</P +></LI +><LI +><P +>you are probably already using other + services (such as telnet and ftp) which send plain text + passwords over the net, so sending them for SMB isn't + such a big deal.</P +></LI +></UL +></DIV +></DIV +><DIV +CLASS="SECT1" +><H1 +CLASS="SECT1" +><A +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 + <B +CLASS="COMMAND" +>passwd</B +> or <B +CLASS="COMMAND" +>yppasswd</B +> programs, + install it in <TT +CLASS="FILENAME" +>/usr/local/samba/bin/</TT +> (or your + main Samba binary directory).</P +><P +><B +CLASS="COMMAND" +>smbpasswd</B +> now works in a client-server mode + where it contacts the local smbd to change the user's password on its + behalf. This has enormous benefits - as follows.</P +><P +><B +CLASS="COMMAND" +>smbpasswd</B +> now has the capability + 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 +><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/rpcclient.1.html b/docs/htmldocs/rpcclient.1.html index 4dfe449366..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.7"></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 @@ -38,7 +38,7 @@ NAME="AEN8" ><B CLASS="COMMAND" >rpcclient</B -> [-A authfile] [-c <command string>] [-d debuglevel] [-h] [-l logfile] [-N] [-s <smb config file>] [-U username[%password]] [-W workgroup] [-N] [-I destinationIP] {server}</P +> [-A authfile] [-c <command string>] [-d debuglevel] [-h] [-l logfile] [-N] [-s <smb config file>] [-U username[%password]] [-W workgroup] [-N] [-I destinationIP] {server}</P ></DIV ><DIV CLASS="REFSECT1" @@ -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 @@ -86,87 +84,54 @@ CLASS="VARIABLELIST" resolved using the <A HREF="smb.conf.5.html#NAMERESOLVEORDER" TARGET="_top" -> <VAR +> <TT CLASS="PARAMETER" ->name resolve order</VAR +><I +>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 ->-c|--command='command string'</DT -><DD -><P ->execute semicolon separated commands (listed - below)) </P -></DD -><DT ->-I IP-address</DT +>-A|--authfile=filename</DT ><DD ><P -><VAR -CLASS="REPLACEABLE" ->IP address</VAR -> is the address of the server to connect to. - It should be specified in standard "a.b.c.d" notation. </P -><P ->Normally the client would attempt to locate a named - SMB/CIFS server by looking it up via the NetBIOS name resolution - mechanism described above in the <VAR -CLASS="PARAMETER" ->name resolve order</VAR -> - parameter above. Using this parameter will force the client - to assume that the server is on the machine with the specified IP - address and the NetBIOS name component of the resource being - connected to will be ignored. </P +>This option allows + you to specify a file from which to read the username and + password used in the connection. The format of the file is + </P ><P ->There is no default for this parameter. If not supplied, - it will be determined automatically by the client as described - above. </P -></DD -><DT ->-V</DT -><DD +><PRE +CLASS="PROGRAMLISTING" +> username = <value> + password = <value> + domain = <value> + </PRE +></P ><P ->Prints the version number for -<B -CLASS="COMMAND" ->smbd</B ->.</P +>Make certain that the permissions on the file restrict + access from unwanted users. </P ></DD ><DT ->-s <configuration file></DT +>-c|--command='command string'</DT ><DD ><P ->The file specified contains the -configuration details required by the server. The -information in this file includes server-specific -information such as what printcap file to use, as well -as descriptions of all the services that the server is -to provide. See <A -HREF="smb.conf.5.html" -TARGET="_top" -><TT -CLASS="FILENAME" ->smb.conf(5)</TT -></A -> for more information. -The default configuration file name is determined at -compile time.</P +>execute semicolon separated commands (listed + below)) </P ></DD ><DT >-d|--debug=debuglevel</DT ><DD ><P -><VAR +><TT CLASS="REPLACEABLE" ->debuglevel</VAR +><I +>debuglevel</I +></TT > is an integer from 0 to 10. The default value if this parameter is not specified is zero.</P @@ -200,52 +165,81 @@ CLASS="FILENAME" > file.</P ></DD ><DT ->-l|--logfile=logbasename</DT +>-h|--help</DT ><DD ><P ->File name for log/debug files. The extension -<CODE -CLASS="CONSTANT" ->".client"</CODE -> will be appended. The log file is -never removed by the client.</P +>Print a summary of command line options.</P ></DD ><DT ->-N</DT +>-I IP-address</DT ><DD ><P ->If specified, this parameter suppresses the normal -password prompt from the client to the user. This is useful when -accessing a service that does not require a password. </P +><TT +CLASS="REPLACEABLE" +><I +>IP address</I +></TT +> is the address of the server to connect to. + It should be specified in standard "a.b.c.d" notation. </P +><P +>Normally the client would attempt to locate a named + SMB/CIFS server by looking it up via the NetBIOS name resolution + mechanism described above in the <TT +CLASS="PARAMETER" +><I +>name resolve order</I +></TT +> + parameter above. Using this parameter will force the client + to assume that the server is on the machine with the specified IP + address and the NetBIOS name component of the resource being + connected to will be ignored. </P ><P ->Unless a password is specified on the command line or -this parameter is specified, the client will request a -password.</P +>There is no default for this parameter. If not supplied, + it will be determined automatically by the client as described + above. </P ></DD ><DT ->-k</DT +>-l|--logfile=logbasename</DT ><DD ><P ->Try to authenticate with kerberos. Only useful in -an Active Directory environment.</P +>File name for log/debug files. The extension + <TT +CLASS="CONSTANT" +>'.client'</TT +> will be appended. The log file is + never removed by the client. + </P ></DD ><DT ->-A|--authfile=filename</DT +>-N|--nopass</DT ><DD ><P ->This option allows -you to specify a file from which to read the username and -password used in the connection. The format of the file is</P -><P -><PRE -CLASS="PROGRAMLISTING" ->username = <value> -password = <value> -domain = <value></PRE -></P +>instruct <B +CLASS="COMMAND" +>rpcclient</B +> not to ask + for a password. By default, <B +CLASS="COMMAND" +>rpcclient</B +> will + prompt for a password. See also the <TT +CLASS="PARAMETER" +><I +>-U</I +></TT +> + option.</P +></DD +><DT +>-s|--conf=smb.conf</DT +><DD ><P ->Make certain that the permissions on the file restrict -access from unwanted users. </P +>Specifies the location of the all-important + <TT +CLASS="FILENAME" +>smb.conf</TT +> file. </P ></DD ><DT >-U|--user=username[%password]</DT @@ -253,125 +247,55 @@ access from unwanted users. </P ><P >Sets the SMB username or username and password. </P ><P ->If %password is not specified, the user will be prompted. The -client will first check the <VAR +>If %password is not specified, the user will be prompted. The + client will first check the <TT CLASS="ENVAR" ->USER</VAR -> environment variable, then the -<VAR +>USER</TT +> environment variable, then the + <TT CLASS="ENVAR" ->LOGNAME</VAR -> variable and if either exists, the -string is uppercased. If these environmental variables are not -found, the username <CODE +>LOGNAME</TT +> variable and if either exists, the + string is uppercased. If these environmental variables are not + found, the username <TT CLASS="CONSTANT" ->GUEST</CODE +>GUEST</TT > is used. </P ><P ->A third option is to use a credentials file which -contains the plaintext of the username and password. This -option is mainly provided for scripts where the admin does not -wish to pass the credentials on the command line or via environment -variables. If this method is used, make certain that the permissions -on the file restrict access from unwanted users. See the -<VAR +>A third option is to use a credentials file which + contains the plaintext of the username and password. This + option is mainly provided for scripts where the admin does not + wish to pass the credentials on the command line or via environment + variables. If this method is used, make certain that the permissions + on the file restrict access from unwanted users. See the + <TT CLASS="PARAMETER" ->-A</VAR +><I +>-A</I +></TT > for more details. </P ><P ->Be cautious about including passwords in scripts. Also, on -many systems the command line of a running process may be seen -via the <B +>Be cautious about including passwords in scripts. Also, on + many systems the command line of a running process may be seen + via the <B CLASS="COMMAND" >ps</B -> command. To be safe always allow -<B +> command. To be safe always allow + <B CLASS="COMMAND" >rpcclient</B -> to prompt for a password and type -it in directly. </P -></DD -><DT ->-n <primary NetBIOS name></DT -><DD -><P ->This option allows you to override -the NetBIOS name that Samba uses for itself. This is identical -to setting the <A -HREF="smb.conf.5.html#netbiosname" -TARGET="_top" -><VAR -CLASS="PARAMETER" ->NetBIOS -name</VAR -></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 ->.</P -></DD -><DT ->-i <scope></DT -><DD -><P ->This specifies a NetBIOS scope that -<B -CLASS="COMMAND" ->nmblookup</B -> will use to communicate with when -generating NetBIOS names. For details on the use of NetBIOS -scopes, see rfc1001.txt and rfc1002.txt. NetBIOS scopes are -<SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->very</I -></SPAN -> rarely used, only set this parameter -if you are the system administrator in charge of all the -NetBIOS systems you communicate with.</P +> to prompt for a password and type + it in directly. </P ></DD ><DT >-W|--workgroup=domain</DT ><DD ><P ->Set the SMB domain of the username. This -overrides the default domain which is the domain defined in -smb.conf. If the domain specified is the same as the servers -NetBIOS name, it causes the client to log on using the servers local -SAM (as opposed to the Domain SAM). </P -></DD -><DT ->-O socket options</DT -><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 -options. </P -></DD -><DT ->-h|--help</DT -><DD -><P ->Print a summary of command line options.</P +>Set the SMB domain of the username. This + overrides the default domain which is the domain defined in + smb.conf. If the domain specified is the same as the server's NetBIOS name, + it causes the client to log on using the server's local SAM (as + opposed to the Domain SAM). </P ></DD ></DL ></DIV @@ -379,133 +303,54 @@ options. </P ><DIV CLASS="REFSECT1" ><A -NAME="AEN144" +NAME="AEN107" ></A ><H2 >COMMANDS</H2 -><DIV -CLASS="REFSECT2" -><A -NAME="AEN146" -></A -><H3 ->LSARPC</H3 ><P +><SPAN +CLASS="emphasis" +><I +CLASS="EMPHASIS" +>LSARPC</I +></SPAN ></P -><DIV -CLASS="VARIABLELIST" -><DL -><DT ->lsaquery</DT -><DD ><P ->Query info policy</P -></DD -><DT ->lookupsids</DT -><DD +></P +><UL +><LI +><P +><B +CLASS="COMMAND" +>lsaquery</B +></P +></LI +><LI ><P ->Resolve a list +><B +CLASS="COMMAND" +>lookupsids</B +> - Resolve a list of SIDs to usernames. </P -></DD -><DT ->lookupnames</DT -><DD +></LI +><LI ><P ->Resolve a list +><B +CLASS="COMMAND" +>lookupnames</B +> - Resolve a list of usernames to SIDs. </P -></DD -><DT ->enumtrusts</DT -><DD -><P ->Enumerate trusted domains</P -></DD -><DT ->enumprivs</DT -><DD -><P ->Enumerate privileges</P -></DD -><DT ->getdispname</DT -><DD -><P ->Get the privilege name</P -></DD -><DT ->lsaenumsid</DT -><DD -><P ->Enumerate the LSA SIDS</P -></DD -><DT ->lsaenumprivsaccount</DT -><DD -><P ->Enumerate the privileges of an SID</P -></DD -><DT ->lsaenumacctrights</DT -><DD -><P ->Enumerate the rights of an SID</P -></DD -><DT ->lsaenumacctwithright</DT -><DD -><P ->Enumerate accounts with a right</P -></DD -><DT ->lsaaddacctrights</DT -><DD -><P ->Add rights to an account</P -></DD -><DT ->lsaremoveacctrights</DT -><DD -><P ->Remove rights from an account</P -></DD -><DT ->lsalookupprivvalue</DT -><DD -><P ->Get a privilege value given its name</P -></DD -><DT ->lsaquerysecobj</DT -><DD -><P ->Query LSA security object</P -></DD -></DL -></DIV -></DIV -><DIV -CLASS="REFSECT2" -><A -NAME="AEN205" -></A -><H3 ->LSARPC-DS</H3 +></LI +><LI ><P +><B +CLASS="COMMAND" +>enumtrusts</B ></P -><DIV -CLASS="VARIABLELIST" -><DL -><DT ->dsroledominfo</DT -><DD -><P ->Get Primary Domain Information</P -></DD -></DL -></DIV +></LI +></UL ><P > </P ><P @@ -513,277 +358,124 @@ CLASS="VARIABLELIST" CLASS="emphasis" ><I CLASS="EMPHASIS" ->DFS</I +>SAMR</I ></SPAN ></P ><P ></P -><DIV -CLASS="VARIABLELIST" -><DL -><DT ->dfsexist</DT -><DD -><P ->Query DFS support</P -></DD -><DT ->dfsadd</DT -><DD -><P ->Add a DFS share</P -></DD -><DT ->dfsremove</DT -><DD -><P ->Remove a DFS share</P -></DD -><DT ->dfsgetinfo</DT -><DD -><P ->Query DFS share info</P -></DD -><DT ->dfsenum</DT -><DD -><P ->Enumerate dfs shares</P -></DD -></DL -></DIV -></DIV -><DIV -CLASS="REFSECT2" -><A -NAME="AEN236" -></A -><H3 ->REG</H3 +><UL +><LI ><P +><B +CLASS="COMMAND" +>queryuser</B ></P -><DIV -CLASS="VARIABLELIST" -><DL -><DT ->shutdown</DT -><DD -><P ->Remote Shutdown</P -></DD -><DT ->abortshutdown</DT -><DD -><P ->Abort Shutdown</P -></DD -></DL -></DIV -></DIV -><DIV -CLASS="REFSECT2" -><A -NAME="AEN247" -></A -><H3 ->SRVSVC</H3 +></LI +><LI ><P +><B +CLASS="COMMAND" +>querygroup</B ></P -><DIV -CLASS="VARIABLELIST" -><DL -><DT ->srvinfo</DT -><DD -><P ->Server query info</P -></DD -><DT ->netshareenum</DT -><DD -><P ->Enumerate shares</P -></DD -><DT ->netfileenum</DT -><DD -><P ->Enumerate open files</P -></DD -><DT ->netremotetod</DT -><DD -><P ->Fetch remote time of day</P -></DD -></DL -></DIV -></DIV -><DIV -CLASS="REFSECT2" -><A -NAME="AEN266" -></A -><H3 ->SAMR</H3 +></LI +><LI ><P +><B +CLASS="COMMAND" +>queryusergroups</B ></P -><DIV -CLASS="VARIABLELIST" -><DL -><DT ->queryuser</DT -><DD -><P ->Query user info</P -></DD -><DT ->querygroup</DT -><DD -><P ->Query group info</P -></DD -><DT ->queryusergroups</DT -><DD -><P ->Query user groups</P -></DD -><DT ->querygroupmem</DT -><DD -><P ->Query group membership</P -></DD -><DT ->queryaliasmem</DT -><DD -><P ->Query alias membership</P -></DD -><DT ->querydispinfo</DT -><DD -><P ->Query display info</P -></DD -><DT ->querydominfo</DT -><DD -><P ->Query domain info</P -></DD -><DT ->enumdomusers</DT -><DD -><P ->Enumerate domain users</P -></DD -><DT ->enumdomgroups</DT -><DD -><P ->Enumerate domain groups</P -></DD -><DT ->enumalsgroups</DT -><DD -><P ->Enumerate alias groups</P -></DD -><DT ->createdomuser</DT -><DD +></LI +><LI ><P ->Create domain user</P -></DD -><DT ->samlookupnames</DT -><DD +><B +CLASS="COMMAND" +>querygroupmem</B +></P +></LI +><LI ><P ->Look up names</P -></DD -><DT ->samlookuprids</DT -><DD +><B +CLASS="COMMAND" +>queryaliasmem</B +></P +></LI +><LI ><P ->Look up names</P -></DD -><DT ->deletedomuser</DT -><DD +><B +CLASS="COMMAND" +>querydispinfo</B +></P +></LI +><LI ><P ->Delete domain user</P -></DD -><DT ->samquerysecobj</DT -><DD +><B +CLASS="COMMAND" +>querydominfo</B +></P +></LI +><LI ><P ->Query SAMR security object</P -></DD -><DT ->getdompwinfo</DT -><DD +><B +CLASS="COMMAND" +>enumdomgroups</B +></P +></LI +></UL ><P ->Retrieve domain password info</P -></DD -><DT ->lookupdomain</DT -><DD +> </P ><P ->Look up domain</P -></DD -></DL -></DIV -></DIV -><DIV -CLASS="REFSECT2" -><A -NAME="AEN337" -></A -><H3 ->SPOOLSS</H3 +><SPAN +CLASS="emphasis" +><I +CLASS="EMPHASIS" +>SPOOLSS</I +></SPAN +></P ><P ></P -><DIV -CLASS="VARIABLELIST" -><DL -><DT ->adddriver <arch> <config></DT -><DD +><UL +><LI ><P -> Execute an AddPrinterDriver() RPC to install the printer driver +><B +CLASS="COMMAND" +>adddriver <arch> <config></B +> + - Execute an AddPrinterDriver() RPC to install the printer driver information on the server. Note that the driver files should already exist in the directory returned by <B CLASS="COMMAND" >getdriverdir</B >. Possible values for - <VAR + <TT CLASS="PARAMETER" ->arch</VAR +><I +>arch</I +></TT > are the same as those for the <B CLASS="COMMAND" >getdriverdir</B > command. - The <VAR + The <TT CLASS="PARAMETER" ->config</VAR +><I +>config</I +></TT > parameter is defined as follows: </P ><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 @@ -794,163 +486,167 @@ Comma Separated list of Files</PRE be "NULL". On a remote NT print server, the Print Monitor for a driver must already be installed prior to adding the driver or else the RPC will fail. </P -></DD -><DT ->addprinter <printername> - <sharename> <drivername> <port></DT -><DD +></LI +><LI ><P -> Add a printer on the remote server. This printer +><B +CLASS="COMMAND" +>addprinter <printername> + <sharename> <drivername> <port></B +> + - Add a printer on the remote server. This printer will be automatically shared. Be aware that the printer driver must already be installed on the server (see <B CLASS="COMMAND" >adddriver</B >) - and the <VAR + and the <TT CLASS="PARAMETER" ->port</VAR +><I +>port</I +></TT >must be a valid port name (see <B CLASS="COMMAND" >enumports</B >.</P -></DD -><DT ->deldriver</DT -><DD +></LI +><LI ><P ->Delete the +><B +CLASS="COMMAND" +>deldriver</B +> - Delete the specified printer driver for all architectures. This does not delete the actual driver files from the server, only the entry from the server's list of drivers. </P -></DD -><DT ->enumdata</DT -><DD +></LI +><LI ><P ->Enumerate all +><B +CLASS="COMMAND" +>enumdata</B +> - Enumerate all printer setting data stored on the server. On Windows NT clients, these values are stored in the registry, while Samba servers store them in the printers TDB. This command corresponds to the MS Platform SDK GetPrinterData() function (* This command is currently unimplemented).</P -></DD -><DT ->enumdataex</DT -><DD +></LI +><LI ><P ->Enumerate printer data for a key</P -></DD -><DT ->enumjobs <printer></DT -><DD -><P ->List the jobs and status of a given printer. +><B +CLASS="COMMAND" +>enumjobs <printer></B +> + - List the jobs and status of a given printer. This command corresponds to the MS Platform SDK EnumJobs() - function </P -></DD -><DT ->enumkey</DT -><DD + function (* This command is currently unimplemented).</P +></LI +><LI ><P ->Enumerate printer keys</P -></DD -><DT ->enumports [level]</DT -><DD -><P -> Executes an EnumPorts() call using the specified +><B +CLASS="COMMAND" +>enumports [level]</B +> + - Executes an EnumPorts() call using the specified info level. Currently only info levels 1 and 2 are supported. </P -></DD -><DT ->enumdrivers [level]</DT -><DD +></LI +><LI ><P -> Execute an EnumPrinterDrivers() call. This lists the various installed +><B +CLASS="COMMAND" +>enumdrivers [level]</B +> + - Execute an EnumPrinterDrivers() call. This lists the various installed printer drivers for all architectures. Refer to the MS Platform SDK documentation for more details of the various flags and calling options. Currently supported info levels are 1, 2, and 3.</P -></DD -><DT ->enumprinters [level]</DT -><DD +></LI +><LI ><P ->Execute an EnumPrinters() call. This lists the various installed +><B +CLASS="COMMAND" +>enumprinters [level]</B +> + - Execute an EnumPrinters() call. This lists the various installed and share printers. Refer to the MS Platform SDK documentation for more details of the various flags and calling options. Currently supported info levels are 0, 1, and 2.</P -></DD -><DT ->getdata <printername> <valuename;></DT -><DD +></LI +><LI ><P ->Retrieve the data for a given printer setting. See +><B +CLASS="COMMAND" +>getdata <printername></B +> + - Retrieve the data for a given printer setting. See the <B CLASS="COMMAND" >enumdata</B > command for more information. This command corresponds to the GetPrinterData() MS Platform - SDK function. </P -></DD -><DT ->getdataex</DT -><DD + SDK function (* This command is currently unimplemented). </P +></LI +><LI ><P ->Get printer driver data with keyname</P -></DD -><DT ->getdriver <printername></DT -><DD -><P -> Retrieve the printer driver information (such as driver file, +><B +CLASS="COMMAND" +>getdriver <printername></B +> + - Retrieve the printer driver information (such as driver file, config file, dependent files, etc...) for the given printer. This command corresponds to the GetPrinterDriver() MS Platform SDK function. Currently info level 1, 2, and 3 are supported. </P -></DD -><DT ->getdriverdir <arch></DT -><DD +></LI +><LI ><P -> Execute a GetPrinterDriverDirectory() +><B +CLASS="COMMAND" +>getdriverdir <arch></B +> + - Execute a GetPrinterDriverDirectory() RPC to retrieve the SMB share name and subdirectory for storing printer driver files for a given architecture. Possible - values for <VAR + values for <TT CLASS="PARAMETER" ->arch</VAR +><I +>arch</I +></TT > are "Windows 4.0" (for Windows 95/98), "Windows NT x86", "Windows NT PowerPC", "Windows Alpha_AXP", and "Windows NT R4000". </P -></DD -><DT ->getprinter <printername></DT -><DD +></LI +><LI ><P ->Retrieve the current printer information. This command +><B +CLASS="COMMAND" +>getprinter <printername></B +> + - Retrieve the current printer information. This command corresponds to the GetPrinter() MS Platform SDK function. </P -></DD -><DT ->getprintprocdir</DT -><DD -><P ->Get print processor directory</P -></DD -><DT ->openprinter <printername></DT -><DD +></LI +><LI ><P ->Execute an OpenPrinterEx() and ClosePrinter() RPC +><B +CLASS="COMMAND" +>openprinter <printername></B +> + - Execute an OpenPrinterEx() and ClosePrinter() RPC against a given printer. </P -></DD -><DT ->setdriver <printername> - <drivername></DT -><DD +></LI +><LI ><P ->Execute a SetPrinter() command to update the printer driver +><B +CLASS="COMMAND" +>setdriver <printername> + <drivername></B +> + - Execute a SetPrinter() command to update the printer driver associated with an installed printer. The printer driver must already be correctly installed on the print server. </P ><P @@ -963,148 +659,53 @@ CLASS="COMMAND" >enumdrivers</B > commands for obtaining a list of of installed printers and drivers.</P -></DD -><DT ->addform</DT -><DD -><P ->Add form</P -></DD -><DT ->setform</DT -><DD -><P ->Set form</P -></DD -><DT ->getform</DT -><DD -><P ->Get form</P -></DD -><DT ->deleteform</DT -><DD -><P ->Delete form</P -></DD -><DT ->enumforms</DT -><DD -><P ->Enumerate form</P -></DD -><DT ->setprinter</DT -><DD -><P ->Set printer comment</P -></DD -><DT ->setprinterdata</DT -><DD -><P ->Set REG_SZ printer data</P -></DD -><DT ->rffpcnex</DT -><DD -><P ->Rffpcnex test</P -></DD -></DL -></DIV -></DIV -><DIV -CLASS="REFSECT2" -><A -NAME="AEN460" -></A -><H3 ->NETLOGON</H3 +></LI +></UL ><P +><SPAN +CLASS="emphasis" +><I +CLASS="EMPHASIS" +>GENERAL OPTIONS</I +></SPAN ></P -><DIV -CLASS="VARIABLELIST" -><DL -><DT ->logonctrl2</DT -><DD -><P ->Logon Control 2</P -></DD -><DT ->logonctrl</DT -><DD -><P ->Logon Control</P -></DD -><DT ->samsync</DT -><DD -><P ->Sam Synchronisation</P -></DD -><DT ->samdeltas</DT -><DD -><P ->Query Sam Deltas</P -></DD -><DT ->samlogon</DT -><DD -><P ->Sam Logon</P -></DD -></DL -></DIV -></DIV -><DIV -CLASS="REFSECT2" -><A -NAME="AEN483" -></A -><H3 ->GENERAL COMMANDS</H3 ><P ></P -><DIV -CLASS="VARIABLELIST" -><DL -><DT ->debuglevel</DT -><DD +><UL +><LI ><P ->Set the current +><B +CLASS="COMMAND" +>debuglevel</B +> - Set the current debug level used to log information.</P -></DD -><DT ->help (?)</DT -><DD +></LI +><LI ><P ->Print a listing of all +><B +CLASS="COMMAND" +>help (?)</B +> - Print a listing of all known commands or extended help on a particular command. </P -></DD -><DT ->quit (exit)</DT -><DD +></LI +><LI ><P ->Exit <B +><B +CLASS="COMMAND" +>quit (exit)</B +> - Exit <B CLASS="COMMAND" >rpcclient </B >.</P -></DD -></DL -></DIV -></DIV +></LI +></UL ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN499" +NAME="AEN227" ></A ><H2 >BUGS</H2 @@ -1123,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 @@ -1133,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="AEN513" +NAME="AEN237" ></A ><H2 >VERSION</H2 @@ -1165,7 +761,7 @@ NAME="AEN513" ><DIV CLASS="REFSECT1" ><A -NAME="AEN516" +NAME="AEN240" ></A ><H2 >AUTHOR</H2 @@ -1178,8 +774,7 @@ NAME="AEN516" >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 69787dbeaf..ef06a89416 100644 --- a/docs/htmldocs/samba-bdc.html +++ b/docs/htmldocs/samba-bdc.html @@ -2,10 +2,11 @@ <HTML ><HEAD ><TITLE ->Samba Backup Domain Controller to Samba Domain Control</TITLE +>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.7"><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 an 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 7. Samba Backup Domain Controller to Samba Domain Control</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="AEN1286" ->7.1. Prerequisite Reading</A -></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="AEN1290" ->7.2. Background</A -></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="AEN1298" ->7.3. What qualifies a Domain Controller on the network?</A -></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="AEN1301" ->7.3.1. How does a Workstation find its domain controller?</A -></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="AEN1304" ->7.3.2. When is the PDC needed?</A -></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="AEN1307" ->7.4. Can Samba be a Backup Domain Controller to an NT PDC?</A -></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="AEN1312" ->7.5. How do I set up a Samba BDC?</A -></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="AEN1329" ->7.5.1. How do I replicate the smbpasswd file?</A -></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="AEN1333" ->7.5.2. Can I do this all with LDAP?</A -></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 an 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 fae541f90f..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.7"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="NEXT" TITLE="General installation" HREF="introduction.html"></HEAD @@ -19,61 +20,32 @@ 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" ->SAMBA Project Documentation</A -></H1 +NAME="SAMBA-HOWTO-COLLECTION">SAMBA Project Documentation</H1 ><H3 CLASS="AUTHOR" ><A -NAME="AEN4" -></A ->SAMBA Team</H3 -><DIV -CLASS="AFFILIATION" -><DIV -CLASS="ADDRESS" -><P -CLASS="ADDRESS" -><CODE -CLASS="EMAIL" -><<A -HREF="mailto:samba@samba.org" ->samba@samba.org</A ->></CODE -></P -></DIV -></DIV -><H4 -CLASS="EDITEDBY" ->Edited by</H4 -><H3 -CLASS="EDITOR" ->John H Terpstra</H3 -><H3 -CLASS="EDITOR" ->Jelmer Vernooij</H3 -><H3 -CLASS="EDITOR" ->Gerald (Jerry) Carter</H3 -><DIV -><DIV -CLASS="ABSTRACT" -><P -></P +NAME="AEN4">SAMBA Team</H3 +><HR></DIV +><H1 ><A -NAME="AEN32" -></A +NAME="AEN8">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. -Samba is always under development, and so is it's documentation. -The most recent version of this document +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" @@ -90,17 +62,6 @@ TARGET="_top" >jelmer@samba.org</A >.</P ><P -></P -></DIV -></DIV -><DIV -CLASS="LEGALNOTICE" -><P -></P -><A -NAME="AEN37" -></A -><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 @@ -109,9 +70,7 @@ TARGET="_top" >http://www.fsf.org/licenses/gpl.txt</A ></P ><P -></P -></DIV -><HR></DIV +>Cheers, jerry</P ><DIV CLASS="TOC" ><DL @@ -135,259 +94,288 @@ HREF="install.html" ><DL ><DT >1.1. <A -HREF="install.html#AEN65" ->Obtaining and installing samba</A +HREF="install.html#AEN26" +>Read the man pages</A ></DT ><DT >1.2. <A -HREF="install.html#AEN71" ->Configuring samba</A +HREF="install.html#AEN36" +>Building the Binaries</A ></DT ><DT >1.3. <A -HREF="install.html#AEN107" +HREF="install.html#AEN64" +>The all important step</A +></DT +><DT +>1.4. <A +HREF="install.html#AEN68" +>Create the smb configuration file.</A +></DT +><DT +>1.5. <A +HREF="install.html#AEN82" +>Test your config file with + <B +CLASS="COMMAND" +>testparm</B +></A +></DT +><DT +>1.6. <A +HREF="install.html#AEN90" +>Starting the smbd and nmbd</A +></DT +><DT +>1.7. <A +HREF="install.html#AEN145" >Try listing the shares available on your server</A ></DT ><DT ->1.4. <A -HREF="install.html#AEN116" +>1.8. <A +HREF="install.html#AEN154" >Try connecting with the unix client</A ></DT ><DT ->1.5. <A -HREF="install.html#AEN137" +>1.9. <A +HREF="install.html#AEN170" >Try connecting from a DOS, WfWg, Win9x, WinNT, Win2k, OS/2, etc... client</A ></DT ><DT ->1.6. <A -HREF="install.html#AEN150" +>1.10. <A +HREF="install.html#AEN184" >What If Things Don't Work?</A ></DT ></DL ></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#AEN183" ->Discussion</A +HREF="improved-browsing.html#AEN229" +>Overview of browsing</A ></DT ><DT >2.2. <A -HREF="browsing-quick.html#AEN204" ->How browsing functions and how to deploy stable and -dependable browsing using Samba</A +HREF="improved-browsing.html#AEN233" +>Browsing support in samba</A ></DT ><DT >2.3. <A -HREF="browsing-quick.html#AEN218" ->Use of the <B -CLASS="COMMAND" ->Remote Announce</B -> parameter</A +HREF="improved-browsing.html#AEN242" +>Problem resolution</A ></DT ><DT >2.4. <A -HREF="browsing-quick.html#AEN241" ->Use of the <B -CLASS="COMMAND" ->Remote Browse Sync</B -> parameter</A +HREF="improved-browsing.html#AEN249" +>Browsing across subnets</A ></DT ><DT >2.5. <A -HREF="browsing-quick.html#AEN252" ->Use of WINS</A +HREF="improved-browsing.html#AEN289" +>Setting up a WINS server</A ></DT ><DT >2.6. <A -HREF="browsing-quick.html#AEN269" ->Do NOT use more than one (1) protocol on MS Windows machines</A +HREF="improved-browsing.html#AEN308" +>Setting up Browsing in a WORKGROUP</A ></DT ><DT >2.7. <A -HREF="browsing-quick.html#AEN277" ->Name Resolution Order</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#AEN335" ->Introduction</A +HREF="browsing-quick.html#AEN377" +>Discussion</A ></DT ><DT >3.2. <A -HREF="passdb.html#AEN342" ->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#AEN380" ->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#AEN411" ->Plain text</A +HREF="browsing-quick.html#AEN404" +>Use of WINS</A ></DT ><DT >3.5. <A -HREF="passdb.html#AEN416" ->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#AEN419" ->LDAP</A -></DT -><DT ->3.7. <A -HREF="passdb.html#AEN637" ->MySQL</A -></DT -><DT ->3.8. <A -HREF="passdb.html#AEN679" ->XML</A +HREF="browsing-quick.html#AEN421" +>Name Resolution Order</A ></DT ></DL ></DD -></DL -></DD -><DT ->II. <A -HREF="type.html" ->Type of installation</A -></DT -><DD -><DL ><DT >4. <A -HREF="servertype.html" ->Nomenclature of Server Types</A +HREF="pwencrypt.html" +>LanMan and NT Password Encryption in Samba</A ></DT ><DD ><DL ><DT >4.1. <A -HREF="servertype.html#AEN717" ->Stand Alone Server</A +HREF="pwencrypt.html#AEN457" +>Introduction</A ></DT ><DT >4.2. <A -HREF="servertype.html#AEN724" ->Domain Member Server</A +HREF="pwencrypt.html#AEN462" +>Important Notes About Security</A ></DT ><DT >4.3. <A -HREF="servertype.html#AEN730" ->Domain Controller</A +HREF="pwencrypt.html#AEN497" +>The smbpasswd Command</A ></DT ></DL ></DD +></DL +></DD ><DT ->5. <A -HREF="securitylevels.html" ->Samba as Stand-Alone Server</A +>II. <A +HREF="type.html" +>Type of installation</A ></DT ><DD ><DL ><DT ->5.1. <A -HREF="securitylevels.html#AEN766" ->User and Share security level</A +>5. <A +HREF="securitylevels.html" +>User and Share security level (for servers not in a domain)</A ></DT -></DL -></DD ><DT >6. <A HREF="samba-pdc.html" ->Samba as an NT4 or Win2k Primary Domain Controller</A +>How to Configure Samba as a NT4 Primary Domain Controller</A ></DT ><DD ><DL ><DT >6.1. <A -HREF="samba-pdc.html#AEN878" +HREF="samba-pdc.html#AEN575" >Prerequisite Reading</A ></DT ><DT >6.2. <A -HREF="samba-pdc.html#AEN883" +HREF="samba-pdc.html#AEN581" >Background</A ></DT ><DT >6.3. <A -HREF="samba-pdc.html#AEN923" +HREF="samba-pdc.html#AEN620" >Configuring the Samba Domain Controller</A ></DT ><DT >6.4. <A -HREF="samba-pdc.html#AEN965" ->Creating Machine Trust Accounts and Joining Clients to the Domain</A +HREF="samba-pdc.html#AEN663" +>Creating Machine Trust Accounts and Joining Clients to the +Domain</A ></DT ><DT >6.5. <A -HREF="samba-pdc.html#AEN1073" +HREF="samba-pdc.html#AEN747" >Common Problems and Errors</A ></DT ><DT >6.6. <A -HREF="samba-pdc.html#AEN1119" ->What other help can I get?</A +HREF="samba-pdc.html#AEN795" +>System Policies and Profiles</A ></DT ><DT >6.7. <A -HREF="samba-pdc.html#AEN1233" +HREF="samba-pdc.html#AEN839" +>What other help can I get?</A +></DT +><DT +>6.8. <A +HREF="samba-pdc.html#AEN953" >Domain Control for Windows 9x/ME</A ></DT +><DT +>6.9. <A +HREF="samba-pdc.html#AEN1091" +>DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba</A +></DT ></DL ></DD ><DT >7. <A HREF="samba-bdc.html" ->Samba Backup Domain Controller to Samba Domain Control</A +>How to Act as a Backup Domain Controller in a Purely Samba Controlled Domain</A ></DT ><DD ><DL ><DT >7.1. <A -HREF="samba-bdc.html#AEN1286" +HREF="samba-bdc.html#AEN1127" >Prerequisite Reading</A ></DT ><DT >7.2. <A -HREF="samba-bdc.html#AEN1290" +HREF="samba-bdc.html#AEN1131" >Background</A ></DT ><DT >7.3. <A -HREF="samba-bdc.html#AEN1298" +HREF="samba-bdc.html#AEN1139" >What qualifies a Domain Controller on the network?</A ></DT ><DT >7.4. <A -HREF="samba-bdc.html#AEN1307" ->Can Samba be a Backup Domain Controller to an NT PDC?</A +HREF="samba-bdc.html#AEN1148" +>Can Samba be a Backup Domain Controller?</A ></DT ><DT >7.5. <A -HREF="samba-bdc.html#AEN1312" +HREF="samba-bdc.html#AEN1152" >How do I set up a Samba BDC?</A ></DT ></DL @@ -401,41 +389,42 @@ HREF="ads.html" ><DL ><DT >8.1. <A -HREF="ads.html#AEN1355" ->Setup your <TT -CLASS="FILENAME" ->smb.conf</TT -></A +HREF="ads.html#AEN1187" +>Installing the required packages for Debian</A ></DT ><DT >8.2. <A -HREF="ads.html#AEN1368" ->Setup your <TT -CLASS="FILENAME" ->/etc/krb5.conf</TT -></A +HREF="ads.html#AEN1193" +>Installing the required packages for RedHat</A ></DT ><DT >8.3. <A -HREF="ads.html#ADS-CREATE-MACHINE-ACCOUNT" ->Create the computer account</A +HREF="ads.html#AEN1202" +>Compile Samba</A ></DT ><DT >8.4. <A -HREF="ads.html#ADS-TEST-SERVER" ->Test your server setup</A +HREF="ads.html#AEN1217" +>Setup your /etc/krb5.conf</A ></DT ><DT >8.5. <A -HREF="ads.html#ADS-TEST-SMBCLIENT" ->Testing with <SPAN -CLASS="APPLICATION" ->smbclient</SPAN -></A +HREF="ads.html#AEN1227" +>Create the computer account</A ></DT ><DT >8.6. <A -HREF="ads.html#AEN1416" +HREF="ads.html#AEN1243" +>Test your server setup</A +></DT +><DT +>8.7. <A +HREF="ads.html#AEN1248" +>Testing with smbclient</A +></DT +><DT +>8.8. <A +HREF="ads.html#AEN1251" >Notes</A ></DT ></DL @@ -443,18 +432,23 @@ HREF="ads.html#AEN1416" ><DT >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 >9.1. <A -HREF="domain-security.html#AEN1439" ->Joining an NT Domain with Samba 3.0</A +HREF="domain-security.html#AEN1273" +>Joining an NT Domain with Samba 2.2</A ></DT ><DT >9.2. <A -HREF="domain-security.html#AEN1493" +HREF="domain-security.html#AEN1337" +>Samba and Windows 2000 Domains</A +></DT +><DT +>9.3. <A +HREF="domain-security.html#AEN1342" >Why is this better than security = server?</A ></DT ></DL @@ -464,779 +458,560 @@ HREF="domain-security.html#AEN1493" ><DT >III. <A HREF="optional.html" ->Advanced Configuration</A +>Optional configuration</A ></DT ><DD ><DL ><DT >10. <A +HREF="integrate-ms-networks.html" +>Integrating MS Windows networks with Samba</A +></DT +><DD +><DL +><DT +>10.1. <A +HREF="integrate-ms-networks.html#AEN1374" +>Agenda</A +></DT +><DT +>10.2. <A +HREF="integrate-ms-networks.html#AEN1396" +>Name Resolution in a pure Unix/Linux world</A +></DT +><DT +>10.3. <A +HREF="integrate-ms-networks.html#AEN1459" +>Name resolution as used within MS Windows networking</A +></DT +><DT +>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 +>10.5. <A +HREF="integrate-ms-networks.html#AEN1514" +>MS Windows security options and how to configure +Samba for seemless integration</A +></DT +><DT +>10.6. <A +HREF="integrate-ms-networks.html#AEN1584" +>Conclusions</A +></DT +></DL +></DD +><DT +>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#AEN1525" +>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#AEN1531" +>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#AEN1542" +>11.3. <A +HREF="unix-permissions.html#AEN1625" >Viewing file ownership</A ></DT ><DT ->10.4. <A -HREF="unix-permissions.html#AEN1562" +>11.4. <A +HREF="unix-permissions.html#AEN1645" >Viewing file or directory permissions</A ></DT ><DT ->10.5. <A -HREF="unix-permissions.html#AEN1598" +>11.5. <A +HREF="unix-permissions.html#AEN1681" >Modifying file or directory permissions</A ></DT ><DT ->10.6. <A -HREF="unix-permissions.html#AEN1620" +>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#AEN1673" +>11.7. <A +HREF="unix-permissions.html#AEN1767" >Interaction with the standard Samba file attribute mapping</A ></DT ></DL ></DD ><DT ->11. <A -HREF="groupmapping.html" ->Configuring Group Mapping</A -></DT -><DT >12. <A -HREF="printing.html" ->Printing Support</A +HREF="pam.html" +>Configuring PAM for distributed but centrally +managed authentication</A ></DT ><DD ><DL ><DT >12.1. <A -HREF="printing.html#AEN1736" ->Introduction</A +HREF="pam.html#AEN1788" +>Samba and PAM</A ></DT ><DT >12.2. <A -HREF="printing.html#AEN1758" ->Configuration</A +HREF="pam.html#AEN1832" +>Distributed Authentication</A ></DT ><DT >12.3. <A -HREF="printing.html#AEN1870" ->The Imprints Toolset</A -></DT -><DT ->12.4. <A -HREF="printing.html#AEN1913" ->Diagnosis</A +HREF="pam.html#AEN1839" +>PAM Configuration in smb.conf</A ></DT ></DL ></DD ><DT >13. <A -HREF="cups-printing.html" ->CUPS Printing Support</A +HREF="msdfs.html" +>Hosting a Microsoft Distributed File System tree on Samba</A ></DT ><DD ><DL ><DT >13.1. <A -HREF="cups-printing.html#AEN2025" ->Introduction</A -></DT -><DT ->13.2. <A -HREF="cups-printing.html#AEN2032" ->Configuring <TT -CLASS="FILENAME" ->smb.conf</TT -> for CUPS</A -></DT -><DT ->13.3. <A -HREF="cups-printing.html#AEN2052" ->CUPS - RAW Print Through Mode</A -></DT -><DT ->13.4. <A -HREF="cups-printing.html#AEN2111" ->CUPS as a network PostScript RIP -- CUPS drivers working on server, Adobe -PostScript driver with CUPS-PPDs downloaded to clients</A -></DT -><DT ->13.5. <A -HREF="cups-printing.html#AEN2132" ->Windows Terminal Servers (WTS) as CUPS clients</A -></DT -><DT ->13.6. <A -HREF="cups-printing.html#AEN2136" ->Setting up CUPS for driver download</A -></DT -><DT ->13.7. <A -HREF="cups-printing.html#AEN2149" ->Sources of CUPS drivers / PPDs</A +HREF="msdfs.html#AEN1859" +>Instructions</A ></DT +></DL +></DD ><DT ->13.8. <A -HREF="cups-printing.html#AEN2205" ->The CUPS Filter Chains</A +>14. <A +HREF="printing.html" +>Printing Support</A ></DT +><DD +><DL ><DT ->13.9. <A -HREF="cups-printing.html#AEN2244" ->CUPS Print Drivers and Devices</A +>14.1. <A +HREF="printing.html#AEN1920" +>Introduction</A ></DT ><DT ->13.10. <A -HREF="cups-printing.html#AEN2321" ->Limiting the number of pages users can print</A +>14.2. <A +HREF="printing.html#AEN1942" +>Configuration</A ></DT ><DT ->13.11. <A -HREF="cups-printing.html#AEN2417" ->Advanced Postscript Printing from MS Windows</A +>14.3. <A +HREF="printing.html#AEN2050" +>The Imprints Toolset</A ></DT ><DT ->13.12. <A -HREF="cups-printing.html#AEN2432" ->Auto-Deletion of CUPS spool files</A +>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#AEN2506" +>15.1. <A +HREF="winbind.html#AEN2225" >Abstract</A ></DT ><DT ->14.2. <A -HREF="winbind.html#AEN2510" +>15.2. <A +HREF="winbind.html#AEN2229" >Introduction</A ></DT ><DT ->14.3. <A -HREF="winbind.html#AEN2523" +>15.3. <A +HREF="winbind.html#AEN2242" >What Winbind Provides</A ></DT ><DT ->14.4. <A -HREF="winbind.html#AEN2534" +>15.4. <A +HREF="winbind.html#AEN2253" >How Winbind Works</A ></DT ><DT ->14.5. <A -HREF="winbind.html#AEN2577" +>15.5. <A +HREF="winbind.html#AEN2293" >Installation and Configuration</A ></DT ><DT ->14.6. <A -HREF="winbind.html#AEN2834" +>15.6. <A +HREF="winbind.html#AEN2542" >Limitations</A ></DT ><DT ->14.7. <A -HREF="winbind.html#AEN2844" +>15.7. <A +HREF="winbind.html#AEN2552" >Conclusion</A ></DT ></DL ></DD ><DT ->15. <A -HREF="advancednetworkmanagement.html" ->Advanced Network Manangement</A +>16. <A +HREF="pdb-mysql.html" +>Passdb MySQL plugin</A ></DT ><DD ><DL ><DT ->15.1. <A -HREF="advancednetworkmanagement.html#AEN2859" ->Configuring Samba Share Access Controls</A -></DT -><DT ->15.2. <A -HREF="advancednetworkmanagement.html#AEN2897" ->Remote Server Administration</A -></DT -><DT ->15.3. <A -HREF="advancednetworkmanagement.html#AEN2914" ->Network Logon Script Magic</A +>16.1. <A +HREF="pdb-mysql.html#AEN2566" +>Building</A ></DT -></DL -></DD ><DT ->16. <A -HREF="policymgmt.html" ->System and Account Policies</A +>16.2. <A +HREF="pdb-mysql.html#AEN2572" +>Configuring</A ></DT -><DD -><DL ><DT ->16.1. <A -HREF="policymgmt.html#AEN2929" ->Creating and Managing System Policies</A +>16.3. <A +HREF="pdb-mysql.html#AEN2589" +>Using plaintext passwords or encrypted password</A ></DT ><DT ->16.2. <A -HREF="policymgmt.html#AEN3002" ->Managing Account/User Policies</A +>16.4. <A +HREF="pdb-mysql.html#AEN2594" +>Getting non-column data from the table</A ></DT ></DL ></DD ><DT >17. <A -HREF="profilemgmt.html" ->Desktop Profile Management</A +HREF="pdb-xml.html" +>Passdb XML plugin</A ></DT ><DD ><DL ><DT >17.1. <A -HREF="profilemgmt.html#AEN3035" ->Roaming Profiles</A +HREF="pdb-xml.html#AEN2613" +>Building</A ></DT ><DT >17.2. <A -HREF="profilemgmt.html#AEN3242" ->Mandatory profiles</A -></DT -><DT ->17.3. <A -HREF="profilemgmt.html#AEN3249" ->Creating/Managing Group Profiles</A -></DT -><DT ->17.4. <A -HREF="profilemgmt.html#AEN3255" ->Default Profile for Windows Users</A +HREF="pdb-xml.html#AEN2619" +>Usage</A ></DT ></DL ></DD ><DT >18. <A -HREF="interdomaintrusts.html" ->Interdomain Trust Relationships</A +HREF="vfs.html" +>Stackable VFS modules</A ></DT ><DD ><DL ><DT >18.1. <A -HREF="interdomaintrusts.html#AEN3386" ->Trust Relationship Background</A +HREF="vfs.html#AEN2640" +>Introduction and configuration</A ></DT ><DT >18.2. <A -HREF="interdomaintrusts.html#AEN3395" ->MS Windows NT4 Trust Configuration</A +HREF="vfs.html#AEN2649" +>Included modules</A ></DT ><DT >18.3. <A -HREF="interdomaintrusts.html#AEN3405" ->Configuring Samba Domain Trusts</A +HREF="vfs.html#AEN2703" +>VFS modules available elsewhere</A ></DT ></DL ></DD ><DT >19. <A -HREF="pam.html" ->PAM Configuration for Centrally Managed Authentication</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="pam.html#AEN3440" ->Samba and PAM</A +HREF="samba-ldap-howto.html#AEN2737" +>Purpose</A ></DT ><DT >19.2. <A -HREF="pam.html#AEN3491" ->Distributed Authentication</A +HREF="samba-ldap-howto.html#AEN2757" +>Introduction</A ></DT ><DT >19.3. <A -HREF="pam.html#AEN3496" ->PAM Configuration in smb.conf</A +HREF="samba-ldap-howto.html#AEN2786" +>Supported LDAP Servers</A ></DT -></DL -></DD ><DT ->20. <A -HREF="vfs.html" ->Stackable VFS modules</A +>19.4. <A +HREF="samba-ldap-howto.html#AEN2791" +>Schema and Relationship to the RFC 2307 posixAccount</A ></DT -><DD -><DL ><DT ->20.1. <A -HREF="vfs.html#AEN3531" ->Introduction and configuration</A +>19.5. <A +HREF="samba-ldap-howto.html#AEN2803" +>Configuring Samba with LDAP</A ></DT ><DT ->20.2. <A -HREF="vfs.html#AEN3540" ->Included modules</A +>19.6. <A +HREF="samba-ldap-howto.html#AEN2850" +>Accounts and Groups management</A ></DT ><DT ->20.3. <A -HREF="vfs.html#AEN3598" ->VFS modules available elsewhere</A +>19.7. <A +HREF="samba-ldap-howto.html#AEN2855" +>Security and sambaAccount</A ></DT -></DL -></DD ><DT ->21. <A -HREF="msdfs.html" ->Hosting a Microsoft Distributed File System tree on Samba</A +>19.8. <A +HREF="samba-ldap-howto.html#AEN2875" +>LDAP specials attributes for sambaAccounts</A ></DT -><DD -><DL ><DT ->21.1. <A -HREF="msdfs.html#AEN3626" ->Instructions</A +>19.9. <A +HREF="samba-ldap-howto.html#AEN2945" +>Example LDIF Entries for a sambaAccount</A ></DT -></DL -></DD ><DT ->22. <A -HREF="integrate-ms-networks.html" ->Integrating MS Windows networks with Samba</A -></DT -><DD -><DL -><DT ->22.1. <A -HREF="integrate-ms-networks.html#AEN3688" ->Name Resolution in a pure Unix/Linux world</A -></DT -><DT ->22.2. <A -HREF="integrate-ms-networks.html#AEN3751" ->Name resolution as used within MS Windows networking</A +>19.10. <A +HREF="samba-ldap-howto.html#AEN2953" +>Comments</A ></DT ></DL ></DD ><DT ->23. <A -HREF="improved-browsing.html" ->Improved browsing in samba</A -></DT -><DD -><DL -><DT ->23.1. <A -HREF="improved-browsing.html#AEN3804" ->Overview of browsing</A -></DT -><DT ->23.2. <A -HREF="improved-browsing.html#AEN3810" ->Browsing support in samba</A -></DT -><DT ->23.3. <A -HREF="improved-browsing.html#AEN3825" ->Problem resolution</A -></DT -><DT ->23.4. <A -HREF="improved-browsing.html#AEN3837" ->Browsing across subnets</A -></DT -><DT ->23.5. <A -HREF="improved-browsing.html#AEN3878" ->Setting up a WINS server</A -></DT -><DT ->23.6. <A -HREF="improved-browsing.html#AEN3901" ->Setting up Browsing in a WORKGROUP</A -></DT -><DT ->23.7. <A -HREF="improved-browsing.html#AEN3927" ->Setting up Browsing in a DOMAIN</A -></DT -><DT ->23.8. <A -HREF="improved-browsing.html#BROWSE-FORCE-MASTER" ->Forcing samba to be the master</A -></DT -><DT ->23.9. <A -HREF="improved-browsing.html#AEN3962" ->Making samba the domain master</A -></DT -><DT ->23.10. <A -HREF="improved-browsing.html#AEN3984" ->Note about broadcast addresses</A -></DT -><DT ->23.11. <A -HREF="improved-browsing.html#AEN3987" ->Multiple interfaces</A -></DT -></DL -></DD -><DT ->24. <A -HREF="securing-samba.html" ->Securing Samba</A +>20. <A +HREF="cvs-access.html" +>HOWTO Access Samba source code via CVS</A ></DT ><DD ><DL ><DT ->24.1. <A -HREF="securing-samba.html#AEN4003" +>20.1. <A +HREF="cvs-access.html#AEN2964" >Introduction</A ></DT ><DT ->24.2. <A -HREF="securing-samba.html#AEN4006" ->Using host based protection</A -></DT -><DT ->24.3. <A -HREF="securing-samba.html#AEN4016" ->Using interface protection</A -></DT -><DT ->24.4. <A -HREF="securing-samba.html#AEN4025" ->Using a firewall</A -></DT -><DT ->24.5. <A -HREF="securing-samba.html#AEN4032" ->Using a IPC$ share deny</A -></DT -><DT ->24.6. <A -HREF="securing-samba.html#AEN4041" ->Upgrading Samba</A -></DT -></DL -></DD -><DT ->25. <A -HREF="unicode.html" ->Unicode/Charsets</A -></DT -><DD -><DL -><DT ->25.1. <A -HREF="unicode.html#AEN4056" ->What are charsets and unicode?</A -></DT -><DT ->25.2. <A -HREF="unicode.html#AEN4065" ->Samba and charsets</A -></DT -></DL -></DD -></DL -></DD -><DT ->IV. <A -HREF="appendixes.html" ->Appendixes</A -></DT -><DD -><DL -><DT ->26. <A -HREF="swat.html" ->SWAT - The Samba Web Admininistration Tool</A -></DT -><DD -><DL -><DT ->26.1. <A -HREF="swat.html#AEN4098" ->SWAT Features and Benefits</A +>20.2. <A +HREF="cvs-access.html#AEN2969" +>CVS Access to samba.org</A ></DT ></DL ></DD ><DT ->27. <A -HREF="nt4migration.html" ->Migration from NT4 PDC to Samba-3 PDC</A -></DT -><DD -><DL -><DT ->27.1. <A -HREF="nt4migration.html#AEN4134" ->Planning and Getting Started</A +>21. <A +HREF="groupmapping.html" +>Group mapping HOWTO</A ></DT ><DT ->27.2. <A -HREF="nt4migration.html#AEN4143" ->Managing Samba-3 Domain Control</A -></DT -></DL -></DD -><DT ->28. <A +>22. <A HREF="speed.html" >Samba performance issues</A ></DT ><DD ><DL ><DT ->28.1. <A -HREF="speed.html#AEN4163" +>22.1. <A +HREF="speed.html#AEN3055" >Comparisons</A ></DT ><DT ->28.2. <A -HREF="speed.html#AEN4169" +>22.2. <A +HREF="speed.html#AEN3061" >Socket options</A ></DT ><DT ->28.3. <A -HREF="speed.html#AEN4176" +>22.3. <A +HREF="speed.html#AEN3068" >Read size</A ></DT ><DT ->28.4. <A -HREF="speed.html#AEN4181" +>22.4. <A +HREF="speed.html#AEN3073" >Max xmit</A ></DT ><DT ->28.5. <A -HREF="speed.html#AEN4186" +>22.5. <A +HREF="speed.html#AEN3078" >Log level</A ></DT ><DT ->28.6. <A -HREF="speed.html#AEN4189" +>22.6. <A +HREF="speed.html#AEN3081" >Read raw</A ></DT ><DT ->28.7. <A -HREF="speed.html#AEN4194" +>22.7. <A +HREF="speed.html#AEN3086" >Write raw</A ></DT ><DT ->28.8. <A -HREF="speed.html#AEN4198" +>22.8. <A +HREF="speed.html#AEN3090" >Slow Clients</A ></DT ><DT ->28.9. <A -HREF="speed.html#AEN4202" +>22.9. <A +HREF="speed.html#AEN3094" >Slow Logins</A ></DT ><DT ->28.10. <A -HREF="speed.html#AEN4205" +>22.10. <A +HREF="speed.html#AEN3097" >Client tuning</A ></DT ></DL ></DD +></DL +></DD +><DT +>IV. <A +HREF="appendixes.html" +>Appendixes</A +></DT +><DD +><DL ><DT ->29. <A +>23. <A HREF="portability.html" >Portability</A ></DT ><DD ><DL ><DT ->29.1. <A -HREF="portability.html#AEN4249" +>23.1. <A +HREF="portability.html#AEN3139" >HPUX</A ></DT ><DT ->29.2. <A -HREF="portability.html#AEN4255" +>23.2. <A +HREF="portability.html#AEN3145" >SCO Unix</A ></DT ><DT ->29.3. <A -HREF="portability.html#AEN4259" +>23.3. <A +HREF="portability.html#AEN3149" >DNIX</A ></DT ><DT ->29.4. <A -HREF="portability.html#AEN4288" +>23.4. <A +HREF="portability.html#AEN3178" >RedHat Linux Rembrandt-II</A ></DT -><DT ->29.5. <A -HREF="portability.html#AEN4294" ->AIX</A -></DT -><DT ->29.6. <A -HREF="portability.html#AEN4300" ->Solaris</A -></DT ></DL ></DD ><DT ->30. <A +>24. <A HREF="other-clients.html" >Samba and other CIFS clients</A ></DT ><DD ><DL ><DT ->30.1. <A -HREF="other-clients.html#AEN4326" +>24.1. <A +HREF="other-clients.html#AEN3199" >Macintosh clients?</A ></DT ><DT ->30.2. <A -HREF="other-clients.html#AEN4335" +>24.2. <A +HREF="other-clients.html#AEN3208" >OS2 Client</A ></DT ><DT ->30.3. <A -HREF="other-clients.html#AEN4375" +>24.3. <A +HREF="other-clients.html#AEN3248" >Windows for Workgroups</A ></DT ><DT ->30.4. <A -HREF="other-clients.html#AEN4399" +>24.4. <A +HREF="other-clients.html#AEN3269" >Windows '95/'98</A ></DT ><DT ->30.5. <A -HREF="other-clients.html#AEN4415" +>24.5. <A +HREF="other-clients.html#AEN3285" >Windows 2000 Service Pack 2</A ></DT -><DT ->30.6. <A -HREF="other-clients.html#AEN4432" ->Windows NT 3.1</A -></DT -></DL -></DD -><DT ->31. <A -HREF="compiling.html" ->How to compile SAMBA</A -></DT -><DD -><DL -><DT ->31.1. <A -HREF="compiling.html#AEN4453" ->Access Samba source code via CVS</A -></DT -><DT ->31.2. <A -HREF="compiling.html#AEN4496" ->Accessing the samba sources via rsync and ftp</A -></DT -><DT ->31.3. <A -HREF="compiling.html#AEN4502" ->Building the Binaries</A -></DT -><DT ->31.4. <A -HREF="compiling.html#AEN4559" ->Starting the smbd and nmbd</A -></DT ></DL ></DD ><DT ->32. <A +>25. <A HREF="bugreport.html" >Reporting Bugs</A ></DT ><DD ><DL ><DT ->32.1. <A -HREF="bugreport.html#AEN4634" +>25.1. <A +HREF="bugreport.html#AEN3309" >Introduction</A ></DT ><DT ->32.2. <A -HREF="bugreport.html#AEN4644" +>25.2. <A +HREF="bugreport.html#AEN3319" >General info</A ></DT ><DT ->32.3. <A -HREF="bugreport.html#AEN4650" +>25.3. <A +HREF="bugreport.html#AEN3325" >Debug levels</A ></DT ><DT ->32.4. <A -HREF="bugreport.html#AEN4671" +>25.4. <A +HREF="bugreport.html#AEN3342" >Internal errors</A ></DT ><DT ->32.5. <A -HREF="bugreport.html#AEN4685" +>25.5. <A +HREF="bugreport.html#AEN3352" >Attaching to a running process</A ></DT ><DT ->32.6. <A -HREF="bugreport.html#AEN4693" +>25.6. <A +HREF="bugreport.html#AEN3355" >Patches</A ></DT ></DL ></DD ><DT ->33. <A +>26. <A HREF="diagnosis.html" ->The samba checklist</A +>Diagnosing your samba server</A ></DT ><DD ><DL ><DT ->33.1. <A -HREF="diagnosis.html#AEN4716" +>26.1. <A +HREF="diagnosis.html#AEN3378" >Introduction</A ></DT ><DT ->33.2. <A -HREF="diagnosis.html#AEN4721" +>26.2. <A +HREF="diagnosis.html#AEN3383" >Assumptions</A ></DT ><DT ->33.3. <A -HREF="diagnosis.html#AEN4740" ->The tests</A +>26.3. <A +HREF="diagnosis.html#AEN3393" +>Tests</A ></DT ><DT ->33.4. <A -HREF="diagnosis.html#AEN4907" +>26.4. <A +HREF="diagnosis.html#AEN3503" >Still having troubles?</A ></DT ></DL diff --git a/docs/htmldocs/passdb.html b/docs/htmldocs/samba-ldap-howto.html index 35a941b63a..884bb756c1 100644 --- a/docs/htmldocs/passdb.html +++ b/docs/htmldocs/samba-ldap-howto.html @@ -2,22 +2,23 @@ <HTML ><HEAD ><TITLE ->User information database</TITLE +>Storing Samba's User/Machine Account information in an LDAP Directory</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><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="General installation" -HREF="introduction.html"><LINK +TITLE="Optional configuration" +HREF="optional.html"><LINK REL="PREVIOUS" -TITLE="Quick Cross Subnet Browsing / Cross Workgroup Browsing guide" -HREF="browsing-quick.html"><LINK +TITLE="Stackable VFS modules" +HREF="vfs.html"><LINK REL="NEXT" -TITLE="Type of installation" -HREF="type.html"></HEAD +TITLE="HOWTO Access Samba source code via CVS" +HREF="cvs-access.html"></HEAD ><BODY CLASS="CHAPTER" BGCOLOR="#FFFFFF" @@ -45,7 +46,7 @@ WIDTH="10%" ALIGN="left" VALIGN="bottom" ><A -HREF="browsing-quick.html" +HREF="vfs.html" ACCESSKEY="P" >Prev</A ></TD @@ -59,7 +60,7 @@ WIDTH="10%" ALIGN="right" VALIGN="bottom" ><A -HREF="type.html" +HREF="cvs-access.html" ACCESSKEY="N" >Next</A ></TD @@ -72,439 +73,13 @@ WIDTH="100%"></DIV CLASS="CHAPTER" ><H1 ><A -NAME="PASSDB" -></A ->Chapter 3. User information database</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="AEN335" ->3.1. Introduction</A -></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="AEN342" ->3.2. Important Notes About Security</A -></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 -> These versions of MS Windows do not support full domain - security protocols, although they may log onto a domain environment. - Of these Only MS Windows XP Home does NOT support domain logons.</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 Me</TD -></TR -><TR -><TD ->Windows XP Home</TD -></TR -></TBODY -></TABLE -><P -></P -><P -> The following versions of MS Windows fully support domain - security protocols.</P -><P -></P -><TABLE -BORDER="0" -><TBODY -><TR -><TD ->Windows NT 3.5x</TD -></TR -><TR -><TD ->Windows NT 4.0</TD -></TR -><TR -><TD ->Windows 2000 Professional</TD -></TR -><TR -><TD ->Windows 200x Server/Advanced Server</TD -></TR -><TR -><TD ->Windows XP Professional</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 -><P ->MS Windows clients will cache the encrypted password alone. - Even when plain text passwords are re-enabled, through the appropriate - registry change, the plain text password is NEVER cached. This means that - in the event that a network connections should become disconnected (broken) - only the cached (encrypted) password will be sent to the resource server - to affect a auto-reconnect. If the resource server does not support encrypted - passwords the auto-reconnect will fail. <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->USE OF ENCRYPTED PASSWORDS - IS STRONGLY ADVISED.</I -></SPAN -></P -></TD -></TR -></TABLE -></DIV -><DIV -CLASS="SECT2" -><H2 -CLASS="SECT2" -><A -NAME="AEN368" ->3.2.1. Advantages of SMB Encryption</A -></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 SM not support 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 -><TR -><TD ->Encrypted password support allows automatic share - (resource) reconnects.</TD -></TR -></TBODY -></TABLE -><P -></P -></DIV -><DIV -CLASS="SECT2" -><H2 -CLASS="SECT2" -><A -NAME="AEN374" ->3.2.2. Advantages of non-encrypted passwords</A -></H2 -><P -></P -><TABLE -BORDER="0" -><TBODY -><TR -><TD ->Plain text passwords are not kept - on disk, and are NOT cached in memory. </TD -></TR -><TR -><TD ->Uses same password file as other unix - services such as login and ftp</TD -></TR -><TR -><TD ->Use of 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="AEN380" ->3.3. The smbpasswd Command</A -></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 -><SAMP -CLASS="PROMPT" ->$ </SAMP -><KBD -CLASS="USERINPUT" ->smbpasswd</KBD -></P -><P -><SAMP -CLASS="PROMPT" ->Old SMB password: </SAMP -><KBD -CLASS="USERINPUT" -><type old value here - - or hit return if there was no old password></KBD -></P -><P -><SAMP -CLASS="PROMPT" ->New SMB Password: </SAMP -><KBD -CLASS="USERINPUT" -><type new value> - </KBD -></P -><P -><SAMP -CLASS="PROMPT" ->Repeat New SMB Password: </SAMP -><KBD -CLASS="USERINPUT" -><re-type new value - </KBD -></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="AEN411" ->3.4. Plain text</A -></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="AEN416" ->3.5. TDB</A -></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="AEN419" ->3.6. LDAP</A -></H1 -><DIV -CLASS="SECT2" -><H2 -CLASS="SECT2" -><A -NAME="AEN421" ->3.6.1. Introduction</A -></H2 +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 @@ -566,13 +141,11 @@ TARGET="_top" ></UL ></DIV ><DIV -CLASS="SECT2" -><H2 -CLASS="SECT2" +CLASS="SECT1" +><H1 +CLASS="SECT1" ><A -NAME="AEN441" ->3.6.2. Introduction</A -></H2 +NAME="AEN2757">19.2. Introduction</H1 ><P >Traditionally, when configuring <A HREF="smb.conf.5.html#ENCRYPTPASSWORDS" @@ -627,27 +200,35 @@ Identified (RID).</P 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. <VAR +for a samdb backend (e.g. <TT CLASS="PARAMETER" ->--with-ldapsam</VAR +><I +>--with-ldapsam</I +></TT > or -<VAR +<TT CLASS="PARAMETER" ->--with-tdbsam</VAR +><I +>--with-tdbsam</I +></TT >) requires compile time support.</P ><P ->When compiling Samba to include the <VAR +>When compiling Samba to include the <TT CLASS="PARAMETER" ->--with-ldapsam</VAR +><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 <VAR +>There are a few points to stress about what the <TT CLASS="PARAMETER" ->--with-ldapsam</VAR +><I +>--with-ldapsam</I +></TT > does not provide. The LDAP support referred to in the this documentation does not include:</P @@ -675,45 +256,42 @@ TARGET="_top" the details of configuring these packages are beyond the scope of this document.</P ></DIV ><DIV -CLASS="SECT2" -><H2 -CLASS="SECT2" +CLASS="SECT1" +><H1 +CLASS="SECT1" ><A -NAME="AEN470" ->3.6.3. Supported LDAP Servers</A -></H2 -><P ->The LDAP samdb code in 2.2.3 (and later) 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 +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 +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="mailto:samba-patches@samba.org" +HREF="samba-patches@samba.org" TARGET="_top" >samba-patches@samba.org</A > and <A -HREF="mailto:jerry@samba.org" +HREF="jerry@samba.org" TARGET="_top" >jerry@samba.org</A >.</P ></DIV ><DIV -CLASS="SECT2" -><H2 -CLASS="SECT2" +CLASS="SECT1" +><H1 +CLASS="SECT1" ><A -NAME="AEN475" ->3.6.4. Schema and Relationship to the RFC 2307 posixAccount</A -></H2 +NAME="AEN2791">19.4. Schema and Relationship to the RFC 2307 posixAccount</H1 ><P ->Samba 3.0 includes the necessary schema file for OpenLDAP 2.0 in +>Samba 2.2.3 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 +>. (Note that this schema +file has been modified since the experimental support initially included +in 2.2.2). The sambaAccount objectclass is given here:</P ><P ><PRE CLASS="PROGRAMLISTING" @@ -730,7 +308,7 @@ CLASS="PROGRAMLISTING" 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="mailto:jerry@samba.org" +HREF="jerry@samba.org" TARGET="_top" >jerry@samba.org</A ></P @@ -741,9 +319,9 @@ CLASS="FILENAME" >/etc/passwd</TT > entry, so is the sambaAccount object meant to supplement the UNIX user account information. A sambaAccount is a -<CODE +<TT CLASS="CONSTANT" ->STRUCTURAL</CODE +>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 @@ -758,31 +336,27 @@ 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" +><H1 +CLASS="SECT1" +><A +NAME="AEN2803">19.5. Configuring Samba with LDAP</H1 +><DIV CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN487" ->3.6.5. Configuring Samba with LDAP</A -></H2 -><DIV -CLASS="SECT3" -><H3 -CLASS="SECT3" -><A -NAME="AEN489" ->3.6.5.1. OpenLDAP configuration</A -></H3 +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 ><P -><SAMP +><TT CLASS="PROMPT" ->root# </SAMP -><KBD -CLASS="USERINPUT" ->cp samba.schema /etc/openldap/schema/</KBD +>root# </TT +><B +CLASS="COMMAND" +>cp samba.schema /etc/openldap/schema/</B ></P ><P >Next, include the <TT @@ -848,17 +422,17 @@ index rid eq ></P ></DIV ><DIV -CLASS="SECT3" -><H3 -CLASS="SECT3" +CLASS="SECT2" +><H2 +CLASS="SECT2" ><A -NAME="AEN506" ->3.6.5.2. Configuring Samba</A -></H3 +NAME="AEN2822">19.5.2. Configuring Samba</H2 ><P ->The following parameters are available in smb.conf only with <VAR +>The following parameters are available in smb.conf only with <TT CLASS="PARAMETER" ->--with-ldapsam</VAR +><I +>--with-ldapsam</I +></TT > was included with compiling Samba.</P ><P @@ -936,9 +510,11 @@ CLASS="PROGRAMLISTING" # 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 <VAR + # must be set by using 'smbpasswd -w <TT CLASS="REPLACEABLE" ->secretpw</VAR +><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. @@ -959,18 +535,16 @@ CLASS="REPLACEABLE" ldap suffix = "ou=people,dc=samba,dc=org" # generally the default ldap search filter is ok - # ldap filter = "(&(uid=%u)(objectclass=sambaAccount))"</PRE + # ldap filter = "(&(uid=%u)(objectclass=sambaAccount))"</PRE ></P ></DIV ></DIV ><DIV -CLASS="SECT2" -><H2 -CLASS="SECT2" +CLASS="SECT1" +><H1 +CLASS="SECT1" ><A -NAME="AEN534" ->3.6.6. Accounts and Groups management</A -></H2 +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 @@ -983,19 +557,17 @@ in a different tree of you LDAP namespace: you should use 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. +>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="SECT2" -><H2 -CLASS="SECT2" +CLASS="SECT1" +><H1 +CLASS="SECT1" ><A -NAME="AEN539" ->3.6.7. Security and sambaAccount</A -></H2 +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 @@ -1068,13 +640,11 @@ access to attrs=lmPassword,ntPassword ></P ></DIV ><DIV -CLASS="SECT2" -><H2 -CLASS="SECT2" +CLASS="SECT1" +><H1 +CLASS="SECT1" ><A -NAME="AEN559" ->3.6.8. LDAP specials attributes for sambaAccounts</A -></H2 +NAME="AEN2875">19.8. LDAP specials attributes for sambaAccounts</H1 ><P >The sambaAccount objectclass is composed of the following attributes:</P ><P @@ -1082,84 +652,84 @@ NAME="AEN559" ><UL ><LI ><P -><CODE +><TT CLASS="CONSTANT" ->lmPassword</CODE +>lmPassword</TT >: the LANMAN password 16-byte hash stored as a character representation of a hexidecimal string.</P ></LI ><LI ><P -><CODE +><TT CLASS="CONSTANT" ->ntPassword</CODE +>ntPassword</TT >: the NT password hash 16-byte stored as a character representation of a hexidecimal string.</P ></LI ><LI ><P -><CODE +><TT CLASS="CONSTANT" ->pwdLastSet</CODE +>pwdLastSet</TT >: The integer time in seconds since 1970 when the - <CODE + <TT CLASS="CONSTANT" ->lmPassword</CODE -> and <CODE +>lmPassword</TT +> and <TT CLASS="CONSTANT" ->ntPassword</CODE +>ntPassword</TT > attributes were last set. </P ></LI ><LI ><P -><CODE +><TT CLASS="CONSTANT" ->acctFlags</CODE +>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 -><CODE +><TT CLASS="CONSTANT" ->logonTime</CODE +>logonTime</TT >: Integer value currently unused</P ></LI ><LI ><P -><CODE +><TT CLASS="CONSTANT" ->logoffTime</CODE +>logoffTime</TT >: Integer value currently unused</P ></LI ><LI ><P -><CODE +><TT CLASS="CONSTANT" ->kickoffTime</CODE +>kickoffTime</TT >: Integer value currently unused</P ></LI ><LI ><P -><CODE +><TT CLASS="CONSTANT" ->pwdCanChange</CODE +>pwdCanChange</TT >: Integer value currently unused</P ></LI ><LI ><P -><CODE +><TT CLASS="CONSTANT" ->pwdMustChange</CODE +>pwdMustChange</TT >: Integer value currently unused</P ></LI ><LI ><P -><CODE +><TT CLASS="CONSTANT" ->homeDrive</CODE +>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 @@ -1167,9 +737,9 @@ CLASS="CONSTANT" ></LI ><LI ><P -><CODE +><TT CLASS="CONSTANT" ->scriptPath</CODE +>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 @@ -1177,18 +747,18 @@ CLASS="CONSTANT" ></LI ><LI ><P -><CODE +><TT CLASS="CONSTANT" ->profilePath</CODE +>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 -><CODE +><TT CLASS="CONSTANT" ->smbHome</CODE +>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 @@ -1198,25 +768,25 @@ CLASS="CONSTANT" ></LI ><LI ><P -><CODE +><TT CLASS="CONSTANT" ->userWorkstation</CODE +>userWorkstation</TT >: character string value currently unused. </P ></LI ><LI ><P -><CODE +><TT CLASS="CONSTANT" ->rid</CODE +>rid</TT >: the integer representation of the user's relative identifier (RID).</P ></LI ><LI ><P -><CODE +><TT CLASS="CONSTANT" ->primaryGroupID</CODE +>primaryGroupID</TT >: the relative identifier (RID) of the primary group of the user.</P ></LI @@ -1261,27 +831,29 @@ its <TT CLASS="FILENAME" >smb.conf</TT > file. When a user named "becky" logons to the domain, -the <VAR +the <TT CLASS="PARAMETER" ->logon home</VAR +><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 <VAR +of the <TT CLASS="PARAMETER" ->logon home</VAR +><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" +CLASS="SECT1" +><H1 +CLASS="SECT1" ><A -NAME="AEN629" ->3.6.9. Example LDIF Entries for a sambaAccount</A -></H2 +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 @@ -1332,230 +904,19 @@ pwdMustChange: 2147483647 ntPassword: 878D8014606CDA29677A44EFA1353FC7</PRE ></P ></DIV -></DIV ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN637" ->3.7. MySQL</A -></H1 -><DIV -CLASS="SECT2" -><H2 -CLASS="SECT2" -><A -NAME="AEN639" ->3.7.1. Creating the database</A -></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<VAR -CLASS="REPLACEABLE" ->username</VAR -> -h<VAR -CLASS="REPLACEABLE" ->hostname</VAR -> -p<VAR -CLASS="REPLACEABLE" ->password</VAR -> <VAR -CLASS="REPLACEABLE" ->databasename</VAR -> < <TT -CLASS="FILENAME" ->/path/to/samba/examples/pdb/mysql/mysql.dump</TT -></B -> </P -></DIV -><DIV -CLASS="SECT2" -><H2 -CLASS="SECT2" -><A -NAME="AEN649" ->3.7.2. Configuring</A -></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] mysql: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 +NAME="AEN2953">19.10. Comments</H1 ><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="AEN666" ->3.7.3. Using plaintext passwords or encrypted password</A -></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="AEN671" ->3.7.4. Getting non-column data from the table</A -></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="AEN679" ->3.8. XML</A -></H1 -><P ->This module requires libxml2 to be installed.</P -><P ->The usage of pdb_xml is pretty straightforward. To export data, use: - -<KBD -CLASS="USERINPUT" ->pdbedit -e xml:filename</KBD -> - -(where filename is the name of the file to put the data in)</P -><P ->To import data, use: -<KBD -CLASS="USERINPUT" ->pdbedit -i xml:filename -e current-pdb</KBD -> - -Where filename is the name to read the data from and current-pdb to put it in.</P +>Please mail all comments regarding this HOWTO to <A +HREF="mailto:jerry@samba.org" +TARGET="_top" +>jerry@samba.org</A +>. This documents was +last updated to reflect the Samba 2.2.3 release. </P ></DIV ></DIV ><DIV @@ -1574,7 +935,7 @@ WIDTH="33%" ALIGN="left" VALIGN="top" ><A -HREF="browsing-quick.html" +HREF="vfs.html" ACCESSKEY="P" >Prev</A ></TD @@ -1592,7 +953,7 @@ WIDTH="33%" ALIGN="right" VALIGN="top" ><A -HREF="type.html" +HREF="cvs-access.html" ACCESSKEY="N" >Next</A ></TD @@ -1602,13 +963,13 @@ ACCESSKEY="N" WIDTH="33%" ALIGN="left" VALIGN="top" ->Quick Cross Subnet Browsing / Cross Workgroup Browsing guide</TD +>Stackable VFS modules</TD ><TD WIDTH="34%" ALIGN="center" VALIGN="top" ><A -HREF="introduction.html" +HREF="optional.html" ACCESSKEY="U" >Up</A ></TD @@ -1616,7 +977,7 @@ ACCESSKEY="U" WIDTH="33%" ALIGN="right" VALIGN="top" ->Type of installation</TD +>HOWTO Access Samba source code via CVS</TD ></TR ></TABLE ></DIV diff --git a/docs/htmldocs/samba-pdc.html b/docs/htmldocs/samba-pdc.html index 0c1e085159..93bbc727d4 100644 --- a/docs/htmldocs/samba-pdc.html +++ b/docs/htmldocs/samba-pdc.html @@ -2,10 +2,11 @@ <HTML ><HEAD ><TITLE ->Samba as an 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.7"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -13,10 +14,10 @@ REL="UP" TITLE="Type of installation" HREF="type.html"><LINK REL="PREVIOUS" -TITLE="Samba as Stand-Alone Server" +TITLE="User and Share security level (for servers not in a domain)" HREF="securitylevels.html"><LINK REL="NEXT" -TITLE="Samba Backup Domain Controller to Samba Domain Control" +TITLE="How to Act as a Backup Domain Controller in a Purely Samba Controlled Domain" HREF="samba-bdc.html"></HEAD ><BODY CLASS="CHAPTER" @@ -72,17 +73,13 @@ WIDTH="100%"></DIV CLASS="CHAPTER" ><H1 ><A -NAME="SAMBA-PDC" -></A ->Chapter 6. Samba as an 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="AEN878" ->6.1. Prerequisite Reading</A -></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 @@ -96,50 +93,19 @@ CLASS="FILENAME" >smb.conf(5)</TT ></A > -manpage.</P +manpage and the <A +HREF="ENCRYPTION.html" +TARGET="_top" +>Encryption chapter</A +> +of this HOWTO Collection.</P ></DIV ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN883" ->6.2. Background</A -></H1 -><P ->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.</P -><P -></P -><UL -><LI -><P -> Domain logons for Windows NT 4.0 / 200x / XP Professional clients. - </P -></LI -><LI -><P -> Placing Windows 9x / Me clients in user level security - </P -></LI -><LI -><P -> Retrieving a list of users and groups from a Samba PDC to - Windows 9x / Me / NT / 200x / XP Professional clients - </P -></LI -><LI -><P -> Roaming Profiles - </P -></LI -><LI -><P -> Network/System Policies - </P -></LI -></UL +NAME="AEN581">6.2. Background</H1 ><DIV CLASS="NOTE" ><P @@ -154,70 +120,113 @@ 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 ALIGN="LEFT" VALIGN="TOP" ><P ->Roaming Profiles and System/Network policies are advanced network administration topics -that are covered separately in this document.</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 ->The following functionalities are new to the Samba 3.0 release:</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 -> Windows NT 4 domain trusts +> domain logons for Windows NT 4.0/2000 clients. </P ></LI ><LI ><P -> Adding users via the User Manager for Domains +> 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 functionalities are NOT provided by Samba 3.0:</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 / Me / XP Home clients are not true members of a domain +>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 / Win2k type domain logons and has been officially supported for some +from NT4 domain logons and has been officially supported for some time.</P ><P -><SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->MS Windows XP Home edition is NOT able to join a domain and does not permit -the use of domain logons.</I -></SPAN -></P -><P ->Implementing a Samba PDC can basically be divided into 3 broad +>Implementing a Samba PDC can basically be divided into 2 broad steps.</P ><P ></P @@ -230,12 +239,8 @@ TYPE="1" ></LI ><LI ><P -> Creating machine trust accounts and joining clients to the domain - </P -></LI -><LI -><P -> Adding and managing domain user accounts +> Creating machine trust accounts and joining clients + to the domain </P ></LI ></OL @@ -243,26 +248,25 @@ TYPE="1" >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.</P +concepts. They will be mentioned only briefly here.</P ></DIV ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN923" ->6.3. Configuring the Samba Domain Controller</A -></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. Here we -attempt to explain the parameters that are covered in -<A +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 ->.</P +>. For convenience, the parameters have been +linked with the actual smb.conf description.</P ><P >Here is an example <TT CLASS="FILENAME" @@ -277,17 +281,21 @@ CLASS="PROGRAMLISTING" HREF="smb.conf.5.html#NETBIOSNAME" TARGET="_top" >netbios name</A -> = <VAR +> = <TT CLASS="REPLACEABLE" ->POGO</VAR +><I +>POGO</I +></TT > <A HREF="smb.conf.5.html#WORKGROUP" TARGET="_top" >workgroup</A -> = <VAR +> = <TT CLASS="REPLACEABLE" ->NARNIA</VAR +><I +>NARNIA</I +></TT > ; we should act as the domain and local master browser @@ -340,7 +348,8 @@ TARGET="_top" >logon path</A > = \\%N\profiles\%u - ; where is a user's home directory and where should it be mounted at? + ; where is a user's home directory and where should it + ; be mounted at? <A HREF="smb.conf.5.html#LOGONDRIVE" TARGET="_top" @@ -376,9 +385,11 @@ TARGET="_top" HREF="smb.conf.5.html#WRITELIST" TARGET="_top" >write list</A -> = <VAR +> = <TT CLASS="REPLACEABLE" ->ntadmin</VAR +><I +>ntadmin</I +></TT > ; share for storing user profiles @@ -413,7 +424,8 @@ TARGET="_top" ><P > Encrypted passwords must be enabled. For more details on how to do this, refer to <A -HREF="passdb.html" +HREF="ENCRYPTION.html" +TARGET="_top" >ENCRYPTION.html</A >. </P @@ -437,18 +449,24 @@ CLASS="FILENAME" ></LI ></UL ><P ->Samba 3.0 offers a complete implementation of group mapping +>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).</P +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" ><H1 CLASS="SECT1" ><A -NAME="AEN965" ->6.4. Creating Machine Trust Accounts and Joining Clients to the Domain</A -></H1 +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 authenticate a client machine (rather than a user) to the Samba @@ -459,127 +477,14 @@ Account."</P 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, 200x, XP Professional clients use machine trust -accounts, but Windows 9x / Me / XP Home clients do not. Hence, a -Windows 9x / Me / XP Home 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 +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-3 PDC also has to stoe machine trust account information -in a suitable back-end data store. With Samba-3 there can be multiple back-ends -for this including:</P -><P -></P -><UL -><LI -><P -> <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->smbpaswd</I -></SPAN -> - the plain ascii file stored used by - earlier versions of Samba. This file configuration option requires - a Unix/Linux system account for EVERY entry (ie: both for user and for - machine accounts). This file will be located in the <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->private</I -></SPAN -> - directory (default is /usr/local/samba/lib/private or on linux /etc/samba). - </P -></LI -><LI -><P -> <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->smbpasswd_nua</I -></SPAN -> - This file is independant of the - system wide user accounts. The use of this back-end option requires - specification of the "non unix account range" option also. It is called - smbpasswd and will be located in the <TT -CLASS="FILENAME" ->private</TT -> directory. - </P -></LI -><LI -><P -> <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->tdbsam</I -></SPAN -> - a binary database backend that will be - stored in the <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->private</I -></SPAN -> directory in a file called - <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->passwd.tdb</I -></SPAN ->. The key benefit of this binary format - file is that it can store binary objects that can not be accomodated - in the traditional plain text smbpasswd file. - </P -></LI -><LI -><P -> <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->tdbsam_nua</I -></SPAN -> like the smbpasswd_nua option above, this - file allows the creation of arbitrary user and machine accounts without - requiring that account to be added to the system (/etc/passwd) file. It - too requires the specification of the "non unix account range" option - in the [globals] section of the smb.conf file. - </P -></LI -><LI -><P -> <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->ldapsam</I -></SPAN -> - An LDAP based back-end. Permits the - LDAP server to be specified. eg: ldap://localhost or ldap://frodo.murphy.com - </P -></LI -><LI -><P -> <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->ldapsam_nua</I -></SPAN -> - LDAP based back-end with no unix - account requirement, like smbpasswd_nua and tdbsam_nua above. - </P -></LI -></UL -><P ->A Samba PDC, however, stores each machine trust account in two parts, -as follows: +Registry. A Samba PDC, however, stores each machine trust account +in two parts, as follows: <P ></P @@ -632,9 +537,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1008" ->6.4.1. Manual Creation of Machine Trust Accounts</A -></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 @@ -649,45 +552,55 @@ CLASS="COMMAND" used to create new Unix accounts. The following is an example for a Linux based Samba server:</P ><P -> <SAMP +> <TT CLASS="PROMPT" ->root# </SAMP +>root# </TT ><B CLASS="COMMAND" ->/usr/sbin/useradd -g 100 -d /dev/null -c <VAR +>/usr/sbin/useradd -g 100 -d /dev/null -c <TT CLASS="REPLACEABLE" +><I >"machine -nickname"</VAR -> -s /bin/false <VAR +nickname"</I +></TT +> -s /bin/false <TT CLASS="REPLACEABLE" ->machine_name</VAR +><I +>machine_name</I +></TT >$ </B ></P ><P -><SAMP +><TT CLASS="PROMPT" ->root# </SAMP +>root# </TT ><B CLASS="COMMAND" ->passwd -l <VAR +>passwd -l <TT CLASS="REPLACEABLE" ->machine_name</VAR +><I +>machine_name</I +></TT >$</B ></P ><P >On *BSD systems, this can be done using the 'chpass' utility:</P ><P -><SAMP +><TT CLASS="PROMPT" ->root# </SAMP +>root# </TT ><B CLASS="COMMAND" ->chpass -a "<VAR +>chpass -a "<TT CLASS="REPLACEABLE" ->machine_name</VAR ->$:*:101:100::0:0:Workstation <VAR +><I +>machine_name</I +></TT +>$:*:101:100::0:0:Workstation <TT CLASS="REPLACEABLE" ->machine_name</VAR +><I +>machine_name</I +></TT >:/dev/null:/sbin/nologin"</B ></P ><P @@ -704,20 +617,26 @@ CLASS="FILENAME" ><P ><PRE CLASS="PROGRAMLISTING" ->doppy$:x:505:501:<VAR +>doppy$:x:505:501:<TT CLASS="REPLACEABLE" ->machine_nickname</VAR +><I +>machine_nickname</I +></TT >:/dev/null:/bin/false</PRE ></P ><P ->Above, <VAR +>Above, <TT CLASS="REPLACEABLE" ->machine_nickname</VAR +><I +>machine_nickname</I +></TT > can be any descriptive name for the client, i.e., BasementComputer. -<VAR +<TT CLASS="REPLACEABLE" ->machine_name</VAR +><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 @@ -735,20 +654,24 @@ CLASS="COMMAND" > command as shown here:</P ><P -><SAMP +><TT CLASS="PROMPT" ->root# </SAMP +>root# </TT ><B CLASS="COMMAND" ->smbpasswd -a -m <VAR +>smbpasswd -a -m <TT CLASS="REPLACEABLE" ->machine_name</VAR +><I +>machine_name</I +></TT ></B ></P ><P ->where <VAR +>where <TT CLASS="REPLACEABLE" ->machine_name</VAR +><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 @@ -766,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 @@ -802,9 +725,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1049" ->6.4.2. "On-the-Fly" Creation of Machine Trust Accounts</A -></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 @@ -839,9 +760,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1058" ->6.4.3. Joining the Client to the Domain</A -></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 @@ -907,9 +826,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1073" ->6.5. Common Problems and Errors</A -></H1 +NAME="AEN747">6.5. Common Problems and Errors</H1 ><P ></P ><P @@ -963,9 +880,9 @@ CLASS="EMPHASIS" will remove all network drive connections: </P ><P -> <SAMP +> <TT CLASS="PROMPT" ->C:\WINNT\></SAMP +>C:\WINNT\></TT > <B CLASS="COMMAND" >net use * /d</B @@ -991,16 +908,23 @@ CLASS="EMPHASIS" ><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 again or consult your + 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 the secrets.tdb database - is changed. The most common cause of a change in domain SID is when - the domain name and/or the server name (netbios name) is changed. - The only way to correct the problem is to restore the original domain - SID or remove the domain client from the domain and rejoin. The domain - SID may be reset using either the smbpasswd or rpcclient utilities. +> 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 @@ -1021,9 +945,11 @@ CLASS="EMPHASIS" </P ><P > This problem is caused by the PDC not having a suitable machine trust account. - If you are using the <VAR + If you are using the <TT CLASS="PARAMETER" ->add user script</VAR +><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. @@ -1067,9 +993,11 @@ CLASS="COMMAND" </P ><P > In order to work around this problem in 2.2.0, configure the - <VAR + <TT CLASS="PARAMETER" ->account</VAR +><I +>account</I +></TT > control flag in <TT CLASS="FILENAME" @@ -1106,9 +1034,182 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1119" ->6.6. What other help can I get?</A -></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 +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" +><H1 +CLASS="SECT1" +><A +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 @@ -1526,27 +1627,60 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1233" ->6.7. Domain Control for Windows 9x/ME</A -></H1 +NAME="AEN953">6.8. Domain Control for Windows 9x/ME</H1 +><DIV +CLASS="NOTE" +><P +></P +><TABLE +CLASS="NOTE" +WIDTH="100%" +BORDER="0" +><TR +><TD +WIDTH="25" +ALIGN="CENTER" +VALIGN="TOP" +><IMG +SRC="../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. Samba-3 does this -now in the same way that MS Windows NT/2K.</P +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 this documentation under the browsing discussions. -It should be noted, that browsing is totally orthogonal to logon support.</P +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 are the focus of this section.</P +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 @@ -1625,9 +1759,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1256" ->6.7.1. Configuration Instructions: Network Logons</A -></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 @@ -1660,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 @@ -1680,20 +1812,20 @@ VALIGN="TOP" >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 <CODE +modes other than <TT CLASS="CONSTANT" ->USER</CODE +>USER</TT >. The only security mode -which will not work due to technical reasons is <CODE +which will not work due to technical reasons is <TT CLASS="CONSTANT" ->SHARE</CODE +>SHARE</TT > -mode security. <CODE +mode security. <TT CLASS="CONSTANT" ->DOMAIN</CODE -> and <CODE +>DOMAIN</TT +> and <TT CLASS="CONSTANT" ->SERVER</CODE +>SERVER</TT > mode security is really just a variation on SMB user level security.</P ><P @@ -1726,6 +1858,685 @@ for its domain.</P ></TABLE ></DIV ></DIV +><DIV +CLASS="SECT2" +><H2 +CLASS="SECT2" +><A +NAME="AEN998">6.8.2. Configuration Instructions: Setting up Roaming User Profiles</H2 +><DIV +CLASS="WARNING" +><P +></P +><TABLE +CLASS="WARNING" +WIDTH="100%" +BORDER="0" +><TR +><TD +WIDTH="25" +ALIGN="CENTER" +VALIGN="TOP" +><IMG +SRC="../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" +><H3 +CLASS="SECT3" +><A +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 +><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="../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" +><H3 +CLASS="SECT3" +><A +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 +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" +><H3 +CLASS="SECT3" +><A +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 +><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="../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" +><H3 +CLASS="SECT3" +><A +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". +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" +><H3 +CLASS="SECT3" +><A +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 +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="../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="../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" +><H3 +CLASS="SECT3" +><A +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 +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" +><H3 +CLASS="SECT3" +><A +NAME="AEN1081">6.8.2.7. Sharing Profiles between W95 and NT Workstation 4.0</H3 +><DIV +CLASS="WARNING" +><P +></P +><TABLE +CLASS="WARNING" +WIDTH="100%" +BORDER="0" +><TR +><TD +WIDTH="25" +ALIGN="CENTER" +VALIGN="TOP" +><IMG +SRC="../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="../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" +><H1 +CLASS="SECT1" +><A +NAME="AEN1091">6.9. DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba</H1 +><DIV +CLASS="WARNING" +><P +></P +><TABLE +CLASS="WARNING" +WIDTH="100%" +BORDER="0" +><TR +><TD +WIDTH="25" +ALIGN="CENTER" +VALIGN="TOP" +><IMG +SRC="../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 @@ -1772,7 +2583,7 @@ ACCESSKEY="N" WIDTH="33%" ALIGN="left" VALIGN="top" ->Samba as Stand-Alone Server</TD +>User and Share security level (for servers not in a domain)</TD ><TD WIDTH="34%" ALIGN="center" @@ -1786,7 +2597,7 @@ ACCESSKEY="U" WIDTH="33%" ALIGN="right" VALIGN="top" ->Samba Backup Domain Controller to Samba Domain Control</TD +>How to Act as a Backup Domain Controller in a Purely Samba Controlled Domain</TD ></TR ></TABLE ></DIV diff --git a/docs/htmldocs/samba.7.html b/docs/htmldocs/samba.7.html index 689fba7cee..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.7"></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/securing-samba.html b/docs/htmldocs/securing-samba.html deleted file mode 100644 index 3cee4ac6b4..0000000000 --- a/docs/htmldocs/securing-samba.html +++ /dev/null @@ -1,320 +0,0 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> -<HTML -><HEAD -><TITLE ->Securing Samba</TITLE -><META -NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK -REL="HOME" -TITLE="SAMBA Project Documentation" -HREF="samba-howto-collection.html"><LINK -REL="UP" -TITLE="Advanced Configuration" -HREF="optional.html"><LINK -REL="PREVIOUS" -TITLE="Improved browsing in samba" -HREF="improved-browsing.html"><LINK -REL="NEXT" -TITLE="Unicode/Charsets" -HREF="unicode.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="improved-browsing.html" -ACCESSKEY="P" ->Prev</A -></TD -><TD -WIDTH="80%" -ALIGN="center" -VALIGN="bottom" -></TD -><TD -WIDTH="10%" -ALIGN="right" -VALIGN="bottom" -><A -HREF="unicode.html" -ACCESSKEY="N" ->Next</A -></TD -></TR -></TABLE -><HR -ALIGN="LEFT" -WIDTH="100%"></DIV -><DIV -CLASS="CHAPTER" -><H1 -><A -NAME="SECURING-SAMBA" -></A ->Chapter 24. Securing Samba</H1 -><DIV -CLASS="SECT1" -><H1 -CLASS="SECT1" -><A -NAME="AEN4003" ->24.1. Introduction</A -></H1 -><P ->This note was attached to the Samba 2.2.8 release notes as it contained an -important security fix. The information contained here applies to Samba -installations in general.</P -></DIV -><DIV -CLASS="SECT1" -><H1 -CLASS="SECT1" -><A -NAME="AEN4006" ->24.2. Using host based protection</A -></H1 -><P ->In many installations of Samba the greatest threat comes for outside -your immediate network. By default Samba will accept connections from -any host, which means that if you run an insecure version of Samba on -a host that is directly connected to the Internet you can be -especially vulnerable.</P -><P ->One of the simplest fixes in this case is to use the <B -CLASS="COMMAND" ->hosts allow</B -> and -<B -CLASS="COMMAND" ->hosts deny</B -> options in the Samba <TT -CLASS="FILENAME" ->smb.conf</TT -> configuration file to only -allow access to your server from a specific range of hosts. An example -might be:</P -><P -><PRE -CLASS="PROGRAMLISTING" -> hosts allow = 127.0.0.1 192.168.2.0/24 192.168.3.0/24 - hosts deny = 0.0.0.0/0</PRE -></P -><P ->The above will only allow SMB connections from 'localhost' (your own -computer) and from the two private networks 192.168.2 and -192.168.3. All other connections will be refused connections as soon -as the client sends its first packet. The refusal will be marked as a -'not listening on called name' error.</P -></DIV -><DIV -CLASS="SECT1" -><H1 -CLASS="SECT1" -><A -NAME="AEN4016" ->24.3. Using interface protection</A -></H1 -><P ->By default Samba will accept connections on any network interface that -it finds on your system. That means if you have a ISDN line or a PPP -connection to the Internet then Samba will accept connections on those -links. This may not be what you want.</P -><P ->You can change this behaviour using options like the following:</P -><P -><PRE -CLASS="PROGRAMLISTING" -> interfaces = eth* lo - bind interfaces only = yes</PRE -></P -><P -></P -><P ->This tells Samba to only listen for connections on interfaces with a -name starting with 'eth' such as eth0, eth1, plus on the loopback -interface called 'lo'. The name you will need to use depends on what -OS you are using, in the above I used the common name for Ethernet -adapters on Linux.</P -><P ->If you use the above and someone tries to make a SMB connection to -your host over a PPP interface called 'ppp0' then they will get a TCP -connection refused reply. In that case no Samba code is run at all as -the operating system has been told not to pass connections from that -interface to any process.</P -></DIV -><DIV -CLASS="SECT1" -><H1 -CLASS="SECT1" -><A -NAME="AEN4025" ->24.4. Using a firewall</A -></H1 -><P ->Many people use a firewall to deny access to services that they don't -want exposed outside their network. This can be a very good idea, -although I would recommend using it in conjunction with the above -methods so that you are protected even if your firewall is not active -for some reason.</P -><P ->If you are setting up a firewall then you need to know what TCP and -UDP ports to allow and block. Samba uses the following:</P -><P -><PRE -CLASS="PROGRAMLISTING" ->UDP/137 - used by nmbd -UDP/138 - used by nmbd -TCP/139 - used by smbd -TCP/445 - used by smbd</PRE -></P -><P ->The last one is important as many older firewall setups may not be -aware of it, given that this port was only added to the protocol in -recent years. </P -></DIV -><DIV -CLASS="SECT1" -><H1 -CLASS="SECT1" -><A -NAME="AEN4032" ->24.5. Using a IPC$ share deny</A -></H1 -><P ->If the above methods are not suitable, then you could also place a -more specific deny on the IPC$ share that is used in the recently -discovered security hole. This allows you to offer access to other -shares while denying access to IPC$ from potentially untrustworthy -hosts.</P -><P ->To do that you could use:</P -><P -><PRE -CLASS="PROGRAMLISTING" -> [ipc$] - hosts allow = 192.168.115.0/24 127.0.0.1 - hosts deny = 0.0.0.0/0</PRE -></P -><P ->this would tell Samba that IPC$ connections are not allowed from -anywhere but the two listed places (localhost and a local -subnet). Connections to other shares would still be allowed. As the -IPC$ share is the only share that is always accessible anonymously -this provides some level of protection against attackers that do not -know a username/password for your host.</P -><P ->If you use this method then clients will be given a 'access denied' -reply when they try to access the IPC$ share. That means that those -clients will not be able to browse shares, and may also be unable to -access some other resources. </P -><P ->This is not recommended unless you cannot use one of the other -methods listed above for some reason.</P -></DIV -><DIV -CLASS="SECT1" -><H1 -CLASS="SECT1" -><A -NAME="AEN4041" ->24.6. Upgrading Samba</A -></H1 -><P ->Please check regularly on <A -HREF="http://www.samba.org/" -TARGET="_top" ->http://www.samba.org/</A -> for updates and -important announcements. Occasionally security releases are made and -it is highly recommended to upgrade Samba when a security vulnerability -is discovered.</P -></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="improved-browsing.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="unicode.html" -ACCESSKEY="N" ->Next</A -></TD -></TR -><TR -><TD -WIDTH="33%" -ALIGN="left" -VALIGN="top" ->Improved browsing in samba</TD -><TD -WIDTH="34%" -ALIGN="center" -VALIGN="top" -><A -HREF="optional.html" -ACCESSKEY="U" ->Up</A -></TD -><TD -WIDTH="33%" -ALIGN="right" -VALIGN="top" ->Unicode/Charsets</TD -></TR -></TABLE -></DIV -></BODY -></HTML ->
\ No newline at end of file diff --git a/docs/htmldocs/securitylevels.html b/docs/htmldocs/securitylevels.html index 256df33ce4..f1b9967540 100644 --- a/docs/htmldocs/securitylevels.html +++ b/docs/htmldocs/securitylevels.html @@ -2,10 +2,11 @@ <HTML ><HEAD ><TITLE ->Samba as Stand-Alone Server</TITLE +>User and Share security level (for servers not in a domain)</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -13,10 +14,10 @@ REL="UP" TITLE="Type of installation" HREF="type.html"><LINK REL="PREVIOUS" -TITLE="Nomenclature of Server Types" -HREF="servertype.html"><LINK +TITLE="Type of installation" +HREF="type.html"><LINK REL="NEXT" -TITLE="Samba as an 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" @@ -45,7 +46,7 @@ WIDTH="10%" ALIGN="left" VALIGN="bottom" ><A -HREF="servertype.html" +HREF="type.html" ACCESSKEY="P" >Prev</A ></TD @@ -72,26 +73,7 @@ WIDTH="100%"></DIV CLASS="CHAPTER" ><H1 ><A -NAME="SECURITYLEVELS" -></A ->Chapter 5. Samba as Stand-Alone Server</H1 -><P ->In this section the function and purpose of Samba's <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->security</I -></SPAN -> -modes are described.</P -><DIV -CLASS="SECT1" -><H1 -CLASS="SECT1" -><A -NAME="AEN766" ->5.1. User and Share security level</A -></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 @@ -102,14 +84,6 @@ 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 -><DIV -CLASS="SECT2" -><H2 -CLASS="SECT2" -><A -NAME="AEN769" ->5.1.1. User Level Security</A -></H2 ><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 @@ -142,15 +116,6 @@ 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 -></DIV -><DIV -CLASS="SECT2" -><H2 -CLASS="SECT2" -><A -NAME="AEN779" ->5.1.2. Share Level Security</A -></H2 ><P >Ok, now for share level security. In share level security the client authenticates itself separately for each share. It will send a @@ -169,25 +134,10 @@ 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 <B -CLASS="COMMAND" ->user =</B -> <TT -CLASS="FILENAME" ->smb.conf</TT -> +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 -></DIV -><DIV -CLASS="SECT2" -><H2 -CLASS="SECT2" -><A -NAME="AEN785" ->5.1.3. Server Level Security</A -></H2 ><P >Finally "server level" security. In server level security the samba server reports to the client that it is in user level security. The @@ -216,263 +166,6 @@ 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 -CLASS="SECT3" -><H3 -CLASS="SECT3" -><A -NAME="AEN790" ->5.1.3.1. Configuring Samba for Seemless Windows Network Integration</A -></H3 -><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 requests.</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 ->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, support was dropped 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 -service connection 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 -> = <VAR -CLASS="REPLACEABLE" ->integer</VAR -> - <A -HREF="smb.conf.5.html#USERNAMELEVEL" -TARGET="_top" ->username level</A -> = <VAR -CLASS="REPLACEABLE" ->integer</VAR -></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 <VAR -CLASS="PARAMETER" ->username level</VAR -> parameter -is rarely needed.</P -><P ->However, passwords 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 <VAR -CLASS="PARAMETER" ->password level</VAR -> -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 <VAR -CLASS="PARAMETER" ->password level</VAR -> 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 -><DIV -CLASS="SECT3" -><H3 -CLASS="SECT3" -><A -NAME="AEN816" ->5.1.3.2. Use MS Windows NT as an authentication server</A -></H3 -><P ->This method involves the additions of the following parameters in the <TT -CLASS="FILENAME" ->smb.conf</TT -> 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 -><DIV -CLASS="SECT2" -><H2 -CLASS="SECT2" -><A -NAME="AEN825" ->5.1.4. Domain Level Security</A -></H2 -><P ->When samba is operating in <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->security = domain</I -></SPAN -> mode this means that -the Samba server has a domain security trust account (a machine account) and will cause -all authentication requests to be passed through to the domain controllers.</P -><DIV -CLASS="SECT3" -><H3 -CLASS="SECT3" -><A -NAME="AEN829" ->5.1.4.1. Samba as a member of an MS Windows NT security domain</A -></H3 -><P ->This method involves additon of the following paramters in the <TT -CLASS="FILENAME" ->smb.conf</TT -> 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 <B -CLASS="COMMAND" ->password server</B -> will cause samba to locate the -domain controller in a way analogous to the way this is done within MS Windows NT. -This is the default behaviour.</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 -><DIV -CLASS="SECT2" -><H2 -CLASS="SECT2" -><A -NAME="AEN848" ->5.1.5. ADS Level Security</A -></H2 -><P ->For information about the configuration option please refer to the entire section entitled -<SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->Samba as an ADS Domain Member.</I -></SPAN -></P -></DIV -></DIV ></DIV ><DIV CLASS="NAVFOOTER" @@ -490,7 +183,7 @@ WIDTH="33%" ALIGN="left" VALIGN="top" ><A -HREF="servertype.html" +HREF="type.html" ACCESSKEY="P" >Prev</A ></TD @@ -518,7 +211,7 @@ ACCESSKEY="N" WIDTH="33%" ALIGN="left" VALIGN="top" ->Nomenclature of Server Types</TD +>Type of installation</TD ><TD WIDTH="34%" ALIGN="center" @@ -532,7 +225,7 @@ ACCESSKEY="U" WIDTH="33%" ALIGN="right" VALIGN="top" ->Samba as an 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 6ebe2fc002..4f02951a9c 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.7"></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 @@ -69,13 +70,17 @@ NAME="AEN17" until the next section begins. Sections contain parameters of the form</P ><P -><VAR +><TT CLASS="REPLACEABLE" ->name</VAR -> = <VAR +><I +>name</I +></TT +> = <TT CLASS="REPLACEABLE" +><I >value - </VAR + </I +></TT ></P ><P >The file is line-based - that is, each newline-terminated @@ -105,7 +110,7 @@ CLASS="REPLACEABLE" ><DIV CLASS="REFSECT1" ><A -NAME="AEN29" +NAME="AEN28" ></A ><H2 >SECTION DESCRIPTIONS</H2 @@ -118,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 @@ -137,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 @@ -172,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" -><SAMP +> <TT CLASS="COMPUTEROUTPUT" ->[foo] - path = /home/bar - read only = no</SAMP -></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" -><SAMP +> <TT CLASS="COMPUTEROUTPUT" ->[aprinter] - path = /usr/spool/public - read only = yes - printable = yes - guest ok = yes</SAMP -></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 @@ -227,7 +242,7 @@ NAME="AEN51" ><DIV CLASS="REFSECT2" ><A -NAME="AEN54" +NAME="AEN53" ></A ><H3 >The [homes] section</H3 @@ -260,19 +275,18 @@ 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 ><P -><KBD +><TT CLASS="USERINPUT" ->path = /data/pchome/%S</KBD +><B +>path = /data/pchome/%S</B +></TT ></P ><P >would be useful if you have different home directories @@ -292,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" -><SAMP +> <TT CLASS="COMPUTEROUTPUT" ->[homes] - read only = no</SAMP -></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 @@ -341,7 +354,7 @@ CLASS="EMPHASIS" ><DIV CLASS="REFSECT2" ><A -NAME="AEN80" +NAME="AEN79" ></A ><H3 >The [printers] section</H3 @@ -393,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" -><SAMP +><TT CLASS="COMPUTEROUTPUT" ->[printers] - path = /usr/spool/public - guest ok = yes - printable = yes </SAMP +> [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" -><SAMP +> <TT CLASS="COMPUTEROUTPUT" ->alias|alias|alias|alias... </SAMP -></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 @@ -426,42 +460,18 @@ CLASS="COMPUTEROUTPUT" first entry of a printcap record. Records are separated by newlines, components (if there are more than one) are separated by vertical bar symbols ('|').</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 ->On SYSV systems which use lpstat to determine what +>NOTE: On SYSV systems which use lpstat to determine what printers are defined on the system you may be able to use "printcap name = lpstat" to automatically obtain a list of printers. See the "printcap name" option for more details.</P -></TD -></TR -></TABLE -></DIV ></DIV ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN104" +NAME="AEN102" ></A ><H2 >PARAMETERS</H2 @@ -469,44 +479,29 @@ NAME="AEN104" >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 @@ -519,7 +514,7 @@ CLASS="EMPHASIS" ><DIV CLASS="REFSECT1" ><A -NAME="AEN114" +NAME="AEN112" ></A ><H2 >VARIABLE SUBSTITUTIONS</H2 @@ -632,16 +627,20 @@ TARGET="_top" >Name of the domain or workgroup of the current user.</P ></DD ><DT ->%$(<VAR +>%$(<TT CLASS="REPLACEABLE" ->envvar</VAR +><I +>envvar</I +></TT >)</DT ><DD ><P >The value of the environment variable - <VAR + <TT CLASS="REPLACEABLE" ->envar</VAR +><I +>envar</I +></TT >.</P ></DD ></DL @@ -692,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 @@ -718,7 +714,7 @@ CLASS="EMPHASIS" ><DIV CLASS="REFSECT1" ><A -NAME="AEN207" +NAME="AEN205" ></A ><H2 >NAME MANGLING</H2 @@ -747,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 @@ -761,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 @@ -774,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 @@ -788,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 @@ -806,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 @@ -823,7 +804,7 @@ CLASS="EMPHASIS" ><DIV CLASS="REFSECT1" ><A -NAME="AEN240" +NAME="AEN238" ></A ><H2 >NOTE ABOUT USERNAME/PASSWORD VALIDATION</H2 @@ -847,9 +828,11 @@ TYPE="1" pair and that username/password pair is validated by the UNIX system's password programs then the connection is made as that username. Note that this includes the - \\server\service%<VAR + \\server\service%<TT CLASS="REPLACEABLE" ->username</VAR +><I +>username</I +></TT > method of passing a username.</P ></LI @@ -899,7 +882,7 @@ CLASS="FILENAME" ><DIV CLASS="REFSECT1" ><A -NAME="AEN259" +NAME="AEN257" ></A ><H2 >COMPLETE LIST OF GLOBAL PARAMETERS</H2 @@ -913,9 +896,11 @@ NAME="AEN259" ><P ><A HREF="#ABORTSHUTDOWNSCRIPT" -><VAR +><TT CLASS="PARAMETER" ->abort shutdown script</VAR +><I +>abort shutdown script</I +></TT ></A ></P ></LI @@ -923,9 +908,11 @@ CLASS="PARAMETER" ><P ><A HREF="#ADDGROUPSCRIPT" -><VAR +><TT CLASS="PARAMETER" ->add group script</VAR +><I +>add group script</I +></TT ></A ></P ></LI @@ -933,9 +920,11 @@ CLASS="PARAMETER" ><P ><A HREF="#ADDPRINTERCOMMAND" -><VAR +><TT CLASS="PARAMETER" ->addprinter command</VAR +><I +>addprinter command</I +></TT ></A ></P ></LI @@ -943,9 +932,11 @@ CLASS="PARAMETER" ><P ><A HREF="#ADDSHARECOMMAND" -><VAR +><TT CLASS="PARAMETER" ->add share command</VAR +><I +>add share command</I +></TT ></A ></P ></LI @@ -953,9 +944,11 @@ CLASS="PARAMETER" ><P ><A HREF="#ADDUSERSCRIPT" -><VAR +><TT CLASS="PARAMETER" ->add user script</VAR +><I +>add user script</I +></TT ></A ></P ></LI @@ -963,9 +956,11 @@ CLASS="PARAMETER" ><P ><A HREF="#ADDUSERTOGROUPSCRIPT" -><VAR +><TT CLASS="PARAMETER" ->add user to group script</VAR +><I +>add user to group script</I +></TT ></A ></P ></LI @@ -973,9 +968,11 @@ CLASS="PARAMETER" ><P ><A HREF="#ADDMACHINESCRIPT" -><VAR +><TT CLASS="PARAMETER" ->add machine script</VAR +><I +>add machine script</I +></TT ></A ></P ></LI @@ -983,9 +980,11 @@ CLASS="PARAMETER" ><P ><A HREF="#DELETEGROUPSCRIPT" -><VAR +><TT CLASS="PARAMETER" ->delete group script</VAR +><I +>delete group script</I +></TT ></A ></P ></LI @@ -993,9 +992,11 @@ CLASS="PARAMETER" ><P ><A HREF="#ADSSERVER" -><VAR +><TT CLASS="PARAMETER" ->ads server</VAR +><I +>ads server</I +></TT ></A ></P ></LI @@ -1003,9 +1004,11 @@ CLASS="PARAMETER" ><P ><A HREF="#ALGORITHMICRIDBASE" -><VAR +><TT CLASS="PARAMETER" ->algorithmic rid base</VAR +><I +>algorithmic rid base</I +></TT ></A ></P ></LI @@ -1013,9 +1016,11 @@ CLASS="PARAMETER" ><P ><A HREF="#ALLOWTRUSTEDDOMAINS" -><VAR +><TT CLASS="PARAMETER" ->allow trusted domains</VAR +><I +>allow trusted domains</I +></TT ></A ></P ></LI @@ -1023,9 +1028,11 @@ CLASS="PARAMETER" ><P ><A HREF="#ANNOUNCEAS" -><VAR +><TT CLASS="PARAMETER" ->announce as</VAR +><I +>announce as</I +></TT ></A ></P ></LI @@ -1033,9 +1040,11 @@ CLASS="PARAMETER" ><P ><A HREF="#ANNOUNCEVERSION" -><VAR +><TT CLASS="PARAMETER" ->announce version</VAR +><I +>announce version</I +></TT ></A ></P ></LI @@ -1043,9 +1052,11 @@ CLASS="PARAMETER" ><P ><A HREF="#AUTHMETHODS" -><VAR +><TT CLASS="PARAMETER" ->auth methods</VAR +><I +>auth methods</I +></TT ></A ></P ></LI @@ -1053,9 +1064,11 @@ CLASS="PARAMETER" ><P ><A HREF="#AUTOSERVICES" -><VAR +><TT CLASS="PARAMETER" ->auto services</VAR +><I +>auto services</I +></TT ></A ></P ></LI @@ -1063,9 +1076,11 @@ CLASS="PARAMETER" ><P ><A HREF="#BINDINTERFACESONLY" -><VAR +><TT CLASS="PARAMETER" ->bind interfaces only</VAR +><I +>bind interfaces only</I +></TT ></A ></P ></LI @@ -1073,9 +1088,11 @@ CLASS="PARAMETER" ><P ><A HREF="#BROWSELIST" -><VAR +><TT CLASS="PARAMETER" ->browse list</VAR +><I +>browse list</I +></TT ></A ></P ></LI @@ -1083,9 +1100,11 @@ CLASS="PARAMETER" ><P ><A HREF="#CHANGENOTIFYTIMEOUT" -><VAR +><TT CLASS="PARAMETER" ->change notify timeout</VAR +><I +>change notify timeout</I +></TT ></A ></P ></LI @@ -1093,9 +1112,11 @@ CLASS="PARAMETER" ><P ><A HREF="#CHANGESHARECOMMAND" -><VAR +><TT CLASS="PARAMETER" ->change share command</VAR +><I +>change share command</I +></TT ></A ></P ></LI @@ -1103,9 +1124,11 @@ CLASS="PARAMETER" ><P ><A HREF="#CONFIGFILE" -><VAR +><TT CLASS="PARAMETER" ->config file</VAR +><I +>config file</I +></TT ></A ></P ></LI @@ -1113,9 +1136,11 @@ CLASS="PARAMETER" ><P ><A HREF="#DEADTIME" -><VAR +><TT CLASS="PARAMETER" ->deadtime</VAR +><I +>deadtime</I +></TT ></A ></P ></LI @@ -1123,9 +1148,11 @@ CLASS="PARAMETER" ><P ><A HREF="#DEBUGHIRESTIMESTAMP" -><VAR +><TT CLASS="PARAMETER" ->debug hires timestamp</VAR +><I +>debug hires timestamp</I +></TT ></A ></P ></LI @@ -1133,9 +1160,11 @@ CLASS="PARAMETER" ><P ><A HREF="#DEBUGPID" -><VAR +><TT CLASS="PARAMETER" ->debug pid</VAR +><I +>debug pid</I +></TT ></A ></P ></LI @@ -1143,9 +1172,11 @@ CLASS="PARAMETER" ><P ><A HREF="#DEBUGTIMESTAMP" -><VAR +><TT CLASS="PARAMETER" ->debug timestamp</VAR +><I +>debug timestamp</I +></TT ></A ></P ></LI @@ -1153,9 +1184,11 @@ CLASS="PARAMETER" ><P ><A HREF="#DEBUGUID" -><VAR +><TT CLASS="PARAMETER" ->debug uid</VAR +><I +>debug uid</I +></TT ></A ></P ></LI @@ -1163,9 +1196,11 @@ CLASS="PARAMETER" ><P ><A HREF="#DEBUGLEVEL" -><VAR +><TT CLASS="PARAMETER" ->debuglevel</VAR +><I +>debuglevel</I +></TT ></A ></P ></LI @@ -1173,9 +1208,11 @@ CLASS="PARAMETER" ><P ><A HREF="#DEFAULT" -><VAR +><TT CLASS="PARAMETER" ->default</VAR +><I +>default</I +></TT ></A ></P ></LI @@ -1183,9 +1220,11 @@ CLASS="PARAMETER" ><P ><A HREF="#DEFAULTSERVICE" -><VAR +><TT CLASS="PARAMETER" ->default service</VAR +><I +>default service</I +></TT ></A ></P ></LI @@ -1193,9 +1232,11 @@ CLASS="PARAMETER" ><P ><A HREF="#DELETEPRINTERCOMMAND" -><VAR +><TT CLASS="PARAMETER" ->deleteprinter command</VAR +><I +>deleteprinter command</I +></TT ></A ></P ></LI @@ -1203,9 +1244,11 @@ CLASS="PARAMETER" ><P ><A HREF="#DELETESHARECOMMAND" -><VAR +><TT CLASS="PARAMETER" ->delete share command</VAR +><I +>delete share command</I +></TT ></A ></P ></LI @@ -1213,9 +1256,11 @@ CLASS="PARAMETER" ><P ><A HREF="#DELETEUSERSCRIPT" -><VAR +><TT CLASS="PARAMETER" ->delete user script</VAR +><I +>delete user script</I +></TT ></A ></P ></LI @@ -1223,9 +1268,11 @@ CLASS="PARAMETER" ><P ><A HREF="#DELETEUSERFROMGROUPSCRIPT" -><VAR +><TT CLASS="PARAMETER" ->delete user from group script</VAR +><I +>delete user from group script</I +></TT ></A ></P ></LI @@ -1233,9 +1280,11 @@ CLASS="PARAMETER" ><P ><A HREF="#DFREECOMMAND" -><VAR +><TT CLASS="PARAMETER" ->dfree command</VAR +><I +>dfree command</I +></TT ></A ></P ></LI @@ -1243,9 +1292,11 @@ CLASS="PARAMETER" ><P ><A HREF="#DISABLENETBIOS" -><VAR +><TT CLASS="PARAMETER" ->disable netbios</VAR +><I +>disable netbios</I +></TT ></A ></P ></LI @@ -1253,9 +1304,11 @@ CLASS="PARAMETER" ><P ><A HREF="#DISABLESPOOLSS" -><VAR +><TT CLASS="PARAMETER" ->disable spoolss</VAR +><I +>disable spoolss</I +></TT ></A ></P ></LI @@ -1263,9 +1316,11 @@ CLASS="PARAMETER" ><P ><A HREF="#DISPLAYCHARSET" -><VAR +><TT CLASS="PARAMETER" ->display charset</VAR +><I +>display charset</I +></TT ></A ></P ></LI @@ -1273,9 +1328,11 @@ CLASS="PARAMETER" ><P ><A HREF="#DNSPROXY" -><VAR +><TT CLASS="PARAMETER" ->dns proxy</VAR +><I +>dns proxy</I +></TT ></A ></P ></LI @@ -1283,9 +1340,11 @@ CLASS="PARAMETER" ><P ><A HREF="#DOMAINLOGONS" -><VAR +><TT CLASS="PARAMETER" ->domain logons</VAR +><I +>domain logons</I +></TT ></A ></P ></LI @@ -1293,9 +1352,11 @@ CLASS="PARAMETER" ><P ><A HREF="#DOMAINMASTER" -><VAR +><TT CLASS="PARAMETER" ->domain master</VAR +><I +>domain master</I +></TT ></A ></P ></LI @@ -1303,9 +1364,11 @@ CLASS="PARAMETER" ><P ><A HREF="#DOSCHARSET" -><VAR +><TT CLASS="PARAMETER" ->dos charset</VAR +><I +>dos charset</I +></TT ></A ></P ></LI @@ -1313,9 +1376,11 @@ CLASS="PARAMETER" ><P ><A HREF="#ENCRYPTPASSWORDS" -><VAR +><TT CLASS="PARAMETER" ->encrypt passwords</VAR +><I +>encrypt passwords</I +></TT ></A ></P ></LI @@ -1323,9 +1388,11 @@ CLASS="PARAMETER" ><P ><A HREF="#ENHANCEDBROWSING" -><VAR +><TT CLASS="PARAMETER" ->enhanced browsing</VAR +><I +>enhanced browsing</I +></TT ></A ></P ></LI @@ -1333,9 +1400,11 @@ CLASS="PARAMETER" ><P ><A HREF="#ENUMPORTSCOMMAND" -><VAR +><TT CLASS="PARAMETER" ->enumports command</VAR +><I +>enumports command</I +></TT ></A ></P ></LI @@ -1343,9 +1412,11 @@ CLASS="PARAMETER" ><P ><A HREF="#GETWDCACHE" -><VAR +><TT CLASS="PARAMETER" ->getwd cache</VAR +><I +>getwd cache</I +></TT ></A ></P ></LI @@ -1353,9 +1424,11 @@ CLASS="PARAMETER" ><P ><A HREF="#HIDELOCALUSERS" -><VAR +><TT CLASS="PARAMETER" ->hide local users</VAR +><I +>hide local users</I +></TT ></A ></P ></LI @@ -1363,9 +1436,11 @@ CLASS="PARAMETER" ><P ><A HREF="#HIDEUNREADABLE" -><VAR +><TT CLASS="PARAMETER" ->hide unreadable</VAR +><I +>hide unreadable</I +></TT ></A ></P ></LI @@ -1373,9 +1448,11 @@ CLASS="PARAMETER" ><P ><A HREF="#HIDEUNWRITEABLEFILES" -><VAR +><TT CLASS="PARAMETER" ->hide unwriteable files</VAR +><I +>hide unwriteable files</I +></TT ></A ></P ></LI @@ -1383,9 +1460,11 @@ CLASS="PARAMETER" ><P ><A HREF="#HIDESPECIALFILES" -><VAR +><TT CLASS="PARAMETER" ->hide special files</VAR +><I +>hide special files</I +></TT ></A ></P ></LI @@ -1393,9 +1472,11 @@ CLASS="PARAMETER" ><P ><A HREF="#HOMEDIRMAP" -><VAR +><TT CLASS="PARAMETER" ->homedir map</VAR +><I +>homedir map</I +></TT ></A ></P ></LI @@ -1403,9 +1484,11 @@ CLASS="PARAMETER" ><P ><A HREF="#HOSTMSDFS" -><VAR +><TT CLASS="PARAMETER" ->host msdfs</VAR +><I +>host msdfs</I +></TT ></A ></P ></LI @@ -1413,9 +1496,11 @@ CLASS="PARAMETER" ><P ><A HREF="#HOSTNAMELOOKUPS" -><VAR +><TT CLASS="PARAMETER" ->hostname lookups</VAR +><I +>hostname lookups</I +></TT ></A ></P ></LI @@ -1423,9 +1508,11 @@ CLASS="PARAMETER" ><P ><A HREF="#HOSTSEQUIV" -><VAR +><TT CLASS="PARAMETER" ->hosts equiv</VAR +><I +>hosts equiv</I +></TT ></A ></P ></LI @@ -1433,9 +1520,11 @@ CLASS="PARAMETER" ><P ><A HREF="#INTERFACES" -><VAR +><TT CLASS="PARAMETER" ->interfaces</VAR +><I +>interfaces</I +></TT ></A ></P ></LI @@ -1443,9 +1532,11 @@ CLASS="PARAMETER" ><P ><A HREF="#KEEPALIVE" -><VAR +><TT CLASS="PARAMETER" ->keepalive</VAR +><I +>keepalive</I +></TT ></A ></P ></LI @@ -1453,9 +1544,11 @@ CLASS="PARAMETER" ><P ><A HREF="#KERNELOPLOCKS" -><VAR +><TT CLASS="PARAMETER" ->kernel oplocks</VAR +><I +>kernel oplocks</I +></TT ></A ></P ></LI @@ -1463,9 +1556,11 @@ CLASS="PARAMETER" ><P ><A HREF="#LANMANAUTH" -><VAR +><TT CLASS="PARAMETER" ->lanman auth</VAR +><I +>lanman auth</I +></TT ></A ></P ></LI @@ -1473,9 +1568,11 @@ CLASS="PARAMETER" ><P ><A HREF="#LARGEREADWRITE" -><VAR +><TT CLASS="PARAMETER" ->large readwrite</VAR +><I +>large readwrite</I +></TT ></A ></P ></LI @@ -1483,9 +1580,11 @@ CLASS="PARAMETER" ><P ><A HREF="#LDAPADMINDN" -><VAR +><TT CLASS="PARAMETER" ->ldap admin dn</VAR +><I +>ldap admin dn</I +></TT ></A ></P ></LI @@ -1493,9 +1592,23 @@ CLASS="PARAMETER" ><P ><A HREF="#LDAPDELETEDN" -><VAR +><TT CLASS="PARAMETER" ->ldap delete dn</VAR +><I +>ldap delete dn</I +></TT +></A +></P +></LI +><LI +><P +><A +HREF="#LDAPDELONLYSAMATTR" +><TT +CLASS="PARAMETER" +><I +>ldap del only sam attr</I +></TT ></A ></P ></LI @@ -1503,9 +1616,11 @@ CLASS="PARAMETER" ><P ><A HREF="#LDAPFILTER" -><VAR +><TT CLASS="PARAMETER" ->ldap filter</VAR +><I +>ldap filter</I +></TT ></A ></P ></LI @@ -1513,9 +1628,11 @@ CLASS="PARAMETER" ><P ><A HREF="#LDAPPORT" -><VAR +><TT CLASS="PARAMETER" ->ldap port</VAR +><I +>ldap port</I +></TT ></A ></P ></LI @@ -1523,9 +1640,11 @@ CLASS="PARAMETER" ><P ><A HREF="#LDAPSERVER" -><VAR +><TT CLASS="PARAMETER" ->ldap server</VAR +><I +>ldap server</I +></TT ></A ></P ></LI @@ -1533,9 +1652,11 @@ CLASS="PARAMETER" ><P ><A HREF="#LDAPSSL" -><VAR +><TT CLASS="PARAMETER" ->ldap ssl</VAR +><I +>ldap ssl</I +></TT ></A ></P ></LI @@ -1543,9 +1664,11 @@ CLASS="PARAMETER" ><P ><A HREF="#LDAPSUFFIX" -><VAR +><TT CLASS="PARAMETER" ->ldap suffix</VAR +><I +>ldap suffix</I +></TT ></A ></P ></LI @@ -1553,9 +1676,11 @@ CLASS="PARAMETER" ><P ><A HREF="#LDAPUSERSUFFIX" -><VAR +><TT CLASS="PARAMETER" ->ldap user suffix</VAR +><I +>ldap user suffix</I +></TT ></A ></P ></LI @@ -1563,9 +1688,11 @@ CLASS="PARAMETER" ><P ><A HREF="#LDAPMACHINESUFFIX" -><VAR +><TT CLASS="PARAMETER" ->ldap machine suffix</VAR +><I +>ldap machine suffix</I +></TT ></A ></P ></LI @@ -1573,9 +1700,11 @@ CLASS="PARAMETER" ><P ><A HREF="#LDAPPASSWDSYNC" -><VAR +><TT CLASS="PARAMETER" ->ldap passwd sync</VAR +><I +>ldap passwd sync</I +></TT ></A ></P ></LI @@ -1583,9 +1712,11 @@ CLASS="PARAMETER" ><P ><A HREF="#LDAPTRUSTIDS" -><VAR +><TT CLASS="PARAMETER" ->ldap trust ids</VAR +><I +>ldap trust ids</I +></TT ></A ></P ></LI @@ -1593,9 +1724,11 @@ CLASS="PARAMETER" ><P ><A HREF="#LMANNOUNCE" -><VAR +><TT CLASS="PARAMETER" ->lm announce</VAR +><I +>lm announce</I +></TT ></A ></P ></LI @@ -1603,9 +1736,11 @@ CLASS="PARAMETER" ><P ><A HREF="#LMINTERVAL" -><VAR +><TT CLASS="PARAMETER" ->lm interval</VAR +><I +>lm interval</I +></TT ></A ></P ></LI @@ -1613,9 +1748,11 @@ CLASS="PARAMETER" ><P ><A HREF="#LOADPRINTERS" -><VAR +><TT CLASS="PARAMETER" ->load printers</VAR +><I +>load printers</I +></TT ></A ></P ></LI @@ -1623,9 +1760,11 @@ CLASS="PARAMETER" ><P ><A HREF="#LOCALMASTER" -><VAR +><TT CLASS="PARAMETER" ->local master</VAR +><I +>local master</I +></TT ></A ></P ></LI @@ -1633,9 +1772,11 @@ CLASS="PARAMETER" ><P ><A HREF="#LOCKDIR" -><VAR +><TT CLASS="PARAMETER" ->lock dir</VAR +><I +>lock dir</I +></TT ></A ></P ></LI @@ -1643,9 +1784,11 @@ CLASS="PARAMETER" ><P ><A HREF="#LOCKDIRECTORY" -><VAR +><TT CLASS="PARAMETER" ->lock directory</VAR +><I +>lock directory</I +></TT ></A ></P ></LI @@ -1653,9 +1796,11 @@ CLASS="PARAMETER" ><P ><A HREF="#LOCKSPINCOUNT" -><VAR +><TT CLASS="PARAMETER" ->lock spin count</VAR +><I +>lock spin count</I +></TT ></A ></P ></LI @@ -1663,9 +1808,11 @@ CLASS="PARAMETER" ><P ><A HREF="#LOCKSPINTIME" -><VAR +><TT CLASS="PARAMETER" ->lock spin time</VAR +><I +>lock spin time</I +></TT ></A ></P ></LI @@ -1673,9 +1820,11 @@ CLASS="PARAMETER" ><P ><A HREF="#PIDDIRECTORY" -><VAR +><TT CLASS="PARAMETER" ->pid directory</VAR +><I +>pid directory</I +></TT ></A ></P ></LI @@ -1683,9 +1832,11 @@ CLASS="PARAMETER" ><P ><A HREF="#LOGFILE" -><VAR +><TT CLASS="PARAMETER" ->log file</VAR +><I +>log file</I +></TT ></A ></P ></LI @@ -1693,9 +1844,11 @@ CLASS="PARAMETER" ><P ><A HREF="#LOGLEVEL" -><VAR +><TT CLASS="PARAMETER" ->log level</VAR +><I +>log level</I +></TT ></A ></P ></LI @@ -1703,9 +1856,11 @@ CLASS="PARAMETER" ><P ><A HREF="#LOGONDRIVE" -><VAR +><TT CLASS="PARAMETER" ->logon drive</VAR +><I +>logon drive</I +></TT ></A ></P ></LI @@ -1713,9 +1868,11 @@ CLASS="PARAMETER" ><P ><A HREF="#LOGONHOME" -><VAR +><TT CLASS="PARAMETER" ->logon home</VAR +><I +>logon home</I +></TT ></A ></P ></LI @@ -1723,9 +1880,11 @@ CLASS="PARAMETER" ><P ><A HREF="#LOGONPATH" -><VAR +><TT CLASS="PARAMETER" ->logon path</VAR +><I +>logon path</I +></TT ></A ></P ></LI @@ -1733,9 +1892,11 @@ CLASS="PARAMETER" ><P ><A HREF="#LOGONSCRIPT" -><VAR +><TT CLASS="PARAMETER" ->logon script</VAR +><I +>logon script</I +></TT ></A ></P ></LI @@ -1743,9 +1904,11 @@ CLASS="PARAMETER" ><P ><A HREF="#LPQCACHETIME" -><VAR +><TT CLASS="PARAMETER" ->lpq cache time</VAR +><I +>lpq cache time</I +></TT ></A ></P ></LI @@ -1753,19 +1916,11 @@ CLASS="PARAMETER" ><P ><A HREF="#MACHINEPASSWORDTIMEOUT" -><VAR -CLASS="PARAMETER" ->machine password timeout</VAR -></A -></P -></LI -><LI -><P -><A -HREF="#MANGLEPREFIX" -><VAR +><TT CLASS="PARAMETER" ->mangle prefix</VAR +><I +>machine password timeout</I +></TT ></A ></P ></LI @@ -1773,9 +1928,11 @@ CLASS="PARAMETER" ><P ><A HREF="#MANGLEDSTACK" -><VAR +><TT CLASS="PARAMETER" ->mangled stack</VAR +><I +>mangled stack</I +></TT ></A ></P ></LI @@ -1783,9 +1940,11 @@ CLASS="PARAMETER" ><P ><A HREF="#MAPTOGUEST" -><VAR +><TT CLASS="PARAMETER" ->map to guest</VAR +><I +>map to guest</I +></TT ></A ></P ></LI @@ -1793,9 +1952,11 @@ CLASS="PARAMETER" ><P ><A HREF="#MAXDISKSIZE" -><VAR +><TT CLASS="PARAMETER" ->max disk size</VAR +><I +>max disk size</I +></TT ></A ></P ></LI @@ -1803,9 +1964,11 @@ CLASS="PARAMETER" ><P ><A HREF="#MAXLOGSIZE" -><VAR +><TT CLASS="PARAMETER" ->max log size</VAR +><I +>max log size</I +></TT ></A ></P ></LI @@ -1813,9 +1976,11 @@ CLASS="PARAMETER" ><P ><A HREF="#MAXMUX" -><VAR +><TT CLASS="PARAMETER" ->max mux</VAR +><I +>max mux</I +></TT ></A ></P ></LI @@ -1823,9 +1988,11 @@ CLASS="PARAMETER" ><P ><A HREF="#MAXOPENFILES" -><VAR +><TT CLASS="PARAMETER" ->max open files</VAR +><I +>max open files</I +></TT ></A ></P ></LI @@ -1833,9 +2000,11 @@ CLASS="PARAMETER" ><P ><A HREF="#MAXPROTOCOL" -><VAR +><TT CLASS="PARAMETER" ->max protocol</VAR +><I +>max protocol</I +></TT ></A ></P ></LI @@ -1843,9 +2012,11 @@ CLASS="PARAMETER" ><P ><A HREF="#MAXSMBDPROCESSES" -><VAR +><TT CLASS="PARAMETER" ->max smbd processes</VAR +><I +>max smbd processes</I +></TT ></A ></P ></LI @@ -1853,9 +2024,11 @@ CLASS="PARAMETER" ><P ><A HREF="#MAXTTL" -><VAR +><TT CLASS="PARAMETER" ->max ttl</VAR +><I +>max ttl</I +></TT ></A ></P ></LI @@ -1863,9 +2036,11 @@ CLASS="PARAMETER" ><P ><A HREF="#MAXWINSTTL" -><VAR +><TT CLASS="PARAMETER" ->max wins ttl</VAR +><I +>max wins ttl</I +></TT ></A ></P ></LI @@ -1873,9 +2048,11 @@ CLASS="PARAMETER" ><P ><A HREF="#MAXXMIT" -><VAR +><TT CLASS="PARAMETER" ->max xmit</VAR +><I +>max xmit</I +></TT ></A ></P ></LI @@ -1883,9 +2060,11 @@ CLASS="PARAMETER" ><P ><A HREF="#MESSAGECOMMAND" -><VAR +><TT CLASS="PARAMETER" ->message command</VAR +><I +>message command</I +></TT ></A ></P ></LI @@ -1893,9 +2072,11 @@ CLASS="PARAMETER" ><P ><A HREF="#MINPASSWDLENGTH" -><VAR +><TT CLASS="PARAMETER" ->min passwd length</VAR +><I +>min passwd length</I +></TT ></A ></P ></LI @@ -1903,9 +2084,11 @@ CLASS="PARAMETER" ><P ><A HREF="#MINPASSWORDLENGTH" -><VAR +><TT CLASS="PARAMETER" ->min password length</VAR +><I +>min password length</I +></TT ></A ></P ></LI @@ -1913,9 +2096,11 @@ CLASS="PARAMETER" ><P ><A HREF="#MINPROTOCOL" -><VAR +><TT CLASS="PARAMETER" ->min protocol</VAR +><I +>min protocol</I +></TT ></A ></P ></LI @@ -1923,9 +2108,11 @@ CLASS="PARAMETER" ><P ><A HREF="#MINWINSTTL" -><VAR +><TT CLASS="PARAMETER" ->min wins ttl</VAR +><I +>min wins ttl</I +></TT ></A ></P ></LI @@ -1933,9 +2120,11 @@ CLASS="PARAMETER" ><P ><A HREF="#NAMECACHETIMEOUT" -><VAR +><TT CLASS="PARAMETER" ->name cache timeout</VAR +><I +>name cache timeout</I +></TT ></A ></P ></LI @@ -1943,9 +2132,11 @@ CLASS="PARAMETER" ><P ><A HREF="#NAMERESOLVEORDER" -><VAR +><TT CLASS="PARAMETER" ->name resolve order</VAR +><I +>name resolve order</I +></TT ></A ></P ></LI @@ -1953,9 +2144,11 @@ CLASS="PARAMETER" ><P ><A HREF="#NETBIOSALIASES" -><VAR +><TT CLASS="PARAMETER" ->netbios aliases</VAR +><I +>netbios aliases</I +></TT ></A ></P ></LI @@ -1963,9 +2156,11 @@ CLASS="PARAMETER" ><P ><A HREF="#NETBIOSNAME" -><VAR +><TT CLASS="PARAMETER" ->netbios name</VAR +><I +>netbios name</I +></TT ></A ></P ></LI @@ -1973,9 +2168,11 @@ CLASS="PARAMETER" ><P ><A HREF="#NETBIOSSCOPE" -><VAR +><TT CLASS="PARAMETER" ->netbios scope</VAR +><I +>netbios scope</I +></TT ></A ></P ></LI @@ -1983,9 +2180,11 @@ CLASS="PARAMETER" ><P ><A HREF="#NISHOMEDIR" -><VAR +><TT CLASS="PARAMETER" ->nis homedir</VAR +><I +>nis homedir</I +></TT ></A ></P ></LI @@ -1993,9 +2192,11 @@ CLASS="PARAMETER" ><P ><A HREF="#NTLMAUTH" -><VAR +><TT CLASS="PARAMETER" ->ntlm auth</VAR +><I +>ntlm auth</I +></TT ></A ></P ></LI @@ -2003,9 +2204,11 @@ CLASS="PARAMETER" ><P ><A HREF="#NONUNIXACCOUNTRANGE" -><VAR +><TT CLASS="PARAMETER" ->non unix account range</VAR +><I +>non unix account range</I +></TT ></A ></P ></LI @@ -2013,9 +2216,11 @@ CLASS="PARAMETER" ><P ><A HREF="#NTPIPESUPPORT" -><VAR +><TT CLASS="PARAMETER" ->nt pipe support</VAR +><I +>nt pipe support</I +></TT ></A ></P ></LI @@ -2023,9 +2228,11 @@ CLASS="PARAMETER" ><P ><A HREF="#NTSTATUSSUPPORT" -><VAR +><TT CLASS="PARAMETER" ->nt status support</VAR +><I +>nt status support</I +></TT ></A ></P ></LI @@ -2033,9 +2240,11 @@ CLASS="PARAMETER" ><P ><A HREF="#NULLPASSWORDS" -><VAR +><TT CLASS="PARAMETER" ->null passwords</VAR +><I +>null passwords</I +></TT ></A ></P ></LI @@ -2043,9 +2252,11 @@ CLASS="PARAMETER" ><P ><A HREF="#OBEYPAMRESTRICTIONS" -><VAR +><TT CLASS="PARAMETER" ->obey pam restrictions</VAR +><I +>obey pam restrictions</I +></TT ></A ></P ></LI @@ -2053,9 +2264,11 @@ CLASS="PARAMETER" ><P ><A HREF="#OPLOCKBREAKWAITTIME" -><VAR +><TT CLASS="PARAMETER" ->oplock break wait time</VAR +><I +>oplock break wait time</I +></TT ></A ></P ></LI @@ -2063,9 +2276,11 @@ CLASS="PARAMETER" ><P ><A HREF="#OSLEVEL" -><VAR +><TT CLASS="PARAMETER" ->os level</VAR +><I +>os level</I +></TT ></A ></P ></LI @@ -2073,9 +2288,11 @@ CLASS="PARAMETER" ><P ><A HREF="#OS2DRIVERMAP" -><VAR +><TT CLASS="PARAMETER" ->os2 driver map</VAR +><I +>os2 driver map</I +></TT ></A ></P ></LI @@ -2083,9 +2300,11 @@ CLASS="PARAMETER" ><P ><A HREF="#PAMPASSWORDCHANGE" -><VAR +><TT CLASS="PARAMETER" ->pam password change</VAR +><I +>pam password change</I +></TT ></A ></P ></LI @@ -2093,9 +2312,11 @@ CLASS="PARAMETER" ><P ><A HREF="#PANICACTION" -><VAR +><TT CLASS="PARAMETER" ->panic action</VAR +><I +>panic action</I +></TT ></A ></P ></LI @@ -2103,9 +2324,11 @@ CLASS="PARAMETER" ><P ><A HREF="#PARANOIDSERVERSECURITY" -><VAR +><TT CLASS="PARAMETER" ->paranoid server security</VAR +><I +>paranoid server security</I +></TT ></A ></P ></LI @@ -2113,9 +2336,11 @@ CLASS="PARAMETER" ><P ><A HREF="#PASSDBBACKEND" -><VAR +><TT CLASS="PARAMETER" ->passdb backend</VAR +><I +>passdb backend</I +></TT ></A ></P ></LI @@ -2123,9 +2348,11 @@ CLASS="PARAMETER" ><P ><A HREF="#PASSWDCHAT" -><VAR +><TT CLASS="PARAMETER" ->passwd chat</VAR +><I +>passwd chat</I +></TT ></A ></P ></LI @@ -2133,9 +2360,11 @@ CLASS="PARAMETER" ><P ><A HREF="#PASSWDCHATDEBUG" -><VAR +><TT CLASS="PARAMETER" ->passwd chat debug</VAR +><I +>passwd chat debug</I +></TT ></A ></P ></LI @@ -2143,9 +2372,11 @@ CLASS="PARAMETER" ><P ><A HREF="#PASSWDPROGRAM" -><VAR +><TT CLASS="PARAMETER" ->passwd program</VAR +><I +>passwd program</I +></TT ></A ></P ></LI @@ -2153,9 +2384,11 @@ CLASS="PARAMETER" ><P ><A HREF="#PASSWORDLEVEL" -><VAR +><TT CLASS="PARAMETER" ->password level</VAR +><I +>password level</I +></TT ></A ></P ></LI @@ -2163,9 +2396,11 @@ CLASS="PARAMETER" ><P ><A HREF="#PASSWORDSERVER" -><VAR +><TT CLASS="PARAMETER" ->password server</VAR +><I +>password server</I +></TT ></A ></P ></LI @@ -2173,9 +2408,11 @@ CLASS="PARAMETER" ><P ><A HREF="#PREFEREDMASTER" -><VAR +><TT CLASS="PARAMETER" ->prefered master</VAR +><I +>prefered master</I +></TT ></A ></P ></LI @@ -2183,9 +2420,11 @@ CLASS="PARAMETER" ><P ><A HREF="#PREFERREDMASTER" -><VAR +><TT CLASS="PARAMETER" ->preferred master</VAR +><I +>preferred master</I +></TT ></A ></P ></LI @@ -2193,39 +2432,47 @@ CLASS="PARAMETER" ><P ><A HREF="#PRELOAD" -><VAR +><TT CLASS="PARAMETER" ->preload</VAR +><I +>preload</I +></TT ></A ></P ></LI ><LI ><P ><A -HREF="#PRELOADMODULES" -><VAR +HREF="#PRINTCAP" +><TT CLASS="PARAMETER" ->preload modules</VAR +><I +>printcap</I +></TT ></A ></P ></LI ><LI ><P ><A -HREF="#PRINTCAP" -><VAR +HREF="#PRINTCAPNAME" +><TT CLASS="PARAMETER" ->printcap</VAR +><I +>printcap name</I +></TT ></A ></P ></LI ><LI ><P ><A -HREF="#PRINTCAPNAME" -><VAR +HREF="#PRINTERDRIVERFILE" +><TT CLASS="PARAMETER" ->printcap name</VAR +><I +>printer driver file</I +></TT ></A ></P ></LI @@ -2233,9 +2480,11 @@ CLASS="PARAMETER" ><P ><A HREF="#PRIVATEDIR" -><VAR +><TT CLASS="PARAMETER" ->private dir</VAR +><I +>private dir</I +></TT ></A ></P ></LI @@ -2243,9 +2492,11 @@ CLASS="PARAMETER" ><P ><A HREF="#PROTOCOL" -><VAR +><TT CLASS="PARAMETER" ->protocol</VAR +><I +>protocol</I +></TT ></A ></P ></LI @@ -2253,9 +2504,11 @@ CLASS="PARAMETER" ><P ><A HREF="#READBMPX" -><VAR +><TT CLASS="PARAMETER" ->read bmpx</VAR +><I +>read bmpx</I +></TT ></A ></P ></LI @@ -2263,9 +2516,11 @@ CLASS="PARAMETER" ><P ><A HREF="#READRAW" -><VAR +><TT CLASS="PARAMETER" ->read raw</VAR +><I +>read raw</I +></TT ></A ></P ></LI @@ -2273,9 +2528,11 @@ CLASS="PARAMETER" ><P ><A HREF="#READSIZE" -><VAR +><TT CLASS="PARAMETER" ->read size</VAR +><I +>read size</I +></TT ></A ></P ></LI @@ -2283,9 +2540,11 @@ CLASS="PARAMETER" ><P ><A HREF="#REALM" -><VAR +><TT CLASS="PARAMETER" ->realm</VAR +><I +>realm</I +></TT ></A ></P ></LI @@ -2293,9 +2552,11 @@ CLASS="PARAMETER" ><P ><A HREF="#REMOTEANNOUNCE" -><VAR +><TT CLASS="PARAMETER" ->remote announce</VAR +><I +>remote announce</I +></TT ></A ></P ></LI @@ -2303,9 +2564,11 @@ CLASS="PARAMETER" ><P ><A HREF="#REMOTEBROWSESYNC" -><VAR +><TT CLASS="PARAMETER" ->remote browse sync</VAR +><I +>remote browse sync</I +></TT ></A ></P ></LI @@ -2313,9 +2576,11 @@ CLASS="PARAMETER" ><P ><A HREF="#RESTRICTANONYMOUS" -><VAR +><TT CLASS="PARAMETER" ->restrict anonymous</VAR +><I +>restrict anonymous</I +></TT ></A ></P ></LI @@ -2323,9 +2588,11 @@ CLASS="PARAMETER" ><P ><A HREF="#ROOT" -><VAR +><TT CLASS="PARAMETER" ->root</VAR +><I +>root</I +></TT ></A ></P ></LI @@ -2333,9 +2600,11 @@ CLASS="PARAMETER" ><P ><A HREF="#ROOTDIR" -><VAR +><TT CLASS="PARAMETER" ->root dir</VAR +><I +>root dir</I +></TT ></A ></P ></LI @@ -2343,9 +2612,11 @@ CLASS="PARAMETER" ><P ><A HREF="#ROOTDIRECTORY" -><VAR +><TT CLASS="PARAMETER" ->root directory</VAR +><I +>root directory</I +></TT ></A ></P ></LI @@ -2353,19 +2624,11 @@ CLASS="PARAMETER" ><P ><A HREF="#SECURITY" -><VAR -CLASS="PARAMETER" ->security</VAR -></A -></P -></LI -><LI -><P -><A -HREF="#SERVERSCHANNEL" -><VAR +><TT CLASS="PARAMETER" ->server schannel</VAR +><I +>security</I +></TT ></A ></P ></LI @@ -2373,19 +2636,11 @@ CLASS="PARAMETER" ><P ><A HREF="#SERVERSTRING" -><VAR -CLASS="PARAMETER" ->server string</VAR -></A -></P -></LI -><LI -><P -><A -HREF="#SETPRIMARYGROUPSCRIPT" -><VAR +><TT CLASS="PARAMETER" ->set primary group script</VAR +><I +>server string</I +></TT ></A ></P ></LI @@ -2393,9 +2648,11 @@ CLASS="PARAMETER" ><P ><A HREF="#SHOWADDPRINTERWIZARD" -><VAR +><TT CLASS="PARAMETER" ->show add printer wizard</VAR +><I +>show add printer wizard</I +></TT ></A ></P ></LI @@ -2403,9 +2660,11 @@ CLASS="PARAMETER" ><P ><A HREF="#SHUTDOWNSCRIPT" -><VAR +><TT CLASS="PARAMETER" ->shutdown script</VAR +><I +>shutdown script</I +></TT ></A ></P ></LI @@ -2413,9 +2672,11 @@ CLASS="PARAMETER" ><P ><A HREF="#SMBPASSWDFILE" -><VAR +><TT CLASS="PARAMETER" ->smb passwd file</VAR +><I +>smb passwd file</I +></TT ></A ></P ></LI @@ -2423,9 +2684,11 @@ CLASS="PARAMETER" ><P ><A HREF="#SMBPORTS" -><VAR +><TT CLASS="PARAMETER" ->smb ports</VAR +><I +>smb ports</I +></TT ></A ></P ></LI @@ -2433,9 +2696,11 @@ CLASS="PARAMETER" ><P ><A HREF="#SOCKETADDRESS" -><VAR +><TT CLASS="PARAMETER" ->socket address</VAR +><I +>socket address</I +></TT ></A ></P ></LI @@ -2443,9 +2708,11 @@ CLASS="PARAMETER" ><P ><A HREF="#SOCKETOPTIONS" -><VAR +><TT CLASS="PARAMETER" ->socket options</VAR +><I +>socket options</I +></TT ></A ></P ></LI @@ -2453,9 +2720,11 @@ CLASS="PARAMETER" ><P ><A HREF="#SOURCEENVIRONMENT" -><VAR +><TT CLASS="PARAMETER" ->source environment</VAR +><I +>source environment</I +></TT ></A ></P ></LI @@ -2463,9 +2732,11 @@ CLASS="PARAMETER" ><P ><A HREF="#SPNEGO" -><VAR +><TT CLASS="PARAMETER" ->use spnego</VAR +><I +>use spnego</I +></TT ></A ></P ></LI @@ -2473,9 +2744,11 @@ CLASS="PARAMETER" ><P ><A HREF="#STATCACHE" -><VAR +><TT CLASS="PARAMETER" ->stat cache</VAR +><I +>stat cache</I +></TT ></A ></P ></LI @@ -2483,9 +2756,11 @@ CLASS="PARAMETER" ><P ><A HREF="#STATCACHESIZE" -><VAR +><TT CLASS="PARAMETER" ->stat cache size</VAR +><I +>stat cache size</I +></TT ></A ></P ></LI @@ -2493,9 +2768,11 @@ CLASS="PARAMETER" ><P ><A HREF="#STRIPDOT" -><VAR +><TT CLASS="PARAMETER" ->strip dot</VAR +><I +>strip dot</I +></TT ></A ></P ></LI @@ -2503,9 +2780,11 @@ CLASS="PARAMETER" ><P ><A HREF="#SYSLOG" -><VAR +><TT CLASS="PARAMETER" ->syslog</VAR +><I +>syslog</I +></TT ></A ></P ></LI @@ -2513,9 +2792,11 @@ CLASS="PARAMETER" ><P ><A HREF="#SYSLOGONLY" -><VAR +><TT CLASS="PARAMETER" ->syslog only</VAR +><I +>syslog only</I +></TT ></A ></P ></LI @@ -2523,9 +2804,11 @@ CLASS="PARAMETER" ><P ><A HREF="#TEMPLATEHOMEDIR" -><VAR +><TT CLASS="PARAMETER" ->template homedir</VAR +><I +>template homedir</I +></TT ></A ></P ></LI @@ -2533,9 +2816,11 @@ CLASS="PARAMETER" ><P ><A HREF="#TEMPLATESHELL" -><VAR +><TT CLASS="PARAMETER" ->template shell</VAR +><I +>template shell</I +></TT ></A ></P ></LI @@ -2543,9 +2828,11 @@ CLASS="PARAMETER" ><P ><A HREF="#TIMEOFFSET" -><VAR +><TT CLASS="PARAMETER" ->time offset</VAR +><I +>time offset</I +></TT ></A ></P ></LI @@ -2553,9 +2840,11 @@ CLASS="PARAMETER" ><P ><A HREF="#TIMESERVER" -><VAR +><TT CLASS="PARAMETER" ->time server</VAR +><I +>time server</I +></TT ></A ></P ></LI @@ -2563,9 +2852,11 @@ CLASS="PARAMETER" ><P ><A HREF="#TIMESTAMPLOGS" -><VAR +><TT CLASS="PARAMETER" ->timestamp logs</VAR +><I +>timestamp logs</I +></TT ></A ></P ></LI @@ -2573,9 +2864,11 @@ CLASS="PARAMETER" ><P ><A HREF="#TOTALPRINTJOBS" -><VAR +><TT CLASS="PARAMETER" ->total print jobs</VAR +><I +>total print jobs</I +></TT ></A ></P ></LI @@ -2583,9 +2876,11 @@ CLASS="PARAMETER" ><P ><A HREF="#UNICODE" -><VAR +><TT CLASS="PARAMETER" ->unicode</VAR +><I +>unicode</I +></TT ></A ></P ></LI @@ -2593,9 +2888,11 @@ CLASS="PARAMETER" ><P ><A HREF="#UNIXCHARSET" -><VAR +><TT CLASS="PARAMETER" ->unix charset</VAR +><I +>unix charset</I +></TT ></A ></P ></LI @@ -2603,9 +2900,11 @@ CLASS="PARAMETER" ><P ><A HREF="#UNIXEXTENSIONS" -><VAR +><TT CLASS="PARAMETER" ->unix extensions</VAR +><I +>unix extensions</I +></TT ></A ></P ></LI @@ -2613,9 +2912,11 @@ CLASS="PARAMETER" ><P ><A HREF="#UNIXPASSWORDSYNC" -><VAR +><TT CLASS="PARAMETER" ->unix password sync</VAR +><I +>unix password sync</I +></TT ></A ></P ></LI @@ -2623,9 +2924,11 @@ CLASS="PARAMETER" ><P ><A HREF="#UPDATEENCRYPTED" -><VAR +><TT CLASS="PARAMETER" ->update encrypted</VAR +><I +>update encrypted</I +></TT ></A ></P ></LI @@ -2633,9 +2936,23 @@ CLASS="PARAMETER" ><P ><A HREF="#USEMMAP" -><VAR +><TT CLASS="PARAMETER" ->use mmap</VAR +><I +>use mmap</I +></TT +></A +></P +></LI +><LI +><P +><A +HREF="#USERHOSTS" +><TT +CLASS="PARAMETER" +><I +>use rhosts</I +></TT ></A ></P ></LI @@ -2643,9 +2960,11 @@ CLASS="PARAMETER" ><P ><A HREF="#USESENDFILE" -><VAR +><TT CLASS="PARAMETER" ->use sendfile</VAR +><I +>use sendfile</I +></TT ></A ></P ></LI @@ -2653,9 +2972,11 @@ CLASS="PARAMETER" ><P ><A HREF="#USERNAMELEVEL" -><VAR +><TT CLASS="PARAMETER" ->username level</VAR +><I +>username level</I +></TT ></A ></P ></LI @@ -2663,9 +2984,11 @@ CLASS="PARAMETER" ><P ><A HREF="#USERNAMEMAP" -><VAR +><TT CLASS="PARAMETER" ->username map</VAR +><I +>username map</I +></TT ></A ></P ></LI @@ -2673,9 +2996,11 @@ CLASS="PARAMETER" ><P ><A HREF="#UTMP" -><VAR +><TT CLASS="PARAMETER" ->utmp</VAR +><I +>utmp</I +></TT ></A ></P ></LI @@ -2683,9 +3008,11 @@ CLASS="PARAMETER" ><P ><A HREF="#UTMPDIRECTORY" -><VAR +><TT CLASS="PARAMETER" ->utmp directory</VAR +><I +>utmp directory</I +></TT ></A ></P ></LI @@ -2693,9 +3020,11 @@ CLASS="PARAMETER" ><P ><A HREF="#WTMPDIRECTORY" -><VAR +><TT CLASS="PARAMETER" ->wtmp directory</VAR +><I +>wtmp directory</I +></TT ></A ></P ></LI @@ -2703,9 +3032,11 @@ CLASS="PARAMETER" ><P ><A HREF="#WINBINDCACHETIME" -><VAR +><TT CLASS="PARAMETER" ->winbind cache time</VAR +><I +>winbind cache time</I +></TT ></A ></P ></LI @@ -2713,9 +3044,11 @@ CLASS="PARAMETER" ><P ><A HREF="#WINBINDENUMUSERS" -><VAR +><TT CLASS="PARAMETER" ->winbind enum users</VAR +><I +>winbind enum users</I +></TT ></A ></P ></LI @@ -2723,9 +3056,11 @@ CLASS="PARAMETER" ><P ><A HREF="#WINBINDENUMGROUPS" -><VAR +><TT CLASS="PARAMETER" ->winbind enum groups</VAR +><I +>winbind enum groups</I +></TT ></A ></P ></LI @@ -2733,9 +3068,11 @@ CLASS="PARAMETER" ><P ><A HREF="#WINBINDGID" -><VAR +><TT CLASS="PARAMETER" ->winbind gid</VAR +><I +>winbind gid</I +></TT ></A ></P ></LI @@ -2743,9 +3080,11 @@ CLASS="PARAMETER" ><P ><A HREF="#WINBINDSEPARATOR" -><VAR +><TT CLASS="PARAMETER" ->winbind separator</VAR +><I +>winbind separator</I +></TT ></A ></P ></LI @@ -2753,9 +3092,11 @@ CLASS="PARAMETER" ><P ><A HREF="#WINBINDUID" -><VAR +><TT CLASS="PARAMETER" ->winbind uid</VAR +><I +>winbind uid</I +></TT ></A ></P ></LI @@ -2763,9 +3104,11 @@ CLASS="PARAMETER" ><P ><A HREF="#WINBINDUSEDEFAULTDOMAIN" -><VAR +><TT CLASS="PARAMETER" ->winbind use default domain</VAR +><I +>winbind use default domain</I +></TT ></A ></P ></LI @@ -2773,9 +3116,11 @@ CLASS="PARAMETER" ><P ><A HREF="#WINSHOOK" -><VAR +><TT CLASS="PARAMETER" ->wins hook</VAR +><I +>wins hook</I +></TT ></A ></P ></LI @@ -2783,9 +3128,11 @@ CLASS="PARAMETER" ><P ><A HREF="#WINSPARTNERS" -><VAR +><TT CLASS="PARAMETER" ->wins partners</VAR +><I +>wins partners</I +></TT ></A ></P ></LI @@ -2793,9 +3140,11 @@ CLASS="PARAMETER" ><P ><A HREF="#WINSPROXY" -><VAR +><TT CLASS="PARAMETER" ->wins proxy</VAR +><I +>wins proxy</I +></TT ></A ></P ></LI @@ -2803,9 +3152,11 @@ CLASS="PARAMETER" ><P ><A HREF="#WINSSERVER" -><VAR +><TT CLASS="PARAMETER" ->wins server</VAR +><I +>wins server</I +></TT ></A ></P ></LI @@ -2813,9 +3164,11 @@ CLASS="PARAMETER" ><P ><A HREF="#WINSSUPPORT" -><VAR +><TT CLASS="PARAMETER" ->wins support</VAR +><I +>wins support</I +></TT ></A ></P ></LI @@ -2823,9 +3176,11 @@ CLASS="PARAMETER" ><P ><A HREF="#WORKGROUP" -><VAR +><TT CLASS="PARAMETER" ->workgroup</VAR +><I +>workgroup</I +></TT ></A ></P ></LI @@ -2833,9 +3188,11 @@ CLASS="PARAMETER" ><P ><A HREF="#WRITERAW" -><VAR +><TT CLASS="PARAMETER" ->write raw</VAR +><I +>write raw</I +></TT ></A ></P ></LI @@ -2844,7 +3201,7 @@ CLASS="PARAMETER" ><DIV CLASS="REFSECT1" ><A -NAME="AEN1035" +NAME="AEN1029" ></A ><H2 >COMPLETE LIST OF SERVICE PARAMETERS</H2 @@ -2858,9 +3215,11 @@ NAME="AEN1035" ><P ><A HREF="#ADMINUSERS" -><VAR +><TT CLASS="PARAMETER" ->admin users</VAR +><I +>admin users</I +></TT ></A ></P ></LI @@ -2868,9 +3227,11 @@ CLASS="PARAMETER" ><P ><A HREF="#ALLOWHOSTS" -><VAR +><TT CLASS="PARAMETER" ->allow hosts</VAR +><I +>allow hosts</I +></TT ></A ></P ></LI @@ -2878,9 +3239,11 @@ CLASS="PARAMETER" ><P ><A HREF="#AVAILABLE" -><VAR +><TT CLASS="PARAMETER" ->available</VAR +><I +>available</I +></TT ></A ></P ></LI @@ -2888,9 +3251,11 @@ CLASS="PARAMETER" ><P ><A HREF="#BLOCKINGLOCKS" -><VAR +><TT CLASS="PARAMETER" ->blocking locks</VAR +><I +>blocking locks</I +></TT ></A ></P ></LI @@ -2898,9 +3263,11 @@ CLASS="PARAMETER" ><P ><A HREF="#BLOCKSIZE" -><VAR +><TT CLASS="PARAMETER" ->block size</VAR +><I +>block size</I +></TT ></A ></P ></LI @@ -2908,9 +3275,11 @@ CLASS="PARAMETER" ><P ><A HREF="#BROWSABLE" -><VAR +><TT CLASS="PARAMETER" ->browsable</VAR +><I +>browsable</I +></TT ></A ></P ></LI @@ -2918,9 +3287,11 @@ CLASS="PARAMETER" ><P ><A HREF="#BROWSEABLE" -><VAR +><TT CLASS="PARAMETER" ->browseable</VAR +><I +>browseable</I +></TT ></A ></P ></LI @@ -2928,9 +3299,11 @@ CLASS="PARAMETER" ><P ><A HREF="#CASESENSITIVE" -><VAR +><TT CLASS="PARAMETER" ->case sensitive</VAR +><I +>case sensitive</I +></TT ></A ></P ></LI @@ -2938,9 +3311,11 @@ CLASS="PARAMETER" ><P ><A HREF="#CASESIGNAMES" -><VAR +><TT CLASS="PARAMETER" ->casesignames</VAR +><I +>casesignames</I +></TT ></A ></P ></LI @@ -2948,9 +3323,11 @@ CLASS="PARAMETER" ><P ><A HREF="#COMMENT" -><VAR +><TT CLASS="PARAMETER" ->comment</VAR +><I +>comment</I +></TT ></A ></P ></LI @@ -2958,9 +3335,11 @@ CLASS="PARAMETER" ><P ><A HREF="#COPY" -><VAR +><TT CLASS="PARAMETER" ->copy</VAR +><I +>copy</I +></TT ></A ></P ></LI @@ -2968,9 +3347,11 @@ CLASS="PARAMETER" ><P ><A HREF="#CREATEMASK" -><VAR +><TT CLASS="PARAMETER" ->create mask</VAR +><I +>create mask</I +></TT ></A ></P ></LI @@ -2978,9 +3359,11 @@ CLASS="PARAMETER" ><P ><A HREF="#CREATEMODE" -><VAR +><TT CLASS="PARAMETER" ->create mode</VAR +><I +>create mode</I +></TT ></A ></P ></LI @@ -2988,9 +3371,11 @@ CLASS="PARAMETER" ><P ><A HREF="#CSCPOLICY" -><VAR +><TT CLASS="PARAMETER" ->csc policy</VAR +><I +>csc policy</I +></TT ></A ></P ></LI @@ -2998,9 +3383,11 @@ CLASS="PARAMETER" ><P ><A HREF="#DEFAULTCASE" -><VAR +><TT CLASS="PARAMETER" ->default case</VAR +><I +>default case</I +></TT ></A ></P ></LI @@ -3008,9 +3395,11 @@ CLASS="PARAMETER" ><P ><A HREF="#DEFAULTDEVMODE" -><VAR +><TT CLASS="PARAMETER" ->default devmode</VAR +><I +>default devmode</I +></TT ></A ></P ></LI @@ -3018,9 +3407,11 @@ CLASS="PARAMETER" ><P ><A HREF="#DELETEREADONLY" -><VAR +><TT CLASS="PARAMETER" ->delete readonly</VAR +><I +>delete readonly</I +></TT ></A ></P ></LI @@ -3028,9 +3419,11 @@ CLASS="PARAMETER" ><P ><A HREF="#DELETEVETOFILES" -><VAR +><TT CLASS="PARAMETER" ->delete veto files</VAR +><I +>delete veto files</I +></TT ></A ></P ></LI @@ -3038,9 +3431,11 @@ CLASS="PARAMETER" ><P ><A HREF="#DENYHOSTS" -><VAR +><TT CLASS="PARAMETER" ->deny hosts</VAR +><I +>deny hosts</I +></TT ></A ></P ></LI @@ -3048,9 +3443,11 @@ CLASS="PARAMETER" ><P ><A HREF="#DIRECTORY" -><VAR +><TT CLASS="PARAMETER" ->directory</VAR +><I +>directory</I +></TT ></A ></P ></LI @@ -3058,9 +3455,11 @@ CLASS="PARAMETER" ><P ><A HREF="#DIRECTORYMASK" -><VAR +><TT CLASS="PARAMETER" ->directory mask</VAR +><I +>directory mask</I +></TT ></A ></P ></LI @@ -3068,9 +3467,11 @@ CLASS="PARAMETER" ><P ><A HREF="#DIRECTORYMODE" -><VAR +><TT CLASS="PARAMETER" ->directory mode</VAR +><I +>directory mode</I +></TT ></A ></P ></LI @@ -3078,9 +3479,11 @@ CLASS="PARAMETER" ><P ><A HREF="#DIRECTORYSECURITYMASK" -><VAR +><TT CLASS="PARAMETER" ->directory security mask</VAR +><I +>directory security mask</I +></TT ></A ></P ></LI @@ -3088,9 +3491,11 @@ CLASS="PARAMETER" ><P ><A HREF="#DONTDESCEND" -><VAR +><TT CLASS="PARAMETER" ->dont descend</VAR +><I +>dont descend</I +></TT ></A ></P ></LI @@ -3098,9 +3503,11 @@ CLASS="PARAMETER" ><P ><A HREF="#DOSFILEMODE" -><VAR +><TT CLASS="PARAMETER" ->dos filemode</VAR +><I +>dos filemode</I +></TT ></A ></P ></LI @@ -3108,9 +3515,11 @@ CLASS="PARAMETER" ><P ><A HREF="#DOSFILETIMERESOLUTION" -><VAR +><TT CLASS="PARAMETER" ->dos filetime resolution</VAR +><I +>dos filetime resolution</I +></TT ></A ></P ></LI @@ -3118,9 +3527,11 @@ CLASS="PARAMETER" ><P ><A HREF="#DOSFILETIMES" -><VAR +><TT CLASS="PARAMETER" ->dos filetimes</VAR +><I +>dos filetimes</I +></TT ></A ></P ></LI @@ -3128,9 +3539,11 @@ CLASS="PARAMETER" ><P ><A HREF="#EXEC" -><VAR +><TT CLASS="PARAMETER" ->exec</VAR +><I +>exec</I +></TT ></A ></P ></LI @@ -3138,9 +3551,11 @@ CLASS="PARAMETER" ><P ><A HREF="#FAKEDIRECTORYCREATETIMES" -><VAR +><TT CLASS="PARAMETER" ->fake directory create times</VAR +><I +>fake directory create times</I +></TT ></A ></P ></LI @@ -3148,9 +3563,11 @@ CLASS="PARAMETER" ><P ><A HREF="#FAKEOPLOCKS" -><VAR +><TT CLASS="PARAMETER" ->fake oplocks</VAR +><I +>fake oplocks</I +></TT ></A ></P ></LI @@ -3158,9 +3575,11 @@ CLASS="PARAMETER" ><P ><A HREF="#FOLLOWSYMLINKS" -><VAR +><TT CLASS="PARAMETER" ->follow symlinks</VAR +><I +>follow symlinks</I +></TT ></A ></P ></LI @@ -3168,9 +3587,11 @@ CLASS="PARAMETER" ><P ><A HREF="#FORCECREATEMODE" -><VAR +><TT CLASS="PARAMETER" ->force create mode</VAR +><I +>force create mode</I +></TT ></A ></P ></LI @@ -3178,9 +3599,11 @@ CLASS="PARAMETER" ><P ><A HREF="#FORCEDIRECTORYMODE" -><VAR +><TT CLASS="PARAMETER" ->force directory mode</VAR +><I +>force directory mode</I +></TT ></A ></P ></LI @@ -3188,9 +3611,11 @@ CLASS="PARAMETER" ><P ><A HREF="#FORCEDIRECTORYSECURITYMODE" -><VAR +><TT CLASS="PARAMETER" ->force directory security mode</VAR +><I +>force directory security mode</I +></TT ></A ></P ></LI @@ -3198,9 +3623,11 @@ CLASS="PARAMETER" ><P ><A HREF="#FORCEGROUP" -><VAR +><TT CLASS="PARAMETER" ->force group</VAR +><I +>force group</I +></TT ></A ></P ></LI @@ -3208,9 +3635,11 @@ CLASS="PARAMETER" ><P ><A HREF="#FORCESECURITYMODE" -><VAR +><TT CLASS="PARAMETER" ->force security mode</VAR +><I +>force security mode</I +></TT ></A ></P ></LI @@ -3218,9 +3647,11 @@ CLASS="PARAMETER" ><P ><A HREF="#FORCEUSER" -><VAR +><TT CLASS="PARAMETER" ->force user</VAR +><I +>force user</I +></TT ></A ></P ></LI @@ -3228,9 +3659,11 @@ CLASS="PARAMETER" ><P ><A HREF="#FSTYPE" -><VAR +><TT CLASS="PARAMETER" ->fstype</VAR +><I +>fstype</I +></TT ></A ></P ></LI @@ -3238,9 +3671,11 @@ CLASS="PARAMETER" ><P ><A HREF="#GROUP" -><VAR +><TT CLASS="PARAMETER" ->group</VAR +><I +>group</I +></TT ></A ></P ></LI @@ -3248,9 +3683,11 @@ CLASS="PARAMETER" ><P ><A HREF="#GUESTACCOUNT" -><VAR +><TT CLASS="PARAMETER" ->guest account</VAR +><I +>guest account</I +></TT ></A ></P ></LI @@ -3258,9 +3695,11 @@ CLASS="PARAMETER" ><P ><A HREF="#GUESTOK" -><VAR +><TT CLASS="PARAMETER" ->guest ok</VAR +><I +>guest ok</I +></TT ></A ></P ></LI @@ -3268,9 +3707,11 @@ CLASS="PARAMETER" ><P ><A HREF="#GUESTONLY" -><VAR +><TT CLASS="PARAMETER" ->guest only</VAR +><I +>guest only</I +></TT ></A ></P ></LI @@ -3278,9 +3719,11 @@ CLASS="PARAMETER" ><P ><A HREF="#HIDEDOTFILES" -><VAR +><TT CLASS="PARAMETER" ->hide dot files</VAR +><I +>hide dot files</I +></TT ></A ></P ></LI @@ -3288,9 +3731,11 @@ CLASS="PARAMETER" ><P ><A HREF="#HIDEFILES" -><VAR +><TT CLASS="PARAMETER" ->hide files</VAR +><I +>hide files</I +></TT ></A ></P ></LI @@ -3298,9 +3743,11 @@ CLASS="PARAMETER" ><P ><A HREF="#HOSTSALLOW" -><VAR +><TT CLASS="PARAMETER" ->hosts allow</VAR +><I +>hosts allow</I +></TT ></A ></P ></LI @@ -3308,9 +3755,11 @@ CLASS="PARAMETER" ><P ><A HREF="#HOSTSDENY" -><VAR +><TT CLASS="PARAMETER" ->hosts deny</VAR +><I +>hosts deny</I +></TT ></A ></P ></LI @@ -3318,9 +3767,11 @@ CLASS="PARAMETER" ><P ><A HREF="#INCLUDE" -><VAR +><TT CLASS="PARAMETER" ->include</VAR +><I +>include</I +></TT ></A ></P ></LI @@ -3328,9 +3779,11 @@ CLASS="PARAMETER" ><P ><A HREF="#INHERITACLS" -><VAR +><TT CLASS="PARAMETER" ->inherit acls</VAR +><I +>inherit acls</I +></TT ></A ></P ></LI @@ -3338,9 +3791,11 @@ CLASS="PARAMETER" ><P ><A HREF="#INHERITPERMISSIONS" -><VAR +><TT CLASS="PARAMETER" ->inherit permissions</VAR +><I +>inherit permissions</I +></TT ></A ></P ></LI @@ -3348,9 +3803,11 @@ CLASS="PARAMETER" ><P ><A HREF="#INVALIDUSERS" -><VAR +><TT CLASS="PARAMETER" ->invalid users</VAR +><I +>invalid users</I +></TT ></A ></P ></LI @@ -3358,9 +3815,11 @@ CLASS="PARAMETER" ><P ><A HREF="#LEVEL2OPLOCKS" -><VAR +><TT CLASS="PARAMETER" ->level2 oplocks</VAR +><I +>level2 oplocks</I +></TT ></A ></P ></LI @@ -3368,9 +3827,11 @@ CLASS="PARAMETER" ><P ><A HREF="#LOCKING" -><VAR +><TT CLASS="PARAMETER" ->locking</VAR +><I +>locking</I +></TT ></A ></P ></LI @@ -3378,9 +3839,11 @@ CLASS="PARAMETER" ><P ><A HREF="#LPPAUSECOMMAND" -><VAR +><TT CLASS="PARAMETER" ->lppause command</VAR +><I +>lppause command</I +></TT ></A ></P ></LI @@ -3388,9 +3851,11 @@ CLASS="PARAMETER" ><P ><A HREF="#LPQCOMMAND" -><VAR +><TT CLASS="PARAMETER" ->lpq command</VAR +><I +>lpq command</I +></TT ></A ></P ></LI @@ -3398,9 +3863,11 @@ CLASS="PARAMETER" ><P ><A HREF="#LPRESUMECOMMAND" -><VAR +><TT CLASS="PARAMETER" ->lpresume command</VAR +><I +>lpresume command</I +></TT ></A ></P ></LI @@ -3408,9 +3875,11 @@ CLASS="PARAMETER" ><P ><A HREF="#LPRMCOMMAND" -><VAR +><TT CLASS="PARAMETER" ->lprm command</VAR +><I +>lprm command</I +></TT ></A ></P ></LI @@ -3418,9 +3887,11 @@ CLASS="PARAMETER" ><P ><A HREF="#MAGICOUTPUT" -><VAR +><TT CLASS="PARAMETER" ->magic output</VAR +><I +>magic output</I +></TT ></A ></P ></LI @@ -3428,9 +3899,11 @@ CLASS="PARAMETER" ><P ><A HREF="#MAGICSCRIPT" -><VAR +><TT CLASS="PARAMETER" ->magic script</VAR +><I +>magic script</I +></TT ></A ></P ></LI @@ -3438,9 +3911,11 @@ CLASS="PARAMETER" ><P ><A HREF="#MANGLECASE" -><VAR +><TT CLASS="PARAMETER" ->mangle case</VAR +><I +>mangle case</I +></TT ></A ></P ></LI @@ -3448,9 +3923,11 @@ CLASS="PARAMETER" ><P ><A HREF="#MANGLEDMAP" -><VAR +><TT CLASS="PARAMETER" ->mangled map</VAR +><I +>mangled map</I +></TT ></A ></P ></LI @@ -3458,9 +3935,11 @@ CLASS="PARAMETER" ><P ><A HREF="#MANGLEDNAMES" -><VAR +><TT CLASS="PARAMETER" ->mangled names</VAR +><I +>mangled names</I +></TT ></A ></P ></LI @@ -3468,9 +3947,11 @@ CLASS="PARAMETER" ><P ><A HREF="#MANGLINGCHAR" -><VAR +><TT CLASS="PARAMETER" ->mangling char</VAR +><I +>mangling char</I +></TT ></A ></P ></LI @@ -3478,9 +3959,11 @@ CLASS="PARAMETER" ><P ><A HREF="#MANGLINGMETHOD" -><VAR +><TT CLASS="PARAMETER" ->mangling method</VAR +><I +>mangling method</I +></TT ></A ></P ></LI @@ -3488,9 +3971,11 @@ CLASS="PARAMETER" ><P ><A HREF="#MAPARCHIVE" -><VAR +><TT CLASS="PARAMETER" ->map archive</VAR +><I +>map archive</I +></TT ></A ></P ></LI @@ -3498,9 +3983,11 @@ CLASS="PARAMETER" ><P ><A HREF="#MAPHIDDEN" -><VAR +><TT CLASS="PARAMETER" ->map hidden</VAR +><I +>map hidden</I +></TT ></A ></P ></LI @@ -3508,9 +3995,11 @@ CLASS="PARAMETER" ><P ><A HREF="#MAPSYSTEM" -><VAR +><TT CLASS="PARAMETER" ->map system</VAR +><I +>map system</I +></TT ></A ></P ></LI @@ -3518,9 +4007,11 @@ CLASS="PARAMETER" ><P ><A HREF="#MAXCONNECTIONS" -><VAR +><TT CLASS="PARAMETER" ->max connections</VAR +><I +>max connections</I +></TT ></A ></P ></LI @@ -3528,9 +4019,11 @@ CLASS="PARAMETER" ><P ><A HREF="#MAXPRINTJOBS" -><VAR +><TT CLASS="PARAMETER" ->max print jobs</VAR +><I +>max print jobs</I +></TT ></A ></P ></LI @@ -3538,9 +4031,11 @@ CLASS="PARAMETER" ><P ><A HREF="#MINPRINTSPACE" -><VAR +><TT CLASS="PARAMETER" ->min print space</VAR +><I +>min print space</I +></TT ></A ></P ></LI @@ -3548,9 +4043,11 @@ CLASS="PARAMETER" ><P ><A HREF="#MSDFSPROXY" -><VAR +><TT CLASS="PARAMETER" ->msdfs proxy</VAR +><I +>msdfs proxy</I +></TT ></A ></P ></LI @@ -3558,9 +4055,11 @@ CLASS="PARAMETER" ><P ><A HREF="#MSDFSROOT" -><VAR +><TT CLASS="PARAMETER" ->msdfs root</VAR +><I +>msdfs root</I +></TT ></A ></P ></LI @@ -3568,9 +4067,11 @@ CLASS="PARAMETER" ><P ><A HREF="#NTACLSUPPORT" -><VAR +><TT CLASS="PARAMETER" ->nt acl support</VAR +><I +>nt acl support</I +></TT ></A ></P ></LI @@ -3578,9 +4079,11 @@ CLASS="PARAMETER" ><P ><A HREF="#ONLYGUEST" -><VAR +><TT CLASS="PARAMETER" ->only guest</VAR +><I +>only guest</I +></TT ></A ></P ></LI @@ -3588,9 +4091,11 @@ CLASS="PARAMETER" ><P ><A HREF="#ONLYUSER" -><VAR +><TT CLASS="PARAMETER" ->only user</VAR +><I +>only user</I +></TT ></A ></P ></LI @@ -3598,9 +4103,11 @@ CLASS="PARAMETER" ><P ><A HREF="#OPLOCKCONTENTIONLIMIT" -><VAR +><TT CLASS="PARAMETER" ->oplock contention limit</VAR +><I +>oplock contention limit</I +></TT ></A ></P ></LI @@ -3608,9 +4115,11 @@ CLASS="PARAMETER" ><P ><A HREF="#OPLOCKS" -><VAR +><TT CLASS="PARAMETER" ->oplocks</VAR +><I +>oplocks</I +></TT ></A ></P ></LI @@ -3618,9 +4127,11 @@ CLASS="PARAMETER" ><P ><A HREF="#PATH" -><VAR +><TT CLASS="PARAMETER" ->path</VAR +><I +>path</I +></TT ></A ></P ></LI @@ -3628,9 +4139,11 @@ CLASS="PARAMETER" ><P ><A HREF="#POSIXLOCKING" -><VAR +><TT CLASS="PARAMETER" ->posix locking</VAR +><I +>posix locking</I +></TT ></A ></P ></LI @@ -3638,9 +4151,23 @@ CLASS="PARAMETER" ><P ><A HREF="#POSTEXEC" -><VAR +><TT +CLASS="PARAMETER" +><I +>postexec</I +></TT +></A +></P +></LI +><LI +><P +><A +HREF="#POSTSCRIPT" +><TT CLASS="PARAMETER" ->postexec</VAR +><I +>postscript</I +></TT ></A ></P ></LI @@ -3648,9 +4175,11 @@ CLASS="PARAMETER" ><P ><A HREF="#PREEXEC" -><VAR +><TT CLASS="PARAMETER" ->preexec</VAR +><I +>preexec</I +></TT ></A ></P ></LI @@ -3658,9 +4187,11 @@ CLASS="PARAMETER" ><P ><A HREF="#PREEXECCLOSE" -><VAR +><TT CLASS="PARAMETER" ->preexec close</VAR +><I +>preexec close</I +></TT ></A ></P ></LI @@ -3668,9 +4199,11 @@ CLASS="PARAMETER" ><P ><A HREF="#PRESERVECASE" -><VAR +><TT CLASS="PARAMETER" ->preserve case</VAR +><I +>preserve case</I +></TT ></A ></P ></LI @@ -3678,9 +4211,11 @@ CLASS="PARAMETER" ><P ><A HREF="#PRINTCOMMAND" -><VAR +><TT CLASS="PARAMETER" ->print command</VAR +><I +>print command</I +></TT ></A ></P ></LI @@ -3688,9 +4223,11 @@ CLASS="PARAMETER" ><P ><A HREF="#PRINTOK" -><VAR +><TT CLASS="PARAMETER" ->print ok</VAR +><I +>print ok</I +></TT ></A ></P ></LI @@ -3698,9 +4235,11 @@ CLASS="PARAMETER" ><P ><A HREF="#PRINTABLE" -><VAR +><TT CLASS="PARAMETER" ->printable</VAR +><I +>printable</I +></TT ></A ></P ></LI @@ -3708,9 +4247,11 @@ CLASS="PARAMETER" ><P ><A HREF="#PRINTER" -><VAR +><TT CLASS="PARAMETER" ->printer</VAR +><I +>printer</I +></TT ></A ></P ></LI @@ -3718,9 +4259,35 @@ CLASS="PARAMETER" ><P ><A HREF="#PRINTERADMIN" -><VAR +><TT +CLASS="PARAMETER" +><I +>printer admin</I +></TT +></A +></P +></LI +><LI +><P +><A +HREF="#PRINTERDRIVER" +><TT CLASS="PARAMETER" ->printer admin</VAR +><I +>printer driver</I +></TT +></A +></P +></LI +><LI +><P +><A +HREF="#PRINTERDRIVERLOCATION" +><TT +CLASS="PARAMETER" +><I +>printer driver location</I +></TT ></A ></P ></LI @@ -3728,9 +4295,11 @@ CLASS="PARAMETER" ><P ><A HREF="#PRINTERNAME" -><VAR +><TT CLASS="PARAMETER" ->printer name</VAR +><I +>printer name</I +></TT ></A ></P ></LI @@ -3738,9 +4307,11 @@ CLASS="PARAMETER" ><P ><A HREF="#PRINTING" -><VAR +><TT CLASS="PARAMETER" ->printing</VAR +><I +>printing</I +></TT ></A ></P ></LI @@ -3748,9 +4319,11 @@ CLASS="PARAMETER" ><P ><A HREF="#PUBLIC" -><VAR +><TT CLASS="PARAMETER" ->public</VAR +><I +>public</I +></TT ></A ></P ></LI @@ -3758,9 +4331,11 @@ CLASS="PARAMETER" ><P ><A HREF="#QUEUEPAUSECOMMAND" -><VAR +><TT CLASS="PARAMETER" ->queuepause command</VAR +><I +>queuepause command</I +></TT ></A ></P ></LI @@ -3768,9 +4343,11 @@ CLASS="PARAMETER" ><P ><A HREF="#QUEUERESUMECOMMAND" -><VAR +><TT CLASS="PARAMETER" ->queueresume command</VAR +><I +>queueresume command</I +></TT ></A ></P ></LI @@ -3778,9 +4355,11 @@ CLASS="PARAMETER" ><P ><A HREF="#READLIST" -><VAR +><TT CLASS="PARAMETER" ->read list</VAR +><I +>read list</I +></TT ></A ></P ></LI @@ -3788,9 +4367,11 @@ CLASS="PARAMETER" ><P ><A HREF="#READONLY" -><VAR +><TT CLASS="PARAMETER" ->read only</VAR +><I +>read only</I +></TT ></A ></P ></LI @@ -3798,9 +4379,11 @@ CLASS="PARAMETER" ><P ><A HREF="#ROOTPOSTEXEC" -><VAR +><TT CLASS="PARAMETER" ->root postexec</VAR +><I +>root postexec</I +></TT ></A ></P ></LI @@ -3808,9 +4391,11 @@ CLASS="PARAMETER" ><P ><A HREF="#ROOTPREEXEC" -><VAR +><TT CLASS="PARAMETER" ->root preexec</VAR +><I +>root preexec</I +></TT ></A ></P ></LI @@ -3818,9 +4403,11 @@ CLASS="PARAMETER" ><P ><A HREF="#ROOTPREEXECCLOSE" -><VAR +><TT CLASS="PARAMETER" ->root preexec close</VAR +><I +>root preexec close</I +></TT ></A ></P ></LI @@ -3828,9 +4415,11 @@ CLASS="PARAMETER" ><P ><A HREF="#SECURITYMASK" -><VAR +><TT CLASS="PARAMETER" ->security mask</VAR +><I +>security mask</I +></TT ></A ></P ></LI @@ -3838,9 +4427,11 @@ CLASS="PARAMETER" ><P ><A HREF="#SETDIRECTORY" -><VAR +><TT CLASS="PARAMETER" ->set directory</VAR +><I +>set directory</I +></TT ></A ></P ></LI @@ -3848,9 +4439,11 @@ CLASS="PARAMETER" ><P ><A HREF="#SHAREMODES" -><VAR +><TT CLASS="PARAMETER" ->share modes</VAR +><I +>share modes</I +></TT ></A ></P ></LI @@ -3858,9 +4451,11 @@ CLASS="PARAMETER" ><P ><A HREF="#SHORTPRESERVECASE" -><VAR +><TT CLASS="PARAMETER" ->short preserve case</VAR +><I +>short preserve case</I +></TT ></A ></P ></LI @@ -3868,9 +4463,11 @@ CLASS="PARAMETER" ><P ><A HREF="#STRICTALLOCATE" -><VAR +><TT CLASS="PARAMETER" ->strict allocate</VAR +><I +>strict allocate</I +></TT ></A ></P ></LI @@ -3878,9 +4475,11 @@ CLASS="PARAMETER" ><P ><A HREF="#STRICTLOCKING" -><VAR +><TT CLASS="PARAMETER" ->strict locking</VAR +><I +>strict locking</I +></TT ></A ></P ></LI @@ -3888,9 +4487,11 @@ CLASS="PARAMETER" ><P ><A HREF="#STRICTSYNC" -><VAR +><TT CLASS="PARAMETER" ->strict sync</VAR +><I +>strict sync</I +></TT ></A ></P ></LI @@ -3898,9 +4499,11 @@ CLASS="PARAMETER" ><P ><A HREF="#SYNCALWAYS" -><VAR +><TT CLASS="PARAMETER" ->sync always</VAR +><I +>sync always</I +></TT ></A ></P ></LI @@ -3908,9 +4511,11 @@ CLASS="PARAMETER" ><P ><A HREF="#USECLIENTDRIVER" -><VAR +><TT CLASS="PARAMETER" ->use client driver</VAR +><I +>use client driver</I +></TT ></A ></P ></LI @@ -3918,9 +4523,11 @@ CLASS="PARAMETER" ><P ><A HREF="#USER" -><VAR +><TT CLASS="PARAMETER" ->user</VAR +><I +>user</I +></TT ></A ></P ></LI @@ -3928,9 +4535,11 @@ CLASS="PARAMETER" ><P ><A HREF="#USERNAME" -><VAR +><TT CLASS="PARAMETER" ->username</VAR +><I +>username</I +></TT ></A ></P ></LI @@ -3938,9 +4547,11 @@ CLASS="PARAMETER" ><P ><A HREF="#USERS" -><VAR +><TT CLASS="PARAMETER" ->users</VAR +><I +>users</I +></TT ></A ></P ></LI @@ -3948,9 +4559,11 @@ CLASS="PARAMETER" ><P ><A HREF="#VALIDUSERS" -><VAR +><TT CLASS="PARAMETER" ->valid users</VAR +><I +>valid users</I +></TT ></A ></P ></LI @@ -3958,9 +4571,11 @@ CLASS="PARAMETER" ><P ><A HREF="#VETOFILES" -><VAR +><TT CLASS="PARAMETER" ->veto files</VAR +><I +>veto files</I +></TT ></A ></P ></LI @@ -3968,9 +4583,11 @@ CLASS="PARAMETER" ><P ><A HREF="#VETOOPLOCKFILES" -><VAR +><TT CLASS="PARAMETER" ->veto oplock files</VAR +><I +>veto oplock files</I +></TT ></A ></P ></LI @@ -3978,9 +4595,11 @@ CLASS="PARAMETER" ><P ><A HREF="#VFSPATH" -><VAR +><TT CLASS="PARAMETER" ->vfs path</VAR +><I +>vfs path</I +></TT ></A ></P ></LI @@ -3988,9 +4607,11 @@ CLASS="PARAMETER" ><P ><A HREF="#VFSOBJECT" -><VAR +><TT CLASS="PARAMETER" ->vfs object</VAR +><I +>vfs object</I +></TT ></A ></P ></LI @@ -3998,9 +4619,11 @@ CLASS="PARAMETER" ><P ><A HREF="#VFSOPTIONS" -><VAR +><TT CLASS="PARAMETER" ->vfs options</VAR +><I +>vfs options</I +></TT ></A ></P ></LI @@ -4008,9 +4631,11 @@ CLASS="PARAMETER" ><P ><A HREF="#VOLUME" -><VAR +><TT CLASS="PARAMETER" ->volume</VAR +><I +>volume</I +></TT ></A ></P ></LI @@ -4018,9 +4643,11 @@ CLASS="PARAMETER" ><P ><A HREF="#WIDELINKS" -><VAR +><TT CLASS="PARAMETER" ->wide links</VAR +><I +>wide links</I +></TT ></A ></P ></LI @@ -4028,9 +4655,11 @@ CLASS="PARAMETER" ><P ><A HREF="#WRITABLE" -><VAR +><TT CLASS="PARAMETER" ->writable</VAR +><I +>writable</I +></TT ></A ></P ></LI @@ -4038,9 +4667,11 @@ CLASS="PARAMETER" ><P ><A HREF="#WRITECACHESIZE" -><VAR +><TT CLASS="PARAMETER" ->write cache size</VAR +><I +>write cache size</I +></TT ></A ></P ></LI @@ -4048,9 +4679,11 @@ CLASS="PARAMETER" ><P ><A HREF="#WRITELIST" -><VAR +><TT CLASS="PARAMETER" ->write list</VAR +><I +>write list</I +></TT ></A ></P ></LI @@ -4058,9 +4691,11 @@ CLASS="PARAMETER" ><P ><A HREF="#WRITEOK" -><VAR +><TT CLASS="PARAMETER" ->write ok</VAR +><I +>write ok</I +></TT ></A ></P ></LI @@ -4068,9 +4703,11 @@ CLASS="PARAMETER" ><P ><A HREF="#WRITEABLE" -><VAR +><TT CLASS="PARAMETER" ->writeable</VAR +><I +>writeable</I +></TT ></A ></P ></LI @@ -4079,7 +4716,7 @@ CLASS="PARAMETER" ><DIV CLASS="REFSECT1" ><A -NAME="AEN1527" +NAME="AEN1533" ></A ><H2 >EXPLANATION OF EACH PARAMETER</H2 @@ -4092,39 +4729,37 @@ 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" -><VAR +><TT CLASS="PARAMETER" ->shutdown script</VAR +><I +>shutdown script</I +></TT ></A >.</P ><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 @@ -4136,7 +4771,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 @@ -4147,10 +4782,12 @@ NAME="ADDPRINTERCOMMAND" NT/2000 print server.</P ><P >For a Samba host this means that the printer must be - physically added to the underlying printing system. The <VAR + physically added to the underlying printing system. The <TT CLASS="PARAMETER" +><I >add - printer command</VAR + printer command</I +></TT > defines a script to be run which will perform the necessary operations for adding the printer to the print system and to add the appropriate service definition @@ -4158,63 +4795,79 @@ 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 <VAR +>The <TT CLASS="PARAMETER" ->addprinter command</VAR +><I +>addprinter command</I +></TT > is automatically invoked with the following parameter (in - order):</P + order:</P ><P ></P ><UL ><LI ><P -><VAR +><TT CLASS="PARAMETER" ->printer name</VAR +><I +>printer name</I +></TT ></P ></LI ><LI ><P -><VAR +><TT CLASS="PARAMETER" ->share name</VAR +><I +>share name</I +></TT ></P ></LI ><LI ><P -><VAR +><TT CLASS="PARAMETER" ->port name</VAR +><I +>port name</I +></TT ></P ></LI ><LI ><P -><VAR +><TT CLASS="PARAMETER" ->driver name</VAR +><I +>driver name</I +></TT ></P ></LI ><LI ><P -><VAR +><TT CLASS="PARAMETER" ->location</VAR +><I +>location</I +></TT ></P ></LI ><LI ><P -><VAR +><TT CLASS="PARAMETER" ->Windows 9x driver location</VAR +><I +>Windows 9x driver location</I +></TT > </P ></LI @@ -4226,9 +4879,11 @@ CLASS="PARAMETER" only. The remaining fields in the structure are generated from answers to the APW questions.</P ><P ->Once the <VAR +>Once the <TT CLASS="PARAMETER" ->addprinter command</VAR +><I +>addprinter command</I +></TT > has been executed, <B CLASS="COMMAND" @@ -4243,39 +4898,37 @@ CLASS="COMMAND" </B > will return an ACCESS_DENIED error to the client.</P ><P -> The "add printer command" program can output a single line of text, - which Samba will set as the port the new printer is connected to. - If this line isn't output, Samba won't reload its printer shares. - </P -><P >See also <A HREF="#DELETEPRINTERCOMMAND" -><VAR +><TT CLASS="PARAMETER" -> deleteprinter command</VAR +><I +> deleteprinter command</I +></TT ></A >, <A HREF="#PRINTING" -><VAR +><TT CLASS="PARAMETER" ->printing</VAR +><I +>printing</I +></TT ></A >, <A HREF="#SHOWADDPRINTERWIZARD" -><VAR +><TT CLASS="PARAMETER" +><I >show add - printer wizard</VAR + printer wizard</I +></TT ></A ></P ><P ->Default: <SPAN -CLASS="emphasis" -><I +>Default: <I CLASS="EMPHASIS" >none</I -></SPAN ></P ><P >Example: <B @@ -4288,23 +4941,27 @@ 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 add and delete shares via the Windows NT 4.0 Server Manager. The - <VAR + <TT CLASS="PARAMETER" ->add share command</VAR +><I +>add share command</I +></TT > is used to define an external program or script which will add a new service definition to <TT CLASS="FILENAME" >smb.conf</TT >. In order to successfully - execute the <VAR + execute the <TT CLASS="PARAMETER" ->add share command</VAR +><I +>add share command</I +></TT >, <B CLASS="COMMAND" >smbd</B @@ -4317,9 +4974,11 @@ CLASS="COMMAND" CLASS="COMMAND" >smbd</B > will automatically invoke the - <VAR + <TT CLASS="PARAMETER" ->add share command</VAR +><I +>add share command</I +></TT > with four parameters. </P ><P @@ -4327,9 +4986,11 @@ CLASS="PARAMETER" ><UL ><LI ><P -><VAR +><TT CLASS="PARAMETER" ->configFile</VAR +><I +>configFile</I +></TT > - the location of the global <TT CLASS="FILENAME" @@ -4339,27 +5000,33 @@ CLASS="FILENAME" ></LI ><LI ><P -><VAR +><TT CLASS="PARAMETER" ->shareName</VAR +><I +>shareName</I +></TT > - the name of the new share. </P ></LI ><LI ><P -><VAR +><TT CLASS="PARAMETER" ->pathName</VAR +><I +>pathName</I +></TT > - path to an **existing** directory on disk. </P ></LI ><LI ><P -><VAR +><TT CLASS="PARAMETER" ->comment</VAR +><I +>comment</I +></TT > - comment string to associate with the new share. </P @@ -4369,37 +5036,40 @@ CLASS="PARAMETER" > This parameter is only used for add file shares. To add printer shares, see the <A HREF="#ADDPRINTERCOMMAND" -><VAR +><TT CLASS="PARAMETER" +><I >addprinter - command</VAR + command</I +></TT ></A >. </P ><P > See also <A HREF="#CHANGESHARECOMMAND" -><VAR +><TT CLASS="PARAMETER" +><I >change share - command</VAR + command</I +></TT ></A >, <A HREF="#DELETESHARECOMMAND" -><VAR +><TT CLASS="PARAMETER" +><I >delete share - command</VAR + command</I +></TT ></A >. </P ><P ->Default: <SPAN -CLASS="emphasis" -><I +>Default: <I CLASS="EMPHASIS" >none</I -></SPAN ></P ><P >Example: <B @@ -4411,17 +5081,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 @@ -4444,7 +5112,7 @@ CLASS="COMMAND" ><A NAME="ADSSERVER" ></A ->>ads server (G)</DT +>ads server (G)</DT ><DD ><P >If this option is specified, samba does @@ -4466,22 +5134,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 @@ -4493,51 +5157,50 @@ 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 <VAR +> be set to <TT CLASS="PARAMETER" ->security = share</VAR +><I +>security = share</I +></TT > - and <VAR + and <TT CLASS="PARAMETER" ->add user script</VAR +><I +>add user script</I +></TT > must be set to a full pathname for a script that will create a UNIX - user given one argument of <VAR + user given one argument of <TT CLASS="PARAMETER" ->%u</VAR +><I +>%u</I +></TT >, which expands into 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 -> contacts the <VAR -CLASS="PARAMETER" ->password server</VAR + at login (session setup in the SMB protocol) time, <A +HREF="smbd.8.html" +TARGET="_top" +> smbd</A +> contacts the <TT +CLASS="PARAMETER" +><I +>password server</I +></TT > and attempts to authenticate the given user with the given password. If the authentication succeeds then <B @@ -4545,24 +5208,25 @@ CLASS="COMMAND" >smbd</B > attempts to find a UNIX user in the UNIX password database to map the - Windows user into. If this lookup fails, and <VAR + Windows user into. If this lookup fails, and <TT CLASS="PARAMETER" +><I >add user script - </VAR + </I +></TT > is set then <B 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 <VAR + any <TT CLASS="PARAMETER" ->%u</VAR +><I +>%u</I +></TT > argument to be the user name to create.</P ><P >If this script successfully creates the user then <B @@ -4575,23 +5239,29 @@ CLASS="COMMAND" ><P >See also <A HREF="#SECURITY" -><VAR +><TT CLASS="PARAMETER" -> security</VAR +><I +> security</I +></TT ></A >, <A HREF="#PASSWORDSERVER" -> <VAR +> <TT CLASS="PARAMETER" ->password server</VAR +><I +>password server</I +></TT ></A >, <A HREF="#DELETEUSERSCRIPT" -><VAR +><TT CLASS="PARAMETER" +><I >delete user - script</VAR + script</I +></TT ></A >.</P ><P @@ -4611,27 +5281,24 @@ 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 - <VAR + <TT CLASS="PARAMETER" ->%g</VAR +><I +>%g</I +></TT > to the group name passed. This script is only useful for installations using the Windows NT domain administration tools. The script is @@ -4645,7 +5312,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 @@ -4656,12 +5323,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 @@ -4673,32 +5337,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 <VAR +>. Any <TT CLASS="PARAMETER" ->%g</VAR -> will be replaced with the group name and - any <VAR +><I +>%g</I +></TT +> will be + replaced with the group name and any <TT CLASS="PARAMETER" ->%u</VAR -> will be replaced with the user name. +><I +>%u</I +></TT +> will + be replaced with the user name. </P ><P >Default: <B @@ -4715,14 +5379,16 @@ CLASS="COMMAND" ><A NAME="ALLOWHOSTS" ></A ->>allow hosts (S)</DT +>allow hosts (S)</DT ><DD ><P >Synonym for <A HREF="#HOSTSALLOW" -> <VAR +> <TT CLASS="PARAMETER" ->hosts allow</VAR +><I +>hosts allow</I +></TT ></A >.</P ></DD @@ -4730,7 +5396,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 @@ -4762,22 +5428,24 @@ 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 HREF="#SECURITY" -><VAR +><TT CLASS="PARAMETER" ->security</VAR +><I +>security</I +></TT ></A > option is set to - <CODE + <TT CLASS="CONSTANT" ->server</CODE -> or <CODE +>server</TT +> or <TT CLASS="CONSTANT" ->domain</CODE +>domain</TT >. If it is set to no, then attempts to connect to a resource from a domain or workgroup other than the one which <A @@ -4806,16 +5474,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, @@ -4839,7 +5510,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 @@ -4861,14 +5532,16 @@ CLASS="COMMAND" ><A NAME="AUTOSERVICES" ></A ->>auto services (G)</DT +>auto services (G)</DT ><DD ><P >This is a synonym for the <A HREF="#PRELOAD" -> <VAR +> <TT CLASS="PARAMETER" ->preload</VAR +><I +>preload</I +></TT ></A >.</P ></DD @@ -4876,7 +5549,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 @@ -4886,9 +5559,11 @@ CLASS="COMMAND" > will use when authenticating a user. This option defaults to sensible values based on <A HREF="#SECURITY" -><VAR +><TT CLASS="PARAMETER" -> security</VAR +><I +> security</I +></TT ></A >. @@ -4911,19 +5586,18 @@ CLASS="COMMAND" ><A NAME="AVAILABLE" ></A ->>available (S)</DT +>available (S)</DT ><DD ><P >This parameter lets you "turn off" a service. If - <VAR + <TT CLASS="PARAMETER" ->available = no</VAR ->, then <SPAN -CLASS="emphasis" ><I +>available = no</I +></TT +>, then <I CLASS="EMPHASIS" >ALL</I -></SPAN > attempts to connect to the service will fail. Such failures are logged.</P @@ -4937,24 +5611,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" @@ -4973,19 +5645,23 @@ CLASS="COMMAND" CLASS="COMMAND" >nmbd</B > will service - name requests on all of these sockets. If <VAR + name requests on all of these sockets. If <TT CLASS="PARAMETER" +><I >bind interfaces - only</VAR + only</I +></TT > is set then <B CLASS="COMMAND" >nmbd</B > will check the source address of any packets coming in on the broadcast sockets and discard any that don't match the broadcast addresses of the - interfaces in the <VAR + interfaces in the <TT CLASS="PARAMETER" ->interfaces</VAR +><I +>interfaces</I +></TT > parameter list. As unicast packets are received on the other sockets it allows <B @@ -4993,9 +5669,11 @@ CLASS="COMMAND" >nmbd</B > to refuse to serve names to machines that send packets that arrive through any interfaces not listed in the - <VAR + <TT CLASS="PARAMETER" ->interfaces</VAR +><I +>interfaces</I +></TT > list. IP Source address spoofing does defeat this simple check, however, so it must not be used seriously as a security feature for <B @@ -5003,14 +5681,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 @@ -5022,60 +5698,63 @@ CLASS="COMMAND" that are serving PPP or other intermittent or non-broadcast network interfaces as it will not cope with non-permanent interfaces.</P ><P ->If <VAR +>If <TT CLASS="PARAMETER" ->bind interfaces only</VAR -> is set then - unless the network address <SPAN -CLASS="emphasis" ><I +>bind interfaces only</I +></TT +> is set then + unless the network address <I CLASS="EMPHASIS" >127.0.0.1</I -></SPAN > is added - to the <VAR -CLASS="PARAMETER" ->interfaces</VAR -> 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 + to the <TT +CLASS="PARAMETER" +><I +>interfaces</I +></TT +> parameter list <A +HREF="smbpasswd.8.html" +TARGET="_top" +><B +CLASS="COMMAND" +>smbpasswd(8)</B +></A +> + and <A +HREF="swat.8.html" +TARGET="_top" +><B +CLASS="COMMAND" +>swat(8)</B +></A +> may + not work as expected due to the reasons covered below.</P ><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 - <VAR + <TT CLASS="PARAMETER" ->bind interfaces only</VAR -> is set then unless the - network address <SPAN -CLASS="emphasis" ><I +>bind interfaces only</I +></TT +> is set then unless the + network address <I CLASS="EMPHASIS" >127.0.0.1</I -></SPAN > is added to the - <VAR + <TT CLASS="PARAMETER" ->interfaces</VAR +><I +>interfaces</I +></TT > parameter list then <B CLASS="COMMAND" > smbpasswd</B @@ -5084,22 +5763,26 @@ 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 -> <VAR -CLASS="PARAMETER" ->-r <VAR + of the local host by using its <A +HREF="smbpasswd.8.html#minusr" +TARGET="_top" +> <TT +CLASS="PARAMETER" +><I +>-r <TT CLASS="REPLACEABLE" ->remote machine</VAR -></VAR +><I +>remote machine</I +></TT +></I +></TT > - parameter, with <VAR + </A +> parameter, with <TT CLASS="REPLACEABLE" ->remote machine</VAR +><I +>remote machine</I +></TT > set to the IP name of the primary interface of the local host.</P ><P @@ -5114,19 +5797,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 @@ -5155,16 +5832,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 @@ -5174,9 +5848,9 @@ CLASS="REFENTRYTITLE" queue the lock request, and periodically attempt to obtain the lock until the timeout period expires.</P ><P ->If this parameter is set to <CODE +>If this parameter is set to <TT CLASS="CONSTANT" ->no</CODE +>no</TT >, then samba will behave as previous versions of Samba would and will fail the lock request immediately if the lock range @@ -5191,15 +5865,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 @@ -5214,19 +5887,31 @@ 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 HREF="#BROWSEABLE" -><VAR +><TT CLASS="PARAMETER" -> browseable</VAR +><I +> browseable</I +></TT ></A >.</P ></DD @@ -5234,23 +5919,24 @@ 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" >NetServerEnum</B > call. Normally - set to <CODE + set to <TT CLASS="CONSTANT" ->yes</CODE +>yes</TT >. You should never need to change this.</P ><P @@ -5263,7 +5949,7 @@ CLASS="COMMAND" ><A NAME="BROWSEABLE" ></A ->>browseable (S)</DT +>browseable (S)</DT ><DD ><P >This controls whether this share is seen in @@ -5278,11 +5964,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="#AEN207" +HREF="#AEN205" >NAME MANGLING</A >.</P ><P @@ -5295,7 +5981,7 @@ CLASS="COMMAND" ><A NAME="CASESIGNAMES" ></A ->>casesignames (S)</DT +>casesignames (S)</DT ><DD ><P >Synonym for <A @@ -5308,23 +5994,26 @@ 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 <VAR + on each requested directory once every <TT CLASS="PARAMETER" +><I >change notify - timeout</VAR + timeout</I +></TT > seconds.</P ><P >Default: <B @@ -5343,23 +6032,27 @@ 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 add and delete shares via the Windows NT 4.0 Server Manager. The - <VAR + <TT CLASS="PARAMETER" ->change share command</VAR +><I +>change share command</I +></TT > is used to define an external program or script which will modify an existing service definition in <TT CLASS="FILENAME" >smb.conf</TT >. In order to successfully - execute the <VAR + execute the <TT CLASS="PARAMETER" ->change share command</VAR +><I +>change share command</I +></TT >, <B CLASS="COMMAND" >smbd</B @@ -5372,9 +6065,11 @@ CLASS="COMMAND" CLASS="COMMAND" >smbd</B > will automatically invoke the - <VAR + <TT CLASS="PARAMETER" ->change share command</VAR +><I +>change share command</I +></TT > with four parameters. </P ><P @@ -5382,9 +6077,11 @@ CLASS="PARAMETER" ><UL ><LI ><P -><VAR +><TT CLASS="PARAMETER" ->configFile</VAR +><I +>configFile</I +></TT > - the location of the global <TT CLASS="FILENAME" @@ -5394,27 +6091,33 @@ CLASS="FILENAME" ></LI ><LI ><P -><VAR +><TT CLASS="PARAMETER" ->shareName</VAR +><I +>shareName</I +></TT > - the name of the new share. </P ></LI ><LI ><P -><VAR +><TT CLASS="PARAMETER" ->pathName</VAR +><I +>pathName</I +></TT > - path to an **existing** directory on disk. </P ></LI ><LI ><P -><VAR +><TT CLASS="PARAMETER" ->comment</VAR +><I +>comment</I +></TT > - comment string to associate with the new share. </P @@ -5427,27 +6130,28 @@ CLASS="PARAMETER" ><P > See also <A HREF="#ADDSHARECOMMAND" -><VAR +><TT CLASS="PARAMETER" +><I >add share - command</VAR + command</I +></TT ></A >, <A HREF="#DELETESHARECOMMAND" -><VAR +><TT CLASS="PARAMETER" +><I >delete - share command</VAR + share command</I +></TT ></A >. </P ><P ->Default: <SPAN -CLASS="emphasis" -><I +>Default: <I CLASS="EMPHASIS" >none</I -></SPAN ></P ><P >Example: <B @@ -5459,7 +6163,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 @@ -5473,18 +6177,17 @@ CLASS="COMMAND" >If you want to set the string that is displayed next to the machine name then see the <A HREF="#SERVERSTRING" -><VAR +><TT CLASS="PARAMETER" -> server string</VAR +><I +> server string</I +></TT ></A > parameter.</P ><P ->Default: <SPAN -CLASS="emphasis" -><I +>Default: <I CLASS="EMPHASIS" >No comment string</I -></SPAN ></P ><P >Example: <B @@ -5496,7 +6199,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 @@ -5528,7 +6231,7 @@ CLASS="COMMAND" ><A NAME="COPY" ></A ->>copy (S)</DT +>copy (S)</DT ><DD ><P >This parameter allows you to "clone" service @@ -5541,12 +6244,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 @@ -5558,15 +6258,17 @@ CLASS="COMMAND" ><A NAME="CREATEMASK" ></A ->>create mask (S)</DT +>create mask (S)</DT ><DD ><P >A synonym for this parameter is <A HREF="#CREATEMODE" -><VAR +><TT CLASS="PARAMETER" ->create mode</VAR +><I +>create mode</I +></TT > </A >.</P @@ -5575,12 +6277,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 @@ -5591,9 +6290,11 @@ CLASS="EMPHASIS" >Following this Samba will bit-wise 'OR' the UNIX mode created from this parameter with the value of the <A HREF="#FORCECREATEMODE" -><VAR +><TT CLASS="PARAMETER" ->force create mode</VAR +><I +>force create mode</I +></TT ></A > parameter which is set to 000 by default.</P @@ -5601,33 +6302,41 @@ CLASS="PARAMETER" >This parameter does not affect directory modes. See the parameter <A HREF="#DIRECTORYMODE" -><VAR +><TT CLASS="PARAMETER" +><I >directory mode - </VAR + </I +></TT ></A > for details.</P ><P >See also the <A HREF="#FORCECREATEMODE" -><VAR +><TT CLASS="PARAMETER" +><I >force - create mode</VAR + create mode</I +></TT ></A > parameter for forcing particular mode bits to be set on created files. See also the <A HREF="#DIRECTORYMODE" -> <VAR +> <TT CLASS="PARAMETER" ->directory mode</VAR +><I +>directory mode</I +></TT ></A > parameter for masking mode bits on created directories. See also the <A HREF="#INHERITPERMISSIONS" -> <VAR +> <TT CLASS="PARAMETER" ->inherit permissions</VAR +><I +>inherit permissions</I +></TT ></A > parameter.</P ><P @@ -5635,9 +6344,11 @@ CLASS="PARAMETER" set by Windows NT/2000 ACL editors. If the administrator wishes to enforce a mask on access control lists also, they need to set the <A HREF="#SECURITYMASK" -><VAR +><TT CLASS="PARAMETER" ->security mask</VAR +><I +>security mask</I +></TT ></A >.</P ><P @@ -5655,14 +6366,16 @@ CLASS="COMMAND" ><A NAME="CREATEMODE" ></A ->>create mode (S)</DT +>create mode (S)</DT ><DD ><P >This is a synonym for <A HREF="#CREATEMASK" -><VAR +><TT CLASS="PARAMETER" -> create mask</VAR +><I +> create mask</I +></TT ></A >.</P ></DD @@ -5670,16 +6383,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 @@ -5708,7 +6418,7 @@ CLASS="COMMAND" ><A NAME="DEADTIME" ></A ->>deadtime (G)</DT +>deadtime (G)</DT ><DD ><P >The value of the parameter (a decimal integer) @@ -5743,7 +6453,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 @@ -5753,9 +6463,11 @@ NAME="DEBUGHIRESTIMESTAMP" ><P >Note that the parameter <A HREF="#DEBUGTIMESTAMP" -><VAR +><TT CLASS="PARAMETER" -> debug timestamp</VAR +><I +> debug timestamp</I +></TT ></A > must be on for this to have an effect.</P @@ -5769,7 +6481,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 @@ -5783,9 +6495,11 @@ TARGET="_top" ><P >Note that the parameter <A HREF="#DEBUGTIMESTAMP" -><VAR +><TT CLASS="PARAMETER" -> debug timestamp</VAR +><I +> debug timestamp</I +></TT ></A > must be on for this to have an effect.</P @@ -5799,15 +6513,17 @@ CLASS="COMMAND" ><A NAME="DEBUGTIMESTAMP" ></A ->>debug timestamp (G)</DT +>debug timestamp (G)</DT ><DD ><P >Samba debug log messages are timestamped by default. If you are running at a high <A HREF="#DEBUGLEVEL" -> <VAR +> <TT CLASS="PARAMETER" ->debug level</VAR +><I +>debug level</I +></TT ></A > these timestamps can be distracting. This boolean parameter allows timestamping @@ -5822,7 +6538,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 @@ -5832,9 +6548,11 @@ NAME="DEBUGUID" ><P >Note that the parameter <A HREF="#DEBUGTIMESTAMP" -><VAR +><TT CLASS="PARAMETER" -> debug timestamp</VAR +><I +> debug timestamp</I +></TT ></A > must be on for this to have an effect.</P @@ -5848,14 +6566,16 @@ CLASS="COMMAND" ><A NAME="DEBUGLEVEL" ></A ->>debuglevel (G)</DT +>debuglevel (G)</DT ><DD ><P >Synonym for <A HREF="#LOGLEVEL" -><VAR +><TT CLASS="PARAMETER" -> log level</VAR +><I +> log level</I +></TT ></A >.</P ></DD @@ -5863,14 +6583,16 @@ CLASS="PARAMETER" ><A NAME="DEFAULT" ></A ->>default (G)</DT +>default (G)</DT ><DD ><P >A synonym for <A HREF="#DEFAULTSERVICE" -><VAR +><TT CLASS="PARAMETER" -> default service</VAR +><I +> default service</I +></TT ></A >.</P ></DD @@ -5878,17 +6600,19 @@ CLASS="PARAMETER" ><A NAME="DEFAULTCASE" ></A ->>default case (S)</DT +>default case (S)</DT ><DD ><P >See the section on <A -HREF="#AEN207" +HREF="#AEN205" > NAME MANGLING</A >. Also note the <A HREF="#SHORTPRESERVECASE" -> <VAR +> <TT CLASS="PARAMETER" ->short preserve case</VAR +><I +>short preserve case</I +></TT ></A > parameter.</P ><P @@ -5901,7 +6625,7 @@ CLASS="COMMAND" ><A NAME="DEFAULTDEVMODE" ></A ->>default devmode (S)</DT +>default devmode (S)</DT ><DD ><P >This parameter is only applicable to <A @@ -5952,17 +6676,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 @@ -5972,23 +6693,29 @@ CLASS="EMPHASIS" ><P >Typically the default service would be a <A HREF="#GUESTOK" -> <VAR +> <TT CLASS="PARAMETER" ->guest ok</VAR +><I +>guest ok</I +></TT ></A >, <A HREF="#READONLY" -> <VAR +> <TT CLASS="PARAMETER" ->read-only</VAR +><I +>read-only</I +></TT ></A > service.</P ><P >Also note that the apparent service name will be changed to equal that of the requested service, this is very useful as it - allows you to use macros like <VAR + allows you to use macros like <TT CLASS="PARAMETER" ->%S</VAR +><I +>%S</I +></TT > to make a wildcard service.</P ><P @@ -5998,48 +6725,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 <VAR -CLASS="PARAMETER" ->%g</VAR -> to the group name passed. - This script is only useful for installations using the Windows NT domain administration tools. +> 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. </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 @@ -6048,9 +6780,11 @@ NAME="DELETEPRINTERCOMMAND" DeletePrinter() RPC call.</P ><P >For a Samba host this means that the printer must be - physically deleted from underlying printing system. The <VAR + physically deleted from underlying printing system. The <TT CLASS="PARAMETER" -> deleteprinter command</VAR +><I +> deleteprinter command</I +></TT > defines a script to be run which will perform the necessary operations for removing the printer from the print system and from <TT @@ -6059,18 +6793,24 @@ CLASS="FILENAME" >. </P ><P ->The <VAR +>The <TT CLASS="PARAMETER" ->deleteprinter command</VAR +><I +>deleteprinter command</I +></TT > is - automatically called with only one parameter: <VAR + automatically called with only one parameter: <TT CLASS="PARAMETER" -> "printer name"</VAR +><I +> "printer name"</I +></TT >.</P ><P ->Once the <VAR +>Once the <TT CLASS="PARAMETER" ->deleteprinter command</VAR +><I +>deleteprinter command</I +></TT > has been executed, <B CLASS="COMMAND" @@ -6087,32 +6827,35 @@ CLASS="COMMAND" ><P >See also <A HREF="#ADDPRINTERCOMMAND" -><VAR +><TT CLASS="PARAMETER" -> addprinter command</VAR +><I +> addprinter command</I +></TT ></A >, <A HREF="#PRINTING" -><VAR +><TT CLASS="PARAMETER" ->printing</VAR +><I +>printing</I +></TT ></A >, <A HREF="#SHOWADDPRINTERWIZARD" -><VAR +><TT CLASS="PARAMETER" +><I >show add - printer wizard</VAR + printer wizard</I +></TT ></A ></P ><P ->Default: <SPAN -CLASS="emphasis" -><I +>Default: <I CLASS="EMPHASIS" >none</I -></SPAN ></P ><P >Example: <B @@ -6125,7 +6868,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. @@ -6144,23 +6887,27 @@ 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 add and delete shares via the Windows NT 4.0 Server Manager. The - <VAR + <TT CLASS="PARAMETER" ->delete share command</VAR +><I +>delete share command</I +></TT > is used to define an external program or script which will remove an existing service definition from <TT CLASS="FILENAME" >smb.conf</TT >. In order to successfully - execute the <VAR + execute the <TT CLASS="PARAMETER" ->delete share command</VAR +><I +>delete share command</I +></TT >, <B CLASS="COMMAND" >smbd</B @@ -6173,9 +6920,11 @@ CLASS="COMMAND" CLASS="COMMAND" >smbd</B > will automatically invoke the - <VAR + <TT CLASS="PARAMETER" ->delete share command</VAR +><I +>delete share command</I +></TT > with two parameters. </P ><P @@ -6183,9 +6932,11 @@ CLASS="PARAMETER" ><UL ><LI ><P -><VAR +><TT CLASS="PARAMETER" ->configFile</VAR +><I +>configFile</I +></TT > - the location of the global <TT CLASS="FILENAME" @@ -6195,9 +6946,11 @@ CLASS="FILENAME" ></LI ><LI ><P -><VAR +><TT CLASS="PARAMETER" ->shareName</VAR +><I +>shareName</I +></TT > - the name of the existing service. </P @@ -6207,37 +6960,40 @@ CLASS="PARAMETER" > This parameter is only used to remove file shares. To delete printer shares, see the <A HREF="#DELETEPRINTERCOMMAND" -><VAR +><TT CLASS="PARAMETER" +><I >deleteprinter - command</VAR + command</I +></TT ></A >. </P ><P > See also <A HREF="#ADDSHARECOMMAND" -><VAR +><TT CLASS="PARAMETER" +><I >add share - command</VAR + command</I +></TT ></A >, <A HREF="#CHANGESHARECOMMAND" -><VAR +><TT CLASS="PARAMETER" +><I >change - share command</VAR + share command</I +></TT ></A >. </P ><P ->Default: <SPAN -CLASS="emphasis" -><I +>Default: <I CLASS="EMPHASIS" >none</I -></SPAN ></P ><P >Example: <B @@ -6249,18 +7005,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 @@ -6290,32 +7047,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 <VAR +>. Any <TT CLASS="PARAMETER" ->%g</VAR -> will be replaced with the group name and - any <VAR +><I +>%g</I +></TT +> will be + replaced with the group name and any <TT CLASS="PARAMETER" ->%u</VAR -> will be replaced with the user name. +><I +>%u</I +></TT +> will + be replaced with the user name. </P ><P >Default: <B @@ -6332,28 +7089,30 @@ 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 delete a directory that contains one or more vetoed directories (see the <A HREF="#VETOFILES" -><VAR +><TT CLASS="PARAMETER" ->veto files</VAR +><I +>veto files</I +></TT ></A > - option). If this option is set to <CODE + option). If this option is set to <TT CLASS="CONSTANT" ->no</CODE +>no</TT > (the default) then if a vetoed directory contains any non-vetoed files or directories then the directory delete will fail. This is usually what you want.</P ><P ->If this option is set to <CODE +>If this option is set to <TT CLASS="CONSTANT" ->yes</CODE +>yes</TT >, then Samba will attempt to recursively delete any files and directories within the vetoed directory. This can be useful for integration with file @@ -6373,10 +7132,12 @@ CLASS="COMMAND" ><P >See also the <A HREF="#VETOFILES" -><VAR +><TT CLASS="PARAMETER" +><I >veto - files</VAR + files</I +></TT ></A > parameter.</P ><P @@ -6389,15 +7150,17 @@ CLASS="COMMAND" ><A NAME="DENYHOSTS" ></A ->>deny hosts (S)</DT +>deny hosts (S)</DT ><DD ><P >Synonym for <A HREF="#HOSTSDENY" -><VAR +><TT CLASS="PARAMETER" +><I >hosts - deny</VAR + deny</I +></TT ></A >.</P ></DD @@ -6405,12 +7168,14 @@ CLASS="PARAMETER" ><A NAME="DFREECOMMAND" ></A ->>dfree command (G)</DT +>dfree command (G)</DT ><DD ><P ->The <VAR +>The <TT CLASS="PARAMETER" ->dfree command</VAR +><I +>dfree command</I +></TT > setting should only be used on systems where a problem occurs with the internal disk space calculations. This has been known to happen with Ultrix, @@ -6434,23 +7199,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 @@ -6461,20 +7220,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 @@ -6484,15 +7263,17 @@ CLASS="PROGRAMLISTING" ><A NAME="DIRECTORY" ></A ->>directory (S)</DT +>directory (S)</DT ><DD ><P >Synonym for <A HREF="#PATH" -><VAR +><TT CLASS="PARAMETER" +><I >path - </VAR + </I +></TT ></A >.</P ></DD @@ -6500,7 +7281,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 @@ -6511,12 +7292,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 @@ -6528,10 +7306,12 @@ CLASS="EMPHASIS" >Following this Samba will bit-wise 'OR' the UNIX mode created from this parameter with the value of the <A HREF="#FORCEDIRECTORYMODE" -><VAR +><TT CLASS="PARAMETER" +><I >force directory mode - </VAR + </I +></TT ></A > parameter. This parameter is set to 000 by default (i.e. no extra mode bits are added).</P @@ -6540,44 +7320,54 @@ CLASS="PARAMETER" set by Windows NT/2000 ACL editors. If the administrator wishes to enforce a mask on access control lists also, they need to set the <A HREF="#DIRECTORYSECURITYMASK" -><VAR +><TT CLASS="PARAMETER" ->directory security mask</VAR +><I +>directory security mask</I +></TT ></A >.</P ><P >See the <A HREF="#FORCEDIRECTORYMODE" -><VAR +><TT CLASS="PARAMETER" +><I >force - directory mode</VAR + directory mode</I +></TT ></A > parameter to cause particular mode bits to always be set on created directories.</P ><P >See also the <A HREF="#CREATEMODE" -><VAR +><TT CLASS="PARAMETER" +><I >create mode - </VAR + </I +></TT ></A > parameter for masking mode bits on created files, and the <A HREF="#DIRECTORYSECURITYMASK" -><VAR +><TT CLASS="PARAMETER" +><I >directory - security mask</VAR + security mask</I +></TT ></A > parameter.</P ><P >Also refer to the <A HREF="#INHERITPERMISSIONS" -><VAR +><TT CLASS="PARAMETER" -> inherit permissions</VAR +><I +> inherit permissions</I +></TT ></A > parameter.</P ><P @@ -6595,14 +7385,16 @@ CLASS="COMMAND" ><A NAME="DIRECTORYMODE" ></A ->>directory mode (S)</DT +>directory mode (S)</DT ><DD ><P >Synonym for <A HREF="#DIRECTORYMASK" -><VAR +><TT CLASS="PARAMETER" -> directory mask</VAR +><I +> directory mask</I +></TT ></A ></P ></DD @@ -6610,7 +7402,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 @@ -6628,40 +7420,43 @@ 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. Administrators of most normal systems will probably want to leave - it as the default of <CODE + it as the default of <TT CLASS="CONSTANT" ->0777</CODE +>0777</TT >.</P ><P >See also the <A HREF="#FORCEDIRECTORYSECURITYMODE" -><VAR +><TT CLASS="PARAMETER" -> force directory security mode</VAR +><I +> force directory security mode</I +></TT ></A >, <A HREF="#SECURITYMASK" -><VAR +><TT CLASS="PARAMETER" ->security mask</VAR +><I +>security mask</I +></TT ></A >, <A HREF="#FORCESECURITYMODE" -><VAR +><TT CLASS="PARAMETER" +><I >force security mode - </VAR + </I +></TT ></A > parameters.</P ><P @@ -6679,7 +7474,7 @@ CLASS="COMMAND" ><A NAME="DISABLENETBIOS" ></A ->>disable netbios (G)</DT +>disable netbios (G)</DT ><DD ><P >Enabling this parameter will disable netbios support @@ -6704,7 +7499,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 @@ -6716,12 +7511,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 @@ -6740,7 +7532,7 @@ CLASS="COMMAND" ><A NAME="DISPLAYCHARSET" ></A ->>display charset (G)</DT +>display charset (G)</DT ><DD ><P >Specifies the charset that samba will use @@ -6765,19 +7557,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 @@ -6792,9 +7583,11 @@ CLASS="COMMAND" ><P >See also the parameter <A HREF="#WINSSUPPORT" -><VAR +><TT CLASS="PARAMETER" -> wins support</VAR +><I +> wins support</I +></TT ></A >.</P ><P @@ -6807,18 +7600,20 @@ CLASS="COMMAND" ><A NAME="DOMAINLOGONS" ></A ->>domain logons (G)</DT +>domain logons (G)</DT ><DD ><P ->If set to <CODE +>If set to <TT CLASS="CONSTANT" ->yes</CODE +>yes</TT >, the Samba server will serve Windows 95/98 Domain logons for the <A HREF="#WORKGROUP" -> <VAR +> <TT CLASS="PARAMETER" ->workgroup</VAR +><I +>workgroup</I +></TT ></A > it is in. Samba 2.2 has limited capability to act as a domain controller for Windows @@ -6838,15 +7633,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" @@ -6855,48 +7651,60 @@ CLASS="COMMAND" claim a special domain specific NetBIOS name that identifies it as a domain master browser for its given <A HREF="#WORKGROUP" -> <VAR +> <TT CLASS="PARAMETER" ->workgroup</VAR +><I +>workgroup</I +></TT ></A >. Local master browsers - in the same <VAR + in the same <TT CLASS="PARAMETER" ->workgroup</VAR +><I +>workgroup</I +></TT > on broadcast-isolated subnets will give this <B 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 <VAR + able to claim this <TT CLASS="PARAMETER" ->workgroup</VAR +><I +>workgroup</I +></TT > specific special NetBIOS name that identifies them as domain master browsers for - that <VAR + that <TT CLASS="PARAMETER" ->workgroup</VAR +><I +>workgroup</I +></TT > by default (i.e. there is no way to prevent a Windows NT PDC from attempting to do this). This means that if this parameter is set and <B CLASS="COMMAND" >nmbd</B > claims - the special name for a <VAR + the special name for a <TT CLASS="PARAMETER" ->workgroup</VAR +><I +>workgroup</I +></TT > before a Windows NT PDC is able to do so then cross subnet browsing will behave strangely and may fail.</P @@ -6908,18 +7716,24 @@ CLASS="COMMAND" >domain logons = yes</B > </A ->, then the default behavior is to enable the <VAR +>, then the default behavior is to enable the <TT CLASS="PARAMETER" +><I >domain - master</VAR -> parameter. If <VAR + master</I +></TT +> parameter. If <TT CLASS="PARAMETER" ->domain logons</VAR +><I +>domain logons</I +></TT > is - not enabled (the default setting), then neither will <VAR + not enabled (the default setting), then neither will <TT CLASS="PARAMETER" +><I >domain - master</VAR + master</I +></TT > be enabled by default.</P ><P >Default: <B @@ -6931,7 +7745,7 @@ CLASS="COMMAND" ><A NAME="DONTDESCEND" ></A ->>dont descend (S)</DT +>dont descend (S)</DT ><DD ><P >There are certain directories on some systems @@ -6953,13 +7767,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 @@ -6971,7 +7782,7 @@ CLASS="COMMAND" ><A NAME="DOSCHARSET" ></A ->>dos charset (G)</DT +>dos charset (G)</DT ><DD ><P >DOS SMB clients assume the server has @@ -6979,14 +7790,13 @@ NAME="DOSCHARSET" charset Samba should talk to DOS clients. </P ><P ->The default depends on which charsets you have installed. +>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 @@ -6994,7 +7804,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 @@ -7017,19 +7827,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 @@ -7052,7 +7864,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 @@ -7063,15 +7875,13 @@ NAME="DOSFILETIMES" CLASS="COMMAND" >smbd</B > is acting - on behalf of is not the file owner. Setting this option to <CODE + on behalf of is not the file owner. Setting this option to <TT CLASS="CONSTANT" -> yes</CODE -> allows DOS semantics and <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbd</SPAN ->(8)</SPAN +> yes</TT +> allows DOS semantics and <A +HREF="smbd.8.html" +TARGET="_top" +>smbd</A > will change the file timestamp as DOS requires.</P ><P @@ -7084,7 +7894,7 @@ CLASS="COMMAND" ><A NAME="ENCRYPTPASSWORDS" ></A ->>encrypt passwords (G)</DT +>encrypt passwords (G)</DT ><DD ><P >This boolean controls whether encrypted passwords @@ -7098,25 +7908,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" @@ -7137,7 +7951,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 @@ -7168,7 +7982,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 @@ -7176,9 +7990,9 @@ NAME="ENUMPORTSCOMMAND" is associated with a port monitor and generally takes the form of a local port (i.e. LPT1:, COM1:, FILE:) or a remote port (i.e. LPD Port Monitor, etc...). By default, Samba has only one - port defined--<CODE + port defined--<TT CLASS="CONSTANT" ->"Samba Printer Port"</CODE +>"Samba Printer Port"</TT >. Under Windows NT/2000, all printers must have a valid port name. If you wish to have a list of ports displayed (<B @@ -7186,24 +8000,23 @@ CLASS="COMMAND" >smbd </B > does not use a port name for anything) other than - the default <CODE + the default <TT CLASS="CONSTANT" ->"Samba Printer Port"</CODE +>"Samba Printer Port"</TT >, you - can define <VAR + can define <TT CLASS="PARAMETER" ->enumports command</VAR +><I +>enumports command</I +></TT > to point to a program which should generate a list of ports, one per line, 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 @@ -7216,14 +8029,16 @@ CLASS="COMMAND" ><A NAME="EXEC" ></A ->>exec (S)</DT +>exec (S)</DT ><DD ><P >This is a synonym for <A HREF="#PREEXEC" -> <VAR +> <TT CLASS="PARAMETER" ->preexec</VAR +><I +>preexec</I +></TT ></A >.</P ></DD @@ -7231,7 +8046,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 @@ -7269,7 +8084,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 @@ -7296,9 +8111,11 @@ CLASS="COMMAND" ><P >It is generally much better to use the real <A HREF="#OPLOCKS" -><VAR +><TT CLASS="PARAMETER" ->oplocks</VAR +><I +>oplocks</I +></TT ></A > support rather than this parameter.</P @@ -7320,21 +8137,22 @@ 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 - parameter to <CODE + 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</CODE +>no</TT > prevents any file or directory that is a symbolic link from being followed (the user will get an error). This option is very useful to stop users from adding a @@ -7360,42 +8178,45 @@ 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 permissions changed. The default for this parameter is (in octal) 000. The modes in this parameter are bitwise 'OR'ed onto the file - mode after the mask set in the <VAR + mode after the mask set in the <TT CLASS="PARAMETER" ->create mask</VAR +><I +>create mask</I +></TT > parameter is applied.</P ><P >See also the parameter <A HREF="#CREATEMASK" -><VAR +><TT CLASS="PARAMETER" +><I >create - mask</VAR + mask</I +></TT ></A > for details on masking mode bits on files.</P ><P >See also the <A HREF="#INHERITPERMISSIONS" -><VAR +><TT CLASS="PARAMETER" +><I >inherit - permissions</VAR + permissions</I +></TT ></A > parameter.</P ><P @@ -7417,41 +8238,44 @@ 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 parameter is (in octal) 0000 which will not add any extra permission bits to a created directory. This operation is done after the mode - mask in the parameter <VAR + mask in the parameter <TT CLASS="PARAMETER" ->directory mask</VAR +><I +>directory mask</I +></TT > is applied.</P ><P >See also the parameter <A HREF="#DIRECTORYMASK" -><VAR +><TT CLASS="PARAMETER" -> directory mask</VAR +><I +> directory mask</I +></TT ></A > for details on masking mode bits on created directories.</P ><P >See also the <A HREF="#INHERITPERMISSIONS" -><VAR +><TT CLASS="PARAMETER" -> inherit permissions</VAR +><I +> inherit permissions</I +></TT ></A > parameter.</P ><P @@ -7473,7 +8297,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 @@ -7490,12 +8314,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. @@ -7504,23 +8325,29 @@ CLASS="EMPHASIS" ><P >See also the <A HREF="#DIRECTORYSECURITYMASK" -><VAR +><TT CLASS="PARAMETER" -> directory security mask</VAR +><I +> directory security mask</I +></TT ></A >, <A HREF="#SECURITYMASK" -> <VAR +> <TT CLASS="PARAMETER" ->security mask</VAR +><I +>security mask</I +></TT ></A >, <A HREF="#FORCESECURITYMODE" -><VAR +><TT CLASS="PARAMETER" +><I >force security mode - </VAR + </I +></TT ></A > parameters.</P ><P @@ -7538,7 +8365,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 @@ -7567,36 +8394,41 @@ CLASS="FILENAME" ><P >If the <A HREF="#FORCEUSER" -><VAR +><TT CLASS="PARAMETER" +><I >force user - </VAR + </I +></TT ></A > parameter is also set the group specified in - <VAR + <TT CLASS="PARAMETER" ->force group</VAR +><I +>force group</I +></TT > will override the primary group - set in <VAR + set in <TT CLASS="PARAMETER" ->force user</VAR +><I +>force user</I +></TT >.</P ><P >See also <A HREF="#FORCEUSER" -><VAR +><TT CLASS="PARAMETER" +><I >force - user</VAR + user</I +></TT ></A >.</P ><P ->Default: <SPAN -CLASS="emphasis" -><I +>Default: <I CLASS="EMPHASIS" >no forced group</I -></SPAN ></P ><P >Example: <B @@ -7608,7 +8440,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 @@ -7626,12 +8458,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. @@ -7640,23 +8469,29 @@ CLASS="EMPHASIS" ><P >See also the <A HREF="#FORCEDIRECTORYSECURITYMODE" -><VAR +><TT CLASS="PARAMETER" -> force directory security mode</VAR +><I +> force directory security mode</I +></TT ></A >, <A HREF="#DIRECTORYSECURITYMASK" -><VAR +><TT CLASS="PARAMETER" +><I >directory security - mask</VAR + mask</I +></TT ></A >, <A HREF="#SECURITYMASK" -><VAR +><TT CLASS="PARAMETER" -> security mask</VAR +><I +> security mask</I +></TT ></A > parameters.</P ><P @@ -7674,7 +8509,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 @@ -7695,19 +8530,18 @@ NAME="FORCEUSER" ><P >See also <A HREF="#FORCEGROUP" -><VAR +><TT CLASS="PARAMETER" +><I >force group - </VAR + </I +></TT ></A ></P ><P ->Default: <SPAN -CLASS="emphasis" -><I +>Default: <I CLASS="EMPHASIS" >no forced user</I -></SPAN ></P ><P >Example: <B @@ -7719,30 +8553,32 @@ 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 <CODE + for a share. The default type is <TT CLASS="CONSTANT" ->NTFS</CODE +>NTFS</TT > for compatibility with Windows NT but this can be changed to other - strings such as <CODE + strings such as <TT CLASS="CONSTANT" ->Samba</CODE -> or <CODE +>Samba</TT +> or <TT CLASS="CONSTANT" >FAT - </CODE + </TT > if required.</P ><P >Default: <B @@ -7759,7 +8595,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 @@ -7767,14 +8603,16 @@ NAME="GETWDCACHE" calls. This can have a significant impact on performance, especially when the <A HREF="#WIDELINKS" -><VAR +><TT CLASS="PARAMETER" ->wide links</VAR +><I +>wide links</I +></TT > </A ->parameter is set to <CODE +>parameter is set to <TT CLASS="CONSTANT" ->no</CODE +>no</TT >.</P ><P >Default: <B @@ -7786,15 +8624,17 @@ CLASS="COMMAND" ><A NAME="GROUP" ></A ->>group (S)</DT +>group (S)</DT ><DD ><P >Synonym for <A HREF="#FORCEGROUP" -><VAR +><TT CLASS="PARAMETER" +><I >force - group</VAR + group</I +></TT ></A >.</P ></DD @@ -7802,15 +8642,17 @@ 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 to services which are specified as <A HREF="#GUESTOK" -><VAR +><TT CLASS="PARAMETER" -> guest ok</VAR +><I +> guest ok</I +></TT ></A > (see below). Whatever privileges this user has will be available to any client connecting to the guest service. @@ -7838,13 +8680,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 @@ -7856,37 +8695,31 @@ CLASS="COMMAND" ><A NAME="GUESTOK" ></A ->>guest ok (S)</DT +>guest ok (S)</DT ><DD ><P ->If this parameter is <CODE +>If this parameter is <TT CLASS="CONSTANT" ->yes</CODE +>yes</TT > for a service, then no password is required to connect to the service. Privileges will be those of the <A HREF="#GUESTACCOUNT" -><VAR +><TT CLASS="PARAMETER" -> guest account</VAR +><I +> guest account</I +></TT ></A >.</P ><P ->This paramater nullifies the benifits of setting - <A -HREF="#RESTRICTANONYMOUS" -><VAR -CLASS="PARAMETER" ->restrict - anonymous</VAR -></A -> = 2</P -><P >See the section below on <A HREF="#SECURITY" -><VAR +><TT CLASS="PARAMETER" -> security</VAR +><I +> security</I +></TT ></A > for more information about this option. </P @@ -7900,27 +8733,31 @@ CLASS="COMMAND" ><A NAME="GUESTONLY" ></A ->>guest only (S)</DT +>guest only (S)</DT ><DD ><P ->If this parameter is <CODE +>If this parameter is <TT CLASS="CONSTANT" ->yes</CODE +>yes</TT > for a service, then only guest connections to the service are permitted. This parameter will have no effect if <A HREF="#GUESTOK" -> <VAR +> <TT CLASS="PARAMETER" ->guest ok</VAR +><I +>guest ok</I +></TT ></A > is not set for the service.</P ><P >See the section below on <A HREF="#SECURITY" -><VAR +><TT CLASS="PARAMETER" -> security</VAR +><I +> security</I +></TT ></A > for more information about this option. </P @@ -7934,7 +8771,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 @@ -7949,7 +8786,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 @@ -7973,31 +8810,34 @@ NAME="HIDEFILES" ><P >See also <A HREF="#HIDEDOTFILES" -><VAR +><TT CLASS="PARAMETER" +><I >hide - dot files</VAR + dot files</I +></TT ></A >, <A HREF="#VETOFILES" -><VAR +><TT CLASS="PARAMETER" -> veto files</VAR +><I +> veto files</I +></TT ></A > and <A HREF="#CASESENSITIVE" -> <VAR +> <TT CLASS="PARAMETER" ->case sensitive</VAR +><I +>case sensitive</I +></TT ></A >.</P ><P ->Default: <SPAN -CLASS="emphasis" -><I +>Default: <I CLASS="EMPHASIS" >no file are hidden</I -></SPAN ></P ><P >Example: <B @@ -8019,7 +8859,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 @@ -8034,7 +8874,7 @@ CLASS="COMMAND" ><A NAME="HIDEUNREADABLE" ></A ->>hide unreadable (G)</DT +>hide unreadable (G)</DT ><DD ><P >This parameter prevents clients from seeing the @@ -8049,7 +8889,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 @@ -8066,7 +8906,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 @@ -8083,29 +8923,34 @@ CLASS="COMMAND" ><A NAME="HOMEDIRMAP" ></A ->>homedir map (G)</DT +>homedir map (G)</DT ><DD ><P >If<A HREF="#NISHOMEDIR" -><VAR +><TT CLASS="PARAMETER" +><I >nis homedir - </VAR + </I +></TT ></A -> is <CODE +> is <TT CLASS="CONSTANT" ->yes</CODE ->, and <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbd</SPAN ->(8)</SPAN +>yes</TT +>, and <A +HREF="smbd.8.html" +TARGET="_top" +><B +CLASS="COMMAND" +>smbd(8)</B +></A > is also acting - as a Win95/98 <VAR + as a Win95/98 <TT CLASS="PARAMETER" ->logon server</VAR +><I +>logon server</I +></TT > then this parameter specifies the NIS (or YP) map from which the server for the user's home directory should be extracted. At present, only the Sun @@ -8120,46 +8965,29 @@ CLASS="COMMAND" the first ':'. There should probably be a better parsing system that copes with different map formats and also Amd (another automounter) maps.</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 +CLASS="EMPHASIS" +>NOTE :</I >A working NIS client is required on the system for this option to work.</P -></TD -></TR -></TABLE -></DIV ><P >See also <A HREF="#NISHOMEDIR" -><VAR +><TT CLASS="PARAMETER" ->nis homedir</VAR +><I +>nis homedir</I +></TT > </A >, <A HREF="#DOMAINLOGONS" -><VAR +><TT CLASS="PARAMETER" ->domain logons</VAR +><I +>domain logons</I +></TT > </A >.</P @@ -8178,25 +9006,27 @@ CLASS="COMMAND" ><A NAME="HOSTMSDFS" ></A ->>host msdfs (G)</DT +>host msdfs (G)</DT ><DD ><P >This boolean parameter is only available if Samba has been configured and compiled with the <B CLASS="COMMAND" > --with-msdfs</B -> option. If set to <CODE +> option. If set to <TT CLASS="CONSTANT" ->yes</CODE +>yes</TT >, Samba will act as a Dfs server, and allow Dfs-aware clients to browse Dfs trees hosted on the server.</P ><P >See also the <A HREF="#MSDFSROOT" -><VAR +><TT CLASS="PARAMETER" -> msdfs root</VAR +><I +> msdfs root</I +></TT ></A > share level parameter. For more information on setting up a Dfs tree on Samba, @@ -8216,7 +9046,7 @@ CLASS="COMMAND" ><A NAME="HOSTNAMELOOKUPS" ></A ->>hostname lookups (G)</DT +>hostname lookups (G)</DT ><DD ><P >Specifies whether samba should use (expensive) @@ -8245,13 +9075,15 @@ CLASS="COMMAND" ><A NAME="HOSTSALLOW" ></A ->>hosts allow (S)</DT +>hosts allow (S)</DT ><DD ><P ->A synonym for this parameter is <VAR +>A synonym for this parameter is <TT CLASS="PARAMETER" +><I >allow - hosts</VAR + hosts</I +></TT >.</P ><P >This parameter is a comma, space, or tab delimited @@ -8278,20 +9110,19 @@ CLASS="FILENAME" >Note that the localhost address 127.0.0.1 will always be allowed access unless specifically denied by a <A HREF="#HOSTSDENY" -><VAR +><TT CLASS="PARAMETER" ->hosts deny</VAR +><I +>hosts deny</I +></TT ></A > option.</P ><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 @@ -8331,22 +9162,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 @@ -8359,34 +9189,32 @@ CLASS="COMMAND" ><A NAME="HOSTSDENY" ></A ->>hosts deny (S)</DT +>hosts deny (S)</DT ><DD ><P ->The opposite of <VAR +>The opposite of <TT CLASS="PARAMETER" ->hosts allow</VAR -> - - hosts listed here are <SPAN -CLASS="emphasis" ><I +>hosts allow</I +></TT +> + - 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 <VAR + this one. Where the lists conflict, the <TT CLASS="PARAMETER" ->allow</VAR +><I +>allow</I +></TT > 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 @@ -8399,7 +9227,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, @@ -8409,68 +9237,49 @@ NAME="HOSTSEQUIV" ><P >This is not be confused with <A HREF="#HOSTSALLOW" -> <VAR +> <TT CLASS="PARAMETER" ->hosts allow</VAR +><I +>hosts allow</I +></TT ></A > which is about hosts - access to services and is more useful for guest services. <VAR + access to services and is more useful for guest services. <TT CLASS="PARAMETER" -> hosts equiv</VAR +><I +> hosts equiv</I +></TT > may be useful for NT clients which will not supply passwords to Samba.</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 ->The use of <VAR +><I +CLASS="EMPHASIS" +>NOTE :</I +> The use of <TT CLASS="PARAMETER" +><I >hosts equiv - </VAR + </I +></TT > can be a major security hole. This is because you are trusting the PC to supply the correct username. It is very easy to get a PC to supply a false username. I recommend that the - <VAR + <TT CLASS="PARAMETER" ->hosts equiv</VAR +><I +>hosts equiv</I +></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 -></TD -></TR -></TABLE -></DIV ><P ->Default: <SPAN -CLASS="emphasis" -><I +>Default: <I CLASS="EMPHASIS" >no host equivalences</I -></SPAN ></P ><P >Example: <B @@ -8482,32 +9291,35 @@ CLASS="COMMAND" ><A NAME="INCLUDE" ></A ->>include (G)</DT +>include (G)</DT ><DD ><P >This allows you to include one config file inside another. The file is included literally, as though typed in place.</P ><P ->It takes the standard substitutions, except <VAR +>It takes the standard substitutions, except <TT CLASS="PARAMETER" +><I >%u - </VAR ->, <VAR + </I +></TT +>, <TT CLASS="PARAMETER" ->%P</VAR -> and <VAR +><I +>%P</I +></TT +> and <TT CLASS="PARAMETER" ->%S</VAR +><I +>%S</I +></TT >. </P ><P ->Default: <SPAN -CLASS="emphasis" -><I +>Default: <I CLASS="EMPHASIS" >no file included</I -></SPAN ></P ><P >Example: <B @@ -8520,7 +9332,7 @@ CLASS="COMMAND" ><A NAME="INHERITACLS" ></A ->>inherit acls (S)</DT +>inherit acls (S)</DT ><DD ><P >This parameter can be used to ensure @@ -8542,35 +9354,43 @@ CLASS="COMMAND" ><A NAME="INHERITPERMISSIONS" ></A ->>inherit permissions (S)</DT +>inherit permissions (S)</DT ><DD ><P >The permissions on new files and directories are normally governed by <A HREF="#CREATEMASK" -><VAR +><TT CLASS="PARAMETER" -> create mask</VAR +><I +> create mask</I +></TT ></A >, <A HREF="#DIRECTORYMASK" -> <VAR +> <TT CLASS="PARAMETER" ->directory mask</VAR +><I +>directory mask</I +></TT ></A >, <A HREF="#FORCECREATEMODE" -><VAR +><TT CLASS="PARAMETER" ->force create mode</VAR +><I +>force create mode</I +></TT > </A > and <A HREF="#FORCEDIRECTORYMODE" -><VAR +><TT CLASS="PARAMETER" +><I >force - directory mode</VAR + directory mode</I +></TT ></A > but the boolean inherit permissions parameter overrides this.</P @@ -8582,33 +9402,36 @@ CLASS="PARAMETER" directory. Their execute bits continue to be determined by <A HREF="#MAPARCHIVE" -><VAR +><TT CLASS="PARAMETER" ->map archive</VAR +><I +>map archive</I +></TT > </A >, <A HREF="#MAPHIDDEN" -><VAR +><TT CLASS="PARAMETER" ->map hidden</VAR +><I +>map hidden</I +></TT > </A > and <A HREF="#MAPSYSTEM" -><VAR +><TT CLASS="PARAMETER" ->map system</VAR +><I +>map system</I +></TT > </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 @@ -8618,28 +9441,36 @@ CLASS="EMPHASIS" ><P >See also <A HREF="#CREATEMASK" -><VAR +><TT CLASS="PARAMETER" +><I >create mask - </VAR + </I +></TT ></A >, <A HREF="#DIRECTORYMASK" -><VAR +><TT CLASS="PARAMETER" -> directory mask</VAR +><I +> directory mask</I +></TT ></A >, <A HREF="#FORCECREATEMODE" -> <VAR +> <TT CLASS="PARAMETER" ->force create mode</VAR +><I +>force create mode</I +></TT ></A > and <A HREF="#FORCEDIRECTORYMODE" -><VAR +><TT CLASS="PARAMETER" ->force directory mode</VAR +><I +>force directory mode</I +></TT > </A >.</P @@ -8653,7 +9484,7 @@ CLASS="COMMAND" ><A NAME="INTERFACES" ></A ->>interfaces (G)</DT +>interfaces (G)</DT ><DD ><P >This option allows you to override the default @@ -8711,36 +9542,32 @@ CLASS="COMMAND" ><P >See also <A HREF="#BINDINTERFACESONLY" -><VAR +><TT CLASS="PARAMETER" +><I >bind - interfaces only</VAR + interfaces only</I +></TT ></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 @@ -8754,39 +9581,44 @@ CLASS="EMPHASIS" '&' 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 - so the value <VAR + so the value <TT CLASS="PARAMETER" ->+&group</VAR +><I +>+&group</I +></TT > means check the UNIX group database, followed by the NIS netgroup database, and - the value <VAR + the value <TT CLASS="PARAMETER" ->&+group</VAR +><I +>&+group</I +></TT > means check the NIS netgroup database, followed by the UNIX group database (the same as the '@' prefix).</P ><P ->The current servicename is substituted for <VAR +>The current servicename is substituted for <TT CLASS="PARAMETER" ->%S</VAR +><I +>%S</I +></TT >. This is useful in the [homes] section.</P ><P >See also <A HREF="#VALIDUSERS" -><VAR +><TT CLASS="PARAMETER" +><I >valid users - </VAR + </I +></TT ></A >.</P ><P ->Default: <SPAN -CLASS="emphasis" -><I +>Default: <I CLASS="EMPHASIS" >no invalid users</I -></SPAN ></P ><P >Example: <B @@ -8799,13 +9631,15 @@ CLASS="COMMAND" ><A NAME="KEEPALIVE" ></A ->>keepalive (G)</DT +>keepalive (G)</DT ><DD ><P >The value of the parameter (an integer) represents - the number of seconds between <VAR + the number of seconds between <TT CLASS="PARAMETER" ->keepalive</VAR +><I +>keepalive</I +></TT > packets. If this parameter is zero, no keepalive packets will be sent. Keepalive packets, if sent, allow the server to tell whether @@ -8814,9 +9648,11 @@ CLASS="PARAMETER" >Keepalives should, in general, not be needed if the socket being used has the SO_KEEPALIVE attribute set on it (see <A HREF="#SOCKETOPTIONS" -><VAR +><TT CLASS="PARAMETER" ->socket options</VAR +><I +>socket options</I +></TT ></A >). Basically you should only use this option if you strike difficulties.</P @@ -8835,60 +9671,67 @@ CLASS="COMMAND" ><A NAME="KERNELOPLOCKS" ></A ->>kernel oplocks (G)</DT +>kernel oplocks (G)</DT ><DD ><P >For UNIXes that support kernel based <A HREF="#OPLOCKS" -><VAR +><TT CLASS="PARAMETER" ->oplocks</VAR +><I +>oplocks</I +></TT ></A > (currently only IRIX and the Linux 2.4 kernel), this parameter allows the use of them to be turned on or off.</P ><P ->Kernel oplocks support allows Samba <VAR +>Kernel oplocks support allows Samba <TT CLASS="PARAMETER" +><I >oplocks - </VAR + </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 <CODE +>This parameter defaults to <TT CLASS="CONSTANT" ->on</CODE +>on</TT >, but is translated to a no-op on systems that no not have the necessary kernel support. You should never need to touch this parameter.</P ><P >See also the <A HREF="#OPLOCKS" -><VAR +><TT CLASS="PARAMETER" ->oplocks</VAR +><I +>oplocks</I +></TT > </A > and <A HREF="#LEVEL2OPLOCKS" -><VAR +><TT CLASS="PARAMETER" +><I >level2 oplocks - </VAR + </I +></TT ></A > parameters.</P ><P @@ -8901,19 +9744,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" @@ -8924,17 +9766,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 @@ -8951,37 +9791,43 @@ CLASS="COMMAND" ><A NAME="LDAPADMINDN" ></A ->>ldap admin dn (G)</DT +>ldap admin dn (G)</DT ><DD ><P -> The <VAR +>The <TT CLASS="PARAMETER" ->ldap admin dn</VAR +><I +>ldap admin dn</I +></TT > defines the Distinguished Name (DN) name used by Samba to contact the ldap server when retreiving - user account information. The <VAR + user account information. The <TT CLASS="PARAMETER" +><I >ldap - admin dn</VAR + admin dn</I +></TT > is used in conjunction with the admin dn password stored in the <TT 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.</P + <A +HREF="smbpasswd.8.html" +TARGET="_top" +><B +CLASS="COMMAND" +>smbpasswd(8)</B +></A +> man + page for more information on how to accomplish this. + </P ></DD ><DT ><A NAME="LDAPDELETEDN" ></A ->>ldap delete dn (G)</DT +>>ldap del only sam attr (G)</DT ><DD ><P > This parameter specifies whether a delete @@ -8989,29 +9835,44 @@ NAME="LDAPDELETEDN" specific to Samba. </P ><P ->Default : <SPAN -CLASS="emphasis" -><I +>Default : <I CLASS="EMPHASIS" >ldap delete dn = no</I -></SPAN ></P ></DD ><DT ><A +NAME="LDAPDELONLYSAMATTR" +></A +>>ldap del only sam attr (G)</DT +><DD +><P +> Inverted synonym for <A +HREF="#LDAPDELETEDN" +><TT +CLASS="PARAMETER" +><I +> ldap delete dn</I +></TT +></A +>. + </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. - The default is to match the login name with the <CODE + The default is to match the login name with the <TT CLASS="CONSTANT" ->uid</CODE +>uid</TT > - attribute for all entries matching the <CODE + attribute for all entries matching the <TT CLASS="CONSTANT" ->sambaAccount</CODE +>sambaAccount</TT > objectclass. Note that this filter should only return one entry. </P @@ -9025,7 +9886,7 @@ CLASS="COMMAND" ><A NAME="LDAPPORT" ></A ->>ldap port (G)</DT +>ldap port (G)</DT ><DD ><P >This parameter is only available if Samba has been @@ -9039,9 +9900,11 @@ CLASS="COMMAND" > This option is used to control the tcp port number used to contact the <A HREF="#LDAPSERVER" -><VAR +><TT CLASS="PARAMETER" ->ldap server</VAR +><I +>ldap server</I +></TT ></A >. The default is to use the stand LDAPS port 636. @@ -9067,7 +9930,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 @@ -9091,17 +9954,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 @@ -9114,9 +9974,11 @@ CLASS="FILENAME" script. </P ><P -> The <VAR +> The <TT CLASS="PARAMETER" ->ldap ssl</VAR +><I +>ldap ssl</I +></TT > can be set to one of three values: </P ><P @@ -9124,29 +9986,37 @@ CLASS="PARAMETER" ><UL ><LI ><P -><VAR +><TT CLASS="PARAMETER" ->Off</VAR +><I +>Off</I +></TT > = Never use SSL when querying the directory.</P ></LI ><LI ><P -><VAR +><TT CLASS="PARAMETER" ->Start_tls</VAR +><I +>Start_tls</I +></TT > = Use the LDAPv3 StartTLS extended operation (RFC2830) for communicating with the directory server.</P ></LI ><LI ><P -><VAR +><TT CLASS="PARAMETER" ->On</VAR +><I +>On</I +></TT > = Use SSL on the ldaps port when contacting the - <VAR + <TT CLASS="PARAMETER" ->ldap server</VAR +><I +>ldap server</I +></TT >. Only available when the backwards-compatiblity <B CLASS="COMMAND" @@ -9154,9 +10024,11 @@ CLASS="COMMAND" > option is specified to configure. See <A HREF="#PASSDBBACKEND" -><VAR +><TT CLASS="PARAMETER" ->passdb backend</VAR +><I +>passdb backend</I +></TT ></A ></P ></LI @@ -9171,7 +10043,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 @@ -9182,56 +10054,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 @@ -9241,9 +10104,11 @@ NAME="LDAPPASSWDSYNC" change via SAMBA. </P ><P -> The <VAR +> The <TT CLASS="PARAMETER" ->ldap passwd sync</VAR +><I +>ldap passwd sync</I +></TT > can be set to one of three values: </P ><P @@ -9251,23 +10116,29 @@ CLASS="PARAMETER" ><UL ><LI ><P -><VAR +><TT CLASS="PARAMETER" ->Yes</VAR +><I +>Yes</I +></TT > = Try to update the LDAP, NT and LM passwords and update the pwdLastSet time.</P ></LI ><LI ><P -><VAR +><TT CLASS="PARAMETER" ->No</VAR +><I +>No</I +></TT > = Update NT and LM passwords and update the pwdLastSet time.</P ></LI ><LI ><P -><VAR +><TT CLASS="PARAMETER" ->Only</VAR +><I +>Only</I +></TT > = Only update the LDAP password and let the LDAP server do the rest.</P ></LI ></UL @@ -9281,7 +10152,7 @@ CLASS="COMMAND" ><A NAME="LDAPTRUSTIDS" ></A ->>ldap trust ids (G)</DT +>ldap trust ids (G)</DT ><DD ><P >Normally, Samba validates each entry @@ -9310,7 +10181,7 @@ CLASS="COMMAND" ><A NAME="LEVEL2OPLOCKS" ></A ->>level2 oplocks (S)</DT +>level2 oplocks (S)</DT ><DD ><P >This parameter controls whether Samba supports @@ -9338,41 +10209,49 @@ NAME="LEVEL2OPLOCKS" ><P >Currently, if <A HREF="#KERNELOPLOCKS" -><VAR +><TT CLASS="PARAMETER" +><I >kernel - oplocks</VAR + oplocks</I +></TT ></A > are supported then level2 oplocks are - not granted (even if this parameter is set to <CODE + not granted (even if this parameter is set to <TT CLASS="CONSTANT" ->yes</CODE +>yes</TT >). Note also, the <A HREF="#OPLOCKS" -><VAR +><TT CLASS="PARAMETER" ->oplocks</VAR +><I +>oplocks</I +></TT > </A -> parameter must be set to <CODE +> parameter must be set to <TT CLASS="CONSTANT" ->yes</CODE +>yes</TT > on this share in order for this parameter to have any effect.</P ><P >See also the <A HREF="#OPLOCKS" -><VAR +><TT CLASS="PARAMETER" ->oplocks</VAR +><I +>oplocks</I +></TT > </A > and <A HREF="#OPLOCKS" -><VAR +><TT CLASS="PARAMETER" ->kernel oplocks</VAR +><I +>kernel oplocks</I +></TT > </A > parameters.</P @@ -9386,62 +10265,69 @@ 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 - values, <CODE + values, <TT CLASS="CONSTANT" ->yes</CODE ->, <CODE +>yes</TT +>, <TT CLASS="CONSTANT" ->no</CODE +>no</TT >, or - <CODE + <TT CLASS="CONSTANT" ->auto</CODE ->. The default is <CODE +>auto</TT +>. The default is <TT CLASS="CONSTANT" ->auto</CODE +>auto</TT >. - If set to <CODE + If set to <TT CLASS="CONSTANT" ->no</CODE +>no</TT > Samba will never produce these - broadcasts. If set to <CODE + broadcasts. If set to <TT CLASS="CONSTANT" ->yes</CODE +>yes</TT > Samba will produce Lanman announce broadcasts at a frequency set by the parameter - <VAR + <TT CLASS="PARAMETER" ->lm interval</VAR ->. If set to <CODE +><I +>lm interval</I +></TT +>. If set to <TT CLASS="CONSTANT" ->auto</CODE +>auto</TT > Samba will not send Lanman announce broadcasts by default but will listen for them. If it hears such a broadcast on the wire it will then start sending them at a frequency set by the parameter - <VAR + <TT CLASS="PARAMETER" ->lm interval</VAR +><I +>lm interval</I +></TT >.</P ><P >See also <A HREF="#LMINTERVAL" -><VAR +><TT CLASS="PARAMETER" +><I >lm interval - </VAR + </I +></TT ></A >.</P ><P @@ -9459,31 +10345,37 @@ CLASS="COMMAND" ><A NAME="LMINTERVAL" ></A ->>lm interval (G)</DT +>lm interval (G)</DT ><DD ><P >If Samba is set to produce Lanman announce broadcasts needed by OS/2 clients (see the <A HREF="#LMANNOUNCE" -> <VAR +> <TT CLASS="PARAMETER" ->lm announce</VAR +><I +>lm announce</I +></TT ></A > parameter) then this parameter defines the frequency in seconds with which they will be made. If this is set to zero then no Lanman announcements will be - made despite the setting of the <VAR + made despite the setting of the <TT CLASS="PARAMETER" ->lm announce</VAR +><I +>lm announce</I +></TT > parameter.</P ><P >See also <A HREF="#LMANNOUNCE" -><VAR +><TT CLASS="PARAMETER" +><I >lm - announce</VAR + announce</I +></TT ></A >.</P ><P @@ -9501,13 +10393,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 @@ -9521,62 +10413,54 @@ 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 <CODE + on a subnet. If set to <TT CLASS="CONSTANT" ->no</CODE +>no</TT > then <B CLASS="COMMAND" > nmbd</B > will not attempt to become a local master browser on a subnet and will also lose in all browsing elections. By - default this value is set to <CODE + default this value is set to <TT CLASS="CONSTANT" ->yes</CODE ->. Setting this value to <CODE +>yes</TT +>. Setting this value to <TT CLASS="CONSTANT" ->yes</CODE +>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 <CODE +>Setting this value to <TT CLASS="CONSTANT" ->no</CODE +>no</TT > will cause <B CLASS="COMMAND" >nmbd</B > - <SPAN -CLASS="emphasis" -><I + <I CLASS="EMPHASIS" >never</I -></SPAN > to become a local master browser.</P ><P >Default: <B @@ -9588,14 +10472,16 @@ CLASS="COMMAND" ><A NAME="LOCKDIR" ></A ->>lock dir (G)</DT +>lock dir (G)</DT ><DD ><P >Synonym for <A HREF="#LOCKDIRECTORY" -><VAR +><TT CLASS="PARAMETER" -> lock directory</VAR +><I +> lock directory</I +></TT ></A >.</P ></DD @@ -9603,16 +10489,18 @@ CLASS="PARAMETER" ><A NAME="LOCKDIRECTORY" ></A ->>lock directory (G)</DT +>lock directory (G)</DT ><DD ><P >This option specifies the directory where lock files will be placed. The lock files are used to implement the <A HREF="#MAXCONNECTIONS" -><VAR +><TT CLASS="PARAMETER" ->max connections</VAR +><I +>max connections</I +></TT > </A > option.</P @@ -9632,7 +10520,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 @@ -9655,17 +10543,19 @@ 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 pause before attempting to gain a failed lock. See <A HREF="#LOCKSPINCOUNT" -><VAR +><TT CLASS="PARAMETER" +><I >lock spin - count</VAR + count</I +></TT ></A > for more details. </P @@ -9680,7 +10570,7 @@ CLASS="COMMAND" ><A NAME="LOCKING" ></A ->>locking (S)</DT +>locking (S)</DT ><DD ><P >This controls whether or not locking will be @@ -9700,23 +10590,17 @@ 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 <CODE + CDROM drives), although setting this parameter of <TT CLASS="CONSTANT" ->no</CODE +>no</TT > is not really recommended even in this case.</P ><P @@ -9733,7 +10617,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 @@ -9752,7 +10636,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 @@ -9778,15 +10662,17 @@ CLASS="COMMAND" ><A NAME="LOGONDRIVE" ></A ->>logon drive (G)</DT +>logon drive (G)</DT ><DD ><P >This parameter specifies the local path to which the home directory will be connected (see <A HREF="#LOGONHOME" -><VAR +><TT CLASS="PARAMETER" ->logon home</VAR +><I +>logon home</I +></TT ></A >) and is only used by NT Workstations. </P @@ -9808,19 +10694,21 @@ CLASS="COMMAND" ><A NAME="LOGONHOME" ></A ->>logon home (G)</DT +>logon home (G)</DT ><DD ><P >This parameter specifies the home directory location when a Win95/98 or NT Workstation logs into a Samba PDC. It allows you to do </P ><P -><SAMP +><TT CLASS="PROMPT" ->C:\> </SAMP -><KBD +>C:\> </TT +><TT CLASS="USERINPUT" ->NET USE H: /HOME</KBD +><B +>NET USE H: /HOME</B +></TT > </P ><P @@ -9849,14 +10737,18 @@ CLASS="COMMAND" ><P >Note that in prior versions of Samba, the <A HREF="#LOGONPATH" -> <VAR +> <TT CLASS="PARAMETER" ->logon path</VAR +><I +>logon path</I +></TT ></A > was returned rather than - <VAR + <TT CLASS="PARAMETER" ->logon home</VAR +><I +>logon home</I +></TT >. This broke <B CLASS="COMMAND" >net use @@ -9883,7 +10775,7 @@ CLASS="COMMAND" ><A NAME="LOGONPATH" ></A ->>logon path (G)</DT +>logon path (G)</DT ><DD ><P >This parameter specifies the home directory @@ -9892,9 +10784,11 @@ NAME="LOGONPATH" nothing to do with Win 9X roaming profiles. To find out how to handle roaming profiles for Win 9X system, see the <A HREF="#LOGONHOME" -> <VAR +> <TT CLASS="PARAMETER" ->logon home</VAR +><I +>logon home</I +></TT ></A > parameter.</P ><P @@ -9927,12 +10821,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 @@ -9962,7 +10853,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 @@ -9974,9 +10865,11 @@ NAME="LOGONSCRIPT" >The script must be a relative path to the [netlogon] service. If the [netlogon] service specifies a <A HREF="#PATH" -> <VAR +> <TT CLASS="PARAMETER" ->path</VAR +><I +>path</I +></TT ></A > of <TT CLASS="FILENAME" @@ -10020,12 +10913,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 @@ -10037,7 +10927,7 @@ CLASS="COMMAND" ><A NAME="LPPAUSECOMMAND" ></A ->>lppause command (S)</DT +>lppause command (S)</DT ><DD ><P >This parameter specifies the command to be @@ -10049,21 +10939,29 @@ NAME="LPPAUSECOMMAND" of implementing this is by using job priorities, where jobs having a too low priority won't be sent to the printer.</P ><P ->If a <VAR +>If a <TT CLASS="PARAMETER" ->%p</VAR +><I +>%p</I +></TT > is given then the printer name - is put in its place. A <VAR + is put in its place. A <TT CLASS="PARAMETER" ->%j</VAR +><I +>%j</I +></TT > is replaced with - the job number (an integer). On HPUX (see <VAR + the job number (an integer). On HPUX (see <TT CLASS="PARAMETER" +><I >printing=hpux - </VAR ->), if the <VAR + </I +></TT +>), if the <TT CLASS="PARAMETER" ->-p%p</VAR +><I +>-p%p</I +></TT > option is added to the lpq command, the job will show up with the correct status, i.e. if the job priority is lower than the set fence priority it will @@ -10075,21 +10973,25 @@ CLASS="PARAMETER" ><P >See also the <A HREF="#PRINTING" -><VAR +><TT CLASS="PARAMETER" +><I >printing - </VAR + </I +></TT ></A > parameter.</P ><P >Default: Currently no default value is given to - this string, unless the value of the <VAR + this string, unless the value of the <TT CLASS="PARAMETER" ->printing</VAR +><I +>printing</I +></TT > - parameter is <CODE + parameter is <TT CLASS="CONSTANT" ->SYSV</CODE +>SYSV</TT >, in which case the default is :</P ><P ><B @@ -10097,13 +10999,15 @@ CLASS="COMMAND" >lp -i %p-%j -H hold</B ></P ><P ->or if the value of the <VAR +>or if the value of the <TT CLASS="PARAMETER" ->printing</VAR +><I +>printing</I +></TT > parameter - is <CODE + is <TT CLASS="CONSTANT" ->SOFTQ</CODE +>SOFTQ</TT >, then the default is:</P ><P ><B @@ -10121,7 +11025,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 @@ -10163,10 +11067,12 @@ CLASS="COMMAND" ><P >See also the <A HREF="#PRINTING" -><VAR +><TT CLASS="PARAMETER" +><I >printing - </VAR + </I +></TT ></A > parameter.</P ><P @@ -10184,7 +11090,7 @@ CLASS="COMMAND" ><A NAME="LPQCOMMAND" ></A ->>lpq command (S)</DT +>lpq command (S)</DT ><DD ><P >This parameter specifies the command to be @@ -10201,9 +11107,11 @@ CLASS="COMMAND" >Currently nine styles of printer status information are supported; BSD, AIX, LPRNG, PLP, SYSV, HPUX, QNX, CUPS, and SOFTQ. This covers most UNIX systems. You control which type is expected - using the <VAR + using the <TT CLASS="PARAMETER" ->printing =</VAR +><I +>printing =</I +></TT > option.</P ><P >Some clients (notably Windows for Workgroups) may not @@ -10212,47 +11120,54 @@ CLASS="PARAMETER" server reports on the first printer service connected to by the client. This only happens if the connection number sent is invalid.</P ><P ->If a <VAR +>If a <TT CLASS="PARAMETER" ->%p</VAR +><I +>%p</I +></TT > is given then the printer name is put in its place. Otherwise it is placed at the end of the command.</P ><P >Note that it is good practice to include the absolute path - in the <VAR + in the <TT CLASS="PARAMETER" ->lpq command</VAR -> as the <VAR +><I +>lpq command</I +></TT +> as the <TT CLASS="ENVAR" >$PATH - </VAR + </TT > may not be available to the server. When compiled with - the CUPS libraries, no <VAR + the CUPS libraries, no <TT CLASS="PARAMETER" ->lpq command</VAR +><I +>lpq command</I +></TT > is needed because smbd will make a library call to obtain the print queue listing.</P ><P >See also the <A HREF="#PRINTING" -><VAR +><TT CLASS="PARAMETER" +><I >printing - </VAR + </I +></TT ></A > parameter.</P ><P ->Default: <SPAN -CLASS="emphasis" -><I +>Default: <I CLASS="EMPHASIS" ->depends on the setting of <VAR +>depends on the setting of <TT CLASS="PARAMETER" -> printing</VAR +><I +> printing</I +></TT ></I -></SPAN ></P ><P >Example: <B @@ -10264,7 +11179,7 @@ CLASS="COMMAND" ><A NAME="LPRESUMECOMMAND" ></A ->>lpresume command (S)</DT +>lpresume command (S)</DT ><DD ><P >This parameter specifies the command to be @@ -10275,47 +11190,59 @@ NAME="LPRESUMECOMMAND" a printer name and job number to resume the print job. See also the <A HREF="#LPPAUSECOMMAND" -><VAR +><TT CLASS="PARAMETER" +><I >lppause command - </VAR + </I +></TT ></A > parameter.</P ><P ->If a <VAR +>If a <TT CLASS="PARAMETER" ->%p</VAR +><I +>%p</I +></TT > is given then the printer name - is put in its place. A <VAR + is put in its place. A <TT CLASS="PARAMETER" ->%j</VAR +><I +>%j</I +></TT > is replaced with the job number (an integer).</P ><P >Note that it is good practice to include the absolute path - in the <VAR + in the <TT CLASS="PARAMETER" ->lpresume command</VAR +><I +>lpresume command</I +></TT > as the PATH may not be available to the server.</P ><P >See also the <A HREF="#PRINTING" -><VAR +><TT CLASS="PARAMETER" +><I >printing - </VAR + </I +></TT ></A > parameter.</P ><P >Default: Currently no default value is given - to this string, unless the value of the <VAR + to this string, unless the value of the <TT CLASS="PARAMETER" ->printing</VAR +><I +>printing</I +></TT > - parameter is <CODE + parameter is <TT CLASS="CONSTANT" ->SYSV</CODE +>SYSV</TT >, in which case the default is :</P ><P ><B @@ -10323,13 +11250,15 @@ CLASS="COMMAND" >lp -i %p-%j -H resume</B ></P ><P ->or if the value of the <VAR +>or if the value of the <TT CLASS="PARAMETER" ->printing</VAR +><I +>printing</I +></TT > parameter - is <CODE + is <TT CLASS="CONSTANT" ->SOFTQ</CODE +>SOFTQ</TT >, then the default is:</P ><P ><B @@ -10347,7 +11276,7 @@ CLASS="COMMAND" ><A NAME="LPRMCOMMAND" ></A ->>lprm command (S)</DT +>lprm command (S)</DT ><DD ><P >This parameter specifies the command to be @@ -10356,42 +11285,49 @@ NAME="LPRMCOMMAND" >This command should be a program or script which takes a printer name and job number, and deletes the print job.</P ><P ->If a <VAR +>If a <TT CLASS="PARAMETER" ->%p</VAR +><I +>%p</I +></TT > is given then the printer name - is put in its place. A <VAR + is put in its place. A <TT CLASS="PARAMETER" ->%j</VAR +><I +>%j</I +></TT > is replaced with the job number (an integer).</P ><P >Note that it is good practice to include the absolute - path in the <VAR + path in the <TT CLASS="PARAMETER" ->lprm command</VAR +><I +>lprm command</I +></TT > as the PATH may not be available to the server.</P ><P >See also the <A HREF="#PRINTING" -><VAR +><TT CLASS="PARAMETER" +><I >printing - </VAR + </I +></TT ></A > parameter.</P ><P ->Default: <SPAN -CLASS="emphasis" -><I +>Default: <I CLASS="EMPHASIS" ->depends on the setting of <VAR +>depends on the setting of <TT CLASS="PARAMETER" +><I >printing - </VAR + </I +></TT ></I -></SPAN ></P ><P >Example 1: <B @@ -10410,7 +11346,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 @@ -10431,12 +11367,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 @@ -10451,24 +11389,28 @@ CLASS="COMMAND" ><A NAME="MAGICOUTPUT" ></A ->>magic output (S)</DT +>magic output (S)</DT ><DD ><P >This parameter specifies the name of a file which will contain output created by a magic script (see the <A HREF="#MAGICSCRIPT" -><VAR +><TT CLASS="PARAMETER" ->magic script</VAR +><I +>magic script</I +></TT ></A > parameter below).</P ><P ->Warning: If two clients use the same <VAR +>Warning: If two clients use the same <TT CLASS="PARAMETER" +><I >magic script - </VAR + </I +></TT > in the same directory the output file content is undefined.</P ><P @@ -10487,7 +11429,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, @@ -10502,45 +11444,35 @@ NAME="MAGICSCRIPT" >If the script generates output, output will be sent to the file specified by the <A HREF="#MAGICOUTPUT" -><VAR +><TT CLASS="PARAMETER" -> magic output</VAR +><I +> magic output</I +></TT ></A > parameter (see above).</P ><P >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 @@ -10552,11 +11484,11 @@ CLASS="COMMAND" ><A NAME="MANGLECASE" ></A ->>mangle case (S)</DT +>mangle case (S)</DT ><DD ><P >See the section on <A -HREF="#AEN207" +HREF="#AEN205" > NAME MANGLING</A ></P ><P @@ -10569,7 +11501,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 @@ -10607,12 +11539,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 @@ -10624,7 +11553,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 @@ -10632,7 +11561,7 @@ NAME="MANGLEDNAMES" or whether non-DOS names should simply be ignored.</P ><P >See the section on <A -HREF="#AEN207" +HREF="#AEN205" > NAME MANGLING</A > for details on how to control the mangling process.</P ><P @@ -10659,9 +11588,11 @@ HREF="#AEN207" >Note that the character to use may be specified using the <A HREF="#MANGLINGCHAR" -><VAR +><TT CLASS="PARAMETER" ->mangling char</VAR +><I +>mangling char</I +></TT > </A > option, if you don't like '~'.</P @@ -10707,7 +11638,7 @@ CLASS="COMMAND" ><A NAME="MANGLINGMETHOD" ></A ->>mangling method (G)</DT +>mangling method (G)</DT ><DD ><P > controls the algorithm used for the generating @@ -10733,7 +11664,7 @@ CLASS="COMMAND" ><A NAME="MANGLEPREFIX" ></A ->>mangle prefix (G)</DT +>mangle prefix (G)</DT ><DD ><P > controls the number of prefix @@ -10756,16 +11687,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 @@ -10795,18 +11724,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="#AEN207" +HREF="#AEN205" >name mangling</A >. The default is a '~' but this may interfere with some software. Use this option to set @@ -10826,7 +11752,7 @@ CLASS="COMMAND" ><A NAME="MAPARCHIVE" ></A ->>map archive (S)</DT +>map archive (S)</DT ><DD ><P >This controls whether the DOS archive attribute @@ -10836,16 +11762,20 @@ NAME="MAPARCHIVE" any file it touches from becoming executable under UNIX. This can be quite annoying for shared source code, documents, etc...</P ><P ->Note that this requires the <VAR +>Note that this requires the <TT CLASS="PARAMETER" ->create mask</VAR +><I +>create mask</I +></TT > parameter to be set such that owner execute bit is not masked out (i.e. it must include 100). See the parameter <A HREF="#CREATEMASK" -> <VAR +> <TT CLASS="PARAMETER" ->create mask</VAR +><I +>create mask</I +></TT ></A > for details.</P ><P @@ -10858,22 +11788,26 @@ CLASS="COMMAND" ><A NAME="MAPHIDDEN" ></A ->>map hidden (S)</DT +>map hidden (S)</DT ><DD ><P >This controls whether DOS style hidden files should be mapped to the UNIX world execute bit.</P ><P ->Note that this requires the <VAR +>Note that this requires the <TT CLASS="PARAMETER" ->create mask</VAR +><I +>create mask</I +></TT > to be set such that the world execute bit is not masked out (i.e. it must include 001). See the parameter <A HREF="#CREATEMASK" -> <VAR +> <TT CLASS="PARAMETER" ->create mask</VAR +><I +>create mask</I +></TT ></A > for details.</P ><P @@ -10886,22 +11820,26 @@ CLASS="COMMAND" ><A NAME="MAPSYSTEM" ></A ->>map system (S)</DT +>map system (S)</DT ><DD ><P >This controls whether DOS style system files should be mapped to the UNIX group execute bit.</P ><P ->Note that this requires the <VAR +>Note that this requires the <TT CLASS="PARAMETER" ->create mask</VAR +><I +>create mask</I +></TT > to be set such that the group execute bit is not masked out (i.e. it must include 010). See the parameter <A HREF="#CREATEMASK" -> <VAR +> <TT CLASS="PARAMETER" ->create mask</VAR +><I +>create mask</I +></TT ></A > for details.</P ><P @@ -10914,35 +11852,35 @@ 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 HREF="#SECURITY" > security</A -> modes other than <VAR +> modes other than <TT CLASS="PARAMETER" ->security = share</VAR +><I +>security = share</I +></TT > - - i.e. <CODE + - i.e. <TT CLASS="CONSTANT" ->user</CODE ->, <CODE +>user</TT +>, <TT CLASS="CONSTANT" ->server</CODE +>server</TT >, - and <CODE + and <TT CLASS="CONSTANT" ->domain</CODE +>domain</TT >.</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 @@ -10952,34 +11890,36 @@ CLASS="REFENTRYTITLE" ><UL ><LI ><P -><CODE +><TT CLASS="CONSTANT" ->Never</CODE +>Never</TT > - Means user login requests with an invalid password are rejected. This is the default.</P ></LI ><LI ><P -><CODE +><TT CLASS="CONSTANT" ->Bad User</CODE +>Bad User</TT > - Means user logins with an invalid password are rejected, unless the username does not exist, in which case it is treated as a guest login and mapped into the <A HREF="#GUESTACCOUNT" -><VAR +><TT CLASS="PARAMETER" -> guest account</VAR +><I +> guest account</I +></TT ></A >.</P ></LI ><LI ><P -><CODE +><TT CLASS="CONSTANT" ->Bad Password</CODE +>Bad Password</TT > - Means user logins with an invalid password are treated as a guest login and mapped into the <A @@ -10991,41 +11931,39 @@ 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 <VAR +> you if you set the <TT CLASS="PARAMETER" +><I >map to - guest</VAR + guest</I +></TT > parameter this way :-).</P ></LI ></UL ><P >Note that this parameter is needed to set up "Guest" - share services when using <VAR + share services when using <TT CLASS="PARAMETER" ->security</VAR +><I +>security</I +></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 to the share) for "Guest" shares.</P ><P >For people familiar with the older Samba releases, this - parameter maps to the old compile-time setting of the <CODE + parameter maps to the old compile-time setting of the <TT CLASS="CONSTANT" -> GUEST_SESSSETUP</CODE +> GUEST_SESSSETUP</TT > value in local.h.</P ><P >Default: <B @@ -11042,14 +11980,16 @@ CLASS="COMMAND" ><A NAME="MAXCONNECTIONS" ></A ->>max connections (S)</DT +>max connections (S)</DT ><DD ><P >This option allows the number of simultaneous - connections to a service to be limited. If <VAR + connections to a service to be limited. If <TT CLASS="PARAMETER" +><I >max connections - </VAR + </I +></TT > is greater than 0 then connections will be refused if this number of connections to the service are already open. A value of zero mean an unlimited number of connections may be made.</P @@ -11057,9 +11997,11 @@ CLASS="PARAMETER" >Record lock files are used to implement this feature. The lock files will be stored in the directory specified by the <A HREF="#LOCKDIRECTORY" -><VAR +><TT CLASS="PARAMETER" ->lock directory</VAR +><I +>lock directory</I +></TT ></A > option.</P @@ -11078,7 +12020,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 @@ -11090,19 +12032,23 @@ NAME="MAXDISKSIZE" data you can put on the disk. In the above case you could still store much more than 100 MB on the disk, but if a client ever asks for the amount of free disk space or the total disk size then the - result will be bounded by the amount specified in <VAR + result will be bounded by the amount specified in <TT CLASS="PARAMETER" +><I >max - disk size</VAR + disk size</I +></TT >.</P ><P >This option is primarily useful to work around bugs in some pieces of software that can't handle very large disks, particularly disks over 1GB in size.</P ><P ->A <VAR +>A <TT CLASS="PARAMETER" ->max disk size</VAR +><I +>max disk size</I +></TT > of 0 means no limit.</P ><P >Default: <B @@ -11119,7 +12065,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 @@ -11146,7 +12092,7 @@ CLASS="COMMAND" ><A NAME="MAXMUX" ></A ->>max mux (G)</DT +>max mux (G)</DT ><DD ><P >This option controls the maximum number of @@ -11162,16 +12108,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 @@ -11190,24 +12134,27 @@ 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" -><VAR +><TT CLASS="PARAMETER" +><I >total - print jobs</VAR + print jobs</I +></TT ></A >. </P @@ -11226,7 +12173,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 @@ -11238,47 +12185,44 @@ NAME="MAXPROTOCOL" ><UL ><LI ><P -><CODE +><TT CLASS="CONSTANT" ->CORE</CODE +>CORE</TT >: Earliest version. No concept of user names.</P ></LI ><LI ><P -><CODE +><TT CLASS="CONSTANT" ->COREPLUS</CODE +>COREPLUS</TT >: Slight improvements on CORE for efficiency.</P ></LI ><LI ><P -><CODE +><TT CLASS="CONSTANT" ->LANMAN1</CODE ->: First <SPAN -CLASS="emphasis" -><I +>LANMAN1</TT +>: First <I CLASS="EMPHASIS" > modern</I -></SPAN > version of the protocol. Long filename support.</P ></LI ><LI ><P -><CODE +><TT CLASS="CONSTANT" ->LANMAN2</CODE +>LANMAN2</TT >: Updates to Lanman1 protocol. </P ></LI ><LI ><P -><CODE +><TT CLASS="CONSTANT" ->NT1</CODE +>NT1</TT >: Current up to date version of the protocol. Used by Windows NT. Known as CIFS.</P ></LI @@ -11290,10 +12234,12 @@ CLASS="CONSTANT" ><P >See also <A HREF="#MINPROTOCOL" -><VAR +><TT CLASS="PARAMETER" +><I >min - protocol</VAR + protocol</I +></TT ></A ></P ><P @@ -11311,7 +12257,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 @@ -11327,12 +12273,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 @@ -11351,15 +12295,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 @@ -11378,20 +12320,21 @@ 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" -> <VAR +> <TT CLASS="PARAMETER" ->wins support = yes</VAR +><I +>wins support = yes</I +></TT ></A >) what the maximum 'time to live' of NetBIOS names that <B @@ -11403,10 +12346,12 @@ CLASS="COMMAND" ><P >See also the <A HREF="#MINWINSTTL" -><VAR +><TT CLASS="PARAMETER" +><I >min - wins ttl</VAR + wins ttl</I +></TT ></A > parameter.</P ><P @@ -11419,7 +12364,7 @@ CLASS="COMMAND" ><A NAME="MAXXMIT" ></A ->>max xmit (G)</DT +>max xmit (G)</DT ><DD ><P >This option controls the maximum packet size @@ -11442,7 +12387,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 @@ -11464,25 +12409,26 @@ 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 your PCs may freeze when sending messages (they should recover after 30 seconds, hopefully).</P ><P >All messages are delivered as the global guest user. - The command takes the standard substitutions, although <VAR + The command takes the standard substitutions, although <TT CLASS="PARAMETER" -> %u</VAR -> won't work (<VAR +><I +> %u</I +></TT +> won't work (<TT CLASS="PARAMETER" ->%U</VAR +><I +>%U</I +></TT > may be better in this case).</P ><P @@ -11493,25 +12439,31 @@ CLASS="PARAMETER" ><UL ><LI ><P -><VAR +><TT CLASS="PARAMETER" ->%s</VAR +><I +>%s</I +></TT > = the filename containing the message.</P ></LI ><LI ><P -><VAR +><TT CLASS="PARAMETER" ->%t</VAR +><I +>%t</I +></TT > = the destination that the message was sent to (probably the server name).</P ></LI ><LI ><P -><VAR +><TT CLASS="PARAMETER" ->%f</VAR +><I +>%f</I +></TT > = who the message is from.</P ></LI @@ -11542,12 +12494,9 @@ 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 @@ -11560,14 +12509,16 @@ CLASS="COMMAND" ><A NAME="MINPASSWDLENGTH" ></A ->>min passwd length (G)</DT +>min passwd length (G)</DT ><DD ><P >Synonym for <A HREF="#MINPASSWORDLENGTH" -> <VAR +> <TT CLASS="PARAMETER" ->min password length</VAR +><I +>min password length</I +></TT ></A >.</P ></DD @@ -11575,7 +12526,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 @@ -11587,22 +12538,28 @@ CLASS="COMMAND" ><P >See also <A HREF="#UNIXPASSWORDSYNC" -><VAR +><TT CLASS="PARAMETER" +><I >unix - password sync</VAR + password sync</I +></TT ></A >, <A HREF="#PASSWDPROGRAM" -> <VAR +> <TT CLASS="PARAMETER" ->passwd program</VAR +><I +>passwd program</I +></TT ></A > and <A HREF="#PASSWDCHATDEBUG" -><VAR +><TT CLASS="PARAMETER" ->passwd chat debug</VAR +><I +>passwd chat debug</I +></TT > </A >.</P @@ -11616,7 +12573,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 @@ -11626,10 +12583,12 @@ NAME="MINPRINTSPACE" ><P >See also the <A HREF="#PRINTING" -><VAR +><TT CLASS="PARAMETER" +><I >printing - </VAR + </I +></TT ></A > parameter.</P ><P @@ -11647,16 +12606,18 @@ 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 lowest SMB protocol dialect than Samba will support. Please refer to the <A HREF="#MAXPROTOCOL" -><VAR +><TT CLASS="PARAMETER" ->max protocol</VAR +><I +>max protocol</I +></TT ></A > parameter for a list of valid protocol names and a brief description @@ -11670,10 +12631,12 @@ CLASS="FILENAME" >If you are viewing this parameter as a security measure, you should also refer to the <A HREF="#LANMANAUTH" -><VAR +><TT CLASS="PARAMETER" +><I >lanman - auth</VAR + auth</I +></TT ></A > parameter. Otherwise, you should never need to change this parameter.</P @@ -11693,21 +12656,21 @@ 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" -><VAR +><TT CLASS="PARAMETER" -> wins support = yes</VAR +><I +> wins support = yes</I +></TT ></A >) what the minimum 'time to live' of NetBIOS names that <B @@ -11726,7 +12689,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 @@ -11738,62 +12701,68 @@ NAME="MSDFSPROXY" >Only Dfs roots can act as proxy shares. Take a look at the <A HREF="#MSDFSROOT" -><VAR +><TT CLASS="PARAMETER" ->msdfs root</VAR +><I +>msdfs root</I +></TT ></A > and <A HREF="#HOSTMSDFS" -><VAR +><TT CLASS="PARAMETER" ->host msdfs</VAR +><I +>host msdfs</I +></TT ></A > options to find out how to set up a Dfs root share.</P ><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 Samba is configured and compiled with the <B CLASS="COMMAND" > --with-msdfs</B -> option. If set to <CODE +> option. If set to <TT CLASS="CONSTANT" ->yes</CODE +>yes</TT >, Samba treats the share as a Dfs root and allows clients to browse the distributed file system tree rooted at the share directory. 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" -><VAR +><TT CLASS="PARAMETER" +><I >host msdfs - </VAR + </I +></TT ></A ></P ><P @@ -11806,7 +12775,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 @@ -11828,7 +12797,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 @@ -11843,9 +12812,9 @@ NAME="NAMERESOLVEORDER" ><UL ><LI ><P -><CODE +><TT CLASS="CONSTANT" ->lmhosts</CODE +>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 @@ -11857,9 +12826,9 @@ TARGET="_top" ></LI ><LI ><P -><CODE +><TT CLASS="CONSTANT" ->host</CODE +>host</TT > : Do a standard host name to IP address resolution, using the system <TT CLASS="FILENAME" @@ -11877,30 +12846,34 @@ CLASS="FILENAME" ></LI ><LI ><P -><CODE +><TT CLASS="CONSTANT" ->wins</CODE +>wins</TT > : Query a name with the IP address listed in the <A HREF="#WINSSERVER" -><VAR +><TT CLASS="PARAMETER" -> wins server</VAR +><I +> wins server</I +></TT ></A > parameter. If no WINS server has been specified this method will be ignored.</P ></LI ><LI ><P -><CODE +><TT CLASS="CONSTANT" ->bcast</CODE +>bcast</TT > : Do a broadcast on each of the known local interfaces listed in the <A HREF="#INTERFACES" -><VAR +><TT CLASS="PARAMETER" ->interfaces</VAR +><I +>interfaces</I +></TT ></A > parameter. This is the least reliable of the name resolution @@ -11929,7 +12902,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 @@ -11946,19 +12919,18 @@ TARGET="_top" ><P >See also <A HREF="#NETBIOSNAME" -><VAR +><TT CLASS="PARAMETER" +><I >netbios - name</VAR + name</I +></TT ></A >.</P ><P ->Default: <SPAN -CLASS="emphasis" -><I +>Default: <I CLASS="EMPHASIS" >empty string (no additional names)</I -></SPAN ></P ><P >Example: <B @@ -11970,7 +12942,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 @@ -11982,19 +12954,18 @@ NAME="NETBIOSNAME" ><P >See also <A HREF="#NETBIOSALIASES" -><VAR +><TT CLASS="PARAMETER" +><I >netbios - aliases</VAR + aliases</I +></TT ></A >.</P ><P ->Default: <SPAN -CLASS="emphasis" -><I +>Default: <I CLASS="EMPHASIS" >machine DNS name</I -></SPAN ></P ><P >Example: <B @@ -12006,7 +12977,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 @@ -12017,7 +12988,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 @@ -12039,9 +13010,11 @@ NAME="NISHOMEDIR" server. When Samba is returning the home share to the client, it will consult the NIS map specified in <A HREF="#HOMEDIRMAP" -> <VAR +> <TT CLASS="PARAMETER" ->homedir map</VAR +><I +>homedir map</I +></TT ></A > and return the server listed there.</P @@ -12059,7 +13032,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 @@ -12069,35 +13042,11 @@ NAME="NONUNIXACCOUNTRANGE" 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 -><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 ->These userids never appear on the system and Samba will never +>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 -></TD -></TR -></TABLE -></DIV ><P >Default: <B CLASS="COMMAND" @@ -12114,7 +13063,7 @@ CLASS="COMMAND" ><A NAME="NTACLSUPPORT" ></A ->>nt acl support (S)</DT +>nt acl support (S)</DT ><DD ><P >This boolean parameter controls whether @@ -12136,20 +13085,18 @@ 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 <CODE + clients to connect to the NT SMB specific <TT CLASS="CONSTANT" ->IPC$</CODE +>IPC$</TT > pipes. This is a developer debugging option and can be left alone.</P @@ -12163,7 +13110,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 @@ -12173,9 +13120,9 @@ TARGET="_top" > will negotiate NT specific status support with Windows NT/2k/XP clients. This is a developer debugging option and should be left alone. - If this option is set to <CODE + If this option is set to <TT CLASS="CONSTANT" ->no</CODE +>no</TT > then Samba offers exactly the same DOS error codes that versions prior to Samba 2.2.3 reported.</P @@ -12191,18 +13138,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 @@ -12214,7 +13159,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 @@ -12224,9 +13169,11 @@ NAME="OBEYPAMRESTRICTIONS" and to ignore any account or session management. Note that Samba always ignores PAM for authentication in the case of <A HREF="#ENCRYPTPASSWORDS" -><VAR +><TT CLASS="PARAMETER" ->encrypt passwords = yes</VAR +><I +>encrypt passwords = yes</I +></TT > </A >. The reason is that PAM modules cannot support the challenge/response @@ -12242,20 +13189,24 @@ CLASS="COMMAND" ><A NAME="ONLYUSER" ></A ->>only user (S)</DT +>only user (S)</DT ><DD ><P >This is a boolean option that controls whether - connections with usernames not in the <VAR + connections with usernames not in the <TT CLASS="PARAMETER" ->user</VAR +><I +>user</I +></TT > list will be allowed. By default this option is disabled so that a client can supply a username to be used by the server. Enabling this parameter will force the server to only use the login - names from the <VAR + names from the <TT CLASS="PARAMETER" ->user</VAR +><I +>user</I +></TT > list and is only really useful in <A HREF="#SECURITYEQUALSSHARE" @@ -12269,18 +13220,22 @@ HREF="#SECURITYEQUALSSHARE" CLASS="COMMAND" >user = %S</B -> which means your <VAR +> which means your <TT CLASS="PARAMETER" ->user</VAR +><I +>user</I +></TT > list will be just the service name, which for home directories is the name of the user.</P ><P >See also the <A HREF="#USER" -><VAR +><TT CLASS="PARAMETER" ->user</VAR +><I +>user</I +></TT > </A > parameter.</P @@ -12294,14 +13249,16 @@ CLASS="COMMAND" ><A NAME="ONLYGUEST" ></A ->>only guest (S)</DT +>only guest (S)</DT ><DD ><P >A synonym for <A HREF="#GUESTONLY" -><VAR +><TT CLASS="PARAMETER" -> guest only</VAR +><I +> guest only</I +></TT ></A >.</P ></DD @@ -12309,7 +13266,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 @@ -12320,13 +13277,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 @@ -12338,15 +13292,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" @@ -12356,27 +13307,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 @@ -12388,7 +13335,7 @@ CLASS="COMMAND" ><A NAME="OPLOCKS" ></A ->>oplocks (S)</DT +>oplocks (S)</DT ><DD ><P >This boolean option tells <B @@ -12413,31 +13360,39 @@ CLASS="FILENAME" >Oplocks may be selectively turned off on certain files with a share. See the <A HREF="#VETOOPLOCKFILES" -><VAR +><TT CLASS="PARAMETER" -> veto oplock files</VAR +><I +> veto oplock files</I +></TT ></A > parameter. On some systems oplocks are recognized by the underlying operating system. This allows data synchronization between all access to oplocked files, whether it be via Samba or NFS or a local UNIX process. See the - <VAR + <TT CLASS="PARAMETER" ->kernel oplocks</VAR +><I +>kernel oplocks</I +></TT > parameter for details.</P ><P >See also the <A HREF="#KERNELOPLOCKS" -><VAR +><TT CLASS="PARAMETER" +><I >kernel - oplocks</VAR + oplocks</I +></TT ></A > and <A HREF="#LEVEL2OPLOCKS" -><VAR +><TT CLASS="PARAMETER" -> level2 oplocks</VAR +><I +> level2 oplocks</I +></TT ></A > parameters.</P ><P @@ -12450,16 +13405,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. @@ -12468,8 +13420,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 @@ -12481,29 +13432,26 @@ 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 <VAR + has a chance of becoming a local master browser for the <TT CLASS="PARAMETER" -> WORKGROUP</VAR +><I +> WORKGROUP</I +></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 @@ -12532,7 +13480,7 @@ 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 @@ -12551,12 +13499,17 @@ 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" @@ -12568,7 +13521,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, @@ -12577,17 +13530,21 @@ NAME="PAMPASSWORDCHANGE" changes when requested by an SMB client instead of the program listed in <A HREF="#PASSWDPROGRAM" -><VAR +><TT CLASS="PARAMETER" ->passwd program</VAR +><I +>passwd program</I +></TT ></A >. It should be possible to enable this without changing your <A HREF="#PASSWDCHAT" -><VAR +><TT CLASS="PARAMETER" ->passwd chat</VAR +><I +>passwd chat</I +></TT ></A > parameter for most setups. @@ -12602,24 +13559,21 @@ 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" @@ -12635,19 +13589,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 @@ -12657,7 +13607,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 @@ -12694,9 +13644,11 @@ CLASS="COMMAND" ><P >See also <A HREF="#NONUNIXACCOUNTRANGE" -> <VAR +> <TT CLASS="PARAMETER" ->non unix account range</VAR +><I +>non unix account range</I +></TT ></A ></P ></LI @@ -12709,9 +13661,11 @@ CLASS="COMMAND" backend. Takes a path to the TDB as an optional argument (defaults to passdb.tdb in the <A HREF="#PRIVATEDIR" -> <VAR +> <TT CLASS="PARAMETER" ->private dir</VAR +><I +>private dir</I +></TT ></A > directory.</P ></LI @@ -12724,17 +13678,21 @@ CLASS="COMMAND" backend, with non unix account support. Takes a path to the TDB as an optional argument (defaults to passdb.tdb in the <A HREF="#PRIVATEDIR" -> <VAR +> <TT CLASS="PARAMETER" ->private dir</VAR +><I +>private dir</I +></TT ></A > directory.</P ><P >See also <A HREF="#NONUNIXACCOUNTRANGE" -> <VAR +> <TT CLASS="PARAMETER" ->non unix account range</VAR +><I +>non unix account range</I +></TT ></A ></P ></LI @@ -12767,10 +13725,12 @@ CLASS="COMMAND" ><P >See also <A HREF="#NONUNIXACCOUNTRANGE" -> <VAR +> <TT CLASS="PARAMETER" +><I >non unix account - range</VAR + range</I +></TT ></A ></P ><P @@ -12778,14 +13738,18 @@ CLASS="PARAMETER" possible. This may be done using either Start-TLS (see <A HREF="#LDAPSSL" -> <VAR +> <TT CLASS="PARAMETER" ->ldap ssl</VAR +><I +>ldap ssl</I +></TT ></A >) or by - specifying <VAR + specifying <TT CLASS="PARAMETER" ->ldaps://</VAR +><I +>ldaps://</I +></TT > in the URL argument. </P @@ -12814,7 +13778,7 @@ CLASS="COMMAND" ><B CLASS="COMMAND" >unixsam</B -> - Allows samba to map all (other) available unix users</P +> - (EXPERIMENTAL) Allows samba to map all (other) available unix users</P ><P >This backend uses the standard unix database for retrieving users. Users included in this pdb are NOT listed in samba user listings and users included in this pdb won't be @@ -12833,17 +13797,17 @@ CLASS="COMMAND" ><P >Default: <B CLASS="COMMAND" ->passdb backend = smbpasswd unixsam</B +>passdb backend = smbpasswd guest</B ></P ><P >Example: <B CLASS="COMMAND" ->passdb backend = tdbsam:/etc/samba/private/passdb.tdb smbpasswd:/etc/samba/smbpasswd unixsam</B +>passdb backend = tdbsam:/etc/samba/private/passdb.tdb smbpasswd:/etc/samba/smbpasswd </B ></P ><P >Example: <B CLASS="COMMAND" ->passdb backend = ldapsam_nua:ldaps://ldap.example.com unixsam</B +>passdb backend = ldapsam_nua:ldaps://ldap.example.com </B ></P ><P >Example: <B @@ -12855,36 +13819,31 @@ 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" -><VAR +><TT CLASS="PARAMETER" ->passwd program</VAR +><I +>passwd program</I +></TT > </A > and what to expect back. If the expected output is not @@ -12896,21 +13855,20 @@ CLASS="PARAMETER" ><P >Note that this parameter only is only used if the <A HREF="#UNIXPASSWORDSYNC" -><VAR +><TT CLASS="PARAMETER" +><I >unix - password sync</VAR + password sync</I +></TT ></A -> parameter is set to <CODE +> parameter is set to <TT CLASS="CONSTANT" ->yes</CODE +>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 @@ -12922,23 +13880,25 @@ HREF="#PASSWDPROGRAM" executed on the NIS master. </P ><P ->The string can contain the macro <VAR +>The string can contain the macro <TT CLASS="PARAMETER" ->%n</VAR +><I +>%n</I +></TT > which is substituted for the new password. The chat sequence can also contain the standard - macros <CODE + macros <TT CLASS="CONSTANT" ->\\n</CODE ->, <CODE +>\n</TT +>, <TT CLASS="CONSTANT" ->\\r</CODE ->, <CODE +>\r</TT +>, <TT CLASS="CONSTANT" -> \\t</CODE -> and <CODE +> \t</TT +> and <TT CLASS="CONSTANT" ->\\s</CODE +>\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. @@ -12951,14 +13911,16 @@ CLASS="CONSTANT" ><P >If the <A HREF="#PAMPASSWORDCHANGE" -><VAR +><TT CLASS="PARAMETER" +><I >pam - password change</VAR + password change</I +></TT ></A -> parameter is set to <CODE +> parameter is set to <TT CLASS="CONSTANT" ->yes</CODE +>yes</TT >, the chat pairs may be matched in any order, and success is determined by the PAM result, not any particular output. The \n macro is ignored for PAM conversions. @@ -12966,41 +13928,49 @@ CLASS="CONSTANT" ><P >See also <A HREF="#UNIXPASSWORDSYNC" -><VAR +><TT CLASS="PARAMETER" +><I >unix password - sync</VAR + sync</I +></TT ></A >, <A HREF="#PASSWDPROGRAM" -><VAR +><TT CLASS="PARAMETER" -> passwd program</VAR +><I +> passwd program</I +></TT ></A > ,<A HREF="#PASSWDCHATDEBUG" -> <VAR +> <TT CLASS="PARAMETER" ->passwd chat debug</VAR +><I +>passwd chat debug</I +></TT ></A > and <A HREF="#PAMPASSWORDCHANGE" -> <VAR +> <TT CLASS="PARAMETER" ->pam password change</VAR +><I +>pam password change</I +></TT ></A >.</P ><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 @@ -13008,30 +13978,27 @@ 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" -><VAR +><TT CLASS="PARAMETER" ->debug level</VAR +><I +>debug level</I +></TT ></A > of 100. This is a dangerous option as it will allow plaintext passwords @@ -13039,43 +14006,55 @@ CLASS="PARAMETER" CLASS="COMMAND" >smbd</B > log. It is available to help - Samba admins debug their <VAR + Samba admins debug their <TT CLASS="PARAMETER" ->passwd chat</VAR +><I +>passwd chat</I +></TT > scripts - when calling the <VAR + when calling the <TT CLASS="PARAMETER" ->passwd program</VAR +><I +>passwd program</I +></TT > and should be turned off after this has been done. This option has no effect if the <A HREF="#PAMPASSWORDCHANGE" -><VAR +><TT CLASS="PARAMETER" ->pam password change</VAR +><I +>pam password change</I +></TT ></A > paramter is set. This parameter is off by default.</P ><P >See also <A HREF="#PASSWDCHAT" -><VAR +><TT CLASS="PARAMETER" ->passwd chat</VAR +><I +>passwd chat</I +></TT > </A >, <A HREF="#PAMPASSWORDCHANGE" -><VAR +><TT CLASS="PARAMETER" ->pam password change</VAR +><I +>pam password change</I +></TT > </A >, <A HREF="#PASSWDPROGRAM" -><VAR +><TT CLASS="PARAMETER" ->passwd program</VAR +><I +>passwd program</I +></TT > </A >.</P @@ -13089,49 +14068,44 @@ 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 - UNIX user passwords. Any occurrences of <VAR + UNIX user passwords. Any occurrences of <TT CLASS="PARAMETER" ->%u</VAR +><I +>%u</I +></TT > 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 <VAR +> that if the <TT CLASS="PARAMETER" +><I >unix - password sync</VAR -> parameter is set to <CODE + password sync</I +></TT +> parameter is set to <TT CLASS="CONSTANT" >yes - </CODE -> then this program is called <SPAN -CLASS="emphasis" -><I + </TT +> then this program is called <I CLASS="EMPHASIS" >AS ROOT</I -></SPAN > before the SMB password in the <A HREF="smbpasswd.5.html" @@ -13145,39 +14119,39 @@ CLASS="COMMAND" > will fail to change the SMB password also (this is by design).</P ><P ->If the <VAR +>If the <TT CLASS="PARAMETER" ->unix password sync</VAR -> parameter - is set this parameter <SPAN -CLASS="emphasis" ><I +>unix password sync</I +></TT +> parameter + 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 <VAR + for security implications. Note that by default <TT CLASS="PARAMETER" +><I >unix - password sync</VAR -> is set to <CODE + password sync</I +></TT +> is set to <TT CLASS="CONSTANT" ->no</CODE +>no</TT >.</P ><P >See also <A HREF="#UNIXPASSWORDSYNC" -><VAR +><TT CLASS="PARAMETER" +><I >unix - password sync</VAR + password sync</I +></TT ></A >.</P ><P @@ -13196,7 +14170,7 @@ CLASS="COMMAND" ><A NAME="PASSWORDLEVEL" ></A ->>password level (G)</DT +>password level (G)</DT ><DD ><P >Some client/server combinations have difficulty @@ -13211,17 +14185,21 @@ NAME="PASSWORDLEVEL" >This parameter defines the maximum number of characters that may be upper case in passwords.</P ><P ->For example, say the password given was "FRED". If <VAR +>For example, say the password given was "FRED". If <TT CLASS="PARAMETER" -> password level</VAR +><I +> password level</I +></TT > is set to 1, the following combinations would be tried if "FRED" failed:</P ><P >"Fred", "fred", "fRed", "frEd","freD"</P ><P ->If <VAR +>If <TT CLASS="PARAMETER" ->password level</VAR +><I +>password level</I +></TT > was set to 2, the following combinations would also be tried: </P ><P @@ -13252,7 +14230,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 @@ -13278,10 +14256,12 @@ CLASS="FILENAME" >The name of the password server is looked up using the parameter <A HREF="#NAMERESOLVEORDER" -><VAR +><TT CLASS="PARAMETER" +><I >name - resolve order</VAR + resolve order</I +></TT ></A > and so may resolved by any method and order described in that parameter.</P @@ -13289,62 +14269,42 @@ CLASS="PARAMETER" >The password server must be a machine capable of using the "LM1.2X002" or the "NT LM 0.12" protocol, and it must be in user level security mode.</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 ->Using a password server - means your UNIX box (running Samba) is only as secure as your - password server. <SPAN -CLASS="emphasis" ><I CLASS="EMPHASIS" +>NOTE:</I +> Using a password server + means your UNIX box (running Samba) is only as secure as your + password server. <I +CLASS="EMPHASIS" >DO NOT CHOOSE A PASSWORD SERVER THAT YOU DON'T COMPLETELY TRUST</I -></SPAN >.</P -></TD -></TR -></TABLE -></DIV ><P >Never point a Samba server at itself for password serving. This will cause a loop and could lock up your Samba server!</P ><P >The name of the password server takes the standard - substitutions, but probably the only useful one is <VAR + substitutions, but probably the only useful one is <TT CLASS="PARAMETER" +><I >%m - </VAR + </I +></TT >, which means the Samba server will use the incoming client as the password server. If you use this then you better trust your clients, and you had better restrict them with hosts allow!</P ><P ->If the <VAR +>If the <TT CLASS="PARAMETER" ->security</VAR +><I +>security</I +></TT > parameter is set to - <CODE + <TT CLASS="CONSTANT" ->domain</CODE +>domain</TT >, then the list of machines in this option must be a list of Primary or Backup Domain controllers for the Domain or the character '*', as the Samba server is effectively @@ -13353,9 +14313,11 @@ CLASS="CONSTANT" CLASS="COMMAND" > security = domain</B > is that if you list several hosts in the - <VAR + <TT CLASS="PARAMETER" ->password server</VAR +><I +>password server</I +></TT > option then <B CLASS="COMMAND" >smbd @@ -13363,15 +14325,17 @@ CLASS="COMMAND" > will try each in turn till it finds one that responds. This is useful in case your primary server goes down.</P ><P ->If the <VAR +>If the <TT CLASS="PARAMETER" ->password server</VAR +><I +>password server</I +></TT > option is set to the character '*', then Samba will attempt to auto-locate the Primary or Backup Domain controllers to authenticate against by - doing a query for the name <CODE + doing a query for the name <TT CLASS="CONSTANT" ->WORKGROUP<1C></CODE +>WORKGROUP<1C></TT > and then contacting each server returned in the list of IP addresses from the name resolution source. </P @@ -13382,13 +14346,15 @@ CLASS="CONSTANT" will be added to the list as well. Samba will not attempt to optimize this list by locating the closest DC.</P ><P ->If the <VAR +>If the <TT CLASS="PARAMETER" ->security</VAR +><I +>security</I +></TT > parameter is - set to <CODE + set to <TT CLASS="CONSTANT" ->server</CODE +>server</TT >, then there are different restrictions that <B CLASS="COMMAND" @@ -13401,9 +14367,11 @@ CLASS="COMMAND" ><LI ><P >You may list several password servers in - the <VAR + the <TT CLASS="PARAMETER" ->password server</VAR +><I +>password server</I +></TT > parameter, however if an <B CLASS="COMMAND" @@ -13434,10 +14402,12 @@ CLASS="COMMAND" ><P >See also the <A HREF="#SECURITY" -><VAR +><TT CLASS="PARAMETER" +><I >security - </VAR + </I +></TT ></A > parameter.</P ><P @@ -13462,7 +14432,7 @@ CLASS="COMMAND" ><A NAME="PATH" ></A ->>path (S)</DT +>path (S)</DT ><DD ><P >This parameter specifies a directory to which @@ -13476,14 +14446,18 @@ NAME="PATH" you probably won't get the results you expect if you do otherwise.</P ><P ->Any occurrences of <VAR +>Any occurrences of <TT CLASS="PARAMETER" ->%u</VAR +><I +>%u</I +></TT > in the path will be replaced with the UNIX username that the client is using - on this connection. Any occurrences of <VAR + on this connection. Any occurrences of <TT CLASS="PARAMETER" ->%m</VAR +><I +>%m</I +></TT > will be replaced by the NetBIOS name of the machine they are connecting from. These replacements are very useful for setting @@ -13491,18 +14465,17 @@ CLASS="PARAMETER" ><P >Note that this path will be based on <A HREF="#ROOTDIR" -> <VAR +> <TT CLASS="PARAMETER" ->root dir</VAR +><I +>root dir</I +></TT ></A > if one was specified.</P ><P ->Default: <SPAN -CLASS="emphasis" -><I +>Default: <I CLASS="EMPHASIS" >none</I -></SPAN ></P ><P >Example: <B @@ -13514,7 +14487,7 @@ CLASS="COMMAND" ><A NAME="PIDDIRECTORY" ></A ->>pid directory (G)</DT +>pid directory (G)</DT ><DD ><P >This option specifies the directory where pid @@ -13535,15 +14508,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 @@ -13561,7 +14535,7 @@ CLASS="COMMAND" ><A NAME="POSTEXEC" ></A ->>postexec (S)</DT +>postexec (S)</DT ><DD ><P >This option specifies a command to be run @@ -13579,19 +14553,18 @@ CLASS="COMMAND" ><P >See also <A HREF="#PREEXEC" -><VAR +><TT CLASS="PARAMETER" ->preexec</VAR +><I +>preexec</I +></TT > </A >.</P ><P ->Default: <SPAN -CLASS="emphasis" -><I +>Default: <I CLASS="EMPHASIS" >none (no command executed)</I -></SPAN > </P ><P @@ -13603,9 +14576,32 @@ CLASS="COMMAND" ></DD ><DT ><A +NAME="POSTSCRIPT" +></A +>postscript (S)</DT +><DD +><P +>This parameter forces a printer to interpret + the print files as PostScript. This is done by adding a <TT +CLASS="CONSTANT" +>%! + </TT +> to the start of print output.</P +><P +>This is most useful when you have lots of PCs that persist + in putting a control-D at the start of print jobs, which then + confuses your printer.</P +><P +>Default: <B +CLASS="COMMAND" +>postscript = no</B +></P +></DD +><DT +><A NAME="PREEXEC" ></A ->>preexec (S)</DT +>preexec (S)</DT ><DD ><P >This option specifies a command to be run whenever @@ -13625,26 +14621,27 @@ CLASS="COMMAND" ><P >See also <A HREF="#PREEXECCLOSE" -><VAR +><TT CLASS="PARAMETER" +><I >preexec close - </VAR + </I +></TT ></A > and <A HREF="#POSTEXEC" -><VAR +><TT CLASS="PARAMETER" +><I >postexec - </VAR + </I +></TT ></A >.</P ><P ->Default: <SPAN -CLASS="emphasis" -><I +>Default: <I CLASS="EMPHASIS" >none (no command executed)</I -></SPAN ></P ><P >Example: <B @@ -13657,16 +14654,18 @@ CLASS="COMMAND" ><A NAME="PREEXECCLOSE" ></A ->>preexec close (S)</DT +>preexec close (S)</DT ><DD ><P >This boolean option controls whether a non-zero return code from <A HREF="#PREEXEC" -><VAR +><TT CLASS="PARAMETER" +><I >preexec - </VAR + </I +></TT ></A > should close the service being connected to.</P ><P @@ -13679,7 +14678,7 @@ CLASS="COMMAND" ><A NAME="PREFERREDMASTER" ></A ->>preferred master (G)</DT +>preferred master (G)</DT ><DD ><P >This boolean parameter controls if <A @@ -13689,9 +14688,9 @@ TARGET="_top" > is a preferred master browser for its workgroup.</P ><P ->If this is set to <CODE +>If this is set to <TT CLASS="CONSTANT" ->yes</CODE +>yes</TT >, on startup, <B CLASS="COMMAND" >nmbd</B @@ -13702,9 +14701,11 @@ CLASS="COMMAND" CLASS="COMMAND" ><A HREF="#DOMAINMASTER" -><VAR +><TT CLASS="PARAMETER" -> domain master</VAR +><I +> domain master</I +></TT ></A > = yes</B >, so that <B @@ -13721,9 +14722,11 @@ CLASS="COMMAND" ><P >See also <A HREF="#OSLEVEL" -><VAR +><TT CLASS="PARAMETER" ->os level</VAR +><I +>os level</I +></TT > </A >.</P @@ -13737,14 +14740,16 @@ CLASS="COMMAND" ><A NAME="PREFEREDMASTER" ></A ->>prefered master (G)</DT +>prefered master (G)</DT ><DD ><P >Synonym for <A HREF="#PREFERREDMASTER" -><VAR +><TT CLASS="PARAMETER" -> preferred master</VAR +><I +> preferred master</I +></TT ></A > for people who cannot spell :-).</P ></DD @@ -13752,7 +14757,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 @@ -13763,18 +14768,17 @@ NAME="PRELOAD" >Note that if you just want all printers in your printcap file loaded then the <A HREF="#LOADPRINTERS" -> <VAR +> <TT CLASS="PARAMETER" ->load printers</VAR +><I +>load printers</I +></TT ></A > option is easier.</P ><P ->Default: <SPAN -CLASS="emphasis" -><I +>Default: <I CLASS="EMPHASIS" >no preloaded services</I -></SPAN ></P ><P >Example: <B @@ -13784,43 +14788,21 @@ CLASS="COMMAND" ></DD ><DT ><A -NAME="PRELOADMODULES" -></A ->>preload modules (G)</DT -><DD -><P ->This is a list of paths to modules that should - be loaded into smbd before a client connects. This improves - the speed of smbd when reacting to new connections somewhat. </P -><P ->It is recommended to only use this option on heavy-performance - servers.</P -><P ->Default: <B -CLASS="COMMAND" ->preload modules = </B -></P -><P ->Example: <B -CLASS="COMMAND" ->preload modules = /usr/lib/samba/passdb/mysql.so</B -></P -></DD -><DT -><A NAME="PRESERVECASE" ></A ->>preserve case (S)</DT +>preserve case (S)</DT ><DD ><P > This controls if new filenames are created with the case that the client passes, or if they are forced to be the <A HREF="#DEFAULTCASE" -><VAR +><TT CLASS="PARAMETER" +><I >default case - </VAR + </I +></TT ></A >.</P ><P @@ -13830,7 +14812,7 @@ CLASS="COMMAND" ></P ><P >See the section on <A -HREF="#AEN207" +HREF="#AEN205" >NAME MANGLING</A > for a fuller discussion.</P @@ -13839,7 +14821,7 @@ HREF="#AEN207" ><A NAME="PRINTCOMMAND" ></A ->>print command (S)</DT +>print command (S)</DT ><DD ><P >After a print job has finished spooling to @@ -13872,28 +14854,33 @@ 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 <VAR + one occurrence of <TT CLASS="PARAMETER" ->%s</VAR -> or <VAR +><I +>%s</I +></TT +> or <TT CLASS="PARAMETER" +><I >%f - </VAR -> - the <VAR + </I +></TT +> - the <TT CLASS="PARAMETER" ->%p</VAR +><I +>%p</I +></TT > is optional. At the time - a job is submitted, if no printer name is supplied the <VAR + a job is submitted, if no printer name is supplied the <TT CLASS="PARAMETER" +><I >%p - </VAR + </I +></TT > will be silently removed from the printer command.</P ><P >If specified in the [global] section, the print command given @@ -13905,15 +14892,17 @@ CLASS="PARAMETER" be created but not processed and (most importantly) not removed.</P ><P >Note that printing may fail on some UNIXes from the - <CODE + <TT CLASS="CONSTANT" ->nobody</CODE +>nobody</TT > account. If this happens then create an alternative guest account that can print and set the <A HREF="#GUESTACCOUNT" -><VAR +><TT CLASS="PARAMETER" ->guest account</VAR +><I +>guest account</I +></TT ></A > in the [global] section.</P @@ -13933,9 +14922,11 @@ CLASS="COMMAND" on how you normally print files on your system. The default for the parameter varies depending on the setting of the <A HREF="#PRINTING" -> <VAR +> <TT CLASS="PARAMETER" ->printing</VAR +><I +>printing</I +></TT ></A > parameter.</P ><P @@ -13999,14 +14990,16 @@ CLASS="COMMAND" ><A NAME="PRINTOK" ></A ->>print ok (S)</DT +>print ok (S)</DT ><DD ><P >Synonym for <A HREF="#PRINTABLE" -> <VAR +> <TT CLASS="PARAMETER" ->printable</VAR +><I +>printable</I +></TT ></A >.</P ></DD @@ -14014,12 +15007,12 @@ CLASS="PARAMETER" ><A NAME="PRINTABLE" ></A ->>printable (S)</DT +>printable (S)</DT ><DD ><P ->If this parameter is <CODE +>If this parameter is <TT CLASS="CONSTANT" ->yes</CODE +>yes</TT >, then clients may open, write to and submit spool files on the directory specified for the service. </P @@ -14028,10 +15021,12 @@ CLASS="CONSTANT" to the service path (user privileges permitting) via the spooling of print data. The <A HREF="#READONLY" -><VAR +><TT CLASS="PARAMETER" +><I >read only - </VAR + </I +></TT ></A > parameter controls only non-printing access to the resource.</P @@ -14045,14 +15040,16 @@ CLASS="COMMAND" ><A NAME="PRINTCAP" ></A ->>printcap (G)</DT +>printcap (G)</DT ><DD ><P >Synonym for <A HREF="#PRINTCAPNAME" -><VAR +><TT CLASS="PARAMETER" -> printcap name</VAR +><I +> printcap name</I +></TT ></A >.</P ></DD @@ -14060,7 +15057,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 @@ -14068,7 +15065,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 @@ -14100,9 +15097,11 @@ CLASS="COMMAND" </B > to automatically obtain lists of available printers. This is the default for systems that define SYSV at configure time in - Samba (this includes most System V based systems). If <VAR + Samba (this includes most System V based systems). If <TT CLASS="PARAMETER" -> printcap name</VAR +><I +> printcap name</I +></TT > is set to <B CLASS="COMMAND" >lpstat</B @@ -14115,40 +15114,33 @@ 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 -><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 ->Under AIX the default printcap +><I +CLASS="EMPHASIS" +>NOTE</I +>: Under AIX the default printcap name is <TT CLASS="FILENAME" >/etc/qconfig</TT @@ -14161,10 +15153,6 @@ CLASS="FILENAME" CLASS="FILENAME" >qconfig</TT > appears in the printcap filename.</P -></TD -></TR -></TABLE -></DIV ><P >Default: <B CLASS="COMMAND" @@ -14180,7 +15168,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 @@ -14201,9 +15189,205 @@ CLASS="COMMAND" ></DD ><DT ><A +NAME="PRINTERDRIVER" +></A +>printer driver (S)</DT +><DD +><P +><I +CLASS="EMPHASIS" +>Note :</I +>This is a deprecated + parameter and will be removed in the next major release + following version 2.2. Please see the instructions in + the <A +HREF="printer_driver2.html" +TARGET="_top" +>Samba 2.2. Printing + HOWTO</A +> for more information + on the new method of loading printer drivers onto a Samba server. + </P +><P +>This option allows you to control the string + that clients receive when they ask the server for the printer driver + associated with a printer. If you are using Windows95 or Windows NT + then you can use this to automate the setup of printers on your + system.</P +><P +>You need to set this parameter to the exact string (case + sensitive) that describes the appropriate printer driver for your + system. If you don't know the exact string to use then you should + first try with no <A +HREF="#PRINTERDRIVER" +><TT +CLASS="PARAMETER" +><I +> printer driver</I +></TT +></A +> option set and the client will + give you a list of printer drivers. The appropriate strings are + shown in a scroll box after you have chosen the printer manufacturer.</P +><P +>See also <A +HREF="#PRINTERDRIVERFILE" +><TT +CLASS="PARAMETER" +><I +>printer + driver file</I +></TT +></A +>.</P +><P +>Example: <B +CLASS="COMMAND" +>printer driver = HP LaserJet 4L</B +></P +></DD +><DT +><A +NAME="PRINTERDRIVERFILE" +></A +>printer driver file (G)</DT +><DD +><P +><I +CLASS="EMPHASIS" +>Note :</I +>This is a deprecated + parameter and will be removed in the next major release + following version 2.2. Please see the instructions in + the <A +HREF="printer_driver2.html" +TARGET="_top" +>Samba 2.2. Printing + HOWTO</A +> for more information + on the new method of loading printer drivers onto a Samba server. + </P +><P +>This parameter tells Samba where the printer driver + definition file, used when serving drivers to Windows 95 clients, is + to be found. If this is not set, the default is :</P +><P +><TT +CLASS="FILENAME" +><TT +CLASS="REPLACEABLE" +><I +>SAMBA_INSTALL_DIRECTORY</I +></TT +> + /lib/printers.def</TT +></P +><P +>This file is created from Windows 95 <TT +CLASS="FILENAME" +>msprint.inf + </TT +> files found on the Windows 95 client system. For more + details on setting up serving of printer drivers to Windows 95 + clients, see the outdated documentation file in the <TT +CLASS="FILENAME" +>docs/</TT +> + directory, <TT +CLASS="FILENAME" +>PRINTER_DRIVER.txt</TT +>.</P +><P +>See also <A +HREF="#PRINTERDRIVERLOCATION" +><TT +CLASS="PARAMETER" +><I +> printer driver location</I +></TT +></A +>.</P +><P +>Default: <I +CLASS="EMPHASIS" +>None (set in compile).</I +></P +><P +>Example: <B +CLASS="COMMAND" +>printer driver file = + /usr/local/samba/printers/drivers.def</B +></P +></DD +><DT +><A +NAME="PRINTERDRIVERLOCATION" +></A +>printer driver location (S)</DT +><DD +><P +><I +CLASS="EMPHASIS" +>Note :</I +>This is a deprecated + parameter and will be removed in the next major release + following version 2.2. Please see the instructions in + the <A +HREF="printer_driver2.html" +TARGET="_top" +>Samba 2.2. Printing + HOWTO</A +> for more information + on the new method of loading printer drivers onto a Samba server. + </P +><P +>This parameter tells clients of a particular printer + share where to find the printer driver files for the automatic + installation of drivers for Windows 95 machines. If Samba is set up + to serve printer drivers to Windows 95 machines, this should be set to</P +><P +><B +CLASS="COMMAND" +>\\MACHINE\PRINTER$</B +></P +><P +>Where MACHINE is the NetBIOS name of your Samba server, + and PRINTER$ is a share you set up for serving printer driver + files. For more details on setting this up see the outdated documentation + file in the <TT +CLASS="FILENAME" +>docs/</TT +> directory, <TT +CLASS="FILENAME" +> PRINTER_DRIVER.txt</TT +>.</P +><P +>See also <A +HREF="#PRINTERDRIVERFILE" +><TT +CLASS="PARAMETER" +><I +> printer driver file</I +></TT +></A +>.</P +><P +>Default: <B +CLASS="COMMAND" +>none</B +></P +><P +>Example: <B +CLASS="COMMAND" +>printer driver location = \\MACHINE\PRINTER$ + </B +></P +></DD +><DT +><A NAME="PRINTERNAME" ></A ->>printer name (S)</DT +>printer name (S)</DT ><DD ><P >This parameter specifies the name of the printer @@ -14213,16 +15397,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 <CODE +>none (but may be <TT CLASS="CONSTANT" ->lp</CODE +>lp</TT > on many systems)</I -></SPAN ></P ><P >Example: <B @@ -14234,14 +15415,16 @@ CLASS="COMMAND" ><A NAME="PRINTER" ></A ->>printer (S)</DT +>printer (S)</DT ><DD ><P >Synonym for <A HREF="#PRINTERNAME" -><VAR +><TT CLASS="PARAMETER" -> printer name</VAR +><I +> printer name</I +></TT ></A >.</P ></DD @@ -14249,64 +15432,74 @@ CLASS="PARAMETER" ><A NAME="PRINTING" ></A ->>printing (S)</DT +>printing (S)</DT ><DD ><P >This parameters controls how printer status information is interpreted on your system. It also affects the - default values for the <VAR + default values for the <TT CLASS="PARAMETER" ->print command</VAR +><I +>print command</I +></TT >, - <VAR + <TT CLASS="PARAMETER" ->lpq command</VAR ->, <VAR +><I +>lpq command</I +></TT +>, <TT CLASS="PARAMETER" +><I >lppause command - </VAR ->, <VAR + </I +></TT +>, <TT CLASS="PARAMETER" ->lpresume command</VAR +><I +>lpresume command</I +></TT >, and - <VAR + <TT CLASS="PARAMETER" ->lprm command</VAR +><I +>lprm command</I +></TT > if specified in the [global] section.</P ><P >Currently nine printing styles are supported. They are - <CODE + <TT CLASS="CONSTANT" ->BSD</CODE ->, <CODE +>BSD</TT +>, <TT CLASS="CONSTANT" ->AIX</CODE +>AIX</TT >, - <CODE + <TT CLASS="CONSTANT" ->LPRNG</CODE ->, <CODE +>LPRNG</TT +>, <TT CLASS="CONSTANT" ->PLP</CODE +>PLP</TT >, - <CODE + <TT CLASS="CONSTANT" ->SYSV</CODE ->, <CODE +>SYSV</TT +>, <TT CLASS="CONSTANT" ->HPUX</CODE +>HPUX</TT >, - <CODE + <TT CLASS="CONSTANT" ->QNX</CODE ->, <CODE +>QNX</TT +>, <TT CLASS="CONSTANT" ->SOFTQ</CODE +>SOFTQ</TT >, - and <CODE + and <TT CLASS="CONSTANT" ->CUPS</CODE +>CUPS</TT >.</P ><P >To see what the defaults are for the other print @@ -14319,7 +15512,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 @@ -14327,7 +15520,7 @@ HREF="#AEN80" ><A NAME="PRIVATEDIR" ></A ->>private dir (G)</DT +>private dir (G)</DT ><DD ><P >This parameters defines the directory @@ -14350,14 +15543,16 @@ CLASS="COMMAND" ><A NAME="PROTOCOL" ></A ->>protocol (G)</DT +>protocol (G)</DT ><DD ><P >Synonym for <A HREF="#MAXPROTOCOL" -> <VAR +> <TT CLASS="PARAMETER" ->max protocol</VAR +><I +>max protocol</I +></TT ></A >.</P ></DD @@ -14365,15 +15560,17 @@ CLASS="PARAMETER" ><A NAME="PUBLIC" ></A ->>public (S)</DT +>public (S)</DT ><DD ><P >Synonym for <A HREF="#GUESTOK" -><VAR +><TT CLASS="PARAMETER" +><I >guest - ok</VAR + ok</I +></TT ></A >.</P ></DD @@ -14381,7 +15578,7 @@ CLASS="PARAMETER" ><A NAME="QUEUEPAUSECOMMAND" ></A ->>queuepause command (S)</DT +>queuepause command (S)</DT ><DD ><P >This parameter specifies the command to be @@ -14395,9 +15592,11 @@ NAME="QUEUEPAUSECOMMAND" but can be issued from the Printers window under Windows 95 and NT.</P ><P ->If a <VAR +>If a <TT CLASS="PARAMETER" ->%p</VAR +><I +>%p</I +></TT > is given then the printer name is put in its place. Otherwise it is placed at the end of the command. </P @@ -14406,16 +15605,15 @@ 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 <VAR +>depends on the setting of <TT CLASS="PARAMETER" +><I >printing - </VAR + </I +></TT ></I -></SPAN ></P ><P >Example: <B @@ -14427,7 +15625,7 @@ CLASS="COMMAND" ><A NAME="QUEUERESUMECOMMAND" ></A ->>queueresume command (S)</DT +>queueresume command (S)</DT ><DD ><P >This parameter specifies the command to be @@ -14435,9 +15633,11 @@ NAME="QUEUERESUMECOMMAND" is the command to undo the behavior that is caused by the previous parameter (<A HREF="#QUEUEPAUSECOMMAND" -><VAR +><TT CLASS="PARAMETER" -> queuepause command</VAR +><I +> queuepause command</I +></TT ></A >).</P ><P @@ -14449,9 +15649,11 @@ CLASS="PARAMETER" but can be issued from the Printers window under Windows 95 and NT.</P ><P ->If a <VAR +>If a <TT CLASS="PARAMETER" ->%p</VAR +><I +>%p</I +></TT > is given then the printer name is put in its place. Otherwise it is placed at the end of the command.</P @@ -14460,18 +15662,17 @@ 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" -><VAR +><TT CLASS="PARAMETER" ->printing</VAR +><I +>printing</I +></TT ></A ></I -></SPAN > </P ><P @@ -14485,7 +15686,7 @@ CLASS="COMMAND" ><A NAME="READBMPX" ></A ->>read bmpx (G)</DT +>read bmpx (G)</DT ><DD ><P >This boolean parameter controls whether <A @@ -14494,9 +15695,9 @@ TARGET="_top" >smbd(8)</A > will support the "Read Block Multiplex" SMB. This is now rarely used and defaults to - <CODE + <TT CLASS="CONSTANT" ->no</CODE +>no</TT >. You should never need to set this parameter.</P ><P @@ -14509,38 +15710,46 @@ 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 access to a service. If the connecting user is in this list then they will not be given write access, no matter what the <A HREF="#READONLY" -><VAR +><TT CLASS="PARAMETER" ->read only</VAR +><I +>read only</I +></TT ></A > option is set to. The list can include group names using the syntax described in the <A HREF="#INVALIDUSERS" -><VAR +><TT CLASS="PARAMETER" -> invalid users</VAR +><I +> invalid users</I +></TT ></A > parameter.</P ><P >See also the <A HREF="#WRITELIST" -><VAR +><TT CLASS="PARAMETER" -> write list</VAR +><I +> write list</I +></TT ></A > parameter and the <A HREF="#INVALIDUSERS" -><VAR +><TT CLASS="PARAMETER" ->invalid users</VAR +><I +>invalid users</I +></TT > </A > parameter.</P @@ -14559,20 +15768,22 @@ CLASS="COMMAND" ><A NAME="READONLY" ></A ->>read only (S)</DT +>read only (S)</DT ><DD ><P >An inverted synonym is <A HREF="#WRITEABLE" -> <VAR +> <TT CLASS="PARAMETER" ->writeable</VAR +><I +>writeable</I +></TT ></A >.</P ><P ->If this parameter is <CODE +>If this parameter is <TT CLASS="CONSTANT" ->yes</CODE +>yes</TT >, then users of a service may not create or modify files in the service's directory.</P @@ -14581,12 +15792,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 @@ -14599,7 +15807,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 @@ -14617,9 +15825,11 @@ NAME="READRAW" >In general this parameter should be viewed as a system tuning tool and left severely alone. See also <A HREF="#WRITERAW" -> <VAR +> <TT CLASS="PARAMETER" ->write raw</VAR +><I +>write raw</I +></TT ></A >.</P ><P @@ -14632,12 +15842,14 @@ CLASS="COMMAND" ><A NAME="READSIZE" ></A ->>read size (G)</DT +>read size (G)</DT ><DD ><P ->The option <VAR +>The option <TT CLASS="PARAMETER" ->read size</VAR +><I +>read size</I +></TT > affects the overlap of disk reads/writes with network reads/writes. If the amount of data being transferred in several of the SMB @@ -14671,7 +15883,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 @@ -14696,7 +15908,7 @@ CLASS="COMMAND" ><A NAME="REMOTEANNOUNCE" ></A ->>remote announce (G)</DT +>remote announce (G)</DT ><DD ><P >This option allows you to setup <A @@ -14727,9 +15939,11 @@ CLASS="COMMAND" If you leave out the workgroup name then the one given in the <A HREF="#WORKGROUP" -><VAR +><TT CLASS="PARAMETER" ->workgroup</VAR +><I +>workgroup</I +></TT ></A > parameter is used instead.</P @@ -14738,10 +15952,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" @@ -14758,7 +15971,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 @@ -14808,14 +16021,14 @@ CLASS="COMMAND" ><A NAME="RESTRICTANONYMOUS" ></A ->>restrict anonymous (G)</DT +>restrict anonymous (G)</DT ><DD ><P >This is a integer parameter, and mirrors as much as possible the functinality the - <CODE + <TT CLASS="CONSTANT" ->RestrictAnonymous</CODE +>RestrictAnonymous</TT > registry key does on NT/Win2k. </P ><P @@ -14828,14 +16041,16 @@ CLASS="COMMAND" ><A NAME="ROOT" ></A ->>root (G)</DT +>root (G)</DT ><DD ><P >Synonym for <A HREF="#ROOTDIRECTORY" -> <VAR +> <TT CLASS="PARAMETER" ->root directory"</VAR +><I +>root directory"</I +></TT ></A >.</P ></DD @@ -14843,14 +16058,16 @@ CLASS="PARAMETER" ><A NAME="ROOTDIR" ></A ->>root dir (G)</DT +>root dir (G)</DT ><DD ><P >Synonym for <A HREF="#ROOTDIRECTORY" -> <VAR +> <TT CLASS="PARAMETER" ->root directory"</VAR +><I +>root directory"</I +></TT ></A >.</P ></DD @@ -14858,7 +16075,7 @@ CLASS="PARAMETER" ><A NAME="ROOTDIRECTORY" ></A ->>root directory (G)</DT +>root directory (G)</DT ><DD ><P >The server will <B @@ -14872,35 +16089,40 @@ CLASS="COMMAND" parts of the filesystem, or attempts to use ".." in file names to access other directories (depending on the setting of the <A HREF="#WIDELINKS" -><VAR +><TT CLASS="PARAMETER" ->wide links</VAR +><I +>wide links</I +></TT ></A > parameter).</P ><P ->Adding a <VAR +>Adding a <TT CLASS="PARAMETER" ->root directory</VAR +><I +>root directory</I +></TT > entry other than "/" adds an extra level of security, but at a price. It absolutely ensures that no access is given to files not in the - sub-tree specified in the <VAR + sub-tree specified in the <TT CLASS="PARAMETER" ->root directory</VAR -> - option, <SPAN -CLASS="emphasis" ><I +>root directory</I +></TT +> + 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 - into the <VAR + into the <TT CLASS="PARAMETER" ->root directory</VAR +><I +>root directory</I +></TT > tree. In particular you will need to mirror <TT CLASS="FILENAME" @@ -14924,12 +16146,14 @@ CLASS="COMMAND" ><A NAME="ROOTPOSTEXEC" ></A ->>root postexec (S)</DT +>root postexec (S)</DT ><DD ><P ->This is the same as the <VAR +>This is the same as the <TT CLASS="PARAMETER" ->postexec</VAR +><I +>postexec</I +></TT > parameter except that the command is run as root. This is useful for unmounting filesystems @@ -14937,9 +16161,11 @@ CLASS="PARAMETER" ><P >See also <A HREF="#POSTEXEC" -><VAR +><TT CLASS="PARAMETER" -> postexec</VAR +><I +> postexec</I +></TT ></A >.</P ><P @@ -14953,12 +16179,14 @@ CLASS="COMMAND" ><A NAME="ROOTPREEXEC" ></A ->>root preexec (S)</DT +>root preexec (S)</DT ><DD ><P ->This is the same as the <VAR +>This is the same as the <TT CLASS="PARAMETER" ->preexec</VAR +><I +>preexec</I +></TT > parameter except that the command is run as root. This is useful for mounting filesystems (such as CDROMs) when a @@ -14966,15 +16194,19 @@ CLASS="PARAMETER" ><P >See also <A HREF="#PREEXEC" -><VAR +><TT CLASS="PARAMETER" -> preexec</VAR +><I +> preexec</I +></TT ></A > and <A HREF="#PREEXECCLOSE" -> <VAR +> <TT CLASS="PARAMETER" ->preexec close</VAR +><I +>preexec close</I +></TT ></A >.</P ><P @@ -14988,26 +16220,32 @@ CLASS="COMMAND" ><A NAME="ROOTPREEXECCLOSE" ></A ->>root preexec close (S)</DT +>root preexec close (S)</DT ><DD ><P ->This is the same as the <VAR +>This is the same as the <TT CLASS="PARAMETER" +><I >preexec close - </VAR + </I +></TT > parameter except that the command is run as root.</P ><P >See also <A HREF="#PREEXEC" -><VAR +><TT CLASS="PARAMETER" -> preexec</VAR +><I +> preexec</I +></TT ></A > and <A HREF="#PREEXECCLOSE" -> <VAR +> <TT CLASS="PARAMETER" ->preexec close</VAR +><I +>preexec close</I +></TT ></A >.</P ><P @@ -15020,7 +16258,7 @@ CLASS="COMMAND" ><A NAME="SECURITY" ></A ->>security (G)</DT +>security (G)</DT ><DD ><P >This option affects how clients respond to @@ -15030,12 +16268,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 @@ -15098,9 +16335,11 @@ CLASS="COMMAND" >, see the <A HREF="#MAPTOGUEST" -><VAR +><TT CLASS="PARAMETER" ->map to guest</VAR +><I +>map to guest</I +></TT > </A >parameter for details.</P @@ -15108,18 +16347,17 @@ 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" -> <VAR +> <TT CLASS="PARAMETER" ->NetBIOS aliases</VAR +><I +>NetBIOS aliases</I +></TT ></A >. </P ><P @@ -15128,13 +16366,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 @@ -15152,12 +16387,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 @@ -15182,17 +16414,21 @@ CLASS="COMMAND" ><P >If the <A HREF="#GUESTONLY" -><VAR +><TT CLASS="PARAMETER" +><I >guest - only</VAR + only</I +></TT ></A > parameter is set, then all the other stages are missed and only the <A HREF="#GUESTACCOUNT" -> <VAR +> <TT CLASS="PARAMETER" ->guest account</VAR +><I +>guest account</I +></TT ></A > username is checked. </P @@ -15202,22 +16438,21 @@ CLASS="PARAMETER" >Is a username is sent with the share connection request, then this username (after mapping - see <A HREF="#USERNAMEMAP" -><VAR +><TT CLASS="PARAMETER" ->username map</VAR +><I +>username map</I +></TT ></A >), is added as a potential username.</P ></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 @@ -15236,376 +16471,355 @@ CLASS="EMPHASIS" ><P >Any users on the <A HREF="#USER" -><VAR +><TT CLASS="PARAMETER" -> user</VAR +><I +> user</I +></TT ></A > list are added as potential usernames. </P ></LI ></UL ><P ->If the <VAR +>If the <TT CLASS="PARAMETER" ->guest only</VAR +><I +>guest only</I +></TT > parameter is not set, then this list is then tried with the supplied password. The first user for whom the password matches will be used as the UNIX user.</P ><P ->If the <VAR +>If the <TT CLASS="PARAMETER" ->guest only</VAR +><I +>guest only</I +></TT > parameter is set, or no username can be determined then if the share is marked - as available to the <VAR + as available to the <TT CLASS="PARAMETER" ->guest account</VAR +><I +>guest account</I +></TT >, 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="#AEN240" +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" -><VAR +><TT CLASS="PARAMETER" ->username map</VAR +><I +>username map</I +></TT ></A > parameter). Encrypted passwords (see the <A HREF="#ENCRYPTPASSWORDS" -> <VAR +> <TT CLASS="PARAMETER" ->encrypted passwords</VAR +><I +>encrypted passwords</I +></TT ></A > parameter) can also be used in this security mode. Parameters such as <A HREF="#USER" -> <VAR +> <TT CLASS="PARAMETER" ->user</VAR +><I +>user</I +></TT ></A > and <A HREF="#GUESTONLY" -> <VAR +> <TT CLASS="PARAMETER" ->guest only</VAR +><I +>guest only</I +></TT ></A > if set are then applied and 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 the server to automatically map unknown users into the <A HREF="#GUESTACCOUNT" -><VAR +><TT CLASS="PARAMETER" ->guest account</VAR +><I +>guest account</I +></TT ></A >. See the <A HREF="#MAPTOGUEST" -><VAR +><TT CLASS="PARAMETER" ->map to guest</VAR +><I +>map to guest</I +></TT > </A > parameter for details on doing this.</P ><P >See also the section <A -HREF="#AEN240" +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" -><VAR -CLASS="PARAMETER" ->encrypted passwords</VAR -> - </A -> parameter to be set to <CODE -CLASS="CONSTANT" ->yes</CODE ->. 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 the server to automatically map unknown users into the <A HREF="#GUESTACCOUNT" -><VAR +><TT CLASS="PARAMETER" ->guest account</VAR +><I +>guest account</I +></TT ></A >. See the <A HREF="#MAPTOGUEST" -><VAR +><TT CLASS="PARAMETER" ->map to guest</VAR +><I +>map to guest</I +></TT > </A > parameter for details on doing this.</P ><P >See also the section <A -HREF="#AEN240" +HREF="#AEN238" > NOTE ABOUT USERNAME/PASSWORD VALIDATION</A >.</P ><P >See also the <A HREF="#PASSWORDSERVER" -><VAR +><TT CLASS="PARAMETER" +><I >password - server</VAR + server</I +></TT ></A > parameter and the <A HREF="#ENCRYPTPASSWORDS" -><VAR +><TT CLASS="PARAMETER" ->encrypted passwords</VAR +><I +>encrypted passwords</I +></TT > </A > 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" -><VAR +><TT CLASS="PARAMETER" ->encrypted passwords</VAR +><I +>encrypted passwords</I +></TT > </A -> parameter to be set to - <CODE +> parameter to be set to <TT CLASS="CONSTANT" ->yes</CODE ->, 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 +>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 -> 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 the server to automatically map unknown users into the <A HREF="#GUESTACCOUNT" -><VAR +><TT CLASS="PARAMETER" ->guest account</VAR +><I +>guest account</I +></TT ></A >. See the <A HREF="#MAPTOGUEST" -><VAR +><TT CLASS="PARAMETER" ->map to guest</VAR +><I +>map to guest</I +></TT > </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="#AEN240" +HREF="#AEN238" > NOTE ABOUT USERNAME/PASSWORD VALIDATION</A >.</P ><P >See also the <A HREF="#PASSWORDSERVER" -><VAR +><TT CLASS="PARAMETER" +><I >password - server</VAR + server</I +></TT ></A > parameter and the <A HREF="#ENCRYPTPASSWORDS" -><VAR +><TT CLASS="PARAMETER" ->encrypted passwords</VAR +><I +>encrypted passwords</I +></TT > </A > parameter.</P @@ -15624,7 +16838,7 @@ CLASS="COMMAND" ><A NAME="SECURITYMASK" ></A ->>security mask (S)</DT +>security mask (S)</DT ><DD ><P >This parameter controls what UNIX permission @@ -15642,40 +16856,43 @@ 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 "appliance" systems. Administrators of most normal systems will - probably want to leave it set to <CODE + probably want to leave it set to <TT CLASS="CONSTANT" ->0777</CODE +>0777</TT >.</P ><P >See also the <A HREF="#FORCEDIRECTORYSECURITYMODE" -> <VAR +> <TT CLASS="PARAMETER" ->force directory security mode</VAR +><I +>force directory security mode</I +></TT ></A >, <A HREF="#DIRECTORYSECURITYMASK" -><VAR +><TT CLASS="PARAMETER" +><I >directory - security mask</VAR + security mask</I +></TT ></A >, <A HREF="#FORCESECURITYMODE" -> <VAR +> <TT CLASS="PARAMETER" ->force security mode</VAR +><I +>force security mode</I +></TT ></A > parameters.</P ><P @@ -15691,54 +16908,9 @@ CLASS="COMMAND" ></DD ><DT ><A -NAME="SERVERSCHANNEL" -></A ->>server schannel (G)</DT -><DD -><P ->This controls whether the server offers or even - demands the use of the netlogon schannel. - <VAR -CLASS="PARAMETER" ->server schannel = no</VAR -> does not - offer the schannel, <VAR -CLASS="PARAMETER" ->server schannel = - auto</VAR -> offers the schannel but does not - enforce it, and <VAR -CLASS="PARAMETER" ->server schannel = - yes</VAR -> denies access if the client is not - able to speak netlogon schannel. This is only the case - for Windows NT4 before SP4.</P -><P ->Please note that with this set to - <VAR -CLASS="PARAMETER" ->no</VAR -> you will have to apply the - WindowsXP requireSignOrSeal-Registry patch found in - the docs/Registry subdirectory.</P -><P ->Default: <B -CLASS="COMMAND" ->server schannel = auto</B -></P -><P ->Example: <B -CLASS="COMMAND" ->server schannel = yes</B ->/para> - </P -></DD -><DT -><A NAME="SERVERSTRING" ></A ->>server string (G)</DT +>server string (G)</DT ><DD ><P >This controls what string will show up in the @@ -15752,15 +16924,19 @@ CLASS="COMMAND" >It also sets what will appear in browse lists next to the machine name.</P ><P ->A <VAR +>A <TT CLASS="PARAMETER" ->%v</VAR +><I +>%v</I +></TT > will be replaced with the Samba version number.</P ><P ->A <VAR +>A <TT CLASS="PARAMETER" ->%h</VAR +><I +>%h</I +></TT > will be replaced with the hostname.</P ><P @@ -15777,51 +16953,9 @@ CLASS="COMMAND" ></DD ><DT ><A -NAME="SETPRIMARYGROUPSCRIPT" -></A ->>set primary group script (G)</DT -><DD -><P ->Thanks to the Posix subsystem in NT a - Windows User has a primary group in addition to the - auxiliary groups. This script sets the primary group - in the unix userdatase when an administrator sets the - primary group from the windows user manager or when - fetching a SAM with <B -CLASS="COMMAND" ->net rpc - vampire</B ->. <VAR -CLASS="PARAMETER" ->%u</VAR -> will be - replaced with the user whose primary group is to be - set. <VAR -CLASS="PARAMETER" ->%g</VAR -> will be replaced with - the group to set. - - </P -><P ->Default: <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->No default value</I -></SPAN -></P -><P ->Example: <B -CLASS="COMMAND" ->set primary group script = /usr/sbin/usermod -g '%g' '%u'</B -></P -></DD -><DT -><A NAME="SETDIRECTORY" ></A ->>set directory (S)</DT +>set directory (S)</DT ><DD ><P >If <B @@ -15847,13 +16981,15 @@ CLASS="COMMAND" ><A NAME="SHAREMODES" ></A ->>share modes (S)</DT +>share modes (S)</DT ><DD ><P >This enables or disables the honoring of - the <VAR + the <TT CLASS="PARAMETER" ->share modes</VAR +><I +>share modes</I +></TT > during a file open. These modes are used by clients to gain exclusive read or write access to a file.</P @@ -15863,38 +16999,35 @@ CLASS="PARAMETER" UNIX doesn't support shared memory (almost all do).</P ><P >The share modes that are enabled by this option are - <CODE + <TT CLASS="CONSTANT" ->DENY_DOS</CODE ->, <CODE +>DENY_DOS</TT +>, <TT CLASS="CONSTANT" ->DENY_ALL</CODE +>DENY_ALL</TT >, - <CODE + <TT CLASS="CONSTANT" ->DENY_READ</CODE ->, <CODE +>DENY_READ</TT +>, <TT CLASS="CONSTANT" ->DENY_WRITE</CODE +>DENY_WRITE</TT >, - <CODE + <TT CLASS="CONSTANT" ->DENY_NONE</CODE -> and <CODE +>DENY_NONE</TT +> and <TT CLASS="CONSTANT" ->DENY_FCB</CODE +>DENY_FCB</TT >. </P ><P >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 @@ -15907,7 +17040,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 @@ -15915,10 +17048,12 @@ NAME="SHORTPRESERVECASE" suitable length, are created upper case, or if they are forced to be the <A HREF="#DEFAULTCASE" -><VAR +><TT CLASS="PARAMETER" +><I >default case - </VAR + </I +></TT ></A >. This option can be use with <A HREF="#PRESERVECASE" @@ -15931,7 +17066,7 @@ CLASS="COMMAND" names are lowered. </P ><P >See the section on <A -HREF="#AEN207" +HREF="#AEN205" > NAME MANGLING</A >.</P ><P @@ -15944,7 +17079,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 @@ -15958,46 +17093,53 @@ NAME="SHOWADDPRINTERWIZARD" open a handle on the printer server with OpenPrinterEx() asking for Administrator privileges. If the user does not have administrative access on the print server (i.e is not root or a member of the - <VAR + <TT CLASS="PARAMETER" ->printer admin</VAR +><I +>printer admin</I +></TT > group), the OpenPrinterEx() call fails and the client makes another open call with a request for a lower privilege level. This should succeed, however the APW icon will not be displayed.</P ><P ->Disabling the <VAR +>Disabling the <TT CLASS="PARAMETER" ->show add printer wizard</VAR +><I +>show add printer wizard</I +></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 >See also <A HREF="#ADDPRINTERCOMMAND" -><VAR +><TT CLASS="PARAMETER" +><I >addprinter - command</VAR + command</I +></TT ></A >, <A HREF="#DELETEPRINTERCOMMAND" -> <VAR +> <TT CLASS="PARAMETER" ->deleteprinter command</VAR +><I +>deleteprinter command</I +></TT ></A >, <A HREF="#PRINTERADMIN" -><VAR +><TT CLASS="PARAMETER" ->printer admin</VAR +><I +>printer admin</I +></TT ></A ></P ><P @@ -16010,15 +17152,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 @@ -16036,52 +17175,51 @@ CLASS="COMMAND" ><P >%m %t %r %f parameters are expanded</P ><P -><VAR +><TT CLASS="PARAMETER" ->%m</VAR +><I +>%m</I +></TT > will be substituted with the shutdown message sent to the server.</P ><P -><VAR +><TT CLASS="PARAMETER" ->%t</VAR +><I +>%t</I +></TT > will be substituted with the number of seconds to wait before effectively starting the shutdown procedure.</P ><P -><VAR +><TT CLASS="PARAMETER" ->%r</VAR -> will be substituted with the - switch <SPAN -CLASS="emphasis" ><I +>%r</I +></TT +> will be substituted with the + switch <I CLASS="EMPHASIS" >-r</I -></SPAN >. It means reboot after shutdown for NT. </P ><P -><VAR +><TT CLASS="PARAMETER" ->%f</VAR -> will be substituted with the - switch <SPAN -CLASS="emphasis" ><I +>%f</I +></TT +> will be substituted with the + 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 @@ -16090,24 +17228,36 @@ 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 ><P >See also <A HREF="#ABORTSHUTDOWNSCRIPT" -><VAR +><TT CLASS="PARAMETER" ->abort shutdown script</VAR +><I +>abort shutdown script</I +></TT ></A >.</P ></DD @@ -16115,7 +17265,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 @@ -16138,7 +17288,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 @@ -16154,7 +17304,7 @@ CLASS="COMMAND" ><A NAME="SOCKETADDRESS" ></A ->>socket address (G)</DT +>socket address (G)</DT ><DD ><P >This option allows you to control what @@ -16175,7 +17325,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 @@ -16256,12 +17406,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 @@ -16309,7 +17456,7 @@ CLASS="COMMAND" ><A NAME="SOURCEENVIRONMENT" ></A ->>source environment (G)</DT +>source environment (G)</DT ><DD ><P >This parameter causes Samba to set environment @@ -16333,12 +17480,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 @@ -16357,37 +17501,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 @@ -16401,13 +17535,15 @@ CLASS="COMMAND" ><A NAME="STATCACHESIZE" ></A ->>stat cache size (G)</DT +>stat cache size (G)</DT ><DD ><P >This parameter determines the number of - entries in the <VAR + entries in the <TT CLASS="PARAMETER" ->stat cache</VAR +><I +>stat cache</I +></TT >. You should never need to change this parameter.</P ><P @@ -16420,13 +17556,13 @@ 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 - disk space allocation in the server. When this is set to <CODE + disk space allocation in the server. When this is set to <TT CLASS="CONSTANT" ->yes</CODE +>yes</TT > the server will change from UNIX behaviour of not committing real disk storage blocks when a file is extended to the Windows behaviour @@ -16435,15 +17571,15 @@ CLASS="CONSTANT" terminology this means that Samba will stop creating sparse files. This can be slow on some systems.</P ><P ->When strict allocate is <CODE +>When strict allocate is <TT CLASS="CONSTANT" ->no</CODE +>no</TT > the server does sparse disk block allocation when a file is extended.</P ><P ->Setting this to <CODE +>Setting this to <TT CLASS="CONSTANT" ->yes</CODE +>yes</TT > can help Samba return out of quota messages on systems that are restricting the disk quota of users.</P @@ -16457,20 +17593,20 @@ 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 - file locking in the server. When this is set to <CODE + file locking in the server. When this is set to <TT CLASS="CONSTANT" ->yes</CODE +>yes</TT > the server will check every read and write access for file locks, and deny access if locks exist. This can be slow on some systems.</P ><P ->When strict locking is <CODE +>When strict locking is <TT CLASS="CONSTANT" ->no</CODE +>no</TT > the server does file lock checks only when the client explicitly asks for them.</P ><P @@ -16490,7 +17626,7 @@ CLASS="COMMAND" ><A NAME="STRICTSYNC" ></A ->>strict sync (S)</DT +>strict sync (S)</DT ><DD ><P >Many Windows applications (including the Windows @@ -16499,16 +17635,14 @@ NAME="STRICTSYNC" the process to be suspended until the kernel has ensured that all outstanding data in kernel disk buffers has been safely stored onto stable storage. This is very slow and should only be done - rarely. Setting this parameter to <CODE + rarely. Setting this parameter to <TT CLASS="CONSTANT" ->no</CODE +>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 @@ -16518,10 +17652,12 @@ CLASS="REFENTRYTITLE" ><P >See also the <A HREF="#SYNCALWAYS" -><VAR +><TT CLASS="PARAMETER" +><I >sync - always></VAR + always></I +></TT ></A > parameter.</P ><P @@ -16534,7 +17670,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 @@ -16550,41 +17686,45 @@ CLASS="COMMAND" ><A NAME="SYNCALWAYS" ></A ->>sync always (S)</DT +>sync always (S)</DT ><DD ><P >This is a boolean parameter that controls whether writes will always be written to stable storage before - the write call returns. If this is <CODE + the write call returns. If this is <TT CLASS="CONSTANT" ->no</CODE +>no</TT > then the server will be guided by the client's request in each write call (clients can set a bit indicating that a particular write should be synchronous). - If this is <CODE + If this is <TT CLASS="CONSTANT" ->yes</CODE +>yes</TT > then every write will be followed by a <B CLASS="COMMAND" >fsync() </B > call to ensure the data is written to disk. Note that - the <VAR + the <TT CLASS="PARAMETER" ->strict sync</VAR +><I +>strict sync</I +></TT > parameter must be set to - <CODE + <TT CLASS="CONSTANT" ->yes</CODE +>yes</TT > in order for this parameter to have any affect.</P ><P >See also the <A HREF="#STRICTSYNC" -><VAR +><TT CLASS="PARAMETER" +><I >strict - sync</VAR + sync</I +></TT ></A > parameter.</P ><P @@ -16597,26 +17737,26 @@ CLASS="COMMAND" ><A NAME="SYSLOG" ></A ->>syslog (G)</DT +>syslog (G)</DT ><DD ><P >This parameter maps how Samba debug messages are logged onto the system syslog logging levels. Samba debug - level zero maps onto syslog <CODE + level zero maps onto syslog <TT CLASS="CONSTANT" ->LOG_ERR</CODE +>LOG_ERR</TT >, debug - level one maps onto <CODE + level one maps onto <TT CLASS="CONSTANT" ->LOG_WARNING</CODE +>LOG_WARNING</TT >, debug level - two maps onto <CODE + two maps onto <TT CLASS="CONSTANT" ->LOG_NOTICE</CODE +>LOG_NOTICE</TT >, debug level three - maps onto LOG_INFO. All higher levels are mapped to <CODE + maps onto LOG_INFO. All higher levels are mapped to <TT CLASS="CONSTANT" -> LOG_DEBUG</CODE +> LOG_DEBUG</TT >.</P ><P >This parameter sets the threshold for sending messages @@ -16632,7 +17772,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 @@ -16648,7 +17788,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 @@ -16658,14 +17798,18 @@ TARGET="_top" >winbindd(8)</A > daemon uses this parameter to fill in the home directory for that user. - If the string <VAR + If the string <TT CLASS="PARAMETER" ->%D</VAR +><I +>%D</I +></TT > is present it is substituted - with the user's Windows NT domain name. If the string <VAR + with the user's Windows NT domain name. If the string <TT CLASS="PARAMETER" +><I >%U - </VAR + </I +></TT > is present it is substituted with the user's Windows NT user name.</P ><P @@ -16678,16 +17822,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 @@ -16700,7 +17842,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 @@ -16722,15 +17864,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 @@ -16743,14 +17884,16 @@ CLASS="COMMAND" ><A NAME="TIMESTAMPLOGS" ></A ->>timestamp logs (G)</DT +>timestamp logs (G)</DT ><DD ><P >Synonym for <A HREF="#DEBUGTIMESTAMP" -><VAR +><TT CLASS="PARAMETER" -> debug timestamp</VAR +><I +> debug timestamp</I +></TT ></A >.</P ></DD @@ -16758,18 +17901,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 @@ -16777,9 +17918,11 @@ CLASS="REFENTRYTITLE" designed as a printing throttle. See also <A HREF="#MAXPRINTJOBS" -><VAR +><TT CLASS="PARAMETER" ->max print jobs</VAR +><I +>max print jobs</I +></TT ></A >. </P @@ -16798,7 +17941,7 @@ CLASS="COMMAND" ><A NAME="UNICODE" ></A ->>unicode (G)</DT +>unicode (G)</DT ><DD ><P >Specifies whether Samba should try @@ -16815,7 +17958,7 @@ CLASS="COMMAND" ><A NAME="UNIXCHARSET" ></A ->>unix charset (G)</DT +>unix charset (G)</DT ><DD ><P >Specifies the charset the unix machine @@ -16825,19 +17968,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 @@ -16856,25 +17999,24 @@ CLASS="COMMAND" ><A NAME="UNIXPASSWORDSYNC" ></A ->>unix password sync (G)</DT +>unix password sync (G)</DT ><DD ><P >This boolean parameter controls whether Samba attempts to synchronize the UNIX password with the SMB password when the encrypted SMB password in the smbpasswd file is changed. - If this is set to <CODE + If this is set to <TT CLASS="CONSTANT" ->yes</CODE -> the program specified in the <VAR +>yes</TT +> the program specified in the <TT CLASS="PARAMETER" ->passwd - program</VAR ->parameter is called <SPAN -CLASS="emphasis" ><I +>passwd + program</I +></TT +>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 @@ -16882,16 +18024,20 @@ CLASS="EMPHASIS" ><P >See also <A HREF="#PASSWDPROGRAM" -><VAR +><TT CLASS="PARAMETER" +><I >passwd - program</VAR + program</I +></TT ></A >, <A HREF="#PASSWDCHAT" -><VAR +><TT CLASS="PARAMETER" -> passwd chat</VAR +><I +> passwd chat</I +></TT ></A >.</P ><P @@ -16904,7 +18050,7 @@ CLASS="COMMAND" ><A NAME="UPDATEENCRYPTED" ></A ->>update encrypted (G)</DT +>update encrypted (G)</DT ><DD ><P >This boolean parameter allows a user logging @@ -16919,25 +18065,27 @@ NAME="UPDATEENCRYPTED" change is made. This is a convenience option to allow the change over to encrypted passwords to be made over a longer period. Once all users have encrypted representations of their passwords in the smbpasswd - file this parameter should be set to <CODE + file this parameter should be set to <TT CLASS="CONSTANT" ->no</CODE +>no</TT >.</P ><P >In order for this parameter to work correctly the <A HREF="#ENCRYPTPASSWORDS" -><VAR +><TT CLASS="PARAMETER" ->encrypt passwords</VAR +><I +>encrypt passwords</I +></TT > </A -> parameter must be set to <CODE +> parameter must be set to <TT CLASS="CONSTANT" ->no</CODE +>no</TT > when - this parameter is set to <CODE + this parameter is set to <TT CLASS="CONSTANT" ->yes</CODE +>yes</TT >.</P ><P >Note that even when this parameter is set a user @@ -16957,7 +18105,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 @@ -16986,14 +18134,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 @@ -17011,15 +18156,15 @@ 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 depend on mmap working correctly on the running system. Samba requires a coherent mmap/read-write system memory cache. Currently only HPUX does not have such a - coherent cache, and so this parameter is set to <CODE + coherent cache, and so this parameter is set to <TT CLASS="CONSTANT" ->no</CODE +>no</TT > by default on HPUX. On all other systems this parameter should be left alone. This parameter is provided to help the Samba developers track down problems with @@ -17033,16 +18178,60 @@ CLASS="COMMAND" ></DD ><DT ><A +NAME="USERHOSTS" +></A +>use rhosts (G)</DT +><DD +><P +>If this global parameter is <TT +CLASS="CONSTANT" +>yes</TT +>, it specifies + that the UNIX user's <TT +CLASS="FILENAME" +>.rhosts</TT +> file in their home directory + will be read to find the names of hosts and users who will be allowed + access without specifying a password.</P +><P +><I +CLASS="EMPHASIS" +>NOTE:</I +> The use of <TT +CLASS="PARAMETER" +><I +>use rhosts + </I +></TT +> can be a major security hole. This is because you are + trusting the PC to supply the correct username. It is very easy to + get a PC to supply a false username. I recommend that the <TT +CLASS="PARAMETER" +><I +> use rhosts</I +></TT +> option be only used if you really know what + you are doing.</P +><P +>Default: <B +CLASS="COMMAND" +>use rhosts = no</B +></P +></DD +><DT +><A NAME="USER" ></A ->>user (S)</DT +>user (S)</DT ><DD ><P >Synonym for <A HREF="#USERNAME" -><VAR +><TT CLASS="PARAMETER" -> username</VAR +><I +> username</I +></TT ></A >.</P ></DD @@ -17050,14 +18239,16 @@ CLASS="PARAMETER" ><A NAME="USERS" ></A ->>users (S)</DT +>users (S)</DT ><DD ><P >Synonym for <A HREF="#USERNAME" -><VAR +><TT CLASS="PARAMETER" -> username</VAR +><I +> username</I +></TT ></A >.</P ></DD @@ -17065,31 +18256,37 @@ CLASS="PARAMETER" ><A NAME="USERNAME" ></A ->>username (S)</DT +>username (S)</DT ><DD ><P >Multiple users may be specified in a comma-delimited list, in which case the supplied password will be tested against each username in turn (left to right).</P ><P ->The <VAR +>The <TT CLASS="PARAMETER" ->username</VAR +><I +>username</I +></TT > line is needed only when the PC is unable to supply its own username. This is the case for the COREPLUS protocol or where your users have different WfWg usernames to UNIX usernames. In both these cases you may also be better using the \\server\share%user syntax instead.</P ><P ->The <VAR +>The <TT CLASS="PARAMETER" ->username</VAR +><I +>username</I +></TT > line is not a great solution in many cases as it means Samba will try to validate the supplied password against each of the usernames in the - <VAR + <TT CLASS="PARAMETER" ->username</VAR +><I +>username</I +></TT > line in turn. This is slow and a bad idea for lots of users in case of duplicate passwords. You may get timeouts or security breaches using this parameter @@ -17106,10 +18303,12 @@ CLASS="PARAMETER" >To restrict a service to a particular set of users you can use the <A HREF="#VALIDUSERS" -><VAR +><TT CLASS="PARAMETER" +><I >valid users - </VAR + </I +></TT ></A > parameter.</P ><P @@ -17123,7 +18322,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 @@ -17133,7 +18332,7 @@ CLASS="PARAMETER" search.</P ><P >See the section <A -HREF="#AEN240" +HREF="#AEN238" >NOTE ABOUT USERNAME/PASSWORD VALIDATION</A > for more information on how @@ -17155,7 +18354,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 @@ -17169,10 +18368,10 @@ NAME="USERNAMELEVEL" combinations to try while trying to determine the UNIX user name. The higher the number the more combinations will be tried, but the slower the discovery of usernames will be. Use this parameter when you have - strange usernames on your UNIX machine, such as <CODE + strange usernames on your UNIX machine, such as <TT CLASS="CONSTANT" >AstrangeUser - </CODE + </TT >.</P ><P >Default: <B @@ -17189,7 +18388,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 @@ -17222,16 +18421,16 @@ NAME="USERNAMEMAP" Using '!' is most useful when you have a wildcard mapping line later in the file.</P ><P ->For example to map from the name <CODE +>For example to map from the name <TT CLASS="CONSTANT" ->admin</CODE +>admin</TT > - or <CODE + or <TT CLASS="CONSTANT" ->administrator</CODE -> to the UNIX name <CODE +>administrator</TT +> to the UNIX name <TT CLASS="CONSTANT" -> root</CODE +> root</TT > you would use:</P ><P ><B @@ -17239,13 +18438,13 @@ CLASS="COMMAND" >root = admin administrator</B ></P ><P ->Or to map anyone in the UNIX group <CODE +>Or to map anyone in the UNIX group <TT CLASS="CONSTANT" ->system</CODE +>system</TT > - to the UNIX name <CODE + to the UNIX name <TT CLASS="CONSTANT" ->sys</CODE +>sys</TT > you would use:</P ><P ><B @@ -17279,34 +18478,46 @@ 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 - of usernames. Thus if you connect to \\server\fred and <CODE + of usernames. Thus if you connect to \\server\fred and <TT CLASS="CONSTANT" -> fred</CODE -> is remapped to <CODE +> fred</TT +> is remapped to <TT CLASS="CONSTANT" ->mary</CODE +>mary</TT > then you will actually be connecting to \\server\mary and will need to - supply a password suitable for <CODE + supply a password suitable for <TT CLASS="CONSTANT" ->mary</CODE +>mary</TT > not - <CODE + <TT CLASS="CONSTANT" ->fred</CODE +>fred</TT >. The only exception to this is the username passed to the <A HREF="#PASSWORDSERVER" -><VAR +><TT CLASS="PARAMETER" -> password server</VAR +><I +> password server</I +></TT ></A > (if you have one). The password server will receive whatever username the client supplies without @@ -17317,12 +18528,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 @@ -17335,12 +18543,12 @@ CLASS="COMMAND" ><A NAME="USESENDFILE" ></A ->>use sendfile (S)</DT +>use sendfile (S)</DT ><DD ><P ->If this parameter is <CODE +>If this parameter is <TT CLASS="CONSTANT" ->yes</CODE +>yes</TT >, and Samba was built with the --with-sendfile-support option, and the underlying operating system supports sendfile system call, then some SMB read calls (mainly ReadAndX @@ -17359,16 +18567,16 @@ CLASS="COMMAND" ><A NAME="UTMP" ></A ->>utmp (G)</DT +>utmp (G)</DT ><DD ><P >This boolean parameter is only available if Samba has been configured and compiled with the option <B CLASS="COMMAND" > --with-utmp</B ->. If set to <CODE +>. If set to <TT CLASS="CONSTANT" ->yes</CODE +>yes</TT > then Samba will attempt to add utmp or utmpx records (depending on the UNIX system) whenever a connection is made to a Samba server. Sites may use this to record the @@ -17382,9 +18590,11 @@ CLASS="CONSTANT" ><P >See also the <A HREF="#UTMPDIRECTORY" -><VAR +><TT CLASS="PARAMETER" -> utmp directory</VAR +><I +> utmp directory</I +></TT ></A > parameter.</P ><P @@ -17397,7 +18607,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 @@ -17408,9 +18618,11 @@ CLASS="COMMAND" used to store the utmp or utmpx files (depending on the UNIX system) that record user connections to a Samba server. See also the <A HREF="#UTMP" -> <VAR +> <TT CLASS="PARAMETER" ->utmp</VAR +><I +>utmp</I +></TT ></A > parameter. By default this is not set, meaning the system will use whatever utmp file the @@ -17420,12 +18632,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 @@ -17437,7 +18646,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 @@ -17452,9 +18661,11 @@ CLASS="COMMAND" See also the <A HREF="#UTMP" -> <VAR +> <TT CLASS="PARAMETER" ->utmp</VAR +><I +>utmp</I +></TT ></A > parameter. By default this is not set, meaning the system will use whatever utmp file the @@ -17464,12 +18675,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 @@ -17481,46 +18689,51 @@ 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 '&' are interpreted using the same rules as described in the - <VAR + <TT CLASS="PARAMETER" ->invalid users</VAR +><I +>invalid users</I +></TT > parameter.</P ><P >If this is empty (the default) then any user can login. - If a username is in both this list and the <VAR + If a username is in both this list and the <TT CLASS="PARAMETER" +><I >invalid - users</VAR + users</I +></TT > list then access is denied for that user.</P ><P ->The current servicename is substituted for <VAR +>The current servicename is substituted for <TT CLASS="PARAMETER" +><I >%S - </VAR + </I +></TT >. This is useful in the [homes] section.</P ><P >See also <A HREF="#INVALIDUSERS" -><VAR +><TT CLASS="PARAMETER" +><I >invalid users - </VAR + </I +></TT ></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 @@ -17532,7 +18745,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 @@ -17542,18 +18755,17 @@ 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 ->Note that the <VAR +>Note that the <TT CLASS="PARAMETER" ->case sensitive</VAR +><I +>case sensitive</I +></TT > option is applicable in vetoing files.</P ><P @@ -17561,20 +18773,21 @@ 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 <VAR + the <TT CLASS="PARAMETER" ->delete veto files</VAR +><I +>delete veto files</I +></TT > parameter to - <VAR + <TT CLASS="PARAMETER" ->yes</VAR +><I +>yes</I +></TT >.</P ><P >Setting this parameter will affect the performance @@ -17583,29 +18796,36 @@ CLASS="PARAMETER" ><P >See also <A HREF="#HIDEFILES" -><VAR +><TT CLASS="PARAMETER" +><I >hide files - </VAR + </I +></TT ></A > and <A HREF="#CASESENSITIVE" -><VAR +><TT CLASS="PARAMETER" -> case sensitive</VAR +><I +> case sensitive</I +></TT ></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 @@ -17615,20 +18835,25 @@ 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 HREF="#OPLOCKS" -><VAR +><TT CLASS="PARAMETER" ->oplocks</VAR +><I +>oplocks</I +></TT ></A > parameter is turned on for a share. It allows the Samba administrator @@ -17636,20 +18861,19 @@ CLASS="PARAMETER" match a wildcarded list, similar to the wildcarded list used in the <A HREF="#VETOFILES" -><VAR +><TT CLASS="PARAMETER" ->veto files</VAR +><I +>veto files</I +></TT ></A > 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 @@ -17673,7 +18897,7 @@ CLASS="COMMAND" ><A NAME="VFSPATH" ></A ->>vfs path (S)</DT +>vfs path (S)</DT ><DD ><P >This parameter specifies the directory @@ -17698,7 +18922,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 @@ -17706,63 +18930,56 @@ 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 to the vfs layer at initialization time. See also <A HREF="#VFSOBJECT" -><VAR +><TT CLASS="PARAMETER" -> vfs object</VAR +><I +> vfs object</I +></TT ></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 @@ -17784,16 +19001,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 @@ -17807,19 +19022,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" @@ -17829,25 +19044,24 @@ CLASS="COMMAND" CLASS="COMMAND" >endpwent()</B > group of system calls. If - the <VAR + the <TT CLASS="PARAMETER" ->winbind enum users</VAR +><I +>winbind enum users</I +></TT > parameter is - <CODE + <TT CLASS="CONSTANT" ->no</CODE +>no</TT >, calls to the <B CLASS="COMMAND" >getpwent</B > 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 @@ -17863,19 +19077,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" @@ -17885,25 +19099,24 @@ CLASS="COMMAND" CLASS="COMMAND" >endgrent()</B > group of system calls. If - the <VAR + the <TT CLASS="PARAMETER" ->winbind enum groups</VAR +><I +>winbind enum groups</I +></TT > parameter is - <CODE + <TT CLASS="CONSTANT" ->no</CODE +>no</TT >, calls to the <B CLASS="COMMAND" >getgrent()</B > 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 @@ -17918,16 +19131,14 @@ 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 @@ -17947,17 +19158,21 @@ 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 - used when listing a username of the form of <VAR + used when listing a username of the form of <TT CLASS="REPLACEABLE" +><I >DOMAIN - </VAR ->\<VAR + </I +></TT +>\<TT CLASS="REPLACEABLE" ->user</VAR +><I +>user</I +></TT >. This parameter is only applicable when using the <TT CLASS="FILENAME" @@ -17987,16 +19202,14 @@ 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 @@ -18013,20 +19226,18 @@ 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 @@ -18046,7 +19257,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 @@ -18111,7 +19322,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 @@ -18120,9 +19331,9 @@ TARGET="_top" >nmbd(8)</A > will respond to broadcast name queries on behalf of other hosts. You may need to set this - to <CODE + to <TT CLASS="CONSTANT" ->yes</CODE +>yes</TT > for some older clients.</P ><P >Default: <B @@ -18134,116 +19345,70 @@ 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 ->If you want to work in multiple namespaces, you can - give every wins server a 'tag'. For each tag, only one - (working) server will be queried for a name. The tag should be - seperated from the ip address by a colon. - </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 need to set up Samba to point +><I +CLASS="EMPHASIS" +>NOTE</I +>. 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 -></TD -></TR -></TABLE -></DIV ><P ->See the documentation file <A -HREF="improved-browsing.html" -TARGET="_top" ->Browsing</A -> in the samba howto collection.</P +>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 CLASS="COMMAND" ->wins server = mary:192.9.200.1 fred:192.168.3.199 mary:192.168.2.61</B -></P -><P ->For this example when querying a certain name, 192.19.200.1 will - be asked first and if that doesn't respond 192.168.2.61. If either - of those doesn't know the name 192.168.3.199 will be queried. - </P -><P ->Example: <B -CLASS="COMMAND" ->wins server = 192.9.200.1 192.168.2.61</B +>wins server = 192.9.200.1</B ></P ></DD ><DT ><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 <CODE + not set this to <TT CLASS="CONSTANT" ->yes</CODE +>yes</TT > unless you have a multi-subnetted network and you wish a particular <B 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 <CODE +> set this to <TT CLASS="CONSTANT" ->yes</CODE +>yes</TT > on more than one machine in your network.</P ><P @@ -18256,7 +19421,7 @@ CLASS="COMMAND" ><A NAME="WORKGROUP" ></A ->>workgroup (G)</DT +>workgroup (G)</DT ><DD ><P >This controls what workgroup your server will @@ -18270,12 +19435,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 @@ -18287,14 +19449,16 @@ CLASS="COMMAND" ><A NAME="WRITABLE" ></A ->>writable (S)</DT +>writable (S)</DT ><DD ><P >Synonym for <A HREF="#WRITEABLE" -><VAR +><TT CLASS="PARAMETER" -> writeable</VAR +><I +> writeable</I +></TT ></A > for people who can't spell :-).</P ></DD @@ -18302,17 +19466,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. @@ -18346,16 +19507,18 @@ 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 access to a service. If the connecting user is in this list then they will be given write access, no matter what the <A HREF="#READONLY" -><VAR +><TT CLASS="PARAMETER" ->read only</VAR +><I +>read only</I +></TT ></A > option is set to. The list can include group names using the @@ -18366,10 +19529,12 @@ CLASS="PARAMETER" ><P >See also the <A HREF="#READLIST" -><VAR +><TT CLASS="PARAMETER" +><I >read list - </VAR + </I +></TT ></A > option.</P ><P @@ -18389,7 +19554,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 @@ -18413,14 +19578,16 @@ CLASS="COMMAND" ><A NAME="WRITEOK" ></A ->>write ok (S)</DT +>write ok (S)</DT ><DD ><P >Inverted synonym for <A HREF="#READONLY" -><VAR +><TT CLASS="PARAMETER" -> read only</VAR +><I +> read only</I +></TT ></A >.</P ></DD @@ -18428,7 +19595,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 @@ -18444,14 +19611,16 @@ CLASS="COMMAND" ><A NAME="WRITEABLE" ></A ->>writeable (S)</DT +>writeable (S)</DT ><DD ><P >Inverted synonym for <A HREF="#READONLY" -><VAR +><TT CLASS="PARAMETER" -> read only</VAR +><I +> read only</I +></TT ></A >.</P ></DD @@ -18461,7 +19630,7 @@ CLASS="PARAMETER" ><DIV CLASS="REFSECT1" ><A -NAME="AEN6291" +NAME="AEN6215" ></A ><H2 >WARNINGS</H2 @@ -18472,12 +19641,11 @@ NAME="AEN6291" 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 @@ -18492,81 +19660,97 @@ CLASS="REFENTRYTITLE" ><DIV CLASS="REFSECT1" ><A -NAME="AEN6299" +NAME="AEN6221" ></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="AEN6302" +NAME="AEN6224" ></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="AEN6332" +NAME="AEN6244" ></A ><H2 >AUTHOR</H2 @@ -18578,14 +19762,14 @@ NAME="AEN6332" ><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 fa70a288cd..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.7"></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 @@ -37,22 +37,20 @@ NAME="AEN8" ><B CLASS="COMMAND" >smbcacls</B -> {//server/share} {filename} [-D acls] [-M acls] [-A acls] [-S acls] [-C name] [-G name] [-n] [-t] [-U username] [-h] [-d]</P +> {//server/share} {filename} [-U username] [-A acls] [-M acls] [-D acls] [-S acls] [-C name] [-G name] [-n] [-h]</P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN24" +NAME="AEN22" ></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 >The <B @@ -64,7 +62,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN32" +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 @@ -134,9 +129,11 @@ CLASS="REFENTRYTITLE" ><DD ><P >The owner of a file or directory can be changed - to the name given using the <VAR + to the name given using the <TT CLASS="PARAMETER" ->-C</VAR +><I +>-C</I +></TT > option. The name can be a sid in the form S-1-x-y-z or a name resolved against the server specified in the first argument. </P @@ -149,9 +146,11 @@ CLASS="PARAMETER" ><DD ><P >The group owner of a file or directory can - be changed to the name given using the <VAR + be changed to the name given using the <TT CLASS="PARAMETER" ->-G</VAR +><I +>-G</I +></TT > option. The name can be a sid in the form S-1-x-y-z or a name resolved against the server specified n the first argument. @@ -168,98 +167,14 @@ CLASS="PARAMETER" and masks to a readable string format. </P ></DD ><DT ->-t</DT +>-h</DT ><DD ><P -> Don't actually do anything, only validate the correctness of - the arguments. - </P -></DD -><DT ->-h|--help</DT -><DD -><P ->Print a summary of command line options.</P -></DD -><DT ->-V</DT -><DD -><P ->Prints the version number for -<B +>Print usage information on the <B CLASS="COMMAND" ->smbd</B ->.</P -></DD -><DT ->-s <configuration file></DT -><DD -><P ->The file specified contains the -configuration details required by the server. The -information in this file includes server-specific -information such as what printcap file to use, as well -as descriptions of all the services that the server is -to provide. See <A -HREF="smb.conf.5.html" -TARGET="_top" -><TT -CLASS="FILENAME" ->smb.conf(5)</TT -></A -> for more information. -The default configuration file name is determined at -compile time.</P -></DD -><DT ->-d|--debug=debuglevel</DT -><DD -><P -><VAR -CLASS="REPLACEABLE" ->debuglevel</VAR -> is an integer -from 0 to 10. The default value if this parameter is -not specified is zero.</P -><P ->The higher this value, the more detail will be -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 -information about operations carried out.</P -><P ->Levels above 1 will generate considerable -amounts of log data, and should only be used when -investigating a problem. Levels above 3 are designed for -use only by developers and generate HUGE amounts of log -data, most of which is extremely cryptic.</P -><P ->Note that specifying this parameter here will -override the <A -HREF="smb.conf.5.html#loglevel" -TARGET="_top" ->log -level</A -> parameter in the <A -HREF="smb.conf.5.html" -TARGET="_top" -><TT -CLASS="FILENAME" ->smb.conf(5)</TT -></A -> file.</P -></DD -><DT ->-l|--logfile=logbasename</DT -><DD -><P ->File name for log/debug files. The extension -<CODE -CLASS="CONSTANT" ->".client"</CODE -> will be appended. The log file is -never removed by the client.</P +>smbcacls + </B +> program.</P ></DD ></DL ></DIV @@ -267,7 +182,7 @@ never removed by the client.</P ><DIV CLASS="REFSECT1" ><A -NAME="AEN111" +NAME="AEN75" ></A ><H2 >ACL FORMAT</H2 @@ -278,10 +193,11 @@ NAME="AEN111" ><PRE CLASS="PROGRAMLISTING" > -REVISION:<revision number> -OWNER:<sid or name> -GROUP:<sid or name> -ACL:<sid or name>:<type>/<flags>/<mask></PRE +REVISION:<revision number> +OWNER:<sid or name> +GROUP:<sid or name> +ACL:<sid or name>:<type>/<flags>/<mask> + </PRE ></P ><P >The revision of the ACL specifies the internal Windows @@ -295,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 -><CODE -CLASS="CONSTANT" ->#define SEC_ACE_FLAG_OBJECT_INHERIT 0x1</CODE -></P +>#define SEC_ACE_FLAG_OBJECT_INHERIT 0x1</P ></LI ><LI ><P -><CODE -CLASS="CONSTANT" ->#define SEC_ACE_FLAG_CONTAINER_INHERIT 0x2</CODE -></P +>#define SEC_ACE_FLAG_CONTAINER_INHERIT 0x2</P ></LI ><LI ><P -><CODE -CLASS="CONSTANT" ->#define SEC_ACE_FLAG_NO_PROPAGATE_INHERIT 0x4</CODE -></P +>#define SEC_ACE_FLAG_NO_PROPAGATE_INHERIT 0x4 + </P ></LI ><LI ><P -><CODE -CLASS="CONSTANT" ->#define SEC_ACE_FLAG_INHERIT_ONLY 0x8</CODE -></P +>#define SEC_ACE_FLAG_INHERIT_ONLY 0x8</P ></LI ></UL ><P @@ -451,7 +356,7 @@ CLASS="EMPHASIS" ><DIV CLASS="REFSECT1" ><A -NAME="AEN165" +NAME="AEN125" ></A ><H2 >EXIT STATUS</H2 @@ -475,17 +380,18 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN171" +NAME="AEN131" ></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="AEN174" +NAME="AEN134" ></A ><H2 >AUTHOR</H2 @@ -502,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 9ea84de950..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.7"></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 @@ -94,14 +89,18 @@ CLASS="VARIABLELIST" <TT CLASS="FILENAME" >//server/service</TT -> where <VAR +> where <TT CLASS="PARAMETER" +><I >server - </VAR + </I +></TT > is the NetBIOS name of the SMB/CIFS server - offering the desired service and <VAR + offering the desired service and <TT CLASS="PARAMETER" ->service</VAR +><I +>service</I +></TT > is the name of the service offered. Thus to connect to the service "printer" on the SMB/CIFS server "smbserver", @@ -118,20 +117,18 @@ CLASS="FILENAME" </P ><P >The server name is looked up according to either - the <VAR + the <TT CLASS="PARAMETER" ->-R</VAR +><I +>-R</I +></TT > parameter to <B 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 @@ -142,21 +139,27 @@ CLASS="REFENTRYTITLE" ><P >The password required to access the specified service on the specified server. If this parameter is - supplied, the <VAR + supplied, the <TT CLASS="PARAMETER" ->-N</VAR +><I +>-N</I +></TT > option (suppress password prompt) is assumed. </P ><P >There is no default password. If no password is supplied on the command line (either by using this parameter or adding - a password to the <VAR + a password to the <TT CLASS="PARAMETER" ->-U</VAR +><I +>-U</I +></TT > option (see - below)) and the <VAR + below)) and the <TT CLASS="PARAMETER" ->-N</VAR +><I +>-N</I +></TT > option is not specified, the client will prompt for a password, even if the desired service does not require one. (If no password is @@ -172,7 +175,28 @@ CLASS="PARAMETER" </P ></DD ><DT ->-R <name resolve order></DT +>-s smb.conf</DT +><DD +><P +>Specifies the location of the all important + <TT +CLASS="FILENAME" +>smb.conf</TT +> file. </P +></DD +><DT +>-O socket options</DT +><DD +><P +>TCP socket options to set on the client + socket. See the socket options parameter in the <TT +CLASS="FILENAME" +> smb.conf (5)</TT +> manpage for the list of valid + options. </P +></DD +><DT +>-R <name resolve order></DT ><DD ><P >This option is used by the programs in the Samba @@ -181,33 +205,30 @@ CLASS="PARAMETER" 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 ><LI ><P -><CODE +><TT CLASS="CONSTANT" ->lmhosts</CODE ->: Lookup an IP +>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 + 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 -><CODE +><TT CLASS="CONSTANT" ->host</CODE ->: Do a standard host +>host</TT +> : Do a standard host name to IP address resolution, using the system <TT CLASS="FILENAME" >/etc/hosts @@ -224,27 +245,31 @@ CLASS="FILENAME" ></LI ><LI ><P -><CODE +><TT CLASS="CONSTANT" ->wins</CODE ->: Query a name with - the IP address listed in the <VAR +>wins</TT +> : Query a name with + the IP address listed in the <TT CLASS="PARAMETER" ->wins server</VAR +><I +>wins server</I +></TT > parameter. If no WINS server has been specified this method will be ignored.</P ></LI ><LI ><P -><CODE +><TT CLASS="CONSTANT" ->bcast</CODE ->: Do a broadcast on +>bcast</TT +> : Do a broadcast on each of the known local interfaces listed in the - <VAR + <TT CLASS="PARAMETER" ->interfaces</VAR +><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 @@ -253,26 +278,22 @@ 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 >The default order is lmhosts, host, wins, bcast and without - this parameter or any entry in the <VAR + this parameter or any entry in the <TT CLASS="PARAMETER" +><I >name resolve order - </VAR -> parameter of the <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smb.conf</SPAN ->(5)</SPAN + </I +></TT +> parameter of the <TT +CLASS="FILENAME" +>smb.conf</TT > file the name resolution methods will be attempted in this order. </P ></DD @@ -308,25 +329,23 @@ CLASS="FILENAME" > to the machine FRED. </P ><P ->You may also find the <VAR +>You may also find the <TT CLASS="PARAMETER" ->-U</VAR +><I +>-U</I +></TT > and - <VAR + <TT CLASS="PARAMETER" ->-I</VAR +><I +>-I</I +></TT > options useful, as they allow you to control the FROM and TO parts of the message. </P ><P ->See the <VAR -CLASS="PARAMETER" ->message command</VAR -> 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 @@ -341,6 +360,106 @@ CLASS="EMPHASIS" messages. </P ></DD ><DT +>-i scope</DT +><DD +><P +>This specifies a NetBIOS scope that smbclient will + use to communicate with when generating NetBIOS names. For details + on the use of NetBIOS scopes, see <TT +CLASS="FILENAME" +>rfc1001.txt</TT +> + and <TT +CLASS="FILENAME" +>rfc1002.txt</TT +>. + NetBIOS scopes are <SPAN +CLASS="emphasis" +><I +CLASS="EMPHASIS" +>very</I +></SPAN +> rarely used, only set + this parameter if you are the system administrator in charge of all + the NetBIOS systems you communicate with. </P +></DD +><DT +>-N</DT +><DD +><P +>If specified, this parameter suppresses the normal + password prompt from the client to the user. This is useful when + accessing a service that does not require a password. </P +><P +>Unless a password is specified on the command line or + this parameter is specified, the client will request a + password.</P +></DD +><DT +>-n NetBIOS name</DT +><DD +><P +>By default, the client will use the local + machine's hostname (in uppercase) as its NetBIOS name. This parameter + allows you to override the host name and use whatever NetBIOS + name you wish. </P +></DD +><DT +>-d debuglevel</DT +><DD +><P +><TT +CLASS="REPLACEABLE" +><I +>debuglevel</I +></TT +> is an integer from 0 to 10, or + the letter 'A'. </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 to + the log files about the activities of the + client. 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 information about operations + carried out. </P +><P +>Levels above 1 will generate considerable amounts of log + data, and should only be used when investigating a problem. + Levels above 3 are designed for use only by developers and + generate HUGE amounts of log data, most of which is extremely + cryptic. If <TT +CLASS="REPLACEABLE" +><I +>debuglevel</I +></TT +> is set to the letter 'A', then <SPAN +CLASS="emphasis" +><I +CLASS="EMPHASIS" +>all + </I +></SPAN +> debug messages will be printed. This setting + is for developers only (and people who <SPAN +CLASS="emphasis" +><I +CLASS="EMPHASIS" +>really</I +></SPAN +> want + to know how the code works internally). </P +><P +>Note that specifying this parameter here will override + the log level parameter in the <TT +CLASS="FILENAME" +>smb.conf (5)</TT +> + file. </P +></DD +><DT >-p port</DT ><DD ><P @@ -353,9 +472,11 @@ CLASS="EMPHASIS" >-l logfilename</DT ><DD ><P ->If specified, <VAR +>If specified, <TT CLASS="REPLACEABLE" ->logfilename</VAR +><I +>logfilename</I +></TT > specifies a base filename into which operational data from the running client will be logged. </P @@ -373,26 +494,30 @@ CLASS="FILENAME" </P ></DD ><DT ->-h|--help</DT +>-h</DT ><DD ><P ->Print a summary of command line options.</P +>Print the usage message for the client. </P ></DD ><DT >-I IP-address</DT ><DD ><P -><VAR +><TT CLASS="REPLACEABLE" ->IP address</VAR +><I +>IP address</I +></TT > is the address of the server to connect to. It should be specified in standard "a.b.c.d" notation. </P ><P >Normally the client would attempt to locate a named SMB/CIFS server by looking it up via the NetBIOS name resolution - mechanism described above in the <VAR + mechanism described above in the <TT CLASS="PARAMETER" ->name resolve order</VAR +><I +>name resolve order</I +></TT > parameter above. Using this parameter will force the client to assume that the server is on the machine with the specified IP @@ -415,6 +540,89 @@ CLASS="PARAMETER" - typically the user's tty. </P ></DD ><DT +>-U username[%pass]</DT +><DD +><P +>Sets the SMB username or username and password. + If %pass is not specified, The user will be prompted. The client + will first check the <TT +CLASS="ENVAR" +>USER</TT +> environment variable, then the + <TT +CLASS="ENVAR" +>LOGNAME</TT +> variable and if either exists, the + string is uppercased. Anything in these variables following a '%' + sign will be treated as the password. If these environment + variables are not found, the username <TT +CLASS="CONSTANT" +>GUEST</TT +> + is used. </P +><P +>If the password is not included in these environment + variables (using the %pass syntax), <B +CLASS="COMMAND" +>smbclient</B +> will look for + a <TT +CLASS="ENVAR" +>PASSWD</TT +> environment variable from which + to read the password. </P +><P +>A third option is to use a credentials file which + contains the plaintext of the domain name, username and password. This + option is mainly provided for scripts where the admin doesn't + wish to pass the credentials on the command line or via environment + variables. If this method is used, make certain that the permissions + on the file restrict access from unwanted users. See the + <TT +CLASS="PARAMETER" +><I +>-A</I +></TT +> for more details. </P +><P +>Be cautious about including passwords in scripts or in + the <TT +CLASS="ENVAR" +>PASSWD</TT +> environment variable. Also, on + many systems the command line of a running process may be seen + via the <B +CLASS="COMMAND" +>ps</B +> command to be safe always allow + <B +CLASS="COMMAND" +>smbclient</B +> to prompt for a password and type + it in directly. </P +></DD +><DT +>-A filename</DT +><DD +><P +>This option allows + you to specify a file from which to read the username, domain name, and + password used in the connection. The format of the file is + </P +><P +><PRE +CLASS="PROGRAMLISTING" +>username = <value> +password = <value> +domain = <value> + </PRE +></P +><P +>If the domain parameter is missing the current workgroup name + is used instead. Make certain that the permissions on the file restrict + access from unwanted users. </P +></DD +><DT >-L</DT ><DD ><P @@ -423,10 +631,12 @@ CLASS="PARAMETER" CLASS="COMMAND" >smbclient -L host</B -> and a list should appear. The <VAR +> and a list should appear. The <TT CLASS="PARAMETER" +><I >-I - </VAR + </I +></TT > option may be useful if your NetBIOS names don't match your TCP/IP DNS host names or if you are trying to reach a host on another network. </P @@ -476,241 +686,16 @@ CLASS="COMMAND" </P ></DD ><DT ->-V</DT +>-W WORKGROUP</DT ><DD ><P ->Prints the version number for -<B -CLASS="COMMAND" ->smbd</B ->.</P -></DD -><DT ->-s <configuration file></DT -><DD -><P ->The file specified contains the -configuration details required by the server. The -information in this file includes server-specific -information such as what printcap file to use, as well -as descriptions of all the services that the server is -to provide. See <A -HREF="smb.conf.5.html" -TARGET="_top" -><TT -CLASS="FILENAME" ->smb.conf(5)</TT -></A -> for more information. -The default configuration file name is determined at -compile time.</P -></DD -><DT ->-d|--debug=debuglevel</DT -><DD -><P -><VAR -CLASS="REPLACEABLE" ->debuglevel</VAR -> is an integer -from 0 to 10. The default value if this parameter is -not specified is zero.</P -><P ->The higher this value, the more detail will be -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 -information about operations carried out.</P -><P ->Levels above 1 will generate considerable -amounts of log data, and should only be used when -investigating a problem. Levels above 3 are designed for -use only by developers and generate HUGE amounts of log -data, most of which is extremely cryptic.</P -><P ->Note that specifying this parameter here will -override 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 +>Override the default workgroup (domain) specified + in the workgroup parameter of the <TT CLASS="FILENAME" ->smb.conf(5)</TT -></A -> file.</P -></DD -><DT ->-l|--logfile=logbasename</DT -><DD -><P ->File name for log/debug files. The extension -<CODE -CLASS="CONSTANT" ->".client"</CODE -> will be appended. The log file is -never removed by the client.</P -></DD -><DT ->-N</DT -><DD -><P ->If specified, this parameter suppresses the normal -password prompt from the client to the user. This is useful when -accessing a service that does not require a password. </P -><P ->Unless a password is specified on the command line or -this parameter is specified, the client will request a -password.</P -></DD -><DT ->-k</DT -><DD -><P ->Try to authenticate with kerberos. Only useful in -an Active Directory environment.</P -></DD -><DT ->-A|--authfile=filename</DT -><DD -><P ->This option allows -you to specify a file from which to read the username and -password used in the connection. The format of the file is</P -><P -><PRE -CLASS="PROGRAMLISTING" ->username = <value> -password = <value> -domain = <value></PRE -></P -><P ->Make certain that the permissions on the file restrict -access from unwanted users. </P -></DD -><DT ->-U|--user=username[%password]</DT -><DD -><P ->Sets the SMB username or username and password. </P -><P ->If %password is not specified, the user will be prompted. The -client will first check the <VAR -CLASS="ENVAR" ->USER</VAR -> environment variable, then the -<VAR -CLASS="ENVAR" ->LOGNAME</VAR -> variable and if either exists, the -string is uppercased. If these environmental variables are not -found, the username <CODE -CLASS="CONSTANT" ->GUEST</CODE -> is used. </P -><P ->A third option is to use a credentials file which -contains the plaintext of the username and password. This -option is mainly provided for scripts where the admin does not -wish to pass the credentials on the command line or via environment -variables. If this method is used, make certain that the permissions -on the file restrict access from unwanted users. See the -<VAR -CLASS="PARAMETER" ->-A</VAR -> for more details. </P -><P ->Be cautious about including passwords in scripts. Also, on -many systems the command line of a running process may be seen -via the <B -CLASS="COMMAND" ->ps</B -> command. To be safe always allow -<B -CLASS="COMMAND" ->rpcclient</B -> to prompt for a password and type -it in directly. </P -></DD -><DT ->-n <primary NetBIOS name></DT -><DD -><P ->This option allows you to override -the NetBIOS name that Samba uses for itself. This is identical -to setting the <A -HREF="smb.conf.5.html#netbiosname" -TARGET="_top" -><VAR -CLASS="PARAMETER" ->NetBIOS -name</VAR -></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 ->.</P -></DD -><DT ->-i <scope></DT -><DD -><P ->This specifies a NetBIOS scope that -<B -CLASS="COMMAND" ->nmblookup</B -> will use to communicate with when -generating NetBIOS names. For details on the use of NetBIOS -scopes, see rfc1001.txt and rfc1002.txt. NetBIOS scopes are -<SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->very</I -></SPAN -> rarely used, only set this parameter -if you are the system administrator in charge of all the -NetBIOS systems you communicate with.</P -></DD -><DT ->-W|--workgroup=domain</DT -><DD -><P ->Set the SMB domain of the username. This -overrides the default domain which is the domain defined in -smb.conf. If the domain specified is the same as the servers -NetBIOS name, it causes the client to log on using the servers local -SAM (as opposed to the Domain SAM). </P -></DD -><DT ->-O socket options</DT -><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 -options. </P +>smb.conf</TT +> + file for this connection. This may be needed to connect to some + servers. </P ></DD ><DT >-T tar options</DT @@ -728,31 +713,39 @@ CLASS="COMMAND" ><UL ><LI ><P -><VAR +><TT CLASS="PARAMETER" ->c</VAR +><I +>c</I +></TT > - Create a tar file on UNIX. Must be followed by the name of a tar file, tape device or "-" for standard output. If using standard output you must turn the log level to its lowest value -d0 to avoid corrupting your tar file. This flag is mutually exclusive with the - <VAR + <TT CLASS="PARAMETER" ->x</VAR +><I +>x</I +></TT > flag. </P ></LI ><LI ><P -><VAR +><TT CLASS="PARAMETER" ->x</VAR +><I +>x</I +></TT > - Extract (restore) a local tar file back to a share. Unless the -D option is given, the tar files will be restored from the top level of the share. Must be followed by the name of the tar file, device or "-" for standard - input. Mutually exclusive with the <VAR + input. Mutually exclusive with the <TT CLASS="PARAMETER" ->c</VAR +><I +>c</I +></TT > flag. Restored files have their creation times (mtime) set to the date saved in the tar file. Directories currently do not get @@ -760,9 +753,11 @@ CLASS="PARAMETER" ></LI ><LI ><P -><VAR +><TT CLASS="PARAMETER" ->I</VAR +><I +>I</I +></TT > - Include files and directories. Is the default behavior when filenames are specified above. Causes tar files to be included in an extract or create (and therefore @@ -771,22 +766,28 @@ CLASS="PARAMETER" ></LI ><LI ><P -><VAR +><TT CLASS="PARAMETER" ->X</VAR +><I +>X</I +></TT > - Exclude files and directories. Causes tar files to be excluded from an extract or create. See example below. Filename globbing works in one of two ways now. - See <VAR + See <TT CLASS="PARAMETER" ->r</VAR +><I +>r</I +></TT > below. </P ></LI ><LI ><P -><VAR +><TT CLASS="PARAMETER" ->b</VAR +><I +>b</I +></TT > - Blocksize. Must be followed by a valid (greater than zero) blocksize. Causes tar file to be written out in blocksize*TBLOCK (usually 512 byte) blocks. @@ -794,30 +795,38 @@ CLASS="PARAMETER" ></LI ><LI ><P -><VAR +><TT CLASS="PARAMETER" ->g</VAR +><I +>g</I +></TT > - Incremental. Only back up files that have the archive bit set. Useful only with the - <VAR + <TT CLASS="PARAMETER" ->c</VAR +><I +>c</I +></TT > flag. </P ></LI ><LI ><P -><VAR +><TT CLASS="PARAMETER" ->q</VAR +><I +>q</I +></TT > - Quiet. Keeps tar from printing diagnostics as it works. This is the same as tarmode quiet. </P ></LI ><LI ><P -><VAR +><TT CLASS="PARAMETER" ->r</VAR +><I +>r</I +></TT > - Regular expression include or exclude. Uses regular expression matching for excluding or excluding files if compiled with HAVE_REGEX_H. @@ -827,31 +836,41 @@ CLASS="PARAMETER" ></LI ><LI ><P -><VAR +><TT CLASS="PARAMETER" ->N</VAR +><I +>N</I +></TT > - Newer than. Must be followed by the name of a file whose date is compared against files found on the share during a create. Only files newer than the file specified are backed up to the tar file. Useful only with the - <VAR + <TT CLASS="PARAMETER" ->c</VAR +><I +>c</I +></TT > flag. </P ></LI ><LI ><P -><VAR +><TT CLASS="PARAMETER" ->a</VAR +><I +>a</I +></TT > - Set archive bit. Causes the archive bit to be reset when a file is backed up. Useful with the - <VAR + <TT CLASS="PARAMETER" ->g</VAR -> and <VAR +><I +>g</I +></TT +> and <TT CLASS="PARAMETER" ->c</VAR +><I +>c</I +></TT > flags. </P ></LI @@ -886,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 @@ -963,12 +982,16 @@ CLASS="COMMAND" ><DD ><P >command string is a semicolon-separated list of - commands to be executed instead of prompting from stdin. <VAR + commands to be executed instead of prompting from stdin. <TT CLASS="PARAMETER" -> -N</VAR -> is implied by <VAR +><I +> -N</I +></TT +> is implied by <TT CLASS="PARAMETER" ->-c</VAR +><I +>-c</I +></TT >.</P ><P >This is particularly useful in scripts and for printing stdin @@ -983,7 +1006,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN344" +NAME="AEN310" ></A ><H2 >OPERATIONS</H2 @@ -991,12 +1014,12 @@ NAME="AEN344" >Once the client is running, the user is presented with a prompt : </P ><P -><SAMP +><TT CLASS="PROMPT" ->smb:\> </SAMP +>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 @@ -1013,7 +1036,7 @@ CLASS="PROMPT" ><P >Parameters shown in square brackets (e.g., "[parameter]") are optional. If not given, the command will use suitable defaults. Parameters - shown in angle brackets (e.g., "<parameter>") are required. + shown in angle brackets (e.g., "<parameter>") are required. </P ><P >Note that all commands operating on the server are actually @@ -1031,9 +1054,11 @@ CLASS="VARIABLELIST" >? [command]</DT ><DD ><P ->If <VAR +>If <TT CLASS="REPLACEABLE" ->command</VAR +><I +>command</I +></TT > is specified, the ? command will display a brief informative message about the specified command. If no command is specified, a list of available commands will @@ -1043,9 +1068,11 @@ CLASS="REPLACEABLE" >! [shell command]</DT ><DD ><P ->If <VAR +>If <TT CLASS="REPLACEABLE" ->shell command</VAR +><I +>shell command</I +></TT > is specified, the ! command will execute a shell locally and run the specified shell command. If no command is specified, a local shell will be run. @@ -1100,23 +1127,27 @@ CLASS="REPLACEABLE" directory on the server will be reported. </P ></DD ><DT ->del <mask></DT +>del <mask></DT ><DD ><P >The client will request that the server attempt - to delete all files matching <VAR + to delete all files matching <TT CLASS="REPLACEABLE" ->mask</VAR +><I +>mask</I +></TT > from the current working directory on the server. </P ></DD ><DT ->dir <mask></DT +>dir <mask></DT ><DD ><P ->A list of the files matching <VAR +>A list of the files matching <TT CLASS="REPLACEABLE" ->mask</VAR +><I +>mask</I +></TT > in the current working directory on the server will be retrieved from the server and displayed. </P @@ -1129,7 +1160,7 @@ CLASS="REPLACEABLE" from the program. </P ></DD ><DT ->get <remote file name> [local file name]</DT +>get <remote file name> [local file name]</DT ><DD ><P >Copy the file called <TT @@ -1157,9 +1188,11 @@ CLASS="COMMAND" >lcd [directory name]</DT ><DD ><P ->If <VAR +>If <TT CLASS="REPLACEABLE" ->directory name</VAR +><I +>directory name</I +></TT > is specified, the current working directory on the local machine will be changed to the directory specified. This operation will fail if for any @@ -1192,13 +1225,13 @@ CLASS="REPLACEABLE" lowercase filenames are the norm on UNIX systems. </P ></DD ><DT ->ls <mask></DT +>ls <mask></DT ><DD ><P >See the dir command above. </P ></DD ><DT ->mask <mask></DT +>mask <mask></DT ><DD ><P >This command allows the user to set up a mask @@ -1224,24 +1257,28 @@ CLASS="REPLACEABLE" mask back to "*" after using the mget or mput commands. </P ></DD ><DT ->md <directory name></DT +>md <directory name></DT ><DD ><P >See the mkdir command. </P ></DD ><DT ->mget <mask></DT +>mget <mask></DT ><DD ><P ->Copy all files matching <VAR +>Copy all files matching <TT CLASS="REPLACEABLE" ->mask</VAR +><I +>mask</I +></TT > from the server to the machine running the client. </P ><P ->Note that <VAR +>Note that <TT CLASS="REPLACEABLE" ->mask</VAR +><I +>mask</I +></TT > is interpreted differently during recursive operation and non-recursive operation - refer to the recurse and mask commands for more information. Note that all transfers in @@ -1251,26 +1288,30 @@ CLASS="COMMAND" > are binary. See also the lowercase command. </P ></DD ><DT ->mkdir <directory name></DT +>mkdir <directory name></DT ><DD ><P >Create a new directory on the server (user access privileges permitting) with the specified name. </P ></DD ><DT ->mput <mask></DT +>mput <mask></DT ><DD ><P ->Copy all files matching <VAR +>Copy all files matching <TT CLASS="REPLACEABLE" ->mask</VAR +><I +>mask</I +></TT > in the current working directory on the local machine to the current working directory on the server. </P ><P ->Note that <VAR +>Note that <TT CLASS="REPLACEABLE" ->mask</VAR +><I +>mask</I +></TT > is interpreted differently during recursive operation and non-recursive operation - refer to the recurse and mask commands for more information. Note that all transfers in <B @@ -1280,7 +1321,7 @@ CLASS="COMMAND" are binary. </P ></DD ><DT ->print <file name></DT +>print <file name></DT ><DD ><P >Print the specified file from the local machine @@ -1289,7 +1330,7 @@ CLASS="COMMAND" >See also the printmode command.</P ></DD ><DT ->printmode <graphics or text></DT +>printmode <graphics or text></DT ><DD ><P >Set the print mode to suit either binary data @@ -1309,7 +1350,7 @@ CLASS="COMMAND" </P ></DD ><DT ->put <local file name> [remote file name]</DT +>put <local file name> [remote file name]</DT ><DD ><P >Copy the file called <TT @@ -1341,7 +1382,7 @@ CLASS="COMMAND" >See the exit command. </P ></DD ><DT ->rd <directory name></DT +>rd <directory name></DT ><DD ><P >See the rmdir command. </P @@ -1366,24 +1407,26 @@ CLASS="COMMAND" using the mask command will be ignored. </P ></DD ><DT ->rm <mask></DT +>rm <mask></DT ><DD ><P ->Remove all files matching <VAR +>Remove all files matching <TT CLASS="REPLACEABLE" ->mask</VAR +><I +>mask</I +></TT > from the current working directory on the server. </P ></DD ><DT ->rmdir <directory name></DT +>rmdir <directory name></DT ><DD ><P >Remove the specified directory (user access privileges permitting) from the server. </P ></DD ><DT ->setmode <filename> <perm=[+|\-]rsha></DT +>setmode <filename> <perm=[+|\-]rsha></DT ><DD ><P >A version of the DOS attrib command to set @@ -1408,13 +1451,15 @@ CLASS="COMMAND" </P ></DD ><DT ->tar <c|x>[IXbgNa]</DT +>tar <c|x>[IXbgNa]</DT ><DD ><P ->Performs a tar operation - see the <VAR +>Performs a tar operation - see the <TT CLASS="PARAMETER" +><I >-T - </VAR + </I +></TT > command line option above. Behavior may be affected by the tarmode command (see below). Using g (incremental) and N (newer) will affect tarmode settings. Note that using the "-" option @@ -1422,18 +1467,20 @@ CLASS="PARAMETER" </P ></DD ><DT ->blocksize <blocksize></DT +>blocksize <blocksize></DT ><DD ><P >Blocksize. Must be followed by a valid (greater than zero) blocksize. Causes tar file to be written out in - <VAR + <TT CLASS="REPLACEABLE" ->blocksize</VAR +><I +>blocksize</I +></TT >*TBLOCK (usually 512 byte) blocks. </P ></DD ><DT ->tarmode <full|inc|reset|noreset></DT +>tarmode <full|inc|reset|noreset></DT ><DD ><P >Changes tar's behavior with regard to archive @@ -1449,7 +1496,7 @@ CLASS="REPLACEABLE" ><DIV CLASS="REFSECT1" ><A -NAME="AEN535" +NAME="AEN501" ></A ><H2 >NOTES</H2 @@ -1470,30 +1517,30 @@ NAME="AEN535" ><DIV CLASS="REFSECT1" ><A -NAME="AEN540" +NAME="AEN506" ></A ><H2 >ENVIRONMENT VARIABLES</H2 ><P ->The variable <VAR +>The variable <TT CLASS="ENVAR" ->USER</VAR +>USER</TT > may contain the username of the person using the client. This information is used only if the protocol level is high enough to support session-level passwords.</P ><P ->The variable <VAR +>The variable <TT CLASS="ENVAR" ->PASSWD</VAR +>PASSWD</TT > may contain the password of the person using the client. This information is used only if the protocol level is high enough to support session-level passwords. </P ><P ->The variable <VAR +>The variable <TT CLASS="ENVAR" ->LIBSMB_PROG</VAR +>LIBSMB_PROG</TT > may contain the path, executed with system(), which the client should connect to instead of connecting to a server. This functionality is primarily @@ -1503,7 +1550,7 @@ CLASS="ENVAR" ><DIV CLASS="REFSECT1" ><A -NAME="AEN548" +NAME="AEN514" ></A ><H2 >INSTALLATION</H2 @@ -1534,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 @@ -1547,7 +1592,7 @@ CLASS="REFENTRYTITLE" ><DIV CLASS="REFSECT1" ><A -NAME="AEN560" +NAME="AEN524" ></A ><H2 >DIAGNOSTICS</H2 @@ -1563,17 +1608,18 @@ NAME="AEN560" ><DIV CLASS="REFSECT1" ><A -NAME="AEN564" +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="AEN567" +NAME="AEN531" ></A ><H2 >AUTHOR</H2 @@ -1585,14 +1631,14 @@ NAME="AEN567" ><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 0afbbcd3f2..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.7"></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 @@ -37,7 +37,7 @@ NAME="AEN8" ><B CLASS="COMMAND" >smbcontrol</B -> [-i] [-s]</P +> [-i]</P ><P ><B CLASS="COMMAND" @@ -47,47 +47,42 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN18" +NAME="AEN17" ></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 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="AEN35" +NAME="AEN26" ></A ><H2 >OPTIONS</H2 @@ -97,32 +92,6 @@ NAME="AEN35" CLASS="VARIABLELIST" ><DL ><DT ->-h|--help</DT -><DD -><P ->Print a summary of command line options.</P -></DD -><DT ->-s <configuration file></DT -><DD -><P ->The file specified contains the -configuration details required by the server. The -information in this file includes server-specific -information such as what printcap file to use, as well -as descriptions of all the services that the server is -to provide. See <A -HREF="smb.conf.5.html" -TARGET="_top" -><TT -CLASS="FILENAME" ->smb.conf(5)</TT -></A -> for more information. -The default configuration file name is determined at -compile time.</P -></DD -><DT >-i</DT ><DD ><P @@ -135,23 +104,32 @@ compile time.</P >destination</DT ><DD ><P ->One of <VAR +>One of <TT CLASS="PARAMETER" ->nmbd</VAR ->, <VAR +><I +>nmbd</I +></TT +> + <TT CLASS="PARAMETER" ->smbd</VAR +><I +>smbd</I +></TT > or a process ID.</P ><P ->The <VAR +>The <TT CLASS="PARAMETER" ->smbd</VAR +><I +>smbd</I +></TT > destination causes the message to "broadcast" to all smbd daemons.</P ><P ->The <VAR +>The <TT CLASS="PARAMETER" ->nmbd</VAR +><I +>nmbd</I +></TT > destination causes the message to be sent to the nmbd daemon specified in the <TT @@ -166,109 +144,116 @@ CLASS="FILENAME" >message-type</DT ><DD ><P ->Type of message to send. See - the section <CODE +>One of: <TT CLASS="CONSTANT" ->MESSAGE-TYPES</CODE -> for details. - </P -></DD -><DT ->parameters</DT -><DD -><P ->any parameters required for the message-type</P -></DD -></DL -></DIV -></DIV -><DIV -CLASS="REFSECT1" -><A -NAME="AEN73" -></A -><H2 ->MESSAGE-TYPES</H2 -><P ->Available message types are:</P -><P -></P -><DIV -CLASS="VARIABLELIST" -><DL -><DT ->close-share</DT -><DD +>close-share</TT +>, + <TT +CLASS="CONSTANT" +>debug</TT +>, + <TT +CLASS="CONSTANT" +>force-election</TT +>, <TT +CLASS="CONSTANT" +>ping + </TT +>, <TT +CLASS="CONSTANT" +>profile</TT +>, <TT +CLASS="CONSTANT" +> debuglevel</TT +>, <TT +CLASS="CONSTANT" +>profilelevel</TT +>, + or <TT +CLASS="CONSTANT" +>printnotify</TT +>.</P ><P ->Order smbd to close the client - connections to the named share. Note that this doesn't affect client - connections to any other shares. This message-type takes an argument of the - share name for which client connections will be closed, or the - "*" character which will close all currently open shares. - This may be useful if you made changes to the access controls on the share. - This message can only be sent to <CODE +>The <TT CLASS="CONSTANT" ->smbd</CODE +>close-share</TT +> message-type sends a + message to smbd which will then close the client connections to + the named share. Note that this doesn't affect client connections + to any other shares. This message-type takes an argument of the + share name for which client connections will be closed, or the + "*" character which will close all currently open shares. + This may be useful if you made changes to the access controls on the share. + This message can only be sent to <TT +CLASS="CONSTANT" +>smbd</TT >.</P -></DD -><DT ->debug</DT -><DD ><P ->Set debug level to the value specified by the - parameter. This can be sent to any of the destinations.</P -></DD -><DT ->force-election</DT -><DD +>The <TT +CLASS="CONSTANT" +>debug</TT +> message-type allows + the debug level to be set to the value specified by the + parameter. This can be sent to any of the destinations.</P ><P ->This message causes the <B +>The <TT +CLASS="CONSTANT" +>force-election</TT +> message-type can only be + sent to the <TT +CLASS="CONSTANT" +>nmbd</TT +> destination. This message + causes the <B CLASS="COMMAND" >nmbd</B -> daemon to - force a new browse master election. </P -></DD -><DT ->ping</DT -><DD +> daemon to force a new browse + master election.</P ><P -> Send specified number of "ping" messages and - wait for the same number of reply "pong" messages. This can be sent to - any of the destinations.</P -></DD -><DT ->profile</DT -><DD -><P ->Change profile settings of a daemon, based on the - parameter. The parameter can be "on" to turn on profile stats - collection, "off" to turn off profile stats collection, "count" - to enable only collection of count stats (time stats are - disabled), and "flush" to zero the current profile stats. This can - be sent to any smbd or nmbd destinations.</P -></DD -><DT ->debuglevel</DT -><DD -><P -> Request debuglevel of a certain daemon and write it to stdout. This - can be sent to any of the destinations.</P -></DD -><DT ->profilelevel</DT -><DD +>The <TT +CLASS="CONSTANT" +>ping</TT +> message-type sends the + number of "ping" messages specified by the parameter and waits + for the same number of reply "pong" messages. This can be sent to + any of the destinations.</P ><P -> Request profilelevel of a certain daemon and write it to stdout. - This can be sent to any smbd or nmbd destinations.</P -></DD -><DT ->printnotify</DT -><DD +>The <TT +CLASS="CONSTANT" +>profile</TT +> message-type sends a + message to an smbd to change the profile settings based on the + parameter. The parameter can be "on" to turn on profile stats + collection, "off" to turn off profile stats collection, "count" + to enable only collection of count stats (time stats are + disabled), and "flush" to zero the current profile stats. This can + be sent to any smbd or nmbd destinations.</P +><P +>The <TT +CLASS="CONSTANT" +>debuglevel</TT +> message-type sends + a "request debug level" message. The current debug level setting + is returned by a "debuglevel" message. This can be + sent to any of the destinations.</P ><P -> Order smbd to send a printer notify message to any Windows NT clients - connected to a printer. This message-type takes the following arguments: - </P +>The <TT +CLASS="CONSTANT" +>profilelevel</TT +> message-type sends + a "request profile level" message. The current profile level + setting is returned by a "profilelevel" message. This can be sent + to any smbd or nmbd destinations.</P ><P +>The <TT +CLASS="CONSTANT" +>printnotify</TT +> message-type sends a + message to smbd which in turn sends a printer notify message to + any Windows NT clients connected to a printer. This message-type + takes the following arguments: + + <P ></P ><DIV CLASS="VARIABLELIST" @@ -278,130 +263,58 @@ CLASS="VARIABLELIST" ><DD ><P >Send a queue pause change notify - message to the printer specified.</P + message to the printer specified.</P ></DD ><DT >queueresume printername</DT ><DD ><P >Send a queue resume change notify - message for the printer specified.</P + message for the printer specified.</P ></DD ><DT >jobpause printername unixjobid</DT ><DD ><P >Send a job pause change notify - message for the printer and unix jobid - specified.</P + message for the printer and unix jobid + specified.</P ></DD ><DT >jobresume printername unixjobid</DT ><DD ><P >Send a job resume change notify - message for the printer and unix jobid - specified.</P + message for the printer and unix jobid + specified.</P ></DD ><DT >jobdelete printername unixjobid</DT ><DD ><P >Send a job delete change notify - message for the printer and unix jobid - specified.</P + message for the printer and unix jobid + specified.</P ></DD ></DL ></DIV -><P -> Note that this message only sends notification that an - event has occured. It doesn't actually cause the - event to happen. - </P -><P ->This message can only be sent to <CODE -CLASS="CONSTANT" ->smbd</CODE ->. </P -></DD -><DT ->samsync</DT -><DD -><P ->Order smbd to synchronise sam database from PDC (being BDC). Can only be sent to <CODE +> + + Note that this message only sends notification that an + event has occured. It doesn't actually cause the + event to happen. + + This message can only be sent to <TT CLASS="CONSTANT" ->smbd</CODE ->. </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 ->Not working at the moment</P -></TD -></TR -></TABLE -></DIV -></DD -><DT ->samrepl</DT -><DD -><P ->Send sam replication message, with specified serial. Can only be sent to <CODE -CLASS="CONSTANT" ->smbd</CODE ->. Should not be used manually.</P -></DD -><DT ->dmalloc-mark</DT -><DD -><P ->Set a mark for dmalloc. Can be sent to both smbd and nmbd. Only available if samba is built with dmalloc support. </P -></DD -><DT ->dmalloc-log-changed</DT -><DD -><P -> Dump the pointers that have changed since the mark set by dmalloc-mark. - Can be sent to both smbd and nmbd. Only available if samba is built with dmalloc support. </P -></DD -><DT ->shutdown</DT -><DD -><P ->Shut down specified daemon. Can be sent to both smbd and nmbd.</P -></DD -><DT ->pool-usage</DT -><DD -><P ->Print a human-readable description of all - talloc(pool) memory usage by the specified daemon/process. Available - for both smbd and nmbd.</P +>smbd</TT +>. + </P ></DD ><DT ->drvupgrade</DT +>parameters</DT ><DD ><P ->Force clients of printers using specified driver - to update their local version of the driver. Can only be - sent to smbd.</P +>any parameters required for the message-type</P ></DD ></DL ></DIV @@ -409,40 +322,44 @@ CLASS="CONSTANT" ><DIV CLASS="REFSECT1" ><A -NAME="AEN167" +NAME="AEN102" ></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="AEN170" +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="AEN179" +NAME="AEN112" ></A ><H2 >AUTHOR</H2 @@ -454,14 +371,14 @@ NAME="AEN179" ><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 afd70cbe03..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.7"></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 @@ -200,106 +195,83 @@ CLASS="COMMAND" </P ></DD ><DT +>-h</DT +><DD +><P +>Prints the help information (usage) + for <B +CLASS="COMMAND" +>smbd</B +>.</P +></DD +><DT >-V</DT ><DD ><P >Prints the version number for -<B + <B CLASS="COMMAND" >smbd</B >.</P ></DD ><DT ->-s <configuration file></DT +>-b</DT ><DD ><P ->The file specified contains the -configuration details required by the server. The -information in this file includes server-specific -information such as what printcap file to use, as well -as descriptions of all the services that the server is -to provide. See <A -HREF="smb.conf.5.html" -TARGET="_top" -><TT -CLASS="FILENAME" ->smb.conf(5)</TT -></A -> for more information. -The default configuration file name is determined at -compile time.</P +>Prints information about how + Samba was built.</P ></DD ><DT ->-d|--debug=debuglevel</DT +>-d <debug level></DT ><DD ><P -><VAR +><TT CLASS="REPLACEABLE" ->debuglevel</VAR +><I +>debuglevel</I +></TT > is an integer -from 0 to 10. The default value if this parameter is -not specified is zero.</P + from 0 to 10. The default value if this parameter is + not specified is zero.</P ><P >The higher this value, the more detail will be -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 -information about operations carried out.</P + 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 + information about operations carried out.</P ><P >Levels above 1 will generate considerable -amounts of log data, and should only be used when -investigating a problem. Levels above 3 are designed for -use only by developers and generate HUGE amounts of log -data, most of which is extremely cryptic.</P + amounts of log data, and should only be used when + investigating a problem. Levels above 3 are designed for + use only by developers and generate HUGE amounts of log + data, most of which is extremely cryptic.</P ><P >Note that specifying this parameter here will -override the <A + override the <A HREF="smb.conf.5.html#loglevel" TARGET="_top" >log -level</A + level</A > parameter in the <A HREF="smb.conf.5.html" TARGET="_top" -><TT +> <TT CLASS="FILENAME" >smb.conf(5)</TT ></A > file.</P ></DD ><DT ->-l|--logfile=logbasename</DT -><DD -><P ->File name for log/debug files. The extension -<CODE -CLASS="CONSTANT" ->".client"</CODE -> will be appended. The log file is -never removed by the client.</P -></DD -><DT ->-h|--help</DT -><DD -><P ->Print a summary of command line options.</P -></DD -><DT ->-b</DT -><DD -><P ->Prints information about how - Samba was built.</P -></DD -><DT >-l <log directory></DT ><DD ><P >If specified, - <VAR + <TT CLASS="REPLACEABLE" ->log directory</VAR +><I +>log directory</I +></TT > specifies a log directory into which the "log.smbd" log file will be created for informational and debug @@ -308,23 +280,18 @@ CLASS="REPLACEABLE" its size may be controlled by the <A HREF="smb.conf.5.html#maxlogsize" TARGET="_top" -><VAR -CLASS="PARAMETER" ->max log size</VAR -></A +>max log size</A > - option in the <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smb.conf</SPAN ->(5)</SPAN -> file. <SPAN -CLASS="emphasis" -><I + option in the <A +HREF="smb.conf.5.html" +TARGET="_top" +><TT +CLASS="FILENAME" +> smb.conf(5)</TT +></A +> file. <I CLASS="EMPHASIS" >Beware:</I -></SPAN > If the directory specified does not exist, <B CLASS="COMMAND" @@ -337,12 +304,33 @@ CLASS="COMMAND" compile time.</P ></DD ><DT +>-O <socket options></DT +><DD +><P +>See the <A +HREF="smb.conf.5.html#socketoptions" +TARGET="_top" +>socket options</A +> + parameter in the <A +HREF="smb.conf.5.html" +TARGET="_top" +><TT +CLASS="FILENAME" +>smb.conf(5) + </TT +></A +> file for details.</P +></DD +><DT >-p <port number></DT ><DD ><P -><VAR +><TT CLASS="REPLACEABLE" ->port number</VAR +><I +>port number</I +></TT > is a positive integer value. The default value if this parameter is not specified is 139.</P @@ -365,13 +353,33 @@ CLASS="REPLACEABLE" >This parameter is not normally specified except in the above situation.</P ></DD +><DT +>-s <configuration file></DT +><DD +><P +>The file specified contains the + configuration details required by the server. The + information in this file includes server-specific + information such as what printcap file to use, as well + as descriptions of all the services that the server is + to provide. See <A +HREF="smb.conf.5.html" +TARGET="_top" +><TT +CLASS="FILENAME" +> smb.conf(5)</TT +></A +> for more information. + The default configuration file name is determined at + compile time.</P +></DD ></DL ></DIV ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN127" +NAME="AEN123" ></A ><H2 >FILES</H2 @@ -394,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 @@ -414,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 @@ -435,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 @@ -448,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 @@ -479,7 +491,7 @@ CLASS="REFENTRYTITLE" ><DIV CLASS="REFSECT1" ><A -NAME="AEN165" +NAME="AEN159" ></A ><H2 >LIMITATIONS</H2 @@ -498,7 +510,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN169" +NAME="AEN163" ></A ><H2 >ENVIRONMENT VARIABLES</H2 @@ -508,17 +520,17 @@ NAME="AEN169" CLASS="VARIABLELIST" ><DL ><DT -><VAR +><TT CLASS="ENVAR" ->PRINTER</VAR +>PRINTER</TT ></DT ><DD ><P >If no printer name is specified to printable services, most systems will use the value of - this variable (or <CODE + this variable (or <TT CLASS="CONSTANT" ->lp</CODE +>lp</TT > if this variable is not defined) as the name of the printer to use. This is not specific to the server, however.</P @@ -529,7 +541,7 @@ CLASS="CONSTANT" ><DIV CLASS="REFSECT1" ><A -NAME="AEN178" +NAME="AEN172" ></A ><H2 >PAM INTERACTION</H2 @@ -537,33 +549,22 @@ NAME="AEN178" >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" -><VAR -CLASS="PARAMETER" ->obey - pam restricions</VAR -></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 @@ -572,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. @@ -590,7 +588,7 @@ CLASS="EMPHASIS" ><DIV CLASS="REFSECT1" ><A -NAME="AEN193" +NAME="AEN183" ></A ><H2 >VERSION</H2 @@ -601,7 +599,7 @@ NAME="AEN193" ><DIV CLASS="REFSECT1" ><A -NAME="AEN196" +NAME="AEN186" ></A ><H2 >DIAGNOSTICS</H2 @@ -624,7 +622,7 @@ NAME="AEN196" ><DIV CLASS="REFSECT1" ><A -NAME="AEN201" +NAME="AEN191" ></A ><H2 >SIGNALS</H2 @@ -646,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 @@ -665,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, @@ -691,55 +688,55 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN219" +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 @@ -757,7 +754,7 @@ TARGET="_top" ><DIV CLASS="REFSECT1" ><A -NAME="AEN246" +NAME="AEN225" ></A ><H2 >AUTHOR</H2 @@ -769,14 +766,14 @@ NAME="AEN246" ><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 32e00315b4..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.7"></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 @@ -179,9 +213,9 @@ TYPE="1" <TT CLASS="FILENAME" >/etc/group</TT ->), let's call it <CODE +>), let's call it <TT CLASS="CONSTANT" ->domadm</CODE +>domadm</TT >. </P ></LI @@ -199,50 +233,69 @@ 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" -><SAMP +><TT CLASS="PROMPT" ->root# </SAMP +>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: -<PRE + </P +><P +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="90%" +><TR +><TD +><PRE CLASS="PROGRAMLISTING" -><SAMP +><TT CLASS="PROMPT" ->root# </SAMP +>root# </TT ><B CLASS="COMMAND" >smbgroupedit \ -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,37 +304,57 @@ 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" -><SAMP +><TT CLASS="PROMPT" ->root# </SAMP +>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: -<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" -><SAMP +><TT CLASS="PROMPT" ->root# </SAMP +>root# </TT ><B 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 28be79c391..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.7"></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 @@ -37,12 +37,12 @@ NAME="AEN8" ><B CLASS="COMMAND" >smbmnt</B -> {mount-point} [-s <share>] [-r] [-u <uid>] [-g <gid>] [-f <mask>] [-d <mask>] [-o <options>] [-h]</P +> {mount-point} [-s <share>] [-r] [-u <uid>] [-g <gid>] [-f <mask>] [-d <mask>] [-o <options>]</P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN20" +NAME="AEN19" ></A ><H2 >DESCRIPTION</H2 @@ -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="AEN32" +NAME="AEN30" ></A ><H2 >OPTIONS</H2 @@ -131,19 +133,13 @@ CLASS="VARIABLELIST" command is run on a 2.4 or higher Linux kernel. </P ></DD -><DT ->-h|--help</DT -><DD -><P ->Print a summary of command line options.</P -></DD ></DL ></DIV ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN63" +NAME="AEN57" ></A ><H2 >AUTHOR</H2 @@ -176,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 5ea2935a3f..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.7"></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 @@ -124,27 +119,27 @@ NAME="AEN35" CLASS="VARIABLELIST" ><DL ><DT ->username=<arg></DT +>username=<arg></DT ><DD ><P >specifies the username to connect as. If - this is not given, then the environment variable <VAR + this is not given, then the environment variable <TT CLASS="ENVAR" -> USER</VAR +> USER</TT > is used. This option can also take the form "user%password" or "user/workgroup" or "user/workgroup%password" to allow the password and workgroup to be specified as part of the username.</P ></DD ><DT ->password=<arg></DT +>password=<arg></DT ><DD ><P >specifies the SMB password. If this option is not given then the environment variable - <VAR + <TT CLASS="ENVAR" ->PASSWD</VAR +>PASSWD</TT > is used. If it can find no password <B CLASS="COMMAND" @@ -161,16 +156,19 @@ CLASS="COMMAND" </P ></DD ><DT ->credentials=<filename></DT +>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 @@ -181,20 +179,14 @@ CLASS="FILENAME" </P ></DD ><DT ->krb</DT -><DD -><P ->Use kerberos (Active Directory). </P -></DD -><DT ->netbiosname=<arg></DT +>netbiosname=<arg></DT ><DD ><P >sets the source NetBIOS name. It defaults to the local hostname. </P ></DD ><DT ->uid=<arg></DT +>uid=<arg></DT ><DD ><P >sets the uid that will own all files on @@ -203,7 +195,7 @@ CLASS="FILENAME" </P ></DD ><DT ->gid=<arg></DT +>gid=<arg></DT ><DD ><P >sets the gid that will own all files on @@ -212,14 +204,14 @@ CLASS="FILENAME" gid. </P ></DD ><DT ->port=<arg></DT +>port=<arg></DT ><DD ><P >sets the remote SMB port number. The default is 139. </P ></DD ><DT ->fmask=<arg></DT +>fmask=<arg></DT ><DD ><P >sets the file mask. This determines the @@ -227,66 +219,66 @@ CLASS="FILENAME" The default is based on the current umask. </P ></DD ><DT ->dmask=<arg></DT +>dmask=<arg></DT ><DD ><P ->Sets the directory mask. This determines the +>sets the directory mask. This determines the permissions that remote directories have in the local filesystem. The default is based on the current umask. </P ></DD ><DT ->debug=<arg></DT +>debug=<arg></DT ><DD ><P ->Sets the debug level. This is useful for +>sets the debug level. This is useful for tracking down SMB connection problems. A suggested value to start with is 4. If set too high there will be a lot of output, possibly hiding the useful output.</P ></DD ><DT ->ip=<arg></DT +>ip=<arg></DT ><DD ><P ->Sets the destination host or IP address. +>sets the destination host or IP address. </P ></DD ><DT ->workgroup=<arg></DT +>workgroup=<arg></DT ><DD ><P ->Sets the workgroup on the destination </P +>sets the workgroup on the destination </P ></DD ><DT ->sockopt=<arg></DT +>sockopt=<arg></DT ><DD ><P ->Sets the TCP socket options. See the <A +>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 -> <VAR +> <TT CLASS="PARAMETER" ->socket options</VAR +><I +>socket options</I +></TT > option. </P ></DD ><DT ->scope=<arg></DT +>scope=<arg></DT ><DD ><P ->Sets the NetBIOS scope </P +>sets the NetBIOS scope </P ></DD ><DT >guest</DT ><DD ><P ->Don't prompt for a password </P +>don't prompt for a password </P ></DD ><DT >ro</DT @@ -301,7 +293,7 @@ CLASS="PARAMETER" >mount read-write </P ></DD ><DT ->iocharset=<arg></DT +>iocharset=<arg></DT ><DD ><P > sets the charset used by the Linux side for codepage @@ -311,7 +303,7 @@ CLASS="PARAMETER" </P ></DD ><DT ->codepage=<arg></DT +>codepage=<arg></DT ><DD ><P > sets the codepage the server uses. See the iocharset @@ -320,7 +312,7 @@ CLASS="PARAMETER" </P ></DD ><DT ->ttl=<arg></DT +>ttl=<arg></DT ><DD ><P > sets how long a directory listing is cached in milliseconds @@ -340,31 +332,31 @@ CLASS="PARAMETER" ><DIV CLASS="REFSECT1" ><A -NAME="AEN134" +NAME="AEN125" ></A ><H2 >ENVIRONMENT VARIABLES</H2 ><P ->The variable <VAR +>The variable <TT CLASS="ENVAR" ->USER</VAR +>USER</TT > may contain the username of the person using the client. This information is used only if the protocol level is high enough to support session-level passwords. The variable can be used to set both username and password by using the format username%password.</P ><P ->The variable <VAR +>The variable <TT CLASS="ENVAR" ->PASSWD</VAR +>PASSWD</TT > may contain the password of the person using the client. This information is used only if the protocol level is high enough to support session-level passwords.</P ><P ->The variable <VAR +>The variable <TT CLASS="ENVAR" ->PASSWD_FILE</VAR +>PASSWD_FILE</TT > may contain the pathname of a file to read the password from. A single line of input is read and used as the password.</P @@ -372,7 +364,7 @@ CLASS="ENVAR" ><DIV CLASS="REFSECT1" ><A -NAME="AEN142" +NAME="AEN133" ></A ><H2 >BUGS</H2 @@ -407,7 +399,7 @@ NAME="AEN142" ><DIV CLASS="REFSECT1" ><A -NAME="AEN151" +NAME="AEN142" ></A ><H2 >SEE ALSO</H2 @@ -417,19 +409,22 @@ NAME="AEN151" ><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="AEN159" +NAME="AEN149" ></A ><H2 >AUTHOR</H2 @@ -462,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 61b60d7d82..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.7"></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 @@ -115,9 +113,9 @@ CLASS="VARIABLELIST" null password this field will contain the characters "NO PASSWORD" as the start of the hex string. If the hex string is equal to 32 'X' characters then the user's account is marked as - <CODE + <TT CLASS="CONSTANT" ->disabled</CODE +>disabled</TT > and the user will not be able to log onto the Samba server. </P ><P @@ -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 @@ -235,18 +233,18 @@ CLASS="EMPHASIS" > - This means the account has no password (the passwords in the fields LANMAN Password Hash and NT Password Hash are ignored). Note that this - will only allow users to log on with no password if the <VAR + will only allow users to log on with no password if the <TT CLASS="PARAMETER" -> null passwords</VAR +><I +> null passwords</I +></TT > 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 @@ -259,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 @@ -297,7 +296,7 @@ CLASS="EMPHASIS" ><DIV CLASS="REFSECT1" ><A -NAME="AEN77" +NAME="AEN73" ></A ><H2 >VERSION</H2 @@ -308,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 @@ -332,7 +331,7 @@ CLASS="REFENTRYTITLE" ><DIV CLASS="REFSECT1" ><A -NAME="AEN89" +NAME="AEN82" ></A ><H2 >AUTHOR</H2 @@ -344,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 6b227f9d1e..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.7"></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 @@ -111,20 +95,14 @@ CLASS="REFENTRYTITLE" ><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 (<VAR -CLASS="PARAMETER" ->-r</VAR ->) and <VAR -CLASS="PARAMETER" ->-U</VAR -> 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 @@ -132,7 +110,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN51" +NAME="AEN43" ></A ><H2 >OPTIONS</H2 @@ -177,13 +155,13 @@ CLASS="FILENAME" ><DD ><P >This option specifies that the username following - should be <CODE + should be <TT CLASS="CONSTANT" ->disabled</CODE +>disabled</TT > in the local smbpasswd - file. This is done by writing a <CODE + file. This is done by writing a <TT CLASS="CONSTANT" ->'D'</CODE +>'D'</TT > flag into the account control space in the smbpasswd file. Once this is done all attempts to authenticate via SMB using this username @@ -191,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 @@ -208,9 +184,9 @@ CLASS="REFENTRYTITLE" ><DD ><P >This option specifies that the username following - should be <CODE + should be <TT CLASS="CONSTANT" ->enabled</CODE +>enabled</TT > in the local smbpasswd file, if the account was previously disabled. If the account was not disabled this option has no effect. Once the account is enabled then @@ -220,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 @@ -236,9 +209,11 @@ CLASS="REFENTRYTITLE" >-D debuglevel</DT ><DD ><P -><VAR +><TT CLASS="REPLACEABLE" ->debuglevel</VAR +><I +>debuglevel</I +></TT > is an integer from 0 to 10. The default value if this parameter is not specified is zero. </P @@ -285,24 +260,30 @@ CLASS="COMMAND" ><P >This option allows a user to specify what machine they wish to change their password on. Without this parameter - smbpasswd defaults to the local host. The <VAR + smbpasswd defaults to the local host. The <TT CLASS="REPLACEABLE" +><I >remote - machine name</VAR + machine name</I +></TT > is the NetBIOS name of the SMB/CIFS server to contact to attempt the password change. This name is resolved into an IP address using the standard name resolution - mechanism in all programs of the Samba suite. See the <VAR + mechanism in all programs of the Samba suite. See the <TT CLASS="PARAMETER" +><I >-R - name resolve order</VAR + name resolve order</I +></TT > parameter for details on changing this resolving mechanism. </P ><P >The username whose password is changed is that of the - current UNIX logged on user. See the <VAR + current UNIX logged on user. See the <TT CLASS="PARAMETER" ->-U username</VAR +><I +>-U username</I +></TT > parameter for details on changing the password for a different username. </P @@ -313,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 @@ -332,32 +310,30 @@ 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 ><LI ><P -><CODE +><TT CLASS="CONSTANT" ->lmhosts</CODE ->: Lookup an IP +>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 + 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 -><CODE +><TT CLASS="CONSTANT" ->host</CODE ->: Do a standard host +>host</TT +> : Do a standard host name to IP address resolution, using the system <TT CLASS="FILENAME" >/etc/hosts @@ -374,27 +350,31 @@ CLASS="FILENAME" ></LI ><LI ><P -><CODE +><TT CLASS="CONSTANT" ->wins</CODE ->: Query a name with - the IP address listed in the <VAR +>wins</TT +> : Query a name with + the IP address listed in the <TT CLASS="PARAMETER" ->wins server</VAR +><I +>wins server</I +></TT > parameter. If no WINS server has been specified this method will be ignored.</P ></LI ><LI ><P -><CODE +><TT CLASS="CONSTANT" ->bcast</CODE ->: Do a broadcast on +>bcast</TT +> : Do a broadcast on each of the known local interfaces listed in the - <VAR + <TT CLASS="PARAMETER" ->interfaces</VAR +><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 @@ -405,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 @@ -430,9 +408,11 @@ CLASS="REFENTRYTITLE" ><DD ><P >This option may only be used in conjunction - with the <VAR + with the <TT CLASS="PARAMETER" ->-r</VAR +><I +>-r</I +></TT > option. When changing a password on a remote machine it allows the user to specify the user name on that machine whose password will be changed. It @@ -474,28 +454,34 @@ CLASS="COMMAND" <B CLASS="COMMAND" >--with-ldapsam</B -> option. The <VAR +> option. The <TT CLASS="PARAMETER" ->-w</VAR +><I +>-w</I +></TT > switch is used to specify the password to be used with the <A HREF="smb.conf.5.html#LDAPADMINDN" TARGET="_top" -><VAR +><TT CLASS="PARAMETER" +><I >ldap admin - dn</VAR + dn</I +></TT ></A >. 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 <VAR + of the admin's DN. This means that if the value of <TT CLASS="PARAMETER" +><I >ldap - admin dn</VAR + admin dn</I +></TT > ever changes, the password will need to be manually updated as well. </P @@ -523,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. @@ -540,7 +523,7 @@ CLASS="EMPHASIS" ><DIV CLASS="REFSECT1" ><A -NAME="AEN189" +NAME="AEN173" ></A ><H2 >NOTES</H2 @@ -554,67 +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 <VAR +> running on the local machine by specifying a + <TT CLASS="PARAMETER" ->allow - hosts</VAR -> or <VAR +><I +>allow hosts</I +></TT +> or <TT CLASS="PARAMETER" ->deny hosts</VAR -> entry in - the <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smb.conf</SPAN ->(5)</SPAN +><I +>deny hosts</I +></TT +> + 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 @@ -626,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 0ed7722b71..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.7"></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,182 +112,159 @@ 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 ->-s <configuration file></DT -><DD -><P ->The file specified contains the -configuration details required by the server. The -information in this file includes server-specific -information such as what printcap file to use, as well -as descriptions of all the services that the server is -to provide. See <A -HREF="smb.conf.5.html" -TARGET="_top" -><TT -CLASS="FILENAME" ->smb.conf(5)</TT -></A -> for more information. -The default configuration file name is determined at -compile time.</P -></DD -><DT ->-d|--debug=debuglevel</DT -><DD -><P -><VAR -CLASS="REPLACEABLE" ->debuglevel</VAR -> is an integer -from 0 to 10. The default value if this parameter is -not specified is zero.</P -><P ->The higher this value, the more detail will be -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 -information about operations carried out.</P -><P ->Levels above 1 will generate considerable -amounts of log data, and should only be used when -investigating a problem. Levels above 3 are designed for -use only by developers and generate HUGE amounts of log -data, most of which is extremely cryptic.</P -><P ->Note that specifying this parameter here will -override the <A -HREF="smb.conf.5.html#loglevel" -TARGET="_top" ->log -level</A -> parameter in the <A -HREF="smb.conf.5.html" -TARGET="_top" -><TT -CLASS="FILENAME" ->smb.conf(5)</TT -></A -> file.</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 + 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 +>The options are :"lmhosts", "host", "wins" and "bcast". + They cause names to be resolved as follows :</P ><P ></P ><UL ><LI ><P -><CODE +><TT CLASS="CONSTANT" ->lmhosts</CODE ->: -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.</P +>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 -><CODE +><TT CLASS="CONSTANT" ->host</CODE ->: -Do a standard host name to IP address resolution, using -the system <TT +>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 + 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 +>/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 + if the NetBIOS name type being queried is the 0x20 + (server) name type, otherwise it is ignored. + </P ></LI ><LI ><P -><CODE +><TT CLASS="CONSTANT" ->wins</CODE ->: -Query a name with the IP address listed in the -<VAR +>wins</TT +> : + Query a name with the IP address listed in the + <TT CLASS="PARAMETER" ->wins server</VAR +><I +>wins server</I +></TT > parameter. If no -WINS server has been specified this method will be -ignored.</P + WINS server has been specified this method will be + ignored. + </P ></LI ><LI ><P -><CODE +><TT CLASS="CONSTANT" ->bcast</CODE ->: -Do a broadcast on each of the known local interfaces -listed in the <VAR +>bcast</TT +> : + Do a broadcast on each of the known local interfaces + listed in the <TT CLASS="PARAMETER" ->interfaces</VAR +><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 + 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 <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smb.conf</SPAN ->(5)</SPAN + defined in the <TT +CLASS="FILENAME" +>smb.conf</TT > file parameter -(<VAR -CLASS="PARAMETER" ->name resolve order</VAR ->) 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 <VAR + this parameter or any entry in the <TT CLASS="PARAMETER" ->name resolve order</VAR -> 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 +><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 @@ -315,7 +284,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN106" +NAME="AEN91" ></A ><H2 >EXAMPLES</H2 @@ -328,30 +297,47 @@ 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" -><SAMP +> <TT CLASS="PROMPT" ->system% </SAMP -><KBD +>system% </TT +><TT CLASS="USERINPUT" ->smbsh</KBD +><B +>smbsh</B +></TT > -<SAMP + <TT CLASS="PROMPT" ->Username: </SAMP -><KBD +>Username: </TT +><TT CLASS="USERINPUT" ->user</KBD +><B +>user</B +></TT > -<SAMP + <TT CLASS="PROMPT" ->Password: </SAMP -><KBD +>Password: </TT +><TT CLASS="USERINPUT" ->XXXXXXX</KBD -></PRE +><B +>XXXXXXX</B +></TT +> + </PRE +></TD +></TR +></TABLE ></P ><P >Any dynamically linked command you execute from @@ -388,17 +374,18 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN126" +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="AEN129" +NAME="AEN115" ></A ><H2 >BUGS</H2 @@ -431,29 +418,30 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN138" +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="AEN147" +NAME="AEN130" ></A ><H2 >AUTHOR</H2 @@ -465,14 +453,14 @@ NAME="AEN147" ><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 fb2c8b25e0..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.7"></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 @@ -37,7 +37,7 @@ NAME="AEN8" ><B CLASS="COMMAND" >smbspool</B -> {job} {user} {title} {copies} {options} [filename]</P +> [job] [user] [title] [copies] [options] [filename]</P ></DIV ><DIV CLASS="REFSECT1" @@ -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,14 +87,15 @@ CLASS="EMPHASIS" ></LI ><LI ><P ->smb://username:password@workgroup/server/printer</P +>smb://username:password@workgroup/server/printer + </P ></LI ></UL ><P >smbspool tries to get the URI from argv[0]. If argv[0] - contains the name of the program then it looks in the <VAR + contains the name of the program then it looks in the <TT CLASS="ENVAR" -> DEVICE_URI</VAR +> DEVICE_URI</TT > environment variable.</P ><P >Programs using the <B @@ -104,16 +103,16 @@ CLASS="COMMAND" >exec(2)</B > functions can pass the URI in argv[0], while shell scripts must set the - <VAR + <TT CLASS="ENVAR" ->DEVICE_URI</VAR +>DEVICE_URI</TT > environment variable prior to running smbspool.</P ></DIV ><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 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="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 23b82759ea..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.7"></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 @@ -37,7 +37,7 @@ NAME="AEN8" ><B CLASS="COMMAND" >smbstatus</B -> [-P] [-b] [-d <debug level>] [-v] [-L] [-B] [-p] [-S] [-s <configuration file>] [-u <username>]</P +> [-P] [-b] [-d <debug level>] [-v] [-L] [-B] [-p] [-S] [-s <configuration file>] [-u <username>]</P ></DIV ><DIV CLASS="REFSECT1" @@ -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 @@ -88,84 +86,10 @@ CLASS="VARIABLELIST" >gives brief output.</P ></DD ><DT ->-V</DT -><DD -><P ->Prints the version number for -<B -CLASS="COMMAND" ->smbd</B ->.</P -></DD -><DT ->-s <configuration file></DT -><DD -><P ->The file specified contains the -configuration details required by the server. The -information in this file includes server-specific -information such as what printcap file to use, as well -as descriptions of all the services that the server is -to provide. See <A -HREF="smb.conf.5.html" -TARGET="_top" -><TT -CLASS="FILENAME" ->smb.conf(5)</TT -></A -> for more information. -The default configuration file name is determined at -compile time.</P -></DD -><DT ->-d|--debug=debuglevel</DT -><DD -><P -><VAR -CLASS="REPLACEABLE" ->debuglevel</VAR -> is an integer -from 0 to 10. The default value if this parameter is -not specified is zero.</P -><P ->The higher this value, the more detail will be -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 -information about operations carried out.</P -><P ->Levels above 1 will generate considerable -amounts of log data, and should only be used when -investigating a problem. Levels above 3 are designed for -use only by developers and generate HUGE amounts of log -data, most of which is extremely cryptic.</P -><P ->Note that specifying this parameter here will -override the <A -HREF="smb.conf.5.html#loglevel" -TARGET="_top" ->log -level</A -> parameter in the <A -HREF="smb.conf.5.html" -TARGET="_top" -><TT -CLASS="FILENAME" ->smb.conf(5)</TT -></A -> file.</P -></DD -><DT ->-l|--logfile=logbasename</DT +>-d|--debug=<debuglevel></DT ><DD ><P ->File name for log/debug files. The extension -<CODE -CLASS="CONSTANT" ->".client"</CODE -> will be appended. The log file is -never removed by the client.</P +>sets debugging to specified level</P ></DD ><DT >-v|--verbose</DT @@ -190,12 +114,13 @@ never removed by the client.</P >-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 @@ -206,19 +131,31 @@ CLASS="REFENTRYTITLE" >causes smbstatus to only list shares.</P ></DD ><DT ->-h|--help</DT +>-s|--conf=<configuration file></DT ><DD ><P ->Print a summary of command line options.</P +>The default configuration file name is + determined at compile time. The file specified contains the + configuration details required by the server. See <A +HREF="smb.conf.5.html" +TARGET="_top" +><TT +CLASS="FILENAME" +>smb.conf(5)</TT +> + </A +> for more information.</P ></DD ><DT ->-u|--user=<username></DT +>-u|--user=<username></DT ><DD ><P >selects information relevant to - <VAR + <TT CLASS="PARAMETER" ->username</VAR +><I +>username</I +></TT > only.</P ></DD ></DL @@ -227,7 +164,7 @@ CLASS="PARAMETER" ><DIV CLASS="REFSECT1" ><A -NAME="AEN99" +NAME="AEN75" ></A ><H2 >VERSION</H2 @@ -238,29 +175,29 @@ NAME="AEN99" ><DIV CLASS="REFSECT1" ><A -NAME="AEN102" +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="AEN111" +NAME="AEN84" ></A ><H2 >AUTHOR</H2 @@ -272,14 +209,14 @@ NAME="AEN111" ><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 87026c35b5..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.7"></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 @@ -38,7 +38,7 @@ NAME="AEN8" ><B CLASS="COMMAND" >smbtar</B -> [-r] [-i] [-a] [-v] {-s server} [-p password] [-x services] [-X] [-N filename] [-b blocksize] [-d directory] [-l loglevel] [-u user] [-t tape] {filenames}</P +> {-s server} [-p password] [-x services] [-X] [-d directory] [-u user] [-t tape] [-t tape] [-b blocksize] [-N filename] [-i] [-r] [-l loglevel] [-v] {filenames}</P ></DIV ><DIV CLASS="REFSECT1" @@ -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 @@ -105,10 +105,12 @@ CLASS="VARIABLELIST" >-d directory</DT ><DD ><P ->Change to initial <VAR +>Change to initial <TT CLASS="PARAMETER" +><I >directory - </VAR + </I +></TT > before restoring / backing up files. </P ></DD ><DT @@ -132,20 +134,15 @@ CLASS="PARAMETER" UNIX login name. </P ></DD ><DT ->-a</DT -><DD -><P ->Reset DOS archive bit mode to - indicate file has been archived. </P -></DD -><DT >-t tape</DT ><DD ><P >Tape device. May be regular file or tape - device. Default: <VAR + device. Default: <TT CLASS="PARAMETER" ->$TAPE</VAR +><I +>$TAPE</I +></TT > environmental variable; if not set, a file called <TT CLASS="FILENAME" @@ -191,16 +188,16 @@ CLASS="COMMAND" ><DD ><P >Log (debug) level. Corresponds to the - <VAR + <TT CLASS="PARAMETER" ->-d</VAR -> flag of <SPAN -CLASS="CITEREFENTRY" -><SPAN -CLASS="REFENTRYTITLE" ->smbclient</SPAN ->(1)</SPAN ->.</P +><I +>-d</I +></TT +> flag of <B +CLASS="COMMAND" +>smbclient(1) + </B +>. </P ></DD ></DL ></DIV @@ -208,14 +205,16 @@ CLASS="REFENTRYTITLE" ><DIV CLASS="REFSECT1" ><A -NAME="AEN104" +NAME="AEN95" ></A ><H2 >ENVIRONMENT VARIABLES</H2 ><P ->The <VAR +>The <TT CLASS="PARAMETER" ->$TAPE</VAR +><I +>$TAPE</I +></TT > variable specifies the default tape device to write to. May be overridden with the -t option. </P @@ -223,7 +222,7 @@ CLASS="PARAMETER" ><DIV CLASS="REFSECT1" ><A -NAME="AEN108" +NAME="AEN99" ></A ><H2 >BUGS</H2 @@ -237,7 +236,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN112" +NAME="AEN103" ></A ><H2 >CAVEATS</H2 @@ -250,7 +249,7 @@ NAME="AEN112" ><DIV CLASS="REFSECT1" ><A -NAME="AEN115" +NAME="AEN106" ></A ><H2 >DIAGNOSTICS</H2 @@ -261,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="AEN122" +NAME="AEN112" ></A ><H2 >VERSION</H2 @@ -283,35 +285,38 @@ NAME="AEN122" ><DIV CLASS="REFSECT1" ><A -NAME="AEN125" +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="AEN137" +NAME="AEN123" ></A ><H2 >AUTHOR</H2 @@ -337,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 15ec19d7fc..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.7"></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 26cba96a28..1a05706f92 100644 --- a/docs/htmldocs/speed.html +++ b/docs/htmldocs/speed.html @@ -5,19 +5,20 @@ >Samba performance issues</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><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="Appendixes" -HREF="appendixes.html"><LINK +TITLE="Optional configuration" +HREF="optional.html"><LINK REL="PREVIOUS" -TITLE="Migration from NT4 PDC to Samba-3 PDC" -HREF="nt4migration.html"><LINK +TITLE="Group mapping HOWTO" +HREF="groupmapping.html"><LINK REL="NEXT" -TITLE="Portability" -HREF="portability.html"></HEAD +TITLE="Appendixes" +HREF="appendixes.html"></HEAD ><BODY CLASS="CHAPTER" BGCOLOR="#FFFFFF" @@ -45,7 +46,7 @@ WIDTH="10%" ALIGN="left" VALIGN="bottom" ><A -HREF="nt4migration.html" +HREF="groupmapping.html" ACCESSKEY="P" >Prev</A ></TD @@ -59,7 +60,7 @@ WIDTH="10%" ALIGN="right" VALIGN="bottom" ><A -HREF="portability.html" +HREF="appendixes.html" ACCESSKEY="N" >Next</A ></TD @@ -72,17 +73,13 @@ WIDTH="100%"></DIV CLASS="CHAPTER" ><H1 ><A -NAME="SPEED" -></A ->Chapter 28. Samba performance issues</H1 +NAME="SPEED">Chapter 22. Samba performance issues</H1 ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN4163" ->28.1. Comparisons</A -></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="AEN4169" ->28.2. Socket options</A -></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="AEN4176" ->28.3. Read size</A -></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="AEN4181" ->28.4. Max xmit</A -></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="AEN4186" ->28.5. Log level</A -></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="AEN4189" ->28.6. Read raw</A -></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="AEN4194" ->28.7. Write raw</A -></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="AEN4198" ->28.8. Slow Clients</A -></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="AEN4202" ->28.9. Slow Logins</A -></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="AEN4205" ->28.10. Client tuning</A -></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 @@ -389,7 +368,7 @@ WIDTH="33%" ALIGN="left" VALIGN="top" ><A -HREF="nt4migration.html" +HREF="groupmapping.html" ACCESSKEY="P" >Prev</A ></TD @@ -407,7 +386,7 @@ WIDTH="33%" ALIGN="right" VALIGN="top" ><A -HREF="portability.html" +HREF="appendixes.html" ACCESSKEY="N" >Next</A ></TD @@ -417,13 +396,13 @@ ACCESSKEY="N" WIDTH="33%" ALIGN="left" VALIGN="top" ->Migration from NT4 PDC to Samba-3 PDC</TD +>Group mapping HOWTO</TD ><TD WIDTH="34%" ALIGN="center" VALIGN="top" ><A -HREF="appendixes.html" +HREF="optional.html" ACCESSKEY="U" >Up</A ></TD @@ -431,7 +410,7 @@ ACCESSKEY="U" WIDTH="33%" ALIGN="right" VALIGN="top" ->Portability</TD +>Appendixes</TD ></TR ></TABLE ></DIV diff --git a/docs/htmldocs/swat.8.html b/docs/htmldocs/swat.8.html index 2abd049b71..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.7"></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 @@ -37,7 +37,7 @@ NAME="AEN8" ><B CLASS="COMMAND" >swat</B -> [-s <smb config file>] [-a]</P +> [-s <smb config file>] [-a]</P ></DIV ><DIV CLASS="REFSECT1" @@ -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. @@ -145,109 +141,17 @@ CLASS="EMPHASIS" ></SPAN ></P ></DD -><DT ->-V</DT -><DD -><P ->Prints the version number for -<B -CLASS="COMMAND" ->smbd</B ->.</P -></DD -><DT ->-s <configuration file></DT -><DD -><P ->The file specified contains the -configuration details required by the server. The -information in this file includes server-specific -information such as what printcap file to use, as well -as descriptions of all the services that the server is -to provide. See <A -HREF="smb.conf.5.html" -TARGET="_top" -><TT -CLASS="FILENAME" ->smb.conf(5)</TT -></A -> for more information. -The default configuration file name is determined at -compile time.</P -></DD -><DT ->-d|--debug=debuglevel</DT -><DD -><P -><VAR -CLASS="REPLACEABLE" ->debuglevel</VAR -> is an integer -from 0 to 10. The default value if this parameter is -not specified is zero.</P -><P ->The higher this value, the more detail will be -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 -information about operations carried out.</P -><P ->Levels above 1 will generate considerable -amounts of log data, and should only be used when -investigating a problem. Levels above 3 are designed for -use only by developers and generate HUGE amounts of log -data, most of which is extremely cryptic.</P -><P ->Note that specifying this parameter here will -override the <A -HREF="smb.conf.5.html#loglevel" -TARGET="_top" ->log -level</A -> parameter in the <A -HREF="smb.conf.5.html" -TARGET="_top" -><TT -CLASS="FILENAME" ->smb.conf(5)</TT -></A -> file.</P -></DD -><DT ->-l|--logfile=logbasename</DT -><DD -><P ->File name for log/debug files. The extension -<CODE -CLASS="CONSTANT" ->".client"</CODE -> will be appended. The log file is -never removed by the client.</P -></DD -><DT ->-h|--help</DT -><DD -><P ->Print a summary of command line options.</P -></DD ></DL ></DIV ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN80" +NAME="AEN44" ></A ><H2 >INSTALLATION</H2 ><P ->Swat is included as binary package with most distributions. The - package manager in this case takes care of the installation and - configuration. This section is only for those who have compiled - swat from scratch. - </P -><P >After you compile SWAT you need to run <B CLASS="COMMAND" >make install @@ -277,7 +181,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT2" ><A -NAME="AEN93" +NAME="AEN56" ></A ><H3 >Inetd Installation</H3 @@ -306,7 +210,7 @@ CLASS="COMMAND" >swat 901/tcp</B ></P ><P ->Note for NIS/YP and LDAP users - you may need to rebuild the +>Note for NIS/YP users - you may need to rebuild the NIS service maps rather than alter your local <TT CLASS="FILENAME" > /etc/services</TT @@ -347,27 +251,27 @@ CLASS="COMMAND" </B > where PID is the process ID of the inetd daemon. </P ></DIV -></DIV ><DIV -CLASS="REFSECT1" +CLASS="REFSECT2" ><A -NAME="AEN115" +NAME="AEN78" ></A -><H2 ->LAUNCHING</H2 +><H3 +>Launching</H3 ><P >To launch SWAT just run your favorite web browser and - point it at "http://localhost:901/".</P + point it at "http://localhost:901/".</P ><P >Note that you can attach to SWAT from any IP connected - machine but connecting from a remote machine leaves your - connection open to password sniffing as passwords will be sent - in the clear over the wire. </P + machine but connecting from a remote machine leaves your + connection open to password sniffing as passwords will be sent + in the clear over the wire. </P +></DIV ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN119" +NAME="AEN82" ></A ><H2 >FILES</H2 @@ -404,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" @@ -427,7 +329,7 @@ CLASS="FILENAME" ><DIV CLASS="REFSECT1" ><A -NAME="AEN142" +NAME="AEN103" ></A ><H2 >WARNINGS</H2 @@ -435,20 +337,22 @@ NAME="AEN142" ><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, <VAR + comments, <TT CLASS="PARAMETER" ->include=</VAR -> and <VAR +><I +>include=</I +></TT +> and <TT CLASS="PARAMETER" +><I >copy= - </VAR + </I +></TT > options. If you have a carefully crafted <TT CLASS="FILENAME" > smb.conf</TT @@ -457,17 +361,18 @@ CLASS="FILENAME" ><DIV CLASS="REFSECT1" ><A -NAME="AEN152" +NAME="AEN111" ></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="AEN155" +NAME="AEN114" ></A ><H2 >SEE ALSO</H2 @@ -475,24 +380,26 @@ NAME="AEN155" ><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="AEN165" +NAME="AEN121" ></A ><H2 >AUTHOR</H2 @@ -504,14 +411,14 @@ NAME="AEN165" ><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 261f522341..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.7"></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 @@ -126,28 +115,20 @@ CLASS="COMMAND" names and before dumping the service definitions.</P ></DD ><DT ->-h|--help</DT +>-h</DT ><DD ><P ->Print a summary of command line options.</P -></DD -><DT ->-V</DT -><DD -><P ->Prints the version number for -<B -CLASS="COMMAND" ->smbd</B ->.</P +>Print usage message </P ></DD ><DT >-L servername</DT ><DD ><P ->Sets the value of the %L macro to <VAR +>Sets the value of the %L macro to <TT CLASS="REPLACEABLE" ->servername</VAR +><I +>servername</I +></TT >. This is useful for testing include files specified with the %L macro. </P @@ -157,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 @@ -178,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 @@ -195,20 +172,21 @@ CLASS="REFENTRYTITLE" specified, then <B CLASS="COMMAND" >testparm</B -> will examine the <VAR +> will examine the <TT CLASS="PARAMETER" +><I >hosts - allow</VAR -> and <VAR + allow</I +></TT +> and <TT CLASS="PARAMETER" ->hosts deny</VAR +><I +>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 @@ -232,7 +210,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN92" +NAME="AEN77" ></A ><H2 >FILES</H2 @@ -242,22 +220,16 @@ NAME="AEN92" 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 @@ -267,7 +239,7 @@ CLASS="REFENTRYTITLE" ><DIV CLASS="REFSECT1" ><A -NAME="AEN105" +NAME="AEN86" ></A ><H2 >DIAGNOSTICS</H2 @@ -281,7 +253,7 @@ NAME="AEN105" ><DIV CLASS="REFSECT1" ><A -NAME="AEN108" +NAME="AEN89" ></A ><H2 >VERSION</H2 @@ -292,29 +264,33 @@ NAME="AEN108" ><DIV CLASS="REFSECT1" ><A -NAME="AEN111" +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="AEN120" +NAME="AEN99" ></A ><H2 >AUTHOR</H2 @@ -326,14 +302,14 @@ NAME="AEN120" ><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 02eea8c57b..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.7"></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,17 +158,17 @@ CLASS="FILENAME" ><DIV CLASS="REFSECT1" ><A -NAME="AEN53" +NAME="AEN48" ></A ><H2 >DIAGNOSTICS</H2 ><P >If a printer is found to be valid, the message - "Printer name <printername> is valid" will be + "Printer name <printername> is valid" will be displayed. </P ><P >If a printer is found to be invalid, the message - "Printer name <printername> is not valid" will be + "Printer name <printername> is not valid" will be displayed. </P ><P >All messages that would normally be logged during @@ -189,18 +186,18 @@ CLASS="FILENAME" ><DIV CLASS="REFSECT1" ><A -NAME="AEN60" +NAME="AEN55" ></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="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 4f0735b5ab..e3f09acc18 100644 --- a/docs/htmldocs/type.html +++ b/docs/htmldocs/type.html @@ -5,16 +5,17 @@ >Type of installation</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><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="Nomenclature of Server Types" -HREF="servertype.html"></HEAD +TITLE="User and Share security level (for servers not in a domain)" +HREF="securitylevels.html"></HEAD ><BODY CLASS="PART" BGCOLOR="#FFFFFF" @@ -42,7 +43,7 @@ WIDTH="10%" ALIGN="left" VALIGN="bottom" ><A -HREF="passdb.html" +HREF="pwencrypt.html" ACCESSKEY="P" >Prev</A ></TD @@ -56,7 +57,7 @@ WIDTH="10%" ALIGN="right" VALIGN="bottom" ><A -HREF="servertype.html" +HREF="securitylevels.html" ACCESSKEY="N" >Next</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="AEN688" -></A -><H1 +NAME="AEN531"><H1 >Introduction</H1 ><P >Samba can operate in various SMB networks. This part contains information on configuring samba @@ -94,211 +91,151 @@ CLASS="TOC" >Table of Contents</B ></DT ><DT ->4. <A -HREF="servertype.html" ->Nomenclature of Server Types</A -></DT -><DD -><DL -><DT ->4.1. <A -HREF="servertype.html#AEN717" ->Stand Alone Server</A -></DT -><DT ->4.2. <A -HREF="servertype.html#AEN724" ->Domain Member Server</A -></DT -><DT ->4.3. <A -HREF="servertype.html#AEN730" ->Domain Controller</A -></DT -><DD -><DL -><DT ->4.3.1. <A -HREF="servertype.html#AEN733" ->Domain Controller Types</A -></DT -></DL -></DD -></DL -></DD -><DT >5. <A HREF="securitylevels.html" ->Samba as Stand-Alone Server</A -></DT -><DD -><DL -><DT ->5.1. <A -HREF="securitylevels.html#AEN766" ->User and Share security level</A -></DT -><DD -><DL -><DT ->5.1.1. <A -HREF="securitylevels.html#AEN769" ->User Level Security</A -></DT -><DT ->5.1.2. <A -HREF="securitylevels.html#AEN779" ->Share Level Security</A -></DT -><DT ->5.1.3. <A -HREF="securitylevels.html#AEN785" ->Server Level Security</A -></DT -><DT ->5.1.4. <A -HREF="securitylevels.html#AEN825" ->Domain Level Security</A -></DT -><DT ->5.1.5. <A -HREF="securitylevels.html#AEN848" ->ADS Level Security</A +>User and Share security level (for servers not in a domain)</A ></DT -></DL -></DD -></DL -></DD ><DT >6. <A HREF="samba-pdc.html" ->Samba as an NT4 or Win2k Primary Domain Controller</A +>How to Configure Samba as a NT4 Primary Domain Controller</A ></DT ><DD ><DL ><DT >6.1. <A -HREF="samba-pdc.html#AEN878" +HREF="samba-pdc.html#AEN575" >Prerequisite Reading</A ></DT ><DT >6.2. <A -HREF="samba-pdc.html#AEN883" +HREF="samba-pdc.html#AEN581" >Background</A ></DT ><DT >6.3. <A -HREF="samba-pdc.html#AEN923" +HREF="samba-pdc.html#AEN620" >Configuring the Samba Domain Controller</A ></DT ><DT >6.4. <A -HREF="samba-pdc.html#AEN965" ->Creating Machine Trust Accounts and Joining Clients to the Domain</A +HREF="samba-pdc.html#AEN663" +>Creating Machine Trust Accounts and Joining Clients to the +Domain</A ></DT ><DD ><DL ><DT >6.4.1. <A -HREF="samba-pdc.html#AEN1008" +HREF="samba-pdc.html#AEN682" >Manual Creation of Machine Trust Accounts</A ></DT ><DT >6.4.2. <A -HREF="samba-pdc.html#AEN1049" +HREF="samba-pdc.html#AEN723" >"On-the-Fly" Creation of Machine Trust Accounts</A ></DT ><DT >6.4.3. <A -HREF="samba-pdc.html#AEN1058" +HREF="samba-pdc.html#AEN732" >Joining the Client to the Domain</A ></DT ></DL ></DD ><DT >6.5. <A -HREF="samba-pdc.html#AEN1073" +HREF="samba-pdc.html#AEN747" >Common Problems and Errors</A ></DT ><DT >6.6. <A -HREF="samba-pdc.html#AEN1119" ->What other help can I get?</A +HREF="samba-pdc.html#AEN795" +>System Policies and Profiles</A ></DT ><DT >6.7. <A -HREF="samba-pdc.html#AEN1233" +HREF="samba-pdc.html#AEN839" +>What other help can I get?</A +></DT +><DT +>6.8. <A +HREF="samba-pdc.html#AEN953" >Domain Control for Windows 9x/ME</A ></DT ><DD ><DL ><DT ->6.7.1. <A -HREF="samba-pdc.html#AEN1256" +>6.8.1. <A +HREF="samba-pdc.html#AEN979" >Configuration Instructions: Network Logons</A ></DT +><DT +>6.8.2. <A +HREF="samba-pdc.html#AEN998" +>Configuration Instructions: Setting up Roaming User Profiles</A +></DT ></DL ></DD +><DT +>6.9. <A +HREF="samba-pdc.html#AEN1091" +>DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba</A +></DT ></DL ></DD ><DT >7. <A HREF="samba-bdc.html" ->Samba Backup Domain Controller to Samba Domain Control</A +>How to Act as a Backup Domain Controller in a Purely Samba Controlled Domain</A ></DT ><DD ><DL ><DT >7.1. <A -HREF="samba-bdc.html#AEN1286" +HREF="samba-bdc.html#AEN1127" >Prerequisite Reading</A ></DT ><DT >7.2. <A -HREF="samba-bdc.html#AEN1290" +HREF="samba-bdc.html#AEN1131" >Background</A ></DT ><DT >7.3. <A -HREF="samba-bdc.html#AEN1298" +HREF="samba-bdc.html#AEN1139" >What qualifies a Domain Controller on the network?</A ></DT ><DD ><DL ><DT >7.3.1. <A -HREF="samba-bdc.html#AEN1301" +HREF="samba-bdc.html#AEN1142" >How does a Workstation find its domain controller?</A ></DT ><DT >7.3.2. <A -HREF="samba-bdc.html#AEN1304" +HREF="samba-bdc.html#AEN1145" >When is the PDC needed?</A ></DT ></DL ></DD ><DT >7.4. <A -HREF="samba-bdc.html#AEN1307" ->Can Samba be a Backup Domain Controller to an NT PDC?</A +HREF="samba-bdc.html#AEN1148" +>Can Samba be a Backup Domain Controller?</A ></DT ><DT >7.5. <A -HREF="samba-bdc.html#AEN1312" +HREF="samba-bdc.html#AEN1152" >How do I set up a Samba BDC?</A ></DT ><DD ><DL ><DT >7.5.1. <A -HREF="samba-bdc.html#AEN1329" +HREF="samba-bdc.html#AEN1169" >How do I replicate the smbpasswd file?</A ></DT -><DT ->7.5.2. <A -HREF="samba-bdc.html#AEN1333" ->Can I do this all with LDAP?</A -></DT ></DL ></DD ></DL @@ -312,50 +249,51 @@ HREF="ads.html" ><DL ><DT >8.1. <A -HREF="ads.html#AEN1355" ->Setup your <TT -CLASS="FILENAME" ->smb.conf</TT -></A +HREF="ads.html#AEN1187" +>Installing the required packages for Debian</A ></DT ><DT >8.2. <A -HREF="ads.html#AEN1368" ->Setup your <TT -CLASS="FILENAME" ->/etc/krb5.conf</TT -></A +HREF="ads.html#AEN1193" +>Installing the required packages for RedHat</A ></DT ><DT >8.3. <A -HREF="ads.html#ADS-CREATE-MACHINE-ACCOUNT" +HREF="ads.html#AEN1202" +>Compile Samba</A +></DT +><DT +>8.4. <A +HREF="ads.html#AEN1217" +>Setup your /etc/krb5.conf</A +></DT +><DT +>8.5. <A +HREF="ads.html#AEN1227" >Create the computer account</A ></DT ><DD ><DL ><DT ->8.3.1. <A -HREF="ads.html#AEN1396" +>8.5.1. <A +HREF="ads.html#AEN1231" >Possible errors</A ></DT ></DL ></DD ><DT ->8.4. <A -HREF="ads.html#ADS-TEST-SERVER" +>8.6. <A +HREF="ads.html#AEN1243" >Test your server setup</A ></DT ><DT ->8.5. <A -HREF="ads.html#ADS-TEST-SMBCLIENT" ->Testing with <SPAN -CLASS="APPLICATION" ->smbclient</SPAN -></A +>8.7. <A +HREF="ads.html#AEN1248" +>Testing with smbclient</A ></DT ><DT ->8.6. <A -HREF="ads.html#AEN1416" +>8.8. <A +HREF="ads.html#AEN1251" >Notes</A ></DT ></DL @@ -363,18 +301,23 @@ HREF="ads.html#AEN1416" ><DT >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 >9.1. <A -HREF="domain-security.html#AEN1439" ->Joining an NT Domain with Samba 3.0</A +HREF="domain-security.html#AEN1273" +>Joining an NT Domain with Samba 2.2</A ></DT ><DT >9.2. <A -HREF="domain-security.html#AEN1493" +HREF="domain-security.html#AEN1337" +>Samba and Windows 2000 Domains</A +></DT +><DT +>9.3. <A +HREF="domain-security.html#AEN1342" >Why is this better than security = server?</A ></DT ></DL @@ -399,7 +342,7 @@ WIDTH="33%" ALIGN="left" VALIGN="top" ><A -HREF="passdb.html" +HREF="pwencrypt.html" ACCESSKEY="P" >Prev</A ></TD @@ -417,7 +360,7 @@ WIDTH="33%" ALIGN="right" VALIGN="top" ><A -HREF="servertype.html" +HREF="securitylevels.html" ACCESSKEY="N" >Next</A ></TD @@ -427,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" @@ -437,7 +380,7 @@ VALIGN="top" WIDTH="33%" ALIGN="right" VALIGN="top" ->Nomenclature of Server Types</TD +>User and Share security level (for servers not in a domain)</TD ></TR ></TABLE ></DIV diff --git a/docs/htmldocs/unix-permissions.html b/docs/htmldocs/unix-permissions.html index 65c3f5352e..f29d450e6d 100644 --- a/docs/htmldocs/unix-permissions.html +++ b/docs/htmldocs/unix-permissions.html @@ -5,19 +5,21 @@ >UNIX Permission Bits and Windows NT Access Control Lists</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><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="Advanced Configuration" +TITLE="Optional configuration" HREF="optional.html"><LINK REL="PREVIOUS" -TITLE="Advanced Configuration" -HREF="optional.html"><LINK +TITLE="Integrating MS Windows networks with Samba" +HREF="integrate-ms-networks.html"><LINK REL="NEXT" -TITLE="Configuring Group Mapping" -HREF="groupmapping.html"></HEAD +TITLE="Configuring PAM for distributed but centrally +managed authentication" +HREF="pam.html"></HEAD ><BODY CLASS="CHAPTER" BGCOLOR="#FFFFFF" @@ -45,7 +47,7 @@ WIDTH="10%" ALIGN="left" VALIGN="bottom" ><A -HREF="optional.html" +HREF="integrate-ms-networks.html" ACCESSKEY="P" >Prev</A ></TD @@ -59,7 +61,7 @@ WIDTH="10%" ALIGN="right" VALIGN="bottom" ><A -HREF="groupmapping.html" +HREF="pam.html" ACCESSKEY="N" >Next</A ></TD @@ -72,69 +74,52 @@ 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="AEN1525" ->10.1. Viewing and changing UNIX permissions using the NT - security dialogs</A -></H1 +NAME="AEN1605">11.1. Viewing and changing UNIX permissions using the NT + security dialogs</H1 ><P ->Windows NT clients can use their native security settings - dialog box to view and modify the underlying UNIX permissions.</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 -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 -> All access to Unix/Linux system file via Samba is controlled at - the operating system file access control level. When trying to - figure out file access problems it is vitally important to identify - the identity of the Windows user as it is presented by Samba at - the point of file access. This can best be determined from the - Samba log files. - </P -></TD -></TR -></TABLE -></DIV +>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="AEN1531" ->10.2. How to view file security on a Samba share</A -></H1 +NAME="AEN1614">11.2. How to view file security on a Samba share</H1 ><P ->From an NT4/2000/XP client, single-click with the right +>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 @@ -144,14 +129,15 @@ CLASS="EMPHASIS" >Properties</I ></SPAN > entry at the bottom of - the menu. This brings up the file properties dialog - box. Click on the tab <SPAN + 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 -> and you +>. Click on this tab and you will see three buttons, <SPAN CLASS="emphasis" ><I @@ -199,9 +185,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1542" ->10.3. Viewing file ownership</A -></H1 +NAME="AEN1625">11.3. Viewing file ownership</H1 ><P >Clicking on the <B CLASS="COMMAND" @@ -215,17 +199,23 @@ CLASS="COMMAND" >"SERVER\user (Long name)"</B ></P ><P ->Where <VAR +>Where <TT CLASS="REPLACEABLE" ->SERVER</VAR +><I +>SERVER</I +></TT > is the NetBIOS name of - the Samba server, <VAR + the Samba server, <TT CLASS="REPLACEABLE" ->user</VAR +><I +>user</I +></TT > is the user name of - the UNIX user who owns the file, and <VAR + the UNIX user who owns the file, and <TT CLASS="REPLACEABLE" ->(Long name)</VAR +><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 @@ -234,13 +224,15 @@ CLASS="COMMAND" </B > button to remove this dialog.</P ><P ->If the parameter <VAR +>If the parameter <TT CLASS="PARAMETER" ->nt acl support</VAR +><I +>nt acl support</I +></TT > - is set to <CODE + is set to <TT CLASS="CONSTANT" ->false</CODE +>false</TT > then the file owner will be shown as the NT user <B CLASS="COMMAND" @@ -268,7 +260,7 @@ CLASS="EMPHASIS" ><P >There is an NT chown command that will work with Samba and allow a user with Administrator privilege connected - to a Samba server as root to change the ownership of + 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" @@ -285,9 +277,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1562" ->10.4. Viewing file or directory permissions</A -></H1 +NAME="AEN1645">11.4. Viewing file or directory permissions</H1 ><P >The third button is the <B CLASS="COMMAND" @@ -302,28 +292,36 @@ CLASS="COMMAND" >"SERVER\user (Long name)"</B ></P ><P ->Where <VAR +>Where <TT CLASS="REPLACEABLE" ->SERVER</VAR +><I +>SERVER</I +></TT > is the NetBIOS name of - the Samba server, <VAR + the Samba server, <TT CLASS="REPLACEABLE" ->user</VAR +><I +>user</I +></TT > is the user name of - the UNIX user who owns the file, and <VAR + the UNIX user who owns the file, and <TT CLASS="REPLACEABLE" ->(Long name)</VAR +><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 <VAR +>If the parameter <TT CLASS="PARAMETER" ->nt acl support</VAR +><I +>nt acl support</I +></TT > - is set to <CODE + is set to <TT CLASS="CONSTANT" ->false</CODE +>false</TT > then the file owner will be shown as the NT user <B CLASS="COMMAND" @@ -339,9 +337,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1577" ->10.4.1. File Permissions</A -></H2 +NAME="AEN1660">11.4.1. File Permissions</H2 ><P >The standard UNIX user/group/world triple and the corresponding "read", "write", "execute" permissions @@ -401,9 +397,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1591" ->10.4.2. Directory Permissions</A -></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 @@ -433,9 +427,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1598" ->10.5. Modifying file or directory permissions</A -></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 @@ -447,13 +439,15 @@ CLASS="COMMAND" with the standard Samba permission masks and mapping of DOS attributes that need to also be taken into account.</P ><P ->If the parameter <VAR +>If the parameter <TT CLASS="PARAMETER" ->nt acl support</VAR +><I +>nt acl support</I +></TT > - is set to <CODE + is set to <TT CLASS="CONSTANT" ->false</CODE +>false</TT > then any attempt to set security permissions will fail with an <B CLASS="COMMAND" @@ -465,7 +459,7 @@ CLASS="COMMAND" CLASS="COMMAND" >"Add"</B > - button will not return a list of users in Samba (it will give + 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 @@ -529,33 +523,38 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1620" ->10.6. Interaction with the standard Samba create mask - parameters</A -></H1 +NAME="AEN1703">11.6. Interaction with the standard Samba create mask + parameters</H1 ><P ->There are four parameters - to control interaction with the standard Samba create mask parameters. - These are :</P +>Note that with Samba 2.0.5 there are four new parameters + to control this interaction. These are :</P ><P -><VAR +><TT CLASS="PARAMETER" ->security mask</VAR +><I +>security mask</I +></TT ></P ><P -><VAR +><TT CLASS="PARAMETER" ->force security mode</VAR +><I +>force security mode</I +></TT ></P ><P -><VAR +><TT CLASS="PARAMETER" ->directory security mask</VAR +><I +>directory security mask</I +></TT ></P ><P -><VAR +><TT CLASS="PARAMETER" ->force directory security mode</VAR +><I +>force directory security mode</I +></TT ></P ><P >Once a user clicks <B @@ -568,17 +567,21 @@ CLASS="COMMAND" HREF="smb.conf.5.html#SECURITYMASK" TARGET="_top" > - <VAR + <TT CLASS="PARAMETER" ->security mask</VAR +><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 <VAR +>Essentially, zero bits in the <TT CLASS="PARAMETER" ->security mask</VAR +><I +>security mask</I +></TT > mask may be treated as a set of bits the user is <SPAN CLASS="emphasis" @@ -594,31 +597,38 @@ CLASS="EMPHASIS" the <A HREF="smb.conf.5.html#CREATEMASK" TARGET="_top" -><VAR +><TT CLASS="PARAMETER" +><I >create mask - </VAR + </I +></TT ></A -> parameter. To allow a user to modify all the - user/group/world permissions on a file, set this parameter +> 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" -> <VAR +> <TT CLASS="PARAMETER" ->force security mode</VAR +><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 <VAR +>Essentially, bits set in the <TT CLASS="PARAMETER" +><I >force security mode - </VAR + </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 @@ -626,60 +636,85 @@ CLASS="PARAMETER" as the <A HREF="smb.conf.5.html#FORCECREATEMODE" TARGET="_top" -><VAR +><TT CLASS="PARAMETER" +><I >force - create mode</VAR + create mode</I +></TT ></A -> parameter. +> 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 <VAR +>The <TT CLASS="PARAMETER" ->security mask</VAR -> and <VAR +><I +>security mask</I +></TT +> and <TT CLASS="PARAMETER" +><I >force - security mode</VAR + 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 <VAR + described above for a file except using the parameter <TT CLASS="PARAMETER" -> directory security mask</VAR -> instead of <VAR +><I +> directory security mask</I +></TT +> instead of <TT CLASS="PARAMETER" +><I >security - mask</VAR ->, and <VAR + mask</I +></TT +>, and <TT CLASS="PARAMETER" +><I >force directory security mode - </VAR -> parameter instead of <VAR + </I +></TT +> parameter instead of <TT CLASS="PARAMETER" +><I >force security mode - </VAR + </I +></TT >.</P ><P ->The <VAR +>The <TT CLASS="PARAMETER" ->directory security mask</VAR +><I +>directory security mask</I +></TT > parameter - by default is set to the same value as the <VAR + by default is set to the same value as the <TT CLASS="PARAMETER" +><I >directory mask - </VAR -> parameter and the <VAR + </I +></TT +> parameter and the <TT CLASS="PARAMETER" +><I >force directory security - mode</VAR + mode</I +></TT > parameter by default is set to the same value as - the <VAR + the <TT CLASS="PARAMETER" ->force directory mode</VAR -> parameter. </P +><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 @@ -688,40 +723,83 @@ CLASS="PARAMETER" >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 <TT + parameters in the <A +HREF="smb.conf.5.html" +TARGET="_top" +><TT CLASS="FILENAME" ->smb.conf</TT +>smb.conf(5) + </TT +></A > file in that share specific section :</P ><P -><VAR +><TT CLASS="PARAMETER" ->security mask = 0777</VAR +><I +>security mask = 0777</I +></TT ></P ><P -><VAR +><TT CLASS="PARAMETER" ->force security mode = 0</VAR +><I +>force security mode = 0</I +></TT ></P ><P -><VAR +><TT CLASS="PARAMETER" ->directory security mask = 0777</VAR +><I +>directory security mask = 0777</I +></TT ></P ><P -><VAR +><TT CLASS="PARAMETER" ->force directory security mode = 0</VAR +><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" ><H1 CLASS="SECT1" ><A -NAME="AEN1673" ->10.7. Interaction with the standard Samba file attribute - mapping</A -></H1 +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 only") into the UNIX permissions of a file. This means there can @@ -777,7 +855,7 @@ WIDTH="33%" ALIGN="left" VALIGN="top" ><A -HREF="optional.html" +HREF="integrate-ms-networks.html" ACCESSKEY="P" >Prev</A ></TD @@ -795,7 +873,7 @@ WIDTH="33%" ALIGN="right" VALIGN="top" ><A -HREF="groupmapping.html" +HREF="pam.html" ACCESSKEY="N" >Next</A ></TD @@ -805,7 +883,7 @@ ACCESSKEY="N" WIDTH="33%" ALIGN="left" VALIGN="top" ->Advanced Configuration</TD +>Integrating MS Windows networks with Samba</TD ><TD WIDTH="34%" ALIGN="center" @@ -819,7 +897,8 @@ ACCESSKEY="U" WIDTH="33%" ALIGN="right" VALIGN="top" ->Configuring Group Mapping</TD +>Configuring PAM for distributed but centrally +managed authentication</TD ></TR ></TABLE ></DIV diff --git a/docs/htmldocs/vfs.html b/docs/htmldocs/vfs.html index 6f5e852b1a..11934ae47c 100644 --- a/docs/htmldocs/vfs.html +++ b/docs/htmldocs/vfs.html @@ -5,19 +5,20 @@ >Stackable VFS modules</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><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="Advanced Configuration" +TITLE="Optional configuration" HREF="optional.html"><LINK REL="PREVIOUS" -TITLE="PAM Configuration for Centrally Managed Authentication" -HREF="pam.html"><LINK +TITLE="Passdb XML plugin" +HREF="pdb-xml.html"><LINK REL="NEXT" -TITLE="Hosting a Microsoft Distributed File System tree on Samba" -HREF="msdfs.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="pam.html" +HREF="pdb-xml.html" ACCESSKEY="P" >Prev</A ></TD @@ -59,7 +60,7 @@ WIDTH="10%" ALIGN="right" VALIGN="bottom" ><A -HREF="msdfs.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 20. Stackable VFS modules</H1 +NAME="VFS">Chapter 18. Stackable VFS modules</H1 ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3531" ->20.1. Introduction and configuration</A -></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="AEN3540" ->20.2. Included modules</A -></H1 +NAME="AEN2649">18.2. Included modules</H1 ><DIV CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3542" ->20.2.1. audit</A -></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,31 +160,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3550" ->20.2.2. extd_audit</A -></H2 -><P ->This module is identical with the <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->audit</I -></SPAN -> module above except -that it sends audit logs to both syslog as well as the smbd log file/s. The -loglevel for this module is set in the smb.conf file. At loglevel = 0, only file -and directory deletions and directory and file creations are logged. At loglevel = 1 -file opens are renames and permission changes are logged , while at loglevel = 2 file -open and close calls are logged also.</P -></DIV -><DIV -CLASS="SECT2" -><H2 -CLASS="SECT2" -><A -NAME="AEN3554" ->20.2.3. recycle</A -></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 @@ -260,9 +229,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3591" ->20.2.4. netatalk</A -></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 @@ -293,9 +260,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3598" ->20.3. VFS modules available elsewhere</A -></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 @@ -309,9 +274,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3602" ->20.3.1. DatabaseFS</A -></H2 +NAME="AEN2707">18.3.1. DatabaseFS</H2 ><P >URL: <A HREF="http://www.css.tayloru.edu/~elorimer/databasefs/index.php" @@ -343,9 +306,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3610" ->20.3.2. vscan</A -></H2 +NAME="AEN2715">18.3.2. vscan</H2 ><P >URL: <A HREF="http://www.openantivirus.org/" @@ -377,7 +338,7 @@ WIDTH="33%" ALIGN="left" VALIGN="top" ><A -HREF="pam.html" +HREF="pdb-xml.html" ACCESSKEY="P" >Prev</A ></TD @@ -395,7 +356,7 @@ WIDTH="33%" ALIGN="right" VALIGN="top" ><A -HREF="msdfs.html" +HREF="samba-ldap-howto.html" ACCESSKEY="N" >Next</A ></TD @@ -405,7 +366,7 @@ ACCESSKEY="N" WIDTH="33%" ALIGN="left" VALIGN="top" ->PAM Configuration for Centrally Managed Authentication</TD +>Passdb XML plugin</TD ><TD WIDTH="34%" ALIGN="center" @@ -419,7 +380,7 @@ ACCESSKEY="U" WIDTH="33%" ALIGN="right" VALIGN="top" ->Hosting a Microsoft Distributed File System tree on Samba</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 229f132ca8..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.7"></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 @@ -85,60 +80,14 @@ CLASS="VARIABLELIST" </P ></DD ><DT ->-h|--help</DT -><DD -><P ->Print a summary of command line options.</P -></DD -><DT ->-l|--logfile=logbasename</DT -><DD -><P ->File name for log/debug files. The extension - <CODE -CLASS="CONSTANT" ->'.client'</CODE -> will be appended. The log file is never removed - by the client. - </P -></DD -><DT ->-V</DT -><DD -><P ->Prints the version number for -<B -CLASS="COMMAND" ->smbd</B ->.</P -></DD -><DT ->-s <configuration file></DT -><DD -><P ->The file specified contains the -configuration details required by the server. The -information in this file includes server-specific -information such as what printcap file to use, as well -as descriptions of all the services that the server is -to provide. See <A -HREF="smb.conf.5.html" -TARGET="_top" -><TT -CLASS="FILENAME" ->smb.conf(5)</TT -></A -> for more information. -The default configuration file name is determined at -compile time.</P -></DD -><DT >-d|--debug=debuglevel</DT ><DD ><P -><VAR +><TT CLASS="REPLACEABLE" ->debuglevel</VAR +><I +>debuglevel</I +></TT > is an integer from 0 to 10. The default value if this parameter is not specified is zero.</P @@ -172,15 +121,22 @@ CLASS="FILENAME" > file.</P ></DD ><DT +>-h|--help</DT +><DD +><P +>Print a summary of command line options.</P +></DD +><DT >-l|--logfile=logbasename</DT ><DD ><P >File name for log/debug files. The extension -<CODE + <TT CLASS="CONSTANT" ->".client"</CODE -> will be appended. The log file is -never removed by the client.</P +>'.client'</TT +> will be appended. The log file is never removed + by the client. + </P ></DD ></DL ></DIV @@ -188,17 +144,14 @@ never removed by the client.</P ><DIV CLASS="REFSECT1" ><A -NAME="AEN66" +NAME="AEN48" ></A ><H2 >COMMANDS</H2 ><P -><SPAN -CLASS="emphasis" ><I CLASS="EMPHASIS" >VFS COMMANDS</I -></SPAN ></P ><P ></P @@ -459,12 +412,9 @@ CLASS="COMMAND" ></LI ></UL ><P -><SPAN -CLASS="emphasis" ><I CLASS="EMPHASIS" >GENERAL COMMANDS</I -></SPAN ></P ><P ></P @@ -509,7 +459,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN197" +NAME="AEN179" ></A ><H2 >VERSION</H2 @@ -520,7 +470,7 @@ NAME="AEN197" ><DIV CLASS="REFSECT1" ><A -NAME="AEN200" +NAME="AEN182" ></A ><H2 >AUTHOR</H2 diff --git a/docs/htmldocs/wbinfo.1.html b/docs/htmldocs/wbinfo.1.html index 9833239078..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.7"></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 @@ -37,42 +37,38 @@ NAME="AEN8" ><B CLASS="COMMAND" >wbinfo</B -> [-u] [-g] [-N netbios-name] [-I ip] [-n name] [-s sid] [-U uid] [-G gid] [-S sid] [-Y sid] [-t] [-m] [--sequence] [-r user] [-a user%password] [-A user%password] [--get-auth-user] [-p]</P +> [-u] [-g] [-i ip] [-N netbios-name] [-n name] [-s sid] [-U uid] [-G gid] [-S sid] [-Y sid] [-t] [-m] [-r user] [-a user%password] [-A user%password] [-p]</P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN29" +NAME="AEN27" ></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 >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="AEN45" +NAME="AEN38" ></A ><H2 >OPTIONS</H2 @@ -97,64 +93,55 @@ 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 >-N name</DT ><DD ><P ->The <VAR +>The <TT CLASS="PARAMETER" ->-N</VAR +><I +>-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 <VAR + specified by the <TT CLASS="PARAMETER" ->name</VAR +><I +>name</I +></TT > parameter. </P ></DD @@ -162,21 +149,22 @@ CLASS="PARAMETER" >-I ip</DT ><DD ><P ->The <VAR +>The <TT CLASS="PARAMETER" ->-I</VAR +><I +>-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 <VAR + specified by the <TT CLASS="PARAMETER" ->ip</VAR +><I +>ip</I +></TT > parameter. </P ></DD @@ -184,45 +172,47 @@ CLASS="PARAMETER" >-n name</DT ><DD ><P ->The <VAR +>The <TT CLASS="PARAMETER" ->-n</VAR +><I +>-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 -> <VAR + domain used is the one specified in the <TT +CLASS="FILENAME" +>smb.conf</TT +> + <TT CLASS="PARAMETER" ->workgroup - </VAR +><I +>workgroup</I +></TT > parameter. </P ></DD ><DT >-s sid</DT ><DD ><P ->Use <VAR +>Use <TT CLASS="PARAMETER" ->-s</VAR +><I +>-s</I +></TT > to resolve - a SID to a name. This is the inverse of the <VAR + a SID to a name. This is the inverse of the <TT CLASS="PARAMETER" +><I >-n - </VAR + </I +></TT > option above. SIDs must be specified as ASCII strings in the traditional Microsoft format. For example, S-1-5-21-1455342024-3071081365-2475485837-500. </P @@ -248,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 @@ -261,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 @@ -283,25 +266,15 @@ 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. </P ></DD ><DT ->--sequence</DT -><DD -><P ->Show sequence numbers of - all known domains</P -></DD -><DT >-r username</DT ><DD ><P @@ -329,57 +302,22 @@ CLASS="REFENTRYTITLE" Windows 2000 servers only). </P ></DD -><DT ->--get-auth-user</DT -><DD -><P ->Print username and password used by winbindd - during session setup to a domain controller. Username - and password can be set using '-A'. Only available for - root.</P -></DD -><DT ->-p</DT -><DD -><P ->Check whether winbindd is still alive. - Prints out either 'succeeded' or 'failed'. - </P -></DD -><DT ->-V</DT -><DD -><P ->Prints the version number for -<B -CLASS="COMMAND" ->smbd</B ->.</P -></DD -><DT ->-h|--help</DT -><DD -><P ->Print a summary of command line options.</P -></DD ></DL ></DIV ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN170" +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 @@ -389,7 +327,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN177" +NAME="AEN125" ></A ><H2 >VERSION</H2 @@ -400,23 +338,25 @@ NAME="AEN177" ><DIV CLASS="REFSECT1" ><A -NAME="AEN180" +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="AEN186" +NAME="AEN133" ></A ><H2 >AUTHOR</H2 @@ -436,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 e08d617c63..1558512a61 100644 --- a/docs/htmldocs/winbind.html +++ b/docs/htmldocs/winbind.html @@ -5,19 +5,20 @@ >Unified Logons between Windows NT and UNIX using Winbind</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><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="Advanced Configuration" +TITLE="Optional configuration" HREF="optional.html"><LINK REL="PREVIOUS" -TITLE="CUPS Printing Support" -HREF="cups-printing.html"><LINK +TITLE="Printing Support" +HREF="printing.html"><LINK REL="NEXT" -TITLE="Advanced Network Manangement" -HREF="advancednetworkmanagement.html"></HEAD +TITLE="Passdb MySQL plugin" +HREF="pdb-mysql.html"></HEAD ><BODY CLASS="CHAPTER" BGCOLOR="#FFFFFF" @@ -45,7 +46,7 @@ WIDTH="10%" ALIGN="left" VALIGN="bottom" ><A -HREF="cups-printing.html" +HREF="printing.html" ACCESSKEY="P" >Prev</A ></TD @@ -59,7 +60,7 @@ WIDTH="10%" ALIGN="right" VALIGN="bottom" ><A -HREF="advancednetworkmanagement.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="AEN2506" ->14.1. Abstract</A -></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="AEN2510" ->14.2. Introduction</A -></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="AEN2523" ->14.3. What Winbind Provides</A -></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="AEN2530" ->14.3.1. Target Uses</A -></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="AEN2534" ->14.4. How Winbind Works</A -></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="AEN2539" ->14.4.1. Microsoft Remote Procedure Calls</A -></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="AEN2543" ->14.4.2. Microsoft Active Directory Services</A -></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="AEN2546" ->14.4.3. Name Service Switch</A -></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="AEN2562" ->14.4.4. Pluggable Authentication Modules</A -></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="AEN2570" ->14.4.5. User and Group ID Allocation</A -></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="AEN2574" ->14.4.6. Result Caching</A -></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="AEN2577" ->14.5. Installation and Configuration</A -></H1 +NAME="AEN2293">15.5. Installation and Configuration</H1 ><P >Many thanks to John Trostel <A HREF="mailto:jtrostel@snapserver.com" @@ -484,14 +442,20 @@ for providing the HOWTO for this section.</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" ><H2 CLASS="SECT2" ><A -NAME="AEN2582" ->14.5.1. Introduction</A -></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 @@ -548,9 +512,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2595" ->14.5.2. Requirements</A -></H2 +NAME="AEN2313">15.5.2. Requirements</H2 ><P >If you have a samba configuration file that you are currently using... <SPAN @@ -618,9 +580,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2609" ->14.5.3. Testing Things Out</A -></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 @@ -663,9 +623,7 @@ CLASS="SECT3" ><H3 CLASS="SECT3" ><A -NAME="AEN2620" ->14.5.3.1. Configure and compile SAMBA</A -></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 @@ -673,44 +631,44 @@ whether or not you have previously built the Samba binaries.</P ><P ><PRE CLASS="PROGRAMLISTING" -><SAMP +><TT CLASS="PROMPT" ->root#</SAMP +>root#</TT > <B CLASS="COMMAND" >autoconf</B > -<SAMP +<TT CLASS="PROMPT" ->root#</SAMP +>root#</TT > <B CLASS="COMMAND" >make clean</B > -<SAMP +<TT CLASS="PROMPT" ->root#</SAMP +>root#</TT > <B CLASS="COMMAND" >rm config.cache</B > -<SAMP +<TT CLASS="PROMPT" ->root#</SAMP +>root#</TT > <B CLASS="COMMAND" ->./configure</B +>./configure --with-winbind</B > -<SAMP +<TT CLASS="PROMPT" ->root#</SAMP +>root#</TT > <B CLASS="COMMAND" >make</B > -<SAMP +<TT CLASS="PROMPT" ->root#</SAMP +>root#</TT > <B CLASS="COMMAND" >make install</B @@ -729,13 +687,11 @@ CLASS="SECT3" ><H3 CLASS="SECT3" ><A -NAME="AEN2639" ->14.5.3.2. Configure <TT +NAME="AEN2357">15.5.3.2. Configure <TT CLASS="FILENAME" >nsswitch.conf</TT > and the -winbind libraries</A -></H3 +winbind libraries</H3 ><P >The libraries needed to run the <B CLASS="COMMAND" @@ -743,9 +699,9 @@ CLASS="COMMAND" > daemon through nsswitch need to be copied to their proper locations, so</P ><P -><SAMP +><TT CLASS="PROMPT" ->root#</SAMP +>root#</TT > <B CLASS="COMMAND" >cp ../samba/source/nsswitch/libnss_winbind.so /lib</B @@ -753,9 +709,9 @@ CLASS="COMMAND" ><P >I also found it necessary to make the following symbolic link:</P ><P -><SAMP +><TT CLASS="PROMPT" ->root#</SAMP +>root#</TT > <B CLASS="COMMAND" >ln -s /lib/libnss_winbind.so /lib/libnss_winbind.so.2</B @@ -763,23 +719,23 @@ CLASS="COMMAND" ><P >And, in the case of Sun solaris:</P ><P -><SAMP +><TT CLASS="PROMPT" ->root#</SAMP +>root#</TT > <B CLASS="COMMAND" >ln -s /usr/lib/libnss_winbind.so /usr/lib/libnss_winbind.so.1</B > -<SAMP +<TT CLASS="PROMPT" ->root#</SAMP +>root#</TT > <B CLASS="COMMAND" >ln -s /usr/lib/libnss_winbind.so /usr/lib/nss_winbind.so.1</B > -<SAMP +<TT CLASS="PROMPT" ->root#</SAMP +>root#</TT > <B CLASS="COMMAND" >ln -s /usr/lib/libnss_winbind.so /usr/lib/nss_winbind.so.2</B @@ -815,9 +771,9 @@ CLASS="COMMAND" your system reboots, but it is faster (and you don't need to reboot) if you do it manually:</P ><P -><SAMP +><TT CLASS="PROMPT" ->root#</SAMP +>root#</TT > <B CLASS="COMMAND" >/sbin/ldconfig -v | grep winbind</B @@ -834,9 +790,7 @@ CLASS="SECT3" ><H3 CLASS="SECT3" ><A -NAME="AEN2672" ->14.5.3.3. Configure smb.conf</A -></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 @@ -909,36 +863,42 @@ CLASS="SECT3" ><H3 CLASS="SECT3" ><A -NAME="AEN2688" ->14.5.3.4. Join the SAMBA server to the PDC domain</A -></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 <VAR +PDC domain, where <TT CLASS="REPLACEABLE" ->DOMAIN</VAR +><I +>DOMAIN</I +></TT > is the name of -your Windows domain and <VAR +your Windows domain and <TT CLASS="REPLACEABLE" ->Administrator</VAR +><I +>Administrator</I +></TT > is a domain user who has administrative privileges in the domain.</P ><P -><SAMP +><TT CLASS="PROMPT" ->root#</SAMP +>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 -<VAR +<TT CLASS="REPLACEABLE" ->DOMAIN</VAR ->" where <VAR +><I +>DOMAIN</I +></TT +>" where <TT CLASS="REPLACEABLE" ->DOMAIN</VAR +><I +>DOMAIN</I +></TT > is your DOMAIN name.</P ></DIV @@ -947,9 +907,7 @@ CLASS="SECT3" ><H3 CLASS="SECT3" ><A -NAME="AEN2699" ->14.5.3.5. Start up the winbindd daemon and test it!</A -></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 @@ -957,35 +915,20 @@ 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 -><SAMP +><TT CLASS="PROMPT" ->root#</SAMP +>root#</TT > <B CLASS="COMMAND" >/usr/local/samba/bin/winbindd</B ></P ><P ->Winbindd can now also run in 'dual daemon mode'. This will make it -run as 2 processes. The first will answer all requests from the cache, -thus making responses to clients faster. The other will -update the cache for the query that the first has just responded. -Advantage of this is that responses stay accurate and are faster. -You can enable dual daemon mode by adding '-B' to the commandline:</P -><P -><SAMP -CLASS="PROMPT" ->root#</SAMP -> <B -CLASS="COMMAND" ->/usr/local/samba/bin/winbindd -B</B -></P -><P >I'm always paranoid and like to make sure the daemon is really running...</P ><P -><SAMP +><TT CLASS="PROMPT" ->root#</SAMP +>root#</TT > <B CLASS="COMMAND" >ps -ae | grep winbindd</B @@ -998,9 +941,9 @@ CLASS="COMMAND" >Now... for the real test, try to get some information about the users on your PDC</P ><P -><SAMP +><TT CLASS="PROMPT" ->root#</SAMP +>root#</TT > <B CLASS="COMMAND" >/usr/local/samba/bin/wbinfo -u</B @@ -1020,10 +963,12 @@ CEO+krbtgt CEO+TsInternetUser</PRE ></P ><P ->Obviously, I have named my domain 'CEO' and my <VAR +>Obviously, I have named my domain 'CEO' and my <TT CLASS="PARAMETER" +><I >winbind -separator</VAR +separator</I +></TT > is '+'.</P ><P >You can do the same sort of thing to get group information from @@ -1031,9 +976,9 @@ the PDC:</P ><P ><PRE CLASS="PROGRAMLISTING" -><SAMP +><TT CLASS="PROMPT" ->root#</SAMP +>root#</TT > <B CLASS="COMMAND" >/usr/local/samba/bin/wbinfo -g</B @@ -1053,9 +998,9 @@ CEO+Group Policy Creator Owners</PRE lists of both local and PDC users and groups. Try the following command:</P ><P -><SAMP +><TT CLASS="PROMPT" ->root#</SAMP +>root#</TT > <B CLASS="COMMAND" >getent passwd</B @@ -1070,9 +1015,9 @@ directories and default shells.</P ><P >The same thing can be done for groups with the command</P ><P -><SAMP +><TT CLASS="PROMPT" ->root#</SAMP +>root#</TT > <B CLASS="COMMAND" >getent group</B @@ -1083,17 +1028,13 @@ CLASS="SECT3" ><H3 CLASS="SECT3" ><A -NAME="AEN2739" ->14.5.3.6. Fix the init.d startup scripts</A -></H3 +NAME="AEN2453">15.5.3.6. Fix the init.d startup scripts</H3 ><DIV CLASS="SECT4" ><H4 CLASS="SECT4" ><A -NAME="AEN2741" ->14.5.3.6.1. Linux</A -></H4 +NAME="AEN2455">15.5.3.6.1. Linux</H4 ><P >The <B CLASS="COMMAND" @@ -1156,22 +1097,8 @@ CLASS="PROGRAMLISTING" }</PRE ></P ><P ->If you would like to run winbindd in dual daemon mode, replace -the line -<PRE -CLASS="PROGRAMLISTING" -> daemon /usr/local/samba/bin/winbindd</PRE -> - -in the example above with: - -<PRE -CLASS="PROGRAMLISTING" -> daemon /usr/local/samba/bin/winbindd -B</PRE ->.</P -><P >The 'stop' function has a corresponding entry to shut down the -services and looks like this:</P +services and look s like this:</P ><P ><PRE CLASS="PROGRAMLISTING" @@ -1201,9 +1128,7 @@ CLASS="SECT4" ><H4 CLASS="SECT4" ><A -NAME="AEN2761" ->14.5.3.6.2. Solaris</A -></H4 +NAME="AEN2472">15.5.3.6.2. Solaris</H4 ><P >On solaris, you need to modify the <TT @@ -1266,28 +1191,13 @@ echo Starting Winbind Daemon ;; esac</PRE ></P -><P ->Again, if you would like to run samba in dual daemon mode, replace -<PRE -CLASS="PROGRAMLISTING" -> /usr/local/samba/bin/winbindd</PRE -> - -in the script above with: - -<PRE -CLASS="PROGRAMLISTING" -> /usr/local/samba/bin/winbindd -B</PRE -></P ></DIV ><DIV CLASS="SECT4" ><H4 CLASS="SECT4" ><A -NAME="AEN2771" ->14.5.3.6.3. Restarting</A -></H4 +NAME="AEN2479">15.5.3.6.3. Restarting</H4 ><P >If you restart the <B CLASS="COMMAND" @@ -1309,9 +1219,7 @@ CLASS="SECT3" ><H3 CLASS="SECT3" ><A -NAME="AEN2777" ->14.5.3.7. Configure Winbind and PAM</A -></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 @@ -1329,9 +1237,9 @@ CLASS="FILENAME" > directory by invoking the command</P ><P -><SAMP +><TT CLASS="PROMPT" ->root#</SAMP +>root#</TT > <B CLASS="COMMAND" >make nsswitch/pam_winbind.so</B @@ -1355,9 +1263,9 @@ CLASS="FILENAME" >/usr/lib/security</TT >.</P ><P -><SAMP +><TT CLASS="PROMPT" ->root#</SAMP +>root#</TT > <B CLASS="COMMAND" >cp ../samba/source/nsswitch/pam_winbind.so /lib/security</B @@ -1367,9 +1275,7 @@ CLASS="SECT4" ><H4 CLASS="SECT4" ><A -NAME="AEN2794" ->14.5.3.7.1. Linux/FreeBSD-specific PAM configuration</A -></H4 +NAME="AEN2502">15.5.3.7.1. Linux/FreeBSD-specific PAM configuration</H4 ><P >The <TT CLASS="FILENAME" @@ -1496,9 +1402,7 @@ CLASS="SECT4" ><H4 CLASS="SECT4" ><A -NAME="AEN2827" ->14.5.3.7.2. Solaris-specific configuration</A -></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 @@ -1572,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 @@ -1583,9 +1487,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2834" ->14.6. Limitations</A -></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 @@ -1596,7 +1498,7 @@ NAME="AEN2834" ><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 @@ -1615,8 +1517,7 @@ NAME="AEN2834" ><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 @@ -1625,9 +1526,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2844" ->14.7. Conclusion</A -></H1 +NAME="AEN2552">15.7. Conclusion</H1 ><P >The winbind system, through the use of the Name Service Switch, Pluggable Authentication Modules, and appropriate @@ -1653,7 +1552,7 @@ WIDTH="33%" ALIGN="left" VALIGN="top" ><A -HREF="cups-printing.html" +HREF="printing.html" ACCESSKEY="P" >Prev</A ></TD @@ -1671,7 +1570,7 @@ WIDTH="33%" ALIGN="right" VALIGN="top" ><A -HREF="advancednetworkmanagement.html" +HREF="pdb-mysql.html" ACCESSKEY="N" >Next</A ></TD @@ -1681,7 +1580,7 @@ ACCESSKEY="N" WIDTH="33%" ALIGN="left" VALIGN="top" ->CUPS Printing Support</TD +>Printing Support</TD ><TD WIDTH="34%" ALIGN="center" @@ -1695,7 +1594,7 @@ ACCESSKEY="U" WIDTH="33%" ALIGN="right" VALIGN="top" ->Advanced Network Manangement</TD +>Passdb MySQL plugin</TD ></TR ></TABLE ></DIV diff --git a/docs/htmldocs/winbindd.8.html b/docs/htmldocs/winbindd.8.html index df490a054b..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.7"></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 @@ -84,12 +79,16 @@ CLASS="COMMAND" CLASS="FILENAME" >pam_winbind</TT > module in the 2.2.2 release only - supports the <VAR + supports the <TT CLASS="PARAMETER" ->auth</VAR -> and <VAR +><I +>auth</I +></TT +> and <TT CLASS="PARAMETER" ->account</VAR +><I +>account</I +></TT > module-types. The latter simply performs a getpwnam() to verify that the system can obtain a uid for the @@ -167,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 @@ -188,7 +198,7 @@ CLASS="FILENAME" ><DIV CLASS="REFSECT1" ><A -NAME="AEN62" +NAME="AEN61" ></A ><H2 >OPTIONS</H2 @@ -240,90 +250,13 @@ CLASS="COMMAND" than a file.</P ></DD ><DT ->-V</DT -><DD -><P ->Prints the version number for -<B -CLASS="COMMAND" ->smbd</B ->.</P -></DD -><DT ->-s <configuration file></DT -><DD -><P ->The file specified contains the -configuration details required by the server. The -information in this file includes server-specific -information such as what printcap file to use, as well -as descriptions of all the services that the server is -to provide. See <A -HREF="smb.conf.5.html" -TARGET="_top" -><TT -CLASS="FILENAME" ->smb.conf(5)</TT -></A -> for more information. -The default configuration file name is determined at -compile time.</P -></DD -><DT ->-d|--debug=debuglevel</DT +>-d debuglevel</DT ><DD ><P -><VAR -CLASS="REPLACEABLE" ->debuglevel</VAR -> is an integer -from 0 to 10. The default value if this parameter is -not specified is zero.</P -><P ->The higher this value, the more detail will be -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 -information about operations carried out.</P -><P ->Levels above 1 will generate considerable -amounts of log data, and should only be used when -investigating a problem. Levels above 3 are designed for -use only by developers and generate HUGE amounts of log -data, most of which is extremely cryptic.</P -><P ->Note that specifying this parameter here will -override the <A -HREF="smb.conf.5.html#loglevel" -TARGET="_top" ->log -level</A -> parameter in the <A -HREF="smb.conf.5.html" -TARGET="_top" -><TT -CLASS="FILENAME" ->smb.conf(5)</TT -></A -> file.</P -></DD -><DT ->-l|--logfile=logbasename</DT -><DD -><P ->File name for log/debug files. The extension -<CODE -CLASS="CONSTANT" ->".client"</CODE -> will be appended. The log file is -never removed by the client.</P -></DD -><DT ->-h|--help</DT -><DD -><P ->Print a summary of command line options.</P +>Sets the debuglevel to an integer between + 0 and 100. 0 is for no debugging and 100 is for reams and + reams. To submit a bug report to the Samba Team, use debug + level 100 (see BUGS.txt). </P ></DD ><DT >-i</DT @@ -369,16 +302,26 @@ CLASS="COMMAND" as 2 threads. The first will answer all requests from the cache, thus making responses to clients faster. The other will update the cache for the query that the first has just responded. - Advantage of this is that responses stay accurate and are faster. + Advantage of this is that responses are accurate and fast. </P ></DD +><DT +>-s|--conf=smb.conf</DT +><DD +><P +>Specifies the location of the all-important + <TT +CLASS="FILENAME" +>smb.conf</TT +> file. </P +></DD ></DL ></DIV ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN126" +NAME="AEN103" ></A ><H2 >NAME AND ID RESOLUTION</H2 @@ -409,7 +352,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN132" +NAME="AEN109" ></A ><H2 >CONFIGURATION</H2 @@ -418,12 +361,10 @@ NAME="AEN132" 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 @@ -434,9 +375,11 @@ CLASS="REFENTRYTITLE" ><A HREF="smb.conf.5.html#WINBINDSEPARATOR" TARGET="_top" -> <VAR +> <TT CLASS="PARAMETER" ->winbind separator</VAR +><I +>winbind separator</I +></TT ></A ></P ></LI @@ -445,9 +388,11 @@ CLASS="PARAMETER" ><A HREF="smb.conf.5.html#WINBINDUID" TARGET="_top" -> <VAR +> <TT CLASS="PARAMETER" ->winbind uid</VAR +><I +>winbind uid</I +></TT ></A ></P ></LI @@ -456,9 +401,11 @@ CLASS="PARAMETER" ><A HREF="smb.conf.5.html#WINBINDGID" TARGET="_top" -> <VAR +> <TT CLASS="PARAMETER" ->winbind gid</VAR +><I +>winbind gid</I +></TT ></A ></P ></LI @@ -467,9 +414,11 @@ CLASS="PARAMETER" ><A HREF="smb.conf.5.html#WINBINDCACHETIME" TARGET="_top" -> <VAR +> <TT CLASS="PARAMETER" ->winbind cache time</VAR +><I +>winbind cache time</I +></TT ></A ></P ></LI @@ -478,9 +427,11 @@ CLASS="PARAMETER" ><A HREF="smb.conf.5.html#WINBINDENUMUSERS" TARGET="_top" -> <VAR +> <TT CLASS="PARAMETER" ->winbind enum users</VAR +><I +>winbind enum users</I +></TT ></A ></P ></LI @@ -489,9 +440,11 @@ CLASS="PARAMETER" ><A HREF="smb.conf.5.html#WINBINDENUMGROUPS" TARGET="_top" -> <VAR +> <TT CLASS="PARAMETER" ->winbind enum groups</VAR +><I +>winbind enum groups</I +></TT ></A ></P ></LI @@ -500,9 +453,11 @@ CLASS="PARAMETER" ><A HREF="smb.conf.5.html#TEMPLATEHOMEDIR" TARGET="_top" -> <VAR +> <TT CLASS="PARAMETER" ->template homedir</VAR +><I +>template homedir</I +></TT ></A ></P ></LI @@ -511,9 +466,11 @@ CLASS="PARAMETER" ><A HREF="smb.conf.5.html#TEMPLATESHELL" TARGET="_top" -> <VAR +> <TT CLASS="PARAMETER" ->template shell</VAR +><I +>template shell</I +></TT ></A ></P ></LI @@ -522,9 +479,11 @@ CLASS="PARAMETER" ><A HREF="smb.conf.5.html#WINBINDUSEDEFAULTDOMAIN" TARGET="_top" -> <VAR +> <TT CLASS="PARAMETER" ->winbind use default domain</VAR +><I +>winbind use default domain</I +></TT ></A ></P ></LI @@ -533,7 +492,7 @@ CLASS="PARAMETER" ><DIV CLASS="REFSECT1" ><A -NAME="AEN176" +NAME="AEN151" ></A ><H2 >EXAMPLE SETUP</H2 @@ -546,35 +505,64 @@ NAME="AEN176" 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 <VAR +> replace the + <TT CLASS="PARAMETER" -> auth</VAR -> lines with something like this: -<PRE +><I +>auth</I +></TT +> 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 <VAR +>Note in particular the use of the <TT CLASS="PARAMETER" ->sufficient - </VAR -> keyword and the <VAR +><I +>sufficient</I +></TT +> + keyword and the <TT CLASS="PARAMETER" ->use_first_pass</VAR +><I +>use_first_pass</I +></TT > keyword. </P ><P >Now replace the account lines with this: </P @@ -588,20 +576,24 @@ CLASS="COMMAND" >The next step is to join the domain. To do that use the <B CLASS="COMMAND" ->net</B +>smbpasswd</B > program like this: </P ><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 <VAR +>The username after the <TT CLASS="PARAMETER" ->-U</VAR +><I +>-U</I +></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" @@ -612,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 @@ -632,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 = + @@ -651,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 @@ -670,7 +670,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN214" +NAME="AEN190" ></A ><H2 >NOTES</H2 @@ -681,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" @@ -694,14 +691,25 @@ 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 > to become aware of new trust relationships between servers, it must be sent a SIGHUP signal. </P ><P +>Client processes resolving names through the <B +CLASS="COMMAND" +>winbindd</B +> + nsswitch module read an environment variable named <TT +CLASS="ENVAR" +> $WINBINDD_DOMAIN</TT +>. If this variable contains a comma separated + list of Windows NT domain names, then winbindd will only resolve users + and groups within those Windows NT domains. </P +><P >PAM is really easy to misconfigure. Make sure you know what you are doing when modifying PAM configuration files. It is possible to set up PAM such that you can no longer log into your system. </P @@ -720,7 +728,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN229" +NAME="AEN206" ></A ><H2 >SIGNALS</H2 @@ -739,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 @@ -774,7 +779,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN248" +NAME="AEN223" ></A ><H2 >FILES</H2 @@ -813,34 +818,6 @@ CLASS="FILENAME" root. </P ></DD ><DT ->$LOCKDIR/winbindd_privilaged/pipe</DT -><DD -><P ->The UNIX pipe over which 'privilaged' clients - communicate with the <B -CLASS="COMMAND" ->winbindd</B -> program. For security - reasons, access to some winbindd functions - like those needed by - the <B -CLASS="COMMAND" ->ntlm_auth</B -> utility - is restricted. By default, - only users in the 'root' group will get this access, however the administrator - may change the group permissions on $LOCKDIR/winbindd_privilaged to allow - programs like 'squid' to use ntlm_auth. - Note that the winbind client will only attempt to connect to the winbindd daemon - if both the <TT -CLASS="FILENAME" ->$LOCKDIR/winbindd_privilaged</TT -> directory - and <TT -CLASS="FILENAME" ->$LOCKDIR/winbindd_privilaged/pipe</TT -> file are owned by - root. </P -></DD -><DT >/lib/libnss_winbind.so.X</DT ><DD ><P @@ -853,9 +830,11 @@ CLASS="FILENAME" ><P >Storage for the Windows NT rid to UNIX user/group id mapping. The lock directory is specified when Samba is initially - compiled using the <VAR + compiled using the <TT CLASS="PARAMETER" ->--with-lockdir</VAR +><I +>--with-lockdir</I +></TT > option. This directory is by default <TT CLASS="FILENAME" @@ -876,7 +855,7 @@ CLASS="FILENAME" ><DIV CLASS="REFSECT1" ><A -NAME="AEN285" +NAME="AEN252" ></A ><H2 >VERSION</H2 @@ -887,7 +866,7 @@ NAME="AEN285" ><DIV CLASS="REFSECT1" ><A -NAME="AEN288" +NAME="AEN255" ></A ><H2 >SEE ALSO</H2 @@ -895,30 +874,27 @@ NAME="AEN288" ><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="AEN301" +NAME="AEN262" ></A ><H2 >AUTHOR</H2 @@ -934,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 |