diff options
| -rw-r--r-- | docs/textdocs/BROWSING-Config.txt | 12 | ||||
| -rw-r--r-- | docs/textdocs/DOMAIN_CONTROL.txt | 19 |
2 files changed, 22 insertions, 9 deletions
diff --git a/docs/textdocs/BROWSING-Config.txt b/docs/textdocs/BROWSING-Config.txt index 33c56e0897..6afd958f77 100644 --- a/docs/textdocs/BROWSING-Config.txt +++ b/docs/textdocs/BROWSING-Config.txt @@ -41,13 +41,13 @@ If only one WINS server is used then the use of the "remote announce" and the Samba WINS does not support MS-WINS replication. This means that when setting up Samba as a WINS server there must only be one nmbd configured as a WINS server -on the network. Some sites have used multiple Samba WINS servers for redundency +on the network. Some sites have used multiple Samba WINS servers for redundancy (one server per subnet) and then used "remote browse sync" and "remote announce" -to affect browse list collation across all segments. Note that this means clients -will only resolve local names, and must be configured to use DNS to resolve names -on other subnets in order to resolve the IP addresses of the servers they can see -on other subnets. This setup is not recommended, but is mentioned as a practical -consideration (ie. an 'if all else fails' scenario). +to affect browse list collation across all segments. Note that this means +clients will only resolve local names, and must be configured to use DNS to +resolve names on other subnets in order to resolve the IP addresses of the +servers they can see on other subnets. This setup is not recommended, but is +mentioned as a practical consideration (ie: an 'if all else fails' scenario). Lastly, take note that browse lists are a collection of unreliable broadcast messages that are repeated at intervals of not more than 15 minutes. This means diff --git a/docs/textdocs/DOMAIN_CONTROL.txt b/docs/textdocs/DOMAIN_CONTROL.txt index bbd03873b1..7c24b50325 100644 --- a/docs/textdocs/DOMAIN_CONTROL.txt +++ b/docs/textdocs/DOMAIN_CONTROL.txt @@ -1,11 +1,11 @@ !== -!== DOMAIN_CONTROL.txt for Samba release 1.9.18 08 Jan 1998 +!== DOMAIN_CONTROL.txt for Samba release 1.9.18p8 13 Jun 1998 !== Initial Release: August 22, 1996 Contributor: John H Terpstra <samba-bugs@samba.anu.edu.au> Copyright (C) 1996-1997 - John H Terpstra -Updated: August 25, 1997 -Status: Current - New Content +Updated: July 5, 1998 +Status: Current Subject: Windows NT Domain Control & Samba ============================================================================ @@ -106,3 +106,16 @@ redirect all access authentication to that server. This way you can use Windows NT to act as your password server with full support for Microsoft encrypted passwords. +Note also, that since release of samba-1.9.18 we now support native encrypted +passwords too. To enable encrypted password handling several things need to be +done: + 1) In smb.conf [globals]: + encrypt passwords = yes + smbpasswd file = /path/smbpasswd +the standard path is /usr/local/samba/private/smbpasswd but this may be +platform specific. + + 2) Use "smbpasswd -a" to add all users to the smbpasswd file. + +Above all read all the documentation for encrypted password support - you will +need it! |