Skip to main content
claudyyus
New Member
June 23, 2022
Question

FortiClient VPN command line errors

  • June 23, 2022
  • 12 replies
  • 11375 views

 FortiClient VPN v.7.0.5.0238 with FortiClientTools

 

   I want to connect to the VPN from the command line. For this I use the auxiliary tool from FortiClientTools.

 

e.g. FortiSSLVPNclient.exe connect -s MyCompanyName i -m -q (No Certificate)

 

    Forticlient ssl vpn connected but no bytes recieved . If I don't use the command line, everything works perfectly.  What is the difference or where is the mistake ?  Specify that if i use an older version of Forticlient I do not encounter this problem. 

 

  

    

12 replies

Anthony_E
Staff
Staff
June 26, 2022

Hello claudyyus,

 

Thank you for using the Community Forum.

I will seek to get you an answer or help. We will reply to this thread with an update as soon as possible.

 

Regards,

Best Regards
Anthony_E
Staff
Staff
June 27, 2022

Hi claudyyus,

 

While I m looking for a solution, I m sharing this documentation with you:

 

https://docs.fortinet.com/document/forticlient/7.0.5/windows-release-notes/371487/introduction

 

It will maybe provide you some interesting information.

 

Regards,

Best Regards
claudyyus
claudyyusAuthor
New Member
August 16, 2022

Any update ?

RachelGomez123
New Member
August 16, 2022

Ensure that the version of FortiClient used is compatible with the user’s version of FortiOS.

Export FortiClient debug logs by doing the following:

Go to File >> Settings. Under the logging section, enable “Export logs.”
Set the “Log Level” to debug and select “Clear logs.”
Attempt to connect to the VPN.
Select Export logs after receiving the connection error.

 

This may help you,

Rachel Gomez

agostinolabruna
New Member
December 5, 2022

Hello, I have the same problem: since I ugraded FortiClient VPN to 7.05 (and to 7.0.7) SSL CMDline does not work, the client connects but bytes received stays at 0.

If I connect using the GUI with the same settings it works.


I noticed that the route is wrong and even the IP that is assigned to the Virtual Adapter

The last version that seems to work is FortiClient VPN 7.0.2. I tested against a variety of versions and 7.0.2 is fine, but as soon as I upgrade the Client to 7.0.5 the cmdline stops working.

VinnieNZ
New Member
March 12, 2023

I've also had this issue.  7.0.2 is the last version of SSLVPNcmdline that works, as soon as we go to 7.0.3, it stops working (ever since the FCCryptDLL.dll file is added to SSLVPNcmdline).

 

Looking at the network adapter for the VPN, we see that no IP ever get's assigned to the adapter - I'm not sure if this is the cause or just a symptom.

 

I've tried pretty much every version from 7.0.3 up, with the matched main VPN client version, each time I get the same issue.

 

I'm keen to get this resolved, please let me know what further info I can provide so we can progress this.

Macro
Visitor III
May 29, 2023

I have this exact issue. It is quite annoying and hopefully it will get resolved soon.

kvimaladevi
Staff
Staff
May 30, 2023

Is Split tunnel enabled in this scenario?

 

Regards,

Vimala

Macro
Visitor III
May 30, 2023

Mine is split tunnel, but I have no idea why that would have anything to do with it. The VPN connects fine when I use the FortiClient and does not work when I use the SSLVPNcmdline.

After a reboot if I try and use the SSLVPNcmdline the Forticlient SSL VPN is connected but no bytes recieved and no IP address is set on the adapter.

The only way to get it to work is connect the Forticlient SSL VPN, once the connection is established, disconnect the Forticlient SSL VPN the connect using the SSLVPNcmdline.

 

It does seem like we are all experiencing the same issue and as @VinnieNZ has mentioned "7.0.2 is the last version of SSLVPNcmdline that works, as soon as we go to 7.0.3, it stops working (ever since the FCCryptDLL.dll file is added to SSLVPNcmdline)."

nmb
New Member
June 14, 2023

Fortinet support says they stop supporting it. A feature request must be submitted for their Dev to look into it. Opening NFR (New Feature Request) is quite complicated too, it must be opened by your account manager or SE (not sure what this means, Sales Engineer?) then cross your finger if Fortinet will look into it. Since it is a free tool, they don't have obligation or whatsoever, but why did they make it available then use at your own risk. 

VinnieNZ
New Member
June 14, 2023

It's difficult for them to claim they "stopped supporting it", when the .exe for SSLVPNcmdline is being actively updated version on version (and it broke when the introduced an extension to it in the FCCryptDLL.dll file): 

 
 

Screenshot 2023-06-15 104805.jpg

 

Thought Leadership Security Summit. Outpace New Threats with AI - enhanced defense. Tuesday, Septmeber 15, 8:30 AM - 2:30 PM PT. The Golf Club at Newcastle, WA.
Virtual event | September 2026. SASE summit. The age of autonomous trust. Register here!