sin/samba-mirror
1
0
Fork 0
mirror of https://github.com/samba-team/samba.git synced 2025-07-31 20:22:15 +03:00
Code Activity

'make everything' in docs

Browse Source
This commit is contained in:
Jelmer Vernooij
-
parent 7f9b0dbf5b
commit 960082d860
53 changed files with 15310 additions and 11443 deletions
Download Patch File Download Diff File Expand all files Collapse all files

BIN
docs/Samba-Developers-Guide.pdf
View File

Binary file not shown.

BIN
docs/Samba-HOWTO-Collection.pdf
View File

Binary file not shown.

1
docs/docs-status
View File

@ -45,6 +45,7 @@ docs/docbook/manpages/testparm.1.sgml
docs/docbook/manpages/testprns.1.sgml
Stuff that needs to be documented:
Doc for package maintainers
Some kind of introduction to the various terms used (locking, wins, browsing, domain, ... )
Merge the various docs about wins and browsing
Windows NT 4.0 Style Trust Relationship

24
docs/faq/clientapp.html
View File

@ -10,8 +10,8 @@ REL="HOME"
TITLE="Samba FAQ"
HREF="samba-faq.html"><LINK
REL="PREVIOUS"
TITLE="Compiling and installing Samba on a Unix host"
HREF="install.html"><LINK
TITLE="Configuration problems"
HREF="config.html"><LINK
REL="NEXT"
TITLE="Common errors"
HREF="errors.html"></HEAD
@ -42,7 +42,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="install.html"
HREF="config.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -71,15 +71,15 @@ CLASS="CHAPTER"
><A
NAME="CLIENTAPP"
></A
>Chapter 3. Specific client application problems</H1
>Chapter 4. Specific client application problems</H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN170"
NAME="AEN175"
></A
>3.1. MS Office Setup reports "Cannot change properties of '\MSOFFICE\SETUP.INI'"</H1
>4.1. MS Office Setup reports "Cannot change properties of '\MSOFFICE\SETUP.INI'"</H1
><P
>When installing MS Office on a Samba drive for which you have admin
user permissions, ie. admin users = username, you will find the
@ -98,9 +98,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN175"
NAME="AEN180"
></A
>3.2. How to use a Samba share as an administrative share for MS Office, etc.</H1
>4.2. How to use a Samba share as an administrative share for MS Office, etc.</H1
><P
>Microsoft Office products can be installed as an administrative installation
from which the application can either be run off the administratively installed
@ -160,9 +160,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN190"
NAME="AEN195"
></A
>3.3. Microsoft Access database opening errors</H1
>4.3. Microsoft Access database opening errors</H1
><P
>Here are some notes on running MS-Access on a Samba drive from <A
HREF="stefank@esi.com.au"
@ -210,7 +210,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="install.html"
HREF="config.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -238,7 +238,7 @@ ACCESSKEY="N"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Compiling and installing Samba on a Unix host</TD
>Configuration problems</TD
><TD
WIDTH="34%"
ALIGN="center"

33
docs/faq/errors.html
View File

@ -71,15 +71,15 @@ CLASS="CHAPTER"
><A
NAME="ERRORS"
></A
>Chapter 4. Common errors</H1
>Chapter 5. Common errors</H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN201"
NAME="AEN206"
></A
>4.1. Not listening for calling name</H1
>5.1. Not listening for calling name</H1
><P
><PRE
CLASS="PROGRAMLISTING"
@ -103,9 +103,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN208"
NAME="AEN213"
></A
>4.2. System Error 1240</H1
>5.2. System Error 1240</H1
><P
>System error 1240 means that the client is refusing to talk
to a non-encrypting server. Microsoft changed WinNT in service
@ -139,9 +139,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN215"
NAME="AEN220"
></A
>4.3. smbclient ignores -N !</H1
>5.3. smbclient ignores -N !</H1
><P
><SPAN
CLASS="QUOTE"
@ -174,9 +174,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN224"
NAME="AEN229"
></A
>4.4. The data on the CD-Drive I've shared seems to be corrupted!</H1
>5.4. The data on the CD-Drive I've shared seems to be corrupted!</H1
><P
>Some OSes (notably Linux) default to auto detection of file type on
cdroms and do cr/lf translation. This is a very bad idea when use with
@ -190,9 +190,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN228"
NAME="AEN233"
></A
>4.5. Why can users access home directories of other users?</H1
>5.5. Why can users access home directories of other users?</H1
><P
><SPAN
CLASS="QUOTE"
@ -243,6 +243,17 @@ CLASS="PROGRAMLISTING"
to the definition of the [homes] share, as recommended in
the smb.conf man page.</P
></DIV
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN246"
></A
>5.6. Until a few minutes after samba has started, clients get the error "Domain Controller Unavailable"</H1
><P
>A domain controller has to announce on the network who it is. This usually takes a while.</P
></DIV
></DIV
><DIV
CLASS="NAVFOOTER"

10
docs/faq/install.html
View File

@ -13,8 +13,8 @@ REL="PREVIOUS"
TITLE="General Information"
HREF="general.html"><LINK
REL="NEXT"
TITLE="Specific client application problems"
HREF="clientapp.html"></HEAD
TITLE="Configuration problems"
HREF="config.html"></HEAD
><BODY
CLASS="CHAPTER"
BGCOLOR="#FFFFFF"
@ -56,7 +56,7 @@ WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="clientapp.html"
HREF="config.html"
ACCESSKEY="N"
>Next</A
></TD
@ -496,7 +496,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="clientapp.html"
HREF="config.html"
ACCESSKEY="N"
>Next</A
></TD
@ -516,7 +516,7 @@ VALIGN="top"
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Specific client application problems</TD
>Configuration problems</TD
></TR
></TABLE
></DIV

96
docs/faq/samba-faq.html
View File

@ -156,118 +156,142 @@ HREF="install.html#AEN155"
></DD
><DT
>3. <A
HREF="config.html"
>Configuration problems</A
></DT
><DD
><DL
><DT
>3.1. <A
HREF="config.html#AEN170"
>I have set 'force user' and samba still makes 'root' the owner of all the files I touch!</A
></DT
></DL
></DD
><DT
>4. <A
HREF="clientapp.html"
>Specific client application problems</A
></DT
><DD
><DL
><DT
>3.1. <A
HREF="clientapp.html#AEN170"
>4.1. <A
HREF="clientapp.html#AEN175"
>MS Office Setup reports "Cannot change properties of '\MSOFFICE\SETUP.INI'"</A
></DT
><DT
>3.2. <A
HREF="clientapp.html#AEN175"
>4.2. <A
HREF="clientapp.html#AEN180"
>How to use a Samba share as an administrative share for MS Office, etc.</A
></DT
><DT
>3.3. <A
HREF="clientapp.html#AEN190"
>4.3. <A
HREF="clientapp.html#AEN195"
>Microsoft Access database opening errors</A
></DT
></DL
></DD
><DT
>4. <A
>5. <A
HREF="errors.html"
>Common errors</A
></DT
><DD
><DL
><DT
>4.1. <A
HREF="errors.html#AEN201"
>5.1. <A
HREF="errors.html#AEN206"
>Not listening for calling name</A
></DT
><DT
>4.2. <A
HREF="errors.html#AEN208"
>5.2. <A
HREF="errors.html#AEN213"
>System Error 1240</A
></DT
><DT
>4.3. <A
HREF="errors.html#AEN215"
>5.3. <A
HREF="errors.html#AEN220"
>smbclient ignores -N !</A
></DT
><DT
>4.4. <A
HREF="errors.html#AEN224"
>5.4. <A
HREF="errors.html#AEN229"
>The data on the CD-Drive I've shared seems to be corrupted!</A
></DT
><DT
>4.5. <A
HREF="errors.html#AEN228"
>5.5. <A
HREF="errors.html#AEN233"
>Why can users access home directories of other users?</A
></DT
><DT
>5.6. <A
HREF="errors.html#AEN246"
>Until a few minutes after samba has started, clients get the error "Domain Controller Unavailable"</A
></DT
></DL
></DD
><DT
>5. <A
>6. <A
HREF="features.html"
>Features</A
></DT
><DD
><DL
><DT
>5.1. <A
HREF="features.html#AEN243"
>6.1. <A
HREF="features.html#AEN251"
>How can I prevent my samba server from being used to distribute the Nimda worm?</A
></DT
><DT
>5.2. <A
HREF="features.html#AEN257"
>6.2. <A
HREF="features.html#AEN265"
>How can I use samba as a fax server?</A
></DT
><DD
><DL
><DT
>5.2.1. <A
HREF="features.html#AEN268"
>6.2.1. <A
HREF="features.html#AEN276"
>Tools for printing faxes</A
></DT
><DT
>5.2.2. <A
HREF="features.html#AEN278"
>6.2.2. <A
HREF="features.html#AEN286"
>Making the fax-server</A
></DT
><DT
>5.2.3. <A
HREF="features.html#AEN294"
>6.2.3. <A
HREF="features.html#AEN302"
>Installing the client drivers</A
></DT
><DT
>5.2.4. <A
HREF="features.html#AEN308"
>6.2.4. <A
HREF="features.html#AEN316"
>Example smb.conf</A
></DT
></DL
></DD
><DT
>5.3. <A
HREF="features.html#AEN312"
>6.3. <A
HREF="features.html#AEN320"
>Samba doesn't work well together with DHCP!</A
></DT
><DT
>5.4. <A
HREF="features.html#AEN325"
>6.4. <A
HREF="features.html#AEN333"
>How can I assign NetBIOS names to clients with DHCP?</A
></DT
><DT
>5.5. <A
HREF="features.html#AEN332"
>6.5. <A
HREF="features.html#AEN340"
>How do I convert between unix and dos text formats?</A
></DT
><DT
>6.6. <A
HREF="features.html#AEN345"
>Does samba have wins replication support?</A
></DT
></DL
></DD
></DL

2313
docs/htmldocs/Samba-Developers-Guide.html
View File

File diff suppressed because it is too large Load Diff

21226
docs/htmldocs/Samba-HOWTO-Collection.html
View File

File diff suppressed because it is too large Load Diff

55
docs/htmldocs/browsing-quick.html
View File

@ -9,12 +9,15 @@ 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="p18.html"><LINK
REL="PREVIOUS"
TITLE="Improved browsing in samba"
HREF="improved-browsing.html"><LINK
TITLE="Oplocks"
HREF="oplocks.html"><LINK
REL="NEXT"
TITLE="Samba performance issues"
HREF="speed.html"></HEAD
TITLE="LanMan and NT Password Encryption in Samba"
HREF="pwencrypt.html"></HEAD
><BODY
CLASS="CHAPTER"
BGCOLOR="#FFFFFF"
@ -42,7 +45,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="improved-browsing.html"
HREF="oplocks.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -56,7 +59,7 @@ WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="speed.html"
HREF="pwencrypt.html"
ACCESSKEY="N"
>Next</A
></TD
@ -71,7 +74,7 @@ CLASS="CHAPTER"
><A
NAME="BROWSING-QUICK"
></A
>Chapter 16. Quick Cross Subnet Browsing / Cross Workgroup Browsing guide</H1
>Chapter 4. Quick Cross Subnet Browsing / Cross Workgroup Browsing guide</H1
><P
>This document should be read in conjunction with Browsing and may
be taken as the fast track guide to implementing browsing across subnets
@ -83,9 +86,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2665"
NAME="AEN392"
></A
>16.1. Discussion</H1
>4.1. Discussion</H1
><P
>Firstly, all MS Windows networking is based on SMB (Server Message
Block) based messaging. SMB messaging is implemented using NetBIOS. Samba
@ -129,9 +132,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2673"
NAME="AEN400"
></A
>16.2. Use of the "Remote Announce" parameter</H1
>4.2. Use of the "Remote Announce" parameter</H1
><P
>The "remote announce" parameter of smb.conf can be used to forcibly ensure
that all the NetBIOS names on a network get announced to a remote network.
@ -187,9 +190,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2687"
NAME="AEN414"
></A
>16.3. Use of the "Remote Browse Sync" parameter</H1
>4.3. Use of the "Remote Browse Sync" parameter</H1
><P
>The "remote browse sync" parameter of smb.conf is used to announce to
another LMB that it must synchronise it's NetBIOS name list with our
@ -209,9 +212,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2692"
NAME="AEN419"
></A
>16.4. Use of WINS</H1
>4.4. Use of WINS</H1
><P
>Use of WINS (either Samba WINS _or_ MS Windows NT Server WINS) is highly
recommended. Every NetBIOS machine registers it's name together with a
@ -271,9 +274,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2703"
NAME="AEN430"
></A
>16.5. Do NOT use more than one (1) protocol on MS Windows machines</H1
>4.5. Do NOT use more than one (1) protocol on MS Windows machines</H1
><P
>A very common cause of browsing problems results from installing more than
one protocol on an MS Windows machine.</P
@ -301,9 +304,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2709"
NAME="AEN436"
></A
>16.6. Name Resolution Order</H1
>4.6. Name Resolution Order</H1
><P
>Resolution of NetBIOS names to IP addresses can take place using a number
of methods. The only ones that can provide NetBIOS name_type information
@ -398,7 +401,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="improved-browsing.html"
HREF="oplocks.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -416,7 +419,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="speed.html"
HREF="pwencrypt.html"
ACCESSKEY="N"
>Next</A
></TD
@ -426,17 +429,21 @@ ACCESSKEY="N"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Improved browsing in samba</TD
>Oplocks</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><A
HREF="p18.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Samba performance issues</TD
>LanMan and NT Password Encryption in Samba</TD
></TR
></TABLE
></DIV

72
docs/htmldocs/bugreport.html
View File

