Page 2 of 3 FirstFirst 123 LastLast
Results 11 to 20 of 25

Thread: Zimbra + LDAP + Posix + Samba

  1. #11
    Greg is offline Zimbra Employee
    Join Date
    Sep 2005
    Location
    Tucson - San Francisco - Moscow
    Posts
    127
    Rep Power
    9

    Default There's a bug

    Bugzilla - Wiki - Downloads - Before posting... Search!
    P.S.: don't forget to vote on this bug
    add Samba LDAP entries to Exchange Migration Tool

  2. #12
    Greg is offline Zimbra Employee
    Join Date
    Sep 2005
    Location
    Tucson - San Francisco - Moscow
    Posts
    127
    Rep Power
    9

    Default

    Just fixed the bug (will be in 5.0.3) and fixed some errors in the HowTo for Zimbra+Samba integration.
    Bugzilla - Wiki - Downloads - Before posting... Search!
    P.S.: don't forget to vote on this bug
    add Samba LDAP entries to Exchange Migration Tool

  3. #13
    adewhurst is offline Starter Member
    Join Date
    Feb 2008
    Posts
    2
    Rep Power
    7

    Smile Thanks



    Thank you very much for your help Greg, it's much appreciated!

  4. #14
    montyZdog's Avatar
    montyZdog is offline Member
    Join Date
    Jun 2007
    Posts
    14
    Rep Power
    7

    Default Admin interface does not load without clearing brouwser cache

    I have a slightly different problem.
    After upgrate directly from 4.5.5 to 5.0.2 everything is working but Admin interface is very slow to load when zimbra_posixaccounts and zimbra_samba zimlets are deployed.
    I still CAN login as a Domain Admin user as well as a Zimbra admin user who does not have posix/samba account. But the picture is the same. When a browser is reloaded Admin interface can be accessed. When I log out and log back - the browser (Firefox) hungs with this message in the status line:
    Loading script:/zimbraAdmin/res/zimbra_posixaccount.js?v=080130223433
    If I then go to Advanced preferences and clear the cache - I am able to load the Admin interface again.
    Since as I mentioned, I am able to login to Admin interface as Domain Admin, this is not exactly the case of the discovered bug.
    I wonder, if the fix in 5.0.3 also address the above problem?
    Last edited by montyZdog; 02-28-2008 at 10:09 AM.

  5. #15
    montyZdog's Avatar
    montyZdog is offline Member
    Join Date
    Jun 2007
    Posts
    14
    Rep Power
    7

    Default HowTo question

    Quote Originally Posted by Greg View Post
    Just fixed the bug (will be in 5.0.3) and fixed some errors in the HowTo for Zimbra+Samba integration.
    Greg,
    In my contributed paragraph on Configuring on RHEL5/CentOS5/Fedora7 using authconfig should there be changes in /etc/ldap.conf example?
    I mean if binddn should be changed to "cn=config" for Zimbra 5.x ?
    Last edited by montyZdog; 02-28-2008 at 11:57 AM.

  6. #16
    montyZdog's Avatar
    montyZdog is offline Member
    Join Date
    Jun 2007
    Posts
    14
    Rep Power
    7

    Default

    [Follow up]
    The above mentioned problem with the Admin interface has gone after I read about Bug 24477 and removed 'sambaAccount'. I kept sambaSamAccount and posixAccount installed as per Wiki. Everything seemingly works and I can mange Samba accounts with Zimbra 5.0.2 GUI including creation of new ones (With 'sambaAccount' loaded I had the error featured in Bug 24477)
    Question now, how do 'sambaAccount' and 'sambaSamAccount' relate? Is it OK if only the latter is installed?
    The Wiki on Zimbra-Samba integration has no mention of 'sambaAccount'

  7. #17
    Greg is offline Zimbra Employee
    Join Date
    Sep 2005
    Location
    Tucson - San Francisco - Moscow
    Posts
    127
    Rep Power
    9

    Default

    Quote Originally Posted by montyZdog View Post
    Greg,
    In my contributed paragraph on Configuring on RHEL5/CentOS5/Fedora7 using authconfig should there be changes in /etc/ldap.conf example?
    I mean if binddn should be changed to "cn=config" for Zimbra 5.x ?
    Yes, binddn should be changed to "cn=config"
    Bugzilla - Wiki - Downloads - Before posting... Search!
    P.S.: don't forget to vote on this bug
    add Samba LDAP entries to Exchange Migration Tool

  8. #18
    Greg is offline Zimbra Employee
    Join Date
    Sep 2005
    Location
    Tucson - San Francisco - Moscow
    Posts
    127
    Rep Power
    9

    Default

    Quote Originally Posted by montyZdog View Post
    [Follow up]
    Question now, how do 'sambaAccount' and 'sambaSamAccount' relate? Is it OK if only the latter is installed?
    The Wiki on Zimbra-Samba integration has no mention of 'sambaAccount'
    sambaAccount and sambaSamAccount are both auxiliary classes for posixAccount. You should not be using both classes at the same time, because they conflict. sambaSamAccount was introduced in Samba 3 to replace sambaAccount. You can look into Samba release notes for more details about this, but the bottom line is use sambaSamAccount and do not use sambaAccount.
    Bugzilla - Wiki - Downloads - Before posting... Search!
    P.S.: don't forget to vote on this bug
    add Samba LDAP entries to Exchange Migration Tool

  9. #19
    montyZdog's Avatar
    montyZdog is offline Member
    Join Date
    Jun 2007
    Posts
    14
    Rep Power
    7

    Default

    Quote Originally Posted by Greg View Post
    the bottom line is use sambaSamAccount and do not use sambaAccount.
    Thanks!
    Though I've never specifically add 'sambaAccount' myself. When configuring samba integration in 4.5.5 I added 'sambaSamAccount'. Also,there are several posts in this topic
    [SOLVED] Unable to add a new account. that mentioned the existence of both 'sambaAccount' and 'sambaSamAccount' after upgrade to 5.0.2.
    I upgraded directly from "Samba-inegrated" 4.5.5 to 5.0.2. Then removed the old versions of extensions and installed new ones. Could it be that upgrade routine somehow adds 'sambaAccount' that later conflicts with 'sambaSamAccount'?

  10. #20
    Greg is offline Zimbra Employee
    Join Date
    Sep 2005
    Location
    Tucson - San Francisco - Moscow
    Posts
    127
    Rep Power
    9

    Default

    Quote Originally Posted by montyZdog View Post
    Thanks!
    Could it be that upgrade routine somehow adds 'sambaAccount' that later conflicts with 'sambaSamAccount'?
    Hm.. I am not aware of any upgrade scripts that would add sambaAccount to zimbraAccountExtraObjectClass
    Bugzilla - Wiki - Downloads - Before posting... Search!
    P.S.: don't forget to vote on this bug
    add Samba LDAP entries to Exchange Migration Tool

Page 2 of 3 FirstFirst 123 LastLast

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. Replies: 9
    Last Post: 03-01-2008, 08:21 PM
  2. 3 testing: LDAP: 389 Failed when restore zimbra
    By victorLeong in forum Administrators
    Replies: 15
    Last Post: 05-24-2007, 06:45 AM
  3. Unable to start tomcat
    By chanck in forum Administrators
    Replies: 11
    Last Post: 06-11-2006, 12:58 AM
  4. Seeming variety of problems on suse-9.1
    By Crexis in forum Installation
    Replies: 52
    Last Post: 03-04-2006, 12:19 AM
  5. Monitoring : Data not yet avalaible
    By s3nz3x in forum Installation
    Replies: 7
    Last Post: 11-30-2005, 07:18 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •