topic You should also have - in Network Security

Accessing ASDM via Inside interface thru site-to-site vpn

chanccmtech — Tue, 12 Mar 2019 09:13:50 GMT

Good Day All,

I had a searched thru the forums looking for a very specific answer, however I can find similar topics regarding to it, but still unable to solve the issue I am currently facing.

Looking at the above diagram, user from 192.10.10.0/24 segment wants to access ASDM of firewall 192.168.51.1 via inside interface. User from that segment is able to communicate each other without any issues, but unable to access ASDM via inside interface. What else in my configuration could I still be missing. Let's just assume I have my ACL in place already.

I have enabled the following:

management-access inside

http server enable

http 0 0 inside

http 0 0 mgmt

nat (inside,outside) source static NETWORK_OBJ_192.168.51.0_24 NETWORK_OBJ_192.168.51.0_24 destination static NETWORK_OBJ_192.10.10.0_24 NETWORK_OBJ_192.10.10.0_24 no-proxy-arp route-lookup

What else could I still be missing? Pointers would be great.

You should also have -

ajay chauhan — Tue, 18 Apr 2017 08:55:52 GMT

You should also have -

http remote_subnet outside

This article may help.

http://www.cisco.com/c/en/us/support/docs/security/adaptive-security-device-manager/118092-configure-asa-00.html

Ajay

I have gone through that

chanccmtech — Wed, 19 Apr 2017 04:42:36 GMT

I have gone through that article before. Doesn't the command:

http 0 0 inside - covers any IP accessing inside interface?

Although by allow "http remote_subnet outside" that is pointing towards the outside interface rather than the inside interface?

Remote subnet is not local

ajay chauhan — Thu, 20 Apr 2017 04:41:11 GMT

Remote subnet is not local hence you should put that on outside. You can simply try that.

Ajay