Firewall rules do nothing, have to disable whole firewall for connection to succeed

LordZylinder 20 Reputation points
2023-08-31T20:47:01.0533333+00:00

Every time i try to setup a (games-)server and let people join from outside my network the, connection fails.

I set up the server, see which ports are needed in there, add those ports to the exception list in my router (this one always works), *add the same ports to my Windows Defender Firewall Inbound- and Outbound-Rules list and it does not work.

I then try to figure out if my Windows Firewall is the problem and disable it for a couple seconds. It Instantly succeeds and as soon as i activate it again the connection fails again. This leads me to believe that the Windows Firewall (in some way, shape, or form) is the problem.

If you have any questions or more troubleshooting advice for me, comment them and I will happily answer and test some more in the hopes to find the problem.

*For Info: I add those rules as follows Inbound Rules>New Rule...>Port>TCP>Specific local ports: [server_port_number]>Allow the connection>For: Domain, Private, Public>Name...>Finish

...also I use Windows 10 Pro

Edit:

Solution: There was a Firewall-Rule that was blocking the port i was using for my server. (Details below)

Windows for business | Windows Server | User experience | Other
0 comments No comments
{count} votes

Accepted answer
  1. Anonymous
    2023-08-31T21:28:10.2766667+00:00

    May need to turn on some logging for the given firewall profile.

    --please don't forget to upvote and Accept as answer if the reply is helpful--

    User's image


2 additional answers

Sort by: Most helpful
  1. Anonymous
    2023-09-01T00:31:36.6366667+00:00

    Looks like the process may use dynamic ports. Might reach out to the developer about port requirements and if there is a configuration to limit any dynamic range.

    --please don't forget to upvote and Accept as answer if the reply is helpful--

    0 comments No comments

  2. LordZylinder 20 Reputation points
    2023-09-01T01:01:13.8766667+00:00

    TLDR; Problem was a Firewall-Rule that blocked the Port.

    That won't be necessary cause it seems like it doesn't and I was my own problem.

    I was just trying to track down if any other rule is blocking it and it actually was. I thaught there shouldn't be any blocking of that port but turns out there was one. It seemes like it happened when I first started the "server.exe" and the windows security alert message popped up asking me which networks I want to allow it to access, I did not check the "public networks" option and it created that block rule automatically.

    Turned it from blocking to allowing and the problem was solved.

    Thanks for the help because without you I wouldn't have googled "when firewall rule is added udp packets still get dropped". (Will check your first comment as the answer cause i can't do it with this one)


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.