NTP Issues w/XP Pro

Hi Folks;

I have a laptop here running XP Pro. It's fully updated and has been a
stellar machine for years.
There's just one issue - lately I've been getting errors in the System log;

Event ID 27

Time Provider NtpClient: The response received from domain controller (my
domain controller) is missing the signature. The response may have been
tampered with and will be ignored.

So what's happening is that it's caffing when it goes to synchronize it's
clock with my domain controller. The thing is, all my Windows 2000 servers
sync perfectly to the domain controller as does my other XP Pro machine.
There's no issues there.

The next entry in the System log shows that it did successfully obtain it's
time setting from the domain controller.

The problem is that often the event log fills up with Event ID 27 and the
same repeating error - that the laptop is getting a response from the DC
that's missing the signature.

As mentioned, every other machine on the network has no time issues with the
DC - including another XP machine. So this issue is localized to the laptop.

If anyone has any ideas on how to correct this issue I'd live to hear them.

Best & Thanks!
Dave

"Dave Onex" wrote in message
...
Hi Folks;

I have a laptop here running XP Pro. It's fully updated and has been a
stellar machine for years.
There's just one issue - lately I've been getting errors in the System
log;

Event ID 27

Time Provider NtpClient: The response received from domain controller (my
domain controller) is missing the signature. The response may have been
tampered with and will be ignored.

So what's happening is that it's caffing when it goes to synchronize it's
clock with my domain controller. The thing is, all my Windows 2000 servers
sync perfectly to the domain controller as does my other XP Pro machine.
There's no issues there.

The next entry in the System log shows that it did successfully obtain
it's time setting from the domain controller.

The problem is that often the event log fills up with Event ID 27 and the
same repeating error - that the laptop is getting a response from the DC
that's missing the signature.

As mentioned, every other machine on the network has no time issues with
the DC - including another XP machine. So this issue is localized to the
laptop.

If anyone has any ideas on how to correct this issue I'd live to hear
them.

Best & Thanks!
Dave




I'm pretty sure I cased it. After watching the system closely it appeared
that at times it would check the time every 15 minutes. I don't know why -
it had never done this before. The more I watched it the more the service
seemed to be pooched somehow.

To solve the issue I exported the registry key from another XP machine
(HKEY_LOCAL_MACHINE\CurrentControlSet\Services\W32 time) and installed it in
the laptop. I then re-started the laptop and observed the behavior - upon
startup it checked the time once, reported it correctly in the System log
and hasn't created any issues since :-)

Best!
Dave Onex