W32tm

[Marko]

Hi people,
I have two DCs running AD. I have given in my script a
command that says net time \\servername /set /yes.
However, in the event viewer logs I keep getting a warning
message saying;
Event Type: Warning
Event Source: w32time
Event Category: None
Event ID: 64
Date: 7/13/2003
Time: 10:58:01 AM
User: N/A
Computer: RAZDC2
Description:
Because of repeated network problems, the time service has
not been able to find a domain controller to synchronize
with for a long time. To reduce network traffic, the time
service will wait 960 minutes before trying again. No
synchronization will take place during this interval, even
if network connectivity is restored. Accumulated time
errors may cause certain network operations to fail. To
tell the time service that network connectivity has been
restored and that it should resynchronize,
execute "w32tm /s" from the command line.
After I execute "w32tm /s" command I get the following
message in command prompt;
"RPC to local server returned 0x0".


After executing the command, I took a lokk at event viewer
logs, only to find the following message;

Event Type: Warning
Event Source: w32time
Event Category: None
Event ID: 54
Date: 7/13/2003
Time: 2:08:22 PM
User: N/A
Computer: RAZDC2
Description:
The Windows Time Service was not able to find a Domain
Controller. A time and date update was not possible.
Data:
0000: e5 03 00 00 å...
I find it real hard to believe that my server fails to
realize it is also a dc running ad. Can anyone give
suggestions.

Thanks in advance.
Marko

 

[Marina Roos]

On the workstations type the following just once:
net stop w32time
w32tm -once
net start w32time

Marina

"Marko" <[email protected]> schreef in bericht
Hi people,
I have two DCs running AD. I have given in my script a
command that says net time \\servername /set /yes.
However, in the event viewer logs I keep getting a warning
message saying;
Event Type: Warning
Event Source: w32time
Event Category: None
Event ID: 64
Date: 7/13/2003
Time: 10:58:01 AM
User: N/A
Computer: RAZDC2
Description:
Because of repeated network problems, the time service has
not been able to find a domain controller to synchronize
with for a long time. To reduce network traffic, the time
service will wait 960 minutes before trying again. No
synchronization will take place during this interval, even
if network connectivity is restored. Accumulated time
errors may cause certain network operations to fail. To
tell the time service that network connectivity has been
restored and that it should resynchronize,
execute "w32tm /s" from the command line.
After I execute "w32tm /s" command I get the following
message in command prompt;
"RPC to local server returned 0x0".


After executing the command, I took a lokk at event viewer
logs, only to find the following message;

Event Type: Warning
Event Source: w32time
Event Category: None
Event ID: 54
Date: 7/13/2003
Time: 2:08:22 PM
User: N/A
Computer: RAZDC2
Description:
The Windows Time Service was not able to find a Domain
Controller. A time and date update was not possible.
Data:
0000: e5 03 00 00 å...
I find it real hard to believe that my server fails to
realize it is also a dc running ad. Can anyone give
suggestions.

Thanks in advance.
Marko

 

[bloater]

The best thing to do is nothing. This error should really just be a warning if you are using the local machines hardware clock for a time source, but it shows up as an error.

It is normal to syncronise from a time source on the internet, but sometimes you just can't do that. There is apparently a registry value to shut this warning up, but I couldn't get it to work, and I can't remember what it is.

Do *not* stop you clients from synchronising regularly. Apparently kerberos authentication can break if the machines' times drift apart. Just put up with that warning and error.

 

[ATISysAdmin]

I am having the same issue. I have 2 domain controllers and neither one of them will keep accurate time. I have configured SNTP servers for the servers to sync to but I can not get them to sync. As a result all of my workstations in the domain have the same incorrect time as the domain controller. My users constantly complain that their computer times are 4 minutes slower than their cell phones.


I have checked everything Microsoft tutorial I can think of and I am not able to find any solution.