Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net. The EventId.Net for Splunk Add-on assumes that Splunk is collecting information from Windows servers and workstation via the Splunk Universal Forwarder.
Changing machine account password for account <computer name>$ failed with the following error: <error message>.
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
What is the use of the machine account password?
What is the role of the Netlogon share?
- Error message: "There are currently no logon servers available to service the logon request" - See ME941761 for a hotfix applicable to Microsoft Windows Server 2003.
- Error message: "The security database on the server does not have a computer account for this workstation trust relationship" - I received this error on a number of servers and Windows XP machines. This problem occurred when I upgraded a NT4 PDC to a 2K server. Somehow, the security records on the PDC and BDC had got out of sync. My solution was to remove the offending PC from the domain, remove its account from both the 2K server (acting as a PDC) and from the BDC. I waited 15 minutes for all the updates to filter through and then rejoined the domain.
See the link to "EventID 3224 from source System" for information on this event.
See the ME247926 and ME259736 articles.
This indicates that the PDC for the domain was not available. Because the BDC was available, the system was able to authenticate, but with no PDC, the password for the account could not be changed. Resolve issues with the PDC or promote the BDC.
In my case, 2 of 3 computers were having problems with this error - were unable to get logged into the domain. I exported the registry key:
from the one working PC into the other 3 and it worked.
Here are the 4 values that were under this Registry entry:
ONLY 1 of the 4 were present. I had to add the other 3. The one present was the 68 value.
Added these, rebooted, and I could log into the domain.
|Private comment: Subscribers only. See example of private comment|
|Links: ME247926, ME259736, ME941761, EventID 3224 from source System|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated