Password change problem

Question

When trying to change password I get an error message that says configuration information could not be read from the domain controller either because the machine is unavailable or access has been denied. How do I fix this?

Answer 1

Hello,

I guess that you are working remotely and are not connected to the domain controller. So to fix this please make sure you are signed into your company's VPN before trying to change your password again. If you are already in the office or the VPN is fully connected, your machine might have lost its secure trust relationship with the domain due to a stale DNS configuration on your network adapter. You could try restarting your computer while connected to the network to refresh your DNS settings and then connect to the domain again. If it's still failed to change your password after that, give me a comment so we could think of another solution.

Answer 2

This error typically occurs when the password change request is sent to a domain controller that doesn’t yet have the current password or required configuration, or when access to the domain controller is blocked.

Use these steps to fix it:

1. Retry against a local domain controller
   If the password was recently reset on a different (remote) domain controller, wait for Active Directory replication to complete, then try again.
   To avoid replication latency, perform the password reset/change on a domain controller in the same site as the user:
   • Open Active Directory Users and Computers.
   • Right‑click the top node in the left pane and select Connect to Domain Controller.
   • Choose a domain controller in the user’s site.
   • Reset the user’s password and, if needed, select User must change password at next logon.
2. Check for replication delays
   If users in remote sites see this error when changing passwords, verify that:
   • The PDC emulator and other domain controllers are replicating correctly.
   • Site links and replication schedules are configured so that password changes replicate promptly.
3. Have the user log on with the latest password before changing it
   In scenarios where a helpdesk reset the password (for example, from password1 to password2), ensure the user:
   • Logs on using the newly set password (password2).
   • Then changes the password once replication has reached the local domain controller.
4. Try the password change again after replication
   Once replication has completed and the local domain controller knows the current password, retry the password change. The operation should succeed when the domain controller recognizes the “old password” supplied during the change.

---

References:

• User may not be able to change their password if you configure the 'User must change password at next logon' setting
• Users can't sign in to the domain after password changes on a Remote Domain Controller