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

    Cant forward Windows RDP

    Scheduled Pinned Locked Moved Firewalling
    7 Posts 3 Posters 1.3k 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.
    • R
      rjabella
      last edited by

      Good day everyone, Im new to pfsense and ive set it up to a virtual environment with 4 interface 3 of them is wan with different ISPs .
      now my problem is when I created a rule in NAT port forward to allow remote desktop from interface WAN1 to the server in local network, i cant get it to connect to the local server when connecting form remote site using the public IP in WAN1 interface. I guess some kind of default rune in pfsense's firewall is blocking the connection…please see my attached configuration and firewall screenshots.https://drive.google.com/file/d/0B9_oQ2J6Bg1gUDV0MmExT0NPN0U/view?usp=sharing
      https://drive.google.com/file/d/0B9_oQ2J6Bg1gNDRjSHNXSVpYM3M/view?usp=sharing
      Please help :-[

      1 Reply Last reply Reply Quote 0
      • N
        NOYB
        last edited by

        Don't specify the source port range.  It is dynamic so you don't know what it will be.

        1 Reply Last reply Reply Quote 0
        • R
          rjabella
          last edited by

          thanks for the reply :)

          ive set the source port range to any…still cant connect...

          1 Reply Last reply Reply Quote 0
          • DerelictD
            Derelict LAYER 8 Netgate
            last edited by

            https://doc.pfsense.org/index.php/Port_Forward_Troubleshooting

            Chattanooga, Tennessee, USA
            A comprehensive network diagram is worth 10,000 words and 15 conference calls.
            DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
            Do Not Chat For Help! NO_WAN_EGRESS(TM)

            1 Reply Last reply Reply Quote 0
            • N
              NOYB
              last edited by

              Not directly relevant to your RDP issue, but at  some point you should probably consider using a VPN server for remote access instead of using RDP.  Should be much more secure.

              1 Reply Last reply Reply Quote 0
              • DerelictD
                Derelict LAYER 8 Netgate
                last edited by

                ^^^

                Chattanooga, Tennessee, USA
                A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                Do Not Chat For Help! NO_WAN_EGRESS(TM)

                1 Reply Last reply Reply Quote 0
                • R
                  rjabella
                  last edited by

                  finally get it to work…changed source port to MS RDP and added a rule in my WAN1 firewall to accept RDP to LAN...thanks everyone  :)

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