| Event Id | 13525 |
| Source | NtFrs |
| Description | The File Replication Service cannot find the DNS name for the computer SRVDELVAUX because the "dNSHostName" attribute could not be read from the distinguished name "cn=srvdelvaux,ou=domain controllers,dc=brussels,dc=delen,dc=be". |
| Event Information | "This information from some newsgroups may help you: ------------------------------------------------------------------------------ RPC errors and such, includig NTFRS errors are usually due to a DNS misonfig 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. 1. Verify that the existing domain controller is pointing to a Windows 2000 DNS server. Do not point it to any external ISP DNS servers. 2. Open the DNS MMC, double click forwarders so that you can see the zone for your domain. 3. Right click on this zone and select properties. Verify that your zone is set to allow dynamic updates, if not change it so that it does. 4. Double click your zone to expand it. 5. If the zones do not exist you should open a command prompt. 6. Type IPconfig /registerdns and enter. 7. Type net stop netlogon. 8. Type in a cmd prompt: net start netlogon. 9. After restarting netlogon go back into your DNS zone and verify that you have the subfolders that I mentioned before. 10. If the folders are not there you may want to try running: netdiag.exe /fix from the support tools. Or try restarting netlogon again. 11. If these SRV folders still do not register, check to make sure that File and Printer Sharing is Enabled on the Interface that is connected to the AD network. 12. If these SRV folders still do not register, check the Primary DNS Suffix to make sure that it exists and is the same exact name as your domain name should be. That can be checked by typing in a cmd prompt: ipconfig /all. If the Primary DNS Suffix is correct, continue 13. On the DC that you are trying to promote verify that it is pointing to the Windows 2000 DNS server that we have been working on for DNS. 14. Go to a command prompt and type nslookup 1stdcnam |
| Reference Links |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.