Endpoint Protection

 View Only
Expand all | Collapse all

Communication Failure

Srikanth_Subra

Srikanth_SubraDec 03, 2012 10:37 PM

ℬrίαη

ℬrίαηDec 03, 2012 10:39 PM

Srikanth_Subra

Srikanth_SubraDec 03, 2012 10:43 PM

Srikanth_Subra

Srikanth_SubraDec 04, 2012 04:43 AM

Srikanth_Subra

Srikanth_SubraDec 04, 2012 09:48 PM

Srikanth_Subra

Srikanth_SubraFeb 18, 2013 04:52 AM

Migration User

Migration UserFeb 21, 2013 06:32 AM

  • 1.  Communication Failure

    Posted Dec 03, 2012 10:15 PM

    Hi,

    in mnay of our servers in symantec logs we found that cannot assign a client authentication token , there is general communication failure logs..what is that error log means..

    during that log time our server networks got disconnected..is this anything to do with symantec?

    please help



  • 2.  RE: Communication Failure



  • 3.  RE: Communication Failure

    Broadcom Employee
    Posted Dec 03, 2012 10:29 PM

    its for reputation check and insight and submitting content update. if the license is invalid or overdeployed the failures are seen.the client machine should have internet connection.



  • 4.  RE: Communication Failure

    Posted Dec 03, 2012 10:30 PM

    Do you have screenshot of error?

    Is the connection back? If so, it should be fine than.



  • 5.  RE: Communication Failure

    Posted Dec 03, 2012 10:33 PM

    The licenses are valid from our management server and no over deployed...

    but then why network is getting disconnected at that time.



  • 6.  RE: Communication Failure

    Posted Dec 03, 2012 10:37 PM

    Please find the screenshots



  • 7.  RE: Communication Failure

    Posted Dec 03, 2012 10:39 PM

    What components are installed?



  • 8.  RE: Communication Failure

    Broadcom Employee
    Posted Dec 03, 2012 10:41 PM

    does this machine has internet connection?

    is there any proxy in between?



  • 9.  RE: Communication Failure

    Posted Dec 03, 2012 10:43 PM

    Only antivirus this is server



  • 10.  RE: Communication Failure

    Posted Dec 03, 2012 11:51 PM

    Try the Communiaction trouleshooting

    http://www.symantec.com/business/support/index?page=content&id=TECH160964&key=54619



  • 11.  RE: Communication Failure

    Broadcom Employee
    Posted Dec 04, 2012 12:10 AM

    the link will not help, this will help if there is communication issue, however the screen capture reveals the client is able to connect to SEPM.



  • 12.  RE: Communication Failure

    Posted Dec 04, 2012 01:11 AM

    Internet connection is available only in one server not for all

     



  • 13.  RE: Communication Failure

    Broadcom Employee
    Posted Dec 04, 2012 02:52 AM

    the machine that has internet should not show the error unless proxy blocks the traffic. can you confirm ?



  • 14.  RE: Communication Failure

    Posted Dec 04, 2012 04:43 AM

    No Pete all servers are showing the same error



  • 15.  RE: Communication Failure

    Posted Dec 04, 2012 05:55 AM

    it says Network access control logs

    seems like you have Network access configured.

    Open up a case with Symantec support they will be able to assist you further.



  • 16.  RE: Communication Failure

    Posted Dec 04, 2012 09:48 PM

    Yes i had installed Network access control also...



  • 17.  RE: Communication Failure

    Posted Jan 24, 2013 05:38 AM
    I have the same problem as well after upgrading to SEP12 RU2. All gups fail to work with the same error mentioned. Any Help ?


  • 18.  RE: Communication Failure

    Posted Feb 18, 2013 01:46 AM

    Upgraded to SEP12 for all GUPs clients solved the problem 



  • 19.  RE: Communication Failure

    Posted Feb 18, 2013 04:52 AM

    But Iam not having GUPs



  • 20.  RE: Communication Failure

    Posted Feb 21, 2013 06:32 AM

    Hi

    What is the version of GUP systems ?

    Regards

     



  • 21.  RE: Communication Failure

    Posted Feb 21, 2013 07:25 AM

    Hi

    When the Symantec Endpoint Protection Manager (SEPM) counts the number of deployed licenses, it allocates a license to every client that is online, or that is not currently online, but exists as a client in the SEPM database.

    The typical configuration of the SEPM is that the SEPM will "remember" what clients have attached to it for up to 60 days after they stop checking in before they are deleted and the license is scavenged and made available for redeployment.

    When a newly deployed client first checks in, it will receive its license from the SEPM, and then connect to Symantec servers "in the cloud" to request its Client Authentication Token (CAT). Symantec Endpoint Protection 12.1 associates the CAT with the client ID value (the "Hardware ID") that individually identifies a specific client. If a client receives a new Hardware ID, it will be treated as a new client, and thus must receive a new CAT.

    The Symantec cloud-based servers do not currently implement any level of license re-use or scavenging of licenses from decommissioned clients.

    This means that although the SEPM may correctly report no "over-deployment" of the license, the cloud-based systems hosted by Symantec will still register an over-deployment, and will not provision the new client with a CAT.

    FYR

    http://www.symantec.com/docs/TECH184530