Hey Guys,
Im having some trouble with the forticlient addon. Firstly I was disappointed that you cant specify logon details in RDM - but more importantly I dont seem to be able to close the VPN...
Not sure if this is a common bug or somthing specific to us?
Cheers
Hi Will,
I will verify with André but it's not our fault if we can specify the logon details. If they don't provide the command line or the API, there is nothing we can do. Could you try to close the VPN with the command line to see if it works?
David Hervieux
Hey David,
That's fair. What command does it currently use to close the vpn?
Hi,
It's
FortiSSLVPNclient.exe /disconnect or ipsec.exe /disconnect
David Hervieux
Hi,
Since the update to VPNAddOn.dll version 3.0.1.3 it will no longer disconnect the FortiSSLVPN automatically. The command for disconnect is "FortiSSLVPNclient.exe disconnect" without the forward slash. Can this be fixed?
Hi,
I think we changed that recently. It was the opposite we had a customer that it was not working with another Forticlient version. We will update the add-on with a new option called "Use legacy Disconnect"
David Hervieux
Hey David - The ipsec doesn't disconnect using the command you provided.
@will.mcenaney
Are you able to disconnect it with a another command?
David Hervieux
Hi,
I added the "legacy Disconnect" option for FortiClient session. It uses the method prior to version 3.0.1.3.
Could you try it and give us feedback please ?
Just have to replace the dll in %LocalAppData%\Devolutions\RemoteDesktopManager
Best regards,
edited by asanscartier on 7/10/2014
André Sanscartier
Hi Andre,
Can confirm that "legacy Disconnect" works fine. Thanks a lot.
Regards
Michael
Hi David,
Sorry - I forgot about this - been very busy.
I have not found a command that will let me disconnect as of yet.
Cheers
Will
@Will
Let me know if you find anything or if you find a workaround.
David Hervieux
hi
have still the same Problem
can not close forticlient session (ipsex.exe)
legay disconnect does not solve the Problem
also tried to Change the vpnaddon.dll from above - same Problem
rdm 12.0.8.0
forticlient 4.2.7 (also not works with newer or older Versions)
br klaus
Hello,
Could you try running the ipsec.exe command out of RDM to see if it works?
It should be one of these two commands:
<pathToExecutable>\ipsec.exe disconnect
<pathToExecutable>\ipsec.exe quit
The second one is what is called when using "legacy disconnect". Do either of these work outside of RDM?
Regards,
Hubert Mireault
hi
both (quit and disconnect) does not work anymore (since Version 4 forticlient)
legacy disconnect on rdm not working
what means legacy disconnect outside rdm?
klaus
Is there an alternative to quit or disconnect? We could add an option to use the new way to close the FortiClient ipsec client, but we need your help since we don't have access to the executable.
Regards,
Hubert Mireault
hi
when i activate "Show Command" i see that rdm send "[path-to-exe]\ipsec.exe -k -b VPNTunelName"
this open the tunnel in silent mode and it works, but in this case the command "[path-to-exe]\ipsec.exe quit" does not work anyway
when i start manually the tunnel with "[path-to-exe]\ipsec.exe VPNTunelName" (withou -k -b), then i can Close the tunnel with "[path-to-exe]\ipsec.exe quit"
the different between starting with or without the Parameter is:
with -k -b -> silent
without Parameters -> see the ipsec Connection in the dos box
so, when i create a new entry "command line" with run:
for example:
"C:\Program Files (x86)\Fortinet\FortiClient\ipsec.exe" "1536_Wechselberger"
and set the "Event" "after disconnect" to
"C:\Program Files (x86)\Fortinet\FortiClient\ipsec.exe" quit
it works
so what means the -k -b exactly (Can not find anything about it at fortinet)
http://kb.fortinet.com/kb/documentLink.do?externalID=FD30811
klaus
We could add an option to run it silently (use "-k" and "-b") which could be disabled. This should fix the issue. What do you think?
Regards,
Hubert Mireault
seems to be okay