The FW 3 server does not see local networks on the Control 2 server. You must add LAN 2 and VPN 2 to the local networks on Control 1:

1. In the Control 1 administration interface, go to Interfaces.
2. Double-click the IPsec VPN tunnel.

VPN tunnel properties

3. On the Local Networks tab, select Use automatically determined local networks.
4. Select Use custom networks.
5. Click Add.
6. In the Add Route dialog box, define all networks from the remote endpoint of Kerio VPN tunnel, and their masks and descriptions. In our example, the networks are LAN 2 and VPN 2.
7. Click OK twice.

The Control 2 server does not see local networks on the FW 3 server. You must add all FW 3 routes to the remote networks on Control 2.

1. In the Control 2 administration interface, go to Interfaces.
2. Double-click the Kerio VPN tunnel.

Remote Networks configuration

3. On the Remote Networks tab, select Use custom networks
4. Click Add.
5. In the Add Route dialog box, define networks on the IPsec tunnel endpoint and their masks and descriptions. In our example, in the networks are LAN 3 and VPN 3.
6. Click OK twice.

To make VPN 3 and LAN 3 visible to users connected through VPN 1, you must add VPN 3 and LAN 3 to the local routes of the Kerio VPN Server.

1. In the Control 1 administration interface, go to Interfaces.
2. Double-click VPN Server.
3. In the VPN Server Properties dialog box, click the Kerio VPN tab.
4. Click Custom Routes

VPN Server properties

5. In the Custom Routes dialog box, add LAN 3 and VPN 3.

Adding custom routes

6. Click OK twice.

From now on, all users connected through VPN 1 see all users connected to VPN 3.

At this point, the setup is finished. To verify that all computers and VPN subnets in the network can communicate, send multiple ping commands from one network to another.