Dns Error 4510
Microsoft Tech Companion App Microsoft Technical Communities Microsoft Virtual Academy Script Center Server and Tools Blogs TechNet Blogs TechNet Flash Newsletter TechNet Gallery TechNet Library TechNet Magazine TechNet Subscriptions TechNet Video TechNet Wiki Windows Sysinternals Virtual Labs Solutions Networking Cloud and Datacenter Security Virtualization Downloads Updates Service Packs Security Bulletins Windows Update Trials Windows Server 2012 R2 System Center 2012 R2 Microsoft SQL Server 2014 SP1 Windows 8.1 Enterprise See all trials » Related Sites Microsoft Download Center TechNet Evaluation Center Drivers Windows Sysinternals TechNet Gallery Training Training Expert-led, virtual classes Training Catalog Class Locator Microsoft Virtual Academy Free Windows Server 2012 courses Free Windows 8 courses SQL Server training Microsoft Official Courses On-Demand Certifications Certification overview MCSA: Windows 10 Windows Server Certification (MCSE) Private Cloud Certification (MCSE) SQL Server Certification (MCSE) Other resources TechNet Events Second shot for certification Born To Learn blog Find technical communities in your area Support Support options For business For developers For IT professionals For technical support Support offerings More support Microsoft Premier Online TechNet Forums MSDN Forums Security Bulletins & Advisories Not an IT pro? Microsoft Customer Support Microsoft Community Forums United States (English) Sign in Home Windows Server 2012 R2 Windows Server 2008 R2 Library Forums We’re sorry. The content you requested has been removed. You’ll be auto redirected in 1 second. DNS Infrastructure DNS Server DNS Server Active Directory Integration DNS Server Active Directory Integration Event ID 4510 Event ID 4510 Event ID 4510 Event ID 4000 Event ID 4001 Event ID 4002 Event ID 4003 Event ID 4004 Event ID 4006 Event ID 4007 Event ID 4010 Event ID 4011 Event ID 4012 Event ID 4013 Event ID 4014 Event ID 4015 Event ID 4016 Event ID 4017 Event ID 4018 Event ID 4019 Event ID 4400 Event ID 4510 Event ID 4511 Event ID 4512 Event ID 4513 Event ID 4514 Event ID 4515 Event ID 4520 Event ID 4521 Event ID 4522 Event ID 4523 Event ID 4524 TOC Collapse the table of con
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > The DNS server was unable to connect to the domain naming FSMO Want to Advertise Here? Solved The DNS server was unable to connect to the domain naming FSMO Posted on 2004-06-14 Windows Server 2003 1 Verified Solution 9 Comments 5,432 Views Last Modified: 2007-12-19 Right Experts, here is one https://technet.microsoft.com/en-us/library/cc735754(v=ws.10).aspx for you; New Windows 2003 DC in a previously Win 2000 domain with the following error in DNS Event ID :4510 source DNS The DNS server was unable to connect to the domain naming FSMO "". No modifications to Directory Partitions are possible until the FSMO server is available for LDAP connections. The event data contains the error code. Using NTDSUTIL we have forced the roles on to the Win 2K3 server and still https://www.experts-exchange.com/questions/21024459/The-DNS-server-was-unable-to-connect-to-the-domain-naming-FSMO.html having the same result. Any help would be aprreciated. 0 Question by:ColinRoyds Facebook Twitter LinkedIn Google LVL 104 Best Solution bySembee Is this domain still in mixed mode? Any Windows 2000 DCs still in use? Any DCs not removed properly? Simon. Go to Solution 9 Comments LVL 104 Overall: Level 104 Windows Server 2003 30 Message Accepted Solution by:Sembee2004-06-14 Is this domain still in mixed mode? Any Windows 2000 DCs still in use? Any DCs not removed properly? Simon. 0 LVL 12 Overall: Level 12 Windows Server 2003 6 Message Author Comment by:ColinRoyds2004-06-14 Hi Simon I think the domain is still in mixed mode, but need to check, will be going onsite in a min or two, and yes again the client removed a 2K DC but never took it off the domain before, flattening the server and rebuilding it.(dcpromo was run) Bizarre thing is I removed the AD off the 2003 box, as well as DNS and WINS, re-installed ADS and everything worked fine. However when I put DNS back on everything stopped working correctly, even the time service was no able to contact the 2000 DC stating no authentication protocol available. I am wondering if there is some sort of IPSEC or similar policy being inforced for DC to DC traffic which is causing this
Analyzer Sample report Advanced filtering Direct links to www.eventid.net Email notifications Scheduled reporting Free for subscribers EventReader Event Viewer Sample report http://www.eventid.net/display-eventid-4510-source-DNS-eventno-3954-phase-1.htm Custom views/filters Servers list, organized in groups Integration with EventID.Net Consolidated view for all logs Free for subscribers Event ID: 4510 Source: DNS Source: DNS Type: Warning Description:The DNS server was unable to connect to the domain naming FSMO