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

    Issue with RDP NAT

    Scheduled Pinned Locked Moved NAT
    3 Posts 3 Posters 470 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.
    • N
      nickolas80
      last edited by

      Hello,
      I'm attempting to setup a NAT to forward 3389 traffic to a machine on the LAN.

      I believe it's setup correctly, however when I attempt to connect from outside the network, it passes the inital connection stage but then hangs on 'configuring remote connection'.
      Could this be a loopback issue?

      I am able to successfully connect to that machine from inside the network.

      I've attached 2 images, one showing the NAT rule and the other showing the access rule.

      Any advice  is greatly appreciated.

      Thanks
      nat.png
      nat.png_thumb
      access.png
      access.png_thumb

      1 Reply Last reply Reply Quote 0
      • NogBadTheBadN
        NogBadTheBad
        last edited by

        Create a vpn connection, its more secure than opening up RDP to the world.

        Think you may need to change it to tcp/udp, I'm not a Windows guy.

        https://en.wikipedia.org/wiki/Remote_Desktop_Protocol

        Andy

        1 x Netgate SG-4860 - 3 x Linksys LGS308P - 1 x Aruba InstantOn AP22

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

          @NogBadTheBad:

          Create a vpn connection, its more secure than opening up RDP to the world.

          Think you may need to change it to tcp/udp, I'm not a Windows guy.

          https://en.wikipedia.org/wiki/Remote_Desktop_Protocol

          Agree with VPN, but at the very very least use a different External port forwarded to 3389 internal, also do UDP/TCP, UDP is used when available and faster, though shouldn't be required.

          The portforward looks correct.

          Do you have only a single WAN IP? Do you have anything special for Outbound NAT? Does pfSense have the WAN IP direct on its WAN interface?

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