Link to home
Start Free TrialLog in
Avatar of john6216
john6216

asked on

WSUS not listing 1 computer

One of my computers is not showing up in the WSUS 2 admin console.  I get the error code 0x80072efd.  The computer not showing is running Windows Server 2003 sp2 in an active directory environment.  We are using a proxy (ISA 2004) but I have pointed the IE settings to direct connect to the internet.  I have also added the WSUS website as a trusted site and enabled auto detect for the settings.  I have attached both the error logs and the latest WSUS client diagnostic tool scan.  
I would like to get that server to report to the WSUS server so I can iron out the wrinkiles before upgrading to WSUS 3.  
Note:  Could it be a DNS issue?  If so how do I point the computer to the WSUS website IP address instead of the name recognition without using the Group Policy already in place with the IP address?
Thanks from Haines, Alaska
WSUS-error-log.txt
wsusclientdiagerror.bmp
Avatar of ChiefIT
ChiefIT
Flag of United States of America image

I have been working with another post where only a couple clients showed up. When running a WSUS client diagnostic tool, they came up with the 503 error on the client (overloaded NIC). The WSUS client diag tool will show a line in the text that says something like:

VerifyWUServerURL() failed with hr=0x801901f7

The proposed fix to this is:
"Check your registry (on the client machine) for a Binary value in
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Internet
Settings\Connections that is called WinHttpSettings. If it exists,
delete it."

and I found that fix on this site:
http://www.wsus.info/forums/index.php?showtopic=5308

Another possibility is:

You have your WSUS web page in the default location and on the default port. The default port is HTTP port 80 for WSUS. Port 8530 has been used as an alternative port for folks who have multiple web sites on their server.

In either case, you are having problems with your clients figuring out the URL for your WSUS server. First I would check to see if my WSUS web page is on port 80, not 8530. Then I would remove the above registry key as explained in the article.

Avatar of john6216
john6216

ASKER

I deleted the WinHttpSettings registry key.  I did a wuauclt /update command and I checked the group policy on the client computer.  It is set to check the 8530 port instead of 80.  The WSUS is on port 8530 on the server holding the program.  

This is frustrating...  I know that it is the URL that is not connecting because I cannot connect with the Windows Update program on the server either.  It gives me the error code 0x80072efd as well.  The solution fixes are to check the firewall settings and the proxy settings and there is a service rule allowing WSUS on port 8530 on our firewall, and the proxy is set to accept WSUS traffic through it, but I set the Internet Explorer settings to direct connect to the internet.  

If you discover any other leads let me know.  I do appreciate your help very much.
WARNING: GetAuthorizationCookie failure, error = 0x80072EFD, soap client error = 5, soap error code = 0, HTTP status code = 200

Have you deleted your cookies and internet cache?
Thanks for the suggestion.  
I went in to the Internet explorer tools, internet options, and deleted the cookies, as well as performed a disk clean on drive c:.  But I am still getting the ox80072efd error.  I will include the latest log on WSUS.  I feel like we are making headway but have not quite got it yet.  THanks for staying with me on this!  It has been a long time comin!  (note the reference to Kenny in the attached log file snippet)  What about the failure to refresh cookie error recieved in the latest log?  Could that be a potential source for the error?
If so how do I correct it?

WSUS-error-loggins.txt
ASKER CERTIFIED SOLUTION
Avatar of ChiefIT
ChiefIT
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I will have to get back to this problem later.  It turns out that we have a bad hard drive.

I am posting a new question with this problem.  Basically the primary hard drive is bad I need to replace it but without it in place I cannot boot to the secondary plex mirrored drive.  So I guess my question is what is the point in having a software based (windows server 2003) based Raid or mirror if it doesn't even work when it is supposed to?  Do you have any ideas on how to replace the primary drive and get the computer to boot to the secondary?  The drive is still barely operable and at this point I can get in to change the boot.ini file if needed?

Points are still in place for this question if you can help...
THanks
how did the hard drive replacement go? Still having problems?
Oh, Excellent! Thanks! Glad to see it worked.

This is an odd way of knocking down WSUS updates. I'll have to keep this for future reference.