similar to: Samba Team? - "ld.so.1: ls: fatal: relocation error: file /usr/lib/nss_winbind.so.1: symbol socket: referenced symbol not fou n d"

I've recompiled samba 2.2.3a and still any time I do a ls -l in a directory where there are files from a PC I get the error : ld.so.1: ls: fatal: relocation error: file /usr/lib/nss_winbind.so.1: symbol socket: referenced symbol not found If I shut off winbind or take winbind out for my /etc/nsswitch.conf file, I can get a directory listing and it lists the users ID that winbind assigned to

The LIBS line at the top of the Makefile read: LIBS=-lsec -lgen -lresolv -lsocket -lnsl -ldl Is there somewhere else that I need to add -lsocket? David -----Original Message----- From: Andrew Bartlett [mailto:abartlet@pcug.org.au] Sent: Thursday, February 28, 2002 4:22 PM To: David Edward Shapiro Cc: 'samba-technical@lists.samba.org'; 'samba@lists.samba.org' Subject: Re:

OK. This is becoming very frustrating!! I have Samba 2.2.3a installed on a Sun running Solaris 8. Winbind is installed and seems to be working fine. My PC users can map the Samba share via their NT domain account information (PDC is an NT4 box). As soon as I copy nsswitch/libnss_winbind.so to /lib and create the symbolic links (nss_winbind.so.1 & nss_winbind.so.2) my PC users can no

Hey, I'm getting this error when ever I've written a file from my Win2k Pro machine to my samba share. Using Samba 2.2.3. Built on Solaris 8. Using winbindd. I created the sym links as suggested under /lib (really /usr/lib): nss_winbind.so.1 -> libnss_winbind.so nss_winbind.so.2 -> libnss_winbind.so Are there some other sim links I need somewhere or is this error something

I had the same problem. You need to go into your Makefile and add the [LIBS] definition to the part where winbind.so is linked. Just take it on to the end of the line and run "make" and "make install" again. You might want to do a "make uninstall" and a "make clean" first. -Dan -----Original Message----- From: Jelmer Vernooij [mailto:jelmer@nl.linux.org]

Any hope getting an answer for this? If you do an ls -la in a directory that is part of a path of a share, you get the following error: ld.so.1: ls: fatal: relocation error: file /lib/nss_winbind.so.1: symbol socket: referenced symbol not found Killed So, for example, if you have a share: [monkey] comment = monkey path = /export/home/monkey #guest account =

After some days, here is my personal cookbook for Samba in Solaris. I needed to share a folder in my Solaris server, but using my Windows Active Directory Account. Here are my proccess, if it can help to anyone or if anyone can make corrections or suggestions. Thx. Personal Cookbook for Samba. Objective: To enable a Unix server for share folders for Microsoft Windows machines with

Well, I managed to get Samba 2.2.3 up and running on our Solaris 8 machine. I installed with the winbind option and everything went though just find. I was able to join the NT domain and now I can do a wbinfo -u "and get a domain user list as well as a "wbinfo -g and get a group list. For some reason though, the authentication isn't working. I tried to "wbinfo -a" and

Thank you Andrew, you pointed me in the right direction. Part of what I m doing to try to get Netatalk to authenticate through Winbind was the following: 4) to install Winbind files: cp nsswitch/libnss_winbind.so /lib # this is the major one - solaris nss is different to linux. ln -s libnss_winbind.so nss_winbind.so.1 cp nsswitch/pam_winbind.so /lib/security Once I deleted /lib/libnss_winbind.so

Hi all, Is it a necessity to use the winbind nss module? I have run a few tests and having it enabled creates a massive bottleneck. It's not nss_winbind itself that is the bottleneck but something in the background (I'm guessing uid/rid->username code). If I disable winbind in nsswitch.conf what impact will it have? Will the system continue to work? eg: #nss_winbind enabled on

Sunfreeware.com has compiled packages of Samba 3.4.2 with kerberos and ldap support included (if you also install the ldap and kerberos packages from sunfreeware.) However it does not include the nss_winbind.so.* or libnss_winbind.so.* files. Solaris does include nss_winbind.so already (since it is included with Samba 3.0.x) or I could compile it from the 3.4.x source code. But then I

Hi. Does anyone have samba 2.2.2 on Solaris 8 working with winbindd? I have samba 2.2.2 installed and configured --with-winbind and have the winbindd daemon running but the following does not work: 1. "getent passwd" Solaris command on returns local users (no Domain users) 2. winbindd authentication to the PDC is not occurring. 3. local users cannot change password since I modified the

When I do "getent group", I want to see the group's members enumerated. With nss_ldap they are; with nss_winbind they aren't: root at gumbo:~# getent group mgmt PI\mgmt:*:1040: There *are* members there (partially redacted): root at gumbo:~# ldbsearch -Htdb:///var/lib/samba/private/sam.ldb cn=mgmt member # record 1 dn: CN=mgmt,CN=Users,REDACTED member:

hi all ! I have compiled Samba 2.2.2 for Solaris 7 ( Solaris 8 also ) but found out that the "nss_winbind" support is available in source-code, but not after compilation. The neccessary entries in the Makefile after "configre" are missing !! Why ? I have got it to run and it works fine with a small amout of groups. But deploying this samba/winbind version to a Windows

This patch attempts to address an issue some have reported where our nss_winbind is even slower than it's simple non-caching implementation needs to be. I think this comes from us not handling the BUILTIN domain properly, and so we constantly attempt to contact the DC, and then fail an internal validation step, throwing away that connection. I think this is also the cause of crashes folks

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Well, I think this is not the only time you guys ever seen that kind of mails. First of all, I did checked all that is to be checked before writing to list. wbinfo -u and wbinfo -g work flawless. Also wbinfo -a, so I can authenticate without problems. The setup is a normal trust setup where domain X (my domain) trusts domain Y (another company).

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ========================================================== == == Subject: Buffer overrun in NSS host lookup Winbind == library on Solaris == CVE ID#: CVE-2007-0453 == == Versions: Samba 3.0.21 - 3.0.23d (inclusive) running on == Sun Solaris == == Summary: A potential overrun in the gethostbyname() == and getipnodebyname() in the

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ========================================================== == == Subject: Buffer overrun in NSS host lookup Winbind == library on Solaris == CVE ID#: CVE-2007-0453 == == Versions: Samba 3.0.21 - 3.0.23d (inclusive) running on == Sun Solaris == == Summary: A potential overrun in the gethostbyname() == and getipnodebyname() in the

Hi all, New to Samba here so please bear with dumb questions. I have a server that's currently running SMB shares off of device 10.0.0.1 on a private network. It has a second device, 10.0.0.2 that I would like to add to the device bindings for Samba. I've tried this in the smb.conf file but it doesn't seem to work. Here's what I tried: workgroup = SOMECOMPANY netbios

Couple questions to those who have the winbindd service up and running... I *think* winbindd is working now... I can browse the samba server through windows explorer and open directories. There is a little delay when I first connect... I assume this is winbind passing the authentication request to my NT servers and awaiting a response. The problem now is that I can't seem to write to the