WSUS Client Diagnostic Tool error 0x80072efe

HI I have a w2k server sp4 as DC that the name of server does not appear on
wsus server computer list.
I have try to lunch the client diagnostic tool and an error is return see
below:
I have try a lot of solutions from this newsgroup but nothing have solved my
problem.
P.S.
If I try to connect to the Microsoft Update site my server working fine.

Thanks in advance Simon

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
<Using Proxy>
Winhttp local machine Proxy
fw1
Winhttp local machine ProxyBypass. . . . . . . NONE
Checking User IE Proxy settings . . . . . . . . . . . . PASS
User IE Proxy
fw1:8080
User IE ProxyByPass
ids<local>
User IE AutoConfig URL Proxy . . . . . . . . . NONE
User IE AutoDetect
AutoDetect not in use

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

VerifyWUServerURL() failed with hr=0x80072efe

The connection with the server was terminated abnormally


Press Enter to Complete

0x80072efe - ERROR INTERNET CONNECTION ABORTED

Most likely, the proxy server 'fw1' is interfering with your access to the
WSUS server.

I notice that IE is configured to use 'fw1:8080' for the proxy server, but
<local> is bypassed (though I'm concerned about the 'ids' in front of
<local>).

However, WinHTTP is configured to use 'fw1' (note the missing port
identifier), and there is no local bypass for WinHTTP.

I'll be that the WUA on this system is trying to talk to a proxy server on
port 80 of 'fw1' and the proxy server is not responding.

If you're bypassing local resources for the proxy server, then the best
solution is to put WinHTTP in DIRECT mode using the command:
proxycfg -d

Othewise clone your working IE proxy configuration to WinHTTP using the
command:
proxycfg -u

(Be sure to verify that your IE proxy configuration is actually working,
however, given my comment about thte 'ids<local>' string.)

[Helder]

I have a similar problem, I´m it´s my first time using WSUS and after running the WSUS diagnostic tool on one of the clients and got the following errors:

Winhttp local machine proxy ....NONE
Winhttp local machine ProxyByPass....NONE
User IE Proxy.... NONE
User IE ProxyByPass..... NONE

VerifyWUServerURL() failed with hr=0x80190193
HTTP 403: the client does not have suficient permissions to access the server

please help any one

ok, these is exactly what the client diagnostic gives me

Checking proxy configuration
checking for winhttp local machine proxy settings ..... PASS
winhttp local machine access type
<direct connection>
winhttp local machine proxy .....................NONE
winhttp local machine proxybypass.............NONE
checking user IE proxy settings ..............................PASS
user IE proxy .........................................NONE
user IE proxybypass.................................NONE
user IE autoconfig URL proxy......................NONE
user IE autodetect
autodetect in use

checking connectio to WSUS/SUS Server
WUServer = http://kit-svr-old/
WUStatusServer = http://kit-srv-old/
useWuServer is enable ..........................................PASS

VerifyWUServerURL() failed with hr=080072ee7

it was not possible to process the server´s name or server address

press enter to complete

It was taken from the same computer, I checked all the abouve and they all work fine

If you could please post the actual and complete output from the Client
Diagnostic Tool, I can provide a more accurate response.

In addition, since this is your first time using WSUS, I would direct you to
this document to be sure you've correctly installed and configured all that
is required.

WSUS Step By Step Guide
http://technet.microsoft.com/en-us/l...22(WS.10).aspx

Truly.. this is not the *exact* and *complete* output of the Client
Diagnostic Tool.

Generally when you're asked for diagnostic information, we'd like to see an
*exact* copy of that output (i.e. use Copy and Paste -- don't retype what
you see on the screen). As an example to make that point -- while it's not
critical here -- you mistyped the error code below 'hr=080072ee7'. Luckily,
I'm able to interpret it correctly, but imagine what challenges would have
caused if you'd missed the '7' or the '2' or the 'e' instead of the 'x'?

*THIS* is the part that matters, though... and, I note, is *DIFFERENT* from
what you posted in your original post

Is this all from the same computer?


In any event, the 0x80072ee7 is an "Internet Name Not Resolved" error and
results from one of these causes:

1. The hostname 'kit-srv-old' is not registered in your DNS Server(s).

2. The DNS Server(s) are offline.

3. The client machine has no connectivity to the DNS Server(s).

4. The client machine is configured to use the incorrect (or nonexistent)
DNS Server(s).

5. The client machine's DNS Suffix is improperly configured.

and a few other more esoteric reasons if none of the above apply.

Also, I would recommend removing the trailing slash from the URL, it should
be just

0x80072efe is a Connection Aborted error.

So now you've provided me output from the same computer with *THREE*
different errors.

Obviously something else in your enviroment is in a volatile state, or we'd
be getting the same errors each time.

Please post the ACTUAL and COMPLETE output of the Client Diagnostic Tool. I
*cannot* (and will not) invest time in diagnosing partial output. Everytime
I have mistakenly done so in the past it's resulted in a *BAD* diagnosis
because unsupplied information changes the context of the diagnosis.

[TerryG]

I know this post is old but I'm hoping someone can still help me. I have about 60 clients in my network and only 31 are showing up in WSUS. I ran the WSUS Client Diagnostics Tool and the results are all the same.

WSUS Client Diagnostics Tool

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

Checking AU Settings
AU Option is 3: Notify Prior to Install...............................PASS
Option is from Control Panel

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

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

VerifyWUServerURL<> failed with hr=0x800672efe

The connection with the server was terminated abnormally



We don't use a proxy server and all the computers are generally configured the same. Why would half of them register on WSUS and not the other half?

[Janos™]

Hi TerryG,

Are you able to run the SCE console on a remote terminal? Are you able to navigate to any web service or application hosted on that same server? I think that you may have something blocking your inbound ports on the SCE server itself. Presuming that 'FQDN' was your way of masking an internal server, the configuration looks correct. Also try to change the GPO from

http://server.domain.com:8530 or something else
to
http://server.domain.com