OK, if I ever get back in I'm going to change them to end with something besides a 1 :|

Your default IP is set by changing the inside interface. The http command allows those hosts or ranges to be able to connect to the firewall via ASDM. If you can't get back in, you could change your workstation IP to the 192.x.x.x address that you accidentally changed, and that should allow you to get back into it. You need to make sure that you are on the same subnet as the new address that you change your ASA to, and also make sure that you've allowed that subnet access before you make your address change. If you haven't saved it since you lost connection, you can always reboot and it will be like it was since the last save.

HTH,

John

Thank you John.

I have been fighting this thing for a long time. Its a good thing my Checkpoint firewall isn't as bad as I thought it was because it has to hold the fort until this thing comes online.

OK, I have two NICs. One is at 192.168.1.28 and one is at 192.168.10.48.

I got back in with my blue telnet cable and Hyperterminal.

I then set the ASA 5505 to use 192.168.1.1 again, then accessed it with https://192.168.1.1 through the 192.168.1.28 NIC.

Once in I went for the Setup Wizard and set the IPs that have permission to access it to both 192.168.1.28 and 192.168.10.48.

I left in place the original 192.168.1.1 because it has a net mask of 255.255.255.0, and the only mask I can give the others is 255.255.255.255, which looks to me like they will be masked out :O

Then I bravely clicked on FINISH, and closed the browser tab.

Next, I went back to Hyperterminal and entered Config t, then interface vlan1, then ip address 192.168.10.1.

Then I put my ethernet cable into the NIC that is set to 192.168.10.48 and attempted to access the ASA 5505.

It produces a dialog telling me that authentication is required, and asking for my username and password.

When I use 192.168.1.1 this doesn't happen. But I had given it a password. After that it asked for the password a couple of times and was happy when I put it in. Then it quit asking for it.

So I enter the password, leaving the username blank, and it asks for it again.

So I try leaving it blank, and it asks for it again.

So I try entering CISCOASA, which is the username it says it has, and the password, and it asks for it again.

Reckon I'll go back to Hyperterminal and change the password to nothing and see if that helps.

I tried removing the password with

passwd

and not entering anything, but it said it was an incomplete command. So I tried

no passwd

and it took it. But still when I go back to the browser and try to enter the ASA 5505 as 192.168.10.48 I am challenged for a username and password, and nothing I give it is acceptable.

The passwd statement is only going to be used for intial login and telnet. If telnet is configured to allow connections but no authentication method is specified, it will prompt the user for the passwd.

With that said, HTTP(s) access to the ASA is going to want to authenticate to the local database. This means that you need to create a username within the ASA. In global config, type: "username cisco password cisco privilege 15"

Type the newly created credentials into the prompt when trying to access the ASA via HTTP(S).

HTH