I’m using several Windows XP Pro (64bit) machines joined to a Windows 2003 Enterprise server. Two of the 70 or so clients refuse to start Windows time service for some unknown reason. The response given when attempting to start it, it refers to “net logon” not started. Net Logon is up and running. A restart of the logon service provides the same response when attempting to restart Windows Time Service. The current time on both machines is only off about 10 minutes from the server. I’ve goggled many and tried many different things but nothing was successful.
I was also told that Windows Time Service did not need to be started on the client workstations because these machines where part of the domain/active directory. Any thoughts on this comment, because no where in my research of this problem have I found anything pertaining to the fact it does not need to be running.