ASDM is unable to contact the ASA

bsisco · ‎03-20-2007

I have a LAN connection to an ASA here in my office, but I'm constantly running into the message in the subject field of this post. When things get really bad, some of my changes make it into the running config while others just end up in the bit bucket.

Anyone else experiencing this issue? Anyone have any suggestions as to a resolution? I can provide just about any information necessary. I've started trending traffic on my PC's interface to provide some background.

TIA

dentt · ‎03-20-2007

I assume that you have the http server enabled, and you have access lists configured for your management stations to connect to the ASA?

Could you post a show run http?

What is the IP of the station you are trying to use the ASDM from?

TD

bsisco · ‎03-20-2007

I apologize for the lack of information - I realized after I posted I did not include versions or config info.

ASDM Launcher v. 1.4(9)

ASDM 5.2(1)

ASA 7.2(1)

http http server enable

http 192.168.169.0 255.255.255.0 Inside_Trunk

My desktop is located on the .169 network which is directly connected to the Inside_Trunk interface.

Problem typically occurs when first loading the ASDM and occasionally while it's up and running on my desktop. Responses from the ASA time out. This has only been an issue when connecting to the ASA (using ASDM) thorugh the Inside interface. The issue did not exist when I was configuring the ASA originally using the management port.

I'm currently replacing the switches in our network and will soon have access to the management network from my desktop but until then it is imperative that I get the reliability I need out of this solution.

dentt · ‎03-20-2007

I would try downloading the latest ASDM interim release and see if that fixes the issue.

I believe the latest ASDM is 522-58

abinjola · ‎03-20-2007

ok lets start from the scratch :-

1)Can you ping the inside_trunk interface from the PC

2)Can you open a browser screen and then type https://ip address of Inside_Trunk , what error message do you get ?

3)Can you turn on the logs and let me know what log message are you noticing in the logs