locked
Switching WSUS server and Windows 8.1/Server2008/Server2012 clients won't connect, Windows 7/Server2003 is fine RRS feed

  • Question

  • I need to split the load of my WSUS on to another site because the amount of computers is straining the internet connection in the amount of uploads performed.

    However I'm having an issue at the second WSUS where only Windows 7 and Server 2003 clients will update...

    Windows 8.1 and Server 2008 and Server2012 won't update giving the following error codes: 8024400A and 80072EE2

    The WSUS is a Server 2012 with Local Update Publisher 1.1 installed. It works fine locally at the site but not across our WAN. 

    The clients appear in the WSUS console but fail to check for updates.

    I've tried it with the firewall turned off...  

    Both WSUS servers are using Microsoft SCEP 2012.

    Has anyone out there experienced this? Or have any suggestions to fix?

    Cheers.

    Sunday, June 1, 2014 3:54 AM

Answers

  • I'm using the IP address because it's sending updates across our WAN, each site has it's own domain.

    Either you have a working DNS... and you USE IT... or you don't.

    The fact that you have a WAN or multiple sites or multiple domains has absolutely nothing to do with having a properly implemented and working Domain Name Service.

    The fact that you have individual domains for each physical site is also something to raise one's eyebrows about. The fact that you've not properly implemented secondary DNS servers among those sites, questions the properness of using multiple domains.

    With all of that in play.... it's no surprise to me at all that something's not working in the WSUS infrastructure.


    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    • Marked as answer by Daniel JiSun Tuesday, June 10, 2014 1:54 AM
    Sunday, June 8, 2014 1:22 AM
  • Hi,

    I'm using the IP address because it's sending updates across our WAN, each site has it's own domain.

    When using the host name at the actual site of the WSUS works fine.

    Cheers

    • Marked as answer by Daniel JiSun Tuesday, June 10, 2014 1:54 AM
    Thursday, June 5, 2014 7:31 AM

