From: "Rich" 

This is a multi-part message in MIME format.

------=_NextPart_000_00FC_01C57516.A0473A40
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

   proxycfg sets the proxy settings for WinHTTP which is used by the WU =
components.  I think this is a variant of the issue I described.  What = is
different is that if you have per-user settings why they are not = being
used.  WU may have changed since I experienced an issue with this = a year
ago.

Rich

  "John Beckett"  wrote in message =
news:l1fcb1t743l3tj3oh7a128kn1la48h8dqb{at}4ax.com...
  On Wed, 15 Jun 2005 22:19:19 -0700, "Rich"  wrote:
  > If I had to guess I would speculate that there is a discrepancy =
between the
  > per-machine and per-user proxy settings.

  Reminder:
  XP SP2 with proxy server set for current user.
  Windows Update fails to download updates (netstat show direct
  connection attempts).

  I carefully exported the ProxyEnable and ProxyServer registry settings
  from HKCU, and imported them to the same place under HKLM (I have some
  old notes telling me that this worked at one time, although I suppose
  I should be using Group Policy - Internet Explorer Maintenance).
  Windows Update no change.
  Reboot. WU no change.

  Google Groups showed acres of agony with similar stories and all sorts
  of weird and wonderful remedies.

  It appears something called proxycfg is what I need, but I came across
  a message with several "it worked" follow-ups so I thought I would try
  it. I did the following, and WU worked:

  net stop wuauserv
  Delete contents of C:\WINDOWS\SoftwareDistribution folder.
  net start wuauserv

  I still had the registry settings under HKLM, so I don't know if they
  were relevant.

  After Windows Update worked and rebooted, I thought I would see what
  proxycfg is about. Sure enough, it tells me that WinHttpSettings are:
     Direct access (no proxy server).

  I should use the -p option (you need Google for the syntax) to fix
  this, but I will leave it alone for now.

  As several newsgroups posters whined, it sure would be easier if there
  was some documentation (ONE manual on this topic would be nice!).

  John

------=_NextPart_000_00FC_01C57516.A0473A40
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable








   proxycfg
sets the proxy =
settings for=20
WinHTTP which is used by the WU components.  I think this
is a = variant=20
of the issue I described.  What is different is that if you have =
per-user=20
settings why they are not being used.  WU may have changed since
I=20 experienced an issue with this a year ago.
 
Rich
 

  "John Beckett" <FirstLast{at}compuserve.com.om=">mailto:FirstLast{at}compuserve.com.omit">FirstLast{at}compuserve.com.om=
it>=20
  wrote in message news:l1fcb1t743l=
3tj3oh7a128kn1la48h8dqb{at}4ax.com...On=20
  Wed, 15 Jun 2005 22:19:19 -0700, "Rich" <{at}>
wrote:> If I =
had to=20
  guess I would speculate that there is a discrepancy between =
the>=20
  per-machine and per-user proxy
settings.Reminder:XP SP2 =
with proxy=20
  server set for current user.Windows Update fails to download =
updates=20
  (netstat show directconnection attempts).I
carefully =
exported the=20
  ProxyEnable and ProxyServer registry settingsfrom HKCU, and =
imported them=20
  to the same place under HKLM (I have someold notes telling me that =
this=20
  worked at one time, although I supposeI should be using Group =
Policy -=20
  Internet Explorer Maintenance).Windows Update no =
change.Reboot. WU no=20
  change.Google Groups showed acres of agony with similar =
stories and=20
  all sortsof weird and wonderful remedies.It appears =
something=20
  called proxycfg is what I need, but I came acrossa message with =
several=20
  "it worked" follow-ups so I thought I would tryit. I did the =
following,=20
  and WU worked:net stop wuauservDelete contents of=20
  C:\WINDOWS\SoftwareDistribution folder.net start
wuauservI =
still=20
  had the registry settings under HKLM, so I don't know if theywere=20
  relevant.After Windows Update worked and rebooted, I
thought I =
would=20
  see whatproxycfg is about. Sure enough, it tells me that =
WinHttpSettings=20
  are:   Direct access (no proxy
server).I should =
use the=20
  -p option (you need Google for the syntax) to fixthis, but I will =
leave it=20
  alone for now.As several newsgroups posters whined, it sure =
would be=20
  easier if therewas some documentation (ONE manual on this topic =
would be=20
 
nice!).John

------=_NextPart_000_00FC_01C57516.A0473A40--

--- BBBS/NT v4.01 Flag-5