Link to home
Start Free TrialLog in
Avatar of Don Coleman
Don ColemanFlag for United States of America

asked on

Cisco VPN Client - Secure VPN connection terminated locally by the client, Reason 412 Peer is no longer responding.

I had initally setup the PIX 501 for several users to gain access to the office network their home desktops. It worked fine when I tested each user by connecting and logging in to the PIX.  That being completed I proceeded to setup the Small Business Server remote VPN connection for mobile users with laptops.  I am now getting the above error so I can only assume that it is one of the changes I made to the PIX for the SBS VPN that is now causing my Cisco VPN Client to fail but I have been unable to determine what it causing the problem.   I have attached the PIX configuration for all to review.  Thanks for the assistance.  

PIX Version 6.3(5)
interface ethernet0 auto
interface ethernet1 100full
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password Q3Dtr5H78W34DD encrypted
passwd D4dskdkkrRFDE55QdE 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 pptp 1723
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 inside_outbound_nat0_acl permit ip any 192.168.70.96 255.255.255.240
access-list outside_cryptomap_dyn_20 permit ip any 192.168.70.96 255.255.255.240
access-list BWPVPN_splitTunnelAcl permit ip 192.168.13.0 255.255.255.0 any
access-list outside_access_in permit tcp any host XX.XXX.XX.238 eq pptp
access-list outside_access_in permit gre any host XX.XXX.XX.238
access-list outside_access_in permit tcp any host XX.XXX.XX.238 eq https
pager lines 24
mtu outside 1500
mtu inside 1500
ip address outside pppoe setroute
ip address inside 192.168.13.1 255.255.255.0
ip audit info action alarm
ip audit attack action alarm
ip local pool BWPPool 192.168.70.100-192.168.70.110
pdm location 192.168.1.0 255.255.255.0 inside
pdm location 192.168.13.0 255.255.255.0 inside
pdm location 192.168.2.0 255.255.255.0 inside
pdm location 192.168.13.100 255.255.255.255 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_access_in in interface outside
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.2.0 255.255.255.0 inside
http 192.168.1.0 255.255.255.0 inside
http 192.168.13.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 match address outside_cryptomap_dyn_20
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 BWPVPN address-pool BWPPool
vpngroup BWPVPN split-tunnel BWPVPN_splitTunnelAcl
vpngroup BWPVPN idle-time 1800
vpngroup BWPVPN password ********
telnet 192.168.1.0 255.255.255.0 inside
telnet 192.168.2.0 255.255.255.0 inside
telnet 192.168.13.0 255.255.255.0 inside
telnet timeout 5
ssh timeout 5
console timeout 0
vpdn group pppoe_group request dialout pppoe
vpdn group pppoe_group localname Potclienttest@sbcglobal.net
vpdn group pppoe_group ppp authentication pap
vpdn username Potclienttest@sbcglobal.net password **********
dhcpd lease 3600
dhcpd ping_timeout 750
dhcpd auto_config outside
username Bclown password 26ei5AkptVHXuWMq encrypted privilege 5
username gbush password 61SjTmqqKxmFUYqz encrypted privilege 15
username jsmith password E2mfE7ppBGu46vJL encrypted privilege 5
username jplumber password PYsWCZrguB0XZfQU encrypted privilege 5
terminal width 80
Avatar of Slawomir Malinowski
Slawomir Malinowski
Flag of United Kingdom of Great Britain and Northern Ireland image

It could be an unstable client internet connection or MTU issue.
Please check your MTU size (try with 1300 or the smallest possible) - application is located in the same plasce where you have you Cisco client.

good luck
Avatar of IanTM
IanTM

just to clarify... does the pix always have the same external ip address?

this line...

    ip address outside pppoe setroute

could indicate that it might not.
Avatar of Don Coleman

ASKER

Yes.  It is a static IP.  I get the same IP every time.  
Amdil, where do I change the MTU size?  I have a suspiscion that the DSL broadband connection on the server side is too slow.
ASKER CERTIFIED SOLUTION
Avatar of IanTM
IanTM

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Not all of your suggestions solved the problem.  The primary being that I was point ALL traffic to the server and I should have been pointing only the PPTP.  Thanks.
I'm glad you're up and running.

However, I've no idea what you're referring to...

"Not all of your suggestions solved the problem. The primary being that I was point ALL traffic to the server and I should have been pointing only the PPTP. Thanks."
...as in your original config you had no inbound static routes therefore no traffic would have ever got to your sbs server.

My config only points PPTP as you required.

static (inside,outside) tcp interface pptp xx.xx.xx.xx pptp netmask 255.255.255.255 0 0


My error.  I had added a static route incorrectly but did not list it in the configuration.