V5 Win update - Clients behind firewall not using proxy.

We have hundreds of Windows XP clients unable to connect to the update site
using the new V5 win update.

We use ISA and ISS proxy servers - I have looked at the log files on
checkpoint NG and it shows clients trying to directly connect to Microsoft
update without using the proxy - The packets are then obviously dropped as
there is no rule to allow http traffic from users to access the internet only
for the proxy. - I have seen several posts with the same problem but no
difinitive answer - It all worked before V5

Please help!
--
Matt

Matt P wrote:

> We have hundreds of Windows XP clients unable to connect to the update site
> using the new V5 win update.
>
> We use ISA and ISS proxy servers - I have looked at the log files on
> checkpoint NG and it shows clients trying to directly connect to Microsoft
> update without using the proxy - The packets are then obviously dropped as
> there is no rule to allow http traffic from users to access the internet only
> for the proxy. - I have seen several posts with the same problem but no
> difinitive answer - It all worked before V5
Hi

I would guess you need to configure the WinHTTP proxy settings on
the clients (using e.g. proxycfg.exe).

Open a command prompt (Start/Run and then "cmd.exe" without the
quotes).

Run this command to display current proxy configuration:

proxycfg


For more help on proxycfg.exe:

proxycfg -?


If you configure the client to your proxy "environment" using proxycfg,
does WU start to work then?


--
torgeir, Microsoft MVP Scripting and WMI, Porsgrunn Norway
Administration scripting examples and an ONLINE version of
the 1328 page Scripting Guide:
http://www.microsoft.com/technet/scr...r/default.mspx

Torgeir Bakken (MVP) wrote:

> Matt P wrote:
>
>> We have hundreds of Windows XP clients unable to connect to the
>> update site using the new V5 win update.
>>
>> We use ISA and ISS proxy servers - I have looked at the log files
>> on checkpoint NG and it shows clients trying to directly connect
>> to Microsoft update without using the proxy - The packets are then
>> obviously dropped as there is no rule to allow http traffic from
>> users to access the internet only for the proxy. - I have seen
>> several posts with the same problem but no difinitive answer
>> - It all worked before V5
>
> I would guess you need to configure the WinHTTP proxy settings on
> the clients (using e.g. proxycfg.exe).
>
> Open a command prompt (Start/Run and then "cmd.exe" without the
> quotes).
>
> Run this command to display current proxy configuration:
>
> proxycfg
>
> For more help on proxycfg.exe:
> proxycfg -?
>
> If you configure the client to your proxy "environment" using proxycfg,
> does WU start to work then?

Response from Matt P:

<quote>
I have tryed this for one client and it seems to work, thanks very
much - Does this mean it needs to be done on every XP client? New
and old? We have proxy settings entered manually into Explorer,
does windows not take these settings when connecting to V5 site?
</quote>

To avoid configuring all your clients, I would think configuring
your proxy server to allow anonymous access to the relevant Windows
Update sites is a better solution.

More about this here:

From: Allenh [MSFT] (a-)
Subject: Re: Temporary fix for 0x8024402C error
Date: 2004-09-29 08:45:32 PST
http://groups.google.com/groups?selm...TNGP10.phx.gbl



--
torgeir, Microsoft MVP Scripting and WMI, Porsgrunn Norway
Administration scripting examples and an ONLINE version of
the 1328 page Scripting Guide:
http://www.microsoft.com/technet/scr...r/default.mspx