MicheleP  Freshman Member

Sorry, solved: it was a different SMTP's port

Yes Peter, I confirm what you say

It belongs to the "fake" subnet (see https://mysupport.zyxel.com/hc/en-us/articles/360003321659--ZyWALL-USG-How-to-configure-VPN-SNAT-on-Zyxel-gateways) the other side of the tunnel wants our clients appear. So: our clients relays on 10.0.0.0/255.255.255.0 in our local subnet, but they must appear as 10.11.244.232/29 at…

Thanks Cooldia, in our case the subnet configured on interface lan1 and 2 were respectively 10.0.0.2/255.255.255.0 and 10.0.0.1/255.255.255.0 so there is no overlapping

I left the default value "IPSec_VPN" for related zone and this is not present in the dropdown list of destinations for a policy route. Anyway, I just realized that all this is not working on a server (Windows 2012) while the traffic is correctly routed in the tunnel from a client Windows 10 in the LAN. Even turning off the…

We can't see it, it is property of PA, but I'm confident they did the right configuration because they realize several VPN site to site with different enterprise

Yes: our local subnet is 10.11.244.232/29 while remote subnet is 192.168.0.0/16