similar to: solaris 8/samba3.0alpha15: ld.so.1: ls: fatal: relocation error: file /lib/nss_winbind.so.1: symbol socket: referenced symbol not found

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]

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'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

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

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

> Several questions posted with no reponse for solaris 8, samba3.0alpha15: > > * testparm whining about valid.dat, users.dat, etc. (If you copy > those files from the source directory and plop them in > /usr/local/samba/lib, my users can not map a drive or send files with > smbclient to nt share.) Testparm output errors: > > incorrect size for

Just replying to let you know I'm listening =)... Sorry Dave, I'm running 2.2.3a on my Solaris 8 machine and even that still has some issues with winbind. By the way, while I have the attention of you Solaris Gurus... I was trying to make my Ultra 1 boot from an external disk on the same scssi channel as the default boot disk. I changed my /etc/vfstab for the new disk to have the right

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

First, don't shout when you set the subject. It just looks like spam. >* Why does testparm complain about can't find include file? > Can't find include file Something tells me that you have an include line in your conf file in the form of include = /usr/local/samba/lib/smb.conf.%m which it tries to include, for every machine that accesses your server, and of course fails,

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

I use a script to get the lastest samba: #!/usr/bin/ksh echo "\npassword: cvs\n" cvs -d :pserver:cvs@pserver.samba.org:/cvsroot login cvs -z5 -d :pserver:cvs@pserver.samba.org:/cvsroot co samba Are there any other commands I could tack on or something I should do differently to make sure I am getting correct rebuilds? For example, should I tack on at the end: cd

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

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

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:

I am running cvs download of samba head 3.0x and it is giving a lot of "it is in the way" messages. I don't recall that from before. I thought it would just overwrite the same file names. Is that not the case, or has something changed about how the cvs comes down? David David E. Shapiro Senior Unix Admin BTi - the future of communications 4300 Six Forks Road, Raleigh, NC 27609

-----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).

I ran some tests to see why getent passwd was not enumerating my domain users and discovered this: If I getent passwd <username> it returns the user information including the primary group defined in the Unix attributes. If I add a Unix GID in the idmap config range to the domain's Domain Users group and getent passwd, it returns all of my domain users with all of the Unix attributes as

Hello list users, I have been struggling to make my AD integrated Debian Lenny box to work fluently also when network connectivity is down. What I would like to achieve: 1) When no network available, local user should still work normally 2) If possible, AD located users should still be able to login if they have previously logged in successfully (cached login) Number 2 is more like optional,

Hello, I'm trying to integrate some of our Solaris 10 10/09 hosts into Microsoft AD running on 2003/2008 R2 servers. After some compile trouble I finally managed to get the whole thing running including winbind in nsswitch.conf for users and groups and PAM for authentication. The problem is that winbind only reports the primary group of an AD user. 'wbinfo -r aduser' only reports

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