Hello,
Thank you for posting in Microsoft Community forum.
This issue involves the LAN (Local Area Network) not connecting, while the Wi-Fi connection works fine. Based on your description, you've attempted several common troubleshooting steps, but the problem persists. The issue could be caused by one of the following:
Solution:
- Create a Block Rule: First, create a block rule to block all outbound traffic on UDP port 53. This will ensure that all DNS requests are blocked by default.
Steps:
Open Windows Firewall with Advanced Security.
Under Outbound Rules, click New Rule.
Choose Custom rule type.
In Protocol and Ports, select UDP and specify the remote port as 53.
In Action, select Block the connection.
Name the rule and save it.
- Create an Allow Rule: Next, create an allow rule to permit only specific DNS servers to communicate through UDP port 53. This rule should be more specific and target the IP addresses of the DNS servers you want to allow.
Steps:
Go back to Outbound Rules and click New Rule.
Choose Custom rule type.
In Protocol and Ports, select UDP and specify the remote port as 53.
In the Which remote IP addresses does this rule apply to? section, select These IP addresses and input the IP addresses of the DNS servers you wish to allow.
In Action, choose Allow the connection.
Name the rule and save it.
- Rule Order:
Ensure that the Allow rule is placed above the Block rule. Although Windows Firewall typically processes the most specific rule first, it’s a good idea to manually adjust the order to ensure that the allow rule takes precedence. Right-click on the rule and select Move Up or Move Down to adjust the order.
- Testing:
After applying the rules, use tools like nslookup to test whether the allowed DNS servers are reachable, and verify that all other DNS requests are being blocked as expected.
Summary:
By creating two rules—one to block all UDP traffic on port 53 and another to allow specific DNS servers—you can ensure that only the specified DNS servers are allowed through Windows Firewall while blocking all other DNS traffic. This approach should work as expected and resolve the user's issue.
If the issue persists, check the firewall logs to see if other unforeseen rules are interfering with traffic.