1 of 1 people found this helpful
I bet the domain controller on that site has stopped replicating, so the most recent password being used for discovery is different on that local DC.
Check the event log on the site's DC for errors relating to AD health & replication, and do an AD health check.
Also check the clocks on the server/clients are correct.
Well although I agree we could have some problems with AD, I don't think it is a replication error. There are only 2 DCs in the environment. Also like I said this is for only 1 of 6 subnets, so the others would be doing the same thing.
I have changed scopes from 192.168.1.1 - 192.168.1.255 to random things like 192.168.1.20-192.168.1.30.
As soon as the discovery completes it locks the account.