Endpoint Protection

 View Only

  • 1.  GUP strange behavior

    Posted Jul 07, 2011 12:22 PM

    I’ve recently discovered that a GUP installed on a Windows XP SP3 machine hasn’t been acting as a GUP: no response on port 2967, not showing in the Content Monitor interface. I’ve moved it to another group and then back to his group and that solved the problem for the next, I don’t know exactly, 24 hours. And then again the same issue, no response on port 2967, not showing in the Content Monitor interface, I’ve tried again the same formula with the same results.

    Both the SEPM console and the GUP are using RU6 MP2.

    Any idea?

    Thanks.



  • 2.  RE: GUP strange behavior

    Posted Jul 07, 2011 01:32 PM

    How many locations do you have in the GUP's group?



  • 3.  RE: GUP strange behavior

    Posted Jul 07, 2011 02:01 PM

    Only one.



  • 4.  RE: GUP strange behavior

    Trusted Advisor
    Posted Jul 08, 2011 09:48 AM

    Hello,

    Try migrating to the Latest version of 11.0.6300 and check if that works for you!!!

    If I am not mistaken, this is related to the Issue:

     

    GUP does not respond immediately to client requests when policy contains GUPs in different subnet
    Fix ID: 2143552
    Symptom: Clients do not immediately contact the nearest GUP when policy is applied containing a GUP in a different subnet. The client does not download from the GUP until the threshold has passed "Maximum time that clients try to download updates from a GUP before Symantec Endpoint Protection Manager".
    Solution: The GUP is now considered ready for connections if the GUPLIST that includes the static GUP is not empty.
     
    Reference:
     


  • 5.  RE: GUP strange behavior

    Posted Jul 08, 2011 10:06 AM

    Hi,

    The GUP and the clients are in the same subnet.

    Thanks.