similar to: "ld.so.1: ls: fatal: relocation error: file /usr/lib/nss_ winbind.so.1: symbol socket: referenced symbol not found" - Samba Team?

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

You can test if winbind is able to resolve user IDs internally with "wbinfo -u". This uses the samba tool "wbinfo" to connect directly to the running winbind daemon and list all the Windows domain users. If that fails, then you have problems with the winbind daemon itself. The authentication between winbind and the PDC can be tested with "wbinfo -t", which is usually

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 =

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:

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]

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

I'm hoping this is an easy question, but the way my day has gone I seriously doubt it is going to be. Today, I installed Samba 3.0.24 with winbind support on my FreeBSD 6.2 server. I am able to join my domain and get information concerning groups and passwords from the domain controller (Windows 2003) without any problem. Where I have run into a problem is using getent to get a copy of the

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 i compiled Samba 3.0.28a under Solaris 8 (sparc). Everything seems to be fine except the libnss_winbind.so. i copied it to /usr/lib and linked it to: libnss_winbind.so.1 libnss_winbind.so.2 nss_winbind.so.1 nss_winbind.so.1 now when i use: id user nothing happens. group user is the same wbinfo -t / -g / -u all work fine. So it must be something with the nss I guess?

Hello List I'm running Samba 3.0.24,1 on a freebsd 6 server I've joined the unix server to an active directory domain and set up PAM I've shared directories and users can access them (provided they belong to the correct group) the problem is : if I list the shared directory mail# /usr/local/lib > ls -al /usr/local/www/www.dmsware.it/ total 6 drwxr-xr-x 3 root wheel 512 Apr

HI! I am trying to configure the samba 2.2.7 binary from sunfreeware ( package for Solaris 7). Is there any way to override the default install location of /usr/local/samba for the lock files? I do not have access to /usr/local as it is NFS mounted and shared by all Solaris 7 boxes. I can pkgadd to a different root path, and I can -s the config file to the install location, but I cannot

I'm just curious to see if I'm fighting an uphill battle that isn't really necessary. Is anyone out there NOT using PAM, running Samba and winbind on Solaris 8? Maybe my problems are related to my attempt to keep it simple and not use pam. -Dan Daniel J. Thomas Systems Administrator Johns Hopkins University Applied Physics Laboratory Laurel, MD Balt: (443) 778-7924 Wash: (240)

Hi, I've got Winbind running (or so I think) on my Solaris 8 server using Samba 2.2.3a. Whenever I do a long directory listing on a directory that contains a file placed via the samba share by an NT user on the trusted domain, the SUN box just hangs there. It acts like it is searching the database, but after three or four minutes I just CRTL + C it. Do you think this is winbind not working

Hello list. The issue I have is that with the changes made to the idmap functionality of winbind, as regards the enumeration of rfc2307 users and groups using getent passwd and getent group, only those AD users that are not in the domains included in the "idmap config (domain)" statements (the ones in trusted domains that get their ID mappings auto-assigned by the TDB backend with

I've seen many different samba related pieces of software named through this newsgroup and I'm afraid I don't understand the different between them all. Could someone clarify these for me? Samba - I pretty much understand this... but if You want to explain it in terms of the other pieces of software, go ahead HEAD SAMBA TNG Slackware Winbind - I also think I understand this. If

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:

http://bugzilla.mindrot.org/show_bug.cgi?id=604 Summary: ld: fatal: Symbol referencing errors. No output written to ssh-add Product: Portable OpenSSH Version: 3.6.1p2 Platform: UltraSparc OS/Version: SunOS Status: NEW Severity: major Priority: P2 Component: Build system

http://bugzilla.mindrot.org/show_bug.cgi?id=604 Summary: ld: fatal: Symbol referencing errors. No output written to ssh-add Product: Portable OpenSSH Version: 3.6.1p2 Platform: UltraSparc OS/Version: SunOS Status: NEW Severity: major Priority: P2 Component: Build system

Ive installed and configured samba using cd samba-3.0.21b/source ./autogen.sh ./configure --with-krb5=/usr/local \ --with-automount \ --with-pam \ --with-utmp \ --with-winbind \ --with-libsmbclient \ --with-ldap \ --with-netlib='-lresolv' make make install cp nsswitch/pam_winbind.so /usr/lib/security cp

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