Microsoft Windows Vista Community Forums - Vistaheads
Recommended Download



Welcome to the Microsoft Windows Vista Community Forums - Vistaheads, YOUR Largest Resource for Windows Vista related information.

You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content and access many other special features. Registration is fast, simple and absolutely free so , join our community today!

If you have any problems with the registration process or your account login, please contact us.

Driver Scanner

wsus client cant connect to server 3.0

microsoft.public.windowsupdate






Speedup My PC
Reply
  #1 (permalink)  
Old 08-29-2008
bertolo
 

Posts: n/a
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



Reply With Quote
Sponsored Links
  #2 (permalink)  
Old 08-29-2008
madbassist1
 

Posts: n/a
Re: wsus client cant connect to server 3.0
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.
Reply With Quote
  #3 (permalink)  
Old 08-29-2008
bertolo
 

Posts: n/a
Re: wsus client cant connect to server 3.0
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.
>

Reply With Quote
  #4 (permalink)  
Old 08-29-2008
PA Bear [MS MVP]
 

Posts: n/a
Re: wsus client cant connect to server 3.0
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... date_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


Reply With Quote
  #5 (permalink)  
Old 09-11-2008
Lawrence Garvin
 

Posts: n/a
Re: wsus client cant connect to server 3.0
> 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

Reply With Quote
Reply


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
Client didn't show on WSUS Server Blue Fish microsoft.public.windowsupdate 1 08-18-2008 09:29
Does WSUS 3 SP1 Client Reboot? SB microsoft.public.windowsupdate 2 04-17-2008 20:17
cannot find the FCS client in wsus Mahmoud Amin microsoft.public.security.forefront 1 12-21-2007 16:10
Client failed to communicate with WSUS server SAFairfax microsoft.public.windowsupdate 1 12-20-2007 22:10




All times are GMT +1. The time now is 00:57.




Driver Scanner - Free Scan Now

Vistaheads.com is part of the Heads Network. See also XPHeads.com , Win7Heads.com and Win8Heads.com.


Design by Vjacheslav Trushkin for phpBBStyles.com.
Powered by vBulletin® Version 3.6.7
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Search Engine Optimization by vBSEO 3.6.0 RC 2

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120