05-20-2011 06:34 AM - edited 03-06-2019 05:10 PM
I don't have access to a console cable and am trying to connect to our ASA5505. I've tried multiple recyclings, multiple computers and cables but just cannot connect to https://192.168.1.1/admin despite getting allocated an IP address. I've also tried manually setting the computer's IP to 192.168.1.2.
I'm sure I'm doing something incrdibly stupid as I have no experience of LANs/firewalls or routers and would be really grateful if someone could tell me how to connect or even just to ping the Cisco box.......
I've also tried several hard resets of the 5505.
Thanks in advance!
05-20-2011 07:08 AM
having looked at the packets. I'm sending out lots of DHCP Discovers but getting nothing back from Cisco. I was incorrect before about the IP address - the client is self-allocating an address (169.254.x.x not 192.168.1.x)
05-20-2011 10:43 AM
Hi,
the client is self-allocating an address (169.254.x.x not 192.168.1.x)
This is what happens on Windows boxes when they get no DHCP replies.
So first put a static IP on the host and then try to ping the ASA. Is there something in between the ASA and host?
Regards.
Alain.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide