An Error Occurred During Dns Lookup
Contents |
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 time provider ntpclient no valid response Subscriptions TechNet Video TechNet Wiki Windows Sysinternals Virtual Labs Solutions Networking Cloud event id 17 whea-logger and Datacenter Security Virtualization Downloads Updates Service Packs Security Bulletins Windows Update Trials Windows Server 2012 R2 System Center w32time event id 17 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, the computer did not resync because no time data was available 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
Ntp Server
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. Windows Time Service Time Source Peer Manual Time Source Acquisition Manual Time Source Acquisition Event ID 17 Event ID 17 Event ID 17 Event ID 16 Event ID 17 Event ID 47 Event ID 48 Event ID 134 Event ID 135 Event ID 136 Event ID 137 TOC Collapse the table of content Expand the table of content This documentation is archived and is not being maintained. This documentation is archived and is not being maintained. Event ID 17 — Manual Time Source Acquisition Updated: November 25, 2009Applies To: Windows Server 2008 An Active Directory forest has a predetermined time synchronization hierarchy. The Windows Time service (W32time) synchronizes time between computers within the h
Amazon Amazon Web Services ( AWS ) Relational Data Services ( RDS ) Hadoop Informatica Java Linux Microsoft .Net Internet Information Server (IIS) MS SQL Server Reporting Services Transact SQL MS Windows PowerShell Win OS MySQL NetApp Quest HomeMicrosoft - Windows - Time Server - Error - Time Provider NtpClient: An error occurred during DNS lookup of the manually configured peer ‘Server1,0x1'. Microsoft - Windows - Time Server - Error - Time Provider NtpClient: An error occurred during DNS lookup of the manually configured peer ‘Server1,0x1'. July 15, 2012July 15, 2012 Daniel Adeniji Microsoft, MS Windows, Time Provider NtpClient, Time Service Time Provider NtpClient: An error occurred during DNS lookup of https://technet.microsoft.com/en-us/library/cc756513(v=ws.10).aspx the manually configured peer ‘Server1,0x1'. NtpClient will try the DNS lookup again in 480 minutes. The error was: No such service is known. The service cannot be found in the specified name space. (0x8007277C) We have this little Network, but for years now the time has been 20 minutes or so off. Never had time to look at it till now. So Googled for help on how to Setup "Microsoft Windows https://danieladeniji.wordpress.com/2012/07/15/microsoft-windows-time-server-error-time-provider-ntpclient-an-error-occurred-during-dns-lookup-of-the-manually-configured-peer-server10x1/ 2003 Time Server" and the first item on the list is : How to configure an authoritative time server in Windows Server http://support.microsoft.com/kb/816042#method2 So that is probably the most authoritative site \ source. The Web docs two (not 99 ways to leave your lover or 99 Problems) routes to make the necessary correction:- Having Microsoft make the correction Or following the manual instructions (basically making a couple of MS Windows Registry Changes) So that I can be a bit aware of the goings on, chose the manual steps. Went down the line and mostly everything lined up. But, somehow the Time Servers did not look quite good: Branch: HKEY_LOCAL_MACHINE \SYSTEM \CurrentControlSet \Services \w32time \Parameters Name: NtpServer Data: Server1,0x1 But, prior to making more changes, tried restarting the Time Service, but did not get too far. To stop & restart, simple enter: net stop w32time net start w32time So reviewed MS original web doc and went to the list of Time Servers: A list of the Simple Network Time Protocol (SNTP) time servers that are available on the Internet: http://support.microsoft.com/kb/262680 So now I know we have a "tiered" list of Servers. As understand it, there are some rules: stratum one time servers - http://support.ntp.org/bin/view/Servers/StratumOneTimeServers - But, it says not to use those as they ar
The fix for the Event ID: 17 error is pretty obvious but I promised my client that I'll blog it so here it is:Problem:Event ID 12 is being http://terenceluk.blogspot.com/2010/08/event-id-17-error-time-provider.html logged in the System event logs on the domain controller (not all of them, just 1 of them): The error complains about:----------------------------------------------------------------------------Time Provider NtpClient: An error occurred during DNS lookup of the manually configured peer 'dc666;dc999'. NtpClient will try the DNS lookup again in 480 minutes. The error was: No such service is known. The service cannot be found in the specified name space. (0x8007277C) For event id more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. ----------------------------------------------------------------------------Resolution:The reason why this is being logged is because there are invalid entries in the registry of this domain controller that is pointing it to invalid servers for NTP. To correct the problem, simply open up the registry with regedit and navigate to:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters\NtpServer Note that I've already removed the invalid entries in the above screenshot.…then remove the invalid event id 17 entries.One this has been completed, the logs should be error free. Posted by Terence Luk at 11:31 PM Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest Labels: Active Directory, Microsoft No comments: Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Terence Luk Search My Blog Blog Archive ► 2016 (54) ► September (1) ► August (1) ► July (5) ► June (4) ► May (8) ► April (6) ► March (4) ► February (11) ► January (14) ► 2015 (79) ► December (10) ► November (12) ► October (1) ► September (2) ► August (3) ► July (2) ► June (11) ► May (1) ► April (9) ► March (14) ► February (7) ► January (7) ► 2014 (103) ► December (5) ► November (13) ► October (18) ► September (4) ► August (1) ► July (3) ► April (11) ► March (13) ► February (19) ► January (16) ► 2013 (170) ► December (5) ► November (12) ► October (16) ► September (17) ► August (7) ► July (13) ► June (1) ► May (9) ► April (17) ► March (24) ► February (31) ► January (18) ► 2012 (203) ► Decem