1. Welcome Guest! In order to create a new topic or reply to an existing one, you must register first. It is easy and free. Click here to sign up now!.
    Dismiss Notice

Weird ntp issue

Discussion in 'Windows Home Server' started by blankmonkey, Apr 14, 2009.

  1. blankmonkey

    blankmonkey Guest

    ok, have a weird one.
    have set the GPO to look at our time server, all servers are supposed to
    look at ntp.us.edu
    But I started getting lots of these id:50 errors on all our servers (below).
    Turns out they are all looking at time.windows.com, the default!
    So I checked with rsop.msc and gpresult, and the servers ARE getting and
    applying the GPO.
    Looking online, everything I see says that the registry needs to be modified
    at HKLM\services\w32time. But my adm file is modifying
    HKLM\software\Policies\W32time.

    So I thought my adm file was corrupted and wrong, but when I loaded a bran
    new test domain and looked at the adm files, they also look at
    HKLM\software\Policies\W32time.

    I am so confused, and google is not helping, can anyone help me out?

    ((((((((((((((((((((((((())))))))))))))))))))))))))))
    Event Type: Warning
    Event Source: W32Time
    Event Category: None
    Event ID: 50
    Date: 4/13/2009
    Time: 10:31:25 AM
    User: N/A
    Computer: SERVER
    Description:
    The time service detected a time difference of greater than 128 milliseconds
    for 90 seconds. The time difference might be caused by synchronization with
    low-accuracy time sources or by suboptimal network conditions. The time
    service is no longer synchronized and cannot provide the time to other
    clients or update the system clock. When a valid time stamp is received from
    a time service provider, the time service will correct itself.

    For more information, see Help and Support Center at
    http://go.microsoft.com/fwlink/events.asp.
     
  2. Hello blankmonkey,

    In a domain make your life easy and let the default time settings. The DC
    with the PDCEmulator role is the time source in a domain, all DC's sync with
    that and all member servers and workstations sync with one available DC.
    The PDCEmulator configure to an external time source and and you are done.

    So in your case let the PDCEmulator sync with ntp.us.edu, before that revert
    the GPO setting and then set it to not configured:
    w32tm /config /manualpeerlist:ntp.us.edu /syncfromflags:manual /reliable:yes
    /update

    On the clients run:
    w32tm /config /syncfromflags:domhier /update

    After that run:
    net stop w32time
    net start w32time

    Best regards

    Meinolf Weber
    Disclaimer: This posting is provided "AS IS" with no warranties, and confers
    no rights.
    ** Please do NOT email, only reply to Newsgroups
    ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


    > ok, have a weird one.
    > have set the GPO to look at our time server, all servers are supposed
    > to
    > look at ntp.us.edu
    > But I started getting lots of these id:50 errors on all our servers
    > (below).
    > Turns out they are all looking at time.windows.com, the default!
    > So I checked with rsop.msc and gpresult, and the servers ARE getting
    > and
    > applying the GPO.
    > Looking online, everything I see says that the registry needs to be
    > modified
    > at HKLM\services\w32time. But my adm file is modifying
    > HKLM\software\Policies\W32time.
    > So I thought my adm file was corrupted and wrong, but when I loaded a
    > bran new test domain and looked at the adm files, they also look at
    > HKLM\software\Policies\W32time.
    >
    > I am so confused, and google is not helping, can anyone help me out?
    >
    > ((((((((((((((((((((((((())))))))))))))))))))))))))))
    > Event Type: Warning
    > Event Source: W32Time
    > Event Category: None
    > Event ID: 50
    > Date: 4/13/2009
    > Time: 10:31:25 AM
    > User: N/A
    > Computer: SERVER
    > Description:
    > The time service detected a time difference of greater than 128
    > milliseconds
    > for 90 seconds. The time difference might be caused by
    > synchronization with
    > low-accuracy time sources or by suboptimal network conditions. The
    > time
    > service is no longer synchronized and cannot provide the time to other
    > clients or update the system clock. When a valid time stamp is
    > received from a time service provider, the time service will correct
    > itself.
    >
    > For more information, see Help and Support Center at
    > http://go.microsoft.com/fwlink/events.asp.
    >
     

Share This Page