>>I can't offer help with the PDM it was very bad IMHO
It looks bad now cause we are all used to ASDM <grin>
Yep it will be split tunneling - you dont say if the PIX is version 6(or ealier) or version 7 (or later)
As posted above if your version 7 then its set with an ACL and within the VPN group policy
**********For Version 7 PIX and ASA firewalls
group-policy VPNPolicy internal
group-policy VPNPolicy attributes
split-tunnel-policy tunnelspecified
split-tunnel-network-list value Split_Tunnel
access-list SSL_Split_Tunnel standard permit 192.1.0.0 255.255.0.0
where 192.1.0.0 / 255.255.0.0 is the INTERNAL network
***********For version 6 PIX firewalls
access-list RemoteVPN_splitTunnelAcl permit ip 192.1.0.0 255.255.0.0 any
vpngroup RemoteVPN split-tunnel RemoteVPN_splitTunnelAcl
wh





by: 3nerdsPosted on 2009-07-30 at 06:25:51ID: 24979522
You are probably correct that it is a split tunnel problem. You are going to need to add an acl telling it what traffic needs to be encrypted and when is ok to go to the internet. You will then need to add this acl to the VPN configuration.
Something like this:
access-list split-tunnel-acl permit ip x.x.x.x 255.255.255.0 y.y.y.y 255.250.255.0--> X is you internal subnet that you are gaining access to. Y is the subnet of your vpnpool
vpngroup vpn-group-name split-tunnel split-tunnel-acl
I can't offer help with the PDM it was very bad IMHO and to unstable to trust to use reliably.
Regards,
3nerds