Endpoint Protection

 View Only

  • 1.  Clients: "Failed to connect to all GUPS, trying SEPM"

    Posted Sep 20, 2013 03:36 PM

    "Failed to connect to all GUPS, trying SEPM"

    This is the error message i get in the client activity logs. Liveupdate policy is configured to never download content from SEPM if GUP is not available, but I don't know why clients continue to download update from the SEPM server.



  • 2.  RE: Clients: "Failed to connect to all GUPS, trying SEPM"

    Posted Sep 20, 2013 08:09 PM

    What version of SEPM/SEP are you on?

    This issue was fixed in 12.1 RU2. See fix note here:

    Client bypasses the newly promoted Group Update Provider despite policy that states it should never bypass the Group Update Provider
    Fix ID: 2757957
    Symptom: Clients bypass newly promoted Group Update Provider and contact Symantec Endpoint Protection Manager directly for content, even though policy states it should never bypass the Group Update Provider.
    Solution: Client does not bypass the Group Update Provider if policy is set to "never bypass," even if the new Group Update Provider's guplist.xml is still empty.
     
     
    New fixes and enhancements in Symantec Endpoint Protection 12.1 Release Update 2
     
    Article:TECH199676  |  Created: 2012-11-13  |  Updated: 2013-04-08  |  Article URL http://www.symantec.com/docs/TECH199676

     



  • 3.  RE: Clients: "Failed to connect to all GUPS, trying SEPM"

    Posted Sep 30, 2013 05:02 AM

    Hi

    Please check if the port 2967 is opened bi-directionally

    Regards

     



  • 4.  RE: Clients: "Failed to connect to all GUPS, trying SEPM"

    Posted Oct 21, 2013 04:02 PM

    AN9,

    Have you been able to investigate this further?



  • 5.  RE: Clients: "Failed to connect to all GUPS, trying SEPM"

    Posted Oct 22, 2013 06:07 AM

    Hi

    Can you please update on the solution provided

    Regards