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.
None of the IP addresses (<IP address>) of this Domain Controller map to the configured site "<site>". While this may be a temporary situation due to IP address changes, it is generally recommended that the IP address of the Domain Controller (accessible to machines in its domain) maps to the Site which it services. If the above list of IP addresses is stable, consider moving this server to a site (or create one if it does not already exist) such that the above IP address maps to the selected site. This may require the creation of a new subnet object (whose range includes the above IP address) which maps to the selected site object.
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
What is the role of the Netlogon share?
I noticed this error when I added a new site and a subnet for the new site on an existing AD with the main domain controllers in the default site. The default site did not have a subnet associated with it. I created another subnet with the default IP range and associated it with the default site.
This warning started to appear with two Domain Controllers in the same site on the same subnet. I create a second site in Sites and services. When I moved the second domain controller to the new site and changed the subnet, I started receiving this warning. Go into the Sites and services applet, and add the local subnet that the remote domain controller is on and ensure that the subnet is mapped to the remote site.
|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