Skip to main content
ScootMcGoot
ScootMcGoot
Visitor III
April 1, 2025
Solved

Computer unable to connect to EMS

  • April 1, 2025
  • 2 replies
  • 1529 views

I have a computer that was sent an invite from the EMS system that was able to go through the set-up process and appears in my system. Today, when the user tried to connect to a VPN they see "Unlicensed VPN access is available until *insert a date here*" (they can still connect to whatever VPN they were attempting). When I access EMS, the device is showing Not Managed by EMS and Not Registered.

 

Please advise on how to handle this.

 

Extra Info:

- I have several open spots in my licensing.

- According to the Log Viewer, the device was unregistered this morning. 

Best answer by AEK

If the client was unregistered this morning then it is unlicensed, and the VPN will work for a limited period.

If your license is not totally consumed (number of clients) then it is probably due to human error.

Try investigate in EMS logs if some admin has unregistered the client.

Also try check in FortiClient logs (\Program Files\Fortinet\FortiClient\logs) if the admin has done anything related, e.g.: FCT re-installation or anything similar.

2 replies

honelbo2
honelbo2
New Member
April 1, 2025

This issue has been present for two days, and just as I was about to restart the server, I found that the EMS connection to this server was normal again

AEK
SuperUser
AEKAnswer
SuperUser
April 1, 2025

If the client was unregistered this morning then it is unlicensed, and the VPN will work for a limited period.

If your license is not totally consumed (number of clients) then it is probably due to human error.

Try investigate in EMS logs if some admin has unregistered the client.

Also try check in FortiClient logs (\Program Files\Fortinet\FortiClient\logs) if the admin has done anything related, e.g.: FCT re-installation or anything similar.

AEK
    ScootMcGoot
    ScootMcGootAuthor
    Visitor III
    April 2, 2025

    Thanks for this, it was definitely user error and they removed themselves from the system.

     

    After sending them a new code to rejoin they were good to go.

      Terms & ConditionsAccessibility statement