After a domain password change, sign-in still reports an incorrect password or the old password appears to work: what should be checked?

Distinguish offline cached sign-in, domain-controller replication delay, existing SMB sessions, Credential Manager, service tasks, and VPN or VDI authentication paths.

1. Conclusion and scope

Prepare the client and server versions, domain membership, DNS and gateway settings, network location, full error text, event timestamps, and recent changes. The reserved example domain corp.example is used throughout; no customer domain, IP address, account, or device identifier is included.

This issue falls under Active Directory and Group Policy. Logs and configuration can often be collected remotely first. Bulk permission changes, switch-path work, production cutovers, and recovery drills should use a controlled implementation window.

2. Symptoms and environment

• Capture the complete error text, event-log timestamp, and failed action rather than relying on a verbal description.
• Record the affected scope, first occurrence, reproducibility, and whether the result changes on another subnet.
• Domain members and computers being joined must use internal DNS; public resolvers do not provide the AD SRV records required for discovery.

3. Troubleshooting sequence

1. Distinguish an offline cached sign-in from failed online domain authentication, and verify whether the endpoint actually contacted a domain controller.
2. Use repadmin to review the replication summary, failing source, error code, site, connection object, and naming context.
3. Windows cannot maintain SMB sessions to the same server with different credentials at the same time. Identify existing sessions before disconnecting and reauthenticating.
4. Review Credential Manager, drive mappings, tasks, services, and scripts for inconsistent account formats; standardise on a verified domain or dedicated service account.
5. If lockouts continue after a password change, investigate offline laptops, mobile devices, old VPN clients, and endpoints that have not restarted or signed out for a long time.
6. When the trust relationship fails, test the secure channel first; confirm local administrator access and user-profile paths before removing and rejoining the computer.

whoami /logonid
nltest /dsgetdc:corp.example
klist
cmdkey /list
net use

4. Safe remediation and rollout

Start with read-only queries, configuration exports, and one-system validation. Once the root cause is confirmed, define the target scope, change window, and rollback method. For multiple computers, use a test OU and a small pilot group, export policy results, and roll out in stages only after side effects are excluded.

• Review Credential Manager, drive mappings, tasks, services, and scripts for inconsistent account formats; standardise on a verified domain or dedicated service account.
• If lockouts continue after a password change, investigate offline laptops, mobile devices, old VPN clients, and endpoints that have not restarted or signed out for a long time.
• When the trust relationship fails, test the secure channel first; confirm local administrator access and user-profile paths before removing and rejoining the computer.

5. Validation, rollback and common mistakes

Do not stop when the service works once. Revalidate with the user workflow, logs, a restart or fresh sign-in, another network location where relevant, and the next policy or backup cycle.

Validation and rollback checks

• Change one variable at a time and export the current configuration before making changes.
• Verify consistent time zones and time sources across clients, domain controllers, and hypervisors to prevent Kerberos failures.
• Confirm AD and SYSVOL replication between domain controllers and verify that the contacted controller has the expected policy version.

Common mistakes to avoid

• Using public DNS or permanent hosts-file entries for domain controllers.
• Removing a computer from the domain before confirming local administrator access.
• Linking a new GPO to the entire domain without a pilot group.