Issue with Domain Services Not Starting After DC2 Delayed Startup, Despite DC1 Being Available
We have two Domain Controllers (DC1 and DC2). One day, DC2 started 20 minutes late. On that day when client PC's ran services we encountered the following error message:
"The xyz service failed to start due to the following error: The account name is invalid or does not exist, or the password is invalid for the account name specified."
It's important to note that we use Domain Account credentials to run these services on the client PCs. Interestingly, other functions, such as the Task Scheduler, worked perfectly fine, despite using the same account as the xyz service.
We want to know that, when DC1 was avialable why we got error message like domain controller not avialable and also why we could not start any services.