Skip to main content
FKribs
FKribs
New Member
July 31, 2014
Solved

VPN stuck at status 98%

  • July 31, 2014
  • 34 replies
  • 824345 views
We are running Windows Server 2012 R2. We have installed the most recent FortiNet client (vpn only), version 5.2.0.0591. We have configured an SSL-VPN connection. When we click on the " connect" button, the status progresses all the way to 98% and then hangs. We have disabled the windows firewall, do not have any anti virus software installed, no group policies are being applied, and no other applications are running when we attempt to make the VPN connection. Thanks for helping!
    Best answer by denniswong34

    Hi All,

     

    I just fix it by apply this fix and re-install fortigate client.

    https://skydrive.live.com/redir?resid=86BDD34D41D3E179!2065&authkey=!AAeyjPB4O4uVxek

     

    You may find the detail from this forums. Hope this could help you all. Thanks.

    https://supportforums.cisco.com/discussion/11682811/anyconnect-msi-installation-failed-windows-7

    34 replies

    neonbit
    neonbit
    New Member
    August 1, 2014
    First thing I would check is the even log on the FortiGate (found under: Log & Report > Event Log > VPN). This should give you some clues on what is causing the VPN to fail. You could also test the VPN connection from another computer/network/username to isolate if the problem is on the FortiGate side or the server.
    Dushyant
    Dushyant
    New Member
    August 1, 2014
    1. Open IE, go to Options -> Connections -> Remove FortiSSL device 2. Go to Control Panel -> Programs and features -> FortiSSL client -> Open, select REPAIR package 3. Open Network connections and you will see new FortiSSL device with icon of vintage phone.
    Warren_Olson_FTNT
    Staff
    Warren_Olson_FTNT
    Staff
    August 1, 2014
    You may also try going into settings for the connection and check the box " Do not warn invalid server certificate" and see if that pushes you over the hump, let us know.
    FKribs
    FKribsAuthor
    New Member
    August 1, 2014
    RE: Warren Olson We tried leaving the " do not warn invalid server certificate" unchecked as well as checked and it did not change the problem. RE: Dushyant After the repair, we noticed that in " Network Connections" that the " fortissl" is showing " Unavailable- device missing" . Looking in the properties of " fortissl" network connection on the " general" tab, in the " Connect using:" box it says " Modem Removed- Unavailable device ()" . RE: neonbit We bumped the logging up to " debug" level and saw this error in the logs: 8/1/2014 5:39:39 PM Error VPN FortiSslvpn: 2356: Ras : connection to fortissl failed : 0:0: This might coincide with the " fortssl" connection mentioned above. The FortiNet VPN client successfully connects with Windows 7 but not with Windows Server 2012 R2.
    Fullmoon
    Fullmoon
    New Member
    August 4, 2014
    ORIGINAL: FKribs The FortiNet VPN client successfully connects with Windows 7 but not with Windows Server 2012 R2.
    I had similar issue, my work around was instead of using ssl vpn we used forticlient.
      harald21
      harald21
      New Member
      August 5, 2014
      Hello, we have a similar issue: Working SSLVPN client at Windows 7 / stuck SSLVPN at Windows 8.0 or 8.1 I have a ticket open at FortiSupport and they identified a bug. (hopefully they fix it soon) Sincerely Harald
      claumakurumure
      claumakurumure
      New Member
      August 5, 2014
      use Forticlient 4.3.5 it works 100%
      FKribs
      FKribsAuthor
      New Member
      August 5, 2014
      FortiClient Version 4.3.5.472 has the same issue. It hangs at 98%.
      claumakurumure
      claumakurumure
      New Member
      August 6, 2014
      This is for windows 8.1 windows 8.0.works perfect on my machine with 4.3.5.472 Message from Fortinet for Windows 8.1 Bug #0232764 is opened for this issue and our developers are currently investigating together with Microsoft support to find a solution for this. We noticed also an issue for the direct Forticlient SSL connection for workstations that were upgraded from Windows 8.0 to Windows 8.1, is some cases this issue was resolved by unistalling the forticlient, rebooting the workstation and reinstalling the Forticlient. Even if the bug is currently opened please perform the following when you have one user that can' t connect: - Check the windows system support for the sslvpn driver. Our sslvpn driver is a virtual PPP adapter, for it to work properly, it needs the following: From Windows Services (run:services.msc), check Telephony (TapiSrv) service is enabled and running From Device Manager, select “View->Show hidden devices”, then open “Network Adapters”, check “WAN Miniport (IP)” is enabled and running properly.
      FKribs
      FKribsAuthor
      New Member
      August 6, 2014
      We have uninstalled, rebooted and reinstalled over 10 times now with no change. We have now set the Telephony service to enabled and running. We have also checked the " WAN Miniport (IP)" and verified that it is enabled. The same problem is still happening.
      Brady_R__Houser
      Brady_R__Houser
      New Member
      August 13, 2014
      We had the problem when we used an old, or too new version. You could try a different version. Sometimes the newest one doesn' t work as well.
      Dipen
      Dipen
      New Member
      August 13, 2014
      Not a new error. I work with a Forti Gold Partner..we faced this issue with numerous customers. No solution in place,,,probably a bug.. Workaround is to use an old SSL-VPN client like Ver4 MR2 client...it worked for us
      Dipen
      Dipen
      New Member
      August 13, 2014
      If you need VPN only please don' t use FortiClient use SSLVPN client (few hundred KBs) instead. I was referring to SSL-VPN client only in my last post.
      FKribs
      FKribsAuthor
      New Member
      August 15, 2014
      We searched the internet and found an old version (SSLVPN v4.0.2297) of SSL VPN client only and we have the same issue. It gets stuck at " Status: Connecting...(98)" . After 60 seconds, it appears to time out and automatically disconnect.
      Show more replies
      Terms & ConditionsCookie settingsAccessibility statement