New port forwards not working
-
Hi All,
I have read the troubleshooting and tried to follow the steps. Please keep me in mind, I have set up pfSense using multiple guides, and everything is working fine, so I have minimal knowledge in what to check and how to check it.
Currently using v2.8 and switched to KEA while i kept everything else the same.
I have two ports set up from 2.6, and they are working fine. One for Plex and another for Qbit.
I try to copy the settings in the third line "Plex Test" with a different port and using my laptop's IP. Everything looks fine so far. It also creates the firewall rule automatically.
However, when I attempt to test it using Diagnostics - Test Port, only the original ones are successful, while the new "Plex Test" consistently fails. I am not concerned about external yet, I am just trying to get it to pass in pfSense.
Failed
I have tried multiple internal IPs and different ports, even those that are currently working, but they stop. I also made sure to add a pass rule in Windows Firewall, which I don't think would cause any issues, as I am just testing in pfSense. I also turned off pfblocker with no success.
Any guidance, please? And if you can keep it simple for my simple brain, that would help.
I have been at this for a few days now.
-
@flyer123 is there any service listening on Port 32401 on 192.168.1.212 Machine? seems like the port 32401 is closed,
And that Test Port is internally testing Ports, no WAN involved , so the WAN rule has nothing to do with the Test Port page.
for example I am testing Port of 172.16.0.12 : 80 (No Rule for 80 POrt on WAN so far)Result succes: 172.16.0.254 is my pfsense Box
11:18:40.462846 IP 172.16.0.254.62197 > 172.16.0.12.80: tcp 0
11:18:40.463234 IP 172.16.0.12.80 > 172.16.0.254.62197: tcp 0
11:18:40.463250 IP 172.16.0.254.62197 > 172.16.0.12.80: tcp 0 -
@enthu19 No, nothing that i am aware of. I have also tried random ports and numbers but its the same result.
As 192.168.1.212 is a windows machine, i also added a pass rule in windows firewall but it still fails which i dont think would affect the internal pfSense test.
The 2 old ports/rules are successful, its just all new ones fail
-
@flyer123
To establish a successful connection on port 32401, the port must be open and actively listening.Run the following command in Command Prompt on the Windows machine to verify:
netstat -ano | findstr :32401
This checks if any process is currently bound to and listening on port 32401.
If no output is returned, it means there's no service actively listening on that port.In that case, make sure the Plex Service is running and configured to use port 32401. Until a service is listening on that port, any connection attempts will fail—even if the port is open in the firewall.
@flyer123 said in New port forwards not working:
The 2 old ports/rules are successful, its just all new ones fail
Probably the old rules have Listeners on the machine for those ports.
-
@enthu19 I have just used the port in Qbit instead (quicker than setting up plex as i used that as a random description) and now there is an output in cmd.
Still failing in pfSense though
-
@flyer123 32401 port seems to be open and listening, can you disable Windows Firewall temporarily ?
PowerShell
netsh advfirewall set allprofiles state offThen test again from pfSense. or any LAN Machine using PowerShell:
Test-NetConnection -ComputerName 192.168.1.212 -Port 32401
-
@enthu19 wow, thank you, its now working and successful in pfSense after turning off the firewall using the PowerShell command
i did have this pass rule in windows firewall, do you know why it didnt work?
-
@flyer123 probably the rule is on a different profile than the current (active) one, delete it.
Enable Firewall:
netsh advfirewall set allprofiles state onRun this command in Powershell:
netsh advfirewall firewall add rule name="Plex 32401" dir=in action=allow protocol=TCP localport=32401 profile=anythen check again
-