asked on

WSUS - Clients cannot connect

Clients cannot connect to WSUS server

REsults of windowupdates.log (wuauclt /resetauthorization /detectnow)

13-03-07      10:23:55:496       948      1428      AU      Triggering AU detection through DetectNow API
2013-03-07      10:23:55:496       948      1428      AU      Triggering Online detection (non-interactive)
2013-03-07      10:23:55:496       948      19a4      AU      #############
2013-03-07      10:23:55:496       948      19a4      AU      ## START ## AU: Search for updates
2013-03-07      10:23:55:496       948      19a4      AU      #########
2013-03-07      10:23:55:496       948      19a4      AU      <<## SUBMITTED ## AU: Search for updates [CallId = {D0C94427-5901-4B49-8238-219A7E2B67A7}]
2013-03-07      10:23:55:496       948      1454      Agent      *************
2013-03-07      10:23:55:496       948      1454      Agent      ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
2013-03-07      10:23:55:496       948      1454      Agent      *********
2013-03-07      10:23:55:496       948      1454      Agent        * Online = Yes; Ignore download priority = No
2013-03-07      10:23:55:496       948      1454      Agent        * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2013-03-07      10:23:55:496       948      1454      Agent        * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2013-03-07      10:23:55:496       948      1454      Agent        * Search Scope = {Machine}
2013-03-07      10:23:55:496       948      1454      Setup      Checking for agent SelfUpdate
2013-03-07      10:23:55:496       948      1454      Setup      Client version: Core: 7.6.7600.256 Aux: 7.6.7600.256
2013-03-07      10:24:18:881       948      1454      Misc      WARNING: Send failed with hr = 80072ee2.
2013-03-07      10:24:18:881       948      1454      Misc      WARNING: SendRequest failed with hr = 80072ee2. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
2013-03-07      10:24:18:881       948      1454      Misc      WARNING: WinHttp: SendRequestUsingProxy failed for <http://192.166.166.167/selfupdate/wuident.cab>. error 0x80072ee2
2013-03-07      10:24:18:881       948      1454      Misc      WARNING: WinHttp: SendRequestToServerForFileInformation MakeRequest failed. error 0x80072ee2
2013-03-07      10:24:18:881       948      1454      Misc      WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80072ee2
2013-03-07      10:24:18:881       948      1454      Misc      WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80072ee2
2013-03-07      10:24:42:578       948      1454      Misc      WARNING: Send failed with hr = 80072ee2.
2013-03-07      10:24:42:578       948      1454      Misc      WARNING: SendRequest failed with hr = 80072ee2. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
2013-03-07      10:24:42:578       948      1454      Misc      WARNING: WinHttp: SendRequestUsingProxy failed for <http://192.166.166.167/selfupdate/wuident.cab>. error 0x80072ee2
2013-03-07      10:24:42:578       948      1454      Misc      WARNING: WinHttp: SendRequestToServerForFileInformation MakeRequest failed. error 0x80072ee2
2013-03-07      10:24:42:578       948      1454      Misc      WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80072ee2
2013-03-07      10:24:42:578       948      1454      Misc      WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80072ee2

Member_2_6492660_1

take a look at this

http://social.technet.microsoft.com/Forums/en-US/winserverwsus/thread/1005edf5-2e7f-4c8b-adf5-a53d428ba39d

Don

0x80072ee2

Most likely you have your GPO incorrectly configured

Is your WSUS server using port 8530 ???

SOLUTION

Tej

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Don

Many times there are chances that in your registry pointing is to different IP which is not expected.

Same thing as my comment

Most likely you have your GPO incorrectly configured

danberry1010

ASKER

I have checked GPO and the IP address of the WSUS server. Each appear to be correct.

When I disable the internal WSUS server in the GPO, the updates work correctly. When I enable the internal WSUS server on the GPO, it does not work. Even when I point the WSUS server to itself for updates, the updates fail.

SOLUTION

Don

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Member_2_6492660_1

OK

What Server OS is running?

What version of WSUS ?

Are you using SQL or internal database?

run this post results

wsusutil checkhealth

Don

Is your WSUS server using port 8530 ???

danberry1010

ASKER

Windows 2008 R2
WSUS version 3
internal database.
Not sure which port is being used, but I opened port 8530 on the server firewall, as well as port 80.
WSUS 3.0 with SP2 has version 3.2.7600.226

SOLUTION

Member_2_6492660_1

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

ASKER CERTIFIED SOLUTION

Don

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Don

Windows 2008 R2

Odds are very high that you are using port 8530

change your gpo to

http://192.166.166.167:8530

Don

Any luck ?

danberry1010

ASKER

Not sure why or what, but the WSUS started seeing, updating and reporting clients.
I checked every setting multiple times, then frustrated I disabled the internal WSUS settings in the GPO. I installed two updates from Microsoft and enabled the internal WSUS settings in the GPO. ( I did not specific port :8530 in the internal IP address of the WSUS server). A few hours later I checked the WSUS server and lo and behold, the clients started updating.