1

I'm configuring a new Windows Server 2019 VPS. I have set the firewall on the Public Profile to "Inbound connections that do not match a rule are blocked"

Public Profile configuration screenshot

I have setup 2 rules to allow connections to my SSH server, and to allow web traffic through, as you can see here:

Inbound rules screenshot

There's also a 3rd rule there to block traffic to port 3389 (RDP). That's the problem - without the RDP blocking rule, traffic is allowed through to port 3389, even though the Firewall is configured to "Inbound connections that do not match a rule are blocked". It makes no sense!!

I have double-checked that the network profile is indeed set to Public, which it is. The Firewall is obeying the block RDP rule, but without it there, it allows RDP traffic.

Does anybody understand what's going on here?!

Improve this question

1 Answer 1

Reset to default
1

Wow, I just found the answer to this. I have been managing the firewall via gpedit.msc. I just opened up the 'Windows Defender Firewall with Advanced Security' link in Control Panel\System and Security\Administrative Tools and found a load of rules in place which were not visible in gpedit.msc. Hence why stuff was getting through that I was not expecting to get through.

Improve this answer
1
  • If the rule does NOT appear in Control Panel > ... > Allowed apps, it would NOT work. After re-adding firewall rule in wf.msc, it shows up there and works.
    – Ivan Chau
    Dec 1, 2022 at 9:48

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .