Skip to main content
rockn4
rockn4
New Member
December 21, 2022
Question

FortiClient VPN vs FortiClient SSLVPN - Inconsistencies

  • December 21, 2022
  • 3 replies
  • 5117 views

Please help. I have a few clients that utilize the Fortinet VPN client for my team to access their system

we can successfully to their system using FortiClient VPN 7.0.7.0345 with no problem, but not the FortiClient SSLVPN.

 

I'd like to streamline the connection process (using Devolutions RDM), and I've heard that installing/using FortiClientTools_7.0.7.0345 to get FortiSSLVPNclient.exe in order to be able to make a connection via command line.

In testing, making the same connection in FortiClient SSLVPN, it acts like it connects, but for some reason I get a bad 169.254.119.19(Tentative) IP address, and any pings I do result in "PING: transmit failed. General failure." Any idea why a connection would work in the normal FortiClient VPN, but not in FortiClient SSLVPN?

3 replies

Anthony_E
Staff
Anthony_E
Staff
December 25, 2022

Hello,

 

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
    gfleming
    Staff
    gfleming
    Staff
    December 27, 2022

    What version of Windows are you using? Does the CLI show connected? Do you see connected status on the FGT? Is it possible you are connecting to a different portal than the GUI? Please ensure your user and settings are the same as in the GUI.

     

    https://community.fortinet.com/t5/FortiClient/Technical-Tip-How-to-use-FortiClient-SSL-VPN-from-the-CLI/ta-p/192581

      rockn4
      rockn4Author
      New Member
      January 6, 2023

      Thanks for your response! I've been testing this in Windows 11 as of late, but I believe I was also testing in Windows 10 a few months back before upgrading Windows with the same results.

       

      Everything shows as connected on the client end, but unfortunately this isn't my network to know if their FGT shows me as connected. But based on an IPCONFIG result, I do show as connected and have some of their IP information - except for getting assigned a 169. network which is my problem. So very likely connected, but just not operational.

       

      Even bypassing the CLI and using the FortiSSLVPNclient GUI, I get the same result as showing connected. I saw somewhere that using an older version of the FortiSSLVPNclient might fix this. I need to find that article again and test.

      gfleming
      Staff
      gfleming
      Staff
      January 6, 2023

      Just a bit of confusion as in your original post you said there was no problem using the GUI. But in this latest response you say the issue is the same in the GUI?

       

      If it's not working either way or its intermittent this is almost certainly an issue on the other end.


      Are the IP ranges configured properly? Do they have enough IP addresses configured to hand out to clients?

      IT_Ahan2
      IT_Ahan2
      Explorer
      December 27, 2022

      what u mean by FortiClient VPN vs FortiClient SSLVPN

        gfleming
        Staff
        gfleming
        Staff
        December 27, 2022

        FortiSSLVPNclient is CLI-based as opposed to regular GUI-based VPN agent.

        Terms & ConditionsAccessibility statement