Some W2K Clients won't Connect to WSUS

Discussion:

(too old to reply)

Andrew M

2005-12-13 11:51:02 UTC

Hi

Like a lot of the posts here I have some W2K clients which refuse to connect
to the WSUS server. All the XP clients and almost all the W2K clients so far
configured are OK.

Here is what I have done:

The failed clients are W2K SP4 with Windows Update client 2.
They are in an NT4 domain so I have set up WSUS in local group policy.
I have looked at
http://support.microsoft.com/default.aspx?scid=kb;en-us;555459&sd=rss&spid=3198
and :

We don't use proxy servers.
I have tried using raw IP address instead of domain name (although domain
name works fine for all other clients)
I have removed the two registry entries named in the above doc.
Still no resolution.
Here is an extract from windows update log file on one of the problem PCs:

2005-12-13 11:31:39 1012 3f8 AU ########### AU: Policy change processed
###########
2005-12-13 11:31:39 1012 3f8 AU # Policy changed, AU restart required = No
2005-12-13 11:31:39 1012 3f8 AU # WSUS server: http://192.168.33.84
2005-12-13 11:31:39 1012 3f8 AU # Detection frequency: 1
2005-12-13 11:31:39 1012 3f8 AU # Approval type: Pre-download notify
(Policy)
2005-12-13 11:31:39 1012 6a0 Misc WARNING: Send failed with hr = 80072efd.
2005-12-13 11:31:39 1012 6a0 Misc WARNING: SendRequest failed with hr =
80072efd. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes
used : <>
2005-12-13 11:31:39 1012 6a0 Misc WARNING: WinHttp: SendRequestUsingProxy
failed for <http://192.168.33.84/selfupdate/wuident.cab>. error 0x80072efd
2005-12-13 11:31:39 1012 6a0 Misc WARNING: WinHttp:
SendRequestToServerForFileInformation MakeRequest failed. error 0x80072efd
2005-12-13 11:31:39 1012 6a0 Misc WARNING: WinHttp:
SendRequestToServerForFileInformation failed with 0x80072efd
2005-12-13 11:31:39 1012 6a0 Misc WARNING: WinHttp: ShouldFileBeDownloaded
failed with 0x80072efd
2005-12-13 11:31:39 1012 6a0 Misc WARNING: Send failed with hr = 80072efd.
2005-12-13 11:31:39 1012 6a0 Misc WARNING: SendRequest failed with hr =
80072efd. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes
used : <>
2005-12-13 11:31:39 1012 6a0 Misc WARNING: WinHttp: SendRequestUsingProxy
failed for <http://192.168.33.84/selfupdate/wuident.cab>. error 0x80072efd
2005-12-13 11:31:39 1012 6a0 Misc WARNING: WinHttp:
SendRequestToServerForFileInformation MakeRequest failed. error 0x80072efd
2005-12-13 11:31:39 1012 6a0 Misc WARNING: WinHttp:
SendRequestToServerForFileInformation failed with 0x80072efd
2005-12-13 11:31:39 1012 6a0 Misc WARNING: WinHttp: ShouldFileBeDownloaded
failed with 0x80072efd
2005-12-13 11:31:39 1012 6a0 Misc WARNING: Send failed with hr = 80072efd.
2005-12-13 11:31:39 1012 6a0 Misc WARNING: SendRequest failed with hr =
80072efd. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes
used : <>
2005-12-13 11:31:39 1012 6a0 Misc WARNING: WinHttp: SendRequestUsingProxy
failed for <http://192.168.33.84/selfupdate/wuident.cab>. error 0x80072efd
2005-12-13 11:31:39 1012 6a0 Misc WARNING: WinHttp:
SendRequestToServerForFileInformation MakeRequest failed. error 0x80072efd
2005-12-13 11:31:39 1012 6a0 Misc WARNING: WinHttp:
SendRequestToServerForFileInformation failed with 0x80072efd
2005-12-13 11:31:39 1012 6a0 Misc WARNING: WinHttp: ShouldFileBeDownloaded
failed with 0x80072efd
2005-12-13 11:31:39 1012 6a0 Misc WARNING: Send failed with hr = 80072efd.
2005-12-13 11:31:39 1012 6a0 Misc WARNING: SendRequest failed with hr =
80072efd. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes
used : <>
2005-12-13 11:31:39 1012 6a0 Misc WARNING: WinHttp: SendRequestUsingProxy
failed for <http://192.168.33.84/selfupdate/wuident.cab>. error 0x80072efd
2005-12-13 11:31:39 1012 6a0 Misc WARNING: WinHttp:
SendRequestToServerForFileInformation MakeRequest failed. error 0x80072efd
2005-12-13 11:31:39 1012 6a0 Misc WARNING: WinHttp:
SendRequestToServerForFileInformation failed with 0x80072efd
2005-12-13 11:31:39 1012 6a0 Misc WARNING: WinHttp: ShouldFileBeDownloaded
failed with 0x80072efd
2005-12-13 11:31:39 1012 6a0 Misc WARNING: DownloadFileInternal failed for
http://192.168.33.84/selfupdate/wuident.cab: error 0x80072efd
2005-12-13 11:31:39 1012 6a0 Setup FATAL: IsUpdateRequired failed with error
0x80072efd
2005-12-13 11:31:39 1012 6a0 Setup WARNING: SelfUpdate: Default Service:
IsUpdateRequired failed: 0x80072efd
2005-12-13 11:31:39 1012 6a0 Setup WARNING: SelfUpdate: Default Service:
IsUpdateRequired failed, error = 0x80072EFD
2005-12-13 11:31:39 1012 6a0 Agent * WARNING: Skipping scan, self-update
check returned 0x80072EFD
2005-12-13 11:31:39 1012 6a0 Agent * WARNING: Exit code = 0x80072EFD
2005-12-13 11:31:39 1012 6a0 Agent *********
2005-12-13 11:31:39 1012 6a0 Agent ** END ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2005-12-13 11:31:39 1012 6a0 Agent *************
2005-12-13 11:31:39 1012 6a0 Agent WARNING: WU client failed Searching for
update with error 0x80072efd
2005-12-13 11:31:39 1012 6a0 AU >>## RESUMED ## AU: Search for updates
[CallId = {C3392906-8327-4849-AE52-1E6C2CA8866C}]
2005-12-13 11:31:39 1012 6a0 AU # WARNING: Search callback failed, result
= 0x80072EFD
2005-12-13 11:31:39 1012 6a0 AU #########
2005-12-13 11:31:39 1012 6a0 AU ## END ## AU: Search for updates [CallId
= {C3392906-8327-4849-AE52-1E6C2CA8866C}]
2005-12-13 11:31:39 1012 6a0 AU #############
2005-12-13 11:31:39 1012 6a0 AU AU setting next detection timeout to
2005-12-13 12:28:38

