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.
Process <process name> (PID=<process id>). DSAccess is unable to connect to any domain controller in domain <name> althoughDNS was successfully queried for the service location (SRV) resource record used to locate a domain controller for that domain.
The query was for the SRV record for <name>
The following domain controllers were identified by the query: <distinguished name>
Common causes of this error include:
- Host (A) records that map the name of the domain controller to its IP addresses are missing or contain incorrect addresses.
- Domain controllers registered in DNS are not connected to the network or are not running.
For information about correcting this problem, <text><text>.
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
What are the DNS zone files and resource records?
As per Microsoft: "This event occurs if Diagnostics Logging on the Topology category of DSAccess is set to Minimum for the server. This event means that the domain controllers from the specified domain will not be used by DSAccess. As long as there is sufficient capacity in suitable domain controllers in other domains, it will not cause mail flow interruption. However, it is recommended that this event be investigated and fixed as soon as possible. If the event contains the name of the local domain, topology discovery cannot be completed, and this will cause mail flow interruption". See MSEX2K3DB for more details.
|Private comment: Subscribers only. See example of private comment|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated