Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    RDP NAT/FORWARD

    Scheduled Pinned Locked Moved NAT
    6 Posts 3 Posters 1.8k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • J
      Jamerson
      last edited by

      Hi Guys,
      We are using in production Pfsense between two Subnets Main gateway is Cisco ASA is forwarding all the traffic to the Pfsense WAN ip 192.168.100.20

      Pfsense WAN side Pfsense WAN side is 192.168.100.20 and Lan is 10.0.0.0/24.
      There is Servers behind the Pfsense which need to be accessible from the LAN of the ASA 192.168.100.0/24
      the block private and begon network is unchecked.
      so I've NAT Port MS RDP 3389 to the host 10.0.0.20. I even forwarded the port on the WAN side and it's did not work.
      do i have to NAT or Forward the port in order to get the RDP working ?
      whenever I run a RDP to Server behind Pfsense the RDP failed.

      thank you

      1 Reply Last reply Reply Quote 0
      • KOMK
        KOM
        last edited by

        do i have to NAT or Forward the port in order to get the RDP working ?

        Yes, of course.  Show your port forward and WAN rule.

        1 Reply Last reply Reply Quote 0
        • J
          Jamerson
          last edited by

          @KOM:

          do i have to NAT or Forward the port in order to get the RDP working ?

          Yes, of course.  Show your port forward and WAN rule.

          tomorrow when I am in the office I will upload the rules screenshots.
          do you mean I need both NAT and rules ?
          I mean when you create a NAT it create automatically a rule on the WAN side?

          1 Reply Last reply Reply Quote 0
          • D
            doktornotor Banned
            last edited by

            When your "WAN side is 192.168.100.20", obviously no forwarding will be possible without configuring the "upstream" router first.

            1 Reply Last reply Reply Quote 0
            • KOMK
              KOM
              last edited by

              do you mean I need both NAT and rules ?
              I mean when you create a NAT it create automatically a rule on the WAN side?

              Yes.  Normally the associated firewall rule is automatically created unless you tell it not to.

              When your "WAN side is 192.168.100.20", obviously no forwarding will be possible without configuring the "upstream" router first.

              He mentioned LAN-side on the Cisco so I'm assuming he's trying to access from 192.168.110.x.  Can you clarify, Jamerson?  Which network are you trying to come in from?

              1 Reply Last reply Reply Quote 0
              • J
                Jamerson
                last edited by

                @KOM:

                do you mean I need both NAT and rules ?
                I mean when you create a NAT it create automatically a rule on the WAN side?

                Yes.  Normally the associated firewall rule is automatically created unless you tell it not to.

                When your "WAN side is 192.168.100.20", obviously no forwarding will be possible without configuring the "upstream" router first.

                He mentioned LAN-side on the Cisco so I'm assuming he's trying to access from 192.168.110.x.  Can you clarify, Jamerson?  Which network are you trying to come in from?

                thank you so much guys,
                had to reboot the PFSENSE and stuff start working.
                probably after creating the NAT rule some hangs , the reboot fix it.

                much appreciate it your support

                1 Reply Last reply Reply Quote 0
                • First post
                  Last post
                Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.