Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Been struggling with this for the past week. It used to work, and the PC im using to connect into the management port is not online, so no idea why its constantly saying Java is now suddenly outdated.OS : Windows 10 Enterprise LTSCASA Version : 9.8.2...
Final attempt that solved this for me in the interim (still have some unresolved SSL warnings) was as follows :-uninstall ASDM Launcher-uninstall Java current version-Install Java 7 Update 51 then hit up the ASDM management IP via Internet Explorer. ...
Thank you yes. Been able to resolve that by editing the shortcut of the ASDM launcher that's created as per previous posts but that creates the Unable to launch issue. I think its Java version related. Going to try and uninstall everything now and lo...
Appreciate it thanks. This is running in production however so its not a first time setup. After about a year I'm just not able to log into the ASA anymore via the ASDM and that's what's been causing the main issue
Yes, the PC has its own dedicated NIC into the management port of the FW. I've set that to 192.168.45.45 (or if I recall that was the default). I'm using 192.168.45.1 for the ASDM Launcher which worked in the past