Thread Info
  • State Verified Answer
  • Replies 7 replies
  • Subscribers 3 subscribers
  • Views 13928 views
  • Users 0 members are here
Options
Suggested

Port forward not working

Jacob Jensen

Hello,

 

I cannot for the life of me get port forwarding working. Have read several guides and tried numerous conbinations but with NO luck. This was all working fine on V16.

 

I stumbled across something weird though

 

Its seem that trafic is going the wrong way in the port forwarding rules.......

 

I have filtered on rules 3 which is the RDP port forward rule but all i can see in the log is my internal 192.168.100.50 contacting the outside world.....

Am I misunderstanding something?

 

Regards

Jacob

Parents Reply Children
  • +1 in reply to Jacob Jensen

    Hi Jacob,

    We found , service has been misconfigured for Forwarding rule.

    Service RDP and "Blue Iris" has been created with Source Port/Destination Port TCP (3389) / (3389), TCP (81) / (81) respectively

    Those should be  TCP (1:65535) / (3389)  and TCP (1:65535) / (81). Please update that.

    Other point, we have been already reported issue NC-22584, where with Dynamic WAN interface and Port dnat rule, after reboot of the appliance, it is not working on some environment.

    That has been resolved in SFOSv17 RC-1. If you catch such kind of issue with Beta-2, you can disable/enable the rule, to be worked.

  • 0 in reply to deeptibhavsar

    Thank you! That did it. Im just not sure i ever put in 1:65535 instead of just the actual port name. Is that something new in V17?

     

    Also. I had to delete the whole firewall rule instead of just being able to edit the application rule (from 3389 and 81 to 1:65535) If i tried to edit those in the firewall rule but it gave an error saying that it was being used in a buisness application rule. 

     

    Regards

    Jacob

  • +1 in reply to Jacob Jensen

    Hi Jacob,

    The behavior is from the XG release. The source port should be any, if you don't want to filter from Source IP Address, else it will work only when  Source IP (Any), Source Port (3389), destination ip is your appliance IP  and destination port (3389).

     

    Yes, for you service edit point, the JIRA id is already logged and tracking it via NC-22557

    Regards,

    Deepti

Unfiltered HTML