Support articles
Find clear, step-by-step solutions to common WithSecure issues across installation, configuration, updates, and product performance.
Remote Desktop Protocol (RDP) still works after Elements Endpoint Protection Agent has isolated the device from the network
Last updated
Issue:
Remote Desktop Protocol (RDP) to a device is still able to connect after Elements Endpoint Protection Agent has isolated the device from the network. Why does the network isolation not work?
Resolution:
If network isolation has been enabled on a device but the device is still able to access the local network resources and / or some parts of the internet, you need to make sure that you do not have any firewall rules created by Group Policy Object (GPO).
For example, if you have created a firewall rule via GPO to allow Remote Desktop Protocol (RDP) access to the devices, the WithSecure isolate from network rule will not be able to override it.
The WithSecure network isolation feature is based on the Windows Firewall functionality. While this approach has its own merits, it also has a lot of limitations, including inability to override any GPO firewall rules.
If you do not have GPO rules, make sure that you have not created too open Network isolation rules in the Elements profile. The Network isolation rules are taken into use then device isolation is triggered.
- Log in to the Elements Security Center
- Navigate to the Security configurations > Profiles page
- Open the profile that is in use on the device
- Go to the Firewall settings page
- Scroll down to the Network isolation section
- Check the current Firewall rules for WithSecure profile: Network isolation and then the Allowed domains settings to make sure that they do not give too wide access for the device when it has been isolated from the network