Re: [389-users] Windows PasswordSync 389 to ADS 2003, fail.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Assuming you're using version 1.2.2+, see Rich's previous email a few
days ago.

http://lists.fedoraproject.org/pipermail/389-users/2010-January/010753.html

Essentially there is a bug in 1.2.2, which has been corrected in 1.2.5
rc4.  I've tested 1.2.4RC4 on Centos 5.4 using RC4 to ADS 2003 and the
sync works.


On Tue, 2010-01-12 at 15:51 -0300, Sergio A. Morales wrote:
> Hi.
> 
> I read the list archives and i found several people with this problem:
> Windows Sync works except password sync from 389 to ADS.
> 
> I have:
> * ADS and 389 with SSL, all ok with this.
> * No password complex policy en ADS
> * Password Encryption in 389: CLEAR
> * Windows Password Sync from AD to 389 works.
> * I have cn=Administrator... in my replica agreement.
> 
> Full resync works and all account are created in Windows... But when i
> change password from 389-console, there no change in ADServer, just
> personal info like email or phone are in sync.
> 
> i have this log:
> [12/Jan/2010:15:36:41 -0300] - Calling dirsync search request plugin
> [12/Jan/2010:15:36:41 -0300] - Sending dirsync search request
> [12/Jan/2010:15:36:41 -0300] NSMMReplicationPlugin -
> agmt="cn=Again" (windows:389): Beginning linger on the connection
> [12/Jan/2010:15:36:41 -0300] NSMMReplicationPlugin -
> agmt="cn=Again" (windows:389): State: sending_updates ->
> wait_for_changes
> [12/Jan/2010:15:37:05 -0300] NSMMReplicationPlugin - changelog program -
> _cl5GetDBFile: found DB object ef489a0 for database
> 2695e682-ff9d11de-beb8fde4-dd7504ff_4b4b955b000000010000.db4
> [12/Jan/2010:15:37:05 -0300] NSMMReplicationPlugin - changelog program -
> cl5GetOperationCount: found DB object ef489a0
> [12/Jan/2010:15:37:41 -0300] NSMMReplicationPlugin -
> agmt="cn=Again" (windows:389): Linger timeout has expired on the
> connection
> [12/Jan/2010:15:37:41 -0300] NSMMReplicationPlugin -
> agmt="cn=Again" (windows:389): Disconnected from the consumer
> 
> 
> I reinstall windows and 389 but nothing...
> 
> Someone has been solved this problem before? or Any ideas about how to
> solve it?
> 
> Thank you
> 
> --
> 389 users mailing list
> 389-users@xxxxxxxxxxxxxxxxxxxxxxx
> https://admin.fedoraproject.org/mailman/listinfo/389-users






IMPORTANT: 
This transmission is sent on behalf of Knouse Foods ® for business
purposes.  It is for the intended recipient only.  If you are not the intended
recipient or a person responsible for delivering this transmission to
the intended recipient, you may not disclose, copy or distribute this
transmission or take any action in reliance on it.  If you received this
transmission in error, please notify us immediately by replying to this
Email message, and please dispose of and delete this transmission.
Thank you.
--
389 users mailing list
389-users@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/389-users

[Index of Archives]     [Fedora Directory Users]     [Fedora Directory Devel]     [Fedora Announce]     [Fedora Legacy Announce]     [Kernel]     [Fedora Legacy]     [Share Photos]     [Fedora Desktop]     [PAM]     [Red Hat Watch]     [Red Hat Development]     [Big List of Linux Books]     [Gimp]     [Yosemite News]

  Powered by Linux