Any ideas anyone?

Andy

Andrew M

2005-12-13 13:04:02 UTC

Permalink

Here's a further update:

I have added the WSUS server to the trusted sites tab in Internet Explorer
and have installed the Bits2 and WinHTTP5.1 update from Microsoft.

Still the problem persists!

Andy

Post by Andrew M
Hi
Like a lot of the posts here I have some W2K clients which refuse to connect
to the WSUS server. All the XP clients and almost all the W2K clients so far
configured are OK.
The failed clients are W2K SP4 with Windows Update client 2.
They are in an NT4 domain so I have set up WSUS in local group policy.
I have looked at
http://support.microsoft.com/default.aspx?scid=kb;en-us;555459&sd=rss&spid=3198
We don't use proxy servers.
I have tried using raw IP address instead of domain name (although domain
name works fine for all other clients)
I have removed the two registry entries named in the above doc.
Still no resolution.
2005-12-13 11:31:39 1012 3f8 AU ########### AU: Policy change processed
###########
2005-12-13 11:31:39 1012 3f8 AU # Policy changed, AU restart required = No
2005-12-13 11:31:39 1012 3f8 AU # WSUS server: http://192.168.33.84
2005-12-13 11:31:39 1012 3f8 AU # Detection frequency: 1
2005-12-13 11:31:39 1012 3f8 AU # Approval type: Pre-download notify
(Policy)
2005-12-13 11:31:39 1012 6a0 Misc WARNING: Send failed with hr = 80072efd.
2005-12-13 11:31:39 1012 6a0 Misc WARNING: SendRequest failed with hr =
80072efd. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes
used : <>
2005-12-13 11:31:39 1012 6a0 Misc WARNING: WinHttp: SendRequestUsingProxy
failed for <http://192.168.33.84/selfupdate/wuident.cab>. error 0x80072efd
SendRequestToServerForFileInformation MakeRequest failed. error 0x80072efd
SendRequestToServerForFileInformation failed with 0x80072efd
2005-12-13 11:31:39 1012 6a0 Misc WARNING: WinHttp: ShouldFileBeDownloaded
failed with 0x80072efd
2005-12-13 11:31:39 1012 6a0 Misc WARNING: Send failed with hr = 80072efd.
2005-12-13 11:31:39 1012 6a0 Misc WARNING: SendRequest failed with hr =
80072efd. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes
used : <>
2005-12-13 11:31:39 1012 6a0 Misc WARNING: WinHttp: SendRequestUsingProxy
failed for <http://192.168.33.84/selfupdate/wuident.cab>. error 0x80072efd
SendRequestToServerForFileInformation MakeRequest failed. error 0x80072efd
SendRequestToServerForFileInformation failed with 0x80072efd
2005-12-13 11:31:39 1012 6a0 Misc WARNING: WinHttp: ShouldFileBeDownloaded
failed with 0x80072efd
2005-12-13 11:31:39 1012 6a0 Misc WARNING: Send failed with hr = 80072efd.
2005-12-13 11:31:39 1012 6a0 Misc WARNING: SendRequest failed with hr =
80072efd. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes
used : <>
2005-12-13 11:31:39 1012 6a0 Misc WARNING: WinHttp: SendRequestUsingProxy
failed for <http://192.168.33.84/selfupdate/wuident.cab>. error 0x80072efd
SendRequestToServerForFileInformation MakeRequest failed. error 0x80072efd
SendRequestToServerForFileInformation failed with 0x80072efd
2005-12-13 11:31:39 1012 6a0 Misc WARNING: WinHttp: ShouldFileBeDownloaded
failed with 0x80072efd
2005-12-13 11:31:39 1012 6a0 Misc WARNING: Send failed with hr = 80072efd.
2005-12-13 11:31:39 1012 6a0 Misc WARNING: SendRequest failed with hr =
80072efd. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes
used : <>
2005-12-13 11:31:39 1012 6a0 Misc WARNING: WinHttp: SendRequestUsingProxy
failed for <http://192.168.33.84/selfupdate/wuident.cab>. error 0x80072efd
SendRequestToServerForFileInformation MakeRequest failed. error 0x80072efd
SendRequestToServerForFileInformation failed with 0x80072efd
2005-12-13 11:31:39 1012 6a0 Misc WARNING: WinHttp: ShouldFileBeDownloaded
failed with 0x80072efd
2005-12-13 11:31:39 1012 6a0 Misc WARNING: DownloadFileInternal failed for
http://192.168.33.84/selfupdate/wuident.cab: error 0x80072efd
2005-12-13 11:31:39 1012 6a0 Setup FATAL: IsUpdateRequired failed with error
0x80072efd
IsUpdateRequired failed: 0x80072efd
IsUpdateRequired failed, error = 0x80072EFD
2005-12-13 11:31:39 1012 6a0 Agent * WARNING: Skipping scan, self-update
check returned 0x80072EFD
2005-12-13 11:31:39 1012 6a0 Agent * WARNING: Exit code = 0x80072EFD
2005-12-13 11:31:39 1012 6a0 Agent *********
2005-12-13 11:31:39 1012 6a0 Agent ** END ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2005-12-13 11:31:39 1012 6a0 Agent *************
2005-12-13 11:31:39 1012 6a0 Agent WARNING: WU client failed Searching for
update with error 0x80072efd
2005-12-13 11:31:39 1012 6a0 AU >>## RESUMED ## AU: Search for updates
[CallId = {C3392906-8327-4849-AE52-1E6C2CA8866C}]
2005-12-13 11:31:39 1012 6a0 AU # WARNING: Search callback failed, result
= 0x80072EFD
2005-12-13 11:31:39 1012 6a0 AU #########
2005-12-13 11:31:39 1012 6a0 AU ## END ## AU: Search for updates [CallId
= {C3392906-8327-4849-AE52-1E6C2CA8866C}]
2005-12-13 11:31:39 1012 6a0 AU #############
2005-12-13 11:31:39 1012 6a0 AU AU setting next detection timeout to
2005-12-13 12:28:38
Any ideas anyone?
Andy

