Skip to main content
Contributor
May 7, 2010
Question

Replacement for FortiClient?

  • May 7, 2010
  • 8 replies
  • 5030 views
Hi, I am running FortiClient 4.1.3.143 in Windows 7 64 bits to access my company' s servers. I see the same problems as described in some other posts in this forum, i.e. HTTP traffic is blocked as long as FortiClient is running (which i believe can be fixed with a registry modification) and then that it takes minutes after reboot before internet is up and running. So, is there any other VPN client out there that can be used as replacement for FortiClient? Thanks...

    8 replies

    Carl_Wallmark
    New Member
    May 7, 2010
    Hi, if you remove your network interface from the Device Manager, and then reinstalling it with " Search for hardware change" , it will solve your " wait for network" .
    Contributor
    May 7, 2010
    I have done that, thanks But, I am still curious about if there are other clients, as I would like to set up a tunnel from my Linux machine as well. And I don' t like all those small fixes that FortiClient seems to require...
    Contributor
    May 7, 2010
    Hi, I wan to know if there is someone who implement ssl web portal and java RDP connexion . All Alt gr keys don' t work . Is there solution?
    Contributor
    May 7, 2010
    Hi, I wan to know if there is someone who implement ssl web portal and java RDP connexion . All Alt gr keys don' t work . Is there solution?
    Contributor
    May 25, 2010
    Hi I am having the same problem as m_gustafsson, why does fortinet block HTTP traffic, that seems so dumb? Is there a way to get round this permanently using a registry fix for example Thanks
    romanr
    New Member
    May 25, 2010
    Hi I am having the same problem as m_gustafsson, why does fortinet block HTTP traffic, that seems so dumb?
    I am not sure if anyone here knows the real reason for the one or other issue to happen. I' ve seen a couple of problems, where the interaction of Forticlient with another product causes comparable problems!! Like Trend Micro and Forticlient will cause HTTP to not work with certain versions! You could try the following: - edit the registry key value using regedit. - Go to HK_LOCAL_MACHINE\Software\Fortinet\FortiClient\FA_FORTIPROXY\enabled - Change the permission from read to Full Control - open the command prompt, run ' net stop fortishield' - Go back to HK_LOCAL_MACHINE\Software\Fortinet\FortiClient\FA_FORTIPROXY\enabled, change the value from 1 to 0. - Restart you pc and enable the realtime protection again.
    Contributor
    May 26, 2010
    Mr Romanr, you are a legend, that registry fix has seemed to work for now, thanks for your help! By the way, to those who have 64 bit windows 7 the registry key seems to be under hklocalmachine, software, wow6432node, fortinet, etc Regards Luke Nash
    optimizzz
    New Member
    May 26, 2010
    the interaction of Forticlient with another product causes comparable problems!!
    i agree with romanr. this is comparable issue. just like if you choose install Norton, you have to remove Macfee or Kaspersky first.
    Contributor
    August 10, 2010
    Hi, if you remove your network interface from the Device Manager, and then reinstalling it with " Search for hardware change" , it will solve your " wait for network" .
    Has anyone had any luck with this? I have installed FortiClient on about 20 machines. The majority of them are Windows XP and do not have any problem. The Windows 7 machines, however, take an extremely long time to acquire a network address. Once they do acquire an address, it still takes a very long time for the web browser to load the first web page. This is only happening on the Win 7 machines. I have uninstalled the NIC from the Device Manager as suggested and reinstalled it with the " Search for hardware change" button, but still suffer from the same problems. I have also ran FortiClient' s " ReinstallNIC.exe" program that they package with the FortiClient tools, but again no luck. The weird thing is, on a Windows 7 Laptop, the wireless interface works just fine, but the wired does not. Anyone have any suggestions to fix this problem?