Error code 0x8024400A

We're setting up a network with a firewall/caching device. All the client
machines were purchased used at one source (probably a business replacing old
machines).

Without the firewall, the Windows XP clients seem to have no problems
getting Windows updates. With the firewall (IPCop), the clients try to get
updates, run slow and finally come up with an error 0x8024400A.

I don't see any reference to this error code except in conjunction with
WSUS. Could these client machines once been set up to use WSUS to get
updates and, once we put them on a network with the IPCop firewall/caching
machine, they believe they ought to be looking for a WSUS server, don’t find
it, and then abort?

Am I following a theory that doen't make sense? Any suggestions on how to
determine and/or fix this?

Thanks.

Jon

 

Since the systems can update when IPCop is disabled then they are set to
obtain updates from the Microsoft update servers, not a local WSUS server.

Suggest you post to the IPCop General-software forum for assistance:



MowGreen
===============
*-343-* FDNY
Never Forgotten
===============

banthecheck.com
"Security updates should *never* have *non-security content* prechecked"


Jon L wrote:
<!--coloro:blue--><span style="color:blue <!--/coloro-->
> We're setting up a network with a firewall/caching device. All the client
> machines were purchased used at one source (probably a business replacing old
> machines).
>
> Without the firewall, the Windows XP clients seem to have no problems
> getting Windows updates. With the firewall (IPCop), the clients try to get
> updates, run slow and finally come up with an error 0x8024400A.
>
> I don't see any reference to this error code except in conjunction with
> WSUS. Could these client machines once been set up to use WSUS to get
> updates and, once we put them on a network with the IPCop firewall/caching
> machine, they believe they ought to be looking for a WSUS server, don’t find
> it, and then abort?
>
> Am I following a theory that doen't make sense? Any suggestions on how to
> determine and/or fix this?
>
> Thanks.
>
> Jon
> <!--colorc--><!--/colorc-->

 

Hello Jon,

Maybe the following aяticle would be worth a look:



Read *carefully* - do not just skim the page and start following steps.


Please let us know what fixes the problem or if the pяoblem remains
-=-


Good luck


Ǝиçεl
◕‿◕
-=-


"Jon L" wrote:
<!--coloro:blue--><span style="color:blue <!--/coloro-->
> We're setting up a network with a firewall/caching device. All the client
> machines were purchased used at one source (probably a business replacing old
> machines).
>
> Without the firewall, the Windows XP clients seem to have no problems
> getting Windows updates. With the firewall (IPCop), the clients try to get
> updates, run slow and finally come up with an error 0x8024400A.
>
> I don't see any reference to this error code except in conjunction with
> WSUS. Could these client machines once been set up to use WSUS to get
> updates and, once we put them on a network with the IPCop firewall/caching
> machine, they believe they ought to be looking for a WSUS server, don’t find
> it, and then abort?
>
> Am I following a theory that doen't make sense? Any suggestions on how to
> determine and/or fix this?
>
> Thanks.
>
> Jon
> <!--colorc--><!--/colorc-->