none
Windows Server 2012 R2 clients can not connect to Windows Server 2012 R2 WSUS Server

    Question

  • Hello

    I have a brand new lab setup. 

    Windows Sever 2012 R2 Datacenter WSUS Server

    Windows Sever 2012 R2 Datacenter Member Servers

    The member servers can not connect to the WSUS sever. I've attached the log from a member server below. I have verified that http://sndeploy01:80/ClientWebService/client.asmx DOES exist. Firewalls are not an issue (all off). Everything else is vanilla. You will see that I have specified port 80. Leaving it as default does not work either.

    Additionally the server can't self-connect.

    I've been reading lots about Hotfixes for Server 2012 R1 and Windows 8 but I cant belive the same error would have been carried in to a brand new release?

    Hopefully I'm doing something stupid. Any ideas?

    Many thanks

    2013-10-24 18:54:36:282 768 814 PT  + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://sndeploy01:80/ClientWebService/client.asmx

    2013-10-24 18:54:36:329 768 814 WS WARNING: Nws Failure: errorCode=0x803d000d
    2013-10-24 18:54:36:329 768 814 WS WARNING: There was an error communicating with the endpoint at 'http://sndeploy01:80/ClientWebService/client.asmx'.
    2013-10-24 18:54:36:329 768 814 WS WARNING: The server returned HTTP status code '404 (0x194)' wdith text 'Not Found'.
    2013-10-24 18:54:36:329 768 814 WS WARNING: The requested resource was not found.
    2013-10-24 18:54:36:329 768 814 WS WARNING: Web service call failed with hr = 80244019.
    2013-10-24 18:54:36:329 768 814 WS WARNING: Current service auth scheme='None'.
    2013-10-24 18:54:36:329 768 814 WS WARNING: Proxy List used: '(null)', Bypass List used: '(null)', Last Proxy used: '(null)', Last auth Schemes used: 'None'.
    2013-10-24 18:54:36:329 768 814 WS FATAL: OnCallFailure(hrCall, m_error) failed with hr=0x80244019
    2013-10-24 18:54:36:329 768 814 PT WARNING: PTError: 0x80244019
    2013-10-24 18:54:36:329 768 814 PT WARNING: GetConfig_WithRecovery failed: 0x80244019
    2013-10-24 18:54:36:329 768 814 PT WARNING: RefreshConfig failed: 0x80244019
    2013-10-24 18:54:36:329 768 814 PT WARNING: RefreshPTState failed: 0x80244019
    2013-10-24 18:54:36:329 768 814 PT WARNING: Sync of Updates: 0x80244019
    2013-10-24 18:54:36:329 768 814 PT WARNING: SyncServerUpdatesInternal failed: 0x80244019
    2013-10-24 18:54:36:329 768 814 Agent  * WARNING: Failed to synchronize, error = 0x80244019
    2013-10-24 18:54:36:329 768 814 Agent  * WARNING: Exit code = 0x80244019



    -------------------- Microsoft Certified Solutions Associate (MCSA) - Windows Server® 2008 Microsoft Certified Solutions Associate (MCSA) - Windows 7® Microsoft Certified IT Professional (MCITP): Enterprise Administrator Microsoft Certified IT Professional(MCITP): Server Administrator Microsoft Certified IT Professional (MCITP): Enterprise Desktop Support Technician 7

    Thursday, October 24, 2013 8:58 PM

Answers

  • WSUS v6 installs to port 8530. You have configured the WSUS URL incorrectly.

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

    Thursday, October 24, 2013 9:17 PM
    Moderator

