Today we had a very disturbing failure.  We have a fully functional VPN on our ASA 5510 adaptive security device running 8.2(5).  I was setting up a new user on a Windows 7 Professional 64 bit machine using FireFox instead of Internet Explorer. The initial connection worked fine but the download of the client failed.  I clicked on the link provided to manually download the client and the Cisco VPN client appeared to download and install properly.  However, when I attempted to open the VPN after the client install it again said that the automatic download of the client failed and it offered the link to download the client again, which I did with exactly the same result. I thought that perhaps the problem was with FireFox so I opened Internet Explorer and entered the url for the VPN.  After the user-id and password were entered (and validated) I received the same error about the client download failure and I selected the link to manually download just like I did the other 3 times in FireFox.  This time it actually looked like it was working as I received the certificate error about AnyConnect (which I normally get) however, the login screen remained on the page after I clicked on the certificate error to continue.   The PC appeared to hang so I ended the VPN session and then attempted to reestablish the connection.  This time when I entered the user-id and password it came back saying "Invalid Logon".  I tried again and received the same result.  I tried a different user but no joy... same result... invalid login.  I went to a different PC; one that had been working fine only a few minutes earlier, and I received the same invalid login message no matter which user-id and password I entered.  Something had happened that was blocking all users from connecting to the VPN. I didn't want to believe that attempting to connect to the VPN using FireFox on a Windows 7 64 bit machine could somehow bring my Cisco VPN down but I was out of options... so I rebooted the ASA and much to my disappoinment the reboot fully restored the VPN service.  Now if this were a $75 dollar LinkSys Router instead of a several thousand dollar security device I would just shake it off, but how can it be that a failed connection attempt could bring a Cisco ASA 5510 VPN to its knees?  I thought that maybe I had exceeded the license max for SSL VPN connections... I think its 2... but if that was the cause then why wouldn't the message indicate such instead of just saying "invalid login".  Also, there were no other open connectionsat the time, unless all the failed downlaod attempts counted as active sessions.  I also had already checked in ASDM and no active VPN sessions were listed. Any guidence anyone can provide would be greatly appreciated. Ed ... View more

Up to now we've been making configuration changes to a production unit.  Not such a good idea. We just bought a second ASA5510 to be used as a test unit but we're having trouble getting past the install of ASDM.  We used the console interface to reset the unit to factory settings and then we followed the Cisco Getting started guide.  We are connected to the management port using a crossover cable (per the instructions) and we opened a web browser to the following url (again... per the instructions) https://192.168.1.1/admin   As expected we receive a certificate warning that we are instructed to ignore.  We click on continue and we receive the dreaded "Unable to Launch Device Manager from 192.168.1.1" and the only option is to hit OK. I realize its not much to go on, but that's all we've got.  We can connect using the Console port and execute commands but at this point we would prefer using the ASDM.  I'm assuming the ASDM image is either not on the disk in the ASA of if it is there is something wrong with it. Yes we enable HTTP on the management port. Any ideas/suggestions would be greatly appreciated. Ed ... View more