wsus client cant connect to server 3.0

I have two Wsus servers 3.0. One primary and second on the next side of my
country. We have few branches. Clients, which connect to server (no primary),
can not conect it. Both the servers have the same configuration. I have two
GPO and both are the same, only name of the server are different.
In logfiles on the client i have this error:
2008-08-29 09:24:36:119 1688 99c PT
WARNING: Initialization failed for Protocol Talker Context: 0x80072ee5
2008-08-29 09:24:36:119 1688 99c Report WARNING:
Reporter failed to upload events with hr = 80072ee5.

client diag tool get me error: Verify WuserverURL 80072ee5 failed with hr =
80072ee5.

i can save file from ....selfupdate\iuident.cab
in registry i have right values.

C ould you help mee?
Thanks

On Aug 29, 7:27*am, bertolo <bert...@discussions.microsoft.com> wrote:
> I have two Wsus servers 3.0. One primary and second on the next side of my
> country. We have few branches. Clients, which connect to server (no primary),
> can not conect it. Both the servers have the same configuration. I have two
> GPO and both are the same, only name of the server are different.
> In logfiles on the client i have this error:
> 2008-08-29 * * * * 09:24:36:119 * * *1688 * * *99c * * * * PT * * * * *
> WARNING: Initialization failed for Protocol Talker Context: 0x80072ee5
> 2008-08-29 * * * * 09:24:36:119 * * *1688 * * *99c * * * * Report *WARNING:
> Reporter failed to upload events with hr = 80072ee5.
>
> client diag tool get me error: Verify WuserverURL 80072ee5 *failed withhr =
> 80072ee5.
>
> i can save file from ....selfupdate\iuident.cab
> in registry i have right values.
>
> C ould you help mee?
> Thanks

Do your servers share a content directory? or does each have it's own?
If each has it's own and they are sharing a URL this could be a
problem.

each server has own content directory

"madbassist1" wrote:

> On Aug 29, 7:27 am, bertolo <bert...@discussions.microsoft.com> wrote:
> > I have two Wsus servers 3.0. One primary and second on the next side of my
> > country. We have few branches. Clients, which connect to server (no primary),
> > can not conect it. Both the servers have the same configuration. I have two
> > GPO and both are the same, only name of the server are different.
> > In logfiles on the client i have this error:
> > 2008-08-29 09:24:36:119 1688 99c PT
> > WARNING: Initialization failed for Protocol Talker Context: 0x80072ee5
> > 2008-08-29 09:24:36:119 1688 99c Report WARNING:
> > Reporter failed to upload events with hr = 80072ee5.
> >
> > client diag tool get me error: Verify WuserverURL 80072ee5 failed with hr =
> > 80072ee5.
> >
> > i can save file from ....selfupdate\iuident.cab
> > in registry i have right values.
> >
> > C ould you help mee?
> > Thanks
>
> Do your servers share a content directory? or does each have it's own?
> If each has it's own and they are sharing a URL this could be a
> problem.
>

Right pew, wrong church. Forwarded to WSUS newsgroup
(microsoft.public.windows.server.update_services) via crosspost as a
convenience to OP.

On the web:
http://www.microsoft.com/communities...pdate_services

In your newsreader:
news://msnews.microsoft.com/microsof...pdate_services
--
~PAB

bertolo wrote:
> I have two Wsus servers 3.0. One primary and second on the next side of my
> country. We have few branches. Clients, which connect to server (no
> primary), can not conect it. Both the servers have the same configuration.
> I have two GPO and both are the same, only name of the server are
> different.
> In logfiles on the client i have this error:
> 2008-08-29 09:24:36:119 1688 99c PT
> WARNING: Initialization failed for Protocol Talker Context: 0x80072ee5
> 2008-08-29 09:24:36:119 1688 99c Report
> WARNING:
> Reporter failed to upload events with hr = 80072ee5.
>
> client diag tool get me error: Verify WuserverURL 80072ee5 failed with hr
> =
> 80072ee5.
>
> i can save file from ....selfupdate\iuident.cab
> in registry i have right values.
>
> C ould you help mee?
> Thanks

> bertolo wrote:

>> I have two Wsus servers 3.0. One primary and second on the next side of
>> my
>> country. We have few branches. Clients, which connect to server (no
>> primary), can not conect it. Both the servers have the same
>> configuration.
>> I have two GPO and both are the same, only name of the server are
>> different.
>> In logfiles on the client i have this error:
>> 2008-08-29 09:24:36:119 1688 99c PT
>> WARNING: Initialization failed for Protocol Talker Context: 0x80072ee5
>> 2008-08-29 09:24:36:119 1688 99c Report
>> WARNING:
>> Reporter failed to upload events with hr = 80072ee5.
>>
>> client diag tool get me error: Verify WuserverURL 80072ee5 failed with
>> hr

0x80072ee5 - Error Internet Invalid URL

What did you configure as the URL to talk to the WSUS Server?


--
Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP
Senior Data Architect, APQC, Houston, Texas
Microsoft MVP - Software Distribution (2005-2008)

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