Re: Win 2003 Server W32Time
- From: "Bruce Sanderson" <bsanders@xxxxxxxxxxxxxxxx>
- Date: Sat, 14 Feb 2009 16:17:40 -0800
Perhaps the Windows Time Service is not configured to get time from an operational NTP server.
If the server can send requests over the Internet, decide which public time server you want to use - e.g. time.nist.gov, (see http://tf.nist.gov/service/its.htm) or one closer to you see the list at http://support.ntp.org/bin/view/Servers/StratumTwoTimeServers.
Issue these commands:
w32tm /config /manualpeerlist:time.nist.org /syncfromflags:manual /update
w32tm /resync /rediscover
Instead of time.nist.org, you can use any other server that has NTP service running (e.g. one from http://support.ntp.org/bin/view/Servers/StratumTwoTimeServers).
After you issue the second command above, you should get a System Event Log entry from the Time Service - Event ID 37 saying that time synchronization was successful. Unless the connection to the configured time source is lost, Windows Time will automatically re-sync when it "thinks" it needs to (quote from http://blogs.msdn.com/w32time/default.aspx - "Normally, W32Time will poll (make a time request) on a floating interval, based on the quality of the time samples being returned by the time source.").
--
Bruce Sanderson
http://members.shaw.ca/bsanders
It is perfectly useless to know the right answer to the wrong question.
"Tecknomage" <tecknode@xxxxxxxxxx> wrote in message news:up80p45k92e1aelcb2415msg66dn4ml0uh@xxxxxxxxxx
On Sat, 7 Feb 2009 21:25:06 +0000 (UTC), Meinolf Weber [MVP-DS]
<meiweb(nospam)@gmx.de> wrote:
Hello MageMaster,
See here:
http://support.microsoft.com/kb/328621
Is the server domain member? Run this command to configure automatic domain
time synchronization:
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
Thanks, but our Fileserver is NOT a domain server. We use a
Workgroup.
Using the solution to add Registry W32Time option for 'retry sync
until good, then once a day' (not exact quote). This is from another
post with URL to a MS FAQ on W32Time.
--
> We get a Event ID 36 error each day.
>
> ---
>
> Event Type: Warning
> Event Source: W32Time
> Event Category: None
> Event ID: 36
> Date: 2/6/2009
> Time: 06:07:56
> User: N/A
> Computer: FILESERVER2
> Description:
>
> The time service has not synchronized the system time for 86400
> seconds because none of the time service providers provided a usable
> time stamp.
>
> The time service is no longer synchronized and cannot provide the time
> to other clients or update the system clock.
>
> Monitor the system events displayed in the Event Viewer to make sure
> that a more serious problem does not exist.
>
> ----
>
> We have no problem with a manual time-sync.
>
> I think the problem is it is trying to sync in the same time period we
> are doing scheduled backups.
>
> Is there a way to move the W32Time sync to a different time period in
> a day?
>
======== Tecknomage ========
Computer Systems Specialist
IT Technician
San Diego, CA
.
- References:
- Win 2003 Server W32Time
- From: MageMaster
- Re: Win 2003 Server W32Time
- From: Meinolf Weber [MVP-DS]
- Re: Win 2003 Server W32Time
- From: Tecknomage
- Win 2003 Server W32Time
- Prev by Date: Re: error login admin domain in vista client business
- Next by Date: Re: Why nest global groups in domain local groups?
- Previous by thread: Re: Win 2003 Server W32Time
- Next by thread: So I WANT to break a server...can you help?
- Index(es):
Relevant Pages
|