|
|
Installed WSUS about three months ago. Everything seemed to be working fine
for the first two months but now updates are not getting pushed out to any
machine.
I have not changed anything since I deployed it. It is running on a windows
2008 server. I have disabled all AV and tried the steps suggested for trouble
shooting connection problems:
To check network connectivity on the WSUS client computer
Click Start, and then click Run.
In the Open box, type iexplore and then press ENTER
In the Internet Explorer Address bar, type:
http://WSUSServerName/iuident.cab
where WSUS server name is the name of your WSUS server. Ensure that you are
prompted to download or open Iuident.cab. This verifies network connectivity
from the WSUS client and the availability of the Iuident.cab file on the WSUS
server.
If there are any boxes prompting you to download or save, click Cancel. In
Internet Explorer Address bar, type:
http://WSUSServerName/selfupdate/AU/x86/osvariable/languagevariable/wuaucomp.cab
where WSUSServerName is the name of your WSUS server and where osvariable is
a variable indicating the operating system of the client computer. The
possible variables for osvariableare NetServer, W2K or XP, and where
languagevariable is a variable indicating the language of the operating
system of the client computer. The possible variables for oslanguage are
based on the standard 2- to 4-letter language abbreviations. For example,
here is a URL for a client computer running an English version of Windows XP:
http://WSUSServerName/selfupdate/AU/x86/XP/EN/wuaucomp.cab
ALL OF THESE WORKED FINE.
Can someone tell me what might be the problem here?
Below is part of the update log from a failed client:
HTTP status code = 0
2008-12-04 09:57:13:307 1924 b5c PT + Caller provided credentials = No
2008-12-04 09:57:13:307 1924 b5c PT + Impersonate flags = 0
2008-12-04 09:57:13:307 1924 b5c PT + Possible authorization schemes used =
2008-12-04 09:57:13:307 1924 b5c PT WARNING: GetAuthorizationCookie failure,
error = 0x80072EFD, soap client error = 5, soap error code = 0, HTTP status
code = 200
2008-12-04 09:57:13:307 1924 b5c PT WARNING: Failed to initialize Simple
Targeting Cookie: 0x80072efd
2008-12-04 09:57:13:307 1924 b5c PT WARNING: PopulateAuthCookies failed:
0x80072efd
2008-12-04 09:57:13:307 1924 b5c PT WARNING: RefreshCookie failed: 0x80072efd
2008-12-04 09:57:13:307 1924 b5c PT WARNING: RefreshPTState failed: 0x80072efd
2008-12-04 09:57:13:307 1924 b5c PT WARNING: PTError: 0x80072efd
2008-12-04 09:57:13:307 1924 b5c Report WARNING: Reporter failed to upload
events with hr = 80072efd.
2008-12-04 10:21:08:015 1924 dc0 PT WARNING: Cached cookie has expired or
new PID is available
2008-12-04 10:21:08:015 1924 dc0 PT Initializing simple targeting cookie,
clientId = 02232632-51b4-495f-9489-6b046327a576, target group = , DNS name =
pl-5677834.usrenalcare.corp.com
2008-12-04 10:21:08:015 1924 dc0 PT Server URL =
https://10.111.6.95/SimpleAuthWebService/SimpleAuth.asmx
2008-12-04 10:21:22:439 1924 dc0 Misc WARNING: Send failed with hr = 80072efd.
2008-12-04 10:21:22:439 1924 dc0 Misc WARNING: SendRequest failed with hr =
80072efd. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes
used : <>
2008-12-04 10:21:22:439 1924 dc0 PT + Last proxy send request failed with
hr = 0x80072EFD, HTTP status code = 0
2008-12-04 10:21:22:439 1924 dc0 PT + Caller provided credentials = No
2008-12-04 10:21:22:439 1924 dc0 PT + Impersonate flags = 0
2008-12-04 10:21:22:439 1924 dc0 PT + Possible authorization schemes used =
2008-12-04 10:21:22:439 1924 dc0 PT WARNING: GetAuthorizationCookie failure,
error = 0x80072EFD, soap client error = 5, soap error code = 0, HTTP status
code = 200
2008-12-04 10:21:22:439 1924 dc0 PT WARNING: Failed to initialize Simple
Targeting Cookie: 0x80072efd
2008-12-04 10:21:22:439 1924 dc0 PT WARNING: PopulateAuthCookies failed:
0x80072efd
2008-12-04 10:21:22:439 1924 dc0 PT WARNING: RefreshCookie failed: 0x80072efd
2008-12-04 10:21:22:439 1924 dc0 PT WARNING: RefreshPTState failed: 0x80072efd
2008-12-04 10:21:22:439 1924 dc0 PT WARNING: PTError: 0x80072efd
|
|
"D303M" <D303M[ at ]discussions.microsoft.com> wrote in message
news:900E609F-9278-43FE-BEF1-83FD6A56B656[ at ]microsoft.com...
[Quoted Text] > Installed WSUS about three months ago. Everything seemed to be working
> fine
> for the first two months but now updates are not getting pushed out to any
> machine.
> I have not changed anything since I deployed it. It is running on a
> windows
> 2008 server. I have disabled all AV and tried the steps suggested for
> trouble
> shooting connection problems:
The steps you've taken are for =WSUS2=, as evidenced by this phrase:
> and where osvariable is
> a variable indicating the operating system of the client computer. The
> possible variables for osvariableare NetServer, W2K or XP
The only WUAs that will actually try to use those URLs are the WUAs
associated with WSUS v2. :-///
So, while that test may have worked, to be honest, it's results are
generally meaningless -- except to tell us that the webserver isn't down.
Furthemore, those diagnostic steps only scratch the surface of the possible
issues. As noted in the text you cited, "...To check network connectivity on
the WSUS client computer..." In effect, all this test does is ensure that
=INTERNET EXPLORER= can talk to the webserver on the machine hosting WSUS.
A ping to the WSUS Server, or a telnet to port 80 would achieve essentially
the same results.
Unfortunately for this test, neither WSUS nor the Windows Update Agent use
Internet Explorer, they use WinHTTP, and that's where the real diagnostics
need to take place.
> Below is part of the update log from a failed client:
But the logfile is a *great* starting place! :-)
> 2008-12-04 09:57:13:307 1924 b5c PT WARNING: GetAuthorizationCookie
> failure,
> error = 0x80072EFD, soap client error = 5, soap error code = 0, HTTP
> status
> code = 200
The 0x80072EFD error means that the =WUA= did not receive a response back
from the server (or any other device). When the WUA gets no response to a
query to the WSUS Server, it logs 0x80072EFD "CANNOT CONNECT". The actual
cause could be any one of a dozen different reasons, but they almost always
fall back to some defect in the network infrastructure and/or configuration.
Remember earlier when I pointed out that even though IE works, that doesn't
tell us anything about WinHTTP. This log entry does. It tells us that
something is completely blocking the traffic flow via WinHTTP from the
client to the WSUS Server.
Back to your "nothing changed".... I'd be looking deeper for something that
*did* change. :-)
Honestly, in all my gazillions of observations over the years, I cannot tell
you how many times that "it worked, but now it doesn't" is traced back to
"something changed". In addition, in about half of those observations, the
admin-in-charge prefaced the whole presentation with "but nothing has
changed".... only to find out that something *DID* change. It's those
changes that are *unknown* that cause these type of problems.
The correct diagnostic response is not to say "But, nothing has changed."
It's to know that "Something DID change and I NEED to find out what it is
that's changed."
> 2008-12-04 10:21:08:015 1924 dc0 PT Server URL =
> https://10.111.6.95/SimpleAuthWebService/SimpleAuth.asmx
Also, let's help the situation by disabling =SSL= and ensuring the system
works without SSL.
If it "was working",
and "now is not working",
and "nothing changed",
and you're using SSL,
then maybe the certificate is defective?
Although if that were the case, you should still get some response back from
the server, in which case you'd not be logging an 0x80072efd error code.
So.. maybe something is simply blocking SSL traffic? Like... a firewall
that's been enabled and is now blocking port 443?
Also, is there some particular reason you've used the IP Address in the URL
configuration, rather than a hostname based URL?
Like, maybe... the hostname couldn't connect.... because your DNS is
misconfigured???
--
Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)
MS WSUS Website: http://www.microsoft.com/wsus
My Websites: http://www.onsitechsolutions.com;
http://wsusinfo.onsitechsolutions.com
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
|
|
|