Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Attention: The Cisco Support Community site will be in read only mode on Dec14, 2017 from 12:01am PST to 11:30am for standard maintenance. Sorry for the inconvenience.

New Member

remote VPN, SSL VPN stop working on ASA


Our ASA was working perfectly fine for remote VPN and SSL VPN but Not sure what happened it stop establishing remote VPN and SSL VPN sessions, we're working on ASA but now remote VPN, SSL VPN users can NOT logged in to the corporate network. I've checked every thing but I don't know what's missing. When I run show crypto isa sa command I get message no crypto isa, but when I compare the configs crypto is there. I've rebooted the ASA but no luck. User are able to logged in via secondary ASA.

1. Remote vpn try to initiate connection to

2. gateway ask for user name / password

3. after password no response and message shows on vpn client status bar establishing session ......................

4. show crypto doesn't shows any active/inactive session info

similar things are happening when I try to initiate a session via SSL VPN, it comes to authentication page, once I enter the login credential but does nothing.

ASA Ver 8.0.3

Please advice.


Syed Wajid.

Cisco Employee

Re: remote VPN, SSL VPN stop working on ASA


Do you have a pool or do you use a DHCP to give an ip to the clients?

Can you  attach the output of the debugs?


debug crypto isakmp 150

debug crypto ipsec 150

SSL (I guess that you are talking about anyconnect)

debug webvpn svc 255

Do you see any error in the client side?

Can you attached the logs of the clients?

New Member

Re: remote VPN, SSL VPN stop working on ASA

I haven't run debug yet, I;ll do it first thing monday morning. any idea why this is happening? we've not made any changes to ASA?

Any advice would really appreciated.



Cisco Employee

Re: remote VPN, SSL VPN stop working on ASA


8.0(3) is old code and there were many memory leaks in it.  The last 8.0(3) code was built over 2 years ago, and the first one was built in 2007.

You should consider either opening a tac case to address your specific issue, or if you don't want to do that, upgrading to a level of code that is more current and see if you still have the same issue.


CreatePlease to create content