Firewall Rule Update Failed for mDNS (Error Reason : Local Port resolved to an empty set)

[Bhuvanasaguni]

Hi Team,

We are facing an issue with Firewall rule set (ID: MDNS-In-UDP). We have tried following methods to resolve

• Refreshing Group Policy using command "gpupdate /force"
• Modifying inbound LPORT to 5353 instead mDNS

Error Information in Event Viewer:

Log Name: Security
Source: Microsoft-Windows-Security-Auditing
Date: xxxx
Event ID: 4957
Task Category: MPSSVC Rule-Level Policy Change
Level: Information
Keywords: Audit Failure
User: N/A
Computer: xxxxxx
Description:
Windows Firewall did not apply the following rule:
Rule Information:
ID: MDNS-In-UDP
Name: mDNS (UDP-In)
Error Information:
Reason: Local Port resolved to an empty set.


Default configuration:

Rule Definition Port Protocol Direction
mDNS (UDP-In) Inbound rule for mDNS traffic. Local: mDNS | Remote: Any UDP In
mDNS (UDP-Out) Outbound rule for mDNS traffic. Local: 5353 | Remote: Any UDP Out


References:

https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc733428(v=ws.10)?redirectedfrom=MSDN
http://kb.eventtracker.com/evtpass/evtpages/EventId_4957_Microsoft-Windows-Security-Auditing_61516.asp
https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/ports-and-protocols.html

Continue reading...