I've just noticed today that a manual check for updates in Windows Update on two of our computers at home, connected to my ASG v8.003 gateway, no longer seems to work. They both chuck out error code 80072F8F [Windows Update encountered an unknown error]. The two computers in question run Windows Vista Home Premium 32-bit [Mum's] and Windows 7 Ultimate 64-bit [mine]. I've narrowed down the culprit to the HTTP/S proxy feature under Web Security, which is weird because I know that there is an exception which presumably was added upon initial installation/setup. I can only get it to work if I disable the proxy first then click the 'Check for updates' option, so I would assume that automated checks are also affected. I haven't fiddled with any of the preset exceptions in any way, I've only added my own exception to stop SSL/anti-virus scanning for the static IP address used at my workplace which shouldn't have any effect on this.
This is an extract from the 'Content Filter (HTTP/S)' log from the last time I checked for Windows updates on the Vista machine:
2010:11:20-23:41:13 pph httpproxy[16821]: id="0001" severity="info" sys="SecureWeb" sub="http" name="http access" action="pass" method="HEAD" srcip="23.9.87.101" dstip="213.199.149.88" user="" statuscode="200" cached="0" profile="REF_DefaultHTTPProfile (Default Proxy)" filteraction="REF_DefaultHTTPCFFAction (Default content filter action)" size="0" time="55 ms" request="0xa35528b8" url="download.windowsupdate.com/.../muv4wuredir.cab
2010:11:20-23:41:13 pph httpproxy[16821]: id="0001" severity="info" sys="SecureWeb" sub="http" name="http access" action="pass" method="HEAD" srcip="23.9.87.101" dstip="213.199.149.88" user="" statuscode="200" cached="0" profile="REF_DefaultHTTPProfile (Default Proxy)" filteraction="REF_DefaultHTTPCFFAction (Default content filter action)" size="0" time="29 ms" request="0xa35528b8" url="download.windowsupdate.com/.../muauth.cab
2010:11:20-23:41:14 pph httpproxy[16821]: id="0001" severity="info" sys="SecureWeb" sub="http" name="http access" action="pass" method="HEAD" srcip="23.9.87.101" dstip="213.199.149.88" user="" statuscode="200" cached="0" profile="REF_DefaultHTTPProfile (Default Proxy)" filteraction="REF_DefaultHTTPCFFAction (Default content filter action)" size="0" time="27 ms" request="0xa35528b8" url="download.windowsupdate.com/.../muv4wuredir.cab
2010:11:20-23:41:14 pph httpproxy[16821]: id="0001" severity="info" sys="SecureWeb" sub="http" name="http access" action="pass" method="HEAD" srcip="23.9.87.101" dstip="65.55.27.219" user="" statuscode="200" cached="0" profile="REF_DefaultHTTPProfile (Default Proxy)" filteraction="REF_DefaultHTTPCFFAction (Default content filter action)" size="0" time="343 ms" request="0xa35bdc00" url="www.update.microsoft.com/.../wuident.cab
2010:11:20-23:41:14 pph httpproxy[16821]: id="0001" severity="info" sys="SecureWeb" sub="http" name="http access" action="pass" method="HEAD" srcip="23.9.87.101" dstip="213.199.149.88" user="" statuscode="200" cached="0" profile="REF_DefaultHTTPProfile (Default Proxy)" filteraction="REF_DefaultHTTPCFFAction (Default content filter action)" size="0" time="30 ms" request="0xa35528b8" url="download.windowsupdate.com/.../wsus3setup.cab
2010:11:20-23:41:24 pph httpproxy[16821]: id="0001" severity="info" sys="SecureWeb" sub="http" name="http access" action="pass" method="HEAD" srcip="23.9.87.101" dstip="213.199.149.88" user="" statuscode="200" cached="0" profile="REF_DefaultHTTPProfile (Default Proxy)" filteraction="REF_DefaultHTTPCFFAction (Default content filter action)" size="0" time="53 ms" request="0xa35528b8" url="download.windowsupdate.com/.../muv4muredir.cab
Having looked up what HTTP 200 is, this all looks pretty standard to me. Does anyone know if Microsoft has changed their update servers in any way, or if this might be a bug with v8.003, or is there something else I should look into?
Any help would be appreciated. Thanks.
Regards,
Jon.
This thread was automatically locked due to age.
Quote