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

    LAN to WAN Connection

    Firewalling
    4
    5
    817
    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.
    • G
      glennyboy
      last edited by

      Good day.

      WAN IP:  203.160.160.101

      How can i access the WAN IP inside the network?

      • RDP for testing purposes.

      Thanks in advance.

      1 Reply Last reply Reply Quote 0
      • A
        almabes
        last edited by

        I'm not quite sure what you're wanting to do.  Are you trying to port forward port 3389 from an internal IP to the WAN interface of your firewall?

        1 Reply Last reply Reply Quote 0
        • G
          glennyboy
          last edited by

          thank you for the reply.

          Objective:

          • i already connected to RDP thru LAN
          • i cant connect to RDP from LAN to WAN, but if im in a different WAN i can connect to RDP.

          When im in same WAN cant connect from LAN to WAN.

          Thank you.

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

            LAN Reflection if you must. Split DNS is a better solution.

            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
            • jahonixJ
              jahonix
              last edited by

              @glennyboy:

              How can i access the WAN IP inside the network?

              Not at all.
              There's no "reflector" on the internet to push your packets back into your WAN interface.
              Testing NAT and rules from inside simply is not possible.

              Every other suggestion (NAT reflections, split DNS) is like using your local IP which you already did.

              1 Reply Last reply Reply Quote 0
              • First post
                Last post