Noel Paton wrote:
> (which is exactly the point that the KB makes, and tells you how to get
> around!)
>
>
>
> --
> Noel Paton (MS-MVP 2002-2005, Windows)
>
> Nil Carborundum Illegitemi
> http://www.btinternet.com/~winnoel/millsrpch.htm
>
> http://tinyurl.com/6oztj
>
> Please read http://dts-l.org/goodpost.htm on how to post messages to NG's
>
> "wtf" <> wrote in message
> news:AE08EF81-F488-4D26-A1E0-...
> > Hate to say it, but this is not true. There are ways to make it work.
> > Consult
> > the KB.
> >
> > All the best
> > --
> > H. Eberhard
> > B&E Consulting
> > Germany
> >
> >
> > "PA Bear" wrote:
> >
> >> See:
> >>
> >> You cannot download updates when you access the Windows Update Web site
> >> from
> >> a Windows XP-based computer that is behind a firewall or a proxy server:
> >> http://support.microsoft.com/default...b;en-us;896226
> >>
> >> --
> >> ~Robear Dyer (PA Bear)
> >> MS MVP-Windows (IE/OE) & Security
> >>
> >> Gillian wrote:
> >> > Hi There
> >> >
> >> > I am having similar problems to others but with a difference. Since V6
> >> > has
> >> > come out of Windows Update on some servers in my network the download
> >> > fails
> >> > and in the windowsupdate.log I get :
> >> >
> >> > 2005-07-19 17:15:53 1000 184 DnldMgr WARNING: Download job failed
> >> > because
> >> > of
> >> > proxy auth or server auth.
> >> > 2005-07-19 17:15:53 1000 184 DnldMgr Error 0x80244017 occurred while
> >> > downloading update; notifying dependent calls.
> >> >
> >> > on a particular machine I then manually installed the update for BITS
> >> > and
> >> > WINHTTP (KB842773) with the hopes that it might help, now when I go to
> >> > the
> >> > windows update site it is stuck on the screen saying "checking for the
> >> > latest updates", and I can now see in the Windowsupdate.log:
> >> >
> >> > 2005-07-19 17:25:10 1000 494 Misc WARNING: WinHttp:
> >> > SendRequestToServerForFileInformation failed with 0x80190191
> >> > 2005-07-19 17:25:10 1000 494 Misc WARNING: WinHttp:
> >> > ShouldFileBeDownloaded
> >> > failed with 0x80190191
> >> >
> >> > However, I have other Windows 2003 servers where the dowloads and
> >> > updates
> >> > work without a problem???
> >> >
> >> > I have added http://*.windowsupdate.microsoft.com
> >> > http://download.windowsupdate.com
> >> > http://update.microsoft.com
> >> > https://*.windowsupdate.microsoft.com
> >> > https://windowsupdate.microsoft.com
> >> >
> >> > to my Trusted list.
> >> >
> >> > I am using NetIQ Webmarshal as a proxy and the user account I am using
> >> > has
> >> > rights to download and browse anything.
> >> >
> >> > Any help would be appreciated.
> >> >
> >> > Many Thanks
> >> >
> >> > Gillian
> >>
> >>
I'm having this problem with a newly installed Windows Server 2003 SP1
box, an older Windows Server 2003 install (not sp1), and an XP SP2
install.
Does anyone have any further information about this issue? I've just
spent the last 4 hours googling around trying to find a resolution, but
I haven't had any luck so far. I've tried everything in the above link
to no avail.
My traffic is being routed through tinyproxy for http traffic and a
socks proxy for everything else. Since we've implemented this setup,
windowsupdate v6 is the first app that I've had problems with. I can
even run WU v4 on W2K Pro with no problems.
I've figured out that the windows update service isn't actually using
the proxy. I deduceded this by using netstat -an and also capturing
packets using ethereal. It's attemping to go directly port 443 (https)
at the following addresses (which update.microsoft.com resolve to) :
64.4.21.93
207.46.157.30
What really gets me with this is that in the WindowsUpdate.log file I
have this (note: I've replaced all IP addresses w/ *):
+ ServiceId = {9482F4B4-E343-43B6-B170-9A65BC822C77}, Server URL =
https://update.microsoft.com/v6/Clie...ce/client.asmx
WARNING: Send failed with hr = 80072ef1.
WARNING: SendRequest failed with hr = 80072ef1. Proxy List used:
<http=*.*.*.*:*;socks=*.*.*.*:*> Bypass List used : <*;*;*;*.*;<local>>
Auth Schemes used : <>
WARNING: Sync of Updates: 0x8024000b
WARNING: Exit code = 0x8024000B
So it says, "Hey I'm going to use these servers for proxies," but then
it never does. What is the deal with this? From my ethereal output, I
know for a fact it never even attempts to go to my proxy server.
If anyone has any insight on this it would be much appreciated. I'm
very close to just living with this and manually downloading the
updates I need.
Thanks
Similar Threads
Linear Mode
