Kitaab

We have a ePO superAgent serving as repository to another ePO deployment across Firewall. The repository was shared and permissions were in place to access it from the ePO server. When we added the repository as source for the ePO it did validate the credentials , however the ePO Wizard failed to list the content of the repositiry in the console. In order to get this working , we needed to create a new share on the SuperAgent instead of utilizing the SuperAgnet repository Then the ePO server configuration was modified to include the new share and everything worked fine after that. Hope this helps/

We faced issue where in Checkpoint IPS flagged certain traffic between ePO server and a remote repository (SuperAgent) and was rejected , thus causing file replication fail between ePO and SuperAgent over Port 8081 When we checked firewall for logs , it was particular identifying the traffic as SQL injection for HIPS content. As we checked HIPS content included files for HIPS and the ePO part that require SQL code for rules to be added / removed or modified in the ePO DB. In the end we had to put exception in IPS to  trust ePO traffic and everything worked fine. Hope this helps