similar to: id mapping / group mapping

Hi, I've reported this before but I guess I'll have to do it again, since it's not fixed yet or I'm understanding something wrong here. The problem is that smbldap-useradd -w 'machinename' will add only posixAccount entrys into ldap but it should add both posixAccount and sambaSAMAccount entrys. So if one doesn't add correct machine account entrys manually to ldap

samba 3.0.2 smbldap-tools 0.8.4 RH 9 nss_ldap configured pam_ldap NOT configured LDAP passwd backend winxp pro domain member Hello, i've configured smbldap-tools in smb.conf to manage users from usrmgr.exe. It works at group creation but have a strange behavior in user creation. In the LDAP there are two manually created accounts; Administrador & invitado, both posixAccount and

Hi, we are using Samba 3 ( CVS checkout from 09/01 ) on a SuSE 8.2 box with all patches applied. The passdb backend is LDAP / eDirectory 8.7 on another machine. The Samba box is supposed to work as a stand alone domain controller, so I am testing to join a client machine to it's domain. This is my "add machine script": /usr/bin/cpu useradd %u -d /dev/null -f

Hi all, I'm new on this list and I'm french, so my english could be worst !;) My question is about sambaSamAccount and posixAccount objectClasses. I want the user "test" be mapped to user root (uid=0, gid=0) when logged into pam over ldap mechanism (such as ssh) And I want the same user "test" be mapped to user test (uid=1003, gid=513) when logged to Samba server.

St?phane, The book "Samba-3 by Example" is being reprinted very soon. Up to date builds of the PDF are available on the Samba web site daily. This document can be downloaded from: http://www.samba.org/samba/docs/Samba-Guide.pdf In chapter 5 I have fully documented how Samba-3 can be deployed with LDAP and using the smbldap-tools. It works perfectly for me and in many sites that

I am still trying to troubleshoot my problem of not being able to join computers to the domain. I have found this comment by John Terpstra:- >Newsgroups: linux.samba >From: John H Terpstra <j...@samba.org> - Find messages by this author >Date: Wed, 14 Jan 2004 00:00:17 +0100 >Curtis, >Do not set the UID of Administrator to 0, it will break winbind use. >Instead, use the

Please help! I'm having a difficult time getting a machine to join my domin. Samba sucessfully adds the machine account using the smbldap-useradd -w script, but I get the error "The user name could not be found". Here's what it looks like it's doing in the ldap logs: 1. There's a login as cn=Manager, which searches for the root account, and then for a bunch of

Stephanie, Thank you for your help. I tryed what you suggest but no luck.. I get this: root@lnxsrvr2:~# /usr/local/samba/bin/net groupmap add ntgroup="Domain Admins" unixgroup="Domain Admins" rid=512 Can't lookup UNIX group Domain Admins Is there something with initial compiling samba 3.0.0 that would disable this? All the documentation that I've seen makes it look so

Mother always told me that there'd be days like this. She just didn't tell me that they go on for weeks. OK - John's book suggests that we're not complete in this arena here...Yeah, I bought the Samba 3 How-to-guide - Borders/Phoenix had 3 on the shelf (now 2) - and also an LDAP book for reference. It's been a fun weekend ;-) problemo... # smbpasswd -x -i MULLEN

Hi list, Could anyone explain why Samba+LDAP PDC needs to have PAM and NSS configured with ldap to authenticate ? I thought that SAMBA authenticates directly against LDAP rather asking PAM/NSS to do this, but this doesn't seem to be true. I configured a Samba+LDAP PDC with the help of idealx.org SAMBA PDC howto. I succeeded with 3.0.2a. Just for experimenting, I used authconfig to disable

Our Samba server was recently the recipient of a major upgrade. I thought all the kinks were worked out, but apparently not. I think this is the first time I've tried to join a machine account to the domain since the upgrade. I've tried using smbldap-tools and also just using smbpasswd (I have my users in LDAP). I'll also say that 'net join' works just fine from my Samba

I have tried to create a samba domain with a ldap backend. This is how my ldap structure looks like. # example.com dn: dc=example,dc=com objectClass: dcObject objectClass: organization o: example dc: example # groups, example.com dn: ou=groups,dc=example,dc=com objectClass: organizationalUnit ou: groups # Domain Admins, groups, example.com dn: cn=Domain Admins,ou=groups,dc=example,dc=com

Hello guys! I'm using samba 3.2.4 (binaries from samba.org) on SLES9+sp3. I am building a PDC with LDAP support (i am attaching my config files), I'm also using ldapsam:trusted and ldapsam:editposix. Although I am setting the account lock after 3 failed tries in usrmgr, and verified that the parameters are actually set in the LDAP, no locking occurs. I started thinking that it was my

> > On Sat, 3 Jul 2004, Tilo Lutz wrote: > > > None of my acounts in ldap have set sambaPwdLastSet, even those > > > acounts which became disabled. If I have understand you right, > > > samba should not disable account if the attribute sambaPwdLastSet > > > is not defined in ldap? > On Mon, 2004-07-05 at 06:56, Gerald (Jerry) Carter wrote: > > If

Hi All, The smbldap-tools in latest Samba tarball 3.0.1 use SambaSAMAccount rather than SambaSamAccount as per the samba.schema file. Attached are four patches to fix this. Darren -------------- next part -------------- --- smbldap-useradd.pl.orig Tue Dec 30 22:34:08 2003 +++ smbldap-useradd.pl Tue Dec 30 22:38:19 2003 @@ -208,7 +208,7 @@ if (!$with_smbpasswd) { # (jtournier)

Hi! I have a problem connecting WinXP clients to my samba3/ldap domain (see my earlier post). I'm using the idealx scripts and they do create a machine account, even if i try to add the machine from WinXP itself. Now I noticed the machine account created by this script has object classes top, inetOrgPerson and posixAccount, but NOT sambaSAMAccount. Is this correct? I thought they should be

Hello, I have a question about machine accounts. I using Samba 3.0, OpenLDAP 2.1.30 and Berkeley 4.2.52 on backend on RedHat machines. I also have 3 slave/BDC's and 1 master/PDC Right now all of my users and groups exist entirely in the LDAP directory. I have a few accounts in addition to the normal system accounts that are used for emergency access. All authention and group enumeration uses

We're trying to migrate from a windows NT domain to a Samba domain. I've installed Samba 3.0.2a with an LDAP backend. The server seems to be running fine as I can browse the shares from a non-domain Win2k workstation after a successful password check. The workstations join the domain just fine but after I join them to the domain I can't log in to them. I've checked my schannel

Hello everyone, I am operating a migration of samba from 3.0.24 (mysql passdb backend) to 3.5.6 (openldap passdb), samba working as a domain controller (PDC) and file share. The main challenge is to provide a seamless migration for users. For this new version, I am using smbldap-tools 0.9.6, nss_ldap, openldap 2.4. Everything run on FreeBSD 8.2. To get used to samba, I have managed to make

Greetings! It is premature for me to send out a "success procedure for migration" yesterday. I overlooked things and I appologize for to this group. Anyway, after migration, computers, users, groups are all created and filled up with the correct membership. However, I still have the same problem with machine password and user password. Further looking into the detail, it looks