[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 210
  • Last Modified:

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

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
creative555
Asked:
creative555
  • 3
  • 3
  • 2
  • +1
1 Solution
 
creative555Author Commented:
DNSerrro.jpgNTfrsId13516.jpg
0
 
Kamran ArshadIT AssociateCommented:
0
 
arnoldCommented:
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
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
MaheshArchitectCommented:
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
 
MaheshArchitectCommented:
You might be interested in solution provided in below thread

http://www.experts-exchange.com/Software/Server_Software/Active_Directory/Q_28618223.html
0
 
arnoldCommented:
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
 
MaheshArchitectCommented:
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
 
arnoldCommented:
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
 
creative555Author Commented:
THank you so much!
0

Featured Post

The new generation of project management tools

With monday.com’s project management tool, you can see what everyone on your team is working in a single glance. Its intuitive dashboards are customizable, so you can create systems that work for you.

  • 3
  • 3
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now