WSUS downloads to 2000 server fail

Hi,

I have a W2K server that stopped receiving downloads from our WSUS server
around 22/02/10...

It also will not download updates from the Windows Update site, failing with
error 0x800704DD.

I've checked the KB, found article ID 968001 and checked that everything was
OK (this refers to an issue with Windows Update being unable to use the
logged on user account).

Still can't download from Windows Update and WSUS fails too...

Is there a known issue with a previous patch that would cause this?

All downloads and Updates and Security features concerning W2K Server, Windows 2000
and Office 2000 has been pulled by MS as per their agreement with the DOJ and Sun
Microsystems. With all the W2K systems mentioned above , you are now on your own.

--
Peter

Please Reply to Newsgroup for the benefit of others
Requests for assistance by email can not and will not be acknowledged.

"nqetech" <> wrote in message
news:BAD5272F-CCA9-4E6B-9555-...
> Hi,
>
> I have a W2K server that stopped receiving downloads from our WSUS server
> around 22/02/10...
>
> It also will not download updates from the Windows Update site, failing with
> error 0x800704DD.
>
> I've checked the KB, found article ID 968001 and checked that everything was
> OK (this refers to an issue with Windows Update being unable to use the
> logged on user account).
>
> Still can't download from Windows Update and WSUS fails too...
>
> Is there a known issue with a previous patch that would cause this?

On Tue, 9 Mar 2010 17:23:09 -0500, "Peter Foldes" <> wrote:

>All downloads and Updates and Security features concerning W2K Server, Windows 2000
>and Office 2000 has been pulled by MS as per their agreement with the DOJ and Sun
>Microsystems. With all the W2K systems mentioned above , you are now on your own.


Do you have a reference to support this statement as MS say July/13 2010 at
http://support.microsoft.com/lifecyc...ilter=FilterNO

You can still download Office 2K SP3 from
http://www.microsoft.com/downloads/d...displaylang=EN

--
Dave Mills
There are 10 types of people, those that understand binary and those that don't.

"nqetech" <> wrote in message
news:BAD5272F-CCA9-4E6B-9555-...

> I have a W2K server that stopped receiving downloads from our WSUS server
> around 22/02/10...
>
> It also will not download updates from the Windows Update site, failing
> with
> error 0x800704DD.

0x800704DD -2147023651 Error_Not_Logged_On to network


> Is there a known issue with a previous patch that would cause this?

Nope.. but somebody reconfiguring something in Group Policy that affects all
of your machines simultaneously would be a good consideration.

The 0x800704DD (Not Logged On) error might be caused by having changed the
LogOn account for the Automatic Updates service. It might also be caused by
an intervening proxy server.

It might also be caused by a computer account with an expired password that
did not get auto-regenerated, although given that a number of systems are
simultaneously affected, this option seems less likely; however, it's
possible the entire collection of Windows 2000 computer accounts were
affected simultaneously. It could also happen if the OU containing these
Windows 2000 accounts were deleted from AD, making it impossible for the
computer to authenticate with the computer account. You might try using the
"Reset Account" option in ADUC on the computer accounts after verifying the
accounts still exist.



--
Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2010)

My Blog: http://onsitechsolutions.spaces.live.com
Microsoft WSUS Website: http://www.microsoft.com/wsus
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

Hi Lawrence,

I was obviously not very clear... it is only 1 server that is behaving in
this way, I have several others that are continuing to update without issues.

I haven't made any changes to WSUS that would have affected this particular
server - in fact, WSUS has been unchanged for some time. It has proved to be
very reliable generally.

The problem with the server isn't just WSUS, since Windows Updates manually
selected via the website also fail to download.

Patches downloaded as standalone executables work fine...

I'm at a loss to understand why this is occurring. I must admit, I had
thought of detaching the server from the domain and then re-attaching it as
other desktop issues have been resolved like this in the past.

Any other suggestions welcome!

David Hicks MCP

"Lawrence Garvin [MVP]" wrote:

> "nqetech" <> wrote in message
> news:BAD5272F-CCA9-4E6B-9555-...
>
> > I have a W2K server that stopped receiving downloads from our WSUS server
> > around 22/02/10...
> >
> > It also will not download updates from the Windows Update site, failing
> > with
> > error 0x800704DD.
>
> 0x800704DD -2147023651 Error_Not_Logged_On to network
>
>
> > Is there a known issue with a previous patch that would cause this?
>
> Nope.. but somebody reconfiguring something in Group Policy that affects all
> of your machines simultaneously would be a good consideration.
>
> The 0x800704DD (Not Logged On) error might be caused by having changed the
> LogOn account for the Automatic Updates service. It might also be caused by
> an intervening proxy server.
>
> It might also be caused by a computer account with an expired password that
> did not get auto-regenerated, although given that a number of systems are
> simultaneously affected, this option seems less likely; however, it's
> possible the entire collection of Windows 2000 computer accounts were
> affected simultaneously. It could also happen if the OU containing these
> Windows 2000 accounts were deleted from AD, making it impossible for the
> computer to authenticate with the computer account. You might try using the
> "Reset Account" option in ADUC on the computer accounts after verifying the
> accounts still exist.
>
>
>
> --
> Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
> Principal/CTO, Onsite Technology Solutions, Houston, Texas
> Microsoft MVP - Software Distribution (2005-2010)
>
> My Blog: http://onsitechsolutions.spaces.live.com
> Microsoft WSUS Website: http://www.microsoft.com/wsus
> My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin
>

