Check if the inside clients have their default g/w set to the inside of the PIX, or if not set to this and it is set to a router, check if the router has a
def route pointing to the internal ip of the PIX, or at least have a static route to the ip pool you assign to the client, via the pix inside interface.
Possible issue 1, is that you have an network card on the PC that has the same address range as your ip address of the vpn client pool. Do an ipconfig /release all, then reconnect if you have this issue.
Another one, is that your client is behind a device doing PAT/NAT, in its current code, the PIX doesn't support IPSec thru nat, so you have to bypass the NAT
My PC's are set to use a router on the inside as their default gateway. I have static routes on the router to send inside interface traffic (172.16.1.x) to the PIX inside interface (172.16.1.254) and inside interface traffice (172.16.2.x) to the PIX inside interface (172.16.1.254. My VPN client is not behind a NAT/PAT device as I have connected my PC to the outside network of the PIX for testing.
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...