Windows Update using WinHTTP with authenticating proxies

Used proxycfg tool with -u switch to set WinHTTP proxy settings to the
browser's manual proxy setting.

After clicking Custom link on Windows Update page an error page is received.
The listing of updates failed.

I am using an authenticating proxy and presumed authentication failed.

Used WinHTPtraceCfg tool to verify my assumption.

<<<<-------- HTTP stream follows below
----------------------------------------------->>>>
22:50:18.613 ::*000000a* :: HTTP/1.1 407 Proxy Authentication Required
22:50:18.613 ::*000000a* :: Proxy-Authenticate: BASIC realm="Client Public
Internet Access Proxy"
22:50:18.613 ::*000000a* :: Cache-Control: no-cache
22:50:18.613 ::*000000a* :: Pragma: no-cache
22:50:18.613 ::*000000a* :: Content-Type: text/html; charset=utf-8
22:50:18.613 ::*000000a* :: Proxy-Connection: close
22:50:18.613 ::*000000a* :: Set-Cookie: BCSI-CSC0552F45=2; Path=/
22:50:18.613 ::*000000a* :: Connection: close
22:50:18.613 ::*000000a* :: Content-Length: 858
22:50:18.613 ::*000000a* ::
22:50:18.613 ::*000000a* ::
22:50:18.613 ::*000000a* :: <<<<-------- End
----------------------------------------------->>>>
22:50:18.613 ::*000000a* :: "www.update.microsoft.com" NOT resolved
22:50:18.613 ::*000000a* :: WinHttpSendRequest: error 12007
[ERROR_WINHTTP_NAME_NOT_RESOLVED]
22:50:18.633 ::*000000a* :: Using proxy server: my_proxy.com:80
22:50:18.683 ::*000000a* :: sending data:
22:50:18.693 ::*000000a* :: 231 (0xe7) bytes

Is there a configuration paramter for entering authentication credentials?

--
George
Internet Administrator

Hello,

Are you using ISA as your proxy server? If so, please check out the article
below

This KB basically has a list of URL’s that you configure ISA to allow
anonymous access to the Windows Update Site
http://support.microsoft.com/kb/885819

Diana Smith [MSFT] <diasmith@hotmail.com>
CSS Security Team

This posting is provided "AS IS" with no warranties, and confers no rights.



"George" <George@discussions.microsoft.com> wrote in message
newsC7C39BC-69B7-402C-B9BB-B56181CA216B@microsoft.com...
> Used proxycfg tool with -u switch to set WinHTTP proxy settings to the
> browser's manual proxy setting.
>
> After clicking Custom link on Windows Update page an error page is
> received.
> The listing of updates failed.
>
> I am using an authenticating proxy and presumed authentication failed.
>
> Used WinHTPtraceCfg tool to verify my assumption.
>
> <<<<-------- HTTP stream follows below
> ----------------------------------------------->>>>
> 22:50:18.613 ::*000000a* :: HTTP/1.1 407 Proxy Authentication Required
> 22:50:18.613 ::*000000a* :: Proxy-Authenticate: BASIC realm="Client Public
> Internet Access Proxy"
> 22:50:18.613 ::*000000a* :: Cache-Control: no-cache
> 22:50:18.613 ::*000000a* :: Pragma: no-cache
> 22:50:18.613 ::*000000a* :: Content-Type: text/html; charset=utf-8
> 22:50:18.613 ::*000000a* :: Proxy-Connection: close
> 22:50:18.613 ::*000000a* :: Set-Cookie: BCSI-CSC0552F45=2; Path=/
> 22:50:18.613 ::*000000a* :: Connection: close
> 22:50:18.613 ::*000000a* :: Content-Length: 858
> 22:50:18.613 ::*000000a* ::
> 22:50:18.613 ::*000000a* ::
> 22:50:18.613 ::*000000a* :: <<<<-------- End
> ----------------------------------------------->>>>
> 22:50:18.613 ::*000000a* :: "www.update.microsoft.com" NOT resolved
> 22:50:18.613 ::*000000a* :: WinHttpSendRequest: error 12007
> [ERROR_WINHTTP_NAME_NOT_RESOLVED]
> 22:50:18.633 ::*000000a* :: Using proxy server: my_proxy.com:80
> 22:50:18.683 ::*000000a* :: sending data:
> 22:50:18.693 ::*000000a* :: 231 (0xe7) bytes
>
> Is there a configuration paramter for entering authentication credentials?
>
> --
> George
> Internet Administrator

Hi Diana,

Thank you for you reply and suggestion!!

I would do what you suggested but unfortunately I do not have
addministrative access to the proxies.


--
George
Internet Administrator


"Diana" wrote:

