ASDM Failure

[bowman]

I inherited an ASA with a new customer. I can connect using CLI, but would prefer ASDM.  I have tried to make the changes to the config and to me it looks like it should work, but I am missing something.  When I connect to https://XXX.XXX.183.202 , I get the normal "Continue to this website (Not recommended) like I do will all the rest of my ASA's.  But when I click on it, I get the old HTTP error 404. Can someone look at my config and let me know what I have missed?

Thanks in advance.

[bowman]

I am confused.  Can you explain to me what the command above does?  I thought factory-default put everything back to factory unless I specified a different internal network but it still wiped out all the other parts of the original config. Does the statement "reload save-config noconfirm" do something additional?

[davedoggydogg]

http server enable

http 192.168.100.0 255.255.255.0 inside

the command above enables asdm traffic on the inside port from the specified network subnet...just replace the numbers with your network subnet.

reference:

http://www.cisco.com/c/en/us/td/docs/security/asa/asa72/configuration/guide/conf_gd/mgaccess.html

[bowman]

I think if you look at the config file I sent, you will see that command is already in the running config. This is a screen shot of the config attached.

As I have stated, this is not my first ASA.  I have a bunch of these and all the others work as required.  I inherited this one and cannot determine what the previous admins did to block ASDM. Hoping someone else can see what I have missed.

[Marius Gunnerud]

The boot system commands is not he issue.  Basically when you have the two images statically configured it will try to boot the ASA in the order they are configured.  So if the 8.2 image fails to boot it will try the 7.2 image.  If you do not have any boot system commands configured then the ASA will try booting the ASA from images it finds in flash top to bottom.

forgive me if you have already answered the following question, but do you get the same result when accessing the ASDM via the inside interface from the local LAN?

What subnet is the following associated with:

http xxx.xxx.0.0 255.255.0.0 outside

Reason I as is because your SSH configuration is configured for 0.0.0.0 0.0.0.0.

--

Please remember to select a correct answer and rate helpful posts

[davedoggydogg]

he has this route with it 

route outside 0.0.0.0 0.0.0.0 XXX.XXX.183.201 1

so ssh would look for  XXX.XXX.183.201 coming from outside leading to "error 404 page not found"?? 

thats why i said try it from management port earlier posts