I believe I'm using the current version of Java because I had to install it on the PC that I'm using as the admin console. I'll see what I can do about down-grading to an earlier version of Java and see what happens.
Main Topics
Browse All TopicsI can't connect to my ASA 5510 using the ASDM Launcher or by connecting to https://192.168.1.1. I have little experience working with Cisco appliances so I was relying heavily on the ASDM Launcher to work through the initial configuration. I'm waiting on approval for a training class.
Ideally I would like to reset/restore/recover the ASA 5510 to its factory out-of-the-box settings. I was able to connect using ASDM Launcher at one time, but I must have mangled the settings somehow which is preventing me from connecting through ASDM.
I've done extensive web searching and found many articles that suggest using the configure factory-default command, which I have done, but still can't connect using ASDM Launcher.
I CAN connect and issue commands from the CLI using the blue Console cable and HyperTerminal, but I lack the skills to troubleshoot and identify the problem from the CLI.
Symptoms:
When I attempt to connect using the ASDM Launcher or https://192.168.1.1 the messages "Contacting the device," "Loading cached software" and "Software update completed" are visible, but I just receive an hour-glass that never goes away and I can't get past the logon screen.
When I try the "Run in Demo Mode" option I receive the following error: "ASDM did not get a response from the ASA in the last 60 seconds. Please check the configuration and your connection and then try again by clicking Refresh."
While in Demo Mode there are two devices (192.168.1.1 & localhost:55000) in the Device List on the left, but I receive the error above when I try to connect to them.
ciscoasa# show running-config
: Saved
:
ASA Version 7.0(7)
!
hostname ciscoasa
domain-name default.domain.invalid
enable password 8Ry2YjIyt7RRXU24 encrypted
names
dns-guard
!
interface Ethernet0/0
shutdown
no nameif
no security-level
no ip address
!
interface Ethernet0/1
shutdown
no nameif
no security-level
no ip address
!
interface Ethernet0/2
shutdown
no nameif
no security-level
no ip address
!
interface Management0/0
nameif management
security-level 100
ip address 192.168.1.1 255.255.255.0
management-only
!
passwd 2KFQnbNIdI.2KYOU encrypted
ftp mode passive
pager lines 24
logging asdm informational
mtu management 1500
asdm image disk0:/asdm-507.bin
no asdm history enable
arp timeout 14400
timeout xlate 3:00:00
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 icmp 0:00:02
timeout sunrpc 0:10:00 h323 0:05:00 h225 1:00:00 mgcp 0:05:00
timeout mgcp-pat 0:05:00 sip 0:30:00 sip_media 0:02:00
timeout uauth 0:05:00 absolute
http server enable
http 192.168.1.0 255.255.255.0 management
no snmp-server location
no snmp-server contact
snmp-server enable traps snmp authentication linkup linkdown coldstart
telnet timeout 5
ssh timeout 5
console timeout 0
dhcpd address 192.168.1.2-192.168.1.254 management
dhcpd lease 3600
dhcpd ping_timeout 50
dhcpd enable management
Cryptochecksum:bad2262d213
: end
ciscoasa#
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
I uninstalled Java 6 Update 13 and installed Java 6 Update 7, but unfortunately the problem still persists. As I mentioned in my OP, ASDM will launch in Demo Mode so maybe Java isn't the culprit?
I receive an error when I attempt to connect to the ASA. When I try to connect I receive a a "Device Err" window that says, "Could not open device 192.168.1.1. However I can ping that IP.
Any other thoughts? Anyone?
oalva,
You were right after all!
After the Java downgrade, I tried to launch ASDM Launcher in "Demo Mode" again and I should have tried to connect in non-Demo Mode as well. So I tried that and I was able to connect and was able to run through the Startup Wizard. Near as I can tell, it's working the way its supposed to.
I downgraded from Java 6 Update 13 to Java 6 Update 7, but a new version between 7 and 12 may have worked ... it's just the one that I selected.
I'm going to poke around in ASDM for a little while then I'll be back to Accept your Solution.
Thanks!
Business Accounts
Answer for Membership
by: oalvaPosted on 2009-03-26 at 10:45:00ID: 23993125
what version of java are you running? I had the same problem when i upgraded my java it acts like it will launch but hangs