Dns problem Event id 13525 / Source Ntfrs
Kartboy
Event Source: NtFrs
Event Category: None
Event ID: 13525
Date: 27/01/2003
Time: 15:05:57
User: N/A
Computer: SRVVANGOGH
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".
The File Replication Service will try using the name "SRVDELVAUX" until the
computer's DNS name appears.
I tried to find out somewhere what this problem means or to have a solution
but???? Help :-p
Ace Fekay [MVP]
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. Here's a series of steps that Tim Hines, MCSE,MVP
put together that I made a few additions to that you can run through to make
sure everything is clean:
=================================
Steps for fixing the problem when DCPROMO does not find the domain, can't
join machines, GPOs don't work, Replication fails, NTFRS errors, can't find
domain controllers, etc.
- Compiled by Tim Hines, MCSE [MVP] with additions by Ace Fekay [MVP]
=================================
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. (you can use
forwardwers for external resolution see this for complete steps on how to:
http://support.microsoft.com/search/preview.aspx?scid=kb;en-us;Q300202)
2. Open the DNS MMC, double click forwarders so that you can see the zone
for your domain. If the zone is missing, see this on how to create the FLZ
(Forward Lookup Zone) and a Reverse Zone too, if you want one (good for
Nslookup, etc):
http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B308201
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. You should have 4 subfolders
(_MSDCS, _SITES, _TCP, _UDP) and a few records.
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
(Restarting netlogon wil force the service to
register its SRV records with the DNS zone thus creating the missing
subfolders. The records that will be registered
are in winnt\system32\config\netlogon.dns).
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:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;254680
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.
Look for the "Primary DNS Suffix entry. It should look like this:
Host Name . . . . . . . . . . . . : computername
Primary DNS Suffix . . . . . . . : domain.com
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : domain.com
If the Primary DNS Name name is missing or not the same, this is a condition
called "disjointed namespace". Netlogon uses this name to find the zone name
in DNS to register into, as long as updates are enabled and it's spelled
correctly.
If it's incorrect, check the bottom of this article:
Troubleshooting Common Active Directory Setup Issues in Windows 2000
http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B260371
and post back your findings for other possible fixes.
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 1stdcname.domainname.com to
verify that you can get a reply.
15. type nslookup and hit enter
16. type set type=srv and enter
17. type _ldap._tcp.domainname.com and hit enter
18. you should see something like this if it works.
_ldap._tcp.domain.com SRV service location:
priority = 0
weight = 100
port = 389
svr hostname = computername.domainname.com
computername.domainname.com internet address = 192.168.0.1
computername.domainname.com internet address = 25.65.3.81
19. Try running dcpromo, it should work.
For more info about the domain controller location process see
http://support.microsoft.com/default.aspx?scid=kb;EN-US;q247811
=================================
--
Ace
Please direct all replies to the newsgroup so all can benefit.
Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
--
"Kartboy" <kar...@hotmail.com> wrote in message
news:NccZ9.11655$Jd....@afrodite.telenet-ops.be...