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.
This host <server name> can not be ACS on any of the subnets as this host has not been added to the ACS server lists in the Directory. Add this server to the list of valid servers for ACS via QoS ACS management console.
|English: Request a translation of the event description in plain English.|
In my case, a zone in my secondary DNS server was configured to be a Primary. To fix it, open up DNS, right click on each zone, choose property and double check the type. I changed it to "Secondary", put in the IP of the Primary and the problem was solved.
From a newsgroup post: "In my case, the problem was caused by a bad NIC (the connection was failing intermittently) which kept the ISA server from finding domain controller".
If the suggestion from error description doesn't help, the error may occur because ACS/RSVP Service (Resource Reservation Protocol (RSVP) and Quality of Service (QoS) Admission Control (ACS)) is not working properly. See "Troubleshooting QoS RSVP" link below.
From a newsgroup post: " The error can appear if DNS server is not properly configured. Run a netdiag /v and dcdiag /v to see what the errors are. To configure DNS properly see Microsoft article ME300202."
|Private comment: Subscribers only. See example of private comment|
|Links: Troubleshooting QoS RSVP, ME300202|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated