locked
Clients can't connect to internal wsus RRS feed

  • Question

  • Hi All 

    i install windows server 2012 r2  with wsus rule

    i configure every thing and group policy  

    but when i go to client pc and check update i got this error


    IT Helpdesk

    Wednesday, August 6, 2014 2:54 PM

Answers

  • 0x80244019 is an HTTP 404, which means you've configured an incorrect URL for the WSUS server.

    Inasmuch as you've deployed it on WS2012R2, and WSUS installs to port 8530 by default, my educated guess (and the experience of thousands before you) is that you failed to include the port suffix on the URL in your GPO.

    http://wsusServerName:8530 would be the correct syntax.


    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 MandoesaM Thursday, August 7, 2014 9:14 AM
    Wednesday, August 6, 2014 4:30 PM
  • but why clients pc take along time to registered in side targeting group

    What are you considering "a long time"?

    Depending on what you did, and in what order you did it, a client could conceivably take up to 22 hours before it appears in a WSUS server; potentially longer depending on what's happening on the client.


    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 MandoesaM Wednesday, August 20, 2014 11:09 AM
    Friday, August 8, 2014 12:38 AM
  • but i have question   why  my client ip address show ipv6   not ipv4   Cause i use ipv4 not ipv6

    Because IPv6 is enabled by default, and used preferentially by WSUS. If you want the display to show IPv4 addresses you'll need to properly disable IPv6 from the client systems, and then delete the computers from WSUS and let them reregister.

    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 MandoesaM Monday, August 25, 2014 11:01 AM
    Thursday, August 21, 2014 2:57 PM

All replies

  • 0x80244019 is an HTTP 404, which means you've configured an incorrect URL for the WSUS server.

    Inasmuch as you've deployed it on WS2012R2, and WSUS installs to port 8530 by default, my educated guess (and the experience of thousands before you) is that you failed to include the port suffix on the URL in your GPO.

    http://wsusServerName:8530 would be the correct syntax.


    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 MandoesaM Thursday, August 7, 2014 9:14 AM
    Wednesday, August 6, 2014 4:30 PM
  • Thank You Working For ME  but why clients pc  take along time to registered in side targeting group 


    IT Helpdesk

    Thursday, August 7, 2014 9:14 AM
  • but why clients pc take along time to registered in side targeting group

    What are you considering "a long time"?

    Depending on what you did, and in what order you did it, a client could conceivably take up to 22 hours before it appears in a WSUS server; potentially longer depending on what's happening on the client.


    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 MandoesaM Wednesday, August 20, 2014 11:09 AM
    Friday, August 8, 2014 12:38 AM
  • Thank You Very Much 

    Working ;)

    but i have question   why  my client ip address show ipv6   not ipv4   Cause i use ipv4  not ipv6


    IT Helpdesk

    Wednesday, August 20, 2014 11:12 AM
  • but i have question   why  my client ip address show ipv6   not ipv4   Cause i use ipv4 not ipv6

    Because IPv6 is enabled by default, and used preferentially by WSUS. If you want the display to show IPv4 addresses you'll need to properly disable IPv6 from the client systems, and then delete the computers from WSUS and let them reregister.

    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 MandoesaM Monday, August 25, 2014 11:01 AM
    Thursday, August 21, 2014 2:57 PM