Lawrence Garvin (MVP)

2005-12-14 02:10:41 UTC

Permalink

Post by Andrew M
We don't use proxy servers.

However, it could be that the WinHTTP is configured to use a non-existent

Post by Andrew M
2005-12-13 11:31:39 1012 6a0 Misc WARNING: Send failed with hr = 80072efd.

Run the Client Diagnostic Tool and post the results.

Also, this '2efd' error can be caused by other defects in the networking
infrastructure, including bad routing tables, defective DNS entries (which
would not be an issue when using a hardcoded IP Address as you are), or when
IIS is configured to use per-IP Address virtual servers and/or host headers
and they don't match the request submitted by the client.

Post by Andrew M
I have tried using raw IP address instead of domain name (although domain
name works fine for all other clients)
I have removed the two registry entries named in the above doc.
Still no resolution.
2005-12-13 11:31:39 1012 3f8 AU ########### AU: Policy change processed
###########
2005-12-13 11:31:39 1012 3f8 AU # Policy changed, AU restart required =
No
2005-12-13 11:31:39 1012 3f8 AU # WSUS server: http://192.168.33.84
2005-12-13 11:31:39 1012 3f8 AU # Detection frequency: 1
2005-12-13 11:31:39 1012 3f8 AU # Approval type: Pre-download notify
(Policy)
2005-12-13 11:31:39 1012 6a0 Misc WARNING: Send failed with hr = 80072efd.
2005-12-13 11:31:39 1012 6a0 Misc WARNING: SendRequest failed with hr =
80072efd. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes
used : <>
2005-12-13 11:31:39 1012 6a0 Misc WARNING: WinHttp: SendRequestUsingProxy
failed for <http://192.168.33.84/selfupdate/wuident.cab>. error 0x80072efd
SendRequestToServerForFileInformation MakeRequest failed. error 0x80072efd
SendRequestToServerForFileInformation failed with 0x80072efd
2005-12-13 11:31:39 1012 6a0 Misc WARNING: WinHttp: ShouldFileBeDownloaded
failed with 0x80072efd
2005-12-13 11:31:39 1012 6a0 Misc WARNING: Send failed with hr = 80072efd.
2005-12-13 11:31:39 1012 6a0 Misc WARNING: SendRequest failed with hr =
80072efd. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes
used : <>
2005-12-13 11:31:39 1012 6a0 Misc WARNING: WinHttp: SendRequestUsingProxy
failed for <http://192.168.33.84/selfupdate/wuident.cab>. error 0x80072efd
SendRequestToServerForFileInformation MakeRequest failed. error 0x80072efd
SendRequestToServerForFileInformation failed with 0x80072efd
2005-12-13 11:31:39 1012 6a0 Misc WARNING: WinHttp: ShouldFileBeDownloaded
failed with 0x80072efd
2005-12-13 11:31:39 1012 6a0 Misc WARNING: Send failed with hr = 80072efd.
2005-12-13 11:31:39 1012 6a0 Misc WARNING: SendRequest failed with hr =
80072efd. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes
used : <>
2005-12-13 11:31:39 1012 6a0 Misc WARNING: WinHttp: SendRequestUsingProxy
failed for <http://192.168.33.84/selfupdate/wuident.cab>. error 0x80072efd
SendRequestToServerForFileInformation MakeRequest failed. error 0x80072efd
SendRequestToServerForFileInformation failed with 0x80072efd
2005-12-13 11:31:39 1012 6a0 Misc WARNING: WinHttp: ShouldFileBeDownloaded
failed with 0x80072efd
2005-12-13 11:31:39 1012 6a0 Misc WARNING: Send failed with hr = 80072efd.
2005-12-13 11:31:39 1012 6a0 Misc WARNING: SendRequest failed with hr =
80072efd. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes
used : <>
2005-12-13 11:31:39 1012 6a0 Misc WARNING: WinHttp: SendRequestUsingProxy
failed for <http://192.168.33.84/selfupdate/wuident.cab>. error 0x80072efd
SendRequestToServerForFileInformation MakeRequest failed. error 0x80072efd
SendRequestToServerForFileInformation failed with 0x80072efd
2005-12-13 11:31:39 1012 6a0 Misc WARNING: WinHttp: ShouldFileBeDownloaded
failed with 0x80072efd
2005-12-13 11:31:39 1012 6a0 Misc WARNING: DownloadFileInternal failed for
http://192.168.33.84/selfupdate/wuident.cab: error 0x80072efd
2005-12-13 11:31:39 1012 6a0 Setup FATAL: IsUpdateRequired failed with
error
0x80072efd
IsUpdateRequired failed: 0x80072efd
IsUpdateRequired failed, error = 0x80072EFD
2005-12-13 11:31:39 1012 6a0 Agent * WARNING: Skipping scan, self-update
check returned 0x80072EFD
2005-12-13 11:31:39 1012 6a0 Agent * WARNING: Exit code = 0x80072EFD
2005-12-13 11:31:39 1012 6a0 Agent *********
2005-12-13 11:31:39 1012 6a0 Agent ** END ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2005-12-13 11:31:39 1012 6a0 Agent *************
2005-12-13 11:31:39 1012 6a0 Agent WARNING: WU client failed Searching for
update with error 0x80072efd
2005-12-13 11:31:39 1012 6a0 AU >>## RESUMED ## AU: Search for updates
[CallId = {C3392906-8327-4849-AE52-1E6C2CA8866C}]
2005-12-13 11:31:39 1012 6a0 AU # WARNING: Search callback failed,
result
= 0x80072EFD
2005-12-13 11:31:39 1012 6a0 AU #########
2005-12-13 11:31:39 1012 6a0 AU ## END ## AU: Search for updates
[CallId
= {C3392906-8327-4849-AE52-1E6C2CA8866C}]
2005-12-13 11:31:39 1012 6a0 AU #############
2005-12-13 11:31:39 1012 6a0 AU AU setting next detection timeout to
2005-12-13 12:28:38
Any ideas anyone?
Andy

