12-16-2016 01:27 AM - edited 12-16-2016 01:28 AM
Hi,
We are testing GProtect 2.3.2 version and its not working fine.
Debug GP client shows "WINHTTP CALLBACK_STATUS_FLAG_CERT_CN_INVALID".
The certificate is issued with the Common Name clientvpn.xxx.xxx, and this is the address of the portal.
If instead of the DNS name of the portal, we put the IP address, the client warns that the CN of the certificate does not match, but allows to establish the connection.
how can we solve this problem??
12-16-2016 03:17 AM
Hi,
Think you getting this:
Thx,
Myky
12-20-2016 12:41 AM
We were using GProtect version 1.2.2 and it was working fine. We decided to upgrade GProtect to version 2.3.2. We created a new certificate with the same CN in order to solve it, but this is not working 😞
Why is not working???
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!
