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.75.2"><link rel="home" href="index.html" title="The Official Samba 3.5.x 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" title="Chapter�24.�Winbind: Use of Domain Accounts"><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 class="email" 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 class="email" 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 class="email" 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 class="email" 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 class="email" 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 class="email" 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#id417283">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="winbind.html#id417609">Introduction</a></span></dt><dt><span class="sect1"><a href="winbind.html#id417687">What Winbind Provides</a></span></dt><dd><dl><dt><span class="sect2"><a href="winbind.html#id417826">Target Uses</a></span></dt><dt><span class="sect2"><a href="winbind.html#id417865">Handling of Foreign SIDs</a></span></dt></dl></dd><dt><span class="sect1"><a href="winbind.html#id417977">How Winbind Works</a></span></dt><dd><dl><dt><span class="sect2"><a href="winbind.html#id418024">Microsoft Remote Procedure Calls</a></span></dt><dt><span class="sect2"><a href="winbind.html#id418102">Microsoft Active Directory Services</a></span></dt><dt><span class="sect2"><a href="winbind.html#id418146">Name Service Switch</a></span></dt><dt><span class="sect2"><a href="winbind.html#id418358">Pluggable Authentication Modules</a></span></dt><dt><span class="sect2"><a href="winbind.html#id418499">User and Group ID Allocation</a></span></dt><dt><span class="sect2"><a href="winbind.html#id418567">Result Caching</a></span></dt></dl></dd><dt><span class="sect1"><a href="winbind.html#id418617">Installation and Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="winbind.html#id418623">Introduction</a></span></dt><dt><span class="sect2"><a href="winbind.html#id418730">Requirements</a></span></dt><dt><span class="sect2"><a href="winbind.html#id418872">Testing Things Out</a></span></dt></dl></dd><dt><span class="sect1"><a href="winbind.html#id421103">Conclusion</a></span></dt><dt><span class="sect1"><a href="winbind.html#id421149">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="winbind.html#id421183">NSCD Problem Warning</a></span></dt><dt><span class="sect2"><a href="winbind.html#id421217">Winbind Is Not Resolving Users and Groups</a></span></dt></dl></dd></dl></div><div class="sect1" title="Features and Benefits"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id417283"></a>Features and Benefits</h2></div></div></div><p>
2
<a class="indexterm" name="id417291"></a>
3
<a class="indexterm" name="id417297"></a>
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.75.2"><link rel="home" href="index.html" title="The Official Samba 3.5.x 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" title="Chapter�24.�Winbind: Use of Domain Accounts"><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 class="email" 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 class="email" 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 class="email" 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 class="email" 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 class="email" 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 class="email" 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#id417272">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="winbind.html#id417589">Introduction</a></span></dt><dt><span class="sect1"><a href="winbind.html#id417666">What Winbind Provides</a></span></dt><dd><dl><dt><span class="sect2"><a href="winbind.html#id417805">Target Uses</a></span></dt><dt><span class="sect2"><a href="winbind.html#id417844">Handling of Foreign SIDs</a></span></dt></dl></dd><dt><span class="sect1"><a href="winbind.html#id417956">How Winbind Works</a></span></dt><dd><dl><dt><span class="sect2"><a href="winbind.html#id418004">Microsoft Remote Procedure Calls</a></span></dt><dt><span class="sect2"><a href="winbind.html#id418082">Microsoft Active Directory Services</a></span></dt><dt><span class="sect2"><a href="winbind.html#id418126">Name Service Switch</a></span></dt><dt><span class="sect2"><a href="winbind.html#id418338">Pluggable Authentication Modules</a></span></dt><dt><span class="sect2"><a href="winbind.html#id418479">User and Group ID Allocation</a></span></dt><dt><span class="sect2"><a href="winbind.html#id418546">Result Caching</a></span></dt></dl></dd><dt><span class="sect1"><a href="winbind.html#id418597">Installation and Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="winbind.html#id418602">Introduction</a></span></dt><dt><span class="sect2"><a href="winbind.html#id418709">Requirements</a></span></dt><dt><span class="sect2"><a href="winbind.html#id418852">Testing Things Out</a></span></dt></dl></dd><dt><span class="sect1"><a href="winbind.html#id421094">Conclusion</a></span></dt><dt><span class="sect1"><a href="winbind.html#id421140">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="winbind.html#id421173">NSCD Problem Warning</a></span></dt><dt><span class="sect2"><a href="winbind.html#id421207">Winbind Is Not Resolving Users and Groups</a></span></dt></dl></dd></dl></div><div class="sect1" title="Features and Benefits"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id417272"></a>Features and Benefits</h2></div></div></div><p>
2
<a class="indexterm" name="id417280"></a>
3
<a class="indexterm" name="id417286"></a>
4
4
Integration of UNIX and Microsoft Windows NT through a unified logon has
5
5
been considered a <span class="quote">“<span class="quote">holy grail</span>”</span> in heterogeneous computing environments for
8
<a class="indexterm" name="id417312"></a>
9
<a class="indexterm" name="id417319"></a>
10
<a class="indexterm" name="id417326"></a>
11
<a class="indexterm" name="id417333"></a>
8
<a class="indexterm" name="id417301"></a>
9
<a class="indexterm" name="id417308"></a>
10
<a class="indexterm" name="id417315"></a>
11
<a class="indexterm" name="id417322"></a>
12
12
There is one other facility without which UNIX and Microsoft Windows network
13
13
interoperability would suffer greatly. It is imperative that there be a
14
14
mechanism for sharing files across UNIX systems and to be able to assign
15
15
domain user and group ownerships with integrity.
17
<a class="indexterm" name="id417345"></a>
18
<a class="indexterm" name="id417354"></a>
19
<a class="indexterm" name="id417361"></a>
20
<a class="indexterm" name="id417368"></a>
17
<a class="indexterm" name="id417334"></a>
18
<a class="indexterm" name="id417343"></a>
19
<a class="indexterm" name="id417350"></a>
20
<a class="indexterm" name="id417357"></a>
21
21
<span class="emphasis"><em>winbind</em></span> is a component of the Samba suite of programs that
22
22
solves the unified logon problem. Winbind uses a UNIX implementation of Microsoft
23
23
RPC calls, Pluggable Authentication Modules (PAMs), and the name service switch (NSS) to
28
28
Winbind provides three separate functions:
29
29
</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>
30
<a class="indexterm" name="id417392"></a>
31
<a class="indexterm" name="id417398"></a>
30
<a class="indexterm" name="id417380"></a>
31
<a class="indexterm" name="id417387"></a>
32
32
Authentication of user credentials (via PAM). This makes it possible to
33
33
log onto a UNIX/Linux system using user and group accounts from a Windows
34
34
NT4 (including a Samba domain) or an Active Directory domain.
35
35
</p></li><li class="listitem"><p>
36
<a class="indexterm" name="id417411"></a>
36
<a class="indexterm" name="id417400"></a>
37
<a class="indexterm" name="id417407"></a>
38
Identity resolution (via NSS). This is the default when winbind is not used.
39
</p></li><li class="listitem"><p>
37
40
<a class="indexterm" name="id417418"></a>
38
Identity resolution (via NSS). This is the default when winbind is not used.
39
</p></li><li class="listitem"><p>
40
<a class="indexterm" name="id417430"></a>
41
<a class="indexterm" name="id417436"></a>
42
<a class="indexterm" name="id417443"></a>
43
<a class="indexterm" name="id417449"></a>
44
<a class="indexterm" name="id417456"></a>
45
<a class="indexterm" name="id417463"></a>
46
<a class="indexterm" name="id417470"></a>
41
<a class="indexterm" name="id417425"></a>
42
<a class="indexterm" name="id417432"></a>
43
<a class="indexterm" name="id417438"></a>
44
<a class="indexterm" name="id417445"></a>
45
<a class="indexterm" name="id417452"></a>
47
46
Winbind maintains a database called winbind_idmap.tdb in which it stores
48
47
mappings between UNIX UIDs, GIDs, and NT SIDs. This mapping is used only
49
48
for users and groups that do not have a local UID/GID. It stores the UID/GID
52
51
then instead of using a local mapping, Winbind will obtain this information
53
52
from the LDAP database.
54
53
</p></li></ul></div><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
55
<a class="indexterm" name="id417498"></a>
56
<a class="indexterm" name="id417504"></a>
54
<a class="indexterm" name="id417477"></a>
55
<a class="indexterm" name="id417484"></a>
56
<a class="indexterm" name="id417493"></a>
57
<a class="indexterm" name="id417500"></a>
58
<a class="indexterm" name="id417507"></a>
57
59
<a class="indexterm" name="id417514"></a>
58
<a class="indexterm" name="id417520"></a>
59
<a class="indexterm" name="id417527"></a>
60
<a class="indexterm" name="id417534"></a>
61
60
If <code class="literal">winbindd</code> is not running, smbd (which calls <code class="literal">winbindd</code>) will fall back to
62
61
using purely local information from <code class="filename">/etc/passwd</code> and <code class="filename">/etc/group</code> and no dynamic
63
62
mapping will be used. On an operating system that has been enabled with the NSS,
64
63
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" title="Introduction"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id417609"></a>Introduction</h2></div></div></div><p>It is well known that UNIX and Microsoft Windows NT have
64
</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" title="Introduction"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id417589"></a>Introduction</h2></div></div></div><p>It is well known that UNIX and Microsoft Windows NT have
66
65
different models for representing user and group information and
67
66
use different technologies for implementing them. This fact has
68
67
made it difficult to integrate the two systems in a satisfactory
70
<a class="indexterm" name="id417623"></a>
71
<a class="indexterm" name="id417630"></a>
69
<a class="indexterm" name="id417602"></a>
70
<a class="indexterm" name="id417609"></a>
72
71
One common solution in use today has been to create
73
72
identically named user accounts on both the UNIX and Windows systems
74
73
and use the Samba suite of programs to provide file and print services
81
80
</p></li><li class="listitem"><p>Authenticating Windows NT users.
82
81
</p></li><li class="listitem"><p>Password changing for Windows NT users.
83
82
</p></li></ul></div><p>
84
<a class="indexterm" name="id417669"></a>
85
<a class="indexterm" name="id417674"></a>
83
<a class="indexterm" name="id417648"></a>
84
<a class="indexterm" name="id417654"></a>
86
85
Ideally, a prospective solution to the unified logon problem
87
86
would satisfy all the above components without duplication of
88
87
information on the UNIX machines and without creating additional
89
88
tasks for the system administrator when maintaining users and
90
89
groups on either system. The Winbind system provides a simple
91
90
and elegant solution to all three components of the unified logon
92
problem.</p></div><div class="sect1" title="What Winbind Provides"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id417687"></a>What Winbind Provides</h2></div></div></div><p>
91
problem.</p></div><div class="sect1" title="What Winbind Provides"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id417666"></a>What Winbind Provides</h2></div></div></div><p>
92
<a class="indexterm" name="id417674"></a>
93
<a class="indexterm" name="id417681"></a>
94
<a class="indexterm" name="id417688"></a>
93
95
<a class="indexterm" name="id417695"></a>
94
<a class="indexterm" name="id417702"></a>
95
<a class="indexterm" name="id417708"></a>
96
<a class="indexterm" name="id417715"></a>
97
96
Winbind unifies UNIX and Windows NT account management by
98
97
allowing a UNIX box to become a full member of an NT domain. Once
99
98
this is done, the UNIX box will see NT users and groups as if
100
99
they were <span class="quote">“<span class="quote">native</span>”</span> UNIX users and groups, allowing the NT domain
101
100
to be used in much the same manner that NIS+ is used within
102
101
UNIX-only environments.</p><p>
103
<a class="indexterm" name="id417732"></a>
104
<a class="indexterm" name="id417739"></a>
105
<a class="indexterm" name="id417745"></a>
106
<a class="indexterm" name="id417752"></a>
102
<a class="indexterm" name="id417711"></a>
103
<a class="indexterm" name="id417718"></a>
104
<a class="indexterm" name="id417725"></a>
105
<a class="indexterm" name="id417731"></a>
107
106
The end result is that whenever a
108
107
program on the UNIX machine asks the operating system to look up
109
108
a user or group name, the query will be resolved by asking the
112
111
(via the NSS name resolution modules in the C library), this
113
112
redirection to the NT domain controller is completely
114
113
transparent.</p><p>
115
<a class="indexterm" name="id417766"></a>
116
<a class="indexterm" name="id417772"></a>
114
<a class="indexterm" name="id417745"></a>
115
<a class="indexterm" name="id417752"></a>
117
116
Users on the UNIX machine can then use NT user and group
118
117
names as they would <span class="quote">“<span class="quote">native</span>”</span> UNIX names. They can chown files
119
118
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>
121
<a class="indexterm" name="id417788"></a>
119
UNIX machine and run a UNIX X Window session as a domain user.</p><p>
120
<a class="indexterm" name="id417768"></a>
122
121
The only obvious indication that Winbind is being used is
123
122
that user and group names take the form <code class="constant">DOMAIN\user</code> and
124
123
<code class="constant">DOMAIN\group</code>. This is necessary because it allows Winbind to determine
125
124
that redirection to a domain controller is wanted for a particular
126
125
lookup and which trusted domain is being referenced.</p><p>
127
<a class="indexterm" name="id417808"></a>
128
<a class="indexterm" name="id417815"></a>
126
<a class="indexterm" name="id417787"></a>
127
<a class="indexterm" name="id417794"></a>
129
128
Additionally, Winbind provides an authentication service that hooks into the PAM system
130
129
to provide authentication via an NT domain to any PAM-enabled
131
130
applications. This capability solves the problem of synchronizing
132
131
passwords between systems, since all passwords are stored in a single
133
location (on the domain controller).</p><div class="sect2" title="Target Uses"><div class="titlepage"><div><div><h3 class="title"><a name="id417826"></a>Target Uses</h3></div></div></div><p>
134
<a class="indexterm" name="id417833"></a>
132
location (on the domain controller).</p><div class="sect2" title="Target Uses"><div class="titlepage"><div><div><h3 class="title"><a name="id417805"></a>Target Uses</h3></div></div></div><p>
133
<a class="indexterm" name="id417813"></a>
135
134
Winbind is targeted at organizations that have an
136
135
existing NT-based domain infrastructure into which they wish
137
136
to put UNIX workstations or servers. Winbind will allow these
139
138
maintain a separate account infrastructure. This greatly
140
139
simplifies the administrative overhead of deploying UNIX
141
140
workstations into an NT-based organization.</p><p>
142
<a class="indexterm" name="id417847"></a>
143
<a class="indexterm" name="id417854"></a>
141
<a class="indexterm" name="id417826"></a>
142
<a class="indexterm" name="id417833"></a>
144
143
Another interesting way in which we expect Winbind to
145
144
be used is as a central part of UNIX-based appliances. Appliances
146
145
that provide file and print services to Microsoft-based networks
147
146
will be able to use Winbind to provide seamless integration of
148
the appliance into the domain.</p></div><div class="sect2" title="Handling of Foreign SIDs"><div class="titlepage"><div><div><h3 class="title"><a name="id417865"></a>Handling of Foreign SIDs</h3></div></div></div><p>
149
<a class="indexterm" name="id417873"></a>
147
the appliance into the domain.</p></div><div class="sect2" title="Handling of Foreign SIDs"><div class="titlepage"><div><div><h3 class="title"><a name="id417844"></a>Handling of Foreign SIDs</h3></div></div></div><p>
148
<a class="indexterm" name="id417852"></a>
150
149
The term <span class="emphasis"><em>foreign SID</em></span> is often met with the reaction that it
151
150
is not relevant to a particular environment. The following documents an interchange
152
151
that took place on the Samba mailing list. It is a good example of the confusion
153
152
often expressed regarding the use of winbind.
155
<a class="indexterm" name="id417889"></a>
154
<a class="indexterm" name="id417868"></a>
156
155
Fact: Winbind is needed to handle users who use workstations that are NOT part
157
156
of the local domain.
159
<a class="indexterm" name="id417900"></a>
158
<a class="indexterm" name="id417879"></a>
160
159
Response: <span class="quote">“<span class="quote">Why? I've used Samba with workstations that are not part of my domains
161
160
lots of times without using winbind. I thought winbind was for using Samba as a member server
162
161
in a domain controlled by another Samba/Windows PDC.</span>”</span>
164
<a class="indexterm" name="id417915"></a>
165
<a class="indexterm" name="id417922"></a>
166
<a class="indexterm" name="id417928"></a>
163
<a class="indexterm" name="id417895"></a>
164
<a class="indexterm" name="id417901"></a>
165
<a class="indexterm" name="id417908"></a>
167
166
If the Samba server will be accessed from a domain other than the local Samba domain, or
168
167
if there will be access from machines that are not local domain members, winbind will
169
168
permit the allocation of UIDs and GIDs from the assigned pool that will keep the identity
170
169
of the foreign user separate from users that are members of the Samba domain.
171
<a class="indexterm" name="id417921"></a>
172
<a class="indexterm" name="id417927"></a>
173
<a class="indexterm" name="id417934"></a>
172
174
<a class="indexterm" name="id417941"></a>
173
<a class="indexterm" name="id417948"></a>
174
<a class="indexterm" name="id417955"></a>
175
<a class="indexterm" name="id417961"></a>
176
175
This means that winbind is eminently useful in cases where a single
177
176
Samba PDC on a local network is combined with both domain member and domain non-member workstations.
178
177
If winbind is not used, the user george on a Windows workstation that is not a domain
181
180
is that the local user george will be treated as the account DOMAIN\george and the
182
181
foreign (non-member of the domain) account will be treated as MACHINE\george because
183
182
each has a different SID.
184
</p></div></div><div class="sect1" title="How Winbind Works"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id417977"></a>How Winbind Works</h2></div></div></div><p>
185
<a class="indexterm" name="id417985"></a>
186
<a class="indexterm" name="id417992"></a>
187
<a class="indexterm" name="id417998"></a>
188
<a class="indexterm" name="id418005"></a>
183
</p></div></div><div class="sect1" title="How Winbind Works"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id417956"></a>How Winbind Works</h2></div></div></div><p>
184
<a class="indexterm" name="id417964"></a>
185
<a class="indexterm" name="id417971"></a>
186
<a class="indexterm" name="id417978"></a>
187
<a class="indexterm" name="id417984"></a>
189
188
The Winbind system is designed around a client/server
190
189
architecture. A long-running <code class="literal">winbindd</code> daemon
191
190
listens on a UNIX domain socket waiting for requests
192
191
to arrive. These requests are generated by the NSS and PAM
193
192
clients and are processed sequentially.</p><p>The technologies used to implement Winbind are described
194
in detail below.</p><div class="sect2" title="Microsoft Remote Procedure Calls"><div class="titlepage"><div><div><h3 class="title"><a name="id418024"></a>Microsoft Remote Procedure Calls</h3></div></div></div><p>
195
<a class="indexterm" name="id418032"></a>
196
<a class="indexterm" name="id418042"></a>
197
<a class="indexterm" name="id418048"></a>
198
<a class="indexterm" name="id418055"></a>
199
<a class="indexterm" name="id418062"></a>
193
in detail below.</p><div class="sect2" title="Microsoft Remote Procedure Calls"><div class="titlepage"><div><div><h3 class="title"><a name="id418004"></a>Microsoft Remote Procedure Calls</h3></div></div></div><p>
194
<a class="indexterm" name="id418012"></a>
195
<a class="indexterm" name="id418021"></a>
196
<a class="indexterm" name="id418028"></a>
197
<a class="indexterm" name="id418034"></a>
198
<a class="indexterm" name="id418041"></a>
200
199
Over the last few years, efforts have been underway by various Samba Team members to implement various aspects of
201
200
the Microsoft Remote Procedure Call (MSRPC) system. This system is used for most network-related operations
202
201
between Windows NT machines, including remote management, user authentication, and print spooling. Although
203
202
initially this work was done to aid the implementation of Primary Domain Controller (PDC) functionality in
204
203
Samba, it has also yielded a body of code that can be used for other purposes.
206
<a class="indexterm" name="id418076"></a>
207
<a class="indexterm" name="id418083"></a>
208
<a class="indexterm" name="id418090"></a>
205
<a class="indexterm" name="id418056"></a>
206
<a class="indexterm" name="id418063"></a>
207
<a class="indexterm" name="id418069"></a>
209
208
Winbind uses various MSRPC calls to enumerate domain users and groups and to obtain detailed information about
210
209
individual users or groups. Other MSRPC calls can be used to authenticate NT domain users and to change user
211
210
passwords. By directly querying a Windows PDC for user and group information, Winbind maps the NT account
212
211
information onto UNIX user and group names.
213
</p></div><div class="sect2" title="Microsoft Active Directory Services"><div class="titlepage"><div><div><h3 class="title"><a name="id418102"></a>Microsoft Active Directory Services</h3></div></div></div><p>
212
</p></div><div class="sect2" title="Microsoft Active Directory Services"><div class="titlepage"><div><div><h3 class="title"><a name="id418082"></a>Microsoft Active Directory Services</h3></div></div></div><p>
213
<a class="indexterm" name="id418090"></a>
214
<a class="indexterm" name="id418096"></a>
215
<a class="indexterm" name="id418103"></a>
214
216
<a class="indexterm" name="id418110"></a>
215
<a class="indexterm" name="id418117"></a>
216
<a class="indexterm" name="id418124"></a>
217
<a class="indexterm" name="id418130"></a>
218
217
Since late 2001, Samba has gained the ability to interact with Microsoft Windows 2000 using its <span class="quote">“<span class="quote">native
219
218
mode</span>”</span> protocols rather than the NT4 RPC services. Using LDAP and Kerberos, a domain member running
220
219
Winbind can enumerate users and groups in exactly the same way as a Windows 200x client would, and in so doing
221
220
provide a much more efficient and effective Winbind implementation.
222
</p></div><div class="sect2" title="Name Service Switch"><div class="titlepage"><div><div><h3 class="title"><a name="id418146"></a>Name Service Switch</h3></div></div></div><p>
223
<a class="indexterm" name="id418154"></a>
224
<a class="indexterm" name="id418161"></a>
225
<a class="indexterm" name="id418167"></a>
226
<a class="indexterm" name="id418174"></a>
221
</p></div><div class="sect2" title="Name Service Switch"><div class="titlepage"><div><div><h3 class="title"><a name="id418126"></a>Name Service Switch</h3></div></div></div><p>
222
<a class="indexterm" name="id418134"></a>
223
<a class="indexterm" name="id418140"></a>
224
<a class="indexterm" name="id418147"></a>
225
<a class="indexterm" name="id418153"></a>
227
226
The NSS is a feature that is present in many UNIX operating systems. It allows system
228
227
information such as hostnames, mail aliases, and user information
229
228
to be resolved from different sources. For example, a standalone
232
231
may first attempt to resolve system information from local files,
233
232
and then consult an NIS database for user information or a DNS server
234
233
for hostname information.</p><p>
234
<a class="indexterm" name="id418168"></a>
235
<a class="indexterm" name="id418174"></a>
236
<a class="indexterm" name="id418181"></a>
235
237
<a class="indexterm" name="id418188"></a>
236
238
<a class="indexterm" name="id418195"></a>
237
<a class="indexterm" name="id418202"></a>
238
<a class="indexterm" name="id418208"></a>
239
<a class="indexterm" name="id418215"></a>
240
239
The NSS application programming interface allows Winbind to present itself as a source of system
241
240
information when resolving UNIX usernames and groups. Winbind uses this interface and information obtained
242
241
from a Windows NT server using MSRPC calls to provide a new source of account enumeration. Using standard UNIX
243
242
library calls, you can enumerate the users and groups on a UNIX machine running Winbind and see all users and
244
243
groups in an NT domain plus any trusted domain as though they were local users and groups.
246
<a class="indexterm" name="id418230"></a>
247
<a class="indexterm" name="id418236"></a>
248
<a class="indexterm" name="id418243"></a>
245
<a class="indexterm" name="id418209"></a>
246
<a class="indexterm" name="id418216"></a>
247
<a class="indexterm" name="id418222"></a>
249
248
The primary control file for NSS is <code class="filename">/etc/nsswitch.conf</code>. When a UNIX application
250
249
makes a request to do a lookup, the C library looks in <code class="filename">/etc/nsswitch.conf</code> for a line that
251
250
matches the service type being requested; for example, the <span class="quote">“<span class="quote">passwd</span>”</span> service type is used when
254
253
</p><pre class="screen">
255
254
passwd: files example
257
<a class="indexterm" name="id418274"></a>
258
<a class="indexterm" name="id418281"></a>
259
<a class="indexterm" name="id418288"></a>
256
<a class="indexterm" name="id418254"></a>
257
<a class="indexterm" name="id418260"></a>
258
<a class="indexterm" name="id418267"></a>
260
259
then the C library will first load a module called <code class="filename">/lib/libnss_files.so</code> followed
261
260
by the module <code class="filename">/lib/libnss_example.so</code>. The C library will dynamically load each of these
262
261
modules in turn and call resolver functions within the modules to try to resolve the request. Once the request
263
262
is resolved, the C library returns the result to the application.
265
<a class="indexterm" name="id418312"></a>
266
<a class="indexterm" name="id418319"></a>
267
<a class="indexterm" name="id418326"></a>
264
<a class="indexterm" name="id418292"></a>
265
<a class="indexterm" name="id418298"></a>
266
<a class="indexterm" name="id418305"></a>
268
267
This NSS interface provides an easy way for Winbind to hook into the operating system. All that needs
269
268
to be done is to put <code class="filename">libnss_winbind.so</code> in <code class="filename">/lib/</code> then add
270
269
<span class="quote">“<span class="quote">winbind</span>”</span> into <code class="filename">/etc/nsswitch.conf</code> at the appropriate place. The C library
271
270
will then call Winbind to resolve user and group names.
272
</p></div><div class="sect2" title="Pluggable Authentication Modules"><div class="titlepage"><div><div><h3 class="title"><a name="id418358"></a>Pluggable Authentication Modules</h3></div></div></div><p>
271
</p></div><div class="sect2" title="Pluggable Authentication Modules"><div class="titlepage"><div><div><h3 class="title"><a name="id418338"></a>Pluggable Authentication Modules</h3></div></div></div><p>
272
<a class="indexterm" name="id418346"></a>
273
<a class="indexterm" name="id418352"></a>
274
<a class="indexterm" name="id418359"></a>
273
275
<a class="indexterm" name="id418366"></a>
274
<a class="indexterm" name="id418373"></a>
275
<a class="indexterm" name="id418379"></a>
276
<a class="indexterm" name="id418386"></a>
277
276
PAMs provide a system for abstracting authentication and authorization technologies. With a PAM
278
277
module, it is possible to specify different authentication methods for different system applications without
279
278
having to recompile these applications. PAM is also useful for implementing a particular policy for
280
279
authorization. For example, a system administrator may only allow console logins from users stored in the
281
280
local password file but only allow users resolved from an NIS database to log in over the network.
283
<a class="indexterm" name="id418401"></a>
282
<a class="indexterm" name="id418380"></a>
283
<a class="indexterm" name="id418387"></a>
284
<a class="indexterm" name="id418394"></a>
285
<a class="indexterm" name="id418400"></a>
284
286
<a class="indexterm" name="id418407"></a>
285
<a class="indexterm" name="id418414"></a>
286
<a class="indexterm" name="id418421"></a>
287
<a class="indexterm" name="id418428"></a>
288
287
Winbind uses the authentication management and password management PAM interface to integrate Windows
289
288
NT users into a UNIX system. This allows Windows NT users to log in to a UNIX machine and be authenticated
290
289
against a suitable PDC. These users can also change their passwords and have this change take effect directly
292
<a class="indexterm" name="id418420"></a>
293
<a class="indexterm" name="id418426"></a>
294
<a class="indexterm" name="id418433"></a>
293
295
<a class="indexterm" name="id418440"></a>
294
<a class="indexterm" name="id418447"></a>
295
<a class="indexterm" name="id418454"></a>
296
<a class="indexterm" name="id418461"></a>
297
296
PAM is configured by providing control files in the directory <code class="filename">/etc/pam.d/</code> for
298
297
each of the services that require authentication. When an authentication request is made by an application,
299
298
the PAM code in the C library looks up this control file to determine what modules to load to do the
301
300
very easy: simply copy the <code class="filename">pam_winbind.so</code> module to <code class="filename">/lib/security/</code>,
302
301
and the PAM control files for relevant services are updated to allow authentication via Winbind. See the PAM
303
302
documentation in <a class="link" href="pam.html" title="Chapter�28.�PAM-Based Distributed Authentication">PAM-Based Distributed Authentication</a>, for more information.
304
</p></div><div class="sect2" title="User and Group ID Allocation"><div class="titlepage"><div><div><h3 class="title"><a name="id418499"></a>User and Group ID Allocation</h3></div></div></div><p>
305
<a class="indexterm" name="id418507"></a>
306
<a class="indexterm" name="id418513"></a>
307
<a class="indexterm" name="id418520"></a>
303
</p></div><div class="sect2" title="User and Group ID Allocation"><div class="titlepage"><div><div><h3 class="title"><a name="id418479"></a>User and Group ID Allocation</h3></div></div></div><p>
304
<a class="indexterm" name="id418486"></a>
305
<a class="indexterm" name="id418493"></a>
306
<a class="indexterm" name="id418500"></a>
308
307
When a user or group is created under Windows NT/200x, it is allocated a numerical relative identifier
309
308
(RID). This is slightly different from UNIX, which has a range of numbers that are used to identify users and
310
309
the same range used to identify groups. It is Winbind's job to convert RIDs to UNIX ID numbers and vice versa.
313
312
allocated the next UNIX ID from the range. The same process applies for Windows NT groups. Over time, Winbind
314
313
will have mapped all Windows NT users and groups to UNIX user IDs and group IDs.
315
<a class="indexterm" name="id418516"></a>
316
<a class="indexterm" name="id418523"></a>
317
<a class="indexterm" name="id418529"></a>
316
318
<a class="indexterm" name="id418536"></a>
317
<a class="indexterm" name="id418543"></a>
318
<a class="indexterm" name="id418550"></a>
319
<a class="indexterm" name="id418557"></a>
320
319
The results of this mapping are stored persistently in an ID mapping database held in a tdb database.
321
320
This ensures that RIDs are mapped to UNIX IDs in a consistent way.
322
</p></div><div class="sect2" title="Result Caching"><div class="titlepage"><div><div><h3 class="title"><a name="id418567"></a>Result Caching</h3></div></div></div><p>
323
<a class="indexterm" name="id418575"></a>
321
</p></div><div class="sect2" title="Result Caching"><div class="titlepage"><div><div><h3 class="title"><a name="id418546"></a>Result Caching</h3></div></div></div><p>
322
<a class="indexterm" name="id418554"></a>
323
<a class="indexterm" name="id418561"></a>
324
<a class="indexterm" name="id418567"></a>
325
<a class="indexterm" name="id418574"></a>
324
326
<a class="indexterm" name="id418581"></a>
325
<a class="indexterm" name="id418588"></a>
326
<a class="indexterm" name="id418595"></a>
327
<a class="indexterm" name="id418601"></a>
328
327
An active directory system can generate a lot of user and group name lookups. To reduce the network
329
328
cost of these lookups, Winbind uses a caching scheme based on the SAM sequence number supplied by NT domain
330
329
controllers. User or group information returned by a PDC is cached by Winbind along with a sequence number
332
331
information is modified. If a cached entry has expired, the sequence number is requested from the PDC and
333
332
compared against the sequence number of the cached entry. If the sequence numbers do not match, then the
334
333
cached information is discarded and up-to-date information is requested directly from the PDC.
335
</p></div></div><div class="sect1" title="Installation and Configuration"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id418617"></a>Installation and Configuration</h2></div></div></div><div class="sect2" title="Introduction"><div class="titlepage"><div><div><h3 class="title"><a name="id418623"></a>Introduction</h3></div></div></div><p>
336
<a class="indexterm" name="id418631"></a>
337
<a class="indexterm" name="id418638"></a>
338
<a class="indexterm" name="id418644"></a>
334
</p></div></div><div class="sect1" title="Installation and Configuration"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id418597"></a>Installation and Configuration</h2></div></div></div><div class="sect2" title="Introduction"><div class="titlepage"><div><div><h3 class="title"><a name="id418602"></a>Introduction</h3></div></div></div><p>
335
<a class="indexterm" name="id418610"></a>
336
<a class="indexterm" name="id418617"></a>
337
<a class="indexterm" name="id418624"></a>
339
338
This section describes the procedures used to get Winbind up and running. Winbind is capable of providing
340
339
access and authentication control for Windows Domain users through an NT or Windows 200x PDC for regular
341
340
services, such as telnet and ftp, as well for Samba services.
342
341
</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>
343
342
<span class="emphasis"><em>Why should I do this?</em></span>
344
<a class="indexterm" name="id418647"></a>
345
<a class="indexterm" name="id418654"></a>
346
<a class="indexterm" name="id418661"></a>
345
347
<a class="indexterm" name="id418667"></a>
346
<a class="indexterm" name="id418674"></a>
347
<a class="indexterm" name="id418681"></a>
348
<a class="indexterm" name="id418688"></a>
349
348
This allows the Samba administrator to rely on the authentication mechanisms on the Windows NT/200x PDC
350
349
for the authentication of domain members. Windows NT/200x users no longer need to have separate accounts on
351
350
the Samba server.
352
351
</p></li><li class="listitem"><p>
353
352
<span class="emphasis"><em>Who should be reading this document?</em></span>
355
<a class="indexterm" name="id418710"></a>
356
<a class="indexterm" name="id418717"></a>
354
<a class="indexterm" name="id418690"></a>
355
<a class="indexterm" name="id418696"></a>
357
356
This document is designed for system administrators. If you are implementing Samba on a file server and wish
358
357
to (fairly easily) integrate existing Windows NT/200x users from your PDC onto the Samba server, this document
360
</p></li></ul></div></div><div class="sect2" title="Requirements"><div class="titlepage"><div><div><h3 class="title"><a name="id418730"></a>Requirements</h3></div></div></div><p>
361
<a class="indexterm" name="id418738"></a>
362
<a class="indexterm" name="id418744"></a>
363
<a class="indexterm" name="id418751"></a>
359
</p></li></ul></div></div><div class="sect2" title="Requirements"><div class="titlepage"><div><div><h3 class="title"><a name="id418709"></a>Requirements</h3></div></div></div><p>
360
<a class="indexterm" name="id418717"></a>
361
<a class="indexterm" name="id418724"></a>
362
<a class="indexterm" name="id418730"></a>
364
363
If you have a Samba configuration file that you are currently using, <span class="emphasis"><em>BACK IT UP!</em></span>
365
364
If your system already uses PAM, <span class="emphasis"><em>back up the <code class="filename">/etc/pam.d</code> directory
366
365
contents!</em></span> If you haven't already made a boot disk, <span class="emphasis"><em>MAKE ONE NOW!</em></span>
368
<a class="indexterm" name="id418779"></a>
369
<a class="indexterm" name="id418786"></a>
370
<a class="indexterm" name="id418792"></a>
367
<a class="indexterm" name="id418758"></a>
368
<a class="indexterm" name="id418765"></a>
369
<a class="indexterm" name="id418772"></a>
371
370
Messing with the PAM configuration files can make it nearly impossible to log in to your machine. That's
372
371
why you want to be able to boot back into your machine in single-user mode and restore your
373
372
<code class="filename">/etc/pam.d</code> to the original state it was in if you get frustrated with the
374
373
way things are going.
376
<a class="indexterm" name="id418811"></a>
377
<a class="indexterm" name="id418818"></a>
375
<a class="indexterm" name="id418790"></a>
376
<a class="indexterm" name="id418797"></a>
378
377
The latest version of Samba-3 includes a functioning winbindd daemon. Please refer to the <a class="ulink" href="http://samba.org/" target="_top">main Samba Web page</a>, or better yet, your closest Samba mirror site for
379
378
instructions on downloading the source code.
380
<a class="indexterm" name="id418815"></a>
381
<a class="indexterm" name="id418821"></a>
382
<a class="indexterm" name="id418828"></a>
381
383
<a class="indexterm" name="id418835"></a>
382
<a class="indexterm" name="id418842"></a>
383
<a class="indexterm" name="id418849"></a>
384
<a class="indexterm" name="id418855"></a>
385
384
To allow domain users the ability to access Samba shares and files, as well as potentially other services
386
385
provided by your Samba machine, PAM must be set up properly on your
387
machine. In order to compile the Winbind modules, you should have at least the PAM development libraries installed
388
on your system. Please refer to the PAM Web site <a class="ulink" href="http://www.kernel.org/pub/linux/libs/pam/" target="_top">http://www.kernel.org/pub/linux/libs/pam/</a>.
389
</p></div><div class="sect2" title="Testing Things Out"><div class="titlepage"><div><div><h3 class="title"><a name="id418872"></a>Testing Things Out</h3></div></div></div><p>
386
machine. In order to compile the Winbind modules, the PAM development libraries should be installed
387
on your system. Please refer to the <a class="ulink" href="http://www.kernel.org/pub/linux/libs/pam/" target="_top">PAM Web Site</a>.
388
</p></div><div class="sect2" title="Testing Things Out"><div class="titlepage"><div><div><h3 class="title"><a name="id418852"></a>Testing Things Out</h3></div></div></div><p>
389
<a class="indexterm" name="id418860"></a>
390
<a class="indexterm" name="id418867"></a>
391
<a class="indexterm" name="id418874"></a>
390
392
<a class="indexterm" name="id418880"></a>
391
<a class="indexterm" name="id418886"></a>
392
<a class="indexterm" name="id418893"></a>
393
<a class="indexterm" name="id418900"></a>
394
<a class="indexterm" name="id418907"></a>
393
<a class="indexterm" name="id418887"></a>
395
394
Before starting, it is probably best to kill off all the Samba-related daemons running on your server.
396
395
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,
397
396
make sure that you have the standard PAM package that supplies the <code class="filename">/etc/pam.d</code>
399
398
and the <code class="filename">/usr/doc</code> and <code class="filename">/usr/man</code> entries for PAM. Winbind is built
400
399
better in Samba if the pam-devel package is also installed. This package includes the header files
401
400
needed to compile PAM-aware applications.
402
</p><div class="sect3" title="Configure nsswitch.conf and the Winbind Libraries on Linux and Solaris"><div class="titlepage"><div><div><h4 class="title"><a name="id418954"></a>Configure <code class="filename">nsswitch.conf</code> and the Winbind Libraries on Linux and Solaris</h4></div></div></div><p>
403
<a class="indexterm" name="id418968"></a>
404
<a class="indexterm" name="id418975"></a>
405
<a class="indexterm" name="id418981"></a>
406
<a class="indexterm" name="id418988"></a>
401
</p><div class="sect3" title="Configure nsswitch.conf and the Winbind Libraries on Linux and Solaris"><div class="titlepage"><div><div><h4 class="title"><a name="id418935"></a>Configure <code class="filename">nsswitch.conf</code> and the Winbind Libraries on Linux and Solaris</h4></div></div></div><p>
402
<a class="indexterm" name="id418949"></a>
403
<a class="indexterm" name="id418955"></a>
404
<a class="indexterm" name="id418962"></a>
405
<a class="indexterm" name="id418969"></a>
407
406
PAM is a standard component of most current generation UNIX/Linux systems. Unfortunately, few systems install
408
407
the <code class="filename">pam-devel</code> libraries that are needed to build PAM-enabled Samba. Additionally, Samba-3
409
408
may auto-install the Winbind files into their correct locations on your system, so before you get too far down
481
480
From this it is apparent that the <code class="filename">/usr/local/lib</code> directory is included
482
481
in the search dynamic link libraries in order to satisfy object module dependencies.
483
</p></div><div class="sect3" title="NSS Winbind on AIX"><div class="titlepage"><div><div><h4 class="title"><a name="id419328"></a>NSS Winbind on AIX</h4></div></div></div><p>(This section is only for those running AIX.)</p><p>
484
<a class="indexterm" name="id419339"></a>
485
<a class="indexterm" name="id419346"></a>
486
<a class="indexterm" name="id419353"></a>
487
<a class="indexterm" name="id419359"></a>
488
<a class="indexterm" name="id419366"></a>
489
<a class="indexterm" name="id419373"></a>
482
</p></div><div class="sect3" title="NSS Winbind on AIX"><div class="titlepage"><div><div><h4 class="title"><a name="id419308"></a>NSS Winbind on AIX</h4></div></div></div><p>(This section is only for those running AIX.)</p><p>
483
<a class="indexterm" name="id419320"></a>
484
<a class="indexterm" name="id419326"></a>
485
<a class="indexterm" name="id419333"></a>
486
<a class="indexterm" name="id419340"></a>
487
<a class="indexterm" name="id419347"></a>
488
<a class="indexterm" name="id419354"></a>
490
489
The Winbind AIX identification module gets built as <code class="filename">libnss_winbind.so</code> in the
491
490
nsswitch directory of the Samba source. This file can be copied to <code class="filename">/usr/lib/security</code>,
492
491
and the AIX naming convention would indicate that it should be named WINBIND. A stanza like the following:
504
503
Loadable Authentication Module Programming Interface</a> for AIX. Further information on administering the modules
505
504
can be found in the <a class="ulink" href="http://publibn.boulder.ibm.com/doc_link/en_US/a_doc_lib/aixbman/baseadmn/iandaadmin.htm" target="_top">System
506
505
Management Guide: Operating System and Devices.</a>
507
</p></div><div class="sect3" title="Configure smb.conf"><div class="titlepage"><div><div><h4 class="title"><a name="id419430"></a>Configure smb.conf</h4></div></div></div><p>
508
<a class="indexterm" name="id419438"></a>
509
<a class="indexterm" name="id419444"></a>
510
<a class="indexterm" name="id419451"></a>
506
</p></div><div class="sect3" title="Configure smb.conf"><div class="titlepage"><div><div><h4 class="title"><a name="id419410"></a>Configure smb.conf</h4></div></div></div><p>
507
<a class="indexterm" name="id419418"></a>
508
<a class="indexterm" name="id419425"></a>
509
<a class="indexterm" name="id419432"></a>
511
510
Several parameters are needed in the <code class="filename">smb.conf</code> file to control the behavior of <span class="application">winbindd</span>. These
512
511
are described in more detail in the <a class="citerefentry" 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 class="link" 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.
513
</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 border="0" summary="Simple list" class="simplelist"><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="id419522"></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="id419538"></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="id419553"></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="id419568"></a><em class="parameter"><code>winbind enum users = yes</code></em></td></tr><tr><td><a class="indexterm" name="id419580"></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="id419595"></a><em class="parameter"><code>template homedir = /home/winnt/%D/%U</code></em></td></tr><tr><td><a class="indexterm" name="id419607"></a><em class="parameter"><code>template shell = /bin/bash</code></em></td></tr></table></div></div><br class="example-break"></div><div class="sect3" title="Join the Samba Server to the PDC Domain"><div class="titlepage"><div><div><h4 class="title"><a name="id419620"></a>Join the Samba Server to the PDC Domain</h4></div></div></div><p>
514
<a class="indexterm" name="id419628"></a>
515
<a class="indexterm" name="id419635"></a>
516
<a class="indexterm" name="id419642"></a>
512
</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 border="0" summary="Simple list" class="simplelist"><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="id419503"></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="id419518"></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="id419533"></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="id419548"></a><em class="parameter"><code>winbind enum users = yes</code></em></td></tr><tr><td><a class="indexterm" name="id419560"></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="id419576"></a><em class="parameter"><code>template homedir = /home/winnt/%D/%U</code></em></td></tr><tr><td><a class="indexterm" name="id419587"></a><em class="parameter"><code>template shell = /bin/bash</code></em></td></tr></table></div></div><br class="example-break"></div><div class="sect3" title="Join the Samba Server to the PDC Domain"><div class="titlepage"><div><div><h4 class="title"><a name="id419601"></a>Join the Samba Server to the PDC Domain</h4></div></div></div><p>
513
<a class="indexterm" name="id419609"></a>
514
<a class="indexterm" name="id419616"></a>
515
<a class="indexterm" name="id419622"></a>
517
516
All machines that will participate in domain security should be members of
518
517
the domain. This applies also to the PDC and all BDCs.
520
<a class="indexterm" name="id419653"></a>
521
<a class="indexterm" name="id419659"></a>
522
<a class="indexterm" name="id419666"></a>
523
<a class="indexterm" name="id419677"></a>
524
<a class="indexterm" name="id419684"></a>
525
<a class="indexterm" name="id419691"></a>
526
<a class="indexterm" name="id419697"></a>
527
<a class="indexterm" name="id419704"></a>
528
<a class="indexterm" name="id419711"></a>
519
<a class="indexterm" name="id419633"></a>
520
<a class="indexterm" name="id419640"></a>
521
<a class="indexterm" name="id419647"></a>
522
<a class="indexterm" name="id419658"></a>
523
<a class="indexterm" name="id419665"></a>
524
<a class="indexterm" name="id419671"></a>
525
<a class="indexterm" name="id419678"></a>
526
<a class="indexterm" name="id419685"></a>
527
<a class="indexterm" name="id419692"></a>
529
528
The process of joining a domain requires the use of the <code class="literal">net rpc join</code>
530
529
command. This process communicates with the domain controller it will register with
531
530
(usually the PDC) via MS DCE RPC. This means, of course, that the <code class="literal">smbd</code>
532
531
process must be running on the target domain controller. It is therefore necessary to temporarily
533
532
start Samba on a PDC so that it can join its own domain.
535
<a class="indexterm" name="id419736"></a>
536
<a class="indexterm" name="id419742"></a>
537
<a class="indexterm" name="id419749"></a>
534
<a class="indexterm" name="id419716"></a>
535
<a class="indexterm" name="id419723"></a>
536
<a class="indexterm" name="id419730"></a>
538
537
Enter the following command to make the Samba server join the domain, where <em class="replaceable"><code>PDC</code></em> is
539
538
the name of your PDC and <em class="replaceable"><code>Administrator</code></em> is a domain user who has administrative
540
539
privileges in the domain.
541
540
</p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
541
<a class="indexterm" name="id419749"></a>
542
<a class="indexterm" name="id419756"></a>
543
<a class="indexterm" name="id419763"></a>
542
544
<a class="indexterm" name="id419769"></a>
543
<a class="indexterm" name="id419776"></a>
544
<a class="indexterm" name="id419782"></a>
545
<a class="indexterm" name="id419789"></a>
546
545
Before attempting to join a machine to the domain, verify that Samba is running
547
546
on the target domain controller (usually PDC) and that it is capable of being reached via ports
548
547
137/udp, 135/tcp, 139/tcp, and 445/tcp (if Samba or Windows Server 2Kx).
550
<a class="indexterm" name="id419801"></a>
549
<a class="indexterm" name="id419782"></a>
551
550
The use of the <code class="literal">net rpc join</code> facility is shown here:
552
551
</p><pre class="screen">
553
552
<code class="prompt">root# </code><strong class="userinput"><code>/usr/local/samba/bin/net rpc join -S PDC -U Administrator</code></strong>
568
567
Use the appropriate path to the location of the <code class="literal">winbindd</code> executable file.
569
568
</p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
570
<a class="indexterm" name="id419911"></a>
571
<a class="indexterm" name="id419918"></a>
569
<a class="indexterm" name="id419891"></a>
570
<a class="indexterm" name="id419898"></a>
572
571
The command to start up Winbind services assumes that Samba has been installed in the
573
572
<code class="filename">/usr/local/samba</code> directory tree. You may need to search for the location of Samba files
574
573
if this is not the location of <code class="literal">winbindd</code> on your system.
576
<a class="indexterm" name="id419941"></a>
577
<a class="indexterm" name="id419948"></a>
575
<a class="indexterm" name="id419922"></a>
576
<a class="indexterm" name="id419928"></a>
578
577
I'm always paranoid and like to make sure the daemon is really running.
579
578
</p><pre class="screen">
580
579
<code class="prompt">root# </code><strong class="userinput"><code>ps -ae | grep winbindd</code></strong>
583
<a class="indexterm" name="id419975"></a>
582
<a class="indexterm" name="id419955"></a>
584
583
This command should produce output like the following if the daemon is running.
585
584
</p><pre class="screen">
586
585
3025 ? 00:00:00 winbindd
589
<a class="indexterm" name="id419991"></a>
590
<a class="indexterm" name="id419998"></a>
588
<a class="indexterm" name="id419972"></a>
589
<a class="indexterm" name="id419978"></a>
591
590
Now, for the real test, try to get some information about the users on your PDC:
592
591
</p><pre class="screen">
593
592
<code class="prompt">root# </code><strong class="userinput"><code>/usr/local/samba/bin/wbinfo -u</code></strong>
640
639
</p><pre class="screen">
641
640
<code class="prompt">root# </code><strong class="userinput"><code>getent group</code></strong>
643
</p></div><div class="sect3" title="Fix the init.d Startup Scripts"><div class="titlepage"><div><div><h4 class="title"><a name="id420184"></a>Fix the init.d Startup Scripts</h4></div></div></div><div class="sect4" title="Linux"><div class="titlepage"><div><div><h5 class="title"><a name="id420190"></a>Linux</h5></div></div></div><p>
644
<a class="indexterm" name="id420197"></a>
645
<a class="indexterm" name="id420204"></a>
646
<a class="indexterm" name="id420211"></a>
647
<a class="indexterm" name="id420218"></a>
648
<a class="indexterm" name="id420224"></a>
649
<a class="indexterm" name="id420231"></a>
650
<a class="indexterm" name="id420238"></a>
651
<a class="indexterm" name="id420244"></a>
652
<a class="indexterm" name="id420249"></a>
642
</p></div><div class="sect3" title="Fix the init.d Startup Scripts"><div class="titlepage"><div><div><h4 class="title"><a name="id420164"></a>Fix the init.d Startup Scripts</h4></div></div></div><div class="sect4" title="Linux"><div class="titlepage"><div><div><h5 class="title"><a name="id420170"></a>Linux</h5></div></div></div><p>
643
<a class="indexterm" name="id420178"></a>
644
<a class="indexterm" name="id420185"></a>
645
<a class="indexterm" name="id420191"></a>
646
<a class="indexterm" name="id420198"></a>
647
<a class="indexterm" name="id420205"></a>
648
<a class="indexterm" name="id420212"></a>
653
649
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. To accomplish this
654
650
task, you need to modify the startup scripts of your system. They are located at
655
651
<code class="filename">/etc/init.d/smb</code> in Red Hat Linux and in <code class="filename">/etc/init.d/samba</code> in Debian
713
</pre></div><div class="sect4" title="Solaris"><div class="titlepage"><div><div><h5 class="title"><a name="id420373"></a>Solaris</h5></div></div></div><p>
709
</pre></div><div class="sect4" title="Solaris"><div class="titlepage"><div><div><h5 class="title"><a name="id420337"></a>Solaris</h5></div></div></div><p>
714
710
Winbind does not work on Solaris 9; see <a class="link" href="Portability.html#winbind-solaris9" title="Winbind on Solaris 9">Winbind on Solaris 9 section</a>
717
<a class="indexterm" name="id420392"></a>
718
<a class="indexterm" name="id420399"></a>
719
<a class="indexterm" name="id420406"></a>
720
<a class="indexterm" name="id420413"></a>
721
<a class="indexterm" name="id420420"></a>
722
<a class="indexterm" name="id420426"></a>
713
<a class="indexterm" name="id420356"></a>
714
<a class="indexterm" name="id420363"></a>
715
<a class="indexterm" name="id420370"></a>
716
<a class="indexterm" name="id420377"></a>
717
<a class="indexterm" name="id420384"></a>
718
<a class="indexterm" name="id420390"></a>
723
719
On Solaris, you need to modify the <code class="filename">/etc/init.d/samba.server</code> startup script. It
724
720
usually only starts smbd and nmbd but should now start winbindd, too. If you have Samba installed in
725
721
<code class="filename">/usr/local/samba/bin</code>, the file could contains something like this:
780
776
</p><pre class="programlisting">
781
777
/usr/local/samba/sbin/winbindd -D
783
</p></div><div class="sect4" title="Restarting"><div class="titlepage"><div><div><h5 class="title"><a name="id420492"></a>Restarting</h5></div></div></div><p>
784
<a class="indexterm" name="id420500"></a>
785
<a class="indexterm" name="id420507"></a>
779
</p></div><div class="sect4" title="Restarting"><div class="titlepage"><div><div><h5 class="title"><a name="id420456"></a>Restarting</h5></div></div></div><p>
780
<a class="indexterm" name="id420464"></a>
781
<a class="indexterm" name="id420471"></a>
786
782
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
787
783
should be able to connect to the Samba server as a domain member just as
788
784
if you were a local user.
789
</p></div></div><div class="sect3" title="Configure Winbind and PAM"><div class="titlepage"><div><div><h4 class="title"><a name="id420536"></a>Configure Winbind and PAM</h4></div></div></div><p>
790
<a class="indexterm" name="id420543"></a>
791
<a class="indexterm" name="id420550"></a>
792
<a class="indexterm" name="id420557"></a>
793
<a class="indexterm" name="id420564"></a>
785
</p></div></div><div class="sect3" title="Configure Winbind and PAM"><div class="titlepage"><div><div><h4 class="title"><a name="id420500"></a>Configure Winbind and PAM</h4></div></div></div><p>
786
<a class="indexterm" name="id420508"></a>
787
<a class="indexterm" name="id420514"></a>
788
<a class="indexterm" name="id420521"></a>
789
<a class="indexterm" name="id420528"></a>
794
790
If you have made it this far, you know that <code class="literal">winbindd</code> and Samba are working together. If you
795
791
want to use Winbind to provide authentication for other services, keep reading. The PAM configuration files
796
792
need to be altered in this step. (Did you remember to make backups of your original
797
793
<code class="filename">/etc/pam.d</code> files? If not, do it now.)
799
<a class="indexterm" name="id420588"></a>
800
<a class="indexterm" name="id420595"></a>
801
<a class="indexterm" name="id420601"></a>
802
<a class="indexterm" name="id420608"></a>
803
<a class="indexterm" name="id420615"></a>
804
<a class="indexterm" name="id420622"></a>
795
<a class="indexterm" name="id420552"></a>
796
<a class="indexterm" name="id420559"></a>
797
<a class="indexterm" name="id420566"></a>
798
<a class="indexterm" name="id420572"></a>
799
<a class="indexterm" name="id420579"></a>
800
<a class="indexterm" name="id420586"></a>
805
801
You will need a PAM module to use winbindd with these other services. This module will be compiled in the
806
802
<code class="filename">../source/nsswitch</code> directory by invoking the command:
807
803
</p><pre class="screen">
814
810
</p><pre class="screen">
815
811
<code class="prompt">root# </code><strong class="userinput"><code>cp ../samba/source/nsswitch/pam_winbind.so /lib/security</code></strong>
817
</p><div class="sect4" title="Linux/FreeBSD-Specific PAM Configuration"><div class="titlepage"><div><div><h5 class="title"><a name="id420694"></a>Linux/FreeBSD-Specific PAM Configuration</h5></div></div></div><p>
818
<a class="indexterm" name="id420702"></a>
813
</p><div class="sect4" title="Linux/FreeBSD-Specific PAM Configuration"><div class="titlepage"><div><div><h5 class="title"><a name="id420659"></a>Linux/FreeBSD-Specific PAM Configuration</h5></div></div></div><p>
814
<a class="indexterm" name="id420667"></a>
819
815
The <code class="filename">/etc/pam.d/samba</code> file does not need to be changed. I just left this file as it was:
820
816
</p><pre class="programlisting">
821
817
auth required /lib/security/pam_stack.so service=system-auth
822
818
account required /lib/security/pam_stack.so service=system-auth
824
<a class="indexterm" name="id420725"></a>
825
<a class="indexterm" name="id420731"></a>
826
<a class="indexterm" name="id420738"></a>
827
<a class="indexterm" name="id420745"></a>
828
<a class="indexterm" name="id420752"></a>
829
<a class="indexterm" name="id420759"></a>
830
<a class="indexterm" name="id420765"></a>
831
<a class="indexterm" name="id420772"></a>
832
<a class="indexterm" name="id420779"></a>
820
<a class="indexterm" name="id420689"></a>
821
<a class="indexterm" name="id420696"></a>
822
<a class="indexterm" name="id420702"></a>
823
<a class="indexterm" name="id420709"></a>
824
<a class="indexterm" name="id420716"></a>
825
<a class="indexterm" name="id420723"></a>
826
<a class="indexterm" name="id420730"></a>
827
<a class="indexterm" name="id420736"></a>
828
<a class="indexterm" name="id420743"></a>
833
829
The other services that I modified to allow the use of Winbind as an authentication service were the normal
834
830
login on the console (or a terminal session), telnet logins, and ftp service. In order to enable these
835
831
services, you may first need to change the entries in <code class="filename">/etc/xinetd.d</code> (or
843
839
</p><pre class="programlisting">
846
<a class="indexterm" name="id420827"></a>
847
<a class="indexterm" name="id420834"></a>
848
<a class="indexterm" name="id420840"></a>
842
<a class="indexterm" name="id420791"></a>
843
<a class="indexterm" name="id420798"></a>
844
<a class="indexterm" name="id420805"></a>
849
845
For ftp services to work properly, you will also need to either have individual directories for the domain
850
846
users already present on the server or change the home directory template to a general directory for all
851
847
domain users. These can be easily set using the <code class="filename">smb.conf</code> global entry <a class="link" href="smb.conf.5.html#TEMPLATEHOMEDIR" target="_top">template homedir</a>.
852
848
</p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
853
<a class="indexterm" name="id420873"></a>
849
<a class="indexterm" name="id420837"></a>
854
850
The directory in <a class="link" href="smb.conf.5.html#TEMPLATEHOMEDIR" target="_top">template homedir</a> is not created automatically! Use pam_mkhomedir or
855
851
pre-create the directories of users to make sure users can log in on UNIX with their own home directory.
857
<a class="indexterm" name="id420895"></a>
858
<a class="indexterm" name="id420901"></a>
859
<a class="indexterm" name="id420908"></a>
853
<a class="indexterm" name="id420859"></a>
854
<a class="indexterm" name="id420865"></a>
855
<a class="indexterm" name="id420872"></a>
860
856
The <code class="filename">/etc/pam.d/ftp</code> file can be changed to allow Winbind ftp access in a manner similar to
861
the samba file. My <code class="filename">/etc/pam.d/ftp</code> file was changed to look like this:
857
the <code class="filename">/etc/pam.d/samba</code>Samba file. My <code class="filename">/etc/pam.d/ftp</code> file was changed to look like this:
862
858
</p><pre class="programlisting">
863
859
auth required /lib/security/pam_listfile.so item=user sense=deny \
864
860
file=/etc/ftpusers onerr=succeed
883
879
session required /lib/security/pam_stack.so service=system-auth
884
880
session optional /lib/security/pam_console.so
886
<a class="indexterm" name="id420964"></a>
887
<a class="indexterm" name="id420971"></a>
888
<a class="indexterm" name="id420977"></a>
882
<a class="indexterm" name="id420933"></a>
883
<a class="indexterm" name="id420940"></a>
884
<a class="indexterm" name="id420947"></a>
889
885
In this case, I added the </p><pre class="programlisting">auth sufficient /lib/security/pam_winbind.so</pre><p> lines
890
886
as before, but also added the </p><pre class="programlisting">required pam_securetty.so</pre><p> above it to disallow
891
887
root logins over the network. I also added a </p><pre class="programlisting">sufficient /lib/security/pam_unix.so
892
888
use_first_pass</pre><p> line after the <code class="literal">winbind.so</code> line to get rid of annoying
893
889
double prompts for passwords.
894
</p></div><div class="sect4" title="Solaris-Specific Configuration"><div class="titlepage"><div><div><h5 class="title"><a name="id421012"></a>Solaris-Specific Configuration</h5></div></div></div><p>
895
<a class="indexterm" name="id421020"></a>
896
<a class="indexterm" name="id421027"></a>
890
</p></div><div class="sect4" title="Solaris-Specific Configuration"><div class="titlepage"><div><div><h5 class="title"><a name="id420982"></a>Solaris-Specific Configuration</h5></div></div></div><p>
891
<a class="indexterm" name="id420990"></a>
892
<a class="indexterm" name="id420996"></a>
897
893
The <code class="filename">/etc/pam.conf</code> needs to be changed. I changed this file so my Domain
898
894
users can log on both locally as well as with telnet. The following are the changes
899
895
that I made. You can customize the <code class="filename">pam.conf</code> file as per your requirements, but
960
956
#other session optional /usr/lib/security/$ISA/pam_krb5.so.1
961
957
#other password optional /usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass
963
<a class="indexterm" name="id421075"></a>
959
<a class="indexterm" name="id421065"></a>
964
960
I also added a <em class="parameter"><code>try_first_pass</code></em> line after the <code class="filename">winbind.so</code>
965
961
line to get rid of annoying double prompts for passwords.
967
963
Now restart your Samba and try connecting through your application that you
968
964
configured in the pam.conf.
969
</p></div></div></div></div><div class="sect1" title="Conclusion"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id421103"></a>Conclusion</h2></div></div></div><p>
970
<a class="indexterm" name="id421111"></a>
971
<a class="indexterm" name="id421118"></a>
972
<a class="indexterm" name="id421124"></a>
973
<a class="indexterm" name="id421131"></a>
974
<a class="indexterm" name="id421138"></a>
965
</p></div></div></div></div><div class="sect1" title="Conclusion"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id421094"></a>Conclusion</h2></div></div></div><p>
966
<a class="indexterm" name="id421102"></a>
967
<a class="indexterm" name="id421108"></a>
968
<a class="indexterm" name="id421115"></a>
969
<a class="indexterm" name="id421121"></a>
970
<a class="indexterm" name="id421128"></a>
975
971
The Winbind system, through the use of the NSS, PAMs, and appropriate Microsoft RPC calls, have allowed us to
976
972
provide seamless integration of Microsoft Windows NT domain users on a UNIX system. The result is a great
977
973
reduction in the administrative cost of running a mixed UNIX and NT network.
978
</p></div><div class="sect1" title="Common Errors"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id421149"></a>Common Errors</h2></div></div></div><p>
974
</p></div><div class="sect1" title="Common Errors"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id421140"></a>Common Errors</h2></div></div></div><p>
979
975
Winbind has a number of limitations in its current released version that we hope to overcome in future releases:
980
976
</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>
981
977
Winbind is currently only available for the Linux, Solaris, AIX, and IRIX operating systems, although
989
985
</p></li><li class="listitem"><p>
990
986
Currently the Winbind PAM module does not take into account possible workstation and logon time
991
987
restrictions that may be set for Windows NT users; this is instead up to the PDC to enforce.
992
</p></li></ul></div><div class="sect2" title="NSCD Problem Warning"><div class="titlepage"><div><div><h3 class="title"><a name="id421183"></a>NSCD Problem Warning</h3></div></div></div><div class="warning" title="Warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p>
988
</p></li></ul></div><div class="sect2" title="NSCD Problem Warning"><div class="titlepage"><div><div><h3 class="title"><a name="id421173"></a>NSCD Problem Warning</h3></div></div></div><div class="warning" title="Warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p>
993
989
Do not under any circumstances run <code class="literal">nscd</code> on any system
994
990
on which <code class="literal">winbindd</code> is running.
996
992
If <code class="literal">nscd</code> is running on the UNIX/Linux system, then
997
993
even though NSSWITCH is correctly configured, it will not be possible to resolve
998
994
domain users and groups for file and directory controls.
999
</p></div><div class="sect2" title="Winbind Is Not Resolving Users and Groups"><div class="titlepage"><div><div><h3 class="title"><a name="id421217"></a>Winbind Is Not Resolving Users and Groups</h3></div></div></div><p><span class="quote">“<span class="quote">
995
</p></div><div class="sect2" title="Winbind Is Not Resolving Users and Groups"><div class="titlepage"><div><div><h3 class="title"><a name="id421207"></a>Winbind Is Not Resolving Users and Groups</h3></div></div></div><p><span class="quote">“<span class="quote">
1000
996
My <code class="filename">smb.conf</code> file is correctly configured. I have specified <a class="link" href="smb.conf.5.html#IDMAPUID" target="_top">idmap uid = 12000</a>,
1001
997
and <a class="link" href="smb.conf.5.html#IDMAPGID" target="_top">idmap gid = 3000-3500</a> and <code class="literal">winbind</code> is running.
1002
998
When I do the following, it all works fine.
added
removed
docs/htmldocs/Samba3-HOWTO/winbind.html
