I don't know if this is a bug, but this is a fact.
After testing many times, I have found the following fact about Windows
Update and ISA 2004 FWC.
Windows update on windows XP have not the ability to use ISA 2004 Firewall
Client as the route to Internet, it only can use Secure NAT and Proxy.
If I only use Secure NAT, I can use windows update successfully.
And If I only set proxy in IE, I can use windows update successfully too,
the proxy server can be any, it can be a proxy application installed on the
same PC with windows update, or it can be ISA proxy.
But if I only use ISA server 2004 firewall client, I can reach to the webpage
http://update.microsoft.com/microsof....aspx?ln=en-us
when I click the Express button on this webpage, It will fail. But at this
time if I install a proxy application on the same computer, and set the proxy
settings in IE to point the proxy just installed, then it update
successfully. Because the windows update client control excuted by press the
"Express" button can't use FWC as route, it only have two choices, Secure NAT
and Proxy. The flow route is Windows Update use proxy application just
installed, and the proxy appliction use FWC to go to websit.
It puzzled me, windows update and ISA FWC both are the production of MS, why
Windows Update can't use FWC as route? I hope the fact is not like this.