| blob | 13cc2a14185c0332760f2a1de6e63fd0f1877709 |
1 <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 24. Winbind: Use of Domain Accounts</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.70.1"><link rel="start" href="index.html" title="The Official Samba-3 HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part III. Advanced Configuration"><link rel="prev" href="VFS.html" title="Chapter 23. Stackable VFS modules"><link rel="next" href="AdvancedNetworkManagement.html" title="Chapter 25. Advanced Network Management"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 24. Winbind: Use of Domain Accounts</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="VFS.html">Prev</a> </td><th width="60%" align="center">Part III. Advanced Configuration</th><td width="20%" align="right"> <a accesskey="n" href="AdvancedNetworkManagement.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="winbind"></a>Chapter 24. Winbind: Use of Domain Accounts</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Tim</span> <span class="surname">Potter</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email"><<a href="mailto:tpot@linuxcare.com.au">tpot@linuxcare.com.au</a>></code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Andrew</span> <span class="surname">Tridgell</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email"><<a href="mailto:tridge@samba.org">tridge@samba.org</a>></code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Naag</span> <span class="surname">Mummaneni</span></h3><span class="contrib">Notes for Solaris</span><div class="affiliation"><div class="address"><p><code class="email"><<a href="mailto:getnag@rediffmail.com">getnag@rediffmail.com</a>></code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="surname">Trostel</span></h3><div class="affiliation"><span class="orgname">SNAP<br></span><div class="address"><p><code class="email"><<a href="mailto:jtrostel@snapserver.com">jtrostel@snapserver.com</a>></code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><code class="email"><<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>></code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email"><<a href="mailto:jht@samba.org">jht@samba.org</a>></code></p></div></div></div></div><div><p class="pubdate">June 15, 2005</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="winbind.html#id2656149">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="winbind.html#id2656492">Introduction</a></span></dt><dt><span class="sect1"><a href="winbind.html#id2656582">What Winbind Provides</a></span></dt><dd><dl><dt><span class="sect2"><a href="winbind.html#id2656736">Target Uses</a></span></dt><dt><span class="sect2"><a href="winbind.html#id2656781">Handling of Foreign SIDs</a></span></dt></dl></dd><dt><span class="sect1"><a href="winbind.html#id2656917">How Winbind Works</a></span></dt><dd><dl><dt><span class="sect2"><a href="winbind.html#id2656968">Microsoft Remote Procedure Calls</a></span></dt><dt><span class="sect2"><a href="winbind.html#id2657054">Microsoft Active Directory Services</a></span></dt><dt><span class="sect2"><a href="winbind.html#id2657102">Name Service Switch</a></span></dt><dt><span class="sect2"><a href="winbind.html#id2657335">Pluggable Authentication Modules</a></span></dt><dt><span class="sect2"><a href="winbind.html#id2657491">User and Group ID Allocation</a></span></dt><dt><span class="sect2"><a href="winbind.html#id2657568">Result Caching</a></span></dt></dl></dd><dt><span class="sect1"><a href="winbind.html#id2657625">Installation and Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="winbind.html#id2657631">Introduction</a></span></dt><dt><span class="sect2"><a href="winbind.html#id2657746">Requirements</a></span></dt><dt><span class="sect2"><a href="winbind.html#id2657898">Testing Things Out</a></span></dt></dl></dd><dt><span class="sect1"><a href="winbind.html#id2660398">Conclusion</a></span></dt><dt><span class="sect1"><a href="winbind.html#id2660446">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="winbind.html#id2660490">NSCD Problem Warning</a></span></dt><dt><span class="sect2"><a href="winbind.html#id2660526">Winbind Is Not Resolving Users and Groups</a></span></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2656149"></a>Features and Benefits</h2></div></div></div><p>
4 Integration of UNIX and Microsoft Windows NT through a unified logon has
5 been considered a “<span class="quote">holy grail</span>” in heterogeneous computing environments for
6 a long time.
7 </p><p>
12 There is one other facility without which UNIX and Microsoft Windows network
13 interoperability would suffer greatly. It is imperative that there be a
14 mechanism for sharing files across UNIX systems and to be able to assign
15 domain user and group ownerships with integrity.
16 </p><p>
21 <span class="emphasis"><em>winbind</em></span> is a component of the Samba suite of programs that
22 solves the unified logon problem. Winbind uses a UNIX implementation of Microsoft
23 RPC calls, Pluggable Authentication Modules (PAMs), and the name service switch (NSS) to
24 allow Windows NT domain users to appear and operate as UNIX users on a UNIX
25 machine. This chapter describes the Winbind system, the functionality
26 it provides, how it is configured, and how it works internally.
27 </p><p>
28 Winbind provides three separate functions:
32 Authentication of user credentials (via PAM). This makes it possible to
33 log onto a UNIX/Linux system using user and group accounts from a Windows
34 NT4 (including a Samba domain) or an Active Directory domain.
35 </p></li><li><p>
38 Identity resolution (via NSS). This is the default when winbind is not used.
39 </p></li><li><p>
47 Winbind maintains a database called winbind_idmap.tdb in which it stores
48 mappings between UNIX UIDs, GIDs, and NT SIDs. This mapping is used only
49 for users and groups that do not have a local UID/GID. It stores the UID/GID
50 allocated from the idmap uid/gid range that it has mapped to the NT SID.
51 If <em class="parameter"><code>idmap backend</code></em> has been specified as <code class="constant">ldap:ldap://hostname[:389]</code>,
52 then instead of using a local mapping, Winbind will obtain this information
53 from the LDAP database.
54 </p></li></ul></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
61 If <span><strong class="command">winbindd</strong></span> is not running, smbd (which calls <span><strong class="command">winbindd</strong></span>) will fall back to
62 using purely local information from <code class="filename">/etc/passwd</code> and <code class="filename">/etc/group</code> and no dynamic
63 mapping will be used. On an operating system that has been enabled with the NSS,
64 the resolution of user and group information will be accomplished via NSS.
65 </p></div><div class="figure"><a name="winbind_idmap"></a><p class="title"><b>Figure 24.1. Winbind Idmap</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/idmap_winbind_no_loop.png" width="243" alt="Winbind Idmap"></div></div></div><br class="figure-break"></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2656492"></a>Introduction</h2></div></div></div><p>It is well known that UNIX and Microsoft Windows NT have
66 different models for representing user and group information and
67 use different technologies for implementing them. This fact has
68 made it difficult to integrate the two systems in a satisfactory
69 manner.</p><p>
72 One common solution in use today has been to create
73 identically named user accounts on both the UNIX and Windows systems
74 and use the Samba suite of programs to provide file and print services
75 between the two. This solution is far from perfect, however, because
76 adding and deleting users on both sets of machines becomes a chore,
77 and two sets of passwords are required both of which
78 can lead to synchronization problems between the UNIX and Windows
79 systems and confusion for users.</p><p>We divide the unified logon problem for UNIX machines into
80 three smaller problems:</p><div class="itemizedlist"><ul type="disc"><li><p>Obtaining Windows NT user and group information.
81 </p></li><li><p>Authenticating Windows NT users.
82 </p></li><li><p>Password changing for Windows NT users.
83 </p></li></ul></div><p>
86 Ideally, a prospective solution to the unified logon problem
87 would satisfy all the above components without duplication of
88 information on the UNIX machines and without creating additional
89 tasks for the system administrator when maintaining users and
90 groups on either system. The Winbind system provides a simple
91 and elegant solution to all three components of the unified logon
92 problem.</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2656582"></a>What Winbind Provides</h2></div></div></div><p>
97 Winbind unifies UNIX and Windows NT account management by
98 allowing a UNIX box to become a full member of an NT domain. Once
99 this is done, the UNIX box will see NT users and groups as if
100 they were “<span class="quote">native</span>” UNIX users and groups, allowing the NT domain
101 to be used in much the same manner that NIS+ is used within
102 UNIX-only environments.</p><p>
107 The end result is that whenever a
108 program on the UNIX machine asks the operating system to look up
109 a user or group name, the query will be resolved by asking the
110 NT domain controller for the specified domain to do the lookup.
111 Because Winbind hooks into the operating system at a low level
112 (via the NSS name resolution modules in the C library), this
113 redirection to the NT domain controller is completely
114 transparent.</p><p>
117 Users on the UNIX machine can then use NT user and group
118 names as they would “<span class="quote">native</span>” UNIX names. They can chown files
119 so they are owned by NT domain users or even login to the
120 UNIX machine and run a UNIX X-Window session as a domain user.</p><p>
122 The only obvious indication that Winbind is being used is
124 <code class="constant">DOMAIN\group</code>. This is necessary because it allows Winbind to determine
125 that redirection to a domain controller is wanted for a particular
126 lookup and which trusted domain is being referenced.</p><p>
129 Additionally, Winbind provides an authentication service that hooks into the PAM system
130 to provide authentication via an NT domain to any PAM-enabled
131 applications. This capability solves the problem of synchronizing
132 passwords between systems, since all passwords are stored in a single
133 location (on the domain controller).</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2656736"></a>Target Uses</h3></div></div></div><p>
135 Winbind is targeted at organizations that have an
136 existing NT-based domain infrastructure into which they wish
137 to put UNIX workstations or servers. Winbind will allow these
138 organizations to deploy UNIX workstations without having to
139 maintain a separate account infrastructure. This greatly
140 simplifies the administrative overhead of deploying UNIX
141 workstations into an NT-based organization.</p><p>
144 Another interesting way in which we expect Winbind to
145 be used is as a central part of UNIX-based appliances. Appliances
146 that provide file and print services to Microsoft-based networks
147 will be able to use Winbind to provide seamless integration of
148 the appliance into the domain.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2656781"></a>Handling of Foreign SIDs</h3></div></div></div><p>
150 The term <span class="emphasis"><em>foreign SID</em></span> is often met with the reaction that it
151 is not relevant to a particular environment. The following documents an interchange
152 that took place on the Samba mailing list. It is a good example of the confusion
153 often expressed regarding the use of winbind.
154 </p><p>
156 Fact: Winbind is needed to handle users who use workstations that are NOT part
157 of the local domain.
158 </p><p>
160 Response: “<span class="quote">Why? I've used Samba with workstations that are not part of my domains
161 lots of times without using winbind. I thought winbind was for using Samba as a member server
163 </p><p>
167 If the Samba server will be accessed from a domain other than the local Samba domain, or
168 if there will be access from machines that are not local domain members, winbind will
169 permit the allocation of UIDs and GIDs from the assigned pool that will keep the identity
170 of the foreign user separate from users that are members of the Samba domain.
171 </p><p>
176 This means that winbind is eminently useful in cases where a single
177 Samba PDC on a local network is combined with both domain member and domain non-member workstations.
178 If winbind is not used, the user george on a Windows workstation that is not a domain
179 member will be able to access the files of a user called george in the account database
180 of the Samba server that is acting as a PDC. When winbind is used, the default condition
181 is that the local user george will be treated as the account DOMAIN\george and the
182 foreign (non-member of the domain) account will be treated as MACHINE\george because
183 each has a different SID.
184 </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2656917"></a>How Winbind Works</h2></div></div></div><p>
189 The Winbind system is designed around a client/server
191 listens on a UNIX domain socket waiting for requests
192 to arrive. These requests are generated by the NSS and PAM
193 clients and are processed sequentially.</p><p>The technologies used to implement Winbind are described
194 in detail below.</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2656968"></a>Microsoft Remote Procedure Calls</h3></div></div></div><p>
200 Over the last few years, efforts have been underway by various Samba Team members to implement various aspects of
201 the Microsoft Remote Procedure Call (MSRPC) system. This system is used for most network-related operations
202 between Windows NT machines, including remote management, user authentication, and print spooling. Although
203 initially this work was done to aid the implementation of Primary Domain Controller (PDC) functionality in
204 Samba, it has also yielded a body of code that can be used for other purposes.
205 </p><p>
209 Winbind uses various MSRPC calls to enumerate domain users and groups and to obtain detailed information about
210 individual users or groups. Other MSRPC calls can be used to authenticate NT domain users and to change user
211 passwords. By directly querying a Windows PDC for user and group information, Winbind maps the NT account
212 information onto UNIX user and group names.
213 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2657054"></a>Microsoft Active Directory Services</h3></div></div></div><p>
218 Since late 2001, Samba has gained the ability to interact with Microsoft Windows 2000 using its “<span class="quote">native
219 mode</span>” protocols rather than the NT4 RPC services. Using LDAP and Kerberos, a domain member running
220 Winbind can enumerate users and groups in exactly the same way as a Windows 200x client would, and in so doing
221 provide a much more efficient and effective Winbind implementation.
222 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2657102"></a>Name Service Switch</h3></div></div></div><p>
227 The NSS is a feature that is present in many UNIX operating systems. It allows system
228 information such as hostnames, mail aliases, and user information
229 to be resolved from different sources. For example, a standalone
230 UNIX workstation may resolve system information from a series of
231 flat files stored on the local file system. A networked workstation
232 may first attempt to resolve system information from local files,
233 and then consult an NIS database for user information or a DNS server
234 for hostname information.</p><p>
240 The NSS application programming interface allows Winbind
241 to present itself as a source of system information when
242 resolving UNIX usernames and groups. Winbind uses this interface
243 and information obtained from a Windows NT server using MSRPC
244 calls to provide a new source of account enumeration. Using standard
245 UNIX library calls, you can enumerate the users and groups on
246 a UNIX machine running Winbind and see all users and groups in
247 an NT domain plus any trusted domain as though they were local
248 users and groups.</p><p>
253 When a UNIX application makes a request to do a lookup,
255 for a line that matches the service type being requested; for
256 example, the “<span class="quote">passwd</span>” service type is used when user or group names
257 are looked up. This config line specifies which implementations
258 of that service should be tried and in what order. If the passwd
259 config line is:
261 passwd: files example
262 </pre><p>
266 then the C library will first load a module called
269 C library will dynamically load each of these modules in turn
270 and call resolver functions within the modules to try to resolve
271 the request. Once the request is resolved, the C library returns the
272 result to the application.</p><p>
276 This NSS interface provides an easy way for Winbind
277 to hook into the operating system. All that needs to be done
278 is to put <code class="filename">libnss_winbind.so</code> in <code class="filename">/lib/</code>
279 then add “<span class="quote">winbind</span>” into <code class="filename">/etc/nsswitch.conf</code> at
280 the appropriate place. The C library will then call Winbind to
281 resolve user and group names.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2657335"></a>Pluggable Authentication Modules</h3></div></div></div><p>
286 PAMs provide a system for abstracting authentication and authorization
287 technologies. With a PAM module, it is possible to specify different
288 authentication methods for different system applications without
289 having to recompile these applications. PAM is also useful
290 for implementing a particular policy for authorization. For example,
291 a system administrator may only allow console logins from users
292 stored in the local password file but only allow users resolved from
293 an NIS database to log in over the network.</p><p>
299 Winbind uses the authentication management and password
300 management PAM interface to integrate Windows NT users into a
301 UNIX system. This allows Windows NT users to log in to a UNIX
302 machine and be authenticated against a suitable PDC.
303 These users can also change their passwords and have
304 this change take effect directly on the PDC.
305 </p><p>
310 PAM is configured by providing control files in the directory
312 require authentication. When an authentication request is made
313 by an application, the PAM code in the C library looks up this
314 control file to determine what modules to load to do the
315 authentication check and in what order. This interface makes adding
316 a new authentication service for Winbind very easy: simply copy
319 control files for relevant services are updated to allow
320 authentication via Winbind. See the PAM documentation
321 in <a href="pam.html" title="Chapter 28. PAM-Based Distributed Authentication">PAM-Based Distributed Authentication</a>, for more information.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2657491"></a>User and Group ID Allocation</h3></div></div></div><p>
325 When a user or group is created under Windows NT/200x,
326 it is allocated a numerical relative identifier (RID). This is
327 slightly different from UNIX, which has a range of numbers that are
328 used to identify users and the same range used to identify
329 groups. It is Winbind's job to convert RIDs to UNIX ID numbers and
330 vice versa. When Winbind is configured, it is given part of the UNIX
331 user ID space and a part of the UNIX group ID space in which to
332 store Windows NT users and groups. If a Windows NT user is
333 resolved for the first time, it is allocated the next UNIX ID from
334 the range. The same process applies for Windows NT groups. Over
335 time, Winbind will have mapped all Windows NT users and groups
336 to UNIX user IDs and group IDs.</p><p>
341 The results of this mapping are stored persistently in
342 an ID mapping database held in a tdb database. This ensures that
343 RIDs are mapped to UNIX IDs in a consistent way.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2657568"></a>Result Caching</h3></div></div></div><p>
349 An active directory system can generate a lot of user and group
350 name lookups. To reduce the network cost of these lookups, Winbind
351 uses a caching scheme based on the SAM sequence number supplied
352 by NT domain controllers. User or group information returned
353 by a PDC is cached by Winbind along with a sequence number also
354 returned by the PDC. This sequence number is incremented by
355 Windows NT whenever any user or group information is modified. If
356 a cached entry has expired, the sequence number is requested from
357 the PDC and compared against the sequence number of the cached entry.
358 If the sequence numbers do not match, then the cached information
359 is discarded and up-to-date information is requested directly
360 from the PDC.</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2657625"></a>Installation and Configuration</h2></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2657631"></a>Introduction</h3></div></div></div><p>
364 This section describes the procedures used to get Winbind up and
365 running. Winbind is capable of providing access
366 and authentication control for Windows Domain users through an NT
367 or Windows 200x PDC for regular services, such as telnet and ftp, as
368 well for Samba services.
371 </p><p>
376 This allows the Samba administrator to rely on the
377 authentication mechanisms on the Windows NT/200x PDC for the authentication
378 of domain members. Windows NT/200x users no longer need to have separate
379 accounts on the Samba server.
380 </p></li><li><p>
382 </p><p>
385 This document is designed for system administrators. If you are
386 implementing Samba on a file server and wish to (fairly easily)
387 integrate existing Windows NT/200x users from your PDC onto the
388 Samba server, this document is for you.
389 </p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2657746"></a>Requirements</h3></div></div></div><p>
393 If you have a Samba configuration file that you are currently using, <span class="emphasis"><em>BACK IT UP!</em></span>
394 If your system already uses PAM, <span class="emphasis"><em>back up the <code class="filename">/etc/pam.d</code> directory
395 contents!</em></span> If you haven't already made a boot disk, <span class="emphasis"><em>MAKE ONE NOW!</em></span>
396 </p><p>
400 Messing with the PAM configuration files can make it nearly impossible to log in to your machine. That's
401 why you want to be able to boot back into your machine in single-user mode and restore your
402 <code class="filename">/etc/pam.d</code> to the original state it was in if you get frustrated with the
403 way things are going.
404 </p><p>
407 The latest version of Samba-3 includes a functioning winbindd daemon. Please refer to the <a href="http://samba.org/" target="_top">main Samba Web page</a>, or better yet, your closest Samba mirror site for
408 instructions on downloading the source code.
409 </p><p>
414 To allow domain users the ability to access Samba shares and files, as well as potentially other services
415 provided by your Samba machine, PAM must be set up properly on your
416 machine. In order to compile the Winbind modules, you should have at least the PAM development libraries installed
417 on your system. Please refer to the PAM Web site <a href="http://www.kernel.org/pub/linux/libs/pam/" target="_top">http://www.kernel.org/pub/linux/libs/pam/</a>.
418 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2657898"></a>Testing Things Out</h3></div></div></div><p>
424 Before starting, it is probably best to kill off all the Samba-related daemons running on your server.
425 Kill off all <span class="application">smbd</span>, <span class="application">nmbd</span>, and <span class="application">winbindd</span> processes that may be running. To use PAM,
426 make sure that you have the standard PAM package that supplies the <code class="filename">/etc/pam.d</code>
427 directory structure, including the PAM modules that are used by PAM-aware services, several PAM libraries,
428 and the <code class="filename">/usr/doc</code> and <code class="filename">/usr/man</code> entries for PAM. Winbind is built
429 better in Samba if the pam-devel package is also installed. This package includes the header files
430 needed to compile PAM-aware applications.
431 </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2657984"></a>Configure <code class="filename">nsswitch.conf</code> and the Winbind Libraries on Linux and Solaris</h4></div></div></div><p>
436 PAM is a standard component of most current generation UNIX/Linux systems. Unfortunately, few systems install
437 the <code class="filename">pam-devel</code> libraries that are needed to build PAM-enabled Samba. Additionally, Samba-3
438 may auto-install the Winbind files into their correct locations on your system, so before you get too far down
439 the track, be sure to check if the following configuration is really
440 necessary. You may only need to configure
442 </p><p>
443 The libraries needed to run the <span class="application">winbindd</span> daemon through nsswitch need to be copied to their proper locations:
444 </p><p>
447 <code class="prompt">root# </code><strong class="userinput"><code>cp ../samba/source/nsswitch/libnss_winbind.so /lib</code></strong>
448 </pre><p>
449 </p><p>
450 I also found it necessary to make the following symbolic link:
451 </p><p>
452 <code class="prompt">root# </code> <strong class="userinput"><code>ln -s /lib/libnss_winbind.so /lib/libnss_winbind.so.2</code></strong>
453 </p><p>And, in the case of Sun Solaris:
456 <code class="prompt">root# </code><strong class="userinput"><code>ln -s /usr/lib/libnss_winbind.so /usr/lib/libnss_winbind.so.1</code></strong>
457 <code class="prompt">root# </code><strong class="userinput"><code>ln -s /usr/lib/libnss_winbind.so /usr/lib/nss_winbind.so.1</code></strong>
458 <code class="prompt">root# </code><strong class="userinput"><code>ln -s /usr/lib/libnss_winbind.so /usr/lib/nss_winbind.so.2</code></strong>
459 </pre><p>
460 </p><p>
465 this after editing:
467 passwd: files winbind
468 shadow: files
469 group: files winbind
470 </pre><p>
476 The libraries needed by the <span><strong class="command">winbindd</strong></span> daemon will be automatically
478 your system reboots, but it is faster (and you do not need to reboot) if you do it manually:
480 <code class="prompt">root# </code><strong class="userinput"><code>/sbin/ldconfig -v | grep winbind</code></strong>
481 </pre><p>
482 This makes <code class="filename">libnss_winbind</code> available to winbindd and reports the current
483 search path that is used by the dynamic link loader. The use of the <span><strong class="command">grep</strong></span>
484 filters the output of the <span><strong class="command">ldconfig</strong></span> command so that we may see proof that
485 this library is indeed recognized by the dynamic link loader.
486 </p><p>
492 The Sun Solaris dynamic link loader management tool is called <span><strong class="command">crle</strong></span>. The
493 use of this tool is necessary to instruct the dynamic link loader to search directories that
494 contain library files that were not supplied as part of the original operating system platform.
495 The following example shows how to use this tool to add the directory <code class="filename">/usr/local/lib</code>
496 to the dynamic link loader's search path:
499 </pre><p>
500 When executed without arguments, <span><strong class="command">crle</strong></span> reports the current dynamic
501 link loader configuration. This is demonstrated here:
505 Configuration file [version 4]: /var/ld/ld.config
506 Default Library Path (ELF): /lib:/usr/lib:/usr/local/lib
507 Trusted Directories (ELF): /lib/secure:/usr/lib/secure (system default)
509 Command line:
510 crle -c /var/ld/ld.config -l /lib:/usr/lib:/usr/local/lib
511 </pre><p>
512 From this it is apparent that the <code class="filename">/usr/local/lib</code> directory is included
513 in the search dynamic link libraries in order to satisfy object module dependencies.
514 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2658383"></a>NSS Winbind on AIX</h4></div></div></div><p>(This section is only for those running AIX.)</p><p>
521 The Winbind AIX identification module gets built as <code class="filename">libnss_winbind.so</code> in the
522 nsswitch directory of the Samba source. This file can be copied to <code class="filename">/usr/lib/security</code>,
523 and the AIX naming convention would indicate that it should be named WINBIND. A stanza like the following:
525 WINBIND:
526 program = /usr/lib/security/WINBIND
527 options = authonly
528 </pre><p>
529 can then be added to <code class="filename">/usr/lib/security/methods.cfg</code>. This module only supports
530 identification, but there have been reports of success using the standard Winbind PAM module for
531 authentication. Use caution configuring loadable authentication modules, since misconfiguration can make
532 it impossible to log on to the system. Information regarding the AIX authentication module API can
533 be found in the “<span class="quote">Kernel Extensions and Device Support Programming Concepts for AIX</span>” document that
534 describes the <a href="http://publibn.boulder.ibm.com/doc_link/en_US/a_doc_lib/aixprggd/kernextc/sec_load_mod.htm" target="_top">
535 Loadable Authentication Module Programming Interface</a> for AIX. Further information on administering the modules
536 can be found in the <a href="http://publibn.boulder.ibm.com/doc_link/en_US/a_doc_lib/aixbman/baseadmn/iandaadmin.htm" target="_top">System
537 Management Guide: Operating System and Devices.</a>
538 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2658496"></a>Configure smb.conf</h4></div></div></div><p>
542 Several parameters are needed in the <code class="filename">smb.conf</code> file to control the behavior of <span class="application">winbindd</span>. These
543 are described in more detail in the <a href="winbindd.8.html"><span class="citerefentry"><span class="refentrytitle">winbindd</span>(8)</span></a> man page. My <code class="filename">smb.conf</code> file, as shown in <a href="winbind.html#winbindcfg" title="Example 24.1. smb.conf for Winbind Setup">the smb.conf for Winbind Setup</a>, was modified to include the necessary entries in the [global] section.
544 </p><div class="example"><a name="winbindcfg"></a><p class="title"><b>Example 24.1. smb.conf for Winbind Setup</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td># separate domain and username with '\', like DOMAIN\username</td></tr><tr><td><a class="indexterm" name="id2658591"></a><em class="parameter"><code>winbind separator = \</code></em></td></tr><tr><td># use uids from 10000 to 20000 for domain users</td></tr><tr><td><a class="indexterm" name="id2658608"></a><em class="parameter"><code>idmap uid = 10000-20000</code></em></td></tr><tr><td># use gids from 10000 to 20000 for domain groups</td></tr><tr><td><a class="indexterm" name="id2658625"></a><em class="parameter"><code>idmap gid = 10000-20000</code></em></td></tr><tr><td># allow enumeration of winbind users and groups</td></tr><tr><td><a class="indexterm" name="id2658642"></a><em class="parameter"><code>winbind enum users = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2658655"></a><em class="parameter"><code>winbind enum groups = yes</code></em></td></tr><tr><td># give winbind users a real shell (only needed if they have telnet access)</td></tr><tr><td><a class="indexterm" name="id2658672"></a><em class="parameter"><code>template homedir = /home/winnt/%D/%U</code></em></td></tr><tr><td><a class="indexterm" name="id2658686"></a><em class="parameter"><code>template shell = /bin/bash</code></em></td></tr></table></div></div><br class="example-break"></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2658701"></a>Join the Samba Server to the PDC Domain</h4></div></div></div><p>
548 All machines that will participate in domain security should be members of
549 the domain. This applies also to the PDC and all BDCs.
550 </p><p>
560 The process of joining a domain requires the use of the <span><strong class="command">net rpc join</strong></span>
561 command. This process communicates with the domain controller it will register with
562 (usually the PDC) via MS DCE RPC. This means, of course, that the <span><strong class="command">smbd</strong></span>
563 process must be running on the target domain controller. It is therefore necessary to temporarily
564 start Samba on a PDC so that it can join its own domain.
565 </p><p>
569 Enter the following command to make the Samba server join the
572 a domain user who has administrative privileges in the domain.
573 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
578 Before attempting to join a machine to the domain, verify that Samba is running
579 on the target domain controller (usually PDC) and that it is capable of being reached via ports
581 </p></div><p>
583 The use of the <span><strong class="command">net rpc join</strong></span> facility is shown here:
585 <code class="prompt">root# </code><strong class="userinput"><code>/usr/local/samba/bin/net rpc join -S PDC -U Administrator</code></strong>
586 </pre><p>
588 <em class="replaceable"><code>DOMAIN</code></em></span>” where <em class="replaceable"><code>DOMAIN</code></em>
589 is your domain name.
590 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2658938"></a>Starting and Testing the <span><strong class="command">winbindd</strong></span> Daemon</h4></div></div></div><p>
594 Eventually, you will want to modify your Samba startup script to
595 automatically invoke the winbindd daemon when the other parts of
596 Samba start, but it is possible to test out just the Winbind
597 portion first. To start up Winbind services, enter the following
598 command as root:
600 <code class="prompt">root# </code><strong class="userinput"><code>/usr/local/samba/sbin/winbindd</code></strong>
601 </pre><p>
602 Use the appropriate path to the location of the <span><strong class="command">winbindd</strong></span> executable file.
603 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
606 The command to start up Winbind services assumes that Samba has been installed in the <code class="filename">/usr/local/samba</code>
607 directory tree. You may need to search for the location of Samba files if this is not the
609 </p></div><p>
612 Winbindd can now also run in “<span class="quote">dual daemon mode</span>”. This will make it
613 run as two processes. The first will answer all requests from the cache,
614 thus making responses to clients faster. The other will
615 update the cache for the query to which the first has just responded.
616 The advantage of this is that responses stay accurate and are faster.
619 <code class="prompt">root# </code><strong class="userinput"><code>/usr/local/samba/sbin/winbindd -B</code></strong>
620 </pre><p>
621 </p><p>
624 I'm always paranoid and like to make sure the daemon is really running.
626 <code class="prompt">root# </code><strong class="userinput"><code>ps -ae | grep winbindd</code></strong>
627 </pre><p>
628 </p><p>
630 This command should produce output like the following if the daemon is running.
633 </pre><p>
634 </p><p>
637 Now, for the real test, try to get some information about the users on your PDC:
639 <code class="prompt">root# </code><strong class="userinput"><code>/usr/local/samba/bin/wbinfo -u</code></strong>
640 </pre><p>
641 This should echo back a list of users on your Windows users on
642 your PDC. For example, I get the following response:
644 CEO\Administrator
645 CEO\burdell
646 CEO\Guest
647 CEO\jt-ad
648 CEO\krbtgt
649 CEO\TsInternetUser
650 </pre><p>
651 Obviously, I have named my domain “<span class="quote">CEO</span>” and my <a class="indexterm" name="id2659182"></a>winbind separator is “<span class="quote">\</span>”.
652 </p><p>
655 You can do the same sort of thing to get group information from the PDC:
657 <code class="prompt">root# </code><strong class="userinput"><code>/usr/local/samba/bin/wbinfo -g</code></strong>
658 CEO\Domain Admins
659 CEO\Domain Users
660 CEO\Domain Guests
661 CEO\Domain Computers
662 CEO\Domain Controllers
663 CEO\Cert Publishers
664 CEO\Schema Admins
665 CEO\Enterprise Admins
666 CEO\Group Policy Creator Owners
667 </pre><p>
675 The function <span><strong class="command">getent</strong></span> can now be used to get unified
676 lists of both local and PDC users and groups. Try the following command:
679 </pre><p>
681 list followed by the domain users with their new UIDs, GIDs, home
682 directories, and default shells.
683 </p><p>
684 The same thing can be done for groups with the command:
687 </pre><p>
688 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2659335"></a>Fix the init.d Startup Scripts</h4></div></div></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2659341"></a>Linux</h5></div></div></div><p>
698 The <span class="application">winbindd</span> daemon needs to start up after the <span class="application">smbd</span> and <span class="application">nmbd</span> daemons are running.
699 To accomplish this task, you need to modify the startup scripts of your system.
702 script to add commands to invoke this daemon in the proper sequence. My
703 startup script starts up <span class="application">smbd</span>, <span class="application">nmbd</span>, and <span class="application">winbindd</span> from the
704 <code class="filename">/usr/local/samba/bin</code> directory directly. The <span><strong class="command">start</strong></span>
705 function in the script looks like this:
707 start() {
709 echo -n $"Starting $KIND services: "
710 daemon /usr/local/samba/bin/smbd $SMBDOPTIONS
711 RETVAL=$?
712 echo
714 echo -n $"Starting $KIND services: "
715 daemon /usr/local/samba/bin/nmbd $NMBDOPTIONS
716 RETVAL2=$?
717 echo
719 echo -n $"Starting $KIND services: "
720 daemon /usr/local/samba/sbin/winbindd
721 RETVAL3=$?
722 echo
724 touch /var/lock/subsys/smb || RETVAL=1
725 return $RETVAL
726 }
727 </pre><p>If you would like to run winbindd in dual daemon mode, replace
728 the line:
730 daemon /usr/local/samba/sbin/winbindd
731 </pre><p>
733 in the example above with:
736 daemon /usr/local/samba/sbin/winbindd -B
737 </pre><p>.
738 </p><p>
739 The <span><strong class="command">stop</strong></span> function has a corresponding entry to shut down the
740 services and looks like this:
742 stop() {
744 echo -n $"Shutting down $KIND services: "
745 killproc smbd
746 RETVAL=$?
747 echo
749 echo -n $"Shutting down $KIND services: "
750 killproc nmbd
751 RETVAL2=$?
752 echo
754 echo -n $"Shutting down $KIND services: "
755 killproc winbindd
756 RETVAL3=$?
758 rm -f /var/lock/subsys/smb
759 echo ""
760 return $RETVAL
761 }
762 </pre></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2659547"></a>Solaris</h5></div></div></div><p>
763 Winbind does not work on Solaris 9; see <a href="Portability.html#winbind-solaris9" title="Winbind on Solaris 9">Winbind on Solaris 9 section</a>
764 for details.
765 </p><p>
772 On Solaris, you need to modify the <code class="filename">/etc/init.d/samba.server</code> startup script. It
773 usually only starts smbd and nmbd but should now start winbindd, too. If you have Samba installed in
774 <code class="filename">/usr/local/samba/bin</code>, the file could contains something like this:
775 </p><p>
777 ##
778 ## samba.server
779 ##
781 if [ ! -d /usr/bin ]
782 then # /usr not mounted
783 exit
784 fi
786 killproc() { # kill the named process(es)
787 pid=`/usr/bin/ps -e |
788 /usr/bin/grep -w $1 |
789 /usr/bin/sed -e 's/^ *//' -e 's/ .*//'`
791 }
793 # Start/stop processes required for Samba server
795 case "$1" in
797 'start')
798 #
799 # Edit these lines to suit your installation (paths, workgroup, host)
800 #
801 echo Starting SMBD
802 /usr/local/samba/bin/smbd -D -s \
803 /usr/local/samba/smb.conf
805 echo Starting NMBD
806 /usr/local/samba/bin/nmbd -D -l \
807 /usr/local/samba/var/log -s /usr/local/samba/smb.conf
809 echo Starting Winbind Daemon
810 /usr/local/samba/sbin/winbindd
811 ;;
813 'stop')
814 killproc nmbd
815 killproc smbd
816 killproc winbindd
817 ;;
819 *)
820 echo "Usage: /etc/init.d/samba.server { start | stop }"
821 ;;
822 esac
823 </pre><p>
824 Again, if you would like to run Samba in dual daemon mode, replace:
826 /usr/local/samba/sbin/winbindd
827 </pre><p>
828 in the script above with:
830 /usr/local/samba/sbin/winbindd -B
831 </pre><p>
832 </p></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2659691"></a>Restarting</h5></div></div></div><p>
835 If you restart the <span class="application">smbd</span>, <span class="application">nmbd</span>, and <span class="application">winbindd</span> daemons at this point, you
836 should be able to connect to the Samba server as a domain member just as
837 if you were a local user.
838 </p></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2659736"></a>Configure Winbind and PAM</h4></div></div></div><p>
843 If you have made it this far, you know that <span><strong class="command">winbindd</strong></span> and Samba are working
844 together. If you want to use Winbind to provide authentication for other
845 services, keep reading. The PAM configuration files need to be altered in
846 this step. (Did you remember to make backups of your original
848 </p><p>
855 You will need a PAM module to use winbindd with these other services. This
857 by invoking the command:
859 <code class="prompt">root# </code><strong class="userinput"><code>make nsswitch/pam_winbind.so</code></strong>
860 </pre><p>
863 your other PAM security modules. On my Red Hat system, this was the
867 <code class="prompt">root# </code><strong class="userinput"><code>cp ../samba/source/nsswitch/pam_winbind.so /lib/security</code></strong>
868 </pre><p>
869 </p><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2659902"></a>Linux/FreeBSD-Specific PAM Configuration</h5></div></div></div><p>
872 just left this file as it was:
874 auth required /lib/security/pam_stack.so service=system-auth
875 account required /lib/security/pam_stack.so service=system-auth
876 </pre><p>
886 The other services that I modified to allow the use of Winbind
887 as an authentication service were the normal login on the console (or a terminal
888 session), telnet logins, and ftp service. In order to enable these
889 services, you may first need to change the entries in
891 Red Hat Linux 7.1 and later uses the new xinetd.d structure, in this case you need
895 enable = no
896 </pre><p>
897 to
899 enable = yes
900 </pre><p>
904 For ftp services to work properly, you will also need to either
905 have individual directories for the domain users already present on
906 the server or change the home directory template to a general
907 directory for all domain users. These can be easily set using
910 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
912 The directory in <a class="indexterm" name="id2660093"></a>template homedir is not created automatically! Use pam_mkhomedir or
913 pre-create the directories of users to make sure users can log in on UNIX with their own home directory.
914 </p></div><p>
919 to allow Winbind ftp access in a manner similar to the
921 changed to look like this:
923 auth required /lib/security/pam_listfile.so item=user sense=deny \
924 file=/etc/ftpusers onerr=succeed
925 auth sufficient /lib/security/pam_winbind.so
926 auth required /lib/security/pam_stack.so service=system-auth
927 auth required /lib/security/pam_shells.so
928 account sufficient /lib/security/pam_winbind.so
929 account required /lib/security/pam_stack.so service=system-auth
930 session required /lib/security/pam_stack.so service=system-auth
931 </pre><p>
934 same way. It now looks like this:
936 auth required /lib/security/pam_securetty.so
937 auth sufficient /lib/security/pam_winbind.so
938 auth sufficient /lib/security/pam_unix.so use_first_pass
939 auth required /lib/security/pam_stack.so service=system-auth
940 auth required /lib/security/pam_nologin.so
941 account sufficient /lib/security/pam_winbind.so
942 account required /lib/security/pam_stack.so service=system-auth
943 password required /lib/security/pam_stack.so service=system-auth
944 session required /lib/security/pam_stack.so service=system-auth
945 session optional /lib/security/pam_console.so
946 </pre><p>
950 In this case, I added the </p><pre class="programlisting">auth sufficient /lib/security/pam_winbind.so</pre><p>
951 lines as before, but also added the </p><pre class="programlisting">required pam_securetty.so</pre><p>
952 above it to disallow root logins over the network. I also added a
954 line after the <span><strong class="command">winbind.so</strong></span> line to get rid of annoying
955 double prompts for passwords.
956 </p></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2660240"></a>Solaris-Specific Configuration</h5></div></div></div><p>
959 The <code class="filename">/etc/pam.conf</code> needs to be changed. I changed this file so my Domain
960 users can log on both locally as well as with telnet. The following are the changes
961 that I made. You can customize the <code class="filename">pam.conf</code> file as per your requirements, but
962 be sure of those changes because in the worst case it will leave your system
963 nearly impossible to boot.
965 #
966 #ident "@(#)pam.conf 1.14 99/09/16 SMI"
967 #
969 # All Rights Reserved.
970 #
971 # PAM configuration
972 #
973 # Authentication management
974 #
975 login auth required /usr/lib/security/pam_winbind.so
976 login auth required /usr/lib/security/$ISA/pam_unix.so.1 try_first_pass
977 login auth required /usr/lib/security/$ISA/pam_dial_auth.so.1 try_first_pass
978 #
979 rlogin auth sufficient /usr/lib/security/pam_winbind.so
980 rlogin auth sufficient /usr/lib/security/$ISA/pam_rhosts_auth.so.1
981 rlogin auth required /usr/lib/security/$ISA/pam_unix.so.1 try_first_pass
982 #
983 dtlogin auth sufficient /usr/lib/security/pam_winbind.so
984 dtlogin auth required /usr/lib/security/$ISA/pam_unix.so.1 try_first_pass
985 #
986 rsh auth required /usr/lib/security/$ISA/pam_rhosts_auth.so.1
987 other auth sufficient /usr/lib/security/pam_winbind.so
988 other auth required /usr/lib/security/$ISA/pam_unix.so.1 try_first_pass
989 #
990 # Account management
991 #
992 login account sufficient /usr/lib/security/pam_winbind.so
993 login account requisite /usr/lib/security/$ISA/pam_roles.so.1
994 login account required /usr/lib/security/$ISA/pam_unix.so.1
995 #
996 dtlogin account sufficient /usr/lib/security/pam_winbind.so
997 dtlogin account requisite /usr/lib/security/$ISA/pam_roles.so.1
998 dtlogin account required /usr/lib/security/$ISA/pam_unix.so.1
999 #
1000 other account sufficient /usr/lib/security/pam_winbind.so
1001 other account requisite /usr/lib/security/$ISA/pam_roles.so.1
1002 other account required /usr/lib/security/$ISA/pam_unix.so.1
1003 #
1004 # Session management
1005 #
1006 other session required /usr/lib/security/$ISA/pam_unix.so.1
1007 #
1008 # Password management
1009 #
1010 #other password sufficient /usr/lib/security/pam_winbind.so
1011 other password required /usr/lib/security/$ISA/pam_unix.so.1
1012 dtsession auth required /usr/lib/security/$ISA/pam_unix.so.1
1013 #
1014 # Support for Kerberos V5 authentication (uncomment to use Kerberos)
1015 #
1016 #rlogin auth optional /usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass
1017 #login auth optional /usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass
1018 #dtlogin auth optional /usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass
1019 #other auth optional /usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass
1020 #dtlogin account optional /usr/lib/security/$ISA/pam_krb5.so.1
1021 #other account optional /usr/lib/security/$ISA/pam_krb5.so.1
1022 #other session optional /usr/lib/security/$ISA/pam_krb5.so.1
1023 #other password optional /usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass
1024 </pre><p>
1026 I also added a <em class="parameter"><code>try_first_pass</code></em> line after the <code class="filename">winbind.so</code>
1027 line to get rid of annoying double prompts for passwords.
1028 </p><p>
1029 Now restart your Samba and try connecting through your application that you
1030 configured in the pam.conf.
1031 </p></div></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2660398"></a>Conclusion</h2></div></div></div><p>
1037 The Winbind system, through the use of the NSS, PAMs, and appropriate
1038 Microsoft RPC calls, have allowed us to provide seamless
1039 integration of Microsoft Windows NT domain users on a
1040 UNIX system. The result is a great reduction in the administrative
1041 cost of running a mixed UNIX and NT network.</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2660446"></a>Common Errors</h2></div></div></div><p>Winbind has a number of limitations in its current
1042 released version that we hope to overcome in future
1043 releases:</p><div class="itemizedlist"><ul type="disc"><li><p>Winbind is currently only available for
1044 the Linux, Solaris, AIX, and IRIX operating systems, although ports to other operating
1045 systems are certainly possible. For such ports to be feasible,
1046 we require the C library of the target operating system to
1047 support the NSS and PAM
1048 systems. This is becoming more common as NSS and
1049 PAM gain support among UNIX vendors.</p></li><li><p>The mappings of Windows NT RIDs to UNIX IDs
1050 is not made algorithmically and depends on the order in which
1051 unmapped users or groups are seen by Winbind. It may be difficult
1052 to recover the mappings of RID to UNIX ID if the file
1053 containing this information is corrupted or destroyed.</p></li><li><p>Currently the Winbind PAM module does not take
1054 into account possible workstation and logon time restrictions
1055 that may be set for Windows NT users; this is
1056 instead up to the PDC to enforce.</p></li></ul></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2660490"></a>NSCD Problem Warning</h3></div></div></div><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p>
1057 Do not under any circumstances run <span><strong class="command">nscd</strong></span> on any system
1059 </p></div><p>
1060 If <span><strong class="command">nscd</strong></span> is running on the UNIX/Linux system, then
1061 even though NSSWITCH is correctly configured, it will not be possible to resolve
1062 domain users and groups for file and directory controls.
1063 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2660526"></a>Winbind Is Not Resolving Users and Groups</h3></div></div></div><p>“<span class="quote">
1067 and <span><strong class="command">winbind</strong></span> is running. When I do the following, it all works fine.
1070 MIDEARTH\maryo
1071 MIDEARTH\jackb
1072 MIDEARTH\ameds
1073 ...
1074 MIDEARTH\root
1077 MIDEARTH\Domain Users
1078 MIDEARTH\Domain Admins
1079 MIDEARTH\Domain Guests
1080 ...
1081 MIDEARTH\Accounts
1083 <code class="prompt">root# </code><strong class="userinput"><code>getent passwd</code></strong>
1086 ...
1089 But the following command just fails:
1092 <code class="prompt">root# </code><strong class="userinput"><code>chown maryo a_file</code></strong>
1093 chown: `maryo': invalid user
1094 </pre><p>
1096 This is driving me nuts! What can be wrong?
1098 Same problem as the one above.
1099 Your system is likely running <span><strong class="command">nscd</strong></span>, the name service
1100 caching daemon. Shut it down, do not restart it! You will find your problem resolved.
1101 </p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="VFS.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="optional.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="AdvancedNetworkManagement.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 23. Stackable VFS modules </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 25. Advanced Network Management</td></tr></table></div></body></html>