Re: WSUS Client Errors 0x80072EE2 and 0x80072efe error

"PCWatch" <> wrote in message
news:4219E10F-6DFE-40DA-AE13-...

> I have an issue regarding my WSUS updates. The windows WSUS client has
> stopped downloading upates from the server (error log below). Im getting
> an
> 0x80072EE2 and 0x80072efe error. I've also tried to reslove the issue with
> no
> luck. Here is what has been done:

The 0x80072EE2 error is a TImeout error.

The 0x80072EFE error is a Connection Aborted error.


> 7) WSUS Server is controlled by the ISP and they tell me all is well.

HUH? ? ? ? ?

"controlled by the ISP"???

> Any advice would be appreciated.

I don't see the 0x80072efe error in this log segment anywhere.

Timeouts are what they are and if you don't have control of both ends of the
network connection, it's going to be near impossible to diagnose.

The place to start, though, as always when something "quits working" is to
take an inventory of "What Has Changed?"



--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
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/pro...awrence.Garvin

"PCWatch" <> wrote in message
news:C59F39E3-A835-469D-93AD-...

> Hi,
>
> Thanx for the reply. The Web Server is in the datacenter and this is
> causing
> the fustration. The ISP is providing WSUS as a service to all client.

Yeah.... this is the part I don't get. These two statements are incongrous.

"The Web Server is in the datacenter..." (I assume this is the web server
running WSUS.)

and

"The ISP is providing WSUS as a service to all client."

What *exactly* do you mean by "ISP" in this context?

> The technicians insist that the WSUS is working perfectly and there is a
> problem on my end.

That's impossible for me to comment on without understanding the exact
network topology of this seemingly unorthodox environment.

> I just want to ensure that I've elimnated all possibilities on the
> client side before I take them to the cleaners.
>
> With regards to your question what was change ?
>
> 1) I installed a new anti-virus - symantec end point

Bingo!

> 2) I changed some of the rules on the hardware firewall.

Bingo!


> I've reversed the above changes by:
>
> 1) Removing the anti-virus.
> 2) Disabling the firewall (for a short period of time and then forced and
> update).
>
> The errors are still appearing.

Let's leave those uninstalled and disabled for the moment.

I'm still *very* confused, though.

WHAT did you install Symantec End Point onto?

WHAT hardware firewall did you modify?

WHERE is the WSUS Server in relation to all of the servers and devices
you've mentioned so far?


--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
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/pro...awrence.Garvin

"PCWatch" <> wrote in message
news:C59F39E3-A835-469D-93AD-...

> Please see below for the 0x80072efe error:

Well... here's a clue...

This is a log entry from your original post:

> 2009-05-31 17:28:24:281 892 cc0 PT Initializing simple targeting cookie,
> clientId = 3eed87c2-b6ba-4c9e-b43b-df68a2796e5a,
> target group = Company,
> DNS name = wwwcomputer

And this is a log entry from this post:

> 2009-06-08 14:13:55:390 812 b28 PT Initializing simple targeting cookie,
> clientId = 3eed87c2-b6ba-4c9e-b43b-df68a2796e5a,
> target group = Hetzner, DNS
> name = wwwpcwatch

They're different computers. (They have DNS misconfigured, as evidenced by
the log entry containing only a machine name, not a fully qualified domain
name -- which is what it should have).

But, most significantly, they have IDENTICAL SusClientID values.

Your client systems have duplicate SusClientIDs.

And that's capable of causing timeouts and aborts -- among a host of other
issues!


--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
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/pro...awrence.Garvin

"PCWatch" <> wrote in message
news:FF22D571-4074-40F1-BA7E-...
> (They have DNS misconfigured, as evidenced by the log entry containing
> only a
> machine name, not a fully qualified domain name -- which is what it should
> have)
>
> The webserver is setup in a workgroupo. They don't have a domain.

Really irrelevant -- a WEB SERVER should have a known FULLY QUALIFIED
hostname.

The point has absolutely nothing to do with whether the web server(s) are in
workgroups or Active Directory.


> 2009-06-09 12:45:45:265 800 ec8 Misc WARNING: WinHttp:
> IsFileToBeDownloaded
> failed with 0x80004004

With regard to the 0x80004004 error code -- this KB article documents an ASP
(server-side) issue that occurs in Microsoft Project Server. It's certainly
possible the same error can be encountered in a WSUS environment.

http://support.microsoft.com/kb/323019


--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
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/pro...awrence.Garvin