It's not always obvious that a firewall even exists as they generally allow regular web traffic to pass normally.If you have temporarily disabled all firewalls that you know of and continue to have this problem, then it's almost certainly a firewall that you aren't aware of.Net Time is a Simple Network Time Protocol (SNTP) client for Windows 95/98/Me/NT/2000/XP/Vista/7/8/10 and Server 2003/2008/2012/2016.(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 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.There shouldn't normally be a reason to change this as the current version of Net Time will check with multiple servers to ensure that it isn't using an invalid time.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.
Once this time period expires, the tray icon will change to a cross and if it's configured to act as a time server, it will stop responding to requests for the time.
Net Time is syncing, but the time is out by an hour - e.g.
Daylight savings time isn't be honoured correctly: Net Time works internally with UTC (Universal Time) and doesn't have any code for handling daylight savings or time zones.
Also, make sure that the Windows Firewall, and other firewalls, aren't bloicking the incoming connections to Net Time. Offset is the time difference between the local system time and the time returned by the time server. Lag is the amount of time that it took for the request from Net Time to go out to the server and for the response to come back.
Net Time has code to try to compensate for high latency connections, but it won't work well on connections with asymmetric network delays - i.e.
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.