Re: Problem with WSUS - computers can no longer connect

Right pew, wrong church. Forwarded to WSUS newsgroup
(microsoft.public.windows.server.update_services) via crosspost as a
convenience to OP.

On the web:
http://www.microsoft.com/communities...pdate_services

In your newsreader:
news://msnews.microsoft.com/microsof...pdate_services

Charlie_Bebop wrote:
> Hi Everyone. First post on here, but this looks like the most
> knowledgeable place I've found when it comes to WSUS. WSUS is installed
> on my DC, and I've been using it successfully for about 6 months.
> However, recently my computers can no longer connect. I see in WSUS that
> all the computers haven't connected for 56 days. Around this date we put
> some new security policies on the domain, but we have rolled all of them
> back one by one, and the clients still won't connect to WSUS. The PC's
> connect using domain group policy.
>
> I have run InstallSelfupdateOnPort80.vbs, and it concluded fine.
>
> When I run clientdiag.exe, everything looks OK:
>
>
>
> Checking Machine State
> Checking for admin rights to run tool . . . . . . . . . PASS
> Automatic Updates Service is running. . . . . . . . . . PASS
> Background Intelligent Transfer Service is running. . . PASS
> Wuaueng.dll version 7.1.6001.65 . . . . . . . . . . . . PASS
> This version is WSUS 2.0
>
> Checking AU Settings
> AU Option is 4: Scheduled 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
> 172.16.100.101:8080
> User IE ProxyByPass
> 192.168.0.0;172.16.0.0;<local>
> User IE AutoConfig URL Proxy . . . . . . . . . NONE
> User IE AutoDetect
> AutoDetect not in use
>
> Checking Connection to WSUS/SUS Server
> WUServer = http://someserver
> WUStatusServer = http://someserver
> UseWuServer is enabled. . . . . . . . . . . . . . . . . PASS
> Client is pointed to SUS 1.0 Server
> Connection to server. . . . . . . . . . . . . . . . . . PASS
> SelfUpdate folder is present. . . . . . . . . . . . . . PASS
>
>
> The only place that suggests where the problem is in the IIS logs:
>
> 2008-08-13 00:02:48 W3SVC1 172.16.x.x HEAD
> /selfupdate/WSUS3/x86/Other/wsus3setup.cab 0808130002 80 - 172.16.x.x
> Windows-Update-Agent 200 0 0
> 2008-08-13 00:02:48 W3SVC1 172.16.x.x GET
> /selfupdate/WSUS3/x86/Other/wsus3setup.cab 0808130002 80 - 172.16.x.x
> Windows-Update-Agent 200 0 0
> 2008-08-13 00:02:50 W3SVC1 172.16.x.x POST
> /SimpleAuthWebService/SimpleAuth.asmx - 80 - 172.16.x.x
> Windows-Update-Agent 404 0 3
> 2008-08-13 00:03:28 W3SVC1 172.16.x.x POST
> /ClientWebService/client.asmx - 80 - 172.16.x.x Windows-Update-Agent 404
> 0 2
>
> The SimpleAuthWebService message is repeated for all the clients. I've
> checked both the files exist.
>
> Could anyone give me some idea as to what's going wrong?

"PA Bear [MS MVP]" wrote:

> Right pew, wrong church. Forwarded to WSUS newsgroup
> (microsoft.public.windows.server.update_services) via crosspost as a
> convenience to OP.
>
> On the web:
> http://www.microsoft.com/communities...pdate_services
>
> In your newsreader:
> news://msnews.microsoft.com/microsof...pdate_services
>
> Charlie_Bebop wrote:
> > Hi Everyone. First post on here, but this looks like the most
> > knowledgeable place I've found when it comes to WSUS. WSUS is installed
> > on my DC, and I've been using it successfully for about 6 months.
> > However, recently my computers can no longer connect. I see in WSUS that
> > all the computers haven't connected for 56 days. Around this date we put
> > some new security policies on the domain, but we have rolled all of them
> > back one by one, and the clients still won't connect to WSUS. The PC's
> > connect using domain group policy.
> >
> > I have run InstallSelfupdateOnPort80.vbs, and it concluded fine.
> >
> > When I run clientdiag.exe, everything looks OK:
> >
> >
> >
> > Checking Machine State
> > Checking for admin rights to run tool . . . . . . . . . PASS
> > Automatic Updates Service is running. . . . . . . . . . PASS
> > Background Intelligent Transfer Service is running. . . PASS
> > Wuaueng.dll version 7.1.6001.65 . . . . . . . . . . . . PASS
> > This version is WSUS 2.0
> >
> > Checking AU Settings
> > AU Option is 4: Scheduled 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
> > 172.16.100.101:8080
> > User IE ProxyByPass
> > 192.168.0.0;172.16.0.0;<local>
> > User IE AutoConfig URL Proxy . . . . . . . . . NONE
> > User IE AutoDetect
> > AutoDetect not in use
> >
> > Checking Connection to WSUS/SUS Server
> > WUServer = http://someserver
> > WUStatusServer = http://someserver
> > UseWuServer is enabled. . . . . . . . . . . . . . . . . PASS
> > Client is pointed to SUS 1.0 Server
> > Connection to server. . . . . . . . . . . . . . . . . . PASS
> > SelfUpdate folder is present. . . . . . . . . . . . . . PASS
> >
> >
> > The only place that suggests where the problem is in the IIS logs:
> >
> > 2008-08-13 00:02:48 W3SVC1 172.16.x.x HEAD
> > /selfupdate/WSUS3/x86/Other/wsus3setup.cab 0808130002 80 - 172.16.x.x
> > Windows-Update-Agent 200 0 0
> > 2008-08-13 00:02:48 W3SVC1 172.16.x.x GET
> > /selfupdate/WSUS3/x86/Other/wsus3setup.cab 0808130002 80 - 172.16.x.x
> > Windows-Update-Agent 200 0 0
> > 2008-08-13 00:02:50 W3SVC1 172.16.x.x POST
> > /SimpleAuthWebService/SimpleAuth.asmx - 80 - 172.16.x.x
> > Windows-Update-Agent 404 0 3
> > 2008-08-13 00:03:28 W3SVC1 172.16.x.x POST
> > /ClientWebService/client.asmx - 80 - 172.16.x.x Windows-Update-Agent 404
> > 0 2
> >
> > The SimpleAuthWebService message is repeated for all the clients. I've
> > checked both the files exist.
> >
> > Could anyone give me some idea as to what's going wrong?
>
>

Apologies, actually found out what the twofold issues were. first, I hadn't
put the port number of 8530 into the url in the group policy settings.
Second, the relevent users didn't have permission to access the wsus site in
IIS. Once I fixed these, it started working again.
Thanks again to PA Bear for moving the post