defender firewall not working with recognized profiles

Question

I am currently using Windows 10 and would like to switch the defender firewall settings between under a domain environment and outside of it.

I am connected to a domain network and when I check with netsh advfirewall show currentprofile, the firewall shows that the domain profile is applied.

Despite this, the rules for the private profile and public profile (both with the same settings) are being applied instead of the domain profile.

If the firewall is not recognized as a domain network even though it is supposed to be connected to a domain network, that would make sense. Is there any possible reason why the domain profile rules are applied even though it is recognized as a domain network and domain profile is applied?

Answer 1

Hello,

Just to make sure, following the information in the official article, did you check the next:

"The domain profile applies to networks where the host system can authenticate to a domain controller. " - Meaning that even if is a Domain network, if the computer can't authenticate to a domain controller, it will still not apply the Domain rules.

Reference: https://learn.microsoft.com/en-us/previous-versions/windows/desktop/ics/windows-firewall-profiles

In order to force the transition please try the next:
Changing your network settings can be done in Start > Settings > Network & Internet, select Sharing options from the list. Open up either Private or Public channels, and turn off network discovery, file and printer sharing, or access homegroup connections using the radio station you chose.

-----------------------------------------------------------------------------------------------------------------------

--If the reply is helpful, please Upvote and Accept as answer--

Answer 2

Thank you for your reply!
We are able to communicate with the domain controller and are able to update the group policy, but should we check if the authentication with the domain controller is established in other ways as well?
Should we check to see if authentication with the domain controller has been established in other ways?
Also, network discovery, file and printer sharing was turned on for private and public, so I turned it off.
No change was observed.
It is possible that the defender firewall settings are being overwritten in the group policy, so I would try changing the settings locally in powershell with the group policy unconfigured and try again.
If there is anything else we should check, please let us know.