Cyberpro60 wrote:
> Judging by the large number of posts both here and elsewhere about
the error
> 8024402C that you get when trying to run Windows Update on an XP
workstation
> on a firewall protected network, a lot of people have been having the
same
> problem as I have.
>
> This error has bugged me for ages. I read all the technotes about
this
> problem and tried a dozen suggestions - all without success. I also
logged
> the problem with Microsoft Windows Update Support Service and was
promised an
> email response within 24 hours. I am still waiting ..... (not very
impressive
> Microsoft)
>
> The good news is that I finally found a solution that works so I
thought I
> would share it with others in a similar position.
>
> First things first though. If you are on a Windows Network and you
are
> running Microsoft ISA Server then you MUST configure ISA to allow the
> appropriate requests to pass through the proxy service. There is an
excellent
> article at
http://www.electrosonics.net/technot...0x8024402C.htm which
> explains how to do this in some detail. (Mind you I tried this quite
a while
> ago and still couldn't get it to work - the reason is that the
problem lies
> elsewhere - more later)
>
> After you have configured ISA Server as discussed above you will
probably
> find, like I did, that the Update service still doesn't work. If you
do as I
> did, and click on the Error status messages provided in the Windows
Update
> Error Reporting Service (comes up automatically when Update fails)
you will
> be directed to an article by Microsoft about this error
> (http://support.microsoft.com/kb/883821) which tells you to open a
command
> window and type the following
>
> proxycfg -d
> net stop wuauserv
> net start wuauserv
>
> Please note: These instructions are COMPLETELY WRONG for an XP
workstation
> on a network. It is wrong because the command proxycfg -d assumes a
DIRECT
> CONNECTION to the internet - which you don't have on a network
running ISA
> server.
>
> If you change the commands as follows
>
> proxcfg -p [Servername] [exception list]
> net stop wuauserv
> net start wuauserv
>
> you will find the Windows Update service works just fine. In the
above
> example [Servername] can be either the SystemServer or whatever you
call your
> server OR, preferrably, the IP number of your server. If you have
followed
> the standard installation routines for a network server this IP will
be
> 192.168.0.1
>
> Since I did this I have had no problems with Windows Update. I hope
this
> helps you to resolve this annoying problem. Let me know your
experiences
> please.
You are completely right that the missing proxy setting is the major
glitch.
Assuming one has already set up their proxy settings within their IE
browser (Tools/Internet Options/Connections/LAN Settings) it's a little
easier to use "proxycfg -u".
proxycfg -u picks up the proxy settings you already have and uses them
rather than having to retype all that stuff in. For the life of me I
can't figure out why Windows update doesn't just use the proxy settings
that the browser was already using in the first place. The thing you
are setting with proxycfg is the proxy information for the things that
don't normally use the regular Windows proxy settings.
192.168.0.1 may be the average IP of firewalls in a home/small network
environment, but in a large corporate environment it can be quite
different because the connection to the firewall might be a few hops
away. Also there might be multiple firewalls where they actually want
you accessing them via names so the DNS servers can help spread the
load between them for access from various parts of a corporation.
Curtis Eickerman
Similar Threads
Linear Mode
