Re: Error 0x8024402C when using ISA Firewall Client

LndK wrote:

> Hi
>
> Like many oithers our site cannot scan for updates on v5.windowsupdate.
> We keep getting error 0x8024402C.
>
> The only way is to uninstall the firewall client and instruct the browser to
> use the ISA server as Proxy (port 8080). This way we can successfully scan
> for updates - BUT WE NEED THE FIREWALL CLIENT in out set-up.
>
> What can I do to overcome this anoying problem?
>
> Best regrds
>


Hi

In the FW configuration, open TCP/IP 443 in both directions
for this process and see if it helps:

%windir%\system32\svchost.exe


--
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

"LndK" <> wrote in message
news:9CDFCC32-4396-4931-A7F1-...
> Hi,
>
> I have tried that with-out any luck. My feeling is that it is my own PC that
> prevents contact to v5. because no packets are send during the scan except
> from the final
> reporting.


Really? A previous trace you submitted indicates that before the error
was reported this happened:

<example>
2004-08-26 10:03:55+0200 1820 2a0 Add header for accept-encoding: xpress
succeeded
2004-08-26 10:03:55+0200 1820 2a0 SendRequest failed with hr = 80072ee7.
</example>

I have seen cases in the past where Accept-encoding was corrupted
somehow, one suspect was the user's firewall. In each case it looked
as if the characters which should have been in the Accept-encoding:
list were replaced by tildes (~).

Are you sure there were no packets sent out? If you saw something
in an outbound packet like those tildes I mentioned it could be a better
clue.


HTH

Robert Aldwinckle
---


>
> http://v5.windowsupdate.microsoft.co...or=-2145107924
>
> The fact that the same machine (with-out firewall client using the ISA as
> proxy server) runs through the same set firewall rules (I think) but is
> capable of perfoming the update scan.
>
> Any other suggestions?
>
> Regards
>
> "Torgeir Bakken (MVP)" wrote:
>
>> LndK wrote:
>>
>> > Hi
>> >
>> > Like many oithers our site cannot scan for updates on v5.windowsupdate.
>> > We keep getting error 0x8024402C.
>> >
>> > The only way is to uninstall the firewall client and instruct the browser to
>> > use the ISA server as Proxy (port 8080). This way we can successfully scan
>> > for updates - BUT WE NEED THE FIREWALL CLIENT in out set-up.
>> >
>> > What can I do to overcome this anoying problem?
>> >
>> > Best regrds
>> >
>>
>>
>> Hi
>>
>> In the FW configuration, open TCP/IP 443 in both directions
>> for this process and see if it helps:
>>
>> %windir%\system32\svchost.exe
>>
>>
>> --
>> 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
>>

If you have, ISA Firewall installed and have installed recent Service
packs for ISA, You will need to do a repair on the ISA firewall client
from the workstation, in add/remove programs. I had this same issue,
once I did the repair Microsoft suggests after the service packs are
applied to ISA 2000 everything runs awesome! good luck!

Steven Church






"LndK" <> wrote in message news:<9CDFCC32-4396-4931-A7F1->...
> Hi,
>
> I have tried that with-out any luck. My feeling is that it is my own PC that
> prevents contact to v5. because no packets are send during the scan except
> from the final
> reporting.
>
> http://v5.windowsupdate.microsoft.co...or=-2145107924
>
> The fact that the same machine (with-out firewall client using the ISA as
> proxy server) runs through the same set firewall rules (I think) but is
> capable of perfoming the update scan.
>
> Any other suggestions?
>
> Regards
>
> "Torgeir Bakken (MVP)" wrote:
>
> > LndK wrote:
> >
> > > Hi
> > >
> > > Like many oithers our site cannot scan for updates on v5.windowsupdate.
> > > We keep getting error 0x8024402C.
> > >
> > > The only way is to uninstall the firewall client and instruct the browser to
> > > use the ISA server as Proxy (port 8080). This way we can successfully scan
> > > for updates - BUT WE NEED THE FIREWALL CLIENT in out set-up.
> > >
> > > What can I do to overcome this anoying problem?
> > >
> > > Best regrds
> > >
> >
> >
> > Hi
> >
> > In the FW configuration, open TCP/IP 443 in both directions
> > for this process and see if it helps:
> >
> > %windir%\system32\svchost.exe
> >
> >
> > --
> > 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
> >