none
Windows Time Service and NTP issue RRS feed

  • Question

  • I have a couple issues related to Windows time service and maybe someone can help.

    last week I had setup the windows time service to run on a server and offer NTP to the rest of the domain workstations and servers. The server is not a DC. Does it need to be? I would not think so since I had it up and running for a time... no pun intended. however when I rebooter the DC and the server the time server has become unavailable. The reason I ask if it needs to be a DC is that in group policy there is the normal domain policies and the "domain controller policies". Would GP need to be set for the time server under the Domain controller policy? or if it is pointing to itself can it be within the normal domain policies? Could this be whats screwing this up?

    "c:\ net time
    Could not locate a time-Server."

    more help is available by typing NET HLPMSG 3912
    "c:\ NET HLPMSG 3912
    Could not locate a time-server."

    Good thing they offer more help on that one.



    I ensured that the Windows time service has been started on both server and workstations.

    I ensured in GPO editor that the service is being sent out to the work stations. at least it looked as it did before the reboot and things were working.

    a few reboots of each.

    tried multiple time providers, the local server I originally used (server name), time.nist,gov...etc

    I went through a few microsoft articles regaurding NTP such as
    "How to configure an authoritative time server in Windows Server 2003" http://support.microsoft.com/kb/816042
    "Configuring the network time service" http://www.windowsnetworking.com/articles_tutorials/Configuring-Windows-Time-Service.html
    and quite a few more, but unfortunatly I was unable to figure out my issue.

    I tried to ensure all registry entries were applicable per microsoft.

    Before I got the time service up for the domain the DC started  having a problem opening the Windows Time Service. Since the DC is not the Time server and the service was working for the rest of the network I want to say the issue is not related:however, it is possible I am wrong on this and the server is the issue. So I looked into the errors,

    "Could not start the Windows Time Service om Local Computer.
    Error 1079: the account specified for this service is different from the account specified for other services running in the same process."

    error sort of says it you would think, so I go to services.msc, right click windows time service and check Log On it currently says NT Authority\NetworkService. From what I understand that this is correct, but I am getting the error. I am not sure what to do about this issue as of yet from here. but I tried changing the log on to a domain admin account, local service, local system....my great aunt ester.... everything I could think of but no luck. I am also not sure which "account specified for other services running the same process." is. I tried to look at the dependencies but it shows none. I tried to match the other services, I looked at the "logon as" list only local System and Network Service. tried both as stated with no luck.

    I Might just need to Blow away the time service on this thing and rebuild that portion but to be honest I have no Idea where to begin on that one and I bet there is just a click or two needed in the right places to make father time speak to my network again.

    If you know father time personaly please send him over to look at my network, or for that matter if you are at all willing and able to contribute to me solving this issue please help.

    wINDOWS 2003 SERVER,
    Windows XP  workstations

    thank you.
    BleepingTech

    Tuesday, August 11, 2009 9:41 AM

Answers

  • Hi,

    Generally, all Domain clients and server are synchronizing time with PDC. And only PDC could synchronize time with an external time server. If the Time Service on PDC cannot work, all these errors may occur.

    Let’s try to solve the Time Service issue first. Please try the suggestion in article below:

    The Windows Time service may generate event ID 7023 after you upgrade to Windows Server 2003 Service Pack 1
    http://support.microsoft.com/kb/892501

    Could you start the Time Service now?

    Thanks.


    This posting is provided "AS IS" with no warranties, and confers no rights.
    Wednesday, August 12, 2009 7:42 AM
    Moderator
  • Hi,

    How did you configure the client Windows Time Services Settings? Did you configure Group Policy? If not, try to configure the following policy and make sure the policy apply to clients. After that, try to check again.

    Computer Configuration\Administrative Templates\System\Windows Time Service

    Computer Configuration\Administrative Templates\System\Windows Time Service\Time Providers

    Thanks.


    This posting is provided "AS IS" with no warranties, and confers no rights.
    Friday, August 14, 2009 10:59 AM
    Moderator

All replies

  • Hi,

    Generally, all Domain clients and server are synchronizing time with PDC. And only PDC could synchronize time with an external time server. If the Time Service on PDC cannot work, all these errors may occur.

    Let’s try to solve the Time Service issue first. Please try the suggestion in article below:

    The Windows Time service may generate event ID 7023 after you upgrade to Windows Server 2003 Service Pack 1
    http://support.microsoft.com/kb/892501

    Could you start the Time Service now?

    Thanks.


    This posting is provided "AS IS" with no warranties, and confers no rights.
    Wednesday, August 12, 2009 7:42 AM
    Moderator

  • BIG thanks on the Help here!!!

    K I got the time service to start on the PDC. the link you gave me helped out tremendously.

    For me it turned out that the logon service needed to be played around with.

    I am still unsuccessful as to the Domain time.

    The server it self and workstations have the same result with the net time command.

    "c:\ net time
    Could not locate a time-Server."

    more help is available by typing NET HLPMSG 3912

    However in RSOP.msc and Net time /quesrysntp  shows the time server correctly.

    I think I have looked at it too long I am still missing something...

     

    Thursday, August 13, 2009 12:31 PM
  • Hi,

    How did you configure the client Windows Time Services Settings? Did you configure Group Policy? If not, try to configure the following policy and make sure the policy apply to clients. After that, try to check again.

    Computer Configuration\Administrative Templates\System\Windows Time Service

    Computer Configuration\Administrative Templates\System\Windows Time Service\Time Providers

    Thanks.


    This posting is provided "AS IS" with no warranties, and confers no rights.
    Friday, August 14, 2009 10:59 AM
    Moderator
  • Hi,

    you will need to run fix from microsoft site : https://support.microsoft.com/en-us/help/816042/how-to-configure-an-authoritative-time-server-in-windows-server

    MicrosoftEasyFix50395.msi

    run the fixit and type the server for NTP (network time provider)  

    thanks,

    Israel Chemo.


    Monday, July 24, 2017 1:33 PM