"nqetech" <> wrote in message
news:C57A5B2B-06D9-40C7-9EB5-...
> Hi Lawrence,
>
> I was obviously not very clear... it is only 1 server that is behaving in
> this way, I have several others that are continuing to update without
> issues.

Okay.. but the suggestions pretty much still apply. Eliminate those that are
purely enterprise-wide, and translate those that can affect only one
machine.

> I haven't made any changes to WSUS that would have affected this
> particular
> server - in fact, WSUS has been unchanged for some time. It has proved to
> be
> very reliable generally.

I tend to agree with this, having clarified that only one Windows 2000
Server system is being affected.


> The problem with the server isn't just WSUS, since Windows Updates
> manually
> selected via the website also fail to download.

But understand that Windows Update and WSUS use the *SAME* client-side
functionality. It makes perfect sense that if accessing WSUS is broken,
accessing WU would also be broken.

> I'm at a loss to understand why this is occurring.

And yet... I just provided a litany of possible reasons -- and all of them
will be tied to SOMEBODY changed SOMETHING on that server! The key is to
find out who/what/when and reset the configuration.

> I must admit, I had
> thought of detaching the server from the domain and then re-attaching it
> as
> other desktop issues have been resolved like this in the past.

Yes... and many times those issues can also be resolved by simply using the
"Reset Account" feature of A.D.U.C. (which is the net effect of
removing/re-adding to the domain, but much simpler).

To restate the previous ideas . . .

1. The 0x800704DD (Not Logged On) error might be caused by having changed
the LogOn account for the Automatic Updates service.

2. It might also be caused by an intervening proxy server and incorrect
proxy credentials.

3. It might also be caused by a computer account with an expired password
that did not get auto-regenerated.

4. It could also happen if the computer account was deleted from AD, making
it impossible for the computer to authenticate.


--
Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2010)

My Blog: http://onsitechsolutions.spaces.live.com
Microsoft WSUS Website: http://www.microsoft.com/wsus
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

Hi Lawrence,

Brilliant, the list of things to check finally made things clear for me...
It wasn't the logon for Automatic Updates, but the BITS service (I will track
down the culprit!).

After correcting BITS and re-starting both services, voila!

Thanks for your patience and kind assistance, much appreciated.

David

"Lawrence Garvin [MVP]" wrote:

> "nqetech" <> wrote in message
> news:C57A5B2B-06D9-40C7-9EB5-...
> > Hi Lawrence,
> >
> > I was obviously not very clear... it is only 1 server that is behaving in
> > this way, I have several others that are continuing to update without
> > issues.
>
> Okay.. but the suggestions pretty much still apply. Eliminate those that are
> purely enterprise-wide, and translate those that can affect only one
> machine.
>
> > I haven't made any changes to WSUS that would have affected this
> > particular
> > server - in fact, WSUS has been unchanged for some time. It has proved to
> > be
> > very reliable generally.
>
> I tend to agree with this, having clarified that only one Windows 2000
> Server system is being affected.
>
>
> > The problem with the server isn't just WSUS, since Windows Updates
> > manually
> > selected via the website also fail to download.
>
> But understand that Windows Update and WSUS use the *SAME* client-side
> functionality. It makes perfect sense that if accessing WSUS is broken,
> accessing WU would also be broken.
>
> > I'm at a loss to understand why this is occurring.
>
> And yet... I just provided a litany of possible reasons -- and all of them
> will be tied to SOMEBODY changed SOMETHING on that server! The key is to
> find out who/what/when and reset the configuration.
>
> > I must admit, I had
> > thought of detaching the server from the domain and then re-attaching it
> > as
> > other desktop issues have been resolved like this in the past.
>
> Yes... and many times those issues can also be resolved by simply using the
> "Reset Account" feature of A.D.U.C. (which is the net effect of
> removing/re-adding to the domain, but much simpler).
>
> To restate the previous ideas . . .
>
> 1. The 0x800704DD (Not Logged On) error might be caused by having changed
> the LogOn account for the Automatic Updates service.
>
> 2. It might also be caused by an intervening proxy server and incorrect
> proxy credentials.
>
> 3. It might also be caused by a computer account with an expired password
> that did not get auto-regenerated.
>
> 4. It could also happen if the computer account was deleted from AD, making
> it impossible for the computer to authenticate.
>
>
> --
> Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
> Principal/CTO, Onsite Technology Solutions, Houston, Texas
> Microsoft MVP - Software Distribution (2005-2010)
>
> My Blog: http://onsitechsolutions.spaces.live.com
> Microsoft WSUS Website: http://www.microsoft.com/wsus
> My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin
>