Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 14 replies
  • Answers 1 answer
  • Subscribers 26 subscribers
  • Views 3680 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

S2S - no connection to remote server

Philipp Marx

Hey,

I would like to connect to a remote server via VPN. The s2s connection works but Iam unable to reach the server on the other side (the remote site is one host only).

I can see that the outgoing traffic goes through the firewall rule LAN to WAN, if I will connect from the local subnet 172.20./16 to the remote server 172.20.200.49.

So whats missing / wrong? Do I have to create a further rule/route - where ?

Thanks in advance!



This thread was automatically locked due to age.
Parents Reply Children
  • 0 in reply to Philipp Marx

    Hi  

    Please see the attached screenshot and disable NAT configuration



    Please create firewall rules LAN to VPN and VPN to LAN.

    Please enable "MASQ" oprion in LAN to VPN rule.

  • 0 in reply to Keyur

    Hi Keyur, 

    we have disabled the nat rule in the vpn gateway settings. 

    Then we have updated the firewall rule for LAN to VPN.

    The "local" remote subnet 10.200.x.x is used for the vpn connection and is configured under "host and services > IP Host" only.

    For our understanding we have to create a route for our local working subnet 172.20.x.x into the 10.200.x.x as well?! 

    We can see that the outgoing traffic to 172.27.200.49 still goes through the "internal > wan" rule. 

     

  • 0 in reply to Philipp Marx

    Hi  

    Could you please let me below details?

    The IP address/Network behind the XG firewall wants to access the server at a remote location.

    Remote server IP address/Network.

    In the screenshot of the firewall rule, in the Source Network, you have defined two networks 172.20.0.0 and 10.200.206.0

    In the IPsec configuration, you have added network 172.20.0.0/16 

  • 0 in reply to Keyur

    Hi Keyur, 

    first, thanks for your time!!

    May be this graphic will help to understand the problem:

     

    The gateway VPN IPSec configuration is as follows: 

    The Firewall Rule LAN to VPN:

    VPN to LAN:

    Regards 

    Philipp

  • 0 in reply to Philipp Marx

    Hi  

    Thank for providing the details diagram.

    Is there any specific requirement to use a 10.200.206.0/24 network for VPN communication?

    We can get it to work by adding network 172.20.0.0/16 as Local subnet and 172.27.200.49/32 as a remote subnet in the IPsec VPN configuration.

    If routes are added for the network 172.20.0.0/16 in XG firewall and it's reachable (I am assuming it is).

    In LAN to VPN rule, you do not require to specify any network, keep it "ANY" for Source and Destination network.

    Second Scenario

    If you wish to NAT the traffic of the network 172.20.0.0/16 with 10.200.206.0/24

    In the IPsec configuration

    Local Subnet - 172.20.0.0/16

    Remote Subnet- 172.27.200.49/32

    Enable NAT- It will show 172.20.0.0/16 by default and NAT to select 10.200.206.0/24

    It will NAT outbound VPN traffic from 172.20.0.0/16 network to 10.200.206.0/24 network



    Y    ou can use troubleshooting guide- https://community.sophos.com/kb/en-us/123320

  • 0 in reply to Keyur

    Hello Keyur, 

    first scenario: 

    yes, that are requirements from our customer. But I will ask him if we could change the subnet. 

    second:

    The problem is if we change the local subnet to 172.20.x.x instead of 100.200.x.x the vpn connection will not come up. We could verify it with our customer that for the authentication we had to use the 100.200.x.x. network. Therefore the second scenario will not work.