One or more of your Symantec Endpoint Security (SES) or Symantec Endpoint Protection (SEP) agents is generating the a Client Authentication Token error or warning similar to the message below in the agent System log.
Fatal [Client authentication token request] Submitting information to Symantec failed.
Error Cannot assign a client authentication token. There was a general communication failure.
This document provides general troubleshooting for these types of issues.
Generally caused by the Symantec agent being unable to access tus1gwynwapex01.symantec.com .
Typically when a Symantec Agent is unable to acquire a Client Authentication Token (CAT) it's because the agent does not have network connectivity to the CAT server tus1gwynwapex01.symantec.com . A browser test can be used as a quick test to see if the workstation itself can access the resource.
Eventually the page should redirect to a Broadcom landing page. If any other response is seen, investigate the network for any firewall, proxy or other network filtering device that may be blocking access. Ensure that all of the URLs listed in this article are allowed.
Additionally, you can confirm if an agent has a CAT by viewing the registry location:
HKLM\software\symantec\symantec endpoint protection\{GUID}\identifiers
a CAT (REG_BINARY) should exist with Data. Another useful registry location is
HKLM\software\symantec\symantec endpoint protection\{GUID}\Submissions\CAT
This registry key will have two items
| Value Data | Description |
|---|---|
| 0x00000000 | Success. |
| 0x00000001 | Submissions and reputation queries are disabled. |
| 0x80070057 | Invalid license type. |
| 0x8007000d | License file path location is unknown. |
| 0x80070002 | No license file found. |
| 0x80070005 | Unable to read license file contents. |
| 0x8007000e | Out of memory. |
| 0x80004002 | Cannot load one of the components. |