w32 time issue

[Mike Brester]

Hello all,

I have recently experienced a time issue on a couple machines in my network.
Randomly I will receive a call from someone saying their time is off. I NTP
configured on my DC. It is pointing to bigben.cac.washington.edu. Looking at
my server I see no W32 time errors or warnings but when I look at the machine
that has the off time I see a w32 warning with an event id 36. I can just go
in and manually set their clock to the correct time and all will be fine
again. I have even let a couple stay with their clock out of synch for a few
days and then all of a sudden it will be correct again. Any one have any
ideas on how to fix this? I am tired of getting calls saying my clock is off.
The bigben address is what I get when I run net time /querysntp from my NTP
server.

 

[Thee Chicago Wolf]

I have recently experienced a time issue on a couple machines in my network.

Randomly I will receive a call from someone saying their time is off. I NTP
configured on my DC. It is pointing to bigben.cac.washington.edu. Looking at
my server I see no W32 time errors or warnings but when I look at the machine
that has the off time I see a w32 warning with an event id 36. I can just go
in and manually set their clock to the correct time and all will be fine
again. I have even let a couple stay with their clock out of synch for a few
days and then all of a sudden it will be correct again. Any one have any
ideas on how to fix this? I am tired of getting calls saying my clock is off.
The bigben address is what I get when I run net time /querysntp from my NTP
server.

Have you tried using the NIST one?

- Thee Chicago Wolf

 

[Mike Brester]

No have not tried that. I am not thinking it is the Ntp that I am getting my
time from but more something either with the PC's themselves or my DC. After
manually adjusting the users time I went back into his event viewer and it
said it was now receiving its time from my other DC. That DC does not have
NTP configured.