W32Time Error 27 in Single Windows XP SP3 Client

Hello Experts,
I've had a problem with NTP / w32time for months now on 1 client (out of 500+, so I know the server and network is OK).  

This PC sometimes looses it's time setting all together (i.e moves to 1/1/93 or something), but mostly just outright has difficulty with NTP. I notice the communication problems in the Windows Event Logs. Example for today: over 300 of the error below in the Event/System logs.

Error 27
Source: W32Time
Time Provider NtpClient: The response received from domain controller DC.domain.int is
missing the signature. The response may have been tampered with and will be ignored.

In the past, I've tried a variety of things including virus scanning, hardware diagnostics (HDD, RAM, etc). I'm sure I ran CHKDSK and SFC, but can't really remember exactly everything which was run. I know the problem never really went away. The user has just ignored it.

Anyone more familiar with Windows XP w32tm and NTP to maybe give me some pointers for this one client?

Thanks for your time!
LVL 7
ottobockAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
ottobockAuthor Commented:
Also, I'm sort of looking for direct troubleshooting steps to try instead of
"Here is a Microsoft Technet Article on w32Time ~ read it."
:-) Thanks!
0
 
Darius GhassemCommented:
Run w32tm /resync /rediscover
0
Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

 
ottobockAuthor Commented:
Strange... Ran the command, and there is no update yet in the event logs (whether it synced or error...) Still checking.
0
 
Darius GhassemCommented:
If the command ran successfully then it sync properly
0
 
ottobockAuthor Commented:
Same error. :-(
0
 
Darius GhassemCommented:
w32tm /monitor
0
 
ottobockAuthor Commented:
OK - I ran the w32tm /monitor, and it returned a list of all the NTP servers in our Domain. I then re-ran w32tm /resync /rediscover and it stated the registration was successful. No errors since, but continuing to monitor. Thanks!
0
 
ottobockAuthor Commented:
Still the same error. I have a feeling there is some corruption deep down, or maybe a strange hardware issue on this PC. This weekend, I ran SFC /scannow and CHKDSK /r, and the errors still occur...
0
 
Darius GhassemCommented:
Disable any AV
0
 
ottobockAuthor Commented:
Still no help... I'm thinking this is caused by a bad OS installation, or possibly bad HW. Thanks anyway for your ideas!
0
 
ottobockAuthor Commented:
OK - I tried the trick from the first link, specifically,

***************
Brent Knight
I got this error on a single WinXP machine on my network. All the other workstations were running W32Time without major problems. The only difference was that this was my own workstation and I had tried to configure the W32tm application manually.
To fix it, I unregistered the service (removing it from the system and the registry) using the command "w32tm /unregister" then restarted the machine. Run "w32tm /register" after reboot and check the service state (should be set to automatic, but start manually if necessary).
This does not get to the root of the problem (probably some misconfiguration of W32tm), but so far I've had no more problems.
***************

After the Unregister/restart, the time/date was way off, and then after the register/query, the time did sync correctly. Now I'll monitor it for a few days.

Thanks!
0
All Courses

From novice to tech pro — start learning today.