All replies

  • Hi,

    The 0x80072ee2 error is an INTERNET TIMEOUT ERROR

    I think 8024400A could be the root cause.

    http://social.technet.microsoft.com/Forums/en-us/405d615c-928c-4efb-a209-1398882238e8/client-wont-join-wsus-server-code-8024400a?forum=winserverwsus

    And base on my research, this error usually relevant to WSUS version. I wonder what second WSUS means. Is this a downstream server? What is the version of upstream server? If you have a WSUS 3.2 upstream server, you may need patch your server with the following update:

    http://support.microsoft.com/kb/2734608/en-us

    Monday, June 2, 2014 12:05 PM
  • I need to split the load of my WSUS on to another site because the amount of computers is straining the internet connection in the amount of uploads performed.

    A more appropriate solution may be to configutre BITS on the client systems so they don't use more than their fair share of the available connection.

    However I'm having an issue at the second WSUS where only Windows 7 and Server 2003 clients will update...

    Let's talk about how you configured this second server. Is it a downstream server of the first server, or is it an independent upstream server? What database is it using? As always, troubleshooting WSUS issues cannot be performed from the WSUS server, you must review the client's WindowsUpdate.log ... so what's in the WindowsUpdate.log of the W8/WS2012 systems? More significantly.. what's different about the W7/WS2003 systems from the W8/WS2012 systems?

    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Tuesday, June 3, 2014 1:09 AM
  • Hi,

    Thanks for the suggestions...

    both servers are downstream servers from another server. Using the Windows database. I had a look at the client windows update log and it looked like a firewall issue. However disabling firewalls on both server and client didn't resolve the problem. 

    I rebuilt the server from scratch today with server 2012 R2 and all is working now.

    Cheers.

    Wednesday, June 4, 2014 6:53 AM
  • Hi there,

    I spoke too soon, I think I got one Windows 8 client to update yesterday by fluke. Now today it won't. 

    There's not much different between the W7 and W8 systems they both use the same antivirus. Same software but updated on W8. 

    Here is the windows update.log:

    2014-06-05 10:44:14:561 976 954 Misc ===========  Logging initialized (build: 7.9.9600.17093, tz: +1000)  ===========
    2014-06-05 10:44:14:639 976 954 Misc  = Process: C:\Windows\system32\svchost.exe
    2014-06-05 10:44:14:639 976 954 Misc  = Module: c:\windows\system32\wuaueng.dll
    2014-06-05 10:44:14:561 976 954 Service *************
    2014-06-05 10:44:14:639 976 954 Service ** START **  Service: Service startup
    2014-06-05 10:44:14:639 976 954 Service *********
    2014-06-05 10:44:15:311 976 954 IdleTmr Non-AoAc machine.  Aoac operations will be ignored.
    2014-06-05 10:44:15:311 976 954 Agent  * WU client version 7.9.9600.17093
    2014-06-05 10:44:15:326 976 954 Agent WARNING: SleepStudyTracker: Machine is non-AOAC. Sleep study tracker disabled.
    2014-06-05 10:44:15:326 976 954 Agent  * Base directory: C:\Windows\SoftwareDistribution
    2014-06-05 10:44:15:326 976 954 Agent  * Access type: No proxy
    2014-06-05 10:44:15:326 976 954 Service UpdateNetworkState Ipv6, cNetworkInterfaces = 1.
    2014-06-05 10:44:15:326 976 954 Service UpdateNetworkState Ipv4, cNetworkInterfaces = 1.
    2014-06-05 10:44:15:326 976 954 Agent  * Network state: Connected
    2014-06-05 10:44:15:326 976 954 Service UpdateNetworkState Ipv6, cNetworkInterfaces = 1.
    2014-06-05 10:44:15:326 976 954 Service UpdateNetworkState Ipv4, cNetworkInterfaces = 1.
    2014-06-05 10:44:16:123 976 954 Agent ***********  Agent: Initializing global settings cache  ***********
    2014-06-05 10:44:16:123 976 954 Agent  * Endpoint Provider: 00000000-0000-0000-0000-000000000000
    2014-06-05 10:44:16:123 976 954 Agent  * WSUS server: http://10.155.194.59:8530
    2014-06-05 10:44:16:123 976 954 Agent  * WSUS status server: http://10.155.194.59:8530
    2014-06-05 10:44:16:123 976 954 Agent  * Target group: Test Group
    2014-06-05 10:44:16:123 976 954 Agent  * Windows Update access disabled: No
    2014-06-05 10:44:16:170 976 954 WuTask WuTaskManager delay initialize completed successfully..
    2014-06-05 10:44:16:170 976 954 AU    Timer: 31DA7559-FE27-4810-8FF6-987195B1FD98, Expires 2014-06-05 00:24:13, not idle-only, not network-only
    2014-06-05 10:44:16:170 976 954 AU    Timer: CF1ABEC6-7887-4964-BB93-B2E21B31CEC1, Expires 2014-06-05 05:36:25, not idle-only, not network-only
    2014-06-05 10:44:16:170 976 954 AU    Timer: 29A863E7-8609-4D1E-B7CD-5668F857F1DB, Expires 2014-06-05 05:36:25, not idle-only, not network-only
    2014-06-05 10:44:16:170 976 954 Report CWERReporter::Init succeeded
    2014-06-05 10:44:16:170 976 954 Agent ***********  Agent: Initializing Windows Update Agent  ***********
    2014-06-05 10:44:16:170 976 954 DnldMgr Download manager restoring 0 downloads
    2014-06-05 10:44:16:170 976 954 AU ###########  AU: Initializing Automatic Updates  ###########
    2014-06-05 10:44:16:170 976 954 AU Additional Service {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} with Approval type {Scheduled} added to AU services list
    2014-06-05 10:44:16:170 976 954 AU AIR Mode is disabled
    2014-06-05 10:44:16:170 976 954 AU  # Policy Driven Provider: http://10.155.194.59:8530
    2014-06-05 10:44:16:170 976 954 AU  # Detection frequency: 22
    2014-06-05 10:44:16:170 976 954 AU  # Target group: Test Group
    2014-06-05 10:44:16:170 976 954 AU  # Approval type: Scheduled (Policy)
    2014-06-05 10:44:16:170 976 954 AU  # Auto-install minor updates: Yes (Policy)
    2014-06-05 10:44:16:170 976 954 AU  # ServiceTypeDefault: Service 117CAB2D-82B1-4B5A-A08C-4D62DBEE7782 Approval type: (Scheduled)
    2014-06-05 10:44:16:170 976 954 AU  # Will interact with non-admins (Non-admins are elevated (Policy))
    2014-06-05 10:44:16:186 976 954 AU WARNING: Failed to get Wu Exemption info from NLM, assuming not exempt, error = 0x80070032
    2014-06-05 10:44:16:186 976 954 AU AU finished delayed initialization
    2014-06-05 10:44:16:202 976 954 AU Adding timer: 
    2014-06-05 10:44:16:202 976 954 AU    Timer: 31DA7559-FE27-4810-8FF6-987195B1FD98, Expires 2014-06-05 03:47:12, not idle-only, not network-only
    2014-06-05 10:44:16:217 976 99c DnldMgr Asking handlers to reconcile their sandboxes
    2014-06-05 10:45:17:562 976 954 AU ReAttemptDownloadsAsUserIfNecessary, No calls in download progress.
    2014-06-05 10:45:31:453 976 778 IdleTmr Incremented idle timer priority operation counter to 1
    2014-06-05 10:45:34:562 976 778 AU Triggering AU detection through DetectNow API
    2014-06-05 10:45:34:562 976 778 AU Additional Service {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} with Approval type {Scheduled} added to AU services list
    2014-06-05 10:45:34:562 976 778 AU Triggering Online detection (interactive)
    2014-06-05 10:45:34:562 976 778 AU Adding timer: 
    2014-06-05 10:45:34:562 976 778 AU    Timer: 31DA7559-FE27-4810-8FF6-987195B1FD98, Expires 2014-06-05 00:45:34, not idle-only, not network-only
    2014-06-05 10:45:34:609 976 954 AU #############
    2014-06-05 10:45:34:609 976 954 AU ## START ##  AU: Search for updates
    2014-06-05 10:45:34:609 976 954 AU #########
    2014-06-05 10:45:34:609 976 954 AU Additional Service {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} with Approval type {Scheduled} added to AU services list
    2014-06-05 10:45:34:609 976 954 IdleTmr WU operation (CSearchCall::Init ID 1) started; operation # 15; does use network; is not at background priority
    2014-06-05 10:45:34:609 976 954 IdleTmr Incremented idle timer priority operation counter to 2
    2014-06-05 10:45:34:797 976 954 Report ***********  Report: Initializing static reporting data  ***********
    2014-06-05 10:45:34:797 976 954 Report  * OS Version = 6.3.9600.0.0.65792
    2014-06-05 10:45:34:797 976 954 Report  * OS Product Type = 0x00000004
    2014-06-05 10:45:34:813 976 954 Report  * Computer Brand = Microsoft Corporation
    2014-06-05 10:45:34:813 976 954 Report  * Computer Model = Virtual Machine
    2014-06-05 10:45:34:813 976 954 Report  * Platform Role = 1
    2014-06-05 10:45:34:813 976 954 Report  * AlwaysOn/AlwaysConnected (AOAC) = 0
    2014-06-05 10:45:34:813 976 954 Report  * Bios Revision = 090004 
    2014-06-05 10:45:34:813 976 954 Report  * Bios Name = BIOS Date: 03/19/09 22:51:32  Ver: 09.00.04
    2014-06-05 10:45:34:813 976 954 Report  * Bios Release Date = 2009-03-19T00:00:00
    2014-06-05 10:45:34:813 976 954 Report  * Bios Sku Number unavailable.
    2014-06-05 10:45:34:813 976 954 Report  * Bios Vendor = American Megatrends Inc.
    2014-06-05 10:45:34:813 976 954 Report  * Bios Family unavailable.
    2014-06-05 10:45:34:828 976 954 Report  * Bios Major Release unavailable.
    2014-06-05 10:45:34:828 976 954 Report  * Bios Minor Release unavailable.
    2014-06-05 10:45:34:828 976 954 Report  * Locale ID = 3081
    2014-06-05 10:45:35:578 976 954 Agent *** START ***  Queueing Finding updates [CallerId = AutomaticUpdatesWuApp  Id = 1]
    2014-06-05 10:45:35:609 976 954 AU <<## SUBMITTED ## AU: Search for updates  [CallId = {CDA6DEA2-9874-4DB5-AAA7-9A05D933C012} ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}]
    2014-06-05 10:45:35:609 976 fc4 Agent ***  END  ***  Queueing Finding updates [CallerId = AutomaticUpdatesWuApp  Id = 1]
    2014-06-05 10:45:35:609 976 fc4 Agent *************
    2014-06-05 10:45:35:609 976 fc4 Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdatesWuApp  Id = 1]
    2014-06-05 10:45:35:609 976 fc4 Agent *********
    2014-06-05 10:45:35:609 976 fc4 Agent  * Online = Yes; Ignore download priority = No
    2014-06-05 10:45:35:609 976 fc4 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"
    2014-06-05 10:45:35:609 976 fc4 Agent  * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2014-06-05 10:45:35:609 976 fc4 Agent  * Search Scope = {Machine & All Users}
    2014-06-05 10:45:35:609 976 fc4 Agent  * Caller SID for Applicability: S-1-5-21-1323361640-3159480285-1943353560-1532
    2014-06-05 10:45:35:609 976 fc4 Agent  * RegisterService is set
    2014-06-05 10:45:35:625 976 fc4 EP Got WSUS Client/Server URL: "http://10.155.194.59:8530/ClientWebService/client.asmx"
    2014-06-05 10:45:35:641 976 fc4 Setup Checking for agent SelfUpdate
    2014-06-05 10:45:35:641 976 fc4 Setup Client version: Core: 7.9.9600.17093  Aux: 7.9.9600.17093
    2014-06-05 10:45:35:641 976 fc4 EP Got WSUS SelfUpdate URL: "http://10.155.194.59:8530/selfupdate"
    2014-06-05 10:45:35:672 976 fc4 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab with dwProvFlags 0x00000080:
    2014-06-05 10:45:35:734 976 fc4 Misc Microsoft signed: NA
    2014-06-05 10:45:35:734 976 fc4 Misc Infrastructure signed: Yes
    2014-06-05 10:45:35:734 976 fc4 Misc WARNING: Cab does not contain correct inner CAB file.
    2014-06-05 10:45:35:734 976 fc4 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab with dwProvFlags 0x00000080:
    2014-06-05 10:45:35:734 976 fc4 Misc Microsoft signed: NA
    2014-06-05 10:45:35:750 976 fc4 Misc Infrastructure signed: Yes
    2014-06-05 10:45:35:766 976 fc4 Setup Skipping SelfUpdate check based on the /SKIP directive in wuident
    2014-06-05 10:45:35:766 976 fc4 Setup SelfUpdate check completed.  SelfUpdate is NOT required.
    2014-06-05 10:45:35:907 976 fc4 PT +++++++++++  PT: Synchronizing server updates  +++++++++++

    --continued--


    Thursday, June 5, 2014 1:53 AM
  • 2014-06-05 10:45:35:907  976 fc4 PT   + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://10.155.194.59:8530/ClientWebService/client.asmx
    2014-06-05 10:45:35:907  976 fc4 PT WARNING: Cached cookie has expired or new PID is available
    2014-06-05 10:45:35:907  976 fc4 EP Got WSUS SimpleTargeting URL: "http://10.155.194.59:8530"
    2014-06-05 10:45:35:907  976 fc4 IdleTmr WU operation (CAuthorizationCookieWrapper::InitializeSimpleTargetingCookie) started; operation # 16; does use network; is at background priority
    2014-06-05 10:45:35:907  976 fc4 PT Initializing simple targeting cookie, clientId = dd6f0741-5343-4959-bfb1-a7d0d1cf5e85, target group = Test Group, DNS name = win8test.domain.wan
    2014-06-05 10:45:35:907  976 fc4 PT   Server URL = http://10.155.194.59:8530/SimpleAuthWebService/SimpleAuth.asmx
    2014-06-05 10:45:35:953  976 fc4 IdleTmr WU operation (CAuthorizationCookieWrapper::InitializeSimpleTargetingCookie, operation # 16) stopped; does use network; is at background priority
    2014-06-05 10:45:35:953  976 fc4 IdleTmr WU operation (CAgentProtocolTalker::GetCookie_WithRecovery) started; operation # 17; does use network; is at background priority
    2014-06-05 10:45:35:984  976 fc4 IdleTmr WU operation (CAgentProtocolTalker::GetCookie_WithRecovery, operation # 17) stopped; does use network; is at background priority
    2014-06-05 10:45:36:000  976 fc4 Agent Reading cached app categories using lifetime 604800 seconds
    2014-06-05 10:45:36:000  976 fc4 Agent Read 0 cached app categories
    2014-06-05 10:45:36:000  976 fc4 Agent SyncUpdates adding 0 visited app categories
    2014-06-05 10:45:38:078  976 fc4 IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started; operation # 18; does use network; is at background priority
    2014-06-05 10:50:48:104  976 fc4 WS WARNING: Nws Failure: errorCode=0x803d0006
    2014-06-05 10:50:48:104  976 fc4 WS WARNING: Original error code: 0x80072ee2
    2014-06-05 10:50:48:104  976 fc4 WS WARNING: There was an error communicating with the endpoint at 'http://10.155.194.59:8530/ClientWebService/client.asmx'.
    2014-06-05 10:50:48:104  976 fc4 WS WARNING: There was an error receiving the HTTP reply.
    2014-06-05 10:50:48:104  976 fc4 WS WARNING: The operation did not complete within the time allotted.
    2014-06-05 10:50:48:104  976 fc4 WS WARNING: The operation timed out
    2014-06-05 10:50:48:104  976 fc4 WS WARNING: MapToSusHResult mapped Nws error 0x803d0006 to 0x8024401c
    2014-06-05 10:50:48:104  976 fc4 WS WARNING: Web service call failed with hr = 8024401c.
    2014-06-05 10:50:48:104  976 fc4 WS WARNING: Current service auth scheme='None'.
    2014-06-05 10:50:48:104  976 fc4 WS WARNING: Proxy List used: '(null)', Bypass List used: '(null)', Last Proxy used: '(null)', Last auth Schemes used: 'None'.
    2014-06-05 10:50:48:104  976 fc4 WS FATAL: OnCallFailure failed with hr=0X8024401C
    2014-06-05 10:50:48:104  976 fc4 WS WARNING: NWS retry 1 for transient error 0x8024401C
    2014-06-05 10:52:56:101  976 fc4 WS WARNING: Nws Failure: errorCode=0x803d0006
    2014-06-05 10:52:56:101  976 fc4 WS WARNING: Original error code: 0x80072ee2
    2014-06-05 10:52:56:101  976 fc4 WS WARNING: There was an error communicating with the endpoint at 'http://10.155.194.59:8530/ClientWebService/client.asmx'.
    2014-06-05 10:52:56:101  976 fc4 WS WARNING: There was an error receiving the HTTP reply.
    2014-06-05 10:52:56:101  976 fc4 WS WARNING: The operation did not complete within the time allotted.
    2014-06-05 10:52:56:101  976 fc4 WS WARNING: There was an error communicating with the endpoint at 'http://10.155.194.59:8530/ClientWebService/client.asmx'.
    2014-06-05 10:52:56:101  976 fc4 WS WARNING: There was an error receiving the HTTP reply.
    2014-06-05 10:52:56:101  976 fc4 WS WARNING: The operation did not complete within the time allotted.
    2014-06-05 10:52:56:101  976 fc4 WS WARNING: The operation timed out
    2014-06-05 10:52:56:101  976 fc4 WS WARNING: MapToSusHResult mapped Nws error 0x803d0006 to 0x8024401c
    2014-06-05 10:52:56:101  976 fc4 WS WARNING: Web service call failed with hr = 8024401c.
    2014-06-05 10:52:56:101  976 fc4 WS WARNING: Current service auth scheme='None'.
    2014-06-05 10:52:56:101  976 fc4 WS WARNING: Proxy List used: '(null)', Bypass List used: '(null)', Last Proxy used: '(null)', Last auth Schemes used: 'None'.
    2014-06-05 10:52:56:101  976 fc4 WS FATAL: OnCallFailure failed with hr=0X8024401C
    2014-06-05 10:52:56:101  976 fc4 WS WARNING: NWS retry 2 for transient error 0x8024401C
    2014-06-05 10:54:13:604  400 6d4 Misc ===========  Logging initialized (build: 7.9.9600.17093, tz: +1000)  ===========
    2014-06-05 10:54:13:604  400 6d4 Misc   = Process: C:\Program Files\Microsoft Security Client\MpCmdRun.exe
    2014-06-05 10:54:13:604  400 6d4 Misc   = Module: C:\Windows\System32\wuapi.dll
    2014-06-05 10:54:13:604  400 6d4 COMAPI -------------
    2014-06-05 10:54:13:604  400 6d4 COMAPI -- START --  COMAPI: Init Search [ClientId = System Center Endpoint Protection (DDEFDD14-250E-4DC8-A0B3-9D667EC5D8EB)]
    2014-06-05 10:54:13:604  400 6d4 COMAPI ---------
    2014-06-05 10:54:13:604  400 6d4 COMAPI -------------
    2014-06-05 10:54:13:604  400 6d4 COMAPI -- START --  COMAPI: Search [ClientId = System Center Endpoint Protection (DDEFDD14-250E-4DC8-A0B3-9D667EC5D8EB)]
    2014-06-05 10:54:13:604  400 6d4 COMAPI ---------
    2014-06-05 10:54:13:604  976 3d8 IdleTmr WU operation (CSearchCall::Init ID 2) started; operation # 24; does use network; is not at background priority
    2014-06-05 10:54:13:604  976 3d8 IdleTmr Incremented idle timer priority operation counter to 3
    2014-06-05 10:54:13:604  976 3d8 Agent *** START ***  Queueing Finding updates [CallerId = System Center Endpoint Protection (DDEFDD14-250E-4DC8-A0B3-9D667EC5D8EB)  Id = 2]
    2014-06-05 10:54:13:604  400 6d4 COMAPI <<-- SUBMITTED -- COMAPI: Search [ClientId = System Center Endpoint Protection (DDEFDD14-250E-4DC8-A0B3-9D667EC5D8EB)]
    2014-06-05 10:55:17:561  976 954 AU User login event timer expired for session id: 1.
    2014-06-05 10:55:17:561  976 954 AU #############
    2014-06-05 10:55:17:561  976 954 AU ## START ##  AU: Install updates
    2014-06-05 10:55:17:561  976 954 AU #########
    2014-06-05 10:55:17:561  976 954 AU   # Initiating scheduled install
    2014-06-05 10:55:17:623  976 954 AU WARNING: There are no approved updates to install
    2014-06-05 10:55:17:623  976 954 AU   # Exit code = 0x8024000C
    2014-06-05 10:55:17:623  976 954 AU #########
    2014-06-05 10:55:17:623  976 954 AU ##  END  ##  AU: Install updates
    2014-06-05 10:55:17:623  976 954 AU ############# 

    Cheers

    Thursday, June 5, 2014 1:53 AM
  • 2014-06-05 10:44:16:123 976 954 Agent * WSUS server: http://10.155.194.59:8530
    2014-06-05 10:44:16:123 976 954 Agent * WSUS status server: http://10.155.194.59:8530

    As I've stated elsewhere, I'm always naturally suspicious of implementations that use IP Addresses instead of hostnames for the WSUS URL. At a minimum it suggests a dysfunctional implementation of DNS, which implicates many other possible issues.

    2014-06-05 10:50:48:104 976 fc4 WS WARNING: There was an error communicating with the endpoint at 'http://10.155.194.59:8530/ClientWebService/client.asmx'.
    2014-06-05 10:50:48:104 976 fc4 WS WARNING: The operation timed out

    Luckily, the WUA v7.9 now gives us much simpler descriptions of what is breaking down.


    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Thursday, June 5, 2014 6:38 AM
  • Hi,

    I'm using the IP address because it's sending updates across our WAN, each site has it's own domain.

    When using the host name at the actual site of the WSUS works fine.

    Cheers

    • Marked as answer by Daniel JiSun Tuesday, June 10, 2014 1:54 AM
    Thursday, June 5, 2014 7:31 AM
  • I'm using the IP address because it's sending updates across our WAN, each site has it's own domain.

    Either you have a working DNS... and you USE IT... or you don't.

    The fact that you have a WAN or multiple sites or multiple domains has absolutely nothing to do with having a properly implemented and working Domain Name Service.

    The fact that you have individual domains for each physical site is also something to raise one's eyebrows about. The fact that you've not properly implemented secondary DNS servers among those sites, questions the properness of using multiple domains.

    With all of that in play.... it's no surprise to me at all that something's not working in the WSUS infrastructure.


    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    • Marked as answer by Daniel JiSun Tuesday, June 10, 2014 1:54 AM
    Sunday, June 8, 2014 1:22 AM