Wsus error 8024402C

[nicholab]

I can't get Wsus to work properly I am getting this error!!

[localzuk]

In my experience, this is down to something related to proxies getting in the way.

 

If you run a command prompt, run the following:

 

netsh winhttp show proxy

 

If it responds with direct, then that eliminates that, if not, post the response here.

 

You should also have an exclusion set within the IE proxy settings for the IP/hostname of that server.

[nicholab]

Some how the server is not configured right that the error I get on a client. There is no proxy to the internet.

[localzuk]

Other possibilities are that the DNS isn't set up right - can you ping the server's hostname? Another thing to check is firewalls in between - is WSUS allowed out on the server, and requests to it allowed out from the client?

[nicholab]

Yes the packet are coming in I have checked with wireshark.

[ricki]

HI

 

Is this what you are getting

 

Clients Unable to Receive Updates with Error 8024402C - TechNet Articles - United States (English) - TechNet Wiki

 

Richard

[ricki]

This might help

Fix the problem with Microsoft Windows Update that is not working

 

Richard

[andy_nic]

is this a new WSUS server set up? or has it been working and now stopped? because I had run windows update on my wsus server as there is a new windows update client software version 7.6.00.256 as mine just stopped working after some of the computers had got this new windows update client from windows update from online.

[ricki]

Windows xp machines may need this Download: Group Policy Preference Client Side Extensions for Windows XP (KB943729) - Microsoft Download Center - Download Details

 

Richard

[nicholab]

This is a new server install

[cpjitservices]

My WSUS stopped working a few days ago, I've just got in today to find my WSUS server asking to do a Windows Update, and behold the updates where for WSUS, so once the updates had completed and the server rebooted everything is all A-OK again!

[Michael]

Hmm this is odd, I've not seen this happen at all. Running 2008 R2 with WSUS 3.0 SP2 at numerous sites.

 

Are you running an earlier version of WSUS?