Skip to main content
A
Anonymous_User
Contributor
July 5, 2011
Question

Forticlient vpn BSOD

  • July 5, 2011
  • 17 replies
  • 13624 views
Hi Guys, Since the Windows updates last week, my forticlient (4.2.3.0271_x64) has been crashing my machine. I run Windows 7 64bit, and the VPN client was working great prior to those updates (KB2552343, KB2547666, KB2545698). I have 3 dump files if someone wants to take a look at them. Thanks in advance for any help you can render.

    17 replies

    A
    Anonymous_UserAuthor
    Contributor
    July 13, 2011
    Ok, I have resolved the BSOD issue. Now the VPN wont connect. It does get to (98), sits there for 30 seconds or so and then returns to the connection dialogue, unconnected. While i was resolving the BSOD issue i noticed there was a dialup adapter called FortiSSL (or something like that) that was reporting device problems. i deleted it and re-installed the whole client. Is there any advice anyone can provide on this?
    vanc
    vanc
    New Member
    July 14, 2011
    If you are using Windows 7, recommend to use the just released 4.2.5. The new release contains a brand new network driver based on NDIS 6. All early releases are using NDIS 5 which has some issues with power management on Vista/Win7. It may not solve your problem. But worth a try.
    A
    Anonymous_UserAuthor
    Contributor
    July 15, 2011
    Where can I download this? I' m asking a free version.
    ede_pfau
    SuperUser
    ede_pfau
    SuperUser
    July 15, 2011
    After looking for a long time for a place to download the free Forticlient 4.2.5 I decided to upload it myself for sharing: http://www.mediafire.com/?4726795mj4j9b Straight from Fortinet' s ftp server. No idea why they don' t do that themselves.
    RAMAN_KRISHNAPRASAD
    RAMAN_KRISHNAPRASAD
    New Member
    March 13, 2012
    I am having same problem of bsod on my windows 7/64 bit
    RAMAN_KRISHNAPRASAD
    RAMAN_KRISHNAPRASAD
    New Member
    March 13, 2012
    I installed 4.2.5 and I am getting following error while connecting to my office VPN : program=FortiProxy msg=Error open redirector device
    vanc
    vanc
    New Member
    July 15, 2011
    After download, please verify the digital signature. Right click on the installer exe file and choose Properties.... In the dialog, if you don' t see " Digital Signatures" . It' s either a corrupted or manipulated file. See the attached picture.
    ede_pfau
    SuperUser
    ede_pfau
    SuperUser
    July 16, 2011
    And additionally, you can compute the HMAC hash and compare to the checksums published in the Release Notes (last 2 pages). The location given offers the 32bit client, the 64bit client and the Release Notes.
    A
    Anonymous_UserAuthor
    Contributor
    July 19, 2011
    Ok, i' ll give the above a try. Can someone provide some advice on doing a complete un-install and registry and device clean of the old Fortinet client? I think this would be prudent so the new install is not affected by the previous install.
    A
    Anonymous_UserAuthor
    Contributor
    July 20, 2011
    Good news! (finally) 4.2.5 has resolved this issue! I' m back on my VPN and hopefully it will be smooth sailing until from now on. Thanks all for the assist!
    ede_pfau
    SuperUser
    ede_pfau
    SuperUser
    July 20, 2011
    I' m glad you made it! FClient usually is rock solid and if it runs initially, it' ll run for a long time with no hassles.
    A
    Anonymous_UserAuthor
    Contributor
    July 20, 2011
    *sigh* I hate to rain on our parade Ede, but after my latest reboot, the VPN establishment is once again causing a BSOD. It occurs right as the VPN is established. Can anyone take a look at the dump files that were generated to see the cause? I' m fairly certain it' s probably device related (virtual device).
    ede_pfau
    SuperUser
    ede_pfau
    SuperUser
    July 20, 2011
    OK, scratch my last post :-(( Are you 100% sure you installed the 64bit client? What other low-level (filter-level) software do you use, like AV? Even if you leave out the AV part of FC, it might collide internally. Sometimes the sequence of drivers loading cause a malfunction. Sorry, back to the crystal ball for peeking...
    Show more replies
    Terms & ConditionsAccessibility statement