This may be related to this old post here: http://www.astaro.org/beta-versions/...ophos-com.html
Anyway, tinkered with having a client using another proxy (not the Beta UTM, another ASG in this case, but I feel it would apply to any mobile worker behind any other proxy) as configured in IE and as the system proxy (on Vista, used netsh winhttp import proxy function to set this), with a firewall configuration that does not allow direct outbound traffic on port 80 or 443 (all web traffic has to go through the proxy), proxy not operating in transparent mode... found that while I could install the Endpoint client, it could not update, as it was trying to go directly to d3.sophosupd.com ... if I look at the client settings, there does appear to be a place to enter proxy information, but it is unconfigurable, even with tamper protection disabled.
This could potentially be a problem for remote or local users behind a proxy and firewall that does not have a specially configured exception for the sophos update site... is there a fix for this?
Anyway, tinkered with having a client using another proxy (not the Beta UTM, another ASG in this case, but I feel it would apply to any mobile worker behind any other proxy) as configured in IE and as the system proxy (on Vista, used netsh winhttp import proxy function to set this), with a firewall configuration that does not allow direct outbound traffic on port 80 or 443 (all web traffic has to go through the proxy), proxy not operating in transparent mode... found that while I could install the Endpoint client, it could not update, as it was trying to go directly to d3.sophosupd.com ... if I look at the client settings, there does appear to be a place to enter proxy information, but it is unconfigurable, even with tamper protection disabled.
This could potentially be a problem for remote or local users behind a proxy and firewall that does not have a specially configured exception for the sophos update site... is there a fix for this?