Re: 0x8024402C - Possible Fix
From: Sebastian Molinari (monoxxi_at_yahoo.com.ar)
Date: 08/31/04
- Next message: Sebastian Molinari: "Re: 0x8024402C is driving me absolutely crazy!"
- Previous message: Sudheer GN [MSFT]: "Re: BITS"
- Next in thread: Frank: "Re: 0x8024402C - Possible Fix"
- Maybe reply: Frank: "Re: 0x8024402C - Possible Fix"
- Reply: Special_K: "Re: 0x8024402C - Possible Fix"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 31 Aug 2004 14:12:58 -0300
erase the folder
C:\WINDOWS\SoftwareDistribution
"all the products are beta lol" <anonymous@discussions.microsoft.com>
escribió en el mensaje news:05d501c48f12$6a88f3c0$a401280a@phx.gbl...
> This error was driving me nuts.
>
> One thing that was absolutely bizzarre to me, is that in
> the log, not only as many ppl are seeing, is there
> reference to an attempted connection by proxy (when ie
> connection settings are not set to proxy) BUT the hostname
> of the proxy matched the hostname that my server was set
> to about a month ago (not the current hostname, and there
> was never a proxy anyway!) This particular machine was
> also never previously connected to this server! My only
> guess is that MS is somehow and for some reason keeping
> some sort of dated reverse DNS log and directing windows
> update to use a proxy on that host.
>
> Now for the good part (after a full day wasted.) To
> resolve the issue, I set ie to actually use a proxy (one
> of the free open ones) and put the exception list in.
>
> Windows update then worked.
>
> I removed the proxy settings, and it worked again.
>
> Problem solved. I hope. Still curious about the cause, I'm
> wandering if perhaps it might be some sort of anti-piracy
> measure that blocks windows update v5 from certain IP's.
> It is possible that I have hooked up customer's systems
> with bad copies to my server to work on...
- Next message: Sebastian Molinari: "Re: 0x8024402C is driving me absolutely crazy!"
- Previous message: Sudheer GN [MSFT]: "Re: BITS"
- Next in thread: Frank: "Re: 0x8024402C - Possible Fix"
- Maybe reply: Frank: "Re: 0x8024402C - Possible Fix"
- Reply: Special_K: "Re: 0x8024402C - Possible Fix"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
