Skip to main content
technician
technician
New Member
July 6, 2017
Question

unable to reach NAT'ed IP

  • July 6, 2017
  • 1 reply
  • 3134 views

Hi, we have a 2 servers which are NAT'ed on 2 public IP's on a branch office. Here in our main office, I can connect remotely to the branch office using their public IP's i.e rdp, ssh, etc

 

My issue is, inside the branch office definitely you're going to use their LAN or private IP in connecting to each other, but whenever I used both of their public IP's to each other, it doesn't work. 

Server1 connects to Server2 or vice versa (via private IP) = good

Server1 connects to Server2 or vice versa (via public IP) = no go

 

Though I know it is better and faster to use the private IP, I'm just curious if is it possible to use the public IP?

 

Thanks

Jeff

    1 reply

    net1
    net1
    New Member
    July 10, 2017

    Hi Jeff,

     

    its possible, but due to the change of behauviour between 5.2 and 5.4 you have to use hairpinning ... (https://en.wikipedia.org/wiki/Hairpinning)

     

    So you have to create a policy with:

    source interface: internal

    source ip: your internal network

    destination Interface: internal

    destination ip: your mapped IP, which you normally use with the wan to lan policy (i know, looks strange ... ;) )

     

    Greez

    Claus

    technician
    technicianAuthor
    New Member
    July 11, 2017

    @net@work

     

    Thanks, yes, been reading this hairpinning and will do some tests about this. 

     

    Thanks

    Jeff

    Terms & ConditionsAccessibility statement