From 27aef6855f1543547b8190f06fd264d1b52a558d Mon Sep 17 00:00:00 2001 From: Jelmer Vernooij Date: Sun, 6 Apr 2003 18:42:44 +0000 Subject: Regenerate docs (This used to be commit 5a2aaa3d5b039776314067aee953921e7865dc4d) --- docs/htmldocs/ads.html | 134 +++++++++++++++++++++++++++++++++++++++---------- 1 file changed, 108 insertions(+), 26 deletions(-) (limited to 'docs/htmldocs/ads.html') diff --git a/docs/htmldocs/ads.html b/docs/htmldocs/ads.html index f37bbf0abc..d6678c250a 100644 --- a/docs/htmldocs/ads.html +++ b/docs/htmldocs/ads.html @@ -83,7 +83,7 @@ CLASS="SECT1" >

8.1. Setup your smb.conf ads server = your.kerberos.server

You do *not* need a smbpasswd file, and older clients will - be authenticated as if "security = domain", although it won't do any harm + be authenticated as if security = domain, + although it won't do any harm and allows you to have local users not in the domain. I expect that the above required options will change soon when we get better active directory integration.

8.2. Setup your /etc/krb5.conf

The minimal configuration for krb5.conf is:

The minimal configuration for krb5.conf is:

Test your config by doing a "kinit USERNAME@REALM" and making sure that
+>Test your config by doing a kinit USERNAME@REALM and making sure that
   your password is accepted by the Win2000 KDC. 
NOTE: The realm must be uppercase. 
The realm must be uppercase. 
You also must ensure that you can do a reverse DNS lookup on the IP
 address of your KDC. Also, the name that this reverse lookup maps to
@@ -151,13 +215,28 @@ must either be the netbios name of the KDC (ie. the hostname with no
 domain attached) or it can alternatively be the netbios name
 followed by the realm. 
The easiest way to ensure you get this right is to add a /etc/hosts
-entry mapping the IP address of your KDC to its netbios name. If you
-don't get this right then you will get a "local error" when you try
-to join the realm.
The easiest way to ensure you get this right is to add a 
+/etc/hosts entry mapping the IP address of your KDC to 
+its netbios name. If you don't get this right then you will get a 
+"local error" when you try to join the realm.
If all you want is kerberos support in smbclient then you can skip
-straight to step 5 now. Step 3 is only needed if you want kerberos
+straight to Test with smbclient now. 
+Creating a computer account 
+and testing your servers
+is only needed if you want kerberos
 support for smbd and winbindd.

8.3. Create the computer account

As a user that has write permission on the Samba private directory (usually root) run: -net ads joinnet ads join

8.3.1. Possible errors

8.4. Test your server setup

On a Windows 2000 client try net use * \\server\shareOn a Windows 2000 client try net use * \\server\share. You should be logged in with kerberos without needing to know a password. If -this fails then run klist ticketsklist tickets. Did you get a ticket for the server? Does it have an encoding type of DES-CBC-MD5 ?

8.5. Testing with smbclient

On your Samba server try to login to a Win2000 server or your Samba server using smbclient and kerberos. Use smbclient as usual, but -specify the -k option to choose kerberos authentication.

-k option to choose kerberos authentication.

8.6. Notes