similar to: Why need to add a machine account to /etc/passwd first with Samba+LDAP

Looking through this chapter today and ran across the following inconsistency under the section NT4 Migration Using LDAP Backend. Step 3 says "3. Create a file called preload.LDIF as shown in Example 8.1. Edit the contents so that the domain name and SID are correct for the site being installed." Then step 4 says "4. Preload the LDAP database so it is ready to receive the

Hi people, Been doing a server installation with Samba as a primary PDC that uses an LDAP backend on CentOS 5. The thing is that I cannot be able to get Samba and LDAP to talk as they should and now Im really stuck. Below are my dumps for /etc/samba/smb.conf, ldap.conf (copied its contents to /etc/openldap/ldap.conf too), and smbldap.conf. Excuse my long post; trying to be as elaborate as

Trying to net rpc vampire an NT4 server Think I am good to go but I keep getting errors - obviously problem with NextFreeUnixId attribute - which is created... dn: cn=NextFreeUnixId,dc=myhomelenders,dc=net objectClass: inetOrgPerson objectClass: sambaUnixIdPool uidNumber: 1000 gidNumber: 1000 cn: NextFreeUnixId sn: NextFreeUnixId structuralObjectClass: inetOrgPerson Every item gets this

Hi, I'm tyrying to set up a Samba PDC with LDAP backend, i followed the excellent samba guide on the chapter making users happy, the problem is according to the guide when I execute the smbpasswd -w "secret" command, the expected outcome is Setting stored password for "cn=Manager,dc=abmas,dc=biz" in secrets.tdb but what i get is Setting stored password for ""

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

Hi. Excuse my English. I've installed Samba+OpenLDAP as a PDC. Everything works fine but Samba ignores completely group information. Linux is ok. Any clue? I'm going crazy here! Here's the sittuation: user: fish1 home dir: /home/reaml/swim/fish1 primary group: swimmers other groups: smokers Directory of smoker's group: /home/realm/smokers Here's an 'ls -l' on

* distro: ubuntu breezy ( 6.06 ) * samba version: shipped version with updates ( 3.0.22-1ubuntu3.1 ) * no ssl * openLDAP is running on the same machine as samba, and referenced as localhost/127.0.0.1 where applicable ( 2.2.26-5ubuntu2.1 ) * nscd is not installed, much less running I've set up a samba pdc with ldap by following the Samba Guide very closely, adapting it to Ubuntu/Debian where

Hi All, I am going through a setup of a test samba3 box with rh9 with my self rolled copy of 3.0.10. I have removed the old rpm version of samba. I compiled 3.0.10 with all defaults except for the install prefix which I set to /usr/local/samba3. I followed the steps given in Chap 6 - making users happy in the online html version. I changed a few things. Instead of MASSIVE as the PDC name I

"My Documents" folder doesn't sync with the server unless users log off from the machine and log back in. Is there a way to sync the "My Documents" folder during the session? Thank you. --------------------------------- Do you Yahoo!? Yahoo! Search presents - Jib Jab's 'Second Term'

I'm attemtping to configure a Ubuntu server for a bunch of windows clients. I'd like the authentication information to be in ldap.So far the stuff works, I can authenticate users in LDAP just fine. But when I want a windows machine to join the domain I get the error 'The user name could not be found'. The computer account gets created (via smbldap-tools) and I can see it in the

Daniel R. Meigs wrote: > Thanks for your reply. The problem was having the computers in ou=Computers. > I put them in ou=People and the problem was solved. > > --Dan > Daniel: I deleted the following options from the smb.conf #ldap user suffix = ou=People #ldap machine suffix = ou=Computers But I left the options set in my smbldap.conf.

After, oh, six months of attempts here and there to read everyone's experiences with Samba/LDAP and inability for a windows 2000/XP machine to join the domain, I finally discovered what was not working properly. In my smb.conf I put: add machine script = /usr/local/sbin/smbldap-useradd -w "%u" As instructed by many How-to's and Idealx. However, I thought to myself, %m

I have an OpenLDAP backend, Samba knows how to talk to it, my Samba users are stored in LDAP and file shares work fine authenticating to the LDAP server. I tried executing smbldap-useradd -w server02 on the command-line and got the following error: failed to perform search; Can't contact LDAP server at /usr/lib/perl5/vendor_perl/5.8.7/smbldap_tools.pm line 362, <DATA> line 283. Error

After further review, I don't believe this is the proper approach to the problem. It seems to me that the %u is being used ambiguously. The logic of how the published API of the variables and the call to the smbldap-useradd program makes it important for the documenters to understand what the tools are doing... not what is happening in samba. We can see what is happening with the tools by

Hi, I running samba-3.0.13-1 on RH9 (openldap-2.0.27-8,krb5-1.2.7-10,nss_ldap-202-5) and configured as show below, my intention is only to make IDMAP storage in LDAP using winbind. I've looked on SAMBA3 by example book and relatives official guide on the site. First I have try to run samba and winbind retriving users and groups from ADS and storing them in winbindd_idmap.tdb and

Greetings! I created a Samba/OpenLDAP/smbldap-tools Primary Domain Controller. So far I am able to do the folowing: 1. Using USRMGR,EXE to administrating users and groups. 2. Adding Windows 2000, XP workstation on the fly. 3. PDBEDIT/SMBLDAP-TOOLS/GQ all works as they suppose to. 4. LDAP autheticate unix accounts. However, I am not able to to the following:

need clarification of the use of: ldap suffix ldap machine suffix ldap user suffix ldap idmap suffix smb.conf.5 indicates you should have a fully qualified suffix such as: ldap suffix = dc=blah,dc=com ldap machine suffix = ou=People,dc=blah,dc=com ldap user suffix = ou=People,dc=blah,dc=com ldap group suffix = ou=Groups,dc=blah,dc=com ldap idmap suffix = ou=Idmap,dc=blah,dc=dom

Hi, I have the following directory shared for the user "pcbadmin". He/she can mount and read/write without any difficulty: [pcbdata] comment = PCB Design Files path = /home/pcbadmin/pcbdata valid users = pcbadmin public = no writable = yes Question: How can I make the same directory only readable by the rest of the users ? TIA, Ben

Greetings, I have Samba 3.0.10 set up with ldapsam (OpenLDAP 2.2.13) and smbldap-tools 0.8.8, using start tls. Account info etc. is read properly from ldap, and adding/removing/modifying users with the "net" command works fine. Oddly, if I try to use USRMGR, for instance, to add a user, only the posix account gets created (by the smbldap-tools script) but the samba sam account add

question on pdbedit - when using it for a migration - existing data is stored in tdbsam. pbdedit -i tdbsam -e ldapsam It wants to take existing machine accounts and put them into an ou=Computers. I'd rather it put them in ou=People. Samba version is 3.09 Thanks....... Jon Johnston Creative Business Solutions IBM, Microsoft, Novell/Suse, Sophos Consultants http://www.cbsol.com