Common Windows Time Service Problems and Solutions (Net Time and W32Tm)

Tool and Error

Root Cause

Solution

Net Time: Could not locate a time server.

•	The manually specified time source might not be in the local workgroup or in the domain, or it might not be announcing itself as a time server. Although you received this message, the time service might still be synchronizing time.
•	The time service might not have been stopped before a configuration change was made.
•	UDP port 123 might be closed on the firewall or router between the client and the server or it is being used by another service.

•	Verify that Windows Time Service is synchronizing time.
•	See “Managing Windows Time Service” in this guide for best practice guidelines for configuring time.
•	The other service using UDP port 123 might be Windows Time Service. Stop and start Windows Time Service to solve the problem.

Net Time: Access denied.

A remote procedure call (RPC) failed to authenticate, usually because a user does not have permission to access the remote computer and run Net Time.

If you know the user name and password of an account that does have access rights, establish credentials to access the remote computer to perform this task.

W32tm: Bind failed.

Two instances of the same service are trying to start by using the same port. The Windows Time Service is already using UDP port 123 (the default port for the time service). Therefore, the W32tm tool is not able to use the port.

When you use the W32tm tool, be sure to stop and start Windows Time Service.