Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

PIX 501 6.3 --> PIX 515E 7.2 Cisco VPN client Drops

Status
Not open for further replies.

sip240

Technical User
Aug 26, 2008
6
US
Hi,

We've got an external ISP network at our office used by contractors to access email, and other related issues - it's not part of the company network.

The external ISP provides a router, and we have two Cisco PIX 501's behind it providing DHCP addresses and NATing those users to the outside world. Everything works - but the 501's are no longer under support and need to be replaced.

So...We took the "pretty basic" 6.3 configs from the 501's and manually pasted them into the two new 515e's running 7.2. The 515e automatically converted an entry to the new 7.2 format and the PDM commands were modified to ASDM, but most of the config lines were taken directly into the 515e without complaint.

Everything seemed to be operating normally, people can hit the web, check email and stuff. However, a couple of contractors complained that when they went to VPN into their company VPN to sync outlook or other mundane things that need to be completed on their companies network, that their VPN connection would drop after 5-10 minutes. The Cisco VPN client connects, they can log in and get to their applications, email, whatever, then it just drops the connection with an error "Secure VPN Connection terminated locally by the client. Reason 412: The remote peer is no longer responding".

These are outbound requests... I.E. These new 515e's are not the VPN endpoints - these guys are just launching the Cisco VPN Client and trying to connect outbound.

We made no modifications to the config on the 515's, and when we drop the 501's back into the network, everything is fine...


Any ideas?
 
What do the logs say? Have you tried changing the MTU?


Brent
Systems Engineer / Consultant
CCNP, CCSP
 
Hi Brent,

I'm going to set the MTU to 1300 Tuesday and see if the problem continues. I'll post an update then.

Thanks for your reply.

Regards,

sip
 
This was apparently caused by something on the backbone between our location and the far end... The path that our provider took to connect our traffic between both locations (and outside of our control) was having issues.

What we can actually see of the traceroute is different now, and all is well.

The change of the MTU from 1500 to 1300 didn't seem to make any difference as the problem was still occurring.


Regards,

sip
 
Glad it's resolved.


Brent
Systems Engineer / Consultant
CCNP, CCSP
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top