07-31-2007 05:09 PM
I recently swapped out a DD WRT gateway/router with a PIX 501, and now I can not connect to the VPN at work (asa 5510) with the Cisco VPN client.
I was able to connect before no problem, the PIX connects to a SBC dsl modem. Bytes in is zero, however bytes out goes up. I am able to log in just fine, I get an IP address, and seem to be connected.
Any help would be much appriacheated, this problem is driving me nuts!
my config:
PIX Version 6.3(5)
interface ethernet0 10full
interface ethernet1 10full
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password yHJEhTyJX51EDD.A encrypted
passwd yHJEhTyJX51EDD.A encrypted
hostname pixfirewall
domain-name ciscopix.com
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 inbound permit tcp any any eq www
access-list inbound permit tcp any any eq 16080
access-list inbound permit tcp any any eq ssh
pager lines 24
mtu outside 1500
mtu inside 1500
ip address outside pppoe setroute
ip address inside 192.168.1.5 255.255.255.0
ip audit info action alarm
ip audit attack action alarm
ip local pool vpnips 192.168.1.200-192.168.1.210
pdm location 192.168.1.99 255.255.255.255 inside
pdm location 192.168.0.0 255.255.0.0 inside
pdm location 192.168.10.0 255.255.255.0 inside
pdm logging informational 100
pdm history enable
arp timeout 14400
global (outside) 1 interface
nat (inside) 1 0.0.0.0 0.0.0.0 0 0
static (inside,outside) tcp interface www 192.168.1.99 www netmask 255.255.255.255 0 0
static (inside,outside) tcp interface 16080 192.168.1.99 16080 netmask 255.255.255.255 0 0
static (inside,outside) tcp interface ssh 192.168.1.99 ssh netmask 255.255.255.255 0 0
access-group inbound in interface outside
router ospf 100
log-adj-changes
route inside 192.168.10.0 255.255.255.0 192.168.1.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 sip-disconnect 0:02:00 sip-invite 0:03:00
timeout uauth 0:05:00 absolute
aaa-server TACACS+ protocol tacacs+
aaa-server TACACS+ max-failed-attempts 3
aaa-server TACACS+ deadtime 10
aaa-server RADIUS protocol radius
aaa-server RADIUS max-failed-attempts 3
aaa-server RADIUS deadtime 10
aaa-server LOCAL protocol local
http server enable
http 192.168.1.0 255.255.255.0 inside
no snmp-server location
no snmp-server contact
snmp-server community public
snmp-server enable traps
floodguard enable
sysopt connection permit-ipsec
isakmp enable outside
telnet 192.168.0.0 255.255.0.0 inside
telnet timeout 5
ssh timeout 5
console timeout 0
vpdn group ISP request dialout pppoe
vpdn group ISP localname ****@sbcglobal.net
vpdn group ISP ppp authentication pap
vpdn group vpngroup client configuration address local vpnips
vpdn group vpngroup pptp echo 60
vpdn group vpngroup client authentication local
vpdn username ****@sbcglobal.net password *********
vpdn username *** password *********
dhcpd address 192.168.1.6-192.168.1.254 inside
dhcpd lease 3600
dhcpd ping_timeout 750
dhcpd auto_config outside
terminal width 80
Cryptochecksum:1bc8dbe33fafd1282a7dae392efe2864
: end
08-01-2007 02:44 AM
Hi
You could do either of 2 things.
1) Enable NAT-Traversal on your ASA
2) Add the following on your pix :
fixup protocol esp-ike
This allows one IPSEC connection to run through PAT.
HTH
Jon
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide