docs/docbook/projdoc/ADS-HOWTO.sgml

   1 <chapter id="ADS">
   2
   3 <chapterinfo>
   4         <author>
   5                 <firstname>Andrew</firstname><surname>Tridgell</surname>
   6         </author>
   7         <pubdate>2002</pubdate>
   8 </chapterinfo>
   9
  10 <title>Samba as a ADS domain member</title>
  11
  12 <para>
  13 This is a rough guide to setting up Samba 3.0 with kerberos authentication against a
  14 Windows2000 KDC.
  15 </para>
  16
  17 <para>Pieces you need before you begin:</para>
  18 <para>
  19 <simplelist>
  20 <member>a Windows 2000 server.</member>
  21 <member>samba 3.0 or higher.</member>
  22 <member>the MIT kerberos development libraries (either install from the above sources or use a package). The heimdal libraries will not work.</member>
  23 <member>the OpenLDAP development libraries.</member>
  24 </simplelist>
  25 </para>
  26
  27 <sect1>
  28 <title>Installing the required packages for Debian</title>
  29
  30 <para>On Debian you need to install the following packages:</para>
  31 <para>
  32 <simplelist>
  33 <member>libkrb5-dev</member>
  34 <member>krb5-user</member>
  35 </simplelist>
  36 </para>
  37 </sect1>
  38
  39 <sect1>
  40 <title>Installing the required packages for RedHat</title>
  41
  42 <para>On RedHat this means you should have at least: </para>
  43 <para>
  44 <simplelist>
  45 <member>krb5-workstation (for kinit)</member>
  46 <member>krb5-libs (for linking with)</member>
  47 <member>krb5-devel (because you are compiling from source)</member>
  48 </simplelist>
  49 </para>
  50
  51 <para>in addition to the standard development environment.</para>
  52
  53 <para>Note that these are not standard on a RedHat install, and you may need
  54 to get them off CD2.</para>
  55
  56 </sect1>
  57
  58 <sect1>
  59 <title>Compile Samba</title>
  60 <para>If your kerberos libraries are in a non-standard location then
  61   remember to add the configure option --with-krb5=DIR.</para>
  62
  63 <para>After you run configure make sure that include/config.h contains
  64   lines like this:</para>
  65
  66 <para><programlisting>
  67 #define HAVE_KRB5 1
  68 #define HAVE_LDAP 1
  69 </programlisting></para>
  70
  71 <para>If it doesn't then configure did not find your krb5 libraries or
  72   your ldap libraries. Look in config.log to figure out why and fix
  73   it.</para>
  74
  75 <para>Then compile and install Samba as usual. You must use at least the
  76   following 3 options in smb.conf:</para>
  77
  78 <para><programlisting>
  79   realm = YOUR.KERBEROS.REALM
  80   security = ADS
  81   encrypt passwords = yes
  82 </programlisting></para>
  83
  84 <para>
  85 In case samba can't figure out your ads server using your realm name, use the
  86 <command>ads server</command> option in <filename>smb.conf</filename>:
  87 <programlisting>
  88   ads server = your.kerberos.server
  89 </programlisting>
  90 </para>
  91
  92 <para>You do *not* need a smbpasswd file, although it won't do any harm
  93   and if you have one then Samba will be able to fall back to normal
  94   password security for older clients. I expect that the above
  95   required options will change soon when we get better active
  96   directory integration.</para>
  97 </sect1>
  98
  99 <sect1>
 100 <title>Setup your /etc/krb5.conf</title>
 101
 102 <para>The minimal configuration for krb5.conf is:</para>
 103
 104 <para><programlisting>
 105 [realms]
 106     YOUR.KERBEROS.REALM = {
 107         kdc = your.kerberos.server
 108     }
 109 </programlisting></para>
 110
 111 <para>Test your config by doing a "kinit USERNAME@REALM" and making sure that
 112   your password is accepted by the Win2000 KDC. </para>
 113
 114 <para>NOTE: The realm must be uppercase. </para>
 115
 116 <para>
 117 You also must ensure that you can do a reverse DNS lookup on the IP
 118 address of your KDC. Also, the name that this reverse lookup maps to
 119 must either be the netbios name of the KDC (ie. the hostname with no
 120 domain attached) or it can alternatively be the netbios name
 121 followed by the realm.
 122 </para>
 123
 124 <para>
 125 The easiest way to ensure you get this right is to add a /etc/hosts
 126 entry mapping the IP address of your KDC to its netbios name. If you
 127 don't get this right then you will get a "local error" when you try
 128 to join the realm.
 129 </para>
 130
 131 <para>
 132 If all you want is kerberos support in smbclient then you can skip
 133 straight to step 5 now. Step 3 is only needed if you want kerberos
 134 support in smbd.
 135 </para>
 136
 137 </sect1>
 138
 139 <sect1>
 140 <title>Create the computer account</title>
 141
 142 <para>
 143 Do a "kinit" as a user that has authority to change arbitrary
 144 passwords on the KDC ("Administrator" is a good choice). Then as a
 145 user that has write permission on the Samba private directory
 146 (usually root) run:
 147 <command>net ads join</command>
 148 </para>
 149
 150 <sect2>
 151 <title>Possible errors</title>
 152
 153 <para>
 154 <variablelist>
 155 <varlistentry><term>"bash: kinit: command not found"</term>
 156 <listitem><para>kinit is in the krb5-workstation RPM on RedHat systems, and is in /usr/kerberos/bin, so it won't be in the path until you log in again (or open a new terminal)</para></listitem></varlistentry>
 157 <varlistentry><term>"ADS support not compiled in"</term>
 158 <listitem><para>Samba must be reconfigured (remove config.cache) and recompiled (make clean all install) after the kerberos libs and headers are installed.</para></listitem></varlistentry>
 159 </variablelist>
 160 </para>
 161
 162 </sect2>
 163
 164 </sect1>
 165
 166 <sect1>
 167 <title>Test your server setup</title>
 168
 169 <para>
 170 On a Windows 2000 client try <command>net use * \\server\share</command>. You should
 171 be logged in with kerberos without needing to know a password. If
 172 this fails then run <command>klist tickets</command>. Did you get a ticket for the
 173 server? Does it have an encoding type of DES-CBC-MD5 ?
 174 </para>
 175
 176 </sect1>
 177
 178 <sect1>
 179 <title>Testing with smbclient</title>
 180
 181 <para>
 182 On your Samba server try to login to a Win2000 server or your Samba
 183 server using smbclient and kerberos. Use smbclient as usual, but
 184 specify the -k option to choose kerberos authentication.
 185 </para>
 186
 187 </sect1>
 188
 189 <sect1>
 190 <title>Notes</title>
 191
 192 <para>You must change administrator password at least once after DC install,
 193  to create the right encoding types</para>
 194
 195 <para>w2k doesn't seem to create the _kerberos._udp and _ldap._tcp in
 196    their defaults DNS setup. Maybe fixed in service packs?</para>
 197
 198 </sect1>
 199
 200 </chapter>