Archive for June, 2008

New clients won’t sync to WSUS with SP1

Ok, you’ve had WSUS 3.0 running smoothly for some months now (finally!)  But now, you add a new computer to your domain and try to get it to sync up with your WSUS server to install the bazillion updates it needs but it doesn’t find any updates.  Your WSUS 3.0 comsole lists the new computer but says “Not yet reported” for it’s status.  You try running wuauclt /detectnow on the new computer but still no joy.  Now you put your clever brain to work and start digging through the logs and you find “WARNING: SyncUpdates failure, error =  0×8024400D” near the bottom of the WindowsUpdate.log file.  You think you’re onto something!  But what???  You find all kinds of misleading posts all over googledom.  Here is likely what is going on:  Microsoft (suprise, suprise) put their foot in it again.  They issued a screwed up MS Office 2003 SP1 re-release in the June, 2008 updates.  To fix the problem, find that update and change it from Declined to Not Approved.  How did I know it was Declined???  It was an inspired guess.  Magically everyone starts reporting in and updating.  Go figure.



1 Comment

Vista errors 1747 and 10107

Suddenly your Vista computer decides to go on strike.  Network connections don’t work, wierd failure messages pop up, and you can’t even open up event viewer to see what the problem is!  You try to start Event logging or other services that should be started but aren’t and you get a “Error 1747: The authentication service is unknown” mesage.  You try other things and your get the fabulous “Error 10107: A system call that should never fail has failed” mesage. (go figure - Microsoft can take the time to create an error mesage the shouldn’t ever happen, but can’t take the time to actually fix the problem!)  Anyway the problem, believe it or not, is likely to be a messed up Winsock stack.  TCP/IP stack Winsock settings in Windows Vista may get corrupted, causing errors and problems with Internet connectivity. Corrupt Winsock or Windows sockets configuration can be due to a lot of reasons such as installation of a networking software, or due to virus, trojan or malware infection, or sometime even due to disinfection of spyware by security software.

When Winsock corrupts, the networking errors that you may face include unable to surf the Internet with “Page cannot be displayed” error message in Internet Explorer or AOL even though the DSL/ADSL/cable Internet connection is connected. Sometimes, Windows Firewall/Internet Connection Sharing (ICS) service is terminated as well.

To repair and reset the Windows Vista Winsock Stack:

  1. Click on Start button.
  2. Type Cmd in the Start Search text box.
  3. Press Ctrl-Shift-Enter keyboard shortcut to run Command Prompt as Administrator. Allow elevation request.
  4. Type netsh winsock reset in the Command Prompt shell, and then press the Enter key.
  5. Restart the computer.

What netsh winsock reset command does is it resets Winsock Catalog to a clean state or default configuration. It removes all Winsock LSP (Layered Service Providers) previously installed, including the potential malfunctioned LSP that causes loss of network packets transmission failure. So all previously-installed LSPs must be reinstalled. This command does not affect Winsock Name Space Provider entries.

Note: To check which LSPs installed on your Vista system, use netsh winsock show catalog command.