w32time errors on domain controller...

[Mark]

Hello,

I am receiving a lot of w32time errors on my domain
controller. I receive each of these 2 errors regularly:

______________________________________________
Event Type: Warning
Event Source: w32time
Event Category: None
Event ID: 54
Date: 12/8/2003
Time: 9:41:09 AM
User: N/A
Computer: PATH2K-SRV1
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 å...


Event Type: Warning
Event Source: w32time
Event Category: None
Event ID: 64
Date: 12/8/2003
Time: 9:41:09 AM
User: N/A
Computer: PATH2K-SRV1
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.
Data:
0000: e5 03 00 00 å...
_____________________________________________

I have found articles about finding a time server and
sync'ing with it using the following command:

net time /setsntp:<time server> /set /yes

Is this my only alternative if I want to get rid of these
errors? I am just wondering why it says it can't find a
domain controller when that computer IS the domain
controller. Is there just a way to tell it that it's the
domain controller and doesn't need to sync with anyone
else?

Any input is appreciated. Thanks.

Mark

 

[Marina Roos]

On the DC, from the commandprompt:

net time /setsntp:time.nist.gov (or any other public timeserver)
net stop w32time
w32tm -once -v
net start w32time

On the W2K/XP-clients from the commandprompt:
net time /setsntp:servername
w32tm -once -v

Marina

"Mark" <[email protected]> schreef in bericht
Hello,

I am receiving a lot of w32time errors on my domain
controller. I receive each of these 2 errors regularly:

______________________________________________
Event Type: Warning
Event Source: w32time
Event Category: None
Event ID: 54
Date: 12/8/2003
Time: 9:41:09 AM
User: N/A
Computer: PATH2K-SRV1
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 å...


Event Type: Warning
Event Source: w32time
Event Category: None
Event ID: 64
Date: 12/8/2003
Time: 9:41:09 AM
User: N/A
Computer: PATH2K-SRV1
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.
Data:
0000: e5 03 00 00 å...
_____________________________________________

I have found articles about finding a time server and
sync'ing with it using the following command:

net time /setsntp:<time server> /set /yes

Is this my only alternative if I want to get rid of these
errors? I am just wondering why it says it can't find a
domain controller when that computer IS the domain
controller. Is there just a way to tell it that it's the
domain controller and doesn't need to sync with anyone
else?

Any input is appreciated. Thanks.

Mark