03-02-2016 11:50 AM
Be kind - I am a novice at network configuration.
I am using the ASA 5505 at a remote site. I am able to use the external VPN IP address for the site to launch ASDM from outside the LAN as well as use the Cisco AnyConnect VPN client.
However, when inside the LAN, I cannot access the internal IP address of the ASA using ASDM or using the URL https://192.168.x.x/admin. I have been successful in doing so in the past so this is unusual. I just updated the ASA software to version 8.2.5(59), but no other known changes have been made.
It may not be related, but I also cannot ping the internal ASA IP address despite using the command icmp permit 192.168.x.0 255.255.255.0 inside
Any ideas what might be causing this?
03-02-2016 04:26 PM
You could be missing the command
http 192.168.x.0 255.255.255.0 inside
check what is configured by issuing the command
show run http
--
Please remember to select a correct answer and rate helpful posts
03-02-2016 08:34 PM
Hello!
On this case I would recommend the same as Marius, get the "http 0 0 inside" for testing purposes after wards, allow the individual addresses that should be allowed to access ASDM, also make sure you are getting ARP entries on the inside, are you able to ping the far end device from the ASA?? is the ASA able to reach the next hop IP address?? try SSH as well and telnet, (SSH 0 0 inside / Telnet 0 0 inside), share the configuration with us, if you keep having problems!
If this helped rate this answer and mark it as correct!
Thanks,
David Castro,
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide