In the immortal words of Justin Alcorn: > Apparently, the delete now worked - but on the FIRST password, not the > second. > > Sequence: > > Create account with password 'FirstPass' > > perl code (delete then add) fails. > > perl code (add then delete) succeeds for change from > FirstPass->SecondPass, but FirstPass will still bind to AD. > > perl code (delete then add) now changes password SecondPass->ThirdPass, > but only FirstPass is deleted. SecondPass and ThirdPass will now > successfully bind to AD, but not FirstPass. > > Interestingly, only ThirdPass will work for a desktop logon. SecondPass > will NOT work except for an LDAP Bind. > > perl code (add then delete) ThirdPass->FourthPass results: > SecondPass is now gone. ThirdPass and FourthPass will bind to AD. > > So the delete is deleting the first password in the stack, as long as > there is actually a password after the delete. > > Any ideas?
Are you sure you're not seeing the effects of replication latency? %% Christopher A. Bongaarts %% [EMAIL PROTECTED] %% %% Internet Services %% http://umn.edu/~cab %% %% University of Minnesota %% +1 (612) 625-1809 %%
