Skip to main content
AtiT
New Member
April 6, 2019
Question

FortClient signature updates from FortiManager

  • April 6, 2019
  • 4 replies
  • 8231 views

Hello, I need some help with the following setup.

I installed a FortiManger as a FDS server for FortiClients and I set the following in the CLI:

 

config system global

set adom-mode advanced set adom-status enable end

config system interface edit "port1" set ip 192.168.1.90 255.255.255.0 set allowaccess ping https ssh set serviceaccess fgtupdates fclupdates webfilter-antispam next end

config fmupdate fct-services set port 8888 end

When I set a FC profile in the EMS to use the IP 192.168.1.90 for signature updates and port 8888 and failover port 8899 the FortiClient shows: Could not connect to the update server Sniffing the packet on the FortiManager I can see that the FortiClient tries to reach the manager on port 80 (why?) after that on port 8899. After the SYN packet a RESET packet is sent from the FortiManager.

When I enable HTTP access on the interface and set the port 80 or 8899 I can see communication to URL /fdsupdate and some response in HTTP: FCPRFCP Response The FortiClient ends with message: Online update failed

Where is the problem? How to set up FDS on FortiManager correctly?

FortiManager, EMS and FortiClient are on 6.0.4 version.

 

4 replies

Stuart_Robertson
New Member
May 13, 2019

Hi,

 

Got the same issues using EMS and Micro-FortiGuard Server.  Any assistance would be appreciated

 

Thanks 

 

 

dombilod1
New Member
May 21, 2019

Hi AtiT

 

Have you found a way to fix this ?  Have the same issue here.

 

Thanks

dombilod1
New Member
May 22, 2019

I fixed the problem by putting same version of Fortimanager, that I was using on EMS and Forticlient.

 

We had EMS and FCT on 6.0.5 and FMGR on 6.2......  Rolling back FMGR to 6.0.5 did the trick.

 

Thanks

Virtual event | September 2026. SASE summit. The age of autonomous trust. Register here!