Andrew M

2005-12-15 14:29:03 UTC

Permalink

Lawrence

Output from Client Diagnostic Tool is below. Interestingly, the last but one
line was not included in the output file, I had to copy it in from a DOS box
where I ran the same tool without the /t option!

WSUS Client Diagnostics Tool

Checking Machine State
Checking for admin rights to run tool . . . . . . . . . PASS
Automatic Updates Service is running. . . . . . . . . . PASS
Background Intelligent Transfer Service is not running. PASS
Wuaueng.dll version 5.8.0.2469. . . . . . . . . . . . . PASS
This version is WSUS 2.0

Checking AU Settings
AU Option is 2 : Notify Prior to Download . . . . . . . PASS
Option is from Policy settings

Checking Proxy Configuration
Checking for winhttp local machine Proxy settings . . . PASS
Winhttp local machine access type
<Direct Connection>
Winhttp local machine Proxy. . . . . . . . . . PASS
Winhttp local machine ProxyBypass. . . . . . . PASS
Checking User IE Proxy settings . . . . . . . . . . . . PASS
User IE Proxy. . . . . . . . . . . . . . . . . PASS
User IE ProxyByPass. . . . . . . . . . . . . . PASS
User IE AutoConfig URL Proxy . . . . . . . . . PASS
User IE AutoDetect
AutoDetect not in use

