Skip to main content
sorreisakommune
sorreisakommune
New Member
September 6, 2018
Solved

Problem with FortiClient and RDP

  • September 6, 2018
  • 2 replies
  • 15401 views

Hi,

 

Have some problem with servers, 2008R, 2012,R2 and 2016 with the FortiClient installed. When we try to rdp to the servers from workstation, the screen appers black, and taking long time to login. Sometimes we have to launch the virtuel servers through vcenter console when the RPD not working. When we uninstall the FortiClient problem is gone. Anyone else having this problem or other tips we can try?

Kent

    Best answer by kd007

    v6.0.2 was just released and this is listed as a Known Issue (bug ID #483523)

    My suggestion to go back to v5.6.6 should still work for you.

    2 replies

    swinters
    swinters
    New Member
    September 7, 2018

    Hi Kent,

     

    We're experiencing the same issue.  It seems to impact Windows 7/Server 2008R2 more severely for us, but the problem still exists with Windows 10/Server 2016.  

     

    I believe it has something to do with Real-Time Protection.  The problem goes away as soon as we disable Realt-Time Protection.  We just recently moved from Symantec Endpoint Protection to FortiClient EMS and FortiClient version 6.0.1.099 is the first version we've installed. I'm hoping this is just a bug with the latest release.  I may try to install 5.6 version of the client to see if the problem exists with an older version.

     

    -Scott 

    kd007
    kd007
    New Member
    September 7, 2018

    I think this is a bug in v6.0.1. We recently started deploying this to some of our servers and have noticed this same issue in tandem with FortiClient consuming high CPU resources. Deploy v5.6.6 instead for now until v6.0.2 is released, it is stable.

    SteveG
    SteveG
    New Member
    September 7, 2018

    You sure it's FortiClient as there was a Windows update a few months back that broke RDP for us. It's easily fixed but needs manual intervention.

     

    https://answers.microsoft...444c-b402-5dee1c0e3bee

    kd007
    kd007Answer
    New Member
    September 8, 2018

    v6.0.2 was just released and this is listed as a Known Issue (bug ID #483523)

    My suggestion to go back to v5.6.6 should still work for you.

    Terms & ConditionsAccessibility statement