Here is the situation. An LDAP Server running SuSE 7.3 OpenLDAP2 (stock RPM) A Samba Server running SuSE 8.0 Samba 2.2.5 (downloaded from suse ftp and compiled with ldap support) An admin workstation running 8.1 supposed to run Directory Administrator. Stock rpm for directory administrator (1.1.9) connects and shows all the accounts. Which were created with idealx commandline scripts. However as I stated before, directory admin 1.1.9 fails to suffice Samba LDAP PCD management. What I've learnt from Directory Administrator guys is that the problems are corrected in the latest release. Although they were very helpful and responsive, none of them seem to be using SuSE and I'm still trying to figure out how to compile the latest version 1.3.4 Here's what I'll do. Try to compile directory admin on 8.1 if I succeed, I'll make it available to both SuSE users and directory admin users, If I fail, I'll go and install debian on my notebook and never again have to worry about making a good piece of software available for myself :) BTW, I really wonder who made 1.1.9 available to SuSE.
On Wednesday 05 February 2003 07:55, Oyku Gencay wrote:
Hi,
I'm using stock directory_admin RPM supplied with SuSE 8.1 version 1.1.9. I'm having difficulty in maintaining my OpenLDAP Samba accounts. The problem is when I try to edit or add an account with samba enabled I get "object class violation" when adding and get "required field empty ..." error. I've tracked the problem and found out that diradmin is not setting the mandatory "rid" field. Which seems to be required for the sambaAccount object in samba.schema supplied with samba. And it's calculated as userrid=2xuidNumber+1000xgrouprid (information extracted from www.idealix.org)
Am I missing something or is rid field not calculated in dir admin, or should I upgrade to latest? If this feature is not present, I'd try to add.
Best regards, Oyku
How did you get stock directory_admin to work. I get a protocol error when I attempt to test the connection or when I connect. I can connect with the character based LDAP tools, and kaddressbook (with 3.1) will talk to the OpenLDAP server but most tools give the protocol error.
I have all the latest patches from SuSE, but I just can't seem to get most LDAP stuff to work properly. I haven't tried using SuSE as a PDC with LDAP as I have to have an NT server for something that I am working on, so it is my PDC. However, it could go away very soon and then it would be nice to have LDAP working properly as the only machine left with WinDoze will be the one my kids use for games and a little surfing.
-- Kelly L. Fulks Home Account
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com