> SeanL wrote:
> Using wsus 3 sp1. All the clients are updating without any issues, the
> only
> problem is that the WSUS Server itself is not updating.
> I ran the diagnostics tool, and the following error came up:
> "VerifyWUServerURL<> failed with hr=0x80072efd - A connection with the
> server could not be established.
> The registry shows the WUServer as http://Servername just like all the
> other clients. Any ideas??
Is the WSUS Server able to successfully resolve the hostname "Servername"?
Is anything blocking access to permit the WSUS Server to access IIS on
itself?
Is the WinHTTP proxy configuration possibly incorrect on the WSUS Server?
Are ALL of the policy configuration values being properly set on the WSUS
Server? The WUServer value could be correct, but if something else is amiss,
the connection could fail. Please post ALL of the (UNEDITED) output from the
Client Diagnostic Tool.
--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)
MS WSUS Website:
http://www.microsoft.com/wsus
My Websites:
http://www.onsitechsolutions.com;
http://wsusinfo.onsitechsolutions.com
My MVP Profile:
http://mvp.support.microsoft.com/pro...awrence.Garvin