Firewall will forward RDP but not anything else
-
@notjohn Why have you opened the RDP-port? Bad idea to begin with.
Maybe a dedicated firewall isn't the right tool for you anyway. -
@bob-dig use it for work purposes but understand the implications. Judgement on my decisions unrelated to the post probably isn't what's meant to be here.
-
@notjohn Have you allowed RDP through firewall rules?
If so do you see that rule being hit in the system log?
Provide screenshots. -
@michmoor I dont see the rule being hit on my system log but i can rdp into my public IP so its open and i can scan to see that its open
-
@notjohn When you scan for 25565, is it open? If its not then there is a good chance you have no firewall rule for it.
-
-
@notjohn
and this shows what im seeing when i check the port
but then 25565
same thing happens when using a 3rd party tester
-
@notjohn ahhhhh ok the last screen shot is the one i like
Doesnt seem that port 25565 is open on the server.On the server run the following
netstat -ano | findstr 25565If the port is listening my second question is do you have Windows Firewall enabled.
-
@michmoor i turned off my windows firewall to solve this and it has not been turned back on yet
-
@notjohn
On the server run the following
netstat -ano | findstr 25565Is the port listening?
edit: Turning off windows firewall resolved this?
-
-
@notjohn you execute the command on your Windows box - the same one you have RDP enabled on.
-
@michmoor so i need to run this directly on the server's shell?
-
@notjohn Yes.
For example on my Windows 10 clientnetstat -ano | findstr 5353 UDP 0.0.0.0:5353 *:* 16988 UDP 0.0.0.0:5353 *:* 16988 UDP 0.0.0.0:5353 *:* 21312 UDP 0.0.0.0:5353 *:* 21312 UDP 0.0.0.0:5353 *:* 3424 UDP 0.0.0.0:5353 *:* 21312 UDP 0.0.0.0:5353 *:* 16988 UDP 192.168.40.1:5353 *:* 3100 UDP 192.168.50.241:5353 *:* 3100 UDP 192.168.80.1:5353 *:* 3100 UDP [::1]:5353 *:* 3100 -
@michmoor
the above is my test on 3389 so no its not listening for 25565 -
@notjohn hence your problem. Im not a minecraft expert here so dont know why your application isn't listening on the intended port but PFsense is not at fault.
-
@michmoor seems strange though because its just a port to open its not specific to minecraft, just the default port the game uses, so the fact it isnt getting through is fishy
-
@notjohn Im not sure you understand whats happening here.
The port is not open on your server. If the port is not open then why expect any outside connections to it to work?
Port 3389 is open on your server. The port is allowed on the firewall. Hence RDP is working.
Port 25565 is not open on your server. The port is allowed on the firewall. How can traffic be redirected to a port thats not open? You need to fix that.
Not a pfsense issue
