06-30-2014 05:39 AM - edited 03-07-2019 07:52 PM
We have a site-site vpn created between our ASA and our cisco router.
When on the cli of the router you can only ping internal remote networks by using ping x.x.x.x source x.x.x.x
The problem this is causing is that Websence and Waas express that run on the router cannot communicate with the remote end.
06-30-2014 06:58 AM
You need to advertise the subnet that for Websence and Waas on to the remote vpn device, so they can reach these devices.
06-30-2014 08:37 AM
I dont understand why I would need to advertise the remote subnet when the vpn does this already. If I connect a laptop to the router, i can successfully contact the remote waas and websence devices. From the cli i cant.
06-30-2014 09:09 AM
When you connect your laptop, you probably have a different source IP address then when you try from the cli.
What is the laptop IP address and what is the outgoing interface IP on the router?
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide