FortiClient
FortiClient proactively defends against advanced attacks. Its tight integration with the Security Fabric enables policy-based automation to contain threats and control outbreaks. FortiClient is compatible with Fabric-Ready partners to further strengthen enterprises’ security posture.
ESCHAN_FTNT
Staff
Staff
Article Id 197011
Description
This article provides a basic troubleshooting step that can be used when the error “FortiGate or FortiClient Enterprise Management Server (EMS) was not found” is seen on FortiClient 5.4 when registering to endpoint FortiGate in version 5.0 or 5.2.

eschan_FD38155_tn_FD38155-1.jpg

Solution
FortiClient registers to the FortiGate using Endpoint Control (EC).  In FortiClient 5.0 and 5.2, the default registration port is TCP port 8010.  FortiOS 5.0 and 5.2 both listen on TCP port 8010.

Starting with FortiClient 5.4,  EC registration will use port 8013 by default.  To register to FortiOS 5.0 or 5.2, the user must specify port 8010 with the IP address, separated by a colon. For example, <IP_Address>:8010.

FortiOS 5.4 will listen on port 8013. If registering from FortiClient 5.4 to FortiOS 5.4, the default ports will match.  Specifying the port number with the IP address is then optional.

For more information, refer to FortiClient 5.4.0 Release Notes which is available in the Fortinet Document Library.

Related Articles

Technical Note: FortiGate or FortiClient Enterprise Management Server (EMS) was not found

Contributors