An anonymous reader writes: It appears the widely-used time.windows.com Network Time Protocol server isn't working correctly. The host name is redirecting to unsynchronized Akamai NTP servers which are off by more than 100 seconds. This issue leaves millions of Windows XP and 2003 machines that still have the default configuration without a good source of network time. While most clients won't notice, there are certainly some important applications (such as kerberos authentication) that rely on accurate client time. This mis-configuration has been in place for at least several hours.
A bug report was submitted via Microsoft's website, but no response has been received in over 6 hours. This has apparently happened at least once before.