RDP connections won't work if Browsing protection is enabled. Unknown error immediately after trying to login. Is this bug and if so, when it is going to be fixed?
Hi @Jukka
Please upload the fsdiag with additional details in the support ticket here https://www.withsecure.com/en/support/contact-support/email-support
Hi @Sethu
Where can I send fsdiag.zip?
Interesting detail. If you have existing RDP connection when Browsing Protection is turned on. Everything works fine, even new RDP connections. When all RDP connections are terminated, you can't open new ones until Browsing Protection is disabled.
To find the root cause, we need to analyze the diagnostic logs. We can provide further assistance to you through our Support team.
Connection control and Block remote access during banking session was never enabled for us.
RDP connection to Server 2022 is only Windows version that doesn't work with these settings.
Currently, there is no way to exclude a particular process from the "Remote access blocking" feature.
This feature activates only when connection control is activated - when a user visits some banking or similar site. During this time more restricted rules applied including Remote Access.
The exclusion could be implemented in future versions if there is demand for that.
Connection Control Remote Access blocker blocks for example:
Alternatively, you can disable the feature in the Policy Manager.
