Guest User!

You are not Sophos Staff.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 45 replies
  • Subscribers 3 subscribers
  • Views 369360 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Cannot open any ports via NAT or firewall rule but existing ones work?

traderjay
Hi All - I am trying to enable remote access for the Plex server and it requires the opening of ports in the 32xx range. 

I enabled the following DNAT rule: TCP 1:65535 → 32400.

Unfortunately the port remains closed when testing using this site and on Plex Server's network config:
Open Port Check Tool

I tried a variety of port numbers and none of them seemed to work which is very baffling. As a last resort, I tried some common port used by RDP such as 3389 and the connection worked....

Lastly, I am also using the following rule on my UTM:

Internal (Network) -> any -> any

I've also reviewed the firewall log and below is the dropped packet:

2015:10:19-12:30:19 homestation ulogd[6592]: id="2001" severity="info" sys="SecureNet" sub="packetfilter" name="Packet dropped" action="drop" fwrule="60001" initf="ppp0" srcip="54.193.168.189" dstip="24.140.238.16" proto="6" length="60" tos="0x00" prec="0x00" ttl="47" srcport="2985" dstport="32400" tcpflags="SYN"


This thread was automatically locked due to age.
Parents
  • 0
    Interface from > to Internal
    Good to hear you're fixed up.  This is one of a handful of times I've seen an issue being resolved by changing the binding FROM the default >.  Leads me to believe that you may have changed this setting for multiple hosts/groups.  Generally changing this setting from the default can cause odd blockages that make little sense, so hard to troubleshoot, but if it's working for you then so be it.
Reply
  • 0
    Interface from > to Internal
    Good to hear you're fixed up.  This is one of a handful of times I've seen an issue being resolved by changing the binding FROM the default >.  Leads me to believe that you may have changed this setting for multiple hosts/groups.  Generally changing this setting from the default can cause odd blockages that make little sense, so hard to troubleshoot, but if it's working for you then so be it.
Children
No Data