@ -9,12 +9,15 @@ CONTENT="Modular DocBook HTML Stylesheet Version 1.77"><LINK
REL="HOME"
TITLE="SAMBA Project Documentation"
HREF="samba-howto-collection.html"><LINK
REL="UP"
TITLE="Appendixes"
HREF="p3106.html"><LINK
REL="PREVIOUS"
TITLE="HOWTO Access Samba source code via CVS"
HREF="cvs-access.html"><LINK
TITLE="Samba and other CIFS clients"
HREF="other-clients.html"><LINK
REL="NEXT"
TITLE="Group mapping HOWTO"
HREF="groupmapping.html"></HEAD
TITLE="Diagnosing your samba server"
HREF="diagnosis.html"></HEAD
><BODY
CLASS="CHAPTER"
BGCOLOR="#FFFFFF"
@ -42,7 +45,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="cvs-access.html"
HREF="other-clients.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -56,7 +59,7 @@ WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="groupmapping.html"
HREF="diagnosis.html"
ACCESSKEY="N"
>Next</A
></TD
@ -71,17 +74,26 @@ CLASS="CHAPTER"
><A
NAME="BUGREPORT"
></A
>Chapter 19. Reporting Bugs</H1
>Chapter 25. Reporting Bugs</H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2921"
NAME="AEN3285"
></A
>19.1. Introduction</H1
>25.1. Introduction</H1
><P
>The email address for bug reports is samba@samba.org</P
>The email address for bug reports for stable releases is <A
HREF="samba@samba.org"
TARGET="_top"
>samba@samba.org</A
>.
Bug reports for alpha releases should go to <A
HREF="mailto:samba-technical@samba.org"
TARGET="_top"
>samba-technical@samba.org</A
>.</P
><P
>Please take the time to read this file before you submit a bug
report. Also, please see if it has changed between releases, as we
@ -102,16 +114,20 @@ that list that may be able to help you.</P
><P
>You may also like to look though the recent mailing list archives,
which are conveniently accessible on the Samba web pages
at http://samba.org/samba/ </P
at <A
HREF="http://samba.org/samba/"
TARGET="_top"
>http://samba.org/samba/</A
>.</P
></DIV
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2928"
NAME="AEN3295"
></A
>19.2. General info</H1
>25.2. General info</H1
><P
>Before submitting a bug report check your config for silly
errors. Look in your log files for obvious messages that tell you that
@ -134,9 +150,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2934"
NAME="AEN3301"
></A
>19.3. Debug levels</H1
>25.3. Debug levels</H1
><P
>If the bug has anything to do with Samba behaving incorrectly as a
server (like refusing to open a file) then the log files will probably
@ -204,9 +220,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2951"
NAME="AEN3318"
></A
>19.4. Internal errors</H1
>25.4. Internal errors</H1
><P
>If you get a "INTERNAL ERROR" message in your log files it means that
Samba got an unexpected signal while running. It is probably a
@ -248,9 +264,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2961"
NAME="AEN3328"
></A
>19.5. Attaching to a running process</H1
>25.5. Attaching to a running process</H1
><P
>Unfortunately some unixes (in particular some recent linux kernels)
refuse to dump a core file if the task has changed uid (which smbd
@ -265,9 +281,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2964"
NAME="AEN3331"
></A
>19.6. Patches</H1
>25.6. Patches</H1
><P
>The best sort of bug report is one that includes a fix! If you send us
patches please use <B
@ -298,7 +314,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="cvs-access.html"
HREF="other-clients.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -316,7 +332,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="groupmapping.html"
HREF="diagnosis.html"
ACCESSKEY="N"
>Next</A
></TD
@ -326,17 +342,21 @@ ACCESSKEY="N"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>HOWTO Access Samba source code via CVS</TD
>Samba and other CIFS clients</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><A
HREF="p3106.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Group mapping HOWTO</TD
>Diagnosing your samba server</TD
></TR
></TABLE
></DIV

47
docs/htmldocs/cvs-access.html
View File

@ -9,12 +9,15 @@ 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="p1346.html"><LINK
REL="PREVIOUS"
TITLE="Samba performance issues"
HREF="speed.html"><LINK
TITLE="Storing Samba's User/Machine Account information in an LDAP Directory"
HREF="samba-ldap-howto.html"><LINK
REL="NEXT"
TITLE="Reporting Bugs"
HREF="bugreport.html"></HEAD
TITLE="Group mapping HOWTO"
HREF="groupmapping.html"></HEAD
><BODY
CLASS="CHAPTER"
BGCOLOR="#FFFFFF"
@ -42,7 +45,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="speed.html"
HREF="samba-ldap-howto.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -56,7 +59,7 @@ WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="bugreport.html"
HREF="groupmapping.html"
ACCESSKEY="N"
>Next</A
></TD
@ -71,15 +74,15 @@ CLASS="CHAPTER"
><A
NAME="CVS-ACCESS"
></A
>Chapter 18. HOWTO Access Samba source code via CVS</H1
>Chapter 20. HOWTO Access Samba source code via CVS</H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2873"
NAME="AEN2891"
></A
>18.1. Introduction</H1
>20.1. Introduction</H1
><P
>Samba is developed in an open environment. Developers use CVS
(Concurrent Versioning System) to "checkin" (also known as
@ -99,9 +102,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2878"
NAME="AEN2896"
></A
>18.2. CVS Access to samba.org</H1
>20.2. CVS Access to samba.org</H1
><P
>The machine samba.org runs a publicly accessible CVS
repository for access to the source code of several packages,
@ -112,9 +115,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN2881"
NAME="AEN2899"
></A
>18.2.1. Access via CVSweb</H2
>20.2.1. Access via CVSweb</H2
><P
>You can access the source code via your
favourite WWW browser. This allows you to access the contents of
@ -133,9 +136,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN2886"
NAME="AEN2904"
></A
>18.2.2. Access via cvs</H2
>20.2.2. Access via cvs</H2
><P
>You can also access the source code via a
normal cvs client. This gives you much more control over you can
@ -253,7 +256,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="speed.html"
HREF="samba-ldap-howto.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -271,7 +274,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="bugreport.html"
HREF="groupmapping.html"
ACCESSKEY="N"
>Next</A
></TD
@ -281,17 +284,21 @@ ACCESSKEY="N"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Samba performance issues</TD
>Storing Samba's User/Machine Account information in an LDAP Directory</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><A
HREF="p1346.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Reporting Bugs</TD
>Group mapping HOWTO</TD
></TR
></TABLE
></DIV

102
docs/htmldocs/diagnosis.html
View File

@ -9,9 +9,12 @@ CONTENT="Modular DocBook HTML Stylesheet Version 1.77"><LINK
REL="HOME"
TITLE="SAMBA Project Documentation"
HREF="samba-howto-collection.html"><LINK
REL="UP"
TITLE="Appendixes"
HREF="p3106.html"><LINK
REL="PREVIOUS"
TITLE="Samba and other CIFS clients"
HREF="other-clients.html"></HEAD
TITLE="Reporting Bugs"
HREF="bugreport.html"></HEAD
><BODY
CLASS="CHAPTER"
BGCOLOR="#FFFFFF"
@ -39,7 +42,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="other-clients.html"
HREF="bugreport.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -64,47 +67,44 @@ CLASS="CHAPTER"
><A
NAME="DIAGNOSIS"
></A
>Chapter 23. Diagnosing your samba server</H1
>Chapter 26. Diagnosing your samba server</H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN3184"
NAME="AEN3354"
></A
>23.1. Introduction</H1
>26.1. Introduction</H1
><P
>This file contains a list of tests you can perform to validate your
Samba server. It also tells you what the likely cause of the problem
is if it fails any one of these steps. If it passes all these tests
then it is probably working fine.</P
><P
>You should do ALL the tests, in the order shown. I have tried to
>You should do ALL the tests, in the order shown. We have tried to
carefully choose them so later tests only use capabilities verified in
the earlier tests.</P
><P
>If you send me an email saying "it doesn't work" and you have not
followed this test procedure then you should not be surprised if I
ignore your email.</P
>If you send one of the samba mailing lists an email saying "it doesn't work"
and you have not followed this test procedure then you should not be surprised
your email is ignored.</P
></DIV
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN3189"
NAME="AEN3359"
></A
>23.2. Assumptions</H1
>26.2. Assumptions</H1
><P
>In all of the tests I assume you have a Samba server called BIGSERVER
and a PC called ACLIENT both in workgroup TESTGROUP. I also assume the
PC is running windows for workgroups with a recent copy of the
microsoft tcp/ip stack. Alternatively, your PC may be running Windows
95 or Windows NT (Workstation or Server).</P
>In all of the tests it is assumed you have a Samba server called
BIGSERVER and a PC called ACLIENT both in workgroup TESTGROUP.</P
><P
>The procedure is similar for other types of clients.</P
><P
>I also assume you know the name of an available share in your
>It is also assumed you know the name of an available share in your
smb.conf. I will assume this share is called "tmp". You can add a
"tmp" share like by adding the following to smb.conf:</P
><P
@ -116,7 +116,7 @@ CLASS="PROGRAMLISTING"
read only = yes&#13;</PRE
></P
><P
>THESE TESTS ASSUME VERSION 2.0.6 OR LATER OF THE SAMBA SUITE. SOME
>THESE TESTS ASSUME VERSION 3.0.0 OR LATER OF THE SAMBA SUITE. SOME
COMMANDS SHOWN DID NOT EXIST IN EARLIER VERSIONS</P
><P
>Please pay attention to the error messages you receive. If any error message
@ -133,17 +133,17 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN3199"
NAME="AEN3369"
></A
>23.3. Tests</H1
>26.3. Tests</H1
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN3201"
NAME="AEN3371"
></A
>23.3.1. Test 1</H2
>26.3.1. Test 1</H2
><P
>In the directory in which you store your smb.conf file, run the command
"testparm smb.conf". If it reports any errors then your smb.conf
@ -151,7 +151,7 @@ configuration file is faulty.</P
><P
>Note: Your smb.conf file may be located in: <TT
CLASS="FILENAME"
>/etc</TT
>/etc/samba</TT
>
Or in: <TT
CLASS="FILENAME"
@ -163,9 +163,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN3207"
NAME="AEN3377"
></A
>23.3.2. Test 2</H2
>26.3.2. Test 2</H2
><P
>Run the command "ping BIGSERVER" from the PC and "ping ACLIENT" from
the unix box. If you don't get a valid response then your TCP/IP
@ -189,9 +189,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN3213"
NAME="AEN3383"
></A
>23.3.3. Test 3</H2
>26.3.3. Test 3</H2
><P
>Run the command "smbclient -L BIGSERVER" on the unix box. You
should get a list of available shares back. </P
@ -260,9 +260,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN3228"
NAME="AEN3398"
></A
>23.3.4. Test 4</H2
>26.3.4. Test 4</H2
><P
>Run the command "nmblookup -B BIGSERVER __SAMBA__". You should get the
IP address of your Samba server back.</P
@ -281,9 +281,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN3233"
NAME="AEN3403"
></A
>23.3.5. Test 5</H2
>26.3.5. Test 5</H2
><P
>run the command <B
CLASS="COMMAND"
@ -302,9 +302,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN3239"
NAME="AEN3409"
></A
>23.3.6. Test 6</H2
>26.3.6. Test 6</H2
><P
>Run the command <B
CLASS="COMMAND"
@ -336,9 +336,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN3247"
NAME="AEN3417"
></A
>23.3.7. Test 7</H2
>26.3.7. Test 7</H2
><P
>Run the command <B
CLASS="COMMAND"
@ -425,9 +425,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN3273"
NAME="AEN3443"
></A
>23.3.8. Test 8</H2
>26.3.8. Test 8</H2
><P
>On the PC type the command <B
CLASS="COMMAND"
@ -485,9 +485,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN3290"
NAME="AEN3460"
></A
>23.3.9. Test 9</H2
>26.3.9. Test 9</H2
><P
>Run the command <B
CLASS="COMMAND"
@ -519,9 +519,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN3298"
NAME="AEN3468"
></A
>23.3.10. Test 10</H2
>26.3.10. Test 10</H2
><P
>Run the command <B
CLASS="COMMAND"
@ -545,9 +545,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN3304"
NAME="AEN3474"
></A
>23.3.11. Test 11</H2
>26.3.11. Test 11</H2
><P
>From file manager try to browse the server. Your samba server should
appear in the browse list of your local workgroup (or the one you
@ -573,9 +573,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN3309"
NAME="AEN3479"
></A
>23.4. Still having troubles?</H1
>26.4. Still having troubles?</H1
><P
>Try the mailing list or newsgroup, or use the ethereal utility to
sniff the problem. The official samba mailing list can be reached at
@ -611,7 +611,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="other-clients.html"
HREF="bugreport.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -635,12 +635,16 @@ VALIGN="top"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Samba and other CIFS clients</TD
>Reporting Bugs</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><A
HREF="p3106.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"

41
docs/htmldocs/domain-security.html
View File

@ -2,19 +2,22 @@
<HTML
><HEAD
><TITLE
>security = domain in Samba 2.x</TITLE
>Samba as a NT4 domain member</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="Type of installation"
HREF="p544.html"><LINK
REL="PREVIOUS"
TITLE="Security levels"
HREF="securitylevels.html"><LINK
TITLE="Samba as a ADS domain member"
HREF="ads.html"><LINK
REL="NEXT"
TITLE="Unified Logons between Windows NT and UNIX using Winbind"
HREF="winbind.html"></HEAD
TITLE="Optional configuration"
HREF="p1346.html"></HEAD
><BODY
CLASS="CHAPTER"
BGCOLOR="#FFFFFF"
@ -42,7 +45,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="securitylevels.html"
HREF="ads.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -56,7 +59,7 @@ WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="winbind.html"
HREF="p1346.html"
ACCESSKEY="N"
>Next</A
></TD
@ -71,13 +74,13 @@ CLASS="CHAPTER"
><A
NAME="DOMAIN-SECURITY"
></A
>Chapter 9. security = domain in Samba 2.x</H1
>Chapter 9. Samba as a NT4 domain member</H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN1133"
NAME="AEN1261"
></A
>9.1. Joining an NT Domain with Samba 2.2</H1
><P
@ -308,12 +311,12 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN1197"
NAME="AEN1325"
></A
>9.2. Samba and Windows 2000 Domains</H1
><P
>Many people have asked regarding the state of Samba's ability to participate in
a Windows 2000 Domain. Samba 2.2 is able to act as a member server of a Windows
a Windows 2000 Domain. Samba 3.0 is able to act as a member server of a Windows
2000 domain operating in mixed or native mode.</P
><P
>There is much confusion between the circumstances that require a "mixed" mode
@ -333,7 +336,7 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN1202"
NAME="AEN1330"
></A
>9.3. Why is this better than security = server?</H1
><P
@ -435,7 +438,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="securitylevels.html"
HREF="ads.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -453,7 +456,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="winbind.html"
HREF="p1346.html"
ACCESSKEY="N"
>Next</A
></TD
@ -463,17 +466,21 @@ ACCESSKEY="N"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Security levels</TD
>Samba as a ADS domain member</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><A
HREF="p544.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Unified Logons between Windows NT and UNIX using Winbind</TD
>Optional configuration</TD
></TR
></TABLE
></DIV

2
docs/htmldocs/findsmb.1.html
View File

@ -193,7 +193,7 @@ NAME="AEN48"
><H2
>VERSION</H2
><P
>This man page is correct for version 2.2 of
>This man page is correct for version 3.0 of
the Samba suite.</P
></DIV
><DIV

31
docs/htmldocs/groupmapping.html
View File

@ -9,12 +9,15 @@ 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="p1346.html"><LINK
REL="PREVIOUS"
TITLE="Reporting Bugs"
HREF="bugreport.html"><LINK
TITLE="HOWTO Access Samba source code via CVS"
HREF="cvs-access.html"><LINK
REL="NEXT"
TITLE="Portability"
HREF="portability.html"></HEAD
TITLE="Samba performance issues"
HREF="speed.html"></HEAD
><BODY
CLASS="CHAPTER"
BGCOLOR="#FFFFFF"
@ -42,7 +45,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="bugreport.html"
HREF="cvs-access.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -56,7 +59,7 @@ WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="portability.html"
HREF="speed.html"
ACCESSKEY="N"
>Next</A
></TD
@ -71,7 +74,7 @@ CLASS="CHAPTER"
><A
NAME="GROUPMAPPING"
></A
>Chapter 20. Group mapping HOWTO</H1
>Chapter 21. Group mapping HOWTO</H1
><P
>
Starting with Samba 3.0 alpha 2, a new group mapping function is available. The
@ -182,7 +185,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="bugreport.html"
HREF="cvs-access.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -200,7 +203,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="portability.html"
HREF="speed.html"
ACCESSKEY="N"
>Next</A
></TD
@ -210,17 +213,21 @@ ACCESSKEY="N"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Reporting Bugs</TD
>HOWTO Access Samba source code via CVS</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><A
HREF="p1346.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Portability</TD
>Samba performance issues</TD
></TR
></TABLE
></DIV

83
docs/htmldocs/improved-browsing.html
View File

@ -9,12 +9,15 @@ 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="p18.html"><LINK
REL="PREVIOUS"
TITLE="Using samba 3.0 with ActiveDirectory support"
HREF="ads.html"><LINK
TITLE="How to Install and Test SAMBA"
HREF="install.html"><LINK
REL="NEXT"
TITLE="Quick Cross Subnet Browsing / Cross Workgroup Browsing guide"
HREF="browsing-quick.html"></HEAD
TITLE="Oplocks"
HREF="oplocks.html"></HEAD
><BODY
CLASS="CHAPTER"
BGCOLOR="#FFFFFF"
@ -42,7 +45,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="ads.html"
HREF="install.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -56,7 +59,7 @@ WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="browsing-quick.html"
HREF="oplocks.html"
ACCESSKEY="N"
>Next</A
></TD
@ -71,15 +74,15 @@ CLASS="CHAPTER"
><A
NAME="IMPROVED-BROWSING"
></A
>Chapter 15. Improved browsing in samba</H1
>Chapter 2. Improved browsing in samba</H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2517"
NAME="AEN228"
></A
>15.1. Overview of browsing</H1
>2.1. Overview of browsing</H1
><P
>SMB networking provides a mechanism by which clients can access a list
of machines in a network, a so-called "browse list". This list
@ -101,9 +104,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2521"
NAME="AEN232"
></A
>15.2. Browsing support in samba</H1
>2.2. Browsing support in samba</H1
><P
>Samba now fully supports browsing. The browsing is supported by nmbd
and is also controlled by options in the smb.conf file (see smb.conf(5)).</P
@ -146,9 +149,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2530"
NAME="AEN241"
></A
>15.3. Problem resolution</H1
>2.3. Problem resolution</H1
><P
>If something doesn't work then hopefully the log.nmb file will help
you track down the problem. Try a debug level of 2 or 3 for finding
@ -180,9 +183,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2537"
NAME="AEN248"
></A
>15.4. Browsing across subnets</H1
>2.4. Browsing across subnets</H1
><P
>With the release of Samba 1.9.17(alpha1 and above) Samba has been
updated to enable it to support the replication of browse lists
@ -211,9 +214,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN2542"
NAME="AEN253"
></A
>15.4.1. How does cross subnet browsing work ?</H2
>2.4.1. How does cross subnet browsing work ?</H2
><P
>Cross subnet browsing is a complicated dance, containing multiple
moving parts. It has taken Microsoft several years to get the code
@ -423,9 +426,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2577"
NAME="AEN288"
></A
>15.5. Setting up a WINS server</H1
>2.5. Setting up a WINS server</H1
><P
>Either a Samba machine or a Windows NT Server machine may be set up
as a WINS server. To set a Samba machine to be a WINS server you must
@ -477,7 +480,7 @@ all smb.conf files :</P
><P
><B
CLASS="COMMAND"
> wins server = &gt;name or IP address&lt;</B
>wins server = &gt;name or IP address&lt;</B
></P
><P
>where &gt;name or IP address&lt; is either the DNS name of the WINS server
@ -506,9 +509,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2596"
NAME="AEN307"
></A
>15.6. Setting up Browsing in a WORKGROUP</H1
>2.6. Setting up Browsing in a WORKGROUP</H1
><P
>To set up cross subnet browsing on a network containing machines
in up to be in a WORKGROUP, not an NT Domain you need to set up one
@ -529,7 +532,7 @@ set the following option in the [global] section of the smb.conf file :</P
><P
><B
CLASS="COMMAND"
> domain master = yes</B
>domain master = yes</B
></P
><P
>The domain master browser should also preferrably be the local master
@ -590,9 +593,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2614"
NAME="AEN325"
></A
>15.7. Setting up Browsing in a DOMAIN</H1
>2.7. Setting up Browsing in a DOMAIN</H1
><P
>If you are adding Samba servers to a Windows NT Domain then
you must not set up a Samba server as a domain master browser.
@ -641,9 +644,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2624"
NAME="AEN335"
></A
>15.8. Forcing samba to be the master</H1
>2.8. Forcing samba to be the master</H1
><P
>Who becomes the "master browser" is determined by an election process
using broadcasts. Each election packet contains a number of parameters
@ -689,9 +692,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2633"
NAME="AEN344"
></A
>15.9. Making samba the domain master</H1
>2.9. Making samba the domain master</H1
><P
>The domain master is responsible for collating the browse lists of
multiple subnets so that browsing can occur between subnets. You can
@ -762,9 +765,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2651"
NAME="AEN362"
></A
>15.10. Note about broadcast addresses</H1
>2.10. Note about broadcast addresses</H1
><P
>If your network uses a "0" based broadcast address (for example if it
ends in a 0) then you will strike problems. Windows for Workgroups
@ -776,9 +779,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2654"
NAME="AEN365"
></A
>15.11. Multiple interfaces</H1
>2.11. Multiple interfaces</H1
><P
>Samba now supports machines with multiple network interfaces. If you
have multiple interfaces then you will need to use the "interfaces"
@ -801,7 +804,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="ads.html"
HREF="install.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -819,7 +822,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="browsing-quick.html"
HREF="oplocks.html"
ACCESSKEY="N"
>Next</A
></TD
@ -829,17 +832,21 @@ ACCESSKEY="N"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Using samba 3.0 with ActiveDirectory support</TD
>How to Install and Test SAMBA</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><A
HREF="p18.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Quick Cross Subnet Browsing / Cross Workgroup Browsing guide</TD
>Oplocks</TD
></TR
></TABLE
></DIV

116
docs/htmldocs/install.html
View File

@ -9,12 +9,15 @@ 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="p18.html"><LINK
REL="PREVIOUS"
TITLE="SAMBA Project Documentation"
HREF="samba-howto-collection.html"><LINK
TITLE="General installation"
HREF="p18.html"><LINK
REL="NEXT"
TITLE="Integrating MS Windows networks with Samba"
HREF="integrate-ms-networks.html"></HEAD
TITLE="Improved browsing in samba"
HREF="improved-browsing.html"></HEAD
><BODY
CLASS="CHAPTER"
BGCOLOR="#FFFFFF"
@ -42,7 +45,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="samba-howto-collection.html"
HREF="p18.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -56,7 +59,7 @@ WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="integrate-ms-networks.html"
HREF="improved-browsing.html"
ACCESSKEY="N"
>Next</A
></TD
@ -77,9 +80,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN20"
NAME="AEN25"
></A
>1.1. Step 0: Read the man pages</H1
>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.
@ -92,10 +95,20 @@ CLASS="PROMPT"
><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
></P
> on older unixes.</P
><P
>Other sources of information are pointed to
by the Samba web site,<A
@ -109,9 +122,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN28"
NAME="AEN35"
></A
>1.2. Step 1: Building the Binaries</H1
>1.2. Building the Binaries</H1
><P
>To do this, first run the program <B
CLASS="COMMAND"
@ -208,9 +221,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN56"
NAME="AEN63"
></A
>1.3. Step 2: The all important step</H1
>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
@ -225,9 +238,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN60"
NAME="AEN67"
></A
>1.4. Step 3: Create the smb configuration file.</H1
>1.4. Create the smb configuration file.</H1
><P
>There are sample configuration files in the examples
subdirectory in the distribution. I suggest you read them
@ -281,9 +294,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN74"
NAME="AEN81"
></A
>1.5. Step 4: Test your config file with
>1.5. Test your config file with
<B
CLASS="COMMAND"
>testparm</B
@ -299,15 +312,21 @@ CLASS="FILENAME"
><P
>Make sure it runs OK and that the services look
reasonable before proceeding. </P
><P
>Always run testparm again when you change
<TT
CLASS="FILENAME"
>smb.conf</TT
>!</P
></DIV
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN80"
NAME="AEN89"
></A
>1.6. Step 5: Starting the smbd and nmbd</H1
>1.6. Starting the smbd and nmbd</H1
><P
>You must choose to start smbd and nmbd either
as daemons or from <B
@ -345,9 +364,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN90"
NAME="AEN99"
></A
>1.6.1. Step 5a: Starting from inetd.conf</H2
>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
@ -449,9 +468,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN119"
NAME="AEN128"
></A
>1.6.2. Step 5b. Alternative: starting it as a daemon</H2
>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
@ -506,9 +525,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN135"
NAME="AEN144"
></A
>1.7. Step 6: Try listing the shares available on your
>1.7. Try listing the shares available on your
server</H1
><P
><TT
@ -547,9 +566,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN144"
NAME="AEN153"
></A
>1.8. Step 7: Try connecting with the unix client</H1
>1.8. Try connecting with the unix client</H1
><P
><TT
CLASS="PROMPT"
@ -610,9 +629,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN160"
NAME="AEN169"
></A
>1.9. Step 8: Try connecting from a DOS, WfWg, Win9x, WinNT,
>1.9. Try connecting from a DOS, WfWg, Win9x, WinNT,
Win2k, OS/2, etc... client</H1
><P
>Try mounting disks. eg:</P
@ -659,7 +678,7 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN174"
NAME="AEN183"
></A
>1.10. What If Things Don't Work?</H1
><P
@ -682,15 +701,16 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN179"
NAME="AEN188"
></A
>1.10.1. Diagnosing Problems</H2
><P
>If you have installation problems then go to
<TT
CLASS="FILENAME"
>DIAGNOSIS.txt</TT
> to try to find the
>If you have installation problems then go to the
<A
HREF="Diagnosis.html"
TARGET="_top"
>Diagnosis</A
> chapter to try to find the
problem.</P
></DIV
><DIV
@ -698,7 +718,7 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN183"
NAME="AEN192"
></A
>1.10.2. Scope IDs</H2
><P
@ -714,7 +734,7 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN186"
NAME="AEN195"
></A
>1.10.3. Choosing the Protocol Level</H2
><P
@ -755,7 +775,7 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN195"
NAME="AEN204"
></A
>1.10.4. Printing from UNIX to a Client PC</H2
><P
@ -776,7 +796,7 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN200"
NAME="AEN209"
></A
>1.10.5. Locking</H2
><P
@ -836,7 +856,7 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN209"
NAME="AEN218"
></A
>1.10.6. Mapping Usernames</H2
><P
@ -862,7 +882,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="samba-howto-collection.html"
HREF="p18.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -880,7 +900,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="integrate-ms-networks.html"
HREF="improved-browsing.html"
ACCESSKEY="N"
>Next</A
></TD
@ -890,17 +910,21 @@ ACCESSKEY="N"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>SAMBA Project Documentation</TD
>General installation</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><A
HREF="p18.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Integrating MS Windows networks with Samba</TD
>Improved browsing in samba</TD
></TR
></TABLE
></DIV

115
docs/htmldocs/integrate-ms-networks.html
View File

@ -9,13 +9,15 @@ 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="p1346.html"><LINK
REL="PREVIOUS"
TITLE="How to Install and Test SAMBA"
HREF="install.html"><LINK
TITLE="Optional configuration"
HREF="p1346.html"><LINK
REL="NEXT"
TITLE="Configuring PAM for distributed but centrally
managed authentication"
HREF="pam.html"></HEAD
TITLE="UNIX Permission Bits and Windows NT Access Control Lists"
HREF="unix-permissions.html"></HEAD
><BODY
CLASS="CHAPTER"
BGCOLOR="#FFFFFF"
@ -43,7 +45,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="install.html"
HREF="p1346.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -57,7 +59,7 @@ WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="pam.html"
HREF="unix-permissions.html"
ACCESSKEY="N"
>Next</A
></TD
@ -72,15 +74,15 @@ CLASS="CHAPTER"
><A
NAME="INTEGRATE-MS-NETWORKS"
></A
>Chapter 2. Integrating MS Windows networks with Samba</H1
>Chapter 10. Integrating MS Windows networks with Samba</H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN223"
NAME="AEN1362"
></A
>2.1. Agenda</H1
>10.1. Agenda</H1
><P
>To identify the key functional mechanisms of MS Windows networking
to enable the deployment of Samba as a means of extending and/or
@ -145,9 +147,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN245"
NAME="AEN1384"
></A
>2.2. Name Resolution in a pure Unix/Linux world</H1
>10.2. Name Resolution in a pure Unix/Linux world</H1
><P
>The key configuration files covered in this section are:</P
><P
@ -187,9 +189,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN261"
NAME="AEN1400"
></A
>2.2.1. <TT
>10.2.1. <TT
CLASS="FILENAME"
>/etc/hosts</TT
></H2
@ -268,9 +270,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN277"
NAME="AEN1416"
></A
>2.2.2. <TT
>10.2.2. <TT
CLASS="FILENAME"
>/etc/resolv.conf</TT
></H2
@ -306,9 +308,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN288"
NAME="AEN1427"
></A
>2.2.3. <TT
>10.2.3. <TT
CLASS="FILENAME"
>/etc/host.conf</TT
></H2
@ -335,9 +337,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN296"
NAME="AEN1435"
></A
>2.2.4. <TT
>10.2.4. <TT
CLASS="FILENAME"
>/etc/nsswitch.conf</TT
></H2
@ -376,7 +378,7 @@ facilities and/or services are correctly configured.</P
sent, TCP/IP networks are silent. All TCP/IP communications assumes a
principal of speaking only when necessary.</P
><P
>Samba version 2.2.0 will add Linux support for extensions to
>Starting with version 2.2.0 samba has Linux support for extensions to
the name service switch infrastructure so that linux clients will
be able to obtain resolution of MS Windows NetBIOS names to IP
Addresses. To gain this functionality Samba needs to be compiled
@ -404,9 +406,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN308"
NAME="AEN1447"
></A
>2.3. Name resolution as used within MS Windows networking</H1
>10.3. Name resolution as used within MS Windows networking</H1
><P
>MS Windows networking is predicated about the name each machine
is given. This name is known variously (and inconsistently) as
@ -489,9 +491,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN320"
NAME="AEN1459"
></A
>2.3.1. The NetBIOS Name Cache</H2
>10.3.1. The NetBIOS Name Cache</H2
><P
>All MS Windows machines employ an in memory buffer in which is
stored the NetBIOS names and IP addresses for all external
@ -516,9 +518,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN325"
NAME="AEN1464"
></A
>2.3.2. The LMHOSTS file</H2
>10.3.2. The LMHOSTS file</H2
><P
>This file is usually located in MS Windows NT 4.0 or
2000 in <TT
@ -619,9 +621,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN333"
NAME="AEN1472"
></A
>2.3.3. HOSTS file</H2
>10.3.3. HOSTS file</H2
><P
>This file is usually located in MS Windows NT 4.0 or 2000 in
<TT
@ -641,9 +643,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN338"
NAME="AEN1477"
></A
>2.3.4. DNS Lookup</H2
>10.3.4. DNS Lookup</H2
><P
>This capability is configured in the TCP/IP setup area in the network
configuration facility. If enabled an elaborate name resolution sequence
@ -661,9 +663,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN341"
NAME="AEN1480"
></A
>2.3.5. WINS Lookup</H2
>10.3.5. WINS Lookup</H2
><P
>A WINS (Windows Internet Name Server) service is the equivaent of the
rfc1001/1002 specified NBNS (NetBIOS Name Server). A WINS server stores
@ -704,9 +706,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN353"
NAME="AEN1492"
></A
>2.4. How browsing functions and how to deploy stable and
>10.4. How browsing functions and how to deploy stable and
dependable browsing using Samba</H1
><P
>As stated above, MS Windows machines register their NetBIOS names
@ -771,9 +773,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN363"
NAME="AEN1502"
></A
>2.5. MS Windows security options and how to configure
>10.5. MS Windows security options and how to configure
Samba for seemless integration</H1
><P
>MS Windows clients may use encrypted passwords as part of a
@ -908,9 +910,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN391"
NAME="AEN1530"
></A
>2.5.1. Use MS Windows NT as an authentication server</H2
>10.5.1. Use MS Windows NT as an authentication server</H2
><P
>This method involves the additions of the following parameters
in the smb.conf file:</P
@ -944,9 +946,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN399"
NAME="AEN1538"
></A
>2.5.2. Make Samba a member of an MS Windows NT security domain</H2
>10.5.2. Make Samba a member of an MS Windows NT security domain</H2
><P
>This method involves additon of the following paramters in the smb.conf file:</P
><P
@ -1007,9 +1009,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN416"
NAME="AEN1555"
></A
>2.5.3. Configure Samba as an authentication server</H2
>10.5.3. Configure Samba as an authentication server</H2
><P
>This mode of authentication demands that there be on the
Unix/Linux system both a Unix style account as well as an
@ -1044,9 +1046,9 @@ CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="AEN423"
NAME="AEN1562"
></A
>2.5.3.1. Users</H3
>10.5.3.1. Users</H3
><P
>A user account that may provide a home directory should be
created. The following Linux system commands are typical of
@ -1067,9 +1069,9 @@ CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="AEN428"
NAME="AEN1567"
></A
>2.5.3.2. MS Windows NT Machine Accounts</H3
>10.5.3.2. MS Windows NT Machine Accounts</H3
><P
>These are required only when Samba is used as a domain
controller. Refer to the Samba-PDC-HOWTO for more details.</P
@ -1088,9 +1090,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN433"
NAME="AEN1572"
></A
>2.6. Conclusions</H1
>10.6. Conclusions</H1
><P
>Samba provides a flexible means to operate as...</P
><P
@ -1136,7 +1138,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="install.html"
HREF="p1346.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -1154,7 +1156,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="pam.html"
HREF="unix-permissions.html"
ACCESSKEY="N"
>Next</A
></TD
@ -1164,18 +1166,21 @@ ACCESSKEY="N"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>How to Install and Test SAMBA</TD
>Optional configuration</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><A
HREF="p1346.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Configuring PAM for distributed but centrally
managed authentication</TD
>UNIX Permission Bits and Windows NT Access Control Lists</TD
></TR
></TABLE
></DIV

29
docs/htmldocs/msdfs.html
View File

@ -9,13 +9,16 @@ 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="p1346.html"><LINK
REL="PREVIOUS"
TITLE="Configuring PAM for distributed but centrally
managed authentication"
HREF="pam.html"><LINK
REL="NEXT"
TITLE="UNIX Permission Bits and Windows NT Access Control Lists"
HREF="unix-permissions.html"></HEAD
TITLE="Printing Support"
HREF="printing.html"></HEAD
><BODY
CLASS="CHAPTER"
BGCOLOR="#FFFFFF"
@ -57,7 +60,7 @@ WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="unix-permissions.html"
HREF="printing.html"
ACCESSKEY="N"
>Next</A
></TD
@ -72,15 +75,15 @@ CLASS="CHAPTER"
><A
NAME="MSDFS"
></A
>Chapter 4. Hosting a Microsoft Distributed File System tree on Samba</H1
>Chapter 13. Hosting a Microsoft Distributed File System tree on Samba</H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN525"
NAME="AEN1847"
></A
>4.1. Instructions</H1
>13.1. Instructions</H1
><P
>The Distributed File System (or Dfs) provides a means of
separating the logical view of files and directories that users
@ -226,9 +229,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN560"
NAME="AEN1882"
></A
>4.1.1. Notes</H2
>13.1.1. Notes</H2
><P
></P
><UL
@ -289,7 +292,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="unix-permissions.html"
HREF="printing.html"
ACCESSKEY="N"
>Next</A
></TD
@ -305,12 +308,16 @@ managed authentication</TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><A
HREF="p1346.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>UNIX Permission Bits and Windows NT Access Control Lists</TD
>Printing Support</TD
></TR
></TABLE
></DIV

20
docs/htmldocs/nmbd.8.html
View File

@ -38,12 +38,12 @@ NAME="AEN8"
><B
CLASS="COMMAND"
>nmbd</B
> [-D] [-a] [-i] [-o] [-P] [-h] [-V] [-d &lt;debug level&gt;] [-H &lt;lmhosts file&gt;] [-l &lt;log directory&gt;] [-n &lt;primary netbios name&gt;] [-p &lt;port number&gt;] [-s &lt;configuration file&gt;]</P
> [-D] [-a] [-i] [-o] [-h] [-V] [-d &lt;debug level&gt;] [-H &lt;lmhosts file&gt;] [-l &lt;log directory&gt;] [-n &lt;primary netbios name&gt;] [-p &lt;port number&gt;] [-s &lt;configuration file&gt;]</P
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN24"
NAME="AEN23"
></A
><H2
>DESCRIPTION</H2
@ -56,7 +56,7 @@ CLASS="COMMAND"
> is a server that understands
and can reply to NetBIOS over IP name service requests, like
those produced by SMB/CIFS clients such as Windows 95/98/ME,
Windows NT, Windows 2000, and LanManager clients. It also
Windows NT, Windows 2000, Windows XP and LanManager clients. It also
participates in the browsing protocols which make up the
Windows "Network Neighborhood" view.</P
><P
@ -117,7 +117,7 @@ CLASS="COMMAND"
><DIV
CLASS="REFSECT1"
><A
NAME="AEN41"
NAME="AEN40"
></A
><H2
>OPTIONS</H2
@ -400,7 +400,7 @@ CLASS="FILENAME"
><DIV
CLASS="REFSECT1"
><A
NAME="AEN131"
NAME="AEN130"
></A
><H2
>FILES</H2
@ -559,7 +559,7 @@ CLASS="FILENAME"
><DIV
CLASS="REFSECT1"
><A
NAME="AEN178"
NAME="AEN177"
></A
><H2
>SIGNALS</H2
@ -624,18 +624,18 @@ CLASS="COMMAND"
><DIV
CLASS="REFSECT1"
><A
NAME="AEN194"
NAME="AEN193"
></A
><H2
>VERSION</H2
><P
>This man page is correct for version 2.2 of
>This man page is correct for version 3.0 of
the Samba suite.</P
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN197"
NAME="AEN196"
></A
><H2
>SEE ALSO</H2
@ -700,7 +700,7 @@ TARGET="_top"
><DIV
CLASS="REFSECT1"
><A
NAME="AEN214"
NAME="AEN213"
></A
><H2
>AUTHOR</H2

25
docs/htmldocs/nmblookup.1.html
View File

@ -38,12 +38,12 @@ NAME="AEN8"
><B
CLASS="COMMAND"
>nmblookup</B
> [-M] [-R] [-S] [-r] [-A] [-h] [-B &lt;broadcast address&gt;] [-U &lt;unicast address&gt;] [-d &lt;debug level&gt;] [-s &lt;smb config file&gt;] [-i &lt;NetBIOS scope&gt;] [-T] {name}</P
> [-M] [-R] [-S] [-r] [-A] [-h] [-B &lt;broadcast address&gt;] [-U &lt;unicast address&gt;] [-d &lt;debug level&gt;] [-s &lt;smb config file&gt;] [-i &lt;NetBIOS scope&gt;] [-T] [-f] {name}</P
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN24"
NAME="AEN25"
></A
><H2
>DESCRIPTION</H2
@ -66,7 +66,7 @@ CLASS="COMMAND"
><DIV
CLASS="REFSECT1"
><A
NAME="AEN30"
NAME="AEN31"
></A
><H2
>OPTIONS</H2
@ -286,6 +286,15 @@ CLASS="EMPHASIS"
> pair that is the normal output.</P
></DD
><DT
>-f</DT
><DD
><P
> Show which flags apply to the name that has been looked up. Possible
answers are zero or more of: Response, Authoritative,
Truncated, Recursion_Desired, Recursion_Available, Broadcast.
</P
></DD
><DT
>name</DT
><DD
><P
@ -302,7 +311,7 @@ CLASS="EMPHASIS"
><DIV
CLASS="REFSECT1"
><A
NAME="AEN110"
NAME="AEN115"
></A
><H2
>EXAMPLES</H2
@ -339,18 +348,18 @@ CLASS="COMMAND"
><DIV
CLASS="REFSECT1"
><A
NAME="AEN122"
NAME="AEN127"
></A
><H2
>VERSION</H2
><P
>This man page is correct for version 2.2 of
>This man page is correct for version 3.0 of
the Samba suite.</P
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN125"
NAME="AEN130"
></A
><H2
>SEE ALSO</H2
@ -377,7 +386,7 @@ TARGET="_top"
><DIV
CLASS="REFSECT1"
><A
NAME="AEN132"
NAME="AEN137"
></A
><H2
>AUTHOR</H2

73
docs/htmldocs/other-clients.html
View File

@ -9,12 +9,15 @@ CONTENT="Modular DocBook HTML Stylesheet Version 1.77"><LINK
REL="HOME"
TITLE="SAMBA Project Documentation"
HREF="samba-howto-collection.html"><LINK
REL="UP"
TITLE="Appendixes"
HREF="p3106.html"><LINK
REL="PREVIOUS"
TITLE="Portability"
HREF="portability.html"><LINK
REL="NEXT"
TITLE="Diagnosing your samba server"
HREF="diagnosis.html"></HEAD
TITLE="Reporting Bugs"
HREF="bugreport.html"></HEAD
><BODY
CLASS="CHAPTER"
BGCOLOR="#FFFFFF"
@ -56,7 +59,7 @@ WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="diagnosis.html"
HREF="bugreport.html"
ACCESSKEY="N"
>Next</A
></TD
@ -71,7 +74,7 @@ CLASS="CHAPTER"
><A
NAME="OTHER-CLIENTS"
></A
>Chapter 22. Samba and other CIFS clients</H1
>Chapter 24. Samba and other CIFS clients</H1
><P
>This chapter contains client-specific information.</P
><DIV
@ -79,9 +82,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN3070"
NAME="AEN3175"
></A
>22.1. Macintosh clients?</H1
>24.1. Macintosh clients?</H1
><P
>Yes. <A
HREF="http://www.thursby.com/"
@ -125,17 +128,17 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN3079"
NAME="AEN3184"
></A
>22.2. OS2 Client</H1
>24.2. OS2 Client</H1
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN3081"
NAME="AEN3186"
></A
>22.2.1. How can I configure OS/2 Warp Connect or
>24.2.1. How can I configure OS/2 Warp Connect or
OS/2 Warp 4 as a client for Samba?</H2
><P
>A more complete answer to this question can be
@ -192,9 +195,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN3096"
NAME="AEN3201"
></A
>22.2.2. How can I configure OS/2 Warp 3 (not Connect),
>24.2.2. How can I configure OS/2 Warp 3 (not Connect),
OS/2 1.2, 1.3 or 2.x for Samba?</H2
><P
>You can use the free Microsoft LAN Manager 2.2c Client
@ -236,9 +239,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN3105"
NAME="AEN3210"
></A
>22.2.3. Are there any other issues when OS/2 (any version)
>24.2.3. Are there any other issues when OS/2 (any version)
is used as a client?</H2
><P
>When you do a NET VIEW or use the "File and Print
@ -258,9 +261,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN3109"
NAME="AEN3214"
></A
>22.2.4. How do I get printer driver download working
>24.2.4. How do I get printer driver download working
for OS/2 clients?</H2
><P
>First, create a share called [PRINTDRV] that is
@ -309,17 +312,17 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN3119"
NAME="AEN3224"
></A
>22.3. Windows for Workgroups</H1
>24.3. Windows for Workgroups</H1
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN3121"
NAME="AEN3226"
></A
>22.3.1. Use latest TCP/IP stack from Microsoft</H2
>24.3.1. Use latest TCP/IP stack from Microsoft</H2
><P
>Use the latest TCP/IP stack from microsoft if you use Windows
for workgroups.</P
@ -339,9 +342,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN3126"
NAME="AEN3231"
></A
>22.3.2. Delete .pwl files after password change</H2
>24.3.2. Delete .pwl files after password change</H2
><P
>WfWg does a lousy job with passwords. I find that if I change my
password on either the unix box or the PC the safest thing to do is to
@ -359,9 +362,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN3131"
NAME="AEN3236"
></A
>22.3.3. Configure WfW password handling</H2
>24.3.3. Configure WfW password handling</H2
><P
>There is a program call admincfg.exe
on the last disk (disk 8) of the WFW 3.11 disk set. To install it
@ -378,9 +381,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN3135"
NAME="AEN3240"
></A
>22.3.4. Case handling of passwords</H2
>24.3.4. Case handling of passwords</H2
><P
>Windows for Workgroups uppercases the password before sending it to the server. Unix passwords can be case-sensitive though. Check the <A
HREF="smb.conf.5.html"
@ -397,9 +400,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN3140"
NAME="AEN3245"
></A
>22.4. Windows '95/'98</H1
>24.4. Windows '95/'98</H1
><P
>When using Windows 95 OEM SR2 the following updates are recommended where Samba
is being used. Please NOTE that the above change will affect you once these
@ -445,9 +448,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN3156"
NAME="AEN3261"
></A
>22.5. Windows 2000 Service Pack 2</H1
>24.5. Windows 2000 Service Pack 2</H1
><P
>
There are several annoyances with Windows 2000 SP2. One of which
@ -557,7 +560,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="diagnosis.html"
HREF="bugreport.html"
ACCESSKEY="N"
>Next</A
></TD
@ -572,12 +575,16 @@ VALIGN="top"
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><A
HREF="p3106.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Diagnosing your samba server</TD
>Reporting Bugs</TD
></TR
></TABLE
></DIV

33
docs/htmldocs/pam.html
View File

@ -10,9 +10,12 @@ 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="p1346.html"><LINK
REL="PREVIOUS"
TITLE="Integrating MS Windows networks with Samba"
HREF="integrate-ms-networks.html"><LINK
TITLE="UNIX Permission Bits and Windows NT Access Control Lists"
HREF="unix-permissions.html"><LINK
REL="NEXT"
TITLE="Hosting a Microsoft Distributed File System tree on Samba"
HREF="msdfs.html"></HEAD
@ -43,7 +46,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="integrate-ms-networks.html"
HREF="unix-permissions.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -72,16 +75,16 @@ CLASS="CHAPTER"
><A
NAME="PAM"
></A
>Chapter 3. Configuring PAM for distributed but centrally
>Chapter 12. Configuring PAM for distributed but centrally
managed authentication</H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN454"
NAME="AEN1776"
></A
>3.1. Samba and PAM</H1
>12.1. Samba and PAM</H1
><P
>A number of Unix systems (eg: Sun Solaris), as well as the
xxxxBSD family and Linux, now utilize the Pluggable Authentication
@ -293,9 +296,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN498"
NAME="AEN1820"
></A
>3.2. Distributed Authentication</H1
>12.2. Distributed Authentication</H1
><P
>The astute administrator will realize from this that the
combination of <TT
@ -326,9 +329,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN505"
NAME="AEN1827"
></A
>3.3. PAM Configuration in smb.conf</H1
>12.3. PAM Configuration in smb.conf</H1
><P
>There is an option in smb.conf called <A
HREF="smb.conf.5.html#OBEYPAMRESTRICTIONS"
@ -378,7 +381,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="integrate-ms-networks.html"
HREF="unix-permissions.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -406,12 +409,16 @@ ACCESSKEY="N"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Integrating MS Windows networks with Samba</TD
>UNIX Permission Bits and Windows NT Access Control Lists</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><A
HREF="p1346.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"

135
docs/htmldocs/pdbedit.8.html
View File

@ -37,12 +37,12 @@ NAME="AEN8"
><B
CLASS="COMMAND"
>pdbedit</B
> [-l] [-v] [-w] [-u username] [-f fullname] [-h homedir] [-d drive] [-s script] [-p profile] [-a] [-m] [-x] [-i passdb-backend] [-e passdb-backend] [-b passdb-backend] [-D debuglevel]</P
> [-l] [-v] [-w] [-u username] [-f fullname] [-h homedir] [-D drive] [-S script] [-p profile] [-a] [-m] [-x] [-i passdb-backend] [-e passdb-backend] [-b passdb-backend] [-d debuglevel] [-s configfile] [-P account-policy] [-V value]</P
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN27"
NAME="AEN30"
></A
><H2
>DESCRIPTION</H2
@ -68,7 +68,7 @@ TARGET="_top"
><DIV
CLASS="REFSECT1"
><A
NAME="AEN34"
NAME="AEN37"
></A
><H2
>OPTIONS</H2
@ -215,7 +215,7 @@ CLASS="COMMAND"
</P
></DD
><DT
>-d drive</DT
>-D drive</DT
><DD
><P
>This option can be used while adding or
@ -229,7 +229,7 @@ CLASS="COMMAND"
</P
></DD
><DT
>-s script</DT
>-S script</DT
><DD
><P
>This option can be used while adding or
@ -352,13 +352,130 @@ CLASS="COMMAND"
>pdbedit -b xml:/root/pdb-backup.xml -l</B
></P
></DD
><DT
>-P account-policy</DT
><DD
><P
>Display an account policy</P
><P
>Valid policies are: minimum password age, reset count minutes, disconnect time,
user must logon to change password, password history, lockout duration, min password length,
maximum password age and bad lockout attempt.
</P
><P
>Example: <B
CLASS="COMMAND"
>pdbedit -P "bad lockout attempt"</B
></P
><P
><PRE
CLASS="PROGRAMLISTING"
> account policy value for bad lockout attempt is 0
</PRE
></P
></DD
><DT
>-V account-policy-value</DT
><DD
><P
>Sets an account policy to a specified value.
This option may only be used in conjunction
with the <TT
CLASS="PARAMETER"
><I
>-P</I
></TT
> option.
</P
><P
>Example: <B
CLASS="COMMAND"
>pdbedit -P "bad lockout attempt" -V 3</B
></P
><P
><PRE
CLASS="PROGRAMLISTING"
> account policy value for bad lockout attempt was 0
account policy value for bad lockout attempt is now 3
</PRE
></P
></DD
><DT
>-d|--debug=debuglevel</DT
><DD
><P
><TT
CLASS="REPLACEABLE"
><I
>debuglevel</I
></TT
> is an integer
from 0 to 10. The default value if this parameter is
not specified is zero.</P
><P
>The higher this value, the more detail will be
logged to the log files about the activities of the
server. At level 0, only critical errors and serious
warnings will be logged. Level 1 is a reasonable level for
day to day running - it generates a small amount of
information about operations carried out.</P
><P
>Levels above 1 will generate considerable
amounts of log data, and should only be used when
investigating a problem. Levels above 3 are designed for
use only by developers and generate HUGE amounts of log
data, most of which is extremely cryptic.</P
><P
>Note that specifying this parameter here will
override the <A
HREF="smb.conf.5.html#loglevel"
TARGET="_top"
>log
level</A
> parameter in the <A
HREF="smb.conf.5.html"
TARGET="_top"
><TT
CLASS="FILENAME"
>smb.conf(5)</TT
></A
> file.</P
></DD
><DT
>-h|--help</DT
><DD
><P
>Print a summary of command line options.</P
></DD
><DT
>-s &lt;configuration file&gt;</DT
><DD
><P
>The file specified contains the
configuration details required by the server. The
information in this file includes server-specific
information such as what printcap file to use, as well
as descriptions of all the services that the server is
to provide. See <A
HREF="smb.conf.5.html"
TARGET="_top"
><TT
CLASS="FILENAME"
>smb.conf(5)</TT
></A
> for more information.
The default configuration file name is determined at
compile time.</P
></DD
></DL
></DIV
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN140"
NAME="AEN182"
></A
><H2
>NOTES</H2
@ -368,7 +485,7 @@ NAME="AEN140"
><DIV
CLASS="REFSECT1"
><A
NAME="AEN143"
NAME="AEN185"
></A
><H2
>VERSION</H2
@ -379,7 +496,7 @@ NAME="AEN143"
><DIV
CLASS="REFSECT1"
><A
NAME="AEN146"
NAME="AEN188"
></A
><H2
>SEE ALSO</H2
@ -399,7 +516,7 @@ TARGET="_top"
><DIV
CLASS="REFSECT1"
><A
NAME="AEN151"
NAME="AEN193"
></A
><H2
>AUTHOR</H2

41
docs/htmldocs/portability.html
View File

@ -9,9 +9,12 @@ CONTENT="Modular DocBook HTML Stylesheet Version 1.77"><LINK
REL="HOME"
TITLE="SAMBA Project Documentation"
HREF="samba-howto-collection.html"><LINK
REL="UP"
TITLE="Appendixes"
HREF="p3106.html"><LINK
REL="PREVIOUS"
TITLE="Group mapping HOWTO"
HREF="groupmapping.html"><LINK
TITLE="Appendixes"
HREF="p3106.html"><LINK
REL="NEXT"
TITLE="Samba and other CIFS clients"
HREF="other-clients.html"></HEAD
@ -42,7 +45,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="groupmapping.html"
HREF="p3106.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -71,7 +74,7 @@ CLASS="CHAPTER"
><A
NAME="PORTABILITY"
></A
>Chapter 21. Portability</H1
>Chapter 23. Portability</H1
><P
>Samba works on a wide range of platforms but the interface all the
platforms provide is not always compatible. This chapter contains
@ -81,9 +84,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN3011"
NAME="AEN3115"
></A
>21.1. HPUX</H1
>23.1. HPUX</H1
><P
>HP's implementation of supplementary groups is, er, non-standard (for
hysterical reasons). There are two group files, /etc/group and
@ -101,15 +104,19 @@ to initgroups() be run as users not in any groups with GIDs outside the
allowed range.</P
><P
>This is documented in the HP manual pages under setgroups(2) and passwd(4).</P
><P
>On HPUX you must use gcc or the HP Ansi compiler. The free compiler
that comes with HP-UX is not Ansi compliant and cannot compile
Samba.</P
></DIV
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN3016"
NAME="AEN3121"
></A
>21.2. SCO Unix</H1
>23.2. SCO Unix</H1
><P
>
If you run an old version of SCO Unix then you may need to get important
@ -124,9 +131,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN3020"
NAME="AEN3125"
></A
>21.3. DNIX</H1
>23.3. DNIX</H1
><P
>DNIX has a problem with seteuid() and setegid(). These routines are
needed for Samba to work correctly, but they were left out of the DNIX
@ -231,9 +238,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN3049"
NAME="AEN3154"
></A
>21.4. RedHat Linux Rembrandt-II</H1
>23.4. RedHat Linux Rembrandt-II</H1
><P
>By default RedHat Rembrandt-II during installation adds an
entry to /etc/hosts as follows:
@ -267,7 +274,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="groupmapping.html"
HREF="p3106.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -295,12 +302,16 @@ ACCESSKEY="N"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Group mapping HOWTO</TD
>Appendixes</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><A
HREF="p3106.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"

634
docs/htmldocs/printing.html
View File

@ -2,19 +2,22 @@
<HTML
><HEAD
><TITLE
>Printing Support in Samba 2.2.x</TITLE
>Printing Support</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="p1346.html"><LINK
REL="PREVIOUS"
TITLE="UNIX Permission Bits and Windows NT Access Control Lists"
HREF="unix-permissions.html"><LINK
TITLE="Hosting a Microsoft Distributed File System tree on Samba"
HREF="msdfs.html"><LINK
REL="NEXT"
TITLE="Debugging Printing Problems"
HREF="printingdebug.html"></HEAD
TITLE="Security levels"
HREF="securitylevels.html"></HEAD
><BODY
CLASS="CHAPTER"
BGCOLOR="#FFFFFF"
@ -42,7 +45,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="unix-permissions.html"
HREF="msdfs.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -56,7 +59,7 @@ WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="printingdebug.html"
HREF="securitylevels.html"
ACCESSKEY="N"
>Next</A
></TD
@ -71,15 +74,15 @@ CLASS="CHAPTER"
><A
NAME="PRINTING"
></A
>Chapter 6. Printing Support in Samba 2.2.x</H1
>Chapter 14. Printing Support</H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN763"
NAME="AEN1908"
></A
>6.1. Introduction</H1
>14.1. Introduction</H1
><P
>Beginning with the 2.2.0 release, Samba supports
the native Windows NT printing mechanisms implemented via
@ -136,12 +139,7 @@ TARGET="_top"
>There has been some initial confusion about what all this means
and whether or not it is a requirement for printer drivers to be
installed on a Samba host in order to support printing from Windows
clients. A bug existed in Samba 2.2.0 which made Windows NT/2000 clients
require that the Samba server possess a valid driver for the printer.
This is fixed in Samba 2.2.1 and once again, Windows NT/2000 clients
can use the local APW for installing drivers to be used with a Samba
served printer. This is the same behavior exhibited by Windows 9x clients.
As a side note, Samba does not use these drivers in any way to process
clients. As a side note, Samba does not use these drivers in any way to process
spooled files. They are utilized entirely by the clients.</P
><P
>The following MS KB article, may be of some help if you are dealing with
@ -165,9 +163,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN785"
NAME="AEN1930"
></A
>6.2. Configuration</H1
>14.2. Configuration</H1
><DIV
CLASS="WARNING"
><P
@ -222,20 +220,6 @@ CLASS="PARAMETER"
> provided
a means of defining the printer driver name to be sent to
the client.</P
><P
>These parameters, including <TT
CLASS="PARAMETER"
><I
>printer driver
file</I
></TT
> parameter, are being deprecated and should not
be used in new installations. For more information on this change,
you should refer to the <A
HREF="printing.html#MIGRATION"
>Migration section</A
>
of this document.</P
></TD
></TR
></TABLE
@ -245,9 +229,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN796"
NAME="AEN1938"
></A
>6.2.1. Creating [print$]</H2
>14.2.1. Creating [print$]</H2
><P
>In order to support the uploading of printer driver
files, you must first configure a file share named [print$].
@ -468,22 +452,14 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN831"
NAME="AEN1973"
></A
>6.2.2. Setting Drivers for Existing Printers</H2
>14.2.2. Setting Drivers for Existing Printers</H2
><P
>The initial listing of printers in the Samba host's
Printers folder will have no real printer driver assigned
to them. By default, in Samba 2.2.0 this driver name was set to
<SPAN
CLASS="emphasis"
><I
CLASS="EMPHASIS"
>NO PRINTER DRIVER AVAILABLE FOR THIS PRINTER</I
></SPAN
>.
Later versions changed this to a NULL string to allow the use
tof the local Add Printer Wizard on NT/2000 clients.
to them. This defaults to a NULL string to allow the use
of the local Add Printer Wizard on NT/2000 clients.
Attempting to view the printer properties for a printer
which has this default driver assigned will result in
the error message:</P
@ -548,9 +524,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN848"
NAME="AEN1989"
></A
>6.2.3. Support a large number of printers</H2
>14.2.3. Support a large number of printers</H2
><P
>One issue that has arisen during the development
phase of Samba 2.2 is the need to support driver downloads for
@ -614,9 +590,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN859"
NAME="AEN2000"
></A
>6.2.4. Adding New Printers via the Windows NT APW</H2
>14.2.4. Adding New Printers via the Windows NT APW</H2
><P
>By default, Samba offers all printer shares defined in <TT
CLASS="FILENAME"
@ -783,9 +759,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN889"
NAME="AEN2030"
></A
>6.2.5. Samba and Printer Ports</H2
>14.2.5. Samba and Printer Ports</H2
><P
>Windows NT/2000 print servers associate a port with each printer. These normally
take the form of LPT1:, COM1:, FILE:, etc... Samba must also support the
@ -820,9 +796,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN897"
NAME="AEN2038"
></A
>6.3. The Imprints Toolset</H1
>14.3. The Imprints Toolset</H1
><P
>The Imprints tool set provides a UNIX equivalent of the
Windows NT Add Printer Wizard. For complete information, please
@ -838,9 +814,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN901"
NAME="AEN2042"
></A
>6.3.1. What is Imprints?</H2
>14.3.1. What is Imprints?</H2
><P
>Imprints is a collection of tools for supporting the goals
of</P
@ -870,9 +846,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN911"
NAME="AEN2052"
></A
>6.3.2. Creating Printer Driver Packages</H2
>14.3.2. Creating Printer Driver Packages</H2
><P
>The process of creating printer driver packages is beyond
the scope of this document (refer to Imprints.txt also included
@ -886,9 +862,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN914"
NAME="AEN2055"
></A
>6.3.3. The Imprints server</H2
>14.3.3. The Imprints server</H2
><P
>The Imprints server is really a database server that
may be queried via standard HTTP mechanisms. Each printer
@ -910,9 +886,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN918"
NAME="AEN2059"
></A
>6.3.4. The Installation Client</H2
>14.3.4. The Installation Client</H2
><P
>More information regarding the Imprints installation client
is available in the <TT
@ -1004,168 +980,388 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN940"
NAME="AEN2081"
></A
>6.4. <A
NAME="MIGRATION"
></A
>Migration to from Samba 2.0.x to 2.2.x</H1
><P
>Given that printer driver management has changed (we hope improved) in
2.2 over prior releases, migration from an existing setup to 2.2 can
follow several paths. Here are the possible scenarios for
migration:</P
><P
></P
><UL
><LI
><P
>If you do not desire the new Windows NT
print driver support, nothing needs to be done.
All existing parameters work the same.</P
></LI
><LI
><P
>If you want to take advantage of NT printer
driver support but do not want to migrate the
9x drivers to the new setup, the leave the existing
<TT
CLASS="FILENAME"
>printers.def</TT
> file. When smbd attempts
to locate a
9x driver for the printer in the TDB and fails it
will drop down to using the printers.def (and all
associated parameters). The <B
CLASS="COMMAND"
>make_printerdef</B
>
tool will also remain for backwards compatibility but will
be removed in the next major release.</P
></LI
><LI
><P
>If you install a Windows 9x driver for a printer
on your Samba host (in the printing TDB), this information will
take precedence and the three old printing parameters
will be ignored (including print driver location).</P
></LI
><LI
><P
>If you want to migrate an existing <TT
CLASS="FILENAME"
>printers.def</TT
>
file into the new setup, the current only solution is to use the Windows
NT APW to install the NT drivers and the 9x drivers. This can be scripted
using <B
CLASS="COMMAND"
>smbclient</B
> and <B
CLASS="COMMAND"
>rpcclient</B
>. See the
Imprints installation client at <A
HREF="http://imprints.sourceforge.net/"
TARGET="_top"
>http://imprints.sourceforge.net/</A
>
for an example.
</P
></LI
></UL
>14.4. Diagnosis</H1
><DIV
CLASS="WARNING"
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN2083"
></A
>14.4.1. Introduction</H2
><P
>This is a short description of how to debug printing problems with
Samba. This describes how to debug problems with printing from a SMB
client to a Samba server, not the other way around. For the reverse
see the examples/printing directory.</P
><P
>Ok, so you want to print to a Samba server from your PC. The first
thing you need to understand is that Samba does not actually do any
printing itself, it just acts as a middleman between your PC client
and your Unix printing subsystem. Samba receives the file from the PC
then passes the file to a external "print command". What print command
you use is up to you.</P
><P
>The whole things is controlled using options in smb.conf. The most
relevant options (which you should look up in the smb.conf man page)
are:</P
><P
><PRE
CLASS="PROGRAMLISTING"
> [global]
print command - send a file to a spooler
lpq command - get spool queue status
lprm command - remove a job
[printers]
path = /var/spool/lpd/samba</PRE
></P
><TABLE
CLASS="WARNING"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="/docbook-dsssl/warning.gif"
HSPACE="5"
ALT="Warning"></TD
><TH
ALIGN="LEFT"
VALIGN="CENTER"
><B
>Achtung!</B
></TH
></TR
><TR
><TD
>&nbsp;</TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>The following <TT
CLASS="FILENAME"
>smb.conf</TT
> parameters are considered to
be deprecated and will be removed soon. Do not use them in new
installations</P
>The following are nice to know about:</P
><P
><PRE
CLASS="PROGRAMLISTING"
> queuepause command - stop a printer or print queue
queueresume command - start a printer or print queue</PRE
></P
><UL
><LI
><P
><TT
CLASS="PARAMETER"
><I
>printer driver file (G)</I
></TT
>
</P
></LI
><LI
>Example:</P
><P
><TT
CLASS="PARAMETER"
><I
>printer driver (S)</I
></TT
>
</P
></LI
><LI
><PRE
CLASS="PROGRAMLISTING"
> print command = /usr/bin/lpr -r -P%p %s
lpq command = /usr/bin/lpq -P%p %s
lprm command = /usr/bin/lprm -P%p %j
queuepause command = /usr/sbin/lpc -P%p stop
queuepause command = /usr/sbin/lpc -P%p start</PRE
></P
><P
><TT
CLASS="PARAMETER"
><I
>printer driver location (S)</I
></TT
>
</P
></LI
></UL
></TD
></TR
></TABLE
>Samba should set reasonable defaults for these depending on your
system type, but it isn't clairvoyant. It is not uncommon that you
have to tweak these for local conditions. The commands should
always have fully specified pathnames, as the smdb may not have
the correct PATH values.</P
><P
>When you send a job to Samba to be printed, it will make a temporary
copy of it in the directory specified in the [printers] section.
and it should be periodically cleaned out. The lpr -r option
requests that the temporary copy be removed after printing; If
printing fails then you might find leftover files in this directory,
and it should be periodically cleaned out. Samba used the lpq
command to determine the "job number" assigned to your print job
by the spooler.</P
><P
>The %&gt;letter&lt; are "macros" that get dynamically replaced with appropriate
values when they are used. The %s gets replaced with the name of the spool
file that Samba creates and the %p gets replaced with the name of the
printer. The %j gets replaced with the "job number" which comes from
the lpq output.</P
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN2099"
></A
>14.4.2. Debugging printer problems</H2
><P
>The have been two new parameters add in Samba 2.2.2 to for
better support of Samba 2.0.x backwards capability (<TT
CLASS="PARAMETER"
><I
>disable
spoolss</I
></TT
>) and for using local printers drivers on Windows
NT/2000 clients (<TT
CLASS="PARAMETER"
><I
>use client driver</I
></TT
>). Both of
these options are described in the smb.coinf(5) man page and are
disabled by default.</P
>One way to debug printing problems is to start by replacing these
command with shell scripts that record the arguments and the contents
of the print file. A simple example of this kind of things might
be:</P
><P
><PRE
CLASS="PROGRAMLISTING"
> print command = /tmp/saveprint %p %s
#!/bin/saveprint
# we make sure that we are the right user
/usr/bin/id -p &#62;/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&#62;&#62;&#38;/tmp/tmp.print</PRE
></P
><P
>Then you print a file and try removing it. You may find that the
print queue needs to be stopped in order to see the queue status
and remove the job:</P
><P
><PRE
CLASS="PROGRAMLISTING"
>&#13;h4: {42} % echo hi &#62;/tmp/hi
h4: {43} % smbclient //localhost/lw4
added interface ip=10.0.0.4 bcast=10.0.0.255 nmask=255.255.255.0
Password:
Domain=[ASTART] OS=[Unix] Server=[Samba 2.0.7]
smb: \&#62; print /tmp/hi
putting file /tmp/hi as hi-17534 (0.0 kb/s) (average 0.0 kb/s)
smb: \&#62; queue
1049 3 hi-17534
smb: \&#62; cancel 1049
Error cancelling job 1049 : code 0
smb: \&#62; cancel 1049
Job 1049 cancelled
smb: \&#62; queue
smb: \&#62; exit</PRE
></P
><P
>The 'code 0' indicates that the job was removed. The comment
by the smbclient is a bit misleading on this.
You can observe the command output and then and look at the
/tmp/tmp.print file to see what the results are. You can quickly
find out if the problem is with your printing system. Often people
have problems with their /etc/printcap file or permissions on
various print queues.</P
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN2108"
></A
>14.4.3. What printers do I have?</H2
><P
>You can use the 'testprns' program to check to see if the printer
name you are using is recognized by Samba. For example, you can
use:</P
><P
><PRE
CLASS="PROGRAMLISTING"
> testprns printer /etc/printcap</PRE
></P
><P
>Samba can get its printcap information from a file or from a program.
You can try the following to see the format of the extracted
information:</P
><P
><PRE
CLASS="PROGRAMLISTING"
> testprns -a printer /etc/printcap
testprns -a printer '|/bin/cat printcap'</PRE
></P
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN2116"
></A
>14.4.4. Setting up printcap and print servers</H2
><P
>You may need to set up some printcaps for your Samba system to use.
It is strongly recommended that you use the facilities provided by
the print spooler to set up queues and printcap information.</P
><P
>Samba requires either a printcap or program to deliver printcap
information. This printcap information has the format:</P
><P
><PRE
CLASS="PROGRAMLISTING"
> name|alias1|alias2...:option=value:...</PRE
></P
><P
>For almost all printing systems, the printer 'name' must be composed
only of alphanumeric or underscore '_' characters. Some systems also
allow hyphens ('-') as well. An alias is an alternative name for the
printer, and an alias with a space in it is used as a 'comment'
about the printer. The printcap format optionally uses a \ at the end of lines
to extend the printcap to multiple lines.</P
><P
>Here are some examples of printcap files:</P
><P
><P
></P
><OL
TYPE="1"
><LI
><P
>pr just printer name</P
></LI
><LI
><P
>pr|alias printer name and alias</P
></LI
><LI
><P
>pr|My Printer printer name, alias used as comment</P
></LI
><LI
><P
>pr:sh:\ Same as pr:sh:cm= testing
:cm= \
testing</P
></LI
><LI
><P
>pr:sh Same as pr:sh:cm= testing
:cm= testing</P
></LI
></OL
></P
><P
>Samba reads the printcap information when first started. If you make
changes in the printcap information, then you must do the following:</P
><P
></P
><OL
TYPE="1"
><LI
><P
>make sure that the print spooler is aware of these changes.
The LPRng system uses the 'lpc reread' command to do this.</P
></LI
><LI
><P
>make sure that the spool queues, etc., exist and have the
correct permissions. The LPRng system uses the 'checkpc -f'
command to do this.</P
></LI
><LI
><P
>You now should send a SIGHUP signal to the smbd server to have
it reread the printcap information.</P
></LI
></OL
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN2144"
></A
>14.4.5. Job sent, no output</H2
><P
>This is the most frustrating part of printing. You may have sent the
job, verified that the job was forwarded, set up a wrapper around
the command to send the file, but there was no output from the printer.</P
><P
>First, check to make sure that the job REALLY is getting to the
right print queue. If you are using a BSD or LPRng print spooler,
you can temporarily stop the printing of jobs. Jobs can still be
submitted, but they will not be printed. Use:</P
><P
><PRE
CLASS="PROGRAMLISTING"
> lpc -Pprinter stop</PRE
></P
><P
>Now submit a print job and then use 'lpq -Pprinter' to see if the
job is in the print queue. If it is not in the print queue then
you will have to find out why it is not being accepted for printing.</P
><P
>Next, you may want to check to see what the format of the job really
was. With the assistance of the system administrator you can view
the submitted jobs files. You may be surprised to find that these
are not in what you would expect to call a printable format.
You can use the UNIX 'file' utitily to determine what the job
format actually is:</P
><P
><PRE
CLASS="PROGRAMLISTING"
> cd /var/spool/lpd/printer # spool directory of print jobs
ls # find job files
file dfA001myhost</PRE
></P
><P
>You should make sure that your printer supports this format OR that
your system administrator has installed a 'print filter' that will
convert the file to a format appropriate for your printer.</P
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN2155"
></A
>14.4.6. Job sent, strange output</H2
><P
>Once you have the job printing, you can then start worrying about
making it print nicely.</P
><P
>The most common problem is extra pages of output: banner pages
OR blank pages at the end.</P
><P
>If you are getting banner pages, check and make sure that the
printcap option or printer option is configured for no banners.
If you have a printcap, this is the :sh (suppress header or banner
page) option. You should have the following in your printer.</P
><P
><PRE
CLASS="PROGRAMLISTING"
> printer: ... :sh</PRE
></P
><P
>If you have this option and are still getting banner pages, there
is a strong chance that your printer is generating them for you
automatically. You should make sure that banner printing is disabled
for the printer. This usually requires using the printer setup software
or procedures supplied by the printer manufacturer.</P
><P
>If you get an extra page of output, this could be due to problems
with your job format, or if you are generating PostScript jobs,
incorrect setting on your printer driver on the MicroSoft client.
For example, under Win95 there is a option:</P
><P
><PRE
CLASS="PROGRAMLISTING"
> Printers|Printer Name|(Right Click)Properties|Postscript|Advanced|</PRE
></P
><P
>that allows you to choose if a Ctrl-D is appended to all jobs.
This is a very bad thing to do, as most spooling systems will
automatically add a ^D to the end of the job if it is detected as
PostScript. The multiple ^D may cause an additional page of output.</P
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN2167"
></A
>14.4.7. Raw PostScript printed</H2
><P
>This is a problem that is usually caused by either the print spooling
system putting information at the start of the print job that makes
the printer think the job is a text file, or your printer simply
does not support PostScript. You may need to enable 'Automatic
Format Detection' on your printer.</P
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN2170"
></A
>14.4.8. Advanced Printing</H2
><P
>Note that you can do some pretty magic things by using your
imagination with the "print command" option and some shell scripts.
Doing print accounting is easy by passing the %U option to a print
command shell script. You could even make the print command detect
the type of output and its size and send it to an appropriate
printer.</P
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN2173"
></A
>14.4.9. Real debugging</H2
><P
>If the above debug tips don't help, then maybe you need to bring in
the bug guns, system tracing. See Tracing.txt in this directory.</P
></DIV
></DIV
></DIV
><DIV
@ -1184,7 +1380,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="unix-permissions.html"
HREF="msdfs.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -1202,7 +1398,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="printingdebug.html"
HREF="securitylevels.html"
ACCESSKEY="N"
>Next</A
></TD
@ -1212,17 +1408,21 @@ ACCESSKEY="N"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>UNIX Permission Bits and Windows NT Access Control Lists</TD
>Hosting a Microsoft Distributed File System tree on Samba</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><A
HREF="p1346.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Debugging Printing Problems</TD
>Security levels</TD
></TR
></TABLE
></DIV

53
docs/htmldocs/printingdebug.html
View File

@ -9,8 +9,11 @@ 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="p1342.html"><LINK
REL="PREVIOUS"
TITLE="Printing Support in Samba 2.2.x"
TITLE="Printing Support"
HREF="printing.html"><LINK
REL="NEXT"
TITLE="Security levels"
@ -71,15 +74,15 @@ CLASS="CHAPTER"
><A
NAME="PRINTINGDEBUG"
></A
>Chapter 7. Debugging Printing Problems</H1
>Chapter 15. Debugging Printing Problems</H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN986"
NAME="AEN2081"
></A
>7.1. Introduction</H1
>15.1. Introduction</H1
><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
@ -141,7 +144,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 %&gt;letter&lt; are "macros" that get dynamically replaced with appropriate
>The %&#62;letter&#60; 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
@ -152,9 +155,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN1002"
NAME="AEN2097"
></A
>7.2. Debugging printer problems</H1
>15.2. Debugging printer problems</H1
><P
>One way to debug printing problems is to start by replacing these
command with shell scripts that record the arguments and the contents
@ -209,9 +212,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN1011"
NAME="AEN2106"
></A
>7.3. What printers do I have?</H1
>15.3. What printers do I have?</H1
><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
@ -238,9 +241,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN1019"
NAME="AEN2114"
></A
>7.4. Setting up printcap and print servers</H1
>15.4. Setting up printcap and print servers</H1
><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
@ -322,9 +325,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN1047"
NAME="AEN2142"
></A
>7.5. Job sent, no output</H1
>15.5. Job sent, no output</H1
><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
@ -367,9 +370,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN1058"
NAME="AEN2153"
></A
>7.6. Job sent, strange output</H1
>15.6. Job sent, strange output</H1
><P
>Once you have the job printing, you can then start worrying about
making it print nicely.</P
@ -413,9 +416,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN1070"
NAME="AEN2165"
></A
>7.7. Raw PostScript printed</H1
>15.7. Raw PostScript printed</H1
><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
@ -428,9 +431,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN1073"
NAME="AEN2168"
></A
>7.8. Advanced Printing</H1
>15.8. Advanced Printing</H1
><P
>Note that you can do some pretty magic things by using your
imagination with the "print command" option and some shell scripts.
@ -444,9 +447,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN1076"
NAME="AEN2171"
></A
>7.9. Real debugging</H1
>15.9. Real debugging</H1
><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
@ -496,12 +499,16 @@ ACCESSKEY="N"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Printing Support in Samba 2.2.x</TD
>Printing Support</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><A
HREF="p1342.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"

52
docs/htmldocs/rpcclient.1.html
View File

@ -127,20 +127,48 @@ CLASS="PROGRAMLISTING"
>-d|--debug=debuglevel</DT
><DD
><P
>set the debuglevel. Debug level 0 is the lowest
and 100 being the highest. This should be set to 100 if you are
planning on submitting a bug report to the Samba team (see <TT
><TT
CLASS="REPLACEABLE"
><I
>debuglevel</I
></TT
> is an integer
from 0 to 10. The default value if this parameter is
not specified is zero.</P
><P
>The higher this value, the more detail will be
logged to the log files about the activities of the
server. At level 0, only critical errors and serious
warnings will be logged. Level 1 is a reasonable level for
day to day running - it generates a small amount of
information about operations carried out.</P
><P
>Levels above 1 will generate considerable
amounts of log data, and should only be used when
investigating a problem. Levels above 3 are designed for
use only by developers and generate HUGE amounts of log
data, most of which is extremely cryptic.</P
><P
>Note that specifying this parameter here will
override the <A
HREF="smb.conf.5.html#loglevel"
TARGET="_top"
>log
level</A
> parameter in the <A
HREF="smb.conf.5.html"
TARGET="_top"
><TT
CLASS="FILENAME"
>BUGS.txt</TT
>).
</P
>smb.conf(5)</TT
></A
> file.</P
></DD
><DT
>-h|--help</DT
><DD
><P
>Print a summary of command line options.
</P
>Print a summary of command line options.</P
></DD
><DT
>-I IP-address</DT
@ -275,7 +303,7 @@ CLASS="COMMAND"
><DIV
CLASS="REFSECT1"
><A
NAME="AEN101"
NAME="AEN107"
></A
><H2
>COMMANDS</H2
@ -677,7 +705,7 @@ CLASS="COMMAND"
><DIV
CLASS="REFSECT1"
><A
NAME="AEN221"
NAME="AEN227"
></A
><H2
>BUGS</H2
@ -722,7 +750,7 @@ CLASS="COMMAND"
><DIV
CLASS="REFSECT1"
><A
NAME="AEN231"
NAME="AEN237"
></A
><H2
>VERSION</H2
@ -733,7 +761,7 @@ NAME="AEN231"
><DIV
CLASS="REFSECT1"
><A
NAME="AEN234"
NAME="AEN240"
></A
><H2
>AUTHOR</H2

57
docs/htmldocs/samba-bdc.html
View File

@ -9,12 +9,15 @@ CONTENT="Modular DocBook HTML Stylesheet Version 1.77"><LINK
REL="HOME"
TITLE="SAMBA Project Documentation"
HREF="samba-howto-collection.html"><LINK
REL="UP"
TITLE="Type of installation"
HREF="p544.html"><LINK
REL="PREVIOUS"
TITLE="How to Configure Samba 2.2 as a Primary Domain Controller"
TITLE="How to Configure Samba as a NT4 Primary Domain Controller"
HREF="samba-pdc.html"><LINK
REL="NEXT"
TITLE="Storing Samba's User/Machine Account information in an LDAP Directory"
HREF="samba-ldap-howto.html"></HEAD
TITLE="Samba as a ADS domain member"
HREF="ads.html"></HEAD
><BODY
CLASS="CHAPTER"
BGCOLOR="#FFFFFF"
@ -56,7 +59,7 @@ WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="samba-ldap-howto.html"
HREF="ads.html"
ACCESSKEY="N"
>Next</A
></TD
@ -71,15 +74,15 @@ CLASS="CHAPTER"
><A
NAME="SAMBA-BDC"
></A
>Chapter 12. How to Act as a Backup Domain Controller in a Purely Samba Controlled Domain</H1
>Chapter 7. How to Act as a Backup Domain Controller in a Purely Samba Controlled Domain</H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2148"
NAME="AEN1118"
></A
>12.1. Prerequisite Reading</H1
>7.1. Prerequisite Reading</H1
><P
>Before you continue reading in this chapter, please make sure
that you are comfortable with configuring a Samba PDC
@ -94,9 +97,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2152"
NAME="AEN1122"
></A
>12.2. Background</H1
>7.2. Background</H1
><P
>What is a Domain Controller? It is a machine that is able to answer
logon requests from workstations in a Windows NT Domain. Whenever a
@ -139,9 +142,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2160"
NAME="AEN1130"
></A
>12.3. What qualifies a Domain Controller on the network?</H1
>7.3. What qualifies a Domain Controller on the network?</H1
><P
>Every machine that is a Domain Controller for the domain SAMBA has to
register the NetBIOS group name SAMBA#1c with the WINS server and/or
@ -156,9 +159,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN2163"
NAME="AEN1133"
></A
>12.3.1. How does a Workstation find its domain controller?</H2
>7.3.1. How does a Workstation find its domain controller?</H2
><P
>A NT workstation in the domain SAMBA that wants a local user to be
authenticated has to find the domain controller for SAMBA. It does
@ -175,9 +178,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN2166"
NAME="AEN1136"
></A
>12.3.2. When is the PDC needed?</H2
>7.3.2. When is the PDC needed?</H2
><P
>Whenever a user wants to change his password, this has to be done on
the PDC. To find the PDC, the workstation does a NetBIOS name query
@ -191,9 +194,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2169"
NAME="AEN1139"
></A
>12.4. Can Samba be a Backup Domain Controller?</H1
>7.4. Can Samba be a Backup Domain Controller?</H1
><P
>With version 2.2, no. The native NT SAM replication protocols have
not yet been fully implemented. The Samba Team is working on
@ -210,9 +213,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2173"
NAME="AEN1143"
></A
>12.5. How do I set up a Samba BDC?</H1
>7.5. How do I set up a Samba BDC?</H1
><P
>Several things have to be done:</P
><P
@ -277,9 +280,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN2190"
NAME="AEN1160"
></A
>12.5.1. How do I replicate the smbpasswd file?</H2
>7.5.1. How do I replicate the smbpasswd file?</H2
><P
>Replication of the smbpasswd file is sensitive. It has to be done
whenever changes to the SAM are made. Every user's password change is
@ -329,7 +332,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="samba-ldap-howto.html"
HREF="ads.html"
ACCESSKEY="N"
>Next</A
></TD
@ -339,17 +342,21 @@ ACCESSKEY="N"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>How to Configure Samba 2.2 as a Primary Domain Controller</TD
>How to Configure Samba as a NT4 Primary Domain Controller</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><A
HREF="p544.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Storing Samba's User/Machine Account information in an LDAP Directory</TD
>Samba as a ADS domain member</TD
></TR
></TABLE
></DIV

79
docs/htmldocs/samba-ldap-howto.html
View File

@ -9,12 +9,15 @@ 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="p1346.html"><LINK
REL="PREVIOUS"
TITLE="How to Act as a Backup Domain Controller in a Purely Samba Controlled Domain"
HREF="samba-bdc.html"><LINK
TITLE="Passdb XML plugin"
HREF="pdb-xml.html"><LINK
REL="NEXT"
TITLE="Using samba 3.0 with ActiveDirectory support"
HREF="ads.html"></HEAD
TITLE="HOWTO Access Samba source code via CVS"
HREF="cvs-access.html"></HEAD
><BODY
CLASS="CHAPTER"
BGCOLOR="#FFFFFF"
@ -42,7 +45,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="samba-bdc.html"
HREF="pdb-xml.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -56,7 +59,7 @@ WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="ads.html"
HREF="cvs-access.html"
ACCESSKEY="N"
>Next</A
></TD
@ -71,15 +74,15 @@ CLASS="CHAPTER"
><A
NAME="SAMBA-LDAP-HOWTO"
></A
>Chapter 13. Storing Samba's User/Machine Account information in an LDAP Directory</H1
>Chapter 19. Storing Samba's User/Machine Account information in an LDAP Directory</H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2211"
NAME="AEN2664"
></A
>13.1. Purpose</H1
>19.1. Purpose</H1
><P
>This document describes how to use an LDAP directory for storing Samba user
account information traditionally stored in the smbpasswd(5) file. It is
@ -145,9 +148,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2231"
NAME="AEN2684"
></A
>13.2. Introduction</H1
>19.2. Introduction</H1
><P
>Traditionally, when configuring <A
HREF="smb.conf.5.html#ENCRYPTPASSWORDS"
@ -262,9 +265,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2260"
NAME="AEN2713"
></A
>13.3. Supported LDAP Servers</H1
>19.3. Supported LDAP Servers</H1
><P
>The LDAP samdb code in 2.2.3 has been developed and tested using the OpenLDAP
2.0 server and client libraries. The same code should be able to work with
@ -287,9 +290,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2265"
NAME="AEN2718"
></A
>13.4. Schema and Relationship to the RFC 2307 posixAccount</H1
>19.4. Schema and Relationship to the RFC 2307 posixAccount</H1
><P
>Samba 2.2.3 includes the necessary schema file for OpenLDAP 2.0 in
<TT
@ -346,17 +349,17 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2277"
NAME="AEN2730"
></A
>13.5. Configuring Samba with LDAP</H1
>19.5. Configuring Samba with LDAP</H1
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN2279"
NAME="AEN2732"
></A
>13.5.1. OpenLDAP configuration</H2
>19.5.1. OpenLDAP configuration</H2
><P
>To include support for the sambaAccount object in an OpenLDAP directory
server, first copy the samba.schema file to slapd's configuration directory.</P
@ -436,9 +439,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN2296"
NAME="AEN2749"
></A
>13.5.2. Configuring Samba</H2
>19.5.2. Configuring Samba</H2
><P
>The following parameters are available in smb.conf only with <TT
CLASS="PARAMETER"
@ -556,9 +559,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2324"
NAME="AEN2777"
></A
>13.6. Accounts and Groups management</H1
>19.6. Accounts and Groups management</H1
><P
>As users accounts are managed thru the sambaAccount objectclass, you should
modify you existing administration tools to deal with sambaAccount attributes.</P
@ -581,9 +584,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2329"
NAME="AEN2782"
></A
>13.7. Security and sambaAccount</H1
>19.7. Security and sambaAccount</H1
><P
>There are two important points to remember when discussing the security
of sambaAccount entries in the directory.</P
@ -660,9 +663,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2349"
NAME="AEN2802"
></A
>13.8. LDAP specials attributes for sambaAccounts</H1
>19.8. LDAP specials attributes for sambaAccounts</H1
><P
>The sambaAccount objectclass is composed of the following attributes:</P
><P
@ -871,9 +874,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2419"
NAME="AEN2872"
></A
>13.9. Example LDIF Entries for a sambaAccount</H1
>19.9. Example LDIF Entries for a sambaAccount</H1
><P
>The following is a working LDIF with the inclusion of the posixAccount objectclass:</P
><P
@ -929,9 +932,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2427"
NAME="AEN2880"
></A
>13.10. Comments</H1
>19.10. Comments</H1
><P
>Please mail all comments regarding this HOWTO to <A
HREF="mailto:jerry@samba.org"
@ -957,7 +960,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="samba-bdc.html"
HREF="pdb-xml.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -975,7 +978,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="ads.html"
HREF="cvs-access.html"
ACCESSKEY="N"
>Next</A
></TD
@ -985,17 +988,21 @@ ACCESSKEY="N"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>How to Act as a Backup Domain Controller in a Purely Samba Controlled Domain</TD
>Passdb XML plugin</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><A
HREF="p1346.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Using samba 3.0 with ActiveDirectory support</TD
>HOWTO Access Samba source code via CVS</TD
></TR
></TABLE
></DIV

41
docs/htmldocs/securitylevels.html
View File

@ -9,12 +9,15 @@ 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="p1346.html"><LINK
REL="PREVIOUS"
TITLE="Debugging Printing Problems"
HREF="printingdebug.html"><LINK
TITLE="Printing Support"
HREF="printing.html"><LINK
REL="NEXT"
TITLE="security = domain in Samba 2.x"
HREF="domain-security.html"></HEAD
TITLE="Unified Logons between Windows NT and UNIX using Winbind"
HREF="winbind.html"></HEAD
><BODY
CLASS="CHAPTER"
BGCOLOR="#FFFFFF"
@ -42,7 +45,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="printingdebug.html"
HREF="printing.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -56,7 +59,7 @@ WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="domain-security.html"
HREF="winbind.html"
ACCESSKEY="N"
>Next</A
></TD
@ -71,15 +74,15 @@ CLASS="CHAPTER"
><A
NAME="SECURITYLEVELS"
></A
>Chapter 8. Security levels</H1
>Chapter 15. Security levels</H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN1089"
NAME="AEN2186"
></A
>8.1. Introduction</H1
>15.1. Introduction</H1
><P
>Samba supports the following options to the global smb.conf parameter</P
><P
@ -95,7 +98,7 @@ CLASS="PARAMETER"
>security</I
></TT
></A
> = [share|user(default)|domain|ads]</PRE
> = [share|user(default)|server|domain|ads]</PRE
></P
><P
>Please refer to the smb.conf man page for usage information and to the document
@ -123,9 +126,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN1100"
NAME="AEN2197"
></A
>8.2. More complete description of security levels</H1
>15.2. More complete description of security levels</H1
><P
>A SMB server tells the client at startup what "security level" it is
running. There are two options "share level" and "user level". Which
@ -229,7 +232,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="printingdebug.html"
HREF="printing.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -247,7 +250,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="domain-security.html"
HREF="winbind.html"
ACCESSKEY="N"
>Next</A
></TD
@ -257,17 +260,21 @@ ACCESSKEY="N"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Debugging Printing Problems</TD
>Printing Support</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><A
HREF="p1346.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>security = domain in Samba 2.x</TD
>Unified Logons between Windows NT and UNIX using Winbind</TD
></TR
></TABLE
></DIV

351
docs/htmldocs/smb.conf.5.html
View File

@ -531,31 +531,6 @@ NAME="AEN112"
CLASS="VARIABLELIST"
><DL
><DT
>%S</DT
><DD
><P
>the name of the current service, if any.</P
></DD
><DT
>%P</DT
><DD
><P
>the root directory of the current service,
if any.</P
></DD
><DT
>%u</DT
><DD
><P
>user name of the current service, if any.</P
></DD
><DT
>%g</DT
><DD
><P
>primary group name of %u.</P
></DD
><DT
>%U</DT
><DD
><P
@ -569,19 +544,6 @@ CLASS="VARIABLELIST"
>primary group name of %U.</P
></DD
><DT
>%H</DT
><DD
><P
>the home directory of the user given
by %u.</P
></DD
><DT
>%v</DT
><DD
><P
>the Samba version.</P
></DD
><DT
>%h</DT
><DD
><P
@ -614,29 +576,6 @@ CLASS="VARIABLELIST"
</P
></DD
><DT
>%N</DT
><DD
><P
>the name of your NIS home directory server.
This is obtained from your NIS auto.map entry. If you have
not compiled Samba with the <SPAN
CLASS="emphasis"
><I
CLASS="EMPHASIS"
>--with-automount</I
></SPAN
>
option then this value will be the same as %L.</P
></DD
><DT
>%p</DT
><DD
><P
>the path of the service's home directory,
obtained from your NIS auto.map entry. The NIS auto.map entry
is split up as "%N:%p".</P
></DD
><DT
>%R</DT
><DD
><P
@ -680,6 +619,12 @@ TARGET="_top"
>the current date and time.</P
></DD
><DT
>%D</DT
><DD
><P
>Name of the domain or workgroup of the current user.</P
></DD
><DT
>%$(<TT
CLASS="REPLACEABLE"
><I
@ -699,13 +644,78 @@ CLASS="REPLACEABLE"
></DL
></DIV
><P
>The following substitutes apply only to some configuration options(only those
that are used when a connection has been established):</P
><P
></P
><DIV
CLASS="VARIABLELIST"
><DL
><DT
>%S</DT
><DD
><P
>the name of the current service, if any.</P
></DD
><DT
>%P</DT
><DD
><P
>the root directory of the current service,
if any.</P
></DD
><DT
>%u</DT
><DD
><P
>user name of the current service, if any.</P
></DD
><DT
>%g</DT
><DD
><P
>primary group name of %u.</P
></DD
><DT
>%H</DT
><DD
><P
>the home directory of the user given
by %u.</P
></DD
><DT
>%N</DT
><DD
><P
>the name of your NIS home directory server.
This is obtained from your NIS auto.map entry. If you have
not compiled Samba with the <SPAN
CLASS="emphasis"
><I
CLASS="EMPHASIS"
>--with-automount</I
></SPAN
>
option then this value will be the same as %L.</P
></DD
><DT
>%p</DT
><DD
><P
>the path of the service's home directory,
obtained from your NIS auto.map entry. The NIS auto.map entry
is split up as "%N:%p".</P
></DD
></DL
></DIV
><P
>There are some quite creative things that can be done
with these substitutions and other smb.conf options.</P
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN203"
NAME="AEN205"
></A
><H2
>NAME MANGLING</H2
@ -804,13 +814,13 @@ CLASS="EMPHASIS"
></DL
></DIV
><P
>By default, Samba 2.2 has the same semantics as a Windows
>By default, Samba 3.0 has the same semantics as a Windows
NT server, in that it is case insensitive but case preserving.</P
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN236"
NAME="AEN238"
></A
><H2
>NOTE ABOUT USERNAME/PASSWORD VALIDATION</H2
@ -888,7 +898,7 @@ CLASS="FILENAME"
><DIV
CLASS="REFSECT1"
><A
NAME="AEN255"
NAME="AEN257"
></A
><H2
>COMPLETE LIST OF GLOBAL PARAMETERS</H2
@ -1669,6 +1679,18 @@ CLASS="PARAMETER"
><LI
><P
><A
HREF="#LDAPTRUSTIDS"
><TT
CLASS="PARAMETER"
><I
>ldap trust ids</I
></TT
></A
></P
></LI
><LI
><P
><A
HREF="#LMANNOUNCE"
><TT
CLASS="PARAMETER"
@ -3147,7 +3169,7 @@ CLASS="PARAMETER"
><DIV
CLASS="REFSECT1"
><A
NAME="AEN1007"
NAME="AEN1013"
></A
><H2
>COMPLETE LIST OF SERVICE PARAMETERS</H2
@ -4650,7 +4672,7 @@ CLASS="PARAMETER"
><DIV
CLASS="REFSECT1"
><A
NAME="AEN1507"
NAME="AEN1513"
></A
><H2
>EXPLANATION OF EACH PARAMETER</H2
@ -5482,12 +5504,12 @@ NAME="ANNOUNCEVERSION"
><P
>This specifies the major and minor version numbers
that nmbd will use when announcing itself as a server. The default
is 4.2. Do not change this parameter unless you have a specific
is 4.9. Do not change this parameter unless you have a specific
need to set a Samba server to be a downlevel server.</P
><P
>Default: <B
CLASS="COMMAND"
>announce version = 4.5</B
>announce version = 4.9</B
></P
><P
>Example: <B
@ -5829,7 +5851,7 @@ TARGET="_top"
request has a time limit associated with it.</P
><P
>If this parameter is set and the lock range requested
cannot be immediately satisfied, Samba 2.2 will internally
cannot be immediately satisfied, samba will internally
queue the lock request, and periodically attempt to obtain
the lock until the timeout period expires.</P
><P
@ -5837,7 +5859,7 @@ TARGET="_top"
CLASS="CONSTANT"
>no</TT
>, then
Samba 2.2 will behave as previous versions of Samba would and
samba will behave as previous versions of Samba would and
will fail the lock request immediately if the lock range
cannot be obtained.</P
><P
@ -5953,7 +5975,7 @@ NAME="CASESENSITIVE"
><DD
><P
>See the discussion in the section <A
HREF="#AEN203"
HREF="#AEN205"
>NAME MANGLING</A
>.</P
><P
@ -6516,7 +6538,7 @@ NAME="DEBUGTIMESTAMP"
>debug timestamp (G)</DT
><DD
><P
>Samba 2.2 debug log messages are timestamped
>Samba debug log messages are timestamped
by default. If you are running at a high <A
HREF="#DEBUGLEVEL"
> <TT
@ -6604,7 +6626,7 @@ NAME="DEFAULTCASE"
><DD
><P
>See the section on <A
HREF="#AEN203"
HREF="#AEN205"
> NAME MANGLING</A
>. Also note the <A
HREF="#SHORTPRESERVECASE"
@ -8703,7 +8725,7 @@ CLASS="COMMAND"
> lp(1)</B
>.</P
><P
>This paramater does not accept % macros, because
>This parameter does not accept % macros, because
many parts of the system require this value to be
constant for correct operation.</P
><P
@ -9972,21 +9994,6 @@ CLASS="PARAMETER"
><TT
CLASS="PARAMETER"
><I
>On</I
></TT
> = Always use SSL when contacting the
<TT
CLASS="PARAMETER"
><I
>ldap server</I
></TT
>.</P
></LI
><LI
><P
><TT
CLASS="PARAMETER"
><I
>Off</I
></TT
> = Never use SSL when querying the directory.</P
@ -10001,11 +10008,40 @@ CLASS="PARAMETER"
> = Use the LDAPv3 StartTLS extended operation
(RFC2830) for communicating with the directory server.</P
></LI
><LI
><P
><TT
CLASS="PARAMETER"
><I
>On</I
></TT
> =
Use SSL on the ldaps port when contacting the
<TT
CLASS="PARAMETER"
><I
>ldap server</I
></TT
>. Only
available when the backwards-compatiblity <B
CLASS="COMMAND"
> --with-ldapsam</B
> option is specified
to configure. See <A
HREF="#PASSDBBACKEND"
><TT
CLASS="PARAMETER"
><I
>passdb backend</I
></TT
></A
></P
></LI
></UL
><P
>Default : <B
CLASS="COMMAND"
>ldap ssl = on</B
>ldap ssl = start_tls</B
></P
></DD
><DT
@ -10015,6 +10051,14 @@ NAME="LDAPSUFFIX"
>ldap suffix (G)</DT
><DD
><P
>Specifies where user and machine accounts are added to the tree. Can be overriden by <B
CLASS="COMMAND"
>ldap user suffix</B
> and <B
CLASS="COMMAND"
>ldap machine suffix</B
>. It also used as the base dn for all ldap searches. </P
><P
>Default : <SPAN
CLASS="emphasis"
><I
@ -10120,6 +10164,35 @@ CLASS="COMMAND"
></DD
><DT
><A
NAME="LDAPTRUSTIDS"
></A
>ldap trust ids (G)</DT
><DD
><P
>Normally, Samba validates each entry
in the LDAP server against getpwnam(). This allows
LDAP to be used for Samba with the unix system using
NIS (for example) and also ensures that Samba does not
present accounts that do not otherwise exist. </P
><P
>This option is used to disable this functionality, and
instead to rely on the presence of the appropriate
attributes in LDAP directly, which can result in a
significant performance boost in some situations.
Setting this option to yes effectivly assumes
that the local machine is running <B
CLASS="COMMAND"
>nss_ldap</B
> against the
same LDAP server.</P
><P
>Default: <B
CLASS="COMMAND"
>ldap trust ids = No</B
></P
></DD
><DT
><A
NAME="LEVEL2OPLOCKS"
></A
>level2 oplocks (S)</DT
@ -11468,7 +11541,7 @@ NAME="MANGLECASE"
><DD
><P
>See the section on <A
HREF="#AEN203"
HREF="#AEN205"
> NAME MANGLING</A
></P
><P
@ -11544,7 +11617,7 @@ NAME="MANGLEDNAMES"
or whether non-DOS names should simply be ignored.</P
><P
>See the section on <A
HREF="#AEN203"
HREF="#AEN205"
> NAME MANGLING</A
> for details on how to control the mangling process.</P
><P
@ -11631,17 +11704,39 @@ NAME="MANGLINGMETHOD"
a better algorithm (generates less collisions) in the names.
However, many Win32 applications store the mangled names and so
changing to the new algorithm must not be done
lightly as these applications may break unless reinstalled.
New installations of Samba may set the default to hash2.</P
lightly as these applications may break unless reinstalled.</P
><P
>Default: <B
CLASS="COMMAND"
>mangling method = hash</B
>mangling method = hash2</B
></P
><P
>Example: <B
CLASS="COMMAND"
>mangling method = hash2</B
>mangling method = hash</B
></P
></DD
><DT
><A
NAME="MANGLEPREFIX"
></A
>mangle prefix (G)</DT
><DD
><P
> controls the number of prefix
characters from the original name used when generating
the mangled names. A larger value will give a weaker
hash and therefore more name collisions. The minimum
value is 1 and the maximum value is 6.</P
><P
>Default: <B
CLASS="COMMAND"
>mangle prefix = 1</B
></P
><P
>Example: <B
CLASS="COMMAND"
>mangle prefix = 4</B
></P
></DD
><DT
@ -11696,7 +11791,7 @@ CLASS="EMPHASIS"
>magic</I
></SPAN
> character in <A
HREF="#AEN203"
HREF="#AEN205"
>name mangling</A
>. The default is a '~'
but this may interfere with some software. Use this option to set
@ -13677,15 +13772,41 @@ CLASS="COMMAND"
>ldap://localhost</B
>)</P
><P
>Note: In this module, any account
without a matching POSIX account is regarded
as 'non unix'.
</P
><P
>See also <A
HREF="#NONUNIXACCOUNTRANGE"
> <TT
CLASS="PARAMETER"
><I
>non unix account range</I
>non unix account
range</I
></TT
></A
></P
><P
>LDAP connections should be secured where
possible. This may be done using either
Start-TLS (see <A
HREF="#LDAPSSL"
> <TT
CLASS="PARAMETER"
><I
>ldap ssl</I
></TT
></A
>) or by
specifying <TT
CLASS="PARAMETER"
><I
>ldaps://</I
></TT
> in
the URL argument.
</P
></LI
><LI
><P
@ -14781,7 +14902,7 @@ CLASS="COMMAND"
></P
><P
>See the section on <A
HREF="#AEN203"
HREF="#AEN205"
>NAME
MANGLING</A
> for a fuller discussion.</P
@ -16547,7 +16668,7 @@ CLASS="EMPHASIS"
be used in granting access.</P
><P
>See also the section <A
HREF="#AEN236"
HREF="#AEN238"
> NOTE ABOUT USERNAME/PASSWORD VALIDATION</A
>.</P
><P
@ -16640,7 +16761,7 @@ CLASS="PARAMETER"
> parameter for details on doing this.</P
><P
>See also the section <A
HREF="#AEN236"
HREF="#AEN238"
> NOTE ABOUT USERNAME/PASSWORD VALIDATION</A
>.</P
><P
@ -16732,7 +16853,7 @@ CLASS="PARAMETER"
> parameter for details on doing this.</P
><P
>See also the section <A
HREF="#AEN236"
HREF="#AEN238"
> NOTE ABOUT USERNAME/PASSWORD VALIDATION</A
>.</P
><P
@ -16871,7 +16992,7 @@ CLASS="COMMAND"
Domain Controller. This issue will be addressed in a future release.</P
><P
>See also the section <A
HREF="#AEN236"
HREF="#AEN238"
> NOTE ABOUT USERNAME/PASSWORD VALIDATION</A
>.</P
><P
@ -17143,7 +17264,7 @@ CLASS="COMMAND"
names are lowered. </P
><P
>See the section on <A
HREF="#AEN203"
HREF="#AEN205"
> NAME MANGLING</A
>.</P
><P
@ -18037,7 +18158,8 @@ NAME="UNICODE"
><DD
><P
>Specifies whether Samba should try
to use unicode on the wire by default.
to use unicode on the wire by default. Note: This does NOT
mean that samba will assume that the unix machine uses unicode!
</P
><P
>Default: <B
@ -18061,6 +18183,11 @@ NAME="UNIXCHARSET"
CLASS="COMMAND"
>unix charset = ASCII</B
></P
><P
>Example: <B
CLASS="COMMAND"
>unix charset = UTF8</B
></P
></DD
><DT
><A
@ -18427,7 +18554,7 @@ CLASS="PARAMETER"
search.</P
><P
>See the section <A
HREF="#AEN236"
HREF="#AEN238"
>NOTE ABOUT
USERNAME/PASSWORD VALIDATION</A
> for more information on how
@ -19763,7 +19890,7 @@ CLASS="PARAMETER"
><DIV
CLASS="REFSECT1"
><A
NAME="AEN6113"
NAME="AEN6150"
></A
><H2
>WARNINGS</H2
@ -19793,18 +19920,18 @@ TARGET="_top"
><DIV
CLASS="REFSECT1"
><A
NAME="AEN6119"
NAME="AEN6156"
></A
><H2
>VERSION</H2
><P
>This man page is correct for version 2.2 of
>This man page is correct for version 3.0 of
the Samba suite.</P
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN6122"
NAME="AEN6159"
></A
><H2
>SEE ALSO</H2
@ -19883,7 +20010,7 @@ CLASS="COMMAND"
><DIV
CLASS="REFSECT1"
><A
NAME="AEN6142"
NAME="AEN6179"
></A
><H2
>AUTHOR</H2

2
docs/htmldocs/smbclient.1.html
View File

@ -38,7 +38,7 @@ NAME="AEN8"
><B
CLASS="COMMAND"
>smbclient</B
> {servicename} [password] [-b &lt;buffer size&gt;] [-d debuglevel] [-D Directory] [-U username] [-W workgroup] [-M &lt;netbios name&gt;] [-m maxprotocol] [-A authfile] [-N] [-l logfile] [-L &lt;netbios name&gt;] [-I destinationIP] [-E &lt;terminal code&gt;] [-c &lt;command string&gt;] [-i scope] [-O &lt;socket options&gt;] [-p port] [-R &lt;name resolve order&gt;] [-s &lt;smb config file&gt;] [-T&lt;c|x&gt;IXFqgbNan]</P
> {servicename} [password] [-b &lt;buffer size&gt;] [-d debuglevel] [-D Directory] [-U username] [-W workgroup] [-M &lt;netbios name&gt;] [-m maxprotocol] [-A authfile] [-N] [-l logfile] [-L &lt;netbios name&gt;] [-I destinationIP] [-E] [-c &lt;command string&gt;] [-i scope] [-O &lt;socket options&gt;] [-p port] [-R &lt;name resolve order&gt;] [-s &lt;smb config file&gt;] [-T&lt;c|x&gt;IXFqgbNan]</P
></DIV
><DIV
CLASS="REFSECT1"

2
docs/htmldocs/smbpasswd.5.html
View File

@ -301,7 +301,7 @@ NAME="AEN73"
><H2
>VERSION</H2
><P
>This man page is correct for version 2.2 of
>This man page is correct for version 3.0 of
the Samba suite.</P
></DIV
><DIV

111
docs/htmldocs/speed.html
View File

@ -9,12 +9,15 @@ 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="p1346.html"><LINK
REL="PREVIOUS"
TITLE="Quick Cross Subnet Browsing / Cross Workgroup Browsing guide"
HREF="browsing-quick.html"><LINK
TITLE="Group mapping HOWTO"
HREF="groupmapping.html"><LINK
REL="NEXT"
TITLE="HOWTO Access Samba source code via CVS"
HREF="cvs-access.html"></HEAD
TITLE="Appendixes"
HREF="p3106.html"></HEAD
><BODY
CLASS="CHAPTER"
BGCOLOR="#FFFFFF"
@ -42,7 +45,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="browsing-quick.html"
HREF="groupmapping.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -56,7 +59,7 @@ WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="cvs-access.html"
HREF="p3106.html"
ACCESSKEY="N"
>Next</A
></TD
@ -71,15 +74,15 @@ CLASS="CHAPTER"
><A
NAME="SPEED"
></A
>Chapter 17. Samba performance issues</H1
>Chapter 22. Samba performance issues</H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2742"
NAME="AEN2982"
></A
>17.1. Comparisons</H1
>22.1. Comparisons</H1
><P
>The Samba server uses TCP to talk to the client. Thus if you are
trying to see if it performs well you should really compare it to
@ -108,17 +111,17 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2748"
NAME="AEN2988"
></A
>17.2. Oplocks</H1
>22.2. Oplocks</H1
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN2750"
NAME="AEN2990"
></A
>17.2.1. Overview</H2
>22.2.1. Overview</H2
><P
>Oplocks are the way that SMB clients get permission from a server to
locally cache file operations. If a server grants an oplock
@ -152,9 +155,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN2758"
NAME="AEN2998"
></A
>17.2.2. Level2 Oplocks</H2
>22.2.2. Level2 Oplocks</H2
><P
>With Samba 2.0.5 a new capability - level2 (read only) oplocks is
supported (although the option is off by default - see the smb.conf
@ -176,9 +179,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN2764"
NAME="AEN3004"
></A
>17.2.3. Old 'fake oplocks' option - deprecated</H2
>22.2.3. Old 'fake oplocks' option - deprecated</H2
><P
>Samba can also fake oplocks, by granting a oplock whenever a client
asks for one. This is controlled using the smb.conf option "fake
@ -197,9 +200,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2768"
NAME="AEN3008"
></A
>17.3. Socket options</H1
>22.3. Socket options</H1
><P
>There are a number of socket options that can greatly affect the
performance of a TCP based server like Samba.</P
@ -225,9 +228,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2775"
NAME="AEN3015"
></A
>17.4. Read size</H1
>22.4. Read size</H1
><P
>The option "read size" affects the overlap of disk reads/writes with
network reads/writes. If the amount of data being transferred in
@ -251,9 +254,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2780"
NAME="AEN3020"
></A
>17.5. Max xmit</H1
>22.5. Max xmit</H1
><P
>At startup the client and server negotiate a "maximum transmit" size,
which limits the size of nearly all SMB commands. You can set the
@ -274,9 +277,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2785"
NAME="AEN3025"
></A
>17.6. Locking</H1
>22.6. Locking</H1
><P
>By default Samba does not implement strict locking on each read/write
call (although it did in previous versions). If you enable strict
@ -291,9 +294,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2789"
NAME="AEN3029"
></A
>17.7. Share modes</H1
>22.7. Share modes</H1
><P
>Some people find that opening files is very slow. This is often
because of the "share modes" code needed to fully implement the dos
@ -321,9 +324,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2794"
NAME="AEN3034"
></A
>17.8. Log level</H1
>22.8. Log level</H1
><P
>If you set the log level (also known as "debug level") higher than 2
then you may suffer a large drop in performance. This is because the
@ -335,9 +338,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2797"
NAME="AEN3037"
></A
>17.9. Wide lines</H1
>22.9. Wide lines</H1
><P
>The "wide links" option is now enabled by default, but if you disable
it (for better security) then you may suffer a performance hit in
@ -349,9 +352,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2800"
NAME="AEN3040"
></A
>17.10. Read raw</H1
>22.10. Read raw</H1
><P
>The "read raw" operation is designed to be an optimised, low-latency
file read operation. A server may choose to not support it,
@ -371,9 +374,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2805"
NAME="AEN3045"
></A
>17.11. Write raw</H1
>22.11. Write raw</H1
><P
>The "write raw" operation is designed to be an optimised, low-latency
file write operation. A server may choose to not support it,
@ -388,9 +391,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2809"
NAME="AEN3049"
></A
>17.12. Read prediction</H1
>22.12. Read prediction</H1
><P
>Samba can do read prediction on some of the SMB commands. Read
prediction means that Samba reads some extra data on the last file it
@ -414,9 +417,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2816"
NAME="AEN3056"
></A
>17.13. Memory mapping</H1
>22.13. Memory mapping</H1
><P
>Samba supports reading files via memory mapping them. One some
machines this can give a large boost to performance, on others it
@ -435,9 +438,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2821"
NAME="AEN3061"
></A
>17.14. Slow Clients</H1
>22.14. Slow Clients</H1
><P
>One person has reported that setting the protocol to COREPLUS rather
than LANMAN2 gave a dramatic speed improvement (from 10k/s to 150k/s).</P
@ -452,9 +455,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2825"
NAME="AEN3065"
></A
>17.15. Slow Logins</H1
>22.15. Slow Logins</H1
><P
>Slow logins are almost always due to the password checking time. Using
the lowest practical "password level" will improve things a lot. You
@ -465,9 +468,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2828"
NAME="AEN3068"
></A
>17.16. Client tuning</H1
>22.16. Client tuning</H1
><P
>Often a speed problem can be traced to the client. The client (for
example Windows for Workgroups) can often be tuned for better TCP
@ -569,9 +572,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2860"
NAME="AEN3100"
></A
>17.17. My Results</H1
>22.17. My Results</H1
><P
>Some people want to see real numbers in a document like this, so here
they are. I have a 486sx33 client running WfWg 3.11 with the 3.11b
@ -610,7 +613,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="browsing-quick.html"
HREF="groupmapping.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -628,7 +631,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="cvs-access.html"
HREF="p3106.html"
ACCESSKEY="N"
>Next</A
></TD
@ -638,17 +641,21 @@ ACCESSKEY="N"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Quick Cross Subnet Browsing / Cross Workgroup Browsing guide</TD
>Group mapping HOWTO</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><A
HREF="p1346.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>HOWTO Access Samba source code via CVS</TD
>Appendixes</TD
></TR
></TABLE
></DIV

69
docs/htmldocs/unix-permissions.html
View File

@ -9,12 +9,16 @@ 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="p1346.html"><LINK
REL="PREVIOUS"
TITLE="Hosting a Microsoft Distributed File System tree on Samba"
HREF="msdfs.html"><LINK
TITLE="Integrating MS Windows networks with Samba"
HREF="integrate-ms-networks.html"><LINK
REL="NEXT"
TITLE="Printing Support in Samba 2.2.x"
HREF="printing.html"></HEAD
TITLE="Configuring PAM for distributed but centrally
managed authentication"
HREF="pam.html"></HEAD
><BODY
CLASS="CHAPTER"
BGCOLOR="#FFFFFF"
@ -42,7 +46,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="msdfs.html"
HREF="integrate-ms-networks.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -56,7 +60,7 @@ WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="printing.html"
HREF="pam.html"
ACCESSKEY="N"
>Next</A
></TD
@ -71,15 +75,15 @@ CLASS="CHAPTER"
><A
NAME="UNIX-PERMISSIONS"
></A
>Chapter 5. UNIX Permission Bits and Windows NT Access Control Lists</H1
>Chapter 11. UNIX Permission Bits and Windows NT Access Control Lists</H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN580"
NAME="AEN1593"
></A
>5.1. Viewing and changing UNIX permissions using the NT
>11.1. Viewing and changing UNIX permissions using the NT
security dialogs</H1
><P
>New in the Samba 2.0.4 release is the ability for Windows
@ -116,9 +120,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN589"
NAME="AEN1602"
></A
>5.2. How to view file security on a Samba share</H1
>11.2. How to view file security on a Samba share</H1
><P
>From an NT 4.0 client, single-click with the right
mouse button on any file or directory in a Samba mounted
@ -186,9 +190,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN600"
NAME="AEN1613"
></A
>5.3. Viewing file ownership</H1
>11.3. Viewing file ownership</H1
><P
>Clicking on the <B
CLASS="COMMAND"
@ -280,9 +284,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN620"
NAME="AEN1633"
></A
>5.4. Viewing file or directory permissions</H1
>11.4. Viewing file or directory permissions</H1
><P
>The third button is the <B
CLASS="COMMAND"
@ -342,9 +346,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN635"
NAME="AEN1648"
></A
>5.4.1. File Permissions</H2
>11.4.1. File Permissions</H2
><P
>The standard UNIX user/group/world triple and
the corresponding "read", "write", "execute" permissions
@ -404,9 +408,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN649"
NAME="AEN1662"
></A
>5.4.2. Directory Permissions</H2
>11.4.2. Directory Permissions</H2
><P
>Directories on an NT NTFS file system have two
different sets of permissions. The first set of permissions
@ -436,9 +440,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN656"
NAME="AEN1669"
></A
>5.5. Modifying file or directory permissions</H1
>11.5. Modifying file or directory permissions</H1
><P
>Modifying file and directory permissions is as simple
as changing the displayed permissions in the dialog box, and
@ -534,9 +538,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN678"
NAME="AEN1691"
></A
>5.6. Interaction with the standard Samba create mask
>11.6. Interaction with the standard Samba create mask
parameters</H1
><P
>Note that with Samba 2.0.5 there are four new parameters
@ -811,9 +815,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN742"
NAME="AEN1755"
></A
>5.7. Interaction with the standard Samba file attribute
>11.7. Interaction with the standard Samba file attribute
mapping</H1
><P
>Samba maps some of the DOS attribute bits (such as "read
@ -870,7 +874,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="msdfs.html"
HREF="integrate-ms-networks.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -888,7 +892,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="printing.html"
HREF="pam.html"
ACCESSKEY="N"
>Next</A
></TD
@ -898,17 +902,22 @@ ACCESSKEY="N"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Hosting a Microsoft Distributed File System tree on Samba</TD
>Integrating MS Windows networks with Samba</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><A
HREF="p1346.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Printing Support in Samba 2.2.x</TD
>Configuring PAM for distributed but centrally
managed authentication</TD
></TR
></TABLE
></DIV

24
docs/htmldocs/wbinfo.1.html
View File

@ -37,12 +37,12 @@ NAME="AEN8"
><B
CLASS="COMMAND"
>wbinfo</B
> [-u] [-g] [-h name] [-i ip] [-n name] [-s sid] [-U uid] [-G gid] [-S sid] [-Y sid] [-t] [-m] [-r user] [-a user%password] [-A user%password]</P
> [-u] [-g] [-i ip] [-N netbios-name] [-n name] [-s sid] [-U uid] [-G gid] [-S sid] [-Y sid] [-t] [-m] [-r user] [-a user%password] [-A user%password] [-p]</P
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN26"
NAME="AEN27"
></A
><H2
>DESCRIPTION</H2
@ -79,7 +79,7 @@ CLASS="COMMAND"
><DIV
CLASS="REFSECT1"
><A
NAME="AEN37"
NAME="AEN38"
></A
><H2
>OPTIONS</H2
@ -123,13 +123,13 @@ CLASS="COMMAND"
>. </P
></DD
><DT
>-h name</DT
>-N name</DT
><DD
><P
>The <TT
CLASS="PARAMETER"
><I
>-h</I
>-N</I
></TT
> option
queries <B
@ -146,13 +146,13 @@ CLASS="PARAMETER"
</P
></DD
><DT
>-i ip</DT
>-I ip</DT
><DD
><P
>The <TT
CLASS="PARAMETER"
><I
>-i</I
>-I</I
></TT
> option
queries <B
@ -308,7 +308,7 @@ CLASS="COMMAND"
><DIV
CLASS="REFSECT1"
><A
NAME="AEN119"
NAME="AEN120"
></A
><H2
>EXIT STATUS</H2
@ -327,18 +327,18 @@ CLASS="COMMAND"
><DIV
CLASS="REFSECT1"
><A
NAME="AEN124"
NAME="AEN125"
></A
><H2
>VERSION</H2
><P
>This man page is correct for version 2.2 of
>This man page is correct for version 3.0 of
the Samba suite.</P
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN127"
NAME="AEN128"
></A
><H2
>SEE ALSO</H2
@ -356,7 +356,7 @@ CLASS="COMMAND"
><DIV
CLASS="REFSECT1"
><A
NAME="AEN132"
NAME="AEN133"
></A
><H2
>AUTHOR</H2

147
docs/htmldocs/winbind.html
View File

@ -9,12 +9,15 @@ 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="p1346.html"><LINK
REL="PREVIOUS"
TITLE="security = domain in Samba 2.x"
HREF="domain-security.html"><LINK
TITLE="Security levels"
HREF="securitylevels.html"><LINK
REL="NEXT"
TITLE="How to Configure Samba 2.2 as a Primary Domain Controller"
HREF="samba-pdc.html"></HEAD
TITLE="Passdb MySQL plugin"
HREF="pdb-mysql.html"></HEAD
><BODY
CLASS="CHAPTER"
BGCOLOR="#FFFFFF"
@ -42,7 +45,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="domain-security.html"
HREF="securitylevels.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -56,7 +59,7 @@ WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="samba-pdc.html"
HREF="pdb-mysql.html"
ACCESSKEY="N"
>Next</A
></TD
@ -71,15 +74,15 @@ CLASS="CHAPTER"
><A
NAME="WINBIND"
></A
>Chapter 10. Unified Logons between Windows NT and UNIX using Winbind</H1
>Chapter 16. Unified Logons between Windows NT and UNIX using Winbind</H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN1255"
NAME="AEN2249"
></A
>10.1. Abstract</H1
>16.1. Abstract</H1
><P
>Integration of UNIX and Microsoft Windows NT through
a unified logon has been considered a "holy grail" in heterogeneous
@ -104,9 +107,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN1259"
NAME="AEN2253"
></A
>10.2. Introduction</H1
>16.2. Introduction</H1
><P
>It is well known that UNIX and Microsoft Windows NT have
different models for representing user and group information and
@ -158,9 +161,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN1272"
NAME="AEN2266"
></A
>10.3. What Winbind Provides</H1
>16.3. What Winbind Provides</H1
><P
>Winbind unifies UNIX and Windows NT account management by
allowing a UNIX box to become a full member of a NT domain. Once
@ -200,9 +203,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN1279"
NAME="AEN2273"
></A
>10.3.1. Target Uses</H2
>16.3.1. Target Uses</H2
><P
>Winbind is targeted at organizations that have an
existing NT based domain infrastructure into which they wish
@ -224,9 +227,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN1283"
NAME="AEN2277"
></A
>10.4. How Winbind Works</H1
>16.4. How Winbind Works</H1
><P
>The winbind system is designed around a client/server
architecture. A long running <B
@ -244,9 +247,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN1288"
NAME="AEN2282"
></A
>10.4.1. Microsoft Remote Procedure Calls</H2
>16.4.1. Microsoft Remote Procedure Calls</H2
><P
>Over the last two years, efforts have been underway
by various Samba Team members to decode various aspects of
@ -270,9 +273,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN1292"
NAME="AEN2286"
></A
>10.4.2. Name Service Switch</H2
>16.4.2. Name Service Switch</H2
><P
>The Name Service Switch, or NSS, is a feature that is
present in many UNIX operating systems. It allows system
@ -350,9 +353,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN1308"
NAME="AEN2302"
></A
>10.4.3. Pluggable Authentication Modules</H2
>16.4.3. Pluggable Authentication Modules</H2
><P
>Pluggable Authentication Modules, also known as PAM,
is a system for abstracting authentication and authorization
@ -399,9 +402,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN1316"
NAME="AEN2310"
></A
>10.4.4. User and Group ID Allocation</H2
>16.4.4. User and Group ID Allocation</H2
><P
>When a user or group is created under Windows NT
is it allocated a numerical relative identifier (RID). This is
@ -425,9 +428,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN1320"
NAME="AEN2314"
></A
>10.4.5. Result Caching</H2
>16.4.5. Result Caching</H2
><P
>An active system can generate a lot of user and group
name lookups. To reduce the network cost of these lookups winbind
@ -448,9 +451,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN1323"
NAME="AEN2317"
></A
>10.5. Installation and Configuration</H1
>16.5. Installation and Configuration</H1
><P
>Many thanks to John Trostel <A
HREF="mailto:jtrostel@snapserver.com"
@ -475,9 +478,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN1330"
NAME="AEN2324"
></A
>10.5.1. Introduction</H2
>16.5.1. Introduction</H2
><P
>This HOWTO describes the procedures used to get winbind up and
running on my RedHat 7.1 system. Winbind is capable of providing access
@ -534,9 +537,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN1343"
NAME="AEN2337"
></A
>10.5.2. Requirements</H2
>16.5.2. Requirements</H2
><P
>If you have a samba configuration file that you are currently
using... <SPAN
@ -574,7 +577,7 @@ CLASS="FILENAME"
> back to the original state they were in if
you get frustrated with the way things are going. ;-)</P
><P
>The latest version of SAMBA (version 2.2.2 as of this writing), now
>The latest version of SAMBA (version 3.0 as of this writing), now
includes a functioning winbindd daemon. Please refer to the
<A
HREF="http://samba.org/"
@ -604,9 +607,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN1357"
NAME="AEN2351"
></A
>10.5.3. Testing Things Out</H2
>16.5.3. Testing Things Out</H2
><P
>Before starting, it is probably best to kill off all the SAMBA
related daemons running on your server. Kill off all <B
@ -649,9 +652,9 @@ CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="AEN1368"
NAME="AEN2362"
></A
>10.5.3.1. Configure and compile SAMBA</H3
>16.5.3.1. Configure and compile SAMBA</H3
><P
>The configuration and compilation of SAMBA is pretty straightforward.
The first three steps may not be necessary depending upon
@ -715,9 +718,9 @@ CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="AEN1387"
NAME="AEN2381"
></A
>10.5.3.2. Configure <TT
>16.5.3.2. Configure <TT
CLASS="FILENAME"
>nsswitch.conf</TT
> and the
@ -820,9 +823,9 @@ CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="AEN1420"
NAME="AEN2414"
></A
>10.5.3.3. Configure smb.conf</H3
>16.5.3.3. Configure smb.conf</H3
><P
>Several parameters are needed in the smb.conf file to control
the behavior of <B
@ -895,9 +898,9 @@ CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="AEN1436"
NAME="AEN2430"
></A
>10.5.3.4. Join the SAMBA server to the PDC domain</H3
>16.5.3.4. Join the SAMBA server to the PDC domain</H3
><P
>Enter the following command to make the SAMBA server join the
PDC domain, where <TT
@ -919,7 +922,7 @@ CLASS="PROMPT"
>root#</TT
> <B
CLASS="COMMAND"
>/usr/local/samba/bin/net rpc join -s PDC -U Administrator</B
>/usr/local/samba/bin/net rpc join -S PDC -U Administrator</B
></P
><P
>The proper response to the command should be: "Joined the domain
@ -941,9 +944,9 @@ CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="AEN1447"
NAME="AEN2441"
></A
>10.5.3.5. Start up the winbindd daemon and test it!</H3
>16.5.3.5. Start up the winbindd daemon and test it!</H3
><P
>Eventually, you will want to modify your smb startup script to
automatically invoke the winbindd daemon when the other parts of
@ -1064,17 +1067,17 @@ CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="AEN1483"
NAME="AEN2477"
></A
>10.5.3.6. Fix the init.d startup scripts</H3
>16.5.3.6. Fix the init.d startup scripts</H3
><DIV
CLASS="SECT4"
><H4
CLASS="SECT4"
><A
NAME="AEN1485"
NAME="AEN2479"
></A
>10.5.3.6.1. Linux</H4
>16.5.3.6.1. Linux</H4
><P
>The <B
CLASS="COMMAND"
@ -1168,9 +1171,9 @@ CLASS="SECT4"
><H4
CLASS="SECT4"
><A
NAME="AEN1502"
NAME="AEN2496"
></A
>10.5.3.6.2. Solaris</H4
>16.5.3.6.2. Solaris</H4
><P
>On solaris, you need to modify the
<TT
@ -1239,9 +1242,9 @@ CLASS="SECT4"
><H4
CLASS="SECT4"
><A
NAME="AEN1509"
NAME="AEN2503"
></A
>10.5.3.6.3. Restarting</H4
>16.5.3.6.3. Restarting</H4
><P
>If you restart the <B
CLASS="COMMAND"
@ -1263,9 +1266,9 @@ CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="AEN1515"
NAME="AEN2509"
></A
>10.5.3.7. Configure Winbind and PAM</H3
>16.5.3.7. Configure Winbind and PAM</H3
><P
>If you have made it this far, you know that winbindd and samba are working
together. If you want to use winbind to provide authentication for other
@ -1321,9 +1324,9 @@ CLASS="SECT4"
><H4
CLASS="SECT4"
><A
NAME="AEN1532"
NAME="AEN2526"
></A
>10.5.3.7.1. Linux/FreeBSD-specific PAM configuration</H4
>16.5.3.7.1. Linux/FreeBSD-specific PAM configuration</H4
><P
>The <TT
CLASS="FILENAME"
@ -1450,9 +1453,9 @@ CLASS="SECT4"
><H4
CLASS="SECT4"
><A
NAME="AEN1565"
NAME="AEN2559"
></A
>10.5.3.7.2. Solaris-specific configuration</H4
>16.5.3.7.2. Solaris-specific configuration</H4
><P
>The /etc/pam.conf needs to be changed. I changed this file so that my Domain
users can logon both locally as well as telnet.The following are the changes
@ -1537,9 +1540,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN1572"
NAME="AEN2566"
></A
>10.6. Limitations</H1
>16.6. Limitations</H1
><P
>Winbind has a number of limitations in its current
released version that we hope to overcome in future
@ -1578,9 +1581,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN1582"
NAME="AEN2576"
></A
>10.7. Conclusion</H1
>16.7. Conclusion</H1
><P
>The winbind system, through the use of the Name Service
Switch, Pluggable Authentication Modules, and appropriate
@ -1606,7 +1609,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="domain-security.html"
HREF="securitylevels.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -1624,7 +1627,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="samba-pdc.html"
HREF="pdb-mysql.html"
ACCESSKEY="N"
>Next</A
></TD
@ -1634,17 +1637,21 @@ ACCESSKEY="N"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>security = domain in Samba 2.x</TD
>Security levels</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><A
HREF="p1346.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>How to Configure Samba 2.2 as a Primary Domain Controller</TD
>Passdb MySQL plugin</TD
></TR
></TABLE
></DIV

59
docs/htmldocs/winbindd.8.html
View File

@ -38,12 +38,12 @@ NAME="AEN8"
><B
CLASS="COMMAND"
>winbindd</B
> [-i] [-d &lt;debug level&gt;] [-s &lt;smb config file&gt;]</P
> [-i] [-B] [-d &lt;debug level&gt;] [-s &lt;smb config file&gt;] [-n]</P
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN14"
NAME="AEN16"
></A
><H2
>DESCRIPTION</H2
@ -192,7 +192,7 @@ CLASS="FILENAME"
><DIV
CLASS="REFSECT1"
><A
NAME="AEN57"
NAME="AEN59"
></A
><H2
>OPTIONS</H2
@ -225,13 +225,46 @@ CLASS="COMMAND"
>winbindd</B
> is required. </P
></DD
><DT
>-n</DT
><DD
><P
>Disable caching. This means winbindd will
always have to wait for a response from the domain controller
before it can respond to a client and this thus makes things
slower. The results will however be more accurate, since
results from the cache might not be up-to-date. This
might also temporarily hang winbindd if the DC doesn't respond.
</P
></DD
><DT
>-B</DT
><DD
><P
>Dual daemon mode. This means winbindd will run
as 2 threads. The first will answer all requests from the cache,
thus making responses to clients faster. The other will
update the cache for the query that the first has just responded.
Advantage of this is that responses are accurate and fast.
</P
></DD
><DT
>-s|--conf=smb.conf</DT
><DD
><P
>Specifies the location of the all-important
<TT
CLASS="FILENAME"
>smb.conf</TT
> file. </P
></DD
></DL
></DIV
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN70"
NAME="AEN85"
></A
><H2
>NAME AND ID RESOLUTION</H2
@ -262,7 +295,7 @@ CLASS="COMMAND"
><DIV
CLASS="REFSECT1"
><A
NAME="AEN76"
NAME="AEN91"
></A
><H2
>CONFIGURATION</H2
@ -402,7 +435,7 @@ CLASS="PARAMETER"
><DIV
CLASS="REFSECT1"
><A
NAME="AEN118"
NAME="AEN133"
></A
><H2
>EXAMPLE SETUP</H2
@ -553,7 +586,7 @@ CLASS="COMMAND"
><DIV
CLASS="REFSECT1"
><A
NAME="AEN157"
NAME="AEN172"
></A
><H2
>NOTES</H2
@ -611,7 +644,7 @@ CLASS="COMMAND"
><DIV
CLASS="REFSECT1"
><A
NAME="AEN173"
NAME="AEN188"
></A
><H2
>SIGNALS</H2
@ -662,7 +695,7 @@ CLASS="COMMAND"
><DIV
CLASS="REFSECT1"
><A
NAME="AEN190"
NAME="AEN205"
></A
><H2
>FILES</H2
@ -738,18 +771,18 @@ CLASS="FILENAME"
><DIV
CLASS="REFSECT1"
><A
NAME="AEN219"
NAME="AEN234"
></A
><H2
>VERSION</H2
><P
>This man page is correct for version 2.2 of
>This man page is correct for version 3.0 of
the Samba suite.</P
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN222"
NAME="AEN237"
></A
><H2
>SEE ALSO</H2
@ -777,7 +810,7 @@ TARGET="_top"
><DIV
CLASS="REFSECT1"
><A
NAME="AEN229"
NAME="AEN244"
></A
><H2
>AUTHOR</H2

4
docs/manpages/findsmb.1
View File

@ -3,7 +3,7 @@
.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
.\" Please send any bug reports, improvements, comments, patches,
.\" etc. to Steve Cheng <steve@ggi-project.org>.
.TH "FINDSMB" "1" "01 October 2002" "" ""
.TH "FINDSMB" "1" "05 November 2002" "" ""
.SH NAME
findsmb \- list info about machines that respond to SMB name queries on a subnet
.SH SYNOPSIS
@ -68,7 +68,7 @@ IP ADDR NETBIOS NAME WORKGROUP/OS/VERSION
.fi
.SH "VERSION"
.PP
This man page is correct for version 2.2 of
This man page is correct for version 3.0 of
the Samba suite.
.SH "SEE ALSO"
.PP

2
docs/manpages/lmhosts.5
View File

@ -3,7 +3,7 @@
.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
.\" Please send any bug reports, improvements, comments, patches,
.\" etc. to Steve Cheng <steve@ggi-project.org>.
.TH "LMHOSTS" "5" "01 October 2002" "" ""
.TH "LMHOSTS" "5" "05 November 2002" "" ""
.SH NAME
lmhosts \- The Samba NetBIOS hosts file
.SH SYNOPSIS

8
docs/manpages/nmbd.8
View File

@ -3,12 +3,12 @@
.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
.\" Please send any bug reports, improvements, comments, patches,
.\" etc. to Steve Cheng <steve@ggi-project.org>.
.TH "NMBD" "8" "01 October 2002" "" ""
.TH "NMBD" "8" "05 November 2002" "" ""
.SH NAME
nmbd \- NetBIOS name server to provide NetBIOS over IP naming services to clients
.SH SYNOPSIS
\fBnmbd\fR [ \fB-D\fR ] [ \fB-a\fR ] [ \fB-i\fR ] [ \fB-o\fR ] [ \fB-P\fR ] [ \fB-h\fR ] [ \fB-V\fR ] [ \fB-d <debug level>\fR ] [ \fB-H <lmhosts file>\fR ] [ \fB-l <log directory>\fR ] [ \fB-n <primary netbios name>\fR ] [ \fB-p <port number>\fR ] [ \fB-s <configuration file>\fR ]
\fBnmbd\fR [ \fB-D\fR ] [ \fB-a\fR ] [ \fB-i\fR ] [ \fB-o\fR ] [ \fB-h\fR ] [ \fB-V\fR ] [ \fB-d <debug level>\fR ] [ \fB-H <lmhosts file>\fR ] [ \fB-l <log directory>\fR ] [ \fB-n <primary netbios name>\fR ] [ \fB-p <port number>\fR ] [ \fB-s <configuration file>\fR ]
.SH "DESCRIPTION"
.PP
@ -17,7 +17,7 @@ This program is part of the Samba suite.
\fBnmbd\fR is a server that understands
and can reply to NetBIOS over IP name service requests, like
those produced by SMB/CIFS clients such as Windows 95/98/ME,
Windows NT, Windows 2000, and LanManager clients. It also
Windows NT, Windows 2000, Windows XP and LanManager clients. It also
participates in the browsing protocols which make up the
Windows "Network Neighborhood" view.
.PP
@ -226,7 +226,7 @@ to allow transient problems to be diagnosed, whilst still running
at a normally low log level.
.SH "VERSION"
.PP
This man page is correct for version 2.2 of
This man page is correct for version 3.0 of
the Samba suite.
.SH "SEE ALSO"
.PP

11
docs/manpages/nmblookup.1
View File

@ -3,12 +3,12 @@
.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
.\" Please send any bug reports, improvements, comments, patches,
.\" etc. to Steve Cheng <steve@ggi-project.org>.
.TH "NMBLOOKUP" "1" "01 October 2002" "" ""
.TH "NMBLOOKUP" "1" "05 November 2002" "" ""
.SH NAME
nmblookup \- NetBIOS over TCP/IP client used to lookup NetBIOS names
.SH SYNOPSIS
\fBnmblookup\fR [ \fB-M\fR ] [ \fB-R\fR ] [ \fB-S\fR ] [ \fB-r\fR ] [ \fB-A\fR ] [ \fB-h\fR ] [ \fB-B <broadcast address>\fR ] [ \fB-U <unicast address>\fR ] [ \fB-d <debug level>\fR ] [ \fB-s <smb config file>\fR ] [ \fB-i <NetBIOS scope>\fR ] [ \fB-T\fR ] \fBname\fR
\fBnmblookup\fR [ \fB-M\fR ] [ \fB-R\fR ] [ \fB-S\fR ] [ \fB-r\fR ] [ \fB-A\fR ] [ \fB-h\fR ] [ \fB-B <broadcast address>\fR ] [ \fB-U <unicast address>\fR ] [ \fB-d <debug level>\fR ] [ \fB-s <smb config file>\fR ] [ \fB-i <NetBIOS scope>\fR ] [ \fB-T\fR ] [ \fB-f\fR ] \fBname\fR
.SH "DESCRIPTION"
.PP
@ -110,6 +110,11 @@ DNS name, and printed out before each
pair that is the normal output.
.TP
\fB-f\fR
Show which flags apply to the name that has been looked up. Possible
answers are zero or more of: Response, Authoritative,
Truncated, Recursion_Desired, Recursion_Available, Broadcast.
.TP
\fBname\fR
This is the NetBIOS name being queried. Depending
upon the previous options this may be a NetBIOS name or IP address.
@ -134,7 +139,7 @@ would query the WINS server samba.org for the domain
master browser (1B name type) for the IRIX workgroup.
.SH "VERSION"
.PP
This man page is correct for version 2.2 of
This man page is correct for version 3.0 of
the Samba suite.
.SH "SEE ALSO"
.PP

72
docs/manpages/pdbedit.8
View File

@ -3,12 +3,12 @@
.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
.\" Please send any bug reports, improvements, comments, patches,
.\" etc. to Steve Cheng <steve@ggi-project.org>.
.TH "PDBEDIT" "8" "01 October 2002" "" ""
.TH "PDBEDIT" "8" "05 November 2002" "" ""
.SH NAME
pdbedit \- manage the SAM database
.SH SYNOPSIS
\fBpdbedit\fR [ \fB-l\fR ] [ \fB-v\fR ] [ \fB-w\fR ] [ \fB-u username\fR ] [ \fB-f fullname\fR ] [ \fB-h homedir\fR ] [ \fB-d drive\fR ] [ \fB-s script\fR ] [ \fB-p profile\fR ] [ \fB-a\fR ] [ \fB-m\fR ] [ \fB-x\fR ] [ \fB-i passdb-backend\fR ] [ \fB-e passdb-backend\fR ] [ \fB-b passdb-backend\fR ] [ \fB-D debuglevel\fR ]
\fBpdbedit\fR [ \fB-l\fR ] [ \fB-v\fR ] [ \fB-w\fR ] [ \fB-u username\fR ] [ \fB-f fullname\fR ] [ \fB-h homedir\fR ] [ \fB-D drive\fR ] [ \fB-S script\fR ] [ \fB-p profile\fR ] [ \fB-a\fR ] [ \fB-m\fR ] [ \fB-x\fR ] [ \fB-i passdb-backend\fR ] [ \fB-e passdb-backend\fR ] [ \fB-b passdb-backend\fR ] [ \fB-d debuglevel\fR ] [ \fB-s configfile\fR ] [ \fB-P account-policy\fR ] [ \fB-V value\fR ]
.SH "DESCRIPTION"
.PP
@ -108,14 +108,14 @@ directory network path.
Example: \fB-h "\\\\\\\\BERSERKER\\\\sorce"\fR
.TP
\fB-d drive\fR
\fB-D drive\fR
This option can be used while adding or
modifing a user account. It will specify the windows drive
letter to be used to map the home directory.
Example: \fB-d "H:"\fR
.TP
\fB-s script\fR
\fB-S script\fR
This option can be used while adding or
modifing a user account. It will specify the user's logon
script path.
@ -181,6 +181,70 @@ Example: \fBpdbedit -e smbpasswd:/root/samba-users.backup\fR
Use a different default passdb backend.
Example: \fBpdbedit -b xml:/root/pdb-backup.xml -l\fR
.TP
\fB-P account-policy\fR
Display an account policy
Valid policies are: minimum password age, reset count minutes, disconnect time,
user must logon to change password, password history, lockout duration, min password length,
maximum password age and bad lockout attempt.
Example: \fBpdbedit -P "bad lockout attempt"\fR
.nf
account policy value for bad lockout attempt is 0
.fi
.TP
\fB-V account-policy-value\fR
Sets an account policy to a specified value.
This option may only be used in conjunction
with the \fI-P\fR option.
Example: \fBpdbedit -P "bad lockout attempt" -V 3\fR
.nf
account policy value for bad lockout attempt was 0
account policy value for bad lockout attempt is now 3
.fi
.TP
\fB-d|--debug=debuglevel\fR
\fIdebuglevel\fR is an integer
from 0 to 10. The default value if this parameter is
not specified is zero.
The higher this value, the more detail will be
logged to the log files about the activities of the
server. At level 0, only critical errors and serious
warnings will be logged. Level 1 is a reasonable level for
day to day running - it generates a small amount of
information about operations carried out.
Levels above 1 will generate considerable
amounts of log data, and should only be used when
investigating a problem. Levels above 3 are designed for
use only by developers and generate HUGE amounts of log
data, most of which is extremely cryptic.
Note that specifying this parameter here will
override the log
level file.
.TP
\fB-h|--help\fR
Print a summary of command line options.
.TP
\fB-s <configuration file>\fR
The file specified contains the
configuration details required by the server. The
information in this file includes server-specific
information such as what printcap file to use, as well
as descriptions of all the services that the server is
to provide. See \fIsmb.conf(5)\fR for more information.
The default configuration file name is determined at
compile time.
.SH "NOTES"
.PP
This command may be used only by root.

25
docs/manpages/rpcclient.1
View File

@ -3,7 +3,7 @@
.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
.\" Please send any bug reports, improvements, comments, patches,
.\" etc. to Steve Cheng <steve@ggi-project.org>.
.TH "RPCCLIENT" "1" "01 October 2002" "" ""
.TH "RPCCLIENT" "1" "05 November 2002" "" ""
.SH NAME
rpcclient \- tool for executing client side MS-RPC functions
.SH SYNOPSIS
@ -48,9 +48,26 @@ execute semicolon separated commands (listed
below))
.TP
\fB-d|--debug=debuglevel\fR
set the debuglevel. Debug level 0 is the lowest
and 100 being the highest. This should be set to 100 if you are
planning on submitting a bug report to the Samba team (see \fIBUGS.txt\fR).
\fIdebuglevel\fR is an integer
from 0 to 10. The default value if this parameter is
not specified is zero.
The higher this value, the more detail will be
logged to the log files about the activities of the
server. At level 0, only critical errors and serious
warnings will be logged. Level 1 is a reasonable level for
day to day running - it generates a small amount of
information about operations carried out.
Levels above 1 will generate considerable
amounts of log data, and should only be used when
investigating a problem. Levels above 3 are designed for
use only by developers and generate HUGE amounts of log
data, most of which is extremely cryptic.
Note that specifying this parameter here will
override the log
level file.
.TP
\fB-h|--help\fR
Print a summary of command line options.

2
docs/manpages/samba.7
View File

@ -3,7 +3,7 @@
.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
.\" Please send any bug reports, improvements, comments, patches,
.\" etc. to Steve Cheng <steve@ggi-project.org>.
.TH "SAMBA" "7" "01 October 2002" "" ""
.TH "SAMBA" "7" "05 November 2002" "" ""
.SH NAME
SAMBA \- A Windows SMB/CIFS fileserver for UNIX
.SH SYNOPSIS

152
docs/manpages/smb.conf.5
View File

@ -3,7 +3,7 @@
.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
.\" Please send any bug reports, improvements, comments, patches,
.\" etc. to Steve Cheng <steve@ggi-project.org>.
.TH "SMB.CONF" "5" "03 October 2002" "" ""
.TH "SMB.CONF" "5" "05 November 2002" "" ""
.SH NAME
smb.conf \- The configuration file for the Samba suite
.SH "SYNOPSIS"
@ -303,19 +303,6 @@ These substitutions are mostly noted in the descriptions below,
but there are some general substitutions which apply whenever they
might be relevant. These are:
.TP
\fB%S\fR
the name of the current service, if any.
.TP
\fB%P\fR
the root directory of the current service,
if any.
.TP
\fB%u\fR
user name of the current service, if any.
.TP
\fB%g\fR
primary group name of %u.
.TP
\fB%U\fR
session user name (the user name that the client
wanted, not necessarily the same as the one they got).
@ -323,13 +310,6 @@ wanted, not necessarily the same as the one they got).
\fB%G\fR
primary group name of %U.
.TP
\fB%H\fR
the home directory of the user given
by %u.
.TP
\fB%v\fR
the Samba version.
.TP
\fB%h\fR
the Internet hostname that Samba is running
on.
@ -349,17 +329,6 @@ on port 445, as clients no longer send this information
\fB%M\fR
the Internet name of the client machine.
.TP
\fB%N\fR
the name of your NIS home directory server.
This is obtained from your NIS auto.map entry. If you have
not compiled Samba with the \fB--with-automount\fR
option then this value will be the same as %L.
.TP
\fB%p\fR
the path of the service's home directory,
obtained from your NIS auto.map entry. The NIS auto.map entry
is split up as "%N:%p".
.TP
\fB%R\fR
the selected protocol level after
protocol negotiation. It can be one of CORE, COREPLUS,
@ -384,10 +353,44 @@ The IP address of the client machine.
\fB%T\fR
the current date and time.
.TP
\fB%D\fR
Name of the domain or workgroup of the current user.
.TP
\fB%$(\fIenvvar\fB)\fR
The value of the environment variable
\fIenvar\fR.
.PP
The following substitutes apply only to some configuration options(only those
that are used when a connection has been established):
.TP
\fB%S\fR
the name of the current service, if any.
.TP
\fB%P\fR
the root directory of the current service,
if any.
.TP
\fB%u\fR
user name of the current service, if any.
.TP
\fB%g\fR
primary group name of %u.
.TP
\fB%H\fR
the home directory of the user given
by %u.
.TP
\fB%N\fR
the name of your NIS home directory server.
This is obtained from your NIS auto.map entry. If you have
not compiled Samba with the \fB--with-automount\fR
option then this value will be the same as %L.
.TP
\fB%p\fR
the path of the service's home directory,
obtained from your NIS auto.map entry. The NIS auto.map entry
is split up as "%N:%p".
.PP
There are some quite creative things that can be done
with these substitutions and other smb.conf options.
.SH "NAME MANGLING"
@ -433,7 +436,7 @@ case. This option can be use with "preserve case = yes"
to permit long filenames to retain their case, while short names
are lowercased. Default \fByes\fR.
.PP
By default, Samba 2.2 has the same semantics as a Windows
By default, Samba 3.0 has the same semantics as a Windows
NT server, in that it is case insensitive but case preserving.
.SH "NOTE ABOUT USERNAME/PASSWORD VALIDATION"
.PP
@ -685,6 +688,9 @@ each parameter for details. Note that some are synonyms.
\fIldap passwd sync\fR
.TP 0.2i
\(bu
\fIldap trust ids\fR
.TP 0.2i
\(bu
\fIlm announce\fR
.TP 0.2i
\(bu
@ -1713,10 +1719,10 @@ Example: \fBannounce as = Win95\fR
\fBannounce version (G)\fR
This specifies the major and minor version numbers
that nmbd will use when announcing itself as a server. The default
is 4.2. Do not change this parameter unless you have a specific
is 4.9. Do not change this parameter unless you have a specific
need to set a Samba server to be a downlevel server.
Default: \fBannounce version = 4.5\fR
Default: \fBannounce version = 4.9\fR
Example: \fBannounce version = 2.0\fR
.TP
@ -1806,12 +1812,12 @@ to obtain a byte range lock on a region of an open file, and the
request has a time limit associated with it.
If this parameter is set and the lock range requested
cannot be immediately satisfied, Samba 2.2 will internally
cannot be immediately satisfied, samba will internally
queue the lock request, and periodically attempt to obtain
the lock until the timeout period expires.
If this parameter is set to no, then
Samba 2.2 will behave as previous versions of Samba would and
samba will behave as previous versions of Samba would and
will fail the lock request immediately if the lock range
cannot be obtained.
@ -2069,7 +2075,7 @@ effect.
Default: \fBdebug pid = no\fR
.TP
\fBdebug timestamp (G)\fR
Samba 2.2 debug log messages are timestamped
Samba debug log messages are timestamped
by default. If you are running at a high \fIdebug level\fR these timestamps
can be distracting. This boolean parameter allows timestamping
to be turned off.
@ -2933,7 +2939,7 @@ this by trying to log in as your guest user (perhaps by using the
\fBsu -\fR command) and trying to print using the
system print command such as \fBlpr(1)\fR or \fB lp(1)\fR.
This paramater does not accept % macros, because
This parameter does not accept % macros, because
many parts of the system require this value to be
constant for correct operation.
@ -3391,20 +3397,25 @@ The \fIldap ssl\fR can be set to one of three values:
.RS
.TP 0.2i
\(bu
\fIOn\fR = Always use SSL when contacting the
\fIldap server\fR.
.TP 0.2i
\(bu
\fIOff\fR = Never use SSL when querying the directory.
.TP 0.2i
\(bu
\fIStart_tls\fR = Use the LDAPv3 StartTLS extended operation
(RFC2830) for communicating with the directory server.
.TP 0.2i
\(bu
\fIOn\fR =
Use SSL on the ldaps port when contacting the
\fIldap server\fR. Only
available when the backwards-compatiblity \fB --with-ldapsam\fR option is specified
to configure. See \fIpassdb backend\fR
.RE
Default : \fBldap ssl = on\fR
Default : \fBldap ssl = start_tls\fR
.TP
\fBldap suffix (G)\fR
Specifies where user and machine accounts are added to the tree. Can be overriden by \fBldap user suffix\fR and \fBldap machine suffix\fR. It also used as the base dn for all ldap searches.
Default : \fBnone\fR
.TP
\fBldap user suffix (G)\fR
@ -3440,6 +3451,23 @@ The \fIldap passwd sync\fR can be set to one of three values:
Default : \fBldap passwd sync = no\fR
.TP
\fBldap trust ids (G)\fR
Normally, Samba validates each entry
in the LDAP server against getpwnam(). This allows
LDAP to be used for Samba with the unix system using
NIS (for example) and also ensures that Samba does not
present accounts that do not otherwise exist.
This option is used to disable this functionality, and
instead to rely on the presence of the appropriate
attributes in LDAP directly, which can result in a
significant performance boost in some situations.
Setting this option to yes effectivly assumes
that the local machine is running \fBnss_ldap\fR against the
same LDAP server.
Default: \fBldap trust ids = No\fR
.TP
\fBlevel2 oplocks (S)\fR
This parameter controls whether Samba supports
level2 (read-only) oplocks on a share.
@ -4056,11 +4084,21 @@ a better algorithm (generates less collisions) in the names.
However, many Win32 applications store the mangled names and so
changing to the new algorithm must not be done
lightly as these applications may break unless reinstalled.
New installations of Samba may set the default to hash2.
Default: \fBmangling method = hash\fR
Default: \fBmangling method = hash2\fR
Example: \fBmangling method = hash2\fR
Example: \fBmangling method = hash\fR
.TP
\fBmangle prefix (G)\fR
controls the number of prefix
characters from the original name used when generating
the mangled names. A larger value will give a weaker
hash and therefore more name collisions. The minimum
value is 1 and the maximum value is 6.
Default: \fBmangle prefix = 1\fR
Example: \fBmangle prefix = 4\fR
.TP
\fBmangled stack (G)\fR
This parameter controls the number of mangled names
@ -4868,7 +4906,18 @@ backend. Takes an LDAP URL as an optional argument (defaults to
backend, with non unix account support. Takes an LDAP URL as an optional argument (defaults to
\fBldap://localhost\fR)
See also \fInon unix account range\fR
Note: In this module, any account
without a matching POSIX account is regarded
as 'non unix'.
See also \fInon unix account
range\fR
LDAP connections should be secured where
possible. This may be done using either
Start-TLS (see \fIldap ssl\fR) or by
specifying \fIldaps://\fR in
the URL argument.
.TP 0.2i
\(bu
\fBnisplussam\fR - The NIS+ based passdb backend. Takes name NIS domain as an optional argument. Only works with sun NIS+ servers.
@ -6553,7 +6602,8 @@ Example: \fBtotal print jobs = 5000\fR
.TP
\fBunicode (G)\fR
Specifies whether Samba should try
to use unicode on the wire by default.
to use unicode on the wire by default. Note: This does NOT
mean that samba will assume that the unix machine uses unicode!
Default: \fBunicode = yes\fR
.TP
@ -6563,6 +6613,8 @@ Samba runs on uses. Samba needs to know this in order to be able to
convert text to the charsets other SMB clients use.
Default: \fBunix charset = ASCII\fR
Example: \fBunix charset = UTF8\fR
.TP
\fBunix extensions(G)\fR
This boolean parameter controls whether Samba
@ -7313,7 +7365,7 @@ sections. In particular, ensure that the permissions on spool
directories are correct.
.SH "VERSION"
.PP
This man page is correct for version 2.2 of
This man page is correct for version 3.0 of
the Samba suite.
.SH "SEE ALSO"
.PP

4
docs/manpages/smbclient.1
View File

@ -3,12 +3,12 @@
.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
.\" Please send any bug reports, improvements, comments, patches,
.\" etc. to Steve Cheng <steve@ggi-project.org>.
.TH "SMBCLIENT" "1" "01 October 2002" "" ""
.TH "SMBCLIENT" "1" "05 November 2002" "" ""
.SH NAME
smbclient \- ftp-like client to access SMB/CIFS resources on servers
.SH SYNOPSIS
\fBsmbclient\fR \fBservicename\fR [ \fBpassword\fR ] [ \fB-b <buffer size>\fR ] [ \fB-d debuglevel\fR ] [ \fB-D Directory\fR ] [ \fB-U username\fR ] [ \fB-W workgroup\fR ] [ \fB-M <netbios name>\fR ] [ \fB-m maxprotocol\fR ] [ \fB-A authfile\fR ] [ \fB-N\fR ] [ \fB-l logfile\fR ] [ \fB-L <netbios name>\fR ] [ \fB-I destinationIP\fR ] [ \fB-E <terminal code>\fR ] [ \fB-c <command string>\fR ] [ \fB-i scope\fR ] [ \fB-O <socket options>\fR ] [ \fB-p port\fR ] [ \fB-R <name resolve order>\fR ] [ \fB-s <smb config file>\fR ] [ \fB-T<c|x>IXFqgbNan\fR ]
\fBsmbclient\fR \fBservicename\fR [ \fBpassword\fR ] [ \fB-b <buffer size>\fR ] [ \fB-d debuglevel\fR ] [ \fB-D Directory\fR ] [ \fB-U username\fR ] [ \fB-W workgroup\fR ] [ \fB-M <netbios name>\fR ] [ \fB-m maxprotocol\fR ] [ \fB-A authfile\fR ] [ \fB-N\fR ] [ \fB-l logfile\fR ] [ \fB-L <netbios name>\fR ] [ \fB-I destinationIP\fR ] [ \fB-E\fR ] [ \fB-c <command string>\fR ] [ \fB-i scope\fR ] [ \fB-O <socket options>\fR ] [ \fB-p port\fR ] [ \fB-R <name resolve order>\fR ] [ \fB-s <smb config file>\fR ] [ \fB-T<c|x>IXFqgbNan\fR ]
.SH "DESCRIPTION"
.PP

4
docs/manpages/smbpasswd.5
View File

@ -3,7 +3,7 @@
.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
.\" Please send any bug reports, improvements, comments, patches,
.\" etc. to Steve Cheng <steve@ggi-project.org>.
.TH "SMBPASSWD" "5" "01 October 2002" "" ""
.TH "SMBPASSWD" "5" "05 November 2002" "" ""
.SH NAME
smbpasswd \- The Samba encrypted password file
.SH SYNOPSIS
@ -135,7 +135,7 @@ in seconds since the epoch (1970) that the last change was made.
All other colon separated fields are ignored at this time.
.SH "VERSION"
.PP
This man page is correct for version 2.2 of
This man page is correct for version 3.0 of
the Samba suite.
.SH "SEE ALSO"
.PP

26
docs/manpages/vfstest.1
View File

@ -3,7 +3,7 @@
.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
.\" Please send any bug reports, improvements, comments, patches,
.\" etc. to Steve Cheng <steve@ggi-project.org>.
.TH "VFSTEST" "1" "01 October 2002" "" ""
.TH "VFSTEST" "1" "05 November 2002" "" ""
.SH NAME
vfstest \- tool for testing samba VFS modules
.SH SYNOPSIS
@ -25,10 +25,26 @@ Execute the specified (colon-seperated) commands.
See below for the commands that are available.
.TP
\fB-d|--debug=debuglevel\fR
set the debuglevel. Debug level 0 is the lowest
and 100 being the highest. This should be set to 100 if you are
planning on submitting a bug report to the Samba team (see
\fIBUGS.txt\fR).
\fIdebuglevel\fR is an integer
from 0 to 10. The default value if this parameter is
not specified is zero.
The higher this value, the more detail will be
logged to the log files about the activities of the
server. At level 0, only critical errors and serious
warnings will be logged. Level 1 is a reasonable level for
day to day running - it generates a small amount of
information about operations carried out.
Levels above 1 will generate considerable
amounts of log data, and should only be used when
investigating a problem. Levels above 3 are designed for
use only by developers and generate HUGE amounts of log
data, most of which is extremely cryptic.
Note that specifying this parameter here will
override the log
level file.
.TP
\fB-h|--help\fR
Print a summary of command line options.

14
docs/manpages/wbinfo.1
View File

@ -3,12 +3,12 @@
.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
.\" Please send any bug reports, improvements, comments, patches,
.\" etc. to Steve Cheng <steve@ggi-project.org>.
.TH "WBINFO" "1" "01 October 2002" "" ""
.TH "WBINFO" "1" "05 November 2002" "" ""
.SH NAME
wbinfo \- Query information from winbind daemon
.SH SYNOPSIS
\fBwbinfo\fR [ \fB-u\fR ] [ \fB-g\fR ] [ \fB-h name\fR ] [ \fB-i ip\fR ] [ \fB-n name\fR ] [ \fB-s sid\fR ] [ \fB-U uid\fR ] [ \fB-G gid\fR ] [ \fB-S sid\fR ] [ \fB-Y sid\fR ] [ \fB-t\fR ] [ \fB-m\fR ] [ \fB-r user\fR ] [ \fB-a user%password\fR ] [ \fB-A user%password\fR ]
\fBwbinfo\fR [ \fB-u\fR ] [ \fB-g\fR ] [ \fB-i ip\fR ] [ \fB-N netbios-name\fR ] [ \fB-n name\fR ] [ \fB-s sid\fR ] [ \fB-U uid\fR ] [ \fB-G gid\fR ] [ \fB-S sid\fR ] [ \fB-Y sid\fR ] [ \fB-t\fR ] [ \fB-m\fR ] [ \fB-r user\fR ] [ \fB-a user%password\fR ] [ \fB-A user%password\fR ] [ \fB-p\fR ]
.SH "DESCRIPTION"
.PP
@ -38,14 +38,14 @@ will also be listed. Note that this operation does not assign
group ids to any groups that have not already been seen by
\fBwinbindd(8)\fR.
.TP
\fB-h name\fR
The \fI-h\fR option
\fB-N name\fR
The \fI-N\fR option
queries \fBwinbindd(8)\fR to query the WINS
server for the IP address associated with the NetBIOS name
specified by the \fIname\fR parameter.
.TP
\fB-i ip\fR
The \fI-i\fR option
\fB-I ip\fR
The \fI-I\fR option
queries \fBwinbindd(8)\fR to send a node status
request to get the NetBIOS name associated with the IP address
specified by the \fIip\fR parameter.
@ -119,7 +119,7 @@ succeeded, or 1 if the operation failed. If the \fBwinbindd(8)
failure.
.SH "VERSION"
.PP
This man page is correct for version 2.2 of
This man page is correct for version 3.0 of
the Samba suite.
.SH "SEE ALSO"
.PP

25
docs/manpages/winbindd.8
View File

@ -3,12 +3,12 @@
.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
.\" Please send any bug reports, improvements, comments, patches,
.\" etc. to Steve Cheng <steve@ggi-project.org>.
.TH "WINBINDD" "8" "01 October 2002" "" ""
.TH "WINBINDD" "8" "18 oktober 2002" "" ""
.SH NAME
winbindd \- Name Service Switch daemon for resolving names from NT servers
.SH SYNOPSIS
\fBwinbindd\fR [ \fB-i\fR ] [ \fB-d <debug level>\fR ] [ \fB-s <smb config file>\fR ]
\fBwinbindd\fR [ \fB-i\fR ] [ \fB-B\fR ] [ \fB-d <debug level>\fR ] [ \fB-s <smb config file>\fR ] [ \fB-n\fR ]
.SH "DESCRIPTION"
.PP
@ -85,6 +85,25 @@ Tells \fBwinbindd\fR to not
become a daemon and detach from the current terminal. This
option is used by developers when interactive debugging
of \fBwinbindd\fR is required.
.TP
\fB-n\fR
Disable caching. This means winbindd will
always have to wait for a response from the domain controller
before it can respond to a client and this thus makes things
slower. The results will however be more accurate, since
results from the cache might not be up-to-date. This
might also temporarily hang winbindd if the DC doesn't respond.
.TP
\fB-B\fR
Dual daemon mode. This means winbindd will run
as 2 threads. The first will answer all requests from the cache,
thus making responses to clients faster. The other will
update the cache for the query that the first has just responded.
Advantage of this is that responses are accurate and fast.
.TP
\fB-s|--conf=smb.conf\fR
Specifies the location of the all-important
\fIsmb.conf\fR file.
.SH "NAME AND ID RESOLUTION"
.PP
Users and groups on a Windows NT server are assigned
@ -291,7 +310,7 @@ This directory is by default \fI/usr/local/samba/var/locks
Storage for cached user and group information.
.SH "VERSION"
.PP
This man page is correct for version 2.2 of
This man page is correct for version 3.0 of
the Samba suite.
.SH "SEE ALSO"
.PP