I had the same problem, I ended up putting a range of LAN IP addresses in the "SSL VPN Client" config page.
For example, my internal LAN is 192.168.24.x
Under teh SSL VPN Client config page I put in 192.168.24.75 for address range begin and 192.168.24.100 for address range end. Then I made sure my DHCP server on the LAN didn't give out that range.
I had it initially setup to use a different range (assuming that's how it is supposed to work), but couldn't get it to route to the internal LAN. I didn't find any firewall settings or route settings that helped that. So, I changed the address range.
Yep that's what I did. I think if you toy around with the SA, it will eventually come up with an error message stating the SSL range can not be within the local ip scheme. Also if your using firmware 1.1.65 or older, setting the SSL range within the local scheme will eventually crash the local DHCP server. I'm running three different ip schemes, over three vlans.
The first time I tried it, I did get an error telling me that the range couldn't be within the LAN range. But, somehow, after another attempt, it took it. But, I'm sure this is a "hack" that will bite me at some point.
It'd be nice to know the correct solution, if the Cisco guys happen to be trolling this discussion board.
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...