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

    NAT works on Port80, but not 3389

    Scheduled Pinned Locked Moved NAT
    3 Posts 3 Posters 535 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.
    • W
      wired-circuit
      last edited by

      This is an odd one.  I have a working NAT Rule setup with auto created firewall rule, this is on port 80 and it works just fine.  However when I do the very same thing and point at 3389 for RDP, it does not work.  I have verified that port 3389 and RDP are open and enabled respectively and have even redirected to another Windows machine to verify.  PFSense is simply ignoring it!?!  Any ideas of what I might look at here, I'm at a loss..

      Thanks

      1 Reply Last reply Reply Quote 0
      • johnpozJ
        johnpoz LAYER 8 Global Moderator
        last edited by

        Why anyone in their right mind would open up rdp to the internet is beyond me.. If you want/need to rdp to your boxes behind pfsense then vpn in..

        So you sure your windows machine firewall allow rdp from network other than local.. Out of the box windows machines would be blocking this.

        So you went through the troubleshooting doc?
        https://doc.pfsense.org/index.php/Port_Forward_Troubleshooting

        You sniffed on pfsense lan or whatever opt interface your windows machines are connected too and verified that your not sending the packets that you got on your wan to your lan..

        An intelligent man is sometimes forced to be drunk to spend time with his fools
        If you get confused: Listen to the Music Play
        Please don't Chat/PM me for help, unless mod related
        SG-4860 24.11 | Lab VMs 2.7.2, 24.11

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

          PFSense is simply ignoring it!?!

          No, pfSense is doing what it is being told to do which is apparently incorrect. Or some other issue is keeping it from working. See the above troubleshooting document for a pretty comprehensive list of things to check. And don't just skim them. actually check them all.

          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
          • First post
            Last post
          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.