Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Help WSUS server is not seeing or updating clients.

1,028 views
Skip to first unread message

wona...@gmail.com

unread,
Apr 10, 2013, 12:52:14 PM4/10/13
to
Hi. I have run clientDiag.exe on a client desktop and here is the output.

C:\>ClientDiag.exe

WSUS Client Diagnostics Tool

Checking Machine State
Checking for admin rights to run tool . . . . . . . . . PASS
Automatic Updates Service is running. . . . . . . . . . PASS
Background Intelligent Transfer Service is not running. PASS
Wuaueng.dll version 7.6.7600.256. . . . . . . . . . . . PASS
This version is WSUS 2.0

Checking AU Settings
AU Option is 3 : Notify Prior to Install. . . . . . . . PASS
Option is from Policy settings

Checking Proxy Configuration
Checking for winhttp local machine Proxy settings . . . PASS
Winhttp local machine access type
<Direct Connection>
Winhttp local machine Proxy. . . . . . . . . . NONE
Winhttp local machine ProxyBypass. . . . . . . NONE
Checking User IE Proxy settings . . . . . . . . . . . . PASS
User IE Proxy. . . . . . . . . . . . . . . . . NONE
User IE ProxyByPass. . . . . . . . . . . . . . NONE
User IE AutoConfig URL Proxy . . . . . . . . . NONE
User IE AutoDetect
AutoDetect not in use

Checking Connection to WSUS/SUS Server
WUServer = http://WSUS.blah
WUStatusServer = http://WSUS.blah
UseWuServer is enabled. . . . . . . . . . . . . . . . . PASS
Client is pointed to SUS 1.0 Server
Connection to server. . . . . . . . . . . . . . . . . . PASS
SelfUpdate folder is present. . . . . . . . . . . . . . PASS


Everything here looks good. But when I log on to the WSUS Server and look at computers there are 0 with status ANY.

I am running this on Server 2003 SBS but the default install of wsus stopped working so I uninstalled it and installed using wsus 3.0 sp2
Version 3.2.7600.226. << I think this is the problem.

Please help, and I will gladly add any more info as needed.

wona...@gmail.com

unread,
Apr 10, 2013, 1:24:28 PM4/10/13
to
Ok here's an update. I looked at %windir%\windowsupdate.log

erver URL = http://<WSUS IP>/SimpleAuthWebService/SimpleAuth.asmx
2013-04-10 10:07:57:239 1240 ea0 PT WARNING: GetAuthorizationCookie failure, error = 0x80244019, soap client error = 10, soap error code = 0, HTTP status code = 404
2013-04-10 10:07:57:239 1240 ea0 PT WARNING: Failed to initialize Simple Targeting Cookie: 0x80244019
2013-04-10 10:07:57:239 1240 ea0 PT WARNING: PopulateAuthCookies failed: 0x80244019

So I tried to load http://<WSUS IP>/SimpleAuthWebService/SimpleAuth.asmx
That does not work.
However http://<WSUS IP>:8530/SimpleAuthWebService/SimpleAuth.asmx does work.

How can I fix this so that the client tries to use port 8530 and not port 80?

wona...@gmail.com

unread,
Apr 10, 2013, 1:34:19 PM4/10/13
to
Rather than trying to fix all the clients I had to move the iis default web site off port 80 and give that to the WSUS Administration using inetmgr. Voila now the comptuers show up in the WSUS console!

Amazing how tyring to ask the question actually solves the problem.

BTW WSUS used to be so easy but it has gotten very difficult and buggy.
WHY MICROSOFT?! WHY?!

BTW If someone still has an answer on how to force clients to use port 8530 rather than port 80 I would love to hear it.
Also the SSL Port 8531 does not work. Anyone know why?

wona...@gmail.com

unread,
Apr 10, 2013, 1:35:32 PM4/10/13
to
So one of the things I learned is that WSUS client diagnostic tool is unreliable.
It doesnt' actually tell you if WSUS client is working.

julienc...@gmail.com

unread,
Dec 3, 2014, 6:24:37 AM12/3/14
to
hi There could you give me instructions on how you changed the default port to 8530, im having the same issue.
thanks
0 new messages