Wininet.dll not working with TLS1.2

Walter Gith 1 Reputation point
2021-07-01T03:29:19.593+00:00

My provider changed their servers to TLS1.2 a couple of days ago. Since then my wininet calls are not working under Windows 10 and edge anymore! I am using the following call:
Public Declare Function FtpGetFile Lib "wininet.dll" Alias "FtpGetFileA" -
(ByVal hFtpSession As Long, ByVal lpszRemoteFile As String, -
ByVal lpszNewFile As String, ByVal fFailIfExists As Boolean, ByVal dwFlagsAndAttributes As Long, -
ByVal dwFlags As Long, ByVal dwContext As Long) As Boolean

Any help would be highly appreciated!

Walter

Windows API - Win32
Windows API - Win32
A core set of Windows application programming interfaces (APIs) for desktop and server applications. Previously known as Win32 API.
2,428 questions
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Xiaopo Yang - MSFT 11,501 Reputation points Microsoft Vendor
    2021-07-01T07:02:51.74+00:00

    With Edge cannot working, I suspect the problem is not FtpGetFileA.
    According to WinINet, As standards evolve, WinINet functions handle the changes in underlying protocols, enabling them to maintain consistent behavior.
    And you should check whether the computer supports TLS1.2 or not. or Perhaps you need to override the default (D)TLS and SSL protocol version settings.

    0 comments
  2. Walter Gith 1 Reputation point
    2021-07-02T00:42:41.99+00:00

    Thank you so much. So far I never had to change anything in the registry. All protocols were supported automatically with the updating of the operating systems. As you said the wininet.dll keeps evolving. I wonder if my host (web service provider) that changed their servers made a mistake. The day say abandoned TLS 1.1/1.0 my software stopped working. Any idea on how to check on this? Thank you.