After installing Symantec Endpoint Protection (SEP), you see the following:
- Traffic to the Download Insight servers is blocked when using proxy servers with authentication defined by URL or .PAC proxy settings.
As a result, Endpoint Protection cannot use the reputation data on the Download Insight servers to evaluate potential threats.
- Endpoint Protection licenses cannot be activated when using a proxy server.
- Symantec Endpoint Protection Manager (SEPM) cannot be enrolled with Cloud services when using a proxy server or other network traffic filtering device.
- Symantec Endpoint Protection Manager is having trouble communicating with Cloud services post enrollment when using a proxy server or other network traffic filtering device.
Endpoint Protection is designed to communicate with specific URLs owned by Symantec to validate licenses, submit samples of suspicious files, and use file reputation security features.
If a proxy or corporate firewall blocks access to these URLs, these issues can occur.
Exclude the appropriate URLs listed in this article within your proxy server's configuration, which allows the necessary traffic to Symantec's servers.
Ping submissions are per definition type (for example, antivirus), and allow Symantec to judge the effectiveness of a set of definitions that are not yet taking any action, such as beta detections, based on the number of "pings" each detection or definition creates. For example, if a detection creates a number of ping replies to Symantec, this detection may be a false positive detection and will be investigated for effectiveness.
This system and related URLs are part of Symantec's false positive avoidance system.
These URLs are designed to accept samples of any detections that are made by the clients. If a client gets a detection, the client queries Symantec to see if a sample is needed (that is, no formal definition created for this item yet).
If a sample is not needed because a formal definition is already created, the client will not submit the sample. This query response system effectively reduces the network traffic created by SEP, and makes SEP more responsive to new and emerging threats.
Client Authentication Token. This is how a client authenticates itself to Symantec to make use of the reputation servers for Download Insight, for example. This is required.
If SEP generates an error report due to a component crash, SEP uses this URL to report the error and associated data back to Symantec.
Data sent back to the client from a reputation query.
URL that SEP clients send reputation requests to. Note that client traffic to ent-shasta-rrs.symantec.com.ntn.symantec.com may also be observed. This URL is used for DNS name resolution to ent-shasta-rrs.symantec.com.
URL that SEP uses to verify if the license being used is current and active.
URL SEP uses to check the license status.
URL that SEP uses to connect to for definition updates.
Endpoint Protection Manager Windows definitions "Latest from Symantec"
Data sent to Symantec about the SEP or SEPM install, i.e. how SEP is being utilized by the customer base.
Data sent to Symantec about installation related events.
Data and crash dumps for processes sent to Symantec to help make the product better.
SEPM Cloud services
Cloud console access.
Enroll and Unenroll of SEPM.
REST Request Router.
SEPM Cloud notification service.
Cloud storage serivces.
See How test connectivity with Insight and Symantec Licensing servers for troubleshooting steps.
Imported Document Id