Why is NAT proving to be so difficult…..?



  • Hi everyone,

    for over a week ive been trying to port forward (RDP 3389) to an internal host so that i can access it from work, and i just cannot seem to figure out what im doing wrong, i followed an pfsense article word for word of how to setup NAT to no avail..  :-[
    firewall Rule also created auto-

    Here is my setup -

    Vigin Modem>TP-LINK Router>PFsense>LAN

    so basically i have a Virgin Modem connected to a hardware router IP- 192.168.5.1 which is connected to a Pfsense firewall. (Virtual Machine)

    The WAN IP for the Pfsense is [b]192.168.5.6 and the LAN IP is 192.168.0.1

    I have port forwarded port 3389 from Hardware router (TP-LINKS) to the IP of pfsense WAN ip- 192.168.5.6

    so what is going on guys, as im begining to lose my faith in Pfsense as its proving to be too dificult to setup?

    Thanks in Advance!




  • Rebel Alliance Developer Netgate

    Remove the source port range. You almost never (ever, seriously) want to set a source port range, especially on a nat rule.



  • thanks for the reply,

    so what do i specify there any or other?

    thanks


  • Banned

    Any…

    @zaf:

    thanks for the reply,

    so what do i specify there any or other?

    thanks



  • Excellent! Thats worked, you are a star!!!!

    Thank you very much for a quick resolution- i was almost about to give up on Pfsense!

    Thanks


Locked