Clients not finding WSUS server

Hi:
I've installed WSUS 3.1 on a Windows 2003 Server.
No clients are showing up in the clients Window.

At first I thought it was a WSUS problem, but I brought my laptop to the
site, and it showed up in the WSUS Computers listing. (by coincidence, the
name of the update server in the domain that the laptop is a member of is the
same as the one experiencing the problem)

Client diag tool shows:

--------------------------------------------------------------------
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 7.2.6001.788. . . . . . . . . . . . PASS
This version is WSUS 2.0

Checking AU Settings
AU Option is 4: Scheduled Install . . . . . . . . . . . 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. . . . . . . . . . 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:\\10.139.1.11:8530
WUStatusServer = http:\\10.139.1.11:8530
UseWuServer is enabled. . . . . . . . . . . . . . . . . PASS

VerifyWUServerURL() failed with hr=0x80072ee5

The URL is invalid
--------------------------------------------------------------------

So clients from another domain can find the server, but clients from the
same domain cannot. Ideas?

You've got a syntax error in the address for the WSUS server. Should be
http://, not http:\\. Look at your group policy applied to those
computers and you should find the error there.

Tone-man 123 wrote:
> Hi:
> I've installed WSUS 3.1 on a Windows 2003 Server.
> No clients are showing up in the clients Window.
>
> At first I thought it was a WSUS problem, but I brought my laptop to the
> site, and it showed up in the WSUS Computers listing. (by coincidence, the
> name of the update server in the domain that the laptop is a member of is the
> same as the one experiencing the problem)
>
> Client diag tool shows:
>
> --------------------------------------------------------------------
> 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 7.2.6001.788. . . . . . . . . . . . PASS
> This version is WSUS 2.0
>
> Checking AU Settings
> AU Option is 4: Scheduled Install . . . . . . . . . . . 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. . . . . . . . . . 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:\\10.139.1.11:8530
> WUStatusServer = http:\\10.139.1.11:8530
> UseWuServer is enabled. . . . . . . . . . . . . . . . . PASS
>
> VerifyWUServerURL() failed with hr=0x80072ee5
>
> The URL is invalid
> --------------------------------------------------------------------
>
> So clients from another domain can find the server, but clients from the
> same domain cannot. Ideas?
>

Oops!
HA!

Thanks for the astute eye.



"Wade Godfrey" wrote:

> You've got a syntax error in the address for the WSUS server. Should be
> http://, not http:\\. Look at your group policy applied to those
> computers and you should find the error there.
>
> Tone-man 123 wrote:
> > Hi:
> > I've installed WSUS 3.1 on a Windows 2003 Server.
> > No clients are showing up in the clients Window.
> >
> > At first I thought it was a WSUS problem, but I brought my laptop to the
> > site, and it showed up in the WSUS Computers listing. (by coincidence, the
> > name of the update server in the domain that the laptop is a member of is the
> > same as the one experiencing the problem)
> >
> > Client diag tool shows:
> >
> > --------------------------------------------------------------------
> > 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 7.2.6001.788. . . . . . . . . . . . PASS
> > This version is WSUS 2.0
> >
> > Checking AU Settings
> > AU Option is 4: Scheduled Install . . . . . . . . . . . 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. . . . . . . . . . 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:\\10.139.1.11:8530
> > WUStatusServer = http:\\10.139.1.11:8530
> > UseWuServer is enabled. . . . . . . . . . . . . . . . . PASS
> >
> > VerifyWUServerURL() failed with hr=0x80072ee5
> >
> > The URL is invalid
> > --------------------------------------------------------------------
> >
> > So clients from another domain can find the server, but clients from the
> > same domain cannot. Ideas?
> >
>