diff options
| author | Jelmer Vernooij <jelmer@samba.org> | 2003-03-18 16:48:14 +0000 |
|---|---|---|
| committer | Jelmer Vernooij <jelmer@samba.org> | 2003-03-18 16:48:14 +0000 |
| commit | 20967627378194121bc48bf387838b8bd7682478 (patch) | |
| tree | 7f9c31e2688d9c9ccb2d1ab385cad16b290e92d5 /docs/htmldocs | |
| parent | 404d5ba54d009f0d86fa28a34ae9f6761443e58c (diff) | |
| download | samba-20967627378194121bc48bf387838b8bd7682478.tar.gz samba-20967627378194121bc48bf387838b8bd7682478.tar.bz2 samba-20967627378194121bc48bf387838b8bd7682478.zip | |
Regenerate
(This used to be commit 25db62e3101dbcae8e9daee3cb16430297afa223)
Diffstat (limited to 'docs/htmldocs')
71 files changed, 8676 insertions, 15035 deletions
diff --git a/docs/htmldocs/Samba-Developers-Guide.html b/docs/htmldocs/Samba-Developers-Guide.html index 5d9702e49e..22cbcec3ee 100644 --- a/docs/htmldocs/Samba-Developers-Guide.html +++ b/docs/htmldocs/Samba-Developers-Guide.html @@ -5,7 +5,7 @@ >SAMBA Developers Guide</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"></HEAD +CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD ><BODY CLASS="BOOK" BGCOLOR="#FFFFFF" @@ -24,8 +24,8 @@ CLASS="TITLEPAGE" CLASS="TITLE" ><A NAME="SAMBA-DEVELOPERS-GUIDE" -></A ->SAMBA Developers Guide</H1 +>SAMBA Developers Guide</A +></H1 ><H3 CLASS="AUTHOR" ><A @@ -848,8 +848,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN24" -></A ->1.1. NETBIOS</H2 +>1.1. NETBIOS</A +></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 @@ -904,8 +904,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN35" -></A ->1.2. BROADCAST NetBIOS</H2 +>1.2. BROADCAST NetBIOS</A +></H2 ><P > Clients can claim names, and therefore offer services on successfully claimed @@ -927,14 +927,14 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN39" -></A ->1.3. NBNS NetBIOS</H2 +>1.3. NBNS NetBIOS</A +></H2 ><P >rfc1001.txt describes, amongst other things, the implementation and use of, a 'NetBIOS Name Service'. NT/AS offers 'Windows Internet Name Service' which is fully rfc1001/2 compliant, but has had to take specific action with certain NetBIOS names in order to make it useful. (for example, it -deals with the registration of <1c> <1d> <1e> names all in different ways. +deals with the registration of <1c> <1d> <1e> names all in different ways. I recommend the reading of the Microsoft WINS Server Help files for full details).</P ><P @@ -987,8 +987,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN54" -></A ->2.1. Introduction</H2 +>2.1. Introduction</A +></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 @@ -1022,8 +1022,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN65" -></A ->2.2. Multithreading and Samba</H2 +>2.2. Multithreading and Samba</A +></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 @@ -1048,8 +1048,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN70" -></A ->2.3. Threading smbd</H2 +>2.3. Threading smbd</A +></H2 ><P >A few problems that would arise from a threaded smbd are:</P ><P @@ -1099,8 +1099,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN86" -></A ->2.4. Threading nmbd</H2 +>2.4. Threading nmbd</A +></H2 ><P >This would be ideal, but gets sunk by portability requirements.</P ><P @@ -1135,8 +1135,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN92" -></A ->2.5. nbmd Design</H2 +>2.5. nbmd Design</A +></H2 ><P >Originally Andrew used recursion to simulate a multi-threaded environment, which use the stack enormously and made for really @@ -1173,22 +1173,22 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN103" -></A ->3.1. New Output Syntax</H2 +>3.1. New Output Syntax</A +></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 @@ -1258,8 +1258,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN128" -></A ->3.2. The DEBUG() Macro</H2 +>3.2. The DEBUG() Macro</A +></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 @@ -1338,8 +1338,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN151" -></A ->3.3. The DEBUGADD() Macro</H2 +>3.3. The DEBUGADD() Macro</A +></H2 ><P >In addition to the kludgey solution to the broken line problem described above, there is a clean solution. The DEBUGADD() macro never @@ -1369,8 +1369,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN159" -></A ->3.4. The DEBUGLVL() Macro</H2 +>3.4. The DEBUGLVL() Macro</A +></H2 ><P >One of the problems with the DEBUG() macro was that DEBUG() lines tended to get a bit long. Consider this example from @@ -1437,16 +1437,16 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN179" -></A ->3.5. New Functions</H2 +>3.5. New Functions</A +></H2 ><DIV CLASS="SECT2" ><H3 CLASS="SECT2" ><A NAME="AEN181" -></A ->3.5.1. dbgtext()</H3 +>3.5.1. dbgtext()</A +></H3 ><P >This function prints debug message text to the debug file (and possibly to syslog) via the format buffer. The function uses a @@ -1463,8 +1463,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN184" -></A ->3.5.2. dbghdr()</H3 +>3.5.2. dbghdr()</A +></H3 ><P >This is the function that writes a debug message header. Headers are not processed via the format buffer. Also note that @@ -1480,8 +1480,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN188" -></A ->3.5.3. format_debug_text()</H3 +>3.5.3. format_debug_text()</A +></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 @@ -1726,8 +1726,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN284" -></A ->5.1. Character Handling</H2 +>5.1. Character Handling</A +></H2 ><P >This section describes character set handling in Samba, as implemented in Samba 3.0 and above</P @@ -1745,8 +1745,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN288" -></A ->5.2. The new functions</H2 +>5.2. The new functions</A +></H2 ><P >The new system works like this:</P ><P @@ -1856,8 +1856,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN317" -></A ->5.3. Macros in byteorder.h</H2 +>5.3. Macros in byteorder.h</A +></H2 ><P >This section describes the macros defined in byteorder.h. These macros are used extensively in the Samba code.</P @@ -1867,8 +1867,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN320" -></A ->5.3.1. CVAL(buf,pos)</H3 +>5.3.1. CVAL(buf,pos)</A +></H3 ><P >returns the byte at offset pos within buffer buf as an unsigned character.</P ></DIV @@ -1878,8 +1878,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN323" -></A ->5.3.2. PVAL(buf,pos)</H3 +>5.3.2. PVAL(buf,pos)</A +></H3 ><P >returns the value of CVAL(buf,pos) cast to type unsigned integer.</P ></DIV @@ -1889,8 +1889,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN326" -></A ->5.3.3. SCVAL(buf,pos,val)</H3 +>5.3.3. SCVAL(buf,pos,val)</A +></H3 ><P >sets the byte at offset pos within buffer buf to value val.</P ></DIV @@ -1900,8 +1900,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN329" -></A ->5.3.4. SVAL(buf,pos)</H3 +>5.3.4. SVAL(buf,pos)</A +></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 @@ -1913,8 +1913,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN332" -></A ->5.3.5. IVAL(buf,pos)</H3 +>5.3.5. IVAL(buf,pos)</A +></H3 ><P >returns the value of the unsigned 32 bit little-endian integer at offset pos within buffer buf.</P @@ -1925,8 +1925,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN335" -></A ->5.3.6. SVALS(buf,pos)</H3 +>5.3.6. SVALS(buf,pos)</A +></H3 ><P >returns the value of the signed short (16 bit) little-endian integer at offset pos within buffer buf.</P @@ -1937,8 +1937,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN338" -></A ->5.3.7. IVALS(buf,pos)</H3 +>5.3.7. IVALS(buf,pos)</A +></H3 ><P >returns the value of the signed 32 bit little-endian integer at offset pos within buffer buf.</P @@ -1949,8 +1949,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN341" -></A ->5.3.8. SSVAL(buf,pos,val)</H3 +>5.3.8. SSVAL(buf,pos,val)</A +></H3 ><P >sets the unsigned short (16 bit) little-endian integer at offset pos within buffer buf to value val.</P @@ -1961,8 +1961,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN344" -></A ->5.3.9. SIVAL(buf,pos,val)</H3 +>5.3.9. SIVAL(buf,pos,val)</A +></H3 ><P >sets the unsigned 32 bit little-endian integer at offset pos within buffer buf to the value val.</P @@ -1973,8 +1973,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN347" -></A ->5.3.10. SSVALS(buf,pos,val)</H3 +>5.3.10. SSVALS(buf,pos,val)</A +></H3 ><P >sets the short (16 bit) signed little-endian integer at offset pos within buffer buf to the value val.</P @@ -1985,8 +1985,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN350" -></A ->5.3.11. SIVALS(buf,pos,val)</H3 +>5.3.11. SIVALS(buf,pos,val)</A +></H3 ><P >sets the signed 32 bit little-endian integer at offset pos withing buffer buf to the value val.</P @@ -1997,8 +1997,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN353" -></A ->5.3.12. RSVAL(buf,pos)</H3 +>5.3.12. RSVAL(buf,pos)</A +></H3 ><P >returns the value of the unsigned short (16 bit) big-endian integer at offset pos within buffer buf.</P @@ -2009,8 +2009,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN356" -></A ->5.3.13. RIVAL(buf,pos)</H3 +>5.3.13. RIVAL(buf,pos)</A +></H3 ><P >returns the value of the unsigned 32 bit big-endian integer at offset pos within buffer buf.</P @@ -2021,8 +2021,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN359" -></A ->5.3.14. RSSVAL(buf,pos,val)</H3 +>5.3.14. RSSVAL(buf,pos,val)</A +></H3 ><P >sets the value of the unsigned short (16 bit) big-endian integer at offset pos within buffer buf to value val. @@ -2034,8 +2034,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN362" -></A ->5.3.15. RSIVAL(buf,pos,val)</H3 +>5.3.15. RSIVAL(buf,pos,val)</A +></H3 ><P >sets the value of the unsigned 32 bit big-endian integer at offset pos within buffer buf to value val.</P @@ -2047,8 +2047,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN365" -></A ->5.4. LAN Manager Samba API</H2 +>5.4. LAN Manager Samba API</A +></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 @@ -2069,8 +2069,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN371" -></A ->5.4.1. Parameters</H3 +>5.4.1. Parameters</A +></H3 ><P >The parameters are as follows:</P ><P @@ -2163,8 +2163,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN406" -></A ->5.4.2. Return value</H3 +>5.4.2. Return value</A +></H3 ><P >The returned parameters (pointed to by rparam), in their order of appearance are:</P @@ -2216,8 +2216,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN420" -></A ->5.5. Code character table</H2 +>5.5. Code character table</A +></H2 ><P >Certain data structures are described by means of ASCIIz strings containing code characters. These are the code characters:</P @@ -2281,8 +2281,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN451" -></A ->6.1. Lexical Analysis</H2 +>6.1. Lexical Analysis</A +></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 @@ -2340,8 +2340,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN472" -></A ->6.1.1. Handling of Whitespace</H3 +>6.1.1. Handling of Whitespace</A +></H3 ><P >Whitespace is defined as all characters recognized by the isspace() function (see ctype(3C)) except for the newline character ('\n') @@ -2377,8 +2377,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN484" -></A ->6.1.2. Handling of Line Continuation</H3 +>6.1.2. Handling of Line Continuation</A +></H3 ><P >Long section header and parameter lines may be extended across multiple lines by use of the backslash character ('\\'). Line @@ -2417,8 +2417,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN495" -></A ->6.1.3. Line Continuation Quirks</H3 +>6.1.3. Line Continuation Quirks</A +></H3 ><P >Note the following example:</P ><P @@ -2477,17 +2477,17 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN515" -></A ->6.2. Syntax</H2 +>6.2. Syntax</A +></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 @@ -2524,8 +2524,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN530" -></A ->6.2.1. About params.c</H3 +>6.2.1. About params.c</A +></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 @@ -2547,12 +2547,12 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN540" -></A ->7.1. Introduction</H2 +>7.1. Introduction</A +></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 -them. They may help people who are looking at unix<->PC +them. They may help people who are looking at unix<->PC interoperability.</P ><P >It was written to help out a person who was writing a paper on unix to @@ -2564,8 +2564,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN544" -></A ->7.2. Usernames</H2 +>7.2. Usernames</A +></H2 ><P >The SMB protocol has only a loose username concept. Early SMB protocols (such as CORE and COREPLUS) have no username concept at @@ -2610,8 +2610,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN552" -></A ->7.3. File Ownership</H2 +>7.3. File Ownership</A +></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 @@ -2637,8 +2637,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN557" -></A ->7.4. Passwords</H2 +>7.4. Passwords</A +></H2 ><P >Many SMB clients uppercase passwords before sending them. I have no idea why they do this. Interestingly WfWg uppercases the password only @@ -2668,8 +2668,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN563" -></A ->7.5. Locking</H2 +>7.5. Locking</A +></H2 ><P >Since samba 2.2, samba supports other types of locking as well. This section is outdated.</P @@ -2708,8 +2708,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN571" -></A ->7.6. Deny Modes</H2 +>7.6. Deny Modes</A +></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, @@ -2731,8 +2731,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN575" -></A ->7.7. Trapdoor UIDs</H2 +>7.7. Trapdoor UIDs</A +></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 @@ -2750,8 +2750,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN579" -></A ->7.8. Port numbers</H2 +>7.8. Port numbers</A +></H2 ><P >There is a convention that clients on sockets use high "unprivilaged" port numbers (>1000) and connect to servers on low "privilaged" port @@ -2782,8 +2782,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN584" -></A ->7.9. Protocol Complexity</H2 +>7.9. Protocol Complexity</A +></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, @@ -2900,14 +2900,14 @@ example, if I'm using a csh style shell:</P ><P ><B CLASS="COMMAND" ->strace -f -p 3872 >& strace.out</B +>strace -f -p 3872 >& strace.out</B ></P ><P >or with a sh style shell:</P ><P ><B CLASS="COMMAND" ->strace -f -p 3872 > strace.out 2>&1</B +>strace -f -p 3872 > strace.out 2>&1</B ></P ><P >Note the "-f" option. This is only available on some systems, and @@ -2963,8 +2963,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN652" -></A ->9.1. Introduction</H2 +>9.1. Introduction</A +></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 @@ -3087,8 +3087,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN688" -></A ->9.1.1. Sources</H3 +>9.1.1. Sources</A +></H3 ><P ></P ><TABLE @@ -3121,8 +3121,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN695" -></A ->9.1.2. Credits</H3 +>9.1.2. Credits</A +></H3 ><P ></P ><TABLE @@ -3156,16 +3156,16 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN702" -></A ->9.2. Notes and Structures</H2 +>9.2. Notes and Structures</A +></H2 ><DIV CLASS="SECT2" ><H3 CLASS="SECT2" ><A NAME="AEN704" -></A ->9.2.1. Notes</H3 +>9.2.1. Notes</A +></H3 ><P ></P ><OL @@ -3216,16 +3216,16 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN717" -></A ->9.2.2. Enumerations</H3 +>9.2.2. Enumerations</A +></H3 ><DIV CLASS="SECT3" ><H4 CLASS="SECT3" ><A NAME="AEN719" -></A ->9.2.2.1. MSRPC Header type</H4 +>9.2.2.1. MSRPC Header type</A +></H4 ><P >command number in the msrpc packet header</P ><P @@ -3266,8 +3266,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN739" -></A ->9.2.2.2. MSRPC Packet info</H4 +>9.2.2.2. MSRPC Packet info</A +></H4 ><P >The meaning of these flags is undocumented</P ><P @@ -3333,16 +3333,16 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN775" -></A ->9.2.3. Structures</H3 +>9.2.3. Structures</A +></H3 ><DIV CLASS="SECT3" ><H4 CLASS="SECT3" ><A NAME="AEN777" -></A ->9.2.3.1. VOID *</H4 +>9.2.3.1. VOID *</A +></H4 ><P >sizeof VOID* is 32 bits.</P ></DIV @@ -3352,8 +3352,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN780" -></A ->9.2.3.2. char</H4 +>9.2.3.2. char</A +></H4 ><P >sizeof char is 8 bits.</P ></DIV @@ -3363,8 +3363,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN783" -></A ->9.2.3.3. UTIME</H4 +>9.2.3.3. UTIME</A +></H4 ><P >UTIME is 32 bits, indicating time in seconds since 01jan1970. documented in cifs6.txt (section 3.5 page, page 30).</P ></DIV @@ -3374,8 +3374,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN786" -></A ->9.2.3.4. NTTIME</H4 +>9.2.3.4. NTTIME</A +></H4 ><P >NTTIME is 64 bits. documented in cifs6.txt (section 3.5 page, page 30).</P ></DIV @@ -3385,8 +3385,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN789" -></A ->9.2.3.5. DOM_SID (domain SID structure)</H4 +>9.2.3.5. DOM_SID (domain SID structure)</A +></H4 ><P ></P ><DIV @@ -3439,8 +3439,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN814" -></A ->9.2.3.6. STR (string)</H4 +>9.2.3.6. STR (string)</A +></H4 ><P >STR (string) is a char[] : a null-terminated string of ascii characters.</P ></DIV @@ -3450,8 +3450,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN817" -></A ->9.2.3.7. UNIHDR (unicode string header)</H4 +>9.2.3.7. UNIHDR (unicode string header)</A +></H4 ><P ></P ><DIV @@ -3484,8 +3484,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN832" -></A ->9.2.3.8. UNIHDR2 (unicode string header plus buffer pointer)</H4 +>9.2.3.8. UNIHDR2 (unicode string header plus buffer pointer)</A +></H4 ><P ></P ><DIV @@ -3512,8 +3512,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN843" -></A ->9.2.3.9. UNISTR (unicode string)</H4 +>9.2.3.9. UNISTR (unicode string)</A +></H4 ><P ></P ><DIV @@ -3534,8 +3534,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN850" -></A ->9.2.3.10. NAME (length-indicated unicode string)</H4 +>9.2.3.10. NAME (length-indicated unicode string)</A +></H4 ><P ></P ><DIV @@ -3562,8 +3562,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN861" -></A ->9.2.3.11. UNISTR2 (aligned unicode string)</H4 +>9.2.3.11. UNISTR2 (aligned unicode string)</A +></H4 ><P ></P ><DIV @@ -3608,8 +3608,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN884" -></A ->9.2.3.12. OBJ_ATTR (object attributes)</H4 +>9.2.3.12. OBJ_ATTR (object attributes)</A +></H4 ><P ></P ><DIV @@ -3660,8 +3660,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN911" -></A ->9.2.3.13. POL_HND (LSA policy handle)</H4 +>9.2.3.13. POL_HND (LSA policy handle)</A +></H4 ><P ></P ><DIV @@ -3682,8 +3682,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN918" -></A ->9.2.3.14. DOM_SID2 (domain SID structure, SIDS stored in unicode)</H4 +>9.2.3.14. DOM_SID2 (domain SID structure, SIDS stored in unicode)</A +></H4 ><P ></P ><DIV @@ -3738,8 +3738,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN941" -></A ->9.2.3.15. DOM_RID (domain RID structure)</H4 +>9.2.3.15. DOM_RID (domain RID structure)</A +></H4 ><P ></P ><DIV @@ -3778,8 +3778,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN960" -></A ->9.2.3.16. LOG_INFO (server, account, client structure)</H4 +>9.2.3.16. LOG_INFO (server, account, client structure)</A +></H4 ><P ><SPAN CLASS="emphasis" @@ -3840,8 +3840,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN987" -></A ->9.2.3.17. CLNT_SRV (server, client names structure)</H4 +>9.2.3.17. CLNT_SRV (server, client names structure)</A +></H4 ><P ><SPAN CLASS="emphasis" @@ -3888,8 +3888,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN1008" -></A ->9.2.3.18. CREDS (credentials + time stamp)</H4 +>9.2.3.18. CREDS (credentials + time stamp)</A +></H4 ><P ></P ><DIV @@ -3916,8 +3916,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN1019" -></A ->9.2.3.19. CLNT_INFO2 (server, client structure, client credentials)</H4 +>9.2.3.19. CLNT_INFO2 (server, client structure, client credentials)</A +></H4 ><P ><SPAN CLASS="emphasis" @@ -3965,8 +3965,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN1040" -></A ->9.2.3.20. CLNT_INFO (server, account, client structure, client credentials)</H4 +>9.2.3.20. CLNT_INFO (server, account, client structure, client credentials)</A +></H4 ><P ><SPAN CLASS="emphasis" @@ -4001,8 +4001,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN1053" -></A ->9.2.3.21. ID_INFO_1 (id info structure, auth level 1)</H4 +>9.2.3.21. ID_INFO_1 (id info structure, auth level 1)</A +></H4 ><P ></P ><DIV @@ -4083,8 +4083,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN1100" -></A ->9.2.3.22. SAM_INFO (sam logon/logoff id info structure)</H4 +>9.2.3.22. SAM_INFO (sam logon/logoff id info structure)</A +></H4 ><P ><SPAN CLASS="emphasis" @@ -4146,8 +4146,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN1127" -></A ->9.2.3.23. GID (group id info)</H4 +>9.2.3.23. GID (group id info)</A +></H4 ><P ></P ><DIV @@ -4174,8 +4174,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN1138" -></A ->9.2.3.24. DOM_REF (domain reference info)</H4 +>9.2.3.24. DOM_REF (domain reference info)</A +></H4 ><P ></P ><DIV @@ -4244,8 +4244,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN1177" -></A ->9.2.3.25. DOM_INFO (domain info, levels 3 and 5 are the same))</H4 +>9.2.3.25. DOM_INFO (domain info, levels 3 and 5 are the same))</A +></H4 ><P ></P ><DIV @@ -4302,8 +4302,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN1208" -></A ->9.2.3.26. USER_INFO (user logon info)</H4 +>9.2.3.26. USER_INFO (user logon info)</A +></H4 ><P ><SPAN CLASS="emphasis" @@ -4554,8 +4554,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN1365" -></A ->9.2.3.27. SH_INFO_1_PTR (pointers to level 1 share info strings)</H4 +>9.2.3.27. SH_INFO_1_PTR (pointers to level 1 share info strings)</A +></H4 ><P ><SPAN CLASS="emphasis" @@ -4625,8 +4625,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN1388" -></A ->9.2.3.28. SH_INFO_1_STR (level 1 share info strings)</H4 +>9.2.3.28. SH_INFO_1_STR (level 1 share info strings)</A +></H4 ><P ></P ><DIV @@ -4653,8 +4653,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN1399" -></A ->9.2.3.29. SHARE_INFO_1_CTR</H4 +>9.2.3.29. SHARE_INFO_1_CTR</A +></H4 ><P >share container with 0 entries:</P ><P @@ -4740,8 +4740,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN1445" -></A ->9.2.3.30. SERVER_INFO_101</H4 +>9.2.3.30. SERVER_INFO_101</A +></H4 ><P ><SPAN CLASS="emphasis" @@ -4953,8 +4953,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN1571" -></A ->9.3. MSRPC over Transact Named Pipe</H2 +>9.3. MSRPC over Transact Named Pipe</A +></H2 ><P >For details on the SMB Transact Named Pipe, see cifs6.txt</P ><DIV @@ -4963,8 +4963,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN1574" -></A ->9.3.1. MSRPC Pipes</H3 +>9.3.1. MSRPC Pipes</A +></H3 ><P >The MSRPC is conducted over an SMB Transact Pipe with a name of <TT @@ -5023,8 +5023,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN1588" -></A ->9.3.2. Header</H3 +>9.3.2. Header</A +></H3 ><P >[section to be rewritten, following receipt of work by Duncan Stansfield]</P ><P @@ -5194,8 +5194,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN1649" -></A ->9.3.2.1. RPC_Packet for request, response, bind and bind acknowledgement</H4 +>9.3.2.1. RPC_Packet for request, response, bind and bind acknowledgement</A +></H4 ><P ></P ><DIV @@ -5264,8 +5264,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN1688" -></A ->9.3.2.2. Interface identification</H4 +>9.3.2.2. Interface identification</A +></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 @@ -5281,8 +5281,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN1693" -></A ->9.3.2.3. RPC_Iface RW</H4 +>9.3.2.3. RPC_Iface RW</A +></H4 ><P ></P ><DIV @@ -5309,8 +5309,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN1704" -></A ->9.3.2.4. RPC_ReqBind RW</H4 +>9.3.2.4. RPC_ReqBind RW</A +></H4 ><P >the remainder of the packet after the header if "type" was Bind in the response header, "type" should be BindAck</P ><P @@ -5381,8 +5381,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN1744" -></A ->9.3.2.5. RPC_Address RW</H4 +>9.3.2.5. RPC_Address RW</A +></H4 ><P ></P ><DIV @@ -5409,8 +5409,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN1755" -></A ->9.3.2.6. RPC_ResBind RW</H4 +>9.3.2.6. RPC_ResBind RW</A +></H4 ><P >the response to place after the header in the reply packet</P ><P @@ -5487,8 +5487,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN1799" -></A ->9.3.2.7. RPC_ReqNorm RW</H4 +>9.3.2.7. RPC_ReqNorm RW</A +></H4 ><P >the remainder of the packet after the header for every other other request</P ><P @@ -5529,8 +5529,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN1819" -></A ->9.3.2.8. RPC_ResNorm RW</H4 +>9.3.2.8. RPC_ResNorm RW</A +></H4 ><P ></P ><DIV @@ -5576,8 +5576,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN1842" -></A ->9.3.3. Tail</H3 +>9.3.3. Tail</A +></H3 ><P >The end of each of the NTLSA and NETLOGON named pipes ends with:</P ><P @@ -5606,8 +5606,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN1854" -></A ->9.3.4. RPC Bind / Bind Ack</H3 +>9.3.4. RPC Bind / Bind Ack</A +></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 @@ -5736,8 +5736,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN1898" -></A ->9.3.5. NTLSA Transact Named Pipe</H3 +>9.3.5. NTLSA Transact Named Pipe</A +></H3 ><P >The sequence of actions taken on this pipe are:</P ><P @@ -5835,8 +5835,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN1939" -></A ->9.3.6. LSA Open Policy</H3 +>9.3.6. LSA Open Policy</A +></H3 ><P ><SPAN CLASS="emphasis" @@ -5851,8 +5851,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN1943" -></A ->9.3.6.1. Request</H4 +>9.3.6.1. Request</A +></H4 ><P ></P ><DIV @@ -5891,8 +5891,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN1962" -></A ->9.3.6.2. Response</H4 +>9.3.6.2. Response</A +></H4 ><P ></P ><DIV @@ -5920,8 +5920,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN1973" -></A ->9.3.7. LSA Query Info Policy</H3 +>9.3.7. LSA Query Info Policy</A +></H3 ><P ><SPAN CLASS="emphasis" @@ -5936,8 +5936,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN1977" -></A ->9.3.7.1. Request</H4 +>9.3.7.1. Request</A +></H4 ><P ></P ><DIV @@ -5964,8 +5964,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN1988" -></A ->9.3.7.2. Response</H4 +>9.3.7.2. Response</A +></H4 ><P ></P ><DIV @@ -6005,16 +6005,16 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN2001" -></A ->9.3.8. LSA Enumerate Trusted Domains</H3 +>9.3.8. LSA Enumerate Trusted Domains</A +></H3 ><DIV CLASS="SECT3" ><H4 CLASS="SECT3" ><A NAME="AEN2003" -></A ->9.3.8.1. Request</H4 +>9.3.8.1. Request</A +></H4 ><P >no extra data</P ></DIV @@ -6024,8 +6024,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN2006" -></A ->9.3.8.2. Response</H4 +>9.3.8.2. Response</A +></H4 ><P ></P ><DIV @@ -6065,16 +6065,16 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN2025" -></A ->9.3.9. LSA Open Secret</H3 +>9.3.9. LSA Open Secret</A +></H3 ><DIV CLASS="SECT3" ><H4 CLASS="SECT3" ><A NAME="AEN2027" -></A ->9.3.9.1. Request</H4 +>9.3.9.1. Request</A +></H4 ><P >no extra data</P ></DIV @@ -6084,8 +6084,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN2030" -></A ->9.3.9.2. Response</H4 +>9.3.9.2. Response</A +></H4 ><P ></P ><DIV @@ -6133,16 +6133,16 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN2054" -></A ->9.3.10. LSA Close</H3 +>9.3.10. LSA Close</A +></H3 ><DIV CLASS="SECT3" ><H4 CLASS="SECT3" ><A NAME="AEN2056" -></A ->9.3.10.1. Request</H4 +>9.3.10.1. Request</A +></H4 ><P ></P ><DIV @@ -6163,8 +6163,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN2063" -></A ->9.3.10.2. Response</H4 +>9.3.10.2. Response</A +></H4 ><P ></P ><DIV @@ -6188,8 +6188,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN2071" -></A ->9.3.11. LSA Lookup SIDS</H3 +>9.3.11. LSA Lookup SIDS</A +></H3 ><P ><SPAN CLASS="emphasis" @@ -6204,8 +6204,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN2075" -></A ->9.3.11.1. Request</H4 +>9.3.11.1. Request</A +></H4 ><P ></P ><DIV @@ -6256,8 +6256,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN2102" -></A ->9.3.11.2. Response</H4 +>9.3.11.2. Response</A +></H4 ><P ></P ><DIV @@ -6311,8 +6311,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN2130" -></A ->9.3.12. LSA Lookup Names</H3 +>9.3.12. LSA Lookup Names</A +></H3 ><P ><SPAN CLASS="emphasis" @@ -6327,8 +6327,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN2134" -></A ->9.3.12.1. Request</H4 +>9.3.12.1. Request</A +></H4 ><P ></P ><DIV @@ -6385,8 +6385,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN2165" -></A ->9.3.12.2. Response</H4 +>9.3.12.2. Response</A +></H4 ><P ></P ><DIV @@ -6441,8 +6441,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN2193" -></A ->9.4. NETLOGON rpc Transact Named Pipe</H2 +>9.4. NETLOGON rpc Transact Named Pipe</A +></H2 ><P >The sequence of actions taken on this pipe are:</P ><P @@ -6541,8 +6541,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN2232" -></A ->9.4.1. LSA Request Challenge</H3 +>9.4.1. LSA Request Challenge</A +></H3 ><P ><SPAN CLASS="emphasis" @@ -6573,8 +6573,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN2240" -></A ->9.4.1.1. Request</H4 +>9.4.1.1. Request</A +></H4 ><P ></P ><DIV @@ -6613,8 +6613,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN2259" -></A ->9.4.1.2. Response</H4 +>9.4.1.2. Response</A +></H4 ><P ></P ><DIV @@ -6638,8 +6638,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN2267" -></A ->9.4.2. LSA Authenticate 2</H3 +>9.4.2. LSA Authenticate 2</A +></H3 ><P ><SPAN CLASS="emphasis" @@ -6670,8 +6670,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN2275" -></A ->9.4.2.1. Request</H4 +>9.4.2.1. Request</A +></H4 ><P ></P ><DIV @@ -6710,8 +6710,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN2294" -></A ->9.4.2.2. Response</H4 +>9.4.2.2. Response</A +></H4 ><P ></P ><DIV @@ -6741,8 +6741,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN2306" -></A ->9.4.3. LSA Server Password Set</H3 +>9.4.3. LSA Server Password Set</A +></H3 ><P ><SPAN CLASS="emphasis" @@ -6781,8 +6781,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN2316" -></A ->9.4.3.1. Request</H4 +>9.4.3.1. Request</A +></H4 ><P ></P ><DIV @@ -6809,8 +6809,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN2327" -></A ->9.4.3.2. Response</H4 +>9.4.3.2. Response</A +></H4 ><P ></P ><DIV @@ -6834,8 +6834,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN2335" -></A ->9.4.4. LSA SAM Logon</H3 +>9.4.4. LSA SAM Logon</A +></H3 ><P ><SPAN CLASS="emphasis" @@ -6851,8 +6851,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN2339" -></A ->9.4.4.1. Request</H4 +>9.4.4.1. Request</A +></H4 ><P ></P ><DIV @@ -6873,8 +6873,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN2346" -></A ->9.4.4.2. Response</H4 +>9.4.4.2. Response</A +></H4 ><P ></P ><DIV @@ -6925,8 +6925,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN2359" -></A ->9.4.5. LSA SAM Logoff</H3 +>9.4.5. LSA SAM Logoff</A +></H3 ><P ><SPAN CLASS="emphasis" @@ -6942,8 +6942,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN2363" -></A ->9.4.5.1. Request</H4 +>9.4.5.1. Request</A +></H4 ><P ></P ><DIV @@ -6964,8 +6964,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN2370" -></A ->9.4.5.2. Response</H4 +>9.4.5.2. Response</A +></H4 ><P ></P ><DIV @@ -6996,15 +6996,15 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN2382" -></A ->9.5. \\MAILSLOT\NET\NTLOGON</H2 +>9.5. \\MAILSLOT\NET\NTLOGON</A +></H2 ><P ><SPAN CLASS="emphasis" ><I CLASS="EMPHASIS" >Note: mailslots will contain a response mailslot, to which the response - should be sent. the target NetBIOS name is REQUEST_NAME<20>, where + should be sent. the target NetBIOS name is REQUEST_NAME<20>, where REQUEST_NAME is the name of the machine that sent the request.</I ></SPAN ></P @@ -7014,8 +7014,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN2386" -></A ->9.5.1. Query for PDC</H3 +>9.5.1. Query for PDC</A +></H3 ><P ><SPAN CLASS="emphasis" @@ -7030,8 +7030,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN2390" -></A ->9.5.1.1. Request</H4 +>9.5.1.1. Request</A +></H4 ><P ></P ><DIV @@ -7094,8 +7094,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN2425" -></A ->9.5.1.2. Response</H4 +>9.5.1.2. Response</A +></H4 ><P ></P ><DIV @@ -7159,8 +7159,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN2460" -></A ->9.5.2. SAM Logon</H3 +>9.5.2. SAM Logon</A +></H3 ><P ><SPAN CLASS="emphasis" @@ -7191,8 +7191,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN2468" -></A ->9.5.2.1. Request</H4 +>9.5.2.1. Request</A +></H4 ><P ></P ><DIV @@ -7279,8 +7279,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN2519" -></A ->9.5.2.2. Response</H4 +>9.5.2.2. Response</A +></H4 ><P ></P ><DIV @@ -7339,8 +7339,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN2550" -></A ->9.6. SRVSVC Transact Named Pipe</H2 +>9.6. SRVSVC Transact Named Pipe</A +></H2 ><P >Defines for this pipe, identifying the query are:</P ><P @@ -7368,8 +7368,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN2562" -></A ->9.6.1. Net Share Enum</H3 +>9.6.1. Net Share Enum</A +></H3 ><P ><SPAN CLASS="emphasis" @@ -7392,8 +7392,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN2568" -></A ->9.6.1.1. Request</H4 +>9.6.1.1. Request</A +></H4 ><P ></P ><DIV @@ -7456,8 +7456,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN2603" -></A ->9.6.1.2. Response</H4 +>9.6.1.2. Response</A +></H4 ><P ></P ><DIV @@ -7499,8 +7499,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN2623" -></A ->9.6.2. Net Server Get Info</H3 +>9.6.2. Net Server Get Info</A +></H3 ><P ><SPAN CLASS="emphasis" @@ -7515,8 +7515,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN2627" -></A ->9.6.2.1. Request</H4 +>9.6.2.1. Request</A +></H4 ><P ></P ><DIV @@ -7543,8 +7543,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN2638" -></A ->9.6.2.2. Response</H4 +>9.6.2.2. Response</A +></H4 ><P ></P ><DIV @@ -7581,16 +7581,16 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN2654" -></A ->9.7. Cryptographic side of NT Domain Authentication</H2 +>9.7. Cryptographic side of NT Domain Authentication</A +></H2 ><DIV CLASS="SECT2" ><H3 CLASS="SECT2" ><A NAME="AEN2656" -></A ->9.7.1. Definitions</H3 +>9.7.1. Definitions</A +></H3 ><P ></P ><DIV @@ -7666,35 +7666,50 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN2699" -></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 +>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 ><P >On joining the domain the client will optionally attempt to change its password and the domain controller may refuse to update it depending on registry settings. This will also occur weekly afterwards.</P -><P ->C: Tc = Time(), Rc' = Cred(Ks,Rc+Tc) C->S ServerPasswordSet,Rc',Tc, -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 +><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 >User: U with password P wishes to login to the domain (incidental data such as workstation and domain omitted)</P -><P ->C: Tc = Time(), Rc' = Cred(Ks,Rc+Tc) C->S NetLogonSamLogon,Rc',Tc,U, -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 +><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 ></DIV ><DIV CLASS="SECT2" @@ -7702,8 +7717,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN2709" -></A ->9.7.3. Comments</H3 +>9.7.3. Comments</A +></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 @@ -7733,8 +7748,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN2716" -></A ->9.8. SIDs and RIDs</H2 +>9.8. SIDs and RIDs</A +></H2 ><P >SIDs and RIDs are well documented elsewhere.</P ><P @@ -7765,16 +7780,16 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN2724" -></A ->9.8.1. Well-known SIDs</H3 +>9.8.1. Well-known SIDs</A +></H3 ><DIV CLASS="SECT3" ><H4 CLASS="SECT3" ><A NAME="AEN2726" -></A ->9.8.1.1. Universal well-known SIDs</H4 +>9.8.1.1. Universal well-known SIDs</A +></H4 ><P ></P ><DIV @@ -7837,8 +7852,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN2761" -></A ->9.8.1.2. NT well-known SIDs</H4 +>9.8.1.2. NT well-known SIDs</A +></H4 ><P ></P ><DIV @@ -7926,8 +7941,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN2812" -></A ->9.8.2. Well-known RIDS</H3 +>9.8.2. Well-known RIDS</A +></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 @@ -7938,8 +7953,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN2815" -></A ->9.8.2.1. Well-known RID users</H4 +>9.8.2.1. Well-known RID users</A +></H4 ><P ><B >Groupname: </B @@ -7971,8 +7986,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN2829" -></A ->9.8.2.2. Well-known RID groups</H4 +>9.8.2.2. Well-known RID groups</A +></H4 ><P ><B >Groupname: </B @@ -8016,8 +8031,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="AEN2847" -></A ->9.8.2.3. Well-known RID aliases</H4 +>9.8.2.3. Well-known RID aliases</A +></H4 ><P ><B >Groupname: </B @@ -8143,8 +8158,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN2896" -></A ->10.1. Abstract</H2 +>10.1. Abstract</A +></H2 ><P >The purpose of this document is to provide some insight into Samba's printing functionality and also to describe the semantics @@ -8156,13 +8171,13 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN2899" -></A ->10.2. Printing Interface to Various Back ends</H2 +>10.2. Printing Interface to Various Back ends</A +></H2 ><P >Samba uses a table of function pointers to seven functions. The -function prototypes are defined in the <TT +function prototypes are defined in the <VAR CLASS="VARNAME" ->printif</TT +>printif</VAR > structure declared in <TT CLASS="FILENAME" @@ -8224,8 +8239,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN2925" -></A ->10.3. Print Queue TDB's</H2 +>10.3. Print Queue TDB's</A +></H2 ><P >Samba provides periodic caching of the output from the "lpq command" for performance reasons. This cache time is configurable in seconds. @@ -8274,7 +8289,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 @@ -8294,14 +8309,12 @@ 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 <TT + stored in <CODE CLASS="CONSTANT" ->LOCK/<TT +>LOCK/<VAR CLASS="REPLACEABLE" -><I ->printer_name</I -></TT -></TT +>printer_name</VAR +></CODE >. If so, then do not update the TDB.</P ></LI @@ -8373,8 +8386,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN2959" -></A ->10.4. ChangeID and Client Caching of Printer Information</H2 +>10.4. ChangeID and Client Caching of Printer Information</A +></H2 ><P >[To be filled in later]</P ></DIV @@ -8384,8 +8397,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN2962" -></A ->10.5. Windows NT/2K Printer Change Notify</H2 +>10.5. Windows NT/2K Printer Change Notify</A +></H2 ><P >When working with Windows NT+ clients, it is possible for a print server to use RPC to send asynchronous change notification @@ -8455,7 +8468,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 @@ -8533,9 +8546,9 @@ information</P ></LI ></UL ><P ->A <TT +>A <VAR CLASS="VARNAME" ->SPOOL_NOTIFY_INFO</TT +>SPOOL_NOTIFY_INFO</VAR > contains:</P ><P ></P @@ -8552,9 +8565,9 @@ in the SPOOL_NOTIFY_INFO_DATA array</P ></LI ></UL ><P ->The <TT +>The <VAR CLASS="VARNAME" ->SPOOL_NOTIFY_INFO_DATA</TT +>SPOOL_NOTIFY_INFO_DATA</VAR > entries contain:</P ><P ></P @@ -8610,8 +8623,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN3033" -></A ->11.1. WINS Failover</H2 +>11.1. WINS Failover</A +></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 @@ -8620,7 +8633,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 @@ -8637,7 +8650,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 @@ -8651,7 +8664,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 @@ -8678,8 +8691,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN3054" -></A ->12.1. Security in the 'new SAM'</H2 +>12.1. Security in the 'new SAM'</A +></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, @@ -8752,8 +8765,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN3071" -></A ->12.2. Standalone from UNIX</H2 +>12.2. Standalone from UNIX</A +></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' @@ -8771,8 +8784,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN3075" -></A ->12.3. Handles and Races in the new SAM</H2 +>12.3. Handles and Races in the new SAM</A +></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 @@ -8814,16 +8827,16 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN3086" -></A ->12.4. Layers</H2 +>12.4. Layers</A +></H2 ><DIV CLASS="SECT2" ><H3 CLASS="SECT2" ><A NAME="AEN3088" -></A ->12.4.1. Application</H3 +>12.4.1. Application</A +></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 @@ -8835,8 +8848,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN3091" -></A ->12.4.2. SAM Interface</H3 +>12.4.2. SAM Interface</A +></H3 ><P >This level 'owns' the various handle structures, the get/set routines on those structures and provides the public interface. The application @@ -8855,8 +8868,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN3095" -></A ->12.4.3. SAM Modules</H3 +>12.4.3. SAM Modules</A +></H3 ><P >These do not communicate with the application directly, only by setting values in the handles, and receiving requests from the interface. These @@ -8873,16 +8886,16 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN3098" -></A ->12.5. SAM Modules</H2 +>12.5. SAM Modules</A +></H2 ><DIV CLASS="SECT2" ><H3 CLASS="SECT2" ><A NAME="AEN3100" -></A ->12.5.1. Special Module: sam_passdb</H3 +>12.5.1. Special Module: sam_passdb</A +></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 @@ -8896,8 +8909,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN3103" -></A ->12.5.2. sam_ads</H3 +>12.5.2. sam_ads</A +></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 @@ -8918,8 +8931,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN3107" -></A ->12.6. Memory Management</H2 +>12.6. Memory Management</A +></H2 ><P > The 'new SAM' development effort also concerned itself with getting a @@ -8974,8 +8987,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN3121" -></A ->12.7. Testing</H2 +>12.7. Testing</A +></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 @@ -8994,9 +9007,9 @@ it particularly valuable.</P ><P >Example useage:</P ><P -><TT +><SAMP CLASS="PROMPT" ->$</TT +>$</SAMP > <B CLASS="COMMAND" >bin/samtest</B @@ -9032,8 +9045,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN3147" -></A ->13.1. Introduction</H2 +>13.1. Introduction</A +></H2 ><P >With the development of LanManager and Windows NT compatible password encryption for Samba, it is now able @@ -9051,8 +9064,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN3151" -></A ->13.2. How does it work?</H2 +>13.2. How does it work?</A +></H2 ><P >LanManager encryption is somewhat similar to UNIX password encryption. The server uses a file containing a @@ -9116,11 +9129,11 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN3162" -></A >13.3. <A NAME="SMBPASSWDFILEFORMAT" ></A ->>The smbpasswd file</H2 +>>The smbpasswd file</A +></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. @@ -9151,28 +9164,24 @@ CLASS="FILENAME" </TT > file use the following command:</P ><P -><TT +><SAMP CLASS="PROMPT" ->$ </TT -><TT +>$ </SAMP +><KBD CLASS="USERINPUT" -><B >cat /etc/passwd | mksmbpasswd.sh - > /usr/local/samba/private/smbpasswd</B -></TT + > /usr/local/samba/private/smbpasswd</KBD ></P ><P >If you are running on a system that uses NIS, use</P ><P -><TT +><SAMP CLASS="PROMPT" ->$ </TT -><TT +>$ </SAMP +><KBD CLASS="USERINPUT" -><B >ypcat passwd | mksmbpasswd.sh - > /usr/local/samba/private/smbpasswd</B -></TT + > /usr/local/samba/private/smbpasswd</KBD ></P ><P >The <B @@ -9212,37 +9221,27 @@ 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 <TT +>Although only the <VAR CLASS="REPLACEABLE" -><I ->username</I -></TT +>username</VAR >, - <TT + <VAR CLASS="REPLACEABLE" -><I ->uid</I -></TT ->, <TT +>uid</VAR +>, <VAR CLASS="REPLACEABLE" -><I -> XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX</I -></TT +> XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX</VAR >, - [<TT + [<VAR CLASS="REPLACEABLE" -><I ->Account type</I -></TT ->] and <TT +>Account type</VAR +>] and <VAR CLASS="REPLACEABLE" -><I -> last-change-time</I -></TT +> last-change-time</VAR > sections are significant and are looked at in the Samba code.</P ><P @@ -9267,9 +9266,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 - <TT + <CODE CLASS="CONSTANT" ->"NO PASSWORD"</TT +>"NO PASSWORD"</CODE > (minus the quotes).</P ><P >For example, to clear the password for user bob, his smbpasswd file @@ -9333,8 +9332,8 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN3225" -></A ->14.1. About</H2 +>14.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 @@ -9348,13 +9347,13 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN3228" -></A ->14.2. General Overview</H2 +>14.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 +>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 @@ -9363,7 +9362,7 @@ CLASS="FILENAME" >.. These shared libraries should be located in the <TT CLASS="FILENAME" -><sambaroot>/lib/rpc</TT +><sambaroot>/lib/rpc</TT >. smbd then attempts to call the rpc_pipe_init function within the shared library.</P ><P diff --git a/docs/htmldocs/Samba-HOWTO-Collection.html b/docs/htmldocs/Samba-HOWTO-Collection.html index d758fbbe11..cad5fbc2bc 100644 --- a/docs/htmldocs/Samba-HOWTO-Collection.html +++ b/docs/htmldocs/Samba-HOWTO-Collection.html @@ -5,7 +5,7 @@ >SAMBA Project Documentation</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"></HEAD +CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD ><BODY CLASS="BOOK" BGCOLOR="#FFFFFF" @@ -24,8 +24,8 @@ CLASS="TITLEPAGE" CLASS="TITLE" ><A NAME="SAMBA-HOWTO-COLLECTION" -></A ->SAMBA Project Documentation</H1 +>SAMBA Project Documentation</A +></H1 ><H3 CLASS="AUTHOR" ><A @@ -99,57 +99,33 @@ HREF="#INSTALL" ><DT >1.1. <A HREF="#AEN26" ->Read the man pages</A +>Obtaining and installing samba</A ></DT ><DT >1.2. <A -HREF="#AEN36" ->Building the Binaries</A +HREF="#AEN31" +>Configuring samba</A ></DT ><DT >1.3. <A HREF="#AEN64" ->The all important step</A -></DT -><DT ->1.4. <A -HREF="#AEN68" ->Create the smb configuration file.</A -></DT -><DT ->1.5. <A -HREF="#AEN82" ->Test your config file with - <B -CLASS="COMMAND" ->testparm</B -></A -></DT -><DT ->1.6. <A -HREF="#AEN90" ->Starting the smbd and nmbd</A -></DT -><DT ->1.7. <A -HREF="#AEN145" >Try listing the shares available on your server</A ></DT ><DT ->1.8. <A -HREF="#AEN154" +>1.4. <A +HREF="#AEN73" >Try connecting with the unix client</A ></DT ><DT ->1.9. <A -HREF="#AEN170" +>1.5. <A +HREF="#AEN89" >Try connecting from a DOS, WfWg, Win9x, WinNT, Win2k, OS/2, etc... client</A ></DT ><DT ->1.10. <A -HREF="#AEN184" +>1.6. <A +HREF="#AEN103" >What If Things Don't Work?</A ></DT ></DL @@ -163,32 +139,32 @@ HREF="#BROWSING-QUICK" ><DL ><DT >2.1. <A -HREF="#AEN230" +HREF="#AEN130" >Discussion</A ></DT ><DT >2.2. <A -HREF="#AEN238" +HREF="#AEN139" >Use of the "Remote Announce" parameter</A ></DT ><DT >2.3. <A -HREF="#AEN252" +HREF="#AEN153" >Use of the "Remote Browse Sync" parameter</A ></DT ><DT >2.4. <A -HREF="#AEN257" +HREF="#AEN158" >Use of WINS</A ></DT ><DT >2.5. <A -HREF="#AEN268" +HREF="#AEN169" >Do NOT use more than one (1) protocol on MS Windows machines</A ></DT ><DT >2.6. <A -HREF="#AEN274" +HREF="#AEN177" >Name Resolution Order</A ></DT ></DL @@ -202,42 +178,42 @@ HREF="#PASSDB" ><DL ><DT >3.1. <A -HREF="#AEN324" +HREF="#AEN227" >Introduction</A ></DT ><DT >3.2. <A -HREF="#AEN331" +HREF="#AEN234" >Important Notes About Security</A ></DT ><DT >3.3. <A -HREF="#AEN357" +HREF="#AEN260" >The smbpasswd Command</A ></DT ><DT >3.4. <A -HREF="#AEN388" +HREF="#AEN291" >Plain text</A ></DT ><DT >3.5. <A -HREF="#AEN393" +HREF="#AEN296" >TDB</A ></DT ><DT >3.6. <A -HREF="#AEN396" +HREF="#AEN299" >LDAP</A ></DT ><DT >3.7. <A -HREF="#AEN614" +HREF="#AEN517" >MySQL</A ></DT ><DT >3.8. <A -HREF="#AEN662" +HREF="#AEN565" >Passdb XML plugin</A ></DT ></DL @@ -265,49 +241,49 @@ HREF="#SAMBA-PDC" ><DL ><DT >5.1. <A -HREF="#AEN722" +HREF="#AEN625" >Prerequisite Reading</A ></DT ><DT >5.2. <A -HREF="#AEN728" +HREF="#AEN631" >Background</A ></DT ><DT >5.3. <A -HREF="#AEN767" +HREF="#AEN670" >Configuring the Samba Domain Controller</A ></DT ><DT >5.4. <A -HREF="#AEN810" +HREF="#AEN713" >Creating Machine Trust Accounts and Joining Clients to the Domain</A ></DT ><DT >5.5. <A -HREF="#AEN894" +HREF="#AEN797" >Common Problems and Errors</A ></DT ><DT >5.6. <A -HREF="#AEN942" +HREF="#AEN845" >System Policies and Profiles</A ></DT ><DT >5.7. <A -HREF="#AEN986" +HREF="#AEN889" >What other help can I get?</A ></DT ><DT >5.8. <A -HREF="#AEN1100" +HREF="#AEN1003" >Domain Control for Windows 9x/ME</A ></DT ><DT >5.9. <A -HREF="#AEN1238" ->DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba</A +HREF="#AEN1141" +>DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba</A ></DT ></DL ></DD @@ -320,27 +296,27 @@ HREF="#SAMBA-BDC" ><DL ><DT >6.1. <A -HREF="#AEN1274" +HREF="#AEN1177" >Prerequisite Reading</A ></DT ><DT >6.2. <A -HREF="#AEN1278" +HREF="#AEN1181" >Background</A ></DT ><DT >6.3. <A -HREF="#AEN1286" +HREF="#AEN1189" >What qualifies a Domain Controller on the network?</A ></DT ><DT >6.4. <A -HREF="#AEN1295" +HREF="#AEN1198" >Can Samba be a Backup Domain Controller to an NT PDC?</A ></DT ><DT >6.5. <A -HREF="#AEN1300" +HREF="#AEN1203" >How do I set up a Samba BDC?</A ></DT ></DL @@ -354,42 +330,42 @@ HREF="#ADS" ><DL ><DT >7.1. <A -HREF="#AEN1339" +HREF="#AEN1242" >Installing the required packages for Debian</A ></DT ><DT >7.2. <A -HREF="#AEN1346" +HREF="#AEN1249" >Installing the required packages for RedHat</A ></DT ><DT >7.3. <A -HREF="#AEN1356" +HREF="#AEN1259" >Compile Samba</A ></DT ><DT >7.4. <A -HREF="#AEN1371" +HREF="#AEN1274" >Setup your /etc/krb5.conf</A ></DT ><DT >7.5. <A -HREF="#AEN1381" +HREF="#AEN1284" >Create the computer account</A ></DT ><DT >7.6. <A -HREF="#AEN1393" +HREF="#AEN1296" >Test your server setup</A ></DT ><DT >7.7. <A -HREF="#AEN1398" +HREF="#AEN1301" >Testing with smbclient</A ></DT ><DT >7.8. <A -HREF="#AEN1401" +HREF="#AEN1304" >Notes</A ></DT ></DL @@ -403,17 +379,17 @@ HREF="#DOMAIN-SECURITY" ><DL ><DT >8.1. <A -HREF="#AEN1423" +HREF="#AEN1326" >Joining an NT Domain with Samba 3.0</A ></DT ><DT >8.2. <A -HREF="#AEN1478" +HREF="#AEN1381" >Samba and Windows 2000 Domains</A ></DT ><DT >8.3. <A -HREF="#AEN1481" +HREF="#AEN1384" >Why is this better than security = server?</A ></DT ></DL @@ -436,34 +412,34 @@ HREF="#INTEGRATE-MS-NETWORKS" ><DL ><DT >9.1. <A -HREF="#AEN1513" +HREF="#AEN1416" >Agenda</A ></DT ><DT >9.2. <A -HREF="#AEN1535" +HREF="#AEN1438" >Name Resolution in a pure Unix/Linux world</A ></DT ><DT >9.3. <A -HREF="#AEN1598" +HREF="#AEN1501" >Name resolution as used within MS Windows networking</A ></DT ><DT >9.4. <A -HREF="#AEN1643" +HREF="#AEN1546" >How browsing functions and how to deploy stable and dependable browsing using Samba</A ></DT ><DT >9.5. <A -HREF="#AEN1653" +HREF="#AEN1556" >MS Windows security options and how to configure Samba for seemless integration</A ></DT ><DT >9.6. <A -HREF="#AEN1723" +HREF="#AEN1626" >Conclusions</A ></DT ></DL @@ -477,39 +453,39 @@ HREF="#UNIX-PERMISSIONS" ><DL ><DT >10.1. <A -HREF="#AEN1744" +HREF="#AEN1647" >Viewing and changing UNIX permissions using the NT security dialogs</A ></DT ><DT >10.2. <A -HREF="#AEN1748" +HREF="#AEN1651" >How to view file security on a Samba share</A ></DT ><DT >10.3. <A -HREF="#AEN1759" +HREF="#AEN1662" >Viewing file ownership</A ></DT ><DT >10.4. <A -HREF="#AEN1779" +HREF="#AEN1682" >Viewing file or directory permissions</A ></DT ><DT >10.5. <A -HREF="#AEN1815" +HREF="#AEN1718" >Modifying file or directory permissions</A ></DT ><DT >10.6. <A -HREF="#AEN1837" +HREF="#AEN1740" >Interaction with the standard Samba create mask parameters</A ></DT ><DT >10.7. <A -HREF="#AEN1901" +HREF="#AEN1804" >Interaction with the standard Samba file attribute mapping</A ></DT @@ -525,17 +501,17 @@ managed authentication</A ><DL ><DT >11.1. <A -HREF="#AEN1922" +HREF="#AEN1825" >Samba and PAM</A ></DT ><DT >11.2. <A -HREF="#AEN1966" +HREF="#AEN1869" >Distributed Authentication</A ></DT ><DT >11.3. <A -HREF="#AEN1973" +HREF="#AEN1876" >PAM Configuration in smb.conf</A ></DT ></DL @@ -549,7 +525,7 @@ HREF="#MSDFS" ><DL ><DT >12.1. <A -HREF="#AEN1993" +HREF="#AEN1896" >Instructions</A ></DT ></DL @@ -563,22 +539,22 @@ HREF="#PRINTING" ><DL ><DT >13.1. <A -HREF="#AEN2054" +HREF="#AEN1957" >Introduction</A ></DT ><DT >13.2. <A -HREF="#AEN2076" +HREF="#AEN1979" >Configuration</A ></DT ><DT >13.3. <A -HREF="#AEN2184" +HREF="#AEN2087" >The Imprints Toolset</A ></DT ><DT >13.4. <A -HREF="#AEN2227" +HREF="#AEN2130" >Diagnosis</A ></DT ></DL @@ -592,37 +568,37 @@ HREF="#WINBIND" ><DL ><DT >14.1. <A -HREF="#AEN2360" +HREF="#AEN2263" >Abstract</A ></DT ><DT >14.2. <A -HREF="#AEN2364" +HREF="#AEN2267" >Introduction</A ></DT ><DT >14.3. <A -HREF="#AEN2377" +HREF="#AEN2280" >What Winbind Provides</A ></DT ><DT >14.4. <A -HREF="#AEN2388" +HREF="#AEN2291" >How Winbind Works</A ></DT ><DT >14.5. <A -HREF="#AEN2431" +HREF="#AEN2334" >Installation and Configuration</A ></DT ><DT >14.6. <A -HREF="#AEN2680" +HREF="#AEN2583" >Limitations</A ></DT ><DT >14.7. <A -HREF="#AEN2690" +HREF="#AEN2593" >Conclusion</A ></DT ></DL @@ -636,57 +612,57 @@ HREF="#IMPROVED-BROWSING" ><DL ><DT >15.1. <A -HREF="#AEN2700" +HREF="#AEN2603" >Overview of browsing</A ></DT ><DT >15.2. <A -HREF="#AEN2704" +HREF="#AEN2608" >Browsing support in samba</A ></DT ><DT >15.3. <A -HREF="#AEN2713" +HREF="#AEN2616" >Problem resolution</A ></DT ><DT >15.4. <A -HREF="#AEN2720" +HREF="#AEN2625" >Browsing across subnets</A ></DT ><DT >15.5. <A -HREF="#AEN2760" +HREF="#AEN2665" >Setting up a WINS server</A ></DT ><DT >15.6. <A -HREF="#AEN2779" +HREF="#AEN2684" >Setting up Browsing in a WORKGROUP</A ></DT ><DT >15.7. <A -HREF="#AEN2797" +HREF="#AEN2702" >Setting up Browsing in a DOMAIN</A ></DT ><DT >15.8. <A -HREF="#AEN2807" +HREF="#AEN2712" >Forcing samba to be the master</A ></DT ><DT >15.9. <A -HREF="#AEN2816" +HREF="#AEN2721" >Making samba the domain master</A ></DT ><DT >15.10. <A -HREF="#AEN2834" +HREF="#AEN2739" >Note about broadcast addresses</A ></DT ><DT >15.11. <A -HREF="#AEN2837" +HREF="#AEN2742" >Multiple interfaces</A ></DT ></DL @@ -700,128 +676,148 @@ HREF="#VFS" ><DL ><DT >16.1. <A -HREF="#AEN2855" +HREF="#AEN2760" >Introduction and configuration</A ></DT ><DT >16.2. <A -HREF="#AEN2864" +HREF="#AEN2769" >Included modules</A ></DT ><DT >16.3. <A -HREF="#AEN2918" +HREF="#AEN2823" >VFS modules available elsewhere</A ></DT ></DL ></DD ><DT >17. <A -HREF="#CVS-ACCESS" ->Access Samba source code via CVS</A -></DT -><DD -><DL -><DT ->17.1. <A -HREF="#AEN2942" ->Introduction</A -></DT -><DT ->17.2. <A -HREF="#AEN2947" ->CVS Access to samba.org</A -></DT -></DL -></DD -><DT ->18. <A HREF="#GROUPMAPPING" >Group mapping HOWTO</A ></DT ><DT ->19. <A +>18. <A HREF="#SPEED" >Samba performance issues</A ></DT ><DD ><DL ><DT ->19.1. <A -HREF="#AEN3033" +>18.1. <A +HREF="#AEN2890" >Comparisons</A ></DT ><DT ->19.2. <A -HREF="#AEN3039" +>18.2. <A +HREF="#AEN2896" >Socket options</A ></DT ><DT ->19.3. <A -HREF="#AEN3046" +>18.3. <A +HREF="#AEN2903" >Read size</A ></DT ><DT ->19.4. <A -HREF="#AEN3051" +>18.4. <A +HREF="#AEN2908" >Max xmit</A ></DT ><DT ->19.5. <A -HREF="#AEN3056" +>18.5. <A +HREF="#AEN2913" >Log level</A ></DT ><DT ->19.6. <A -HREF="#AEN3059" +>18.6. <A +HREF="#AEN2916" >Read raw</A ></DT ><DT ->19.7. <A -HREF="#AEN3064" +>18.7. <A +HREF="#AEN2921" >Write raw</A ></DT ><DT ->19.8. <A -HREF="#AEN3068" +>18.8. <A +HREF="#AEN2925" >Slow Clients</A ></DT ><DT ->19.9. <A -HREF="#AEN3072" +>18.9. <A +HREF="#AEN2929" >Slow Logins</A ></DT ><DT ->19.10. <A -HREF="#AEN3075" +>18.10. <A +HREF="#AEN2932" >Client tuning</A ></DT ></DL ></DD ><DT ->20. <A +>19. <A HREF="#GROUPPROFILES" ->Creating Group Profiles</A +>Creating Group Prolicy Files</A ></DT ><DD ><DL ><DT ->20.1. <A -HREF="#AEN3123" +>19.1. <A +HREF="#AEN2980" >Windows '9x</A ></DT ><DT ->20.2. <A -HREF="#AEN3132" +>19.2. <A +HREF="#AEN2990" >Windows NT 4</A ></DT ><DT ->20.3. <A -HREF="#AEN3170" +>19.3. <A +HREF="#AEN3028" >Windows 2000/XP</A ></DT ></DL ></DD +><DT +>20. <A +HREF="#SECURING-SAMBA" +>Securing Samba</A +></DT +><DD +><DL +><DT +>20.1. <A +HREF="#AEN3109" +>Introduction</A +></DT +><DT +>20.2. <A +HREF="#AEN3112" +>Using host based protection</A +></DT +><DT +>20.3. <A +HREF="#AEN3119" +>Using interface protection</A +></DT +><DT +>20.4. <A +HREF="#AEN3128" +>Using a firewall</A +></DT +><DT +>20.5. <A +HREF="#AEN3135" +>Using a IPC$ share deny</A +></DT +><DT +>20.6. <A +HREF="#AEN3144" +>Upgrading Samba</A +></DT +></DL +></DD ></DL ></DD ><DT @@ -840,24 +836,29 @@ HREF="#PORTABILITY" ><DL ><DT >21.1. <A -HREF="#AEN3251" +HREF="#AEN3156" >HPUX</A ></DT ><DT >21.2. <A -HREF="#AEN3257" +HREF="#AEN3162" >SCO Unix</A ></DT ><DT >21.3. <A -HREF="#AEN3261" +HREF="#AEN3166" >DNIX</A ></DT ><DT >21.4. <A -HREF="#AEN3290" +HREF="#AEN3195" >RedHat Linux Rembrandt-II</A ></DT +><DT +>21.5. <A +HREF="#AEN3201" +>AIX</A +></DT ></DL ></DD ><DT @@ -869,95 +870,124 @@ HREF="#OTHER-CLIENTS" ><DL ><DT >22.1. <A -HREF="#AEN3311" +HREF="#AEN3221" >Macintosh clients?</A ></DT ><DT >22.2. <A -HREF="#AEN3320" +HREF="#AEN3230" >OS2 Client</A ></DT ><DT >22.3. <A -HREF="#AEN3360" +HREF="#AEN3270" >Windows for Workgroups</A ></DT ><DT >22.4. <A -HREF="#AEN3381" +HREF="#AEN3294" >Windows '95/'98</A ></DT ><DT >22.5. <A -HREF="#AEN3397" +HREF="#AEN3310" >Windows 2000 Service Pack 2</A ></DT ></DL ></DD ><DT >23. <A +HREF="#COMPILING" +>How to compile SAMBA</A +></DT +><DD +><DL +><DT +>23.1. <A +HREF="#AEN3337" +>Access Samba source code via CVS</A +></DT +><DT +>23.2. <A +HREF="#AEN3380" +>Accessing the samba sources via rsync and ftp</A +></DT +><DT +>23.3. <A +HREF="#AEN3386" +>Building the Binaries</A +></DT +><DT +>23.4. <A +HREF="#AEN3414" +>Starting the smbd and nmbd</A +></DT +></DL +></DD +><DT +>24. <A HREF="#BUGREPORT" >Reporting Bugs</A ></DT ><DD ><DL ><DT ->23.1. <A -HREF="#AEN3421" +>24.1. <A +HREF="#AEN3476" >Introduction</A ></DT ><DT ->23.2. <A -HREF="#AEN3431" +>24.2. <A +HREF="#AEN3486" >General info</A ></DT ><DT ->23.3. <A -HREF="#AEN3437" +>24.3. <A +HREF="#AEN3492" >Debug levels</A ></DT ><DT ->23.4. <A -HREF="#AEN3454" +>24.4. <A +HREF="#AEN3509" >Internal errors</A ></DT ><DT ->23.5. <A -HREF="#AEN3464" +>24.5. <A +HREF="#AEN3519" >Attaching to a running process</A ></DT ><DT ->23.6. <A -HREF="#AEN3467" +>24.6. <A +HREF="#AEN3522" >Patches</A ></DT ></DL ></DD ><DT ->24. <A +>25. <A HREF="#DIAGNOSIS" ->Diagnosing your samba server</A +>The samba checklist</A ></DT ><DD ><DL ><DT ->24.1. <A -HREF="#AEN3490" +>25.1. <A +HREF="#AEN3545" >Introduction</A ></DT ><DT ->24.2. <A -HREF="#AEN3495" +>25.2. <A +HREF="#AEN3550" >Assumptions</A ></DT ><DT ->24.3. <A -HREF="#AEN3505" +>25.3. <A +HREF="#AEN3560" >Tests</A ></DT ><DT ->24.4. <A -HREF="#AEN3615" +>25.4. <A +HREF="#AEN3670" >Still having troubles?</A ></DT ></DL @@ -1005,105 +1035,61 @@ HREF="#INSTALL" ><DT >1.1. <A HREF="#AEN26" ->Read the man pages</A +>Obtaining and installing samba</A ></DT ><DT >1.2. <A -HREF="#AEN36" ->Building the Binaries</A -></DT -><DT ->1.3. <A -HREF="#AEN64" ->The all important step</A -></DT -><DT ->1.4. <A -HREF="#AEN68" ->Create the smb configuration file.</A -></DT -><DT ->1.5. <A -HREF="#AEN82" ->Test your config file with - <B -CLASS="COMMAND" ->testparm</B -></A -></DT -><DT ->1.6. <A -HREF="#AEN90" ->Starting the smbd and nmbd</A +HREF="#AEN31" +>Configuring samba</A ></DT ><DD ><DL ><DT ->1.6.1. <A -HREF="#AEN100" ->Starting from inetd.conf</A +>1.2.1. <A +HREF="#AEN36" +>Editing the smb.conf file</A ></DT ><DT ->1.6.2. <A -HREF="#AEN129" ->Alternative: starting it as a daemon</A +>1.2.2. <A +HREF="#AEN58" +>SWAT</A ></DT ></DL ></DD ><DT ->1.7. <A -HREF="#AEN145" +>1.3. <A +HREF="#AEN64" >Try listing the shares available on your server</A ></DT ><DT ->1.8. <A -HREF="#AEN154" +>1.4. <A +HREF="#AEN73" >Try connecting with the unix client</A ></DT ><DT ->1.9. <A -HREF="#AEN170" +>1.5. <A +HREF="#AEN89" >Try connecting from a DOS, WfWg, Win9x, WinNT, Win2k, OS/2, etc... client</A ></DT ><DT ->1.10. <A -HREF="#AEN184" +>1.6. <A +HREF="#AEN103" >What If Things Don't Work?</A ></DT ><DD ><DL ><DT ->1.10.1. <A -HREF="#AEN189" ->Diagnosing Problems</A -></DT -><DT ->1.10.2. <A -HREF="#AEN193" +>1.6.1. <A +HREF="#AEN108" >Scope IDs</A ></DT ><DT ->1.10.3. <A -HREF="#AEN196" ->Choosing the Protocol Level</A -></DT -><DT ->1.10.4. <A -HREF="#AEN205" ->Printing from UNIX to a Client PC</A -></DT -><DT ->1.10.5. <A -HREF="#AEN210" +>1.6.2. <A +HREF="#AEN111" >Locking</A ></DT -><DT ->1.10.6. <A -HREF="#AEN219" ->Mapping Usernames</A -></DT ></DL ></DD ></DL @@ -1117,32 +1103,32 @@ HREF="#BROWSING-QUICK" ><DL ><DT >2.1. <A -HREF="#AEN230" +HREF="#AEN130" >Discussion</A ></DT ><DT >2.2. <A -HREF="#AEN238" +HREF="#AEN139" >Use of the "Remote Announce" parameter</A ></DT ><DT >2.3. <A -HREF="#AEN252" +HREF="#AEN153" >Use of the "Remote Browse Sync" parameter</A ></DT ><DT >2.4. <A -HREF="#AEN257" +HREF="#AEN158" >Use of WINS</A ></DT ><DT >2.5. <A -HREF="#AEN268" +HREF="#AEN169" >Do NOT use more than one (1) protocol on MS Windows machines</A ></DT ><DT >2.6. <A -HREF="#AEN274" +HREF="#AEN177" >Name Resolution Order</A ></DT ></DL @@ -1156,146 +1142,146 @@ HREF="#PASSDB" ><DL ><DT >3.1. <A -HREF="#AEN324" +HREF="#AEN227" >Introduction</A ></DT ><DT >3.2. <A -HREF="#AEN331" +HREF="#AEN234" >Important Notes About Security</A ></DT ><DD ><DL ><DT >3.2.1. <A -HREF="#AEN346" +HREF="#AEN249" >Advantages of SMB Encryption</A ></DT ><DT >3.2.2. <A -HREF="#AEN351" +HREF="#AEN254" >Advantages of non-encrypted passwords</A ></DT ></DL ></DD ><DT >3.3. <A -HREF="#AEN357" +HREF="#AEN260" >The smbpasswd Command</A ></DT ><DT >3.4. <A -HREF="#AEN388" +HREF="#AEN291" >Plain text</A ></DT ><DT >3.5. <A -HREF="#AEN393" +HREF="#AEN296" >TDB</A ></DT ><DT >3.6. <A -HREF="#AEN396" +HREF="#AEN299" >LDAP</A ></DT ><DD ><DL ><DT >3.6.1. <A -HREF="#AEN398" +HREF="#AEN301" >Introduction</A ></DT ><DT >3.6.2. <A -HREF="#AEN418" +HREF="#AEN321" >Introduction</A ></DT ><DT >3.6.3. <A -HREF="#AEN447" +HREF="#AEN350" >Supported LDAP Servers</A ></DT ><DT >3.6.4. <A -HREF="#AEN452" +HREF="#AEN355" >Schema and Relationship to the RFC 2307 posixAccount</A ></DT ><DT >3.6.5. <A -HREF="#AEN464" +HREF="#AEN367" >Configuring Samba with LDAP</A ></DT ><DT >3.6.6. <A -HREF="#AEN511" +HREF="#AEN414" >Accounts and Groups management</A ></DT ><DT >3.6.7. <A -HREF="#AEN516" +HREF="#AEN419" >Security and sambaAccount</A ></DT ><DT >3.6.8. <A -HREF="#AEN536" +HREF="#AEN439" >LDAP specials attributes for sambaAccounts</A ></DT ><DT >3.6.9. <A -HREF="#AEN606" +HREF="#AEN509" >Example LDIF Entries for a sambaAccount</A ></DT ></DL ></DD ><DT >3.7. <A -HREF="#AEN614" +HREF="#AEN517" >MySQL</A ></DT ><DD ><DL ><DT >3.7.1. <A -HREF="#AEN616" +HREF="#AEN519" >Building</A ></DT ><DT >3.7.2. <A -HREF="#AEN622" +HREF="#AEN525" >Creating the database</A ></DT ><DT >3.7.3. <A -HREF="#AEN632" +HREF="#AEN535" >Configuring</A ></DT ><DT >3.7.4. <A -HREF="#AEN649" +HREF="#AEN552" >Using plaintext passwords or encrypted password</A ></DT ><DT >3.7.5. <A -HREF="#AEN654" +HREF="#AEN557" >Getting non-column data from the table</A ></DT ></DL ></DD ><DT >3.8. <A -HREF="#AEN662" +HREF="#AEN565" >Passdb XML plugin</A ></DT ><DD ><DL ><DT >3.8.1. <A -HREF="#AEN664" +HREF="#AEN567" >Building</A ></DT ><DT >3.8.2. <A -HREF="#AEN670" +HREF="#AEN573" >Usage</A ></DT ></DL @@ -1318,166 +1304,50 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN26" -></A ->1.1. Read the man pages</H2 -><P ->The man pages distributed with SAMBA contain - lots of useful info that will help to get you started. - If you don't know how to read man pages then try - something like:</P -><P -><TT -CLASS="PROMPT" ->$ </TT -><TT -CLASS="USERINPUT" -><B ->man smbd.8</B -></TT -> - or - <TT -CLASS="PROMPT" ->$ </TT -><TT -CLASS="USERINPUT" -><B ->nroff -man smbd.8 | more - </B -></TT -> on older unixes.</P +>1.1. Obtaining and installing samba</A +></H2 ><P ->Other sources of information are pointed to - by the Samba web site,<A -HREF="http://www.samba.org/" +>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" -> http://www.samba.org</A -></P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN36" -></A ->1.2. Building the Binaries</H2 -><P ->To do this, first run the program <B -CLASS="COMMAND" ->./configure - </B -> in the source directory. This should automatically - configure Samba for your operating system. If you have unusual - needs then you may wish to run</P -><P -><TT -CLASS="PROMPT" ->root# </TT -><TT -CLASS="USERINPUT" -><B ->./configure --help - </B -></TT -></P -><P ->first to see what special options you can enable. - Then executing</P -><P -><TT -CLASS="PROMPT" ->root# </TT -><TT -CLASS="USERINPUT" -><B ->make</B -></TT -></P -><P ->will create the binaries. Once it's successfully - compiled you can use </P -><P -><TT -CLASS="PROMPT" ->root# </TT -><TT -CLASS="USERINPUT" -><B ->make install</B -></TT -></P -><P ->to install the binaries and manual pages. You can - separately install the binaries and/or man pages using</P -><P -><TT -CLASS="PROMPT" ->root# </TT -><TT -CLASS="USERINPUT" -><B ->make installbin - </B -></TT -></P -><P ->and</P -><P -><TT -CLASS="PROMPT" ->root# </TT -><TT -CLASS="USERINPUT" -><B ->make installman - </B -></TT -></P -><P ->Note that if you are upgrading for a previous version - of Samba you might like to know that the old versions of - the binaries will be renamed with a ".old" extension. You - can go back to the previous version with</P -><P -><TT -CLASS="PROMPT" ->root# </TT -><TT -CLASS="USERINPUT" -><B ->make revert - </B -></TT -></P +>the samba homepage</A +> + </P ><P ->if you find this version a disaster!</P +>If you need to compile samba from source, check the + appropriate appendix chapter.</P ></DIV ><DIV CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN64" -></A ->1.3. The all important step</H2 -><P ->At this stage you must fetch yourself a - coffee or other drink you find stimulating. Getting the rest - of the install right can sometimes be tricky, so you will - probably need it.</P +NAME="AEN31" +>1.2. Configuring samba</A +></H2 ><P ->If you have installed samba before then you can skip - this step.</P -></DIV +>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="SECT1" -><HR><H2 -CLASS="SECT1" +CLASS="SECT2" +><HR><H3 +CLASS="SECT2" ><A -NAME="AEN68" -></A ->1.4. Create the smb configuration file.</H2 +NAME="AEN36" +>1.2.1. Editing the smb.conf file</A +></H3 ><P >There are sample configuration files in the examples subdirectory in the distribution. I suggest you read them @@ -1525,19 +1395,18 @@ CLASS="FILENAME" ><P >For more information about security settings for the [homes] share please refer to the document UNIX_SECURITY.txt.</P -></DIV ><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" +CLASS="SECT3" +><HR><H4 +CLASS="SECT3" ><A -NAME="AEN82" -></A ->1.5. Test your config file with +NAME="AEN50" +>1.2.1.1. Test your config file with <B CLASS="COMMAND" >testparm</B -></H2 +></A +></H4 ><P >It's important that you test the validity of your <TT @@ -1556,205 +1425,33 @@ CLASS="FILENAME" >smb.conf</TT >!</P ></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN90" -></A ->1.6. Starting the smbd and nmbd</H2 -><P ->You must choose to start smbd and nmbd either - as daemons or from <B -CLASS="COMMAND" ->inetd</B ->. Don't try - to do both! Either you can put them in <TT -CLASS="FILENAME" -> inetd.conf</TT -> and have them started on demand - by <B -CLASS="COMMAND" ->inetd</B ->, or you can start them as - daemons either from the command line or in <TT -CLASS="FILENAME" -> /etc/rc.local</TT ->. See the man pages for details - on the command line options. Take particular care to read - the bit about what user you need to be in order to start - Samba. In many cases you must be root.</P -><P ->The main advantage of starting <B -CLASS="COMMAND" ->smbd</B -> - and <B -CLASS="COMMAND" ->nmbd</B -> using the recommended daemon method - is that they will respond slightly more quickly to an initial connection - request.</P -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN100" -></A ->1.6.1. Starting from inetd.conf</H3 -><P ->NOTE; The following will be different if - you use NIS or NIS+ to distributed services maps.</P -><P ->Look at your <TT -CLASS="FILENAME" ->/etc/services</TT ->. - What is defined at port 139/tcp. If nothing is defined - then add a line like this:</P -><P -><TT -CLASS="USERINPUT" -><B ->netbios-ssn 139/tcp</B -></TT -></P -><P ->similarly for 137/udp you should have an entry like:</P -><P -><TT -CLASS="USERINPUT" -><B ->netbios-ns 137/udp</B -></TT -></P -><P ->Next edit your <TT -CLASS="FILENAME" ->/etc/inetd.conf</TT -> - and add two lines something like this:</P -><P -><PRE -CLASS="PROGRAMLISTING" -> netbios-ssn stream tcp nowait root /usr/local/samba/bin/smbd smbd - netbios-ns dgram udp wait root /usr/local/samba/bin/nmbd nmbd - </PRE -></P -><P ->The exact syntax of <TT -CLASS="FILENAME" ->/etc/inetd.conf</TT -> - varies between unixes. Look at the other entries in inetd.conf - for a guide.</P -><P ->NOTE: Some unixes already have entries like netbios_ns - (note the underscore) in <TT -CLASS="FILENAME" ->/etc/services</TT ->. - You must either edit <TT -CLASS="FILENAME" ->/etc/services</TT -> or - <TT -CLASS="FILENAME" ->/etc/inetd.conf</TT -> to make them consistent.</P -><P ->NOTE: On many systems you may need to use the - "interfaces" option in smb.conf to specify the IP address - and netmask of your interfaces. Run <B -CLASS="COMMAND" ->ifconfig</B -> - as root if you don't know what the broadcast is for your - net. <B -CLASS="COMMAND" ->nmbd</B -> tries to determine it at run - time, but fails on some unixes. See the section on "testing nmbd" - for a method of finding if you need to do this.</P -><P ->!!!WARNING!!! Many unixes only accept around 5 - parameters on the command line in <TT -CLASS="FILENAME" ->inetd.conf</TT ->. - This means you shouldn't use spaces between the options and - arguments, or you should use a script, and start the script - from <B -CLASS="COMMAND" ->inetd</B ->.</P -><P ->Restart <B -CLASS="COMMAND" ->inetd</B ->, perhaps just send - it a HUP. If you have installed an earlier version of <B -CLASS="COMMAND" -> nmbd</B -> then you may need to kill nmbd as well.</P ></DIV ><DIV CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN129" -></A ->1.6.2. Alternative: starting it as a daemon</H3 -><P ->To start the server as a daemon you should create - a script something like this one, perhaps calling - it <TT -CLASS="FILENAME" ->startsmb</TT ->.</P -><P -><PRE -CLASS="PROGRAMLISTING" -> #!/bin/sh - /usr/local/samba/bin/smbd -D - /usr/local/samba/bin/nmbd -D - </PRE -></P -><P ->then make it executable with <B -CLASS="COMMAND" ->chmod - +x startsmb</B -></P +NAME="AEN58" +>1.2.2. SWAT</A +></H3 ><P ->You can then run <B -CLASS="COMMAND" ->startsmb</B -> by - hand or execute it from <TT -CLASS="FILENAME" ->/etc/rc.local</TT -> - </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 kill it send a kill signal to the processes - <B -CLASS="COMMAND" ->nmbd</B -> and <B -CLASS="COMMAND" ->smbd</B ->.</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: 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 +>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 @@ -1762,25 +1459,21 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN145" -></A ->1.7. Try listing the shares available on your - server</H2 +NAME="AEN64" +>1.3. Try listing the shares available on your + server</A +></H2 ><P -><TT +><SAMP CLASS="PROMPT" ->$ </TT -><TT +>$ </SAMP +><KBD CLASS="USERINPUT" -><B >smbclient -L - <TT + <VAR CLASS="REPLACEABLE" -><I ->yourhostname</I -></TT -></B -></TT +>yourhostname</VAR +></KBD ></P ><P >You should get back a list of shares available on @@ -1803,39 +1496,31 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN154" -></A ->1.8. Try connecting with the unix client</H2 +NAME="AEN73" +>1.4. Try connecting with the unix client</A +></H2 ><P -><TT +><SAMP CLASS="PROMPT" ->$ </TT -><TT +>$ </SAMP +><KBD CLASS="USERINPUT" -><B ->smbclient <TT +>smbclient <VAR CLASS="REPLACEABLE" -><I -> //yourhostname/aservice</I -></TT -></B -></TT +> //yourhostname/aservice</VAR +></KBD ></P ><P ->Typically the <TT +>Typically the <VAR CLASS="REPLACEABLE" -><I ->yourhostname</I -></TT +>yourhostname</VAR > would be the name of the host where you installed <B CLASS="COMMAND" > smbd</B ->. The <TT +>. The <VAR CLASS="REPLACEABLE" -><I ->aservice</I -></TT +>aservice</VAR > is any service you have defined in the <TT CLASS="FILENAME" @@ -1850,15 +1535,13 @@ CLASS="FILENAME" >For example if your unix host is bambi and your login name is fred you would type:</P ><P -><TT +><SAMP CLASS="PROMPT" ->$ </TT -><TT +>$ </SAMP +><KBD CLASS="USERINPUT" -><B >smbclient //bambi/fred - </B -></TT + </KBD ></P ></DIV ><DIV @@ -1866,46 +1549,40 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN170" -></A ->1.9. Try connecting from a DOS, WfWg, Win9x, WinNT, - Win2k, OS/2, etc... client</H2 +NAME="AEN89" +>1.5. Try connecting from a DOS, WfWg, Win9x, WinNT, + Win2k, OS/2, etc... client</A +></H2 ><P >Try mounting disks. eg:</P ><P -><TT +><SAMP CLASS="PROMPT" ->C:\WINDOWS\> </TT -><TT +>C:\WINDOWS\> </SAMP +><KBD CLASS="USERINPUT" -><B >net use d: \\servername\service - </B -></TT + </KBD ></P ><P >Try printing. eg:</P ><P -><TT +><SAMP CLASS="PROMPT" ->C:\WINDOWS\> </TT -><TT +>C:\WINDOWS\> </SAMP +><KBD CLASS="USERINPUT" -><B >net use lpt1: - \\servername\spoolservice</B -></TT + \\servername\spoolservice</KBD ></P ><P -><TT +><SAMP CLASS="PROMPT" ->C:\WINDOWS\> </TT -><TT +>C:\WINDOWS\> </SAMP +><KBD CLASS="USERINPUT" -><B >print filename - </B -></TT + </KBD ></P ><P >Celebrate, or send me a bug report!</P @@ -1915,55 +1592,41 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN184" -></A ->1.10. What If Things Don't Work?</H2 -><P ->If nothing works and you start to think "who wrote - this pile of trash" then I suggest you do step 2 again (and - again) till you calm down.</P +NAME="AEN103" +>1.6. What If Things Don't Work?</A +></H2 ><P ->Then you might read the file DIAGNOSIS.txt and the +>Then you might read the file HOWTO chapter Diagnosis and the FAQ. If you are still stuck then try the mailing list or newsgroup (look in the README for details). Samba has been successfully installed at thousands of sites worldwide, so maybe someone else has hit your problem and has overcome it. You could also use the WWW site to scan back issues of the samba-digest.</P ><P ->When you fix the problem PLEASE send me some updates to the - documentation (or source code) so that the next person will find it - easier. </P -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN189" -></A ->1.10.1. Diagnosing Problems</H3 -><P ->If you have installation problems then go to the - <A -HREF="Diagnosis.html" -TARGET="_top" ->Diagnosis</A -> chapter to try to find the - problem.</P -></DIV +>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="AEN193" -></A ->1.10.2. Scope IDs</H3 +NAME="AEN108" +>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 + All your PCs will need to have the same setting for this to work. I do not recommend scope IDs.</P ></DIV ><DIV @@ -1971,71 +1634,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN196" -></A ->1.10.3. Choosing the Protocol Level</H3 -><P ->The SMB protocol has many dialects. Currently - Samba supports 5, called CORE, COREPLUS, LANMAN1, - LANMAN2 and NT1.</P -><P ->You can choose what maximum protocol to support - in the <TT -CLASS="FILENAME" ->smb.conf</TT -> file. The default is - NT1 and that is the best for the vast majority of sites.</P -><P ->In older versions of Samba you may have found it - necessary to use COREPLUS. The limitations that led to - this have mostly been fixed. It is now less likely that you - will want to use less than LANMAN1. The only remaining advantage - of COREPLUS is that for some obscure reason WfWg preserves - the case of passwords in this protocol, whereas under LANMAN1, - LANMAN2 or NT1 it uppercases all passwords before sending them, - forcing you to use the "password level=" option in some cases.</P -><P ->The main advantage of LANMAN2 and NT1 is support for - long filenames with some clients (eg: smbclient, Windows NT - or Win95). </P -><P ->See the smb.conf(5) manual page for more details.</P -><P ->Note: To support print queue reporting you may find - that you have to use TCP/IP as the default protocol under - WfWg. For some reason if you leave Netbeui as the default - it may break the print queue reporting on some systems. - It is presumably a WfWg bug.</P -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN205" -></A ->1.10.4. Printing from UNIX to a Client PC</H3 -><P ->To use a printer that is available via a smb-based - server from a unix host with LPR you will need to compile the - smbclient program. You then need to install the script - "smbprint". Read the instruction in smbprint for more details. - </P -><P ->There is also a SYSV style script that does much - the same thing called smbprint.sysv. It contains instructions.</P -><P ->See the CUPS manual for information about setting up - printing from a unix host with CUPS to a smb-based server. </P -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN210" -></A ->1.10.5. Locking</H3 +NAME="AEN111" +>1.6.2. Locking</A +></H3 ><P >One area which sometimes causes trouble is locking.</P ><P @@ -2088,19 +1689,6 @@ NAME="AEN210" or DENY_ALL. There are also special compatibility modes called DENY_FCB and DENY_DOS.</P ></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN219" -></A ->1.10.6. Mapping Usernames</H3 -><P ->If you have different usernames on the PCs and - the unix server then take a look at the "username map" option. - See the smb.conf man page for details.</P -></DIV ></DIV ></DIV ><DIV @@ -2116,21 +1704,24 @@ 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 +><P +>Note: 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 ><DIV CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN230" -></A ->2.1. Discussion</H2 +NAME="AEN130" +>2.1. Discussion</A +></H2 ><P >Firstly, all MS Windows networking is based on SMB (Server Message -Block) based messaging. SMB messaging is implemented using NetBIOS. Samba -implements NetBIOS by encapsulating it over TCP/IP. MS Windows products can -do likewise. NetBIOS based networking uses broadcast messaging to affect -browse list management. When running NetBIOS over TCP/IP this uses UDP -based messaging. UDP messages can be broadcast or unicast.</P +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 "remote announce" parameter to smb.conf helps to project browse announcements @@ -2144,18 +1735,23 @@ segment is configured with it's own Samba WINS server, then the only way to get cross segment browsing to work is by using the "remote announce" and the "remote browse sync" parameters to your smb.conf file.</P ><P ->If only one WINS server is used then the use of the "remote announce" and the -"remote browse sync" parameters should NOT be necessary.</P +>If only one WINS server is used for an entire multi-segment network 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 +>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 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 @@ -2167,9 +1763,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN238" -></A ->2.2. Use of the "Remote Announce" parameter</H2 +NAME="AEN139" +>2.2. Use of the "Remote Announce" parameter</A +></H2 ><P >The "remote announce" parameter of smb.conf can be used to forcibly ensure that all the NetBIOS names on a network get announced to a remote network. @@ -2225,9 +1821,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN252" -></A ->2.3. Use of the "Remote Browse Sync" parameter</H2 +NAME="AEN153" +>2.3. Use of the "Remote Browse Sync" parameter</A +></H2 ><P >The "remote browse sync" parameter of smb.conf is used to announce to another LMB that it must synchronise it's NetBIOS name list with our @@ -2248,9 +1844,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN257" -></A ->2.4. Use of WINS</H2 +NAME="AEN158" +>2.4. 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 @@ -2302,22 +1898,23 @@ CLASS="emphasis" 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 +> use both "wins support = yes" together +with "wins server = a.b.c.d" particularly not using it's own IP address. +Specifying both will cause nmbd to refuse to start!</P ></DIV ><DIV CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN268" -></A ->2.5. Do NOT use more than one (1) protocol on MS Windows machines</H2 +NAME="AEN169" +>2.5. 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 take part in a process of electing the LMB (and DMB) +>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 @@ -2333,6 +1930,19 @@ 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 @@ -2340,9 +1950,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN274" -></A ->2.6. Name Resolution Order</H2 +NAME="AEN177" +>2.6. 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 @@ -2431,9 +2041,9 @@ CLASS="SECT1" ><H2 CLASS="SECT1" ><A -NAME="AEN324" -></A ->3.1. Introduction</H2 +NAME="AEN227" +>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 @@ -2472,9 +2082,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN331" -></A ->3.2. Important Notes About Security</H2 +NAME="AEN234" +>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 @@ -2580,9 +2190,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN346" -></A ->3.2.1. Advantages of SMB Encryption</H3 +NAME="AEN249" +>3.2.1. Advantages of SMB Encryption</A +></H3 ><P ></P ><TABLE @@ -2614,9 +2224,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN351" -></A ->3.2.2. Advantages of non-encrypted passwords</H3 +NAME="AEN254" +>3.2.2. Advantages of non-encrypted passwords</A +></H3 ><P ></P ><TABLE @@ -2650,9 +2260,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN357" -></A ->3.3. The smbpasswd Command</H2 +NAME="AEN260" +>3.3. The smbpasswd Command</A +></H2 ><P >The smbpasswd utility is a utility similar to the <B @@ -2682,47 +2292,39 @@ CLASS="COMMAND" ><P >To run smbpasswd as a normal user just type :</P ><P -><TT +><SAMP CLASS="PROMPT" ->$ </TT -><TT +>$ </SAMP +><KBD CLASS="USERINPUT" -><B ->smbpasswd</B -></TT +>smbpasswd</KBD ></P ><P -><TT +><SAMP CLASS="PROMPT" ->Old SMB password: </TT -><TT +>Old SMB password: </SAMP +><KBD CLASS="USERINPUT" -><B -><type old value here - - or hit return if there was no old password></B -></TT +><type old value here - + or hit return if there was no old password></KBD ></P ><P -><TT +><SAMP CLASS="PROMPT" ->New SMB Password: </TT -><TT +>New SMB Password: </SAMP +><KBD CLASS="USERINPUT" -><B -><type new value> - </B -></TT +><type new value> + </KBD ></P ><P -><TT +><SAMP CLASS="PROMPT" ->Repeat New SMB Password: </TT -><TT +>Repeat New SMB Password: </SAMP +><KBD CLASS="USERINPUT" -><B -><re-type new value - </B -></TT +><re-type new value + </KBD ></P ><P >If the old value does not match the current value stored for @@ -2762,9 +2364,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN388" -></A ->3.4. Plain text</H2 +NAME="AEN291" +>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 @@ -2782,9 +2384,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN393" -></A ->3.5. TDB</H2 +NAME="AEN296" +>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 @@ -2795,17 +2397,17 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN396" -></A ->3.6. LDAP</H2 +NAME="AEN299" +>3.6. LDAP</A +></H2 ><DIV CLASS="SECT2" ><H3 CLASS="SECT2" ><A -NAME="AEN398" -></A ->3.6.1. Introduction</H3 +NAME="AEN301" +>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 @@ -2871,9 +2473,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN418" -></A ->3.6.2. Introduction</H3 +NAME="AEN321" +>3.6.2. Introduction</A +></H3 ><P >Traditionally, when configuring <A HREF="smb.conf.5.html#ENCRYPTPASSWORDS" @@ -2928,35 +2530,27 @@ 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. <TT +for a samdb backend (e.g. <VAR CLASS="PARAMETER" -><I ->--with-ldapsam</I -></TT +>--with-ldapsam</VAR > or -<TT +<VAR CLASS="PARAMETER" -><I ->--with-tdbsam</I -></TT +>--with-tdbsam</VAR >) requires compile time support.</P ><P ->When compiling Samba to include the <TT +>When compiling Samba to include the <VAR CLASS="PARAMETER" -><I ->--with-ldapsam</I -></TT +>--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 <TT +>There are a few points to stress about what the <VAR CLASS="PARAMETER" -><I ->--with-ldapsam</I -></TT +>--with-ldapsam</VAR > does not provide. The LDAP support referred to in the this documentation does not include:</P @@ -2988,9 +2582,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN447" -></A ->3.6.3. Supported LDAP Servers</H3 +NAME="AEN350" +>3.6.3. Supported LDAP Servers</A +></H3 ><P >The LDAP samdb code in 2.2.3 has been developed and tested using the OpenLDAP 2.0 server and client libraries. The same code should be able to work with @@ -3013,9 +2607,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN452" -></A ->3.6.4. Schema and Relationship to the RFC 2307 posixAccount</H3 +NAME="AEN355" +>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 @@ -3049,9 +2643,9 @@ CLASS="FILENAME" >/etc/passwd</TT > entry, so is the sambaAccount object meant to supplement the UNIX user account information. A sambaAccount is a -<TT +<CODE CLASS="CONSTANT" ->STRUCTURAL</TT +>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 @@ -3070,24 +2664,24 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN464" -></A ->3.6.5. Configuring Samba with LDAP</H3 +NAME="AEN367" +>3.6.5. Configuring Samba with LDAP</A +></H3 ><DIV CLASS="SECT3" ><H4 CLASS="SECT3" ><A -NAME="AEN466" -></A ->3.6.5.1. OpenLDAP configuration</H4 +NAME="AEN369" +>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 -><TT +><SAMP CLASS="PROMPT" ->root# </TT +>root# </SAMP ><B CLASS="COMMAND" >cp samba.schema /etc/openldap/schema/</B @@ -3160,15 +2754,13 @@ CLASS="SECT3" ><HR><H4 CLASS="SECT3" ><A -NAME="AEN483" -></A ->3.6.5.2. Configuring Samba</H4 +NAME="AEN386" +>3.6.5.2. Configuring Samba</A +></H4 ><P ->The following parameters are available in smb.conf only with <TT +>The following parameters are available in smb.conf only with <VAR CLASS="PARAMETER" -><I ->--with-ldapsam</I -></TT +>--with-ldapsam</VAR > was included with compiling Samba.</P ><P @@ -3246,11 +2838,9 @@ 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 <TT + # must be set by using 'smbpasswd -w <VAR CLASS="REPLACEABLE" -><I ->secretpw</I -></TT +>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. @@ -3271,7 +2861,7 @@ 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 @@ -3280,9 +2870,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN511" -></A ->3.6.6. Accounts and Groups management</H3 +NAME="AEN414" +>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 @@ -3305,9 +2895,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN516" -></A ->3.6.7. Security and sambaAccount</H3 +NAME="AEN419" +>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 @@ -3384,9 +2974,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN536" -></A ->3.6.8. LDAP specials attributes for sambaAccounts</H3 +NAME="AEN439" +>3.6.8. LDAP specials attributes for sambaAccounts</A +></H3 ><P >The sambaAccount objectclass is composed of the following attributes:</P ><P @@ -3394,84 +2984,84 @@ NAME="AEN536" ><UL ><LI ><P -><TT +><CODE CLASS="CONSTANT" ->lmPassword</TT +>lmPassword</CODE >: the LANMAN password 16-byte hash stored as a character representation of a hexidecimal string.</P ></LI ><LI ><P -><TT +><CODE CLASS="CONSTANT" ->ntPassword</TT +>ntPassword</CODE >: the NT password hash 16-byte stored as a character representation of a hexidecimal string.</P ></LI ><LI ><P -><TT +><CODE CLASS="CONSTANT" ->pwdLastSet</TT +>pwdLastSet</CODE >: The integer time in seconds since 1970 when the - <TT + <CODE CLASS="CONSTANT" ->lmPassword</TT -> and <TT +>lmPassword</CODE +> and <CODE CLASS="CONSTANT" ->ntPassword</TT +>ntPassword</CODE > attributes were last set. </P ></LI ><LI ><P -><TT +><CODE CLASS="CONSTANT" ->acctFlags</TT +>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 -><TT +><CODE CLASS="CONSTANT" ->logonTime</TT +>logonTime</CODE >: Integer value currently unused</P ></LI ><LI ><P -><TT +><CODE CLASS="CONSTANT" ->logoffTime</TT +>logoffTime</CODE >: Integer value currently unused</P ></LI ><LI ><P -><TT +><CODE CLASS="CONSTANT" ->kickoffTime</TT +>kickoffTime</CODE >: Integer value currently unused</P ></LI ><LI ><P -><TT +><CODE CLASS="CONSTANT" ->pwdCanChange</TT +>pwdCanChange</CODE >: Integer value currently unused</P ></LI ><LI ><P -><TT +><CODE CLASS="CONSTANT" ->pwdMustChange</TT +>pwdMustChange</CODE >: Integer value currently unused</P ></LI ><LI ><P -><TT +><CODE CLASS="CONSTANT" ->homeDrive</TT +>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 @@ -3479,9 +3069,9 @@ CLASS="CONSTANT" ></LI ><LI ><P -><TT +><CODE CLASS="CONSTANT" ->scriptPath</TT +>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 @@ -3489,18 +3079,18 @@ CLASS="CONSTANT" ></LI ><LI ><P -><TT +><CODE CLASS="CONSTANT" ->profilePath</TT +>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 -><TT +><CODE CLASS="CONSTANT" ->smbHome</TT +>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 @@ -3510,25 +3100,25 @@ CLASS="CONSTANT" ></LI ><LI ><P -><TT +><CODE CLASS="CONSTANT" ->userWorkstation</TT +>userWorkstation</CODE >: character string value currently unused. </P ></LI ><LI ><P -><TT +><CODE CLASS="CONSTANT" ->rid</TT +>rid</CODE >: the integer representation of the user's relative identifier (RID).</P ></LI ><LI ><P -><TT +><CODE CLASS="CONSTANT" ->primaryGroupID</TT +>primaryGroupID</CODE >: the relative identifier (RID) of the primary group of the user.</P ></LI @@ -3573,19 +3163,15 @@ its <TT CLASS="FILENAME" >smb.conf</TT > file. When a user named "becky" logons to the domain, -the <TT +the <VAR CLASS="PARAMETER" -><I ->logon home</I -></TT +>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 <TT +of the <VAR CLASS="PARAMETER" -><I ->logon home</I -></TT +>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 @@ -3595,9 +3181,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN606" -></A ->3.6.9. Example LDIF Entries for a sambaAccount</H3 +NAME="AEN509" +>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 @@ -3654,17 +3240,17 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN614" -></A ->3.7. MySQL</H2 +NAME="AEN517" +>3.7. MySQL</A +></H2 ><DIV CLASS="SECT2" ><H3 CLASS="SECT2" ><A -NAME="AEN616" -></A ->3.7.1. Building</H3 +NAME="AEN519" +>3.7.1. Building</A +></H3 ><P >To build the plugin, run <B CLASS="COMMAND" @@ -3683,9 +3269,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN622" -></A ->3.7.2. Creating the database</H3 +NAME="AEN525" +>3.7.2. 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 @@ -3696,26 +3282,18 @@ contains the correct queries to create the required tables. Use the command : <B CLASS="COMMAND" ->mysql -u<TT +>mysql -u<VAR CLASS="REPLACEABLE" -><I ->username</I -></TT -> -h<TT +>username</VAR +> -h<VAR CLASS="REPLACEABLE" -><I ->hostname</I -></TT -> -p<TT +>hostname</VAR +> -p<VAR CLASS="REPLACEABLE" -><I ->password</I -></TT -> <TT +>password</VAR +> <VAR CLASS="REPLACEABLE" -><I ->databasename</I -></TT +>databasename</VAR > < <TT CLASS="FILENAME" >/path/to/samba/examples/pdb/mysql/mysql.dump</TT @@ -3727,9 +3305,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN632" -></A ->3.7.3. Configuring</H3 +NAME="AEN535" +>3.7.3. Configuring</A +></H3 ><P >This plugin lacks some good documentation, but here is some short info:</P ><P @@ -3838,9 +3416,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN649" -></A ->3.7.4. Using plaintext passwords or encrypted password</H3 +NAME="AEN552" +>3.7.4. Using plaintext passwords or encrypted password</A +></H3 ><P >I strongly discourage the use of plaintext passwords, however, you can use them:</P ><P @@ -3853,9 +3431,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN654" -></A ->3.7.5. Getting non-column data from the table</H3 +NAME="AEN557" +>3.7.5. 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 @@ -3879,17 +3457,17 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN662" -></A ->3.8. Passdb XML plugin</H2 +NAME="AEN565" +>3.8. Passdb XML plugin</A +></H2 ><DIV CLASS="SECT2" ><H3 CLASS="SECT2" ><A -NAME="AEN664" -></A ->3.8.1. Building</H3 +NAME="AEN567" +>3.8.1. Building</A +></H3 ><P >This module requires libxml2 to be installed.</P ><P @@ -3907,9 +3485,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN670" -></A ->3.8.2. Usage</H3 +NAME="AEN573" +>3.8.2. Usage</A +></H3 ><P >The usage of pdb_xml is pretty straightforward. To export data, use: @@ -3944,7 +3522,7 @@ CLASS="TITLE" ><DIV CLASS="PARTINTRO" ><A -NAME="AEN678" +NAME="AEN581" ></A ><H1 >Introduction</H1 @@ -3973,22 +3551,22 @@ HREF="#SAMBA-PDC" ><DL ><DT >5.1. <A -HREF="#AEN722" +HREF="#AEN625" >Prerequisite Reading</A ></DT ><DT >5.2. <A -HREF="#AEN728" +HREF="#AEN631" >Background</A ></DT ><DT >5.3. <A -HREF="#AEN767" +HREF="#AEN670" >Configuring the Samba Domain Controller</A ></DT ><DT >5.4. <A -HREF="#AEN810" +HREF="#AEN713" >Creating Machine Trust Accounts and Joining Clients to the Domain</A ></DT @@ -3996,59 +3574,59 @@ Domain</A ><DL ><DT >5.4.1. <A -HREF="#AEN829" +HREF="#AEN732" >Manual Creation of Machine Trust Accounts</A ></DT ><DT >5.4.2. <A -HREF="#AEN870" +HREF="#AEN773" >"On-the-Fly" Creation of Machine Trust Accounts</A ></DT ><DT >5.4.3. <A -HREF="#AEN879" +HREF="#AEN782" >Joining the Client to the Domain</A ></DT ></DL ></DD ><DT >5.5. <A -HREF="#AEN894" +HREF="#AEN797" >Common Problems and Errors</A ></DT ><DT >5.6. <A -HREF="#AEN942" +HREF="#AEN845" >System Policies and Profiles</A ></DT ><DT >5.7. <A -HREF="#AEN986" +HREF="#AEN889" >What other help can I get?</A ></DT ><DT >5.8. <A -HREF="#AEN1100" +HREF="#AEN1003" >Domain Control for Windows 9x/ME</A ></DT ><DD ><DL ><DT >5.8.1. <A -HREF="#AEN1126" +HREF="#AEN1029" >Configuration Instructions: Network Logons</A ></DT ><DT >5.8.2. <A -HREF="#AEN1145" +HREF="#AEN1048" >Configuration Instructions: Setting up Roaming User Profiles</A ></DT ></DL ></DD ><DT >5.9. <A -HREF="#AEN1238" ->DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba</A +HREF="#AEN1141" +>DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba</A ></DT ></DL ></DD @@ -4061,53 +3639,53 @@ HREF="#SAMBA-BDC" ><DL ><DT >6.1. <A -HREF="#AEN1274" +HREF="#AEN1177" >Prerequisite Reading</A ></DT ><DT >6.2. <A -HREF="#AEN1278" +HREF="#AEN1181" >Background</A ></DT ><DT >6.3. <A -HREF="#AEN1286" +HREF="#AEN1189" >What qualifies a Domain Controller on the network?</A ></DT ><DD ><DL ><DT >6.3.1. <A -HREF="#AEN1289" +HREF="#AEN1192" >How does a Workstation find its domain controller?</A ></DT ><DT >6.3.2. <A -HREF="#AEN1292" +HREF="#AEN1195" >When is the PDC needed?</A ></DT ></DL ></DD ><DT >6.4. <A -HREF="#AEN1295" +HREF="#AEN1198" >Can Samba be a Backup Domain Controller to an NT PDC?</A ></DT ><DT >6.5. <A -HREF="#AEN1300" +HREF="#AEN1203" >How do I set up a Samba BDC?</A ></DT ><DD ><DL ><DT >6.5.1. <A -HREF="#AEN1317" +HREF="#AEN1220" >How do I replicate the smbpasswd file?</A ></DT ><DT >6.5.2. <A -HREF="#AEN1321" +HREF="#AEN1224" >Can I do this all with LDAP?</A ></DT ></DL @@ -4123,51 +3701,51 @@ HREF="#ADS" ><DL ><DT >7.1. <A -HREF="#AEN1339" +HREF="#AEN1242" >Installing the required packages for Debian</A ></DT ><DT >7.2. <A -HREF="#AEN1346" +HREF="#AEN1249" >Installing the required packages for RedHat</A ></DT ><DT >7.3. <A -HREF="#AEN1356" +HREF="#AEN1259" >Compile Samba</A ></DT ><DT >7.4. <A -HREF="#AEN1371" +HREF="#AEN1274" >Setup your /etc/krb5.conf</A ></DT ><DT >7.5. <A -HREF="#AEN1381" +HREF="#AEN1284" >Create the computer account</A ></DT ><DD ><DL ><DT >7.5.1. <A -HREF="#AEN1385" +HREF="#AEN1288" >Possible errors</A ></DT ></DL ></DD ><DT >7.6. <A -HREF="#AEN1393" +HREF="#AEN1296" >Test your server setup</A ></DT ><DT >7.7. <A -HREF="#AEN1398" +HREF="#AEN1301" >Testing with smbclient</A ></DT ><DT >7.8. <A -HREF="#AEN1401" +HREF="#AEN1304" >Notes</A ></DT ></DL @@ -4181,17 +3759,17 @@ HREF="#DOMAIN-SECURITY" ><DL ><DT >8.1. <A -HREF="#AEN1423" +HREF="#AEN1326" >Joining an NT Domain with Samba 3.0</A ></DT ><DT >8.2. <A -HREF="#AEN1478" +HREF="#AEN1381" >Samba and Windows 2000 Domains</A ></DT ><DT >8.3. <A -HREF="#AEN1481" +HREF="#AEN1384" >Why is this better than security = server?</A ></DT ></DL @@ -4311,9 +3889,9 @@ CLASS="SECT1" ><H2 CLASS="SECT1" ><A -NAME="AEN722" -></A ->5.1. Prerequisite Reading</H2 +NAME="AEN625" +>5.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 @@ -4339,9 +3917,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN728" -></A ->5.2. Background</H2 +NAME="AEN631" +>5.2. Background</A +></H2 ><DIV CLASS="NOTE" ><P @@ -4491,9 +4069,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN767" -></A ->5.3. Configuring the Samba Domain Controller</H2 +NAME="AEN670" +>5.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. I will not @@ -4519,21 +4097,17 @@ CLASS="PROGRAMLISTING" HREF="smb.conf.5.html#NETBIOSNAME" TARGET="_top" >netbios name</A -> = <TT +> = <VAR CLASS="REPLACEABLE" -><I ->POGO</I -></TT +>POGO</VAR > <A HREF="smb.conf.5.html#WORKGROUP" TARGET="_top" >workgroup</A -> = <TT +> = <VAR CLASS="REPLACEABLE" -><I ->NARNIA</I -></TT +>NARNIA</VAR > ; we should act as the domain and local master browser @@ -4623,11 +4197,9 @@ TARGET="_top" HREF="smb.conf.5.html#WRITELIST" TARGET="_top" >write list</A -> = <TT +> = <VAR CLASS="REPLACEABLE" -><I ->ntadmin</I -></TT +>ntadmin</VAR > ; share for storing user profiles @@ -4703,10 +4275,10 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN810" -></A +NAME="AEN713" >5.4. Creating Machine Trust Accounts and Joining Clients to the -Domain</H2 +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 @@ -4777,9 +4349,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN829" -></A ->5.4.1. Manual Creation of Machine Trust Accounts</H3 +NAME="AEN732" +>5.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 @@ -4794,55 +4366,45 @@ CLASS="COMMAND" used to create new Unix accounts. The following is an example for a Linux based Samba server:</P ><P -> <TT +> <SAMP CLASS="PROMPT" ->root# </TT +>root# </SAMP ><B CLASS="COMMAND" ->/usr/sbin/useradd -g 100 -d /dev/null -c <TT +>/usr/sbin/useradd -g 100 -d /dev/null -c <VAR CLASS="REPLACEABLE" -><I >"machine -nickname"</I -></TT -> -s /bin/false <TT +nickname"</VAR +> -s /bin/false <VAR CLASS="REPLACEABLE" -><I ->machine_name</I -></TT +>machine_name</VAR >$ </B ></P ><P -><TT +><SAMP CLASS="PROMPT" ->root# </TT +>root# </SAMP ><B CLASS="COMMAND" ->passwd -l <TT +>passwd -l <VAR CLASS="REPLACEABLE" -><I ->machine_name</I -></TT +>machine_name</VAR >$</B ></P ><P >On *BSD systems, this can be done using the 'chpass' utility:</P ><P -><TT +><SAMP CLASS="PROMPT" ->root# </TT +>root# </SAMP ><B CLASS="COMMAND" ->chpass -a "<TT +>chpass -a "<VAR CLASS="REPLACEABLE" -><I ->machine_name</I -></TT ->$:*:101:100::0:0:Workstation <TT +>machine_name</VAR +>$:*:101:100::0:0:Workstation <VAR CLASS="REPLACEABLE" -><I ->machine_name</I -></TT +>machine_name</VAR >:/dev/null:/sbin/nologin"</B ></P ><P @@ -4859,26 +4421,20 @@ CLASS="FILENAME" ><P ><PRE CLASS="PROGRAMLISTING" ->doppy$:x:505:501:<TT +>doppy$:x:505:501:<VAR CLASS="REPLACEABLE" -><I ->machine_nickname</I -></TT +>machine_nickname</VAR >:/dev/null:/bin/false</PRE ></P ><P ->Above, <TT +>Above, <VAR CLASS="REPLACEABLE" -><I ->machine_nickname</I -></TT +>machine_nickname</VAR > can be any descriptive name for the client, i.e., BasementComputer. -<TT +<VAR CLASS="REPLACEABLE" -><I ->machine_name</I -></TT +>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 @@ -4896,24 +4452,20 @@ CLASS="COMMAND" > command as shown here:</P ><P -><TT +><SAMP CLASS="PROMPT" ->root# </TT +>root# </SAMP ><B CLASS="COMMAND" ->smbpasswd -a -m <TT +>smbpasswd -a -m <VAR CLASS="REPLACEABLE" -><I ->machine_name</I -></TT +>machine_name</VAR ></B ></P ><P ->where <TT +>where <VAR CLASS="REPLACEABLE" -><I ->machine_name</I -></TT +>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 @@ -4967,9 +4519,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN870" -></A ->5.4.2. "On-the-Fly" Creation of Machine Trust Accounts</H3 +NAME="AEN773" +>5.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 @@ -4995,7 +4547,7 @@ be created manually.</P ><PRE CLASS="PROGRAMLISTING" >[global] - # <...remainder of parameters...> + # <...remainder of parameters...> add user script = /usr/sbin/useradd -d /dev/null -g 100 -s /bin/false -M %u </PRE ></P ></DIV @@ -5004,9 +4556,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN879" -></A ->5.4.3. Joining the Client to the Domain</H3 +NAME="AEN782" +>5.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 @@ -5072,9 +4624,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN894" -></A ->5.5. Common Problems and Errors</H2 +NAME="AEN797" +>5.5. Common Problems and Errors</A +></H2 ><P ></P ><P @@ -5128,9 +4680,9 @@ CLASS="EMPHASIS" will remove all network drive connections: </P ><P -> <TT +> <SAMP CLASS="PROMPT" ->C:\WINNT\></TT +>C:\WINNT\></SAMP > <B CLASS="COMMAND" >net use * /d</B @@ -5193,11 +4745,9 @@ CLASS="EMPHASIS" </P ><P > This problem is caused by the PDC not having a suitable machine trust account. - If you are using the <TT + If you are using the <VAR CLASS="PARAMETER" -><I ->add user script</I -></TT +>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. @@ -5241,11 +4791,9 @@ CLASS="COMMAND" </P ><P > In order to work around this problem in 2.2.0, configure the - <TT + <VAR CLASS="PARAMETER" -><I ->account</I -></TT +>account</VAR > control flag in <TT CLASS="FILENAME" @@ -5282,9 +4830,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN942" -></A ->5.6. System Policies and Profiles</H2 +NAME="AEN845" +>5.6. System Policies and Profiles</A +></H2 ><P >Much of the information necessary to implement System Policies and Roving User Profiles in a Samba domain is the same as that for @@ -5459,9 +5007,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN986" -></A ->5.7. What other help can I get?</H2 +NAME="AEN889" +>5.7. 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 @@ -5879,9 +5427,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN1100" -></A ->5.8. Domain Control for Windows 9x/ME</H2 +NAME="AEN1003" +>5.8. Domain Control for Windows 9x/ME</A +></H2 ><DIV CLASS="NOTE" ><P @@ -5958,7 +5506,7 @@ TYPE="1" ><LI ><P > The client broadcasts (to the IP broadcast address of the subnet it is in) - a NetLogon request. This is sent to the NetBIOS name DOMAIN<1c> at the + a NetLogon request. This is sent to the NetBIOS name DOMAIN<1c> at the NetBIOS layer. The client chooses the first response it receives, which contains the NetBIOS name of the logon server to use in the format of \\SERVER. @@ -6013,9 +5561,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN1126" -></A ->5.8.1. Configuration Instructions: Network Logons</H3 +NAME="AEN1029" +>5.8.1. Configuration Instructions: Network Logons</A +></H3 ><P >The main difference between a PDC and a Windows 9x logon server configuration is that</P @@ -6068,20 +5616,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 <TT +modes other than <CODE CLASS="CONSTANT" ->USER</TT +>USER</CODE >. The only security mode -which will not work due to technical reasons is <TT +which will not work due to technical reasons is <CODE CLASS="CONSTANT" ->SHARE</TT +>SHARE</CODE > -mode security. <TT +mode security. <CODE CLASS="CONSTANT" ->DOMAIN</TT -> and <TT +>DOMAIN</CODE +> and <CODE CLASS="CONSTANT" ->SERVER</TT +>SERVER</CODE > mode security is really just a variation on SMB user level security.</P ><P @@ -6119,9 +5667,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN1145" -></A ->5.8.2. Configuration Instructions: Setting up Roaming User Profiles</H3 +NAME="AEN1048" +>5.8.2. Configuration Instructions: Setting up Roaming User Profiles</A +></H3 ><DIV CLASS="WARNING" ><P @@ -6172,9 +5720,9 @@ CLASS="SECT3" ><HR><H4 CLASS="SECT3" ><A -NAME="AEN1153" -></A ->5.8.2.1. Windows NT Configuration</H4 +NAME="AEN1056" +>5.8.2.1. Windows NT Configuration</A +></H4 ><P >To support WinNT clients, in the [global] section of smb.conf set the following (for example):</P @@ -6223,9 +5771,9 @@ CLASS="SECT3" ><HR><H4 CLASS="SECT3" ><A -NAME="AEN1161" -></A ->5.8.2.2. Windows 9X Configuration</H4 +NAME="AEN1064" +>5.8.2.2. Windows 9X Configuration</A +></H4 ><P >To support Win9X clients, you must use the "logon home" parameter. Samba has now been fixed so that "net use/home" now works as well, and it, too, relies @@ -6254,9 +5802,9 @@ CLASS="SECT3" ><HR><H4 CLASS="SECT3" ><A -NAME="AEN1169" -></A ->5.8.2.3. Win9X and WinNT Configuration</H4 +NAME="AEN1072" +>5.8.2.3. Win9X and WinNT Configuration</A +></H4 ><P >You can support profiles for both Win9X and WinNT clients by setting both the "logon home" and "logon path" parameters. For example:</P @@ -6299,9 +5847,9 @@ CLASS="SECT3" ><HR><H4 CLASS="SECT3" ><A -NAME="AEN1176" -></A ->5.8.2.4. Windows 9X Profile Setup</H4 +NAME="AEN1079" +>5.8.2.4. Windows 9X 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". @@ -6459,9 +6007,9 @@ CLASS="SECT3" ><HR><H4 CLASS="SECT3" ><A -NAME="AEN1212" -></A ->5.8.2.5. Windows NT Workstation 4.0</H4 +NAME="AEN1115" +>5.8.2.5. Windows NT Workstation 4.0</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 @@ -6573,9 +6121,9 @@ CLASS="SECT3" ><HR><H4 CLASS="SECT3" ><A -NAME="AEN1225" -></A ->5.8.2.6. Windows NT Server</H4 +NAME="AEN1128" +>5.8.2.6. Windows NT Server</A +></H4 ><P >There is nothing to stop you specifying any path that you like for the location of users' profiles. Therefore, you could specify that the @@ -6587,9 +6135,9 @@ CLASS="SECT3" ><HR><H4 CLASS="SECT3" ><A -NAME="AEN1228" -></A ->5.8.2.7. Sharing Profiles between W95 and NT Workstation 4.0</H4 +NAME="AEN1131" +>5.8.2.7. Sharing Profiles between W95 and NT Workstation 4.0</A +></H4 ><DIV CLASS="WARNING" ><P @@ -6680,9 +6228,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN1238" -></A ->5.9. DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba</H2 +NAME="AEN1141" +>5.9. DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba</A +></H2 ><DIV CLASS="WARNING" ><P @@ -6757,16 +6305,16 @@ may need to know to interact with the rest of the system.</P >The registry files can be located on any Windows NT machine by opening a command prompt and typing:</P ><P -><TT +><SAMP CLASS="PROMPT" ->C:\WINNT\></TT +>C:\WINNT\></SAMP > dir %SystemRoot%\System32\config</P ><P >The environment variable %SystemRoot% value can be obtained by typing:</P ><P -><TT +><SAMP CLASS="PROMPT" ->C:\WINNT></TT +>C:\WINNT></SAMP >echo %SystemRoot%</P ><P >The active parts of the registry that you may want to be familiar with are @@ -6825,9 +6373,9 @@ CLASS="SECT1" ><H2 CLASS="SECT1" ><A -NAME="AEN1274" -></A ->6.1. Prerequisite Reading</H2 +NAME="AEN1177" +>6.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 @@ -6842,9 +6390,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN1278" -></A ->6.2. Background</H2 +NAME="AEN1181" +>6.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 @@ -6887,9 +6435,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN1286" -></A ->6.3. What qualifies a Domain Controller on the network?</H2 +NAME="AEN1189" +>6.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 @@ -6904,9 +6452,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN1289" -></A ->6.3.1. How does a Workstation find its domain controller?</H3 +NAME="AEN1192" +>6.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 @@ -6923,9 +6471,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN1292" -></A ->6.3.2. When is the PDC needed?</H3 +NAME="AEN1195" +>6.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 @@ -6939,9 +6487,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN1295" -></A ->6.4. Can Samba be a Backup Domain Controller to an NT PDC?</H2 +NAME="AEN1198" +>6.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 @@ -6962,9 +6510,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN1300" -></A ->6.5. How do I set up a Samba BDC?</H2 +NAME="AEN1203" +>6.5. How do I set up a Samba BDC?</A +></H2 ><P >Several things have to be done:</P ><P @@ -7029,9 +6577,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN1317" -></A ->6.5.1. How do I replicate the smbpasswd file?</H3 +NAME="AEN1220" +>6.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 @@ -7050,9 +6598,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN1321" -></A ->6.5.2. Can I do this all with LDAP?</H3 +NAME="AEN1224" +>6.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 @@ -7106,9 +6654,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN1339" -></A ->7.1. Installing the required packages for Debian</H2 +NAME="AEN1242" +>7.1. Installing the required packages for Debian</A +></H2 ><P >On Debian you need to install the following packages:</P ><P @@ -7136,9 +6684,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN1346" -></A ->7.2. Installing the required packages for RedHat</H2 +NAME="AEN1249" +>7.2. Installing the required packages for RedHat</A +></H2 ><P >On RedHat this means you should have at least: </P ><P @@ -7175,9 +6723,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN1356" -></A ->7.3. Compile Samba</H2 +NAME="AEN1259" +>7.3. Compile Samba</A +></H2 ><P >If your kerberos libraries are in a non-standard location then remember to add the configure option --with-krb5=DIR.</P @@ -7231,9 +6779,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN1371" -></A ->7.4. Setup your /etc/krb5.conf</H2 +NAME="AEN1274" +>7.4. Setup your /etc/krb5.conf</A +></H2 ><P >The minimal configuration for krb5.conf is:</P ><P @@ -7270,9 +6818,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN1381" -></A ->7.5. Create the computer account</H2 +NAME="AEN1284" +>7.5. Create the computer account</A +></H2 ><P >As a user that has write permission on the Samba private directory (usually root) run: @@ -7285,9 +6833,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN1385" -></A ->7.5.1. Possible errors</H3 +NAME="AEN1288" +>7.5.1. Possible errors</A +></H3 ><P ><P ></P @@ -7310,9 +6858,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN1393" -></A ->7.6. Test your server setup</H2 +NAME="AEN1296" +>7.6. Test your server setup</A +></H2 ><P >On a Windows 2000 client try <B CLASS="COMMAND" @@ -7330,9 +6878,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN1398" -></A ->7.7. Testing with smbclient</H2 +NAME="AEN1301" +>7.7. Testing with smbclient</A +></H2 ><P >On your Samba server try to login to a Win2000 server or your Samba server using smbclient and kerberos. Use smbclient as usual, but @@ -7343,9 +6891,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN1401" -></A ->7.8. Notes</H2 +NAME="AEN1304" +>7.8. Notes</A +></H2 ><P >You must change administrator password at least once after DC install, to create the right encoding types</P @@ -7366,30 +6914,30 @@ CLASS="SECT1" ><H2 CLASS="SECT1" ><A -NAME="AEN1423" -></A ->8.1. Joining an NT Domain with Samba 3.0</H2 +NAME="AEN1326" +>8.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 - <TT + <CODE CLASS="CONSTANT" ->SERV1</TT +>SERV1</CODE > and are joining an or Win2k NT domain called - <TT + <CODE CLASS="CONSTANT" ->DOM</TT +>DOM</CODE >, which has a PDC with a NetBIOS name - of <TT + of <CODE CLASS="CONSTANT" ->DOMPDC</TT +>DOMPDC</CODE > and two backup domain controllers - with NetBIOS names <TT + with NetBIOS names <CODE CLASS="CONSTANT" ->DOMBDC1</TT -> and <TT +>DOMBDC1</CODE +> and <CODE CLASS="CONSTANT" >DOMBDC2 - </TT + </CODE >.</P ><P >Firstly, you must edit your <A @@ -7405,11 +6953,9 @@ CLASS="FILENAME" >Change (or add) your <A HREF="smb.conf.5.html#SECURITY" TARGET="_top" -> <TT +> <VAR CLASS="PARAMETER" -><I ->security =</I -></TT +>security =</VAR ></A > line in the [global] section of your smb.conf to read:</P @@ -7427,11 +6973,9 @@ CLASS="COMMAND" >Next change the <A HREF="smb.conf.5.html#WORKGROUP" TARGET="_top" -><TT +><VAR CLASS="PARAMETER" -><I -> workgroup =</I -></TT +> workgroup =</VAR ></A > line in the [global] section to read: </P ><P @@ -7445,26 +6989,22 @@ CLASS="COMMAND" >You must also have the parameter <A HREF="smb.conf.5.html#ENCRYPTPASSWORDS" TARGET="_top" -> <TT +> <VAR CLASS="PARAMETER" -><I ->encrypt passwords</I -></TT +>encrypt passwords</VAR ></A -> set to <TT +> set to <CODE CLASS="CONSTANT" >yes - </TT + </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" -> <TT +> <VAR CLASS="PARAMETER" -><I ->password server =</I -></TT +>password server =</VAR ></A > line in the [global] section to read: </P @@ -7497,41 +7037,35 @@ CLASS="COMMAND" >In order to actually join the domain, you must run this command:</P ><P -><TT +><SAMP CLASS="PROMPT" ->root# </TT -><TT +>root# </SAMP +><KBD CLASS="USERINPUT" -><B >net join -S DOMPDC - -U<TT + -U<VAR CLASS="REPLACEABLE" -><I ->Administrator%password</I -></TT -></B -></TT +>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 <TT + is DOMPDC. The <VAR CLASS="REPLACEABLE" -><I ->Administrator%password</I -></TT +>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 -><TT +><SAMP CLASS="COMPUTEROUTPUT" ->Joined domain DOM.</TT +>Joined domain DOM.</SAMP > - or <TT + or <SAMP CLASS="COMPUTEROUTPUT" ->Joined 'SERV1' to realm 'MYREALM'</TT +>Joined 'SERV1' to realm 'MYREALM'</SAMP > </P ><P @@ -7568,9 +7102,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN1478" -></A ->8.2. Samba and Windows 2000 Domains</H2 +NAME="AEN1381" +>8.2. Samba and Windows 2000 Domains</A +></H2 ><P >Many people have asked regarding the state of Samba's ability to participate in a Windows 2000 Domain. Samba 3.0 is able to act as a member server of a Windows @@ -7582,16 +7116,16 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN1481" -></A ->8.3. Why is this better than security = server?</H2 +NAME="AEN1384" +>8.3. 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 <TT + to your server. This means that if domain user <CODE CLASS="CONSTANT" >DOM\fred - </TT + </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 @@ -7676,7 +7210,7 @@ CLASS="TITLE" ><DIV CLASS="PARTINTRO" ><A -NAME="AEN1499" +NAME="AEN1402" ></A ><H1 >Introduction</H1 @@ -7700,19 +7234,19 @@ HREF="#INTEGRATE-MS-NETWORKS" ><DL ><DT >9.1. <A -HREF="#AEN1513" +HREF="#AEN1416" >Agenda</A ></DT ><DT >9.2. <A -HREF="#AEN1535" +HREF="#AEN1438" >Name Resolution in a pure Unix/Linux world</A ></DT ><DD ><DL ><DT >9.2.1. <A -HREF="#AEN1551" +HREF="#AEN1454" ><TT CLASS="FILENAME" >/etc/hosts</TT @@ -7720,7 +7254,7 @@ CLASS="FILENAME" ></DT ><DT >9.2.2. <A -HREF="#AEN1567" +HREF="#AEN1470" ><TT CLASS="FILENAME" >/etc/resolv.conf</TT @@ -7728,7 +7262,7 @@ CLASS="FILENAME" ></DT ><DT >9.2.3. <A -HREF="#AEN1578" +HREF="#AEN1481" ><TT CLASS="FILENAME" >/etc/host.conf</TT @@ -7736,7 +7270,7 @@ CLASS="FILENAME" ></DT ><DT >9.2.4. <A -HREF="#AEN1586" +HREF="#AEN1489" ><TT CLASS="FILENAME" >/etc/nsswitch.conf</TT @@ -7746,47 +7280,47 @@ CLASS="FILENAME" ></DD ><DT >9.3. <A -HREF="#AEN1598" +HREF="#AEN1501" >Name resolution as used within MS Windows networking</A ></DT ><DD ><DL ><DT >9.3.1. <A -HREF="#AEN1610" +HREF="#AEN1513" >The NetBIOS Name Cache</A ></DT ><DT >9.3.2. <A -HREF="#AEN1615" +HREF="#AEN1518" >The LMHOSTS file</A ></DT ><DT >9.3.3. <A -HREF="#AEN1623" +HREF="#AEN1526" >HOSTS file</A ></DT ><DT >9.3.4. <A -HREF="#AEN1628" +HREF="#AEN1531" >DNS Lookup</A ></DT ><DT >9.3.5. <A -HREF="#AEN1631" +HREF="#AEN1534" >WINS Lookup</A ></DT ></DL ></DD ><DT >9.4. <A -HREF="#AEN1643" +HREF="#AEN1546" >How browsing functions and how to deploy stable and dependable browsing using Samba</A ></DT ><DT >9.5. <A -HREF="#AEN1653" +HREF="#AEN1556" >MS Windows security options and how to configure Samba for seemless integration</A ></DT @@ -7794,24 +7328,24 @@ Samba for seemless integration</A ><DL ><DT >9.5.1. <A -HREF="#AEN1681" +HREF="#AEN1584" >Use MS Windows NT as an authentication server</A ></DT ><DT >9.5.2. <A -HREF="#AEN1689" +HREF="#AEN1592" >Make Samba a member of an MS Windows NT security domain</A ></DT ><DT >9.5.3. <A -HREF="#AEN1706" +HREF="#AEN1609" >Configure Samba as an authentication server</A ></DT ></DL ></DD ><DT >9.6. <A -HREF="#AEN1723" +HREF="#AEN1626" >Conclusions</A ></DT ></DL @@ -7825,53 +7359,53 @@ HREF="#UNIX-PERMISSIONS" ><DL ><DT >10.1. <A -HREF="#AEN1744" +HREF="#AEN1647" >Viewing and changing UNIX permissions using the NT security dialogs</A ></DT ><DT >10.2. <A -HREF="#AEN1748" +HREF="#AEN1651" >How to view file security on a Samba share</A ></DT ><DT >10.3. <A -HREF="#AEN1759" +HREF="#AEN1662" >Viewing file ownership</A ></DT ><DT >10.4. <A -HREF="#AEN1779" +HREF="#AEN1682" >Viewing file or directory permissions</A ></DT ><DD ><DL ><DT >10.4.1. <A -HREF="#AEN1794" +HREF="#AEN1697" >File Permissions</A ></DT ><DT >10.4.2. <A -HREF="#AEN1808" +HREF="#AEN1711" >Directory Permissions</A ></DT ></DL ></DD ><DT >10.5. <A -HREF="#AEN1815" +HREF="#AEN1718" >Modifying file or directory permissions</A ></DT ><DT >10.6. <A -HREF="#AEN1837" +HREF="#AEN1740" >Interaction with the standard Samba create mask parameters</A ></DT ><DT >10.7. <A -HREF="#AEN1901" +HREF="#AEN1804" >Interaction with the standard Samba file attribute mapping</A ></DT @@ -7887,17 +7421,17 @@ managed authentication</A ><DL ><DT >11.1. <A -HREF="#AEN1922" +HREF="#AEN1825" >Samba and PAM</A ></DT ><DT >11.2. <A -HREF="#AEN1966" +HREF="#AEN1869" >Distributed Authentication</A ></DT ><DT >11.3. <A -HREF="#AEN1973" +HREF="#AEN1876" >PAM Configuration in smb.conf</A ></DT ></DL @@ -7911,14 +7445,14 @@ HREF="#MSDFS" ><DL ><DT >12.1. <A -HREF="#AEN1993" +HREF="#AEN1896" >Instructions</A ></DT ><DD ><DL ><DT >12.1.1. <A -HREF="#AEN2028" +HREF="#AEN1931" >Notes</A ></DT ></DL @@ -7934,122 +7468,122 @@ HREF="#PRINTING" ><DL ><DT >13.1. <A -HREF="#AEN2054" +HREF="#AEN1957" >Introduction</A ></DT ><DT >13.2. <A -HREF="#AEN2076" +HREF="#AEN1979" >Configuration</A ></DT ><DD ><DL ><DT >13.2.1. <A -HREF="#AEN2084" +HREF="#AEN1987" >Creating [print$]</A ></DT ><DT >13.2.2. <A -HREF="#AEN2119" +HREF="#AEN2022" >Setting Drivers for Existing Printers</A ></DT ><DT >13.2.3. <A -HREF="#AEN2135" +HREF="#AEN2038" >Support a large number of printers</A ></DT ><DT >13.2.4. <A -HREF="#AEN2146" +HREF="#AEN2049" >Adding New Printers via the Windows NT APW</A ></DT ><DT >13.2.5. <A -HREF="#AEN2176" +HREF="#AEN2079" >Samba and Printer Ports</A ></DT ></DL ></DD ><DT >13.3. <A -HREF="#AEN2184" +HREF="#AEN2087" >The Imprints Toolset</A ></DT ><DD ><DL ><DT >13.3.1. <A -HREF="#AEN2188" +HREF="#AEN2091" >What is Imprints?</A ></DT ><DT >13.3.2. <A -HREF="#AEN2198" +HREF="#AEN2101" >Creating Printer Driver Packages</A ></DT ><DT >13.3.3. <A -HREF="#AEN2201" +HREF="#AEN2104" >The Imprints server</A ></DT ><DT >13.3.4. <A -HREF="#AEN2205" +HREF="#AEN2108" >The Installation Client</A ></DT ></DL ></DD ><DT >13.4. <A -HREF="#AEN2227" +HREF="#AEN2130" >Diagnosis</A ></DT ><DD ><DL ><DT >13.4.1. <A -HREF="#AEN2229" +HREF="#AEN2132" >Introduction</A ></DT ><DT >13.4.2. <A -HREF="#AEN2245" +HREF="#AEN2148" >Debugging printer problems</A ></DT ><DT >13.4.3. <A -HREF="#AEN2254" +HREF="#AEN2157" >What printers do I have?</A ></DT ><DT >13.4.4. <A -HREF="#AEN2262" +HREF="#AEN2165" >Setting up printcap and print servers</A ></DT ><DT >13.4.5. <A -HREF="#AEN2290" +HREF="#AEN2193" >Job sent, no output</A ></DT ><DT >13.4.6. <A -HREF="#AEN2301" +HREF="#AEN2204" >Job sent, strange output</A ></DT ><DT >13.4.7. <A -HREF="#AEN2313" +HREF="#AEN2216" >Raw PostScript printed</A ></DT ><DT >13.4.8. <A -HREF="#AEN2316" +HREF="#AEN2219" >Advanced Printing</A ></DT ><DT >13.4.9. <A -HREF="#AEN2319" +HREF="#AEN2222" >Real debugging</A ></DT ></DL @@ -8065,99 +7599,99 @@ HREF="#WINBIND" ><DL ><DT >14.1. <A -HREF="#AEN2360" +HREF="#AEN2263" >Abstract</A ></DT ><DT >14.2. <A -HREF="#AEN2364" +HREF="#AEN2267" >Introduction</A ></DT ><DT >14.3. <A -HREF="#AEN2377" +HREF="#AEN2280" >What Winbind Provides</A ></DT ><DD ><DL ><DT >14.3.1. <A -HREF="#AEN2384" +HREF="#AEN2287" >Target Uses</A ></DT ></DL ></DD ><DT >14.4. <A -HREF="#AEN2388" +HREF="#AEN2291" >How Winbind Works</A ></DT ><DD ><DL ><DT >14.4.1. <A -HREF="#AEN2393" +HREF="#AEN2296" >Microsoft Remote Procedure Calls</A ></DT ><DT >14.4.2. <A -HREF="#AEN2397" +HREF="#AEN2300" >Microsoft Active Directory Services</A ></DT ><DT >14.4.3. <A -HREF="#AEN2400" +HREF="#AEN2303" >Name Service Switch</A ></DT ><DT >14.4.4. <A -HREF="#AEN2416" +HREF="#AEN2319" >Pluggable Authentication Modules</A ></DT ><DT >14.4.5. <A -HREF="#AEN2424" +HREF="#AEN2327" >User and Group ID Allocation</A ></DT ><DT >14.4.6. <A -HREF="#AEN2428" +HREF="#AEN2331" >Result Caching</A ></DT ></DL ></DD ><DT >14.5. <A -HREF="#AEN2431" +HREF="#AEN2334" >Installation and Configuration</A ></DT ><DD ><DL ><DT >14.5.1. <A -HREF="#AEN2438" +HREF="#AEN2341" >Introduction</A ></DT ><DT >14.5.2. <A -HREF="#AEN2451" +HREF="#AEN2354" >Requirements</A ></DT ><DT >14.5.3. <A -HREF="#AEN2465" +HREF="#AEN2368" >Testing Things Out</A ></DT ></DL ></DD ><DT >14.6. <A -HREF="#AEN2680" +HREF="#AEN2583" >Limitations</A ></DT ><DT >14.7. <A -HREF="#AEN2690" +HREF="#AEN2593" >Conclusion</A ></DT ></DL @@ -8171,66 +7705,66 @@ HREF="#IMPROVED-BROWSING" ><DL ><DT >15.1. <A -HREF="#AEN2700" +HREF="#AEN2603" >Overview of browsing</A ></DT ><DT >15.2. <A -HREF="#AEN2704" +HREF="#AEN2608" >Browsing support in samba</A ></DT ><DT >15.3. <A -HREF="#AEN2713" +HREF="#AEN2616" >Problem resolution</A ></DT ><DT >15.4. <A -HREF="#AEN2720" +HREF="#AEN2625" >Browsing across subnets</A ></DT ><DD ><DL ><DT >15.4.1. <A -HREF="#AEN2725" +HREF="#AEN2630" >How does cross subnet browsing work ?</A ></DT ></DL ></DD ><DT >15.5. <A -HREF="#AEN2760" +HREF="#AEN2665" >Setting up a WINS server</A ></DT ><DT >15.6. <A -HREF="#AEN2779" +HREF="#AEN2684" >Setting up Browsing in a WORKGROUP</A ></DT ><DT >15.7. <A -HREF="#AEN2797" +HREF="#AEN2702" >Setting up Browsing in a DOMAIN</A ></DT ><DT >15.8. <A -HREF="#AEN2807" +HREF="#AEN2712" >Forcing samba to be the master</A ></DT ><DT >15.9. <A -HREF="#AEN2816" +HREF="#AEN2721" >Making samba the domain master</A ></DT ><DT >15.10. <A -HREF="#AEN2834" +HREF="#AEN2739" >Note about broadcast addresses</A ></DT ><DT >15.11. <A -HREF="#AEN2837" +HREF="#AEN2742" >Multiple interfaces</A ></DT ></DL @@ -8244,48 +7778,48 @@ HREF="#VFS" ><DL ><DT >16.1. <A -HREF="#AEN2855" +HREF="#AEN2760" >Introduction and configuration</A ></DT ><DT >16.2. <A -HREF="#AEN2864" +HREF="#AEN2769" >Included modules</A ></DT ><DD ><DL ><DT >16.2.1. <A -HREF="#AEN2866" +HREF="#AEN2771" >audit</A ></DT ><DT >16.2.2. <A -HREF="#AEN2874" +HREF="#AEN2779" >recycle</A ></DT ><DT >16.2.3. <A -HREF="#AEN2911" +HREF="#AEN2816" >netatalk</A ></DT ></DL ></DD ><DT >16.3. <A -HREF="#AEN2918" +HREF="#AEN2823" >VFS modules available elsewhere</A ></DT ><DD ><DL ><DT >16.3.1. <A -HREF="#AEN2922" +HREF="#AEN2827" >DatabaseFS</A ></DT ><DT >16.3.2. <A -HREF="#AEN2930" +HREF="#AEN2835" >vscan</A ></DT ></DL @@ -8294,149 +7828,155 @@ HREF="#AEN2930" ></DD ><DT >17. <A -HREF="#CVS-ACCESS" ->Access Samba source code via CVS</A -></DT -><DD -><DL -><DT ->17.1. <A -HREF="#AEN2942" ->Introduction</A -></DT -><DT ->17.2. <A -HREF="#AEN2947" ->CVS Access to samba.org</A -></DT -><DD -><DL -><DT ->17.2.1. <A -HREF="#AEN2950" ->Access via CVSweb</A -></DT -><DT ->17.2.2. <A -HREF="#AEN2955" ->Access via cvs</A -></DT -></DL -></DD -></DL -></DD -><DT ->18. <A HREF="#GROUPMAPPING" >Group mapping HOWTO</A ></DT ><DT ->19. <A +>18. <A HREF="#SPEED" >Samba performance issues</A ></DT ><DD ><DL ><DT ->19.1. <A -HREF="#AEN3033" +>18.1. <A +HREF="#AEN2890" >Comparisons</A ></DT ><DT ->19.2. <A -HREF="#AEN3039" +>18.2. <A +HREF="#AEN2896" >Socket options</A ></DT ><DT ->19.3. <A -HREF="#AEN3046" +>18.3. <A +HREF="#AEN2903" >Read size</A ></DT ><DT ->19.4. <A -HREF="#AEN3051" +>18.4. <A +HREF="#AEN2908" >Max xmit</A ></DT ><DT ->19.5. <A -HREF="#AEN3056" +>18.5. <A +HREF="#AEN2913" >Log level</A ></DT ><DT ->19.6. <A -HREF="#AEN3059" +>18.6. <A +HREF="#AEN2916" >Read raw</A ></DT ><DT ->19.7. <A -HREF="#AEN3064" +>18.7. <A +HREF="#AEN2921" >Write raw</A ></DT ><DT ->19.8. <A -HREF="#AEN3068" +>18.8. <A +HREF="#AEN2925" >Slow Clients</A ></DT ><DT ->19.9. <A -HREF="#AEN3072" +>18.9. <A +HREF="#AEN2929" >Slow Logins</A ></DT ><DT ->19.10. <A -HREF="#AEN3075" +>18.10. <A +HREF="#AEN2932" >Client tuning</A ></DT ></DL ></DD ><DT ->20. <A +>19. <A HREF="#GROUPPROFILES" ->Creating Group Profiles</A +>Creating Group Prolicy Files</A ></DT ><DD ><DL ><DT ->20.1. <A -HREF="#AEN3123" +>19.1. <A +HREF="#AEN2980" >Windows '9x</A ></DT ><DT ->20.2. <A -HREF="#AEN3132" +>19.2. <A +HREF="#AEN2990" >Windows NT 4</A ></DT ><DD ><DL ><DT ->20.2.1. <A -HREF="#AEN3155" +>19.2.1. <A +HREF="#AEN3013" >Side bar Notes</A ></DT ><DT ->20.2.2. <A -HREF="#AEN3159" +>19.2.2. <A +HREF="#AEN3017" >Mandatory profiles</A ></DT ><DT ->20.2.3. <A -HREF="#AEN3162" +>19.2.3. <A +HREF="#AEN3020" >moveuser.exe</A ></DT ><DT ->20.2.4. <A -HREF="#AEN3165" +>19.2.4. <A +HREF="#AEN3023" >Get SID</A ></DT ></DL ></DD ><DT ->20.3. <A -HREF="#AEN3170" +>19.3. <A +HREF="#AEN3028" >Windows 2000/XP</A ></DT ></DL ></DD +><DT +>20. <A +HREF="#SECURING-SAMBA" +>Securing Samba</A +></DT +><DD +><DL +><DT +>20.1. <A +HREF="#AEN3109" +>Introduction</A +></DT +><DT +>20.2. <A +HREF="#AEN3112" +>Using host based protection</A +></DT +><DT +>20.3. <A +HREF="#AEN3119" +>Using interface protection</A +></DT +><DT +>20.4. <A +HREF="#AEN3128" +>Using a firewall</A +></DT +><DT +>20.5. <A +HREF="#AEN3135" +>Using a IPC$ share deny</A +></DT +><DT +>20.6. <A +HREF="#AEN3144" +>Upgrading Samba</A +></DT +></DL +></DD ></DL ></DIV ></DIV @@ -8452,9 +7992,9 @@ CLASS="SECT1" ><H2 CLASS="SECT1" ><A -NAME="AEN1513" -></A ->9.1. Agenda</H2 +NAME="AEN1416" +>9.1. Agenda</A +></H2 ><P >To identify the key functional mechanisms of MS Windows networking to enable the deployment of Samba as a means of extending and/or @@ -8519,9 +8059,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN1535" -></A ->9.2. Name Resolution in a pure Unix/Linux world</H2 +NAME="AEN1438" +>9.2. Name Resolution in a pure Unix/Linux world</A +></H2 ><P >The key configuration files covered in this section are:</P ><P @@ -8561,11 +8101,11 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN1551" -></A +NAME="AEN1454" >9.2.1. <TT CLASS="FILENAME" >/etc/hosts</TT +></A ></H3 ><P >Contains a static list of IP Addresses and names. @@ -8642,11 +8182,11 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN1567" -></A +NAME="AEN1470" >9.2.2. <TT CLASS="FILENAME" >/etc/resolv.conf</TT +></A ></H3 ><P >This file tells the name resolution libraries:</P @@ -8680,11 +8220,11 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN1578" -></A +NAME="AEN1481" >9.2.3. <TT CLASS="FILENAME" >/etc/host.conf</TT +></A ></H3 ><P ><TT @@ -8709,11 +8249,11 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN1586" -></A +NAME="AEN1489" >9.2.4. <TT CLASS="FILENAME" >/etc/nsswitch.conf</TT +></A ></H3 ><P >This file controls the actual name resolution targets. The @@ -8778,9 +8318,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN1598" -></A ->9.3. Name resolution as used within MS Windows networking</H2 +NAME="AEN1501" +>9.3. 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 @@ -8800,16 +8340,16 @@ the client/server.</P ><PRE CLASS="PROGRAMLISTING" > Unique NetBIOS Names: - MACHINENAME<00> = Server Service is running on MACHINENAME - MACHINENAME<03> = Generic Machine Name (NetBIOS name) - MACHINENAME<20> = LanMan Server service is running on MACHINENAME - WORKGROUP<1b> = Domain Master Browser + MACHINENAME<00> = Server Service is running on MACHINENAME + MACHINENAME<03> = Generic Machine Name (NetBIOS name) + MACHINENAME<20> = LanMan Server service is running on MACHINENAME + WORKGROUP<1b> = Domain Master Browser Group Names: - WORKGROUP<03> = Generic Name registered by all members of WORKGROUP - WORKGROUP<1c> = Domain Controllers / Netlogon Servers - WORKGROUP<1d> = Local Master Browsers - WORKGROUP<1e> = Internet Name Resolvers</PRE + WORKGROUP<03> = Generic Name registered by all members of WORKGROUP + WORKGROUP<1c> = Domain Controllers / Netlogon Servers + WORKGROUP<1d> = Local Master Browsers + WORKGROUP<1e> = Internet Name Resolvers</PRE ></P ><P >It should be noted that all NetBIOS machines register their own @@ -8828,7 +8368,7 @@ be needed. An example of this is what happens when an MS Windows client wants to locate a domain logon server. It find this service and the IP address of a server that provides it by performing a lookup (via a NetBIOS broadcast) for enumeration of all machines that have -registered the name type *<1c>. A logon request is then sent to each +registered the name type *<1c>. A logon request is then sent to each IP address that is returned in the enumerated list of IP addresses. Which ever machine first replies then ends up providing the logon services.</P ><P @@ -8863,9 +8403,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN1610" -></A ->9.3.1. The NetBIOS Name Cache</H3 +NAME="AEN1513" +>9.3.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 @@ -8890,9 +8430,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN1615" -></A ->9.3.2. The LMHOSTS file</H3 +NAME="AEN1518" +>9.3.2. The LMHOSTS file</A +></H3 ><P >This file is usually located in MS Windows NT 4.0 or 2000 in <TT @@ -8927,8 +8467,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) @@ -8937,16 +8477,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. @@ -8993,9 +8533,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN1623" -></A ->9.3.3. HOSTS file</H3 +NAME="AEN1526" +>9.3.3. HOSTS file</A +></H3 ><P >This file is usually located in MS Windows NT 4.0 or 2000 in <TT @@ -9015,9 +8555,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN1628" -></A ->9.3.4. DNS Lookup</H3 +NAME="AEN1531" +>9.3.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 @@ -9035,9 +8575,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN1631" -></A ->9.3.5. WINS Lookup</H3 +NAME="AEN1534" +>9.3.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 @@ -9064,11 +8604,9 @@ CLASS="PROGRAMLISTING" wins server = xxx.xxx.xxx.xxx</PRE ></P ><P ->where <TT +>where <VAR CLASS="REPLACEABLE" -><I ->xxx.xxx.xxx.xxx</I -></TT +>xxx.xxx.xxx.xxx</VAR > is the IP address of the WINS server.</P ></DIV @@ -9078,10 +8616,10 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN1643" -></A +NAME="AEN1546" >9.4. How browsing functions and how to deploy stable and -dependable browsing using Samba</H2 +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 @@ -9145,10 +8683,10 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN1653" -></A +NAME="AEN1556" >9.5. MS Windows security options and how to configure -Samba for seemless integration</H2 +Samba for seemless integration</A +></H2 ><P >MS Windows clients may use encrypted passwords as part of a challenege/response authentication model (a.k.a. NTLMv1) or @@ -9217,43 +8755,35 @@ CLASS="PROGRAMLISTING" HREF="smb.conf.5.html#PASSWORDLEVEL" TARGET="_top" >passsword level</A -> = <TT +> = <VAR CLASS="REPLACEABLE" -><I ->integer</I -></TT +>integer</VAR > <A HREF="smb.conf.5.html#USERNAMELEVEL" TARGET="_top" >username level</A -> = <TT +> = <VAR CLASS="REPLACEABLE" -><I ->integer</I -></TT +>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 <TT +character, the <VAR CLASS="PARAMETER" -><I ->username level</I -></TT +>username level</VAR > 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 +the <VAR CLASS="PARAMETER" -><I ->password level</I -></TT +>password level</VAR > must be set to the maximum number of upper case letter which <SPAN CLASS="emphasis" @@ -9263,11 +8793,9 @@ CLASS="EMPHASIS" ></SPAN > appear is a password. Note that is the server OS uses the traditional -DES version of crypt(), then a <TT +DES version of crypt(), then a <VAR CLASS="PARAMETER" -><I ->password level</I -></TT +>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 @@ -9282,9 +8810,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN1681" -></A ->9.5.1. Use MS Windows NT as an authentication server</H3 +NAME="AEN1584" +>9.5.1. Use MS Windows NT as an authentication server</A +></H3 ><P >This method involves the additions of the following parameters in the smb.conf file:</P @@ -9318,9 +8846,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN1689" -></A ->9.5.2. Make Samba a member of an MS Windows NT security domain</H3 +NAME="AEN1592" +>9.5.2. Make Samba a member of an MS Windows NT security domain</A +></H3 ><P >This method involves additon of the following paramters in the smb.conf file:</P ><P @@ -9381,9 +8909,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN1706" -></A ->9.5.3. Configure Samba as an authentication server</H3 +NAME="AEN1609" +>9.5.3. Configure Samba as an authentication server</A +></H3 ><P >This mode of authentication demands that there be on the Unix/Linux system both a Unix style account as well as an @@ -9418,9 +8946,9 @@ CLASS="SECT3" ><HR><H4 CLASS="SECT3" ><A -NAME="AEN1713" -></A ->9.5.3.1. Users</H4 +NAME="AEN1616" +>9.5.3.1. Users</A +></H4 ><P >A user account that may provide a home directory should be created. The following Linux system commands are typical of @@ -9430,10 +8958,10 @@ the procedure for creating an account.</P CLASS="PROGRAMLISTING" > # useradd -s /bin/bash -d /home/"userid" -m "userid" # passwd "userid" - Enter Password: <pw> + Enter Password: <pw> # smbpasswd -a "userid" - Enter Password: <pw></PRE + Enter Password: <pw></PRE ></P ></DIV ><DIV @@ -9441,9 +8969,9 @@ CLASS="SECT3" ><HR><H4 CLASS="SECT3" ><A -NAME="AEN1718" -></A ->9.5.3.2. MS Windows NT Machine Accounts</H4 +NAME="AEN1621" +>9.5.3.2. MS Windows NT Machine Accounts</A +></H4 ><P >These are required only when Samba is used as a domain controller. Refer to the Samba-PDC-HOWTO for more details.</P @@ -9462,9 +8990,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN1723" -></A ->9.6. Conclusions</H2 +NAME="AEN1626" +>9.6. Conclusions</A +></H2 ><P >Samba provides a flexible means to operate as...</P ><P @@ -9506,10 +9034,10 @@ CLASS="SECT1" ><H2 CLASS="SECT1" ><A -NAME="AEN1744" -></A +NAME="AEN1647" >10.1. Viewing and changing UNIX permissions using the NT - security dialogs</H2 + security dialogs</A +></H2 ><P >New in the Samba 2.0.4 release is the ability for Windows NT clients to use their native security settings dialog box to @@ -9525,9 +9053,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN1748" -></A ->10.2. How to view file security on a Samba share</H2 +NAME="AEN1651" +>10.2. How to view file security on a Samba share</A +></H2 ><P >From an NT 4.0 client, single-click with the right mouse button on any file or directory in a Samba mounted @@ -9595,9 +9123,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN1759" -></A ->10.3. Viewing file ownership</H2 +NAME="AEN1662" +>10.3. Viewing file ownership</A +></H2 ><P >Clicking on the <B CLASS="COMMAND" @@ -9611,23 +9139,17 @@ CLASS="COMMAND" >"SERVER\user (Long name)"</B ></P ><P ->Where <TT +>Where <VAR CLASS="REPLACEABLE" -><I ->SERVER</I -></TT +>SERVER</VAR > is the NetBIOS name of - the Samba server, <TT + the Samba server, <VAR CLASS="REPLACEABLE" -><I ->user</I -></TT +>user</VAR > is the user name of - the UNIX user who owns the file, and <TT + the UNIX user who owns the file, and <VAR CLASS="REPLACEABLE" -><I ->(Long name)</I -></TT +>(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 @@ -9636,15 +9158,13 @@ CLASS="COMMAND" </B > button to remove this dialog.</P ><P ->If the parameter <TT +>If the parameter <VAR CLASS="PARAMETER" -><I ->nt acl support</I -></TT +>nt acl support</VAR > - is set to <TT + is set to <CODE CLASS="CONSTANT" ->false</TT +>false</CODE > then the file owner will be shown as the NT user <B CLASS="COMMAND" @@ -9689,9 +9209,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN1779" -></A ->10.4. Viewing file or directory permissions</H2 +NAME="AEN1682" +>10.4. Viewing file or directory permissions</A +></H2 ><P >The third button is the <B CLASS="COMMAND" @@ -9706,36 +9226,28 @@ CLASS="COMMAND" >"SERVER\user (Long name)"</B ></P ><P ->Where <TT +>Where <VAR CLASS="REPLACEABLE" -><I ->SERVER</I -></TT +>SERVER</VAR > is the NetBIOS name of - the Samba server, <TT + the Samba server, <VAR CLASS="REPLACEABLE" -><I ->user</I -></TT +>user</VAR > is the user name of - the UNIX user who owns the file, and <TT + the UNIX user who owns the file, and <VAR CLASS="REPLACEABLE" -><I ->(Long name)</I -></TT +>(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 <TT +>If the parameter <VAR CLASS="PARAMETER" -><I ->nt acl support</I -></TT +>nt acl support</VAR > - is set to <TT + is set to <CODE CLASS="CONSTANT" ->false</TT +>false</CODE > then the file owner will be shown as the NT user <B CLASS="COMMAND" @@ -9751,9 +9263,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN1794" -></A ->10.4.1. File Permissions</H3 +NAME="AEN1697" +>10.4.1. File Permissions</A +></H3 ><P >The standard UNIX user/group/world triple and the corresponding "read", "write", "execute" permissions @@ -9813,9 +9325,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN1808" -></A ->10.4.2. Directory Permissions</H3 +NAME="AEN1711" +>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 @@ -9845,9 +9357,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN1815" -></A ->10.5. Modifying file or directory permissions</H2 +NAME="AEN1718" +>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 @@ -9859,15 +9371,13 @@ 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 <TT +>If the parameter <VAR CLASS="PARAMETER" -><I ->nt acl support</I -></TT +>nt acl support</VAR > - is set to <TT + is set to <CODE CLASS="CONSTANT" ->false</TT +>false</CODE > then any attempt to set security permissions will fail with an <B CLASS="COMMAND" @@ -9943,40 +9453,32 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN1837" -></A +NAME="AEN1740" >10.6. Interaction with the standard Samba create mask - parameters</H2 + parameters</A +></H2 ><P >Note that with Samba 2.0.5 there are four new parameters to control this interaction. These are :</P ><P -><TT +><VAR CLASS="PARAMETER" -><I ->security mask</I -></TT +>security mask</VAR ></P ><P -><TT +><VAR CLASS="PARAMETER" -><I ->force security mode</I -></TT +>force security mode</VAR ></P ><P -><TT +><VAR CLASS="PARAMETER" -><I ->directory security mask</I -></TT +>directory security mask</VAR ></P ><P -><TT +><VAR CLASS="PARAMETER" -><I ->force directory security mode</I -></TT +>force directory security mode</VAR ></P ><P >Once a user clicks <B @@ -9989,21 +9491,17 @@ CLASS="COMMAND" HREF="smb.conf.5.html#SECURITYMASK" TARGET="_top" > - <TT + <VAR CLASS="PARAMETER" -><I ->security mask</I -></TT +>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 <TT +>Essentially, zero bits in the <VAR CLASS="PARAMETER" -><I ->security mask</I -></TT +>security mask</VAR > mask may be treated as a set of bits the user is <SPAN CLASS="emphasis" @@ -10019,12 +9517,10 @@ CLASS="EMPHASIS" the <A HREF="smb.conf.5.html#CREATEMASK" TARGET="_top" -><TT +><VAR CLASS="PARAMETER" -><I >create mask - </I -></TT + </VAR ></A > parameter to provide compatibility with Samba 2.0.4 where this permission change facility was introduced. To allow a user to @@ -10035,22 +9531,18 @@ CLASS="PARAMETER" the bits set in the <A HREF="smb.conf.5.html#FORCESECURITYMODE" TARGET="_top" -> <TT +> <VAR CLASS="PARAMETER" -><I ->force security mode</I -></TT +>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 <TT +>Essentially, bits set in the <VAR CLASS="PARAMETER" -><I >force security mode - </I -></TT + </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 @@ -10058,82 +9550,60 @@ CLASS="PARAMETER" as the <A HREF="smb.conf.5.html#FORCECREATEMODE" TARGET="_top" -><TT +><VAR CLASS="PARAMETER" -><I >force - create mode</I -></TT + create mode</VAR ></A > parameter to provide compatibility with Samba 2.0.4 where the permission change facility was introduced. To allow a user to modify all the user/group/world permissions on a file with no restrictions set this parameter to 000.</P ><P ->The <TT +>The <VAR CLASS="PARAMETER" -><I ->security mask</I -></TT -> and <TT +>security mask</VAR +> and <VAR CLASS="PARAMETER" -><I >force - security mode</I -></TT + 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 <TT + described above for a file except using the parameter <VAR CLASS="PARAMETER" -><I -> directory security mask</I -></TT -> instead of <TT +> directory security mask</VAR +> instead of <VAR CLASS="PARAMETER" -><I >security - mask</I -></TT ->, and <TT + mask</VAR +>, and <VAR CLASS="PARAMETER" -><I >force directory security mode - </I -></TT -> parameter instead of <TT + </VAR +> parameter instead of <VAR CLASS="PARAMETER" -><I >force security mode - </I -></TT + </VAR >.</P ><P ->The <TT +>The <VAR CLASS="PARAMETER" -><I ->directory security mask</I -></TT +>directory security mask</VAR > parameter - by default is set to the same value as the <TT + by default is set to the same value as the <VAR CLASS="PARAMETER" -><I >directory mask - </I -></TT -> parameter and the <TT + </VAR +> parameter and the <VAR CLASS="PARAMETER" -><I >force directory security - mode</I -></TT + mode</VAR > parameter by default is set to the same value as - the <TT + the <VAR CLASS="PARAMETER" -><I ->force directory mode</I -></TT +>force directory mode</VAR > parameter to provide compatibility with Samba 2.0.4 where the permission change facility was introduced.</P @@ -10155,62 +9625,46 @@ CLASS="FILENAME" ></A > file in that share specific section :</P ><P -><TT +><VAR CLASS="PARAMETER" -><I ->security mask = 0777</I -></TT +>security mask = 0777</VAR ></P ><P -><TT +><VAR CLASS="PARAMETER" -><I ->force security mode = 0</I -></TT +>force security mode = 0</VAR ></P ><P -><TT +><VAR CLASS="PARAMETER" -><I ->directory security mask = 0777</I -></TT +>directory security mask = 0777</VAR ></P ><P -><TT +><VAR CLASS="PARAMETER" -><I ->force directory security mode = 0</I -></TT +>force directory security mode = 0</VAR ></P ><P >As described, in Samba 2.0.4 the parameters :</P ><P -><TT +><VAR CLASS="PARAMETER" -><I ->create mask</I -></TT +>create mask</VAR ></P ><P -><TT +><VAR CLASS="PARAMETER" -><I ->force create mode</I -></TT +>force create mode</VAR ></P ><P -><TT +><VAR CLASS="PARAMETER" -><I ->directory mask</I -></TT +>directory mask</VAR ></P ><P -><TT +><VAR CLASS="PARAMETER" -><I ->force directory mode</I -></TT +>force directory mode</VAR ></P ><P >were used instead of the parameters discussed here.</P @@ -10220,10 +9674,10 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN1901" -></A +NAME="AEN1804" >10.7. Interaction with the standard Samba file attribute - mapping</H2 + 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 @@ -10276,9 +9730,9 @@ CLASS="SECT1" ><H2 CLASS="SECT1" ><A -NAME="AEN1922" -></A ->11.1. Samba and PAM</H2 +NAME="AEN1825" +>11.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 @@ -10490,9 +9944,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN1966" -></A ->11.2. Distributed Authentication</H2 +NAME="AEN1869" +>11.2. Distributed Authentication</A +></H2 ><P >The astute administrator will realize from this that the combination of <TT @@ -10523,9 +9977,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN1973" -></A ->11.3. PAM Configuration in smb.conf</H2 +NAME="AEN1876" +>11.3. PAM Configuration in smb.conf</A +></H2 ><P >There is an option in smb.conf called <A HREF="smb.conf.5.html#OBEYPAMRESTRICTIONS" @@ -10535,9 +9989,9 @@ TARGET="_top" The following is from the on-line help for this option in SWAT;</P ><P >When Samba 2.2 is configure to enable PAM support (i.e. -<TT +<CODE CLASS="CONSTANT" ->--with-pam</TT +>--with-pam</CODE >), this parameter will control whether or not Samba should obey PAM's account and session management directives. The default behavior @@ -10571,9 +10025,9 @@ CLASS="SECT1" ><H2 CLASS="SECT1" ><A -NAME="AEN1993" -></A ->12.1. Instructions</H2 +NAME="AEN1896" +>12.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 @@ -10589,21 +10043,17 @@ TARGET="_top" machine (for Dfs-aware clients to browse) using Samba.</P ><P >To enable SMB-based DFS for Samba, configure it with the - <TT + <VAR CLASS="PARAMETER" -><I ->--with-msdfs</I -></TT +>--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" -><TT +><VAR CLASS="PARAMETER" -><I -> host msdfs</I -></TT +> host msdfs</VAR ></A > parameter in the <TT CLASS="FILENAME" @@ -10613,18 +10063,16 @@ CLASS="FILENAME" level boolean <A HREF="smb.conf.5.html#MSDFSROOT" TARGET="_top" -><TT +><VAR CLASS="PARAMETER" -><I -> msdfs root</I -></TT +> 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 +>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 @@ -10652,54 +10100,44 @@ CLASS="PROGRAMLISTING" >In the /export/dfsroot directory we set up our dfs links to other servers on the network.</P ><P -><TT +><SAMP CLASS="PROMPT" ->root# </TT -><TT +>root# </SAMP +><KBD CLASS="USERINPUT" -><B ->cd /export/dfsroot</B -></TT +>cd /export/dfsroot</KBD ></P ><P -><TT +><SAMP CLASS="PROMPT" ->root# </TT -><TT +>root# </SAMP +><KBD CLASS="USERINPUT" -><B ->chown root /export/dfsroot</B -></TT +>chown root /export/dfsroot</KBD ></P ><P -><TT +><SAMP CLASS="PROMPT" ->root# </TT -><TT +>root# </SAMP +><KBD CLASS="USERINPUT" -><B ->chmod 755 /export/dfsroot</B -></TT +>chmod 755 /export/dfsroot</KBD ></P ><P -><TT +><SAMP CLASS="PROMPT" ->root# </TT -><TT +>root# </SAMP +><KBD CLASS="USERINPUT" -><B ->ln -s msdfs:storageA\\shareA linka</B -></TT +>ln -s msdfs:storageA\\shareA linka</KBD ></P ><P -><TT +><SAMP CLASS="PROMPT" ->root# </TT -><TT +>root# </SAMP +><KBD CLASS="USERINPUT" -><B ->ln -s msdfs:serverB\\share,serverC\\share linkb</B -></TT +>ln -s msdfs:serverB\\share,serverC\\share linkb</KBD ></P ><P >You should set up the permissions and ownership of @@ -10719,9 +10157,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN2028" -></A ->12.1.1. Notes</H3 +NAME="AEN1931" +>12.1.1. Notes</A +></H3 ><P ></P ><UL @@ -10760,9 +10198,9 @@ CLASS="SECT1" ><H2 CLASS="SECT1" ><A -NAME="AEN2054" -></A ->13.1. Introduction</H2 +NAME="AEN1957" +>13.1. Introduction</A +></H2 ><P >Beginning with the 2.2.0 release, Samba supports the native Windows NT printing mechanisms implemented via @@ -10843,9 +10281,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN2076" -></A ->13.2. Configuration</H2 +NAME="AEN1979" +>13.2. Configuration</A +></H2 ><DIV CLASS="WARNING" ><P @@ -10884,19 +10322,15 @@ a printer$ service which provides read-only access via no password in order to support printer driver downloads.</P ><P >However, the initial implementation allowed for a -parameter named <TT +parameter named <VAR CLASS="PARAMETER" -><I ->printer driver location</I -></TT +>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 <TT +parameter named <VAR CLASS="PARAMETER" -><I ->printer driver</I -></TT +>printer driver</VAR > provided a means of defining the printer driver name to be sent to the client.</P @@ -10909,9 +10343,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN2084" -></A ->13.2.1. Creating [print$]</H3 +NAME="AEN1987" +>13.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$]. @@ -10950,11 +10384,9 @@ CLASS="PROGRAMLISTING" >The <A HREF="smb.conf.5.html#WRITELIST" TARGET="_top" -><TT +><VAR CLASS="PARAMETER" -><I ->write list</I -></TT +>write list</VAR ></A > is used to allow administrative level user accounts to have write access in order to update files @@ -11094,12 +10526,10 @@ one of two conditions must hold true:</P must be a member of the <A HREF="smb.conf.5.html#PRINTERADMIN" TARGET="_top" -><TT +><VAR CLASS="PARAMETER" -><I >printer - admin</I -></TT + admin</VAR ></A > list.</P ></LI @@ -11115,11 +10545,9 @@ 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 <TT +a root (or <VAR CLASS="PARAMETER" -><I ->printer admin</I -></TT +>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 @@ -11132,9 +10560,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN2119" -></A ->13.2.2. Setting Drivers for Existing Printers</H3 +NAME="AEN2022" +>13.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 @@ -11204,9 +10632,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN2135" -></A ->13.2.3. Support a large number of printers</H3 +NAME="AEN2038" +>13.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 @@ -11227,9 +10655,9 @@ of how this could be accomplished:</P ><PRE CLASS="PROGRAMLISTING" > -<TT +<SAMP CLASS="PROMPT" ->$ </TT +>$ </SAMP >rpcclient pogo -U root%secret -c "enumdrivers" Domain=[NARNIA] OS=[Unix] Server=[Samba 2.2.0-alpha3] @@ -11243,9 +10671,9 @@ Printer Driver Info 1: Printer Driver Info 1: Driver Name: [HP LaserJet 4Si/4SiMX PS] -<TT +<SAMP CLASS="PROMPT" ->$ </TT +>$ </SAMP >rpcclient pogo -U root%secret -c "enumprinters" Domain=[NARNIA] OS=[Unix] Server=[Samba 2.2.0-alpha3] flags:[0x800000] @@ -11253,13 +10681,13 @@ Domain=[NARNIA] OS=[Unix] Server=[Samba 2.2.0-alpha3] description:[POGO\\POGO\hp-print,NO DRIVER AVAILABLE FOR THIS PRINTER,] comment:[] -<TT +<SAMP CLASS="PROMPT" ->$ </TT +>$ </SAMP >rpcclient pogo -U root%secret \ -<TT +<SAMP CLASS="PROMPT" ->> </TT +>> </SAMP > -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 @@ -11270,9 +10698,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN2146" -></A ->13.2.4. Adding New Printers via the Windows NT APW</H3 +NAME="AEN2049" +>13.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" @@ -11287,11 +10715,9 @@ 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 <TT + privileges (i.e. root or <VAR CLASS="PARAMETER" -><I ->printer admin</I -></TT +>printer admin</VAR >). </P ></LI @@ -11300,12 +10726,10 @@ CLASS="PARAMETER" ><A HREF="smb.conf.5.html#SHOWADDPRINTERWIZARD" TARGET="_top" -><TT +><VAR CLASS="PARAMETER" -><I >show - add printer wizard = yes</I -></TT + add printer wizard = yes</VAR ></A > (the default). </P @@ -11316,12 +10740,10 @@ CLASS="PARAMETER" server, the <A HREF="smb.conf.5.html#ADDPRINTERCOMMAND" TARGET="_top" -><TT +><VAR CLASS="PARAMETER" -><I >add -printer command</I -></TT +printer command</VAR ></A > must have a defined value. The program hook must successfully add the printer to the system (i.e. @@ -11338,35 +10760,29 @@ CLASS="FILENAME" not exist, <B CLASS="COMMAND" >smbd</B -> will execute the <TT +> will execute the <VAR CLASS="PARAMETER" -><I >add printer -command</I -></TT +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 -<TT +<VAR CLASS="PARAMETER" -><I ->add printer program</I -></TT +>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" -><TT +><VAR CLASS="PARAMETER" -><I >delete -printer command</I -></TT +printer command</VAR ></A > for removing entries from the "Printers..." folder.</P @@ -11374,11 +10790,9 @@ folder.</P >The following is an example <A HREF="smb.conf.5.html#ADDPRINTERCOMMAN" TARGET="_top" -><TT +><VAR CLASS="PARAMETER" -><I ->add printer command</I -></TT +>add printer command</VAR ></A > script. It adds the appropriate entries to <TT CLASS="FILENAME" @@ -11413,8 +10827,8 @@ echo " :sd=/var/spool/lpd/$2:\\" >> $PRINTCAP echo " :mx=0:ml=0:sh:\\" >> $PRINTCAP echo " :lp=/usr/local/samba/var/print/$5.prn:" >> $PRINTCAP -touch "/usr/local/samba/var/print/$5.prn" >> /tmp/printadd.$$ 2>&1 -chown $LP "/usr/local/samba/var/print/$5.prn" >> /tmp/printadd.$$ 2>&1 +touch "/usr/local/samba/var/print/$5.prn" >> /tmp/printadd.$$ 2>&1 +chown $LP "/usr/local/samba/var/print/$5.prn" >> /tmp/printadd.$$ 2>&1 mkdir /var/spool/lpd/$2 chmod 700 /var/spool/lpd/$2 @@ -11439,9 +10853,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN2176" -></A ->13.2.5. Samba and Printer Ports</H3 +NAME="AEN2079" +>13.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 @@ -11460,12 +10874,10 @@ CLASS="FILENAME" > possesses a <A HREF="smb.conf.5.html#ENUMPORTSCOMMAND" TARGET="_top" -><TT +><VAR CLASS="PARAMETER" -><I >enumports -command</I -></TT +command</VAR ></A > which can be used to define an external program that generates a listing of ports on a system.</P @@ -11476,9 +10888,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN2184" -></A ->13.3. The Imprints Toolset</H2 +NAME="AEN2087" +>13.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 @@ -11494,9 +10906,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN2188" -></A ->13.3.1. What is Imprints?</H3 +NAME="AEN2091" +>13.3.1. What is Imprints?</A +></H3 ><P >Imprints is a collection of tools for supporting the goals of</P @@ -11526,9 +10938,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN2198" -></A ->13.3.2. Creating Printer Driver Packages</H3 +NAME="AEN2101" +>13.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 @@ -11542,9 +10954,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN2201" -></A ->13.3.3. The Imprints server</H3 +NAME="AEN2104" +>13.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 @@ -11566,9 +10978,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN2205" -></A ->13.3.4. The Installation Client</H3 +NAME="AEN2108" +>13.3.4. The Installation Client</A +></H3 ><P >More information regarding the Imprints installation client is available in the <TT @@ -11660,17 +11072,17 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN2227" -></A ->13.4. Diagnosis</H2 +NAME="AEN2130" +>13.4. Diagnosis</A +></H2 ><DIV CLASS="SECT2" ><H3 CLASS="SECT2" ><A -NAME="AEN2229" -></A ->13.4.1. Introduction</H3 +NAME="AEN2132" +>13.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 @@ -11732,7 +11144,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 @@ -11743,9 +11155,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN2245" -></A ->13.4.2. Debugging printer problems</H3 +NAME="AEN2148" +>13.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 @@ -11761,7 +11173,7 @@ CLASS="PROGRAMLISTING" /usr/bin/id -p >/tmp/tmp.print # we run the command and save the error messages # replace the command with the one appropriate for your system - /usr/bin/lpr -r -P$1 $2 2>>&/tmp/tmp.print</PRE + /usr/bin/lpr -r -P$1 $2 2>>&/tmp/tmp.print</PRE ></P ><P >Then you print a file and try removing it. You may find that the @@ -11800,9 +11212,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN2254" -></A ->13.4.3. What printers do I have?</H3 +NAME="AEN2157" +>13.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 @@ -11829,9 +11241,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN2262" -></A ->13.4.4. Setting up printcap and print servers</H3 +NAME="AEN2165" +>13.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 @@ -11913,9 +11325,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN2290" -></A ->13.4.5. Job sent, no output</H3 +NAME="AEN2193" +>13.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 @@ -11958,9 +11370,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN2301" -></A ->13.4.6. Job sent, strange output</H3 +NAME="AEN2204" +>13.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 @@ -12004,9 +11416,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN2313" -></A ->13.4.7. Raw PostScript printed</H3 +NAME="AEN2216" +>13.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 @@ -12019,9 +11431,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN2316" -></A ->13.4.8. Advanced Printing</H3 +NAME="AEN2219" +>13.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. @@ -12035,9 +11447,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN2319" -></A ->13.4.9. Real debugging</H3 +NAME="AEN2222" +>13.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 @@ -12056,9 +11468,9 @@ CLASS="SECT1" ><H2 CLASS="SECT1" ><A -NAME="AEN2360" -></A ->14.1. Abstract</H2 +NAME="AEN2263" +>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 @@ -12083,9 +11495,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN2364" -></A ->14.2. Introduction</H2 +NAME="AEN2267" +>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 @@ -12137,9 +11549,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN2377" -></A ->14.3. What Winbind Provides</H2 +NAME="AEN2280" +>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 @@ -12179,9 +11591,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN2384" -></A ->14.3.1. Target Uses</H3 +NAME="AEN2287" +>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 @@ -12203,9 +11615,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN2388" -></A ->14.4. How Winbind Works</H2 +NAME="AEN2291" +>14.4. How Winbind Works</A +></H2 ><P >The winbind system is designed around a client/server architecture. A long running <B @@ -12223,9 +11635,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN2393" -></A ->14.4.1. Microsoft Remote Procedure Calls</H3 +NAME="AEN2296" +>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 @@ -12249,9 +11661,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN2397" -></A ->14.4.2. Microsoft Active Directory Services</H3 +NAME="AEN2300" +>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 @@ -12268,9 +11680,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN2400" -></A ->14.4.3. Name Service Switch</H3 +NAME="AEN2303" +>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 @@ -12348,9 +11760,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN2416" -></A ->14.4.4. Pluggable Authentication Modules</H3 +NAME="AEN2319" +>14.4.4. Pluggable Authentication Modules</A +></H3 ><P >Pluggable Authentication Modules, also known as PAM, is a system for abstracting authentication and authorization @@ -12397,9 +11809,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN2424" -></A ->14.4.5. User and Group ID Allocation</H3 +NAME="AEN2327" +>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 @@ -12423,9 +11835,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN2428" -></A ->14.4.6. Result Caching</H3 +NAME="AEN2331" +>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 @@ -12446,9 +11858,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN2431" -></A ->14.5. Installation and Configuration</H2 +NAME="AEN2334" +>14.5. Installation and Configuration</A +></H2 ><P >Many thanks to John Trostel <A HREF="mailto:jtrostel@snapserver.com" @@ -12473,9 +11885,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN2438" -></A ->14.5.1. Introduction</H3 +NAME="AEN2341" +>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 @@ -12532,9 +11944,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN2451" -></A ->14.5.2. Requirements</H3 +NAME="AEN2354" +>14.5.2. Requirements</A +></H3 ><P >If you have a samba configuration file that you are currently using... <SPAN @@ -12602,9 +12014,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN2465" -></A ->14.5.3. Testing Things Out</H3 +NAME="AEN2368" +>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 @@ -12647,9 +12059,9 @@ CLASS="SECT3" ><HR><H4 CLASS="SECT3" ><A -NAME="AEN2476" -></A ->14.5.3.1. Configure and compile SAMBA</H4 +NAME="AEN2379" +>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 @@ -12657,44 +12069,44 @@ whether or not you have previously built the Samba binaries.</P ><P ><PRE CLASS="PROGRAMLISTING" -><TT +><SAMP CLASS="PROMPT" ->root#</TT +>root#</SAMP > <B CLASS="COMMAND" >autoconf</B > -<TT +<SAMP CLASS="PROMPT" ->root#</TT +>root#</SAMP > <B CLASS="COMMAND" >make clean</B > -<TT +<SAMP CLASS="PROMPT" ->root#</TT +>root#</SAMP > <B CLASS="COMMAND" >rm config.cache</B > -<TT +<SAMP CLASS="PROMPT" ->root#</TT +>root#</SAMP > <B CLASS="COMMAND" >./configure</B > -<TT +<SAMP CLASS="PROMPT" ->root#</TT +>root#</SAMP > <B CLASS="COMMAND" >make</B > -<TT +<SAMP CLASS="PROMPT" ->root#</TT +>root#</SAMP > <B CLASS="COMMAND" >make install</B @@ -12713,13 +12125,13 @@ CLASS="SECT3" ><HR><H4 CLASS="SECT3" ><A -NAME="AEN2495" -></A +NAME="AEN2398" >14.5.3.2. Configure <TT CLASS="FILENAME" >nsswitch.conf</TT > and the -winbind libraries</H4 +winbind libraries</A +></H4 ><P >The libraries needed to run the <B CLASS="COMMAND" @@ -12727,9 +12139,9 @@ CLASS="COMMAND" > daemon through nsswitch need to be copied to their proper locations, so</P ><P -><TT +><SAMP CLASS="PROMPT" ->root#</TT +>root#</SAMP > <B CLASS="COMMAND" >cp ../samba/source/nsswitch/libnss_winbind.so /lib</B @@ -12737,9 +12149,9 @@ CLASS="COMMAND" ><P >I also found it necessary to make the following symbolic link:</P ><P -><TT +><SAMP CLASS="PROMPT" ->root#</TT +>root#</SAMP > <B CLASS="COMMAND" >ln -s /lib/libnss_winbind.so /lib/libnss_winbind.so.2</B @@ -12747,23 +12159,23 @@ CLASS="COMMAND" ><P >And, in the case of Sun solaris:</P ><P -><TT +><SAMP CLASS="PROMPT" ->root#</TT +>root#</SAMP > <B CLASS="COMMAND" >ln -s /usr/lib/libnss_winbind.so /usr/lib/libnss_winbind.so.1</B > -<TT +<SAMP CLASS="PROMPT" ->root#</TT +>root#</SAMP > <B CLASS="COMMAND" >ln -s /usr/lib/libnss_winbind.so /usr/lib/nss_winbind.so.1</B > -<TT +<SAMP CLASS="PROMPT" ->root#</TT +>root#</SAMP > <B CLASS="COMMAND" >ln -s /usr/lib/libnss_winbind.so /usr/lib/nss_winbind.so.2</B @@ -12799,9 +12211,9 @@ CLASS="COMMAND" your system reboots, but it is faster (and you don't need to reboot) if you do it manually:</P ><P -><TT +><SAMP CLASS="PROMPT" ->root#</TT +>root#</SAMP > <B CLASS="COMMAND" >/sbin/ldconfig -v | grep winbind</B @@ -12818,9 +12230,9 @@ CLASS="SECT3" ><HR><H4 CLASS="SECT3" ><A -NAME="AEN2528" -></A ->14.5.3.3. Configure smb.conf</H4 +NAME="AEN2431" +>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 @@ -12845,7 +12257,7 @@ include the following entries in the [global] section:</P ><PRE CLASS="PROGRAMLISTING" >[global] - <...> + <...> # separate domain and username with '+', like DOMAIN+username <A HREF="winbindd.8.html#WINBINDSEPARATOR" @@ -12893,44 +12305,36 @@ CLASS="SECT3" ><HR><H4 CLASS="SECT3" ><A -NAME="AEN2544" -></A ->14.5.3.4. Join the SAMBA server to the PDC domain</H4 +NAME="AEN2447" +>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 <TT +PDC domain, where <VAR CLASS="REPLACEABLE" -><I ->DOMAIN</I -></TT +>DOMAIN</VAR > is the name of -your Windows domain and <TT +your Windows domain and <VAR CLASS="REPLACEABLE" -><I ->Administrator</I -></TT +>Administrator</VAR > is a domain user who has administrative privileges in the domain.</P ><P -><TT +><SAMP CLASS="PROMPT" ->root#</TT +>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 -<TT +<VAR CLASS="REPLACEABLE" -><I ->DOMAIN</I -></TT ->" where <TT +>DOMAIN</VAR +>" where <VAR CLASS="REPLACEABLE" -><I ->DOMAIN</I -></TT +>DOMAIN</VAR > is your DOMAIN name.</P ></DIV @@ -12939,9 +12343,9 @@ CLASS="SECT3" ><HR><H4 CLASS="SECT3" ><A -NAME="AEN2555" -></A ->14.5.3.5. Start up the winbindd daemon and test it!</H4 +NAME="AEN2458" +>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 @@ -12949,9 +12353,9 @@ SAMBA start, but it is possible to test out just the winbind portion first. To start up winbind services, enter the following command as root:</P ><P -><TT +><SAMP CLASS="PROMPT" ->root#</TT +>root#</SAMP > <B CLASS="COMMAND" >/usr/local/samba/bin/winbindd</B @@ -12960,9 +12364,9 @@ CLASS="COMMAND" >I'm always paranoid and like to make sure the daemon is really running...</P ><P -><TT +><SAMP CLASS="PROMPT" ->root#</TT +>root#</SAMP > <B CLASS="COMMAND" >ps -ae | grep winbindd</B @@ -12975,9 +12379,9 @@ CLASS="COMMAND" >Now... for the real test, try to get some information about the users on your PDC</P ><P -><TT +><SAMP CLASS="PROMPT" ->root#</TT +>root#</SAMP > <B CLASS="COMMAND" >/usr/local/samba/bin/wbinfo -u</B @@ -12997,12 +12401,10 @@ CEO+krbtgt CEO+TsInternetUser</PRE ></P ><P ->Obviously, I have named my domain 'CEO' and my <TT +>Obviously, I have named my domain 'CEO' and my <VAR CLASS="PARAMETER" -><I >winbind -separator</I -></TT +separator</VAR > is '+'.</P ><P >You can do the same sort of thing to get group information from @@ -13010,9 +12412,9 @@ the PDC:</P ><P ><PRE CLASS="PROGRAMLISTING" -><TT +><SAMP CLASS="PROMPT" ->root#</TT +>root#</SAMP > <B CLASS="COMMAND" >/usr/local/samba/bin/wbinfo -g</B @@ -13032,9 +12434,9 @@ CEO+Group Policy Creator Owners</PRE lists of both local and PDC users and groups. Try the following command:</P ><P -><TT +><SAMP CLASS="PROMPT" ->root#</TT +>root#</SAMP > <B CLASS="COMMAND" >getent passwd</B @@ -13049,9 +12451,9 @@ directories and default shells.</P ><P >The same thing can be done for groups with the command</P ><P -><TT +><SAMP CLASS="PROMPT" ->root#</TT +>root#</SAMP > <B CLASS="COMMAND" >getent group</B @@ -13062,17 +12464,17 @@ CLASS="SECT3" ><HR><H4 CLASS="SECT3" ><A -NAME="AEN2591" -></A ->14.5.3.6. Fix the init.d startup scripts</H4 +NAME="AEN2494" +>14.5.3.6. Fix the init.d startup scripts</A +></H4 ><DIV CLASS="SECT4" ><H5 CLASS="SECT4" ><A -NAME="AEN2593" -></A ->14.5.3.6.1. Linux</H5 +NAME="AEN2496" +>14.5.3.6.1. Linux</A +></H5 ><P >The <B CLASS="COMMAND" @@ -13129,7 +12531,7 @@ CLASS="PROGRAMLISTING" daemon /usr/local/samba/bin/winbindd RETVAL3=$? echo - [ $RETVAL -eq 0 -a $RETVAL2 -eq 0 -a $RETVAL3 -eq 0 ] && touch /var/lock/subsys/smb || \ + [ $RETVAL -eq 0 -a $RETVAL2 -eq 0 -a $RETVAL3 -eq 0 ] && touch /var/lock/subsys/smb || \ RETVAL=1 return $RETVAL }</PRE @@ -13155,7 +12557,7 @@ CLASS="PROGRAMLISTING" echo -n $"Shutting down $KIND services: " killproc winbindd RETVAL3=$? - [ $RETVAL -eq 0 -a $RETVAL2 -eq 0 -a $RETVAL3 -eq 0 ] && rm -f /var/lock/subsys/smb + [ $RETVAL -eq 0 -a $RETVAL2 -eq 0 -a $RETVAL3 -eq 0 ] && rm -f /var/lock/subsys/smb echo "" return $RETVAL }</PRE @@ -13166,9 +12568,9 @@ CLASS="SECT4" ><HR><H5 CLASS="SECT4" ><A -NAME="AEN2610" -></A ->14.5.3.6.2. Solaris</H5 +NAME="AEN2513" +>14.5.3.6.2. Solaris</A +></H5 ><P >On solaris, you need to modify the <TT @@ -13197,7 +12599,7 @@ killproc() { # kill the named process(es) pid=`/usr/bin/ps -e | /usr/bin/grep -w $1 | /usr/bin/sed -e 's/^ *//' -e 's/ .*//'` - [ "$pid" != "" ] && kill $pid + [ "$pid" != "" ] && kill $pid } # Start/stop processes required for samba server @@ -13237,9 +12639,9 @@ CLASS="SECT4" ><HR><H5 CLASS="SECT4" ><A -NAME="AEN2617" -></A ->14.5.3.6.3. Restarting</H5 +NAME="AEN2520" +>14.5.3.6.3. Restarting</A +></H5 ><P >If you restart the <B CLASS="COMMAND" @@ -13261,9 +12663,9 @@ CLASS="SECT3" ><HR><H4 CLASS="SECT3" ><A -NAME="AEN2623" -></A ->14.5.3.7. Configure Winbind and PAM</H4 +NAME="AEN2526" +>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 @@ -13281,9 +12683,9 @@ CLASS="FILENAME" > directory by invoking the command</P ><P -><TT +><SAMP CLASS="PROMPT" ->root#</TT +>root#</SAMP > <B CLASS="COMMAND" >make nsswitch/pam_winbind.so</B @@ -13307,9 +12709,9 @@ CLASS="FILENAME" >/usr/lib/security</TT >.</P ><P -><TT +><SAMP CLASS="PROMPT" ->root#</TT +>root#</SAMP > <B CLASS="COMMAND" >cp ../samba/source/nsswitch/pam_winbind.so /lib/security</B @@ -13319,9 +12721,9 @@ CLASS="SECT4" ><HR><H5 CLASS="SECT4" ><A -NAME="AEN2640" -></A ->14.5.3.7.1. Linux/FreeBSD-specific PAM configuration</H5 +NAME="AEN2543" +>14.5.3.7.1. Linux/FreeBSD-specific PAM configuration</A +></H5 ><P >The <TT CLASS="FILENAME" @@ -13448,9 +12850,9 @@ CLASS="SECT4" ><HR><H5 CLASS="SECT4" ><A -NAME="AEN2673" -></A ->14.5.3.7.2. Solaris-specific configuration</H5 +NAME="AEN2576" +>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 @@ -13535,9 +12937,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN2680" -></A ->14.6. Limitations</H2 +NAME="AEN2583" +>14.6. Limitations</A +></H2 ><P >Winbind has a number of limitations in its current released version that we hope to overcome in future @@ -13577,9 +12979,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN2690" -></A ->14.7. Conclusion</H2 +NAME="AEN2593" +>14.7. Conclusion</A +></H2 ><P >The winbind system, through the use of the Name Service Switch, Pluggable Authentication Modules, and appropriate @@ -13601,9 +13003,9 @@ CLASS="SECT1" ><H2 CLASS="SECT1" ><A -NAME="AEN2700" -></A ->15.1. Overview of browsing</H2 +NAME="AEN2603" +>15.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 "browse list". This list @@ -13614,8 +13016,13 @@ list is heavily used by all SMB clients. Configuration of SMB browsing has been problematic for some Samba users, hence this document.</P ><P ->Browsing will NOT work if name resolution from NetBIOS names to IP -addresses does not function correctly. Use of a WINS server is highly +>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 @@ -13625,16 +13032,14 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN2704" -></A ->15.2. Browsing support in samba</H2 -><P ->Samba now fully supports browsing. The browsing is supported by nmbd -and is also controlled by options in the smb.conf file (see smb.conf(5)).</P +NAME="AEN2608" +>15.2. Browsing support in samba</A +></H2 ><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 +>Samba facilitates browsing. The browsing is supported by nmbd +and is also controlled by options in the smb.conf file (see smb.conf(5)). +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 @@ -13649,12 +13054,12 @@ regardless of whether it is NT, Samba or any other type of domain master that is providing this service.</P ><P >[Note that nmbd can be configured as a WINS server, but it is not -necessary to specifically use samba as your WINS server. NTAS can -be configured as your WINS server. In a mixed NT server and -samba environment on a Wide Area Network, it is recommended that -you use the NT server's WINS server capabilities. In a samba-only -environment, it is recommended that you use one and only one nmbd -as your WINS server].</P +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 ><P >To get browsing to work you need to run nmbd as usual, but will need to use the "workgroup" option in smb.conf to control what workgroup @@ -13670,9 +13075,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN2713" -></A ->15.3. Problem resolution</H2 +NAME="AEN2616" +>15.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 @@ -13688,6 +13093,19 @@ filemanager should display the list of available shares.</P 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 >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 @@ -13704,11 +13122,11 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN2720" -></A ->15.4. Browsing across subnets</H2 +NAME="AEN2625" +>15.4. Browsing across subnets</A +></H2 ><P ->With the release of Samba 1.9.17(alpha1 and above) Samba has been +>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 @@ -13735,15 +13153,14 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN2725" -></A ->15.4.1. How does cross subnet browsing work ?</H3 +NAME="AEN2630" +>15.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. -However, with the 1.9.17 release, Samba is capable of cross subnet -browsing when configured correctly.</P +Samba is capable of cross subnet browsing when configured correctly.</P ><P >Consider a network set up as follows :</P ><P @@ -13824,7 +13241,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 @@ -13947,9 +13364,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN2760" -></A ->15.5. Setting up a WINS server</H2 +NAME="AEN2665" +>15.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 @@ -13961,9 +13378,9 @@ CLASS="COMMAND" > wins support = yes</B ></P ><P ->Versions of Samba previous to 1.9.17 had this parameter default to +>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 1.9.17 or above, or at the very +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 @@ -14001,10 +13418,10 @@ 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 smb.conf file of the Samba @@ -14015,7 +13432,7 @@ CLASS="COMMAND" >" option and the "<B CLASS="COMMAND" ->wins server = >name<</B +>wins server = <name></B >" option then nmbd will fail to start.</P ><P @@ -14030,9 +13447,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN2779" -></A ->15.6. Setting up Browsing in a WORKGROUP</H2 +NAME="AEN2684" +>15.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 @@ -14073,11 +13490,12 @@ server, if you require.</P ><P >Next, you should ensure that each of the subnets contains a machine that can act as a local master browser for the -workgroup. Any NT machine should be able to do this, as will -Windows 95 machines (although these tend to get rebooted more -often, so it's not such a good idea to use these). To make a -Samba server a local master browser set the following -options in the [global] section of the smb.conf file :</P +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 +smb.conf file :</P ><P ><PRE CLASS="PROGRAMLISTING" @@ -14114,16 +13532,16 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN2797" -></A ->15.7. Setting up Browsing in a DOMAIN</H2 +NAME="AEN2702" +>15.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 (DOMAIN>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 @@ -14165,9 +13583,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN2807" -></A ->15.8. Forcing samba to be the master</H2 +NAME="AEN2712" +>15.8. Forcing samba to be the master</A +></H2 ><P >Who becomes the "master browser" is determined by an election process using broadcasts. Each election packet contains a number of parameters @@ -14180,8 +13598,8 @@ option in smb.conf to a higher number. It defaults to 0. Using 34 would make it win all elections over every other system (except other samba systems!)</P ><P ->A "os level" of 2 would make it beat WfWg and Win95, but not NTAS. A -NTAS domain controller uses level 32.</P +>A "os level" 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 @@ -14213,9 +13631,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN2816" -></A ->15.9. Making samba the domain master</H2 +NAME="AEN2721" +>15.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 @@ -14286,9 +13704,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN2834" -></A ->15.10. Note about broadcast addresses</H2 +NAME="AEN2739" +>15.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 @@ -14300,9 +13718,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN2837" -></A ->15.11. Multiple interfaces</H2 +NAME="AEN2742" +>15.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 "interfaces" @@ -14321,9 +13739,9 @@ CLASS="SECT1" ><H2 CLASS="SECT1" ><A -NAME="AEN2855" -></A ->16.1. Introduction and configuration</H2 +NAME="AEN2760" +>16.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. @@ -14362,17 +13780,17 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN2864" -></A ->16.2. Included modules</H2 +NAME="AEN2769" +>16.2. Included modules</A +></H2 ><DIV CLASS="SECT2" ><H3 CLASS="SECT2" ><A -NAME="AEN2866" -></A ->16.2.1. audit</H3 +NAME="AEN2771" +>16.2.1. audit</A +></H3 ><P >A simple module to audit file access to the syslog facility. The following operations are logged: @@ -14408,9 +13826,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN2874" -></A ->16.2.2. recycle</H3 +NAME="AEN2779" +>16.2.2. recycle</A +></H3 ><P >A recycle-bin like modules. When used any unlink call will be intercepted and files moved to the recycle @@ -14479,9 +13897,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN2911" -></A ->16.2.3. netatalk</H3 +NAME="AEN2816" +>16.2.3. netatalk</A +></H3 ><P >A netatalk module, that will ease co-existence of samba and netatalk file sharing services.</P @@ -14512,9 +13930,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN2918" -></A ->16.3. VFS modules available elsewhere</H2 +NAME="AEN2823" +>16.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 @@ -14528,9 +13946,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN2922" -></A ->16.3.1. DatabaseFS</H3 +NAME="AEN2827" +>16.3.1. DatabaseFS</A +></H3 ><P >URL: <A HREF="http://www.css.tayloru.edu/~elorimer/databasefs/index.php" @@ -14562,9 +13980,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN2930" -></A ->16.3.2. vscan</H3 +NAME="AEN2835" +>16.3.2. vscan</A +></H3 ><P >URL: <A HREF="http://www.openantivirus.org/" @@ -14584,181 +14002,9 @@ by Rainer Link.</P CLASS="CHAPTER" ><HR><H1 ><A -NAME="CVS-ACCESS" -></A ->Chapter 17. Access Samba source code via CVS</H1 -><DIV -CLASS="SECT1" -><H2 -CLASS="SECT1" -><A -NAME="AEN2942" -></A ->17.1. Introduction</H2 -><P ->Samba is developed in an open environment. Developers use CVS -(Concurrent Versioning System) to "checkin" (also known as -"commit") new source code. Samba's various CVS branches can -be accessed via anonymous CVS using the instructions -detailed in this chapter.</P -><P ->This document is a modified version of the instructions found at -<A -HREF="http://samba.org/samba/cvs.html" -TARGET="_top" ->http://samba.org/samba/cvs.html</A -></P -></DIV -><DIV -CLASS="SECT1" -><HR><H2 -CLASS="SECT1" -><A -NAME="AEN2947" -></A ->17.2. CVS Access to samba.org</H2 -><P ->The machine samba.org runs a publicly accessible CVS -repository for access to the source code of several packages, -including samba, rsync and jitterbug. There are two main ways of -accessing the CVS server on this host.</P -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN2950" -></A ->17.2.1. Access via CVSweb</H3 -><P ->You can access the source code via your -favourite WWW browser. This allows you to access the contents of -individual files in the repository and also to look at the revision -history and commit logs of individual files. You can also ask for a diff -listing between any two versions on the repository.</P -><P ->Use the URL : <A -HREF="http://samba.org/cgi-bin/cvsweb" -TARGET="_top" ->http://samba.org/cgi-bin/cvsweb</A -></P -></DIV -><DIV -CLASS="SECT2" -><HR><H3 -CLASS="SECT2" -><A -NAME="AEN2955" -></A ->17.2.2. Access via cvs</H3 -><P ->You can also access the source code via a -normal cvs client. This gives you much more control over you can -do with the repository and allows you to checkout whole source trees -and keep them up to date via normal cvs commands. This is the -preferred method of access if you are a developer and not -just a casual browser.</P -><P ->To download the latest cvs source code, point your -browser at the URL : <A -HREF="http://www.cyclic.com/" -TARGET="_top" ->http://www.cyclic.com/</A ->. -and click on the 'How to get cvs' link. CVS is free software under -the GNU GPL (as is Samba). Note that there are several graphical CVS clients -which provide a graphical interface to the sometimes mundane CVS commands. -Links to theses clients are also available from http://www.cyclic.com.</P -><P ->To gain access via anonymous cvs use the following steps. -For this example it is assumed that you want a copy of the -samba source code. For the other source code repositories -on this system just substitute the correct package name</P -><P -></P -><OL -TYPE="1" -><LI -><P -> Install a recent copy of cvs. All you really need is a - copy of the cvs client binary. - </P -></LI -><LI -><P -> Run the command - </P -><P -> <B -CLASS="COMMAND" ->cvs -d :pserver:cvs@samba.org:/cvsroot login</B -> - </P -><P -> When it asks you for a password type <TT -CLASS="USERINPUT" -><B ->cvs</B -></TT ->. - </P -></LI -><LI -><P -> Run the command - </P -><P -> <B -CLASS="COMMAND" ->cvs -d :pserver:cvs@samba.org:/cvsroot co samba</B -> - </P -><P -> This will create a directory called samba containing the - latest samba source code (i.e. the HEAD tagged cvs branch). This - currently corresponds to the 3.0 development tree. - </P -><P -> CVS branches other HEAD can be obtained by using the <TT -CLASS="PARAMETER" -><I ->-r</I -></TT -> - and defining a tag name. A list of branch tag names can be found on the - "Development" page of the samba web site. A common request is to obtain the - latest 2.2 release code. This could be done by using the following command. - </P -><P -> <B -CLASS="COMMAND" ->cvs -d :pserver:cvs@samba.org:/cvsroot co -r SAMBA_2_2 samba</B -> - </P -></LI -><LI -><P -> Whenever you want to merge in the latest code changes use - the following command from within the samba directory: - </P -><P -> <B -CLASS="COMMAND" ->cvs update -d -P</B -> - </P -></LI -></OL -></DIV -></DIV -></DIV -><DIV -CLASS="CHAPTER" -><HR><H1 -><A NAME="GROUPMAPPING" ></A ->Chapter 18. Group mapping HOWTO</H1 +>Chapter 17. Group mapping HOWTO</H1 ><P > Starting with Samba 3.0 alpha 2, a new group mapping function is available. The @@ -14859,15 +14105,15 @@ CLASS="CHAPTER" ><A NAME="SPEED" ></A ->Chapter 19. Samba performance issues</H1 +>Chapter 18. Samba performance issues</H1 ><DIV CLASS="SECT1" ><H2 CLASS="SECT1" ><A -NAME="AEN3033" -></A ->19.1. Comparisons</H2 +NAME="AEN2890" +>18.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 @@ -14896,9 +14142,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN3039" -></A ->19.2. Socket options</H2 +NAME="AEN2896" +>18.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 @@ -14924,9 +14170,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN3046" -></A ->19.3. Read size</H2 +NAME="AEN2903" +>18.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 @@ -14950,9 +14196,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN3051" -></A ->19.4. Max xmit</H2 +NAME="AEN2908" +>18.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 @@ -14973,9 +14219,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN3056" -></A ->19.5. Log level</H2 +NAME="AEN2913" +>18.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 @@ -14987,9 +14233,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN3059" -></A ->19.6. Read raw</H2 +NAME="AEN2916" +>18.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, @@ -15009,9 +14255,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN3064" -></A ->19.7. Write raw</H2 +NAME="AEN2921" +>18.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, @@ -15026,9 +14272,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN3068" -></A ->19.8. Slow Clients</H2 +NAME="AEN2925" +>18.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 @@ -15043,9 +14289,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN3072" -></A ->19.9. Slow Logins</H2 +NAME="AEN2929" +>18.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 @@ -15056,9 +14302,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN3075" -></A ->19.10. Client tuning</H2 +NAME="AEN2932" +>18.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 @@ -15164,15 +14410,15 @@ CLASS="CHAPTER" ><A NAME="GROUPPROFILES" ></A ->Chapter 20. Creating Group Profiles</H1 +>Chapter 19. Creating Group Prolicy Files</H1 ><DIV CLASS="SECT1" ><H2 CLASS="SECT1" ><A -NAME="AEN3123" -></A ->20.1. Windows '9x</H2 +NAME="AEN2980" +>19.1. Windows '9x</A +></H2 ><P >You need the Win98 Group Policy Editor to set Group Profiles up under Windows '9x. It can be found on the Original @@ -15196,25 +14442,28 @@ CLASS="FILENAME" > that needs to be placed in the root of the [NETLOGON] share. If your Win98 is configured to log onto the Samba Domain, it will automatically read this file and update the -Win98 registry of the machine that is logging on.</P +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 Win98 will check the +>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 Win98 machine. Hence, you will notice -things changing back to the original settings.</P +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" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN3132" -></A ->20.2. Windows NT 4</H2 +NAME="AEN2990" +>19.2. Windows NT 4</A +></H2 ><P ->Unfortunately, the Resource Kit info is Win NT4/2K version specific.</P +>Unfortunately, the Resource Kit info is Win NT4 or 200x specific.</P ><P >Here is a quick guide:</P ><P @@ -15249,7 +14498,7 @@ ALT="Note"></TD ALIGN="LEFT" VALIGN="TOP" ><P ->I am using the term "migrate" lossely. You can copy a profile to +>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 @@ -15291,9 +14540,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN3155" -></A ->20.2.1. Side bar Notes</H3 +NAME="AEN3013" +>19.2.1. Side bar Notes</A +></H3 ><P >You should obtain the SID of your NT4 domain. You can use smbpasswd to do this. Read the man page.</P @@ -15307,9 +14556,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN3159" -></A ->20.2.2. Mandatory profiles</H3 +NAME="AEN3017" +>19.2.2. Mandatory profiles</A +></H3 ><P >The above method can be used to create mandatory profiles also. To convert a group profile into a mandatory profile simply locate the NTUser.DAT file @@ -15320,9 +14569,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN3162" -></A ->20.2.3. moveuser.exe</H3 +NAME="AEN3020" +>19.2.3. moveuser.exe</A +></H3 ><P >The W2K professional resource kit has moveuser.exe. moveuser.exe changes the security of a profile from one user to another. This allows the account @@ -15333,9 +14582,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN3165" -></A ->20.2.4. Get SID</H3 +NAME="AEN3023" +>19.2.4. Get SID</A +></H3 ><P >You can identify the SID by using GetSID.exe from the Windows NT Server 4.0 Resource Kit.</P @@ -15356,9 +14605,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN3170" -></A ->20.3. Windows 2000/XP</H2 +NAME="AEN3028" +>19.3. Windows 2000/XP</A +></H2 ><P >You must first convert the profile from a local profile to a domain profile on the MS Windows workstation as follows:</P @@ -15588,6 +14837,178 @@ changed).</P ></DIV ></DIV ></DIV +><DIV +CLASS="CHAPTER" +><HR><H1 +><A +NAME="SECURING-SAMBA" +></A +>Chapter 20. Securing Samba</H1 +><DIV +CLASS="SECT1" +><H2 +CLASS="SECT1" +><A +NAME="AEN3109" +>20.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="AEN3112" +>20.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 'hosts allow' and +'hosts deny' options in the Samba smb.conf 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="AEN3119" +>20.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="AEN3128" +>20.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="AEN3135" +>20.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="AEN3144" +>20.6. Upgrading Samba</A +></H2 +><P +>Please check regularly on http://www.samba.org/ 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 ><DIV CLASS="PART" @@ -15615,24 +15036,38 @@ HREF="#PORTABILITY" ><DL ><DT >21.1. <A -HREF="#AEN3251" +HREF="#AEN3156" >HPUX</A ></DT ><DT >21.2. <A -HREF="#AEN3257" +HREF="#AEN3162" >SCO Unix</A ></DT ><DT >21.3. <A -HREF="#AEN3261" +HREF="#AEN3166" >DNIX</A ></DT ><DT >21.4. <A -HREF="#AEN3290" +HREF="#AEN3195" >RedHat Linux Rembrandt-II</A ></DT +><DT +>21.5. <A +HREF="#AEN3201" +>AIX</A +></DT +><DD +><DL +><DT +>21.5.1. <A +HREF="#AEN3203" +>Sequential Read Ahead</A +></DT +></DL +></DD ></DL ></DD ><DT @@ -15644,37 +15079,37 @@ HREF="#OTHER-CLIENTS" ><DL ><DT >22.1. <A -HREF="#AEN3311" +HREF="#AEN3221" >Macintosh clients?</A ></DT ><DT >22.2. <A -HREF="#AEN3320" +HREF="#AEN3230" >OS2 Client</A ></DT ><DD ><DL ><DT >22.2.1. <A -HREF="#AEN3322" +HREF="#AEN3232" >How can I configure OS/2 Warp Connect or OS/2 Warp 4 as a client for Samba?</A ></DT ><DT >22.2.2. <A -HREF="#AEN3337" +HREF="#AEN3247" >How can I configure OS/2 Warp 3 (not Connect), OS/2 1.2, 1.3 or 2.x for Samba?</A ></DT ><DT >22.2.3. <A -HREF="#AEN3346" +HREF="#AEN3256" >Are there any other issues when OS/2 (any version) is used as a client?</A ></DT ><DT >22.2.4. <A -HREF="#AEN3350" +HREF="#AEN3260" >How do I get printer driver download working for OS/2 clients?</A ></DT @@ -15682,168 +15117,230 @@ HREF="#AEN3350" ></DD ><DT >22.3. <A -HREF="#AEN3360" +HREF="#AEN3270" >Windows for Workgroups</A ></DT ><DD ><DL ><DT >22.3.1. <A -HREF="#AEN3362" +HREF="#AEN3272" >Use latest TCP/IP stack from Microsoft</A ></DT ><DT >22.3.2. <A -HREF="#AEN3367" +HREF="#AEN3277" >Delete .pwl files after password change</A ></DT ><DT >22.3.3. <A -HREF="#AEN3372" +HREF="#AEN3282" >Configure WfW password handling</A ></DT ><DT >22.3.4. <A -HREF="#AEN3376" +HREF="#AEN3286" >Case handling of passwords</A ></DT +><DT +>22.3.5. <A +HREF="#AEN3291" +>Use TCP/IP as default protocol</A +></DT ></DL ></DD ><DT >22.4. <A -HREF="#AEN3381" +HREF="#AEN3294" >Windows '95/'98</A ></DT ><DT >22.5. <A -HREF="#AEN3397" +HREF="#AEN3310" >Windows 2000 Service Pack 2</A ></DT ></DL ></DD ><DT >23. <A -HREF="#BUGREPORT" ->Reporting Bugs</A +HREF="#COMPILING" +>How to compile SAMBA</A ></DT ><DD ><DL ><DT >23.1. <A -HREF="#AEN3421" +HREF="#AEN3337" +>Access Samba source code via CVS</A +></DT +><DD +><DL +><DT +>23.1.1. <A +HREF="#AEN3339" >Introduction</A ></DT ><DT +>23.1.2. <A +HREF="#AEN3344" +>CVS Access to samba.org</A +></DT +></DL +></DD +><DT >23.2. <A -HREF="#AEN3431" ->General info</A +HREF="#AEN3380" +>Accessing the samba sources via rsync and ftp</A ></DT ><DT >23.3. <A -HREF="#AEN3437" ->Debug levels</A +HREF="#AEN3386" +>Building the Binaries</A ></DT ><DT >23.4. <A -HREF="#AEN3454" +HREF="#AEN3414" +>Starting the smbd and nmbd</A +></DT +><DD +><DL +><DT +>23.4.1. <A +HREF="#AEN3424" +>Starting from inetd.conf</A +></DT +><DT +>23.4.2. <A +HREF="#AEN3453" +>Alternative: starting it as a daemon</A +></DT +></DL +></DD +></DL +></DD +><DT +>24. <A +HREF="#BUGREPORT" +>Reporting Bugs</A +></DT +><DD +><DL +><DT +>24.1. <A +HREF="#AEN3476" +>Introduction</A +></DT +><DT +>24.2. <A +HREF="#AEN3486" +>General info</A +></DT +><DT +>24.3. <A +HREF="#AEN3492" +>Debug levels</A +></DT +><DT +>24.4. <A +HREF="#AEN3509" >Internal errors</A ></DT ><DT ->23.5. <A -HREF="#AEN3464" +>24.5. <A +HREF="#AEN3519" >Attaching to a running process</A ></DT ><DT ->23.6. <A -HREF="#AEN3467" +>24.6. <A +HREF="#AEN3522" >Patches</A ></DT ></DL ></DD ><DT ->24. <A +>25. <A HREF="#DIAGNOSIS" ->Diagnosing your samba server</A +>The samba checklist</A ></DT ><DD ><DL ><DT ->24.1. <A -HREF="#AEN3490" +>25.1. <A +HREF="#AEN3545" >Introduction</A ></DT ><DT ->24.2. <A -HREF="#AEN3495" +>25.2. <A +HREF="#AEN3550" >Assumptions</A ></DT ><DT ->24.3. <A -HREF="#AEN3505" +>25.3. <A +HREF="#AEN3560" >Tests</A ></DT ><DD ><DL ><DT ->24.3.1. <A -HREF="#AEN3507" +>25.3.1. <A +HREF="#AEN3562" >Test 1</A ></DT ><DT ->24.3.2. <A -HREF="#AEN3513" +>25.3.2. <A +HREF="#AEN3568" >Test 2</A ></DT ><DT ->24.3.3. <A -HREF="#AEN3519" +>25.3.3. <A +HREF="#AEN3574" >Test 3</A ></DT ><DT ->24.3.4. <A -HREF="#AEN3534" +>25.3.4. <A +HREF="#AEN3589" >Test 4</A ></DT ><DT ->24.3.5. <A -HREF="#AEN3539" +>25.3.5. <A +HREF="#AEN3594" >Test 5</A ></DT ><DT ->24.3.6. <A -HREF="#AEN3545" +>25.3.6. <A +HREF="#AEN3600" >Test 6</A ></DT ><DT ->24.3.7. <A -HREF="#AEN3553" +>25.3.7. <A +HREF="#AEN3608" >Test 7</A ></DT ><DT ->24.3.8. <A -HREF="#AEN3579" +>25.3.8. <A +HREF="#AEN3634" >Test 8</A ></DT ><DT ->24.3.9. <A -HREF="#AEN3596" +>25.3.9. <A +HREF="#AEN3651" >Test 9</A ></DT ><DT ->24.3.10. <A -HREF="#AEN3604" +>25.3.10. <A +HREF="#AEN3659" >Test 10</A ></DT ><DT ->24.3.11. <A -HREF="#AEN3610" +>25.3.11. <A +HREF="#AEN3665" >Test 11</A ></DT ></DL ></DD ><DT ->24.4. <A -HREF="#AEN3615" +>25.4. <A +HREF="#AEN3670" >Still having troubles?</A ></DT ></DL @@ -15867,9 +15364,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN3251" -></A ->21.1. HPUX</H2 +NAME="AEN3156" +>21.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 @@ -15897,9 +15394,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN3257" -></A ->21.2. SCO Unix</H2 +NAME="AEN3162" +>21.2. SCO Unix</A +></H2 ><P > If you run an old version of SCO Unix then you may need to get important @@ -15914,9 +15411,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN3261" -></A ->21.3. DNIX</H2 +NAME="AEN3166" +>21.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 @@ -16021,9 +15518,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN3290" -></A ->21.4. RedHat Linux Rembrandt-II</H2 +NAME="AEN3195" +>21.4. RedHat Linux Rembrandt-II</A +></H2 ><P >By default RedHat Rembrandt-II during installation adds an entry to /etc/hosts as follows: @@ -16040,6 +15537,27 @@ 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" +><HR><H2 +CLASS="SECT1" +><A +NAME="AEN3201" +>21.5. AIX</A +></H2 +><DIV +CLASS="SECT2" +><H3 +CLASS="SECT2" +><A +NAME="AEN3203" +>21.5.1. Sequential Read Ahead</A +></H3 +><P +>Disabling Sequential Read Ahead using "vmtune -r 0" improves +samba performance significally.</P +></DIV +></DIV ></DIV ><DIV CLASS="CHAPTER" @@ -16055,9 +15573,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN3311" -></A ->22.1. Macintosh clients?</H2 +NAME="AEN3221" +>22.1. Macintosh clients?</A +></H2 ><P >Yes. <A HREF="http://www.thursby.com/" @@ -16101,18 +15619,18 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN3320" -></A ->22.2. OS2 Client</H2 +NAME="AEN3230" +>22.2. OS2 Client</A +></H2 ><DIV CLASS="SECT2" ><H3 CLASS="SECT2" ><A -NAME="AEN3322" -></A +NAME="AEN3232" >22.2.1. How can I configure OS/2 Warp Connect or - OS/2 Warp 4 as a client for Samba?</H3 + OS/2 Warp 4 as a client for Samba?</A +></H3 ><P >A more complete answer to this question can be found on <A @@ -16168,10 +15686,10 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN3337" -></A +NAME="AEN3247" >22.2.2. How can I configure OS/2 Warp 3 (not Connect), - OS/2 1.2, 1.3 or 2.x for Samba?</H3 + 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 @@ -16212,10 +15730,10 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN3346" -></A +NAME="AEN3256" >22.2.3. Are there any other issues when OS/2 (any version) - is used as a client?</H3 + 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 @@ -16234,10 +15752,10 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN3350" -></A +NAME="AEN3260" >22.2.4. How do I get printer driver download working - for OS/2 clients?</H3 + 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 @@ -16247,17 +15765,13 @@ NAME="AEN3350" ><P >Install the NT driver first for that printer. Then, add to your smb.conf a parameter, os2 driver map = - <TT + <VAR CLASS="REPLACEABLE" -><I ->filename</I -></TT +>filename</VAR >". Then, in the file - specified by <TT + specified by <VAR CLASS="REPLACEABLE" -><I ->filename</I -></TT +>filename</VAR >, map the name of the NT driver name to the OS/2 driver name as follows:</P @@ -16285,17 +15799,17 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN3360" -></A ->22.3. Windows for Workgroups</H2 +NAME="AEN3270" +>22.3. Windows for Workgroups</A +></H2 ><DIV CLASS="SECT2" ><H3 CLASS="SECT2" ><A -NAME="AEN3362" -></A ->22.3.1. Use latest TCP/IP stack from Microsoft</H3 +NAME="AEN3272" +>22.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 @@ -16315,9 +15829,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN3367" -></A ->22.3.2. Delete .pwl files after password change</H3 +NAME="AEN3277" +>22.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 @@ -16335,9 +15849,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN3372" -></A ->22.3.3. Configure WfW password handling</H3 +NAME="AEN3282" +>22.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 @@ -16354,9 +15868,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN3376" -></A ->22.3.4. Case handling of passwords</H3 +NAME="AEN3286" +>22.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" @@ -16367,15 +15881,30 @@ 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="AEN3291" +>22.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="AEN3381" -></A ->22.4. Windows '95/'98</H2 +NAME="AEN3294" +>22.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 @@ -16421,9 +15950,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN3397" -></A ->22.5. Windows 2000 Service Pack 2</H2 +NAME="AEN3310" +>22.5. Windows 2000 Service Pack 2</A +></H2 ><P > There are several annoyances with Windows 2000 SP2. One of which @@ -16503,17 +16032,513 @@ create accounts on the Samba host for Domain users.</I CLASS="CHAPTER" ><HR><H1 ><A +NAME="COMPILING" +></A +>Chapter 23. 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="AEN3337" +>23.1. Access Samba source code via CVS</A +></H2 +><DIV +CLASS="SECT2" +><H3 +CLASS="SECT2" +><A +NAME="AEN3339" +>23.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="AEN3344" +>23.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="AEN3347" +>23.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="AEN3352" +>23.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 +> <B +CLASS="COMMAND" +>cvs -d :pserver:cvs@samba.org:/cvsroot login</B +> + </P +><P +> When it asks you for a password type <KBD +CLASS="USERINPUT" +>cvs</KBD +>. + </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 <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 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="SECT1" +><HR><H2 +CLASS="SECT1" +><A +NAME="AEN3380" +>23.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="AEN3386" +>23.3. Building the Binaries</A +></H2 +><P +>To do this, first run the program <B +CLASS="COMMAND" +>./configure + </B +> in the source directory. This should automatically + configure Samba for your operating system. If you have unusual + needs then you may wish to run</P +><P +><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 +><DIV +CLASS="SECT1" +><HR><H2 +CLASS="SECT1" +><A +NAME="AEN3414" +>23.4. Starting the smbd and nmbd</A +></H2 +><P +>You must choose to start smbd and nmbd either + as daemons or from <B +CLASS="COMMAND" +>inetd</B +>. Don't try + to do both! Either you can put them in <TT +CLASS="FILENAME" +> inetd.conf</TT +> and have them started on demand + by <B +CLASS="COMMAND" +>inetd</B +>, or you can start them as + daemons either from the command line or in <TT +CLASS="FILENAME" +> /etc/rc.local</TT +>. See the man pages for details + on the command line options. Take particular care to read + the bit about what user you need to be in order to start + Samba. In many cases you must be root.</P +><P +>The main advantage of starting <B +CLASS="COMMAND" +>smbd</B +> + and <B +CLASS="COMMAND" +>nmbd</B +> using the recommended daemon method + is that they will respond slightly more quickly to an initial connection + request.</P +><DIV +CLASS="SECT2" +><HR><H3 +CLASS="SECT2" +><A +NAME="AEN3424" +>23.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 +><P +>NOTE: Some unixes already have entries like netbios_ns + (note the underscore) in <TT +CLASS="FILENAME" +>/etc/services</TT +>. + You must either edit <TT +CLASS="FILENAME" +>/etc/services</TT +> or + <TT +CLASS="FILENAME" +>/etc/inetd.conf</TT +> to make them consistent.</P +><P +>NOTE: On many systems you may need to use the + "interfaces" option in smb.conf to specify the IP address + and netmask of your interfaces. Run <B +CLASS="COMMAND" +>ifconfig</B +> + as root if you don't know what the broadcast is for your + net. <B +CLASS="COMMAND" +>nmbd</B +> tries to determine it at run + time, but fails on some unixes. See the section on "testing nmbd" + for a method of finding if you need to do this.</P +><P +>!!!WARNING!!! Many unixes only accept around 5 + parameters on the command line in <TT +CLASS="FILENAME" +>inetd.conf</TT +>. + This means you shouldn't use spaces between the options and + arguments, or you should use a script, and start the script + from <B +CLASS="COMMAND" +>inetd</B +>.</P +><P +>Restart <B +CLASS="COMMAND" +>inetd</B +>, perhaps just send + it a HUP. If you have installed an earlier version of <B +CLASS="COMMAND" +> nmbd</B +> then you may need to kill nmbd as well.</P +></DIV +><DIV +CLASS="SECT2" +><HR><H3 +CLASS="SECT2" +><A +NAME="AEN3453" +>23.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 +><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 +><DIV +CLASS="CHAPTER" +><HR><H1 +><A NAME="BUGREPORT" ></A ->Chapter 23. Reporting Bugs</H1 +>Chapter 24. Reporting Bugs</H1 ><DIV CLASS="SECT1" ><H2 CLASS="SECT1" ><A -NAME="AEN3421" -></A ->23.1. Introduction</H2 +NAME="AEN3476" +>24.1. Introduction</A +></H2 ><P >The email address for bug reports for stable releases is <A HREF="samba@samba.org" @@ -16556,9 +16581,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN3431" -></A ->23.2. General info</H2 +NAME="AEN3486" +>24.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 @@ -16581,9 +16606,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN3437" -></A ->23.3. Debug levels</H2 +NAME="AEN3492" +>24.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 @@ -16651,9 +16676,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN3454" -></A ->23.4. Internal errors</H2 +NAME="AEN3509" +>24.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 @@ -16695,9 +16720,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN3464" -></A ->23.5. Attaching to a running process</H2 +NAME="AEN3519" +>24.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 @@ -16712,9 +16737,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN3467" -></A ->23.6. Patches</H2 +NAME="AEN3522" +>24.6. Patches</A +></H2 ><P >The best sort of bug report is one that includes a fix! If you send us patches please use <B @@ -16735,15 +16760,15 @@ CLASS="CHAPTER" ><A NAME="DIAGNOSIS" ></A ->Chapter 24. Diagnosing your samba server</H1 +>Chapter 25. The samba checklist</H1 ><DIV CLASS="SECT1" ><H2 CLASS="SECT1" ><A -NAME="AEN3490" -></A ->24.1. Introduction</H2 +NAME="AEN3545" +>25.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 @@ -16763,9 +16788,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN3495" -></A ->24.2. Assumptions</H2 +NAME="AEN3550" +>25.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 @@ -16801,17 +16826,17 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN3505" -></A ->24.3. Tests</H2 +NAME="AEN3560" +>25.3. Tests</A +></H2 ><DIV CLASS="SECT2" ><H3 CLASS="SECT2" ><A -NAME="AEN3507" -></A ->24.3.1. Test 1</H3 +NAME="AEN3562" +>25.3.1. Test 1</A +></H3 ><P >In the directory in which you store your smb.conf file, run the command "testparm smb.conf". If it reports any errors then your smb.conf @@ -16831,9 +16856,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN3513" -></A ->24.3.2. Test 2</H3 +NAME="AEN3568" +>25.3.2. Test 2</A +></H3 ><P >Run the command "ping BIGSERVER" from the PC and "ping ACLIENT" from the unix box. If you don't get a valid response then your TCP/IP @@ -16857,9 +16882,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN3519" -></A ->24.3.3. Test 3</H3 +NAME="AEN3574" +>25.3.3. Test 3</A +></H3 ><P >Run the command "smbclient -L BIGSERVER" on the unix box. You should get a list of available shares back. </P @@ -16928,9 +16953,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN3534" -></A ->24.3.4. Test 4</H3 +NAME="AEN3589" +>25.3.4. Test 4</A +></H3 ><P >Run the command "nmblookup -B BIGSERVER __SAMBA__". You should get the IP address of your Samba server back.</P @@ -16949,9 +16974,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN3539" -></A ->24.3.5. Test 5</H3 +NAME="AEN3594" +>25.3.5. Test 5</A +></H3 ><P >run the command <B CLASS="COMMAND" @@ -16970,9 +16995,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN3545" -></A ->24.3.6. Test 6</H3 +NAME="AEN3600" +>25.3.6. Test 6</A +></H3 ><P >Run the command <B CLASS="COMMAND" @@ -17004,9 +17029,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN3553" -></A ->24.3.7. Test 7</H3 +NAME="AEN3608" +>25.3.7. Test 7</A +></H3 ><P >Run the command <B CLASS="COMMAND" @@ -17014,7 +17039,7 @@ CLASS="COMMAND" >. You should then be prompted for a password. You should use the password of the account you are logged into the unix box with. If you want to test with -another account then add the -U >accountname< option to the end of +another account then add the -U >accountname< option to the end of the command line. eg: <B CLASS="COMMAND" @@ -17080,7 +17105,7 @@ CLASS="COMMAND" > etc. Type <B CLASS="COMMAND" ->help >command<</B +>help >command<</B > for instructions. You should especially check that the amount of free disk space shown is correct when you type <B @@ -17093,9 +17118,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN3579" -></A ->24.3.8. Test 8</H3 +NAME="AEN3634" +>25.3.8. Test 8</A +></H3 ><P >On the PC type the command <B CLASS="COMMAND" @@ -17153,9 +17178,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN3596" -></A ->24.3.9. Test 9</H3 +NAME="AEN3651" +>25.3.9. Test 9</A +></H3 ><P >Run the command <B CLASS="COMMAND" @@ -17187,9 +17212,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN3604" -></A ->24.3.10. Test 10</H3 +NAME="AEN3659" +>25.3.10. Test 10</A +></H3 ><P >Run the command <B CLASS="COMMAND" @@ -17213,9 +17238,9 @@ CLASS="SECT2" ><HR><H3 CLASS="SECT2" ><A -NAME="AEN3610" -></A ->24.3.11. Test 11</H3 +NAME="AEN3665" +>25.3.11. Test 11</A +></H3 ><P >From file manager try to browse the server. Your samba server should appear in the browse list of your local workgroup (or the one you @@ -17241,9 +17266,9 @@ CLASS="SECT1" ><HR><H2 CLASS="SECT1" ><A -NAME="AEN3615" -></A ->24.4. Still having troubles?</H2 +NAME="AEN3670" +>25.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 diff --git a/docs/htmldocs/ads.html b/docs/htmldocs/ads.html index 2c556b61f3..6fc44d9170 100644 --- a/docs/htmldocs/ads.html +++ b/docs/htmldocs/ads.html @@ -5,7 +5,7 @@ >Samba as a ADS domain member</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -112,9 +112,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1339" -></A ->7.1. Installing the required packages for Debian</H1 +NAME="AEN1242" +>7.1. Installing the required packages for Debian</A +></H1 ><P >On Debian you need to install the following packages:</P ><P @@ -142,9 +142,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1346" -></A ->7.2. Installing the required packages for RedHat</H1 +NAME="AEN1249" +>7.2. Installing the required packages for RedHat</A +></H1 ><P >On RedHat this means you should have at least: </P ><P @@ -181,9 +181,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1356" -></A ->7.3. Compile Samba</H1 +NAME="AEN1259" +>7.3. Compile Samba</A +></H1 ><P >If your kerberos libraries are in a non-standard location then remember to add the configure option --with-krb5=DIR.</P @@ -237,9 +237,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1371" -></A ->7.4. Setup your /etc/krb5.conf</H1 +NAME="AEN1274" +>7.4. Setup your /etc/krb5.conf</A +></H1 ><P >The minimal configuration for krb5.conf is:</P ><P @@ -276,9 +276,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1381" -></A ->7.5. Create the computer account</H1 +NAME="AEN1284" +>7.5. Create the computer account</A +></H1 ><P >As a user that has write permission on the Samba private directory (usually root) run: @@ -291,9 +291,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1385" -></A ->7.5.1. Possible errors</H2 +NAME="AEN1288" +>7.5.1. Possible errors</A +></H2 ><P ><P ></P @@ -316,9 +316,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1393" -></A ->7.6. Test your server setup</H1 +NAME="AEN1296" +>7.6. Test your server setup</A +></H1 ><P >On a Windows 2000 client try <B CLASS="COMMAND" @@ -336,9 +336,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1398" -></A ->7.7. Testing with smbclient</H1 +NAME="AEN1301" +>7.7. Testing with smbclient</A +></H1 ><P >On your Samba server try to login to a Win2000 server or your Samba server using smbclient and kerberos. Use smbclient as usual, but @@ -349,9 +349,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1401" -></A ->7.8. Notes</H1 +NAME="AEN1304" +>7.8. Notes</A +></H1 ><P >You must change administrator password at least once after DC install, to create the right encoding types</P diff --git a/docs/htmldocs/appendixes.html b/docs/htmldocs/appendixes.html index 469ef170cd..21071bceaa 100644 --- a/docs/htmldocs/appendixes.html +++ b/docs/htmldocs/appendixes.html @@ -5,13 +5,13 @@ >Appendixes</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK REL="PREVIOUS" -TITLE="Creating Group Profiles" -HREF="groupprofiles.html"><LINK +TITLE="Securing Samba" +HREF="securing-samba.html"><LINK REL="NEXT" TITLE="Portability" HREF="portability.html"></HEAD @@ -42,7 +42,7 @@ WIDTH="10%" ALIGN="left" VALIGN="bottom" ><A -HREF="groupprofiles.html" +HREF="securing-samba.html" ACCESSKEY="P" >Prev</A ></TD @@ -91,24 +91,38 @@ HREF="portability.html" ><DL ><DT >21.1. <A -HREF="portability.html#AEN3251" +HREF="portability.html#AEN3156" >HPUX</A ></DT ><DT >21.2. <A -HREF="portability.html#AEN3257" +HREF="portability.html#AEN3162" >SCO Unix</A ></DT ><DT >21.3. <A -HREF="portability.html#AEN3261" +HREF="portability.html#AEN3166" >DNIX</A ></DT ><DT >21.4. <A -HREF="portability.html#AEN3290" +HREF="portability.html#AEN3195" >RedHat Linux Rembrandt-II</A ></DT +><DT +>21.5. <A +HREF="portability.html#AEN3201" +>AIX</A +></DT +><DD +><DL +><DT +>21.5.1. <A +HREF="portability.html#AEN3203" +>Sequential Read Ahead</A +></DT +></DL +></DD ></DL ></DD ><DT @@ -120,37 +134,37 @@ HREF="other-clients.html" ><DL ><DT >22.1. <A -HREF="other-clients.html#AEN3311" +HREF="other-clients.html#AEN3221" >Macintosh clients?</A ></DT ><DT >22.2. <A -HREF="other-clients.html#AEN3320" +HREF="other-clients.html#AEN3230" >OS2 Client</A ></DT ><DD ><DL ><DT >22.2.1. <A -HREF="other-clients.html#AEN3322" +HREF="other-clients.html#AEN3232" >How can I configure OS/2 Warp Connect or OS/2 Warp 4 as a client for Samba?</A ></DT ><DT >22.2.2. <A -HREF="other-clients.html#AEN3337" +HREF="other-clients.html#AEN3247" >How can I configure OS/2 Warp 3 (not Connect), OS/2 1.2, 1.3 or 2.x for Samba?</A ></DT ><DT >22.2.3. <A -HREF="other-clients.html#AEN3346" +HREF="other-clients.html#AEN3256" >Are there any other issues when OS/2 (any version) is used as a client?</A ></DT ><DT >22.2.4. <A -HREF="other-clients.html#AEN3350" +HREF="other-clients.html#AEN3260" >How do I get printer driver download working for OS/2 clients?</A ></DT @@ -158,168 +172,230 @@ HREF="other-clients.html#AEN3350" ></DD ><DT >22.3. <A -HREF="other-clients.html#AEN3360" +HREF="other-clients.html#AEN3270" >Windows for Workgroups</A ></DT ><DD ><DL ><DT >22.3.1. <A -HREF="other-clients.html#AEN3362" +HREF="other-clients.html#AEN3272" >Use latest TCP/IP stack from Microsoft</A ></DT ><DT >22.3.2. <A -HREF="other-clients.html#AEN3367" +HREF="other-clients.html#AEN3277" >Delete .pwl files after password change</A ></DT ><DT >22.3.3. <A -HREF="other-clients.html#AEN3372" +HREF="other-clients.html#AEN3282" >Configure WfW password handling</A ></DT ><DT >22.3.4. <A -HREF="other-clients.html#AEN3376" +HREF="other-clients.html#AEN3286" >Case handling of passwords</A ></DT +><DT +>22.3.5. <A +HREF="other-clients.html#AEN3291" +>Use TCP/IP as default protocol</A +></DT ></DL ></DD ><DT >22.4. <A -HREF="other-clients.html#AEN3381" +HREF="other-clients.html#AEN3294" >Windows '95/'98</A ></DT ><DT >22.5. <A -HREF="other-clients.html#AEN3397" +HREF="other-clients.html#AEN3310" >Windows 2000 Service Pack 2</A ></DT ></DL ></DD ><DT >23. <A -HREF="bugreport.html" ->Reporting Bugs</A +HREF="compiling.html" +>How to compile SAMBA</A ></DT ><DD ><DL ><DT >23.1. <A -HREF="bugreport.html#AEN3421" +HREF="compiling.html#AEN3337" +>Access Samba source code via CVS</A +></DT +><DD +><DL +><DT +>23.1.1. <A +HREF="compiling.html#AEN3339" >Introduction</A ></DT ><DT +>23.1.2. <A +HREF="compiling.html#AEN3344" +>CVS Access to samba.org</A +></DT +></DL +></DD +><DT >23.2. <A -HREF="bugreport.html#AEN3431" ->General info</A +HREF="compiling.html#AEN3380" +>Accessing the samba sources via rsync and ftp</A ></DT ><DT >23.3. <A -HREF="bugreport.html#AEN3437" ->Debug levels</A +HREF="compiling.html#AEN3386" +>Building the Binaries</A ></DT ><DT >23.4. <A -HREF="bugreport.html#AEN3454" +HREF="compiling.html#AEN3414" +>Starting the smbd and nmbd</A +></DT +><DD +><DL +><DT +>23.4.1. <A +HREF="compiling.html#AEN3424" +>Starting from inetd.conf</A +></DT +><DT +>23.4.2. <A +HREF="compiling.html#AEN3453" +>Alternative: starting it as a daemon</A +></DT +></DL +></DD +></DL +></DD +><DT +>24. <A +HREF="bugreport.html" +>Reporting Bugs</A +></DT +><DD +><DL +><DT +>24.1. <A +HREF="bugreport.html#AEN3476" +>Introduction</A +></DT +><DT +>24.2. <A +HREF="bugreport.html#AEN3486" +>General info</A +></DT +><DT +>24.3. <A +HREF="bugreport.html#AEN3492" +>Debug levels</A +></DT +><DT +>24.4. <A +HREF="bugreport.html#AEN3509" >Internal errors</A ></DT ><DT ->23.5. <A -HREF="bugreport.html#AEN3464" +>24.5. <A +HREF="bugreport.html#AEN3519" >Attaching to a running process</A ></DT ><DT ->23.6. <A -HREF="bugreport.html#AEN3467" +>24.6. <A +HREF="bugreport.html#AEN3522" >Patches</A ></DT ></DL ></DD ><DT ->24. <A +>25. <A HREF="diagnosis.html" ->Diagnosing your samba server</A +>The samba checklist</A ></DT ><DD ><DL ><DT ->24.1. <A -HREF="diagnosis.html#AEN3490" +>25.1. <A +HREF="diagnosis.html#AEN3545" >Introduction</A ></DT ><DT ->24.2. <A -HREF="diagnosis.html#AEN3495" +>25.2. <A +HREF="diagnosis.html#AEN3550" >Assumptions</A ></DT ><DT ->24.3. <A -HREF="diagnosis.html#AEN3505" +>25.3. <A +HREF="diagnosis.html#AEN3560" >Tests</A ></DT ><DD ><DL ><DT ->24.3.1. <A -HREF="diagnosis.html#AEN3507" +>25.3.1. <A +HREF="diagnosis.html#AEN3562" >Test 1</A ></DT ><DT ->24.3.2. <A -HREF="diagnosis.html#AEN3513" +>25.3.2. <A +HREF="diagnosis.html#AEN3568" >Test 2</A ></DT ><DT ->24.3.3. <A -HREF="diagnosis.html#AEN3519" +>25.3.3. <A +HREF="diagnosis.html#AEN3574" >Test 3</A ></DT ><DT ->24.3.4. <A -HREF="diagnosis.html#AEN3534" +>25.3.4. <A +HREF="diagnosis.html#AEN3589" >Test 4</A ></DT ><DT ->24.3.5. <A -HREF="diagnosis.html#AEN3539" +>25.3.5. <A +HREF="diagnosis.html#AEN3594" >Test 5</A ></DT ><DT ->24.3.6. <A -HREF="diagnosis.html#AEN3545" +>25.3.6. <A +HREF="diagnosis.html#AEN3600" >Test 6</A ></DT ><DT ->24.3.7. <A -HREF="diagnosis.html#AEN3553" +>25.3.7. <A +HREF="diagnosis.html#AEN3608" >Test 7</A ></DT ><DT ->24.3.8. <A -HREF="diagnosis.html#AEN3579" +>25.3.8. <A +HREF="diagnosis.html#AEN3634" >Test 8</A ></DT ><DT ->24.3.9. <A -HREF="diagnosis.html#AEN3596" +>25.3.9. <A +HREF="diagnosis.html#AEN3651" >Test 9</A ></DT ><DT ->24.3.10. <A -HREF="diagnosis.html#AEN3604" +>25.3.10. <A +HREF="diagnosis.html#AEN3659" >Test 10</A ></DT ><DT ->24.3.11. <A -HREF="diagnosis.html#AEN3610" +>25.3.11. <A +HREF="diagnosis.html#AEN3665" >Test 11</A ></DT ></DL ></DD ><DT ->24.4. <A -HREF="diagnosis.html#AEN3615" +>25.4. <A +HREF="diagnosis.html#AEN3670" >Still having troubles?</A ></DT ></DL @@ -344,7 +420,7 @@ WIDTH="33%" ALIGN="left" VALIGN="top" ><A -HREF="groupprofiles.html" +HREF="securing-samba.html" ACCESSKEY="P" >Prev</A ></TD @@ -372,7 +448,7 @@ ACCESSKEY="N" WIDTH="33%" ALIGN="left" VALIGN="top" ->Creating Group Profiles</TD +>Securing Samba</TD ><TD WIDTH="34%" ALIGN="center" diff --git a/docs/htmldocs/browsing-quick.html b/docs/htmldocs/browsing-quick.html index 680bdfc1de..aa3dba2ee4 100644 --- a/docs/htmldocs/browsing-quick.html +++ b/docs/htmldocs/browsing-quick.html @@ -5,7 +5,7 @@ >Quick Cross Subnet Browsing / Cross Workgroup Browsing guide</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -81,21 +81,24 @@ 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 +><P +>Note: 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 ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN230" -></A ->2.1. Discussion</H1 +NAME="AEN130" +>2.1. Discussion</A +></H1 ><P >Firstly, all MS Windows networking is based on SMB (Server Message -Block) based messaging. SMB messaging is implemented using NetBIOS. Samba -implements NetBIOS by encapsulating it over TCP/IP. MS Windows products can -do likewise. NetBIOS based networking uses broadcast messaging to affect -browse list management. When running NetBIOS over TCP/IP this uses UDP -based messaging. UDP messages can be broadcast or unicast.</P +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 "remote announce" parameter to smb.conf helps to project browse announcements @@ -109,18 +112,23 @@ segment is configured with it's own Samba WINS server, then the only way to get cross segment browsing to work is by using the "remote announce" and the "remote browse sync" parameters to your smb.conf file.</P ><P ->If only one WINS server is used then the use of the "remote announce" and the -"remote browse sync" parameters should NOT be necessary.</P +>If only one WINS server is used for an entire multi-segment network 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 +>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 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 @@ -132,9 +140,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN238" -></A ->2.2. Use of the "Remote Announce" parameter</H1 +NAME="AEN139" +>2.2. Use of the "Remote Announce" parameter</A +></H1 ><P >The "remote announce" parameter of smb.conf can be used to forcibly ensure that all the NetBIOS names on a network get announced to a remote network. @@ -190,9 +198,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN252" -></A ->2.3. Use of the "Remote Browse Sync" parameter</H1 +NAME="AEN153" +>2.3. Use of the "Remote Browse Sync" parameter</A +></H1 ><P >The "remote browse sync" parameter of smb.conf is used to announce to another LMB that it must synchronise it's NetBIOS name list with our @@ -213,9 +221,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN257" -></A ->2.4. Use of WINS</H1 +NAME="AEN158" +>2.4. Use of WINS</A +></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 @@ -267,22 +275,23 @@ CLASS="emphasis" 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 +> use both "wins support = yes" together +with "wins server = a.b.c.d" particularly not using it's own IP address. +Specifying both will cause nmbd to refuse to start!</P ></DIV ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN268" -></A ->2.5. Do NOT use more than one (1) protocol on MS Windows machines</H1 +NAME="AEN169" +>2.5. Do NOT use more than one (1) protocol on MS Windows machines</A +></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 take part in a process of electing the LMB (and DMB) +>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 @@ -298,6 +307,19 @@ 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 @@ -305,9 +327,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN274" -></A ->2.6. Name Resolution Order</H1 +NAME="AEN177" +>2.6. Name Resolution Order</A +></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 diff --git a/docs/htmldocs/bugreport.html b/docs/htmldocs/bugreport.html index 813d0055cc..cc4fc83df6 100644 --- a/docs/htmldocs/bugreport.html +++ b/docs/htmldocs/bugreport.html @@ -5,7 +5,7 @@ >Reporting Bugs</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -13,10 +13,10 @@ REL="UP" TITLE="Appendixes" HREF="appendixes.html"><LINK REL="PREVIOUS" -TITLE="Samba and other CIFS clients" -HREF="other-clients.html"><LINK +TITLE="How to compile SAMBA" +HREF="compiling.html"><LINK REL="NEXT" -TITLE="Diagnosing your samba server" +TITLE="The samba checklist" HREF="diagnosis.html"></HEAD ><BODY CLASS="CHAPTER" @@ -45,7 +45,7 @@ WIDTH="10%" ALIGN="left" VALIGN="bottom" ><A -HREF="other-clients.html" +HREF="compiling.html" ACCESSKEY="P" >Prev</A ></TD @@ -74,15 +74,15 @@ CLASS="CHAPTER" ><A NAME="BUGREPORT" ></A ->Chapter 23. Reporting Bugs</H1 +>Chapter 24. Reporting Bugs</H1 ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3421" -></A ->23.1. Introduction</H1 +NAME="AEN3476" +>24.1. Introduction</A +></H1 ><P >The email address for bug reports for stable releases is <A HREF="samba@samba.org" @@ -125,9 +125,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3431" -></A ->23.2. General info</H1 +NAME="AEN3486" +>24.2. General info</A +></H1 ><P >Before submitting a bug report check your config for silly errors. Look in your log files for obvious messages that tell you that @@ -150,9 +150,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3437" -></A ->23.3. Debug levels</H1 +NAME="AEN3492" +>24.3. Debug levels</A +></H1 ><P >If the bug has anything to do with Samba behaving incorrectly as a server (like refusing to open a file) then the log files will probably @@ -220,9 +220,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3454" -></A ->23.4. Internal errors</H1 +NAME="AEN3509" +>24.4. Internal errors</A +></H1 ><P >If you get a "INTERNAL ERROR" message in your log files it means that Samba got an unexpected signal while running. It is probably a @@ -264,9 +264,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3464" -></A ->23.5. Attaching to a running process</H1 +NAME="AEN3519" +>24.5. Attaching to a running process</A +></H1 ><P >Unfortunately some unixes (in particular some recent linux kernels) refuse to dump a core file if the task has changed uid (which smbd @@ -281,9 +281,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3467" -></A ->23.6. Patches</H1 +NAME="AEN3522" +>24.6. Patches</A +></H1 ><P >The best sort of bug report is one that includes a fix! If you send us patches please use <B @@ -314,7 +314,7 @@ WIDTH="33%" ALIGN="left" VALIGN="top" ><A -HREF="other-clients.html" +HREF="compiling.html" ACCESSKEY="P" >Prev</A ></TD @@ -342,7 +342,7 @@ ACCESSKEY="N" WIDTH="33%" ALIGN="left" VALIGN="top" ->Samba and other CIFS clients</TD +>How to compile SAMBA</TD ><TD WIDTH="34%" ALIGN="center" @@ -356,7 +356,7 @@ ACCESSKEY="U" WIDTH="33%" ALIGN="right" VALIGN="top" ->Diagnosing your samba server</TD +>The samba checklist</TD ></TR ></TABLE ></DIV diff --git a/docs/htmldocs/compiling.html b/docs/htmldocs/compiling.html new file mode 100644 index 0000000000..95c29b5193 --- /dev/null +++ b/docs/htmldocs/compiling.html @@ -0,0 +1,631 @@ +<!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 23. 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="AEN3337" +>23.1. Access Samba source code via CVS</A +></H1 +><DIV +CLASS="SECT2" +><H2 +CLASS="SECT2" +><A +NAME="AEN3339" +>23.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="AEN3344" +>23.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="AEN3347" +>23.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="AEN3352" +>23.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 +> <B +CLASS="COMMAND" +>cvs -d :pserver:cvs@samba.org:/cvsroot login</B +> + </P +><P +> When it asks you for a password type <KBD +CLASS="USERINPUT" +>cvs</KBD +>. + </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 <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 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="SECT1" +><H1 +CLASS="SECT1" +><A +NAME="AEN3380" +>23.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="AEN3386" +>23.3. Building the Binaries</A +></H1 +><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 +><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 +><DIV +CLASS="SECT1" +><H1 +CLASS="SECT1" +><A +NAME="AEN3414" +>23.4. Starting the smbd and nmbd</A +></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="AEN3424" +>23.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 +><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="AEN3453" +>23.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 +><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 +><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 deleted file mode 100644 index 4e088faf70..0000000000 --- a/docs/htmldocs/cvs-access.html +++ /dev/null @@ -1,307 +0,0 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> -<HTML -><HEAD -><TITLE ->Access Samba source code via CVS</TITLE -><META -NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK -REL="HOME" -TITLE="SAMBA Project Documentation" -HREF="samba-howto-collection.html"><LINK -REL="UP" -TITLE="Optional configuration" -HREF="optional.html"><LINK -REL="PREVIOUS" -TITLE="Stackable VFS modules" -HREF="vfs.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="vfs.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" -></A ->Chapter 17. Access Samba source code via CVS</H1 -><DIV -CLASS="SECT1" -><H1 -CLASS="SECT1" -><A -NAME="AEN2942" -></A ->17.1. Introduction</H1 -><P ->Samba is developed in an open environment. Developers use CVS -(Concurrent Versioning System) to "checkin" (also known as -"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="AEN2947" -></A ->17.2. CVS Access to samba.org</H1 -><P ->The machine samba.org runs a publicly accessible CVS -repository for access to the source code of several packages, -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="AEN2950" -></A ->17.2.1. Access via CVSweb</H2 -><P ->You can access the source code via your -favourite WWW browser. This allows you to access the contents of -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="AEN2955" -></A ->17.2.2. Access via cvs</H2 -><P ->You can also access the source code via a -normal cvs client. This gives you much more control over you can -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="vfs.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" ->Stackable VFS modules</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 0c71043074..e91ac21f03 100644 --- a/docs/htmldocs/diagnosis.html +++ b/docs/htmldocs/diagnosis.html @@ -2,10 +2,10 @@ <HTML ><HEAD ><TITLE ->Diagnosing your samba server</TITLE +>The samba checklist</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -67,15 +67,15 @@ CLASS="CHAPTER" ><A NAME="DIAGNOSIS" ></A ->Chapter 24. Diagnosing your samba server</H1 +>Chapter 25. The samba checklist</H1 ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3490" -></A ->24.1. Introduction</H1 +NAME="AEN3545" +>25.1. Introduction</A +></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 +95,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3495" -></A ->24.2. Assumptions</H1 +NAME="AEN3550" +>25.2. Assumptions</A +></H1 ><P >In all of the tests it is assumed you have a Samba server called BIGSERVER and a PC called ACLIENT both in workgroup TESTGROUP.</P @@ -133,17 +133,17 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3505" -></A ->24.3. Tests</H1 +NAME="AEN3560" +>25.3. Tests</A +></H1 ><DIV CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3507" -></A ->24.3.1. Test 1</H2 +NAME="AEN3562" +>25.3.1. Test 1</A +></H2 ><P >In the directory in which you store your smb.conf file, run the command "testparm smb.conf". If it reports any errors then your smb.conf @@ -163,9 +163,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3513" -></A ->24.3.2. Test 2</H2 +NAME="AEN3568" +>25.3.2. Test 2</A +></H2 ><P >Run the command "ping BIGSERVER" from the PC and "ping ACLIENT" from the unix box. If you don't get a valid response then your TCP/IP @@ -189,9 +189,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3519" -></A ->24.3.3. Test 3</H2 +NAME="AEN3574" +>25.3.3. Test 3</A +></H2 ><P >Run the command "smbclient -L BIGSERVER" on the unix box. You should get a list of available shares back. </P @@ -260,9 +260,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3534" -></A ->24.3.4. Test 4</H2 +NAME="AEN3589" +>25.3.4. Test 4</A +></H2 ><P >Run the command "nmblookup -B BIGSERVER __SAMBA__". You should get the IP address of your Samba server back.</P @@ -281,9 +281,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3539" -></A ->24.3.5. Test 5</H2 +NAME="AEN3594" +>25.3.5. Test 5</A +></H2 ><P >run the command <B CLASS="COMMAND" @@ -302,9 +302,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3545" -></A ->24.3.6. Test 6</H2 +NAME="AEN3600" +>25.3.6. Test 6</A +></H2 ><P >Run the command <B CLASS="COMMAND" @@ -336,9 +336,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3553" -></A ->24.3.7. Test 7</H2 +NAME="AEN3608" +>25.3.7. Test 7</A +></H2 ><P >Run the command <B CLASS="COMMAND" @@ -346,7 +346,7 @@ CLASS="COMMAND" >. You should then be prompted for a password. You should use the password of the account you are logged into the unix box with. If you want to test with -another account then add the -U >accountname< option to the end of +another account then add the -U >accountname< option to the end of the command line. eg: <B CLASS="COMMAND" @@ -412,7 +412,7 @@ CLASS="COMMAND" > etc. Type <B CLASS="COMMAND" ->help >command<</B +>help >command<</B > for instructions. You should especially check that the amount of free disk space shown is correct when you type <B @@ -425,9 +425,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3579" -></A ->24.3.8. Test 8</H2 +NAME="AEN3634" +>25.3.8. Test 8</A +></H2 ><P >On the PC type the command <B CLASS="COMMAND" @@ -485,9 +485,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3596" -></A ->24.3.9. Test 9</H2 +NAME="AEN3651" +>25.3.9. Test 9</A +></H2 ><P >Run the command <B CLASS="COMMAND" @@ -519,9 +519,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3604" -></A ->24.3.10. Test 10</H2 +NAME="AEN3659" +>25.3.10. Test 10</A +></H2 ><P >Run the command <B CLASS="COMMAND" @@ -545,9 +545,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3610" -></A ->24.3.11. Test 11</H2 +NAME="AEN3665" +>25.3.11. Test 11</A +></H2 ><P >From file manager try to browse the server. Your samba server should appear in the browse list of your local workgroup (or the one you @@ -573,9 +573,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3615" -></A ->24.4. Still having troubles?</H1 +NAME="AEN3670" +>25.4. Still having troubles?</A +></H1 ><P >Try the mailing list or newsgroup, or use the ethereal utility to sniff the problem. The official samba mailing list can be reached at diff --git a/docs/htmldocs/domain-security.html b/docs/htmldocs/domain-security.html index fcb40641e4..d47138d791 100644 --- a/docs/htmldocs/domain-security.html +++ b/docs/htmldocs/domain-security.html @@ -5,7 +5,7 @@ >Samba as a NT4 or Win2k domain member</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -80,30 +80,30 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1423" -></A ->8.1. Joining an NT Domain with Samba 3.0</H1 +NAME="AEN1326" +>8.1. Joining an NT Domain with Samba 3.0</A +></H1 ><P >Assume you have a Samba 3.0 server with a NetBIOS name of - <TT + <CODE CLASS="CONSTANT" ->SERV1</TT +>SERV1</CODE > and are joining an or Win2k NT domain called - <TT + <CODE CLASS="CONSTANT" ->DOM</TT +>DOM</CODE >, which has a PDC with a NetBIOS name - of <TT + of <CODE CLASS="CONSTANT" ->DOMPDC</TT +>DOMPDC</CODE > and two backup domain controllers - with NetBIOS names <TT + with NetBIOS names <CODE CLASS="CONSTANT" ->DOMBDC1</TT -> and <TT +>DOMBDC1</CODE +> and <CODE CLASS="CONSTANT" >DOMBDC2 - </TT + </CODE >.</P ><P >Firstly, you must edit your <A @@ -119,11 +119,9 @@ CLASS="FILENAME" >Change (or add) your <A HREF="smb.conf.5.html#SECURITY" TARGET="_top" -> <TT +> <VAR CLASS="PARAMETER" -><I ->security =</I -></TT +>security =</VAR ></A > line in the [global] section of your smb.conf to read:</P @@ -141,11 +139,9 @@ CLASS="COMMAND" >Next change the <A HREF="smb.conf.5.html#WORKGROUP" TARGET="_top" -><TT +><VAR CLASS="PARAMETER" -><I -> workgroup =</I -></TT +> workgroup =</VAR ></A > line in the [global] section to read: </P ><P @@ -159,26 +155,22 @@ CLASS="COMMAND" >You must also have the parameter <A HREF="smb.conf.5.html#ENCRYPTPASSWORDS" TARGET="_top" -> <TT +> <VAR CLASS="PARAMETER" -><I ->encrypt passwords</I -></TT +>encrypt passwords</VAR ></A -> set to <TT +> set to <CODE CLASS="CONSTANT" >yes - </TT + </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" -> <TT +> <VAR CLASS="PARAMETER" -><I ->password server =</I -></TT +>password server =</VAR ></A > line in the [global] section to read: </P @@ -211,41 +203,35 @@ CLASS="COMMAND" >In order to actually join the domain, you must run this command:</P ><P -><TT +><SAMP CLASS="PROMPT" ->root# </TT -><TT +>root# </SAMP +><KBD CLASS="USERINPUT" -><B >net join -S DOMPDC - -U<TT + -U<VAR CLASS="REPLACEABLE" -><I ->Administrator%password</I -></TT -></B -></TT +>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 <TT + is DOMPDC. The <VAR CLASS="REPLACEABLE" -><I ->Administrator%password</I -></TT +>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 -><TT +><SAMP CLASS="COMPUTEROUTPUT" ->Joined domain DOM.</TT +>Joined domain DOM.</SAMP > - or <TT + or <SAMP CLASS="COMPUTEROUTPUT" ->Joined 'SERV1' to realm 'MYREALM'</TT +>Joined 'SERV1' to realm 'MYREALM'</SAMP > </P ><P @@ -282,9 +268,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1478" -></A ->8.2. Samba and Windows 2000 Domains</H1 +NAME="AEN1381" +>8.2. Samba and Windows 2000 Domains</A +></H1 ><P >Many people have asked regarding the state of Samba's ability to participate in a Windows 2000 Domain. Samba 3.0 is able to act as a member server of a Windows @@ -296,16 +282,16 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1481" -></A ->8.3. Why is this better than security = server?</H1 +NAME="AEN1384" +>8.3. Why is this better than security = server?</A +></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 <TT + to your server. This means that if domain user <CODE CLASS="CONSTANT" >DOM\fred - </TT + </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 diff --git a/docs/htmldocs/findsmb.1.html b/docs/htmldocs/findsmb.1.html index bf63db867c..bc0aec55c0 100644 --- a/docs/htmldocs/findsmb.1.html +++ b/docs/htmldocs/findsmb.1.html @@ -5,7 +5,7 @@ >findsmb</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"></HEAD +CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD ><BODY CLASS="REFENTRY" BGCOLOR="#FFFFFF" @@ -110,9 +110,9 @@ CLASS="REFENTRYTITLE" >nmblookup</SPAN >(1)</SPAN > - will be called with <TT + will be called with <CODE CLASS="CONSTANT" ->-B</TT +>-B</CODE > option.</P ></DD ><DT @@ -139,9 +139,9 @@ CLASS="REFENTRYTITLE" >nmblookup</SPAN >(1)</SPAN > - as part of the <TT + as part of the <CODE CLASS="CONSTANT" ->-B</TT +>-B</CODE > option.</P ></DD ></DL @@ -174,9 +174,9 @@ CLASS="COMMAND" not show any information about the operating system or server version.</P ><P ->The command with <TT +>The command with <CODE CLASS="CONSTANT" ->-r</TT +>-r</CODE > option must be run on a system without <SPAN CLASS="CITEREFENTRY" @@ -192,9 +192,9 @@ CLASS="COMMAND" > 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 <TT + the command must be run as root and with <CODE CLASS="CONSTANT" ->-r</TT +>-r</CODE > option on a machine without <B CLASS="COMMAND" @@ -205,9 +205,9 @@ CLASS="COMMAND" CLASS="COMMAND" >findsmb</B > - without <TT + without <CODE CLASS="CONSTANT" ->-r</TT +>-r</CODE > option set would yield output similar to the following</P ><PRE diff --git a/docs/htmldocs/groupmapping.html b/docs/htmldocs/groupmapping.html index d7eafcb58f..54921b3798 100644 --- a/docs/htmldocs/groupmapping.html +++ b/docs/htmldocs/groupmapping.html @@ -5,7 +5,7 @@ >Group mapping HOWTO</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -13,8 +13,8 @@ REL="UP" TITLE="Optional configuration" HREF="optional.html"><LINK REL="PREVIOUS" -TITLE="Access Samba source code via CVS" -HREF="cvs-access.html"><LINK +TITLE="Stackable VFS modules" +HREF="vfs.html"><LINK REL="NEXT" TITLE="Samba performance issues" HREF="speed.html"></HEAD @@ -45,7 +45,7 @@ WIDTH="10%" ALIGN="left" VALIGN="bottom" ><A -HREF="cvs-access.html" +HREF="vfs.html" ACCESSKEY="P" >Prev</A ></TD @@ -74,7 +74,7 @@ CLASS="CHAPTER" ><A NAME="GROUPMAPPING" ></A ->Chapter 18. Group mapping HOWTO</H1 +>Chapter 17. Group mapping HOWTO</H1 ><P > Starting with Samba 3.0 alpha 2, a new group mapping function is available. The @@ -185,7 +185,7 @@ WIDTH="33%" ALIGN="left" VALIGN="top" ><A -HREF="cvs-access.html" +HREF="vfs.html" ACCESSKEY="P" >Prev</A ></TD @@ -213,7 +213,7 @@ ACCESSKEY="N" WIDTH="33%" ALIGN="left" VALIGN="top" ->Access Samba source code via CVS</TD +>Stackable VFS modules</TD ><TD WIDTH="34%" ALIGN="center" diff --git a/docs/htmldocs/groupprofiles.html b/docs/htmldocs/groupprofiles.html index c9184032aa..6741aa3599 100644 --- a/docs/htmldocs/groupprofiles.html +++ b/docs/htmldocs/groupprofiles.html @@ -2,10 +2,10 @@ <HTML ><HEAD ><TITLE ->Creating Group Profiles</TITLE +>Creating Group Prolicy Files</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -16,8 +16,8 @@ REL="PREVIOUS" TITLE="Samba performance issues" HREF="speed.html"><LINK REL="NEXT" -TITLE="Appendixes" -HREF="appendixes.html"></HEAD +TITLE="Securing Samba" +HREF="securing-samba.html"></HEAD ><BODY CLASS="CHAPTER" BGCOLOR="#FFFFFF" @@ -59,7 +59,7 @@ WIDTH="10%" ALIGN="right" VALIGN="bottom" ><A -HREF="appendixes.html" +HREF="securing-samba.html" ACCESSKEY="N" >Next</A ></TD @@ -74,15 +74,15 @@ CLASS="CHAPTER" ><A NAME="GROUPPROFILES" ></A ->Chapter 20. Creating Group Profiles</H1 +>Chapter 19. Creating Group Prolicy Files</H1 ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3123" -></A ->20.1. Windows '9x</H1 +NAME="AEN2980" +>19.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 @@ -106,25 +106,28 @@ CLASS="FILENAME" > that needs to be placed in the root of the [NETLOGON] share. If your Win98 is configured to log onto the Samba Domain, it will automatically read this file and update the -Win98 registry of the machine that is logging on.</P +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 Win98 will check the +>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 Win98 machine. Hence, you will notice -things changing back to the original settings.</P +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="AEN3132" -></A ->20.2. Windows NT 4</H1 +NAME="AEN2990" +>19.2. Windows NT 4</A +></H1 ><P ->Unfortunately, the Resource Kit info is Win NT4/2K version specific.</P +>Unfortunately, the Resource Kit info is Win NT4 or 200x specific.</P ><P >Here is a quick guide:</P ><P @@ -159,7 +162,7 @@ ALT="Note"></TD ALIGN="LEFT" VALIGN="TOP" ><P ->I am using the term "migrate" lossely. You can copy a profile to +>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 @@ -201,9 +204,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3155" -></A ->20.2.1. Side bar Notes</H2 +NAME="AEN3013" +>19.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 @@ -217,9 +220,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3159" -></A ->20.2.2. Mandatory profiles</H2 +NAME="AEN3017" +>19.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 @@ -230,9 +233,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3162" -></A ->20.2.3. moveuser.exe</H2 +NAME="AEN3020" +>19.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 @@ -243,9 +246,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3165" -></A ->20.2.4. Get SID</H2 +NAME="AEN3023" +>19.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 @@ -266,9 +269,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3170" -></A ->20.3. Windows 2000/XP</H1 +NAME="AEN3028" +>19.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 @@ -532,7 +535,7 @@ WIDTH="33%" ALIGN="right" VALIGN="top" ><A -HREF="appendixes.html" +HREF="securing-samba.html" ACCESSKEY="N" >Next</A ></TD @@ -556,7 +559,7 @@ ACCESSKEY="U" WIDTH="33%" ALIGN="right" VALIGN="top" ->Appendixes</TD +>Securing Samba</TD ></TR ></TABLE ></DIV diff --git a/docs/htmldocs/improved-browsing.html b/docs/htmldocs/improved-browsing.html index b912cb57e5..b58945a0b5 100644 --- a/docs/htmldocs/improved-browsing.html +++ b/docs/htmldocs/improved-browsing.html @@ -5,7 +5,7 @@ >Improved browsing in samba</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -80,9 +80,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2700" -></A ->15.1. Overview of browsing</H1 +NAME="AEN2603" +>15.1. Overview of browsing</A +></H1 ><P >SMB networking provides a mechanism by which clients can access a list of machines in a network, a so-called "browse list". This list @@ -93,8 +93,13 @@ list is heavily used by all SMB clients. Configuration of SMB browsing has been problematic for some Samba users, hence this document.</P ><P ->Browsing will NOT work if name resolution from NetBIOS names to IP -addresses does not function correctly. Use of a WINS server is highly +>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 @@ -104,16 +109,14 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2704" -></A ->15.2. Browsing support in samba</H1 +NAME="AEN2608" +>15.2. Browsing support in samba</A +></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 +>Samba facilitates browsing. The browsing is supported by nmbd +and is also controlled by options in the smb.conf file (see smb.conf(5)). +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 @@ -128,12 +131,12 @@ regardless of whether it is NT, Samba or any other type of domain master that is providing this service.</P ><P >[Note that nmbd can be configured as a WINS server, but it is not -necessary to specifically use samba as your WINS server. NTAS can -be configured as your WINS server. In a mixed NT server and -samba environment on a Wide Area Network, it is recommended that -you use the NT server's WINS server capabilities. In a samba-only -environment, it is recommended that you use one and only one nmbd -as your WINS server].</P +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 ><P >To get browsing to work you need to run nmbd as usual, but will need to use the "workgroup" option in smb.conf to control what workgroup @@ -149,9 +152,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2713" -></A ->15.3. Problem resolution</H1 +NAME="AEN2616" +>15.3. Problem resolution</A +></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 @@ -167,6 +170,19 @@ filemanager should display the list of available shares.</P 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 >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 @@ -183,11 +199,11 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2720" -></A ->15.4. Browsing across subnets</H1 +NAME="AEN2625" +>15.4. Browsing across subnets</A +></H1 ><P ->With the release of Samba 1.9.17(alpha1 and above) Samba has been +>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 @@ -214,15 +230,14 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2725" -></A ->15.4.1. How does cross subnet browsing work ?</H2 +NAME="AEN2630" +>15.4.1. How does cross subnet browsing work ?</A +></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. -However, with the 1.9.17 release, Samba is capable of cross subnet -browsing when configured correctly.</P +Samba is capable of cross subnet browsing when configured correctly.</P ><P >Consider a network set up as follows :</P ><P @@ -303,7 +318,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 @@ -426,9 +441,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2760" -></A ->15.5. Setting up a WINS server</H1 +NAME="AEN2665" +>15.5. Setting up a WINS server</A +></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 @@ -440,9 +455,9 @@ CLASS="COMMAND" > wins support = yes</B ></P ><P ->Versions of Samba previous to 1.9.17 had this parameter default to +>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 1.9.17 or above, or at the very +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 @@ -480,10 +495,10 @@ 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 smb.conf file of the Samba @@ -494,7 +509,7 @@ CLASS="COMMAND" >" option and the "<B CLASS="COMMAND" ->wins server = >name<</B +>wins server = <name></B >" option then nmbd will fail to start.</P ><P @@ -509,9 +524,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2779" -></A ->15.6. Setting up Browsing in a WORKGROUP</H1 +NAME="AEN2684" +>15.6. Setting up Browsing in a WORKGROUP</A +></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 @@ -552,11 +567,12 @@ server, if you require.</P ><P >Next, you should ensure that each of the subnets contains a machine that can act as a local master browser for the -workgroup. Any NT machine should be able to do this, as will -Windows 95 machines (although these tend to get rebooted more -often, so it's not such a good idea to use these). To make a -Samba server a local master browser set the following -options in the [global] section of the smb.conf file :</P +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 +smb.conf file :</P ><P ><PRE CLASS="PROGRAMLISTING" @@ -593,16 +609,16 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2797" -></A ->15.7. Setting up Browsing in a DOMAIN</H1 +NAME="AEN2702" +>15.7. Setting up Browsing in a DOMAIN</A +></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 (DOMAIN>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 @@ -644,9 +660,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2807" -></A ->15.8. Forcing samba to be the master</H1 +NAME="AEN2712" +>15.8. Forcing samba to be the master</A +></H1 ><P >Who becomes the "master browser" is determined by an election process using broadcasts. Each election packet contains a number of parameters @@ -659,8 +675,8 @@ option in smb.conf to a higher number. It defaults to 0. Using 34 would make it win all elections over every other system (except other samba systems!)</P ><P ->A "os level" of 2 would make it beat WfWg and Win95, but not NTAS. A -NTAS domain controller uses level 32.</P +>A "os level" 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 @@ -692,9 +708,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2816" -></A ->15.9. Making samba the domain master</H1 +NAME="AEN2721" +>15.9. Making samba the domain master</A +></H1 ><P >The domain master is responsible for collating the browse lists of multiple subnets so that browsing can occur between subnets. You can @@ -765,9 +781,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2834" -></A ->15.10. Note about broadcast addresses</H1 +NAME="AEN2739" +>15.10. Note about broadcast addresses</A +></H1 ><P >If your network uses a "0" based broadcast address (for example if it ends in a 0) then you will strike problems. Windows for Workgroups @@ -779,9 +795,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2837" -></A ->15.11. Multiple interfaces</H1 +NAME="AEN2742" +>15.11. Multiple interfaces</A +></H1 ><P >Samba now supports machines with multiple network interfaces. If you have multiple interfaces then you will need to use the "interfaces" diff --git a/docs/htmldocs/install.html b/docs/htmldocs/install.html index e518e270bf..d596ba4fd9 100644 --- a/docs/htmldocs/install.html +++ b/docs/htmldocs/install.html @@ -5,7 +5,7 @@ >How to Install and Test SAMBA</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -81,166 +81,50 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN26" -></A ->1.1. Read the man pages</H1 -><P ->The man pages distributed with SAMBA contain - lots of useful info that will help to get you started. - If you don't know how to read man pages then try - something like:</P +>1.1. Obtaining and installing samba</A +></H1 ><P -><TT -CLASS="PROMPT" ->$ </TT -><TT -CLASS="USERINPUT" -><B ->man smbd.8</B -></TT -> - or - <TT -CLASS="PROMPT" ->$ </TT -><TT -CLASS="USERINPUT" -><B ->nroff -man smbd.8 | more - </B -></TT -> on older unixes.</P -><P ->Other sources of information are pointed to - by the Samba web site,<A -HREF="http://www.samba.org/" +>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" -> http://www.samba.org</A -></P -></DIV -><DIV -CLASS="SECT1" -><H1 -CLASS="SECT1" -><A -NAME="AEN36" -></A ->1.2. Building the Binaries</H1 -><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 +>the samba homepage</A +> + </P ><P ->if you find this version a disaster!</P +>If you need to compile samba from source, check the + appropriate appendix chapter.</P ></DIV ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN64" -></A ->1.3. The all important step</H1 -><P ->At this stage you must fetch yourself a - coffee or other drink you find stimulating. Getting the rest - of the install right can sometimes be tricky, so you will - probably need it.</P +NAME="AEN31" +>1.2. Configuring samba</A +></H1 ><P ->If you have installed samba before then you can skip - this step.</P -></DIV +>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="SECT1" -><H1 -CLASS="SECT1" +CLASS="SECT2" +><H2 +CLASS="SECT2" ><A -NAME="AEN68" -></A ->1.4. Create the smb configuration file.</H1 +NAME="AEN36" +>1.2.1. Editing the smb.conf file</A +></H2 ><P >There are sample configuration files in the examples subdirectory in the distribution. I suggest you read them @@ -288,19 +172,18 @@ CLASS="FILENAME" ><P >For more information about security settings for the [homes] share please refer to the document UNIX_SECURITY.txt.</P -></DIV ><DIV -CLASS="SECT1" -><H1 -CLASS="SECT1" +CLASS="SECT3" +><H3 +CLASS="SECT3" ><A -NAME="AEN82" -></A ->1.5. Test your config file with +NAME="AEN50" +>1.2.1.1. Test your config file with <B CLASS="COMMAND" >testparm</B -></H1 +></A +></H3 ><P >It's important that you test the validity of your <TT @@ -319,205 +202,33 @@ CLASS="FILENAME" >smb.conf</TT >!</P ></DIV -><DIV -CLASS="SECT1" -><H1 -CLASS="SECT1" -><A -NAME="AEN90" -></A ->1.6. Starting the smbd and nmbd</H1 -><P ->You must choose to start smbd and nmbd either - as daemons or from <B -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" -></A ->1.6.1. Starting from inetd.conf</H2 -><P ->NOTE; The following will be different if - you use NIS or NIS+ to distributed services maps.</P -><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="AEN129" -></A ->1.6.2. Alternative: starting it as a daemon</H2 -><P ->To start the server as a daemon you should create - a script something like this one, perhaps calling - 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 +NAME="AEN58" +>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 ></DIV ></DIV ><DIV @@ -525,25 +236,21 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN145" -></A ->1.7. Try listing the shares available on your - server</H1 +NAME="AEN64" +>1.3. Try listing the shares available on your + server</A +></H1 ><P -><TT +><SAMP CLASS="PROMPT" ->$ </TT -><TT +>$ </SAMP +><KBD CLASS="USERINPUT" -><B >smbclient -L - <TT + <VAR CLASS="REPLACEABLE" -><I ->yourhostname</I -></TT -></B -></TT +>yourhostname</VAR +></KBD ></P ><P >You should get back a list of shares available on @@ -566,39 +273,31 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN154" -></A ->1.8. Try connecting with the unix client</H1 +NAME="AEN73" +>1.4. Try connecting with the unix client</A +></H1 ><P -><TT +><SAMP CLASS="PROMPT" ->$ </TT -><TT +>$ </SAMP +><KBD CLASS="USERINPUT" -><B ->smbclient <TT +>smbclient <VAR CLASS="REPLACEABLE" -><I -> //yourhostname/aservice</I -></TT -></B -></TT +> //yourhostname/aservice</VAR +></KBD ></P ><P ->Typically the <TT +>Typically the <VAR CLASS="REPLACEABLE" -><I ->yourhostname</I -></TT +>yourhostname</VAR > would be the name of the host where you installed <B CLASS="COMMAND" > smbd</B ->. The <TT +>. The <VAR CLASS="REPLACEABLE" -><I ->aservice</I -></TT +>aservice</VAR > is any service you have defined in the <TT CLASS="FILENAME" @@ -613,15 +312,13 @@ CLASS="FILENAME" >For example if your unix host is bambi and your login name is fred you would type:</P ><P -><TT +><SAMP CLASS="PROMPT" ->$ </TT -><TT +>$ </SAMP +><KBD CLASS="USERINPUT" -><B >smbclient //bambi/fred - </B -></TT + </KBD ></P ></DIV ><DIV @@ -629,46 +326,40 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN170" -></A ->1.9. Try connecting from a DOS, WfWg, Win9x, WinNT, - Win2k, OS/2, etc... client</H1 +NAME="AEN89" +>1.5. Try connecting from a DOS, WfWg, Win9x, WinNT, + Win2k, OS/2, etc... client</A +></H1 ><P >Try mounting disks. eg:</P ><P -><TT +><SAMP CLASS="PROMPT" ->C:\WINDOWS\> </TT -><TT +>C:\WINDOWS\> </SAMP +><KBD CLASS="USERINPUT" -><B >net use d: \\servername\service - </B -></TT + </KBD ></P ><P >Try printing. eg:</P ><P -><TT +><SAMP CLASS="PROMPT" ->C:\WINDOWS\> </TT -><TT +>C:\WINDOWS\> </SAMP +><KBD CLASS="USERINPUT" -><B >net use lpt1: - \\servername\spoolservice</B -></TT + \\servername\spoolservice</KBD ></P ><P -><TT +><SAMP CLASS="PROMPT" ->C:\WINDOWS\> </TT -><TT +>C:\WINDOWS\> </SAMP +><KBD CLASS="USERINPUT" -><B >print filename - </B -></TT + </KBD ></P ><P >Celebrate, or send me a bug report!</P @@ -678,55 +369,41 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN184" -></A ->1.10. What If Things Don't Work?</H1 -><P ->If nothing works and you start to think "who wrote - this pile of trash" then I suggest you do step 2 again (and - again) till you calm down.</P +NAME="AEN103" +>1.6. What If Things Don't Work?</A +></H1 ><P ->Then you might read the file DIAGNOSIS.txt and the +>Then you might read the file HOWTO chapter Diagnosis and the FAQ. If you are still stuck then try the mailing list or newsgroup (look in the README for details). Samba has been successfully installed at thousands of sites worldwide, so maybe someone else has hit your problem and has overcome it. You could also use the WWW site to scan back issues of the samba-digest.</P ><P ->When you fix the problem PLEASE send me some updates to the - documentation (or source code) so that the next person will find it - easier. </P -><DIV -CLASS="SECT2" -><H2 -CLASS="SECT2" -><A -NAME="AEN189" -></A ->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 +>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" ><H2 CLASS="SECT2" ><A -NAME="AEN193" -></A ->1.10.2. Scope IDs</H2 +NAME="AEN108" +>1.6.1. Scope IDs</A +></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 @@ -734,71 +411,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN196" -></A ->1.10.3. Choosing the Protocol Level</H2 -><P ->The SMB protocol has many dialects. Currently - Samba supports 5, called CORE, COREPLUS, LANMAN1, - 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" -></A ->1.10.4. Printing from UNIX to a Client PC</H2 -><P ->To use a printer that is available via a smb-based - server from a unix host with LPR you will need to compile the - 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" -></A ->1.10.5. Locking</H2 +NAME="AEN111" +>1.6.2. Locking</A +></H2 ><P >One area which sometimes causes trouble is locking.</P ><P @@ -851,19 +466,6 @@ NAME="AEN210" 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" -></A ->1.10.6. Mapping Usernames</H2 -><P ->If you have different usernames on the PCs and - the unix server then take a look at the "username map" option. - See the smb.conf man page for details.</P -></DIV ></DIV ></DIV ><DIV diff --git a/docs/htmldocs/integrate-ms-networks.html b/docs/htmldocs/integrate-ms-networks.html index 8299a456bb..99614cfb3f 100644 --- a/docs/htmldocs/integrate-ms-networks.html +++ b/docs/htmldocs/integrate-ms-networks.html @@ -5,7 +5,7 @@ >Integrating MS Windows networks with Samba</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -80,9 +80,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1513" -></A ->9.1. Agenda</H1 +NAME="AEN1416" +>9.1. Agenda</A +></H1 ><P >To identify the key functional mechanisms of MS Windows networking to enable the deployment of Samba as a means of extending and/or @@ -147,9 +147,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1535" -></A ->9.2. Name Resolution in a pure Unix/Linux world</H1 +NAME="AEN1438" +>9.2. Name Resolution in a pure Unix/Linux world</A +></H1 ><P >The key configuration files covered in this section are:</P ><P @@ -189,11 +189,11 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1551" -></A +NAME="AEN1454" >9.2.1. <TT CLASS="FILENAME" >/etc/hosts</TT +></A ></H2 ><P >Contains a static list of IP Addresses and names. @@ -270,11 +270,11 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1567" -></A +NAME="AEN1470" >9.2.2. <TT CLASS="FILENAME" >/etc/resolv.conf</TT +></A ></H2 ><P >This file tells the name resolution libraries:</P @@ -308,11 +308,11 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1578" -></A +NAME="AEN1481" >9.2.3. <TT CLASS="FILENAME" >/etc/host.conf</TT +></A ></H2 ><P ><TT @@ -337,11 +337,11 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1586" -></A +NAME="AEN1489" >9.2.4. <TT CLASS="FILENAME" >/etc/nsswitch.conf</TT +></A ></H2 ><P >This file controls the actual name resolution targets. The @@ -406,9 +406,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1598" -></A ->9.3. Name resolution as used within MS Windows networking</H1 +NAME="AEN1501" +>9.3. Name resolution as used within MS Windows networking</A +></H1 ><P >MS Windows networking is predicated about the name each machine is given. This name is known variously (and inconsistently) as @@ -428,16 +428,16 @@ the client/server.</P ><PRE CLASS="PROGRAMLISTING" > Unique NetBIOS Names: - MACHINENAME<00> = Server Service is running on MACHINENAME - MACHINENAME<03> = Generic Machine Name (NetBIOS name) - MACHINENAME<20> = LanMan Server service is running on MACHINENAME - WORKGROUP<1b> = Domain Master Browser + MACHINENAME<00> = Server Service is running on MACHINENAME + MACHINENAME<03> = Generic Machine Name (NetBIOS name) + MACHINENAME<20> = LanMan Server service is running on MACHINENAME + WORKGROUP<1b> = Domain Master Browser Group Names: - WORKGROUP<03> = Generic Name registered by all members of WORKGROUP - WORKGROUP<1c> = Domain Controllers / Netlogon Servers - WORKGROUP<1d> = Local Master Browsers - WORKGROUP<1e> = Internet Name Resolvers</PRE + WORKGROUP<03> = Generic Name registered by all members of WORKGROUP + WORKGROUP<1c> = Domain Controllers / Netlogon Servers + WORKGROUP<1d> = Local Master Browsers + WORKGROUP<1e> = Internet Name Resolvers</PRE ></P ><P >It should be noted that all NetBIOS machines register their own @@ -456,7 +456,7 @@ be needed. An example of this is what happens when an MS Windows client wants to locate a domain logon server. It find this service and the IP address of a server that provides it by performing a lookup (via a NetBIOS broadcast) for enumeration of all machines that have -registered the name type *<1c>. A logon request is then sent to each +registered the name type *<1c>. A logon request is then sent to each IP address that is returned in the enumerated list of IP addresses. Which ever machine first replies then ends up providing the logon services.</P ><P @@ -491,9 +491,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1610" -></A ->9.3.1. The NetBIOS Name Cache</H2 +NAME="AEN1513" +>9.3.1. The NetBIOS Name Cache</A +></H2 ><P >All MS Windows machines employ an in memory buffer in which is stored the NetBIOS names and IP addresses for all external @@ -518,9 +518,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1615" -></A ->9.3.2. The LMHOSTS file</H2 +NAME="AEN1518" +>9.3.2. The LMHOSTS file</A +></H2 ><P >This file is usually located in MS Windows NT 4.0 or 2000 in <TT @@ -555,8 +555,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) @@ -565,16 +565,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. @@ -621,9 +621,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1623" -></A ->9.3.3. HOSTS file</H2 +NAME="AEN1526" +>9.3.3. HOSTS file</A +></H2 ><P >This file is usually located in MS Windows NT 4.0 or 2000 in <TT @@ -643,9 +643,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1628" -></A ->9.3.4. DNS Lookup</H2 +NAME="AEN1531" +>9.3.4. DNS Lookup</A +></H2 ><P >This capability is configured in the TCP/IP setup area in the network configuration facility. If enabled an elaborate name resolution sequence @@ -663,9 +663,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1631" -></A ->9.3.5. WINS Lookup</H2 +NAME="AEN1534" +>9.3.5. WINS Lookup</A +></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,11 +692,9 @@ CLASS="PROGRAMLISTING" wins server = xxx.xxx.xxx.xxx</PRE ></P ><P ->where <TT +>where <VAR CLASS="REPLACEABLE" -><I ->xxx.xxx.xxx.xxx</I -></TT +>xxx.xxx.xxx.xxx</VAR > is the IP address of the WINS server.</P ></DIV @@ -706,10 +704,10 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1643" -></A +NAME="AEN1546" >9.4. How browsing functions and how to deploy stable and -dependable browsing using Samba</H1 +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 @@ -773,10 +771,10 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1653" -></A +NAME="AEN1556" >9.5. MS Windows security options and how to configure -Samba for seemless integration</H1 +Samba for seemless integration</A +></H1 ><P >MS Windows clients may use encrypted passwords as part of a challenege/response authentication model (a.k.a. NTLMv1) or @@ -845,43 +843,35 @@ CLASS="PROGRAMLISTING" HREF="smb.conf.5.html#PASSWORDLEVEL" TARGET="_top" >passsword level</A -> = <TT +> = <VAR CLASS="REPLACEABLE" -><I ->integer</I -></TT +>integer</VAR > <A HREF="smb.conf.5.html#USERNAMELEVEL" TARGET="_top" >username level</A -> = <TT +> = <VAR CLASS="REPLACEABLE" -><I ->integer</I -></TT +>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 <TT +character, the <VAR CLASS="PARAMETER" -><I ->username level</I -></TT +>username level</VAR > 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 +the <VAR CLASS="PARAMETER" -><I ->password level</I -></TT +>password level</VAR > must be set to the maximum number of upper case letter which <SPAN CLASS="emphasis" @@ -891,11 +881,9 @@ CLASS="EMPHASIS" ></SPAN > appear is a password. Note that is the server OS uses the traditional -DES version of crypt(), then a <TT +DES version of crypt(), then a <VAR CLASS="PARAMETER" -><I ->password level</I -></TT +>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 @@ -910,9 +898,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1681" -></A ->9.5.1. Use MS Windows NT as an authentication server</H2 +NAME="AEN1584" +>9.5.1. Use MS Windows NT as an authentication server</A +></H2 ><P >This method involves the additions of the following parameters in the smb.conf file:</P @@ -946,9 +934,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1689" -></A ->9.5.2. Make Samba a member of an MS Windows NT security domain</H2 +NAME="AEN1592" +>9.5.2. Make Samba a member of an MS Windows NT security domain</A +></H2 ><P >This method involves additon of the following paramters in the smb.conf file:</P ><P @@ -1009,9 +997,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1706" -></A ->9.5.3. Configure Samba as an authentication server</H2 +NAME="AEN1609" +>9.5.3. Configure Samba as an authentication server</A +></H2 ><P >This mode of authentication demands that there be on the Unix/Linux system both a Unix style account as well as an @@ -1046,9 +1034,9 @@ CLASS="SECT3" ><H3 CLASS="SECT3" ><A -NAME="AEN1713" -></A ->9.5.3.1. Users</H3 +NAME="AEN1616" +>9.5.3.1. Users</A +></H3 ><P >A user account that may provide a home directory should be created. The following Linux system commands are typical of @@ -1058,10 +1046,10 @@ the procedure for creating an account.</P CLASS="PROGRAMLISTING" > # useradd -s /bin/bash -d /home/"userid" -m "userid" # passwd "userid" - Enter Password: <pw> + Enter Password: <pw> # smbpasswd -a "userid" - Enter Password: <pw></PRE + Enter Password: <pw></PRE ></P ></DIV ><DIV @@ -1069,9 +1057,9 @@ CLASS="SECT3" ><H3 CLASS="SECT3" ><A -NAME="AEN1718" -></A ->9.5.3.2. MS Windows NT Machine Accounts</H3 +NAME="AEN1621" +>9.5.3.2. MS Windows NT Machine Accounts</A +></H3 ><P >These are required only when Samba is used as a domain controller. Refer to the Samba-PDC-HOWTO for more details.</P @@ -1090,9 +1078,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1723" -></A ->9.6. Conclusions</H1 +NAME="AEN1626" +>9.6. Conclusions</A +></H1 ><P >Samba provides a flexible means to operate as...</P ><P diff --git a/docs/htmldocs/introduction.html b/docs/htmldocs/introduction.html index a68950fede..199b1b8f30 100644 --- a/docs/htmldocs/introduction.html +++ b/docs/htmldocs/introduction.html @@ -5,7 +5,7 @@ >General installation</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -104,105 +104,61 @@ HREF="install.html" ><DT >1.1. <A HREF="install.html#AEN26" ->Read the man pages</A +>Obtaining and installing samba</A ></DT ><DT >1.2. <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 +HREF="install.html#AEN31" +>Configuring samba</A ></DT ><DD ><DL ><DT ->1.6.1. <A -HREF="install.html#AEN100" ->Starting from inetd.conf</A +>1.2.1. <A +HREF="install.html#AEN36" +>Editing the smb.conf file</A ></DT ><DT ->1.6.2. <A -HREF="install.html#AEN129" ->Alternative: starting it as a daemon</A +>1.2.2. <A +HREF="install.html#AEN58" +>SWAT</A ></DT ></DL ></DD ><DT ->1.7. <A -HREF="install.html#AEN145" +>1.3. <A +HREF="install.html#AEN64" >Try listing the shares available on your server</A ></DT ><DT ->1.8. <A -HREF="install.html#AEN154" +>1.4. <A +HREF="install.html#AEN73" >Try connecting with the unix client</A ></DT ><DT ->1.9. <A -HREF="install.html#AEN170" +>1.5. <A +HREF="install.html#AEN89" >Try connecting from a DOS, WfWg, Win9x, WinNT, Win2k, OS/2, etc... client</A ></DT ><DT ->1.10. <A -HREF="install.html#AEN184" +>1.6. <A +HREF="install.html#AEN103" >What If Things Don't Work?</A ></DT ><DD ><DL ><DT ->1.10.1. <A -HREF="install.html#AEN189" ->Diagnosing Problems</A -></DT -><DT ->1.10.2. <A -HREF="install.html#AEN193" +>1.6.1. <A +HREF="install.html#AEN108" >Scope IDs</A ></DT ><DT ->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" +>1.6.2. <A +HREF="install.html#AEN111" >Locking</A ></DT -><DT ->1.10.6. <A -HREF="install.html#AEN219" ->Mapping Usernames</A -></DT ></DL ></DD ></DL @@ -216,32 +172,32 @@ HREF="browsing-quick.html" ><DL ><DT >2.1. <A -HREF="browsing-quick.html#AEN230" +HREF="browsing-quick.html#AEN130" >Discussion</A ></DT ><DT >2.2. <A -HREF="browsing-quick.html#AEN238" +HREF="browsing-quick.html#AEN139" >Use of the "Remote Announce" parameter</A ></DT ><DT >2.3. <A -HREF="browsing-quick.html#AEN252" +HREF="browsing-quick.html#AEN153" >Use of the "Remote Browse Sync" parameter</A ></DT ><DT >2.4. <A -HREF="browsing-quick.html#AEN257" +HREF="browsing-quick.html#AEN158" >Use of WINS</A ></DT ><DT >2.5. <A -HREF="browsing-quick.html#AEN268" +HREF="browsing-quick.html#AEN169" >Do NOT use more than one (1) protocol on MS Windows machines</A ></DT ><DT >2.6. <A -HREF="browsing-quick.html#AEN274" +HREF="browsing-quick.html#AEN177" >Name Resolution Order</A ></DT ></DL @@ -255,146 +211,146 @@ HREF="passdb.html" ><DL ><DT >3.1. <A -HREF="passdb.html#AEN324" +HREF="passdb.html#AEN227" >Introduction</A ></DT ><DT >3.2. <A -HREF="passdb.html#AEN331" +HREF="passdb.html#AEN234" >Important Notes About Security</A ></DT ><DD ><DL ><DT >3.2.1. <A -HREF="passdb.html#AEN346" +HREF="passdb.html#AEN249" >Advantages of SMB Encryption</A ></DT ><DT >3.2.2. <A -HREF="passdb.html#AEN351" +HREF="passdb.html#AEN254" >Advantages of non-encrypted passwords</A ></DT ></DL ></DD ><DT >3.3. <A -HREF="passdb.html#AEN357" +HREF="passdb.html#AEN260" >The smbpasswd Command</A ></DT ><DT >3.4. <A -HREF="passdb.html#AEN388" +HREF="passdb.html#AEN291" >Plain text</A ></DT ><DT >3.5. <A -HREF="passdb.html#AEN393" +HREF="passdb.html#AEN296" >TDB</A ></DT ><DT >3.6. <A -HREF="passdb.html#AEN396" +HREF="passdb.html#AEN299" >LDAP</A ></DT ><DD ><DL ><DT >3.6.1. <A -HREF="passdb.html#AEN398" +HREF="passdb.html#AEN301" >Introduction</A ></DT ><DT >3.6.2. <A -HREF="passdb.html#AEN418" +HREF="passdb.html#AEN321" >Introduction</A ></DT ><DT >3.6.3. <A -HREF="passdb.html#AEN447" +HREF="passdb.html#AEN350" >Supported LDAP Servers</A ></DT ><DT >3.6.4. <A -HREF="passdb.html#AEN452" +HREF="passdb.html#AEN355" >Schema and Relationship to the RFC 2307 posixAccount</A ></DT ><DT >3.6.5. <A -HREF="passdb.html#AEN464" +HREF="passdb.html#AEN367" >Configuring Samba with LDAP</A ></DT ><DT >3.6.6. <A -HREF="passdb.html#AEN511" +HREF="passdb.html#AEN414" >Accounts and Groups management</A ></DT ><DT >3.6.7. <A -HREF="passdb.html#AEN516" +HREF="passdb.html#AEN419" >Security and sambaAccount</A ></DT ><DT >3.6.8. <A -HREF="passdb.html#AEN536" +HREF="passdb.html#AEN439" >LDAP specials attributes for sambaAccounts</A ></DT ><DT >3.6.9. <A -HREF="passdb.html#AEN606" +HREF="passdb.html#AEN509" >Example LDIF Entries for a sambaAccount</A ></DT ></DL ></DD ><DT >3.7. <A -HREF="passdb.html#AEN614" +HREF="passdb.html#AEN517" >MySQL</A ></DT ><DD ><DL ><DT >3.7.1. <A -HREF="passdb.html#AEN616" +HREF="passdb.html#AEN519" >Building</A ></DT ><DT >3.7.2. <A -HREF="passdb.html#AEN622" +HREF="passdb.html#AEN525" >Creating the database</A ></DT ><DT >3.7.3. <A -HREF="passdb.html#AEN632" +HREF="passdb.html#AEN535" >Configuring</A ></DT ><DT >3.7.4. <A -HREF="passdb.html#AEN649" +HREF="passdb.html#AEN552" >Using plaintext passwords or encrypted password</A ></DT ><DT >3.7.5. <A -HREF="passdb.html#AEN654" +HREF="passdb.html#AEN557" >Getting non-column data from the table</A ></DT ></DL ></DD ><DT >3.8. <A -HREF="passdb.html#AEN662" +HREF="passdb.html#AEN565" >Passdb XML plugin</A ></DT ><DD ><DL ><DT >3.8.1. <A -HREF="passdb.html#AEN664" +HREF="passdb.html#AEN567" >Building</A ></DT ><DT >3.8.2. <A -HREF="passdb.html#AEN670" +HREF="passdb.html#AEN573" >Usage</A ></DT ></DL diff --git a/docs/htmldocs/lmhosts.5.html b/docs/htmldocs/lmhosts.5.html index 2977cb1227..375fe5618d 100644 --- a/docs/htmldocs/lmhosts.5.html +++ b/docs/htmldocs/lmhosts.5.html @@ -5,7 +5,7 @@ >lmhosts</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"></HEAD +CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD ><BODY CLASS="REFENTRY" BGCOLOR="#FFFFFF" diff --git a/docs/htmldocs/msdfs.html b/docs/htmldocs/msdfs.html index f10e0995d5..214f01c135 100644 --- a/docs/htmldocs/msdfs.html +++ b/docs/htmldocs/msdfs.html @@ -5,7 +5,7 @@ >Hosting a Microsoft Distributed File System tree on Samba</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -81,9 +81,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1993" -></A ->12.1. Instructions</H1 +NAME="AEN1896" +>12.1. Instructions</A +></H1 ><P >The Distributed File System (or Dfs) provides a means of separating the logical view of files and directories that users @@ -99,21 +99,17 @@ TARGET="_top" machine (for Dfs-aware clients to browse) using Samba.</P ><P >To enable SMB-based DFS for Samba, configure it with the - <TT + <VAR CLASS="PARAMETER" -><I ->--with-msdfs</I -></TT +>--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" -><TT +><VAR CLASS="PARAMETER" -><I -> host msdfs</I -></TT +> host msdfs</VAR ></A > parameter in the <TT CLASS="FILENAME" @@ -123,18 +119,16 @@ CLASS="FILENAME" level boolean <A HREF="smb.conf.5.html#MSDFSROOT" TARGET="_top" -><TT +><VAR CLASS="PARAMETER" -><I -> msdfs root</I -></TT +> 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 +>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 @@ -162,54 +156,44 @@ CLASS="PROGRAMLISTING" >In the /export/dfsroot directory we set up our dfs links to other servers on the network.</P ><P -><TT +><SAMP CLASS="PROMPT" ->root# </TT -><TT +>root# </SAMP +><KBD CLASS="USERINPUT" -><B ->cd /export/dfsroot</B -></TT +>cd /export/dfsroot</KBD ></P ><P -><TT +><SAMP CLASS="PROMPT" ->root# </TT -><TT +>root# </SAMP +><KBD CLASS="USERINPUT" -><B ->chown root /export/dfsroot</B -></TT +>chown root /export/dfsroot</KBD ></P ><P -><TT +><SAMP CLASS="PROMPT" ->root# </TT -><TT +>root# </SAMP +><KBD CLASS="USERINPUT" -><B ->chmod 755 /export/dfsroot</B -></TT +>chmod 755 /export/dfsroot</KBD ></P ><P -><TT +><SAMP CLASS="PROMPT" ->root# </TT -><TT +>root# </SAMP +><KBD CLASS="USERINPUT" -><B ->ln -s msdfs:storageA\\shareA linka</B -></TT +>ln -s msdfs:storageA\\shareA linka</KBD ></P ><P -><TT +><SAMP CLASS="PROMPT" ->root# </TT -><TT +>root# </SAMP +><KBD CLASS="USERINPUT" -><B ->ln -s msdfs:serverB\\share,serverC\\share linkb</B -></TT +>ln -s msdfs:serverB\\share,serverC\\share linkb</KBD ></P ><P >You should set up the permissions and ownership of @@ -229,9 +213,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2028" -></A ->12.1.1. Notes</H2 +NAME="AEN1931" +>12.1.1. Notes</A +></H2 ><P ></P ><UL diff --git a/docs/htmldocs/net.8.html b/docs/htmldocs/net.8.html index 1652fb4141..63becc2071 100644 --- a/docs/htmldocs/net.8.html +++ b/docs/htmldocs/net.8.html @@ -5,7 +5,7 @@ >net</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"></HEAD +CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD ><BODY CLASS="REFENTRY" BGCOLOR="#FFFFFF" @@ -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" @@ -317,21 +317,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 +345,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 +366,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 diff --git a/docs/htmldocs/nmbd.8.html b/docs/htmldocs/nmbd.8.html index 87a042a912..f4f8caf81f 100644 --- a/docs/htmldocs/nmbd.8.html +++ b/docs/htmldocs/nmbd.8.html @@ -5,7 +5,7 @@ >nmbd</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"></HEAD +CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD ><BODY CLASS="REFENTRY" BGCOLOR="#FFFFFF" @@ -38,7 +38,7 @@ NAME="AEN8" ><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" @@ -215,9 +215,9 @@ CLASS="COMMAND" CLASS="COMMAND" >nmbd</B > also logs to standard - output, as if the <TT + output, as if the <CODE CLASS="CONSTANT" ->-S</TT +>-S</CODE > parameter had been given. </P ></DD @@ -244,7 +244,7 @@ CLASS="COMMAND" >.</P ></DD ><DT ->-H <filename></DT +>-H <filename></DT ><DD ><P >NetBIOS lmhosts file. The lmhosts @@ -253,12 +253,10 @@ CLASS="COMMAND" resolution mechanism <A HREF="smb.conf.5.html#nameresolveorder" TARGET="_top" -><TT +><VAR CLASS="PARAMETER" -><I >name resolve - order</I -></TT + order</VAR ></A > described in <SPAN CLASS="CITEREFENTRY" @@ -320,7 +318,7 @@ CLASS="COMMAND" >.</P ></DD ><DT ->-d <debug level></DT +>-d <debug level></DT ><DD ><P >debuglevel is an integer @@ -344,11 +342,9 @@ CLASS="COMMAND" the <A HREF="smb.conf.5.html#loglevel" TARGET="_top" -><TT +><VAR CLASS="PARAMETER" -><I ->log level</I -></TT +>log level</VAR ></A > parameter in the <SPAN @@ -360,7 +356,7 @@ CLASS="REFENTRYTITLE" > file.</P ></DD ><DT ->-l <log directory></DT +>-l <log directory></DT ><DD ><P >The -l parameter specifies a directory @@ -395,7 +391,7 @@ CLASS="COMMAND" </P ></DD ><DT ->-n <primary NetBIOS name></DT +>-n <primary NetBIOS name></DT ><DD ><P >This option allows you to override @@ -403,12 +399,10 @@ CLASS="COMMAND" to setting the <A HREF="smb.conf.5.html#netbiosname" TARGET="_top" -><TT +><VAR CLASS="PARAMETER" -><I >NetBIOS - name</I -></TT + name</VAR ></A > parameter in the <SPAN CLASS="CITEREFENTRY" @@ -427,7 +421,7 @@ CLASS="REFENTRYTITLE" >.</P ></DD ><DT ->-p <UDP port number></DT +>-p <UDP port number></DT ><DD ><P >UDP port number is a positive integer value. @@ -440,7 +434,7 @@ CLASS="COMMAND" won't need help!</P ></DD ><DT ->-s <configuration file></DT +>-s <configuration file></DT ><DD ><P >The default configuration file name @@ -565,9 +559,9 @@ CLASS="FILENAME" <A HREF="smb.conf.5.html#WINSSUPPORT" TARGET="_top" -><TT +><CODE CLASS="CONSTANT" ->wins support</TT +>wins support</CODE ></A > parameter in the <SPAN @@ -603,9 +597,9 @@ CLASS="EMPHASIS" > (see the <A HREF="smb.conf.5.html#LOCALMASTER" TARGET="_top" -><TT +><CODE CLASS="CONSTANT" ->local master</TT +>local master</CODE ></A > parameter in the <SPAN diff --git a/docs/htmldocs/nmblookup.1.html b/docs/htmldocs/nmblookup.1.html index 9e6da1c7b2..1e3c3c56ad 100644 --- a/docs/htmldocs/nmblookup.1.html +++ b/docs/htmldocs/nmblookup.1.html @@ -5,7 +5,7 @@ >nmblookup</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"></HEAD +CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></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" @@ -82,24 +82,20 @@ CLASS="VARIABLELIST" ><DD ><P >Searches for a master browser by looking - up the NetBIOS name <TT + up the NetBIOS name <VAR CLASS="REPLACEABLE" -><I ->name</I -></TT +>name</VAR > with a - type of <TT + type of <CODE CLASS="CONSTANT" ->0x1d</TT ->. If <TT +>0x1d</CODE +>. If <VAR CLASS="REPLACEABLE" -><I -> name</I -></TT +> name</VAR > is "-" then it does a lookup on the special name - <TT + <CODE CLASS="CONSTANT" ->__MSBROWSE__</TT +>__MSBROWSE__</CODE >.</P ></DD ><DT @@ -145,11 +141,9 @@ CLASS="REFENTRYTITLE" >-A</DT ><DD ><P ->Interpret <TT +>Interpret <VAR CLASS="REPLACEABLE" -><I ->name</I -></TT +>name</VAR > as an IP Address and do a node status query on this address.</P ></DD @@ -160,7 +154,7 @@ CLASS="REPLACEABLE" >Print a help (usage) message.</P ></DD ><DT ->-B <broadcast address></DT +>-B <broadcast address></DT ><DD ><P >Send the query to the given broadcast address. Without @@ -169,11 +163,9 @@ CLASS="REPLACEABLE" either auto-detected or defined in the <A HREF="smb.conf.5.html#INTERFACES" TARGET="_top" -><TT +><VAR CLASS="PARAMETER" -><I ->interfaces</I -></TT +>interfaces</VAR > </A > parameter of the <SPAN @@ -186,26 +178,22 @@ CLASS="REFENTRYTITLE" </P ></DD ><DT ->-U <unicast address></DT +>-U <unicast address></DT ><DD ><P >Do a unicast query to the specified address or - host <TT + host <VAR CLASS="REPLACEABLE" -><I ->unicast address</I -></TT +>unicast address</VAR >. This option - (along with the <TT + (along with the <VAR CLASS="PARAMETER" -><I ->-R</I -></TT +>-R</VAR > option) is needed to query a WINS server.</P ></DD ><DT ->-d <debuglevel></DT +>-d <debuglevel></DT ><DD ><P >debuglevel is an integer from 0 to 10.</P @@ -229,11 +217,9 @@ CLASS="COMMAND" the <A HREF="smb.conf.5.html#LOGLEVEL" TARGET="_top" -><TT +><VAR CLASS="PARAMETER" -><I -> log level</I -></TT +> log level</VAR ></A > parameter in the <TT CLASS="FILENAME" @@ -241,7 +227,7 @@ CLASS="FILENAME" > file.</P ></DD ><DT ->-s <smb.conf></DT +>-s <smb.conf></DT ><DD ><P >This parameter specifies the pathname to @@ -253,7 +239,7 @@ TARGET="_top" the Samba setup on the machine.</P ></DD ><DT ->-i <scope></DT +>-i <scope></DT ><DD ><P >This specifies a NetBIOS scope that @@ -307,7 +293,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 diff --git a/docs/htmldocs/oplocks.html b/docs/htmldocs/oplocks.html deleted file mode 100644 index 6aa91fb17f..0000000000 --- a/docs/htmldocs/oplocks.html +++ /dev/null @@ -1,208 +0,0 @@ -<!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 b5564b9f26..6ef6188311 100644 --- a/docs/htmldocs/optional.html +++ b/docs/htmldocs/optional.html @@ -5,7 +5,7 @@ >Optional configuration</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -78,7 +78,7 @@ CLASS="TITLE" ><DIV CLASS="PARTINTRO" ><A -NAME="AEN1499" +NAME="AEN1402" ></A ><H1 >Introduction</H1 @@ -102,19 +102,19 @@ HREF="integrate-ms-networks.html" ><DL ><DT >9.1. <A -HREF="integrate-ms-networks.html#AEN1513" +HREF="integrate-ms-networks.html#AEN1416" >Agenda</A ></DT ><DT >9.2. <A -HREF="integrate-ms-networks.html#AEN1535" +HREF="integrate-ms-networks.html#AEN1438" >Name Resolution in a pure Unix/Linux world</A ></DT ><DD ><DL ><DT >9.2.1. <A -HREF="integrate-ms-networks.html#AEN1551" +HREF="integrate-ms-networks.html#AEN1454" ><TT CLASS="FILENAME" >/etc/hosts</TT @@ -122,7 +122,7 @@ CLASS="FILENAME" ></DT ><DT >9.2.2. <A -HREF="integrate-ms-networks.html#AEN1567" +HREF="integrate-ms-networks.html#AEN1470" ><TT CLASS="FILENAME" >/etc/resolv.conf</TT @@ -130,7 +130,7 @@ CLASS="FILENAME" ></DT ><DT >9.2.3. <A -HREF="integrate-ms-networks.html#AEN1578" +HREF="integrate-ms-networks.html#AEN1481" ><TT CLASS="FILENAME" >/etc/host.conf</TT @@ -138,7 +138,7 @@ CLASS="FILENAME" ></DT ><DT >9.2.4. <A -HREF="integrate-ms-networks.html#AEN1586" +HREF="integrate-ms-networks.html#AEN1489" ><TT CLASS="FILENAME" >/etc/nsswitch.conf</TT @@ -148,47 +148,47 @@ CLASS="FILENAME" ></DD ><DT >9.3. <A -HREF="integrate-ms-networks.html#AEN1598" +HREF="integrate-ms-networks.html#AEN1501" >Name resolution as used within MS Windows networking</A ></DT ><DD ><DL ><DT >9.3.1. <A -HREF="integrate-ms-networks.html#AEN1610" +HREF="integrate-ms-networks.html#AEN1513" >The NetBIOS Name Cache</A ></DT ><DT >9.3.2. <A -HREF="integrate-ms-networks.html#AEN1615" +HREF="integrate-ms-networks.html#AEN1518" >The LMHOSTS file</A ></DT ><DT >9.3.3. <A -HREF="integrate-ms-networks.html#AEN1623" +HREF="integrate-ms-networks.html#AEN1526" >HOSTS file</A ></DT ><DT >9.3.4. <A -HREF="integrate-ms-networks.html#AEN1628" +HREF="integrate-ms-networks.html#AEN1531" >DNS Lookup</A ></DT ><DT >9.3.5. <A -HREF="integrate-ms-networks.html#AEN1631" +HREF="integrate-ms-networks.html#AEN1534" >WINS Lookup</A ></DT ></DL ></DD ><DT >9.4. <A -HREF="integrate-ms-networks.html#AEN1643" +HREF="integrate-ms-networks.html#AEN1546" >How browsing functions and how to deploy stable and dependable browsing using Samba</A ></DT ><DT >9.5. <A -HREF="integrate-ms-networks.html#AEN1653" +HREF="integrate-ms-networks.html#AEN1556" >MS Windows security options and how to configure Samba for seemless integration</A ></DT @@ -196,24 +196,24 @@ Samba for seemless integration</A ><DL ><DT >9.5.1. <A -HREF="integrate-ms-networks.html#AEN1681" +HREF="integrate-ms-networks.html#AEN1584" >Use MS Windows NT as an authentication server</A ></DT ><DT >9.5.2. <A -HREF="integrate-ms-networks.html#AEN1689" +HREF="integrate-ms-networks.html#AEN1592" >Make Samba a member of an MS Windows NT security domain</A ></DT ><DT >9.5.3. <A -HREF="integrate-ms-networks.html#AEN1706" +HREF="integrate-ms-networks.html#AEN1609" >Configure Samba as an authentication server</A ></DT ></DL ></DD ><DT >9.6. <A -HREF="integrate-ms-networks.html#AEN1723" +HREF="integrate-ms-networks.html#AEN1626" >Conclusions</A ></DT ></DL @@ -227,53 +227,53 @@ HREF="unix-permissions.html" ><DL ><DT >10.1. <A -HREF="unix-permissions.html#AEN1744" +HREF="unix-permissions.html#AEN1647" >Viewing and changing UNIX permissions using the NT security dialogs</A ></DT ><DT >10.2. <A -HREF="unix-permissions.html#AEN1748" +HREF="unix-permissions.html#AEN1651" >How to view file security on a Samba share</A ></DT ><DT >10.3. <A -HREF="unix-permissions.html#AEN1759" +HREF="unix-permissions.html#AEN1662" >Viewing file ownership</A ></DT ><DT >10.4. <A -HREF="unix-permissions.html#AEN1779" +HREF="unix-permissions.html#AEN1682" >Viewing file or directory permissions</A ></DT ><DD ><DL ><DT >10.4.1. <A -HREF="unix-permissions.html#AEN1794" +HREF="unix-permissions.html#AEN1697" >File Permissions</A ></DT ><DT >10.4.2. <A -HREF="unix-permissions.html#AEN1808" +HREF="unix-permissions.html#AEN1711" >Directory Permissions</A ></DT ></DL ></DD ><DT >10.5. <A -HREF="unix-permissions.html#AEN1815" +HREF="unix-permissions.html#AEN1718" >Modifying file or directory permissions</A ></DT ><DT >10.6. <A -HREF="unix-permissions.html#AEN1837" +HREF="unix-permissions.html#AEN1740" >Interaction with the standard Samba create mask parameters</A ></DT ><DT >10.7. <A -HREF="unix-permissions.html#AEN1901" +HREF="unix-permissions.html#AEN1804" >Interaction with the standard Samba file attribute mapping</A ></DT @@ -289,17 +289,17 @@ managed authentication</A ><DL ><DT >11.1. <A -HREF="pam.html#AEN1922" +HREF="pam.html#AEN1825" >Samba and PAM</A ></DT ><DT >11.2. <A -HREF="pam.html#AEN1966" +HREF="pam.html#AEN1869" >Distributed Authentication</A ></DT ><DT >11.3. <A -HREF="pam.html#AEN1973" +HREF="pam.html#AEN1876" >PAM Configuration in smb.conf</A ></DT ></DL @@ -313,14 +313,14 @@ HREF="msdfs.html" ><DL ><DT >12.1. <A -HREF="msdfs.html#AEN1993" +HREF="msdfs.html#AEN1896" >Instructions</A ></DT ><DD ><DL ><DT >12.1.1. <A -HREF="msdfs.html#AEN2028" +HREF="msdfs.html#AEN1931" >Notes</A ></DT ></DL @@ -336,122 +336,122 @@ HREF="printing.html" ><DL ><DT >13.1. <A -HREF="printing.html#AEN2054" +HREF="printing.html#AEN1957" >Introduction</A ></DT ><DT >13.2. <A -HREF="printing.html#AEN2076" +HREF="printing.html#AEN1979" >Configuration</A ></DT ><DD ><DL ><DT >13.2.1. <A -HREF="printing.html#AEN2084" +HREF="printing.html#AEN1987" >Creating [print$]</A ></DT ><DT >13.2.2. <A -HREF="printing.html#AEN2119" +HREF="printing.html#AEN2022" >Setting Drivers for Existing Printers</A ></DT ><DT >13.2.3. <A -HREF="printing.html#AEN2135" +HREF="printing.html#AEN2038" >Support a large number of printers</A ></DT ><DT >13.2.4. <A -HREF="printing.html#AEN2146" +HREF="printing.html#AEN2049" >Adding New Printers via the Windows NT APW</A ></DT ><DT >13.2.5. <A -HREF="printing.html#AEN2176" +HREF="printing.html#AEN2079" >Samba and Printer Ports</A ></DT ></DL ></DD ><DT >13.3. <A -HREF="printing.html#AEN2184" +HREF="printing.html#AEN2087" >The Imprints Toolset</A ></DT ><DD ><DL ><DT >13.3.1. <A -HREF="printing.html#AEN2188" +HREF="printing.html#AEN2091" >What is Imprints?</A ></DT ><DT >13.3.2. <A -HREF="printing.html#AEN2198" +HREF="printing.html#AEN2101" >Creating Printer Driver Packages</A ></DT ><DT >13.3.3. <A -HREF="printing.html#AEN2201" +HREF="printing.html#AEN2104" >The Imprints server</A ></DT ><DT >13.3.4. <A -HREF="printing.html#AEN2205" +HREF="printing.html#AEN2108" >The Installation Client</A ></DT ></DL ></DD ><DT >13.4. <A -HREF="printing.html#AEN2227" +HREF="printing.html#AEN2130" >Diagnosis</A ></DT ><DD ><DL ><DT >13.4.1. <A -HREF="printing.html#AEN2229" +HREF="printing.html#AEN2132" >Introduction</A ></DT ><DT >13.4.2. <A -HREF="printing.html#AEN2245" +HREF="printing.html#AEN2148" >Debugging printer problems</A ></DT ><DT >13.4.3. <A -HREF="printing.html#AEN2254" +HREF="printing.html#AEN2157" >What printers do I have?</A ></DT ><DT >13.4.4. <A -HREF="printing.html#AEN2262" +HREF="printing.html#AEN2165" >Setting up printcap and print servers</A ></DT ><DT >13.4.5. <A -HREF="printing.html#AEN2290" +HREF="printing.html#AEN2193" >Job sent, no output</A ></DT ><DT >13.4.6. <A -HREF="printing.html#AEN2301" +HREF="printing.html#AEN2204" >Job sent, strange output</A ></DT ><DT >13.4.7. <A -HREF="printing.html#AEN2313" +HREF="printing.html#AEN2216" >Raw PostScript printed</A ></DT ><DT >13.4.8. <A -HREF="printing.html#AEN2316" +HREF="printing.html#AEN2219" >Advanced Printing</A ></DT ><DT >13.4.9. <A -HREF="printing.html#AEN2319" +HREF="printing.html#AEN2222" >Real debugging</A ></DT ></DL @@ -467,99 +467,99 @@ HREF="winbind.html" ><DL ><DT >14.1. <A -HREF="winbind.html#AEN2360" +HREF="winbind.html#AEN2263" >Abstract</A ></DT ><DT >14.2. <A -HREF="winbind.html#AEN2364" +HREF="winbind.html#AEN2267" >Introduction</A ></DT ><DT >14.3. <A -HREF="winbind.html#AEN2377" +HREF="winbind.html#AEN2280" >What Winbind Provides</A ></DT ><DD ><DL ><DT >14.3.1. <A -HREF="winbind.html#AEN2384" +HREF="winbind.html#AEN2287" >Target Uses</A ></DT ></DL ></DD ><DT >14.4. <A -HREF="winbind.html#AEN2388" +HREF="winbind.html#AEN2291" >How Winbind Works</A ></DT ><DD ><DL ><DT >14.4.1. <A -HREF="winbind.html#AEN2393" +HREF="winbind.html#AEN2296" >Microsoft Remote Procedure Calls</A ></DT ><DT >14.4.2. <A -HREF="winbind.html#AEN2397" +HREF="winbind.html#AEN2300" >Microsoft Active Directory Services</A ></DT ><DT >14.4.3. <A -HREF="winbind.html#AEN2400" +HREF="winbind.html#AEN2303" >Name Service Switch</A ></DT ><DT >14.4.4. <A -HREF="winbind.html#AEN2416" +HREF="winbind.html#AEN2319" >Pluggable Authentication Modules</A ></DT ><DT >14.4.5. <A -HREF="winbind.html#AEN2424" +HREF="winbind.html#AEN2327" >User and Group ID Allocation</A ></DT ><DT >14.4.6. <A -HREF="winbind.html#AEN2428" +HREF="winbind.html#AEN2331" >Result Caching</A ></DT ></DL ></DD ><DT >14.5. <A -HREF="winbind.html#AEN2431" +HREF="winbind.html#AEN2334" >Installation and Configuration</A ></DT ><DD ><DL ><DT >14.5.1. <A -HREF="winbind.html#AEN2438" +HREF="winbind.html#AEN2341" >Introduction</A ></DT ><DT >14.5.2. <A -HREF="winbind.html#AEN2451" +HREF="winbind.html#AEN2354" >Requirements</A ></DT ><DT >14.5.3. <A -HREF="winbind.html#AEN2465" +HREF="winbind.html#AEN2368" >Testing Things Out</A ></DT ></DL ></DD ><DT >14.6. <A -HREF="winbind.html#AEN2680" +HREF="winbind.html#AEN2583" >Limitations</A ></DT ><DT >14.7. <A -HREF="winbind.html#AEN2690" +HREF="winbind.html#AEN2593" >Conclusion</A ></DT ></DL @@ -573,66 +573,66 @@ HREF="improved-browsing.html" ><DL ><DT >15.1. <A -HREF="improved-browsing.html#AEN2700" +HREF="improved-browsing.html#AEN2603" >Overview of browsing</A ></DT ><DT >15.2. <A -HREF="improved-browsing.html#AEN2704" +HREF="improved-browsing.html#AEN2608" >Browsing support in samba</A ></DT ><DT >15.3. <A -HREF="improved-browsing.html#AEN2713" +HREF="improved-browsing.html#AEN2616" >Problem resolution</A ></DT ><DT >15.4. <A -HREF="improved-browsing.html#AEN2720" +HREF="improved-browsing.html#AEN2625" >Browsing across subnets</A ></DT ><DD ><DL ><DT >15.4.1. <A -HREF="improved-browsing.html#AEN2725" +HREF="improved-browsing.html#AEN2630" >How does cross subnet browsing work ?</A ></DT ></DL ></DD ><DT >15.5. <A -HREF="improved-browsing.html#AEN2760" +HREF="improved-browsing.html#AEN2665" >Setting up a WINS server</A ></DT ><DT >15.6. <A -HREF="improved-browsing.html#AEN2779" +HREF="improved-browsing.html#AEN2684" >Setting up Browsing in a WORKGROUP</A ></DT ><DT >15.7. <A -HREF="improved-browsing.html#AEN2797" +HREF="improved-browsing.html#AEN2702" >Setting up Browsing in a DOMAIN</A ></DT ><DT >15.8. <A -HREF="improved-browsing.html#AEN2807" +HREF="improved-browsing.html#AEN2712" >Forcing samba to be the master</A ></DT ><DT >15.9. <A -HREF="improved-browsing.html#AEN2816" +HREF="improved-browsing.html#AEN2721" >Making samba the domain master</A ></DT ><DT >15.10. <A -HREF="improved-browsing.html#AEN2834" +HREF="improved-browsing.html#AEN2739" >Note about broadcast addresses</A ></DT ><DT >15.11. <A -HREF="improved-browsing.html#AEN2837" +HREF="improved-browsing.html#AEN2742" >Multiple interfaces</A ></DT ></DL @@ -646,48 +646,48 @@ HREF="vfs.html" ><DL ><DT >16.1. <A -HREF="vfs.html#AEN2855" +HREF="vfs.html#AEN2760" >Introduction and configuration</A ></DT ><DT >16.2. <A -HREF="vfs.html#AEN2864" +HREF="vfs.html#AEN2769" >Included modules</A ></DT ><DD ><DL ><DT >16.2.1. <A -HREF="vfs.html#AEN2866" +HREF="vfs.html#AEN2771" >audit</A ></DT ><DT >16.2.2. <A -HREF="vfs.html#AEN2874" +HREF="vfs.html#AEN2779" >recycle</A ></DT ><DT >16.2.3. <A -HREF="vfs.html#AEN2911" +HREF="vfs.html#AEN2816" >netatalk</A ></DT ></DL ></DD ><DT >16.3. <A -HREF="vfs.html#AEN2918" +HREF="vfs.html#AEN2823" >VFS modules available elsewhere</A ></DT ><DD ><DL ><DT >16.3.1. <A -HREF="vfs.html#AEN2922" +HREF="vfs.html#AEN2827" >DatabaseFS</A ></DT ><DT >16.3.2. <A -HREF="vfs.html#AEN2930" +HREF="vfs.html#AEN2835" >vscan</A ></DT ></DL @@ -696,149 +696,155 @@ HREF="vfs.html#AEN2930" ></DD ><DT >17. <A -HREF="cvs-access.html" ->Access Samba source code via CVS</A -></DT -><DD -><DL -><DT ->17.1. <A -HREF="cvs-access.html#AEN2942" ->Introduction</A -></DT -><DT ->17.2. <A -HREF="cvs-access.html#AEN2947" ->CVS Access to samba.org</A -></DT -><DD -><DL -><DT ->17.2.1. <A -HREF="cvs-access.html#AEN2950" ->Access via CVSweb</A -></DT -><DT ->17.2.2. <A -HREF="cvs-access.html#AEN2955" ->Access via cvs</A -></DT -></DL -></DD -></DL -></DD -><DT ->18. <A HREF="groupmapping.html" >Group mapping HOWTO</A ></DT ><DT ->19. <A +>18. <A HREF="speed.html" >Samba performance issues</A ></DT ><DD ><DL ><DT ->19.1. <A -HREF="speed.html#AEN3033" +>18.1. <A +HREF="speed.html#AEN2890" >Comparisons</A ></DT ><DT ->19.2. <A -HREF="speed.html#AEN3039" +>18.2. <A +HREF="speed.html#AEN2896" >Socket options</A ></DT ><DT ->19.3. <A -HREF="speed.html#AEN3046" +>18.3. <A +HREF="speed.html#AEN2903" >Read size</A ></DT ><DT ->19.4. <A -HREF="speed.html#AEN3051" +>18.4. <A +HREF="speed.html#AEN2908" >Max xmit</A ></DT ><DT ->19.5. <A -HREF="speed.html#AEN3056" +>18.5. <A +HREF="speed.html#AEN2913" >Log level</A ></DT ><DT ->19.6. <A -HREF="speed.html#AEN3059" +>18.6. <A +HREF="speed.html#AEN2916" >Read raw</A ></DT ><DT ->19.7. <A -HREF="speed.html#AEN3064" +>18.7. <A +HREF="speed.html#AEN2921" >Write raw</A ></DT ><DT ->19.8. <A -HREF="speed.html#AEN3068" +>18.8. <A +HREF="speed.html#AEN2925" >Slow Clients</A ></DT ><DT ->19.9. <A -HREF="speed.html#AEN3072" +>18.9. <A +HREF="speed.html#AEN2929" >Slow Logins</A ></DT ><DT ->19.10. <A -HREF="speed.html#AEN3075" +>18.10. <A +HREF="speed.html#AEN2932" >Client tuning</A ></DT ></DL ></DD ><DT ->20. <A +>19. <A HREF="groupprofiles.html" ->Creating Group Profiles</A +>Creating Group Prolicy Files</A ></DT ><DD ><DL ><DT ->20.1. <A -HREF="groupprofiles.html#AEN3123" +>19.1. <A +HREF="groupprofiles.html#AEN2980" >Windows '9x</A ></DT ><DT ->20.2. <A -HREF="groupprofiles.html#AEN3132" +>19.2. <A +HREF="groupprofiles.html#AEN2990" >Windows NT 4</A ></DT ><DD ><DL ><DT ->20.2.1. <A -HREF="groupprofiles.html#AEN3155" +>19.2.1. <A +HREF="groupprofiles.html#AEN3013" >Side bar Notes</A ></DT ><DT ->20.2.2. <A -HREF="groupprofiles.html#AEN3159" +>19.2.2. <A +HREF="groupprofiles.html#AEN3017" >Mandatory profiles</A ></DT ><DT ->20.2.3. <A -HREF="groupprofiles.html#AEN3162" +>19.2.3. <A +HREF="groupprofiles.html#AEN3020" >moveuser.exe</A ></DT ><DT ->20.2.4. <A -HREF="groupprofiles.html#AEN3165" +>19.2.4. <A +HREF="groupprofiles.html#AEN3023" >Get SID</A ></DT ></DL ></DD ><DT ->20.3. <A -HREF="groupprofiles.html#AEN3170" +>19.3. <A +HREF="groupprofiles.html#AEN3028" >Windows 2000/XP</A ></DT ></DL ></DD +><DT +>20. <A +HREF="securing-samba.html" +>Securing Samba</A +></DT +><DD +><DL +><DT +>20.1. <A +HREF="securing-samba.html#AEN3109" +>Introduction</A +></DT +><DT +>20.2. <A +HREF="securing-samba.html#AEN3112" +>Using host based protection</A +></DT +><DT +>20.3. <A +HREF="securing-samba.html#AEN3119" +>Using interface protection</A +></DT +><DT +>20.4. <A +HREF="securing-samba.html#AEN3128" +>Using a firewall</A +></DT +><DT +>20.5. <A +HREF="securing-samba.html#AEN3135" +>Using a IPC$ share deny</A +></DT +><DT +>20.6. <A +HREF="securing-samba.html#AEN3144" +>Upgrading Samba</A +></DT +></DL +></DD ></DL ></DIV ></DIV diff --git a/docs/htmldocs/other-clients.html b/docs/htmldocs/other-clients.html index 7f0f99319e..4309b530ef 100644 --- a/docs/htmldocs/other-clients.html +++ b/docs/htmldocs/other-clients.html @@ -5,7 +5,7 @@ >Samba and other CIFS clients</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -16,8 +16,8 @@ REL="PREVIOUS" TITLE="Portability" HREF="portability.html"><LINK REL="NEXT" -TITLE="Reporting Bugs" -HREF="bugreport.html"></HEAD +TITLE="How to compile SAMBA" +HREF="compiling.html"></HEAD ><BODY CLASS="CHAPTER" BGCOLOR="#FFFFFF" @@ -59,7 +59,7 @@ WIDTH="10%" ALIGN="right" VALIGN="bottom" ><A -HREF="bugreport.html" +HREF="compiling.html" ACCESSKEY="N" >Next</A ></TD @@ -82,9 +82,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3311" -></A ->22.1. Macintosh clients?</H1 +NAME="AEN3221" +>22.1. Macintosh clients?</A +></H1 ><P >Yes. <A HREF="http://www.thursby.com/" @@ -128,18 +128,18 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3320" -></A ->22.2. OS2 Client</H1 +NAME="AEN3230" +>22.2. OS2 Client</A +></H1 ><DIV CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3322" -></A +NAME="AEN3232" >22.2.1. How can I configure OS/2 Warp Connect or - OS/2 Warp 4 as a client for Samba?</H2 + OS/2 Warp 4 as a client for Samba?</A +></H2 ><P >A more complete answer to this question can be found on <A @@ -195,10 +195,10 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3337" -></A +NAME="AEN3247" >22.2.2. How can I configure OS/2 Warp 3 (not Connect), - OS/2 1.2, 1.3 or 2.x for Samba?</H2 + OS/2 1.2, 1.3 or 2.x for Samba?</A +></H2 ><P >You can use the free Microsoft LAN Manager 2.2c Client for OS/2 from @@ -239,10 +239,10 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3346" -></A +NAME="AEN3256" >22.2.3. Are there any other issues when OS/2 (any version) - is used as a client?</H2 + is used as a client?</A +></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 +261,10 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3350" -></A +NAME="AEN3260" >22.2.4. How do I get printer driver download working - for OS/2 clients?</H2 + for OS/2 clients?</A +></H2 ><P >First, create a share called [PRINTDRV] that is world-readable. Copy your OS/2 driver files there. Note @@ -274,17 +274,13 @@ NAME="AEN3350" ><P >Install the NT driver first for that printer. Then, add to your smb.conf a parameter, os2 driver map = - <TT + <VAR CLASS="REPLACEABLE" -><I ->filename</I -></TT +>filename</VAR >". Then, in the file - specified by <TT + specified by <VAR CLASS="REPLACEABLE" -><I ->filename</I -></TT +>filename</VAR >, map the name of the NT driver name to the OS/2 driver name as follows:</P @@ -312,17 +308,17 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3360" -></A ->22.3. Windows for Workgroups</H1 +NAME="AEN3270" +>22.3. Windows for Workgroups</A +></H1 ><DIV CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3362" -></A ->22.3.1. Use latest TCP/IP stack from Microsoft</H2 +NAME="AEN3272" +>22.3.1. Use latest TCP/IP stack from Microsoft</A +></H2 ><P >Use the latest TCP/IP stack from microsoft if you use Windows for workgroups.</P @@ -342,9 +338,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3367" -></A ->22.3.2. Delete .pwl files after password change</H2 +NAME="AEN3277" +>22.3.2. Delete .pwl files after password change</A +></H2 ><P >WfWg does a lousy job with passwords. I find that if I change my password on either the unix box or the PC the safest thing to do is to @@ -362,9 +358,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3372" -></A ->22.3.3. Configure WfW password handling</H2 +NAME="AEN3282" +>22.3.3. Configure WfW password handling</A +></H2 ><P >There is a program call admincfg.exe on the last disk (disk 8) of the WFW 3.11 disk set. To install it @@ -381,9 +377,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3376" -></A ->22.3.4. Case handling of passwords</H2 +NAME="AEN3286" +>22.3.4. Case handling of passwords</A +></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" @@ -394,15 +390,30 @@ 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="AEN3291" +>22.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="AEN3381" -></A ->22.4. Windows '95/'98</H1 +NAME="AEN3294" +>22.4. Windows '95/'98</A +></H1 ><P >When using Windows 95 OEM SR2 the following updates are recommended where Samba is being used. Please NOTE that the above change will affect you once these @@ -448,9 +459,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3397" -></A ->22.5. Windows 2000 Service Pack 2</H1 +NAME="AEN3310" +>22.5. Windows 2000 Service Pack 2</A +></H1 ><P > There are several annoyances with Windows 2000 SP2. One of which @@ -560,7 +571,7 @@ WIDTH="33%" ALIGN="right" VALIGN="top" ><A -HREF="bugreport.html" +HREF="compiling.html" ACCESSKEY="N" >Next</A ></TD @@ -584,7 +595,7 @@ ACCESSKEY="U" WIDTH="33%" ALIGN="right" VALIGN="top" ->Reporting Bugs</TD +>How to compile SAMBA</TD ></TR ></TABLE ></DIV diff --git a/docs/htmldocs/p1346.html b/docs/htmldocs/p1346.html deleted file mode 100644 index e558561800..0000000000 --- a/docs/htmldocs/p1346.html +++ /dev/null @@ -1,917 +0,0 @@ -<!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 deleted file mode 100644 index a8f2a3c53c..0000000000 --- a/docs/htmldocs/p18.html +++ /dev/null @@ -1,438 +0,0 @@ -<!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 deleted file mode 100644 index 9967d8fb59..0000000000 --- a/docs/htmldocs/p3106.html +++ /dev/null @@ -1,391 +0,0 @@ -<!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 deleted file mode 100644 index 502d978b5f..0000000000 --- a/docs/htmldocs/p544.html +++ /dev/null @@ -1,388 +0,0 @@ -<!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 a64de2a1b4..d110c385f1 100644 --- a/docs/htmldocs/pam.html +++ b/docs/htmldocs/pam.html @@ -6,7 +6,7 @@ managed authentication</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -82,9 +82,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1922" -></A ->11.1. Samba and PAM</H1 +NAME="AEN1825" +>11.1. Samba and PAM</A +></H1 ><P >A number of Unix systems (eg: Sun Solaris), as well as the xxxxBSD family and Linux, now utilize the Pluggable Authentication @@ -296,9 +296,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1966" -></A ->11.2. Distributed Authentication</H1 +NAME="AEN1869" +>11.2. Distributed Authentication</A +></H1 ><P >The astute administrator will realize from this that the combination of <TT @@ -329,9 +329,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1973" -></A ->11.3. PAM Configuration in smb.conf</H1 +NAME="AEN1876" +>11.3. PAM Configuration in smb.conf</A +></H1 ><P >There is an option in smb.conf called <A HREF="smb.conf.5.html#OBEYPAMRESTRICTIONS" @@ -341,9 +341,9 @@ TARGET="_top" The following is from the on-line help for this option in SWAT;</P ><P >When Samba 2.2 is configure to enable PAM support (i.e. -<TT +<CODE CLASS="CONSTANT" ->--with-pam</TT +>--with-pam</CODE >), this parameter will control whether or not Samba should obey PAM's account and session management directives. The default behavior diff --git a/docs/htmldocs/passdb.html b/docs/htmldocs/passdb.html index f53641624a..7a8fb7fdec 100644 --- a/docs/htmldocs/passdb.html +++ b/docs/htmldocs/passdb.html @@ -5,7 +5,7 @@ >User information database</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -80,9 +80,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN324" -></A ->3.1. Introduction</H1 +NAME="AEN227" +>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 @@ -121,9 +121,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN331" -></A ->3.2. Important Notes About Security</H1 +NAME="AEN234" +>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 @@ -229,9 +229,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN346" -></A ->3.2.1. Advantages of SMB Encryption</H2 +NAME="AEN249" +>3.2.1. Advantages of SMB Encryption</A +></H2 ><P ></P ><TABLE @@ -263,9 +263,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN351" -></A ->3.2.2. Advantages of non-encrypted passwords</H2 +NAME="AEN254" +>3.2.2. Advantages of non-encrypted passwords</A +></H2 ><P ></P ><TABLE @@ -299,9 +299,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN357" -></A ->3.3. The smbpasswd Command</H1 +NAME="AEN260" +>3.3. The smbpasswd Command</A +></H1 ><P >The smbpasswd utility is a utility similar to the <B @@ -331,47 +331,39 @@ CLASS="COMMAND" ><P >To run smbpasswd as a normal user just type :</P ><P -><TT +><SAMP CLASS="PROMPT" ->$ </TT -><TT +>$ </SAMP +><KBD CLASS="USERINPUT" -><B ->smbpasswd</B -></TT +>smbpasswd</KBD ></P ><P -><TT +><SAMP CLASS="PROMPT" ->Old SMB password: </TT -><TT +>Old SMB password: </SAMP +><KBD CLASS="USERINPUT" -><B -><type old value here - - or hit return if there was no old password></B -></TT +><type old value here - + or hit return if there was no old password></KBD ></P ><P -><TT +><SAMP CLASS="PROMPT" ->New SMB Password: </TT -><TT +>New SMB Password: </SAMP +><KBD CLASS="USERINPUT" -><B -><type new value> - </B -></TT +><type new value> + </KBD ></P ><P -><TT +><SAMP CLASS="PROMPT" ->Repeat New SMB Password: </TT -><TT +>Repeat New SMB Password: </SAMP +><KBD CLASS="USERINPUT" -><B -><re-type new value - </B -></TT +><re-type new value + </KBD ></P ><P >If the old value does not match the current value stored for @@ -411,9 +403,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN388" -></A ->3.4. Plain text</H1 +NAME="AEN291" +>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 @@ -431,9 +423,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN393" -></A ->3.5. TDB</H1 +NAME="AEN296" +>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 @@ -444,17 +436,17 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN396" -></A ->3.6. LDAP</H1 +NAME="AEN299" +>3.6. LDAP</A +></H1 ><DIV CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN398" -></A ->3.6.1. Introduction</H2 +NAME="AEN301" +>3.6.1. Introduction</A +></H2 ><P >This document describes how to use an LDAP directory for storing Samba user account information traditionally stored in the smbpasswd(5) file. It is @@ -520,9 +512,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN418" -></A ->3.6.2. Introduction</H2 +NAME="AEN321" +>3.6.2. Introduction</A +></H2 ><P >Traditionally, when configuring <A HREF="smb.conf.5.html#ENCRYPTPASSWORDS" @@ -577,35 +569,27 @@ 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. <TT +for a samdb backend (e.g. <VAR CLASS="PARAMETER" -><I ->--with-ldapsam</I -></TT +>--with-ldapsam</VAR > or -<TT +<VAR CLASS="PARAMETER" -><I ->--with-tdbsam</I -></TT +>--with-tdbsam</VAR >) requires compile time support.</P ><P ->When compiling Samba to include the <TT +>When compiling Samba to include the <VAR CLASS="PARAMETER" -><I ->--with-ldapsam</I -></TT +>--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 <TT +>There are a few points to stress about what the <VAR CLASS="PARAMETER" -><I ->--with-ldapsam</I -></TT +>--with-ldapsam</VAR > does not provide. The LDAP support referred to in the this documentation does not include:</P @@ -637,9 +621,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN447" -></A ->3.6.3. Supported LDAP Servers</H2 +NAME="AEN350" +>3.6.3. Supported LDAP Servers</A +></H2 ><P >The LDAP samdb code in 2.2.3 has been developed and tested using the OpenLDAP 2.0 server and client libraries. The same code should be able to work with @@ -662,9 +646,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN452" -></A ->3.6.4. Schema and Relationship to the RFC 2307 posixAccount</H2 +NAME="AEN355" +>3.6.4. Schema and Relationship to the RFC 2307 posixAccount</A +></H2 ><P >Samba 3.0 includes the necessary schema file for OpenLDAP 2.0 in <TT @@ -698,9 +682,9 @@ CLASS="FILENAME" >/etc/passwd</TT > entry, so is the sambaAccount object meant to supplement the UNIX user account information. A sambaAccount is a -<TT +<CODE CLASS="CONSTANT" ->STRUCTURAL</TT +>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 @@ -719,24 +703,24 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN464" -></A ->3.6.5. Configuring Samba with LDAP</H2 +NAME="AEN367" +>3.6.5. Configuring Samba with LDAP</A +></H2 ><DIV CLASS="SECT3" ><H3 CLASS="SECT3" ><A -NAME="AEN466" -></A ->3.6.5.1. OpenLDAP configuration</H3 +NAME="AEN369" +>3.6.5.1. OpenLDAP configuration</A +></H3 ><P >To include support for the sambaAccount object in an OpenLDAP directory server, first copy the samba.schema file to slapd's configuration directory.</P ><P -><TT +><SAMP CLASS="PROMPT" ->root# </TT +>root# </SAMP ><B CLASS="COMMAND" >cp samba.schema /etc/openldap/schema/</B @@ -809,15 +793,13 @@ CLASS="SECT3" ><H3 CLASS="SECT3" ><A -NAME="AEN483" -></A ->3.6.5.2. Configuring Samba</H3 +NAME="AEN386" +>3.6.5.2. Configuring Samba</A +></H3 ><P ->The following parameters are available in smb.conf only with <TT +>The following parameters are available in smb.conf only with <VAR CLASS="PARAMETER" -><I ->--with-ldapsam</I -></TT +>--with-ldapsam</VAR > was included with compiling Samba.</P ><P @@ -895,11 +877,9 @@ 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 <TT + # must be set by using 'smbpasswd -w <VAR CLASS="REPLACEABLE" -><I ->secretpw</I -></TT +>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. @@ -920,7 +900,7 @@ 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 @@ -929,9 +909,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN511" -></A ->3.6.6. Accounts and Groups management</H2 +NAME="AEN414" +>3.6.6. Accounts and Groups management</A +></H2 ><P >As users accounts are managed thru the sambaAccount objectclass, you should modify you existing administration tools to deal with sambaAccount attributes.</P @@ -954,9 +934,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN516" -></A ->3.6.7. Security and sambaAccount</H2 +NAME="AEN419" +>3.6.7. Security and sambaAccount</A +></H2 ><P >There are two important points to remember when discussing the security of sambaAccount entries in the directory.</P @@ -1033,9 +1013,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN536" -></A ->3.6.8. LDAP specials attributes for sambaAccounts</H2 +NAME="AEN439" +>3.6.8. LDAP specials attributes for sambaAccounts</A +></H2 ><P >The sambaAccount objectclass is composed of the following attributes:</P ><P @@ -1043,84 +1023,84 @@ NAME="AEN536" ><UL ><LI ><P -><TT +><CODE CLASS="CONSTANT" ->lmPassword</TT +>lmPassword</CODE >: the LANMAN password 16-byte hash stored as a character representation of a hexidecimal string.</P ></LI ><LI ><P -><TT +><CODE CLASS="CONSTANT" ->ntPassword</TT +>ntPassword</CODE >: the NT password hash 16-byte stored as a character representation of a hexidecimal string.</P ></LI ><LI ><P -><TT +><CODE CLASS="CONSTANT" ->pwdLastSet</TT +>pwdLastSet</CODE >: The integer time in seconds since 1970 when the - <TT + <CODE CLASS="CONSTANT" ->lmPassword</TT -> and <TT +>lmPassword</CODE +> and <CODE CLASS="CONSTANT" ->ntPassword</TT +>ntPassword</CODE > attributes were last set. </P ></LI ><LI ><P -><TT +><CODE CLASS="CONSTANT" ->acctFlags</TT +>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 -><TT +><CODE CLASS="CONSTANT" ->logonTime</TT +>logonTime</CODE >: Integer value currently unused</P ></LI ><LI ><P -><TT +><CODE CLASS="CONSTANT" ->logoffTime</TT +>logoffTime</CODE >: Integer value currently unused</P ></LI ><LI ><P -><TT +><CODE CLASS="CONSTANT" ->kickoffTime</TT +>kickoffTime</CODE >: Integer value currently unused</P ></LI ><LI ><P -><TT +><CODE CLASS="CONSTANT" ->pwdCanChange</TT +>pwdCanChange</CODE >: Integer value currently unused</P ></LI ><LI ><P -><TT +><CODE CLASS="CONSTANT" ->pwdMustChange</TT +>pwdMustChange</CODE >: Integer value currently unused</P ></LI ><LI ><P -><TT +><CODE CLASS="CONSTANT" ->homeDrive</TT +>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 @@ -1128,9 +1108,9 @@ CLASS="CONSTANT" ></LI ><LI ><P -><TT +><CODE CLASS="CONSTANT" ->scriptPath</TT +>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 @@ -1138,18 +1118,18 @@ CLASS="CONSTANT" ></LI ><LI ><P -><TT +><CODE CLASS="CONSTANT" ->profilePath</TT +>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 -><TT +><CODE CLASS="CONSTANT" ->smbHome</TT +>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 @@ -1159,25 +1139,25 @@ CLASS="CONSTANT" ></LI ><LI ><P -><TT +><CODE CLASS="CONSTANT" ->userWorkstation</TT +>userWorkstation</CODE >: character string value currently unused. </P ></LI ><LI ><P -><TT +><CODE CLASS="CONSTANT" ->rid</TT +>rid</CODE >: the integer representation of the user's relative identifier (RID).</P ></LI ><LI ><P -><TT +><CODE CLASS="CONSTANT" ->primaryGroupID</TT +>primaryGroupID</CODE >: the relative identifier (RID) of the primary group of the user.</P ></LI @@ -1222,19 +1202,15 @@ its <TT CLASS="FILENAME" >smb.conf</TT > file. When a user named "becky" logons to the domain, -the <TT +the <VAR CLASS="PARAMETER" -><I ->logon home</I -></TT +>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 <TT +of the <VAR CLASS="PARAMETER" -><I ->logon home</I -></TT +>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 @@ -1244,9 +1220,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN606" -></A ->3.6.9. Example LDIF Entries for a sambaAccount</H2 +NAME="AEN509" +>3.6.9. Example LDIF Entries for a sambaAccount</A +></H2 ><P >The following is a working LDIF with the inclusion of the posixAccount objectclass:</P ><P @@ -1303,17 +1279,17 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN614" -></A ->3.7. MySQL</H1 +NAME="AEN517" +>3.7. MySQL</A +></H1 ><DIV CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN616" -></A ->3.7.1. Building</H2 +NAME="AEN519" +>3.7.1. Building</A +></H2 ><P >To build the plugin, run <B CLASS="COMMAND" @@ -1332,9 +1308,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN622" -></A ->3.7.2. Creating the database</H2 +NAME="AEN525" +>3.7.2. 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 @@ -1345,26 +1321,18 @@ contains the correct queries to create the required tables. Use the command : <B CLASS="COMMAND" ->mysql -u<TT +>mysql -u<VAR CLASS="REPLACEABLE" -><I ->username</I -></TT -> -h<TT +>username</VAR +> -h<VAR CLASS="REPLACEABLE" -><I ->hostname</I -></TT -> -p<TT +>hostname</VAR +> -p<VAR CLASS="REPLACEABLE" -><I ->password</I -></TT -> <TT +>password</VAR +> <VAR CLASS="REPLACEABLE" -><I ->databasename</I -></TT +>databasename</VAR > < <TT CLASS="FILENAME" >/path/to/samba/examples/pdb/mysql/mysql.dump</TT @@ -1376,9 +1344,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN632" -></A ->3.7.3. Configuring</H2 +NAME="AEN535" +>3.7.3. Configuring</A +></H2 ><P >This plugin lacks some good documentation, but here is some short info:</P ><P @@ -1487,9 +1455,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN649" -></A ->3.7.4. Using plaintext passwords or encrypted password</H2 +NAME="AEN552" +>3.7.4. Using plaintext passwords or encrypted password</A +></H2 ><P >I strongly discourage the use of plaintext passwords, however, you can use them:</P ><P @@ -1502,9 +1470,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN654" -></A ->3.7.5. Getting non-column data from the table</H2 +NAME="AEN557" +>3.7.5. 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 @@ -1528,17 +1496,17 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN662" -></A ->3.8. Passdb XML plugin</H1 +NAME="AEN565" +>3.8. Passdb XML plugin</A +></H1 ><DIV CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN664" -></A ->3.8.1. Building</H2 +NAME="AEN567" +>3.8.1. Building</A +></H2 ><P >This module requires libxml2 to be installed.</P ><P @@ -1556,9 +1524,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN670" -></A ->3.8.2. Usage</H2 +NAME="AEN573" +>3.8.2. Usage</A +></H2 ><P >The usage of pdb_xml is pretty straightforward. To export data, use: diff --git a/docs/htmldocs/pdb-mysql.html b/docs/htmldocs/pdb-mysql.html deleted file mode 100644 index e98d0c30d0..0000000000 --- a/docs/htmldocs/pdb-mysql.html +++ /dev/null @@ -1,341 +0,0 @@ -<!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.77+"><LINK -REL="HOME" -TITLE="SAMBA Project Documentation" -HREF="samba-howto-collection.html"><LINK -REL="UP" -TITLE="Optional configuration" -HREF="optional.html"><LINK -REL="PREVIOUS" -TITLE="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" -></A ->Chapter 16. Passdb MySQL plugin</H1 -><DIV -CLASS="SECT1" -><H1 -CLASS="SECT1" -><A -NAME="AEN2562" -></A ->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="AEN2568" -></A ->16.2. Creating the database</H1 -><P ->You either can set up your own table and specify the field names to pdb_mysql (see below -for the column names) or use the default table. The file <TT -CLASS="FILENAME" ->examples/pdb/mysql/mysql.dump</TT -> -contains the correct queries to create the required tables. Use the command : - -<B -CLASS="COMMAND" ->mysql -u<TT -CLASS="REPLACEABLE" -><I ->username</I -></TT -> -h<TT -CLASS="REPLACEABLE" -><I ->hostname</I -></TT -> -p<TT -CLASS="REPLACEABLE" -><I ->password</I -></TT -> <TT -CLASS="REPLACEABLE" -><I ->databasename</I -></TT -> < <TT -CLASS="FILENAME" ->/path/to/samba/examples/pdb/mysql/mysql.dump</TT -></B -> </P -></DIV -><DIV -CLASS="SECT1" -><H1 -CLASS="SECT1" -><A -NAME="AEN2578" -></A ->16.3. Configuring</H1 -><P ->This plugin lacks some good documentation, but here is some short info:</P -><P ->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="AEN2595" -></A ->16.4. Using plaintext passwords or encrypted password</H1 -><P ->I strongly discourage the use of plaintext passwords, however, you can use them:</P -><P ->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="AEN2600" -></A ->16.5. Getting non-column data from the table</H1 -><P ->It is possible to have not all data in the database and making some 'constant'.</P -><P ->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 deleted file mode 100644 index 1b419dcc74..0000000000 --- a/docs/htmldocs/pdb-xml.html +++ /dev/null @@ -1,189 +0,0 @@ -<!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.77+"><LINK -REL="HOME" -TITLE="SAMBA Project Documentation" -HREF="samba-howto-collection.html"><LINK -REL="UP" -TITLE="Optional configuration" -HREF="optional.html"><LINK -REL="PREVIOUS" -TITLE="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" -></A ->Chapter 17. Passdb XML plugin</H1 -><DIV -CLASS="SECT1" -><H1 -CLASS="SECT1" -><A -NAME="AEN2619" -></A ->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="AEN2625" -></A ->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 14497f522c..ee7b980211 100644 --- a/docs/htmldocs/pdbedit.8.html +++ b/docs/htmldocs/pdbedit.8.html @@ -5,7 +5,7 @@ >pdbedit</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"></HEAD +CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD ><BODY CLASS="REFENTRY" BGCOLOR="#FFFFFF" @@ -277,11 +277,9 @@ retype new password</PRE ><DD ><P >This option may only be used in conjunction - with the <TT + with the <VAR CLASS="PARAMETER" -><I ->-a</I -></TT +>-a</VAR > option. It will make pdbedit to add a machine trust account instead of a user account (-u username will provide the machine name).</P @@ -374,11 +372,9 @@ CLASS="PROGRAMLISTING" ><P >Sets an account policy to a specified value. This option may only be used in conjunction - with the <TT + with the <VAR CLASS="PARAMETER" -><I ->-P</I -></TT +>-P</VAR > option. </P ><P @@ -397,11 +393,9 @@ account policy value for bad lockout attempt is now 3</PRE >-d|--debug=debuglevel</DT ><DD ><P -><TT +><VAR CLASS="REPLACEABLE" -><I ->debuglevel</I -></TT +>debuglevel</VAR > is an integer from 0 to 10. The default value if this parameter is not specified is zero.</P @@ -441,7 +435,7 @@ CLASS="FILENAME" >Print a summary of command line options.</P ></DD ><DT ->-s <configuration file></DT +>-s <configuration file></DT ><DD ><P >The file specified contains the diff --git a/docs/htmldocs/portability.html b/docs/htmldocs/portability.html index 4942cdb1bb..b6d406ce1d 100644 --- a/docs/htmldocs/portability.html +++ b/docs/htmldocs/portability.html @@ -5,7 +5,7 @@ >Portability</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -84,9 +84,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3251" -></A ->21.1. HPUX</H1 +NAME="AEN3156" +>21.1. HPUX</A +></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 +114,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3257" -></A ->21.2. SCO Unix</H1 +NAME="AEN3162" +>21.2. SCO Unix</A +></H1 ><P > If you run an old version of SCO Unix then you may need to get important @@ -131,9 +131,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3261" -></A ->21.3. DNIX</H1 +NAME="AEN3166" +>21.3. DNIX</A +></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 +238,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3290" -></A ->21.4. RedHat Linux Rembrandt-II</H1 +NAME="AEN3195" +>21.4. RedHat Linux Rembrandt-II</A +></H1 ><P >By default RedHat Rembrandt-II during installation adds an entry to /etc/hosts as follows: @@ -257,6 +257,27 @@ 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="AEN3201" +>21.5. AIX</A +></H1 +><DIV +CLASS="SECT2" +><H2 +CLASS="SECT2" +><A +NAME="AEN3203" +>21.5.1. Sequential Read Ahead</A +></H2 +><P +>Disabling Sequential Read Ahead using "vmtune -r 0" improves +samba performance significally.</P +></DIV +></DIV ></DIV ><DIV CLASS="NAVFOOTER" diff --git a/docs/htmldocs/printing.html b/docs/htmldocs/printing.html index 92eb52c7cc..91a1ad72b0 100644 --- a/docs/htmldocs/printing.html +++ b/docs/htmldocs/printing.html @@ -5,7 +5,7 @@ >Printing Support</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -80,9 +80,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2054" -></A ->13.1. Introduction</H1 +NAME="AEN1957" +>13.1. Introduction</A +></H1 ><P >Beginning with the 2.2.0 release, Samba supports the native Windows NT printing mechanisms implemented via @@ -163,9 +163,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2076" -></A ->13.2. Configuration</H1 +NAME="AEN1979" +>13.2. Configuration</A +></H1 ><DIV CLASS="WARNING" ><P @@ -204,19 +204,15 @@ a printer$ service which provides read-only access via no password in order to support printer driver downloads.</P ><P >However, the initial implementation allowed for a -parameter named <TT +parameter named <VAR CLASS="PARAMETER" -><I ->printer driver location</I -></TT +>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 <TT +parameter named <VAR CLASS="PARAMETER" -><I ->printer driver</I -></TT +>printer driver</VAR > provided a means of defining the printer driver name to be sent to the client.</P @@ -229,9 +225,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2084" -></A ->13.2.1. Creating [print$]</H2 +NAME="AEN1987" +>13.2.1. Creating [print$]</A +></H2 ><P >In order to support the uploading of printer driver files, you must first configure a file share named [print$]. @@ -270,11 +266,9 @@ CLASS="PROGRAMLISTING" >The <A HREF="smb.conf.5.html#WRITELIST" TARGET="_top" -><TT +><VAR CLASS="PARAMETER" -><I ->write list</I -></TT +>write list</VAR ></A > is used to allow administrative level user accounts to have write access in order to update files @@ -414,12 +408,10 @@ one of two conditions must hold true:</P must be a member of the <A HREF="smb.conf.5.html#PRINTERADMIN" TARGET="_top" -><TT +><VAR CLASS="PARAMETER" -><I >printer - admin</I -></TT + admin</VAR ></A > list.</P ></LI @@ -435,11 +427,9 @@ 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 <TT +a root (or <VAR CLASS="PARAMETER" -><I ->printer admin</I -></TT +>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 @@ -452,9 +442,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2119" -></A ->13.2.2. Setting Drivers for Existing Printers</H2 +NAME="AEN2022" +>13.2.2. Setting Drivers for Existing Printers</A +></H2 ><P >The initial listing of printers in the Samba host's Printers folder will have no real printer driver assigned @@ -524,9 +514,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2135" -></A ->13.2.3. Support a large number of printers</H2 +NAME="AEN2038" +>13.2.3. Support a large number of printers</A +></H2 ><P >One issue that has arisen during the development phase of Samba 2.2 is the need to support driver downloads for @@ -547,9 +537,9 @@ of how this could be accomplished:</P ><PRE CLASS="PROGRAMLISTING" > -<TT +<SAMP CLASS="PROMPT" ->$ </TT +>$ </SAMP >rpcclient pogo -U root%secret -c "enumdrivers" Domain=[NARNIA] OS=[Unix] Server=[Samba 2.2.0-alpha3] @@ -563,9 +553,9 @@ Printer Driver Info 1: Printer Driver Info 1: Driver Name: [HP LaserJet 4Si/4SiMX PS] -<TT +<SAMP CLASS="PROMPT" ->$ </TT +>$ </SAMP >rpcclient pogo -U root%secret -c "enumprinters" Domain=[NARNIA] OS=[Unix] Server=[Samba 2.2.0-alpha3] flags:[0x800000] @@ -573,13 +563,13 @@ Domain=[NARNIA] OS=[Unix] Server=[Samba 2.2.0-alpha3] description:[POGO\\POGO\hp-print,NO DRIVER AVAILABLE FOR THIS PRINTER,] comment:[] -<TT +<SAMP CLASS="PROMPT" ->$ </TT +>$ </SAMP >rpcclient pogo -U root%secret \ -<TT +<SAMP CLASS="PROMPT" ->> </TT +>> </SAMP > -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 @@ -590,9 +580,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2146" -></A ->13.2.4. Adding New Printers via the Windows NT APW</H2 +NAME="AEN2049" +>13.2.4. Adding New Printers via the Windows NT APW</A +></H2 ><P >By default, Samba offers all printer shares defined in <TT CLASS="FILENAME" @@ -607,11 +597,9 @@ 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 <TT + privileges (i.e. root or <VAR CLASS="PARAMETER" -><I ->printer admin</I -></TT +>printer admin</VAR >). </P ></LI @@ -620,12 +608,10 @@ CLASS="PARAMETER" ><A HREF="smb.conf.5.html#SHOWADDPRINTERWIZARD" TARGET="_top" -><TT +><VAR CLASS="PARAMETER" -><I >show - add printer wizard = yes</I -></TT + add printer wizard = yes</VAR ></A > (the default). </P @@ -636,12 +622,10 @@ CLASS="PARAMETER" server, the <A HREF="smb.conf.5.html#ADDPRINTERCOMMAND" TARGET="_top" -><TT +><VAR CLASS="PARAMETER" -><I >add -printer command</I -></TT +printer command</VAR ></A > must have a defined value. The program hook must successfully add the printer to the system (i.e. @@ -658,35 +642,29 @@ CLASS="FILENAME" not exist, <B CLASS="COMMAND" >smbd</B -> will execute the <TT +> will execute the <VAR CLASS="PARAMETER" -><I >add printer -command</I -></TT +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 -<TT +<VAR CLASS="PARAMETER" -><I ->add printer program</I -></TT +>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" -><TT +><VAR CLASS="PARAMETER" -><I >delete -printer command</I -></TT +printer command</VAR ></A > for removing entries from the "Printers..." folder.</P @@ -694,11 +672,9 @@ folder.</P >The following is an example <A HREF="smb.conf.5.html#ADDPRINTERCOMMAN" TARGET="_top" -><TT +><VAR CLASS="PARAMETER" -><I ->add printer command</I -></TT +>add printer command</VAR ></A > script. It adds the appropriate entries to <TT CLASS="FILENAME" @@ -733,8 +709,8 @@ echo " :sd=/var/spool/lpd/$2:\\" >> $PRINTCAP echo " :mx=0:ml=0:sh:\\" >> $PRINTCAP echo " :lp=/usr/local/samba/var/print/$5.prn:" >> $PRINTCAP -touch "/usr/local/samba/var/print/$5.prn" >> /tmp/printadd.$$ 2>&1 -chown $LP "/usr/local/samba/var/print/$5.prn" >> /tmp/printadd.$$ 2>&1 +touch "/usr/local/samba/var/print/$5.prn" >> /tmp/printadd.$$ 2>&1 +chown $LP "/usr/local/samba/var/print/$5.prn" >> /tmp/printadd.$$ 2>&1 mkdir /var/spool/lpd/$2 chmod 700 /var/spool/lpd/$2 @@ -759,9 +735,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2176" -></A ->13.2.5. Samba and Printer Ports</H2 +NAME="AEN2079" +>13.2.5. Samba and Printer Ports</A +></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 @@ -780,12 +756,10 @@ CLASS="FILENAME" > possesses a <A HREF="smb.conf.5.html#ENUMPORTSCOMMAND" TARGET="_top" -><TT +><VAR CLASS="PARAMETER" -><I >enumports -command</I -></TT +command</VAR ></A > which can be used to define an external program that generates a listing of ports on a system.</P @@ -796,9 +770,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2184" -></A ->13.3. The Imprints Toolset</H1 +NAME="AEN2087" +>13.3. The Imprints Toolset</A +></H1 ><P >The Imprints tool set provides a UNIX equivalent of the Windows NT Add Printer Wizard. For complete information, please @@ -814,9 +788,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2188" -></A ->13.3.1. What is Imprints?</H2 +NAME="AEN2091" +>13.3.1. What is Imprints?</A +></H2 ><P >Imprints is a collection of tools for supporting the goals of</P @@ -846,9 +820,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2198" -></A ->13.3.2. Creating Printer Driver Packages</H2 +NAME="AEN2101" +>13.3.2. Creating Printer Driver Packages</A +></H2 ><P >The process of creating printer driver packages is beyond the scope of this document (refer to Imprints.txt also included @@ -862,9 +836,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2201" -></A ->13.3.3. The Imprints server</H2 +NAME="AEN2104" +>13.3.3. The Imprints server</A +></H2 ><P >The Imprints server is really a database server that may be queried via standard HTTP mechanisms. Each printer @@ -886,9 +860,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2205" -></A ->13.3.4. The Installation Client</H2 +NAME="AEN2108" +>13.3.4. The Installation Client</A +></H2 ><P >More information regarding the Imprints installation client is available in the <TT @@ -980,17 +954,17 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2227" -></A ->13.4. Diagnosis</H1 +NAME="AEN2130" +>13.4. Diagnosis</A +></H1 ><DIV CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2229" -></A ->13.4.1. Introduction</H2 +NAME="AEN2132" +>13.4.1. Introduction</A +></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 @@ -1052,7 +1026,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 @@ -1063,9 +1037,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2245" -></A ->13.4.2. Debugging printer problems</H2 +NAME="AEN2148" +>13.4.2. Debugging printer problems</A +></H2 ><P >One way to debug printing problems is to start by replacing these command with shell scripts that record the arguments and the contents @@ -1081,7 +1055,7 @@ CLASS="PROGRAMLISTING" /usr/bin/id -p >/tmp/tmp.print # we run the command and save the error messages # replace the command with the one appropriate for your system - /usr/bin/lpr -r -P$1 $2 2>>&/tmp/tmp.print</PRE + /usr/bin/lpr -r -P$1 $2 2>>&/tmp/tmp.print</PRE ></P ><P >Then you print a file and try removing it. You may find that the @@ -1120,9 +1094,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2254" -></A ->13.4.3. What printers do I have?</H2 +NAME="AEN2157" +>13.4.3. What printers do I have?</A +></H2 ><P >You can use the 'testprns' program to check to see if the printer name you are using is recognized by Samba. For example, you can @@ -1149,9 +1123,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2262" -></A ->13.4.4. Setting up printcap and print servers</H2 +NAME="AEN2165" +>13.4.4. Setting up printcap and print servers</A +></H2 ><P >You may need to set up some printcaps for your Samba system to use. It is strongly recommended that you use the facilities provided by @@ -1233,9 +1207,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2290" -></A ->13.4.5. Job sent, no output</H2 +NAME="AEN2193" +>13.4.5. Job sent, no output</A +></H2 ><P >This is the most frustrating part of printing. You may have sent the job, verified that the job was forwarded, set up a wrapper around @@ -1278,9 +1252,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2301" -></A ->13.4.6. Job sent, strange output</H2 +NAME="AEN2204" +>13.4.6. Job sent, strange output</A +></H2 ><P >Once you have the job printing, you can then start worrying about making it print nicely.</P @@ -1324,9 +1298,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2313" -></A ->13.4.7. Raw PostScript printed</H2 +NAME="AEN2216" +>13.4.7. Raw PostScript printed</A +></H2 ><P >This is a problem that is usually caused by either the print spooling system putting information at the start of the print job that makes @@ -1339,9 +1313,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2316" -></A ->13.4.8. Advanced Printing</H2 +NAME="AEN2219" +>13.4.8. Advanced Printing</A +></H2 ><P >Note that you can do some pretty magic things by using your imagination with the "print command" option and some shell scripts. @@ -1355,9 +1329,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2319" -></A ->13.4.9. Real debugging</H2 +NAME="AEN2222" +>13.4.9. Real debugging</A +></H2 ><P >If the above debug tips don't help, then maybe you need to bring in the bug guns, system tracing. See Tracing.txt in this directory.</P diff --git a/docs/htmldocs/pwencrypt.html b/docs/htmldocs/pwencrypt.html deleted file mode 100644 index b15d74c5d0..0000000000 --- a/docs/htmldocs/pwencrypt.html +++ /dev/null @@ -1,445 +0,0 @@ -<!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.77+"><LINK -REL="HOME" -TITLE="SAMBA Project Documentation" -HREF="samba-howto-collection.html"><LINK -REL="UP" -TITLE="General installation" -HREF="introduction.html"><LINK -REL="PREVIOUS" -TITLE="Quick Cross Subnet Browsing / Cross Workgroup Browsing guide" -HREF="browsing-quick.html"><LINK -REL="NEXT" -TITLE="User information database" -HREF="passdb.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="passdb.html" -ACCESSKEY="N" ->Next</A -></TD -></TR -></TABLE -><HR -ALIGN="LEFT" -WIDTH="100%"></DIV -><DIV -CLASS="CHAPTER" -><H1 -><A -NAME="PWENCRYPT" -></A ->Chapter 4. LanMan and NT Password Encryption in Samba</H1 -><DIV -CLASS="SECT1" -><H1 -CLASS="SECT1" -><A -NAME="AEN457" -></A ->4.1. Introduction</H1 -><P ->Newer windows clients send encrypted passwords over - the wire, instead of plain text passwords. The newest clients - 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" -></A ->4.2. Important Notes About Security</H1 -><P ->The unix and SMB password encryption techniques seem similar - on the surface. This similarity is, however, only skin deep. The unix - 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="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/warning.gif" -HSPACE="5" -ALT="Warning"></TD -><TD -ALIGN="LEFT" -VALIGN="TOP" -><P ->Note that Windows NT 4.0 Service pack 3 changed the - default for permissible authentication so that plaintext - passwords are <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->never</I -></SPAN -> sent over the wire. - The solution to this is either to switch to encrypted passwords - with Samba or edit the Windows NT registry to re-enable plaintext - passwords. See the document WinNT.txt for details on how to do - this.</P -><P ->Other Microsoft operating systems which also exhibit - this behavior includes</P -><P -></P -><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" -></A ->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" -></A ->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" -></A ->4.3. The smbpasswd Command</H1 -><P ->The smbpasswd command maintains the two 32 byte password fields - in the smbpasswd file. If you wish to make it similar to the unix - <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="passdb.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" ->User information database</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 611512a53b..6e71ddeb14 100644 --- a/docs/htmldocs/rpcclient.1.html +++ b/docs/htmldocs/rpcclient.1.html @@ -5,7 +5,7 @@ >rpcclient</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"></HEAD +CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD ><BODY CLASS="REFENTRY" BGCOLOR="#FFFFFF" @@ -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" @@ -86,11 +86,9 @@ CLASS="VARIABLELIST" resolved using the <A HREF="smb.conf.5.html#NAMERESOLVEORDER" TARGET="_top" -> <TT +> <VAR CLASS="PARAMETER" -><I ->name resolve order</I -></TT +>name resolve order</VAR ></A > line from <SPAN CLASS="CITEREFENTRY" @@ -111,9 +109,9 @@ CLASS="REFENTRYTITLE" ><P ><PRE CLASS="PROGRAMLISTING" ->username = <value> -password = <value> -domain = <value></PRE +>username = <value> +password = <value> +domain = <value></PRE ></P ><P >Make certain that the permissions on the file restrict @@ -136,11 +134,9 @@ domain = <value></PRE >-d|--debug=debuglevel</DT ><DD ><P -><TT +><VAR CLASS="REPLACEABLE" -><I ->debuglevel</I -></TT +>debuglevel</VAR > is an integer from 0 to 10. The default value if this parameter is not specified is zero.</P @@ -177,21 +173,17 @@ CLASS="FILENAME" >-I IP-address</DT ><DD ><P -><TT +><VAR CLASS="REPLACEABLE" -><I ->IP address</I -></TT +>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 <TT + mechanism described above in the <VAR CLASS="PARAMETER" -><I ->name resolve order</I -></TT +>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 @@ -207,9 +199,9 @@ CLASS="PARAMETER" ><DD ><P >File name for log/debug files. The extension - <TT + <CODE CLASS="CONSTANT" ->'.client'</TT +>'.client'</CODE > will be appended. The log file is never removed by the client. </P @@ -226,11 +218,9 @@ CLASS="COMMAND" CLASS="COMMAND" >rpcclient</B > will - prompt for a password. See also the <TT + prompt for a password. See also the <VAR CLASS="PARAMETER" -><I ->-U</I -></TT +>-U</VAR > option.</P ></DD @@ -251,18 +241,18 @@ CLASS="FILENAME" >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 <TT + client will first check the <VAR CLASS="ENVAR" ->USER</TT +>USER</VAR > environment variable, then the - <TT + <VAR CLASS="ENVAR" ->LOGNAME</TT +>LOGNAME</VAR > variable and if either exists, the string is uppercased. If these environmental variables are not - found, the username <TT + found, the username <CODE CLASS="CONSTANT" ->GUEST</TT +>GUEST</CODE > is used. </P ><P >A third option is to use a credentials file which @@ -271,11 +261,9 @@ CLASS="CONSTANT" 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 + <VAR CLASS="PARAMETER" -><I ->-A</I -></TT +>-A</VAR > for more details. </P ><P >Be cautious about including passwords in scripts. Also, on @@ -441,7 +429,7 @@ CLASS="EMPHASIS" ><P ><B CLASS="COMMAND" ->adddriver <arch> <config></B +>adddriver <arch> <config></B > - Execute an AddPrinterDriver() RPC to install the printer driver information on the server. Note that the driver files should @@ -450,21 +438,17 @@ CLASS="COMMAND" CLASS="COMMAND" >getdriverdir</B >. Possible values for - <TT + <VAR CLASS="PARAMETER" -><I ->arch</I -></TT +>arch</VAR > are the same as those for the <B CLASS="COMMAND" >getdriverdir</B > command. - The <TT + The <VAR CLASS="PARAMETER" -><I ->config</I -></TT +>config</VAR > parameter is defined as follows: </P ><P @@ -493,8 +477,8 @@ Comma Separated list of Files</PRE ><P ><B CLASS="COMMAND" ->addprinter <printername> - <sharename> <drivername> <port></B +>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 @@ -502,11 +486,9 @@ CLASS="COMMAND" CLASS="COMMAND" >adddriver</B >) - and the <TT + and the <VAR CLASS="PARAMETER" -><I ->port</I -></TT +>port</VAR >must be a valid port name (see <B CLASS="COMMAND" @@ -540,7 +522,7 @@ CLASS="COMMAND" ><P ><B CLASS="COMMAND" ->enumjobs <printer></B +>enumjobs <printer></B > - List the jobs and status of a given printer. This command corresponds to the MS Platform SDK EnumJobs() @@ -582,7 +564,7 @@ CLASS="COMMAND" ><P ><B CLASS="COMMAND" ->getdata <printername></B +>getdata <printername></B > - Retrieve the data for a given printer setting. See the <B @@ -596,7 +578,7 @@ CLASS="COMMAND" ><P ><B CLASS="COMMAND" ->getdriver <printername></B +>getdriver <printername></B > - Retrieve the printer driver information (such as driver file, config file, dependent files, etc...) for @@ -608,16 +590,14 @@ CLASS="COMMAND" ><P ><B CLASS="COMMAND" ->getdriverdir <arch></B +>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 <TT + values for <VAR CLASS="PARAMETER" -><I ->arch</I -></TT +>arch</VAR > are "Windows 4.0" (for Windows 95/98), "Windows NT x86", "Windows NT PowerPC", "Windows Alpha_AXP", and "Windows NT R4000". </P @@ -626,7 +606,7 @@ CLASS="PARAMETER" ><P ><B CLASS="COMMAND" ->getprinter <printername></B +>getprinter <printername></B > - Retrieve the current printer information. This command corresponds to the GetPrinter() MS Platform SDK function. @@ -636,7 +616,7 @@ CLASS="COMMAND" ><P ><B CLASS="COMMAND" ->openprinter <printername></B +>openprinter <printername></B > - Execute an OpenPrinterEx() and ClosePrinter() RPC against a given printer. </P @@ -645,8 +625,8 @@ CLASS="COMMAND" ><P ><B CLASS="COMMAND" ->setdriver <printername> - <drivername></B +>setdriver <printername> + <drivername></B > - Execute a SetPrinter() command to update the printer driver associated with an installed printer. The printer driver must diff --git a/docs/htmldocs/samba-bdc.html b/docs/htmldocs/samba-bdc.html index 42f653fb7d..c0c1805f8f 100644 --- a/docs/htmldocs/samba-bdc.html +++ b/docs/htmldocs/samba-bdc.html @@ -5,7 +5,7 @@ >How to Act as a Backup Domain Controller in a Purely Samba Controlled Domain</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -80,9 +80,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1274" -></A ->6.1. Prerequisite Reading</H1 +NAME="AEN1177" +>6.1. Prerequisite Reading</A +></H1 ><P >Before you continue reading in this chapter, please make sure that you are comfortable with configuring a Samba PDC @@ -97,9 +97,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1278" -></A ->6.2. Background</H1 +NAME="AEN1181" +>6.2. Background</A +></H1 ><P >What is a Domain Controller? It is a machine that is able to answer logon requests from workstations in a Windows NT Domain. Whenever a @@ -142,9 +142,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1286" -></A ->6.3. What qualifies a Domain Controller on the network?</H1 +NAME="AEN1189" +>6.3. What qualifies a Domain Controller on the network?</A +></H1 ><P >Every machine that is a Domain Controller for the domain SAMBA has to register the NetBIOS group name SAMBA#1c with the WINS server and/or @@ -159,9 +159,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1289" -></A ->6.3.1. How does a Workstation find its domain controller?</H2 +NAME="AEN1192" +>6.3.1. How does a Workstation find its domain controller?</A +></H2 ><P >A NT workstation in the domain SAMBA that wants a local user to be authenticated has to find the domain controller for SAMBA. It does @@ -178,9 +178,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1292" -></A ->6.3.2. When is the PDC needed?</H2 +NAME="AEN1195" +>6.3.2. When is the PDC needed?</A +></H2 ><P >Whenever a user wants to change his password, this has to be done on the PDC. To find the PDC, the workstation does a NetBIOS name query @@ -194,9 +194,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1295" -></A ->6.4. Can Samba be a Backup Domain Controller to an NT PDC?</H1 +NAME="AEN1198" +>6.4. Can Samba be a Backup Domain Controller to an NT PDC?</A +></H1 ><P >With version 2.2, no. The native NT SAM replication protocols have not yet been fully implemented. The Samba Team is working on @@ -217,9 +217,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1300" -></A ->6.5. How do I set up a Samba BDC?</H1 +NAME="AEN1203" +>6.5. How do I set up a Samba BDC?</A +></H1 ><P >Several things have to be done:</P ><P @@ -284,9 +284,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1317" -></A ->6.5.1. How do I replicate the smbpasswd file?</H2 +NAME="AEN1220" +>6.5.1. How do I replicate the smbpasswd file?</A +></H2 ><P >Replication of the smbpasswd file is sensitive. It has to be done whenever changes to the SAM are made. Every user's password change is @@ -305,9 +305,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1321" -></A ->6.5.2. Can I do this all with LDAP?</H2 +NAME="AEN1224" +>6.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 diff --git a/docs/htmldocs/samba-howto-collection.html b/docs/htmldocs/samba-howto-collection.html index 82e29206ac..51b4fddcba 100644 --- a/docs/htmldocs/samba-howto-collection.html +++ b/docs/htmldocs/samba-howto-collection.html @@ -5,7 +5,7 @@ >SAMBA Project Documentation</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK REL="NEXT" TITLE="General installation" HREF="introduction.html"></HEAD @@ -27,8 +27,8 @@ CLASS="TITLEPAGE" CLASS="TITLE" ><A NAME="SAMBA-HOWTO-COLLECTION" -></A ->SAMBA Project Documentation</H1 +>SAMBA Project Documentation</A +></H1 ><H3 CLASS="AUTHOR" ><A @@ -102,57 +102,33 @@ HREF="install.html" ><DT >1.1. <A HREF="install.html#AEN26" ->Read the man pages</A +>Obtaining and installing samba</A ></DT ><DT >1.2. <A -HREF="install.html#AEN36" ->Building the Binaries</A +HREF="install.html#AEN31" +>Configuring samba</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 -><DT ->1.7. <A -HREF="install.html#AEN145" >Try listing the shares available on your server</A ></DT ><DT ->1.8. <A -HREF="install.html#AEN154" +>1.4. <A +HREF="install.html#AEN73" >Try connecting with the unix client</A ></DT ><DT ->1.9. <A -HREF="install.html#AEN170" +>1.5. <A +HREF="install.html#AEN89" >Try connecting from a DOS, WfWg, Win9x, WinNT, Win2k, OS/2, etc... client</A ></DT ><DT ->1.10. <A -HREF="install.html#AEN184" +>1.6. <A +HREF="install.html#AEN103" >What If Things Don't Work?</A ></DT ></DL @@ -166,32 +142,32 @@ HREF="browsing-quick.html" ><DL ><DT >2.1. <A -HREF="browsing-quick.html#AEN230" +HREF="browsing-quick.html#AEN130" >Discussion</A ></DT ><DT >2.2. <A -HREF="browsing-quick.html#AEN238" +HREF="browsing-quick.html#AEN139" >Use of the "Remote Announce" parameter</A ></DT ><DT >2.3. <A -HREF="browsing-quick.html#AEN252" +HREF="browsing-quick.html#AEN153" >Use of the "Remote Browse Sync" parameter</A ></DT ><DT >2.4. <A -HREF="browsing-quick.html#AEN257" +HREF="browsing-quick.html#AEN158" >Use of WINS</A ></DT ><DT >2.5. <A -HREF="browsing-quick.html#AEN268" +HREF="browsing-quick.html#AEN169" >Do NOT use more than one (1) protocol on MS Windows machines</A ></DT ><DT >2.6. <A -HREF="browsing-quick.html#AEN274" +HREF="browsing-quick.html#AEN177" >Name Resolution Order</A ></DT ></DL @@ -205,42 +181,42 @@ HREF="passdb.html" ><DL ><DT >3.1. <A -HREF="passdb.html#AEN324" +HREF="passdb.html#AEN227" >Introduction</A ></DT ><DT >3.2. <A -HREF="passdb.html#AEN331" +HREF="passdb.html#AEN234" >Important Notes About Security</A ></DT ><DT >3.3. <A -HREF="passdb.html#AEN357" +HREF="passdb.html#AEN260" >The smbpasswd Command</A ></DT ><DT >3.4. <A -HREF="passdb.html#AEN388" +HREF="passdb.html#AEN291" >Plain text</A ></DT ><DT >3.5. <A -HREF="passdb.html#AEN393" +HREF="passdb.html#AEN296" >TDB</A ></DT ><DT >3.6. <A -HREF="passdb.html#AEN396" +HREF="passdb.html#AEN299" >LDAP</A ></DT ><DT >3.7. <A -HREF="passdb.html#AEN614" +HREF="passdb.html#AEN517" >MySQL</A ></DT ><DT >3.8. <A -HREF="passdb.html#AEN662" +HREF="passdb.html#AEN565" >Passdb XML plugin</A ></DT ></DL @@ -268,49 +244,49 @@ HREF="samba-pdc.html" ><DL ><DT >5.1. <A -HREF="samba-pdc.html#AEN722" +HREF="samba-pdc.html#AEN625" >Prerequisite Reading</A ></DT ><DT >5.2. <A -HREF="samba-pdc.html#AEN728" +HREF="samba-pdc.html#AEN631" >Background</A ></DT ><DT >5.3. <A -HREF="samba-pdc.html#AEN767" +HREF="samba-pdc.html#AEN670" >Configuring the Samba Domain Controller</A ></DT ><DT >5.4. <A -HREF="samba-pdc.html#AEN810" +HREF="samba-pdc.html#AEN713" >Creating Machine Trust Accounts and Joining Clients to the Domain</A ></DT ><DT >5.5. <A -HREF="samba-pdc.html#AEN894" +HREF="samba-pdc.html#AEN797" >Common Problems and Errors</A ></DT ><DT >5.6. <A -HREF="samba-pdc.html#AEN942" +HREF="samba-pdc.html#AEN845" >System Policies and Profiles</A ></DT ><DT >5.7. <A -HREF="samba-pdc.html#AEN986" +HREF="samba-pdc.html#AEN889" >What other help can I get?</A ></DT ><DT >5.8. <A -HREF="samba-pdc.html#AEN1100" +HREF="samba-pdc.html#AEN1003" >Domain Control for Windows 9x/ME</A ></DT ><DT >5.9. <A -HREF="samba-pdc.html#AEN1238" ->DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba</A +HREF="samba-pdc.html#AEN1141" +>DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba</A ></DT ></DL ></DD @@ -323,27 +299,27 @@ HREF="samba-bdc.html" ><DL ><DT >6.1. <A -HREF="samba-bdc.html#AEN1274" +HREF="samba-bdc.html#AEN1177" >Prerequisite Reading</A ></DT ><DT >6.2. <A -HREF="samba-bdc.html#AEN1278" +HREF="samba-bdc.html#AEN1181" >Background</A ></DT ><DT >6.3. <A -HREF="samba-bdc.html#AEN1286" +HREF="samba-bdc.html#AEN1189" >What qualifies a Domain Controller on the network?</A ></DT ><DT >6.4. <A -HREF="samba-bdc.html#AEN1295" +HREF="samba-bdc.html#AEN1198" >Can Samba be a Backup Domain Controller to an NT PDC?</A ></DT ><DT >6.5. <A -HREF="samba-bdc.html#AEN1300" +HREF="samba-bdc.html#AEN1203" >How do I set up a Samba BDC?</A ></DT ></DL @@ -357,42 +333,42 @@ HREF="ads.html" ><DL ><DT >7.1. <A -HREF="ads.html#AEN1339" +HREF="ads.html#AEN1242" >Installing the required packages for Debian</A ></DT ><DT >7.2. <A -HREF="ads.html#AEN1346" +HREF="ads.html#AEN1249" >Installing the required packages for RedHat</A ></DT ><DT >7.3. <A -HREF="ads.html#AEN1356" +HREF="ads.html#AEN1259" >Compile Samba</A ></DT ><DT >7.4. <A -HREF="ads.html#AEN1371" +HREF="ads.html#AEN1274" >Setup your /etc/krb5.conf</A ></DT ><DT >7.5. <A -HREF="ads.html#AEN1381" +HREF="ads.html#AEN1284" >Create the computer account</A ></DT ><DT >7.6. <A -HREF="ads.html#AEN1393" +HREF="ads.html#AEN1296" >Test your server setup</A ></DT ><DT >7.7. <A -HREF="ads.html#AEN1398" +HREF="ads.html#AEN1301" >Testing with smbclient</A ></DT ><DT >7.8. <A -HREF="ads.html#AEN1401" +HREF="ads.html#AEN1304" >Notes</A ></DT ></DL @@ -406,17 +382,17 @@ HREF="domain-security.html" ><DL ><DT >8.1. <A -HREF="domain-security.html#AEN1423" +HREF="domain-security.html#AEN1326" >Joining an NT Domain with Samba 3.0</A ></DT ><DT >8.2. <A -HREF="domain-security.html#AEN1478" +HREF="domain-security.html#AEN1381" >Samba and Windows 2000 Domains</A ></DT ><DT >8.3. <A -HREF="domain-security.html#AEN1481" +HREF="domain-security.html#AEN1384" >Why is this better than security = server?</A ></DT ></DL @@ -439,34 +415,34 @@ HREF="integrate-ms-networks.html" ><DL ><DT >9.1. <A -HREF="integrate-ms-networks.html#AEN1513" +HREF="integrate-ms-networks.html#AEN1416" >Agenda</A ></DT ><DT >9.2. <A -HREF="integrate-ms-networks.html#AEN1535" +HREF="integrate-ms-networks.html#AEN1438" >Name Resolution in a pure Unix/Linux world</A ></DT ><DT >9.3. <A -HREF="integrate-ms-networks.html#AEN1598" +HREF="integrate-ms-networks.html#AEN1501" >Name resolution as used within MS Windows networking</A ></DT ><DT >9.4. <A -HREF="integrate-ms-networks.html#AEN1643" +HREF="integrate-ms-networks.html#AEN1546" >How browsing functions and how to deploy stable and dependable browsing using Samba</A ></DT ><DT >9.5. <A -HREF="integrate-ms-networks.html#AEN1653" +HREF="integrate-ms-networks.html#AEN1556" >MS Windows security options and how to configure Samba for seemless integration</A ></DT ><DT >9.6. <A -HREF="integrate-ms-networks.html#AEN1723" +HREF="integrate-ms-networks.html#AEN1626" >Conclusions</A ></DT ></DL @@ -480,39 +456,39 @@ HREF="unix-permissions.html" ><DL ><DT >10.1. <A -HREF="unix-permissions.html#AEN1744" +HREF="unix-permissions.html#AEN1647" >Viewing and changing UNIX permissions using the NT security dialogs</A ></DT ><DT >10.2. <A -HREF="unix-permissions.html#AEN1748" +HREF="unix-permissions.html#AEN1651" >How to view file security on a Samba share</A ></DT ><DT >10.3. <A -HREF="unix-permissions.html#AEN1759" +HREF="unix-permissions.html#AEN1662" >Viewing file ownership</A ></DT ><DT >10.4. <A -HREF="unix-permissions.html#AEN1779" +HREF="unix-permissions.html#AEN1682" >Viewing file or directory permissions</A ></DT ><DT >10.5. <A -HREF="unix-permissions.html#AEN1815" +HREF="unix-permissions.html#AEN1718" >Modifying file or directory permissions</A ></DT ><DT >10.6. <A -HREF="unix-permissions.html#AEN1837" +HREF="unix-permissions.html#AEN1740" >Interaction with the standard Samba create mask parameters</A ></DT ><DT >10.7. <A -HREF="unix-permissions.html#AEN1901" +HREF="unix-permissions.html#AEN1804" >Interaction with the standard Samba file attribute mapping</A ></DT @@ -528,17 +504,17 @@ managed authentication</A ><DL ><DT >11.1. <A -HREF="pam.html#AEN1922" +HREF="pam.html#AEN1825" >Samba and PAM</A ></DT ><DT >11.2. <A -HREF="pam.html#AEN1966" +HREF="pam.html#AEN1869" >Distributed Authentication</A ></DT ><DT >11.3. <A -HREF="pam.html#AEN1973" +HREF="pam.html#AEN1876" >PAM Configuration in smb.conf</A ></DT ></DL @@ -552,7 +528,7 @@ HREF="msdfs.html" ><DL ><DT >12.1. <A -HREF="msdfs.html#AEN1993" +HREF="msdfs.html#AEN1896" >Instructions</A ></DT ></DL @@ -566,22 +542,22 @@ HREF="printing.html" ><DL ><DT >13.1. <A -HREF="printing.html#AEN2054" +HREF="printing.html#AEN1957" >Introduction</A ></DT ><DT >13.2. <A -HREF="printing.html#AEN2076" +HREF="printing.html#AEN1979" >Configuration</A ></DT ><DT >13.3. <A -HREF="printing.html#AEN2184" +HREF="printing.html#AEN2087" >The Imprints Toolset</A ></DT ><DT >13.4. <A -HREF="printing.html#AEN2227" +HREF="printing.html#AEN2130" >Diagnosis</A ></DT ></DL @@ -595,37 +571,37 @@ HREF="winbind.html" ><DL ><DT >14.1. <A -HREF="winbind.html#AEN2360" +HREF="winbind.html#AEN2263" >Abstract</A ></DT ><DT >14.2. <A -HREF="winbind.html#AEN2364" +HREF="winbind.html#AEN2267" >Introduction</A ></DT ><DT >14.3. <A -HREF="winbind.html#AEN2377" +HREF="winbind.html#AEN2280" >What Winbind Provides</A ></DT ><DT >14.4. <A -HREF="winbind.html#AEN2388" +HREF="winbind.html#AEN2291" >How Winbind Works</A ></DT ><DT >14.5. <A -HREF="winbind.html#AEN2431" +HREF="winbind.html#AEN2334" >Installation and Configuration</A ></DT ><DT >14.6. <A -HREF="winbind.html#AEN2680" +HREF="winbind.html#AEN2583" >Limitations</A ></DT ><DT >14.7. <A -HREF="winbind.html#AEN2690" +HREF="winbind.html#AEN2593" >Conclusion</A ></DT ></DL @@ -639,57 +615,57 @@ HREF="improved-browsing.html" ><DL ><DT >15.1. <A -HREF="improved-browsing.html#AEN2700" +HREF="improved-browsing.html#AEN2603" >Overview of browsing</A ></DT ><DT >15.2. <A -HREF="improved-browsing.html#AEN2704" +HREF="improved-browsing.html#AEN2608" >Browsing support in samba</A ></DT ><DT >15.3. <A -HREF="improved-browsing.html#AEN2713" +HREF="improved-browsing.html#AEN2616" >Problem resolution</A ></DT ><DT >15.4. <A -HREF="improved-browsing.html#AEN2720" +HREF="improved-browsing.html#AEN2625" >Browsing across subnets</A ></DT ><DT >15.5. <A -HREF="improved-browsing.html#AEN2760" +HREF="improved-browsing.html#AEN2665" >Setting up a WINS server</A ></DT ><DT >15.6. <A -HREF="improved-browsing.html#AEN2779" +HREF="improved-browsing.html#AEN2684" >Setting up Browsing in a WORKGROUP</A ></DT ><DT >15.7. <A -HREF="improved-browsing.html#AEN2797" +HREF="improved-browsing.html#AEN2702" >Setting up Browsing in a DOMAIN</A ></DT ><DT >15.8. <A -HREF="improved-browsing.html#AEN2807" +HREF="improved-browsing.html#AEN2712" >Forcing samba to be the master</A ></DT ><DT >15.9. <A -HREF="improved-browsing.html#AEN2816" +HREF="improved-browsing.html#AEN2721" >Making samba the domain master</A ></DT ><DT >15.10. <A -HREF="improved-browsing.html#AEN2834" +HREF="improved-browsing.html#AEN2739" >Note about broadcast addresses</A ></DT ><DT >15.11. <A -HREF="improved-browsing.html#AEN2837" +HREF="improved-browsing.html#AEN2742" >Multiple interfaces</A ></DT ></DL @@ -703,128 +679,148 @@ HREF="vfs.html" ><DL ><DT >16.1. <A -HREF="vfs.html#AEN2855" +HREF="vfs.html#AEN2760" >Introduction and configuration</A ></DT ><DT >16.2. <A -HREF="vfs.html#AEN2864" +HREF="vfs.html#AEN2769" >Included modules</A ></DT ><DT >16.3. <A -HREF="vfs.html#AEN2918" +HREF="vfs.html#AEN2823" >VFS modules available elsewhere</A ></DT ></DL ></DD ><DT >17. <A -HREF="cvs-access.html" ->Access Samba source code via CVS</A -></DT -><DD -><DL -><DT ->17.1. <A -HREF="cvs-access.html#AEN2942" ->Introduction</A -></DT -><DT ->17.2. <A -HREF="cvs-access.html#AEN2947" ->CVS Access to samba.org</A -></DT -></DL -></DD -><DT ->18. <A HREF="groupmapping.html" >Group mapping HOWTO</A ></DT ><DT ->19. <A +>18. <A HREF="speed.html" >Samba performance issues</A ></DT ><DD ><DL ><DT ->19.1. <A -HREF="speed.html#AEN3033" +>18.1. <A +HREF="speed.html#AEN2890" >Comparisons</A ></DT ><DT ->19.2. <A -HREF="speed.html#AEN3039" +>18.2. <A +HREF="speed.html#AEN2896" >Socket options</A ></DT ><DT ->19.3. <A -HREF="speed.html#AEN3046" +>18.3. <A +HREF="speed.html#AEN2903" >Read size</A ></DT ><DT ->19.4. <A -HREF="speed.html#AEN3051" +>18.4. <A +HREF="speed.html#AEN2908" >Max xmit</A ></DT ><DT ->19.5. <A -HREF="speed.html#AEN3056" +>18.5. <A +HREF="speed.html#AEN2913" >Log level</A ></DT ><DT ->19.6. <A -HREF="speed.html#AEN3059" +>18.6. <A +HREF="speed.html#AEN2916" >Read raw</A ></DT ><DT ->19.7. <A -HREF="speed.html#AEN3064" +>18.7. <A +HREF="speed.html#AEN2921" >Write raw</A ></DT ><DT ->19.8. <A -HREF="speed.html#AEN3068" +>18.8. <A +HREF="speed.html#AEN2925" >Slow Clients</A ></DT ><DT ->19.9. <A -HREF="speed.html#AEN3072" +>18.9. <A +HREF="speed.html#AEN2929" >Slow Logins</A ></DT ><DT ->19.10. <A -HREF="speed.html#AEN3075" +>18.10. <A +HREF="speed.html#AEN2932" >Client tuning</A ></DT ></DL ></DD ><DT ->20. <A +>19. <A HREF="groupprofiles.html" ->Creating Group Profiles</A +>Creating Group Prolicy Files</A ></DT ><DD ><DL ><DT ->20.1. <A -HREF="groupprofiles.html#AEN3123" +>19.1. <A +HREF="groupprofiles.html#AEN2980" >Windows '9x</A ></DT ><DT ->20.2. <A -HREF="groupprofiles.html#AEN3132" +>19.2. <A +HREF="groupprofiles.html#AEN2990" >Windows NT 4</A ></DT ><DT ->20.3. <A -HREF="groupprofiles.html#AEN3170" +>19.3. <A +HREF="groupprofiles.html#AEN3028" >Windows 2000/XP</A ></DT ></DL ></DD +><DT +>20. <A +HREF="securing-samba.html" +>Securing Samba</A +></DT +><DD +><DL +><DT +>20.1. <A +HREF="securing-samba.html#AEN3109" +>Introduction</A +></DT +><DT +>20.2. <A +HREF="securing-samba.html#AEN3112" +>Using host based protection</A +></DT +><DT +>20.3. <A +HREF="securing-samba.html#AEN3119" +>Using interface protection</A +></DT +><DT +>20.4. <A +HREF="securing-samba.html#AEN3128" +>Using a firewall</A +></DT +><DT +>20.5. <A +HREF="securing-samba.html#AEN3135" +>Using a IPC$ share deny</A +></DT +><DT +>20.6. <A +HREF="securing-samba.html#AEN3144" +>Upgrading Samba</A +></DT +></DL +></DD ></DL ></DD ><DT @@ -843,24 +839,29 @@ HREF="portability.html" ><DL ><DT >21.1. <A -HREF="portability.html#AEN3251" +HREF="portability.html#AEN3156" >HPUX</A ></DT ><DT >21.2. <A -HREF="portability.html#AEN3257" +HREF="portability.html#AEN3162" >SCO Unix</A ></DT ><DT >21.3. <A -HREF="portability.html#AEN3261" +HREF="portability.html#AEN3166" >DNIX</A ></DT ><DT >21.4. <A -HREF="portability.html#AEN3290" +HREF="portability.html#AEN3195" >RedHat Linux Rembrandt-II</A ></DT +><DT +>21.5. <A +HREF="portability.html#AEN3201" +>AIX</A +></DT ></DL ></DD ><DT @@ -872,95 +873,124 @@ HREF="other-clients.html" ><DL ><DT >22.1. <A -HREF="other-clients.html#AEN3311" +HREF="other-clients.html#AEN3221" >Macintosh clients?</A ></DT ><DT >22.2. <A -HREF="other-clients.html#AEN3320" +HREF="other-clients.html#AEN3230" >OS2 Client</A ></DT ><DT >22.3. <A -HREF="other-clients.html#AEN3360" +HREF="other-clients.html#AEN3270" >Windows for Workgroups</A ></DT ><DT >22.4. <A -HREF="other-clients.html#AEN3381" +HREF="other-clients.html#AEN3294" >Windows '95/'98</A ></DT ><DT >22.5. <A -HREF="other-clients.html#AEN3397" +HREF="other-clients.html#AEN3310" >Windows 2000 Service Pack 2</A ></DT ></DL ></DD ><DT >23. <A +HREF="compiling.html" +>How to compile SAMBA</A +></DT +><DD +><DL +><DT +>23.1. <A +HREF="compiling.html#AEN3337" +>Access Samba source code via CVS</A +></DT +><DT +>23.2. <A +HREF="compiling.html#AEN3380" +>Accessing the samba sources via rsync and ftp</A +></DT +><DT +>23.3. <A +HREF="compiling.html#AEN3386" +>Building the Binaries</A +></DT +><DT +>23.4. <A +HREF="compiling.html#AEN3414" +>Starting the smbd and nmbd</A +></DT +></DL +></DD +><DT +>24. <A HREF="bugreport.html" >Reporting Bugs</A ></DT ><DD ><DL ><DT ->23.1. <A -HREF="bugreport.html#AEN3421" +>24.1. <A +HREF="bugreport.html#AEN3476" >Introduction</A ></DT ><DT ->23.2. <A -HREF="bugreport.html#AEN3431" +>24.2. <A +HREF="bugreport.html#AEN3486" >General info</A ></DT ><DT ->23.3. <A -HREF="bugreport.html#AEN3437" +>24.3. <A +HREF="bugreport.html#AEN3492" >Debug levels</A ></DT ><DT ->23.4. <A -HREF="bugreport.html#AEN3454" +>24.4. <A +HREF="bugreport.html#AEN3509" >Internal errors</A ></DT ><DT ->23.5. <A -HREF="bugreport.html#AEN3464" +>24.5. <A +HREF="bugreport.html#AEN3519" >Attaching to a running process</A ></DT ><DT ->23.6. <A -HREF="bugreport.html#AEN3467" +>24.6. <A +HREF="bugreport.html#AEN3522" >Patches</A ></DT ></DL ></DD ><DT ->24. <A +>25. <A HREF="diagnosis.html" ->Diagnosing your samba server</A +>The samba checklist</A ></DT ><DD ><DL ><DT ->24.1. <A -HREF="diagnosis.html#AEN3490" +>25.1. <A +HREF="diagnosis.html#AEN3545" >Introduction</A ></DT ><DT ->24.2. <A -HREF="diagnosis.html#AEN3495" +>25.2. <A +HREF="diagnosis.html#AEN3550" >Assumptions</A ></DT ><DT ->24.3. <A -HREF="diagnosis.html#AEN3505" +>25.3. <A +HREF="diagnosis.html#AEN3560" >Tests</A ></DT ><DT ->24.4. <A -HREF="diagnosis.html#AEN3615" +>25.4. <A +HREF="diagnosis.html#AEN3670" >Still having troubles?</A ></DT ></DL diff --git a/docs/htmldocs/samba-ldap-howto.html b/docs/htmldocs/samba-ldap-howto.html deleted file mode 100644 index fa966d8eb1..0000000000 --- a/docs/htmldocs/samba-ldap-howto.html +++ /dev/null @@ -1,1011 +0,0 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> -<HTML -><HEAD -><TITLE ->Storing Samba's User/Machine Account information in an LDAP Directory</TITLE -><META -NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK -REL="HOME" -TITLE="SAMBA Project Documentation" -HREF="samba-howto-collection.html"><LINK -REL="UP" -TITLE="Optional configuration" -HREF="optional.html"><LINK -REL="PREVIOUS" -TITLE="Stackable VFS modules" -HREF="vfs.html"><LINK -REL="NEXT" -TITLE="HOWTO Access Samba source code via CVS" -HREF="cvs-access.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="vfs.html" -ACCESSKEY="P" ->Prev</A -></TD -><TD -WIDTH="80%" -ALIGN="center" -VALIGN="bottom" -></TD -><TD -WIDTH="10%" -ALIGN="right" -VALIGN="bottom" -><A -HREF="cvs-access.html" -ACCESSKEY="N" ->Next</A -></TD -></TR -></TABLE -><HR -ALIGN="LEFT" -WIDTH="100%"></DIV -><DIV -CLASS="CHAPTER" -><H1 -><A -NAME="SAMBA-LDAP-HOWTO" -></A ->Chapter 17. Storing Samba's User/Machine Account information in an LDAP Directory</H1 -><DIV -CLASS="SECT1" -><H1 -CLASS="SECT1" -><A -NAME="AEN2957" -></A ->17.1. Purpose</H1 -><P ->This document describes how to use an LDAP directory for storing Samba user -account information traditionally stored in the smbpasswd(5) file. It is -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="SECT1" -><H1 -CLASS="SECT1" -><A -NAME="AEN2977" -></A ->17.2. Introduction</H1 -><P ->Traditionally, when configuring <A -HREF="smb.conf.5.html#ENCRYPTPASSWORDS" -TARGET="_top" ->"encrypt -passwords = yes"</A -> in Samba's <TT -CLASS="FILENAME" ->smb.conf</TT -> file, user account -information such as username, LM/NT password hashes, password change times, and account -flags have been stored in the <TT -CLASS="FILENAME" ->smbpasswd(5)</TT -> file. There are several -disadvantages to this approach for sites with very large numbers of users (counted -in the thousands).</P -><P -></P -><UL -><LI -><P ->The first is that all lookups must be performed sequentially. Given that -there are approximately two lookups per domain logon (one for a normal -session connection such as when mapping a network drive or printer), this -is a performance bottleneck for lareg sites. What is needed is an indexed approach -such as is used in databases.</P -></LI -><LI -><P ->The second problem is that administrators who desired to replicate a -smbpasswd file to more than one Samba server were left to use external -tools such as <B -CLASS="COMMAND" ->rsync(1)</B -> and <B -CLASS="COMMAND" ->ssh(1)</B -> -and wrote custom, in-house scripts.</P -></LI -><LI -><P ->And finally, the amount of information which is stored in an -smbpasswd entry leaves no room for additional attributes such as -a home directory, password expiration time, or even a Relative -Identified (RID).</P -></LI -></UL -><P ->As a result of these defeciencies, a more robust means of storing user attributes -used by smbd was developed. The API which defines access to user accounts -is commonly referred to as the samdb interface (previously this was called the passdb -API, and is still so named in the CVS trees). In Samba 2.2.3, enabling support -for a samdb backend (e.g. <TT -CLASS="PARAMETER" -><I ->--with-ldapsam</I -></TT -> or -<TT -CLASS="PARAMETER" -><I ->--with-tdbsam</I -></TT ->) requires compile time support.</P -><P ->When compiling Samba to include the <TT -CLASS="PARAMETER" -><I ->--with-ldapsam</I -></TT -> autoconf -option, smbd (and associated tools) will store and lookup user accounts in -an LDAP directory. In reality, this is very easy to understand. If you are -comfortable with using an smbpasswd file, simply replace "smbpasswd" with -"LDAP directory" in all the documentation.</P -><P ->There are a few points to stress about what the <TT -CLASS="PARAMETER" -><I ->--with-ldapsam</I -></TT -> -does not provide. The LDAP support referred to in the this documentation does not -include:</P -><P -></P -><UL -><LI -><P ->A means of retrieving user account information from - an Windows 2000 Active Directory server.</P -></LI -><LI -><P ->A means of replacing /etc/passwd.</P -></LI -></UL -><P ->The second item can be accomplished by using LDAP NSS and PAM modules. LGPL -versions of these libraries can be obtained from PADL Software -(<A -HREF="http://www.padl.com/" -TARGET="_top" ->http://www.padl.com/</A ->). However, -the details of configuring these packages are beyond the scope of this document.</P -></DIV -><DIV -CLASS="SECT1" -><H1 -CLASS="SECT1" -><A -NAME="AEN3006" -></A ->17.3. Supported LDAP Servers</H1 -><P ->The LDAP samdb code in 2.2.3 has been developed and tested using the OpenLDAP -2.0 server and client libraries. The same code should be able to work with -Netscape's Directory Server and client SDK. However, due to lack of testing -so far, there are bound to be compile errors and bugs. These should not be -hard to fix. If you are so inclined, please be sure to forward all patches to -<A -HREF="samba-patches@samba.org" -TARGET="_top" ->samba-patches@samba.org</A -> and -<A -HREF="jerry@samba.org" -TARGET="_top" ->jerry@samba.org</A ->.</P -></DIV -><DIV -CLASS="SECT1" -><H1 -CLASS="SECT1" -><A -NAME="AEN3011" -></A ->17.4. Schema and Relationship to the RFC 2307 posixAccount</H1 -><P ->Samba 2.2.3 includes the necessary schema file for OpenLDAP 2.0 in -<TT -CLASS="FILENAME" ->examples/LDAP/samba.schema</TT ->. (Note that this schema -file has been modified since the experimental support initially included -in 2.2.2). The sambaAccount objectclass is given here:</P -><P -><PRE -CLASS="PROGRAMLISTING" ->objectclass ( 1.3.1.5.1.4.1.7165.2.2.2 NAME 'sambaAccount' SUP top STRUCTURAL - DESC 'Samba Account' - MUST ( uid $ rid ) - MAY ( cn $ lmPassword $ ntPassword $ pwdLastSet $ logonTime $ - logoffTime $ kickoffTime $ pwdCanChange $ pwdMustChange $ acctFlags $ - displayName $ smbHome $ homeDrive $ scriptPath $ profilePath $ - description $ userWorkstations $ primaryGroupID $ domain ))</PRE -></P -><P ->The samba.schema file has been formatted for OpenLDAP 2.0. The OID's are -owned by the Samba Team and as such is legal to be openly published. -If you translate the schema to be used with Netscape DS, please -submit the modified schema file as a patch to <A -HREF="jerry@samba.org" -TARGET="_top" ->jerry@samba.org</A -></P -><P ->Just as the smbpasswd file is mean to store information which supplements a -user's <TT -CLASS="FILENAME" ->/etc/passwd</TT -> entry, so is the sambaAccount object -meant to supplement the UNIX user account information. A sambaAccount is a -<TT -CLASS="CONSTANT" ->STRUCTURAL</TT -> objectclass so it can be stored individually -in the directory. However, there are several fields (e.g. uid) which overlap -with the posixAccount objectclass outlined in RFC2307. This is by design.</P -><P ->In order to store all user account information (UNIX and Samba) in the directory, -it is necessary to use the sambaAccount and posixAccount objectclasses in -combination. However, smbd will still obtain the user's UNIX account -information via the standard C library calls (e.g. getpwnam(), et. al.). -This means that the Samba server must also have the LDAP NSS library installed -and functioning correctly. This division of information makes it possible to -store all Samba account information in LDAP, but still maintain UNIX account -information in NIS while the network is transitioning to a full LDAP infrastructure.</P -></DIV -><DIV -CLASS="SECT1" -><H1 -CLASS="SECT1" -><A -NAME="AEN3023" -></A ->17.5. Configuring Samba with LDAP</H1 -><DIV -CLASS="SECT2" -><H2 -CLASS="SECT2" -><A -NAME="AEN3025" -></A ->17.5.1. OpenLDAP configuration</H2 -><P ->To include support for the sambaAccount object in an OpenLDAP directory -server, first copy the samba.schema file to slapd's configuration directory.</P -><P -><TT -CLASS="PROMPT" ->root# </TT -><B -CLASS="COMMAND" ->cp samba.schema /etc/openldap/schema/</B -></P -><P ->Next, include the <TT -CLASS="FILENAME" ->samba.schema</TT -> file in <TT -CLASS="FILENAME" ->slapd.conf</TT ->. -The sambaAccount object contains two attributes which depend upon other schema -files. The 'uid' attribute is defined in <TT -CLASS="FILENAME" ->cosine.schema</TT -> and -the 'displayName' attribute is defined in the <TT -CLASS="FILENAME" ->inetorgperson.schema</TT -> -file. Both of these must be included before the <TT -CLASS="FILENAME" ->samba.schema</TT -> file.</P -><P -><PRE -CLASS="PROGRAMLISTING" ->## /etc/openldap/slapd.conf - -## schema files (core.schema is required by default) -include /etc/openldap/schema/core.schema - -## needed for sambaAccount -include /etc/openldap/schema/cosine.schema -include /etc/openldap/schema/inetorgperson.schema -include /etc/openldap/schema/samba.schema - -## uncomment this line if you want to support the RFC2307 (NIS) schema -## include /etc/openldap/schema/nis.schema - -....</PRE -></P -><P ->It is recommended that you maintain some indices on some of the most usefull attributes, -like in the following example, to speed up searches made on sambaAccount objectclasses -(and possibly posixAccount and posixGroup as well).</P -><P -><PRE -CLASS="PROGRAMLISTING" -># Indices to maintain -## required by OpenLDAP 2.0 -index objectclass eq - -## support pb_getsampwnam() -index uid pres,eq -## support pdb_getsambapwrid() -index rid eq - -## uncomment these if you are storing posixAccount and -## posixGroup entries in the directory as well -##index uidNumber eq -##index gidNumber eq -##index cn eq -##index memberUid eq</PRE -></P -></DIV -><DIV -CLASS="SECT2" -><H2 -CLASS="SECT2" -><A -NAME="AEN3042" -></A ->17.5.2. Configuring Samba</H2 -><P ->The following parameters are available in smb.conf only with <TT -CLASS="PARAMETER" -><I ->--with-ldapsam</I -></TT -> -was included with compiling Samba.</P -><P -></P -><UL -><LI -><P -><A -HREF="smb.conf.5.html#LDAPSSL" -TARGET="_top" ->ldap ssl</A -></P -></LI -><LI -><P -><A -HREF="smb.conf.5.html#LDAPSERVER" -TARGET="_top" ->ldap server</A -></P -></LI -><LI -><P -><A -HREF="smb.conf.5.html#LDAPADMINDN" -TARGET="_top" ->ldap admin dn</A -></P -></LI -><LI -><P -><A -HREF="smb.conf.5.html#LDAPSUFFIX" -TARGET="_top" ->ldap suffix</A -></P -></LI -><LI -><P -><A -HREF="smb.conf.5.html#LDAPFILTER" -TARGET="_top" ->ldap filter</A -></P -></LI -><LI -><P -><A -HREF="smb.conf.5.html#LDAPPORT" -TARGET="_top" ->ldap port</A -></P -></LI -></UL -><P ->These are described in the <A -HREF="smb.conf.5.html" -TARGET="_top" ->smb.conf(5)</A -> man -page and so will not be repeated here. However, a sample smb.conf file for -use with an LDAP directory could appear as</P -><P -><PRE -CLASS="PROGRAMLISTING" ->## /usr/local/samba/lib/smb.conf -[global] - security = user - encrypt passwords = yes - - netbios name = TASHTEGO - workgroup = NARNIA - - # ldap related parameters - - # define the DN to use when binding to the directory servers - # The password for this DN is not stored in smb.conf. Rather it - # must be set by using 'smbpasswd -w <TT -CLASS="REPLACEABLE" -><I ->secretpw</I -></TT ->' to store the - # passphrase in the secrets.tdb file. If the "ldap admin dn" values - # changes, this password will need to be reset. - ldap admin dn = "cn=Samba Manager,ou=people,dc=samba,dc=org" - - # specify the LDAP server's hostname (defaults to locahost) - ldap server = ahab.samba.org - - # Define the SSL option when connecting to the directory - # ('off', 'start tls', or 'on' (default)) - ldap ssl = start tls - - # define the port to use in the LDAP session (defaults to 636 when - # "ldap ssl = on") - ldap port = 389 - - # specify the base DN to use when searching the directory - ldap suffix = "ou=people,dc=samba,dc=org" - - # generally the default ldap search filter is ok - # ldap filter = "(&(uid=%u)(objectclass=sambaAccount))"</PRE -></P -></DIV -></DIV -><DIV -CLASS="SECT1" -><H1 -CLASS="SECT1" -><A -NAME="AEN3070" -></A ->17.6. Accounts and Groups management</H1 -><P ->As users accounts are managed thru the sambaAccount objectclass, you should -modify you existing administration tools to deal with sambaAccount attributes.</P -><P ->Machines accounts are managed with the sambaAccount objectclass, just -like users accounts. However, it's up to you to stored thoses accounts -in a different tree of you LDAP namespace: you should use -"ou=Groups,dc=plainjoe,dc=org" to store groups and -"ou=People,dc=plainjoe,dc=org" to store users. Just configure your -NSS and PAM accordingly (usually, in the /etc/ldap.conf configuration -file).</P -><P ->In Samba release 2.2.3, the group management system is based on posix -groups. This meand that Samba make usage of the posixGroup objectclass. -For now, there is no NT-like group system management (global and local -groups).</P -></DIV -><DIV -CLASS="SECT1" -><H1 -CLASS="SECT1" -><A -NAME="AEN3075" -></A ->17.7. Security and sambaAccount</H1 -><P ->There are two important points to remember when discussing the security -of sambaAccount entries in the directory.</P -><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="SECT1" -><H1 -CLASS="SECT1" -><A -NAME="AEN3095" -></A ->17.8. LDAP specials attributes for sambaAccounts</H1 -><P ->The sambaAccount objectclass is composed of the following attributes:</P -><P -></P -><UL -><LI -><P -><TT -CLASS="CONSTANT" ->lmPassword</TT ->: the LANMAN password 16-byte hash stored as a character - representation of a hexidecimal string.</P -></LI -><LI -><P -><TT -CLASS="CONSTANT" ->ntPassword</TT ->: the NT password hash 16-byte stored as a character - representation of a hexidecimal string.</P -></LI -><LI -><P -><TT -CLASS="CONSTANT" ->pwdLastSet</TT ->: The integer time in seconds since 1970 when the - <TT -CLASS="CONSTANT" ->lmPassword</TT -> and <TT -CLASS="CONSTANT" ->ntPassword</TT -> attributes were last set. - </P -></LI -><LI -><P -><TT -CLASS="CONSTANT" ->acctFlags</TT ->: string of 11 characters surrounded by square brackets [] - representing account flags such as U (user), W(workstation), X(no password expiration), and - D(disabled).</P -></LI -><LI -><P -><TT -CLASS="CONSTANT" ->logonTime</TT ->: Integer value currently unused</P -></LI -><LI -><P -><TT -CLASS="CONSTANT" ->logoffTime</TT ->: Integer value currently unused</P -></LI -><LI -><P -><TT -CLASS="CONSTANT" ->kickoffTime</TT ->: Integer value currently unused</P -></LI -><LI -><P -><TT -CLASS="CONSTANT" ->pwdCanChange</TT ->: Integer value currently unused</P -></LI -><LI -><P -><TT -CLASS="CONSTANT" ->pwdMustChange</TT ->: Integer value currently unused</P -></LI -><LI -><P -><TT -CLASS="CONSTANT" ->homeDrive</TT ->: specifies the drive letter to which to map the - UNC path specified by homeDirectory. The drive letter must be specified in the form "X:" - where X is the letter of the drive to map. Refer to the "logon drive" parameter in the - smb.conf(5) man page for more information.</P -></LI -><LI -><P -><TT -CLASS="CONSTANT" ->scriptPath</TT ->: The scriptPath property specifies the path of - the user's logon script, .CMD, .EXE, or .BAT file. The string can be null. The path - is relative to the netlogon share. Refer to the "logon script" parameter in the - smb.conf(5) man page for more information.</P -></LI -><LI -><P -><TT -CLASS="CONSTANT" ->profilePath</TT ->: specifies a path to the user's profile. - This value can be a null string, a local absolute path, or a UNC path. Refer to the - "logon path" parameter in the smb.conf(5) man page for more information.</P -></LI -><LI -><P -><TT -CLASS="CONSTANT" ->smbHome</TT ->: The homeDirectory property specifies the path of - the home directory for the user. The string can be null. If homeDrive is set and specifies - a drive letter, homeDirectory should be a UNC path. The path must be a network - UNC path of the form \\server\share\directory. This value can be a null string. - Refer to the "logon home" parameter in the smb.conf(5) man page for more information. - </P -></LI -><LI -><P -><TT -CLASS="CONSTANT" ->userWorkstation</TT ->: character string value currently unused. - </P -></LI -><LI -><P -><TT -CLASS="CONSTANT" ->rid</TT ->: the integer representation of the user's relative identifier - (RID).</P -></LI -><LI -><P -><TT -CLASS="CONSTANT" ->primaryGroupID</TT ->: the relative identifier (RID) of the primary group - of the user.</P -></LI -></UL -><P ->The majority of these parameters are only used when Samba is acting as a PDC of -a domain (refer to the <A -HREF="Samba-PDC-HOWTO.html" -TARGET="_top" ->Samba-PDC-HOWTO</A -> for details on -how to configure Samba as a Primary Domain Controller). The following four attributes -are only stored with the sambaAccount entry if the values are non-default values:</P -><P -></P -><UL -><LI -><P ->smbHome</P -></LI -><LI -><P ->scriptPath</P -></LI -><LI -><P ->logonPath</P -></LI -><LI -><P ->homeDrive</P -></LI -></UL -><P ->These attributes are only stored with the sambaAccount entry if -the values are non-default values. For example, assume TASHTEGO has now been -configured as a PDC and that <B -CLASS="COMMAND" ->logon home = \\%L\%u</B -> was defined in -its <TT -CLASS="FILENAME" ->smb.conf</TT -> file. When a user named "becky" logons to the domain, -the <TT -CLASS="PARAMETER" -><I ->logon home</I -></TT -> string is expanded to \\TASHTEGO\becky. -If the smbHome attribute exists in the entry "uid=becky,ou=people,dc=samba,dc=org", -this value is used. However, if this attribute does not exist, then the value -of the <TT -CLASS="PARAMETER" -><I ->logon home</I -></TT -> parameter is used in its place. Samba -will only write the attribute value to the directory entry is the value is -something other than the default (e.g. \\MOBY\becky).</P -></DIV -><DIV -CLASS="SECT1" -><H1 -CLASS="SECT1" -><A -NAME="AEN3165" -></A ->17.9. Example LDIF Entries for a sambaAccount</H1 -><P ->The following is a working LDIF with the inclusion of the posixAccount objectclass:</P -><P -><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 -CLASS="SECT1" -><H1 -CLASS="SECT1" -><A -NAME="AEN3173" -></A ->17.10. Comments</H1 -><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 -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="vfs.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="cvs-access.html" -ACCESSKEY="N" ->Next</A -></TD -></TR -><TR -><TD -WIDTH="33%" -ALIGN="left" -VALIGN="top" ->Stackable VFS modules</TD -><TD -WIDTH="34%" -ALIGN="center" -VALIGN="top" -><A -HREF="optional.html" -ACCESSKEY="U" ->Up</A -></TD -><TD -WIDTH="33%" -ALIGN="right" -VALIGN="top" ->HOWTO Access Samba source code via CVS</TD -></TR -></TABLE -></DIV -></BODY -></HTML ->
\ No newline at end of file diff --git a/docs/htmldocs/samba-pdc.html b/docs/htmldocs/samba-pdc.html index 63a52129d0..7c4caf4f30 100644 --- a/docs/htmldocs/samba-pdc.html +++ b/docs/htmldocs/samba-pdc.html @@ -5,7 +5,7 @@ >Samba as a NT4 or Win2k Primary Domain Controller</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -80,9 +80,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN722" -></A ->5.1. Prerequisite Reading</H1 +NAME="AEN625" +>5.1. Prerequisite Reading</A +></H1 ><P >Before you continue reading in this chapter, please make sure that you are comfortable with configuring basic files services @@ -108,9 +108,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN728" -></A ->5.2. Background</H1 +NAME="AEN631" +>5.2. Background</A +></H1 ><DIV CLASS="NOTE" ><P @@ -260,9 +260,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN767" -></A ->5.3. Configuring the Samba Domain Controller</H1 +NAME="AEN670" +>5.3. Configuring the Samba Domain Controller</A +></H1 ><P >The first step in creating a working Samba PDC is to understand the parameters necessary in smb.conf. I will not @@ -288,21 +288,17 @@ CLASS="PROGRAMLISTING" HREF="smb.conf.5.html#NETBIOSNAME" TARGET="_top" >netbios name</A -> = <TT +> = <VAR CLASS="REPLACEABLE" -><I ->POGO</I -></TT +>POGO</VAR > <A HREF="smb.conf.5.html#WORKGROUP" TARGET="_top" >workgroup</A -> = <TT +> = <VAR CLASS="REPLACEABLE" -><I ->NARNIA</I -></TT +>NARNIA</VAR > ; we should act as the domain and local master browser @@ -392,11 +388,9 @@ TARGET="_top" HREF="smb.conf.5.html#WRITELIST" TARGET="_top" >write list</A -> = <TT +> = <VAR CLASS="REPLACEABLE" -><I ->ntadmin</I -></TT +>ntadmin</VAR > ; share for storing user profiles @@ -472,10 +466,10 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN810" -></A +NAME="AEN713" >5.4. Creating Machine Trust Accounts and Joining Clients to the -Domain</H1 +Domain</A +></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 @@ -546,9 +540,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN829" -></A ->5.4.1. Manual Creation of Machine Trust Accounts</H2 +NAME="AEN732" +>5.4.1. Manual Creation of Machine Trust Accounts</A +></H2 ><P >The first step in manually creating a machine trust account is to manually create the corresponding Unix account in @@ -563,55 +557,45 @@ CLASS="COMMAND" used to create new Unix accounts. The following is an example for a Linux based Samba server:</P ><P -> <TT +> <SAMP CLASS="PROMPT" ->root# </TT +>root# </SAMP ><B CLASS="COMMAND" ->/usr/sbin/useradd -g 100 -d /dev/null -c <TT +>/usr/sbin/useradd -g 100 -d /dev/null -c <VAR CLASS="REPLACEABLE" -><I >"machine -nickname"</I -></TT -> -s /bin/false <TT +nickname"</VAR +> -s /bin/false <VAR CLASS="REPLACEABLE" -><I ->machine_name</I -></TT +>machine_name</VAR >$ </B ></P ><P -><TT +><SAMP CLASS="PROMPT" ->root# </TT +>root# </SAMP ><B CLASS="COMMAND" ->passwd -l <TT +>passwd -l <VAR CLASS="REPLACEABLE" -><I ->machine_name</I -></TT +>machine_name</VAR >$</B ></P ><P >On *BSD systems, this can be done using the 'chpass' utility:</P ><P -><TT +><SAMP CLASS="PROMPT" ->root# </TT +>root# </SAMP ><B CLASS="COMMAND" ->chpass -a "<TT +>chpass -a "<VAR CLASS="REPLACEABLE" -><I ->machine_name</I -></TT ->$:*:101:100::0:0:Workstation <TT +>machine_name</VAR +>$:*:101:100::0:0:Workstation <VAR CLASS="REPLACEABLE" -><I ->machine_name</I -></TT +>machine_name</VAR >:/dev/null:/sbin/nologin"</B ></P ><P @@ -628,26 +612,20 @@ CLASS="FILENAME" ><P ><PRE CLASS="PROGRAMLISTING" ->doppy$:x:505:501:<TT +>doppy$:x:505:501:<VAR CLASS="REPLACEABLE" -><I ->machine_nickname</I -></TT +>machine_nickname</VAR >:/dev/null:/bin/false</PRE ></P ><P ->Above, <TT +>Above, <VAR CLASS="REPLACEABLE" -><I ->machine_nickname</I -></TT +>machine_nickname</VAR > can be any descriptive name for the client, i.e., BasementComputer. -<TT +<VAR CLASS="REPLACEABLE" -><I ->machine_name</I -></TT +>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 @@ -665,24 +643,20 @@ CLASS="COMMAND" > command as shown here:</P ><P -><TT +><SAMP CLASS="PROMPT" ->root# </TT +>root# </SAMP ><B CLASS="COMMAND" ->smbpasswd -a -m <TT +>smbpasswd -a -m <VAR CLASS="REPLACEABLE" -><I ->machine_name</I -></TT +>machine_name</VAR ></B ></P ><P ->where <TT +>where <VAR CLASS="REPLACEABLE" -><I ->machine_name</I -></TT +>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 @@ -736,9 +710,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN870" -></A ->5.4.2. "On-the-Fly" Creation of Machine Trust Accounts</H2 +NAME="AEN773" +>5.4.2. "On-the-Fly" Creation of Machine Trust Accounts</A +></H2 ><P >The second (and recommended) way of creating machine trust accounts is simply to allow the Samba server to create them as needed when the client @@ -764,7 +738,7 @@ be created manually.</P ><PRE CLASS="PROGRAMLISTING" >[global] - # <...remainder of parameters...> + # <...remainder of parameters...> add user script = /usr/sbin/useradd -d /dev/null -g 100 -s /bin/false -M %u </PRE ></P ></DIV @@ -773,9 +747,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN879" -></A ->5.4.3. Joining the Client to the Domain</H2 +NAME="AEN782" +>5.4.3. Joining the Client to the Domain</A +></H2 ><P >The procedure for joining a client to the domain varies with the version of Windows.</P @@ -841,9 +815,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN894" -></A ->5.5. Common Problems and Errors</H1 +NAME="AEN797" +>5.5. Common Problems and Errors</A +></H1 ><P ></P ><P @@ -897,9 +871,9 @@ CLASS="EMPHASIS" will remove all network drive connections: </P ><P -> <TT +> <SAMP CLASS="PROMPT" ->C:\WINNT\></TT +>C:\WINNT\></SAMP > <B CLASS="COMMAND" >net use * /d</B @@ -962,11 +936,9 @@ CLASS="EMPHASIS" </P ><P > This problem is caused by the PDC not having a suitable machine trust account. - If you are using the <TT + If you are using the <VAR CLASS="PARAMETER" -><I ->add user script</I -></TT +>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. @@ -1010,11 +982,9 @@ CLASS="COMMAND" </P ><P > In order to work around this problem in 2.2.0, configure the - <TT + <VAR CLASS="PARAMETER" -><I ->account</I -></TT +>account</VAR > control flag in <TT CLASS="FILENAME" @@ -1051,9 +1021,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN942" -></A ->5.6. System Policies and Profiles</H1 +NAME="AEN845" +>5.6. System Policies and Profiles</A +></H1 ><P >Much of the information necessary to implement System Policies and Roving User Profiles in a Samba domain is the same as that for @@ -1228,9 +1198,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN986" -></A ->5.7. What other help can I get?</H1 +NAME="AEN889" +>5.7. What other help can I get?</A +></H1 ><P >There are many sources of information available in the form of mailing lists, RFC's and documentation. The docs that come @@ -1648,9 +1618,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1100" -></A ->5.8. Domain Control for Windows 9x/ME</H1 +NAME="AEN1003" +>5.8. Domain Control for Windows 9x/ME</A +></H1 ><DIV CLASS="NOTE" ><P @@ -1727,7 +1697,7 @@ TYPE="1" ><LI ><P > The client broadcasts (to the IP broadcast address of the subnet it is in) - a NetLogon request. This is sent to the NetBIOS name DOMAIN<1c> at the + a NetLogon request. This is sent to the NetBIOS name DOMAIN<1c> at the NetBIOS layer. The client chooses the first response it receives, which contains the NetBIOS name of the logon server to use in the format of \\SERVER. @@ -1782,9 +1752,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1126" -></A ->5.8.1. Configuration Instructions: Network Logons</H2 +NAME="AEN1029" +>5.8.1. Configuration Instructions: Network Logons</A +></H2 ><P >The main difference between a PDC and a Windows 9x logon server configuration is that</P @@ -1837,20 +1807,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 <TT +modes other than <CODE CLASS="CONSTANT" ->USER</TT +>USER</CODE >. The only security mode -which will not work due to technical reasons is <TT +which will not work due to technical reasons is <CODE CLASS="CONSTANT" ->SHARE</TT +>SHARE</CODE > -mode security. <TT +mode security. <CODE CLASS="CONSTANT" ->DOMAIN</TT -> and <TT +>DOMAIN</CODE +> and <CODE CLASS="CONSTANT" ->SERVER</TT +>SERVER</CODE > mode security is really just a variation on SMB user level security.</P ><P @@ -1888,9 +1858,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1145" -></A ->5.8.2. Configuration Instructions: Setting up Roaming User Profiles</H2 +NAME="AEN1048" +>5.8.2. Configuration Instructions: Setting up Roaming User Profiles</A +></H2 ><DIV CLASS="WARNING" ><P @@ -1941,9 +1911,9 @@ CLASS="SECT3" ><H3 CLASS="SECT3" ><A -NAME="AEN1153" -></A ->5.8.2.1. Windows NT Configuration</H3 +NAME="AEN1056" +>5.8.2.1. Windows NT Configuration</A +></H3 ><P >To support WinNT clients, in the [global] section of smb.conf set the following (for example):</P @@ -1992,9 +1962,9 @@ CLASS="SECT3" ><H3 CLASS="SECT3" ><A -NAME="AEN1161" -></A ->5.8.2.2. Windows 9X Configuration</H3 +NAME="AEN1064" +>5.8.2.2. Windows 9X Configuration</A +></H3 ><P >To support Win9X clients, you must use the "logon home" parameter. Samba has now been fixed so that "net use/home" now works as well, and it, too, relies @@ -2023,9 +1993,9 @@ CLASS="SECT3" ><H3 CLASS="SECT3" ><A -NAME="AEN1169" -></A ->5.8.2.3. Win9X and WinNT Configuration</H3 +NAME="AEN1072" +>5.8.2.3. Win9X and WinNT Configuration</A +></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 @@ -2068,9 +2038,9 @@ CLASS="SECT3" ><H3 CLASS="SECT3" ><A -NAME="AEN1176" -></A ->5.8.2.4. Windows 9X Profile Setup</H3 +NAME="AEN1079" +>5.8.2.4. Windows 9X Profile Setup</A +></H3 ><P >When a user first logs in on Windows 9X, the file user.DAT is created, as are folders "Start Menu", "Desktop", "Programs" and "Nethood". @@ -2228,9 +2198,9 @@ CLASS="SECT3" ><H3 CLASS="SECT3" ><A -NAME="AEN1212" -></A ->5.8.2.5. Windows NT Workstation 4.0</H3 +NAME="AEN1115" +>5.8.2.5. Windows NT Workstation 4.0</A +></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 @@ -2342,9 +2312,9 @@ CLASS="SECT3" ><H3 CLASS="SECT3" ><A -NAME="AEN1225" -></A ->5.8.2.6. Windows NT Server</H3 +NAME="AEN1128" +>5.8.2.6. Windows NT Server</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 @@ -2356,9 +2326,9 @@ CLASS="SECT3" ><H3 CLASS="SECT3" ><A -NAME="AEN1228" -></A ->5.8.2.7. Sharing Profiles between W95 and NT Workstation 4.0</H3 +NAME="AEN1131" +>5.8.2.7. Sharing Profiles between W95 and NT Workstation 4.0</A +></H3 ><DIV CLASS="WARNING" ><P @@ -2449,9 +2419,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1238" -></A ->5.9. DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba</H1 +NAME="AEN1141" +>5.9. DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba</A +></H1 ><DIV CLASS="WARNING" ><P @@ -2526,16 +2496,16 @@ may need to know to interact with the rest of the system.</P >The registry files can be located on any Windows NT machine by opening a command prompt and typing:</P ><P -><TT +><SAMP CLASS="PROMPT" ->C:\WINNT\></TT +>C:\WINNT\></SAMP > dir %SystemRoot%\System32\config</P ><P >The environment variable %SystemRoot% value can be obtained by typing:</P ><P -><TT +><SAMP CLASS="PROMPT" ->C:\WINNT></TT +>C:\WINNT></SAMP >echo %SystemRoot%</P ><P >The active parts of the registry that you may want to be familiar with are diff --git a/docs/htmldocs/samba.7.html b/docs/htmldocs/samba.7.html index 796bce7d20..689fba7cee 100644 --- a/docs/htmldocs/samba.7.html +++ b/docs/htmldocs/samba.7.html @@ -5,7 +5,7 @@ >samba</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"></HEAD +CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD ><BODY CLASS="REFENTRY" BGCOLOR="#FFFFFF" diff --git a/docs/htmldocs/securing-samba.html b/docs/htmldocs/securing-samba.html new file mode 100644 index 0000000000..7db24fff09 --- /dev/null +++ b/docs/htmldocs/securing-samba.html @@ -0,0 +1,307 @@ +<!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="Optional configuration" +HREF="optional.html"><LINK +REL="PREVIOUS" +TITLE="Creating Group Prolicy Files" +HREF="groupprofiles.html"><LINK +REL="NEXT" +TITLE="Appendixes" +HREF="appendixes.html"></HEAD +><BODY +CLASS="CHAPTER" +BGCOLOR="#FFFFFF" +TEXT="#000000" +LINK="#0000FF" +VLINK="#840084" +ALINK="#0000FF" +><DIV +CLASS="NAVHEADER" +><TABLE +SUMMARY="Header navigation table" +WIDTH="100%" +BORDER="0" +CELLPADDING="0" +CELLSPACING="0" +><TR +><TH +COLSPAN="3" +ALIGN="center" +>SAMBA Project Documentation</TH +></TR +><TR +><TD +WIDTH="10%" +ALIGN="left" +VALIGN="bottom" +><A +HREF="groupprofiles.html" +ACCESSKEY="P" +>Prev</A +></TD +><TD +WIDTH="80%" +ALIGN="center" +VALIGN="bottom" +></TD +><TD +WIDTH="10%" +ALIGN="right" +VALIGN="bottom" +><A +HREF="appendixes.html" +ACCESSKEY="N" +>Next</A +></TD +></TR +></TABLE +><HR +ALIGN="LEFT" +WIDTH="100%"></DIV +><DIV +CLASS="CHAPTER" +><H1 +><A +NAME="SECURING-SAMBA" +></A +>Chapter 20. Securing Samba</H1 +><DIV +CLASS="SECT1" +><H1 +CLASS="SECT1" +><A +NAME="AEN3109" +>20.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="AEN3112" +>20.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 'hosts allow' and +'hosts deny' options in the Samba smb.conf 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="AEN3119" +>20.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="AEN3128" +>20.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="AEN3135" +>20.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="AEN3144" +>20.6. Upgrading Samba</A +></H1 +><P +>Please check regularly on http://www.samba.org/ 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="groupprofiles.html" +ACCESSKEY="P" +>Prev</A +></TD +><TD +WIDTH="34%" +ALIGN="center" +VALIGN="top" +><A +HREF="samba-howto-collection.html" +ACCESSKEY="H" +>Home</A +></TD +><TD +WIDTH="33%" +ALIGN="right" +VALIGN="top" +><A +HREF="appendixes.html" +ACCESSKEY="N" +>Next</A +></TD +></TR +><TR +><TD +WIDTH="33%" +ALIGN="left" +VALIGN="top" +>Creating Group Prolicy Files</TD +><TD +WIDTH="34%" +ALIGN="center" +VALIGN="top" +><A +HREF="optional.html" +ACCESSKEY="U" +>Up</A +></TD +><TD +WIDTH="33%" +ALIGN="right" +VALIGN="top" +>Appendixes</TD +></TR +></TABLE +></DIV +></BODY +></HTML +>
\ No newline at end of file diff --git a/docs/htmldocs/securitylevels.html b/docs/htmldocs/securitylevels.html index 9501fa5c6a..0904611dbe 100644 --- a/docs/htmldocs/securitylevels.html +++ b/docs/htmldocs/securitylevels.html @@ -5,7 +5,7 @@ >User and Share security level (for servers not in a domain)</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK diff --git a/docs/htmldocs/smb.conf.5.html b/docs/htmldocs/smb.conf.5.html index 5a8bfe7d67..e66b848be7 100644 --- a/docs/htmldocs/smb.conf.5.html +++ b/docs/htmldocs/smb.conf.5.html @@ -5,7 +5,7 @@ >smb.conf</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"></HEAD +CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD ><BODY CLASS="REFENTRY" BGCOLOR="#FFFFFF" @@ -69,17 +69,13 @@ NAME="AEN17" until the next section begins. Sections contain parameters of the form</P ><P -><TT +><VAR CLASS="REPLACEABLE" -><I ->name</I -></TT -> = <TT +>name</VAR +> = <VAR CLASS="REPLACEABLE" -><I >value - </I -></TT + </VAR ></P ><P >The file is line-based - that is, each newline-terminated @@ -178,11 +174,11 @@ CLASS="FILENAME" The share is accessed via the share name "foo":</P ><PRE CLASS="SCREEN" -><TT +><SAMP CLASS="COMPUTEROUTPUT" >[foo] path = /home/bar - read only = no</TT + read only = no</SAMP ></PRE ><P >The following sample section defines a printable share. @@ -199,13 +195,13 @@ CLASS="EMPHASIS" elsewhere):</P ><PRE CLASS="SCREEN" -><TT +><SAMP CLASS="COMPUTEROUTPUT" >[aprinter] path = /usr/spool/public read only = yes printable = yes - guest ok = yes</TT + guest ok = yes</SAMP ></PRE ></DIV ><DIV @@ -274,11 +270,9 @@ CLASS="EMPHASIS" in your [homes] section then you may find it useful to use the %S macro. For example :</P ><P -><TT +><KBD CLASS="USERINPUT" -><B ->path = /data/pchome/%S</B -></TT +>path = /data/pchome/%S</KBD ></P ><P >would be useful if you have different home directories @@ -300,10 +294,10 @@ CLASS="USERINPUT" section:</P ><PRE CLASS="SCREEN" -><TT +><SAMP CLASS="COMPUTEROUTPUT" >[homes] - read only = no</TT + read only = no</SAMP ></PRE ><P >An important point is that if guest access is specified @@ -401,12 +395,12 @@ NAME="AEN80" this:</P ><PRE CLASS="SCREEN" -><TT +><SAMP CLASS="COMPUTEROUTPUT" >[printers] path = /usr/spool/public guest ok = yes - printable = yes </TT + printable = yes </SAMP ></PRE ><P >All aliases given for a printer in the printcap file @@ -416,9 +410,9 @@ CLASS="COMPUTEROUTPUT" more lines like this:</P ><PRE CLASS="SCREEN" -><TT +><SAMP CLASS="COMPUTEROUTPUT" ->alias|alias|alias|alias... </TT +>alias|alias|alias|alias... </SAMP ></PRE ><P >Each alias should be an acceptable printer name for @@ -614,20 +608,16 @@ TARGET="_top" >Name of the domain or workgroup of the current user.</P ></DD ><DT ->%$(<TT +>%$(<VAR CLASS="REPLACEABLE" -><I ->envvar</I -></TT +>envvar</VAR >)</DT ><DD ><P >The value of the environment variable - <TT + <VAR CLASS="REPLACEABLE" -><I ->envar</I -></TT +>envar</VAR >.</P ></DD ></DL @@ -833,11 +823,9 @@ 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%<TT + \\server\service%<VAR CLASS="REPLACEABLE" -><I ->username</I -></TT +>username</VAR > method of passing a username.</P ></LI @@ -901,11 +889,9 @@ NAME="AEN258" ><P ><A HREF="#ABORTSHUTDOWNSCRIPT" -><TT +><VAR CLASS="PARAMETER" -><I ->abort shutdown script</I -></TT +>abort shutdown script</VAR ></A ></P ></LI @@ -913,11 +899,9 @@ CLASS="PARAMETER" ><P ><A HREF="#ADDGROUPSCRIPT" -><TT +><VAR CLASS="PARAMETER" -><I ->add group script</I -></TT +>add group script</VAR ></A ></P ></LI @@ -925,11 +909,9 @@ CLASS="PARAMETER" ><P ><A HREF="#ADDPRINTERCOMMAND" -><TT +><VAR CLASS="PARAMETER" -><I ->addprinter command</I -></TT +>addprinter command</VAR ></A ></P ></LI @@ -937,11 +919,9 @@ CLASS="PARAMETER" ><P ><A HREF="#ADDSHARECOMMAND" -><TT +><VAR CLASS="PARAMETER" -><I ->add share command</I -></TT +>add share command</VAR ></A ></P ></LI @@ -949,11 +929,9 @@ CLASS="PARAMETER" ><P ><A HREF="#ADDUSERSCRIPT" -><TT +><VAR CLASS="PARAMETER" -><I ->add user script</I -></TT +>add user script</VAR ></A ></P ></LI @@ -961,11 +939,9 @@ CLASS="PARAMETER" ><P ><A HREF="#ADDUSERTOGROUPSCRIPT" -><TT +><VAR CLASS="PARAMETER" -><I ->add user to group script</I -></TT +>add user to group script</VAR ></A ></P ></LI @@ -973,11 +949,9 @@ CLASS="PARAMETER" ><P ><A HREF="#ADDMACHINESCRIPT" -><TT +><VAR CLASS="PARAMETER" -><I ->add machine script</I -></TT +>add machine script</VAR ></A ></P ></LI @@ -985,11 +959,9 @@ CLASS="PARAMETER" ><P ><A HREF="#DELETEGROUPSCRIPT" -><TT +><VAR CLASS="PARAMETER" -><I ->delete group script</I -></TT +>delete group script</VAR ></A ></P ></LI @@ -997,11 +969,9 @@ CLASS="PARAMETER" ><P ><A HREF="#ADSSERVER" -><TT +><VAR CLASS="PARAMETER" -><I ->ads server</I -></TT +>ads server</VAR ></A ></P ></LI @@ -1009,11 +979,9 @@ CLASS="PARAMETER" ><P ><A HREF="#ALGORITHMICRIDBASE" -><TT +><VAR CLASS="PARAMETER" -><I ->algorithmic rid base</I -></TT +>algorithmic rid base</VAR ></A ></P ></LI @@ -1021,11 +989,9 @@ CLASS="PARAMETER" ><P ><A HREF="#ALLOWTRUSTEDDOMAINS" -><TT +><VAR CLASS="PARAMETER" -><I ->allow trusted domains</I -></TT +>allow trusted domains</VAR ></A ></P ></LI @@ -1033,11 +999,9 @@ CLASS="PARAMETER" ><P ><A HREF="#ANNOUNCEAS" -><TT +><VAR CLASS="PARAMETER" -><I ->announce as</I -></TT +>announce as</VAR ></A ></P ></LI @@ -1045,11 +1009,9 @@ CLASS="PARAMETER" ><P ><A HREF="#ANNOUNCEVERSION" -><TT +><VAR CLASS="PARAMETER" -><I ->announce version</I -></TT +>announce version</VAR ></A ></P ></LI @@ -1057,11 +1019,9 @@ CLASS="PARAMETER" ><P ><A HREF="#AUTHMETHODS" -><TT +><VAR CLASS="PARAMETER" -><I ->auth methods</I -></TT +>auth methods</VAR ></A ></P ></LI @@ -1069,11 +1029,9 @@ CLASS="PARAMETER" ><P ><A HREF="#AUTOSERVICES" -><TT +><VAR CLASS="PARAMETER" -><I ->auto services</I -></TT +>auto services</VAR ></A ></P ></LI @@ -1081,11 +1039,9 @@ CLASS="PARAMETER" ><P ><A HREF="#BINDINTERFACESONLY" -><TT +><VAR CLASS="PARAMETER" -><I ->bind interfaces only</I -></TT +>bind interfaces only</VAR ></A ></P ></LI @@ -1093,11 +1049,9 @@ CLASS="PARAMETER" ><P ><A HREF="#BROWSELIST" -><TT +><VAR CLASS="PARAMETER" -><I ->browse list</I -></TT +>browse list</VAR ></A ></P ></LI @@ -1105,11 +1059,9 @@ CLASS="PARAMETER" ><P ><A HREF="#CHANGENOTIFYTIMEOUT" -><TT +><VAR CLASS="PARAMETER" -><I ->change notify timeout</I -></TT +>change notify timeout</VAR ></A ></P ></LI @@ -1117,11 +1069,9 @@ CLASS="PARAMETER" ><P ><A HREF="#CHANGESHARECOMMAND" -><TT +><VAR CLASS="PARAMETER" -><I ->change share command</I -></TT +>change share command</VAR ></A ></P ></LI @@ -1129,11 +1079,9 @@ CLASS="PARAMETER" ><P ><A HREF="#CONFIGFILE" -><TT +><VAR CLASS="PARAMETER" -><I ->config file</I -></TT +>config file</VAR ></A ></P ></LI @@ -1141,11 +1089,9 @@ CLASS="PARAMETER" ><P ><A HREF="#DEADTIME" -><TT +><VAR CLASS="PARAMETER" -><I ->deadtime</I -></TT +>deadtime</VAR ></A ></P ></LI @@ -1153,11 +1099,9 @@ CLASS="PARAMETER" ><P ><A HREF="#DEBUGHIRESTIMESTAMP" -><TT +><VAR CLASS="PARAMETER" -><I ->debug hires timestamp</I -></TT +>debug hires timestamp</VAR ></A ></P ></LI @@ -1165,11 +1109,9 @@ CLASS="PARAMETER" ><P ><A HREF="#DEBUGPID" -><TT +><VAR CLASS="PARAMETER" -><I ->debug pid</I -></TT +>debug pid</VAR ></A ></P ></LI @@ -1177,11 +1119,9 @@ CLASS="PARAMETER" ><P ><A HREF="#DEBUGTIMESTAMP" -><TT +><VAR CLASS="PARAMETER" -><I ->debug timestamp</I -></TT +>debug timestamp</VAR ></A ></P ></LI @@ -1189,11 +1129,9 @@ CLASS="PARAMETER" ><P ><A HREF="#DEBUGUID" -><TT +><VAR CLASS="PARAMETER" -><I ->debug uid</I -></TT +>debug uid</VAR ></A ></P ></LI @@ -1201,11 +1139,9 @@ CLASS="PARAMETER" ><P ><A HREF="#DEBUGLEVEL" -><TT +><VAR CLASS="PARAMETER" -><I ->debuglevel</I -></TT +>debuglevel</VAR ></A ></P ></LI @@ -1213,11 +1149,9 @@ CLASS="PARAMETER" ><P ><A HREF="#DEFAULT" -><TT +><VAR CLASS="PARAMETER" -><I ->default</I -></TT +>default</VAR ></A ></P ></LI @@ -1225,11 +1159,9 @@ CLASS="PARAMETER" ><P ><A HREF="#DEFAULTSERVICE" -><TT +><VAR CLASS="PARAMETER" -><I ->default service</I -></TT +>default service</VAR ></A ></P ></LI @@ -1237,11 +1169,9 @@ CLASS="PARAMETER" ><P ><A HREF="#DELETEPRINTERCOMMAND" -><TT +><VAR CLASS="PARAMETER" -><I ->deleteprinter command</I -></TT +>deleteprinter command</VAR ></A ></P ></LI @@ -1249,11 +1179,9 @@ CLASS="PARAMETER" ><P ><A HREF="#DELETESHARECOMMAND" -><TT +><VAR CLASS="PARAMETER" -><I ->delete share command</I -></TT +>delete share command</VAR ></A ></P ></LI @@ -1261,11 +1189,9 @@ CLASS="PARAMETER" ><P ><A HREF="#DELETEUSERSCRIPT" -><TT +><VAR CLASS="PARAMETER" -><I ->delete user script</I -></TT +>delete user script</VAR ></A ></P ></LI @@ -1273,11 +1199,9 @@ CLASS="PARAMETER" ><P ><A HREF="#DELETEUSERFROMGROUPSCRIPT" -><TT +><VAR CLASS="PARAMETER" -><I ->delete user from group script</I -></TT +>delete user from group script</VAR ></A ></P ></LI @@ -1285,11 +1209,9 @@ CLASS="PARAMETER" ><P ><A HREF="#DFREECOMMAND" -><TT +><VAR CLASS="PARAMETER" -><I ->dfree command</I -></TT +>dfree command</VAR ></A ></P ></LI @@ -1297,11 +1219,9 @@ CLASS="PARAMETER" ><P ><A HREF="#DISABLENETBIOS" -><TT +><VAR CLASS="PARAMETER" -><I ->disable netbios</I -></TT +>disable netbios</VAR ></A ></P ></LI @@ -1309,11 +1229,9 @@ CLASS="PARAMETER" ><P ><A HREF="#DISABLESPOOLSS" -><TT +><VAR CLASS="PARAMETER" -><I ->disable spoolss</I -></TT +>disable spoolss</VAR ></A ></P ></LI @@ -1321,11 +1239,9 @@ CLASS="PARAMETER" ><P ><A HREF="#DISPLAYCHARSET" -><TT +><VAR CLASS="PARAMETER" -><I ->display charset</I -></TT +>display charset</VAR ></A ></P ></LI @@ -1333,11 +1249,9 @@ CLASS="PARAMETER" ><P ><A HREF="#DNSPROXY" -><TT +><VAR CLASS="PARAMETER" -><I ->dns proxy</I -></TT +>dns proxy</VAR ></A ></P ></LI @@ -1345,11 +1259,9 @@ CLASS="PARAMETER" ><P ><A HREF="#DOMAINLOGONS" -><TT +><VAR CLASS="PARAMETER" -><I ->domain logons</I -></TT +>domain logons</VAR ></A ></P ></LI @@ -1357,11 +1269,9 @@ CLASS="PARAMETER" ><P ><A HREF="#DOMAINMASTER" -><TT +><VAR CLASS="PARAMETER" -><I ->domain master</I -></TT +>domain master</VAR ></A ></P ></LI @@ -1369,11 +1279,9 @@ CLASS="PARAMETER" ><P ><A HREF="#DOSCHARSET" -><TT +><VAR CLASS="PARAMETER" -><I ->dos charset</I -></TT +>dos charset</VAR ></A ></P ></LI @@ -1381,11 +1289,9 @@ CLASS="PARAMETER" ><P ><A HREF="#ENCRYPTPASSWORDS" -><TT +><VAR CLASS="PARAMETER" -><I ->encrypt passwords</I -></TT +>encrypt passwords</VAR ></A ></P ></LI @@ -1393,11 +1299,9 @@ CLASS="PARAMETER" ><P ><A HREF="#ENHANCEDBROWSING" -><TT +><VAR CLASS="PARAMETER" -><I ->enhanced browsing</I -></TT +>enhanced browsing</VAR ></A ></P ></LI @@ -1405,11 +1309,9 @@ CLASS="PARAMETER" ><P ><A HREF="#ENUMPORTSCOMMAND" -><TT +><VAR CLASS="PARAMETER" -><I ->enumports command</I -></TT +>enumports command</VAR ></A ></P ></LI @@ -1417,11 +1319,9 @@ CLASS="PARAMETER" ><P ><A HREF="#GETWDCACHE" -><TT +><VAR CLASS="PARAMETER" -><I ->getwd cache</I -></TT +>getwd cache</VAR ></A ></P ></LI @@ -1429,11 +1329,9 @@ CLASS="PARAMETER" ><P ><A HREF="#HIDELOCALUSERS" -><TT +><VAR CLASS="PARAMETER" -><I ->hide local users</I -></TT +>hide local users</VAR ></A ></P ></LI @@ -1441,11 +1339,9 @@ CLASS="PARAMETER" ><P ><A HREF="#HIDEUNREADABLE" -><TT +><VAR CLASS="PARAMETER" -><I ->hide unreadable</I -></TT +>hide unreadable</VAR ></A ></P ></LI @@ -1453,11 +1349,9 @@ CLASS="PARAMETER" ><P ><A HREF="#HIDEUNWRITEABLEFILES" -><TT +><VAR CLASS="PARAMETER" -><I ->hide unwriteable files</I -></TT +>hide unwriteable files</VAR ></A ></P ></LI @@ -1465,11 +1359,9 @@ CLASS="PARAMETER" ><P ><A HREF="#HIDESPECIALFILES" -><TT +><VAR CLASS="PARAMETER" -><I ->hide special files</I -></TT +>hide special files</VAR ></A ></P ></LI @@ -1477,11 +1369,9 @@ CLASS="PARAMETER" ><P ><A HREF="#HOMEDIRMAP" -><TT +><VAR CLASS="PARAMETER" -><I ->homedir map</I -></TT +>homedir map</VAR ></A ></P ></LI @@ -1489,11 +1379,9 @@ CLASS="PARAMETER" ><P ><A HREF="#HOSTMSDFS" -><TT +><VAR CLASS="PARAMETER" -><I ->host msdfs</I -></TT +>host msdfs</VAR ></A ></P ></LI @@ -1501,11 +1389,9 @@ CLASS="PARAMETER" ><P ><A HREF="#HOSTNAMELOOKUPS" -><TT +><VAR CLASS="PARAMETER" -><I ->hostname lookups</I -></TT +>hostname lookups</VAR ></A ></P ></LI @@ -1513,11 +1399,9 @@ CLASS="PARAMETER" ><P ><A HREF="#HOSTSEQUIV" -><TT +><VAR CLASS="PARAMETER" -><I ->hosts equiv</I -></TT +>hosts equiv</VAR ></A ></P ></LI @@ -1525,11 +1409,9 @@ CLASS="PARAMETER" ><P ><A HREF="#INTERFACES" -><TT +><VAR CLASS="PARAMETER" -><I ->interfaces</I -></TT +>interfaces</VAR ></A ></P ></LI @@ -1537,11 +1419,9 @@ CLASS="PARAMETER" ><P ><A HREF="#KEEPALIVE" -><TT +><VAR CLASS="PARAMETER" -><I ->keepalive</I -></TT +>keepalive</VAR ></A ></P ></LI @@ -1549,11 +1429,9 @@ CLASS="PARAMETER" ><P ><A HREF="#KERNELOPLOCKS" -><TT +><VAR CLASS="PARAMETER" -><I ->kernel oplocks</I -></TT +>kernel oplocks</VAR ></A ></P ></LI @@ -1561,11 +1439,9 @@ CLASS="PARAMETER" ><P ><A HREF="#LANMANAUTH" -><TT +><VAR CLASS="PARAMETER" -><I ->lanman auth</I -></TT +>lanman auth</VAR ></A ></P ></LI @@ -1573,11 +1449,9 @@ CLASS="PARAMETER" ><P ><A HREF="#LARGEREADWRITE" -><TT +><VAR CLASS="PARAMETER" -><I ->large readwrite</I -></TT +>large readwrite</VAR ></A ></P ></LI @@ -1585,11 +1459,9 @@ CLASS="PARAMETER" ><P ><A HREF="#LDAPADMINDN" -><TT +><VAR CLASS="PARAMETER" -><I ->ldap admin dn</I -></TT +>ldap admin dn</VAR ></A ></P ></LI @@ -1597,11 +1469,9 @@ CLASS="PARAMETER" ><P ><A HREF="#LDAPFILTER" -><TT +><VAR CLASS="PARAMETER" -><I ->ldap filter</I -></TT +>ldap filter</VAR ></A ></P ></LI @@ -1609,11 +1479,9 @@ CLASS="PARAMETER" ><P ><A HREF="#LDAPPORT" -><TT +><VAR CLASS="PARAMETER" -><I ->ldap port</I -></TT +>ldap port</VAR ></A ></P ></LI @@ -1621,11 +1489,9 @@ CLASS="PARAMETER" ><P ><A HREF="#LDAPSERVER" -><TT +><VAR CLASS="PARAMETER" -><I ->ldap server</I -></TT +>ldap server</VAR ></A ></P ></LI @@ -1633,11 +1499,9 @@ CLASS="PARAMETER" ><P ><A HREF="#LDAPSSL" -><TT +><VAR CLASS="PARAMETER" -><I ->ldap ssl</I -></TT +>ldap ssl</VAR ></A ></P ></LI @@ -1645,11 +1509,9 @@ CLASS="PARAMETER" ><P ><A HREF="#LDAPSUFFIX" -><TT +><VAR CLASS="PARAMETER" -><I ->ldap suffix</I -></TT +>ldap suffix</VAR ></A ></P ></LI @@ -1657,11 +1519,9 @@ CLASS="PARAMETER" ><P ><A HREF="#LDAPUSERSUFFIX" -><TT +><VAR CLASS="PARAMETER" -><I ->ldap user suffix</I -></TT +>ldap user suffix</VAR ></A ></P ></LI @@ -1669,11 +1529,9 @@ CLASS="PARAMETER" ><P ><A HREF="#LDAPMACHINESUFFIX" -><TT +><VAR CLASS="PARAMETER" -><I ->ldap machine suffix</I -></TT +>ldap machine suffix</VAR ></A ></P ></LI @@ -1681,11 +1539,9 @@ CLASS="PARAMETER" ><P ><A HREF="#LDAPPASSWDSYNC" -><TT +><VAR CLASS="PARAMETER" -><I ->ldap passwd sync</I -></TT +>ldap passwd sync</VAR ></A ></P ></LI @@ -1693,11 +1549,9 @@ CLASS="PARAMETER" ><P ><A HREF="#LDAPTRUSTIDS" -><TT +><VAR CLASS="PARAMETER" -><I ->ldap trust ids</I -></TT +>ldap trust ids</VAR ></A ></P ></LI @@ -1705,11 +1559,9 @@ CLASS="PARAMETER" ><P ><A HREF="#LMANNOUNCE" -><TT +><VAR CLASS="PARAMETER" -><I ->lm announce</I -></TT +>lm announce</VAR ></A ></P ></LI @@ -1717,11 +1569,9 @@ CLASS="PARAMETER" ><P ><A HREF="#LMINTERVAL" -><TT +><VAR CLASS="PARAMETER" -><I ->lm interval</I -></TT +>lm interval</VAR ></A ></P ></LI @@ -1729,11 +1579,9 @@ CLASS="PARAMETER" ><P ><A HREF="#LOADPRINTERS" -><TT +><VAR CLASS="PARAMETER" -><I ->load printers</I -></TT +>load printers</VAR ></A ></P ></LI @@ -1741,11 +1589,9 @@ CLASS="PARAMETER" ><P ><A HREF="#LOCALMASTER" -><TT +><VAR CLASS="PARAMETER" -><I ->local master</I -></TT +>local master</VAR ></A ></P ></LI @@ -1753,11 +1599,9 @@ CLASS="PARAMETER" ><P ><A HREF="#LOCKDIR" -><TT +><VAR CLASS="PARAMETER" -><I ->lock dir</I -></TT +>lock dir</VAR ></A ></P ></LI @@ -1765,11 +1609,9 @@ CLASS="PARAMETER" ><P ><A HREF="#LOCKDIRECTORY" -><TT +><VAR CLASS="PARAMETER" -><I ->lock directory</I -></TT +>lock directory</VAR ></A ></P ></LI @@ -1777,11 +1619,9 @@ CLASS="PARAMETER" ><P ><A HREF="#LOCKSPINCOUNT" -><TT +><VAR CLASS="PARAMETER" -><I ->lock spin count</I -></TT +>lock spin count</VAR ></A ></P ></LI @@ -1789,11 +1629,9 @@ CLASS="PARAMETER" ><P ><A HREF="#LOCKSPINTIME" -><TT +><VAR CLASS="PARAMETER" -><I ->lock spin time</I -></TT +>lock spin time</VAR ></A ></P ></LI @@ -1801,11 +1639,9 @@ CLASS="PARAMETER" ><P ><A HREF="#PIDDIRECTORY" -><TT +><VAR CLASS="PARAMETER" -><I ->pid directory</I -></TT +>pid directory</VAR ></A ></P ></LI @@ -1813,11 +1649,9 @@ CLASS="PARAMETER" ><P ><A HREF="#LOGFILE" -><TT +><VAR CLASS="PARAMETER" -><I ->log file</I -></TT +>log file</VAR ></A ></P ></LI @@ -1825,11 +1659,9 @@ CLASS="PARAMETER" ><P ><A HREF="#LOGLEVEL" -><TT +><VAR CLASS="PARAMETER" -><I ->log level</I -></TT +>log level</VAR ></A ></P ></LI @@ -1837,11 +1669,9 @@ CLASS="PARAMETER" ><P ><A HREF="#LOGONDRIVE" -><TT +><VAR CLASS="PARAMETER" -><I ->logon drive</I -></TT +>logon drive</VAR ></A ></P ></LI @@ -1849,11 +1679,9 @@ CLASS="PARAMETER" ><P ><A HREF="#LOGONHOME" -><TT +><VAR CLASS="PARAMETER" -><I ->logon home</I -></TT +>logon home</VAR ></A ></P ></LI @@ -1861,11 +1689,9 @@ CLASS="PARAMETER" ><P ><A HREF="#LOGONPATH" -><TT +><VAR CLASS="PARAMETER" -><I ->logon path</I -></TT +>logon path</VAR ></A ></P ></LI @@ -1873,11 +1699,9 @@ CLASS="PARAMETER" ><P ><A HREF="#LOGONSCRIPT" -><TT +><VAR CLASS="PARAMETER" -><I ->logon script</I -></TT +>logon script</VAR ></A ></P ></LI @@ -1885,11 +1709,9 @@ CLASS="PARAMETER" ><P ><A HREF="#LPQCACHETIME" -><TT +><VAR CLASS="PARAMETER" -><I ->lpq cache time</I -></TT +>lpq cache time</VAR ></A ></P ></LI @@ -1897,11 +1719,19 @@ CLASS="PARAMETER" ><P ><A HREF="#MACHINEPASSWORDTIMEOUT" -><TT +><VAR CLASS="PARAMETER" -><I ->machine password timeout</I -></TT +>machine password timeout</VAR +></A +></P +></LI +><LI +><P +><A +HREF="#MANGLEPREFIX" +><VAR +CLASS="PARAMETER" +>mangle prefix</VAR ></A ></P ></LI @@ -1909,11 +1739,9 @@ CLASS="PARAMETER" ><P ><A HREF="#MANGLEDSTACK" -><TT +><VAR CLASS="PARAMETER" -><I ->mangled stack</I -></TT +>mangled stack</VAR ></A ></P ></LI @@ -1921,11 +1749,9 @@ CLASS="PARAMETER" ><P ><A HREF="#MAPTOGUEST" -><TT +><VAR CLASS="PARAMETER" -><I ->map to guest</I -></TT +>map to guest</VAR ></A ></P ></LI @@ -1933,11 +1759,9 @@ CLASS="PARAMETER" ><P ><A HREF="#MAXDISKSIZE" -><TT +><VAR CLASS="PARAMETER" -><I ->max disk size</I -></TT +>max disk size</VAR ></A ></P ></LI @@ -1945,11 +1769,9 @@ CLASS="PARAMETER" ><P ><A HREF="#MAXLOGSIZE" -><TT +><VAR CLASS="PARAMETER" -><I ->max log size</I -></TT +>max log size</VAR ></A ></P ></LI @@ -1957,11 +1779,9 @@ CLASS="PARAMETER" ><P ><A HREF="#MAXMUX" -><TT +><VAR CLASS="PARAMETER" -><I ->max mux</I -></TT +>max mux</VAR ></A ></P ></LI @@ -1969,11 +1789,9 @@ CLASS="PARAMETER" ><P ><A HREF="#MAXOPENFILES" -><TT +><VAR CLASS="PARAMETER" -><I ->max open files</I -></TT +>max open files</VAR ></A ></P ></LI @@ -1981,11 +1799,9 @@ CLASS="PARAMETER" ><P ><A HREF="#MAXPROTOCOL" -><TT +><VAR CLASS="PARAMETER" -><I ->max protocol</I -></TT +>max protocol</VAR ></A ></P ></LI @@ -1993,11 +1809,9 @@ CLASS="PARAMETER" ><P ><A HREF="#MAXSMBDPROCESSES" -><TT +><VAR CLASS="PARAMETER" -><I ->max smbd processes</I -></TT +>max smbd processes</VAR ></A ></P ></LI @@ -2005,11 +1819,9 @@ CLASS="PARAMETER" ><P ><A HREF="#MAXTTL" -><TT +><VAR CLASS="PARAMETER" -><I ->max ttl</I -></TT +>max ttl</VAR ></A ></P ></LI @@ -2017,11 +1829,9 @@ CLASS="PARAMETER" ><P ><A HREF="#MAXWINSTTL" -><TT +><VAR CLASS="PARAMETER" -><I ->max wins ttl</I -></TT +>max wins ttl</VAR ></A ></P ></LI @@ -2029,11 +1839,9 @@ CLASS="PARAMETER" ><P ><A HREF="#MAXXMIT" -><TT +><VAR CLASS="PARAMETER" -><I ->max xmit</I -></TT +>max xmit</VAR ></A ></P ></LI @@ -2041,11 +1849,9 @@ CLASS="PARAMETER" ><P ><A HREF="#MESSAGECOMMAND" -><TT +><VAR CLASS="PARAMETER" -><I ->message command</I -></TT +>message command</VAR ></A ></P ></LI @@ -2053,11 +1859,9 @@ CLASS="PARAMETER" ><P ><A HREF="#MINPASSWDLENGTH" -><TT +><VAR CLASS="PARAMETER" -><I ->min passwd length</I -></TT +>min passwd length</VAR ></A ></P ></LI @@ -2065,11 +1869,9 @@ CLASS="PARAMETER" ><P ><A HREF="#MINPASSWORDLENGTH" -><TT +><VAR CLASS="PARAMETER" -><I ->min password length</I -></TT +>min password length</VAR ></A ></P ></LI @@ -2077,11 +1879,9 @@ CLASS="PARAMETER" ><P ><A HREF="#MINPROTOCOL" -><TT +><VAR CLASS="PARAMETER" -><I ->min protocol</I -></TT +>min protocol</VAR ></A ></P ></LI @@ -2089,11 +1889,9 @@ CLASS="PARAMETER" ><P ><A HREF="#MINWINSTTL" -><TT +><VAR CLASS="PARAMETER" -><I ->min wins ttl</I -></TT +>min wins ttl</VAR ></A ></P ></LI @@ -2101,11 +1899,9 @@ CLASS="PARAMETER" ><P ><A HREF="#NAMECACHETIMEOUT" -><TT +><VAR CLASS="PARAMETER" -><I ->name cache timeout</I -></TT +>name cache timeout</VAR ></A ></P ></LI @@ -2113,11 +1909,9 @@ CLASS="PARAMETER" ><P ><A HREF="#NAMERESOLVEORDER" -><TT +><VAR CLASS="PARAMETER" -><I ->name resolve order</I -></TT +>name resolve order</VAR ></A ></P ></LI @@ -2125,11 +1919,9 @@ CLASS="PARAMETER" ><P ><A HREF="#NETBIOSALIASES" -><TT +><VAR CLASS="PARAMETER" -><I ->netbios aliases</I -></TT +>netbios aliases</VAR ></A ></P ></LI @@ -2137,11 +1929,9 @@ CLASS="PARAMETER" ><P ><A HREF="#NETBIOSNAME" -><TT +><VAR CLASS="PARAMETER" -><I ->netbios name</I -></TT +>netbios name</VAR ></A ></P ></LI @@ -2149,11 +1939,9 @@ CLASS="PARAMETER" ><P ><A HREF="#NETBIOSSCOPE" -><TT +><VAR CLASS="PARAMETER" -><I ->netbios scope</I -></TT +>netbios scope</VAR ></A ></P ></LI @@ -2161,11 +1949,9 @@ CLASS="PARAMETER" ><P ><A HREF="#NISHOMEDIR" -><TT +><VAR CLASS="PARAMETER" -><I ->nis homedir</I -></TT +>nis homedir</VAR ></A ></P ></LI @@ -2173,11 +1959,9 @@ CLASS="PARAMETER" ><P ><A HREF="#NTLMAUTH" -><TT +><VAR CLASS="PARAMETER" -><I ->ntlm auth</I -></TT +>ntlm auth</VAR ></A ></P ></LI @@ -2185,11 +1969,9 @@ CLASS="PARAMETER" ><P ><A HREF="#NONUNIXACCOUNTRANGE" -><TT +><VAR CLASS="PARAMETER" -><I ->non unix account range</I -></TT +>non unix account range</VAR ></A ></P ></LI @@ -2197,11 +1979,9 @@ CLASS="PARAMETER" ><P ><A HREF="#NTPIPESUPPORT" -><TT +><VAR CLASS="PARAMETER" -><I ->nt pipe support</I -></TT +>nt pipe support</VAR ></A ></P ></LI @@ -2209,11 +1989,9 @@ CLASS="PARAMETER" ><P ><A HREF="#NTSTATUSSUPPORT" -><TT +><VAR CLASS="PARAMETER" -><I ->nt status support</I -></TT +>nt status support</VAR ></A ></P ></LI @@ -2221,11 +1999,9 @@ CLASS="PARAMETER" ><P ><A HREF="#NULLPASSWORDS" -><TT +><VAR CLASS="PARAMETER" -><I ->null passwords</I -></TT +>null passwords</VAR ></A ></P ></LI @@ -2233,11 +2009,9 @@ CLASS="PARAMETER" ><P ><A HREF="#OBEYPAMRESTRICTIONS" -><TT +><VAR CLASS="PARAMETER" -><I ->obey pam restrictions</I -></TT +>obey pam restrictions</VAR ></A ></P ></LI @@ -2245,11 +2019,9 @@ CLASS="PARAMETER" ><P ><A HREF="#OPLOCKBREAKWAITTIME" -><TT +><VAR CLASS="PARAMETER" -><I ->oplock break wait time</I -></TT +>oplock break wait time</VAR ></A ></P ></LI @@ -2257,11 +2029,9 @@ CLASS="PARAMETER" ><P ><A HREF="#OSLEVEL" -><TT +><VAR CLASS="PARAMETER" -><I ->os level</I -></TT +>os level</VAR ></A ></P ></LI @@ -2269,11 +2039,9 @@ CLASS="PARAMETER" ><P ><A HREF="#OS2DRIVERMAP" -><TT +><VAR CLASS="PARAMETER" -><I ->os2 driver map</I -></TT +>os2 driver map</VAR ></A ></P ></LI @@ -2281,11 +2049,9 @@ CLASS="PARAMETER" ><P ><A HREF="#PAMPASSWORDCHANGE" -><TT +><VAR CLASS="PARAMETER" -><I ->pam password change</I -></TT +>pam password change</VAR ></A ></P ></LI @@ -2293,11 +2059,9 @@ CLASS="PARAMETER" ><P ><A HREF="#PANICACTION" -><TT +><VAR CLASS="PARAMETER" -><I ->panic action</I -></TT +>panic action</VAR ></A ></P ></LI @@ -2305,11 +2069,9 @@ CLASS="PARAMETER" ><P ><A HREF="#PARANOIDSERVERSECURITY" -><TT +><VAR CLASS="PARAMETER" -><I ->paranoid server security</I -></TT +>paranoid server security</VAR ></A ></P ></LI @@ -2317,11 +2079,9 @@ CLASS="PARAMETER" ><P ><A HREF="#PASSDBBACKEND" -><TT +><VAR CLASS="PARAMETER" -><I ->passdb backend</I -></TT +>passdb backend</VAR ></A ></P ></LI @@ -2329,11 +2089,9 @@ CLASS="PARAMETER" ><P ><A HREF="#PASSWDCHAT" -><TT +><VAR CLASS="PARAMETER" -><I ->passwd chat</I -></TT +>passwd chat</VAR ></A ></P ></LI @@ -2341,11 +2099,9 @@ CLASS="PARAMETER" ><P ><A HREF="#PASSWDCHATDEBUG" -><TT +><VAR CLASS="PARAMETER" -><I ->passwd chat debug</I -></TT +>passwd chat debug</VAR ></A ></P ></LI @@ -2353,11 +2109,9 @@ CLASS="PARAMETER" ><P ><A HREF="#PASSWDPROGRAM" -><TT +><VAR CLASS="PARAMETER" -><I ->passwd program</I -></TT +>passwd program</VAR ></A ></P ></LI @@ -2365,11 +2119,9 @@ CLASS="PARAMETER" ><P ><A HREF="#PASSWORDLEVEL" -><TT +><VAR CLASS="PARAMETER" -><I ->password level</I -></TT +>password level</VAR ></A ></P ></LI @@ -2377,11 +2129,9 @@ CLASS="PARAMETER" ><P ><A HREF="#PASSWORDSERVER" -><TT +><VAR CLASS="PARAMETER" -><I ->password server</I -></TT +>password server</VAR ></A ></P ></LI @@ -2389,11 +2139,9 @@ CLASS="PARAMETER" ><P ><A HREF="#PREFEREDMASTER" -><TT +><VAR CLASS="PARAMETER" -><I ->prefered master</I -></TT +>prefered master</VAR ></A ></P ></LI @@ -2401,11 +2149,9 @@ CLASS="PARAMETER" ><P ><A HREF="#PREFERREDMASTER" -><TT +><VAR CLASS="PARAMETER" -><I ->preferred master</I -></TT +>preferred master</VAR ></A ></P ></LI @@ -2413,11 +2159,9 @@ CLASS="PARAMETER" ><P ><A HREF="#PRELOAD" -><TT +><VAR CLASS="PARAMETER" -><I ->preload</I -></TT +>preload</VAR ></A ></P ></LI @@ -2425,11 +2169,9 @@ CLASS="PARAMETER" ><P ><A HREF="#PRINTCAP" -><TT +><VAR CLASS="PARAMETER" -><I ->printcap</I -></TT +>printcap</VAR ></A ></P ></LI @@ -2437,23 +2179,9 @@ CLASS="PARAMETER" ><P ><A HREF="#PRINTCAPNAME" -><TT +><VAR CLASS="PARAMETER" -><I ->printcap name</I -></TT -></A -></P -></LI -><LI -><P -><A -HREF="#PRINTERDRIVERFILE" -><TT -CLASS="PARAMETER" -><I ->printer driver file</I -></TT +>printcap name</VAR ></A ></P ></LI @@ -2461,11 +2189,9 @@ CLASS="PARAMETER" ><P ><A HREF="#PRIVATEDIR" -><TT +><VAR CLASS="PARAMETER" -><I ->private dir</I -></TT +>private dir</VAR ></A ></P ></LI @@ -2473,11 +2199,9 @@ CLASS="PARAMETER" ><P ><A HREF="#PROTOCOL" -><TT +><VAR CLASS="PARAMETER" -><I ->protocol</I -></TT +>protocol</VAR ></A ></P ></LI @@ -2485,11 +2209,9 @@ CLASS="PARAMETER" ><P ><A HREF="#READBMPX" -><TT +><VAR CLASS="PARAMETER" -><I ->read bmpx</I -></TT +>read bmpx</VAR ></A ></P ></LI @@ -2497,11 +2219,9 @@ CLASS="PARAMETER" ><P ><A HREF="#READRAW" -><TT +><VAR CLASS="PARAMETER" -><I ->read raw</I -></TT +>read raw</VAR ></A ></P ></LI @@ -2509,11 +2229,9 @@ CLASS="PARAMETER" ><P ><A HREF="#READSIZE" -><TT +><VAR CLASS="PARAMETER" -><I ->read size</I -></TT +>read size</VAR ></A ></P ></LI @@ -2521,11 +2239,9 @@ CLASS="PARAMETER" ><P ><A HREF="#REALM" -><TT +><VAR CLASS="PARAMETER" -><I ->realm</I -></TT +>realm</VAR ></A ></P ></LI @@ -2533,11 +2249,9 @@ CLASS="PARAMETER" ><P ><A HREF="#REMOTEANNOUNCE" -><TT +><VAR CLASS="PARAMETER" -><I ->remote announce</I -></TT +>remote announce</VAR ></A ></P ></LI @@ -2545,11 +2259,9 @@ CLASS="PARAMETER" ><P ><A HREF="#REMOTEBROWSESYNC" -><TT +><VAR CLASS="PARAMETER" -><I ->remote browse sync</I -></TT +>remote browse sync</VAR ></A ></P ></LI @@ -2557,11 +2269,9 @@ CLASS="PARAMETER" ><P ><A HREF="#RESTRICTANONYMOUS" -><TT +><VAR CLASS="PARAMETER" -><I ->restrict anonymous</I -></TT +>restrict anonymous</VAR ></A ></P ></LI @@ -2569,11 +2279,9 @@ CLASS="PARAMETER" ><P ><A HREF="#ROOT" -><TT +><VAR CLASS="PARAMETER" -><I ->root</I -></TT +>root</VAR ></A ></P ></LI @@ -2581,11 +2289,9 @@ CLASS="PARAMETER" ><P ><A HREF="#ROOTDIR" -><TT +><VAR CLASS="PARAMETER" -><I ->root dir</I -></TT +>root dir</VAR ></A ></P ></LI @@ -2593,11 +2299,9 @@ CLASS="PARAMETER" ><P ><A HREF="#ROOTDIRECTORY" -><TT +><VAR CLASS="PARAMETER" -><I ->root directory</I -></TT +>root directory</VAR ></A ></P ></LI @@ -2605,11 +2309,9 @@ CLASS="PARAMETER" ><P ><A HREF="#SECURITY" -><TT +><VAR CLASS="PARAMETER" -><I ->security</I -></TT +>security</VAR ></A ></P ></LI @@ -2617,11 +2319,9 @@ CLASS="PARAMETER" ><P ><A HREF="#SERVERSTRING" -><TT +><VAR CLASS="PARAMETER" -><I ->server string</I -></TT +>server string</VAR ></A ></P ></LI @@ -2629,11 +2329,9 @@ CLASS="PARAMETER" ><P ><A HREF="#SHOWADDPRINTERWIZARD" -><TT +><VAR CLASS="PARAMETER" -><I ->show add printer wizard</I -></TT +>show add printer wizard</VAR ></A ></P ></LI @@ -2641,11 +2339,9 @@ CLASS="PARAMETER" ><P ><A HREF="#SHUTDOWNSCRIPT" -><TT +><VAR CLASS="PARAMETER" -><I ->shutdown script</I -></TT +>shutdown script</VAR ></A ></P ></LI @@ -2653,11 +2349,9 @@ CLASS="PARAMETER" ><P ><A HREF="#SMBPASSWDFILE" -><TT +><VAR CLASS="PARAMETER" -><I ->smb passwd file</I -></TT +>smb passwd file</VAR ></A ></P ></LI @@ -2665,11 +2359,9 @@ CLASS="PARAMETER" ><P ><A HREF="#SMBPORTS" -><TT +><VAR CLASS="PARAMETER" -><I ->smb ports</I -></TT +>smb ports</VAR ></A ></P ></LI @@ -2677,11 +2369,9 @@ CLASS="PARAMETER" ><P ><A HREF="#SOCKETADDRESS" -><TT +><VAR CLASS="PARAMETER" -><I ->socket address</I -></TT +>socket address</VAR ></A ></P ></LI @@ -2689,11 +2379,9 @@ CLASS="PARAMETER" ><P ><A HREF="#SOCKETOPTIONS" -><TT +><VAR CLASS="PARAMETER" -><I ->socket options</I -></TT +>socket options</VAR ></A ></P ></LI @@ -2701,11 +2389,9 @@ CLASS="PARAMETER" ><P ><A HREF="#SOURCEENVIRONMENT" -><TT +><VAR CLASS="PARAMETER" -><I ->source environment</I -></TT +>source environment</VAR ></A ></P ></LI @@ -2713,11 +2399,9 @@ CLASS="PARAMETER" ><P ><A HREF="#SPNEGO" -><TT +><VAR CLASS="PARAMETER" -><I ->use spnego</I -></TT +>use spnego</VAR ></A ></P ></LI @@ -2725,11 +2409,9 @@ CLASS="PARAMETER" ><P ><A HREF="#STATCACHE" -><TT +><VAR CLASS="PARAMETER" -><I ->stat cache</I -></TT +>stat cache</VAR ></A ></P ></LI @@ -2737,11 +2419,9 @@ CLASS="PARAMETER" ><P ><A HREF="#STATCACHESIZE" -><TT +><VAR CLASS="PARAMETER" -><I ->stat cache size</I -></TT +>stat cache size</VAR ></A ></P ></LI @@ -2749,11 +2429,9 @@ CLASS="PARAMETER" ><P ><A HREF="#STRIPDOT" -><TT +><VAR CLASS="PARAMETER" -><I ->strip dot</I -></TT +>strip dot</VAR ></A ></P ></LI @@ -2761,11 +2439,9 @@ CLASS="PARAMETER" ><P ><A HREF="#SYSLOG" -><TT +><VAR CLASS="PARAMETER" -><I ->syslog</I -></TT +>syslog</VAR ></A ></P ></LI @@ -2773,11 +2449,9 @@ CLASS="PARAMETER" ><P ><A HREF="#SYSLOGONLY" -><TT +><VAR CLASS="PARAMETER" -><I ->syslog only</I -></TT +>syslog only</VAR ></A ></P ></LI @@ -2785,11 +2459,9 @@ CLASS="PARAMETER" ><P ><A HREF="#TEMPLATEHOMEDIR" -><TT +><VAR CLASS="PARAMETER" -><I ->template homedir</I -></TT +>template homedir</VAR ></A ></P ></LI @@ -2797,11 +2469,9 @@ CLASS="PARAMETER" ><P ><A HREF="#TEMPLATESHELL" -><TT +><VAR CLASS="PARAMETER" -><I ->template shell</I -></TT +>template shell</VAR ></A ></P ></LI @@ -2809,11 +2479,9 @@ CLASS="PARAMETER" ><P ><A HREF="#TIMEOFFSET" -><TT +><VAR CLASS="PARAMETER" -><I ->time offset</I -></TT +>time offset</VAR ></A ></P ></LI @@ -2821,11 +2489,9 @@ CLASS="PARAMETER" ><P ><A HREF="#TIMESERVER" -><TT +><VAR CLASS="PARAMETER" -><I ->time server</I -></TT +>time server</VAR ></A ></P ></LI @@ -2833,11 +2499,9 @@ CLASS="PARAMETER" ><P ><A HREF="#TIMESTAMPLOGS" -><TT +><VAR CLASS="PARAMETER" -><I ->timestamp logs</I -></TT +>timestamp logs</VAR ></A ></P ></LI @@ -2845,11 +2509,9 @@ CLASS="PARAMETER" ><P ><A HREF="#TOTALPRINTJOBS" -><TT +><VAR CLASS="PARAMETER" -><I ->total print jobs</I -></TT +>total print jobs</VAR ></A ></P ></LI @@ -2857,11 +2519,9 @@ CLASS="PARAMETER" ><P ><A HREF="#UNICODE" -><TT +><VAR CLASS="PARAMETER" -><I ->unicode</I -></TT +>unicode</VAR ></A ></P ></LI @@ -2869,11 +2529,9 @@ CLASS="PARAMETER" ><P ><A HREF="#UNIXCHARSET" -><TT +><VAR CLASS="PARAMETER" -><I ->unix charset</I -></TT +>unix charset</VAR ></A ></P ></LI @@ -2881,11 +2539,9 @@ CLASS="PARAMETER" ><P ><A HREF="#UNIXEXTENSIONS" -><TT +><VAR CLASS="PARAMETER" -><I ->unix extensions</I -></TT +>unix extensions</VAR ></A ></P ></LI @@ -2893,11 +2549,9 @@ CLASS="PARAMETER" ><P ><A HREF="#UNIXPASSWORDSYNC" -><TT +><VAR CLASS="PARAMETER" -><I ->unix password sync</I -></TT +>unix password sync</VAR ></A ></P ></LI @@ -2905,11 +2559,9 @@ CLASS="PARAMETER" ><P ><A HREF="#UPDATEENCRYPTED" -><TT +><VAR CLASS="PARAMETER" -><I ->update encrypted</I -></TT +>update encrypted</VAR ></A ></P ></LI @@ -2917,23 +2569,9 @@ CLASS="PARAMETER" ><P ><A HREF="#USEMMAP" -><TT +><VAR CLASS="PARAMETER" -><I ->use mmap</I -></TT -></A -></P -></LI -><LI -><P -><A -HREF="#USERHOSTS" -><TT -CLASS="PARAMETER" -><I ->use rhosts</I -></TT +>use mmap</VAR ></A ></P ></LI @@ -2941,11 +2579,9 @@ CLASS="PARAMETER" ><P ><A HREF="#USESENDFILE" -><TT +><VAR CLASS="PARAMETER" -><I ->use sendfile</I -></TT +>use sendfile</VAR ></A ></P ></LI @@ -2953,11 +2589,9 @@ CLASS="PARAMETER" ><P ><A HREF="#USERNAMELEVEL" -><TT +><VAR CLASS="PARAMETER" -><I ->username level</I -></TT +>username level</VAR ></A ></P ></LI @@ -2965,11 +2599,9 @@ CLASS="PARAMETER" ><P ><A HREF="#USERNAMEMAP" -><TT +><VAR CLASS="PARAMETER" -><I ->username map</I -></TT +>username map</VAR ></A ></P ></LI @@ -2977,11 +2609,9 @@ CLASS="PARAMETER" ><P ><A HREF="#UTMP" -><TT +><VAR CLASS="PARAMETER" -><I ->utmp</I -></TT +>utmp</VAR ></A ></P ></LI @@ -2989,11 +2619,9 @@ CLASS="PARAMETER" ><P ><A HREF="#UTMPDIRECTORY" -><TT +><VAR CLASS="PARAMETER" -><I ->utmp directory</I -></TT +>utmp directory</VAR ></A ></P ></LI @@ -3001,11 +2629,9 @@ CLASS="PARAMETER" ><P ><A HREF="#WTMPDIRECTORY" -><TT +><VAR CLASS="PARAMETER" -><I ->wtmp directory</I -></TT +>wtmp directory</VAR ></A ></P ></LI @@ -3013,11 +2639,9 @@ CLASS="PARAMETER" ><P ><A HREF="#WINBINDCACHETIME" -><TT +><VAR CLASS="PARAMETER" -><I ->winbind cache time</I -></TT +>winbind cache time</VAR ></A ></P ></LI @@ -3025,11 +2649,9 @@ CLASS="PARAMETER" ><P ><A HREF="#WINBINDENUMUSERS" -><TT +><VAR CLASS="PARAMETER" -><I ->winbind enum users</I -></TT +>winbind enum users</VAR ></A ></P ></LI @@ -3037,11 +2659,9 @@ CLASS="PARAMETER" ><P ><A HREF="#WINBINDENUMGROUPS" -><TT +><VAR CLASS="PARAMETER" -><I ->winbind enum groups</I -></TT +>winbind enum groups</VAR ></A ></P ></LI @@ -3049,11 +2669,9 @@ CLASS="PARAMETER" ><P ><A HREF="#WINBINDGID" -><TT +><VAR CLASS="PARAMETER" -><I ->winbind gid</I -></TT +>winbind gid</VAR ></A ></P ></LI @@ -3061,11 +2679,9 @@ CLASS="PARAMETER" ><P ><A HREF="#WINBINDSEPARATOR" -><TT +><VAR CLASS="PARAMETER" -><I ->winbind separator</I -></TT +>winbind separator</VAR ></A ></P ></LI @@ -3073,11 +2689,9 @@ CLASS="PARAMETER" ><P ><A HREF="#WINBINDUID" -><TT +><VAR CLASS="PARAMETER" -><I ->winbind uid</I -></TT +>winbind uid</VAR ></A ></P ></LI @@ -3085,11 +2699,9 @@ CLASS="PARAMETER" ><P ><A HREF="#WINBINDUSEDEFAULTDOMAIN" -><TT +><VAR CLASS="PARAMETER" -><I ->winbind use default domain</I -></TT +>winbind use default domain</VAR ></A ></P ></LI @@ -3097,11 +2709,9 @@ CLASS="PARAMETER" ><P ><A HREF="#WINSHOOK" -><TT +><VAR CLASS="PARAMETER" -><I ->wins hook</I -></TT +>wins hook</VAR ></A ></P ></LI @@ -3109,11 +2719,9 @@ CLASS="PARAMETER" ><P ><A HREF="#WINSPARTNERS" -><TT +><VAR CLASS="PARAMETER" -><I ->wins partners</I -></TT +>wins partners</VAR ></A ></P ></LI @@ -3121,11 +2729,9 @@ CLASS="PARAMETER" ><P ><A HREF="#WINSPROXY" -><TT +><VAR CLASS="PARAMETER" -><I ->wins proxy</I -></TT +>wins proxy</VAR ></A ></P ></LI @@ -3133,11 +2739,9 @@ CLASS="PARAMETER" ><P ><A HREF="#WINSSERVER" -><TT +><VAR CLASS="PARAMETER" -><I ->wins server</I -></TT +>wins server</VAR ></A ></P ></LI @@ -3145,11 +2749,9 @@ CLASS="PARAMETER" ><P ><A HREF="#WINSSUPPORT" -><TT +><VAR CLASS="PARAMETER" -><I ->wins support</I -></TT +>wins support</VAR ></A ></P ></LI @@ -3157,11 +2759,9 @@ CLASS="PARAMETER" ><P ><A HREF="#WORKGROUP" -><TT +><VAR CLASS="PARAMETER" -><I ->workgroup</I -></TT +>workgroup</VAR ></A ></P ></LI @@ -3169,11 +2769,9 @@ CLASS="PARAMETER" ><P ><A HREF="#WRITERAW" -><TT +><VAR CLASS="PARAMETER" -><I ->write raw</I -></TT +>write raw</VAR ></A ></P ></LI @@ -3182,7 +2780,7 @@ CLASS="PARAMETER" ><DIV CLASS="REFSECT1" ><A -NAME="AEN1022" +NAME="AEN1018" ></A ><H2 >COMPLETE LIST OF SERVICE PARAMETERS</H2 @@ -3196,11 +2794,9 @@ NAME="AEN1022" ><P ><A HREF="#ADMINUSERS" -><TT +><VAR CLASS="PARAMETER" -><I ->admin users</I -></TT +>admin users</VAR ></A ></P ></LI @@ -3208,11 +2804,9 @@ CLASS="PARAMETER" ><P ><A HREF="#ALLOWHOSTS" -><TT +><VAR CLASS="PARAMETER" -><I ->allow hosts</I -></TT +>allow hosts</VAR ></A ></P ></LI @@ -3220,11 +2814,9 @@ CLASS="PARAMETER" ><P ><A HREF="#AVAILABLE" -><TT +><VAR CLASS="PARAMETER" -><I ->available</I -></TT +>available</VAR ></A ></P ></LI @@ -3232,11 +2824,9 @@ CLASS="PARAMETER" ><P ><A HREF="#BLOCKINGLOCKS" -><TT +><VAR CLASS="PARAMETER" -><I ->blocking locks</I -></TT +>blocking locks</VAR ></A ></P ></LI @@ -3244,11 +2834,9 @@ CLASS="PARAMETER" ><P ><A HREF="#BLOCKSIZE" -><TT +><VAR CLASS="PARAMETER" -><I ->block size</I -></TT +>block size</VAR ></A ></P ></LI @@ -3256,11 +2844,9 @@ CLASS="PARAMETER" ><P ><A HREF="#BROWSABLE" -><TT +><VAR CLASS="PARAMETER" -><I ->browsable</I -></TT +>browsable</VAR ></A ></P ></LI @@ -3268,11 +2854,9 @@ CLASS="PARAMETER" ><P ><A HREF="#BROWSEABLE" -><TT +><VAR CLASS="PARAMETER" -><I ->browseable</I -></TT +>browseable</VAR ></A ></P ></LI @@ -3280,11 +2864,9 @@ CLASS="PARAMETER" ><P ><A HREF="#CASESENSITIVE" -><TT +><VAR CLASS="PARAMETER" -><I ->case sensitive</I -></TT +>case sensitive</VAR ></A ></P ></LI @@ -3292,11 +2874,9 @@ CLASS="PARAMETER" ><P ><A HREF="#CASESIGNAMES" -><TT +><VAR CLASS="PARAMETER" -><I ->casesignames</I -></TT +>casesignames</VAR ></A ></P ></LI @@ -3304,11 +2884,9 @@ CLASS="PARAMETER" ><P ><A HREF="#COMMENT" -><TT +><VAR CLASS="PARAMETER" -><I ->comment</I -></TT +>comment</VAR ></A ></P ></LI @@ -3316,11 +2894,9 @@ CLASS="PARAMETER" ><P ><A HREF="#COPY" -><TT +><VAR CLASS="PARAMETER" -><I ->copy</I -></TT +>copy</VAR ></A ></P ></LI @@ -3328,11 +2904,9 @@ CLASS="PARAMETER" ><P ><A HREF="#CREATEMASK" -><TT +><VAR CLASS="PARAMETER" -><I ->create mask</I -></TT +>create mask</VAR ></A ></P ></LI @@ -3340,11 +2914,9 @@ CLASS="PARAMETER" ><P ><A HREF="#CREATEMODE" -><TT +><VAR CLASS="PARAMETER" -><I ->create mode</I -></TT +>create mode</VAR ></A ></P ></LI @@ -3352,11 +2924,9 @@ CLASS="PARAMETER" ><P ><A HREF="#CSCPOLICY" -><TT +><VAR CLASS="PARAMETER" -><I ->csc policy</I -></TT +>csc policy</VAR ></A ></P ></LI @@ -3364,11 +2934,9 @@ CLASS="PARAMETER" ><P ><A HREF="#DEFAULTCASE" -><TT +><VAR CLASS="PARAMETER" -><I ->default case</I -></TT +>default case</VAR ></A ></P ></LI @@ -3376,11 +2944,9 @@ CLASS="PARAMETER" ><P ><A HREF="#DEFAULTDEVMODE" -><TT +><VAR CLASS="PARAMETER" -><I ->default devmode</I -></TT +>default devmode</VAR ></A ></P ></LI @@ -3388,11 +2954,9 @@ CLASS="PARAMETER" ><P ><A HREF="#DELETEREADONLY" -><TT +><VAR CLASS="PARAMETER" -><I ->delete readonly</I -></TT +>delete readonly</VAR ></A ></P ></LI @@ -3400,11 +2964,9 @@ CLASS="PARAMETER" ><P ><A HREF="#DELETEVETOFILES" -><TT +><VAR CLASS="PARAMETER" -><I ->delete veto files</I -></TT +>delete veto files</VAR ></A ></P ></LI @@ -3412,11 +2974,9 @@ CLASS="PARAMETER" ><P ><A HREF="#DENYHOSTS" -><TT +><VAR CLASS="PARAMETER" -><I ->deny hosts</I -></TT +>deny hosts</VAR ></A ></P ></LI @@ -3424,11 +2984,9 @@ CLASS="PARAMETER" ><P ><A HREF="#DIRECTORY" -><TT +><VAR CLASS="PARAMETER" -><I ->directory</I -></TT +>directory</VAR ></A ></P ></LI @@ -3436,11 +2994,9 @@ CLASS="PARAMETER" ><P ><A HREF="#DIRECTORYMASK" -><TT +><VAR CLASS="PARAMETER" -><I ->directory mask</I -></TT +>directory mask</VAR ></A ></P ></LI @@ -3448,11 +3004,9 @@ CLASS="PARAMETER" ><P ><A HREF="#DIRECTORYMODE" -><TT +><VAR CLASS="PARAMETER" -><I ->directory mode</I -></TT +>directory mode</VAR ></A ></P ></LI @@ -3460,11 +3014,9 @@ CLASS="PARAMETER" ><P ><A HREF="#DIRECTORYSECURITYMASK" -><TT +><VAR CLASS="PARAMETER" -><I ->directory security mask</I -></TT +>directory security mask</VAR ></A ></P ></LI @@ -3472,11 +3024,9 @@ CLASS="PARAMETER" ><P ><A HREF="#DONTDESCEND" -><TT +><VAR CLASS="PARAMETER" -><I ->dont descend</I -></TT +>dont descend</VAR ></A ></P ></LI @@ -3484,11 +3034,9 @@ CLASS="PARAMETER" ><P ><A HREF="#DOSFILEMODE" -><TT +><VAR CLASS="PARAMETER" -><I ->dos filemode</I -></TT +>dos filemode</VAR ></A ></P ></LI @@ -3496,11 +3044,9 @@ CLASS="PARAMETER" ><P ><A HREF="#DOSFILETIMERESOLUTION" -><TT +><VAR CLASS="PARAMETER" -><I ->dos filetime resolution</I -></TT +>dos filetime resolution</VAR ></A ></P ></LI @@ -3508,11 +3054,9 @@ CLASS="PARAMETER" ><P ><A HREF="#DOSFILETIMES" -><TT +><VAR CLASS="PARAMETER" -><I ->dos filetimes</I -></TT +>dos filetimes</VAR ></A ></P ></LI @@ -3520,11 +3064,9 @@ CLASS="PARAMETER" ><P ><A HREF="#EXEC" -><TT +><VAR CLASS="PARAMETER" -><I ->exec</I -></TT +>exec</VAR ></A ></P ></LI @@ -3532,11 +3074,9 @@ CLASS="PARAMETER" ><P ><A HREF="#FAKEDIRECTORYCREATETIMES" -><TT +><VAR CLASS="PARAMETER" -><I ->fake directory create times</I -></TT +>fake directory create times</VAR ></A ></P ></LI @@ -3544,11 +3084,9 @@ CLASS="PARAMETER" ><P ><A HREF="#FAKEOPLOCKS" -><TT +><VAR CLASS="PARAMETER" -><I ->fake oplocks</I -></TT +>fake oplocks</VAR ></A ></P ></LI @@ -3556,11 +3094,9 @@ CLASS="PARAMETER" ><P ><A HREF="#FOLLOWSYMLINKS" -><TT +><VAR CLASS="PARAMETER" -><I ->follow symlinks</I -></TT +>follow symlinks</VAR ></A ></P ></LI @@ -3568,11 +3104,9 @@ CLASS="PARAMETER" ><P ><A HREF="#FORCECREATEMODE" -><TT +><VAR CLASS="PARAMETER" -><I ->force create mode</I -></TT +>force create mode</VAR ></A ></P ></LI @@ -3580,11 +3114,9 @@ CLASS="PARAMETER" ><P ><A HREF="#FORCEDIRECTORYMODE" -><TT +><VAR CLASS="PARAMETER" -><I ->force directory mode</I -></TT +>force directory mode</VAR ></A ></P ></LI @@ -3592,11 +3124,9 @@ CLASS="PARAMETER" ><P ><A HREF="#FORCEDIRECTORYSECURITYMODE" -><TT +><VAR CLASS="PARAMETER" -><I ->force directory security mode</I -></TT +>force directory security mode</VAR ></A ></P ></LI @@ -3604,11 +3134,9 @@ CLASS="PARAMETER" ><P ><A HREF="#FORCEGROUP" -><TT +><VAR CLASS="PARAMETER" -><I ->force group</I -></TT +>force group</VAR ></A ></P ></LI @@ -3616,11 +3144,9 @@ CLASS="PARAMETER" ><P ><A HREF="#FORCESECURITYMODE" -><TT +><VAR CLASS="PARAMETER" -><I ->force security mode</I -></TT +>force security mode</VAR ></A ></P ></LI @@ -3628,11 +3154,9 @@ CLASS="PARAMETER" ><P ><A HREF="#FORCEUSER" -><TT +><VAR CLASS="PARAMETER" -><I ->force user</I -></TT +>force user</VAR ></A ></P ></LI @@ -3640,11 +3164,9 @@ CLASS="PARAMETER" ><P ><A HREF="#FSTYPE" -><TT +><VAR CLASS="PARAMETER" -><I ->fstype</I -></TT +>fstype</VAR ></A ></P ></LI @@ -3652,11 +3174,9 @@ CLASS="PARAMETER" ><P ><A HREF="#GROUP" -><TT +><VAR CLASS="PARAMETER" -><I ->group</I -></TT +>group</VAR ></A ></P ></LI @@ -3664,11 +3184,9 @@ CLASS="PARAMETER" ><P ><A HREF="#GUESTACCOUNT" -><TT +><VAR CLASS="PARAMETER" -><I ->guest account</I -></TT +>guest account</VAR ></A ></P ></LI @@ -3676,11 +3194,9 @@ CLASS="PARAMETER" ><P ><A HREF="#GUESTOK" -><TT +><VAR CLASS="PARAMETER" -><I ->guest ok</I -></TT +>guest ok</VAR ></A ></P ></LI @@ -3688,11 +3204,9 @@ CLASS="PARAMETER" ><P ><A HREF="#GUESTONLY" -><TT +><VAR CLASS="PARAMETER" -><I ->guest only</I -></TT +>guest only</VAR ></A ></P ></LI @@ -3700,11 +3214,9 @@ CLASS="PARAMETER" ><P ><A HREF="#HIDEDOTFILES" -><TT +><VAR CLASS="PARAMETER" -><I ->hide dot files</I -></TT +>hide dot files</VAR ></A ></P ></LI @@ -3712,11 +3224,9 @@ CLASS="PARAMETER" ><P ><A HREF="#HIDEFILES" -><TT +><VAR CLASS="PARAMETER" -><I ->hide files</I -></TT +>hide files</VAR ></A ></P ></LI @@ -3724,11 +3234,9 @@ CLASS="PARAMETER" ><P ><A HREF="#HOSTSALLOW" -><TT +><VAR CLASS="PARAMETER" -><I ->hosts allow</I -></TT +>hosts allow</VAR ></A ></P ></LI @@ -3736,11 +3244,9 @@ CLASS="PARAMETER" ><P ><A HREF="#HOSTSDENY" -><TT +><VAR CLASS="PARAMETER" -><I ->hosts deny</I -></TT +>hosts deny</VAR ></A ></P ></LI @@ -3748,11 +3254,9 @@ CLASS="PARAMETER" ><P ><A HREF="#INCLUDE" -><TT +><VAR CLASS="PARAMETER" -><I ->include</I -></TT +>include</VAR ></A ></P ></LI @@ -3760,11 +3264,9 @@ CLASS="PARAMETER" ><P ><A HREF="#INHERITACLS" -><TT +><VAR CLASS="PARAMETER" -><I ->inherit acls</I -></TT +>inherit acls</VAR ></A ></P ></LI @@ -3772,11 +3274,9 @@ CLASS="PARAMETER" ><P ><A HREF="#INHERITPERMISSIONS" -><TT +><VAR CLASS="PARAMETER" -><I ->inherit permissions</I -></TT +>inherit permissions</VAR ></A ></P ></LI @@ -3784,11 +3284,9 @@ CLASS="PARAMETER" ><P ><A HREF="#INVALIDUSERS" -><TT +><VAR CLASS="PARAMETER" -><I ->invalid users</I -></TT +>invalid users</VAR ></A ></P ></LI @@ -3796,11 +3294,9 @@ CLASS="PARAMETER" ><P ><A HREF="#LEVEL2OPLOCKS" -><TT +><VAR CLASS="PARAMETER" -><I ->level2 oplocks</I -></TT +>level2 oplocks</VAR ></A ></P ></LI @@ -3808,11 +3304,9 @@ CLASS="PARAMETER" ><P ><A HREF="#LOCKING" -><TT +><VAR CLASS="PARAMETER" -><I ->locking</I -></TT +>locking</VAR ></A ></P ></LI @@ -3820,11 +3314,9 @@ CLASS="PARAMETER" ><P ><A HREF="#LPPAUSECOMMAND" -><TT +><VAR CLASS="PARAMETER" -><I ->lppause command</I -></TT +>lppause command</VAR ></A ></P ></LI @@ -3832,11 +3324,9 @@ CLASS="PARAMETER" ><P ><A HREF="#LPQCOMMAND" -><TT +><VAR CLASS="PARAMETER" -><I ->lpq command</I -></TT +>lpq command</VAR ></A ></P ></LI @@ -3844,11 +3334,9 @@ CLASS="PARAMETER" ><P ><A HREF="#LPRESUMECOMMAND" -><TT +><VAR CLASS="PARAMETER" -><I ->lpresume command</I -></TT +>lpresume command</VAR ></A ></P ></LI @@ -3856,11 +3344,9 @@ CLASS="PARAMETER" ><P ><A HREF="#LPRMCOMMAND" -><TT +><VAR CLASS="PARAMETER" -><I ->lprm command</I -></TT +>lprm command</VAR ></A ></P ></LI @@ -3868,11 +3354,9 @@ CLASS="PARAMETER" ><P ><A HREF="#MAGICOUTPUT" -><TT +><VAR CLASS="PARAMETER" -><I ->magic output</I -></TT +>magic output</VAR ></A ></P ></LI @@ -3880,11 +3364,9 @@ CLASS="PARAMETER" ><P ><A HREF="#MAGICSCRIPT" -><TT +><VAR CLASS="PARAMETER" -><I ->magic script</I -></TT +>magic script</VAR ></A ></P ></LI @@ -3892,11 +3374,9 @@ CLASS="PARAMETER" ><P ><A HREF="#MANGLECASE" -><TT +><VAR CLASS="PARAMETER" -><I ->mangle case</I -></TT +>mangle case</VAR ></A ></P ></LI @@ -3904,11 +3384,9 @@ CLASS="PARAMETER" ><P ><A HREF="#MANGLEDMAP" -><TT +><VAR CLASS="PARAMETER" -><I ->mangled map</I -></TT +>mangled map</VAR ></A ></P ></LI @@ -3916,11 +3394,9 @@ CLASS="PARAMETER" ><P ><A HREF="#MANGLEDNAMES" -><TT +><VAR CLASS="PARAMETER" -><I ->mangled names</I -></TT +>mangled names</VAR ></A ></P ></LI @@ -3928,11 +3404,9 @@ CLASS="PARAMETER" ><P ><A HREF="#MANGLINGCHAR" -><TT +><VAR CLASS="PARAMETER" -><I ->mangling char</I -></TT +>mangling char</VAR ></A ></P ></LI @@ -3940,11 +3414,9 @@ CLASS="PARAMETER" ><P ><A HREF="#MANGLINGMETHOD" -><TT +><VAR CLASS="PARAMETER" -><I ->mangling method</I -></TT +>mangling method</VAR ></A ></P ></LI @@ -3952,11 +3424,9 @@ CLASS="PARAMETER" ><P ><A HREF="#MAPARCHIVE" -><TT +><VAR CLASS="PARAMETER" -><I ->map archive</I -></TT +>map archive</VAR ></A ></P ></LI @@ -3964,11 +3434,9 @@ CLASS="PARAMETER" ><P ><A HREF="#MAPHIDDEN" -><TT +><VAR CLASS="PARAMETER" -><I ->map hidden</I -></TT +>map hidden</VAR ></A ></P ></LI @@ -3976,11 +3444,9 @@ CLASS="PARAMETER" ><P ><A HREF="#MAPSYSTEM" -><TT +><VAR CLASS="PARAMETER" -><I ->map system</I -></TT +>map system</VAR ></A ></P ></LI @@ -3988,11 +3454,9 @@ CLASS="PARAMETER" ><P ><A HREF="#MAXCONNECTIONS" -><TT +><VAR CLASS="PARAMETER" -><I ->max connections</I -></TT +>max connections</VAR ></A ></P ></LI @@ -4000,11 +3464,9 @@ CLASS="PARAMETER" ><P ><A HREF="#MAXPRINTJOBS" -><TT +><VAR CLASS="PARAMETER" -><I ->max print jobs</I -></TT +>max print jobs</VAR ></A ></P ></LI @@ -4012,11 +3474,9 @@ CLASS="PARAMETER" ><P ><A HREF="#MINPRINTSPACE" -><TT +><VAR CLASS="PARAMETER" -><I ->min print space</I -></TT +>min print space</VAR ></A ></P ></LI @@ -4024,11 +3484,9 @@ CLASS="PARAMETER" ><P ><A HREF="#MSDFSPROXY" -><TT +><VAR CLASS="PARAMETER" -><I ->msdfs proxy</I -></TT +>msdfs proxy</VAR ></A ></P ></LI @@ -4036,11 +3494,9 @@ CLASS="PARAMETER" ><P ><A HREF="#MSDFSROOT" -><TT +><VAR CLASS="PARAMETER" -><I ->msdfs root</I -></TT +>msdfs root</VAR ></A ></P ></LI @@ -4048,11 +3504,9 @@ CLASS="PARAMETER" ><P ><A HREF="#NTACLSUPPORT" -><TT +><VAR CLASS="PARAMETER" -><I ->nt acl support</I -></TT +>nt acl support</VAR ></A ></P ></LI @@ -4060,11 +3514,9 @@ CLASS="PARAMETER" ><P ><A HREF="#ONLYGUEST" -><TT +><VAR CLASS="PARAMETER" -><I ->only guest</I -></TT +>only guest</VAR ></A ></P ></LI @@ -4072,11 +3524,9 @@ CLASS="PARAMETER" ><P ><A HREF="#ONLYUSER" -><TT +><VAR CLASS="PARAMETER" -><I ->only user</I -></TT +>only user</VAR ></A ></P ></LI @@ -4084,11 +3534,9 @@ CLASS="PARAMETER" ><P ><A HREF="#OPLOCKCONTENTIONLIMIT" -><TT +><VAR CLASS="PARAMETER" -><I ->oplock contention limit</I -></TT +>oplock contention limit</VAR ></A ></P ></LI @@ -4096,11 +3544,9 @@ CLASS="PARAMETER" ><P ><A HREF="#OPLOCKS" -><TT +><VAR CLASS="PARAMETER" -><I ->oplocks</I -></TT +>oplocks</VAR ></A ></P ></LI @@ -4108,11 +3554,9 @@ CLASS="PARAMETER" ><P ><A HREF="#PATH" -><TT +><VAR CLASS="PARAMETER" -><I ->path</I -></TT +>path</VAR ></A ></P ></LI @@ -4120,11 +3564,9 @@ CLASS="PARAMETER" ><P ><A HREF="#POSIXLOCKING" -><TT +><VAR CLASS="PARAMETER" -><I ->posix locking</I -></TT +>posix locking</VAR ></A ></P ></LI @@ -4132,23 +3574,9 @@ CLASS="PARAMETER" ><P ><A HREF="#POSTEXEC" -><TT +><VAR CLASS="PARAMETER" -><I ->postexec</I -></TT -></A -></P -></LI -><LI -><P -><A -HREF="#POSTSCRIPT" -><TT -CLASS="PARAMETER" -><I ->postscript</I -></TT +>postexec</VAR ></A ></P ></LI @@ -4156,11 +3584,9 @@ CLASS="PARAMETER" ><P ><A HREF="#PREEXEC" -><TT +><VAR CLASS="PARAMETER" -><I ->preexec</I -></TT +>preexec</VAR ></A ></P ></LI @@ -4168,11 +3594,9 @@ CLASS="PARAMETER" ><P ><A HREF="#PREEXECCLOSE" -><TT +><VAR CLASS="PARAMETER" -><I ->preexec close</I -></TT +>preexec close</VAR ></A ></P ></LI @@ -4180,11 +3604,9 @@ CLASS="PARAMETER" ><P ><A HREF="#PRESERVECASE" -><TT +><VAR CLASS="PARAMETER" -><I ->preserve case</I -></TT +>preserve case</VAR ></A ></P ></LI @@ -4192,11 +3614,9 @@ CLASS="PARAMETER" ><P ><A HREF="#PRINTCOMMAND" -><TT +><VAR CLASS="PARAMETER" -><I ->print command</I -></TT +>print command</VAR ></A ></P ></LI @@ -4204,11 +3624,9 @@ CLASS="PARAMETER" ><P ><A HREF="#PRINTOK" -><TT +><VAR CLASS="PARAMETER" -><I ->print ok</I -></TT +>print ok</VAR ></A ></P ></LI @@ -4216,11 +3634,9 @@ CLASS="PARAMETER" ><P ><A HREF="#PRINTABLE" -><TT +><VAR CLASS="PARAMETER" -><I ->printable</I -></TT +>printable</VAR ></A ></P ></LI @@ -4228,11 +3644,9 @@ CLASS="PARAMETER" ><P ><A HREF="#PRINTER" -><TT +><VAR CLASS="PARAMETER" -><I ->printer</I -></TT +>printer</VAR ></A ></P ></LI @@ -4240,35 +3654,9 @@ CLASS="PARAMETER" ><P ><A HREF="#PRINTERADMIN" -><TT +><VAR CLASS="PARAMETER" -><I ->printer admin</I -></TT -></A -></P -></LI -><LI -><P -><A -HREF="#PRINTERDRIVER" -><TT -CLASS="PARAMETER" -><I ->printer driver</I -></TT -></A -></P -></LI -><LI -><P -><A -HREF="#PRINTERDRIVERLOCATION" -><TT -CLASS="PARAMETER" -><I ->printer driver location</I -></TT +>printer admin</VAR ></A ></P ></LI @@ -4276,11 +3664,9 @@ CLASS="PARAMETER" ><P ><A HREF="#PRINTERNAME" -><TT +><VAR CLASS="PARAMETER" -><I ->printer name</I -></TT +>printer name</VAR ></A ></P ></LI @@ -4288,11 +3674,9 @@ CLASS="PARAMETER" ><P ><A HREF="#PRINTING" -><TT +><VAR CLASS="PARAMETER" -><I ->printing</I -></TT +>printing</VAR ></A ></P ></LI @@ -4300,11 +3684,9 @@ CLASS="PARAMETER" ><P ><A HREF="#PUBLIC" -><TT +><VAR CLASS="PARAMETER" -><I ->public</I -></TT +>public</VAR ></A ></P ></LI @@ -4312,11 +3694,9 @@ CLASS="PARAMETER" ><P ><A HREF="#QUEUEPAUSECOMMAND" -><TT +><VAR CLASS="PARAMETER" -><I ->queuepause command</I -></TT +>queuepause command</VAR ></A ></P ></LI @@ -4324,11 +3704,9 @@ CLASS="PARAMETER" ><P ><A HREF="#QUEUERESUMECOMMAND" -><TT +><VAR CLASS="PARAMETER" -><I ->queueresume command</I -></TT +>queueresume command</VAR ></A ></P ></LI @@ -4336,11 +3714,9 @@ CLASS="PARAMETER" ><P ><A HREF="#READLIST" -><TT +><VAR CLASS="PARAMETER" -><I ->read list</I -></TT +>read list</VAR ></A ></P ></LI @@ -4348,11 +3724,9 @@ CLASS="PARAMETER" ><P ><A HREF="#READONLY" -><TT +><VAR CLASS="PARAMETER" -><I ->read only</I -></TT +>read only</VAR ></A ></P ></LI @@ -4360,11 +3734,9 @@ CLASS="PARAMETER" ><P ><A HREF="#ROOTPOSTEXEC" -><TT +><VAR CLASS="PARAMETER" -><I ->root postexec</I -></TT +>root postexec</VAR ></A ></P ></LI @@ -4372,11 +3744,9 @@ CLASS="PARAMETER" ><P ><A HREF="#ROOTPREEXEC" -><TT +><VAR CLASS="PARAMETER" -><I ->root preexec</I -></TT +>root preexec</VAR ></A ></P ></LI @@ -4384,11 +3754,9 @@ CLASS="PARAMETER" ><P ><A HREF="#ROOTPREEXECCLOSE" -><TT +><VAR CLASS="PARAMETER" -><I ->root preexec close</I -></TT +>root preexec close</VAR ></A ></P ></LI @@ -4396,11 +3764,9 @@ CLASS="PARAMETER" ><P ><A HREF="#SECURITYMASK" -><TT +><VAR CLASS="PARAMETER" -><I ->security mask</I -></TT +>security mask</VAR ></A ></P ></LI @@ -4408,11 +3774,9 @@ CLASS="PARAMETER" ><P ><A HREF="#SETDIRECTORY" -><TT +><VAR CLASS="PARAMETER" -><I ->set directory</I -></TT +>set directory</VAR ></A ></P ></LI @@ -4420,11 +3784,9 @@ CLASS="PARAMETER" ><P ><A HREF="#SHAREMODES" -><TT +><VAR CLASS="PARAMETER" -><I ->share modes</I -></TT +>share modes</VAR ></A ></P ></LI @@ -4432,11 +3794,9 @@ CLASS="PARAMETER" ><P ><A HREF="#SHORTPRESERVECASE" -><TT +><VAR CLASS="PARAMETER" -><I ->short preserve case</I -></TT +>short preserve case</VAR ></A ></P ></LI @@ -4444,11 +3804,9 @@ CLASS="PARAMETER" ><P ><A HREF="#STRICTALLOCATE" -><TT +><VAR CLASS="PARAMETER" -><I ->strict allocate</I -></TT +>strict allocate</VAR ></A ></P ></LI @@ -4456,11 +3814,9 @@ CLASS="PARAMETER" ><P ><A HREF="#STRICTLOCKING" -><TT +><VAR CLASS="PARAMETER" -><I ->strict locking</I -></TT +>strict locking</VAR ></A ></P ></LI @@ -4468,11 +3824,9 @@ CLASS="PARAMETER" ><P ><A HREF="#STRICTSYNC" -><TT +><VAR CLASS="PARAMETER" -><I ->strict sync</I -></TT +>strict sync</VAR ></A ></P ></LI @@ -4480,11 +3834,9 @@ CLASS="PARAMETER" ><P ><A HREF="#SYNCALWAYS" -><TT +><VAR CLASS="PARAMETER" -><I ->sync always</I -></TT +>sync always</VAR ></A ></P ></LI @@ -4492,11 +3844,9 @@ CLASS="PARAMETER" ><P ><A HREF="#USECLIENTDRIVER" -><TT +><VAR CLASS="PARAMETER" -><I ->use client driver</I -></TT +>use client driver</VAR ></A ></P ></LI @@ -4504,11 +3854,9 @@ CLASS="PARAMETER" ><P ><A HREF="#USER" -><TT +><VAR CLASS="PARAMETER" -><I ->user</I -></TT +>user</VAR ></A ></P ></LI @@ -4516,11 +3864,9 @@ CLASS="PARAMETER" ><P ><A HREF="#USERNAME" -><TT +><VAR CLASS="PARAMETER" -><I ->username</I -></TT +>username</VAR ></A ></P ></LI @@ -4528,11 +3874,9 @@ CLASS="PARAMETER" ><P ><A HREF="#USERS" -><TT +><VAR CLASS="PARAMETER" -><I ->users</I -></TT +>users</VAR ></A ></P ></LI @@ -4540,11 +3884,9 @@ CLASS="PARAMETER" ><P ><A HREF="#VALIDUSERS" -><TT +><VAR CLASS="PARAMETER" -><I ->valid users</I -></TT +>valid users</VAR ></A ></P ></LI @@ -4552,11 +3894,9 @@ CLASS="PARAMETER" ><P ><A HREF="#VETOFILES" -><TT +><VAR CLASS="PARAMETER" -><I ->veto files</I -></TT +>veto files</VAR ></A ></P ></LI @@ -4564,11 +3904,9 @@ CLASS="PARAMETER" ><P ><A HREF="#VETOOPLOCKFILES" -><TT +><VAR CLASS="PARAMETER" -><I ->veto oplock files</I -></TT +>veto oplock files</VAR ></A ></P ></LI @@ -4576,11 +3914,9 @@ CLASS="PARAMETER" ><P ><A HREF="#VFSPATH" -><TT +><VAR CLASS="PARAMETER" -><I ->vfs path</I -></TT +>vfs path</VAR ></A ></P ></LI @@ -4588,11 +3924,9 @@ CLASS="PARAMETER" ><P ><A HREF="#VFSOBJECT" -><TT +><VAR CLASS="PARAMETER" -><I ->vfs object</I -></TT +>vfs object</VAR ></A ></P ></LI @@ -4600,11 +3934,9 @@ CLASS="PARAMETER" ><P ><A HREF="#VFSOPTIONS" -><TT +><VAR CLASS="PARAMETER" -><I ->vfs options</I -></TT +>vfs options</VAR ></A ></P ></LI @@ -4612,11 +3944,9 @@ CLASS="PARAMETER" ><P ><A HREF="#VOLUME" -><TT +><VAR CLASS="PARAMETER" -><I ->volume</I -></TT +>volume</VAR ></A ></P ></LI @@ -4624,11 +3954,9 @@ CLASS="PARAMETER" ><P ><A HREF="#WIDELINKS" -><TT +><VAR CLASS="PARAMETER" -><I ->wide links</I -></TT +>wide links</VAR ></A ></P ></LI @@ -4636,11 +3964,9 @@ CLASS="PARAMETER" ><P ><A HREF="#WRITABLE" -><TT +><VAR CLASS="PARAMETER" -><I ->writable</I -></TT +>writable</VAR ></A ></P ></LI @@ -4648,11 +3974,9 @@ CLASS="PARAMETER" ><P ><A HREF="#WRITECACHESIZE" -><TT +><VAR CLASS="PARAMETER" -><I ->write cache size</I -></TT +>write cache size</VAR ></A ></P ></LI @@ -4660,11 +3984,9 @@ CLASS="PARAMETER" ><P ><A HREF="#WRITELIST" -><TT +><VAR CLASS="PARAMETER" -><I ->write list</I -></TT +>write list</VAR ></A ></P ></LI @@ -4672,11 +3994,9 @@ CLASS="PARAMETER" ><P ><A HREF="#WRITEOK" -><TT +><VAR CLASS="PARAMETER" -><I ->write ok</I -></TT +>write ok</VAR ></A ></P ></LI @@ -4684,11 +4004,9 @@ CLASS="PARAMETER" ><P ><A HREF="#WRITEABLE" -><TT +><VAR CLASS="PARAMETER" -><I ->writeable</I -></TT +>writeable</VAR ></A ></P ></LI @@ -4697,7 +4015,7 @@ CLASS="PARAMETER" ><DIV CLASS="REFSECT1" ><A -NAME="AEN1526" +NAME="AEN1510" ></A ><H2 >EXPLANATION OF EACH PARAMETER</H2 @@ -4729,11 +4047,9 @@ CLASS="REFENTRYTITLE" > that should stop a shutdown procedure issued by the <A HREF="#SHUTDOWNSCRIPT" -><TT +><VAR CLASS="PARAMETER" -><I ->shutdown script</I -></TT +>shutdown script</VAR ></A >.</P ><P @@ -4767,12 +4083,10 @@ 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 <TT + physically added to the underlying printing system. The <VAR CLASS="PARAMETER" -><I >add - printer command</I -></TT + printer command</VAR > 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 @@ -4788,11 +4102,9 @@ CLASS="REFENTRYTITLE" >(8)</SPAN >.</P ><P ->The <TT +>The <VAR CLASS="PARAMETER" -><I ->addprinter command</I -></TT +>addprinter command</VAR > is automatically invoked with the following parameter (in order):</P @@ -4801,56 +4113,44 @@ CLASS="PARAMETER" ><UL ><LI ><P -><TT +><VAR CLASS="PARAMETER" -><I ->printer name</I -></TT +>printer name</VAR ></P ></LI ><LI ><P -><TT +><VAR CLASS="PARAMETER" -><I ->share name</I -></TT +>share name</VAR ></P ></LI ><LI ><P -><TT +><VAR CLASS="PARAMETER" -><I ->port name</I -></TT +>port name</VAR ></P ></LI ><LI ><P -><TT +><VAR CLASS="PARAMETER" -><I ->driver name</I -></TT +>driver name</VAR ></P ></LI ><LI ><P -><TT +><VAR CLASS="PARAMETER" -><I ->location</I -></TT +>location</VAR ></P ></LI ><LI ><P -><TT +><VAR CLASS="PARAMETER" -><I ->Windows 9x driver location</I -></TT +>Windows 9x driver location</VAR > </P ></LI @@ -4862,11 +4162,9 @@ CLASS="PARAMETER" only. The remaining fields in the structure are generated from answers to the APW questions.</P ><P ->Once the <TT +>Once the <VAR CLASS="PARAMETER" -><I ->addprinter command</I -></TT +>addprinter command</VAR > has been executed, <B CLASS="COMMAND" @@ -4881,31 +4179,30 @@ 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" -><TT +><VAR CLASS="PARAMETER" -><I -> deleteprinter command</I -></TT +> deleteprinter command</VAR ></A >, <A HREF="#PRINTING" -><TT +><VAR CLASS="PARAMETER" -><I ->printing</I -></TT +>printing</VAR ></A >, <A HREF="#SHOWADDPRINTERWIZARD" -><TT +><VAR CLASS="PARAMETER" -><I >show add - printer wizard</I -></TT + printer wizard</VAR ></A ></P ><P @@ -4932,22 +4229,18 @@ NAME="ADDSHARECOMMAND" ><P >Samba 2.2.0 introduced the ability to dynamically add and delete shares via the Windows NT 4.0 Server Manager. The - <TT + <VAR CLASS="PARAMETER" -><I ->add share command</I -></TT +>add share command</VAR > 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 <TT + execute the <VAR CLASS="PARAMETER" -><I ->add share command</I -></TT +>add share command</VAR >, <B CLASS="COMMAND" >smbd</B @@ -4960,11 +4253,9 @@ CLASS="COMMAND" CLASS="COMMAND" >smbd</B > will automatically invoke the - <TT + <VAR CLASS="PARAMETER" -><I ->add share command</I -></TT +>add share command</VAR > with four parameters. </P ><P @@ -4972,11 +4263,9 @@ CLASS="PARAMETER" ><UL ><LI ><P -><TT +><VAR CLASS="PARAMETER" -><I ->configFile</I -></TT +>configFile</VAR > - the location of the global <TT CLASS="FILENAME" @@ -4986,33 +4275,27 @@ CLASS="FILENAME" ></LI ><LI ><P -><TT +><VAR CLASS="PARAMETER" -><I ->shareName</I -></TT +>shareName</VAR > - the name of the new share. </P ></LI ><LI ><P -><TT +><VAR CLASS="PARAMETER" -><I ->pathName</I -></TT +>pathName</VAR > - path to an **existing** directory on disk. </P ></LI ><LI ><P -><TT +><VAR CLASS="PARAMETER" -><I ->comment</I -></TT +>comment</VAR > - comment string to associate with the new share. </P @@ -5022,33 +4305,27 @@ CLASS="PARAMETER" > This parameter is only used for add file shares. To add printer shares, see the <A HREF="#ADDPRINTERCOMMAND" -><TT +><VAR CLASS="PARAMETER" -><I >addprinter - command</I -></TT + command</VAR ></A >. </P ><P > See also <A HREF="#CHANGESHARECOMMAND" -><TT +><VAR CLASS="PARAMETER" -><I >change share - command</I -></TT + command</VAR ></A >, <A HREF="#DELETESHARECOMMAND" -><TT +><VAR CLASS="PARAMETER" -><I >delete share - command</I -></TT + command</VAR ></A >. </P @@ -5089,7 +4366,7 @@ CLASS="REFENTRYTITLE" ><P >Default: <B CLASS="COMMAND" ->add machine script = <empty string> +>add machine script = <empty string> </B ></P ><P @@ -5172,24 +4449,18 @@ CLASS="emphasis" CLASS="EMPHASIS" >NOT</I ></SPAN -> be set to <TT +> be set to <VAR CLASS="PARAMETER" -><I ->security = share</I -></TT +>security = share</VAR > - and <TT + and <VAR CLASS="PARAMETER" -><I ->add user script</I -></TT +>add user script</VAR > must be set to a full pathname for a script that will create a UNIX - user given one argument of <TT + user given one argument of <VAR CLASS="PARAMETER" -><I ->%u</I -></TT +>%u</VAR >, which expands into the UNIX user name to create.</P ><P @@ -5200,11 +4471,9 @@ CLASS="CITEREFENTRY" CLASS="REFENTRYTITLE" >smbd</SPAN >(8)</SPAN -> contacts the <TT +> contacts the <VAR CLASS="PARAMETER" -><I ->password server</I -></TT +>password server</VAR > and attempts to authenticate the given user with the given password. If the authentication succeeds then <B @@ -5212,12 +4481,10 @@ 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 <TT + Windows user into. If this lookup fails, and <VAR CLASS="PARAMETER" -><I >add user script - </I -></TT + </VAR > is set then <B CLASS="COMMAND" >smbd</B @@ -5229,11 +4496,9 @@ CLASS="EMPHASIS" >AS ROOT</I ></SPAN >, expanding - any <TT + any <VAR CLASS="PARAMETER" -><I ->%u</I -></TT +>%u</VAR > argument to be the user name to create.</P ><P >If this script successfully creates the user then <B @@ -5246,35 +4511,29 @@ CLASS="COMMAND" ><P >See also <A HREF="#SECURITY" -><TT +><VAR CLASS="PARAMETER" -><I -> security</I -></TT +> security</VAR ></A >, <A HREF="#PASSWORDSERVER" -> <TT +> <VAR CLASS="PARAMETER" -><I ->password server</I -></TT +>password server</VAR ></A >, <A HREF="#DELETEUSERSCRIPT" -><TT +><VAR CLASS="PARAMETER" -><I >delete user - script</I -></TT + script</VAR ></A >.</P ><P >Default: <B CLASS="COMMAND" ->add user script = <empty string> +>add user script = <empty string> </B ></P ><P @@ -5306,11 +4565,9 @@ CLASS="REFENTRYTITLE" >(8)</SPAN > when a new group is requested. It will expand any - <TT + <VAR CLASS="PARAMETER" -><I ->%g</I -></TT +>%g</VAR > to the group name passed. This script is only useful for installations using the Windows NT domain administration tools. The script is @@ -5370,17 +4627,13 @@ CLASS="EMPHASIS" >AS ROOT</I ></SPAN >. - Any <TT + Any <VAR CLASS="PARAMETER" -><I ->%g</I -></TT +>%g</VAR > will be replaced with the group name and - any <TT + any <VAR CLASS="PARAMETER" -><I ->%u</I -></TT +>%u</VAR > will be replaced with the user name. </P ><P @@ -5403,11 +4656,9 @@ NAME="ALLOWHOSTS" ><P >Synonym for <A HREF="#HOSTSALLOW" -> <TT +> <VAR CLASS="PARAMETER" -><I ->hosts allow</I -></TT +>hosts allow</VAR ></A >.</P ></DD @@ -5452,19 +4703,17 @@ NAME="ALLOWTRUSTEDDOMAINS" ><P >This option only takes effect when the <A HREF="#SECURITY" -><TT +><VAR CLASS="PARAMETER" -><I ->security</I -></TT +>security</VAR ></A > option is set to - <TT + <CODE CLASS="CONSTANT" ->server</TT -> or <TT +>server</CODE +> or <CODE CLASS="CONSTANT" ->domain</TT +>domain</CODE >. If it is set to no, then attempts to connect to a resource from a domain or workgroup other than the one which <A @@ -5553,11 +4802,9 @@ NAME="AUTOSERVICES" ><P >This is a synonym for the <A HREF="#PRELOAD" -> <TT +> <VAR CLASS="PARAMETER" -><I ->preload</I -></TT +>preload</VAR ></A >.</P ></DD @@ -5575,11 +4822,9 @@ CLASS="COMMAND" > will use when authenticating a user. This option defaults to sensible values based on <A HREF="#SECURITY" -><TT +><VAR CLASS="PARAMETER" -><I -> security</I -></TT +> security</VAR ></A >. @@ -5590,7 +4835,7 @@ CLASS="PARAMETER" ><P >Default: <B CLASS="COMMAND" ->auth methods = <empty string></B +>auth methods = <empty string></B ></P ><P >Example: <B @@ -5606,11 +4851,9 @@ NAME="AVAILABLE" ><DD ><P >This parameter lets you "turn off" a service. If - <TT + <VAR CLASS="PARAMETER" -><I ->available = no</I -></TT +>available = no</VAR >, then <SPAN CLASS="emphasis" ><I @@ -5666,23 +4909,19 @@ CLASS="COMMAND" CLASS="COMMAND" >nmbd</B > will service - name requests on all of these sockets. If <TT + name requests on all of these sockets. If <VAR CLASS="PARAMETER" -><I >bind interfaces - only</I -></TT + only</VAR > 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 <TT + interfaces in the <VAR CLASS="PARAMETER" -><I ->interfaces</I -></TT +>interfaces</VAR > parameter list. As unicast packets are received on the other sockets it allows <B @@ -5690,11 +4929,9 @@ CLASS="COMMAND" >nmbd</B > to refuse to serve names to machines that send packets that arrive through any interfaces not listed in the - <TT + <VAR CLASS="PARAMETER" -><I ->interfaces</I -></TT +>interfaces</VAR > list. IP Source address spoofing does defeat this simple check, however, so it must not be used seriously as a security feature for <B @@ -5721,11 +4958,9 @@ 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 <TT +>If <VAR CLASS="PARAMETER" -><I ->bind interfaces only</I -></TT +>bind interfaces only</VAR > is set then unless the network address <SPAN CLASS="emphasis" @@ -5734,11 +4969,9 @@ CLASS="EMPHASIS" >127.0.0.1</I ></SPAN > is added - to the <TT + to the <VAR CLASS="PARAMETER" -><I ->interfaces</I -></TT +>interfaces</VAR > parameter list <SPAN CLASS="CITEREFENTRY" ><SPAN @@ -5765,11 +4998,9 @@ CLASS="EMPHASIS" ></SPAN > address as an SMB client to issue the password change request. If - <TT + <VAR CLASS="PARAMETER" -><I ->bind interfaces only</I -></TT +>bind interfaces only</VAR > is set then unless the network address <SPAN CLASS="emphasis" @@ -5778,11 +5009,9 @@ CLASS="EMPHASIS" >127.0.0.1</I ></SPAN > is added to the - <TT + <VAR CLASS="PARAMETER" -><I ->interfaces</I -></TT +>interfaces</VAR > parameter list then <B CLASS="COMMAND" > smbpasswd</B @@ -5797,22 +5026,16 @@ CLASS="CITEREFENTRY" CLASS="REFENTRYTITLE" >smbpasswd</SPAN >(8)</SPAN -> <TT +> <VAR CLASS="PARAMETER" -><I ->-r <TT +>-r <VAR CLASS="REPLACEABLE" -><I ->remote machine</I -></TT -></I -></TT +>remote machine</VAR +></VAR > - parameter, with <TT + parameter, with <VAR CLASS="REPLACEABLE" -><I ->remote machine</I -></TT +>remote machine</VAR > set to the IP name of the primary interface of the local host.</P ><P @@ -5887,9 +5110,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 <TT +>If this parameter is set to <CODE CLASS="CONSTANT" ->no</TT +>no</CODE >, then samba will behave as previous versions of Samba would and will fail the lock request immediately if the lock range @@ -5937,11 +5160,9 @@ NAME="BROWSABLE" ><P >See the <A HREF="#BROWSEABLE" -><TT +><VAR CLASS="PARAMETER" -><I -> browseable</I -></TT +> browseable</VAR ></A >.</P ></DD @@ -5963,9 +5184,9 @@ CLASS="REFENTRYTITLE" CLASS="COMMAND" >NetServerEnum</B > call. Normally - set to <TT + set to <CODE CLASS="CONSTANT" ->yes</TT +>yes</CODE >. You should never need to change this.</P ><P @@ -6036,12 +5257,10 @@ CLASS="REFENTRYTITLE" >smbd</SPAN >(8)</SPAN > daemon only performs such a scan - on each requested directory once every <TT + on each requested directory once every <VAR CLASS="PARAMETER" -><I >change notify - timeout</I -></TT + timeout</VAR > seconds.</P ><P >Default: <B @@ -6065,22 +5284,18 @@ NAME="CHANGESHARECOMMAND" ><P >Samba 2.2.0 introduced the ability to dynamically add and delete shares via the Windows NT 4.0 Server Manager. The - <TT + <VAR CLASS="PARAMETER" -><I ->change share command</I -></TT +>change share command</VAR > 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 <TT + execute the <VAR CLASS="PARAMETER" -><I ->change share command</I -></TT +>change share command</VAR >, <B CLASS="COMMAND" >smbd</B @@ -6093,11 +5308,9 @@ CLASS="COMMAND" CLASS="COMMAND" >smbd</B > will automatically invoke the - <TT + <VAR CLASS="PARAMETER" -><I ->change share command</I -></TT +>change share command</VAR > with four parameters. </P ><P @@ -6105,11 +5318,9 @@ CLASS="PARAMETER" ><UL ><LI ><P -><TT +><VAR CLASS="PARAMETER" -><I ->configFile</I -></TT +>configFile</VAR > - the location of the global <TT CLASS="FILENAME" @@ -6119,33 +5330,27 @@ CLASS="FILENAME" ></LI ><LI ><P -><TT +><VAR CLASS="PARAMETER" -><I ->shareName</I -></TT +>shareName</VAR > - the name of the new share. </P ></LI ><LI ><P -><TT +><VAR CLASS="PARAMETER" -><I ->pathName</I -></TT +>pathName</VAR > - path to an **existing** directory on disk. </P ></LI ><LI ><P -><TT +><VAR CLASS="PARAMETER" -><I ->comment</I -></TT +>comment</VAR > - comment string to associate with the new share. </P @@ -6158,21 +5363,17 @@ CLASS="PARAMETER" ><P > See also <A HREF="#ADDSHARECOMMAND" -><TT +><VAR CLASS="PARAMETER" -><I >add share - command</I -></TT + command</VAR ></A >, <A HREF="#DELETESHARECOMMAND" -><TT +><VAR CLASS="PARAMETER" -><I >delete - share command</I -></TT + share command</VAR ></A >. </P @@ -6208,11 +5409,9 @@ CLASS="COMMAND" >If you want to set the string that is displayed next to the machine name then see the <A HREF="#SERVERSTRING" -><TT +><VAR CLASS="PARAMETER" -><I -> server string</I -></TT +> server string</VAR ></A > parameter.</P ><P @@ -6301,11 +5500,9 @@ NAME="CREATEMASK" >A synonym for this parameter is <A HREF="#CREATEMODE" -><TT +><VAR CLASS="PARAMETER" -><I ->create mode</I -></TT +>create mode</VAR > </A >.</P @@ -6330,11 +5527,9 @@ CLASS="EMPHASIS" >Following this Samba will bit-wise 'OR' the UNIX mode created from this parameter with the value of the <A HREF="#FORCECREATEMODE" -><TT +><VAR CLASS="PARAMETER" -><I ->force create mode</I -></TT +>force create mode</VAR ></A > parameter which is set to 000 by default.</P @@ -6342,41 +5537,33 @@ CLASS="PARAMETER" >This parameter does not affect directory modes. See the parameter <A HREF="#DIRECTORYMODE" -><TT +><VAR CLASS="PARAMETER" -><I >directory mode - </I -></TT + </VAR ></A > for details.</P ><P >See also the <A HREF="#FORCECREATEMODE" -><TT +><VAR CLASS="PARAMETER" -><I >force - create mode</I -></TT + create mode</VAR ></A > parameter for forcing particular mode bits to be set on created files. See also the <A HREF="#DIRECTORYMODE" -> <TT +> <VAR CLASS="PARAMETER" -><I ->directory mode</I -></TT +>directory mode</VAR ></A > parameter for masking mode bits on created directories. See also the <A HREF="#INHERITPERMISSIONS" -> <TT +> <VAR CLASS="PARAMETER" -><I ->inherit permissions</I -></TT +>inherit permissions</VAR ></A > parameter.</P ><P @@ -6384,11 +5571,9 @@ 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" -><TT +><VAR CLASS="PARAMETER" -><I ->security mask</I -></TT +>security mask</VAR ></A >.</P ><P @@ -6411,11 +5596,9 @@ NAME="CREATEMODE" ><P >This is a synonym for <A HREF="#CREATEMASK" -><TT +><VAR CLASS="PARAMETER" -><I -> create mask</I -></TT +> create mask</VAR ></A >.</P ></DD @@ -6506,11 +5689,9 @@ NAME="DEBUGHIRESTIMESTAMP" ><P >Note that the parameter <A HREF="#DEBUGTIMESTAMP" -><TT +><VAR CLASS="PARAMETER" -><I -> debug timestamp</I -></TT +> debug timestamp</VAR ></A > must be on for this to have an effect.</P @@ -6538,11 +5719,9 @@ TARGET="_top" ><P >Note that the parameter <A HREF="#DEBUGTIMESTAMP" -><TT +><VAR CLASS="PARAMETER" -><I -> debug timestamp</I -></TT +> debug timestamp</VAR ></A > must be on for this to have an effect.</P @@ -6562,11 +5741,9 @@ NAME="DEBUGTIMESTAMP" >Samba debug log messages are timestamped by default. If you are running at a high <A HREF="#DEBUGLEVEL" -> <TT +> <VAR CLASS="PARAMETER" -><I ->debug level</I -></TT +>debug level</VAR ></A > these timestamps can be distracting. This boolean parameter allows timestamping @@ -6591,11 +5768,9 @@ NAME="DEBUGUID" ><P >Note that the parameter <A HREF="#DEBUGTIMESTAMP" -><TT +><VAR CLASS="PARAMETER" -><I -> debug timestamp</I -></TT +> debug timestamp</VAR ></A > must be on for this to have an effect.</P @@ -6614,11 +5789,9 @@ NAME="DEBUGLEVEL" ><P >Synonym for <A HREF="#LOGLEVEL" -><TT +><VAR CLASS="PARAMETER" -><I -> log level</I -></TT +> log level</VAR ></A >.</P ></DD @@ -6631,11 +5804,9 @@ NAME="DEFAULT" ><P >A synonym for <A HREF="#DEFAULTSERVICE" -><TT +><VAR CLASS="PARAMETER" -><I -> default service</I -></TT +> default service</VAR ></A >.</P ></DD @@ -6651,11 +5822,9 @@ HREF="#AEN206" > NAME MANGLING</A >. Also note the <A HREF="#SHORTPRESERVECASE" -> <TT +> <VAR CLASS="PARAMETER" -><I ->short preserve case</I -></TT +>short preserve case</VAR ></A > parameter.</P ><P @@ -6739,29 +5908,23 @@ CLASS="EMPHASIS" ><P >Typically the default service would be a <A HREF="#GUESTOK" -> <TT +> <VAR CLASS="PARAMETER" -><I ->guest ok</I -></TT +>guest ok</VAR ></A >, <A HREF="#READONLY" -> <TT +> <VAR CLASS="PARAMETER" -><I ->read-only</I -></TT +>read-only</VAR ></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 <TT + allows you to use macros like <VAR CLASS="PARAMETER" -><I ->%S</I -></TT +>%S</VAR > to make a wildcard service.</P ><P @@ -6801,11 +5964,9 @@ CLASS="REFENTRYTITLE" >smbd</SPAN >(8)</SPAN > when a group is requested to be deleted. - It will expand any <TT + It will expand any <VAR CLASS="PARAMETER" -><I ->%g</I -></TT +>%g</VAR > to the group name passed. This script is only useful for installations using the Windows NT domain administration tools. </P @@ -6823,11 +5984,9 @@ 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 <TT + physically deleted from underlying printing system. The <VAR CLASS="PARAMETER" -><I -> deleteprinter command</I -></TT +> deleteprinter command</VAR > defines a script to be run which will perform the necessary operations for removing the printer from the print system and from <TT @@ -6836,24 +5995,18 @@ CLASS="FILENAME" >. </P ><P ->The <TT +>The <VAR CLASS="PARAMETER" -><I ->deleteprinter command</I -></TT +>deleteprinter command</VAR > is - automatically called with only one parameter: <TT + automatically called with only one parameter: <VAR CLASS="PARAMETER" -><I -> "printer name"</I -></TT +> "printer name"</VAR >.</P ><P ->Once the <TT +>Once the <VAR CLASS="PARAMETER" -><I ->deleteprinter command</I -></TT +>deleteprinter command</VAR > has been executed, <B CLASS="COMMAND" @@ -6870,29 +6023,23 @@ CLASS="COMMAND" ><P >See also <A HREF="#ADDPRINTERCOMMAND" -><TT +><VAR CLASS="PARAMETER" -><I -> addprinter command</I -></TT +> addprinter command</VAR ></A >, <A HREF="#PRINTING" -><TT +><VAR CLASS="PARAMETER" -><I ->printing</I -></TT +>printing</VAR ></A >, <A HREF="#SHOWADDPRINTERWIZARD" -><TT +><VAR CLASS="PARAMETER" -><I >show add - printer wizard</I -></TT + printer wizard</VAR ></A ></P ><P @@ -6938,22 +6085,18 @@ NAME="DELETESHARECOMMAND" ><P >Samba 2.2.0 introduced the ability to dynamically add and delete shares via the Windows NT 4.0 Server Manager. The - <TT + <VAR CLASS="PARAMETER" -><I ->delete share command</I -></TT +>delete share command</VAR > 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 <TT + execute the <VAR CLASS="PARAMETER" -><I ->delete share command</I -></TT +>delete share command</VAR >, <B CLASS="COMMAND" >smbd</B @@ -6966,11 +6109,9 @@ CLASS="COMMAND" CLASS="COMMAND" >smbd</B > will automatically invoke the - <TT + <VAR CLASS="PARAMETER" -><I ->delete share command</I -></TT +>delete share command</VAR > with two parameters. </P ><P @@ -6978,11 +6119,9 @@ CLASS="PARAMETER" ><UL ><LI ><P -><TT +><VAR CLASS="PARAMETER" -><I ->configFile</I -></TT +>configFile</VAR > - the location of the global <TT CLASS="FILENAME" @@ -6992,11 +6131,9 @@ CLASS="FILENAME" ></LI ><LI ><P -><TT +><VAR CLASS="PARAMETER" -><I ->shareName</I -></TT +>shareName</VAR > - the name of the existing service. </P @@ -7006,33 +6143,27 @@ CLASS="PARAMETER" > This parameter is only used to remove file shares. To delete printer shares, see the <A HREF="#DELETEPRINTERCOMMAND" -><TT +><VAR CLASS="PARAMETER" -><I >deleteprinter - command</I -></TT + command</VAR ></A >. </P ><P > See also <A HREF="#ADDSHARECOMMAND" -><TT +><VAR CLASS="PARAMETER" -><I >add share - command</I -></TT + command</VAR ></A >, <A HREF="#CHANGESHARECOMMAND" -><TT +><VAR CLASS="PARAMETER" -><I >change - share command</I -></TT + share command</VAR ></A >. </P @@ -7081,7 +6212,7 @@ CLASS="COMMAND" ><P >Default: <B CLASS="COMMAND" ->delete user script = <empty string> +>delete user script = <empty string> </B ></P ><P @@ -7113,17 +6244,13 @@ CLASS="EMPHASIS" >AS ROOT</I ></SPAN >. - Any <TT + Any <VAR CLASS="PARAMETER" -><I ->%g</I -></TT +>%g</VAR > will be replaced with the group name and - any <TT + any <VAR CLASS="PARAMETER" -><I ->%u</I -></TT +>%u</VAR > will be replaced with the user name. </P ><P @@ -7148,23 +6275,21 @@ NAME="DELETEVETOFILES" delete a directory that contains one or more vetoed directories (see the <A HREF="#VETOFILES" -><TT +><VAR CLASS="PARAMETER" -><I ->veto files</I -></TT +>veto files</VAR ></A > - option). If this option is set to <TT + option). If this option is set to <CODE CLASS="CONSTANT" ->no</TT +>no</CODE > (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 <TT +>If this option is set to <CODE CLASS="CONSTANT" ->yes</TT +>yes</CODE >, then Samba will attempt to recursively delete any files and directories within the vetoed directory. This can be useful for integration with file @@ -7184,12 +6309,10 @@ CLASS="COMMAND" ><P >See also the <A HREF="#VETOFILES" -><TT +><VAR CLASS="PARAMETER" -><I >veto - files</I -></TT + files</VAR ></A > parameter.</P ><P @@ -7207,12 +6330,10 @@ NAME="DENYHOSTS" ><P >Synonym for <A HREF="#HOSTSDENY" -><TT +><VAR CLASS="PARAMETER" -><I >hosts - deny</I -></TT + deny</VAR ></A >.</P ></DD @@ -7223,11 +6344,9 @@ NAME="DFREECOMMAND" >>dfree command (G)</DT ><DD ><P ->The <TT +>The <VAR CLASS="PARAMETER" -><I ->dfree command</I -></TT +>dfree command</VAR > 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, @@ -7306,12 +6425,10 @@ NAME="DIRECTORY" ><P >Synonym for <A HREF="#PATH" -><TT +><VAR CLASS="PARAMETER" -><I >path - </I -></TT + </VAR ></A >.</P ></DD @@ -7347,12 +6464,10 @@ CLASS="EMPHASIS" >Following this Samba will bit-wise 'OR' the UNIX mode created from this parameter with the value of the <A HREF="#FORCEDIRECTORYMODE" -><TT +><VAR CLASS="PARAMETER" -><I >force directory mode - </I -></TT + </VAR ></A > parameter. This parameter is set to 000 by default (i.e. no extra mode bits are added).</P @@ -7361,54 +6476,44 @@ 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" -><TT +><VAR CLASS="PARAMETER" -><I ->directory security mask</I -></TT +>directory security mask</VAR ></A >.</P ><P >See the <A HREF="#FORCEDIRECTORYMODE" -><TT +><VAR CLASS="PARAMETER" -><I >force - directory mode</I -></TT + directory mode</VAR ></A > parameter to cause particular mode bits to always be set on created directories.</P ><P >See also the <A HREF="#CREATEMODE" -><TT +><VAR CLASS="PARAMETER" -><I >create mode - </I -></TT + </VAR ></A > parameter for masking mode bits on created files, and the <A HREF="#DIRECTORYSECURITYMASK" -><TT +><VAR CLASS="PARAMETER" -><I >directory - security mask</I -></TT + security mask</VAR ></A > parameter.</P ><P >Also refer to the <A HREF="#INHERITPERMISSIONS" -><TT +><VAR CLASS="PARAMETER" -><I -> inherit permissions</I -></TT +> inherit permissions</VAR ></A > parameter.</P ><P @@ -7431,11 +6536,9 @@ NAME="DIRECTORYMODE" ><P >Synonym for <A HREF="#DIRECTORYMASK" -><TT +><VAR CLASS="PARAMETER" -><I -> directory mask</I -></TT +> directory mask</VAR ></A ></P ></DD @@ -7471,36 +6574,30 @@ CLASS="EMPHASIS" 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 <TT + it as the default of <CODE CLASS="CONSTANT" ->0777</TT +>0777</CODE >.</P ><P >See also the <A HREF="#FORCEDIRECTORYSECURITYMODE" -><TT +><VAR CLASS="PARAMETER" -><I -> force directory security mode</I -></TT +> force directory security mode</VAR ></A >, <A HREF="#SECURITYMASK" -><TT +><VAR CLASS="PARAMETER" -><I ->security mask</I -></TT +>security mask</VAR ></A >, <A HREF="#FORCESECURITYMODE" -><TT +><VAR CLASS="PARAMETER" -><I >force security mode - </I -></TT + </VAR ></A > parameters.</P ><P @@ -7631,11 +6728,9 @@ CLASS="COMMAND" ><P >See also the parameter <A HREF="#WINSSUPPORT" -><TT +><VAR CLASS="PARAMETER" -><I -> wins support</I -></TT +> wins support</VAR ></A >.</P ><P @@ -7651,17 +6746,15 @@ NAME="DOMAINLOGONS" >>domain logons (G)</DT ><DD ><P ->If set to <TT +>If set to <CODE CLASS="CONSTANT" ->yes</TT +>yes</CODE >, the Samba server will serve Windows 95/98 Domain logons for the <A HREF="#WORKGROUP" -> <TT +> <VAR CLASS="PARAMETER" -><I ->workgroup</I -></TT +>workgroup</VAR ></A > it is in. Samba 2.2 has limited capability to act as a domain controller for Windows @@ -7698,18 +6791,14 @@ CLASS="COMMAND" claim a special domain specific NetBIOS name that identifies it as a domain master browser for its given <A HREF="#WORKGROUP" -> <TT +> <VAR CLASS="PARAMETER" -><I ->workgroup</I -></TT +>workgroup</VAR ></A >. Local master browsers - in the same <TT + in the same <VAR CLASS="PARAMETER" -><I ->workgroup</I -></TT +>workgroup</VAR > on broadcast-isolated subnets will give this <B CLASS="COMMAND" @@ -7727,29 +6816,23 @@ CLASS="REFENTRYTITLE" instead of just the list for their broadcast-isolated subnet.</P ><P >Note that Windows NT Primary Domain Controllers expect to be - able to claim this <TT + able to claim this <VAR CLASS="PARAMETER" -><I ->workgroup</I -></TT +>workgroup</VAR > specific special NetBIOS name that identifies them as domain master browsers for - that <TT + that <VAR CLASS="PARAMETER" -><I ->workgroup</I -></TT +>workgroup</VAR > 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 <TT + the special name for a <VAR CLASS="PARAMETER" -><I ->workgroup</I -></TT +>workgroup</VAR > before a Windows NT PDC is able to do so then cross subnet browsing will behave strangely and may fail.</P @@ -7761,24 +6844,18 @@ CLASS="COMMAND" >domain logons = yes</B > </A ->, then the default behavior is to enable the <TT +>, then the default behavior is to enable the <VAR CLASS="PARAMETER" -><I >domain - master</I -></TT -> parameter. If <TT + master</VAR +> parameter. If <VAR CLASS="PARAMETER" -><I ->domain logons</I -></TT +>domain logons</VAR > is - not enabled (the default setting), then neither will <TT + not enabled (the default setting), then neither will <VAR CLASS="PARAMETER" -><I >domain - master</I -></TT + master</VAR > be enabled by default.</P ><P >Default: <B @@ -7922,9 +6999,9 @@ NAME="DOSFILETIMES" CLASS="COMMAND" >smbd</B > is acting - on behalf of is not the file owner. Setting this option to <TT + on behalf of is not the file owner. Setting this option to <CODE CLASS="CONSTANT" -> yes</TT +> yes</CODE > allows DOS semantics and <SPAN CLASS="CITEREFENTRY" ><SPAN @@ -8035,9 +7112,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--<TT + port defined--<CODE CLASS="CONSTANT" ->"Samba Printer Port"</TT +>"Samba Printer Port"</CODE >. Under Windows NT/2000, all printers must have a valid port name. If you wish to have a list of ports displayed (<B @@ -8045,15 +7122,13 @@ CLASS="COMMAND" >smbd </B > does not use a port name for anything) other than - the default <TT + the default <CODE CLASS="CONSTANT" ->"Samba Printer Port"</TT +>"Samba Printer Port"</CODE >, you - can define <TT + can define <VAR CLASS="PARAMETER" -><I ->enumports command</I -></TT +>enumports command</VAR > 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 @@ -8082,11 +7157,9 @@ NAME="EXEC" ><P >This is a synonym for <A HREF="#PREEXEC" -> <TT +> <VAR CLASS="PARAMETER" -><I ->preexec</I -></TT +>preexec</VAR ></A >.</P ></DD @@ -8159,11 +7232,9 @@ CLASS="COMMAND" ><P >It is generally much better to use the real <A HREF="#OPLOCKS" -><TT +><VAR CLASS="PARAMETER" -><I ->oplocks</I -></TT +>oplocks</VAR ></A > support rather than this parameter.</P @@ -8197,9 +7268,9 @@ CLASS="REFENTRYTITLE" >(8)</SPAN > from following symbolic links in a particular share. Setting this - parameter to <TT + parameter to <CODE CLASS="CONSTANT" ->no</TT +>no</CODE > 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 @@ -8240,33 +7311,27 @@ CLASS="EMPHASIS" 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 <TT + mode after the mask set in the <VAR CLASS="PARAMETER" -><I ->create mask</I -></TT +>create mask</VAR > parameter is applied.</P ><P >See also the parameter <A HREF="#CREATEMASK" -><TT +><VAR CLASS="PARAMETER" -><I >create - mask</I -></TT + mask</VAR ></A > for details on masking mode bits on files.</P ><P >See also the <A HREF="#INHERITPERMISSIONS" -><TT +><VAR CLASS="PARAMETER" -><I >inherit - permissions</I -></TT + permissions</VAR ></A > parameter.</P ><P @@ -8303,32 +7368,26 @@ CLASS="EMPHASIS" 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 <TT + mask in the parameter <VAR CLASS="PARAMETER" -><I ->directory mask</I -></TT +>directory mask</VAR > is applied.</P ><P >See also the parameter <A HREF="#DIRECTORYMASK" -><TT +><VAR CLASS="PARAMETER" -><I -> directory mask</I -></TT +> directory mask</VAR ></A > for details on masking mode bits on created directories.</P ><P >See also the <A HREF="#INHERITPERMISSIONS" -><TT +><VAR CLASS="PARAMETER" -><I -> inherit permissions</I -></TT +> inherit permissions</VAR ></A > parameter.</P ><P @@ -8381,29 +7440,23 @@ CLASS="EMPHASIS" ><P >See also the <A HREF="#DIRECTORYSECURITYMASK" -><TT +><VAR CLASS="PARAMETER" -><I -> directory security mask</I -></TT +> directory security mask</VAR ></A >, <A HREF="#SECURITYMASK" -> <TT +> <VAR CLASS="PARAMETER" -><I ->security mask</I -></TT +>security mask</VAR ></A >, <A HREF="#FORCESECURITYMODE" -><TT +><VAR CLASS="PARAMETER" -><I >force security mode - </I -></TT + </VAR ></A > parameters.</P ><P @@ -8450,35 +7503,27 @@ CLASS="FILENAME" ><P >If the <A HREF="#FORCEUSER" -><TT +><VAR CLASS="PARAMETER" -><I >force user - </I -></TT + </VAR ></A > parameter is also set the group specified in - <TT + <VAR CLASS="PARAMETER" -><I ->force group</I -></TT +>force group</VAR > will override the primary group - set in <TT + set in <VAR CLASS="PARAMETER" -><I ->force user</I -></TT +>force user</VAR >.</P ><P >See also <A HREF="#FORCEUSER" -><TT +><VAR CLASS="PARAMETER" -><I >force - user</I -></TT + user</VAR ></A >.</P ><P @@ -8531,29 +7576,23 @@ CLASS="EMPHASIS" ><P >See also the <A HREF="#FORCEDIRECTORYSECURITYMODE" -><TT +><VAR CLASS="PARAMETER" -><I -> force directory security mode</I -></TT +> force directory security mode</VAR ></A >, <A HREF="#DIRECTORYSECURITYMASK" -><TT +><VAR CLASS="PARAMETER" -><I >directory security - mask</I -></TT + mask</VAR ></A >, <A HREF="#SECURITYMASK" -><TT +><VAR CLASS="PARAMETER" -><I -> security mask</I -></TT +> security mask</VAR ></A > parameters.</P ><P @@ -8592,12 +7631,10 @@ NAME="FORCEUSER" ><P >See also <A HREF="#FORCEGROUP" -><TT +><VAR CLASS="PARAMETER" -><I >force group - </I -></TT + </VAR ></A ></P ><P @@ -8630,18 +7667,18 @@ CLASS="REFENTRYTITLE" >smbd</SPAN >(8)</SPAN > when a client queries the filesystem type - for a share. The default type is <TT + for a share. The default type is <CODE CLASS="CONSTANT" ->NTFS</TT +>NTFS</CODE > for compatibility with Windows NT but this can be changed to other - strings such as <TT + strings such as <CODE CLASS="CONSTANT" ->Samba</TT -> or <TT +>Samba</CODE +> or <CODE CLASS="CONSTANT" >FAT - </TT + </CODE > if required.</P ><P >Default: <B @@ -8666,16 +7703,14 @@ NAME="GETWDCACHE" calls. This can have a significant impact on performance, especially when the <A HREF="#WIDELINKS" -><TT +><VAR CLASS="PARAMETER" -><I ->wide links</I -></TT +>wide links</VAR > </A ->parameter is set to <TT +>parameter is set to <CODE CLASS="CONSTANT" ->no</TT +>no</CODE >.</P ><P >Default: <B @@ -8692,12 +7727,10 @@ NAME="GROUP" ><P >Synonym for <A HREF="#FORCEGROUP" -><TT +><VAR CLASS="PARAMETER" -><I >force - group</I -></TT + group</VAR ></A >.</P ></DD @@ -8711,11 +7744,9 @@ NAME="GUESTACCOUNT" >This is a username which will be used for access to services which are specified as <A HREF="#GUESTOK" -><TT +><VAR CLASS="PARAMETER" -><I -> guest ok</I -></TT +> guest ok</VAR ></A > (see below). Whatever privileges this user has will be available to any client connecting to the guest service. @@ -8764,40 +7795,34 @@ NAME="GUESTOK" >>guest ok (S)</DT ><DD ><P ->If this parameter is <TT +>If this parameter is <CODE CLASS="CONSTANT" ->yes</TT +>yes</CODE > for a service, then no password is required to connect to the service. Privileges will be those of the <A HREF="#GUESTACCOUNT" -><TT +><VAR CLASS="PARAMETER" -><I -> guest account</I -></TT +> guest account</VAR ></A >.</P ><P >This paramater nullifies the benifits of setting <A HREF="#RESTRICTANONYMOUS" -><TT +><VAR CLASS="PARAMETER" -><I >restrict - anonymous</I -></TT + anonymous</VAR ></A > = 2</P ><P >See the section below on <A HREF="#SECURITY" -><TT +><VAR CLASS="PARAMETER" -><I -> security</I -></TT +> security</VAR ></A > for more information about this option. </P @@ -8814,28 +7839,24 @@ NAME="GUESTONLY" >>guest only (S)</DT ><DD ><P ->If this parameter is <TT +>If this parameter is <CODE CLASS="CONSTANT" ->yes</TT +>yes</CODE > for a service, then only guest connections to the service are permitted. This parameter will have no effect if <A HREF="#GUESTOK" -> <TT +> <VAR CLASS="PARAMETER" -><I ->guest ok</I -></TT +>guest ok</VAR ></A > is not set for the service.</P ><P >See the section below on <A HREF="#SECURITY" -><TT +><VAR CLASS="PARAMETER" -><I -> security</I -></TT +> security</VAR ></A > for more information about this option. </P @@ -8888,28 +7909,22 @@ NAME="HIDEFILES" ><P >See also <A HREF="#HIDEDOTFILES" -><TT +><VAR CLASS="PARAMETER" -><I >hide - dot files</I -></TT + dot files</VAR ></A >, <A HREF="#VETOFILES" -><TT +><VAR CLASS="PARAMETER" -><I -> veto files</I -></TT +> veto files</VAR ></A > and <A HREF="#CASESENSITIVE" -> <TT +> <VAR CLASS="PARAMETER" -><I ->case sensitive</I -></TT +>case sensitive</VAR ></A >.</P ><P @@ -9009,16 +8024,14 @@ NAME="HOMEDIRMAP" ><P >If<A HREF="#NISHOMEDIR" -><TT +><VAR CLASS="PARAMETER" -><I >nis homedir - </I -></TT + </VAR ></A -> is <TT +> is <CODE CLASS="CONSTANT" ->yes</TT +>yes</CODE >, and <SPAN CLASS="CITEREFENTRY" ><SPAN @@ -9026,11 +8039,9 @@ CLASS="REFENTRYTITLE" >smbd</SPAN >(8)</SPAN > is also acting - as a Win95/98 <TT + as a Win95/98 <VAR CLASS="PARAMETER" -><I ->logon server</I -></TT +>logon server</VAR > 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 @@ -9057,27 +8068,23 @@ CLASS="EMPHASIS" ><P >See also <A HREF="#NISHOMEDIR" -><TT +><VAR CLASS="PARAMETER" -><I ->nis homedir</I -></TT +>nis homedir</VAR > </A >, <A HREF="#DOMAINLOGONS" -><TT +><VAR CLASS="PARAMETER" -><I ->domain logons</I -></TT +>domain logons</VAR > </A >.</P ><P >Default: <B CLASS="COMMAND" ->homedir map = <empty string></B +>homedir map = <empty string></B ></P ><P >Example: <B @@ -9096,20 +8103,18 @@ NAME="HOSTMSDFS" if Samba has been configured and compiled with the <B CLASS="COMMAND" > --with-msdfs</B -> option. If set to <TT +> option. If set to <CODE CLASS="CONSTANT" ->yes</TT +>yes</CODE >, 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" -><TT +><VAR CLASS="PARAMETER" -><I -> msdfs root</I -></TT +> msdfs root</VAR ></A > share level parameter. For more information on setting up a Dfs tree on Samba, @@ -9161,12 +8166,10 @@ NAME="HOSTSALLOW" >>hosts allow (S)</DT ><DD ><P ->A synonym for this parameter is <TT +>A synonym for this parameter is <VAR CLASS="PARAMETER" -><I >allow - hosts</I -></TT + hosts</VAR >.</P ><P >This parameter is a comma, space, or tab delimited @@ -9193,11 +8196,9 @@ CLASS="FILENAME" >Note that the localhost address 127.0.0.1 will always be allowed access unless specifically denied by a <A HREF="#HOSTSDENY" -><TT +><VAR CLASS="PARAMETER" -><I ->hosts deny</I -></TT +>hosts deny</VAR ></A > option.</P ><P @@ -9279,11 +8280,9 @@ NAME="HOSTSDENY" >>hosts deny (S)</DT ><DD ><P ->The opposite of <TT +>The opposite of <VAR CLASS="PARAMETER" -><I ->hosts allow</I -></TT +>hosts allow</VAR > - hosts listed here are <SPAN CLASS="emphasis" @@ -9293,11 +8292,9 @@ CLASS="EMPHASIS" ></SPAN > permitted access to services unless the specific services have their own lists to override - this one. Where the lists conflict, the <TT + this one. Where the lists conflict, the <VAR CLASS="PARAMETER" -><I ->allow</I -></TT +>allow</VAR > list takes precedence.</P ><P @@ -9330,18 +8327,14 @@ NAME="HOSTSEQUIV" ><P >This is not be confused with <A HREF="#HOSTSALLOW" -> <TT +> <VAR CLASS="PARAMETER" -><I ->hosts allow</I -></TT +>hosts allow</VAR ></A > which is about hosts - access to services and is more useful for guest services. <TT + access to services and is more useful for guest services. <VAR CLASS="PARAMETER" -><I -> hosts equiv</I -></TT +> hosts equiv</VAR > may be useful for NT clients which will not supply passwords to Samba.</P ><P @@ -9351,20 +8344,16 @@ CLASS="emphasis" CLASS="EMPHASIS" >NOTE :</I ></SPAN -> The use of <TT +> The use of <VAR CLASS="PARAMETER" -><I >hosts equiv - </I -></TT + </VAR > 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 + <VAR CLASS="PARAMETER" -><I ->hosts equiv</I -></TT +>hosts equiv</VAR > 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 @@ -9400,22 +8389,16 @@ NAME="INCLUDE" inside another. The file is included literally, as though typed in place.</P ><P ->It takes the standard substitutions, except <TT +>It takes the standard substitutions, except <VAR CLASS="PARAMETER" -><I >%u - </I -></TT ->, <TT + </VAR +>, <VAR CLASS="PARAMETER" -><I ->%P</I -></TT -> and <TT +>%P</VAR +> and <VAR CLASS="PARAMETER" -><I ->%S</I -></TT +>%S</VAR >. </P ><P @@ -9465,37 +8448,29 @@ NAME="INHERITPERMISSIONS" >The permissions on new files and directories are normally governed by <A HREF="#CREATEMASK" -><TT +><VAR CLASS="PARAMETER" -><I -> create mask</I -></TT +> create mask</VAR ></A >, <A HREF="#DIRECTORYMASK" -> <TT +> <VAR CLASS="PARAMETER" -><I ->directory mask</I -></TT +>directory mask</VAR ></A >, <A HREF="#FORCECREATEMODE" -><TT +><VAR CLASS="PARAMETER" -><I ->force create mode</I -></TT +>force create mode</VAR > </A > and <A HREF="#FORCEDIRECTORYMODE" -><TT +><VAR CLASS="PARAMETER" -><I >force - directory mode</I -></TT + directory mode</VAR ></A > but the boolean inherit permissions parameter overrides this.</P @@ -9507,29 +8482,23 @@ CLASS="PARAMETER" directory. Their execute bits continue to be determined by <A HREF="#MAPARCHIVE" -><TT +><VAR CLASS="PARAMETER" -><I ->map archive</I -></TT +>map archive</VAR > </A >, <A HREF="#MAPHIDDEN" -><TT +><VAR CLASS="PARAMETER" -><I ->map hidden</I -></TT +>map hidden</VAR > </A > and <A HREF="#MAPSYSTEM" -><TT +><VAR CLASS="PARAMETER" -><I ->map system</I -></TT +>map system</VAR > </A > as usual.</P @@ -9549,36 +8518,28 @@ CLASS="EMPHASIS" ><P >See also <A HREF="#CREATEMASK" -><TT +><VAR CLASS="PARAMETER" -><I >create mask - </I -></TT + </VAR ></A >, <A HREF="#DIRECTORYMASK" -><TT +><VAR CLASS="PARAMETER" -><I -> directory mask</I -></TT +> directory mask</VAR ></A >, <A HREF="#FORCECREATEMODE" -> <TT +> <VAR CLASS="PARAMETER" -><I ->force create mode</I -></TT +>force create mode</VAR ></A > and <A HREF="#FORCEDIRECTORYMODE" -><TT +><VAR CLASS="PARAMETER" -><I ->force directory mode</I -></TT +>force directory mode</VAR > </A >.</P @@ -9650,12 +8611,10 @@ CLASS="COMMAND" ><P >See also <A HREF="#BINDINTERFACESONLY" -><TT +><VAR CLASS="PARAMETER" -><I >bind - interfaces only</I -></TT + interfaces only</VAR ></A >.</P ><P @@ -9692,41 +8651,33 @@ CLASS="EMPHASIS" ><P >A name starting with '+' is interpreted only by looking in the UNIX group database. A name starting with - '&' is interpreted only by looking in the NIS netgroup database + '&' is interpreted only by looking in the NIS netgroup database (this requires NIS to be working on your system). The characters - '+' and '&' may be used at the start of the name in either order - so the value <TT + '+' and '&' may be used at the start of the name in either order + so the value <VAR CLASS="PARAMETER" -><I ->+&group</I -></TT +>+&group</VAR > means check the UNIX group database, followed by the NIS netgroup database, and - the value <TT + the value <VAR CLASS="PARAMETER" -><I ->&+group</I -></TT +>&+group</VAR > 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 <TT +>The current servicename is substituted for <VAR CLASS="PARAMETER" -><I ->%S</I -></TT +>%S</VAR >. This is useful in the [homes] section.</P ><P >See also <A HREF="#VALIDUSERS" -><TT +><VAR CLASS="PARAMETER" -><I >valid users - </I -></TT + </VAR ></A >.</P ><P @@ -9752,11 +8703,9 @@ NAME="KEEPALIVE" ><DD ><P >The value of the parameter (an integer) represents - the number of seconds between <TT + the number of seconds between <VAR CLASS="PARAMETER" -><I ->keepalive</I -></TT +>keepalive</VAR > packets. If this parameter is zero, no keepalive packets will be sent. Keepalive packets, if sent, allow the server to tell whether @@ -9765,11 +8714,9 @@ 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" -><TT +><VAR CLASS="PARAMETER" -><I ->socket options</I -></TT +>socket options</VAR ></A >). Basically you should only use this option if you strike difficulties.</P @@ -9793,22 +8740,18 @@ NAME="KERNELOPLOCKS" ><P >For UNIXes that support kernel based <A HREF="#OPLOCKS" -><TT +><VAR CLASS="PARAMETER" -><I ->oplocks</I -></TT +>oplocks</VAR ></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 <TT +>Kernel oplocks support allows Samba <VAR CLASS="PARAMETER" -><I >oplocks - </I -></TT + </VAR > to be broken whenever a local UNIX process or NFS operation accesses a file that <SPAN CLASS="CITEREFENTRY" @@ -9826,30 +8769,26 @@ CLASS="EMPHASIS" ></SPAN > cool feature :-).</P ><P ->This parameter defaults to <TT +>This parameter defaults to <CODE CLASS="CONSTANT" ->on</TT +>on</CODE >, 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" -><TT +><VAR CLASS="PARAMETER" -><I ->oplocks</I -></TT +>oplocks</VAR > </A > and <A HREF="#LEVEL2OPLOCKS" -><TT +><VAR CLASS="PARAMETER" -><I >level2 oplocks - </I -></TT + </VAR ></A > parameters.</P ><P @@ -9915,19 +8854,15 @@ NAME="LDAPADMINDN" >>ldap admin dn (G)</DT ><DD ><P -> The <TT +> The <VAR CLASS="PARAMETER" -><I ->ldap admin dn</I -></TT +>ldap admin dn</VAR > defines the Distinguished Name (DN) name used by Samba to contact the ldap server when retreiving - user account information. The <TT + user account information. The <VAR CLASS="PARAMETER" -><I >ldap - admin dn</I -></TT + admin dn</VAR > is used in conjunction with the admin dn password stored in the <TT CLASS="FILENAME" @@ -9959,20 +8894,20 @@ NAME="LDAPFILTER" ><DD ><P >This parameter specifies the RFC 2254 compliant LDAP search filter. - The default is to match the login name with the <TT + The default is to match the login name with the <CODE CLASS="CONSTANT" ->uid</TT +>uid</CODE > - attribute for all entries matching the <TT + attribute for all entries matching the <CODE CLASS="CONSTANT" ->sambaAccount</TT +>sambaAccount</CODE > objectclass. Note that this filter should only return one entry. </P ><P >Default : <B CLASS="COMMAND" ->ldap filter = (&(uid=%u)(objectclass=sambaAccount))</B +>ldap filter = (&(uid=%u)(objectclass=sambaAccount))</B ></P ></DD ><DT @@ -9993,11 +8928,9 @@ CLASS="COMMAND" > This option is used to control the tcp port number used to contact the <A HREF="#LDAPSERVER" -><TT +><VAR CLASS="PARAMETER" -><I ->ldap server</I -></TT +>ldap server</VAR ></A >. The default is to use the stand LDAPS port 636. @@ -10070,11 +9003,9 @@ CLASS="FILENAME" script. </P ><P -> The <TT +> The <VAR CLASS="PARAMETER" -><I ->ldap ssl</I -></TT +>ldap ssl</VAR > can be set to one of three values: </P ><P @@ -10082,37 +9013,29 @@ CLASS="PARAMETER" ><UL ><LI ><P -><TT +><VAR CLASS="PARAMETER" -><I ->Off</I -></TT +>Off</VAR > = Never use SSL when querying the directory.</P ></LI ><LI ><P -><TT +><VAR CLASS="PARAMETER" -><I ->Start_tls</I -></TT +>Start_tls</VAR > = Use the LDAPv3 StartTLS extended operation (RFC2830) for communicating with the directory server.</P ></LI ><LI ><P -><TT +><VAR CLASS="PARAMETER" -><I ->On</I -></TT +>On</VAR > = Use SSL on the ldaps port when contacting the - <TT + <VAR CLASS="PARAMETER" -><I ->ldap server</I -></TT +>ldap server</VAR >. Only available when the backwards-compatiblity <B CLASS="COMMAND" @@ -10120,11 +9043,9 @@ CLASS="COMMAND" > option is specified to configure. See <A HREF="#PASSDBBACKEND" -><TT +><VAR CLASS="PARAMETER" -><I ->passdb backend</I -></TT +>passdb backend</VAR ></A ></P ></LI @@ -10209,11 +9130,9 @@ NAME="LDAPPASSWDSYNC" change via SAMBA. </P ><P -> The <TT +> The <VAR CLASS="PARAMETER" -><I ->ldap passwd sync</I -></TT +>ldap passwd sync</VAR > can be set to one of three values: </P ><P @@ -10221,29 +9140,23 @@ CLASS="PARAMETER" ><UL ><LI ><P -><TT +><VAR CLASS="PARAMETER" -><I ->Yes</I -></TT +>Yes</VAR > = Try to update the LDAP, NT and LM passwords and update the pwdLastSet time.</P ></LI ><LI ><P -><TT +><VAR CLASS="PARAMETER" -><I ->No</I -></TT +>No</VAR > = Update NT and LM passwords and update the pwdLastSet time.</P ></LI ><LI ><P -><TT +><VAR CLASS="PARAMETER" -><I ->Only</I -></TT +>Only</VAR > = Only update the LDAP password and let the LDAP server do the rest.</P ></LI ></UL @@ -10314,49 +9227,41 @@ NAME="LEVEL2OPLOCKS" ><P >Currently, if <A HREF="#KERNELOPLOCKS" -><TT +><VAR CLASS="PARAMETER" -><I >kernel - oplocks</I -></TT + oplocks</VAR ></A > are supported then level2 oplocks are - not granted (even if this parameter is set to <TT + not granted (even if this parameter is set to <CODE CLASS="CONSTANT" ->yes</TT +>yes</CODE >). Note also, the <A HREF="#OPLOCKS" -><TT +><VAR CLASS="PARAMETER" -><I ->oplocks</I -></TT +>oplocks</VAR > </A -> parameter must be set to <TT +> parameter must be set to <CODE CLASS="CONSTANT" ->yes</TT +>yes</CODE > on this share in order for this parameter to have any effect.</P ><P >See also the <A HREF="#OPLOCKS" -><TT +><VAR CLASS="PARAMETER" -><I ->oplocks</I -></TT +>oplocks</VAR > </A > and <A HREF="#OPLOCKS" -><TT +><VAR CLASS="PARAMETER" -><I ->kernel oplocks</I -></TT +>kernel oplocks</VAR > </A > parameters.</P @@ -10382,56 +9287,50 @@ CLASS="REFENTRYTITLE" > 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, <TT + values, <CODE CLASS="CONSTANT" ->yes</TT ->, <TT +>yes</CODE +>, <CODE CLASS="CONSTANT" ->no</TT +>no</CODE >, or - <TT + <CODE CLASS="CONSTANT" ->auto</TT ->. The default is <TT +>auto</CODE +>. The default is <CODE CLASS="CONSTANT" ->auto</TT +>auto</CODE >. - If set to <TT + If set to <CODE CLASS="CONSTANT" ->no</TT +>no</CODE > Samba will never produce these - broadcasts. If set to <TT + broadcasts. If set to <CODE CLASS="CONSTANT" ->yes</TT +>yes</CODE > Samba will produce Lanman announce broadcasts at a frequency set by the parameter - <TT + <VAR CLASS="PARAMETER" -><I ->lm interval</I -></TT ->. If set to <TT +>lm interval</VAR +>. If set to <CODE CLASS="CONSTANT" ->auto</TT +>auto</CODE > 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 - <TT + <VAR CLASS="PARAMETER" -><I ->lm interval</I -></TT +>lm interval</VAR >.</P ><P >See also <A HREF="#LMINTERVAL" -><TT +><VAR CLASS="PARAMETER" -><I >lm interval - </I -></TT + </VAR ></A >.</P ><P @@ -10455,31 +9354,25 @@ NAME="LMINTERVAL" >If Samba is set to produce Lanman announce broadcasts needed by OS/2 clients (see the <A HREF="#LMANNOUNCE" -> <TT +> <VAR CLASS="PARAMETER" -><I ->lm announce</I -></TT +>lm announce</VAR ></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 <TT + made despite the setting of the <VAR CLASS="PARAMETER" -><I ->lm announce</I -></TT +>lm announce</VAR > parameter.</P ><P >See also <A HREF="#LMANNOUNCE" -><TT +><VAR CLASS="PARAMETER" -><I >lm - announce</I -></TT + announce</VAR ></A >.</P ><P @@ -10527,20 +9420,20 @@ CLASS="REFENTRYTITLE" >nmbd</SPAN >(8)</SPAN > to try and become a local master browser - on a subnet. If set to <TT + on a subnet. If set to <CODE CLASS="CONSTANT" ->no</TT +>no</CODE > 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 <TT + default this value is set to <CODE CLASS="CONSTANT" ->yes</TT ->. Setting this value to <TT +>yes</CODE +>. Setting this value to <CODE CLASS="CONSTANT" ->yes</TT +>yes</CODE > doesn't mean that Samba will <SPAN CLASS="emphasis" @@ -10560,9 +9453,9 @@ CLASS="EMPHASIS" ></SPAN > in elections for local master browser.</P ><P ->Setting this value to <TT +>Setting this value to <CODE CLASS="CONSTANT" ->no</TT +>no</CODE > will cause <B CLASS="COMMAND" >nmbd</B @@ -10589,11 +9482,9 @@ NAME="LOCKDIR" ><P >Synonym for <A HREF="#LOCKDIRECTORY" -><TT +><VAR CLASS="PARAMETER" -><I -> lock directory</I -></TT +> lock directory</VAR ></A >.</P ></DD @@ -10608,11 +9499,9 @@ NAME="LOCKDIRECTORY" files will be placed. The lock files are used to implement the <A HREF="#MAXCONNECTIONS" -><TT +><VAR CLASS="PARAMETER" -><I ->max connections</I -></TT +>max connections</VAR > </A > option.</P @@ -10662,12 +9551,10 @@ NAME="LOCKSPINTIME" pause before attempting to gain a failed lock. See <A HREF="#LOCKSPINCOUNT" -><TT +><VAR CLASS="PARAMETER" -><I >lock spin - count</I -></TT + count</VAR ></A > for more details. </P @@ -10716,9 +9603,9 @@ CLASS="EMPHASIS" >may</I ></SPAN > not need locking (such as - CDROM drives), although setting this parameter of <TT + CDROM drives), although setting this parameter of <CODE CLASS="CONSTANT" ->no</TT +>no</CODE > is not really recommended even in this case.</P ><P @@ -10786,11 +9673,9 @@ NAME="LOGONDRIVE" >This parameter specifies the local path to which the home directory will be connected (see <A HREF="#LOGONHOME" -><TT +><VAR CLASS="PARAMETER" -><I ->logon home</I -></TT +>logon home</VAR ></A >) and is only used by NT Workstations. </P @@ -10819,14 +9704,12 @@ NAME="LOGONHOME" location when a Win95/98 or NT Workstation logs into a Samba PDC. It allows you to do </P ><P -><TT +><SAMP CLASS="PROMPT" ->C:\> </TT -><TT +>C:\> </SAMP +><KBD CLASS="USERINPUT" -><B ->NET USE H: /HOME</B -></TT +>NET USE H: /HOME</KBD > </P ><P @@ -10855,18 +9738,14 @@ CLASS="COMMAND" ><P >Note that in prior versions of Samba, the <A HREF="#LOGONPATH" -> <TT +> <VAR CLASS="PARAMETER" -><I ->logon path</I -></TT +>logon path</VAR ></A > was returned rather than - <TT + <VAR CLASS="PARAMETER" -><I ->logon home</I -></TT +>logon home</VAR >. This broke <B CLASS="COMMAND" >net use @@ -10902,11 +9781,9 @@ 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" -> <TT +> <VAR CLASS="PARAMETER" -><I ->logon home</I -></TT +>logon home</VAR ></A > parameter.</P ><P @@ -10986,11 +9863,9 @@ NAME="LOGONSCRIPT" >The script must be a relative path to the [netlogon] service. If the [netlogon] service specifies a <A HREF="#PATH" -> <TT +> <VAR CLASS="PARAMETER" -><I ->path</I -></TT +>path</VAR ></A > of <TT CLASS="FILENAME" @@ -11063,29 +9938,21 @@ 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 <TT +>If a <VAR CLASS="PARAMETER" -><I ->%p</I -></TT +>%p</VAR > is given then the printer name - is put in its place. A <TT + is put in its place. A <VAR CLASS="PARAMETER" -><I ->%j</I -></TT +>%j</VAR > is replaced with - the job number (an integer). On HPUX (see <TT + the job number (an integer). On HPUX (see <VAR CLASS="PARAMETER" -><I >printing=hpux - </I -></TT ->), if the <TT + </VAR +>), if the <VAR CLASS="PARAMETER" -><I ->-p%p</I -></TT +>-p%p</VAR > 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 @@ -11097,25 +9964,21 @@ CLASS="PARAMETER" ><P >See also the <A HREF="#PRINTING" -><TT +><VAR CLASS="PARAMETER" -><I >printing - </I -></TT + </VAR ></A > parameter.</P ><P >Default: Currently no default value is given to - this string, unless the value of the <TT + this string, unless the value of the <VAR CLASS="PARAMETER" -><I ->printing</I -></TT +>printing</VAR > - parameter is <TT + parameter is <CODE CLASS="CONSTANT" ->SYSV</TT +>SYSV</CODE >, in which case the default is :</P ><P ><B @@ -11123,15 +9986,13 @@ CLASS="COMMAND" >lp -i %p-%j -H hold</B ></P ><P ->or if the value of the <TT +>or if the value of the <VAR CLASS="PARAMETER" -><I ->printing</I -></TT +>printing</VAR > parameter - is <TT + is <CODE CLASS="CONSTANT" ->SOFTQ</TT +>SOFTQ</CODE >, then the default is:</P ><P ><B @@ -11191,12 +10052,10 @@ CLASS="COMMAND" ><P >See also the <A HREF="#PRINTING" -><TT +><VAR CLASS="PARAMETER" -><I >printing - </I -></TT + </VAR ></A > parameter.</P ><P @@ -11231,11 +10090,9 @@ 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 <TT + using the <VAR CLASS="PARAMETER" -><I ->printing =</I -></TT +>printing =</VAR > option.</P ><P >Some clients (notably Windows for Workgroups) may not @@ -11244,43 +10101,35 @@ 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 <TT +>If a <VAR CLASS="PARAMETER" -><I ->%p</I -></TT +>%p</VAR > 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 <TT + in the <VAR CLASS="PARAMETER" -><I ->lpq command</I -></TT -> as the <TT +>lpq command</VAR +> as the <VAR CLASS="ENVAR" >$PATH - </TT + </VAR > may not be available to the server. When compiled with - the CUPS libraries, no <TT + the CUPS libraries, no <VAR CLASS="PARAMETER" -><I ->lpq command</I -></TT +>lpq command</VAR > is needed because smbd will make a library call to obtain the print queue listing.</P ><P >See also the <A HREF="#PRINTING" -><TT +><VAR CLASS="PARAMETER" -><I >printing - </I -></TT + </VAR ></A > parameter.</P ><P @@ -11288,11 +10137,9 @@ CLASS="PARAMETER" CLASS="emphasis" ><I CLASS="EMPHASIS" ->depends on the setting of <TT +>depends on the setting of <VAR CLASS="PARAMETER" -><I -> printing</I -></TT +> printing</VAR ></I ></SPAN ></P @@ -11317,59 +10164,47 @@ NAME="LPRESUMECOMMAND" a printer name and job number to resume the print job. See also the <A HREF="#LPPAUSECOMMAND" -><TT +><VAR CLASS="PARAMETER" -><I >lppause command - </I -></TT + </VAR ></A > parameter.</P ><P ->If a <TT +>If a <VAR CLASS="PARAMETER" -><I ->%p</I -></TT +>%p</VAR > is given then the printer name - is put in its place. A <TT + is put in its place. A <VAR CLASS="PARAMETER" -><I ->%j</I -></TT +>%j</VAR > is replaced with the job number (an integer).</P ><P >Note that it is good practice to include the absolute path - in the <TT + in the <VAR CLASS="PARAMETER" -><I ->lpresume command</I -></TT +>lpresume command</VAR > as the PATH may not be available to the server.</P ><P >See also the <A HREF="#PRINTING" -><TT +><VAR CLASS="PARAMETER" -><I >printing - </I -></TT + </VAR ></A > parameter.</P ><P >Default: Currently no default value is given - to this string, unless the value of the <TT + to this string, unless the value of the <VAR CLASS="PARAMETER" -><I ->printing</I -></TT +>printing</VAR > - parameter is <TT + parameter is <CODE CLASS="CONSTANT" ->SYSV</TT +>SYSV</CODE >, in which case the default is :</P ><P ><B @@ -11377,15 +10212,13 @@ CLASS="COMMAND" >lp -i %p-%j -H resume</B ></P ><P ->or if the value of the <TT +>or if the value of the <VAR CLASS="PARAMETER" -><I ->printing</I -></TT +>printing</VAR > parameter - is <TT + is <CODE CLASS="CONSTANT" ->SOFTQ</TT +>SOFTQ</CODE >, then the default is:</P ><P ><B @@ -11412,37 +10245,29 @@ 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 <TT +>If a <VAR CLASS="PARAMETER" -><I ->%p</I -></TT +>%p</VAR > is given then the printer name - is put in its place. A <TT + is put in its place. A <VAR CLASS="PARAMETER" -><I ->%j</I -></TT +>%j</VAR > is replaced with the job number (an integer).</P ><P >Note that it is good practice to include the absolute - path in the <TT + path in the <VAR CLASS="PARAMETER" -><I ->lprm command</I -></TT +>lprm command</VAR > as the PATH may not be available to the server.</P ><P >See also the <A HREF="#PRINTING" -><TT +><VAR CLASS="PARAMETER" -><I >printing - </I -></TT + </VAR ></A > parameter.</P ><P @@ -11450,12 +10275,10 @@ CLASS="PARAMETER" CLASS="emphasis" ><I CLASS="EMPHASIS" ->depends on the setting of <TT +>depends on the setting of <VAR CLASS="PARAMETER" -><I >printing - </I -></TT + </VAR ></I ></SPAN ></P @@ -11524,27 +10347,23 @@ NAME="MAGICOUTPUT" which will contain output created by a magic script (see the <A HREF="#MAGICSCRIPT" -><TT +><VAR CLASS="PARAMETER" -><I ->magic script</I -></TT +>magic script</VAR ></A > parameter below).</P ><P ->Warning: If two clients use the same <TT +>Warning: If two clients use the same <VAR CLASS="PARAMETER" -><I >magic script - </I -></TT + </VAR > in the same directory the output file content is undefined.</P ><P >Default: <B CLASS="COMMAND" ->magic output = <magic script name>.out +>magic output = <magic script name>.out </B ></P ><P @@ -11572,11 +10391,9 @@ NAME="MAGICSCRIPT" >If the script generates output, output will be sent to the file specified by the <A HREF="#MAGICOUTPUT" -><TT +><VAR CLASS="PARAMETER" -><I -> magic output</I -></TT +> magic output</VAR ></A > parameter (see above).</P ><P @@ -11731,11 +10548,9 @@ HREF="#AEN206" >Note that the character to use may be specified using the <A HREF="#MANGLINGCHAR" -><TT +><VAR CLASS="PARAMETER" -><I ->mangling char</I -></TT +>mangling char</VAR > </A > option, if you don't like '~'.</P @@ -11910,20 +10725,16 @@ 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 <TT +>Note that this requires the <VAR CLASS="PARAMETER" -><I ->create mask</I -></TT +>create mask</VAR > 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" -> <TT +> <VAR CLASS="PARAMETER" -><I ->create mask</I -></TT +>create mask</VAR ></A > for details.</P ><P @@ -11942,20 +10753,16 @@ NAME="MAPHIDDEN" >This controls whether DOS style hidden files should be mapped to the UNIX world execute bit.</P ><P ->Note that this requires the <TT +>Note that this requires the <VAR CLASS="PARAMETER" -><I ->create mask</I -></TT +>create mask</VAR > 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" -> <TT +> <VAR CLASS="PARAMETER" -><I ->create mask</I -></TT +>create mask</VAR ></A > for details.</P ><P @@ -11974,20 +10781,16 @@ NAME="MAPSYSTEM" >This controls whether DOS style system files should be mapped to the UNIX group execute bit.</P ><P ->Note that this requires the <TT +>Note that this requires the <VAR CLASS="PARAMETER" -><I ->create mask</I -></TT +>create mask</VAR > 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" -> <TT +> <VAR CLASS="PARAMETER" -><I ->create mask</I -></TT +>create mask</VAR ></A > for details.</P ><P @@ -12006,22 +10809,20 @@ NAME="MAPTOGUEST" >This parameter is only useful in <A HREF="#SECURITY" > security</A -> modes other than <TT +> modes other than <VAR CLASS="PARAMETER" -><I ->security = share</I -></TT +>security = share</VAR > - - i.e. <TT + - i.e. <CODE CLASS="CONSTANT" ->user</TT ->, <TT +>user</CODE +>, <CODE CLASS="CONSTANT" ->server</TT +>server</CODE >, - and <TT + and <CODE CLASS="CONSTANT" ->domain</TT +>domain</CODE >.</P ><P >This parameter can take three different values, which tell @@ -12040,36 +10841,34 @@ CLASS="REFENTRYTITLE" ><UL ><LI ><P -><TT +><CODE CLASS="CONSTANT" ->Never</TT +>Never</CODE > - Means user login requests with an invalid password are rejected. This is the default.</P ></LI ><LI ><P -><TT +><CODE CLASS="CONSTANT" ->Bad User</TT +>Bad User</CODE > - 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" -><TT +><VAR CLASS="PARAMETER" -><I -> guest account</I -></TT +> guest account</VAR ></A >.</P ></LI ><LI ><P -><TT +><CODE CLASS="CONSTANT" ->Bad Password</TT +>Bad Password</CODE > - Means user logins with an invalid password are treated as a guest login and mapped into the <A @@ -12087,22 +10886,18 @@ CLASS="emphasis" CLASS="EMPHASIS" >hate</I ></SPAN -> you if you set the <TT +> you if you set the <VAR CLASS="PARAMETER" -><I >map to - guest</I -></TT + guest</VAR > parameter this way :-).</P ></LI ></UL ><P >Note that this parameter is needed to set up "Guest" - share services when using <TT + share services when using <VAR CLASS="PARAMETER" -><I ->security</I -></TT +>security</VAR > modes other than share. This is because in these modes the name of the resource being requested is <SPAN @@ -12117,9 +10912,9 @@ CLASS="EMPHASIS" 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 <TT + parameter maps to the old compile-time setting of the <CODE CLASS="CONSTANT" -> GUEST_SESSSETUP</TT +> GUEST_SESSSETUP</CODE > value in local.h.</P ><P >Default: <B @@ -12140,12 +10935,10 @@ NAME="MAXCONNECTIONS" ><DD ><P >This option allows the number of simultaneous - connections to a service to be limited. If <TT + connections to a service to be limited. If <VAR CLASS="PARAMETER" -><I >max connections - </I -></TT + </VAR > 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 @@ -12153,11 +10946,9 @@ 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" -><TT +><VAR CLASS="PARAMETER" -><I ->lock directory</I -></TT +>lock directory</VAR ></A > option.</P @@ -12188,23 +10979,19 @@ 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 <TT + result will be bounded by the amount specified in <VAR CLASS="PARAMETER" -><I >max - disk size</I -></TT + disk size</VAR >.</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 <TT +>A <VAR CLASS="PARAMETER" -><I ->max disk size</I -></TT +>max disk size</VAR > of 0 means no limit.</P ><P >Default: <B @@ -12306,12 +11093,10 @@ CLASS="REFENTRYTITLE" > will remote "Out of Space" to the client. See all <A HREF="#TOTALPRINTJOBS" -><TT +><VAR CLASS="PARAMETER" -><I >total - print jobs</I -></TT + print jobs</VAR ></A >. </P @@ -12342,25 +11127,25 @@ NAME="MAXPROTOCOL" ><UL ><LI ><P -><TT +><CODE CLASS="CONSTANT" ->CORE</TT +>CORE</CODE >: Earliest version. No concept of user names.</P ></LI ><LI ><P -><TT +><CODE CLASS="CONSTANT" ->COREPLUS</TT +>COREPLUS</CODE >: Slight improvements on CORE for efficiency.</P ></LI ><LI ><P -><TT +><CODE CLASS="CONSTANT" ->LANMAN1</TT +>LANMAN1</CODE >: First <SPAN CLASS="emphasis" ><I @@ -12372,17 +11157,17 @@ CLASS="EMPHASIS" ></LI ><LI ><P -><TT +><CODE CLASS="CONSTANT" ->LANMAN2</TT +>LANMAN2</CODE >: Updates to Lanman1 protocol. </P ></LI ><LI ><P -><TT +><CODE CLASS="CONSTANT" ->NT1</TT +>NT1</CODE >: Current up to date version of the protocol. Used by Windows NT. Known as CIFS.</P ></LI @@ -12394,12 +11179,10 @@ CLASS="CONSTANT" ><P >See also <A HREF="#MINPROTOCOL" -><TT +><VAR CLASS="PARAMETER" -><I >min - protocol</I -></TT + protocol</VAR ></A ></P ><P @@ -12495,11 +11278,9 @@ CLASS="REFENTRYTITLE" >(8)</SPAN > when acting as a WINS server (<A HREF="#WINSSUPPORT" -> <TT +> <VAR CLASS="PARAMETER" -><I ->wins support = yes</I -></TT +>wins support = yes</VAR ></A >) what the maximum 'time to live' of NetBIOS names that <B @@ -12511,12 +11292,10 @@ CLASS="COMMAND" ><P >See also the <A HREF="#MINWINSTTL" -><TT +><VAR CLASS="PARAMETER" -><I >min - wins ttl</I -></TT + wins ttl</VAR ></A > parameter.</P ><P @@ -12566,7 +11345,7 @@ NAME="MESSAGECOMMAND" ><P ><B CLASS="COMMAND" ->message command = csh -c 'xedit %s;rm %s' &</B +>message command = csh -c 'xedit %s;rm %s' &</B > </P ><P @@ -12582,21 +11361,17 @@ CLASS="EMPHASIS" THAT THIS COMMAND RETURN IMMEDIATELY</I ></SPAN >. That's why I - have the '&' on the end. If it doesn't return immediately then + have the '&' on the end. If it doesn't return immediately then your PCs may freeze when sending messages (they should recover after 30 seconds, hopefully).</P ><P >All messages are delivered as the global guest user. - The command takes the standard substitutions, although <TT + The command takes the standard substitutions, although <VAR CLASS="PARAMETER" -><I -> %u</I -></TT -> won't work (<TT +> %u</VAR +> won't work (<VAR CLASS="PARAMETER" -><I ->%U</I -></TT +>%U</VAR > may be better in this case).</P ><P @@ -12607,31 +11382,25 @@ CLASS="PARAMETER" ><UL ><LI ><P -><TT +><VAR CLASS="PARAMETER" -><I ->%s</I -></TT +>%s</VAR > = the filename containing the message.</P ></LI ><LI ><P -><TT +><VAR CLASS="PARAMETER" -><I ->%t</I -></TT +>%t</VAR > = the destination that the message was sent to (probably the server name).</P ></LI ><LI ><P -><TT +><VAR CLASS="PARAMETER" -><I ->%f</I -></TT +>%f</VAR > = who the message is from.</P ></LI @@ -12646,7 +11415,7 @@ CLASS="PARAMETER" ><B CLASS="COMMAND" >message command = /bin/mail -s 'message from %f on - %m' root < %s; rm %s</B + %m' root < %s; rm %s</B ></P ><P >If you don't have a message command then the message @@ -12673,7 +11442,7 @@ CLASS="EMPHASIS" >Example: <B CLASS="COMMAND" >message command = csh -c 'xedit %s; - rm %s' &</B + rm %s' &</B ></P ></DD ><DT @@ -12685,11 +11454,9 @@ NAME="MINPASSWDLENGTH" ><P >Synonym for <A HREF="#MINPASSWORDLENGTH" -> <TT +> <VAR CLASS="PARAMETER" -><I ->min password length</I -></TT +>min password length</VAR ></A >.</P ></DD @@ -12709,28 +11476,22 @@ CLASS="COMMAND" ><P >See also <A HREF="#UNIXPASSWORDSYNC" -><TT +><VAR CLASS="PARAMETER" -><I >unix - password sync</I -></TT + password sync</VAR ></A >, <A HREF="#PASSWDPROGRAM" -> <TT +> <VAR CLASS="PARAMETER" -><I ->passwd program</I -></TT +>passwd program</VAR ></A > and <A HREF="#PASSWDCHATDEBUG" -><TT +><VAR CLASS="PARAMETER" -><I ->passwd chat debug</I -></TT +>passwd chat debug</VAR > </A >.</P @@ -12754,12 +11515,10 @@ NAME="MINPRINTSPACE" ><P >See also the <A HREF="#PRINTING" -><TT +><VAR CLASS="PARAMETER" -><I >printing - </I -></TT + </VAR ></A > parameter.</P ><P @@ -12784,11 +11543,9 @@ NAME="MINPROTOCOL" lowest SMB protocol dialect than Samba will support. Please refer to the <A HREF="#MAXPROTOCOL" -><TT +><VAR CLASS="PARAMETER" -><I ->max protocol</I -></TT +>max protocol</VAR ></A > parameter for a list of valid protocol names and a brief description @@ -12802,12 +11559,10 @@ CLASS="FILENAME" >If you are viewing this parameter as a security measure, you should also refer to the <A HREF="#LANMANAUTH" -><TT +><VAR CLASS="PARAMETER" -><I >lanman - auth</I -></TT + auth</VAR ></A > parameter. Otherwise, you should never need to change this parameter.</P @@ -12839,11 +11594,9 @@ CLASS="REFENTRYTITLE" > when acting as a WINS server (<A HREF="#WINSSUPPORT" -><TT +><VAR CLASS="PARAMETER" -><I -> wins support = yes</I -></TT +> wins support = yes</VAR ></A >) what the minimum 'time to live' of NetBIOS names that <B @@ -12874,21 +11627,17 @@ NAME="MSDFSPROXY" >Only Dfs roots can act as proxy shares. Take a look at the <A HREF="#MSDFSROOT" -><TT +><VAR CLASS="PARAMETER" -><I ->msdfs root</I -></TT +>msdfs root</VAR ></A > and <A HREF="#HOSTMSDFS" -><TT +><VAR CLASS="PARAMETER" -><I ->host msdfs</I -></TT +>host msdfs</VAR ></A > options to find out how to set up a Dfs root share.</P @@ -12909,9 +11658,9 @@ NAME="MSDFSROOT" Samba is configured and compiled with the <B CLASS="COMMAND" > --with-msdfs</B -> option. If set to <TT +> option. If set to <CODE CLASS="CONSTANT" ->yes</TT +>yes</CODE >, Samba treats the share as a Dfs root and allows clients to browse the distributed file system tree rooted at the share directory. @@ -12930,12 +11679,10 @@ TARGET="_top" ><P >See also <A HREF="#HOSTMSDFS" -><TT +><VAR CLASS="PARAMETER" -><I >host msdfs - </I -></TT + </VAR ></A ></P ><P @@ -12985,9 +11732,9 @@ NAME="NAMERESOLVEORDER" ><UL ><LI ><P -><TT +><CODE CLASS="CONSTANT" ->lmhosts</TT +>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 <A @@ -12999,9 +11746,9 @@ TARGET="_top" ></LI ><LI ><P -><TT +><CODE CLASS="CONSTANT" ->host</TT +>host</CODE > : Do a standard host name to IP address resolution, using the system <TT CLASS="FILENAME" @@ -13019,34 +11766,30 @@ CLASS="FILENAME" ></LI ><LI ><P -><TT +><CODE CLASS="CONSTANT" ->wins</TT +>wins</CODE > : Query a name with the IP address listed in the <A HREF="#WINSSERVER" -><TT +><VAR CLASS="PARAMETER" -><I -> wins server</I -></TT +> wins server</VAR ></A > parameter. If no WINS server has been specified this method will be ignored.</P ></LI ><LI ><P -><TT +><CODE CLASS="CONSTANT" ->bcast</TT +>bcast</CODE > : Do a broadcast on each of the known local interfaces listed in the <A HREF="#INTERFACES" -><TT +><VAR CLASS="PARAMETER" -><I ->interfaces</I -></TT +>interfaces</VAR ></A > parameter. This is the least reliable of the name resolution @@ -13092,12 +11835,10 @@ TARGET="_top" ><P >See also <A HREF="#NETBIOSNAME" -><TT +><VAR CLASS="PARAMETER" -><I >netbios - name</I -></TT + name</VAR ></A >.</P ><P @@ -13130,12 +11871,10 @@ NAME="NETBIOSNAME" ><P >See also <A HREF="#NETBIOSALIASES" -><TT +><VAR CLASS="PARAMETER" -><I >netbios - aliases</I -></TT + aliases</VAR ></A >.</P ><P @@ -13189,11 +11928,9 @@ NAME="NISHOMEDIR" server. When Samba is returning the home share to the client, it will consult the NIS map specified in <A HREF="#HOMEDIRMAP" -> <TT +> <VAR CLASS="PARAMETER" -><I ->homedir map</I -></TT +>homedir map</VAR ></A > and return the server listed there.</P @@ -13229,7 +11966,7 @@ NAME="NONUNIXACCOUNTRANGE" ><P >Default: <B CLASS="COMMAND" ->non unix account range = <empty string> +>non unix account range = <empty string> </B ></P ><P @@ -13275,9 +12012,9 @@ CLASS="REFENTRYTITLE" >smbd</SPAN >(8)</SPAN > will allow Windows NT - clients to connect to the NT SMB specific <TT + clients to connect to the NT SMB specific <CODE CLASS="CONSTANT" ->IPC$</TT +>IPC$</CODE > pipes. This is a developer debugging option and can be left alone.</P @@ -13301,9 +12038,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 <TT + If this option is set to <CODE CLASS="CONSTANT" ->no</TT +>no</CODE > then Samba offers exactly the same DOS error codes that versions prior to Samba 2.2.3 reported.</P @@ -13352,11 +12089,9 @@ 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" -><TT +><VAR CLASS="PARAMETER" -><I ->encrypt passwords = yes</I -></TT +>encrypt passwords = yes</VAR > </A >. The reason is that PAM modules cannot support the challenge/response @@ -13376,20 +12111,16 @@ NAME="ONLYUSER" ><DD ><P >This is a boolean option that controls whether - connections with usernames not in the <TT + connections with usernames not in the <VAR CLASS="PARAMETER" -><I ->user</I -></TT +>user</VAR > 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 <TT + names from the <VAR CLASS="PARAMETER" -><I ->user</I -></TT +>user</VAR > list and is only really useful in <A HREF="#SECURITYEQUALSSHARE" @@ -13403,22 +12134,18 @@ HREF="#SECURITYEQUALSSHARE" CLASS="COMMAND" >user = %S</B -> which means your <TT +> which means your <VAR CLASS="PARAMETER" -><I ->user</I -></TT +>user</VAR > 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" -><TT +><VAR CLASS="PARAMETER" -><I ->user</I -></TT +>user</VAR > </A > parameter.</P @@ -13437,11 +12164,9 @@ NAME="ONLYGUEST" ><P >A synonym for <A HREF="#GUESTONLY" -><TT +><VAR CLASS="PARAMETER" -><I -> guest only</I -></TT +> guest only</VAR ></A >.</P ></DD @@ -13553,39 +12278,31 @@ CLASS="FILENAME" >Oplocks may be selectively turned off on certain files with a share. See the <A HREF="#VETOOPLOCKFILES" -><TT +><VAR CLASS="PARAMETER" -><I -> veto oplock files</I -></TT +> veto oplock files</VAR ></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 - <TT + <VAR CLASS="PARAMETER" -><I ->kernel oplocks</I -></TT +>kernel oplocks</VAR > parameter for details.</P ><P >See also the <A HREF="#KERNELOPLOCKS" -><TT +><VAR CLASS="PARAMETER" -><I >kernel - oplocks</I -></TT + oplocks</VAR ></A > and <A HREF="#LEVEL2OPLOCKS" -><TT +><VAR CLASS="PARAMETER" -><I -> level2 oplocks</I -></TT +> level2 oplocks</VAR ></A > parameters.</P ><P @@ -13641,11 +12358,9 @@ CLASS="REFENTRYTITLE" >nmbd</SPAN >(8)</SPAN > - has a chance of becoming a local master browser for the <TT + has a chance of becoming a local master browser for the <VAR CLASS="PARAMETER" -><I -> WORKGROUP</I -></TT +> WORKGROUP</VAR > in the local broadcast area.</P ><P ><SPAN @@ -13689,8 +12404,8 @@ NAME="OS2DRIVERMAP" path to a file containing a mapping of Windows NT printer driver names to OS/2 printer driver names. The format is:</P ><P -><nt driver name> = <os2 driver - name>.<device name></P +><nt driver name> = <os2 driver + name>.<device name></P ><P >For example, a valid entry using the HP LaserJet 5 printer driver would appear as <B @@ -13710,7 +12425,7 @@ TARGET="_top" ><P >Default: <B CLASS="COMMAND" ->os2 driver map = <empty string> +>os2 driver map = <empty string> </B ></P ></DD @@ -13727,21 +12442,17 @@ NAME="PAMPASSWORDCHANGE" changes when requested by an SMB client instead of the program listed in <A HREF="#PASSWDPROGRAM" -><TT +><VAR CLASS="PARAMETER" -><I ->passwd program</I -></TT +>passwd program</VAR ></A >. It should be possible to enable this without changing your <A HREF="#PASSWDCHAT" -><TT +><VAR CLASS="PARAMETER" -><I ->passwd chat</I -></TT +>passwd chat</VAR ></A > parameter for most setups. @@ -13777,7 +12488,7 @@ CLASS="REFENTRYTITLE" ><P >Default: <B CLASS="COMMAND" ->panic action = <empty string></B +>panic action = <empty string></B ></P ><P >Example: <B @@ -13848,11 +12559,9 @@ CLASS="COMMAND" ><P >See also <A HREF="#NONUNIXACCOUNTRANGE" -> <TT +> <VAR CLASS="PARAMETER" -><I ->non unix account range</I -></TT +>non unix account range</VAR ></A ></P ></LI @@ -13865,11 +12574,9 @@ CLASS="COMMAND" backend. Takes a path to the TDB as an optional argument (defaults to passdb.tdb in the <A HREF="#PRIVATEDIR" -> <TT +> <VAR CLASS="PARAMETER" -><I ->private dir</I -></TT +>private dir</VAR ></A > directory.</P ></LI @@ -13882,21 +12589,17 @@ 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" -> <TT +> <VAR CLASS="PARAMETER" -><I ->private dir</I -></TT +>private dir</VAR ></A > directory.</P ><P >See also <A HREF="#NONUNIXACCOUNTRANGE" -> <TT +> <VAR CLASS="PARAMETER" -><I ->non unix account range</I -></TT +>non unix account range</VAR ></A ></P ></LI @@ -13929,12 +12632,10 @@ CLASS="COMMAND" ><P >See also <A HREF="#NONUNIXACCOUNTRANGE" -> <TT +> <VAR CLASS="PARAMETER" -><I >non unix account - range</I -></TT + range</VAR ></A ></P ><P @@ -13942,18 +12643,14 @@ CLASS="PARAMETER" possible. This may be done using either Start-TLS (see <A HREF="#LDAPSSL" -> <TT +> <VAR CLASS="PARAMETER" -><I ->ldap ssl</I -></TT +>ldap ssl</VAR ></A >) or by - specifying <TT + specifying <VAR CLASS="PARAMETER" -><I ->ldaps://</I -></TT +>ldaps://</VAR > in the URL argument. </P @@ -14050,11 +12747,9 @@ CLASS="REFENTRYTITLE" > uses to determine what to send to the <A HREF="#PASSWDPROGRAM" -><TT +><VAR CLASS="PARAMETER" -><I ->passwd program</I -></TT +>passwd program</VAR > </A > and what to expect back. If the expected output is not @@ -14066,16 +12761,14 @@ CLASS="PARAMETER" ><P >Note that this parameter only is only used if the <A HREF="#UNIXPASSWORDSYNC" -><TT +><VAR CLASS="PARAMETER" -><I >unix - password sync</I -></TT + password sync</VAR ></A -> parameter is set to <TT +> parameter is set to <CODE CLASS="CONSTANT" ->yes</TT +>yes</CODE >. This sequence is then called <SPAN CLASS="emphasis" @@ -14094,25 +12787,23 @@ HREF="#PASSWDPROGRAM" executed on the NIS master. </P ><P ->The string can contain the macro <TT +>The string can contain the macro <VAR CLASS="PARAMETER" -><I ->%n</I -></TT +>%n</VAR > which is substituted for the new password. The chat sequence can also contain the standard - macros <TT + macros <CODE CLASS="CONSTANT" ->\\n</TT ->, <TT +>\\n</CODE +>, <CODE CLASS="CONSTANT" ->\\r</TT ->, <TT +>\\r</CODE +>, <CODE CLASS="CONSTANT" -> \\t</TT -> and <TT +> \\t</CODE +> and <CODE CLASS="CONSTANT" ->\\s</TT +>\\s</CODE > to give line-feed, carriage-return, tab and space. The chat sequence string can also contain a '*' which matches any sequence of characters. @@ -14125,16 +12816,14 @@ CLASS="CONSTANT" ><P >If the <A HREF="#PAMPASSWORDCHANGE" -><TT +><VAR CLASS="PARAMETER" -><I >pam - password change</I -></TT + password change</VAR ></A -> parameter is set to <TT +> parameter is set to <CODE CLASS="CONSTANT" ->yes</TT +>yes</CODE >, 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. @@ -14142,36 +12831,28 @@ CLASS="CONSTANT" ><P >See also <A HREF="#UNIXPASSWORDSYNC" -><TT +><VAR CLASS="PARAMETER" -><I >unix password - sync</I -></TT + sync</VAR ></A >, <A HREF="#PASSWDPROGRAM" -><TT +><VAR CLASS="PARAMETER" -><I -> passwd program</I -></TT +> passwd program</VAR ></A > ,<A HREF="#PASSWDCHATDEBUG" -> <TT +> <VAR CLASS="PARAMETER" -><I ->passwd chat debug</I -></TT +>passwd chat debug</VAR ></A > and <A HREF="#PAMPASSWORDCHANGE" -> <TT +> <VAR CLASS="PARAMETER" -><I ->pam password change</I -></TT +>pam password change</VAR ></A >.</P ><P @@ -14213,11 +12894,9 @@ CLASS="REFENTRYTITLE" > log with a <A HREF="#DEBUGLEVEL" -><TT +><VAR CLASS="PARAMETER" -><I ->debug level</I -></TT +>debug level</VAR ></A > of 100. This is a dangerous option as it will allow plaintext passwords @@ -14225,55 +12904,43 @@ CLASS="PARAMETER" CLASS="COMMAND" >smbd</B > log. It is available to help - Samba admins debug their <TT + Samba admins debug their <VAR CLASS="PARAMETER" -><I ->passwd chat</I -></TT +>passwd chat</VAR > scripts - when calling the <TT + when calling the <VAR CLASS="PARAMETER" -><I ->passwd program</I -></TT +>passwd program</VAR > and should be turned off after this has been done. This option has no effect if the <A HREF="#PAMPASSWORDCHANGE" -><TT +><VAR CLASS="PARAMETER" -><I ->pam password change</I -></TT +>pam password change</VAR ></A > paramter is set. This parameter is off by default.</P ><P >See also <A HREF="#PASSWDCHAT" -><TT +><VAR CLASS="PARAMETER" -><I ->passwd chat</I -></TT +>passwd chat</VAR > </A >, <A HREF="#PAMPASSWORDCHANGE" -><TT +><VAR CLASS="PARAMETER" -><I ->pam password change</I -></TT +>pam password change</VAR > </A >, <A HREF="#PASSWDPROGRAM" -><TT +><VAR CLASS="PARAMETER" -><I ->passwd program</I -></TT +>passwd program</VAR > </A >.</P @@ -14291,11 +12958,9 @@ NAME="PASSWDPROGRAM" ><DD ><P >The name of a program that can be used to set - UNIX user passwords. Any occurrences of <TT + UNIX user passwords. Any occurrences of <VAR CLASS="PARAMETER" -><I ->%u</I -></TT +>%u</VAR > will be replaced with the user name. The user name is checked for existence before calling the password changing program.</P @@ -14318,16 +12983,14 @@ CLASS="emphasis" CLASS="EMPHASIS" >Note</I ></SPAN -> that if the <TT +> that if the <VAR CLASS="PARAMETER" -><I >unix - password sync</I -></TT -> parameter is set to <TT + password sync</VAR +> parameter is set to <CODE CLASS="CONSTANT" >yes - </TT + </CODE > then this program is called <SPAN CLASS="emphasis" ><I @@ -14347,11 +13010,9 @@ CLASS="COMMAND" > will fail to change the SMB password also (this is by design).</P ><P ->If the <TT +>If the <VAR CLASS="PARAMETER" -><I ->unix password sync</I -></TT +>unix password sync</VAR > parameter is set this parameter <SPAN CLASS="emphasis" @@ -14367,25 +13028,21 @@ CLASS="EMPHASIS" >ALL</I ></SPAN > programs called, and must be examined - for security implications. Note that by default <TT + for security implications. Note that by default <VAR CLASS="PARAMETER" -><I >unix - password sync</I -></TT -> is set to <TT + password sync</VAR +> is set to <CODE CLASS="CONSTANT" ->no</TT +>no</CODE >.</P ><P >See also <A HREF="#UNIXPASSWORDSYNC" -><TT +><VAR CLASS="PARAMETER" -><I >unix - password sync</I -></TT + password sync</VAR ></A >.</P ><P @@ -14419,21 +13076,17 @@ 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 <TT +>For example, say the password given was "FRED". If <VAR CLASS="PARAMETER" -><I -> password level</I -></TT +> password level</VAR > is set to 1, the following combinations would be tried if "FRED" failed:</P ><P >"Fred", "fred", "fRed", "frEd","freD"</P ><P ->If <TT +>If <VAR CLASS="PARAMETER" -><I ->password level</I -></TT +>password level</VAR > was set to 2, the following combinations would also be tried: </P ><P @@ -14490,12 +13143,10 @@ CLASS="FILENAME" >The name of the password server is looked up using the parameter <A HREF="#NAMERESOLVEORDER" -><TT +><VAR CLASS="PARAMETER" -><I >name - resolve order</I -></TT + resolve order</VAR ></A > and so may resolved by any method and order described in that parameter.</P @@ -14526,25 +13177,21 @@ CLASS="EMPHASIS" server!</P ><P >The name of the password server takes the standard - substitutions, but probably the only useful one is <TT + substitutions, but probably the only useful one is <VAR CLASS="PARAMETER" -><I >%m - </I -></TT + </VAR >, 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 <TT +>If the <VAR CLASS="PARAMETER" -><I ->security</I -></TT +>security</VAR > parameter is set to - <TT + <CODE CLASS="CONSTANT" ->domain</TT +>domain</CODE >, 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 @@ -14553,11 +13200,9 @@ CLASS="CONSTANT" CLASS="COMMAND" > security = domain</B > is that if you list several hosts in the - <TT + <VAR CLASS="PARAMETER" -><I ->password server</I -></TT +>password server</VAR > option then <B CLASS="COMMAND" >smbd @@ -14565,17 +13210,15 @@ 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 <TT +>If the <VAR CLASS="PARAMETER" -><I ->password server</I -></TT +>password server</VAR > 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 <TT + doing a query for the name <CODE CLASS="CONSTANT" ->WORKGROUP<1C></TT +>WORKGROUP<1C></CODE > and then contacting each server returned in the list of IP addresses from the name resolution source. </P @@ -14586,15 +13229,13 @@ 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 <TT +>If the <VAR CLASS="PARAMETER" -><I ->security</I -></TT +>security</VAR > parameter is - set to <TT + set to <CODE CLASS="CONSTANT" ->server</TT +>server</CODE >, then there are different restrictions that <B CLASS="COMMAND" @@ -14607,11 +13248,9 @@ CLASS="COMMAND" ><LI ><P >You may list several password servers in - the <TT + the <VAR CLASS="PARAMETER" -><I ->password server</I -></TT +>password server</VAR > parameter, however if an <B CLASS="COMMAND" @@ -14642,18 +13281,16 @@ CLASS="COMMAND" ><P >See also the <A HREF="#SECURITY" -><TT +><VAR CLASS="PARAMETER" -><I >security - </I -></TT + </VAR ></A > parameter.</P ><P >Default: <B CLASS="COMMAND" ->password server = <empty string></B +>password server = <empty string></B > </P ><P @@ -14686,18 +13323,14 @@ NAME="PATH" you probably won't get the results you expect if you do otherwise.</P ><P ->Any occurrences of <TT +>Any occurrences of <VAR CLASS="PARAMETER" -><I ->%u</I -></TT +>%u</VAR > in the path will be replaced with the UNIX username that the client is using - on this connection. Any occurrences of <TT + on this connection. Any occurrences of <VAR CLASS="PARAMETER" -><I ->%m</I -></TT +>%m</VAR > will be replaced by the NetBIOS name of the machine they are connecting from. These replacements are very useful for setting @@ -14705,11 +13338,9 @@ CLASS="PARAMETER" ><P >Note that this path will be based on <A HREF="#ROOTDIR" -> <TT +> <VAR CLASS="PARAMETER" -><I ->root dir</I -></TT +>root dir</VAR ></A > if one was specified.</P ><P @@ -14795,11 +13426,9 @@ CLASS="COMMAND" ><P >See also <A HREF="#PREEXEC" -><TT +><VAR CLASS="PARAMETER" -><I ->preexec</I -></TT +>preexec</VAR > </A >.</P @@ -14816,30 +13445,7 @@ CLASS="EMPHASIS" >Example: <B CLASS="COMMAND" >postexec = echo \"%u disconnected from %S - from %m (%I)\" >> /tmp/log</B -></P -></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 + from %m (%I)\" >> /tmp/log</B ></P ></DD ><DT @@ -14859,28 +13465,24 @@ NAME="PREEXEC" ><B CLASS="COMMAND" >preexec = csh -c 'echo \"Welcome to %S!\" | - /usr/local/samba/bin/smbclient -M %m -I %I' & </B + /usr/local/samba/bin/smbclient -M %m -I %I' & </B ></P ><P >Of course, this could get annoying after a while :-)</P ><P >See also <A HREF="#PREEXECCLOSE" -><TT +><VAR CLASS="PARAMETER" -><I >preexec close - </I -></TT + </VAR ></A > and <A HREF="#POSTEXEC" -><TT +><VAR CLASS="PARAMETER" -><I >postexec - </I -></TT + </VAR ></A >.</P ><P @@ -14895,7 +13497,7 @@ CLASS="EMPHASIS" >Example: <B CLASS="COMMAND" >preexec = echo \"%u connected to %S from %m - (%I)\" >> /tmp/log</B + (%I)\" >> /tmp/log</B ></P ></DD ><DT @@ -14908,12 +13510,10 @@ NAME="PREEXECCLOSE" >This boolean option controls whether a non-zero return code from <A HREF="#PREEXEC" -><TT +><VAR CLASS="PARAMETER" -><I >preexec - </I -></TT + </VAR ></A > should close the service being connected to.</P ><P @@ -14936,9 +13536,9 @@ TARGET="_top" > is a preferred master browser for its workgroup.</P ><P ->If this is set to <TT +>If this is set to <CODE CLASS="CONSTANT" ->yes</TT +>yes</CODE >, on startup, <B CLASS="COMMAND" >nmbd</B @@ -14949,11 +13549,9 @@ CLASS="COMMAND" CLASS="COMMAND" ><A HREF="#DOMAINMASTER" -><TT +><VAR CLASS="PARAMETER" -><I -> domain master</I -></TT +> domain master</VAR ></A > = yes</B >, so that <B @@ -14970,11 +13568,9 @@ CLASS="COMMAND" ><P >See also <A HREF="#OSLEVEL" -><TT +><VAR CLASS="PARAMETER" -><I ->os level</I -></TT +>os level</VAR > </A >.</P @@ -14993,11 +13589,9 @@ NAME="PREFEREDMASTER" ><P >Synonym for <A HREF="#PREFERREDMASTER" -><TT +><VAR CLASS="PARAMETER" -><I -> preferred master</I -></TT +> preferred master</VAR ></A > for people who cannot spell :-).</P ></DD @@ -15016,11 +13610,9 @@ NAME="PRELOAD" >Note that if you just want all printers in your printcap file loaded then the <A HREF="#LOADPRINTERS" -> <TT +> <VAR CLASS="PARAMETER" -><I ->load printers</I -></TT +>load printers</VAR ></A > option is easier.</P ><P @@ -15048,12 +13640,10 @@ NAME="PRESERVECASE" with the case that the client passes, or if they are forced to be the <A HREF="#DEFAULTCASE" -><TT +><VAR CLASS="PARAMETER" -><I >default case - </I -></TT + </VAR ></A >.</P ><P @@ -15112,29 +13702,21 @@ CLASS="EMPHASIS" >MUST</I ></SPAN > contain at least - one occurrence of <TT + one occurrence of <VAR CLASS="PARAMETER" -><I ->%s</I -></TT -> or <TT +>%s</VAR +> or <VAR CLASS="PARAMETER" -><I >%f - </I -></TT -> - the <TT + </VAR +> - the <VAR CLASS="PARAMETER" -><I ->%p</I -></TT +>%p</VAR > is optional. At the time - a job is submitted, if no printer name is supplied the <TT + a job is submitted, if no printer name is supplied the <VAR CLASS="PARAMETER" -><I >%p - </I -></TT + </VAR > will be silently removed from the printer command.</P ><P >If specified in the [global] section, the print command given @@ -15146,17 +13728,15 @@ CLASS="PARAMETER" be created but not processed and (most importantly) not removed.</P ><P >Note that printing may fail on some UNIXes from the - <TT + <CODE CLASS="CONSTANT" ->nobody</TT +>nobody</CODE > account. If this happens then create an alternative guest account that can print and set the <A HREF="#GUESTACCOUNT" -><TT +><VAR CLASS="PARAMETER" -><I ->guest account</I -></TT +>guest account</VAR ></A > in the [global] section.</P @@ -15168,7 +13748,7 @@ CLASS="PARAMETER" ><P ><B CLASS="COMMAND" ->print command = echo Printing %s >> +>print command = echo Printing %s >> /tmp/print.log; lpr -P %p %s; rm %s</B ></P ><P @@ -15176,11 +13756,9 @@ 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" -> <TT +> <VAR CLASS="PARAMETER" -><I ->printing</I -></TT +>printing</VAR ></A > parameter.</P ><P @@ -15249,11 +13827,9 @@ NAME="PRINTOK" ><P >Synonym for <A HREF="#PRINTABLE" -> <TT +> <VAR CLASS="PARAMETER" -><I ->printable</I -></TT +>printable</VAR ></A >.</P ></DD @@ -15264,9 +13840,9 @@ NAME="PRINTABLE" >>printable (S)</DT ><DD ><P ->If this parameter is <TT +>If this parameter is <CODE CLASS="CONSTANT" ->yes</TT +>yes</CODE >, then clients may open, write to and submit spool files on the directory specified for the service. </P @@ -15275,12 +13851,10 @@ CLASS="CONSTANT" to the service path (user privileges permitting) via the spooling of print data. The <A HREF="#READONLY" -><TT +><VAR CLASS="PARAMETER" -><I >read only - </I -></TT + </VAR ></A > parameter controls only non-printing access to the resource.</P @@ -15299,11 +13873,9 @@ NAME="PRINTCAP" ><P >Synonym for <A HREF="#PRINTCAPNAME" -><TT +><VAR CLASS="PARAMETER" -><I -> printcap name</I -></TT +> printcap name</VAR ></A >.</P ></DD @@ -15351,11 +13923,9 @@ 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 <TT + Samba (this includes most System V based systems). If <VAR CLASS="PARAMETER" -><I -> printcap name</I -></TT +> printcap name</VAR > is set to <B CLASS="COMMAND" >lpstat</B @@ -15425,7 +13995,7 @@ NAME="PRINTERADMIN" ><P >Default: <B CLASS="COMMAND" ->printer admin = <empty string></B +>printer admin = <empty string></B > </P ><P @@ -15436,214 +14006,6 @@ CLASS="COMMAND" ></DD ><DT ><A -NAME="PRINTERDRIVER" -></A ->>printer driver (S)</DT -><DD -><P -><SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->Note :</I -></SPAN ->This is a deprecated - parameter and will be removed in the next major release - following version 2.2. Please see the instructions in - the <A -HREF="printing.html" -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 -><SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->Note :</I -></SPAN ->This is a deprecated - parameter and will be removed in the next major release - following version 2.2. Please see the instructions in - the <A -HREF="printing.html" -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: <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->None (set in compile).</I -></SPAN -></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 -><SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->Note :</I -></SPAN ->This is a deprecated - parameter and will be removed in the next major release - following version 2.2. Please see the instructions in - the <A -HREF="printing.html" -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 @@ -15660,9 +14022,9 @@ NAME="PRINTERNAME" CLASS="emphasis" ><I CLASS="EMPHASIS" ->none (but may be <TT +>none (but may be <CODE CLASS="CONSTANT" ->lp</TT +>lp</CODE > on many systems)</I ></SPAN @@ -15682,11 +14044,9 @@ NAME="PRINTER" ><P >Synonym for <A HREF="#PRINTERNAME" -><TT +><VAR CLASS="PARAMETER" -><I -> printer name</I -></TT +> printer name</VAR ></A >.</P ></DD @@ -15699,69 +14059,59 @@ NAME="PRINTING" ><P >This parameters controls how printer status information is interpreted on your system. It also affects the - default values for the <TT + default values for the <VAR CLASS="PARAMETER" -><I ->print command</I -></TT +>print command</VAR >, - <TT + <VAR CLASS="PARAMETER" -><I ->lpq command</I -></TT ->, <TT +>lpq command</VAR +>, <VAR CLASS="PARAMETER" -><I >lppause command - </I -></TT ->, <TT + </VAR +>, <VAR CLASS="PARAMETER" -><I ->lpresume command</I -></TT +>lpresume command</VAR >, and - <TT + <VAR CLASS="PARAMETER" -><I ->lprm command</I -></TT +>lprm command</VAR > if specified in the [global] section.</P ><P >Currently nine printing styles are supported. They are - <TT + <CODE CLASS="CONSTANT" ->BSD</TT ->, <TT +>BSD</CODE +>, <CODE CLASS="CONSTANT" ->AIX</TT +>AIX</CODE >, - <TT + <CODE CLASS="CONSTANT" ->LPRNG</TT ->, <TT +>LPRNG</CODE +>, <CODE CLASS="CONSTANT" ->PLP</TT +>PLP</CODE >, - <TT + <CODE CLASS="CONSTANT" ->SYSV</TT ->, <TT +>SYSV</CODE +>, <CODE CLASS="CONSTANT" ->HPUX</TT +>HPUX</CODE >, - <TT + <CODE CLASS="CONSTANT" ->QNX</TT ->, <TT +>QNX</CODE +>, <CODE CLASS="CONSTANT" ->SOFTQ</TT +>SOFTQ</CODE >, - and <TT + and <CODE CLASS="CONSTANT" ->CUPS</TT +>CUPS</CODE >.</P ><P >To see what the defaults are for the other print @@ -15810,11 +14160,9 @@ NAME="PROTOCOL" ><P >Synonym for <A HREF="#MAXPROTOCOL" -> <TT +> <VAR CLASS="PARAMETER" -><I ->max protocol</I -></TT +>max protocol</VAR ></A >.</P ></DD @@ -15827,12 +14175,10 @@ NAME="PUBLIC" ><P >Synonym for <A HREF="#GUESTOK" -><TT +><VAR CLASS="PARAMETER" -><I >guest - ok</I -></TT + ok</VAR ></A >.</P ></DD @@ -15854,11 +14200,9 @@ NAME="QUEUEPAUSECOMMAND" but can be issued from the Printers window under Windows 95 and NT.</P ><P ->If a <TT +>If a <VAR CLASS="PARAMETER" -><I ->%p</I -></TT +>%p</VAR > is given then the printer name is put in its place. Otherwise it is placed at the end of the command. </P @@ -15871,12 +14215,10 @@ CLASS="PARAMETER" CLASS="emphasis" ><I CLASS="EMPHASIS" ->depends on the setting of <TT +>depends on the setting of <VAR CLASS="PARAMETER" -><I >printing - </I -></TT + </VAR ></I ></SPAN ></P @@ -15898,11 +14240,9 @@ NAME="QUEUERESUMECOMMAND" is the command to undo the behavior that is caused by the previous parameter (<A HREF="#QUEUEPAUSECOMMAND" -><TT +><VAR CLASS="PARAMETER" -><I -> queuepause command</I -></TT +> queuepause command</VAR ></A >).</P ><P @@ -15914,11 +14254,9 @@ CLASS="PARAMETER" but can be issued from the Printers window under Windows 95 and NT.</P ><P ->If a <TT +>If a <VAR CLASS="PARAMETER" -><I ->%p</I -></TT +>%p</VAR > is given then the printer name is put in its place. Otherwise it is placed at the end of the command.</P @@ -15933,11 +14271,9 @@ CLASS="emphasis" CLASS="EMPHASIS" >depends on the setting of <A HREF="#PRINTING" -><TT +><VAR CLASS="PARAMETER" -><I ->printing</I -></TT +>printing</VAR ></A ></I ></SPAN @@ -15963,9 +14299,9 @@ TARGET="_top" >smbd(8)</A > will support the "Read Block Multiplex" SMB. This is now rarely used and defaults to - <TT + <CODE CLASS="CONSTANT" ->no</TT +>no</CODE >. You should never need to set this parameter.</P ><P @@ -15985,46 +14321,38 @@ NAME="READLIST" 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" -><TT +><VAR CLASS="PARAMETER" -><I ->read only</I -></TT +>read only</VAR ></A > option is set to. The list can include group names using the syntax described in the <A HREF="#INVALIDUSERS" -><TT +><VAR CLASS="PARAMETER" -><I -> invalid users</I -></TT +> invalid users</VAR ></A > parameter.</P ><P >See also the <A HREF="#WRITELIST" -><TT +><VAR CLASS="PARAMETER" -><I -> write list</I -></TT +> write list</VAR ></A > parameter and the <A HREF="#INVALIDUSERS" -><TT +><VAR CLASS="PARAMETER" -><I ->invalid users</I -></TT +>invalid users</VAR > </A > parameter.</P ><P >Default: <B CLASS="COMMAND" ->read list = <empty string></B +>read list = <empty string></B ></P ><P >Example: <B @@ -16041,17 +14369,15 @@ NAME="READONLY" ><P >An inverted synonym is <A HREF="#WRITEABLE" -> <TT +> <VAR CLASS="PARAMETER" -><I ->writeable</I -></TT +>writeable</VAR ></A >.</P ><P ->If this parameter is <TT +>If this parameter is <CODE CLASS="CONSTANT" ->yes</TT +>yes</CODE >, then users of a service may not create or modify files in the service's directory.</P @@ -16096,11 +14422,9 @@ NAME="READRAW" >In general this parameter should be viewed as a system tuning tool and left severely alone. See also <A HREF="#WRITERAW" -> <TT +> <VAR CLASS="PARAMETER" -><I ->write raw</I -></TT +>write raw</VAR ></A >.</P ><P @@ -16116,11 +14440,9 @@ NAME="READSIZE" >>read size (G)</DT ><DD ><P ->The option <TT +>The option <VAR CLASS="PARAMETER" -><I ->read size</I -></TT +>read size</VAR > affects the overlap of disk reads/writes with network reads/writes. If the amount of data being transferred in several of the SMB @@ -16210,11 +14532,9 @@ CLASS="COMMAND" If you leave out the workgroup name then the one given in the <A HREF="#WORKGROUP" -><TT +><VAR CLASS="PARAMETER" -><I ->workgroup</I -></TT +>workgroup</VAR ></A > parameter is used instead.</P @@ -16235,7 +14555,7 @@ CLASS="FILENAME" ><P >Default: <B CLASS="COMMAND" ->remote announce = <empty string> +>remote announce = <empty string> </B ></P ></DD @@ -16285,7 +14605,7 @@ CLASS="COMMAND" ><P >Default: <B CLASS="COMMAND" ->remote browse sync = <empty string> +>remote browse sync = <empty string> </B ></P ></DD @@ -16298,9 +14618,9 @@ NAME="RESTRICTANONYMOUS" ><P >This is a integer parameter, and mirrors as much as possible the functinality the - <TT + <CODE CLASS="CONSTANT" ->RestrictAnonymous</TT +>RestrictAnonymous</CODE > registry key does on NT/Win2k. </P ><P @@ -16318,11 +14638,9 @@ NAME="ROOT" ><P >Synonym for <A HREF="#ROOTDIRECTORY" -> <TT +> <VAR CLASS="PARAMETER" -><I ->root directory"</I -></TT +>root directory"</VAR ></A >.</P ></DD @@ -16335,11 +14653,9 @@ NAME="ROOTDIR" ><P >Synonym for <A HREF="#ROOTDIRECTORY" -> <TT +> <VAR CLASS="PARAMETER" -><I ->root directory"</I -></TT +>root directory"</VAR ></A >.</P ></DD @@ -16361,28 +14677,22 @@ 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" -><TT +><VAR CLASS="PARAMETER" -><I ->wide links</I -></TT +>wide links</VAR ></A > parameter).</P ><P ->Adding a <TT +>Adding a <VAR CLASS="PARAMETER" -><I ->root directory</I -></TT +>root directory</VAR > 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 <TT + sub-tree specified in the <VAR CLASS="PARAMETER" -><I ->root directory</I -></TT +>root directory</VAR > option, <SPAN CLASS="emphasis" @@ -16393,11 +14703,9 @@ CLASS="EMPHASIS" > 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 <TT + into the <VAR CLASS="PARAMETER" -><I ->root directory</I -></TT +>root directory</VAR > tree. In particular you will need to mirror <TT CLASS="FILENAME" @@ -16424,11 +14732,9 @@ NAME="ROOTPOSTEXEC" >>root postexec (S)</DT ><DD ><P ->This is the same as the <TT +>This is the same as the <VAR CLASS="PARAMETER" -><I ->postexec</I -></TT +>postexec</VAR > parameter except that the command is run as root. This is useful for unmounting filesystems @@ -16436,17 +14742,15 @@ CLASS="PARAMETER" ><P >See also <A HREF="#POSTEXEC" -><TT +><VAR CLASS="PARAMETER" -><I -> postexec</I -></TT +> postexec</VAR ></A >.</P ><P >Default: <B CLASS="COMMAND" ->root postexec = <empty string> +>root postexec = <empty string> </B ></P ></DD @@ -16457,11 +14761,9 @@ NAME="ROOTPREEXEC" >>root preexec (S)</DT ><DD ><P ->This is the same as the <TT +>This is the same as the <VAR CLASS="PARAMETER" -><I ->preexec</I -></TT +>preexec</VAR > parameter except that the command is run as root. This is useful for mounting filesystems (such as CDROMs) when a @@ -16469,25 +14771,21 @@ CLASS="PARAMETER" ><P >See also <A HREF="#PREEXEC" -><TT +><VAR CLASS="PARAMETER" -><I -> preexec</I -></TT +> preexec</VAR ></A > and <A HREF="#PREEXECCLOSE" -> <TT +> <VAR CLASS="PARAMETER" -><I ->preexec close</I -></TT +>preexec close</VAR ></A >.</P ><P >Default: <B CLASS="COMMAND" ->root preexec = <empty string> +>root preexec = <empty string> </B ></P ></DD @@ -16498,29 +14796,23 @@ NAME="ROOTPREEXECCLOSE" >>root preexec close (S)</DT ><DD ><P ->This is the same as the <TT +>This is the same as the <VAR CLASS="PARAMETER" -><I >preexec close - </I -></TT + </VAR > parameter except that the command is run as root.</P ><P >See also <A HREF="#PREEXEC" -><TT +><VAR CLASS="PARAMETER" -><I -> preexec</I -></TT +> preexec</VAR ></A > and <A HREF="#PREEXECCLOSE" -> <TT +> <VAR CLASS="PARAMETER" -><I ->preexec close</I -></TT +>preexec close</VAR ></A >.</P ><P @@ -16611,11 +14903,9 @@ CLASS="COMMAND" >, see the <A HREF="#MAPTOGUEST" -><TT +><VAR CLASS="PARAMETER" -><I ->map to guest</I -></TT +>map to guest</VAR > </A >parameter for details.</P @@ -16632,11 +14922,9 @@ CLASS="EMPHASIS" > where it is offers both user and share level security under different <A HREF="#NETBIOSALIASES" -> <TT +> <VAR CLASS="PARAMETER" -><I ->NetBIOS aliases</I -></TT +>NetBIOS aliases</VAR ></A >. </P ><P @@ -16699,21 +14987,17 @@ CLASS="COMMAND" ><P >If the <A HREF="#GUESTONLY" -><TT +><VAR CLASS="PARAMETER" -><I >guest - only</I -></TT + only</VAR ></A > parameter is set, then all the other stages are missed and only the <A HREF="#GUESTACCOUNT" -> <TT +> <VAR CLASS="PARAMETER" -><I ->guest account</I -></TT +>guest account</VAR ></A > username is checked. </P @@ -16723,11 +15007,9 @@ CLASS="PARAMETER" >Is a username is sent with the share connection request, then this username (after mapping - see <A HREF="#USERNAMEMAP" -><TT +><VAR CLASS="PARAMETER" -><I ->username map</I -></TT +>username map</VAR ></A >), is added as a potential username.</P @@ -16759,39 +15041,31 @@ CLASS="EMPHASIS" ><P >Any users on the <A HREF="#USER" -><TT +><VAR CLASS="PARAMETER" -><I -> user</I -></TT +> user</VAR ></A > list are added as potential usernames. </P ></LI ></UL ><P ->If the <TT +>If the <VAR CLASS="PARAMETER" -><I ->guest only</I -></TT +>guest only</VAR > 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 <TT +>If the <VAR CLASS="PARAMETER" -><I ->guest only</I -></TT +>guest only</VAR > parameter is set, or no username can be determined then if the share is marked - as available to the <TT + as available to the <VAR CLASS="PARAMETER" -><I ->guest account</I -></TT +>guest account</VAR >, then this guest user will be used, otherwise access is denied.</P ><P @@ -16826,37 +15100,29 @@ CLASS="EMPHASIS" 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" -><TT +><VAR CLASS="PARAMETER" -><I ->username map</I -></TT +>username map</VAR ></A > parameter). Encrypted passwords (see the <A HREF="#ENCRYPTPASSWORDS" -> <TT +> <VAR CLASS="PARAMETER" -><I ->encrypted passwords</I -></TT +>encrypted passwords</VAR ></A > parameter) can also be used in this security mode. Parameters such as <A HREF="#USER" -> <TT +> <VAR CLASS="PARAMETER" -><I ->user</I -></TT +>user</VAR ></A > and <A HREF="#GUESTONLY" -> <TT +> <VAR CLASS="PARAMETER" -><I ->guest only</I -></TT +>guest only</VAR ></A > if set are then applied and may change the UNIX user to use on this connection, but only after @@ -16880,20 +15146,16 @@ CLASS="EMPHASIS" guest shares don't work in user level security without allowing the server to automatically map unknown users into the <A HREF="#GUESTACCOUNT" -><TT +><VAR CLASS="PARAMETER" -><I ->guest account</I -></TT +>guest account</VAR ></A >. See the <A HREF="#MAPTOGUEST" -><TT +><VAR CLASS="PARAMETER" -><I ->map to guest</I -></TT +>map to guest</VAR > </A > parameter for details on doing this.</P @@ -16925,16 +15187,14 @@ CLASS="REFENTRYTITLE" > has been used to add this machine into a Windows NT Domain. It expects the <A HREF="#ENCRYPTPASSWORDS" -><TT +><VAR CLASS="PARAMETER" -><I ->encrypted passwords</I -></TT +>encrypted passwords</VAR > </A -> parameter to be set to <TT +> parameter to be set to <CODE CLASS="CONSTANT" ->yes</TT +>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 @@ -16985,20 +15245,16 @@ CLASS="EMPHASIS" guest shares don't work in user level security without allowing the server to automatically map unknown users into the <A HREF="#GUESTACCOUNT" -><TT +><VAR CLASS="PARAMETER" -><I ->guest account</I -></TT +>guest account</VAR ></A >. See the <A HREF="#MAPTOGUEST" -><TT +><VAR CLASS="PARAMETER" -><I ->map to guest</I -></TT +>map to guest</VAR > </A > parameter for details on doing this.</P @@ -17010,20 +15266,16 @@ HREF="#AEN239" ><P >See also the <A HREF="#PASSWORDSERVER" -><TT +><VAR CLASS="PARAMETER" -><I >password - server</I -></TT + server</VAR ></A > parameter and the <A HREF="#ENCRYPTPASSWORDS" -><TT +><VAR CLASS="PARAMETER" -><I ->encrypted passwords</I -></TT +>encrypted passwords</VAR > </A > parameter.</P @@ -17048,17 +15300,15 @@ CLASS="COMMAND" user</B >. It expects the <A HREF="#ENCRYPTPASSWORDS" -><TT +><VAR CLASS="PARAMETER" -><I ->encrypted passwords</I -></TT +>encrypted passwords</VAR > </A > parameter to be set to - <TT + <CODE CLASS="CONSTANT" ->yes</TT +>yes</CODE >, unless the remote server does not support them. However note that if encrypted passwords have been negotiated then Samba cannot @@ -17130,20 +15380,16 @@ CLASS="EMPHASIS" guest shares don't work in user level security without allowing the server to automatically map unknown users into the <A HREF="#GUESTACCOUNT" -><TT +><VAR CLASS="PARAMETER" -><I ->guest account</I -></TT +>guest account</VAR ></A >. See the <A HREF="#MAPTOGUEST" -><TT +><VAR CLASS="PARAMETER" -><I ->map to guest</I -></TT +>map to guest</VAR > </A > parameter for details on doing this.</P @@ -17155,20 +15401,16 @@ HREF="#AEN239" ><P >See also the <A HREF="#PASSWORDSERVER" -><TT +><VAR CLASS="PARAMETER" -><I >password - server</I -></TT + server</VAR ></A > parameter and the <A HREF="#ENCRYPTPASSWORDS" -><TT +><VAR CLASS="PARAMETER" -><I ->encrypted passwords</I -></TT +>encrypted passwords</VAR > </A > parameter.</P @@ -17215,36 +15457,30 @@ CLASS="EMPHASIS" 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 <TT + probably want to leave it set to <CODE CLASS="CONSTANT" ->0777</TT +>0777</CODE >.</P ><P >See also the <A HREF="#FORCEDIRECTORYSECURITYMODE" -> <TT +> <VAR CLASS="PARAMETER" -><I ->force directory security mode</I -></TT +>force directory security mode</VAR ></A >, <A HREF="#DIRECTORYSECURITYMASK" -><TT +><VAR CLASS="PARAMETER" -><I >directory - security mask</I -></TT + security mask</VAR ></A >, <A HREF="#FORCESECURITYMODE" -> <TT +> <VAR CLASS="PARAMETER" -><I ->force security mode</I -></TT +>force security mode</VAR ></A > parameters.</P ><P @@ -17276,19 +15512,15 @@ CLASS="COMMAND" >It also sets what will appear in browse lists next to the machine name.</P ><P ->A <TT +>A <VAR CLASS="PARAMETER" -><I ->%v</I -></TT +>%v</VAR > will be replaced with the Samba version number.</P ><P ->A <TT +>A <VAR CLASS="PARAMETER" -><I ->%h</I -></TT +>%h</VAR > will be replaced with the hostname.</P ><P @@ -17337,11 +15569,9 @@ NAME="SHAREMODES" ><DD ><P >This enables or disables the honoring of - the <TT + the <VAR CLASS="PARAMETER" -><I ->share modes</I -></TT +>share modes</VAR > during a file open. These modes are used by clients to gain exclusive read or write access to a file.</P @@ -17351,26 +15581,26 @@ CLASS="PARAMETER" UNIX doesn't support shared memory (almost all do).</P ><P >The share modes that are enabled by this option are - <TT + <CODE CLASS="CONSTANT" ->DENY_DOS</TT ->, <TT +>DENY_DOS</CODE +>, <CODE CLASS="CONSTANT" ->DENY_ALL</TT +>DENY_ALL</CODE >, - <TT + <CODE CLASS="CONSTANT" ->DENY_READ</TT ->, <TT +>DENY_READ</CODE +>, <CODE CLASS="CONSTANT" ->DENY_WRITE</TT +>DENY_WRITE</CODE >, - <TT + <CODE CLASS="CONSTANT" ->DENY_NONE</TT -> and <TT +>DENY_NONE</CODE +> and <CODE CLASS="CONSTANT" ->DENY_FCB</TT +>DENY_FCB</CODE >. </P ><P @@ -17403,12 +15633,10 @@ NAME="SHORTPRESERVECASE" suitable length, are created upper case, or if they are forced to be the <A HREF="#DEFAULTCASE" -><TT +><VAR CLASS="PARAMETER" -><I >default case - </I -></TT + </VAR ></A >. This option can be use with <A HREF="#PRESERVECASE" @@ -17448,21 +15676,17 @@ 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 - <TT + <VAR CLASS="PARAMETER" -><I ->printer admin</I -></TT +>printer admin</VAR > 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 <TT +>Disabling the <VAR CLASS="PARAMETER" -><I ->show add printer wizard</I -></TT +>show add printer wizard</VAR > parameter will always cause the OpenPrinterEx() on the server to fail. Thus the APW icon will never be displayed. <SPAN @@ -17476,28 +15700,22 @@ CLASS="EMPHASIS" ><P >See also <A HREF="#ADDPRINTERCOMMAND" -><TT +><VAR CLASS="PARAMETER" -><I >addprinter - command</I -></TT + command</VAR ></A >, <A HREF="#DELETEPRINTERCOMMAND" -> <TT +> <VAR CLASS="PARAMETER" -><I ->deleteprinter command</I -></TT +>deleteprinter command</VAR ></A >, <A HREF="#PRINTERADMIN" -><TT +><VAR CLASS="PARAMETER" -><I ->printer admin</I -></TT +>printer admin</VAR ></A ></P ><P @@ -17536,28 +15754,22 @@ CLASS="COMMAND" ><P >%m %t %r %f parameters are expanded</P ><P -><TT +><VAR CLASS="PARAMETER" -><I ->%m</I -></TT +>%m</VAR > will be substituted with the shutdown message sent to the server.</P ><P -><TT +><VAR CLASS="PARAMETER" -><I ->%t</I -></TT +>%t</VAR > will be substituted with the number of seconds to wait before effectively starting the shutdown procedure.</P ><P -><TT +><VAR CLASS="PARAMETER" -><I ->%r</I -></TT +>%r</VAR > will be substituted with the switch <SPAN CLASS="emphasis" @@ -17569,11 +15781,9 @@ CLASS="EMPHASIS" for NT. </P ><P -><TT +><VAR CLASS="PARAMETER" -><I ->%f</I -></TT +>%f</VAR > will be substituted with the switch <SPAN CLASS="emphasis" @@ -17606,18 +15816,16 @@ $time=0 let "time/60" let "time++" -/sbin/shutdown $3 $4 +$time $1 &</PRE +/sbin/shutdown $3 $4 +$time $1 &</PRE > Shutdown does not return so we need to launch it in background. </P ><P >See also <A HREF="#ABORTSHUTDOWNSCRIPT" -><TT +><VAR CLASS="PARAMETER" -><I ->abort shutdown script</I -></TT +>abort shutdown script</VAR ></A >.</P ></DD @@ -17915,11 +16123,9 @@ NAME="STATCACHESIZE" ><DD ><P >This parameter determines the number of - entries in the <TT + entries in the <VAR CLASS="PARAMETER" -><I ->stat cache</I -></TT +>stat cache</VAR >. You should never need to change this parameter.</P ><P @@ -17936,9 +16142,9 @@ NAME="STRICTALLOCATE" ><DD ><P >This is a boolean that controls the handling of - disk space allocation in the server. When this is set to <TT + disk space allocation in the server. When this is set to <CODE CLASS="CONSTANT" ->yes</TT +>yes</CODE > the server will change from UNIX behaviour of not committing real disk storage blocks when a file is extended to the Windows behaviour @@ -17947,15 +16153,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 <TT +>When strict allocate is <CODE CLASS="CONSTANT" ->no</TT +>no</CODE > the server does sparse disk block allocation when a file is extended.</P ><P ->Setting this to <TT +>Setting this to <CODE CLASS="CONSTANT" ->yes</TT +>yes</CODE > can help Samba return out of quota messages on systems that are restricting the disk quota of users.</P @@ -17973,16 +16179,16 @@ NAME="STRICTLOCKING" ><DD ><P >This is a boolean that controls the handling of - file locking in the server. When this is set to <TT + file locking in the server. When this is set to <CODE CLASS="CONSTANT" ->yes</TT +>yes</CODE > 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 <TT +>When strict locking is <CODE CLASS="CONSTANT" ->no</TT +>no</CODE > the server does file lock checks only when the client explicitly asks for them.</P ><P @@ -18011,9 +16217,9 @@ 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 <TT + rarely. Setting this parameter to <CODE CLASS="CONSTANT" ->no</TT +>no</CODE > (the default) means that <SPAN CLASS="CITEREFENTRY" @@ -18030,12 +16236,10 @@ CLASS="REFENTRYTITLE" ><P >See also the <A HREF="#SYNCALWAYS" -><TT +><VAR CLASS="PARAMETER" -><I >sync - always></I -></TT + always></VAR ></A > parameter.</P ><P @@ -18069,40 +16273,36 @@ NAME="SYNCALWAYS" ><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 <TT + the write call returns. If this is <CODE CLASS="CONSTANT" ->no</TT +>no</CODE > 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 <TT + If this is <CODE CLASS="CONSTANT" ->yes</TT +>yes</CODE > 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 <TT + the <VAR CLASS="PARAMETER" -><I ->strict sync</I -></TT +>strict sync</VAR > parameter must be set to - <TT + <CODE CLASS="CONSTANT" ->yes</TT +>yes</CODE > in order for this parameter to have any affect.</P ><P >See also the <A HREF="#STRICTSYNC" -><TT +><VAR CLASS="PARAMETER" -><I >strict - sync</I -></TT + sync</VAR ></A > parameter.</P ><P @@ -18120,21 +16320,21 @@ NAME="SYSLOG" ><P >This parameter maps how Samba debug messages are logged onto the system syslog logging levels. Samba debug - level zero maps onto syslog <TT + level zero maps onto syslog <CODE CLASS="CONSTANT" ->LOG_ERR</TT +>LOG_ERR</CODE >, debug - level one maps onto <TT + level one maps onto <CODE CLASS="CONSTANT" ->LOG_WARNING</TT +>LOG_WARNING</CODE >, debug level - two maps onto <TT + two maps onto <CODE CLASS="CONSTANT" ->LOG_NOTICE</TT +>LOG_NOTICE</CODE >, debug level three - maps onto LOG_INFO. All higher levels are mapped to <TT + maps onto LOG_INFO. All higher levels are mapped to <CODE CLASS="CONSTANT" -> LOG_DEBUG</TT +> LOG_DEBUG</CODE >.</P ><P >This parameter sets the threshold for sending messages @@ -18176,18 +16376,14 @@ TARGET="_top" >winbindd(8)</A > daemon uses this parameter to fill in the home directory for that user. - If the string <TT + If the string <VAR CLASS="PARAMETER" -><I ->%D</I -></TT +>%D</VAR > is present it is substituted - with the user's Windows NT domain name. If the string <TT + with the user's Windows NT domain name. If the string <VAR CLASS="PARAMETER" -><I >%U - </I -></TT + </VAR > is present it is substituted with the user's Windows NT user name.</P ><P @@ -18270,11 +16466,9 @@ NAME="TIMESTAMPLOGS" ><P >Synonym for <A HREF="#DEBUGTIMESTAMP" -><TT +><VAR CLASS="PARAMETER" -><I -> debug timestamp</I -></TT +> debug timestamp</VAR ></A >.</P ></DD @@ -18301,11 +16495,9 @@ CLASS="REFENTRYTITLE" designed as a printing throttle. See also <A HREF="#MAXPRINTJOBS" -><TT +><VAR CLASS="PARAMETER" -><I ->max print jobs</I -></TT +>max print jobs</VAR ></A >. </P @@ -18388,15 +16580,13 @@ NAME="UNIXPASSWORDSYNC" >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 <TT + If this is set to <CODE CLASS="CONSTANT" ->yes</TT -> the program specified in the <TT +>yes</CODE +> the program specified in the <VAR CLASS="PARAMETER" -><I >passwd - program</I -></TT + program</VAR >parameter is called <SPAN CLASS="emphasis" ><I @@ -18410,20 +16600,16 @@ CLASS="EMPHASIS" ><P >See also <A HREF="#PASSWDPROGRAM" -><TT +><VAR CLASS="PARAMETER" -><I >passwd - program</I -></TT + program</VAR ></A >, <A HREF="#PASSWDCHAT" -><TT +><VAR CLASS="PARAMETER" -><I -> passwd chat</I -></TT +> passwd chat</VAR ></A >.</P ><P @@ -18451,27 +16637,25 @@ 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 <TT + file this parameter should be set to <CODE CLASS="CONSTANT" ->no</TT +>no</CODE >.</P ><P >In order for this parameter to work correctly the <A HREF="#ENCRYPTPASSWORDS" -><TT +><VAR CLASS="PARAMETER" -><I ->encrypt passwords</I -></TT +>encrypt passwords</VAR > </A -> parameter must be set to <TT +> parameter must be set to <CODE CLASS="CONSTANT" ->no</TT +>no</CODE > when - this parameter is set to <TT + this parameter is set to <CODE CLASS="CONSTANT" ->yes</TT +>yes</CODE >.</P ><P >Note that even when this parameter is set a user @@ -18551,9 +16735,9 @@ NAME="USEMMAP" >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 <TT + coherent cache, and so this parameter is set to <CODE CLASS="CONSTANT" ->no</TT +>no</CODE > 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 @@ -18567,51 +16751,6 @@ 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 -><SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->NOTE:</I -></SPAN -> 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 @@ -18619,11 +16758,9 @@ NAME="USER" ><P >Synonym for <A HREF="#USERNAME" -><TT +><VAR CLASS="PARAMETER" -><I -> username</I -></TT +> username</VAR ></A >.</P ></DD @@ -18636,11 +16773,9 @@ NAME="USERS" ><P >Synonym for <A HREF="#USERNAME" -><TT +><VAR CLASS="PARAMETER" -><I -> username</I -></TT +> username</VAR ></A >.</P ></DD @@ -18655,30 +16790,24 @@ NAME="USERNAME" list, in which case the supplied password will be tested against each username in turn (left to right).</P ><P ->The <TT +>The <VAR CLASS="PARAMETER" -><I ->username</I -></TT +>username</VAR > 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 <TT +>The <VAR CLASS="PARAMETER" -><I ->username</I -></TT +>username</VAR > 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 - <TT + <VAR CLASS="PARAMETER" -><I ->username</I -></TT +>username</VAR > 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 @@ -18695,12 +16824,10 @@ CLASS="PARAMETER" >To restrict a service to a particular set of users you can use the <A HREF="#VALIDUSERS" -><TT +><VAR CLASS="PARAMETER" -><I >valid users - </I -></TT + </VAR ></A > parameter.</P ><P @@ -18714,7 +16841,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 @@ -18733,7 +16860,7 @@ HREF="#AEN239" >Default: <B CLASS="COMMAND" >The guest account if a guest service, - else <empty string>.</B + else <empty string>.</B ></P ><P >Examples:<B @@ -18760,10 +16887,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 <TT + strange usernames on your UNIX machine, such as <CODE CLASS="CONSTANT" >AstrangeUser - </TT + </CODE >.</P ><P >Default: <B @@ -18813,16 +16940,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 <TT +>For example to map from the name <CODE CLASS="CONSTANT" ->admin</TT +>admin</CODE > - or <TT + or <CODE CLASS="CONSTANT" ->administrator</TT -> to the UNIX name <TT +>administrator</CODE +> to the UNIX name <CODE CLASS="CONSTANT" -> root</TT +> root</CODE > you would use:</P ><P ><B @@ -18830,13 +16957,13 @@ CLASS="COMMAND" >root = admin administrator</B ></P ><P ->Or to map anyone in the UNIX group <TT +>Or to map anyone in the UNIX group <CODE CLASS="CONSTANT" ->system</TT +>system</CODE > - to the UNIX name <TT + to the UNIX name <CODE CLASS="CONSTANT" ->sys</TT +>sys</CODE > you would use:</P ><P ><B @@ -18877,29 +17004,27 @@ guest = *</PRE ></P ><P >Note that the remapping is applied to all occurrences - of usernames. Thus if you connect to \\server\fred and <TT + of usernames. Thus if you connect to \\server\fred and <CODE CLASS="CONSTANT" -> fred</TT -> is remapped to <TT +> fred</CODE +> is remapped to <CODE CLASS="CONSTANT" ->mary</TT +>mary</CODE > then you will actually be connecting to \\server\mary and will need to - supply a password suitable for <TT + supply a password suitable for <CODE CLASS="CONSTANT" ->mary</TT +>mary</CODE > not - <TT + <CODE CLASS="CONSTANT" ->fred</TT +>fred</CODE >. The only exception to this is the username passed to the <A HREF="#PASSWORDSERVER" -><TT +><VAR CLASS="PARAMETER" -><I -> password server</I -></TT +> password server</VAR ></A > (if you have one). The password server will receive whatever username the client supplies without @@ -18931,9 +17056,9 @@ NAME="USESENDFILE" >>use sendfile (S)</DT ><DD ><P ->If this parameter is <TT +>If this parameter is <CODE CLASS="CONSTANT" ->yes</TT +>yes</CODE >, 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 @@ -18959,9 +17084,9 @@ NAME="UTMP" Samba has been configured and compiled with the option <B CLASS="COMMAND" > --with-utmp</B ->. If set to <TT +>. If set to <CODE CLASS="CONSTANT" ->yes</TT +>yes</CODE > 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 @@ -18975,11 +17100,9 @@ CLASS="CONSTANT" ><P >See also the <A HREF="#UTMPDIRECTORY" -><TT +><VAR CLASS="PARAMETER" -><I -> utmp directory</I -></TT +> utmp directory</VAR ></A > parameter.</P ><P @@ -19003,11 +17126,9 @@ 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" -> <TT +> <VAR CLASS="PARAMETER" -><I ->utmp</I -></TT +>utmp</VAR ></A > parameter. By default this is not set, meaning the system will use whatever utmp file the @@ -19049,11 +17170,9 @@ CLASS="COMMAND" See also the <A HREF="#UTMP" -> <TT +> <VAR CLASS="PARAMETER" -><I ->utmp</I -></TT +>utmp</VAR ></A > parameter. By default this is not set, meaning the system will use whatever utmp file the @@ -19084,40 +17203,32 @@ NAME="VALIDUSERS" ><DD ><P >This is a list of users that should be allowed - to login to this service. Names starting with '@', '+' and '&' + to login to this service. Names starting with '@', '+' and '&' are interpreted using the same rules as described in the - <TT + <VAR CLASS="PARAMETER" -><I ->invalid users</I -></TT +>invalid users</VAR > parameter.</P ><P >If this is empty (the default) then any user can login. - If a username is in both this list and the <TT + If a username is in both this list and the <VAR CLASS="PARAMETER" -><I >invalid - users</I -></TT + users</VAR > list then access is denied for that user.</P ><P ->The current servicename is substituted for <TT +>The current servicename is substituted for <VAR CLASS="PARAMETER" -><I >%S - </I -></TT + </VAR >. This is useful in the [homes] section.</P ><P >See also <A HREF="#INVALIDUSERS" -><TT +><VAR CLASS="PARAMETER" -><I >invalid users - </I -></TT + </VAR ></A ></P ><P @@ -19158,11 +17269,9 @@ CLASS="EMPHASIS" > include the unix directory separator '/'.</P ><P ->Note that the <TT +>Note that the <VAR CLASS="PARAMETER" -><I ->case sensitive</I -></TT +>case sensitive</VAR > option is applicable in vetoing files.</P ><P @@ -19177,17 +17286,13 @@ CLASS="EMPHASIS" >fail</I ></SPAN > unless you also set - the <TT + the <VAR CLASS="PARAMETER" -><I ->delete veto files</I -></TT +>delete veto files</VAR > parameter to - <TT + <VAR CLASS="PARAMETER" -><I ->yes</I -></TT +>yes</VAR >.</P ><P >Setting this parameter will affect the performance @@ -19196,20 +17301,16 @@ CLASS="PARAMETER" ><P >See also <A HREF="#HIDEFILES" -><TT +><VAR CLASS="PARAMETER" -><I >hide files - </I -></TT + </VAR ></A > and <A HREF="#CASESENSITIVE" -><TT +><VAR CLASS="PARAMETER" -><I -> case sensitive</I -></TT +> case sensitive</VAR ></A >.</P ><P @@ -19243,11 +17344,9 @@ NAME="VETOOPLOCKFILES" ><P >This parameter is only valid when the <A HREF="#OPLOCKS" -><TT +><VAR CLASS="PARAMETER" -><I ->oplocks</I -></TT +>oplocks</VAR ></A > parameter is turned on for a share. It allows the Samba administrator @@ -19255,11 +17354,9 @@ CLASS="PARAMETER" match a wildcarded list, similar to the wildcarded list used in the <A HREF="#VETOFILES" -><TT +><VAR CLASS="PARAMETER" -><I ->veto files</I -></TT +>veto files</VAR ></A > parameter.</P @@ -19346,11 +17443,9 @@ NAME="VFSOPTIONS" to the vfs layer at initialization time. See also <A HREF="#VFSOBJECT" -><TT +><VAR CLASS="PARAMETER" -><I -> vfs object</I -></TT +> vfs object</VAR ></A >.</P ><P @@ -19452,15 +17547,13 @@ CLASS="COMMAND" CLASS="COMMAND" >endpwent()</B > group of system calls. If - the <TT + the <VAR CLASS="PARAMETER" -><I ->winbind enum users</I -></TT +>winbind enum users</VAR > parameter is - <TT + <CODE CLASS="CONSTANT" ->no</TT +>no</CODE >, calls to the <B CLASS="COMMAND" >getpwent</B @@ -19510,15 +17603,13 @@ CLASS="COMMAND" CLASS="COMMAND" >endgrent()</B > group of system calls. If - the <TT + the <VAR CLASS="PARAMETER" -><I ->winbind enum groups</I -></TT +>winbind enum groups</VAR > parameter is - <TT + <CODE CLASS="CONSTANT" ->no</TT +>no</CODE >, calls to the <B CLASS="COMMAND" >getgrent()</B @@ -19561,7 +17652,7 @@ CLASS="REFENTRYTITLE" ><P >Default: <B CLASS="COMMAND" ->winbind gid = <empty string> +>winbind gid = <empty string> </B ></P ><P @@ -19578,17 +17669,13 @@ NAME="WINBINDSEPARATOR" ><DD ><P >This parameter allows an admin to define the character - used when listing a username of the form of <TT + used when listing a username of the form of <VAR CLASS="REPLACEABLE" -><I >DOMAIN - </I -></TT ->\<TT + </VAR +>\<VAR CLASS="REPLACEABLE" -><I ->user</I -></TT +>user</VAR >. This parameter is only applicable when using the <TT CLASS="FILENAME" @@ -19634,7 +17721,7 @@ CLASS="REFENTRYTITLE" ><P >Default: <B CLASS="COMMAND" ->winbind uid = <empty string> +>winbind uid = <empty string> </B ></P ><P @@ -19664,7 +17751,7 @@ CLASS="REFENTRYTITLE" ><P >Default: <B CLASS="COMMAND" ->winbind use default domain = <no> +>winbind use default domain = <no> </B ></P ><P @@ -19751,9 +17838,9 @@ TARGET="_top" >nmbd(8)</A > will respond to broadcast name queries on behalf of other hosts. You may need to set this - to <TT + to <CODE CLASS="CONSTANT" ->yes</TT +>yes</CODE > for some older clients.</P ><P >Default: <B @@ -19825,9 +17912,9 @@ CLASS="REFENTRYTITLE" >nmbd</SPAN >(8)</SPAN > process in Samba will act as a WINS server. You should - not set this to <TT + not set this to <CODE CLASS="CONSTANT" ->yes</TT +>yes</CODE > unless you have a multi-subnetted network and you wish a particular <B CLASS="COMMAND" @@ -19839,9 +17926,9 @@ CLASS="emphasis" CLASS="EMPHASIS" >NEVER</I ></SPAN -> set this to <TT +> set this to <CODE CLASS="CONSTANT" ->yes</TT +>yes</CODE > on more than one machine in your network.</P ><P @@ -19890,11 +17977,9 @@ NAME="WRITABLE" ><P >Synonym for <A HREF="#WRITEABLE" -><TT +><VAR CLASS="PARAMETER" -><I -> writeable</I -></TT +> writeable</VAR ></A > for people who can't spell :-).</P ></DD @@ -19953,11 +18038,9 @@ NAME="WRITELIST" 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" -><TT +><VAR CLASS="PARAMETER" -><I ->read only</I -></TT +>read only</VAR ></A > option is set to. The list can include group names using the @@ -19968,18 +18051,16 @@ CLASS="PARAMETER" ><P >See also the <A HREF="#READLIST" -><TT +><VAR CLASS="PARAMETER" -><I >read list - </I -></TT + </VAR ></A > option.</P ><P >Default: <B CLASS="COMMAND" ->write list = <empty string> +>write list = <empty string> </B ></P ><P @@ -20022,11 +18103,9 @@ NAME="WRITEOK" ><P >Inverted synonym for <A HREF="#READONLY" -><TT +><VAR CLASS="PARAMETER" -><I -> read only</I -></TT +> read only</VAR ></A >.</P ></DD @@ -20055,11 +18134,9 @@ NAME="WRITEABLE" ><P >Inverted synonym for <A HREF="#READONLY" -><TT +><VAR CLASS="PARAMETER" -><I -> read only</I -></TT +> read only</VAR ></A >.</P ></DD @@ -20069,7 +18146,7 @@ CLASS="PARAMETER" ><DIV CLASS="REFSECT1" ><A -NAME="AEN6323" +NAME="AEN6228" ></A ><H2 >WARNINGS</H2 @@ -20100,7 +18177,7 @@ CLASS="REFENTRYTITLE" ><DIV CLASS="REFSECT1" ><A -NAME="AEN6331" +NAME="AEN6236" ></A ><H2 >VERSION</H2 @@ -20110,7 +18187,7 @@ NAME="AEN6331" ><DIV CLASS="REFSECT1" ><A -NAME="AEN6334" +NAME="AEN6239" ></A ><H2 >SEE ALSO</H2 @@ -20174,7 +18251,7 @@ CLASS="REFENTRYTITLE" ><DIV CLASS="REFSECT1" ><A -NAME="AEN6364" +NAME="AEN6269" ></A ><H2 >AUTHOR</H2 diff --git a/docs/htmldocs/smbcacls.1.html b/docs/htmldocs/smbcacls.1.html index 66dbf8d2f9..7500bdaeea 100644 --- a/docs/htmldocs/smbcacls.1.html +++ b/docs/htmldocs/smbcacls.1.html @@ -5,7 +5,7 @@ >smbcacls</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"></HEAD +CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD ><BODY CLASS="REFENTRY" BGCOLOR="#FFFFFF" @@ -134,11 +134,9 @@ CLASS="REFENTRYTITLE" ><DD ><P >The owner of a file or directory can be changed - to the name given using the <TT + to the name given using the <VAR CLASS="PARAMETER" -><I ->-C</I -></TT +>-C</VAR > 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 @@ -151,11 +149,9 @@ CLASS="PARAMETER" ><DD ><P >The group owner of a file or directory can - be changed to the name given using the <TT + be changed to the name given using the <VAR CLASS="PARAMETER" -><I ->-G</I -></TT +>-G</VAR > 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. @@ -198,10 +194,10 @@ NAME="AEN79" ><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 @@ -229,30 +225,30 @@ ACL:<sid or name>:<type>/<flags>/<mask></PRE ><UL ><LI ><P -><TT +><CODE CLASS="CONSTANT" ->#define SEC_ACE_FLAG_OBJECT_INHERIT 0x1</TT +>#define SEC_ACE_FLAG_OBJECT_INHERIT 0x1</CODE ></P ></LI ><LI ><P -><TT +><CODE CLASS="CONSTANT" ->#define SEC_ACE_FLAG_CONTAINER_INHERIT 0x2</TT +>#define SEC_ACE_FLAG_CONTAINER_INHERIT 0x2</CODE ></P ></LI ><LI ><P -><TT +><CODE CLASS="CONSTANT" ->#define SEC_ACE_FLAG_NO_PROPAGATE_INHERIT 0x4</TT +>#define SEC_ACE_FLAG_NO_PROPAGATE_INHERIT 0x4</CODE ></P ></LI ><LI ><P -><TT +><CODE CLASS="CONSTANT" ->#define SEC_ACE_FLAG_INHERIT_ONLY 0x8</TT +>#define SEC_ACE_FLAG_INHERIT_ONLY 0x8</CODE ></P ></LI ></UL diff --git a/docs/htmldocs/smbclient.1.html b/docs/htmldocs/smbclient.1.html index 8ae4f84fe3..4a287acf1d 100644 --- a/docs/htmldocs/smbclient.1.html +++ b/docs/htmldocs/smbclient.1.html @@ -5,7 +5,7 @@ >smbclient</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"></HEAD +CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD ><BODY CLASS="REFENTRY" BGCOLOR="#FFFFFF" @@ -38,7 +38,7 @@ 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] [-k]</P ></DIV ><DIV CLASS="REFSECT1" @@ -94,18 +94,14 @@ CLASS="VARIABLELIST" <TT CLASS="FILENAME" >//server/service</TT -> where <TT +> where <VAR CLASS="PARAMETER" -><I >server - </I -></TT + </VAR > is the NetBIOS name of the SMB/CIFS server - offering the desired service and <TT + offering the desired service and <VAR CLASS="PARAMETER" -><I ->service</I -></TT +>service</VAR > is the name of the service offered. Thus to connect to the service "printer" on the SMB/CIFS server "smbserver", @@ -122,11 +118,9 @@ CLASS="FILENAME" </P ><P >The server name is looked up according to either - the <TT + the <VAR CLASS="PARAMETER" -><I ->-R</I -></TT +>-R</VAR > parameter to <B CLASS="COMMAND" >smbclient</B @@ -148,27 +142,21 @@ CLASS="REFENTRYTITLE" ><P >The password required to access the specified service on the specified server. If this parameter is - supplied, the <TT + supplied, the <VAR CLASS="PARAMETER" -><I ->-N</I -></TT +>-N</VAR > 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 <TT + a password to the <VAR CLASS="PARAMETER" -><I ->-U</I -></TT +>-U</VAR > option (see - below)) and the <TT + below)) and the <VAR CLASS="PARAMETER" -><I ->-N</I -></TT +>-N</VAR > option is not specified, the client will prompt for a password, even if the desired service does not require one. (If no password is @@ -212,7 +200,7 @@ CLASS="REFENTRYTITLE" options. </P ></DD ><DT ->-R <name resolve order></DT +>-R <name resolve order></DT ><DD ><P >This option is used by the programs in the Samba @@ -227,9 +215,9 @@ CLASS="REFENTRYTITLE" ><UL ><LI ><P -><TT +><CODE CLASS="CONSTANT" ->lmhosts</TT +>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 @@ -244,9 +232,9 @@ CLASS="REFENTRYTITLE" ></LI ><LI ><P -><TT +><CODE CLASS="CONSTANT" ->host</TT +>host</CODE >: Do a standard host name to IP address resolution, using the system <TT CLASS="FILENAME" @@ -264,31 +252,27 @@ CLASS="FILENAME" ></LI ><LI ><P -><TT +><CODE CLASS="CONSTANT" ->wins</TT +>wins</CODE >: Query a name with - the IP address listed in the <TT + the IP address listed in the <VAR CLASS="PARAMETER" -><I ->wins server</I -></TT +>wins server</VAR > parameter. If no WINS server has been specified this method will be ignored.</P ></LI ><LI ><P -><TT +><CODE CLASS="CONSTANT" ->bcast</TT +>bcast</CODE >: Do a broadcast on each of the known local interfaces listed in the - <TT + <VAR CLASS="PARAMETER" -><I ->interfaces</I -></TT +>interfaces</VAR > parameter. This is the least reliable of the name resolution methods as it depends on the target host being on a locally @@ -307,12 +291,10 @@ CLASS="REFENTRYTITLE" (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 <TT + this parameter or any entry in the <VAR CLASS="PARAMETER" -><I >name resolve order - </I -></TT + </VAR > parameter of the <SPAN CLASS="CITEREFENTRY" ><SPAN @@ -354,25 +336,19 @@ CLASS="FILENAME" > to the machine FRED. </P ><P ->You may also find the <TT +>You may also find the <VAR CLASS="PARAMETER" -><I ->-U</I -></TT +>-U</VAR > and - <TT + <VAR CLASS="PARAMETER" -><I ->-I</I -></TT +>-I</VAR > options useful, as they allow you to control the FROM and TO parts of the message. </P ><P ->See the <TT +>See the <VAR CLASS="PARAMETER" -><I ->message command</I -></TT +>message command</VAR > parameter in the <SPAN CLASS="CITEREFENTRY" ><SPAN @@ -441,11 +417,9 @@ CLASS="EMPHASIS" >-d debuglevel</DT ><DD ><P -><TT +><VAR CLASS="REPLACEABLE" -><I ->debuglevel</I -></TT +>debuglevel</VAR > is an integer from 0 to 10, or the letter 'A'. </P ><P @@ -463,11 +437,9 @@ CLASS="REPLACEABLE" 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 + cryptic. If <VAR CLASS="REPLACEABLE" -><I ->debuglevel</I -></TT +>debuglevel</VAR > is set to the letter 'A', then <SPAN CLASS="emphasis" ><I @@ -505,11 +477,9 @@ CLASS="FILENAME" >-l logfilename</DT ><DD ><P ->If specified, <TT +>If specified, <VAR CLASS="REPLACEABLE" -><I ->logfilename</I -></TT +>logfilename</VAR > specifies a base filename into which operational data from the running client will be logged. </P @@ -536,21 +506,17 @@ CLASS="FILENAME" >-I IP-address</DT ><DD ><P -><TT +><VAR CLASS="REPLACEABLE" -><I ->IP address</I -></TT +>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 <TT + mechanism described above in the <VAR CLASS="PARAMETER" -><I ->name resolve order</I -></TT +>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 @@ -578,19 +544,19 @@ CLASS="PARAMETER" ><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 + will first check the <VAR CLASS="ENVAR" ->USER</TT +>USER</VAR > environment variable, then the - <TT + <VAR CLASS="ENVAR" ->LOGNAME</TT +>LOGNAME</VAR > 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 + variables are not found, the username <CODE CLASS="CONSTANT" ->GUEST</TT +>GUEST</CODE > is used. </P ><P @@ -599,9 +565,9 @@ CLASS="CONSTANT" CLASS="COMMAND" >smbclient</B > will look for - a <TT + a <VAR CLASS="ENVAR" ->PASSWD</TT +>PASSWD</VAR > environment variable from which to read the password. </P ><P @@ -611,17 +577,15 @@ CLASS="ENVAR" 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 + <VAR CLASS="PARAMETER" -><I ->-A</I -></TT +>-A</VAR > for more details. </P ><P >Be cautious about including passwords in scripts or in - the <TT + the <VAR CLASS="ENVAR" ->PASSWD</TT +>PASSWD</VAR > environment variable. Also, on many systems the command line of a running process may be seen via the <B @@ -645,9 +609,9 @@ CLASS="COMMAND" ><P ><PRE CLASS="PROGRAMLISTING" ->username = <value> -password = <value> -domain = <value></PRE +>username = <value> +password = <value> +domain = <value></PRE ></P ><P >If the domain parameter is missing the current workgroup name @@ -663,12 +627,10 @@ domain = <value></PRE CLASS="COMMAND" >smbclient -L host</B -> and a list should appear. The <TT +> and a list should appear. The <VAR CLASS="PARAMETER" -><I >-I - </I -></TT + </VAR > 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 @@ -747,39 +709,31 @@ CLASS="COMMAND" ><UL ><LI ><P -><TT +><VAR CLASS="PARAMETER" -><I ->c</I -></TT +>c</VAR > - 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 - <TT + <VAR CLASS="PARAMETER" -><I ->x</I -></TT +>x</VAR > flag. </P ></LI ><LI ><P -><TT +><VAR CLASS="PARAMETER" -><I ->x</I -></TT +>x</VAR > - 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 <TT + input. Mutually exclusive with the <VAR CLASS="PARAMETER" -><I ->c</I -></TT +>c</VAR > flag. Restored files have their creation times (mtime) set to the date saved in the tar file. Directories currently do not get @@ -787,11 +741,9 @@ CLASS="PARAMETER" ></LI ><LI ><P -><TT +><VAR CLASS="PARAMETER" -><I ->I</I -></TT +>I</VAR > - 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 @@ -800,28 +752,22 @@ CLASS="PARAMETER" ></LI ><LI ><P -><TT +><VAR CLASS="PARAMETER" -><I ->X</I -></TT +>X</VAR > - 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 <TT + See <VAR CLASS="PARAMETER" -><I ->r</I -></TT +>r</VAR > below. </P ></LI ><LI ><P -><TT +><VAR CLASS="PARAMETER" -><I ->b</I -></TT +>b</VAR > - 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. @@ -829,38 +775,30 @@ CLASS="PARAMETER" ></LI ><LI ><P -><TT +><VAR CLASS="PARAMETER" -><I ->g</I -></TT +>g</VAR > - Incremental. Only back up files that have the archive bit set. Useful only with the - <TT + <VAR CLASS="PARAMETER" -><I ->c</I -></TT +>c</VAR > flag. </P ></LI ><LI ><P -><TT +><VAR CLASS="PARAMETER" -><I ->q</I -></TT +>q</VAR > - Quiet. Keeps tar from printing diagnostics as it works. This is the same as tarmode quiet. </P ></LI ><LI ><P -><TT +><VAR CLASS="PARAMETER" -><I ->r</I -></TT +>r</VAR > - Regular expression include or exclude. Uses regular expression matching for excluding or excluding files if compiled with HAVE_REGEX_H. @@ -870,41 +808,31 @@ CLASS="PARAMETER" ></LI ><LI ><P -><TT +><VAR CLASS="PARAMETER" -><I ->N</I -></TT +>N</VAR > - 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 - <TT + <VAR CLASS="PARAMETER" -><I ->c</I -></TT +>c</VAR > flag. </P ></LI ><LI ><P -><TT +><VAR CLASS="PARAMETER" -><I ->a</I -></TT +>a</VAR > - Set archive bit. Causes the archive bit to be reset when a file is backed up. Useful with the - <TT + <VAR CLASS="PARAMETER" -><I ->g</I -></TT -> and <TT +>g</VAR +> and <VAR CLASS="PARAMETER" -><I ->c</I -></TT +>c</VAR > flags. </P ></LI @@ -1016,16 +944,12 @@ CLASS="COMMAND" ><DD ><P >command string is a semicolon-separated list of - commands to be executed instead of prompting from stdin. <TT + commands to be executed instead of prompting from stdin. <VAR CLASS="PARAMETER" -><I -> -N</I -></TT -> is implied by <TT +> -N</VAR +> is implied by <VAR CLASS="PARAMETER" -><I ->-c</I -></TT +>-c</VAR >.</P ><P >This is particularly useful in scripts and for printing stdin @@ -1056,9 +980,9 @@ NAME="AEN336" >Once the client is running, the user is presented with a prompt : </P ><P -><TT +><SAMP CLASS="PROMPT" ->smb:\> </TT +>smb:\> </SAMP ></P ><P >The backslash ("\\") indicates the current working directory @@ -1078,7 +1002,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 @@ -1096,11 +1020,9 @@ CLASS="VARIABLELIST" >? [command]</DT ><DD ><P ->If <TT +>If <VAR CLASS="REPLACEABLE" -><I ->command</I -></TT +>command</VAR > 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 @@ -1110,11 +1032,9 @@ CLASS="REPLACEABLE" >! [shell command]</DT ><DD ><P ->If <TT +>If <VAR CLASS="REPLACEABLE" -><I ->shell command</I -></TT +>shell command</VAR > 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. @@ -1169,27 +1089,23 @@ 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 <TT + to delete all files matching <VAR CLASS="REPLACEABLE" -><I ->mask</I -></TT +>mask</VAR > 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 <TT +>A list of the files matching <VAR CLASS="REPLACEABLE" -><I ->mask</I -></TT +>mask</VAR > in the current working directory on the server will be retrieved from the server and displayed. </P @@ -1202,7 +1118,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 @@ -1230,11 +1146,9 @@ CLASS="COMMAND" >lcd [directory name]</DT ><DD ><P ->If <TT +>If <VAR CLASS="REPLACEABLE" -><I ->directory name</I -></TT +>directory name</VAR > is specified, the current working directory on the local machine will be changed to the directory specified. This operation will fail if for any @@ -1267,13 +1181,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 @@ -1299,28 +1213,24 @@ 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 <TT +>Copy all files matching <VAR CLASS="REPLACEABLE" -><I ->mask</I -></TT +>mask</VAR > from the server to the machine running the client. </P ><P ->Note that <TT +>Note that <VAR CLASS="REPLACEABLE" -><I ->mask</I -></TT +>mask</VAR > 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 @@ -1330,30 +1240,26 @@ 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 <TT +>Copy all files matching <VAR CLASS="REPLACEABLE" -><I ->mask</I -></TT +>mask</VAR > in the current working directory on the local machine to the current working directory on the server. </P ><P ->Note that <TT +>Note that <VAR CLASS="REPLACEABLE" -><I ->mask</I -></TT +>mask</VAR > 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 @@ -1363,7 +1269,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 @@ -1372,7 +1278,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 @@ -1392,7 +1298,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 @@ -1424,7 +1330,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 @@ -1449,26 +1355,24 @@ CLASS="COMMAND" using the mask command will be ignored. </P ></DD ><DT ->rm <mask></DT +>rm <mask></DT ><DD ><P ->Remove all files matching <TT +>Remove all files matching <VAR CLASS="REPLACEABLE" -><I ->mask</I -></TT +>mask</VAR > 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 @@ -1493,15 +1397,13 @@ CLASS="COMMAND" </P ></DD ><DT ->tar <c|x>[IXbgNa]</DT +>tar <c|x>[IXbgNa]</DT ><DD ><P ->Performs a tar operation - see the <TT +>Performs a tar operation - see the <VAR CLASS="PARAMETER" -><I >-T - </I -></TT + </VAR > 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 @@ -1509,20 +1411,18 @@ 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 - <TT + <VAR CLASS="REPLACEABLE" -><I ->blocksize</I -></TT +>blocksize</VAR >*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 @@ -1564,25 +1464,25 @@ NAME="AEN532" ><H2 >ENVIRONMENT VARIABLES</H2 ><P ->The variable <TT +>The variable <VAR CLASS="ENVAR" ->USER</TT +>USER</VAR > 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 <TT +>The variable <VAR CLASS="ENVAR" ->PASSWD</TT +>PASSWD</VAR > 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 <TT +>The variable <VAR CLASS="ENVAR" ->LIBSMB_PROG</TT +>LIBSMB_PROG</VAR > may contain the path, executed with system(), which the client should connect to instead of connecting to a server. This functionality is primarily diff --git a/docs/htmldocs/smbcontrol.1.html b/docs/htmldocs/smbcontrol.1.html index 25c8e33e08..dcea1b564a 100644 --- a/docs/htmldocs/smbcontrol.1.html +++ b/docs/htmldocs/smbcontrol.1.html @@ -5,7 +5,7 @@ >smbcontrol</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"></HEAD +CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD ><BODY CLASS="REFENTRY" BGCOLOR="#FFFFFF" @@ -109,31 +109,23 @@ CLASS="VARIABLELIST" >destination</DT ><DD ><P ->One of <TT +>One of <VAR CLASS="PARAMETER" -><I ->nmbd</I -></TT ->, <TT +>nmbd</VAR +>, <VAR CLASS="PARAMETER" -><I ->smbd</I -></TT +>smbd</VAR > or a process ID.</P ><P ->The <TT +>The <VAR CLASS="PARAMETER" -><I ->smbd</I -></TT +>smbd</VAR > destination causes the message to "broadcast" to all smbd daemons.</P ><P ->The <TT +>The <VAR CLASS="PARAMETER" -><I ->nmbd</I -></TT +>nmbd</VAR > destination causes the message to be sent to the nmbd daemon specified in the <TT @@ -148,39 +140,39 @@ CLASS="FILENAME" >message-type</DT ><DD ><P ->One of: <TT +>One of: <CODE CLASS="CONSTANT" ->close-share</TT +>close-share</CODE >, - <TT + <CODE CLASS="CONSTANT" ->debug</TT +>debug</CODE >, - <TT + <CODE CLASS="CONSTANT" ->force-election</TT ->, <TT +>force-election</CODE +>, <CODE CLASS="CONSTANT" >ping - </TT ->, <TT + </CODE +>, <CODE CLASS="CONSTANT" ->profile</TT ->, <TT +>profile</CODE +>, <CODE CLASS="CONSTANT" -> debuglevel</TT ->, <TT +> debuglevel</CODE +>, <CODE CLASS="CONSTANT" ->profilelevel</TT +>profilelevel</CODE >, - or <TT + or <CODE CLASS="CONSTANT" ->printnotify</TT +>printnotify</CODE >.</P ><P ->The <TT +>The <CODE CLASS="CONSTANT" ->close-share</TT +>close-share</CODE > 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 @@ -188,25 +180,25 @@ CLASS="CONSTANT" 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 + This message can only be sent to <CODE CLASS="CONSTANT" ->smbd</TT +>smbd</CODE >.</P ><P ->The <TT +>The <CODE CLASS="CONSTANT" ->debug</TT +>debug</CODE > 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 ->The <TT +>The <CODE CLASS="CONSTANT" ->force-election</TT +>force-election</CODE > message-type can only be - sent to the <TT + sent to the <CODE CLASS="CONSTANT" ->nmbd</TT +>nmbd</CODE > destination. This message causes the <B CLASS="COMMAND" @@ -214,17 +206,17 @@ CLASS="COMMAND" > daemon to force a new browse master election.</P ><P ->The <TT +>The <CODE CLASS="CONSTANT" ->ping</TT +>ping</CODE > 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 ->The <TT +>The <CODE CLASS="CONSTANT" ->profile</TT +>profile</CODE > 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 @@ -233,25 +225,25 @@ CLASS="CONSTANT" disabled), and "flush" to zero the current profile stats. This can be sent to any smbd or nmbd destinations.</P ><P ->The <TT +>The <CODE CLASS="CONSTANT" ->debuglevel</TT +>debuglevel</CODE > 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 ->The <TT +>The <CODE CLASS="CONSTANT" ->profilelevel</TT +>profilelevel</CODE > 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 +>The <CODE CLASS="CONSTANT" ->printnotify</TT +>printnotify</CODE > 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 @@ -308,9 +300,9 @@ CLASS="VARIABLELIST" event has occured. It doesn't actually cause the event to happen. - This message can only be sent to <TT + This message can only be sent to <CODE CLASS="CONSTANT" ->smbd</TT +>smbd</CODE >. </P ></DD diff --git a/docs/htmldocs/smbd.8.html b/docs/htmldocs/smbd.8.html index 47788cdb36..6f1cb8c057 100644 --- a/docs/htmldocs/smbd.8.html +++ b/docs/htmldocs/smbd.8.html @@ -5,7 +5,7 @@ >smbd</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"></HEAD +CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD ><BODY CLASS="REFENTRY" BGCOLOR="#FFFFFF" @@ -37,7 +37,7 @@ NAME="AEN8" ><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" @@ -227,14 +227,12 @@ CLASS="COMMAND" Samba was built.</P ></DD ><DT ->-d <debug level></DT +>-d <debug level></DT ><DD ><P -><TT +><VAR CLASS="REPLACEABLE" -><I ->debuglevel</I -></TT +>debuglevel</VAR > is an integer from 0 to 10. The default value if this parameter is not specified is zero.</P @@ -256,12 +254,10 @@ CLASS="REPLACEABLE" override the <A HREF="smb.conf.5.html#loglevel" TARGET="_top" -><TT +><VAR CLASS="PARAMETER" -><I >log - level</I -></TT + level</VAR ></A > parameter in the <SPAN CLASS="CITEREFENTRY" @@ -272,15 +268,13 @@ CLASS="REFENTRYTITLE" > file.</P ></DD ><DT ->-l <log directory></DT +>-l <log directory></DT ><DD ><P >If specified, - <TT + <VAR CLASS="REPLACEABLE" -><I ->log directory</I -></TT +>log directory</VAR > specifies a log directory into which the "log.smbd" log file will be created for informational and debug @@ -289,11 +283,9 @@ CLASS="REPLACEABLE" its size may be controlled by the <A HREF="smb.conf.5.html#maxlogsize" TARGET="_top" -><TT +><VAR CLASS="PARAMETER" -><I ->max log size</I -></TT +>max log size</VAR ></A > option in the <SPAN @@ -320,17 +312,15 @@ CLASS="COMMAND" compile time.</P ></DD ><DT ->-O <socket options></DT +>-O <socket options></DT ><DD ><P >See the <A HREF="smb.conf.5.html#socketoptions" TARGET="_top" -><TT +><VAR CLASS="PARAMETER" -><I ->socket options</I -></TT +>socket options</VAR ></A > parameter in the <SPAN @@ -342,14 +332,12 @@ CLASS="REFENTRYTITLE" > file for details.</P ></DD ><DT ->-p <port number></DT +>-p <port number></DT ><DD ><P -><TT +><VAR CLASS="REPLACEABLE" -><I ->port number</I -></TT +>port number</VAR > is a positive integer value. The default value if this parameter is not specified is 139.</P @@ -373,7 +361,7 @@ CLASS="REPLACEABLE" in the above situation.</P ></DD ><DT ->-s <configuration file></DT +>-s <configuration file></DT ><DD ><P >The file specified contains the @@ -534,17 +522,17 @@ NAME="AEN177" CLASS="VARIABLELIST" ><DL ><DT -><TT +><VAR CLASS="ENVAR" ->PRINTER</TT +>PRINTER</VAR ></DT ><DD ><P >If no printer name is specified to printable services, most systems will use the value of - this variable (or <TT + this variable (or <CODE CLASS="CONSTANT" ->lp</TT +>lp</CODE > if this variable is not defined) as the name of the printer to use. This is not specific to the server, however.</P @@ -566,12 +554,10 @@ NAME="AEN186" by the limitations of the SMB protocol and the <A HREF="smb.conf.5.html#OBEYPAMRESRICTIONS" TARGET="_top" -><TT +><VAR CLASS="PARAMETER" -><I >obey - pam restricions</I -></TT + pam restricions</VAR ></A > <SPAN CLASS="CITEREFENTRY" diff --git a/docs/htmldocs/smbgroupedit.8.html b/docs/htmldocs/smbgroupedit.8.html index 856c778cb4..32e00315b4 100644 --- a/docs/htmldocs/smbgroupedit.8.html +++ b/docs/htmldocs/smbgroupedit.8.html @@ -5,7 +5,7 @@ >smbgroupedit</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"></HEAD +CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD ><BODY CLASS="REFENTRY" BGCOLOR="#FFFFFF" @@ -179,9 +179,9 @@ TYPE="1" <TT CLASS="FILENAME" >/etc/group</TT ->), let's call it <TT +>), let's call it <CODE CLASS="CONSTANT" ->domadm</TT +>domadm</CODE >. </P ></LI @@ -210,9 +210,9 @@ TYPE="a" ><P ><PRE CLASS="PROGRAMLISTING" -><TT +><SAMP CLASS="PROMPT" ->root# </TT +>root# </SAMP ><B CLASS="COMMAND" >smbgroupedit -vs | grep "Domain Admins"</B @@ -226,9 +226,9 @@ Domain Admins (S-1-5-21-1108995562-3116817432-1375597819-512) -> -1</PRE "Domain Admins" group, by running the command: <PRE CLASS="PROGRAMLISTING" -><TT +><SAMP CLASS="PROMPT" ->root# </TT +>root# </SAMP ><B CLASS="COMMAND" >smbgroupedit \ @@ -254,9 +254,9 @@ CLASS="EMPHASIS" >To verify that your mapping has taken effect: <PRE CLASS="PROGRAMLISTING" -><TT +><SAMP CLASS="PROMPT" ->root# </TT +>root# </SAMP ><B CLASS="COMMAND" >smbgroupedit -vs|grep "Domain Admins"</B @@ -269,9 +269,9 @@ 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 CLASS="PROGRAMLISTING" -><TT +><SAMP CLASS="PROMPT" ->root# </TT +>root# </SAMP ><B CLASS="COMMAND" >smbgroupedit -a unixgroup -td</B diff --git a/docs/htmldocs/smbmnt.8.html b/docs/htmldocs/smbmnt.8.html index de3af0b0a4..1eabc3ce0e 100644 --- a/docs/htmldocs/smbmnt.8.html +++ b/docs/htmldocs/smbmnt.8.html @@ -5,7 +5,7 @@ >smbmnt</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"></HEAD +CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD ><BODY CLASS="REFENTRY" BGCOLOR="#FFFFFF" @@ -37,7 +37,7 @@ NAME="AEN8" ><B CLASS="COMMAND" >smbmnt</B -> {mount-point} [-s <share>] [-r] [-u <uid>] [-g <gid>] [-f <mask>] [-d <mask>] [-o <options>]</P +> {mount-point} [-s <share>] [-r] [-u <uid>] [-g <gid>] [-f <mask>] [-d <mask>] [-o <options>]</P ></DIV ><DIV CLASS="REFSECT1" diff --git a/docs/htmldocs/smbmount.8.html b/docs/htmldocs/smbmount.8.html index bc9fcf72e2..0844c21a7d 100644 --- a/docs/htmldocs/smbmount.8.html +++ b/docs/htmldocs/smbmount.8.html @@ -5,7 +5,7 @@ >smbmount</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"></HEAD +CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD ><BODY CLASS="REFENTRY" BGCOLOR="#FFFFFF" @@ -124,27 +124,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 <TT + this is not given, then the environment variable <VAR CLASS="ENVAR" -> USER</TT +> USER</VAR > 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 - <TT + <VAR CLASS="ENVAR" ->PASSWD</TT +>PASSWD</VAR > is used. If it can find no password <B CLASS="COMMAND" @@ -161,15 +161,15 @@ 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 CLASS="PROGRAMLISTING" ->username = <value> -password = <value></PRE +>username = <value> +password = <value></PRE ></P ><P >This is preferred over having passwords in plaintext in a @@ -181,14 +181,14 @@ CLASS="FILENAME" </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 @@ -197,7 +197,7 @@ CLASS="FILENAME" </P ></DD ><DT ->gid=<arg></DT +>gid=<arg></DT ><DD ><P >sets the gid that will own all files on @@ -206,14 +206,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 @@ -221,7 +221,7 @@ 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 @@ -229,7 +229,7 @@ CLASS="FILENAME" 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 @@ -238,20 +238,20 @@ CLASS="FILENAME" output, possibly hiding the useful output.</P ></DD ><DT ->ip=<arg></DT +>ip=<arg></DT ><DD ><P >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 ></DD ><DT ->sockopt=<arg></DT +>sockopt=<arg></DT ><DD ><P >sets the TCP socket options. See the <A @@ -264,16 +264,14 @@ CLASS="REFENTRYTITLE" >smb.conf</SPAN >(5)</SPAN ></A -> <TT +> <VAR CLASS="PARAMETER" -><I ->socket options</I -></TT +>socket options</VAR > option. </P ></DD ><DT ->scope=<arg></DT +>scope=<arg></DT ><DD ><P >sets the NetBIOS scope </P @@ -297,7 +295,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 @@ -307,7 +305,7 @@ CLASS="PARAMETER" </P ></DD ><DT ->codepage=<arg></DT +>codepage=<arg></DT ><DD ><P > sets the codepage the server uses. See the iocharset @@ -316,7 +314,7 @@ CLASS="PARAMETER" </P ></DD ><DT ->ttl=<arg></DT +>ttl=<arg></DT ><DD ><P > sets how long a directory listing is cached in milliseconds @@ -341,26 +339,26 @@ NAME="AEN130" ><H2 >ENVIRONMENT VARIABLES</H2 ><P ->The variable <TT +>The variable <VAR CLASS="ENVAR" ->USER</TT +>USER</VAR > 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 <TT +>The variable <VAR CLASS="ENVAR" ->PASSWD</TT +>PASSWD</VAR > 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 <TT +>The variable <VAR CLASS="ENVAR" ->PASSWD_FILE</TT +>PASSWD_FILE</VAR > 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 diff --git a/docs/htmldocs/smbpasswd.5.html b/docs/htmldocs/smbpasswd.5.html index a07be03b41..61b60d7d82 100644 --- a/docs/htmldocs/smbpasswd.5.html +++ b/docs/htmldocs/smbpasswd.5.html @@ -5,7 +5,7 @@ >smbpasswd</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"></HEAD +CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD ><BODY CLASS="REFENTRY" BGCOLOR="#FFFFFF" @@ -115,9 +115,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 - <TT + <CODE CLASS="CONSTANT" ->disabled</TT +>disabled</CODE > and the user will not be able to log onto the Samba server. </P ><P @@ -235,11 +235,9 @@ 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 <TT + will only allow users to log on with no password if the <VAR CLASS="PARAMETER" -><I -> null passwords</I -></TT +> null passwords</VAR > parameter is set in the <A HREF="smb.conf.5.html#NULLPASSWORDS" TARGET="_top" diff --git a/docs/htmldocs/smbpasswd.8.html b/docs/htmldocs/smbpasswd.8.html index 223cd02521..6b227f9d1e 100644 --- a/docs/htmldocs/smbpasswd.8.html +++ b/docs/htmldocs/smbpasswd.8.html @@ -5,7 +5,7 @@ >smbpasswd</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"></HEAD +CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD ><BODY CLASS="REFENTRY" BGCOLOR="#FFFFFF" @@ -37,7 +37,7 @@ NAME="AEN8" ><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" @@ -107,20 +107,16 @@ CLASS="REFENTRYTITLE" was typed correctly. No passwords will be echoed on the screen whilst being typed. If you have a blank SMB password (specified by the string "NO PASSWORD" in the smbpasswd file) then just press - the <Enter> key when asked for your old password. </P + the <Enter> key when asked for your old password. </P ><P >smbpasswd can also be used by a normal user to change their SMB password on remote machines, such as Windows NT Primary Domain - Controllers. See the (<TT + Controllers. See the (<VAR CLASS="PARAMETER" -><I ->-r</I -></TT ->) and <TT +>-r</VAR +>) and <VAR CLASS="PARAMETER" -><I ->-U</I -></TT +>-U</VAR > options below. </P ><P @@ -151,7 +147,7 @@ CLASS="VARIABLELIST" ><P >This option specifies that the username following should be added to the local smbpasswd file, with the - new password typed (type <Enter> for the old password). This + new password typed (type <Enter> for the old password). This option is ignored if the username following already exists in the smbpasswd file and it is treated like a regular change password command. Note that the default passdb backends require @@ -181,13 +177,13 @@ CLASS="FILENAME" ><DD ><P >This option specifies that the username following - should be <TT + should be <CODE CLASS="CONSTANT" ->disabled</TT +>disabled</CODE > in the local smbpasswd - file. This is done by writing a <TT + file. This is done by writing a <CODE CLASS="CONSTANT" ->'D'</TT +>'D'</CODE > flag into the account control space in the smbpasswd file. Once this is done all attempts to authenticate via SMB using this username @@ -212,9 +208,9 @@ CLASS="REFENTRYTITLE" ><DD ><P >This option specifies that the username following - should be <TT + should be <CODE CLASS="CONSTANT" ->enabled</TT +>enabled</CODE > 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 @@ -240,11 +236,9 @@ CLASS="REFENTRYTITLE" >-D debuglevel</DT ><DD ><P -><TT +><VAR CLASS="REPLACEABLE" -><I ->debuglevel</I -></TT +>debuglevel</VAR > is an integer from 0 to 10. The default value if this parameter is not specified is zero. </P @@ -291,30 +285,24 @@ 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 <TT + smbpasswd defaults to the local host. The <VAR CLASS="REPLACEABLE" -><I >remote - machine name</I -></TT + machine name</VAR > 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 <TT + mechanism in all programs of the Samba suite. See the <VAR CLASS="PARAMETER" -><I >-R - name resolve order</I -></TT + name resolve order</VAR > 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 <TT + current UNIX logged on user. See the <VAR CLASS="PARAMETER" -><I ->-U username</I -></TT +>-U username</VAR > parameter for details on changing the password for a different username. </P @@ -350,9 +338,9 @@ CLASS="EMPHASIS" ><UL ><LI ><P -><TT +><CODE CLASS="CONSTANT" ->lmhosts</TT +>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 @@ -366,9 +354,9 @@ CLASS="REFENTRYTITLE" ></LI ><LI ><P -><TT +><CODE CLASS="CONSTANT" ->host</TT +>host</CODE >: Do a standard host name to IP address resolution, using the system <TT CLASS="FILENAME" @@ -386,31 +374,27 @@ CLASS="FILENAME" ></LI ><LI ><P -><TT +><CODE CLASS="CONSTANT" ->wins</TT +>wins</CODE >: Query a name with - the IP address listed in the <TT + the IP address listed in the <VAR CLASS="PARAMETER" -><I ->wins server</I -></TT +>wins server</VAR > parameter. If no WINS server has been specified this method will be ignored.</P ></LI ><LI ><P -><TT +><CODE CLASS="CONSTANT" ->bcast</TT +>bcast</CODE >: Do a broadcast on each of the known local interfaces listed in the - <TT + <VAR CLASS="PARAMETER" -><I ->interfaces</I -></TT +>interfaces</VAR > 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 @@ -446,11 +430,9 @@ CLASS="REFENTRYTITLE" ><DD ><P >This option may only be used in conjunction - with the <TT + with the <VAR CLASS="PARAMETER" -><I ->-r</I -></TT +>-r</VAR > 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 @@ -492,34 +474,28 @@ CLASS="COMMAND" <B CLASS="COMMAND" >--with-ldapsam</B -> option. The <TT +> option. The <VAR CLASS="PARAMETER" -><I ->-w</I -></TT +>-w</VAR > switch is used to specify the password to be used with the <A HREF="smb.conf.5.html#LDAPADMINDN" TARGET="_top" -><TT +><VAR CLASS="PARAMETER" -><I >ldap admin - dn</I -></TT + dn</VAR ></A >. Note that the password is stored in the <TT CLASS="FILENAME" >secrets.tdb</TT > and is keyed off - of the admin's DN. This means that if the value of <TT + of the admin's DN. This means that if the value of <VAR CLASS="PARAMETER" -><I >ldap - admin dn</I -></TT + admin dn</VAR > ever changes, the password will need to be manually updated as well. </P @@ -578,17 +554,13 @@ CLASS="COMMAND" is to add a restriction to the hosts that may access the <B CLASS="COMMAND" > smbd</B -> running on the local machine by specifying either <TT +> running on the local machine by specifying either <VAR CLASS="PARAMETER" -><I >allow - hosts</I -></TT -> or <TT + hosts</VAR +> or <VAR CLASS="PARAMETER" -><I ->deny hosts</I -></TT +>deny hosts</VAR > entry in the <SPAN CLASS="CITEREFENTRY" diff --git a/docs/htmldocs/smbsh.1.html b/docs/htmldocs/smbsh.1.html index c8c61fb6fe..625f63d260 100644 --- a/docs/htmldocs/smbsh.1.html +++ b/docs/htmldocs/smbsh.1.html @@ -5,7 +5,7 @@ >smbsh</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"></HEAD +CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD ><BODY CLASS="REFENTRY" BGCOLOR="#FFFFFF" @@ -38,7 +38,7 @@ NAME="AEN8" ><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" @@ -130,7 +130,7 @@ CLASS="EMPHASIS" </P ></DD ><DT ->-R <name resolve order></DT +>-R <name resolve order></DT ><DD ><P >This option is used to determine what naming @@ -145,9 +145,9 @@ CLASS="EMPHASIS" ><UL ><LI ><P -><TT +><CODE CLASS="CONSTANT" ->lmhosts</TT +>lmhosts</CODE >: Lookup an IP address in the Samba lmhosts file. If the line in lmhosts has no name type attached to the @@ -164,9 +164,9 @@ CLASS="REFENTRYTITLE" ></LI ><LI ><P -><TT +><CODE CLASS="CONSTANT" ->host</TT +>host</CODE >: Do a standard host name to IP address resolution, using the system <TT @@ -186,16 +186,14 @@ CLASS="FILENAME" ></LI ><LI ><P -><TT +><CODE CLASS="CONSTANT" ->wins</TT +>wins</CODE >: Query a name with the IP address listed in the - <TT + <VAR CLASS="PARAMETER" -><I ->wins server</I -></TT +>wins server</VAR > parameter. If no WINS server has been specified this method will be ignored. @@ -203,16 +201,14 @@ CLASS="PARAMETER" ></LI ><LI ><P -><TT +><CODE CLASS="CONSTANT" ->bcast</TT +>bcast</CODE >: Do a broadcast on each of the known local interfaces - listed in the <TT + listed in the <VAR CLASS="PARAMETER" -><I ->interfaces</I -></TT +>interfaces</VAR > parameter. This is the least reliable of the name resolution methods as it depends on the target host @@ -229,20 +225,16 @@ CLASS="REFENTRYTITLE" >smb.conf</SPAN >(5)</SPAN > file parameter - (<TT + (<VAR CLASS="PARAMETER" -><I ->name resolve order</I -></TT +>name resolve order</VAR >) will be used. </P ><P >The default order is lmhosts, host, wins, bcast. Without - this parameter or any entry in the <TT + this parameter or any entry in the <VAR CLASS="PARAMETER" -><I >name resolve order - </I -></TT + </VAR > parameter of the <SPAN CLASS="CITEREFENTRY" ><SPAN @@ -253,7 +245,7 @@ CLASS="REFENTRYTITLE" will be attempted in this order. </P ></DD ><DT ->-d <debug level></DT +>-d <debug level></DT ><DD ><P >debug level is an integer from 0 to 10.</P @@ -277,18 +269,14 @@ CLASS="REFENTRYTITLE" ><DD ><P >If specified causes all debug messages to be - written to the file specified by <TT + written to the file specified by <VAR CLASS="REPLACEABLE" -><I >logfilename - </I -></TT + </VAR >. If not specified then all messages will be - written to<TT + written to<VAR CLASS="REPLACEABLE" -><I ->stderr</I -></TT +>stderr</VAR >. </P ></DD @@ -326,32 +314,26 @@ CLASS="COMMAND" operating system. <PRE CLASS="PROGRAMLISTING" -><TT +><SAMP CLASS="PROMPT" ->system% </TT -><TT +>system% </SAMP +><KBD CLASS="USERINPUT" -><B ->smbsh</B -></TT +>smbsh</KBD > -<TT +<SAMP CLASS="PROMPT" ->Username: </TT -><TT +>Username: </SAMP +><KBD CLASS="USERINPUT" -><B ->user</B -></TT +>user</KBD > -<TT +<SAMP CLASS="PROMPT" ->Password: </TT -><TT +>Password: </SAMP +><KBD CLASS="USERINPUT" -><B ->XXXXXXX</B -></TT +>XXXXXXX</KBD ></PRE ></P ><P @@ -372,7 +354,7 @@ CLASS="COMMAND" the workgroup MYGROUP. The command <B CLASS="COMMAND" ->ls /smb/MYGROUP/<machine-name></B +>ls /smb/MYGROUP/<machine-name></B > will show the share names for that machine. You could then, for example, use the <B CLASS="COMMAND" diff --git a/docs/htmldocs/smbspool.8.html b/docs/htmldocs/smbspool.8.html index b66d08381d..ca9641a72e 100644 --- a/docs/htmldocs/smbspool.8.html +++ b/docs/htmldocs/smbspool.8.html @@ -5,7 +5,7 @@ >smbspool</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"></HEAD +CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD ><BODY CLASS="REFENTRY" BGCOLOR="#FFFFFF" @@ -94,9 +94,9 @@ CLASS="EMPHASIS" ></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 <TT + contains the name of the program then it looks in the <VAR CLASS="ENVAR" -> DEVICE_URI</TT +> DEVICE_URI</VAR > environment variable.</P ><P >Programs using the <B @@ -104,9 +104,9 @@ CLASS="COMMAND" >exec(2)</B > functions can pass the URI in argv[0], while shell scripts must set the - <TT + <VAR CLASS="ENVAR" ->DEVICE_URI</TT +>DEVICE_URI</VAR > environment variable prior to running smbspool.</P ></DIV diff --git a/docs/htmldocs/smbstatus.1.html b/docs/htmldocs/smbstatus.1.html index 47b7ef112f..973fb5bb87 100644 --- a/docs/htmldocs/smbstatus.1.html +++ b/docs/htmldocs/smbstatus.1.html @@ -5,7 +5,7 @@ >smbstatus</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"></HEAD +CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD ><BODY CLASS="REFENTRY" BGCOLOR="#FFFFFF" @@ -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" @@ -88,7 +88,7 @@ CLASS="VARIABLELIST" >gives brief output.</P ></DD ><DT ->-d|--debug=<debuglevel></DT +>-d|--debug=<debuglevel></DT ><DD ><P >sets debugging to specified level</P @@ -132,7 +132,7 @@ CLASS="REFENTRYTITLE" >causes smbstatus to only list shares.</P ></DD ><DT ->-s|--conf=<configuration file></DT +>-s|--conf=<configuration file></DT ><DD ><P >The default configuration file name is @@ -146,15 +146,13 @@ CLASS="REFENTRYTITLE" > for more information.</P ></DD ><DT ->-u|--user=<username></DT +>-u|--user=<username></DT ><DD ><P >selects information relevant to - <TT + <VAR CLASS="PARAMETER" -><I ->username</I -></TT +>username</VAR > only.</P ></DD ></DL diff --git a/docs/htmldocs/smbtar.1.html b/docs/htmldocs/smbtar.1.html index 1eb0017417..fe405a0d84 100644 --- a/docs/htmldocs/smbtar.1.html +++ b/docs/htmldocs/smbtar.1.html @@ -5,7 +5,7 @@ >smbtar</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"></HEAD +CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD ><BODY CLASS="REFENTRY" BGCOLOR="#FFFFFF" @@ -105,12 +105,10 @@ CLASS="VARIABLELIST" >-d directory</DT ><DD ><P ->Change to initial <TT +>Change to initial <VAR CLASS="PARAMETER" -><I >directory - </I -></TT + </VAR > before restoring / backing up files. </P ></DD ><DT @@ -138,11 +136,9 @@ CLASS="PARAMETER" ><DD ><P >Tape device. May be regular file or tape - device. Default: <TT + device. Default: <VAR CLASS="PARAMETER" -><I ->$TAPE</I -></TT +>$TAPE</VAR > environmental variable; if not set, a file called <TT CLASS="FILENAME" @@ -188,11 +184,9 @@ CLASS="COMMAND" ><DD ><P >Log (debug) level. Corresponds to the - <TT + <VAR CLASS="PARAMETER" -><I ->-d</I -></TT +>-d</VAR > flag of <SPAN CLASS="CITEREFENTRY" ><SPAN @@ -212,11 +206,9 @@ NAME="AEN100" ><H2 >ENVIRONMENT VARIABLES</H2 ><P ->The <TT +>The <VAR CLASS="PARAMETER" -><I ->$TAPE</I -></TT +>$TAPE</VAR > variable specifies the default tape device to write to. May be overridden with the -t option. </P diff --git a/docs/htmldocs/smbumount.8.html b/docs/htmldocs/smbumount.8.html index 83041b796c..15ec19d7fc 100644 --- a/docs/htmldocs/smbumount.8.html +++ b/docs/htmldocs/smbumount.8.html @@ -5,7 +5,7 @@ >smbumount</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"></HEAD +CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD ><BODY CLASS="REFENTRY" BGCOLOR="#FFFFFF" diff --git a/docs/htmldocs/speed.html b/docs/htmldocs/speed.html index c99a49142c..85863dcd5f 100644 --- a/docs/htmldocs/speed.html +++ b/docs/htmldocs/speed.html @@ -5,7 +5,7 @@ >Samba performance issues</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -16,7 +16,7 @@ REL="PREVIOUS" TITLE="Group mapping HOWTO" HREF="groupmapping.html"><LINK REL="NEXT" -TITLE="Creating Group Profiles" +TITLE="Creating Group Prolicy Files" HREF="groupprofiles.html"></HEAD ><BODY CLASS="CHAPTER" @@ -74,15 +74,15 @@ CLASS="CHAPTER" ><A NAME="SPEED" ></A ->Chapter 19. Samba performance issues</H1 +>Chapter 18. Samba performance issues</H1 ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3033" -></A ->19.1. Comparisons</H1 +NAME="AEN2890" +>18.1. Comparisons</A +></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 +111,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3039" -></A ->19.2. Socket options</H1 +NAME="AEN2896" +>18.2. Socket options</A +></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 +139,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3046" -></A ->19.3. Read size</H1 +NAME="AEN2903" +>18.3. Read size</A +></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 +165,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3051" -></A ->19.4. Max xmit</H1 +NAME="AEN2908" +>18.4. Max xmit</A +></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 +188,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3056" -></A ->19.5. Log level</H1 +NAME="AEN2913" +>18.5. Log level</A +></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 +202,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3059" -></A ->19.6. Read raw</H1 +NAME="AEN2916" +>18.6. Read raw</A +></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 +224,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3064" -></A ->19.7. Write raw</H1 +NAME="AEN2921" +>18.7. Write raw</A +></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 +241,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3068" -></A ->19.8. Slow Clients</H1 +NAME="AEN2925" +>18.8. Slow Clients</A +></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 +258,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3072" -></A ->19.9. Slow Logins</H1 +NAME="AEN2929" +>18.9. Slow Logins</A +></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 +271,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3075" -></A ->19.10. Client tuning</H1 +NAME="AEN2932" +>18.10. Client tuning</A +></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 @@ -431,7 +431,7 @@ ACCESSKEY="U" WIDTH="33%" ALIGN="right" VALIGN="top" ->Creating Group Profiles</TD +>Creating Group Prolicy Files</TD ></TR ></TABLE ></DIV diff --git a/docs/htmldocs/swat.8.html b/docs/htmldocs/swat.8.html index 0c65e7b1d6..d78fee1960 100644 --- a/docs/htmldocs/swat.8.html +++ b/docs/htmldocs/swat.8.html @@ -5,7 +5,7 @@ >swat</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"></HEAD +CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD ><BODY CLASS="REFENTRY" BGCOLOR="#FFFFFF" @@ -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" @@ -350,17 +350,13 @@ CLASS="REFENTRYTITLE" >smb.conf</SPAN >(5)</SPAN > file. It will rearrange the entries and delete all - comments, <TT + comments, <VAR CLASS="PARAMETER" -><I ->include=</I -></TT -> and <TT +>include=</VAR +> and <VAR CLASS="PARAMETER" -><I >copy= - </I -></TT + </VAR > options. If you have a carefully crafted <TT CLASS="FILENAME" > smb.conf</TT diff --git a/docs/htmldocs/testparm.1.html b/docs/htmldocs/testparm.1.html index 52413a1c27..3f93b9b241 100644 --- a/docs/htmldocs/testparm.1.html +++ b/docs/htmldocs/testparm.1.html @@ -5,7 +5,7 @@ >testparm</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"></HEAD +CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD ><BODY CLASS="REFENTRY" BGCOLOR="#FFFFFF" @@ -38,7 +38,7 @@ NAME="AEN8" ><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" @@ -135,11 +135,9 @@ CLASS="COMMAND" >-L servername</DT ><DD ><P ->Sets the value of the %L macro to <TT +>Sets the value of the %L macro to <VAR CLASS="REPLACEABLE" -><I ->servername</I -></TT +>servername</VAR >. This is useful for testing include files specified with the %L macro. </P @@ -187,17 +185,13 @@ CLASS="REFENTRYTITLE" specified, then <B CLASS="COMMAND" >testparm</B -> will examine the <TT +> will examine the <VAR CLASS="PARAMETER" -><I >hosts - allow</I -></TT -> and <TT + allow</VAR +> and <VAR CLASS="PARAMETER" -><I ->hosts deny</I -></TT +>hosts deny</VAR > parameters in the <SPAN CLASS="CITEREFENTRY" diff --git a/docs/htmldocs/testprns.1.html b/docs/htmldocs/testprns.1.html index 07513566af..5efef1fb85 100644 --- a/docs/htmldocs/testprns.1.html +++ b/docs/htmldocs/testprns.1.html @@ -5,7 +5,7 @@ >testprns</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"></HEAD +CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD ><BODY CLASS="REFENTRY" BGCOLOR="#FFFFFF" @@ -167,11 +167,11 @@ NAME="AEN53" >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 diff --git a/docs/htmldocs/type.html b/docs/htmldocs/type.html index be7e722b2e..d4db19bf43 100644 --- a/docs/htmldocs/type.html +++ b/docs/htmldocs/type.html @@ -5,7 +5,7 @@ >Type of installation</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -78,7 +78,7 @@ CLASS="TITLE" ><DIV CLASS="PARTINTRO" ><A -NAME="AEN678" +NAME="AEN581" ></A ><H1 >Introduction</H1 @@ -107,22 +107,22 @@ HREF="samba-pdc.html" ><DL ><DT >5.1. <A -HREF="samba-pdc.html#AEN722" +HREF="samba-pdc.html#AEN625" >Prerequisite Reading</A ></DT ><DT >5.2. <A -HREF="samba-pdc.html#AEN728" +HREF="samba-pdc.html#AEN631" >Background</A ></DT ><DT >5.3. <A -HREF="samba-pdc.html#AEN767" +HREF="samba-pdc.html#AEN670" >Configuring the Samba Domain Controller</A ></DT ><DT >5.4. <A -HREF="samba-pdc.html#AEN810" +HREF="samba-pdc.html#AEN713" >Creating Machine Trust Accounts and Joining Clients to the Domain</A ></DT @@ -130,59 +130,59 @@ Domain</A ><DL ><DT >5.4.1. <A -HREF="samba-pdc.html#AEN829" +HREF="samba-pdc.html#AEN732" >Manual Creation of Machine Trust Accounts</A ></DT ><DT >5.4.2. <A -HREF="samba-pdc.html#AEN870" +HREF="samba-pdc.html#AEN773" >"On-the-Fly" Creation of Machine Trust Accounts</A ></DT ><DT >5.4.3. <A -HREF="samba-pdc.html#AEN879" +HREF="samba-pdc.html#AEN782" >Joining the Client to the Domain</A ></DT ></DL ></DD ><DT >5.5. <A -HREF="samba-pdc.html#AEN894" +HREF="samba-pdc.html#AEN797" >Common Problems and Errors</A ></DT ><DT >5.6. <A -HREF="samba-pdc.html#AEN942" +HREF="samba-pdc.html#AEN845" >System Policies and Profiles</A ></DT ><DT >5.7. <A -HREF="samba-pdc.html#AEN986" +HREF="samba-pdc.html#AEN889" >What other help can I get?</A ></DT ><DT >5.8. <A -HREF="samba-pdc.html#AEN1100" +HREF="samba-pdc.html#AEN1003" >Domain Control for Windows 9x/ME</A ></DT ><DD ><DL ><DT >5.8.1. <A -HREF="samba-pdc.html#AEN1126" +HREF="samba-pdc.html#AEN1029" >Configuration Instructions: Network Logons</A ></DT ><DT >5.8.2. <A -HREF="samba-pdc.html#AEN1145" +HREF="samba-pdc.html#AEN1048" >Configuration Instructions: Setting up Roaming User Profiles</A ></DT ></DL ></DD ><DT >5.9. <A -HREF="samba-pdc.html#AEN1238" ->DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba</A +HREF="samba-pdc.html#AEN1141" +>DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba</A ></DT ></DL ></DD @@ -195,53 +195,53 @@ HREF="samba-bdc.html" ><DL ><DT >6.1. <A -HREF="samba-bdc.html#AEN1274" +HREF="samba-bdc.html#AEN1177" >Prerequisite Reading</A ></DT ><DT >6.2. <A -HREF="samba-bdc.html#AEN1278" +HREF="samba-bdc.html#AEN1181" >Background</A ></DT ><DT >6.3. <A -HREF="samba-bdc.html#AEN1286" +HREF="samba-bdc.html#AEN1189" >What qualifies a Domain Controller on the network?</A ></DT ><DD ><DL ><DT >6.3.1. <A -HREF="samba-bdc.html#AEN1289" +HREF="samba-bdc.html#AEN1192" >How does a Workstation find its domain controller?</A ></DT ><DT >6.3.2. <A -HREF="samba-bdc.html#AEN1292" +HREF="samba-bdc.html#AEN1195" >When is the PDC needed?</A ></DT ></DL ></DD ><DT >6.4. <A -HREF="samba-bdc.html#AEN1295" +HREF="samba-bdc.html#AEN1198" >Can Samba be a Backup Domain Controller to an NT PDC?</A ></DT ><DT >6.5. <A -HREF="samba-bdc.html#AEN1300" +HREF="samba-bdc.html#AEN1203" >How do I set up a Samba BDC?</A ></DT ><DD ><DL ><DT >6.5.1. <A -HREF="samba-bdc.html#AEN1317" +HREF="samba-bdc.html#AEN1220" >How do I replicate the smbpasswd file?</A ></DT ><DT >6.5.2. <A -HREF="samba-bdc.html#AEN1321" +HREF="samba-bdc.html#AEN1224" >Can I do this all with LDAP?</A ></DT ></DL @@ -257,51 +257,51 @@ HREF="ads.html" ><DL ><DT >7.1. <A -HREF="ads.html#AEN1339" +HREF="ads.html#AEN1242" >Installing the required packages for Debian</A ></DT ><DT >7.2. <A -HREF="ads.html#AEN1346" +HREF="ads.html#AEN1249" >Installing the required packages for RedHat</A ></DT ><DT >7.3. <A -HREF="ads.html#AEN1356" +HREF="ads.html#AEN1259" >Compile Samba</A ></DT ><DT >7.4. <A -HREF="ads.html#AEN1371" +HREF="ads.html#AEN1274" >Setup your /etc/krb5.conf</A ></DT ><DT >7.5. <A -HREF="ads.html#AEN1381" +HREF="ads.html#AEN1284" >Create the computer account</A ></DT ><DD ><DL ><DT >7.5.1. <A -HREF="ads.html#AEN1385" +HREF="ads.html#AEN1288" >Possible errors</A ></DT ></DL ></DD ><DT >7.6. <A -HREF="ads.html#AEN1393" +HREF="ads.html#AEN1296" >Test your server setup</A ></DT ><DT >7.7. <A -HREF="ads.html#AEN1398" +HREF="ads.html#AEN1301" >Testing with smbclient</A ></DT ><DT >7.8. <A -HREF="ads.html#AEN1401" +HREF="ads.html#AEN1304" >Notes</A ></DT ></DL @@ -315,17 +315,17 @@ HREF="domain-security.html" ><DL ><DT >8.1. <A -HREF="domain-security.html#AEN1423" +HREF="domain-security.html#AEN1326" >Joining an NT Domain with Samba 3.0</A ></DT ><DT >8.2. <A -HREF="domain-security.html#AEN1478" +HREF="domain-security.html#AEN1381" >Samba and Windows 2000 Domains</A ></DT ><DT >8.3. <A -HREF="domain-security.html#AEN1481" +HREF="domain-security.html#AEN1384" >Why is this better than security = server?</A ></DT ></DL diff --git a/docs/htmldocs/unix-permissions.html b/docs/htmldocs/unix-permissions.html index 71198ecaa6..57246f1e2f 100644 --- a/docs/htmldocs/unix-permissions.html +++ b/docs/htmldocs/unix-permissions.html @@ -5,7 +5,7 @@ >UNIX Permission Bits and Windows NT Access Control Lists</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -81,10 +81,10 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1744" -></A +NAME="AEN1647" >10.1. Viewing and changing UNIX permissions using the NT - security dialogs</H1 + security dialogs</A +></H1 ><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 @@ -100,9 +100,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1748" -></A ->10.2. How to view file security on a Samba share</H1 +NAME="AEN1651" +>10.2. How to view file security on a Samba share</A +></H1 ><P >From an NT 4.0 client, single-click with the right mouse button on any file or directory in a Samba mounted @@ -170,9 +170,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1759" -></A ->10.3. Viewing file ownership</H1 +NAME="AEN1662" +>10.3. Viewing file ownership</A +></H1 ><P >Clicking on the <B CLASS="COMMAND" @@ -186,23 +186,17 @@ CLASS="COMMAND" >"SERVER\user (Long name)"</B ></P ><P ->Where <TT +>Where <VAR CLASS="REPLACEABLE" -><I ->SERVER</I -></TT +>SERVER</VAR > is the NetBIOS name of - the Samba server, <TT + the Samba server, <VAR CLASS="REPLACEABLE" -><I ->user</I -></TT +>user</VAR > is the user name of - the UNIX user who owns the file, and <TT + the UNIX user who owns the file, and <VAR CLASS="REPLACEABLE" -><I ->(Long name)</I -></TT +>(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 @@ -211,15 +205,13 @@ CLASS="COMMAND" </B > button to remove this dialog.</P ><P ->If the parameter <TT +>If the parameter <VAR CLASS="PARAMETER" -><I ->nt acl support</I -></TT +>nt acl support</VAR > - is set to <TT + is set to <CODE CLASS="CONSTANT" ->false</TT +>false</CODE > then the file owner will be shown as the NT user <B CLASS="COMMAND" @@ -264,9 +256,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1779" -></A ->10.4. Viewing file or directory permissions</H1 +NAME="AEN1682" +>10.4. Viewing file or directory permissions</A +></H1 ><P >The third button is the <B CLASS="COMMAND" @@ -281,36 +273,28 @@ CLASS="COMMAND" >"SERVER\user (Long name)"</B ></P ><P ->Where <TT +>Where <VAR CLASS="REPLACEABLE" -><I ->SERVER</I -></TT +>SERVER</VAR > is the NetBIOS name of - the Samba server, <TT + the Samba server, <VAR CLASS="REPLACEABLE" -><I ->user</I -></TT +>user</VAR > is the user name of - the UNIX user who owns the file, and <TT + the UNIX user who owns the file, and <VAR CLASS="REPLACEABLE" -><I ->(Long name)</I -></TT +>(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 <TT +>If the parameter <VAR CLASS="PARAMETER" -><I ->nt acl support</I -></TT +>nt acl support</VAR > - is set to <TT + is set to <CODE CLASS="CONSTANT" ->false</TT +>false</CODE > then the file owner will be shown as the NT user <B CLASS="COMMAND" @@ -326,9 +310,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1794" -></A ->10.4.1. File Permissions</H2 +NAME="AEN1697" +>10.4.1. File Permissions</A +></H2 ><P >The standard UNIX user/group/world triple and the corresponding "read", "write", "execute" permissions @@ -388,9 +372,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1808" -></A ->10.4.2. Directory Permissions</H2 +NAME="AEN1711" +>10.4.2. Directory Permissions</A +></H2 ><P >Directories on an NT NTFS file system have two different sets of permissions. The first set of permissions @@ -420,9 +404,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1815" -></A ->10.5. Modifying file or directory permissions</H1 +NAME="AEN1718" +>10.5. Modifying file or directory permissions</A +></H1 ><P >Modifying file and directory permissions is as simple as changing the displayed permissions in the dialog box, and @@ -434,15 +418,13 @@ 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 <TT +>If the parameter <VAR CLASS="PARAMETER" -><I ->nt acl support</I -></TT +>nt acl support</VAR > - is set to <TT + is set to <CODE CLASS="CONSTANT" ->false</TT +>false</CODE > then any attempt to set security permissions will fail with an <B CLASS="COMMAND" @@ -518,40 +500,32 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1837" -></A +NAME="AEN1740" >10.6. Interaction with the standard Samba create mask - parameters</H1 + parameters</A +></H1 ><P >Note that with Samba 2.0.5 there are four new parameters to control this interaction. These are :</P ><P -><TT +><VAR CLASS="PARAMETER" -><I ->security mask</I -></TT +>security mask</VAR ></P ><P -><TT +><VAR CLASS="PARAMETER" -><I ->force security mode</I -></TT +>force security mode</VAR ></P ><P -><TT +><VAR CLASS="PARAMETER" -><I ->directory security mask</I -></TT +>directory security mask</VAR ></P ><P -><TT +><VAR CLASS="PARAMETER" -><I ->force directory security mode</I -></TT +>force directory security mode</VAR ></P ><P >Once a user clicks <B @@ -564,21 +538,17 @@ CLASS="COMMAND" HREF="smb.conf.5.html#SECURITYMASK" TARGET="_top" > - <TT + <VAR CLASS="PARAMETER" -><I ->security mask</I -></TT +>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 <TT +>Essentially, zero bits in the <VAR CLASS="PARAMETER" -><I ->security mask</I -></TT +>security mask</VAR > mask may be treated as a set of bits the user is <SPAN CLASS="emphasis" @@ -594,12 +564,10 @@ CLASS="EMPHASIS" the <A HREF="smb.conf.5.html#CREATEMASK" TARGET="_top" -><TT +><VAR CLASS="PARAMETER" -><I >create mask - </I -></TT + </VAR ></A > parameter to provide compatibility with Samba 2.0.4 where this permission change facility was introduced. To allow a user to @@ -610,22 +578,18 @@ CLASS="PARAMETER" the bits set in the <A HREF="smb.conf.5.html#FORCESECURITYMODE" TARGET="_top" -> <TT +> <VAR CLASS="PARAMETER" -><I ->force security mode</I -></TT +>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 <TT +>Essentially, bits set in the <VAR CLASS="PARAMETER" -><I >force security mode - </I -></TT + </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 @@ -633,82 +597,60 @@ CLASS="PARAMETER" as the <A HREF="smb.conf.5.html#FORCECREATEMODE" TARGET="_top" -><TT +><VAR CLASS="PARAMETER" -><I >force - create mode</I -></TT + create mode</VAR ></A > parameter to provide compatibility with Samba 2.0.4 where the permission change facility was introduced. To allow a user to modify all the user/group/world permissions on a file with no restrictions set this parameter to 000.</P ><P ->The <TT +>The <VAR CLASS="PARAMETER" -><I ->security mask</I -></TT -> and <TT +>security mask</VAR +> and <VAR CLASS="PARAMETER" -><I >force - security mode</I -></TT + 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 <TT + described above for a file except using the parameter <VAR CLASS="PARAMETER" -><I -> directory security mask</I -></TT -> instead of <TT +> directory security mask</VAR +> instead of <VAR CLASS="PARAMETER" -><I >security - mask</I -></TT ->, and <TT + mask</VAR +>, and <VAR CLASS="PARAMETER" -><I >force directory security mode - </I -></TT -> parameter instead of <TT + </VAR +> parameter instead of <VAR CLASS="PARAMETER" -><I >force security mode - </I -></TT + </VAR >.</P ><P ->The <TT +>The <VAR CLASS="PARAMETER" -><I ->directory security mask</I -></TT +>directory security mask</VAR > parameter - by default is set to the same value as the <TT + by default is set to the same value as the <VAR CLASS="PARAMETER" -><I >directory mask - </I -></TT -> parameter and the <TT + </VAR +> parameter and the <VAR CLASS="PARAMETER" -><I >force directory security - mode</I -></TT + mode</VAR > parameter by default is set to the same value as - the <TT + the <VAR CLASS="PARAMETER" -><I ->force directory mode</I -></TT +>force directory mode</VAR > parameter to provide compatibility with Samba 2.0.4 where the permission change facility was introduced.</P @@ -730,62 +672,46 @@ CLASS="FILENAME" ></A > file in that share specific section :</P ><P -><TT +><VAR CLASS="PARAMETER" -><I ->security mask = 0777</I -></TT +>security mask = 0777</VAR ></P ><P -><TT +><VAR CLASS="PARAMETER" -><I ->force security mode = 0</I -></TT +>force security mode = 0</VAR ></P ><P -><TT +><VAR CLASS="PARAMETER" -><I ->directory security mask = 0777</I -></TT +>directory security mask = 0777</VAR ></P ><P -><TT +><VAR CLASS="PARAMETER" -><I ->force directory security mode = 0</I -></TT +>force directory security mode = 0</VAR ></P ><P >As described, in Samba 2.0.4 the parameters :</P ><P -><TT +><VAR CLASS="PARAMETER" -><I ->create mask</I -></TT +>create mask</VAR ></P ><P -><TT +><VAR CLASS="PARAMETER" -><I ->force create mode</I -></TT +>force create mode</VAR ></P ><P -><TT +><VAR CLASS="PARAMETER" -><I ->directory mask</I -></TT +>directory mask</VAR ></P ><P -><TT +><VAR CLASS="PARAMETER" -><I ->force directory mode</I -></TT +>force directory mode</VAR ></P ><P >were used instead of the parameters discussed here.</P @@ -795,10 +721,10 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1901" -></A +NAME="AEN1804" >10.7. Interaction with the standard Samba file attribute - mapping</H1 + mapping</A +></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 diff --git a/docs/htmldocs/vfs.html b/docs/htmldocs/vfs.html index 0e39297ebb..84ff1227d4 100644 --- a/docs/htmldocs/vfs.html +++ b/docs/htmldocs/vfs.html @@ -5,7 +5,7 @@ >Stackable VFS modules</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -16,8 +16,8 @@ REL="PREVIOUS" TITLE="Improved browsing in samba" HREF="improved-browsing.html"><LINK REL="NEXT" -TITLE="Access Samba source code via CVS" -HREF="cvs-access.html"></HEAD +TITLE="Group mapping HOWTO" +HREF="groupmapping.html"></HEAD ><BODY CLASS="CHAPTER" BGCOLOR="#FFFFFF" @@ -59,7 +59,7 @@ WIDTH="10%" ALIGN="right" VALIGN="bottom" ><A -HREF="cvs-access.html" +HREF="groupmapping.html" ACCESSKEY="N" >Next</A ></TD @@ -80,9 +80,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2855" -></A ->16.1. Introduction and configuration</H1 +NAME="AEN2760" +>16.1. Introduction and configuration</A +></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 +121,17 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2864" -></A ->16.2. Included modules</H1 +NAME="AEN2769" +>16.2. Included modules</A +></H1 ><DIV CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2866" -></A ->16.2.1. audit</H2 +NAME="AEN2771" +>16.2.1. audit</A +></H2 ><P >A simple module to audit file access to the syslog facility. The following operations are logged: @@ -167,9 +167,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2874" -></A ->16.2.2. recycle</H2 +NAME="AEN2779" +>16.2.2. recycle</A +></H2 ><P >A recycle-bin like modules. When used any unlink call will be intercepted and files moved to the recycle @@ -238,9 +238,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2911" -></A ->16.2.3. netatalk</H2 +NAME="AEN2816" +>16.2.3. netatalk</A +></H2 ><P >A netatalk module, that will ease co-existence of samba and netatalk file sharing services.</P @@ -271,9 +271,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2918" -></A ->16.3. VFS modules available elsewhere</H1 +NAME="AEN2823" +>16.3. VFS modules available elsewhere</A +></H1 ><P >This section contains a listing of various other VFS modules that have been posted but don't currently reside in the Samba CVS @@ -287,9 +287,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2922" -></A ->16.3.1. DatabaseFS</H2 +NAME="AEN2827" +>16.3.1. DatabaseFS</A +></H2 ><P >URL: <A HREF="http://www.css.tayloru.edu/~elorimer/databasefs/index.php" @@ -321,9 +321,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2930" -></A ->16.3.2. vscan</H2 +NAME="AEN2835" +>16.3.2. vscan</A +></H2 ><P >URL: <A HREF="http://www.openantivirus.org/" @@ -373,7 +373,7 @@ WIDTH="33%" ALIGN="right" VALIGN="top" ><A -HREF="cvs-access.html" +HREF="groupmapping.html" ACCESSKEY="N" >Next</A ></TD @@ -397,7 +397,7 @@ ACCESSKEY="U" WIDTH="33%" ALIGN="right" VALIGN="top" ->Access Samba source code via CVS</TD +>Group mapping HOWTO</TD ></TR ></TABLE ></DIV diff --git a/docs/htmldocs/vfstest.1.html b/docs/htmldocs/vfstest.1.html index 56c409288a..ff6310fd3e 100644 --- a/docs/htmldocs/vfstest.1.html +++ b/docs/htmldocs/vfstest.1.html @@ -5,7 +5,7 @@ >vfstest</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"></HEAD +CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD ><BODY CLASS="REFENTRY" BGCOLOR="#FFFFFF" @@ -88,11 +88,9 @@ CLASS="VARIABLELIST" >-d|--debug=debuglevel</DT ><DD ><P -><TT +><VAR CLASS="REPLACEABLE" -><I ->debuglevel</I -></TT +>debuglevel</VAR > is an integer from 0 to 10. The default value if this parameter is not specified is zero.</P @@ -136,9 +134,9 @@ CLASS="FILENAME" ><DD ><P >File name for log/debug files. The extension - <TT + <CODE CLASS="CONSTANT" ->'.client'</TT +>'.client'</CODE > will be appended. The log file is never removed by the client. </P @@ -168,14 +166,14 @@ CLASS="EMPHASIS" ><P ><B CLASS="COMMAND" ->load <module.so></B +>load <module.so></B > - Load specified VFS module </P ></LI ><LI ><P ><B CLASS="COMMAND" ->populate <char> <size></B +>populate <char> <size></B > - Populate a data buffer with the specified data </P ></LI @@ -183,7 +181,7 @@ CLASS="COMMAND" ><P ><B CLASS="COMMAND" ->showdata [<offset> <len>]</B +>showdata [<offset> <len>]</B > - Show data currently in data buffer </P ></LI @@ -434,21 +432,21 @@ CLASS="EMPHASIS" ><P ><B CLASS="COMMAND" ->conf <smb.conf></B +>conf <smb.conf></B > - Load a different configuration file</P ></LI ><LI ><P ><B CLASS="COMMAND" ->help [<command>]</B +>help [<command>]</B > - Get list of commands or info about specified command</P ></LI ><LI ><P ><B CLASS="COMMAND" ->debuglevel <level></B +>debuglevel <level></B > - Set debug level</P ></LI ><LI diff --git a/docs/htmldocs/wbinfo.1.html b/docs/htmldocs/wbinfo.1.html index cf46eca0ef..9c87282ac1 100644 --- a/docs/htmldocs/wbinfo.1.html +++ b/docs/htmldocs/wbinfo.1.html @@ -5,7 +5,7 @@ >wbinfo</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"></HEAD +CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD ><BODY CLASS="REFENTRY" BGCOLOR="#FFFFFF" @@ -140,11 +140,9 @@ CLASS="REFENTRYTITLE" >-N name</DT ><DD ><P ->The <TT +>The <VAR CLASS="PARAMETER" -><I ->-N</I -></TT +>-N</VAR > option queries <SPAN CLASS="CITEREFENTRY" @@ -154,11 +152,9 @@ CLASS="REFENTRYTITLE" >(8)</SPAN > to query the WINS server for the IP address associated with the NetBIOS name - specified by the <TT + specified by the <VAR CLASS="PARAMETER" -><I ->name</I -></TT +>name</VAR > parameter. </P ></DD @@ -166,11 +162,9 @@ CLASS="PARAMETER" >-I ip</DT ><DD ><P ->The <TT +>The <VAR CLASS="PARAMETER" -><I ->-I</I -></TT +>-I</VAR > option queries <SPAN CLASS="CITEREFENTRY" @@ -180,11 +174,9 @@ CLASS="REFENTRYTITLE" >(8)</SPAN > to send a node status request to get the NetBIOS name associated with the IP address - specified by the <TT + specified by the <VAR CLASS="PARAMETER" -><I ->ip</I -></TT +>ip</VAR > parameter. </P ></DD @@ -192,11 +184,9 @@ CLASS="PARAMETER" >-n name</DT ><DD ><P ->The <TT +>The <VAR CLASS="PARAMETER" -><I ->-n</I -></TT +>-n</VAR > option queries <SPAN CLASS="CITEREFENTRY" @@ -215,30 +205,24 @@ CLASS="CITEREFENTRY" CLASS="REFENTRYTITLE" >smb.conf</SPAN >(5)</SPAN -> <TT +> <VAR CLASS="PARAMETER" -><I >workgroup - </I -></TT + </VAR > parameter. </P ></DD ><DT >-s sid</DT ><DD ><P ->Use <TT +>Use <VAR CLASS="PARAMETER" -><I ->-s</I -></TT +>-s</VAR > to resolve - a SID to a name. This is the inverse of the <TT + a SID to a name. This is the inverse of the <VAR CLASS="PARAMETER" -><I >-n - </I -></TT + </VAR > 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 diff --git a/docs/htmldocs/winbind.html b/docs/htmldocs/winbind.html index d587696817..991876796e 100644 --- a/docs/htmldocs/winbind.html +++ b/docs/htmldocs/winbind.html @@ -5,7 +5,7 @@ >Unified Logons between Windows NT and UNIX using Winbind</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -80,9 +80,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2360" -></A ->14.1. Abstract</H1 +NAME="AEN2263" +>14.1. Abstract</A +></H1 ><P >Integration of UNIX and Microsoft Windows NT through a unified logon has been considered a "holy grail" in heterogeneous @@ -107,9 +107,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2364" -></A ->14.2. Introduction</H1 +NAME="AEN2267" +>14.2. Introduction</A +></H1 ><P >It is well known that UNIX and Microsoft Windows NT have different models for representing user and group information and @@ -161,9 +161,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2377" -></A ->14.3. What Winbind Provides</H1 +NAME="AEN2280" +>14.3. What Winbind Provides</A +></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 +203,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2384" -></A ->14.3.1. Target Uses</H2 +NAME="AEN2287" +>14.3.1. Target Uses</A +></H2 ><P >Winbind is targeted at organizations that have an existing NT based domain infrastructure into which they wish @@ -227,9 +227,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2388" -></A ->14.4. How Winbind Works</H1 +NAME="AEN2291" +>14.4. How Winbind Works</A +></H1 ><P >The winbind system is designed around a client/server architecture. A long running <B @@ -247,9 +247,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2393" -></A ->14.4.1. Microsoft Remote Procedure Calls</H2 +NAME="AEN2296" +>14.4.1. Microsoft Remote Procedure Calls</A +></H2 ><P >Over the last few years, efforts have been underway by various Samba Team members to decode various aspects of @@ -273,9 +273,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2397" -></A ->14.4.2. Microsoft Active Directory Services</H2 +NAME="AEN2300" +>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 @@ -292,9 +292,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2400" -></A ->14.4.3. Name Service Switch</H2 +NAME="AEN2303" +>14.4.3. Name Service Switch</A +></H2 ><P >The Name Service Switch, or NSS, is a feature that is present in many UNIX operating systems. It allows system @@ -372,9 +372,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2416" -></A ->14.4.4. Pluggable Authentication Modules</H2 +NAME="AEN2319" +>14.4.4. Pluggable Authentication Modules</A +></H2 ><P >Pluggable Authentication Modules, also known as PAM, is a system for abstracting authentication and authorization @@ -421,9 +421,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2424" -></A ->14.4.5. User and Group ID Allocation</H2 +NAME="AEN2327" +>14.4.5. User and Group ID Allocation</A +></H2 ><P >When a user or group is created under Windows NT is it allocated a numerical relative identifier (RID). This is @@ -447,9 +447,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2428" -></A ->14.4.6. Result Caching</H2 +NAME="AEN2331" +>14.4.6. Result Caching</A +></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 +470,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2431" -></A ->14.5. Installation and Configuration</H1 +NAME="AEN2334" +>14.5. Installation and Configuration</A +></H1 ><P >Many thanks to John Trostel <A HREF="mailto:jtrostel@snapserver.com" @@ -497,9 +497,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2438" -></A ->14.5.1. Introduction</H2 +NAME="AEN2341" +>14.5.1. Introduction</A +></H2 ><P >This HOWTO describes the procedures used to get winbind up and running on my RedHat 7.1 system. Winbind is capable of providing access @@ -556,9 +556,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2451" -></A ->14.5.2. Requirements</H2 +NAME="AEN2354" +>14.5.2. Requirements</A +></H2 ><P >If you have a samba configuration file that you are currently using... <SPAN @@ -626,9 +626,9 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN2465" -></A ->14.5.3. Testing Things Out</H2 +NAME="AEN2368" +>14.5.3. Testing Things Out</A +></H2 ><P >Before starting, it is probably best to kill off all the SAMBA related daemons running on your server. Kill off all <B @@ -671,9 +671,9 @@ CLASS="SECT3" ><H3 CLASS="SECT3" ><A -NAME="AEN2476" -></A ->14.5.3.1. Configure and compile SAMBA</H3 +NAME="AEN2379" +>14.5.3.1. Configure and compile SAMBA</A +></H3 ><P >The configuration and compilation of SAMBA is pretty straightforward. The first three steps may not be necessary depending upon @@ -681,44 +681,44 @@ whether or not you have previously built the Samba binaries.</P ><P ><PRE CLASS="PROGRAMLISTING" -><TT +><SAMP CLASS="PROMPT" ->root#</TT +>root#</SAMP > <B CLASS="COMMAND" >autoconf</B > -<TT +<SAMP CLASS="PROMPT" ->root#</TT +>root#</SAMP > <B CLASS="COMMAND" >make clean</B > -<TT +<SAMP CLASS="PROMPT" ->root#</TT +>root#</SAMP > <B CLASS="COMMAND" >rm config.cache</B > -<TT +<SAMP CLASS="PROMPT" ->root#</TT +>root#</SAMP > <B CLASS="COMMAND" >./configure</B > -<TT +<SAMP CLASS="PROMPT" ->root#</TT +>root#</SAMP > <B CLASS="COMMAND" >make</B > -<TT +<SAMP CLASS="PROMPT" ->root#</TT +>root#</SAMP > <B CLASS="COMMAND" >make install</B @@ -737,13 +737,13 @@ CLASS="SECT3" ><H3 CLASS="SECT3" ><A -NAME="AEN2495" -></A +NAME="AEN2398" >14.5.3.2. Configure <TT CLASS="FILENAME" >nsswitch.conf</TT > and the -winbind libraries</H3 +winbind libraries</A +></H3 ><P >The libraries needed to run the <B CLASS="COMMAND" @@ -751,9 +751,9 @@ CLASS="COMMAND" > daemon through nsswitch need to be copied to their proper locations, so</P ><P -><TT +><SAMP CLASS="PROMPT" ->root#</TT +>root#</SAMP > <B CLASS="COMMAND" >cp ../samba/source/nsswitch/libnss_winbind.so /lib</B @@ -761,9 +761,9 @@ CLASS="COMMAND" ><P >I also found it necessary to make the following symbolic link:</P ><P -><TT +><SAMP CLASS="PROMPT" ->root#</TT +>root#</SAMP > <B CLASS="COMMAND" >ln -s /lib/libnss_winbind.so /lib/libnss_winbind.so.2</B @@ -771,23 +771,23 @@ CLASS="COMMAND" ><P >And, in the case of Sun solaris:</P ><P -><TT +><SAMP CLASS="PROMPT" ->root#</TT +>root#</SAMP > <B CLASS="COMMAND" >ln -s /usr/lib/libnss_winbind.so /usr/lib/libnss_winbind.so.1</B > -<TT +<SAMP CLASS="PROMPT" ->root#</TT +>root#</SAMP > <B CLASS="COMMAND" >ln -s /usr/lib/libnss_winbind.so /usr/lib/nss_winbind.so.1</B > -<TT +<SAMP CLASS="PROMPT" ->root#</TT +>root#</SAMP > <B CLASS="COMMAND" >ln -s /usr/lib/libnss_winbind.so /usr/lib/nss_winbind.so.2</B @@ -823,9 +823,9 @@ CLASS="COMMAND" your system reboots, but it is faster (and you don't need to reboot) if you do it manually:</P ><P -><TT +><SAMP CLASS="PROMPT" ->root#</TT +>root#</SAMP > <B CLASS="COMMAND" >/sbin/ldconfig -v | grep winbind</B @@ -842,9 +842,9 @@ CLASS="SECT3" ><H3 CLASS="SECT3" ><A -NAME="AEN2528" -></A ->14.5.3.3. Configure smb.conf</H3 +NAME="AEN2431" +>14.5.3.3. Configure smb.conf</A +></H3 ><P >Several parameters are needed in the smb.conf file to control the behavior of <B @@ -869,7 +869,7 @@ include the following entries in the [global] section:</P ><PRE CLASS="PROGRAMLISTING" >[global] - <...> + <...> # separate domain and username with '+', like DOMAIN+username <A HREF="winbindd.8.html#WINBINDSEPARATOR" @@ -917,44 +917,36 @@ CLASS="SECT3" ><H3 CLASS="SECT3" ><A -NAME="AEN2544" -></A ->14.5.3.4. Join the SAMBA server to the PDC domain</H3 +NAME="AEN2447" +>14.5.3.4. Join the SAMBA server to the PDC domain</A +></H3 ><P >Enter the following command to make the SAMBA server join the -PDC domain, where <TT +PDC domain, where <VAR CLASS="REPLACEABLE" -><I ->DOMAIN</I -></TT +>DOMAIN</VAR > is the name of -your Windows domain and <TT +your Windows domain and <VAR CLASS="REPLACEABLE" -><I ->Administrator</I -></TT +>Administrator</VAR > is a domain user who has administrative privileges in the domain.</P ><P -><TT +><SAMP CLASS="PROMPT" ->root#</TT +>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 -<TT +<VAR CLASS="REPLACEABLE" -><I ->DOMAIN</I -></TT ->" where <TT +>DOMAIN</VAR +>" where <VAR CLASS="REPLACEABLE" -><I ->DOMAIN</I -></TT +>DOMAIN</VAR > is your DOMAIN name.</P ></DIV @@ -963,9 +955,9 @@ CLASS="SECT3" ><H3 CLASS="SECT3" ><A -NAME="AEN2555" -></A ->14.5.3.5. Start up the winbindd daemon and test it!</H3 +NAME="AEN2458" +>14.5.3.5. Start up the winbindd daemon and test it!</A +></H3 ><P >Eventually, you will want to modify your smb startup script to automatically invoke the winbindd daemon when the other parts of @@ -973,9 +965,9 @@ SAMBA start, but it is possible to test out just the winbind portion first. To start up winbind services, enter the following command as root:</P ><P -><TT +><SAMP CLASS="PROMPT" ->root#</TT +>root#</SAMP > <B CLASS="COMMAND" >/usr/local/samba/bin/winbindd</B @@ -984,9 +976,9 @@ CLASS="COMMAND" >I'm always paranoid and like to make sure the daemon is really running...</P ><P -><TT +><SAMP CLASS="PROMPT" ->root#</TT +>root#</SAMP > <B CLASS="COMMAND" >ps -ae | grep winbindd</B @@ -999,9 +991,9 @@ CLASS="COMMAND" >Now... for the real test, try to get some information about the users on your PDC</P ><P -><TT +><SAMP CLASS="PROMPT" ->root#</TT +>root#</SAMP > <B CLASS="COMMAND" >/usr/local/samba/bin/wbinfo -u</B @@ -1021,12 +1013,10 @@ CEO+krbtgt CEO+TsInternetUser</PRE ></P ><P ->Obviously, I have named my domain 'CEO' and my <TT +>Obviously, I have named my domain 'CEO' and my <VAR CLASS="PARAMETER" -><I >winbind -separator</I -></TT +separator</VAR > is '+'.</P ><P >You can do the same sort of thing to get group information from @@ -1034,9 +1024,9 @@ the PDC:</P ><P ><PRE CLASS="PROGRAMLISTING" -><TT +><SAMP CLASS="PROMPT" ->root#</TT +>root#</SAMP > <B CLASS="COMMAND" >/usr/local/samba/bin/wbinfo -g</B @@ -1056,9 +1046,9 @@ CEO+Group Policy Creator Owners</PRE lists of both local and PDC users and groups. Try the following command:</P ><P -><TT +><SAMP CLASS="PROMPT" ->root#</TT +>root#</SAMP > <B CLASS="COMMAND" >getent passwd</B @@ -1073,9 +1063,9 @@ directories and default shells.</P ><P >The same thing can be done for groups with the command</P ><P -><TT +><SAMP CLASS="PROMPT" ->root#</TT +>root#</SAMP > <B CLASS="COMMAND" >getent group</B @@ -1086,17 +1076,17 @@ CLASS="SECT3" ><H3 CLASS="SECT3" ><A -NAME="AEN2591" -></A ->14.5.3.6. Fix the init.d startup scripts</H3 +NAME="AEN2494" +>14.5.3.6. Fix the init.d startup scripts</A +></H3 ><DIV CLASS="SECT4" ><H4 CLASS="SECT4" ><A -NAME="AEN2593" -></A ->14.5.3.6.1. Linux</H4 +NAME="AEN2496" +>14.5.3.6.1. Linux</A +></H4 ><P >The <B CLASS="COMMAND" @@ -1153,7 +1143,7 @@ CLASS="PROGRAMLISTING" daemon /usr/local/samba/bin/winbindd RETVAL3=$? echo - [ $RETVAL -eq 0 -a $RETVAL2 -eq 0 -a $RETVAL3 -eq 0 ] && touch /var/lock/subsys/smb || \ + [ $RETVAL -eq 0 -a $RETVAL2 -eq 0 -a $RETVAL3 -eq 0 ] && touch /var/lock/subsys/smb || \ RETVAL=1 return $RETVAL }</PRE @@ -1179,7 +1169,7 @@ CLASS="PROGRAMLISTING" echo -n $"Shutting down $KIND services: " killproc winbindd RETVAL3=$? - [ $RETVAL -eq 0 -a $RETVAL2 -eq 0 -a $RETVAL3 -eq 0 ] && rm -f /var/lock/subsys/smb + [ $RETVAL -eq 0 -a $RETVAL2 -eq 0 -a $RETVAL3 -eq 0 ] && rm -f /var/lock/subsys/smb echo "" return $RETVAL }</PRE @@ -1190,9 +1180,9 @@ CLASS="SECT4" ><H4 CLASS="SECT4" ><A -NAME="AEN2610" -></A ->14.5.3.6.2. Solaris</H4 +NAME="AEN2513" +>14.5.3.6.2. Solaris</A +></H4 ><P >On solaris, you need to modify the <TT @@ -1221,7 +1211,7 @@ killproc() { # kill the named process(es) pid=`/usr/bin/ps -e | /usr/bin/grep -w $1 | /usr/bin/sed -e 's/^ *//' -e 's/ .*//'` - [ "$pid" != "" ] && kill $pid + [ "$pid" != "" ] && kill $pid } # Start/stop processes required for samba server @@ -1261,9 +1251,9 @@ CLASS="SECT4" ><H4 CLASS="SECT4" ><A -NAME="AEN2617" -></A ->14.5.3.6.3. Restarting</H4 +NAME="AEN2520" +>14.5.3.6.3. Restarting</A +></H4 ><P >If you restart the <B CLASS="COMMAND" @@ -1285,9 +1275,9 @@ CLASS="SECT3" ><H3 CLASS="SECT3" ><A -NAME="AEN2623" -></A ->14.5.3.7. Configure Winbind and PAM</H3 +NAME="AEN2526" +>14.5.3.7. Configure Winbind and PAM</A +></H3 ><P >If you have made it this far, you know that winbindd and samba are working together. If you want to use winbind to provide authentication for other @@ -1305,9 +1295,9 @@ CLASS="FILENAME" > directory by invoking the command</P ><P -><TT +><SAMP CLASS="PROMPT" ->root#</TT +>root#</SAMP > <B CLASS="COMMAND" >make nsswitch/pam_winbind.so</B @@ -1331,9 +1321,9 @@ CLASS="FILENAME" >/usr/lib/security</TT >.</P ><P -><TT +><SAMP CLASS="PROMPT" ->root#</TT +>root#</SAMP > <B CLASS="COMMAND" >cp ../samba/source/nsswitch/pam_winbind.so /lib/security</B @@ -1343,9 +1333,9 @@ CLASS="SECT4" ><H4 CLASS="SECT4" ><A -NAME="AEN2640" -></A ->14.5.3.7.1. Linux/FreeBSD-specific PAM configuration</H4 +NAME="AEN2543" +>14.5.3.7.1. Linux/FreeBSD-specific PAM configuration</A +></H4 ><P >The <TT CLASS="FILENAME" @@ -1472,9 +1462,9 @@ CLASS="SECT4" ><H4 CLASS="SECT4" ><A -NAME="AEN2673" -></A ->14.5.3.7.2. Solaris-specific configuration</H4 +NAME="AEN2576" +>14.5.3.7.2. Solaris-specific configuration</A +></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 @@ -1559,9 +1549,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2680" -></A ->14.6. Limitations</H1 +NAME="AEN2583" +>14.6. Limitations</A +></H1 ><P >Winbind has a number of limitations in its current released version that we hope to overcome in future @@ -1601,9 +1591,9 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN2690" -></A ->14.7. Conclusion</H1 +NAME="AEN2593" +>14.7. Conclusion</A +></H1 ><P >The winbind system, through the use of the Name Service Switch, Pluggable Authentication Modules, and appropriate diff --git a/docs/htmldocs/winbindd.8.html b/docs/htmldocs/winbindd.8.html index dba9988e30..b114c40647 100644 --- a/docs/htmldocs/winbindd.8.html +++ b/docs/htmldocs/winbindd.8.html @@ -5,7 +5,7 @@ >winbindd</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"></HEAD +CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD ><BODY CLASS="REFENTRY" BGCOLOR="#FFFFFF" @@ -38,7 +38,7 @@ NAME="AEN8" ><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" @@ -84,16 +84,12 @@ CLASS="COMMAND" CLASS="FILENAME" >pam_winbind</TT > module in the 2.2.2 release only - supports the <TT + supports the <VAR CLASS="PARAMETER" -><I ->auth</I -></TT -> and <TT +>auth</VAR +> and <VAR CLASS="PARAMETER" -><I ->account</I -></TT +>account</VAR > module-types. The latter simply performs a getpwnam() to verify that the system can obtain a uid for the @@ -374,11 +370,9 @@ CLASS="REFENTRYTITLE" ><A HREF="smb.conf.5.html#WINBINDSEPARATOR" TARGET="_top" -> <TT +> <VAR CLASS="PARAMETER" -><I ->winbind separator</I -></TT +>winbind separator</VAR ></A ></P ></LI @@ -387,11 +381,9 @@ CLASS="PARAMETER" ><A HREF="smb.conf.5.html#WINBINDUID" TARGET="_top" -> <TT +> <VAR CLASS="PARAMETER" -><I ->winbind uid</I -></TT +>winbind uid</VAR ></A ></P ></LI @@ -400,11 +392,9 @@ CLASS="PARAMETER" ><A HREF="smb.conf.5.html#WINBINDGID" TARGET="_top" -> <TT +> <VAR CLASS="PARAMETER" -><I ->winbind gid</I -></TT +>winbind gid</VAR ></A ></P ></LI @@ -413,11 +403,9 @@ CLASS="PARAMETER" ><A HREF="smb.conf.5.html#WINBINDCACHETIME" TARGET="_top" -> <TT +> <VAR CLASS="PARAMETER" -><I ->winbind cache time</I -></TT +>winbind cache time</VAR ></A ></P ></LI @@ -426,11 +414,9 @@ CLASS="PARAMETER" ><A HREF="smb.conf.5.html#WINBINDENUMUSERS" TARGET="_top" -> <TT +> <VAR CLASS="PARAMETER" -><I ->winbind enum users</I -></TT +>winbind enum users</VAR ></A ></P ></LI @@ -439,11 +425,9 @@ CLASS="PARAMETER" ><A HREF="smb.conf.5.html#WINBINDENUMGROUPS" TARGET="_top" -> <TT +> <VAR CLASS="PARAMETER" -><I ->winbind enum groups</I -></TT +>winbind enum groups</VAR ></A ></P ></LI @@ -452,11 +436,9 @@ CLASS="PARAMETER" ><A HREF="smb.conf.5.html#TEMPLATEHOMEDIR" TARGET="_top" -> <TT +> <VAR CLASS="PARAMETER" -><I ->template homedir</I -></TT +>template homedir</VAR ></A ></P ></LI @@ -465,11 +447,9 @@ CLASS="PARAMETER" ><A HREF="smb.conf.5.html#TEMPLATESHELL" TARGET="_top" -> <TT +> <VAR CLASS="PARAMETER" -><I ->template shell</I -></TT +>template shell</VAR ></A ></P ></LI @@ -478,11 +458,9 @@ CLASS="PARAMETER" ><A HREF="smb.conf.5.html#WINBINDUSEDEFAULTDOMAIN" TARGET="_top" -> <TT +> <VAR CLASS="PARAMETER" -><I ->winbind use default domain</I -></TT +>winbind use default domain</VAR ></A ></P ></LI @@ -514,11 +492,9 @@ group: files winbind</PRE >In <TT CLASS="FILENAME" >/etc/pam.d/*</TT -> replace the <TT +> replace the <VAR CLASS="PARAMETER" -><I -> auth</I -></TT +> auth</VAR > lines with something like this: <PRE CLASS="PROGRAMLISTING" @@ -528,17 +504,13 @@ auth sufficient /lib/security/pam_winbind.so auth required /lib/security/pam_pwdb.so use_first_pass shadow nullok</PRE ></P ><P ->Note in particular the use of the <TT +>Note in particular the use of the <VAR CLASS="PARAMETER" -><I >sufficient - </I -></TT -> keyword and the <TT + </VAR +> keyword and the <VAR CLASS="PARAMETER" -><I ->use_first_pass</I -></TT +>use_first_pass</VAR > keyword. </P ><P >Now replace the account lines with this: </P @@ -560,11 +532,9 @@ CLASS="COMMAND" >net join -S PDC -U Administrator</B ></P ><P ->The username after the <TT +>The username after the <VAR CLASS="PARAMETER" -><I ->-U</I -></TT +>-U</VAR > can be any Domain user that has administrator privileges on the machine. Substitute the name or IP of your PDC for "PDC".</P @@ -672,9 +642,9 @@ CLASS="COMMAND" CLASS="COMMAND" >winbindd</B > - nsswitch module read an environment variable named <TT + nsswitch module read an environment variable named <VAR CLASS="ENVAR" -> $WINBINDD_DOMAIN</TT +> $WINBINDD_DOMAIN</VAR >. 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 @@ -802,11 +772,9 @@ 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 <TT + compiled using the <VAR CLASS="PARAMETER" -><I ->--with-lockdir</I -></TT +>--with-lockdir</VAR > option. This directory is by default <TT CLASS="FILENAME" |