similar to: Authentication problem when using LDAP

I can't really guess the point of your intelligent answer from this. If I have to assume you're surprised, I guess I am too. The cn exists in ldap, with all the attributes that I imported from other databases, the message given by smbpasswd suggests that it either tried to create an entry or update it with sambaaccount attributes ( which it didn't ), neither of which are the expected

freebsd 5.3, samba 3.10 I get this far with LDAP/Samba integrationg. Stuck on creating users/machines with smbpasswd -a (-m) username command. schema files weren't modified, everything else is pretty much at defaults. First the relevant config parts: passdb backend = ldapsam_compat:ldap://localhost/ ldap suffix = dc=company,dc=com ldap machine suffix = ou=Computers ldap user suffix =

Hello everybody, I'm asking myself a rather simple issue (i hope it hasn't already be explained somewhere). I'm using ldapsam_compat on 3.0.1pre3(+Debian patches & smbldap-tools 0.8.1) to store both user accounts and machine accounts. It works just fine, but there still is something that i find quite odd. My smb.conf contains: add machine script =

Hi all, In an attempt to get the old v2.2 Samba behaviour to work, I tried to enable the ldapsam_compat mode in passwd backend. Win2k cannot connect, username and password not accepted. The LDAP logs reveal that Samba is trying to make the following search: (&(&(uid=minfrin)(objectClass=sambaSamAccount))(objectClass=sambaAccount)) This search returns users who have both the old v2.2

I'm having some issues with samba 3 and my ldap passwords. First I'll tell you what I'm working with. Ldap server is RH 7.3 and openldap 2.0.25 DBM Samba 3.0.2a-1 using ldapsam_compat (Compiled from RPM source by me ) on RHEL 3 Samba 2.2.8-1.ldap on RH9 -------------- The Samba 2 works great. Auth against ldap no problem, has been for over a year. The Samba 3 does not work.. Well

Sorry to repost this question.. But I am at my wits end.. The server has been off line for 2 weeks. So I will have to downgrade to samba 2.X by the end of the day unless a miracle happens ;) I'm having some issues with samba 3 and my ldap passwords. First I'll tell you what I'm working with. Ldap server is RH 7.3 and openldap 2.0.25 DBM Samba 3.0.2a-1 using ldapsam_compat (Compiled

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have seen this problem posted several times and the common answer doesn't seem to be doing it for me. Here's the error: Trying to load: ldapsam_compat:ldap://127.0.0.1/ Attempting to register passdb backend ldapsam Successfully added passdb backend 'ldapsam' Attempting to register passdb backend ldapsam_compat Successfully added

Hi all, I'm sorry i have to complain about something that seems to go wrong with samba. I'm a long time satisfacted Samba 2 user and i have to switch to 3.0. I'm using samba 3.0.0 on a test Debian machine with pre-built packages from Debian. It comes with openldap 2.1.22 I've tested Samba 3.0 as a PDC for WinXP machines... and it works great! :-) But i am facing an issue i

This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_000_01C344B0.28BC0750 Content-Type: text/plain; charset="windows-1252" Summary: Currently R provides > dev.control(displaylist='inhbit') to turn *off* the recording of graphics operations in a device, but there is no

Hello all, I'm having an issue with adding machine accounts to a Samba 3.0.0 PDC with an LDAP passwd db backend. This is on a RedHat 9 with an rpm I compiled from the 3.0.0 release. I have configured samba to where it is using LDAP and able to add user accounts and group mappings to LDAP, but when I try to add a computer account using smbpasswd -a -m data it is not able to add the account.

Hi All, I Have installed the Sun Directory Server 5.2 from JES 2004Q2 CD's with following options /etc/hosts 192.168.1.23 train01.tipu.com.pk train01 loghost DNS is running for tipu.com.pk on the same machine and here is /etc/resolv.conf domain tipu.com.pk nameserver 192.168.1.23 Directory Server installed using the following Suffix dc=tipu,dc=com,dc=pk when i run

I am trying to apply methods used by Chaloupka & Limpus (1997) ( http://www.int-res.com/articles/meps/146/m146p001.pdf) to my own turtle growth data. I am having trouble with two things... 1) After the GAM is fit, the residuals are skewed. >m1 <- gam(growth~s(mean.size, bs="cr")+s(year,bs="cr",k=7)+s(cohort,bs="cr")+s(age,bs="cr"), data=grow,

Hi, We have a linux/samba only domain serving files to about 16-18 Windows clients (mostly XP, a few W2K). PDC: SuSE OpenXchange 4.4 samba 2.2.8a openldap 2.1.4 Domain Member Server (DMS) CentOS 4.4 samba 3.0.10 I set the Domain Member Server up using the default passdb backend (/etc/samba/smbpasswd) to start with and that all worked fine. I would like to use LDAP for centralised

Problem number one: ------------------- I'm running a few-hours-old CVS version of Samba 3.0 with LDAP as the authentication backend, and I'm having some problems trying to set up the LDAP accounts using "smbpasswd". I build the structure of the LDAP database by importing a couple of LDIF's, and then I import the following user account to create an administrative account

Hi, when I try to add an user with smbpasswd -a test_user I get teh following error. ----- Trying to load: ldapsam_compat:ldap://localhost Attempting to find an passdb backend to match ldapsam_compat:ldap://localhost (ldapsam_compat) No builtin backend found, trying to load plugin Probing module ldapsam_compat: Trying to load from /usr/local/samba/lib/pdb/ldapsam_compat.so Error loading module

Hi, when trying to upgrade my smb servers from older 3.x versions to samba 3.0.23, I discovered, that (already in 3.0.22), the "--with-ldapsam" option has been removed. According to the corresponding entry in the release notes, this was "only used for backwards compatibility for 2.2 smb.conf files". As far as I can see however, not only the configuration file syntax has

I'm in the process of replacing a Samba 2.2.12 PDC with Samba 3.0.14a-Debian. An LDAP database serves as the user data store, and I've made no changes to the Samba 2.2.x-compatible LDAP records. Since I don't relish LDAP schema changes, I've specified ldapsam_compat as my passdb backend; I figured that since I was already running a compatible LDAP schema, there was no need to make

Summary: patch to add environment parameter to load() to allow -------- specification of destination environment. --> Patch against R 0.63.2 appended at end of this message. <-- Story: ------ I've been running some rather long MCMC chains, which occasionally crash, either due to an "Invalid tag in name extraction" error, or due to the machine going down. (I'm playing

Please someone tell me I'm insane. Relevant parts of the config: passdb backend = ldapsam:ldap://ldap.byramhealthcare.com/ ldap admin dn = "cn=admin,dc=byramhealthcare,dc=com" #enable SSL after we get it working without first ldap ssl = off ldap user suffix = "ou=People,dc=byramhealthcare,dc=com" ldap machine suffix = "ou=People,dc=byramhealthcare,dc=com" $

I'm having a problem adding a password to users. I get "NDS error: no additional information available (-306) when I use smbpasswd. Also I can see in ndstrace that the search string is (&(objectClass=sambaAccount)(uid=WORKGROUP/test)) and not (&(objectClass=sambaAccount)(uid=test)). I have "ldap fileter = (&(cn=%u)(objectClass=sambaAccount)) in my smb.conf. Another