The issue described pertains to the unexpected behavior of Windows Server 2022 firewall rules, where RDP access from a specific management system is inconsistently blocked or allowed. The server is configured with Group Policy to manage its firewall settings and has logging enabled for different network profiles (public, private, domain). Initially, RDP traffic from the specified management system is dropped by the public profile firewall despite being on the domain network. After updating the policy to allow RDP access from everywhere and then reverting back to the initial setting, RDP access inexplicably starts functioning as expected without any further changes. This anomaly indicates a potential issue with how the Windows Server 2022 firewall interprets or applies Group Policy settings in certain configurations, leading to inconsistent network traffic control.
- Windows Server 2022
- Ensure Group Policy settings for the Windows Firewall are correctly configured by reviewing and testing rule application under different scenarios.
- Check the firewall logging files to monitor how changes in policy affect traffic control, specifically looking at 'public' and 'domain' profile logs.
- Consider using a consistent approach to manage firewall rules, such as ensuring that merge local is set appropriately based on organizational requirements.
Minimal direct impact. This issue primarily affects the management of firewall rules through Group Policy in homelab environments using Windows Server 2022.