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

    After replacing my Dylink router with Pfsense I can no longer RDP to my Windows

    Scheduled Pinned Locked Moved NAT
    13 Posts 5 Posters 2.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.
    • D
      doktornotor Banned
      last edited by

      You need TCP+UDP for RDP.

      1 Reply Last reply Reply Quote 0
      • K
        kejianshi
        last edited by

        Try forwarding both TCP and UDP.

        Also, just to be sure - Make sure pfsense WAN interface is showing a public IP - not private.

        Also try rebooting pfsense after you forward both TCP and udp apply the rule.

        1 Reply Last reply Reply Quote 0
        • K
          kejianshi
          last edited by

          Damn that guy can type fast….

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

            Thank you Guy - will try and get back to you soon with outcome.

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

              Hi Guys,

              I changed TCP to TCP/UDP and rebooted pfSense.  Same outcome.

              The WAN port is picking up a Public IP and the RDP  request is visible in the pfSense Log with a green triangle next to it  … but I can not trace it to the State Table.

              Any ideas?

              Thank you

              1 Reply Last reply Reply Quote 0
              • K
                kejianshi
                last edited by

                Try it from something other than a cell based connection.

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

                  Filtering Diagnostics > States on :3389 while attempting to connect should certainly show something.

                  I know you state it worked with the d-link, but are you sure the target server has pfSense as its default gateway?  Are you sure it's not a software firewall issue on the target server?

                  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
                  • J
                    j601
                    last edited by

                    Hi Derelict

                    Thank you for pointing me in the right direction.

                    I stated that I did not make any changes on my network and obviously I had to make one simple but very important change.

                    D-Link was on IP 192.168.1.1 and pfSense is on 192.168.1.3.  On the Server the Gateway was 192.168.1.1. The Workstation that I use I have a static IP.  When I connected pfSense I changed the gateway to point to 192.168.1.3. I intended to go and make the change on the Server.  You reminded me to do just that.

                    Changed the Gateway on the Server and the RDP connection works!

                    A beginner’s mistake is fixed.

                    Thank you again,

                    1 Reply Last reply Reply Quote 0
                    • chpalmerC
                      chpalmer
                      last edited by

                      @doktornotor:

                      You need TCP+UDP for RDP.

                      I never have any UDP rules for RDP..  Just TCP.

                      :o

                      Triggering snowflakes one by one..
                      Intel(R) Core(TM) i5-4590T CPU @ 2.00GHz on an M400 WG box.

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

                        You can see what's being use like this:

                        (UDP being used since RDP 8.0 - W7 with KB2592687 and any later versions. It should fallback to TCP but someone @M$ obviously finally realized that TCP sucks for RDP over WAN…)

                        1 Reply Last reply Reply Quote 0
                        • chpalmerC
                          chpalmer
                          last edited by

                          Ill give it a try…  I find other solutions for remoting in have always been a little better.  Id like the MS version to be similar in performance.

                          :)

                          Triggering snowflakes one by one..
                          Intel(R) Core(TM) i5-4590T CPU @ 2.00GHz on an M400 WG box.

                          1 Reply Last reply Reply Quote 0
                          • K
                            kejianshi
                            last edited by

                            Yeah - over a long haul, having that UDP port open SHOULD knock off alot of laggyness.

                            I use UDP VPN myself.  I'm not a big fan of opening ports on the wan for RDP directly.

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