Trouble connecting to QuickVPN?

Question

Cisco

There is a task to connect 2 offices through VPN. Where the Cisco router should connect, the equipment is configured correctly, the work has been tested on many clients.
From my side, w2k8 R2, with two network cards, working as a gateway for the local network.
The Internet looks white ip, gateway and dns from the provider, the local address of the server is 192.168.0.1
Accordingly, my subnet is 192.168.0.0/24, I need to get into the subnet 192.168.1.0/24. QuickVPN is used to connect. The connection is not established.
Here's what happens in the logs of the QuickVPN client.:

2011/07/07 08:52:57 [STATUS]OS Version: Windows 7<br/>
2011/07/07 08:52:57 [STATUS]Windows Firewall Domain Profile Settings: ON<br/>
2011/07/07 08:52:57 [STATUS]Windows Firewall Private Profile Settings: ON<br/>
2011/07/07 08:52:57 [STATUS]Windows Firewall Private Profile Settings: ON<br/>
2011/07/07 08:52:57 [STATUS]One network interface detected with IP address 192.168.0.1<br/>
2011/07/07 08:52:57 [STATUS]Connecting...<br/>
2011/07/07 08:52:57 [DEBUG]Input VPN Server Address = 95.х.х.х<br/>
2011/07/07 08:52:57 [STATUS]Connecting to remote gateway with IP address: 95.х.х.х<br/>
2011/07/07 08:53:01 [STATUS]Remote gateway was reached by https ...<br/>
2011/07/07 08:53:01 [STATUS]Provisioning...<br/>
2011/07/07 08:53:11 [STATUS]Success to connect.<br/>
2011/07/07 08:53:11 [STATUS]Tunnel is configured. Ping test is about to start.<br/>
2011/07/07 08:53:11 [STATUS]Verifying Network...<br/>
2011/07/07 08:53:17 [WARNING]Failed to ping remote VPN Router!<br/>
2011/07/07 08:53:20 [WARNING]Failed to ping remote VPN Router!<br/>
2011/07/07 08:53:23 [WARNING]Failed to ping remote VPN Router!<br/>
2011/07/07 08:53:26 [WARNING]Failed to ping remote VPN Router!<br/>
2011/07/07 08:53:29 [WARNING]Failed to ping remote VPN Router!<br/>
2011/07/07 08:53:31 [WARNING]Ping was blocked, which can be caused by an unexpected disconnect.<br/>
2011/07/07 08:53:33 [STATUS]Disconnecting...<br/>
2011/07/07 08:53:42 [STATUS]Success to disconnect.

This software at startup creates an IPSec tunnel, where it takes the starting point (closest to the network) - 192.168.0.1, the final one - 95.x.x.x. Tried changing the starting point to my ISP's gateway, same effect.
And yes, most importantly, if I try to connect, having only 1 interface involved, which looks to the Internet, the connection is established.
As far as I understand, a problem in routing.
Maybe someone will be able to direct to the right idea, how to edit?

Answer 1

route print
I think it's worth looking here when the tunnel is turned off and on