PIX VPN Client, no default gateway, can not connet to internal hosts

[xdeq]

Hi,
PIX 506E and Cisco VPN Client 4.0.3C
I can establish VPN session, enter user name and password.
Get the DNS, WINS servers. but the default gateway is empty.
I can not get to any resources in internal network.
This is only on one laptop. Other machines work fine.

any idea?

removed Sygate Personal Firewall
tried couple versions of the Cisco VPN client.
I also have Checkpoint Client on this machine.



D:\Documents and Settings\bob>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : bobmobile
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : ccc

Ethernet adapter LAN:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network Connection
Physical Address. . . . . . . . . : 00-00-39-DB-78-2E
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.249.71
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.249.1
DHCP Server . . . . . . . . . . . : 192.168.249.1
DNS Servers . . . . . . . . . . . : 206.80.192.1
Lease Obtained. . . . . . . . . . : Tuesday, October 19, 2004 4:09:27 PM
Lease Expires . . . . . . . . . . : Tuesday, October 19, 2004 5:09:27 PM

Ethernet adapter CISCO VPN:

Connection-specific DNS Suffix . : ccc
Description . . . . . . . . . . . : Cisco Systems VPN Adapter
Physical Address. . . . . . . . . : 00-05-9A-3C-78-00
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 172.17.2.2
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 192.9.200.50
192.9.200.53
Primary WINS Server . . . . . . . : 192.9.200.50
Secondary WINS Server . . . . . . : 192.9.200.53


D:\Documents and Settings\bob>ssh2 60.60.60.14 -l robertk
: Saved
: Written by enable_15 at 07:42:54.355 UTC Mon Oct 18 2004
PIX Version 6.3(3)
interface ethernet0 auto
interface ethernet1 auto
nameif ethernet0 outside security0
nameif ethernet1 inside security100
hostname cccpix
domain-name ccc.local
fixup protocol dns maximum-length 512
fixup protocol ftp 21
fixup protocol h323 h225 1720
fixup protocol h323 ras 1718-1719
fixup protocol http 80
fixup protocol rsh 514
fixup protocol rtsp 554
fixup protocol sip 5060
fixup protocol sip udp 5060
fixup protocol skinny 2000
fixup protocol smtp 25
fixup protocol sqlnet 1521
fixup protocol tftp 69
names
access-list icmp permit icmp any any echo-reply
access-list icmp permit icmp any any source-quench
access-list icmp permit icmp any any unreachable
access-list icmp permit icmp any any time-exceeded
access-list outside_acl_inbound permit icmp any any
access-list inside_outbound_nat0_acl permit ip 192.9.200.0 255.255.255.0 172.17.2.0 255.255.255.0
access-list inside_outbound_nat0_acl permit ip 192.9.201.0 255.255.255.0 172.17.2.0 255.255.255.0
access-list outside_cryptomap_dyn_20 permit ip any 172.17.2.0 255.255.255.0
access-list OUTSIDE_IN permit icmp any any
access-list OUTSIDE_IN deny ip any any
pager lines 24
logging on
logging buffered debugging
icmp permit any outside
mtu outside 1500
mtu inside 1500
ip address outside pppoe setroute
ip address inside 192.9.200.254 255.255.255.0
ip audit info action alarm
ip audit attack action alarm
ip local pool VPNpool 172.17.2.1-172.17.2.254
pdm location 192.9.201.0 255.255.255.0 inside
pdm logging informational 100
pdm history enable
arp timeout 14400
global (outside) 1 interface
nat (inside) 0 access-list inside_outbound_nat0_acl
nat (inside) 1 0.0.0.0 0.0.0.0 0 0
access-group OUTSIDE_IN in interface outside
route inside 192.9.201.0 255.255.255.0 192.9.200.1 1
timeout xlate 0:05:00
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 rpc 0:10:00 h225 1:00:00
timeout h323 0:05:00 mgcp 0:05:00 sip 0:30:00 sip_media 0:02:00
timeout uauth 0:05:00 absolute
aaa-server TACACS+ protocol tacacs+
aaa-server RADIUS protocol radius
aaa-server LOCAL protocol local
aaa authentication ssh console LOCAL
http server enable
http 192.9.200.0 255.255.255.0 inside
no snmp-server location
no snmp-server contact
snmp-server community public
no snmp-server enable traps
floodguard enable
sysopt connection permit-ipsec
crypto ipsec transform-set ESP-3DES-MD5 esp-3des esp-md5-hmac
crypto dynamic-map outside_dyn_map 20 set transform-set ESP-3DES-MD5
crypto map outside_map 65535 ipsec-isakmp dynamic outside_dyn_map
crypto map outside_map client authentication LOCAL
crypto map outside_map interface outside
isakmp enable outside
isakmp policy 20 authentication pre-share
isakmp policy 20 encryption 3des
isakmp policy 20 hash md5
isakmp policy 20 group 2
isakmp policy 20 lifetime 86400
vpngroup cccgroup address-pool VPNpool
vpngroup cccgroup dns-server 192.9.200.50 192.9.200.53
vpngroup cccgroup wins-server 192.9.200.50 192.9.200.53
vpngroup cccgroup default-domain ccc
vpngroup cccgroup split-tunnel inside_outbound_nat0_acl
vpngroup cccgroup idle-time 1800
vpngroup cccgroup password ********
telnet 0.0.0.0 0.0.0.0 inside
telnet timeout 5
ssh 0.0.0.0 0.0.0.0 outside
ssh 0.0.0.0 0.0.0.0 inside
ssh timeout 60
console timeout 0
vpdn group PPPOEGROUP request dialout pppoe
vpdn group PPPOEGROUP localname ccc_chicago@static_ameritech.net
vpdn group PPPOEGROUP ppp authentication pap
vpdn username ccc_chicago@static_ameritech.net password ********
dhcpd auto_config outside
username bob password faVz11234/bfY2 encrypted privilege 2
terminal width 80

 

[mbilgrav]

your config looks ok, made by PDM
try enable Nat-traversal
isakmp nat-t

HTH
Martin

 

[xdeq]

Thanks
This is not about the configuration on the PIX or the laptop.
I am able to connect from another location.
Same laptop connected to another network and can not ping, connect, nothing.

looks lie this is the device beetween us.
I was able to connect and authenticate.
In the network monitor I can comminication (sent, received packets) but in the VPN client statistics Bytes Received = 0.

At the same time I have CheckPoint FW client and can connect to another site over IPSEC.

How can I investigate what is wrong?