1 <?xml version="1.0" encoding="iso-8859-1"?>
2 <!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
7 <firstname>Tim</firstname><surname>Potter</surname>
9 <orgname>Samba Team</orgname>
10 <address><email>tpot@linuxcare.com.au</email></address>
15 <firstname>Naag</firstname><surname>Mummaneni</surname>
17 <address><email>getnag@rediffmail.com</email></address>
19 <contrib>Notes for Solaris</contrib>
22 <firstname>John</firstname><surname>Trostel</surname>
24 <orgname>SNAP</orgname>
25 <address><email>jtrostel@snapserver.com</email></address>
31 <pubdate>27 June 2002</pubdate>
34 <title>Winbind: Use of Domain Accounts</title>
37 <title>Features and Benefits</title>
40 Integration of UNIX and Microsoft Windows NT through a unified logon has
41 been considered a <quote>holy grail</quote> in heterogeneous computing environments for
46 There is one other facility without which UNIX and Microsoft Windows network
47 interoperability would suffer greatly. It is imperative that there be a
48 mechanism for sharing files across UNIX systems and to be able to assign
49 domain user and group ownerships with integrity.
53 <emphasis>winbind</emphasis> is a component of the Samba suite of programs that
54 solves the unified logon problem. Winbind uses a UNIX implementation of Microsoft
55 RPC calls, Pluggable Authentication Modules, and the Name Service Switch to
56 allow Windows NT domain users to appear and operate as UNIX users on a UNIX
57 machine. This chapter describes the Winbind system, explaining the functionality
58 it provides, how it is configured, and how it works internally.
62 Winbind provides three separate functions:
67 Authentication of user credentials (via PAM).
71 Identity resolution (via NSS).
75 Winbind maintains a database called winbind_idmap.tdb in which it stores
76 mappings between UNIX UIDs / GIDs and NT SIDs. This mapping is used only
77 for users and groups that do not have a local UID/GID. It stored the UID/GID
78 allocated from the idmap uid/gid range that it has mapped to the NT SID.
79 If <parameter>idmap backend</parameter> has been specified as ldapsam:url
80 then instead of using a local mapping Winbind will obtain this information
81 from the LDAP database.
86 <indexterm><primary>winbindd</primary></indexterm>
87 <indexterm><primary>starting samba</primary><secondary>winbindd</secondary></indexterm>
88 If <command>winbindd</command> is not running, smbd (which calls <command>winbindd</command>) will fall back to
89 using purely local information from <filename>/etc/passwd</filename> and <filename>/etc/group</filename> and no dynamic
94 <image id="winbind_idmap">
95 <imagedescription>Winbind Idmap</imagedescription>
96 <imagefile scale="50">idmap_winbind_no_loop</imagefile>
103 <title>Introduction</title>
105 <para>It is well known that UNIX and Microsoft Windows NT have
106 different models for representing user and group information and
107 use different technologies for implementing them. This fact has
108 made it difficult to integrate the two systems in a satisfactory
111 <para>One common solution in use today has been to create
112 identically named user accounts on both the UNIX and Windows systems
113 and use the Samba suite of programs to provide file and print services
114 between the two. This solution is far from perfect, however, as
115 adding and deleting users on both sets of machines becomes a chore
116 and two sets of passwords are required &smbmdash; both of which
117 can lead to synchronization problems between the UNIX and Windows
118 systems and confusion for users.</para>
120 <para>We divide the unified logon problem for UNIX machines into
121 three smaller problems:</para>
124 <listitem><para>Obtaining Windows NT user and group information.
127 <listitem><para>Authenticating Windows NT users.
130 <listitem><para>Password changing for Windows NT users.
135 <para>Ideally, a prospective solution to the unified logon problem
136 would satisfy all the above components without duplication of
137 information on the UNIX machines and without creating additional
138 tasks for the system administrator when maintaining users and
139 groups on either system. The Winbind system provides a simple
140 and elegant solution to all three components of the unified logon
146 <title>What Winbind Provides</title>
148 <para>Winbind unifies UNIX and Windows NT account management by
149 allowing a UNIX box to become a full member of an NT domain. Once
150 this is done the UNIX box will see NT users and groups as if
151 they were <quote>native</quote> UNIX users and groups, allowing the NT domain
152 to be used in much the same manner that NIS+ is used within
153 UNIX-only environments.</para>
155 <para>The end result is that whenever any
156 program on the UNIX machine asks the operating system to lookup
157 a user or group name, the query will be resolved by asking the
158 NT Domain Controller for the specified domain to do the lookup.
159 Because Winbind hooks into the operating system at a low level
160 (via the NSS name resolution modules in the C library), this
161 redirection to the NT Domain Controller is completely
164 <para>Users on the UNIX machine can then use NT user and group
165 names as they would <quote>native</quote> UNIX names. They can chown files
166 so they are owned by NT domain users or even login to the
167 UNIX machine and run a UNIX X-Window session as a domain user.</para>
169 <para>The only obvious indication that Winbind is being used is
170 that user and group names take the form <constant>DOMAIN\user</constant> and
171 <constant>DOMAIN\group</constant>. This is necessary as it allows Winbind to determine
172 that redirection to a Domain Controller is wanted for a particular
173 lookup and which trusted domain is being referenced.</para>
175 <para>Additionally, Winbind provides an authentication service
176 that hooks into the Pluggable Authentication Modules (PAM) system
177 to provide authentication via an NT domain to any PAM-enabled
178 applications. This capability solves the problem of synchronizing
179 passwords between systems since all passwords are stored in a single
180 location (on the Domain Controller).</para>
183 <title>Target Uses</title>
185 <para>Winbind is targeted at organizations that have an
186 existing NT-based domain infrastructure into which they wish
187 to put UNIX workstations or servers. Winbind will allow these
188 organizations to deploy UNIX workstations without having to
189 maintain a separate account infrastructure. This greatly
190 simplifies the administrative overhead of deploying UNIX
191 workstations into an NT-based organization.</para>
193 <para>Another interesting way in which we expect Winbind to
194 be used is as a central part of UNIX-based appliances. Appliances
195 that provide file and print services to Microsoft-based networks
196 will be able to use Winbind to provide seamless integration of
197 the appliance into the domain.</para>
204 <title>How Winbind Works</title>
206 <para>The Winbind system is designed around a client/server
207 architecture. A long running <command>winbindd</command> daemon
208 listens on a UNIX domain socket waiting for requests
209 to arrive. These requests are generated by the NSS and PAM
210 clients and is processed sequentially.</para>
212 <para>The technologies used to implement Winbind are described
213 in detail below.</para>
216 <title>Microsoft Remote Procedure Calls</title>
218 <para>Over the last few years, efforts have been underway
219 by various Samba Team members to decode various aspects of
220 the Microsoft Remote Procedure Call (MSRPC) system. This
221 system is used for most network-related operations between
222 Windows NT machines including remote management, user authentication
223 and print spooling. Although initially this work was done
224 to aid the implementation of Primary Domain Controller (PDC)
225 functionality in Samba, it has also yielded a body of code that
226 can be used for other purposes.</para>
228 <para>Winbind uses various MSRPC calls to enumerate domain users
229 and groups and to obtain detailed information about individual
230 users or groups. Other MSRPC calls can be used to authenticate
231 NT domain users and to change user passwords. By directly querying
232 a Windows PDC for user and group information, Winbind maps the
233 NT account information onto UNIX user and group names.</para>
237 <title>Microsoft Active Directory Services</title>
240 Since late 2001, Samba has gained the ability to
241 interact with Microsoft Windows 2000 using its <quote>Native
242 Mode</quote> protocols, rather than the NT4 RPC services.
243 Using LDAP and Kerberos, a Domain Member running
244 Winbind can enumerate users and groups in exactly the
245 same way as a Windows 200x client would, and in so doing
246 provide a much more efficient and effective Winbind implementation.
251 <title>Name Service Switch</title>
253 <para>The Name Service Switch, or NSS, is a feature that is
254 present in many UNIX operating systems. It allows system
255 information such as hostnames, mail aliases and user information
256 to be resolved from different sources. For example, a standalone
257 UNIX workstation may resolve system information from a series of
258 flat files stored on the local filesystem. A networked workstation
259 may first attempt to resolve system information from local files,
260 and then consult an NIS database for user information or a DNS server
261 for hostname information.</para>
263 <para>The NSS application programming interface allows Winbind
264 to present itself as a source of system information when
265 resolving UNIX usernames and groups. Winbind uses this interface,
266 and information obtained from a Windows NT server using MSRPC
267 calls to provide a new source of account enumeration. Using standard
268 UNIX library calls, one can enumerate the users and groups on
269 a UNIX machine running Winbind and see all users and groups in
270 a NT domain plus any trusted domain as though they were local
271 users and groups.</para>
273 <para>The primary control file for NSS is
274 <filename>/etc/nsswitch.conf</filename>.
275 When a UNIX application makes a request to do a lookup,
276 the C library looks in <filename>/etc/nsswitch.conf</filename>
277 for a line that matches the service type being requested, for
278 example the <quote>passwd</quote> service type is used when user or group names
279 are looked up. This config line specifies which implementations
280 of that service should be tried and in what order. If the passwd
281 config line is:</para>
284 passwd: files example
287 <para>then the C library will first load a module called
288 <filename>/lib/libnss_files.so</filename> followed by
289 the module <filename>/lib/libnss_example.so</filename>. The
290 C library will dynamically load each of these modules in turn
291 and call resolver functions within the modules to try to resolve
292 the request. Once the request is resolved, the C library returns the
293 result to the application.</para>
295 <para>This NSS interface provides an easy way for Winbind
296 to hook into the operating system. All that needs to be done
297 is to put <filename>libnss_winbind.so</filename> in <filename>/lib/</filename>
298 then add <quote>winbind</quote> into <filename>/etc/nsswitch.conf</filename> at
299 the appropriate place. The C library will then call Winbind to
300 resolve user and group names.</para>
304 <title>Pluggable Authentication Modules</title>
306 <para>Pluggable Authentication Modules, also known as PAM,
307 is a system for abstracting authentication and authorization
308 technologies. With a PAM module it is possible to specify different
309 authentication methods for different system applications without
310 having to recompile these applications. PAM is also useful
311 for implementing a particular policy for authorization. For example,
312 a system administrator may only allow console logins from users
313 stored in the local password file but only allow users resolved from
314 a NIS database to log in over the network.</para>
316 <para>Winbind uses the authentication management and password
317 management PAM interface to integrate Windows NT users into a
318 UNIX system. This allows Windows NT users to log in to a UNIX
319 machine and be authenticated against a suitable Primary Domain
320 Controller. These users can also change their passwords and have
321 this change take effect directly on the Primary Domain Controller.
324 <para>PAM is configured by providing control files in the directory
325 <filename>/etc/pam.d/</filename> for each of the services that
326 require authentication. When an authentication request is made
327 by an application, the PAM code in the C library looks up this
328 control file to determine what modules to load to do the
329 authentication check and in what order. This interface makes adding
330 a new authentication service for Winbind very easy. All that needs
331 to be done is that the <filename>pam_winbind.so</filename> module
332 is copied to <filename>/lib/security/</filename> and the PAM
333 control files for relevant services are updated to allow
334 authentication via Winbind. See the PAM documentation
335 in <link linkend="pam">PAM-Based Distributed Authentication</link> for more information.</para>
340 <title>User and Group ID Allocation</title>
342 <para>When a user or group is created under Windows NT/200x
343 it is allocated a numerical relative identifier (RID). This is
344 slightly different from UNIX which has a range of numbers that are
345 used to identify users, and the same range in which to identify
346 groups. It is Winbind's job to convert RIDs to UNIX ID numbers and
347 vice versa. When Winbind is configured, it is given part of the UNIX
348 user ID space and a part of the UNIX group ID space in which to
349 store Windows NT users and groups. If a Windows NT user is
350 resolved for the first time, it is allocated the next UNIX ID from
351 the range. The same process applies for Windows NT groups. Over
352 time, Winbind will have mapped all Windows NT users and groups
353 to UNIX user IDs and group IDs.</para>
355 <para>The results of this mapping are stored persistently in
356 an ID mapping database held in a tdb database). This ensures that
357 RIDs are mapped to UNIX IDs in a consistent way.</para>
362 <title>Result Caching</title>
365 <indexterm><primary>SAM</primary></indexterm>
366 An active system can generate a lot of user and group
367 name lookups. To reduce the network cost of these lookups, Winbind
368 uses a caching scheme based on the SAM sequence number supplied
369 by NT Domain Controllers. User or group information returned
370 by a PDC is cached by Winbind along with a sequence number also
371 returned by the PDC. This sequence number is incremented by
372 Windows NT whenever any user or group information is modified. If
373 a cached entry has expired, the sequence number is requested from
374 the PDC and compared against the sequence number of the cached entry.
375 If the sequence numbers do not match, then the cached information
376 is discarded and up-to-date information is requested directly
383 <title>Installation and Configuration</title>
386 <title>Introduction</title>
389 This section describes the procedures used to get Winbind up and
390 running. Winbind is capable of providing access
391 and authentication control for Windows Domain users through an NT
392 or Windows 200x PDC for regular services, such as telnet and ftp, as
393 well for Samba services.
399 <emphasis>Why should I do this?</emphasis>
402 <para>This allows the Samba administrator to rely on the
403 authentication mechanisms on the Windows NT/200x PDC for the authentication
404 of Domain Members. Windows NT/200x users no longer need to have separate
405 accounts on the Samba server.
411 <emphasis>Who should be reading this document?</emphasis>
415 This document is designed for system administrators. If you are
416 implementing Samba on a file server and wish to (fairly easily)
417 integrate existing Windows NT/200x users from your PDC onto the
418 Samba server, this document is for you.
426 <title>Requirements</title>
429 If you have a Samba configuration file that you are currently using, <emphasis>BACK IT UP!</emphasis>
430 If your system already uses PAM, <emphasis>back up the <filename>/etc/pam.d</filename> directory
431 contents!</emphasis> If you haven't already made a boot disk, <emphasis>MAKE ONE NOW!</emphasis>
435 Messing with the PAM configuration files can make it nearly impossible to log in to your machine. That's
436 why you want to be able to boot back into your machine in single user mode and restore your
437 <filename>/etc/pam.d</filename> back to the original state they were in if you get frustrated with the
438 way things are going.
442 The latest version of Samba-3 includes a functioning winbindd daemon. Please refer to the <ulink
443 url="http://samba.org/">main Samba Web page</ulink> or, better yet, your closest Samba mirror site for
444 instructions on downloading the source code.
448 To allow domain users the ability to access Samba shares and files, as well as potentially other services
449 provided by your Samba machine, PAM must be set up properly on your
450 machine. In order to compile the Winbind modules, you should have at least the PAM development libraries installed
451 on your system. Please refer the PAM web site <ulink url="http://www.kernel.org/pub/linux/libs/pam/"/>.
456 <title>Testing Things Out</title>
459 Before starting, it is probably best to kill off all the Samba-related daemons running on your server.
460 Kill off all &smbd;, &nmbd;, and &winbindd; processes that may be running. To use PAM,
461 make sure that you have the standard PAM package that supplies the <filename>/etc/pam.d</filename>
462 directory structure, including the PAM modules that are used by PAM-aware services, several pam libraries,
463 and the <filename>/usr/doc</filename> and <filename>/usr/man</filename> entries for pam. Winbind built
464 better in Samba if the pam-devel package is also installed. This package includes the header files
465 needed to compile PAM-aware applications.
469 <title>Configure <filename>nsswitch.conf</filename> and the Winbind Libraries on Linux and Solaris</title>
472 PAM is a standard component of most current generation UNIX/Linux systems. Unfortunately, few systems install
473 the <filename>pam-devel</filename> libraries that are needed to build PAM-enabled Samba. Additionally, Samba-3
474 may auto-install the Winbind files into their correct locations on your system, so before you get too far down
475 the track be sure to check if the following configuration is really
476 necessary. You may only need to configure
477 <filename>/etc/nsswitch.conf</filename>.
481 The libraries needed to run the &winbindd; daemon through nsswitch need to be copied to their proper locations:
486 &rootprompt;<userinput>cp ../samba/source/nsswitch/libnss_winbind.so /lib</userinput>
491 I also found it necessary to make the following symbolic link:
495 &rootprompt; <userinput>ln -s /lib/libnss_winbind.so /lib/libnss_winbind.so.2</userinput>
498 <para>And, in the case of Sun Solaris:</para>
500 &rootprompt;<userinput>ln -s /usr/lib/libnss_winbind.so /usr/lib/libnss_winbind.so.1</userinput>
501 &rootprompt;<userinput>ln -s /usr/lib/libnss_winbind.so /usr/lib/nss_winbind.so.1</userinput>
502 &rootprompt;<userinput>ln -s /usr/lib/libnss_winbind.so /usr/lib/nss_winbind.so.2</userinput>
506 Now, as root you need to edit <filename>/etc/nsswitch.conf</filename> to
507 allow user and group entries to be visible from the &winbindd;
508 daemon. My <filename>/etc/nsswitch.conf</filename> file look like
512 <para><programlisting>
513 passwd: files winbind
516 </programlisting></para>
519 The libraries needed by the <command>winbindd</command> daemon will be automatically
520 entered into the <command>ldconfig</command> cache the next time
521 your system reboots, but it is faster (and you do not need to reboot) if you do it manually:
525 &rootprompt;<userinput>/sbin/ldconfig -v | grep winbind</userinput>
529 This makes <filename>libnss_winbind</filename> available to winbindd
530 and echos back a check to you.
536 <title>NSS Winbind on AIX</title>
538 <para>(This section is only for those running AIX.)</para>
541 The Winbind AIX identification module gets built as <filename>libnss_winbind.so</filename> in the
542 nsswitch directory of the Samba source. This file can be copied to <filename>/usr/lib/security</filename>,
543 and the AIX naming convention would indicate that it should be named WINBIND. A stanza like the following:
546 <para><programlisting>
548 program = /usr/lib/security/WINBIND
550 </programlisting></para>
553 can then be added to <filename>/usr/lib/security/methods.cfg</filename>. This module only supports
554 identification, but there have been success reports using the standard Winbind PAM module for
555 authentication. Use caution configuring loadable authentication
556 modules since you can make
557 it impossible to logon to the system. More information about the AIX authentication module API can
558 be found at <quote>Kernel Extensions and Device Support Programming Concepts for AIX</quote><ulink
559 url="http://publibn.boulder.ibm.com/doc_link/en_US/a_doc_lib/aixprggd/kernextc/sec_load_mod.htm">
560 in Chapter 18(John, there is no section like this in 18). Loadable Authentication Module Programming
561 Interface</ulink> and more information on administering the modules
562 can be found at <ulink
563 url="http://publibn.boulder.ibm.com/doc_link/en_US/a_doc_lib/aixbman/baseadmn/iandaadmin.htm"> <quote>System
564 Management Guide: Operating System and Devices.</quote></ulink>
569 <title>Configure smb.conf</title>
572 Several parameters are needed in the &smb.conf; file to control the behavior of &winbindd;. These
573 are described in more detail in the <citerefentry><refentrytitle>winbindd</refentrytitle>
574 <manvolnum>8</manvolnum></citerefentry> man page. My &smb.conf; file, as shown in <link
575 linkend="winbindcfg">the next example</link>, was modified to include the necessary entries in the [global] section.
579 <smbconfexample id="winbindcfg">
580 <title>smb.conf for Winbind set-up</title>
581 <smbconfsection>[global]</smbconfsection>
582 <member><...></member>
583 <smbconfcomment> separate domain and username with '\', like DOMAIN\username</smbconfcomment>
584 <smbconfoption name="winbind separator">\</smbconfoption>
585 <smbconfcomment> use uids from 10000 to 20000 for domain users</smbconfcomment>
586 <smbconfoption name="idmap uid">10000-20000</smbconfoption>
587 <smbconfcomment> use gids from 10000 to 20000 for domain groups</smbconfcomment>
588 <smbconfoption name="idmap gid">10000-20000</smbconfoption>
589 <smbconfcomment> allow enumeration of winbind users and groups</smbconfcomment>
590 <smbconfoption name="winbind enum users">yes</smbconfoption>
591 <smbconfoption name="winbind enum groups">yes</smbconfoption>
592 <smbconfcomment> give winbind users a real shell (only needed if they have telnet access)</smbconfcomment>
593 <smbconfoption name="template homedir">/home/winnt/%D/%U</smbconfoption>
594 <smbconfoption name="template shell">/bin/bash</smbconfoption>
595 </smbconfexample></para>
601 <title>Join the Samba Server to the PDC Domain</title>
604 All machines that will participate in domain security should be members of
605 the domain. This applies also to the PDC and all BDCs.
609 The process of joining a domain requires the use of the <command>net rpc join</command>
610 command. This process communicates with the domain controller it will register with
611 (usually the PDC) via MS DCE RPC. This means, of course, that the <command>smbd</command>
612 process must be running on the target DC. This means that it is necessary to temporarily
613 start Samba on a PDC so that it can join its own domain.
617 Enter the following command to make the Samba server join the
618 domain, where <replaceable>PDC</replaceable> is the name of
619 your PDC and <replaceable>Administrator</replaceable> is
620 a domain user who has administrative privileges in the domain.
624 Before attempting to join a machine to the domain verify that Samba is running
625 on the target DC (usually PDC) and that it is capable of being reached via ports
626 137/udp, 135/tcp, 139/tcp, and 445/tcp (if Samba or Windows Server 2Kx.
630 &rootprompt;<userinput>/usr/local/samba/bin/net rpc join -S PDC -U Administrator</userinput>
634 The proper response to the command should be: <quote>Joined the domain
635 <replaceable>DOMAIN</replaceable></quote> where <replaceable>DOMAIN</replaceable>
642 <title>Starting and Testing the <command>winbindd</command> Daemon</title>
645 Eventually, you will want to modify your Samba startup script to
646 automatically invoke the winbindd daemon when the other parts of
647 Samba start, but it is possible to test out just the Winbind
648 portion first. To start up Winbind services, enter the following
653 &rootprompt;<userinput>/usr/local/samba/sbin/winbindd</userinput>
657 The above assumes that Samba has been installed in the <filename>/usr/local/samba</filename>
658 directory tree. You may need to search for the location of Samba files if this is not the
659 location of <command>winbindd</command> on your system.
663 Winbindd can now also run in <quote>dual daemon mode</quote>. This will make it
664 run as two processes. The first will answer all requests from the cache,
665 thus making responses to clients faster. The other will
666 update the cache for the query that the first has just responded.
667 The advantage of this is that responses stay accurate and are faster.
668 You can enable dual daemon mode by adding <option>-B</option> to the command-line:
672 &rootprompt;<userinput>/usr/local/samba/sbin/winbindd -B</userinput>
676 I'm always paranoid and like to make sure the daemon is really running.
680 &rootprompt;<userinput>ps -ae | grep winbindd</userinput>
683 This command should produce output like this, if the daemon is running you would expect
684 to see a report something like this:
687 3025 ? 00:00:00 winbindd
691 Now, for the real test, try to get some information about the users on your PDC:
695 &rootprompt;<userinput>/usr/local/samba/bin/wbinfo -u</userinput>
699 This should echo back a list of users on your Windows users on
700 your PDC. For example, I get the following response:
713 Obviously, I have named my domain <quote>CEO</quote> and my <smbconfoption name="winbind separator"/> is <quote>\</quote>.
717 You can do the same sort of thing to get group information from the PDC:
721 &rootprompt;<userinput>/usr/local/samba/bin/wbinfo -g</userinput>
726 CEO\Domain Controllers
729 CEO\Enterprise Admins
730 CEO\Group Policy Creator Owners
734 The function <command>getent</command> can now be used to get unified
735 lists of both local and PDC users and groups. Try the following command:
739 &rootprompt;<userinput>getent passwd</userinput>
743 You should get a list that looks like your <filename>/etc/passwd</filename>
744 list followed by the domain users with their new UIDs, GIDs, home
745 directories and default shells.
749 The same thing can be done for groups with the command:
753 &rootprompt;<userinput>getent group</userinput>
760 <title>Fix the init.d Startup Scripts</title>
766 The &winbindd; daemon needs to start up after the &smbd; and &nmbd; daemons are running.
767 To accomplish this task, you need to modify the startup scripts of your system.
768 They are located at <filename>/etc/init.d/smb</filename> in Red Hat Linux and they are located in
769 <filename>/etc/init.d/samba</filename> in Debian Linux. Edit your
770 script to add commands to invoke this daemon in the proper sequence. My
771 startup script starts up &smbd;, &nmbd;, and &winbindd; from the
772 <filename>/usr/local/samba/bin</filename> directory directly. The <command>start</command>
773 function in the script looks like this:
776 <para><programlisting>
779 echo -n $"Starting $KIND services: "
780 daemon /usr/local/samba/bin/smbd $SMBDOPTIONS
784 echo -n $"Starting $KIND services: "
785 daemon /usr/local/samba/bin/nmbd $NMBDOPTIONS
789 echo -n $"Starting $KIND services: "
790 daemon /usr/local/samba/sbin/winbindd
793 [ $RETVAL -eq 0 -a $RETVAL2 -eq 0 -a $RETVAL3 -eq 0 ] && \
794 touch /var/lock/subsys/smb || RETVAL=1
797 </programlisting></para>
799 <para>If you would like to run winbindd in dual daemon mode, replace
802 daemon /usr/local/samba/sbin/winbindd
805 in the example above with:
808 daemon /usr/local/samba/sbin/winbindd -B
813 The <command>stop</command> function has a corresponding entry to shut down the
814 services and looks like this:
817 <para><programlisting>
820 echo -n $"Shutting down $KIND services: "
825 echo -n $"Shutting down $KIND services: "
830 echo -n $"Shutting down $KIND services: "
833 [ $RETVAL -eq 0 -a $RETVAL2 -eq 0 -a $RETVAL3 -eq 0 ] && \
834 rm -f /var/lock/subsys/smb
838 </programlisting></para>
842 <title>Solaris</title>
845 Winbind does not work on Solaris 9, see <link linkend="winbind-solaris9">Winbind on Solaris 9</link> section for details.
849 On Solaris, you need to modify the <filename>/etc/init.d/samba.server</filename> startup script. It
850 usually only starts smbd and nmbd but should now start winbindd, too. If you have Samba installed in
851 <filename>/usr/local/samba/bin</filename>, the file could contains something like this:
855 <smbfile name="samba.server.sh">
862 then # /usr not mounted
866 killproc() { # kill the named process(es)
867 pid=`/usr/bin/ps -e |
868 /usr/bin/grep -w $1 |
869 /usr/bin/sed -e 's/^ *//' -e 's/ .*//'`
870 [ "$pid" != "" ] && kill $pid
873 # Start/stop processes required for Samba server
879 # Edit these lines to suit your installation (paths, workgroup, host)
882 /usr/local/samba/bin/smbd -D -s \
883 /usr/local/samba/smb.conf
886 /usr/local/samba/bin/nmbd -D -l \
887 /usr/local/samba/var/log -s /usr/local/samba/smb.conf
889 echo Starting Winbind Daemon
890 /usr/local/samba/sbin/winbindd
900 echo "Usage: /etc/init.d/samba.server { start | stop }"
903 </programlisting></smbfile></para>
906 Again, if you would like to run Samba in dual daemon mode, replace:
908 /usr/local/samba/sbin/winbindd
910 in the script above with:
912 /usr/local/samba/sbin/winbindd -B
919 <title>Restarting</title>
921 If you restart the &smbd;, &nmbd;, and &winbindd; daemons at this point, you
922 should be able to connect to the Samba server as a Domain Member just as
923 if you were a local user.
929 <title>Configure Winbind and PAM</title>
932 If you have made it this far, you know that <command>winbindd</command> and Samba are working
933 together. If you want to use Winbind to provide authentication for other
934 services, keep reading. The PAM configuration files need to be altered in
935 this step. (Did you remember to make backups of your original
936 <filename>/etc/pam.d</filename> files? If not, do it now.)
940 You will need a PAM module to use winbindd with these other services. This
941 module will be compiled in the <filename>../source/nsswitch</filename> directory
942 by invoking the command:
946 &rootprompt;<userinput>make nsswitch/pam_winbind.so</userinput>
950 from the <filename>../source</filename> directory. The
951 <filename>pam_winbind.so</filename> file should be copied to the location of
952 your other PAM security modules. On my Red Hat system, this was the
953 <filename>/lib/security</filename> directory. On Solaris, the PAM security
954 modules reside in <filename>/usr/lib/security</filename>.
958 &rootprompt;<userinput>cp ../samba/source/nsswitch/pam_winbind.so /lib/security</userinput>
962 <title>Linux/FreeBSD-specific PAM configuration</title>
965 The <filename>/etc/pam.d/samba</filename> file does not need to be changed. I
966 just left this file as it was:
970 <para><programlisting>
971 auth required /lib/security/pam_stack.so service=system-auth
972 account required /lib/security/pam_stack.so service=system-auth
973 </programlisting></para>
976 The other services that I modified to allow the use of Winbind
977 as an authentication service were the normal login on the console (or a terminal
978 session), telnet logins, and ftp service. In order to enable these
979 services, you may first need to change the entries in
980 <filename>/etc/xinetd.d</filename> (or <filename>/etc/inetd.conf</filename>).
981 Red Hat Linux 7.1 and later uses the new xinetd.d structure, in this case you need
982 to change the lines in <filename>/etc/xinetd.d/telnet</filename>
983 and <filename>/etc/xinetd.d/wu-ftp</filename> from
986 <para><programlisting>
992 </programlisting></para>
995 For ftp services to work properly, you will also need to either
996 have individual directories for the domain users already present on
997 the server, or change the home directory template to a general
998 directory for all domain users. These can be easily set using
999 the &smb.conf; global entry
1000 <smbconfoption name="template homedir"/>.
1004 <para>The directory in <smbconfoption name="template homedir"/> is not created automatically! Use pam_mkhomedir or pre-create
1005 the directories of users to make sure users can log in on UNIX with
1006 their own home directory.
1011 The <filename>/etc/pam.d/ftp</filename> file can be changed
1012 to allow Winbind ftp access in a manner similar to the
1013 samba file. My <filename>/etc/pam.d/ftp</filename> file was
1014 changed to look like this:
1017 <para><smbfile name="pam.ftp.winbind"><programlisting>
1018 auth required /lib/security/pam_listfile.so item=user sense=deny \
1019 file=/etc/ftpusers onerr=succeed
1020 auth sufficient /lib/security/pam_winbind.so
1021 auth required /lib/security/pam_stack.so service=system-auth
1022 auth required /lib/security/pam_shells.so
1023 account sufficient /lib/security/pam_winbind.so
1024 account required /lib/security/pam_stack.so service=system-auth
1025 session required /lib/security/pam_stack.so service=system-auth
1026 </programlisting></smbfile></para>
1029 The <filename>/etc/pam.d/login</filename> file can be changed nearly the
1030 same way. It now looks like this:
1033 <para><smbfile name="pam.login.winbind"><programlisting>
1034 auth required /lib/security/pam_securetty.so
1035 auth sufficient /lib/security/pam_winbind.so
1036 auth sufficient /lib/security/pam_unix.so use_first_pass
1037 auth required /lib/security/pam_stack.so service=system-auth
1038 auth required /lib/security/pam_nologin.so
1039 account sufficient /lib/security/pam_winbind.so
1040 account required /lib/security/pam_stack.so service=system-auth
1041 password required /lib/security/pam_stack.so service=system-auth
1042 session required /lib/security/pam_stack.so service=system-auth
1043 session optional /lib/security/pam_console.so
1044 </programlisting></smbfile></para>
1047 In this case, I added the <programlisting>auth sufficient /lib/security/pam_winbind.so</programlisting>
1048 lines as before, but also added the <programlisting>required pam_securetty.so</programlisting>
1049 above it, to disallow root logins over the network. I also added a
1050 <programlisting>sufficient /lib/security/pam_unix.so use_first_pass</programlisting>
1051 line after the <command>winbind.so</command> line to get rid of annoying
1052 double prompts for passwords.
1058 <title>Solaris-specific configuration</title>
1061 The <filename>/etc/pam.conf</filename> needs to be changed. I changed this file so my Domain
1062 users can logon both locally as well as telnet. The following are the changes
1063 that I made. You can customize the <filename>pam.conf</filename> file as per your requirements, but
1064 be sure of those changes because in the worst case it will leave your system
1065 nearly impossible to boot.
1068 <para><programlisting>
1070 #ident "@(#)pam.conf 1.14 99/09/16 SMI"
1072 # Copyright (c) 1996-1999, Sun Microsystems, Inc.
1073 # All Rights Reserved.
1077 # Authentication management
1079 login auth required /usr/lib/security/pam_winbind.so
1080 login auth required /usr/lib/security/$ISA/pam_unix.so.1 try_first_pass
1081 login auth required /usr/lib/security/$ISA/pam_dial_auth.so.1 try_first_pass
1083 rlogin auth sufficient /usr/lib/security/pam_winbind.so
1084 rlogin auth sufficient /usr/lib/security/$ISA/pam_rhosts_auth.so.1
1085 rlogin auth required /usr/lib/security/$ISA/pam_unix.so.1 try_first_pass
1087 dtlogin auth sufficient /usr/lib/security/pam_winbind.so
1088 dtlogin auth required /usr/lib/security/$ISA/pam_unix.so.1 try_first_pass
1090 rsh auth required /usr/lib/security/$ISA/pam_rhosts_auth.so.1
1091 other auth sufficient /usr/lib/security/pam_winbind.so
1092 other auth required /usr/lib/security/$ISA/pam_unix.so.1 try_first_pass
1094 # Account management
1096 login account sufficient /usr/lib/security/pam_winbind.so
1097 login account requisite /usr/lib/security/$ISA/pam_roles.so.1
1098 login account required /usr/lib/security/$ISA/pam_unix.so.1
1100 dtlogin account sufficient /usr/lib/security/pam_winbind.so
1101 dtlogin account requisite /usr/lib/security/$ISA/pam_roles.so.1
1102 dtlogin account required /usr/lib/security/$ISA/pam_unix.so.1
1104 other account sufficient /usr/lib/security/pam_winbind.so
1105 other account requisite /usr/lib/security/$ISA/pam_roles.so.1
1106 other account required /usr/lib/security/$ISA/pam_unix.so.1
1108 # Session management
1110 other session required /usr/lib/security/$ISA/pam_unix.so.1
1112 # Password management
1114 #other password sufficient /usr/lib/security/pam_winbind.so
1115 other password required /usr/lib/security/$ISA/pam_unix.so.1
1116 dtsession auth required /usr/lib/security/$ISA/pam_unix.so.1
1118 # Support for Kerberos V5 authentication (uncomment to use Kerberos)
1120 #rlogin auth optional /usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass
1121 #login auth optional /usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass
1122 #dtlogin auth optional /usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass
1123 #other auth optional /usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass
1124 #dtlogin account optional /usr/lib/security/$ISA/pam_krb5.so.1
1125 #other account optional /usr/lib/security/$ISA/pam_krb5.so.1
1126 #other session optional /usr/lib/security/$ISA/pam_krb5.so.1
1127 #other password optional /usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass
1128 </programlisting></para>
1131 I also added a <parameter>try_first_pass</parameter> line after the <filename>winbind.so</filename>
1132 line to get rid of annoying double prompts for passwords.
1136 Now restart your Samba and try connecting through your application that you
1137 configured in the pam.conf.
1149 <title>Conclusion</title>
1151 <para>The Winbind system, through the use of the Name Service
1152 Switch, Pluggable Authentication Modules, and appropriate
1153 Microsoft RPC calls have allowed us to provide seamless
1154 integration of Microsoft Windows NT domain users on a
1155 UNIX system. The result is a great reduction in the administrative
1156 cost of running a mixed UNIX and NT network.</para>
1161 <title>Common Errors</title>
1163 <para>Winbind has a number of limitations in its current
1164 released version that we hope to overcome in future
1168 <listitem><para>Winbind is currently only available for
1169 the Linux, Solaris, AIX, and IRIX operating systems, although ports to other operating
1170 systems are certainly possible. For such ports to be feasible,
1171 we require the C library of the target operating system to
1172 support the Name Service Switch and Pluggable Authentication
1173 Modules systems. This is becoming more common as NSS and
1174 PAM gain support among UNIX vendors.</para></listitem>
1176 <listitem><para>The mappings of Windows NT RIDs to UNIX IDs
1177 is not made algorithmically and depends on the order in which
1178 unmapped users or groups are seen by Winbind. It may be difficult
1179 to recover the mappings of RID to UNIX ID mapping if the file
1180 containing this information is corrupted or destroyed.</para>
1183 <listitem><para>Currently the Winbind PAM module does not take
1184 into account possible workstation and logon time restrictions
1185 that may be set for Windows NT users, this is
1186 instead up to the PDC to enforce.</para></listitem>
1190 <title>NSCD Problem Warning</title>
1192 <?latex \nopagebreak ?>
1195 Do not under any circumstances run <command>nscd</command> on any system
1196 on which <command>winbindd</command> is running.
1200 If <command>nscd</command> is running on the UNIX/Linux system, then
1201 even though NSSWITCH is correctly configured it will not be possible to resolve
1202 domain users and groups for file and directory controls.
1208 <title>Winbind Is Not Resolving Users and Groups</title>
1211 My &smb.conf; file is correctly configured. I have specified
1212 <smbconfoption name="idmap uid">12000</smbconfoption>,
1213 and <smbconfoption name="idmap gid">3000-3500</smbconfoption>
1214 and <command>winbind</command> is running. When I do the following it all works fine.
1218 &rootprompt;<userinput>wbinfo -u</userinput>
1225 &rootprompt;<userinput>wbinfo -g</userinput>
1226 MIDEARTH\Domain Users
1227 MIDEARTH\Domain Admins
1228 MIDEARTH\Domain Guests
1232 &rootprompt;<userinput>getent passwd</userinput>
1233 root:x:0:0:root:/root:/bin/bash
1234 bin:x:1:1:bin:/bin:/bin/bash
1236 maryo:x:15000:15003:Mary Orville:/home/MIDEARTH/maryo:/bin/false
1240 But the following command just fails:
1243 &rootprompt;<userinput>chown maryo a_file</userinput>
1244 chown: `maryo': invalid user
1247 This is driving me nuts! What can be wrong?
1251 Same problem as the one above.
1252 Your system is likely running <command>nscd</command>, the name service
1253 caching daemon. Shut it down, do not restart it! You will find your problem resolved.