Page 2 of 2 FirstFirst 12
Results 11 to 15 of 15

Thread: Not all GAL LDAP Mapping Attributes synchronized

  1. #11
    ChaSer is offline Loyal Member
    Join Date
    Oct 2009
    Location
    Ukraine
    Posts
    79
    Rep Power
    5

    Default

    Quote Originally Posted by rdronov View Post
    ...
    zimbraGalAutoCompleteLdapFilter: adAutoComplete
    ...
    zimbraGalLdapFilter: ad
    ...
    There is no Exchange server in my Active Directory domain.
    But I change this two constants so its work without Exchange and has same bug - some LDAP fields not synced.
    zimbraGalLdapFilterDef ad|(displayName=*%s*)(cn=*%s*)(sn=*%s*)(givenName=*% s*)(mail=*%s*))
    zimbraGalLdapFilterDef adAutoComplete|(displayName=%s*)(cn=%s*)(sn=%s*)(givenName=%s*)( mail=%s*))

    I use tcpdump and see that Zimbra request "title" and "company" field from AD server.
    But there is no this fields in reply from AD server.
    Maybe incorrect request format from Zimbra ?

  2. #12
    rdronov is offline Active Member
    Join Date
    Jan 2009
    Posts
    40
    Rep Power
    6

    Default

    Hi ChaSer,

    I think that Exchange extends AD schema and adds some mail-related attributes to AD. Zimbra just search for them. You could use Exchange distributive to extend schema without server installation. Maybe, it help to resolv your issue.

    Regards,
    Roman

  3. #13
    dsent is offline Junior Member
    Join Date
    Mar 2010
    Posts
    7
    Rep Power
    5

    Default

    I have the same problem with Zimbra 6.0.5 on SLES 11 64-bit synchronizing with AD on Windows 2008 Server R2.
    Many fields are not synchronised - e.g. mobile, department.

  4. #14
    ChaSer is offline Loyal Member
    Join Date
    Oct 2009
    Location
    Ukraine
    Posts
    79
    Rep Power
    5

    Default

    Same bug in 6.0.6 version and still no reply on bugzilla
    Almost four months...
    Third part of the year...

  5. #15
    ChaSer is offline Loyal Member
    Join Date
    Oct 2009
    Location
    Ukraine
    Posts
    79
    Rep Power
    5

    Default

    FYI

    The thing that is necessary to specify port 389 instead of 3268 for Active Directory LDAP connection !!!

    Information from Microsoft:
    * Port 3268. This port is used for queries specifically targeted for the global catalog. LDAP requests sent to port 3268 can be used to search for objects in the entire forest. However, only the attributes marked for replication to the global catalog can be returned. For example, a userís department could not be returned using port 3268 since this attribute is not replicated to the global catalog.
    * Port 389. This port is used for requesting information from the local domain controller. LDAP requests sent to port 389 can be used to search for objects only within the global catalogís home domain. However, the requesting application can obtain all of the attributes for those objects. For example, a request to port 389 could be used to obtain a userís department.

Page 2 of 2 FirstFirst 12

Thread Information

Users Browsing this Thread

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

Similar Threads

  1. LDAP Filter issue and GAL
    By G-Money in forum Administrators
    Replies: 2
    Last Post: 06-24-2010, 12:13 PM
  2. missing LDAP Attributes for GAL
    By reinhard in forum Administrators
    Replies: 5
    Last Post: 11-24-2009, 01:09 PM
  3. Extending external LDAP -> GAL setup in UI
    By ab5602 in forum Developers
    Replies: 1
    Last Post: 12-17-2007, 12:30 PM
  4. External Ldap user attributes
    By jherington in forum Installation
    Replies: 0
    Last Post: 11-20-2007, 12:50 AM
  5. External LDAP GAL help (please)
    By dlochart in forum Administrators
    Replies: 24
    Last Post: 07-09-2007, 05:46 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
  •