Cisco ASA 5505 can't connect to internal network

I'm trying to change the internal IP address on my Cisco ASA 5505 so I can connect it to my building LAN.  I used the startup wizard but it rejected saying Internal IP subnet does not match DHCP range, even though I disabled DHCP.

I then manually changed the internal IP address making sure DHCP was disabled.  That worked but ASDM no longer connects to the device, even though I can ping it with the new address.

Is there some trick to changing the internal IP adress?  Any help is very much appreciated.

Kind Regards, Peter.
Peter_CullAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

acronymsCommented:
Not much experience on the later models but on the older ones you deleted the dhcpd lines which allowed you to change the internal IP addresss but before you did that you should allow telnet access from the new subnet the new internal address is on. By not doing this you block yourself as you are on a new range but you cannot administer it.

Hope this makes sense

Regards

0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Peter_CullAuthor Commented:
Thanks, I think you're right.  Problem is I cannot connect to the box.  Is there a way to do a factory reset without ASDM?

Regards
0
acronymsCommented:
Eeekk!! You can connect through the console cable and eliminate the issue.

You will then be in the system but not connecting through the IP of the unit. You can rectify anything you have done from there.

Did you commit the running config to the memory? If not just reboot the cisco and the config will be back to the way you last did a write mem or equivalent on the ASDM. I suspect the ADSM does this for you without you really knowing about it.

Regards



0
clonga13Commented:
Connect to the console port and check to make sure your telnet and HTTP allow your new network to access it from the inside. ASDM uses HTTPS to connect and make changes. If you really want to go to factory defaults, then use the startup wizard or hold down the reset button during boot up.
0
Peter_CullAuthor Commented:
That worked perfectly.  I reset to factory defaults using console port (I don't think reset button does anything), then in Administrative Access page added internal IP range.

Great to get it working.  Many thanks.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Cisco

From novice to tech pro — start learning today.