From 7054fb250718ac7aa3da7d1345cde55b60457f32 Mon Sep 17 00:00:00 2001
From: Andrew Bartlett <abartlet@samba.org>
Date: Sat, 1 Feb 2003 03:26:53 +0000
Subject: Clear up the winbind doco on ADS support, and specify 'net join' not
 'net rpc join' as people are using the 'wrong' one and wondering why it
 doesn't quite work.

Andrew Bartlett
(This used to be commit dfe565e6ce7ae724a95ba9f162ab51436cf4b63e)
---
 docs/docbook/projdoc/winbind.sgml | 26 +++++++++++++++++++++-----
 1 file changed, 21 insertions(+), 5 deletions(-)

(limited to 'docs/docbook/projdoc/winbind.sgml')

diff --git a/docs/docbook/projdoc/winbind.sgml b/docs/docbook/projdoc/winbind.sgml
index b144c5e06b..06579617f5 100644
--- a/docs/docbook/projdoc/winbind.sgml
+++ b/docs/docbook/projdoc/winbind.sgml
@@ -175,7 +175,7 @@
 	<sect2>
 		<title>Microsoft Remote Procedure Calls</title>
 		
-		<para>Over the last two years, efforts have been underway 
+		<para>Over the last few years, efforts have been underway 
 		by various Samba Team members to decode various aspects of 
 		the Microsoft Remote Procedure Call (MSRPC) system. This 
 		system is used for most network related operations between 
@@ -193,6 +193,21 @@
 		NT account information onto UNIX user and group names.</para>
 	</sect2>
 	
+	<sect2>
+		<title>Microsoft Active Directory Services</title>
+
+		<para>
+                Since late 2001, Samba has gained the ability to
+                interact with Microsoft Windows 2000 using its 'Native
+                Mode' protocols, rather than the NT4 RPC services.
+                Using LDAP and Kerberos, a domain member running
+                winbind can enumerate users and groups in exactly the
+                same way as a Win2k client would, and in so doing
+                provide a much more efficient and
+                effective winbind implementation.  
+                </para>
+	</sect2>
+	
 	<sect2>
 		<title>Name Service Switch</title>
 		
@@ -466,7 +481,7 @@ whether or not you have previously built the Samba binaries.
 <prompt>root#</prompt> <command>autoconf</command>
 <prompt>root#</prompt> <command>make clean</command>
 <prompt>root#</prompt> <command>rm config.cache</command>
-<prompt>root#</prompt> <command>./configure --with-winbind</command>
+<prompt>root#</prompt> <command>./configure</command>
 <prompt>root#</prompt> <command>make</command>
 <prompt>root#</prompt> <command>make install</command>
 </programlisting></para>
@@ -584,7 +599,7 @@ a domain user who has administrative privileges in the domain.
 	
 
 <para>
-<prompt>root#</prompt> <command>/usr/local/samba/bin/net rpc join -S PDC -U Administrator</command>
+<prompt>root#</prompt> <command>/usr/local/samba/bin/net join -S PDC -U Administrator</command>
 </para>
 
 
@@ -1065,7 +1080,7 @@ configured in the pam.conf.
 
 	<itemizedlist>
 		<listitem><para>Winbind is currently only available for 
-		the Linux operating system, although ports to other operating 
+		the Linux, Solaris and IRIX operating systems, although ports to other operating 
 		systems are certainly possible. For such ports to be feasible, 
 		we require the C library of the target operating system to 
 		support the Name Service Switch and Pluggable Authentication
@@ -1081,7 +1096,8 @@ configured in the pam.conf.
 		
 		<listitem><para>Currently the winbind PAM module does not take 
 		into account possible workstation and logon time restrictions 
-		that may be been set for Windows NT users.</para></listitem>
+		that may be been set for Windows NT users, this is
+		instead up to the PDC to enforce.</para></listitem>
 	</itemizedlist>
 </sect1>
 
-- 
cgit