Proxy Authentication Required

[Esteban Mitjavila]

Hi all:

I have installed WSUS in Windows Server 2003. I have configured proxy
options in WSUS configuration with username/password because is required, and
the basic authentication option checked.

I started the first synchronization and all ok. After that I have approved 3
hotfixes, and when WSUS start download this hotfixes, I received an error in
the Event Viewer.

Event ID: 364
"Content file download failed. Reason: Proxy authentication is required.
Source File:
/msdownload/update/v3-19990518/cabpool/windowsserver2003.windowsxp-kb908519-x64-enu_54be6eb969704ef63587360990d0e888171844fa.exe
Destination File:
c:\WSUS\WsusContent\FA\54BE6EB969704EF63587360990D0E888171844FA.exe."

It seems that I need to change the username and password used to
authenticate proxy. But if I try to download directly using Internet Explorer
with the same proxy/username/password I can download it correctly.

I think that the problem are BITS and the authentication. I have tried to
change the option Foreground download, but the result is the same.

The SoftwareDistribution.log file shows this:

2006-01-25 16:08:58.447
UTC Error wsusservice.232 ContentSyncAgent.JobError Download error:
http://au.download.windowsupdate.com/msdownload/update/v3-19990518/cabpool/windows2000-kb908519-x86-enu_99d7239e2b5b0ec6523b4c31e5d7509aba15dade.exe
failed in download: (-2145844841) Proxy authentication is required.

Anyone has any ideas to help me?

Thanks in advance.

Esteban.

[Lawrence Garvin (MVP)]

Esteban, use 'proxycfg -u' to clone your IE proxy configuration settings to
WinHTTP.

That should resolve your issue, if IE is working correctly.

"Esteban Mitjavila" <EstebanM...@discussions.microsoft.com> wrote in
message news:5BEA10B6-6ABE-4C4E...@microsoft.com...

[Esteban Mitjavila]

Thanks Lawrence for your fast response.

Unaffortunately this command does not resolve the problem. It's true that
before executing this command the proxy configuration of WinHTTP are clear.
Now the proxy configuration are correct, but the problem persists.

I think that the problem is in BITS, that do not send the credentials to the
proxy server. Looking at the WSUS log file, I don't find any line that the
WSUS is sendind the authentication credentials to BITS.

Using bitsadmin tool I have this response:

BITSADMIN version 2.0 [ 6.6.2600.2180 ]
BITS administration utility.
(C) Copyright 2000-2004 Microsoft Corp.

GUID: {344A661F-4920-405D-9D76-297578B5CAB1} DISPLAY:
36c0c09d-ace7-4b84-9545-66
38ba4625f3
TYPE: DOWNLOAD STATE: ERROR OWNER: NT AUTHORITY\NETWORK SERVICE
PRIORITY: HIGH FILES: 0 / 1 BYTES: 12868 / 599280
CREATION TIME: 27/01/2006 10:15:01 MODIFICATION TIME: 27/01/2006 10:15:35
COMPLETION TIME: UNKNOWN ACL FLAGS:
NOTIFY INTERFACE: UNREGISTERED NOTIFICATION FLAGS: 3
RETRY DELAY: 600 NO PROGRESS TIMEOUT: 86400 ERROR COUNT: 1
PROXY USAGE: OVERRIDE PROXY LIST: proxy:8080 PROXY BYPASS LIST: <lo
cal>
ERROR FILE:
http://au.download.windowsupdate.com/msdownload/update/v3-1999051
8/cabpool/windowsserver2003-kb908519-x86-enu_73af495c0bed118f4396cccd0ac2fe65186
13da5.exe ->
c:\WSUS\WsusContent\A5\73AF495C0BED118F4396CCCD0AC2FE6518613DA5.exe

ERROR CODE: 0x80190197 - Proxy authentication is required.
ERROR CONTEXT: 0x00000005 - The error occurred while the remote file was
being p
rocessed.
DESCRIPTION: SUSFile
JOB FILES:
12868 / 599280 WORKING
http://au.download.windowsupdate.com/msdownload/u
pdate/v3-19990518/cabpool/windowsserver2003-kb908519-x86-enu_73af495c0bed118f439
6cccd0ac2fe6518613da5.exe ->
c:\WSUS\WsusContent\A5\73AF495C0BED118F4396CCCD0AC2
FE6518613DA5.exe
NOTIFICATION COMMAND LINE: none

Listed 1 job(s).

If you have more ideas, I'll be very very agree.

Thanks in advance.

Esteban.

[Esteban Mitjavila]

Now, I'm going crazy.

After execute "proxycfg -p proxy:8080" I was able to download successfully 3
of 7 hotfixes approved, but now if I retry to download this I get the same
error: "Proxy Authentication Requiered".

Esteban.

[Lawrence Garvin (MVP)]

I agree, it looks like the proxy server is not getting any authentication
credentials.

Did you configure the Synchronization Options page in the WSUS Admin Console
to provide the authentication credentials, as needed? Also, if necessary, be
sure to mark the checkbox to use "basic authentication" if your proxy does
not support NTLM authentication.

"Esteban Mitjavila" <EstebanM...@discussions.microsoft.com> wrote in

message news:EEAE4684-9276-4D80...@microsoft.com...

[Esteban Mitjavila]

Thanks again Lawrence.

The checkbox to "use basic authentication" is checked because the proxy does
not support NTLM authentication.

Ok, I have passed to the next level ;-) .... Ethereal.

Looking the trace obtained, we can see this sequence:

1.- BITS request for proxy server
2.- Proxy server ACK the request
3.- BITS request for URL (the hotfix)
4.- Proxy server denies the request (error 407 - Proxy Auth Req)
5.- BITS reset de connection
6.- BITS request for URL (the hotfix) usign credentials (only a range of the
file)
7.- Proxy server ACK the request and serves the content required.
8.- Proxy server sends a Partial Content (HTTP 1.1 206)

This sequence repeats until the fifth request. At this time when the Proxy
server request auth, BITS reset the connection and finish download with an
error code 407. Why BITS does not continue downloading?.

I have tested the same machine using another Proxy Server (ISA Server) and
it works Ok.

It's clear for me... the problem is Proxy Server, but I don't know why.

I don't know what kind of proxy server are using (can hear bizarre, but it's
true. It's a long history). The responsible is out of the office, and the
proxy server is out of our country.

If you have more ideas to test while I'm trying to discover what kind of
proxy are using, please tell me.

Thank you very very very much for your patience and for your responses.

Regards.

[Lawrence Garvin]

> I have tested the same machine using another Proxy Server (ISA Server) and
> it works Ok.

This is usually an indication that the fault exists in the proxy server that
is not cooperating.

Since you've demonstrated that the WSUS server works with a -different-
proxy server, we can conclude that the issue is not the WSUS server.

Unfortunately, troubleshooting a proxy server is beyond the scope of this
forum -- especially if you don't have the authorization to access and
administer it directly.

"Esteban Mitjavila" <EstebanM...@discussions.microsoft.com> wrote in

message news:1ED80F16-D883-4725...@microsoft.com...