Our pix 506e firewall (this is the first time we are setting it up - it is a used device) is connected through ethernet 0 to a router, but we are unable to find the IP address assigned to it to access the configuration utility - Cisco PIX Device Manager (PDM). We are following the instructions seen here; http://www.cisco.com/en/US/docs/security/pix/pix62/quick/guide/506quick.html.
Our configuration is as follows;
internet - modem - router - pix
The router management software does not reveal it either. The Pix documentation states that the inside interface of the PIX Firewall is assigned 192.168.1.1 and the PDM can be accessed from https://192.168.1.1/startup.html. We've connected clients (with an automatically assigned IP) to the Pix through ethernet 1 and tried to connect to the PDM unsuccessfully.
We are aware that the PDM could be accessed from a console as seen here;
but we don't have these accessories at the moment.
The routers IP address is 192.168.1.1 and it assigns ips beginning from 192.168.1.2 - 192.168.1.x...
It would look like the Pix could not be 192.168.1.1 as it is the IP of the router. Is there any advice or suggestions you have that would help us find the IP address of the pix connected to the router so we could access the PDM to configure it?
if the firewall was used .. it is probably already configured with different IP addresses and user access. The only way I can see is by consoling in to the pix and do a password recovery as per the below procedure. You can then configure the PIX accordingly and get PDM also working.
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...