ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Unable to connect to the standard ICAP interface of Protection Engine with secure ICAP is enabled


Article ID: 227118


Updated On:


Protection Engine for Cloud Services


When Secure ICAP is enabled per Configure the secure ICAP options clients can no longer connect to Symantec Protection Engine (SPE) on the standard ICAP port configured (default 1344).


This is by design, when secure ICAP is enabled for SPE, the SPE instance in question no longer listens for standard ICAP communications.


If both secure and standard ICAP are required in the same environment, Symantec recommends implementing at least two SPE servers, one to provide secure ICAP, and one to provide standard ICAP.