For the people reporting "storms" and other problems when clients run Windows Update, can you include details on the version of windows running on the client, and also on how the client is configured to talk to the proxy? (transparent, explicit settings, etc). I have squid (and NetApp) caches with hundreds of windows desktops behind them, and do not see this problem. The difference here may be that very few of these clients have upgraded to XP, and are configured to use Proxy Automatic Configuration (PAC) scripts to choose what traffic goes via Squid (all non-ssl traffic to *.(com|net|org) does go to the cache). On 5/5/05, dev singh <dev.pratap@xxxxxxxxx> wrote: > Can u plz tell what configuration are to be made on the client to get > windows update working . I've never had any problems with Windows Update when manually updating (clicking on the link), with the traffic going via squid. Always worked, never caused a "storm" or any other network issues. There are known issues where the automatic update feature may not be able to make requests out to the Internet at all if you are using a configured proxy server (not transparency, but setting the proxy server and port in control panel, and or using PAC). Kevin Kadow
