If An圜onnect filter was having the same issue, we would have seen a prompt from Cisco's end. Here the SEP Network Content filter seems to not be able to work with An圜onnect socket filter, hence the warning is given from SEP side. The 2 Socket filters (An圜onnect and SEP) should be independent of each other. I reviewed this issue and it seems like the Symantec Endpoint Protection (SEP) is aware of the incompatibility from their side and is working on the same for providing a solution, as stated in the broadcom KB article:
This occurs with An圜onnect version 3, version 3 and 2. I am unable to rollout Big Sur until we have both An圜onnect and Symantec Endpoint antivirus protection, but the current situation is unusable. When we click Finish Setup, Symantec Endpoint will re-enable Network Content Filtering, and the warning message will go away, only to return another ten to fifteen minutes later. Unfortunately, Symantec Endpoint Protection also wants to Filter Network Content too, and they were installed first:Īfter we enable Cisco An圜onnect's Network Content Filtering, this will conflict with Symantec Endpoint Protection's Network Content Filtering, and Symantec Endpoint will present a warning message every ten to fifteen minutes indicating we are not protected:
Symantec Endpoint Protection v14.3 RU1 will run without a problem on Big Sur until Cisco An圜onnect is installed.Īfter the "Cisco An圜onnect Socket Filter" is enabled as part of the An圜onnect install procedure, Symantec Endpoint will display a warning indicating that Setup hasn't completed and the Mac is not protected.Ĭisco An圜onnect Socket Filter would like to Filter Network Content If I can just flesh out this issue a little more, we have noticed a Networking Content Filtering conflict between Cisco An圜onnect 4.9.x and Symantec Endpoint Protection v14.3 RU1 (.1000) running on MacOS Big Sur.
0 kommentar(er)