Checking Connection to WSUS/SUS Server
WUServer = http://192.168.33.84
WUStatusServer = http://192.168.33.84
UseWuServer is enabled. . . . . . . . . . . . . . . . . PASS

VerifyWUServerURL() failed with hr=0x80072efd
A connection with the server could not be established

Regards

Andy

Post by Lawrence Garvin (MVP)

Post by Andrew M
We don't use proxy servers.

However, it could be that the WinHTTP is configured to use a non-existent

Post by Andrew M
2005-12-13 11:31:39 1012 6a0 Misc WARNING: Send failed with hr = 80072efd.

Run the Client Diagnostic Tool and post the results.
Also, this '2efd' error can be caused by other defects in the networking
infrastructure, including bad routing tables, defective DNS entries (which
would not be an issue when using a hardcoded IP Address as you are), or when
IIS is configured to use per-IP Address virtual servers and/or host headers
and they don't match the request submitted by the client.

Lawrence Garvin (MVP)

2005-12-17 02:08:00 UTC

Permalink

Post by Andrew M
VerifyWUServerURL() failed with hr=0x80072efd
A connection with the server could not be established

0x80072efd - ERROR INTERNET CANNOT CONNECT

It's pretty straightforward... a connection with the server could not be
established.

This is a networking infrastructure error. It's been observed to be caused
by any one of the following:
- the client's proxy configuration is incorrect (this client has no
proxy configuration)
- the proxy server is not configured to service the client's request
(you've stated there is no proxy server)
- DNS services are misconfigured, or not responding (you have an IP
Address configured, so DNS is not an issue)
- the client and server are on different subnets and the routing tables
are defective
- no website exists at the configured URL
- a client configured to use a dialup connection is disconnected
- a client configured to use a wireless connection is not authenticated,
or being blocked by a MAC filter
- the intended virtual server is not configured to listen to the address
configured in the URL
aka, the web server doesn't exist
- a server-side firewall has been enabled on the WSUS server and is
blocking access to web services on port 80

One thing this is definitely not is a permissions issue on the web server,
or misconfigured virtual directories. Those scenarios result in HTTP '401'
and '404' errors. This scenario is characterized by the complete absence of
an HTTP error message, indicating that the GET request is never received by
the web server. (This can be verified by inspecting the IIS Logfiles and
noting the absence of any requests from this client.)

Post by Andrew M
Lawrence
Output from Client Diagnostic Tool is below. Interestingly, the last but one
line was not included in the output file, I had to copy it in from a DOS box
where I ran the same tool without the /t option!
WSUS Client Diagnostics Tool
Checking Machine State
Checking for admin rights to run tool . . . . . . . . . PASS
Automatic Updates Service is running. . . . . . . . . . PASS
Background Intelligent Transfer Service is not running. PASS
Wuaueng.dll version 5.8.0.2469. . . . . . . . . . . . . PASS
This version is WSUS 2.0
Checking AU Settings
AU Option is 2 : Notify Prior to Download . . . . . . . PASS
Option is from Policy settings
Checking Proxy Configuration
Checking for winhttp local machine Proxy settings . . . PASS
Winhttp local machine access type
<Direct Connection>
Winhttp local machine Proxy. . . . . . . . . . PASS
Winhttp local machine ProxyBypass. . . . . . . PASS
Checking User IE Proxy settings . . . . . . . . . . . . PASS
User IE Proxy. . . . . . . . . . . . . . . . . PASS
User IE ProxyByPass. . . . . . . . . . . . . . PASS
User IE AutoConfig URL Proxy . . . . . . . . . PASS
User IE AutoDetect
AutoDetect not in use
Checking Connection to WSUS/SUS Server
WUServer = http://192.168.33.84
WUStatusServer = http://192.168.33.84
UseWuServer is enabled. . . . . . . . . . . . . . . . . PASS
VerifyWUServerURL() failed with hr=0x80072efd
A connection with the server could not be established
Regards
Andy

Post by Lawrence Garvin (MVP)

Post by Andrew M
We don't use proxy servers.

However, it could be that the WinHTTP is configured to use a non-existent

Post by Andrew M
2005-12-13 11:31:39 1012 6a0 Misc WARNING: Send failed with hr = 80072efd.

Run the Client Diagnostic Tool and post the results.
Also, this '2efd' error can be caused by other defects in the networking
infrastructure, including bad routing tables, defective DNS entries (which
would not be an issue when using a hardcoded IP Address as you are), or when
IIS is configured to use per-IP Address virtual servers and/or host headers
and they don't match the request submitted by the client.

Post by Andrew M
I have tried using raw IP address instead of domain name (although domain
name works fine for all other clients)
I have removed the two registry entries named in the above doc.
Still no resolution.
2005-12-13 11:31:39 1012 3f8 AU ########### AU: Policy change processed
###########
2005-12-13 11:31:39 1012 3f8 AU # Policy changed, AU restart required =
No
2005-12-13 11:31:39 1012 3f8 AU # WSUS server: http://192.168.33.84
2005-12-13 11:31:39 1012 3f8 AU # Detection frequency: 1
2005-12-13 11:31:39 1012 3f8 AU # Approval type: Pre-download notify
(Policy)
2005-12-13 11:31:39 1012 6a0 Misc WARNING: Send failed with hr = 80072efd.
2005-12-13 11:31:39 1012 6a0 Misc WARNING: SendRequest failed with hr =
80072efd. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes
used : <>
SendRequestUsingProxy
failed for <http://192.168.33.84/selfupdate/wuident.cab>. error 0x80072efd
SendRequestToServerForFileInformation MakeRequest failed. error 0x80072efd
SendRequestToServerForFileInformation failed with 0x80072efd
ShouldFileBeDownloaded
failed with 0x80072efd
2005-12-13 11:31:39 1012 6a0 Misc WARNING: Send failed with hr = 80072efd.
2005-12-13 11:31:39 1012 6a0 Misc WARNING: SendRequest failed with hr =
80072efd. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes
used : <>
SendRequestUsingProxy
failed for <http://192.168.33.84/selfupdate/wuident.cab>. error 0x80072efd
SendRequestToServerForFileInformation MakeRequest failed. error 0x80072efd
SendRequestToServerForFileInformation failed with 0x80072efd
ShouldFileBeDownloaded
failed with 0x80072efd
2005-12-13 11:31:39 1012 6a0 Misc WARNING: Send failed with hr = 80072efd.
2005-12-13 11:31:39 1012 6a0 Misc WARNING: SendRequest failed with hr =
80072efd. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes
used : <>
SendRequestUsingProxy
failed for <http://192.168.33.84/selfupdate/wuident.cab>. error 0x80072efd
SendRequestToServerForFileInformation MakeRequest failed. error 0x80072efd
SendRequestToServerForFileInformation failed with 0x80072efd
ShouldFileBeDownloaded
failed with 0x80072efd
2005-12-13 11:31:39 1012 6a0 Misc WARNING: Send failed with hr = 80072efd.
2005-12-13 11:31:39 1012 6a0 Misc WARNING: SendRequest failed with hr =
80072efd. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes
used : <>
SendRequestUsingProxy
failed for <http://192.168.33.84/selfupdate/wuident.cab>. error 0x80072efd
SendRequestToServerForFileInformation MakeRequest failed. error 0x80072efd
SendRequestToServerForFileInformation failed with 0x80072efd
ShouldFileBeDownloaded
failed with 0x80072efd
2005-12-13 11:31:39 1012 6a0 Misc WARNING: DownloadFileInternal failed for
http://192.168.33.84/selfupdate/wuident.cab: error 0x80072efd
2005-12-13 11:31:39 1012 6a0 Setup FATAL: IsUpdateRequired failed with
error
0x80072efd
IsUpdateRequired failed: 0x80072efd
IsUpdateRequired failed, error = 0x80072EFD
2005-12-13 11:31:39 1012 6a0 Agent * WARNING: Skipping scan, self-update
check returned 0x80072EFD
2005-12-13 11:31:39 1012 6a0 Agent * WARNING: Exit code = 0x80072EFD
2005-12-13 11:31:39 1012 6a0 Agent *********
2005-12-13 11:31:39 1012 6a0 Agent ** END ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2005-12-13 11:31:39 1012 6a0 Agent *************
2005-12-13 11:31:39 1012 6a0 Agent WARNING: WU client failed Searching for
update with error 0x80072efd
2005-12-13 11:31:39 1012 6a0 AU >>## RESUMED ## AU: Search for updates
[CallId = {C3392906-8327-4849-AE52-1E6C2CA8866C}]
2005-12-13 11:31:39 1012 6a0 AU # WARNING: Search callback failed,
result
= 0x80072EFD
2005-12-13 11:31:39 1012 6a0 AU #########
2005-12-13 11:31:39 1012 6a0 AU ## END ## AU: Search for updates
[CallId
= {C3392906-8327-4849-AE52-1E6C2CA8866C}]
2005-12-13 11:31:39 1012 6a0 AU #############
2005-12-13 11:31:39 1012 6a0 AU AU setting next detection timeout to
2005-12-13 12:28:38
Any ideas anyone?
Andy

Andrew M

2005-12-19 11:43:02 UTC

Permalink

Lawrence

This PC was also unable to receive updates from another service for
antispyware running on the same server so I rebuilt the client PC from an
image in the end. After installing the Windows Update Software and the
management agent for the antispyware both worked fine. This would suggest
that there was something wrong with the client.

However, one thing I didn't mention was a reference in an earlier look at
the WSUS client log files to "Server congestion detected". Now, the server in
question runs MSDE apps for several centralised apps - antivirus,
antispyware, network auditing software and WSUS. Maybe the problem is there
but if so why would rebuiling the client solve the problem? Is it because
each client only tries to contact the server on a limited range of port
numbers and the ones for this client were already busy elsewhere?

Incidentally I am also seeing the same error on another client PC now so
maybe I should distribute these server processes to different boxes? I will
try and investigate this server congestion error further.

Andy

Post by Lawrence Garvin (MVP)

Post by Andrew M
VerifyWUServerURL() failed with hr=0x80072efd
A connection with the server could not be established

0x80072efd - ERROR INTERNET CANNOT CONNECT
It's pretty straightforward... a connection with the server could not be
established.
This is a networking infrastructure error. It's been observed to be caused
- the client's proxy configuration is incorrect (this client has no
proxy configuration)
- the proxy server is not configured to service the client's request
(you've stated there is no proxy server)
- DNS services are misconfigured, or not responding (you have an IP
Address configured, so DNS is not an issue)
- the client and server are on different subnets and the routing tables
are defective
- no website exists at the configured URL
- a client configured to use a dialup connection is disconnected
- a client configured to use a wireless connection is not authenticated,
or being blocked by a MAC filter
- the intended virtual server is not configured to listen to the address
configured in the URL
aka, the web server doesn't exist
- a server-side firewall has been enabled on the WSUS server and is
blocking access to web services on port 80
One thing this is definitely not is a permissions issue on the web server,
or misconfigured virtual directories. Those scenarios result in HTTP '401'
and '404' errors. This scenario is characterized by the complete absence of
an HTTP error message, indicating that the GET request is never received by
the web server. (This can be verified by inspecting the IIS Logfiles and
noting the absence of any requests from this client.)

Andrew M

2005-12-19 13:52:02 UTC

Permalink

OK - Confession Time!
I have solved my problem. It was due to McAfee Viruscan Enterprise V8.0i
blocking certain ports on the client PCs. The two with problems had
different, stricter settings to all other PCs and hence they were the only
two with problems.

Anyone using Viruscan Enterprise should watch out for port blocking under
the "Access Protection" heading.

I wander how many other problems are caused by psuedo-firewall features in
these anti-virus programs?

Thanks for your help Lawrence.

Andy

Post by Andrew M
Lawrence
This PC was also unable to receive updates from another service for
antispyware running on the same server so I rebuilt the client PC from an
image in the end. After installing the Windows Update Software and the
management agent for the antispyware both worked fine. This would suggest
that there was something wrong with the client.
However, one thing I didn't mention was a reference in an earlier look at
the WSUS client log files to "Server congestion detected". Now, the server in
question runs MSDE apps for several centralised apps - antivirus,
antispyware, network auditing software and WSUS. Maybe the problem is there
but if so why would rebuiling the client solve the problem? Is it because
each client only tries to contact the server on a limited range of port
numbers and the ones for this client were already busy elsewhere?
Incidentally I am also seeing the same error on another client PC now so
maybe I should distribute these server processes to different boxes? I will
try and investigate this server congestion error further.
Andy

Post by Lawrence Garvin (MVP)

Post by Andrew M
VerifyWUServerURL() failed with hr=0x80072efd
A connection with the server could not be established

0x80072efd - ERROR INTERNET CANNOT CONNECT
It's pretty straightforward... a connection with the server could not be
established.
This is a networking infrastructure error. It's been observed to be caused
- the client's proxy configuration is incorrect (this client has no
proxy configuration)
- the proxy server is not configured to service the client's request
(you've stated there is no proxy server)
- DNS services are misconfigured, or not responding (you have an IP
Address configured, so DNS is not an issue)
- the client and server are on different subnets and the routing tables
are defective
- no website exists at the configured URL
- a client configured to use a dialup connection is disconnected
- a client configured to use a wireless connection is not authenticated,
or being blocked by a MAC filter
- the intended virtual server is not configured to listen to the address
configured in the URL
aka, the web server doesn't exist
- a server-side firewall has been enabled on the WSUS server and is
blocking access to web services on port 80
One thing this is definitely not is a permissions issue on the web server,
or misconfigured virtual directories. Those scenarios result in HTTP '401'
and '404' errors. This scenario is characterized by the complete absence of
an HTTP error message, indicating that the GET request is never received by
the web server. (This can be verified by inspecting the IIS Logfiles and
noting the absence of any requests from this client.)

Lawrence Garvin (MVP)

2005-12-19 20:39:46 UTC

Permalink

Yes it would.. and outbound firewall blocking is something I did not mention
in the original post.

Post by Andrew M
However, one thing I didn't mention was a reference in an earlier look at
the WSUS client log files to "Server congestion detected".

Can you post the log segment showing this error message. I've -never- seen
this phrase used before.

Post by Andrew M
Now, the server in
question runs MSDE apps for several centralised apps - antivirus,
antispyware, network auditing software and WSUS. Maybe the problem is there

Yeah... is the server running multiple instances of /MSDE/ or /WMSDE/, or is
the WSUS database running on a dedicated instance of /MSDE/ or /WSMDE/?

Post by Andrew M
but if so why would rebuiling the client solve the problem?

Good question... :-)

