Access ASDM ASA on the external Interface

We have three ASA5510s, each configured for ssh and http access to the Cel outside.  One of them has aaa users/passwords defined for both ssh and http.  I can access the ASA configured for aaa of the designated host allowed in the external interface normally using credentials of the aaa.  When I try to access one of the other two, they will refuse the enable login password.  The configured aaa ASA is version 8.2 with ASDM 6.21.  The other two are the two ASA version 7.0 with ASDM 5.07.  The ASA requires aaa is configured for https access?  How can I make these other two accept the ASDM login?  Thank you!

If you do not have aaa then configured for ASSISTANT Deputy Ministers, you must use empty username and password enable.

Also, you can use the "aaa authenticate http LOCAL console" and use a user/pwd to a private 15 user name to connect to the ASDM.

To resolve what is a failure you can activate "debug http" and "debug aaa" on the SAA to see the reasons for which the user is rejected.

I hope it helps.

PK

Tags: Cisco Security

Similar Questions

  • ASDM does not work in the external interface

    Hello

    I'm new to ASA. I have ASA 5510 and strives to enable ASDM access through the external interface. but is not working for me... not. I set up a public ip address on the external interface and activated the ssh and asdm. SSH works but asdm does not work. This is a test environment, so I have not yet set up an ACL.

    VPN-TEST # show version

    Cisco Adaptive Security Appliance Version 8.2 software (1)

    Version 6.2 Device Manager (1)

    Updated Wednesday, 5 May 09 22:45 by manufacturers

    System image file is "disk0: / asa821 - k8.bin.

    The configuration file to the startup was "startup-config '.

    VPN TEST up to 4 hours and 33 minutes

    Material: ASA5510, 1024 MB RAM, Pentium 4 Celeron 1600 MHz processor

    Internal ATA Compact Flash, 256 MB

    BIOS Flash Firmware Hub @ 0xffe00000, 1024 KB

    Hardware encryption device: edge Cisco ASA - 55 x 0 Accelerator (revision 0 x 0)

    Start firmware: CN1000-MC-BOOT - 2.00

    SSL/IKE firmware: CNLite-MC-Smls-PLUS - 2.03

    Microcode IPSec:-CNlite-MC-IPSECm-HAND - 2.04

    0: Ext: Ethernet0/0: the address is d0d0.fd1d.8758, irq 9

    1: Ext: Ethernet0/1: the address is d0d0.fd1d.8759, irq 9

    2: Ext: Ethernet0/2: the address is d0d0.fd1d.875a, irq 9

    3: Ext: Ethernet0/3: the address is d0d0.fd1d.875b, irq 9

    4: Ext: Management0/0: the address is d0d0.fd1d.8757, irq 11

    5: Int: not used: irq 11

    6: Int: not used: irq 5

    The devices allowed for this platform:

    The maximum physical Interfaces: unlimited

    VLAN maximum: 50

    Internal hosts: unlimited

    Failover: disabled

    VPN - A: enabled

    VPN-3DES-AES: enabled

    Security contexts: 0

    GTP/GPRS: disabled

    SSL VPN peers: 2

    The VPN peers total: 250

    Sharing license: disabled

    AnyConnect for Mobile: disabled

    AnyConnect for Linksys phone: disabled

    AnyConnect Essentials: disabled

    Assessment of Advanced endpoint: disabled

    Proxy sessions for the UC phone: 2

    Total number of Sessions of Proxy UC: 2

    Botnet traffic filter: disabled

    This platform includes a basic license.

    VPN-TEST # http see race

    Enable http server

    http 0.0.0.0 0.0.0.0 outdoors

    VPN-TEST # display running asdm

    ASDM image disk0: / asdm - 621.bin

    enable ASDM history

    Could someone please help me know what Miss me?

    Kind regards

    Praveen

    That's it, please add any combination of encryption by using the command "ssl encryption" algorithms, please add them in one line next to each other, and you can use '? ' to check available combinations.

    Kind regards

    Mohammad

  • VPN client and ssh to the external interface of the ASA

    Hello world

    I was testing clientless ssl in my lab at home.

    When you're connected via vpn without customer, I am able to ssh ASA outside interface, but when I use ssl vpn only I can't ssh to the external interface of the ASA.

    Need to figure out how I can ssh to the external interface of the ASA using clientless ssl vpn?

    Concerning

    MAhesh

    Mahesh,

    When you are on clientless SSL VPN to your customer is not limited routes of the Internet, isn't being NATted etc. If ASA is set to allow ssh from outside, then the VPN SSL without client user is no different from any other.

    A the user SSL VPN full tunnel can have any or all of these factors at play. One of them can cause the impossibility to access the ASA outside interface via ssh. I see the configuration to tell you which one (or more) is to blame.

  • Network for access to the external interface inside

    Hey,.

    I have an ASA5520 7.2 (1) I have a few probs with - which is something I struggle with that.

    I'm trying to hit a website of a host on the inside network that is actually hosted internally, but decides the static NAT would focus on the external interface of the firewall.

    Now I can see the TCP built, translation occurring at a port on the external interface, this port high dialogue to one of the static electricity would be addresses on the external interface, then that's all. There are no more entries in my journal in regards to the connection and I get not syn on the internal web server is so the connection is not back in.

    IP address outside 222.x.x.9 255.255.255.248

    IP address inside 192.168.87.1 255.255.255.0

    Static NAT to Web servers: -.

    public static 222.x.x.10 (Interior, exterior) 192.168.87.5

    access lists access... :-

    list of allowed inbound tcp extended access any host 192.168.87.5 eq http

    Access-group interface incoming outside in

    Everything works fine when creating a global internet address - just not when address from inside and dynamic PAT is performed to the original address.

    Here's a capture session by using the following access to capture list inside and outside interfaces simultaneously

    permit for line of web access-list 1 scope ip host 222.222.222.10 all

    web access-list extended 2 line ip allow any host 222.222.222.10

    on the INSIDE interface (nothing is connected to the outside) (ip addresses have been replaced by nonsense) - but address 222 is would take into account the interface static and the other is on the internal network.

    316: 19:14:02.900206 192.168.87.10.2275 > 222.222.222.10.80: S 2029971541:2029971541 (0) win 64512

    317: 19:14:05.973185 192.168.87.10.2275 > 222.222.222.10.80: S 2029971541:2029971541 (0) win 64512

    192.168.87.10 is my client is trying to connect

    Someone of any witch hunt, which is stop this function work?

    All networks are directly attached and there is no route summary ancestral anywhere.

    I hope you guys can help!

    Concerning

    Paul.

    To my knowledge the ASA supports only hairpining on a VPN tunnel. The security apparatus does not allow traffic that is sent to an interface to go back in the direction of what she received.

  • VPN; list of access on the external interface allowing encrypted traffic

    Hi, I have a question about the access list on the external interface of a router 836. We have several routers on our clients site, some are lan2lan, some are client2router vpn.

    My question is; Why should I explicitly put the ip addresses of the client vpn or tunnel lan to the access list. Because the encrypted traffic to already allowing ESPs & isakmp.

    The access list is set to the outgoing interface with: ip access-group 102 to

    Note access-list 102 incoming Internet via ATM0.1

    Note access-list 102 permit IP VPN range

    access-list 102 permit ip 192.123.32.0 0.0.0.255 192.123.33.0 0.0.0.255

    access-list 102 permit ip 14.1.1.0 0.0.0.255 any

    access-list 102 permit esp a whole

    Note access-list 102 Open VPN Ports and other

    access-list 102 permit udp any host x.x.x.x eq isakmp newspaper

    I have to explicitly allow 192.123.32.0 (range of lan on the other side) & 14.1.1.0 (range of vpn client) because if I'm not I won't be able to reach the network.

    The vpn connection is not the problem, all traffic going through it.

    As far as I know, allowing ESPs & isakmp should be sufficient.

    Can anyone clarify this for me please?

    TNX

    Sebastian

    This has been previously answered on this forum. See http://forums.cisco.com/eforum/servlet/NetProf?page=netprof&CommCmd=MB%3Fcmd%3Dpass_through%26location%3Doutline%40%5E1%40.ee9f970/0#selected_message for more details.

  • SSH to the external interface

    How to configure ssh on the external interface of the asa? I have defined an applied, external interface access list, but it did not work for some reason any

    Here is a list of access

    interface GigabitEthernet0/1

    nameif outside

    security-level 0

    IP 10.254.17.9 255.255.255.248

    !

    interface GigabitEthernet0/2

    No nameif

    security-level 100

    no ip address

    !

    interface GigabitEthernet0/3

    EIGRP 2008 description

    nameif eigrp

    security-level 100

    IP 10.40.50.65 255.255.255.252

    !

    interface Management0/0

    nameif management

    security-level 100

    IP 192.168.251.1 255.255.255.0

    management only

    !

    boot system Disk0: / asa821 - k8.bin

    passive FTP mode

    access-list 110 scope ip allow a whole

    NAT allowed ip extended access list a whole

    allow_ping list extended access permit icmp any any echo response

    allow_ping list extended access permit icmp any any source-quench

    allow_ping list extended access allow all unreachable icmp

    allow_ping list extended access permit icmp any one time exceed

    allow_ping list extended access udp allowed any any eq isakmp

    allow_ping list extended access allow esp a whole

    allow_ping ah allowed extended access list a whole

    allow_ping list extended access will permit a full

    allow_ping list extended access permit tcp any any eq ssh

    access-list extended ip allowed any one sheep

    icmp_inside list extended access permit icmp any one

    icmp_inside of access allowed any ip an extended list

    pager lines 24

    asdm of logging of information

    Outside 1500 MTU

    EIGRP MTU 1500

    management of MTU 1500

    no failover

    ICMP unreachable rate-limit 1 burst-size 1

    ICMP allow all outside

    don't allow no asdm history

    ARP timeout 14400

    Global 1 interface (outside)

    Access-group allow_ping in interface outside

    Can't say I've seen this before, but SSH is easy to do on the SAA.

    I recommend you to take out the first interface access list to see if that would be it.

    You have published only a partial section of the config, but make sure you have the SSH command with the address of the subnet that you connect from. Your config is no longer visible as I type this but try "SSH 0.0.0.0 0.0.0.0 outdoors. This allows all subnets access to the external interface. This command works as an access list to restrict connectivity to approved subnets. i.e. ' SSH 10.0.0.0 255.0.0.0 out "only allow hosts on the 10.x.x.x network to connect via SSH.

    Turn 'debug ssh' to see what errors are too.

    And, you can always remove your keys (related encryption rsa key) and rebuild their return (encryption key generate rsa 1024 mod gen). This will make your ssh client, I use PuTTY, think that this is a new feature and invites the OK to connect.

    Good luck.

    Kevin

  • Change the IP address of the external Interface

    I need to change the IP address of the external interface remotely.  I have SSH in to the ASA plan and make a change.  I can't be there to make this change, since the site is out of State.  There will be problems?  The current configuration is

    interface Ethernet0/0
    nameif outside
    security-level 0
    IP 66.102.7.22 255.255.255.248

    The new IP address will be 66.102.7.18 255.255.255.248.  Also, is this the right syntax?

    interface Ethernet 0/0

    no address ip 66.102.7.22 255.255.255.248

    IP 66.102.7.18 255.255.255.248

    Thank you.

    Diane

    Diane,

    If you access the ASA via its public IP address on the external interface, and if you change this IP address, you will lose communication with the ASA.

    It's better if you can make the change from the inside.

    If you need to change remotely, you can change the IP address, and then try the SSH connection to the new IP address.

    However if a problem occurs, you cannot access the ASA.

    The syntax is correct.

    Federico.

  • VPN SSL from the inside on the external interface

    Hi all

    First of all I know that I can activate the SSL interface inside, but that's not what I need or want.

    Scenario:

    Several interfaces and VLAN on the SAA (running 8.0.5).

    SSL VPN configured and enabled on the external interface.

    Need to know if it is possible to access the SSL VPN from other interfaces directly to the IP address external interface, something like her hairpin.

    Possible a solution (if it exists) with or without NAT (I have public IPs on some interfaces).

    This will be useful for users who can connect any interface (inside, outside, or other) and with only a DNS record, I'll be able to manage everything.

    Concerning

    PS: Is DNS doctoring an option? The tests that I have done this does not work.

    Post edited by: rcordeiro

    Hello

    Unfortunately, it is not possible. You cannot communicate with an ASA interface which is not directly connected through the firewall.

    Kind regards

    NT

  • Static and VPN on the external interface

    Hello

    Can someone tell me if it is possible (and if so, how) do vpn enabled on the external interface and to have something like:

    public static x.x.x.x interface (indoor, outdoor)

    IE: I have two addresses ip - one for the router an e0 on the pix. I create a static and lists of access to allow inbound http/https server inside but I also want to allow vpn hit e0 and work. My configs work if I use an ip address 3 for the static, but not if they share. I can imagine that the static method takes the vpn traffic before the pix can use it OR maybe as the pix has no route to the now (due to the static method) that it cannot answer?

    Hope I'm making sense

    Thanks for the time spent on this

    see you soon

    Andy

    I think you want something like this:

    public static tcp (indoor, outdoor) interface http 10.10.10.10 http netmask 255.255.255.255 0 0 (where 10.10.10.10 is your web server)

    public static tcp (indoor, outdoor) interface https 10.10.10.10 https netmask 255.255.255.255 0 0

    access-list 101 permit tcp any host x.x.x.x eq 80 (where x.x.x.x is your IP interface)

    access-list 101 permit tcp any host x.x.x.x eq 443

    Access-group 101 in external interface

    It will be useful.

    Steve

  • Telnet on PIX with the external interface

    Is there a way to telnet in PIX Firewall through the external interface?

    SSH is a valid method to access the site, but I wonder if there is another way to do it. PDM is another tool for access and modification of the configuration.

    Any help will be useful.

    Best wishes

    Onur

    I'm pretty sure that Telent directly to the external interface of a PIX is not available. It is such a big security risk that it is not offered as an option.

    SSH is a much better way to go (even if it's only SSH1).

    You can probably VPN in your network and Telnet from inside.

    Good luck

    Scott

  • Cannot ping inside the ASA from the inside interface

    Don't know what I did wrong... appreciate any help

    Here is the page layout

    laptop--> cisco 3750 switch--> ASA5505 firewall--> future VPN tunnel

    Laptop, switch interface VLAN and inside the ASA are all in the same subnet

    Switch and ASA have all interfaces local network VIRTUAL 52 (the subnet in question), except for the external interface

    -----------------

    This is the problem

    laptop getting ip addressing and def GW via DHCP from the firewall

    switch and FW can ping each other without problem

    FW can't ping, still gets the DHCP scope.

    Thank you

    Dave

    Hello

    How did you setup?

    The laptop is connected to a port of the 3750 (VLAN 52).

    The connection between the 3750 and the SAA is a chest or a link L3?

    If the 3750 has a SVI belonging to VLAN52, you can ping from the correct PC? As well as the ASA?

    Federico.

  • Secondary public network on the external interface

    We already have a range of public address configured on the external interface (213.XX. YY. ZZ/29). Our supplier we've assigned a new range of public addresses (62.XX. YY. ZZ/29).

    How can I configure this on the PIX?

    PS: as far as I know, the secondary addresses are not possible!

    Hello

    You don't need to configure anything on the PIX make you just as your ISP routes the new addresses to your PIX - then you can use the new address to what you like.

    Concerning

    Kim

  • MULTIPLE ADDRESSES ON THE EXTERNAL INTERFACE IP

    Hi all

    We put in place a number of ASAs for use with corporate VPN. When remote users connect using anyconnect they can hairpin on the Internet from Headquarters and must assign a public IP address for this purpose. To avoid people getting the same public address every time they go to the internet, we want to set up a pool of public addresses which will be awarded at random to the user of the VPN. Also, for their incoming connection requests, we have a ddns that solves a unique ip address for incoming connections. So, in summary clients connect to a single IP address on our ASAs, then hairpin at the internet and receive a public IP address from a pool. Look at us a few options to do so, but would appreciate any suggestions as to how best to achieve this goal.

    Thank you

    Hello

    It seems to me that the order of the chosen one NAT IP address of the NAT pool is random. I tested on my home with a pool of public addresses small ASA5505.

    I don't know if there is difference between different levels of Software ASA or rather the NAT configuration format. Since the 8.2 (and below) and 8.3 format (and more recent) is completely different.

    If we guess you configure NAT pool for VPN Client users connected to the ASA then configurations need you so

    Software of 8.3 and above

    permit same-security-traffic intra-interface

    object-group, network VPN-POOL

    Description the user VPN address Pools

    object-network 10.10.10.0 255.255.255.128

    object-network 10.10.20.0 255.255.255.128

    network of the PUBLIC-POOL object

    1.1.1.1 range 1.1.1.254

    interface of VPN-POOL PUBLIC POOL dynamic NAT (outside, outside) after auto source

    8.2 software and below

    permit same-security-traffic intra-interface

    NAT (outside) 200 10.10.10.0 255.255.255.0

    NAT (outside) 200 10.10.20.0 255.255.255.0

    Global 1.1.1.1 - 1.1.1.254 200 (outside)

    Global 200 (external) interface

    I don't know what is the amount of your user, but I guess you don't such a pool of important public addresses for users. The configurations above also contain a dynamic PAT when the NAT pool runs out.

    Is that what you're looking for?

    Hope this helps

    -Jouni

  • Can't ssh on pix from the external interface

    I am using s/w ver 7.0 (4).

    The config for ssh is:

    generate crypto module rsa keys 1024

    WR mem

    SSH a.b.c.d 255.255.255.255 outside

    but it does not work.

    Help, please

    Yes, if your external interface is mapped to y.y.y.y, then you will be not able to ssh to x.x.x.x as it will be pass on to y.y.y.y.

    You can change the static 1 to 1 to the port for each particular port address translation you need sent to y.y.y.y.

    Please evaluate the useful messages.

  • VPN site-to-customer contact on the external interface

    Hello

    I would like to configure client-to-site ipsec vpn using asa as an attachment. I tested, but it seemed that it did not work. I don't know if it of possible or not. Could someone advise me please?

    Thanks in advance,

    Nitass

    Network diagram

    Here's what you can do. On the SAA add a static host for the server route, but do point to the inside interface of the firewall.

    route inside 10.0.2.100 255.255.255.255 10.0.1.254

    The firewall knows that he has to get out of the e2 interface because it is directly connected.

    On the server, you will need a static route to the VPN Pool pointing on the firewall.

    route add 10.0.3.0 mask 255.255.255.0  10.0.2.254

    On the firewall, you also have to add a route for the VPN Pool.

    route inside 10.0.3.0 255.255.255.0 10.0.1.200

Maybe you are looking for