1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Re: synchornize time - w32tm

Discussion in 'Windows XP' started by VanguardLH, May 18, 2010.

  1. VanguardLH

    VanguardLH Flightless Bird

    keekee wrote:

    > Hello,
    > I issue the following commands, but I don't see the time on my
    > computer is adjusted.
    > Before I issue the commands, I make my computer time inaccurate.
    >
    > C:/>w32tm /config /manualpeerlist:"time.nist.gov,
    > time.windows.com,bigben.cac.washington.edu" /update
    > The command completed successfully.
    >
    > C:/>net stop w32time
    > The Windows Time service is stopping.
    > The Windows Time service was stopped successfully.
    >
    > C:/>net start w32time
    > The Windows Time service is starting.
    > The Windows Time service was started successfully.
    >
    > thanks.


    When Microsoft decides to randomly connect to an NTP server to do a time
    update is something that only Microsoft knows. I've read their articles
    but have yet to see an algorithm that can be deciphered to see exactly
    when a time sync will occur. It could be a week before the next update.
    Did you logoff and logon, or did you just sit inside your same Windows
    session waiting for whenever the time service decides to connect?

    w32tm /resync

    Describe in "w32tm /?". Never used it so I don't know if it works to
    force an immediate resynchronization. You might want to use the Update
    Now button in the Date applet in Control Panel under its Internet Time
    tab. I use Socketwatch (payware) but there are plenty of free "atomic
    clock" sync utilities.

    Also, just because you list multiple NTP servers doesn't mean they get
    use. I, too, added several domains in the registry (I'd have to go
    lookup the key again) but only the currently selected one gets used. To
    see which *one* will get used, use the Date applet in Control Panel,
    Internet Time tab, and notice which *one* is selected. Add more NTP
    servers to the list doesn't mean they all get used. It just gives you a
    list from which you can select. Microsoft's NTP server is quite busy
    since that is the default one used by the vast majority of Windows
    users. As such, you'll probably get an error and no sync which means
    having to wait around for days or a week before a retry (and maybe the
    NTP server is too busy at that time, too).

    I prefer a 3rd party NTP client that can poll many NTP servers (since
    some may not be responsive) and also use the one with the least delay (a
    local NTP server may not have the least hops or lowest network lag
    versus an NTP server a lot farther away). For example, my local
    university's NTP server doesn't respond as fast as an NTP server a state
    away.
     
  2. Jose

    Jose Flightless Bird

    On May 18, 5:06 am, VanguardLH <V...@nguard.LH> wrote:
    > keekee wrote:
    > > Hello,
    > > I issue the following commands, but I don't see the time on my
    > > computer is adjusted.
    > > Before I issue the commands, I make my computer time inaccurate.

    >
    > > C:/>w32tm /config /manualpeerlist:"time.nist.gov,
    > > time.windows.com,bigben.cac.washington.edu" /update
    > > The command completed successfully.

    >
    > > C:/>net stop w32time
    > > The Windows Time service is stopping.
    > > The Windows Time service was stopped successfully.

    >
    > > C:/>net start w32time
    > > The Windows Time service is starting.
    > > The Windows Time service was started successfully.

    >
    > > thanks.

    >
    > When Microsoft decides to randomly connect to an NTP server to do a time
    > update is something that only Microsoft knows.  I've read their articles
    > but have yet to see an algorithm that can be deciphered to see exactly
    > when a time sync will occur.  It could be a week before the next update..
    > Did you logoff and logon, or did you just sit inside your same Windows
    > session waiting for whenever the time service decides to connect?
    >
    > w32tm /resync
    >
    > Describe in "w32tm /?".  Never used it so I don't know if it works to
    > force an immediate resynchronization.  You might want to use the Update
    > Now button in the Date applet in Control Panel under its Internet Time
    > tab.  I use Socketwatch (payware) but there are plenty of free "atomic
    > clock" sync utilities.
    >
    > Also, just because you list multiple NTP servers doesn't mean they get
    > use.  I, too, added several domains in the registry (I'd have to go
    > lookup the key again) but only the currently selected one gets used.  To
    > see which *one* will get used, use the Date applet in Control Panel,
    > Internet Time tab, and notice which *one* is selected.  Add more NTP
    > servers to the list doesn't mean they all get used.  It just gives you a
    > list from which you can select.  Microsoft's NTP server is quite busy
    > since that is the default one used by the vast majority of Windows
    > users.  As such, you'll probably get an error and no sync which means
    > having to wait around for days or a week before a retry (and maybe the
    > NTP server is too busy at that time, too).  
    >
    > I prefer a 3rd party NTP client that can poll many NTP servers (since
    > some may not be responsive) and also use the one with the least delay (a
    > local NTP server may not have the least hops or lowest network lag
    > versus an NTP server a lot farther away).  For example, my local
    > university's NTP server doesn't respond as fast as an NTP server a state
    > away.


    Time sync occurs every 604800 seconds by default which is every 7
    days. It is not some random interval that only Microsoft knows.

    HKLM\System\CurrentControlSet\Services\W32Time\TimeProviders\NtpClient
    \SpecialPollInterval

    You can change it to whatever you want.

    Keekee - what is it you are trying to accomplish or are you just
    experimenting and not seeing the results you expect?
     

Share This Page