0x8024402C - Possible Fix
From: all the products are beta lol (anonymous_at_discussions.microsoft.com)
Date: 08/31/04
- Next message: Dave: "SP2 & ODBC"
- Previous message: Tip: "Re: XP SP2 CD arrived today"
- Next in thread: Special_K: "Re: 0x8024402C - Possible Fix"
- Reply: Special_K: "Re: 0x8024402C - Possible Fix"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 30 Aug 2004 21:24:33 -0700
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: Dave: "SP2 & ODBC"
- Previous message: Tip: "Re: XP SP2 CD arrived today"
- Next in thread: Special_K: "Re: 0x8024402C - Possible Fix"
- Reply: Special_K: "Re: 0x8024402C - Possible Fix"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
