similar to: Understanding Documentation about BDC in HowTo Collection

On Apr 29, 2008, at 1:27 AM, Gabor Greif wrote: > Hi all, > > I have reported more than enough about the space savings achieved > and the associated costs, here comes the current patch for review. > > Since this one is substantially smaller than the previous one, I did > not cut it in pieces. The front part is about headers and the rest > the .cpp and other files. Hi

Hi List, Last week i have upgrate my samba from 3.023d to 3.0.28 and now i have some trouble in my LOGs like this: Dec 31 08:59:23 ldapmaster smbd[10453]: pdb_increment_bad_password_count: pdb_get_account_policy failed. Dec 31 08:59:39 ldapmaster smbd[12758]: [2007/12/31 08:59:39, 0, effective(0, 0), real(0, 0)] passdb/pdb_get_set.c:pdb_get_group_sid(211) Dec 31 08:59:39 ldapmaster smbd[12758]:

Hopefully, you can help me out. I'm trying to figure out why I'm getting the error I get. From the debug output, it looks like it's adding the objectClass to the user (so they can get the sambaSID attribute attached to them), but it's not actually happening. The schema is, obviously, in the LDAP server in question. Any thoughts? D # smbpasswd -D 99 -a testuser Netbios name

Hi all, I have reported more than enough about the space savings achieved and the associated costs, here comes the current patch for review. Since this one is substantially smaller than the previous one, I did not cut it in pieces. The front part is about headers and the rest the .cpp and other files. Cheers, Gabor -------------- next part -------------- An embedded and charset-unspecified

OK, I had this working a few days ago, but have evidently changed something that I cannot locate. Someone hit me with their 2x4. Samba 3.0.22, Fedora Core 4, ldapsam (OpenLDAP 2.3.24). smbd will not start, with the "ERROR: failed to setup guest info" error (I have "guest account = guest", which is a valid user with correct info in LDAP): ldap_connect_system: Binding to ldap

Hi! i run samba 4.1.2 in DC mode. win7 client joined to this domain successfully. now i try to configure external idmap. i would like it to use our existing ldap server: idmap config DOM : backend = rfc2307 idmap config DOM : range = 1110000-1119999 idmap config DOM : ldap_server = stand-alone idmap config DOM : ldap_url = ldap://ldap.domain.ru idmap config DOM : ldap_user_dn =

Hi, I did upgrade from samba 3.0.28b to 3.4.9. Now the trust does not work anymore. When we try to reestablish the trust, we get an error: ldapmaster:/etc/openldap/schema # net rpc trustdom establish BIO Enter EVAN$'s password: Could not connect to server HEINBLOED Storing password for trusted domain failed. Google does not really help and logfiles (loglevl 10) do not tell me what is wrong.

Hi, I have installed and configured Samba as PDC with Heimdal kerberos and openLDAP as backend for both on debian lenny. But i stuck on groups. I have created a file in my home directory mapped to my documents. I can change rwx permission on linux and windows and it works perfectly. but this file has as a group my default group. this file should be read by users from accounting and managers

I've only got LDAP configured as a passdb type in my smb.conf, but samba appears to be completely ignoring that and creating an /etc/samba/smbpass file (full output of that at the bottom) my smb.conf has: ldap admin dn = "cn=Admin,dc=byramhealthcare,dc=com" ldap ssl = off passdb backend ldapsam:ldap://ldapmaster.byramhealthcare.com ldap delete dn = no ldap user suffix =

We've just built a RHEL 5 ES server to test the issues we've been having with group permissions since 3.0.23 (re: 3.0.23d UNIX vs. AD group permissions) and we found we have the same issue with the Redhat built rpm of version 3.0.23c. The following is the ldap and winbind portion of our smb.conf, the same as used on our current Solaris production servers: # ldap settings ldap

I have a samba 2.2.8a PDC. I want join my windows 2000 cluster on this PDC. I join first node without problem. The problem is with second node. When I try join this node i recieve this error: " mydomain\root does not have permission to administer the cluster . Please use an account that has access privileges to the cluster" I have verify the permission of user root on first node