Windows time Service fails to start

March 5, 2009 at 05:35:30
Specs: Windows XP Pro 64 bit, Quad-intel/32gb

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.

See More: Windows time Service fails to start

Report •

March 5, 2009 at 21:36:49
arkraven, can't tell you why it won't start, but may know a workaround. There's a proggie called "Stay Alive 2000" (don't have the addy. Google?) It's designed to ping an ISP at intervals to feign activity and keep a connection alive, but it also gets the current atomic clock time and resets system clocks. Maybe time via another route will do it?
Ed in Texas.

Report •

March 6, 2009 at 07:07:28
Thanks Ed for the info. I will keep that in mind.

I have found out more on my problem. I have tested the theory of turning off three other domain workstations time service to determine if their time would be off. It appears (so far) that windows time service on a client performs nothing with the XP workstation is joined to a domain. I will leave the service off over the weekend to see the results on Monday.

Report •

Related Solutions

Ask Question