From 3db52feb1f3b2c07ce0b06ad4a7099fa6efe3fc7 Mon Sep 17 00:00:00 2001 From: Andrew Tridgell Date: Mon, 13 Dec 1999 13:27:58 +0000 Subject: first pass at updating head branch to be to be the same as the SAMBA_2_0 branch (This used to be commit 453a822a76780063dff23526c35408866d0c0154) --- docs/htmldocs/DOMAIN_MEMBER.html | 25 +- docs/htmldocs/nmbd.8.html | 8 +- docs/htmldocs/nmblookup.1.html | 16 +- docs/htmldocs/samba.7.html | 8 - docs/htmldocs/smb.conf.5.html | 976 +++++++++++++++++++++++++-------------- docs/htmldocs/smbclient.1.html | 18 +- docs/htmldocs/smbd.8.html | 29 +- docs/htmldocs/smbstatus.1.html | 2 +- docs/htmldocs/swat.8.html | 2 +- docs/htmldocs/testparm.1.html | 11 +- 10 files changed, 693 insertions(+), 402 deletions(-) (limited to 'docs/htmldocs') diff --git a/docs/htmldocs/DOMAIN_MEMBER.html b/docs/htmldocs/DOMAIN_MEMBER.html index 6d9741f2f2..409534c99e 100644 --- a/docs/htmldocs/DOMAIN_MEMBER.html +++ b/docs/htmldocs/DOMAIN_MEMBER.html @@ -13,7 +13,7 @@

Joining an NT Domain with Samba 2.0

Jeremy Allison, Samba Team

-

11th November 1998

+

7th October 1999

@@ -23,7 +23,8 @@


In order for a Samba-2 server to join an NT domain, you must first add the NetBIOS name of the Samba server to the NT domain on the PDC using Server Manager for Domains. This creates the machine account in the -domain (PDC) SAM. +domain (PDC) SAM. Note that you should add the Samba server as a "Windows +NT Workstation or Server", NOT as a Primary or backup domain controller.


Assume you have a Samba-2 server with a NetBIOS name of SERV1 and are joining an NT domain called DOM, which has a PDC with a NetBIOS name of DOMPDC and two backup domain controllers with NetBIOS names DOMBDC1 @@ -63,6 +64,9 @@ use domain security.


line in the [global] section to read:


workgroup = DOM


as this is the name of the domain we are joining. +


You must also have the parameter "encrypt passwords" +set to "yes" in order for your users to authenticate to the +NT PDC.


Finally, add (or modify) a:


"password server ="


line in the [global] section to read: @@ -72,18 +76,13 @@ to contact in order to authenticate users. Samba will try to contact each of these servers in order, so you may want to rearrange this list in order to spread out the authentication load among domain controllers. -


Currently, Samba requires that a defined list of domain controllers be -listed in this parameter in order to authenticate with domain-level -security. NT does not use this method, and will either broadcast or -use a WINS database in order to find domain controllers to +


Alternatively, if you want smbd to automatically determine the +list of Domain controllers to use for authentication, you may set this line to be : +


password server = * +


This method, which is new in Samba 2.0.6 and above, allows Samba +to use exactly the same mechanism that NT does. This method either broadcasts or +uses a WINS database in order to find domain controllers to authenticate against. -


Originally, I considered this idea for Samba, but dropped it because -it seemed so insecure. However several Samba-2 alpha users have -requested that this feature be added to make Samba more NT-like, so -I'll probably add a special name of '*' (which means: act like NT -when looking for domain controllers) in a future release of the -code. At present, however, you need to know where your domain -controllers are.


Finally, restart your Samba daemons and get ready for clients to begin using domain security!


Why is this better than security = server?
diff --git a/docs/htmldocs/nmbd.8.html b/docs/htmldocs/nmbd.8.html index 3139e90ad1..03fd3588e2 100644 --- a/docs/htmldocs/nmbd.8.html +++ b/docs/htmldocs/nmbd.8.html @@ -25,7 +25,7 @@ naming services to clients


SYNOPSIS

-


nmbd [-D] [-o] [-a] [-H lmhosts file] [-d debuglevel] [-l log file basename] [-n primary NetBIOS name] [-p port number] [-s configuration file] [-i NetBIOS scope] [-h] +


nmbd [-D] [-a] [-o] [-h] [-V] [-H lmhosts file] [-d debuglevel] [-l log file basename] [-n primary NetBIOS name] [-p port number] [-s configuration file] [-i NetBIOS scope]


DESCRIPTION

@@ -70,6 +70,10 @@ append log messages to the log file. This is the default.
  • -o If this parameter is specified, the log files will be overwritten when opened. By default, the log files will be appended to. +


    +

  • -h Prints the help information (usage) for nmbd. +


    +

  • -V Prints the version number for nmbd.


  • -H filename NetBIOS lmhosts file.


    The lmhosts file is a list of NetBIOS names to IP addresses that is @@ -133,8 +137,6 @@ use of NetBIOS scopes, see rfc1001.txt and rfc1002.txt. NetBIOS scopes are very rarely used, only set this parameter if you are the system administrator in charge of all the NetBIOS systems you communicate with. -


    -

  • -h Prints the help information (usage) for nmbd.



    FILES

    diff --git a/docs/htmldocs/nmblookup.1.html b/docs/htmldocs/nmblookup.1.html index 5ff58e5b40..2c3e80c76e 100644 --- a/docs/htmldocs/nmblookup.1.html +++ b/docs/htmldocs/nmblookup.1.html @@ -24,7 +24,7 @@


    SYNOPSIS

    -


    nmblookup [-M] [-R] [-S] [-r] [-A] [-h] [-B broadcast address] [-U unicast address] [-d debuglevel] [-s smb config file] [-i NetBIOS scope] name +


    nmblookup [-M] [-R] [-S] [-r] [-A] [-h] [-B broadcast address] [-U unicast address] [-d debuglevel] [-s smb config file] [-i NetBIOS scope] [-T] name


    DESCRIPTION

    @@ -38,8 +38,9 @@ or to a particular machine. All queries are done over UDP.