Post by Andrew M
Is it because
each client only tries to contact the server on a limited range of port
numbers and the ones for this client were already busy elsewhere?

Nope. ALL clients contact the webservices on the WSUS server on the same
port number. The clients -never- talk to the database directly.

Post by Andrew M
Incidentally I am also seeing the same error on another client PC now so
maybe I should distribute these server processes to different boxes? I will
try and investigate this server congestion error further.
Andy

Post by Lawrence Garvin (MVP)

Post by Andrew M
VerifyWUServerURL() failed with hr=0x80072efd
A connection with the server could not be established

0x80072efd - ERROR INTERNET CANNOT CONNECT
It's pretty straightforward... a connection with the server could not be
established.
This is a networking infrastructure error. It's been observed to be caused
- the client's proxy configuration is incorrect (this client has no
proxy configuration)
- the proxy server is not configured to service the client's request
(you've stated there is no proxy server)
- DNS services are misconfigured, or not responding (you have an IP
Address configured, so DNS is not an issue)
- the client and server are on different subnets and the routing tables
are defective
- no website exists at the configured URL
- a client configured to use a dialup connection is disconnected
- a client configured to use a wireless connection is not
authenticated,
or being blocked by a MAC filter
- the intended virtual server is not configured to listen to the address
configured in the URL
aka, the web server doesn't exist
- a server-side firewall has been enabled on the WSUS server and is
blocking access to web services on port 80
One thing this is definitely not is a permissions issue on the web server,
or misconfigured virtual directories. Those scenarios result in HTTP '401'
and '404' errors. This scenario is characterized by the complete absence of
an HTTP error message, indicating that the GET request is never received by
the web server. (This can be verified by inspecting the IIS Logfiles and
noting the absence of any requests from this client.)