Ntp not updating system clock

If it can't find a unique secondary server that provides a time which is a close fit to the time returned by the primary server, it will fail with "Inconsistent Responses" The most common causes for this is if multiple servers are configured but point to the same IP address, or you're using the default servers and you are in a region with only 1 actual server in the NTP Pool.Possible solutions are to either remove all but one server address - in which case, the time returned by it will always be used - even if it's invalid, or change your servers - if you're using the NTP Pool servers, then you should point to the servers for a larger geographic area.If Time adjustment greater than: The default setting for this means that the local time will be updated regardless of how much difference there is between the current local time and the time reported by the remote server.

(32 bit and 64 bit operating systems are both supported) If you're looking for a program to keep your system time accurate, you've just found it!If you can run a UDP traceroute to port 123 on one of the time servers that you're using, that should give you an indication of where the firewall is located.Net Time is failing to sync - it reports that it had "Inconsistent responses" If there is a large time difference between the local system and the time returned by the time server, Net Time will automatically check with a secondary server to ensure that the time that it has received is actually valid.You can also manually your time zone information using the free Microsoft tool: Windows Time Zone Editor Alternatively, the Windows Server 2003 Resource Kit Tools reportedly includes a command line tool for advanced users.I have configured Net Time to provide time to other systems, but it's not working: Ensure that the Windows Time Service is disabled along with any other NTP servers that may be running.