> Hello,
>
> Are you using ISA as your proxy server? If so, please check out the article
> below
>
> This KB basically has a list of URL’s that you configure ISA to allow
> anonymous access to the Windows Update Site
> http://support.microsoft.com/kb/885819
>
> Diana Smith [MSFT] <diasmith@hotmail.com>
> CSS Security Team
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
>
> "George" <George@discussions.microsoft.com> wrote in message
> newsC7C39BC-69B7-402C-B9BB-B56181CA216B@microsoft.com...
> > Used proxycfg tool with -u switch to set WinHTTP proxy settings to the
> > browser's manual proxy setting.
> >
> > After clicking Custom link on Windows Update page an error page is
> > received.
> > The listing of updates failed.
> >
> > I am using an authenticating proxy and presumed authentication failed.
> >
> > Used WinHTPtraceCfg tool to verify my assumption.
> >
> > <<<<-------- HTTP stream follows below
> > ----------------------------------------------->>>>
> > 22:50:18.613 ::*000000a* :: HTTP/1.1 407 Proxy Authentication Required
> > 22:50:18.613 ::*000000a* :: Proxy-Authenticate: BASIC realm="Client Public
> > Internet Access Proxy"
> > 22:50:18.613 ::*000000a* :: Cache-Control: no-cache
> > 22:50:18.613 ::*000000a* :: Pragma: no-cache
> > 22:50:18.613 ::*000000a* :: Content-Type: text/html; charset=utf-8
> > 22:50:18.613 ::*000000a* :: Proxy-Connection: close
> > 22:50:18.613 ::*000000a* :: Set-Cookie: BCSI-CSC0552F45=2; Path=/
> > 22:50:18.613 ::*000000a* :: Connection: close
> > 22:50:18.613 ::*000000a* :: Content-Length: 858
> > 22:50:18.613 ::*000000a* ::
> > 22:50:18.613 ::*000000a* ::
> > 22:50:18.613 ::*000000a* :: <<<<-------- End
> > ----------------------------------------------->>>>
> > 22:50:18.613 ::*000000a* :: "www.update.microsoft.com" NOT resolved
> > 22:50:18.613 ::*000000a* :: WinHttpSendRequest: error 12007
> > [ERROR_WINHTTP_NAME_NOT_RESOLVED]
> > 22:50:18.633 ::*000000a* :: Using proxy server: my_proxy.com:80
> > 22:50:18.683 ::*000000a* :: sending data:
> > 22:50:18.693 ::*000000a* :: 231 (0xe7) bytes
> >
> > Is there a configuration paramter for entering authentication credentials?
> >
> > --
> > George
> > Internet Administrator
>

George wrote:

> Used proxycfg tool with -u switch to set WinHTTP proxy settings to the
> browser's manual proxy setting.
>
> After clicking Custom link on Windows Update page an error page is received.
> The listing of updates failed.
>
> I am using an authenticating proxy and presumed authentication failed.

My understanding is that proxycfg configures proxy settings for noninteractive
use, so I would assume it is not able to cope with authenticating proxies.

However, I can confirm that Windows Update is able to cope with authenticating
proxies, I use it occasionally in this configuration. You need to configure the
proxy for Internet Explorer in the context of the user who is performing the
update rather than using proxycfg.

If you use proxycfg -d to set noninteractive use to direct access, Windows
Update should then work. Note that there will be very long delays, I presume
this is because the Windows Update Agent is attempting to access Windows Update
directly and timing out. However once the direct access times out it will then
try using the proxy and ask for authentication.

Harry.

Hello Harry,

I did the proxycfg -d and repeated the Microsoft Update with the same error
results.

--
George
Internet Administrator


"Harry Johnston [MVP]" wrote:

> George wrote:
>
> > Used proxycfg tool with -u switch to set WinHTTP proxy settings to the
> > browser's manual proxy setting.
> >
> > After clicking Custom link on Windows Update page an error page is received.
> > The listing of updates failed.
> >
> > I am using an authenticating proxy and presumed authentication failed.
>
> My understanding is that proxycfg configures proxy settings for noninteractive
> use, so I would assume it is not able to cope with authenticating proxies.
>
> However, I can confirm that Windows Update is able to cope with authenticating
> proxies, I use it occasionally in this configuration. You need to configure the
> proxy for Internet Explorer in the context of the user who is performing the
> update rather than using proxycfg.
>
> If you use proxycfg -d to set noninteractive use to direct access, Windows
> Update should then work. Note that there will be very long delays, I presume
> this is because the Windows Update Agent is attempting to access Windows Update
> directly and timing out. However once the direct access times out it will then
> try using the proxy and ask for authentication.
>
> Harry.
>

George wrote:

> I did the proxycfg -d and repeated the Microsoft Update with the same error
> results.

Is this Windows Update or Microsoft Update? Last time I tried, I believe
Microsoft Update did *not* work through an authenticating proxy. Windows Update
does, although as I said there are long delays.

Harry.

MS update.

I was looking for verification that there has been no change.

Thanks
--
George
Internet Administrator


"Harry Johnston [MVP]" wrote:

> George wrote:
>
> > I did the proxycfg -d and repeated the Microsoft Update with the same error
> > results.
>
> Is this Windows Update or Microsoft Update? Last time I tried, I believe
> Microsoft Update did *not* work through an authenticating proxy. Windows Update
> does, although as I said there are long delays.
>
> Harry.
>