Windows time service was not able

To reduce network traffic, the time service will wait minutes before trying again. No synchronization will take place during this interval, even if network connectivity is restored. Accumulated time errors may cause certain network operations to fail. Join our community to see this answer! Unlock 1 Answer and 4 Comments.

Andrew Hancock - VMware vExpert. See if this solution works for you by signing up for a 7 day free trial. At first, you should make sure options of Set time automatically and Set time zone automatically are turned on.

Click Update now to change the Internet time settings. Here if you find that though you have to open the Internet time server — time. Soon Windows 10 will automatically sync your clock with the Internet. At this moment, you are entitled to make your time synchronized. And it is no wonder that time not syncing on Windows 10 can be resolved. There is another problem that when you synchronize the time, an error may appear reminding you that the RPC server is unavailable.

Usually, if the services about the time on Windows 10 is stopped, there is no doubt that you cannot synchronize the time to the Internet server. Therefore, you would better start or restart the Windows Time in Services. Scroll down to find out Windows time and right click it to Start it. As long as you opened the Windows time services on Windows 10, you are able to make the time synchronized as well.

The interdomain trust account is created when a new AD DS domain joins a forest, and the Net Logon service manages the session key. In this way, the domain controller that is configured as reliable in the forest root domain becomes the authenticated time source for all of the domain controllers in both the parent and child domains, and indirectly for all computers located in the domain tree.

The Windows Time service can be configured to work between forests, but it is important to note that this configuration is not secure. For example, an NTP server might be available in a different forest. However, because that computer is in a different forest, there is no Kerberos session key with which to sign and authenticate NTP packets. To obtain accurate time synchronization from a computer in a different forest, the client needs network access to that computer and the time service must be configured to use a specific time source located in the other forest.

If a client is manually configured to access time from an NTP server outside of its own domain hierarchy, the NTP packets sent between the client and the time server are not authenticated, and therefore are not secure.

Even with the implementation of forest trusts, the Windows Time service is not secure across forests. Although the Net Logon secure channel is the authentication mechanism for the Windows Time service, authentication across forests is not supported. Hardware-based clocks such as GPS or radio clocks are often used as highly accurate reference clock devices.

By default, the Windows Time service NTP time provider does not support the direct connection of a hardware device to a computer, although it is possible to create a software-based independent time provider that supports this type of connection. This type of provider, in conjunction with the Windows Time service, can provide a reliable, stable time reference. Hardware devices, such as a cesium clock or a Global Positioning System GPS receiver, provide accurate current time by following a standard to obtain an accurate definition of time.

Cesium clocks are extremely stable and are unaffected by factors such as temperature, pressure, or humidity, but are also very expensive.

A GPS receiver is much less expensive to operate and is also an accurate reference clock. GPS receivers obtain their time from satellites that obtain their time from a cesium clock. Without the use of an independent time provider, Windows time servers can acquire their time by connecting to an external NTP server, which is connected to a hardware device by means of a telephone or the Internet. Organizations such as the United States Naval Observatory provide NTP servers that are connected to extremely reliable reference clocks.

You can configure your AD DS forest to synchronize time from these external hardware devices only if they are also acting as NTP servers on your network. To do so, configure the domain controller functioning as the primary domain controller PDC emulator in your forest root to synchronize with the NTP server provided by the GPS device.

The primary difference between the two is that SNTP does not have the error management and complex filtering systems that NTP provides.

The time service in Windows NT Server 4. For example, if your domain is configured to synchronize time by using the domain hierarchy-based method of synchronization and you want computers in the domain hierarchy to synchronize time with a Windows NT 4. Windows NT 4. Therefore, to ensure accurate time synchronization across your network, it is recommended that you upgrade any Windows NT 4.

The Windows Time service is designed to synchronize the clocks of computers on a network. The network time synchronization process, also called time convergence, occurs throughout a network as each computer accesses time from a more accurate time server. Time convergence involves a process by which an authoritative server provides the current time to client computers in the form of NTP packets. The information provided within a packet indicates whether an adjustment needs to be made to the computer's current clock time so that it is synchronized with the more accurate server.

As part of the time convergence process, domain members attempt to synchronize time with any domain controller located in the same domain. If the computer is a domain controller, it attempts to synchronize with a more authoritative domain controller. Computers running Windows XP Home Edition or computers that are not joined to a domain do not attempt to synchronize with the domain hierarchy, but are configured by default to obtain time from time.

To establish a computer running Windows Server as authoritative, the computer must be configured to be a reliable time source. By default, the first domain controller that is installed on a Windows Server domain is automatically configured to be a reliable time source.

Because it is the authoritative computer for the domain, it must be configured to synchronize with an external time source rather than with the domain hierarchy. Also by default, all other Windows Server domain members are configured to synchronize with the domain hierarchy.

After you have established a Windows Server network, you can configure the Windows Time service to use one of the following options for synchronization:. Synchronization that is based on a domain hierarchy uses the AD DS domain hierarchy to find a reliable source with which to synchronize time.

Based on domain hierarchy, the Windows Time service determines the accuracy of each time server. In a Windows Server forest, the computer that holds the primary domain controller PDC emulator operations master role, located in the forest root domain, holds the position of best time source, unless another reliable time source has been configured.

The following figure illustrates a path of time synchronization between computers in a domain hierarchy. A computer that is configured to be a reliable time source is identified as the root of the time service.

The root of the time service is the authoritative server for the domain and typically is configured to retrieve time from an external NTP server or hardware device. A time server can be configured as a reliable time source to optimize how time is transferred throughout the domain hierarchy. If a domain controller is configured to be a reliable time source, Net Logon service announces that domain controller as a reliable time source when it logs on to the network.

The un-register went fine, but while trying to register again I'm getting below error:. Regards, Dave Patrick Thanks for the prompt reply. There was still a zombie w32tm service running, which I was not able to stop via service. It took a couple of machine reboot before it starts working fine. I still need to monitor for a couple of days if that had resolved automatic time update issue I was facing. Office Office Exchange Server.

Not an IT pro?