Thanks for this! I kept getting error reports from my firewall software about
Windows Update continually trying to go direct from behind my Squid proxy.


It's this type of "hidden" information that is an example of
quintessential dislike for working with MS OS's.  It is on my
machine and dated Aug 18, 2001, so I'm guessing it was
released with the original XP, but do they say *anything*
about it in their documentation?  At least the tool is
self documenting enough...

The output of the program on my machine was:

C:\> proxycfg
Current WinHTTP proxy settings under

 HKEY_LOCAL_MACHINE\
   SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\Connections\
     WinHttpSettings :

   Flags        = PROXY_TYPE_DIRECT
   Proxy Server = -not set-
   Bypass List  = -not set-

C:\> proxycfg -h

WinHTTP Proxy Configuration Tool

usage:

   proxycfg -?  : to view help information

   proxycfg     : to view current winhttp proxy settings (in HKLM)

   proxycfg [-d] [-p <server-name> [<bypass-list>]]

       -d : set PROXY_TYPE_DIRECT
       -p : set PROXY_TYPE_PROXY, proxy server, and optional bypass list

proxycfg -u : to set winhttp proxy settings
from current user's manual setting (in HKCU)
---------
I used "-u" and it seems to have created the correct entries. The entry in the
registry under Connections, "WinHttpSettings", is one long binary blob so it's
not something that can be easily edited or interpreted by hand.


Thanks!
Linda

Kevin wrote:

Yes, there is a fix.

While "Windows Automatic Update" on WinXP doesn't inherently pick
up proxy settings for IE from the Control Panel, there is a command-line
tool called "proxycfg" (installed via SP2?) which can force WAU to use
a proxy.  Apparently there is also a way to set the proxy for WAU via
directly manipulating the registry, if you're cool with that.

Kevin Kadow


Reply via email to