Can't ping anything when IPSEC VPN'ed in through SA520
I'm currently working with a setup where the SA520 is the outward facing device, performing NAT with a subnet of 192.168.1.x, with a UC540's WAN port connected to one of the LAN ports on the SA520. The UC540 is also performing NAT with a subnet of 192.168.10.x. THere is a SF300-24P plugged in to the expansion port on the UC540. While plugged in directly to any of the devices, I have static routes set so that I can ping any of the devices on these subnets. This has been tested to work.
I am able to IPSEC VPN in to SA520, with the VPN pool on the 192.168.12.x subnet. Once connected I can NOT ping any device on any subnet, nor any websites. Do I need to add a static route or VPN policy somewhere to allow connections from the 192.168.12.x subnet to the other subnets?
Reboot and Factory Default Reset on ISA500 Series Integrated Security Appliances
Reboot or restart of the network device is made when certain changes in the settings need reboot or if the device is frozen. The configuration...
WAN Quality of Service (QoS) Policy Profiles Settings on ISA500 Series Integrated Security Appliances
Wide Area Network (WAN) Quality of Service (QoS) policy profiles manage traffic through classed-based profiles. These pro...
Cisco QuickVPN Installation Tips for Windows Operating Systems
For a video showing installation tips on Quick VPN, visit http://youtu.be/hHu2z6A78N8
Cisco QuickVPN is a free software designed for remote access to a ne...