Skip to main content
AKrause
AKrause
New Member
September 17, 2007
Question

FortiClient AV update failed

  • September 17, 2007
  • 6 replies
  • 5224 views
Hi, we encouter problems with the AV-updates of FortiClient. Update failed! network error! says the log. anyone else with the same problem? regards, Andreas

    6 replies

    A
    Anonymous_User
    Contributor
    September 17, 2007
    Check to see if the client machine can resolve and ping guard.fortinet.net If not, you need to check the DNS settings on the client machine.
    AKrause
    AKrauseAuthor
    New Member
    September 17, 2007
    ORIGINAL: Dean Fox Check to see if the client machine can resolve and ping guard.fortinet.net
    DNS settings are correct. guard.fortinet.net can be resolved. Teh name is resolved to different IPs - some reply to ping, and some don' t. However, AV updates do not work. We have about 150 FC installations running for several customers. Many complain about this issue, so it is obviously not a single client issue. regards, Andreas
    vanc
    vanc
    New Member
    September 17, 2007
    Rush hour effects. You can complain to Fortinet and push them to add more update servers.
    AKrause
    AKrauseAuthor
    New Member
    September 18, 2007
    Here is what support says: The failed AV updates might be due to the difference of timezone between the FortiGate Distribution Server that your customer is requesting the update from and your customer' s PC. This is because our FDS is will respond to update request according to timezones. To resolve this, try the following: (1)Perform a " ping forticlient.fortinet.net" from the affected PC (2)Use the IP that responded to the ping request and configure your FortiClient to update specifically from that particular FDS. (3)To configure the FortiClient to update specifically from a particular FDS: - Maintenance >Update >check the " Use this server to update:" checkbox >click apply This works, but this cannot be serious! Regular AV-updates do not work anymore, you have to manually set the update server to IP. This info is not provided to customers on fortinet' s on initiative, but needs to be asked via support. They just can' t be serious. Andreas
    vanc
    vanc
    New Member
    September 24, 2007
    More FDS servers added. I don' t see update failure again.
    FortiRack_Eric
    FortiRack_Eric
    New Member
    October 15, 2007
    Clients still have the same problem. This needs to be addressed! Has it to do with the effect of changing the default upgrade time to every 4 hours? Regards, Eric
    vanc
    vanc
    New Member
    October 15, 2007
    FortiClient has a bug which may prevent it from trying all available servers. The bug has been fixed in MR5 patch-2. I have been running some interim build for over a week and the update failure message does not appear. Patch-2 is supposed to be released this week. Just wait for a couple of days.
    Terms & ConditionsAccessibility statement