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

    Portfoward not working but IPSEC VPN works, something im missing?

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    2 Posts 1 Posters 324 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.
    • S
      scottrotton
      last edited by

      Hi All,

      i have a new pfsense setup im trialing, im very familiar with sonicwalls but this is the first PFSENSE i have setup. im trying to port forward to 3389 to a testmachine i have setup. Config looks like this

      Anyway setup is as follows

      AWS VPC
      172.16.0.0/16

      Private
      172.16.0.0/24

      Public
      172.16.1.0/24

      I have an internet gateway to the PFsense on the public side of AWS
      PFsense
      private ip: 172.16.0.254
      public ip: 172.16.1.116, 52.65.x.x.x (not giving out public IP yet)

      setup is set to port forward
      NAT: dest = wan address, Port 3389, translate to 172.16.0.99
      Firewall rule = 3389 allow all

      When i test externally it doesnt work. via 52.65.x.x.x

      When i connect to a IPSEC VPN i can see the other network, and conect to RDP on 172.16.0.99

      When i diagnose using test port, it says it can reach port 3389 if i select interface LAN.

      So it seems maybe im missing something simple as when i connect to VPN i can see the other network. I should add i have changed the ip address on the VM to

      172.16.0.99
      255.255.255.0
      GW 172.16.0.254 (LAN address of pfsense)

      Any help is appreciated

      1 Reply Last reply Reply Quote 0
      • S
        scottrotton
        last edited by

        Ignore i was using the WAN IP address to create the rule, when i should of been using the public facing local IP

        which in my instance was 172.16.1.116

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