Monitor unlimited number of servers
Filter log events
Create email and web-based reports

Direct access to Microsoft articles
Customized keywords for major search engines
Access to premium content

Event ID: 13525 Source: NtFrs

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.
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.

Windows Event Log Analysis Splunk App

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



Cisco ASA Log Analyzer Splunk App

Obtain enhanced visibility into Cisco ASA firewall logs using the free Firegen for Cisco ASA Splunk App. Take advantage of dashboards built to optimize the threat analysis process.