[Samba] winbind problem on solaris (samba head)

Don Hammer hammerd at evanite.com
Thu Jun 27 15:47:02 GMT 2002


The information I have on using winbind, is that if you don't use pam it
will not work. I compiled samba-2.2.4 with winbind, pam pam_smbpass and
smbwrapper

Don Hammer
Network Administrator
Evanite Fiber Corporation
1115 SE Crystal Lake Dr
Corvallis, OR 97333
(541) 753-0391 voice
(541) 753-0388 fax
hammerd at evanite.com


-----Original Message-----
From: samba-admin at lists.samba.org [mailto:samba-admin at lists.samba.org]On
Behalf Of David Shapiro
Sent: Thursday, June 27, 2002 2:34 PM
To: 'samba at lists.samba.org'
Subject: [Samba] winbind problem on solaris (samba head)


Hello,

I just buildt via cvs samba head.  I used just the option --with-winbind (no
pam).  The first problem is that sessionid.tdb is missing after the build.
I don't know how to make it make a new one (can I copy one from another
server or is there something in it that would make that a bad idea?).  The
other problem is that wbinfo -t says secret is good, wbinfo -g/u return the
correct information.

...but getent passwd or getent group do not return anything but what is in
/etc/passwd and /etc/group.

I did copy libnss_winbind.so to /usr/lib and link libnss_winbind.so.2 to it.
I even did another link to libnss_winbind.so.1 too.
I did add in /etc/nsswitch.conf for passwd and group to use winbind and
file.
I use crle and did a crle -u to update libraries.  crle shows
libnss_winbind.so.2.

I am using gcc 3.1 and gnu binutils 2.11.2.

Please help me fix this so that winbind works.


Thanks,

David E. Shapiro


--
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

********* PRIVACY STATEMENT *********
This e-mail and its attachments contain
confidential information, and are intended
only for the individual or entity indicated.
If you are not the intended recipient,
you are hereby notified that the disclosure,
copying, distribution or use of the contents
of this transmission is strictly prohibited,
and no privilege or protection has been waived.
If you have received this communication in error,
please notify the sender immediately and then
delete the message from the computer.




More information about the samba mailing list