Thanks Ken... looking at the .log reveals an old WSUS server I decommissioned from this domain long ago... it must still be lurking in a GP somewhere.
I'll run that down first before bothering the list any further. Thanks for the pointer. -sc From: Ken Schaefer [mailto:[email protected]] Sent: Tuesday, January 05, 2010 7:40 PM To: NT System Admin Issues Subject: RE: Windows Update failure What's in the WindowsUpdate.log file? Do a wuauclt /detectnow and then past the entries for the attempted update from the log file. Cheers Ken From: Steven M. Caesare [mailto:[email protected]] Sent: Wednesday, 6 January 2010 11:32 AM To: NT System Admin Issues Subject: Windows Update failure So.. both my home Win2K8sp1 DC's decided to stop resolving DNS twice in the last several days. The service was running, it just stopped resolving names. A restart of the service did the trick. Being the typical cobbler without shoes, I hadn't patched these boxes in a while. Attampting to Windows Update either of them results in a failure code 8024402C in the GUI. Curiously, this is not logged in Applications, Security, System or MS/Windows/windowsUpdateClient/Operational event logs. The MS article for this error (http://windows.microsoft.com/en-US/windows-vista/Windows-Update-error-8 024402C), appears to suggest generic connectivity issues (firewall, etc..) or WSUS. Neither apply here (and I disabled IE ESC to be sure). I can browse the interweb just fine No AV or local FW enabled. Nor proxy. Thoughts? -sc ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
