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

book

Article ID: 227118

calendar_today

Updated On:

Products

Protection Engine for Cloud Services

Issue/Introduction

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).

Resolution

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

Workaround

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.