Home > Event Id > W32time 17 Error

W32time 17 Error


By creating an account, you're agreeing to our Terms of Use, Privacy Policy and to receive emails from Spiceworks. In Start Search, type Command Prompt. In addition to the troubleshooting suggestions “Meinolf Weber” provided, I also would like to suggest you check apply the following hotfix: Name resolution may fail on a Windows Server 2003 Email Reset Password Cancel Need to recover your Spiceworks IT Desktop password? click site

Comments: Conan This is what worked for me: Open Registry Editor (regedit.exe) and configure the following registry entries: HKLM\SYSTEM\CurrentControlSet\Services\W32Time\Parameters\Type This registry entry determines which peers W32Time will accept synchronization from. In Edit Value, type Peers in the Value data box, and then click OK. Resolve issues as necessary on the DNS Server service, and then resynchronize the client with the time source peer. The response may have been tampered with and will be ignored.

Event Id 17 Whea-logger

The default server is, but you can use any NTP server you like.THanks you for your reply.My configured default used server. This is located under Administrative Templates -> Network -> Network Connections -> Windows Firewall -> Domain Profile -> Windows Firewall -> Define Port Exceptions. In the right pane, right-click NtpServer, and then click Modify. The system tries to resolve the name of the time server but it fails.

Yes No Additional feedback? 1500 characters remaining Submit Skip this Thank you! See MSW2KDB and "How to fix time synchronization errors" for additional information on this problem. The Windows Time service (W32time) synchronizes time between computers within the hierarchy, with the most accurate reference clocks at the top. Time Provider Ntpclient No Valid Response I use "" because it's a little faster than the US ones.

No attempt to contact a source will be made for 14 minutes. Make an exception for UDP port 123.

0 Habanero OP Muhammad Bilal May 5, 2010 at 3:53 UTC Yasaf what you suggest??? 0 Habanero OP Muhammad Bilal May 5, 2010 at read the full info here NtpClient will try the DNS lookup again in 60 minutes.

Connect with top rated Experts 17 Experts available now in Live! Event Id 17 Bthusb can you copy the solutions from expert exchange?? 0 Cayenne OP Tomer Nagar May 5, 2010 at 3:56 UTC M. At the top of the Start menu, right-click Command Prompt, and then click Run as administrator. The Last Successful Sync Time line of the output displays the date and time that you ran the W32TM /resync command in the previous step.

Event Id 17 A Corrected Hardware Error Has Occurred

This message will not be logged again until a successful lookup of this manually configured peer occurs. see this NtpClient will try the DNS lookup again in 30 minutes. Event Id 17 Whea-logger Or sign in with one of these services Sign in with Facebook Sign in with Twitter Sign Up All Content All Content This Topic This Forum Advanced Search Facebook Twitter Google Time Provider Ntpclient An Error Occurred During Dns Lookup You may get a better answer to your question by starting a new discussion.

because it is occuring every 15 minutes in event viewer. get redirected here This command displays the status of the Windows Time service synchornization. In Start Search, type Command Prompt. The error was: No such service is known. Windows Event Id 17

Get 1:1 Help Now Advertise Here Enjoyed your answer? About Advertising Privacy Terms Help Sitemap × Join millions of IT pros like you Log in to Spiceworks Reset community password Agree to Terms of Service Connect with Or Sign up Login here! navigate to this website Note Peers is a placeholder for a space-delimited list of peers from which your computer obtains time stamps.

This message will not be logged again until a successful lookup of this manually configured peer occurs. Event Id 17 Rbac This peer will be discarded as a time source and NtpClient will attempt to discover a new peer with this DNS name. The error was: No such service is known.

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.

Verify To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority. Sign In   Sign In Remember me Not recommended on shared computers Sign in anonymously Sign In Forgot your password? This occurs on reboot, and then suceeds on the 15 min retry, looking at the logs it looks like the the NTP service attempts to resolve the DNS name to IP Event Id 17 Windows 10 Join & Ask a Question Need Help in Real-Time?

If you do not append ,0x1 to the end of each DNS name, the changes will not take effect. NtpClient will try the DNS lookup again in 480 minutes. Recommend Us Quick Tip Connect to EventID.Net directly from the Microsoft Event Viewer!Instructions Customer services Contact usSupportTerms of Use Help & FAQ Sales FAQEventID.Net FAQ Advertise with us Articles Managing logsRecommended By creating an account, you're agreeing to our Terms of Use and our Privacy Policy Not a member?