Workstation client, allow firewall *.domain.com?

k2x80w · 2022-07-27T08:08:14+00:00

There was an error rendering this rich post.

k2x80w

I try to allow *.domain.com in one of our firewall profiles, but WithSecure do not allow to use * mark

Internet is blocked and only certain addresses are allowed.

I can put domain.com or subdomain.domain.com,

but I need to allow all subdomains (because I do not know all subdomains)...so *.domain.com

How to do that?

Find more posts tagged with

Accepted answers

All comments

k2x80w

This is funny.

Our problem is Teamviewer.

They told only *.teamviewer.com ...nothing more.

And Withsecure we cannot add *.teamviewer.com

sad...

Sethu Laks

Hi @k2x80w

When configuring the sites/IP addresses into the "Local/Remote IP Addresses" field in the firewall rule, multiple sites/IP addresses shall be separated by comma.

The same practice is applicable, when configuring the port numbers into the "Local/Remote IP ports" field in the firewall rule.

Its because WithSecure Firewall feature integrates with Windows Firewall to do the network filtering. Hence, the configuration follows the limitation from the Windows Firewall, when configuring the firewall rule via the Profile Editor. For example, wildcard is not permitted when defining the application path field in the firewall rule:

https://docs.microsoft.com/en-us/windows/security/threat-protection/windows-firewall/best-practices-configuring

https://social.technet.microsoft.com/Forums/en-US/4d81f0c8-152d-4e02-bc43-5ab4f6438f6a/allow-program-through-windows-firewall-in-user-profile?forum=win10itprosecurity