none
TLS Handshake RRS feed

  • Question

  • Hi,

    I want to have a HTTPS connection from micro-controller to IIS server.

    IIS webserver works fine when I connect through an Internet Browser. Micro-Controller also works fine when  it connects to other Web-Servers for example NginX.

    but without any changes on IIS, I cannot connect from micro-controller to IIS . When I searched through the logs in Event Viewer I found this error message : 

    "A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection. The TLS protocol defined fatal alert code is 51.

       Target name:

    The TLS alert registry can be found at http://www.iana.org/assignments/tls-parameters/tls-parameters.xhtml#tls-parameters-6"

    I also coded a Socket Server in C# using SslStream.AuthenticateAsServer to replace IIS server. but I get this Exception:

    "Exception: A call to SSPI failed, see inner exception.

    Inner exception: The token supplied to the function is invalid

    If there was an error with Certificate, I wouldn't have been able to connect IIS over Internet Explorer.

    If anyone has any Idea, when these two error messages occur?

    I'd appreciate your help.

    Thursday, June 7, 2018 3:06 PM

All replies

  • Hi arashios,

    Thank you for posting here.

    Since your question is more related to IIS, you could post a new thread in IIS forum for suitable support.

    https://forums.iis.net/

    The CLR Forum discuss and ask questions about .NET Framework Base Classes (BCL) such as Collections, I/O, Regigistry, Globalization, Reflection. Also discuss all the other Microsoft libraries that are built on or extend the .NET Framework, including Managed Extensibility Framework (MEF), Charting Controls, CardSpace, Windows Identity Foundation (WIF), Point of Sale (POS), Transactions.

    Best Regards,

    Wendy


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Monday, June 11, 2018 9:31 PM