Solved

event ID 13516 NTFRS. DNS error 4015 on all new 2012 DCs that e introduced into 2003 environment.

Posted on 2015-02-16
9
176 Views
Last Modified: 2015-02-24
event ID 13516 NTFRS. DNS error 4015 on all new 2012 DCs that were introduced into 2003 environment.

Please help.
Do we need to do any additional migration/configuration steps for NTFRS? Let me know
0
Comment
Question by:creative555
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 3
  • 2
  • +1
9 Comments
 

Author Comment

by:creative555
ID: 40613046
DNSerrro.jpgNTfrsId13516.jpg
0
 
LVL 32

Expert Comment

by:Kamran Arshad
ID: 40613797
0
 
LVL 79

Expert Comment

by:arnold
ID: 40613872
Once you add the fileshare service (add role services to fileserver role) that includes support for windows 2003 file services, this and the other errors should go away.

Windows 2003 uses NTFRS to replicate sysvol data. the 2008 and newer use DFSR to replicate sysvol data.
0
Visualize your virtual and backup environments

Create well-organized and polished visualizations of your virtual and backup environments when planning VMware vSphere, Microsoft Hyper-V or Veeam deployments. It helps you to gain better visibility and valuable business insights.

 
LVL 37

Expert Comment

by:Mahesh
ID: 40614311
I never added support for 2003 file services explicitly for this to work
what is the domain and forest functional level of domain?

Also check if netlogon and sysvol is shared on new DC, I guess not
Also check if file replication service is started in auto mode on 2012 DC

You might try to force NTFRS replication
http://blogs.technet.com/b/justinturner/archive/2007/04/27/quick-tip-force-frs-replication.aspx

Else forcefully demote \ remove the 2012 servers from domain, clear out problem and again add new 2012 DCs
0
 
LVL 37

Expert Comment

by:Mahesh
ID: 40614393
You might be interested in solution provided in below thread

http://www.experts-exchange.com/Software/Server_Software/Active_Directory/Q_28618223.html
0
 
LVL 79

Expert Comment

by:arnold
ID: 40614410
Mahesh, note old DC in the example you posted is SBS 2011 (Server 2008) if I am not mistaken.
The issue the asker has here is the DC they have in this environment is Server 2003.  The sysvol is available seemingly through replication with other Server 2012s.
0
 
LVL 37

Expert Comment

by:Mahesh
ID: 40614923
I doubt if sysvol is available on 2012 DCs because I suspect that FRS service is not running as well

Only author can confirm
0
 
LVL 79

Accepted Solution

by:
arnold earned 500 total points
ID: 40614944
Mahesh, The asker has had various other questions on this topic which is how I have come to understand so much about the situation.

The person has multiple DC including 2012s of which this one was just added.
If this DC has a way to reach any of the other 2012 DCs the replication for sysvol could have occurred while the DNS service periodically throws the errors listed in this and other questions. Yes, the DNS zone could very well be current by the same process.
These errors could be sporatic when this 2012 DC contacts the 2003 DC for replication/etc. at which point these errors are generated, they could be intermittent, but show up daily or hourly.
0
 

Author Closing Comment

by:creative555
ID: 40629026
THank you so much!
0

Featured Post

Office 365 Training for Admins - 7 Day Trial

Learn how to provision tenants, synchronize on-premise Active Directory, implement Single Sign-On, customize Office deployment, and protect your organization with eDiscovery and DLP policies.  Only from Platform Scholar.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

A company’s centralized system that manages user data, security, and distributed resources is often a focus of criminal attention. Active Directory (AD) is no exception. In truth, it’s even more likely to be targeted due to the number of companies …
Always backup Domain, SYSVOL etc.using processes according to Microsoft Best Practices. This is meant as a disaster recovery process for small environments that did not implement backup processes and did not run a secondary domain controller that ne…
This Micro Tutorial hows how you can integrate  Mac OSX to a Windows Active Directory Domain. Apple has made it easy to allow users to bind their macs to a windows domain with relative ease. The following video show how to bind OSX Mavericks to …
Are you ready to implement Active Directory best practices without reading 300+ pages? You're in luck. In this webinar hosted by Skyport Systems, you gain insight into Microsoft's latest comprehensive guide, with tips on the best and easiest way…
Suggested Courses

632 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question