Re: Unable to download through Windows Update on WinXP SP2

Well, maybe the rest of these people got it to work, but it didn't work for
me. Perhaps the significant difference with my installation is that we are
not using MS server but are using a third party server - which seems to work
with about everything BUT Win Update.

Sorry, Microsoft guys, but this is YOUR problem with using proxy servers
with Win Update which USED to work. If I plug the network directly to the
DSL modem and bypass the proxy server (and change settings to direct), even
with SP2, WU works. Forget the BS, that's the facts.

More data: proxycfg revealed that WinHTTP did not originally have the proxy
set. It does now but it doesn't make any difference to the original problem.

In my travels in investigating this, I came across a sketchy reference to a
WinProxy Auto-Detect and a wpad.dat file. I can't find this anywhere on my XP
or 2000 systems. I assume that it is buried and hidden from us peasants. This
must be some more of Microsoft's nannyware where they are arrogant enough to
think that they can find my proxy server. Obviously, not.

I await a real fix from Uncle Bill and company and not these deleting folder
contents BS. Only a bonehead would design software to not look at the manual
settings (like WinHTTP and IE), first, and THEN go looking for a proxy server.


"r2715" wrote:

>
> Oenone wrote:
> > Hi Torgeir,
> >
> > Many thanks for your detailed reply.
> >
> > I passed your message to our network administrator who implemented
> the
> > recommended changes to the ISA Server, but it hasn't made any
> difference.
> >
> > A misconfigured ISA Server also wouldn't explain why the SP1 computer
> can
> > still use Windows Update. We've also now found a single SP2 computer
> that is
> > able to use WU too without any problems. The rest of the SP2 PCs are
> still
> > unable to be updated.
> >
> > Do you (or does anyone else) have any other suggestions as to what
> might be
> > going wrong?
> >
> > --
> >
> > (O)enone
>
> Here's what works for our company:
> 1. Click on Start, and then click Run.
> 2. Type cmd in the Open box to get a DOS prompt.
> 3. Type "net stop wuauserv" without the quotes at the command prompt,
> and press Enter.
> 4. Delete (or put in recycle bin) the contents of
> C:\WINDOWS\SoftwareDistribution (but not the SoftwareDistribution
> folder) 5. Type net start wuauserv at the command prompt, and press
> Enter.
> 6. Now try Windows Update again.
>
> This is some kind of Microsoft foul-up that they really need to fix and
> quite blaming proxy connections.
>
>

"colorfguru" <colorfguru@discussions.microsoft.com> wrote in message
news:C0F3E657-8FF4-4CF3-8B1B-272A990D80CD@microsoft.com
....

in this long abandoned thread:

http://www.microsoft.com/communities...8-113ed4ce07e2


> Well, maybe the rest of these people got it to work, but it didn't work for
> me. Perhaps the significant difference with my installation is that we are
> not using MS server but are using a third party server - which seems to work
> with about everything BUT Win Update.
>
> Sorry, Microsoft guys, but this is YOUR problem with using proxy servers
> with Win Update which USED to work. If I plug the network directly to the
> DSL modem and bypass the proxy server (and change settings to direct), even
> with SP2, WU works. Forget the BS, that's the facts.


Exactly; in order to make a connection to the WU site now
with WUv5 or WUv6 through your proxy server you need to
make it allow anonymous access. Note that the connection
by BITS (at least) is not made using your account.

<title>You experience problems when you access the Windows Update Version 5
or Version 6 Web site through a server that is running ISA Server</title>
http://support.microsoft.com/default...b;en-us;885819


BTW I strongly suspect the some of the "successes" in this thread
probably got attracted to it only because of its overly general Subject
and failed to notice the significant detail that the OP provided about
an ISA proxy being involved. Further since the task of making
it work for the OP was handled by a different group I would not
be surprised if the final "resolution" was not entirely coincidental
with some appropriate change being made to the proxy server. <eg>


Good luck

Robert Aldwinckle
---