Topic: Windows Update - STILL!

[paulmancan2]

I'm really surprised no one has come accross this problem.

I find that no clients (fresh installs of XP SP2) are able to use Windows Update behind my SME 5.6U6 box UNLESS I ENABLE SQUID PROXY!

With SQUID enabled everything works just fine.

If I disable it (as I do by default) WU continually fails. The log suggests:

SendRequest failed with hr = 80072efd. Proxy List used: <proxy.of.com:3128> Bypass List used : <(null)>

Now I know that the temptation is to assume that this is a client problem, but it cannot be. These are clean installed workstations and there are no proxy settings configured in IE.

Thanks for any help!

P.S. If I remove the SME box and put any cheapo harware router in it's place, WU works just fine!

[Appesteijn]

Hi,

I'm runiing a 5.6U6 box with Squid disabled and my WU works fine. I had some problems with clients, who weren't able to update, but my guess was that it was the DNS-server on the SME. Because when I didn't used the DHCP and gave my clients a manual ip and dns-servers of my ISP, it worked fine.

[swats]

Paulmancan2,

I just ran into this problem today and thought I would share the solution with you (or at least what worked for me.)

Windows auto update attempts to locate an auto proxy server to determine the proxy settings it should use.  If no auto proxy server is found, it assumes no proxy.  It completely ignores the proxy settings in IE.  Because my installation uses a proxy, I had to set the proxy in the registry key that auto update uses.  Following is how to check it and set it if needed:

To EXAMINE the proxy settings used by auto update:
C:> proxycfg

To DELETE all proxy settings in this registry key:
C:> proxycfg -d

To SET a proxy for autoupdate:
C:> proxycfg -p your-proxy-goes-here.com:port#

I recommend that if this approach is for you, delete previous settings before setting new ones.

Also note that you must stop the auto update service and restart it before the changes take place.  The whole sequence would look like this:

To STOP the auto update service:
C:> net stop wuauserv
C:> proxycfg -d
C:> proxycfg -p thisismyproxy:8080
C:> net start wuauserv

By running SQUID, you're supplying a proxy for auto update to use.  

Hope this helps you and any others that may experience the same issue.

[CharlieBrady]

I'm really surprised no one has come accross this problem.

I find that no clients (fresh installs of XP SP2) are able to use Windows Update behind my SME 5.6U6 box UNLESS I ENABLE SQUID PROXY!

With SQUID enabled everything works just fine.

Why have you disabled SQUID?

The server has various ways to advertise that it is equipped with a proxy (wpad/proxy.pac). If you disable squid, you'll need to disable those advertisements as well.

[girkers]

I don't believe this to be true, as my Windows Update does not work if I have my proxy set in IE.  Whereas if I turn off the proxy it works fine.

I have set the settings as suggested earlier and this may no difference either way.

Proxy on - Don't work
Proxy off - Works.

I can post the squid log error messages if anyone is interested.

[paulmancan2]

Interesting replies.

Charlie I disable SQUID just because I don't see any use for it or benefit. It does not provide a performance benefit in my environment and I am just in the habit of disabling things that I don't use.

So from what you are saying, simply disabling the service is problematic in itself.

Thanks again and for any further info about what is going on!