FortiClient VPN don't launch

avatar

Hello,

I'm trying to use the FortiClient VPN. I configured the path of the ".exe", but when I launch my session, a cmd pop-up appears but the FortiClient VPN doesn't launch.

I use the "7.0.7.0345" version of FortiClient VPN and "2022.3.30.0 64-bit" of RDM.

I also tried to run the command in cmd but it doesn't work.

Best regards,
Ferrara Evan

All Comments (18)

avatar

Hello,

Our Forticlient integration is based on a command line that was provided to us a few years ago. Our integration is not based on the app installed on your computer. Since we are not a Fortinet customer, it's not possible for us to test their new releases or to contact their support department. I have asked a few times to some of our clients to contact them and provide us some feedback on their CLI. I want to know if their command line is still available and if yes, is there some documentation that they can provide us. Unfortunately, no one from our community was able to provide us this type of information.

That being said, are you able to provide us a working command line for Forticlient? Is it possible for you to contact them and ask them if they still offer a CLI?

Best regards,

Jeff Dagenais

avatar

Hello,

I contacted them and I wait for an answer.

For your request, here is a command that appears when I launch a session :
ipsec.exe -k -b -U "username" -P "password" "server IP".

I come back to you when I receive an answer.

Best regards,
Ferrara Evan

avatar

Hello Evan,

The engineering team confirmed this is already the command line we are using in RDM. Please let us know if you hear back from the support team.

Best regards,

Richard Boisvert

avatar

Hello Richard,

I come back to you when I receive an answer.

Best regards,
Ferrara Evan

avatar

Hello Richard,

I received an answer, they tell me that the command for use FortiClient SSL VPN (not the FortiCLient VPN) is :
FortiSSLVPNclient.exe connect -h serverIP:Port -u username:password -i

When I try the command, all works but the connection is not established, but when I put the same information in the FortiClient VPN when I setup an SSL connection, it's work.

Now when I know that I can connect to my SSL server via FortiClientVPN, the problem is that the FortiClientVPN don't launch when I start a session.
The other problem is that, when I start a session SSL via FortiCLientSSLVPN, the FortiClientVPN launch too but neither of them get an IP address.

I hope you understood my problems.


P.S = FortiClientVPN is the logicial available on "https://www.fortinet.com/support/product-downloads"
FortiClientSSLVPN is the logicial available on "https://support.fortinet.com"


Best regards,
Ferrara Evan

avatar

Hello,

Thank you for the details, I have sent them to the engineering team.

Best regards,

Richard Boisvert

avatar

Hello,

Do you have any news ?

Best regards,
Ferrara Evan

avatar

Hello,

Here is the feedback we receive from the engineering team:

We do the same command in the back end, unfortunately. If it does not work, we unfortunately cannot test it further on our end since an account is required for the application, which we do not have.

Would you be able to run the same command line that RDM uses. To help with this, there is even a "show command" checkbox in the FortiClient entry that will show you the command line we are sending before we execute it. It will (possibly) display a comparison between what works and what does not.

Just note that the "show command" option is for debugging purposes only, it should not be left checked, otherwise users could see the command line visually.

It seems to be an issue with the FortiClient application, but if you can help us confirm by performing the following:

  • The command line that RDM runs is the same as the command line that FortiClient mentions
  • You receive the same behavior by doing the command line in RDM and in CMD of windows (so, doing the same thing we do, basically)


Best regards,

Richard Boisvert

avatar

Hello,

I followed your procedure with the "show command" that shows me the command : "ipsec.exe -k -b -U "username" -P "password" "server IP""

I executed this command in the CMD but it doesn't work. A pop-up appears, but nothing gets started.

Best regards,
Ferrara Evan

avatar

Hello,

Thank you for providing us with the command and the result, I have sent it to the engineering team so they can investigate.

Best regards,

Richard Boisvert

avatar

Hello,

Your FortiSSL connection mode seems to be set incorrectly, could you make sure it is set to "FortiSSL"? The command you receive after should be the correct one. The command you sent us is the one used by "FortiClient".

forum image

Best regards,

Richard Boisvert

avatar

Hello,

Sorry, I thought you were talking about the FortiClient.

I have this command : FortiSSLVPNclient.exe connect -h "IP address+port" -u "username;password". This command works, but the FortiClient launch too, and neither of them get an IP address. I tried to uninstall the FortiClient and there the connection was not established on the FortiSSL.

Best regards,
Ferrara Evan

avatar

Hello,

Just to be certain, when you run the command line externally (not in RDM), the IP address is not filed out? If so, it is out of our hands, unfortunately. The Forti team provided us, and confirmed, it is the appropriate command to run.

Best regards,

Richard Boisvert

avatar

Hello,

The connection is not established even when I click on the "Connect" button (see attachments)

When I click on the "Connect" button, for not even a second it says "Connecting (10)" and then switches back to Disconnected.

Best regards,
Ferrara Evan
forum image

avatar

Hello Ferrara,

Thank you for confirming it is not working via the command line either. Until that is fixed, our hands are tied.

Best regards,

Richard Boisvert

avatar

Hello,

I contacted FortiNet, but for the moment they did not find a solution.

Best regards,
Ferrara Evan

avatar

Hello,

I received an answer from Fortinet. They tell me that the problem doesn't come from them.

I don't know if you have more information about my problem.

Best regards,
Ferrara Evan

avatar

Hello,

Unfortunately, if you have the same behavior with the CLI and RDM, and since RDM uses the CLI in in backend, we cannot make any progress on the issue unless the CLI issue is fixed.

Best regards,

Richard Boisvert