Let me start off by saying i have been having this issue for the last 3 days been trying to add a 2012 server to upgrade are ageing 2003 r2 server. right now its not going so well.
here what i got so far:
when we add the 2012 server to AD and try to make it the master AD we get dns errors and AD replication errors left and right. one of the biggest errors are the dns 4015 error witch i have seen around here and seems like a lot of other people are having issue there as well.
error list i am getting
4015-
Log Name: DNS Server
Source: Microsoft-Windows-DNS-Server-Service
Date: 12/3/2013 8:50:18 AM
Event ID: 4015
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: singh2012.singh.net
Description:
The DNS server has encountered a critical error from the Active Directory. Check that the Active Directory is functioning properly. The extended error debug information (which may be empty) is "". The event data contains the error.
Event Xml:
1925 -
Log Name: Directory Service
Source: Microsoft-Windows-ActiveDirectory_DomainService
Date: 12/3/2013 8:48:41 AM
Event ID: 1925
Task Category: Knowledge Consistency Checker
Level: Warning
Keywords: Classic
User: ANONYMOUS LOGON
Computer: singh2012.singh.net
Description:
The attempt to establish a replication link for the following writable directory partition failed.
Directory partition:
DC=DomainDnsZones,DC=singh,DC=net
Source directory service:
CN=NTDS Settings,CN=SINGHSERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=singh,DC=net
Source directory service address:
6116a0d0-fb84-411d-8950-4df48e894ab9._msdcs.singh.net
Intersite transport (if any):
This directory service will be unable to replicate with the source directory service until this problem is corrected.
User Action
Verify if the source directory service is accessible or network connectivity is available.
Additional Data
Error value:
8524 The DSA operation is unable to proceed because of a DNS lookup failure.
Event Xml:
DC=DomainDnsZones,DC=singh,DC=net
6116a0d0-fb84-411d-8950-4df48e894ab9._msdcs.singh.net
The DSA operation is unable to proceed because of a DNS lookup failure.
CN=NTDS Settings,CN=SINGHSERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=singh,DC=net
8524
1307 -
Log Name: Directory Service
Source: Microsoft-Windows-ActiveDirectory_DomainService
Date: 12/3/2013 8:48:29 AM
Event ID: 1307
Task Category: Knowledge Consistency Checker
Level: Warning
Keywords: Classic
User: ANONYMOUS LOGON
Computer: singh2012.singh.net
Description:
The Knowledge Consistency Checker (KCC) has detected that attempts to establish a replication link with the following directory service has consistently failed.
Attempts:
18
Directory service:
CN=NTDS Settings,CN=WSUS2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=singh,DC=net
Period of time (minutes):
273
The Connection object for this directory service will be ignored, and a new temporary connection will be established to ensure that replication continues. Once replication with this directory service resumes, the temporary connection will be removed.
Additional Data
Error value:
8524 The DSA operation is unable to proceed because of a DNS lookup failure.
Event Xml:
18
CN=NTDS Settings,CN=WSUS2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=singh,DC=net
273
The DSA operation is unable to proceed because of a DNS lookup failure.
8524
1202 -
Log Name: DFS Replication
Source: DFSR
Date: 11/27/2013 9:03:20 AM
Event ID: 1202
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: singh2012.singh.net
Description:
The DFS Replication service failed to contact domain controller to access configuration information. Replication is stopped. The service will try again during the next configuration polling cycle, which will occur in 60 minutes. This event can be caused by TCP/IP connectivity, firewall, Active Directory Domain Services, or DNS issues.
Additional Information:
Error: 160 (One or more arguments are not correct.)
Event Xml:
60
160
One or more arguments are not correct.
i have been looking in to the DNS problems with this and that what seem to be the issue from what i see in the log and looking over them is some sort of pointer issue with the DNS server/ servers. but i don't see any issues with DNS when i look over the DNS records or that i missing something that i am probably not seeing. right now the 2003 is our only work AD right now we had another one but that die on me. so i trying to get the 2012 up and running before i leave the job.
can some shed some light on this issue, will be most helpful