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.
The File Replication Service cannot find the DNS name for the computer <computer> because the "dNSHostName" attribute could not be read from the distinguished name "cn=srvdelvaux,ou=domain controllers,dc=brussels,dc=delen,dc=be". The File Replication Service will try using the name <computer name> until the computer's DNS name appears.
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
What is the role of a DNS server?
What is the role of File Replication Service?
From a newsgroup post: "RPC errors and such, including NTFRS errors are usually due to a DNS miss configuration on the client part (the DC would be a client too). AD stores info such as DC locations and service locations (like LDAP, Kerberos, etc) that it needs to know where stuff is when it attempts domain specific communication between other DCs and/or clients". See the link to Google Thread below for a few steps to guide you in solving the problem.
|Private comment: Subscribers only. See example of private comment|
|Links: Google Thread|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated