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.
Windows cannot establish a connection to <domain name> with (<error code>).
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
How does a client find an NT domain controller?
How does a client find an AD domain controller?
What is the role of Userenv?
|Our approach: This information is only available to subscribers. An example of Our approach|
Error code 0 = "The operation completed successfully." - This is not an error code in itself so the message is a bit deceiving. Most probably, the result from the function that is establishing the connection is ok but some other error is affecting the operation and that error is not captured in the event.
Error code 1787 = The security database on the server does not have a computer account for this workstation trust relationship. See ME257623 for more details.
Error code 10053 = "An established connection was aborted by the software in your host machine." - no additional info
Error code 0x2747 = An operation on a socket could not be performed because the system lacked sufficient Buffer space or because a queue was full. See ME196271 for details.
Error code 10038 - See the link to Citrix Support Document ID: CTX105618 for details on this problem.
Woodrow Wayne Collins
Error code 1311 = "There are currently no logon servers available to service the logon request".
ME824302 might provide useful in this situation.
We received this issue on a DC after downloading a signed ActiveX application from a browser session. The AD-Integrated Forward Lookup Zone literally "disappeared" from the snap-in, and some users in the domain reported odd resource access issues. Simple solution - Search for newly created files to determine what application was installed, uninstall, and reboot. The server replayed the AD logs are functionality was restored.
You might want to check your trusts between domains. This helped out. I went to Domains and Trusts, Trusted Domains, choose the domain, then select edit, and then checked the actual trust by the "Verify" button. I had a broken trust. It will ask you if you want to re-establish a trust. Say yes. Then go to the other Domain Controller on the other Domain and do the same thing.
|Private comment: Subscribers only. See example of private comment|
|Links: Active Directory Diagnostics, Troubleshooting, and Recovery|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (1) - More links...|
Send comments or solutions
- Notify me when updated