Something similar recently happened to me on my home SBS2008 server. I removed WSUS and reinstalled. Don't know if that is the "proper" way to fix, but it worked for me.
Also, I had an issue because I disabled IPV6 on the NIC. I re-enabled it which fixed the issue. However, I can't recall exactly what the "issue" was. I did both of these at the same time, so I am not sure which "fixed" the WSUS problem. Sorry to be so vague, but I don't remember exactly what the error was. BF From: Steven M. Caesare [mailto:[email protected]] Sent: Tuesday, January 05, 2010 7:32 PM 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-8024402C), 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/> ~
