Support articles

Find clear, step-by-step solutions to common WithSecure issues across installation, configuration, updates, and product performance.

Elements Endpoint Protection Firewall blocks the network traffic despite I have created a firewall rule in WithSecure profile to allow it

Issue:

Firewall blocks the network traffic despite I have created a firewall rule in the Elements Endpoint Protection firewall profile to allow it. There is no firewall rule in the WithSecure profile to block the network traffic.

Examples:

From pfirewall.log, it tells that the network traffic was dropped:

2020-11-06 11:14:07 DROP TCP     0 - 0 0 0 - - - SEND

Blocks.ndjson log shows that the connection was dropped:

I: Type: FWPM_NET_EVENT_TYPE_CLASSIFY_DROP. Dropped by layer: ALE Connect v6 Layer. Direction: outbound. Local port: 50262. Remote port: 80.

Resolution:

You need to ensure that the firewall rule has been configured correctly, to allow the required network traffic.

In case the firewall rule has been configured correctly, most likely the network traffic was blocked by either the built-in Windows Firewall rule, or the firewall rule defined via GPO.

The reason is that WithSecure firewall integrates with Windows Firewall to perform network filtering. Network traffic is allowed or blocked based on a combination of all the firewall rules created in the WithSecure Firewall profile, the built-in Windows Firewall rules, and the firewall rules defined via GPO. Firewall rules created via GPO take precedence over a WithSecure profile firewall rule.

Additionally, a firewall rule to block takes precedence over a firewall rule to allow.

You can try to disable "Allow other rules" in the WithSecure firewall profile and see if has an effect:

  1. Log in to the Elements Security Center portal
  2. Navigate to the Security Configurations > Profiles page
  3. Select the profile that is in use on the device
  4. Go to the Firewall settings page 
  5. In the Firewall rules for WithSecure profile section, disable Allow other rules
  6. Click Save profile

This will disable the built-in Windows Firewall rules (but not the Windows Firewall rules defined via GPO).

If this help to workaround the issue, you need to look into the built-in Windows Firewall rules to find out which ones could have blocked the network traffic.

In case the issue remains after disabling "Allow other rules", you can proceed to disable the firewall rules created by Elements Endpoint Protection. You can disable the WithSecure firewall profile altogether to ensure the issue is not caused by firewall rules created by Elements Endpoint Protection:

  1. Log in to the Elements Security Center portal
  2. Navigate to the Security configurations > profile page
  3. Select the profile that is in use on the device
  4. Go to the Firewall settings page
  5. From the WithSecure firewall mode drop-down menu, select Do nothing 
  6. Click Save profile

When the firewall mode is set to "Do nothing", it disables the product firewall integration with the Windows Firewall and remove Windows Firewall rules included in the WithSecure firewall profile, except for some predefined rules to allow the product, DNS, and DHCP traffic.

If the issue persists after disabling all the firewall rules created by Elements Endpoint Protection, then the issue is not caused by the product’s firewall rules.

Next step would be to make sure the issue is not caused by any other Elements Endpoint Protection feature. You can disable all security features by following these steps:

  1. Log in to the Elements Security Center (https://elements.withsecure.com)
  2. Navigate to the Security Configurations > Profiles page
  3. Select the profile that is in use on the device
  4. Go to the General settings page 
  5. Scroll down to the Security features section and enable Allow users to turn off all security features 
  6. Click Save profile

Once the profile has been taken into use, from the local of WithSecure Elements Agent user interface, a user can click on the three dots and select Turn off all security features. 

If you are able to reproduce the issue after disabling all the security features, the issue is not caused by the Elements Endpoint Protection product.

If the issue is not caused by Elements Endpoint Protection firewall rules or security features, continue to troubleshoot the firewall issue by checking if any block rules are created by GPO.