Client Security or Server Security Web traffic scanning is blocking HTTP connections to an internal server, URL or of an application

Issue:

When the Client Security or Server Security Web traffic scanning (Advanced Network Protection)  feature is enabled, some applications are slow to start, unable to connect to an internal server and some URLs are inaccessible or some applications have connectivity or performance issues

Java-based applications are slow to start or unable to connect to an internal server or there are connectivity issues.

Resolution:

If the Web Traffic Scanning is causing issues for an application that connects to an internal server or slowness in some Java based applications, you can add the server address as trusted.

This will exclude the network traffic from Web Traffic Scanning.      

How to add the server address as trusted:

1. Log in to Policy Manager Console
2. Select the host or domain from the Domain Tree
3. Go to the Settings tab 
4. Go to the Web content control page
5. Click Add on the right side of the Trusted sites list
6. Enter the server address in the Address column
7. Distribute the policy (Ctrl+D)

No wildcard is needed in the address, for example:

• http://193.110.109.55
• http://sql-server-2008:8080
• SAMPLESERVER:8080

     
If the steps above did not solve your problem, disable Botnet Blocker to see if it is the cause for the issue.

       How to disable Botnet blocker:

1. Log in to Policy Manager Console
2. Select the host or domain from the Domain Tree
3. Go to the Settings tab and select Standard view
4. Navigate to Web traffic scanning and select Botnet Blocker
5. Set the DNS query filtering to Allow all queries
6. Distribute the policy (Ctrl+D)

If disabling disabling the Botnet blocker did not solve the issue, disable DeepGuard temporarily and then try to reproduce the issue. How to disable DeepGuard:

1. Open the Client Security local user interface
2. Go to the Malware Protection tab
3. Click Edit settings from the left side of the user interface to enable administrator rights
4. Disable DeepGuard using the on / off switch

If the issue is resolved by disabling DeepGuard, you can create a global scanning exclusion for the affected application in the policy:

1. Log in to the Policy Manager Console
2. Select a host or policy domain from the Domain Tree
3. Go to the Settings tab
4. Go to the Real-time scanning settings page
5. Scroll down to the Files and applications excluded from scanning table and enable Do not scan the following files and applications 
6. Click Add on the right side of the table 
7. Add the application path and click OK
8. Distribute the policy (Ctrl + D)

It is also good to make sure ORSP Service (Security Cloud) is enabled. You may find more information about the Security Cloud here       

How to enable ORSP via Policy Manager console:

1. Log in to Policy Manager Console
2. Select the host or domain from the Domain Tree
3. Go to the Settings tab 
4. Navigate to Windows > Real-time scanning 
5. Enable Use Security Cloud
6. Distribute the policy (Ctrl+D)

You can run the WithSecure Connection Checker Tool found in the Client Security or Server Security installation folder to make sure that the connectivity to all the back-end services is OK.