All replies

  • WSUS v6 installs to port 8530. You have configured the WSUS URL incorrectly.

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

    Thursday, October 24, 2013 9:17 PM
    Moderator
  • Great stuff! Instant fix. Thank you!

    -------------------- Microsoft Certified Solutions Associate (MCSA) - Windows Server® 2008 Microsoft Certified Solutions Associate (MCSA) - Windows 7® Microsoft Certified IT Professional (MCITP): Enterprise Administrator Microsoft Certified IT Professional(MCITP): Server Administrator Microsoft Certified IT Professional (MCITP): Enterprise Desktop Support Technician 7

    Thursday, October 24, 2013 9:29 PM
  • Is this the same port that the WSUS server uses to connect with Microsoft Update to get update content? i.e. is there anything that needs opened up between the WSUS server and the Internet for it to receive updates?

    TIA

    Tuesday, May 27, 2014 5:54 PM
  • Is this the same port that the WSUS server uses to connect with Microsoft Update to get update content?

    No.

    The connection TO Microsoft is always on 80/443. The metadata synchronization is performed via SSL on port 443; the content download is performed via HTTP on port 80.


    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.

    Wednesday, May 28, 2014 10:30 PM
    Moderator
  • Lawrence,

    May I ask a follow up question?  I'm having a similar error, but mine is configured correctly with port 8530.  This server is in a DMZ and reaching back to a WSUS server on the internal.  We have port 8530 opened on firewall, and have verified connectivity via telnet (icmp is off).  When I run wuauclt -detectnow and look at the windowsupdate.log, it's telling me there was an error connecting to the endpoint.  Another line tells me there was an error receiving the http reply.  Why is it replying on port 80?  I thought everything was going over 8530?

    Thanks,

    CP


    Craig Patton

    Thursday, October 05, 2017 12:16 PM
  • Lawrence,

    May I ask a follow up question?  I'm having a similar error, but mine is configured correctly with port 8530.  This server is in a DMZ and reaching back to a WSUS server on the internal.  We have port 8530 opened on firewall, and have verified connectivity via telnet (icmp is off).  When I run wuauclt -detectnow and look at the windowsupdate.log, it's telling me there was an error connecting to the endpoint.  Another line tells me there was an error receiving the http reply.  Why is it replying on port 80?  I thought everything was going over 8530?

    Thanks,

    CP


    Craig Patton

    First, Lawrence passed away a few years ago, suddenly, so he won't be responding.

    Second, there have been recently some reports of some funky things happening with WSUS and ports. The permanent fix for this seems to be to toggle the usecustomwebsite using wsusutil and then toggling it back.

    so for you, from an Admin cmd prompt,

    "%ProgramFiles%\Update Services\Tools\wsusutil.exe" usecustomwebsite off
    "%ProgramFiles%\Update Services\Tools\wsusutil.exe" usecustomwebsite on


    Adam Marshall, MCSE: Security
    http://www.adamj.org

    Thursday, October 05, 2017 12:56 PM
  • Adam,

    Thanks for your help, and sorry to hear about Lawrence.  If you don't mind, I'm still having an issue.  I don't have a \tools directory where you indicated.  But I found the wsusutil.exe in c:\windows\winsxs\....

    However, when I try to run it as you indicated, it says it cannot start due to incompatibility with 64 bit versions of windows.  (I'm using Server 2012 R2).  Why would they put a 32 bit version of the utility on a 64 bit server that doesn't work?

    Thanks

    CP


    Craig Patton

    Thursday, October 05, 2017 2:40 PM
  • Adam,

    Thanks for your help, and sorry to hear about Lawrence.  If you don't mind, I'm still having an issue.  I don't have a \tools directory where you indicated.  But I found the wsusutil.exe in c:\windows\winsxs\....

    However, when I try to run it as you indicated, it says it cannot start due to incompatibility with 64 bit versions of windows.  (I'm using Server 2012 R2).  Why would they put a 32 bit version of the utility on a 64 bit server that doesn't work?

    Thanks

    CP


    Craig Patton

    Are you looking on the WSUS Server itself? Mine is Server 2012 R2 as well and the file does exist in

    "C:\Program Files\Update Services\Tools\WsusUtil.exe"


    Adam Marshall, MCSE: Security
    http://www.adamj.org

    Thursday, October 05, 2017 11:34 PM