FortiClient - Credential or SSLVPN configuration is wrong (-7200).

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

FortiClient - Credential or SSLVPN configuration is wrong (-7200).

L0 Member

For some time now, many of our users have been having problems connecting via VPN.

In short, we can say that with their home routers they can't log in at all, or every once in a while.

What is interesting is that switching to the Internet from a shared hotspot from the phone works much better.

I've been looking into the matter for some time to investigate this and gather as much information as possible on the subject.

I looked at several users who reported such a problem.

The information I gathered:

In most cases we are using Forticlient 7.4.1.1736, 7.4.2.1737, 7.4.3.1790.

All users with the problem receive the same message: Credential or SSLVPN configuration is wrong (-7200).

This indicates a problem with the login credentials, but this is not true. Using the same credentials, they log in via hotspot from their phone without any problem.

The problem occurs on different versions of forticlient. You can't say that it depends on its version.

I prepared a script to check some basic things:

-checking the correctness of the port on which the connection to the VPN server is attempted (in our case 12443)-whether open/closed

-checking the size of the MTU

-checking the sending of a UDP packet to the remote VPN address - plovpn.innoviafilms.pl:12443 (we use the DTLS option to improve the performance of Teams via VPN)

In all cases where I checked there is no problem from this side.

I checked the connection with the DTLS option enabled and disabled, and it doesn't make any difference either.

And now most importantly I checked the VPN connection using the old authentication method (without MFA/Cyberark) and it works every time and without any problem.

As you can see the problem is not with the ISP, home router, settings or forticlient version.

The problem is the MFA authorization by Cyberark. In my opinion, there is some kind of configuration issue.

It's not quite right, which results in a problem connecting to the VPN.

1 accepted solution

Accepted Solutions

L7 Applicator

Hey @Tomasz Woźniak​ 

For something such as this it may be best to open a Support Case and review it with our technical support team.

 

-Matt

View solution in original post

1 REPLY 1

L7 Applicator

Hey @Tomasz Woźniak​ 

For something such as this it may be best to open a Support Case and review it with our technical support team.

 

-Matt

  • 1 accepted solution
  • 1436 Views
  • 1 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

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!