> > -----Original Message----- > From: fedora-directory-users-bounces@xxxxxxxxxx [mailto:fedora-directory-users-bounces@xxxxxxxxxx] On Behalf Of Doug Tucker > Sent: Tuesday, September 08, 2009 9:05 AM > To: General discussion list for the 389 Directory server project. > Subject: Re: Pass Sync Doesn't Work > > > > >> would be greatly appreciated. > > > > > > 1 - In windows registry-HKLM-Software-PasswordSync, > > > change the "log level" setting from "0" to "1" > > > > > > 2 - Restart the passsync service > > > > > > 3 - look for passsync.log under C:\Program Files\*Password > > > Synchronization\ > > > > > > > > > --Chandra > > > > Thanks, I'll ask the windows guy to set this. I haven't seen anything > about this, but merely thinking. If the passync service is installed on > the PDC host, if a windows user changes their password, but are > connected to the BDC when they do so, will passync still catch the > change? OK! The logging was a tremendous help to at least seeing where the failure is. When the password change is made on the PDC, passync DOES catch it and replicate to 389. However, if the password change occurs on the BDC, even though we see the change replicated to the PDC, passync is NOT catching it and replicating to 389. Does anyone have any ideas? -- 389 users mailing list 389-users@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-directory-users
