none
WSUS console is not opening after configuring on SSL (Https ) -8531 port - can some one please help to fix the issues ?

    Frage

  • Hi,

    I m configuring wsus on windows server 2012 R2 standalone ( workgroup) on port 8351.  i got wildcard certificate from my trusted Root CA authority. I have imported into the local computer Trusted Root CA store. after that i have binding to port 8531 with crets. SSL for the following virtual roots only:SimpleAuthWebService DSSAuthWebService ServerSyncWebService APIRemoting30 ClientWebService

    after that c:\Program Files\Update Services\Tools”\ WSUSUtil.exe configuressl fqdn name , after that i have rested server and try to open WSUS console and getting error "Error connection error "

    getting error on event viewer also - 

    Windows Update Services – Multiple Errors in Event Viewer – Event ID 12052,12042, 12022, 12032, 12012, 12002,13042

    really appreciate if you can help to fix the issues.  

    Mittwoch, 6. Juni 2018 13:34

Antworten

  • Hi Rakpatel2,

    Thanks for your detailed information.

    For this issue, it is suggested to join a domain to configure WSUS. So please try to join a domain and see whether it works.

    Meanwhile, I have do some research and it maybe SSL handshake fails with the name check. You could configure the Primary DNS Suffix to match the name of the server’s FQDN (the same as on the SSL certificate). The detail steps as following:

    1. Go to Control Panel -> System and Security -> System 
    2. under Computer Name, Domain and Workgroup Settings, click Change Settings.
    3. Then, you can set the Primary DNS Suffix for your server

    Here is a link for your reference:

    http://blog.viitaila.fi/2013/12/12/error-connecting-to-a-stand-alone-wsus-server-using-ssl/

    Note: This is a 3rd party link for your reference only.

    Hope above information helps.

    Best Regards

    Tina Cao

    ===================

    Please remember to mark the replies as answers if they help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    Donnerstag, 7. Juni 2018 02:56

Alle Antworten

  • Hi Rakpatel2,

    Thanks for your detailed information.

    For this issue, it is suggested to join a domain to configure WSUS. So please try to join a domain and see whether it works.

    Meanwhile, I have do some research and it maybe SSL handshake fails with the name check. You could configure the Primary DNS Suffix to match the name of the server’s FQDN (the same as on the SSL certificate). The detail steps as following:

    1. Go to Control Panel -> System and Security -> System 
    2. under Computer Name, Domain and Workgroup Settings, click Change Settings.
    3. Then, you can set the Primary DNS Suffix for your server

    Here is a link for your reference:

    http://blog.viitaila.fi/2013/12/12/error-connecting-to-a-stand-alone-wsus-server-using-ssl/

    Note: This is a 3rd party link for your reference only.

    Hope above information helps.

    Best Regards

    Tina Cao

    ===================

    Please remember to mark the replies as answers if they help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    Donnerstag, 7. Juni 2018 02:56
  • thanks a lot for your response.

    sorry i was keep busying trying to resolve the issues. i resolve the issues with same way. 

    if i would check your response before then i would at lest save my few days.

    appreciate for your response.  

    Thanks. 

    Mittwoch, 13. Juni 2018 23:37