similar to: Winbind login: has "DOMAIN+user", wants "user"

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

Hi all, we're using Winbind on a Solaris 9 machine to authenticate our Users, who are held in a Windows 2003SP1 AD. We are now using Samba 3.0.21b and everything works as expected. I configured the nsswitch and installed "libnss_winbind.so" and "pam_winbind.so" as described in the documentation and winbind is able to resolve the AD users and groups and the useres are able

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

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

I am attempting to use winbind for Telnet authentication but winbind pam doesn't recognize ads realm or smb.conf workgroup..see error snapshot. pdtsun03 is hostname of solaris 10 ADS domain member running samba 3.0.11. "net ads join" worked..."net ads user" returns all MYADSDOMAIN users and samba shares work from both unix and NT side. one note..After make install, I

Hi everyone, I'm trying to use winbind as nsswitch module on a domain member against a samba PDC, and it used to work fine with samba 3.4. But now after upgrading to 3.5.11, getent group/passwd don't show domain users/groups anymore. However wbinfo -g and wbinfo -u work as expected. Also: # wbinfo -i matare matare:*:50011:50000:Victor Matar?:/home/SGI/matare:/bin/false # wbinfo -U 50011

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

Update: Success!!!! The corrective action was to move the below pam.conf settings to the top of each section. auth sufficient /usr/lib/security/pam_winbind.so try_first_pass account sufficient /usr/lib/security/pam_winbind.so try_first_pass session sufficient /usr/lib/security/pam_winbind.so try_first_pass -----Original Message----- From: Garrett, Joseph Sent: Thursday,

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

Hello I have been having problems with authentication on a suse 9 box with samba 3.0.3 installed from rpms. I have googled till my fingers bled, there is just the question, no answer, someone must have been able to solve it out of all the people who had the problem? I joined the domain with net join, this was successful I can list users/groups, authenticate and check the secret with wbinfo

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

Hello all, I currently have the following setup working nicely: A Samba PDC, with LDAP-SAM, syncs passwords between LDAP and Samba (and /etc/shadow when appropriate) correctly - either when changing them through Samba (samba has PAM support enabled and working) or through normal Unix mechanisms (/usr/bin/passwd, using pam_smbpass, pam_ldap, etc.). Several other Linux machines, running Samba,

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

Solaris 8, Samba 3.0.1, Winbind with LDAP backend and security = ads. This may or may not be a problem, depending on what is "expected behaviour". We came across a user that was defined both locally and in AD. Their local primary group, call it "localgrp", was not the same as their global primary group, call it "globalgrp". One important note is that by using an

I'm trying to setup a Solaris 10 Sparc station to authenticate users on login with Windows ADS. I have found the documentation for this but having no luck in getting the pam modules to work. Here is what I have done so far: Compiling Kerberos MIT5-1.8.3: cd into the src directory ./configure --prefix=/opt/local gmake gmake install Compiling Samba 3.5.6: setenv CFLAGS "-O2"

Hello everybody, for a while I am running a Samba 4.1 AD server under FreeBSD (from the FreeBSD ports). At thw moment the domain has ca. 20 Windows 7 desktops. I wanted to add a Samba 4.1 file server as a member server, was able to joint the domain and see AD users via "winbind -u" but "getent password" or "id <user>" does not work. The smb4.conf is

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