5505 out-of-the-box web access

[David Thulin]

Hi!

I am probably doing something remarkably dumb...I just can't seem to fix it.

I packed up the 5505, plugged everything in, got an IP (the 5505 responds to ping) but I get a timeout when trying 192.168.1.1/admin. I tried using W7/IE and Chrome book/Chrome with identical results. Help!

Thanks,

David

[David Thulin]

As said. Remarkable. I needed to force the browser to httpS://.

D

[David Thulin]

OK - next challenge. When I try to do an IP-change of the ASA from ASDM the ASA hangs. The only way I get it alive again (distribute DHCP, respond to ping) is by cycling power. Then it is back to the old IP. Changing stuff like the device name and saving it works - verified via console.

I am guessing that ASDM changes the IP, loses connection and never saves. Should I maybe do IP/DHCP via console and first then connect via ASDM?

David

[David Thulin]

Hi again!

I seem to be stuck in a catch 22. I can't change the device IP because it does not match DHCP and I can't change DHCP because it does not match IP. Same with DHCP turned off. Both CLI and ASDM tried.

What am I doing wrong?

D

[Marius Gunnerud]

You need to connect to the ASA using a console cable. from there you can change the interface IP and the DHCP no problem.

Another option, depending on what license you have installed, is to create a 3rd VLAN with a separate IP address and then connect to the port you configured to be in that vlan, adjust the IP address on your computer to correspond to the same subnet as the newly configured interface and connect.  Then you should be able to change the inside interface IP and the DHCP also.

[David Thulin]

Thanks! I thought that was what I was doing, but maybe not. I also temporarily switched the subnet to 255.255.0.0 (back now) and it got a new IP, DHCP works, it responds to ping, CLI works, but now ASDM is dead. Both via browser and local copy. Both http:// and https://.

I set "no shutdown" on all ports...what am I doing wrong?

Thanks again!

D

[Marius Gunnerud]

If you have change the IP of the inside interface and asdm was working earlier, then you only need to add the following command to allow access from the new subnet(where 192.168.2.0 is the new subnet):

Http 192.168.2.0 255.255.255.0 inside

[David Thulin]

You are my hero! Thanks a million!

D

[Marius Gunnerud]

Great! Glad you got it working.

Please rate helpful posts :-)