Branch Office VPN host not reachable

Possible you have the 172.16.16.0/24 at the branch location too..

Because it is the initial used configuration-interface ... this error occurs sometimes.

Hi Adekunle,

As indicated by dirkkotte, both sides might have the same network and are overlapping.

Your branch network is reaching the internal 172.16.16.0/24 network instead of the HO.

Check the  KBA as a reference for configuring NAT over IPSec with an overlapping network

https://soph.so/TrenKz

A wonderful day to your Dirk. I ll be heading to the center on Thursday and i will give you the feedback.

Thank you so much for your time and attention.

I do appreciate your effort. Ill be there this Thursday for further update. I really guess as much though.

i tried all steps. still stating unreachable.

not working. i deleted the whole process and then started a fresh one. still the same.

after checking your screenshots, i found the subnet 172.16.16.0/24 at booth locations.
If PORT1 in BO is not connected/used. You should remove the IP from this interface (or clear the interface-config at all)

Thank you. currently i am using 172.16.16.0/24 at both end. configure everything correctly using the same link (https://soph.so/TrenKz) sent to me. still not working.

ok, but if you follow the link (and create double-NAT) you should NOT ping 172.16.16.34 to reach a device at the "other-side".

Because the subnet (172.16.16.0/24) is local and "directly connected", the traffic stay local.

Corresponding to the guide ... you should ping an "alias-IP" like 172.16.22.34 ... which is routed to the other side and the other side do NAT 172.16.22.34 back to 172.16.16.34.

A really bad configuration.

First you should try to change the IP-range at one side ... it is more simple (mostly) than NAT and DNS manipulations...